i'm dumb as a brick cause that's what i have...a brick. honestly, i'm not sure how i managed this. it was late at night and i've done so many things trying to fix. here's my current situation:
i followed a guide somewhere on what to do if you think you've bricked your phone. it involves a pit file, a system.tar.md5, a kernel.tar.md5, and a recovery.tar.md5.
using odin, i can successfully flash the system.tar.md5 and the kernel.tar.md5.
...but the recovery.tar.md5 fails almost immediately. i have also tried using odin to flash clockworkrecovery. it too fails almost immediately.
my phone will not power on. however, if i plug the usb cable to my computer and the phone, i get the big battery picture (like it's recharging) but the little flower-like 'busy' indicator in the middle is not moving.
Remove the battery. Hold volume down and plug the phone into your computer. It should enter download mode, enabling you to Odin back to stock.
i've already tried that. it fails at the end of the flash when odin gets to 'recovery.bin'
have you restored back to stock before with those files?
you might have a bad download. Try re-downloading your files and try with the new files.
yes, all the roms? i have on hand i have previously used before and they worked. now everything i throw at it fails when it gets to recovery.bin and the phone won't power on. when i press the power button, nothing happens. however, if i plug into my computer, i get the previously mentioned battery screen.
My suggestion is that if you're able to get into Odin, don't lose hope you should be able to get back to stock.
Also, i'm not sure what files and what thread you followed for returning to stock, but this is my GO TO thread for anytime i want a really fresh start from scratch.
http://forum.xda-developers.com/showthread.php?t=977493
use the downloads from that thread and follow the instructions. You will need to do some more work afterwards to get back to where you want, but it should get you up and running at least
P.S. - the recovery odin file in that thread is outdated i believe, so don't flash newer stuff from that recovery
for example, i have a DL09.tar.md5 file that i have used to successfully flash before. now, this is what i get in odin:
<ID:0/007> Added!!
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> Enter CS for MD5..
<ID:0/007> Check MD5.. Do not unplug the cable..
<ID:0/007> Please wait..
<ID:0/007> Checking MD5 finished Sucessfully..
<ID:0/007> Leave CS..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> cache.rfs
<ID:0/007> dbdata.rfs
<ID:0/007> factoryfs.rfs
<ID:0/007> modem.bin
<ID:0/007> recovery.bin
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
i also have a EB01_DXC.tar.md5 file that i have successfully used before. now, i get:
<ID:0/007> Added!!
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> Enter CS for MD5..
<ID:0/007> Check MD5.. Do not unplug the cable..
<ID:0/007> Please wait..
<ID:0/007> Checking MD5 finished Sucessfully..
<ID:0/007> Leave CS..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> cache.rfs
<ID:0/007> dbdata.rfs
<ID:0/007> zImage
<ID:0/007> recovery.bin
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
ok... i had weird things happen to me not too long ago and it turned out to be my USB cable.
It charges my phone but anything dealing with pc connection it bugged out
i bought a replacement online for about $3 on amazon from OEM store or something like that.
but first try to get your hands on another cable, or at the least try different USB ports on your PC, preferably the ones closest to the power supply and see if that makes a difference
djlim4 said:
My suggestion is that if you're able to get into Odin, don't lose hope you should be able to get back to stock.
Also, i'm not sure what files and what thread you followed for returning to stock, but this is my GO TO thread for anytime i want a really fresh start from scratch.
http://forum.xda-developers.com/showthread.php?t=977493
use the downloads from that thread and follow the instructions. You will need to do some more work afterwards to get back to where you want, but it should get you up and running at least
P.S. - the recovery odin file in that thread is outdated i believe, so don't flash newer stuff from that recovery
Click to expand...
Click to collapse
thanks. i already had the ci500_vzw_eb01_froyo_rel.tar.md5 file. it never worked for me. odin on win7 32-bit would stop working at the end. however, i never had that particular pit file. i'm redownloading the tar.md5 just to make sure. however, the link to the pit file in that article is no longer working. none of those 'dropbox' links have ever worked for me. i'm trying to google that specific atlas pit filename but i keep getting broken links. any pointers?
http://dl.dropbox.com/u/19519343/atlas_v2.2.pit
i just uploaded it to my db... hope it works for you
ok. i found that particular pit file somewhere else (atlas_v2.2.pit).
i'm a little confused about what you meant about the recovery files in the article you linked to. are you saying don't use the recovery files in that article?
yea, that's an old CWR
if you're just trying to get your phone up and running, that last step is not necessary... if your phone boots up initially after the first odin flash, you can proceed however you want from there
i'm going to try the first stuff first and see how that goes...but if i'm still in the same situation then, i'm tempted to go ahead and try that old odin recovery file since recovery seems to be where my issues are. doesn't seem like it could make it any worse. however, the link there doesn't work for that either. any chance you could spot me a link for that too?
p.s. really really thank you for the help!
yea no prob... i'll check back in later when i get home from work and see if you need anything else. Good luck.
http://forum.xda-developers.com/showthread.php?t=1046905
the CWR situation got kinda confusing at one point and i didnt keep up with all the little details until it sort of got ironed out... i know that the most current one is 3.x and that thread i believe has a few options to get that on. If not, look up GizmoDroid. He wrote up a very detailed post on Clockwork and the whole confusion behind it and cleared up some stuff, sorry gotta get back to work, dun have time to look for that thread.
http://dl.dropbox.com/u/19519343/cwm-recovery-ALL.tar
ok... that is the OLD CWR, but it worked for all the stuff pre-eb01 i think...
def not for comm rom or official froyo released stuff, but that's the recovery file that's in the link i first sent you.
if you want the updated clockwork, check post # 5 of this thread
http://forum.xda-developers.com/showthread.php?t=1082726
was kind of bored waiting for the ci500_eb01_froyo_rel.tar.md5 file to download. i plugged my data cable into the back of the computer and tried flashing this 'CWMRecovery_DJ05_DL09.tar.md5' file i had laying around. didn't work at first. then i tried doing it with the atlas pit file you so kindly provided. it worked! the very first time in 24hrs and 100s of tries that i've actually been able to flash anything having to do with recovery...
...but phone still wouldn't power on. i plugged it into my wall charger and tried to power on. no go. well, i left it there plugged in. about 5 minutes later, i turn around and the stock recovery screen is up! yay! even tho it was barking about being unable to mount /dev/block/st111 and /dev/block/mmcblk0p1 ...i'm still pretty excited...some kind of progress i guess
i'm beginning to think all my problems are coming from the mad-crazy flashing i was doing last night with a very low battery. intuition told me that was a bad thing but i was already having problems and my OCD wouldn't let me go to sleep without getting my phone back in working order. OCD bad. Sleep good. low battery bad. charged battery good.
hey that's good news, at least there's some progress.
Will be offline for a while, but i hope there are enough links there for you to tinker with and hopefully get everything fixed.
i'm just glad my "bricked" folder of my dropbox finally got some use
YES! using that atlas pit file, the froyo rom linked there, and somewhat charged battery i am up and running!!!!
thank you thank you thank you!
Related
Hey guys, a friend asked me to take a look at her old Samsung Fascinate because she wasn't getting any service on it. So, I took a peek and something's gone wrong. Under the About Phone section it seems the phone doesn't know a lot of things such as the Hardware version, Baseband version, phone #, MIN, PRL version, ERI version, MEID, etc.
I don't really know why it would be stuck like this, even after a hard reset and a factory wipe. The phone was never rooted or anything.
I did attempt to root it following a few different guides I found in this forum ,which I might add is not nearly as easy as it was for my Nexus S. None of my attempts worked, SuperOneClick just hangs and I tried the guide by droidstyle(?) but the links to "powerwashed 20 b3" result in a .7z that I can't successfully extract from.
So I'm kinda stuck on this and looking for a little guidance on what to try to get this thing working.
XavierBK said:
Hey guys, a friend asked me to take a look at her old Samsung Fascinate because she wasn't getting any service on it. So, I took a peek and something's gone wrong. Under the About Phone section it seems the phone doesn't know a lot of things such as the Hardware version, Baseband version, phone #, MIN, PRL version, ERI version, MEID, etc.
I don't really know why it would be stuck like this, even after a hard reset and a factory wipe. The phone was never rooted or anything.
I did attempt to root it following a few different guides I found in this forum ,which I might add is not nearly as easy as it was for my Nexus S. None of my attempts worked, SuperOneClick just hangs and I tried the guide by droidstyle(?) but the links to "powerwashed 20 b3" result in a .7z that I can't successfully extract from.
So I'm kinda stuck on this and looking for a little guidance on what to try to get this thing working.
Click to expand...
Click to collapse
You obviously didn't find droidstyle's guide because it's about as easy to follow as you're going to get. Follow his directions to go back to stock and go from there
Crawshayi said:
You obviously didn't find droidstyle's guide because it's about as easy to follow as you're going to get.
Click to expand...
Click to collapse
Not to be an ass, but...
XavierBK said:
I tried the guide by droidstyle(?) but the links to "powerwashed 20 b3" result in a .7z that I can't successfully extract from.
Click to expand...
Click to collapse
Crawshayi said:
Follow his directions to go back to stock and go from there
Click to expand...
Click to collapse
The phone still IS stock.
XavierBK said:
Not to be an ass, but...
The phone still IS stock.
Click to expand...
Click to collapse
If I were you, I'd go to DROIDSTYLES
GUUDE and ODIN back to stock( even though you say it IS stock). Try it, his guide is our BIBLE. :thumbup::thumbup:
Sent from my SCH-I500 using xda app-developers app
Okay my bad, didn't see that you mentioned droidstyle's guide already. Even so, if I were in your spot I would:
1) Odin back to stock via droidstyle's guide (yes I know you said you're already on stock, but it's better to start as fresh as can be)
2) Try a few different roms (AOKP ICS, CM10, AOKP JB, etc) and see if anything changes (personally I have been using CM10 nightlies as a daily driver and it's my current favorite)
3) Try to activate the phone via *228
Hopefully just flashing a new rom will fix this (she will LOVE you for installing a JB rom, they are simply the best the fascinate has ever been).
Note: You MUST Odin back to stock if you plan to go backwards (for example if you want to try a GB rom coming from CM10)
Well, I've been trying the "Back to stock" portion of the guide for a while now... haven't had any luck. I keep ending up with a solid color screen on the phone (blue, white, and magenta are what I've seen so far...) and Odin just seems to stall. Twice it has run the cycle but ended in FAIL. Any ideas?
As far as *228... it won't connect to anything, not even for emergency calls.
That could be caused by a bad cable or usb port... try different cables (if possible) and different usb ports. Also, I've heard uninstalling and reinstalling the samsung usb drivers can work as well
Different cables - Check
Different ports - Check
Uninstall/Reinstall drivers - check
Still a no go. I haven't gotten a solid screen color in the last 10 or so tries but they still fail. I'll post exactly what Odin reports...
Code:
<ID:0/010> Added!!
<ID:0/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> Enter CS for MD5..
<ID:0/010> Check MD5.. Do not unplug the cable..
<ID:0/010> Please wait..
<ID:0/010> Checking MD5 finished Sucessfully..
<ID:0/010> Leave CS..
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> param.lfs
<ID:0/010> Sbl.bin
<ID:0/010> boot.bin
<ID:0/010> recovery.bin
<ID:0/010> zImage
<ID:0/010> factoryfs.rfs
<ID:0/010> dbdata.rfs
<ID:0/010> cache.rfs
<ID:0/010> movinand.bin
<ID:0/010> modem.bin
<ID:0/010>
<ID:0/010> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/010> Removed!!
This still sounds like it's probably related to the cable, as I know there have been people here with problems like this and they had to really search around until finding a usb cable that would work. I wish I could help out more on that subject, but as I have never had this issue I don't have any specific recommendations. I think someone had said they finally got a Kindle Fire usb cable to work, but I'm not 100% on that.
My only other suggestions for this would be to make sure you're using the latest version of Odin and maybe try re-downloading the files in case one got corrupted somehow. Pull the sd card out too just for the heck of it while you're flashing. Maybe even try this on a different PC if you have one available?
I managed to try it on another machine with different cables and it still ended in failures. Any other ideas? I'm about to give up on this thing.
I'm out of ideas honestly. What I would do is maybe post this problem in the general Q&A forum to get more views and opinions as this might qualify as a general hardware failure
Information about my phone first off:
Phone Name: Samsung Galaxy S3
Carrier: T-Mobile
Locale: (US)
Model: SGH-T999
Update (01:38PM EST): ROMs from the list I was using were bad. Loaded a customer ROM and had no issue getting it resolved.
Update (08:54AM EST): I attempted an install and the error that came back when trying to install OTA_T999_UVALJ4_UVDLJA.zip. Said an MD5 file was missing.
Update (08:42AM EST): I'm downloading the OTA Update fro UVALJ4 - UVDLJA and will report back shortly once it finishes downloading.
Worth noting: I have backed up anything important to me from Titanium Back Up so I am not to worried about loss of data.
So I thought I'd finally jump up to Jelly Bean and keep my rooted status on my phone. I initially started out having an issue just downloading an OTA update from T-Mobile thinking my rooting was doing something to prevent it from updating. I searched and found a way to update via Kies, but lost root in the process. I attempted to use a root option which apparently wasn't the correct one and I found myself no longer booting into my phone. It displaying an error about needing to access Kies and trying to the recovery option. I ran its recovery option, but it was not seeing my device on the list so I pulled the software and drivers from my machine, rebooted and tried again to no avail, Kies was still not seeing my phone and any chance of recovering from this felt like it was going down the toilet. I still have access to the boot screen for downloading and my recovery program TWRP on it. I ran into issue attempting to install new firmware with Odin getting failed errors. I looked up said errors relating to ext4 and came up empty. I am certain I deleted something important but I am still in a position to load from my external SD card and Odin on my machine can make attempts to push firmware over, but I am at an impasse here because about most of the way in, it fails. I tried using the root firmware listed here. I downloaded T999_UVDLJA at the top of that list and only had Auto Reboot and F. Reset Time per instructions noted in that topic.
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_TMO_T999UVDLJA.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> boot.img
<ID:0/003> cache.img.ext4
<ID:0/003> NON-HLOS.bin
<ID:0/003> recovery.img
<ID:0/003> rpm.mbn
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> system.img.ext4
<ID:0/003> __XmitData_Read ..
<ID:0/003> XmitData Fail..
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
This is my first time posting, but I assure you, I spent a lot of time reading through these forums and I'm not sure where I am making a mistake at and I would appreciate any insight others have. Please let me know if there is any relevant information you think I might have left out that would be pertinent to answering this question more thoroughly and accurately.
Currently at this moment of edit, I am attempted to push T999_UVALJ4 to my phone with the same result:
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_TMO_T999UVDLJA.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> boot.img
<ID:0/003> cache.img.ext4
<ID:0/003> NON-HLOS.bin
<ID:0/003> recovery.img
<ID:0/003> rpm.mbn
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> system.img.ext4
<ID:0/003> __XmitData_Read ..
<ID:0/003> XmitData Fail..
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Re: [Q] Tried to update to Jelly Bean with my SGS3, made a mess...
Have you tried flashing a custom ROM based on stock? That way you might be able to re-install the drivers and other such important system files.
Sent from my Xperia Pro using xda app-developers app
ajabhi95 said:
Have you tried flashing a custom ROM based on stock? That way you might be able to re-install the drivers and other such important system files.
Sent from my Xperia Pro using xda app-developers app
Click to expand...
Click to collapse
What drivers? I tried a OTA, but no luck. It complained there was no MD5 file and when I got one with an MD5 file, it says it couldn't open then the zip file.
Re: [Q] Tried to update to Jelly Bean with my SGS3, made a mess...
No man I'm suggesting that you try flashing a ROM based on stock via TWRP
Sent from my Xperia Pro using xda app-developers app
ajabhi95 said:
No man I'm suggesting that you try flashing a ROM based on stock via TWRP
Sent from my Xperia Pro using xda app-developers app
Click to expand...
Click to collapse
How does a ROM vary in comparison to the firmware that Odin uses? I am assuming not, but TWRP seems to use ZIP files to do their installs instead of tar files like Odin. How am I supposed to be packaging these?
MistoRoboto said:
How does a ROM vary in comparison to the firmware that Odin uses?
Click to expand...
Click to collapse
The custom ROMS found the development sections are either based on CM10/AOSP/AOKP or Samsung's Original touchwiz. Most of these ROMS have been modified to improve stability, performance and battery life. They also come prepackaged with SuperSU (root).
Example
Download this ROM:
http://forum.xda-developers.com/showthread.php?t=1804260
Copy it to your sd-card, pop it back into s3, go to TWRP>Mount> Use External SD. Go back to the main menu and Install the ROM. This one comes with an aroma installer so you can further customize what you want to install.
illmatic24 said:
The custom ROMS found the development sections are either based on CM10/AOSP/AOKP or Samsung's Original touchwiz. Most of these ROMS have been modified to improve stability, performance and battery life. They also come prepackaged with SuperSU (root).
Example
Download this ROM:
http://forum.xda-developers.com/showthread.php?t=1804260
Copy it to your sd-card, pop it back into s3, go to TWRP>Mount> Use External SD. Go back to the main menu and Install the ROM. This one comes with an aroma installer so you can further customize what you want to install.
Click to expand...
Click to collapse
Downloading right now, will report back on the results.
MistoRoboto said:
Downloading right now, will report back on the results.
Click to expand...
Click to collapse
Good luck. :good:
illmatic24 said:
Good luck. :good:
Click to expand...
Click to collapse
illmatic24, it appears that ROM I was using was just bad. Though that makes me wonder if I will ever be able to find the original if I ever decide to sell this phone. That ROM you linked me to is amazing, there are more options there than I know what to do with.
MistoRoboto said:
illmatic24, it appears that ROM I was using was just bad. Though that makes me wonder if I will ever be able to find the original if I ever decide to sell this phone. That ROM you linked me to is amazing, there are more options there than I know what to do with.
Click to expand...
Click to collapse
I'm glad it worked. Cheers and don't forget to thank the developer of the ROM.
I am having nearly the same problem with my Samsung SPH-l710. This thread seems to indicate the OP had a bad file download. I may have a new problem.
Today, I tried the process linked here:
http://honai-android.blogspot.com/2013/05/how-to-root-galaxy-s3-sprint-sph-l710.html
I had used a similar one about a year a go and it worked great.
This time, the process failed.
The phone will no longer boot (gets stuck on the logo screen). I can still hold "vol down + home + power".
I did a search and found this thread. I re-downloaded the file hoping my download was bad, same result.
So, then I got the latest stock rom from here:
http://forum.xda-developers.com/showthread.php?t=1737859
It fails also - here is the (last part) of the output window from Odin3:
------------------------------------------------------
<ID:0/003> system.img.ext4
<ID:0/003> __Xmit Write fail
<ID:0/003> XmitData Fail..
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
------------------------------------------------------
I think it said that same thing, or similar, the first time.
It fails here for any rom I try.
What am I doing wrong? Surely all these roms aren't bad?
Thanks for any help.
Also, I have tried several brand new micro USB cables, and different USB ports, as suggested here:
http://forum.xda-developers.com/showthread.php?t=1761870
I tried one more thing - I killed Kies as suggested here:
http://forum.xda-developers.com/showthread.php?t=2082081
STILL it didn't work...
Then I moved to my windows 7 laptop - problem fixed!
I spent like 7 hours on this, and all I had to do was move to my laptop.
What a major pain...I found one more forum for a Samsung galaxy note (can't remember what version) who moved to a laptop and it worked. I will post the link if I can find that thread again.
**** Major Update: Thanks to imnuts and his alternate restore, I'm back on track and unrooted stock again.
For some reason the sboot.bin causes ODIN to fail. If this is just an isolated incident, cool, if not, this could mean getting back to stock out of necessity may be harder than we expected. Something to keep an eye on.
For reference, imnuts' post with the stock restore images:
http://forum.xda-developers.com/showthread.php?t=2040264
*** UPDATE: Still can't update with the stock image but I used the root66 stock rooted image and ODIN was able to complete. I'm able to boot the phone normally however it won't activate. I am completely lost here. ***
Was stock rooted no mods, so I flashed back to stock so I could perform the OTA update. That went fine so I installed the update.
Using Adam's new post OTA root the process didn't take so I tried a second time. The process hung and I had to do a battery pull.
Now it either boots into the Plug into Kies for emergency firmware upgrade or the Samsung Galxy Note 2 boot logo and goes no further.
Again attempting to restore to stock I flashed with Odin and here's where it gets interesting.
The process FAILS at the sboot.bin element.
*** Is it posible the OTA update made the stock recovery image incompatable? ***
Using the instructions here: http://forum.xda-developers.com/showthread.php?t=2024207
----- ODIN LOG -----
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CI605_I605VRLJB_I605VRALJB_CL414933_HWID04_HW-Rev0406_low_ship_user.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> cache.img
<ID:0/004> hidden.img
<ID:0/004> modem.bin
<ID:0/004> param.bin
<ID:0/004> recovery.img
<ID:0/004> sboot.bin
<ID:0/004> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
----- END ODIN LOG -----
ODIN and Casual see the phone and can talk to it however KIES cannot so I can't do this emergency recovery the phone is telling me to do. KIES says the device is not responding and to reboot it.
I can boot into Download Mode. I was able to get into Recovery Mode but can't now. The error in Recovery Mode was something about /system not being found.
I have no idea what to do. I have tried the process on 2 different computers. Am I Bricked Bricked?
Thanks in advance.
Under the root66 image the phone is only registering 4 gigs of available space.
Junior member, where did you find the alternate restore method?
exmeaguy said:
Junior member, where did you find the alternate restore method?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2040264
Took me a moment to find it. The only difference between the 2 is that the alternate one is without sboot.bin.
Thanks for checking. When I run the first method (3 times now) it fails at the sboot.bin step. I did download the alternate method once from the first site, but it said the file was not a PDA file. How did you get the alternate method file to work? I appreciate the help.
---------- Post added at 12:40 AM ---------- Previous post was at 12:38 AM ----------
The file extension ends with XZ, which Odin said was not a PDA file.
exmeaguy said:
Thanks for checking. When I run the first method (3 times now) it fails at the sboot.bin step. I did download the alternate method once from the first site, but it said the file was not a PDA file. How did you get the alternate method file to work? I appreciate the help.
---------- Post added at 12:40 AM ---------- Previous post was at 12:38 AM ----------
The file extension ends with XZ, which Odin said was not a PDA file.
Click to expand...
Click to collapse
It has an odd file extension .xz (perhaps meant to be .gz) so I told 7zip to extract it. resulting file ended in .tar.md5. Then it works.
Hope this helps.
Thanks Junior member I will try that.
exmeaguy said:
Thanks Junior member I will try that.
Click to expand...
Click to collapse
I'm curious why you keep calling him junior member?
Sent from my SCH-I605 (AKA NOTE 2)
Oops, sorry rdeckerr, I was looking too quickly at the name and looked at the wring line.
exmeaguy said:
Oops, sorry rdeckerr, I was looking too quickly at the name and looked at the wring line.
Click to expand...
Click to collapse
hahahaha
Wasn't sure if it was a newbie hazing kind of thing. That's funny though. No worries!
I thought I saw on one of your posts that you used root66 (same as me) and that your phone only shows 4gb of space. Did you re-root with root66 or did you use another method?
exmeaguy said:
I thought I saw on one of your posts that you used root66 (same as me) and that your phone only shows 4gb of space. Did you re-root with root66 or did you use another method?
Click to expand...
Click to collapse
Originally I was rooted with Adam Outler's casual / ODIN method (which was flawless first time round). I had tried the root66 this time just to see if it would actually take with ODIN since the stock restore kept failing. I was just desperate to find a rom that would "pass" on ODIN. I just needed to know my phone was still capable of booting fully back into android. Even if it happened to be without radio / activation capability or a wrongly registered internal storage space (which was friggin wierd, couldn't even take a screenshot).
I will re-root with Adam's process, when the kinks are out (say next weekend when I have a couple days it doesn't matter if my phone is dead . I had A.O.'s original root running for a couple weeks and it was great. The implementation was smooth, not requiring reinstalling / restoring anything. I'd backed up of course but it was one of those nice times the backups weren't necessary.
So at the moment for the sake of my job, I'm leaving it stock for the week. I just can't be without a phone for work.
rdeckerr said:
http://forum.xda-developers.com/showthread.php?t=2040264
Took me a moment to find it. The only difference between the 2 is that the alternate one is without sboot.bin.
Click to expand...
Click to collapse
Welli have the same exact issue. I am so lost its riddiculous. I have been working on this for over 20 hours and have gotten no where.
The only thing. Can add is that I attempted to root my device with the method that injects the 1 gig file in the system. Worked fine and installed cwm. Restarted and bricked with the unauthorized by verizon message. Downloaded the stock file without bootloader first and worked fine. I then tried every sinfle methodand trick I coild find to no avail.
Every time I try to install the baseline bootloader so I can unlock it fails at the end. If itry to put a full stock image on it fails at the beginning.
They both fail when tryinf to do the sboot.bin. so its obviously with that.
I need some ind of fix but no one seems to have it. I cant be doomed to a uncustomized device!
I am thinking of seeing if my verizon store will take it back and give me a fresh one so I can do the original exploit method.
It might work. Ive had the phone for less than a month.
Don't you need to flash a pit file if you're not doing so when you run into sboot.bin issues?
universexda said:
Don't you need to flash a pit file if you're not doing so when you run into sboot.bin issues?
Click to expand...
Click to collapse
No it fails at sboot because the ll4 boot loader is set to block any writing of a boot loader at all. That's why you need the alternate restore because it didn't write sboot.
Sent from my SCH-I605 using Tapatalk 2
rdeckerr said:
**** Major Update: Thanks to imnuts and his alternate restore, I'm back on track and unrooted stock again.
For some reason the sboot.bin causes ODIN to fail. If this is just an isolated incident, cool, if not, this could mean getting back to stock out of necessity may be harder than we expected. Something to keep an eye on.
For reference, imnuts' post with the stock restore images:
http://forum.xda-developers.com/showthread.php?t=2040264
*** UPDATE: Still can't update with the stock image but I used the root66 stock rooted image and ODIN was able to complete. I'm able to boot the phone normally however it won't activate. I am completely lost here. ***
Was stock rooted no mods, so I flashed back to stock so I could perform the OTA update. That went fine so I installed the update.
Using Adam's new post OTA root the process didn't take so I tried a second time. The process hung and I had to do a battery pull.
Now it either boots into the Plug into Kies for emergency firmware upgrade or the Samsung Galxy Note 2 boot logo and goes no further.
Again attempting to restore to stock I flashed with Odin and here's where it gets interesting.
The process FAILS at the sboot.bin element.
*** Is it posible the OTA update made the stock recovery image incompatable? ***
Using the instructions here: http://forum.xda-developers.com/showthread.php?t=2024207
----- ODIN LOG -----
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CI605_I605VRLJB_I605VRALJB_CL414933_HWID04_HW-Rev0406_low_ship_user.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> cache.img
<ID:0/004> hidden.img
<ID:0/004> modem.bin
<ID:0/004> param.bin
<ID:0/004> recovery.img
<ID:0/004> sboot.bin
<ID:0/004> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
----- END ODIN LOG -----
ODIN and Casual see the phone and can talk to it however KIES cannot so I can't do this emergency recovery the phone is telling me to do. KIES says the device is not responding and to reboot it.
I can boot into Download Mode. I was able to get into Recovery Mode but can't now. The error in Recovery Mode was something about /system not being found.
I have no idea what to do. I have tried the process on 2 different computers. Am I Bricked Bricked?
Thanks in advance.
Click to expand...
Click to collapse
Is there a fix for this? I have been getting the same error message via odin. Can someone post the fix or link so we can get back up and running...thanks.
kintwofan said:
No it fails at sboot because the ll4 boot loader is set to block any writing of a boot loader at all. That's why you need the alternate restore because it didn't write sboot
Click to expand...
Click to collapse
The alternate restore won't attempt to restore the bootloader to stock right?
universexda said:
The alternate restore won't attempt to restore the bootloader to stock right?
Click to expand...
Click to collapse
That's right. It will restore everything except the boot loader. It's really to restore and keep boot loader unlocked, but add an added benefit let's unbrick the new ota.
Sent from my SCH-I605 using Tapatalk 2
Same problem
I have the same problem as the original post i keep getting stuck at shoot.bin, as it is know my phone is unusable! I was wondering if their is any method to get it back to the original FW.
aka113 said:
I have the same problem as the original post i keep getting stuck at shoot.bin, as it is know my phone is unusable! I was wondering if their is any method to get it back to the original FW.
Click to expand...
Click to collapse
Did you actually read any of this thread? We got his phone working.
Sent from my SCH-I605 using Tapatalk 2
Okay, A little background quick! I just signed up for XDA because I have been lurking all day, and everyone seems to have their problems solved fairly quickly. Unfortunately none of the fixes here have helped me.
I was running KitKat for a while on my Verizon Galaxy Note 2 SCH-I605. I started having trouble with my SD card and it seemed my only route to fixing it was to root. Initially I was ignorant and used some one click solution. It certainly rooted my device, but it did not unlock my bootloader and when I tried accessing CWM Recovery my phone soft bricked. I proceeded to download ODIN and my phone's stock firmware. I flashed it and fixed my phone.
At this point I should have said goodbye to rooting, but I am a stupid stupid man. I flashed a rooted stock for my phone and it worked, but once again running CWM soft bricked me. I tried a few different things, rooting and trying to get things to work - flashing stock whenever I soft bricked again. Eventually, for whatever reason, ODIN froze when flashing STOCK. This was right around where I was giving up on the whole escapade. I an Install Firmware error and a message for KIES to repair it. I looked online, but none of the methods seemed to fix it. VZW Upgrade Assistant didn't help, and KIES won't either.
The Crux of the Problem:
I managed to get my phone in download mode and in a state of relief flashed stock to fix my phone and leave this all behind. Odin flashed, it all went well. I was very careful to follow the proper steps to ensure a proper flash of stock. Odin went through all its steps, my phone went to reboot. This time odin said PASS! before my phone finished rebooting. Now my phone is just sitting on the screen that says "Samsung GALAXY Note II". I can get to the download screen still, but I can not get to recovery to factory reset.
I know I screwed up on this, please don't tell me everything I should and shouldn't have done. I know i shouldn't have done any of this. I just want some help putting this behind me, whatever the cost. Please help me out guys!
Guys
Please help! I absolutely need my phone, and my only alternative is buying a new one. My older phones have batteries that last 5 minutes tops. Please help me here! I don't have Almost a grand for a new phone!
OMG
I got it! Fixed! After 7 hours of deep searching and experimentation I found the cure for my phone! All the things I was doing! It was so simple! Unfortunately it landed me back with KitKat Stock (Whatever, I'll deal with it), but it saved me. I flashed 4.3 Stock that I got from SamFirmware!
This is a newer firmware than I had before, but so be it! I'm so estatic!
Thank you guys! A lot of the info I found tonight was throughout the forums. No one thing here fixed my issue, but a combination of the threads here brought me to this conclusion! You guys are the bomb! Have a wonderful day!
Good job man
Sent from my SCH-I605 using Tapatalk
And your method was???? lol... I was helping my friend unroot from stock rooted with twrp, and my method was to start fresh with a stock 4.3 i found at samsfirmware. I used odin 3.09 and all went well until it finished and was boot looping (more of a flash). I tried the normal go to recovery and wipe davlik and factory reset but i cant get into recovery. So next i tried to re flash and once that didnt work i made sure my note 2 drivers were up to date. And here I am still cant flash and cant figure anything out and still cant flash. Below is what it shows for me, but yea if you could share what you did it would be so helpful!
:<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I605VRUEMJ9_I605VZWEMJ9_I605VRUEMJ9_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I'll cut to the chase, I own a Verizon Samsung Galexy S4.
It's rooted, and I used Eclipse rom, but I wanted to update to Lollipop.
So I flashed the stock SCH-I545NC5 4.4.2 and everything was fine.
Now, I used software update and it would download, restart, and give me the "failed to download/update" etc. error ( I have figured out later that this was due to me still being rooted.)
Anyway, I then tried to use Kies3 and everything was going great.
It restarted annnnd boom, I get the firmware failed to update screen with the exclamation point telling me to use emergency repair. So I did. Aaand that fails every time too... so I did some searching and finally found the SCH-I545NC5 factory rom tar.md5 file for Odin.
I have all of the drivers and everything, and I have used Odin3 before to update this phone without trouble.
But now whenever I try to flash stock it gives me this:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_VZW_I545VRUFNC5_I545VZWFNC5_1151670_REV06_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> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1
It prints all of that out in a second or less...
I then got the .pit and tried that, it will stay at getting pit for mapping for ~5 minutes or more.
And that's where I am now... I'm at my wits end, can anyone help?
Many people say that using a different USB port or a different cable might work.
GDReaper said:
Many people say that using a different USB port or a different cable might work.
Click to expand...
Click to collapse
Well, that didn't seem to work :/
Does anyone know if I would be able to take this into a Verizon store to get help? or if they would refuse due to root?
yeronix said:
Well, that didn't seem to work :/
Does anyone know if I would be able to take this into a Verizon store to get help? or if they would refuse due to root?
Click to expand...
Click to collapse
If you want your warranty rights, then they might refuse it.
GDReaper said:
If you want your warranty rights, then they might refuse it.
Click to expand...
Click to collapse
Well I don't have a warranty.. I have heard they can flash there to fix(?) stuff... would that work, would they even do that?
yeronix said:
Well I don't have a warranty.. I have heard they can flash there to fix(?) stuff... would that work, would they even do that?
Click to expand...
Click to collapse
Well, since you're paying, they will certainly try, I guess.
GDReaper said:
Well, since you're paying, they will certainly try, I guess.
Click to expand...
Click to collapse
Well alright then.
Do you know of anything else I could try? I've tried a different cable, other ports, and another computer at this point.
yeronix said:
Well alright then.
Do you know of anything else I could try? I've tried a different cable, other ports, and another computer at this point.
Click to expand...
Click to collapse
To be honest I am not very familiar with Odin problems. I just suggested what I saw on other threads.
I also stumbled upon a similar error when I tried to flash a stock rom.
Well good news is it's working! I had been flashing NC5/NK1 thinking that's what I needed. Not the case! I tried flashing the latest GOC1 and it worked!!!!
I also uninstalled Kies3 and disables my antivirus, I think that played a large part in it.
Yes, Kies messes with Odin if they both run at the same time.