Greetings.
I didn't post in very long time on this forum,since I could handle most of the problems on my own,now I need some andvanced tips and advices,so I'm reporting in.
I bough myself a Samsung Galaxy S4 Black Edition last year here in Bosnia and Hercegovina.Beautiful phone,never got a scratch on it,It had Android 4.2.2 Jelly Bean out of the box but all of the features from basic S4 except one,it couldn't update firmware to Lolipop 5.0.1.
That used to bother me,since I had much older devices that supported JB and this phone was just special,enough that I couldn't let it be my daily driver having unused potential,so i threw myself at work(which will later prove a very bad decision).
I checked for OTA updates in the settings and that option would litteraly do nothing,providing no info,or searching for new updates.
Smash that Build number,got into developer mode,toggle USB debugging,Install Kies on PC,run it as Admin,download latest drivers,connect the device,Firmware update asks for IMEI and s/n,type them in,says to check my s/n and IMEI,do that few times under different compatibility options,still the same.
I thought it must be something bad with data/catche so i reset to recovery mode and wipe them out,setup the phone,enter the OTA update for second time,it shows me "Your device have been modified, Software updates are not available", check device status and it states "Samsung",after several attempts it sometime said "Modified" sometimes "Samsung",Kies didn't recognise the device through all this process.
I was already lost here,but I thought,hell Kies isn't working,neather is OTA,i could flash using Odin,that might do the trick.
Went to Sammobile,downloaded latest drivers and Odin,found one Firmware that I though was compatible.,unbloked them in properties and set to rin as Admin.
Uninstalled Kies and checked for leftover drivers again,and it was all clear to go,ran odin,mounted firmware,set device in download mode and started flashing but Odin poped out "complete(write) operation fail" error.
Didn't want to try fixing it,went straight back to SM and downloaded two other firmwares,one said "complete(write) operation fail",and the other "Re-Partition operation failed",so I thought Odin was bad,since I checked on two PC's with several USB ports.
Download two more versions of Odin and find a stock s4 PIT file here somewhere for repartrition error.
Extracted everything,unblocked and ran with privilegies,same thing on both Odin versions,except that only Odin 3.07 could flash the pit file alone with no problems it passed.
Next time i ran download mode i tried to flash the firmware write fail came up again,extracted recovery and flashed it alone,worked like a charm,so I tried flashing once again,it proceedes a little further with same write error.
Reset the phone to wipe data and catche and it goes into "Firmware Upgrade Encountered An Issue Error",Install kies,it still doesn't recognise the phone.
Out of option right now I go for search of alternative recovery software,and I found the famous "Dr.Fone" (how stupid I was to not read all those,"if it wasn't for this software my phone would die" comments)
Installed it,ran recovery my phone shuts down and displays "set warranty bit: kernel message",from this point nothing works except recovery mode,so I install CWM recovery and flash a Custom ROM,now only this option that sets my phone in working order and I want to recover it's Firmware back,Anyone that could help me with this issue,or had it solved before?
Atleast give it a try.
this amount of pain can't be titled
Drow_Warlord said:
Greetings.
I didn't post in very long time on this forum,since I could handle most of the problems on my own,now I need some andvanced tips and advices,so I'm reporting in.
I bough myself a Samsung Galaxy S4 Black Edition last year here in Bosnia and Hercegovina.Beautiful phone,never got a scratch on it,It had Android 4.2.2 Jelly Bean out of the box but all of the features from basic S4 except one,it couldn't update firmware to Lolipop 5.0.1.
That used to bother me,since I had much older devices that supported JB and this phone was just special,enough that I couldn't let it be my daily driver having unused potential,so i threw myself at work(which will later prove a very bad decision).
I checked for OTA updates in the settings and that option would litteraly do nothing,providing no info,or searching for new updates.
Smash that Build number,got into developer mode,toggle USB debugging,Install Kies on PC,run it as Admin,download latest drivers,connect the device,Firmware update asks for IMEI and s/n,type them in,says to check my s/n and IMEI,do that few times under different compatibility options,still the same.
I thought it must be something bad with data/catche so i reset to recovery mode and wipe them out,setup the phone,enter the OTA update for second time,it shows me "Your device have been modified, Software updates are not available", check device status and it states "Samsung",after several attempts it sometime said "Modified" sometimes "Samsung",Kies didn't recognise the device through all this process.
I was already lost here,but I thought,hell Kies isn't working,neather is OTA,i could flash using Odin,that might do the trick.
Went to Sammobile,downloaded latest drivers and Odin,found one Firmware that I though was compatible.,unbloked them in properties and set to rin as Admin.
Uninstalled Kies and checked for leftover drivers again,and it was all clear to go,ran odin,mounted firmware,set device in download mode and started flashing but Odin poped out "complete(write) operation fail" error.
Didn't want to try fixing it,went straight back to SM and downloaded two other firmwares,one said "complete(write) operation fail",and the other "Re-Partition operation failed",so I thought Odin was bad,since I checked on two PC's with several USB ports.
Download two more versions of Odin and find a stock s4 PIT file here somewhere for repartrition error.
Extracted everything,unblocked and ran with privilegies,same thing on both Odin versions,except that only Odin 3.07 could flash the pit file alone with no problems it passed.
Next time i ran download mode i tried to flash the firmware write fail came up again,extracted recovery and flashed it alone,worked like a charm,so I tried flashing once again,it proceedes a little further with same write error.
Reset the phone to wipe data and catche and it goes into "Firmware Upgrade Encountered An Issue Error",Install kies,it still doesn't recognise the phone.
Out of option right now I go for search of alternative recovery software,and I found the famous "Dr.Fone" (how stupid I was to not read all those,"if it wasn't for this software my phone would die" comments)
Installed it,ran recovery my phone shuts down and displays "set warranty bit: kernel message",from this point nothing works except recovery mode,so I install CWM recovery and flash a Custom ROM,now only this option that sets my phone in working order and I want to recover it's Firmware back,Anyone that could help me with this issue,or had it solved before?
Atleast give it a try.
Click to expand...
Click to collapse
Day#4 Fail compilation
I see that this gets no response,but I'll continue this thread just in case I fix this and somebody else gets into same problem themselves.
I mentioned before that I somehow flashed custom ROM over CWM and that helped my phone boot into working state after bootloop error caused by greatest Android software there is on the internet,the legendary "Dr.Fone"
The Custom rom used was "[OFFICIAL][i9500][5.1.x] CyanogenMod 12.1 for Samsung Galaxy S4 [NIGHTLY]" From xda user: Alberto96 (thank you friend).
After several other failed attempts of implementing Stock firmware on this bricked device over the PC,I got to the point where I think that it's literally imposible to make it work since I tried so many ways and patterns of installation with no difference in the outcome results whatsoever.
I took a moment to rethink my strat over this and googled other ways of flashing that firmware without using PC.
Found 2 possible solutions that I'm trying to make use of,first is Odin Mobile and the Other is FlashFire.
Since both require rooted devices,finding way to root bricked S4 wasn't a very pleasant experiance,since flashing SuperSU through CWM recovery didn't work,Odin managed to flash me nice Autoroot from Chainfire over the custom ROM I installed before,I found a problem even there since the I9505 autoroot wouldn't work,the custom firware had changed the phone model to I9507 that I downloaded the Autoroot for,was a confusing issue,but I managed to root it anyways.
Page I used for this purpose was Chainfire Autoroot database(sorry if I'm violating forum rules but I think this could be left here without further discussion about it).
After rebooting the device I downloaded Rootcheck software along with SuperSU and FlashFire which confirmed that it's fully unlocked/rooted.
Now I'm recharging my phone so I can later tonight go ahead and transfer firmware to it's SD card and try to flash it once again with FlashFire,last option I'm thinking of as of now if this wouldn't have any progress is to download Odin mobile and try another flash,I'm running out of ideas on this one.
Sorry for the long posts,but these get no respose so who cares.
Related
Hi,
I've been using Linux for over ten years but am a newb with tablets and flashing etc. Thought I'd be able to stick Linux on my P3110 but soon realized I needed to take baby steps first. So I tried Heimdall to root my device according to the instructions on androidauthority.com galaxy-tab-2-7-0-p3110-root-clockworkmod-recovery-96473
This did not work so despite many attempts so I eventually filed a bug report for Heimdall which was addressed in the wip/1.4RC3 branch... which I may have got a bit too eager to use before it was quite ready. I rebuilt despite the warning the build files weren't then updated. I tried it anyway and it didn't seem to work, but third time or so lucky it appeared to work. Unfortunately the P3110 reset but stayed stuck on the Samsung logo.
I've now got a Vista install inside VirtualBox and have sucessfully used Odin to flash CWM Recovery onto it, and then used CWM recovery to install some other root package ( tips4tab.com how-to-root-and-install-clockworkmod-recovery-on-samsung-galaxy-tab-2-7-0-wi-fi-gt-p3110 ) but still have the same result: the P3110 stays stuck on the logo.
So all the while I've been researching how to do this I've seen hints the solution is to install the stock rom onto the device, but many solutions seem to involve Kies which from my experiments thus far won't recognize a non-working device such as mine.
Anyway, I eventually found sammobile.com and am currently downloading P3110XXCLK7_P3110OXACLK7_BTU.zip which is the latest firmware for my P3110 (UK) which from what I believe needs to be copied to an SD card and the SD inserted into the P3110.
My question is does this sound like the right thing to do to get my device working again?
Yes extract the 1.1gb P3110XXCLK7_P3110OXACLK7_HOME.tar.md5 from the Zip and use Odin to install it to the P3110. It takes some time and afterward you'll see a yellow android dancing the dance of life with a blue data stream. After rebooting the device will then take you through the initial setup stage again
good
Yea just what dat guy is sayin :good:
Hey guys, I just got my Note Pro a week ago and just started looking into rooting. I keep getting a notification about a 128mb stability update. I would assume it's gonna update to the latest build but I'm not sure what the latest build is or if it'll be rootable afterwords. my current build is KOT49H.P900UEU1ANAE. What is the latest build #? Is there a list of updates somewhere detailing what the improvements are? I just want to root, debloat, turn off OTA and remove KNOX.
Edit: sorry forgot to mention it's just the wife model SM-P900
So 48 views and not one person can tell me the latest build# ? I'll figure out the rest.
Sent from my SM-N900V using Tapatalk
Have you checked SamMobile?
http://www.sammobile.com/firmwares/database/SM-P900/XAR/
How i got there:
http://www.sammobile.com
1. Click Firmware on the top.
2. Click the greyed out firmware database link under the blue banner.
3. Under "Select your firmware" I picked Tablet-->Android-->SM-P900....-->Cellular South (which matches the US variants)
muzzy996 said:
Have you checked SamMobile?
http://www.sammobile.com/firmwares/database/SM-P900/XAR/
How i got there:
http://www.sammobile.com
1. Click Firmware on the top.
2. Click the greyed out firmware database link under the blue banner.
3. Under "Select your firmware" I picked Tablet-->Android-->SM-P900....-->Cellular South (which matches the US variants)
Click to expand...
Click to collapse
Thanks muzzy! I had already been to SamMobile but all it had was foreign countries listed. I didn't know about Cellular South being the US version. I'll look again.
Edit: oh look a list of the updates and release dates! My Wi - fi reception seems slow, do any of the update fix that?
I honestly can't say. I'm on NC5 which is dated back in April and have no major issues.
I'm rooted and debloated though, not that this would impact the wifi performance . .
48 views doesn't mean 48 users. About 44 of those are Google Content Crawler, which is Google search engine's bots crawling the net for content to display in google.com. It is an automated process.
Samsung doesn't release changelists, so we don't know what each update does beyond what we can see.
Thanks for the help guys! I just accepted the first update and it took me to ANC5. I guess I'll have to accept all updates until current and then try CF-Auto-Root. I'll report back then.
Actually I just got my tablet like a week ago as well. I m on the same build no as well....haven't updated yet. I also haven't installed Knox either. There is a download arrow on the Knox icon and if I click the icon it starts downloading so I just cancel it. I am thinking of rooting as well. Well what I m trying to say is...keep the thread updated and I will just follow your lead.....hehe.
It always helps to know your country as well as different countries are on slightly different versions. You can always go to sanmobile.com, click on firmware and search for p-900. That will give you the list of all the latest ROMs for different countries / carriers. US based ROMs are listed as "Cellular South".
Successful Root!
Okay guys sorry it's taken so long to respond, I had hernia surgery on Monday so I've been behind on getting this rooted.
My plan was to use CF-Auto-Root and then load TWRP recovery and then load "Debloat Stock Variant" by Gatsrom. I decided to do it in that order because I wasn't sure I could load a custom recovery without being rooted first.
I accepted all updates up to the current = P900UEU1BNK1. Using Win 7 and loaded Samsung drivers. Downloaded ODIN 3.09, Odin 3.07 came with CF-Auto-Root and downloaded TWRP. Booted into download mode and made sure ODIN recognized my P900. And this is when to fun began! Everything seem to be going okay but I did run into a snag. I used ODIN 3.07 because that's what came with Auto- Root and I'd read somewhere of people having trouble with 3.09??? Anyways I got a red "FAIL" message and my screen displayed multicolored lines. I tried running it in ODIN 3.09 and got the same result. (i didn't disconnect anything between the 3.07 or 3.09 attempts, maybe i should have?). I disconnected my P900 and it rebooted giving me a Firmware Error screen telling me to use Kies "Recovery Mode". I tried Kies Recovery but Kies3 wouldn't even recognize the P900. (I started freaking a little at this point!) Anyways, I decided to try and load TWRP because I thought I've got nothing to lose! I loaded TWRP into ODIN and it took, so I thought, because my P900 rebooted into an up and running normal state. (Big Sigh!) I tried booting into recovery but TWRP didn't take, it came up to stock recovery, trying to load TWRP just kicked the P900 out of the Firmware Error state it was in?? I decided to give Auto-Root another go after rebooting Win 7. Used ODIN 3.09 this time and everything went fine and I was rooted! Then I loaded TWRP and it loaded fine! I performed a TWRP backup at this point and things seem to be running smoothly. I still need to load the Debloat Variant, that's what's on my plate for today.
http://forum.xda-developers.com/showthread.php?t=2656551
http://forum.xda-developers.com/showthread.php?t=2706982
http://forum.xda-developers.com/gal...t/rom-original-stock-debloated-stock-t2860069
You are a much braver sole than I. Hope all goes smoothly.
I could be wrong but I would think that if one is going to a different ROM then rooting isn't necessary. Simply use Odin to flash TWRP but ensure that auto reboot is not enabled in Odin when you do it. If you allow the device to begin booting into stock system it's going to overwrite recovery again (with stock recovery) so what you want to do is flash TWRP, and once it's flashed FORCE a reboot directly into recovery again using the hardware keys on the device. At that point you can do an nandroid backup and then flash your ROM.
Sent from my SM-P900 using Tapatalk
treetopsranch said:
You are a much braver sole than I. Hope all goes smoothly.
Click to expand...
Click to collapse
I'm not that brave treetop! I just know my way around a computer and I've rooted a few of these things. Plus I know the guys here on XDA are good at helping out if you hit a snag. Luckily I figured this one out on my own! You've just gotta do your research before jumping in and search read, search read, search read! I provided some links to get you started....get to it!
muzzy99 said:
I could be wrong but I would think that if one is going to a different ROM then rooting isn't necessary. Simply use Odin to flash TWRP but ensure that auto reboot is not enabled in Odin when you do it. If you allow the device to begin booting into stock system it's going to overwrite recovery again (with stock recovery) so what you want to do is flash TWRP, and once it's flashed FORCE a reboot directly into recovery again using the hardware keys on the device. At that point you can do an nandroid backup and then flash your ROM.
Sent from my SM-P900 using Tapatalk
Click to expand...
Click to collapse
Thanks for the info muzzy, I'll remember that for next time! :good:
I did get the Debloat Variant up and running and loaded Xposed framework with sdcard full access. Everything seems to be running smoothly!
Ok So I finally got to it and successfully rooted (in first try, if I may add ). Thanks to xblue's guide/heroic efforts I avoided certain things and everything went smoothly. So Basically I installed samsung drivers using Kies, rebooted pc (Win 8.1). Downloaded cf autoroot and downloaded odin 3.09 as autoroot comes with 3.07. Replaced ONLY 3.07 odin exe with 3.09. Started Odin in Admin mode, put the tablet in download mode. Attched to pc and Odin recognized it. Then Gave it a final thought......lol. Pressed Start, device booted couple times. Then PASS appeared on the Odin window after like 30 secs. Installed root checker...successfully rooted. Installed TWRP via odin and flashed that successfully. Made a full back up and installed a ROM of my choice. I am a happy camper.
Sweet Deal singhsta! I'm glad my efforts were a help!
i would update to the latest version.. i tried using the original one that you have however i got the screen flicker issue so had to update.. the first update isnt very good wifi keeps dropping but the most recent version doesn't tho you may have a bug where every time you unlock the screen the tablet is still asleep even though the icons are visible so you have to lock the screen again and unlock. however if you factory reset this bug goes away.
i find the latest version is the most stable and battery life is better if you disable all the unnecessary apps that you can i usually get rid of most of the samsung back up apps and all the google ones bar the ones it needs to run play store etc and maintaining the ones that sync for back up.
wifi was really slow when i first got it and would drop very annoying but now it seems better but have experienced slow wifi i think it's a hardware issue all note pro's have in built that should have been sorted by the latest build. i hope they finally give it an update in the coming months even to 4.4.4. or something.
Hi, Ive been stuck with this problem for about 3 days now. I have tried EVERYTHING possible and now I'm getting impatient. I've tried every advice on almost every forum or blog. But still cant seem to resolve the issue.
I was running echoe rom 5.1 and tried to flash cm 12 on it through philz recovery. It failed the first time but I was able to access philz. Then I tried to flash stock firmware through Odin and I dont know what happened, it failed and I got an error "Firmware upgrade failed and try recovering through kies...."
I tried kies, my device wasnt able to connect( I tried all the ports and cables I have) and even reinstalled kies just to check. No luck.
Then I killed all the kies processes and tried to flash a stock firmware, this time odin gave an error "PIT partition not found".
I have tried multiple PIT files for i9505 16gb with multiple stock roms on multiple versions of Odin (1.85, 3.07, 3.09, 3.10) some forums asked to tick 're-partition', some said to untick 'auto reboot', Ive tried all of them, still fails.
I can only access download mode on my phone right now, not philz recovery and neither stock android recovery.
my write protection is also enabled, I think this is the core issue, once the protection is disabled, PIT can re partition and flash a stock, and once a stock is flashed, I can flash any recovery and flash any custom ROM through that.
I have been flashing and rooting androids since the last 2 years and never encountered such a problem. Always found some solution online.
I would really appreciate if you guys could help with the problem. Thanks
XDA Visitor said:
Hi, Ive been stuck with this problem for about 3 days now. I have tried EVERYTHING possible and now I'm getting impatient. I've tried every advice on almost every forum or blog. But still cant seem to resolve the issue.
I was running echoe rom 5.1 and tried to flash cm 12 on it through philz recovery. It failed the first time but I was able to access philz. Then I tried to flash stock firmware through Odin and I dont know what happened, it failed and I got an error "Firmware upgrade failed and try recovering through kies...."
I tried kies, my device wasnt able to connect( I tried all the ports and cables I have) and even reinstalled kies just to check. No luck.
Then I killed all the kies processes and tried to flash a stock firmware, this time odin gave an error "PIT partition not found".
I have tried multiple PIT files for i9505 16gb with multiple stock roms on multiple versions of Odin (1.85, 3.07, 3.09, 3.10) some forums asked to tick 're-partition', some said to untick 'auto reboot', Ive tried all of them, still fails.
I can only access download mode on my phone right now, not philz recovery and neither stock android recovery.
my write protection is also enabled, I think this is the core issue, once the protection is disabled, PIT can re partition and flash a stock, and once a stock is flashed, I can flash any recovery and flash any custom ROM through that.
I have been flashing and rooting androids since the last 2 years and never encountered such a problem. Always found some solution online.
I would really appreciate if you guys could help with the problem. Thanks
Click to expand...
Click to collapse
Hello there! Welcome to XDA!
First register an XDA account (so you can ask in the proper forum)
then, please visit the following forum... (see below)
try asking here: (You will have a much better chance of getting help there)
Galaxy S4 Q&A, Help & Troubleshooting
or
Galaxy S4 Main Section
Good Luck!
thanks mate!
Registered and posted here
http://forum.xda-developers.com/galaxy-s4/help/s4-lte-i9505-soft-bricked-t3199387
Thread closed
Some say "Bricking" is when the phone doesn't turn on at all, or does and displays and does nothing; some say there are different states of bricking. In any case... I'm only an intermediate, and I did not have any booting problems before this. So, with the least-common denominator in mind, please read on.
I have a Samsung Galaxy S3, SGH-i747 ATT. It was out of warranty anyway and I've flashed custom ROMs on it many times before without issue. I dropped it about a week ago and the LCD broke. Upon having it fixed, I noticed it no longer booted properly. I am able to get into ODIN's download mode, and I am able to flash stock recovery, but neither have proven helpful.
I was originally running Slimkat 4.4, but decided to flash back to the stock Android ROM since it would no longer boot properly anyway. This is where it gets strange.
First I attempted to flash CWM and TWRP as my recoveries. ODIN said both were successful in flashing on their respective attempts, but each one was simply a black screen after the Samsung logo disappeared. The blue text in the top-left letting me know it was booting into recovery was present with the logo, but after it disappeared, nothing.
So I tried to install stock recovery, and to my surprise, it worked, though it's really not useful for anything. Chainfire's CF-autoroot was also flashable and functional, but when I tried using adb to push files to the device, I would get several errors:
From the ADB command line, when trying to push something, I'd get "Error: closed".
From the recovery's log, sometimes when I'd successfully send a ROM to be installed, I'd get various notifications, such as: "Failed to verify whole-file signature" and "Incorrect footer", "Installation aborted".
When I attempt to flash any ROMs via ODIN, I get a few different errors, including (Not verbatim, these are from memory):
REV CHECK FAIL
DEV UNSUPPORTED
FUSED 2 > BINARY 0 [This one is especially confusing to me]
SECURE CHECK FAIL
and one from the ODIN side that said something along the lines of "HLOS-BIN" or something when it failed to flash.
So I can turn the device on, get to download mode, and even flash the stock ROM and CF-autoroot... but after 20 hours of reading other people's similar problems and varying degrees of success in their solving them, I'm stumped. I hope someone here might be able to share their superior knowledge vis-a-vis Android!
-Krust
Update
I've tried many things.
Right now I'm trying to re-flash Slimkat 4.4 (Which I was already using), and I know anything JB 4.3 or above will restrict the bootloader from downgrading, so maybe that was the problem. But if this doesn't work... I'm not sure what to do. Will post error updates if any.
-Krust
Same Status
I still get REV CHECK FAIL Fused 2 > Binary 0 error.
I believe this is from attempting to flash to a version lower than what I had (4.4).
I am unable to find stock firmware for the ATT SGH-i747 for 4.4 or above.
Please help! This is my only phone, and I know it can be restored because I can still get into download mode, but something's blocking ODIN from performing the flash, even on packages that seem to be the correct version.
Update
From what I have been able to find, I will need to update to an Android variant 4.4.2 or above due to the restricted bootloader.
My only problem... I haven't been able to FIND any stock ROMs for 4.4.2.
Everything I try returns a variety of errors, the most common being FUSED 2 > BINARY 0 (Which I now understand means I am attempting to downgrade) because I have not been able to find anything like Slimkat 4.4.2 that is in .tar format to flash.
I am very stuck and confused, and this is my only phone. Lesson learned: Keep up with the nuances of updates. But for now, I really need to get this fixed. Does anyone have experience with this particular problem?
Update
I was able to flash a modded TWRP recovery and was able to boot into it.
However, when I try to install ROMs via zip, I get the error E: Cannot execute binary update file.
One ROM, a Slimkat for i747M (Which isn't even my phone), appeared to flash successfully, but wouldn't boot.
GApps for Slimkat 4.4.4 was also able to flash successfully on its own, but the corresponding Slimkat could not.
I am quite stuck. Please help.
Hi,
Try posting your question here:
AT&T Galaxy S III Q&A, Help & Troubleshooting
The experts there may be able to help.
Good luck!
I have hear a S7 wich hangs on white samsung boot logo.
The device is stock, no root and no custom rom.
The problems started on a failed update, it started to hang during use.
I made a backup and then tried to reset it, sadly i came no further then this boot logo after it crashed again.
I decided to enter recovery mode, when entering recovery each time i get a blue install screen of an update and each times it fails with an error.
Then i did a wipe cache and rebooted, same result, it stops at boot logo
Then i did a wipe/format factory reset (from recovery) and reboot, here also it hangs on samsung logo
Also it reports the following:
fail to open recovery cause no such file or directory
I even let the phone boot for 8 hours on the logo, it gets really hot but it does not go pass the samsung boot logo
When booting and the phone is connected by USB to my laptop i get messages that android rom is prepared and 1 later it is installed, but that is it, no booting etc.
I then entered download mode and used ODIN, downloaded the latest stock rom and try to flash it.
But here also i get each try a FAILED on the boot, even when i do no enter BL i get a FAILED, so only AP it fails also.
I tried now about 5 different stock rom versions and they all fail.
Have really no idea how to fix this, as mentioned the phone is fully stock, so stock bootloader, stock rom etc.
Anyone any idea how to get this phone up and running again?
B3rt said:
I have hear a S7 wich hangs on white samsung boot logo.
The device is stock, no root and no custom rom.
The problems started on a failed update, it started to hang during use.
I made a backup and then tried to reset it, sadly i came no further then this boot logo after it crashed again.
I decided to enter recovery mode, when entering recovery each time i get a blue install screen of an update and each times it fails with an error.
Then i did a wipe cache and rebooted, same result, it stops at boot logo
Then i did a wipe/format factory reset (from recovery) and reboot, here also it hangs on samsung logo
Also it reports the following:
fail to open recovery cause no such file or directory
I even let the phone boot for 8 hours on the logo, it gets really hot but it does not go pass the samsung boot logo
When booting and the phone is connected by USB to my laptop i get messages that android rom is prepared and 1 later it is installed, but that is it, no booting etc.
I then entered download mode and used ODIN, downloaded the latest stock rom and try to flash it.
But here also i get each try a FAILED on the boot, even when i do no enter BL i get a FAILED, so only AP it fails also.
I tried now about 5 different stock rom versions and they all fail.
Have really no idea how to fix this, as mentioned the phone is fully stock, so stock bootloader, stock rom etc.
Anyone any idea how to get this phone up and running again?
Click to expand...
Click to collapse
What country are you in?
What network were you using?
What firmware was on your phone nougat or Oreo?
What firmware are you trying to flash?
What version of Odin are you using?
cooltt said:
What country are you in?
What network were you using?
What firmware was on your phone nougat or Oreo?
What firmware are you trying to flash?
What version of Odin are you using?
Click to expand...
Click to collapse
Living in The Netherlands
The phone is free, not network limited but was last used on T-Mobile
I am not 100% sure, i believe Android 8
i tried: DNL-G930FXXU3ESA3-20190131134911 and EUR-G930FXXS4ESAE-20190218105256 and DNL-G930FXXU2DRC1-20180402094302 and BTU-G930FXXU1DPLT-20170117160813 and G930FXXU1DQAN_G930FFTM1DQAD_FTM
Tried Odin3_v3.12.3 and Odin3-v3.13.1
B3rt said:
Living in The Netherlands
The phone is free, not network limited but was last used on T-Mobile
I am not 100% sure, i believe Android 8
i tried: DNL-G930FXXU3ESA3-20190131134911 and EUR-G930FXXS4ESAE-20190218105256 and DNL-G930FXXU2DRC1-20180402094302 and BTU-G930FXXU1DPLT-20170117160813 and G930FXXU1DQAN_G930FFTM1DQAD_FTM
Tried Odin3_v3.12.3 and Odin3-v3.13.1
Click to expand...
Click to collapse
Your trying to flash old versions of the firmware, once the boot loader is updated you can't go back.
This is the latest version of T Mobile for the Netherlands (TNL), it's always best to try the firmware you were on first [url]https://www.sammobile.com/firmwares/galaxy-s7/SM-G930F/TNL/download/G930FXXU3ESA3/255865/[/URL]
If that doesn't work this is the latest version of Unbranded BTU [url]https://www.sammobile.com/firmwares/galaxy-s7/SM-G930F/BTU/download/G930FXXS4ESAE/257466/[/URL]
Also use Odin 13. Put all files in correct slots and use CSC not HOME_CSC
As far as i could see these are all android 8 and 1 android 7 firmwares, so they are not that old.
Believe the latest one is from January this year, i know the last time the phone was updated was last October, after that all updates failed to install OTA
The link you gave me is exactly the same version i used only without the branding, so i already used the latest one.
I tried to be sure the download from the link you given but with those download speeds (15kb) it is almost impossible to download these firmware's, i am not gonna take a subscription to for 1 time fast downloading and also i do not want to risk that i paid for a fast download it fails again....
So if someone has a download link which i can use and try an other firmware please feel free to share it.
BTW i used the last Odin3-v3.13.1 version, i cannot find a newer one.
B3rt said:
As far as i could see these are all android 8 and 1 android 7 firmwares, so they are not that old.
Believe the latest one is from January this year, i know the last time the phone was updated was last October, after that all updates failed to install OTA
The link you gave me is exactly the same version i used only without the branding, so i already used the latest one.
I tried to be sure the download from the link you given but with those download speeds (15kb) it is almost impossible to download these firmware's, i am not gonna take a subscription to for 1 time fast downloading and also i do not want to risk that i paid for a fast download it fails again....
So if someone has a download link which i can use and try an other firmware please feel free to share it.
BTW i used the last Odin3-v3.13.1 version, i cannot find a newer one.
Click to expand...
Click to collapse
Ok well you can listen to me or not.
None of the firmwares you are using are for your device, PHN is Netherlands and the BTU you are using BTU-G930FXXU1DPLT is on a U1 boot loader, BTU is now on S4 which is 3 versions above U1.
The reason you only download from Sammobile or updato.com is because the firmware is correct, reliable and not full of virus/spyware. You can also download direct from Samsung severs with SamFirm Tool.