Develop Bugs

Stuck on samsung screen and failed to mount /efs, /cache system...

Hello,
I have a galaxy note 2.
I am currently having big issues :
The phone get stuck on samsung galaxy note 2 screen
When I press Start / volume Up and Home, i get to this recovery mode where it says that /efs canno't be mount, same with /cache and /system (if i remember)
E: failed to mount /efs (No such file or directory)
E: failed to mount /system (No such file or directory)
E: failed to mount /cache (No such file or directory)
#MANUAL MODE #
--Applying Multi-CSC...
Applied the CSC-code: unknown
Successfully applied multi-CSC
I tried wipe / reset to factory option but it not working
For the historic, what I did on this phone :
1. I rooted it with odin CF-Auto-Root-t03g-t03gxx-gtn7100.tar.md5
2. Everything was fine during 1 year, then i had issue (phone crashing, settings reseting to default), so i decided to update the rom with the official one N7100XXUFND3_N7100OXAFND3_N7100XXUFND3_HOME.tar.md5
3. Since yesterday night the phone is stuck on home
4. I try to reflash with odin with the offical rom and i get this error
ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
I still have a backup of the EFS, i read that i should restore the EFS but I can't do it with ADB because when i type root shell in adb it says : "error : device not found" (I am in download mode though)
Thank you for your help

will kies help?

䙉ʐû said:
will kies help?
Click to expand...
Click to collapse
Hello, thank for your answer
Kies, doesn't detect my phone... I success to download the firmware with Kies but then it says that my phone is not accessible.
Odin detects my phone though.
I have installed samsung drivers,

Side54723 said:
Hello, thank for your answer
Kies, doesn't detect my phone... I success to download the firmware with Kies but then it says that my phone is not accessible.
Odin detects my phone though.
I have installed samsung drivers,
Click to expand...
Click to collapse
I have windows 8 by the way !

Side54723 said:
I have windows 8 by the way !
Click to expand...
Click to collapse
maybe you can try to flash a third-party recovery like CWM with odin and watch if it flashed successfully and if you can enter recovery. the recovery file is a normal tar.md5 which can be flashed like stock firmware.Drivers works well under windows 8 8.1even the newest windows10 tp

䙉ʐû said:
maybe you can try to flash a third-party recovery like CWM with odin and watch if it flashed successfully and if you can enter recovery. the recovery file is a normal tar.md5 which can be flashed like stock firmware.Drivers works well under windows 8 8.1even the newest windows10 tp
Click to expand...
Click to collapse
Where can i download it ? I have a french galaxy note 2 7100
Thank you,

