Develop Bugs

N7105 - Only get into Dowload-mode after Update

Dear Community,
I stucked with my Samsung N7105 since 2 days , so im requesting for your power & knowledge
After Updating the phone i dont get any response, i only have access to the download-mode, which output is:
Code:
ODIN MODE
PRODUCT NAME:
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
I installed the samsung usb-driver 1.5.43 and tried Odin 3.07 / 3.09 to get CWM (CF-Autoroot) on it. Device was detected, but odin is requesting for a PIT-file, so i gave him this one
http://forum.xda-developers.com/showthread.php?t=2137008
also tried the one from Dr. Ketan (which seems to be the same)
http://d-h.st/hwQ
output from odin (tried different versions & usb-ports):
Code:
<ID:0/015> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-t0lte-t0ltexx-gtn7105.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/015> Odin v.3 engine (ID:15)..
<ID:0/015> File analysis..
<ID:0/015> SetupConnection..
<ID:0/015> Initialzation..
<ID:0/015> Set PIT file..
<ID:0/015> DO NOT TURN OFF TARGET!!
<ID:0/015> FAIL!
<ID:0/015>
<ID:0/015> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
So i tried Heimdall, from the official source http://glassechidna.com.au/heimdall/, because of the better debug-output in command-line.
First step was, getting/printing the PIT...failed - It seems Heimdall also getting no response (connection-problem?). Im abit unsure with the usb-drivers. As described I replaced the samsung driver with zadig.
But in Zadig i have two options , which seems to be related to the samsung-drivers. "CDC Abstract Control Model" & "Gadget Serial" --> I replaced the 1st one with the libusb-win32(v1.2.6.0) Drivers.
There are also libusbk(v3.0.5.16) & WinUSB(v6.1.7600.16385) for choice, but as i understand Heimdall is using the libusb-win32-Libary(?)
Trying to get/print the PIT with Heimdall I get the following:
G:\samsung\heimdall-suite-1.4.0-win32>heimdall print-pit --no-reboot --usb-log-level warning
Heimdall v1.4.0
Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
libusbx: warning [winusbx_claim_interface] auto-claimed interface 0 (required to claim 1 with WinUSB)
Setting up interface...
Initialising protocol...
libusbx: warning [winusbx_submit_control_transfer] ControlTransfer failed: [87] Falscher Parameter.
libusbx: warning [winusbx_submit_control_transfer] ControlTransfer failed: [87] Falscher Parameter.
libusbx: warning [winusbx_submit_control_transfer] ControlTransfer failed: [87] Falscher Parameter.
libusbx: warning [winusbx_submit_control_transfer] ControlTransfer failed: [87] Falscher Parameter.
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
ERROR: Failed to receive PIT file size!
ERROR: Failed to download PIT file!
Ending session...
ERROR: Failed to send end session packet!
Releasing device interface...
libusbx: warning [libusb_exit] some libusb_devices were leaked
Click to expand...
Click to collapse
Is he claiming the wrong Interface? Steady I get a little frustrated, have someone any idea or are there other methods to get informations from the phone...flashing a a new recovery on it?

U need to install rescue firmware 4.1 which was uploaded by steff in dn3 latest post
I created the thread on how to recover bricked note 2
You can read in first or second page
I am travelling so at the moment I can't upload the recscu firmware but u can request steff195 to upload this here
It has full rom image plus pit file u can fix your phone via 3.07 odin
Then u can flash any stock 4.4.2 to bring it back to bug free life
And then rooting and etc
Sent from my GT-N7100 using XDA Premium 4 mobile app

[Q] Soft Brick Note 2 II sgh-i317m philz touch help needed

