Database Info

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

[FIXED] Vicious cycle for Relocking Bootloader and Find Device Storage Corrupted

Greetings. After trying Derpfest on my Redmi Note 7 Pro, I decided to switch back to MiUI. I wiped out the entire Custom ROM, then installed Indian version firmware, and then installed the latest MiUI ROM in recovery mode (I prefer Orange Fox). After that, I wanted to relock my bootloader so I got the latest MiUI 11 fastboot ROM and then used MiFlash and used the clean_all_and_lock option. My device relocked it's bootloader, however, it turned out that several things like sensors or Find Device service were not working correctly. It also showed a message "Find device storage corrupted, your device is now unsafe". Looking for solutions, I ended up unlocking the bootloader again, getting back OFox, and installing the persist.img file which I extracted from my fastboot ROM. This fixed the issue with the sensors. But now, I still can't get access to services like Find Device (both from Xiaomi and Google). If I have to avoid the 'Find Device Storage corrupted' error, I have to unlock bootloader. If I have to lock bootloader, I get the error message. What am I supposed to do?
I also have tried older Fastboot ROMs, although they were all MiUI 11. Should I try fastbooting into a MiUI 10 ROM and then get OTA to do everything else? If this is the case, which specific version of MiUI 10 ROM should I flash? I can't remember which version my phone came with. My model number M1901F7S. And also, I've never used Magisk. I didn't really care if I wanted to root or not. Derpfest passed Safetynet pretty nicely. But now I do not wish to root. I don't want Magisk or anything else, I want to secure the phone just as it was before.
EDIT : Turns out that Find Device (from both Google and Xiaomi) are actually working, just in a less effective scale than what I previously used to have (before getting the custom ROM). But yet, can I bring my phone back to the locked bootloader state? I want to secure it completely, just like how it was when it came out of the box. I also cannot install apps like Netflix. I would really like to know how to relock my bootloader.
EDIT 2: I've fixed it. Indeed, I had to flash a stock MiUI 10 ROM. Version 10.0.2 and whatever number ahead worked for me and gave me no problems, and then I simply updated to MiUI 11 using OTA Updates.
However, I do not recommend using MiFlash tool, and instead recommend pasting the ROM files into your platform_tools folder and then running flash_all_lock/flash_all. MiFlash may sometimes glitch and cause problems.

Question T-mobile oneplus 9 (LE2117) has an unlocked bootloader now?

Hello all, after lurking here for a while, I found something that's making me post.
I have a carrier locked OP9. I just received the update to Android 12, and it has broken critical features. (Particularly not being able to stop apps from being closed accidentally!)
I have looked at Lineage OS in the past, and the process to get the LE2117's bootloader unlocked was... complicated.
However, while trying to fix other problems, rooting around in the developer options, I noticed that "unlock bootloader" was actually toggleable!
I think I have an unlocked bootloader now, but it's on android 12, and all the guides for rooting and installing a custom MOD for this phone say you must revert to android 11 before anything else.
So what now? Am I waiting for lineageOS 19 to come out, because that's the one based on android 12? I'm new to custom roms, and don't get the coding side of how all this works. (But I'm pretty determined to figure this out.)
Thanks for any help or advice you've got!

each stock update has a new firmware right now atleast all the roms are based on a11 latest firmware im not sure since oneplus got a12 if roms will switch to the newer firmware here is to hoping!

Gotcha, thanks. So waiting for lineage 19 it is, it sounds like, since that one is based off android 12.

dark_sable said:
Gotcha, thanks. So waiting for lineage 19 it is, it sounds like, since that one is based off android 12.
Click to expand...
Click to collapse
I am pretty sure there is root for 12. All you need to do is dump the payload from the 12 update OnePlus let's loose, and patch it with magisk and flash it via fastboot. Via bootloader it is easy I am using a TMobile OnePlus 9. All you need to do is revert back to 11 via a msm tool. There is a post here for that. After downgrading to unlock your bootloader is easy only takes time. There is a post for it I don't remember all the details but all you have to do is get you imei code and email OnePlus. Soon they will sent you a code to fastboot flash to unlock the bootloader. After that most of these 12 work for us on our model phone. I am using evolution x. It tells me every day I can go to 12 .

