Hi everyone, I'm in a bit of trouble and I am really hoping that someone can help me out.
Yesterday I was flashing some rom or kernel or something and for some reason decided to try to repartition(my stupid mistake), but Odin stayed on Do Not Turn Off Target for a few hours so I thought I had no other choice but too restart the process, so I unplugged it. Well since then I get the phone-!-Computer, but I am still able to get to the download screen.
The problem is this:
<ID:0/008> Added!!
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> cache.rfs
<ID:0/008> Complete(Write) operation failed.<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
What I have tried so far:
1) flashing stock, and other versions-same result
2) using different computers, different OS ( 7 and XP )
3) Odin v1 and v1.3
4) changing the port number
5) trying to repartition again, always hangs for hours at Do Not Turn Off Target
6) I have tried many, many times
I have found others having similar issues but most were able to fix by reflashing to stock, didnt work for me.
I would greatly appreciate any help, thank you
did you install the Samsung drivers on your computer?
First off WRONG forums, more than likely it's you don't have the drovers installed correctly or it's not recognizing the phone correctly in odin
Sent from my SGH-T959 using XDA App
Yes, I forgot to mention that but I do have the drivers installed. Over the past few days all has worked pretty well, things just went bad after i checked the repartition box and Odin hung.
stefan.buddle said:
First off WRONG forums, more than likely it's you don't have the drovers installed correctly or it's not recognizing the phone correctly in odin
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Sorry about that, I am pretty freaked out over this, didnt think to post elsewhere. If moderators can move to appropriate forum, thank you.
I am pretty sure that the drivers are correct and working, I have gone from stock to JI6 and back to stock in the last week with Odin. Also I was able to get adb to work before this happened. Thanks for the input guys.
marin 8703 said:
Sorry about that, I am pretty freaked out over this, didnt think to post elsewhere. If moderators can move to appropriate forum, thank you.
I am pretty sure that the drivers are correct and working, I have gone from stock to JI6 and back to stock in the last week with Odin. Also I was able to get adb to work before this happened. Thanks for the input guys.
Click to expand...
Click to collapse
Well repartition isn't anything to be scared of in odin. I would recommend downloading eugene373s froyo that doesnt brick, flash that via odin with repartition checked, then flash back to stock with repartition unchecked. This fixes voodoo soft bricks among other types of bricks. If using windows vista or windows 7 to open odin right click on it and run as administrator. I've heard it sometimes workes without that step, but I never got it to work without doing that.
Edit: also try redownloading the pit file, sometimes if it gets corrupted it can cause problems.
Sent from my SGH-T959 using XDA App
wildklymr said:
Well repartition isn't anything to be scared of in odin. I would recommend downloading eugene373s froyo that doesnt brick, flash that via odin with repartition checked, then flash back to stock with repartition unchecked. This fixes voodoo soft bricks among other types of bricks. If using windows vista or windows 7 to open odin right click on it and run as administrator. I've heard it sometimes workes without that step, but I never got it to work without doing that.
Edit: also try redownloading the pit file, sometimes if it gets corrupted it can cause problems.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
I will try this right now...
Tried this and get the same result. While doing this with repartition checked, Odin hangs again, also tried with repartition unchecked and receive the same result as in first post.
I also tried flashing the stock kernel and it gives pretty much the same result except it fails after zImage instead of cache.rfs. It looks like it just cant write anything. What could be wrong?
<ID:0/002> Added!!
<ID:0/002> Odin v.3 engine (ID:2)..
<ID:0/002> File analysis..
<ID:0/002> SetupConnection..
<ID:0/002> Initialzation..
<ID:0/002> Get PIT for mapping..
<ID:0/002> Firmware update start..
<ID:0/002> zImage
<ID:0/002> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
marin 8703 said:
I will try this right now...
Tried this and get the same result. While doing this with repartition checked, Odin hangs again, also tried with repartition unchecked and receive the same result as in first post.
I also tried flashing the stock kernel and it gives pretty much the same result except it fails after zImage instead of cache.rfs. It looks like it just cant write anything. What could be wrong?
Click to expand...
Click to collapse
Not sure, as far as I can tell you're doing it right. Maybe an actual malfunction. With the ota bricking a lot of phones of non modders, tmobile wont suspect one more person calling in for an exchange.
Edit: did you redownload the pit file?
Sent from my SGH-T959 using XDA App
wildklymr said:
Not sure, as far as I can tell you're doing it right. Maybe an actual malfunction. With the ota bricking a lot of phones of non modders, tmobile wont suspect one more person calling in for an exchange.
Edit: did you redownload the pit file?
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Yea i re-downloaded everything, but still no luck. I guess its not gonna happen
If nothing works out in the next day or so, I'm going to give t-mobile a try.
Thanks for all the help, if anyone has any other suggestions I'm still willing to try.
Some great news. I'm back in business with my vibrant. The issue seems to have something to do with odin, because after several tries WITHOUT closing odin it worked. Until now I would restart odin because I thought that might help but the opposite worked better.
With that and the advise that wildklymr provided I was finally able to flash back to stock.
Thank you very much for the help, really appreciate it.
Sent from my SGH-T959 using XDA App
marin 8703 said:
Some great news. I'm back in business with my vibrant. The issue seems to have something to do with odin, because after several tries WITHOUT closing odin it worked. Until now I would restart odin because I thought that might help but the opposite worked better.
With that and the advise that wildklymr provided I was finally able to flash back to stock.
Thank you very much for the help, really appreciate it.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
I just ran into the same problem as you tonight. I tried what you did with not closing odin and it worked for me too.
how many tries of not closing odin til it worked?
im actually experiencing this now on my Galaxy TAB.
lol .. multiple tries .. changing the USB ports .. and reinstalling drivers worked for me .. phew .-.
Thanks guys, had the same problem.
Had to retry without restarting ODIN and it worked.
Took 3 tries, was in a bit of a crisis as I've never seen the phone-!-Computer before
The opposite worked for me. Had to restart Odin.
I too had the same problem. Had to hit the "Start" just one more time (without restarting ODIN) to take care of it.
same for me... about three times with changing ports... nightmare ;/
Good News - Found Fix!
Keep Odin open and change USB ports, remount the PDA & flash. Hope this helped, worked for me
marin 8703 said:
Hi everyone, I'm in a bit of trouble and I am really hoping that someone can help me out.
Yesterday I was flashing some rom or kernel or something and for some reason decided to try to repartition(my stupid mistake), but Odin stayed on Do Not Turn Off Target for a few hours so I thought I had no other choice but too restart the process, so I unplugged it. Well since then I get the phone-!-Computer, but I am still able to get to the download screen.
The problem is this:
What I have tried so far:
1) flashing stock, and other versions-same result
2) using different computers, different OS ( 7 and XP )
3) Odin v1 and v1.3
4) changing the port number
5) trying to repartition again, always hangs for hours at Do Not Turn Off Target
6) I have tried many, many times
I have found others having similar issues but most were able to fix by reflashing to stock, didnt work for me.
I would greatly appreciate any help, thank you
Click to expand...
Click to collapse
Hello Buddy if you are under Windows 7 or 8 try to LUNCH Odin with Administrator
hi guys
i also have this problem
but my problem is a little different
im trying to flash stock rom 5.1.1 for my galaxy note4 (n910c) but i see the same problem as you had
but i can flash all roms that i have downloaded them before except this rom
so seems like the problem appears with some certain roms
so you have to download another rom and flash it regularly
but i didnt realize that is the rom really corrupted?
Related
Was stuck on dl01 with voodoo, bloatware frozen, rooted, and using launcherpro.
I followed the first link in that sticky: http://forum.xda-developers.com/showthread.php?t=908451
and now my phone wont boot up. when I turn it on I see the samsung logo and then it goes through this:
--Wiping data--
Formatting FOTA...
Formatting DATA...
Data Wipe failed.
Formatting Cache
Formatting DBDATA
Wipe_Data Failed.
Click to expand...
Click to collapse
then it will go back to the samsung logo and go around in circles again.
everything went fine with odin. This is what the little message window said:
<ID:0/005> Added!!
<ID:0/005> Removed!!
<ID:0/005> Added!!
<ID:0/005> Removed!!
<ID:0/005> Added!!
<ID:0/005> Removed!!
<ID:0/004> Added!!
<ID:0/004> Removed!!
<ID:0/004> Added!!
<ID:0/004> Removed!!
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> Enter CS for MD5..
<ID:0/005> Check MD5.. Do not unplug the cable..
<ID:0/005> Please wait..
<ID:0/005> Removed!!
<ID:0/005> Removed!!
<ID:0/005> Removed!!
<ID:0/005> Checking MD5 finished Sucessfully..
<ID:0/005> Leave CS..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> cache.rfs
<ID:0/005> dbdata.rfs
<ID:0/005> factoryfs.rfs
<ID:0/005> modem.bin
<ID:0/005> recovery.bin
<ID:0/005> zImage
<ID:0/005> Removed!!
<ID:0/005> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
Click to expand...
Click to collapse
I have no idea what went wrong but now i have no phone and this sux big time.
Dont panic this has happened to me.
Try this link:
http://forum.xda-developers.com/showthread.php?t=1026746
And use the method in SECTION 2: HEIMDALL
Rockstar52 said:
Dont panic this has happened to me.
Try this link:
http://forum.xda-developers.com/showthread.php?t=1026746
And use the method in SECTION 2: HEIMDALL
Click to expand...
Click to collapse
will take a look at that in a minute thanx.
but what the hell went wrong? was it something to do with voodoo?? none of the steps said to disable it or anything....
Yes you must disable VooDo before you do anything. Voodo is a real pain if your a new to flashing.
Rockstar52 said:
Yes you must disable VooDo before you do anything. Voodo is a real pain if your a new to flashing.
Click to expand...
Click to collapse
okay this tutorial is not working. I went strait to heimdall step two and I get two problems.
1) in step 3 it says "Now drop the usb drop down box and you will find an option for SAMSUNG android composite ADB device, or Samsung composite usb driver..."
I dont get that, I get "unknown device" My computer is 6 years old and i have always had problems with the usb recognizing my fascinate. It always says some type of problem and when i troubleshoot it says no drivers are installed even though i have installed them.
2)when I select the unknown device and hit install drivers i get installing drivers failed.
If you can get odin to work again use atlas_v2.2.pit to format back to rfs file-system. Use the PIT button in odin.
fupamobile said:
okay this tutorial is not working. I went strait to heimdall step two and I get two problems.
1) in step 3 it says "Now drop the usb drop down box and you will find an option for SAMSUNG android composite ADB device, or Samsung composite usb driver..."
I dont get that, I get "unknown device" My computer is 6 years old and i have always had problems with the usb recognizing my fascinate. It always says some type of problem and when i troubleshoot it says no drivers are installed even though i have installed them.
2)when I select the unknown device and hit install drivers i get installing drivers failed.
Click to expand...
Click to collapse
Definitely try to Odin the Pit 2.2 that DMT suggested.
Here's a link to a giude that should help get you back to stock as it isn't as intimidating for some as the un-bricking one: http://forum.xda-developers.com/showthread.php?t=1124391
And if that fails might I suggest trying it on a more up to date PC, maybe your issues have come from that if your pc never recognized the phone properly.
Nnneeeedd heellp nowwww!!!!!!!!!!
Go to the development stickies and go to the 2 one...how to go from
Cm7 to anything else...that's not the official title but it its something like that. The links for the eb01. tar, the atlas 2.2pit and newer odin versions are all in the first post.
I use odin 1.7..which version are you on? I'm sure if you use odin 1.7 or newer and put the 2.2 atlas pit file in the pit section with repartition checked and put the official vzw eb01 .tar in the pda section and run it..that will get your phone back in stock unrooted bloated form but at least your phone will work and then you can go and flash what you like..but I would try a different odin version and the eb01 with the pit file and you will get your phone back
Sent from my SCH-I500 using XDA App
Are you willing to just go back to stock or start all over again?
Put the phone in Download mode
Remove battery
plug usb into PC
plug usb into phone [battery still out]
push [and hold] volume button down
Should see yellow triangle [once you see this you can let go off the volume]
Use Odin then to flash the Stock image to your phone.
Link to ODIN v1.3 http://www.mediafire.com/download.php?r5izui8a3trpo85
Download the ED01 stock rom
Put it into the PDA section of Odin and flash and Boom Back to stock!
Stock ED01 http://www.multiupload.com/6ET46L1ATD
Nothing will be deleted off of your sd card
xwhofarted said:
Are you willing to just go back to stock or start all over again?
Put the phone in Download mode
Remove battery
plug usb into PC
plug usb into phone [battery still out]
push [and hold] volume button down
Should see yellow triangle [once you see this you can let go off the volume]
Use Odin then to flash the Stock image to your phone.
Link to ODIN v1.3 http://www.mediafire.com/download.php?r5izui8a3trpo85
Download the ED01 stock rom
Put it into the PDA section of Odin and flash and Boom Back to stock!
Stock ED01 http://www.multiupload.com/6ET46L1ATD
Nothing will be deleted off of your sd card
Click to expand...
Click to collapse
Well I got the drivers installed and i was on to step 5 but heimdall.exe wont open.
I think I will just do it this way i guess. this is all because of stupid voodoo
Voodoo used to be a p.i.t.a but it really isn't that hard now with the newer cwm supporting both voodoo and non voodoo, the steps myself and the person who posted above me are describing direction for odin..not heimdall.I don't know much about heimdall or how to use it but you can get your phone back and working using odin
Use the link in junkboy0's reply..follow the directions in the first post.
fupamobile said:
Well I got the drivers installed and i was on to step 5 but heimdall.exe wont open.
I think I will just do it this way i guess. this is all because of stupid voodoo
Click to expand...
Click to collapse
Sent from my SCH-I500 using XDA App
efan450 said:
Go to the development stickies and go to the 2 one...how to go from
Cm7 to anything else...that's not the official title but it its something like that. The links for the eb01. tar, the atlas 2.2pit and newer odin versions are all in the first post.
I use odin 1.7..which version are you on? I'm sure if you use odin 1.7 or newer and put the 2.2 atlas pit file in the pit section with repartition checked and put the official vzw eb01 .tar in the pda section and run it..that will get your phone back in stock unrooted bloated form but at least your phone will work and then you can go and flash what you like..but I would try a different odin version and the eb01 with the pit file and you will get your phone back
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
what should i do about voodoo though?
i am going to do this as two of you have suggested:http://forum.xda-developers.com/showthread.php?t=1124391
but i dunno about voodoo. just ignore it for now? It addresses it in that post but i dont undestand what it is saying
using Odin and the stock image it will over write the voodoo
I have never used the heimdall way. I have been stuck in boot loops many times and ODIN has always saved the day!
As long as you can get to Download mode your phone can be fixed
fupamobile said:
what should i do about voodoo though?
i am going to do this as two of you have suggested:http://forum.xda-developers.com/showthread.php?t=1124391
but i dunno about voodoo. just ignore it for now? It addresses it in that post but i dont undestand what it is saying
Click to expand...
Click to collapse
Yup ignore voodoo for now...when you use the atlas2.2 file in the pit section and the eb01.tar in the pda section...if repartition isn't checked make sure you check it...run it and it will bring you to stock with voodoo removed and then you can flash whatever you wanted from there...if you get stuck,p.m.me and I'll send you files with complete directions but it would have to wait till I get home from work tonight..don't panic we'll get you up and running again!
Get the newest odin, eb01. tar, and atlas 2.2pit file, and I would grab
One of the newer recovery.tar files too so when your back to stock you can flash a working recovery if you want to flash some rom after all is fixed....i recommend the 3-30 fix all recovery, but just make sure you get a tar file so you can odin it after your phone is fixed.
Sent from my SCH-I500 using XDA App
xwhofarted said:
using Odin and the stock image it will over write the voodoo
I have never used the heimdall way. I have been stuck in boot loops many times and ODIN has always saved the day!
As long as you can get to Download mode your phone can be fixed
Click to expand...
Click to collapse
interesting.
in the q/a section there is a sticky on how to go stock. not only does it not tell me how to address voodoo(why i am here) but it tells me to go to DL09 and them OTA to eb01.
the method you guys are posting seems much more logical. it sends me strait to froyo and doesnt brick my phone because it just overwrites voodoo. correct?
once voodoo is "overwritten", is it gone off my phone? if not, should i address it at all after this tutorial? froyo is downloading right now
xwhofarted said:
using Odin and the stock image it will over write the voodoo
I have never used the heimdall way. I have been stuck in boot loops many times and ODIN has always saved the day!
As long as you can get to Download mode your phone can be fixed
Click to expand...
Click to collapse
I concur...soft bricked, boot looped, many many times and never used heimdall either
Sent from my SCH-I500 using XDA App
fupamobile said:
interesting.
in the q/a section there is a sticky on how to go stock. not only does it not tell me how to address voodoo(why i am here) but it tells me to go to DL09 and them OTA to eb01.
the method you guys are posting seems much more logical. it sends me strait to froyo and doesnt brick my phone because it just overwrites voodoo. correct?
once voodoo is "overwritten", is it gone off my phone? if not, should i address it at all after this tutorial? froyo is downloading right now
Click to expand...
Click to collapse
Correct voodoo will be gone but you can just flash another voodoo kernel later and you can flash voodoo over voodoo just not voodoo to non voodoo with out removing it
Sent from my SCH-I500 using XDA App
efan450 said:
Yup ignore voodoo for now...when you use the atlas2.2 file in the pit section and the eb01.tar in the pda section...if repartition isn't checked make sure you check it...run it and it will bring you to stock with voodoo removed and then you can flash whatever you wanted from there...if you get stuck,p.m.me and I'll send you files with complete directions but it would have to wait till I get home from work tonight..don't panic we'll get you up and running again!
Get the newest odin, eb01. tar, and atlas 2.2pit file, and I would grab
One of the newer recovery.tar files too so when your back to stock you can flash a working recovery if you want to flash some rom after all is fixed....i recommend the 3-30 fix all recovery, but just make sure you get a tar file so you can odin it after your phone is fixed.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
okay. I am just following what that tutorial says to do. I dont even know what a working recovery is. I never even had a rom on this thing. I have realized I am in way over my head here and have spent too much time dealing with my phone.
really all i want is to be up to date, have root, debinged/bloat, launcherpro so i dont have to use stupid touchwiz. thats basically all i need. maybe in the future i might get other stuff. but for now i think it will suit me best to just rely on verizon/samsung to keep my phone up to date and then just re root everytime. seems much simpler and safer
fupamobile said:
okay. I am just following what that tutorial says to do. I dont even know what a working recovery is. I never even had a rom on this thing. I have realized I am in way over my head here and have spent too much time dealing with my phone.
really all i want is to be up to date, have root, debinged/bloat, launcherpro so i dont have to use stupid touchwiz. thats basically all i need. maybe in the future i might get other stuff. but for now i think it will suit me best to just rely on verizon/samsung to keep my phone up to date and then just re root everytime. seems much simpler and safer
Click to expand...
Click to collapse
Recovery..clock work mod...or cwm is the recovery program you will use to install custom rom, kernels, or zip files...I will send you a p.m.later with files, info, and instructions and you can read over it and decide if you want to do it now or wait till you're a lil more familiar with the process..but for now odin the pit atlas 2.2 file and eb01 and you will be stock and be able to use launcher pro.
Sent from my SCH-I500 using XDA App
Problem:
My GSII was running normally on the latest RootBox version, Dorimax Kernel 7.46, I was using SD Maid Pro, to Optimize database, I didn't actually knew what the function do, but it has to do something with improving the performance of my phone, and i already used it before many times.
But this time it was stuck for like 10 minutes while optimizing database so i turned off my phone and turned it on again, and BAM, stuck on samsung logo, I couldn't access recovery, only download mode.
Steps I already took:
1. Flashed Dorimanx Kernel 7.45 .tar with Odin -> Odin Stuck at NAND Write Start
2. Flashed Stock Roms, ICS (I9100XXLPH and I9100XWLPG) and JB (I9100XWLS8_I9100FOPLS3) -> Odin Stuck at NAND Write Start (Failed)
3. Flashed it on a different Laptop (x86 and x64) -> Same results.
Here is the log from ODIN:
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100_XEU_I9100XWLPG_PRE-ROOTED_I9100XXLPX_I9100XEULP5.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> boot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Step that I'm thinking of taking:
I suspected then that I had to go nasty and flash PIT and re-partition.
Basically this is the last solution for hopeless flashaholics, so based on these threads (1) (2) I downloaded the pit zip, but it contained lots of patched pit files, and each for different brick area.
The problem I cannot access recovery mode so I can't know the bricked part. I read in the thread that if I don't know i have to try each one (92 pit files).
And that was a solution for the MMC_CAP_ERASE brick, which actually is not present if i'm using Dorimanx Kernel or JB AOSP ROMs.
So now I'm not sure if flashing pit will be the correct solution, I was starting to think of flashing a bootloader as in thread
So fellow flashaholics, before I mess up with pit files, and f*ck my phone more, any more suggestions?
(Btw I don't have yellow triangle, so basically I can send it to repairing service or whatever, but actually staying without a smartphone for at least a week is quite impossible for me, if you know what I mean)
Download and flash with odin 1.3.
Sent from my GT-I9100 using xda app-developers app
Pit files should be regarded as a last resort.
Try all odin versions possible
Try all usb ports.
Try all usb cables.
Try all pc/laptops you can.
Try flashing various ROMs.
Try flashing various kernels via Odin.
Uninstall & reinstall Kies.
Sent from the little guy
Download and flash with odin 1.3.
Click to expand...
Click to collapse
Odin 1.3? I did try to flash with Odin 1.85 but didn't want to go older than that. But anyway I'm not loosing anything, so i'll give it a shot.
Pit files should be regarded as a last resort.
Try all odin versions possible
Try all usb ports.
Try all usb cables.
Try all pc/laptops you can.
Try flashing various ROMs.
Try flashing various kernels via Odin.
Uninstall & reinstall Kies.
Click to expand...
Click to collapse
Thanks for the advice, but the problem that it's just stuck at NAND bla bla bla, and not continuing, even thought I tried multiple ROMs, and Kernels, and Laptops. I already uninstalled Kies, it's useless anyway, I reinstalled USB drivers, basically i exploited every possible solution other than flashing a PIT file. But I'll keep trying.
silv3rfox said:
Odin 1.3? I did try to flash with Odin 1.85 but didn't want to go older than that. But anyway I'm not loosing anything, so i'll give it a shot.
Thanks for the advice, but the problem that it's just stuck at NAND bla bla bla, and not continuing, even thought I tried multiple ROMs, and Kernels, and Laptops. I already uninstalled Kies, it's useless anyway, I reinstalled USB drivers, basically i exploited every possible solution other than flashing a PIT file. But I'll keep trying.
Click to expand...
Click to collapse
I have exact same problem today, still trying to recover the NAND
I had the exact problem with two phones. I tried everything but with no luck. Than I downloaded odin 1.3 and that solved my problem. Try odin 1.3 you don't lose anything.
Sent from my GT-I9100 using xda app-developers app
GreatVortex said:
I had the exact problem with two phones. I tried everything but with no luck. Than I downloaded odin 1.3 and that solved my problem. Try odin 1.3 you don't lose anything.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
OK I'll try Odin 1.3
If it doesn't fly...keep trying with another versions.
Sent from the little guy
Nope. Doesn't work.
I can get into download mode
I cannot get into recovery mode
I can charge the battery if I connect the phone to PC/charger
All attempts stuck at NAND write
Is this motherboard problem?
Any help?
Flash siyah v5.
Sent from the little guy
Did try.
Siyah stuck at zimage.
I tried almost everything all day long. Is there any hard core way to reset this phone?
I read about .PIT file method to reset, but looks like no guide to do it here. Can you help me please?
kopiko09 said:
Did try.
Siyah stuck at zimage.
I tried almost everything all day long. Is there any hard core way to reset this phone?
I read about .PIT file method to reset, but looks like no guide to do it here. Can you help me please?
Click to expand...
Click to collapse
There are, but you really need to know what you're doing.
Are you sure you had tried everything and then tried it again?
If, and only if, YES, we can start talking about pit files.
Sent from the little guy
OK I'll try everything again once more. If still fail I'll let you know tomorrow. Thanks
Promise me (and your device) you'll try it ALL out again.
Sent from the little guy
OK I'll try everything again once more. If still fail I'll let you know tomorrow. Thanks
Click to expand...
Click to collapse
I tried to flash different ROMs with ODIN 1.3, it didn't get past the boot.bin, i retried with Odin 3.07, but still same old problem stuck at NAND Write bla bla bla!
Hope you'll get something, that'll give me some hope to retry again!
I had the exact problem with two phones. I tried everything but with no luck. Than I downloaded odin 1.3 and that solved my problem. Try odin 1.3 you don't lose anything.
Click to expand...
Click to collapse
What did you flash with Odin 1.3?
I flashed this: http://www.hotfile.com/dl/190226031/b214985/I9100XWLS8_I9100FOPLS3_FOP.zip.html
In Odin the only thing selected was auto reboot. All other things were unselected(unthicked).
This is the Odin that i used: View attachment Odin3_v1.3.rar
Sry for my english.
P.S. If you have kies installed Uninstall it before flash or make sure all kies process are stoped in task manager.
I'm trying with Odin 3.07 now
try all odins you can get your hands on.
Sent from the little guy
OK, one thing is sure. Odin 1.3 does NOT work. It stucks earlier than other version of odin. Not even get to NAND write step
To start with: Odin stuck's at flashing.
Details:
Model: Samsung Galaxy S 2 I9100Т, almost 2 years have past since it was purchased.
History of ROMs used: Almost after the purchase it was flashed with the latest nightly Cyanogenmod 9+ something that is 4.0.1 Android.
But the ROM was for normal SGSII, not T, although it worked good for something about a year. It was flashed with stable Cyanogen 9.1, also not for the T. With that ROM it worked another 7-8 months and suddenly got a problem with "Apps not responding at all". So, first it was factory reseted via CWM recovery, and after that, i was asked to get a new OS for it. So i flashed nightly Cyanogen 10.1xx. All ROMs, that were used with this device, were downloaded from the Cyanogenmod "official site".
Case History: After a month of doing well with 10.1 nightly, during a downloading or even installation process of a casual, but a 3D game, with a size of 20+ megaz, it suddenly got stuck and stoped responding to any input. It was rebooted by taking out the battery, w8ng for a few mins, and putting it back. After that it started to get stuck, right on the loading screen, repeatedly. I tried wiping cache via recovery: it was "doing something" for 5 mins and then saying: "Kernal Panic". Then i tried factory reset option, and the result was the same. Also, installing a new ROM via install zip recovery feature, that ended with the same message, also after a long w8ng time.
Not so successful Reanimation history: While trying to flash official service 1 file NEE (Nordic Contries) firmware 4.0.4 with Odin 1.85, it got stuck almost right at the start, while it was trying to flash a "cache" part, the process status bar havent appeared on the device even after 20 minutes of wating time. So i decided that it should be disconnected from the PC for good. That led to a standart soft brick, with a picture: "mobile - ! - PC " and a message, asking to flash something, that actually works with Kies. Download mode is still availible but recovery isn't anymore.
I tried flashing with Odin 1.85 and 3.04, and even 3.07. I tried flashing quite an amount of offcial firmwares: 2.3.3 и 4.0.3 и 4.0.4. и 4.1.2, both 1 file and 3 file versions. All the same: it kept getting stuck almost at the start, with a message or process, depending on a firmware version, but always same for the same ROM, and as i said before the process bar havent appeared on a phone even for a moment during all those attempts.
Notice: The PC, that was used to Odin-flash this device, a month before was able to flash another SGSII and did it perfectly.
Thanks in advance to everyone, who may help me in this "case", and sorry for not so good english.
Chellout said:
To start with: Odin stucks on flashing on this device.
Details:
Model: Samsung Galaxy S 2 I9100Т, almost 2 years past since it was purchased.
History of ROMs used: Almost after the purchase it was flashed with the latest nighlty Cyanogenmod 9+ something that is 4.0.1 Android.
But the ROM was for normal SGSII not T, although it was working good for something around a year. It was flashed stable Cyanogen 9.1 then, also not for the T, With this it worked another 7-8 months and suddenly got a problem with Apps not responding at all. So first it was factory reseted via CWM recovery, and after i was asked to get a new OS for it. So i flashed nighly Cyanogen 10.1xx. All ROMs that were used with this device were downloaded from the Cyanogenmod "official site".
Case History: After a month of going well with 10.1 nighly, during a downloading or even installation process of a casual but a 3D game with a size of 20+ megaz, it suddenly got stuck and stop responding to any input. It was rebooted by taking out the battery w8 for a few mins and putting it back. After that it started to get stuck right on the loading screen repeatedly. I tried wiping cache via recovery it was "doing something" for 5 mins and then saying: Kernal Panic. Then i tried factory reset option and the result was the same. Also installing a new ROM via install zip recovery feature ended with the same message after a long w8ng time.
Not so successful Reanimation history: While trying to flash official service 1 file NEE (Nordic Contries) firmware 4.0.4 with Odin 1.85, NEE, it got almost right at the start while it tryied to flash a "cache" part, the process status bar havent even appear on the device even after 20 minutes of w8ng time. So i decided that it should be disconnetcted from the PC for good. That led to a standart soft brick with a picture : "mobile - ! - PC " and a message asking to flash something that actually works with Kies. Download mode is still availible but recovery isn't anymore.
I tried flashing with Odin 1.85 and 3.04 and even 3.07. I tried flashing quite an ammount of offcial firmwares: 2.3.3 и 4.0.3 и 4.0.4. и 4.1.2, both 1 file and 3 file versions, it was all almost the same: it got stuck almost at the start with a message or process depending on a firmwave version but always same for the same ROMs, and as i said before the process bar havent appeared on a phone even for a moment during all those attempts.
Notice: The PC that was used to Odin-flash this device, a moth before it was able to flash another SGSII and done it perfectly.
Thanks in advance to everyone, who may help me in this "case", and sorry for not so good english.
Click to expand...
Click to collapse
Siyah? No siyah? How come no siyah?
Flash siyah.
gastonw said:
Siyah? No siyah? How come no siyah?
Flash siyah.
Click to expand...
Click to collapse
I'll gladly do it, once i'm able to get something to work on this device. Thanks.
Chellout said:
I'll gladly do it, once i'm able to get something to work on this device. Thanks.
Click to expand...
Click to collapse
Forced download screen? Flash it with odin.
gastonw said:
Forced download screen? Flash it with odin.
Click to expand...
Click to collapse
Apparently, i guess y havent read the whole post.
just uninstall the drivers , restart pc and then reinstall the drivers on the pc and c if that works :/ or this http://forum.xda-developers.com/showthread.php?t=1457458
It sounds to me that you have a hardware failure and there is nothing you can do. If your rom was somehow messed up, then your recovery should have been fine. Try returning it to stock as much as possible and send the device to samsung. Try to atleast reset your download counter.
Chellout said:
Apparently, i guess y havent read the whole post.
Click to expand...
Click to collapse
Kid, noticed tha pc logo with the exclamation sign in the middle?
Thats forced download.
Sent from the little guy
gastonw said:
Kid, noticed tha pc logo with the exclamation sign in the middle?
Thats forced download.
Sent from the little guy
Click to expand...
Click to collapse
Yes, i can easlly enter Download mode aka Odin mode, from this with 3 fingers method. But as i mentioned in the first post, Odin doesn't want to flash anything, it stops right at the start.
If you can provide me a link to the cure, ill be greateful.
There's no magic link.
How many odin versions have you tried?
Kies applications closed?
Sent from the little guy
gastonw said:
There's no magic link.
How many odin versions have you tried?
Kies applications closed?
Sent from the little guy
Click to expand...
Click to collapse
1.85, 3.04. 3.07. and 4.42 none of them were able to get the process bar moving.
Kies uninstalled even, tho i have the drivers.
Install kies, then close it all up.
Post the log to see where odin fails / stops
Sent from the little guy
gastonw said:
Install kies, then close it all up.
Post the log to see where odin fails / stops
Sent from the little guy
Click to expand...
Click to collapse
Done with Kies. What exactly you think i should try to flash with Odin to provide you the output?
And btw, the last working OS was custom JB by cyanogenmod.
Chellout said:
Done with Kies. What exactly you think i should try to flash with Odin to provide you the output?
And btw, the last working OS was custom JB by cyanogenmod.
Click to expand...
Click to collapse
Yes, remember cm from OP.
You could flash LSJ (google "jelly bean test firmware s2 sammobile") so you can get the odin fail log up on the screen.
Flash only csc, code and modem.
Sent from the little guy
gastonw said:
Yes, remember cm from OP.
You could flash LSJ (google "jelly bean test firmware s2 sammobile") so you can get the odin fail log up on the screen.
Flash only csc, code and modem.
Sent from the little guy
Click to expand...
Click to collapse
Okey, so im trying to flash this http://www.sammobile.com/2012/11/15/i9100xxlsj-–-galaxy-s-ii-android-4-1-2-jelly-bean-test-firmware/
with the provided 3.04 Odin.
Gona post the resut soon.
Chellout said:
Okey, so im trying to flash this http://www.sammobile.com/2012/11/15/i9100xxlsj-–-galaxy-s-ii-android-4-1-2-jelly-bean-test-firmware/
with the provided 3.04 Odin.
Gona post the resut soon.
Click to expand...
Click to collapse
Try odin 1.85 also, it's know to work better sometimes.
Mistaken.
Chellout said:
Mistaken.
Click to expand...
Click to collapse
What is that you are flashing there?
EDIT: Lol
gastonw said:
What is that you are flashing there?
EDIT: Lol
Click to expand...
Click to collapse
Now i flashed it, though result is the same, sadly almost same as it was during all my previous tries:
<ID:0/007> Removed!!
<ID:0/007> Added!!
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> boot.bin
<ID:0/007> NAND Write Start!!
<ID:0/007> data.img
And here it is... for anothe 10 minutes, roughly
And the screenshot here:
Chellout said:
Now i flashed it, though result is the same, sadly almost same as it was during all my previous tries:
<ID:0/007> Removed!!
<ID:0/007> Added!!
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> boot.bin
<ID:0/007> NAND Write Start!!
<ID:0/007> data.img
And here it is... for anothe 10 minutes, roughly
And the screenshot here:
Click to expand...
Click to collapse
Ok, so it get stucked there in all usb ports?
Sure looks like nand corruption.
Hey All,
I definitely hard bricked my phone, I've tried everything on XDA, every Odin, every stock and rooted rom in combination with different Pit's, baselines etc.. etc..
Not sure if I am rooted anymore or unrooted since I have installed so many Rom's.. My screen gets stuck on Samsung Logo, I can only get into Download Mode (Odin Mode) and I am sure of that.
I started off trying to install a custom rom, things went bad, after it all went bad i realized my mistakes reading, upon reading XDA.
My question for all you wonderful people on XDA is.. what do i do now with a paper weight? Do i keep trying and Beat it till it works, or replace the motherboard? & if i replace the mobo can i simply get an AT&T Mobo on this Verizon? (I have at&t, its an unlocked Verizon phone).. & where do I go to do it? (cheapest place please, totally not rich)
more info:
can't partition in odin/ i always encounter some sort of error in the middle of trying to do anything with odin.. I am only successful when i install the 66root file, and if I select the 'T Flash' option in odin it sometimes works with other roms.. but no matter what I still get stuck on the Logo Screen
list of what i have tried:
http://galaxynote2root.com/galaxy-n...o-install-custom-rom-on-rooted-galaxy-note-2/
http://www.androidayos.com/2013/04/...-note-2-sch-i605-original-firmware-stock-rom/
http://forum.xda-developers.com/showthread.php?p=39299305
http://forum.xda-developers.com/showthread.php?t=2118348
http://forum.xda-developers.com/showthread.php?t=2024207
& MUCH MORE.
I know i am dumb for how I went about doing all this so please keep it informational... thank you all!!
gnit0 said:
Hey All,
I definitely hard bricked my phone, I've tried everything on XDA, every Odin, every stock and rooted rom in combination with different Pit's, baselines etc.. etc..
Not sure if I am rooted anymore or unrooted since I have installed so many Rom's.. My screen gets stuck on Samsung Logo, I can only get into Download Mode (Odin Mode) and I am sure of that.
I started off trying to install a custom rom, things went bad, after it all went bad i realized my mistakes reading, upon reading XDA.
My question for all you wonderful people on XDA is.. what do i do now with a paper weight? Do i keep trying and Beat it till it works, or replace the motherboard? & if i replace the mobo can i simply get an AT&T Mobo on this Verizon? (I have at&t, its an unlocked Verizon phone).. & where do I go to do it? (cheapest place please, totally not rich)
more info:
can't partition in odin/ i always encounter some sort of error in the middle of trying to do anything with odin.. I am only successful when i install the 66root file, and if I select the 'T Flash' option in odin it sometimes works with other roms.. but no matter what I still get stuck on the Logo Screen
list of what i have tried:
http://galaxynote2root.com/galaxy-n...o-install-custom-rom-on-rooted-galaxy-note-2/
http://www.androidayos.com/2013/04/...-note-2-sch-i605-original-firmware-stock-rom/
http://forum.xda-developers.com/showthread.php?p=39299305
http://forum.xda-developers.com/showthread.php?t=2118348
http://forum.xda-developers.com/showthread.php?t=2024207
& MUCH MORE.
I know i am dumb for how I went about doing all this so please keep it informational... thank you all!!
Click to expand...
Click to collapse
If you can still access Download Mode then you arent truly hard bricked.
If you havent tried it you need to try flashing the PIT file. There is also the "alternative recovery method" that you should try. I think flashing the PIT file, which I believe is in one of Adams casual posts, will get you back on track but I might be wrong. Hopefully someone else will stroll through and be abke to give you a bit more help than me.
As for the first 2 urls, NEVER EVER EVER use root methods that are not on XDA. Not many people have experience with them and they could be potentially dangerous.
You also need to specify exactly what all you have tried out of those threads instead of just linking the thread.
Sent from my SCH-I605 using XDA Premium HD app
Alternative Retry
shangrila500 said:
If you can still access Download Mode then you arent truly hard bricked.
If you havent tried it you need to try flashing the PIT file. There is also the "alternative recovery method" that you should try. I think flashing the PIT file, which I believe is in one of Adams casual posts, will get you back on track but I might be wrong. Hopefully someone else will stroll through and be abke to give you a bit more help than me.
As for the first 2 urls, NEVER EVER EVER use root methods that are not on XDA. Not many people have experience with them and they could be potentially dangerous.
You also need to specify exactly what all you have tried out of those threads instead of just linking the thread.
Sent from my SCH-I605 using XDA Premium HD app
Click to expand...
Click to collapse
I have tried the alternative recovery method, but i went ahead and tried again. Stuck at "Get PIT for mapping.."
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I605_VRALJB_Restore.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..
USB
gnit0 said:
I have tried the alternative recovery method, but i went ahead and tried again. Stuck at "Get PIT for mapping.."
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I605_VRALJB_Restore.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..
Click to expand...
Click to collapse
I've tried different USB Ports, Chords and Machines (win 7 64bit, win 7 32bit & XP)
gnit0 said:
I have tried the alternative recovery method, but i went ahead and tried again. Stuck at "Get PIT for mapping.."
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I605_VRALJB_Restore.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..
Click to expand...
Click to collapse
I had this problem.
And I just used another computer and it worked fine.
Sent from my SCH-I605 using xda app-developers app
barrackOBAMA said:
I had this problem.
And I just used another computer and it worked fine.
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
If the PIT and alternate recovery method don't work or wouldn't hurt to try it on a different computer as barrackOBAMA suggests. If that doesn't work we can always try something else. The most important thing is to stay calm. These phones are incredibly hard to hard brick, and as long as you can get into Download Mode it can usually be fixed. It might be a long process but it'll be free where if you bought a motherboard it would cost you more money.
Sent from my SCH-I605 using XDA Premium HD app
shangrila500 said:
If the PIT and alternate recovery method don't work or wouldn't hurt to try it on a different computer as barrackOBAMA suggests. If that doesn't work we can always try something else. The most important thing is to stay calm. These phones are incredibly hard to hard brick, and as long as you can get into Download Mode it can usually be fixed. It might be a long process but it'll be free where if you bought a motherboard it would cost you more money.
Sent from my SCH-I605 using XDA Premium HD app
Click to expand...
Click to collapse
thanks guys, I really do appreciate the help and I have no problem testing any method thrown my way, if you guys were to tell me to throw it at a pigeon, I probably would do it. I have tried on 3 different VM's.. not sure if thats really considered a "different machine" or not.. I am in the middle of restoring my old dell laptop to try it on that.
shangrila500 said:
If the PIT and alternate recovery method don't work or wouldn't hurt to try it on a different computer as barrackOBAMA suggests. If that doesn't work we can always try something else. The most important thing is to stay calm. These phones are incredibly hard to hard brick, and as long as you can get into Download Mode it can usually be fixed. It might be a long process but it'll be free where if you bought a motherboard it would cost you more money.
Sent from my SCH-I605 using XDA Premium HD app
Click to expand...
Click to collapse
ah dude.. tried it on a different PC and still stuck on this motherless error <ID:0/004> Get PIT for mapping..
Honestly think I did something to the emmc or whatever it is. I don't know if I'm violating TOS but I will donate 50 bux to whomever can help. If saying I will donate is a violation please forgive.
gnit0 said:
Honestly think I did something to the emmc or whatever it is. I don't know if I'm violating TOS but I will donate 50 bux to whomever can help. If saying I will donate is a violation please forgive.
Click to expand...
Click to collapse
Lemme ask you this, do you have Kies installed? My friend had the same issue with his N2 where it would freeze in Odin and do nothing else at all after it said getting PIT for mapping. He finally had to bring it over to me and use my computer to root it, his is the AT&T version, and even though he had Kies installed he couldn't get the phone to connect right. He finally had to install Kies and all the drivers and them reinstall Kies first then the standalone drivers that were linked and after that everything worked. That may be worth a shot. I also know a lot of people have issues using VM machines and Windows 8, it seems everything works smoothest on Windows 7.
As for boring the emmc, you may have but like I said earlier it's really hard to screw this phone up so I really think it is just an issue with VM ware or possibly you haven't flashed the right file that it needs yet. We'll figure it out though hopefully, it will just take some trial and error.
Have you tried the alternate restore method? If not I will link it, it seems to fix a lot of people's phones when nothing else will.
Honestly I think it is something with the computers you're using and the drivers being wonky as usual.
Sent from my SCH-I605 using XDA Premium HD app
shangrila500 said:
Lemme ask you this, do you have Kies installed? My friend had the same issue with his N2 where it would freeze in Odin and do nothing else at all after it said getting PIT for mapping. He finally had to bring it over to me and use my computer to root it, his is the AT&T version, and even though he had Kies installed he couldn't get the phone to connect right. He finally had to install Kies and all the drivers and them reinstall Kies first then the standalone drivers that were linked and after that everything worked. That may be worth a shot. I also know a lot of people have issues using VM machines and Windows 8, it seems everything works smoothest on Windows 7.
As for boring the emmc, you may have but like I said earlier it's really hard to screw this phone up so I really think it is just an issue with VM ware or possibly you haven't flashed the right file that it needs yet. We'll figure it out though hopefully, it will just take some trial and error.
Have you tried the alternate restore method? If not I will link it, it seems to fix a lot of people's phones when nothing else will.
Honestly I think it is something with the computers you're using and the drivers being wonky as usual.
Sent from my SCH-I605 using XDA Premium HD app
Click to expand...
Click to collapse
Hey Shangrila, appreciate you helping me, I am going to try and completely uninstall all drivers for Samsung, uninstall kies, install drivers and test, if it doesn't work, re-install kies and drivers. I have tried to restore with and without kies, and all over again. I will try again but this time i will completely wipe all drivers and re-install note 2 drivers
May I ask what the first step that you did was that bricked it? You are stuck on the samsung logo flashing?
meat614 said:
May I ask what the first step that you did was that bricked it? You are stuck on the samsung logo flashing?
Click to expand...
Click to collapse
It started with a trade on craigslist. Traded my at&t iPhin 5 (i love you man insider) for this Verizon sch-i605 unlocked. I had no idea if it were able to accept custom roms or not, but i do know it was rooted (used supersu) i am a highly tech savvy guy but i don't know **** about android. I did a factory restore from setting, I then tried to install casual, downloaded it and ran it but it kept erroring so i then went and tried to upload a mod on sdcard and went to recovery mode wipe device and cache.. after that it stopped working. tried to install all sorts of roms, boot loaders, pits and what not. now all i get is error after error, either nand error or getting pit mapping halt. for some reason root66 is the only rom that is successfull but without pit file. and not sure what "T Flash" is on Odin, but some roms work while that is checked.
some roms i have tried:
CI605_I605VRLJB_I605VRALJB_CL414933_HWID04_HW_Rev0406_low_ship_user.tar.md5
I605_VRALJB_Restore.tar.md5
cwm6-root-note2.tar
root66_VZW_stock_system.tar.md5
BootloaderBaseline2.tar.md5
TWRP2430VZW.tar.md5
gnit0 said:
Hey Shangrila, appreciate you helping me, I am going to try and completely uninstall all drivers for Samsung, uninstall kies, install drivers and test, if it doesn't work, re-install kies and drivers. I have tried to restore with and without kies, and all over again. I will try again but this time i will completely wipe all drivers and re-install note 2 drivers
Click to expand...
Click to collapse
If I can help I most definitely will. This sounds exactly like a driver issue thoug because it isnt able to communicate with the phone yo get the PIT for mapping. That was the same exact thing that happened with my friends phone on his laptop when I was setting everything up and showing him how to use Odin to root his phone, it would show up on a port and act like it would work but it would freeze every single damn time on the getting PIT for mapping part and wouldn't do anything else until I unplugged the phone and then it would say failed.
The main thing that helped him was wiping the drivers completely though and then just reinstalling Kies, I think he installed the other drivers after that but i can remember for sure, and it finally worked perfectly. I only have Kies on my laptop, I dont have the second set of drivers, but if you cant get it to work with just Kies try installing the other set and then test it again. You may even have to launch Kies for it to install the drivers correctly, it's been so long I can't remember that part either. Just install Kies first without the other set of drivers, launch Kies and make sure everything is set up with Kies, and see if that works. If not then install the 2nd set and try to use Odin again.
Also what OS are you doing all this on? If it's Windows 7 then it may take a little playing with the drivers to get it right. Also which version of Odin are you using? I cant get the newest version to work correctly on my laptop so that could also be part of it. Have you tried the alternative restore method? While I am 99% site it is the drivers it is always best to cover all bases.
Sent from my SCH-I605 using XDA Premium HD app
---------- Post added at 11:08 PM ---------- Previous post was at 11:06 PM ----------
gnit0 said:
It started with a trade on craigslist. Traded my at&t iPhin 5 (i love you man insider) for this Verizon sch-i605 unlocked. I had no idea if it were able to accept custom roms or not, but i do know it was rooted (used supersu) i am a highly tech savvy guy but i don't know **** about android. I did a factory restore from setting, I then tried to install casual, downloaded it and ran it but it kept erroring so i then went and tried to upload a mod on sdcard and went to recovery mode wipe device and cache.. after that it stopped working. tried to install all sorts of roms, boot loaders, pits and what not. now all i get is error after error, either nand error or getting pit mapping halt. for some reason root66 is the only rom that is successfull but without pit file. and not sure what "T Flash" is on Odin, but some roms work while that is checked.
some roms i have tried:
CI605_I605VRLJB_I605VRALJB_CL414933_HWID04_HW_Rev0406_low_ship_user.tar.md5
I605_VRALJB_Restore.tar.md5
cwm6-root-note2.tar
root66_VZW_stock_system.tar.md5
BootloaderBaseline2.tar.md5
TWRP2430VZW.tar.md5
Click to expand...
Click to collapse
Watch what you check in Odin. You are ONLY supposed to check what is told in the guide, NONE OTHER! Thats a really good way to mess things up and make it harder to fix!
Can you boot into recovery? If so is there a nandroid you could try restoring?
Sent from my SCH-I605 using XDA Premium HD app
aug ttaham
i have been trying with these below none stop
Odin - 3.07
PDA - I605_VRALJB_Restore.tar.md5.xz
PIT - sch-i605-16gb.pit
none stop
gnit0 said:
i have been trying with these below none stop
Odin - 3.07
PDA - I605_VRALJB_Restore.tar.md5.xz
PIT - sch-i605-16gb.pit
none stop
Click to expand...
Click to collapse
What do you mean by none stop? Did you mean non stop? Or they aren't stopping? Sorry for asking, just a little late and I had a long day.
Sent from my SCH-I605 using XDA Premium HD app
shangrila500 said:
What do you mean by none stop? Did you mean non stop? Or they aren't stopping? Sorry for asking, just a little late and I had a long day.
Sent from my SCH-I605 using XDA Premium HD app
Click to expand...
Click to collapse
I meant i have been trying those none stop, ive tried to restore with those files atleast 10 times..
I tried to uninstall drivers and kies and then restoring but i got nothing, then tried with newly installed kies... and nothing as well.. arggg
still stuck on Get Pit Mapping
& no, i cannot get into recovery... just stays at the samsung gn 2 logo screen, and if i hold up button home and power, it just shuts off and on again... even if i release power button when i see the logo... stays at logo
gnit0 said:
i have been trying with these below none stop
Odin - 3.07
PDA - I605_VRALJB_Restore.tar.md5.xz
PIT - sch-i605-16gb.pit
none stop
Click to expand...
Click to collapse
Also this is the alternative method I was talking about:
http://forum.xda-developers.com/showthread.php?t=2040264
In the first post there is a link that says alternative restore, it has a different sboot so it will leave you unlocked. It works a lot when the PIT doesnt, its worth a shot. I still think its drivers but im throwing everything I can out so maybe you'll be able to use your phone, I know how it is to not have one to use until you can fix yours.
Sent from my SCH-I605 using XDA Premium HD app
---------- Post added at 11:27 PM ---------- Previous post was at 11:24 PM ----------
gnit0 said:
I meant i have been trying those none stop, ive tried to restore with those files atleast 10 times..
I tried to uninstall drivers and kies and then restoring but i got nothing, then tried with newly installed kies... and nothing as well.. arggg
still stuck on Get Pit Mapping
& no, i cannot get into recovery... just stays at the samsung gn 2 logo screen, and if i hold up button home and power, it just shuts off and on again... even if i release power button when i see the logo... stays at logo
Click to expand...
Click to collapse
What OS are you using? Are you using VMware right now? It still sounds like a driver issue, is there any chance you have a different computer with Windows 7 installed that you could try if the alternative restore method I linked a minute ago doesn't work?
Sent from my SCH-I605 using XDA Premium HD app
shangrila500 said:
Also this is the alternative method I was talking about:
http://forum.xda-developers.com/showthread.php?t=2040264
In the first post there is a link that says alternative restore, it has a different sboot so it will leave you unlocked. It works a lot when the PIT doesnt, its worth a shot. I still think its drivers but im throwing everything I can out so maybe you'll be able to use your phone, I know how it is to not have one to use until you can fix yours.
Sent from my SCH-I605 using XDA Premium HD app
Click to expand...
Click to collapse
that is the exact file i have been trying with odin 3.0.7 and the pit file.
shangrila500 said:
What OS are you using? Are you using VMware right now? It still sounds like a driver issue, is there any chance you have a different computer with Windows 7 installed that you could try if the alternative restore method I linked a minute ago doesn't work?
Sent from my SCH-I605 using XDA Premium HD app
Click to expand...
Click to collapse
I am trying on a local windows 7 64bit machine.. i have 16gb ram, amd fx 8120 8-core processor, and a ssd hybrid.. my mobo is a asus m5a97.. stopped using the VM's
Hello all,
I want to preface everything that while I know a bit about rooting and messing with the stock status of android phones, I'm still generally a newbie at this.
Last night I started experiencing problems with my phone. I was using it normally until it ran out of battery while in a call, but I figured this happened in the past so it shouldn't be a problem. I plugged it in, however it wouldn't boot up. The CM11.2 loading screen just wouldn't stop spinning. Booting into recovery and download mode was working fine, but I couldn't get into the OS. Since I wanted for a long time to upgrade my Jellybean to Lollipop (and found this thread http://forum.xda-developers.com/gal.../rom-cyanogenmod-12-1-nightly-builds-t3147661 just last night), I decided it's time.
I boot into recovery and try and backup my data, but as soon as I click, the device freezes. Fast forward 5 attempts later with 3 different SD cards, it would still do the same thing. Already annoyed, I decide just to factory reset/wipe data, in order to flash the new Nightly and Gapps. As soon as I click, same thing happens, the CWM freezes and I have to manually reboot.
I figured the CWM is corrupt and I started searching on forums what to do. Tried flashing a new CWM with Odin (specifically this) but now I can't boot into recovery anymore, only download mode. I'm scared of doing more on my own. The current state of the phone is that it stays frozen at the "Samsung Galaxy S2" screen, the one with the yellow triangle w/ "!". Could you please help?
@Ricksis
Personally what I would try next is flashing a stock rom with odin and starting again. Although I suspect you might have hardware issues. A lot of S2's are dying these days.
If you can find someone who can lend you a battery(I know, not too many S2's out there any more!) try that, as it is possible the battery is causing these issues. Good luck
Edit: Remember to flash stock pit(if you flash stock rom) if you have repatitioned previously
noppy22 said:
@Ricksis
Personally what I would try next is flashing a stock rom with odin and starting again. Although I suspect you might have hardware issues. A lot of S2's are dying these days.
If you can find someone who can lend you a battery(I know, not too many S2's out there any more!) try that, as it is possible the battery is causing these issues. Good luck
Edit: Remember to flash stock pit(if you flash stock rom) if you have repatitioned previously
Click to expand...
Click to collapse
I don't have problems with the battery generally. It lasts for 8-12h on a normal day (which I think it's a lot for a 3 year old 2000mAh battery), and almost 3 days with the phone in standby. It just happened that last evening I was stuck in a call and away from a plug. Sadly, like you said, noone that I know still has an S2 around.
As for the stock rom, is there one that you would recommend? I'm really reluctant to do more steps on my own. I have not repartitioned and I tried to stay away of PIT flashes since I have also read last night about how they should be the last resort, because they have a high chance of bricking the device.
I tried getting a stock firmware from Sammobile, specifically firmwares/confirm/14909/I9100XWLSU_I9100OROLS5_ORO/. I tried flashing it, and this happened:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100XWMS2_I9100BULS3_I9100VDFLSF_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> cache.img
<ID:0/003> factoryfs.img
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Ricksis said:
I don't have problems with the battery generally. It lasts for 8-12h on a normal day (which I think it's a lot for a 3 year old 2000mAh battery), and almost 3 days with the phone in standby. It just happened that last evening I was stuck in a call and away from a plug. Sadly, like you said, noone that I know still has an S2 around.
As for the stock rom, is there one that you would recommend? I'm really reluctant to do more steps on my own. I have not repartitioned and I tried to stay away of PIT flashes since I have also read last night about how they should be the last resort, because they have a high chance of bricking the device.
Click to expand...
Click to collapse
A battery can die suddenly. I recommend trying to rule it out first as the problems you describe can be because of a battery that has come to the end, and if it is the case you may not get past it.
Anyway get a stock rom for your region from
sammobile.com
or http://androidfirmwares.net/Home/sgs2
or http://www.tsar3000.com/Joomla/inde...alaxy-sii-firmware&catid=55:samsung&Itemid=82
noppy22 said:
A battery can die suddenly. I recommend trying to rule it out first as the problems you describe can be because of a battery that has come to the end, and if it is the case you may not get past it.
Click to expand...
Click to collapse
I tried flashing 3 different stock roms, they all failed like at 3%. I found a friend with an S2, going to his place later today. What should I do/expect from his battery ?
Ricksis said:
I tried flashing 3 different stock roms, they all failed like at 3%. I found a friend with an S2, going to his place later today. What should I do/expect from his battery ?
Click to expand...
Click to collapse
I'm not sure you can expect anything. It's just a common problem. See if you can get it fully charged and try the stock rom with odin again. Also check out this guide
As I said it seems like there is a hardware problem, the battery is just where I would start. Once you can rule that out you can look elsewhere
From your description, your odin flash got past the 'nand write' stage which is where most odin flashes fail.....from that point of view, things are a lot more positive than for other users facing odin flash fails.....
Can you confirm that your device is the international variant? It's just that in your OP you mention flashing a cwm package that you found on the Verizon S2 forum.
http://i.imgur.com/rVnFwJM.jpg
keithross39 said:
From your description, your odin flash got past the 'nand write' stage which is where most odin flashes fail.....from that point of view, things are a lot more positive than for other users facing odin flash fails.....
Can you confirm that your device is the international variant? It's just that in your OP you mention flashing a cwm package that you found on the Verizon S2 forum.
Click to expand...
Click to collapse
I tried with multiple stock roms, but they all fail in the same stage. I bought the phone carrier free, and its code is GT-I9100 (no extra letters afterwards like a lot of S2s have). I also found another solution, but it stopped after NAND WRITE start.
Hopper8 said:
Another option for i9100
If you have an i9100, probably the best option to flash is to flash 4.1.2 JellyBean leak. Huge thanks to It_ler for providing the file after it was lost during the shutdown of hosting site hotfile.com and re-hosting on his dev-host, and for keithross39 for re-hosting the file on his storage. Download it here: or here. This is a 3-part firmware. It will wipe your device as it flashes, and in many cases this extra wipe while flashing contributes to a successful flash. To set this file up in Odin (as it is 3 parts): PDA = CODE_I9100XXLSJ.tar, PHONE = MODEM_I9100XXLS6.tar, and CSC = CSC_HOME_OXX_I9100OXXLS1.tar. As usual, do not tick 'repartition'.
Click to expand...
Click to collapse
I also found this http://forum.xda-developers.com/chef-central/android/nand-write-start-fail-odin-soluction-t2851096
That 3 part firmware mentioned in your quoted text has a better chance of successful flash than a regular firmware as it formats and repartitions the device during the flash.....normal firmwares just overwrite what is already on the device.
I've had a quick look at the thread you linked to, and from what I understand, the OP is providing a way to flash the firmware partition by partition......
In theory, this is a good solution, but unfortunately, I don't know enough about the firmware structure or about the odin flashing process to be able to meaningfully pass comment on that method.......My uninformed instinct tells me 'why not'......but my practical, logical side tells me 'caution'....
http://i.imgur.com/rVnFwJM.jpg
keithross39 said:
That 3 part firmware mentioned in your quoted text has a better chance of successful flash than a regular firmware as it formats and repartitions the device during the flash.....normal firmwares just overwrite what is already on the device.
Click to expand...
Click to collapse
In Odin 3.07, everything but PDA is greyed out for me. I donwloaded v1.85 and tried the 3 part thing: Odin freezes at NAND Write Start!!, and as for my phone, there is no blue progress bar appearing on the screen in the first place while i'm in download mode.
Just tried the pit file solution as well:
<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> Re-Partition operation failed.
Things to check for odin flashing.......
1) firewall disabled
2) antivirus disabled
2) all Kies processes killed (use task manager)
4) run Odin as administrator
5) only use main board USB sockets (pc/laptop side)
6) make sure Samsung drivers correctly installed.
7) windows 8 & 10 may not allow odin to operate correctly.
8) Use official Samsung usb lead.....no cheap s**te off eBay
9) try all usb ports on pc/laptop
10) try different cables
11) try different PC's/Laptops.......
12) do the whole procedure multiple times.....Odin flashing is a bit like playing the lottery......it may not work the first 9 or 19 times, but for some reason, on the 10 or 20th attempt, it does.......
The only thing that will 'win the day' is perseverance......
http://i.imgur.com/rVnFwJM.jpg
---------- Post added at 11:33 PM ---------- Previous post was at 11:22 PM ----------
There is (possibly) a plan B.......
Are you able to get into recovery?
If you are, you *could* try flashing PhilZ recovery which will root your phone.....then you can give flashing a custom rom a try.......
You possibly still could go that route even without recovery......by (maybe) Odin flashing a custom kernel .tar and then flashing a custom rom......
(I'm not talking about the latest CM12. ....but an older KK or JB based rom.....they're far more stable and complete than the LP based roms.....)
http://i.imgur.com/rVnFwJM.jpg
I had a busy week and only could try some solutions today. Unfortunately, I think they ended up with the hardbrick of my phone, as I am not able to turn it on anymore, not even in download mode.
Are you *sure* that it's not just a failed battery.....you mentioned previously, that you thought there might be an issue with it.....
http://i.imgur.com/rVnFwJM.jpg
keithross39 said:
Are you *sure* that it's not just a failed battery.....you mentioned previously, that you thought there might be an issue with it.....
Click to expand...
Click to collapse
I'm not sure, but I kinda fiddled enough with ODIN for just the battery to be the cause. Of course I am no expert, but I see no connection between the battery failing and all the other problems: cwm11.2 not wiping cache/dalvik or performing factory resets, the option to only boot in download mode later, etc. When I plug the phone to the USB port, nothing happens anymore.
Sooooo... RIP phone? ...
Ricksis said:
Sooooo... RIP phone? ...
Click to expand...
Click to collapse
If you are sure there's nothing else you can try........
But, even though it's an old device, it's still going to cost money to replace it....
You mentioned that odin failed to recognise it......
Another *possibly* would be the USB socket......
It would account for the lack of odin recognition *AND* a dead (uncharged) battery which could lead you to assume the whole phone is dead.
The port may have been ok at the start of your recovery attempts, but they do wear out (especially on older devices simply due to wear and tear) and by the last attempt it could have failed......
The part costs pocket change on ebay and is relatively easy to replace....I've done it myself......
Here's a guide I wrote on replacing the board......
http://forum.xda-developers.com/showthread.php?t=2335961
http://i.imgur.com/rVnFwJM.jpg