Okay, guys...
I've been flashing since the Touch Pro 2 days, but haven't much since bootloader tend to be locked down these days. That said, I know my way around Odin and such, so I don't need anyone to hold my hand. Anyways...
A friend brought me her N970U (ATT) with a no charge issues. Resolved that, but all it would do was boot loop. Her goal was simply to get pictures off of the device, so I was trying to retain data. Wiped cache and repaired apps to no avail, figured next step would be to dirty flash via Odin. I used the firmwares provided by @iBowToAndroid, but I couldn't get anything to flash except the most recent BL. Now I can't even get boot loop. Goes straight to the bootloader with the error:
Reason boot: Hash of data does not match digest in descriptor. [2nd] (3)
Calculated Hash of (boot): 5C45D4E6BB, (VEMETA): 4514875C6A
SAMSUNG boot, N970USQU4DTH7, 33954676R
VBMETA N970USQU5ETLL, 36955741R
Not sure why it's failing to flash anything besides that one BL, any help is appreciated.
flatlander_2k5 said:
Okay, guys...
I've been flashing since the Touch Pro 2 days, but haven't much since bootloader tend to be locked down these days. That said, I know my way around Odin and such, so I don't need anyone to hold my hand. Anyways...
A friend brought me her N970U (ATT) with a no charge issues. Resolved that, but all it would do was boot loop. Her goal was simply to get pictures off of the device, so I was trying to retain data. Wiped cache and repaired apps to no avail, figured next step would be to dirty flash via Odin. I used the firmwares provided by @iBowToAndroid, but I couldn't get anything to flash except the most recent BL. Now I can't even get boot loop. Goes straight to the bootloader with the error:
Reason boot: Hash of data does not match digest in descriptor. [2nd] (3)
Calculated Hash of (boot): 5C45D4E6BB, (VEMETA): 4514875C6A
SAMSUNG boot, N970USQU4DTH7, 33954676R
VBMETA N970USQU5ETLL, 36955741R
Not sure why it's failing to flash anything besides that one BL, any help is appreciated.
Click to expand...
Click to collapse
It won't boot unless the full firmware matches the BL. So you need to flash the full TLL package, sans USERDATA and using HOME CSC
iBowToAndroid said:
It won't boot unless the full firmware matches the BL. So you need to flash the full TLL package, sans USERDATA and using HOME CSC
Click to expand...
Click to collapse
That's the issue, though. It fails trying to flash anything besides the BL. I've tried doing them all together and each individually. Re-downloaded a time or two in case of a bad file, but no dice
flatlander_2k5 said:
That's the issue, though. It fails trying to flash anything besides the BL. I've tried doing them all together and each individually. Re-downloaded a time or two in case of a bad file, but no dice
Click to expand...
Click to collapse
Can you be more specific? Any specific error messages etc?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
flatlander_2k5 said:
.
Click to expand...
Click to collapse
Try a different port, different cable, different computer, and also try Odin 3.14.1
Update: finally got all of the files to unzip correctly after using Frija to download them. Everything installed successfully via Odin, but it's giving a modem error on the device, saying it was flashed with unauthorised software.
flatlander_2k5 said:
Update: finally got all of the files to unzip correctly after using Frija to download them. Everything installed successfully via Odin, but it's giving a modem error on the device, saying it was flashed with unauthorised software.
Click to expand...
Click to collapse
Post a pic or screenshot of the error
I used the USC download since ATT isn't available, then used the home CSC for ATT provided from @iBowToAndroid
flatlander_2k5 said:
I used the USC download since ATT isn't available, then used the home CSC for ATT provided from @iBowToAndroid
Click to expand...
Click to collapse
How is ATT not available, if you used the CSC from the ATT package that I uploaded......?
(Not like it matters anyway, because all firmware is universal)
What I mean is that Frija says that ATT isn't a supported CSC, so I had to choose another one. I used all of the files from that download (BL, AP, CP) except the home CSC, for which I used your most recent one.
Flashed the home CSC that downloaded with the USC package and it's back to bootloop. If I go to the BL and repair apps, it gets to like 338 of 4xx and reboots. This phone is giving me a headache.
flatlander_2k5 said:
What I mean is that Frija says that ATT isn't a supported CSC, so I had to choose another one. I used all of the files from that download (BL, AP, CP) except the home CSC, for which I used your most recent one.
Click to expand...
Click to collapse
You can't get "my most recent" CSC without downloading the full firmware, because it's all one zip file. So obviously you downloaded the full firmware. So why didn't you just flash my whole firmware?
flatlander_2k5 said:
Flashed the home CSC that downloaded with the USC package and it's back to bootloop. If I go to the BL and repair apps, it gets to like 338 of 4xx and reboots. This phone is giving me a headache.
Click to expand...
Click to collapse
You need to flash the full TLL package. Doesn't matter if it's USC from Frija or ATT from me. Choose one package and flash all 4 files from it - AP, BL, CP, and HOME CSC
iBowToAndroid said:
You can't get "my most recent" CSC without downloading the full firmware, because it's all one zip file. So obviously you downloaded the full firmware. So why didn't you just flash my whole firmware?
Click to expand...
Click to collapse
The AP wouldn't unzip correctly, regardless of which mirror I used. Tried 7-zip and WinRar multiple days/times, got two errors unzipping every single time. Frija's download was the first one that I could unzip the whole package and it pass in Odin.
I am currently using every part of that download, which is how I got from the bootloader error back to the original boot loop issue.
flatlander_2k5 said:
The AP wouldn't unzip correctly, regardless of which mirror I used. Tried 7-zip and WinRar multiple days/times, got two errors unzipping every single time. Frija's download was the first one that I could unzip the whole package and it pass in Odin.
I am currently using every part of that download, which is how I got from the bootloader error back to the original boot loop issue.
Click to expand...
Click to collapse
If you're referring to my package, the AP is zipped up in the entire firmware package. So are you saying the entire package wouldn't unzip correctly?
iBowToAndroid said:
If you're referring to my package, the AP is zipped up in the entire firmware package. So are you saying the entire package wouldn't unzip correctly?
Click to expand...
Click to collapse
When I unzip your download, it gives two errors and Odin won't accept the AP. Per the pictures, I've tried using two different decompression tools.
flatlander_2k5 said:
When I unzip your download, it gives two errors and Odin won't accept the AP. Per the pictures, I've tried using two different decompression tools.
Click to expand...
Click to collapse
I still have the zip itself on hand (the same one that I uploaded), and it passes the 7-Zip archive test and also extracts without errors. You might have gotten a bad download - that can happen with AFH, if it gives you a janky mirror. Try downloading again, and try a different mirror if it gives you a slow one
EDIT: I just re-downloaded it from AFH, in case it was a bad upload. Tested fine and extracted fine, so it appears to have been a bad download
iBowToAndroid said:
I still have the zip itself on hand (the same one that I uploaded), and it passes the 7-Zip archive test and also extracts without errors. You might have gotten a bad download - that can happen with AFH, if it gives you a janky mirror. Try downloading again, and try a different mirror if it gives you a slow one
EDIT: I just re-downloaded it from AFH, in case it was a bad upload. Tested fine and extracted fine, so it appears to have been a bad download
Click to expand...
Click to collapse
I've downloaded it various times from different mirrors, thinking exactly that. I get the same error every time. Downloads from frija extracted without issue.
I'll note that this computer is a fresh OS install with no third-party virus protection or anything installed that might normally cause issues.
flatlander_2k5 said:
I've downloaded it various times from different mirrors, thinking exactly that. I get the same error every time. Downloads from frija extracted without issue.
I'll note that this computer is a fresh OS install with no third-party virus protection or anything installed that might normally cause issues.
Click to expand...
Click to collapse
Antivirus wouldn't cause zip errors like that. That can only be caused by a broken archive.
Here's my Google Drive mirror - try that
N970U_TLL_5.zip
drive.google.com
Related
ABOUT
-------------------
This is a package to return your Infuse 4G to a complete stock state with the AT&T UCLB3 Gingerbread release. It includes a PIT file to repartition your phone. Also, this resets the Custom Binary Download counter. Consider this a way to put the phone back to stock or to recover from a soft-brick without going all the way back to Froyo.
There is both a complete stock version and a rooted version below.
PACKAGES
-------------------
Stock UCLB3
UCLB3_Unbrick_1.1.zip
Stock UCLB3 with root
UCLB3_Unbrick_root_1.1.zip
The version with root works exactly like the above version, but adds root. To add CWM recovery to the rooted version, download a custom Gingerbread kernel from HERE or HERE and flash the zImage using SGS Kernel Flasher (found in the Play Store) on the phone. If you go this route for root and CWM, your Custom Binary Download counter will not show any custom binary activity.
INSTALL
-------------------
1.) Download and extract the zip package.
2.) Place phone in download mode.
3.) If needed, install latest Samsung USB drivers by installing Samsung Kies from HERE.
4.) Open the included Odin exe.
5.) If phone is detected, the window under ID:COM will turn yellow.
6.) Click on "PIT" to browse to and select infuse_gb.pit. Make sure that Re-Partition is selected.
7.) Click on "PDA" to browse to and select PDA_UCLB3.tar.md5.
8.) Click on "PHONE" to browse to and select PHONE_UCLB3.tar.md5.
9.) Click on "Start", and allow Odin to flash the phone. Do not unplug or power off the phone until Odin is finished.
10.) When the Odin dialogue reads "PASS!", the phone should reboot into the stock UCLB3 Setup Wizard.
FAQ
-------------------
1.) Should I do a software Factory Reset in settings after flashing this?
In the case that the Setup Wizard does not appear on the first boot, apps from a previous installation are still present, or you have other issues, go to Settings / Privacy and choose "Factory data reset" and then "Reset phone". This will ensure that the phone is completely reset, and that there is nothing left-over from a previous install to cause issues.
2.) I have rainbow distortion in recovery or in the boot animation. How can I get Gingerbread bootloaders to fix this?:
If you have rainbow distortion, you still have Froyo bootloaders. You can download THIS .rar file, extract using 7zip, and flash the tar.md5 package in Odin (use the pda slot). Flashing Gingerbread bootloaders will correct rainbow distortion in recovery and in the boot animation. Only flash these if you are having issues with rainbow distortion, and only if you have had success flashing other, less dangerous items in Odin.
3.) Does this package remove anything from the internal or external sdcard partitions?
This package does not remove anything from your internal or external sdcard partitions, so all of your user files stay on the phone. If you are using this to reset your phone to stock before selling it, etc., you should format personal storage by using options found under Settings / SD card and phone storage.
THANKS
-------------------
gtg465x for earlier unbrick packages and posts on using dd
imnuts for posts on how to create Odin images
Przekret for the Samsung UCLB3 leak
Everyone in the Infuse 4g XDA forum - for everything else
CHANGELOG
-----------------
6/13/2012 - v. 1.1:
Fixed a bug in the initial version of the UCLB3 Unbrick that caused the phone to lose APN settings. After flashing the new version of the UCLB3 Unbrick, the phone now reboots into the Setup Wizard and does not have APN issues. Thank you to hvega11 for the heads up on the bug.
The new version is in a zip archive called UCLB3_Unbrick_1.1.zip and contains a README.txt file with this changelog information. If the zip archive README.txt does not contain this changelog, then you are using the older version. It is suggested that you delete that version and download version 1.1.
If you downloaded and used the initial version, you might have lost APN and carrier settings immediately after flashing. Go to Settings / Privacy and do a factory reset. This will set you back to normal. The new version should not normally require a factory reset after flashing, but a factory reset in settings is suggested if you have any issues.
Nice job, JScott.
You da Odin Man!
Wow, Scott you are "working it" these past weeks, Thank You Sir for your work.
Added to ISET page..thx again
qkster said:
Nice job, JScott.
You da Odin Man!
Click to expand...
Click to collapse
Just trying to add some more options to help folks out. If you like Heimdall one-click, qkster has you covered. Can't do Heimdall or prefer Odin, we've got that too.
bigjoe2675 said:
Added to ISET page..thx again
Click to expand...
Click to collapse
Thanks bigjoe, just tryin' to keep you busy.
Sent from my SAMSUNG-SGH-I997 using Tapatalk 2
jscott30 said:
Thanks bigjoe, just tryin' to keep you busy. Sent from my SAMSUNG-SGH-I997 using Tapatalk 2
Click to expand...
Click to collapse
Always on the look out for the updates...
Just got off of work and i check xda to find a new port and a lb3 unbrick. I'm quiting work so i don't miss anything tomorrow. Excellent work on this. I'm tickled pink.
Sent from my SAMSUNG-SGH-I997 using xda premium
hey just a heads up I just flashed this and lost apn settings and network operators
hvega11 said:
hey just a heads up I just flashed this and lost apn settings and network operators
Click to expand...
Click to collapse
EDIT: This bug has been fixed, thanks hvega11 for the heads up!
Also, are you on AT&T or something else?
EDIT: Now that I'm on the PC, I can see that you are with AT&T. You can't see all of that in Tapatalk.
att theres just signal bars no att logo no h icon then in settings when you click apn its empty the click on network operators and its grayed out you cant add or change anything at this point
Alright, have you tried doing a factory reset in Settings / Privacy? I'm also going to test again here. Let me know what you get after factory reset, though.
EDIT: Just got finished with another test. I got the exact same behavior. After flashing the UCLB3 Unbrick, the phone had no APN settings or carrier information. After doing a factory reset in Settings / Privacy, all is back to normal. Do that if you haven't, and you'll be good to go.
Thanks for the heads up. I'm taking the file down until we get better results without having to do a factory reset in settings. I think that I know what is causing this.
jscott30 said:
Alright, have you tried doing a factory reset in Settings / Privacy? I'm also going to test again here. Let me know what you get after factory reset, though.
EDIT: Just got finished with another test. I got the exact same behavior. After flashing the UCLB3 Unbrick, the phone had no APN settings or carrier information. After doing a factory reset in Settings / Privacy, all is back to normal. Do that if you haven't, and you'll be good to go.
Thanks for the heads up. I'm taking the file down until we get better results without having to do a factory reset in settings. I think that I know what is causing this.
Click to expand...
Click to collapse
What do you think is causing this?
Occasionally, I also noted that a factory reset is also needed to clear out all other data. I did not noted the APN problem though.
qkster said:
What do you think is causing this?
Occasionally, I also noted that a factory reset is also needed to clear out all other data. I did not noted the APN problem though.
Click to expand...
Click to collapse
Since the PIT file repartitions the phone, the unbrick package has to have a dbdata.rfs file to rewrite that partition. Of course, neither this or the PIT file were included with the Przekret UCLB3 leak, so I dumped both from the phone, and edited the PIT file in a hex editor to remove several extra lines. The PIT file is good to go; I'm pretty sure that the issue lies in when I dumped the dbdata.rfs file from my phone. I live on the side of a mountain, and have very poor reception. I'm going to try to keep my personal settings and environment out of the mix when I dump the dbdata.rfs file. I'm trying a few things, but will let you know for sure after I test a theory.
Thanks jscott for the quick response sorry trying to do a factory reset didn't even cross my mind lol I had already odined back so I didn't get to try it.
Thanks again hvega11 for giving us a heads up about the APN issue / bug in the first version of the UCLB3 Unbrick.
The UCLB3 Unbrick is fixed and good to go. It was the dbdata.rfs file. I needed to dump it right after clearing cache and data (factory reset), and with the phone on the Setup Wizard screen. The tricky part was still having adb access at that point with USB debugging enabled. I remembered that you can wipe data and cache in CWM recovery and still keep USB debugging enabled, so I did that. At reboot, as soon as I saw the Setup Wizard, I got an adb shell and dumped the necessary files.
The phone starts at the Setup Wizard now after using the UCLB3 Unbrick, and doesn't have any APN issues.
EDIT: Version 1.1 has been uploaded. The APN bug has been fixed. This is working 100% for me. I've tested it over and over, and tried many different scenarios coming from ICS and Gingerbread roms. Every time I get a 100% working stock phone at the UCLB3 Setup Wizard.
EDIT 2: The only time that users might have to do a Factory Reset in settings is in the case that apps from a previous install are still present, or if any other issues arise - just to be sure that nothing is left-over from a previous installation. In most cases, the user won't have to do a Factory Reset in settings.
I need as many people as possible to test this and report back that it works. Thanks!
glad you got it fixed ill try it out tonight and report back
I've found that I personally prefer having an unbrick option that has root. So, I've updated the OP with a rooted UCLB3 Unbrick.
To get to CWM recovery from the rooted version: Flash any suitable custom Gingerbread kernel by using SGS Kernel Flasher. Then, it's back to flash, flash, flash, flash, flash, oops, unbrick, flash, flash, flash...
Neat thing is, that by not using download mode to install a custom kernel, the Custom Binary Download counter doesn't show any custom binary activity.
jscott30 said:
I've found that I personally prefer having an unbrick option that has root. So, I've updated the OP with a rooted UCLB3
Click to expand...
Click to collapse
Gotta have Root
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
A Unbrick with root. Very nice. Thank you a hundred times over. I feel like flashing something that i know i shouldn't just so i can use this.
Sent from my MB865 using xda premium
Hi guys,
i wonder you can help.
I used a software called dr fone to try and recover some messages from kik.
It was running and then it rebooted my S7, but then it was stuck at the samsung logo. I left it for a while and nothing was happening so I unplugged it and tried to restart. but now it always just boots to the samsung logo with a flashing notification light.
I've wiped the cache and that didn't help.
Does anyone know how I can solve this issue? Preferably, obviously, I want to keep all my data but if not then there's nothing I can do.
Will a factory reset do anything?
Can I flash a custom rom without root? And without unlocking bootloader? (I've no idea if the bootloader is unlocked or not)
Can I flash a Rom with odin(?) that will fix the device and keep the data?
Help please!
And a word of advice. Never ever use Dr Fone!
Flash stock over the top with ODIN 3.12.3 or newer, use HOME_CSC instead of CSC to avoid factory reset
*Detection* said:
Flash stock over the top with ODIN 3.12.3 or newer, use HOME_CSC instead of CSC to avoid factory reset
Click to expand...
Click to collapse
Thanks for the reply!
I've no idea what home_csc and csc is but I'll do some research!
Will any stock ROM do?
xxx889 said:
Thanks for the reply!
I've no idea what home_csc and csc is but I'll do some research!
Will any stock ROM do?
Click to expand...
Click to collapse
The stock firmware comes as 4 separate files you need to flash at the same time, there are two choices for CSC as above
CSC = Factory reset
HOME_CSC = No reset
Only choose one
Flash the stock ROM for your model S7, and your region / carrier
updato.com is probably the best place to find it, or the samfirm tool here on XDA
*Detection* said:
The stock firmware comes as 4 separate files you need to flash at the same time, there are two choices for CSC as above
CSC = Factory reset
HOME_CSC = No reset
Only choose one
Flash the stock ROM for your model S7, and your region / carrier
updato.com is probably the best place to find it, or the samfirm tool here on XDA
Click to expand...
Click to collapse
Thanks,
OK, I've downloaded ODIN3 v3.1.2.3, the One Click Root version.
I'm currently downloading the stock firmware from updato.com, it's 2.1 GB in size, does that sound right? And it's going to take over 2 hours to download!
I can't see the options for HOME_CSC and CSC yet in odin, maybe I'm come across that later in the process?
I'm just waiting now foe the download, but once the stock firmware is finally downloaded, do I just boot up the S7 using Vol Down + Home + Power to get to the Download Mode. I press Vol up to select continue and then ...
xxx889 said:
Thanks,
OK, I've downloaded ODIN3 v3.1.2.3, the One Click Root version.
I'm currently downloading the stock firmware from updato.com, it's 2.1 GB in size, does that sound right? And it's going to take over 2 hours to download!
I can't see the options for HOME_CSC and CSC yet in odin, maybe I'm come across that later in the process?
I'm just waiting now foe the download, but once the stock firmware is finally downloaded, do I just boot up the S7 using Vol Down + Home + Power to get to the Download Mode. I press Vol up to select continue and then ...
Click to expand...
Click to collapse
You need ODIN 3.12.3 or newer, unless that is a typo that is too old
Here is 3.12.7
Code:
https://mega.nz/#!jUgRiTSa!fnAVwr7yFi4dlPk4V0oQ5DuoFe3iiG0jH-ws91IHOPc
Yep, enter download mode, connect phone to PC USB, make sure the COM port is highlighted at the top of ODIN, then load the 4 firmware sections into ODIN
Hit start and wait for it to complete, you might find if that Dr Fone did more damage that you need to factory reset if the first try doesn't fix it
ODIN has the correct locations labelled for the specific parts of the ROM
BL
AP
CP
CSC
Each section of firmware is labelled accordingly, match them up
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
*Detection* said:
You need ODIN 3.12.3 or newer, unless that is a typo that is too old
Here is 3.12.7
Code:
https://mega.nz/#!jUgRiTSa!fnAVwr7yFi4dlPk4V0oQ5DuoFe3iiG0jH-ws91IHOPc
Yep, enter download mode, connect phone to PC USB, make sure the COM port is highlighted at the top of ODIN, then load the 4 firmware sections into ODIN
Hit start and wait for it to complete, you might find if that Dr Fone did more damage that you need to factory reset if the first try doesn't fix it
ODIN has the correct locations labelled for the specific parts of the ROM
BL
AP
CP
CSC
Each section of firmware is labelled accordingly, match them up
Click to expand...
Click to collapse
Thanks again!
It was a typo for ODIN but I think I downloaded the wrong version anyway as I don't think the one click root version is the right one? It's strange though, I went to https://odindownload.com site, which i thought was the official site and their latest version is 3.12.3? And you've linked me to 3.12.7. I don't have root but this version should still be OK?
I think I get the home.csc now. It's just a file from the stock firmware that I just select to go in the CSC box.
I'll just wait for the download now and I'll let you know how I get on. And thanks so much for all your help so far.
*Detection* said:
You need ODIN 3.12.3 or newer, unless that is a typo that is too old
Here is 3.12.7
Code:
https://mega.nz/#!jUgRiTSa!fnAVwr7yFi4dlPk4V0oQ5DuoFe3iiG0jH-ws91IHOPc
Yep, enter download mode, connect phone to PC USB, make sure the COM port is highlighted at the top of ODIN, then load the 4 firmware sections into ODIN
Hit start and wait for it to complete, you might find if that Dr Fone did more damage that you need to factory reset if the first try doesn't fix it
ODIN has the correct locations labelled for the specific parts of the ROM
BL
AP
CP
CSC
Each section of firmware is labelled accordingly, match them up
Click to expand...
Click to collapse
In case you're not here when I have finished the download, can you tell me if I have to change anything in the options in ODIN or leave as default? There's only "Auto Reboot" and "F. Reset Time" selected.
Also, at the moment, my phone is connected to my laptop but is turned off. The com box in odin is
0:[COM3] and is highlight a sort of bluey colour. Does that mean it's connected properly or does the phone need to be turned on for it to highlight to a different colour?
Thanks
xxx889 said:
In case you're not here when I have finished the download, can you tell me if I have to change anything in the options in ODIN or leave as default? There's only "Auto Reboot" and "F. Reset Time" selected.
Also, at the moment, my phone is connected to my laptop but is turned off. The com box in odin is
0:[COM3] and is highlight a sort of bluey colour. Does that mean it's connected properly or does the phone need to be turned on for it to highlight to a different colour?
Thanks
Click to expand...
Click to collapse
Well the phone needs to be turned on to flash with ODIN anyway so..
Don't change anything in ODIN, leave it as default
Use the newest version of ODIN for best results
*Detection* said:
Well the phone needs to be turned on to flash with ODIN anyway so..
Don't change anything in ODIN, leave it as default
Use the newest version of ODIN for best results
Click to expand...
Click to collapse
Yep, but you mentioned that to make sure that the com port highlighted and I'm just wondering if that is what you meant or should it change to a different highlight when I turn the phone on to connect? The log also already says <ID:0/003> Added.
I will be using your version of ODIN!
Thanks
xxx889 said:
Yep, but you mentioned that to make sure that the com port highlighted and I'm just wondering if that is what you meant or should it change to a different highlight when I turn the phone on to connect? The log also already says <ID:0/003> Added.
I will be using your version of ODIN!
Thanks
Click to expand...
Click to collapse
Well it doesn't matter what colour it is when the phone is off lol
It only matters that the COM port is highlighted when the phone is ON and connected, to show that ODIN can see the phone
But either way, pressing start and the phone responding is a sure way to know too
*Detection* said:
Well it doesn't matter what colour it is when the phone is off lol
It only matters that the COM port is highlighted when the phone is ON and connected, to show that ODIN can see the phone
But either way, pressing start and the phone responding is a sure way to know too
Click to expand...
Click to collapse
Right, Odin has finished.
It rebooted, took a little while to get past the samsung logo. Then sort of reached the home screen, but then it has crashed, become unresponsive. I can't get into the phone. Can't unlock it.
When it first reached the home screen, it said that
com.sec.epdg has stopped
ims service has stopped
and now it's just black screen, buttons don't appear to work also, when I first saw the home screen, a notification said that the "android is upgrading" with a progress bar.
Any ideas? Do i just wait?
xxx889 said:
Right, Odin has finished.
It rebooted, took a little while to get past the samsung logo. Then sort of reached the home screen, but then it has crashed, become unresponsive. I can't get into the phone. Can't unlock it.
When it first reached the home screen, it said that
com.sec.epdg has stopped
ims service has stopped
and now it's just black screen, buttons don't appear to work also, when I first saw the home screen, a notification said that the "android is upgrading" with a progress bar.
Any ideas? Do i just wait?
Click to expand...
Click to collapse
Did you download the latest firmware? As in Nougat?
Possible if you downloaded an older version it would cause the crashing because newer apps and system apps vs older OS don't work well together
You could try booting into recovery and clearing CACHE
If that doesn't work and you definitely flashed the latest firmware, you might need to factory reset, but connect your phone to the PC while it is booted and see what you can recover via USB if it will let you
You could try safe mode too
https://us.community.samsung.com/t5...leshoot-problems/m-p/13707/highlight/true#M37
*Detection* said:
Did you download the latest firmware? As in Nougat?
Possible if you downloaded an older version it would cause the crashing because newer apps and system apps vs older OS don't work well together
You could try booting into recovery and clearing CACHE
If that doesn't work and you definitely flashed the latest firmware, you might need to factory reset, but connect your phone to the PC while it is booted and see what you can recover via USB if it will let you
You could try safe mode too
https://us.community.samsung.com/t5...leshoot-problems/m-p/13707/highlight/true#M37
Click to expand...
Click to collapse
Yeah, I downloaded latest version Nougat version from but looking at it again now, I just chose the first region in the list which was United Kingdom (BTU), but there are other versions, which i think are for different networks like VOD, VIR, but also XEU and H3G which I'm not sure what they are. Mine is unlocked so does it matter which one U chose? (I don't know what network, if any, it was locked to before).
Do you know which one I should choose or does it not make any difference?
I have cleared the cache and no change.
xxx889 said:
Yeah, I downloaded latest version Nougat version from but looking at it again now, I just chose the first region in the list which was United Kingdom (BTU), but there are other versions, which i think are for different networks like VOD, VIR, but also XEU and H3G which I'm not sure what they are. Mine is unlocked so does it matter which one U chose? (I don't know what network, if any, it was locked to before).
Do you know which one I should choose or does it not make any difference?
I have cleared the cache and no change.
Click to expand...
Click to collapse
No it won't be due to that, BTU and XEU are the unbranded versions, the others will have carrier bloatware apps and branding on them
You could try flashing once more, but I think you're gonna end up having to reset unfortunately
*Detection* said:
No it won't be due to that, BTU and XEU are the unbranded versions, the others will have carrier bloatware apps and branding on them
You could try flashing once more, but I think you're gonna end up having to reset unfortunately
Click to expand...
Click to collapse
I'm downloading the XEU version as we speak.... I thought it was so close...
Samsung smart switch can't connect to the phone.
xxx889 said:
I'm downloading the XEU version as we speak.... I thought it was so close...
Samsung smart switch can't connect to the phone.
Click to expand...
Click to collapse
If you already have BTU there's no point flashing XEU, I meant try flashing BTU again, I've once run into a problem that required me to flash the same stock ROM twice before it would boot correctly back in the Marshmallow days
Difference between XEU and BTU = when you receive OTA updates, nothing more
Moral of the story, always backup whatever is important, especially if you're about to mess about with something like Dr Fone
*Detection* said:
If you already have BTU there's no point flashing XEU, I meant try flashing BTU again, I've once run into a problem that required me to flash the same stock ROM twice before it would boot correctly back in the Marshmallow days
Difference between XEU and BTU = when you receive OTA updates, nothing more
Moral of the story, always backup whatever is important, especially if you're about to mess about with something like Dr Fone
Click to expand...
Click to collapse
I'm going to try flashing them both a couple of times if need be before resorting to factory reset.
How would I do a factory reset? Would it be with just using the CSC file, rather then the HOME_CSC in ODIN?
My moral of the story is DO NOT USE DR FONE EVER! Dangerous, pathetic software.
Ironic that I tried to use this software to recover data, only for it to lose all my data!
xxx889 said:
I'm going to try flashing them both a couple of times if need be before resorting to factory reset.
How would I do a factory reset? Would it be with just using the CSC file, rather then the HOME_CSC in ODIN?
My moral of the story is DO NOT USE DR FONE EVER! Dangerous, pathetic software.
Ironic that I tried to use this software to recover data, only for it to lose all my data!
Click to expand...
Click to collapse
Yea, CSC or enter recovery and reset from there
Yep, I would avoid any software like that, the name alone sounds alarm bells to me
Stick to XDA projects, or software recommended by devs/long term members here
and apps are
*Detection* said:
Yea, CSC or enter recovery and reset from there
Yep, I would avoid any software like that, the name alone sounds alarm bells to me
Stick to XDA projects, or software recommended by devs/long term members here
Click to expand...
Click to collapse
Flashing the XEU firmware worked! I don't know whether it was the different versions or just flashing it again made the difference but I don't care. I lost some system settings and my keyboard but I think most of my data and apps are still there.
Thank you very much for your help!
Hey guys, I really screwed up big time with my S7. My model is the SM-G930F. I have numbered my mistakes below so it is easier to follow.
1) I wanted to root my phone, so I followed the guide for HighonAndroid on youtube.
2) Fast forward, got TWRP and flashed Magisk root v16 and samsung anti-root removal 2.4.
3) Restarted phone and got this message along the lines of "integrity of phone has been damaged... please factory reset"
4) I advanced factory reset, and also accidentally ticked the software reset as well :crying:
5) Phone is bricked, and stuck in bootloading error. Cannot be turned off, it would just continue to recycle the Samsung S7 screen on repeat until put into TWRP mode...
6) Can only assess download mode and TWRP mode
If you are still following, this is where I am stuck ATM. I just want a working phone at this point...
7) Download official 7.0 nougat software for my phone model.
8) Odin the firmware over however the message stays stuck at this: https://imgur.com/a/UMQPw
9) Cry
If anybody can help that will be great, thanks!
Looks like Odin is not signing a com port to the phone.
Drivers are installed? Tried different usb cables and usb ports?
audit13 said:
Looks like Odin is not signing a com port to the phone.
Drivers are installed? Tried different usb cables and usb ports?
Click to expand...
Click to collapse
The phone stays connected, but the second I flash my phone just reboots.
You're not flashing BL, CP, and CSC?
I was under the impression S7 was beyond the time of using single tar/md5 files, you should have 4 separate files (BL, CP, CSC, AP). Where'd you get the firmware?
Try updato.com or sammobile.com, even the oldest S7 firmware I've downloaded still came with the 4 firmware files.
Beanvee7 said:
I was under the impression S7 was beyond the time of using single tar/md5 files, you should have 4 separate files (BL, CP, CSC, AP). Where'd you get the firmware?
Try updato.com or sammobile.com, even the oldest S7 firmware I've downloaded still came with the 4 firmware files.
Click to expand...
Click to collapse
Yes I got the file from sammobile. I have tried flashing the 4 files however alas, it again just reboots my phone. I will follow up with an image when I get home and try it out again.
Beanvee7 said:
I was under the impression S7 was beyond the time of using single tar/md5 files, you should have 4 separate files (BL, CP, CSC, AP). Where'd you get the firmware?
Try updato.com or sammobile.com, even the oldest S7 firmware I've downloaded still came with the 4 firmware files.
Click to expand...
Click to collapse
Yeah here we go: https://imgur.com/a/FF0Rd
Still does not work. It continues to reboot. Tried different computers the phone will just reboot. Is there any hope left? I can access TWRP, meaning is it possible to restore/flash a backup from another user?
You can try Smart Switch which is the official method of a factory flash.
Otherwise for Odin if I recall correctly the latest firmware will chuck a fit if you aren't flashing the right firmware for your country, since the DRAG bootloader is meant to be more locked down.
You could also try different Odin versions maybe https://forum.xda-developers.com/showthread.php?t=2711451
You could try a stock ROM flash via zip like super stock or superman choosing clean install. Would be easier than trying to orchestrate a backup from someone.
Is there any errors that I have now seem consistent with anybody else's issue? Something like I might be flashing the wrong firmware into my phone, as a result the phone just reboots in download mode?
I have tried using both the new and old versions of odin and it still has the same result.
I am using the phone model SM-G930FZDAXSG
Really thanks a lot guys. Just having you guys readily available took a lot of stress off my chest. Someone cares
The issue has just been resolved! Yey. The problem was not running odin in administrator mode. As a result, my phone would just reboot instantaneously after flashing.
I'm getting a problem where everytime I try to call someone or I receive a call, my SIM cards become undetected, the phone crashes after a short time and then doesn't detect SIM cards again, and Samsung or Google backups stop working, and all Samsung account related apps refuse to work. Only fixable after multiple factory resets.
After some investigation, I found that the Baseband and IMEI of the phone seem to be "unknown" whenever this occurs.
Is there a reason to this, or even a fix?
ZaneJulien said:
I'm getting a problem where everytime I try to call someone or I receive a call, my SIM cards become undetected, the phone crashes after a short time and then doesn't detect SIM cards again, and Samsung or Google backups stop working, and all Samsung account related apps refuse to work. Only fixable after multiple factory resets.
After some investigation, I found that the Baseband and IMEI of the phone seem to be "unknown" whenever this occurs.
Is there a reason to this, or even a fix?
Click to expand...
Click to collapse
same with my A125F variant, try to reset your device and it will fix the problem
and don't update your device with the build number of A125FXXU1BUG6, i think there's is a bug with that update..
You were completely right! It WAS the new update. I flashed the previous firmware and my SIMs work perfectly now! I've turned off auto-update in the normal area and developer settings too, hopefully can avoid it till it's fixed sometime. Thanks again!
I found a way how to fix it... try to flash the A125FXXU1BUG6 firmware version together with the pit file and it will fixed the problem
Hi all,
That sounds exactly like the problem I have
When I ROOT, I unblock BOOTLOADER, the connection to the network is blocked.
When I ROOT, I unblock BOOTLOADER, the connection to the network is blocked: / Bootloader unlocked = connection blocking
forum.xda-developers.com
(I was assuming it was due to the unlocking)
I was using Frija to get the latest (bugged?!) version - I was unable to find the previous one
Baseband A125FXXU1BUE1 / Build A125FXXU1BUE3 (XSA)
Could anyone please describe where to get an older version / the pit file?
Thanks a lot for that!
is your device is A125F?
A125F pit file i used this pit to fix the problem
A12_EUR_OPEN
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Jayke770 said:
A125F pit file i used this pit to fix the problem
A12_EUR_OPEN
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Click to expand...
Click to collapse
Thanks a lot, if I cannot find the lower firmware (it's on Samfrew, but downloading will take ages...), I'll give it a try. And good to have it if I get a bootloop!
Whoooo? said:
Thanks a lot, if I cannot find the lower firmware (it's on Samfrew, but downloading will take ages...), I'll give it a try. And good to have it if I get a bootloop!
Click to expand...
Click to collapse
i have an app that can download latest firmware for Samsung
or just try this website https://www.google.com/url?sa=t&sou...0QFnoECEIQAQ&usg=AOvVaw0neIA-O_nYmWom070upF4v
Just as a note for everyone who has the same problem -
I could fix this without the pit file, all that was required was flashing the complete (previous) firmware with Odin.
So not just the AP file but all the other ones as well (AP, BL, CP, CSC). Maybe a modem issue?
Hey guys, i tried everything, but have not been able to fix it.
I have the SM-A125W
and I tried flashing:
Samfw.com_SM-A125W_RWC_A125WVLU2AUFA_fac
Samfw.com_SM-A125W_RWC_A125WVLU2AUG5_fac
Samfw.com_SM-A125W_XAC_A125WVLU2AUFA_fac
Samfw.com_SM-A125W_XAC_A125WVLU2AUG5_fac
and used the pit file:
from: https://www.full-repair-firmware.com/p/galaxy-a12.html
and also, checked repartition option in odin,
When i make a phone call, and hang up, the sim card and phone number shows UNKNOWN
and when i perform a factory reset, it comes back and then goes again when i make a phone call.
Are we able to use the SP flash tool on this phone?
What seems to be the problem here?
I had this problem as well after updating firmware to A125FXXU1BUG6. I could not find a way to repair the IMEI until I found this file.
All I did was flash the tar file using odin in CP. I didn't need to flash other firmware packages or anything else.
Voilà!! Enjoy!
andef said:
I had this problem as well after updating firmware to A125FXXU1BUG6. I could not find a way to repair the IMEI until I found this file.
All I did was flash the tar file using odin in CP. I didn't need to flash other firmware packages or anything else.
Voilà!! Enjoy!
Click to expand...
Click to collapse
Does it also work with the new update A125FXXU1BUI3?
andef said:
I had this problem as well after updating firmware to A125FXXU1BUG6. I could not find a way to repair the IMEI until I found this file.
All I did was flash the tar file using odin in CP. I didn't need to flash other firmware packages or anything else.
Voilà!! Enjoy!
Click to expand...
Click to collapse
Allehandro said:
Does it also work with the new update A125FXXU1BUI3?
Click to expand...
Click to collapse
THANKS SOOOO MUCH. IT WORKED. IT WORKED WITH THE NEW UPDATE AND IMEI AND BASEBAND ARE BOTH WORKING. LIFESAVER!!!
andef said:
I had this problem as well after updating firmware to A125FXXU1BUG6. I could not find a way to repair the IMEI until I found this file.
All I did was flash the tar file using odin in CP. I didn't need to flash other firmware packages or anything else.
Voilà!! Enjoy!
Click to expand...
Click to collapse
Allehandro said:
Does it also work with the new update A125FXXU1BUI3?
Click to expand...
Click to collapse
I've flashed the new A125FXXU1BUJ4 November security update and the bug is still there but I was able to flash the same IMEI/Baseband repair file and it worked. THANKS FOR THAT.
andef said:
I had this problem as well after updating firmware to A125FXXU1BUG6. I could not find a way to repair the IMEI until I found this file.
All I did was flash the tar file using odin in CP. I didn't need to flash other firmware packages or anything else.
Voilà!! Enjoy!
Click to expand...
Click to collapse
However, this file according to your link now becomes paid, please re-upload into XDA
i already fix my a12
I am using a125n. On Android 11, Clearing /mnt/vendor/nvdata, flashing with pit, re-locking does not work. But flashing android 10 CP makes the phone work well.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you're not sure it a software fail, "Unknown" Baseband probably cause by faulty MT6177mv chip on mainboard. Usually damage by warter or falling, and it just need to reflow or replace a new one.both imei will re-apear when the baseband chip working.
Talking from personnal experient
I haven't used my Tab 2 (P5110) in a long time. I rely on my phone quite a bit instead.
Recently, I've been doing a bit of IoT stuff and though the Tab would make an excellent remote controller.
When I boot it, it shows the Samsung logo and goes no further.
Is there anything I can do to recover it, please?
I can get it into Odin mode, but I can't remember what can be done from there.
Can someone just steer me to a refresher, please?
Use recovery and do factory reset
KDMcM said:
I haven't used my Tab 2 (P5110) in a long time. I rely on my phone quite a bit instead.
Recently, I've been doing a bit of IoT stuff and though the Tab would make an excellent remote controller.
When I boot it, it shows the Samsung logo and goes no further.
Is there anything I can do to recover it, please?
I can get it into Odin mode, but I can't remember what can be done from there.
Can someone just steer me to a refresher, please?
Click to expand...
Click to collapse
You can flash TWRP from Odin and flash Custom Rom
drnightshadow said:
Use recovery and do factory reset
Click to expand...
Click to collapse
With apologies, if I knew what "use recovery" meant, I probably would have already done it.
Can you help, please?
hmd_msrf_k said:
You can flash TWRP from Odin and flash Custom Rom
Click to expand...
Click to collapse
I've downloaded twrp-2.8.5.0-p5110.tar.
The guide on the TWRP download site says I should install Odin and look for the "PDA tab or button". I have Odin 3.14.1 and the buttons are BL, AP, CP, CSC and USERDATA.
Elsewhere, here, I'm told to use AP. Is AP the correct / safe option?
Thanks.
KDMcM said:
I've downloaded twrp-2.8.5.0-p5110.tar.
The guide on the TWRP download site says I should install Odin and look for the "PDA tab or button". I have Odin 3.14.1 and the buttons are BL, AP, CP, CSC and USERDATA.
Elsewhere, here, I'm told to use AP. Is AP the correct / safe option?
Thanks.
Click to expand...
Click to collapse
Yes you can use AP, but why are you using too old recovery?.
New Version of TWRP is available and you should use that one
hmd_msrf_k said:
Yes you can use AP, but why are you using too old recovery?.
New Version of TWRP is available and you should use that one
Click to expand...
Click to collapse
It's the most recent one I could find as a .tar file. The more recent ones seem to be .img.
Download TWRP for p5110
Download TWRP Open Recovery for p5110
eu.dl.twrp.me
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It's not looking good for the good guys. Is this a dead loss?
Thanks.
Try different Odin, oldest is better
KDMcM said:
View attachment 5805273
Click to expand...
Click to collapse
Try Odin 3.07, it has PDA option, it may work
KDMcM said:
I haven't used my Tab 2 (P5110) in a long time. I rely on my phone quite a bit instead.
Recently, I've been doing a bit of IoT stuff and though the Tab would make an excellent remote controller.
When I boot it, it shows the Samsung logo and goes no further.
Is there anything I can do to recover it, please?
I can get it into Odin mode, but I can't remember what can be done from there.
Can someone just steer me to a refresher, please?
Click to expand...
Click to collapse
use old odin/heimdall and flash stock firmware
$cronos_ said:
use old odin/heimdall and flash stock firmware
Click to expand...
Click to collapse
Where can I get a heimdall Windows Binary, please?
Also, not sure where I can get stock firmware!
Thanks!
hmd_msrf_k said:
Try Odin 3.07, it has PDA option, it may work
Click to expand...
Click to collapse
Interesting. First try the progress bar went to about 80% and I thought it was working. Then it failed.
Second try ... waited for ages then failed outright.
Any other thoughts, please?
i
KDMcM said:
Interesting. First try the progress bar went to about 80% and I thought it was working. Then it failed.
Second try ... waited for ages then failed outright.
Any other thoughts, please?
View attachment 5807221
Click to expand...
Click to collapse
Interesting.
I have a couple of suggestions
1) Try to place the tar file in a folder without any spaces in the name in it and try to flash it again
2) Try to download the latest TWRP tar file from here https://dl.twrp.me/espressowifi/ and flash it with Odin 3.14.1
If none of this work, then I have no idea
KDMcM said:
Interesting. First try the progress bar went to about 80% and I thought it was working. Then it failed.
Second try ... waited for ages then failed outright.
Any other thoughts, please?
View attachment 5807221
Click to expand...
Click to collapse
use the latest odin, (in the latest it is called ap instead of pda partition)