Database Info

[Q] Multiple GSIII's fail to install OTA

Hi, my family has multiple Verizon Galaxy SIIIs that were supposed to receive OTA updates about a week ago, but for whatever reason, as I cannot pinpoint the exact cause, none of them will install the update.
Each phone has:
Been rooted, by means of flashing a custom stock ROM through Odin
Had numerous stock applications frozen with Titanium, but we've tried unfreezing all of them prior to trying again with no effect
So I'm assuming it's that the phone's rooted. Is there any way to apply the update manually without unlocking the bootloader (ie. using the stock recovery or Odin to flash the update) and still have the possibility of keeping root?

Yes, the entire updated rom's are available in the development section. The latest being the vrlhd.
Sent from my VZW GS3 running Synergy/Trinity/Dark Horse Rises

AvataroftheSun said:
Hi, my family has multiple Verizon Galaxy SIIIs that were supposed to receive OTA updates about a week ago, but for whatever reason, as I cannot pinpoint the exact cause, none of them will install the update.
Each phone has:
Been rooted, by means of flashing a custom stock ROM through Odin
Had numerous stock applications frozen with Titanium, but we've tried unfreezing all of them prior to trying again with no effect
So I'm assuming it's that the phone's rooted. Is there any way to apply the update manually without unlocking the bootloader (ie. using the stock recovery or Odin to flash the update) and still have the possibility of keeping root?
Click to expand...
Click to collapse
I had to Odin back to stock and go get a new SIM card from Verizon... Got the OTA instantly after the new sim was put in... It's a known issue
Sent from my SCH-I535 using xda app-developers app

annoyingduck said:
Yes, the entire updated rom's are available in the development section. The latest being the vrlhd.
Click to expand...
Click to collapse
Mm, checked those out, and scrosler says that the bootloader needs to be unlocked, and doesn't provide any other information on how to flash it properly (Odin vs. custom recovery). Though if it's stock, it shouldn't matter...

I odin'd back to root66 and it took the update as soon as i checked for it. (and I dont even live in Verizon coverage)

[Q] Note 10.1 4G N8020 messed up

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

[Q] Help! Rooted phone with Custom Mode, ROM Manager Bricked

Hey guys,
I just got my phone and it updated to 4.4 pretty much out of the box. I still wanted to root so I used a method I found on here (will find if necessary) which is supposed to not trip the KNOX by putting the phone into "Custom Mode." Everything went fine until I tried to use ROM Manager to install CM.
When I boot I get the message "System software not authorized by Verizon Wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help." I've tried reflashing using Odin, clearing the cache and factory resets, but I get the same error every time.
I'm currently downloading another stock ROM which might work, but I wanted to see if anyone else has had this problem?
Thank you!

mortified21 said:
Hey guys,
I just got my phone and it updated to 4.4 pretty much out of the box. I still wanted to root so I used a method I found on here (will find if necessary) which is supposed to not trip the KNOX by putting the phone into "Custom Mode." Everything went fine until I tried to use ROM Manager to install CM.
When I boot I get the message "System software not authorized by Verizon Wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help." I've tried reflashing using Odin, clearing the cache and factory resets, but I get the same error every time.
I'm currently downloading another stock ROM which might work, but I wanted to see if anyone else has had this problem?
Thank you!
Click to expand...
Click to collapse
You are permanently stuck on the TW 4.3 OTA because the bootloader is signed with special keys that prevents:
-installing a custom recovery
-flashing custom roms/kernels
-downgrading your software below 4.3
If you can boot into download mode, do this 4.3 soft brick method.
With TW 4.3 OTA, all you can do is root using a tool called: Saferoot.

If you have 4.3 stock firmware you can root and that's it, no custom recovery, no custom rom, kernel, nothing, and just a heads up there are like 10 threads where people don't read and have done what you have, you need to flash the Odin 4.3 image for you phone to work again, never take an ota, enjoy your locked down device now
Sent from my SCH-I535 using XDA Premium 4 mobile app

