I'm on a warranty exchanged 1012 build Captivate. I initially decided to go ahead and flash a new ROM to it, and proceeded to do so using Odin 1-click like I had done so many times in the past with my old 1008 build Captivate. Odin hung for quite some time, and I feared the USB cable I was using was faulty to a certain degree. No biggie, just restart the process and all would be good.
That wasn't the case here though. It simply doesn't boot anymore. I believe it to be a soft brick as there is an image available on the screen. It's the wretched cellphone --- computer screen. I attempted to reboot into download mode like I had done using the VOL+/VOL- and USB insert method, but all that appeared was this symbol. I was simply trying to restore to stock 2.1, as this Captivate came with stock 2.2.
I've even built a JIG, a couple actually, using varying resistors. The first JIG I built before attempting the ODIN flash that killed my phone. Prior to flashing ODIN, the JIG appeared to work brilliantly. It put my phone into download mode about two seconds after contact. Now all it does is bring up that damn cellphone --- computer screen.
What is strange is that the phone, when plugged into the computer after I attempt to put it into download mode using my JIG(s), the computer will play that sound that it plays when it recognizes a USB device. In addition to that, if I plug it in when ODIN is open, ODIN recognizes the phone and displays a yellow block with "0:[COM11]" in it.
I went ahead and downloaded the necessary things from this thread:
http://forum.xda-developers.com/showpost.php?p=10056254&postcount=36
and began trying to flash to stock using his instructions. So far ODIN appears to be running, but is stuck at modem.bin.
Maybe its not making any progress at all, but I'd like to hope so. Does anyone know if the 1012 batch can get into download mode using a method outside of the normal key presses and JIGs? Any recommendations for me to revive this Captivate? I did enjoy the fact that it didn't shut down on me every 30 minutes. The GPS still sucked on it though. But I need to bring it back to life, just don't know what other options there are. As far as I know, if the screen presents you with an image of any sorts, its just a soft brick and CAN be recovered.
Can't use one click with your build number. You would need to use full odin. There are numerous articles here on how to do that.
mrhaley30705 said:
Can't use one click with your build number. You would need to use full odin. There are numerous articles here on how to do that.
Click to expand...
Click to collapse
Yeah, found out the hard way. I do wish there was a stickied post that broke down the build numbers and the various caveats of each build number, including tried and proven methods of restoring to stock and other things.
My situation was quite strange, as ODIN appeared to recognize the phone even though it only displayed the "cellphone --- computer" icon. I'm wondering if the failed flash screwed up the download mode graphic and replaced it with the "cellphone --- computer" graphic? Either way, it didn't "appear" to actually be in download mode, it was.
That screen only means that a flash was incomplete. Flashing anything even a modem successfully will get rid of that screen, granted your kernel/rom was broken so it wouldn't have booted properly but that screen would've went away, replaced by a bootloop. so to fix it completely to an up and running state an entire rom package is needed. Like you used.
Just informing you that, that screen isn't the **** your pants moment. that time comes when the phones does absolutely nothing, as long as there is ANYTHING you are 99% of the time ok. That 1% is when your usb port on the phone is broken, or your pc drivers just all of a sudden decide to extend their arms and give you the figner, or you try odin again with the same faulty connection that gave you the bad connection/incomplete flash and that time it hangs on the bootloaders and bricks it.
Odin recognizes my phone in all modes except completely off: booted, recovery, download and I just tested the phone...!...pc screen on purpose by yanking the chord during a kernel flash got that screen of coarse cause the flash was incomplete. But unless the phone is in download mode it doesn't initiate download protocol and odin will hang on setting up connection.
You can't really have a guide line for what works on what builds for any certainty because every phone of a certain build doesn't behave the same way.
I have 3 captivates I flash. 1, a 1010, and 2 are 1012s all of them have no issue whatsoever with odin one click. It's just the luck of the draw...
I recently had this EXACT issue. The way i fixed it was building a jig out of 3 100k 1/4w resistors and forcing my phone into download mode.
Studacris helped me out there!
if your still having issues, its http://forum.xda-developers.com/showthread.php?t=1079000
I also just went through this. I just had to keep trying. The jig is what saved me.
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
Related
Hi
My brother (a no-geek) has a captivate, and lives in a different city (I donot have physical access to the phone). He visited me few weeks ago and I installed CM-7 on his phone, i know my bad. Some of his videos were not working, so i asked him to update to the latest CM-7 build. He download the build, saved it on int sd_card and used ClockWork Recovery to install the selected ROM. Upon reboot it entered in never-ending splash screen. I found couple of odin ROMs, and posted him link, we tried to flash them, but no good.
Status --
The COM ports are detected, but the process at times halts at <SET PARTITION> at times at <SET UP>... at times all thread completed successful would show up as soon as hitting START.
I dont have a captivate, can someone please suggest a sure shot solution and post me a link for ODIN, with a root rom. I am using Team Whiskey on my Vibrant, and I prefer stable modified ROM because of its features and power.
I can explain him the process on skype using desktop sharing, but the ROM should be good. Thankyou very much in advance.
if he can access recovery, try wiping everything thru recovery then start again
Phone is in Soft Brick state.
Phone is in Soft Brick state. So i cannot boot into the phone and go to CW recovery.
What he needs is just a stable usb connection that's how he got to this point, bad communication between the phone and computer. On cm7 I beleive you need the nexus s drivers installed. Also make sure it's plugged into a usb port that's attached directly to the motherboard (back of pc, port 1 on laptop)
@studacris
I think the drivers are already installed good. The connection is also good, as i can the COM port detection in the ODIN, with one of the boxes changing its colour from NO-COLOUR to YELLOW-COLOUR.
I think the ROM builds are not good. They go action-less during flashing, actually nothing (progress bar) comes on phone, it keeps showing the Downloading screen, endlessly. Odin usually is stuck at at <SET PARTITION> at times at <SET UP>...
Can someone post a link for a test one click odin. Well i would prefer one click.
You did try DG's JF6 one click, thats the only one I use, how are you establishing dowload mode on the phone or are you even doing this.
REMY4223 said:
I would suggest to Odin back to stock then update to Froyo via Kies.
Click to expand...
Click to collapse
if you could do all that, why would you need to send back for a new phone ? If you could do any of that, the OP wouldn't be in a non-functioning predicament
Ragin Caucasian said:
if you could do all that, why would you need to send back for a new phone ? If you could do any of that, the OP wouldn't be in a non-functioning predicament
Click to expand...
Click to collapse
+1 If you read the OP the problem is he can't flash back to stock he is having problems flashing anything period, @ the OP correct me if I'm wrong but I have a strong hunch that you are leaving out some pretty crucial steps, I have a feeling that you are not putting the phone into download mode, I also believe that you are gonna need to make a jig and pay a visit to your brother to help him out especially if its bricked the same way mine just was flashing with cm7 roms. But if you are getting a com port to show without having to put in download mode then you are farther along in the boot process. If this is the case you may be able to adb into recovery do a full wipe excluding /boot and reflash. Will the PC recognize the phone with it in its current boot locked state? If so then recovering should be somewhat of a breeze.
http://forum.xda-developers.com/showthread.php?t=829392 read this post it may help otherwise there are tons others
- I am getting to downloading mode by
--- pressing the "vol +" and "vol -" buttons and then connecting the usb cable to the computer.
--- then removing the cable, after the phone enters the download mode. Then, start the odin and connect the phone through usb cable again. The odin detects the phone on one of the COM port.
- I havent tired wiping the phone through recovery. But i need to get to recovery first. I dont know in a soft brick state if i can get into recovery.
- regarding getting back to 2.1... i would like to flash to the latest version. Kies update is not an option for me, as i not in US.
This phone was purchased from craiglist, i used one click root method to root it and the same script an option to get the unlock codes. After that i experimented a lot on the phone with various scripts. Last i was using congnition on it. Then saw CM7, i liked it on my vibrant, so i flashed it on my captivate (which i got for my brother). Now i have to get back to some stable modified ROM... I am thinking about trying Srendipity or cog ROM... but before than i have to install a rooted stock ROM.
That is the story and issue... but thanks a lot for help. Any more suggestions.
viveksharma2108 said:
- I am getting to downloading mode by
--- pressing the "vol +" and "vol -" buttons and then connecting the usb cable to the computer.
--- then removing the cable, after the phone enters the download mode. Then, start the odin and connect the phone through usb cable again. The odin detects the phone on one of the COM port.
- I havent tired wiping the phone through recovery. But i need to get to recovery first. I dont know in a soft brick state if i can get into recovery.
- regarding getting back to 2.1... i would like to flash to the latest version. Kies update is not an option for me, as i not in US.
This phone was purchased from craiglist, i used one click root method to root it and the same script an option to get the unlock codes. After that i experimented a lot on the phone with various scripts. Last i was using congnition on it. Then saw CM7, i liked it on my vibrant, so i flashed it on my captivate (which i got for my brother). Now i have to get back to some stable modified ROM... I am thinking about trying Srendipity or cog ROM... but before than i have to install a rooted stock ROM.
That is the story and issue... but thanks a lot for help. Any more suggestions.
Click to expand...
Click to collapse
Try putting the phone into download mode after you open Odin. Which version of Odin is this? Also, installing the nightly build of CM7 again often fixes the boot loop on the newer builds. I would try that if you can get to recovery.
Sent from my SGH-I897 using XDA Premium App
I rooted my cappy(cappy 1) and installed serendipity 6.4 on a clockwork kernel back in May for the first time based upon info I gathered here from all the experiences and advice. It went flawless. I odined back to stock and attempted to update the kernel to the one from the link on the serendipity 7 page and while it was doing the kernel flash it went into a boot loop that I apparently am not smart enough to recover from. Odin does see the phone for just a split second and starts but the phone restarts before it gets done. My wifes(cappy 2) came in the mail yesterday and she wanted freedom too so I rooted and tried to use a kernel I d/l from a site I recognized from everyones post and it said to use sgs kernel flash and I have had pretty much the same result in this phone too!! ??? whatsup?? I did it without fail the first time and now I am questioning myeslf. Neither will boot to recovery, neither will connect to pc via usb long enough to use odin. I am dumb about ADB. Clicked on the adb file and it flashes through really quick on my pc then closes. Tried to make the usb manual jumper with the resistors and I can't seem to have any luck with the technique. I ordered the jig for the usb connection for like 9.00 but I won't get it til next week. Any help would be appreciated...... I am at a total loss!!!
Are you using Odin from download mode? As long as you have a cappy with working button combos, start Odin (right click and run it as an administrator) without the phone plugged in. Pull the battery out, remove the SIM and external SD card if you have one, replace the battery and leave the phone off. With the phone off, hold both volume buttons and plug the usb cord in. The phone should turn itself on in download mode, at which point you can hit start in Odin.
If this is what you're already doing I'm not trying to talk down to you, I just couldn't tell from your post. If this is indeed what you are already doing, are you getting an error in Odin?
the three button was working on both before but now seems to no longer.... I can't for the life of me get to recovery or download mode.... I think I could revive both if I could just get that far. and had a good kernel file which I obviously am not getting or I am doing somthing way wrong. Neither are totally bricked... the try to come on but keep restarting themselves. BTW thanks for the help and I don't feel talked down to at all.... felling pretty silly/crappy about my abilities right now. Thought I had the whole root/kernel/rom thing figured out til now.....
as far as odin errors. my first phone would hook to odin and then lose the connection because the phone turned itself off. the second one will not eastablish a connection at all.... does that make sense??
I would shoot for download mode at this point. When you tried the resistors to build your own jig, was the phone off when you were trying to get it to work?
1whttcdreamer said:
as far as odin errors. my first phone would hook to odin and then lose the connection because the phone turned itself off. the second one will not eastablish a connection at all.... does that make sense??
Click to expand...
Click to collapse
If you're in download mode, your phone shouldn't turn itself off. What odin package are you using?
yes, phone was off and I had 4 resistors with a total value of just between 300K and 301K. I was in my opinion unsuccessful in touching the two pins correctly without the resistors touching. I may try to disect a usb cord tonight and solder my resistors to the black and green wires(think thats correct) and see if I have any better luck. To impatient to await the jig for 5 or so days. But at least i'll have it for later use. Then I guess go back stock and start over. but I gotta get D/L mode to work first. I think odin was version 3.1.7 I'm at work and don't recall exactly. I know I D/L'ed a odin console and a set of files to put in particular places as to direct odin what to use. It came as a complete D/L. I also have tried the one click odin files before(this is what I used the first time back in may) any and all help is greatly appreciated.
1whttcdreamer said:
yes, phone was off and I had 4 resistors with a total value of just between 300K and 301K. I was in my opinion unsuccessful in touching the two pins correctly without the resistors touching. I may try to disect a usb cord tonight and solder my resistors to the black and green wires(think thats correct) and see if I have any better luck. To impatient to await the jig for 5 or so days. But at least i'll have it for later use. Then I guess go back stock and start over. but I gotta get D/L mode to work first. I think odin was version 3.1.7 I'm at work and don't recall exactly. I know I D/L'ed a odin console and a set of files to put in particular places as to direct odin what to use. It came as a complete D/L. I also have tried the one click odin files before(this is what I used the first time back in may) any and all help is greatly appreciated.
Click to expand...
Click to collapse
I have never been successful in touching the pins without cutting apart a USB cord. With the cord, though, it's a piece of cake. You don't even have to solder them, just stick the plug in there and you can hold the resistors (as long as they're covered with something) to touch the right pins. I don't know that the color coding is consistent, but you can figure it out either with a multimeter or trial and error. I also think it's 3 resistors not 4, but your values are correct so that's probably what you were doing.
Once you get into DL mode, you have a couple of options:
1. Try Serendipity 7 again. I've done several installs from their instructions and they work perfectly, but there are a lot of steps and you need to be careful to hit them all in order (I've definitely ended up in your situation before because I thought I remembered what needed to do but missed something).
2. Flash a one click. You can find them all here:
http://forum.xda-developers.com/showthread.php?t=1300843
If you were going to go this route, what I would do is flash the one-click for KF1. This will give you Samsung gingerbread bootloaders which are both compatible with everything and will give you your button combos back for download and recovery modes. Once you flash this, you should only use bootloader-free packages and you will always have your button combos with no risk of a hard brick.
Once you have KF1, you can root it from here:
http://forum.xda-developers.com/showthread.php?t=1127249
then get CWM recovery, skip to step 13 in the S7 download instructions, and flash it in recovery.
Good luck!
Thanks Ever So Much!!
:cool Well long story short my jig worked. You were right, it was very easy to make. Soldered resistors to pins so now I have a working jig. My original phone is so totally fixed. Running rooted 2.3.3 Serendipity 7 with CWM. Thank you very much for the confidence building and advice on where to start and finish.
I attempting to get the phone to load the "Sammy 1.5" Rom. I have a Galaxy S Captivate I897.
I was not initially able to get Odin 1.85 to recognize my phone. So I used Heimdall to place it back to UCKB2.
Now Odin recognizes the phone. So then going back to the instructions for Sammy ROM:
http://forum.xda-developers.com/showthread.php?t=1486344
I fired up Odin 1.85, placed Cog Kernel Beta 2 in the PDA slot. And now the phone is stuck at:
"File Analysis.."
Its been there for over 25 minutes.
Any suggestions?
Note: I had KK4 working on the phone (small quirks: games suck) just prior to attempting this MOD.
I had this issue with my backup phone. It never seemed to like to take a flash on the first try. If I put it in download mode via a jig it seemed to work better.
One trick that worked for me was to pull the battery (Yikes! I know it soft bricks it) and I would then get the incomplete flash screen. I would then Odin from that screen and it would take.
Red_81 said:
I had this issue with my backup phone. It never seemed to like to take a flash on the first try. If I put it in download mode via a jig it seemed to work better.
One trick that worked for me was to pull the battery (Yikes! I know) and I would then get the incomplete flash screen. I would then Odin from that screen and it would take.
Click to expand...
Click to collapse
Via a jig? Are you saying that you dance a jig when you connect the phone? Just kidding. What kind of jig are you talking about?
A jig is a usb connector that has a 301k Ohm resistor on the 4th and 5th pin (the top and bottom pins next to the headphone jack.) Most if not all Samsungs android devices use this method to get in Download Mode.
Layman way to make one found here. Don't buy the usb plug he used since thats really expensive but you can understand the theory of it. You can buy one here if you like. Cheaper to just grab the resistors and buying some plugs else where, splicing a spare cable or just trying to hit the 2 pins in the port.
Here is an example of one you can buy if you don't want to build your own. They are all over amazon and ebay. This is not an endorsement for this particular seller/product. Just an example so you can see what we're talking about. For $10 or less they're great to have around and can be a lifesaver.
http://www.amazon.com/SainSonic-Don...73JQ/ref=sr_1_1?ie=UTF8&qid=1329842683&sr=8-1
Thank you. I do have a jig from when I bricked my first Captivate. I got Odin to recognize the phone. Now she is stuck at "Setup Connection"
I must be missing a step somewhere, or, I have something installed that Odin doesn't like.
Let me ask this?
If I installed kk4 with Heimdall, should Odin still recognize the phone in download mode?
Richdd said:
Thank you. I do have a jig from when I bricked my first Captivate. I got Odin to recognize the phone. Now she is stuck at "Setup Connection"
I must be missing a step somewhere, or, I have something installed that Odin doesn't like.
Let me ask this?
If I installed kk4 with Heimdall, should Odin still recognize the phone in download mode?
Click to expand...
Click to collapse
Yes. Odin and Heimdall don't care how you flashed to where you are - they only care if the phone is in download mode.
Ok, I reinstalled KK4. I get a screwed up multi color screen. Then the phone boots correctly.
It seems I've missed something. I'm going to have to figure out how to get Odin recognize the phone. To be able to install the ROM I want.
EDIT
I noticed that when my phone reboots, my live wall paper goes back to the phones default wall paper. Does not remember what setting I have placed on the phone.
It sounds like you might have a mismatch between your bootloaders (most likely you have froyo/eclair) and your Rom (a GB rom).
If Heimdall worked, grab one of the Heimdall one-click packages that has bootloaders (you may have to flash twice to get the "flash bootloaders" option). That should straighten you out.
Ok, I'm downloading one now. I'll try it in a few. Thanks again everyone for helping!!
Edit
I tried everything with Odin. Nothing worked.
Heimdall works. I installed Heimdall I897UCKK4 Stock, Wipe, with option to install Bootloaders, Param,and Repartition-Heimdall One-Click. The phone boots good. Everything except games seem to be working for now. Still have to figure out how to get Odin to work to load that "SAMMY 1.5" ROM.
No firmware and USB problem
I have a large problem, my wifes galaxy s won't go by the first screen (says GALAXY S GT-I9000)
So i thought i'd fix it using odin using the 3 button combo. But that isn't working anymore.
Luckily i have a usb jig which gets me to the download mode ...... but !
When i connect the pc cable (tried 2 OE samsung ones) i get device not recognized so i can't use odin to fix it.
What can i do, or do i have to send it to a repair centre to be resurrected ?
I have searched and searched but not found any topics with the same issues i have on her phone.
Need a bit more info i.e were you flashing the phone??if so which rom?
Then phone was playing up so i flashed darkys 10.4.2.
However the usb connection wouldn't work so i flashed it to standard JVT
using mobile odin.
Then i rooted it and went to go into recovery mode and it wouldn't turn on.
I tried to help the gentleman , but no luck . From what he told me , phone turns on after battery insertion , and It is not recognised by usb => so odin not usable .
If you can get to download mode but the phone isn't recognized by your computer then i'd say it's a driver issue. Install your phone's drivers again. To do that, just installing kies is enough BUT be sure to open task manager in windows and kill any process that has kies in it's name before opening odin.
If that still isn't flying i'd try using different USB ports and even with a different computer.
Extra advice:
- try not to flash bootloaders for now. That means picking a rom that has no bootloaders included but matches your phone's current bootloader. If you were using gingerbread flash a gingerbread rom, if you were using froyo, flash a froyo rom.
phone not starting up past first screen (GALAXY S GT-I9000 in white on black screen), phone not recognized neither by pc nor laptop ( usb drivers installed ) , phone turns on after battery insertion without pressing anything.
This manual is from a German board
Take the battery out, then hold the 3 keys combo for download and put the battery back on. Now you should start the download mode.
If not, then try it with a jig.
Good luck!
GOT A JIG. WORKS FINE.
But pc wont recognize it !!
Have you double checked that you have the right drivers installed? I know you have to use the Nexus S drivers for CM9, not sure about Darky's ROM.
Drivers
Download drivers 64 bit | 32 bit from here and install.
It is NOT the drivers as my other galaxy s connects fine every time.
Drivers have been removed and installed repeatedly.
I would suggest a different computer, maybe a different cable. I have this same issue with my infuse, hope you get this resolved.
Sent from my Desire HD using XDA App
Already tried that as well
You could try Adam outler's unbrickable mod.
Pasted from other thread:
I just wrote a wall of text b4 and my browser crashed GG
Well, here we go again, i will only tell what I did/the process
I did a nandroidbackup, then i wiped all data (data+cache+dalvik), installed CyanogenMod 9 (Build 16), it rebooted automaticly, so I entered recovery again, installed Google Apps from there, wiped data and cache (no dalvik), rebooted.
Ended up looping at the Samsung screen (not animation), and I couldnt do the 3-button-combo, so the NANDroid backup is useless.
I can enter the download thing, but i dont even know what it does.
Tried plugging it in the charger (after letting it dry out during the night), and only the loop thing appears. Cant do anything.
I see that theres something called odin (Since my download thing is working (VolDown+Home+Power) if its that you mean.
If its possible to fix my phones state, please tell me how, since I startedrooting, flashing and stuff yesterday (Gotta start at some point) and followed HDTechVideos tut (On his website)
woolf clubs said:
You could try Adam outler's unbrickable mod.
Click to expand...
Click to collapse
I have nowhere near enough ability for that. Pity though.
Your problem is most likely the USB port. Maybe cleaning it might help. It happened to me for a few months then when I got the S2 I stopped using it. Began to use it as my home 3g wifi modem and kept it on charge the whole time. A few weeks later tried connecting it to the computer and it worked first go. Ever since it has worked perferctly. I suspect the problem possibly started by a rain drop getting into the port.
Mind you, even when it wasn't being recognised by the PC, I would constantly connect, remove, reconnect, reboot PC and phone etc and it would sometimes get recognised. Other times it wouldn't connect but Odin still recognised it.
Sounds silly but try leaving it on charge as I did and maybe, just maybe you'll be lucky like I was.
Sent from my GT-I9100T
Well as of today it is away to the O2 repair centre.
Its under warranty (unless the find out it was rooted etc) so fingers crossed.
Well had a text back today to say my phone has been despatched, so here is hoping that its fixed.
It came back from the repair centre yesterday with a note saying a part had been replaced,
no costs for me, yippeeeeeeee.
Howdy there.
First off, this is not "just another bricked Note thread".
I got this thing from a friend who did not have a clue what he did with it, but he told me he tried to "root it or something" He didn't have any files left, or any memory what he used.
I have for weeks tried every single trick in the book, followed every tutorial, and it shows no sign of coming to life any time soon.
When I got it, it just got stuck on the Samsung flash screen. I couldn't get into any sort of recovery, but I got into download mode, so I tried reflashing the stock firmware with ODIN, but it got stuck on NAND WRITE START for 2 hours, and then failed. All Kies processes were killed, I double checked.
After that, it only shows the "Firmware update failed, start emergency recovery mode in kies"
Kies does not support initialization for N7000, doubted it would have worked anyways.
After this, I went on to read about the brick bug for N7000
Since then I have tried repartitioning the device with all kinds of pit files, I have tried installing about 20 different firmwares, I have tried installing just a kernel, both stock and others, and NOTHING works.
Some pit files get stuck in DO NOT TURN OFF DEVICE for 6-24 hours, until I have disconnected or battery has run out, and some fail by themselves after 20 minutes.
Firmwares get stuck at NAND WRITE START, and fail after about an hour
Kernels fill up the bar with the green dots showing it's doing something but as soon as the log says "NAND Write Start" it gets stuck.
Is there ANYTHING still worth testing, before throwing it in the well? I will not go to a service center and pay to fix a spare phone that will lay in a box until I MIGHT need it some day.
It doesn't matter if my storage space goes down to only 500mb space with some sort of repartitioning, nothing matters. I just want it to run.
I do not have any recovery, and I haven't successfully installed any,
Basically the only thing I can do, is get to Download mode, and the only program so far finding it is ODIN.
I am very thankful for any help, and don't hesitate checking if I forgot something very basic, I might just as well have forgot something very important, but I feel I have tried everything.
Thank you!
-Jimi
It is exactly this: just another bricked Note thread.
ThaiDai said:
It is exactly this: just another bricked Note thread.
Click to expand...
Click to collapse
Well, okay then. Thanks for clearing that up.
I just figured that it's something worse since NOTHING works, hence the "not just another" meaning "not just the same as the others". Atleast I thought it meant that. Perhaps my English isn't so good. Oh well.
I have read dozens of other threads about this where people have been able to get into recovery mode, repartition, or flash a new kernel, or at least SOMETHING, but mine just blocks everything.
-Jimi
Okay then, let's simplify the question/request.
Is there ANY way at all to scan or/and repartition my emmc?
WITHOUT a recovery.
WITHOUT it accepting anything through ODIN, not even the standard pit file, or any of the custom ones I have tried from another thread.
WITHOUT adb.
I can only get to Download Mode.
Heimdall seemed to understand my phone a bit, but couldn't flash anything.
Kernels got stuck at 100%
Factoryfs got stuck at 4%
Recovery got an error "finishing the packet" or something.
Could I use Heimdall to scan or repartition my emmc maybe?
If you are unable to Odin flash a recovery or stock rom then there's no other way. If you found other methods but is still unsuccessful then your phone is dead anyways.
I have seen the NAND write stuck error sometimes goes away on a different PC. If the memory is not already broken but worth a try.. Also use original USB cable, main PC usb port, odin 1.85.
nokiamodeln91 said:
I have seen the NAND write stuck error sometimes goes away on a different PC. If the memory is not already broken but worth a try.. Also use original USB cable, main PC usb port, odin 1.85.
Click to expand...
Click to collapse
Nah, I think the memory is broken.
I have only tested with odin 1.75, but on 3 different PCs
My laptop with Win 8.1
My old computer with XP
And my work computer with Win 7 home
Still, I do not want to give up!
In my frustration I started to flash everything and anything that just had a N7000 tag on it, and somehow somewhere something happened.
I do not have the "firmware failed, use kies recovery" message anymore.
I am instead getting the Samsung splash screen, but it freezes there, I can't do anything.
And also, if my device is off, I can charge it! The battery shows up, but then it freezes with the circle in it before it fills with green to show how much it is charged, but now it atleast accepts charge. Before it didn't.
But I still wonder if I could not scan and repartition my phone with anything else than recovery mode? Perhaps I could flash a repartitioned custom Pit file with Odin if I could just scan it somehow?
I got a similar problem with my uncle's Note. It was working fine all these years, until last month when I rooted it to upgrade it to 5.1. The phone worked for over a month post upgrading.
However, now, when I power it up, nothing happens, absolutely nothing. If I connect it to a power source, the offline battery charging symbol comes up saying 100%. Recovery mode doesnot work, though I can go in Download mode.
I tried a couple of stock ROM images through ODIN. They were flashed successfully, but the issue persists. Looks like another dead Note.
froyoguy said:
I got a similar problem with my uncle's Note. It was working fine all these years, until last month when I rooted it to upgrade it to 5.1. The phone worked for over a month post upgrading.
However, now, when I power it up, nothing happens, absolutely nothing. If I connect it to a power source, the offline battery charging symbol comes up saying 100%. Recovery mode doesnot work, though I can go in Download mode.
I tried a couple of stock ROM images through ODIN. They were flashed successfully, but the issue persists. Looks like another dead Note.
Click to expand...
Click to collapse
Which rom was this?
AutumQueen92 said:
Which rom was this?
Click to expand...
Click to collapse
Thanks for your reply. Couldn't check it until last night. I was running NightOwl when this happened. Last night, I thought something and flashed the same Philz recovery through Odin and some how it worked.
I have started realizing that it is a hardware issue, since the device does not start without being connected to a power source. 1 out of 20 tries take me into recovery (of course while the device is connected to the charger, or else the screen is always black).
However, the recovery doesn't stay too long. I tried flashing a newer version of NightOwl, but while the recovery is still opening the package, the phone restarts .
One weird thing is that the phone doesn't starts without being connected to the PC or the charger. But when connected, within seconds, the offline charging screen says 100%, which is making me believe something is wrong with the hardware.
Part of the "hardware" is your battery...