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
Related
Hi all
A week ago a rooted my Samsung Galaxy S6 device following this post: http://forum.xda-developers.com/galaxy-s6/general/root-pingpongroot-s6-root-tool-t3103016
All was OK. At that point my device is using the Android Version: 5.0.2
The question I have is that now the version 5.1.1 (Lillipop) has been released, I would like to know if my rooted device can still be upgrading when the new version is released in my region (Mexico) by the phone provider. (Telcel). In case it cannot be updated automatically, I guess I will need to do it manually or unroot my device. In that scenario, Does someone know a good tutorial how to do that?
Regards!
@LesthadMK, sure you can update rooted devices. But it may not be possible via OTA update. You will have to download the full firmware and install it manually.
Because root makes changes to system partition, OTA fails when you have rooted. If you unroot and flash stock recovery and kernel back, then OTA may work. Otherwise, simply flash the full firmware, in .tar format using Odin software, and you're good.
It's good to have full firmware saved on PC anyway, as if in case you brick your device, you can fix it by installing your device's firmware manually.
If you need help with 5.1.1 firmware installation on your s6, let me know the build no. of your device.. I will guide you to page you need to look at.
Thanks for the help. I have download Odin in case I need to do it manually.
Also, mentioned that yesterday I read an article saying that using the Samsung software "Smart Switch" in an rooted device will upgrade the device to the newest version (which I don't know if it it's true or not) Any way this is the link I found:.... Well seems since I'm newby I cannot post some external links. So just google it as: How to Use Smart Switch to Update Your Galaxy S6—Even It's Rooted.
By other hand, this is the build number for my device: G920IDVU1AOE3, so if you can help me to know how to upgrade that version that would be very helpful
Regards!
Hi there,
I have a Samsung Galaxy Tab A6 (SMT-580) which I bought today. I followed this tutorial to install twrp, ultimately to root the device:
dottech .org/200476/how-to-install-twrp-recovery-on-samsung-galaxy-tab-a-sm-t580/
Everything worked fine and I was able to boot and reboot fine. Until I signed in with my Google Account. After trying to reboot, I get a black screen with the Samsung logo and a text in red saying: Custom binary blocked by FRP Lock. I went back to the store and they advised me to install Samsung Smart Switch to try and restore. In the Smart Switch program I get an error saying that the device is not supported by Smart Switch.
I can get into download mode, not into any other mode. The tablet doesn't start up at all. On the download mode it also says FRP Lock ON.
When I go back into ODIN and retry to install the from above TWRP image, it says operation failed.
Can anybody please advice? I am at a complete loss. Am I supposed to flash the original boot file? Where can I find that for my device? Will my tablet accept that, since ODIN didn't even want to flash my current TWRP image a second time?
P.S. I only read later that you are supposed to change the OEM setting. I didn't. Is that the cause of this issue, and if so, can I do something about it?
Thanks
Hi. Have you got it fixed yet? You need to download and flash stock firmware for your model and flash it in odin. Once it's done you have to enable oem unlock before you flash twrp. Let it be enabled as long as you you have twrp, root or anything custom.
Skickat från min SM-A310F via Tapatalk
ok, I read this is the place for noobs, so, I too got myself into a FRP LOCK on my Galaxy Tab A6 sm-T280. I use the tablet strictly for flying my drone for surveillance around the rural location where I live. It was having some connectivity problems, so I rooted it to hopefully get enough horsepower to run the DJI Go app. That didn't work so I did a wipe/factory reset, had a problem with the password, and here I am.
I am researching, and gathering the required tools to fix it.
I finally found some guides that are basic enough for me to understand.
I found numerous sites to download the stock rom, but not sure which ones are safe. Suggestions? Also, I am not sure about the country code for the firmware. I am in the USA, and I don't see it listed anywhere. Does it matter? This android stuff is all new and confusing to this old man. I am determined to get this tablet fixed, and would appreciate any and all advice. Thanks, Gary
edit: Will this rom work? : T280XXUOAPL1 using XAA for theCSC? Is xaa the default/generic for U.S.A. ?
My Fried gave this phone to me (SM-N915G) which is stuck at Powered by Android, and told me to fix it.
He said that when he update to MM from LP without KIES or Odin, the phone suddenly restarted and stuck there getting HOT
He had no experiece to repair it so he asked me to fix it.
So for 3 days lately, i have tried many ways to fix it but wihout any progress, as follow :
1. Flashing Official MM wby using Odin -> still stuck
2. Downgrading Flash Official LP using Odin -> still stuck
3. Installed TWRP, and flasing CFW Micky387_MM_V3.0 for 915F/FY/G (flashing Bootloader and modem as required) -> still stuck with set warranty bit : kernel
4. After Flashing Micky CFW and Failde, i try to flash Emotion Kernel -> still stuck with Kernel is Seandroid Enforcing
5. Redoing Flash Micky CFW with other CSC -> Still Stuck (even i tried with 915F and 915FY as in the aroma installer)
6. Never failed during flash procedure with Odin or TWRP, everything is smooth
7. When stuck, the device is getting Hot slowly but and when left as long as 15 minutes, the HH is getting HOT (TWRP read 72 degree at most)
**Update
8. Tried using Official SmartSwitch sucessfully but the result is still the same -> Still Stuck and getting hot as usual T.T
Last Download Mode status is :
Odin Mode (High Speed)
Product name: SM-N915G
Current Binary: Samsung Official
System Status: Official
Reactivation Lock: Off
Knox warranty void: 0x1 (2)
Quallcomm secureboot : Enable (CSB)
RP SWREV: S1, T1, R1, A1, P1
Secure Download: Enable
UDC START
I am now thinking, should i flash another Kernel or PIT or Bootloader? but i still cant decide what to do next to revive this Phone
Please help, any suggestion is greatly appreciated, thank you.
Please give some help, thank you.
Help Please anyone?
This is Hard Brick or Soft Brick?
Any suggestion or Opinion please
Thank you
wingz17 said:
Help Please anyone?
This is Hard Brick or Soft Brick?
Any suggestion or Opinion please
Thank you
Click to expand...
Click to collapse
Have you tried a reinstall using KIES?
The Radius Kid said:
Have you tried a reinstall using KIES?
Click to expand...
Click to collapse
Yes i have try to recover but not using KIES, but using smartswitch...
Is it diffrent by using KIES or SmartSwitch?
Thank you.
wingz17 said:
Yes i have try to recover but not using KIES, but using smartswitch...
Is it diffrent by using KIES or SmartSwitch?
Thank you.
Click to expand...
Click to collapse
I can tell you that Kies and NOT Kies 3 was what worked for me when I downloaded/installed Marshmallow from Samsung's website.
Figure that one out.
That was also using a 64 bit version of Windows 7 Pro.
The Radius Kid said:
I can tell you that Kies and NOT Kies 3 was what worked for me when I downloaded/installed Marshmallow from Samsung's website.
Figure that one out.
That was also using a 64 bit version of Windows 7 Pro.
Click to expand...
Click to collapse
Thank you for the suggestion,
I will try that one out and let you know.
wingz17 said:
Thank you for the suggestion,
I will try that one out and let you know.
Click to expand...
Click to collapse
The Radius Kid said:
I can tell you that Kies and NOT Kies 3 was what worked for me when I downloaded/installed Marshmallow from Samsung's website.
Figure that one out.
That was also using a 64 bit version of Windows 7 Pro.
Click to expand...
Click to collapse
Sorry For the long response, i have tried flasing using KIES but still stuck on the android, and no progress.
Right now i am run out of option, please help, thank you.
wingz17 said:
Sorry For the long response, i have tried flasing using KIES but still stuck on the android, and no progress.
Right now i am run out of option, please help, thank you.
Click to expand...
Click to collapse
I'm going to guess that you've tried installing MM using Kies directly from Sammobile?
If so,have you tried turning off your computer's antivirus when you download/install?
It sounds like the bootloader is looking for something and can't find it.....kind of like what happened to me when I totally ripped KNOX out of my phone.
Restore time!
Good thing I did CWM backups.
In your case,your computer's anti virus could be seeing something in the download and ripping it out.
I've seen my browsers do that when I download stuff....pain in the....
Have you tried a different battery?
Maybe a search of the forums to see if anyone else has had this problem and solved it?
I kind of remember seeing something like this a while back.
The Radius Kid said:
I'm going to guess that you've tried installing MM using Kies directly from Sammobile?
If so,have you tried turning off your computer's antivirus when you download/install?
It sounds like the bootloader is looking for something and can't find it.....kind of like what happened to me when I totally ripped KNOX out of my phone.
Restore time!
Good thing I did CWM backups.
In your case,your computer's anti virus could be seeing something in the download and ripping it out.
I've seen my browsers do that when I download stuff....pain in the....
Have you tried a different battery?
Maybe a search of the forums to see if anyone else has had this problem and solved it?
I kind of remember seeing something like this a while back.
Click to expand...
Click to collapse
Thank you for the response,
I was using KIES 2.64 that downloaded from Samsung website to fix the phone as your suggestion (tools->firmware upgrade and initialisation) but still fail to fix it.
Nope, the antivirus still active when KIES download the FW and Flash it into the phone, but it is new to me that antivirus will intercept ongoing dowloaded files, if so i think the antivirus will give some notification or warning about the content of the file that being downloaded and in my case, my antivirus is still cool and no notification whatsoever.
The bad thing is i do not have any cwm backup and since this is my friend phone and not mine, well... we dont have any backup for this phone.
Regarding the battery, i admit that i havent try other battery, since i dont see any connecton between it, in my opinion, the phone works well, the charging animation working, and no sign of weak battery... but i will try to do it if i can get some other battery
I have surfed many forums and websites, but almost 90% can be fixed with simple flashing from odin or just by clearing up cache and data from recovery.
Other that that, wither, no one respond to the problem, or just some discussion without conclusion, really frustrating.
I even go further to read about android booting sequence to identify whats wrong with the boot sequence, but still confused...
But i have some question if you would to answer :
1 . Stuck at Android logo, bootloader or kernel problem?
2 . Is it possible that one of the mainboard chip that have some part in booting process is malfunctioning? But if so, the phone will be dead bricked right?
3. How about the booting process is halted due some hardware failure? ex : some chip (other than chip that have part in booting process) is bad and so the bootloader init is halted
4. The Worst guess, is it possible that the phone is fake? (the serial number behind the baterry is accepted by kies though)
Thank you very much, you are the only one who still response to my problem. :good:
As it seems you use the wrong Bootlaoder. Is his phone N915P or N915G? When you flash N915G Bootloader to N915P, it will not boot but the bootloader will work correctly. Try to flash the N915P bootloader.
I have N915FY phone but did not know first if I had N915F or FY. I flashed the N915F bootloader version, which flashed successfully, but was not booting. Bootloader said that my phones model is N915F. After flashing the FY Bootloader version, it successfully booted to system.
Bordo_Bereli51 said:
As it seems you use the wrong Bootlaoder. Is his phone N915P or N915G? When you flash N915G Bootloader to N915P, it will not boot but the bootloader will work correctly. Try to flash the N915P bootloader.
I have N915FY phone but did not know first if I had N915F or FY. I flashed the N915F bootloader version, which flashed successfully, but was not booting. Bootloader said that my phones model is N915F. After flashing the FY Bootloader version, it successfully booted to system.
Click to expand...
Click to collapse
Thank you for the Response,
First, his phone is N915G (according to the box and the information in the battery compartment)
(Really sorry for the mistake i made at the thread title)
And regarding bootloader, that is also my concern at first, i think maybe i was flasing wrong region and bootloader, and so i search the way to find out the real version of the phone, but after trying many ways described on the net (by imei or serial number) , i still cannot found out the way.
But one instance when i try using KIES, and KIES asked for the version and serial number when device upgrade and initialisation, i entered the exact version and serial number that is found behind the phone in battery compartment. KIES immediately confirms that the version and serial number is valid, (i still wonder though, is KIES check it online at Samsung server or there are some serial number database embedded in the KIES) and continue to run trough the official fw download and installation by KIES but at the end still no success.
Is it possible that the version and serial number is wrong ? if so, how to determine the correct one?
and is it safe to try flasing another bootloader?
Thank you very much
Hello, there is no bootloader related to serial number or something. There are different bootloaders for different models and android version. When you flash MM-Version, you need to be sure that you use the right bootloader and baseband files for MM. If you flash different region-locked firmware/bootloader, it will not affect btw. not solve the boot-stuck problem.
http://samsung-updates.com/device/?id=SM-N915G Try to flash 6.0.1 firmware that is related to your region if you still want to try to flash different region-firmware.
Maybe download the XSA 6.0.1 Firmware with the pit file XSA http://gsm-firmware.com/index.php?a=browse&b=file-info&id=15892.
Then flash XSA 6.0.1 and TBLTE_SEA_XSA.pit together in odin. Under Odin 3 V3.12 ticke the re-partition at option-tab and select TBLTE_SEA_XSA.pit under pit-tab.
Bordo_Bereli51 said:
Hello, there is no bootloader related to serial number or something. There are different bootloaders for different models and android version. When you flash MM-Version, you need to be sure that you use the right bootloader and baseband files for MM. If you flash different region-locked firmware/bootloader, it will not affect btw. not solve the boot-stuck problem.
http://samsung-updates.com/device/?id=SM-N915G Try to flash 6.0.1 firmware that is related to your region if you still want to try to flash different region-firmware.
Maybe download the XSA 6.0.1 Firmware with the pit file XSA http://gsm-firmware.com/index.php?a=browse&b=file-info&id=15892.
Then flash XSA 6.0.1 and TBLTE_SEA_XSA.pit together in odin. Under Odin 3 V3.12 ticke the re-partition at option-tab and select TBLTE_SEA_XSA.pit under pit-tab.
Click to expand...
Click to collapse
Thanks for the reply!
Although there is no bootloader related to serial number, but if we put the serial number in KIES, it will identify what CSC and region, which can be use as a guide to choose the correct FW or let KIES do the Flashing according to the inputted serial number, and as long as the serial number is correct one, that is my opinion but please CMIIW.
When flashing MM, if i use the MM that has been downloaded, the bootloader and baseband is included in the MM image right? or shouuld i flash it separately?
i have tried your suggestion but with no sucess, i have dowloaded the PIT and the FW, flash it trough odin which was sucess, but still stuck.
I do not tick auto restart at Odin, so i manually restart the phone, but i encounter an event which at 20% installing system update (below the greed droid guy) the progress bar is vanished and replaced with erasing, and after that the phone stuck again at the same spot.
Do you have any idea why?
Thank you very much.
Just thinking, should i erase the NAND in ODIN?
If so, how to restore it?
I think that if i backup the NAND using custom recovery and restore it later, it just bring back the same problem, if the NAND causing all this.
Do anyone have some NAND backup that i could use? or any other suggestion?
Thank you
Can you boot to recovery? if yes, try to wipe data and cache.
If it still not working, try to backup your efs with a custom recovery (ex. TWRP), or better the entire System like data, system, boot, efs, modem and save it to your computer.
After saving the backup, try to flash the firmware with pit file while checked NAND erase all.
When its finished and your device boots up, you can flash back your custom recovery and recover only the efs-partition.
If its not working, then there is maybe problems with your eMMC. But be aware using nand erase all. It is the last riskfully option left after trying several things.
I have a backup of my resurrection rom. If you want it I can upload it.
Hi guys,
I was hoping someone could help me out. I have rooted before (long time ago) but I can't seem to find a lot of information on this specific phone (SM-J727S). I have been searching online (and across many dodgy looking websites, thanks No Script!) and this is about all that I have found:
The Galaxy J7 is also known as the Galaxy Wide 2 in South Korea
http://pdadb.net/index.php?m=device&id=11601&c=samsung_sm-j727s_galaxy_wide_2
It was released on May 2017, runs Android 7.0 (Nougat) and uses the Exynos chipset
TWRP has a release for the J700 series but I'm not sure if it would work on the J727S
https://twrp.me/devices/samsunggalaxyj7exynos.html
The source code for the system has been released, but I couldn't find a stock ROM (which made me reluctant to try TWRP)
http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=j727s
This is the closest I got to a Stock ROM but I don't trust the site, is this site trustworthy? (again, I came across too many dodgy sites to just download anything)
https://stockromupdate.com/2017/07/26/stock-rom-sm-j727s-samsung-galaxy-wide-2/
The KingRoot method currently will not work and is asking me to wait for an update (phone is probably too new to root?)
The closest thing I can find on this forum are these posts (but none reference the J727S model)
https://forum.xda-developers.com/galaxy-j7/development/root-sm-j727p-galaxy-j7-perx-td-lte-t3611202
https://forum.xda-developers.com/galaxy-j7/help/root-sm-j727p-galaxy-j7-perx-galaxy-j7-t3598117
So, I'm hoping someone could point me in the right direction. Thanks in advance
I'd thought I'd mention that the bootloader is unlockable in this phone. I had read elsewhere that other people cannot access the 'OEM Unlock' option on their version of the J7. It isn't the case with this phone
https://forum.xda-developers.com/galaxy-j7/help/galaxy-j7-pop-galaxy-halo-t3647805/page2
I also got a message from Google talking about my accounts being accessed by a 'J7 Pop'. I guess the Galaxy Wide 2 is also known as the J7 Pop?
So, I'm still on the track of rooting this device. I'm just gonna update any relevant stuff here.
The closest TWRP that I can find is for the 2016 version of this phone, it has the same Exynos chipset.
I'm thinking of trying this, but are there any problems with flashing the wrong version of TWRP? (Will I brick the phone? Or will it just error-out on recovery and boot normally?)
https://twrp.me/devices/samsunggalaxyj72016exynos.html
I also found (what I believe to be) the Stock ROM for this type of phone, you have to sign up to the site in order to download it. It is specific to SK Telecom (Korean telecommunications provider)
https://www.sammobile.com/firmwares/samsung-galaxy/SM-J727S/SKC/download/J727SKSU1AQD6/172065/
If someone can advise about going forward with the similar TWRP version I'd appreciate it. Cheers!
EDIT: Kinda answered my own question, from the TWRP download page https://dl.twrp.me/j7xelte/
Downloading an image for a different device, no matter how similar, usually does not work.
Click to expand...
Click to collapse
Any way to request an TWRP version?
I am Korean, and it's very hard It's angry me............................
XDDDD I'm from South Korea too and the J727S is customized with the Knox Enrollment Service that blocks the wifi and cellular data AND apk installization. (trying to uninstall it )
I found this: https://www.androidinfotech.com/2018/02/root-samsung-galaxy-wide-2-sm-j727s-nougat.html
anyone habe twrp for this model ????
Hi.. I've this model also.. tried to downgrade..but it can't..always failed
My friend was installing the twrp to root a J7 metal.
Now the cell phone does not restart, and I do not know what the **** it did KKkkkkkkkkkk
It wants to remove the twrp without formatting the device.
If installing the original rom by Odin using home_csc does it return to normal without formatting?
Restore
CPI Justiceiro said:
My friend was installing the twrp to root a J7 metal.
Now the cell phone does not restart, and I do not know what the **** it did KKkkkkkkkkkk
It wants to remove the twrp without formatting the device.
If installing the original rom by Odin using home_csc does it return to normal without formatting?
Click to expand...
Click to collapse
If you have the firmware file the phone was on at the time he tried to Root it just flash the files using Odin an you should be good !
peter couniaz said:
If you have the firmware file the phone was on at the time he tried to Root it just flash the files using Odin an you should be good !
Click to expand...
Click to collapse
This is will make a clear data???
He canoot loose the data from the phone..
Home CSC file !
CPI Justiceiro said:
This is will make a clear data???
He canoot loose the data from the phone..
Click to expand...
Click to collapse
If he flashes the Home CSC file it may restore data but he may have to start from scratch ! Sorry an good luck !
P.S did he have it backed to Google if so Google will give the option to restore when you sign in !
Very hard to find twrp or cwm foe this model..also the combination file..and upgreded to android 9..
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