Related
Hello and thanks in advance for any suggestions or comments.
Here is my problem. I was trying to flash back to stock using Odin3 and have tried many times. However it progresses to FACTORYFS and stops any progress. And it sits and sits and sits. No progress. Why??? Please. If anyone can give me any advice please do. Thanks.
Forst you need to have your phone in download mode.... if your havin trouble with the process download AIO VIBRANT TOLLBOX.. its really helpful and also you need to have the appropiate files and if it keeps doing that.... download odin again....
Sent from my GT-I9000 using XDA Premium App
Are you running windows 7?
If so, reboot your computer, hit F7 to get into the safe mode options, then disable device driver enforcement.
Sounds wierd but it fixes my odin from locking up everytime.
Hi,
Can you link to the firmware you downloaded? I've seen this a few times and it was a faulty TAR package. If you are looking for a good reliable 2.1 JFD package I have on one of my download pages:
http://www.mobiletechvideos.com/blog/?page_id=186
I had this same problem several weeks ago. I used the same files Ive always used to odin. Just keep trying it. It took me over 3 hours before it finally went thru. Ive been scared to use odin every since/
check the md5
try another usb port
using the latest odin?
any other usb devices plugged in? If so, remove them, reboot, try again.
using the usb that came with your phone?
Man, you guys are awesome. I'm always amazed and impressed at everyones willingness to help others in need even if their(my)problems are self inflicted. Thank you.
We just had a baby and are at the doctors office at the moment but as soon as we are done I will get back to it and see what can be done.
Again thanks a million.
acontreras138 said:
Man, you guys are awesome. I'm always amazed and impressed at everyones willingness to help others in need even if their(my)problems are self inflicted. Thank you.
We just had a baby and are at the doctors office at the moment but as soon as we are done I will get back to it and see what can be done.
Again thanks a million.
Click to expand...
Click to collapse
Dude... CONGRATULATIONS!!
Best thing that ever happened to me.
Congrats! Kids ROCK!!!
Don't be afraid to PM these guys, there are people more than willing to help you out here at XDA. Saved my behind more than once. Just have patience, as they say - "help is on the way"
Ok first thanks for the words of encouragement with the baby. She is beautiful.
Now back to work. First things first. When it freezes at FACTORY FS what is the safest way to disconnect? Battery pull?(seems scary) x out?(also scary).
I have disabled the driver enforcement but still have the same problem. Thanks though.
s15274n said:
check the md5
try another usb port
using the latest odin?
any other usb devices plugged in? If so, remove them, reboot, try again.
using the usb that came with your phone?
Click to expand...
Click to collapse
Alright so far I have
1. Disabled devices driver enforcement
2. Tried all 3 of my usb ports
3. Currently using Odin3v1.00 (about to search for a newer version)
4. Removed all connected usb devices
5. Rebooted twice
Results = same. Bummer
I have not checked the md5. Not really sure how to and what/where to check. I know its something that I should know by know but never have needed to till now I guess.
MD5 - use Hashtab
http://implbits.com/HashTab.aspx
That IS an old version of odin, that is known to hang... my signature for going back to stock has files, inc newer ODIN.
I suggest getting a new pit and tar from there too.
Going back to stock in my signature
I'm still curious as to whether you tried my 2.1 JFD tar package. This will eliminate the thought of a corrupt PDA TAR package. Can you please try it? I replied on page 1. In the past your issue was caused by a corrupt/incomplete TAR package.
connexion2005 said:
I'm still curious as to whether you tried my 2.1 JFD tar package. This will eliminate the thought of a corrupt PDA TAR package. Can you please try it? I replied on page 1. In the past your issue was caused by a corrupt/incomplete TAR package.
Click to expand...
Click to collapse
I will give anything a shot at this point. Downloading now.
Sent from my HTC Vision using XDA App
connexion2005 said:
I'm still curious as to whether you tried my 2.1 JFD tar package. This will eliminate the thought of a corrupt PDA TAR package. Can you please try it? I replied on page 1. In the past your issue was caused by a corrupt/incomplete TAR package.
Click to expand...
Click to collapse
PASS PASS PASS! THANK YOU! seriously huge thank you to every one who posted and made any suggestions. You guys neve fail to amaze me. Humanity is not lost. I shall pay it forward today. Xda rocks!
Sent from my HTC Vision using XDA App
s15274n said:
MD5 - use Hashtab
http://implbits.com/HashTab.aspx
That IS an old version of odin, that is known to hang... my signature for going back to stock has files, inc newer ODIN.
I suggest getting a new pit and tar from there too.
Going back to stock in my signature
Click to expand...
Click to collapse
And to you sir thank you for putting up with my unending questions. My freaking out. Thank you. Where do I donate?
Sent from my HTC Vision using XDA App
connexion2005 said:
I'm still curious as to whether you tried my 2.1 JFD tar package. This will eliminate the thought of a corrupt PDA TAR package. Can you please try it? I replied on page 1. In the past your issue was caused by a corrupt/incomplete TAR package.
Click to expand...
Click to collapse
And to you too. Thank you.it was your package that finally passed the the flash. Where do I donate?
Sent from my HTC Vision using XDA App
I am glad you got it all square man. No need to donate, but when you flash trigger or cm7 you should hook them up. Donate links are above the avatar of the developers.
Did you check the md5? Willing to bet mine and his have the same, assuming one was not corrupt.
Now go stare wildly.... At your new kid!
I Had CM7 on my vibrant but cant take the intability and lack of Gps. I have searched the forums and tried everything i could. I can get into download mode, but odin always gets stuck at cache.rfs. What do I do? i really dont want to take this to tmobile.
If you have the JFD pit and pda did you check the partition box? Going from CM7 to JFD you need to partition. Just make sure its the JFD odin you got.
Moped_Ryder said:
If you have the JFD pit and pda did you check the partition box? Going from CM7 to JFD you need to partition. Just make sure its the JFD odin you got.
Click to expand...
Click to collapse
It still hangs on cache.rfs. Im sure its the JFD for Odin. i downloaded them in one rar archive.
I'm frustrated.
At this point i would go back to CM7 if i could. The phone originally had the Phone-!-computer. its not doing that now.
skullreapper66 said:
At this point i would go back to CM7 if i could. The phone originally had the Phone-!-computer. its not doing that now.
Click to expand...
Click to collapse
what version of odin are you using, try 1.85 if you arent
mine use to freeze with 1.7, not all the time just some times, i havent needed to use .85 yet, im only going to when i need to
kyle51 said:
what version of odin are you using, try 1.85 if you arent
mine use to freeze with 1.7, not all the time just some times, i havent needed to use .85 yet, im only going to when i need to
Click to expand...
Click to collapse
I have tried 1.7, 1.0, 1.85, and 1.3. all with pretty much the same results
When u plug it in if it gets removed then restart odin an re do download mode i had similar problem
Sent from my SGH-T959 using XDA Premium App
Jasonhunterx said:
When u plug it in if it gets removed then restart odin an re do download mode i had similar problem
Sent from my SGH-T959 using XDA Premium App
Click to expand...
Click to collapse
Tried this and nothing
could it have anything to do with the file path thats on my computer? files scattered everywhere, but im sure my post will likely be pushed to the back of the forum. happens to me all the time.
No help for me i guess. It wont turn on except download mode, would tmobile know i bricked it if i sent it back?
You can try downloading the PIT and PDA from a different source and see if that helps.....just my 0.2. Good luck man!
try a different usb...
Thanks button if i helped
Just keep trying. It will eventually go thru. Several weeks ago I had this problem. After 3.5 hours it finally went thru.
Bi-winning V3
Dan_Brutal said:
You can try downloading the PIT and PDA from a different source and see if that helps.....just my 0.2. Good luck man!
Click to expand...
Click to collapse
I have tried several different sources. thx
yalkowni said:
try a different usb...
Thanks button if i helped
Click to expand...
Click to collapse
I have tried this already and it doesnt make any difference. i actually cant get my computer to recognize it with the stock cable. as for ports, i have tried that too with the same results
GreggoryD502 said:
Just keep trying. It will eventually go thru. Several weeks ago I had this problem. After 3.5 hours it finally went thru.
Bi-winning V3
Click to expand...
Click to collapse
I will, but I've been trying for a couple days now.
@ skullreapper66 if your on windows seven or xp i guess keep pressing f8 or f9 one of them. when you boot up, until you go into a black menu and scroll down to disable signature verification
jalenthejiv said:
@ skullreapper66 if your on windows seven or xp i guess keep pressing f8 or f9 one of them. when you boot up, until you go into a black menu and scroll down to disable signature verification
Click to expand...
Click to collapse
Didnt work. thanks though
Taken from my guide:
IF ODIN HANGS ON YOU:
- Are you using my files (all 3 of them?)
- Did you check the MD5 using Hashtab
- Are you using the cable that came with your phone?
- Have you tried other USB ports on you PC?
- Have you removed all other USB devices and rebooted (ie webcam)
Please check the MD5 of the pit/tar using Hashtab.
http://www.youtube.com/watch?v=O9Jp3w8Z10s
Hi!
I've got an SGS2 (i9100) and i tried to update firmware using Kies 2.0 which i installed and downloaded for the first time today.
During the upgrade something happened and all i get on the phone now is the logo i've described.
Kies is trying to do "emergency recovery" and is just sitting at 0% so i'm not sure what that's doing.
I've tried ODIN which seems to pick up the phone on COM4 so i downloaded the I9100XXKI3 file from this thread...
http://forum.xda-developers.com/showthread.php?t=1449771
and clicked on start and it gets to zImage and just sits there, i'm not sure if it's doing anything but i left it for 30 minutes and nothing happened.
I've also tried OneClickUnbrick from here:
http://forum.xda-developers.com/showthread.php?t=1153310
and that can't find the phone.
I can get into ODIN mode on the phone (I think that's recovery) by doing volume down, bottom button and power on.
Anyone got any ideas above what i'm trying?
I think i should be able to get hold of a jig/jtag cable beyond that no idea!
Fixed!
Downloaded the latest ODIN
Downloaded the GT-I9100_XEU_I9100XWKI4_I9100XEUKH2_I9100XXKI1.tar.md5
Plugged into my work PC which didn't have Kies and it also had a different USB cable (that might have mattered)
Swapped the battery for a fully charged one (the original was on 14%!!)
Phone was off and then plugged into the PC
Let the drivers install
Ran ODIN
ODIN picked up the phone (yellow box)
Only selected PDA and located the above tar.md5
clicked on start
*stuff happened*
got a progress bar on the phone
rebooted
it went into a recovery mode and cleared cache and some other stuff automatically.
rebooted
took about 5mins to boot up
bingo!
Hope this helps anyone else with the same problem.
Try different USB ports (must use a powered/mainboard port), different USB cables (particularly the cable that came with the phone), different versions of Odin (search for them), redownload the package you were trying to flash and test the package with 7Zip, IZarc, WinRar or similar to ensure there are no damaged files in it.
If those don't work, try another PC.
If you can get into download mode & Odin recognises the phone (yellow in COM panel), you can almost always save it.
Thanks MistahBungle.
Shall i forget using Kies then?
As this phone doesn't need to be rooted and do you think the data on the phone is gone now or if i manage to reflash something it was just upgrade what's there?
thing is i can't remember what version it was trying to upgrade to. i know it was on 2.3.5 which i think is XXKI3.
I seem to remember the battery was pretty low as well, can that cause a problem?
If u had ur phones drivers properly installed on ur pc, u can dl a program called Heimdall one click unbrick. Look up how 2 use it on YouTube. Works great with any Android device that gets the "phone-triangle-pc" screen.
Sent from my Rooted samsung-SGH-I727 using XDA
Yeah Kies is rubbish. Bin it. Also, when you're using Odin, check Windoze task manager & make doubly absolutely 100000% sure that Kies & any of it's processes are not running. If they are, kill them. You need the drivers that come with Kies to use Odin, but Kies & Odin running at the same time does not work.
Unless the stock rom you flash specifically wipes, you might retain your data (I hope you made regular backups).
Yeah low battery could easily cause a flash to barf.
bewA said:
Thanks MistahBungle.
Shall i forget using Kies then?
As this phone doesn't need to be rooted and do you think the data on the phone is gone now or if i manage to reflash something it was just upgrade what's there?
thing is i can't remember what version it was trying to upgrade to. i know it was on 2.3.5 which i think is XXKI3.
I seem to remember the battery was pretty low as well, can that cause a problem?
Click to expand...
Click to collapse
Thank you again!
Is there version of the stock firmware you know that won't wipe.
From what i can tell if i tick repartition and provide a pit file then this will dump everything so maybe if i can not apply those then in theory that won't wipe anything? i'm not sure if that's accurate logic.
I've downloaded this:
GT-I9100_XEU_I9100XWKI4_I9100XEUKH2_I9100XXKI1
and i'm downloading
I9100XXKI3.rar
I'm slightly worried about grabbing the right PIT file as i've seen people flash the one for a G version or plain 9100 on the wrong version and it's bricked the phone.
I know the one i'm trying to repair is just I9100 (that's what it says behind the battery and in ODIN mode).
I'm more of a Galaxy Nexus abuser so the the SGS2 stuff is new territory.
it also doesn't help that majority of stuff i've been finding used to be on some file sharing sites and they've either had the site shut down and panic'd and now only allowing downloads unless you own the account!
Do not tick repartition or touch anything to do with PIT !
Clear ? Good.
If you use firmware download from links on XDA there will be only one file which you flash in PDA section of Odin, no need to touch PIT. Ever.
bewA said:
Thank you again!
Is there version of the stock firmware you know that won't wipe.
From what i can tell if i tick repartition and provide a pit file then this will dump everything so maybe if i can not apply those then in theory that won't wipe anything? i'm not sure if that's accurate logic.
I've downloaded this:
GT-I9100_XEU_I9100XWKI4_I9100XEUKH2_I9100XXKI1
and i'm downloading
I9100XXKI3.rar
I'm slightly worried about grabbing the right PIT file as i've seen people flash the one for a G version or plain 9100 on the wrong version and it's bricked the phone.
I know the one i'm trying to repair is just I9100 (that's what it says behind the battery and in ODIN mode).
I'm more of a Galaxy Nexus abuser so the the SGS2 stuff is new territory.
Click to expand...
Click to collapse
crystal clear!
Good man Always remember, anything to do with PIT is an absolute last resort to only be messed with in very specific circumstances (I.E. you know for certain the problem you're having is a partition issue).
bewA said:
crystal clear!
Click to expand...
Click to collapse
and to confirm this:
CODE_I9100XXKI3_CL577579_REV02_user_low_ship.tar.md5
OR
GT-I9100_XEU_I9100XWKI4_I9100XEUKH2_I9100XXKI1.tar.md5
is the only file i need to use in the PDA section?
I presume the first one you got from Samfirmware or elsewhere ? Use the one you got from here (the second one). 1 file, PDA section of Odin (at the risk of repeating myself).
bewA said:
and to confirm this:
CODE_I9100XXKI3_CL577579_REV02_user_low_ship.tar.md5
OR
GT-I9100_XEU_I9100XWKI4_I9100XEUKH2_I9100XXKI1.tar.md5
is the only file i need to use in the PDA section?
Click to expand...
Click to collapse
i know i'm sorry I just need to make sure i understand the process!
Just to update you.
Flashed the second file using ODIN for the PDA.
Swapped a fully charged Samsung battery with someone in the office plugged into my work pc which already had Samsung drivers (for my GN).
and now all working!!
Didn't loose any data!
Thank you so much MistahBungle!!
No worries guv. Glad you got it sorted & also glad you didn't lose any data as well
bewA said:
Just to update you.
Flashed the second file using ODIN for the PDA.
Swapped a fully charged Samsung battery with someone in the office plugged into my work pc which already had Samsung drivers (for my GN).
and now all working!!
Didn't loose any data!
Thank you so much MistahBungle!!
Click to expand...
Click to collapse
MistahBungle said:
No worries guv. Glad you got it sorted & also glad you didn't lose any data as well
Click to expand...
Click to collapse
You've saved me from divorce!
Now i just need to look at doing ICS... after i've fully charged the phone!
Hahaha Hmmmm. Is that a good or bad thing tho ?
So far as ICS is concerned, I've tried Miui V4 which is ****e & needs a lot of work. I tried CM9 about two weeks ago & it was fantastic considering how little they've had to work with, and I'm just about to try the 20 March build of CM9 now. Looking at the discussion thread, they've made a fair bit of progress since I tried it previously.
Obviously there are other ICS variants out there & quite a few stock ICS roms floating around. As always, do your homework/research first, make sure you fully understand whatever it is you're wanting to do to your phone, always check downloads (large ones anyways) to ensure they're not corrupt & you should be fine
bewA said:
You've saved me from divorce!
Now i just need to look at doing ICS... after i've fully charged the phone!
Click to expand...
Click to collapse
Well i'll be going to a Stock ICS but as far as doing it with Kies that going in the digital bin (to put it politely)!
As the phone is an unbranded one (not fixed to a network) from what i've read there isn't a UK unbranded one yet, i was toying with the idea of doing I9100XXLPQ but i might let the dust settle depending on what i read throughout the day
Alright guys as my title states I pulled a "noob move" and it looks like I've soft bricked my phone (It won't boot past the verizon splash screen). I've done a little research and I'm pretty familiar with Odin and how it works. Seems to be the same concept as jungle flasher and I've modded a few 360's in my time. I've tried, to no avail, to flash my phone back with the stock image numerous times and I figured it was time to consult the experts. What I've done so far: Downloaded the factory stock restore TAR from Rwilco12's site and put that in the PDA file browser of Odin. My phone shows up in Odin when connected in download mode with a light blue com:4 box. I read sometimes this is supposed to be yellow? Other versions of Odin it is yellow. This instance was attempted in 3.07. 1.85 it shows up as yellow. Regardless of either version, they both fail after the "aboot" step. I've tried two computers and have failed miserably all morning. Any help or advice would be much appreciated.
-Be easy on me, it's my first time.
-HerdOn
HerdOn said:
Alright guys as my title states I pulled a "noob move" and it looks like I've soft bricked my phone (It won't boot past the verizon splash screen). I've done a little research and I'm pretty familiar with Odin and how it works. Seems to be the same concept as jungle flasher and I've modded a few 360's in my time. I've tried, to no avail, to flash my phone back with the stock image numerous times and I figured it was time to consult the experts. What I've done so far: Downloaded the factory stock restore TAR from Rwilco12's site and put that in the PDA file browser of Odin. My phone shows up in Odin when connected in download mode with a light blue com:4 box. I read sometimes this is supposed to be yellow? Other versions of Odin it is yellow. This instance was attempted in 3.07. 1.85 it shows up as yellow. Regardless of either version, they both fail after the "aboot" step. I've tried two computers and have failed miserably all morning. Any help or advice would be much appreciated.
-Be easy on me, it's my first time.
-HerdOn
Click to expand...
Click to collapse
Have you tried a different USB cable and/or running odin as an administrator?
BladeRunner said:
Have you tried a different USB cable and/or running odin as an administrator?
Click to expand...
Click to collapse
Yes, I've used the factory samsung and another cable while running as an administrator. Thanks for the thought though!
HerdOn said:
Yes, I've used the factory samsung and another cable while running as an administrator. Thanks for the thought though!
Click to expand...
Click to collapse
which Verizon release are you on VRUAMDK or VRUAME7?
BladeRunner said:
which Verizon release are you on VRUAMDK or ?
Click to expand...
Click to collapse
VRUAME7 is the most recent with the latest OTA update correct? If so that's the one I was on. Now I did root it successfully initially, it got stuck this way after installing SuperSU... I guess I should have said that initially. My apologies.
HerdOn said:
VRUAME7 is the most recent with the latest OTA update correct? If so that's the one I was on. Now I did root it successfully initially, it got stuck this way after installing SuperSU... I guess I should have said that initially. My apologies.
Click to expand...
Click to collapse
ME7 is the current OTA, yes. Are you using the correct .TAR file from here? http://www.androidfilehost.com/?fid=23032113221600748? Also did you try doing a data wipe/factory reset in stock android recovery?
BladeRunner said:
ME7 is the current OTA, yes. Are you using the correct .TAR file from here? Also did you try doing a data wipe/factory reset in stock android recovery?
Click to expand...
Click to collapse
The link you sent was broken, I'm using the rwilco12 factory image. It wont let me post a link because I don't have enough posts.
I have tried doing the data wipe/factory reset but it kept saying error. and now it says Firmware upgrade encountered an issue please select recovery mode in kies and try again. That's when going to the volume up "recovery" mode. Volume down, "download" mode still works fine.
http://www.androidfilehost.com/?fid=23032113221600748
The link BladeRunner posted had an extra question mark. Try that one.
Sent from my SCH-I545 using xda app-developers app
HerdOn said:
The link you sent was broken, I'm using the rwilco12 factory image. It wont let me post a link because I don't have enough posts.
I have tried doing the data wipe/factory reset but it kept saying error. and now it says Firmware upgrade encountered an issue please select recovery mode in kies and try again. That's when going to the volume up "recovery" mode. Volume down, "download" mode still works fine.
Click to expand...
Click to collapse
sorry, here is the link to the Odin files thread: http://forum.xda-developers.com/showthread.php?t=2301259 Download the VRAUME7 factory image. I'm not sure but I think you may have the MDK image from RWILCO and there's no going back to that once you've updated to ME7.
---------- Post added at 02:26 PM ---------- Previous post was at 02:25 PM ----------
Checkm8 said:
http://www.androidfilehost.com/?fid=23032113221600748
The link BladeRunner posted had an extra question mark. Try that one.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
Thanks! Don't know where that extra "?" came from
Alright I'm downloading that version now. Its capping my connection so it should be done in 25 mins and we'll try again! Thanks for your help so far bladerunner. Seems like we're getting somewhere...
Bladerunner, you were right my friend! The image is finally going to the phone. After nearly pulling all of my hair out, we're making extreme progress!
Ten minutes later my phone is back to factory flawless condition. Thanks Bladerunner for all your help! It's very much appreciated..
HerdOn said:
Ten minutes later my phone is back to factory flawless condition. Thanks Bladerunner for all your help! It's very much appreciated..
Click to expand...
Click to collapse
Excellent! No problem
I have a Verizon Galaxy S4 and after I flashed what I thought was a recovery of CleanROM it turns out it was actually VRUAME7 (Found Here).
Since I was under the impression it was CleanROM, I tried flashing the stock image of VRUAMDK (also found at the link above).
Obviously, my GS4 didn't like that move, and got mad, now I am not able to flash VRUAME7, it keeps failing in Odin.
Any thoughts?
Pipester said:
I have a Verizon Galaxy S4 and after I flashed what I thought was a recovery of CleanROM it turns out it was actually VRUAME7 (Found Here).
Since I was under the impression it was CleanROM, I tried flashing the stock image of VRUAMDK (also found at the link above).
Obviously, my GS4 didn't like that move, and got mad, now I am not able to flash VRUAME7, it keeps failing in Odin.
Any thoughts?
Click to expand...
Click to collapse
If you're at ME7, installing a recovery will fail. You must recover by flashing stock. If your download is failing in Odin, then it's not ME7 or corrupted, so try again.
For examples of some of the dozens of others posting about this:
"Back to Stock" http://forum.xda-developers.com/showthread.php?t=2421038
"HELP ME UNBRICK PLEASE" http://forum.xda-developers.com/showthread.php?t=2420674
"Flashing back to stock" http://forum.xda-developers.com/showthread.php?t=2420485
"HELP! I think I hard bricked my s4" http://forum.xda-developers.com/showthread.php?t=2324965
k1mu said:
If you're at ME7, installing a recovery will fail. You must recover by flashing stock. If your download is failing in Odin, then it's not ME7 or corrupted, so try again.
For examples of some of the dozens of others posting about this:
"Back to Stock" http://forum.xda-developers.com/showthread.php?t=2421038
"HELP ME UNBRICK PLEASE" http://forum.xda-developers.com/showthread.php?t=2420674
"Flashing back to stock" http://forum.xda-developers.com/showthread.php?t=2420485
"HELP! I think I hard bricked my s4" http://forum.xda-developers.com/showthread.php?t=2324965
Click to expand...
Click to collapse
That's just it. Since I flashed VRUAME7, I mistakenly flashed VRUAMDK... So I tried flashing VRUME7 again, and it keeps failing.
Pipester said:
That's just it. Since I flashed VRUAME7, I mistakenly flashed VRUAMDK... So I tried flashing VRUME7 again, and it keeps failing.
Click to expand...
Click to collapse
See http://forum.xda-developers.com/showthread.php?t=2421307&goto=nextoldest#post45009830
You're not alone, and just need the right file to flash.
There have been quite a few people in the same situation. Theres no reason me7 shouldnt take unless you got bad or the wrong files. Is it by chance giving you the error when flashing aboot?
Sent from my SCH-I545 using Tapatalk 2
k1mu said:
See http://forum.xda-developers.com/showthread.php?t=2421307&goto=nextoldest#post45009830
You're not alone, and just need the right file to flash.
Click to expand...
Click to collapse
No dice.
Try this
http://forum.xda-developers.com/showthread.php?p=43420116
Flash under pda
Sent from my SCH-I545 using Tapatalk 2
hexitnow said:
Try this
http://forum.xda-developers.com/showthread.php?p=43420116
Flash under pda
Click to expand...
Click to collapse
I already tried that one.
It keeps failing at system.img.ext4
Well, As it turns out... it was my USB hub. My USB cable was going into a hub. For the hell of it I decided to move my usb cable to a port directly on my PC and it worked.
I feel dumb.
Thank you guys for your help!!
Pipester said:
Well, As it turns out... it was my USB hub. My USB cable was going into a hub. For the hell of it I decided to move my usb cable to a port directly on my PC and it worked.
I feel dumb.
Thank you guys for your help!!
Click to expand...
Click to collapse
Don't feel dumb, anyone could have made that mistake! I learned the phone must be connected to a USB port on the PC and not to a hub while flashing a stock Moto ROM to my Motorola V9M and how long ago was that?
http://mark.cdmaforums.com/USC-V9M-Monster1.htm
It was 2008 or earlier. I can't remember breakfast so there's no way I can recall all the way back to 2008!
It's easy to forget and even easier for the devs to not mention this in their instructions for flashing!
FWIW, I do use a powered hub now and I don't have any problems but I think it depends on the hub, on the PC (specifically the Motherboard) and on the USB handling of the OS so what works for me may or may not work for anyone else.
Again, don't feel dumb, just be glad it was an easy fix!
Pipester said:
Well, As it turns out... it was my USB hub. My USB cable was going into a hub. For the hell of it I decided to move my usb cable to a port directly on my PC and it worked.
I feel dumb.
Thank you guys for your help!!
Click to expand...
Click to collapse
Thank you for letting us know the cause, as it will help others in the future!
k1mu said:
Thank you for letting us know the cause, as it will help others in the future!
Click to expand...
Click to collapse
No problem. It's important to note that it initially worked in the HUB, but somewhere down the line there must have been some communication errors. So, just because it worked once, doesn't mean it will always work.