SlimSnoopOS said:
You are permanently stuck on the TW 4.3 OTA because the bootloader is signed with special keys that prevents:
-installing a custom recovery
-flashing custom roms/kernels
-downgrading your software below 4.3
If you can boot into download mode, do this 4.3 soft brick method.
With TW 4.3 OTA, all you can do is root using a tool called: Saferoot.
Click to expand...
Click to collapse
Worked perfectly! Thank you so much!

mortified21 said:
Worked perfectly! Thank you so much!
Click to expand...
Click to collapse
My pleasure but all the thanks is owed to ThePagel, make sure to post your success in his thread. The more people that report their success with that method, then the less fear someone else may have in using that should they suffer the same experiences. :victory::good::good:
If you need any updates on the state of TW 4.3 then keep this discussion thread bookmarked.

I did the same thing today. The 4.3 update installed by itself!!! So i rooted it using Saferoot,
i installed rom manager, clicked the Install rom from sd card and i got that message. it will repeat that message and it wont boot. So i went into Odin mode and hit the volume down button to restart it. And after that it booted normally.
So basically i am stuck with 4.3? and is there 4.4 out for our phones yet?
also forgot to mention, it says my OS is custom when i first realized it updated.

AURMEND said:
I did the same thing today. The 4.3 update installed by itself!!! So i rooted it using Saferoot,
i installed rom manager, clicked the Install rom from sd card and i got that message. it will repeat that message and it wont boot. So i went into Odin mode and hit the volume down button to restart it. And after that it booted normally.
So basically i am stuck with 4.3? and is there 4.4 out for our phones yet?
also forgot to mention, it says my OS is custom when i first realized it updated.
Click to expand...
Click to collapse
Once you successfully updated with 4.3, you stuck with 4.3, there is no going back or flash anything and 4.3 is the latest factory rom for now. There's no 4.4 yet for our phone. There is custom 4.4 but only for people who didn't take the 4.3 update. Since they still have unlocked bootloader so they could load any custom rom.

buhohitr said:
Once you successfully updated with 4.3, you stuck with 4.3, there is no going back or flash anything and 4.3 is the latest factory rom for now. There's no 4.4 yet for our phone. There is custom 4.4 but only for people who didn't take the 4.3 update. Since they still have unlocked bootloader so they could load any custom rom.
Click to expand...
Click to collapse
Dang this sucks. I have no idea how it installed automatically then. I was listening to music the whole time. And I was trying to get a custom 4.4 after the update...

AURMEND said:
Dang this sucks. I have no idea how it installed automatically then. I was listening to music the whole time. And I was trying to get a custom 4.4 after the update...
Click to expand...
Click to collapse
Yep! sucks big time!!

Need help un-bricking my soft-bricked GS3

First off, I have a Verizon GS3 (SCH-I535). As of this morning, it was running the new 4.3 standard (no root, no unlocked bootloader, no custom recovery). I didn't like some of the UI changes in 4.3, and since I wanted to try custom ROMs out anyways, I figured now would be as good a time as any.
After doing hours of research, I was able to successfully get my phone rooted and TWRP installed (using the GooManager app). I had the AOKP d2vzw rom (milestone 1) downloaded and on my phone. I then tried to use GooManager to install the ROM. The phone rebooted into download mode, then gave an error message. I think I didn't properly unlock the bootloader.
After that, the phone wouldn't boot to a ROM at all. I've been trying to install stock ROMs using ODIN and was able to get the stock recovery back, but now all I can get to is the stock recovery and the Download Mode. Whenever the phone boots normally, I get the message, "System software not authorized by Verizon Wireless has been found on your phone . . ."
The biggest issue I've had is that it seem like nothing will install properly using ODIN. When trying to flash TWRP, it fails after NAND Write Start!!. When trying to flash a bootloader, it'll give a write/fail after aboot.
At this point, I'll be happy just getting it back to a working ROM. Any help would be appreciated.

