Related
I installed Clock Work Mod on my Samsung Galaxy Mini and after that, I selected "Reboot from recovery mode" and then after that the device turned off. It would not turn on anymore! Can't enter download mode and recovery mode, screen is off, no backlights. Odin would not detect it too. Please help.
I don't know if this is the right section. Thanks.
Up. Help me.
neilgoco said:
I installed Clock Work Mod on my Samsung Galaxy Mini and after that, I selected "Reboot from recovery mode" and then after that the device turned off. It would not turn on anymore! Can't enter download mode and recovery mode, screen is off, no backlights. Odin would not detect it too. Please help.
I don't know if this is the right section. Thanks.
Click to expand...
Click to collapse
Sometime the phone discharges have u tried starting op in 'download mode' while charging and reinstalling Froyo again using Odin?
Yesterday I have received my sgm mobile and i had exactly the same problem with the same aplication. The mobile seems to be dead it is not detected by the pc and can't be charged. Can anybody help us ?
i have same problem with my mini today, i upgraded to 2.34 because of wi-fi, it won't connect and everything was allright.
then i downgraded to 2.2 wih 2.33 ops and odin 4.38, but then my phone it doesn't even turn on. i mean no recovery mode, no downloading mode, nothing. it don't turn on at all and odin don't detect. what to do?
hey use the jig method type unbricking galaxy s jig in youtube
and do the same u will get download mode in it and never use ROM MANAGER
however its a great software but it dont supports some samsung phones.
especially low end phones
debsattam said:
hey use the jig method type unbricking galaxy s jig in youtube
and do the same u will get download mode in it and never use ROM MANAGER
however its a great software but it dont supports some samsung phones.
especially low end phones
Click to expand...
Click to collapse
Can you post a link to that specific video? Thanks.
debsattam said:
hey use the jig method type unbricking galaxy s jig in youtube
and do the same u will get download mode in it and never use ROM MANAGER
however its a great software but it dont supports some samsung phones.
especially low end phones
Click to expand...
Click to collapse
By the way, is the USB Jig for SGS the same size with the USB slot of the Galaxy Mini? Does the USB Jig works on Galaxy Mini? Is this tried and tested on this pgone? Sorry for too many questions. Thanks.
---
I am here: http://maps.google.com/maps?ll=14.728119,121.029307
Go a google search with "unbricking galaxy s jig"
It can be use for xperia mini too.
Gudluck!
It might be,battery suddenly empty. Its hard for phone to brick.Charge ur phone 1st at full... And choose the right baseband according rom prequistid. I b4 this rooted and installing CWM on this galaxy mini and the phone at samsung logo or samsung galaxy mini logo.
As on my condition,follow guide that been explained. If u have flashed the CWM, REBOOT. Then at samsung logo,press volume down,then u can access CWM. To avoid other probs, flash it with cyanogen mod. Or it maybe cant be loaded.
As far i concerned, for galaxy mini got 2 type of recovery. That is,
Enchanced recovery
&
Tass Recovery
For me,choose tass recovery.
Sent from my HTC Vision with Doubleshot Rom
(I think this set of steps works in these conditions: Hard-brick, absolutely non-responsive to any button combination. Odin still recognizes the phone when connected through USB port)
1.- Remove both the SIM card and de microSD card.
2.- KEEP YOUR BATTERY REMOVED
3.- Apply the Download-mode button combination (known by you all)
4.- WHILE HOLDING THE COMBINATION, insert the battery, and keep the buttons pressed untill you get the download mode.
5.- Flash your phone with a valid firmware through Odin (Preferebly, have Odin prepared before doing this trick)
I finally flashed it widh Gingerbread 2.3.4 but i don't really like it, because it ended up a little buggy, which i am still trying to get rid of.
Anyway, i hope this helps.
Have a nice day
Fomelogo
---------- Post added at 03:29 PM ---------- Previous post was at 03:25 PM ----------
Uploaded with ImageShack.us
This tutorial is very complicated and I have tried to explain it as best as I can, hope it help some of you guys.
PS. If you have any USB driver problems or windows deleted problems with device managers or drivers in general causing errors you must fix these problems first or use a different computer, if the drivers wont install properly you cannot do it on that computer.
EDIT: Gingerbread 2.3.4 firmware, I can confirm this works
Did I get some of the previous posts about using usb jigs for SGS on samsung galaxy GT S 5570 right??
What software is required?
Some USB jigs for SGS 900XX (as in 9000i 9003i etc) are available on line for between INR 250 to 600 (1 U$D is approx 49 INR).
arsalanahmed said:
(I think this set of steps works in these conditions: Hard-brick, absolutely non-responsive to any button combination. Odin still recognizes the phone when connected through USB port)
1.- Remove both the SIM card and de microSD card.
2.- KEEP YOUR BATTERY REMOVED
3.- Apply the Download-mode button combination (known by you all)
4.- WHILE HOLDING THE COMBINATION, insert the battery, and keep the buttons pressed untill you get the download mode.
5.- Flash your phone with a valid firmware through Odin (Preferebly, have Odin prepared before doing this trick)
I finally flashed it widh Gingerbread 2.3.4 but i don't really like it, because it ended up a little buggy, which i am still trying to get rid of.
Anyway, i hope this helps.
Have a nice day
Fomelogo
---------- Post added at 03:29 PM ---------- Previous post was at 03:25 PM ----------
Uploaded with ImageShack.us
This tutorial is very complicated and I have tried to explain it as best as I can, hope it help some of you guys.
PS. If you have any USB driver problems or windows deleted problems with device managers or drivers in general causing errors you must fix these problems first or use a different computer, if the drivers wont install properly you cannot do it on that computer.
EDIT: Gingerbread 2.3.4 firmware, I can confirm this works
Click to expand...
Click to collapse
Step 1-4 done,
but my Odin doesn't detect it..
Should I go to jig mode?
The best thing is to give it to the service center
I agree, I should have made it
armanke13 said:
Step 1-4 done,
but my Odin doesn't detect it..
Should I go to jig mode?
Click to expand...
Click to collapse
My odin detects the phone, report a new succesful update...
...but the phone is still not booting up - the logo do not appear !!
(battery is hot, something is going on...)
stepph said:
My odin detects the phone, report a new succesful update...
...but the phone is still not booting up - the logo do not appear !!
(battery is hot, something is going on...)
Click to expand...
Click to collapse
cud be the firmware u used or somethin?
roofrider said:
cud be the firmware u used or somethin?
Click to expand...
Click to collapse
tried two official for my region from 'checks fus downloader'...
stepph said:
tried two official for my region from 'checks fus downloader'...
Click to expand...
Click to collapse
not sure abt fusdownloader...but almost every1 here use firmwares frm samfirmware.com
and no1 had any prob.
roofrider said:
not sure abt fusdownloader...but almost every1 here use firmwares frm samfirmware.com
and no1 had any prob.
Click to expand...
Click to collapse
i'm behind a firwall and cannot acces... i'll try tonite from home...
and let you know...
Not working....
arsalanahmed said:
(I think this set of steps works in these conditions: Hard-brick, absolutely non-responsive to any button combination. Odin still recognizes the phone when connected through USB port)
1.- Remove both the SIM card and de microSD card.
2.- KEEP YOUR BATTERY REMOVED
3.- Apply the Download-mode button combination (known by you all)
4.- WHILE HOLDING THE COMBINATION, insert the battery, and keep the buttons pressed untill you get the download mode.
5.- Flash your phone with a valid firmware through Odin (Preferebly, have Odin prepared before doing this trick)
I finally flashed it widh Gingerbread 2.3.4 but i don't really like it, because it ended up a little buggy, which i am still trying to get rid of.
Anyway, i hope this helps.
Have a nice day
Fomelogo
---------- Post added at 03:29 PM ---------- Previous post was at 03:25 PM ----------
Uploaded with ImageShack.us
This tutorial is very complicated and I have tried to explain it as best as I can, hope it help some of you guys.
PS. If you have any USB driver problems or windows deleted problems with device managers or drivers in general causing errors you must fix these problems first or use a different computer, if the drivers wont install properly you cannot do it on that computer.
EDIT: Gingerbread 2.3.4 firmware, I can confirm this works
Click to expand...
Click to collapse
Dear Arsalan,
I face same problem with my galaxy mini and try to use your procedure for ON my galaxy mini but I not successful please help me.
Hi
Firstly, I'm sorry about my incorrect english.
I have a big problem with my rooted Galaxy Note Stock ICS 4.0.4.
After a phone restore (done in the Options menu) I encountered a boot problem.
When I turn the phone on, I see the white Galaxy Note GT-7000 writing and then
the Samsung Galaxy boot logo which continues flashing all the time but the
OS isn't booting. There isn't a boot loop which restarts the phone, only the blinking
Samsung animation.
I do really not know much about Android, rooting, flashing etc so I don't know what
is the problem and what I can do to fix it.
Recently I did a data/factory reset and cache partition wipe in the recovery mode,
hoping that this could help, but that didn't change anything.
After that I flashed another stock rom (ICS 4.0.4 Switzerland (Swisscom)) with
Odin in download mode, but there's still the endless boot problem.
I read about brick and that its not recommended to wipe anyting.
What could be my problem and how could I resolve it?
I'm sorry if theres just another thread which speaks about the same problem, but I
didn't find anyone with the identical situation as mine.
I'm very grateful for any answers.
hmm.. it could be because of data partition corruption..
download this http://www.mediafire.com/download.php?ukk00n20dahxxkp
place it on external SD.. boot into recovery and choose apply update from ext storage
once done. boot into recovery again.. now ... in the new CWM. do
factory reset., wipe cache partition
advanced menu> wipe dalvik cache
reboot
Hi,
thank you for your answer. But perhaps as I turned the phone on the first time
since yesterday (i didn't do anything since), I'm not anymore able to go into recovery mode
and the boot process ends just at the white Galaxy Note writing (without bootloop, there's
only the static text)
Only the download mode works fine, but obviously I cant install your file from there...
If you can get into download mode, better flash a stock ics rom first. After the flash is successful you can try to do the procedure as in my previous post.
I tried to flash different roms (also stock ones) but the download of the "factoryfs.img" doesn't finish.
The only thing I could do is to interrupt the downloading and restart from the beginning.
I read that this problem happens sometimes and that it could be resolved rebooting the phone and
the pc, but I didn't got it working
Do you know why it doesn't work? The first time I flashed successfully, but that was the first and the last time.
I don't even get an error or a fail notification...
LSinus said:
I tried to flash different roms (also stock ones) but the download of the "factoryfs.img" doesn't finish.
The only thing I could do is to interrupt the downloading and restart from the beginning.
I read that this problem happens sometimes and that it could be resolved rebooting the phone and
the pc, but I didn't got it working
Do you know why it doesn't work? The first time I flashed successfully, but that was the first and the last time.
I don't even get an error or a fail notification...
Click to expand...
Click to collapse
If Odin stops at "factoryfs.img" you bricked your device.
(I wrote this and the following lines a few times now in the last days, but the different OP are consequently ignoring the message and try other intelligent approaches, in the end they will not succeed, because their Note is still bricked).
Solution: Samsung replaces your motherboard (that is the only real repair).
Workaround: eMMC scanner and repartition trick in hg42's threads.
Nothing else will help if your device is bricked.
ThaiDai said:
If Odin stops at "factoryfs.img" you bricked your device.
(I wrote this and the following lines a few times now in the last days, but the different OP are consequently ignoring the message and try other intelligent approaches, in the end they will not succeed, because their Note is still bricked).
Solution: Samsung replaces your motherboard (that is the only real repair).
Workaround: eMMC scanner and repartition trick in hg42's threads.
Nothing else will help if your device is bricked.
Click to expand...
Click to collapse
i know what you are getting to but till one is completely satisfied that the phone is bricked, they wouldnt go about repartitioned the memory and loose 3 GB... at least i wouldnt and i am sure no one will till all possible scenarios are exhausted, So try to be a little positive..
---------- Post added at 05:22 PM ---------- Previous post was at 05:18 PM ----------
Recently I did a data/factory reset and cache partition wipe in the recovery mode,
hoping that this could help, but that didn't change anything.
After that I flashed another stock rom (ICS 4.0.4 Switzerland (Swisscom)) with
Odin in download mode, but there's still the endless boot problem.
Click to expand...
Click to collapse
You did a factory reset on stock recovery ... and then you installed a stock rom .. was Odin able to flash till the end and it said PASS?
nokiamodeln91 said:
You did a factory reset on stock recovery ... and then you installed a stock rom .. was Odin able to flash till the end and it said PASS?
Click to expand...
Click to collapse
The first time I was able to flash the stock rom successfully (said PASS), but this was the first and last time it worked...
nokiamodeln91 said:
i know what you are getting to but till one is completely satisfied that the phone is bricked, they wouldnt go about repartitioned the memory and loose 3 GB... at least i wouldnt and i am sure no one will till all possible scenarios are exhausted, So try to be a little positive..
Click to expand...
Click to collapse
You said something about loosing 3 GB repartitioning the memory. Its possible to revive the phone by this way?
Does anyone know approximately how much it will cost me to replace the motherboard of the Note?
download this PIT file http://d-h.st/FVh
now put the phone in download mode again, open odin and select the PIT file in the PIT tab. also make sure repartition is checked.
select the rom in PDA (if more that one file for rom, choose appropriate options)
connect the phone .. when the port is shows in odin flash again,,, check if this also stops at the same factoryfs
---------- Post added at 09:24 PM ---------- Previous post was at 09:21 PM ----------
LSinus said:
You said something about loosing 3 GB repartitioning the memory. Its possible to revive the phone by this way?
Does anyone know approximately how much it will cost me to replace the motherboard of the Note?
Click to expand...
Click to collapse
if you have warranty thats the first one to do. if not then there is a way by repartitioning the memory to skip the bad blocks, not a guaranteed method but works most of the time. cost of motherboard is high about 350-400$
One final try. If you are able to go recovery mode,pressing volume up, home, power buttons, flash abyss kernel 4.2, do all wipes and formats and flash a custom rom such as kingdroid.
Sent from my GT-N7000 using xda premium
---------- Post added at 10:03 PM ---------- Previous post was at 10:00 PM ----------
If you don't have custom rom in your external sd card, try to copy via another note.
Sent from my GT-N7000 using xda premium
nokiamodeln91 said:
download this PIT file http://d-h.st/FVh
now put the phone in download mode again, open odin and select the PIT file in the PIT tab. also make sure repartition is checked.
select the rom in PDA (if more that one file for rom, choose appropriate options)
connect the phone .. when the port is shows in odin flash again,,, check if this also stops at the same factoryfs
---------- Post added at 09:24 PM ---------- Previous post was at 09:21 PM ----------
if you have warranty thats the first one to do. if not then there is a way by repartitioning the memory to skip the bad blocks, not a guaranteed method but works most of the time. cost of motherboard is high about 350-400$
Click to expand...
Click to collapse
Thank you for your attempt helping me. Perhaps the flashing still fails (factoryfs.img could not be downloaded entirely).
Damn, 350-400$ only for the motherboard is a lot, considering that I bought this almost new phone for around 340$...
Isn't there any other way to get rid of the "brick"? I would accept any loss of memory just to get the phone working...
By the way is it a soft- or a hardbrick?
http://forum.xda-developers.com/showthread.php?t=1667886
http://forum.xda-developers.com/showpost.php?p=26285877&postcount=12
I bought a second hand GT-I9000 running stock OS. I want to root it, put on a new ROM and then unlock to other phone providers as its locked on Vodafone.
I have rooted a bunch of devices previously without problems but hit a big problem with this phone.
First I downloaded and installed the samsung drivers. I then plugged in the phone and it recognised it.
I am using the latest version of Odin 3.07 and downloaded the .tar file for my baseband version - XXJPY:
cf-root-xx_xeu_jpy-v1.3-busybox-1.17.1.tar
I got the phone into download mode, showing the green (yellow) triangle, added the .tar file in PDA mode with F. Reset Time and Auto Reboot on.
The bar on Odin was blue and the box said "added" so I hit start. The large first box at the top of the Odin screen (left hand side) came up with KERNEL and the whole process started but seemed to be taking ages then the phone screen scrambled.
The phone was soft bricked and I have got it back to download mode.
The problem I have now is Odin wont recognise the phone in download mode. I am installing new samsung drivers in the hope this will solve this problem.
I have got the .pit file for my phone from another thread and if I understand correctly I use this file in Odin to get the phone back to life??
If I can get it working again can anyone tell me why the root failed?
mark1holland1 said:
I bought a second hand GT-I9000 running stock OS. I want to root it, put on a new ROM and then unlock to other phone providers as its locked on Vodafone.
I have rooted a bunch of devices previously without problems but hit a big problem with this phone.
First I downloaded and installed the samsung drivers. I then plugged in the phone and it recognised it.
I am using the latest version of Odin 3.07 and downloaded the .tar file for my baseband version - XXJPY:
cf-root-xx_xeu_jpy-v1.3-busybox-1.17.1.tar
I got the phone into download mode, showing the green (yellow) triangle, added the .tar file in PDA mode with F. Reset Time and Auto Reboot on.
The bar on Odin was blue and the box said "added" so I hit start. The large first box at the top of the Odin screen (left hand side) came up with KERNEL and the whole process started but seemed to be taking ages then the phone screen scrambled.
The phone was soft bricked and I have got it back to download mode.
The problem I have now is Odin wont recognise the phone in download mode. I am installing new samsung drivers in the hope this will solve this problem.
I have got the .pit file for my phone from another thread and if I understand correctly I use this file in Odin to get the phone back to life??
If I can get it working again can anyone tell me why the root failed?
Click to expand...
Click to collapse
Hi...Hm never had this problem, maybe something went wrong with USB connection, hope you get it working...
I was using this method for rooting and there was no problems.
http://theunlockr.com/2012/10/22/how-to-root-the-samsung-galaxy-s-i9000-cf-kernel-method/
Best regards!
I cant get the phone to be recognised by my PC - damn thing comes up as unrecognised USB device!
Installingmkies, anyone ever seen this problem?
I have the phone recognised by my PC and have run the .pit file which Odin said was a success, however, the phone wont start except in download mode
how can I install anything?
do I need to install factory firmware first??
A new version of Odin is NOT DESIGNED for GT-I9000. Use Odin 1.83 and older
DumF0rGaming said:
A new version of Odin is NOT DESIGNED for GT-I9000. Use Odin 1.83 and older
Click to expand...
Click to collapse
Thanks for that.
The problem I have is that I cannot get any firmware to install - it starts fine then fails and the screen scrambles.
I have used the pit file to repartition first but it still fails
I guess you have to try install JVU via Heimdall v1.1+zadig, then root it and go directly to the newest CM
mark1holland1 said:
.....I am using the latest version of Odin 3.07.....
Click to expand...
Click to collapse
It is wrong Odin version.
Our forum mate @DumF0rGaming already wrote you correct answer, if Odin use 1.82 or 1.83, or use Heimdall as he wrote you. Odin v3.x or 4.x will usually recognize device, but instantly freeze by try to flash.
DumF0rGaming said:
I guess you have to try install JVU via Heimdall v1.1+zadig, then root it and go directly to the newest CM
Click to expand...
Click to collapse
Hi, many thanks for the information, due you have any links or information. I have not used Heimdall yet.
tetakpatak said:
It is wrong Odin version.
Our forum mate @DumF0rGaming already wrote you correct answer, if Odin use 1.82 or 1.83, or use Heimdall as he wrote you. Odin v3.x or 4.x will usually recognize device, but instantly freeze by try to flash.
Click to expand...
Click to collapse
I have got the device recognised and partitioned with the pit file using 1.83 Odin but cannot find a stock file which works
It starts and just hangs with a tiny sliver of the green bar on the phone.
Its driving me INSANE!
mark1holland1 said:
I have got the device recognised and partitioned with the pit file using 1.83 Odin but cannot find a stock file which works. It starts and just hangs with a tiny sliver of the green bar on the phone.
Click to expand...
Click to collapse
Patience, mate... cool head helps better. Use this step-by-step guide of mine where all download links still work. The workflow there is about installing Froyo stock ROM (big choice for all regions) and after that you can flash SpeedMod kernel which features CWM recovery. That ROM seems to be good ground to upgrade further to CM10x, I had no bugs at all (some people upgrading from other ROMs seem to be more prone to bugs).
Here is the guide: http://forum.xda-developers.com/showthread.php?p=44710247#post44710247
And you are sure that you have i9000?
tetakpatak said:
Patience, mate... cool head helps better. Use this step-by-step guide of mine where all download links still work. The workflow there is about installing Froyo stock ROM (big choice for all regions) and after that you can flash SpeedMod kernel which features CWM recovery. That ROM seems to be good ground to upgrade further to CM10x, I had no bugs at all (some people upgrading from other ROMs seem to be more prone to bugs).
Here is the guide: http://forum.xda-developers.com/showthread.php?p=44710247#post44710247
And you are sure that you have i9000?
Click to expand...
Click to collapse
Thanks for all this information, this is exactly what I have been looking around for the past few hours. This is an absolutely excellent write up you provided.
I still think I may have a problem as the blue bar appeared to show progress but then has stopped. The process seems to be stuck on PARAM in Odin showing this <ID:0/003> param.lfs
mark1holland1 said:
I still think I may have a problem as the blue bar appeared to show progress but then has stopped. The process seems to be stuck on PARAM in Odin showing this <ID:0/003> param.lfs
Click to expand...
Click to collapse
Well, Odin indeed needs several minutes to complete the flashing. But if really nothing changes for longer than 7-8 minutes, pull out the USB cable and then battery and repeat the procedure. Try also an older Odin version, I think 1.72 or even 1.0 work well with the i9000. Check in search field, there is an topic with all Odin versions and their compatibility.
I hope it will work next try, good luck! Post the results please.
EDIT: if Odin fails to complete the flashing, Heimdall is probably good idea. Our forum mate has sent you download link of the older version thaht works well with the i9000. Heimdall is actually more reliable flasher, but it has bit different workflow. Here is website where you can read more about it:
http://www.glassechidna.com.au/products/heimdall/
---------- Post added at 08:19 PM ---------- Previous post was at 08:00 PM ----------
mark1holland1 said:
Odin showing this <ID:0/003> param.lfs
Click to expand...
Click to collapse
"param.lfs" is actually extremely important file where the flashing shouldn't been interrupted. But its flashing should take normally only several seconds, so if the Odin stuck there and nothing changes for really long time, you can't make it worse than it already is by removing the cable....
tetakpatak said:
Well, Odin indeed needs several minutes to complete the flashing. But if really nothing changes for longer than 7-8 minutes, pull out the USB cable and then battery and repeat the procedure. Try also an older Odin version, I think 1.72 or even 1.0 work well with the i9000. Check in search field, there is an topic with all Odin versions and their compatibility.
I hope it will work next try, good luck! Post the results please.
EDIT: if Odin fails to complete the flashing, Heimdall is probably good idea. Our forum mate has sent you download link of the older version thaht works well with the i9000. Heimdall is actually more reliable flasher, but it has bit different workflow. Here is website where you can read more about it:
http://www.glassechidna.com.au/products/heimdall/
---------- Post added at 08:19 PM ---------- Previous post was at 08:00 PM ----------
"param.lfs" is actually extremely important file where the flashing shouldn't been interrupted. But its flashing should take normally only several seconds, so if the Odin stuck there and nothing changes for really long time, you can't make it worse than it already is by removing the cable....
Click to expand...
Click to collapse
It just seems to stick at the start, the bar begins and then just hangs.
Many thanks for your time on this, I am downloading Heimdall as we speak......
mark1holland1 said:
I have got the device recognised and partitioned with the pit file using 1.83 Odin... It starts and just hangs with a tiny sliver of the green bar on the phone. Its driving me INSANE!
Click to expand...
Click to collapse
Before next try, make soft reset of your phone: pull out the battery and keep power button pressed for ca 30sec.
Meanwhile, close Odin and run it again, prepare again all the files and put your phone into download mode just short before you start with flashing.
---------- Post added at 08:25 PM ---------- Previous post was at 08:24 PM ----------
mark1holland1 said:
It just seems to stick at the start, the bar begins and then just hangs.
Many thanks for your time on this, I am downloading Heimdall as we speak......
Click to expand...
Click to collapse
Try bit older Odin version. Already 1.82 should work well...
---------- Post added at 08:28 PM ---------- Previous post was at 08:25 PM ----------
mark1holland1 said:
...
Click to expand...
Click to collapse
Here you have Odin 1.7 and 1.82, I didn't check if download links are still active
tetakpatak said:
Before next try, make soft reset of your phone: pull out the battery and keep power button pressed for ca 30sec.
Meanwhile, close Odin and run it again, prepare again all the files and put your phone into download mode just short before you start with flashing.
---------- Post added at 08:25 PM ---------- Previous post was at 08:24 PM ----------
Try bit older Odin version. Already 1.82 should work well...
---------- Post added at 08:28 PM ---------- Previous post was at 08:25 PM ----------
Here you have Odin 1.7 and 1.82, I didn't check if download links are still active
Click to expand...
Click to collapse
I tried Odin 1.7 and it still sticks, this time earlier (after removing the battery and pressing power for 30 secs)
I honestly am at my wits end with this, trying Hiemdall...........
mark1holland1 said:
I tried Odin 1.7 and it still sticks, this time earlier (after removing the battery and pressing power for 30 secs)
I honestly am at my wits end with this, trying Hiemdall...........
Click to expand...
Click to collapse
Yes... as you prefer, mate. Read as first carefully how it works, as the workflow is different.
tetakpatak said:
Yes... as you prefer, mate. Read as first carefully how it works, as the workflow is different.
Click to expand...
Click to collapse
IT failed on the kernel, tried it twice
says fails to deliver data or up load it
If there is a kernel problem is the phone essentially bricked or does anyone know of a solution???
mark1holland1 said:
If there is a kernel problem is the phone essentially bricked or does anyone know of a solution???
Click to expand...
Click to collapse
Are you trying to flash Froyo stock ROM out of three files? I didn't try it with Heimdall. I know our forum mate @DumF0rGaming has mentioned recently some 2.3.6 ROM that should work particulary good with Heimdall. Check his post of last few days.
Good that your phone gives signs of life. Don't worry now, there are so many ways how it could work. We all have semi-bricked our phones on some point before and restored them again. You need patience. I would also try with several Odin versions, also try to connect the cable to different USB slot on your PC. Often it is some stupid reason that makes the flashing suddenly work.
Try also with Odin 1.0
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.
I have checked all the related Q and A's and none of them seem to fix my problem. My brother's Samsung Captivate I896 Rogers was rooted with running CM10.2 but it kept crashing no matter what Gapps I installed or factory reset so my brother decided that he wanted to go back to a Stock Rogers Rom. While trying to do this with the ODIN one click App the USB accidentally came out and now the phone is stuck in Download mode and even though Odin recognizes the phone. None of the bootloaders work and Odin is hanging every time on "Setup Connection". If anyone could tell me how to fix this it would be much appreciated. Thank You.
LanreLogic said:
I have checked all the related Q and A's and none of them seem to fix my problem. My brother's Samsung Captivate I896 Rogers was rooted with running CM10.2 but it kept crashing no matter what Gapps I installed or factory reset so my brother decided that he wanted to go back to a Stock Rogers Rom. While trying to do this with the ODIN one click App the USB accidentally came out and now the phone is stuck in Download mode and even though Odin recognizes the phone. None of the bootloaders work and Odin is hanging every time on "Setup Connection". If anyone could tell me how to fix this it would be much appreciated. Thank You.
Click to expand...
Click to collapse
Flash the non-bootloader Odin kk4 from this post: http://forum.xda-developers.com/showpost.php?p=18370912&postcount=3
It doesn't have to be the Rogers' one. As for Gapps, Usually the correct one to flash are in the thread's OP.
BWolf56 said:
Flash the non-bootloader Odin kk4 from this post: http://forum.xda-developers.com/showpost.php?p=18370912&postcount=3
It doesn't have to be the Rogers' one. As for Gapps, Usually the correct one to flash are in the thread's OP.
Click to expand...
Click to collapse
I also had this problem , what worked for me was remove the battery , couple minutes , insert back in ,open odin , have it ready to go at this point , button combo , or jig to download , as soon as odin sees device , start flash , a one click back to stock would be the better way to go , start with a clean slate and all
captivate i896 , cyanfox 2.0.2
---------- Post added at 10:35 PM ---------- Previous post was at 10:24 PM ----------
LanreLogic said:
I have checked all the related Q and A's and none of them seem to fix my problem. My brother's Samsung Captivate I896 Rogers was rooted with running CM10.2 but it kept crashing no matter what Gapps I installed or factory reset so my brother decided that he wanted to go back to a Stock Rogers Rom. While trying to do this with the ODIN one click App the USB accidentally came out and now the phone is stuck in Download mode and even though Odin recognizes the phone. None of the bootloaders work and Odin is hanging every time on "Setup Connection". If anyone could tell me how to fix this it would be much appreciated. Thank You.
Click to expand...
Click to collapse
woops , double post
LanreLogic
I also had this problem , what worked for me was remove the battery , wait couple minutes , insert back in ,"open odin" , have it all ready to go at this point , use button combo , or jig to download , or any way you can get there lol
as soon as odin sees device , start flash , a one click back to stock would be the better way to go , start with a clean slate and all
captivate i896 , cyanfox 2.0.2
( softbricked , many times )