Side54723 said:
Where can i download it ? I have a french galaxy note 2 7100
Thank you,
Click to expand...
Click to collapse
I tried to flash with CWM and odin fails on WIN7
The icon is blue (0:[COM8)
I selected "Note2-CWM-6.0.4.3-GT-N7100.tar" in PDA
<ID:0/008> Added!!
<ID:0/008> Removed!!
<ID:0/008> Added!!
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> recovery.img
<ID:0/008> NAND Write Start!!
<ID:0/008> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
Thanks for help

Side54723 said:
Where can i download it ? I have a french galaxy note 2 7100
Thank you,
Click to expand...
Click to collapse
You can search for it in the N7100 Android Development Forum ，there are many excellent recovery like CWM ，Philz and TWRP.Most of them work well on international N7100
---------- Post added at 11:14 AM ---------- Previous post was at 11:04 AM ----------
Side54723 said:
I tried to flash with CWM and odin fails on WIN7
The icon is blue (0:[COM8)
I selected "Note2-CWM-6.0.4.3-GT-N7100.tar" in PDA
<ID:0/008> Added!!
<ID:0/008> Removed!!
<ID:0/008> Added!!
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> recovery.img
<ID:0/008> NAND Write Start!!
<ID:0/008> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
Thanks for help
Click to expand...
Click to collapse
Make sure you have a good cable and use back USB(2.0) port if you are using a desktop.Maybe youcan try another recovery file and flash as many times as you can(someone said it would work)

䙉ʐû said:
You can search for it in the N7100 Android Development Forum ，there are many excellent recovery like CWM ，Philz and TWRP.Most of them work well on international N7100
---------- Post added at 11:14 AM ---------- Previous post was at 11:04 AM ----------
Make sure you have a good cable and use back USB(2.0) port if you are using a desktop.Maybe youcan try another recovery file and flash as many times as you can(someone said it would work)
Click to expand...
Click to collapse
Hello,
I tried CWM and philz with ODIN.
Maybe i should try from SD CARD ?
I changed 3 usb cable and I am using USB 2.0 (LAPTOP)

Side54723 said:
Hello,
I tried CWM and philz with ODIN.
Maybe i should try from SD CARD ?
I changed 3 usb cable and I am using USB 2.0 (LAPTOP)
Click to expand...
Click to collapse
That means you cant flash recovery either?

䙉ʐû said:
That means you cant flash recovery either?
Click to expand...
Click to collapse
I tried flashing with philz recovery, cwm, by odin or by sd card.
The sd card is not recognized (even after repartition it) => /Sdcard canno't be mount and i can't see any files
I also tried to update the rom + pit + repartition mais still failing in odin

hi,
i also have similar problem with my N7100.
phone stuck in Samsung GT-N7100 logo.
unable to go to Recovery Mode, but download mode OK.
tried to flash Stock Firmware with Odin, but failed
Code:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7100XXUFNI4_N7100OLBFNI1_N7100DXUFNI1_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> Firmware update start..
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
tried to flash PhilZ Touch 6 Recovery, but failed. :crying:
Code:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> philz_touch_6.48.4-n7100.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> SingleDownload.
<ID:0/005> recovery.img
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
from the log, it seem like Odin unable to write. anyone know whats the problem?
tried swap battery with friends, friends phone work well with my battery, but mine still the same even with my friends battery.

Side54723 said:
Hello,
I have a galaxy note 2.
I am currently having big issues :
The phone get stuck on samsung galaxy note 2 screen
When I press Start / volume Up and Home, i get to this recovery mode where it says that /efs canno't be mount, same with /cache and /system (if i remember)
E: failed to mount /efs (No such file or directory)
E: failed to mount /system (No such file or directory)
E: failed to mount /cache (No such file or directory)
#MANUAL MODE #
--Applying Multi-CSC...
Applied the CSC-code: unknown
Successfully applied multi-CSC
I tried wipe / reset to factory option but it not working
For the historic, what I did on this phone :
1. I rooted it with odin CF-Auto-Root-t03g-t03gxx-gtn7100.tar.md5
2. Everything was fine during 1 year, then i had issue (phone crashing, settings reseting to default), so i decided to update the rom with the official one N7100XXUFND3_N7100OXAFND3_N7100XXUFND3_HOME.tar.md5
3. Since yesterday night the phone is stuck on home
4. I try to reflash with odin with the offical rom and i get this error
ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
I still have a backup of the EFS, i read that i should restore the EFS but I can't do it with ADB because when i type root shell in adb it says : "error : device not found" (I am in download mode though)
Thank you for your help
Click to expand...
Click to collapse
Do these at your own risk.
search for PIT file made by dr ketan and flash it together with the stock n7100 firmware in odin. that will solve tour problem.
somebody posted pit file here.. be sure that your n7100 is 16gb
http://forum.xda-developers.com/show....php?t=1927983
extract it and use that together with the stock firmware in odin. select pit for pit files and pda for stock firmware
after finish flashing it will be stuck again in samsung logo. boot again to recovery mode and wipe data/reset to factory mode and then reboot

[Q] SGH-T999 soft-bricked in download mode only, Odin fails every time! Please help

SGH-T999 soft-bricked in download mode only, Odin fails every time! Please help me
I am new to forums and am in dire need of help. I have learned all that I know through google searches and spending at least 10 hours trying to solve this, so I need simple, easy-to-follow instructions.
I wanted to try experimenting with cyanogenmod so I tried using the one-click installer. On my wife’s galaxy s3 it failed but installed CWM and I think it removed GAAPS and booted up in stock touchwiz. After trying to get cyanogen on it and failing I decided to use Odin to get it back to factory settings and it worked!!
My Tmobile SGH-T999, however, is soft-bricked. I can't even get into simple recovery (volume up + power + home) but I can get into download mode. When I try booting it up normally, I get the message:
"firmware upgrade encountered an issue. Please select recovery mode in Kies and try again". The top left of the screen says:
Product name: GSH-T999
CUSTOM BINARY DOWNLOAD: NO
CURRENT BINARY: Samsung official
SYSTEM STATUS: Official
QUALCOMM SECUREBOOT: ENABLE
Warrenty Bit: 0
BOOTLOADER AP SWREV: 1
I've tried using Odin 3.07 to put the same firmware (from sammobile) that I used on my wife's phone. I tried flashing the firmware with the proper 16gb pit file and that also failed. I'm pretty sure the PIT file I have works because I didn't get an error message (an earlier attempt with a different PIT failed with a PIT error message on the phone).
Whenever I use Odin it completes 99% of the way and give me this error message (at the end)
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T999UVUENC2_T999TMBENC2_T999UVUENC2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Successfully..
<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> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl3.mbn
<ID:0/003> aboot.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> NON-HLOS.bin
<ID:0/003> cache.img.ext4
<ID:0/003> FAIL! (Write)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
I've installed the latest samsung USB drivers, got from sammobile.com the latest firmware (for 4.3) and put it in the PDA slot, got what seems to be an accurate PIT file. I'm using a new USB cable. It worked for my wife's galaxy s3 but I have no idea how to make it pass!
I sincerely hope that you can help me.
warmly,
-Bryce J
PM me if you want to chat, text, or call me!

What did you do to yours to get it softbricked in the first place? Did you ever update to a 4.4 ROM? You are trying 4.3 and if you ever updated to 4.4 bootloaders/modem, then you can't go down to 4.3
Did you buy your phone new, or used online? A lot of used phones are some bastardized hybrid i747 and t999 parts.

sameboat
I'm having something similar. I'm just trying to get to factory reset but can't even get to recovery mode.

Simple fix. Download the stock firmware and boot into Download mode. Follow the Odin tutorial and you should be fine.

[Q] Black Screen of Death after flashing Stock-Rom with Odin

Hi everybody,
i have same problems with the Stock-Rom of Lolipop with VD2-Branding.
ODIN has faild with:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T805XXU1BOCC_T805VFG1BOC4_T805XXU1BOC1_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> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004> modem.bin
<ID:0/004> cache.img
<ID:0/004> hidden.img
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Now i have a "Black Screen of Death".
The ROM: VD2-T805XXU1BOCC-20150403134302.zip
Odin: 3.10.6
Hardware: Samsung Galaxy Tab S LTE 16GB (SM-T805) from Vodafone D2 Germany
Flashing with TWRP also failed. Is it possible, that i use the wrong image?
Edit: Now it works, but the way was very terrible. Odin flashing till error. Following this i have flash the Recovery TWRP. Now the Tablet has booted, but i disbelieve it works fine.
Can someone help me to install the offiicial Rom correctly?
Thanks a lot and have a nice day!
best regards masterkifke

Masterkifke said:
T805XXU1BOCC_T805VFG1BOC4_T805XXU1BOC1_HOME.tar.md5
Click to expand...
Click to collapse
Masterkifke said:
VD2-T805XXU1BOCC-20150403134302.zip
Click to expand...
Click to collapse
Masterkifke said:
Hardware: Samsung Galaxy Tab S LTE 16GB (SM-T805) from Vodafone D2
Click to expand...
Click to collapse
Does your SM-T805 have a letter after the model? Like C, M, W or Y?
If not, then when I search www.sammobile.com for your firmware, this is the download file name I find that you should be using. I am not sure what the file name will be after extracting the zip though. Would take five hours of downloading for me to find out.
But if you compare this name to the file you originally downloaded and it is the same, then I think you are flashing the correct firmware.
T805XXU1BOCC_T805VFG1BOC4_VD2.zip

Ignore the error then boot into recovery and wipe cache.
Job done.

Thanks for help.
The device comes without an extension like C , M, W or Y and the ROM is from sammobile. So i think the ROM is correct.
But the problem is after flashing and getting the error, i don't have any access to recovery and for wipe the cache -> POWER + VOLUME UP + HOME goes directly into "Back Screen of Death".
So i must install TWRP before.
But my target is to the device bringing back into factory state.
At the moment it works fine.
Thank you for help.
best regards from germany
masterkifke

It won't boot if you don't have a valid recovery installed. Flashing stock firmware always installs stock recovery.
So either reflash stock firmware, flash stock recovery or flash twrp.
However I can quite clearly see from your first post that recovery has flashed fine, so it seems the problem is you are not using the right timing and button combo to enter recovery mode.
Many people have encountered the hidden.img fail when flashing a different region firmware as its csc specific.
All you need do to solve it is enter recovery mode and wipe cache.

Samsung T550 Galaxy Tab A - Can I unlock this thing?

Hi everyone,
I have a Galaxy Tab A which was given to me in work. It was supposed to be used for a specific purpose but after a year or so they decided it wasn't needed (it's never actually been used).
Here's the problem(s).
1. It has MobiControl installed on it which is blocking ALL apps and settings. I can't get in to settings to allow USB Debug etc so I can't flash a different ROM. It's not been used for so long nobody can remember the password for MobiControl and the guy who set it up has moved on, never to be heard of again.
2. When I try to hard reset from Recovery i get an error "MDM does not allow factory Reset. Phone will REBOOT automatically".
I have tried to use Odin but, without allowing USB Debug I don't think I can actually do anything??
I would appreciate any ideas if anyone has any. It's such a shame to just throw it in the bin but at the moment that looks quite likely
Thanks
Stuart

When using Odin, you don't need to check USB debug. Hold power, volume down and home button to get to the first screen, then volume up to Download Mode.
Download your firmware from sammobile then using Odin to flash it in download mode, then you may get rid of this app.

Thanks for the reply. I tried to do this a couple of nights ago but it would always fail. I assumed because USB Debugging wasn't enabled but maybe it's because the app is blocking it?? I'll try again tonight maybe and post the error if it comes back up.
Another possible issue could be that i'm not sure which firmware to use. It's possible the tablet isn't originally a UK device so would that matter? Which one would you recommend I use? https://www.sammobile.com/firmwares/galaxy-tab-a/SM-T555/
(apologies, my subject does say SM-T550 but it is the T555 LTE version).
Many thanks
Stuart

Try installing TWRP then FORMAT the Data partition using the (FORMAT DATA BUTTON)
Reboot to download mode immediately from TWRP and then install the stock firmware with ODIN.

ashyx said:
Try installing TWRP then FORMAT the Data partition using the (FORMAT DATA BUTTON)
Reboot to download mode immediately from TWRP and then install the stock firmware with ODIN.
Click to expand...
Click to collapse
Thanks for the idea but I have 2 problems.
1. I can't seem to find a TWRP download for my tablet. https://twrp.me/Devices/Samsung/ shows Galaxy Tab A but it doesn't have a 9.7 inch option.
2. To install TWRP wouldn't I need to get in to my settings to allow enable OEM unlock? I can't access settings so that's not going to happen.
I just tried to install firmware using Odin but It doesn't work. I get the following:
<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.1203)..
<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> sbl1.mbn
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

