Related
I recently rooted my galaxy s6 edge g925t and was successful, but i couldn't stop there, i wanted to upgrade to android 6.0. i spent hours searching for a custom ROM/firmware and found one that i thought would work. I installed that custom OS through TWRP installer. After i finished the installation i tried to restart the phone but it just stayed at the "Samsung Galaxy S6 EDGE" boot logo and didn't play the boot animation. I searched online for ways of unbricking the phone and i eventually got to the recovery mode and tried to wipe the internal storage. then i restarted the phone and was back to the same Samsung logo. I again tried to get back to the recovery mode, but this time i did an advanced wipe and i ended up deleting the OS. if tried installing the stock ROM/firmware via Odin but can't get it to work. Is there anything i can still do? Can anyone please help me?
What happens when you try and flash the Odin image? The Rom you flashed, did that flash a new bootloader or firmware? If so it might have messed up the partitions on the phone.
M9x3mos said:
What happens when you try and flash the Odin image? The Rom you flashed, did that flash a new bootloader or firmware? If so it might have messed up the partitions on the phone.
Click to expand...
Click to collapse
The phone doesn't accept that either.
What custom ROM did you install? And what stock ROM did you try to ODIN flash?
Also, what is happening when you do that. I gathered out didn't work, but what error comes up?
zabrador said:
What custom ROM did you install? And what stock ROM did you try to ODIN flash?
Click to expand...
Click to collapse
TyrannusRomV23.1.zip is the custom rom, and SM-G925T_1_20150327095252_d1ygbqk7km (1) is the name of the stock i tried.
also the error that ODIN shows is that it FAILed and the phone shows in red letters in the top corner "check fail. DEVICE: 3, BINARY: 1
i dont know the entire message from the phone b/c my screen is blacked out in the top corner, but thats what i can see.
micahtjosaas said:
TyrannusRomV23.1.zip is the custom rom, and SM-G925T_1_20150327095252_d1ygbqk7km (1) is the name of the stock i tried.
also the error that ODIN shows is that it FAILed and the phone shows in red letters in the top corner "check fail. DEVICE: 3, BINARY: 1
i dont know the entire message from the phone b/c my screen is blacked out in the top corner, but thats what i can see.
Click to expand...
Click to collapse
Yeah, I don't think TyrannusRom is runnable on a G925T :/
Flashing stock with ODIN should do the trick. It's hard to tell where that stock file is from, so I would try to download the latest directly from SamMobile here (this is specifically for the G925T). If it's still not working, copy/paste the error ODIN is giving you here if you can.
Also, this thread seems to suggest you might be able to just re-flash the bootloader.
THANK YOU so much!!! that worked, iv looke on sammobile before but couldn't get anything to work, thanks so much
micahtjosaas said:
THANK YOU so much!!! that worked, iv looke on sammobile before but couldn't get anything to work, thanks so much
Click to expand...
Click to collapse
No problem! Glad you're back up and running
HONOR 7X ( indian variant )
Phone is in a boot loop.
It shows Honor Logo and then the Error screen with the following message :
ERROR MODE
Attention!
Please update system again
Error!
Func NO : 15 (bl31 image)
Error NO : 1 (security verify failed!)
I tried to manually update to Oreo and was successful.
But VoLTE was not working properly.
So, i decided to roll back to EMUI 5.0 (Nougat) and got stuck in Boot Loop.
Initially both twrp and fastboot was working.
I tried to flash Stock recovery for oreo using fastboot.
But it didn't work.
At that point i lost both twrp and stock recovery.
It went into ERROR mode with different error codes saying "No Recovery Image" and "Load Failed"
I tried to Erase recovery and re-flash it.
I tried erasing System and flashing the system.img for oreo which was extracted from UPDATE.APP
I tried Multi tools.
I tried dload method.
Nothing worked. Same error mode.
Then i finally tried flashing the stock recovery again and relocked the oem.
Now, I can't even get into Fastboot.
It just displays the ERROR Screen.
I tried draining the battery to 0% and restarting it.
I tried all button combinations.
No luck.
Nothing works.
Now, i have a bricked phone with no recovery and no fastboot.
And i don't know whether they will accept this in the service center.
Is there someone who could really help me get my phone back?
rahulrk.2303 said:
HONOR 7X ( indian variant )
Phone is in a boot loop.
It shows Honor Logo and then the Error screen with the following message :
ERROR MODE
Attention!
Please update system again
Error!
Func NO : 15 (bl31 image)
Error NO : 1 (security verify failed!)
I tried to manually update to Oreo and was successful.
But VoLTE was not working properly.
So, i decided to roll back to EMUI 5.0 (Nougat) and got stuck in Boot Loop.
Initially both twrp and fastboot was working.
I tried to flash Stock recovery for oreo using fastboot.
But it didn't work.
At that point i lost both twrp and stock recovery.
It went into ERROR mode with different error codes saying "No Recovery Image" and "Load Failed"
I tried to Erase recovery and re-flash it.
I tried erasing System and flashing the system.img for oreo which was extracted from UPDATE.APP
I tried Multi tools.
I tried dload method.
Nothing worked. Same error mode.
Then i finally tried flashing the stock recovery again and relocked the oem.
Now, I can't even get into Fastboot.
It just displays the ERROR Screen.
I tried draining the battery to 0% and restarting it.
I tried all button combinations.
No luck.
Nothing works.
Now, i have a bricked phone with no recovery and no fastboot.
And i don't know whether they will accept this in the service center.
Is there someone who could really help me get my phone back?
Click to expand...
Click to collapse
I was gonna do a roll back too. Maybe I need to re exam your problem first.
Like why did you flash the Oreo system image after you rolled back?
Sorry, but I don't know of any steps forward for you, but can you tell the steps you did in the "Roll-back" and try to be detailed.
Please take a full back up before you roll back.
mrmazak said:
I was gonna do a roll back too. Maybe I need to re exam your problem first.
Like why did you flash the Oreo system image after you rolled back?
Sorry, but I don't know of any steps forward for you, but can you tell the steps you did in the "Roll-back" and try to be detailed.
Click to expand...
Click to collapse
I didn't succeed rolling back. I flashed the system.img and stock recovery of emui 5.0. But it got me the error.
Maybe the system partitions of emui 8.0 and 5.0 are different.
For example, The recovery partition has changed to recovery_ramdisk in emui 8.0.
Then, I tried flashing system.img and recovery of emui 8.0.
I got stuck in a bootloop.
But fastboot was accessible.
I tried flashing twrp for 8.0 by openkirin. It didn't work too.
Then i thought maybe i should flash the stock recovery and relock the oem and i did it.
Now i ended up with a locked bootloader, no recovery. Just the error message and the bootloop.
Somebody please help.
rahulrk.2303 said:
I didn't succeed rolling back. I flashed the system.img and stock recovery of emui 5.0. But it got me the error.
Maybe the system partitions of emui 8.0 and 5.0 are different.
For example, The recovery partition has changed to recovery_ramdisk in emui 8.0.
Then, I tried flashing system.img and recovery of emui 8.0.
I got stuck in a bootloop.
But fastboot was accessible.
I tried flashing twrp for 8.0 by openkirin. It didn't work too.
Then i thought maybe i should flash the stock recovery and relock the oem and i did it.
Now i ended up with a locked bootloader, no recovery. Just the error message and the bootloop.
Somebody please help.
Click to expand...
Click to collapse
OK, yes there is different partition table for oreo, so more that those partitions was needed.
one thing you might be able to try, is a manuael update.
put the oreo update.zip in the root of sd card. put card in phone, and hold both volume buttons together with power button.
mrmazak said:
OK, yes there is different partition table for oreo, so more that those partitions was needed.
one thing you might be able to try, is a manuael update.
put the oreo update.zip in the root of sd card. put card in phone, and hold both volume buttons together with power button.
Click to expand...
Click to collapse
I've already tried the dload method. But holding both volume buttons + power button didn't work. It loads into the error mode screen again. Maybe I'll copy the update.zip into the root of SD card and try again. But i think the phone won't boot into software update mode.
Is it hard bricked or soft bricked?
Should i try taking it to the service center?
People
Dont try to roll back from Oreo to Nougat on update ZIPs...
Partitions changed on Oreo System. The available update to Oreo it must read the previous partitions and configure the new partitions.
If you try to do it AFTER installing the update, the installation will get error cause can't read the Nougat partitions.
rahulrk.2303
With the phone powered off, press Vol Down key and insert the USB cable.
What happens?
RSGI said:
People
Dont try to roll back from Oreo to Nougat on update ZIPs...
Partitions changed on Oreo System. The available update to Oreo it must read the previous partitions and configure the new partitions.
If you try to do it AFTER installing the update, the installation will get error cause can't read the Nougat partitions.
rahulrk.2303
With the phone powered off, press Vol Down key and insert the USB cable.
What happens?
Click to expand...
Click to collapse
Nothing. It vibrates. Honor logo. Again the same error screen. I know it's supposed to go into fastboot mode. But unfortunately, it doesn't.
rahulrk.2303 said:
Nothing. It vibrates. Honor logo. Again the same error screen. I know it's supposed to go into fastboot mode. But unfortunately, it doesn't.
Click to expand...
Click to collapse
There is Oreo downgrade proceedure on Chinese huiwei club website. But your device needs full firmware package available.
There is full downgrade packages for al00 al10 and tl10.
rahulrk.2303 said:
Nothing. It vibrates. Honor logo. Again the same error screen. I know it's supposed to go into fastboot mode. But unfortunately, it doesn't.
Click to expand...
Click to collapse
Man... The FASTBOOT partiton is also screwed up...
The only change you got, other take the phone to the Huawei Service Center, is the dload method.
But for that you'lll need full packages.
mrmazak
Can you share a link to those packages?
RSGI said:
Man... The FASTBOOT partiton is also screwed up...
The only change you got, other take the phone to the Huawei Service Center, is the dload method.
But for that you'lll need full packages.
mrmazak
Can you share a link to those packages?
Click to expand...
Click to collapse
I have downloaded updateL22.zip for oreo and tried the dload method. It didn't work. It still boots to the same error mode. Is this condition hard brick or soft brick? I don't think there is a problem with the motherboard because the screen is turning on and it's in a bootloop. But i can't access recovery or fastboot. I'm confused. Maybe it's a software issue. But there is no way i could access the phone in order to flash something. I'm planning to take it to the service center and act innocent. Any suggestions? Will they find out that i unlocked or rooted and messed with the partitions. Is there any chance they could fix it?
RSGI said:
Man... The FASTBOOT partiton is also screwed up...
The only change you got, other take the phone to the Huawei Service Center, is the dload method.
But for that you'lll need full packages.
mrmazak
Can you share a link to those packages?
Click to expand...
Click to collapse
the three marked as full
b192
dated 3-28
http://pro-teammt.ru/firmware-database/?firmware_model=bnd-&firmware_page=0
mrmazak said:
the three marked as full
b192
dated 3-28
http://pro-teammt.ru/firmware-database/?firmware_model=bnd-&firmware_page=0
Click to expand...
Click to collapse
That's the one i tried.
The BNDAL10 one.
rahulrk.2303 said:
I have downloaded updateL22.zip for oreo and tried the dload method. It didn't work. It still boots to the same error mode. Is this condition hard brick or soft brick? I don't think there is a problem with the motherboard because the screen is turning on and it's in a bootloop. But i can't access recovery or fastboot. I'm confused. Maybe it's a software issue. But there is no way i could access the phone in order to flash something. I'm planning to take it to the service center and act innocent. Any suggestions? Will they find out that i unlocked or rooted and messed with the partitions. Is there any chance they could fix it?
Click to expand...
Click to collapse
If you take it to the service center, it wont matter how you play it...
The phone just dont get that way unless, somehow, the warranty was voided...
The less you say, the less you will pay for they to fix it... I believe that over those Service Centers they can fix almost everythng.
That package is not a full package! you need a Full Package
mrmazak said:
the three marked as full
b192
dated 3-28
http://pro-teammt.ru/firmware-database/?firmware_model=bnd-&firmware_page=0
Click to expand...
Click to collapse
Here´s a noob question:
What update.zip should i download?
1 - The one in the filelist section
2 - The one at the update section
Please, dont tell me that they're the same....
RSGI said:
If you take it to the service center, it wont matter how you play it...
The phone just dont get that way unless, somehow, the warranty was voided...
The less you say, the less you will pay for they to fix it... I believe that over those Service Centers they can fix almost everythng.
That package is not a full package! you need a Full Package
Click to expand...
Click to collapse
Is there nothing more i could do?
And what do you think the problem is?
Software issue or Hardware?
rahulrk.2303 said:
Is there nothing more i could do?
And what do you think the problem is?
Software issue or Hardware?
Click to expand...
Click to collapse
How the phone end up this way?
What were you trying to do?
How the heck you screw Fastboot? just kidding
If were trying to update, flash something to the device, its most likely a software issue.
If the phone fell down, bumped into something... well this increases the change that some hardware may by screwed also...
RSGI said:
If you take it to the service center, it wont matter how you play it...
The phone just dont get that way unless, somehow, the warranty was voided...
The less you say, the less you will pay for they to fix it... I believe that over those Service Centers they can fix almost everythng.
That package is not a full package! you need a Full Package
Here´s a noob question:
What update.zip should i download?
1 - The one in the filelist section
2 - The one at the update section
Please, dont tell me that they're the same....
Click to expand...
Click to collapse
but i think the update.zip listed in file list is same , don't really know.
all three are needed for full package.
RSGI said:
How the phone end up this way?
What were you trying to do?
How the heck you screw Fastboot? just kidding
If were trying to update, flash something to the device, its most likely a software issue.
If the phone fell down, bumped into something... well this increases the change that some hardware may by screwed also...
Click to expand...
Click to collapse
I flashed Oreo update successfully.
I wanted to Rollback.
I flashed system and recovery of nougat and locked the oem.
The problem is that we can't rollback from oreo to nougat because of different partitions.
I realized that only after locking the oem.
And now there's nothing i could do.
Btw, this is only due to flashing. So, i hope it's not a Motherboard problem.
The cost of flashing Software from service center is very less, even if my warranty is void.
rahulrk.2303 said:
I flashed Oreo update successfully.
I wanted to Rollback.
I flashed system and recovery of nougat and locked the oem.
**The problem is that we can't rollback from oreo to nougat because of different partitions.
Click to expand...
Click to collapse
???Well to be true you did not flash a roll-back(did you?) you only replaced system and recovery. The true roll-back "update.zip" should do more than that.???
I realized that only after locking the oem.
And now there's nothing i could do.
Btw, this is only due to flashing. So, i hope it's not a Motherboard problem.
The cost of flashing Software from service center is very less, even if my warranty is void.
Click to expand...
Click to collapse
mrmazak said:
???Well to be true you did not flash a roll-back(did you) you only replaced system and recovery. The true roll-back "update.zip" should do more than that.???
Click to expand...
Click to collapse
Tbh, i did everything one by one because nothing seems working.
I've tried every single method, trust me.
Can't flash unbranded Oreo ROM and "e: failed to find /misc partition" message after
Hi guys, here's the deal.
I've bought this phone from an Argentina company called Claro, it has all typical bloatware from the carrier, apps, logo boot, ringtones, etc. So I've decided to flash my brand new Samsung Galaxy A5 2017 (SM-A520M) with the unbranded OREO ROM version from SamMobile, with the 4 files through Odin. Well, the thing's that I didn't know that because of the new security patchs (and for what I know), the OEM unlocked option was disabled it was impossible to flash. I mean Odin recognized it but the steps didn't even appear like always did. I've investigated a bit and I saw that OEM was disabled and because of that, I'll have to wait a week or so to unlock the feature. I've read that setting the date a week back I was able to activate it. And so I did, and it worked, so I thought... I've plugged the phone with Odin in Download Mode and I was determined to finally flash the new ROM. Long story short, it got stuck on SET PARTITION, which I think is the first message that pop-ups on Odin when flashing. So, I waited and waited but nothing happened, I saw that the whole process got stuck. The only thing I remember to read was NAND START WRITTING and nothing else.
After several minutes with no response I've unplugged my phone, and I press the power button. I saw the Samsung logo on loop, I almost died. I've read some forums about the issue but nothing certain, I guess this problem is kinda new. My concern was that when I went to Recovery Mode I saw the message below the options "e:/ failed to find misc/partition" that's when I really thought that it was a real problem and probably my phone was bricked forever. Luckily I made the factory reset and then it booted again. The phone is working great but, I'm very concerned about that message that appears on Recovery Mode, there's something wrong with that partition and for what I read and know about it there could be something missing from my phone that could be essential.
Thoughts? What can I do? I also downloaded Samsung Smart Switch to try to recover the firmware and install it to begin again but the option won't appear. My phone is detected, but I can't use the Emergency Recover with the original Firmware on Smart Switch. One more detail, the phone was bought from a company and it has the logo, ringtones and app from that company. Reason why there's no Oreo update yet with the company, so I have to wait but I really want the unbranded Oreo ROM.
What can I do? I really want Oreo unbranded but I don't know how to procced without screwing my phone. Thanks for reading, this is my first post in the forum.
Which Odin version have you used?
Ok i tell you u have to do to recover your phone and get oreo ?
1-u have to use new version of odin V13.3.1 (with LZ4 support )
2-Download any stock firmware oreo 8.0 from sammobile and flash it
Thats it
I case that not work with u so downlad combinition rom (factory binary rom ) and flash it
Wipe your phone then reflash stock rom oreo
It was very helpful for me
Reeii said:
Which Odin version have you used?
Click to expand...
Click to collapse
the latest version 3.13.1
ayman16 said:
Ok i tell you u have to do to recover your phone and get oreo
1-u have to use new version of odin V13.3.1 (with LZ4 support )
2-Download any stock firmware oreo 8.0 from sammobile and flash it
Thats it
I case that not work with u so downlad combinition rom (factory binary rom ) and flash it
Wipe your phone then reflash stock rom oreo
It was very helpful for me
Click to expand...
Click to collapse
No man, if it were that easy I wouldn't post anything. There's something that won't allow me to do it. It seems that because my phone is in "Pre-Normal" status on downlaod mode there's no chance to flash until it changes to "Normal," and for what I've read I have to wait one week. My question has to do with if is something serious the message "e: failed to find /misc partition" in download mode. What do I have to do from now on? Please read the whole post so you can understand my query. Thank you for your reply and intention to help. :good:
I have simmilar message, but i am not even rooted. "Failed to clear BCB message : failed to find misc partition."
There is nothing to worry about.
Hallo M8s,
i have flashed a samsung A505X ( demo device) with A505F firmware. Everything went successfully but phone stucks in download mode. Is there anyway to get the original demo Firmware to flash back? I have searched the net without avail.
Or let me formulate it this way, is there anyway to revive it?
Thanks
have you tried flashing with Odin patched version ?
Locutus974 said:
have you tried flashing with Odin patched version ?
Click to expand...
Click to collapse
Hallo,
no i have not tried with it. Let me do so and return to you for feedback.
Regards
Locutus974 said:
have you tried flashing with Odin patched version ?
Click to expand...
Click to collapse
Hallo,
I flashed it with Odin 3.13.1.3B PatchedD but still the same issue. When the phone starts it goes directly into download mode. Ttere is noway to enter recovery to wipe.
Regards
benarmand said:
Hallo,
I flashed it with Odin 3.13.1.3B PatchedD but still the same issue. When the phone starts it goes directly into download mode. Ttere is noway to enter recovery to wipe.
Regards
Click to expand...
Click to collapse
When boot in odin in does a message appear on the screen with red letters?
Hallo,
when I try a downgrade yes there is a message in red that appears notifying that the binary can’t be flashed..
But when I use binary 3 all went smoothly till the end and I get green signal in Odin, only phone ends up again in download mode.
Btw I have even bought the unique available demo firmware ( binary 1) on the market to flash it back to its former state, but it can’t be flashed coz I have upgraded the phone to binary 3. So I am looking for eventual workarounds to downgrade.
Regards
Hi all,
I updated my exynos S20 to latest FW via Smart Switch from PC. On 92% it stucked. I left it several minutes, but it did not helped.
I have blue screen with message - Secure check fail: (Radio). See attachement.
I tried to download the full FW package from sammobile and flash it over odin but it get stuck at prism.img, no error, just wouldnt move.
Any ideas please?
What did you use to update Smart Switch or Odin?
Idebutterpiep said:
What did you use to update Smart Switch or Odin?
Click to expand...
Click to collapse
The smart switch first and the update failed. I was also unable to restore the emergency backup from smart switch. So I tried to update it with Odin, but it failed on prism.img. I tried different odin version, cables, usb ports and PCs. I was broken so I gave it last chance and tried to restore emergency backup from smart switch once again and it passed. So I have phone back alive.
Hi! I have the same issue. I've tried to update to DUH5 XEO FROM DUH2 with Odin and it stoped on PRISM. I've tried the older (DUH2 and older) versions and I've got "not supporter version". I've tried DUH5 XEO severals times with diffrent cables and computers - no succes. I'm not able to use recovery with Smart Switch also - no recovery is found. I'm using original firmaware from sammobile. Error code is "secure check failed (radio)".
Any ideas how to unbrick the phone?
It failed again for me during september update via smartswitch. I was able to fix it again like I wrote before.
You can try to flash the previous august fw via odin. it will fail and you will see fail message with binary version on the display. unplug it, restart the phone and flash it vith odin again but now with september fw update. odin flash will pass and the phone will boot up to system.
smatak said:
It failed again for me during september update via smartswitch. I was able to fix it again like I wrote before.
You can try to flash the previous august fw via odin. it will fail and you will see fail message with binary version on the display. unplug it, restart the phone and flash it vith odin again but now with september fw update. odin flash will pass and the phone will boot up to system.
Click to expand...
Click to collapse
Hi! Thanks! I've tried so but with no success. I suspect:
1. something goes wrong with flashing and there is a wrong version information in memory
2. there was a change in previous version operator selection and multicert version is not possible any more for my phone
Thanks anyway. I'll wait for operators version a few days and we'll see.
Hi,
I face exactly same issue... I use XEF firmwares (France) and was on DUH2 version, I've tryied to update to DUH5 via ODIN, and the upade process stay stuck on PRISM step.
Now my phone boot with blue screen "An error has occured while updating the device software. Use the Emergency recovery function in the SmartSwitch app"
I've try different solutions but don't find yet how to sort it out :
a) Try again flash of DUH5 via ODIN, exactly same issue (ie : update stops on PRISM step)
b) Opened SmartSwitch emergency recovery menu, but It don't list nothing... no way to choose my phone!
c) Try to flash back the previous DUH2 fimaware via ODIN, it stops at the very begning of the process with this
message in red :
ON_FAIL_SECURE_CHECK_FAIL
SM_REV. CHECK FAIL (BOOTLOADER) DEVICE : 0xa BINARY : 0x9
d) Try to flash another country version (DBT / Germany) of the last firmware DUH5, without no more success
I'm really disapointed, and the FoMo is growing
Any idea on how to ressucite my precious S20 ?
noiwid said:
Hi,
I face exactly same issue... I use XEF firmwares (France) and was on DUH2 version, I've tryied to update to DUH5 via ODIN, and the upade process stay stuck on PRISM step.
Now my phone boot with blue screen "An error has occured while updating the device software. Use the Emergency recovery function in the SmartSwitch app"
I've try different solutions but don't find yet how to sort it out :
a) Try again flash of DUH5 via ODIN, exactly same issue (ie : update stops on PRISM step)
b) Opened SmartSwitch emergency recovery menu, but It don't list nothing... no way to choose my phone!
c) Try to flash back the previous DUH2 fimaware via ODIN, it stops at the very begning of the process with this
message in red :
ON_FAIL_SECURE_CHECK_FAIL
SM_REV. CHECK FAIL (BOOTLOADER) DEVICE : 0xa BINARY : 0x9
d) Try to flash another country version (DBT / Germany) of the last firmware DUH5, without no more success
I'm really disapointed, and the FoMo is growing
Any idea on how to ressucite my precious S20 ?
Click to expand...
Click to collapse
I had exactly the same issue just now. I just reflashed the HOME_CSC file. The phone then booted into a brief error message, but it went away and rebooted again. The phone appears to have rebooted fine just now with no issues... ¯\_(ツ)_/¯
Thanks for your feedback, I finaly find the way to get my phone back by trying again to reflash it with the DUH5 firmware, but this time with the CSC instead of the HOME_CSV... means it was cleared from all datas (except SD).
I had a full backup from 30 days ago, and autobackup of whatsapp/journal/messages from 3/7 days ago... so it wasn't so bad it could be. But it's really painfull and timekiller to end configuration of the phone (re-logon all apps / set them up), etc..
Moral : We should always take time to do a full backup before a firmware update...
unfnknblvbl said:
I had exactly the same issue just now. I just reflashed the HOME_CSC file. The phone then booted into a brief error message, but it went away and rebooted again. The phone appears to have rebooted fine just now with no issues... ¯\_(ツ)_/¯
Click to expand...
Click to collapse
This worked for me as well. I was stuck on PRISM.img and then I just yanked the phone from the USB connection and broke the Odin flash...Switched off the phone and booted into DOWNLOAD mode using the key combo...Then I flashed JUST the HOME_CSC_XXXX file in Odin and voila, my device has booted just fine! Thank you so much! Enough tinkering around with root and custom ROMs now...
Hi,
I just had exactly same issue while updating to the brand new One UI 4 +Android 12 on my S20 (SM-980F) with the Switzerland firmware (G980FXXSCEUL7 / G980FOXMCEUL6).
In ODIN I was stuck on PRISM step. I unplugged rawly the cable. Reboot (vol down + side button hold 7 sec), it restart with blue screen (bricked mode), I just repush HOME_CSC in ODIN and it fix the problem, reboot and complete the installation...... Really nice fix as I kept all my datas :/ Thanks
noiwid said:
Hi,
I just had exactly same issue while updating to the brand new One UI 4 +Android 12 on my S20 (SM-980F) with the Switzerland firmware (G980FXXSCEUL7 / G980FOXMCEUL6).
In ODIN I was stuck on PRISM step. I unplugged rawly the cable. Reboot (vol down + side button hold 7 sec), it restart with blue screen (bricked mode), I just repush HOME_CSC in ODIN and it fix the problem, reboot and complete the installation...... Really nice fix as I kept all my datas :/ Thanks
Click to expand...
Click to collapse
This was a life saver tip. I thought my data is gone as I had not backed up. But this worked like a charm.
I was updating to Android 12 One UI 4.0 from beta 2 of One UI 4.0 and it was stuck at Prism.img.
Flashed just the HOME CSC and rebooted just fine.
enjoylife1788 said:
This was a life saver tip. I thought my data is gone as I had not backed up. But this worked like a charm.
I was updating to Android 12 One UI 4.0 from beta 2 of One UI 4.0 and it was stuck at Prism.img.
Flashed just the HOME CSC and rebooted just fine.
Click to expand...
Click to collapse
Happy to read that ! #HappyEnd
noiwid said:
Hi,
I just had exactly same issue while updating to the brand new One UI 4 +Android 12 on my S20 (SM-980F) with the Switzerland firmware (G980FXXSCEUL7 / G980FOXMCEUL6).
In ODIN I was stuck on PRISM step. I unplugged rawly the cable. Reboot (vol down + side button hold 7 sec), it restart with blue screen (bricked mode), I just repush HOME_CSC in ODIN and it fix the problem, reboot and complete the installation...... Really nice fix as I kept all my datas :/ Thanks
Click to expand...
Click to collapse
Same issue,
This fixed it for me as well. thank you!
noiwid said:
Hi,
I just had exactly same issue while updating to the brand new One UI 4 +Android 12 on my S20 (SM-980F) with the Switzerland firmware (G980FXXSCEUL7 / G980FOXMCEUL6).
In ODIN I was stuck on PRISM step. I unplugged rawly the cable. Reboot (vol down + side button hold 7 sec), it restart with blue screen (bricked mode), I just repush HOME_CSC in ODIN and it fix the problem, reboot and complete the installation...... Really nice fix as I kept all my datas :/ Thanks
Click to expand...
Click to collapse
Thank you so much! Almost thought I got rid of all data on my mom's S20 haha
noiwid said:
Hi,
I just had exactly same issue while updating to the brand new One UI 4 +Android 12 on my S20 (SM-980F) with the Switzerland firmware (G980FXXSCEUL7 / G980FOXMCEUL6).
In ODIN I was stuck on PRISM step. I unplugged rawly the cable. Reboot (vol down + side button hold 7 sec), it restart with blue screen (bricked mode), I just repush HOME_CSC in ODIN and it fix the problem, reboot and complete the installation...... Really nice fix as I kept all my datas :/ Thanks
Click to expand...
Click to collapse
I created an XDA account just to say thanks for this answer. Fully functional on the S20+. Thank you!
________________________________________________________________________________________
Criei uma conta no XDA só para agradecer por essa resposta. Totalmente funcional no S20+. Obrigado!
Hi Victor,
Glad to see my message still help !
Thanks for your feedback.
noiwid said:
Hi,
I just had exactly same issue while updating to the brand new One UI 4 +Android 12 on my S20 (SM-980F) with the Switzerland firmware (G980FXXSCEUL7 / G980FOXMCEUL6).
In ODIN I was stuck on PRISM step. I unplugged rawly the cable. Reboot (vol down + side button hold 7 sec), it restart with blue screen (bricked mode), I just repush HOME_CSC in ODIN and it fix the problem, reboot and complete the installation...... Really nice fix as I kept all my datas :/ Thanks
Click to expand...
Click to collapse
Holy crap, this worked!
hay guys
it did not work on my s22 ultra any ideas
I tried everything
- reflash the older one
- the csc file only and the home_csc
- and the original one
- and also the csc file only
no matter what it gets stuck n PRISM.img Phase
HELP !!!!!!!
Ayman__0 said:
hay guys
it did not work on my s22 ultra any ideas
I tried everything
- reflash the older one
- the csc file only and the home_csc
- and the original one
- and also the csc file only
no matter what it gets stuck n PRISM.img Phase
HELP !!!!!!!
Click to expand...
Click to collapse
Did you get through with this? I have the same problem!