Version 4.2.5 upgrade failed, need help recovering. - G1 Android Development

Cyanogenmod version 4.2.3 then 4.2.4 were running great on my G1 for a couple of weeks. Recently, I noticed the Cyanogenmod Updater saying the 4.2.5 stable was available. I went ahead downloaded it, did a Nandroid backup and then flashed it. However, on reboot, the Android splash screen kept freezing then trying the reboot. I could not get past this screen. I tried reflashing a couple of times with the same frozen results.
I did a factory reset. I can fully reboot, but now it appears I have regressed back to Kernel version 2.6.29. I also, don't think I have root anymore since I tried to sudo on terminal and it told me I don't have permission. What happened?
When I go to recovery mode, (pwr + home) I get a triangle with an exclamation point. I get the "E:Can't open /cache/recovery/command" I only have four options: reboot system, apply sdcard:update.zip, wipe data/factory reset, wipe cache partition.
I'm guessing that Apps to SD is not working because I might have some vanilla recovery image taking over that is not Cyanogenmod so it does not see the cache on the SDCard partition that I have.
I also noticed that I can get the "Fastboot" screen if I do the Pwr + Camera btn. I've seen posts that I should be able to get everything back that way, using but I haven't found a step-by-step on how to use if for noobs.
Can anyone suggest how I can get back everything? I still have all my data including backup files and apps on the sdcard.
Thank you.

try posting this in the 4.2.5 thread and not starting a new thread just for your problem.

Not only did you fail to flash your phone correctly but you also failed to post on the correct forum!

Currently, the CyanogenMod thread has over 5,000 replies. Could you imagine how cluttered this forum would be if everyone was as inconsiderate and selfish as you, and felt the need to open a new thread whenever an issue with CyanogenMod occurred?

jay652 said:
Currently, the CyanogenMod thread has over 5,000 replies. Could you imagine how cluttered this forum would be if everyone was as inconsiderate and selfish as you, and felt the need to open a new thread whenever an issue with CyanogenMod occurred?
Click to expand...
Click to collapse
There is also a Q&A section
Locked

Related

Completely Bricked Phone (?)

