Stuck a Teamwin-logo, cant go into recovery mode - Galaxy Tab S Q&A, Help & Troubleshooting

I flashed my Galaxy Tab S 8.4 a while ago with TWRP and installed CM12. Worked fine until a couple of days ago when I turned on the tablet. It got stuck on the Teamwin-logo and I cant do anything what so ever... Cant turn it off, reboot, go into recovery etc no matter what I do. Even if I let the battery die out the **** starts again as soon as I turn it on again. Can this be fixed and if so, how? Thanks a bunch!

Put it into download mode and reflash twrp.
Hold HOME +VOL DOWN +POWER in that order until download mode appears.

ashyx said:
Put it into download mode and reflash twrp.
Hold HOME +VOL DOWN +POWER in that order until download mode appears.
Click to expand...
Click to collapse
Well, that worked but now I´m stuck at "Downloading... Do not turn off the target!" instead. *sigh*

Lunaspice78 said:
Well, that worked but now I´m stuck at "Downloading... Do not turn off the target!" instead. *sigh*
Click to expand...
Click to collapse
Well of course it worked. You have to flash TWRP!

ashyx said:
Well of course it worked. You have to flash TWRP!
Click to expand...
Click to collapse
How am I suppose to flash it when I cant get any further than "Downloading..." ?

Lunaspice78 said:
How am I suppose to flash it when I cant get any further than "Downloading..." ?
Click to expand...
Click to collapse
Because that's how you flash twrp. Am I missing something here? :what:
How did you flash twrp the first time?
Also no need to create new threads on the same issue.

ashyx said:
Because that's how you flash twrp. Am I missing something here? :what:
How did you flash twrp the first time?
Also no need to create new threads on the same issue.
Click to expand...
Click to collapse
I did just like that... going into download mode. But as I said, when I go into download mode I get stuck at "Downloading... Do not turn off target!" I cant get any further. The only thing to do is a reboot -> power + vol up and down which results in being stuck in another TWRP-loop. When ever I try to enter recovery mode by power + home + vol up, either when in the TWRP-boot screen loop or when being stuck in the download mode nothing happens. Oh, and also... I cant turn off my device. I try to empty its batteries and when I plug in the charger it boots up and gets stuck at looping the TWRP-logo.
Sorry for the doublepost.

OK I'm a little confused so please clarify.
You put the tablet in download mode. You plug in the usb cable and you see the added message in Odin?
You then load twrp into the AP slot and press start to begin flashing.
Now are you saying here nothing happens, no flashing at all? What does odin do, can you post a screen shot?

ashyx said:
OK I'm a little confused so please clarify.
You put the tablet in download mode. You plug in the usb cable and you see the added message in Odin?
You then load twrp into the AP slot and press start to begin flashing.
Now are you saying here nothing happens, no flashing at all? What does odin do, can you post a screen shot?
Click to expand...
Click to collapse
No no... I dont even get to the point where I can load TWRP etc. This is what it looks like:
http://img.wonderhowto.com/img/00/3...ndows-so-easy-your-grandma-can-do-it.w654.jpg
Not my picture, just trying to illustrate. It has been like this for several hours now and the only thing I can do from here is reboot the device (POWER + vol up + down) which puts the device back in TWRP-boot loop or I can put it in download mod again (POW + HOME + vol down). If I do that the same screen appears and I´m stuck again. No way to enter recovery mode, boot into to the OS or anything.

Hi,
Same problem.
Tried solution above to re-flash TWRP/CWM via Odin.
File with recovery (.tar) successfuly sent to phone in Dwonload mode from Odin but after reboot still stuck on Teamwin logo.
Any other advice?
P.S. Phone stuck after Factory reset attempt from Settings menu.
Odin log:
<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/003> Added!!
<ID:0/003> Odin engine v(ID:3.1100)..
<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> 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)

Well, you dont have the same problem because you actually have the option to flash which I dont. I´m stuck at the screen showed in the screenshot in the above post.

no... I dont even get to the point where I can load TWRP etc. This is what it looks like:
http://img.wonderhowto.com/img/00/3...ndows-so-easy-your-grandma-can-do-it.w654.jpg
Not my picture, just trying to illustrate. It has been like this for several hours now and the only thing I can do from here is reboot the device (POWER + vol up + down) which puts the device back in TWRP-boot loop or I can put it in download mod again (POW + HOME + vol down). If I do that the same screen appears and I´m stuck again. No way to enter recovery mode, boot into to the OS or anything.
Click to expand...
Click to collapse
I don't understand what you're saying here. That's the screen EVERYBODY sees when installing firmware.
What else are you expecting to see? :what:
Put it in download mode. When you see that screen start up odin, load twrp into the AP slot. Plug in the usb cable, wait for the added message in Odin then hit start.
That's it twrp will then flash.
---------- Post added at 09:41 AM ---------- Previous post was at 09:36 AM ----------
xronofag said:
Hi,
Same problem.
Tried solution above to re-flash TWRP/CWM via Odin.
File with recovery (.tar) successfuly sent to phone in Dwonload mode from Odin but after reboot still stuck on Teamwin logo.
Any other advice?
P.S. Phone stuck after Factory reset attempt from Settings menu.
Odin log:
<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/003> Added!!
<ID:0/003> Odin engine v(ID:3.1100)..
<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> 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)
Click to expand...
Click to collapse
According to that nothing flashed, did you flash using the AP slot?

ashyx said:
I don't understand what you're saying here. That's the screen EVERYBODY sees when installing firmware.
What else are you expecting to see? :what:
Put it in download mode. When you see that screen start up odin, load twrp into the AP slot. Plug in the usb cable, wait for the added message in Odin then hit start.
That's it twrp will then flash.
---------- Post added at 09:41 AM ---------- Previous post was at 09:36 AM ----------
According to that nothing flashed, did you flash using the AP slot?
Click to expand...
Click to collapse
I tried in AP first and then in BL. Both results are the same. Nothing changes.
Here is the same for BL slot. What I am doing wrong?
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1100)..
<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> 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)

xronofag said:
I tried in AP first and then in BL. Both results are the same. Nothing changes.
Here is the same for BL slot. What I am doing wrong?
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1100)..
<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> 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)
Click to expand...
Click to collapse
Please post me a screenshot shot of odin after the flash and the firmware you are flashing.
Only use AP nothing else.

I´m so sorry ashyx for have taken up your time. I feel like a retard. I figured out what I was doing wrong (and I´m not gonna tell you how stupid that was) and now my device works just fine. Thanks for your help anyway!

ashyx said:
Please post me a screenshot shot of odin after the flash and the firmware you are flashing.
Only use AP nothing else.
Click to expand...
Click to collapse
Forum does not allow me to post images as my account has low rights.
Before flash --- http ://s15.postimg.org/74jen6ukr/screen_odin_1.png
After flash --- http ://s29.postimg.org/4te6j5zg7/screen_odin_2.png
twrp-2.8.6.1-i9300.tar from official download page