jimmisavage said:
Thanks for the idea but I have 2 problems.
1. I can't seem to find a TWRP download for my tablet. https://twrp.me/Devices/Samsung/ shows Galaxy Tab A but it doesn't have a 9.7 inch option.
2. To install TWRP wouldn't I need to get in to my settings to allow enable OEM unlock? I can't access settings so that's not going to happen.
I just tried to install firmware using Odin but It doesn't work. I get the following:
<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.1203)..
<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> sbl1.mbn
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
You need my builds of TWRP below:
https://forum.xda-developers.com/galaxy-tab-a/development/recovery-t3426560
Also it looks like you are flashing the wrong firmware.
Post a link to the firmware you are attempting to flash and screen shot of odin.
Either way you will need to flash twrp first.
Also the T555 doesn't need OEM UNLOCK enabling.

ashyx said:
You need my builds of TWRP below:
https://forum.xda-developers.com/galaxy-tab-a/development/recovery-t3426560
Also it looks like you are flashing the wrong firmware.
Post a link to the firmware you are attempting to flash and screen shot of odin.
Either way you will need to flash twrp first.
Also the T555 doesn't need OEM UNLOCK enabling.
Click to expand...
Click to collapse
Thank you. I'll try and install your version now.
The firmware i was using is https://www.sammobile.com/firmwares/...tab-a/SM-T555/
I didn't know which one to use so i chose the UK Vodafone one. I'm not sure which is the correct one though.

