My phone got stuck in bootlop after updating the march 2019 security patch. I had to get new phone as Amazon replaced it . Please don't update the new security patch it will kill your phone and there is no support to it from the company. To avoid getting stuck switch on the OEM UNLOCKING IN DEVELOPER OPTIONS so you can flash a new rom if you ever get stuck .
Hope it was helpful.
If anyone getting the same issue please tell me the fix for the same.
You should have remove the sim tray, so as they say before updating.
shizuni said:
You should have remove the sim tray, so as they say before updating.
Click to expand...
Click to collapse
I tried that too it doesn't work. And after using the oem unlocking i was able to flash an official rom .
__adiimathur said:
I tried that too it doesn't work. And after using the oem unlocking i was able to flash an official rom .
Click to expand...
Click to collapse
Just to clarify, u didnt put back the sim tray after update and then restarting right?
No my sim tray was ejected .
__adiimathur said:
No my sim tray was ejected .
Click to expand...
Click to collapse
Ejected before installation untill restart?
shizuni said:
Ejected before installation untill restart?
Click to expand...
Click to collapse
I got my new mi a2 and i havent updated the device yet can you pls help me out wht to do? i really wanna update to get this over with.
__adiimathur said:
I got my new mi a2 and i havent updated the device yet can you pls help me out wht to do? i really wanna update to get this over with.
Click to expand...
Click to collapse
If u have wifi, remove the sim tray before updating, and remain removed during installing and dont put it back untill full restart
Pls don't put back the sim tray if it is during the boot sequence when u restart, it will boot loop during March security update.
I finally successfully updated my phone without any bootloop. The only way to do it is to remove the sim tray as mentioned before while updating.
Steps for updating successfully.
1. REMOVE YOUR SIM TRAY.
2. Connect to wifi.
3. Download the security upadte.
4. DO NOT INSERT THE SIM TRAY UNTIL AND UNLESS THE UPDATE PROCESS IS COMPLETE.
Once the phone is updated successfully, you are free to insert your sim tray back in and from now on there will be no problem in installing any future updates.
Related
I'm using the Paranoid Android Final 4.41 Version on my SGS+
When I start the build in encryption, which encrypts the data partition the GSM Modem isn't working after the encryption process came to success.
I reproduced this twice. The phone doesn't detect the SIM Card anymore.
I'd like to post this as a bug report in the right SGS+ AP Developer Thread, but I'm not allowed to do so, because I'm a new user.
Maybe someone reading this here can answer this?
No expert available, regarding this topic?
Is your phone SIM-locked?
No SIM-Lock.
guitarhead said:
No SIM-Lock.
Click to expand...
Click to collapse
What does it say under Baseband version?
I9001xxkph
Did you try with a different SIM?
Unfortunately I don't have another card. But thanx for your help. I've given up. Instead I'll protect my phone with a roundhousekick!
What does this mean? It is definitely not locked to the phone. Bought separately.
guitarhead said:
What does this mean? It is definitely not locked to the phone. Bought separately.
Click to expand...
Click to collapse
It means that your device works only with one carrier.
To see if your device is locked try a SIM card from a different operator. If it doesn't work then your device is locked.
If you want to unlock it read this.
Thanks for your description. It is definitely not locked. The phone was bought with no Sim Card and the card was bought separately. Other carriers are working.
Any other opinions?
guitarhead said:
Thanks for your description. It is definitely not locked. The phone was bought with no Sim Card and the card was bought separately. Other carriers are working.
Any other opinions?
Click to expand...
Click to collapse
Did you remove the SIM card before encryption?
Also are you using a SIM PIN?
Tried both: left in and remove. I am using a Sim Pin
Hey,
I was running Android P Beta, and had an OTA update today.
As it's been said on the beta topic, it apparently put me back on Oreo (the pattern lock is different on P).
But now I can't unlock the phone with the pattern at boot. When I put it the right pattern, it gives me a black screen, and ask me to unlock again.
So nothing's coming up, no wifi, no backup etc.
Does anyone have an idea on how to solve this **** ?
Thanks guys.
Deeptwix said:
Hey,
I was running Android P Beta, and had an OTA update today.
As it's been said on the beta topic, it apparently put me back on Oreo (the pattern lock is different on P).
But now I can't unlock the phone with the pattern at boot. When I put it the right pattern, it gives me a black screen, and ask me to unlock again.
So nothing's coming up, no wifi, no backup etc.
Does anyone have an idea on how to solve this **** ?
Thanks guys.
Click to expand...
Click to collapse
Boot to Recovery mode. Wipe/factory reset and reboot system.
koschey_immortal said:
Boot to Recovery mode. Wipe/factory reset and reboot system.
Click to expand...
Click to collapse
Thanks for your answer.
I know I could do that, but I'd like to be able to get some data back first (like whatsapp messages).
Whichi is why I'm trying to find a workaround, but so far it's not really a success.
have you tried android unlock my phone method?
Go to google and sign in. Then go to find/locate my device and then check the option unlock my phone. It will help surely.
Styleshman said:
have you tried android unlock my phone method?
Go to google and sign in. Then go to find/locate my device and then check the option unlock my phone. It will help surely.
Click to expand...
Click to collapse
i think that OTA update on Android P is in real "Android 0 8.1 June Update", as mentioned here, if this true that's the reason why you have problems
Hello friends, i have Sm-n950f device. Yesterday, i tried to root my device. I successfully installed TWRP recovery but afterwards, i got error that only official binary allowed to be installed and i was stuck on samsung logo. Then with odin i install official firmware again and i found oem unlock missing. I tried some methods to get it back by setting up date 8 days back but nothing happen. Now my device have 1 july security pacth and its again showing update for august patch. What should i do??
Thanks
cheemak said:
Hello friends, i have Sm-n950f device. Yesterday, i tried to root my device. I successfully installed TWRP recovery but afterwards, i got error that only official binary allowed to be installed and i was stuck on samsung logo. Then with odin i install official firmware again and i found oem unlock missing. I tried some methods to get it back by setting up date 8 days back but nothing happen. Now my device have 1 july security pacth and its again showing update for august patch. What should i do??
Thanks
Click to expand...
Click to collapse
Maybe try this and see if it works for you
https://forum.xda-developers.com/galaxy-note-8/how-to/oem-unlock-quick-fix-highly-recommend-t3791984
I tried these steps whole day but it did not work for me.,,, any other suggestion please?
thanks for your reply
cheemak said:
Hello friends, i have Sm-n950f device. Yesterday, i tried to root my device. I successfully installed TWRP recovery but afterwards, i got error that only official binary allowed to be installed and i was stuck on samsung logo. Then with odin i install official firmware again and i found oem unlock missing. I tried some methods to get it back by setting up date 8 days back but nothing happen. Now my device have 1 july security pacth and its again showing update for august patch. What should i do??
Thanks
Click to expand...
Click to collapse
If the workaround to bring back the oem unlock toggle isn't working, then you will have to wait the 7 days for it to appear. Then you can toggle it and try installing twrp again. You likely missed a step in the process last time which resulted in 'jail'.
cheemak said:
I tried these steps whole day but it did not work for me.,,, any other suggestion please?
thanks for your reply
Click to expand...
Click to collapse
You could try my method here - https://forum.xda-developers.com/showpost.php?p=76962872&postcount=28
I tried this method as well but without sim card and it didn't work,,, is sim card important to insert? Now my device running time is about 20 hours so I don't want to restart my device if I restarted then it again come back to 0. What should I do not getting??
indercheema14 said:
I tried this method as well but without sim card and it didn't work,,, is sim card important to insert? Now my device running time is about 20 hours so I don't want to restart my device if I restarted then it again come back to 0. What should I do not getting??
Click to expand...
Click to collapse
Reboots don't affect the 7 day timer. Your uptime timer will reset, but the 7 day timer for OEM unlock is server-side.
sefrcoko said:
Reboots don't affect the 7 day timer. Your uptime timer will reset, but the 7 day timer for OEM unlock is server-side.
Click to expand...
Click to collapse
Ok thank you for information,, i am getting OTA update for august security patch,, should i install this update or not? i want to root my device and install custom rom but still waiting for oem button to appear in developer option? what you suggest?
cheemak said:
Ok thank you for information,, i am getting OTA update for august security patch,, should i install this update or not? i want to root my device and install custom rom but still waiting for oem button to appear in developer option? what you suggest?
Click to expand...
Click to collapse
I'm not sure but I think that installing the update could restart the 7-day wait period. If you want to root as fast as possible then it's probably safer to not install the update for now and just wait for the OEM Unlock toggle to appear. There is also a stick thread here with a workaround to skip the 7 day waiting period, but it didn't seem to work for everyone (although it did work for me the one time I tried it).
Any luck///need help too.
Any luck with getting the OEM to show?
I've tried them all waiting 7 to 2 weeks, factory reset change date at setting up insert sim card and no luck. I got my note 8 at soon as it came out so maybe it has something to do with it? I want to root it so bad it cant because of no OEM. Any new information would be great!
dandel0074 said:
Any luck with getting the OEM to show?
I've tried them all waiting 7 to 2 weeks, factory reset change date at setting up insert sim card and no luck. I got my note 8 at soon as it came out so maybe it has something to do with it? I want to root it so bad it cant because of no OEM. Any new information would be great!
Click to expand...
Click to collapse
What model do you have? What's your csc?
sefrcoko said:
What model do you have? What's your csc?
Click to expand...
Click to collapse
Damn, sorry I thought I listed it. I have a t mobile note 8 where the OEM wont show up and a unlocked note 9 N9600 where the OEM is grayed out to which I tried Odin flashing N9600 CPT/TCP version (not to sure right early this moment) and the flash passed but the phone was exactly the same without any changes and still the OEM was grayed out. I tried 3 different methods of changing dates on both phones with no luck. Any kind of new information or version ti they and get this OEM to work for me would be greatly appreciated.
dandel0074 said:
Damn, sorry I thought I listed it. I have a t mobile note 8 where the OEM wont show up and a unlocked note 9 N9600 where the OEM is grayed out to which I tried Odin flashing N9600 CPT/TCP version (not to sure right early this moment) and the flash passed but the phone was exactly the same without any changes and still the OEM was grayed out. I tried 3 different methods of changing dates on both phones with no luck. Any kind of new information or version ti they and get this OEM to work for me would be greatly appreciated.
Click to expand...
Click to collapse
Ok the T-Mobile model has a locked bootloader that can't be unlocked, so OEM unlock won't work.
The N9600's bootloader can be unlocked though. I have tried the date trick in the past on another Note 8 variant and it worked, but I have since read different things such as recent firmware updates stopping the trick, or needing to jump more than 30 days ahead instead of 7 to make it work. Not sure if all that's true or not, but if nothing works then I would probably back things up, flash original firmware through Odin with full wipe and wait 7 days to see if OEM unlock appears.
sefrcoko said:
Ok the T-Mobile model has a locked bootloader that can't be unlocked, so OEM unlock won't work.
The N9600's bootloader can be unlocked though. I have tried the date trick in the past on another Note 8 variant and it worked, but I have since read different things such as recent firmware updates stopping the trick, or needing to jump more than 30 days ahead instead of 7 to make it work. Not sure if all that's true or not, but if nothing works then I would probably back things up, flash original firmware through Odin with full wipe and wait 7 days to see if OEM unlock appears.
Click to expand...
Click to collapse
Yes I know the t mobile bootloader cant be unlocked but still can get be rooted and use some mods with the lost of 20% battery lose but one has to get OEM unlocked under developers options (that option never shows up for me) I've tried 7 to 14 day without reboot but not 30. I've give that a try on the note 8.
As for the note 9 N9600, I thought it came unlocked already but still just need the OEM unlock switched, which for me is grayed out and cant be switched. I'll use factory reset on both and try the 30 days trick instead of 7 and see if itll work.
Thanks for the info.
dandel0074 said:
Yes I know the t mobile bootloader cant be unlocked but still can get be rooted and use some mods with the lost of 20% battery lose but one has to get OEM unlocked under developers options (that option never shows up for me) I've tried 7 to 14 day without reboot but not 30. I've give that a try on the note 8.
As for the note 9 N9600, I thought it came unlocked already but still just need the OEM unlock switched, which for me is grayed out and cant be switched. I'll use factory reset on both and try the 30 days trick instead of 7 and see if itll work.
Thanks for the info.
Click to expand...
Click to collapse
Yeah the samfail method for u.s. snapdragon models was patched by Samsung at one point, but it depends on which version bootloader you currently have installed if I recall correctly. Check through the samfail thread for more info there. I have an exynos, so can't say for sure about n9600 but that's what I would try at this point
sefrcoko said:
Yeah the samfail method for u.s. snapdragon models was patched by Samsung at one point, but it depends on which version bootloader you currently have installed if I recall correctly. Check through the samfail thread for more info there. I have an exynos, so can't say for sure about n9600 but that's what I would try at this point
Click to expand...
Click to collapse
I cant do anything without figuring out how to get OEM unlock to show up on my note and OEM unlock option greyed out removed from my note 9. The only step one found was the tricking the device on changing the date and that didnt work on the note 8 (going to try it for 30 plus days and see if thatll work) as for the note 9,,,,,,, I dont know why it's even grayed out.
dandel0074 said:
I cant do anything without figuring out how to get OEM unlock to show up on my note and OEM unlock option greyed out removed from my note 9. The only step one found was the tricking the device on changing the date and that didnt work on the note 8 (going to try it for 30 plus days and see if thatll work) as for the note 9,,,,,,, I dont know why it's even grayed out.
Click to expand...
Click to collapse
Like I said you won't get it on the T-Mobile model (and iirc it's not needed for samfail, even if you are on the proper bootloader, etc.), but you can always check the 9600 and/or OEM unlock threads for more on that one if the stock flash/wipe and waiting period approach isn't preferred or doesn't work out.
I bought MIA2 in January, global version and update it to pie without problems and then, aI installed the January security update, then I had a bootloop problem, and since it was untouched the only option was warranty or test point. Since I didn't want to lose some pictures, I opened my brand new device, :crying: did the test point, and put the V10.0.2 rom with MiFlash. It worked but I couldn't recover mi pictures.
Now, phone is offering me to install the February security update, and I'm scared to have the same issue again. I have USB debbuging activated and also the option for the OEM unlock activated. But haven't touched anything else.
Should I try to install this update?
Are these options enough to recover the phone if I have a problem or should I do test point again in case of bootloop?
Thanks for your answers!!
marioandresl said:
I have USB debbuging activated and also the option for the OEM unlock activated. But haven't touched anything else.
Should I try to install this update?
Are these options enough to recover the phone if I have a problem or should I do test point again in case of bootloop?
Thanks for your answers!!
Click to expand...
Click to collapse
I have updated with the latest February patch without any issues. My bootloader is also unlocked.
bidhu said:
I have updated with the latest February patch without any issues. My bootloader is also unlocked.
Click to expand...
Click to collapse
Ok guys I just Updated to V10.0.4 Or February update without problems. Thanks!!
Hello, I flashed my mi8 like I do every week.
This week I flashed the xiaomi.eu weekly rom, used it for 10hours, then my phone randomly restarted, and now it don't detect SIM cards and don't turn on WIFI, and the phone restart every X minutes.
I think the persist partition has gone. I can't find it on TWRP.
Any help?
Thank you
eRvY said:
Hello, I flashed my mi8 like I do every week.
This week I flashed the xiaomi.eu weekly rom, used it for 10hours, then my phone randomly restarted, and now it don't detect SIM cards and don't turn on WIFI, and the phone restart every X minutes.
I think the persist partition has gone. I can't find it on TWRP.
Any help?
Thank you
Click to expand...
Click to collapse
Which TWRP did you use?
alone_in_dark said:
Which TWRP did you use?
Click to expand...
Click to collapse
I used the same I ever used, but a very old one? Do you think it's related to twrp?
eRvY said:
I used the same I ever used, but a very old one? Do you think it's related to twrp?
Click to expand...
Click to collapse
Follow his posts:
https://forum.xda-developers.com/search.php?searchid=461808923
Hope it might help you.
eRvY said:
I used the same I ever used, but a very old one? Do you think it's related to twrp?
Click to expand...
Click to collapse
Have you solved your problem? Can you please tell which TWRP were you using specifically?
alone_in_dark said:
Follow his posts:
https://forum.xda-developers.com/search.php?searchid=461808923
Hope it might help you.
Click to expand...
Click to collapse
i cant find that post?
I have the same problem.
Have you tried installing all possible ROMs nothing resoved?
Does anyone have a solution?
Follow this thread:
https://forum.xda-developers.com/mi-8/how-to/how-to-fix-mi8-sensors-t3844551
Which TWRP were you using specifically?
alone_in_dark said:
Follow this thread:
https://forum.xda-developers.com/mi-8/how-to/how-to-fix-mi8-sensors-t3844551
Which TWRP were you using specifically?
Click to expand...
Click to collapse
I'm having the same issues, I'm running the latest official TWRP. The thread you linked won't open.
alone_in_dark said:
Follow this thread:
https://forum.xda-developers.com/mi-8/how-to/how-to-fix-mi8-sensors-t3844551
Which TWRP were you using specifically?
Click to expand...
Click to collapse
Not solved ..
Anyone with a solution ??
Are you guys having the same issues as I?
Phone boot, don't detect SIM or Wifi, and reboot after 3-5mins?
Anyone find the solution?
alone_in_dark said:
Follow this thread:
https://forum.xda-developers.com/mi-8/how-to/how-to-fix-mi8-sensors-t3844551
Which TWRP were you using specifically?
Click to expand...
Click to collapse
eRvY said:
Are you guys having the same issues as I?
Phone boot, don't detect SIM or Wifi, and reboot after 3-5mins?
Anyone find the solution?
Click to expand...
Click to collapse
not yet, and I think it will be difficult,
but so many people with the same problem xiaomi will have to solve ..
Everyone should ask xiaomi support I already made my request I'm waiting for response.
sk3lt said:
not yet, and I think it will be difficult,
but so many people with the same problem xiaomi will have to solve ..
Everyone should ask xiaomi support I already made my request I'm waiting for response.
Click to expand...
Click to collapse
I sent my phone to checked by a professional, because it fell from the couch in the afternoon, and everything is working, no shorts.
Now I was almost 100% that the 19/12/2019 update ****ed my phone.
I already bought a realme x2 , because this is my 2nd xiaomi that die out of nowhere, the last one was a Mi4, random shutted down, and never went back to life.
Is your Mi8 chinese or globa versionl?
Mine is chinese
Same problem (global version). Did you fix It?
Hey guys, im from brazil and have same problem, anybody have a help?
Im trying unlock my fastboot for downgrade rom.
I found a fix, remove SIM card, wait 10 seconds, power off phone, put SIM cards back inside and boot the phone
tmcsword said:
Hey guys, im from brazil and have same problem, anybody have a help?
Im trying unlock my fastboot for downgrade rom.
Click to expand...
Click to collapse
This issue has happened on many phones over the past 5 years, and it can definitely be resolved, it has nothing to do with unlocking anything, it's a encryption problem.
It is possible that when Mi-Cloud attempts to register your sim card, that some sort of security packet is downloaded to the phone for your protection. Ensure that you can sign into your mi_cloud account and locate your device, if using Miui. Also, be sure that you have international texts enabled, they text just once or twice so it doesn't cost more than a few cents.
With all of that being said a persist issue isn't the same thing as a sim card issue, and if you phone will not boot you are well past taking out your sim card. The easiest and fastest solution is to restore your persist partition from a TWRP backup, if you have one.
If that is not an option follow my instructions here: https://forum.xda-developers.com/showpost.php?p=79824537&postcount=2
tsongming said:
This issue has happened on many phones over the past 5 years, and it can definitely be resolved, it has nothing to do with unlocking anything, it's a encryption problem.
It is possible that when Mi-Cloud attempts to register your sim card, that some sort of security packet is downloaded to the phone for your protection. Ensure that you can sign into your mi_cloud account and locate your device, if using Miui. Also, be sure that you have international texts enabled, they text just once or twice so it doesn't cost more than a few cents.
With all of that being said a persist issue isn't the same thing as a sim card issue, and if you phone will not boot you are well past taking out your sim card. The easiest and fastest solution is to restore your persist partition from a TWRP backup, if you have one.
If that is not an option follow my instructions here: https://forum.xda-developers.com/showpost.php?p=79824537&postcount=2
Click to expand...
Click to collapse
Dear look, my fastboot is locked, for install twrp ( do you have some instruction for instal TWRP ? ) I think the bootloader need be unlocked, sure?
Thanks for try help me.
tmcsword said:
Dear look, my fastboot is locked, for install twrp ( do you have some instruction for instal TWRP ? ) I think the bootloader need be unlocked, sure?
Thanks for try help me.
Click to expand...
Click to collapse
If you are meaning that your bootloader is locked then the only option ( if your phone is linked to your MiCloud account) Is to return to a stock rom using Miflash or by downloading a fast boot images rom and using the flash all.bat method. The link that I provided earlier has a fast boot images rom linked.
Clarify whether or not you can access fastboot. If you can in fact access fast boot, and you previously used custom ROMs the instructions for installing TWRP are on the official TWRP website. You simply use ADB to push it yo the recovery partition.
tsongming said:
This issue has happened on many phones over the past 5 years, and it can definitely be resolved, it has nothing to do with unlocking anything, it's a encryption problem.
It is possible that when Mi-Cloud attempts to register your sim card, that some sort of security packet is downloaded to the phone for your protection. Ensure that you can sign into your mi_cloud account and locate your device, if using Miui. Also, be sure that you have international texts enabled, they text just once or twice so it doesn't cost more than a few cents.
With all of that being said a persist issue isn't the same thing as a sim card issue, and if you phone will not boot you are well past taking out your sim card. The easiest and fastest solution is to restore your persist partition from a TWRP backup, if you have one.
If that is not an option follow my instructions here: https://forum.xda-developers.com/showpost.php?p=79824537&postcount=2
Click to expand...
Click to collapse
hey whats up man,I hope u still answers questions I really hope you do because I'm in a dire situation where is my xiaomi mi8 cant connect to my sim card .It all started this year after a use of this phone since 2019 january.After my trip overseas , I got my own national sim card in again after that it occurs the problem at first was not that consistent,sometimes it detects, sometimes its good,after a while I thought that the sim card is loose so I wedged the simcard with a bit of paper,about sometime it works and then it starts to overheat when it doesn't detect the sim card inside and starts to reboot on its own, if I remove my simcard,its all good I can use wifi without overheating,how can I actually solve this problem? i quite believe that mi account /micloud that is causing all of this? whats your opinion on this? Im not an expert at all.Thanks for your time of reading this