Phone was originally bone stock, I then rooted & installed TWRP recovery, booted into TWRP and did the Backup option and saved it to SD Card, I then flashed CM 12.1 and used it for a little over a month, trying the various Nightly updates.
I decided to go back to the stock rom I had backed up previously, It restores successfully but when I boot the phone everything is crashing once it hits the home screen, "Unfortunately xxxx has stopped" is seen over and over, I can't load anything, even the settings menu crashes.
I then tried rebooting into TWRP and did Factory reset but when I do this It wont ever get past the Samsung logo on reboot.
Not sure what went wrong with the backup or if Im missing a step, I also tried enabling the verify MD5 check option for the Backup and it says everything is fine.
For now I'm back in CM 12.1, Any ideas appreciated!
Hello and thank you for using XDA Assist.
Your device has a dedicated forum and within that forum you have a Q&A section specifically for your device.
Please try searching within this forum http://forum.xda-developers.com/galaxy-s3-sprint/help and I am sure others have previously experienced the same thing.
You will find the device experts for your Sprint S3 there.
Within that forum you could also find a stock rooted Rom and download and flash that. You do need to know exactly what boot loader your device is running.
Good luck
Ragnar
Related
hi, i've been experimenting with a samsung gt-i5800 which i was given for free if i could unbrick it (it only needed factory restored) i've successfully rooted it and decided to have a go at installing a custom rom, because i was fed up of having to use a static ip address to connect to wifi.
i used odin to put cyanogenmod 7 on it. it worked, and i'm happy with the mod, but it's showing that there's 0kb of internal storage, and every time it's rebooted it behaves as if it's been factory reset (settings, contacts apps etc are all gone) i've read a few topics about these problems, apparently the solution is to wipe it and reinstall the custom rom.
what i'm not entirely clear about is what is meant by wiping it. i'm assuming it doesn't just mean using the recovery menu to factory restore again? what exactly do i need to delete and how do i do it safely? thanks!
Hi,
I suggest you to go here for find some good help => Galaxy 3 Q&A, Help & Troubleshooting
and at the same time, you can go here and read to find your problem with CM 7 version => Galaxy 3 Android Development
Good luck
thanks, i figured out how to use CWM recovery to properly clear it out, then reinstalled from a zip with CWM, it's now working properly.
I have a Samsung Galaxy S3 (I-747) Using Rom Manager for first time I backed up and immediately checked how the restore would work. Lots of stop errors after restore so went back to boot menu for recovery and that worked. First I noticed sim card didn't work and no IMEI number ATT told me. There is no baseband either or any kind of IMEI backed up. Found a factory restore from one of these XDA forums. Process worked but no baseband and cant use sim still. Not bricked yet but want to learn more because i want custom rom knowledge.
Hi,
Here is a similar thread you can read through and hopefully it helps... You could post there also,
http://forum.xda-developers.com/galaxy-s3-att/help/imei-null-null-baseband-unknown-t2951225
Good luck!
I was using latest cyanogenmod versions on my Moto g safely for the past 2 months or so. Today after trying to restart my device it got stuck on the boot animation. I am fairly confident that I can simply reinstall the OS to fix this issue however as far as I know, only media files will stay intact whereas apps and their data will vanish. If I understood correctly, the backup option through the recovery (CWM in my case) will backup entire ROM, so I tried using one available through "adb backup" command when phone is plugged in my PC. However it asks me to unlock and confirm it on my phone so I guess the OS needs to be actually running for this. Is there another way?
XDA Visitor said:
I was using latest cyanogenmod versions on my Moto g safely for the past 2 months or so. Today after trying to restart my device it got stuck on the boot animation. I am fairly confident that I can simply reinstall the OS to fix this issue however as far as I know, only media files will stay intact whereas apps and their data will vanish. If I understood correctly, the backup option through the recovery (CWM in my case) will backup entire ROM, so I tried using one available through "adb backup" command when phone is plugged in my PC. However it asks me to unlock and confirm it on my phone so I guess the OS needs to be actually running for this. Is there another way?
Click to expand...
Click to collapse
Hello, and welcome to XDA! You could try a clean install again, and you might find that the phone boots, or you could try flashing another rom. One option would be to check the cm thread to see if others have had this issue and if it's now been fixed, or to ask for help. Did you download your rom from an XDA thread? If so, ask in that thread. If not, try this rom and see if it solves the problem: http://forum.xda-developers.com/moto-g/orig-development/rom-official-cyanogenmod-12-nightly-t2994749. You would need to register in order to post.
Good luck!
I have a Note-4 T-Mobile variant(N910T), I have been using Xenon HD and then CM 12.1. After a while when I wanted to go back to stock, and when I flashed stock rom back, the phone was really laggy at first and during setup, there was a popup which said that Factory mode is enabled and I have to switch back to User mode before using it and after a few seconds it disappeared, this happens every time i reboot while in Stock Rom. Somehow after a few minutes, I get the WiFi on again but the keyboard gets stuck after a few presses and phone gets real laggy. After the setup I googled the problem and found out something regarding the EFS Folder, so I rooted it once again and installed ES File explorer and went into EFS and found that it was empty. I tried placing a phone call and it went through and I was also able to use LTE, but when I went to about phone to see IMEI, i saw that the IMEI was wrong, I even tried to setup fingerprints, but it kept saying me to reboot as something was wrong with the fingerprint sensor. Now the weird thing here is that when I am in a Non-touchwiz based Custom Rom, I do not find any lag and the IMEI is correct. I have tried these things already:
Going to EFS and switching Factory mode on, but as i told EFS folder is empty.
Backing up EFS from the custom and restoring when I'm in Stock.
If anyone knows how to fix this, could you please help me?
Thanks!
Hello,
Welcome to XDA.
Try posting your question in the forum linked below.
http://forum.xda-developers.com/note-4/help
The experts there may be able to help.
My first post here is exactly as the title implies. I rooted my lg g3 us990 with kingroot(after attempting others) and have been using it for a while, working perfectly. I then got the idea to start learning about custom roms and attempting to install one.
So I used twrp and set up my recovery, I then backed up my current state. I found a rom that I assumed "should" work, CM12.1 and added it to my qeue on twrp. Starting out good.
I wiped my all options except internal storage and sd card and proceeded to flash CM12. All seemed well, it rebooted, with boot error message 1003 in the top left, on the LG boot page. Then, the cyanogenmod face came up, slightly uneven, and the boot went on for an hour. Not so good.
No biggie, I still had a backup to go back too right? Wrong. I went through the same steps to wipe memory, then restore my backup. LG screen, same error message, boot loop, CRAP.
Any help would be greatly appreciated to get my phone working again. I understand the rom not working, but why wouldnt my backup work?
Note, I am able to get into both twrp recovery and download mode.
Also, my twrp is displaying the wrong time, is that normal?
paul8m3 said:
My first post here is exactly as the title implies. I rooted my lg g3 us990 with kingroot(after attempting others) and have been using it for a while, working perfectly. I then got the idea to start learning about custom roms and attempting to install one.
So I used twrp and set up my recovery, I then backed up my current state. I found a rom that I assumed "should" work, CM12.1 and added it to my qeue on twrp. Starting out good.
I wiped my all options except internal storage and sd card and proceeded to flash CM12. All seemed well, it rebooted, with boot error message 1003 in the top left, on the LG boot page. Then, the cyanogenmod face came up, slightly uneven, and the boot went on for an hour. Not so good.
No biggie, I still had a backup to go back too right? Wrong. I went through the same steps to wipe memory, then restore my backup. LG screen, same error message, boot loop, CRAP.
Any help would be greatly appreciated to get my phone working again. I understand the rom not working, but why wouldnt my backup work?
Click to expand...
Click to collapse
Greetings and welcome to assist. I think your issue is related to a locked bootloader so unlocking it should fix it, I found this thread that might help you
https://forum.xda-developers.com/tmobile-g4/help/totally-screwed-secure-boot-1003-error-t3326495
Good Luck
Sawdoctor
sawdoctor said:
Greetings and welcome to assist. I think your issue is related to a locked bootloader so unlocking it should fix it, I found this thread that might help you
https://forum.xda-developers.com/tmobile-g4/help/totally-screwed-secure-boot-1003-error-t3326495
Good Luck
Sawdoctor
Click to expand...
Click to collapse
Thank you for the reply. I was fortunate enough to have a generous person give me a bunch of compatible roms and help me through my 'functionality' problem. Next is working on getting rid of that error message.