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
So I rooted my s4 mini i9195 and flashed aicp ver 10 and now I have no wifi, no mobile, no lte, the haptic feedback buttons don't work, no led, and my computer doesn't recognize the s4 mini unless I go into download mode. When I start up the phone it says something about something being wrong with the internal hardware of my phone but it's a brand new phone and I didn't have these problems before flashing this rom. I tried using odin to go back to stock and it fails at nand-write start. I tried loading a new pit and that fails too. I'm completely stuck now. I have no idea what to do. Can someone please help me?
How you flashed aicp?
I used cwm.
Here's what comes up on odin when I try to flash back to stock:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9195XXUCOD3_I9195BTUCOD1_I9195XXUCOD3_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> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<ID:0/006> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Can you enter in recovery mode?
yeah, I can. I tried clearing caches and data and flashing aicp over again, it didn't work-in fact, for whatever reason the aicp rom isn't in my sd card anymore.
Try to flash a stock deodexed rom from here http://forum.xda-developers.com/showthread.php?t=2552363 using your custom recovery
the problem with that is I can't get anything from my computer to my phone because the phone doesn't pop up on My Computer and the phone doesn't give me any options when it's plugged in. It's only recognized when in download mode and trying to do anything in download mode doesn't seem to work.
Download direct to you phone and then move to sdcard or download to pc and than just using a card reader move rom to your sdcard and then try to flash
I can't download directly to my phone, I have no connection whatsoever on my phone.
Use a computer and a card reader ))
I'm going to get an sd reader later today. I tried flashing the modem and this is what I got:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MODEM_I9195XXUCOC2.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> NON-HLOS.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> Transmission Complete..
<ID:0/006> Now Writing.. Please wait about 2 minutes
<ID:0/006>
<ID:0/006> Receive Response from boot-loader
<ID:0/006> Complete(Write) operation failed.
<ID:0/006> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
What firmware did you have before flashing aicp?
It was android 4.4.2 touchwiz I believe but I don't know the details. The phone was up-to-date and it's I9195
Whatever try to restore to a stock rom by flashing a deodexed rom
so the rom flashed properly but I still didn't have mobile data or wifi or haptic feedback. I'm not really worried about the haptic keys because I can just use softkeys if necessary but the mobile data and wifi are an issue. LED worked when I shut the phone down to put it into download mode to flash the modem. Flashing the modem was unsuccessful:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MODEM_I9195XXUCOC2.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> NON-HLOS.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> Transmission Complete..
<ID:0/005> Now Writing.. Please wait about 2 minutes
<ID:0/005>
<ID:0/005> Receive Response from boot-loader
<ID:0/005> Complete(Write) operation failed.
<ID:0/005> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
And the phone came up with red lettered "Secure Check Fail Modem"
Try to call *#06# And tell what you get
At least look here http://forum.xda-developers.com/gal...rom-aicp-6-0-kk-4-4-4-9195-919015-10-t2907258
IMEI 990004400585315 / 01
I looked on that thread but nothing about my issue is coming up.
<ID:0/005> Receive Response from boot-loader
<ID:0/005> Complete(Write) operation failed.
Does this mean that I should flash a new bootloader? I never unlocked knox because beyond voiding the warranty, I didn't think it would have any effect on flashing but I may be wrong?
Your phone is definitely a "i9195" and not a "i9195L"? Was your phone locked to a network?
I found this http://forums.androidcentral.com/sa...ot-flash-really-really-stuck-please-help.html try to do how is described in the last thread but remember that you have a 9195 not a s3
Need help recovering SM-T310 8", stuck at boot screen, Odin won't load TWRP onto it
I've been trying to get this tab back in working order for several hours now - When I first started working on it, all it showed was the "Samsung Galaxy Tab 3" screen, going right back to that when I turn it off (not even staying off.) I tried putting it in download mode (Power+Down+Home, it does work) and loading TWRP 3.1.1 with Odin (tried both 3.07 and 3.12.3) and it fails almost immediately after hitting Start, Kies won't recognize it over USB, and when I put in the model and S/N it says it's "not eligible".
Also, I've tried using the stock recovery mode, but the factory reset doesn't help, and it doesn't recognize the format of the only rom I could find for it (that doesn't require a premium membership.) It's a .tar.md5, TWRP is supposed to be able to handle it, but the system recovery doesn't see it at all.
(click for big)
Here's the Odin log:
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T310.TWRP.3.1.1-0.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)
Help, please? I've gone through multiple past threads here and on other sites I found on Google to get this far, but I've been unable to make any appreciable progress.
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