I just tried to install TWRP but get an error again. I tried lollipop and marshmallow and no luck with either
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1203)..
<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> recovery.img
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

jimmisavage said:
I just tried to install TWRP but get an error again. I tried lollipop and marshmallow and no luck with either
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1203)..
<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> recovery.img
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Can you boot to Download (odin) mode and post a screen shot of the details it displays.
Just for info I have the T555 model also.
It maybe that your device is locked so won't flash any firmware. If it IS a Vodafone device your bootloader will be locked and you've no chance of flashing anything except official firmware.

ashyx said:
You need my builds of TWRP below:
https://forum.xda-developers.com/galaxy-tab-a/development/recovery-t3426560
Also it looks like you are flashing the wrong firmware.
Post a link to the firmware you are attempting to flash and screen shot of odin.
Either way you will need to flash twrp first.
Also the T555 doesn't need OEM UNLOCK enabling.
Click to expand...
Click to collapse
ashyx said:
Can you boot to Download (odin) mode and post a screen shot of the details it displays.
Just for info I have the T555 model also.
It maybe that your device is locked so won't flash any firmware. If it IS a Vodafone device your bootloader will be locked and you've no chance of flashing anything except official firmware.
Click to expand...
Click to collapse
Thanks for taking the time to help! Here's a picture...

