Hi there,sorry for my bad english i'm Indonesian
My Gnote N8000 upgrade via OTA Official to Kitkat
After few months it's okay,but once week ago My Gnote Restart when i'm using browser.
It's non root and non cwm installing
When i try to flash with Odin V 1.84,1.85,3.09 it's have a same,it's failed
I try to flash with :
Jellybean Stock Rom :
KIES_HOME_N8000XXBLJ9_N8000OXABLJ9_412156_REV00_user_low_ship.tar
Kitkat Stock Rom :
N8000XXUDNE5_N8000OLBDNE3_N8000DXUDND1_HOME.tar
This is in my result in My Fail odin :
Spoiler: my odin
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N8000XXUDNE5_N8000OLBDNE3_N8000DXUDND1_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> SingleDownload.
<ID:0/006> boot.img
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
When i try to get in to recovery mode its just restart again and Logo Samsung Galaxy Note 10
In downloading Mode :
Odin Mode
PRODUCT NAME : GT-N8000
CURRENT BINARY : SAMSUNG OFFICIAL
SYSTEM STATUS : OFFICIAL
RP SWREV : A2
I try anything,i read in xda dev,but just have a same result
Please Anyone can help me
thank you very much before
Regads
Just got my Note 3 (SM-N900v) and first thing I tried to do is root it with Root De La Vega.
True confession: I had no backup before trying to root.
I downloaded the Samsung drivers and installed them.
I downloaded the Odin3.09 program and installed it.
Booted the phone into download mode.
Connected the USB3 cable to the phone.
Started Odin, added the root de la vega file and clicked start.
It gets as far as this:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Root_de_la_Vega.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/014> Odin v.3 engine (ID:14)..
<ID:0/014> File analysis..
<ID:0/014> SetupConnection..
<ID:0/014> Initialzation..
<ID:0/014> Get PIT for mapping..
<ID:0/014> Firmware update start..
<ID:0/014> SingleDownload.
<ID:0/014> cache.img.ext4
<ID:0/014> NAND Write Start!!
<ID:0/014> FAIL! (Auth)
<ID:0/014>
<ID:0/014> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
After it failed the first time, I unplugged the phone and pulled the battery to start over, only this time when it
powered up, it told me:
"Firmware upgrade encountered an issue. Please use Software Repair Assistant & try again"
I'm stumped and don't know what to do now. Any suggestions would be greatly appreciated.
Model:SM-N900V Android Version = 4.4.2 Baseband version =N900VVRUCNC4
Hi there,
All you need for recover your device is in this thread:
[HOWTO] Recover from a HARD BRICK [N900V] [MJE/NC2/NC4]
For other questions please post here:
Verizon Galaxy Note 3 Q&A, Help & Troubleshooting
Good luck
Hello guys, I've a S6 Edge 32GB and I think I bricked it. I was just finished rooting, starting to mess with a camera mod and changed etc folder permission to rw- r-- r--. Since then my phone wouldn't boot. I have the TWRP and did a factory reset. It didn't help, as now it's saying I have no OS. I tried with Odin 3.10.6 to put the stock rom to no avail, since it gives me the following error -
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G925FXXU1AODG_G925FVFG1AOD1_G925FXXU1AODC_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin engine v(ID:3.1005)..
<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> SingleDownload.
<ID:0/006> sboot.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
On the phone screen after it fails, a line appears with the following details:
sw rev check fail device 3 binary 1
I also tried to install the md5 inside the zip file with the TWRP without success.
Thanks for the help in advance.
bump
It fails at Sboot, so you are flashing an old firmware and the phone wont accept it. Flash the latest BTU firmware.
Did u factory reset before flashing? Also it looks like your having the nand write start error there's a fix for it
https://www.google.com/url?sa=t&sou...LzW2Axxf0gwXh4lBA&sig2=HqewJZ5ldtkXUio9dAsQuQ
Also if u didn't reset here's what u do... Flash twrp recovery (not 3.0.0 I've heard it got some s6 bricked) then go to wipe, format data and format everything (will loose all data) then boot back into download mode and flash stock firmware
install Smart Switch
open smart switch > more > Emergency Software Recovery and initialization > device initialization
put your model name like below (example) put your model name
Model name : SM-G920F
click search
then put your S/N number (look the back of your phone) click ok and follow Smart Switch Instruction
Try flash via odin show fail..ALREADY VIEW ALOT YOURTUBE AND XDA..NOT FIX.. PRESS POWER + VOL BUTTON CAN'T ENTER RECOVER MODE. OR EMMC CHIP SPOIL? THANK
Pls help.
One use the report button and ask a mod to move the post to the correct section .Q&A
Try flash via odin show fail
What fail .
What are you flashing ??
JJEgan said:
One use the report button and ask a mod to move the post to the correct section .Q&A
Try flash via odin show fail
What fail .
What are you flashing ??
Click to expand...
Click to collapse
Because keep stuck on samsung logo. Can't go into recovery mode too. Suspect firmware corrupt. Fail show at 1st pic there Sboot.bin. So try re-flash stock rom, one of my htc problem like this after flash phone work as normal.
Some say this due to EMMC chip issue.
Pls help.
Try flashing a full firmware .
Full as in a single file
JJEgan said:
Try flashing a full firmware .
Full as in a single file
Click to expand...
Click to collapse
All already try. The pic 'FAIL" red color show in odin is single file(full firmware).
This case similar like my other HTC keep reboot in logo, htc after flash work as normal.
Alot of people facing same issue too, search around forum still unable to fix. Probably emmc.
Usual for Emmc fail is Odin fails at Nand write.
Sent from my SM-N930F using XDA-Developers Legacy app
JJEgan said:
Usual for Emmc fail is Odin fails at Nand write.
Sent from my SM-N930F using XDA- Legacy app
Click to expand...
Click to collapse
This note already problem quite some time, before that show the error below, at NAND Write start, so is EMMC problem, need replace the chip?
Also the battery charging bar not running, previously when charge will show the battery bar running.
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N8000XXUDPB1_N8000LUXDPB1_N8000XXUDNH1_HOME.tar.md 5 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)
This note already problem quite some time, before that show the error below, at NAND Write start, so is EMMC problem, need replace the chip?
Probably but ask a service centre .
Enter in download mode and try to flash any recovery cwm, twrp or philz with odin. See if now you're able to boot into recovery mode.
Enviado do meu GT-I9301I através de Tapatalk
skyx1128 said:
Try flash via odin show fail..ALREADY VIEW ALOT YOURTUBE AND XDA..NOT FIX.. PRESS POWER + VOL BUTTON CAN'T ENTER RECOVER MODE. OR EMMC CHIP SPOIL? THANK
Pls help.
Click to expand...
Click to collapse
I have the same problem but mine shows a error at system.img.
View attachment 5290635
And When I power it through the adaptor it shows the charging symbol and then it turns off. (As shown in the above image).
This happen when it ran out of charge for a day since then its been stuck with this logo. (As shown above).
Wrong firmware sys.img.
Wrong size PIT file .
JJEgan said:
Wrong firmware sys.img.
Wrong size PIT file .
Click to expand...
Click to collapse
I appreciate your help but I am new to all this and if you can explain things in detail would be helpful.
I have worked on xiaomi phones before but they use adb & fastboot to flash things, so I am a beginner for the flashing of samsung devices.
I downloaded the files from samobile and one more from other source and they are for the correct model as well.
This log is of the file download from the other source and was a single file.
Odin Log:
<ID:0/009> 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/009> Odin engine v(ID:3.1401)..
<ID:0/009> File analysis..
<ID:0/009> Total Binary size: 1764 M
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> NAND Write Start!!
<ID:0/009> SingleDownload.
<ID:0/009> system.img
<ID:0/009> FAIL!
<ID:0/009>
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/009> Removed!!
This log is of the file download from samobile with four different files.
Odin Log:
<ID:0/009> 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..
<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/009> Odin engine v(ID:3.1401)..
<ID:0/009> File analysis..
<ID:0/009> Total Binary size: 1765 M
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Set PIT file..
<ID:0/009> DO NOT TURN OFF TARGET!!
<ID:0/009>
<ID:0/009> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
In a post similar to this, someone mentioned that device stuck on logo could be due to a corrupted kernel.
Firmware is tied to the 16 or 32 Gb memory , check yours first.
JJEgan said:
Firmware is tied to the 16 or 32 Gb memory , check yours first.
Click to expand...
Click to collapse
Mine is the 16GB model and the firmware is also correct.
Probable
Flash stock but still custom rom
Hi folks , I installed cyanogenmod rom to my Samsung Galaxy Note 10.1 (GT-N8005) a year ago. It stuck on boot animation. Then I flash stock rom via odin , it passed. But still stuck on cyanogenmod boot animation. Can anyone help ? How can I...
forum.xda-developers.com
JJEgan said:
Probable
Flash stock but still custom rom
Hi folks , I installed cyanogenmod rom to my Samsung Galaxy Note 10.1 (GT-N8005) a year ago. It stuck on boot animation. Then I flash stock rom via odin , it passed. But still stuck on cyanogenmod boot animation. Can anyone help ? How can I...
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks for the help but I already checked this link and many others but the conclusion was when the error occurs at "NAND write" step then the emmc chip was probably damaged but mine stops at a different step. And also if I replace the emmc wouldn't I lose the data?
[RECOVERY][OFFICIAL] TWRP 3.6.0_9 [N8000 N8010 N8020]
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and...
forum.xda-developers.com
try flashing this twrp recovery, note use odin 3.10.5, note disable auto reboot, in options, after sucess reboot recovery, click flash, and see how big the internal storage is. If no sucess flashing twrp recovery or internal storage = 0MB your emmc is fried, else you device still has life.
If your device still has life install this custom android(LineageOS is just the UI name, it is stable android)(follow the steps)(ask @html6405 for questions, I can only help you to here)
LineageOS 16.0 Android 9 for GT-N8000 GT-N8010 GT-N8013 GT-N8020 FINAL VERSION EOL
/* * Your warranty is now void. * * I am not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. Please * do some research if you have any concerns about features included in...
forum.xda-developers.com
Hello everybody!!!
The Galaxy Note 10.1 GT-N8000 of my friend don't work again, when it's powered on it shows a message
In english
Encryption failure
Unable to complete the encryption due to an interruption, reset the factory data (operation which erases all your data) before use. After resetting, try encrypting the device again
There is a button to do that, but nothing it's happen when i click
Recovery mode is not accessible to wipe data.
I try to flash some stock ROMs with odine but the flash failed
Odine3 log
<ID:0/004> 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/004> Odin engine v(ID:3.1401)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 1787 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> NAND Write Start!!
<ID:0/004> SingleDownload.
<ID:0/004> boot.img
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Anyone can help me please
NOTE : Model number GT-N8000
I think you should manage to enter Recovery Mode to reset the factory data.
Its failing on boot image probably due to different/ later boot .
As said recovery mode and FORMAT system data etc .
Then Odin flash latest stock rom .