Hey there,
Got my moms Galaxy over here. Thing wasn't updated and slow as hell so I thought I'd update it. Went through the Kies process but that didn't really work, phone just couldn't make connection despite what ever driver I used (win or mac, got both here).
So first things went haywire when I read somewhere to flash recovery I needed to do something via Heimdall. Did that with the command window and afterwards the phone got stuck in a bootloop (only the I9000+samsung repeating over and over again).
Then I tried flashing GB from samfirmware, which failed. All done through odin, the screen went purple at dbdata.rfs. So I went with stock froyo, from the androidworld.nl forums and same thing happens but now it's a blue screen at factoryfs.rfs.
What am I doing wrong?
Try flashing again via Odin and this time don't touch your pc while it is flashing. That yellow purple screen has happened to me while I was doing other things while flashing was going on in the background.
And check if your phone is i9000 or i9000+ and flash the their respective firmware .
Sent from my GT-I9000 using XDA App
gcuchiha said:
Try flashing again via Odin and this time don't touch your pc while it is flashing. That yellow purple screen has happened to me while I was doing other things while flashing was going on in the background.
And check if your phone is i9000 or i9000+ and flash the their respective firmware .
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Same thing, didn't do anything and screen went gray. This is so random for me, as flashing is SO easy with my own Desire but this thing is on a whole different level.
Try changing your Odin version to 1.82 and try again.
Sent from my GT-I9000 using XDA App
Or 1.3 idk try both.
Sent from my GT-I9000 using XDA App
gcuchiha said:
Try changing your Odin version to 1.82 and try again.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
gcuchiha said:
Or 1.3 idk try both.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Actually did both already! The 1.3 was from the 2.2 pack from the Dutch forum. Got 1.82 from the samfirmware website. No luck yet
1.82 shows a bootloader function, do I need to have one of those files with it?
No don't flash bootloader
Sent from my GT-I9000 using XDA App
gcuchiha said:
No don't flash bootloader
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
I was about to try this actually! http://forum.xda-developers.com/showthread.php?t=1196179
Since the screwup started with Heimdall, might fix it with that?
Watch a YouTube video and see if you're doing everything properly.
What I do is
1. Go to download mode
2. Open Odin, select pit, PDA, phone, CSC files. And remember to check the re partition option
3. Connect your phone
4. Click start.
Sent from my GT-I9000 using XDA App
Maybe. I never used heimdall. Maybe you could try that.
Sent from my GT-I9000 using XDA App
gcuchiha said:
Watch a YouTube video and see if you're doing everything properly.
What I do is
1. Go to download mode
2. Open Odin, select pit, PDA, phone, CSC files. And remember to check the re partition option
3. Connect your phone
4. Click start.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Doing all that yeah, exactly in that order.
Hmmm. Then I guess heimdall is your only hope ,since it started the problem.
Sent from my GT-I9000 using XDA App
Hmm, in Heimdall it gets all the way up to MODEM @ 59%. Then it fails and crashes..
weird
[edit] buuuuuuuut I got android recovery back! okay now we have progress!
and now by adding the packaged zImage from CM have CM.. progress again!
Are you using the original USB cable?. Same thing happened to me with a cheap ebay cable...
cabessius said:
Are you using the original USB cable?. Same thing happened to me with a cheap ebay cable...
Click to expand...
Click to collapse
Hm, no. It's a replacement cable (cheap) which I used for my Desire, no problem with that at all. Though it might be it indeed! Will be two days before I can get the original cable.
In the meanwhile I got CWM-based Recovery v.5.0.2.6 working.. while installing cyanogenmod it goes "checking blm status", then "install from sd complete".. a bit strange and it doesn't boot into the rom but into the recovery.
Lipinsky said:
Hm, no. It's a replacement cable (cheap) which I used for my Desire, no problem with that at all. Though it might be it indeed! Will be two days before I can get the original cable.
In the meanwhile I got CWM-based Recovery v.5.0.2.6 working.. while installing cyanogenmod it goes "checking blm status", then "install from sd complete".. a bit strange and it doesn't boot into the rom but into the recovery.
Click to expand...
Click to collapse
Switching back to the original cable fixed the problem for me. Hope it does for you as well, try that and tell us what happened!.
Can I still use Odin then, now with CWM recovery?
You can use Mobile Odin by Chainfire (look for it in the market), it works exactly as an Odin built-in your SGS with no need for PC.
cabessius said:
You can use Mobile Odin by Chainfire (look for it in the market), it works exactly as an Odin built-in your SGS with no need for PC.
Click to expand...
Click to collapse
Uhm, well I can't get really into any market as no rom will boot at this moment..
Guys, thanks for the cable advice! Could get my hands on a SE cable and flashed 2.3.5 stock through Odin. Happy that I didn't wreck my moms phone :')
Related
Was going to flash new Rom and I think I cleared partian cache, also cleared dalvik cache went to reboot phone stuck at black Galaxy S screen I was running perception 10. I have a 1010 captivate was told I cant use regular odin with this model. Tried re-installing rom through recovery but says fail at line 14 and seredipty rom says fail at line 21. Please help
http://forum.xda-developers.com/showpost.php?p=10056254&postcount=36
Read and try this
Sent from my Captivate using XDA Premium App
Ok I tried this 3 times and odin keeps getting stuck on modem.bin any suggestions
Are you opening Odin prior to connecting phone?
Sent from my Captivate using XDA Premium App
yes am I supposed to
Yes. Just checking hmm
Sent from my Captivate using XDA Premium App
I dont have to add a modem where it says phone do I, How long should it stay at modem .bin
How long has it been there?
That should not take long
If stuck pull battery keep out for a couple then retry. Also I believe ig you right click Odin you can run as administrator try thay
Sent from my Captivate using XDA Premium App
I read that but theres no option to run as admin, tried it again and this time said cannot open serial port, Ill try again
Try different ports on pc
Sent from my Captivate using XDA Premium App
Long shot but read this
not found any responses. Here is my situation:
*My computer recognizes the phone *ODIN recognizes the phone *the phone is in download mode *ODIN gets stuck *I have tried multiple times, but it continuously gets stuck at DO NOT TURN OFF TARGET!! *The max I have waited is around 30ish minutes *3 button combo works on my phone *I have tried non-one click ODIN to JH2 and it freezes on modem.bin
I have used ODIN before, and I have no idea why this is not working. If anyone could help me it would be greatly appreciated.
PROBLEM SOLVED: Antivirus software screwed with ODIN" __________________ How to videos For the Samsung Captivate b
Sent from my Captivate using XDA Premium App
I disabled firewall and anti virus still freezes at modem.bin damn
Did the software do come with a modem.bin
Sent from my Captivate using XDA Premium App
not sure how do u check I just followed link step by step
When you extracted the rar. File to get the tar to put in PDA. Was there. A modem
Sent from my Captivate using XDA Premium App
ya theres a modem file
Try rebooting your computer. Then try again if same issue then
Also maybe redownload the rom software in case of corruption
I am not sure of this but at this point might as well throw that in.
Sent from my Captivate using XDA Premium App
Ok borrowed sisters Laptop downloaded all files and did process over and worked like a charm first time, must have been problem with my desktop wow, my question now is do I have to update to JH7 to root and flash serendipity or can I do it from the current JH2.Mcord thanks for you help I really appreciate it
If you have the update.zip on your SD for clockwork recovery I believe you should be able to get into recovery reinstall packages twice then install zip from SD choose serindipity and flash away
If you dont have it let me know I will post a do link
Happy things are up and running for you
Sent from my Captivate using XDA Premium App
thanks I have it on there Ill try it thanks again
I have a Samsung Galaxy Tab GT-P1000. Using Odin3 v3.04 I (accidently) flashed the Bootloader with the wrong binary. With the Auto-Reboot option selected on the Odin3, the device turned off and is not turning on again.
Before flashing, my Tab had the official Samsung GB 2.3.3 (P1000JPJPC if I am not mistaken).
Some threads suggest that I charge the Tab using the wall charger for 4 hours, and see if the battery icon appears on the screen or not, then connect the tab to the PC. I did that. I connected the Tab to the wall charger overnight. Nothing appeared on the screen. Then the next morning I connected the Tab to the PC, nothing happened. The PC does not recognize that there is anything connected on its USB port.
The Tab is not turning on. I've tried to press (and long press) almost every combination of the Tab's keys I could think of, but the Tab just won't turn on.
I guess I hardbricked my device (as explained in this thread)
I don't think I'll be able to apply the Unbrickable process explained here.
Having said that, my question is: Is there anything else I can do at home to revive my Tab, or do I need to send it to Samsung repair center?
-Adel
I think you brick it.
Flashing bad boot loader kills the tab.
Sent from my GT-I9300 using xda app-developers app
You can also send it to mobiletechvideos.com.
priyana said:
I think you brick it.
Flashing bad boot loader kills the tab.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
If you've completely killed your tab, what can be done to fix it. I have a similar problem with my tab in that it gets to the screen that says samsung galaxy tab and then stops there. I have been searching the net and have rooted the tab and then tried to flash firmware but i am struggling to get the tab to read the ext sd card with the firmware on it.I don't really know my way around this type f thing but have to figure it out because I can't afford to take it in to be repaired right now. Advise will be appreciated.
G
komplotter said:
If you've completely killed your tab, what can be done to fix it. I have a similar problem with my tab in that it gets to the screen that says samsung galaxy tab and then stops there. I have been searching the net and have rooted the tab and then tried to flash firmware but i am struggling to get the tab to read the ext sd card with the firmware on it.I don't really know my way around this type f thing but have to figure it out because I can't afford to take it in to be repaired right now. Advise will be appreciated.
G
Click to expand...
Click to collapse
Your problem is different from OP.
Can you boot to download mode? Can you boot to recovery, if so which recovery (stock or cwm).
Ave you tried Overcome method , as in my signature?
Sent from my GT-P1000 using xda app-developers app
priyana said:
Your problem is different from OP.
Can you boot to download mode? Can you boot to recovery, if so which recovery (stock or cwm).
Ave you tried Overcome method , as in my signature?
Sent from my GT-P1000 using xda app-developers app
Click to expand...
Click to collapse
Hi Priyana,
Thanks for your reply. Yes, as far I could tell from reading up on it, I would guess mine is not bricked.
I can boot to download mode and to recovery - cwm (v3.0.0.5). I have tried downloading Overcome and anything else I thought might work but this is where I get stuck. I've wiped the cache and other things like that described on the net and on videos (actually this is what got me into this in the first place). When I copy a .zip file onto the external sd card and put it in the tab, I can't install the zip from the sd card because it can't find the directory I made. I'll have a look in your signature and see what I can find there but any guidance would be much appreciated.
Komplotter,
Yeah, I am not sure about cwm 3.0 accessing external SD.
Try using overcome restock, jump to page 7 PDF.
Flash stock, then overcome kernel.
That gives cwm 5.0
Sent from my GT-P1000 using xda app-developers app
priyana said:
Komplotter,
Yeah, I am not sure about cwm 3.0 accessing external SD.
Try using overcome restock, jump to page 7 PDF.
Flash stock, then overcome kernel.
That gives cwm 5.0
Sent from my GT-P1000 using xda app-developers app
Click to expand...
Click to collapse
Hi,
I managed to get CWM 5.5.0.4 and get ICS installed in my tab by using two files (CF-Root-TAB7_XX_OXA_JQ1-v3.3-CWM3RFS and P1000XXJQ1_P1000XXJQ1_P1000XXJPZ). I would still like to use Overcome and I have had a brief look at the installation guide. I'll have a more thorough look and then give it a shot. I see that there is a version 4.1.0. Would I use that in that same way as the 4.0.0 ROM, because the Overcome7_ROMv4_Wipe file won't extract (there seems to be a problem with it and I've downloaded it twice).
You don't need the overcome ROM.
Just GB stock safe and overcome kernel.
Sent from my GT-P1000 using xda app-developers app
[Solved!]
Hey everyone!
I followed the Cyanogenmod guide from cm's website on how to install cm 10 on rooted att captivate from android 2.2 froyo.
I followed the guide exactly up to installing cwm recovery via heimdall on a windows 7 (heimdall wouldn't work on an xp I have so I switched to my 7) and everything worked as it said it would, however after finishing and getting the blue bar on the download mode screen, I held the vol up/down and pwr keys per the guide and the phone went to the att logo screen that it shows when you first turn it on and it just flashes that screen.
I can get into download mode still but it won't go into the options screen to hard reset or use cwm recovery.
I rooted it using the superoneclick method and I backedup with titanium.
I haven't been able to find anyone on xda or any other site with the same problem as me (everyone with a similar problem had a different version of android or something so I was afraid to try the solutions given for them.)
Please Help!! Thank you so much in advance!!
http://forum.xda-developers.com/showthread.php?t=731989
Follow this guide after putting your phone into download mode.
Sent from my SGH-I897 using Tapatalk 2
chdiryoung said:
Hey everyone!
I followed the Cyanogenmod guide from cm's website on how to install cm 10 on rooted att captivate from android 2.2 froyo.
I followed the guide exactly up to installing cwm recovery via heimdall on a windows 7 (heimdall wouldn't work on an xp I have so I switched to my 7) and everything worked as it said it would, however after finishing and getting the blue bar on the download mode screen, I held the vol up/down and pwr keys per the guide and the phone went to the att logo screen that it shows when you first turn it on and it just flashes that screen.
I can get into download mode still but it won't go into the options screen to hard reset or use cwm recovery.
I rooted it using the superoneclick method and I backedup with titanium.
I haven't been able to find anyone on xda or any other site with the same problem as me (everyone with a similar problem had a different version of android or something so I was afraid to try the solutions given for them.)
Please Help!! Thank you so much in advance!!
Click to expand...
Click to collapse
See this Captivate - PC Connection Issues, Download Mode and Recovery Mode Help thread on more info on how to get the phone to boot into Recovery...http://forum.xda-developers.com/showpost.php?p=33227541&postcount=1
Sent from my SAMSUNG-SGH-I747 using xda premium
Thanks, I tried getting into recovery mode using the guide on that thread but no luck. I haven't gotten to try the first guide suggested yet so when I have time I'll try that. Thankfully I can get into download mode fine.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Here is the last Stock Firmware released, i897ucKK4 Gingerbread 2.3.5, if ya wanna flash it instead.. http://forum.xda-developers.com/showpost.php?p=18370912&postcount=3 ...Since ya can get in Download mode.
Flashin to KK4 with the Bootloaders included (if u don't already have them) has solved the button combo problems for others who were not able to get into recovery, etc.
Heed all warnings about flashin bootloaders. It only takes a few seconds to flash the boot.bin and sbl.bin, but ya don't wanna interupt the flash durin that process, i.e. loose power, accidently disconnect micro usb/usb cable, etc.
Once ya have the gb boots, there is no need to flash bootloaders again.
Sent from my SAMSUNG-SGH-I747 using xda premium
Thanks so much, I'm gonna try that on Monday first chance I get!
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
4-2ndtwin said:
Here is the last Stock Firmware released, i897ucKK4 Gingerbread 2.3.5, if ya wanna flash it instead.. http://forum.xda-developers.com/showpost.php?p=18370912&postcount=3 ...Since ya can get in Download mode.
Flashin to KK4 with the Bootloaders included (if u don't already have them) has solved the button combo problems for others who were not able to get into recovery, etc.
Heed all warnings about flashin bootloaders. It only takes a few seconds to flash the boot.bin and sbl.bin, but ya don't wanna interupt the flash durin that process, i.e. loose power, accidently disconnect micro usb/usb cable, etc.
Once ya have the gb boots, there is no need to flash bootloaders again.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
How long should/could it take Odin to detect/recognize my captivate? I couldn't wait to try the KK4 flash, but I've waited for about 10 minutes and it's not showing anything in Odin.:\
It should only take a few seconds.
See that Captivate - PC Connection Issues...thread i linked u to in my reply a few posts up.
Sent from my SAMSUNG-SGH-I747 using xda premium
Well I've been up all night lol but I got everything to work!! I guess it all just clicked with me and I understood and found all the answers in threads. THANK YOU SO MUCH!! Your link and Odin one click worked perfect. I think I had a problem with the drivers, that's why it wouldn't detect it. I read in another thread it could be that and I tried reinstalling the Samsung drivers but no luck. So I just switched to my windows xp where I'd never used heimdall drivers(I was on my windows 7) and did it on there, worked perfectly! I then went on to reinstall cwm and then cm 10.1.2 and I love it! Now I'm waiting for the Google play store .zip to download so I can flash it onto my i897! THANKS AGAIN!!! :thumbup:
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
I randomly got stuck into a boot loop on my Samsung Captivate i897. I've read around a bit and seems like I need to use Odin to fix this issue. I couldn't get into download more through the phone buttons so I ordered a JIG. I am now in download mode and have Odin v3.04 installed. Can I use this version or do I need to have a specific version for the Captivate i897? Anyways, I believe I need the PIT and PDA files to do this fix. If so, can someone link me to them? I am not able to find a working link for these 2 files.
Any help would be appreciated :good:
miqballin said:
Any help would be appreciated :good:
Click to expand...
Click to collapse
What ROM you are currently running and what kernel?
Might be software or hardware issue, more information is needed.
Val D. said:
What ROM you are currently running and what kernel?
Might be software or hardware issue, more information is needed.
Click to expand...
Click to collapse
Sorry, It has been a while and I cannot remember I wish I could get into SOMETHING on the phone to retrieve this information instead of staring at the loading screen forever
There is a sticky thread in Captivate Android Development with Odin one-click stock ROMs. Flash the phone back to stock ROM and see if it solves the problem. In your case I would use Android 2.1 package without bootloaders, because there is no information about what bootloaders you have. Read carefully the flashing instructions and you should be fine.
You can also use the universal Odin from the galaxy s2/3/4 forums. I've used it a bit with no issues.
Sent from my GT-I9000 using XDA Premium 4 mobile app
If u have a custom rom u also have custom recovery ? Flash ur backup of original or other. Can still put random backup or custom rom from sd card. If ur crazy about that particular rom then get a fresh copy.
Sent from my SCH-I535 using xda app-developers app
Odin Version: 1.83, 1.85 or Heimdall
Pit: Heimdall can extract PIT
I'd recommend getting the KK4 Heimdall One Click, since it works cross-platform, its safer than Odin and it comes with bootloader in case you wanted to try the i9000 GB BL/Any i9000 based rom
thebulletfromhell said:
Odin Version: 1.83, 1.85 or Heimdall
Pit: Heimdall can extract PIT
I'd recommend getting the KK4 Heimdall One Click, since it works cross-platform, its safer than Odin and it comes with bootloader in case you wanted to try the i9000 GB BL/Any i9000 based rom
Click to expand...
Click to collapse
Playing with other bootloaders (I9000) is not something to get started with.. I highly discourage people of doing so unless they fully understand what they're doing.
Sent from my SGH-I747 using xda app-developers app
BWolf56 said:
Playing with other bootloaders (I9000) is not something to get started with.. I highly discourage people of doing so unless they fully understand what they're doing.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
But if you want to use an i9000 rom, you're going to need the BL though. For AOSP, either is fine I'm pretty sure
thebulletfromhell said:
But if you want to use an i9000 rom, you're going to need the BL though. For AOSP, either is fine I'm pretty sure
Click to expand...
Click to collapse
True. I guess what I meant is more along the lines of don't play with those if you're getting started or getting back into flashing. Bootloaders are the only way to brick your phone so the less you play with them, the better!
Sent from my SGH-I747 using xda app-developers app
Val D. said:
There is a sticky thread in Captivate Android Development with Odin one-click stock ROMs. Flash the phone back to stock ROM and see if it solves the problem. In your case I would use Android 2.1 package without bootloaders, because there is no information about what bootloaders you have. Read carefully the flashing instructions and you should be fine.
Click to expand...
Click to collapse
Thanks for all the replies people. I have downloaded Android 2.1 w/o bootloader. Currently I am viewing this thread [http://forum.xda-developers.com/showthread.php?t=1350266] as I believe this is the one I need to follow before flashing, correct? Or did you mean another thread when you mentioned 'Read carefully the flashing instructions' ?
Thanks once again.
miqballin said:
Thanks for all the replies people. I have downloaded Android 2.1 w/o bootloader. Currently I am viewing this thread [http://forum.xda-developers.com/showthread.php?t=1350266] as I believe this is the one I need to follow before flashing, correct? Or did you mean another thread when you mentioned 'Read carefully the flashing instructions' ?
Thanks once again.
Click to expand...
Click to collapse
That is the one. You'll need the gb bootloaders if you don't already have them.
Sent from my SGH-I747 using xda app-developers app
BWolf56 said:
That is the one. You'll need the gb bootloaders if you don't already have them.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Ok thanks. gb = gingerbread right?
Also, I am stuck at this step: "Find a neat-o ROM from Captivate Development Section and get it onto your internal SD card (the one you cant remove) download using phone internet browser or download and copy to phone using PC."
When I plug phone into PC through USB, My Computer shows 2 new drives but I am unable to open either
Go to Settings/ Applications/ USB settings/ then select Mass storage, then back out to Home screen. Then when u connect ur phone to ur pc, look at ur Captivate screen, it will show USB connected, then u have to tap the button that says...Connect storage to PC.
That should do it. :thumbup:
4-2ndtwin said:
Go to Settings/ Applications/ USB settings/ then select Mass storage, then back out to Home screen. Then when u connect ur phone to ur pc, look at ur Captivate screen, it will show USB connected, then u have to tap the button that says...Connect storage to PC.
That should do it. :thumbup:
Click to expand...
Click to collapse
Think you missed the fact that I can't load into my phone The issue at hand is a boot loop
Can ya reboot into Recovery ? If yes then wipe data/factory reset, then reboot.
If not and u can get into download mode u can try one of the stock KK4 One Clicks that i put together. They will wipe data, dbdata and cache for u and will put u on complete stock i897uckk4 gingerbread 2.3.5 firmware.
One clicks found here... http://forum.xda-developers.com/showpost.php?p=18370912&postcount=3
4-2ndtwin said:
Can ya reboot into Recovery ? If yes then wipe data/factory reset, then reboot.
If not and u can get into download mode u can try one of the stock KK4 One Clicks that i put together. They will wipe data, dbdata and cache for u and will put u on complete stock i897uckk4 gingerbread 2.3.5 firmware.
One clicks found here... http://forum.xda-developers.com/showpost.php?p=18370912&postcount=3
Click to expand...
Click to collapse
I am trying to do what was suggested earlier in this thread first. I will try your suggesstion after I am just stuck on trying to access the phone internal SD but my computer is not recognizing the device
miqballin said:
I am trying to do what was suggested earlier in this thread first. I will try your suggesstion after I am just stuck on trying to access the phone internal SD but my computer is not recognizing the device
Click to expand...
Click to collapse
You might wanna check your drivers, try another cable and another port. If all fails, try another pc.
Sent from my SGH-I747 using xda app-developers app
BWolf56 said:
You might wanna check your drivers, try another cable and another port. If all fails, try another pc.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
The problem isn't with the cable, drivers, or ports I believe. It is because I do not have USB debugging enabled; and there is no way I can enable it since I cannot get into my phone :/ Is it possible to enable it through the computer via any software?
miqballin said:
The problem isn't with the cable, drivers, or ports I believe. It is because I do not have USB debugging enabled; and there is no way I can enable it since I cannot get into my phone :/ Is it possible to enable it through the computer via any software?
Click to expand...
Click to collapse
Usb debugging is only needed for ADB and couple other things. It doesn't change anything to the pc recognizing your phone. (Think about it, out of the box, you can connect it to your pc and it doesn't have usb debugging on)
Sent from my SGH-I747 using xda app-developers app
Hi to everyone who's reading this.
I have got stuck with an Note GT-N7000 from a friend. It was running the original Samsung firmware and never flashed before. Now the device is stuck at the bootscreen.
If I press the Home+VolUp+Power, it just flashes the bootscreen (see IMG_20131006_212031.jpg) then the screen is black again and shortly after that the boot screen shows again. For comparison if I just press power then this short flash doesn't happen. But the same bootscreen is shown.
I have tried to flash PhilZ-cwm6 recovery, but Odin3 stops at "NAND Write Start" no error line or anything (see Odin3.jpg). After an reboot there was that yellow triangle indicating a modification of the firmware. But no change to the problem.
To provide as much info as possible I also attached a photo of the label below the battery (see IMG_20131006_211932.jpg).
The device is older than 2 years now, so there is now warranty.
The behavior is somehow similar to:
http://forum.xda-developers.com/showthread.php?t=2466339
I'm a little bit afraind i could brick it even while trying to repartition the phone.
http://forum.xda-developers.com/showthread.php?t=1667886
Another thread discribing pit, but i'm not stuck at factoryfs. May this apply to me too?
http://forum.xda-developers.com/showthread.php?p=26285877
Thanks in advance for any help.
Regards Marco
Stuck at flashing kernel? Hmmm. Try a different USB cable, front port, kill all kies processes is any, try a different PC.
Friendly word of advice, blank out your imei from the second image.
Sent from my C6833 using XDA Premium 4 mobile app
nokiamodeln91 said:
Stuck at flashing kernel? Hmmm. Try a different USB cable, front port, kill all kies processes is any, try a different PC.
Click to expand...
Click to collapse
Ok, I tried the same procedure on my notebook using the cable from my Wonder with the same result. As I'm using the drivers that came with Windows Update, I have no kies installed anyways. I Tried to install the drivers from this thread http://forum.xda-developers.com/showthread.php?t=1424997. But I think my system isn't using them.
Could that Microsoft provided drivers be the problem?
As the battery only has 3.1 volts with no change over several hours of charging and the phone doesn't enter the download mode anymore with a battery low error. I'll first try to replace it with a new one. Maybe that's that cause after all. I just hope the charging circuits aren't broken.
SpyderTracks said:
Friendly word of advice, blank out your imei from the second image.
Sent from my C6833 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks, for that advice! Didn't know that the IMEI can be used to blacklist stolen devices (Wikipedia). Someone might do a prank with it.
para756 said:
Ok, I tried the same procedure on my notebook using the cable from my Wonder with the same result. As I'm using the drivers that came with Windows Update, I have no kies installed anyways. I Tried to install the drivers from this thread http://forum.xda-developers.com/showthread.php?t=1424997. But I think my system isn't using them.
Could that Microsoft provided drivers be the problem?
As the battery only has 3.1 volts with no change over several hours of charging and the phone doesn't enter the download mode anymore with a battery low error. I'll first try to replace it with a new one. Maybe that's that cause after all. I just hope the charging circuits aren't broken.
Thanks, for that advice! Didn't know that the IMEI can be used to blacklist stolen devices (Wikipedia). Someone might do a prank with it.
Click to expand...
Click to collapse
Don't think the ms drivers work at all for proper connection.
Sent from my C6833 using XDA Premium 4 mobile app
SpyderTracks said:
Don't think the ms drivers work at all for proper connection.
Sent from my C6833 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Ok, i got the new battery and I've got the windows drivers working. But still with the same result. Any other ideas?
Should i try a different Flash file?
I allready downloaded the an original firmware but i'm afraid to do even more damage, if I don't wipe data and cache. So I wanted to flash the recovery first.
Are there any other steps that i have to do first? Maybe i'm missing something.
Have you installed kies? If not, install that first. It will install all three required drivers. Then go to task manager and kill all process that relates to kies. Then reboot the phone into download mode and flash again. You can also try the firmware you downloaded using original Pit file with repartition.
nokiamodeln91 said:
Have you installed kies? If not, install that first. It will install all three required drivers. Then go to task manager and kill all process that relates to kies. Then reboot the phone into download mode and flash again. You can also try the firmware you downloaded using original Pit file with repartition.
Click to expand...
Click to collapse
I had no keys installed, but I did now. Unfortunately I think the drivers in mentioned before seam to be the same.
Meanwhile I also tried to flash the original firmware and a Gingerbread Firmware form that brick safe install thread. In comparison to the CWM there is no progress on the green bar, just 2 pixel. I thought that I might have not waited long enough, but for that CWM flash the bar was completed for at least 10 minutes.
As I Installed Kies now I saw that option that allows a firmware update through kies. But it doesn't seam to initialize the update, quite similar to the behavior Odin shows.
I don't' like messing around without a way to identify that I have the right set of drivers installed. I tried to find some information about the drivers through the forum search and Google, but so far with no result.
I attached the drivers I use. If you (or someone else) did this before and got a working configuration, would you be so kind and make some screenshots of the drivers you use?
The same game with the the USB-Cable, has someone a correct wiremap, that I could check? (obviously not easy for the mini-USB connector)
By PIT-File you mean the "Pit file for 16GB model" from this thread? http://forum.xda-developers.com/showthread.php?t=1424997 or just the checkbox Re-Partition? That's really the last thing I want to try now, because I know to less about internal structure of the device. If Re-Partition fails and the downloader (Power+VolDown+Home) is on that partition I might kill the last point I can modify this Note ATM.
Just something more i want to add: Odin doesn't show that blue progress bar. I never used Odin before, but i searched for the process on YouTube and i just guess that Odon mode on the Galaxy Note it should show that bar too.
Meanwhile I also tried to flash a Krenel zImage with heimdall (The Kernel zImage is linked from the recovery CM tells to use in the installation process with heimdall). As Heimdall brings it's own drivers and behaves similar, I would guess, that the drivers at not the problem anyways.
How did you flash the gb rom? You need to try a rom flash using odin. Yes I mean the 16 gb pit if you have the 16 gb note.
Do you have access to Cwm recovery?
---------- Post added at 02:55 AM ---------- Previous post was at 02:52 AM ----------
Odin 3+ has a blue progress bar and old odin has green. When flashing firmware the download mode on phone also shows a green progress bar which is the indication of write.
When you connect the phone in download mode does your phone screen say "downloading"?
nokiamodeln91 said:
How did you flash the gb rom? You need to try a rom flash using odin. Yes I mean the 16 gb pit if you have the 16 gb note.
Do you have access to Cwm recovery?
Click to expand...
Click to collapse
To flash GB I followed this thread http://forum.xda-developers.com/showthread.php?t=1763151 to step 10.
The Phone was stock before it broke. I just hope i didn't confuse you. I tried several aproaches now.
All the roms i tried so far have been single file roms.
The 1st thing i did was trying to flash PhilZ-cwm6 recovery.
Then I replaced the battery, because odin download mode stated the battery is beeing low.
I repated the process with different versions of the drivers provided in this forum and by kies.
After that i tried different Firmware versions.
And finally i tried heimdall because it seams to be a good alternative to Odin.
Yes I am a bit confused. May be not because of your steps but too much to read..
Is recovery mode accessible? As your last post say Cwm recovery flash.
When the phone is in download mode, what's displayed on the screen?
nokiamodeln91 said:
Yes I am a bit confused. May be not because of your steps but too much to read..
Is recovery mode accessible? As your last post say Cwm recovery flash.
When the phone is in download mode, what's displayed on the screen?
Click to expand...
Click to collapse
OK i'll try it short
Recovery never was accessible. Download mode ist shown by the screenshot in the 1st post. Only the counter went up to 9.
There is no download mode screenshot in the first post. Could you post again.
nokiamodeln91 said:
There is no download mode screenshot in the first post. Could you post again.
Click to expand...
Click to collapse
I'm verry sorry, that was my fault. I added it to the 1st post. It's getting late for me.
Yeah. Just saw it. All looks fine. I cannot find a reason why odin is not flashing even the kernel. If bricked, it's usually in the system partition, then also kernel should be flashed successfully.
Tried changing the use cable?
nokiamodeln91 said:
Yeah. Just saw it. All looks fine. I cannot find a reason why odin is not flashing even the kernel. If bricked, it's usually in the system partition, then also kernel should be flashed successfully.
Tried changing the use cable?
Click to expand...
Click to collapse
Yeah, tried 2 cabels and 2 PCs so far...
I will report the result's here when I tried the repartitioning. So have a good day/night and thanks for your time.
I'm sorry if this was already covered. If you flash JUST philz with Odin, can you get into recovery?
Sent from my GT-N7000 using Tapatalk 2
AndroidSlave said:
I'm sorry if this was already covered. If you flash JUST philz with Odin, can you get into recovery?
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Yep, that was the 1st thing I was trying. But I cant flash philz or anything else. Thats all the problem.
I'm thankfull for anyone who gives it a try.
para756 said:
Yep, that was the 1st thing I was trying. But I cant flash philz or anything else. Thats all the problem.
I'm thankfull for anyone who gives it a try.
Click to expand...
Click to collapse
Just throwing ideas out and sorry if you're already doing it...
I always run Odin as administrator.
I would personally start from scratch regarding drivers, delete kies and Samsung drivers, then go into device manager and check there aren't any remaining ms drivers. Reboot and reinstall kies, then shut down kies processes.
I always put the Odin folder on root of c.
The symptoms point to driver issues I think, that's where you usually see this kind of behaviour.
Sent from my C6833 using XDA Premium 4 mobile app
OK, I SuperBricked (no ODIN) it now. For others with the same symptomes, don't use Re-Partition. As I won't try it with JTAG maybe the device goes to eBay. Thanks to everyone and don't worry, it would have been broken anyways.
Maybe if someone is in the same situatuon: Try harder on different cable/drivers/os before using a Pit file.