Lunaspice78 said:
I´m so sorry ashyx for have taken up your time. I feel like a retard. I figured out what I was doing wrong (and I´m not gonna tell you how stupid that was) and now my device works just fine. Thanks for your help anyway!
Click to expand...
Click to collapse
Come on spill the beans, we all do daft things.
Don't keep me hanging! :sly:
---------- Post added at 07:38 PM ---------- Previous post was at 07:34 PM ----------
xronofag said:
Forum does not allow me to post images as my account has low rights.
Before flash --- http ://s15.postimg.org/74jen6ukr/screen_odin_1.png
After flash --- http ://s29.postimg.org/4te6j5zg7/screen_odin_2.png
twrp-2.8.6.1-i9300.tar from official download page
Click to expand...
Click to collapse
Can I ask why you are trying to flash TWRP for the GALAXY S3 and not TWRP for the TAB S? :what:
Surely you should be flashing this:
http://forum.xda-developers.com/showthread.php?t=3074633

ashyx said:
Come on spill the beans, we all do daft things.
Don't keep me hanging! :sly:
---------- Post added at 07:38 PM ---------- Previous post was at 07:34 PM ----------
Can I ask why you are trying to flash TWRP for the GALAXY S3 and not TWRP for the TAB S? :what:
Surely you should be flashing this:
http://forum.xda-developers.com/showthread.php?t=3074633
Click to expand...
Click to collapse
OMG just noticed the thread in on Tab S2. Well I have the problem with Galaxy S3 GT-i9300.
Any luck that I can still get help in this thread? If not, thanks anyways for the time and consideration. Appreciate it.

xronofag said:
OMG just noticed the thread in on Tab S2. Well I have the problem with Galaxy S3 GT-i9300.
Any luck that I can still get help in this thread? If not, thanks anyways for the time and consideration. Appreciate it.
Click to expand...
Click to collapse
Flash the stock firmware this will clear the command that is stuck in cache causing the issue.
For future reference never try to factory reset from android without original recovery.

ashyx said:
Flash the stock firmware this will clear the command that is stuck in cache causing the issue.
For future reference never try to factory reset from android without original recovery.
Click to expand...
Click to collapse
Thanks. This is still an issue for me.
I only know how to flash from recovery(reboot to recovery choose ROM from internal FLASH etc) but the problem is that I can not enter the recovery mode. I am stuck in this cyclic TeamWin logo. Do you know how to act in such case top proceed wtih stock ROM flashin as advised above?

Related

Help with Samsung Galaxy