funkybear34 said:
each stock update has a new firmware right now atleast all the roms are based on a11 latest firmware im not sure since oneplus got a12 if roms will switch to the newer firmware here is to hoping!
Click to expand...
Click to collapse
Yes yes they do.

I've run into this same issue with wanting to use a Custom ROM. I have the T-Mobile version on A12 and it's now rooted. Another user shared the patched image file with me. I flashed it with fastboot boot boot.img then direct installed through Magisk to gain root. But all the custom roms here require A11 downgrade through the MSM tool and you have to use an MSM tool for T-Mobile, which was shared with me and explained but I'm not willing to downgrade. Until a custom ROM releases that I can flash on top of A12 I won't use it. I've had bad experiences with MSM tool to recover from brick and didn't succeed and had to send back to OnePlus for repair.

JimmyL216 said:
I've run into this same issue with wanting to use a Custom ROM. I have the T-Mobile version on A12 and it's now rooted. Another user shared the patched image file with me. I flashed it with fastboot boot boot.img then direct installed through Magisk to gain root. But all the custom roms here require A11 downgrade through the MSM tool and you have to use an MSM tool for T-Mobile, which was shared with me and explained but I'm not willing to downgrade. Until a custom ROM releases that I can flash on top of A12 I won't use it. I've had bad experiences with MSM tool to recover from brick and didn't succeed and had to send back to OnePlus for repair.
Click to expand...
Click to collapse
It amazes me how many people have problems with the MSM Tool. I was afraid I was going to have problems after reading all the issues people have had and had zero and I've used it twice. Both times I just put the phone in EDL and connected it to the USB-C port on my tower. Windows 11 surprisingly didn't even give me any issues.

EtherealRemnant said:
It amazes me how many people have problems with the MSM Tool. I was afraid I was going to have problems after reading all the issues people have had and had zero and I've used it twice. Both times I just put the phone in EDL and connected it to the USB-C port on my tower. Windows 11 surprisingly didn't even give me any issues.
Click to expand...
Click to collapse
I can't get my phone to go into EDL mode. Ever. Took every suggestion I've read. It just never went into EDL mode

JimmyL216 said:
I can't get my phone to go into EDL mode. Ever. Took every suggestion I've read. It just never went into EDL mode
Click to expand...
Click to collapse
What worked for me was shutting the phone off, removing my case, holding both volume up and down, then plugging the phone in. The screen won't show anything, you have to look at the MSM Tool and see that it's connected to know you did it right. Both times I tried it worked perfectly.
You can also use adb reboot edl if you can get the thing to boot and have USB debugging turned on.

Question [SOLVED] Can anyone help me unbrick? I have tried lite firehose, MSM for global, MSM for Indian 9 Pro, none work