jimmisavage said:
Thanks for taking the time to help! Here's a picture...
Click to expand...
Click to collapse
Do you know if this device is a carrier version or the international version?
Is there a serial on the back. I'd email this to me not post it.

ashyx said:
Do you know if this device is a carrier version or the international version?
Is there a serial on the back. I'd email this to me not post it.
Click to expand...
Click to collapse
I've just emailed you.
I'm not sure if it's a carrier version or the international version. I'm not even sure if it's originally a UK model.

jimmisavage said:
I've just emailed you.
I'm not sure if it's a carrier version or the international version. I'm not even sure if it's originally a UK model.
Click to expand...
Click to collapse
Well don't flash anything carrier related. Just flash the regular firmware.
I haven't received your mail so I've pm'd you.
EDIT. never mind got it now.
---------- Post added at 06:08 PM ---------- Previous post was at 05:40 PM ----------
jimmisavage said:
I've just emailed you.
I'm not sure if it's a carrier version or the international version. I'm not even sure if it's originally a UK model.
Click to expand...
Click to collapse
Sorry, when I said serial I should have said the model number on the back as well.
You can post that here.

ashyx said:
Well don't flash anything carrier related. Just flash the regular firmware.
I haven't received your mail so I've pm'd you.
EDIT. never mind got it now.
---------- Post added at 06:08 PM ---------- Previous post was at 05:40 PM ----------
Sorry, when I said serial I should have said the model number on the back as well.
You can post that here.
Click to expand...
Click to collapse
Do you mean IMEI number? I don't see a model number

jimmisavage said:
Do you mean IMEI number? I don't see a model number
Click to expand...
Click to collapse
I've messaged you all the details on the back of the tablet

jimmisavage said:
I've messaged you all the details on the back of the tablet
Click to expand...
Click to collapse
From what I can gather it's non carrier locked model.
Have you tried to flash the stock UK firmware? The code is BTU
http://updato.com/firmware-archive-select-model?record=3EFD4C401EE211E7963AFA163EE8F90B
Also which TWRP version did you try to flash?

