Hello. I tried to install custom recoveries / root the phone, bricked it, and now I can't even perform this http://www.android.gs/how-to-unbrick-samsung-galaxy-s5/ way to unbrick the phone with the stock firmware image. It fails at the same point every time with system.img.ext4 (the largest file) after success with the other files. Attempted on a Windows 7 VM with Odin 3.09 and Odin 3.07 and Samsung USB Drivers. Is there any way at this point to save the device? I might add that in Odin, the device COM:3 or whatever shows up as blue, not yellow.
Also, it seems this worked before as I followed the instructions, but I attempted to root again. Stupid me.
UPDATE: I was using this on VMWare Fusion on Mac OS X, something I'm reading in various forums that this is something to NOT do. Will try on Windows physical machine.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G900TUVU1BNH5_G900TTMB1BNH5_G900TUVU1BNH5_HOME.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> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
jdmanley87 said:
Hello. I tried to install custom recoveries / root the phone, bricked it, and now I can't even perform this http://www.android.gs/how-to-unbrick-samsung-galaxy-s5/ way to unbrick the phone with the stock firmware image. It fails at the same point every time with system.img.ext4 (the largest file) after success with the other files. Attempted on a Windows 7 VM with Odin 3.09 and Odin 3.07 and Samsung USB Drivers. Is there any way at this point to save the device? I might add that in Odin, the device COM:3 or whatever shows up as blue, not yellow.
Also, it seems this worked before as I followed the instructions, but I attempted to root again. Stupid me.
UPDATE: I was using this on VMWare Fusion on Mac OS X, something I'm reading in various forums that this is something to NOT do. Will try on Windows physical machine.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G900TUVU1BNH5_G900TTMB1BNH5_G900TUVU1BNH5_HOME.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> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
I would say to try it on a windows based machine, try different cables on that machine, see if there is a possibility of verifying the MD5 checksum of the file you are attempting to flash, verify that the drivers are properly installed, All the usual stuff really.
If you can enter download mode and Odin is actually seeing it then chances are it should work. Working on a Mac shouldn't make any difference but it could, especially seeing as you're using win 7 in a virtual environment.
Also are you attempting to flash the right file for your phone?
Well thankfully this T-mobile store accepted the return after I told them what happened for only the restocking fee, and gave me a new one. I'm not going to attempt to root this one. Maybe later on, I'll get a new phone that I like, as I'm having a hard time finding a quality phone that unlocks without crazy issues like this (like the Nexus 5, only without its serious screen cracking issues).
Yeah, my work laptop is a Mac with VMWare Fusion running Windows 7. Office programs crash almost every time I use them, and the experience overall feels very flaky compared to Windows XP or 7 on a physical machine. Turns out I have a nettop PC with a product key to install Windows 7 natively on that.
I'm also surprised to see there aren't any guides for such a popular device (the S5) that go from A to CyanogenMod in a straightforward manner. Like every other device that CM has a port has a guide like that.
You would have had better luck just rooting directly in OSX. It failed because you tried to do it on a virtual machine. The USB drivers were not created to run in an emulated environment and quite frankly i am surprised Odin detected the phone at all. You could have un-bricked it on a Windows or OSX system, not on a VM. You can't take any shortcuts when you are rooting. Rooting was easier on my S5 than it was on my Nexus devices!
Honestly I tried at first to get the S4, because that is supported by CM's own installer, as is the Nexus 5. Store was sold out, and the S5 seemed very similar. I think I remember now, I used the CM installer on my Nexus 5 from an actual Windows laptop (no VM b.s.). So it really is the bad USB drivers in VMs causing these issues? I guess that makes sense. Is VirtualBox necessarily as bad as VMWare in this sense?
jdmanley87 said:
Honestly I tried at first to get the S4, because that is supported by CM's own installer, as is the Nexus 5. Store was sold out, and the S5 seemed very similar. I think I remember now, I used the CM installer on my Nexus 5 from an actual Windows laptop (no VM b.s.). So it really is the bad USB drivers in VMs causing these issues? I guess that makes sense. Is VirtualBox necessarily as bad as VMWare in this sense?
Click to expand...
Click to collapse
Just stick with either OSX or Windows. The top issues that interfere with unlocking/rooting devices are the USB drivers and the USB cable. So make sure that you are using the S5 cable for starters. Then make sure you have a clean install of the Samsung drivers, both of them. (ADB and MTP) In other words, before you attempt to root make sure the S5 is detected in the bootloader and the MTP transfer mode. When you use a VM you are communicating with the computer through the adb program, emulation driver, and then the actual hardware driver essentially going through 3 layers of software which is just asking for trouble.
If you are unsure look up Skipsoft toolkit for the S5 and it will setup the drivers and can even root it for you. I prefer to do it the old school way but i have used it and can verify it works quite nicely. I have been doing this since the OG Droid and the S5 was easy to root.
Edit: here is the link: http://forum.xda-developers.com/showthread.php?t=2719834
This is for Windows but I have seen MAC ones also.
Sorry mate, but the s5 is an absolute walk in the park to root, install a custom recovery and add a ROM. Root is obtain by downgrading (if needed) then installing an apk (towel root) then install your recovery, then install a custom ROM, install the boatloader and modem if needed, usually not.
Related
Hey,
A while ago I've installed CM10.1 on my S4, but I was missing a lot of samsung features. So I've installed 4.2.2 again, set the binary back to the official one so I was able to update my phone again. Now that 4.3 has came out I tried to install it but then my phone bricked. The first attempt was not with odin but official via OTA.
Now i've got a soft bricked S4, tried to install the firmware several times via Odin but Odin keeps failing. If I first try to install it it wil fail at the aboot.mbn point. When I root it with Autoroot CF and then try to install the firmware it fails at system.img.ext4 as I show down here. Has anyone an idea how to fix this? Tried many options already like installing a new recovery like CWM Recovery and TWRP. (Couldn't find a stock recovery, maybe thats the solution.)
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUEMJ7_I9505PHNEMJ8_I9505XXUEMJ7_HOME.tar.md 5 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> Firmware update start..
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> tz.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Currently have CM10.2 installed so I can use my phone, this works but not great. Wifi, Calling, Camera, Headphone and much other options won't work. I really want to install official Samsung 4.3 firmware and be able to update again with OTA.
chendoyen said:
Hey,
A while ago I've installed CM10.1 on my S4, but I was missing a lot of samsung features. So I've installed 4.2.2 again, set the binary back to the official one so I was able to update my phone again. Now that 4.3 has came out I tried to install it but then my phone bricked. The first attempt was not with odin but official via OTA.
Now i've got a soft bricked S4, tried to install the firmware several times via Odin but Odin keeps failing. If I first try to install it it wil fail at the aboot.mbn point. When I root it with Autoroot CF and then try to install the firmware it fails at system.img.ext4 as I show down here. Has anyone an idea how to fix this? Tried many options already like installing a new recovery like CWM Recovery and TWRP. (Couldn't find a stock recovery, maybe thats the solution.)
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUEMJ7_I9505PHNEMJ8_I9505XXUEMJ7_HOME.tar.md 5 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> Firmware update start..
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> tz.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Currently have CM10.2 installed so I can use my phone, this works but not great. Wifi, Calling, Camera, Headphone and much other options won't work. I really want to install official Samsung 4.3 firmware and be able to update again with OTA.
Click to expand...
Click to collapse
I thought the only way to fix a bricked phone is to have it repaired or something. But I dont understand why you would switch back to samsung ui, but thats not my business. I believe is risky to go back to the phones normal UI after installing a rom because of the update problem. Basically I would never go back to the normal phones UI even if I wanted to after installing a rom, because I feel like there will be a problem. I dont really know a solution but maybe you can give it into someone to repair it, but I believe it costs A LOT. Sorry I don't really have a good solution for you. These are the risks with installing roms and switching back.
Are you using the official cable that came with the phone
Sent from my GT-I9505 using xda app-developers app
imlgl said:
Are you using the official cable that came with the phone
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
Yes, also tried another cable.
Also tried: Another Odin version, another PC and different USB ports.
Anyone?
Nobody an idea?
You could try the following things:
Re-install samsung drivers
Make sure Kies is not running in the background
Try changing ports
Try different USB cable
bAk3ry said:
You could try the following things:
Re-install samsung drivers
Make sure Kies is not running in the background
Try changing ports
Try different USB cable
Click to expand...
Click to collapse
Tried again another PC and it worked a bit, I now have stock samsung firmware 4.3 installed but still no wifi and no sound. Is there a solution for that? Already tried to install CWM and TWRP but still doesn't work. When I try to play music it says audio file not supported (.MP3 file, before problems always worked) S Voice keeps crashing... And when I try to turn Wifi on I get a security message that says:
The device detected an application attempts to perform action that are not allowed. These actions are blocked.
You need to flash one of the WiFi 'fixes' from this thread, read it to work out which file you need to flash.
MistahBungle said:
You need to flash one of the WiFi 'fixes' from this thread, read it to work out which file you need to flash.
Click to expand...
Click to collapse
Tried that but it still won't work.
Bought a GS5 (Verizon) SM-G900V for my friend in Brazil and tried to root it and now the phone is stuck in Odin Mode. I cannot get into recovery mode, and I have tried Odin 3.09 on two different computers. I always get fail trying to write the stock image that was on it (NI2) and it it stuck at system.im.ext4.
I have tried pulling the battery countless times to get into recovery mode and to flash it via Odin. Nothing works. The device is not recognized by Keis on either computer either. It asks for the VZW Software Repair Assistant, but I cannot locate a download for that.
He leaves in a few hours, so I need a fix ASAP. Any help is GREATLY appreciated!
Thanks!
jmorehouse said:
Bought a GS5 (Verizon) SM-G900V for my friend in Brazil and tried to root it and now the phone is stuck in Odin Mode. I cannot get into recovery mode, and I have tried Odin 3.09 on two different computers. I always get fail trying to write the stock image that was on it (NI2) and it it stuck at system.im.ext4.
I have tried pulling the battery countless times to get into recovery mode and to flash it via Odin. Nothing works. The device is not recognized by Keis on either computer either. It asks for the VZW Software Repair Assistant, but I cannot locate a download for that.
He leaves in a few hours, so I need a fix ASAP. Any help is GREATLY appreciated!
Thanks!
Click to expand...
Click to collapse
It sounds like you need to use Odin to flash a complete stock retail ROM and start over with the rooting process. It's kind of confusing trying to figure out the problem you're having though. What recovery are you trying to boot to? The stock recovery or SafeStrap? Like I said though, I would start completely over with these steps.
1. Flash a full retail tar with Odin https://www.androidfilehost.com/?fid=23622183712474060
2. Flash NCG firmware with Odin so you can root http://www.androidfilehost.com/?fid=23610159112652200
3. Root using Towelroot https://www.androidfilehost.com/?fid=23681161096070831
4. After root flash NI2 firmware back with Odin https://www.androidfilehost.com/?fid=23622183712474000
5. Install SafeStrap recovery http://forum.xda-developers.com/devdb/project/?id=4718#downloads
6. Go to the Play Store and download SuperSU and install it
If you follow these steps and it works you'll be good to go.
ludeawakening said:
It sounds like you need to use Odin to flash a complete stock retail ROM and start over with the rooting process. It's kind of confusing trying to figure out the problem you're having though. What recovery are you trying to boot to? The stock recovery or SafeStrap? Like I said though, I would start completely over with these steps.
1. Flash a full retail tar with Odin https://www.androidfilehost.com/?fid=23622183712474060
2. Flash NCG firmware so you can root http://www.androidfilehost.com/?fid=23610159112652200
3. Root using Towelroot https://www.androidfilehost.com/?fid=23681161096070831
4. After root flash NI2 firmware back with Odin https://www.androidfilehost.com/?fid=23622183712474000
5. Install SafeStrap recovery http://forum.xda-developers.com/devdb/project/?id=4718#downloads
6. Go to the Play Store and download SuperSU and install it
If you follow these steps and it works you'll be good to go.
Click to expand...
Click to collapse
Thanks, yes, very confusing. I am tried stock recovery. I will try and do full retail back on now again, but I have been reading there is issues with Odin and Verizon 4.4.4 updates. Heimdall is having issues communicating on my mac too. Is that something you are familiar with (the communications issues that is)?
jmorehouse said:
Thanks, yes, very confusing. I am tried stock recovery. I will try and do full retail back on now again, but I have been reading there is issues with Odin and Verizon 4.4.4 updates. Heimdall is having issues communicating on my mac too. Is that something you are familiar with (the communications issues that is)?
Click to expand...
Click to collapse
Tried flashing your stock rom and below is the output from Odin...
Code:
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_VZW_G900VVRU1ANI2_G900VVZW1ANI2_2525521_REV00_user_low_ship_MULTI_CERT.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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
jmorehouse said:
Thanks, yes, very confusing. I am tried stock recovery. I will try and do full retail back on now again, but I have been reading there is issues with Odin and Verizon 4.4.4 updates. Heimdall is having issues communicating on my mac too. Is that something you are familiar with (the communications issues that is)?
Click to expand...
Click to collapse
You will not be able to use the stock recovery for flashing anything. You'll have to use SafeStrap for flashing purposes. But if you're just trying to get a rooted stock ROM working, you won't need to use the recovery at all. It's mainly for flashing custom ROM's on this phone. Odin is our best friend for solving major issues on this device since the bootloader is locked. I hope the steps I listed helps.
And yes, I also have communication problems on a Mac with this phone. My PC will boot to OS X 10.7.2 and Windows 7, but when booted to my Mac drive, it can not see my phone. My friends MacBook Pro doesn't see the phone either. I haven't looked into a work-around yet, I just boot from my Windows drive, or use my Windows laptop if I need to be connected to the computer for any reason.
---------- Post added at 01:39 PM ---------- Previous post was at 01:33 PM ----------
jmorehouse said:
Tried flashing your stock rom and below is the output from Odin...
Code:
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_VZW_G900VVRU1ANI2_G900VVZW1ANI2_2525521_REV00_user_low_ship_MULTI_CERT.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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Try to reinstall the Samsung drivers and try again. Make sure the "Re-partition" box is checked in Odin. Use these drivers http://developer.samsung.com/technical-doc/view.do?v=T000000117#none
ludeawakening said:
You will not be able to use the stock recovery for flashing anything. You'll have to use SafeStrap for flashing purposes. But if you're just trying to get a rooted stock ROM working, you won't need to use the recovery at all. It's mainly for flashing custom ROM's on this phone. Odin is our best friend for solving major issues on this device since the bootloader is locked. I hope the steps I listed helps.
And yes, I also have communication problems on a Mac with this phone. My PC will boot to OS X 10.7.2 and Windows 7, but when booted to my Mac drive, it can not see my phone. My friends MacBook Pro doesn't see the phone either. I haven't looked into a work-around yet, I just boot from my Windows drive, or use my Windows laptop if I need to be connected to the computer for any reason.
---------- Post added at 01:39 PM ---------- Previous post was at 01:33 PM ----------
Try to reinstall the Samsung drivers and try again. Make sure the "Re-partition" box is checked in Odin. Use these drivers #
Click to expand...
Click to collapse
Thanks. I did that, restarted and now I get the following in Odin:
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_VZW_G900VVRU1ANI2_G900VVZW1ANI2_2525521_REV00_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Is it a factory cable? If it is redownload the file.
Yes sometimes the cable does make a difference. You can try downloading the file again, although, getting a bad download from XDA is pretty rare. I'm not familiar with Odin failing to flash a file. I've never had it happen to me.
Sent from my SM-G900V using XDA Free mobile app
jmorehouse said:
Thanks. I did that, restarted and now I get the following in Odin:
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_VZW_G900VVRU1ANI2_G900VVZW1ANI2_2525521_REV00_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
It is a stock cable. Installed the latest version of the drivers taken from Samsung Kies 3.2.14113.3 (2014-11-20) for Windows and got the following:
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_VZW_G900VVRU1ANI2_G900VVZW1ANI2_2525521_REV00_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I'm starting to think it may be a hardware problem with the phone, because you are following all of the steps exactly how you should. Odin does show that the phone is connected to a Com port right?
Sent from my SM-G900V using XDA Free mobile app
ludeawakening said:
I'm starting to think it may be a hardware problem with the phone, because you are following all of the steps exactly how you should. Odin does show that the phone is connected to a Com port right?
Sent from my SM-G900V using XDA Free mobile app
Click to expand...
Click to collapse
That is correct. It shows it on COM3.
I'm really not sure what going on. It should be working. I'll ask someone and see if they have any ideas.
Sent from my SM-G900V using XDA Free mobile app
ludeawakening said:
I'm really not sure what going on. It should be working. I'll ask someone and see if they have any ideas.
Sent from my SM-G900V using XDA Free mobile app
Click to expand...
Click to collapse
Please and thank you. I am going to try and get another laptop to try it on.
jmorehouse said:
Please and thank you. I am going to try and get another laptop to try it on.
Click to expand...
Click to collapse
Grabbed a cheap netbook off of CL and boom! There we go, it worked. Thanks so much for the help.
jmorehouse said:
Grabbed a cheap netbook off of CL and boom! There we go, it worked. Thanks so much for the help.
Click to expand...
Click to collapse
No problem. I'm glad it worked out for you. If you have any other issues don't hesitate to PM me. Helping people is one of my favorite things to do on here.
ludeawakening said:
No problem. I'm glad it worked out for you. If you have any other issues don't hesitate to PM me. Helping people is one of my favorite things to do on here.
Click to expand...
Click to collapse
Nice "thorough"job helping out the op!! :thumbup:
Sent from my SM-G900V using XDA Free mobile app
Savagerun said:
Nice "thorough"job helping out the op!! :thumbup:
Sent from my SM-G900V using XDA Free mobile app
Click to expand...
Click to collapse
Thank you. If I do step in to help, I'm the type that will not give up on someone until either the issue is solved, or it's deemed that there is a hardware issue or something and nothing can be done. I remember what it was like being lost on trying to do this stuff. I researched and studied for a long time on how Android works, so I might as well put all that gained knowledge to good use by helping people now. And that's what an awesome community like XDA does, we help each other.
jmorehouse said:
Grabbed a cheap netbook off of CL and boom! There we go, it worked. Thanks so much for the help.
Click to expand...
Click to collapse
I got your PM and I've been trying to send a reply with info on ROM's but it will not send for some reason. I'll just give you the info here. Send me another PM with your email if you don't mind, and we can communicate that way if messages continue to not work.
If you want a ROM that is on the most current base that looks the most unbranded I would go with ACHERON. I say g_ding84 has done a very good job at removing the Verizon bloatware from the ROM. I personally do not care about being on a current, so I am still running Alliance Build 2. It offers the most customization and I just had to freeze five apps to unbrand it. I use Titanium Backup Pro to freeze apps. I don't really like removing apps like that. You'll need to find the apk somewhere, or buy Titanium Backup Pro from the Play Store. I won't post any links to free versions of any apps on here. I really do not condom finding free versions of a paid app because it's not fair to the developer.
Anyway, If you would like to go with Alliance, this is the link for it http://forum.xda-developers.com/verizon-galaxy-s5/development/rom-version-1aosp-love-9-7-14-t2870149
To use this ROM you have to be sure to flash the NE9 firmware back to the phone with Odin. This is the firmware you would need to flash. http://www.androidfilehost.com/?fid=23610159112652201
The apps that you can freeze to debrand it are:
Cloud 14.2.22.2
FamilyBase Companion 4.4.5
My Verizon Mobile 10.0.709
Verizon Location Agent 0.0.2.409
Verizon Login 3.1.19
ludeawakening said:
I got your PM and I've been trying to send a reply with info on ROM's but it will not send for some reason. I'll just give you the info here. Send me another PM with your email if you don't mind, and we can communicate that way if messages continue to not work.
If you want a ROM that is on the most current base that looks the most unbranded I would go with ACHERON. I say g_ding84 has done a very good job at removing the Verizon bloatware from the ROM. I personally do not care about being on a current, so I am still running Alliance Build 2. It offers the most customization and I just had to freeze five apps to unbrand it. I use Titanium Backup Pro to freeze apps. I don't really like removing apps like that. You'll need to find the apk somewhere, or buy Titanium Backup Pro from the Play Store. I won't post any links to free versions of any apps on here. I really do not condom finding free versions of a paid app because it's not fair to the developer.
Anyway, If you would like to go with Alliance, this is the link for it http://forum.xda-developers.com/verizon-galaxy-s5/development/rom-version-1aosp-love-9-7-14-t2870149
To use this ROM you have to be sure to flash the NE9 firmware back to the phone with Odin. This is the firmware you would need to flash. http://www.androidfilehost.com/?fid=23610159112652201
The apps that you can freeze to debrand it are:
Cloud 14.2.22.2
FamilyBase Companion 4.4.5
My Verizon Mobile 10.0.709
Verizon Location Agent 0.0.2.409
Verizon Login 3.1.19
Click to expand...
Click to collapse
Awesome, thanks so much! Can you point me to a tutorial for SafeStrap Recovery?
jmorehouse said:
Awesome, thanks so much! Can you point me to a tutorial for SafeStrap Recovery?
Click to expand...
Click to collapse
You can find a video in this thread http://forum.xda-developers.com/showthread.php?t=2784290
Sent from my SM-G900V using XDA Free mobile app
Ok fellas, I'm definitely bricked here. I went to flash TWRP (before brick) and that's when it happened. Using Mac with VM Fusion, I'm able to flash my Samsung Tablet fine with this same machine fyi.
So if I just turn the phone on it goes the the Samsung Galaxy S5 initial screen and is stuck. (def no boot loop)
I've downloaded the stock firmware (yes it's the correct one) and all Odin's 3.07 - 3.10. (ran as administrator)
I've uninstalled \ reinstalled usb drivers several times, Kies is completely uninstalled.
The problem in ODIN (any version I use), is that I add the firmware, run it and get the same thing every time:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G870AUCU1ANE4_G870AATT1ANE4_G870AUCU1ANE4_HOME.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> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Any ideas on how to fix this thing?
DirtDigler said:
Ok fellas, I'm definitely bricked here. I went to flash TWRP (before brick) and that's when it happened.
So if I just turn the phone on it goes the the Samsung Galaxy S5 initial screen and is stuck. (def no boot loop)
I've downloaded the stock firmware (yes it's the correct one) and all Odin's 3.07 - 3.10. (ran as administrator)
I've uninstalled \ reinstalled usb drivers several times, Kies is completely uninstalled.
The problem in ODIN (any version I use), is that I add the firmware, run it and get the same thing every time:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G870AUCU1ANE4_G870AATT1ANE4_G870AUCU1ANE4_HOME.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> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Any ideas on how to fix this thing?
Click to expand...
Click to collapse
I hope you are using windows pc not mac, if using windows try in another pc or in your pc block antiviras temp.
Good luck
jdomadia said:
I hope you are using windows pc not mac, if using windows try in another pc or in your pc block antiviras temp.
Good luck
Click to expand...
Click to collapse
Yea I'm using VM Fusion on top of the Mac. It's actually flashing now when using a dedicated Windows box... that's just strange because I'm able to flash my Samsung 10.1 tablet fine with the VM Windows instance. Oh well. Lesson learned.
DirtDigler said:
Yea I'm using VM Fusion on top of the Mac. It's actually flashing now when using a dedicated Windows box... that's just strange because I'm able to flash my Samsung 10.1 tablet fine with the VM Windows instance. Oh well. Lesson learned.
Click to expand...
Click to collapse
Glade your problem solved.
DirtDigler said:
Yea I'm using VM Fusion on top of the Mac. It's actually flashing now when using a dedicated Windows box... that's just strange because I'm able to flash my Samsung 10.1 tablet fine with the VM Windows instance. Oh well. Lesson learned.
Click to expand...
Click to collapse
Can you boot in recovery by pressing and holding combination of buttons?
DirtDigler said:
Ok fellass
Click to expand...
Click to collapse
Next time ask your questions in Q&A that's what it's there for.
Hey guys... My xolo q500 is bricked. It stucks at the logo and doesn't go further. I was trying to install cwm recovery. But cwm was not available for my device so i tried to flash cwm of some other device from the rom manager. It was of xolo q700.But now my phone niether boots up normally nor boots in the recovery menu. It stucks at the xolo logo. I googled but i found unbricking methods for mediatek devices via sp flash tools but my device is qualcomm based so that didn't worked. Please help me how can i unbrick my device? Is there any method to unbrick qualcomm based devices?
Sent from my XT1022 using XDA Free mobile app
verma_ayush said:
Hey guys... My xolo q500 is bricked. It stucks at the logo and doesn't go further. I was trying to install cwm recovery. But cwm was not available for my device so i tried to flash cwm of some other device from the rom manager. It was of xolo q700.But now my phone niether boots up normally nor boots in the recovery menu. It stucks at the xolo logo. I googled but i found unbricking methods for mediatek devices via sp flash tools but my device is qualcomm based so that didn't worked. Please help me how can i unbrick my device? Is there any method to unbrick qualcomm based devices?
Sent from my XT1022 using XDA Free mobile app
Click to expand...
Click to collapse
You realize that you are in a Samsung Galaxy s5 forum right? You will need to find information and files directly related to your specific phone.
verma_ayush said:
Hey guys... My xolo q500 is bricked. It stucks at the logo and doesn't go further. I was trying to install cwm recovery. But cwm was not available for my device so i tried to flash cwm of some other device from the rom manager. It was of xolo q700.But now my phone niether boots up normally nor boots in the recovery menu. It stucks at the xolo logo. I googled but i found unbricking methods for mediatek devices via sp flash tools but my device is qualcomm based so that didn't worked. Please help me how can i unbrick my device? Is there any method to unbrick qualcomm based devices?
Click to expand...
Click to collapse
Try asking here, you're in the wrong place http://forum.xda-developers.com/showthread.php?t=2577489
Try jodin for mac.. Connect to different usb port... Make sure you have downloaded correct file...
Sent from my GT-I9300 using XDA Free mobile app
lingowistico said:
Try asking here, you're in the wrong place http://forum.xda-developers.com/showthread.php?t=2577489
Click to expand...
Click to collapse
Thankx buddy but that is not of much use. Everyone is just asking no has provided the solution for providing custom rom......lol. Thi device did'nt even have specific forum.
verma_ayush said:
Thankx buddy but that is not of much use. Everyone is just asking no has provided the solution for providing custom rom......lol. Thi device did'nt even have specific forum.
Click to expand...
Click to collapse
Yes, exactly. That's why that thread is the most appropriate for YOU. Because there is no dedicated forum for your phone. Or you can start a new thread in here http://forum.xda-developers.com/android/help . That's it. Good luck :good:
Deleted
Allo,
I finally found the ROM for Galaxy S4 SGH-I337M and the CF auto root.
ROM file : I337MVLUGOC4_I337MOYAGOC4_I337MVLUGOC4_HOME.tar.md5 (Virgin mobile, lollipop 5.0.1)
CF Root : CF-Auto-Root-jfltecan-jfltevl-sghi337m.tar.md5
The problem is that ODIN transfers the image to the phone but fails at the very last bytes. It says added, fails, removed.
Odin 3.09 is used, autorebbot and F.Reset are ticked. Nothing else.
What am I doing wrong???? What is required to have a sucessful upload?
Need help, phone is bricked.
I just flashed this file with odin 3.04, no problems except I had to flash it twice to change baseband, and my carrier is fido, so I had to change csc. I have seen recommendations here to use that version of Odin with this particular model, never failed me. Also, I use my original Samsung cable for Odin flashes, seen posts that cheap cables make a difference. and make sure you have all the correct drivers installed. I can't help other then that, sorry, limited knowledge myself, but the search button is your friend, all kinds of answers on the forums.
pcote_xda said:
Allo,
I finally found the ROM for Galaxy S4 SGH-I337M and the CF auto root.
ROM file : I337MVLUGOC4_I337MOYAGOC4_I337MVLUGOC4_HOME.tar.md5 (Virgin mobile, lollipop 5.0.1)
CF Root : CF-Auto-Root-jfltecan-jfltevl-sghi337m.tar.md5
The problem is that ODIN transfers the image to the phone but fails at the very last bytes. It says added, fails, removed.
Odin 3.09 is used, autorebbot and F.Reset are ticked. Nothing else.
What am I doing wrong???? What is required to have a sucessful upload?
Need help, phone is bricked.
Click to expand...
Click to collapse
99% of all Odin errors are solved by the following:
- Different usb port
- Different cable
Allo,
I followed the instructions provided by JesterDoobie and I took note of the advise provided by Lennyz1988.
It works my friends, thank you for your support. At the end, I had to use a Samsung genuine cable to reach a complete and successful upload of the ROM.
With a third party cable, it would transfer but at the end (99% completed) it would indicate in red FAILS and the ODIN messages were:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337MVLUGOC4_I337MOYAGOC4_I337MVLUGOC4_HOME.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> Firmware update start..
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> cache.img.ext4
<ID:0/003> hidden.img.ext4
<ID:0/003> modem.bin
<ID:0/003> NON-HLOS.bin
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
With the procedure and Samsung cable = home run.
Ok i have searched the site for an exact answer to the issue i have encountered, with not getting a specific answer to my question. If there is already a thread for my exact problem, or two to solve the two issues i have encountered, please share the link, thank you.
My Wife and I got her son a Galaxy J3 (SM-J320fn) open network, with a Giff Gaff sim, from Argos. Its his first phone and we wanted to see if he could look after it, and if so, we would get him a better model at Christmas. Now his dad wanted to put google family link on the device, and due to it being only android 5.1, this was not possible. This sparked a huge row between my wife and her ex, with him being a general ****. I have tinkered with PC's and X-box 360s before, and thought i could have a go at Rooting the device and installing a custom android 7 rom. I didn't go into this lightly, and read that XDA was the very best place to seek advice and guides. I read up on rooting the device i had, Odin,TWRP and the OS linage android 7 rom. I was comfortable, that although it was very in depth to my skill set, i felt i could do it. I followed the guide to rooting the J320fn, installing the drivers, and USB debugging, fired up ODIN as administrator and installed TWRP, from there i followed the guide to install the custom ROM after than.
all was fine. device was android 7 and google family link was installed. everybody was happy...
My step son left his phone in the school office after his football match after school the other day and the device powered down for the first time since i uploaded the custom rom. When powering up the device we got the custom binary blocked by FRP lock issue. ok... so i came back here to XDA to read a thread about that. i decided that maybe i should have looked into other parental apps instead of messing about with the phone. so i went down the root of restoring the stock firmware and to battle it out with the dad about using a different parental app. so i downloaded the stock firmware for the device, and put the device into download mode. i ran ODIN but the install failed and on the device the loading bar at the bottom was about 5mm into the download and nothing else moved... ****... ok... now what? i took out the battery, and then powered up again. "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again" ... Oh man, now what. so i return back XDA to look at this. read the guide and went to KIES3 to install stock firmware, but kies doesn't seem to recognise my device model? i click the emergency firmware recovery, but lists no device to recover?
so now im searching frantically to solve this... i downloaded the stock firmware from SamMobile; J320FNXXU0ARA1_J320FNEVR0ARA1_J320FNXXU0ARA1_HOME.tar.md5 (which took like 17 hours.. meh) and that Fails in ODIN too...
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1100)..
<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> cache.img
<ID:0/003> hidden.img
<ID:0/003> nvitem.bin
<ID:0/003> PM_sharkl_arm7.bin
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
then i read to try install TWRP again, which also didn't work either as that brought up the binary blocked by FRP again and Failed in ODIN.
"<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1100)..
<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> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)"
So now i really don't know what to do... is it bricked? any and all help would be much appreciated.
Thank you
Rob