Help downgrading encrypted bootloader samsung phone. - General Questions and Answers

Hi all !
Hope everyone have a great day, i have got a samsung galaxy A6 US variant TMB, (SM-A600T) with android version 9, I was trying to root the phone but didn't have the knowledge that this phone can't be rooted because of locked bootloader which can't be unlock with any procedure. So i gave up and just updated my phone to the latest version available of PIE . (Android 9), To tell you more, before it was also on the same version of android 9 but earlier date. I have not updated a whole version of android but just to a latest date of android 9, Android 10 is also available for this phone but i haven't done that yet. The main problem with my phone is that before this update i just needed to charge my phone once in 24 hours, and now after update i need the same phone with same demands to charge it 3 times in 24 hours, Did every optimization for battery, unused apps, extra apps uninstalled, just one google account left, synchronization is off, NFC and near scanning is off, Bluetooth / Wifi is off, GPS is off. Auto update for apps and system software is off. Battery saving mode is enabled, clear cash has been done, factory reset is already done with flashing this version of android with odin tool, and etc every other thing has been tried with no luck, please don't advise for these things as the main problem for me is just the android version itself which i have newly flashed. Because of locked bootloader i can't flash back my older version of android 9 with odin tool, phone gives error of bootloader :
sw rev check fail device 2 binary 5​something like above after many tries the same result. tried my old firmware with the new bootloader but still no luck. (Same error). Any help or suggestions will be greatly appreciated. I am thinking what if i extract the AP of the new flashed firmware and replace the system.img.lz4 with my old firmware's system.img.lz4 to trick the phone and reflash with the new firmware but old system image file, Can this be done ? or i may brick my phone for ever ? what if i take my phone to the outside market and request a z3x flash for the old firmware version ? will that work ?
Please give any accurate solution i really want my old phone back, this locked bootloader has become a really annoying thing for me. I will never buy a phone like this which bootloader's can't be open again. Or if i wasn't able to flash this to my old version i will never use android again in my life, Better option will be to buy an iphone after 17 years of android use.
Thanks in advance.

Related

Samsung On5 G550T1 MetroPCS REV0.4 stock OS anyone?

Hi All,
The short of a long story is that I just changed carriers and found out way late that I couldn't bring my Sprint phone to MetroPCS. So now I'm using the budget PCS On5 that came with the deal when we signed up.
I successfully loaded TRWP and then rooted however, I didn't know about FRP until it smacked me in the face. The root went fine but later SU prompted me to update the binary and when it did, it tripped factory reset protection and soft bricked my phone.
I want to reinstall stock OS on this phone but it appears that I have a software version that I haven't been able to find on the web yet. I found the stock rom for the MetroPCS On5 easily enough but it's Revision 0.0 and the box I have for the phone says REV0.4.
When I try to Odin Flash the REV0.0 version, I get SW REV CHECK FAIL DEVICE 2, BINARY 1 fail. So I guess I had the latest software on my phone and the phone thinks I'm trying to roll back using the 0.0 revsion.
My question is this, does anyone here have the stock rom for G550T1 REV0.4? Help!
If nobody does, maybe I can still fix this phone. I have a TRWP backup from the sister phone (same model same revision 0.4) that I'm using right now but I can't get back into TRWP on the soft bricked phone to recover that way to use the backup file.
Next I thought I might take the backup files and turn it into a rom and just flash that. However, with the tutorials I followed I kept running into problems. When I went to unpack the files per the tutorial, my rar software said that the file was corrupt. Maybe it is. but maybe not. It was my first time attempting to make a rom. If I can't find the software I need, could any of you Android geniuses help me get this backup into a flashable format?
I have to admit I'm daunted by the FRS in 5.0 and above. Is it defeatable? How do you root newer Android versions?
Thanks!
I did the same thing to my phone. did you get yours fixed?> if so could you provide me with the rom?
I haven't found the fix yet. Hopefully somebody will come through with a helping hand!
I finally got it figured out! So here is what i did and hopefully it will work for you.
1. I Odin flashed a good BL from the ROM REV0.0 floating around on the net. So at least I could now get into download mode.
2. Then I used Kies3 > Tools > Firmware Upgrade and Initialisation. It will ask you for your model number and then when you click ok it will ask you for a SN.
3. The trick is that Samsung doesn't put the SN that you need on the phone or the box. (personally, I couldn't find it on the phone either once I got it up and running) so go here: https://forum.xda-developers.com/android/general/root-samsung-galaxy-on5-t3435457/page46 and get a SN from post #454 and use that. (don't forget to say thanks)
4. Click Ok. Let it work, and max and relax.
Mine took about 10 minutes. Hopefully this will work for you too! Thanks XDA!
Help!
What is BL from the ROM REV0.0? I need your help, I have the MetroPCS On5 and I installed Reborn ON5 I want to go back to the MetroPCS ROM because the camera and the audio do not work and I tried to install the original ROM through Odin but it does not work I get an error. What I can do? I would like to use this method but I do not have very clear files needed.
You could help me bro, I'll thank you

