Background: My GS3 was rooted and running ICS 4.0.1 and TWRP recovery nearly since the day I got it--stock Tochwiz ROM for the main reason of being able to tether and run Google Wallet. Everything was working great, but I completely restored the phone to stock (no root, stock recovery, phone wiped) with the intention of installing the latest OTA, Jelly Bean 4.1.1 (and then subsequent 4.1.2 which was pushed down a few days ago) and then re rooting and re installing TWRP recovery.
Issue: After closely following the steps outlined here to root my GS3, unlock bootloader and install TWRP, everything seemed to work fine, until Google Wallet installation gave me an error that NFC was disabled. When going to my settings to correct this (Settings>Wireless and network>More settings) I noticed I had absolutely NO NFC SETTINGS. I already tried re-flashing a fresh download, searching XDA and Google, with no luck. Any suggestions? I really miss NFC already.
Related
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
Model xt912 Razr Maxx "verizon"
I used "razr_blade_zip" to root phone. Followed instructions and worked fine. Then installed "safestrap" 3.65. Then went to recovery mode and created a back-up. Then installed cm11-20131126 unofficial-spyder and google app package. I installed cm 11 on slot 1. Rebooted and everything worked well. I did notice cell signal was low. After I installed a few basic rooted apps to increase network speed like "example Faster Gps". Still so far so good. Here is when things went wrong. After reading about SuperSu I decided to install it and missed a step. I ended up unrooting my in phone. I can't use Safestrap to install back-up. I'm not sure what a hard reset will do. I have googled issue but no real answer on fixing this. Thanks for any help!!!!!
Model xt912 Razr Maxx "verizon"
I used "razr_blade_zip" to root phone. Followed instructions and worked fine. Then installed "safestrap" 3.65. Then went to recovery mode and created a back-up. Then installed cm11-20131126 unofficial-spyder and google app package. I installed cm 11 on slot 1. Rebooted and everything worked well. I did notice cell signal was low. After I installed a few basic rooted apps to increase network speed like "example Faster Gps". Still so far so good. Here is when things went wrong. After reading about SuperSu I decided to install it and missed a step. I ended up unrooting my in phone. I can't use Safestrap to install back-up. I'm not sure what a hard reset will do. I have googled issue but no real answer on fixing this. Thanks for any help!!!!!
I am having a really weird issue I'm hoping someone can help me out with. I was on 4.1.2 Clean ROM which was working great. I wanted to move to 4.3 Clean ROM (8.1 Core Edition). I did the upgrade and then flashed my modem to ML1 both via TWRP.
The ROM setup fine and ran great. However the first time I did a reboot, the phone gets stuck at the Samsung Galaxy S3 logo and never goes anywhere. I left it sit there for 30 minutes and it was hard locked. Only a battery pull would reset it. Through numerous reboots/pulls, the same thing would happen. I tried wiping Dalvik and Cache in TWRP and fixing permissions, to no avail. Reinstalling Clean ROM 8.1 via TWRP without formatting data did not fix the issue either. The only way to get my phone back up and running was a complete wipe and reinstalling from scratch. Then as soon as I reboot the first time, the issue comes back. I've tested this on a clean install - letting the phone go through the initial setup process but not installing or updating any apps - and it still happens.
So I moved on to try AllianceROM build 22, also a 4.3 build and wiped to do a clean install. No matter what options I choose in the setup, the same problem happens. Interestingly in AllianceROM I always get a acore process has failed error on the first boot.
Then I went to download the Knox-free rooted version of stock 4.3 available from Scott's website. I have the same issue with this. Also a wipe with clean install.
It's obvious there is something my phone doesn't like about moving from 4.1.2 to 4.3. In total, I have probably installed three different ROM's about 20 times now after the past couple days.
I've searched about this problem extensively and the only thing I found is a thread for the AT&T S3 that talks about this exact issue, and using Odin to go to stock 4.3 and loading a custom ROM to fix the issue. But I am under the impression that a 100% stock 4.3 will lock my bootloader.
What I plan to do next is use Odin to flash a stock 4.1.2, then go through the process of moving to a custom 4.3 ROM again.
If anyone knows of a tar'd version of 4.3 that won't lock my bootloader, I would be grateful!
If anyone knows of a different way to fix my problem, I would be grateful for that too!
Well I think I can declare victory. My phone is running Clean Rom 8.1 CE and has survived a reboot after every app install for a total of 15 so far.
As it turns out, I think being on TWRP 2.5 and trying to upgrade to Android 4.3 was the issue. Before I went the route of flashing a stock 4.1.2 release, I thought to check if my version of TWRP was the latest, and it was not. I flashed TWRP 2.7, and did a complete wipe and clean install of Clean Rom 8.1 CE, and it's running like a champ.
I know, I know...the install guide on most every ROM says to use the latest version of your recovery - until now I thought that was a "recommendation" or "best practice" and not a hard requirement. Turns out, at least for me, that it is very much a hard requirement. In reading the release notes for TWRP 2.6 and 2.7, they both appear to implement things specifically for Android 4.3 or 4.4.
Hopefully this info helps someone who may be having the same issue.
I have a Verizon Galaxy SCH-I535, it had Android 4.3, but I downgraded it to 4.1.2 creating a custom-stock ROM.
Now I rooted it, unlocked the bootloader, installed TWRP 3.0.0 and tested other recoveries as well, and also flashed several ROMs, all of them correctly but when the ROMs starts, just about to show the FIRST SCREEN of the Setup Wizard, the image crashes and shows blinking colored dots.
At the end the only ROM I can have booted is the 4.1.2 that I saved.
Can anyone tell me how can I do to have a different ROM installed, and thta is correctly booted,thanks.
aaronkish said:
I have a Verizon Galaxy SCH-I535, it had Android 4.3, but I downgraded it to 4.1.2 creating a custom-stock ROM.
Now I rooted it, unlocked the bootloader, installed TWRP 3.0.0 and tested other recoveries as well, and also flashed several ROMs, all of them correctly but when the ROMs starts, just about to show the FIRST SCREEN of the Setup Wizard, the image crashes and shows blinking colored dots.
At the end the only ROM I can have booted is the 4.1.2 that I saved.
Can anyone tell me how can I do to have a different ROM installed, and thta is correctly booted,thanks.
Click to expand...
Click to collapse
I have my old S3 running CleanRom and I've for the most part never had an issue with the setup wizard on that device. On others have. Are you clearing the cache and the dalvik after flashing the rom?
Sent from my Nexus 6
ShapesBlue said:
I have my old S3 running CleanRom and I've for the most part never had an issue with the setup wizard on that device. On others have. Are you clearing the cache and the dalvik after flashing the rom?
Sent from my Nexus 6
Click to expand...
Click to collapse
Yes, I always clean cache, dalvik, system, data and even internal storage.
I have tried with:
(5.0.2)aicp_d2vzw_lp-8.0-RELEASE-20150210
(5.1.1)aicp_d2vzw_lp-9.0-NIGHTLY-20150605
(5.1.1)cm-12.1-20150606-NIGHTLY-d2vzw
(5.1.1)OCT-L-M6-FINAL-5.1.1-20151229-d2vzw
(5.1.1)Slim-d2vzw-5.1.1.beta.0.12-OFFICIAL-20151116-0147
(6.0.1)Broken-v4.6-d2vzw-6.0.1-OFFICIAL-20160503
(6.0.1)Slim-d2vzw-6.0.1.alpha.0.2-WEEKLY-20160628-0745
No luck with any of those, but I restored the backup I did before(Android 4.1.2), and everythings works fine. Funny thing is that it even shows the screen for "Updating apps 1 of 83" and so, but when it "wants" to start it crashes and reboots in a few seconds.
But, anyways, that is past now, I lost my mind and flashed the stock 4.3, it hardbricked my phone, I used the unbrick method for 4.4.2 and I don't know how I ended up with the wrong kernel so there is no going back now, I flashed stock 4.4.2, so no downgrade possible now.
I have read about JTAG solution to downgrade, is it possible?
I bought the Octoplus Dongle for Samsung Lite, but I don't think it works for this type of problem.
I will ask in a different thread. Thanks anyways.
aaronkish said:
Yes, I always clean cache, dalvik, system, data and even internal storage.
I have tried with:
(5.0.2)aicp_d2vzw_lp-8.0-RELEASE-20150210
(5.1.1)aicp_d2vzw_lp-9.0-NIGHTLY-20150605
(5.1.1)cm-12.1-20150606-NIGHTLY-d2vzw
(5.1.1)OCT-L-M6-FINAL-5.1.1-20151229-d2vzw
(5.1.1)Slim-d2vzw-5.1.1.beta.0.12-OFFICIAL-20151116-0147
(6.0.1)Broken-v4.6-d2vzw-6.0.1-OFFICIAL-20160503
(6.0.1)Slim-d2vzw-6.0.1.alpha.0.2-WEEKLY-20160628-0745
No luck with any of those, but I restored the backup I did before(Android 4.1.2), and everythings works fine. Funny thing is that it even shows the screen for "Updating apps 1 of 83" and so, but when it "wants" to start it crashes and reboots in a few seconds.
But, anyways, that is past now, I lost my mind and flashed the stock 4.3, it hardbricked my phone, I used the unbrick method for 4.4.2 and I don't know how I ended up with the wrong kernel so there is no going back now, I flashed stock 4.4.2, so no downgrade possible now.
I have read about JTAG solution to downgrade, is it possible?
I bought the Octoplus Dongle for Samsung Lite, but I don't think it works for this type of problem.
I will ask in a different thread. Thanks anyways.
Click to expand...
Click to collapse
Did you update the radio/baseband to NE1? No need to utilize a jtag as your flashing custom roms so the device is already bootloader unlocked
Edit: nevermind you updated to the latest stock so as you already know your bootloader is locked
Sent from my Nexus 6