OK, being a Canadian I'll equate this to getting my car stuck in the snow, I just need a little push hopefully...
Ever since updating to 4.4.2 OTA (or possibly since rooting) my Note 2 would randomly reboot once or sometimes twice a day while running the stock ROM from Rogers (similar to the ATT Rom). Sidenote: I attribute the problem to software but my gut tells me I might also have a hardware issue. I tried doing a restore once on the stock and the phone ran a little faster but was still plagued with the random rebooting issue.
I decided that since my contract was up in a couple of months I would ditch the stock rom and try a custom rom maybe my reboot issue would get better on a custom ROM. I thought CM11 would be a safe bet. So, I added Philz Touch recovery via Odin 3.07 (see versions below) I did a full back up and flashed the new rom using Philz Touch recovery.
CM11 ran fine for about three or four days BUT the phone still did one or two random reboots!
One night it had just finished receiving a text and about a minute later did a reboot and POOF! I was at the Samsung Logon screen soft bricked.
I can boot into download mode (power+down volume+home) and I can boot into CMW recovery (power + up volume + home) EXCEPT not into Philz Touch anymore, it boots into "CMW-based Recovery v6.0.5.0" What happened to Philz Touch I am wondering?
(I tried using Kies but Kies won't recognize the phone connection so I have uninstalled Kies)
CWM is throwing out a bunch of errors on start too:
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
CMW seems to throw errors like this whenever I try to use any of the options. I can't install my backup zip or wipe or do much of anything.
When I run Odin the connection on the com port is recognized but when I try to load a stock ROM or any other ROM I get a write FAIL error. I've tried different versions of Odin and different cables, doesn't seem to get me past this write error.
What's my next step? Thanks for any advice or help in advance.
Galaxy Note ii (sgh-i317m Rogers Canada)
Cyanogenmod (cm-11-20140618-NIGHTLY-t0lte)
CMW 6.0.5.0
Philz Touch 6.07.09
Odin 3.07, 3.09 various versions.
Windows 8

mkochsch said:
OK, being a Canadian I'll equate this to getting my car stuck in the snow, I just need a little push hopefully...
Ever since updating to 4.4.2 OTA (or possibly since rooting) my Note 2 would randomly reboot once or sometimes twice a day while running the stock ROM from Rogers (similar to the ATT Rom). Sidenote: I attribute the problem to software but my gut tells me I might also have a hardware issue. I tried doing a restore once on the stock and the phone ran a little faster but was still plagued with the random rebooting issue.
I decided that since my contract was up in a couple of months I would ditch the stock rom and try a custom rom maybe my reboot issue would get better on a custom ROM. I thought CM11 would be a safe bet. So, I added Philz Touch recovery via Odin 3.07 (see versions below) I did a full back up and flashed the new rom using Philz Touch recovery.
CM11 ran fine for about three or four days BUT the phone still did one or two random reboots!
One night it had just finished receiving a text and about a minute later did a reboot and POOF! I was at the Samsung Logon screen soft bricked.
I can boot into download mode (power+down volume+home) and I can boot into CMW recovery (power + up volume + home) EXCEPT not into Philz Touch anymore, it boots into "CMW-based Recovery v6.0.5.0" What happened to Philz Touch I am wondering?
(I tried using Kies but Kies won't recognize the phone connection so I have uninstalled Kies)
CWM is throwing out a bunch of errors on start too:
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
CMW seems to throw errors like this whenever I try to use any of the options. I can't install my backup zip or wipe or do much of anything.
When I run Odin the connection on the com port is recognized but when I try to load a stock ROM or any other ROM I get a write FAIL error. I've tried different versions of Odin and different cables, doesn't seem to get me past this write error.
What's my next step? Thanks for any advice or help in advance.
Galaxy Note ii (sgh-i317m Rogers Canada)
Cyanogenmod (cm-11-20140618-NIGHTLY-t0lte)
CMW 6.0.5.0
Philz Touch 6.07.09
Odin 3.07, 3.09 various versions.
Windows 8
Click to expand...
Click to collapse
Try downloading philz again then flash it via odin then wipe everything but the modem and the ex sd then reboot the recovery and when it says to apply root hit no then the phone will reboot into recovery then flash the rom again and let me know what happens

First things first. Thank you for having a look at this. I'm really trying not to do a PIT flash on this one.
This is what happens when I try to flash Philz Touch (6.07.9 t0lteatt) using Odin 3.09. The progress bar goes about 3/4 of the way across and then in big red letters "fail" (see log below). This is the same version of Philz Touch I was running.
How do I "not wipe" the modem from CWM recovery? Do you mean go into "mounts and storage" and start formatting? BTW none of these directories will mount at the moment. I get: 'Error mounting /system' etc.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> philz_touch_6.07.9-t0lteatt.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
p.s. Is there any way to use adb.exe to diagnose exactly what the issue might be?

You need to update your recovery. I use TWRP for all roms.
System and data wiping won't remove a modem.

rangercaptain said:
You need to update your recovery. I use TWRP for all roms.
System and data wiping won't remove a modem.
Click to expand...
Click to collapse
I initially did my Nandroid backup on my external SD card. TWRP probably won't read a CWM backup.
When I try to restore my backup I get the following:
Checking MD5 sums...
All MD5 checksums verified
Erasing boot before restore...
Restoring boot image...
Restoring system...
E: format_volume: make_ext4fs failed on /dev/block/mmcblk0p13
Error while formatting /system

mkochsch said:
I initially did my Nandroid backup on my external SD card. TWRP probably won't read a CWM backup.
When I try to restore my backup I get the following:
Checking MD5 sums...
All MD5 checksums verified
Erasing boot before restore...
Restoring boot image...
Restoring system...
E: format_volume: make_ext4fs failed on /dev/block/mmcblk0p13
Error while formatting /system
Click to expand...
Click to collapse
What philz recovery did you download maybe Make sure you downloaded the right one for your phone I can't remember what one the i317m has to be

And did you move or rename your backup?

terpin32 said:
What philz recovery did you download maybe Make sure you downloaded the right one for your phone I can't remember what one the i317m has to be
Click to expand...
Click to collapse
Philz Touch 6.07.09

rangercaptain said:
And did you move or rename your backup?
Click to expand...
Click to collapse
Move or rename, no. Backed up to laptop.

mkochsch said:
Philz Touch 6.07.09
Click to expand...
Click to collapse
I know you had that one but make sure you got the right one for your model but I would flash a newer one over it in odin and that should fix your problem

terpin32 said:
I know you had that one but make sure you got the right one for your model but I would flash a newer one over it in odin and that should fix your problem
Click to expand...
Click to collapse
It just does the same as every other version of Philz Touch and everything else I try to flash.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> philz_touch_6.48.4-t0lteatt.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)

Is it possible that the built-in SD card is the problem?

mkochsch said:
It just does the same as every other version of Philz Touch and everything else I try to flash.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> philz_touch_6.48.4-t0lteatt.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Does the rom boot up?

No. It is soft bricked. I get the Samsung screen. I can boot into both download mode (Volume down) and CMW (volume up). However in download mode Odin fails (from versions 1.85-3.09). In CWM mode the aforementioned errors occur when I try to flash roms, restore NAND backups or mount directories.

I am getting almost the exact same issue. Mine kept randomly rebooting then one day it crashed and went to a bootloop. I have tried flashing different roms and recoveries however, it just sits on the Samsung note II splash screen.
I have had to go back to my captivate just to have a working phone... I have about given up.

Someone please help with rom flash issues

ok so far i unlocked bootloader so im a dev N910z
i flashed custom kernel: N910F-Stock_Kernel_XXU1COJ3_Root_Permissive_NTFS_PhilZ_v2.0
and i flashed TWRP: twrp-3.0.2-0-trltevzw.tar
after stock rom flash attempt via odin i get:
on odin:
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
on phone:
sw rev check fail: [aboot] fused 2 > binary 1
[1] emmc write fail: ABOOT
on adp side load:
cannot read file
I cant get the phone to flash any roms Via: twrp, download mode or odin....
please someone tell me what im doing wrong... i just want a debloated stock rom/or at least a stock rom (i used a debloater app and i guess i deleted something that prevents games from loading) i would like to via text if that is ok with whomever is willing to help... im matt my cell is 843 9901111 PLEASE HELP im a newb haha

Double check and make sure the bootloader is unlocked.
Sent from my SM-N910V using Tapatalk

Soft brick - cannot flash via recovery or Odin

Basically woke up with my phone as a brick... phone crashed when my alarm was supposed to go off (luckily I was already awake) and now hangs on the boot splash screen.
Device is an i747m, previously running S3Rx 3.0 (Android 4.3) with MK5 bootloader and modem. CWM 6.0.4.7 installed.
I am able to boot into both recovery and download mode.
However, in recovery mode, I get the errors:
Code:
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
Furthermore, if I try to factory reset, I get the error:
Code:
Formatting /data...
Error mounting /data!
While in recovery, I am not able to flash a new recovery or ROM. There are no errors when flashing, however, after rebooting nothing has changed. I'm assuming that's because the system cannot access the storage.
Through Odin, I can flash TWRP with no errors. However, once I try to boot into recovery, I am still on CWM 6.0.4.7.
Through Odin, I am unable to flash ROMs (trying to flash 4.3 MK5 stock rom). I am using Odin 3.07 on a W7 x64 computer with Samsung drivers installed and an official Samsung USB cable.
I receive the error:
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747MVLUEMK5_I747MOYCEMK5_I747MVLUEMK5_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
It appears that there is a problem with the internal memory since I can't read/write, but I am unsure if it is fixable.
I have come across this thread, but I am skeptical if it will work since it is for the Verizon S3.
I also came across this thread in my research, but I can't get cygwin to download >.> It seems promising, but I am unable to try it at the moment.
Any help or suggestions would be greatly appreciated. Please let me know if any additional information is required.

Have you tried flashing a 4.4.2 ROM?

audit13 said:
Have you tried flashing a 4.4.2 ROM?
Click to expand...
Click to collapse
Yes, I have tried flashing the 4.4.2 NE6 ROM using Odin with the same result (NAND write fails).
I have also tried flashing via Heimdall. No success there either. Heimdall is able to upload the file to my device (according to the progress bar), but then terminates with, ERROR: Failed to confirm end of file transfer sequence!
Also, the PIT file I extracted from my device via Heimdall does not match a "normal" i747m 16gb PIT found on the internet... I also cannot flash the 'normal' PIT onto my device (same error as above).

It's possible the internal memory chip is damaged which is not easy to repair. Simplest fix may be to buy a used s3 with a smashed screen and do a motherboard swap.

Yeah, that's what I'm thinking too at this point since I can't get anything to write onto the memory. I just loaded up Aroma File Manager through recovery and it looks like most of the files on my internal memory are gone, even though I have not been able to successfully factory reset through recovery. At least I have TiBkps of everything.
Do you think I could franken-phone using an i9100 (international model S3)?

Boot into download to find out.

Complete(Write) operation failed.

hi
got a problem - phone hanged during startup on att logo, then i tried following
1. reboot via recovery - hanged after reboot
2. clear cache - hanged after reboot
3. factory reset - after reboot on samsung galaxy logo
4. OAT firmare is not picked up
5. odin nugat - getting write failed
6. odin marshmallow - same:
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
for marshmallow i used following firmware
G891AUCS2API2_CL8737252_QB10881022_REV02_user_low_ship_MULTI_CERT.rar.
in recovery following error message shown at the bottom:
dm-verity verification failed
E:failed to mount /system (invalid argument)
any idea what to do next?

danila2 said:
hi
got a problem - phone hanged during startup on att logo, then i tried following
1. reboot via recovery - hanged after reboot
2. clear cache - hanged after reboot
3. factory reset - after reboot on samsung galaxy logo
4. OAT firmare is not picked up
5. odin nugat - getting write failed
6. odin marshmallow - same:
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
for marshmallow i used following firmware
G891AUCS2API2_CL8737252_QB10881022_REV02_user_low_ship_MULTI_CERT.rar.
in recovery following error message shown at the bottom:
dm-verity verification failed
E:failed to mount /system (invalid argument)
any idea what to do next?
Click to expand...
Click to collapse
Download qb2 for nougat again.
Be sure u got correct Odin.
As I had no problem redoing my phone
Friday night back to qb2.
Sent from my SAMSUNG-SM-G891A using Tapatalk