Hello,
My S10+ got soft bricked after OTA update, i tried all fixes i could find(recovery factory reset/cache deletion etc), i also tried using odin to flash 2 different versions of firmware for my model but this also did not work.
The phone is not OEM unlocked.
How do i fix it?
Related
I have the international version of Note 3, bought in Argentina (with Exynos). Yesterday, I installed the lastest Lollipop stock ROM from Russia.
I didn't do a full wipe. Everything works well (except Swype, which I disabled for now), but if I turn on Wifi, it doesn't detect any network, and in a few seconds, the SAMSUNG (booting) screen appears, and keeps loop booting like that until I turn off Wifi.
What may be the problem? Should I do a full wipe? Should I try to access the log and see what fails?
Thanks in advance.
Factory reset flash a new firmware .
In that order?
Is there any way to know what is failing without factory reseting?
[PROBLEM] Rooted > Flashed to U Firmware > Soft Brick > Flashed back to Verizon FW
Hi, relatively new to this, so sorry in advance if I made some obvious mistakes, but my phone is now soft bricked and I can't find a solution.
1) I was on Nougat
2) Rooted with Odin to remove Verizon bloat
3) Didn't really change much, still had MMS issues etc
4) Did a the deep verizon debloat. Started getting an endless message 'IMS Service has stopped'
5) Decided to flash U Firmware to get a non-Verizon, unrooted starting point. Used HOME_CSC to keep data
6) Soft bricked phone (didn't finish install and was stuck on a boot menu with the message 'dm-verity verification failed' )
7) Flashed back to a previous version of Verizon firmware, again, HOME_CSC - (G935VVRS4APH1_CL8875708_QB10880117_REV02_user_low_ship_MULTI_CERT.zip). (Did this twice now, once with PrinceCosmy Odin)
8) Install went well, Verizon logo on boot.
9) Soft brick #2 - I'm being asked for a password to decrypt storage...I set no password for this. So I'm stuck.
Thanks in advance, any support is much appreciated!
The PH1 firmware is very old. You might have better luck flashing to QF2. Honestly, your best bet is to boot into recovery to do a factory reset, then start over completely. That will clear the decryption issue. Then look at the QF2 ROM in this forum.
CVertigo1 said:
The PH1 firmware is very old. You might have better luck flashing to QF2. Honestly, your best bet is to boot into recovery to do a factory reset, then start over completely. That will clear the decryption issue. Then look at the QF2 ROM in this forum.
Click to expand...
Click to collapse
Thanks! I was hoping to not have to reset, but have recently backed it won't be a big deal.
I have two other questions though
a) how do I know which firmware is QF2? (the device was originally on MM but through smart switch I upgraded to Nougat)
b) what's the process for the factory reset? I'm trying via the recovery menu and it isn't working (the MM 6.0.1/ G935UUES4AQC1 install)
Thanks
(UPDATE - OK so I went back to the U firmware, and from that boot menu selected 'Wipe Partition/Cache'. Also did a factory reset which looked like it failed. Still couldn't boot phone though. However I went back to the verizon firmware and there was no passcode prompt now. Phone is factory reset to 6.0.1.
Should I go to QF2 now?
How can I get to a non-verizon firmware?)
OK, I've solved everything I mentioned above by doing as suggested,
I think I had a partition of something somewhere that was no good.
1 - Factory Reset from boot menu (after wiping partition/cache)
2 - Flashed PH1
3 - Verizon bloatware reinstalled and was loading phone properly
4 - Did a factory reset from here via settings
5 - After factory reset, Flashed QC1 w/out HOME_CSC
6 - Now booting properly with a clean(ish), non-Verizon firmware.
I'm still interested in removing as much bloat as possible from Samsung, and am constantly being harassed notified that my Nougat update is downloaded and ready to install!
Hope that helps someone!
So I have a SM-G950W (BMC (Bell) originally but using unlocked on RWS (Rogers)) . Nothing has ever been flashed before except for OTA updates.
I upgraded to the Oreo OTA update and my phone got stuck in a bootloop. Ive tried wiping Cache and Factory resetting and no dice.
I decided to flash the official firmware with odin. I downoaded BMC/RWC/XAC and have tried flashing each of those through the newest Odin (1.13.1). This always ends successfully.
On bootup I get to the Samsung logo and the LED blinks red and the phone reboots. This happens indefinitely.
Ive tried wiping factory and cache again after this and it did not help. If I flash the HOME_CSC instead of CSC It gives me an encryption error and wants me to factory reset, after that I get the same red led bootloop result.
Any ideas on what I can do/ Am I missing any steps?
EDIT: Unsure if this is related but in the recovery menu it says this at the bottom:
fail to open recovery_cause(No such file or directory)
Reboot Recovery Cause is [UNKNOWN]
No support SINGLE-SKU
File based OTA
Supported API: 3
remove failed dir '/system/carrier/ATT/priv-app/AttIqi_ATT' (No such file or directory)
[libfs_merger] Error fetching verity device number: no such device or address
[libfs_merger] Couldnt get verity device number!
[libfs_merger] Error removing device mapping: no such device or address
Successfully verified dmverity hash tree
Same issue with SM-G950U1
Hi Mike, I have the same issue that you are reporting and in the recovery menu, it says the same as yours at the bottom. I didn't find any solution for having the phone stop rebooting. Please, if you have found any solution share it. I'll do the same if I can get the phone out of the boot looping. What I have done so far is flash the phone with the last official firmware downloaded with SamFirm.
I'm not sure but the problem might be related to the firmware. I'm now downloading an older firmware (with android 7.0) to check if the phone starts ok with that firmware. I'll let you know if I have good news.
Regards!
EDITED:
I found a solution!!
Hey, just want to share how I stopped the bootlooping.
You will need to flash your phone following this post https://forum.xda-developers.com/galaxy-s8+/how-to/snap-guide-flashing-standard-fw-carrier-t3627255 and download Firmware from Updato. Do not download the last version of the Firmware, because it will continue doing the bootloop. I've downloaded the following firmware:
Galaxy S8 / SM-G950U1 / 7.0 Nougat(Android ) / December 26, 17
And the phone has started!
Remember to use the last version of Odin from this post https://forum.xda-developers.com/showpost.php?p=75703449&postcount=276
If not you will not be able to flash your phone.
Hope you can fix the phone as I have done!
Let me know when you fix it.
Best!
Hey Mike,
You are not alone. Samsung apparently has messed up another OTA again. I have the same issue after Oreo update. Showed my phone to a certified Samsung repair shop and they said they had several people showing up that day with the same issue and they were not able to fix it. The best bet to contact Samsung Customer Support and they will assist you in sending your phone to a repair center.
I hope there was a faster way to fix the issue.
Hey Mike, I have updated my first answer with a workaround to fix the bootlooping. Let me know if it works in your case that I think was the same as mine.
Regards!
Hey Guys. Having the same exact issue for G955U1. I would to know if what gorito17 suggest fix the issue besides him.
Can anyone give me a little guidance:
UK Vodafone supplied S7 Edge, not rooted. Received Oreo update this morning, phone is now stuck in a bootloop - it will get as far as the "Android is starting... optimising applications", that goes away and then it just reboots.
I've been in to the recovery menu and tried wiping the cache partition - to which it reports "could not find /misc partition". Attempting to mount system partition reports the same thing.
Do I have any chance of resurrecting this? the firmware isn't yet on sammobile but I was wondering if updating via ADB or sdcard would help.
Grateful for any help!
install again via odin or directly on the Samsung page. with me it works super well
Can't get the ROM for Oreo as yet. Downloading 7.0 from sammobile and will try flashing that via adb and see if I can resurrect it. Anyone want to guess the chances of this working ?
Crafty77 said:
Can't get the ROM for Oreo as yet. Downloading 7.0 from sammobile and will try flashing that via adb and see if I can resurrect it. Anyone want to guess the chances of this working ?
Click to expand...
Click to collapse
That should work... download de 7.0 and install via Odin with mobile in download mode.
I always wake up my brick mobiles like this.
Have 'updated' my Ş7 with Oreo and now stuck with the boot logo.
Will they f***ing idiots from Samsung ever make a normal software without causing troubles?
My UK Vodafone supplied S7 also is stuck in a bootloop after the Oreo update.
My phone s7 is stuck in bootloop too. Don't know what to do. Nearest Samsung support is 36 miles away.
Its so hot to touch. Pressed all buttons to reset as advised but no luck.
wipe all in recovery or flash firmware through odin ,,
hope this helps.
here is the Oreo factory image for Vodafone https://androidfilehost.com/?fid=890278863836283079
only works with the latest Odin https://odindownloader.com/wp-content/uploads/Odin3_v3.13.1.zip
Galaxy S7 Vodafone here. Bootloop as well...
This update needs to be pulled. There will be thousands of people with the S7 on Vodafone most of whom won't be interested in using Odin to fix a problem caused by Samsung/Vodafone.
Just updated mine and wished I hadn't S7 edge, UK, Vodafone. Won;t leave the bootloop and cant get it to wipe cache or data. Can get it into download mode and shall be trying to reinstall
Updated my S7 Edge Vodafone - bootloop. Tried reinstalling with Odin and same result - still bootloop. This is unbelievable. Is this vodafone forcing this update or Samsung?
Any other ideas as I really don't want to wipe my phone completely? Have tried Odin reinstall twice just in case.
AndyBurmey said:
Updated my S7 Edge Vodafone - bootloop. Tried reinstalling with Odin and same result - still bootloop. This is unbelievable. Is this vodafone forcing this update or Samsung?
Any other ideas as I really don't want to wipe my phone completely? Have tried Odin reinstall twice just in case.
Click to expand...
Click to collapse
I had to wipe my phone.
Is this the only fix so far? Really don't want to do that if I don't have to as my SD encryption key is stored on the phone and I didn't decrypt it before updating...
Lammy696 said:
Is this the only fix so far? Really don't want to do that if I don't have to as my SD encryption key is stored on the phone and I didn't decrypt it before updating...
Click to expand...
Click to collapse
Hey Lammy696,
My mother is on Vodafone UK with the S7 Edge and is experiencing the bootloop. I would advise not to update for the time being.
I would strongly advise decrypting your SD card prior to updating.
I have tried wiping cache etc as per normal update process but that failed. Only options I have is to flash a custom recovery, mount the storage and backup (if I can do this) or to wipe it completely.
If you want to keep your warranty and support, do not use the custom recovery option.
Good luck.
Unfortunately I've already updated and have probably lost all that data now
Is it safe to update now?
Hi,
I have a carrier branded s10+, in Europe, with no simlock. I have tried to flash an open market firmware with Odin but it fails. After clicking start fails immediately without doing anything to the phone.
I have previusly removed the Samsung account to turn of FRP as I always did when flashing.
What could be the problem? The fingerprint having the phone encrypted? I will eventually factory reset and try to flash it with no initial setup being done, but I kinda want to avoid a factory reset if it won't make a difference.
This is not the first time I use Odin, but this problem is new to me.
Add a screenshot of Odin when the error occurs.
mmuntean2 said:
Hi,
I have a carrier branded s10+, in Europe, with no simlock. I have tried to flash an open market firmware with Odin but it fails. After clicking start fails immediately without doing anything to the phone.
I have previusly removed the Samsung account to turn of FRP as I always did when flashing.
What could be the problem? The fingerprint having the phone encrypted? I will eventually factory reset and try to flash it with no initial setup being done, but I kinda want to avoid a factory reset if it won't make a difference.
This is not the first time I use Odin, but this problem is new to me.
Click to expand...
Click to collapse
you will probably need to use a modify version of odin https://forum.xda-developers.com/s10-plus/how-to/sm-g975u-firmware-downloads-tmo-spr-att-t3908657 2nd post
Found the solution. after removing the Samsung account, disabling encryption on the phone and disabling Find my phone from device managers, I enabled OEM Unlocking. Flashing worked with no issues after this.