Hi smart people!
Just to throw it out there, I am not very tech savvy so excuse me if I misuse terms and such.
I believe I completely bricked my phone (I hope I'm wrong). After I downloaded Cyanogen through ROM Manager, my finger stumbled on the "continue" or "next" button or whatever WITHOUT checking the boxes to clear data, etc. I believe this is where I went wrong as I think I followed all other steps correctly (fyi I used the one click recovery flasher and made a back up).
Now when I turn on my phone, it goes from the stock LG loading screen to a modified LG loading screen (Cyanogen's I'm assuming) but it gets stuck there.
I've been searching on the different threads for quite a while and pressing the different combinations of volume up/volume down/power don't seem to do anything. I cannot get to the recovery screen.
Please help! I will forever be indebted to all of you. I am stupid and shouldn't have tried to do this on my own. Thanks in advance
What you will need to do is flash CWM via NVflash then boot into CWm and install your ROM.
If you flash CWM via ROM Manager it causes problems like what you're describing, I know from my own experience of following a friends instructions and doing that then having that exact issue. After getting my phone working again I then started to frequent the boards here.
As soon as I read the first couple lines I saw rom manager and saw the problem, you to search something that you have typed out all within this thread... I'm not near a computer but you should just search through these threads and you find your solution in detailed description. You need to get recovery from nvflasher just search that
Sent from my LG-P999 using xda premium
thanks for your replies
thank you to both of you for your prompt replies. i will try doing this within the next couple hours and post any results. this is the thread i found with the information you guys gave: http://forum.xda-developers.com/showthread.php?t=1058649
thanks again
No, that's not for G2x. Go here: http://forum.xda-developers.com/showthread.php?t=1056847
Ya it needs to be the one that gunnman wrote out for people.
Sent from my LG-P999 using xda premium
Hey guys...on step #10, it says to "select 'have disk'" but i do not see that option in the list.
Thanks
okay now i realize i should have been doing the cwm recovery. sorry guys and thanks again
reboot error
hey guys,
I successfully was able to boot into cwm and then i restored a backup from yesterday. however when rebooting, it displays the LG logo and then the screen goes black and the back light flickers on and off. not quite sure what to do now...if you guys could let me know what i should do or post a link to another thread, i'd really appreciate it. i honestly have been going through other threads but i guess i'm just not competent enough to know which directions apply to my problem.....
thank you..hopefully this is the last time i'll have to bother you!
The back-up could be corrupt and since the one time I had a problem with a nandroid was when it was created after ROM Manager sent the info to CWM, that's likely the case. Just redownload CM7 to your SD card, along with Gapps, wipe system, data and cache then flash CM7 followed by Gapps.
justintheshark30 said:
hey guys,
I successfully was able to boot into cwm and then i restored a backup from yesterday. however when rebooting, it displays the LG logo and then the screen goes black and the back light flickers on and off. not quite sure what to do now...if you guys could let me know what i should do or post a link to another thread, i'd really appreciate it. i honestly have been going through other threads but i guess i'm just not competent enough to know which directions apply to my problem.....
thank you..hopefully this is the last time i'll have to bother you!
Click to expand...
Click to collapse
Have you wiped everything before restoring your backup through CWM? If not, boot into CWM, wipe data/factory reset, go to mounts and storage, format system, then go into advanced options, wipe delvik cache, then restore your backup.
I'm guessing you did a backup through rom manager, so if this doesn't work, you'll have to download a rom of your choice from the development section of this forum, load it onto your sd card through CWM although this is not recommended but you won't have any other choices, (to mount your sd card in CWM, go to mounts and storage, mount sd card), then wipe everything as mentioned above, then flash the new rom.
Or you can follow the instructions on this thread http://forum.xda-developers.com/showthread.php?t=1248644 to flash 2.3.3 via nvflash to get a working phone for now until you learn how to properly flash custom roms.
Hope this helps
P.S. for future reference, you did not brick your phone, you got stuck in a boot loop, you know your phone is bricked when you don't see anything on the screen when you turn it on, usually it's just a software issue, but sometimes it could be hardware, for example I burned the motherboard on my previous android phone trying to customize it lol
jj_z1 said:
Have you wiped everything before restoring your backup through CWM? If not, boot into CWM, wipe data/factory reset, go to mounts and storage, format system, then go into advanced options, wipe delvik cache, then restore your backup.
I'm guessing you did a backup through rom manager, so if this doesn't work, you'll have to download a rom of your choice from the development section of this forum, load it onto your sd card through CWM although this is not recommended but you won't have any other choices, (to mount your sd card in CWM, go to mounts and storage, mount sd card), then wipe everything as mentioned above, then flash the new rom.
Or you can follow the instructions on this thread http://forum.xda-developers.com/showthread.php?t=1248644 to flash 2.3.3 via nvflash to get a working phone for now until you learn how to properly flash custom roms.
Hope this helps
Click to expand...
Click to collapse
He's already flashed CWM the right way, and tried to restore from a nandroid. I already mentioned getting a different ROM, he's already stated that he got this all started trying to flash CM7. Please read the posts which have already been made, we don't need the same information being posted again, if someone already posted something and you feel it needs clarified then clarify but from what I can tell you read one post and that was it.
Волк said:
He's already flashed CWM the right way, and tried to restore from a nandroid. I already mentioned getting a different ROM, he's already stated that he got this all started trying to flash CM7. Please read the posts which have already been made, we don't need the same information being posted again, if someone already posted something and you feel it needs clarified then clarify but from what I can tell you read one post and that was it.
Click to expand...
Click to collapse
I really hate posting anything that doesn't have to do with anything phone related but I just couldn't stop myself from replying to your post!
1) I actually read all posts in the thread!
2) I did not in any way suggest that he didn't flash CWM the right way, I merely asked if he had done a full wipe before restoring his backup!!
3) Your reply was submitted while I was typing mine, so I'm sorry I didn't check the thread again before submitting my reply!!!
4) I'm well aware of what he tried to do already, but thanks for repeating it!!!!
5) If YOU read all previous posts you'll notice that my post does not exactly replicate any other, there's some new information in there that the OP might find useful!!!!!
6) From what I can tell, you need to work on your english and comprehension skills!!!!!!
To the OP, sorry for trolling your thread with this post, but I just couldn't help it, and to Bonk I hope you'll be the mature one and not reply to this post.
Is that to say you're immature? If one were to judge by the number of exclamation marks you have I'd say yes.
The only "new" thing was asking if he wiped before the restore, which, at this point, would be useless to ask as I already told him to make sure to wipe.
To the OP: How goes everything thus far?
thank you
that's what i ended up doing and it worked. thank you so much for all your help!
Волк said:
The back-up could be corrupt and since the one time I had a problem with a nandroid was when it was created after ROM Manager sent the info to CWM, that's likely the case. Just redownload CM7 to your SD card, along with Gapps, wipe system, data and cache then flash CM7 followed by Gapps.
Click to expand...
Click to collapse
And dalvik cache for good measure, even though it is stored on the cache partition and will probably get wiped when you wipe cache. Sometimes it's good to overdo thing's.
Unable to do anything!
Well i was playing with the phone, rooted and kept playing with different ROMS till i would have found a good stable one, but something happened, I ended up not being able to use any functions in cwm (apply update from..., backup and restore, install from zip). I wiped data/factory reset, cache partition, dalvik and i have the ROMS inside, i can see them in CWM. just can't read them. or any zip i use. what happened? is this bricked? if so do i have to go from scratch with the phone and use SDK?
efrembarrow said:
Well i was playing with the phone, rooted and kept playing with different ROMS till i would have found a good stable one, but something happened, I ended up not being able to use any functions in cwm (apply update from..., backup and restore, install from zip). I wiped data/factory reset, cache partition, dalvik and i have the ROMS inside, i can see them in CWM. just can't read them. or any zip i use. what happened? is this bricked? if so do i have to go from scratch with the phone and use SDK?
Click to expand...
Click to collapse
Start over. Do what it states here: http://forum.xda-developers.com/showthread.php?t=1248644
efrembarrow said:
Well i was playing with the phone, rooted and kept playing with different ROMS till i would have found a good stable one, but something happened, I ended up not being able to use any functions in cwm (apply update from..., backup and restore, install from zip). I wiped data/factory reset, cache partition, dalvik and i have the ROMS inside, i can see them in CWM. just can't read them. or any zip i use. what happened? is this bricked? if so do i have to go from scratch with the phone and use SDK?
Click to expand...
Click to collapse
Did you battery pull and start over?
Sent from my LG-P999 using xda premium
UNROOT help
Hello again smart people,
I was hoping we would never meet again (for the better) but unfortunately i must unroot my phone to receive work emails. I have tried unrooting my LG G2x multiple times but to no avail thus far.
Here is the process I have tried:
1) boot into recovery - wipe cache/data factory reset, wipe cache partition, wipe dalvik cache
2) restore - using stock rom i found online
3) flash stock recovery image using nvflash
4) (attempt to) unroot using superoneclick - AFTER GOING THROUGH MULTIPLE STEPS, IT SAYS "TRUE" UNDER "CHECKING IF ROOTED". (also, i know it is rooted because it says the phone already appears to be rooted when i try to root again).
Do you guys have any idea what the issue could be?
Thank you in advance...

