Related
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, 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
Hi, I bought a used SGS3. I want to root it as I have allways done with my Android phones.
After a lot of hours I spent trying to do it I find out that it could be related to: "CUSTOM BINARY DOWNLOAD: NO" message.
The facts:
- As I know the only way to root the device is using "custom binary download" mode.
- When I try to do it I read at download mode:
ODIN MODE
PRODUCT NAME: GT-I9300
CUSTOM BINARY DOWNLOAD: NO
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
- Odin allways fails at this point and I suppose it is related to above message.
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Added!!
- As I read to increase the binary download counter I need to be root, but I am not.
Conclusion: I will never be root, change de ROM or use privileged apps like backup apps and a device like that is useless for me.
I spent a lot of time trying to solve this and I am desperate.
I will thank any hint on this. Do I have any chance to fix this, root de device and chage ROM to cyanogen or other?
Thanks,
txemi
Do you want to root your s3 or flash custom ROMs?
Device: Samsung Galaxy S3
ROM: CyanogenMod 11 (Temasek Unofficial V24)
Kernel: Boeffla-Kernel-CM11-2.1-Beta7-
Both. I think I cannot flash if I am not root. I would like to be able to became root first and later flash custom ROMs.
txemitron said:
Both. I think I cannot flash if I am not root. I would like to be able to became root first and later flash custom ROMs.
Click to expand...
Click to collapse
Okay.
First go in download mode and flash the CWM (Clockworkmod Recorvery) for your s3 via Odin in Bootloader.
Device: Samsung Galaxy S3
ROM: CyanogenMod 11 (Temasek Unofficial V24)
Kernel: Boeffla-Kernel-CM11-2.1-Beta7-
Odin usually fails with:
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
txemitron said:
Odin usually fails with:
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
did you flash cf autoroot ? does odin see the phone? while flashing you must be in download mode. it shouldnt take more than a few seconds
txemitron said:
Odin usually fails with:
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Select file from PDA button and uncheck re-partition
GT-I9300 cihazımdan Tapatalk kullanılarak gönderildi
After some tests with linux and analyzing dmesg and lsubs output I realised that the real problem was not a software issue, hardware usb port instead.
Being a used phone I have just bought USB cable cannot fit properly in usb port and is nearly impossible to have an usb stable connection. It is not a problem of CUSTOM BINARY DOWNLOAD, it is a problem with any thing requiring usb connection. It seems previous owner did not mind because he used the phone as is and did not use usb for data transfers.
I tryed some cables I have at home but they did not work, now I do not know what to do. I am considering next options, I do not know if there are any more.
1) Going to Samsung tech support. I am not sure if it is expensive or it does take a long time to get phone fixed.
2) Try to give the phone back to seller.
3) Spend a lot of time and going crazy testing usb cables in case some work.
4) Look for some buyer that does not mind about usb and buy another phone for me.
Thanks again for your responses,
txemi