I need to revert back to CRL1 or CRK1 from DRL7 and i can't figure it out, I tried using ODIN but I always get All threads completed. (succeed 0 / failed 1). On S8 SM-G950U ATT. I also get the dm-verity error when trying to use the sd card method.
So is your efs corrupted? Check the bootloader versions. Odin should work no problem as long as the bootloaders are the same.
any resolution for this?
Related
Hi there!
I recently tried to install the Echoe ROM onto my Samsung Galaxy S4 GT-I9505 and now it is soft bricked and I cannot restore it back to stock. I have tried flashing it with Odin however it simply comes up with the error '<ID:0/004> Complete(Write) operation failed. <OSM> All threads completed. (succeed 0 / failed 1)'. I have tried repartitioning the device with a pit file but still no luck. I have even tried disabling my firewall and antivirus in case that does something but I have still not been able to do it.
If anyone can help it would be greatly appreciated!
Gerald746 said:
Hi there!
I recently tried to install the Echoe ROM onto my Samsung Galaxy S4 GT-I9505 and now it is soft bricked and I cannot restore it back to stock. I have tried flashing it with Odin however it simply comes up with the error '<ID:0/004> Complete(Write) operation failed. <OSM> All threads completed. (succeed 0 / failed 1)'. I have tried repartitioning the device with a pit file but still no luck. I have even tried disabling my firewall and antivirus in case that does something but I have still not been able to do it.
If anyone can help it would be greatly appreciated!
Click to expand...
Click to collapse
How did you installed Echoe?
Gerald746 said:
Hi there!
I recently tried to install the Echoe ROM onto my Samsung Galaxy S4 GT-I9505 and now it is soft bricked and I cannot restore it back to stock. I have tried flashing it with Odin however it simply comes up with the error '<ID:0/004> Complete(Write) operation failed. <OSM> All threads completed. (succeed 0 / failed 1)'. I have tried repartitioning the device with a pit file but still no luck. I have even tried disabling my firewall and antivirus in case that does something but I have still not been able to do it.
If anyone can help it would be greatly appreciated!
Click to expand...
Click to collapse
Wich version of echoerom and why not ask in echoe thread anyway check this out
http://forum.xda-developers.com/showthread.php?t=2265477
speedwayfan75 said:
How did you installed Echoe?
Click to expand...
Click to collapse
I tried flashing with Odin.
Gerald746 said:
I tried flashing with Odin.
Click to expand...
Click to collapse
No custom rom can be flashed with odin. You need a custom recovery for flashing a custom ROM.
Can you enter download mode?
speedwayfan75 said:
No custom rom can be flashed with odin. You need a custom recovery for flashing a custom ROM.
Can you enter download mode?
Click to expand...
Click to collapse
Sorry no I didn't I used the bootloader but something obviously went wrong and yes I can enter download mode.
Gerald746 said:
Sorry no I didn't I used the bootloader but something obviously went wrong and yes I can enter download mode.
Click to expand...
Click to collapse
You used the bootloader????
How can you use a bootloader and for what?
speedwayfan75 said:
You used the bootloader????
How can you use a bootloader and for what?
Click to expand...
Click to collapse
Hahaha no my friend he should used the boobloader[emoji6]
Gerald746 said:
Hi there!
I recently tried to install the Echoe ROM onto my Samsung Galaxy S4 GT-I9505 and now it is soft bricked and I cannot restore it back to stock. I have tried flashing it with Odin however it simply comes up with the error '<ID:0/004> Complete(Write) operation failed. <OSM> All threads completed. (succeed 0 / failed 1)'. I have tried repartitioning the device with a pit file but still no luck. I have even tried disabling my firewall and antivirus in case that does something but I have still not been able to do it.
If anyone can help it would be greatly appreciated!
Click to expand...
Click to collapse
Well you can't flash any custom rom through ODIN.
the only thing you can do is go to download mode root your phone again and see if you can restore a nandroid backup succesfully at least if you thought about creating a nandroidbackup before flashing a new rom.
if this is not working install stock rom first and then try to install a custom rom of your choice.
goodluck
My phone is currently stuck saying:
"Samsung Galaxy Note3
Custom"
History: installed rooted NC2 months ago, phone ran really crappy, had safestrap recovery, decided i'd sit down to install jasmine rom eventually
Today: followed Jasmine 5.0 directions, did a wipe, I believe the wipe told me "cannount unmount internal storage"
did this twice, and phone rebooted.
got a loop of "samsung galaxy note3 custom"
followed this: http://www.androidrootz.com/2013/10/how-to-unrootunbrick-galaxy-note-3.html
(Note: Jasmine never installed, i got tripped up when i tried to wipe cache, etc) I was on 4.4.2
Now I get "samsung galaxy note3 custom" without a loop.
---
I can boot to recovery, but I suppose I have nothing it can install to recover. I am not 100% sure what steps to take. I realize this topic gets posted often, I am sorry. I read through a number of "I bricked my phone" topics before posting this.
skidawgz said:
My phone is currently stuck saying:
"Samsung Galaxy Note3
Custom"
History: installed rooted NC2 months ago, phone ran really crappy, had safestrap recovery, decided i'd sit down to install jasmine rom eventually
Today: followed Jasmine 5.0 directions, did a wipe, I believe the wipe told me "cannount unmount internal storage"
did this twice, and phone rebooted.
got a loop of "samsung galaxy note3 custom"
followed this: http://www.androidrootz.com/2013/10/how-to-unrootunbrick-galaxy-note-3.html
(Note: Jasmine never installed, i got tripped up when i tried to wipe cache, etc) I was on 4.4.2
Now I get "samsung galaxy note3 custom" without a loop.
---
I can boot to recovery, but I suppose I have nothing it can install to recover. I am not 100% sure what steps to take. I realize this topic gets posted often, I am sorry. I read through a number of "I bricked my phone" topics before posting this.
Click to expand...
Click to collapse
Go to sammobile.com and get the 4.4.2 firmware and use Odin (latest version) to install.
You'll have to reroot (which can be done on 4.4.2) and reinstall safestrap.
The above presumes you don't have a backup made with safestrap.
Sent from my Note 3 via Tapatalk
donc113 said:
Go to sammobile.com and get the 4.4.2 firmware and use Odin (latest version) to install.
You'll have to reroot (which can be done on 4.4.2) and reinstall safestrap.
The above presumes you don't have a backup made with safestrap.
Sent from my Note 3 via Tapatalk
Click to expand...
Click to collapse
Thanks much for your help!
I'm getting this:
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Also I did make backups, I was just able to find them.... However I have several folders/files with long names. Not sure which is the backup
skidawgz said:
I'm getting this:
FAIL! (Auth)
Complete(Write) operation failed.
All threads completed. (succeed 0 / failed 1)
Also I did make backups, I was just able to find them.... However I have several folders/files with long names. Not sure which is the backup
Click to expand...
Click to collapse
Which version of Odin are you using? I believe you need 3.09 or higher.
How did you make the backups? If via Safestrap...you have to use it to recover. The date of the backup is typically embedded in the file name.
Also if you haven't. ...read this thread
http://forum.xda-developers.com/showthread.php?t=2483380
Sent from my Note 3 via Tapatalk
Odin3_v3.10.6 and ill check that out thanks!
The phone says
SW REV CHECK FAIL : [aboot]Fused 4 > Binary 3
skidawgz said:
The phone says
SW REV CHECK FAIL : [aboot]Fused 4 > Binary 3
Click to expand...
Click to collapse
That means you're trying to install an older version of the software. You must load either 4.4.4 or 5.0 because the bootloader was updated to either 4.4.4 or 5.0 at some point.
That means you've lost root.
Sent from my Note 3 via Tapatalk
donc113 said:
That means you're trying to install an older version of the software. You must load either 4.4.4 or 5.0 because the bootloader was updated to either 4.4.4 or 5.0 at some point.
That means you've lost root.
Sent from my Note 3 via Tapatalk
Click to expand...
Click to collapse
Thats what I feared, but I guess not the absolute end of the world... Should I essentially just stick with stock Verizon updates from now on?
I cannot get root back past the NC4 bootloader right?
skidawgz said:
Thats what I feared, but I guess not the absolute end of the world... Should I essentially just stick with stock Verizon updates from now on?
I cannot get root back past the NC4 bootloader right?
Click to expand...
Click to collapse
Yes, that is correct. You can load either 4.4.4 or 5.0 via Odin. You can get either version on sammobile. And correct...no root available for either. So all you'll have is stock updates from now on unless someone magically figures out how to get root on those....very unlikely though.
Sent from my Note 3 via Tapatalk
Phone is up and running again on 5.0 and I'd like to thank you for your support!
skidawgz said:
Phone is up and running again on 5.0 and I'd like to thank you for your support!
Click to expand...
Click to collapse
Glad to assist. While you may have lost root..you also no longer have an expensive brick.
Sent from my Note 3 via Tapatalk
Hey everyone, I posted this in the standard Galaxy S7 Edge forum, but I realize that this would probably be the more appropriate forum to post in.
Mods, can you possibly delete the other thread?
My friend accidentally flashed the ATT Nougat firmware to his VZW Galaxy S7 Edge. He asked my help to restore it back to VZW stock firmware.
The current Baseband Version on this phone is: G935AUCS4BQE1
I downloaded Odin 3.12.3 and the firmware: G935VVRU4BQA2_G935VVZW4BQA2_VZW
After correctly selecting the BL, AP, CP, CSC files, I get an error message saying:
<ID:0/004> FAIL! SHA256 is invalid
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
In the other thread, I was told to download the correct Verizon firmware, but I was under the impression that this was indeed the latest official verizon firmware.
Out of curiosity, I was wondering which firmware would be the most appropriate to flash. The phone does still boot up. Any help would be appreciated. Thank you!
G930TUVS4BQL2_CL12142063_QB16000831_REV02_user_low_ship_MULTI_CERT_meta.tar.rar
Thanks. I will try it on my boot looped SM-G930T tonight.
First off, Thank you to muniz_ri for the zip.
I have a 930A (S7) running ATT firmware and having some issues every now and then running the ATT firmware on TMobile (my phone suddenly is not recognized by TMo and 4G data stops working. I have to switch the SIM card with another TMo user and switch back to my SIM and it starts working...).
I tried to load the previous version yesterday of the TMo firmware posted by muniz_ri (G930TUVS4BQJ2) and Odin (Prince) failed with a Write failure- some file was larger than could be written (ext4 fail). It then stuck at boot.
I was able to recover by flashing the ATT firmware back again.
Question- How do I get this latest TMo firmware onto the phone? Do I need to repartition or something?
Thanks for your time.
webzo said:
First off, Thank you to muniz_ri for the zip.
I have a 930A (S7) running ATT firmware and having some issues every now and then running the ATT firmware on TMobile (my phone suddenly is not recognized by TMo and 4G data stops working. I have to switch the SIM card with another TMo user and switch back to my SIM and it starts working...).
I tried to load the previous version yesterday of the TMo firmware posted by muniz_ri (G930TUVS4BQJ2) and Odin (Prince) failed with a Write failure- some file was larger than could be written (ext4 fail). It then stuck at boot.
I was able to recover by flashing the ATT firmware back again.
Question- How do I get this latest TMo firmware onto the phone? Do I need to repartition or something?
Thanks for your time.
Click to expand...
Click to collapse
I figured I would try flashing the new software you have provided above, and maybe have better luck. But no, still same deal. I captured the log messages this time-
Odin stated-
system.img.ext4
FAIL! (ext4)
Complete (write) operation failed
On the phone, I see this-
Volume size is too big 1228800 < 1254400
ODIN: Invalid ext image
[18] eMMC write fail system
So, something is too big to be written into the existing partition, I guess.
It sounds like, reading through some posts, I need to use a PIT file and re-partition or something
Any ideas on how to approach this?
By the way, yesterday, I was able to get out of the boot loop by using Odin Prince Comsey to flash to G930AUCS4BQE1 (ATT firmware from june-2017)
Today, Prince comsey wouldn't work. It ended up at-
FAIL! Model dismatch fail
After some digging around, it seemed like Odin Prince Comsey is not to be used for Stock ROMs... tried with Odin 3.12.3 and that never got past "SetupConnection". Tried again with Odin 3.12.10 and that worked.
Anyway, back to the problem at hand.... I am at G930AUCS4BQE1 (ATT from June) and need to get to G930TUVS4BQL2 (TMo, December) or G930UUEU4BQJ5 (latest 930U).
Any pointers are greatly appreciated..
Thanks.
I believe flashing the csc file rather than the home_csc automatically reformats the partitions for the rom you are flashing. If it does not, you are correct that you need the pit file which is used to reformat partitions accordingly. The pit file for TMobile can be found around this forum.
Hi Folks,
I am running a OneUI based custom ROM and have TWRP flashed in my S7 Edge. I am trying to flash the stock Rom via ODIN but it does not work. After clicking START button in ODIN, it shows 'All threads completed. (succeed 1 / failed 0)' and phone restarts immediately and boots to the OS. No flash happens!.
Please help. Thanks in advance.