Related
Hey guys,
First of all I checked every brick thread I could find and I am pretty sure none of the solutions applies to my problem.
I've flashed hundreds of times on numerous phones so I take most precautions to make sure I don't brick my phone, still, that's what happened now for the first time.
Situation:
- Download mode and recovery mode checked... both working
- Had Darky's DarkSteel 3.0 running with LagFix (no problems)
- Disabled LagFix by adding the folder
- Reboot ... disabled lagfix ... still running strong
- Flashed Darky's LegendarySteel 4.0 ... running
- Reboot ... hey no Voodoo ... oops lagfix folder was still there of course
- removed folder
- reboot ... still no lagfix ... OK so I accidentally chose the wrong Darky's ... The one with SpeedFix kernel not the one with Voodoo
- remember: lagfix folder still there, but I thought it would not be enabled as Darky's SpeedFix version had no Voodoo, also, Quadrant showed 900 like you would expect without lagfix
- Checked recovery/download just for precaution ... both working still
- Flashed the rom I wanted: Darky's LegendarySteel 4.0 with VOODOO
- So basically, I flashed WITHOUT "disable lagfix" folder, somehow thinking this would not be a problem considering LagFix wasn't running on the previous rom, and was disabled before flashing the previous rom.
- Clockwork Recovery clear cache / wipe partition ... choose zip ... run update ... OK REBOOT
- Stuck at Galaxy S logo
- No recovery
- Download mode works
- Tried Odin to flash stock rom using PIT 512 with and without repartition ... both just wait for a long time on some message "checking file system" and I don't know how long that should take but after 20mins I gave up.
- Tried rebooting and waiting forever as advised on the Voodoo site ("if you had a lagfix enabled previously, it will take forever, just be patient") well I waited forever (hours?) and still "Galaxy S" bootup screen
- Kies recognizes nothing
- Same for ADB
- Only download mode works ... Odin does recognize the device so all could not be lost right?
My questions:
- What should I flash (including firmware, PIT, odin version, repartition, wait time etc) to get up and running again?
Any help would be greatly appreciated!!!
nin2thevoid said:
Hey guys,
First of all I checked every brick thread I could find and I am pretty sure none of the solutions applies to my problem.
I've flashed hundreds of times on numerous phones so I take most precautions to make sure I don't brick my phone, still, that's what happened now for the first time.
Situation:
- Download mode and recovery mode checked... both working
- Had Darky's DarkSteel 3.0 running with LagFix (no problems)
- Disabled LagFix by adding the folder
- Reboot ... disabled lagfix ... still running strong
- Flashed Darky's LegendarySteel 4.0 ... running
- Reboot ... hey no Voodoo ... oops lagfix folder was still there of course
- removed folder
- reboot ... still no lagfix ... OK so I accidentally chose the wrong Darky's ... The one with SpeedFix kernel not the one with Voodoo
- remember: lagfix folder still there, but I thought it would not be enabled as Darky's SpeedFix version had no Voodoo, also, Quadrant showed 900 like you would expect without lagfix
- Checked recovery/download just for precaution ... both working still
- Flashed the rom I wanted: Darky's LegendarySteel 4.0 with VOODOO
- So basically, I flashed WITHOUT "disable lagfix" folder, somehow thinking this would not be a problem considering LagFix wasn't running on the previous rom, and was disabled before flashing the previous rom.
- Clockwork Recovery clear cache / wipe partition ... choose zip ... run update ... OK REBOOT
- Stuck at Galaxy S logo
- No recovery
- Download mode works
- Tried Odin to flash stock rom using PIT 512 with and without repartition ... both just wait for a long time on some message "checking file system" and I don't know how long that should take but after 20mins I gave up.
- Tried rebooting and waiting forever as advised on the Voodoo site ("if you had a lagfix enabled previously, it will take forever, just be patient") well I waited forever (hours?) and still "Galaxy S" bootup screen
- Kies recognizes nothing
- Same for ADB
- Only download mode works ... Odin does recognize the device so all could not be lost right?
My questions:
- What should I flash (including firmware, PIT, odin version, repartition, wait time etc) to get up and running again?
Any help would be greatly appreciated!!!
Click to expand...
Click to collapse
Flash some ecleir ROM with 512 re-partition. Hope this helps.
ragin said:
Flash some ecleir ROM with 512 re-partition. Hope this helps.
Click to expand...
Click to collapse
Try the Odin 1.7 from my thread posted here.
Try flashing back to the kernal that you had on the rom first?
Don't really know if it would help.. just taking a shot in the dark..
God I love this forum. Thanks for the tips all. I was using older ODIN and now using 1.7 (couldn't find it in the specified thread since the link was missing ^^ but used the forum search instead).
It's flashing ... At least that!! I will report back how it goes!
Edit:
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<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> zImage
<ID:0/003> dbdata.rfs
<ID:0/003> factoryfs.rfs
<ID:0/003> param.lfs
<ID:0/003> modem.bin
<ID:0/003> cache.rfs
<ID:0/003> Removed!!
<ID:0/003> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
Live and kicking again! Woot... Thanks all!
Well, atleast we know that odin 1.7 is more stable and more "unbrick" friendly =)
nin2thevoid said:
God I love this forum. Thanks for the tips all. I was using older ODIN and now using 1.7 (couldn't find it in the specified thread since the link was missing ^^ but used the forum search instead).
It's flashing ... At least that!! I will report back how it goes!
Edit:
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<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> zImage
<ID:0/003> dbdata.rfs
<ID:0/003> factoryfs.rfs
<ID:0/003> param.lfs
<ID:0/003> modem.bin
<ID:0/003> cache.rfs
<ID:0/003> Removed!!
<ID:0/003> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
Live and kicking again! Woot... Thanks all!
Click to expand...
Click to collapse
If it has helped you, please post a reply in my thread. can help others like you.
from my experience odin works the best if you connect your phone and hit the flash button immediately. connecting the phone in download mode and waiting with it always caused the flash process to "stuck" just like you describe.
anyway happy 1.7 helped you.
I had the exact same problem last night.
to solve the issue... I basically reflashed to ECLAIR JM8.
Then installed the ROM i wanted from clockwork recovery, and everything went back to normal!
Hope things work out well for you! cheers!!
I guess Re-Partition solved the problem. This should also work with Odin 1.0 / 1.3
No it was 1.7 that solved it since I did the exact same steps as with 1.3. Upgrading Odin was the fix for sure. I'm surprised not many people use 1.7... all the tutorials and guides point to 1.0 and 1.3.
Thanks for all the help guys!
hi gays,
actuly i have the same problem " screen of death "
but it happened whit my when i tried to flash -speedmod kernel - and - ce-root- in PDA
and it's stopped in middel of the action -- it happened in odin3 1.7 > it's naver happened in odin3 1.3 and odin3 1.3.2
i think there something wrong with 1.7
--sorry for bad English - i hope you understand what i'm tring to say
thanks for your time !!
I have a similar problem, which is not solved yet. I would be glad if someone would help.
Explanation of my probs:
I think I've bricked my SGS. It's a European version, not branded with T-mobile or any operator.
Friday I flashed the JPU (Android 2.2.1) and it worked fine. I've updated it several times via Odin, and never really had problems.
Then I installed the Voodoo recovery image and a custom ROM (Darkys 5.2 ROM). Still worked fine, a quadrant score of 1650. But then... I went to the recovery and chose to partition the internal SD card (EXT3/4). The phone said it succeeded doing this, but then it rebooted and I only got the Samsung logo (in white, no colors). Waited for 10 minutes, nothing happened.
Now I can't get it into recovery mode, however, the 3-button combo is still working, so I can get it into download mode as usual. But it does'nt work. It starts, I get the green slider on the phone, but after a very short time the update stops, it happends while Odin writes sbl.bin
I've tried several ROM's, but it does not work. I don't know what to do now - why can't I flash the phone even though it's in download mode?
Hope that someone can help me.
--- update ---
Hmm, maybe I'm on the right track now - I hope so.
Now I can turn on the phone, but it does go into the stock recovery, even though I just turn it on. It's the stock recovery (Android system recovery <2e> Samsung recovery Utils - for BML -
I downloaded Odin 1.7 from this link:
Download Odin-1.7with.pit.512.803.zip from General-Search.com
I did this on my work computer instead of my laptop. Never used Odin on this computer before. Then I just wanted to test Odin, so I chose some random PDA file I had on the computer. I chose the JPK Root + Busybox 1.17.1 + 2e\i9000_Kernel.tar that I used for rooting the JPK firmware when I was running that.
Then I have flashed the other file from that package (I9000XXJPK_Kernel.tar) - but when I turn on the phone, it stops but shows the white Galaxy S logo.
...more to come.
UPDATE!
UPDATE! Flashed JM7 firmware (that's the newest I already had downloaded on my work computer) and the beast is ALIVE AGAIN! Hallelujah!
I solved it with old ODIN flash 1.3 firmware JPA_JP4_U_JPP.tar (no pit file) USB pluged and unpluged a cuple of times. no repartition and no bootblock . After first flash i had to wipe and factery restore in 2e recovery. and flash again. After that the phone was fine. The KIES version i have installed is 1.5.3.10103.102. I think it is the driver version that KIES installs that is the problem, You could try installing older KIES vith older drivers. After first flash the new firmware could not install aps after first boot, thats why i wiped and flashed again.
Sory for bad English
Help pls.. I can run but it failed in the end after waiting it to run. I had tried reopening the oldin and replug in batt all no use...
Thank you so much for the tips here guys, been trying to recover my nephews softbricked i9000 for 5 days now - finally sorted, woohoo!!!!
I used Odin 1.7, Re-Partitioned with the 512 pit file and flashed a stock rom.
This was my last attempt too so Christmas has come early!
My wifes phone started to act up last night so I suggested that she reboot it. However, upon rebooting it just gets stuck at
the Boot Animation. Any ideas on how to resolve this? I guess I have to flash a new rom? I am also thinking of flashing it
back to stock rom is it possible in this state?
Thanks.
delphiguy said:
My wifes phone started to act up last night so I suggested that she reboot it. However, upon rebooting it just gets stuck at
the Boot Animation. Any ideas on how to resolve this? I guess I have to flash a new rom? I am also thinking of flashing it
back to stock rom is it possible in this state?
Thanks.
Click to expand...
Click to collapse
try to wipe everything in recovery and reboot, If Fails, try flash a kernel .tar in download mode with Odin, If fails, than you have no choice but to go into download mode and Flash the ROM you want
I already tried to reflash a stock rom (XXJVT) via odin, then it worked initially, then it hangs... and when I restarted its again stuck at the
boot animation. Any ideas?
delphiguy said:
I already tried to reflash a stock rom (XXJVT) via odin, then it worked initially, then it hangs... and when I restarted its again stuck at the
boot animation. Any ideas?
Click to expand...
Click to collapse
Do a clean Flash, Format SD cards, Factory Reset and Wipe everything in recovery before and after Flashing a ROM
Im sorry but I dont see Format SD Card in my recovery menu.
This is what I have in my recovery.
Android system recovery <3e>
Enter: Ok Key, SElect : Vol UP / Vol Down
reboot system now
apply update from sdcard
wipe data/factory reset
wide cache partition
--copying media files
E:failed to mount /sdcard (File exists)
E:copy_dbdata_media:Can't mount /sdcard
your storage not prepared yet. please use UI menu
for format and reboot actions.
Media files copy failed.
#MANUAL MODE#
--Applying Multi-CSC...
Installed Multi-CSC
Applied the CSC-code 'KOR'.
Successfully applied multi-csc
Any ideas?
delphiguy said:
Im sorry but I dont see Format SD Card in my recovery menu. Any ideas?
Click to expand...
Click to collapse
Format SD card and factory reset is done in menu> setting Storage and Privacy before flashing a ROM
try to flash the ROM again using Ezbase Recovery or GB Flash kit , link found in Collections for Android (my Signature)
xsenman said:
Format SD card and factory reset is done in menu> setting Storage and Privacy before flashing a ROM
try to flash the ROM again using Ezbase Recovery or GB Flash kit , link found in Collections for Android (my Signature)
Click to expand...
Click to collapse
Thanks Ill give it a try again... btw, do i flash this via odin as well?
your CSC says KOR, do you have a Samsung Galaxy S or Anycal Galaxy S?? Anycal is M110S and not I9000
yes all uses ODIN , but make sure what model your phone is
xsenman said:
your CSC says KOR, do you have a Samsung Galaxy S or Anycal Galaxy S?? Anycal is M110S and not I9000
yes all uses ODIN , but make sure what model your phone is
Click to expand...
Click to collapse
Yes I have Samsung Galaxy S I9000, btw when I tried to download EZBase I get a server not found error, but Im downloading GB Flash kit now.
I've downloaded GB Flash Kit and am trying to flash it via Odin but it seems that its stuck:
Here's the message from Odin
<ID:0/009> Added!!
<ID:0/009> Removed!!
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PDA_XWJW5_Sbl.tar.md5 is valid.
<OSM> PHONE_XDJV1.tar.md5 is valid.
<OSM> CSC_OXXJVC.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
delphiguy said:
I've downloaded GB Flash Kit and am trying to flash it via Odin but it seems that its stuck:
Here's the message from Odin
Click to expand...
Click to collapse
Remove Ext SD card and Sim card , and always restart Odin , to try again , when using the Pit file, Partition is TICKED
xsenman said:
Remove Ext SD card and Sim card , and always restart Odin , to try again , when using the Pit file, Partition is TICKED
Click to expand...
Click to collapse
I retried again, there is no Sim Card as I left it with the wife, and no Ext SD Card as well... went ok with
Odin, but then it rebooted immediately to recovery, and when I did Reboot System, its again stuck on
Boot Animation.
Ill be leaving the office soon, so i will continue this in my house, however, I dont have windows at the house...
any Odin alternatives LinuxMint?
Thanks.
delphiguy said:
I retried again, there is no Sim Card as I left it with the wife, and no Ext SD Card as well... went ok with
Odin, but then it rebooted immediately to recovery, and when I did Reboot System, its again stuck on
Boot Animation.
Ill be leaving the office soon, so i will continue this in my house, however, I dont have windows at the house...
any Odin alternatives LinuxMint?
Thanks.
Click to expand...
Click to collapse
use heimdall, download the Rescue kit for i9000, contains complete package for linux
updated the Collections. check out Quick Solutions,
Bro, you are not Cf-rooted. Tell us more about your phone so that you can get the correct clockworkmod recovery.
I had a similar problem. The solution I found that worked, based on a suggestion elsewhere, was to flash the new (stock) ROM twice in a row. Have no idea why this worked.
The story on this phone is that I got it July of last year and somewhere in Feb/Mar of this year
I installed a CustomRom for the first time, SlimICS, then I gave it to my wife as I got a GalaxyNote.
Then about a week ago it started to act up, at first it keeps on rebooting, then it starts to
show a message after reboot that encrytion has failed and has to be factory reseted, my wife
just basically ignore the message and just reboot again... it worked for a while, then the other
day, it rebooted itself into recovery, and when booted everything is just amiss, forceclose everywhere
notification is missing... so I thought maybe time for a new ROM or something, so I decided to
bring it back to Stock GB Rom first... but even this I cant seem to accomplish.
Anyways I just tried to flash the package Rescue kit for i9000 suggested by xsenman from heimdall,
but still after rebooting, it goes to recovery with this error:
--Copying media files
E:failed to mount /sdcard (File exists)
E:copy_dbdata_media:Cant mount /sdcard
your storage not prepared yet. please use UI
menu for format and reboot actions.
Meida files copy failed.
--Wiping data...
Formatting /data
E:format_volume: rfs format failed on /dev/block/mmcblkOp2
Formatting /dbdata
Formatting /cache
Deleted Meta Data
Data Wipe Failed
Also if I may add, I cant seem to turn the unit off without taking the battery out, because it just keeps on going back to
recovery.
Any ideas?
delphiguy said:
Any ideas?
Click to expand...
Click to collapse
had the solution for this added to Quick Solutions, just click Collections for Android below, scroll down and try it.
You are boot looping because you don't have /dbdata. This seems to he normal when flashing back to stock. Do a search for a galaxy s dbdata.tar and flash it under pda in Odin. Thats what I have to do.
Good luck
Sent from my GT-I9000 using xda premium
xsenman said:
had the solution for this added to Quick Solutions, just click Collections for Android below, scroll down and try it.
Click to expand...
Click to collapse
Apologies for my late reply... I've tried doing all that is in your page but still no luck. I guess my wifes phone is bricked and needs to be
serviced by Samsung, I just hope it doest cost us much. Thanks for all the help.
I currently own a Samsung Galaxy S3 i9305 that is running on CM11 4.4.3 nightly. Just today the phone battery died, but somehow the phone booted up again but was stuck on the initial samsung boot logo, the one with the device name and model number. I could only enter CWM, where i got the errors showing:
E: Can't mount /cache/recovery/command/
E: Can't mount /cache/recovery/log/
E: Can't open /cache/recovery/log/
E: Can't mount /cache/recovery/last_log/
E: Can't open /cache/recovery/last_log/
E: Can't mount /cache/recovery/last_install/
E: Can't open /cache/recovery/last_install/
Then I proceeded to factory wipe the phone, which didn't work. Tried wiping the system, didn't work either. I even tried going back to stock ROM using Odin but it kept showing that it failed to do so. So now I can only move between recovery and download mode, nothing else. Can't mount system, SD and so on.
Hope someone has a solution for this problem. I really need my phone... Thanks to whoever can help!!
anmolgrao said:
I currently own a Samsung Galaxy S3 i9305 that is running on CM11 4.4.3 nightly. Just today the phone battery died, but somehow the phone booted up again but was stuck on the initial samsung boot logo, the one with the device name and model number. I could only enter CWM, where i got the errors showing:
E: Can't mount /cache/recovery/command/
E: Can't mount /cache/recovery/log/
E: Can't open /cache/recovery/log/
E: Can't mount /cache/recovery/last_log/
E: Can't open /cache/recovery/last_log/
E: Can't mount /cache/recovery/last_install/
E: Can't open /cache/recovery/last_install/
Then I proceeded to factory wipe the phone, which didn't work. Tried wiping the system, didn't work either. I even tried going back to stock ROM using Odin but it kept showing that it failed to do so. So now I can only move between recovery and download mode, nothing else. Can't mount system, SD and so on.
Hope someone has a solution for this problem. I really need my phone... Thanks to whoever can help!!
Click to expand...
Click to collapse
Seems like the problem lies with the recovery, cant mount and open its own files. the recovery related files should be in your internal sd (phone memory) to delete all of that with all the other systems stuff, try this:
- wipe data factory reset
- wipe cache partition
- in mounts and storage --> format system/format cache/format data and now the internal sd = format /data and /data/media (/sdcard)
if you want delete also everything in your external sd, then format /storage/sdcard1
- in advanced --> wipe dalvik cache
now turn off your device in power option --> power off. boot into downloadmode and now flash the stock rom with odin, as everhting is wiped odin shouldnt give you errors now.
i hope this helps mate..
MaHo_66 said:
Seems like the problem lies with the recovery, cant mount and open its own files. the recovery related files should be in your internal sd (phone memory) to delete all of that with all the other systems stuff, try this:
- wipe data factory reset
- wipe cache partition
- in mounts and storage --> format system/format cache/format data and now the internal sd = format /data and /data/media (/sdcard)
if you want delete also everything in your external sd, then format /storage/sdcard1
- in advanced --> wipe dalvik cache
now turn off your device in power option --> power off. boot into downloadmode and now flash the stock rom with odin, as everhting is wiped odin shouldnt give you errors now.
i hope this helps mate..
Click to expand...
Click to collapse
Tried formatting everything...only format boot worked. Can't wipe cache either. Everything comes up as failed. I have no idea what to do, do I use Odin to flash a new recovery? Odin can detect my phone but so far the attempts to go back to stock ROM has been failing as I mentioned. Would this be hard brick or soft brick? Thanks anyway!!
anmolgrao said:
Tried formatting everything...only format boot worked. Can't wipe cache either. Everything comes up as failed. I have no idea what to do, do I use Odin to flash a new recovery? Odin can detect my phone but so far the attempts to go back to stock ROM has been failing as I mentioned. Would this be hard brick or soft brick? Thanks anyway!!
Click to expand...
Click to collapse
yes, seems like you have to flash another recovery with odin to replace cwm. lets try that! download here philz touch 6.41.6 and flash with odin then see if the problem still persists, if you have succes flash immediately stock rom, to start fresh again.
i wouldnt say you have hardbricked it since you can go into downloadmode, probably a softbrick..
MaHo_66 said:
yes, seems like you have to flash another recovery with odin to replace cwm. lets try that! download here philz touch 6.41.6 and flash with odin then see if the problem still persists, if you have succes flash immediately stock rom, to start fresh again
Click to expand...
Click to collapse
Thanks a lot!! Will try it out tmrw, cause Ive got to do other stuff... just to stay a step ahead, what happens if this fails too?
in that case you will need to do a full install with 4 files(not package) and a PIT file to re-create your partitions...if this fails phone is bricked...hardware bricked...
anmolgrao said:
Thanks a lot!! Will try it out tmrw, cause Ive got to do other stuff... just to stay a step ahead, what happens if this fails too?
Click to expand...
Click to collapse
if this fails, then nothing will happen. you have to find a way to restore back to stock, if you cant i guess you will need to bring the device to your local service shop. but try everything and search everywhere for a solution, im sure there is a way to fix it !!
---------- Post added at 03:54 PM ---------- Previous post was at 03:45 PM ----------
spiderman07 said:
in that case you will need to do a full install with 4 files(not package) and a PIT file to re-create your partitions...if this fails phone is bricked...hardware bricked...
Click to expand...
Click to collapse
im sorry but you need to stop talking bull**** man!! oke, he could try the 4 files and pit file method but you cant say its hardware bricked..
if so, then do explain pls why you think its hardbricked??
sorry if i said bull****...but if this will happens to me(i flash different roms every week so this might happen) what is to do?
spiderman07 said:
sorry if i said bull****...but if this will happens to me(i flash different roms every week so this might happen) what is to do?
Click to expand...
Click to collapse
thats what we trying to find out dude... if i knew exactly what to do in such case, i would have told it by now
MaHo_66 said:
yes, seems like you have to flash another recovery with odin to replace cwm. lets try that! download here philz touch 6.41.6 and flash with odin then see if the problem still persists, if you have succes flash immediately stock rom, to start fresh again.
i wouldnt say you have hardbricked it since you can go into downloadmode, probably a softbrick..
Click to expand...
Click to collapse
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> SingleDownload.
<ID:0/009> recovery.img
<ID:0/009> NAND Write Start!!
<ID:0/009> FAIL!
<ID:0/009>
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
This is the result of trying to install a new recovery...what to do now?
It feels like we are running out of options here..
Sent from my GT-I9305 using Tapatalk
anmolgrao said:
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> SingleDownload.
<ID:0/009> recovery.img
<ID:0/009> NAND Write Start!!
<ID:0/009> FAIL!
<ID:0/009>
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
This is the result of trying to install a new recovery...what to do now?
Click to expand...
Click to collapse
hey do you have another usb cable (original preferred) try with another if you have and try every possible usb port. i had one or two times this same problem using usb port 2.0, but i also have a usb port 3.0 which is much better and that worked for me, since then im using usb port 3.0. you have usb debugging enabled right in developer options? anyway try this with recovery and a stock official firmware
MaHo_66 said:
hey do you have another usb cable (original preferred) try with another if you have and try every possible usb port. i had one or two times this same problem using usb port 2.0, but i also have a usb port 3.0 which is much better and that worked for me, since then im using usb port 3.0. you have usb debugging enabled right in developer options? anyway try this with recovery and a stock official firmware
Click to expand...
Click to collapse
Not working at all ...guess I'll have to take it down to a technician since I'm not too knowledgeable about the 4 files stuff and all. Hopefully I won't have to go and get a lousier phone hahaha. Anyway thanks to all who tried to help me, really appreciate it!!
gt-i9305
debrick.bin for gt-i9305 ?
Hi all !
Since a few days i have an Samsung Galaxy S4 Active (i9295), in the past i always rooted my Samsung Phones and flashed them with a custom ROM.
I boot up phone in recovery/download mode, restarting the phone while holding volume down.
The android figure pops up and everything looks fine, so i connect it to the computer and start Odin 3.07 (also tried other versions)
Odin can communicate with the device and shows [COM4], i press AP/PDA depening on Odin version and select the custom recovery file. I get back the following in the console.
Code:
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!
Odin tells me, RESTART on the top and indeed the device is restarting. It boots normally without a problem or error. Odin still shows RESTART on the computer screen.
Now im like, did it worked ? Lets boot to recovery !
No, it didnt work... No custom recovery.. BUT ! Odin now shows Passed and give me the following output in the console.
Code:
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
I tried TWERP recovery, CWM Recovery and CWM with swipe.
Also tried to use a other computer, this didnt make any diffrence.
I hope for some tips
Oh, im stock now !
BrianVogel said:
Hi all !
Since a few days i have an Samsung Galaxy S4 Active (i9295), in the past i always rooted my Samsung Phones and flashed them with a custom ROM.
I boot up phone in recovery/download mode, restarting the phone while holding volume down.
The android figure pops up and everything looks fine, so i connect it to the computer and start Odin 3.07 (also tried other versions)
Odin can communicate with the device and shows [COM4], i press AP/PDA depening on Odin version and select the custom recovery file. I get back the following in the console.
Code:
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!
Odin tells me, RESTART on the top and indeed the device is restarting. It boots normally without a problem or error. Odin still shows RESTART on the computer screen.
Now im like, did it worked ? Lets boot to recovery !
No, it didnt work... No custom recovery.. BUT ! Odin now shows Passed and give me the following output in the console.
Code:
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
I tried TWERP recovery, CWM Recovery and CWM with swipe.
Also tried to use a other computer, this didnt make any diffrence.
I hope for some tips
Oh, im stock now !
Click to expand...
Click to collapse
I had this exact same issue when I tried to install custom recovery and it took me longer than it should have to solve. I rooted the phone first and then I was able to flash custom recovery. I have no idea why it worked, but it did. Try that and let me know.
Thanks for your quick reply
I always install SuperUser with CWM, so how can i do this without CWM ?
BrianVogel said:
Thanks for your quick reply
I always install SuperUser with CWM, so how can i do this without CWM ?
Click to expand...
Click to collapse
FIXED !
No root needed
When u flash with odin and it does a reboot, DIRECTLY input volume UP.
First reboot needs to enter CWM to let it work, if you skip this, it will be removed and default again.
Phone is flashed now without any problems
@BrianVogel
It is best to completely power off, wait, enter download mode.
If needed - modem.bin and NON-HLOS.bin can be then be Odin flashed without repeating the flash twice. Many shady guides tell you to flash modems twice to "make it stick". The reason it won't stick is download mode entered from restart meny.
Never run Odin on same PC where Kies is installed. Odin and Kies will fight to gain control of USB connected device.
Some borked Win7 need to run a Fix from M$ KB to properly detect Samsung phone as hardware even after installation of USB driver. Google to find the Fix, download and run.
Always connect directly to PC USB - never USB hub.
I had same problem and solve with these steps:
- In ODIN uncheck "Auto-reboot"
- flash using AP/PDA as you did, but your phone remains on
- disconnect cable
- now press Home + Volume Up + Power and hold while phone turn off and turn on again into recovery
- you should see new recowery and follow on screen steps
Hello everyone!
After browsing the forums and reading through some of the information available on bricked Galaxy Note N7000 devices, I decided to post a thread about my specific issue, given that it happened spontaneously, on a device which was never modded/rooted in any way, and which has been kept gingerly for almost four years! I will provide a brief, step-by-step overview of the issue as well as the different attempts at addressing it that have already been undertaken, in the hope that some of you will be so kind as to give me your opinion on what I could do next!
- A couple days ago, I received a phone call, and, as usual, I connected my headphones to the device. I immediately heard a crackling noise from them, as the device rebooted itself.
- I noticed that the device was stuck on the Samsung Galaxy Note GT - N7000 black and white logo. As a result, I tried turning it off, and connecting it to my charger. The grey battery icon popped up, and was quickly substituted by the green "charging" icon with moving dots. After a few minutes, I tried turning on the phone again, and it was stuck on the splash screen once more.
- I tried going into the recovery menu, which I successfully did, and, upon rebooting from it, the phone moved past the splash screen to the pink and purple Samsung animated logo; that was quickly followed by a screen I had never seen before, a password bar, and the message "Enter password to use encrypted device storage". Not knowing what to do, I turned off the device.
- the next logical step was to contact Samsung Italy, and I was told to try wiping cache and data from the recovery menu and attempt a restore to factory settings. Nothing particular happened, as the phone got once again stuck on the Note splashscreen, and the recovery menu showed a series of red lines, containing information such as:
E:failed to mount /efs (No such file or directory)
E:failed to mount /system ((No such file or directory))
# MANUAL MODE #
--Appling Multi-CSC
E:failed to mount /system (No such file or directory)
can't mount '/system' (No such file or directory)
E:failed to mount /cache (No such file or directory)
can't mount '/cache' (No such file or directory)
- Next step was to take the phone to a local repair shop, where I was told that flashing the firmware was really my only option, given the functioning download and recovery menus; I left the phone with the technician, who called me later in the evening asking me if the phone was still under warranty. I told him there was no warranty, so he attempted to install a custom recovery menu via Odin, namely the following versions of PhilZ: PhilZ-cwm6-XXLSZ-OXA-4.93.6.tar and PhilZ-cwm6-XXLTA-ATL-5.15.0.tar. Upon seeing the failed install, he decided to wait for the firmware to finish its download (abysmal connection speeds in my area) and try flashing it.
- The following morning, I joined the technician in his office as he showed me that the phone could now no longer access recovery mode, seeing as the custom recovery install failed, and the flash attempt counter had gone up to three (like I mentioned earlier, I took great care not to do anything too fancy with this phone, seeing as it's my work phone), with a yellow warning sign appearing under the splash screen.
- The technician's attempt to install stock firmware (N7000XXLSZ_N7000XXLSO_N7000ITVLS4_HOME.tar.md5) was met with failure. Odin fails at the "NAND Write" step, as shown by the following log (I replicated it at home):
<ID:0/012> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXLSZ_N7000XXLSO_N7000ITVLS4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/012> Odin engine v(ID:3.1005)..
<ID:0/012> File analysis..
<ID:0/012> SetupConnection..
<ID:0/012> Initialzation..
<ID:0/012> Get PIT for mapping..
<ID:0/012> Firmware update start..
<ID:0/012> SingleDownload.
<ID:0/012> cache.img
<ID:0/012> NAND Write Start!!
<ID:0/012> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
- attempting to install a PIT file via Odin to repartition the device (filename: Q1_20110914_16GB) was also met with failure (the error message said something like "failed to repartition"), but, as I didn't pay enough attention to the steps taken by the technician to be able to replicate the operations at home - like I said, I've never done this before.
To sum up, the phone is showing the following symptoms:
- battery icon not changing from grey to green
- stock recovery menu not accessible due to a failed attempt at installing a custom recovery menu (+3 custom flash counter)
- yellow triangle on splash screen, where the device remains stuck indefinitely
- download mode still accessible, device recognized by Odin, firmware flash fails at NAND Write Start
I really hope some of you will be able to give me your two cents on how to proceed! Thank you in advance for any and all help!
Lightside
Sounds tough, but you did right by pouring everything you know on the problem here.
First I'd try to use the stock partition available here: http://forum.xda-developers.com/showthread.php?t=2642299
Then look for a PhilZ recovery in this forum to Odin flash.
If it works, then proceed to flash a stock rom via recovery.
If not, then try the partition method with a stock rom. I used the guide provided in the link above and it worked flawlessly.
I'd wait for other members to pour in their thoughts on this if they're gracious enough but you're still welcome to try this
AutumQueen92 said:
Sounds tough, but you did right by pouring everything you know on the problem here.
First I'd try to use the stock partition available here: http://forum.xda-developers.com/showthread.php?t=2642299
Then look for a PhilZ recovery in this forum to Odin flash.
If it works, then proceed to flash a stock rom via recovery.
If not, then try the partition method with a stock rom. I used the guide provided in the link above and it worked flawlessly.
I'd wait for other members to pour in their thoughts on this if they're gracious enough but you're still welcome to try this
Click to expand...
Click to collapse
Hello, and thank you for your advice! I have just tried flashing the pit file provided in the thread you linked, and this is the Odin log:
<ID:0/012> Added!!
<ID:0/012> Odin engine v(ID:3.1005)..
<ID:0/012> File analysis..
<ID:0/012> SetupConnection..
<ID:0/012> Initialzation..
<ID:0/012> Set PIT file..
<ID:0/012> DO NOT TURN OFF TARGET!!
<ID:0/012> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
EDIT: I've tried every Odin version I could get my hands on, and attempted using all 5 custom pit files. I even tried reflashing PhilZ-cwm6-XXLTA-ATL-5.15.0.tar, to no avail. Have I exhausted all my options?
Lightside said:
Hello everyone!
After browsing the forums and reading through some of the information available on bricked Galaxy Note N7000 devices, I decided to post a thread about my specific issue, given that it happened spontaneously, on a device which was never modded/rooted in any way, and which has been kept gingerly for almost four years! I will provide a brief, step-by-step overview of the issue as well as the different attempts at addressing it that have already been undertaken, in the hope that some of you will be so kind as to give me your opinion on what I could do next!
- A couple days ago, I received a phone call, and, as usual, I connected my headphones to the device. I immediately heard a crackling noise from them, as the device rebooted itself.
- I noticed that the device was stuck on the Samsung Galaxy Note GT - N7000 black and white logo. As a result, I tried turning it off, and connecting it to my charger. The grey battery icon popped up, and was quickly substituted by the green "charging" icon with moving dots. After a few minutes, I tried turning on the phone again, and it was stuck on the splash screen once more.
- I tried going into the recovery menu, which I successfully did, and, upon rebooting from it, the phone moved past the splash screen to the pink and purple Samsung animated logo; that was quickly followed by a screen I had never seen before, a password bar, and the message "Enter password to use encrypted device storage". Not knowing what to do, I turned off the device.
- the next logical step was to contact Samsung Italy, and I was told to try wiping cache and data from the recovery menu and attempt a restore to factory settings. Nothing particular happened, as the phone got once again stuck on the Note splashscreen, and the recovery menu showed a series of red lines, containing information such as:
E:failed to mount /efs (No such file or directory)
E:failed to mount /system ((No such file or directory))
# MANUAL MODE #
--Appling Multi-CSC
E:failed to mount /system (No such file or directory)
can't mount '/system' (No such file or directory)
E:failed to mount /cache (No such file or directory)
can't mount '/cache' (No such file or directory)
- Next step was to take the phone to a local repair shop, where I was told that flashing the firmware was really my only option, given the functioning download and recovery menus; I left the phone with the technician, who called me later in the evening asking me if the phone was still under warranty. I told him there was no warranty, so he attempted to install a custom recovery menu via Odin, namely the following versions of PhilZ: PhilZ-cwm6-XXLSZ-OXA-4.93.6.tar and PhilZ-cwm6-XXLTA-ATL-5.15.0.tar. Upon seeing the failed install, he decided to wait for the firmware to finish its download (abysmal connection speeds in my area) and try flashing it.
- The following morning, I joined the technician in his office as he showed me that the phone could now no longer access recovery mode, seeing as the custom recovery install failed, and the flash attempt counter had gone up to three (like I mentioned earlier, I took great care not to do anything too fancy with this phone, seeing as it's my work phone), with a yellow warning sign appearing under the splash screen.
- The technician's attempt to install stock firmware (N7000XXLSZ_N7000XXLSO_N7000ITVLS4_HOME.tar.md5) was met with failure. Odin fails at the "NAND Write" step, as shown by the following log (I replicated it at home):
<ID:0/012> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXLSZ_N7000XXLSO_N7000ITVLS4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/012> Odin engine v(ID:3.1005)..
<ID:0/012> File analysis..
<ID:0/012> SetupConnection..
<ID:0/012> Initialzation..
<ID:0/012> Get PIT for mapping..
<ID:0/012> Firmware update start..
<ID:0/012> SingleDownload.
<ID:0/012> cache.img
<ID:0/012> NAND Write Start!!
<ID:0/012> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
- attempting to install a PIT file via Odin to repartition the device (filename: Q1_20110914_16GB) was also met with failure (the error message said something like "failed to repartition"), but, as I didn't pay enough attention to the steps taken by the technician to be able to replicate the operations at home - like I said, I've never done this before.
To sum up, the phone is showing the following symptoms:
- battery icon not changing from grey to green
- stock recovery menu not accessible due to a failed attempt at installing a custom recovery menu (+3 custom flash counter)
- yellow triangle on splash screen, where the device remains stuck indefinitely
- download mode still accessible, device recognized by Odin, firmware flash fails at NAND Write Start
I really hope some of you will be able to give me your two cents on how to proceed! Thank you in advance for any and all help!
Lightside
Click to expand...
Click to collapse
OMG this is the condition of my GS2 , my note is perfect, im trying something tomorrow, will let you know
coko___bear said:
OMG this is the condition of my GS2 , my note is perfect, im trying something tomorrow, will let you know
Click to expand...
Click to collapse
At this point, I appreciate any and all help, so thanks for replying
Up?