Any way to downgrade from Nougat to MM without losing FP Sensor,Haptic Feedack&Camera

Any way to downgrade from Nougat to MM without losing FP Sensor,Haptic Feedack&Camera
I recently purchased a new S7 not realizing that it was equipped with a Nougat OS. I would like to restore my current phone to the new one, but my current phone runs on MarshMallow. After restoring the backup, my new phone has no haptic feedback, no fingerprint sensor with "an error has occurred with the fingerprint sensor. if this message appears repeatedly, restart your phone" message and the Camera doesn't work.
I'm sure it has something to do with bootloader N using MM. Even restoring Stock Marshmallow firmware (Including BL) on the new phone removes these functions. Does anyone have any ideas on how I can get these to operate?
My current phone has
Bootloader Version: G930W8OYA2APK3 (MM)
Baseband and PDA Version: G930W8OYA2API1 (MM)
When I restore my old phone to the new one, it ends up with
Bootloader Version: G930W8OYA2BQK4 (N)
Baseband and PDA Version: G930W8OYA2API1 (MM)
EDIT: Just tried the Nougat firmware with MM Bootloader. All of the functionality is present.
Bootloader Version: G930W8OYA2API1 (MM)
PDA Version: G930W8OYA2BQK4 (N)
Just restored old backup with MM bootloader (Boot, Data, System only).
No Fingerprint Sensor or Camera.
BTW, ignore the HAPTIC FEEDBACK portion of this post. I believe it is working.
Any help with this matter would be greatly appreciated.
Not possible to downgrade since the bootloader block you from flashing lower version of that. You may try to flash without BL, but your phone will be malfunction
Thank you for your reply. I don't think I'll be able to get the fingerprint wizard to work but having a functional camera would be a necessity. From the System/Priv-App folder I copied the SamsungCamera5 (from MM) and the SamsungCamera6 (from N) onto an SD Card. I guess I can try to play around with them to see if either will work, but I don't think they will since my restored backup should already have SamsungCamera5 and the SamsungCamera6 apk probably isn't compatible with MM. Kinda disappointing that I'll have to continue to use my old phone with a broken screen instead of the brand new one I purchased.
Sleaze0 said:
Thank you for your reply. I don't think I'll be able to get the fingerprint wizard to work but having a functional camera would be a necessity. From the System/Priv-App folder I copied the SamsungCamera5 (from MM) and the SamsungCamera6 (from N) onto an SD Card. I guess I can try to play around with them to see if either will work, but I don't think they will since my restored backup should already have SamsungCamera5 and the SamsungCamera6 apk probably isn't compatible with MM. Kinda disappointing that I'll have to continue to use my old phone with a broken screen instead of the brand new one I purchased.
Click to expand...
Click to collapse
do not flash AP from a firmware set made prior to the bootloader youre on, it will more than malfunction, itll probably brick
i went back and read all the tl : dr stuff and saw that you seem to have got it working, oddly enough. The camera issue is likely the kernel
Thanks for the info on the thanks button. I've just about given up trying to get Marshmallow to work properly on this phone. Looks like it'll take weeks to configure my new Nougat phone to be similar to the three years of tweaks I've made to my old MM one. Oh well, first world problems I guess.
As others have pointed out, you can't use Odin to successfully flash a ROM with a bootloader that is earlier (in version) than the bootloader you have installed. The "gatekeeper" is Odin, however, not the bootloader.
Though I haven't tried it, it is my understanding that there is a way around this. Install TWRP, and use it to install a custom ROM which uses the version of bootloader that you want/need. Once the bootloader has been rolled back, you can use Odin to reinstall Nougat (or whatever). I don't know whether this might require a particular build of Odin, but I doubt it
Droiderat said:
As others have pointed out, you can't use Odin to successfully flash a ROM with a bootloader that is earlier (in version) than the bootloader you have installed. The "gatekeeper" is Odin, however, not the bootloader.
Though I haven't tried it, it is my understanding that there is a way around this. Install TWRP, and use it to install a custom ROM which uses the version of bootloader that you want/need. Once the bootloader has been rolled back, you can use Odin to reinstall Nougat (or whatever). I don't know whether this might require a particular build of Odin, but I doubt it
Click to expand...
Click to collapse
i cant even begin to imagine how/why that would work. the bootloader doesnt really care what ROM you install, its the other way around. The ROM being installed has to be compatible with the bootloader. So, installing a ROM wouldnt really do anything to the bootloader and therefore wouldnt be able to bypass the lock in knox.
The procedure I outlined apparently works where the custom ROM includes a related bootloader. Thus, when it is installed via TWRP, it replaces both the existing ROM and the bootloader. I know that TWRP can be used to install a bootloader, as I have done it (on a SM-930F). And if the gatekeeper is Odin and not the bootloader itself, then this could work.
As I stated, I haven't tried this, nor have I extensively researched it. I've only read about it, and am passing it along as a possible solution.
This post can be closed since the phone was deemed Lost or Stolen by the carrier, therefore they couldn't unlock it for me to use my SIM card. I've since returned the phone. At least I learned a few lessons for my next one. Mainly, back up the phone when you first get it. Thanks again for all of the feedback.