[Q] Resurrection Remix ICS 1.0 SGS2 - backup restore issue

Hi folks,
Sincere apologies if this is answered elsewhere. I've searched the development thread and done a few searches elsewhere but it's not come up.
I'm running Resurrection Remix 1.0 on my Galaxy S2 i9100. So far, everything works great - except the gyroscope. And specifically, panning screens when I'm moving apps and widgets about.
This is such a minor gripe that I feel sort of guilty for bringing it up, but I'd appreciate any help! I've tried to flash the fix that sorts the text out but it comes up with the following error: E:signature verification failed
I'm not sure if that's even going to help, but I figured it wouldn't hinder it. I have wiped the cache partition first, and I'm trying to install the zip file from an SD card.
Sure I'm making a fairly elementary mistake somewhere!
Cheers,
Nick
Ugh.
Right, I've made a bollocks of this. In installing the "fix," I've wiped the ROM and all the apps I had installed with it.
Now, I had backed up using CWM Recovery and Titanium Backup - but now those apps aren't on my phone (well, they're buried in it, but they're not part of the GUI and I can't access them). What's more, I can't reinstall the apps I had downloaded from Google Play.
I assume that's an issue at their end - and I assume that I need to use Titanium and CWM to recover the back-ups - but is that the case?
Again, any advice much appreciated...
I've installed an app called Recovery Manager, and the only backup it can see is one I made a couple of days ago. Which I'll take.
The problem I have is, when I boot into recovery mode, it's not using the CWM interface I used to flash the damn ROM in the first place; the CWM logo isn't showing, and it's all blue, rather than orange. There's an Android with a rotating blue shape on its belly. Not sure if that helps!
But either way, I can locate the folder in this new recovery mode but there's nothing in it to recover (or so it seems).
Really stumped.
Hi, I´m running the same ROM and have the same problem. The ROM overwrites CWM somehow and so you can´t access it for recovery. When you boot into recovery, all you get is the stock recovery. If you have an external storage card, Max at Galaxy2root.com offers a solution and a zip file to run to get CWM temporarily - but it disappears after a reboot. I haven´t tried it yet. Tomorrow!
All my reading indicates that there will be no fix for this until WestCrip changes the basic ROM. So we are stuck with a temporary solution.....
U can install.CWM by rom manager n reboot into recovery

