[HELP!] Phone requesting SIM Unlock PIN after a flash?
Installed SlimKat and then swapped to CM11 on the Mrs' S4 Mini a while back because it started acting up, then CM11 one day just rebooted her phone and wouldn't let it boot (stuck in a boot cycle) so I decided to wipe the phone and pop on a stock firmware from Sammobile.com. All went fine flashing with ODIN, however now whenever the phone boots up it is asking for a SIM Unlock PIN - the phone is on Tesco Mobile and worked fine with the original Samsung firmware on and the other ROMS but now when i've come to put these what I thought were stock ROMs on it is asking for a SIM Unlock Pin and wont recognise the sim card for some reason.
All of the firmwares ive tried from SAMMOBILE have been UK ones for O2, EE and another carrier. My thinking was that O2 would work but it didnt and neither did any of the others. Whats caused the phone to do this blocking of the SIM? Anyone any ideas? Is there anything I can do to get the phone back up and running? Hope it isn't borked as she will be less than happy haha!
Have you tried installing a custom rom again? Maybe straight CM11 not slim kat as that rom is outdated compared to standard straight CM11.
---------- Post added at 12:59 AM ---------- Previous post was at 12:52 AM ----------
RuffBuster said:
Have you tried installing a custom rom again? Maybe straight CM11 not slim kat as that rom is outdated compared to standard straight CM11.
Click to expand...
Click to collapse
Have you tried the BTU firmware from sammobile? I know this is firmware for factory unlocked phones. What model of S4 Mini you using?
Also once you get the right firmware try flashing a couple of times, 2 or 3 times over. Turn auto reboot off on Odin. And then before it boots get into stock recovery and wipe data and cache before first boot.
These are just ideas...
But before all of the above .. Have you tried wiping data and cache from recovery a first resort? Just an idea.
---------- Post added at 01:02 AM ---------- Previous post was at 12:59 AM ----------
Hope you get it going again, don't want the missus carving you a new one. I wouldn't dare touch my girls phones cus my life wouldn't be worth it lol.
In future you MUST make NANDROID backups and copy the EFS folder of the root directory as soon as humanly possible. I know it's too late now but it's a must with any future phone.
RuffBuster said:
Have you tried installing a custom rom again? Maybe straight CM11 not slim kat as that rom is outdated compared to standard straight CM11.
---------- Post added at 12:59 AM ---------- Previous post was at 12:52 AM ----------
Have you tried the BTU firmware from sammobile? I know this is firmware for factory unlocked phones. What model of S4 Mini you using?
Also once you get the right firmware try flashing a couple of times, 2 or 3 times over. Turn auto reboot off on Odin. And then before it boots get into stock recovery and wipe data and cache before first boot.
These are just ideas...
But before all of the above .. Have you tried wiping data and cache from recovery a first resort? Just an idea.
---------- Post added at 01:02 AM ---------- Previous post was at 12:59 AM ----------
Hope you get it going again, don't want the missus carving you a new one. I wouldn't dare touch my girls phones cus my life wouldn't be worth it lol.
In future you MUST make NANDROID backups and copy the EFS folder of the root directory as soon as humanly possible. I know it's too late now but it's a must with any future phone.
Click to expand...
Click to collapse
Nope not bothered putting a custom ROM again, just wanted to get it back to fresh. Its weird though as I used to CWM recovery on but now that doesnt work and it just looks like the regular samsung/android recovery when I go into it at boot.
I'll try the BTU firmware off Sammobile and report back, shes just got a plain old i9195 UK version, nothing fancy! I always boot into recovery delete the cache and then do a factory reset then go to reboot the phone and reboot into download mode to flash the new firmware. Have tried it different ways though of flashing first then clearing cache etc but still the same. Really doing my head in now! Never had this problem when flashing phones before!!!!
Related
i am trying to keep myself from pulling my hair out so i am turning to the great xda. im a long time lurker with only a few posts because i usually take every step to insure the problem is not because of my mistake.
but recently i have ran into a problem i cannot solve. i recently upgraded to 4.3 and tried the illusion and pa3+ roms. everything worked until i realized i lost root (which is needed for the xposed installer). so i looked it up and fixed it. after i got rooted i lost all mobile data. i flashed illusion again and got data again until i rooted my phone. so then i figured, ok i'll go back to 4.2.2. no cigar. still no data.
so i figured i would have to start fresh.i flashed mc2 stock via odin, rooted, custom recovery, etc. with the toolkit and then tried multiple aosp 4.2.2 based roms and still no data. but when i flash a 4.1.2 tw base everything works again.
im guessing 4.3 changed something internally permanently. i have used triangle away, odin, and always wipe everything twice and format data in between roms.
is there something else im missing? this is the second time this happened. ended up having to turn the phone in and get a new one already.
so what im asking is is there anything i can do that goes beyond odin and triangle away to perform sort of like an "ultimate stock flash" i can use to where it like i got it from the store? just odin and triangle away don't work.
Don't know if this would help.
HTML:
http://androidromupdate.com/2012/11/13/l900vpalj1-sprint-galaxy-note-2-original-jelly-bean-factory-stock-rom/
I used it trying to get my WIFI to work (it didn't help) and then let sprint update the phone to the lastest version.
---------- Post added at 05:11 PM ---------- Previous post was at 05:05 PM ----------
mightybhwk said:
Don't know if this would help.
HTML:
http://androidromupdate.com/2012/11/13/l900vpalj1-sprint-galaxy-note-2-original-jelly-bean-factory-stock-rom/
I used it trying to get my WIFI to work (it didn't help) and then let sprint update the phone to the lastest version.
Click to expand...
Click to collapse
Sorry hit the wrong button. Here is the link.
http://androidromupdate.com/2012/11/13/l900vpalj1-sprint-galaxy-note-2-original-jelly-bean-factory-stock-rom/
if you made a nandroid back up, check to see if you backed up your efs partition. you may be able to restore it.
So my phone is stuck in bootloop. and I cant get my phone to boot correctly.
To start, I was running 4.2.2 AOKP for about half a year and it started to not work as well. Force closing alot, freezing etc. So I decided it was time to update. While I was running AOKP, I experienced bootloop almost every time I turned off my phone. This became regular, but by pulling the battery and trying again (sometimes I had to do with a few times) it always got working again.
I went and found the new 4.3 Carbon ROM and decided that looked cool and would be a nice upgrade. So I downloaded it and the new 4.3 gapps. Put them on an external sd card, and put it into my phone. I then booted into CWM and did a factory reset. Then I went and installed the Carbon from the external sd, installed gapps, and rebooted immediately. I was then, and still am, stuck in a bootloop.
I can restart my phone go back into clockwork.
But I cant get the phone, despite all my efforts, to boot correctly. I have tried to wipe caches, wipe dalvik, format system. All of it. yet I cannot boot correctly.
I really need a working phone. Any help would be really great.
Thanks all
Also, I am using TWRP 2.6.3 to do the flash of the Carbon after it failed the first time
Moheemo said:
Also, I am using TWRP 2.6.3 to do the flash of the Carbon after it failed the first time
Click to expand...
Click to collapse
2.6.3.0 seems to be giving many people issues. You need to install 2.6.1.0.
And is your radio up to date? Only 2 work...the new T-Mobile and Telus radios.
After those 2 things are taken care of, you should be fine. Tho lots of things can cause boot loops, and there's many.. many posts about it. If my suggestions don't help.....Search and read up. Try some various fixes.
Maybe try a different rom too.
Sent from my cellular telephone
---------- Post added at 03:09 PM ---------- Previous post was at 03:06 PM ----------
Hope you did a nandroid backup in recovery? Restore it if so. If not, you may need to start from scratch and Odin flash stock rom, flash recovery and root again.
Sent from my cellular telephone
Moheemo said:
So my phone is stuck in bootloop. and I cant get my phone to boot correctly.
To start, I was running 4.2.2 AOKP for about half a year and it started to not work as well. Force closing alot, freezing etc. So I decided it was time to update. While I was running AOKP, I experienced bootloop almost every time I turned off my phone. This became regular, but by pulling the battery and trying again (sometimes I had to do with a few times) it always got working again.
I went and found the new 4.3 Carbon ROM and decided that looked cool and would be a nice upgrade. So I downloaded it and the new 4.3 gapps. Put them on an external sd card, and put it into my phone. I then booted into CWM and did a factory reset. Then I went and installed the Carbon from the external sd, installed gapps, and rebooted immediately. I was then, and still am, stuck in a bootloop.
I can restart my phone go back into clockwork.
But I cant get the phone, despite all my efforts, to boot correctly. I have tried to wipe caches, wipe dalvik, format system. All of it. yet I cannot boot correctly.
I really need a working phone. Any help would be really great.
Thanks all
Click to expand...
Click to collapse
flash stock rom zip via odin then you should be good to root and try to flash another custom rom again:good:
So I'm not 100% sure what happened to tell you the truth. I rooted without issues.. flashed a ROM.. still no issues.. Went to switch ROMs, wiped all cache, and than my phone was getting FC on EVERYTHING...
I decided I'd try and unroot and reroot.. but I'm stuck. I can now get into my phone without FC's.. but still no signal or Wifi. During this process of freaking out... I tried to relock my bootloader. so it now says "relocked." I can get into recovery to flash a different ROM.. but I'm getting an error about permission.. I'm assuming because the bootloader is locked...
I'm completely stuck... hopefully someone is able to lend a hand. My main machine is a Mac... but I do have access to a Windows if need be.
Any help would be appreciated as I'm now back to using my iPhone
Thanks!
Anyone?
I'd be willing to pay at this point.
Try wiping everything
skinney said:
So I'm not 100% sure what happened to tell you the truth. I rooted without issues.. flashed a ROM.. still no issues.. Went to switch ROMs, wiped all cache, and than my phone was getting FC on EVERYTHING...
I decided I'd try and unroot and reroot.. but I'm stuck. I can now get into my phone without FC's.. but still no signal or Wifi. During this process of freaking out... I tried to relock my bootloader. so it now says "relocked." I can get into recovery to flash a different ROM.. but I'm getting an error about permission.. I'm assuming because the bootloader is locked...
I'm completely stuck... hopefully someone is able to lend a hand. My main machine is a Mac... but I do have access to a Windows if need be.
Any help would be appreciated as I'm now back to using my iPhone
Thanks!
Click to expand...
Click to collapse
It sounds like you just need to do a full wipe instead of only wiping out the cache and dalvik.
Anytime you switch rom's, you will want to do a full wipe of cache, dalvik, data, and system. You don't need to wipe your sdcard though, in case you were worried about anything saved on there.
I tried a full wipe as well..
But since I'm "relocked" for the bootloader.. I can't even reflash a ROM..
And I can't unlock it since I'm not on a stock rom
I worked with her one this via LogMeIn last night. I have a TMo HTC One rooted and SOFF, plus ive been in this for over 4 years now, so I have a lot of knowledge here.
Basically, she ran the exploit, but forgot to nandroid before flashing a rom, and i think the rom zip was corrupt. So if anyone has a VZW nandroid stock backup, this is worth a shot in restoring her phone. She has the TWRP installed, but cant flash a new ROM or even stock ROM because she gets an error message. Since her bootloader says Relocked, we think this is why the ROMs wont flash.
I tried to install the Rom.zip via RUU mode, and she gets a different error message than the thread to follow the guide to restore. Once again, i dont know the error off hand, but i can have her post it if necessary once she gets home from work. The Rom.zip's MD5 matches, so its completely good, just wont flash. The phone goes into bootloader and fastboot and recovery all fine. It boots into the phone, but she cannot access her Wifi or Mobile Networks. She said she might have ADB access though.
I told her to try to rerun the SOFF exploit, but it failed. I only assisted her via LMI and SMS messaging, but her phone does work outside of the OS. I had her try HTCdev for the hell of it and it doesnt work.
I dont know if a nandroid backup would work because of the fact that her bootloader is "Relocked" now, but its worth a shot. If she can restore the stock rooted system image and data, shell be fine. The kernel works, the bootloader and recovery work. Fastboot commands work as weel. So i think if someone would be nice enough to upload the nandroid for her, it could resolve her problem.
If she has ADB access, then i dont see why doing the current method to return to stock wouldnt work since that method uses ADB to relock it or whatever that command is.
Just trying to assist my friend,
So it's "re-locked" - is it still S-Off?
Have you tried the decrypted RUU ?
---------- Post added at 06:39 PM ---------- Previous post was at 06:31 PM ----------
Actually, also check this thread (it's still short! ) - looks like you might be able to get it to show the bootloader as unlocked again - at which point (I think, anyway, based on my reading so far) you could run the RUU and that should get you back to normal...
jntdroid said:
So it's "re-locked" - is it still S-Off?
Have you tried the decrypted RUU ?
---------- Post added at 06:39 PM ---------- Previous post was at 06:31 PM ----------
Actually, also check this thread (it's still short! ) - looks like you might be able to get it to show the bootloader as unlocked again - at which point (I think, anyway, based on my reading so far) you could run the RUU and that should get you back to normal...
Click to expand...
Click to collapse
I appreciate the help.. I did get my bootloader to go from "relocked" to lock.. and tried the "return to stock" post... but I get this error..
Sarah--MacBook-Pro:desktop sarahx1224$ cd root
Sarah--MacBook-Pro:root sarahx1224$ ./fastboot-mac flash zip Rom.zip
ERROR: could not clear input pipe; result -536854447< waiting for device >
Since shes now Locked again and S-ON, Im going to walk her through flashing the system.img file via fastboot. As long as we can restore her system we should be good here.
Last night, we tried but the md5 of the raw system.img file did not match. After downloading it again, the md5 still did not match, but weirdly enough, it was the same md5 as the first download.
When she gets off of work, we will try again to flash via fastboot.
Sent from my HTC One using XDA Premium 4 mobile app
First off, sorry if this was answered before, I searched but there is little info to be found about the D852 in particular.
The phone is from Fido, which should be the same as Rogers since they are the same company. The original firmware was 20c, Lollipop 5.0.1. The phone is currently running TWRP 2.8.7.0 and CM12.1 nightlies.
The main issue is when I power off either in System or Recovery, SOMETIMES it will not power back on without pulling the battery. The odd thing is the randomness of it, I cannot figure out a pattern.
I also tried the CM recovery that ships with the CM nightlies. I tried several revisions of those CM nightlies. I tried several TWRP revisions as well. Same power off/on issue, which brings be to believe this may be a bootloader issue.
Any ideas what I should try next? I could try reflashing the original software that came with the phone, but I'd like that to be a last resort. I spent far too much time rooting, flashing TWRP and CM to revert.
Thanks for reading.
Mine did this too (D852G from videotron) You should try to flash the bootstack, that's what I did and now it boot everytime!
svcr0c0 said:
First off, sorry if this was answered before, I searched but there is little info to be found about the D852 in particular.
The phone is from Fido, which should be the same as Rogers since they are the same company. The original firmware was 20c, Lollipop 5.0.1. The phone is currently running TWRP 2.8.7.0 and CM12.1 nightlies.
The main issue is when I power off either in System or Recovery, SOMETIMES it will not power back on without pulling the battery. The odd thing is the randomness of it, I cannot figure out a pattern.
I also tried the CM recovery that ships with the CM nightlies. I tried several revisions of those CM nightlies. I tried several TWRP revisions as well. Same power off/on issue, which brings be to believe this may be a bootloader issue.
Any ideas what I should try next? I could try reflashing the original software that came with the phone, but I'd like that to be a last resort. I spent far too much time rooting, flashing TWRP and CM to revert.
Thanks for reading.
Click to expand...
Click to collapse
I have a D852 as well. How are you finding CM? Stable for daily use?
---------- Post added at 02:21 PM ---------- Previous post was at 02:20 PM ----------
RapHaeL_4_4_4_ said:
Mine did this too (D852G from videotron) You should try to flash the bootstack, that's what I did and now it boot everytime!
Click to expand...
Click to collapse
I have this issue on my D852 as well. What is bootstacl?
Thanks. I will look into it. A silly question, but do I have the D852 or D852g? My phone reports D852, so that is the TWRP I flashed Also, which bootstack do you recommend?
The CM12.1 very usable, at least over the past two days since I got the phone. No system crashes yet, although Firefox did restart once. I also use Open Camera over the stock CM one, and there is a long delay before the first picture is taken. There also seems to be a microphone issue, one person complained when I held the phone too far from my face. I am spoiled, coming from a Nexus 4 which has the best support possible. And even it had some quirks.
oxxshadow said:
I have a D852 as well. How are you finding CM? Stable for daily use?
---------- Post added at 02:21 PM ---------- Previous post was at 02:20 PM ----------
I have this issue on my D852 as well. What is bootstacl?
Click to expand...
Click to collapse
1- I don't use cm12.1, I had exodus rom for a month and its amazing (I prefer AOSP based rom), but it came back to the stock because of the vibration strength (feels weak on the custom rom not based on stock)
2- A bootstack is multiple file that tell your device how to boot
---------- Post added at 03:29 PM ---------- Previous post was at 03:27 PM ----------
svcr0c0 said:
Thanks. I will look into it. A silly question, but do I have the D852 or D852g? My phone reports D852, so that is the TWRP I flashed Also, which bootstack do you recommend?
The CM12.1 very usable, at least over the past two days since I got the phone. No system crashes yet, although Firefox did restart once. I also use Open Camera over the stock CM one, and there is a long delay before the first picture is taken. There also seems to be a microphone issue, one person complained when I held the phone too far from my face. I am spoiled, coming from a Nexus 4 which has the best support possible. And even it had some quirks.
Click to expand...
Click to collapse
D852G is only with videotron and a bootstack is not a rom! Its multiple file that tell your device how to boot.
I'll try to find one for D852, I will post here when I find it.
So I did some looking around and I cannot figure out which boot loader to flash. I don't want to risk trying out untested bootloaders as they may revert the vulnerability or brick the phone.
Any suggestions would be highly appreciated. Thanks.
Bumping for lack of answers.
So far CM12.1 has been very decent. I'd like to use a different camera app, and cool reader is crashing very often, but overall I am sticking with it. No overheating, and great battery life.
svcr0c0 said:
Bumping for lack of answers.
So far CM12.1 has been very decent. I'd like to use a different camera app, and cool reader is crashing very often, but overall I am sticking with it. No overheating, and great battery life.
Click to expand...
Click to collapse
were you able to find a solution to the booting issue?
Not yet. I have not seen any new releases for the d852, at least not in a few quick searches. I just don't want to take risks in bricking a working device. At the moment I am simply never powering down my G3. Reboot straight into recovery, then back into system once the CM update flashes.
Lesson learned, I will never buy a non-nexus device, or at least a device that is not factory unlockable. Jumping through hoops to get access to the hardware you own is a silly endeavour.
I tried the following and it seems working:
1. My goal is to be able to flash Lollipop modem, once I flash Dene's modem, I got into battery pull problem.
2. I started looking at boot stack.
3. I noticed Dene's modem extraction includes 2 extra files: rpm.img and tz.img.
4. I removed them from Dene's zip and flash the modem file only.
5. I was on KK modem on AOSP rom, lollipop modem working.
Not sure will it work on Dene's rom, need to try.
kenship said:
I tried the following and it seems working:
1. My goal is to be able to flash Lollipop modem, once I flash Dene's modem, I got into battery pull problem.
2. I started looking at boot stack.
3. I noticed Dene's modem extraction includes 2 extra files: rpm.img and tz.img.
4. I removed them from Dene's zip and flash the modem file only.
5. I was on KK modem on AOSP rom, lollipop modem working.
Not sure will it work on Dene's rom, need to try.
Click to expand...
Click to collapse
I found if you update to stock lollipop then root and install TWRP I don't have battery pull issue with any custom rom.
Currently running Dene's 21A test build with no issues.
DAE1964 said:
I found if you update to stock lollipop then root and install TWRP I don't have battery pull issue with any custom rom.
Currently running Dene's 21A test build with no issues.
Click to expand...
Click to collapse
Unfortunately I did that a couple times using Autorec, Imageprep, none worked. Are you using any one of the above to flash TWRP?
I don't recall how I got TWRP installed. I did a flash upgrade to v2.8.7.0 though. Sorry I can't be more helpful.
So my uncle's Verizon Note 8 running well on TracFone had not gotten an update since it was purchased new. It was running the software it originally shipped with.
I put my Verizon sim in it and was able to update it to current software.
After doing all this his phone will not run properly on TracFone. Data is very slow. I'm trying to figure out what happened and if it is fixable....? TIA
I would first try going into the System Recovery and wipe the cache. Reboot the phone and see if that helps. If not, there is a chance that you may have to do a factory reset. If you use Samsung SmartSwitch, you can back up practically everything to the SD card and be able to restore it.
---------- Post added at 01:31 ---------- Previous post was at 01:17 ----------
It's also possible that the APN settings may have been changed when you put your Verizon SIM card in it. Check the APN settings to make sure they are correct: https://bestmvno.com/apn-settings/page-plus-cellular-apn-settings/
mikeyk101 said:
I would first try going into the System Recovery and wipe the cache. Reboot the phone and see if that helps. If not, there is a chance that you may have to do a factory reset. If you use Samsung SmartSwitch, you can back up practically everything to the SD card and be able to restore it.
---------- Post added at 01:31 ---------- Previous post was at 01:17 ----------
It's also possible that the APN settings may have been changed when you put your Verizon SIM card in it. Check the APN settings to make sure they are correct: https://bestmvno.com/apn-settings/page-plus-cellular-apn-settings/
Click to expand...
Click to collapse
Thanks for responding. I've tried all these things and no luck at all.