Last night, I tried flashing a new ROM and whenever I restarted or booted the phone, it sent me to recovery mode. I couldn't do anything about it. Today I flashed the Odin version of GeeWiz and when I try to flash a new ROM in recovery, it says "operation aborted" and when I try to restore my backup, it says "system.img not found. Skipping"
How can I fix this??? Please help very soon!
Please! Am I bricked?
I'm not sure what went wrong, you're not really supplying any details about what you did, but I would say make sure to follow droidstyle's guide exactly as he says to, and if you still have issues to come back here with exactly what went wrong.
ODIN CWMALL, then try that backup again.
See droidstyle's guide.
Worse case justODIN back to stock EH03 and start again.
MultipleMonomials said:
ODIN CWMALL, then try that backup again.
Click to expand...
Click to collapse
Didn't work.
Then your backup really is corrupted. You're not trying to restore a backup made with a different version of CWM, are you? What ROM were you on and what ROM did you flash?
MultipleMonomials said:
Then your backup really is corrupted. You're not trying to restore a backup made with a different version of CWM, are you? What ROM were you on and what ROM did you flash?
Click to expand...
Click to collapse
I was on cyanogen mod. But also If I try to flash roms through cwm, it doesn't work.
Me thinks you need to take the advice of what has been mentioned and follow droidstyle's to get yourself back to stock. That is...if you want to take a cchance on getting your phone to work again.
Sent from my SCH-R530U using Tapatalk 2
I took all of the advice. I eventually ended up using a different recovery and my roms flashed fine. I feel really stupid
OK, two new problems. My phone keeps booting into recovery, and the battery messes up. When I boot with it plugged in, it's at like 14% and when I boot without it plugged in, it's at like 65%. Please help!
Maybe try to re-calibrate the battery? The simpliest method I've come across is found here, just scroll down a bit to the section labeled 'RECONDITION YOUR BATTERY'. As far as booting into recovery, I'm not too sure what might have happened there, might just need to start again from stock like you've probably already done a hundred times
Related
Okay, so after installing the kang build 25 ICS for the vibrant, everything went fine. Randomly I get a random reboot and my phone says there was an "encryption error" and that I have to do a factory reset. Since I already had everything backed up, I didn't mind the data wipe. When it went rebooted the CWM screen came up and started wiping everything but when it got to the "formatting data" part, it failed. I tried this many times and it kept failing... SO, I decided to ODIN back to JFD. After doing so, all I get is the Vibrant screen, then an instant shut down. I even tried Eugene's old No Brick Froyo PDA, then tried to reinstall the JFD image, but got no luck.
Question is: What should I do now?
Any help will be GREATLY appreciated. Thanks!
Its a little involved but It's all I could find to help buddy
http://www.youtube.com/watch?v=Rdn5GoRjhn0
It's not the easiest thing in the world to accomplish but It is a guarantied way to get your vibrant into successful download mode to reflash to stock.
At the least something to get you started
Good Luck!
Perhaps it could be a bootloader problem? If you're sure you are doing Odin right, including repartition with the pit file, you could look at your SBL.
.
Sorry but what is SBL?
lolrus101 said:
Sorry but what is SBL?
Click to expand...
Click to collapse
I dont know how to explain it very well lol but to check if the rom you are trying to odin has the sbl in it. Rename it and put a .zip at the end. Then extract to see if its in there it should be named "sbl". To change it back simply delete the .zip off the original file.
JFD
I'm trying to ODIN the original JFD firmware, and I just checked that it does not have SBL in it.
Try odining a rom that has the sbl file in it thats probably why its not working.
---------- Post added at 04:14 AM ---------- Previous post was at 04:09 AM ----------
Here http://forum.xda-developers.com/showthread.php?t=1278683 you need to have java installed to open it
Just tried the Heimdall thing. No luck. As soon as it says rebooting, it goes to the vibrant screen, then the battery charging screen, then continues to bootloop. Same thing happened with Odin
why don't you try what I did
http://forum.xda-developers.com/showpost.php?p=23056603&postcount=10
lolrus101 said:
I'm trying to ODIN the original JFD firmware, and I just checked that it does not have SBL in it.
Click to expand...
Click to collapse
The SBL is the Secondary Boot Loader, which is loaded by the Primary Boot Loader.
I haven't personally encountered any roms which also flash bootloaders.
I did manage to get my phone bootlooped in some weird way which apparently could only be fixed by reflashing the SBL. Note: flashing bootloaders is more dangerous than regular roms.
I am presently running a GB SBL from this thread:
http://forum.xda-developers.com/showthread.php?t=1117990
ian577416 said:
http://www.youtube.com/watch?v=Rdn5GoRjhn0
It's not the easiest thing in the world to accomplish but It is a guarantied way to get your vibrant into successful download mode to reflash to stock.
At the least something to get you started
Good Luck!
Click to expand...
Click to collapse
a 301kohm jig is ONLY good if you have a valid Initial Bootloader, Primitive Bootloader, Partition Table AND Secondary Bootloader. If you damage any of those, a 301kohm jig won't work.
Use UnBrickable Mod. http://forum.xda-developers.com/showthread.php?t=1277056
Flashed the GB bootloader and no luck either . Flashed back to the froyo one, and got the data wipe error again, the phone rebooted, and now its at "KERNEL PANIC - UPLOAD MODE"
AdamOutler said:
a 301kohm jig is ONLY good if you have a valid Initial Bootloader, Primitive Bootloader, Partition Table AND Secondary Bootloader. If you damage any of those, a 301kohm jig won't work.
Use UnBrickable Mod. http://forum.xda-developers.com/showthread.php?t=1277056
Click to expand...
Click to collapse
I have already tried the Heimdall method... and I can access download mode. I think the thing that is causing the bootloop is that the Data wipe fails after a restore. Thats when the bootloop kicks in
lolrus101 said:
I have already tried the Heimdall method... and I can access download mode. I think the thing that is causing the bootloop is that the Data wipe fails after a restore. Thats when the bootloop kicks in
Click to expand...
Click to collapse
If you did Odin/Heimdall to stock after flashing the SBL, and it is still messed up, its beyond me and I'd really like to know the fix. Wiping should be irrelevant after Odining to stock.
If you are getting errors in recovery when you try to wipe/format/restore, that indicates a mismatch between the kernel and the partitioning or filesystem.
cashmundy said:
If you did Odin/Heimdall to stock after flashing the SBL, and it is still messed up, its beyond me and I'd really like to know the fix. Wiping should be irrelevant after Odining to stock.
If you are getting errors in recovery when you try to wipe/format/restore, that indicates a mismatch between the kernel and the partitioning or filesystem.
Click to expand...
Click to collapse
SO the thing is I used the GLITCH kernel with vibrant build 25... I dont think I was supposed to... could that have caused the problem? maybe a voodoo problem?
There are two glitch kernel series that I know of, one for CM7 and one for CM9 and ICS (I think, not sure, that all ICS builds and CM9 use the same basic filesystem scheme).
All stock builds use a Samsung FS scheme which is different from the two above. So there are at least three mutually-incompatible families of FS+kernel pairs.
I used the CM9 kernel I think...
After the installation went fine, I got the encryption error which told me to reboot. as soon as I did, I got the Data wipe fail. Any ideas?
Encryption Error
I'm going through the same thing. I had my phone at ICS passion for months, last night I noticed my phone was in a boot load screen, but it was dimmed. I simply went and took out my battery. . maybe not the best idea, cause I'm now unable to flash back to stock.
I used odin to go back to stock, but I keep getting a boot load/reset. Nothing is happening.
If anyone has found out more on this, please let me know. Thank you so much.
tabthelab said:
I'm going through the same thing. I had my phone at ICS passion for months, last night I noticed my phone was in a boot load screen, but it was dimmed. I simply went and took out my battery. . maybe not the best idea, cause I'm now unable to flash back to stock.
I used odin to go back to stock, but I keep getting a boot load/reset. Nothing is happening.
If anyone has found out more on this, please let me know. Thank you so much.
Click to expand...
Click to collapse
If you are still able to access Clockworkmod Recovery CWM (NOT STOCK RECOVERY) then try this:
http://forum.xda-developers.com/showthread.php?t=1447303
Otherwise just give up. There is currently no fix for this bug as of now.
This is really getting out of hand ICS rom devs should put a big caution sign on their thread(s) stating the following:
WARNING THIS ROM WILL BRICK YOUR DEVICE!!!
Goodluck... in the meantime find yourself a spare phone like i did cuz you certainly ain't fixing this one.
Sent from my Galaxy Nexus using XDA
mother of god
I hope this helps you. I finally, after hours of nothing, tried to use Odin to flash to 2.2 froyo. cha ching. got in.
tar file I used here: http://forum.xda-developers.com/showthread.php?t=833024&page=49
worked for me. I hope it helps you
Hi Guys,
Sorry to bother you with this, but I'm out of ideas...
I decided to root my i9100 using this guide9.
As I was doing this, the recovery rom would reboot when using the volume buttons to navigate (only on the first "page") - This was easily worked around by using the touchscreen, but now I'm wondering if this was the start of my issues...
I applied the SU busy box installer, and got root. I installed rom manager, and noticed that it seemed to lock up when doing certain things. I put this down to CWM saying there was no official mod for the i9100.
The next day I decided to try and install a CM10.1 nightly, so I took a backup, wiped cache and data, and applied the rom and gapps.
When I rebooted, the phone wouldn't finished booting, it just sat at the initial logo screen.
After that, I tried following this recovery guide but the odin flash failed at around 80% (I retried and the same happened again).
Since then I've had difficulty getting in to recovery mode. I've tried flashing various stock roms with odin, and trying to restore with Kies.
In Kies I get as far as it conencting to the phone in download mode, but it pops up a "notice" in a foreign language - presumably Korean (and I can't copy the text to even attempt a google translation).
I tried flashing Siyah-s2-v5.0.1 to get a different recovery - that seemed to have a garbled progress bar, before hanging when I tried to wipe /data again.
When I use odin to flash a stock rom - is it supposed to restore absolutely everything? I'm not sure how I'm still getting problems if this is the case. Any ideas on what to try next?
(The current stock rom I'm try ing to use is this one)
Let me know if I'm missing any info, and thanks in advance for any help.
Using rom manager would have been the start of your problems-not the temp cwm recovery in the rooting guide.
If you can boot into download mode then I would download LP7 stock rom, disable kies and flash that with Odin.
{go back to your iphone since you are an android noob}
Thanks for the reply.
Rom manager didn't work properly for me, so I stopped using it. I used the temp cwm recovery to install the CM nightly.
I can boot in to download mode, but I've already tried an LP7 rom, - as with the others, it doesn't boot.
Any ideas on how to tell why it isn't booting? logcat doesn't seem to want to to work. Not sure if it's broken / too early in the boot process / etc
Silly Billy said:
Thanks for the reply.
Rom manager didn't work properly for me, so I stopped using it. I used the temp cwm recovery to install the CM nightly.
I can boot in to download mode, but I've already tried an LP7 rom, - as with the others, it doesn't boot.
Any ideas on how to tell why it isn't booting? logcat doesn't seem to want to to work. Not sure if it's broken / too early in the boot process / etc
Click to expand...
Click to collapse
I9100 right?
Try this:
- Download this ROM.
- Kies installed? uninstall it, re install it. Close it all up with Task manager (3 or 4 applications running).
- Flash ROM via Odin (CSC, MODEM, PHONE).
- If that doesn't fly, try another usb port & usb cable. Another PC would also be recommended.
- Repeat the process.
- Still no luck? try flashing a previous siyah version.
- No go? repeat all the above.
- Let us know how you did.
gastonw;37017081- Download this ROM.[/QUOTE said:
Thanks, I'll give it a go. (Will take a while for the file to download from hotfile...).
Are odin images for stock roms supposed to restore the stock recovery, or do they leave that alone?
Click to expand...
Click to collapse
As a matter of interest, how far did you go with Phistachios repair guide.
{go back to your iphone since you are an android noob}
Silly Billy said:
Thanks, I'll give it a go. (Will take a while for the file to download from hotfile...).
Are odin images for stock roms supposed to restore the stock recovery, or do they leave that alone?
Click to expand...
Click to collapse
Focus on getting a ROM to boot.
That ROM will install stock recovery.
gastonw said:
Let us know how you did.
Click to expand...
Click to collapse
For some reason, I can't get Odin to flash that rom - it just hands for a while at the start of data.img, before saying "Complete(Write) operation failed."
There a .pit file in the archive, although the link says not to repartition (so I didn't).
Some roms seem to get written, some don't, I'm not sure why...
theunderling said:
As a matter of interest, how far did you go with Phistachios repair guide.
Click to expand...
Click to collapse
Odin failed about 80% through flashing (step 4, after taking the ICS steps). I tried flashing the kernel afterwards, which flashed, but didn't help with my boot issues.
gastonw said:
Focus on getting a ROM to boot.
That ROM will install stock recovery.
Click to expand...
Click to collapse
Of course, I was just trying to get a better understanding of how things work - I'd settle for anything booting right now.
I was meaning how far did you go with his guide.He says (near the end) to flash a bootloader/kernel/rom.
You can try everything in his guide, but understand about the risks involved with pit and bootloaders.
{go back to your iphone since you are an android noob}
theunderling said:
I was meaning how far did you go with his guide.He says (near the end) to flash a bootloader/kernel/rom.
You can try everything in his guide, but understand about the risks involved with pit and bootloaders.
{go back to your iphone since you are an android noob}
Click to expand...
Click to collapse
He's right.
Keep trying, consider pit files & bootloaders as a last resort.
Tried everything?
Used another usb cable for the flash? tried in another PC? tried in a laptop?
Are you sure kies is all shut down?
I've read about so many people having the same issue than you, they keep on flashing as in trial & error and most times they come out winners.
GL!
gastonw said:
He's right.
Keep trying, consider pit files & bootloaders as a last resort.
Tried everything?
Used another usb cable for the flash? tried in another PC? tried in a laptop?
Are you sure kies is all shut down?
I've read about so many people having the same issue than you, they keep on flashing as in trial & error and most times they come out winners.
GL!
Click to expand...
Click to collapse
I guess I'll keep at it then.
I'd tried another cable with kies shut down. Just tried a different machine, and flashed the ROM you suggested with heimdall. It flashed without complaining (unlike odin), but I'm still getting a boot loop.
Looking at the initial recovery guide I was following - I suspect that I might've flashed the bootloader (the guide shows in bold which file goes in which box, so I probably loaded them all). Maybe this is the source of my troubles...
I also noticed that heimdall can pull data from the phone too - if I can pull and mount these, am I likely to find any useful log files?
For completeness (and anyone else who finds themselves with the same issue): It seems I hit the EMMC brick bug, which rendered some of my EMMC storage unusable.
This helpful chap came up with a workaround to partition around the dead space. (Please read the post carefully and make sure this really is your problem before flashing!)
That method will let you know what part of your memory is corrupted. It's done via recovery as far as I remember.
Did you bring your device back to life?
Sent from the little guy
gastonw said:
That method will let you know what part of your memory is corrupted. It's done via recovery as far as I remember.
Did you bring your device back to life?
Click to expand...
Click to collapse
Yes, that's right. IIRC, I flashed a working recovery with Odin, then did most of the work from adb shell.
I got my device back to life for the most part. I get the occasional hang but haven't investigated much (have since bought a Nexus 4, so not using the S2 so much).
Just thought I'd share for the next poor soul who has the same problem
I was trying to upgrade from 4.0.3 to 4.1.2 and I accidently flashed wrong CWM (v5) instead v6 and it got stuck at Samsung logo, reflashed 4.0.3 and now it gets stuck at the S logo (after start up sound).
Anyone know where I can get the multi-file old-style firmware so I can get this working again?
Thanks in advance!
Use Odin.... If You Already Usingtgen tell me Which file you tried to flash...
Sent from my iPhone using Tapatalk
otester said:
I was trying to upgrade from 4.0.3 to 4.1.2 and I accidently flashed wrong CWM (v5) instead v6 and it got stuck at Samsung logo, reflashed 4.0.3 and now it gets stuck at the S logo (after start up sound).
Anyone know where I can get the multi-file old-style firmware so I can get this working again?
Thanks in advance!
Click to expand...
Click to collapse
Here you got ICS ROMs & LS8.
That's for I9100, make sure you're packing the right model as well.
I managed to get it working again by VOLUP+Power+Menu and going into CWM and restoring from a backup.
But it is rather concerning that if I hadn't of had a backup I would be screwed right now, I use Odin and I was using the thread you posted above, however even after flashing those and even wiping user data, it still boot looped.
otester said:
I managed to get it working again by VOLUP+Power+Menu and going into CWM and restoring from a backup.
But it is rather concerning that if I hadn't of had a backup I would be screwed right now, I use Odin and I was using the thread you posted above, however even after flashing those and even wiping user data, it still boot looped.
Click to expand...
Click to collapse
hummm.........
If you can flash a back up you should be able to flash anything else. I mean, there's nothing wrong with your device.
Are you sure kies is all closed before flashing via Odin?
Try Mobile Odin to flash a stock ROM.
otester said:
I managed to get it working again by VOLUP+Power+Menu and going into CWM and restoring from a backup.
But it is rather concerning that if I hadn't of had a backup I would be screwed right now, I use Odin and I was using the thread you posted above, however even after flashing those and even wiping user data, it still boot looped.
Click to expand...
Click to collapse
Did you try follow the guide here: http://forum.xda-developers.com/showthread.php?t=1108499
It outlines what you did, only it suggests flashing a stock ROM through Odin instead of restoring a backup. Data stored on the internal memory will be lost during process, but it seems you have no way of retrieving it anyway! Give it a go with the stock ROM's link that gastonw linked you.
otester said:
I managed to get it working again by VOLUP+Power+Menu and going into CWM and restoring from a backup.
But it is rather concerning that if I hadn't of had a backup I would be screwed right now, I use Odin and I was using the thread you posted above, however even after flashing those and even wiping user data, it still boot looped.
Click to expand...
Click to collapse
Dude, your device was not "bricked" and it was of no concern. The problem was simply that you flashed a incompatible kernel.
To solve it all you needed to do was flash compatible kernel in download mode using ODIN and you would have then had correct cwm, root and rom would have booted no problem.
So I accidently F'ed my phone when I was trying to do the carrier unlock method. I installed the T-Mo radio and forgot to download the correct ROM. So I was like no biggie Ill just re-flash the correct radio. Long story short I decided to just go back to stock for the time being. Hooked up to Odin and flashed the pda-odin-att-stock.tar. Rebooted and and let it sit for a few minutes. Then booted into the stock recovery and factory reset the phone. Once it booted back up everything seems legit its just EXTREMELY SLOW. Like to the point of I cant do anything with it.
Where should I go from here. Ive been searching the forums but doesnt seem like anyone has had this exact issue. Should I try to root it again using the original pda.tar file and then load TWRP back on and try a new ROM. is there another one that includes the radio or is my radio fixed with the back to stock tar?
Any help would be appreciated. I need my phone back.
So I tried to basically root it again and installed TWRP and now its basically bricked. I can get into download mode but nothing else. And returning it to stock doesnt help now either. So ya Im stumped.
If it goes into download mode, maybe you need to re-flash TWRP or CWM?
Try This
Same thing happened to me a few days ago; if this isn't solved yet, what I did was:
Take out the battery
Keep it out for about 10 seconds
Plug it back in
now when you turn it on you should be able to get into TWRP
Flash ROM (Stock or whatever)
If you don't have a ROM when you search for it in TWRP, I think there's one last thing you could do, ADB sideload I think its called. Though I never needed to use it.
scoutsdoitbetter said:
So I tried to basically root it again and installed TWRP and now its basically bricked. I can get into download mode but nothing else. And returning it to stock doesnt help now either. So ya Im stumped.
Click to expand...
Click to collapse
If you have download mode, no brick.
Odin back to stock with .tar file.
You don't have to he rooted to flash ROM. Go to Super Everything thread and read on how to flash, root or whatever.
Read read read and understand what you are doing first
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
I was rooted on a stock rom with n9005 CWM for kitkat. I tried flashing the deodexed version for wifi tether. I didnt realize i needed odexed instead. now i am stuck on the sprint screen upon reboot. i tried using odin to reflash that rom again as well as a Cf auto root. both flashed but still stuck on the same screen upon reboot. I then tried to wipe and clear all data and cashe as well as factory reset from recovery mode. still the same issue. ANY help will be appreciated.
NOTE: i looked for 3 days for help on XDA as well as other sites and can not find anything specific to my case, or anything that will work. Please if you offer help include links as i have searched for everything i could think of.
Have you tried to get the stock tar file and use that in Odin? That would bring you back to complete stock.
is this it
i downloaded this SM-N900P_NAB_Stock_Bootloader.tar.md5 from rwilco12's android repository
is this what you are referencing? or is there a different stock file you are refering to?
is this it?
DarkManX4lf said:
Have you tried to get the stock tar file and use that in Odin? That would bring you back to complete stock.
Click to expand...
Click to collapse
i downloaded this SM-N900P_NAB_Stock_Bootloader.tar.md5 from rwilco12's android repository
is this what you are referencing? or is there a different stock file you are refering to?
I meant this one
http://forum.xda-developers.com/showthread.php?t=2712205
twrigh5 said:
i downloaded this SM-N900P_NAB_Stock_Bootloader.tar.md5 from rwilco12's android repository
is this what you are referencing? or is there a different stock file you are refering to?
Click to expand...
Click to collapse
First, let's diagnose what's wrong, to see what you need to do to fix it.
Flashing a DeOdex Mod onto an Odex ROM.
This will mess up your system files. What you'll most-likely get is a bootloop (or stuck at startup, which is where you're at). When this happens, you should be able to still access Recovery and Download Modes. This is good news! This means you have many options to fix your phone.
Possible solutions for your problem.
Restore a backup in Recovery.
The first rule when flashing ROMs/Mods is that you read and understand the thread first.
A close second rule is to make a backup before flashing anything.
I doubt that you have a backup, since that would've been the first thing you would've tried. That's ok, we just have to do a little more work to get your phone fixed.
Reflash the custom ROM in Recovery
This doesn't apply to you too much, because you weren't running a custom ROM, just a rooted stock ROM, but I think it's good for others who might have a similar problem. If you had a bootloop issue, you can always re-flash the ROM in recovery. I'd just recommend wiping data, cache, dalvik cache, and system prior to flashing the ROM.
Reflash the Stock ROM in ODIN.
This is the last-case scenario. I'd go to this thread that micmars wrote and follow his instructions very carefully. Doing this should get your phone back to stock. Then I'd re-do the rooting like you did originally (make sure you're using the kit-kat instructions.
Once you get your phone back and running (and rooted), the first thing I'd recommend is to create a nandroid backup in recovery. This will be your life-saver whenever something gets messed up.
Hope this helps!
EDIT:
I figured that I should give you a reason why the CFAutoRoot didn't work for you:
CF Auto Root only modifies certain files. It's not flashing an entire rooted ROM onto your phone, it's just selectively modifying/replacing files so that you have root access. So, when the system is messed up due to flashing a incompatible Mod, CF Auto Root is not likely to fix those issues. Only flashing a stock Rom, like DarkManX4lf suggested.
topherk said:
First, let's diagnose what's wrong, to see what you need to do to fix it.
Flashing a DeOdex Mod onto an Odex ROM.
This will mess up your system files. What you'll most-likely get is a bootloop (or stuck at startup, which is where you're at). When this happens, you should be able to still access Recovery and Download Modes. This is good news! This means you have many options to fix your phone.
Possible solutions for your problem.
Restore a backup in Recovery.
The first rule when flashing ROMs/Mods is that you read and understand the thread first.
A close second rule is to make a backup before flashing anything.
I doubt that you have a backup, since that would've been the first thing you would've tried. That's ok, we just have to do a little more work to get your phone fixed.
Reflash the custom ROM in Recovery
This doesn't apply to you too much, because you weren't running a custom ROM, just a rooted stock ROM, but I think it's good for others who might have a similar problem. If you had a bootloop issue, you can always re-flash the ROM in recovery. I'd just recommend wiping data, cache, dalvik cache, and system prior to flashing the ROM.
Reflash the Stock ROM in ODIN.
This is the last-case scenario. I'd go to this thread that micmars wrote and follow his instructions very carefully. Doing this should get your phone back to stock. Then I'd re-do the rooting like you did originally (make sure you're using the kit-kat instructions.
Once you get your phone back and running (and rooted), the first thing I'd recommend is to create a nandroid backup in recovery. This will be your life-saver whenever something gets messed up.
Hope this helps!
Click to expand...
Click to collapse
Thanks for your fast response. Im sure as soon as the file downloads i will be just fine. Thanks again!
DarkManX4lf said:
I meant this one
http://forum.xda-developers.com/showthread.php?t=2712205
Click to expand...
Click to collapse
the download isnt working right now, but maybe it will in a few. if you know of another link id appreciate that, if not then thanks again for all youre help thus far and i will just wait and hopefully it works.
Hmm the link wasn't working either earlier this week. Try posting in the thread or messaging mcmars.
twrigh5 said:
the download isnt working right now, but maybe it will in a few. if you know of another link id appreciate that, if not then thanks again for all youre help thus far and i will just wait and hopefully it works.
Click to expand...
Click to collapse
I'm able to download it at home (currently at 10%). I'll upload it to Dropbox when it's done and PM you the link.
topherk said:
I'm able to download it at home (currently at 10%). I'll upload it to Dropbox when it's done and PM you the link.
Click to expand...
Click to collapse
thanks a lot!
twrigh5 said:
thanks a lot!
Click to expand...
Click to collapse
My upload speed is atrocious, so it might be a few hours (it's a large file!)
How did the OP make out? Let us know.
topherk said:
My upload speed is atrocious, so it might be a few hours (it's a large file!)
Click to expand...
Click to collapse
it stuck on the yellow screen for like 3 minutes and i was sad.... than it worked! THANKS SO MUCH!!!! it all worked greatly. i appreciate everyones help!
Yeah. On a full stock Odin flash, things need a little longer to initialize and set up at the first boot. Even after you boot up completely, it takes awhile for everything to finish and settle down.