Hey! Newbie here in need of some help... (sorry for the poor formatting)
So about two years ago i got a J7 Pro (box says SM-J730G/DS, which is important for later) from my carrier (IUS) (MX), and I tried to root it. Apparently it didn't go well or something, I honestly have no recollection, and then because of external forces I had to change to iPhone.
The only thing I remeber before I stopped using it is that the settings app was kinda messed up (eg. there were two "Battery" settings, there was a new option called "Service provider" which had the options "KT twophone service", which apparently is Korean, and "My Wi-Fi home settings", etc.) Also, I got a "Processing failed" error message when wanting to check for updates.
Now yesterday I decided to unearth it again and of couse everything was the same, so I investigated how to return to stock firmware. The Smart Switch option isn't possible anymore; the only viable way (atm) for me is via Odin. The phone also somehow does not boot into recovery mode by Volume Down + Power.
I downloaded the firmware, and this is where everything gets messy. It seems the firmware I had flashed previously was SM-J730GM, which is still the only one I can find for my carrier and region. It is the firmware too that I flashed today (J730GMUBU2AQI3 and J730GMUBU2AQF3) through Odin, however I was not able to flash the BL, CP and CSC, because I would get a myriad of errors (one run I would get "repartition operation failed", on another, "cm.bin fail", or fail on the "set .pit file", and so on).
Remember when I said the box info was important? Yeah, the app Phone Info *Samsung* says both the bootloader and the broadband version are J730GUBU1AQF3, not J730GMUBU2AQF3. However, Sammobile says that for my region/carrier (MX/IUS), it is GM, not G. The back of my phone, however, says J730G/DS
I am at a loss. I read that one possibility is to use the Re-partition and NAND Erase options in Odin, but since I don't know whether my phone is J730G or J730GM, and I don't have a way to backup my EFS folder, I don't feel like doing that.
Could someone please explain to me what I can do to fix this?
Here is the settings screenshots link: https:// imgur . com/a/7k8jZcX
And of the Phone Info app: https:// imgur . com/a/YDDhaqd
Again, I'm really sorry for the formatting.
akathoristos said:
Hey! Newbie here in need of some help... (sorry for the poor formatting)
So about two years ago i got a J7 Pro (box says SM-J730G/DS, which is important for later) from my carrier (IUS) (MX), and I tried to root it. Apparently it didn't go well or something, I honestly have no recollection, and then because of external forces I had to change to iPhone.
The only thing I remeber before I stopped using it is that the settings app was kinda messed up (eg. there were two "Battery" settings, there was a new option called "Service provider" which had the options "KT twophone service", which apparently is Korean, and "My Wi-Fi home settings", etc.) Also, I got a "Processing failed" error message when wanting to check for updates.
Now yesterday I decided to unearth it again and of couse everything was the same, so I investigated how to return to stock firmware. The Smart Switch option isn't possible anymore; the only viable way (atm) for me is via Odin. The phone also somehow does not boot into recovery mode by Volume Down + Power.
I downloaded the firmware, and this is where everything gets messy. It seems the firmware I had flashed previously was SM-J730GM, which is still the only one I can find for my carrier and region. It is the firmware too that I flashed today (J730GMUBU2AQI3 and J730GMUBU2AQF3) through Odin, however I was not able to flash the BL, CP and CSC, because I would get a myriad of errors (one run I would get "repartition operation failed", on another, "cm.bin fail", or fail on the "set .pit file", and so on).
Remember when I said the box info was important? Yeah, the app Phone Info *Samsung* says both the bootloader and the broadband version are J730GUBU1AQF3, not J730GMUBU2AQF3. However, Sammobile says that for my region/carrier (MX/IUS), it is GM, not G. The back of my phone, however, says J730G/DS
I am at a loss. I read that one possibility is to use the Re-partition and NAND Erase options in Odin, but since I don't know whether my phone is J730G or J730GM, and I don't have a way to backup my EFS folder, I don't feel like doing that.
Could someone please explain to me what I can do to fix this?
Here is the settings screenshots link: https:// imgur . com/a/7k8jZcX
And of the Phone Info app: https:// imgur . com/a/YDDhaqd
Again, I'm really sorry for the formatting.
Click to expand...
Click to collapse
1. Try heimdall instead of odin
2. Try with pc, adb fastboot wipe commands
akathoristos said:
Hey! Newbie here in need of some help... (sorry for the poor formatting)
.....
Click to expand...
Click to collapse
Okay so,
1. What is the current state of your phone(is it bricked or working)?
2. What version of Android do you have( 7.0 Nougat ) or ?
If your phone is NOT bricked, I recommend first to go to developer settings and do OEM unlock
(you can enable developer settings by tapping the field Build Number fast multiple times in About phone information)
then, you can download stock firmware for J730G( not J730GM) and it doesn't have to be from your carrier or country.
After that, you can either use your stock rom or flash recovery and then flash custom ROM.
Related
Hi all,
New user here, not much experience rooting or messing with firmware for phones. I was following the guide on how to flash the SM-935U firmware to the verizon model of the Galaxy S7 Edge, and may have bricked my phone. Here's what I did.
Followed the guide to the letter.
Powered off phone, booted to Download mode
Fired up Odin, selected the SM-935U firmware files, and clicked start.
It gave me an Auth error, which research revealed means that I forgot to turn off Reactivation Lock. I figured, "Fine, I'll just disable it. However, I can't get the phone to boot again. Every time I leave download mode, it boots into Android Recovery, where, no matter what I do, it just reboots into Android Recovery. I can't Wipe anything because it can't mount /system - probably due to Reactivation Lock?
I've been research and researching ways around this, and everything I find just points back to flashing it with the stock firmware. But then I read that you can't even do that if Reactivation lock is on, because Odin will still fail with the Auth error. So, I can only get it to boot to recovery mode, and I can't flash it with anything?
I did read somewhere that if I choose to wipe the phone's EFS with Odin that it should override activation lock, but then it clears the phones IMEI, which is an even bigger mess, isn't it?
I feel like I have to be missing something... since it never did the wipe, why is it that I can't get past the recovery mode. Shouldn't I still be able to get into the system somehow?
Does Anyone have any thoughts or suggestions for me? I'd really like to not be stuck with a permanently bricked S7 edge if at all possible....
Solved
Just wanted to post this to help anyone else who might have this issue. Turns out that you can flash the stock firmware, as long as you're flashing at least the same version or newer of the stock firmware as what the phone was running prior to getting stuck in recovery mode. It shows you what version it was running in the recovery mode at the top.
So for me, I googled the exact firmware version that recovery mode said the phone was running, downloaded it, flashed it with ODIN, and it worked just fine. Had to choose to wipe with the recovery mode after I flashed it, but then it booted like normal. - Then I enabled OEM unlocking under the developer menu, and tried flashing the U firmware again with ODIN, and it still failed with the auth error. Huh.
Turns out (maybe I wasn't doing it right or something) that you can't flash older versions of the firmware to the phone. But, as long as OEM unlocking is enabled, you can flash the U (unlocked) version of the current firmware to the phone and it will take just fine. Hint: I was able to determine the "version" number by looking at the last 4-5 characters of the build number... the verizon version I was running for my SM-935V was: VZW-G935VVRU4API3 - So I googled the API3 firmware and found the U (unlocked) version for my carrier (I happen to be using T-Mobile) on this site: https://samsung-firmware.org/model/SM-G935U/ and found the zip file name which was TMB-G935UUEU4API3-20161011161050.zip, googled that, got the rapidgator link, downloaded it, and that flashed just fine to the phone, and now my T-Mobile SIM works perfectly in what was previously the SM-935V, which now identifies as an SM-935U in settings. It's beautiful.
Also, you need the PIT file, but I was able to use the PIT file for the phone model number (again, found at the top of the android recovery menu), which for my phone was: HERO2QLTE_USA_VZW.pit (googled that and got it off androidfilehost) - I was able to use that PIT file for the T-Mobile U version of the firmware and it worked just fine.
Hope this helps someone.
Hi guys!
So I have a S7E 935F unlocked.
I tried to root the device and did everything as written and shown in every tutorial but it failed to do so.
After flashing recovery TWRP and trying to flash SuperSU the device just got into a boot loop.
I was reading around and understood that this is a problem due to encryption of the FS.
So I downloaded my firmware from sammobile and flashed my device again, everything got back to normal.
Well, almost normal. The rom I have has the same build number, version, kernel, everything is the same as the original one only that I have things in the settings menu I never has, like I have "apps" twice, one for apps permissions etc and one for apps manager, I also have "T roaming" no idea what it is, never had it, I have "service provider KT twophone".
Also the settings app crash a lot, browser gets stuck a lot, can't change system language to English (app crash).
At the home screen I Samsung Pay which I never had and I have some sort of a news app integrated on my home screen and it's marked with two stripes.
I verified this is a global rom for my country, not by any mobile company as before, I really don't have a clue what to do.
Can someone please advise?
T roaming and KT twophone service are both from korean carriers, maybe you have a wrong CSC installed or your /efs/imei/mps_code.dat is messed up.
Try to download and install the latest firmware of your region using Samfirm and if it still doesn't solve the problem, open up /efs/imei/mps_code.dat and see if matches your region name.
OK so I D/L the firmware again and same thing...
I checked /efs folder and its empty, maybe the content is hidden? Anyways my device has its IMEI and I can use it to make calls... thoughts?
roeio82 said:
OK so I D/L the firmware again and same thing...
I checked /efs folder and its empty, maybe the content is hidden? Anyways my device has its IMEI and I can use it to make calls... thoughts?
Click to expand...
Click to collapse
You need smart switch on your pc, enter your imei number in smart switch and it will download correct firmware according to your imei, then flash it. Good Luck
Sent from my SM-G935F using Tapatalk
Hi the same thing happend to me in settings but did downloading the firmware via smart switch change the settings and if so how do you do this
Tommmy5555 said:
Hi the same thing happend to me in settings but did downloading the firmware via smart switch change the settings and if so how do you do this
Click to expand...
Click to collapse
Hello, this smart switch method is obsolete. Use odin to re-flash your stock rom in case of any issues. Be sure to use correct and matching binary firmware.
Hey guys,
I just got a used S8+. Upon booting up it was a clean factory reset. I went forward with the setup.
When i open up Samsung Pay i get the "samsung pay access to samsung pay has been denied...." msg.
This phone is not rooted, i have downloaded a root check and comes back as false.
The person who had the phone never rooted the phone.
And i also get this notification " Security Notice, unauthorized actions have been detected..."
Anyone know what could be wrong with it?
go into download mode, and see there if knox has been tripped. also can you use secure folder?
I had a similiar issue (KNOX not tripped). Just downloaded stock Odin ROM, flashed it and everything worked again.
This is what i get when in download mode?
Ill test Secure Folder now...brb
This is what i get when secure folder is launched.
Secure folder cannot be set up because unauthorized software was installed on the device.
kernel.killer said:
I had a similiar issue (KNOX not tripped). Just downloaded stock Odin ROM, flashed it and everything worked again.
Click to expand...
Click to collapse
IF its not too much trouble can you point me to the right link
https://forum.xda-developers.com/galaxy-s8+/how-to/official-stock-firmware-update-odin-t3582175 In SamFirm model enter your model number (presumably SM-G955U1, can be found in settings) and in region your active CSC (most likely ATT - Settings -> About Phone -> Software Information -> Service provider SW ver., last line of this field contains something in format XXX/XXX/YYY, use the first three letters). In Odin use HOME_CSC for CSC field, to keep your data.
kernel.killer said:
https://forum.xda-developers.com/galaxy-s8+/how-to/official-stock-firmware-update-odin-t3582175 In SamFirm model enter your model number (presumably SM-G955U1, can be found in settings) and in region your active CSC (most likely ATT - Settings -> About Phone -> Software Information -> Service provider SW ver., last line of this field contains something in format XXX/XXX/YYY, use the first three letters). In Odin use HOME_CSC for CSC field, to keep your data.
Click to expand...
Click to collapse
Thank you,
If the phone is fresh and i don't care about data. Should i flash all of the files?
djfred500 said:
Thank you,
If the phone is fresh and i don't care about data. Should i flash all of the files?
Click to expand...
Click to collapse
Yes, it is alway best to flash all files, but if you don't mind loosing your data, you can flash CSC_* package in place of CSC, to also repartition your phone and start fresh. But if you want to keep your data, you can flash the HOME_CSC_* package instead.
Just tried it with all the files and i get this.
I am so lost i am about to pull my hair out...
Ok finally was able to get it up and running with Samsung Pay working...
Ill be back later with a How-To for those folks that are stuck with the same exact problem.
djfred500 said:
Ok finally was able to get it up and running with Samsung Pay working...
Ill be back later with a How-To for those folks that are stuck with the same exact problem.
Click to expand...
Click to collapse
Hi!
You can say how please?
Thanks!
Hi,
I'm in big troubles, my phone is bricked, it lost the serial number and IMEI, so i can't connect to my service provider (but wifi is still able).
All started a week ago, I was on ambasadii rom 3.8 (all OK), but I started to play with developer options :silly: and maybe I turned off OEM unlock in DEV options, so when i tried to reboot in the top corner of the phone appeared a red message (custom binary blocked by FAP lock), Yesterday I tried to Unbrick my phone so I flashed my stock VD2 rom the version U2CRF7 from Updato (Android 8, bootloader 2), i tried to save my data so I flashed Home_CSC , my phone booted FInally but the launcher and some android service were crushed, (I cant remember if My phone had still IMEI in that moment), so I had the brilliant :silly: :silly: idea of making a full wipe with TWRP without backing up MY EFS, then I flashed renovate ice 11.1 (I played with MULTI CC (I put 000)), but when I booted up, what a sad surprise I lost the connection with my service provider, wheen i tried to check my IMEI it appeared UNKNOW, I believed that it was a rom problem so I flashed again Ambasadii and I hadnt still had conection, my IMEI was 00000000000000 and my S/N was a completly mess, I noticed that the rom recognized my 950F like a 950FD, I was scarred so I flashed again the Stock VD2 firmware (WITH CSC this time) and then my phone only reboot in recovery and a bunch of messages appear with white letters, it says:
Supported API:3
dm verity verification failed...
12 lines more
er_symlink fail to mount /system as rw
I really need your help, I'm stuck
Go to your google account linked with the device on a computer and check devices connected to thsi account you will find ur imei for this phone.... Thank me later??
khawarjaved said:
Go to your google account linked with the device on a computer and check devices connected to thsi account you will find ur imei for this phone.... Thank me later
Click to expand...
Click to collapse
Men that is not funny
sorry for my English friend but I'll tell you what worked for me, download odin and find the rom of your cell phone, the series (in samssmobile is the simplest but it takes a long time to download) put the files in each corresponding place and ready , with that I return the imei, I hope it serves you
to give you an idea, search in youtube s8 brick odin, although I repeat, look for your serial version with which your phone came (including operator if you have one)
Hello Everyone,
First of all I am a newbie when it comes to Android, so forgive me for asking such a noob question.
So here is the story, my girlfriend's dad passed away few months ago. He used an old Samsung S8, sadly we do not know what the login pattern is or his Google account password (We did try recovery options but to no avail)
As there was no other option, I went ahead and had the phone factory reset, and from what I learned the phone is now FRP locked.
After a reading a few more guides I downloaded a tool called Odin and some 'Stock ROM' and flashed it hoping that would resolve the issue (Oh boy, how wrong I was) and the phone is now stuck on a screen saying "Error occurred while updating the device software, use the emergency recovery function"
My girlfriend just wanted to be able to use it for some time, and now I feel really bad for screwing it up.
Just wondering what my options are and if the phone is salvageable at all?
Hey, are you sure you downloaded the right ROM for this S8? Since there are two models of this phone, each with a different chipset (Exynos / Qualcomm Snapdragon). I feel like this error could come from a bad firmware? Does Odin still see the phone when you connect it to the PC?
Edit: Apparently people solved this problem using Samsung's Smart Switch on PC.
Yes, I think I downloaded the correct one. The phone is from Telstra Australia and so downloaded the ROM from Samfrew that was listed as Telstra, I typed in the model number which is SM-G950F it is this firmware that came up.
Yes when I put the phone into Recovery mode and connect to PC, Odin detects it, but the flash gets stuck halfway. I've loaded the BL, AP, CP and CSC that came within the ZIP file from Samfrew and under options only ticked 'Auto Reboot' and 'F.Reset Time'
Also tried just with the BL and AP but same deal.
blackslash said:
Also tried just with the BL and AP but same deal.
Click to expand...
Click to collapse
Have you tried Samsung's Smart Switch app on PC? Apparently people successfuly fixed this error with it.
blackslash said:
Also tried just with the BL and AP but same deal.
Click to expand...
Click to collapse
I've never had to deal with a Samsung that has a FRP lock, that could just be the reason why the flashing fails, i wouldn't know. I hope you can get the Factory Reset to work :/
Also tried the Smart Switch app but it would recognize the phone. Thank you for looking into this.
You could send a message to this user "makeyourself" : https://forum.xda-developers.com/t/i-think-i-screwed-the-pooch-on-this-one.3939572/post-79729654 , he seems aware about the FRP locks / flashing issues.
Good luck with your S8.
@Derbi75 thanks heaps, will message makeyourself now.
Ideas? Anyone?
blackslash said:
Ideas? Anyone?
Click to expand...
Click to collapse
From what I know, the error only appears if the phone was interrupted during flashing. Such as, Odin was writing into phone but you probably removed the USB or stuff. The screen you see is actually download mode. It is just renamed. Try plugging in your device when it's on the error screen then re-flash it.