WhiteRabbit44 said:
First off, I have a Verizon GS3 (SCH-I535). As of this morning, it was running the new 4.3 standard (no root, no unlocked bootloader, no custom recovery). I didn't like some of the UI changes in 4.3, and since I wanted to try custom ROMs out anyways, I figured now would be as good a time as any.
After doing hours of research, I was able to successfully get my phone rooted and TWRP installed (using the GooManager app). I had the AOKP d2vzw rom (milestone 1) downloaded and on my phone. I then tried to use GooManager to install the ROM. The phone rebooted into download mode, then gave an error message. I think I didn't properly unlock the bootloader.
After that, the phone wouldn't boot to a ROM at all. I've been trying to install stock ROMs using ODIN and was able to get the stock recovery back, but now all I can get to is the stock recovery and the Download Mode. Whenever the phone boots normally, I get the message, "System software not authorized by Verizon Wireless has been found on your phone . . ."
The biggest issue I've had is that it seem like nothing will install properly using ODIN. When trying to flash TWRP, it fails after NAND Write Start!!. When trying to flash a bootloader, it'll give a write/fail after aboot.
At this point, I'll be happy just getting it back to a working ROM. Any help would be appreciated.
Click to expand...
Click to collapse
When you are on 4.3, you can't unlock your phone anymore. That means no AOSP roms, but you can still use custom touchwiz roms based on 4.3. You're softbricked and you have to use this thread to fix it.
http://forum.xda-developers.com/showthread.php?t=2586319
After that completes, you can use this to root.
http://forum.xda-developers.com/showthread.php?t=2565758
Once you're rooted, this is the only recovery you can install, don't flash any other recovery.
http://forum.xda-developers.com/showthread.php?t=2605648
Read up on all the threads, 4.3 is completely different then 4.1 was.
Sent from my SCH-I535 using Tapatalk 2

Extra Info:
With Odin, I have made sure Kies is uninstalled. I've also tried multiple USB cables, including the ones the phone came with, and I've tried almost every USB port on my computer. Whenever Odin fails, it's in the exact same spot every time, which makes me think it's a software issue, not a hardware issue.
EDIT:
I was actually able to get the stock.vzw-root66 ROM installed by Odin without any errors. The phone rebooted immediately, then showed the android robot with the blue spinny thing in his chest, then the phone went back to the same Verizon error message.

BadUsername said:
When you are on 4.3, you can't unlock your phone anymore. That means no AOSP roms, but you can still use custom touchwiz roms based on 4.3. You're softbricked and you have to use this thread to fix it.
http://forum.xda-developers.com/showthread.php?t=2586319
After that completes, you can use this to root.
http://forum.xda-developers.com/showthread.php?t=2565758
Once you're rooted, this is the only recovery you can install, don't flash any other recovery.
http://forum.xda-developers.com/showthread.php?t=2605648
Read up on all the threads, 4.3 is completely different then 4.1 was.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
This worked like a charm! Thank you. I admit I am fairly new at all of this and did a ton of research beforehand, but I apparently did not research the differences between 4.1 and 4.3. You saved my butt!

WhiteRabbit44 said:
This worked like a charm! Thank you. I admit I am fairly new at all of this and did a ton of research beforehand, but I apparently did not research the differences between 4.1 and 4.3. You saved my butt!
Click to expand...
Click to collapse
TW 4.3 discussion thread has most info consolidated in one place:
http://forum.xda-developers.com/showthread.php?t=2575661
Sent from my SCH-I535 using Tapatalk 4

s3 root failed

I tried to root and it failed now I am trying to get My s3 verison 535 back to original. Unfortunately I no longer have my verizon service for this phone. I have tried to reset it but part way thru the set up it says set up failed.
Then It returns back to the verizon red screen
Any Ideas
thanks John

648charlie said:
I tried to root and it failed now I am trying to get My s3 verison 535 back to original. Unfortunately I no longer have my verizon service for this phone. I have tried to reset it but part way thru the set up it says set up failed.
Then It returns back to the verizon red screen
Any Ideas
thanks John
Click to expand...
Click to collapse
Can you tell us what steps you used to try to root?
What was the status of your phone before you tried to root?
Were you on the most recent update from Verizon? (It was over a year ago.)

