Ok, I got a new Note II the other day with 4.3 already installed via Kies or OTA. I attempted to push, via ODIN, "CF-Auto-Root-d2tmo-d2tmo-sght999.tar". I REALIZE THIS IS THE ROOT FOR S3; I KNOW I FLASHED THE WRONG FILE. PLEASE DO NOT POST SAYING I FLASHED THE WRONG FILE. I KNOW I SCREWED UP BIG TIME, AND I'M HOPING SOMEONE IS NICE ENOUGH TO TRY AND HELP ME THROUGH THIS. My laptop sat there for the better part of 2 hours acting like ODIN was cranking along but the bar never moved. After 2 hours, I had to pull the cord from the phone (stupid move, I know!), and this is, of course, where the problem began.
Now, I get the coveted "Firmware Upgrade encountered an issue. Please select recovery mode in Kies & try again." screen. The phone will, obviously, go no further than this in booting up. I am able to get to download mode.
I attempted to install JellyBean Release 4.3 (December 2013) from this thread to alleviate the issue. Here's the ODIN result:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_TMO_T889UVUCMK7_2.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> cache.img
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
Now, as I sit here and write this, I think installing a stock firmware like this one might not work at all. I need to install a recovery (stock or otherwise) to make this problem disappear. I tried to reinstall the CF-Auto-Root file and got this result:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-d2tmo-d2tmo-sght999.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-d2tmo-d2tmo-sght999.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
Again, it didn't do anything for hours. I pulled the cord again since it didn't look like it was actually writing anything to my phone.
I don't think I can use KIES as a last resort since I never backed up the phone through KIES before. I am out of ideas, and I would really like to get this phone operational again. Also, the serial number has been removed from the device (Igot the phone from Ebay), so I don't think I could use this route either.
Any and all help would be greatly appreciated.
Thanks in advance!
Download and flash CF auto-root for sgh-t889(link below)it includes recovery, then perform factory reset by rebooting in to recovery.
http://download.chainfire.eu/266/CF-Root/CF-Auto-Root/CF-Auto-Root-t0ltetmo-t0ltetmo-sght889.zip
Sent from my SGH-T889 using xda app-developers app
My phone just boots to the "Saumsung Galaxy Note II" screen and it is stuck there. I dont think its a loop because it doesnt loop (by that I mean it doesnt disappear and appear).
I m afraid using odin would erase everything.
I want to save my data, what should I do? Which rom do i use?
I tried downloading 3 to 4 note 2 roms but they all failed in odin.
Please specify what I need to download in order to save my data.
At this point, I am also ready to just give up and restore factory settings. I went to the at&t technicans, who are completely useless and they used their roms and couldnt help at all. I went to a fix phone place and they couldnt do anything either.
Please help!
Your request is ambiguous at best.
.
We have absolutely no idea what you have done beyond flashing multiple roms to the device..
I assume the device is dirty due too multiple frameworks being flashed over one another..
If it were my device...I'd go clean slate and restore the device to a stock configuration and work up from there.
.
It's a mess in there for sure.
So see the return to stock thread in the general section...and use Odin if possible....and IMHO...stay away from kies....g
i have no idea either. for all i know, none of them did anything since they all failed after this boot freeze has been happening.
im trying to go clean slate but i cant even do that.
im trying to odin with http://www.sammobile.com/firmwares/confirm/13212/I317UCAMA4_I317ATTAMA4_ATT/
but it doesnt work either!!!
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_I317UCAMA4_I317ATTAMA4_578342_REV04_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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
downloaded both roms and both failed again
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_I317UCALJ2_I317ATTALJ2_215287_REV04_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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
This morning I flashed Lineage 14.1 and there were no errors. But it got stuck at the Samsung logo during reboot. I waited about 15 minutes. I could not figure out how to fix it so I decided to flash the stock firmware using Odin. It passed but also got stuck at the same screen during reboot. Then I did a hard system recovery but still could not boot past the Samsung logo. After that I install Samsung Kies 3, but it said the phone is no longer supported. Then I tried Kies 2.6 but it said the phone SGH-M919 does not support initialization. Now I can't get to the system recovery screen anymore. It would say there is an issue with the firmware update and try again in Kies. I cannot flash the stock firmware in Odin anymore either. It would fail with a complete write error. I don't know what else to try. Please help me.
Did you confirm the phone's model # in download mode?
You tried different USB cables, different USB ports, and different versions of Odin?
What was the exact Odin error?
Yes, the model is correct SGH-M919. I've tried Odin 3.0.7 and 3.10.6. I used Odin 3.0.7 to root and install TWRP recovery using the same original Samsung USB cable. So the cable and port should be OK. I tried it again this morning and noticed it took a long time after the message "Get PIT for mapping.."
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> M919UVUFOK3_M919TMBFOK3_M919UVUFOK3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I tried it again using a different USB port and this time it failed right away. I didn't see the line "Get PIT for mapping" this time. Here are the messages in Odin.
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> M919UVUFOK3_M919TMBFOK3_M919UVUFOK3_HOME.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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
<ID:0/005> Added!!
I was using the USB ports at the front of the PC and none of them worked. I tried one port at the back and it worked. Thank you very much. I never thought this would make a difference because I use the ports in the front all the time with my other iPhones, iPads, USB memory sticks and never had a problem. I lost all my data on the phone but that's OK. I would not dare to install custom ROM again. It looked so easy in youtube videos. Thanks again.
Glad you got it working. I always use the ports at the back of my desktop because I find it more reliable than the front case ports.
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