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.
Hi
I think my problem is in worst situation ever.
First, I was on CM11.
Then I heard VZW GS3 finally got 4.3 update, so I just went back to 4.1.2 official firmware.
Then my problem started.
I got that update, and then boot was successful.
However, all of my game data and pictures were gone.
So I tried to fix that because I thought that game data and pictures were still remain at some where.
Why?
cause the memory usage showed to me it was 4GB left.
it was same amount as when I was in 4.1.2 with all the data and pictures.
so, I tried to go back to 4.1.2, but I couldn't.
And I was using CWM latest version for GS3, but OTA disable it.
So every time that I trying to go to recovery mod, it shows "System software not authorized blahblahblah..."
Anyway, then I try to boot that system nomarly.
I thought it will going to boot, but it shows Samsung Galaxy S3 logo, then booted again.
then shows "System software not authorized by Verizon Wireless blahblahblah..."
Then I try to flesh CWM 6.0.1.2 recover by odin 3.07, but it keep shows Failed.
I look up to phone error message was
Secure check failed : recovery.
It didn't installed.
So, I fleshed into stock recovery, and it installed perfectly.
So I did factory reset, and wipe caches, but still same.
It is not booting.
keep showing
System software not authorized.........
is any solution that I can do with now?
(sorry for my bad English.)
Ok, so I think I may have finally killed one of my S2 Skyrockets.
I attempted to use the factory reset function from within Candy 5.1.1. However, on reboot the phone entered TWRP, or rather tried. Instead of booting into the recovery, it just kept restarting over and over again. I couldn't get it to boot into the OS or TWRP.
Thinking I had just soft-bricked it, I went into ODIN mode and uploaded a full restore image. Now I don't get stuck in a TWRP bootloop, I am stuck in a different bootloot. I see "Rethink Possible" go black, wait a few seconds, then it restarts again. I have pulled the battery out several times, attempted to boot into recovery (where I get the original TWRP bootloop) etc.
Is there any way to recover this device, or am I hosed?
[UPDATE]
Ok, this was one of the scarier things I've run into, but I recovered the phone. I used the sammobile version of the UCMC1 image (which blows away everything). This didn't reboot, it just hung. However, I was able to get into 3e (the stock recovery) and do a factory reset. THAT got me past the block. I'm now in the process of putting TWRP back on along with Candy.
Apparently you REALLY don't want to screw with the factory reset function...
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.
Where to start ?
Well, I tried to reflash the ROM i had to have a fresh start and when I installed FlashFire, the thing wouldnt go past checking for OTA; basically it crashed at launch. I realized my best bet was to factory reset the phone so I could reinstall the apps, big mistake. I factory reset it thought the OS settings and it didnt go through to it, tried several times and nothing. I ended up entering recovery and wiping it through there and then reboot the phone. Phone reboot, and whole completing the Setup Wizard, it crashes while finalizing it, every , time. I can't get pass this point, same happens during the safe mode. I might have deleted the SetupWizard while playing Titanium Backup when I first flashed the ROM.
The other dilemma is I cannot get any PC to recognize the damn phone, I'm not sure if it is the charging port which is broken, my pc, or the drivers I'm using. At this point I'm open to try something new. Any ideas ?
Thanks.