so this is basically what happened. i rooted my samsung fascinate, then tried to do some voodoo5 thing, stopped halfway, tried several other lag fixes, failed, factory reset my phone about 20 times, and tried to reset my phone to stock with odin and restore files, but now, all it will do is tell me all these applications stopped working and i have to force stop them, i cannot get past teh unlocking screen, because the main screen, like after you fit the puzzle piece, is just black, i can see the status bar, but nothign works, and the force stop message keeps popping up
run a stock ruu.
k good news, i did the stock restore wiht odin, and i restored from a backup i had, now its working fine, but what do i have to do if i wanna flash a new version of voodoo kernel? do i have to disable the previous kernel, or do i hvae to erase the whole kernel?
Related
Hi! I was trying to use Odin3 to go back to stock on my Captivate. I was doing this because I wanted to flash Serendipity ROM. It said I had to master clear which I clicked and it sat there for about 20minutes saying "Master Clear Started...". I got worried and removed my captivate and tried using Odin3 with just start. It also got stuck on "DO NOT TURN OFF TARGET". I have tried both ways a million times and also on separate machines but it isn't working.
In the beginning I tried to flash serendipity over cm7 which did not work. I wiped cache partition and factory reseted it. It also did not work. Does this have any part in the problems I am having right now? How can I fix this?
Good evening everyone.
Going to try to be as concise here as possible.
Rooted my phone as per VINCOM's awesome guide here, everything went well.
Phone was functioning normally.
I proceeded to load superuser/ updated binaries etc.
Downloaded rom toolkit/titanium back up and proceeded to freeze certain apps that were considered bloatware.
after about an hour or so, I was on my browser, went to the home screen, but the browser stayed open, yet buzzed as if the command was heard.
did a battery pull, and since that it has stopped at the S logo opening screen.
I cannot get it to go into recovery at this point either. My phone has periodically shown the sticky power button issue with resets and every 2 second vibrations, but it had not done this for some time.
Upon trying to go into recovery (both volume keys held plus power, I seems to start doing the vibrating every two seconds.
At this point I am lost on what to do.
Any advice would be appreciated.
Me[kk]A said:
Good evening everyone.
Going to try to be as concise here as possible.
Rooted my phone as per VINCOM's awesome guide here, everything went well.
Phone was functioning normally.
I proceeded to load superuser/ updated binaries etc.
Downloaded rom toolkit/titanium back up and proceeded to freeze certain apps that were considered bloatware.
after about an hour or so, I was on my browser, went to the home screen, but the browser stayed open, yet buzzed as if the command was heard.
did a battery pull, and since that it has stopped at the S logo opening screen.
I cannot get it to go into recovery at this point either. My phone has periodically shown the sticky power button issue with resets and every 2 second vibrations, but it had not done this for some time.
Upon trying to go into recovery (both volume keys held plus power, I seems to start doing the vibrating every two seconds.
At this point I am lost on what to do.
Any advice would be appreciated.
Click to expand...
Click to collapse
Just an update, flashed stock firmware for ICS 4.04 successfully, managed to get the phone once into recovery, did a factory reset cache wipe twice... everything remains the same. FML
Me[kk]A said:
Just an update, flashed stock firmware for ICS 4.04 successfully, managed to get the phone once into recovery, did a factory reset cache wipe twice... everything remains the same. FML
Click to expand...
Click to collapse
managed to get my phone going.
tried flashing odin again with the stock 4.04 provided by VINCOM.
Things seem back to normal.
Still boggled by what bricked the phone.
Thoughts?
Yesterday I went through the process of rooting, unlocking and flashing my GS3. I used CWM to make a backup of my stock rom (which I then saved a copy on my computer) and then flashed to Paranoid Android, which I loved. I used Titanium Backup to load my contacts up, and got prompted with a reboot. Once I did, I kept getting android.process.acore errors, and eventually narrowed it down to Titanium and my contacts (wasn't hard, only thing installed). I decided to flash to stock and backup my contacts to Google, but everytime I enter CWM recovery to restore, it reboots before I have a chance to. Both entering via Rom Manager and into recovery mode. I have used a downloaded stock rom to try and flash back to stock in Odin, and continually get error messages. I would just stick with PA, but every 5 seconds brings up a android.process.acore error because it is still trying to DL my contacts. Anyone have any ideas/hints/tips/etc that I should try?
Nevermind, finally found a stock rom that worked for me.
Update: It turns out it was not a software problem, and had nothing to do with my root, CWM, or PA. After flashing to stock, the problem persisted, even after a full reset and update to 4.1.2. Took the phone to Best Buy, since that is where I have my insurance through. They told me that the power button had gone faulty, which makes sense cause pressing it will prompt power off options, and slightly touching it will lock the phone. According to the guys there, it's a problem they've seen on a few S3's lately. So, I have a refurb on the way via Geek Squad. I jokingly asked for a S4 or One as a refurb replacement, but sadly don't think that'll happen. Anyway, figured i'd update this to let everyone know just in case you encounter the same symptoms.
Cant flash Cyanogen, recovery faulty & weird crashes in stock on refurbished Nexus 5
Hey guys,
so I recently got a "refurbished" replacement for my Nexus 5 and I decided since im starting out fresh (can't access the data on the old one), I'll try out Cyanogen mod.
I can assure you that I followed all the instructions exactly. At some point I checked every download for his checksums and all were ok.
Each time I started the process by flashing a factory image (flash-all.bat), to have a clean start.
I also tried to wipe cache/dalvik cache/data afterwards, but not always. This didn't change the behavior.
These things happened to me while trying to accomplish the task, and working around the issues as they arised:
Flashing TWRP: High (3 of 4) chance that TWRP wouldn't even start up, the phone would hang and just flash the TWRP background picture on screen.
When I did get through to TWRP, applying the Cyanogenmod .zip got stuck at "patching system image unconditionally". Let it go on for hours.
I figured that TWRP was broken and tried Clockworkmod instead. CWM at least always started after flashing it. But same as TWRP, it failed in installing the Cyanogenmod .zip. I tried putting it onto the phone by going into the stock android and then through adb push command, but also through sideloading directly into CWM.
What I noticed when going into the stock ROM was, that a lot of Google processes were failing during the initial setup (where it wants to know ur WiFi, date, Google acc, etc), like Maps, Settings, Play Services, and some others. Sometimes they were failing so hard it was impossible to type in the WiFi passphrase because the notifications of different "xxx has stopped working" were coming to fast, sometimes not a single one was failing. I could not find any pattern to this. When they were failing so hard I couldn't get through the initial setup I would just flash the stock again, until I got only some of them failing, or none at all.
Back to CWM and installing the Cyanogenmod .zip:
It failed with different errors. I got status 0, status 1, I think I once got status 6 or 7, but half of the time it hanged exactly where TWRP was hanging. The errors were random. After getting status X, I would sideload it right again, to get other status Y, sideload again, to get the hang. Could not recognize a pattern.
During this I switched USB ports, and cables, and even tried using my laptop instead of the desktop. One of the cables was faulty, it didn't even allow a connection, but any other setup showed the same behaviour.
Is there anything else I can/should try? Is it my fault, or is the phone bad?
Assuming the phone is bad, I suppose I still could get a stock running without the crashes, so it would _feel_ like the phone is alright (which is what Google probably did before sending it out again as "refurbished"), but I think there would be errors in the future, also I don't want a phone with such an uncertainty. Would they swap it? Also, it is a LG-D820, which means it might have issues with european LTE, haven't gotten to trying that out since I don't use LTE right now, nor will I in the near future.
Best regards,
napster
napstr said:
Hey guys,
so I recently got a "refurbished" replacement for my Nexus 5 and I decided since im starting out fresh (can't access the data on the old one), I'll try out Cyanogen mod.
I can assure you that I followed all the instructions exactly. At some point I checked every download for his checksums and all were ok.
Each time I started the process by flashing a factory image (flash-all.bat), to have a clean start.
I also tried to wipe cache/dalvik cache/data afterwards, but not always. This didn't change the behavior.
These things happened to me while trying to accomplish the task, and working around the issues as they arised:
Flashing TWRP: High (3 of 4) chance that TWRP wouldn't even start up, the phone would hang and just flash the TWRP background picture on screen.
When I did get through to TWRP, applying the Cyanogenmod .zip got stuck at "patching system image unconditionally". Let it go on for hours.
I figured that TWRP was broken and tried Clockworkmod instead. CWM at least always started after flashing it. But same as TWRP, it failed in installing the Cyanogenmod .zip. I tried putting it onto the phone by going into the stock android and then through adb push command, but also through sideloading directly into CWM.
What I noticed when going into the stock ROM was, that a lot of Google processes were failing during the initial setup (where it wants to know ur WiFi, date, Google acc, etc), like Maps, Settings, Play Services, and some others. Sometimes they were failing so hard it was impossible to type in the WiFi passphrase because the notifications of different "xxx has stopped working" were coming to fast, sometimes not a single one was failing. I could not find any pattern to this. When they were failing so hard I couldn't get through the initial setup I would just flash the stock again, until I got only some of them failing, or none at all.
Back to CWM and installing the Cyanogenmod .zip:
It failed with different errors. I got status 0, status 1, I think I once got status 6 or 7, but half of the time it hanged exactly where TWRP was hanging. The errors were random. After getting status X, I would sideload it right again, to get other status Y, sideload again, to get the hang. Could not recognize a pattern.
During this I switched USB ports, and cables, and even tried using my laptop instead of the desktop. One of the cables was faulty, it didn't even allow a connection, but any other setup showed the same behaviour.
Is there anything else I can/should try? Is it my fault, or is the phone bad?
Assuming the phone is bad, I suppose I still could get a stock running without the crashes, so it would _feel_ like the phone is alright (which is what Google probably did before sending it out again as "refurbished"), but I think there would be errors in the future, also I don't want a phone with such an uncertainty. Would they swap it? Also, it is a LG-D820, which means it might have issues with european LTE, haven't gotten to trying that out since I don't use LTE right now, nor will I in the near future.
Best regards,
napster
Click to expand...
Click to collapse
Hi.
According to what you say, it seems an hardware problem of you phone. Don't know if it may help but you can try installing an older factory image (for example kitkat) and seeing if the "force closing" problems are still there. If your phone is ok it should be able to run a factory image at least.
Download the nexus root toolkit, create a nandroid backup, then when either in CWM or TWRP wipe everything off the phone then try to flash a ASOP rom like Cataclysm if nothing else works then I don't know how to help sorry-.-
So I tried to get the stock ROM up and running again, and it seems even that is not possible. Several processes keep crashing during various tasks, even when idling. After having a short chat with Google Support about the issues I got an RMA offered, so things are cool. I locked the phone again, set the tamper-bit to false and wiped everything.
Hi, I have tried to reset my phone to a factory settings several times, but it was never switched back to the initial settings of a brand new phone. Prior to trying to do this reset, I have tried to root the phone by installing TWRP (I was never successful according to a few root checker apps) and then was stuck with being unable to remove TWRP from the phone. I managed to do that a few days ago with the help of Odin and a stock firmware, however I didn't get the initial settings of a brand new phone. When I do a factory reset, I see a blue screen with an android icon and a message ''Erasing data'' but when I launch the phone I always see a yellow background that I setup in December. I don't see any custom installed apps, only the default ones, but since I want to sell the phone I would like to be able to reset the phone back to the initial settings without a yellow background showing on a Home and Lock screens. Any help?
luxserpie said:
Hi, I have tried to reset my phone to a factory settings several times, but it was never switched back to the initial settings of a brand new phone. Prior to trying to do this reset, I have tried to root the phone by installing TWRP (I was never successful according to a few root checker apps) and then was stuck with being unable to remove TWRP from the phone. I managed to do that a few days ago with the help of Odin and a stock firmware, however I didn't get the initial settings of a brand new phone. When I do a factory reset, I see a blue screen with an android icon and a message ''Erasing data'' but when I launch the phone I always see a yellow background that I setup in December. I don't see any custom installed apps, only the default ones, but since I want to sell the phone I would like to be able to reset the phone back to the initial settings without a yellow background showing on a Home and Lock screens. Any help?
Click to expand...
Click to collapse
this may sound dumb, but ive had this exact same issue on many previous phones, and it was resolved by doing a factory reset from within the GUI a few times, yes literally do it at least twice, and then doing a factory reset in the stock recovery literally 3 times, and for the overkill, flash the factory tarball via odin for giggles. If that doesnt do it, not sure what else will
youdoofus said:
this may sound dumb, but ive had this exact same issue on many previous phones, and it was resolved by doing a factory reset from within the GUI a few times, yes literally do it at least twice, and then doing a factory reset in the stock recovery literally 3 times, and for the overkill, flash the factory tarball via odin for giggles. If that doesnt do it, not sure what else will
Click to expand...
Click to collapse
I'll do all that one more time to remove the gold screen, leave the phone aside and purchase a new phone for use. I'm sure it will work since nothing had changed since the last year when I knew the phone last time by hear. Thank God, phones don't talk. I'm sure it will work because it worked with all other phones I had since I know them so well. I wish I thought of it earlier. How smart!