Samsung galaxy note 10.1 - Galaxy Note 10.1 Q&A, Help & Troubleshooting

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 .

Related

Galaxy note edge wiped and can't install any ROMS

hello all,
I'm a noob and i messed up my note edge. I rooted it on stock kk 4.4.4 rom from Rogers and installed superuser and twrp. I wanted to do a factory reset through the settings and reset and erase everything but it won't allow me to. Every time i select erase it would just do nothing. Do i thought I'd be smart and enter twrp by holding volume up, home, and power button then wipe everything. Now when i power on the phone it just boot loops with the original Samsung galaxy note edge splash screen. I am unable to find the original rom for my N915W8 Rogers phone so i read I'm done forums a T-Mobile rom should work. I downloaded a lollipop T-Mobile rom and tried to flash it with Odin but comes up as fail. I tried to put the zip file into my external micro sd card and use twrp to install and it failed again. Any help is greatly appreciated. My end goal is to be able to get the lollipop Rogers rom with root back on my phone.
Thanks
Enter Download Mode and use Odin to restore the stock ROM.
Thanks for the reply. I tried ODIN but unable to flash. It fails right away.
This is what I get:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N915TUVU1BOG2_N915TTMB1BOG2_N915TUVU1BOG2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1005)..
<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> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl1.mbn
<ID:0/004> rpm.mbn
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Any other clue? I think the problem is I have no data in my phone. I am thinking it needs some base to work off of. Please don't laugh at my logic lol.

Desperate help needed with soft/hard bricked Samsung GT-N7000

I am new to Andriod world. I was trying to down grade GT-N7000 from Android 4.1.2 to ICS 4.0.4. With my bad luck during the process while device in download mode and ODIN started the cable accidently got unplugged. Since then I am not able to get in to recovery mode and it keeps flashing "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again". I tried that but no luck as it asks for recovery code..serial and model number entries did not work. However, it can still get in download mode so I tried reflashing with ODIN and following is the log:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXLRK_N7000XXLRK_N7000ORALP2_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> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> cache.img
<ID:0/004> NAND Write Start!!
<ID:0/004> factoryfs.img
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
So that's where I am at this moment and hoping some of you experts can help me out to revive this phone. Please accept my advance thanks for taking the time to help.

Please help. Cant not unroot my sm s6.

Hi all,
I have Samsung Galaxy S6 G920F . I am trying to unroot my phone back to its factory settings. I downloaded the fimware and odin however i am getting below error message once i press the start in ODIN. I really dont have any idea what is going on. I tried different USB cables, frimware but didnt work out. Any help is highly appreciated . These are what i am getting ;
<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.1101)..
<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> SingleDownload.
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> cache.img
<ID:0/004> cm.bin
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<OSM> G920FXXU1AODE_G920FOXE1AODE_G920FXXU1AODE_HOME.tar .md5 is valid.
is this version of firmware lower than the one curently instaled.
i had similar problem
it appears that is was on portugal firmware G920FXXS4DPG2_G920FOXX3DPD1_TPH (latest update of 109MB) and was trying to downgrade to G920FXXU3DPDP_G920FOXX3DPD1_TWO ,and was getting error ''cm sw rev check fail device 4 binary 3''
and smart switch failed because my it was trying TWO_CRO with lower verion.

Help on T-mobile Note 5 SM-N920T failed to flash odin

I have this problem i cant reflash it on odin. Ive already rooted the device because when i get this it has a deep sleep issue so i fix it. After i rooted and install twrp recovery it works fine. But after i accidentally rooted again. It stuck up to boot loop t mobile logo.
Now when im flashin it on odin it say fails en recovery mode says.
SW REV. CHECK FAIL. DEVICE: 4 BINARY 3
Here is the log file i get from odin when im flashing a stock firmware on odin
GT-N920T T-mobile
Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N920TUVU3DPG1_N920TTMB3DPG1_N920TUVU3DPG1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1005)..
<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> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> cm.bin
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Somebody help me please? For this fix

[Q] Possibly bricked GT-N8010

Hey,
I was successfully running LineageOS on my GT-N8010.
However, it froze at one point and I force turned it off, and ever since I just get the 'Firmware upgrade encountered an issue' screen. However, I am still able to get into download mode.
I'm now wanting to get it back to stock so I can re-try LineageOS on it. I have the stock image but if I try to install through ODIN I just get an error(posted below) and also on the tablet I get SW Rev. Invalid magic string.
Any idea how I could try sort it out?
In the details section of the download screen it shows;
ODIN MODE
Product name: GT-N8010
Current Binary: Samsung official
System status: Custom
Log:
Code:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary 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.1100)..
<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> SingleDownload.
<ID:0/004> tz.img
<ID:0/004> NAND Write Start!!
<ID:0/004> sboot.bin
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Odin requires TAR files not image .
Flash stock rom via Odin .
Sboot.bin fail means you are flashing firmware with an older bootloader than is currently on the device .
JJEgan said:
Odin requires TAR files not image .
Flash stock rom via Odin .
Sboot.bin fail means you are flashing firmware with an older bootloader than is currently on the device .
Click to expand...
Click to collapse
Edit:
Looks like I didn't have the latest version, tried a newer one but it now gets stucks and after about 5mins of trying it stops at system.img;
Logs:
<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.1301)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 1746 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> sboot.bin
<ID:0/004> tz.img
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Stuck on system.img means odin not recognized your system partition..
And or change USB port change usb cable .
Make sure that you have the least official firmware for your device and if it still fails,
it looks like a eMMC failure.
This problem is very common on the N80XX devices.
I already had to replace hundreds of eMMC's on them.

Categories

Resources