Hi everyone,
I have retrieved a Samsung Tab 3.7.0 SM-T210. The OS was the old KitKat 4.4.2, very slow and buggy. I tried to flash a new recovery and OS and spent the 3 last days getting fails. I think I have read the all internet about this situation and would like to make a last try with your help.
When I got the tablet, I was surprised that in download mode it was indicated custom and custom binary and not official as it has not, I think, been flashed in the past by the people owning it. With HW rev 0x5 at the end.
The first thing I wanted to do was to unlock the bootloader, however, I could not find any option in developer mode talking about OEM bootloader, neither Auto Update. After reading some people on forumes saying that this device might not have a locked bootloader, I finally thought that this tablet did not have its bootloader locked. Then I decided to go further with the flash of a TWRP recovery.
At the beginning the stock recovery was working. I am under archlinux, I have fastboot and heimdall. To do it as right as possible I installed a VM with Windows 10 and tried to flash a custom TWRP corresponding to the tablet with Odin. But the process got stuck at the SetupConnection step. I installed Windows 7 too, tried 5 different Windows OS, tried 4 different USB cables, reinstalled the USB drivers, tried 5 different Odin versions, tried different archives, just recoveries and all stock system. Still getting stuck at the SetupConnection.
I finally decided to try heimdall thinking that the VM could be the problem. With heimdall I run flash commands such as heimdall flash --RECOVERY twrp-3.2.3-0-lt02ltespr.img --no-reboot and got it doing something, the shell was saying it's 100% done and the tablet, in download mode, was showing a complete blue bar. Then, the recovery was just broken. Could not access it anymore, the Samsung Tab3 logo showing up and staying when trying to access it. I tried to flash some others archives, I opened it off and remove the battery for 5 minutes, still the same thing.
The operating system was still accessible and buggy, applications saying connection issues, etc. I did a factory reset from the running KitKat android OS and now have the Samsung Tab3 logo showing up and staying when trying to access it.
Now, I can only access the download mode and that's all. I have the impression that I am not the first one having these kind of trouble with this tablet. Is it a hardware issue on all these tablets ? Should I try something more advanced with heimdall, dd ?
Does someone have a solution in this situation ?
Thanks for your time and help.
I finally used heimdall and was able to flash all the partitions with the stock images. Now I am back in stock version. I would like to flash a TWRP recovery.
Can someone tell me if I have to unlock the bootloader with this device ? If it is, how can unlock it ? I can not find anything in the settings developer section, and can not use a call number input in order to enter a system code as it's a tablet. Do I have to wipe something from the stock recovery in order to see it ?
Thanks for your time.
Hi -yo-.
You don't need to do OEM unlock as this device is so old.
Also twrp-3.2.3-0-lt02ltespr.img is NOT for this device.
For recovery look from here and for ROM here.
Thanks jonezy82 for the answer. Indeed, I figured all of that out.
I decided to get it back stock and not trying to flash anything custom.
Thanks for your time.
Related
Hey all, thanks for reading. I've caught myself in a predicament. I can solve most issues that crop up my way, but right now I'm a bit stuck. It is likely fairly simple and I am just dumb...
The huge issue here is that I am running stock lollipop for the D415 model. I am having the typical base-band and WiFi issue that a lot were having. Like most, I just booted up into TWRP and restored a backup. I Wanted to try again so I flashed the stock ROM and tried again; didn't work...oopss..
LG Flash Tool refuses to locate my device. Download mode fails to connect my device properly. Error is:
EP1/out FAIL nfo=40 pg0=ffbd880
usb_read() transaction failed
So now I am stuck with a broken stock ROM, no TWRP, and no current way to re-flash a stock ROM.
Steps taken so far:
1. Reinstall all drivers
2. Attempt to root and install TWRP to access my backups (No access to Download mode)
3. Started all over with original USB.
What can I do? Thank you again for reading my long post.
Came back to it after a few weeks and issue has been resolved. Despite error warnings fastboot operated correctly, only manually. Any script etc. that booted device into fastboot would never find the device. Simple as flashing recovery and restoring a backup.
tl;dr: I'm not very bright.
FiniteDGk said:
Hey all, thanks for reading. I've caught myself in a predicament. I can solve most issues that crop up my way, but right now I'm a bit stuck. It is likely fairly simple and I am just dumb...
The huge issue here is that I am running stock lollipop for the D415 model. I am having the typical base-band and WiFi issue that a lot were having. Like most, I just booted up into TWRP and restored a backup. I Wanted to try again so I flashed the stock ROM and tried again; didn't work...oopss..
LG Flash Tool refuses to locate my device. Download mode fails to connect my device properly. Error is:
EP1/out FAIL nfo=40 pg0=ffbd880
usb_read() transaction failed
So now I am stuck with a broken stock ROM, no TWRP, and no current way to re-flash a stock KDZ.
Steps taken so far:
1. Reinstall all drivers
2. Attempt to root and install TWRP to access my backups (No access to Download mode)
3. Started all over with original USB.
What can I do? Thank you again for reading my long post.
EDIT: Forgot to include that I see the proper devices in device manager.
EDIT 2: Device is properly configured and can be found in ADB when powered on.
Click to expand...
Click to collapse
where u able to fix it? i currently have no recovery or OS it just stays at the LG screen i can only get into Download mode i tried to flash a kdz but it cant read my phone....it turns on but thats it i cant got past the LG screen and when i connect my phone now i get different device drivers than before like LGE AndroidNet USB Serial Port and USB Modem....idk what to do
Hello XDA,
(TLDR - I've mucked things up and would like some help returning to stock, please! I can't enter download mode and am unsure how to work around this. I have access to TWRP and the phone shows up under adb devices. Phone does not show up under fastboot devices.)
Long version:
So I'm new to all of this and was trying to flash Cyanogenmod to my g2. I was following the instructions found on the cyanogen wiki (can't post links). I got to the bit where I was trying to sideload/push and install cyanogen when TWRP started to give me errors (error executing updater binary in zip cm 11, or something like that).
I did a bunch of googling, and after about an hour of not being able to find a solution, I decided to just return to stock for now. That proved problematic as well, unfortunately. I was following a guide found on droidviews (how to return lg g2 to stock firmware. can't post the link.) using the kdz method. I reached step 17 before I encountered a problem. When I enter download mode, I end up stuck on an updating firmware screen. I am unable to get past this and actually enter download mode. I'm unsure how to proceed at this point.
I have access to TWRP. The phone shows up under adb devices. The phone does NOT show up under fastboot devices. I can boot into download mode but not actually get past that updating firmware screen. I'm hoping there is an easy fix and I'm just being a bit of a derp, but I've been looking around for a while and am not sure how to proceed. Please advise!
Finally got everything to work by flashing a lollipop based rom. Just that i lost my contacts and sms.
I nearly bricked my Razr i XT when downgrading from a Kitkat update to JB 4.1.2 but thanks to the great work here I am making some progress but cannot get Recovery or Root. the unlocking of bootloader via the Motorola website went fine and thanks to this post
http://forum.xda-developers.com/showthread.php?t=2239706 I got the rom I wanted, and it's fine.
I have read many other tutorials on installing a recovery and have downloaded and tried 6 or 7 CWM and TWRP images
but it never completes - fastboot says it has, but the phone stubbornly hangs at the flashing.
I have no problems getting into fastboot, but failed many times, and in desperation have tried with USB debugging on and off
and with and without sim and sdcard inserted.
attached are some photos to show where I am stuck at, and I would greatly appreciate some help
carkev said:
I nearly bricked my Razr i XT when downgrading from a Kitkat update to JB 4.1.2 but thanks to the great work here I am making some progress but cannot get Recovery or Root. the unlocking of bootloader via the Motorola website went fine and thanks to this post
http://forum.xda-developers.com/showthread.php?t=2239706 I got the rom I wanted, and it's fine.
I have read many other tutorials on installing a recovery and have downloaded and tried 6 or 7 CWM and TWRP images
but it never completes - fastboot says it has, but the phone stubbornly hangs at the flashing.
I have no problems getting into fastboot, but failed many times, and in desperation have tried with USB debugging on and off
and with and without sim and sdcard inserted.
attached are some photos to show where I am stuck at, and I would greatly appreciate some help
Click to expand...
Click to collapse
U said fastboot hangs at flashing the recovery, but on the command lines on your PC it says finished. Have u tried booting into recovery?
What recovery did u use and where did u get it?
USB debugging, simcard and sdcard don't have anything to do with fastboot. But it is likely that u didn't know that
thanks for looking at this.
I did try booting into recovery from my PC by after rebooting it and then taking the recovery option, but the phone hung at the Motorola bootloader unlocked warning screen.
this link was typical of the various tutorials I used: http://androidteen.com/motorola-razr-i-how-to-root-and-install-clockworkmod-cwm-recovery-on-android-4-1-2-jelly-bean-firmware/
to be fair I cannot recall where I got all the recovery images from - I have that many, and had to rename them recovery.img, so cannot remember the original download names
update:
I have just tried an app from the google play named Root Android, which advised trying other apps - Kingroot, Framaroot & Towelroot,
but they all failed .
what did catch my eye yesterday was the yellow text when in fastboot that says 'dismatched partition entry'
I ignored it as the img files I was trying to flash are all much smaller than the 100mb stated,
but today I am beginning to think that perhaps my recovery partition is corrupt and look for ways to repair it.
does that make any sense?
carkev said:
update:
I have just tried an app from the google play named Root Android, which advised trying other apps - Kingroot, Framaroot & Towelroot,
but they all failed .
what did catch my eye yesterday was the yellow text when in fastboot that says 'dismatched partition entry'
I ignored it as the img files I was trying to flash are all much smaller than the 100mb stated,
but today I am beginning to think that perhaps my recovery partition is corrupt and look for ways to repair it.
does that make any sense?
Click to expand...
Click to collapse
That could be it. Try flashing a rsd lite package from JB. Than go to the recovery and see if u have stock back.
Hazou said:
That could be it. Try flashing a rsd lite package from JB. Than go to the recovery and see if u have stock back.
Click to expand...
Click to collapse
thanks HazouPH, I'll give that a go
I have solved my problem with CWM:victory:
whilst I am not 100% certain I am pretty much sure it was a driver problem - for those who this may benefit, here is what I did.
1. I did not reflash my phone, but stayed with the one in my original post.
2. remember that the main problem was that Fastboot said I had succeeded in flashing a Recovery image, but that the phone 'hung'
at flash as in my photo. and then from my phone I could not get to recovery from the fastboot menu .
3. I stumbled across a posting (on XDA, but I cannot remember where) that said the Motorola drivers were not as good as they should be and that the Motohelper one's would be fine - so I downloaded them, and have attached the zip below.
4. I then decided to tidy up my PC and uninstalled all mobile phone drivers, plus any redundant USB Device drivers
5 for the USB tidying up I tend to use USBdview, which is superb and can be found here
6 when all this was done I simply tried the reflash of CWM - and got the same situation I had been having all along
but amazingly, when I selected 'recovery' it went in CWM - I nearly fainted with surprise!
from all this I can only assume it was a driver problem as I had changed nothing else.
perhaps it was Motohelper drivers- perhaps it was USBdview that did it for me - I will never really know, nor care!
I now have CWM v6.0.1.9 - it is touchscreen and permanent, plus I use the cute Reboot by app by Petrus to control my phone.
happy days!
Hey!
I unlocked bootloader, installed TWRP, and rooted the phone.
Now I cannot get into recovery, the screen just goes black and white led lights up. I tried to factory reset in phone settings, but it wont do nothing. I try to switch off the phone, press vol+ & plug the usb cable to do the unbrick thing, but its not responding to that either.
Fastboot oem device-info says tampered false & bootloader unlock true.
Ned help!
Assuming you have Windows on your PC, if you try to enter download mode (in order to use unbrick method), can you hear a device plugged in sound and/or see the device in Device Manager? Maybe you don't have the drivers.
If fastboot is working too (because you could type "oem device-info" and get an output), you may want to try flashing a custom kernel/ROM or TWRP once again to get it working.
Are you sure you have flashed correct files and haven't mistaken OP3T with OP3?
AFAIK everythings OP3T specific.
Now I ran msmdltool, sideloaded most up-to-date stock rom, managed to flash TWRP and magisk, everythings going smooth this far. I made backups and tried to flash RR rom, but its saying "...this device ( . ) ERROR 7" whats the deal?
*FIXED*
I read that TWRP merged OP3 & OP3T, found a proper dl link for the newest ver TWRP and manage to flash the rom.
So If someone is having same kind of problems like me and trying to figure what can go wrong when you following step-by-step guides, pay attention to details. In this case first after unbrick I forgot to sideload newest ver stock rom. This error 7 thing was a minor and easy to fix, but still can take couple of hours to figure out(find a proper dl link)
I am not an expert user but have always been able to root and install custom ROMs over the past years to devices including ASUS A500, Nexus 4 and 7, Samsung P605, Note 4, and note 8.
However, I have obviously done something to my Note 8 and can no longer install TWRP or SU or anything in fact. This happened after I moved from the official Samsung Pie release to the Lineage 17.1 (Android 10) which I ran successfully for a couple of weeks; but I missed the Samsung DEX support and I used this heavily for streaming to my non-smart TV. So whilst I loved the Lineage experience I moved back to the standard Samsung Pie.
This caused a couple of problems in that I could no longer use some of the Samsung apps since the device recognised that it had been rooted and it burned in the warranty bit, and Samsung ell me that the only way around this on the note 8 is to replace the processor board; and this seems to be correct.
So, I now want to go back to Lineage 17.1, since it was stable and I have lost interest in anything Samsung after this experience.
I can no longer install TWRP (or SU or Magisk) to allow me to root and install Lineage. I have done everything on all the helpful forums, including wipes etc, followed install instructions to the letter (many times) and whilst the loading of TWRP via Odin goes through the motions and completes properly, when I try to go into it all I get is the regular Samsung boot stuff. I have tried SU etc via an SD Card but these always give errors, I have tried the no verify software but it too won’t install.
Many attempts have been made to load TWRP and sometimes it screws up the phone but I can always load the latest Samsung software via Odin; here is the latest Samsung software I am using:-
- AP_N950FXXSADTC4_CL16983991_QB29943831_REV00_user_low_ship_meta_OS9.tar.md5
- BL_N950FXXSADTC4_CL16983991_QB29943831_REV00_user_low_ship.tar.md5
- CP_N950FXXSADTB1_CL1300388_QB15232239_SIGNED.tar.md5
- CSC_OLN_N950FOLNADTB1_CL16983991_QB29490845_REV00_user_low_ship.tar.md5
I would appreciate any help whatsoever. Perhaps someone has done the same thing? Maybe I am screwed!
@neilgoodyer
Did you remember to turn OEM unlock on?
When the phone is in download mode, does it say "prenormal" anywhere? If it does, you won't be able to flash TWRP until that disappears, I don't know the exact way to get rid of it, but I usually sign in to my Samsung account on the phone, then check for an update which registers the device, then it soon disappears for me (prenormal)
stonedpsycho said:
@neilgoodyer
Did you remember to turn OEM unlock on?
When the phone is in download mode, does it say "prenormal" anywhere? If it does, you won't be able to flash TWRP until that disappears, I don't know the exact way to get rid of it, but I usually sign in to my Samsung account on the phone, then check for an update which registers the device, then it soon disappears for me (prenormal)
Click to expand...
Click to collapse
Thanks for the advice:
Yes, OEM unlock on. In fact it seems to turn it on automatically when I invoke developer mode. When in download mode I don't get "prenormal" anywhere. The only somewhat negative comment on that screen is the the warranty count is 1 because I previously loaded Lineage 17.1 Odin completes normally indicating all was well but still only the Samsung bootloader.
Samsung Account is working and I am always able to get my backup loaded whenever I have to reload the current Samsung software,.
It's got me bamboozled and without TWRP I can't do anything......, can't even load a previous custom rom and work my way forward from that. I did think about a previous Samsung software release for the Note 8 Exynos but the "archive" at sammobile doesn't show any.
neilgoodyer said:
Thanks for the advice:
Yes, OEM unlock on. In fact it seems to turn it on automatically when I invoke developer mode. When in download mode I don't get "prenormal" anywhere. The only somewhat negative comment on that screen is the the warranty count is 1 because I previously loaded Lineage 17.1 Odin completes normally indicating all was well but still only the Samsung bootloader.
Samsung Account is working and I am always able to get my backup loaded whenever I have to reload the current Samsung software,.
It's got me bamboozled and without TWRP I can't do anything......, can't even load a previous custom rom and work my way forward from that. I did think about a previous Samsung software release for the Note 8 Exynos but the "archive" at sammobile doesn't show any.
Click to expand...
Click to collapse
When you flash TWRP with Odin, does it pass or give any error code? Have you tried a different TWRP version, maybe the one you have has become corrupt somehow.
stonedpsycho said:
When you flash TWRP with Odin, does it pass or give any error code? Have you tried a different TWRP version, maybe the one you have has become corrupt somehow.
Click to expand...
Click to collapse
Thanks, Yes it completes with a PASS. I have tried several versions of Odin, all appear to work but same results unfortunately.
neilgoodyer said:
Thanks, Yes it completes with a PASS. I have tried several versions of Odin, all appear to work but same results unfortunately.
Click to expand...
Click to collapse
Tried a different TWRP?
Like you said above, I too am bamboozled too.
neilgoodyer said:
Thanks, Yes it completes with a PASS. I have tried several versions of Odin, all appear to work but same results unfortunately.
Click to expand...
Click to collapse
Have you tried ticking on the format option in odin so it deletes everything before flashing the firmware? I would have tried to flash just twrp with the format option ticked to see what happens. I would do a little research before just trying to do that though.
Edit: With the phone connected to your PC using command prompt (in your adb location) type in fastboot boot recovery.img and see what happens.
MrMike2182 said:
Have you tried ticking on the format option in odin so it deletes everything before flashing the firmware? I would have tried to flash just twrp with the format option ticked to see what happens. I would do a little research before just trying to do that though.
Edit: With the phone connected to your PC using command prompt (in your adb location) type in fastboot boot recovery.img and see what happens.
Click to expand...
Click to collapse
Thanks, I will research further that suggestion with odin. I did try doing things with adb, however, it doesn't seem to work with the samsung note 8 (mine anyway).