Hello there,
I have a problem with my T210 that I'm unable to fix. I've tried them all but it did not change at all.
So, starting things off, the problem started after flashing T210XXBOA3 using Odin. I've booted and did the setup process, all working fine till there. Then back to Odin I've flashed t210-TWRP 3.0.0. After that, I went into recovery before booting up and I did the mistake of letting TWRP install the root (I have the app to install the root but no root). So I've booted the device again and I was greeted by the system again, but with the difference that it seems unable to save any change to any part of the memory, and after 15 seconds to 1 minute it will always restart.
Whatever setting you change before it reboots, it is forgotten and always starts up at the same state as before. Even if you add a file to the memory, after a reboot it disappears.
Same goes from the recovery. Wiping, installations or whatever else will show as progressing properly, but the system will be unchanged after you reboot.
I've tried all I can think off:
- Odin: Most of the time it will give out "Nand write start fail". However, when the installation actually starts it shows the process till completion, but again no changes at all when you start the system.
- TWRP: Factory reset no changes, Advanced wipe with all selected no changes, wipe+zip installation (using sd for the files) no changes, data format no changes. I even tried to manually send the commands for a wipe using the terminal, but no changes
It will always show as if the commands were applied and files deleted (even checking with the file manager), but as soon as you reboot it is back to the original state.
- I even tried using the factory reset built in the setting, but when you click on erase everything it does not send the command.
- Lastly, I've tried to disconnect the battery hoping that a discharge would affect the situation in any way. It didn't
So here is the status.
Please hit me with any suggestion to fix this issue.
D4V3an0n said:
Hello there,
I have a problem with my T210 that I'm unable to fix. I've tried them all but it did not change at all.
So, starting things off, the problem started after flashing T210XXBNH4_T210OXABNH4 using Odin. I've booted and did the setup process, all working fine till there. Then back to Odin I've flashed t210-TWRP 3.0.0. After that, I went into recovery before booting up and I did the mistake of letting TWRP install the root (I have the app to install the root but no root). So I've booted the device again and I was greeted by the system again, but with the difference that it seems unable to save any change to any part of the memory, and after 15 seconds to 1 minute it will always restart.
Whatever setting you change before it reboots, it is forgotten and always starts up at the same state as before. Even if you add a file to the memory, after a reboot it disappears.
Same goes from the recovery. Wiping, installations or whatever else will show as progressing properly, but the system will be unchanged after you reboot.
I've tried all I can think off:
- Odin: Most of the time it will give out "Nand write start fail". However, when the installation actually starts it shows the process till completion, but again no changes at all when you start the system.
- TWRP: Factory reset no changes, Advanced wipe with all selected no changes, wipe+zip installation (using sd for the files) no changes, data format no changes. I even tried to manually send the commands for a wipe using the terminal, but no changes
It will always show as if the commands were applied and files deleted (even checking with the file manager), but as soon as you reboot it is back to the original state.
- I even tried using the factory reset built in the setting, but when you click on erase everything it does not send the command.
- Lastly, I've tried to disconnect the battery hoping that a discharge would affect the situation in any way. It didn't
So here is the status.
Please hit me with any suggestion to fix this issue.
Click to expand...
Click to collapse
Hello I will try to help you
Go to this link and download repair firmware for your tab
https://firmware.gem-flash.com/index.php?a=browse&b=category&id=12003
Open Odin and tick erase
Select csc, pda, etc from the firmware you have downloaded
This will fix the fimware
Sorry for bad English
sasi2006166 said:
Hello I will try to help you
Go to this link and download repair firmware for your tab
https://firmware.gem-flash.com/index.php?a=browse&b=category&id=12003
Open Odin and tick erase
Select csc, pda, etc from the firmware you have downloaded
This will fix the fimware
Sorry for bad English
Click to expand...
Click to collapse
HI,
Thank you for your answer. I tried what you said, but I am unable to.
My device is now acting differently than before. As I said with Odin it gave "NAND write start fail" most of the time, but after multiple attempts, it would go through the flashing process.
I'm now always getting instead a "Complete (write) operation failed"
here is the log of two following attempt:
Code:
<ID:0/006> Added!!
<ID:0/006> Removed!!
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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/006> Odin engine v(ID:3.1301)..
<ID:0/006> File analysis..
<ID:0/006> Total Binary size: 1536 M
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Erase...
<ID:0/006> ERASE_SECTOR: 0
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> NAND Write Start!!
<ID:0/006> SingleDownload.
<ID:0/006> PBL.bin
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
<ID:0/006> Added!!
<ID:0/006> Odin engine v(ID:3.1301)..
<ID:0/006> File analysis..
<ID:0/006> Total Binary size: 1536 M
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Erase...
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
ps. there is a Removed/added between the two because if you don't the process would get stuck at SetupConnection indefinitely
pps. also sometimes at the second attemp it will also say "There is no PIT partition" right before the "Complete(Write) operation failed" error
I've tried to change USB port, change the cable, reinstall drivers (the device seems to be recognized correctly), change the version of Odin (from 1.3 to 3.13.1), and even do multiple attempts during the same Odin session as some suggest that would solve the "Complete (write) operation failed".
However, the problem persists.
What next?
D4V3an0n said:
HI,
Thank you for your answer. I tried what you said, but I am unable to.
My device is now acting differently than before. As I said with Odin it gave "NAND write start fail" most of the time, but after multiple attempts, it would go through the flashing process.
I'm now always getting instead a "Complete (write) operation failed"
here is the log of two following attempt:
Code:
<ID:0/006> Added!!
<ID:0/006> Removed!!
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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/006> Odin engine v(ID:3.1301)..
<ID:0/006> File analysis..
<ID:0/006> Total Binary size: 1536 M
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Erase...
<ID:0/006> ERASE_SECTOR: 0
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> NAND Write Start!!
<ID:0/006> SingleDownload.
<ID:0/006> PBL.bin
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
<ID:0/006> Added!!
<ID:0/006> Odin engine v(ID:3.1301)..
<ID:0/006> File analysis..
<ID:0/006> Total Binary size: 1536 M
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Erase...
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
ps. there is a Removed/added between the two because if you don't the process would get stuck at SetupConnection indefinitely
pps. also sometimes at the second attemp it will also say "There is no PIT partition" right before the "Complete(Write) operation failed" error
I've tried to change USB port, change the cable, reinstall drivers (the device seems to be recognized correctly), change the version of Odin (from 1.3 to 3.13.1), and even do multiple attempts during the same Odin session as some suggest that would solve the "Complete (write) operation failed".
However, the problem persists.
What next?
Click to expand...
Click to collapse
Try using another USB and Odin 3.10
Edit:Try flashing only bootloader and tell me
sasi2006166 said:
Try using another USB and Odin 3.10
Edit:Try flashing only bootloader and tell me
Click to expand...
Click to collapse
I've tried with all the USBs that I have.
With Odin 3.10 it is the same. Same error same log.
I've also tried flashing only the bootloader, but no difference.
edit: I would like to underline that USB debug works for the few minutes that the device stays turned on. Is there anything I could try through there?
edit2: I've also now tried with all four of the firmware versions that are available at the provided link. Same Complete(write) error tho.
D4V3an0n said:
I've tried with all the USBs that I have.
With Odin 3.10 it is the same. Same error same log.
I've also tried flashing only the bootloader, but no difference.
edit: I would like to underline that USB debug works for the few minutes that the device stays turned on. Is there anything I could try through there?
edit2: I've also now tried with all four of the firmware versions that are available at the provided link. Same Complete(write) error tho.
Click to expand...
Click to collapse
First Try unistalling root and in flash firmware with odin
Edit:Try flashing Android 4.1 and tick erase all
Link android 4.1 4 file firmware:
https://androidfilehost.com/?fid=24499762636002697
Fixed?
sasi2006166 said:
Fixed?
Click to expand...
Click to collapse
Sorry for the late reply.
The root is not installed. As I said the TWRP installed an app as a system to install the root, but I have no root. I have no way to remove the app as the recovery is unable to apply any change to the system.
I've tried to install 4.1.2, but usual Odin error.
D4V3an0n said:
Sorry for the late reply.
The root is not installed. As I said the TWRP installed an app as a system to install the root, but I have no root. I have no way to remove the app as the recovery is unable to apply any change to the system.
I've tried to install 4.1.2, but usual Odin error.
Click to expand...
Click to collapse
Try flashing custom stock rom
Edit: First try flashing recovery, and flash fimware
May not make any difference, but I always had better luck with Odin 3.07. You can grab it HERE.
Also, keep in mind that if you have flashed the KitKat bootloader, you can not go back to the 4.1.2 firmware.
sasi2006166 said:
Try flashing custom stock ROM
Edit: First try flashing recovery, and flash fimware
Click to expand...
Click to collapse
Flashing a recovery gives out the same Complete(write) failure.
Custom stock ROM flashed by recovery go to the completion of the process, but they do not change a thing to the system. Is there any custom ROM for odin?
gr8nole said:
May not make any difference, but I always had better luck with Odin 3.07. You can grab it HERE.
Also, keep in mind that if you have flashed the KitKat bootloader, you can not go back to the 4.1.2 firmware.
Click to expand...
Click to collapse
With the 3.07 version of Odin, I've managed to get the other weird problem that I've mentioned at the start of my tread. The flashing will go to completion, but the system is unchanged.
Here is the log flashing T210XXBOA3 (4.4.2) with erase:
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BL_T210XXBOA3_CL3952694_QB3792367_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> AP_T210XXBOA3_CL3952694_QB3792367_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CSC_ILO_T210ILOBNI2_CL2813887_QB2395848_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Erase...
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> PBL.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> param.lfs
<ID:0/006> loke_2nd.bin
<ID:0/006> loke_pxa988.bin
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img
<ID:0/006> NVM.img
<ID:0/006> cache.img
<ID:0/006> hidden.img
<ID:0/006> RQT_CLOSE !!
<ID:0/006> RES OK !!
<ID:0/006> Removed!!
<ID:0/006> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
The system and bootloader currently installed are 4.4.2 T210XXBOA3. The same I was trying to install.
Edit: on that note here is another attempt flashing T210XXBNH5 with same results, no changes to the system:
Code:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BL_T210XXBNH5_2432755_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> AP_T210XXBNH5_2432755_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CP_T210XXBNH5_2432755_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CSC_OJV_T210OJVBNH1_2432755_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Erase...
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> PBL.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> param.lfs
<ID:0/006> loke_2nd.bin
<ID:0/006> loke_pxa988.bin
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img
<ID:0/006> NVM.img
<ID:0/006> radio.img
<ID:0/006> Transmission Complete..
<ID:0/006> Now Writing.. Please wait about 2 minutes
<ID:0/006> Receive Response from boot-loader
<ID:0/006> cache.img
<ID:0/006> hidden.img
<ID:0/006> RQT_CLOSE !!
<ID:0/006> RES OK !!
<ID:0/006> Removed!!
<ID:0/004> Removed!!
<ID:0/004> Removed!!
<ID:0/006> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Ok, let's focus on one thing at a time.
When you say "no changes to the system", does that mean you still can't write to storage and the device still reboots?
One thing to remember is that flashing through Odin does not wipe memory, so your settings and data will remain intact.
I recommend trying this: Flash stock 4.4.2 firmware. Do not attempt any custom recovery yet. Boot into system and do a factory reset, or boot into stock recovery and do factory reset.
If you can get that to work; then you can try adding the custom recovery and root.
gr8nole said:
Ok, let's focus on one thing at a time.
When you say "no changes to the system", does that mean you still can't write to storage and the device still reboots?
One thing to remember is that flashing through Odin does not wipe memory, so your settings and data will remain intact.
I recommend trying this: Flash stock 4.4.2 firmware. Do not attempt any custom recovery yet. Boot into system and do a factory reset, or boot into stock recovery and do factory reset.
If you can get that to work; then you can try adding the custom recovery and root.
Click to expand...
Click to collapse
When I say nothing has changed I mean it in every way. For example, in the last attempt, I've used a different build version of the system, but the one installed is still the same one. Every setting is the same and the Superuser.apk (that is probably the one causing problems and installed as a system app) is still there every time. I even tried flashing Cwm recovery through Odin, and even though the process went through I still have TWRP.
Besides, I was using Odin nand erase in many of my attempts, and if I'm not mistaken that should format the content.
Moreover, I've mentioned before that not even the changes to the system did while the device is booted, such as setting changes, are kept. As soon as you reboot, it is back to the previous state.
About factory reset: Factory reset through the system does not work, it just reboots. Through TWRP recovery I've tried everything as mentioned in the main thread: factory Reset, Advanced wipe with system selected as well, Format data, manual wipe using shell commands. TWRP will go through the process, but no changes made. (I've tried again now just for the sake of completion but the result is the same).
I have an idea
Flash twrp and boot to recovery
Go to advanced-file manager
Go to system-app or priv app and find superuser.apk
Click on it and delete
And re flash the firmware
sasi2006166 said:
I have an idea
Flash twrp and boot to recovery
Go to advanced-file manager
Go to system-app or priv app and find superuser.apk
Click on it and delete
And re flash the firmware
Click to expand...
Click to collapse
Tried before and tried again now with your exact process, no changes.
I've also tried before to delete it (apk and data folder) using twrp terminal, twrp file manager and adb shell with usb debugging. No changes at all. (with those three methods I've also tried manually applying a factory reset but as usual no changes at all.)
D4V3an0n said:
Tried before and tried again now with your exact process, no changes.
I've also tried before to delete it (apk and data folder) using twrp terminal, twrp file manager and adb shell with usb debugging. No changes at all. (with those three methods I've also tried manually applying a factory reset but as usual no changes at all.)
Click to expand...
Click to collapse
With Odin try flashing ONLY PDA and BOOTLOADER
sasi2006166 said:
With Odin try flashing ONLY PDA and BOOTLOADER
Click to expand...
Click to collapse
No use, same result.
D4V3an0n said:
No use, same result.
Click to expand...
Click to collapse
Hey you have fixed?
Make screen recording and share
sorry for bad english
sasi2006166 said:
Hey you have fixed?
Make screen recording and share
sorry for bad english
Click to expand...
Click to collapse
still not fixed
has anyone got any idea on how to fix it
Related
Hello,
I have seen my note2 die in front of my eyes :/ reading a whatsapp the screen turned weird and shutdown, never to live again I fear.
I guess nand corruption? Infact was freezing and rebooting every now and then.
Model is n7100 international version (got it from an italian provider), rooted with samsung galaxy note 2 toolkit.
My flash counter is 1 and I read custom everywhere in the download mode. I'd give this to service centre but I guess I can't like this, right?
Any way of resetting flash counter from download mode? tried stock recovery and rom to no avail
So I can only enter download mode correctly and flash, no booting as stuck at samsung's glowing logo.
Results: tried flashing cwm (tried several versions from the main thread on xda http://forum.xda-developers.com/showthread.php?t=2000138) flashes OK, but does not work entering recovery (I try invoking recovery by turning the phone on, having volume up and home button pressed) but the phone hangs in a loop.
My aim is to: access mounts (extract data from sdcard0, internal), wipe it/delete everything, flash stock rom and recovery.
I can only flash recovery image successfully, the original sammobile rom for n7100 will pass md5 correctly but won't flash in the end
BTW all flashes require a double md5 check and a double pressure of start to go on...
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7100XXDMC3_N7100ITVDMB1_N7100XXDLK7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/013> Added!!
<OSM> All threads completed. (succeed 0 / failed 0)
[here I press start again]
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7100XXDMC3_N7100ITVDMB1_N7100XXDLK7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/013> Odin v.3 engine (ID:13)..
<ID:0/013> File analysis..
<ID:0/013> SetupConnection..
<ID:0/013> Initialzation..
<ID:0/013> Get PIT for mapping..
<ID:0/013> Firmware update start..
<ID:0/013> sboot.bin
<ID:0/013> NAND Write Start!!
<ID:0/013>
<ID:0/013> Complete(Write) operation failed.
<ID:0/013> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
OTHER try with other sam.updates rom for my device = success in flashing, not in booting.
<ID:0/013> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7100XXDLL4_N7100VFGDLL2_N7100BUDLL1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/013> Odin v.3 engine (ID:13)..
<ID:0/013> File analysis..
<ID:0/013> SetupConnection..
<ID:0/013> Initialzation..
<ID:0/013> Get PIT for mapping..
<ID:0/013> Firmware update start..
<ID:0/013> boot.img
<ID:0/013> NAND Write Start!!
<ID:0/013> recovery.img
<ID:0/013> system.img
<ID:0/013> modem.bin
<ID:0/013> cache.img
<ID:0/013> hidden.img
<ID:0/013> RQT_CLOSE !!
<ID:0/013> RES OK !!
<ID:0/013> Completed..
<ID:0/013> Added!!
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/013> Removed!!
I asked krollontrack about data recovery but they do not offer the service on cell phones as results are flaky.
My flash counter is 1 and I read custom everywhere in the download mode. I'd give this to service centre but I guess I can't like this, right?
#G# said:
Hello,
I have seen my note2 die in front of my eyes :/ reading a whatsapp the screen turned weird and shutdown, never to live again I fear.
I guess nand corruption? Infact was freezing and rebooting every now and then.
Model is n7100 international version (got it from an italian provider), rooted with samsung galaxy note 2 toolkit.
So I can only enter download mode correctly and flash, no booting as stuck at samsung's glowing logo.
Results: tried flashing cwm (tried several versions from the main thread on xda http://forum.xda-developers.com/showthread.php?t=2000138) flashes OK, but does not work entering recovery (I try invoking recovery by turning the phone on, having volume up and home button pressed) but the phone hangs in a loop.
My aim is to: access mounts (extract data from sdcard0, internal), wipe it/delete everything, flash stock rom and recovery.
I can only flash recovery image successfully, the original sammobile rom for n7100 will pass md5 correctly but won't flash in the end
BTW all flashes require a double md5 check and a double pressure of start to go on...
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7100XXDMC3_N7100ITVDMB1_N7100XXDLK7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/013> Added!!
<OSM> All threads completed. (succeed 0 / failed 0)
[here I press start again]
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7100XXDMC3_N7100ITVDMB1_N7100XXDLK7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/013> Odin v.3 engine (ID:13)..
<ID:0/013> File analysis..
<ID:0/013> SetupConnection..
<ID:0/013> Initialzation..
<ID:0/013> Get PIT for mapping..
<ID:0/013> Firmware update start..
<ID:0/013> sboot.bin
<ID:0/013> NAND Write Start!!
<ID:0/013>
<ID:0/013> Complete(Write) operation failed.
<ID:0/013> Added!!
<OSM> All threads completed. (succeed 0 / failed 1
I asked krollontrack about data recovery but they do not offer the service on cell phones as results are flaky.
My flash counter is 1 and I read custom everywhere in the download mode. I'd give this to service centre but I guess I can't like this, right?
Click to expand...
Click to collapse
Just tell Service Center sudden death. They might replaced it for you. I try before.
could it have been cos of your nickname resembling reality?
88sexylady said:
Just tell Service Center sudden death. They might replaced it for you. I try before.
Click to expand...
Click to collapse
Aha! I am thinking about trying, maybe I should send a sexy lady to they guy at the front desk to gain the same attention
Hadn't even thought about flash counters...
Infact if it was possible I'd like to reset flash count from download mode, or... make it so the screen actually stays off )
G
I had this with my SGS 3.
I tried to flash a different framework and got boot loop. Tried flashing a stock rom with odin and once it restarted it would boot loop again and odin would say fail.
I flashed cf root kernel with odin to get CWM and then used Zoots wipe script (mega wipe) to bring it back to bare bones. Then took out the battery and put it back in and 3 button into download mode and then flashed the stock rom again... This time it booted up. There is always hope as long as you can get download mode my friend
Sent from my GT-N7100 using xda premium
and again
and again.
turned off at 2% battery to replace the battery with the spare one.
Waited for full shutdown etc -> boot loop. Shut! Had twrt recovery and could copy data over to the sd (just a couple of things I was missing from the latest backup).
Why? No understanding. Did not dig (formatting dalvik I also accidentally formatted /system and data (...)), yet I am surprised: twice in 12 months.
Great phone for the rest.
Odin showed no mercy for a while... then magically worked, stock sammobile rom.
4.3 rocks and it still records phonecalls, major thing on the main phone for me.
Good afternoon, and thank you for taking your time to read my thread.
I recently attempted to root my phone, and having little to no issue rooting many other devices (including my previous phone, a Galaxy Prevail) I decided I was fed up with the bloatware.
I began the process, but encountered an issue where ODIN failed while attempting to root the device.
I am not 100% sure, but I know this information may very well help me to a solution: I don't think I enabled debug mode in settings.
When attempting to use KIES to restore firmware, I get a "this device is not recognized" error, and even when trying to manually enter S/N and device info, it will not let me use any part of KIES to restore it.
So I then tried to use ODIN to flash stock firmware...
First error I receive is almost immediate:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747UCDLK3_I747ATTDLK3_I747UCDLK3_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> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
Occasionally, and after about 3 minutes this appears. (and it seems only when attempting to use ODIN on the device multiple times before reboot)
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747UCDLK3_I747ATTDLK3_I747UCDLK3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Please, if you have any advice for me I am begging.. I only was able to upgrade to this device because of a promotion AT&T had to get it for $5 dollars.. I am very income restricted so buying a new device is a crippling idea. If you do by chance suggest I download a new version of ODIN ( I am using 3.07, I find it most stable) or a new stock firmware etc, please provide links as I have attempted many different mirrors (with horrendous download speeds) for different stock recovery firmware.
THANK YOU!!!
I appreciate your time.. All it took was attempting to root the phone another time to restore access... Wow.. I hate myself ._.
Vonzilla said:
I appreciate your time.. All it took was attempting to root the phone another time to restore access... Wow.. I hate myself ._.
Click to expand...
Click to collapse
So, what's the state of the phone now and what happens when you try to power on? Is it now booting normally to system?
I updated my i317M (Telus) via OTA and the next day it rebooted and went into boot loop.
I've tried flashing the phone with 4 different stock roms (from 4.1.2 to 4.4.2) but they all fail.
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I317MVLBMA3_I317MOYABMA3_I317MVLBMA3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> sboot.bin
<ID:0/006> NAND Write Start!!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I've tried flashing Philz Touch recovery but that fails as well.
I've tried to boot it into recovery mode but it shows a dead Android with error logs like "E:failed to mount"
Help?
goyagoyago said:
I updated my i317M (Telus) via OTA and the next day it rebooted and went into boot loop.
I've tried flashing the phone with 4 different stock roms (from 4.1.2 to 4.4.2) but they all fail.
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I317MVLBMA3_I317MOYABMA3_I317MVLBMA3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> sboot.bin
<ID:0/006> NAND Write Start!!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I've tried flashing Philz Touch recovery but that fails as well.
I've tried to boot it into recovery mode but it shows a dead Android with error logs like "E:failed to mount"
Help?
Click to expand...
Click to collapse
Try flashing with odin again but before flashing open the tar and remove the bootloader out of it.
Hi, thanks for the reply cnote.
Would the bootloader be sboot.bin or boot.img or both?
thanks again
edit: or rather, how do you remove the bootloader and remake the tar file?
goyagoyago said:
Hi, thanks for the reply cnote.
Would the bootloader be sboot.bin or boot.img or both?
thanks again
edit: or rather, how do you remove the bootloader and remake the tar file?
Click to expand...
Click to collapse
I believe it;s both. Just retrieve the tar file only.
sboot is the bootloader boot.img is the kernel .Have you tried the latest NH2 for your phone also maybe try using a pit file
The nh2 you will have to get from sammobile and the pit file can be found here http://forum.xda-developers.com/showthread.php?t=2609871
Also after odin is finished go into factory recovery and do a factory reset or its just going to sit at the boot screen
flashing pit file also gives an error :S
Hi there,
I have run into this problem with my cellphone (S4 Mini gt-i9192). After it discharged, i connected it on the charger. My device failed to boot and got stuck at download mode ("Could not do normal boot" and mmc read fail). I've tried some procedures i found on the internet:
- flashing some original ROMs with and without PIT file
- hard reset
- wipe cache data
- boot thorugh recovery
The results vary, but I never got it a pass on Odin. Without a PIT file Odin displays "There is no PIT partition" and with PIT file, is displays:
<ID:0/005> Added!!
<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/005> Odin engine v(ID:3.1101)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Auto reboot and F. Reset Time are enabled with or without PIT file and Re-partition is only enabled with a PIT file. So, nothing out of usual for this part.
I also remark that I have never rooted it. I realize I should keep downloading stock ROMs and hope for a flash that works because there might a problem with my mmc, but maybe someone knows another procedure to recommend me. I appreciate all feedback and thank for it in advance. ALso, tell me if I didn't provide any info that could help solve this problem.
Hi everyone,
looks like my mobile remains in bootloop (Samsung Logo) and I can’t solve it since a few days. As I didn’t find the right solution in the forum I hope that somebody of you have a clever idea what I could test.
It started that the phone rebooted every few minutes (maybe an update was running) and I couldn’t do anything. After I wiped cache and data in the recovery mode (factory reset) the mobile worked for one day. As I needed to reboot the mobile I get stucked on the screen with the Samsung logo.
As I’m still able to access download and recovery mode I tried the same procedure as written above without success. I downloaded the latest firmware (A320FLXXS5CSK1 / DBT) with samfirm (V.0.5.0) and flashed it with Odin (V3.14.1). This was successful with Odin but I waited over an hour and the mobile didn’t pass over the Samsung screen. I tried to repeat the procedure and disabled autoboot – no success even after starting samsung recovery mode and wipe cache + data. (Odin successful – installing android on mobile after reboot remains on samsung logo)
In recovery mode I see the following failures but not sure if it indicates to the root cause as I tested the recovery mode with a working SMA320FL and saw the same failures.
#fail to open recovery_cause(No such file or directory)#
#Reboot Recovery Cause is [UNKNOWN]#
E:Failed to clear BCB message: failed to find /misc partition
I had an SD card in usage. I tried it with and without: No change.
I can’t install TWRP as the phone is FRP locked and as soon as I try to install TWRP it will be blocked. As I couldn’t find a combination file with the same binary I couldn’t try the described procedure by forens1c.
https://forum.xda-developers.com/sa...20fl-2017-unlock-solution-frp-update-t3884971
Downgrade as far I understood is not possible due to the latest version of bootloader.
Further information:
Android 8.0
SM-A320FL
Current binary:Samsung Official
System Status: Custom
FRP Lock: On
B:5 K:3 S:3
Odin Log as example:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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/006> Added!!
<ID:0/006> Odin engine v(ID:3.1401)..
<ID:0/006> File analysis..
<ID:0/006> skip file list for home binary
<ID:0/006> param.bin
<ID:0/006> userdata.img
<ID:0/006> modem_debug.bin
<ID:0/006> Home Binary Download
<ID:0/006> Total Binary size: 3864 M
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> NAND Write Start!!
<ID:0/006> SingleDownload.
<ID:0/006> sboot.bin
<ID:0/006> cm.bin
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img
<ID:0/006> modem.bin
<ID:0/006> cache.img
<ID:0/006> hidden.img
<ID:0/006> RQT_CLOSE !!
<ID:0/006> RES OK !!
<ID:0/006> Removed!!
<ID:0/006> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Would be good to have any advice what else could be tested.
Flix24 said:
Hi everyone,
looks like my mobile remains in bootloop (Samsung Logo) and I can’t solve it since a few days. As I didn’t find the right solution in the forum I hope that somebody of you have a clever idea what I could test.
It started that the phone rebooted every few minutes (maybe an update was running) and I couldn’t do anything. After I wiped cache and data in the recovery mode (factory reset) the mobile worked for one day. As I needed to reboot the mobile I get stucked on the screen with the Samsung logo.
As I’m still able to access download and recovery mode I tried the same procedure as written above without success. I downloaded the latest firmware (A320FLXXS5CSK1 / DBT) with samfirm (V.0.5.0) and flashed it with Odin (V3.14.1). This was successful with Odin but I waited over an hour and the mobile didn’t pass over the Samsung screen. I tried to repeat the procedure and disabled autoboot – no success even after starting samsung recovery mode and wipe cache + data. (Odin successful – installing android on mobile after reboot remains on samsung logo)
In recovery mode I see the following failures but not sure if it indicates to the root cause as I tested the recovery mode with a working SMA320FL and saw the same failures.
#fail to open recovery_cause(No such file or directory)#
#Reboot Recovery Cause is [UNKNOWN]#
E:Failed to clear BCB message: failed to find /misc partition
I had an SD card in usage. I tried it with and without: No change.
I can’t install TWRP as the phone is FRP locked and as soon as I try to install TWRP it will be blocked. As I couldn’t find a combination file with the same binary I couldn’t try the described procedure by forens1c.
https://forum.xda-developers.com/sa...20fl-2017-unlock-solution-frp-update-t3884971
Downgrade as far I understood is not possible due to the latest version of bootloader.
Further information:
Android 8.0
SM-A320FL
Current binary:Samsung Official
System Status: Custom
FRP Lock: On
B:5 K:3 S:3
Odin Log as example:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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/006> Added!!
<ID:0/006> Odin engine v(ID:3.1401)..
<ID:0/006> File analysis..
<ID:0/006> skip file list for home binary
<ID:0/006> param.bin
<ID:0/006> userdata.img
<ID:0/006> modem_debug.bin
<ID:0/006> Home Binary Download
<ID:0/006> Total Binary size: 3864 M
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> NAND Write Start!!
<ID:0/006> SingleDownload.
<ID:0/006> sboot.bin
<ID:0/006> cm.bin
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img
<ID:0/006> modem.bin
<ID:0/006> cache.img
<ID:0/006> hidden.img
<ID:0/006> RQT_CLOSE !!
<ID:0/006> RES OK !!
<ID:0/006> Removed!!
<ID:0/006> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Would be good to have any advice what else could be tested.
Click to expand...
Click to collapse
Try repartition device.