I don't have high hopes that this is fixable, but my Verizon Galaxy S4 phone was bricked after taking the OC1 update.
Long story short, I flashed the stock Lollipop OC1 firmware to my phone via Odin3 (v3.10) instead of the neutered one with the NK4 bootloader, by accident... I stupidly didn't read the full file name in a hurry. So, now I have an unrooted stock OC1 lollipop firmware on my machine.
Not doing all my research and thus not knowing that the OC1 bootloader is locked, I tried to use Odin to re-flash an NC5 boot.img (the old NG6 to NC5 downgrade method). This actually flashed just fine. But, it put me in a bootloop.
So, I tried to re-flash the full stock OC1 firmware. This failed as per the Odin output below:
File analysis...
SetupConnection...
Initialization...
Get PIT for mapping...
Firmware update start...
SingleDownload.
boot.img
NAND write start!!
recovery.img
system.img.ext4
__XmitData_Write
Complete(Write) operation failed.
All threads completed. (succeed 0 / failed 1)
I get similar failing results whenever I try to flash any firmware via Odin.
So I can only access download mode. My recovery won't boot, and when I just try to boot it up normally it gave a screen saying:
Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again.
So I download Kies, it recognizes there is a device there, but doesn't recognize it as a compatible device.
I use the Kies option under tools "Emergency firmware recovery," but the device doesn't pop up as one in need of recovery.
So I use the "Firmware Upgrade and Initialization" tool. I type in Galaxy S4, it downloads the firmware, starts updating... and has an unexpected error. It says to run recovery. But I already tried that, and the device isn't recognized.
However, now on boot there is a slightly newer screen, saying:
Software Update Failed
Your device didn't update successfully. Use the Verizon Software Repair Assistant on a computer to repair your device and complete the update.
(sorry I don't have a picture)
Now, I can't install the Verizon Software Upgrade/Repair Assistant because apparently you can't download it from their site, since it is supposed to install automatically when you plug your phone into your computer via USB. That obviously isn't happening with my phone in the state it's in.
On XDA here, I found someone posting this software Repair Assistant as "SUA_ar" tool. It installed on my computer, but the software doesn't even recognize my device when it is plugged in, so it won't even try to recover.
By the way, both in download mode and when I try to boot up, the top left of the screen says this:
ODIN MODE
PRODUCT NAME: SCH-I545
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
REACTIVATION LOCK: OFF
CSB-CONFIG-LSB: 0x30
SECURE DOWNLOAD: ENABLE
WRITE PROTECTION: Enable
eMMC BURST MODE: enabled
At this point, I don't care about root, tripping KNOX, or anything. I just want to know if there is a way I can get it working as a phone again.
I definitely deserve mockery for my stupidity, but if you can help, too, that would be great.
@KaosMaster (I think)has a special little ZIP that may work. It is the full wipe, but it also contains files for re partition and whatnot. That MIGHT work.
You must use the following files:
https://docs.google.com/file/d/0B4RU_ZH5QUASNmxLX3JpejBXREE/edit?usp=docslist_api
If you want to revert to NK1 please use this image!
https://docs.google.com/file/d/0B4RU_ZH5QUAST1M5WkRNcy1Xek0/edit?usp=docslist_api
This is to repair to OC1:
https://docs.google.com/file/d/0B4RU_ZH5QUASaU9LcDJ3WWZfdXM/edit?usp=docslist_api
In the ODIN you just downloaded, select the CSC button, and select the extracted ALl_VZW_I545****.tar.md5
Then select these checkboxes:
Auto-Reboot
Re-Partition
F. Reset Time
NAND Erase All
Phone Bootloader Update
Phone EFS Clear
Hit START
Wow, thanks for the quick responses!
Unfortunately, the phone doesn't seem to want to let it do the NAND erase all for some reason! Or at least that's what I gather from this output:
Odin v.3 engine (ID:5)
File analysis...
SetupConnection...
Initialization...
Erase...
Complete(Write)operation failed.
All threads completed. (succeed 0 / failed 1).
This happened with both the NK1 and the OC1. Strange, I don't know what is limiting that Erase procedure...
In the top left corner of the phone, under all the ODIN MODE data, now it says:
START[224,1440]
ERASING USERDATA PARTITION...
And there is just a tiny bit of progress bar under the android logo.
If that matters.
Just uncheck the erase all for now, but I would try one more time with that setup...
It should just work
---------- Post added at 05:56 AM ---------- Previous post was at 05:55 AM ----------
And you didn't select re partition...
That is important
I did select re-partition, sorry I forgot to include that part in the output.
I unchecked "NAND erase all" and it had this failure after Initialization...
Set PIT file...
DO NOT TURN OFF TARGET!!
Get PIT for mapping...
Firmware update start..
SingleDownload.
aboot.mbn
NAND Write Start!!
FAIL! (Auth)
Complete(Write) operation failed.
All threads completed. (succeed 0 / failed 1)
You have to use the OC1 lollipop file then
Pull battery, re insert, then ODIN mode on power
Yes, this is actually with the OC1 file you provided, in the CSC slot. Should I try it in the AP slot with same options (except NAND erase)?
Oh...you can try that!! But I am worried about your hardware NOW.
If you just let it start, it gets to the emergency screen?? If yes, ODIN flash with that screen on the device.
Also they battery must be above 80% or it might not flash.
Oh, you mean do not flash it in Download mode? I should flash it in the screen where it says "Software Update Failed" ?
Yes try that
Also..I am working on a set of repair files
It made it farther!
I haven't tried AP slot yet. This is with OC1 file, in CSC slot, selecting NAND Erase All (and the other ones you said too)
Initialization..
Erase..
Set PIT file..
DO NOT TURN OFF TARGET!!
Get PIT for mapping..
Firmware update start..
SingleDownload.
aboot.mbn
NAND Write Start!!
sbl1.mbn
sbl2.mbn
sbl3.mbn
rpm.mbn
Complete(Write) operation failed.
etc...
Pull battery...go into ODIN...repeat
Ughh. Now Odin isn't even recognizing my phone in the emergency screen. It still recognizes it in download mode, though.
It was seeing it before in the emergency screen, obviously. Restarted Odin, restarted my phone a couple times, still nothing. Trying a couple more times.
Go to where you hold the buttons to download...This is ODIN. Will have the boot to flash in 5 mins
Good things happening! I just took it out and inserted it a couple more times after restarting Odin.
It's now flashing system.img.ext4 and hasn't failed yet. Fingers crossed...
Awesome!! All the checkboxes marked also??
Yes, even NAND Erase All.
That's how we ROLL!! Enjoy! Your device is like brand new!
You are very much the man, Kaos! It's back up!
I've been addicted to root for the past 4 years with various devices, but I think I'll chill out with that after this craziness. ... for now.
Related
Hi guys,
So I tried to root my phone today - I dont know what happened or what I did wrong, but my phone now is locked constantly into a boot cycle. It'll turn on, boot into the lockscreen for maybe 20 seconds, then reboot itself. Nothing i do seems to help. I tried flashing back to the stock rom, flashing back to stock rom + root, but to no avail. Ive been desperately trying to find a solution that will at least allow me to get to the data on the phone (i have some pictures that i haven't backed up that are absolutely essential) and then i have no problem doing a complete data wipe or whatever is necessary.
Someone PLEASE help! phone is completely unusable at this point!
Yes, I can enter download mode
re: Boot Looping
victor3063 said:
Hi guys,
So I tried to root my phone today - I dont know what happened or what I did wrong, but my phone now is locked constantly into a boot cycle. It'll turn on, boot into the lockscreen for maybe 20 seconds, then reboot itself. Nothing i do seems to help. I tried flashing back to the stock rom, flashing back to stock rom + root, but to no avail. Ive been desperately trying to find a solution that will at least allow me to get to the data on the phone (i have some pictures that i haven't backed up that are absolutely essential) and then i have no problem doing a complete data wipe or whatever is necessary.
Someone PLEASE help! phone is completely unusable at this point!
Yes, I can enter download mode
Click to expand...
Click to collapse
When you flashed the STOCK rom was it a ZIP or a TAR file?
Before I can help I need to know.
Zipfiles require CWM Recovery for flashing and TAR files require ODIN for flashing.
I flashed the TAR file in ODIN 1.85, PDA.tar from the unzipped file UCKH7_stock_odin.7z
So I just tried it again, for something like the 4th or 5th time. I checked only "AUTO REBOOT" and "RESET TIME" in Odin, selected PDA as PDA.tar from UCKH7_stock_odin, got the following sequence from Odin
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> factoryfs.img
<ID:0/006> NAND Write Start!!
<ID:0/006> zImage
<ID:0/006> RQT_CLOSE !!
<ID:0/006> RES OK !!
<ID:0/006> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/006> Removed!!
<ID:0/007> Added!!
<ID:0/007> Removed!!
<ID:0/007> Added!!
<ID:0/007> Removed!!
where I'm locked into the bootcycle again. It does boot up into my lock screen, I can interact with the screen for maybe 10 seconds, and then it just reboots. I've let it run for a little while to see if it can figure itself out, but after the third or fourth time i get nervous and pull the battery.
victor3063 said:
I flashed the TAR file in ODIN 1.85, PDA.tar from the unzipped file UCKH7_stock_odin.7z
Click to expand...
Click to collapse
ok, here is what to do.
Download this stock rooted rom: http://www.multiupload.com/PNQC9KOD4D
and download the MODEM file for the rom: http://www.multiupload.com/VWTSCXE5L0
After you extract both TAR files flash both of them at the same time by
putting the PDA tar file into the PDA slot in ODIN and the MODEM tar file
in the PHONE slot in ODIN then start flashing.
Don't check or uncheck any checkboxes in ODIN.
When its done flashing, it should boot into the STOCK ROOTED rom.
Before, or after doing the above boot into recovery and do a data wipe/factory reset
Sent from my SAMSUNG-SGH-I777 using XDA App
Didn't work. Still stuck in the same boot pattern. Redownloaded ODIN, redownloaded all the links again just to guard against any kind of corrupted files, but same end result, constant reboot cycle.
Samsung galaxy s2 --> at&t rethink possible --> preparing usb storage/lock screen --> reboot
You probably need to do a wipe data/factory reset.
Since you apparently have files that you want - enter CWM recovery and adb pull them.
re: try this
victor3063 said:
So I just tried it again, for something like the 4th or 5th time. I checked only "AUTO REBOOT" and "RESET TIME" in Odin, selected PDA as PDA.tar from UCKH7_stock_odin, got the following sequence from Odin
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> factoryfs.img
<ID:0/006> NAND Write Start!!
<ID:0/006> zImage
<ID:0/006> RQT_CLOSE !!
<ID:0/006> RES OK !!
<ID:0/006> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/006> Removed!!
<ID:0/007> Added!!
<ID:0/007> Removed!!
<ID:0/007> Added!!
<ID:0/007> Removed!!
where I'm locked into the bootcycle again. It does boot up into my lock screen, I can interact with the screen for maybe 10 seconds, and then it just reboots. I've let it run for a little while to see if it can figure itself out, but after the third or fourth time i get nervous and pull the battery.
Click to expand...
Click to collapse
Try this first if you have not tryed it yet, it looks like odin flashed the PDA
file sucessfully, but did not flash the modem.
So put the modem into the PDA slot in ODIN and flash it.
If that don't work then do it vica versa and only flash the
PDA file in the PDA slot in ODIN.
This way you will know for sure which TAR file is not flashing.
(if you only have one TAR file to flash at a time with ODIN always put it in PDA slot)
If that don't work then try the method below.
Try this, turn off the phone or pull the battery, turn the phone back on or
replace the battery and go into CWM recovery and select
"Wipe Data/Factory Reset" Don't worry, it will NOT delete any pictures
or videos, or anything which you personcally have saved into a folder
you have created and it will not even touch the external sdcard if you have one.
It will however delete all the apps which you have installed in the phone prior
to having the problems you have now..
Is the data wipe / factory reset going to delete pictures off my phone? thats really my last resort.. I have a couple dozen pictures that I took on my phone since i purchased that I haven't had a chance to backup.
Does anybody have any ideas?
victor3063 said:
Is the data wipe / factory reset going to delete pictures off my phone? thats really my last resort.. I have a couple dozen pictures that I took on my phone since i purchased that I haven't had a chance to backup.
Does anybody have any ideas?
Click to expand...
Click to collapse
Its not going to delete any pictures, videos or even music you have
on the phone.
Anything which YOU have SAVED to the phone will not be touched
except usernames or passwords, credit card #'s might be deleted.
But actual files or folders you created will stay intact as well as
the external sdcard if you have one will not even be touched.
I think the reboot is occurring due to corrupted settings of network or files ystem. You can try this. pull out the battery, remove sim and sd card if you have any, then try booting..
Factory reset or data wipe should not theoretically wipe your pictures.. It basically wipes only /data partition. I have done factory reset which retained my pictures..
But to be on safer side, try the above step to see, if you can get the phone running..
Had same issue trying to factory restore with Odin. Wipe from e3 did the trick.
Sent from my SAMSUNG-SGH-I777 using XDA App
victor3063 said:
Is the data wipe / factory reset going to delete pictures off my phone? thats really my last resort.. I have a couple dozen pictures that I took on my phone since i purchased that I haven't had a chance to backup.
Does anybody have any ideas?
Click to expand...
Click to collapse
Those SHOULD be on /sdcard, but I can't guarantee it. Also, if you use 3e recovery, there's a chance that might hit /sdcard.
MJ, you should never guarantee something like that to someone.
Make sure you have ADB set up - I suggest Googling Droid Explorer if you're on Windows
Flash a CWM-enabled kernel
Enter CWM using the three-finger trick (this should work fine)
In CWM, go to Mounts and Storage and mount /sdcard and /data if they are not mounted
Connect to your phone using ADB and start looking for your files - I think Droid Explorer makes this MUCH easier by providing a nice graphical frontend to ADB push/pull
so this is what i'm doing right now.
Obviously my problem is constant rebooting.
1. Flash UCKH7 stock odin PDA.tar and UCKH7 modem via odin onto phone via odin
2. flash CWM recovery ClockworkMod Recovery 5.0.2.3 via odin as PDA
3. both these step pass OK, now Samsung Galaxy S2 I9100 bootscreen with yellow triangle shows up + at&t logo, however constant reboot problem is still present
4. pull battery unplug usb replugin battery and attempt to enter cwm recovery via holding down volume up+volume down+power button
5. CWM based recovery 5.0.2.3 flashes up for a brief second after bootscreen, then immediately reboots and reenters boot cycle
REALLY stuck here. i spent the whole day looking through the forum and i'm really not sure where i went wrong. the only thing that doesnt have the reboot cycle is download mode.
im basically trying to reach the step where i can enter cwm recovery and attempt to do a factory wipe, but it still reboots the enter i enter cwm recovery and enters the normal reboot cycle. i have NO IDEA how i couldve corrupted the file system this badly, perhaps the usb cable got bumped during the initial root? who knows. all i know is i cant even bring the phone to any form of usable status right now. any ideas?
re: boot looping
victor3063 said:
im basically trying to reach the step where i can enter cwm recovery and attempt to do a factory wipe, but it still reboots the enter i enter cwm recovery and enters the normal reboot cycle. i have NO IDEA how i couldve corrupted the file system this badly, perhaps the usb cable got bumped during the initial root? who knows. all i know is i cant even bring the phone to any form of usable status right now. any ideas?
Click to expand...
Click to collapse
You really do have a problem.......
I remember before getting this new SGS2 when I had the Samsung Infuse.
There was a thread in the Infuse forum called "The Ultimate Unbrick", I know
that there is a simular thread here for our SGS2 however the unbrick here is
lacking the PIT file.
I am 100% sure that if you could get a hold of something like the
Ultimate Unbrick which included the *.PIT file that it would solve the
problem you have.
The Ultimate Unbrick for the Samsung Infuse consisted of a
PDA*.TAR, PHONE*.TAR and the *.PIT file and it came with ODIN too.
The PIT file repartitions the sdcard to stock which fixes any partition
errors the phone may have due to flashing a non-compatible rom or
due to the flashing process being interupted while odin was flashing.
You might want to ask around the forum here if anyone has a stock
ODIN rom which includes PDA, MODEM and the PIT file for SGS2 i777.
I know for a fact that for the Infuse phone a complete stock package like
that always worked for fixing and solving problems like yours.
The only problem a package like this could not fix was if the phone
was hard-bricked meaning that it would not turn on at all no matter what.
Good luck with it..........
wow, the thought that i might be completely bricked is genuinely terrifying. really frustrating too, as i definitely consider myself fairly tech savvy.
Are you getting any indication that any of your capacitive buttons are acting like they are continually being pressed?
Did your phone at any time get wet?
The reason I ask is it almost seems like a hardware problem at this point. I would pull your battery and check the water indicators and see if there are any signs of moisture.
If there are no signs of moisture and you are pretty positive the phone is dry I would put the battery back in, don't turn it on, plug it into a wall charger and let it charge for a few hours. Then try to get into recovery again.
If after that you are still getting boot loop even in recovery we will link you to a .pit file and have you try a re flash to stock with a re partition.
Sent from my SAMSUNG-SGH-I777 using XDA App
thanks for the advice dayv.
I'm 100% sure theres been no water damage. I've barely had the phone for a week, and everything was working fine up until now. Other than that, I guess i'm going to have to go for the pit method - going to charge the phone overnight, see if it boots into cwm one last time, and then i'm going to use the following pit file from paulyhoffman
http://forum.xda-developers.com/showthread.php?t=1286218
so just to go over the procedure one last time - download mode on phone (only thing that seems to be working correctly so far)
flash PIT (I777UCKH7.pit), PDA (PDA.tar) and PHONE(UCKH7_modem.tar) at the same time, with REPARTITION, AUTO REBOOT, and RESET TIME checked in Odin?
Hi guys,
I've owned android phones since the G1, motocliq, nexus, sgs2 (intl), motodroid, all rooted, custom rom, etc etc... So when a friend asked me to unlock (for which i had to root) his i777 I thought I could handle it.
I followed the guide: http://forum.xda-developers.com/showthread.php?t=1286220
Went into download mode (could only do it with the VOL+-USB trick) and flashed CWM on Odin. Flashed fine, no problem, rebooted and only showed SAMSUNG letters on the bootup, nothing more. Tried going into CWM Recovery, no luck, Download mode, works fine. So I went over and re-flashed it, worked, but still can't get it to boot, or Recovery to work.
So then I started trying to flash other PDA's thinking i could do it, and maybe cwm was bugged, every time I try to flash ANYTHING that's not that specific CWM it says Write error, FAILED. When i reboot, the phone is softbricked (computer-phone logo saying connect recovery on kies). After this nothing at all will flash, except that CWM, which gives me download mode again... Which doesnt matter because the softbrick screen is a download mode in itself.
Im running out of options, im not sure where I should keep looking, Heimdall, installed, tried to flash, it transfers, at 99% says error writing and cancels. Tried flashing a new .pit and repartitioning, same story, wont let me.
Any suggestions would be more than welcomed :/
Sincerely,
Rodo
See if you can go back to out of box:
http://galaxys2root.com/att-galaxy-s2/how-to-unroot-att-galaxy-s2-sgh-i777/
Rodocopz said:
Hi guys,
I've owned android phones since the G1, motocliq, nexus, sgs2 (intl), motodroid, all rooted, custom rom, etc etc... So when a friend asked me to unlock (for which i had to root) his i777 I thought I could handle it.
I followed the guide: http://forum.xda-developers.com/showthread.php?t=1286220
Went into download mode (could only do it with the VOL+-USB trick) and flashed CWM on Odin. Flashed fine, no problem, rebooted and only showed SAMSUNG letters on the bootup, nothing more. Tried going into CWM Recovery, no luck, Download mode, works fine. So I went over and re-flashed it, worked, but still can't get it to boot, or Recovery to work.
So then I started trying to flash other PDA's thinking i could do it, and maybe cwm was bugged, every time I try to flash ANYTHING that's not that specific CWM it says Write error, FAILED. When i reboot, the phone is softbricked (computer-phone logo saying connect recovery on kies). After this nothing at all will flash, except that CWM, which gives me download mode again... Which doesnt matter because the softbrick screen is a download mode in itself.
Im running out of options, im not sure where I should keep looking, Heimdall, installed, tried to flash, it transfers, at 99% says error writing and cancels. Tried flashing a new .pit and repartitioning, same story, wont let me.
Any suggestions would be more than welcomed :/
Sincerely,
Rodo
Click to expand...
Click to collapse
Use my return-to-stock packages from dev forum.
Hi Entropy, I've tried but I can't seem to find an Odin flashable .tar, they're all CWM flashes and my CWM is screwed.
> http://forum.xda-developers.com/showthread.php?t=1289460
Oh and I tried flashing http://forum.xda-developers.com/showthread.php?t=1286432 with heimdall too. write error
Did you try this?
http://forum.xda-developers.com/showthread.php?t=1286432
This has the back to stock odin files, Thanks to Entropy!
This has UCKH7_stock_odin_noroot.7z which is flashable by odin. Try this.. You have to use 7zip to get the tar file..
Yup.. no luck :/
Error writing
Changed drivers, installed heimdall, used a different computer, no luck. (and works just fine with my other phones so I doubt its that.)
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> factoryfs.img
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Try installing Entropy's stock, or stock + root using one of these Odin3 One-Click Downloaders. That will take some of the variables out of the equation. If that doesn't go, you need to figure out if the problem in in the pc or the phone. Let us know your results.
I don't guess you need instructions, but if you do, they are in the flashing custom binaries guide linked in my sig.
Tried at least two previously, they report the same error. giant FAIL in red. I tried another computer previously, and this computer flashes my i9100 just fine (which i presume are the same drivers). In any case I installed the heimdall drivers for USB (on windows, which ruins Odin, but works fine after you uninstall those drivers) included in the package.
Still having no luck with this issue... Anyone know what could be causing that write error on download mode Odin? Perhaps I could flash a different recovery console?
Have you installed Samsung kies just to make sure you have proper drivers? Can make all the difference in the world.
Some people have a tough time getting the wrong drivers uninstalled. Easy check if that is the problem, go to a different pc that you haven't plugged your phone into and first install the right version of kies that you need.
Then plug your phone in and flash through Odin, transfer files over or redownload, hopefully all will be well.
Sent from my SAMSUNG-SGH-I777 using XDA App
Im still stuck with this issue and apparently after a few extra flashes it now shows:
Custom binary download: NO
Current Bunary: Samsung Official
Which isnt true, but w/e. It will still only flash SGH-1777 clockwork recovery and it will now not even show the samsung logo and become unresponsive as soon as you put the battery in. (the phone heats up, even if i dont try to turn it on, drains the battery dead in a couple hours)
So, I want to give it a try with heimdall and a full repartitioning, but I do not have the necessary files. Ive been looking and I cant find all the partition files, aka
PDA/Code:
FactoryFS=factoryfs.frs
Kernel(zImage)=zImage
Param.lfs=param.lfs
Primary Bootloader=boot.bin
Secondary Bootloader=slb.bin
CSC:
Cache=cache.rfs
Database Data=dbdata.rfs
In Other:
Modem=modem.bin
Recovery=recovery.bin
Could someone dump these files for me? Thanks!
Stupidly, I took the update (to MI1) after getting my new S4. I later discovered this meant Safestrap was my only option for installing custom ROMS.
Even more stupidly, I decided I wanted to do a 'clean' install of my ROM, so I wiped everything with Safestrap.
Now I can only boot into download mode. Attempting to boot normally or into recovery mode results in the "Firmware upgrade encountered an issue. Please use Software Repair Assistant & try again." screen.
Kies is a no-go since I can't access my serial number now.
So far, everything I've tried to flash with Odin (both 1.85 and 3.09) results in:
...
<ID:0/005> aboot.mbn
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
including the ME7 image which fixed a similar problem in this thread.
Is there any hope?
ANBHF said:
Stupidly, I took the update (to MI1) after getting my new S4. I later discovered this meant Safestrap was my only option for installing custom ROMS.
Even more stupidly, I decided I wanted to do a 'clean' install of my ROM, so I wiped everything with Safestrap.
Now I can only boot into download mode. Attempting to boot normally or into recovery mode results in the "Firmware upgrade encountered an issue. Please use Software Repair Assistant & try again." screen.
Kies is a no-go since I can't access my serial number now.
So far, everything I've tried to flash with Odin (both 1.85 and 3.09) results in:
...
<ID:0/005> aboot.mbn
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
including the ME7 image which fixed a similar problem in this thread.
Is there any hope?
Click to expand...
Click to collapse
Use the ml1 image. Once upgraded you cant go backwards in firmware.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
You didn't really screw yourself as much as you think, if you were on ME7 before upgrading to MI1 then it wouldn't have mattered since ME7 has a locked bootloader, thus Safestrap is the only option. If you had MDK however... then yeah you screwed yourself, but if you just bought it that's very unlikely
Yeah, box says it was ME7.
So I got the (rooted) MI1 ROM from this thread , in flashed it with Odin (using the PDA button in v1.85). It completed, and Odin isn't claiming there were any problems, but I still can't get it to boot normal or into recovery mode. If I try to do either, the upper left corner of the screen says, in red, "Could not do normal boot." and it goes back into downloading mode.
Guessing that's still not the right ROM or I installed it wrong?
UPDATE:
Problem solved. I followed the steps in this thread, using the ROM provided there, and the exact version of Odin listed.
Hi, please can you suggest what else I can try to fix this phone.
I have Samsung S3 GT-I9300
It was working fine but suddenly, I turned it on and It is stuck on the Samsung LOGO forever.
It doesn't go to recovery mode when pressing HOME+VOL UP+POWER.
But I could go to Download mode. however Odin fails to install CWM and TWRP
this is download mode:
ODIN MODE
PRODUCT NAME:GT-I9300
CUSTOM BINARY DOWNLOAD:YES (9counts)
CURRENT BINARY: Custum
SYSTEM STATUS:Custom
I tried to install official recovery but it fails too
Code:
<ID:0/022> Added!!
<ID:0/022> Odin v.3 engine (ID:22)..
<ID:0/022> File analysis..
<ID:0/022> SetupConnection..
<ID:0/022> Initialzation..
<ID:0/022> Get PIT for mapping..
<ID:0/022> Firmware update start..
<ID:0/022> SingleDownload.
<ID:0/022> recovery.img
<ID:0/022> NAND Write Start!!
<ID:0/022> FAIL!
<ID:0/022>
<ID:0/022> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
although it fails It says : Current binary: samsung Official .
ODIN MODE
PRODUCT NAME:GT-I9300
CUSTOM BINARY DOWNLOAD:YES (9counts)
CURRENT BINARY: Samsung Official
SYSTEM STATUS:Custom
but the problem remain the same, NO RECOVERY MODE, and still the same LOGO stuck screen.
Please Any suggestions... .??
Try the rescue firmware thread in general forum, using a pit file. Also, downgrading the bootloader might help flash to work.
boomboomer said:
Try the rescue firmware thread in general forum, using a pit file. Also, downgrading the bootloader might help flash to work.
Click to expand...
Click to collapse
Thanks for your reply .
Just before I start flashing, I want to confirm things as I am a newbie.
I have downloaded FIRMWARE FACTORY 4.1.2
GT-I9300XXEMG4_KOR_MULTI_FACTORY
from this link.
http://forum.xda-developers.com/showpost.php?p=30087735&postcount=6
Do I have to check Re-partition box too beside auto reboot and F. Reset time?
About downgrading, I don't really know which bootloader I have.
Depend on what version firmware you were on before 4.1 or 4.3. Follow the instructions in that thread.
Downgrade bootloader to BLFB, search for it.
boomboomer said:
Depend on what version firmware you were on before 4.1 or 4.3. Follow the instructions in that thread.
Downgrade bootloader to BLFB, search for it.
Click to expand...
Click to collapse
Odin fails to install again. with Re-partition selected :/
Can you please point me to this BLFB , there are bunch of threads but nothing is clear.
I appreciate your help a lot
I screwed it more trying to install this Bootloader_XXELLA_Odin.tar
now it show this message
"firmware upgrade encountered an issue. please select recovery mode in kies and try again"
i45.tinypic.com/27y2tmd.jpg
please any advices, I am still able to go download mode
1. Downgrade bootloader
2. Flash stock firmware
If the bootloader flashed correctly, then try step 2.
The bootloader you used is not ideal, I don't know if that still has the problem but it might work.
boomboomer said:
1. Downgrade bootloader
2. Flash stock firmware
If the bootloader flashed correctly, then try step 2.
The bootloader you used is not ideal, I don't know if that still has the problem but it might work.
Click to expand...
Click to collapse
because I don't know which or where to find or how to know the right bootloader to install I screwed it more.
can you please give me a link of the bootloader that I am supposed to flash?,
this is is my phone info it may help.
this is my phone: vgy.me/rCuQQD.jpg
this is what kies, show when I try to install firmware: vgy.me/nTicsC.jpg
(it's a real Samsung although it was made in china )
I don't have any links, don't use kies as it just breaks Odin.
boomboomer said:
I don't have any links, don't use kies as it just breaks Odin.
Click to expand...
Click to collapse
I just installed kies after I got this message "firmware upgrade encountered an issue. please select recovery mode in kies and try again"
but it didn't work.
I think there is no luck with this phone !!!! : (
Thanks for your help anyway.
[SOLVED]EDIT:
Here is how I solved the problem. I a xda thread I found a similar problem and someone claiming this:
-Downloaded stock firmware and extracted files
-removed .md5 off the end and extracted it again
-inside should be boot.img cache.img recovery.img system.img etc.
-used Unified Android Toolkit to create individual flashable files of each file
-flashed them in the order they came
-everything passed
Click to expand...
Click to collapse
So I tried it, and it worked till the last .tar with the system.img in it. Here I had to switch USB cables from the original Samsung one to my Usb cabel from the Amazon Fire Stick. And then it also worked. For the flashing I used Odin 3.10.6 and the firmware was the G925FXXU2COH2 one. I deactivated Auto-reboot in Odin and after flashing each file I manually restarted the phone to Download mode by holding Vol down + Home + Power.
/[SOLVED]Edit
Hey guys,
this is my current situation: Phone is stuck in cyan screen with "An error has occurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC software". I can't use Smart Switch because I was rooted and on "XtreStoLite Deo-Mod Edition 2.3" when the phone bricked. ODIN does recognize the phone. I used Odin3 v3.10.6.
What I did to brick it:
- Downloaded a firmware and tried to flash it to unroot the phone, following that guide
http://forum.xda-developers.com/galaxy-s6/general/how-to-unroot-unbrick-galaxy-s6-t3110608
Model SM-G925F
Model name GALAXY S6 Edge
Country Germany
Version Android 5.1.1
Changelist 5599585
Build date Wed, 12 Aug 2015 08:11:31 +0000
Product code DBT
PDA G925FXXU2COH2
CSC G925FDBT2COH3
Click to expand...
Click to collapse
Since I was on "XtreStoLite Deo-Mod Edition 2.3" the device had the XXU2COH2 BL and stuff (I guessed)
- ODIN failed directly after NAND Write Start!!
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
What I tried to fix the problem:
- Flashing TWRP form http://forum.xda-developers.com/gal...p-recovery-2-8-7-1-g925f-android-5-1-t3144866 --> Fails
-Flashing G925FXXU2COH2 stock firmware and G925FXXU2BOGB_G925FDBT2BOG8_DBT (from http://stockroms.net/file/GalaxyS6Edge/SM-G925F/Germany/5.1.1/G925FXXU2BOGB_G925FDBT2BOG8_DBT.zip)
- After finding this http://forum.xda-developers.com/galaxy-s6-edge/help/guide-s6-edge-unbrick-guide-t3187655 and some other threads I removed the hidden.img from both firmwares I already tried, repacked them and flashed with ODIN.
---> modified G925FXXU2BOGB_G925FDBT2BOG8_DBT fails after flashing modem
----> modified G925FXXU2COH2 fails like this:
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
Click to expand...
Click to collapse
Sooo.. according to the guide I mentionied I would need to flash pit and Stock firmware at once like this:
1) Get your device to download mode by using this combo "VolumeDown-Home-Power"
2) Open an UP TO DATE ODIN.
3) Find the corresponding .PIT file for your S6 EDGE.
4) Find the corresponding stock rom for your S6 EDGE.
5) Then put them into odin CORRECTLY. Rom to "AP", .pit to PIT
6) Make Sure these are checked: "Re-partition","NAND all erase"
7) Plug your device in and then press start.
Click to expand...
Click to collapse
But I am not sure if this is the right thing to do. Also I don't know which of the provided pits for the SM-G925F I am supposed to use? http://forum.xda-developers.com/gal...925-pit-files-multi-thread-download-t3171636/ Whats the difference between them? Aaaand I'm still not sure which firmware I should be flashing
I would really appriciate your help..
Small update:
Found this suggestion on reddit and tried it
If you've tried to flash firmware off of Sammobile, and had your heart stop when the flash fails, fear no longer.
To fix the soft brick:
Open the firmware file in winrar and extract the hidden.img. Rename it as hidden.img.tar.
Load the new file into the PDA tab, and flash.
When the phone boots, the displayed image will be touchwiz teal, there will be a little android and GALAXY spelt above it. Don't freak out.
Give it a minute and it should boot.
Click to expand...
Click to collapse
After flashing the hidden.img.tar I was stuck on the Samsung Logo (before the bootanimation) but I could boot into normal Downloading mode. Tried flashing the stock firmware without the hidden.img and got
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1005)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
Click to expand...
Click to collapse
And I'm back to the screen saying I should use Smart Switch..
Well I again flashed the hidden.img.tar, then I could get in TWRP. I did restore on old backup and did a factory reset. The phone booted! So I dicided to try the unroot one more time. I was on kind a funny Baseband-Version so I decided to flash COH2 Bootloader and Modem, but Odin right after starting the NAND write and I was stuck on the Error massage from the beginning..
Flashed hidden.img.tar and the phone booted normaly.
What is going on? What do I need to flash or do to get back to stock?
In the device information I now have:
Modell: SM-G925F
Android-Version: 5.1.1
Basebandversion: G925FXXU2BOGE
Kernel-version: 3,10,61-Alex-V_1.2
Buildnumber: XtreStoLite Deo Mod v.2.3 - XXU2COH2
It is really kind of mixed up and I have know idea why I can't just flash with ODIN.
Worked for me but with very minor tweak
You guys are awesome! Thanks to you, I got myself out of a pickle.
I had softbricked my phone and I was stuck with a NAND Write error in ODIN with my G920F (Samsung Galaxy S6). Here's what I did:
Removed ".md5" at the end of "G920FXXU2BOFL_G920FOJV2BOEE_G920FXXU2BOFJ_HOME.tar.md5" (so file ends with ".tar").
Used 7zip to unpack.
Using Unified Android Toolkit, repacked each resulting ".img" file into separate ".tar" files (within Unified Android Toolkit, select 99 then 8, then 1 then 3 (auto-detect images). Resulting ".tar" files will be stored in the OUTPUT folder.
Using ODIN 3.10.7, flashed each ".tar" file, one by one, in the order that they were shown in 7zip. It's a very good idea to uncheck "Auto Reboot". After each flashing, vol down+home+button, and vol up again. Repeat until the last file. File flashing order was as follows:
- boot
- recovery
- system
- cache
- hidden
In the end, I rebooted the phone normally. Took about 6 or 7 minutes. An unusual green android screen was displayed, followed by another saying "erasing"... eventually, the phone rebooted as if it had been factory reset. Now going through the tedious process of reinstalling all of my apps.
Stuk in bootloop
spencersj said:
You guys are awesome! Thanks to you, I got myself out of a pickle.
I had softbricked my phone and I was stuck with a NAND Write error in ODIN with my G920F (Samsung Galaxy S6). Here's what I did:
Removed ".md5" at the end of "G920FXXU2BOFL_G920FOJV2BOEE_G920FXXU2BOFJ_HOME.tar.md5" (so file ends with ".tar").
Used 7zip to unpack.
Using Unified Android Toolkit, repacked each resulting ".img" file into separate ".tar" files (within Unified Android Toolkit, select 99 then 8, then 1 then 3 (auto-detect images). Resulting ".tar" files will be stored in the OUTPUT folder.
Using ODIN 3.10.7, flashed each ".tar" file, one by one, in the order that they were shown in 7zip. It's a very good idea to uncheck "Auto Reboot". After each flashing, vol down+home+button, and vol up again. Repeat until the last file. File flashing order was as follows:
- boot
- recovery
- system
- cache
- hidden
In the end, I rebooted the phone normally. Took about 6 or 7 minutes. An unusual green android screen was displayed, followed by another saying "erasing"... eventually, the phone rebooted as if it had been factory reset. Now going through the tedious process of reinstalling all of my apps.
Click to expand...
Click to collapse
After flashing boot.tar my phone is stuck in bootloop and nt coming out despite hard reset also and i m also unable to flash new fw via odin.
plz help.
it states SOLVED.....???