I'll try and flash that one this evening.
I tried 2 TWRP versions.
twrp_3.0.2-1_SM-P550_mm_15816
and
http://www.androidfilehost.com/?fid=24052804347801971

jimmisavage said:
I'll try and flash that one this evening.
I tried 2 TWRP versions.
twrp_3.0.2-1_SM-P550_mm_15816
and
http://www.androidfilehost.com/?fid=24052804347801971
Click to expand...
Click to collapse
Nope, you're flashing the wrong versions.
You have a T555 running Marshmallow as far as I'm aware. You need the one below:
https://www.androidfilehost.com/?fid=529152257862710020

Don't I feel stupid! I'll try and flash both tonight and will let you know the outcome.
Thanks again for all your help.

Nope - Neither will work.
On the tablet is says MDM MODE. CAN'T DOWNLOAD (in red letters)
and on in Odin I get:
<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.1203)..
<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> sbl1.mbn
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I guess that's pretty much the end of it?

Need help un-bricking my kids tab 3 7.0 SM-T210R...

Hi guys, bit of a noob here...I messed up my kids tablet.
It was running NoleKat 2.X, previous to that was running stock 4.4.2.
In an effort to get tablet back to stock to clear up some bootloop issues - used odin to flash stock 4.1.2 it worked no problem except Samsung update to 4.4.2 would no longer work...
so I break out odin again and grab what I think is the right stock 4.4.2 Rom from sammobile....try to flash it, it fails and now tablet only boots straight into recovery <3e>.
I tried wipes from recovery they all fail due to some make_extf4fs failed on dev block.
adb sideload will crash when ROM transfer gets to about 70%.
tablet will not take any other ADB commands
Smart switch and Kies will not reconize tablet say its unsupported - works fine on another tablet.
I can get it into odin mode but odin will fail no matter what I try and flash...works fine to flash second tablet I have.
Any suggestions or do I need a new tablet.
Plaz

I think what happened is due to the bootloader...it was different on JB, so the KK rom won't boot on it without the KK bootloader. Did you try to flash @gr8nole TWRP? If you can get it to flash, you may be able to recover it.
Sent from my KYOCERA-C6745 using Tapatalk

RealWelder said:
I think what happened is due to the bootloader...it was different on JB, so the KK rom won't boot on it without the KK bootloader. Did you try to flash @gr8nole TWRP? If you can get it to flash, you may be able to recover it.
Sent from my KYOCERA-C6745 using Tapatalk
Click to expand...
Click to collapse
Let me try that using odin - if its a bootloader issue should I not be able to flash JB stock then? should I try it if TWRP is a no go?
Thanks
Plazomat

plazomat said:
Let me try that using odin - if its a bootloader issue should I not be able to flash JB stock then? should I try it if TWRP is a no go?
Thanks
Plazomat
Click to expand...
Click to collapse
I would. Also, it's possible that your download became corrupted, might try redownloading stock from SamMobile again. I think we can probably get it going, though. There is still hope. Lol
Sent from my KYOCERA-C6745 using Tapatalk

RealWelder said:
I would. Also, it's possible that your download became corrupted, might try redownloading stock from SamMobile again. I think we can probably get it going, though. There is still hope. Lol
Sent from my KYOCERA-C6745 using Tapatalk
Click to expand...
Click to collapse
So when I flash twrp 2.8.0 it , the progress bar goes all the way green then fails after a few seconds here is the oding log...
<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/003> Odin engine v(ID:3.1203)..
<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> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Thanks for any help RealWelder...
Plaz

And when I try to flash a jelly bean stock rom it fails almost instantly....and log is as such..
<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/003> Odin engine v(ID:3.1203)..
<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> SingleDownload.
<ID:0/003> boot.img
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Plaz

plazomat said:
And when I try to flash a jelly bean stock rom it fails almost instantly....and log is as such..
<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/003> Odin engine v(ID:3.1203)..
<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> SingleDownload.
<ID:0/003> boot.img
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Plaz
Click to expand...
Click to collapse
One more thing I should add - not sure if it makes any difference but I never get the android picture just before I get into odin mode....I need to time it, waiting for the backlight to come up, release home/power/volume down, then tap volume up and I get the odin mode text information only - never a picture.
Odin will only attempt to flash once from a fresh entry into recovery - once it fails...if I just try again it won't get past getting PIT table and pukes that PIT is missing or something like that - I will see if I can post that log as well..
PLAZ

