Related
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!
Hi, im a noob user about roms and root, and 1 week ago i had a problem flashing roms, i flashed shostock3 with rom manager (i didnt know that i could be dangerous in my phone) after flashing shostock i decided to flash a kernel, but when i tried to reboot recovery mode in rom manager the phone turned off, and when i try to turn it on stops in "samsung galaxy s2" logo, the good news is i can acess download mode.
Does anyone know how to solve this problem?
Thanks.
gecafe said:
Hi, im a noob user about roms and root, and 1 week ago i had a problem flashing roms, i flashed shostock3 with rom manager (i didnt know that i could be dangerous in my phone) after flashing shostock i decided to flash a kernel, but when i tried to reboot recovery mode in rom manager the phone turned off, and when i try to turn it on stops in "samsung galaxy s2" logo, the good news is i can acess download mode.
Does anyone know how to solve this problem?
Thanks.
Click to expand...
Click to collapse
In download mode you can install the last stock 4.1.2 Jelly Bean UCMD8 firmware using the program Odin follow this complete tutorial :
http://www.android.gs/flash-android...d8-update-for-the-att-samsung-galaxy-s2-i777/
After installing the stock ROM root your phone in this way:
1-Download Framaroot apk file into your device.
2-Go to Menu—>Download, locate the Frameroot apk file.
3-Press on Frameroot apk file in the Download folder. A pop-out windows ask for confirmation, press confirm/yes to proceed with Framaroot installation.
4-Once Framaroot successfully installed on your device, you shall find Framaroot icon in the Menu.
5-Press on Framaroot icon in Menu to launch the app.
6-In Framaroot user interface, choose Aragorn exploits within the list of exploits.
7-You shall now receive a exploit results: “Success… Superuser and su binary installed. You have to reboot your device”
Sent from my SGH-I777 using xda app-developers app
Flashing with odin this happened
<ID:0/011> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I777UCMD8_I777ATTMD8_I777UCMD8_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/011> Odin v.3 engine (ID:11)..
<ID:0/011> File analysis..
<ID:0/011> SetupConnection..
<ID:0/011> Initialzation..
<ID:0/011> Get PIT for mapping..
<ID:0/011> Firmware update start..
<ID:0/011> boot.bin
<ID:0/011> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
gecafe said:
Flashing with odin this happened
<ID:0/011> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I777UCMD8_I777ATTMD8_I777UCMD8_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/011> Odin v.3 engine (ID:11)..
<ID:0/011> File analysis..
<ID:0/011> SetupConnection..
<ID:0/011> Initialzation..
<ID:0/011> Get PIT for mapping..
<ID:0/011> Firmware update start..
<ID:0/011> boot.bin
<ID:0/011> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Try again use Odin3 v.1.85
Sent from my SGH-I777 using xda app-developers app
pepe100 said:
Try again use Odin3 v.1.85
Sent from my SGH-I777 using xda app-developers app
Click to expand...
Click to collapse
That's what i used, but im gonna install it again
Still failing, downloaded another odin3 1.85, run it as administrator but didnt work.
what else should i try?
gecafe said:
Still failing, downloaded another odin3 1.85, run it as administrator but didnt work.
what else should i try?
Click to expand...
Click to collapse
I'm not sure what rom manager does to the memory, but I think the phone can be recovered.
Please delete rom manager from your I777 and never use it on this phone, as it is not compatible.
Try the following sequence to see if this will clear the problem:
Odin3 v1.85 is recommended.
Steps 1 & 2 in sequence without rebooting if possible.
1) Download the Tar version of Siyah 2.6.14 Kernel. Flash it in PDA. Without ticking Re-Partitioning.
2) Flash the Tar.md5 of the full stock Gingerbread distribution from the Download Repository, I777UCKH7 including the bootloaders and everything, in the PDA slot.
You may need to enter recovery and perform a wipe data/factory reset, either before, during or after these two steps.
3) If that is successful you are done. If it is not, then:
4) Download the SBL Bootloader from the Download Repository. Flash it as PDA in ODIN, without ticking Re-Partitioning. (Please observe normal bootloader flashing caution.)
5) Flash the Kernel, as in step 1.
6) Flash the full stock Gingerbread distribution, as in step 2.
creepyncrawly said:
I'm not sure what rom manager does to the memory, but I think the phone can be recovered.
Please delete rom manager from your I777 and never use it on this phone, as it is not compatible.
Try the following sequence to see if this will clear the problem:
Odin3 v1.85 is recommended.
Steps 1 & 2 in sequence without rebooting if possible.
1) Download the Tar version of Siyah 2.6.14 Kernel. Flash it in PDA. Without ticking Re-Partitioning.
2) Flash the Tar.md5 of the full stock Gingerbread distribution from the Download Repository, I777UCKH7 including the bootloaders and everything, in the PDA slot.
You may need to enter recovery and perform a wipe data/factory reset, either before, during or after these two steps.
3) If that is successful you are done. If it is not, then:
4) Download the SBL Bootloader from the Download Repository. Flash it as PDA in ODIN, without ticking Re-Partitioning. (Please observe normal bootloader flashing caution.)
5) Flash the Kernel, as in step 1.
6) Flash the full stock Gingerbread distribution, as in step 2.
Click to expand...
Click to collapse
Thanks mate im gonna try it, but how do i get recovery mode, i tried to do it but it didn't work, i tried this:
Press volume+ and volume- at the same time 5 seconds and later press power button, i always get to the download mode.
OK guys, i have not solved my problem but i could investigate something thanks to my friend's i777 phone, and this is:
I noticed he had Rom manager, and he said he uses it lot of times and his phone have not gotten a problem, so i tried the rom magager recovery mode (what i tried and f***** my phone), the phone worked great and did not have any problem, after trying lot of things i decided to use the NQ antivirus, and it detected the rom manager as a virus and dangerous app i had to uninstall, actually just tried it in a i777 phone, tomorow i'll try on a different phone to see if this is normal.
Im gonna keep investigating about what rom manager does after solving my problem.
creepyncrawly said:
I'm not sure what rom manager does to the memory, but I think the phone can be recovered.
Please delete rom manager from your I777 and never use it on this phone, as it is not compatible.
Try the following sequence to see if this will clear the problem:
Odin3 v1.85 is recommended.
Steps 1 & 2 in sequence without rebooting if possible.
1) Download the Tar version of Siyah 2.6.14 Kernel. Flash it in PDA. Without ticking Re-Partitioning.
2) Flash the Tar.md5 of the full stock Gingerbread distribution from the Download Repository, I777UCKH7 including the bootloaders and everything, in the PDA slot.
You may need to enter recovery and perform a wipe data/factory reset, either before, during or after these two steps.
3) If that is successful you are done. If it is not, then:
4) Download the SBL Bootloader from the Download Repository. Flash it as PDA in ODIN, without ticking Re-Partitioning. (Please observe normal bootloader flashing caution.)
5) Flash the Kernel, as in step 1.
6) Flash the full stock Gingerbread distribution, as in step 2.
Click to expand...
Click to collapse
No matter what i do, Odin is still failing, so i havent been able to do anything, well the stock GB from the download repository got stuck in setupconnection, i dont know what to do, i don want to pay for fixing my phone.
Practically every post in this thread from people trying to help you are the answers you need. Your instance on continuing to use Rom Manager on this phone, even after you've been warned about it, AND there's been a sticky regarding the dangers for nearly 2 years, are simply incredible!
If you can't get Odin to work (something as simple as trying the USB port in the back of the computer may work), your only option is to pay someone to fix it for you.
And by the way, entering recovery for the i777 is all three buttons at the same time, then releasing them once the boot logo appears.
gecafe said:
No matter what i do, Odin is still failing, so i havent been able to do anything, well the stock GB from the download repository got stuck in setupconnection, i dont know what to do, i don want to pay for fixing my phone.
Click to expand...
Click to collapse
You need to try a different known good usb cable, or different ports on the computer, or even a different computer to see if you can get Odin to complete. If you are absolutely sure that the reason Odin does not complete is not due to the above, then you may have a firmware problem that is beyond my ability to help you, or you may have some kind of hardware issue.
If it were my phone, I would probably send it to Mobile Tech Videos, since they are reliable and very good, but if you are not willing to spend money, then I don't have anything else to suggest.
Edit: It occurred to me that you may not have followed the full sequence. Did you get to step 4, and if not you need to try to flash the sbl.tar by itself in the pda slot and then go back to step 1.
I have been there...
This has happened to me a couple of times. You can either do a complete flash of a stock rom and go from there, OR, you can flash a recovery kernel. There is an old Sylah image floating around. You can flash this with the Odin tool. I believe Odin 3.07 worked best for me.
SteveMurphy said:
Practically every post in this thread from people trying to help you are the answers you need. Your instance on continuing to use Rom Manager on this phone, even after you've been warned about it, AND there's been a sticky regarding the dangers for nearly 2 years, are simply incredible!
If you can't get Odin to work (something as simple as trying the USB port in the back of the computer may work), your only option is to pay someone to fix it for you.
And by the way, entering recovery for the i777 is all three buttons at the same time, then releasing them once the boot logo appears.
Click to expand...
Click to collapse
First of all is im a newbie in XDA i saw the warning when i joined, it seems u got mad, if u cant be patient with a noob, dude just let others help me.
Thanks im gonna try another pc and cable.
Hi XDA.
First off: I HAVE A 9100G!
Yesterday I tried to root and flash PACman.
Rooting went allright, even though I didnt backup/grant superpermissions.
Then I tried to flash Pacman 9100, the non-G version. At that moment I didn't know I had a 9100G.
I did get the error code 7, which meant it wasn't for my phone, but I googled a workaround to fix this. This was mistake #1.
After this, my phone pretty much broke.
I tried to flash other ROM's but every rom would fail at this:
<ID:0/003> hidden.img
<ID:0/003> MLO
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
.
So at that point I didnt have any ROM installed, and could install no other ROM.
After trying to install a ROM I had to flash a new kernel to be able to get into recovery.
After a while I couldnt install kernels anymore. In Odin the flash would 'Pass', but after the reboot it would freeze halfway in the kernel-install.
After freezing, it would go in a loop.
So currently, I have a phone which only says Galaxy SII with the yellowtriangle under it.
I can, however, still get into download mode, so I don't think it's done yet.
If someone, could help me get my phone working again, U'll be my hero of the month..
I'll be really active to answer all questions and try all possibilities.
- Sam
Aristona said:
Hi XDA.
First off: I HAVE A 9100G!
Yesterday I tried to root and flash PACman.
Rooting went allright, even though I didnt backup/grant superpermissions.
Then I tried to flash Pacman 9100, the non-G version. At that moment I didn't know I had a 9100G.
I did get the error code 7, which meant it wasn't for my phone, but I googled a workaround to fix this. This was mistake #1.
After this, my phone pretty much broke.
I tried to flash other ROM's but every rom would fail at this:
<ID:0/003> hidden.img
<ID:0/003> MLO
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
.
So at that point I didnt have any ROM installed, and could install no other ROM.
After trying to install a ROM I had to flash a new kernel to be able to get into recovery.
After a while I couldnt install kernels anymore. In Odin the flash would 'Pass', but after the reboot it would freeze halfway in the kernel-install.
After freezing, it would go in a loop.
So currently, I have a phone which only says Galaxy SII with the yellowtriangle under it.
I can, however, still get into download mode, so I don't think it's done yet.
If someone, could help me get my phone working again, U'll be my hero of the month..
I'll be really active to answer all questions and try all possibilities.
- Sam
Click to expand...
Click to collapse
can you acces recovery mode right now?if odin fails try to use to flash another ROM with Recovery.
LYandroid said:
can you acces recovery mode right now?if odin fails try to use to flash another ROM with Recovery.
Click to expand...
Click to collapse
I can't enter recovery, but neither can I flash via Odin. Odin keeps failing after factoryfs.
Try to flash 2.3.6 3 files via odin maybe it will works
Wysłane z mojego GT-I9100 przy użyciu Tapatalka
I will not go into detail but suffice to say I was running my Samsung Galaxy S3 GT-I9300 on a stock Samsung Android 4.1.2 ROM and it was rooted and had a custom CWM Recovery.
I then flashed to CM 10.0.0 but encountered problems and tried to revert to my original ROM. This resulted in my phone displaying the initial black background boot screen with the words "Samsung Galaxy SIII GT-I9300". It stuck there and I could not switch it off nor could I get into Recovery Mode.
I was able to get into Download mode and connect to Odin to reflash my original ROM but Odin continually got stuck in the process at "Setup Communication" and on the odd occasion it got past that it then stuck on "Get Pit Mapping".
After much research of this and other forums found one lone article about Samsung introducing new ROMS from July 2013 onwards which had efs2 and that once upgrading to an efs2 ROM you could not go back to a previous efs1 ROM which I think I tried to do.
I eventually decided therefore to bite the bullet and I downloaded GT-I9300.pit and flashed it using Odin with Re-Partition selected. I was then able to flash Samsungs latest Android 4.3 (I9300XXUGMK6) ROM for the I9300.
The result is that whilst the phone is again fully functional I am unable to install a custom recovery nor can I root my phone.
I thought that if I used the GT-I9300.pit file it would re-partition the phone as a I9300 should be partitioned but it seems I was wrong.
I am happy with my phone now that I have recovered it but would like to be able to backup my rom but I need root to do that. Does anyone know what I have done with my phone and are you able to advise as to how I might now root it again?
Thanks
matrixmainframe said:
I am happy with my phone now that I have recovered it but would like to be able to backup my rom but I need root to do that. Does anyone know what I have done with my phone and are you able to advise as to how I might now root it again?
Thanks
Click to expand...
Click to collapse
After flashing the stock rom when coming from a custom rom is always best to do a factory reset to clear the phone.
You can root with CF auto root from my signature it works perfectly well on stock 4.3 MK6, then use TWRP or Philz recovery both are in the Dev section
ag4751 said:
After flashing the stock rom when coming from a custom rom is always best to do a factory reset to clear the phone.
You can root with CF auto root from my signature it works perfectly well on stock 4.3 MK6, then use TWRP or Philz recovery both are in the Dev section
Click to expand...
Click to collapse
When I try to flash a recovery or try to root I get the following.
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-m0-m0xx-gti9300.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
As you can see from the above it looks as though the process falters at "<ID:0/003> Get PIT for mapping.." which would appear to have something to do with the fact that I had to re-partition using GT-I9300.pit and that is what prompted my question in the first place.
It appears to me that the GT-I9300.pit file has altered my partitions in a non I9300 way despite having I9300 in the filename and that is why I posted the question in the hope someone would know what I had done and hopefully know a way I could either reverse what I had done or suggest a way to root despite my apparently new partition format?
matrixmainframe said:
When I try to flash a recovery or try to root I get the following.
It appears to me that the GT-I9300.pit file has altered my partitions in a non I9300 way despite having I9300 in the filename and that is why I posted the question in the hope someone would know what I had done and hopefully know a way I could either reverse what I had done or suggest a way to root despite my apparently new partition format?
Click to expand...
Click to collapse
Have a look here then you my be able to recover your device, it is Korean based so will default to KOR not BTU but it could repair the PIT problem if that is what you have.
ag4751 said:
Have a look here then you my be able to recover your device, it is Korean based so will default to KOR not BTU but it could repair the PIT problem if that is what you have.
Click to expand...
Click to collapse
Please read my initial post(#1).
I have already recovered my phone and it is working correctly on Samsung Official Stock 4.3 ROM (Android 4.3 - I9300XXUGMK6) EXCEPT that I cannot flash a custom Recovery nor can I root the phone. I have several apps that only operate on a rooted phone so just rooting it without a custom recovery would suffice.
If someone tells me that it is no longer possible to root my phone then I will be disappointed but I can live with it. I just thought someone might know the answer.
That problem in Odin might be related to incorrect drivers for your phone.
Remove any kies or Samsung softwares and reboot pc. Reinstall kies and connect phone 2 pc for drivers install. Then try a different usb port to flash smth on the phone.
Trimis de pe al meu GT-I9300 folosind Tapatalk
matrixmainframe said:
Please read my initial post(#1).
I have already recovered my phone and it is working correctly on Samsung Official Stock 4.3 ROM (Android 4.3 - I9300XXUGMK6) EXCEPT that I cannot flash a custom Recovery nor can I root the phone. I have several apps that only operate on a rooted phone so just rooting it without a custom recovery would suffice.
If someone tells me that it is no longer possible to root my phone then I will be disappointed but I can live with it. I just thought someone might know the answer.
Click to expand...
Click to collapse
I think i had the same problem with rooting and done reinstalling drivers and change the port so it is now rooted.
Also try unticking autoreboot then after the instalation is done disconnect the phone and remove/reinsert battery and boot to recovery so the auto root files start to install...
Of course everything you do is at your own risk...
BR
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.