I modded the global MSM so that it will flash to this frankenphone.
All of those stuck on Indian firmware, rejoice! I modded the global MSM!
Long story short, I bricked my device today, had to use the Indian 9 Pro firmware to fix it as the global MSM wasn't recognizing it, and was very frustrated I couldn't go back to full global firmware. I figured out how to fix this. Just use it...
forum.xda-developers.com
EDIT: For anyone else trying this and getting unsupported target O2, click the Target dropdown and change it to India. It's a device mismatch that can be overridden that way. It's flashing now and I'm sure it will work fine.
EDIT2: Yeah, that worked fine. To get back to global and get a working phone, follow the steps here: https://forum.xda-developers.com/t/...ection-error-check-this.4308601/post-86528671
TWRP has been updated since that guide was made and no longer has you select between A/B partitions to format and it will give you errors on partitions when you flash but it does work regardless and boots up fine with full working radio.
When it's back up and running, if you don't plan to go straight to a custom ROM, turn USB debugging back on, reboot to fastboot, boot (don't flash) TWRP again, and use this copy partitions script to make sure both partitions have the same software.
copy-partitions-20210323_1922.zip | by The Muppets for Generic Device/Other
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
Now you should be good to go (until the next time this insanely finicky device decides it doesn't want to cooperate). I have not figured out how to make it actually be recognized as the global device that it is, if anyone knows how to do that, please let me know. It is now recognized as an Indian 9 Pro variant which means I have to use the Indian 9 Pro MSM and go through this headache any time it decides to be a pain.
Original post: So I have an LE2115 and was doing some testing for a ROM dev. He asked me to flash Lineage to see if something worked there, I flashed the recovery, it booted back to fastboot. Tried flashing it again, same thing. Tried the global fastboot stock flash that's pinned here and that seemed to go okay until it rebooted, from there I had a black screen.
Fired up my global MSM tool which has always worked before, Sahara error. Got it back into EDL again, checked lite firehose, device not match image... Tried Indian 9 Pro MSM and it says unsupported target.
Am I just completely hosed here or is there something else I can do? I'm not new to ROM flashing, been doing it since the HTC Hero in 2009 and long before that with Windows Mobile 5 on my PPC-6700 and this is the first time I have what appears to be a totally bricked device so any help would be greatly appreciated.
It doesn't do anything but go to EDL.

Question Easiest/best way to get to stock Android 13?

So I've got a TMobile OnePlus 9 that's been converted to the global ROM. From here what's the easiest way to get updated to stock OxygenOS Android 13? When I run the system update in settings it'll update to Android 12 but the phone says that there's no sim card in. Am I doing something wrong? I don't mind unlocking the bootloader and flaking a recovery if there's a stock rooted zip I can flash.

I've tried myself but updating anything to 12 and up my touchscreen stops working, but using the TMobile India modded MSM should work getting to the global rom "but now realizing it was cuz I used something else to recover from a brick" but here
Safely convert regions (includes T-Mobile) as well as restore the ability to use OOS12 after using Indian MSM to recover from a brick (Windows only)
It seems lots of us have had to use the India 9 Pro MSM to recover our devices and in the process, we lose the ability to go back to OOS12 or ROMs based on that firmware because the touchscreen stops working and also trying to convert T-Mobile...
forum.xda-developers.com

th
underworld737 said:
I've tried myself but updating anything to 12 and up my touchscreen stops working, but using the TMobile India modded MSM should work getting to the global rom "but now realizing it was cuz I used something else to recover from a brick" but here
Safely convert regions (includes T-Mobile) as well as restore the ability to use OOS12 after using Indian MSM to recover from a brick (Windows only)
It seems lots of us have had to use the India 9 Pro MSM to recover our devices and in the process, we lose the ability to go back to OOS12 or ROMs based on that firmware because the touchscreen stops working and also trying to convert T-Mobile...
forum.xda-developers.com
Click to expand...
Click to collapse
thanks I'll ck it out

this doesn't work for my device le2119 the mod fix zip throws an error unsupported device eu. I made the mistake of activating slot b. is there any way of switching back without fastboot. all I get is a black screen no matter what button combo I press. I can only get edl and I'd rather not flash the eu msm again.

paulb1977 said:
this doesn't work for my device le2119 the mod fix zip throws an error unsupported device eu. I made the mistake of activating slot b. is there any way of switching back without fastboot. all I get is a black screen no matter what button combo I press. I can only get edl and I'd rather not flash the eu msm again.
Click to expand...
Click to collapse
ive gotten the same error too, im on 11.2.10.10, but cant upgrade to OOS12/13 without the touchscreen breaking/dual sim bug, i forgot the link to the 9 pro india msm to flash it with, but ive tried flashing one that was 9 pro and kept getting "device not match image", no clue why

I just read somewhere that downgrading to 11.2.2.2 may work but only place I can find that firmware is on some Chinese site. I can flash the eu pro version all day long. but now I tried flashing an India mod firmware with no success and reflasjed eu again but phone is stuck at 0% power and all I get is a bootloop