plazomat said:
One more thing I should add - not sure if it makes any difference but I never get the android picture just before I get into odin mode....I need to time it, waiting for the backlight to come up, release home/power/volume down, then tap volume up and I get the odin mode text information only - never a picture.
Odin will only attempt to flash once from a fresh entry into recovery - once it fails...if I just try again it won't get past getting PIT table and pukes that PIT is missing or something like that - I will see if I can post that log as well..
PLAZ
Click to expand...
Click to collapse
Hi i have the same problem can u help me pls?

Making some progress i think....I found rootjunky's link to odin 3.07 and at least it does not "fail" right away.
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> recovery.img
<ID:0/003> PBL.bin
<ID:0/003> param.lfs
<ID:0/003> loke_2nd.bin
<ID:0/003> loke_pxa988.bin
<ID:0/003> system.img
<ID:0/003> cache.img
<ID:0/003> hidden.img
<ID:0/003> radio.img
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Problem is no matter what stock rom or custom recovery i flash - tablet always always always reboots to samsung ( I think) recovery....
Plaz

plazomat said:
Making some progress i think....I found rootjunky's link to odin 3.07 and at least it does not "fail" right away.
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> recovery.img
<ID:0/003> PBL.bin
<ID:0/003> param.lfs
<ID:0/003> loke_2nd.bin
<ID:0/003> loke_pxa988.bin
<ID:0/003> system.img
<ID:0/003> cache.img
<ID:0/003> hidden.img
<ID:0/003> radio.img
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Problem is no matter what stock rom or custom recovery i flash - tablet always always always reboots to recovery....
Plaz
Click to expand...
Click to collapse
I use Odin 3.04, if that helps. In the past I've bricked mine a number of times and have always managed to fix it. Once I encountered a similar situation, where basically the system partition was shrunk from 1.4gb to 1.2gb and Odin would fail everything because of it. I was lucky enough to still have TWRP, so I used it to flash my rom's flashable zip and that fixed it. I think we need to get back to total stock 4.2.2 and then reupgrade to 4.4.2. Or we need to get TWRP to flash... Can you open up a terminal shell anywhere and get root? If so we could manually flash TWRP.
Sent from my KYOCERA-C6745 using Tapatalk

RealWelder said:
I use Odin 3.04, if that helps. In the past I've bricked mine a number of times and have always managed to fix it. Once I encountered a similar situation, where basically the system partition was shrunk from 1.4gb to 1.2gb and Odin would fail everything because of it. I was lucky enough to still have TWRP, so I used it to flash my rom's flashable zip and that fixed it. I think we need to get back to total stock 4.2.2 and then reupgrade to 4.4.2. Or we need to get TWRP to flash... Can you open up a terminal shell anywhere and get root? If so we could manually flash TWRP.
Sent from my KYOCERA-C6745 using Tapatalk
Click to expand...
Click to collapse
I can try using Odin 3.04 see if that helps at all...
I have tried using ABD commands from my PC in powershelll and a CMD window, but the only time it responds to anything is when I put it into ADB sideload mode from the "recovery".
I will try to flash a stock 4.2.2 with Odin 3.04 and report back.
Is there anyway to Odin Flash your ROM?
Thanks for help Real Welder
Plaz

plazomat said:
I can try using Odin 3.04 see if that helps at all...
I have tried using ABD commands from my PC in powershelll and a CMD window, but the only time it responds to anything is when I put it into ADB sideload mode from the "recovery".
I will try to flash a stock 4.2.2 with Odin 3.04 and report back.
Is there anyway to Odin Flash your ROM?
Thanks for help Real Welder
Plaz
Click to expand...
Click to collapse
I tried to do an Odin flashable before and it passed and everything, but once the ROM booted up it wouldn't connect to the pc anymore via mtp. I could try to upload one and if it boots up we can flash TWRP and then my ROM and everything will work correctly. The main thing is just getting out of the loop. Report back on the 4.2 flash, meanwhile I'll try to get an Odin flashable for you to try.
Here is my ROM in Odin format. Hope it helps!
https://drive.google.com/file/d/1g6sM4l--bYqIGrzeUu0aMEEc0vBmQwga/view?usp=drivesdk
Sent from my KYOCERA-C6745 using Tapatalk

