Hi,
A few weeks ago I updated my phone with official and since then was unable to flash twrp thanks to the RMM state. I have waited 7 days with my phone on and OEM unlock is still not showing (although I get sometimes random sim card disconnections and need to type my PIN code again).
Latest flashed version using Odin is A520FXXUBCSF1
Thanks in advance
Look at the thread about it by corsicanu.
SnowFuhrer said:
Look at the thread about it by corsicanu.
Click to expand...
Click to collapse
Tried to flash version CRK7 (closest version I could find for my CSC) but it said either that my bootloader couldn't be downgraded or my kernel couldn't be (my current bl is rev 11, kernel 8).
Related
hi
i downgraded the phone from 4.3 to to 4.1.1 using mobile odin but now the baseband is unknown and IMEI Null
how to fix this up , please
Did you downgrade to unlock the phone? This method can't be used to unlock the phone.
the phone does not work with me
audit13 said:
Did you downgrade to unlock the phone? This method can't be used to unlock the phone.
Click to expand...
Click to collapse
No . I don`t , my story with this phone is long, first time the phone has android 4.0.1 , i wanted to upgrade it to 4.3 OTA i just followed the instruction on YouTube how to upgrade
once the operation of upgrading is finished the phone rebooted and no signal nothing appear on lcd no vibration so i thought after searching that phone is hard bricked
what i did then looking for brick image to make phone up and then flash another one , i found my self in trouble unlocked phone became locked i lost everything on phone
baseband and IMEi is null and unknown ,
i bought the phone as unlocked sim phone and now nothing success with me
what i should do to fix this problem?
If you can get into download mode, flash a custom recovery to your phone and then flash an old cm11 ROM to see if you can get the phone booted.
which one to use
audit13 said:
If you can get into download mode, flash a custom recovery to your phone and then flash an old cm11 ROM to see if you can get the phone booted.
Click to expand...
Click to collapse
which is best a custom recovery you advise me to use , i have a lot openrecovery-twrp-2.6.3.1-d2att and CWM-Recovery
finally working but ,
audit13 said:
If you can get into download mode, flash a custom recovery to your phone and then flash an old cm11 ROM to see if you can get the phone booted.
Click to expand...
Click to collapse
dear after a couple of tries , finally i flash the 4.3ucufne4 and successfully flashed and working 100%
but the sim card locked the phone became locked although it was unlocked
how to solve this
Hello guys.
Just few months ago I got an used S3 T999 (T-Mobile). I didn't know so much about how to change the ROM and also root the cellphone, but I found a lot of info in this forum and I learned how to do it. First, I noticed that my S3 had an update available: 4.3 JB (The stock one). When I made the update, few days after I changed the ROM (installing it with the CWM recovery, of course): the CyanogenMod 12.1.1 (http://forum.xda-developers.com/gal.../rom-cyanogenmod-12-t-mobile-samsung-t3055048).
Since that, I've been using that one and I haven't found problems. But really, I thought that I can unlock the cellphone whenever I want with an app that I heard months before I got the cellphone. I tried that one and few more ways but I can't make it... GalaxSim Unlock, Galaxy S Unlock, the code with the phone dialer... Nothing. I've been finding in the whole internet and the only thing I found is: My S3 T999 isn't compatible OR It has to be on 4.1 Stock Version.
When I found that Info I tried to do a downgrade. I were lucky that I didn't brick my S3, because I read about doing a Downgrade when you upgraded your S3 to the 4.3 JB version and the EFS Folder V2 and V1 (about the baseband or whatever). Also I tried to downgrade from the CyanogenMod 12.1 to 4.3 JB and I made it (with that one I tried all ways and I couldn't unlock it. Then I came back to the 12.1.1 CyanogenMod), but I can't make it with an older version and try those ways I said.
If you need more info to make an answer: Yes, I made a backup to the EFS when I made the Upgrade to the CyanogenMod 12.1. YES, my S3 is totally rooted. YES, I installed the correct ROM for my cellphone in all cases (the same model and baseband).
Now (as I said) I have:
- CyanogenMod 12.1.1
- Baseband: T999UVUENC2
About ODIN mode info (I don't know if you need this):
- Warranty Bit: 1
- Bootloader RP SWREV: 1
- Qualcomm SecureBoot: Enable
- Current Binary: Custom
- System Status: Custom
- Product Name: SGH-T999
- Custom Binary Download: Yes (12 counts)
I'll be grateful if you can help me with this. I can't use my network because I'm not T-Mobile User.
Beforehand, thanks.
There is no free method to unlock the phone once you are on the 4.3 bootloader. The phone needs to be using a stock 4.1.1 before you can use the free unlock method.
You will have to get an unlock code and return to a stock dialler in order to enter the unlock code.
audit13 said:
There is no free method to unlock the phone once you are on the 4.3 bootloader. The phone needs to be using a stock 4.1.1 before you can use the free unlock method.
You will have to get an unlock code and return to a stock dialler in order to enter the unlock code.
Click to expand...
Click to collapse
So I have to pay for a code (With the IMEI way) and then install a stock version like 4.3 JB in order to use the dialler?
Correct.
Hi all,
I've searched and searched but haven't been able to find anyone else with the same issue I have with my S9, so i'm hoping somebody might be able to help me out!
Basically i installed twrp and then installed Lineageos with Odin. But after a while decided i wanted to go back to stock (there were a few things i was missing, dolby atmos, the stock camera, wi-fi calling and google pay.)
I downloaded a stock firmware from updato and installed with Odin. I used the BTU version, although my phone would have come with the XEU version as standard. I used the HOME_CSC (not sure if that is important?)
So now my phone has stock firmware and got an OTA update yesterday. But when i go into dev settings OEM unlock is greyed out and says 'Bootloader is already unlocked' and my phone is also uncertified in the play store and failed safetynet.
So i'm hoping to be able to get my phone back to the boot loader locked state and to get it certified and passing safetynet. I've waited 7 days as some people have suggested, phone was up for 170 hours but OEM unlock is the same and phone is still uncertified. My next thought is to install the XEU firmware and see if that makes any difference, but i'm not convinced it will.
Does anyone have any idea on how i can fix this please??
evjohns said:
Hi all,
I've searched and searched but haven't been able to find anyone else with the same issue I have with my S9, so i'm hoping somebody might be able to help me out!
Basically i installed twrp and then installed Lineageos with Odin. But after a while decided i wanted to go back to stock (there were a few things i was missing, dolby atmos, the stock camera, wi-fi calling and google pay.)
I downloaded a stock firmware from updato and installed with Odin. I used the BTU version, although my phone would have come with the XEU version as standard. I used the HOME_CSC (not sure if that is important?)
So now my phone has stock firmware and got an OTA update yesterday. But when i go into dev settings OEM unlock is greyed out and says 'Bootloader is already unlocked' and my phone is also uncertified in the play store and failed safetynet.
So i'm hoping to be able to get my phone back to the boot loader locked state and to get it certified and passing safetynet. I've waited 7 days as some people have suggested, phone was up for 170 hours but OEM unlock is the same and phone is still uncertified. My next thought is to install the XEU firmware and see if that makes any difference, but i'm not convinced it will.
Does anyone have any idea on how i can fix this please??
Click to expand...
Click to collapse
HOME_CSC does not reset the device, CSC does, chances are some of the root stuff / system modified files are still present causing these problems
Factory reset, if that doesn't work, flash again but use CSC this time
*Detection* said:
HOME_CSC does not reset the device, CSC does, chances are some of the root stuff / system modified files are still present causing these problems
Factory reset, if that doesn't work, flash again but use CSC this time
Click to expand...
Click to collapse
Thanks, I'll try that again later. Any idea whether it matters if i use the XEU or BTU firmware?
evjohns said:
Thanks, I'll try that again later. Any idea whether it matters if i use the XEU or BTU firmware?
Click to expand...
Click to collapse
Probably won't be able to switch to BTU if you were originally on XEU, BTU is multiCSC and contains XEU so the phone will default to it's original CSC
The firmware will flash fine, but if you check the CSC it will likely still be on XEU unless you managed to change it when you were custom
*Detection* said:
Probably won't be able to switch to BTU if you were originally on XEU, BTU is multiCSC and contains XEU so the phone will default to it's original CSC
The firmware will flash fine, but if you check the CSC it will likely still be on XEU unless you managed to change it when you were custom
Click to expand...
Click to collapse
Yep you're right, it's still XEU. I'll try a factory reset. I'm hoping the OTA update may have fixed a few things.
Can you lock the bootloader back?
parnunu said:
Can you lock the bootloader back?
Click to expand...
Click to collapse
I did a factory reset, then flashed the stock ROM again and used CSC, but the boot loader is still unlocked. I don't have the option to re-lock it, so seems like maybe you can't
Just in case this helps anyone else, I did a complete reset of the stock ROM using @rifek4 instructions from https://forum.xda-developers.com/galaxy-s7/how-to/guide-onelatest-stock-fw-csc-root-t3702963
But i'm still not able to re-lock the boot loader. So going to leave it now and hope the option comes back after 7 days.
rifek4 said:
https://forum.xda-developers.com/showpost.php?p=76388485&postcount=51
Click to expand...
Click to collapse
Thanks for replying. Do you think that method would help me to re-lock the boot loader?
When I go to the settings the OEM unlock says "boot loader is already unlocked"
Basically all I want to do is get safety net to pass again, and it seems that having an unlocked boot loader makes it fail.
Just in case this helps anyone else.
I downloaded magisk 16.7 beta, 16.6 caused my OS (lineage 15.1) to crash, but 16.7 was fine. I installed universal safety net fix for magisk, beta version. Installation said it failed, but when I rebooted it had worked!
Safety net now passes, device is certified in play store and Google pay is working fine. As @rifek4 said, bootloader lock has nothing to do with safety net (although I've seen a lot of people claiming it does).
I waited 7 days then disabled oem unlock in the developer option.
DONE.
None of skip wait time method work for me.
my friend rooted his device but stupidly turned off OEM and now his device won't turn on
I tried looking for an international firmware and flashed it on Odin but it got stuck at recovery.img, been like that for an hour,
Is it because OEM is locked? (so is FRP by the way)
Do I have to enable a setting from Odin?
he has an S9+ G965F dual SIM, he bought it from Spain but says its an international model, he doesn't seem to find the country code anywhere on the box
I need help and everything is appreciated, the sooner the better, thanks!
Check in download mode which version Bootloader the phone is running (B:1 or B:2) and match it with the firmware you are flashing, you cannot downgrade the Bootloader
G960FXXU2BRGA <<< Version 2 BL
Fixed!
*Detection* said:
Check in download mode which version Bootloader the phone is running (B:1 or B:2) and match it with the firmware you are flashing, you cannot downgrade the Bootloader
G960FXXU2BRGA <<< Version 2 BL
Click to expand...
Click to collapse
He managed to fix it himself, I was using Odin with TeamViewer from my computer to his laptop, and I think that messed with something as he repeated the exact same steps after I disconnected and worked flawlessly
Thanks everyone that helped and the community offering help!
Hi All,
Happy new year. I had been struggling to root the S9 and getting the following error
"only official released binaries are allowed to be flashed(recovery)" while ODIN flashing of TWRP 3.2.1.1.tar
I tried a few methods mentioned in the forum - Wipe/factory reset->Flash Official firmware-> again TWRP using odin
Also tried OEM unlock option. Still cannot succeed in rooting the phone.
Kindly help me with the files and procedure to root and install stock rom. Thank you all in advance.
Regards,
Raghav
Need to have both rmm normal and oem unlocked
amakuramio said:
Need to have both rmm normal and oem unlocked
Click to expand...
Click to collapse
So do I need to flash rmm before twrp flashing?
amakuramio said:
Need to have both rmm normal and oem unlocked
Click to expand...
Click to collapse
I know there are lists of threads dealing with this topic, but I would request for your help in the procedure to root the phone successfully. Thanks in advance
amakuramio said:
Need to have both rmm normal and oem unlocked
Click to expand...
Click to collapse
How to make rmm normal?? How long to wait 7 days or 14 days after OEM unlock. Also need to put the sim on the phone or can just leave it ON with wifi connection?