Hey guys, made an account just to ask this question as every time I try to flash CWM or TWRP my tab 3 just fails to do it
I follow all the instructions,
Boot into download mode
select the file in odin 3.07
deselect auto reboot
click start
I then tried all different combinations of buttons, i.e Power+vol up
but when I do that, unless I boot back into android, it just perpetually resets and wont go into recovery mode
Am I missing something here? a prerequisite?
Did you try the combination Volume+ and Home and PowerOn, after you see the Samung Galaxy Logo, let go off the Power-Button and keep holding Volume+ and Home?
This ist the (Custom-)Recovery Mode, Power and Vol- would be Download-Mode.
Pitey said:
Did you try the combination Volume+ and Home and PowerOn, after you see the Samung Galaxy Logo, let go off the Power-Button and keep holding Volume+ and Home?
This ist the (Custom-)Recovery Mode, Power and Vol- would be Download-Mode.
Click to expand...
Click to collapse
When I try the Vol+, power on and home it does the exact same thing, except resets once and then boots in to android
@AppleAssassin
First you are going to READ All this before executing anything. It took me a long time to write this, you should at least read it.
Please understand that we can not disconnect the battery!! So every time we press the POWER longer than 5 seconds TAB mimics a battery disconnect. Guess what, if you let the power button pressed after "Samsung" Logo shows, it will power of again!! This is what I suspect is your problem!!!!!!!!!!!!!!!!!!!!!!. One you see Samsung Logo you need to release the Power.
Also, The original Command for Samsung Download Mode is [Power]+[Volume Down]+[Menu]. But in fact mine just go in Download without [Menu], just [Power]+[Volume Down] and release after Samsung logo.
Since our TAB 10 has a big screen it makes a little difficult to navigate on recoveries. I found that the best is a CWM improve version called Philz Adv CWM 6.55.0. You can read moonbutt74 tread at http://forum.xda-developers.com/gal...ockworkmod-recovery-6-0-5-0-gt-p5210-t2830871
This will send you to: h__p://d-h.st/users/moonbutt74/?fld_id=38524#files
And I will suggest you download =>http://fs1.d-h.st/download/00136/SSY/PhilzAdvCWM-6_55_0-gtP-5210-v2.zip
1)First you need to feel comfortable. Realize that your tablet screen is a BIGGG button. Once you are doing the Dangerous stuff, if you have butter hands you can get in trouble easily. I do preferred to work with my TAB3 in a Flat surface like a table. Hands away if you do not need to touch anything.
2)Google and Youtube is your friend. I try to search for a video on TAB3 10 Recovery but no luck. So please look at:
Samsung Galaxy Tab 3 ClockWorkMod Recovery Install =>http://www.youtube.com/watch?v=XolmtyvS3Yk&feature=youtu.be
That is for a 7" instead of a 10". You only need to realize that the [MENU Button] is on the side in a 7#. TAB3 10" [MENU Button] is on in the bottom (Land Scape). Use ONLY the software that applied to you particular model. Ignore the software names of the video.
You can have more videos at:
[VIDEOS] Galaxy Tab 3 7in How to root, recovery, roms, & Kitkat=>http://forum.xda-developers.com/showthread.php?t=2459817
3)First turn on Tab and in Android OS Play with your buttons and verify they work. Learn to know what is your [Power] [Volume Down] [Volume Up] & [Menu]. Set clear in your mind that the [Volume Down] is the closes to the [Power].
4) If anything Fails you can get in to Download mode with adb command. But Please note that I will suggest you to figure out first why the volume method is not working, you will need them in the future. Be smart!.
See this video =>http://www.youtube.com/watch?v=NPYCpbMoWkQ
It show you how to use Googles SDK adb. Downloading SDK takes for ever. This what I will sugest you use. Instead use "Minimal ADB" by going to to this page http://forum.xda-developers.com/showthread.php?t=2317790 READ that page too.
Download Version 1.1.3 for windows =>https://docs.google.com/file/d/0B1S0LCuXCnnmSWh6NGJmSE1BUWc/edit?usp=sharing
As you will found installation will create a Shortcut in you Desktop. Using that "Minimal ADB and Fastboot" Shortcut will make the first 5 minutes of the previous video useless. So you only need the last minute where you type "adb reboot download". But here is my explanation:
a) Hook your Tab3 to the PC
b) Use "Minimal ADB and Fastboot" Shortcut
c) Verify that you Tab3 is recognized. Type in "Minimal ADB" the command
Code:
[COLOR="Blue"]adb device[/COLOR]s
If you find your self with this
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>[COLOR="Blue"]adb devices[/COLOR]
List of devices attached
12345678901234 [COLOR="Red"]offline[/COLOR]
This means you device is offline. To repair go to: Settings>Developer Options>
Now Unselected "Usb Debugging option" and reselect.
A Windows Pop Up, Click "Ok"
now lets try again adb devices
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
12345678901234 [COLOR="Blue"]device[/COLOR]
Success! is connected.
d) Now type in the Minimal ADB CMD window "adb reboot download" [Enter]
Code:
adb reboot download
You will see your tab turn off and reboot in Download mode. Now you can use Odin.
r2d23cpo said:
@AppleAssassin
First you are going to READ All this before executing anything. It took me a long time to write this, you should at least read it.
Please understand that we can not disconnect the battery!! So every time we press the POWER longer than 5 seconds TAB mimics a battery disconnect. Guess what, if you let the power button pressed after "Samsung" Logo shows, it will power of again!! This is what I suspect is your problem!!!!!!!!!!!!!!!!!!!!!!. One you see Samsung Logo you need to release the Power.
Also, The original Command for Samsung Download Mode is [Power]+[Volume Down]+[Menu]. But in fact mine just go in Download without [Menu], just [Power]+[Volume Down] and release after Samsung logo.
Since our TAB 10 has a big screen it makes a little difficult to navigate on recoveries. I found that the best is a CWM improve version called Philz Adv CWM 6.55.0. You can read moonbutt74 tread at http://forum.xda-developers.com/gal...ockworkmod-recovery-6-0-5-0-gt-p5210-t2830871
This will send you to: h__p://d-h.st/users/moonbutt74/?fld_id=38524#files
And I will suggest you download =>http://fs1.d-h.st/download/00136/SSY/PhilzAdvCWM-6_55_0-gtP-5210-v2.zip
1)First you need to feel comfortable. Realize that your tablet screen is a BIGGG button. Once you are doing the Dangerous stuff, if you have butter hands you can get in trouble easily. I do preferred to work with my TAB3 in a Flat surface like a table. Hands away if you do not need to touch anything.
2)Google and Youtube is your friend. I try to search for a video on TAB3 10 Recovery but no luck. So please look at:
Samsung Galaxy Tab 3 ClockWorkMod Recovery Install =>http://www.youtube.com/watch?v=XolmtyvS3Yk&feature=youtu.be
That is for a 7" instead of a 10". You only need to realize that the [MENU Button] is on the side in a 7#. TAB3 10" [MENU Button] is on in the bottom (Land Scape). Use ONLY the software that applied to you particular model. Ignore the software names of the video.
You can have more videos at:
[VIDEOS] Galaxy Tab 3 7in How to root, recovery, roms, & Kitkat=>http://forum.xda-developers.com/showthread.php?t=2459817
3)First turn on Tab and in Android OS Play with your buttons and verify they work. Learn to know what is your [Power] [Volume Down] [Volume Up] & [Menu]. Set clear in your mind that the [Volume Down] is the closes to the [Power].
4) If anything Fails you can get in to Download mode with adb command. But Please note that I will suggest you to figure out first why the volume method is not working, you will need them in the future. Be smart!.
See this video =>http://www.youtube.com/watch?v=NPYCpbMoWkQ
It show you how to use Googles SDK adb. Downloading SDK takes for ever. This what I will sugest you use. Instead use "Minimal ADB" by going to to this page http://forum.xda-developers.com/showthread.php?t=2317790 READ that page too.
Download Version 1.1.3 for windows =>https://docs.google.com/file/d/0B1S0LCuXCnnmSWh6NGJmSE1BUWc/edit?usp=sharing
As you will found installation will create a Shortcut in you Desktop. Using that "Minimal ADB and Fastboot" Shortcut will make the first 5 minutes of the previous video useless. So you only need the last minute where you type "adb reboot download". But here is my explanation:
a) Hook your Tab3 to the PC
b) Use "Minimal ADB and Fastboot" Shortcut
c) Verify that you Tab3 is recognized. Type in "Minimal ADB" the command
Code:
[COLOR="Blue"]adb device[/COLOR]s
If you find your self with this
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>[COLOR="Blue"]adb devices[/COLOR]
List of devices attached
12345678901234 [COLOR="Red"]offline[/COLOR]
This means you device is offline. To repair go to: Settings>Developer Options>
Now Unselected "Usb Debugging option" and reselect.
A Windows Pop Up, Click "Ok"
now lets try again adb devices
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
12345678901234 [COLOR="Blue"]device[/COLOR]
Success! is connected.
d) Now type in the Minimal ADB CMD window "adb reboot download" [Enter]
Code:
adb reboot download
You will see your tab turn off and reboot in Download mode. Now you can use Odin.
Click to expand...
Click to collapse
Hey, thanks for writing all that but the problem isn't getting in to download mode. It's after I use odin in download mode. Whether I use "Auto Reboot" or manually reboot. Neither work. If I manually reboot out of download mode after I flash using odin, using the power+vol up and then release the power button as soon as I see the samsung logo it reboots again and then boots into android.
AppleAssassin said:
Hey, thanks for writing all that but the problem isn't getting in to download mode. It's after I use odin in download mode. Whether I use "Auto Reboot" or manually reboot. Neither work. If I manually reboot out of download mode after I flash using odin, using the power+vol up and then release the power button as soon as I see the samsung logo it reboots again and then boots into android.
Click to expand...
Click to collapse
So the problem is in fact You Can Not get into Recovery Mode!
My best guest is that the recovery file you are using is no good or that the procedure using Odin is no good.
Before we do anything lets use ADB Minimal to go into Recovery Mode and see what is the output.
So lets do Step #4 of my previous tutorial. But the last command instead of "adb reboot download" you are going to do
Code:
adb reboot recovery
Tel me what you see without pushing any buttons.
r2d23cpo said:
So the problem is in fact You Can Not get into Recovery Mode!
My best guest is that the recovery file you are using is no good or that the procedure using Odin is no good.
Before we do anything lets use ADB Minimal to go into Recovery Mode and see what is the output.
So lets do Step #4 of my previous tutorial. But the last command instead of "adb reboot download" you are going to do
Code:
adb reboot recovery
Tel me what you see without pushing any buttons.
Click to expand...
Click to collapse
I can boot recovery mode when the device has been turned off using power+vol up but I cannot reboot in to recovery from download mode. I can also reboot into recovery OR download mode using the adb fastboot
Also, with that cwm file you sent. How can I use it with odin because it is a .img file and not .tar or .md5?
AppleAssassin said:
I can boot recovery mode when the device has been turned off using power+vol up but I cannot reboot in to recovery from download mode. I can also reboot into recovery OR download mode using the adb fastboot
Click to expand...
Click to collapse
Boy o Boy, you have no problem!
You are just complaining about Odin. Why Odin is not allowing you to reboot into recovery form it self! For that I have no Idea. Normally I used Odin ones to get my first Recovery and no more! I could used it again to load a factory OS, but I do not see my self doing that soon. The rest I do it from recovery using update.zip.
r2d23cpo said:
Boy o Boy, you have no problem!
You are just complaining about Odin. Why Odin is not allowing you to reboot into recovery form it self! For that I have no Idea. Normally I used Odin ones to get my first Recovery and no more! I could used it again to load a factory OS, but I do not see my self doing that soon. The rest I do it from recovery using update.zip.
Click to expand...
Click to collapse
I'm not complaining about odin. I'm expecting odin to do its job, and it seems to do it but my tab perpetually reboots after I "flash" the file and try to enter recovery mode
AppleAssassin said:
Also, with that cwm file you sent. How can I use it with odin because it is a .img file and not .tar or .md5?
Click to expand...
Click to collapse
You are definitely right! I just realized that. Looks like the developer @moonbutt74 assumed we all had a recovery all ready and did not make an Odin Package!!
If you have a linux machine you could: Extract "recovery.img" from "PhilzAdvCWM-6_55_0-gtP-5210-v2.zip" then do
Code:
tar -H ustar -c recovery.img > recovery.tar
md5sum -t recovery.tar >> recovery.tar
mv recovery.tar recovery.tar.md5
Windows does not allow you to do this easily. Here are some code compile to do that in cigwin. I called it img2tar,
Code:
1) Download and extract the img2tar.rar to your desktop.
2) Navigate to img2tar Folder
3) Open "PhilzAdvCWM-6_55_0-gtP-5210-v2.zip" and using winrar or winzip extract "recovery.img" and place a copy inside img2tar Folder
4) Double click in Runme.bat
5) Now you should see "recovery.tar.md5" witch is a Odin type file.
KK 4.4.2 is a trick Android Rom. If you let the TAB to reboot automatically after you install recovery with Odin, chances are that su or recovery will fail. So I suggest you deselect "Auto Reboot" only let "F.Reset Time" This is not a tutorial in ODIN I suggest anyone read more about it. In particular DO NOT mark "RE-Partition" it is very dangerous. That is there for very Special occasions.
Odin
1) Turn Off your TAB.
2) Run Odin 3.07
3) Hook the cable to the TAB3
4) Press Just [Power]+[Volume Down] this is enogth in my tab. But if you Prefer [Power]+[Volume Down]+[Menu] Your Tab should Show the Warning! Screen and the Yellow Triangle. Nothing should be shown oin Odin yet.
5) As the test read [Volume Up] to Continue. Your Tab3 shows now the Android and read Downloading. Your PC did a "Beep" acnoledging the Driver is ready. Odin now shows in First Slot of "ID:COM" a Blue data that Reads "0:[COMx]" where x is a number for comport. Number does not mater. This tell you ODIN as recognized your Device.
6) Options: Now make sure check-mark ONLY for "F.Reset Time" is selected. Nothing more. Please read my warning before.
7) Files [Download] select check mark of PDA
8) Press PDA and Navigate to where you have your recovery in you case "img2tar\recovery.tar.md5"
9) "Message" window . Odin tell you the status in this window. you should see
Code:
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
So be smart wait!!
10) Then is file is validated you will see
Code:
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> recovery.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS.
11) Now after you see Successful Odin is ready. If you do not see there is something wrong.
12) Now we can press "START"
13) You should see ID:COM with progress bar. TAB3 shows a progress bar too. On top it reads "Recovery". With time you should read in Message
Code:
<ID:0/011> Odin v.3 engine (ID:11)..
<ID:0/011> File analysis..
<ID:0/011> SetupConnection..
<ID:0/011> Initialzation..
<ID:0/011> Get PIT for mapping..
<ID:0/011> Firmware update start..
<ID:0/011> recovery.img
<ID:0/011> NAND Write Start!!
<ID:0/011> RQT_CLOSE !!
<ID:0/011> RES OK !!
14)You need to wait until Blue "Recovery" change to "Reset". Remember TAB3 will not boot automatically since we deselect. So Once we see reset we know it is ready.
15) Now we go to the TAB3 and press [Power]+[Volume UP] to get into recovery. This is important since some time recovery fails if we let the TAB3 reboot in to OS. KitKat bad behavior will screw our recovery on purposed.
16) navigate if you like to see your new recovery
17) Here is what I do different at this time I go and install super su again. This is the only su that we have test that survive Kitkat attack=>http://download.chainfire.eu/452/SuperSU/UPDATE-SuperSU-v2.02.zip
18) Now reboot.
Now I had also attached the files with philz inside. I hope there is no problem. But if for any reason any of the authors complain, I will delete this and/or authorize moderators to do it them self. It is only been done to help AppleAssassin and with the cause in fact that this file is not available in Odin form yet. @moonbutt74 Can you please add to your folder an ODIN type of file for all of your Recoveries. I know many will appreciate that.
But Please note that I have left the ing2tar mechanism so that any can transform their *.img in to tar.md5 and do it them self!
AppleAssassin said:
I'm not complaining about odin. I'm expecting odin to do its job, and it seems to do it but my tab perpetually reboots after I "flash" the file and try to enter recovery mode
Click to expand...
Click to collapse
Forget me for saying "complaining". Be smart. I understood you say you can get in to Recovery! So why use Odin again!!!!
In any case I have provided you the files.
Please Note, I had Test the files my self, but I give no warranties on it used. Do it at your own risk.
Finally uploaded the Philz tar.md5
Code:
http://d-h.st/j6y
As I say as soon any possible author complains I will delete lt. So be quick.
r2d23cpo said:
You are definitely right! I just realized that. Looks like the developer @moonbutt74 assumed we all had a recovery all ready and did not make an Odin Package!!
If you have a linux machine you could: Extract "recovery.img" from "PhilzAdvCWM-6_55_0-gtP-5210-v2.zip" then do
Code:
tar -H ustar -c recovery.img > recovery.tar
md5sum -t recovery.tar >> recovery.tar
mv recovery.tar recovery.tar.md5
Windows does not allow you to do this easily. Here are some code compile to do that in cigwin. I called it img2tar,
Code:
1) Download and extract the img2tar.rar to your desktop.
2) Navigate to img2tar Folder
3) Open "PhilzAdvCWM-6_55_0-gtP-5210-v2.zip" and using winrar or winzip extract "recovery.img" and place a copy inside img2tar Folder
4) Double click in Runme.bat
5) Now you should see "recovery.tar.md5" witch is a Odin type file.
KK 4.4.2 is a trick Android Rom. If you let the TAB to reboot automatically after you install recovery with Odin, chances are that su or recovery will fail. So I suggest you deselect "Auto Reboot" only let "F.Reset Time" This is not a tutorial in ODIN I suggest anyone read more about it. In particular DO NOT mark "RE-Partition" it is very dangerous. That is there for very Special occasions.
Odin
1) Turn Off your TAB.
2) Run Odin 3.07
3) Hook the cable to the TAB3
4) Press Just [Power]+[Volume Down] this is enogth in my tab. But if you Prefer [Power]+[Volume Down]+[Menu] Your Tab should Show the Warning! Screen and the Yellow Triangle. Nothing should be shown oin Odin yet.
5) As the test read [Volume Up] to Continue. Your Tab3 shows now the Android and read Downloading. Your PC did a "Beep" acnoledging the Driver is ready. Odin now shows in First Slot of "ID:COM" a Blue data that Reads "0:[COMx]" where x is a number for comport. Number does not mater. This tell you ODIN as recognized your Device.
6) Options: Now make sure check-mark ONLY for "F.Reset Time" is selected. Nothing more. Please read my warning before.
7) Files [Download] select check mark of PDA
8) Press PDA and Navigate to where you have your recovery in you case "img2tar\recovery.tar.md5"
9) "Message" window . Odin tell you the status in this window. you should see
Code:
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
So be smart wait!!
10) Then is file is validated you will see
Code:
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> recovery.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/011> Removed!!
<ID:0/011> Added!!
11) Now after you see Successfull...Added this means Odin is ready. If you do not see theis something is wrong.
12) Now we can press "START"
13) You should see ID:COM with progress bar. TAB3 shows a progress bar too. On top it reads "Recovery". With time you should read in Message
Code:
<ID:0/011> Odin v.3 engine (ID:11)..
<ID:0/011> File analysis..
<ID:0/011> SetupConnection..
<ID:0/011> Initialzation..
<ID:0/011> Get PIT for mapping..
<ID:0/011> Firmware update start..
<ID:0/011> recovery.img
<ID:0/011> NAND Write Start!!
<ID:0/011> RQT_CLOSE !!
<ID:0/011> RES OK !!
14)You need to wait until Blue "Recovery" change to "Reset". Remember TAB3 will not boot automaticly sinec we deselect. So Once we see reset we know it is ready.
15) Now we go to the TAB3 and press [Power]+[Volume UP] to get into recovery. This is important since some time recovery fails if we let the TAB3 reboot in to OS. KitKat bad behavior will screw our recovery on purposed.
16) navigate if you like to see your new recovery
17) Here is what I do different at this time I go and install super su again. This is the only su that we have test that survive Kitkat attack=>http://download.chainfire.eu/452/SuperSU/UPDATE-SuperSU-v2.02.zip
18) Now reboot.
Now I had also attached the files with philz inside. I hope there is no problem. But if for any reason any of the authors complain, I will delete this and/or authorize moderators to do it them self. It is only been done to help AppleAssassin and with the cause in fact that this file is not available in Odin form yet. @moonbutt74 Can you please add to your folder an ODIN type of file for all of your Recoveries. I know many will appreciate that.
But Please note that I have left the ing2tar mechanism so that any can transform their *.img in to tar.md5 and do it them self!
Forget me for saying "complaining". Be smart. I understood you say you can get in to Recovery! So why use Odin again!!!!
In any case I have provided you the files.
Please Note, I had Test the files my self, but I give no warranties on it used. Do it at your own risk.
Click to expand...
Click to collapse
It works!
It has to work, i am Perfect.
Just kidding. I am glad you resolve your problem. Remember thanks to @moonbutt74 Philz CWM and chainfire that really the guys that make this possible.
r2d23cpo said:
It has to work, i am Perfect.
Just kidding. I am glad you resolve your problem. Remember thanks to @moonbutt74 Philz CWM and chainfire that really the guys that make this possible.
Click to expand...
Click to collapse
I encountered the same problem. Thanks to your solution i could solve it. Thank you very much.
Hello, I rooted with odin and put in philz recovery and had SU 2.02 working but then I wanted to try pimpdroid, so I cleared the data for a fresh install as described and then tried to install pimpdroid...nothing happens just Samsung boot screen forever... Tried to go back to SU still nothing...tried to factory reflash and the same...did I brick this thing somehow or anyone can tell me what to do? It's the Canadian version. Was starting with 4.42.
HELP!! PLEAAAAZE?!?!!?
Related
Hey guys,
The GT-N7100 of my friend does not boot.It is stuck at the first screen ( Black screen with samsung galaxy note II gt-n7100).
He tried to install a custom rom and installed a Custom Recovery. In Custom Recovery the cache partition couldnt be load. So I cant wipe or format anything. If I want to install a zip, the Recovery just get stuck before even selecting a zip file.
I can access download mode. So I tried to flash another recovery. Odin says successful but the recovery is still the same ????
I also tried to flash a stock rom with Odin... nothing changed
So I dont know what to do next
Please help me!
Thanks in advance
Luke44 said:
Hey guys,
The GT-N7100 of my friend does not boot.It is stuck at the first screen ( Black screen with samsung galaxy note II gt-n7100).
He tried to install a custom rom and installed a Custom Recovery. In Custom Recovery the cache partition couldnt be load. So I cant wipe or format anything. If I want to install a zip, the Recovery just get stuck before even selecting a zip file.
I can access download mode. So I tried to flash another recovery. Odin says successful but the recovery is still the same ????
I also tried to flash a stock rom with Odin... nothing changed
So I dont know what to do next
Please help me!
Thanks in advance
Click to expand...
Click to collapse
well flash philz recovery via odin
untick "autoreboot" in odin. Once flash is done, keep pressing power button until it reboots (normally will go to recovery)
when in recovery, if you choose option "reboot system now" and you get "yes - disable flash recovery", select that option to avoid stock recovery overwriting cwm
now proceed with wipe and after flashing rom ,fix permission and wipe cache and dalvic cache twice then reboot
shhbz said:
well flash philz recovery via odin
untick "autoreboot" in odin. Once flash is done, keep pressing power button until it reboots (normally will go to recovery)
when in recovery, if you choose option "reboot system now" and you get "yes - disable flash recovery", select that option to avoid stock recovery overwriting cwm
now proceed with wipe and after flashing rom ,fix permission and wipe cache and dalvic cache twice then reboot
Click to expand...
Click to collapse
I flashed philz recovery. After pressing the power button just the battery symbol appeared... no reboot. So I treid to boot into the new recovery... but still the old recovery boots
Heres the log from Odin:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> philz_touch_5.11.2-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> 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> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/004> Added!!
http://forum.xda-developers.com/showpost.php?p=32273406
I wanted to try this, but this download contains just one file. Even if I extract the tar, there are not the files included which are discribed in the thread...
quite strange....
I simply cant flash anything with Odin. Odin says success, but nothing happened to the phone. I didnt read something about people who are having the same issue
This drives me mad .....
Luke44 said:
http://forum.xda-developers.com/showpost.php?p=32273406
I wanted to try this, but this download contains just one file. Even if I extract the tar, there are not the files included which are discribed in the thread...
quite strange....
I simply cant flash anything with Odin. Odin says success, but nothing happened to the phone. I didnt read something about people who are having the same issue
This drives me mad .....
Click to expand...
Click to collapse
well its not sds for sure so it seems either recovery has gone corrupted as,the pit file u said is not required though u can find it here to http://forum.xda-developers.com/showthread.php?t=1896696 post 4 no4 pit file16gb
but i would suggest you to try the recovery thing as mentioned in the link as see as the one i mentioned is used when it does not enter recovery try this version http://d-h.st/vCc
keep the power button pressed it should enter recovery leave the power button when u see samsung logo
I did it long time back so dont remember exactly whether to keep pressing power button or to hold power button worked for me as auto reboot was not working for me so did the other way round as mentioned to you
shhbz said:
well its not sds for sure so it seems either recovery has gone corrupted as,the pit file u said is not required though u can find it here to http://forum.xda-developers.com/showthread.php?t=1896696 post 4 no4 pit file16gb
but i would suggest you to try the recovery thing as mentioned in the link as see as the one i mentioned is used when it does not enter recovery try this version http://d-h.st/vCc
keep the power button pressed it should enter recovery leave the power button when u see samsung logo
I did it long time back so dont remember exactly whether to keep pressing power button or to hold power button worked for me as auto reboot was not working for me so did the other way round as mentioned to you
Click to expand...
Click to collapse
Im glad to hear that it is not sds.
I tried to flash the recovery of your link:
If I leave the phone connected if I press the power button after flashing just the battery symbol apears after a while.
If I disconnect the phone, it tries to boot normal...no recovery...
If I tap on the power button again and again nothing happens.....
If I try to boot into recovery with the 3 button combo there is still the old clockwork recovery.
I also tried to do a emergency recovery with kies. Kies does download all the files and when it starts to flash it gets stuck at 0 % and sais phone is not connected in the right way but it is...
In Odin mode the phone displays
custom binary downloads : Yes ( 1 counts)
But did flash the recovery at least 3 times ...So why does it still display 1
Luke44 said:
Im glad to hear that it is not sds.
I tried to flash the recovery of your link:
If I leave the phone connected if I press the power button after flashing just the battery symbol apears after a while.
If I disconnect the phone, it tries to boot normal...no recovery...
If I tap on the power button again and again nothing happens.....
If I try to boot into recovery with the 3 button combo there is still the old clockwork recovery.
I also tried to do a emergency recovery with kies. Kies does download all the files and when it starts to flash it gets stuck at 0 % and sais phone is not connected in the right way but it is...
In Odin mode the phone displays
custom binary downloads : Yes ( 1 counts)
But did flash the recovery at least 3 times ...So why does it still display 1
Click to expand...
Click to collapse
do u have kies installed when u trying odin if yes then delete it just install the samsung drivers nothing else and disable your antivirus too.
orelse u may try
thats quite strange ok now its time to try the mskip tool just delete all old samsung drivers and kies
and start fresh from here http://forum.xda-developers.com/showthread.php?t=1923956
and as far as the count in concerned its 1 as you were only able to enter recovery once thats why after that u were not able to so as many times u enter custom recovery the count increases
http://forum.xda-developers.com/showthread.php?t=1896696
Do you think it makes sense todo re-partition with the pit file?
There is also a Bootloader to download on this site...
Luke44 said:
http://forum.xda-developers.com/showthread.php?t=1896696
Do you think it makes sense todo re-partition with the pit file?
There is also a Bootloader to download on this site...
Click to expand...
Click to collapse
i would say no until there is an error which shows no pit partition found but after the above steps if it does not then u can give it a fresh start flash the pit first then the firmware . check youtube as how to do it there are vidoes described on how to flash pit and then the firmware.
i would suggest not to do something which you are not sure of and land urself in other issues though flashing pit and firmware is fine but i am not sure about the bootloader maybe u can ask in that specific thread , keten might be the best person to guide you in that case if its safe
shhbz said:
i would say no until there is an error which shows no pit partition found but after the above steps if it does not then u can give it a fresh start flash the pit first then the firmware . check youtube as how to do it there are vidoes described on how to flash pit and then the firmware.
i would suggest not to do something which you are not sure of and land urself in other issues though flashing pit and firmware is fine but i am not sure about the bootloader maybe u can ask in that specific thread , keten might be the best person to guide you in that case if its safe
Click to expand...
Click to collapse
Sorry but I cant find such a viedo...
Luke44 said:
Sorry but I cant find such a viedo...
Click to expand...
Click to collapse
I tried to flsh this, but odin says:
<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>
<ID:0/003> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
What exact information you can see on Download Mode Rt Upper corner.
post full details here
dr.ketan said:
What exact information you can see on Download Mode Rt Upper corner.
post full details here
Click to expand...
Click to collapse
In the right upper corner is nothing...
In the left upper corner:
ODIN MODE (written in red)
PRODUCT NAME: GT-N7100
CUSTOM BINARY DOWNLOAD: Yes (1 counts)
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
Try different USB port, don't use any extension cable to connect device.
close firewall and still issue try different cable and PC
Download PIT
select it for PIT tab (It will auto select re-partition, keep it selected) - Flash
Also confirm Kies is not running in BG
Luke44 said:
Sorry but I cant find such a viedo...
Click to expand...
Click to collapse
There is I am on phn so would be difficult for me to find but its simple u just select the pit file first in odin and flash keeping ur phn in download mode and then the firmware tar file
Try different USB port, don't use any extension cable to connect device.
close firewall and still issue try different cable and PC
Download PIT
select it for PIT tab (It will auto select re-partition, keep it selected) - Flash
Also confirm Kies is not running in BG
Click to expand...
Click to collapse
I tried a different computer with different cable. On the computer I used this time there is not even kies installed.
Same result as before...
dr.ketan said:
Try different USB port, don't use any extension cable to connect device.
close firewall and still issue try different cable and PC
Download PIT
select it for PIT tab (It will auto select re-partition, keep it selected) - Flash
Also confirm Kies is not running in BG
Click to expand...
Click to collapse
I tried it a few more times..it really doesnt work
Whats wrong with this !"§$%& phone:crying::crying::crying:
Hello,
I rooted my Samsung 5210 using Odin v3.07.
In the message screen it said:
<ID:0/007> RES OK !!
<ID:0/007> Removed!!
<ID:0/007> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/004> Added!!
<ID:0/004> Removed!!
(Also attached a screen shot).
The tablet rebooted, but before I could press Home + Power + Volume Up to enter the Recovery Mode to flash the root zip file, the regular start screen appeared. I rebooted it manually, but since then it's dead - neither pressing the Power or the Home + Power + Volume Up will start the tablet.
Any idea how this can be solved ?
Johi13 said:
Hello,
I rooted my Samsung 5210 using Odin v3.07.
In the message screen it said:
<ID:0/007> RES OK !!
<ID:0/007> Removed!!
<ID:0/007> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/004> Added!!
<ID:0/004> Removed!!
(Also attached a screen shot).
The tablet rebooted, but before I could press Home + Power + Volume Up to enter the Recovery Mode to flash the root zip file, the regular start screen appeared. I rebooted it manually, but since then it's dead - neither pressing the Power or the Home + Power + Volume Up will start the tablet.
Any idea how this can be solved ?
Click to expand...
Click to collapse
Wao, almost 13 hours and no body has answered. There a a few things you have to do to improve the chance you get help. But before let me say a few things.
1) About Your self:
Your record shows 1rst post in xda!
Can you talk about you, your knowledge and skils.
Is this your first android device? Have you done rom modification before? What?
About P5210?
Is your device New? Can you talk about what you had in your device preciously. Most 5210 came with 4.2.2 but it been said that new are coming with 4.4.2? What was yours.
About your Procedure.
What procedure are you following- Please tell us the link? Just as a note If you are following a Link in the web best to do is to request help in the same Link. But never mind lets continue here.
2) You said: "I rooted my Samsung 5210 using Odin v3.07. "
This is strange: Normally we used Odin to install a partition, or going back to stock. So most of the time Odin is used at the beginning to install the a new Recovery CWM, TWRP or new improves like Philz. Afterwards we reboot into Recovery (NOT ODIN) to install the Super SU (root). Then we restart in Android OS and once up we run Super SU and verify it work. The we can say that we are rooted.
But you said "I rooted" So it was rooted or not?
3) Now in the other hand your picture shows you where trying not to root but to Install a TWRP image? a file called "TWRP Recovery\recovery.tar.md5" So we fall back to what procedure are you following and what files?
4)
The tablet rebooted, but before I could press Home + Power + Volume Up to enter the Recovery Mode to flash the root zip file, the regular start screen appeared.
Click to expand...
Click to collapse
This happens because you did not un-Check "Auto Reboot", look at your Odin image.
You said : "regular start screen appeared" . Did you let it boot all the way to Android OS and then did "Power Off"?
I rebooted it manually, but since then it's dead - neither pressing the Power or the Home + Power + Volume Up will start the tablet
Click to expand...
Click to collapse
What is "rebooted it manually"? I guess all reboot are manually, we do have to manually ask the device to reboot? Listen I do not what to be mean. I am trying to show that what you have written is just confusing??
..., but since then it's dead - neither pressing the Power or the Home + Power + Volume Up will start the tablet
Click to expand...
Click to collapse
Here is the MOST disturbing part of you message. Installing a new recovery.img should not had modified your boot-loaders!! The first boot-loader is the one in charge of responding to [Power] or [Home] + [Power] + [Volume Up]
Once you tell us what procedure you are following and what files, we may have an Idea if you use a bad recovery.img. but for now let said you have a bad recovery image.
You should at least bee able to press [Power] for 5 to 8 seconds and release. This will mimic a Battery Removed. then you could do one of two things:
a) Press power and see it reboot and see the Samsung Logo. And it should boot in to OS.
or
b) Or you should be able to press [Home] + [Power] + [Volume Down] in fact you do not need [HOME] in Tab3 just [Power] + [Volume Down].
Then you should see it booting in "Download Mode"
So why are you saying " it's dead" it is disturbing to me.
NOW here is the MOST important part of this. See me response it has at least 10 times more words than you initial request. And clearly it took me 10 times more time to do it. So do you assignment and tell us more info so that we can help you.
r2d23cpo said:
Wao, almost 13 hours and no body has answered. There a a few things you have to do to improve the chance you get help. But before let me say a few things.
1) About Your self:
Your record shows 1rst post in xda!
Can you talk about you, your knowledge and skils.
Is this your first android device? Have you done rom modification before? What?
Click to expand...
Click to collapse
Well, I guess you're right, I should share a bit more info. I have two android devices: a Samsung Galaxy S Duos (S7562) mobile phone and the Samsung Galaxy Tab 3 (GT-P5210). The mobile has been rooted a while ago and caused me no issues.
About P5210?
Is your device New? Can you talk about what you had in your device preciously. Most 5210 came with 4.2.2 but it been said that new are coming with 4.4.2? What was yours.
Click to expand...
Click to collapse
The device is about 9 months old. I'm not sure, but I guess it was on 4.2.2.
About your Procedure.
What procedure are you following- Please tell us the link? Just as a note If you are following a Link in the web best to do is to request help in
the same Link. But never mind lets continue here.
Click to expand...
Click to collapse
I followed those instructions (apparently I am not yet allowed to insert external links as I do not yet have enough posts in this community)
1. Download Odin v3.07 from this link and extract to your computer.
2. Download TWRP Recovery from here and extract it on your computer. Keep extracting the archive until you get recovery.tar.md5 file.
3. Now download Samsung Galaxy Tab 3 10.1 root file from here and transfer the root.zip file to internal memory of the tablet.
4. Turn off the tablet and press Home+Power+Volume down button simultaneously until you get to a warning screen. Release the buttons and press Volume up button to continue. When the tablet is in download mode, connect it to the computer using USB cable.
5. Start Odin and click on PDA button then select the file “recovery.tar.md5″.
6. On the Odin window make sure “Re-partition” is unchecked.
7. Now click on the Start button to root Samsung Galaxy Tab 3 10.1.
8. Once the flashing process is complete the tablet will reboot.
9. When the tablet is rebooting press Home+Power+Volume up button to enter Recovery mode. From the TWRP recovery flash the root.zip file and reboot the tablet.
I could complete the procedure up to step 9. After reboot I missed to press Home & Power & Volume and it booted regularly. Afterwards I tried to catch up with the missing step, tried to reboot the device but it never came up again.
2) You said: "I rooted my Samsung 5210 using Odin v3.07. "
This is strange: Normally we used Odin to install a partition, or going back to stock. So most of the time Odin is used at the beginning to install the a new Recovery CWM, TWRP or new improves like Philz. Afterwards we reboot into Recovery (NOT ODIN) to install the Super SU (root). Then we restart in Android OS and once up we run Super SU and verify it work. The we can say that we are rooted.
But you said "I rooted" So it was rooted or not?
Click to expand...
Click to collapse
See above.
3) Now in the other hand your picture shows you where trying not to root but to Install a TWRP image? a file called "TWRP Recovery\recovery.tar.md5" So we fall back to what procedure are you following and what files?
Click to expand...
Click to collapse
See above.
4) This happens because you did not un-Check "Auto Reboot", look at your Odin image.
You said : "regular start screen appeared" . Did you let it boot all the way to Android OS and then did "Power Off"?
Click to expand...
Click to collapse
See above.
Here is the MOST disturbing part of you message. Installing a new recovery.img should not had modified your boot-loaders!! The first boot-loader is the one in charge of responding to [Power] or [Home] + [Power] + [Volume Up]
Once you tell us what procedure you are following and what files, we may have an Idea if you use a bad recovery.img. but for now let said you have a bad recovery image.
You should at least bee able to press [Power] for 5 to 8 seconds and release. This will mimic a Battery Removed. then you could do one of two things:
a) Press power and see it reboot and see the Samsung Logo. And it should boot in to OS.
or
b) Or you should be able to press [Home] + [Power] + [Volume Down] in fact you do not need [HOME] in Tab3 just [Power] + [Volume Down].
Then you should see it booting in "Download Mode"
Click to expand...
Click to collapse
I tried this now several times, nothing happens.
Should you need more information, then please let me know.
thanks!
@Johi13
From you simplistic way of answer this is what I got.
*Your experience: I guess you may not be experienced but had done Recovery Installation and root in the past. This is good. I guess then you know what you are doing.
*Your device: "The device is about 9 months old" , I too also believe should had been 4.2.2 originally. So that root out any weird 4.4.2 bootloaders
*Your procedure:??? The procedure shown seems ok except for the 7 instruction:
7. Now click on the Start button to root Samsung Galaxy Tab 3 10.1.
Click to expand...
Click to collapse
should read instead
7. Now click on the Start button to send new recovery to Samsung Galaxy Tab 3 10.1.
Click to expand...
Click to collapse
It my be true that you can not post links. In fact NONE of us should past live links. We can always use one of many alternatives. lets say i want to place this link but I am not allowed:
http://forum.xda-developers.com/showthread.php?t=2442915
So I can do this
Code:
Samsung Galaxy Tab 3 > Galaxy Tab 3 10.1 Android Development > [RECOVERY][TWRP_2.7] SGT3 Recovery[FINAL]
or I can do this
Code:
Please google "[RECOVERY][TWRP_2.7] SGT3 Recovery[FINAL]"
or I can do this:
Code:
h__p://forum.xda-developers.com/showthread.php?t=2442915
Then we here can look and read and inspect the files.
But it does not matter lets assume all is OK. Procedure seems OK and lets say Files are Ok.
You have said
" I rebooted it manually, but since then it's dead - neither pressing the Power or the Home + Power + Volume Up will start the tablet."
"tried to reboot the device but it never came up again"
THIS IS THE IMPORTANT.
I
Installing a new recovery.img should not had modified your boot-loaders!! The first boot-loader is the one in charge of responding to [Power] or [Home] + [Power] + [Volume Up]
Click to expand...
Click to collapse
So this means
You should at least bee able to press [Power] for 5 to 8 seconds and release. This will mimic a Battery Removed. then you could do one of two things:
a) Press power and see it reboot and see the Samsung Logo. And it should boot in to OS.
or
b) Or you should be able to press [Home] + [Power] + [Volume Down] in fact you do not need [HOME] in Tab3 just [Power] + [Volume Down].
Then you should see it booting in "Download Mode"
Click to expand...
Click to collapse
But your response is just:
I tried this now several times, nothing happens.
Click to expand...
Click to collapse
I can not help you any more except suggest you the following:
You could have a broken button like the [Power] ! If the buttons do not work it can not Boot-up.
You may have a Battery with to little juice! Hook it to an outlet ans see if it take charge.
Apart from that you may have damage you boot loading partition!! If this happens there is little we can do. It requires then Specialize service that almost only Samsung can provide such as Jtag or something similar. There is in some Samsung devices that have a Hardware option that when the bootloaders can not be reach it then try to boot from External SDCARD, I have no Idea is this is the case of Tab3 10.
@Johi13
Just a thought, If you could disconnect the battery, and reconnect, you may be able to press just [Volume Down] and see the Battery Icon.
Then you may be able to follow similar instructions.
http://forum.xda-developers.com/showpost.php?p=55270064&postcount=2
Please post results if that works.
I purchased a used Samsung Galaxy Tab S 10.5 on ebay. Originally it had Android 4.4.2
When I turned it on the device is in retail demo mode.
I have tried the following
1) passwords found on this forum such as (5444, M729Q16K8546, blue, unlimited, easy, galaxy)
2) none of these worked
3) Can not deselect "samsung retail mode" in settings/security/administrators
I tried updating to android 6.0.1 by doing the following but the retail mode is still there
It will not enter into download mode so I did the following
1) Enabled developer options on tablet
2) Used command "adb reboot download"
3) Installed Android 6.0.1 stock rom (T800XXU1CPH7_T800XAR1CPH4_XAR.zip) from sammobile.com
4) Tablet installed and updated Android
5) Retail mode is still there and I still can not get rid of it
Any suggestions are greatly appreciated
Thanks
Never had a retail demo device so my answer may be limited.
Did you tried/are able to install TWRP ?
If you can get TWRP you can try to make a complete factory wipe (Advanced Wipe > check all the boxes > wipe)
Then reboot to download mode (Reboot > Download)
Install the stock rom again
Here is the link: https://forum.xda-developers.com/ga...p-2-8-6-1-unofficial-sm-t800-805-807-t3074633
Flash it via odin
I have tried to do TWRP but can not get it to work. I did not use the apk I was using ODIN on my pc. I was using a TWRP file twrp_3.0.0-0_T800. Not sure if that was the issue or not.
Here are the steps I used:
1) put phone into download mode by using adb on pc (adb reboot download)
2) In ODIN
a) turn off autop reboot
b) select AP file twrp_3.0.0-0_T800
c) wait for success in ODIN
3) tablet never rebooted so I used these keys (press at same time until reboot power+vol down+vol up+home)
4) Tablet rebooted into normal running mode
If you don't enter in recovery right away you flash it the system will revert the changes back. so if the system start to boot normally you need to flash via odin again.
I recommend you to flash the version i linked, as it is more compatible with MM bootloader, also turning off auto reboot is a very important thing.
You need to press all the buttons together power+vol down+vol up+home, (press power last) . when the screen light up release the volume up button (the next to power button) and keep holding the rest.
also...
You can try one trick that i use sometimes, it will give you more time to make the key combination, connect the device to the charger and press and hold power+vol up until the screen turn off, it may show a battery icon, so you disconnect the charger and wait the icon go away. the device should be turned off now. so you basically press and hold vol down+home+power (press power last)
If you done the combination correctly and the screen became black, don't worry, it is a bug, just wait some time (1 min i think) and press home key, it should show the recovery.
It can be a pain in the a** sometimes... but trust me, it generally works.
Ok, so far so good. It took a while but I got into TWRP. But I can't seem to select the image file.
I have it on an external MicroSD in the root. File is called T800XXU1CPH7_T800XAR1CPH4_XAR.zip
I can browse files on the list on the left. But I can't seem to find the file
Did I miss a step?
Somehow after going through menus, it recognized the file
But when I tried to install it, I got these errors
Zip Signature verification failed!
Error installing zip file /sdcard/download/T800XXU1CPH7_T800ZXAR1CPH4_XAR.zip
Could not find 'META-INF/com/google/android/update-binary' in zip file
Error installing zip file /sdcard/download/T800XXU1CPH7_T800ZXAR1CPH4_XAR.zip
you got me wrong, in the TWRP what you need to do is make a complete wipe (Wipe > Advanced Wipe > check all the boxes > wipe)
then you need to enter in download mode. (Reboot > Download)
and flash the rom via odin!
extract the zip on your pc, it should be a .Tar file, select AP mode on odin, select the .tar and flash it in there.
I apologize for the confusion. Those steps worked!!
I think part of the problem is that I did not extract the firmware file. I kept trying to flash the TAR file.
I did a wipe in TWRP
Then rebooted into download mode
Flashed extracted firmware file in ODIN in AP Box
Then the tablet rebooted and was in setup mode like a brand new tablet!! Who hoo.
Works great
Thanks for all the help
Hi everyone.
I accidentally disable an option at debug settings OEM i think, well i disabled all debug setting (I did not even know that would kill my phone) and when restart my phone later a message says "Custom binary locked by FRP" here is the problem, i downloaded my correct firmware SM-G920P XXXPI3 (From sammobile) and Odin 1.85, when enter into download mode Odin say:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G920PVPS4CPI3_G920PSPT4CPI3_G920PVPS4CPI3_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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
But when i open Odin3 3.11.1 a message say:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G920PVPS4CPI3_G920PSPT4CPI3_G920PVPS4CPI3_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..
and stuck at "SETUPCONNECTION"
Also in my phone appears this:
Product name: SM-G920P
Current binary: Custom
System status: Custom
Frp lock: ON
Secure download: Enabled
Knox warranty void: 1 (0x0500) So support center is not a choice
RP SWERV: B4 K2 S3
i already tried install, uninstall, reinstall drivers, change usb cables, dont connect to a usb hub. i dont have try Smart switch and Kies yet because i dont have the serial number.
Any help? please somebody tell me there is a hope :crying: i just bought this phone 2 weeks ago
Go here and get the latest files: https://forum.xda-developers.com/sp...uide-links-files-update-root-restore-t3366862
Download a more recent version of Odin. 3.10.7 should be fine.
Download the most recent TAR file, which is QB1. I link to a much faster and more stable download page than Sammobile. The TAR file that you are using is from 2016.
Try again and it should work.
koop1955 said:
Go here and get the latest files: https://forum.xda-developers.com/sp...uide-links-files-update-root-restore-t3366862
Download a more recent version of Odin. 3.10.7 should be fine.
Download the most recent TAR file, which is QB1. I link to a much faster and more stable download page than Sammobile. The TAR file that you are using is from 2016.
Try again and it should work.
Click to expand...
Click to collapse
¡THANK YOU VERY MUCH, IT WORKS! i could flashed and now i can used
Same problem for my j200h
Any one could help me plzzzz....
I downloaded various types of firmwares but
This all stucks at setup connection
So please help......
Iam trying this since 3 days
I hope xda could help me......
farhanfarru said:
I downloaded various types of firmwares but
This all stucks at setup connection
So please help......
Iam trying this since 3 days
I hope xda could help me......
Click to expand...
Click to collapse
Hi, I'm on the SM-G930W8 variant but this should work for you too if you are running exynos!
Make sure you are running odin version: v3.13.1.
Steps:
1. Right Click, start Odin as Administrator.
2. Select files required.
3. Untick Auto-Reboot and Untick F. Reset Time
4. Put your device into download mode from power off. Do not plug in your device to the computer until you have added the files you wish to flash.
5. Make sure Odin successfully sees your device (you should see COM:<number>).
6. Click Start.
7. Your device will get stuck on the SetupConnection step.
8. Hold POWER + Vol DOWN + HOME until you see the download screen again. This will reboot your device into download mode.
9. Now unplug the device and plug it in again and flash the file.
10. Profit!
Drop a thanks if this helped!
appledoor said:
Hi, I'm on the SM-G930W8 variant but this should work for you too if you are running exynos!
Make sure you are running odin version: v3.13.1.
Steps:
1. Right Click, start Odin as Administrator.
2. Select files required.
3. Untick Auto-Reboot and Untick F. Reset Time
4. Put your device into download mode from power off. Do not plug in your device to the computer until you have added the files you wish to flash.
5. Make sure Odin successfully sees your device (you should see COM:<number>).
6. Click Start.
7. Your device will get stuck on the SetupConnection step.
8. Hold POWER + Vol DOWN + HOME until you see the download screen again. This will reboot your device into download mode.
9. Now unplug the device and plug it in again and flash the file.
10. Profit!
Drop a thanks if this helped!
Click to expand...
Click to collapse
Amazing, it actually worked! How in the world did you figure that out? Such a weird sequence of steps. I was at my wits end and this was the only thing that worked, so thanks!
Thank you! Those exact sequence of steps worked for me too!
That worked for me as well ! Thanks !!!
You ****ing saved my life <33
man you are a savior!
thank you so much.
it's 1 am and i was so much frustrated due to this.
thanks man
---------- Post added at 01:16 AM ---------- Previous post was at 01:13 AM ----------
appledoor said:
Hi, I'm on the SM-G930W8 variant but this should work for you too if you are running exynos!
Make sure you are running odin version: v3.13.1.
Steps:
1. Right Click, start Odin as Administrator.
2. Select files required.
3. Untick Auto-Reboot and Untick F. Reset Time
4. Put your device into download mode from power off. Do not plug in your device to the computer until you have added the files you wish to flash.
5. Make sure Odin successfully sees your device (you should see COM:<number>).
6. Click Start.
7. Your device will get stuck on the SetupConnection step.
8. Hold POWER + Vol DOWN + HOME until you see the download screen again. This will reboot your device into download mode.
9. Now unplug the device and plug it in again and flash the file.
10. Profit!
Drop a thanks if this helped!
Click to expand...
Click to collapse
man you are a savior!
thank you so much.
it's 1 am and i was so much frustrated due to this.
thanks man
Thanks a lot
I Love You man, really. You saved me.
Spent so much time and can only find your solution to work. God bless you
appledoor said:
Hi, I'm on the SM-G930W8 variant but this should work for you too if you are running exynos!
Make sure you are running odin version: v3.13.1.
Steps:
1. Right Click, start Odin as Administrator.
2. Select files required.
3. Untick Auto-Reboot and Untick F. Reset Time
4. Put your device into download mode from power off. Do not plug in your device to the computer until you have added the files you wish to flash.
5. Make sure Odin successfully sees your device (you should see COM:<number>).
6. Click Start.
7. Your device will get stuck on the SetupConnection step.
8. Hold POWER + Vol DOWN + HOME until you see the download screen again. This will reboot your device into download mode.
9. Now unplug the device and plug it in again and flash the file.
10. Profit!
Drop a thanks if this helped!
Click to expand...
Click to collapse
Hello everyone please how can I get android version 7 firmware for my galaxy a7100 2016
appledoor said:
Hi, I'm on the SM-G930W8 variant but this should work for you too if you are running exynos!
Make sure you are running odin version: v3.13.1.
Steps:
1. Right Click, start Odin as Administrator.
2. Select files required.
3. Untick Auto-Reboot and Untick F. Reset Time
4. Put your device into download mode from power off. Do not plug in your device to the computer until you have added the files you wish to flash.
5. Make sure Odin successfully sees your device (you should see COM:<number>).
6. Click Start.
7. Your device will get stuck on the SetupConnection step.
8. Hold POWER + Vol DOWN + HOME until you see the download screen again. This will reboot your device into download mode.
9. Now unplug the device and plug it in again and flash the file.
10. Profit!
Drop a thanks if this helped!
Click to expand...
Click to collapse
It's 2021, and even on an S21 Ultra, these steps more or less worked for me (because I have no dedicated home button, I simply turned the phone off completely, did the VOL UP + VOL DOWN while plugging in USB method to get to Download mode, and then pressed "START" again, and off it went.
Thank you very much.
appledoor said:
Hi, I'm on the SM-G930W8 variant but this should work for you too if you are running exynos!
Make sure you are running odin version: v3.13.1.
Steps:
1. Right Click, start Odin as Administrator.
2. Select files required.
3. Untick Auto-Reboot and Untick F. Reset Time
4. Put your device into download mode from power off. Do not plug in your device to the computer until you have added the files you wish to flash.
5. Make sure Odin successfully sees your device (you should see COM:<number>).
6. Click Start.
7. Your device will get stuck on the SetupConnection step.
8. Hold POWER + Vol DOWN + HOME until you see the download screen again. This will reboot your device into download mode.
9. Now unplug the device and plug it in again and flash the file.
10. Profit!
Drop a thanks if this helped!
Click to expand...
Click to collapse
Wow. Amazing this worked! I was having this problem with my S20 FE 5G and it completely worked. I held VOLUME UP + VOLUME DOWN + POWER and then continued to hold VOLUME UP + VOLUME down and it booted into download mode. I didn't have to unplug. Thanks a ton!
appledoor said:
Hi, I'm on the SM-G930W8 variant but this should work for you too if you are running exynos!
Make sure you are running odin version: v3.13.1.
Steps:
1. Right Click, start Odin as Administrator.
2. Select files required.
3. Untick Auto-Reboot and Untick F. Reset Time
4. Put your device into download mode from power off. Do not plug in your device to the computer until you have added the files you wish to flash.
5. Make sure Odin successfully sees your device (you should see COM:<number>).
6. Click Start.
7. Your device will get stuck on the SetupConnection step.
8. Hold POWER + Vol DOWN + HOME until you see the download screen again. This will reboot your device into download mode.
9. Now unplug the device and plug it in again and flash the file.
10. Profit!
Drop a thanks if this helped!
Click to expand...
Click to collapse
I dont know how the hell this worked but you helped me unbrick my tab 3 lite stuck on a firmware upgrade encountered an error page! Thank you so much, you're a lifesaver!!
Hi
I have a new SM-G988B/DS and try to flash a Magisk patched AP file to get root access.
Unfortuantly ODIN get stuck at modem_debug.bin.
I followed this instruction and downloaded images from Sammobile.
How to Root Galaxy S20/S20+/S20 Ultra using Magisk - A Complete Guide
A comprehensive step-by-step guide to unlock the bootloader and root Samsung Galaxy S20, S20+, and S20 Ultra using Magisk, without TWRP.
www.thecustomdroid.com
I compared md5, no data corrupted.
Magisk 25.2, Odin engine v(ID:3.1401
When I flash the unpached AP file the phone boot normal to setup screen.
So I assume that magisks patch did something wrong.
I`m using the following files:
BL_G988BXXUFGVL5_G988BXXUFGVL5_MQB60138112_REV01_user_low_ship_MULTI_CERT.tar.md5
CP_G988BXXUFGVL5_CP23411210_MQB60138112_REV01_user_low_ship_MULTI_CERT.tar.md5
CSC_OXM_G988BOXMFGVL5_MQB60138112_REV01_user_low_ship_MULTI_CERT.tar.md5
HOME_CSC_OXM_G988BOXMFGVL5_MQB60138112_REV01_user_low_ship_MULTI_CERT.tar.md5
dont work:
magisk_patched-25200_WgJpi.tar
work:
AP_G988BXXUFGVL5_G988BXXUFGVL5_MQB60138112_REV01_user_low_ship_MULTI_CERT_meta_OS13.tar.md5
Ondin Log:
Code:
<ID:0/005> recovery.img
<ID:0/005> dtbo.img
<ID:0/005> super.img
<ID:0/005> userdata.img
<ID:0/005> vbmeta.img
<ID:0/005> vbmeta_samsung.img
<ID:0/005> dqmdbg.img
<ID:0/005> misc.bin
<ID:0/005> boot.img
<ID:0/005> modem.bin
<ID:0/005> modem_debug.bin
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
Does anyone has an idea how to solve this?
Thanks a lot!
Just flash magisk through twrp.
Hi
I downloaded https://dl.twrp.me/twrpapp/me.twrp.twrpapp-26.apk.html / twrp-3.7.0_11-0-z3s.img.tar
Select the file as AP in Odin, but I get an error "Complete(Write) operation failed"
I followed this guide:
Install TWRP on Samsung Galaxy S20, S20+ or S20 Ultra (Exynos)
In this detailed turorial, we will show you how to install TWRP Recovery on Samsung Galaxy S20, S20+, or S20 Ultra Exynos variant.
www.getdroidtips.com
I also detected that the device has a Czech CSC, so I downloaded the Czech Images -> same error modem_debug.bin failed, but without magisk patch the device boots normal.
Thanks for your help!
Here's how to root it:
note: phone must be plugged into the computer throughout the process.
1. Download the firmware and extract it. You'll have the AP, BL, CP, CSC files
2. boot to download mode
3. Open up Odin and add AP, BL, CP, CSC and in USERDATA add the twrp (attached below)
4. Untick Auto Reboot in Options then Start.
5. Once done, hold power + vol down till the screen goes off then quickly hold power + vol up till twrp pops up.
6. When you're in twrp, format data then flash samsung multidisabler and magisk.zip (attached below)
7. Reboot to system.
edit: DON'T use patched AP.
edit2: OEM unlock must be on. It's in developer option.
Wow thanks for your detailed answer I will try this now!
Just to ensure: untick auto reboot means the checkbox shall not be selected? because all odin screenshots and videos show a selected checkbox. Don't want to brick it. Thanks
Wow very big thanks for your help, it work!
Is there any way to send you a donation for your effort?
luki1000 said:
Wow very big thanks for your help, it work!
Is there any way to send you a donation for your effort?
Click to expand...
Click to collapse
Nah man, no need. Happy to help
HarizNaim said:
Here's how to root it:
note: phone must be plugged into the computer throughout the process.
1. Download the firmware and extract it. You'll have the AP, BL, CP, CSC files
2. boot to download mode
3. Open up Odin and add AP, BL, CP, CSC and in USERDATA add the twrp (attached below)
4. Untick Auto Reboot in Options then Start.
5. Once done, hold power + vol down till the screen goes off then quickly hold power + vol up till twrp pops up.
6. When you're in twrp, format data then flash samsung multidisabler and magisk.zip (attached below)
7. Reboot to system.
edit: DON'T use patched AP.
Click to expand...
Click to collapse
for me userdata for TWRP never works phone gets stuck in download mode in the end of the flashing.
So i follow official guideline from TWRP topic to make it work
Open Odin v3.14.1 and place the downloaded TWRP .tar file in AP tab, downloaded vbmeta .tar file in CP tab and click Start - once you press start grab the phone and press vol up + power to force it boot straight in TWRP after flashing
Click to expand...
Click to collapse
contrinsan said:
for me userdata for TWRP never works phone gets stuck in download mode in the end of the flashing.
So i follow official guideline from TWRP topic to make it work
Click to expand...
Click to collapse
Did you flash twrp with the firmware? My phone only get stuck when I flash twrp in userdata without the firmware.
I added the complete firmware to odin and TWRP to userdata. Flash all together. That worked for me.
tricky part was pressing the correct button after flash is complete (power +up)
HarizNaim said:
Here's how to root it:
note: phone must be plugged into the computer throughout the process.
1. Download the firmware and extract it. You'll have the AP, BL, CP, CSC files
2. boot to download mode
3. Open up Odin and add AP, BL, CP, CSC and in USERDATA add the twrp (attached below)
4. Untick Auto Reboot in Options then Start.
5. Once done, hold power + vol down till the screen goes off then quickly hold power + vol up till twrp pops up.
6. When you're in twrp, format data then flash samsung multidisabler and magisk.zip (attached below)
7. Reboot to system.
edit: DON'T use patched AP.
Click to expand...
Click to collapse
Bro a question the boot loader from de Download mode needs to be unlocked because, I tried that a time but the phone said only official image or recovery is allowed to flash
ZoldierZ21 said:
Bro a question the boot loader from de Download mode needs to be unlocked because, I tried that a time but the phone said only official image or recovery is allowed to flash
Click to expand...
Click to collapse
Oh yeah forgot about that. Just turn on OEM unlock in developer option.
Hi everyone I have a doubt about a SM-G988B I have one but it`s locked by the network and I see the OEM unlock appear in it but when I try to flash any custom rom I got a problem with the recovery, and the updates appear when I do a downgrade to android twelve
HarizNaim said:
Oh yeah forgot about that. Just turn on OEM unlock in developer
Click to expand...
Click to collapse
i will do it again and i will send you a picture of what it do
luki1000 said:
Wow very big thanks for your help, it work!
Is there any way to send you a donation for your effort?
Click to expand...
Click to collapse
what model you have the same of us o another
ZoldierZ21 said:
what model you have the same of us o another
Click to expand...
Click to collapse
*#1234#
AP G988BXXUFHWAK
CP G988BXXUFHWAK
CSC G988BOXMFHWAK
SM-G988B/DS
128GB /12Gb Ram S20 Ultra 5G black
Purchased from Amazon, I guess its a Czech version. https://www.amazon.de/dp/B084K6P9HP/ref=pe_27091401_487024491_TE_item
Your OEM settings screenshot look identical to mine.
luki1000 said:
*#1234#
AP G988BXXUFHWAK
CP G988BXXUFHWAK
CSC G988BOXMFHWAK
SM-G988B/DS
128GB /12Gb Ram S20 Ultra 5G black
Purchased from Amazon, I guess its a Czech version. https://www.amazon.de/dp/B084K6P9HP/ref=pe_27091401_487024491_TE_item
Your OEM settings screenshot look identical to mine.
Click to expand...
Click to collapse
what version of android you have
ZoldierZ21 said:
what version of android you have
Click to expand...
Click to collapse
13
ZoldierZ21 said:
what version of android you have
Click to expand...
Click to collapse
ok ok i pull on its working now
HarizNaim said:
Here's how to root it:
note: phone must be plugged into the computer throughout the process.
1. Download the firmware and extract it. You'll have the AP, BL, CP, CSC files
2. boot to download mode
3. Open up Odin and add AP, BL, CP, CSC and in USERDATA add the twrp (attached below)
4. Untick Auto Reboot in Options then Start.
5. Once done, hold power + vol down till the screen goes off then quickly hold power + vol up till twrp pops up.
6. When you're in twrp, format data then flash samsung multidisabler and magisk.zip (attached below)
7. Reboot to system.
edit: DON'T use patched AP.
edit2: OEM unlock must be on. It's in developer option.
Click to expand...
Click to collapse
it works now but a question what have to seeing the auto reboot at all