RealWelder said:
I tried to do an Odin flashable before and it passed and everything, but once the ROM booted up it wouldn't connect to the pc anymore via mtp. I could try to upload one and if it boots up we can flash TWRP and then my ROM and everything will work correctly. The main thing is just getting out of the loop. Report back on the 4.2 flash, meanwhile I'll try to get an Odin flashable for you to try.
Here is my ROM in Odin format. Hope it helps!
https://drive.google.com/file/d/1g6sM4l--bYqIGrzeUu0aMEEc0vBmQwga/view?usp=drivesdk
Sent from my KYOCERA-C6745 using Tapatalk
Click to expand...
Click to collapse
Thanks RealWelder you are awesome to still be supporting these old beaters - gonna try this in the morning when I get some time....
Plaz

Did either of you have any luck?
Sent from my KYOCERA-C6745 using Tapatalk

RealWelder said:
Did either of you have any luck?
Sent from my KYOCERA-C6745 using Tapatalk
Click to expand...
Click to collapse
Sorry Real - I haven't got a chance to try it - life got in the way...been itching to get this moving again...plan is to attempt it later today..
I read that the kernel may have to be flashed with something like the blackhawk kernel...because this tab was once upgraded to 4.4.2 and I went back to a 4.1.2 stock rom...any opinons on if I should bother with that first? or at all?
Thanks so much for the help.
Plaz

plazomat said:
Sorry Real - I haven't got a chance to try it - life got in the way...been itching to get this moving again...plan is to attempt it later today..
I read that the kernel may have to be flashed with something like the blackhawk kernel...because this tab was once upgraded to 4.4.2 and I went back to a 4.1.2 stock rom...any opinons on if I should bother with that first? or at all?
Thanks so much for the help.
Plaz
Click to expand...
Click to collapse
Couple things to keep in mind here:
If the full 4.4.2 firmware was flashed to the device at any point, then the bootloader was updated. The 4.4.2 bootloader needs to have the stock 4.4.2 recovery or one of the custom recoveries that has the "recovery bootloop" fix. The most recent TWRP will work.
The 4.4.2 bootloader looks for a signal that the recovery session is complete before it will boot into the OS properly. Older 4.1.2 recoveries do not provide this "recovery complete" signal, so it gets stuck in the recovery bootloop.
This may or may not be useful in your case as I admit that I didn't read this whole thread.

gr8nole said:
Couple things to keep in mind here:
If the full 4.4.2 firmware was flashed to the device at any point, then the bootloader was updated. The 4.4.2 bootloader needs to have the stock 4.4.2 recovery or one of the custom recoveries that has the "recovery bootloop" fix. The most recent TWRP will work.
The 4.4.2 bootloader looks for a signal that the recovery session is complete before it will boot into the OS properly. Older 4.1.2 recoveries do not provide this "recovery complete" signal, so it gets stuck in the recovery bootloop.
This may or may not be useful in your case as I admit that I didn't read this whole thread.
Click to expand...
Click to collapse
Thanks gr8nole - tried flashing the 3.0.0 TWRP still no joy - keeps booting into stock (ithink) recovery. I pulled it from your file repo on Android file host.
I say I think cause the font is so big and the display is in landscape mode.
Plaz

RealWelder said:
Did either of you have any luck?
Sent from my KYOCERA-C6745 using Tapatalk
Click to expand...
Click to collapse
Gave it a go with your ROM...still recovery boot loop as suggested by gr8nole.
Here is log..
<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> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> system.img
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Thanks again
Plaz

Hi Gents, still messing with this when I have time and no joy...
Can't get a custom recovery to stick, odin flashes file but when device reboots just goes back to stock recovery...
Any clues.
Plaz