I'm trying to install TWRP on my Galaxy tab 3 10.1 (Model GT-P5210) using ODIN v3.13.1 which is currently running stock everything. Before trying to install I enabled USB debugging. I did not unlock the bootloader before attempting to install TWRP using ODIN. I do not know how to tell if I have an unlocked bootloader or how to unlock it.
I am installing the version listed here: https://forum.xda-developers.com/ga...covery-twrp-3-x-samsung-galaxy-tab-3-t3340938
I am using the version labelled FLASH WITH ODIN: Galaxy Tab 3 10.1 Wifi: GT-P5210
The file I downloaded is called "twrp-3.0.2-0-santos10wifi.tar.md5"
The first time I tried I left "Auto Reboot" option selected in ODIN. Odin said "PASS!" and booted into Android. When it finished loading I powered off the device and booted to recovery, but it booted to stock recovery, not TWRP.
I read that some people have this problem and that it is fixed by deselecting "Auto Reboot" in Odin. I did that, but after ODIN said "PASS!", I tried to restart the device but was unable to. I tried every possible button combination for 30+ seconds, including combinations that are supposed to simulate disconnecting the battery, but the device did not respond to anything at all. After growing desperate, I flashed TWRP in ODIN again, but selected "Auto Reboot" as this seems to be the only way to get the device to respond after flashing with ODIN. Booting into recovery after this led to stock recovery again. Again I tried flashing with "Auto Reboot" deselected. I again could not restart the phone. After trying to flash again using "Auto Reboot" the flash process got stuck. At this point I could not do anything to get the phone to restart. Eventually I figured out how to get the back cover off and I had to manually disconnect the battery. After reconnecting the battery the device booted into Android just fine and now I am letting it charge.
How can I get TWRP to flash correctly?
I got it to work by selecting the "Auto Reboot" option in Odin, but booting into recovery manually and quickly after the package was installed, but before it had time to boot into android.
I think were having the same issue...
IT WORKED TO ME, TOO! Thanks!
After install the TWRP file via Odin (I installed the file CF-Auto-Root-santos10wifi-santos10wifixx-gtp5210.zip in chainfire.eu domain), the Android restart and THIS is the moment to open the recovery mode: press the power and volume down, and when appear de logo in the screen, release the power button and maintain de volume down.
the_angel_moroni said:
I got it to work by selecting the "Auto Reboot" option in Odin, but booting into recovery manually and quickly after the package was installed, but before it had time to boot into android.
Click to expand...
Click to collapse
Related
I was using PA rom for a few months and everything was fine until my gnex suddenly bootloop for no reason. Wasn't flashing a new rom, or tweaking anything. Phone just crash and when i try to reboot it, it just stuck in a bootloop. Showing google, then animation screen and afterwards reboot again back to google and animation and keeps repeating.
Phone info:
-rooted
-bootloader unlocked
-on custom rom (PA ROM)
Attempt to fix problem:
-flash a diff rom ( still boot loop )
-factory reset,wipe system cache etc. ( still boot loop )
-flash factory image 4.3 ( still boot loop ) [All is done through adb, manually flash each radio,bootloader, system etc one by one ]
-flash factory image 4.0 ( still boot loop )
So currently i'm on stock android, stock recovery, stock bootloader, stock baseband etc. But it is still bootlooping, anyone know what can i do?
ps, i did search through the forum, most people got pass this problem through flashing stock image, but mine doesn't
did you erase and then flash userdata?
Similar to my problem, hope it someone knows an answer.
Same problem!
Not to hijack your thread, but I'm having the same problem -
My phone was charging and working fine. I left the room and came back and the phone was stuck at the "Google" bootloader screen. I pulled the battery and reinserted. It went to the Cyanagen boot animation, then froze. Subsequent battery pulls resulted in it freezing at the Google screen.
I can not access recovery (power + vol up + vol down), but I can access the Odin download screen (power + vol down). Odin will connect to my phone, but I can't reflash the stock firmware. After attempting to flash the firmware my phone shows the phone-triangle-computer screen regardless of what buttons I push during start up. I can still connect to Odin, but can't reflash stock. I receive the "complete write failure" message each time. I've tried switching USB ports and USB cords without success.
Sprint SPH 700
Rooted with bootloader unlocked
Running Cyanagen ROM
Any tips? Do I need to reload the PIT file? Thank you!
TSRibeye said:
Not to hijack your thread, but I'm having the same problem -
My phone was charging and working fine. I left the room and came back and the phone was stuck at the "Google" bootloader screen. I pulled the battery and reinserted. It went to the Cyanagen boot animation, then froze. Subsequent battery pulls resulted in it freezing at the Google screen.
I can not access recovery (power + vol up + vol down), but I can access the Odin download screen (power + vol down). Odin will connect to my phone, but I can't reflash the stock firmware. After attempting to flash the firmware my phone shows the phone-triangle-computer screen regardless of what buttons I push during start up. I can still connect to Odin, but can't reflash stock. I receive the "complete write failure" message each time. I've tried switching USB ports and USB cords without success.
Sprint SPH 700
Rooted with bootloader unlocked
Running Cyanagen ROM
Any tips? Do I need to reload the PIT file? Thank you!
Click to expand...
Click to collapse
I finally got thru the phone to pc fail screen by using a older version of Odin(3.04).Then the flash went thru w/o a hitch. Is your PC recognizing the Phone? If not the drivers may need to be uninstalled and reinstalled. I had to use the samsung usb cord and no other also.
Zepius said:
did you erase and then flash userdata?
Click to expand...
Click to collapse
yup i did that....fastboot erase userdata and also fastboot erase data. still boot loops
Flash factory image via fastboot,
Sent from my maguro using xda app-developers app
bunodosoma said:
I finally got thru the phone to pc fail screen by using a older version of Odin(3.04).Then the flash went thru w/o a hitch. Is your PC recognizing the Phone? If not the drivers may need to be uninstalled and reinstalled. I had to use the samsung usb cord and no other also.
Click to expand...
Click to collapse
Yup, my PC recognizes the phone. I can push partial tar files (for example, recovery only) to the phone just fine. I'll try a different version of Odin. Thanks!
(Originally posted this in the wrong forum, so I am reposting here.)
I have the Galaxy Note II with T-Mobile.
Some background: It was running Android 4.1.2. I rooted my phone once, about two weeks ago, just so I could take an image of it in case of an update issue. (I think the software was called nandroid.) Once I took the backup, I unrooted it again.
Since then, doing the Software Update check under settings never returned any results. It would just keep checking until I clicked cancel.
Anyway, when T-Mobile released the 4.3 update Monday morning, I tried updating to it using the Kies software on my PC (by connecting it through the USB cable). It got up to about 60% installation and then just hung for over an hour. So I unplugged the phone, re-plugged it back in, and then attempted the emergency firmware recovery through Kies. It went through this and got upto 76% installation and then just hung again for another hour. I again unplugged it to re-try the emergency recovery again, but every time I connected the phone, Kies would not detect it again. I re-seated the battery, rebooted my computer, uninstalled and reinstalled Kies, but Kies would not detect my phone again.
I am/was running the stock rom, but my phone won't even boot into it's normal screen. Any time I turn it again, i see the screen--"there were errors during firmware upgrade. try emergency recovery in Kies."
I can't even figure out a way to get to a screen where I can install the image I took using Nandroid a few weeks ago.
Any help or advice anyone can provide would be extremely appreciated!
Use Odin to fix it.
If you can put your phone into download mode then it should be 'saveable' ..
Double0EK said:
Use Odin to fix it.
If you can put your phone into download mode then it should be 'saveable' ..
Click to expand...
Click to collapse
I am able to put it into download mode. When I follow the instructions I found for Odin, the process seems to go smoothly. However, once my phone reboots, it stays on the "Samsung Galaxy Note II" screen (with the black background). I've left it like that for over 30 minutes, and it just stays on that screen.
Should there be another step I should be following?
diggeryo said:
I am able to put it into download mode. When I follow the instructions I found for Odin, the process seems to go smoothly. However, once my phone reboots, it stays on the "Samsung Galaxy Note II" screen (with the black background). I've left it like that for over 30 minutes, and it just stays on that screen.
Should there be another step I should be following?
Click to expand...
Click to collapse
Try installing SuperSU from Playstore
It has an option of doing a FULL UNROOT
I am sure that will help.
If not then install Rom Manager from PS
Through RomManager reboot in Recovery
1.) Wipe device 3x times
2.) Wipe cache 3x times
3.) Under advance you will Find Dalvik Cache -- wipe that 3x times
[MENTION=522570 [MENTION=1065870 [user=1879310]@@@@[/user][/MENTION]@@[/MENTION]@@
But more importantly why would you want 4.3 stock anyway?
Install TWRP Recovery or ClockWorkMod recovery and install/Flash CM1 (Cyagonemod) or any other custom roms 4.4.x kitkat
Nothing is really working for me.
I can't boot into normal mode. I am able to get into "download" mode, but whenever I try to load an image using the Odin software (both a stock image and a Cyagonemod image), it starts to load the image, but just hangs a certain percent of the way through.
I also can't get to that screen where it gives you the text based options to wipe your device, cache, etc.
I've tried loading both TWRP recovery and ClockWorkMod recovery (through Odin), and though it seems to load properly (Odin says "Pass"), when the phone reboots, it goes to the "Samsumg Galaxy Note II" screen (the one with white text on a black background), and just stays there.
I've gotten T-Mobile to agree to send me a new phone. But if I can't get into any of the items I mention above, how can I make sure my old device is wiped before sending it back to them?
Just do this un root with chain fire root away app.
Then use triangle away app.
Then find 4.1.2 MB1 stock Odin tar. The complete package .
Odin to stock .
Reboot and then update via Ota.
You have to un root first and also have to triangle away which removes flash counter in Odin.
System modified status will not allow Ota.
That's the best suggestion I have
Sent from my SGH-T889 using xda app-developers app
diggeryo said:
Nothing is really working for me.
I can't boot into normal mode. I am able to get into "download" mode, but whenever I try to load an image using the Odin software (both a stock image and a Cyagonemod image), it starts to load the image, but just hangs a certain percent of the way through.
I also can't get to that screen where it gives you the text based options to wipe your device, cache, etc.
I've tried loading both TWRP recovery and ClockWorkMod recovery (through Odin), and though it seems to load properly (Odin says "Pass"), when the phone reboots, it goes to the "Samsumg Galaxy Note II" screen (the one with white text on a black background), and just stays there.
I've gotten T-Mobile to agree to send me a new phone. But if I can't get into any of the items I mention above, how can I make sure my old device is wiped before sending it back to them?
Click to expand...
Click to collapse
have you tried booting into recovery? after you load the custom recovery with odin and it reboots, pull the battery put it back, then hold vol up + home and then + power. hold all 3 until recovery. try a factory reset and reboot.
Sent from my SGH-T889 using XDA Premium 4 mobile app
wolfpack612 said:
have you tried booting into recovery? after you load the custom recovery with odin and it reboots, pull the battery put it back, then hold vol up + home and then + power. hold all 3 until recovery. try a factory reset and reboot.
Click to expand...
Click to collapse
I have. It brings me to the same screen with the Samsung Galaxy Note II text on the black background and just stays there.
So, in summary, I can get into download mode (vol down+home+power), but it seems nothing else.
Try factory settings the phone through stock recovery and then check your phone status. It should say 'normal' but if it says 'modified,' download Triangle away and run the tracking setting (it'll make your phone say normal so you can download the OTA). Given you're on tmobile and your phone is the T889 model, check for software updates and install the OTA. Your phone will take a bit and will probably be stuck on the T-Mobile 4G boot screen for several minutes (it's normal). This should work.
Hello, I tried looking into this problem but couldn't find anything similar.
I'm trying to flash CWM recovery using Odin, as it doesn't need root.
I used the usual method (Select OPS, tick one package, untick timer, select package, then start)
Problem is, after I click start, it starts rebooting at "close serial port and wait until rebooting" or something like that, then it shows the battery icon on the device for a few seconds, then starts rebooting to the home screen, and then Odin doesn't do anything, and the recovery doesn't seem to be installed.
Any fix for this?
Thanks.
Edit: Solved! Guess it was a driver or cable problem, it worked after a restart, thanks anyway.
Hi guys, I rooted a friends s3 to enable aws on it and it was working , yesterday she calls me and tells me that it is not working anymore. So I check it and notice there is no root access.
I try to install it using CFRoot . odin flashes fine , I see it running on the phone but once you boot in Supersu states it is not rooted.
Next tried a slew of programs, towelroot apk but nothing works.
Next tried to factory reset, boot in to twrp and I get asked for a password, hit cancel and I get in to the menu. I try to mount the sd card and it fails, trying to install zip from sd fails, factory reset seems to work, wipe data fails and ask for a decrypt code.
I also tried using CWM recovery with basically the same results.
THe last thing I tried was downloading the same firmware 4.4.2 and flashing with odin, it says successful but after rebooting, the phone is exactly the same, nothing changed , it has the same apps, same wallpaper.
I am wondering if my friend let her son play with the phone and turned on some kind of encryption or security that is stopping it from getting wiped back to stock.
Try flashing stock ROM again but uncheck everything except f reset time. When you see the word "reset" in the status window, remove the USB cable from the phone, remove the battery, wait 3 seconds, replace battery, use button combination to boot into recovery, factory wipe, reboot.
To root, flash twrp, then flash supersu.zip from recovery.
Download the latest tar version of TWRP from here: https://dl.twrp.me/d2att/
Download supersu from here: http://forum.xda-developers.com/showthread.php?t=1538053
Save supersu to the phone's internal or memory.
When flashing TWRP in Odin, uncheck everything except f reset time. When you see the word "reset" in the status window, remove the USB cable from the phone, remove the battery, wait 3 seconds, replace battery, use button combination to boot into recovery, flash supersu.zip, reboot.
Hello everyone,
My phone (S4 mini GT-I9195) decided all of a sudden to stop working. I couldn't boot it, charge it, nothing but a black screen. After some research on the world wide web, I came to the conclusion that it might be "bricked", as the cool kids call it. I came upon a guide on this website that seemed promising: https://forum.xda-developers.com/showthread.php?t=2600869
I followed the instructions, found a debrick.img corresponding to my GT-I9195, put it on a sd card and managed to boot the phone.
Next was entering Download mode and flash with a stock firmware via Odin (v3.09). I used a 4.4.2 firmware I found on Sammobile (I9195XXUCNK4_I9195QXZCOA1_XEF) corresponding to my region and phone.
Everything went fine with Odin, I waited until it said "PASS!" and rebooted the phone.
The next step was to enter Recovery mode, and that's where I have a problem. I use the combination "Volume up + Home + Power" to enter it, it vibrates once, shows me the Samsung logo (+ model) with "Recovery booting...." written in blue on the top left corner, I release all the buttons, and after a few seconds, it goes to a black screen, it vibrates twice and reboot on the Samsung logo, but without the "Recovery booting..." message on top left corner. After that, it enters a bootloop that only ends when I remove the battery.
So, I can never enter the recovery mode (I tried multiple times, with different methods, such as releasing only the power button, but to no avail) and cannot complete the debrick guide. I tried different stock firmwares but always with the same result.
Did I do something wrong? What can I do differently to enter recovery mode? Should I prepare the funeral for my phone?
Thank you in advance for your answers.
You should try flashing cwm with odin, then formating your system partition, if you can externally put a rom on your memory card then do so, after that install that rom on your phone, if that doesn't work then try flashing your stock firmware after you had done everything...Of course I don't know if any of this will work because I haven't run into a issue like this before, though one time my recovery was blocked and flashing cwm on it fixed it, instead of flashing stock firmware I went for cyanogenmod (now lineage os) so it might work for you, who knows.
Well, first of all, thank you for your leads.
Secondly, as you suggested, I tried flashing with Odin, with CMW (6.0.4.6 and 6.0.5.1). It went smoothly in Download mode, I get the green PASS!, but just as before, when it reboots in Recovery mode, it doesn't go beyond the blue "Recovery booting...." step, instead, the dreaded bootloop begins.
I also tried flashing with TWRP (3.0.2.0), but unfortunately no change...
And without any custom recovery, I cannot try the lineage os.
I'm begining to feel the end ^^
paupiette said:
Well, first of all, thank you for your leads.
Secondly, as you suggested, I tried flashing with Odin, with CMW (6.0.4.6 and 6.0.5.1). It went smoothly in Download mode, I get the green PASS!, but just as before, when it reboots in Recovery mode, it doesn't go beyond the blue "Recovery booting...." step, instead, the dreaded bootloop begins.
I also tried flashing with TWRP (3.0.2.0), but unfortunately no change...
And without any custom recovery, I cannot try the lineage os.
I'm begining to feel the end ^^
Click to expand...
Click to collapse
I have TWRP on my mini. When I first flashed TWRP (3.0.2.1) via Odin, I had to manually boot into recovery by holding VolUp+Home+Power as soon as I see PASS!, BEFORE the phone automatically reboots.
I have to try this a couple times to get TWRP to stick. From what I read, if you let the phone boot automatically after flashing from Odin, it will automatically overwrite the new flash with stock Samsung recover (which is bad in your case.) So you have to interrupt this by a manual reboot before the phone does its thing. If you are successful, you should boot directly into TWRP on the manual reboot. From then on TWRP will overwrite the stock recovery and you will be good to go.
I find the timing of this manual reboot a bit tricky on the phone. Do it too soon, and the TWRP was not flashed, a second too late, and the phone boots to stock. I had to try that a few times to get it right. Basically, be ready with the buttons and press it the instant you see PASS! So maybe you can try flashing TWRP again before giving up.
I have encountered the same problems today. After waking up, my phone (S4 Mini) told me an update (17 MB) was available. Happy about still getting updates, I started the process and the telephone rebooted. When returning ten minutes later it was all dark and wouldn't respond to any button combination. After working through a lot of threads and forums, trying to fix the problem, I managed to get a debrick image for the phone as well as the right firmware from Sammobile (which is astonishingly the same one that paupiette uses, though I'm from Germany, but the phone seems to have a French regional code).
At first I wasn't able to get to the Download Mode, instead my phone always told me this while denying my attempts to flash it:
BOOTE RECOVERY MODE
CHECK BOOT PARTITIONS..
COPY FROM T-FLASH..
BOOT RECOVERY..
WRITE 139008 sectors..
FLASH WRITE FAILURE
ddi: mmc_read failed
ODIN MODE
PRODUCT NAME: GT-I9195
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
CSB-CONFIG-LSB: 0x30
BOOTLOADER RPSWREV: 2
WRITE PROTECTION: Enable
Nothing seemed to work and some other topics on different forums blamed the internal flash chip (eMMC) to be the cause for all the trouble. I gave up on my phone, loosening the skrews on the back to get a look on the board. Before ripping apart the last bits, I tried to start the Download Mode one more time, so I put in the battery and hold the three buttons. Et voilà - the phone came up with that white booting screen. It was looping this process over and over as paupiette had allready described. I managed to start the Download Mode and flash with Odin3 (v3.12). A green "PASS!" told be, it worked until it began to enter the loop of rebooting again unable to enter the Recovery Menu.
So close but yet so far away from what I want.
Any new ideas or suggestions?