samsung galaxy s7 custom binary blocked by frp lock

Greetings, ever since i tried rooting my phone, i knew something went wrong (i used cf autoroot).
So the first thing i noticed, i was asked to reset the phone or something similar to that, meaning i would lose all my data.
I tried to find a workaround as this had never happened to me before while rooting a phone, and someone had said that i was supposed to download twrp
and change some partition and then change it back. I dont remember what else he mentioned and what exactly i tried doing, i realised it was formatted either way and i had to start fresh. As i setup my phone i went and switched the oem unlock back to "off", as i did not wanna attempt to root again, but i hadn't realised that my phone was infact rooted sucessfully, leading me to my first error after restarting. "Custom binary blocked by frp lock", with absolutely no access to recovery mode at all anymore. Again, trying to find a workaround, i download some stockfirmware that i atleast had hoped was the right one for my phone, after a couple failed attempts of flashing with odin, ( i had gotten various different error messeges on download mode screen such as (REV Check fail device 7 binary 0 and others witch i cannot remember), now im getting a new error screen, stating that an error has occured while updating the device software. I cant flash twrp recovery as the frp lock is on, and the only thing i can guess is that im flashing the wrong firmware, but i cant find a matching code at all.
Its the following: sm-g930fzkadbt
IMEI: 35214310282955
on the back of the phone it says uk yateley, although the phone was purchased in germany.
Im not sure what to do anymore, any advice would be greatly appreciated.
PS: I have managed to get back to the old error screen with the custom binary info, this time with bootloop, by checking the deviceinfo box on odin
Yep you've now learned the hard way not to mess about and read the proper guides.
Anyway "dbt" is just unbranded german firmware. Download UK "BTU" and flash with Odin, it's UK unbranded.
FRP lock means you'll need to unlock the phone with the google account and password that was on it before you started messing about with it.
If you don't know the google email and password you need to read up on how to bypass FRP lock and it's a nightmare.
cooltt said:
Yep you've now learned the hard way not to mess about and read the proper guides.
Anyway "dbt" is just unbranded german firmware. Download UK "BTU" and flash with Odin, it's UK unbranded.
FRP lock means you'll need to unlock the phone with the google account and password that was on it before you started messing about with it.
If you don't know the google email and password you need to read up on how to bypass FRP lock and it's a nightmare.
Click to expand...
Click to collapse
Thanks for your reply, just a question, will any btu update work? Should i download latest android version btu firmware?
(Also yes, it was stupid of me to try and do it quick but i had rooted 3 different samsung galaxy phones in the past without issues, either i did something wrong or it took something way too specific to do the job, perhaps the phone's unrootable, but thank you either way) :fingers-crossed:
Elef244 said:
Thanks for your reply, just a question, will any btu update work? Should i download latest android version btu firmware?
(Also yes, it was stupid of me to try and do it quick but i had rooted 3 different samsung galaxy phones in the past without issues, either i did something wrong or it took something way too specific to do the job, perhaps the phone's unrootable, but thank you either way) :fingers-crossed:
Click to expand...
Click to collapse
You'll likely only find the last version of BTU think it was August 2019. It isn't updated officially anymore but it'll be fine to use.
cooltt said:
You'll likely only find the last version of BTU think it was August 2019. It isn't updated officially anymore but it'll be fine to use.
Click to expand...
Click to collapse
I've found android 6 to android 8 with all the monthly updates, im just trying the latest of the latest though i dont remember my android version, ill try android 7 and 6 if that doesn't work, thanks again. I'll make sure to reply if this works or doesn't.
cooltt said:
Yep you've now learned the hard way not to mess about and read the proper guides.
Anyway "dbt" is just unbranded german firmware. Download UK "BTU" and flash with Odin, it's UK unbranded.
FRP lock means you'll need to unlock the phone with the google account and password that was on it before you started messing about with it.
If you don't know the google email and password you need to read up on how to bypass FRP lock and it's a nightmare.
Click to expand...
Click to collapse
OK so i thought it worked but i can only enter recovery mode now and download mode, but cant actually boot the system, it just boots up the battery screen whenever i plug the charger, and never shows the actual battery info, just the thunder icon. Formatting from recovery mode doesn't help either (Note whenever i launch recovery mode it says installing update, then says no command and brings me to the recovery menu) Any ideas?
PS: It fixed itself. Sorry for the pointless edit.

Someone HELP!!!

Hi all,
I'm having a nightmare of a time with my Galaxy S7... For some unknown reason I decided to root my phone about 2 months ago using CF Auto Root.. worked great.. This morning, was having bad lag issues, so I restarted the phone.. as soon as the Samsung logo came up, I got a red message at the top of the screen saying "Custom Binary locked by FRP".. kind of freaked out and booted the phone into Recovery mode.. wiped Cache and wiped phone (to go back to factory setting I guess).. restarted... since then, I had no boot.. it did loop for a while as I was trying to charge the phone.. but that's it.
Now, the only way the phone will power on is if I plug it into my computer in Download Mode. I am trying to flash the ROM, custom or stock, but Odin fails almost as soon as it starts the sboot.bin and the phone screen shows "SW REV. CHECK FAIL (BOOTLOADER) DEVICE: 6, BINARY: 1".. Also, When I try to power on the phone, it HAS to be plugged in to my computer or charger cable and it just loops with a message at the top of the screen.
I can't do anything with this phone and cant find any solutions online... please help! :crying:
PM me for images of all screens please
I had the some problem while playing with my handset I switched off OEM unlock for some reason under developer option..
Next time i reset my handset it stuck on that warning
You need to download combination file, flash it with odin, then unlock developer mode, toggle OEM unlock, than flash back your current firmware, or if you have full twrp back up restore it
JayMor81 said:
Hi all,
I'm having a nightmare of a time with my Galaxy S7... For some unknown reason I decided to root my phone about 2 months ago using CF Auto Root.. worked great.. This morning, was having bad lag issues, so I restarted the phone.. as soon as the Samsung logo came up, I got a red message at the top of the screen saying "Custom Binary locked by FRP".. kind of freaked out and booted the phone into Recovery mode.. wiped Cache and wiped phone (to go back to factory setting I guess).. restarted... since then, I had no boot.. it did loop for a while as I was trying to charge the phone.. but that's it.
Now, the only way the phone will power on is if I plug it into my computer in Download Mode. I am trying to flash the ROM, custom or stock, but Odin fails almost as soon as it starts the sboot.bin and the phone screen shows "SW REV. CHECK FAIL (BOOTLOADER) DEVICE: 6, BINARY: 1".. Also, When I try to power on the phone, it HAS to be plugged in to my computer or charger cable and it just loops with a message at the top of the screen.
I can't do anything with this phone and cant find any solutions online... please help! :crying:
PM me for images of all screens please
Click to expand...
Click to collapse
This problem appears on the forum over and over. Its a direct result of not understanding what type of S7 you have and what you need to do before modification.
The error you have in Odin means the firmware you are trying to flash is older than the bootloader file on your device. You can never downgrade a bootloader only upgrade.
In your case you need to flash a firmware version 6 or above for your device. So if you have a branded T Mobile for example you will need to download and flash T Mobile firmware version 6 or above. The firmware must also be for your region where you live.
The FRP lock is because you didn't sign out of, or remove the Google account on the device before modification. Its a security feature. It will still appear after you've flashed firmware but as long as you know the email and password the phone will start fine.
cooltt said:
This problem appears on the forum over and over. Its a direct result of not understanding what type of S7 you have and what you need to do before modification.
The error you have in Odin means the firmware you are trying to flash is older than the bootloader file on your device. You can never downgrade a bootloader only upgrade.
In your case you need to flash a firmware version 6 or above for your device. So if you have a branded T Mobile for example you will need to download and flash T Mobile firmware version 6 or above. The firmware must also be for your region where you live.
The FRP lock is because you didn't sign out of, or remove the Google account on the device before modification. Its a security feature. It will still appear after you've flashed firmware but as long as you know the email and password the phone will start fine.
Click to expand...
Click to collapse
Dammit.. I tried to put as much detail as possible in there lol.. obviously I forgot some.. My mistake the Galaxy s7 that I am using is a Rogers Mobile (Canada) SM-G930W8. As for not signing out before modification, omfg, that makes perfect sense.. didn't even think of doing that before rooting.. I appreciate the help!! I will give this a go and see what outcome I get.. Thanks!
[/COLOR]That was nice of you to respond so helpfully, despite you having seen the scenario posted over and over.
cooltt said:
This problem appears on the forum over and over. Its a direct result of not understanding what type of S7 you have and what you need to do before modification.
The error you have in Odin means the firmware you are trying to flash is older than the bootloader file on your device. You can never downgrade a bootloader only upgrade.
In your case you need to flash a firmware version 6 or above for your device. So if you have a branded T Mobile for example you will need to download and flash T Mobile firmware version 6 or above. The firmware must also be for your region where you live.
The FRP lock is because you didn't sign out of, or remove the Google account on the device before modification. Its a security feature. It will still appear after you've flashed firmware but as long as you know the email and password the phone will start fine.
Click to expand...
Click to collapse
Can't make or receive calls
Please I need help my I rooted my S7 (flat) flashed the original OS with odin Installed Twrp flashed Andriod 9 and since then I can't make or receive calls wifi seems fine. Someone please come to my rescue:crying:
Cesilina said:
Please I need help my I rooted my S7 (flat) flashed the original OS with odin Installed Twrp flashed Andriod 9 and since then I can't make or receive calls wifi seems fine. Someone please come to my rescue:crying:
Click to expand...
Click to collapse
The S7 didn't receive Android 9 so the ROM is a custom one. Any issues with custom ROM's should be asked on the ROM thread itself where you got the ROM from. It's quite normal for custom ROM'S to have bugs.
You can try flashing the ROM (Android 9 Pie) again to see if it works. If not there are several different A9 ROM's to choose from.
cooltt said:
The S7 didn't receive Android 9 so the ROM is a custom one. Any issues with custom ROM's should be asked on the ROM thread itself where you got the ROM from. It's quite normal for custom ROM'S to have bugs.
You can try flashing the ROM (Android 9 Pie) again to see if it works. If not there are several different A9 ROM's to choose from.
Click to expand...
Click to collapse
Thank you for reply. I have tried atleast 4 different custom ROMs but to avail
Cesilina said:
Thank you for reply. I have tried atleast 4 different custom ROMs but to avail
Click to expand...
Click to collapse
Do you still have an imei number listed in settings?
Can't make or receive calls
cooltt said:
Do you still have an imei number listed in settings?
Click to expand...
Click to collapse
Yes please I still have an IMEI number

Unable to get back to A 10 after Oneplus flashed A9 to device

I am trying to get my phone back to the original A10.
I had an issue whereby the fingerprint sensor would not work properly and assistant wouldnt respnd to teh the wake wordand I was constantly resetting the phone to get it to work properly so I contacted oneplus support who said that it was best for them to flash the phone and in doing so they have flashed Android 9 and are now saying they cannot flash to Android 10 for me and I have to wait for an update on EE to get back to Android 10 which is stupid
having spoken to EE say have said this is a oneplus issue
oneplus support has been shocking what can you advise me
I have already tried the local upgrade process where I have downloaded the Android 10 file and copied it to the root of my device but when I go to system updates the phone will not see the file no matter what I do
I have already tried the local upgrade process where I have downloaded the Android 10 file and copied it to the root of my device but when I go to system updates the phone will not see the fine no matter what I do
I have also tried to get the phone to force an OTA update but that does not work either
please help
bartjunited said:
I am trying to get my phone back to the original A10.
I had an issue whereby the fingerprint sensor would not work properly and assistant wouldnt respnd to teh the wake wordand I was constantly resetting the phone to get it to work properly so I contacted oneplus support who said that it was best for them to flash the phone and in doing so they have flashed Android 9 and are now saying they cannot flash to Android 10 for me and I have to wait for an update on EE to get back to Android 10 which is stupid
having spoken to EE say have said this is a oneplus issue
oneplus support has been shocking what can you advise me
I have already tried the local upgrade process where I have downloaded the Android 10 file and copied it to the root of my device but when I go to system updates the phone will not see the file no matter what I do
I have already tried the local upgrade process where I have downloaded the Android 10 file and copied it to the root of my device but when I go to system updates the phone will not see the fine no matter what I do
I have also tried to get the phone to force an OTA update but that does not work either
please help
Click to expand...
Click to collapse
Flash OOS via MSM
Would this void my warranty
Does my device news to be rooted
I have the official 10 update O too
Just had a look can't find OOS rom which one is it please
https://forum.xda-developers.com/on...ock-fastboot-roms-oneplus-7-pro-t3931424/amp/
Google it next time a litlle bit..and btw wrong thread

Categories

Resources