So here’s my story. I was playing around with my phone on CleanROM and noticed that I was unable to get to extended network anymore. So I backed up my phone and Odined back to stock. After having a minor panic attack when Odin failed a few times, I finally got the image to push through. Booted up and still was unable to get connected to extended network. So then I reprovisioned my SIM card. Booted back up an finally was able to see extended network again . I then rooted my phone again and restored my backup and all is still working.
Now since I unlocked the bootloader before going back to stock and now restored my backup, is my phone still unlocked? When I open EZ-Unlock, it still shows as unlocked, but I thought that I would ask here too just to make sure.
i figured you wouldnt be only because going back to stock it should put that boot image back on thats locked... not sure either
Yup
:thumbdown:
:beer:
Yes you need to unlock the bootloader after odining a stock package everytime!
Thanks for the replies! I cleared the app data for EZ unlock and it switched to unknown so it must not actually check to see if it's done, it just remembers what it has done already.
Related
I was sitting on BART listening to pandora and reading news on pulse when suddenly I lost service. It has not come back at all no matter how many times I turn on airplane mode or take out battery.
I searched and found some Nexus one users with a similar problem but theirs all came back when they rebooted.
I thought it might haves something to do with the ota update so I posted the problem in one of those threads and someone suggested I check the IMEI. It has not reset to 0.
My phones history: I rooted about a month ago and tried to install a new ROM but bricked. I used Odin to flash back to stock and the phone has worked since. That said, even though I though I flashed back to unrooted stock, when I turn on the phone it still shows the open lock and says "custom" under samsung. So from my limited knowledge, this could mean that the bootloader is still unlocked?
If I try to do a factory reset and there is something still tweaked from when I tried to root, is that risky to the phone? At this point I don't care much about the data. I just really need the phone to ring when people call me.
When you odined back to stock did u do a factory reset after? In my experience a factory reset after a major change always cured the issues.
Sent from my SCH-I535 using xda app-developers app
Go back to stock via ODIN if you're not on it already, dial *2767*3855# after backing up anything you may want on internal storage (like photos, etc) because it will be wiped.
I ended up switching from cmda auto Perl to lte and it worked
Sent from my SCH-I535 using Tapatalk 2
I had previously rooted, unlocked and put a custom bootloader on my S3. I was enjoying Beans 10, but wanted to try Slimbeans. I got the initial .zip of Slimbeans installed, but the AIO .zip kept failing, so I had a useless device. Interestingly, I could not boot to recovery. My computer wasn't recognizing my stock Verizon ROMs. I was able to eventually download root66 and Odin that onto my phone, but when it starts up, it gets stuck at the Verizon 4G/LTE screen and never gets passed it. I have pulled the battery and turned the phone on several times, but get the same result. I thought I'd try another Odin attempt, but when I hold down the vol. down/power/home keys and then select the vol. up, I very briefly see the android guy and then then phone reboots. Please help, I'm stuck!
Well, I downloaded a different stock ROM and got that installed. In the meantime, I had to use my iPhone 4 as a backup. When I contacted Verizon to switch me back to the S3, it shows me as roaming. The tech was no help. Anyone with an idea?
Check network settings. Make sure you are on SIM and not NV
Sent from my SCH-I535 using Tapatalk 2
Thanks for the reply. GrainOSand, I had missed this.
I got the stock ROM flashed and thought I was good. The tech's were no help, but told me I needed a new SIM card. I went to my local Verizon store, got the card, the guy there tried to get my S3 going again, but couldn't.
Now, it acts like it is in a loop. It starts the Startup Wizard and very soon I just get the circle spinning and it tries to call the network. I Odin'd the ROM again with the same effect. I have a new phone that is supposed to be here tomorrow, but my Flash counter is at 1. Anyone know how I can get this thing working enough to use Triangle Away?
So, am I asking retarded questions, or is there really no answer?
At the wizard, try tapping all four corners clockwise, starting at the upper left to bypass the activation screen.
lvgdgts said:
Thanks for the reply. GrainOSand, I had missed this.
I got the stock ROM flashed and thought I was good. The tech's were no help, but told me I needed a new SIM card. I went to my local Verizon store, got the card, the guy there tried to get my S3 going again, but couldn't.
Now, it acts like it is in a loop. It starts the Startup Wizard and very soon I just get the circle spinning and it tries to call the network. I Odin'd the ROM again with the same effect. I have a new phone that is supposed to be here tomorrow, but my Flash counter is at 1. Anyone know how I can get this thing working enough to use Triangle Away?
Click to expand...
Click to collapse
You need to root the phone then install and run triangle away to get rid of the flash count http://forum.xda-developers.com/showthread.php?t=1494114 then odin back to stock
Also Im pretty sure you can simply odin to either the F2 or G1 ICS builds then type this in the dialer to fix the roaming issue as long as your imei is still intact.... *2767*3855#
No need to have the phone replaced, easily fixable
Roninrc51 said:
At the wizard, try tapping all four corners clockwise, starting at the upper left to bypass the activation screen.
Click to expand...
Click to collapse
That sounded interesting, but didn't work.
x714x said:
You need to root the phone then install and run triangle away to get rid of the flash count http://forum.xda-developers.com/showthread.php?t=1494114 then odin back to stock
Also Im pretty sure you can simply odin to either the F2 or G1 ICS builds then type this in the dialer to fix the roaming issue as long as your imei is still intact.... *2767*3855#
No need to have the phone replaced, easily fixable
Click to expand...
Click to collapse
I'll give this a go at home tonight.
Hello guys, I have a Samsung S3 that was purchased "unlocked" to work on T-Mobiles network. After that failed attempt, we switched over to Verizon. 3 weeks later the phone read a message "System Software not authorized". I tried the steps detailed: http://forum.xda-developers.com/showthread.php?t=1840030&highlight=system+software+not+authorized with no errors. However, the phone will not boot. I get infinite boot loop. Honestly, I dont know where to go next. The phone still shows a "unlocked" icon when booted also. All I want to do is get the phone back to its original VZW supported state. Thoughts?
.
Interesting enough, after another wipe of the cache the phone booted up. How can I remove the 'custom' icon and lock this phone back up? I don't want to be denied service at VZW in the future if possible.
You could flash a stock ICS ROM and then update using OTA and it would remove the root, unless its not activated on Verizon. If not, I'll help from there. Let me ask some people to see if my method would work first though.
Sent from my SCH-I535 using xda app-developers app
I was messing around with CM and I went into twrp to restore a backup and now my phone is locked. Can anyone point me where to go with this?
If you encrypted your device they only solution to decrypt is to factory reset.
Sent from my HTC6525LVW using Tapatalk
You need to search around here. This is a documented issue with aosp ROMs. Someone put out a command line fix (i think it's in the noon-carrier-specific m8 forum) or you can use the ruu files found in this forum.
electric turd said:
I was messing around with CM and I went into twrp to restore a backup and now my phone is locked. Can anyone point me where to go with this?
Click to expand...
Click to collapse
i just sent in my phone after this same issue i had tried the newest nightly from CM and flashed fine ran through the whole set up process then found out my bluetooth dont work so i restored my most recent bak booted my phone up and i get a message to put in my password that i have never set up
electric turd said:
I was messing around with CM and I went into twrp to restore a backup and now my phone is locked. Can anyone point me where to go with this?
Click to expand...
Click to collapse
I have had this twice now, i fixed it by formatting data in twrp then factory resetting and restoring a backup from my sd. I lost all my internal storage.
factory reset dont work either sorry were both S.O.L. unless u have insurance then just "loose ur phone"
I'm back guys!!!!! I ruu'ed in fastboot. Weird thing was when my phone booted back up it still had supersu!!!!!! That made me happy. I then flashed twrp through flashify and restored a back up I made before this whole fiasco. Thanks again for everything!!!!
So you returned your phone to Verizon over this? If it turns on you can fix it.
electric turd said:
I'm back guys!!!!! I ruu'ed in fastboot. Weird thing was when my phone booted back up it still had supersu!!!!!! That made me happy. I then flashed twrp through flashify and restored a back up I made before this whole fiasco. Thanks again for everything!!!!
So you returned your phone to Verizon over this? If it turns on you can fix it.
Click to expand...
Click to collapse
mine turns off right after it boots dosent matter where it boots to
skcitzo said:
i just sent in my phone after this same issue i had tried the newest nightly from CM and flashed fine ran through the whole set up process then found out my bluetooth dont work so i restored my most recent bak booted my phone up and i get a message to put in my password that i have never set up
Click to expand...
Click to collapse
So you sent in a phone that you broke and that can be fixed but are too lazy to research? And this is why companies lock down bootloaders. If you cant do basic searching, then dont root your phone.
Ok so admittedly I made a noob mistake and inadvertently unchecked OEM unlock and rebooted. So I'm stuck on FRP lock. From what I see, my only option is to flash the original firmware on the phone.
My question is simple: I don't have TWRP and can't do a NAND backup. Will my internal SD card get wiped as well? If so, is there ANY way I can back it up before hand??
Thanks...
Ok so I managed to save my arse after all, but I figured I would leave a reply here for archival purposes.
I used Odin to flash the stock Bootloader and PDA. Not only it didn't touch my SD, but it really didn't wipe anything and I only lost my root.
Two things happened I didn't see documented anywhere I looked: I got a weird crash on boot update and ended up in Stock recovery after auto reboot and got a slew of error messages, but a simple phone reboot worked.
Then I was asked for a password to restart, which turned out to be "default_password"...
Hope this will help someone down the road!
Sent from my SM-G930W8 using XDA-Developers mobile app
Cleaned & wiped all stuff, flashed stock 6.0.1 with Odin AP,BL,CP,CSC and same FRP google login shows up. Mind sharing those two files?
For sure, I just used the latest firmware on Sammobile: this is the generic one for Canada, but I'm on Rogers so I used this one.
I only used the BL and PDA, but I also made sure I wasn't locked out on my Samsung Account. FRP can be because of the custom binaries, but it can also be a system lock out and I've read that in some cases it's because the phone has soft locked itself out. Not sure how accurate that is, but wouldn't hurt to check I guess...
now all ok or still facing same?