Related
so yeah i got my first replacement after the first time this happened... i tried flashing krylon360's rom with odin but got a fail at factory.rfs. keep in mind i am in no way shape or form a noob with odin, i have brought many of my buddies' devices back to life, but for some reason even though i use a USB jig ( which works in my captivate and personally tested and working on the SGS4g before the unrecoverable soft brick) any help please i dont want to have to send it back to t-mobile again... they already charge 10bucks just for shipping.
muleman said:
so yeah i got my first replacement after the first time this happened... i tried flashing krylon360's rom with odin but got a fail at factory.rfs. keep in mind i am in no way shape or form a noob with odin, i have brought many of my buddies' devices back to life, but for some reason even though i use a USB jig ( which works in my captivate and personally tested and working on the SGS4g before the unrecoverable soft brick) any help please i dont want to have to send it back to t-mobile again... they already charge 10bucks just for shipping.
Click to expand...
Click to collapse
Hmm I'd say if the USB jig didn't work, you're not soft bricked. That's a hard brick.
What kind of USB jig are you using?
Was it a ROM or a kernel you flashed? which one, version etc.?
Jig - verified WORKING before the flash attempt
tried to flash [ROM-ODIN]T959VUVKB5 Stock + Root By: krylon360
new sgs4g
new USB cable
opened Odin first, set file
plugged in phone got a good port connection
clicked "Start"
failed at factory.rfs
phone--!--comp screen
unresponsive to JIG
donation rewards for anybody that can help! lol this is depressing, my old captivate isnt this sensitive and has been through hell and back, but this SGS4g.... im dissappointed in.
Uninstall all the drivers for the phone make sure you have the right ones also, and try plugging it into a usb 2.0 slot then run it again, this seemed to work for me. I ran into the same issue I plugged in my jig but it gave me a black screen, but odin recognized it and I flashedthe kd1 update and it was fixed. Hope this helps
muleman said:
Jig - verified WORKING before the flash attempt
tried to flash [ROM-ODIN]T959VUVKB5 Stock + Root By: krylon360
new sgs4g
new USB cable
opened Odin first, set file
plugged in phone got a good port connection
clicked "Start"
failed at factory.rfs
phone--!--comp screen
unresponsive to JIG
Click to expand...
Click to collapse
hold your horses... I got some news for you.
you can flash at that screen
try flashing mine again, or try white's ODIN image.
Along with what krylon said, maybe a bad download, try download file again
Sent from my SGH-T959V using XDA Premium App
will do thanks guys, ill try it tonight and let ya know how it goes for me.
i still dont get how odin gets a connection but the phone itself cannot with the jig... not logical but hey in the process of flashing now
krylon360 said:
hold your horses... I got some news for you.
you can flash at that screen
try flashing mine again, or try white's ODIN image.
Click to expand...
Click to collapse
youre the man.... Thanks much
muleman said:
i still dont get how odin gets a connection but the phone itself cannot with the jig... not logical but hey in the process of flashing now
Click to expand...
Click to collapse
Heimdall works at that same warning screen too. I've done it on my SGS4G.
I am confused..
sgyee said:
Heimdall works at that same warning screen too. I've done it on my SGS4G.
Click to expand...
Click to collapse
If the computer is not recognizing the phone being plugged in, how is ODIN going to be able to process? I don't know if mine SGS4G is irrepairable but when I plug it in to the computer, it will not even show up on device manager. The drivers have been installed in the past and I have used ODIN before.
When I try using ODIN now it won't work since it won't recognize the phone.
I have used JIG and simply will not buzz. It's pretty much as dead as if the phone is not even on.
Any help guys??
amishraa said:
If the computer is not recognizing the phone being plugged in, how is ODIN going to be able to process? I don't know if mine SGS4G is irrepairable but when I plug it in to the computer, it will not even show up on device manager. The drivers have been installed in the past and I have used ODIN before.
When I try using ODIN now it won't work since it won't recognize the phone.
I have used JIG and simply will not buzz. It's pretty much as dead as if the phone is not even on.
Any help guys??
Click to expand...
Click to collapse
If its currently in the state which I'm assuming..
-won't turn on, no sign of life period...
-plugging it in the wall charger won't even show the green battery status...
-won't get recognized when plugged into pc (or odin)...
-all combinations of buttons and battery pulling+usb cable plugging does nothing...
Yea I think its safe to say it went to a land far far away just like my friend's phone and only Samsung can revive it now.. Because I remember reading all the stories how everyone brought theres back to life so easily with the button combos or the jig usage, but those phones all at least showed a sign of life with that cable screen. But if its pitch black like I'm assuming then...
Same here. The jig didn't seem to work - I still got the cell + comp but odin worked anyway and reflashed stock. It's probably better to run Odin off a desktop if you have one.
That screen scared the holy hell out of me a couple of days ago. I ended up having to re-install the samsung drivers for windows 7 and then odin picked the phone right up. The reason I *knew* the phone was recoverable from that screen was simple, though:
I read the screen. It wouldn't be telling you to try something in Kies if you couldn't do anything at that screen. So, I just kept ****ing around trying different things until it worked.
*I* have personally noticed that that screen tends to come up when you accidentally or inadvertently select "Re-Partition" on a rom/image that's not setup for it, or if for any reason your phone gets disconnected or powered off during the flashing process.
That screen scared the holy hell out of me a couple of days ago. I ended up having to re-install the samsung drivers for windows 7 and then odin picked the phone right up. The reason I *knew* the phone was recoverable from that screen was simple, though:
I read the screen. It wouldn't be telling you to try something in Kies if you couldn't do anything at that screen. So, I just kept ****ing around trying different things until it worked.
*I* have personally noticed that that screen tends to come up when you accidentally or inadvertently select "Re-Partition" on a rom/image that's not setup for it, or if for any reason your phone gets disconnected or powered off during the flashing process.
Click to expand...
Click to collapse
I second this. I have been running into this screen while trying to install root from the 2.3.4 leak. I have had black screen, fuzzy screen, random pixel screen. In most cases I have been able recognize the phone using odin. A few of the key steps that I have used to get the phone recognizable in odin are:
1. If the computer says "usb not recognized" when initially plugging in the phone, uplug it and plug it back in. Most of the time when I do this the phone is recognized as samsung device.
1b: If odin now recognizes the phone after running through step 1 I will try to flash the files again. it will usually fail after trying to load the flash files on the first try. I have to mess around with this process a few times and I can usually get a successful flash.
2. I had an case when having to deal with this problem yesterday. I was running through steps 1,1b and not having success. Odin was hanging, (I forget which step). I let it sit for about 10 minutes and was still hanging. I unplugged the phone with odin still hanging pulled battery, powered on, plugged back in. Odin, which was still open and still trying to connect, continued its already started process after plugging it back in!!! This was an accident to still have the odin running and trying to connect, but after reconnecting the phone it successfully flashed!
*I* have personally noticed that that screen tends to come up when you accidentally or inadvertently select "Re-Partition" on a rom/image that's not setup for it, or if for any reason your phone gets disconnected or powered off during the flashing process.
Click to expand...
Click to collapse
These kind of observations are especially helpful! I can concur that I get the same <phone..!..pc> error, when odin tries to flash and gets a write fail, however, I do not have the "re-partition" option set. I then have to run through my previously mentioned steps to try to get a successful flash.
My question is what can i do to keep odin from failing to write when flashing?? I have only been using PDA packages, with the exception of using discrete packages (pit,csc,phone,pda) when loading the 2.3.4 rom leak.
It seems like the flashing write error in odin in causing the <phone..!..pc> error quite often with different flash processes. Does anyone have a solution to what might be causing this write error and what can be done to prevent this whole cycle? If so I sticky or new thread might be useful for other users. It has caused to have to warranty my first phone, urrrg!
Scariest feeling ever........ Not seeing your phone come up on Odin.
Sent from my SGH-T959V using XDA Premium App
Woops ahahahha. Was talkin to my friend. SOrry!
fvnktion said:
I second this. I have been running into this screen while trying to install root from the 2.3.4 leak. I have had black screen, fuzzy screen, random pixel screen. ..... [cut] ......
Click to expand...
Click to collapse
I had the same issue yesterday, when I tried to flash KD1 vanilla (stock) ROM
using ODIN, it failed the first 4 seconds, it boots into fuzzy looking screen and
that's it, every time I tried to boot it the fuzzy screen fades away to pitch black.
there is 2 possibilities that messed up the whole thing for me:
1) Bad ROM.. (i.e, can't be used with ODIN) although some members said it works
but don't know if there anything special to do before hand, if I want to downgrade.
2) Samsung Kies' fault, I installed just right before I used ODIN, and told me my
device is not registered.. hmm.
It could be both cases, but I suspect Kies the culprit, I had to uninstall it, and
uninstall the drivers came with it, installed the drivers found here in these forums,
and Odin recognized a COM port, although black screen on the phone, flashed
to KH1 and I am back to business. phew..
GB is awesome, but I can't stand the weak WIFI issue even with the latest KH1
I have to stand 3 feet away from my router to get a solid signal, with froyo
vanilla rom, I was able to connect like 50 feet away. but that's another problem
not for this thread.
Heh funny thing I read today in some thread, there is a conflict between Kies and
Odin after the incident happened. my fault for not reading a lot, jumping the gun
almost cost me the phone :/
OK, Ive been without my note for a whole day and been researching wht to do nonstop
What happened to me was that, since i had updated to official kitkat, i soon developed a taste for lollipop, and went on to try out different ROMs and finally settled on to crDroid
So it was one of those days where everything was going well until the note stopped opening apps for like a minute then showd a black screen and then all of a sudden restarted
Since this was a Sammy i thought it would get back up again.... But no, even a 5 minute didnt wake this beast up, it remained stuck at the boot logo, i.e, Samasung Galaxy Note 10.1
Im like ok ill go on do a factory reset and wipe cache and all, upon trying to accesss the recovery after the boot logo the recovery kinda opens then gets back at boot logo, a black screen shows up then turns on to be a full brightness black screen for a sec then goes back
I can access the download mode and can odin things but they fail every single time.
I have tried to odin a recovery and a stock recovery so far and they show a nand write error
i also have tried to PIT but they get stuck at get PIT for mapping
I have also tried all versions of odin tried changing a USB Port and the wire with no success
So is there any hope for my NOTE??
Please i need help its urgent
Osama Abedin said:
OK, Ive been without my note for a whole day and been researching wht to do nonstop
What happened to me was that, since i had updated to official kitkat, i soon developed a taste for lollipop, and went on to try out different ROMs and finally settled on to crDroid
So it was one of those days where everything was going well until the note stopped opening apps for like a minute then showd a black screen and then all of a sudden restarted
Since this was a Sammy i thought it would get back up again.... But no, even a 5 minute didnt wake this beast up, it remained stuck at the boot logo, i.e, Samasung Galaxy Note 10.1
Im like ok ill go on do a factory reset and wipe cache and all, upon trying to accesss the recovery after the boot logo the recovery kinda opens then gets back at boot logo, a black screen shows up then turns on to be a full brightness black screen for a sec then goes back
I can access the download mode and can odin things but they fail every single time.
I have tried to odin a recovery and a stock recovery so far and they show a nand write error
i also have tried to PIT but they get stuck at get PIT for mapping
I have also tried all versions of odin tried changing a USB Port and the wire with no success
So is there any hope for my NOTE??
Please i need help its urgent
Click to expand...
Click to collapse
is it rooted ?
i have the same problem from 2 months and i am finally got that i must replace the motherboard
Sounds like its written its last, flash is dead.
Since you are able to enter in download mode there is hope. Trying to flash recovery which doesn't match the firmware version will always fail. So, try flashing some of the base firmwares which will return everything to stock. I was in your situation few months ago and managed to flash Android Revolution HD 4.4.2 after first flashing stock firmware via odin. I got my 4.4.2 base firmware from "sammobile.com", firmware section (sorry i don't have enough posts for using links).
I remember i tried flashing TWRP for GT N8000 and i also tried Philz then CWM all for GT N8000
I also tried flashing base rom but it gives NAND write fail
Nand write fail can mean damaged PIT or the actual nand memory is damaged and needs a new motherboard .
flash with pit file
found these pit files for the device.
you can flash the pit file for GT-N8000 in odin
don't forget to repartition, it's a very delicate situation, you don't want to mess it up, before going to this, you should confirm if the size are same. you wont like to flash a 16gb to 32gb partition.
http://forum.xda-developers.com/showthread.php?p=41158546#post41158546
good luck and please share your fix if its done
billysam said:
found these pit files for the device.
you can flash the pit file for GT-N8000 in odin
don't forget to repartition, it's a very delicate situation, you don't want to mess it up, before going to this, you should confirm if the size are same. you wont like to flash a 16gb to 32gb partition.
http://forum.xda-developers.com/showthread.php?p=41158546#post41158546
good luck and please share your fix if its done
Click to expand...
Click to collapse
thx for telling me... im trying out a new wire so will try it out nxt week
Sorry for the late reply tho
Osama Abedin said:
thx for telling me... im trying out a new wire so will try it out nxt week
Sorry for the late reply tho
Click to expand...
Click to collapse
same problem for me, this did not work, still write error
I have a similar problem. Everything is stuck. I am tryingo to go back to stock, but if I try to connect (via Odin, Heimdall, fastbot or adb sideload) i can't.
Is there any advice?
Thanks
nope not yet
I'm early ???
So it turned out that my AMAZING tablet had its storage device corrupted... I. E I exceeded the read write count
Similar problem Bricked N8005
I bought my N8005 (variant of N8000 but phone is disabled just data 3G is available) in 2012. I rooted it once and used custom rom for a while but last year installed official stock ROM again. Yesterday I started a game called "zombidle" (possibly this is an unnecessary info) and tablet restarted itself but stuck on "samsung" logo.
I tried to enter recovery mode but it always restarted and cannot enter recovery mode.
Tried to install different versions of CWM, Philz and TWRP recovery using odin but it always FAILed when NANDwrite started. Tried odin 1.85, 1.87, 3.07, 3.09, 3.12 but all same.
I tried to install same stock ROM but always FAILed.
Then I tried to install a custom rom but it failed too.
I read about bad pit files. Searched internet and found some pit files but nothing changed, FAILed at same point.
Did I finished all solutions?
Should I take it to the doctor?
Any sugesstions?
Thanks in advance.
Edit: Today I took it to the Samsung doctors. They said that; this is a mainboard issue and mainboard needs to be changed. That will be over 400TL (TL=Turkish Lira). Device is still in markets and new N8005 is 1300TL (i think this is also expensive. Because new Samsung Galaxy Tab S2 T817 32GB 9.7" is 1900TL in my country).
Does it worth to fix? Any opinions? Can I fix it myself somehow?
Nand write fail probable defunct memory.
Hi all..or anyone out there
I have had the seemingly strange bootloop problem on my stock note N8010...which stuck on the dreaded "samsung galaxy note 10.1" and only has odin feature working. (and no factory reset options because I think the poor old tab is crammed to bursting with apps, files and cache and so had a meltdown) poor thing.
so anyway I check these sites of techie wonder and wisdom and followed every logical option..starting with the simple ones
first ran power down and tried to boot up (x3) with no joy, then take apart the tablet to disconnect / reconnect the battery and boot up (x3) still no change.
So went and got the firmware from samwares (both jelly bean and kitkat) to then flash through odin....tried and failed first because of dodgy cable, but the then got a new one...and joy of joys (at first) odin recognised my tab and the firmware flashed across with pass..but then auto rebooted straight back into the dreaded samsung 10.1 again....so tried different versions of odins... and tried other global n8010 firmware...but funnily and frustratingly then all fully download and pass in odin (and the andoid logo and green download status bar on the tablet seems to shown that downloading is and has fully taken place.... but the darn thing still wont boot up past the samsung galaxy note 10.1
Sadly coming to the ends of my tether (of so many nearly there false hopes, high and lows) and very little cash to send it to the Sami tech bods doesnt help matter....I then read and tried the (supposed) last resort pit file/firmware option...first with kitkat (as apparently that worked for someone somewhere) and then tried with jelly bean..again each time itAlways passes in odin.... but auto reboots into the dreaded bootloop logo .... to haunt and torment me.. Aaaaagh!!!!.....I would not mind if it said action failed (for once) like some others seem to experiencet...but it always passes in ODIN????
So.....have come to the semi ignorant conclusion it is either the bootloader section of the tablet or the original software that is messed up or some internal hardware component has a fault.
but was wondering if there is anthing left to try...or would it potentially be possible or worth trying to root a tablet in this condition?
As although I have not ventured into the wild worlds of rooting.....I am now pretty confident of messing with this tablets mind..and have little to lose...so any further ideas and help would be great.
Exact same here. Never flashed, totally stock N8010. My wife hadn't used it for a couple of weeks. So she grabs it again and it was off. booted to nothing but the boot logo. Nothing worked except Download mode.
Flashing stock roms has Odin reporting success, but it still won't boot up. Trying re-Partition does give a fail as soon as I press start.
And we aren't alone. It appears there are quite a few of these cases. I have no idea how to solve this.
I have done a bit of rom flashing on my old galaxy S (the first one) and bootloaders and such usually were included in a ROM. Rooting was done with Recovery or an app and I think it was also possible with adb, IIRC (it's been a while).
It's my wife's Note and she's starting to scope out mini iPads...
Same problem with GT-N8010
I am also having the same problem.
I tried to upload a new ROM via ODIN. All was successful from the ODIN app (PASSED). but stuck on the boot screen. Power and Vol up does not work (it appears to but then crashes out to the boot screen again) so no way to do a hard factory reset.
Volume down/power does work and allows you to get to Odin mode. but as above, uploading a new ROM does not seem to work.
This is an un-rooted GT-N8010 with the stock ROM when I purchased it back in 2013 I believe.
Come on guys, give us some ideas.
Thanks
Gene
Sounds like wrong model firmware flashed as that's the usual bootloop problem .
Try Odin firmware flash wait to passed then remove battery for a short while and replace and try recovery mode .
In my case there is no incompatible firmware issue... The tablet just stopped working one morning and that was that.
Can't comment on the other posters though.
Sent from my GT-I9305 using XDA Free mobile app
Gene_uk said:
In my case there is no incompatible firmware issue... The tablet just stopped working one morning and that was that.
Can't comment on the other posters though.
Sent from my GT-I9305 using XDA Free mobile app
Click to expand...
Click to collapse
My wife's the same. Never done anything to it. No idea how to remove the battery. I let the battery run down once, then recharged it, made no difference.
That was before trying to flash the new firmware. My Note says N8010 on the back, it says so in the download mode. I got a firmware from SamMobile for the N8010. Don't know what else I can do.
Widdly said:
My wife's the same. Never done anything to it. No idea how to remove the battery. I let the battery run down once, then recharged it, made no difference.
That was before trying to flash the new firmware. My Note says N8010 on the back, it says so in the download mode. I got a firmware from SamMobile for the N8010. Don't know what else I can do.
Click to expand...
Click to collapse
Having same problem here ... tried flashing different firmwares along with PIT file - still no luck ..
stuck on samsung galaxy note screen .. cannot get recovery mode
Any help guys?
I'm kind of at my wits end, which may not be saying much
I've had my note 5 for 4 or 5 weeks, rooted and tried every custom ROM. I got curious this morning when I found I was on OH6 baseband, and wanted to update to OI5 before flashing to loco's OI5 ROM. I downloaded the files from the resource thread and flashed both the modem/baseband and bootloader with Odin 3.10.6. Phone booted back into android, checked new baseband and all was well. Placed new ROM on my phone and went into TWRP. Well, tried to, but it was stuck, sorry I don't remember the verbage, but something along the lines of unenforced kernel, but it stopped right there.
Went back to Odin, flashed TWRP 2.8.7.1, same thing. Did it again, same results. Odin again with baseband and bootloader. Same thing.
It gets worse.
Decided, OK, I'll fix you, so I'd start fresh. I went to sammobile and download OI5, the newest firmware. Takes over an hour to DL from that site, unless you want to pay for the faster service. Anyway, finished downloading, flashed with Odin, phone started to boot, then gets stuck in a bootloop righ after T-Mobile logo. Let it do this for 30-45 minutes with no luck, flashed Odin again, same results. I had the older firmware on hand, so I flashed OH6, but I get a failed result. Thought maybe bad file so I tried OGE firmware, getting the bad flash message with this one too. Re-downloaded OH6 from sammobile, but got same fail flash results. Tried different USB port on my computer, different USB cords (3), tried a different computer with same results for each file, including bootloop and failed flashes.
Wew!!
Any suggestions at this point? Any insight would be greatly appreciated.
Referenced firmware:
N920TUVU1AOGE_N920TTMB1AOGE_N920TUVU1AOGE_HOME.tar.md5
N920TUVU1BOH6_N920TTMB1BOH6_N920TUVU1BOH6_HOME.tar.md5
N920TUVU2COI5_N920TTMB2COI5_N920TUVU2COI5_HOME.tar.md5
edit: I played around some more after searching on the note 5 bootloop subject. Found a site dedicated to s6, which was close enough for the time being. I found if I hold the power and volume down it will cycle power down, but not completely power off. So what I did was cycle off and immediately hold home, power and volume up, with the thinking I would either get into TWRP or samsung power menu, so I could clear cache and devlac. Got into TWRP (which I couldn't before ?!?#?) and wiped, installed forever loco.
Looks I'm good to go, but I suppose forever patience is key here.
You can close this up.
Sounds like Mr toads wild ride... glad you are back up and running.
dandroid7 said:
Sounds like Mr toads wild ride... glad you are back up and running.
Click to expand...
Click to collapse
I was scratching real hard for a while. Still, didn't find how to turn a bootloop note 5 completely off other than getting into either android or custom recovery.
Plus, I fully expected my files to be gone, but they weren't!! Meaning none of the Odin firmware took, even though on the OI5 the little android told me he was erasing "everything".
This won't deter me from continuing my exploits, but I might start writing some things down. LOL
Delete please.
Hello all,
I have flashed ROMs via recovery and Odin plenty of times. I would say I generally know what I am doing and I flash ROMs on the regular. This is my third Samsung device and have been rooting/flashing for almost 3 years, so not a noob. And this is the first time I encounter problem with my phone while flashing ROM.
I was stuck in a bootloop on my Note and it wouldn't even let me boot into recovery, so I decided to Odin and back to stock and try again... I got the one-click, phone recognized, yellow COM box popped up, hit start, walked away for 10-15 minutes. Come back and there has barely been any progress at all... I could barely see the green progress bar. I figured something is wrong because I've done this before and it only takes a minute at most. What I did next is what I think messed me up...I pulled my phone and closed the Odin dialogue box and tried to redo it. Problem is, nothing I could do would get me the Yellow COM box. The phone goes into download mode but Odin doesn't seem to want to recognize it. I've tried EVERYTHING. When I boot the phone normally, I get the Samsung error screen saying there was an issue with a firmware upgrade and I should try Kies. I download Kies and attempt to upgrade firmware but my phone still not recognized. I already tried it to other PC still the same result.
I can't post the pic of my phone.
Is there nothing I can do to restore it?:crying::crying:
ton8_22 said:
Hello all,
I have flashed ROMs via recovery and Odin plenty of times. I would say I generally know what I am doing and I flash ROMs on the regular. This is my third Samsung device and have been rooting/flashing for almost 3 years, so not a noob. And this is the first time I encounter problem with my phone while flashing ROM.
I was stuck in a bootloop on my Note and it wouldn't even let me boot into recovery, so I decided to Odin and back to stock and try again... I got the one-click, phone recognized, yellow COM box popped up, hit start, walked away for 10-15 minutes. Come back and there has barely been any progress at all... I could barely see the green progress bar. I figured something is wrong because I've done this before and it only takes a minute at most. What I did next is what I think messed me up...I pulled my phone and closed the Odin dialogue box and tried to redo it. Problem is, nothing I could do would get me the Yellow COM box. The phone goes into download mode but Odin doesn't seem to want to recognize it. I've tried EVERYTHING. When I boot the phone normally, I get the Samsung error screen saying there was an issue with a firmware upgrade and I should try Kies. I download Kies and attempt to upgrade firmware but my phone still not recognized. I already tried it to other PC still the same result.
I can't post the pic of my phone.
Is there nothing I can do to restore it?:crying::crying:
Click to expand...
Click to collapse
You sound like you have a problem similar to what I had.
I was downloading 6.01 to install using KIES 3 and got no recognition from my Windows 7 based computer when I connected up and ran KIES.
I had the Sammy 1.55.5 USB drivers installed.
What I did it was use KIES,not KIES 3.
Samsung says KIES 3 but that turned out to be wrong in my case,although I'm not sure why?
I'm now running M/M and happily gutting the bloat out of it.
It feels better than new now!
Solved
Anyway, I already solved it!
ton8_22 said:
Anyway, I already solved it!
Click to expand...
Click to collapse
i have the same problem....
how did you solve it?