Related
So I'm totally at a loss of where to go or what to even search for.
I have a verizon Galaxy s3 that I rooted and unlocked the bootloader on. I flashed a couple ROMs and now it won't connect to the network. It tells me it is in roaming mode only. I called verizon, but they said to just return the phone because it won't talk to their network.
I've read some things about "triangle away" and I kind of tried that. But it kept telling me that my flash count was 0 anyway. So it didn't do anything.
My IMEI and ICCID are correct to my sim card and phone. I originally flashed CM10 for the verizon s3 and it worked great for a few weeks. Then I tried a couple others and they worked also. Then I flashed the euroskank ROM, and that's when it no longer would connect. I went back to a previous nandroid, and still no connecting.
I don't know what the problem is, or what to search for, or where to go.
Should I try to install a stock rom. I know I keep seeing things about odin and installing the stock rom. Should I do that? That's something I haven't tried yet.
So, I tried reprovisioning the phone with *2767*3855#
And when I did that, it said sorry, your phone is not yet activated.
But I know it is, or, at least was activated. And when I call verizon they tell me it has been activated already. I don't know what to do. I'm thinking of trying to go back to stock
Same Problem
Flashed CM10.1 nightly just to test it out and then boom, no more connection. On any ROM. Scariest part? I have gone through the restore process and am now back to an unrooted phone with out of the box firmware. I believe I will take it back to Verizon now and see if they will give me a new one.
SpencePatriot said:
Flashed CM10.1 nightly just to test it out and then boom, no more connection. On any ROM. Scariest part? I have gone through the restore process and am now back to an unrooted phone with out of the box firmware. I believe I will take it back to Verizon now and see if they will give me a new one.
Click to expand...
Click to collapse
So I don't know if we have the same issue or not. But I got mine working for now. Don't know if I'll run into problems later, but this is how I got it working right now.
First, I installed back to stock settings and radio. I followed the instructions in this post
http://forum.xda-developers.com/showthread.php?t=1762709
I did the stuff in section 5. Including Flashing a Stock Radio. So I went back to the VRALG1 4.0.4 ROM.
And I did the I535VRLHE radio.
But it still didn't work. BUT, once in stock settings, I did the reprovisioning.
*2767*3855#
And then that finally worked, it went through, and my phone activated. So it works now. Hooray!
But I REALLY really want to know what happened. So I can avoid this happening again in the future. Can anyone tell me what happened, and why this fixed it? And how to prevent it happening again as a flash more ROMs in the future?
Also, SpecePatriot, let me know if that works for you. It'd be good to have more than one source to know that works.
nertskull said:
So I don't know if we have the same issue or not. But I got mine working for now. Don't know if I'll run into problems later, but this is how I got it working right now.
First, I installed back to stock settings and radio. I followed the instructions in this post
http://forum.xda-developers.com/showthread.php?t=1762709
I did the stuff in section 5. Including Flashing a Stock Radio. So I went back to the VRALG1 4.0.4 ROM.
And I did the I535VRLHE radio.
But it still didn't work. BUT, once in stock settings, I did the reprovisioning.
*2767*3855#
And then that finally worked, it went through, and my phone activated. So it works now. Hooray!
But I REALLY really want to know what happened. So I can avoid this happening again in the future. Can anyone tell me what happened, and why this fixed it? And how to prevent it happening again as a flash more ROMs in the future?
Also, SpecePatriot, let me know if that works for you. It'd be good to have more than one source to know that works.
Click to expand...
Click to collapse
I also flashed a cm 10.1 Nightly this one to be more specific http://forum.xda-developers.com/showthread.php?t=1843628 and it caused me to not be able to make any phone calls. I tried what you did and it worked and just to make sure that it was that rom causing problems i rooted and flashed it again and it happend again.
sin 7227 said:
I also flashed a cm 10.1 Nightly this one to be more specific http://forum.xda-developers.com/showthread.php?t=1843628 and it caused me to not be able to make any phone calls. I tried what you did and it worked and just to make sure that it was that rom causing problems i rooted and flashed it again and it happend again.
Click to expand...
Click to collapse
Well that's good to know that you got it back working again. Sounds like it might be just be the ROM and not anything weird that we did to cause the loss of connectivity.
Thanks nertskull
Thanks nertskull, I had this problem after trying to downgrade from CM10.1 to CM10 and was stuck. I tried so many different methods and nothing worked until this one, thanks so much!
Input
halfgod85 said:
Thanks nertskull, I had this problem after trying to downgrade from CM10.1 to CM10 and was stuck. I tried so many different methods and nothing worked until this one, thanks so much!
Click to expand...
Click to collapse
I had the an issue with my phone stuck roaming and this method worked great! Only problem I came across was trying to run Samsungs update for Jelly Bean, Every time I attempted to update my phone would crash and go back to ICS. Luckily I had a back up so I wiped my phone, restored from my previous backup (which had Jelly Bean) and worked without roaming issues!
My input is if your having roaming issues is to use a backup you made before you had the roaming issue. Follow this tutorial above to get your phone back to stock, root your phone, then restore from your backup through CWM or whatever you are using.
I am not too sure what causes the roaming issue but I did notice while looking for networks, my phone found ATT ad TMobile haha.I am assuming what happened was that the Cyanogenmod update I was downloading automatically was set for another carry which changed my wireless settings. I will be downloading nightly's manually for now on lol
Thanks for this fix, Saved me a lot of time and aggression
Mitch90 said:
I had the an issue with my phone stuck roaming and this method worked great! Only problem I came across was trying to run Samsungs update for Jelly Bean, Every time I attempted to update my phone would crash and go back to ICS. Luckily I had a back up so I wiped my phone, restored from my previous backup (which had Jelly Bean) and worked without roaming issues!
My input is if your having roaming issues is to use a backup you made before you had the roaming issue. Follow this tutorial above to get your phone back to stock, root your phone, then restore from your backup through CWM or whatever you are using.
I am not too sure what causes the roaming issue but I did notice while looking for networks, my phone found ATT ad TMobile haha.I am assuming what happened was that the CM update I was downloading automatically was set for another carry which changed my wireless settings. I will be downloading nightly's manually for now on lol
Thanks for this fix, Saved me a lot of time and aggression
Click to expand...
Click to collapse
My S3 is having the same issue after a CM10 modification. Reflashing to a stock ROM fails, wiping and reflashing fails, trying a different rom on cwm fails, no backups to flash to (all result in error). So I stumbled upon this thread, read about reprovisioning, and I took it to mean input the numeric code into the phone dialer. I did that, and nothing happened. Can anyone provide insight on reprovision and how to do it? Google search on reprovision isn't giving me any hints.
If the reprovision is just failing and I've been doing it right, does anyone have any other suggestions? Really hoping my phone isn't soft-bricked with no ability to call/text.
nertskull said:
So I don't know if we have the same issue or not. But I got mine working for now. Don't know if I'll run into problems later, but this is how I got it working right now.
First, I installed back to stock settings and radio. I followed the instructions in this post
http://forum.xda-developers.com/showthread.php?t=1762709
I did the stuff in section 5. Including Flashing a Stock Radio. So I went back to the VRALG1 4.0.4 ROM.
And I did the I535VRLHE radio.
But it still didn't work. BUT, once in stock settings, I did the reprovisioning.
*2767*3855#
And then that finally worked, it went through, and my phone activated. So it works now. Hooray!
But I REALLY really want to know what happened. So I can avoid this happening again in the future. Can anyone tell me what happened, and why this fixed it? And how to prevent it happening again as a flash more ROMs in the future?
Also, SpecePatriot, let me know if that works for you. It'd be good to have more than one source to know that works.
Click to expand...
Click to collapse
I know this is a few weeks old, but I have to say thank you for this. It worked perfectly for me, and rather than wait 48 hours for Verizon tech support to call me back, I was able to solve my own problem. Thank you, again.
Darthbull said:
I know this is a few weeks old, but I have to say thank you for this. It worked perfectly for me, and rather than wait 48 hours for Verizon tech support to call me back, I was able to solve my own problem. Thank you, again.
Click to expand...
Click to collapse
Hey guys, when you provision does it wipe the entire phone, including the SD card? (internal SD card and external SD card)
stuck...
I tried all the above, stock, radios, kernels, codes, ##RTN#, none of it works, my radio works cause i tried 911 and it jumped on roaming and began to make call at which point of course i hung up before letting it connect any words of wisdom... at this point just a tablet for wifi
stang68x said:
Hey guys, when you provision does it wipe the entire phone, including the SD card? (internal SD card and external SD card)
Click to expand...
Click to collapse
Bump
no sd wipe
stang68x said:
Bump
Click to expand...
Click to collapse
neither *2767*3855# nor ##786# wipe sd card, files on sd card stay intact
I have a galaxy note 2 on Verizon. This used to happen to me on CM 10.1 first stages but issue got fixed as the nightlies started. It only happened to me when I sometimes rebooted the phone or when the battery completely drained from 100-0% then when I would charge it and boot the phone it would show me an x and no signal bars. I would have to restore to a TW rom to get it to activate again but going into settings and switching to CDMA/LTE mode. Now I'm on ParanoidAndroid 2.99beta ROM and it still gives me that issue. Hopefully soon it will be fixed.:fingers-crossed:
nertskull said:
So I don't know if we have the same issue or not. But I got mine working for now. Don't know if I'll run into problems later, but this is how I got it working right now.
First, I installed back to stock settings and radio. I followed the instructions in this post
http://forum.xda-developers.com/showthread.php?t=1762709
I did the stuff in section 5. Including Flashing a Stock Radio. So I went back to the VRALG1 4.0.4 ROM.
And I did the I535VRLHE radio.
But it still didn't work. BUT, once in stock settings, I did the reprovisioning.
*2767*3855#
And then that finally worked, it went through, and my phone activated. So it works now. Hooray!
But I REALLY really want to know what happened. So I can avoid this happening again in the future. Can anyone tell me what happened, and why this fixed it? And how to prevent it happening again as a flash more ROMs in the future?
Also, SpecePatriot, let me know if that works for you. It'd be good to have more than one source to know that works.
Click to expand...
Click to collapse
This worked for me after trying everything else. I wish I found this 4 hours ago.
wwonka69 said:
This worked for me after trying everything else. I wish I found this 4 hours ago.
Click to expand...
Click to collapse
Spoke too soon. I wanted to try Miui and backed up and then installe miui but it was flaky so I tried wiping and then restoring but Now I have the No radio problem back.
Even after I restore to a clean install I still get this issue.
wwonka69 said:
Spoke too soon. I wanted to try Miui and backed up and then installe miui but it was flaky so I tried wiping and then restoring but Now I have the No radio problem back.
Even after I restore to a clean install I still get this issue.
Click to expand...
Click to collapse
Ok it only works if you are on 4.04 as far as I can tell.
bump:good:
nertskull said:
So I don't know if we have the same issue or not. But I got mine working for now. Don't know if I'll run into problems later, but this is how I got it working right now.
First, I installed back to stock settings and radio. I followed the instructions in this post
http://forum.xda-developers.com/showthread.php?t=1762709
I did the stuff in section 5. Including Flashing a Stock Radio. So I went back to the VRALG1 4.0.4 ROM.
And I did the I535VRLHE radio.
But it still didn't work. BUT, once in stock settings, I did the reprovisioning.
*2767*3855#
And then that finally worked, it went through, and my phone activated. So it works now. Hooray!
But I REALLY really want to know what happened. So I can avoid this happening again in the future. Can anyone tell me what happened, and why this fixed it? And how to prevent it happening again as a flash more ROMs in the future?
Also, SpecePatriot, let me know if that works for you. It'd be good to have more than one source to know that works.
Click to expand...
Click to collapse
Thank you buddy,
This helped me get my phone back in working order -- For those of you wondering why the "*2767*3855# is not working is because you are using the wrong flash. You must use "Official VRALG1 4.0.4" - and currently the link is down on the thread - I just googled it and found it elsewhere. I tried one of the other OTA's and it would not work. Also, do exactly as netskull described - even regarding the antenna. When using VRALG1 4.04 - The second i entered the last "hashtag (#)" it popped up another screen which helped get my phone working. I did not have to press send or anything. Kind of sucks that I lost all data on my internal card, but I DID back it up and now I will have to go through and restore. Since some people were wondering -- It did not mess with anything on the external card... It did unroot my device, however, so I will have to do that again as well.
For some reason, flashing the latest MIUI messed up my phone and put it in roaming all the time. Oh well, happy i got it working, and subscribed . Thanks once again Nertskull.
I was running the latest stable version of CM10.1 on my GS3 and all was going well until someone sent me a text message and I tried to respond. I was greeted with the error of message not sent. I attempted to text someone else to have the same error. Attempting to call someone will just hang and eventually say call failed.
I thought it was a radio issue so attempted to flash different modems but had the same result. So I restored my previous rom Beans 11 that was working after wiping and the same issue. Data works perfect, but voice and text does not. I searched and odin'd back to stock VRLG1 and entered *2767*3855# in hopes of that fixing the problem, again no voice/text.
Any suggestions further help? I don't know what else to try!
*CM10.1 was working fine, and then calls/texting stopped but data continued to work without trouble.
*IMEI seems to be intact
*Flashed backup of known working rom and issue still persists
*Flashed back to VRLG1 and attempted *2767*3855# as per another post to no avail and this is where I sit.
Same thing. Installed jellybeans 12 now I can't call or text. Prior text was hit and miss some days....restored stock rooted image flashed other Roms....no help. Dialed the ** number....so screwed. Ayneegry should have backed up my few several times. No idea what to do.
Sent from my SCH-I535 using Tapatalk 2
When you say "Data" do you mean wifi or 3g/4g? If you have no phone/text/3g/4g then it's probably your imei. Check under phone settings, see if it's gone. If it's gone you gotta restore, do a search.
If you have 3g/4g then I don't know what the problem is. Sorry, just trying to help
Odin back to ICS and reprovision your phone by going into the dialer and typing *2767*3855#
rgrossie - data as in 3G/4G works no problem... phone showed IMEI still there but followed a thread to restore it anyway to make sure that wasn't the issue...
Edgehood -- I've tried that, and that's where I currently sit, stock ICS with 4G data but doing the re-provision doesn't seem to fix anything -- occasionally a text will slip through, but I'm unable to reply
astrocity said:
Same thing. Installed jellybeans 12 now I can't call or text. Prior text was hit and miss some days....restored stock rooted image flashed other Roms....no help. Dialed the ** number....so screwed. Ayneegry should have backed up my few several times. No idea what to do.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I hear ya, if I can't figure out what's up, I'll end up having to go back to verizon and see what I can do... It was out of the blue, everything was working and then suddenly it just stopped. Happened on a flash that was a little over a day old, so who knows.
Check Mobile network
I have thiss problem happen occasionally when I flash custom roms. Look under your mobile networks, see if either CDMA/SIM is checked or NV. If NV is checked switch to CDMA/SIM and then reboot. That seems to fix that problem most of the time.
Edit: After some tests found out this doesn't always stick, but I did find out that after switching from NV to CDMA/SIM turn on airplane mode so the radios are tunred off, wait a few moments, then turn airplane mode off. That worked more consistently than restarting it.
MrRevesz said:
rgrossie - data as in 3G/4G works no problem... phone showed IMEI still there but followed a thread to restore it anyway to make sure that wasn't the issue...
Edgehood -- I've tried that, and that's where I currently sit, stock ICS with 4G data but doing the re-provision doesn't seem to fix anything -- occasionally a text will slip through, but I'm unable to reply
Click to expand...
Click to collapse
Did you ever fix this? I currently have the same problem and have no idea what to do.
i had the same problem but a imei/efs restore fixed it. My imei was not missing but data worked and not calls or text. Changed sim and still same, even odined back to stock and unlockex and rooted no luck restored nandroid no luck. Then restored synergy imei/efs backup and good to go. Hope it helps.
Cruzin' tha Galaxy SIII via Obsessed Rom / "INAPPROPRIATE" Kernel
I had the same issue two days ago when I flashed to the latest MIUI Rom. Here's how I fixed it.
Go into settings, mobile networks, make sure subscription is set to SIM. After that open the phone, type *#*#4636#*#* make sure it's set to LTE/CDMA/AUTO
Reboot phone and all should be well.
Sent from my 16GB Blue Verizon Galaxy S3 running MIUI v5 with KT kernel
If you Odin back to the original stock unroofed ROM, you'd have to take all the ota Verizon updates to vmf1. Then reset your phone.
Pain in the a$$ but has always worked for me. I had same problem running carbon.
I read in another post that Odin back to root66, them reset your phone would work too.
Sent from my SCH-I535 using xda app-developers app
I was running slim 4.2.1 for quite some time with no problems, i loved it. I flashed 4.2.2 and my phone got stuck in NV and my phone number would come up as 000-000-3370. On first boot everything seems to be fine except that i get an error when i try to open up the play store. On my next boot is when I would see these problems. I tried everything from dirty flashing from a working 4.2.1 rom to completely formatting everything, even my external sd, and the same thing happens. This happens with every 4.2.2 rom out there. When i reboot i get stuck on the activating screen and my phone will get stuck in NV and ruim/sim wont stick no matter what i do. i don't know what else to do. someone please help!
It isn't a rom issue it is an S 3 issue that randomly occurs when flashing ROMs. You will have to flash the stock rom and reprovision your phone. I know because it has happened to me twice and both times it was with a Touchwiz ROM. You should have backed up your IMEI just in case this happens.
my imei is backed up. but why is it only 4.2.2 roms that do this?
I was able to flash back to a 4.2.1 Rom, namely pure Google for now, with no problems. but when I flash any 4.2.2 Rom the same thing happens.
All 4.2 ROMs used to do this to me.
However.
Only also happened when I flashed miui.
Now I run liquid smooth and haven't had the problem since.
sent from that young galaxy.
God bless the American people!
do u guys think I should Odin back to stock, then root, unlock, and try to flash 4.2.2?
Actually, there is an easier way
I have had this happen numerous times and it lef me to mess with my phone a little bit. I originally thought that setting it to CDMA/SIM and then rebooting would fix the problem, but I found a simpler solution to that. The last time I encountered the problem I simply set the phone to RUIM/SIM under mobile networks and then Turned on airplane mode for a few seconds then turned it off and I found my number under phone settings and everything. Try that and let me know how it goes.
Edit: Sorry, the term is RUIM/SIM, not CDMA/SIM. My bad.
hmmm, I'll definitely give that a shot later on tonight.
well I tried it, it works. but only temporarily. once I reboot it reverts back to how it was. any other thoughts?
anyone?
Chitala383 said:
anyone?
Click to expand...
Click to collapse
try this. i had the same problem. http://forum.xda-developers.com/showpost.php?p=35600769&postcount=2
nope, none of that works either. no matter what I do ruim/sim will not stick on a reboot on any 4.2.2 Rom. I'm really getting frustrated with this.
no one has any other solutions for me?
Chitala383 said:
anyone?
Click to expand...
Click to collapse
Does your phone display an IMEI number?
Settings->About->Status
Don't need the number, just to know if you have it there....
Also do you still have Root/Unlocked bootloader?
yes, i have an imei. i lost it once before so now its backed up, i'll never make that mistake again. it was a nightmare trying to get it back. and yes, i am rooted and unlocked.
Chitala383 said:
yes, i have an imei. i lost it once before so now its backed up, i'll never make that mistake again. it was a nightmare trying to get it back. and yes, i am rooted and unlocked.
Click to expand...
Click to collapse
Have you done a complete factory restore through Odin? You would lose root and unlocked bootloader, but it may be faster to restore to stock, and reroot/mod than to try to find an "easy" fix. I was having some issues the other day in between a few ROM's, but I just factory restored, and restarted from "scratch". Now I am running perfect.
You may have already tried, but on page 1 you asked if you should, and I did not see a confirmation you did so.
Had the same problem... And yes, the phone must be reprovisioned. Although sometimes you can just adjust the network settings and change it from NV. That worked for me also.
Sent from my SCH-I535 using Tapatalk 2
I flashed root 66 via Odin, bootloop. flashed the ma2 stock image, bootloop. then flashed the lk3 stock image with success. but still with the same results as before.
tomorrow I'll try flashing g1 and start from scratch there. what do u guys think?
well, I odin'd back to bone stock G1, rooted with rootdebugfs, flashed cwm with ez recovery, unlocked my bootloader with ez unlock, flashed liquidsmooth 4.2.2 rc2 and guess what. same ****!!!!!!!!!!!!! i'm really getting fed up with this. someone has to have a solution to this cuz this is really pissing me off.
I am having a huge issue with my phone. I have been flashing custom roms for the past few years and this is the first time I have ever ran into a issue like this. I flashed SlimRom 4.3 build 2 a couple weeks back, it was taking forever to switch between 3g and LTE sometimes up to 5 mins to lock. Not to mention the signal was super low. I ignored it for the most part as it is a newer rom and figured it was just a bug and would hold off for now till kitkat released.
Then my phone would just start random rebooting about once or twice a day. Then on my way home from work i was bluetoothed to my vehicle when it did a random reboot. After that Ive been stuck in 1xRTT since. I also managed to loose my IMEI and PRL version they are both set at 0 and I do not have a backup. Has anyone else ever had this issue? I don't have a clue how to get it working again. My phone is out of warranty I am in the midst of flashing it back to stock to see if that works. Ive searched for hours trying to find a fix. Thanks.
Reverted back to stock.still no luck. Also play store won't work. No connection wirh retry button even while connected to wifi
What firmware/radio do you have? If you've been on custom roms a while you might need to update your radio baseband (most current is VRBMF1). You can flash an updated radio without regard for the Rom you're using.
Sent from my SCH-I535 using xda app-developers app
---------- Post added at 10:29 AM ---------- Previous post was at 10:25 AM ----------
The imei thing is a separate issue. I lost mine without a backup when I first started flashing roms... I think it was cM at the time. I ended up going all the way back to an early stock image, grabbing the OTA updates and then rooting and flashing all over again. I don't know what part in particular got me my imei back.
Sent from my SCH-I535 using xda app-developers app
Do you mean a backup of efs partition or a nandroid? There is a thread at rootzwiki about recovering your imei-efs items. When u get it back do
Su
Reboot nvbackup
In a terminal then you wont have to worry about this again. If you have a nandroid restore it and you'll b good.
Yes my efs folder was completely empty. I reverted back to stock 4.0.4 still had a "0" for IMEI so i used QPST and entered in the IMEI manually and it stuck. I have signal back now. I just got factory mode off. Now my phone is stuck on "Activating", a factory reset should fix that. So this is resolved. Thanks for the help.
quicksilv312 said:
Yes my efs folder was completely empty. I reverted back to stock 4.0.4 still had a "0" for IMEI so i used QPST and entered in the IMEI manually and it stuck. I have signal back now. I just got factory mode off. Now my phone is stuck on "Activating", a factory reset should fix that. So this is resolved. Thanks for the help.
Click to expand...
Click to collapse
Is this the fix to get everything up and running again (flash back to ICS)? I was about to start my own thread until I read this. I lost my IMEI, ERI and MEID but didn't back it up first (I know I know ... boo). I manually input my IMEI using QPST like you did and was also able to fix my ERI and MEID and now I have data and text, but still no voice connection. I've flashed a stock (rooted) ROM and tried the reprovision code *2767*3855# and the RTN codes ##786# & ##72786# but nothing happens (I've seen in other forums this only works in ICS and not JB). Last night I downloaded a stock unrooted JB ROM (4.1.2) and ICS ROM (4.0.4) and am planning to ODIN back to stock and complete a factory reset to see if it will kick the gears back in motion again.
I'm not meaning to hi-jack this thread but confirm this is the solution to completing a non-backed-up IMEI/ERI/MEID fix.
-Edit-
There are tons of threads out there starting with "I've lost signal, what happened?" and ending with "I'll report back and let you know what I've found." or "Verizon replaced it for me." but none offer a viable user solution. I'd love to see the answer posted so other searchers out there can find help.
I can confirm everything you did will restore your IMEI/ERI and connectivity. I did all the steps you did (manually input IMEI and use the utility to repair ERI and MEID), then reverted back to unrooted stock using odin. I still didn't have signal until I did a factory restet IN THE ROM. Going back to stock using odin and doing a factory reset in CWM didn't fix the issue, but going into the phone's settings and completing a factory reset from there caused my signal and connection to come back.
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.