I have signed into kies and it says
dawgdoc said:
Can you tell us what steps you used to try to root?
What was the status of your phone before you tried to root?
Were you on the most recent update from Verizon? (It was over a year ago.)
Click to expand...
Click to collapse
s3 was working when I switched to a note 4. I took the verizon service off the phone and it sat in the garage for about a year set at 4.42 installed king root.
when I reset the phone it says king root in shell
pda ne1 phone ne1 csc ne1 vzw both current and latest firm ware I can get a screen with time and be able to go into settings
does the fact that I have no service affect the phone going to the verizon screen?

648charlie said:
s3 was working when I switched to a note 4. I took the verizon service off the phone and it sat in the garage for about a year set at 4.42 installed king root.
when I reset the phone it says king root in shell
pda ne1 phone ne1 csc ne1 vzw both current and latest firm ware I can get a screen with time and be able to go into settings
does the fact that I have no service affect the phone going to the verizon screen?
Click to expand...
Click to collapse
Not having service shouldn't affect it in that way.
I bought a used i535 back in May that was on the stock 4.4.2 rom from a couple that had done no mods to the phone. It had been unused for several months. After receiving it I wiped it and did a factory reset. Following that I rooted with TowelRoot, installed BusyBox, and then SafeStrap. At that point I installed SuperLiteROM and followed that with XPosed. I never put the phone into service but had no issues with installing apps, xposed modules, etc. That is there were no issues until I lent it to a coworker.
I am not familiar with King Root and if it can cause problems. Likewise, I am not familiar with KingoRoot.
I sounds like you are getting to a homescreen since you are seeing a clock widget and can open settings. It could be that your launcher has been compromised. If that is true, the simplest fix may be to reflash the stock NE1 rom. Doing so most likely will cause you to loose root.
@ShapesBlue do you have any other ideas on this?

dawgdoc said:
Not having service shouldn't affect it in that way.
I bought a used i535 back in May that was on the stock 4.4.2 rom from a couple that had done no mods to the phone. It had been unused for several months. After receiving it I wiped it and did a factory reset. Following that I rooted with TowelRoot, installed BusyBox, and then SafeStrap. At that point I installed SuperLiteROM and followed that with XPosed. I never put the phone into service but had no issues with installing apps, xposed modules, etc. That is there were no issues until I lent it to a coworker.
I am not familiar with King Root and if it can cause problems. Likewise, I am not familiar with KingoRoot.
I sounds like you are getting to a homescreen since you are seeing a clock widget and can open settings. It could be that your launcher has been compromised. If that is true, the simplest fix may be to reflash the stock NE1 rom. Doing so most likely will cause you to loose root.
@ShapesBlue do you have any other ideas on this?
Click to expand...
Click to collapse
Yeah, I would say to restore stock firmware but as you know, after 4.3 you have a locked bootloader, this includes the 4.4.2 that you have now, if you flash the stock firmware make sure you flash exactly what you have now or one of the newer stock firmwares, do not try anything older than your 4.4.2, that would be a downgrade and the locked bootloader can't be downgraded or the device will perma-brick. Flashing stock and doing root over again is the simplest solution compared to troubleshooting this issue, more could get messed up if you try too many things.
648charlie said:
I tried to root and it failed now I am trying to get My s3 verison 535 back to original. Unfortunately I no longer have my verizon service for this phone. I have tried to reset it but part way thru the set up it says set up failed.
Then It returns back to the verizon red screen
Any Ideas
thanks John
Click to expand...
Click to collapse
Sent from my SCH-I535 using Tapatalk

got launcher from google apps
Droidriven said:
Yeah, I would say to restore stock firmware but as you know, after 4.3 you have a locked bootloader, this includes the 4.4.2 that you have now, if you flash the stock firmware make sure you flash exactly what you have now or one of the newer stock firmwares, do not try anything older than your 4.4.2, that would be a downgrade and the locked bootloader can't be downgraded or the device will perma-brick. Flashing stock and doing root over again is the simplest solution compared to troubleshooting this issue, more could get messed up if you try too many things.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Loaded launcher from google apps, talked to verizon and they put s3 inservice for 5 minutes and I made a call.
all is well
thank you thank you
John