Hello Everybody,
I'll make this short and sweet. I've tried to flash cyanogen mod using the installer, it says it was successful but it wasn't. All it did was reset my touchwhiz (Using Samsung Galaxy S3 i747M Rogers version) back to it's original state. I also think root was removed. I tried to use my CWM recovery file, but it didn't work. It actually messed with my radios and I had no service. My screen was also spammed with "gapps has stopped working" messsages. I've fixed that part of the issue by flashing the stock touchwhiz. My apps/pictures are still there, but app data has been deleted. CWM did not restore properly. Is this due to root being removed? If I re-root my phone, will I be able to get it back to the state is was in before trying to flash cyanogen?
Related
Hi guys,
I have the international version of the Galaxy S3 and I have a little problem. The first thing I did when I've got it was root it with Odin and everything went fine but now I see the rooting doesn't work as it should. Buisybox says it needs to be rooted and SuperSu is configured to allow everything. Also, when I launch CWM Manager (v3.55) a popup says that it should be used with CF-Root v5.0 or newer.
My question is, how should I update everything? When I format/upgrade my old Galaxy S2 to give it to my dad, I simply flashed CF-Root to the CW10 and it broke the phone's boot. Luckily I had backed up everything using CF-Root the day before. Should I uninstall it first? How? And how can I do it without loosing the backup I'll make to my S3 before I try anything?
What I mean is... how can I update everything in a "clean" way?
Thanks in advance!
Hi all. Tried my first root + custom rom installation and i messed up the device..
i had the newest KIES firmware update (phone XXBMA5) and (XXBMA6) and i rooted the device with odin (3.07). That went OK.
Then i installed the CWM recovery with odin and that was OK too.
Then i downloaded the latest Omega Rom (i missread that it supports N8020) and followed the installation instructions to the point where it started installing Omega V2.0 from SDCARD and then it asked me to select device from a list that included only (N8000,N8010,N8013)..
So the situation now is that i have working odin, working CWM and backup of the EFS (img+tar) but no working recovery. i live in Finland and the device is Sonera locked i think, so the stock roms (international) do not work i guess.
KIES has a backup of my Note but i can't even get to a point where KIES discovers the device.
So basically i think i need a working ROM for my model (Note 10.1 4G N8020), or can i recover the original samsung software somehow ?
Any advices ?
Removed
Just a thought, but can't you reflash CWM or the stock recovery?
If you didn't install the rom why do you need to re-install anything. Just powering down and powering up should have left you as was....
Alajarvi84 said:
working CWM .......... but no working recovery.
Click to expand...
Click to collapse
Maybe i'm missing something but isn't CWM your custom recovery?
It doesn't sound like you've actually installed any rom yet.The Omega installer doesn't actually install anything until a few steps after the one you mentioned about the model type.
I'm with ultramag69 on this one. You should still be on a stock rom unless you already wiped your original rom.
Hi again. Problem solved, just had to do emergency thing from KIES. Like i said this was the first time trying root + custom ro install and to be honest it went to ****. Somehow i managed to delete the stock firmware so that is why the recovery gave me (no files). I did make some backup but when tried to restore it said MD5 mismatch or something. At first the KIES emergency recovery could not find the device, but after i switched from CWMcto stock recovery it worked.
So what did i learn from all this ? Nothing, because i am getting too old (tired+lazy ) to do proper investigation. So one could say my strategy is to bang my head to the wall as long as it takes to go trough. Even if i could just go around it
So basically i am now at the point where i started, with stock 4.1.2 rooted. Used the triangle away to wipe the (6) custom installs or something away, but it still says custom in the settings> information. Does this mean that OTA won't work ? Any way around it ? Because i would like to check now and then that is my version of android the newest one..
Could someone recommend a custom ROM for my Note 10.1 4G (LTE) N8020 4.1.2 because the only one i was able to find was the CyanogenMod (or something) and it basically makes the S-Pen (almost) useless. What i would like is the Omega ROM, but like stated before the installation only supported N8000, N8010 & N8013...
Added screenshot from info.
Thanks anyway
What is truly amazing is that i did not brick the device tough..
switch from cwm to stock
Alajarvi84 said:
Hi again. Problem solved, just had to do emergency thing from KIES. Like i said this was the first time trying root + custom ro install and to be honest it went to ****. Somehow i managed to delete the stock firmware so that is why the recovery gave me (no files). I did make some backup but when tried to restore it said MD5 mismatch or something. At first the KIES emergency recovery could not find the device, but after i switched from CWMcto stock recovery it worked.
So what did i learn from all this ? Nothing, because i am getting too old (tired+lazy ) to do proper investigation. So one could say my strategy is to bang my head to the wall as long as it takes to go trough. Even if i could just go around it
So basically i am now at the point where i started, with stock 4.1.2 rooted. Used the triangle away to wipe the (6) custom installs or something away, but it still says custom in the settings> information. Does this mean that OTA won't work ? Any way around it ? Because i would like to check now and then that is my version of android the newest one..
Could someone recommend a custom ROM for my Note 10.1 4G (LTE) N8020 4.1.2 because the only one i was able to find was the CyanogenMod (or something) and it basically makes the S-Pen (almost) useless. What i would like is the Omega ROM, but like stated before the installation only supported N8000, N8010 & N8013...
Added screenshot from info.
Thanks anyway
Click to expand...
Click to collapse
How did you switch from CWM to stock? I have having a problem syncing with kies also using omega rom on n8013.
jjndimp said:
How did you switch from CWM to stock? I have having a problem syncing with kies also using omega rom on n8013.
Click to expand...
Click to collapse
I was not easy, i just tried the download mode over and over again with KIES open in windows and somehow it finally did find my device and offered a emergency restore. That is it, and the device was restored to default "original state".
OMG.... one would think after nearly having bricked your device you would either A) stop messing around with it or, B) read and learn more about what you're wanting to achieve and THEN maybe trying something with the ABSOLUTE certainty that a backup to restore is available to you in case of any mishap!
Moral of story :
Don't do anything until you are absolutely sure you have read EVERYTHING about what you are going to do.
For others wanting to mess with their devices, take heed! You may not be as lucky as OP (or troller) whichever is applicable.
There comes a certain point, that when crossed one does not care what happens to the device at hand. After fighting with my n8020 for several days in a row i couldn't care less, and like said before i dont have the level of enhusiasm like i had when i was younger. Of course i know now what went wrong.. But seriously, these are just overpriced toys, so it's not a matter of life and death.
Sent from my GT-N8020 using XDA Premium HD app
My wife's rooted Samsung Galaxy S3 (vzw) has been acting strange lately. It has been asking to update and then locking into a screen that says "System software not authorized by Verizon..." I can successfully reset the phone, as well as get into Odin, but I cannot get into recovery mode to flash a new rom. (The first and only rom I flashed on her phone was stock Touchwiz about 8 months ago.)
I'm kind of a noob at this stuff, so I'm not sure what to do. First, I'm not sure why this is happening in the first place. My research shows that it can happen when you don't unlock the phone properly, but I'm virtually certain I did. In any event, what next? I have read that I should Odin back to stock. Is it appropriate for me to attempt to Odin back to a rooted stock rom? Is that even possible? For example, can I Odin back to this rom (http://forum.xda-developers.com/showthread.php?t=2332840)?
eyc said:
My wife's rooted Samsung Galaxy S3 (vzw) has been acting strange lately. It has been asking to update and then locking into a screen that says "System software not authorized by Verizon..." I can successfully reset the phone, as well as get into Odin, but I cannot get into recovery mode to flash a new rom. (The first and only rom I flashed on her phone was stock Touchwiz about 8 months ago.)
I'm kind of a noob at this stuff, so I'm not sure what to do. First, I'm not sure why this is happening in the first place. My research shows that it can happen when you don't unlock the phone properly, but I'm virtually certain I did. In any event, what next? I have read that I should Odin back to stock. Is it appropriate for me to attempt to Odin back to a rooted stock rom? Is that even possible? For example, can I Odin back to this rom (http://forum.xda-developers.com/showthread.php?t=2332840)?
Click to expand...
Click to collapse
the files that you use to odin with are a different extension (.tar) than what you flash with (.rar)...so you can only use cwm/twrp to use that rooted image. I recommend using odin to get back to stock, then using the root one click method that was recently stickied...that will get you up in running and able to use roms quickly
Yes its possible but first try to install a custom recovery. Download goomanager and then install open recovery script from the menu options. Then you should be able to boot into twrp and flash a new rom
Sent from my XT912 using xda app-developers app
eyc said:
My wife's rooted Samsung Galaxy S3 (vzw) has been acting strange lately. It has been asking to update and then locking into a screen that says "System software not authorized by Verizon..." I can successfully reset the phone, as well as get into Odin, but I cannot get into recovery mode to flash a new rom. (The first and only rom I flashed on her phone was stock Touchwiz about 8 months ago.)
I'm kind of a noob at this stuff, so I'm not sure what to do. First, I'm not sure why this is happening in the first place. My research shows that it can happen when you don't unlock the phone properly, but I'm virtually certain I did. In any event, what next? I have read that I should Odin back to stock. Is it appropriate for me to attempt to Odin back to a rooted stock rom? Is that even possible? For example, can I Odin back to this rom (http://forum.xda-developers.com/showthread.php?t=2332840)?
Click to expand...
Click to collapse
If you are Verizon Stock rooted and have SU and busybox installed without disabling updates, that will occur whenever Verizon rolls out an OTA. if you want the update, ODIN back to stock and take the updates before rooting. If you don;t want updates then find the thread on disable Verizon OTA and that will stop the update request.
Hey Everybody
I'm new to the whole rooting process, which I did fine on Saturday the 4th of October 2014. Today (October 8th 2014) I tried to install Cyanogen using the installer, it said it worked, but when my phone rebooted it was in the original version of touchwhiz that came with my Galaxy S3 SGH-I747 Rogers version. I wanted to get my files back, so I went into CWM and tried to recover, which didn't work. I tried again and again and it finally loaded my apps, but I had no service and I was spammed with "failure to load .gapps.google" or something like that. I went into CWM and wiped cache, tried again, same issue. I then wiped everything, went back into it and it still was NOT working. What do I do? I have no service at all! I've tried pulling the SIM and putting it back, but no success. Please HELP!
EDIT: I flashed stock ROM using ODIN, which worked. I would still like to know why CWM didn't work though, and if it is still possible to try to get it to work
lasttimelord12 said:
Hey Everybody
I'm new to the whole rooting process, which I did fine on Saturday the 4th of October 2014. Today (October 8th 2014) I tried to install Cyanogen using the installer, it said it worked, but when my phone rebooted it was in the original version of touchwhiz that came with my Galaxy S3 SGH-I747 Rogers version. I wanted to get my files back, so I went into CWM and tried to recover, which didn't work. I tried again and again and it finally loaded my apps, but I had no service and I was spammed with "failure to load .gapps.google" or something like that. I went into CWM and wiped cache, tried again, same issue. I then wiped everything, went back into it and it still was NOT working. What do I do? I have no service at all! I've tried pulling the SIM and putting it back, but no success. Please HELP!
Click to expand...
Click to collapse
Anybody?
I'm a beginner myself, and i do not know much about installing custom roms on samsung phones, but maybe you did not flash a compatible custom kernel to support the custom rom? it seems like you did not flash gapps either, but that should not stop you from getting network service. my last guess would be that you need to also install a baseband perhaps. all this information should be there in the galaxy s3 section of the forums.
ishaang said:
did not flash a compatible custom kernel to support the custom rom? it seems like you did not flash gapps either, but that should not stop you from getting network service. .
Click to expand...
Click to collapse
Hey there, first off, thank you for replying.
I didn't manually use odin or other flashing software to flash the ROM. Unlike the rooting method (which went smoothly) I used the cyanogen mod installer. The installer itself said that cyanogen was installed successfully, but it was not. After it said this, my screen (on the phone) turned off, and I was brought to a fresh install of touchwhiz. I've actually fixed the networking issue by flashing touchwhiz stock,but that still doesn't explain why my CWM backup wasn't working.
I see...I haven't used the cyanogen mod installer myself so cannot say...
What I suggest is that, if you're up for trying again, to manually flash a rom - either Cyanogenmod or any other. There seem to be a lot of good roms available for your phone, and whichever rom you choose will come with instructions for how to install. The usual method will involve the following steps as far as I know:
- Root
- Unlock Bootloader
- Flash Custom Kernel with recovery
- Flash ROM
- Flash GAPPS
These steps are not difficult at all as long as you follow the instructions for your specific phone. I have a Sony Xperia SL and thats how I installed a custom rom on it many times. Sorry I could not help much not knowing Samsung procedures but good luck!
lasttimelord12 said:
Hey Everybody
I'm new to the whole rooting process, which I did fine on Saturday the 4th of October 2014. Today (October 8th 2014) I tried to install Cyanogen using the installer, it said it worked, but when my phone rebooted it was in the original version of touchwhiz that came with my Galaxy S3 SGH-I747 Rogers version. I wanted to get my files back, so I went into CWM and tried to recover, which didn't work. I tried again and again and it finally loaded my apps, but I had no service and I was spammed with "failure to load .gapps.google" or something like that. I went into CWM and wiped cache, tried again, same issue. I then wiped everything, went back into it and it still was NOT working. What do I do? I have no service at all! I've tried pulling the SIM and putting it back, but no success. Please HELP!
EDIT: I flashed stock ROM using ODIN, which worked. I would still like to know why CWM didn't work though, and if it is still possible to try to get it to work
Click to expand...
Click to collapse
OK,
Download stock ROM for your device from Samsung-updates.com according to device model and region.
Then flash it with Odin.
Good luck
Here's a basic rundown of what happened. I completely rooted my Galaxy S III i535 on 4.4.2, and i installed SafeStrap (A Version of TWRP) since the Verizon S3 has a locked bootloader.
So here's what I tried to do. Using SafeStrap, I backed up my stock rom. And i selected another ROM slot. Using this, i tried experimenting by installing a ROM for another Carrier (They say not to do this, but i have in the past with success, so i thought it mightve worked)
(KEEP IN MIND, THE STOCK OS WAS STILL INSTALLED AND I EVEN HAD A BACKUP)
So, it didnt work and stopped halfway. I rebooted the phone, and Hard bricked.
Doesnt boot up, does not turn on, will not boot recovery or download, or any sign of some boot at all.
And, i get the qhsusb_dload sign on my pc.
Can anyone point me in the right direction, or at least tell me the cause of this problem? Thanks.
CrimsonKatsuro said:
Here's a basic rundown of what happened. I completely rooted my Galaxy S III i535 on 4.4.2, and i installed SafeStrap (A Version of TWRP) since the Verizon S3 has a locked bootloader.
So here's what I tried to do. Using SafeStrap, I backed up my stock rom. And i selected another ROM slot. Using this, i tried experimenting by installing a ROM for another Carrier (They say not to do this, but i have in the past with success, so i thought it mightve worked)
(KEEP IN MIND, THE STOCK OS WAS STILL INSTALLED AND I EVEN HAD A BACKUP)
So, it didnt work and stopped halfway. I rebooted the phone, and Hard bricked.
Doesnt boot up, does not turn on, will not boot recovery or download, or any sign of some boot at all.
And, i get the qhsusb_dload sign on my pc.
Can anyone point me in the right direction, or at least tell me the cause of this problem? Thanks.
Click to expand...
Click to collapse
The solution may be a debrick image. They are designed to boot the phone from an external sdcard and from there reinstall the stock rom/firmware. I haven't searched yet, but check the general and development threads, possibly the stickied summary thread.
Check this thread