Hello all, all of a sudden my phone start booting in to CWM with the error message:
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
With any attempts to restore/wipe data, I get a similar message saying it is unable to mount. Now, I am unable to boot my phone even to the CWM menu since it keeps rebooting on its own and sometimes it won't even go into the CWM menu. I have looking up this error many times and I have been unable to find a solution that works for me.
I have tried wiping the cache from CWM, wiping all data, and nandroid data, all of which ended in a error message except wiping the cache which did not solve the problem.
I have also tried this : http://forum.xda-developers.com/showthread.php?t=1284196 but could not get my computer to recognize the device. If anyone could help or provide any suggestions, it would be greatly appreciated.
Try flashing firmware via Odin. Uninstall/ reinstall drivers if connection issues.
Sent from my SGH-T999 using Tapatalk
DocHoliday77 said:
Try flashing firmware via Odin. Uninstall/ reinstall drivers if connection issues.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Could you provide some instructions as to how I can try flashing firmware via odin? One of my attempts at this has ended in an "FAIL" in Odin.
woahs said:
Could you provide some instructions as to how I can try flashing firmware via odin? One of my attempts at this has ended in an "FAIL" in Odin.
Click to expand...
Click to collapse
Doc's how-to:
http://forum.xda-developers.com/showpost.php?p=33115792&postcount=2
Scroll down to the blue "How to Flash the Stock Firmware" section
GenericAsianGuy said:
Doc's how-to:
http://forum.xda-developers.com/showpost.php?p=33115792&postcount=2
Scroll down to the blue "How to Flash the Stock Firmware" section
Click to expand...
Click to collapse
I have tried this and when I hit Start in Odin, I get the message:
<ID:0/006> SetupConnection..
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
and a FAIL! in the top left.
If kies is installed uninstall it. Does odin go through the md5 check? What is your current firmware build and what build are you trying to flash? Also uninstall drivers through device manager. Then reinstall.
Sent from my SGH-T999 using Tapatalk
DocHoliday77 said:
If kies is installed uninstall it. Does odin go through the md5 check? What is your current firmware build and what build are you trying to flash? Also uninstall drivers through device manager. Then reinstall.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
My phone doesn't boot up anymore. Goes straight to CWM and reboots itself. I don't remember what the current firmware build is and I'm not trying to flash anything. My phone just decided to turn off one day and won't turn back on.
Do you at least know if you updated to 4.3? If so, you can only flash the same or newer firmware from now on. So when you tried to flash with odin, if you used older firmware it would fail.
Can you boot into download mode? Hold volume down, home and power.
Sent from my SGH-T999 using Tapatalk
DocHoliday77 said:
Do you at least know if you updated to 4.3? If so, you can only flash the same or newer firmware from now on. So when you tried to flash with odin, if you used older firmware it would fail.
Can you boot into download mode? Hold volume down, home and power.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Booting in downloading mode was working at some point by it isn't anymore. I don't think I have updated to 4.3, it is most likely 4.1 or 4.2 and I have tried flashing 4.3.
I suggest trying to use the debrick.img from NC2 then. Its the latest available so it should work regardless of what you previously had. If you do get download mode this way you will have to odin flash the NC2 firmware.
Sent from my SGH-T999 using Tapatalk
Related
Went from the stock ICS on my cousins phone and updated him to the stock JB through Kies, and now on boot it just gets stuck on the 4g screen.
Also, when I do power+volume+ button it says "E:failed to mount /efs (invalid argument)" and E:Can't mount /efs/log/boot_cause and Can't open /efs/log/boot_cause
Any ideas guys?
Fabiofan said:
Went from the stock ICS on my cousins phone and updated him to the stock JB through Kies, and now on boot it just gets stuck on the 4g screen.
Also, when I do power+volume+ button it says "E:failed to mount /efs (invalid argument)" and E:Can't mount /efs/log/boot_cause and Can't open /efs/log/boot_cause
Any ideas guys?
Click to expand...
Click to collapse
Grab the GB27 odin build from the repository. Flash that. You should be good to go.
Sent from my SPH-D710 using xda premium
Trying to get a log with ADB
graydiggy said:
Grab the GB27 odin build from the repository. Flash that. You should be good to go.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Still no go for me after running rwilco12.com/Files/Devices/Samsung%20Galaxy%20S2%20%28Sprint%29%20%28SPH-D710%29/Stock%20ROMs/JB/GB27/No%20Data%20Restore/Rooted/SPH-D710_GB27_1014481_Rooted_Nodata.exe[/url]
I also tried tGA10_Agats Recovery.exe, wiped the dalvik cache, cache partition, and fixed permissions. Then I ran SPH-D710_GB27_1014481_Kernel.exe to get the stock kernel back.
adb devices
List of devices attached
try the restore, not the nodata
I've tried all of these methods and am having the same issues. I'm very close to just bricking it and calling it a wash. Is there anything at all I can do that will allow me to restore the missing info need for the phone to boot properly?
Could you flash FL24 (restore, NOT nodata) then get the OTA update? I didn't have any luck with flashing GB27.
As graydiggy mentioned try the One-click FULL RESTORE/RESET. Make sure you follow the directions from here. Also run the One-click 'as adminstrator' on your PC too.
Fabiofan said:
Went from the stock ICS on my cousins phone and updated him to the stock JB through Kies, and now on boot it just gets stuck on the 4g screen.
Also, when I do power+volume+ button it says "E:failed to mount /efs (invalid argument)" and E:Can't mount /efs/log/boot_cause and Can't open /efs/log/boot_cause
Any ideas guys?
Click to expand...
Click to collapse
Ok I had the same problem and found a solution! First to get off that bootloop go to rwilco.com and download fl22 and use odin to install it which is ICS, root your phone with the agat 0.6.8 then you go to the play store and download busybox free and gs2 repair. Run busybox do a smart install then open gs2 repair and on the second tab do the 1st and 2nd options only, restart your phone now you can upgrade to jellybean.
My dad's Wind Note 2 (SGH-T889V) is stuck in download mode with the error message "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
He told me he left it to charge overnight and when he woke up, it was just a black screen with a blue led light. He couldn't accept calls or turn the screen on so after about an hour, he pulled out the battery and put it back in. Then the error message came up with no led light.
I tried using kies, but I have no recovery code. And if I try the firmware upgrade, after it succeeds, it just reboots to the same error message.
I used it before and had rooted and flashed some custom ROMs on it, but when I gave it to my dad, I returned to stock and unrooted. The method I followed was to download the stock odin flashable firmware and flash through odin.
So now I have been trying to flash the stock firmware using the same method. For other people who have this error, apparently that is supposed to fix it. But even after it passes in odin, the phone just reboots straight back to the same error message.
I have also tried to flash clockworkmod recovery through odin and after it passes, it shows the Samsung logo (not animation) and just stays there.
Flash counter is at 4 I think, so I don't want to send it in for them to fix.
I am pretty sure the battery is getting drained when the phone is supposed to be off. When I pull the battery, put it back in and then leave it overnight, in the morning I have to charge it up before I can turn it on.
So here is the situation:
With stock image and stock recovery flashed:
- trying to boot regularly gives the error (download mode)
- trying to boot to recovery gives same error (download mode)
- trying to boot to download mode succeeds with no error
With stock image and clockworkmod recovery flashed:
- trying to boot regularly shows the error message (download mode)
- trying to boot to recovery hangs at the Samsung logo
- trying to boot to download mode succeeds with no error
Image showing all the screens I have been able to get to..
I have tried this using linux + heimdall and xp + odin as well as windows 7 + odin. Heimdall was a little confusing for me though, so I didn't follow through with it.. If anyone has detailed instructions on how to use it with the T889(V) Note 2, I could try.
If you have any idea about how I could solve this, please let me know. Thanks
HI, sorry for your troubles ... The pic i attached, will work the same as download mode.. Can you link me the file you flashed in odin please
deeznutz1977 said:
HI, sorry for your troubles ... The pic i attached, will work the same as download mode.. Can you link me the file you flashed in odin please
Click to expand...
Click to collapse
I used the image from sammobile http://www.hotfile.com/dl/196123502/b8cb710/T889VVLBMA3_T889VYVLBMA3_GLW.zip.html
mobabur94 said:
I used the image from sammobile http://www.hotfile.com/dl/196123502/b8cb710/T889VVLBMA3_T889VYVLBMA3_GLW.zip.html
Click to expand...
Click to collapse
did you try using another cable? different usb port? re downloading the file... did you factory reset before flashing ?
deeznutz1977 said:
did you try using another cable? different usb port? re downloading the file... did you factory reset before flashing ?
Click to expand...
Click to collapse
Yeah, I have tried different cables in different usb ports on different computers running different operating systems. I downloaded the file twice.
I could not factory reset before flashing because I could not boot to android, or get into recovery mode
mobabur94 said:
Yeah, I have tried different cables in different usb ports on different computers running different operating systems. I downloaded the file twice.
I could not factory reset before flashing because I could not boot to android, or get into recovery mode
Click to expand...
Click to collapse
Try flashing this http://forum.xda-developers.com/showthread.php?t=1975560 i know its rooted but...
deeznutz1977 said:
Try flashing this http://forum.xda-developers.com/showthread.php?t=1975560 i know its rooted but...
Click to expand...
Click to collapse
Thanks, I am downloading it now. I'll let you know how it goes.
deeznutz1977 said:
Try flashing this http://forum.xda-developers.com/showthread.php?t=1975560 i know its rooted but...
Click to expand...
Click to collapse
I flashed that image which passed in odin but it also doesn't work (same error message), just like the sammobile one :/
Any other ideas?
Maybe try flashing another kernel or try using Mr skips note2 toolkit.... I'm sorry. I don't know. What version of Odin are you using
Sent from my SGH-T889 using Tapatalk 4
deeznutz1977 said:
Maybe try flashing another kernel or try using Mr skips note2 toolkit.... I'm sorry. I don't know. What version of Odin are you using
Sent from my SGH-T889 using Tapatalk 4
Click to expand...
Click to collapse
I can't use the toolkit because I can't get into adb mode.. I tried using odin 1.85 and 3.07 and 3.04 :s
I'm not sure which kernel to try or how to flash one without cwm or twrp
Try the cf auto root by chainfire in original Dev. ? Damn dude
Sent from my SGH-T889 using Tapatalk 4
deeznutz1977 said:
Try the cf auto root by chainfire in original Dev. ? Damn dude
Sent from my SGH-T889 using Tapatalk 4
Click to expand...
Click to collapse
I downloaded CF-Auto-Root but didn't flash it yet. Instead, I noticed that the instructions said to disconnect usb, start odin, enter download mode, connect usb and then continue. I guess I hadn't been disconnecting and reconnecting before because I just tried doing that with the stock image and cwm and I got into cwm.
However I cannot really do anything because I am getting the following error in cwm:
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
I get similar "Can't mount " errors when going into mounts and storage and trying to mount anything.
I have a feeling there is something wrong with the partition table? Do I need to check re-partition? Will I need a .pit file?
I want to try and flash stock or cf-auto-root with re-partition checked and see if that fixes anything, but I think I would need a .pit file.. @deeznuts1977, what do you think?
mobabur94 said:
I downloaded CF-Auto-Root but didn't flash it yet. Instead, I noticed that the instructions said to disconnect usb, start odin, enter download mode, connect usb and then continue. I guess I hadn't been disconnecting and reconnecting before because I just tried doing that with the stock image and cwm and I got into cwm.
However I cannot really do anything because I am getting the following error in cwm:
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
I get similar "Can't mount " errors when going into mounts and storage and trying to mount anything.
I have a feeling there is something wrong with the partition table? Do I need to check re-partition? Will I need a .pit file?
I want to try and flash stock or cf-auto-root with re-partition checked and see if that fixes anything, but I think I would need a .pit file.. @deeznuts1977, what do you think?
Click to expand...
Click to collapse
No re partition. That will cause problems. Cf is Odin flashable as for the errors there logs don't worry too much about that now..... Try using twrp. It's much better and more stable imo
Sent from my SGH-T889 using Tapatalk 4
netflix won't work
mobabur94 said:
I can't use the toolkit because I can't get into adb mode.. I tried using odin 1.85 and 3.07 and 3.04 :s
I'm not sure which kernel to try or how to flash one without cwm or twrp
Click to expand...
Click to collapse
i'm on
[ROM][OFFICIAL][JB 4.3] PAC-man [CM 10.2][PA 3.99][AOKP MR2]
but Netflix won't play movies. Installation seems to be ok, Netflix loading ok, but movies won't play.
any fixs
deeznutz1977 said:
No re partition. That will cause problems. Cf is Odin flashable as for the errors there logs don't worry too much about that now..... Try using twrp. It's much better and more stable imo
Sent from my SGH-T889 using Tapatalk 4
Click to expand...
Click to collapse
Crap, I have no clue what to do now. I flashed cf-auto-root and then it just turned off. I don't think the battery was dead because 20 minutes before in cwm I saw percentage to be around 60%. Now I can't turn the phone on at all with any combination. Tried a different battery too. Odin said the flash passed too..
mobabur94 said:
Crap, I have no clue what to do now. I flashed cf-auto-root and then it just turned off. I don't think the battery was dead because 20 minutes before in cwm I saw percentage to be around 60%. Now I can't turn the phone on at all with any combination. Tried a different battery too. Odin said the flash passed too..
Click to expand...
Click to collapse
When you plug it in what does it do.
Sent from my SGH-T889 using Tapatalk 4
deeznutz1977 said:
When you plug it in what does it do.
Sent from my SGH-T889 using Tapatalk 4
Click to expand...
Click to collapse
When I plug it in, I get no device detected stuff in windows and I don't see and 'added' in Odin.
On my Linux computer, I plugged in my galaxy nexus and lsusb detects it. But with this note 2, lsusb doesn't detect anything
Hey everyone,
Was hoping I could get some help on this.
So I never rooted my T-Mobile Galaxy S3, it's totally stock, but I'm about to sell it and I went to do the factory reset in the settings and when it finally rebooted it rebooted into recovery... So then I went to wipe data/factory reset and it started the process but after the cache and data wipe then I get:
E:failed to mount /cache (Invalid Argument)
E: Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to mount /cache (invalid argument
E: can't mount /cache/recovery/last_log
E: can't open /cache/recovery/last_log
(i just typed that quickly while staring at the screen so please excuse any typos)
Now if I reboot it just never seems to finish booting (well I let it go for a solid 5 minutes and nothing...
I'm gonna bring it to work today while I wait for some responses but any ideas whats wrong with this thing?
Thank you!
hmm. If you can get into download moade, you could try flashing the official firmware through Odin and see if you could factory wipe in the stock recovery.
If that doesn't work, you could also try flashing a pre-rooted firmware with clockworks mod recovery and try wiping from there, then flash back official firmware through Odin.
Sent from my SGH-T999 using Tapatalk
ayeitschris said:
hmm. If you can get into download moade, you could try flashing the official firmware through Odin and see if you could factory wipe in the stock recovery.
If that doesn't work, you could also try flashing a pre-rooted firmware with clockworks mod recovery and try wiping from there, then flash back official firmware through Odin.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
thanks i will try that. i've never actually used odin before, but looks like i CAN get into download mode, so hopefully i'm not totally screwed... only problem is i downloaded the wrong file and it says i have to wait 30 minutes to download another file haha. bah.
polarbearmc said:
thanks i will try that. i've never actually used odin before, but looks like i CAN get into download mode, so hopefully i'm not totally screwed... only problem is i downloaded the wrong file and it says i have to wait 30 minutes to download another file haha. bah.
Click to expand...
Click to collapse
Two Things
1. Make sure you grab the UVDMD5 file from Sammobile and then ODIN version 3.07. There's a nice tutorial on the Root 66 thread.
2. If you are selling, reset your flash counter with Triangle Away.
3. Do note the latest version of TWRP is unstable. If you are using TWRP then put at least 2.5 version. Given you are flashing via ODIN, its a moot anyway.
Perseus71 said:
Two Things
1. Make sure you grab the UVDMD5 file from Sammobile and then ODIN version 3.07. There's a nice tutorial on the Root 66 thread.
2. If you are selling, reset your flash counter with Triangle Away.
3. Do note the latest version of TWRP is unstable. If you are using TWRP then put at least 2.5 version. Given you are flashing via ODIN, its a moot anyway.
Click to expand...
Click to collapse
thanks for the info! i've got 37 seconds to go then i can download UVDMD5 haha so i'll report back later if it works.
also since i'm not (and have never been) rooted, I can't use Triangle Away, can I? i thought it was a root only app.
Yes its Root Only app. But then when you use Root66 image for UVDMD5, your phone will be rooted.
Perseus71 said:
Yes its Root Only app. But then when you use Root66 image for UVDMD5, your phone will be rooted.
Click to expand...
Click to collapse
SOOOO...
Here's the story... I wasn't totally honest about just downloading the wrong file, I felt dumb and left out that I also flashed with Odin the "wrong file" (The Kernel file only from the T999UVDMD5 firmware download page) and it was just stuck in a permanent booting at the Samsung screen... So Anyway while waiting on the full firmware file to download, I went through recovery and wiped one more time (post flashing the kernel) and voila! Booted right up to the setup screen! So anyway pointing me in the direction of using Odin definitely worked, so again, thank you.
couple of things real quick. please dont leave info out. people who are trying to help are using their own time to do so, and it just mskes it harder in them.
and in the future, just downliad firmware from my firmware thread. i made it so you dont have to wait on such slow downloads.
Sent from my T-Mobile MyTouch 3G Slide(HTC Espresso) using Tapatalk 2
DocHoliday77 said:
couple of things real quick. please dont leave info out. people who are trying to help are using their own time to do so, and it just mskes it harder in them.
and in the future, just downliad firmware from my firmware thread. i made it so you dont have to wait on such slow downloads.
Sent from my T-Mobile MyTouch 3G Slide(HTC Espresso) using Tapatalk 2
Click to expand...
Click to collapse
no problem. although i hadn't left anything out at first, just before my final message. also i'm terrible at searching XDA. i seriously searched for a solid 15 minutes (without finding your post) before deciding to post my message haha. sorry.
Hello, my note II died one night. Either displays battery icon when charging or stuck on samsung logo. I can get in to odin recovery but cannot get in to bootloader mode. Device is not rooted and I did not turn on usb debugging mode earlier on. And now is the question. What do I do to recover pictures from it?. Is it possible at all?
vocal said:
Hello, my note II died one night. Either displays battery icon when charging or stuck on samsung logo. I can get in to odin recovery but cannot get in to bootloader mode. Device is not rooted and I did not turn on usb debugging mode earlier on. And now is the question. What do I do to recover pictures from it?. Is it possible at all?
Click to expand...
Click to collapse
Do you have a custom recovery? If so: make a data backup.
Otherwise: try rooting and recovering using download mode. (If it still works)
There are many tutorials on rooting (with download mode).
Question: How long is it stuck on the samsung logo? Do you have a bootloop? You are not rooted, but are you on a custom rom?
klect said:
Do you have a custom recovery? If so: make a data backup.
Otherwise: try rooting and recovering using download mode. (If it still works)
There are many tutorials on rooting (with download mode).
Question: How long is it stuck on the samsung logo? Do you have a bootloop? You are not rooted, but are you on a custom rom?
Click to expand...
Click to collapse
It is not rooted. I have stock ROM and dont have any backups. It shows samsung galaxy note II for ever or sometimes battery logo but it frozen and dont shows its charging. Cannot go into bootloader mode just into odin mode
vocal said:
It is not rooted. I have stock ROM and dont have any backups. It shows samsung galaxy note II for ever or sometimes battery logo but it frozen and dont shows its charging. Cannot go into bootloader mode just into odin mode
Click to expand...
Click to collapse
And with odin mode you mean download mode? If so: Flash SU via odin, flash recovery, make a backup, flash a ROM. Most data will be in the backup, If you flash the ROM without wiping you still have all of your pictures and stuff.
Edit: I see you did not turn on USB debugging, however, as far as my knowledge goes, this is your only solution...
There is a way to push it to your device though (ADB), but I think it doesn't work without USB debugging...
vocal said:
Hello, my note II died one night. Either displays battery icon when charging or stuck on samsung logo. I can get in to odin recovery but cannot get in to bootloader mode. Device is not rooted and I did not turn on usb debugging mode earlier on. And now is the question. What do I do to recover pictures from it?. Is it possible at all?
Click to expand...
Click to collapse
Try to reflash stock rom using Odin. Flashing stock roms probaly keeps ur apps and data safe.. Unless you to a factory reset.. U can flash stock rom without triggering USB debugging
Sent from my GT-N7100 using XDA Premium 4 mobile app
Have you tried using kies? Isn't there an emergency firmware package or something like that. If your not rooted kies is your best bet
Sent from my GT-N7105 using Tapatalk
via odin iays : no pit partition and flahing failed
vocal said:
via odin iays : no pit partition and flahing failed
Click to expand...
Click to collapse
Try emergency firmware with kies if that doesn't work get the pit file from mskips toolkit. I think you have to go to the website for it now. skipsoft.net
Sent from my GT-N7105 using Tapatalk
sawdoctor said:
Try emergency firmware with kies if that doesn't work get the pit file from mskips toolkit. I think you have to go to the website for it now. skipsoft.net
Sent from my GT-N7105 using Tapatalk
Click to expand...
Click to collapse
finally I got PIT file for note II, cwm6 with root and stock ROM but...
odin3 stays forever on: get PIT for mapping.....
tried just PIT but same effect. Without PIT file it says: no PIT partition, flashing failed.
toolkit does not talk to the device as waiting for USB debugging mode on the device. even if I choose download via odin still the same.
Any ideas?
vocal said:
kies stays forever on:GET pit for mapping.....
toolkit does not talk to device as waiting for adb on the device. even if I choose download via odin.
Any ideas?
Click to expand...
Click to collapse
Don't know if this guide will help ?
http://forum.xda-developers.com/showthread.php?t=2261153
sawdoctor said:
Don't know if this guide will help ?
http://forum.xda-developers.com/showthread.php?t=2261153
Click to expand...
Click to collapse
thanks, but kies says: no response from the device
Is it possible that even if I can put device in the DL mode nothing can be done?
I tried kies on different PC. PC can see only USB camera and USB composite device and Kies stays forever on: connecting to device.
I tried my second device and kies recognized it straight away. Anyone have any ideas what is going on with my note II?
As I mentioned before I can put it into DL mode but it looks like its frozen just after doing that.
Any help will be appraciated.
I took note II from friend of mine to compare DL mode and I found something strange
His screen says:
ODIN MODE
Product NAME: GT-N7100
Custom binary download: NO
Current Binary: Samsung Official
System Status: Official
Knox warranty void: 0
AP SWAEV: A2
When mine says:
ODIN MODE
Product NAME:
Custom binary download: NO
Current Binary: Samsung Official
System Status: Custom
I have NOT changed ROM on my device and I had it boxed
Any ideas?
still trying different things as no replies on my post.
when I leave my device connected to PC (switched on as normal but showing only samsung logo) after 5 mins PC says found USB device, device not recognized. then after 5 seconds it disconnects. and it goes in circles. same if I try in bootloader mode, but it stays on samsung logo as well. In DL mode, PC recognizes only composite device and modem.... Any ideas please? I dont want recover data anymore as I think its lost but I would like to unbrick my note2
Did you flash pit file? If not, download it from here http://d-h.st/Dlv
Using ODIN, select the PIT file, and make sure to TICK the Re-partition option.
I hope you already have a stock ROM downloaded. In the PDA tab of ODIN,select that rom and then press start. Wait and pray.
zeeshanonlyme said:
Did you flash pit file? If not, download it from here http://d-h.st/Dlv
Using ODIN, select the PIT file, and make sure to TICK the Re-partition option.
I hope you already have a stock ROM downloaded. In the PDA tab of ODIN,select that rom and then press start. Wait and pray.
Click to expand...
Click to collapse
Yes I tried. It fails
<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> FAIL!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Are you sure the repartiton option was ticked? I seem to have forgotten whether it should be ticked or not.
Do one thing. After loading the necessary files, tick re partition.
if it fails,
Load all the necessary files and make sure repartition is NOT tickd.Report back.
zeeshanonlyme said:
Are you sure the repartiton option was ticked? I seem to have forgotten whether it should be ticked or not.
Do one thing. After loading the necessary files, tick re partition.
if it fails,
Load all the necessary files and make sure repartition is NOT tickd.Report back.
Click to expand...
Click to collapse
If I choose PIT file, re-partition box is ticked automaticaly. W/o re-partition box ticked, I have message: no binary file selected.
As I mensioned before, In DL mode, my device is not showing model number. Does it matter?
Before I tried all possibilities and suggestions on Win 8 PC, now trying on win 7 and I have more promising results, however I will try on newly installed system just to be sure that drivers and other stuff are ok. I tried different USB cables and different batteries. Still nothing, so hoping new system will help. except, anyone has different idea?
Ok, so I have done some research and even if I can put n7100 into DL mode but there is no product name displayed, device needs either new EMMC, or new PCB or JTAG. I will go with JTAG as my first option and will report as it might be usefull for someone in the future
Alright folks, here's what I've got:
An S3, which is rooted, using TWRP for recovery and on a CM11 nightly. This had been running happily with no problems since February.
About a week ago, it began randomly shutting down / restarting for no apparent reason. It would do this maybe once a day.
Two days ago, it did this again while I was surfing the internet, but then proceeded into a boot loop and now will not start up at all. It shows the Samsung screen, then the Galaxy S3 screen, then stops and loops on the CM animated screen. As far as I know I didn't do anything to trigger this - no new app downloads, no new ROM flashing, etc - it just did it suddenly in use.
I can successfully get into both download mode and recovery and the phone will stay there (so I don't think this is the power button issue), but I can't do anything useful from either mode. In TWRP I get error messages regarding failure to mount cache regardless of what I do. I can't do a factory reset or wipe it, and can't flash anything.
It will connect to Odin in Download mode, but anything I have tried there comes up "Fail", or "Complete - Write Operation Failed". Can't flash back to stock, can't flash CM again. I've tried a couple different cables and different USB ports, and reinstalling the drivers. The computer in question, which has worked with Odin before, is running Win 8.
I'm at the end of what I know to do to this thing, and am beginning to suspect it has a hardware problem. Any thoughts or things to try?
I'm in a similar boat as you :
I flashed a ROM, it was working w/o issue for 3 days then all of a sudden when I launched an app on my phone (don't recall which one, but one I used regularly), the phone rebooted and was stuck at the loading screen.
TWRP couldn't mount ANY partition either..
Here is my story...
http://forum.xda-developers.com/showthread.php?t=2725985
It's either a coincidental hardware failure or something weird is going on with the custom ROMS.
the.teejster said:
I'm in a similar boat as you :
I flashed a ROM, it was working w/o issue for 3 days then all of a sudden when I launched an app on my phone (don't recall which one, but one I used regularly), the phone rebooted and was stuck at the loading screen.
TWRP couldn't mount ANY partition either..
Here is my story...
http://forum.xda-developers.com/showthread.php?t=2725985
It's either a coincidental hardware failure or something weird is going on with the custom ROMS.
Click to expand...
Click to collapse
This does sound like a similar issue. However, since I had been running the same ROM for almost 2 months with no problems, I thought I was safe from ROM-related issues.....
I've now tried a couple different versions of Odin and they all fail, though 1.85 gives me more info (much like you saw).
Have you tried removing sim card and sd card from the phone before going into download mode and plugging to computer? I did this when I almost bricked my phone and I was able to flash factory firmware with Odin 3.07. From now on, I'm staying away from any Nightly build...
Nico3d3 said:
Have you tried removing sim card and sd card from the phone before going into download mode and plugging to computer? I did this when I almost bricked my phone and I was able to flash factory firmware with Odin 3.07. From now on, I'm staying away from any Nightly build...
Click to expand...
Click to collapse
Yep, I tried pulling the SIM and SD card. No change in behavior either with or without.
If you are not running a stock 4.3 bootloader, could try using Odin to flash a stock ROM from sammobile.com. If you have the 4.3 bootloader, this could be causing the failed flash. What is the screen info when your phone is on download mode?
Have you tried using Philz Touch to flash?
audit13 said:
If you are not running a stock 4.3 bootloader, could try using Odin to flash a stock ROM from sammobile.com. If you have the 4.3 bootloader, this could be causing the failed flash. What is the screen info when your phone is on download mode?
Have you tried using Philz Touch to flash?
Click to expand...
Click to collapse
Download screen is currently showing:
ODIN MODE
PRODUCT NAME: SGH-I747
CUSTOM BINARY DOWNLOAD: Yes (1 counts)
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
QUALCOMM SECUREBOOT: ENABLE
Warranty Bit: 1
BOOTLOADER AP SWREV: 2
I've tried to get Philz on the phone and that fails, as did trying to flash stock from sammobile. I'm getting a write failure in Odin.
Also just tried to install Philz from within TWRP.
This goes through and says "Successful", but then ends with:
Updating partition details
E: Unable to mount '/cache'
Selecting Wipe Cache/Dalvik results in:
Failed
Formatting Cache using make_ext4fs function.
E:Unable to mount 'cache'
Updating partition details
E: Unable to mount 'cache'
Use Odin to install Philz rather than twrp.
audit13 said:
Use Odin to install Philz rather than twrp.
Click to expand...
Click to collapse
Attempting in Odin gets me:
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection
<ID:0/005> Initialization..
<ID:/005> Gt PIT for mapping..
<ID:/005> Firmware update start..
<ID:0/005> recovery.img
<ID:0/005> Complete (Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1).
Grr....
Try flashing Philz for the d2att instead and see what happens. I have used the d2att and d2lte version on my Canadian Bell i747m.