I have a Sprint Galaxy S II 4G Touch, I rooted with Odin SPH-D710.EL_29CL852097_ROOTED_NODATA program. The phone worked fine. I then tried to unroot the phone using Odin v. 1.85 twith the PIT file that came with it and the Stock_EK02.Tar file. I accidently inserted the Tar file into the BOOTLOADER, PDA AND PHONE boxes. Now my phone is stuck in the Galaxy S II screen, however I can get to Odin recovery mode. Is there anyway to reclaim any usage from my phone. Please Help...
Reboot on download mode and install one of the sfhub one click roms the el29 might need good for you.
Sent from my SPH-D710 using xda premium
By reboot I mean take the battery off put it back on hold volume down and power button at the same time then when you see a choice press volume up the install the one click roms from sfhub they are great
Sent from my SPH-D710 using xda premium
RN69 said:
I have a Sprint Galaxy S II 4G Touch, I rooted with Odin SPH-D710.EL_29CL852097_ROOTED_NODATA program. The phone worked fine. I then tried to unroot the phone using Odin v. 1.85 twith the PIT file that came with it and the Stock_EK02.Tar file. I accidently inserted the Tar file into the BOOTLOADER, PDA AND PHONE boxes. Now my phone is stuck in the Galaxy S II screen, however I can get to Odin recovery mode. Is there anyway to reclaim any usage from my phone. Please Help...
Click to expand...
Click to collapse
Download the one-click option and follow the steps outlined by sfhub. It will restore your phone to a stock out of the box state.
Reboot
When I do the reboot via battery out volume down with power button, I get a screen that has ODIN MODE in red at top left. Below that in white is PRODOCUT NAME: SPH-0710,CUSTOM BINARY DOWNLOAD: NO, CURRENT BINARY: SAMSUNG OFFICIAL. Below that the green Android robot. Below that Downloading... Do not turn target off!! No other options. The only way to install is from a file from the computer... can I install the hub file from computer and do I do with odin? The Galaxy S II screen and this reboot are the only options I can get too. Your help is greatly appreciated.
RN69 said:
When I do the reboot via battery out volume down with power button, I get a screen that has ODIN MODE in red at top left. Below that in white is PRODOCUT NAME: SPH-0710,CUSTOM BINARY DOWNLOAD: NO, CURRENT BINARY: SAMSUNG OFFICIAL. Below that the green Android robot. Below that Downloading... Do not turn target off!! No other options. The only way to install is from a file from the computer... can I install the hub file from computer and do I do with odin? The Galaxy S II screen and this reboot are the only options I can get too. Your help is greatly appreciated.
Click to expand...
Click to collapse
Sfhub's program is the easiest thing you've ever done (it's saved my bacon loads of times!). You just put the phone into download mode, plug it into your PC and then run the program you downloaded from the post I originally linked.
Good luck!
I didn't get a link... I see many sfhubs downloads. I have the rooted EL29 No data downloading EL29 Stock Root. However, I have tried the one click EL29 No data root and then phone will only boot to Galaxy screen... I am new to Android OS.. I have only been familiar with Nokia since the beginning of time. Have transformed many of those... But can always go back to factory..Clicked Thanks too.... what file do I need???
Here you go:
http://forum.xda-developers.com/showthread.php?t=1433101
Also, here is a pretty easy tutorial I wrote a while back, it includes the link above:
http://forum.xda-developers.com/showpost.php?p=24158551&postcount=9980
I have download and tried to install the SPH-D710.EL29_CL852097_ROOTED-OneClick file. It failed. This is the message odin gave me:
<ID:0/005> 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/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> recovery.bin
<ID:0/005>
<ID:0/005>
<OSM> All threads completed. (succeed 0 / failed 1)
Debugging was checked before my phone bricked. I am only able to get to Odin Download mode and the Galaxy S II screen same as before.
RN69 said:
I have download and tried to install the SPH-D710.EL29_CL852097_ROOTED-OneClick file. It failed.
Debugging was checked before my phone bricked. I am only able to get to Odin Download mode and the Galaxy S II screen same as before.
Click to expand...
Click to collapse
That's not a good sign but let's try a couple of other things.
If you have Kies installed remove/uninstall it.
Download the full Samsung driver suite and install it from here:
http://org.downloadcenter.samsung.c...342248/Sprint_d710_USB_Driver_v1_3_2360_0.exe
Try the oneclick odin again. If it still fails, try your usb cable in all the different usb ports or even try a different computer too if possible. If you have access to a different cable that would be nice to try also.
I have a Sprint Galaxy S II 4G Touch, I rooted with Odin SPH-D710.EL_29CL852097_ROOTED_NODATA program. The phone worked fine. I then tried to unroot the phone using Odin v. 1.85 twith the PIT file that came with it and the Stock_EK02.Tar file. I accidently inserted the Tar file into the BOOTLOADER, PDA AND PHONE boxes. Now my phone is stuck in the Galaxy S II screen, however I can get to Odin recovery mode. Is there anyway to reclaim any usage from my phone. Please Help...
I have tried all of the above methods in this thread. I still get the same failed status with the one click file. I have tried laptops, desktops on multiple usb ports.
still getting the same fail message,posted above.
I disabled the phone with Odin3 v. 1.85.. see above. Is there any single files to flash into the BOOTLOADER, PDA AND PHONE spaces that I originally overwrote? I also ran again with the Re-Partion box clicked. Please Help!!!
When you are in download mode, tell us exactly what text is displayed on the screen there please.
---------- Post added at 12:31 PM ---------- Previous post was at 12:20 PM ----------
Also, have you tried using odin to flash just a kernel yet?
When I do the reboot via battery out volume down with power button, I get a screen that has ODIN MODE in red at top left. Below that in white is PRODOCUT NAME: SPH-0710, then below that, CUSTOM BINARY DOWNLOAD: NO, below that, CURRENT BINARY: SAMSUNG OFFICIAL. Below that the green Android robot. Below that Downloading in white. then in green: Do not turn target off!!
I tried to flash the Tar file I stated earlier but flashed it in the wrong places. What kernal/s would you suggest flashing?
Sorry for the slow responses having issues with my Samsung Transform Ultra now too. That is what I am using for my data service on PC. I did a mandatory samsung update the other day and barnacle doesn't work, can not unroot the phone and down to usb tethered connection that is to slow, but one phone at a time. I would like to get my Galaxy back. It was great.
And on PC on the Odin screen I get:
<ID:0/003> 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/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> recovery.bin
<ID:0/003>
<ID:0/003>
<OSM> All threads completed. (succeed 0 / failed 1)
and a red FAIL! box
Ok no problem.
Here is a link to an Odin guide. Not very helpful but it tells you a few necessary things and it's handy to have around if you ever need to know what the buttons are:
http://forum.xda-developers.com/showthread.php?t=1274337
Right above where it says:
DO NOT USE PHONE FOR ANYTHING BUT A RADIO/MODEM - YOU WILL DEFINITELY NOT BE ABLE TO USE YOUR PHONE FOR CALLS, AND YOU MAY POSSIBLY BRICK IT - YOU'VE BEEN WARNED
it tells you what the different keys are.
Anyway, download StockCWM-EL26.TAR from here (you may have to rename it without the MD5 to work with ODIN):
http://chris41g.devphone.org/index.php?dir=EpicTouch/Stock+Repack/EL26/
Open odin, load the tar file in pda, the only 2 things should be checked are reboot and PDA, click on start.
Let me know what happens.
I got this message on the PC Odin screen when I flashed the EL-26.tar:
<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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> zImage
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Completed..
<ID:0/003> Removed!!
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/008> Added!!
Ok, Now the phone boots into a different Galaxy screen. Now boots to Samsung Galaxy S ii GT-I9100 screen and when connected to the usb cable on restart the PC explorer shows the 2 internal mmc drives then doesn't if that makes any sense.
Then in Odin Mode on the phone has changed too. ODIN MODE in red top left. Under that in white is: PRODUCT NAME: SPH-0710, under that is CUSTON BINARY DOWNLOAD: YES (2 counts), under that CURRENT BINARY: CUSTOM... THEM THE ANDROID robot then Downloading then Do not turn off target!!
Ok cool we're making progress, now do you have any flashable rom zip files on the phone? And calkulin's format all? If so, boot up with pwr/vol up key, flash format all, then rom.
Sent from my SPH-D710 using XDA
---------- Post added at 08:22 PM ---------- Previous post was at 08:11 PM ----------
I just want you to know ahead of time , if we can get it running with a ROM, I'm going to ask you to save what you need off of the phone because I'm going to ask you to do a full reset back to stock and format everything. I want to make sure you are good to go especially due to what you did in ODIN initially so maybe this won't happen again. I will give you more instructions on that later though, let's see how this goes. Tnx.
OK when I boot with volume up/power button... I get many options... from top to bottom they are: - reboot system now, - apply update from sdcard, - wipe data/factory reset, - wipe cache partition, - install zip from sdcard, - backu and restore, - mounts and storage, - advanced, - power off...
Below that at the bottom in white I get ClockworkMod Recovery v5.0.2.7 then under:
E:Can't mount /cache/recovery/commmand
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
That's fine. Do you remember if you have any roms on the phone and are they on internal or external SD?
---------- Post added at 08:51 PM ---------- Previous post was at 08:35 PM ----------
What's up with the lag again between responses? Are you tethering the pc (no high speed internet?)
Your gonna want to download a rom and copy it over to your phone if u dont have 1.. To do so while in recovery u can goto mounts and storage mount usb.. Then u can copy and paste..after that.. Factory reset twice.. The power button is he back button home button is enter button vol up goes up vol down goes dowb.. Goto advanced options in main recovery menu and wipe dalvik cache...flash a rom and reboot..once rebooted...u need to power down and boot into download mode vol - & power.. Load sfhub el29 stock rooted and let it flash...once done..shut down..flash latest modem fe10. Go into your phone update prl and profile... Shut down..goto download mode flash el26 cwm kernel and once phone shuts off innediatelt vol + & power.. Youll boot into recovery now flash the rom of your choice im assuming first one u did in recovery and flash it.. Flash gapps and kernel if need be...u can get all the newest kernels and modems from sfhubs post abd youll want to dowoad the cwm ones to flash through recovery
Sent from my SPH-D710 using xda premium

[Q] SDS, sboot.bin + PIT fail, alternatives?

Hi all, i have a n7100 and the problem was that it just rebooted from nothing and was stuck on samsung logo, then i took it to the official repair center and they couldn do anything and told me that they needed to send it to samsung for repair but they will not do that due to root... so i took it to samsung autorized repair center and the same, they just tried to upload the stock rom but nothing... wont boot, buy a new board will cost me around $600 with those guys... so the problem is this
I can enter download mode and recovery:good:, so:
using odin, all roms (4 dif roms) fail to upload at sboot.bin
<ID:0/011> sboot.bin
<ID:0/011> FAIL!
(using 2 dif machines and 2 dif cables, all 4 roms)
then i tried to reformat using pit "N7100_t03g_0907-stock.pit" and
checking [Re-Partition] then it says there is no pit partition
<ID:0/003> Get PIT for mapping..
<ID:0/003>
<ID:0/003> There is no PIT partition.
the only rom i was able to fully upload was N7100UBALJ2_N7100TCEALJ1_TCE
but because it contains not the sboot.bin file...
still not booting
also using CWM recovery 6.0.1.4 i can't mount cache, system, data, sdcard neither format
[Error mounting /cache!] etc etc etc
i even used aromafm http://forum.xda-developers.com/showthread.php?t=1646108 to see files on internal sdcard but all those mentioned folders-partitions apear as empty folders but folders like dev, etc, lib, proc, res, sbin, sys, tmp apear ok (files inside)
and one final thing i cant replace CWM recovery for TWRP or stock recovery, i have both odin and sdcard versions but after finishing succesfully, rebooting and entering recovery again there is CWM...
so my questions are:
is there any other way to repartition not using odin+PIT
is there any utility to check internal sdcard integrity?
what about sboot.bin not being able to flash
any ideas?
At download mode is it writing the model of the phone?
Sent from my GT-N7100 using Tapatalk 2
vagsvag said:
At download mode is it writing the model of the phone?
Sent from my GT-N7100 using Tapatalk 2
Click to expand...
Click to collapse
yes it says:
odin mode
prod name: GT-N7100
cus bin downloads: yes (1 counts)
curr binary: custom
sys status: custom
mrshdw said:
yes it says:
odin mode
prod name: GT-N7100
cus bin downloads: yes (1 counts)
curr binary: custom
sys status: custom
Click to expand...
Click to collapse
Ok you have not sds for sure
You had install before 4.3 leak or mj5 bootloader?
vagsvag said:
Ok you have not sds for sure
You had install before 4.3 leak or mj5 bootloader?
Click to expand...
Click to collapse
nope still dont know much about bootloaders, will you please show me steps or thread
willing to do anything before emmc chip replacement, thanks!
mrshdw said:
nope still dont know much about bootloaders, will you please show me steps or thread
willing to do anything before emmc chip replacement, thanks!
Click to expand...
Click to collapse
I don't think you need replacement something didn't went well
I saw that cwm gave you message for broken cache partition etc
Take a look here chainfire has a fix for broken cache partition
http://forum.xda-developers.com/showthread.php?t=1932327
---------- Post added at 11:38 AM ---------- Previous post was at 11:15 AM ----------
It is not necessary to flash bootloader if you didn't touch it.
Also is dangerous if something happens you can't recover after.
vagsvag said:
I don't think you need replacement something didn't went well
I saw that cwm gave you message for broken cache partition etc
Take a look here chainfire has a fix for broken cache partition
http://forum.xda-developers.com/showthread.php?t=1932327
---------- Post added at 11:38 AM ---------- Previous post was at 11:15 AM ----------
It is not necessary to flash bootloader if you didn't touch it.
Also is dangerous if something happens you can't recover after.
Click to expand...
Click to collapse
yaep already tried that before, and now green button says PASS
<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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> cache.img
<ID:0/003> NAND Write Start!!
<ID:0/003> recovery.img
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Completed..
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 1 / failed 0)
but still cache cant mount in CWM, some messages [Can't mount /cache/recovery/command] and [Error mounting /cache] as those msgs appears always
Try this recovery it has 2 versions tar to flash via pc odin or zip to flash via cwm. Prefer odin, maybe cwm is broken.
http://forum.xda-developers.com/showthread.php?t=2028103
You are sure also when you try to flash that any kies process is not running at background.
vagsvag said:
Try this recovery it has 2 versions tar to flash via pc odin or zip to flash via cwm. Prefer odin, maybe cwm is broken.
http://forum.xda-developers.com/showthread.php?t=2028103
You are sure also when you try to flash that any kies process is not running at background.
Click to expand...
Click to collapse
via odin it passes - green button
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> philz_touch_5.15.0-n7100.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Removed!!
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Added!!
<ID:0/003> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
after rebooting same CWM 6.0.1.4 appears
the zip file installed file via cwm also passes it took a while but at the end all ok
reboot but again same CWM
and yes sure kies is not in the system as only installed and uninstalled for the drivers
tried few different recoverys - different versions - oding & cwm install zip file from sdcard but all refuses to stay
Seems at reboot cwm installs its self or i don't know what.
Here are rescue firmwares uploaded by a xda member
http://forum.xda-developers.com/showpost.php?p=32273406&postcount=5
If it is work maybe you have problem with efs because samsung updated efs 2 or 3 times i think.
I hope you have an efs backup
Post when you try
---------- Post added at 01:22 PM ---------- Previous post was at 12:51 PM ----------
Also 6.0.1.4 is old cwm and has not been patched with the Sudden Death Syndrome fix.
This problem is 6.0.1.4 problem and the same had other people with other devices
http://forum.xda-developers.com/showthread.php?t=2231928
http://forum.xda-developers.com/showthread.php?t=1937539
See, I had the EXACT same problem, including the "can't mount" messages on recovery and inability to boot.
I ended up fixing it this way:
http://forum.xda-developers.com/showthread.php?p=43760271
Try and see if it helps at all.
Cheers!
Sent from my GT-N7100
vagsvag said:
Seems at reboot cwm installs its self or i don't know what.
Here are rescue firmwares uploaded by a xda member
http://forum.xda-developers.com/showpost.php?p=32273406&postcount=5
If it is work maybe you have problem with efs because samsung updated efs 2 or 3 times i think.
I hope you have an efs backup
Post when you try
---------- Post added at 01:22 PM ---------- Previous post was at 12:51 PM ----------
Also 6.0.1.4 is old cwm and has not been patched with the Sudden Death Syndrome fix.
This problem is 6.0.1.4 problem and the same had other people with other devices
http://forum.xda-developers.com/showthread.php?t=2231928
http://forum.xda-developers.com/showthread.php?t=1937539
Click to expand...
Click to collapse
already tried before with those 3 roms, first 2 failing on sboot.bin
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> modem.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> sboot.bin
<ID:0/005> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
and third one 4 parts + PIT stoping at PIT when ticking [Re-Partiton]
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005>
<ID:0/005> There is no PIT partition.
<ID:0/005> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
and if not, stopping like first 2 on sboot.bin
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
and yes i have efs backup, the first time you select "mount /efs" in cwm it mounts, then if you unmount and mount again, it wont, it says "Error mounting /efs!" (works only for efs folder, but cache system data etc always unable to mount) so i restarted cwm and mount efs folder then using aroma fm copied to external sd cool!
also have some backup that i made with cwm, 3 files "system.ext4.dup" "boot.img" "recovery.img"
vladeco said:
See, I had the EXACT same problem, including the "can't mount" messages on recovery and inability to boot.
I ended up fixing it this way:
http://forum.xda-developers.com/showthread.php?p=43760271
Try and see if it helps at all.
Cheers!
Sent from my GT-N7100
Click to expand...
Click to collapse
im reading... thats an alternative to odin -> HEIMDALL, but before that im just curious about NAND erase all in odin.. will it make the difference? i mean will i be able to continue repartition using PIT file... if so, ill try...
did you were unable to flash sboot.bin also??
This tool you had try?
http://forum.xda-developers.com/showthread.php?t=1923956
He had remove the download link, you can find it here
http://www.skipsoft.net/?page_id=1099
Also take a look and here drketan's tool
http://forum.xda-developers.com/showthread.php?t=2445480
Sent from my GT-N7100 using Tapatalk 2
vagsvag said:
This tool you had try?
http://forum.xda-developers.com/showthread.php?t=1923956
He had remove the download link, you can find it here
http://www.skipsoft.net/?page_id=1099
Also take a look and here drketan's tool
http://forum.xda-developers.com/showthread.php?t=2445480
Sent from my GT-N7100 using Tapatalk 2
Click to expand...
Click to collapse
ok great tools, i have the toolkit but haven't tried all options, going to check more on that and also dr ketans tool
really appreciate all your help, tell you if a have any advance
mrshdw said:
im reading... thats an alternative to odin -> HEIMDALL, but before that im just curious about NAND erase all in odin.. will it make the difference? i mean will i be able to continue repartition using PIT file... if so, ill try...
did you were unable to flash sboot.bin also??
Click to expand...
Click to collapse
For me it only worked when I checked that box. I couldn't flash anything before that. Try not ticking that box and see if it works for you. It didn't for me so it was like a last resort in my case!
About SBOOT: Only the current version at the time, since I had already updated to it and it doesn't support downgrading. Just use the one you're currently using (included in your stock rom) and you should be fine.
I will be more than happy to guide you if you need any help.
Cheers!
Sent from my GT-N7100
vladeco said:
For me it only worked when I checked that box. I couldn't flash anything before that. Try not ticking that box and see if it works for you. It didn't for me so it was like a last resort in my case!
About SBOOT: Only the current version at the time, since I had already updated to it and it doesn't support downgrading. Just use the one you're currently using (included in your stock rom) and you should be fine.
I will be more than happy to guide you if you need any help.
Cheers!
Sent from my GT-N7100
Click to expand...
Click to collapse
ok i get it, if i find the same rom that i had, ill be able to fully flash rom, including sboot.bin, but no -older- roms as "it doesn't support downgrading", well i need to find that rom, dont remember which one i had, but i can keep trying, stock rom is not in the phone anymore, but remember flashing one a few month ago, but dont remember which one i had (sad & sorry)
for now after some downloads ill try to flash again, with and without PIT + Reformat, and if everything fails then use the NAND Erase all option.... seems clear! ill keep you posted

[Q] Help!!! Softbricked my SM-T520

HI everybody, I soft bricked my Galaxy tab pro 10.1 wifi, does anybody had a .pit file to share so I can fix it?
thanks
Laurence1222 said:
HI everybody, I soft bricked my Galaxy tab pro 10.1 wifi, does anybody had a .pit file to share so I can fix it?
thanks
Click to expand...
Click to collapse
Anything I can do?
Laurence1222 said:
Anything I can do?
Click to expand...
Click to collapse
What did you do to it?
crpalmer said:
What did you do to it?
Click to expand...
Click to collapse
I screwed up when loading a rom, now when I turn it on it tells me to connect to samsung kies, other than that all I can do is put it into download mode.
Laurence1222 said:
I screwed up when loading a rom, now when I turn it on it tells me to connect to samsung kies, other than that all I can do is put it into download mode.
Click to expand...
Click to collapse
Easy. Just download your firmware from sammobile. Then flash it using Odin in download mode.
Good luck!
ik4evr2 said:
Easy. Just download your firmware from sammobile. Then flash it using Odin in download mode.
Good luck!
Click to expand...
Click to collapse
Thank you so much! It worked!
I'm glad it worked! Please giive some thanks by clicking the thanks button, and if you would like to donate a little something a google play gift card code would do
Same problem
Laurence1222 said:
Thank you so much! It worked!
Click to expand...
Click to collapse
Hi there, im in the same dilemma. My tablet Sm T520 wifi version stuck in "firmware upgrade encountered an issue" screen. I cant turn off, can only turn into downloaf mode. Could you please help me and guode me through what exactly you did to get yours workjng again.
Could you please give me the names of the firmware update and what version of Odin you used? Any other relevant information would be helpful. Thx alot
I Have the same problem, flashing back from a custom rom to stock, downloaded in rom from samfirmware, flashed with odin and got a fail at the end. Stuck with the error to connect to kies, kies doesnt recognise when I connect to it, so I tried some other stock firmwares with odin 3.04 3.09 and 1.85 and all are failing at the end
Any ideas?
---------- Post added at 06:49 PM ---------- Previous post was at 06:06 PM ----------
Error from odin below
.<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img
<ID:0/003> cache.img
<ID:0/003> hidden.img
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
hardbreed said:
I Have the same problem, flashing back from a custom rom to stock, downloaded in rom from samfirmware, flashed with odin and got a fail at the end. Stuck with the error to connect to kies, kies doesnt recognise when I connect to it, so I tried some other stock firmwares with odin 3.04 3.09 and 1.85 and all are failing at the end
Any ideas?
---------- Post added at 06:49 PM ---------- Previous post was at 06:06 PM ----------
Error from odin below
.<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img
<ID:0/003> cache.img
<ID:0/003> hidden.img
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Do you have the box or serial number on hand?
If you're able to enter download mode, do the following:
Open Kies 3 and enter download mode, and hook up the tablet
Tools-firmware update and initialization
Enter model number and serial number
Wait
The process may take an hour, so make sure the battery is fully charged.
That did the trick, thanks a million for the help
Basically, Samsung phones/tablets are "unbrickable" as long as you can run download mode and have serial number on hand.
In the same boat. Tablet started acting funny last night. Deleted a bunch of apps, but left the icons.
Figured I would do a restore from a previous backup. That failed and now the tablet wouldn't boot.
So I downloaded Kies3, tells me that my tablet model is not supported. Tried earlier Kies, hangs on connection.
So I downloaded the latest firmware for my tablet from Sammobile to try and flash in Odin.
Flashes successully, however does not boot after. It has been stuck on the Samsung logo for an hour.
Any ideas?
scrolanky said:
In the same boat. Tablet started acting funny last night. Deleted a bunch of apps, but left the icons.
Figured I would do a restore from a previous backup. That failed and now the tablet wouldn't boot.
So I downloaded Kies3, tells me that my tablet model is not supported. Tried earlier Kies, hangs on connection.
So I downloaded the latest firmware for my tablet from Sammobile to try and flash in Odin.
Flashes successully, however does not boot after. It has been stuck on the Samsung logo for an hour.
Any ideas?
Click to expand...
Click to collapse
If I don't have the box, how do I find out the serial number of a soft bricked tablet ?
mingkee said:
Do you have the box or serial number on hand?
If you're able to enter download mode, do the following:
Open Kies 3 and enter download mode, and hook up the tablet
Tools-firmware update and initialization
Enter model number and serial number
Wait
The process may take an hour, so make sure the battery is fully charged.
Click to expand...
Click to collapse
Thank you so much to have posted this. Solved a boot loop problem I was having perfectly. Now I can go back to using my tablet.

stuck on boot screen with no recovery mode [SM-t320]

Hello Guys!! I'm hoping someone can give me a hand. I got a Samsung Galaxy Tab Pro 8.4 (SM-T320) that is soft brick. If i'm not mistaken the device was been updated via OTA and crashed. Every time i try to turn on the device I get the following message "firmware upgrade encountered an issue. Please select recovery mode in Kies & try again". For some reason I'm not able to boot the device into recovery mode. It seems the partition got damaged. Please note that I'm using the following commands to boot into recovery mode (volume up+home+power). I have tried connecting my tablet to Samsung Kies v2.6.3.14074_11 and use the option "Firmware Upgrade & Initialisation" but at the end of the procedure I get the following message "This version of the device cannot be updated". I have attempted to flash the device using Odin v3.07. The stock ROM I used was T320UEU1ANG1_T320XAC1ANG1_HOME.tar.md5. The Odin PASSED and reset device but the phone did not boot back up. It just gets stuck on the boot screen. I have also tried to flash the device with custom recovery cwmr-20140605.tar. but I didn't have any luck. If anyone has any ideas or solutions, please let me know. I'll greatly appreciated.
bmesta said:
Hello Guys!! I'm hoping someone can give me a hand. I got a Samsung Galaxy Tab Pro 8.4 (SM-T320) that is soft brick. If i'm not mistaken the device was been updated via OTA and crashed. Every time i try to turn on the device I get the following message "firmware upgrade encountered an issue. Please select recovery mode in Kies & try again". For some reason I'm not able to boot the device into recovery mode. It seems the partition got damaged. Please note that I'm using the following commands to boot into recovery mode (volume up+home+power). I have tried connecting my tablet to Samsung Kies v2.6.3.14074_11 and use the option "Firmware Upgrade & Initialisation" but at the end of the procedure I get the following message "This version of the device cannot be updated". I have attempted to flash the device using Odin v3.07. The stock ROM I used was T320UEU1ANG1_T320XAC1ANG1_HOME.tar.md5. The Odin PASSED and reset device but the phone did not boot back up. It just gets stuck on the boot screen. I have also tried to flash the device with custom recovery cwmr-20140605.tar. but I didn't have any luck. If anyone has any ideas or solutions, please let me know. I'll greatly appreciated.
Click to expand...
Click to collapse
Very strange.
Did you tried another firmware version using odin?
edlabh said:
Very strange.
Did you tried another firmware version using odin?
Click to expand...
Click to collapse
I just attempted to use odin v3.09 but I'm still having the same problem. It keeps getting stuck on the samsung galaxy tab pro sm-t320 screen without recovery mode. I have attempted to flash cmw again but the problem persists. I also noticed the battery won't charge anymore. I'm not sure if this was due to a failed flash. Anyone has any other ideas?
bmesta said:
I just attempted to use odin v3.09 but I'm still having the same problem. It keeps getting stuck on the samsung galaxy tab pro sm-t320 screen without recovery mode. I have attempted to flash cmw again but the problem persists. I also noticed the battery won't charge anymore. I'm not sure if this was due to a failed flash. Anyone has any other ideas?
Click to expand...
Click to collapse
Get the cwmr tar file (unzip the zip). Flash it in Odin. When it starts to flash it, hold the volume up key until it shows the galaxy tab pro splash screen and says something like "warranty bit set: recovery".
That should get you back to recovery. If that doesn't work, post a screen shot of Odin after the flash.
If your kernel is broken, which it sounds like it is, it's normal that it won't charge because it needs to boot the kernel to charge even when you "power off".
crpalmer said:
Get the cwmr tar file (unzip the zip). Flash it in Odin. When it starts to flash it, hold the volume up key until it shows the galaxy tab pro splash screen and says something like "warranty bit set: recovery".
That should get you back to recovery. If that doesn't work, post a screen shot of Odin after the flash.
If your kernel is broken, which it sounds like it is, it's normal that it won't charge because it needs to boot the kernel to charge even when you "power off".
Click to expand...
Click to collapse
I managed to get my tablet to charge by tearing down the device and reconnecting the battery. After doing this, i plugged it directly to the wall. I got this idea from a youtube video. Im going to leave the battery charging all night. Hopefully tom its a good day and i have a working device
bmesta said:
I managed to get my tablet to charge by tearing down the device and reconnecting the battery. After doing this, i plugged it directly to the wall. I got this idea from a youtube video. Im going to leave the battery charging all night. Hopefully tom its a good day and i have a working device
Click to expand...
Click to collapse
Wow!
just now I realize this problem with non-removable battery. This really sucks!
How did you charge the battery? Maybe a lipo charger?
edlabh said:
Wow!
just now I realize this problem with non-removable battery. This really sucks!
How did you charge the battery? Maybe a lipo charger?
Click to expand...
Click to collapse
Im really happy to say that now i got a working tablet. I guess removing the battery did the trick.
'edlabh' thanks for all your help. I was able to charge the battery by plugging it directly to the wall. Please note that i had to take the entire tablet apart and disconnect the batteryfor 15 min before reconnecting it. Thank god im good with teardowns and i dont give up that easy
crpalmer said:
Get the cwmr tar file (unzip the zip). Flash it in Odin. When it starts to flash it, hold the volume up key until it shows the galaxy tab pro splash screen and says something like "warranty bit set: recovery".
That should get you back to recovery. If that doesn't work, post a screen shot of Odin after the flash.
If your kernel is broken, which it sounds like it is, it's normal that it won't charge because it needs to boot the kernel to charge even when you "power off".
Click to expand...
Click to collapse
Hello, I was wondering if you would help with the kernel... Idk how to do it. I have done everything he did and even opened my tablet and took out the battery but it still did not work. :crying:
---------- Post added at 07:01 PM ---------- Previous post was at 06:32 PM ----------
crpalmer said:
Get the cwmr tar file (unzip the zip). Flash it in Odin. When it starts to flash it, hold the volume up key until it shows the galaxy tab pro splash screen and says something like "warranty bit set: recovery".
That should get you back to recovery. If that doesn't work, post a screen shot of Odin after the flash.
If your kernel is broken, which it sounds like it is, it's normal that it won't charge because it needs to boot the kernel to charge even when you "power off".
Click to expand...
Click to collapse
I already tried flashing TWRP, CWM, CF Autoroot (to be able to install a custom recovery). I opened it and removed the battery for 15 mins. unlike this guy, it didnt work for me. I also tried flashing CM12. The tablet wont turn on without being plugged in and I can only access "Downloading Mode"
Perhaps the kernel is broken, but how do I fix it?
This is Odin's message, after flashing stock firmware.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T320UEU1ANG1_T320XAC1ANG1_HOME.tar.md5 is invalid.
<OSM> End...
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T320UEU1ANG1_T320XAC1ANG1_HOME.tar.md5 is invalid.
<OSM> End...
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T320XXU1BOC1_T320UVS1BOC1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/003> Removed!!
<ID:0/003> Removed!!
<ID:0/003> Removed!!
<ID:0/003> Removed!!
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Removed!!
<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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> modem.bin
<ID:0/003> cache.img.ext4
<ID:0/003> hidden.img.ext4
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/003> Removed!!
But it still wont boot past the splash screen nor can I access recovery mode.
Install Kies 3 from Samsung and try the tools -> emergency firmware recover option before anything else gets messed up.
Odin is not safe to mess around with, if you accidentally check a wrong option or use any field other then AP, you might end up with perm brick
Sometimes the vol keys are reversed try Power + the other vol key
otyg said:
Install Kies 3 from Samsung and try the tools -> emergency firmware recover option before anything else gets messed up.
Odin is not safe to mess around with, if you accidentally check a wrong option or use any field other then AP, you might end up with perm brick
Sometimes the vol keys are reversed try Power + the other vol key
Click to expand...
Click to collapse
Also, another thing is the when I plug it in and press the power button it lights up and shows the battery icon with no charge stuck in a loading icon that is not animated.
I will try your suggestion but I had already try (on Kies) Update and Recovery but it didnt work (perhaps because of the tablet being in Downloading mode?)
UPDATE: Kies 3 wont recognize tablet, even in Downloading mode (which is the only mode I can access).
Thanks!
This thread is very old. But I've the same problem, stuck at samsung logo and only get into download mode. Accessing the twrp recovery mode is not possible. I've not flashed the device and the battery had over 90% percent. I started the device suddenly it turned of and it was not possible to start it again. Has anyone solved this problem?
I didn't thought that the battery was the problem, because one time the devices started and showed about 90%, but it was the battery. The batteries are very bad for this device, this is my third one.

Screen says There is no PIT partition after Firmware Install Failure

So I've been at this for a total of 9 hours now...here's the story:
Yesterday I have my trusty Note 4 on the charger, it charges fully and I unplug from the cord.
I hit the home button and the screen stays black like it was frozen.
I hit the power button, nothing happens.
I pull the battery, put it back in, nothing.
It finally goes back on and I get the Cant do normal boot:"MMC_Failed" and I'm stuck on the Odin screen.
Try to just re-flash the stock rooted ROM I was using at the time of this disaster and I kept getting the same message so I bring the phone to a Sprint service center where, when I walk in the front door and tap the power button, the phone lights right up and works. Now I look like a clown.
I leave the store and it freezes again so I try a factory reset, which sets this whole process in motion again once I set it up...freezes, "can't do normal boot" etc.
Then after someone suggested to flash the latest TWRP (3.0.0.0) and a stock firmware, I get a "system write fail" in Odin (both 3.09 & 3.10) so I try to flash the stock ROM again now I get a "No PIT File" error.
I flash the PIT file specific for my phone I got from SamMobile along with the same ROM and the phone wouldn't start.
I noticed the "system" was unchecked in TWRP so I checked it before doing anything but still no luck as of last night/this morning at 3:00am.
I wake up this morning and it goes right on with no issue just like a fresh/factory reset device.
Is there something i can do to make sure everything is ok so I don't have to go through this again?
I need this Note 4 to work.
I have been running stock OJ6 rooted ROM and that's it. No mods or anything, just root so for this to start acting up the way it did or why it happened is beyond me.
Someone recommended to install ClockworkMod so that would fix the "system" error but I'd rather see if anyone else had the same problem and how they fixed it before I attempt anything else.
Usually, any time I ever had a problem I clear the dalvik/cache, factory reset or flash firmware in Odin and everything is straight.
Thanks ahead of time for any help.
What method are you rooting with? Kernel and SuperSU version? Stock patched kernel or custom kernel?
Sounds like hardware failure but it could be unstable root with Knox fighting it and causing confusion. Knox and root don't coexist well.
When you pull battery, do you wait at least 30 seconds and use power button to drain residual power before reinserting battery? I've also noticed that power down doesn't happen so quickly as you think it should. Also, every black screen is not a power down state. Something is not quite right if you experience black screens in system booted mode but I wouldn't be so quick to pull the battery. Give it time to recover or hold power and volume up to reboot it if black screen persists on you. Battery pulls may be corrupting memory or losing data.
Edit: Philz CWM recovery has been recommended to wipe and flash when TWRP fails to do so. But it's been demonstrated that stock recovery can wipe where Philz fails to. Ultimately, I think some of the users reporting such were experiencing hardware failure so it's either randomness of successful wipe or the stronger tool demonstrating itself. Also since TWRP has been updated, it's unknown in my thinking which is the better Recovery to wipe and flash with. I prefer TWRP but thankfully haven't had the occasion of failed Odin or recovery flashes.
Your battery or power switch may contributing to the bad experience as well.
Sent from my SM-N920P using Tapatalk
samep said:
What method are you rooting with? Kernel and SuperSU version? Stock patched kernel or custom kernel?
Sounds like hardware failure but it could be unstable root with Knox fighting it and causing confusion. Knox and root don't coexist well.
When you pull battery, do you wait at least 30 seconds and use power button to drain residual power before reinserting battery? I've also noticed that power down doesn't happen so quickly as you think it should. Also, every black screen is not a power down state. Something is not quite right if you experience black screens in system booted mode but I wouldn't be so quick to pull the battery. Give it time to recover or hold power and volume up to reboot it if black screen persists on you. Battery pulls may be corrupting memory or losing data.
Edit: Philz CWM recovery has been recommended to wipe and flash when TWRP fails to do so. But it's been demonstrated that stock recovery can wipe where Philz fails to. Ultimately, I think some of the users reporting such were experiencing hardware failure so it's either randomness of successful wipe or the stronger tool demonstrating itself. Also since TWRP has been updated, it's unknown in my thinking which is the better Recovery to wipe and flash with. I prefer TWRP but thankfully haven't had the occasion of failed Odin or recovery flashes.
Your battery or power switch may contributing to the bad experience as well.
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
yeah I hold the power button for like 30 seconds to a minute to make sure the charge is gone.
I just re-flashed thhhe rom but i'm gonna try to unroot if i can now that I can get into recovery again, i wasn't able to last night
broad_st_bully said:
yeah I hold the power button for like 30 seconds to a minute to make sure the charge is gone.
I just re-flashed thhhe rom but i'm gonna try to unroot if i can now that I can get into recovery again, i wasn't able to last night
Click to expand...
Click to collapse
If you're trying to boot un-rooted, you may be using stock kernel with systemless root? Why stock kernel? It's more stable in that fashion of full un-root with systemless SuperSU root.
But latest Beastmode works well; keep it updated. There was the initial release that somehow got hindered by a Samsung security update and boot looped once the update was pushed.
Anyway, if you're using systemless root, keep the SuperSU beta up to date for stability purposes. It's experimental as far as Lollipop is concerned and doesn't play well with system modifications.
Or maybe you're not using it for frequent full un-root? I'm actually testing it again with stock kernel ATM.
Sent from my SM-N920P using Tapatalk
samep said:
If you're trying to boot un-rooted, you may be using stock kernel with systemless root? Why stock kernel? It's more stable in that fashion of full un-root with systemless SuperSU root.
But latest Beastmode works well; keep it updated. There was the initial release that somehow got hindered by a Samsung security update and boot looped once the update was pushed.
Anyway, if you're using systemless root, keep the SuperSU beta up to date for stability purposes. It's experimental as far as Lollipop is concerned and doesn't play well with system modifications.
Or maybe you're not using it for frequent full un-root? I'm actually testing it again with stock kernel ATM.
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
Odin wasn't working, kept getting "write/fail" so I flashed the PIT file along with the stock firmware after *everything on earth* didn't work, Odin did it's thing and I got the green PASS! but still can't boot the phone regularly...I got into factory recovery just to make sure i was not rooted, did a factory reset and it doesn't reboot...I'm lost here...
my main thing was to get it to unroot so I can bring it to Sprint and let them try to fix it...but I can't boot to make sure it's running stock, I don't wanna get there and they boot it and see the phone is rooted...
Flashed PIT file and stock firmware and got the following (pass):
<ID:0/006> Removed!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910PVPU4COJ6_N910PSPT4COJ6_N910PVPU4COJ6_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Added!!
<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> 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> SingleDownload.
<ID:0/006> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl1.mbn
<ID:0/006> rpm.mbn
<ID:0/006> tz.mbn
<ID:0/006> sdi.mbn
<ID:0/006> NON-HLOS.bin
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img.ext4
<ID:0/006> cache.img.ext4
<ID:0/006> modem.bin
<ID:0/006> RQT_CLOSE !!
<ID:0/006> RES OK !!
<ID:0/006> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/006> Removed!!
factory recovery is installed and I'm guessing the stock firmware but I still can not boot the phone except for recovery and odin/download mode...this is crazy:silly:
broad_st_bully said:
Odin wasn't working, kept getting "write/fail" so I flashed the PIT file along with the stock firmware after *everything on earth* didn't work, Odin did it's thing and I got the green PASS! but still can't boot the phone regularly...I got into factory recovery just to make sure i was not rooted, did a factory reset and it doesn't reboot...I'm lost here...
my main thing was to get it to unroot so I can bring it to Sprint and let them try to fix it...but I can't boot to make sure it's running stock, I don't wanna get there and they boot it and see the phone is rooted...
Click to expand...
Click to collapse
If it dus not boot try to flash repair firmware
broad_st_bully said:
Flashed PIT file and stock firmware and got the following (pass):
Removed!!
Enter CS for MD5..
Check MD5.. Do not unplug the cable..
Please wait..
N910PVPU4COJ6_N910PSPT4COJ6_N910PVPU4COJ6_HOME.tar.md5 is valid.
Checking MD5 finished Sucessfully..
Leave CS..
Added!!
Odin v.3 engine (ID:6)..
File analysis..
SetupConnection..
Initialzation..
Set PIT file..
DO NOT TURN OFF TARGET!!
Get PIT for mapping..
Firmware update start..
SingleDownload.
aboot.mbn
NAND Write Start!!
sbl1.mbn
rpm.mbn
tz.mbn
sdi.mbn
NON-HLOS.bin
boot.img
recovery.img
system.img.ext4
cache.img.ext4
modem.bin
RQT_CLOSE !!
RES OK !!
Remain Port .... 0
All threads completed. (succeed 1 / failed 0)
Removed!!
factory recovery is installed and I'm guessing the stock firmware but I still can not boot the phone except for recovery and odin/download mode...this is crazy:silly:
Click to expand...
Click to collapse
If you've wiped everything but extSdCard and flashed the stock tar in Odin, there shouldn't be any trace of root. You're not rooted.
Did you try factory reset in stock recovery? Can't recall, but is there also a format data option in stock recovery? If so, try that too.
Sent from my SM-N920P using Tapatalk
broad_st_bully said:
Flashed PIT file and stock firmware and got the following (pass):
<ID:0/006> Removed!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910PVPU4COJ6_N910PSPT4COJ6_N910PVPU4COJ6_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Added!!
<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> 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> SingleDownload.
<ID:0/006> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl1.mbn
<ID:0/006> rpm.mbn
<ID:0/006> tz.mbn
<ID:0/006> sdi.mbn
<ID:0/006> NON-HLOS.bin
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img.ext4
<ID:0/006> cache.img.ext4
<ID:0/006> modem.bin
<ID:0/006> RQT_CLOSE !!
<ID:0/006> RES OK !!
<ID:0/006> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/006> Removed!!
factory recovery is installed and I'm guessing the stock firmware but I still can not boot the phone except for recovery and odin/download mode...this is crazy:silly:
Click to expand...
Click to collapse
You need a repair firmware 4 file firmware
PDA
Modem
CSC
Bootloder
Go here http://www.tsar3000.com/Joomla/index.php?option=com_content&view=category&id=55&Itemid=82 and find firmware acoding to your phone model and country region and flash via odin hit thanks if helped
waheem said:
You need a repair firmware 4 file firmware
PDA
Modem
CSC
Bootloder
Go here http://www.tsar3000.com/Joomla/index.php?option=com_content&view=category&id=55&Itemid=82 and find firmware acoding to your phone model and country region and flash via odin hit thanks if helped
Click to expand...
Click to collapse
Thanks for all the help...I think it's fixed though...hopefully...I let it sit a few minutes, factory reset it again and hit "power down", turned it on after a minute, went through the setup and setup as a new device then got an update...it's updating now so I'll know if it's ok once the update is finished...hope so!
broad_st_bully said:
Thanks for all the help...I think it's fixed though...hopefully...I let it sit a few minutes, factory reset it again and hit "power down", turned it on after a minute, went through the setup and setup as a new device then got an update...it's updating now so I'll know if it's ok once the update is finished...hope so!
Click to expand...
Click to collapse
I'm gonna try your link. even though it seems to be working now it still reads "MMC_READ FAILED" in Odin/DL mode...gonna try and see if your fix helps, thank you.:good:
broad_st_bully said:
Thanks for all the help...I think it's fixed though...hopefully...I let it sit a few minutes, factory reset it again and hit "power down", turned it on after a minute, went through the setup and setup as a new device then got an update...it's updating now so I'll know if it's ok once the update is finished...hope so!
Click to expand...
Click to collapse
tried to flash that file, back where i started, it failed in Odin right away, stuck with the "firmware upgrade encountered an issue" for Kies that doesn't even work for this phone for some reason....Kies is straight trash...
broad_st_bully said:
I'm gonna try your link. even though it seems to be working now it still reads "MMC_READ FAILED" in Odin/DL mode...gonna try and see if your fix helps, thank you.:good:
Click to expand...
Click to collapse
Just press thanks buttons if help
broad_st_bully said:
tried to flash that file, back where i started, it failed in Odin right away, stuck with the "firmware upgrade encountered an issue" for Kies that doesn't even work for this phone for some reason....Kies is straight trash...
Click to expand...
Click to collapse
@broad_st_bully any luck on this issue since last post? or had you given up? I am experiencing the same issue but with the tmobile version running cmremix rooted.... at least it was...

Categories

Resources