I have a Samsung Tab 3 (SM-T210R) that started rebooting in the middle of the night. It gets to the main screen and about 10 seconds later reboots. The date is reset to December.
I've tried everything I can find. First the easy stuff such as full charge, different USB cable, different USB port.
I've also tried other things. I do have TWRP installed and tried factory reset that appears to do nothing. I've also tried CWR with factory reset and get errors such as "can't mount /cache/recovery/log" and "can't open an't mount /cache/recovery/log".
I tried to flash a stock ROM with several versions of odin and it fails. At one time it said pit not found so tried to flash that it it fails as well. The last attempt with odin v 3.07 and pit and stock ROM it just hung.
I'm now going to try an different computer.
Any thoughts on what to do next? I've spent at least 10 hours on this and go nothing but frustration.
Thank you
Edit ----
Odin on a older PC appeared to work. The flash ROM and PIT were loaded successfully according to Odin .... BUT, everything appears as it was before. All the old apps show up, the rebooting issue remains.
It would appear that no flashing takes. I also tried to flash newer version of TWRP and CWR and neither took.
mtbgca said:
I have a Samsung Tab 3 (SM-T210R) that started rebooting in the middle of the night. It gets to the main screen and about 10 seconds later reboots. The date is reset to December.
I've tried everything I can find. First the easy stuff such as full charge, different USB cable, different USB port.
I've also tried other things. I do have TWRP installed and tried factory reset that appears to do nothing. I've also tried CWR with factory reset and get errors such as "can't mount /cache/recovery/log" and "can't open an't mount /cache/recovery/log".
I tried to flash a stock ROM with several versions of odin and it fails. At one time it said pit not found so tried to flash that it it fails as well. The last attempt with odin v 3.07 and pit and stock ROM it just hung.
I'm now going to try an different computer.
Any thoughts on what to do next? I've spent at least 10 hours on this and go nothing but frustration.
Thank you
Edit ----
Odin on a older PC appeared to work. The flash ROM and PIT were loaded successfully according to Odin .... BUT, everything appears as it was before. All the old apps show up, the rebooting issue remains.
It would appear that no flashing takes. I also tried to flash newer version of TWRP and CWR and neither took.
Click to expand...
Click to collapse
If Stock ROM flashed with Odin doesn't solve the issue, then you probably have hardware issue.
Take it to a repair shop or Samsung Customer Service.
Nonta72 said:
If Stock ROM flashed with Odin doesn't solve the issue, then you probably have hardware issue.
Take it to a repair shop or Samsung Customer Service.
Click to expand...
Click to collapse
Thanks for the reply, To me it appears to be software. I can use TWRP and communicate via adb. For example, push , shell, sideload from my PC to the tablet. I can copy, move and delete files.
I'm suspecting it's a partition problem but don't know enough to confirm it or fix it.
mtbgca said:
Thanks for the reply, To me it appears to be software. I can use TWRP and communicate via adb. For example, push , shell, sideload from my PC to the tablet. I can copy, move and delete files.
I'm suspecting it's a partition problem but don't know enough to confirm it or fix it.
Click to expand...
Click to collapse
Odin normally formats all the partitions, so, it should have fixed it if it was a partition problem.
Related
Ok, so I wanted Ice Cream Sandwich on my Samsung Galaxy S Vibrant SGH-T959.
I found a Youtube video and eventually installed the passion ICS rom on my phone successfully. Then, I inserted my external sd card and took it back out with out unmounting it. This made my phone want to wipe all my (internal) sdcard data. So stupidly, I did. Luckily I have a recent backup. But then I did a reboot, and it said that the encryption failed and I needed to reset my phone. I complied. Then it would only go into the mod recovery screen, since I had no rom to reinstall (my sdcard wouldn't mount for some odd reason, even after I tried repeatedly). So I decided to start over. I used odin to revert it to what it came like. I unplugged it because it got stuck at cache.rfs and soft-bricked it. Luckily I know how to fix this so I got it back into odin, and I got it to work until it would have a blue reset box in the top left corner, and it said I removed my device. My phone then tried to reboot. It showed the vibrant screen, then crashed and showed the little swirl thing that it does before it shows the green charging battery, it would show that, then show that with the battery in the background, then crash and start again, never getting to the green battery. I tried unplugging it and booting it that way... it went to the vibrant screen and crashed yet again. Also can't get it to display the pink animation. I tried the odin thing again just to get the same result. I tried to boot into recovery mode and it won't even do that. It wont show the terminal thing to save its life. Any ideas? I can get it to the download screen. Any hope? (sorry for the in-depth story, but I thought it might help someone pinpoint what was wrong) I am sporting windows xp. Losing data isn't a problem for either my internal sdcard or external sdcard seeing as I have complete backups on my computer.
Thanks!
Help Please!
UPDATED!
I just tried again and it showed the terminal thing for the first time since I used odin. It will now show the green battery screen, it went into terminal and looked like it was doing stuff and it said that the data wipe failed. Boot Pattern still the same, goes to the vibrant screen and then crashes.
UPDATED YET AGAIN!
It will now go into recovery.
AND AGAIN
Now after I wiped it etc. in recovery mode and rebooted and now it just shows the vibrant screen and crashes over and over on its own.
here's a work around fix
http://forum.xda-developers.com/showthread.php?t=1580902&highlight=encryption
Not-Working Links, noncompaitibility with windows xp it doesn't restore to 2.1
So I tried that a bit ago and the pit file link to download doesn't work. So I used the default one for the vibrant. Didn't successfully run 2.1. Still same problem. Oh, and also, the whole command prompt open in that folder doesn't work on xp, only windows 7 or vista, I found a fix, but still it doesn't recognize adb as a command that is acceptable or whatever.
Thanks, but any other help?
I try Odin and when my phone shows data formatting..... it says data wipe failed afterwards. I think this is the problem.
blu422 said:
So I tried that a bit ago and the pit file link to download doesn't work. So I used the default one for the vibrant. Didn't successfully run 2.1. Still same problem. Oh, and also, the whole command prompt open in that folder doesn't work on xp, only windows 7 or vista, I found a fix, but still it doesn't recognize adb as a command that is acceptable or whatever.
Thanks, but any other help?
I try Odin and when my phone shows data formatting..... it says data wipe failed afterwards. I think this is the problem.
Click to expand...
Click to collapse
Looking back... I didn't know what adb was and now that I have the android SDK installed I'm sure I would be able to fix. Too bad I sold it for an insanely low price. Ugh.
Galaxy S3 T999 rooted and flashed more than daily.
So today has been a very bad day for me. Updated to cm.10.2 nightly and stupidly also flashed the siyah kernel, which is not optimized for the new rom. The process com.android phone didnt respond, so i tried wiping cahse, factory reseting, everything!!! i deleted everything on my phone and i soft bricked it. now im stuck on my boot screen and my pc cant recognize my usb cable. I tried re-installing the usb ports and tried to flash the stock via odin, but nothing happened, i just lost my recovery mod and only have my dl option. but odins always seems to fail me. tried 5-6 times.
Btw. i also tried to adb push a new rom in my phone earlier, but didnt work..
Someone please help me!!!
Edit: Odin always says "<ID:0/005> Complete(Write) operation failed."
[solved] soft bricked and odin fails
mquc said:
So today has been a very bad day for me. Updated to cm.10.2 nightly and stupidly also flashed the siyah kernel, which is not optimized for the new rom. The process com.android phone didnt respond, so i tried wiping cahse, factory reseting, everything!!! i deleted everything on my phone and i soft bricked it. now im stuck on my boot screen and my pc cant recognize my usb cable. I tried re-installing the usb ports and tried to flash the stock via odin, but nothing happened, i just lost my recovery mod and only have my dl option. but odins always seems to fail me. tried 5-6 times.
Btw. i also tried to adb push a new rom in my phone earlier, but didnt work..
Someone please help me!!!
Edit: Odin always says "<ID:0/005> Complete(Write) operation failed."
Click to expand...
Click to collapse
Happy to say, that I today went out and bought a new cable and used my friends lap top and everything worked just fine. Case can be closed.
I've searched for hours for different solutions and have tried them all. I'm on my last leg, and I can't wrap my head around what is going on.
I'm running an S2 with ShoStock3 rom. It's been rooted for over a year now without any major hiccups at all. Last night, it froze on me. Usually when it does this, I just force-restart by holding the power button down until it cycles. Phone usually boots right back up, and I'm all set. This time it just stayed on the boot screen. For eternity. I let it sit like that for more than 45 min, and it never budged. Turn it off from the booth screen, it'll boot right back up. I can go into download mode, but not recovery, and every little trick I've tried works.
I've tried flashing new kernels with ODIN. Tried various recoveries, like Philz and even went as far as the one touch factory ROM and using the regular method for getting the stock ROM. Nothing. Maybe I'm doing something wrong. Most people who have this problem only recently added a new ROM or modified something. I haven't touched the ROM, kernel, etc. for over a year before this happened.
ODIN never makes it far when trying to flash anything. It depends on what is being flashed. It never gets past nand read/write. It never gets past boot.bin. It never gets past factory.img. Etc. Etc. I don't know if maybe something isn't going through between computer and phone, and that's why I'm not having success or what in the world is going on. Every tutorial or help I found confidently stated that all you have to do is flash this kernel, go to recovery, clear cache, and you're all set. But I feel like I'm the odd man out.
I'm afraid that this won't see much attentions, as the S2 is far from new, but like I said I am on my last leg. I just don't understand how it stops working from cycling power. I also don't understand how every attempt doesn't even scratch the surface. Any and all help will be greatly appreciated
The most basic step is to verify you're using the correct button combo to get into recovery: power+both volume keys, then release after the second Samsung logo.
SteveMurphy said:
The most basic step is to verify you're using the correct button combo to get into recovery: power+both volume keys, then release after the second Samsung logo.
Click to expand...
Click to collapse
^^ while the device is NOT USB connected to a computer.
Actually, you're lucky. This device is so popular, even though is it getting old, that there are still a handful of knowledgeable people hanging around.
You need to get into recovery. As Steve and Cyril have said, try the correct button combination, and post back here to verify that you are using the correct combo and that it will not go into recovery.
If you do get into recovery, perform a wipe data/factory reset and see if that gets your phone to boot into the system.
If you are unable to get into the recovery with the correct combo, then you may have one of several possible issues. The first possibility to troubleshoot is nand read/write corruption. Do the following:
Instructions to clear nand read/write corruption. Instructions are specific; do them in order, and don't skip.
Odin3 v1.85 is recommended.
1) Download the SBL Bootloader from the Download Repository. Flash it as PDA in ODIN, without ticking Re-Partitioning. (Please observe normal bootloader flashing caution.)
2) Download the Tar version of Siyah 2.6.14 Kernel. Flash it in PDA. Without ticking Re-Partitioning
3) Flash the Tar.md5 of the full stock Gingerbread distribution from the Download Repository, I777UCKH7 including the bootloaders and everything, in the PDA slot.
I have done the correct button combination for recovery, I promise you that. It brings up Samsung logo first, cuts off, and brings it up a second time, but releasing does nothing. I've tried it several times with different delays as well.
creepyncrawly said:
Instructions to clear nand read/write corruption. Instructions are specific; do them in order, and don't skip.
Odin3 v1.85 is recommended.
1) Download the SBL Bootloader from the Download Repository. Flash it as PDA in ODIN, without ticking Re-Partitioning. (Please observe normal bootloader flashing caution.)
2) Download the Tar version of Siyah 2.6.14 Kernel. Flash it in PDA. Without ticking Re-Partitioning
3) Flash the Tar.md5 of the full stock Gingerbread distribution from the Download Repository, I777UCKH7 including the bootloaders and everything, in the PDA slot.
Click to expand...
Click to collapse
I've actually tried this. On step one, it hangs up on "NAND Write Start!!", just like everything else that tries to get flashed.
To clarify, I should be flashing the I777 UCKH7 sbl.tar file, correct?
Luckily for me I qualified for a free upgrade from ATT for an S4, but I don't want to give up on this phone just yet. Especially with all of the data I have yet to recover from it.
XxArxAngelxX said:
I have done the correct button combination for recovery, I promise you that. It brings up Samsung logo first, cuts off, and brings it up a second time, but releasing does nothing. I've tried it several times with different delays as well.
I've actually tried this. On step one, it hangs up on "NAND Write Start!!", just like everything else that tries to get flashed.
To clarify, I should be flashing the I777 UCKH7 sbl.tar file, correct?
Luckily for me I qualified for a free upgrade from ATT for an S4, but I don't want to give up on this phone just yet. Especially with all of the data I have yet to recover from it.
Click to expand...
Click to collapse
Yes, that is the correct secondary boot loader.
Next, you must assume that there is a connection problem between the phone and the computer. The micro usb port, the cable, the usb port on the computer and the computer itself are all possible weak links in the connection. So try different cables, different ports on the computer, escpecially one directly connected to the mother board, even try a different computer. You can not proceed until you can get the phone to receive a flash and pass. A few people have even reported that they finally were able to complete a flash just by trying repeatedly over and over until it finally passed.
creepyncrawly said:
Yes, that is the correct secondary boot loader.
Next, you must assume that there is a connection problem between the phone and the computer. The micro usb port, the cable, the usb port on the computer and the computer itself are all possible weak links in the connection. So try different cables, different ports on the computer, escpecially one directly connected to the mother board, even try a different computer. You can not proceed until you can get the phone to receive a flash and pass. A few people have even reported that they finally were able to complete a flash just by trying repeatedly over and over until it finally passed.
Click to expand...
Click to collapse
Tried using different computer. Brand new cord. Multiple times tried. Different ports. I dunno, it's doing the same thing. It stops whenever it gets to NAND Write Start.
EDIT: Tried something I saw in another thread. Used stock binary with pit file. Never finished, so aborted it. Now phone doesn't come on at all for any reason whatsoever. -.- Pretty sure I fried it
Hello everyone.
Last week my phone got an OTA update from Sprint and went to android 4.4.2 . I have a stock Samsung Galaxy Note 2 never rooted or rommed it before. After the update the phone acted weird right away. It would freeze up or restart or icons disappeared. About an hour after it shut down then went into this loop of it starts goes to the Samsung Note 2 Model splash and that was it. I would have to pull the battery to turn it off. I tried restarts about 2 dozen times yanking battery holding start button then reinserting battery same thing every time. I also tried 4 different batteries to make sure it wasn't a battery issue.I made sure to pull my sd card to make sure that wasn't an issue. Finally I figured oh well Ill just do a full factory wipe and install. It took a bit but I was able to get into the recover panel.. Its weird when I went in there it went through a whole bunch of red talking about E:failed to mount/cache no such file ...or something to that. I went ahead choose wipe data/factory reset.....This said that failed.....I tried to wipe the cache which seemed to work then tried reset again...same thing failed.. I tried powering off and do this a few times but nothing. I then went on to see if maybe odin would work.. I have odin 3.10, have my samsung drives loaded,kies is not on my machine. I found the sprint tar fil for my note 2 believe its 4.3 . I put my phone in odin dl mode...I opened odin as admin....I selected AP (in new vesion its this old versions was pda)..I went ot my unzipped tar file loaded that in...phone is shown on com4..odin says md5 completed successful so I hit start.....It sits for awhile log says something to likes of communicating..Then after about 15 minutes I get the failed sign.......Can anyone help me fix this and tell me what happened. The phone was fine until that damn ota.....Below are a few images showing the different times I mentioned....I do notice when I put my phone in odin dl mode I have 2 lines I dodnt see if I look at others images of their phone in odin dl mode... One is something about Knox Warranty Void:0 and under that AP:SVREV:A3 .........OK I dont see how to put images in here .I click the add image and it wants a link so I cant getr them from my computer...If anyone knows how Ill add them
Flash 4.3 oder 4.4 Fule via odin. But you need the 3-part firmware and the PIT. Then it works perfectly.
battlekaier said:
Flash 4.3 oder 4.4 Fule via odin. But you need the 3-part firmware and the PIT. Then it works perfectly.
Click to expand...
Click to collapse
Can you explain more Im not real sure how to do what your saying? Where do I get the files your talking of? Thanks for responding....ps just for updates I can not longer get into recovery mode only odin DL mode
Bump..anyone?
This problem has been driving me absolutely mental. About 2 months ago, I tried to root my Galaxy Tab 4 8.0 by T-Mobile (it was an old device anyways), I used the Odin method, and while it was installing, it said that the process was successful, and I saw it all come through. However, when my device restarted, it was stuck at "Starting apps..." for about an hour, so I tried restarting. Then it was stuck on the T-Mobile logo for 1.5 hours. I did a hard wipe/reset, and it was fine... for about a week.
The funny thing about it is, after I did the hard reset, certain bugs would happen, a different bug each time. (For example, Google Play apps would be stuck at "installing", screenshots wouldn't save, apps would crash repeatedly, etc) So if I tried to restart, it wouldn't fix it, but instead it would bootloop. I have to hard reset/wipe my whole system each time it happens, and it drives me up the friggin wall.
I saw online that you can try flashing your system by installing the default drivers onto your computer, and install it on your system through Odin. (or something like that, I'm not that professional at mobile technology) Awesome. Just one problem.. I have looked everywhere and I can't find the driver specifically for my system. I have looked for the driver ever since the problem got worse and I found out about this information, but I found nothing.
If anyone has any idea on how you can help, please respond as soon as you can. Thank you very much.
iamnekro said:
This problem has been driving me absolutely mental. About 2 months ago, I tried to root my Galaxy Tab 4 8.0 by T-Mobile (it was an old device anyways), I used the Odin method, and while it was installing, it said that the process was successful, and I saw it all come through. However, when my device restarted, it was stuck at "Starting apps..." for about an hour, so I tried restarting. Then it was stuck on the T-Mobile logo for 1.5 hours. I did a hard wipe/reset, and it was fine... for about a week.
The funny thing about it is, after I did the hard reset, certain bugs would happen, a different bug each time. (For example, Google Play apps would be stuck at "installing", screenshots wouldn't save, apps would crash repeatedly, etc) So if I tried to restart, it wouldn't fix it, but instead it would bootloop. I have to hard reset/wipe my whole system each time it happens, and it drives me up the friggin wall.
I saw online that you can try flashing your system by installing the default drivers onto your computer, and install it on your system through Odin. (or something like that, I'm not that professional at mobile technology) Awesome. Just one problem.. I have looked everywhere and I can't find the driver specifically for my system. I have looked for the driver ever since the problem got worse and I found out about this information, but I found nothing.
If anyone has any idea on how you can help, please respond as soon as you can. Thank you very much.
Click to expand...
Click to collapse
What you read in the internet means re-flashing your stock rom (system), that is the fix for your problem, the way to do it is to download and install Samsung USB drivers if you hadn't done that already, and Download stock rom from here or here search your model number in the search box and choose the stock rom based on your country, and flash with Odin, it's pretty much the same way you tried to root using CF-ROOT method:
1-you boot into download mode (volume down + home button + power button)
2-and then connect your phone to PC.
3-open Odin and uncheck everything except "auto reboot" and "F. Reset Time" (you should find it like that already), make sure your phone is recognized by Odin, you will see a blue box with a message saying "0:[COMX]" where X is a number.
4-press AP (or PDA in some versions) locate your stock rom which should be in .md5 format, and choose it, then 5-press start.
6-wait for the process to finish (takes a while) and then the phone should reboot itself and you will get a message in Odin saying "Reset!"
PS: you must register on the sites to download..bad thing i know but it's obligation.
Searched both of these websites for the drivers, found nothing.. I've been searching the internet for hours and not one driver was found. Extremely disappointed.
iamnekro said:
Searched both of these websites for the drivers, found nothing.. I've been searching the internet for hours and not one driver was found. Extremely disappointed.
Click to expand...
Click to collapse
Give me your model number.
Sorry found it in the thread title
@iamnekro
That is the link from the first site:
SM-T337T latest firmware android 5.1.1
That is the link from the second site:
SM-T337T latest firmware android 5.1.1
Obviously you didn't search at all...LOL
PS: It's called Stock Firmware or Stock ROM.... not Drivers
Register on any of the sites first to download.
And press the thanks button please
Regards Migo
I'll have to close the thread.. my computer isn't that advanced and is low on space anyways...
iamnekro said:
I'll have to close the thread.. my computer isn't that advanced and is low on space anyways...
Click to expand...
Click to collapse
It doesn't need any advanced computer and only the size of the stock rom and Odin, it's no big deal.