Related
Purchased two Bell Canada Samsung Galaxy S as-is from local kijiji.
They all performing the same thing, rebooting at Galaxy S logo, GT-I9000M page, it won't go any further. and there is no recovery mode at start-up.
Here are the steps which I have played with for past two days.
1. Trying to get to recovery mode
- tried ADB, but it doesn't work, since "USB debug" is not on, and it won't accept as a device, and I am not able to turn that on, since I can't even get on the main screen.
- tried three key combo, vol up + home + power on, at least a hundred times for past two days, it doesn't work. fortunately download mode is working (at least I have more option to try). and I know how to get to recovery mode, I played with my friend's before.
2. Trying to use ODIN to flash the firmware
- unchecked "re-partition", unchecked "bootloader", pick 512 as PIT and then choose following as PDA
JH2, JK3, JK4, JL2
always successful on refresh, but phone still does the same, stuck at LOGO page
- also tried, checked "re-partition", and checked "bootloader", pick 512 as PIT and repacking following into PDA, Phone/Modem, CSC, still won't work...
JP series, JH, JK series, JL
At the beginning I though it was problem on CSC, I didn't use correct one to match my phone model #, but what's mine??? I can't go into my phone to check. I checked my friend's I9000, he used I9000BMCJK4, and I assume all JK series should work with me, since our IMEI are similar. And I tried many times on different cache.rft as CSC.tar, still no luck for me
I go crazy now, $400 USD gone. Seriously needing help. Any help is highly appreciated.
try the one jl2 download file and samsungfirmwares.com it flashes a special bootloader that may fix things.. it should be a single file you put in as pda nothing else..
if not they may have permantely trashed internal memory and you are sol.
lgkahn said:
try the one jl2 download file and samsungfirmwares.com it flashes a special bootloader that may fix things.. it should be a single file you put in as pda nothing else..
if not they may have permantely trashed internal memory and you are sol.
Click to expand...
Click to collapse
I have tried one of JL2 file from somewhere (don't remember where), but I will get one JL2 file from samsungfirmwares.com again, see if that works.
Do you mean, only choose the file for PDA, left PIT empty, and get everything uncheck?
permantely trashed internal memory? are these the common problem with this model? I got two of these, and both of them have the same issue, I think, there should be a way to slove it, right? Should I give up these thoughts???
anyways, thanks anyways, I will report back after I flesh JL2 from samsungfirmwares.com
Ok, you need to flash jl2 with pda, repartition, pit file and the secondary boot loader... The SBL(secondary boot loader) is what will actually fix your phone
Hopefully it will work.
Sent from my GT-I9000m using XDA App
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> cache.rfs
<ID:0/005> Sbl.bin
<ID:0/005> zImage
<ID:0/005> factoryfs.rfs
<ID:0/005> modem.bin
<ID:0/005> param.lfs
<ID:0/005> Removed!!
<ID:0/005> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
Still no luck on this firmware, I9000UGJL2, by the way, should be samfirmware.com instead of samsungfirmwares.com
above message I got from ODIN3 v1.30, it looks fine for refresh, but it doesn't work. the phone keep rebooting, it won't pass LOGO page, again, only download mode I can use.
HELP! HELP! HELP!
any leads???
is "<ID:0/005> Sbl.bin" secondary boot loader???
I got the file for PDA, I9000UGJL2, is this the one? if not, where should I get it? how do I update it?
I did it again, with "re-partition" checked, PIT choosed as s1_odin_20100512.pit, I9000UGJL2_homebinary_add_param.tar (which I just downloaded from samfirmware.com), it still doesn't work.
anything else I can try? maybe something simple I didn't do???
I too am a bell user I had the same problem a few weeks back. This is going to sound messed up, but i'm going to do my best to explain how I solved the problem.
DO NOT MULTI-TASK ON THE COMPUTER WHILE DOING THIS. CLOSE ALL OTHER APPLICATIONS.
-remove external sd and sim card
-go into download mode (hold vol down+power+home).
-turn on ODIN
-plug in usb (both computer and phone)
-check re-partition
-ONLY use the 512 pit file. DO NOT use a rom.
-start ODIN and it should only take a minute. this will wipe your device completely but still allow you to access download mode.
- remove usb close ODIN
- start up ODIN again and connect usb
- use 512 pit and JP1 or JP2 rom.
- After flashing, this SHOULD give you an error and send you straight into recovery mode. you're looking for a specific error code. you need the error to have "sl01" or "sl10" (whichever, i forgot which it was) at the end of the path. if the end of the path has "m(something)" then use a different rom till you get the "sl10".
these errors are internal sd errors which your phone is experiencing right now, but the phone is fixable from the "sl10" error.
continuing...
- once you get the "sl10" error, close ODIN, unplug USB, turn off phone.
- go back into download mode.
- boot up ODIN with 512 pit and ULG2 rom.
- plug in phone
- start flashing.
this can give you two outcomes:
1) fixed galaxy S
2) error code with "m(something)" at the end of the error path.
if it's #2 do this all over again until it works.
This took me 3 days to figure out these steps, 10 hours each day. although it doesnt seem to make sense, my phone is working right now and it is where I am writing all this from. My only explanation is that Bell gets ****ty product from samsung. it's almost impossible to flash custom roms on a bell galaxy i9000 because the internal SD seems to have trouble being mounted.
i hope this helps and i hope it doesnt take long for you to fix this problem.
btw, if it does get fixed data connection wont be available. to enable it go to your apn settings. create new named "Bell" with apn as "pda.bell.ca" and leave all other options blank. data should be restored after that.
Sent from my GT-I9000M using XDA Premium App
jt_kyle said:
I too am a bell user I had the same problem a few weeks back. This is going to sound messed up, but i'm going to do my best to explain how I solved the problem.
DO NOT MULTI-TASK ON THE COMPUTER WHILE DOING THIS. CLOSE ALL OTHER APPLICATIONS.
-remove external sd and sim card
-go into download mode (hold vol down+power+home).
-turn on ODIN
-plug in usb (both computer and phone)
-check re-partition
-ONLY use the 512 pit file. DO NOT use a rom.
-start ODIN and it should only take a minute. this will wipe your device completely but still allow you to access download mode.
- remove usb close ODIN
- start up ODIN again and connect usb
- use 512 pit and JP1 or JP2 rom.
- After flashing, this SHOULD give you an error and send you straight into recovery mode. you're looking for a specific error code. you need the error to have "sl01" or "sl10" (whichever, i forgot which it was) at the end of the path. if the end of the path has "m(something)" then use a different rom till you get the "sl10".
these errors are internal sd errors which your phone is experiencing right now, but the phone is fixable from the "sl10" error.
continuing...
- once you get the "sl10" error, close ODIN, unplug USB, turn off phone.
- go back into download mode.
- boot up ODIN with 512 pit and ULG2 rom.
- plug in phone
- start flashing.
this can give you two outcomes:
1) fixed galaxy S
2) error code with "m(something)" at the end of the error path.
if it's #2 do this all over again until it works.
This took me 3 days to figure out these steps, 10 hours each day. although it doesnt seem to make sense, my phone is working right now and it is where I am writing all this from. My only explanation is that Bell gets ****ty product from samsung. it's almost impossible to flash custom roms on a bell galaxy i9000 because the internal SD seems to have trouble being mounted.
i hope this helps and i hope it doesnt take long for you to fix this problem.
btw, if it does get fixed data connection wont be available. to enable it go to your apn settings. create new named "Bell" with apn as "pda.bell.ca" and leave all other options blank. data should be restored after that.
Sent from my GT-I9000M using XDA Premium App
Click to expand...
Click to collapse
great!!! Another option I can try. Thank you.
I will try it out right after my work. so the idea behind this, is bricking it into recovery mode and S10 error code. and then fresh right back with correct ULG2 (is this correct? frist time heard about this rom)
anyways, I will post back with result.
Where can i find this ULG2 rom?
did it work?
Thananjeyen said:
Where can i find this ULG2 rom?
Click to expand...
Click to collapse
I think jt_kyle meant I9000UGJL2
and you can get them from samfirmware.com
Paallikko said:
did it work?
Click to expand...
Click to collapse
yes, lucky I got one of my Bell Samsung phone work. Since I done a million times of refreshing and rebooting and etc... I am not sure what I did, now I still trying to remember last 10 steps I did to make this work.
But definitely, I could not have done this repair without jt_kyle. Thank you so much, jt_kyle.
jt_kyle, Thank you!!!
but none of JP1 or JP2 is givining me the error "tl10", I tried
I9000DXJP1
I9000TGYZSJP2
I9000XXJP1
I9000XXJP2
it come out error started with "m..."
I just keep refreshing each on PDA 3 to 4 times, and choose with re-partition or without. At the end I try a few another ROMs as well, I still get no "tl10", but somehow, just that magicical moment, the screen come out a set of commands that look like format sd card, so I got excited, fresh it with JL2. It is back to work.
still no clue the steps of fixing the problem.
one done, the another one to go.
any more ideas please, and I think I am really close to solve this one now.
Thank you All
FIX
Look for a file called I9000UGJL2Complete follow the same steps pit and so on after your phone boots up youll have a blank baseband then you get the I9000UGJL2 modem and flash it where it says phone this has unbricked a few for me hope this helps
EVERED78 said:
Look for a file called I9000UGJL2Complete follow the same steps pit and so on after your phone boots up youll have a blank baseband then you get the I9000UGJL2 modem and flash it where it says phone this has unbricked a few for me hope this helps
Click to expand...
Click to collapse
if you have a way for me to give you this file i do have it just not sure how to do so because its 286MB
Could it be dead?
Since you have one of the infamous i9000m's it might also just be a dead SD card? You might try calling samsung and trying to get it repaired under warrenty as they are all under a year old (try and flash jl2 first even it will not boot up). It sounds like no receipt may not be an issue.
Lots of info from allgamer's list of i9000m issues in the general section.
At least you have one in the meantime!
same problem
Hey ive got pretty much the same problem that you had. Only differences are that I'm from Australia and am on Virgin network.
My phone became semi bricked one day when it restarted and since the 3 button combinations did not work i ordered in a USB jig which i received today. I used odin 1.8 to try and flash to I9000BVJJPD which i got from samfirmware.com but it ended up stuck on the logo screen vibrating once in a while. I decided to repeat it with no avail and began to use other roms and use .PIT.
This is where my phone became even worse and is now in it's current position; rebooting at the GT-I9000 page. I tried the method that jt_kyle suggested, substituting australian roms instead but it is still in the same position.
Does anyone have any other suggestions or should i just try getting a warranty?
Look for the ugjl2 complette and repeat what I said
Sent from my GT-I9000 using XDA Premium App
EVERED78 said:
if you have a way for me to give you this file i do have it just not sure how to do so because its 286MB
Click to expand...
Click to collapse
I think I have this I9000M_JL2_JL2_JL2_JL2_UG_BMC file, is the same file that you are talking about? JL2 Complete?
I tried this file many times, it won't work neither.
for past one hour I played around this phone, trying to repeat the steps I did for the first phone. Unfortunately, nothing is working for me AGAIN!
but I got these error page all the time, like following...
update media, please wait
E:Can't mount /dev/block/mmcblk0p1
(I/O error)
E:copy_dbdata_media:Can't mount SDCARD:
I think that's bigest problem in my case, and for a lot of people in this forum. Do any people has a good solution for this???
Hello... just got a Galaxy S new and I think I have fully bricked it.
It was on 2.2 stock and I installed Darkys v10.1 extreme rom on it following the steps in this guide..
http://www.darkyrom.com/community/i...-darkyrom-gingerbread-jvh-noob-friendly.3080/
I first installed
- Ficeto_JVH_I9000_Odin:
- DarkyROM_v10.1:
and installed the PIT and PDA.
I decided that I didn't like Darkys and tried to install Cyanogenmod 7 on it..
my friend said I needed to install a PIT first, then install a JPY rom afterwards.
I used Odin 1.3 and selected this pit "s1_odin_20100512"
and I think I pressed Re-Partition as previously in the guide that was what they did..
Auto reboot and F. Reset time were both ticked
This was the log
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> Removed!!
<ID:0/003> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
How can I save my new baby?!!!
When I mean bricked, I don't think it turns on at all...... doesn't light up or enter recovery.
Most ironic is, I bricked it relatively easily when people said it's virtually unbrickable.
!!!!!!!!
You may never flash just a pit file!!!
You only use it when you flash a 3file rom.
That's the same for repartition.
If you can get it in download mode, everything is fine.
Else your screwed...
A sgs is virtually unbrickable if you had flashed it correctly.
When you don't know how to flash always follow a tut!!!
Sent from my GT-I9000 using Tapatalk
I never realised you could just use a .pit without the rest.
The .pit file isn't "installed" it is a file which tells the system how to wipe and then repartition the memory in your phone. Essentially you wiped the phone without installing anything on it after that. I am not sure if it wipes the bootloaders as well (at the very least it has partially wiped them if recovery is not working)
If you can get download mode to work, then you should be alright. If it doesn't work, a jig may or may not help. If you can not get download mode to work, then you have no other recourse than to send it back for repairs. They will need to replace the erased bootloaders if this is the case.
If on the other hand you do manage to get it to work, read very carefully the process that is actually involved in flashing firmwares with odin/heimdall. Yes it is very hard to permanently brick your phone if you know what you are doing. Hell in most cases even if you don't know what you're doing it's hard to permanently brick your phone. You went ahead and did one of the few things that is a danger area though. In general though, you should not repartition (ie use the .pit file) unless necessary (although repartitioning wont really do anything bad it's completely unneeded in most cases) and don't flash boot-loaders unless necessary. NEVER repartition without flashing a rom with it.
Shanakin said:
I never realised you could just use a .pit without the rest.
The .pit file isn't "installed" it is a file which tells the system how to wipe and then repartition the memory in your phone. Essentially you wiped the phone without installing anything on it after that. I am not sure if it wipes the bootloaders as well (at the very least it has partially wiped them if recovery is not working)
If you can get download mode to work, then you should be alright. If it doesn't work, a jig may or may not help. If you can not get download mode to work, then you have no other recourse than to send it back for repairs. They will need to replace the erased bootloaders if this is the case.
If on the other hand you do manage to get it to work, read very carefully the process that is actually involved in flashing firmwares with odin/heimdall. Yes it is very hard to permanently brick your phone if you know what you are doing. Hell in most cases even if you don't know what you're doing it's hard to permanently brick your phone. You went ahead and did one of the few things that is a danger area though. In general though, you should not repartition (ie use the .pit file) unless necessary (although repartitioning wont really do anything bad it's completely unneeded in most cases) and don't flash boot-loaders unless necessary. NEVER repartition without flashing a rom with it.
Click to expand...
Click to collapse
Thanks for your long and detailed explanation of what I have exactly done..
I had kind of guessed by now of what I have done.. which is very unfortunate as like you said, "I never realised you could just use a .pit without the rest. ".
Such a dangerous thing, I wouldn't have expected the software to allow me to do that
Instead of making a jig with resistors, I have read that you can cut a micro usb cable instead??
Would you be able to direct me to other resources or information on how to make one?
If a jig doesn't work, how much money am I looking at for someone to fix it?
Thank you very much,
Kind regards
you never said whether download mode works or not ??
azzledazzle said:
you never said whether download mode works or not ??
Click to expand...
Click to collapse
From what it appears, it doesn't seem to turn on at all...
Removed because azzledazzle beat me to it
Altimas said:
So can you confirm you cannot get into download mode?
Click to expand...
Click to collapse
How can I confirm that I can't get into download mode?
Volume DOWN button + home button + power button all at same time,
azzledazzle said:
Volume DOWN button + home button + power button all at same time,
Click to expand...
Click to collapse
Unfortunately it's not looking like it works :'(
USB JIG may be your only hope then.
but before you do that, take battery out for 5 mins. Then hold the 3 button combo for DOWNLOAD mode, THEN put the battery back in, STILL holding the 3 button combo.
and also, does the phone do anything when plugged in ?? no charging indicator or lights, vibrations ???
azzledazzle said:
USB JIG may be your only hope then.
but before you do that, take battery out for 5 mins. Then hold the 3 button combo for DOWNLOAD mode, THEN put the battery back in, STILL holding the 3 button combo.
and also, does the phone do anything when plugged in ?? no charging indicator or lights, vibrations ???
Click to expand...
Click to collapse
I will try taking the battery out and putting it back in with the three buttons together.
Also, no light or vibration when plugged in USB..
If the jig fails, any idea of the ball park for the cost for it to be repaired?
if the jig fails, send it off to samsung a blame it on a failed KIES update, act dumb and hope for the best, chances are they wont charge
azzledazzle said:
usb jig may be your only hope then.
But before you do that, take battery out for 5 mins. Then hold the 3 button combo for download mode, then put the battery back in, still holding the 3 button combo.
And also, does the phone do anything when plugged in ?? No charging indicator or lights, vibrations ???
Click to expand...
Click to collapse
yes omfg you don't understand how happy i am righ tnow.
I took out the battery and did what you said and i get the downloading screen now.
It is 1am in sydney and i am willing to stay up to get my phone on the downloading screen!!
It has finally turned on!
Please help me, what do I need to do next?
jing713 said:
yes omfg you don't understand how happy i am righ tnow.
I took out the battery and did what you said and i get the downloading screen now.
It is 1am in sydney and i am willing to stay up to get my phone back up running!!!!
Please help me !
Click to expand...
Click to collapse
first of all CHILL OUT !! dont panic or you could make the same mistake.
Download this http://sourceforge.net/projects/teamhacksung/files/galaxys/GT-I9000_FROYO_FULL_PDA.tar/download
DO NOT use pit and DO NOT select re-partition
let me know the outcome, if the above firmware dont fix it, we need to get you a 3 file firmware THEN and only THEN do we add PIT and REPARTITION
azzledazzle said:
first of all CHILL OUT !! dont panic or you could make the same mistake.
Download this http://sourceforge.net/projects/teamhacksung/files/galaxys/GT-I9000_FROYO_FULL_PDA.tar/download
DO NOT use pit and DO NOT select re-partition
let me know the outcome, if the above firmware dont fix it, we need to get you a 3 file firmware THEN and only THEN do we add PIT and REPARTITION
Click to expand...
Click to collapse
Thanks for the encouraging words..
I'm downloading it now, 370mb?!
After download, do I use Odin 1.3 or 1.7 to flash the TAR and ONLY THE TAR?
BTW I'm with Windows 7 64 bit, I've seen guides saying 1.7 may not work perfectly... however It worked fine for me with installying Darkys rom..
i use 1.7 too, also running win 7 64 bit. no problems for me.
the firmware is a FULL FROYO including all dbdata's bootloaders, kernel the full monty
only insert the .tar file in the PDA section of odin.
it may not fix you completely, but it will restore most of the corruption, however we may need a 3 file firmware with PIT to fix the file system.
but we will cross that bridge when we need to
azzledazzle said:
i use 1.7 too, also running win 7 64 bit. no problems for me.
the firmware is a FULL FROYO including all dbdata's bootloaders, kernel the full monty
only insert the .tar file in the PDA section of odin.
it may not fix you completely, but it will restore most of the corruption, however we may need a 3 file firmware with PIT to fix the file system.
but we will cross that bridge when we need to
Click to expand...
Click to collapse
Ahh okay.
At the moment, I'm getting a "USB Device Not Recognized" notice with plugging it in..
right ok........
do you have kies installed on your PC ?? if you do uninstall it, and then re install it, this will re-install the drivers,
if you dont have kies, try this http://forum.xda-developers.com/showthread.php?t=728929
Finally, when you are about to flash using odin MAKE SURE KIES IS **NOT** RUNNING, EVEN IN THE ICON TRAY.
azzledazzle said:
right ok........
do you have kies installed on your PC ?? if you do uninstall it, and then re install it, this will re-install the drivers,
if you dont have kies, try this http://forum.xda-developers.com/showthread.php?t=728929
Finally, when you are about to flash using odin MAKE SURE KIES IS **NOT** RUNNING, EVEN IN THE ICON TRAY.
Click to expand...
Click to collapse
Nah I don't have kies.... I installed the drivers itself instead. hmm hah.
<ID:0/012> Added!!
<ID:0/012> Odin v.3 engine (ID:12)..
<ID:0/012> File analysis..
<ID:0/012> SetupConnection..
<ID:0/012> Initialzation..
<ID:0/012> Get PIT for mapping..
does nothing else... Don't know what to do. I mean, I can't plug it out or turn off, right?
I tried to get back to the stock rom... and yes, i did an factory reset and cache wipe etc before..
Anyone who can help me?
NP, this thing happened to me... Is it because you clicked on re-partition...?
I cant guarantee, but i unplugged it, and it was soft bricked, i then flashed it without repartition checked.
Hopefully works for you
GL
you can indeed uplug it in this situation. Pull the battery and let it sit, go back into download mode and reflash the stock firmware.
If you check re-partition, make sure you have a pit 512 file that you are flashing. If you do not have a pit file, then make sure re-partition is unchecked.
Thanks both.
I did not check re-partition. I am not experienced with all this and i'm fairly new.
I just tried to flash the stock rom, because I couldn't boot up properly.
Ok. I'm trying to flash it again. It's actually doing more then it did before. I'll let you know
EDIT
OK.
I tried again but it was stuck again. Now at like 95% of the completion -.-
I tried for the third time. It keeps failing ....
anyone who can help me with this?
btw, i just noticed i posted this in the Galaxy S forum accidently. I have a SGSII instead. But I think it doesn't make any difference?
edit:
After the fourth time it worked..
sebas156 said:
btw, i just noticed i posted this in the Galaxy S forum accidently. I have a SGSII instead. But I think it doesn't make any difference?
edit:
After the fourth time it worked..
Click to expand...
Click to collapse
Lol fourth time...
SGSII your using the correct firmware then right? The link i gave shouldn't apply to you it could brick your phone...
Yh, Odin can be annoying sometimes, you can either wait a while and try again later, restart and try again, or use heimdall. Or you could flash a zip through recovery (not sure if that last one works if you cant get past boot)
Talon26 said:
Lol fourth time...
SGSII your using the correct firmware then right? The link i gave shouldn't apply to you it could brick your phone...
Yh, Odin can be annoying sometimes, you can either wait a while and try again later, restart and try again, or use heimdall. Or you could flash a zip through recovery (not sure if that last one works if you cant get past boot)
Click to expand...
Click to collapse
Umm no I used the right SGSII firmware. You didn't even gave me a link.
I'm sure I used the right firmware.
the first time I tried (when I posted), it got stuck before it even really started. second time and third time at 90-100%. the last time it worked.
I have no clue why it wasn't working, but this was the only solution for me (no, I couldn't boot, so I couldn't put anything on my SD and use CWM).
odin hangs often for the simplest of reasons, especially a loose usb connection -- test this by plugging into you pc or laptop and see if it stays linked or unlinks after a short duration or if the cable is jiggled -- you then know to hold the cable when using odin, or better still, get a replacement usb cable
Hi I just decided to change my custom firmware to darkynote from rocketrom. It worked perfectly but I wanted to update my kernal also so afterwards i rebooted into recovery and installed version 2.6 of Abyss Note. Now My phone boots to the "Samsung Galaxy Note N7000" Screen and stays there unless i plug it in, then when i start it it goes to a frozen battery screen. I cant boot into recovery but i can boot into download mode. Can someone help me get my phone back to stock? I can't seem to find a tutorial anywhere that will work for me.
please help
edit: extra details, the Odin3 v1.85 process gets stopped at NAND Write Start!!
Here is the message feed:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXKL7_N7000OXAKL7_N7000XXKL7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> factoryfs.img
<ID:0/006> NAND Write Start!!
Also tried using CF-Root kernal. no luck there. The Bar in Odin says KERNEL and the green bar is full, also stuck at NAND Write Start!!.
Someone respond, im gonna cry.
First Relax man, dont be in hurry, read this guide twice/thrice n calmly proceed...
It is nice still you can entre to download mode.
First get Stock firmware from here Type N700 in search field, it will show all available firmware, select you wish to flash n download
Note : If you select latest ROM KL7, you won't get Root + CWM, for that you have to Flash another ROM first, then You have to Root + CWM,then Install Mobile odin pro, now flash KL7 with Mobile Odin pro with 'ever root' option enable. If you selecting another ROM, ignore this note
Get odin n extract
Install:
Install Kies on your computer, connect your phone and make sure that all the drivers installed correctly.
Extract tar file from the ROM you have download(password available at site from you have download). Put the phone into download mode (vol. down+home+power buttons),
Comlete close kies, if open. start odin, connect the phone via USB. Choose continue on the phone,
make sure that only two boxes are checked in odin - Auto Reboot and F.Reset Time.
Choose PDA button in Odin and select tar file you extracted before.
Choose START button.
The phone will reboot after the flash. Done.
Alright sounds good but i left it at the NAND write start thing overnight and when i came back it said this:
<ID:0/006> NAND Write Start!!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
Now I have a black screen and its flashing on and off with the frozen battery symbol. I think the battery is drained or something.
Also my download of the rom finished, there isnt any tar files its just a zip with an MD5 file and a Dll. Should i just but the MD5 file in the PDA section?
Edit: now my phone wont do anything when i try to put it in download mode.
Anyway if you are still able to entre Download mode, then try to flash stock kernel as i said above.
But thats what I mean, is it possible for the phone to not boot into download because the battery is dead or is my phone just bricked forever $850 dollars out the window.
tangelos said:
I cant boot into recovery but i can boot into download mode.
Click to expand...
Click to collapse
Actually i dont understand properly, your first post said U R getting into DW mode, if you can entre into boot mode, i guide you earlier, i cant say it bricked.
many time this happen after some error in procedure.
If you even not able to entre into Download mode, you need to entre it with JIG.
dr.ketan said:
Actually i dont understand properly, your first post said U R getting into DW mode, if you can entre into boot mode, i guide you earlier, i cant say it bricked.
many time this happen after some error in procedure.
If you even not able to entre into Download mode, you need to entre it with JIG.
Click to expand...
Click to collapse
Actually I was just updating you. At first it was working, then i tried a tutorial simmilar then the one you just gave me and it caused the phone to not turn on whatsoever. Can you link me to one of these "jigs". Thanks
You can get it readymade from market e.g. ebay or you can make it own home made
see here http://forum.xda-developers.com/showthread.php?t=819551
better first try with other battery once, if you cud manage
I was able to get a hold of one locally. When I plug it in, nothing happens. Any advice? Its for a GSII. Is that why? Or is it the battery thing. Before it stopped working completely, when i booted into download it would say low battery. Looks like its game over for my new phone .
I tried this with an old usb cable http://forum.xda-developers.com/showthread.php?p=20914895#post20914895.
Inserted the USB Jig afterwards. No luck
I suppose i have to take it to be J-tagged: http://toronto.kijiji.ca/c-buy-and-...-JTag-Service-Phone-Unlock-W0QQAdIdZ341742939
I'm sorry if this is not helping, or being so late, but I wanted to share my experience.
So, now can you enter the recovery menu by pressing the 3 buttons?
if you can then do a factory reset/wipe from the recovery and then flash an entire flashable ROM, maybe a stockROM or ROCKETROM.
you can upload ROCKETrom from the ordinary windows explorer , just copy and paste to the ex.SD.
the looping android animation actually happened to mine, and that's how I fixed it.
BTW: I didn't use Odin at all, or any other program.
Thanks for trying to help but this is completely irellavent. My phony CAN'T get into recovery and it NO LONGER CAN even get into Odin (download mode). I guess I wasn't clear when posting. Is anyone aware of a hardbrick fix or if sammy will repair ,my phone for a price.
Hi buddy. The EXACT same happened to be when trying to flash RocketV16. Frozen charge screen and everything.
To sort it I first let the phone start and hang on the black/white writing splash screen, removed the battery while it was on, held down the power button without the battery in for 3-5 seconds, put the battery back in. I then held Vol Down, the Home button and then the power down button (hold down power last) for some seconds until the Odin-Mode downloader came up.
After that I just followed a guide on flashing with Odin.
No more £9999999999 brick
unfortunatly i cant try that stratagy because i cant even get to the splash screen anymore. + i gave it to a local guy who claims to be able to jtag it. If it doesnt work ill send it to samsung and of course pay because i voided my warrenty. oh well. better then my old i9000m.
Galaxy Note N7000 Screen
I hate to hijack your thread but what I have to ask directly relates to your issue.
I have been searching for any file that contains this actual GALAXY Note Boot Screen - I am looking for this image file with the hope of making this my sole wallpaper/background. If there is anyway you or those who are reading this can PLEASE attach the file or at the very least provide a link so I 'd be able to download it for myself. I'd sincerely appreciate any help I can get.
I'm willing to pay ANY PERSON WHO PROVIDES A HIGH QUALITY IMAGE HOPEFULLY ALREADY SIZED FOR IMMEDIATE USE.
I'm sorry - please don't take this message as that of "shouting", My hope was to capture readers attention. Again, I apologize in advance for anyone having taken this message as shouting. That was not my intent.
Jim
connection
hey,i don't get how u manage to transfer stock firmware into the phone when pc cannot detect any file from the note???is it using odin??if yes,may someone share how to connect the phone to the pc via odin??
---------- Post added at 07:37 PM ---------- Previous post was at 07:27 PM ----------
hey how you manage to upload rocket rom,my pc cannot detect any file from my phone..even simple window explorer does not turn up..i hope u may help me...
me too Stuck at Galaxy Note Boot Logo
dr.ketan said:
First Relax man, dont be in hurry, read this guide twice/thrice n calmly proceed...
It is nice still you can entre to download mode.
First get Stock firmware from here Type N700 in search field, it will show all available firmware, select you wish to flash n download
Note : If you select latest ROM KL7, you won't get Root + CWM, for that you have to Flash another ROM first, then You have to Root + CWM,then Install Mobile odin pro, now flash KL7 with Mobile Odin pro with 'ever root' option enable. If you selecting another ROM, ignore this note
Get odin n extract
Install:
Install Kies on your computer, connect your phone and make sure that all the drivers installed correctly.
Extract tar file from the ROM you have download(password available at site from you have download). Put the phone into download mode (vol. down+home+power buttons),
Comlete close kies, if open. start odin, connect the phone via USB. Choose continue on the phone,
make sure that only two boxes are checked in odin - Auto Reboot and F.Reset Time.
Choose PDA button in Odin and select tar file you extracted before.
Choose START button.
The phone will reboot after the flash. Done.
Click to expand...
Click to collapse
Dr Ketan,I have mentioned the same in your other thread about stucking at Galaxy Note Boot Logo forver.
I was on CheckRom v6 and then i went to flash a kernel and then got stuck at Galaxy Note Boot Logo.
I am not able to got to recovery mode by pressing power+home and vol+,but I can go to Download mode by pressing power+home and vol-.so i went to desktop Odin and tried flashing one of the rom(Dr Ketan Guide to Rooting).Seems like Odin was succesful but still stuck at Galaxy Note Boot Logo.
please need help here,I hope my Galaxy Note is not Bricked!
Try flashing a cf root kernel back
Sent from my GT-N7000 using XDA
Remkve battery for few min, thn put it back n try to enter recovery
If you able to enter recovery wipe cache n wipe data, thn reflash rom with pc odin.
Sent from my GT-N7000 using xda premium
Hello gentlement. I have an Galaxy S I9000, and i have used a custom rom for about 2-3 months, unfortunately i can't remember which one, and as i cant boot my phone, im not sure how i can find out. I flashed it using Odin and Clockwork mod, both of which worked great. The problem now started out with me not being able to start my phone while charging, didn't pay much attention to it and just waited until it was charged, or unplugged it, started it, then charged it while it was on.
Now im having a different problem. I cant start my phone, the startscreen just says "Samsung galaxy S" etc, and it tries to reboot again and again.
I can start the phone into "download mode", but recovery mode doesnt seem to work.
Since the rom has been working flawlessly in the past, im not sure its the roms "fault"; might just be my phone singing on it's last verse.
Does anybody know what can cause this, or have a fix i can do in download mode?
I think i have read all the necesarry stickies, if i've missed something i apologize.
Thanks for all responses, regards - superegge
When this happens on ICS I reflash a kernel through odin in download mode and then reflash the ROM.
If your ROM is non wipe you could try this, otherwise I'd just try flashing a kernel and see if it boots.
superegge said:
Does anybody know what can cause this, or have a fix i can do in download mode?
Click to expand...
Click to collapse
First power down, remove battery, remove sim card and EXT SD card, preess power button for a min, reinsert battery and power it....
If still the same, flash a pit file as per guide given in Quick Fixes link below
xsenman said:
First power down, remove battery, remove sim card and EXT SD card, preess power button for a min, reinsert battery and power it....
If still the same, flash a pit file as per guide given in Quick Fixes link below
Click to expand...
Click to collapse
Thank you both for responses. I've tried following your guide many times now, installed odin etc. But everytime i try to flash my phone, this happens:
<ID:0/007> Added!!
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> Removed!
Sometimes it gets to some zImage thing, but my device is still "removed" shortly after. Is it maybe a faulty cable?
Will check back in tomorrow, need to sleep now. Again, thanks for your help
superegge said:
Sometimes it gets to some zImage thing, but my device is still "removed" shortly after. Is it maybe a faulty cable?
Will check back in tomorrow, need to sleep now. Again, thanks for your help
Click to expand...
Click to collapse
yep, it could be due to cable or mostly the PC, try on lap top or another PC, added concerning this to Quick fixes, take a rest first,
ive had the same problem with Odin. But that had to do with rooting, and the oneclick superuser program.
Hopefully it will work when you try on a new pc. Good luck superegge!