[Q] Help! Can't get past M logo after EOS4 installation on STINGRAY

Hi all, I've been rooting and installing custom roms on lots of devices for a couple of years now. I didn't consider myself a noob after successfully getting cyanogen 9 or 10 on tenderloin and cm10.2 on tate.
However, it seems that I have completely missed something while installing EOS4 20130705-199 on the Motorola Xoom.
I had no problems with SDK install, adb, fastboot, got TWRP running w/ root. All this is from stock, mind you, if that makes any difference.
So then I decided to grab teamEOS's EOS4 and run that as the newest Android OS (that is arguably stable) that has been ported to the Xoom.
Well, I think I must have rebooted at a point that I wasn't supposed to, because I lost the ability to load the EOS-stingray-20130705-199.zip via ADB.
So I went into TWRP recovery and attempted to ADB sideload the rom file. Seemed to work for transferring, but after wiping caches and rebooting, I'm stuck on MOTO dual-core logo. I can get back into TWRP, though so I tried doing factory reset, wiping caches, and installing from an 8GB microSD card (/sdcard). Wiped caches again and then reboot... Same result, MOTO dual-core logo.
Ok, so now to barebones... Boot into fastboot mode and flash boot.img from EOS-stingray-20130705-199.zip and then boot back into TWRP and install rom again.... Same result, MOTO dual-core logo.
As you can probably guess at this point I'm getting a bit frustrated. I'm about ready to see how a Xoom flies when launched from a skeet clay launcher. Pull!..... BLAM! Just kidding, but I really do need to get this device back running.
Does anybody have any suggestions?
199 may be bad (and be why it's not booting), try EOS-stingray-20130617-197 instead.
Format system partition first (in TWRP it's in Wipe->advanced), factory reset, then flash the EOS-stingray-20130617-197.zip AND an appropriate Gapps. Do not factory reset after the rom or gapps (for various reasons I am to tired to go into.) Assuming you have a good copy of the 197 it should boot.
airesch said:
199 may be bad (and be why it's not booting), try EOS-stingray-20130617-197 instead.
Format system partition first (in TWRP it's in Wipe->advanced), factory reset, then flash the EOS-stingray-20130617-197.zip AND an appropriate Gapps. Do not factory reset after the rom or gapps (for various reasons I am to tired to go into.) Assuming you have a good copy of the 197 it should boot.
Click to expand...
Click to collapse
Thanks for the reply. I shall give -197 a try.
As an aside, you don't need to feel obligated to explain your reasons for suggestions (re: Do not factory reset). The advice alone is worth it's weight in gold.
Bad news.
I just downloaded -197 fresh from goo, in fact I did it twice because I couldn't believe the results.
It actually fails to install giving the error "cannot open zip file" -199 never did that.
I also tried -131 (cdma) just to prove to myself that I have the right model. Same results, MOTO logo no boot.
Can't actually believe i am saying this, looks like goo's version is corrupt (my md5 doesn't match theirs and I just looked up the cached version of the webpage and it has d81cded40671c9c0963f95273859dbdd (which is what mine is.)
I will try to pm you a link of the file I have on my dropbox in a bit.
Thanks for this AIRESCH
Your version of -197 is working perfectly.
I think we need to sound the alarm here at XDA, because there are going to be a bunch of pissed off people (like me) who think they have a good image to flash when actually they have a bin of gibberish!
Thanks again.
punishermoose said:
Thanks for this AIRESCH
Your version of -197 is working perfectly.
Click to expand...
Click to collapse
Excellent
punishermoose said:
I think we need to sound the alarm here at XDA, because there are going to be a bunch of pissed off people (like me) who think they have a good image to flash when actually they have a bin of gibberish!
Click to expand...
Click to collapse
Not sure this is necessary, goo has been replacing/upgrading hardware and may not have everything up yet (none of the files were there for a good week at the start of the month.) They may get the right files back up before too long. It does suck for anyone trying to get the files right now tho.
I'm glad your up and working.
Do not factory reset after the rom or gapps (for various reasons I am to tired to go into.)
As an aside, you don't need to feel obligated to explain your reasons for suggestions (re: Do not factory reset).
Click to expand...
Click to collapse
ah, but you don't learn if it's not explained
Reason is: the Xoom only has a 256MB system partition and unfortunately the OS+Gapps (which normally resides in system) as of 4.1 or 4.2 comes to well over this amount. The rom developers HAVE been (they are currently trying to change this) making it so that some of Gapps gets enough copied into the data partition to make everything fit and symlink the files back into system. This has the positive effect of being able to have everything work even without enough space. However the downside is that if you factory reset it will wipe out the files in the data partition, leaving broken symlinks pointing to nothing, and makes it so some of it doesn't work anymore (how much depends on what gapps your using.)
In short: We have awesome devs that are still trying to fix the problem, but their current solution requires you to re-flash gapps (at a minimum, i normally recommend re-flashing both system and gapps) after a factory reset (which is not the end of the world (unless you don't have them both anymore.))
Can someone please share a link with me or pm me please? I still haven't found a working copy of 197 anywhere.
Sent from my SAMSUNG-SGH-I717 using XDA Premium 4 mobile app
SgtTeabag said:
Can someone please share a link with me or pm me please? I still haven't found a working copy of 197 anywhere.
Sent from my SAMSUNG-SGH-I717 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'm in the same boat. Need a good download/copy of 197, please! The goo.im 197 download is borked!!

[Q] chameleon os superuser or root problem

I run chameleon os custom rom on Samsung infuse 4g. Superuser by Clockworkmod got binded/imbedded into rom. Was working fine, then out of nowhere got disabled under superuser settings and will not change back. I select apps only and all other choices but as soon as I select it, it switches back to disable. Google play no longer shows it as an app that I have downloaded so I can't get updates. I have tried installing it again both by just downloading it and by disabling it under app management and downloading it, but both ways when I open it tries to downloading binaries and fails. Same thing happens with any other superuser I try to download. I cannot get it to work. Please help. I no longer want chameleon as my rom because of too many issues with it constantly rebooting and internet only working sometimes. i want to try another rom but can't with superuser not working. Here is my phone info:
> Model #
> SGH-I997
>
> Android
> 4.2.2
>
> Baseband version
> I997UCLB3
>
> Kernel version
> 2.6.35.7-I997UCLB3-CL9997492-g431d68f
>
> CPU
> ARMv7 Processor rev2 (v71)
>
> ChameleonOS version
> 0.7-20130426-unofficial-infuse4g
>
> Build date
> Fri Apr26 16:05:35 AST 2013
>
> Build number
> cos_infuse4g-userdebug 4.2.2JDQ39
> Cng.andros11.20130426 test-keys
robertmlangdon2 said:
I run chameleon os custom rom on Samsung infuse 4g. Superuser by Clockworkmod got binded/imbedded into rom. Was working fine, then out of nowhere got disabled under superuser settings and will not change back. I select apps only and all other choices but as soon as I select it, it switches back to disable. Google play no longer shows it as an app that I have downloaded so I can't get updates. I have tried installing it again both by just downloading it and by disabling it under app management and downloading it, but both ways when I open it tries to downloading binaries and fails. Same thing happens with any other superuser I try to download. I cannot get it to work. Please help. I no longer want chameleon as my rom because of too many issues with it constantly rebooting and internet only working sometimes. i want to try another rom but can't with superuser not working.
Click to expand...
Click to collapse
You mean to say you cannot boot into CWM recovery and flash a different ROM? Interesting. I have an HTC, and the steps to rooting it are in a different order... that after unlocking the bootloader, you install CWM, and then optionally root the stock ROM with the SuperUser package (those who don't do the last step are usually flashing a ROM instead of mucking around for another second with the stock OS).
SU shouldn't be needed for custom recovery. But maybe Chameleon does something weird like not give you a custom recovery you can boot into? If that's the case, you could pop the device into download mode and go back to stock with Odin, effectively starting from scratch.
still need help, thank you.
I am starting to believe more than before that the actual problem is that somehow my phone got unrooted. How do I set my phone in download mode and use Odin? I usually wipe the cache, install the rom, install gapps, wipe cache partition, and wipe dalvik cache. I have never flashed a rom before. Or even better what is the best way to root my phone again now that I am using chameleon? I believe if I can do that it will fix my problems and I can install cyanfox (the latest rom I have downloaded). Do I use super one click? That is what I think I used before but now that I am not using stock rom I don't know what to use.
robertmlangdon2 said:
I am starting to believe more than before that the actual problem is that somehow my phone got unrooted. How do I set my phone in download mode and use Odin? I usually wipe the cache, install the rom, install gapps, wipe cache partition, and wipe dalvik cache. I have never flashed a rom before. Or even better what is the best way to root my phone again now that I am using chameleon? I believe if I can do that it will fix my problems and I can install cyanfox (the latest rom I have downloaded). Do I use super one click? That is what I think I used before but now that I am not using stock rom I don't know what to use.
Click to expand...
Click to collapse
If you are unable to get into ClockWorkMod recovery (hold Vol-Up+Vol-Dn keys while pressing Pwr button) and have it do anything (so your wipe, install, gapps, dalvik - that process would be called flashing). Then I would Odin back to stock.
For this, you would need to get into download mode. IIRC (just sold my Infuse), it is (with the device fully turned off) hold both volume buttons in while inserting the micro usb cable (that is subsequently inserted into your PC). The ODIN program comes with the download packages (hopefully), so extract the whole package, and run that.
Odin should pick up the phone in the first column as "COMX" (e.g. "COM5"). You are good to flash. To the right, there are PHONE and PDA buttons, click on each, and select the corresponding file (that was also in the package) for each (so PHONE will have something like PHONE.tgz.md5). Once both files are loaded, make sure re-partition is UN-checked, and press Start (or Go, or whatever the action word is). This will take a few minutes, but the COMX column should highlight green with "SUCCESS" in the end.
That's all there is to it. The reason why I'm shying away from SuperOneClick is that it was designed for stock gingerbread/froyo, so it has the potential of breaking something. Hope this helps.
EDIT:
Alternatively, you could try pushing su to the device with adb (depends on how you lost root):
Code:
adb shell mount -o rw,remount -t ext4 /dev/block/platform/msm_sdcc.1/by-name/system /system
adb push su /system/xbin/
adb shell chmod 06755 /system/xbin/su
... with this file (extracted).
Source (with mount point changed)
new problem
I am now running cyanfox which runs android 4.4 and Google.process.gapps has stopped keeps popping up. To get rid of it I have to do a factory reset but after a few days it always comes back. I have Googled the problem and tried numerous things to try to fix it but everything only works temporary. What should I do besides get another phone? I can't afford that right now.
robertmlangdon2 said:
I am now running cyanfox which runs android 4.4 and Google.process.gapps has stopped keeps popping up. To get rid of it I have to do a factory reset but after a few days it always comes back. I have Googled the problem and tried numerous things to try to fix it but everything only works temporary. What should I do besides get another phone? I can't afford that right now.
Click to expand...
Click to collapse
I wouldn;t suggest another phoen is things are working well genrally. The problem could lie in the GApps package or the ROM itself. I use the PA Gapps package. If you are having rouble with that one, try from a different date. Just wipe dlavik in between to prevent any nastyness.
If it still persists, try another ROM, like Carbon.
tried installing the new gapps
So far, so good but I won't know for sure for a few days. I'll keep you up to date. Thank you
what version of android is carbon?
Do you have the link for carbon rom for Samsung infuse 4g? And what version of android is it? My phone runs better with those gapps but I am still getting the same problems. I will give it a try but if carbon doesn't work I am definitely going to have to just get another phone. So far I'm. 0-2 on custom roms for this phone. I thought cyanfox would of worked cause I got it off of xda, which really makes me think this phone has some sort of hardware problem but carbon has been around longer. So maybe it will work better.
Carbon is on XDA as well too, and it is based on CM 11 / Android 4.4 Kitkat:
http://forum.xda-developers.com/showthread.php?t=2137800
Hope this works for you... :fingers-crossed:
problems solved
It appears it was definitely a problem with the ROM. Phone has been operating 100% better. :victory: My cache needs to be cleared frequently and some minor problems with the Facebook back but when isn't there problems with Facebook lol. But as soon as I clean out the cache from my apps, everything is running like new again. I greatly appreciate your help. I can't thank you enough.
Was working great then more problems
Joel,
Carbon was running great for me but then all of a sudden android.process.acore has stopped kept popping up along with all sort of other things stopping then eventually GApps not working again. I have erased my contacts, Erased Media, unchecked all my Syncs, I have tried all sorts of other Gapps packages and even another ROM (cyanogen 11) and they work to begin with then the same problems keep coming back. Is it because I went from Gingerbread right to Kitkat? My phone hasn't worked for about a week now with me trying all different ways to fix it. Do I need to install Ice Cream Sandwich then Jellybean before going to Kitkat or do I just need to try even more GApps? I used to install new ROMs all the time but android has changed so much over the last couple years and when i had to get rid of my old phone and went back to my Infuse 4g the old ROM was just completely outdated and now I can't seem to get this right. The phone itself is still a great phone and I don't understand why I am having these issues. I factory reset, wipe cache, wipe dalvik, install new ROM, install GApps, wipe cache again, and wipe dalvik again. I usually don't wipe the cache or the dalvik until after the ROM and GApps install but just lately have been doing the extra wipe just in-case because nothing else is working. But that has failed too. You have been a great help so far and I can't seem to fix this on my own, so again I turn to you for help. Please help me figure this out.
robertmlangdon2 said:
Is it because I went from Gingerbread right to Kitkat?
Click to expand...
Click to collapse
It's possible. I mentioned this before somewhere, but this could be the after-effect of a small /datadata partition, which having a separate partition is standard in a KitKat ROM (at least for this phone). When it fills up, there's no telling what happens.
Both BeanStalk and CM11 have /datadata partition alternatives (the separate partition has been abandoned) built in. You may want to try one of those:
http://forum.xda-developers.com/showpost.php?p=55574460&postcount=3801
http://forum.xda-developers.com/showpost.php?p=56604749&postcount=593
Unfortunately I couldn't find something similar for Carbon.
Thank you!!!!!!
I hate to count my chickens before they're hatched but I truly believe that was the problem. Even Facebook works now. But I thought I had it fixed before then just under a week and it completely messed up and I couldn't even get it to work for a day after that. But it works now. I can't thank you enough. If you ever come across one for Carbon ROM please let me know. This is a good ROM but I liked Carbon better. Again, thank you Joel. :good::good:
Help!!!!!!!!!!!!!!!!!!!!!!!
Sorry to bother you again Joel but I have a major problem again and I dont even know wht happenned. You have helped me through evrything so far and I couldn't be more thankful. There may be nothing you can do to help me, I don't know. I was using my phone as A Wifi Hotspot when out of know where as soon as i got on facebook on my tablet my phone rebooted on it's own into Clockworkmod recovery. when I reboot it, it goes right back into recovery, it wont read the internal sd card and it wont install any zip off any inserted sd card(it reads them but wont install anything, it always pops up with android guy on his back with a red X and a generic error). it lets me erase cache but won't erase delvik cache or format anything, the screen just flashes and it pops back a screen. I dont think the phone overheated because it wasnt hot to the touch at all. I was only using it as a wifi hotspot for about 30 minutes when it happenned. i had used it as a hotspot many times before with no problems and i dont know how it woud be a virus when i wasnt on any abnormal sites. Any help you can give me would be greatly appreciated. Thank you in advance.
Help!!!!!!!!!!!!!!!!!!!!!!!
Sorry to bother you again Joel but I have a major problem again and I dont even know wht happenned. You have helped me through everything so far and I couldn't be more thankful. The phone might be fried and there may be nothing you can do to help me, I don't know. I was using my phone as A Wifi Hotspot when out of know where as soon as i got on facebook on my tablet my phone rebooted on it's own into Clockworkmod recovery. when I reboot it, it goes right back into recovery, it wont read the internal sd card and it wont install any zip off any inserted sd card(it reads them but wont install anything, it always pops up with android guy on his back with a red X and a generic error). it lets me erase cache but won't erase delvik cache or format anything, the screen just flashes and it pops back a screen. I dont think the phone overheated because it wasnt hot to the touch at all. I was only using it as a wifi hotspot for about 30 minutes when it happenned. i had used it as a hotspot many times before with no problems and i dont know how it woud be a virus when i wasnt on any abnormal sites. Any help you can give me would be greatly appreciated. Thank you in advance.
If you can get into Download Mode, I would Odin back to stock. Are you AT&T or Rogers? There are a couple recent threads in this forum with download links, although people have been having difficulties with finding the AT&T variety.
Unfortunately, that's all I can recommend. Good luck.
we'll see how this works out
I just checked and it will go into download mode. So I guess I just need to find the AT&T thread of Oden and hopefully that works. I have never done it that way before but I read your previous response much earlier in this thread on how to do it and it sounds pretty simple so hopefully I can do it. If you can find a link to the at&t version before me it would definitely help but I will see what I can find.
robertmlangdon2 said:
I just checked and it will go into download mode. So I guess I just need to find the AT&T thread of Oden and hopefully that works. I have never done it that way before but I read your previous response much earlier in this thread on how to do it and it sounds pretty simple so hopefully I can do it. If you can find a link to the at&t version before me it would definitely help but I will see what I can find.
Click to expand...
Click to collapse
Looks like you are all set for the files then.
I just PM'ed everyone who I've recommended those packages in the past. Hopefully I get a bite.
found a thread but need your help
I found a thread with links but with what is written on this thread I am confused. The thread link is
http://forum.xda-developers.com/showthread.php?t=1613523
I'm not sure what to download and if anything needs to be changed after downloading it or if this link is a waste of my time. I was hoping you could help. Thanks.
robertmlangdon2 said:
I found a thread with links but with what is written on this thread I am confused. The thread link is
http://forum.xda-developers.com/showthread.php?t=1613523
I'm not sure what to download and if anything needs to be changed after downloading it or if this link is a waste of my time. I was hoping you could help. Thanks.
Click to expand...
Click to collapse
I would recommend Option D for what you need, but AFAIK, the links on this page are dead.
If you go to the last page though, there is a link for Option C, which would work for your needs. Hope this helps.

[Q] problem fixing samsung sgh-T699

Hey,
i have samsung sgh-t699, i once updated my phone to cm 11 via its settings panel and in the middle of update it failed and said error.
so i had to find a way to fix and i downloaded cyanogenmod cm11 nighty and installed it via install zip from external sd card and it was sucessfull but i could no longer install any of the previous softwares i had cause it said software already exist on your phone.
so i decided to start all over again i wiped data/factory reset, wipe cache, wipe davik and re installed cm 11 and gapp and the cwm said installation from sdcard sucessfull. but when i rebooted system nothing hapens i just see the cyanogen mode animation going round and round and my phone wont boot any futher step than that it just heats up untill i switch it off. i did the reinstallation several time , flashed a new odin all the time untill my download binary count reads 15 and the same thing happens.
i dont know what else to do, please anyone any idea....please help
farhakassim said:
Hey,
i have samsung sgh-t699, i once updated my phone to cm 11 via its settings panel and in the middle of update it failed and said error.
so i had to find a way to fix and i downloaded cyanogenmod cm11 nighty and installed it via install zip from external sd card and it was sucessfull but i could no longer install any of the previous softwares i had cause it said software already exist on your phone.
so i decided to start all over again i wiped data/factory reset, wipe cache, wipe davik and re installed cm 11 and gapp and the cwm said installation from sdcard sucessfull. but when i rebooted system nothing hapens i just see the cyanogen mode animation going round and round and my phone wont boot any futher step than that it just heats up untill i switch it off. i did the reinstallation several time , flashed a new odin all the time untill my download binary count reads 15 and the same thing happens.
i dont know what else to do, please anyone any idea....please help
Click to expand...
Click to collapse
It might be the specific nightly you are dealing with that is faulty. My advice would be to try another nightly version build from a different date. Do a full system wipe like you did before, Wiping Data, cache, and Dalvik. Then try installing a nightly from another date, until you get one to work for you properly. One is bound to work eventually. My brother had issues similar on his tablet, we ended up discovering that the specific build that day was to blame. Lastly as a tip for the future, a question like this is supposed to posted in the Q/A section under your specific device. Here's the link http://forum.xda-developers.com/galaxy-s-relay-4g/help. If you have further questions here's a link to the CM11 forum for your specific device. http://forum.xda-developers.com/showthread.php?t=2779975. Since they actually have the device, they can offer you better answers if my suggestion didn't work. It never hurts to shoot them a message. Best of luck, hopefully you can get CM 11 to work properly on your device.
ZekeAdebayo said:
It might be the specific nightly you are dealing with that is faulty. My advice would be to try another nightly version build from a different date. Do a full system wipe like you did before, Wiping Data, cache, and Dalvik. Then try installing a nightly from another date, until you get one to work for you properly. One is bound to work eventually. My brother had issues similar on his tablet, we ended up discovering that the specific build that day was to blame. Lastly as a tip for the future, a question like this is supposed to posted in the Q/A section under your specific device. Here's the link http://forum.xda-developers.com/galaxy-s-relay-4g/help. If you have further questions here's a link to the CM11 forum for your specific device. http://forum.xda-developers.com/showthread.php?t=2779975. Since they actually have the device, they can offer you better answers if my suggestion didn't work. It never hurts to shoot them a message. Best of luck, hopefully you can get CM 11 to work properly on your device.
Click to expand...
Click to collapse
thank you soo much i am trying up your advice...and i'll try also reposting on the right forum.

Categories

Resources