hi just bought the phone but i think the owner messed around with the bootloader but not sure, how do i check if the bootloader is still locked ?
You can't unlock or lock the bootloader. It is unlocked by Samsung already if you're using international variant.
You can check if a custom image (kernel/recovery) installed before or your current kernel/recovery is custom or not.
Just go to download mode and pass the warning. You'll see some info on screen. If "KNOX WARRANTY VOID" is 1, a custom image (kernel/recovery) installed before on your device. If CURRENT BINARY is CUSTOM, your current kernel/recovery is custom.
Related
Hi there!, i have a brand new moto G like 4 days ago, i want to know some points about unlocking the boot loader, so would be very nice if someone can clear my doubts about it....
1 - When you unlock the boot loader, you lost something more than the warranty from motorola an OTA updates?
2 - If i install a custom recovery, can i make a working full nand backup of my original carrier rom? ( 14.71.8.falcon_umts.AmericaMovil.en.CL )
3 - Is there a way to download official firmwares from motorola servers? i cant find 14.71.8.falcon_umts.AmericaMovil.en.CL anywhere.
4 - Can i can i make a working full nand backup of my original carrier rom WITHOUT UNLOCKING and FLASH ANOTHER STOCK ROM FROM OTHER COUNTRY? (Ex: US Global)
Best regards!!
Probably best to start by reading the multitude of posts already covering all your questions.
1 -When unlocking the bootloader, you'll need to get the unlock code from motorola... you will loose only warranty. if i were you, i'll use the phone for a week or two to test the hardware such as battery,etc...
2 -Yes, you can also fastboot a custom recovery to do a nandroid backup of your carrrier rom. But you'll need to unlock the bootloader.
3 - You can get most stock firmware from the android dev section.. please check if yours is listed there.
4 - Without unlocking the bootloader, you can't fastboot custom recovery nor install one, but you can flash stock firmware but can't confirm from another country.
deadpunk said:
1 -When unlocking the bootloader, you'll need to get the unlock code from motorola... you will loose only warranty. if i were you, i'll use the phone for a week or two to test the hardware such as battery,etc...
2 -Yes, you can also fastboot a custom recovery to do a nandroid backup of your carrrier rom. But you'll need to unlock the bootloader.
3 - You can get most stock firmware from the android dev section.. please check if yours is listed there.
4 - Without unlocking the bootloader, you can't fastboot custom recovery nor install one, but you can flash stock firmware but can't confirm from another country.
Click to expand...
Click to collapse
Thanks Dude!!!
In a stupid attempt to try to root my Moto G, I followed the instructions here up to step 6, rebooted, and was greeted in fastboot with a "failed to validate boot image" message. I have tried flashing a new boot image but I get a remote failure saying "Preflash validation failed", presumably because the phone's bootloader is locked.
The phone is from Cricket/AIO/ATT or whatever and does NOT qualify for bootloader unlocking.
Is there any way to fix this, or have I bricked my phone?
If you still have a warranty, USE IT. (Your warranty isnt void until the bootloader is unlocked, and if the warranty period hasnt expired yet)
1. Try to enter stock recovery and Factory Reset the phone.
2. Try to do a tethered root and then try unlocking the bootloader. (This is probally why the root failed) (If it does not qualify, try using sunshine: http://theroot.ninja/)
3. SKIP THIS STEP IF YOU DID AN OTA UPDATE TO 4.4.4 - watch this video: http://youtu.be/laU6NQ0LxR0
4. Try to enter stock recovery and Factory Reset the phone.
5. Flash a custom recovery such as ClockWorkMod
6. Try flashing stock rom with a flashable zip.
7. Try flashing a custom rom such as cyanogenmod
DISCLAIMER: YOU THE USER ARE TO TAKE FULL RESPONSIBILITY FOR ANY OF YOUR ACTIONS. I AM NOT TO BLAME IF YOUR DEVICE DIES.
skyguy126 said:
If you still have a warranty, USE IT. (Your warranty isnt void until the bootloader is unlocked, and if the warranty period hasnt expired yet)
1. Try to enter stock recovery and Factory Reset the phone.
2. Try to do a tethered root and then try unlocking the bootloader. (This is probally why the root failed) (If it does not qualify, try using sunshine)
3. SKIP THIS STEP IF YOU DID AN OTA UPDATE TO 4.4.4 - watch this video
4. Try to enter stock recovery and Factory Reset the phone.
5. Flash a custom recovery such as ClockWorkMod
6. Try flashing stock rom with a flashable zip.
7. Try flashing a custom rom such as cyanogenmod
DISCLAIMER: YOU THE USER ARE TO TAKE FULL RESPONSIBILITY FOR ANY OF YOUR ACTIONS. I AM NOT TO BLAME IF YOUR DEVICE DIES.
Click to expand...
Click to collapse
Thanks for the reply. Will definitely look into warranty if all else fails, I've only had the device for about a month.
The stock recovery factory reset doesn't fix the boot image. It successfully wipes everything but it still reboots right back to fastboot.
I cannot unlock the bootloader as it has been locked by the carrier and does not qualify for bootloader unlocking according to Motorola, and it looks like sunshine is a paid service, which even if I paid for I would have to be able to get into the phone to install the apk anyway.
It fails flashing any boot images or custom recoveries with a "(bootloader) Preflash validation failed" error.
To do any flashing you need an unlocked bootloader. Sunshine is a bootloader unlocking utility, its a paid app for a reason, the amount of time the devs put into making an app like that requires payment. You do not need root for installing sunshine as the app will root for you. You need to go to settings > security > and check install from unknown sources. Then download the app and run it. You can just download sunshine to check if your bootloader can be unlocked as at first it will not do anything but run a sieres of compatability tests to see if the bootloader is unlockable. Only then will it ask you for payment. But I highly suggest sending it into warranty and then try the rooting process again, but this time with an unlocked bootloader.
skyguy126 said:
To do any flashing you need an unlocked bootloader. Sunshine is a bootloader unlocking utility, its a paid app for a reason, the amount of time the devs put into making an app like that requires payment. You do not need root for installing sunshine as the app will root for you. You need to go to settings > security > and check install from unknown sources. Then download the app and run it. You can just download sunshine to check if your bootloader can be unlocked as at first it will not do anything but run a sieres of compatability tests to see if the bootloader is unlockable. Only then will it ask you for payment. But I highly suggest sending it into warranty and then try the rooting process again, but this time with an unlocked bootloader.
Click to expand...
Click to collapse
Yes, that's all fine and dandy, but like I said I'm stuck in fastboot so I wouldn't be able to use it anyway. At this point I don't even care about rooting, I'd just like to get my device working.
You do not need an unlocked bootloader to fastboot flash a Motorola firmware image.
You will get a 'Preflash Validation' error when flashing a firmware image older than 4.4.4.
Can you provide more information about your phone. Is it the LTE version? Do you know the exact model number?
lost101 said:
You do not need an unlocked bootloader to fastboot flash a Motorola firmware image.
You will get a 'Preflash Validation' error when flashing a firmware image older than 4.4.4.
Can you provide more information about your phone. Is it the LTE version? Do you know the exact model number?
Click to expand...
Click to collapse
It's an XT1032 and was running on 4.4.2. Maybe I tried with the wrong stock firmware, I used "AIO_XT1032_4.4.2-KXB20.9-1.10-1.9_CFC_1FF.xml", which I found in this thread. The version matched the info I found using "getvar all" in fastboot so I figured it was the correct one. The http://sbf.droid-developers.org site seems to be down at the moment so I guess I can try a few more when it comes back up.
That would appear to be the correct firmware. However it would also appear your bootloader is preventing you from flashing it. As I said, the best solution would be to flash the 4.4.4 firmware image for your carrier, however there isn't one at this time.
You can always try flashing the XT1032 EU Retail 4.4.4 firmware image. It doesn't matter where you are in the world, it will should work fine.
http://forum.xda-developers.com/showpost.php?p=54757500&postcount=348
Hello. Even though im having real issues finding oem unlock and am desperate to twrp and root for custom roms. I just recently red that SM-G955F are bootloader unlocked by default. Is this true? Can I go ahead and flash twrp with odin?
I bought s8 plus (G955f) couple days ago and i wanted to change rom and flash twrp but i cant, while trying flash twrp on odin its failing, i have android 9 and oem unlock option, i tried to flash older rom (i dont have a screenshot) thats official but it show this error sw rev check fail bootloader binary 4 device 11 and stuck on bootloader.img.
kitsane said:
I bought s8 plus (G955f) couple days ago and i wanted to change rom and flash twrp but i cant, while trying flash twrp on odin its failing, i have android 9 and oem unlock option, i tried to flash older rom (i dont have a screenshot) thats official but it show this error sw rev check fail bootloader binary 4 device 11 and stuck on bootloader.img.
Click to expand...
Click to collapse
A couple of things i can see but will need more information
The SW Rev check error is your trying to flash older firmware than what is on your phone. Use latest firmware.
If you have OEM unlocked but KG/RMM state in prenorrnal state then you can't flash.
From your screen shot of odin, you phone is not connected. Near the top left there a box with ID:Com should show up as being connected.
Also use the latest twrp from twrp website.
spawnlives said:
A couple of things i can see but will need more information
The SW Rev check error is your trying to flash older firmware than what is on your phone. Use latest firmware.
If you have OEM unlocked but KG/RMM state in prenorrnal state then you can't flash.
From your screen shot of odin, you phone is not connected. Near the top left there a box with ID:Com should show up as being connected.
Also use the latest twrp from twrp website.
Click to expand...
Click to collapse
SW rev shows only when im flashing android 8 (older firmware)
I dont know how to check KG/RMM state
Yes i know i just removed it after and make screenshot much much later, it always shows when phone is in dl mode
Yes Im using latest twrp from twrp site.
spawnlives said:
A couple of things i can see but will need more information
The SW Rev check error is your trying to flash older firmware than what is on your phone. Use latest firmware.
If you have OEM unlocked but KG/RMM state in prenorrnal state then you can't flash.
From your screen shot of odin, you phone is not connected. Near the top left there a box with ID:Com should show up as being connected.
Also use the latest twrp from twrp website.
Click to expand...
Click to collapse
I checked in download mode KG/RMM state RMM is prenormal and KG is checking
kitsane said:
SW rev shows only when im flashing android 8 (older firmware)
I dont know how to check KG/RMM state
Yes i know i just removed it after and make screenshot much much later, it always shows when phone is in dl mode
Yes Im using latest twrp from twrp site.
Click to expand...
Click to collapse
Due to bootloader version numbers you can not downgrade your device only upgrade. Bootloader is the 5th number/letter from the right of the firmware name you are downloading.
KG/RMM state can be checked in download mode.
prenorrnal - can't flash ( you can only flash stock samsung firmware )
checking/not there - you can flash
Edit:
If RMM is prenormal you can't flash. you can try the date method to see if help this changes the state.
There are many guides on this method some are slightly different
eg:
How to bypass KG State and/or RMM state prenormal
Hello Guys :) I want to tell how to bypass RMM state: prenormal to install TWRP Also this will resolve "Only official binaries are allowed" Disclaimer: I am NOT responsible for any damage done if you use my guide. It worked for me 100% and...
forum.xda-developers.com
or wait the so called waiting 7 days ( 168 hrs ) seems to fix this as well ( with internet connection ).
spawnlives said:
Due to bootloader version numbers you can not downgrade your device only upgrade. Bootloader is the 5th number/letter from the right of the firmware name you are downloading.
KG/RMM state can be checked in download mode.
prenorrnal - can't flash ( you can only flash stock samsung firmware )
checking/not there - you can flash
Edit:
If RMM is prenormal you can't flash. you can try the date method to see if help this changes the state.
There are many guides on this method some are slightly different
eg:
How to bypass KG State and/or RMM state prenormal
Hello Guys :) I want to tell how to bypass RMM state: prenormal to install TWRP Also this will resolve "Only official binaries are allowed" Disclaimer: I am NOT responsible for any damage done if you use my guide. It worked for me 100% and...
forum.xda-developers.com
or wait the so called waiting 7 days ( 168 hrs ) seems to fix this as well ( with internet connection ).
Click to expand...
Click to collapse
Thanks its probably it, i will check it tommorow, thank you for help.
So I first bought my Samsung a11 as an android 10 model,
I then flashed it after I bought it with an open-line android 11 version and got twrp and root. This was a year ago I think.
Now they released the final update for this Samsung phone model, and I want to at least get the latest and last version of my phone.
But I kinda forgot how to do the procedures again.
So my question is does flashing the new android version firmware using odin remove TWRP installed on my device?
my phone model is: A115FXXU2BUJ2 (android 11)
the firmware I want to install: A115FXXU3CV13 (android 12)
if so what do I need to do in order to successfully have both the new firmware I want to install and twrp installed on my device? (i kinda know how to root using twrp and magisk so no problems here)
Any help would be much appreciated!
????.?? said:
So I first bought my Samsung a11 as an android 10 model,
I then flashed it after I bought it with an open-line android 11 version and got twrp and root. This was a year ago I think.
Now they released the final update for this Samsung phone model, and I want to at least get the latest and last version of my phone.
But I kinda forgot how to do the procedures again.
So my question is does flashing the new android version firmware using odin remove TWRP installed on my device?
my phone model is: A115FXXU2BUJ2 (android 11)
the firmware I want to install: A115FXXU3CV13 (android 12)
if so what do I need to do in order to successfully have both the new firmware I want to install and twrp installed on my device? (i kinda know how to root using twrp and magisk so no problems here)
Any help would be much appreciated!
Click to expand...
Click to collapse
Yes, flashing the update via Odin will remove TWRP and root, it will also, more than likely, lock your bootloader, then you won't be able to reinstall TWRP or root the device unless you unlock the bootloader, if it can be unlocked.
Droidriven said:
Yes, flashing the update via Odin will remove TWRP and root, it will also, more than likely, lock your bootloader, then you won't be able to reinstall TWRP or root the device unless you unlock the bootloader, if it can be unlocked.
Click to expand...
Click to collapse
My phone's bootloader is already unlocked, after flashing the updated android version firmware will the bootloader become lock again? and how do i avoid rmm and frp lock?(just incase this happens)
????.?? said:
My phone's bootloader is already unlocked, after flashing the updated android version firmware will the bootloader become lock again? and how do i avoid rmm and frp lock?(just incase this happens)
Click to expand...
Click to collapse
If the bootloader in the update is a securely locked bootloader, it will probably have locked bootloader after flashing and might not be able to be unlocked. That was the whole point of me warning you in my last post. Now I've had to post again just to say the same thing that I already said. I guess I was talking to the wind.
There is no way to know what the results will be after updating unless you find someone that has already updated the exact same model number of A11 or bite the bullet and update yours then see what you get.
Droidriven said:
If the bootloader in the update is a securely locked bootloader, it will probably have locked bootloader after flashing and might not be able to be unlocked. That was the whole point of me warning you in my last post. Now I've had to post again just to say the same thing that I already said. I guess I was talking to the wind.
There is no way to know what the results will be after updating unless you find someone that has already updated the exact same model number of A11 or bite the bullet and update yours then see what you get.
Click to expand...
Click to collapse
I see, looks like i need to find someone who have done it and see if it works. I didnt get what you mean about after flashing, it might have a chance to lock the bootloader depends on the update. I think ill just try and see what happens. Thank you.
I dont know guys with that phone but there should be a tool that bypass auth and unlock the bootloader in any case. I ONLY knows MTK devices, not sure about that samsung i use a .Bat file.
????.?? said:
I see, looks like i need to find someone who have done it and see if it works. I didnt get what you mean about after flashing, it might have a chance to lock the bootloader depends on the update. I think ill just try and see what happens. Thank you.
Click to expand...
Click to collapse
No, I said that after the update, it could cause the bootloader to be locked and then may not be unlockable from that point on. It depends on the bootloader in the update. If this happens, you will be unable to install TWRP or root via Magisk. That is why you need to confirm whether or not flashing the update will relock the bootloader during the flashing process and, if it does, whether or not it can be unlocked again after the update.
In other words, look at exactly what you are about to jump into before you make the jump because you might land in the one place that you absolutely do not want to land.