Related
Hi,
Figured id start off by explaining the history on my Samsung Note N8010
A while back i installed Hyperdrive Rom RS8 (i think), no problems, flawless. However it did change my device id to an N8013, not sure why.
Recently i wanted to use SkyGo Tablet app, however root cloak and Voodoo does not cloak SkyGo Tablet app on this specific rom so i figured id revert back to the original 4.1.2 stock.
I used Mobile Odin, grabbed the zip/tar from the Sam-mobile and hit go.
On reboot, it would not load in, stuck on the Samsung Note 10.1 splash. I do have access to download mode and recovery mode, but it's labelled Android System Reocvery <3e>.
It is worth noting that USB debug did not work on Hyperdrive, so currently no matter what computer i connect this tablet to Odin, Kies or anything will not see it.
When trying to "apply update from sd card" i get E:\ mount problems, it pretty much fails every time.
Any suggestions?
kitchenspoon said:
Hi,
Figured id start off by explaining the history on my Samsung Note N8010
A while back i installed Hyperdrive Rom RS8 (i think), no problems, flawless. However it did change my device id to an N8013, not sure why.
Recently i wanted to use SkyGo Tablet app, however root cloak and Voodoo does not cloak SkyGo Tablet app on this specific rom so i figured id revert back to the original 4.1.2 stock.
I used Mobile Odin, grabbed the zip/tar from the Sam-mobile and hit go.
On reboot, it would not load in, stuck on the Samsung Note 10.1 splash. I do have access to download mode and recovery mode, but it's labelled Android System Reocvery <3e>.
It is worth noting that USB debug did not work on Hyperdrive, so currently no matter what computer i connect this tablet to Odin, Kies or anything will not see it.
When trying to "apply update from sd card" i get E:\ mount problems, it pretty much fails every time.
Any suggestions?
Click to expand...
Click to collapse
The original issue is probably one of two things. If you downloaded the rom directly to your device its Likely a bad download. DID YOU CHECK MD5 Before flashing. There are also limitations to Mobile odin.
What i would suggest is to uninstall Kies . Make sure you have no other android devices installed on your computer .Download the older version again from Samsung website. Install on your computer. Download odin again i think you want the one a version back as well NOT Latest.
Reboot into download mode. Run odin. if it still does not see your device check Device manager and see if its showing up with a yellow mark. Look for a post i made last week explaining how to correct usb driver for windows.. Download mode should work with out usb debug on if i remember correctly..
erica_renee said:
The original issue is probably one of two things. If you downloaded the rom directly to your device its Likely a bad download. DID YOU CHECK MD5 Before flashing. There are also limitations to Mobile odin.
What i would suggest is to uninstall Kies . Make sure you have no other android devices installed on your computer .Download the older version again from Samsung website. Install on your computer. Download odin again i think you want the one a version back as well NOT Latest.
Reboot into download mode. Run odin. if it still does not see your device check Device manager and see if its showing up with a yellow mark. Look for a post i made last week explaining how to correct usb driver for windows.. Download mode should work with out usb debug on if i remember correctly..
Click to expand...
Click to collapse
Hi, cheers for the response,
I have tried all of what you have said but unfortunately no PC will see my device, not even an "unrecognized device". I have access to android system reocvery <e3> and Download mode (Odin) but the pc just won't recognized, tried new leads and so forth, nothing.
Hey guys,
I got my hands on a somewhat old Galaxy S2 Plus GT-I9105P. Decided it was long overdue for some help so I decided to install a custom recovery (CWM) and in turn a custom rom in order to breathe some new life into it. Searched around xda and I found a very basic and easy-to-follow guide on how to install a custom recovery on my phone (Talking about this one over here : http://forum.xda-developers.com/showthread.php?t=2663834 ). I basically followed every single step 1 to 1 with the guide until I got to a problem. The .exe file I had downloaded through the provided link for Odin gave an error in Chinese and it mentioned an .ini file. Couldn't find it so I turned to a newer version of Odin. So far so good. Boot up my phone in Download Mode, plug it up to my pc, drivers start to install and bam, would you have guessed it, the drivers failed to install. I turned to google to find the suitable drivers for my device. Downloaded them, installed them, and when in Download Mode the PC recognized the device properly, no errors , no nothing. I open up Odin ( the newer version I downloaded [3.10.7]) and I see the device being recognised, showed up in a blue box. I go to locate my desired recovery file, add it and uncheck the boxes I was told to. Basically I've been doing things 1 to 1 with the instructions on the post. I click on Start and the thing sits on Localising connection or something of that sort not really sure. It stayed there for awhile until I decided to try again. This time I downloaded an older version of Odin I saw in the youtube video, which beegee had linked to. This time things go a bit further, as far as I can tell, and then BAM a big red FAIL. The error was "complete(write) operation failed". Tried with a few different versions of Odin and a few different driver versions as well but no luck.
After some head scratching I decided to turn to linux, but since I am not that savy with the environment I followed a guide which led me to installing the SDK for Android. I noticed that the only thing that it would lead me to would be to root my phone so I ditched it and found a linux alternative to Odin called Heimdall. Installed it but I currently have no idea how to properly operate it.
If any bright individual knows a solution to my problem, please do share as I am in need.
Thanks,
VoidViper
bump.
Hi all,
I've got a Galaxy S6 SM-G920I which will boot to : An error has occurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC software.
I've installed the latest Samsung USB drivers to my PC.
I've installed smart switch and it says my device is " Unsupported Device " . I also updated smart switch to latest version and that made no difference.
I recently deleted 2 important video files by mistake.
A call to Samsung reveiled that there is no way to recovery deleted data from phones internal storage...
A bit of googling lead me to believe the data is still there, its just not visible. Here : https://howtorecover.me/data-recovery-internal-storage-android-phone-guide
So i'm following this guide and get stuck at the > su command. a bit more research reveals I need to root my device.
So I followed a guide on this forum to install latest version of twrp, odin, and magisk.
I reboot and I have root access to the phone.
I continue the guide and fail to proceed after the command > fdisk -l
So I install busybox, and grant it root access.
Command runs but has no output....
At this stage I decide to give up and initiate a system recovery from my phones settings.
Which lead to an endless boot cycle showing the Samsung logo.
More internet research lead me to believe downloading a stock firmware from sammobile might help.
So I downloaded G920IDVU4FRH2_G920ITEL4FRI1_TEL firmware and discovered the instructions on that webpage do not match the extracted content...
So I think that what I feed into odin was the wrong stuff and I've bricked my phone.
I can also access my phones download boot option, and thats all at the moment.
Comments and suggestions welcome
Found the solution here : https://www.reddit.com/r/GalaxyS8/comments/6nb51r/galaxy_s8_odin_flash_fail_softbrick/dk94krm/
Open Odin, place all the necessary files into their slots.
Go the the options tab, make sure "Auto Reboot" IS ticked.
Press "start", but as soon as you do, hold down Vol down+Bix+Power on your phone. Odin will fail and your phone will reboot into download mode again. Now press "Start" in Odin again, and your phone should flash without a problem. This might take a few attempts to get right, but I hope it helps.
At all flash new rom
Hi there!
Hard days trying to root and flash a twrp to my Galaxy Tab4 T533. Finally made it!
I wanted to install Lineage OS 14.1 via TWRP, but it gives error 7, which stands for not compatible problem (maybe?).
I couldnt find the correct ROM for my T533, can anybody help me? Or suggest any other ROM?
Thanks!
I also have a T533 and I am getting crazy trying to root it. It was also hard to flash Twrp until I found the correct tar file. How did you root it? I'm also looking for a custom rom, if I find it I'll let you know. Thank you in advance
Good custom ROMs for that variant aren't available. That is another device with another SoC, so I can't support it. TWRP can be done (if I have a good tester), but nothing more.
TWRP on SM-T533
I want to upgrade the firmware on my Samsung Galaxy Tab 4, also known as model SM-T533 or MATISSE, from stock Android 5.1 to a later ROM
I have tried this upgrade several times and failed.
As I understand I have to perform the following actions
1. Set Developer Options active on tablet (DONE)
2. Install a RECOVERY mod, such as TWRP so I can then install custom firmware such as LineageOS . Not be able to install TWRP is the problem – using the sketchy instructions on site getdroidtips at twrp-recovery-galaxy-tab-4-10-1 and the TWRP 3.0.1 for MATISSE from on site androidfilehost at fid=24459283995311427
3. Install new firmware . I want to install Lineage 17.0 – that seems to be the most up-to-date for the SM-T533, instructions : on site getdroidtips at lineage-os-17-1-galaxy-tab-4-10-1. However, as I can’t install / start TWRP I can’t install LineageOS 17
What I can do Successfully
1. Press POWER + VOL DOWN + HOME then VOL UP to get tablet into DOWNLOAD mode
2. Plug USB Cable between tablet and Windows PC
3. Run Odin 3.14.4 on Windows PC. The tablet is detected as ID_COM 0:[COM33] box is blue
and the Log shows “ADDED”.
4. I click all Odin Options to OFF including “Auto Reboot”
5. I click ODIN “AP” then select file twrp-3.0.1.0-matisse_20160402-2032.tar
6. I run “START “ on ODIN. The status on ODIN in top left hand box shows RECOVERY the RESET then PASS! in green .
What does not work
7. I disconnect the USB cable then hold down the HOME+VOLUP+POWER button on tablet. The tablet screen goes black then shows the Samsung “splash” screen showing “Samsung Galaxy Tab 4” and in Yellow “Set Warranty bit : recovery” in top-left hand corner on tablet screen. Then nothing changes on the tablet.
8. I have tried this process several times and re-read what instructions I Can find but I can’t launch TWRP on the SM-T533 tablet. I can restart the tablet by pressing VOLDOWN+POWER+HOME then VOLDOWN To restart in stock Android
Thanks
cliverlong said:
I want to upgrade the firmware on my Samsung Galaxy Tab 4, also known as model SM-T533 or MATISSE, from stock Android 5.1 to a later ROM
I have tried this upgrade several times and failed.
As I understand I have to perform the following actions
1. Set Developer Options active on tablet (DONE)
2. Install a RECOVERY mod, such as TWRP so I can then install custom firmware such as LineageOS . Not be able to install TWRP is the problem – using the sketchy instructions on site getdroidtips at twrp-recovery-galaxy-tab-4-10-1 and the TWRP 3.0.1 for MATISSE from on site androidfilehost at fid=24459283995311427
3. Install new firmware . I want to install Lineage 17.0 – that seems to be the most up-to-date for the SM-T533, instructions : on site getdroidtips at lineage-os-17-1-galaxy-tab-4-10-1. However, as I can’t install / start TWRP I can’t install LineageOS 17
What I can do Successfully
1. Press POWER + VOL DOWN + HOME then VOL UP to get tablet into DOWNLOAD mode
2. Plug USB Cable between tablet and Windows PC
3. Run Odin 3.14.4 on Windows PC. The tablet is detected as ID_COM 0:[COM33] box is blue
and the Log shows “ADDED”.
4. I click all Odin Options to OFF including “Auto Reboot”
5. I click ODIN “AP” then select file twrp-3.0.1.0-matisse_20160402-2032.tar
6. I run “START “ on ODIN. The status on ODIN in top left hand box shows RECOVERY the RESET then PASS! in green .
What does not work
7. I disconnect the USB cable then hold down the HOME+VOLUP+POWER button on tablet. The tablet screen goes black then shows the Samsung “splash” screen showing “Samsung Galaxy Tab 4” and in Yellow “Set Warranty bit : recovery” in top-left hand corner on tablet screen. Then nothing changes on the tablet.
8. I have tried this process several times and re-read what instructions I Can find but I can’t launch TWRP on the SM-T533 tablet. I can restart the tablet by pressing VOLDOWN+POWER+HOME then VOLDOWN To restart in stock Android
Thanks
Click to expand...
Click to collapse
If you are seriously interested on updating your tab 4:
- take twrp sources and make a good new twrp. For a starting point, you can see what has been done in github.com/matteo0026/android_device_samsung_matisse . Just remove init folder, rename everything from matisse to matissevewifi (your device's codename) and point to github.com/Galaxy-MSM8916/android_kernel_samsung_msm8916 for the kernel. Be sure that in defconfigs there is your too.
- take los16 or 17.1 sources and basing on the work that has been done in github.com/Galaxy-MSM8916 for the other devices with that SoC.
What you told in point number 7 is normal because you installed a custom recovery. When you boot custom ROMs, you'll see "Set warranty bit: kernel". Don't worry, it's just a warning.
If you want some other infos, you can answer below here or better, contact me in PM here on XDA or in Telegram (I'm matteo0026 there too)
TWRP on SM-T533
Hello matteo0026
I definitely want to give this a try to upgrade the TAB 4. It makes sense to create my own TWRP from sources. My technical skills are not very deep so it may take me some time to even successfully build a TWRP. I will contact you to let you know how I get on - or more likely when I have a problem with the build process.
Thanks
Hiya matt
I have a tab4 t533 and want firmware that includes a BL CS AP file.
Mine is an ex demo one
Thankd
musafir 7 said:
Hiya matt
I have a tab4 t533 and want firmware that includes a BL CS AP file.
Mine is an ex demo one
Thankd
Click to expand...
Click to collapse
[TOOL] SamFirm A.i.o - Tools & Firmware downloader & MTP Bypass FRP
SamFirm Tool A.I.O Hello guys I have created a little tool to download Software Tools , check & Download latest Samsung & Apple Firmware, and Bypass FRP (MTP Mode), Changelog: 1.0.0 • Download All Odin3 & Samsung USB Drivers (All...
forum.xda-developers.com
Use this tool (if the file .exe is shown you as virus, admit it on device and execute it another time) to download the firmware
@matteo0026 I am also very interested in getting an update as many applications now require Android 6 or higher.
I have been looking at solutions to get a stable TWRP. Currently to my knowledge the most successful version (the one I use) is this one : https://www.androidfilehost.com/?fid=24421527759889282
It allows to do a certain number of operations but often causes a bootloop of the recovery. I think I remember (I don't have my tablet at hand) that you have to reflash twrp with odin to get out of this bootloop.
I expose these details to share my experience and maybe allow soon an update to lineageOS (Android 6 or higher)
liott said:
@matteo0026 I am also very interested in getting an update as many applications now require Android 6 or higher.
I have been looking at solutions to get a stable TWRP. Currently to my knowledge the most successful version (the one I use) is this one : https://www.androidfilehost.com/?fid=24421527759889282
It allows to do a certain number of operations but often causes a bootloop of the recovery. I think I remember (I don't have my tablet at hand) that you have to reflash twrp with odin to get out of this bootloop.
I expose these details to share my experience and maybe allow soon an update to lineageOS (Android 6 or higher)
Click to expand...
Click to collapse
It's supposed that @sub77 did a TWRP with this device/kernel tree: https://github.com/GalaxyTab4/twrp_matissevewifi
Actually, I just advice you to look at Galaxy-MSM8916 GitHub organisation to get a good kernel (probably, some specific matissevewifi stuff have to be added, but I'm not sure). Then, get my matissewifi tree and adapt it for matissevewifi. And recovery should be okay.
liott said:
@matteo0026 I am also very interested in getting an update as many applications now require Android 6 or higher.
I have been looking at solutions to get a stable TWRP. Currently to my knowledge the most successful version (the one I use) is this one : https://www.androidfilehost.com/?fid=24421527759889282
It allows to do a certain number of operations but often causes a bootloop of the recovery. I think I remember (I don't have my tablet at hand) that you have to reflash twrp with odin to get out of this bootloop.
I expose these details to share my experience and maybe allow soon an update to lineageOS (Android 6 or higher)
Click to expand...
Click to collapse
hello you done at least android 9?
hello everyone i am looking for custom rom for sm-t533
I am looking for it too. please help us
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. I finally thought that this tablet did not have its bootloader locked. 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.
- yo - said:
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. I finally thought that this tablet did not have its bootloader locked. 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.
Click to expand...
Click to collapse
This is obviously your own fault you should of unlocked the bootloader first before flashing twrp
Your device is basically bricked because u risked your device trying to flash twrp with a locked bootloader
Austinredstoner said:
This is obviously your own fault you should of unlocked the bootloader first before flashing twrp
Your device is basically bricked because u risked your device trying to flash twrp with a locked bootloader
Click to expand...
Click to collapse
As I said, 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. I spent hours searching about that and could not find it. Also, some people were saying that this device doesn't have a locked bootloader.
Is it possible to do anything in this situation ?
- yo - said:
As I said, 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. I spent hours searching about that and could not find it. Also, some people were saying that this device doesn't have a locked bootloader.
Is it possible to do anything in this situation ?
Click to expand...
Click to collapse
I don't know because I don't have that device
- yo - said:
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. I finally thought that this tablet did not have its bootloader locked. 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.
Click to expand...
Click to collapse
There is a forum for this device.
Samsung Galaxy Tab 3
The Samsung Galaxy Tab 3, much like its predecessors, comes in three sizes, 7", 8" and 10". The 7" is powered by an Exonys 1.2GHz dual core processor, the 8" is powered by the Samsung Exonys 1.5GHz dual core processor and the 10.1" powered by a 1.6GHz dual core Atom processor. They run on 1GB...
forum.xda-developers.com
Did not know that. Sorry. I am going to post it under the right topic. If someone want to delete it.