[Q] Potential self-brick of my GT-N7000 Galaxy Note - Galaxy Note GT-N7000 Q&A, Help & Troubleshooting

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?

Related

Sprint SGT - E:Can't mount /dev/block/mmcblk0p1

Hi there Galaxy Tab community!
I'm having trouble fixing a Sprint Galaxy Tab (SPH-P100, CDMA).
I have tried a lot of different solutions and none of them are working for me.
Maybe someone can point out what the issue with my SGT is.
Current status: will get stuck at the "glowing" Samsung Logo (have let it sit for 15-20 minutes after reflashes but still stays there)
I don't really know how to explain this issue so I'm hoping one of you kind members can explain this to me. In Android system recovery <3e> mode before I did any flashing I get this error notice:
# MANUAL MODE #
E:Can't mount /dev/block/mmcblk0p1
(no such file or directory)
E:Can't mount CACHE:log/recovery.log
E:Can't open CACHE:log/recovery.log
E:Can't mount /dev/block/mmcblk0p1
(no such file or directory)
Is E: the SD card?
I do not have an SD card put in. And when I do, the above error message still appears. There is no SD card mounting error notice. And attempting to do an SD card update.zip does attempt successfully.
Now after trying to ODIN flash back to stock firmware (EA24, DJ30, stock with no modem) they all flash successfully, but all of them still get stuck at glowing samsung logo. And I still get the above mounting error message in recovery.
I did not tick "re-partition" yet, would this make a difference? (I tried searching for what it does but couldn't find any explanation)
Would flashing with Heimdall be any different than ODIN?
And the other solution I read was to reformat the internal SD to rfs format using roto JME (but I think that's only for GSM support?)
ANy help/suggestions would be appreciated!
UPDATE!!!: FIXED!!
Followed this step by step carefully and exactly from step 1 - 7: posted by emieczko (THANK YOU!!!!)
http://forum.xda-developers.com/showpost.php?p=13113921&postcount=21
so now I have to figure out if I still get the above error about E:.. but im scared if its really fixed for good. I will keep this updated! I love this forum!
UPDATE 2: shoot.. spoke too soon haha, tried to do a reflash of EA24 through heimdall and now in original situation. Only attempted another flash because each time i shutdown and restarted it would get stuck, until i would go into recovery and do a factory wipe/ clear cache, which would allow it to then boot to android.
UPDATE3: humm interesting, the OP http://forum.xda-developers.com/showpost.php?p=11650984&postcount=1 actually worked and booted right after a successful flash of the no_modem stock firmware using ODIN and the pit file supplied. and the crazy part is, it still had my gmail account info saved even after i had 'factory reset' a few times when it wouldnt boot up correctly.
UPDATE 4: Okay managed to update from stock no modem (tab_sprint_noModem_20101226) using odin 1.3, then ODIN the EA24 (Sprint Galaxy Tab EA24 Flasher) successfully with first boot attempt! Then since this was more of an official flash, EB25 was downloaded and installed with first boot success! Then the next update before Gingerbread, and then gingerbread OTA was installed successfully with first boot success!!! So now under gingerbread rom everything seems to be working smoothly. no problems with the market, wifi issues seem to be fixed.. only last real thing to make it an officially fixed tab is rebooting and seeing if it boots okay and booting into recovery and seeing if the E: errors still occur.. both which I don't want to face atm haha.\
UPDATE 5: So I was able to successfully reboot 3 times in a row. The method I used was the tablet plugged in with charger the entire time. I noticed upon removal of charger, apps would force close within minutes if i attempt to open even more apps system reboot and hang would occur. The only solution to get it up and working again is to plug the charger back in, then factory reset/ wipe cache and reboot. (FYI: first boot after a factory reset, the tab should vibrate on the 3rd-8th "glow" cycle of the samsung logo. if you see the logo loop.. then yea its boot loop haha). Attemping to boot the tab up without charger plugged in, causes a boot logo hang.. I'm starting to suspect defective tablet :-\
UPDATE 6: Looks like this tablet functions 100% normal when plugged in via USB to PC or Charger. Booting into recovery does not show any failed mounts (reboot into recovery 3 tmies) UNTIL i unplug it and try to reboot into recovery again. ACCIDENTALLY flashed the DK28 (epic 4g) modem! ahhhh after reading all the warnings .. fortunately I was able to ODIN the pit and EA24 rom successfully and the GPS still works. AT the moment I am letting the tablet incrementally update itself to gingerbread (while it is plugged in via usb to pc). And done.. now to do more unorthodox tests to see why its failing with no usb plugged
UPDATE 7: I think this is a hardware issue.. seems to only work normal when plugged in. doh.
So even after flashing the stock EA24 rar in Odin, it just sits at the boot logo and won't do anything? That is odd. In the stock recovery did you do a factory data wipe?
pvtjoker42 said:
So even after flashing the stock EA24 rar in Odin, it just sits at the boot logo and won't do anything? That is odd. In the stock recovery did you do a factory data wipe?
Click to expand...
Click to collapse
Correct! This is the ODIN log after a successful flash of the SPH-P100.EA24.SECURE.REV07-FULL_CL871413
<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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.bin
<ID:0/003> Sbl.bin
<ID:0/003> param.lfs
<ID:0/003> zImage
<ID:0/003> recovery.bin
<ID:0/003> factoryfs.rfs
<ID:0/003> cache.rfs
<ID:0/003> dbdata.rfs
<ID:0/003> modem.bin
<ID:0/003> Removed!!
<ID:0/003> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/004> Added!!
<ID:0/004> Removed!!
Does anybody the average time ti takes to stay on that glowing Samsung Logo after a factory reset/ flash?
edit: nevermind, its less than 10 glowing logo cycles.
Here is the best way to sovle the problem.
if your TAB stuck in the logo ,and recovery got the tips, the IC sandisk "sdin5d2-2g" on the mainboard is broblem .I let some body who is good at repairing mobile phone to use tools to take the IC out ,and throw it into bin. I go back home unpack the zImage kernel ,modify the file in it ,such as fota.rc,recovery.fstab , (in Ubuntu , grep mmblk * */* */*/* ) ,let the mmcblk0p1 for sdcard ,mmcblk0p3 for cache mmcblk0p4 for data , and repack the kernel . Then I repartition my kingston 8g C6 TF card to four primary partition,5.4 for the 1st ,180m for the 2nd ,190m for the 3th ,2G for the 4th. At last I use heimdall to reflash zhe new zImage into kernel and recovery .When the tab reboot ,let it into recovery and wipe the data and cache and reboot . After 10mins ,you will get the first setting for the tab.
here is my new zImage: /115。com/file/dnm9n22m#
the links: /www。diypda。com/forum.php?mod=viewthread&tid=336743
I am a new man in XDA, I can't post the outside link ,so please use " . " to replace " 。 " and add "http:/ " the links ,sorry !
My email is [email protected], you are welcome !

Help! Support request - GT-i9305

Hi All,
I've managed to break my phone and need some helps.
Background info:
I own a Samsung GT-i9305 which I purchased from Optus (Australian carrier) a few months ago. When I first got the phone I installed CF root, TWRP and a custom rom (illusion_i9305-2.6.stable-OFFICIAL). Everything was fine and dandy until a few days ago when the phone started randomly restarting every time I pressed the power/lock button. After researching the issue I found that the power button was simply stuck and only needed a light tap to fix the issue, (This is were Sh!t hit the fan) However because of my ignorance and lack of knowledge I automatically assumed it was the custom rom, so I began flashing everything until my phone was no longer functional. (My flash counter is 14 currently)
Issue: My phone no longer boots a ROM and have had some weird errors within TWRP that don't make sense to me (hoping someone with more knowledge than I can assist)
Errors:
Unable to mount system (when installing a rom, please note: this has only occurred twice and seems to be intermittent)
Work done to device: (using Odin v03.7)
Multiple flashes of CF root
Multiple flashes of TWRP & CWM
Multiple attempts at installing custom .zip Roms within TWRP (I prefer TWRP over CWM)
- You get the basic idea, frantically flashing everything to try and fix the issue. -
Current issue:
I've currently got TWRP 2.6.3.0 on the phone but when I install a custom ROM it doesn't boot, only stays on the loading screen.
NOTE: I performed a full wipe on the phone and a full wipe after installing the custom ROM but it still wont boot
ROM: illusion_i9305-2.6.stable-OFFICIAL (only because it worked)
I've tried to include all the information I can however if you need more info just ask. I'm looking for a way to either reset my phone to the stock ROM (with a download link, as the ones i've tried are horribly slow) or an alternative way to fix my issue. Clear instructions are much appreciated.
EDIT:
- I have downloaded "I9305XXBMA5_I9305OPSBMA1_OPS.zip" and extracted the .tar.md5
- I received the below error when trying to flash the stock Optus image to the device
ODIN LOG:
<OSM> Please wait..
<OSM> I9305XXBMA5_I9305OPSBMA1_I9305XXBLL5_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> system.img
<ID:0/006> NAND Write Start!!
<ID:0/006> __Xmit Write fail
<ID:0/006> XmitData Fail..
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
RESOLVED!
Solution:
Flash Stock ROM I9305XXALI5_I9305OPSALI5_OPS (Optus Aus ROM 4.1.2)
Changing to an earlier firmware version resolved all issues. This thread can now be closed.

[Q] SIII LTE I9305 - Problems after OTA Update to 4.4.4 and factory reset

Hi there,
i'm having a weired problem with my Samsung Galaxy S III LTE (GT-I9305 - DBT), after
updating from official 4.3 (DBT - PDA:MKC / Phone: MK1 / CSC: MJ4) to a yesterday via OTA provided update to Kitkat 4.4.4
(recovery says KTU84P.I9305XXUFNI3)
The device has only seen official firmware and has never been rooted or tried to be manually manipulated.
I did these steps.
1.) OTA update was available, downloaded via WLAN on the device (took a while), then the update was initiated
on the device directly (no kies). Update went ok so far, after the first reboot the "app optimisation process" began
, at this point there were some pop ups saying some of the google "play" apps were stopped (Play movies, play books, play kiosk.
also a so called "setup assistent").
The device was "normally" usable at this point, but the above mentioned apps have been left unusable, also some "apps stopped"
pop ups show up after every reboot on the device.
2.) So i decided to boot up in recovery mode to do an "wipe cache partition" - but this didn't help. The error messages concerning
some of the system apps were still there.
3.) Although i knew, that i had to some re-setup after it, i thought "ok, let's give a factory reset a chance" (a wipe dalvik cache was
no option, because of the original bootloader and an unrooted device). After the factory reset, the device came up with the samsung
setup assistant, which seems ok to me, BUT at this point the device gets stucked in the first setups steps because there were so many
"apps stopped" messages concerning critical system apps (in my opinion). Here a just a few: "samsung account", "google play services",
"youtube", "google play music", "setup-assistant". The devices is now stucked at the point to accept the eula, no chance to get any step
further.
After this and the informations i found online, i would call this device a "soft brick"?
My idea was to reinstall the original 4.3 firmware to reanimate the device via odin (tried 3.09 and 1.85). I got the official one file package
from the previously android version (I9305XXUEMKC_I9305DBTEMJ4_I9305XXUEMK1_HOME.tar). But there is no way to flash this via
odin. The process always aborts with an write failed message. Only selected options are "Auto Reboot" and "F Reset Time", the image
ist selected via the AP-Button, "ID-COM" went blue after connecting device).
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9305XXUEMKC_I9305DBTEMJ4_I9305XXUEMK1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/011> Added!!
<ID:0/011> Odin v.3 engine (ID:11)..
<ID:0/011> File analysis..
<ID:0/011> SetupConnection..
<ID:0/011> Initialzation..
<ID:0/011> Get PIT for mapping..
<ID:0/011> Firmware update start..
<ID:0/011> SingleDownload.
<ID:0/011> sboot.bin
<ID:0/011> NAND Write Start!!
<ID:0/011> FAIL!
<ID:0/011>
<ID:0/011> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Could it be, that flashing the downgrade to official 4.3 is impossible because of a newer installed bootloader on OTA update process?
On the device there ist follwing message at download mode after failing the flash process:
ODIN MODE
PRODUCT NAME: GT-I9305
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
Secure Download: Enabled
KNOW WARRANTY VOID: 0
AP SWREV: A3
SW REV. CHECK FAIL, DEVICE:3, BINARY:2
Has anyone an idea how to bring this device back to life? Unfortunaly there are no update packages for 4.4.4 DBT at this moment, to give it a try with the latest
android version. Firmware restore and initialisation via kies is also not availabe because it says the device is not supported.
Hi After ota update no xamera Icon on the lockscreen can you help me?
Sent from my GT-I9305 using XDA Free mobile app
I've got a problem after updating to kit kat 4.4.4. Fact is that before updating I used "Screen Mirroring" with my LG SmartTV. That feature was always working perfect with 4.3. But now it's impossible to connect to my TV. TV and phone say "connecting" but after few seconds TV shows a popup saying "Device disconnected" and then my phone brings a "Error connecting Screen Mirroring". And my question is "WHYYYY?!?!" It's assumed that an update gives a more useful phone and instead of that I got the opposite. Incredible... can anyone help me, please? I would be very very thankful!
EDIT: Now, when I try to connect both devices, my phone brings a popup saying "Can not connect because of a hardware problem". WTF?
reflash the ROM with the Android 4.4.4 image now avaible on SamMobile
I have had the same problem
Joker_i9305 said:
Hi there,
i'm having a weired problem with my Samsung Galaxy S III LTE (GT-I9305 - DBT), after
updating from official 4.3 (DBT - PDA:MKC / Phone: MK1 / CSC: MJ4) to a yesterday via OTA provided update to Kitkat 4.4.4
(recovery says KTU84P.I9305XXUFNI3)
The device has only seen official firmware and has never been rooted or tried to be manually manipulated.
I did these steps.
1.) OTA update was available, downloaded via WLAN on the device (took a while), then the update was initiated
on the device directly (no kies). Update went ok so far, after the first reboot the "app optimisation process" began
, at this point there were some pop ups saying some of the google "play" apps were stopped (Play movies, play books, play kiosk.
also a so called "setup assistent").
The device was "normally" usable at this point, but the above mentioned apps have been left unusable, also some "apps stopped"
pop ups show up after every reboot on the device.
2.) So i decided to boot up in recovery mode to do an "wipe cache partition" - but this didn't help. The error messages concerning
some of the system apps were still there.
3.) Although i knew, that i had to some re-setup after it, i thought "ok, let's give a factory reset a chance" (a wipe dalvik cache was
no option, because of the original bootloader and an unrooted device). After the factory reset, the device came up with the samsung
setup assistant, which seems ok to me, BUT at this point the device gets stucked in the first setups steps because there were so many
"apps stopped" messages concerning critical system apps (in my opinion). Here a just a few: "samsung account", "google play services",
"youtube", "google play music", "setup-assistant". The devices is now stucked at the point to accept the eula, no chance to get any step
further.
After this and the informations i found online, i would call this device a "soft brick"?
My idea was to reinstall the original 4.3 firmware to reanimate the device via odin (tried 3.09 and 1.85). I got the official one file package
from the previously android version (I9305XXUEMKC_I9305DBTEMJ4_I9305XXUEMK1_HOME.tar). But there is no way to flash this via
odin. The process always aborts with an write failed message. Only selected options are "Auto Reboot" and "F Reset Time", the image
ist selected via the AP-Button, "ID-COM" went blue after connecting device).
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9305XXUEMKC_I9305DBTEMJ4_I9305XXUEMK1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/011> Added!!
<ID:0/011> Odin v.3 engine (ID:11)..
<ID:0/011> File analysis..
<ID:0/011> SetupConnection..
<ID:0/011> Initialzation..
<ID:0/011> Get PIT for mapping..
<ID:0/011> Firmware update start..
<ID:0/011> SingleDownload.
<ID:0/011> sboot.bin
<ID:0/011> NAND Write Start!!
<ID:0/011> FAIL!
<ID:0/011>
<ID:0/011> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Could it be, that flashing the downgrade to official 4.3 is impossible because of a newer installed bootloader on OTA update process?
On the device there ist follwing message at download mode after failing the flash process:
ODIN MODE
PRODUCT NAME: GT-I9305
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
Secure Download: Enabled
KNOW WARRANTY VOID: 0
AP SWREV: A3
SW REV. CHECK FAIL, DEVICE:3, BINARY:2
Has anyone an idea how to bring this device back to life? Unfortunaly there are no update packages for 4.4.4 DBT at this moment, to give it a try with the latest
android version. Firmware restore and initialisation via kies is also not availabe because it says the device is not supported.
Click to expand...
Click to collapse
Joker_i9305 said:
Hi there,
i'm having a weired problem with my Samsung Galaxy S III LTE (GT-I9305 - DBT), after
updating from official 4.3 (DBT - PDA:MKC / Phone: MK1 / CSC: MJ4) to a yesterday via OTA provided update to Kitkat 4.4.4
(recovery says KTU84P.I9305XXUFNI3)
The device has only seen official firmware and has never been rooted or tried to be manually manipulated.
I did these steps.
1.) OTA update was available, downloaded via WLAN on the device (took a while), then the update was initiated
on the device directly (no kies). Update went ok so far, after the first reboot the "app optimisation process" began
, at this point there were some pop ups saying some of the google "play" apps were stopped (Play movies, play books, play kiosk.
also a so called "setup assistent").
The device was "normally" usable at this point, but the above mentioned apps have been left unusable, also some "apps stopped"
pop ups show up after every reboot on the device.
2.) So i decided to boot up in recovery mode to do an "wipe cache partition" - but this didn't help. The error messages concerning
some of the system apps were still there.
3.) Although i knew, that i had to some re-setup after it, i thought "ok, let's give a factory reset a chance" (a wipe dalvik cache was
no option, because of the original bootloader and an unrooted device). After the factory reset, the device came up with the samsung
setup assistant, which seems ok to me, BUT at this point the device gets stucked in the first setups steps because there were so many
"apps stopped" messages concerning critical system apps (in my opinion). Here a just a few: "samsung account", "google play services",
"youtube", "google play music", "setup-assistant". The devices is now stucked at the point to accept the eula, no chance to get any step
further.
After this and the informations i found online, i would call this device a "soft brick"?
My idea was to reinstall the original 4.3 firmware to reanimate the device via odin (tried 3.09 and 1.85). I got the official one file package
from the previously android version (I9305XXUEMKC_I9305DBTEMJ4_I9305XXUEMK1_HOME.tar). But there is no way to flash this via
odin. The process always aborts with an write failed message. Only selected options are "Auto Reboot" and "F Reset Time", the image
ist selected via the AP-Button, "ID-COM" went blue after connecting device).
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9305XXUEMKC_I9305DBTEMJ4_I9305XXUEMK1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/011> Added!!
<ID:0/011> Odin v.3 engine (ID:11)..
<ID:0/011> File analysis..
<ID:0/011> SetupConnection..
<ID:0/011> Initialzation..
<ID:0/011> Get PIT for mapping..
<ID:0/011> Firmware update start..
<ID:0/011> SingleDownload.
<ID:0/011> sboot.bin
<ID:0/011> NAND Write Start!!
<ID:0/011> FAIL!
<ID:0/011>
<ID:0/011> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Could it be, that flashing the downgrade to official 4.3 is impossible because of a newer installed bootloader on OTA update process?
On the device there ist follwing message at download mode after failing the flash process:
ODIN MODE
PRODUCT NAME: GT-I9305
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
Secure Download: Enabled
KNOW WARRANTY VOID: 0
AP SWREV: A3
SW REV. CHECK FAIL, DEVICE:3, BINARY:2
Has anyone an idea how to bring this device back to life? Unfortunaly there are no update packages for 4.4.4 DBT at this moment, to give it a try with the latest
android version. Firmware restore and initialisation via kies is also not availabe because it says the device is not supported.
Click to expand...
Click to collapse
The firmware package you are trying to flash through ODIN is 4.3. Once updated to 4.4.4 you can not downgrade to 4.3. Grab 4.4.4 from here : http://www.sammobile.com/firmwares/3/?download=35546 and flash it thorugh Odin just like the same way
In the meantime just got my device back repaired from Samsung customer care center. Device is working again without failures under 4.4.4.
The mainboard was replaced, i thought this was the best way for me, as the device was still in warranty period. I can't estimate if it really was
a hardware problem or not - simply glad to have a working device back.
Although your remarks concerning impossible "downgrade" to 4.3 after upgrading to 4.4.4 once seem to be plausible for me causing the flashing
failures with odin.
As LightningJackMcQeen mentioned, the way to flash 4.4.4 via odin was the solution for his problems.
KennyMRos said:
I've got a problem after updating to kit kat 4.4.4. Fact is that before updating I used "Screen Mirroring" with my LG SmartTV. That feature was always working perfect with 4.3. But now it's impossible to connect to my TV. TV and phone say "connecting" but after few seconds TV shows a popup saying "Device disconnected" and then my phone brings a "Error connecting Screen Mirroring". And my question is "WHYYYY?!?!" It's assumed that an update gives a more useful phone and instead of that I got the opposite. Incredible... can anyone help me, please? I would be very very thankful!
EDIT: Now, when I try to connect both devices, my phone brings a popup saying "Can not connect because of a hardware problem". WTF?
Click to expand...
Click to collapse
Give it a factory reset and try again.
i'm having exactly the same problems, but the difference is that my warranty is void, sending it back to samsung is therefore no option, i also tried flashing the XXUEFNI3 file but didn't work either, any ideas?
this problem is due to the fact that if you go up you can't go down.
for example: if you got the 4.3 update from 4.2.2(or 4.1.2) you couldn't go back(knox issues). if you have flashed at a point in time 4.4 on your phone you can't flash 4.3...you can only go up. so solve the problem by flashing 4.4.4.
more and more countries release 4.4.4 - check it here: http://live.samsung-updates.com/index.php?device=GT-I9305
i'm not from germany(i'm from other country in europe) but i got their firmware and words like a charm. it's incredible smooth(99.99% like a custom ROM) an no bugs what so ever.

Errors with ATT S5 Active

I recently screwed up my S5 active and am desperate for help.
I only ever really occasionally screw with the OS, and I did a poor job of documenting what I did with this phone, so I will do my best to recollect exactly the state.
The phone is an AT&T Samsung Galaxy S5 active, model G870A
The recovery was some kind of robot icon that would show for maybe ~10 seconds at the start of boot (not a regular android, more square). I've tried searching for it to, as yet, no avail.
I'm fairly certain that the image I put on the device was KoolKit_S5_Active_V1.1.0.
I cannot recall if I used safestrap, towelroot, twrp, or some combination of these in order to get the above on the device. I have copies of each sitting in a folder I created for the phone.
The other day, SuperSU said it needed the binary updated. Me, being dumb, wanting the notification to go away, decided to appease it. It asked if I wanted to do so using recovery. I figured this would be easier, so I clicked "yes". And then my life got a lot more stressful.
When the phone boots now, it goes into ODIN mode and displays the message "android could not do normal boot. ODIN MODE".
I cannot get it to any other screen. Recovery, download mode, whatever. (I'm pretty sure this is download mode, but I cannot initiate any mode, it just goes into this).
I've been poking around on these forums. The first suggestion I thought might work was to use ODIN to (re?) flash towelroot. Or TWRP. I forget which one I tried, but it wound up resulting in a failure in ODIN, and a message on the screen stating something along the lines of "sys rev check fail no version".
I am very confused about what I need to be flashing using ODIN, but I have managed to cobble together that it has to be through ODIN.
I don't necessarily need links, I can find those, and I may already have the files. I'd really like to know which files it is that I need.
Do I need a firmware? What is the file format for that? tar.md5? etc.
Ideally I'd just like to get back to a regular run mode where my worst problem was a wonky USB port. I would deeply appreciate it if anyone could get me in that direction.
Thank you
It's working.
I plugged it in, tried to flash a PIT file. That failed. Apparently one does not flash those alone.
The screen said something like "check failed : PIT" ...
I went here:
http://forum.xda-developers.com/showthread.php?t=2799754
Followed the instructions. Got a failure. (This was, stupidly and fortunately, without restarting phone after pit failure).
Phone rebooted like nothing was ever wrong.
ODIN log:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G870AUCU1ANE4_G870AATT1ANE4_G870AUCU1ANE4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/005> Added!!
<ID:0/005> Removed!!
<ID:0/005> Added!!
Click to expand...
Click to collapse
P.S.: Previously unidentified robot was safestrap:
http://img.wonderhowto.com/img/96/6...hwiz-launcher-your-samsung-galaxy-s5.w654.jpg
Im glad you could fix it.
I also have a problem with a AT&T S5 active, the phone has horrible screen lag (even the booting screen is slow)
I tried doing a factory reset and also doing a downgrade to kit-kat using Odin, but the problem persists

Please help - Sorry if this is the place

Hi folks,
I friend of mine have this phone that is stuck in Odin mode. The problem is that none of the "press and hold keys" commands work and the phone just reboots into Odin every time. She has "tons" of Pictures of her first born Child on the device, without any cloud backup! :crying:
Any suggestions what to try next?
What i have done so far:
Trying all the "press and hold keys"
Letting the battery drain out and the hook up the Power to it... When connecting Power the screen turns White for 15-20 minutes and then if i reboot it, it goes back to Odin/download mode...
Is it possible that opening the phone and removing the battery could work?
Jeppe_77 said:
Hi folks,
I friend of mine have this phone that is stuck in Odin mode. The problem is that none of the "press and hold keys" commands work and the phone just reboots into Odin every time. She has "tons" of Pictures of her first born Child on the device, without any cloud backup! :crying:
Any suggestions what to try next?
What i have done so far:
Trying all the "press and hold keys"
Letting the battery drain out and the hook up the Power to it... When connecting Power the screen turns White for 15-20 minutes and then if i reboot it, it goes back to Odin/download mode...
Is it possible that opening the phone and removing the battery could work?
Click to expand...
Click to collapse
I am no expert, just going to suggest what I would try, hopefully someone may know what to do exactly.
You could try downloading stock filmware from Sammobile or updato (making sure to at least flash the same filmware build or higher, or Odin won't flash it) if you use the "home csc" csc file, it should not wipe the data on the phone, and what I hope may fix the phone not booting.
First of all you should have mentioned the model no. Second, you can try flashing the stock firmware from sammobile. Now, the tricky part is, if prior to this soft brick the phone was on a custom rom or had been rooted, then flashing the firmware alone won't bring the device back to life, a factory reset will be needed after flashing stock firmware, which doesnt seems like a favorable option considering that the data on device is important. There can be other ways to fix this without losing the data but for that illl need to know the device details.
Oh and btw, opening the device and messing with the battery won't help at all. Don't do that.
Sent from my SM-N950F using Tapatalk
Get a pit file and flash it though oden may work or not.......
yashthemw said:
First of all you should have mentioned the model no. Second, you can try flashing the stock firmware from sammobile. Now, the tricky part is, if prior to this soft brick the phone was on a custom rom or had been rooted, then flashing the firmware alone won't bring the device back to life, a factory reset will be needed after flashing stock firmware, which doesnt seems like a favorable option considering that the data on device is important. There can be other ways to fix this without losing the data but for that illl need to know the device details.
Oh and btw, opening the device and messing with the battery won't help at all. Don't do that.
Sent from my SM-N950F using Tapatalk
Click to expand...
Click to collapse
Its an Galaxy Note 8 (SM-N950F)
The only thing i can see in the display is
https:// imgshare.io/image/odin-2.U7KCu
We dont know what firmware was beeing used Before this, it´s not custom or rooted tho. I assume its the latest official tho
I grabbed the latest from Sammobile, N950FXXU7DSJ1_N950FCKH7DSJ1_HTS
I could try the above suggestions but what about trying to flash the BL? Could it not be the BL that is cuppupt somehow?
I did try and flash the BL now but Odin software says:
<ID:0/004> Odin engine v(ID:3.1301)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 7 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004>
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
So it seems the partitions are gone, @stinka318. Next, where do i find PIT-files?
Found PIT file but it failed.
Also tried CSC flash but it fails (looks like Odin might not cennect to the device (ID:COM 0: [COM4])
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1301)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 179 M
<ID:0/004> SetupConnection..
<ID:0/004> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
Driver related? i have the Samsung USB drivers installed….
https://zfirmware.com/download-samsung-galaxy-note-8-pit-file/
Seems like it's a kernel problem, or maybe the phone IMEI reported stolen?
Have you tried installing custom binaries? TWRP maybe?
Or messing with OEM unlock found in Developer Options?
Most of the for solving such problem, you have to flash the exact same firmware found on phone before the problem.
Try rooting using odin and then twrp and thenflashing a custom firmware..... That could help..... Just a thought.... Wipe everything except internal storage
https://mega.nz/#!Lk8RiKQR!FiH50HLQp1aijVkRARSPtBN6M6wFphShHsm7i6u23lw
Try flashing this via odin through AP.
Sent from my SM-N950F using Tapatalk

Categories

Resources