Hello,
I bought a second hand SM-T805 tab, mainly as a multimedia reader. The device itself is great, but the software turns out to be a real downer. So much uneeded stuff just sucking up battery time. Thus, I'm wondering what can be done to alleviate that. I'm fairly experienced with linux, recently hacked a zyxel nas to boot a custom debian, but a complete android noob. I mean come on: where is my console ?
So good advices are very welcome
For an instance, would it be possible to run a clean and fast kernel on that device, offering all drivers (cam, sound, touchscreen and so on), with a speedy interface, console command and nfs/samba support ? How about a stock android only patched with samsung drivers ? What would be the drawbacks compared to stock samsung software.
Than comes the question how it's done. Are there any complete guides on this forum about flashing an sm-t805 ? Any reasons why I should think twice about doing so ? Would it be possible to return to stock samsung afterwards ?
So many questions! Thank you for your help,
qwerkus
qwerkus said:
Hello,
I bought a second hand SM-T805 tab, mainly as a multimedia reader. The device itself is great, but the software turns out to be a real downer. So much uneeded stuff just sucking up battery time. Thus, I'm wondering what can be done to alleviate that. I'm fairly experienced with linux, recently hacked a zyxel nas to boot a custom debian, but a complete android noob. I mean come on: where is my console ?
So good advices are very welcome
For an instance, would it be possible to run a clean and fast kernel on that device, offering all drivers (cam, sound, touchscreen and so on), with a speedy interface, console command and nfs/samba support ? How about a stock android only patched with samsung drivers ? What would be the drawbacks compared to stock samsung software.
Than comes the question how it's done. Are there any complete guides on this forum about flashing an sm-t805 ? Any reasons why I should think twice about doing so ? Would it be possible to return to stock samsung afterwards ?
So many questions! Thank you for your help,
qwerkus
Click to expand...
Click to collapse
Install stock lollipop from odin and after that install TWRP with odin. I recommand this rom: IronRom. There is also a description about how to do this thing here, take a look
qwerkus said:
Hello,
I bought a second hand SM-T805 tab, mainly as a multimedia reader. The device itself is great, but the software turns out to be a real downer. So much uneeded stuff just sucking up battery time. Thus, I'm wondering what can be done to alleviate that. I'm fairly experienced with linux, recently hacked a zyxel nas to boot a custom debian, but a complete android noob. I mean come on: where is my console ?
So good advices are very welcome
For an instance, would it be possible to run a clean and fast kernel on that device, offering all drivers (cam, sound, touchscreen and so on), with a speedy interface, console command and nfs/samba support ? How about a stock android only patched with samsung drivers ? What would be the drawbacks compared to stock samsung software.
Than comes the question how it's done. Are there any complete guides on this forum about flashing an sm-t805 ? Any reasons why I should think twice about doing so ? Would it be possible to return to stock samsung afterwards ?
So many questions! Thank you for your help,
qwerkus
Click to expand...
Click to collapse
- console command: you can use Terminal Emulator app.
- you can always return to stock by flashing stock firmware via Odin.
Thank you for your replies. I found this page: http://forum.xda-developers.com/galaxy-tab-s/general/index-galaxy-tab-s-t3149566 It seems to sum up the possibilites offered on xda-devs for the sm-t805. Yet still miss documentation: why would I do what, how does the samsung stock software work and so on. For an instance, I got a cheap sd card - can't I boot to it and install a custom OS there, why leaving the stock rom untouched ? Flashing is always a tricky operation, which I would not recommend unless really necessary, especially when other storage medium is present.
Related
This has most definately (I would assume) been asked before, but for some reason I can't find any info about. I wanted to know if there is a way(possible) to develop a flashable Android 2.1 ROM to the Tilt 2 (or any other windows mobile device)? I ask because I personally would want to fore-go the HaRET method since this is just Android running on top of Windows Mobile and therefore you won't see the speed benefits or full functionality of Android. If this hasn't been done yet it seems like it should be possible since the HTC phones share a lot of the same hardware i.e. Hero and touch pro2. Can anyone provide info as to why this is or isn't possible?
Thanks
sakshaug007 said:
This has most definately (I would assume) been asked before, but for some reason I can't find any info about. I wanted to know if there is a way(possible) to develop a flashable Android 2.1 ROM to the Tilt 2 (or any other windows mobile device)? I ask because I personally would want to fore-go the HaRET method since this is just Android running on top of Windows Mobile and therefore you won't see the speed benefits or full functionality of Android. If this hasn't been done yet it seems like it should be possible since the HTC phones share a lot of the same hardware i.e. Hero and touch pro2. Can anyone provide info as to why this is or isn't possible?
Thanks
Click to expand...
Click to collapse
This is currently in development i believe but in practical terms we would need a fully functioning ROM first in order to make a flashable Android ROM practical...Haret is easy because you can boot right back to WinMo...instead of having to reflash your device
sakshaug007 said:
This has most definately (I would assume) been asked before, but for some reason I can't find any info about. I wanted to know if there is a way(possible) to develop a flashable Android 2.1 ROM to the Tilt 2 (or any other windows mobile device)? I ask because I personally would want to fore-go the HaRET method since this is just Android running on top of Windows Mobile and therefore you won't see the speed benefits or full functionality of Android. If this hasn't been done yet it seems like it should be possible since the HTC phones share a lot of the same hardware i.e. Hero and touch pro2. Can anyone provide info as to why this is or isn't possible?
Thanks
Click to expand...
Click to collapse
Android does not run on top of windows. Running android using haret can be viewed as booting up a Live CD on your computer. A complete flash (over writing WM OS in ROM) might be possible in the future. Take a look at the Kaiser and Vogue forums the ability to flash into ROM already exists for those two devices. The problem with porting android into any device is that most of the information such as drivers, hardware chip sets etc. are not publicly available. The devs here, are in some cases literally reverse engineering parts of the phones hardware trying to get things working. Just give em some time and support.
Yup, If you look at the kaiser android threads they do have android running from nand removing WM completely. I think they want to get a functioning build before they start trying to flash to nand. One step at a time.
Reefermattness said:
Yup, If you look at the kaiser android threads they do have android running from nand removing WM completely. I think they want to get a functioning build before they start trying to flash to nand. One step at a time.
Click to expand...
Click to collapse
He's right, if you get a dodgy build ETC.. you have a problem!
and android is still buggy
psyopstt said:
Android does not run on top of windows. Running android using haret can be viewed as booting up a Live CD on your computer.
Click to expand...
Click to collapse
With a live CD you actually boot from the cd and never touch windows. With haret, you boot into windows and run it.
Are you saying it unloads windows?
Windows is not still running underneath?
I was looking for info to determine if I would be better off running the most stripped down lean version of windows for better android performance.. but from this post it sounds like it does not matter?? Is this true?
i think the best way right now is to use the minimum rom for winmo, and use that dualboot program.
x51 said:
With a live CD you actually boot from the cd and never touch windows. With haret, you boot into windows and run it.
Are you saying it unloads windows?
Windows is not still running underneath?
I was looking for info to determine if I would be better off running the most stripped down lean version of windows for better android performance.. but from this post it sounds like it does not matter?? Is this true?
Click to expand...
Click to collapse
HaRET completely unloads Windows Mobile from memory before loading the Linux kernel, and eventually Android, rather than simply running Android alongside Windows Mobile. If you know what loadlin was, it's essentially the same concept of unloading one OS and loading another, without shutting down the device. Therefore, the ROM you're running doesn't actually affect the speed at which Android, or any other Linux distro, runs.
neodarksaver said:
i think the best way right now is to use the minimum rom for winmo, and use that dualboot program.
Click to expand...
Click to collapse
Think this is what you are looking for.
http://forum.xda-developers.com/showthread.php?t=624964
But Android on the Rhodiums right now isn't really ready for day to day use yet.
DaveTheTytnIIGuy said:
HaRET completely unloads Windows Mobile from memory before loading the Linux kernel, and eventually Android, rather than simply running Android alongside Windows Mobile. If you know what loadlin was, it's essentially the same concept of unloading one OS and loading another, without shutting down the device. Therefore, the ROM you're running doesn't actually affect the speed at which Android, or any other Linux distro, runs.
Click to expand...
Click to collapse
Excellent, Thats just what I was wondering... thanks!
I would definitely be willing to give nand flashing a go once battery is working, as i dont use sound, bluetooth or gps, it would be nice to just have android on rather than having to boot into winmo first
sebbo90 said:
I would definitely be willing to give nand flashing a go once battery is working, as i dont use sound, bluetooth or gps, it would be nice to just have android on rather than having to boot into winmo first
Click to expand...
Click to collapse
Still not even close to that, we gotta get the system to up to stable state since their would be no way to reboot if something were to lock up. its not a matter of if, just a matter of when. I had the vogue for a long time with the flashable image and it was the best thing ever with just how stable its gotten. it turns your old ass device into a new beast quite literally. the only thing bothering me is the prioritization of the current devs working on the builds.
Can someone tell me the name of the users who are working on the driver/kernel? i might be able to help them get those drivers working.
sebbo90 said:
I would definitely be willing to give nand flashing a go once battery is working, as i dont use sound, bluetooth or gps, it would be nice to just have android on rather than having to boot into winmo first
Click to expand...
Click to collapse
the cab version of AOSP 2.1, the new build, is just as good right now. The battery life is decent while running Android. Plus if u dont want to boot into windows first, get The Gene Y Dual Boot cab..its here on the forum. get the one that points to the "andboot" folder. then u can just boot straight into Android. I got it. Wrks fine. Thats just intil a flash available. but me personally, i like the option of both Wm or Android. The More , the Merrier,..lol
demandarin said:
the cab version of AOSP 2.1, the new build, is just as good right now. The battery life is decent while running Android. Plus if u dont want to boot into windows first, get The Gene Y Dual Boot cab..its here on the forum. get the one that points to the "andboot" folder. then u can just boot straight into Android. I got it. Wrks fine. Thats just intil a flash available. but me personally, i like the option of both Wm or Android. The More , the Merrier,..lol
Click to expand...
Click to collapse
Im not a fan of the dual boot .cab seems a little buggy like the load up times when i have used it. I guess this way with winmo i can have 3 os's
I came upon this device on Christmas (a gift from my girlfriend to her father) and wanted to root it and also install clockworkmod recovery, so I could mess with it a bit without bricking it. Since I found a lack of tailored guides for it, I decided to write this one, although I really did no actual development whatsoever. Normally I would be posting this on general, but given the spirit of this forum, I guess I'll just leave it here. Also, keep in mind I don't have the device anymore and am writing this from memory. If I missed anything or you have any doubts, please let me know (for example, I can't recall specifically the drivers I installed to make it work properly).
Please, please read the whole guide before trying anything, and if you are a novice user, just leave this be, I don't want you to turn your tablet into a paperweight because of my shoddy instructions written from memory and you probably don't need any of this anyway as there are no custom roms yet.
!!!DISCLAIMER!!!: As stated above, anything you do is at your own risk. I provided the procedures that worked for me on a Qilive 97r tablet, which is an Auchan branded ARCHOS 97b Platinum HD, so my step by step should work for all of you. There are probably easier ways to do this, and I hint at them in the guide, but beware I have not tried them and cannot vouch for them. In fact, I cannot and will not take any responsability if you brick your device following these instructions, correctly or otherwise. You do this at YOUR OWN RISK. You have been warned!
Rooting:
I followed this guide on Windows 7 x64 and it worked perfectly.
So thanks to dhigby for that. I would just like to make a couple of remarks:
When you get to step 7 (Installing Superuser by ChainDD), don't. Install SuperSU by Chainfire instead, Use it to update the superuser binary (I think a prompt shows up) and when asked, let it delete the "other" superuser applications, that is, the chinese one. Clean and easy, you don't need to follow any more steps.
Congratulations, you now have (english language) root!
Clockworkmod Recovery:
There is no specific recovery for this device. Fortunately, thanks to AndroTab.info, there's a generic version for 3188 devices that you'll see should work quite nicely, albeight with some caveats.
What works:
Nandroid backup to/from external SDCard (won't recognize internal)
Installing zip files should also work, although I didn't try it at the time, as the device wasn't mine and I can't since I don't have it anymore, but since it mounts system partitions perfectly well I wouldn't think there would be a problem. Try it at your own risk though.
Other things probably work, give it a try.
What doesn't work:
Internal SDCard access
Probably other things
Installation:
Now that you have a rooted tablet, installing clockworkmod recovery is easy-peasy. Go to developer options and enable USB Debugging, then make sure you have a working adb daemon (look it up) that recognizes your tablet.
NOTE: I'm not sure if I had to install any specific drivers for this to work, I think if so they were installed while rooting by the chinese app. Anyhow, here's the Rockchip drivers, you might want to try to install them if you can't get a connection: http://www.rockchip.nl/downloads/
Download the file RK30GENERIC_CWM.zip from here - that's the recovery.
Now extract flash_image and recovery.img from the downloaded file above to the folder where you have your adb and follow the following commands.
Push the files to /dev partition on the device:
Code:
adb push flash_image /dev/
adb push recovery.img /dev/
Then enter root shell, like so:
Code:
adb shell
su
Now flash recovery.img into recovery partition with flash_image:
Code:
chmod 755 /dev/flash_image
/dev/flash_image recovery /dev/recovery.img
Now power off your device. To enter recovery press volume down then the power button and keep them pressed until CWM boots. Voilá!
NOTE: The instructions above were adapted from here and all credit goes to AndroTab.info ; I posted these particular instructions because they are the ones I used and worked for me; there are other methods listed on that page which might or might not work, TRY THEM AT YOUR OWN RISK.
Backing up your original recovery (for warranty, if anything goes wrong, etc.)
To obtain a backup image of your recovery \ restore it back afterwards, follow this guide here. All credit goes to Originalas.
Don't follow it to the letter though: first and foremost, you need a working linux installation. If you don't have one, I recommend Wubi.
Then:
Follow step 1;
Ignore step 2 (it's outdated);
Follow 3;
Follow 4 - but don't expect the screen to turn on, it won't, just hold the volume down button for 10 seconds or so after plugging it in, don't press the power button!
Ignore 5, 6 and 7
Follow 8, but don't use the last command to flash the CWM recovery onto the device. This is because since it is a generic version, it relies on the original recovery kernel. Flashing the image like stated in step 8 would probably overwrite the kernel and result in no recovery at all (I might be wrong about this).
Do follow the last command to restore your own backup if you ever need to.
I am unsure if recovery dumps obtained in this way are device specific; I don't see a reason why they should be, so I'll provide you with my own backup:
ORIGINAL RECOVERY
Flash through any method of your choice, but keep in mind I haven't tried this on other devices, so, as you know by now DO IT AT YOUR OWN RISK.
Closing remarks:
There you have it. Sorry for not holding your hand through every step, but this is meant for people who know a bit of what they're doing, making it faster than having to look up and figure out all these things and quirks on their own. If you have any doubts don't hesitate to ask, but keep in mind I don't have the device anymore and don't know much more than what I have written here. I do appreciate feedback and corrections, and will gladly change the guide giving you full credit - if it's really urgent just PM me, I might not check this thread often.
Cheers!
thanks, works like a charm...do you have any news about updates\custom roms? I can't find anything even in the archos main site
Jammed_Death said:
thanks, works like a charm...do you have any news about updates\custom roms? I can't find anything even in the archos main site
Click to expand...
Click to collapse
I wouldn't keep my hopes up on custom roms. The software is really bad and what it does with the hardware is terrible. It's like a bunch of chipmunks put the code together by randomly typing into a keyboard.
That said, the likelihood of a new kernel to fix that is next to nil. However, since the ROM is as far as I can tell pretty near stock, you can get a pretty good experience from the device by installing gravity box xposed module. I also recommend trickstermod and changing the governor to performance, as well as some kernel tweaking if you know what you are doing.
Also, very important, limit the amount of processes running in the background to 3 in dev settings or change the used memory limit to something like 1.2 gb. It has 2 gb of RAM, but, as I said, the ROM sucks, the system eats away a full gigabyte, and it doesn't effectively kill background apps, leaving you with a sluggish device if you multitask.
Anyway, those are just some ideas, if you have some more or would like to code for this device, feel free to share Also, as I always say, give it time. You never know who is gonna get they're hands on the device and do something amazing with it.
Newbleeto said:
I wouldn't keep my hopes up on custom roms. The software is really bad and what it does with the hardware is terrible. It's like a bunch of chipmunks put the code together by randomly typing into a keyboard.
That said, the likelihood of a new kernel to fix that is next to nil. However, since the ROM is as far as I can tell pretty near stock, you can get a pretty good experience from the device by installing gravity box xposed module. I also recommend trickstermod and changing the governor to performance, as well as some kernel tweaking if you know what you are doing.
Also, very important, limit the amount of processes running in the background to 3 in dev settings or change the used memory limit to something like 1.2 gb. It has 2 gb of RAM, but, as I said, the ROM sucks, the system eats away a full gigabyte, and it doesn't effectively kill background apps, leaving you with a sluggish device if you multitask.
Anyway, those are just some ideas, if you have some more or would like to code for this device, feel free to share Also, as I always say, give it time. You never know who is gonna get they're hands on the device and do something amazing with it.
Click to expand...
Click to collapse
hi and thanx for the answer
yes i saw that it's almost stock but crappy optimized...in the very first start of the tablet i had 1.8gb occupied by nothing and clean master always notifies me that 90% of the ram is busy...meh
maybe just a kernel will fix like you say but you know, android 4.4 will be a must (rockchip already released sdk for 3188). I am not a coder (totally zero) but i will try your suggestion...just a question about the performance governor, does it drain more battery?
i am trying to backup my rom but cwm is so buggy...first was impossible, now i'm stuck on backing up boot image
there is a twrp available for this tablet?
solved
ehy can someone provide a stock rom for the qilive 97r? I'm using a omni 4.4.4 but i want to rever back
thank you
Dump stock ROM QiLive 97R
Jammed_Death said:
ehy can someone provide a stock rom for the qilive 97r? I'm using a omni 4.4.4 but i want to rever back
thank you
Click to expand...
Click to collapse
Yes, i have one. How could i send to you?
Could we change your Omni stock ROM by mine?
I have tried ROM Archos 97b Platinum but touch screen is not working. The only possibiliti to work is by a USB Mouse.
Many thanks.
Redinpais said:
Yes, i have one. How could i send to you?
Could we change your Omni stock ROM by mine?
I have tried ROM Archos 97b Platinum but touch screen is not working. The only possibiliti to work is by a USB Mouse.
Many thanks.
Click to expand...
Click to collapse
you can upload it on mega or gdrive or something like that
for the omni come here, http://forum.xda-developers.com/showthread.php?t=2310818
author thread with links and guides I think you can even try the fixes with your current rom but better ask oma
about the cwm, there is a way to mount sdcard?
Dump stock ROM QiLive 97R
Jammed_Death said:
you can upload it on mega or gdrive or something like that
Click to expand...
Click to collapse
Here he are...
https://www.wetransfer.com/download...556a9cf8fdbc6ddd7ab35ab820141126224717/09298e
Is only available until Decenber, 3 ,so Download it now.
Jammed_Death said:
for the omni come here, http://forum.xda-developers.com/showthread.php?t=2310818
author thread with links and guides I think you can even try the fixes with your current rom but better ask oma
Click to expand...
Click to collapse
I've been watching but I can not understand. Is confused. There are many files and do not know what to do to "fix".
If you are Portuguese, I would like to talk to you on Skype.
Can be?
Jammed_Death said:
about the cwm, there is a way to mount sdcard?
Click to expand...
Click to collapse
I don´t know how I can answer that. I'm new in android, so I sorry.
Jammed_Death said:
thanks, works like a charm...do you have any news about updates\custom roms? I can't find anything even in the archos main site
Click to expand...
Click to collapse
Try this. Sooooooooo beautiful.:good:
(Because this - "To prevent spam on the XDA forums, ALL new users prevented from posting outside links in their messages. After approximately 10 posts, you will be able to post outside links. Thank you for understanding!" i can not put link now. So ask me by Skype) SORRY
:victory:
Follow the instrutions ther and enjoy KK 4.4.2 Oma ROM Iron KK v1.2 - 24-05-2013 (My QiLive say now - Nexus 7 :angel:
Regards
Qilive 97r
Hi guys , if any body can help me with my tablet Qilive 97r, when I tryed to install new rom via RK development tool there was an error, and my tablet do not booting any more, just black display, do not know what to do, maybe somebody know where I can download original rom , and original installer, I will be thankful for that's.
Denysorlyk said:
Hi guys , if any body can help me with my tablet Qilive 97r, when I tryed to install new rom via RK development tool there was an error, and my tablet do not booting any more, just black display, do not know what to do, maybe somebody know where I can download original rom , and original installer, I will be thankful for that's.
Click to expand...
Click to collapse
I'm interested
please ROM stock
Hello, i need help , if somebody know where I can download original rom , and original installer, I will be thankful for that's.
Hello everybody,
It's nearly my first week with my new Samsung Galaxy Tab S 10.5 LTE T805 and I have to admit that,
it is an AwEsOmE experience Great features, fantastic speed, Whoahow screen and colors, e.t.c
But to my also great surprise, I found out that although I have connected my USB stick to my tablet using a microUSB-to-USB
cable, there is no way to "see" it. The USB is formatted in NTFS and I know that there are issues between that and Android, but
I couldn't believe that there isn't a workaround to that problem. Before the Samsung tablet I had an Asus Transformer TF700 Pad with a matching keyboard which by the way had a USB 2.0 port and i could connect my USB sticks and USB HDDs without any issues. It was on JellyBean stock root and ofcourse rooted. Thank God i didn't give it away!!! Until there is a solution on the horizon, with my Samsung:crying: I am going to do all the downloads and transfers to USBs with my Asus.
So this where I need your experience and your knowledge.
Is there something wrong with my tablet, my microUSB cable or it is a known problem regarding the Android?
Is there a way to bypass this problem that anyone from the community might know?
So practically the microUSB port exists only to charge our tablet? What happens if someone wants to put a USB stick in the proccess, because that someone wanted to transfer a number of files from his tablet at home to the PC at work?
Please, I would appreciate it if you could help me out with your knowledge
Thank you in advance for your time,
P.S.
My Samsung is rooted with Stock root KitKat and TWRP custom recovery installed
You need need a different kernel as the stock kernel doesnt natively support ntfs, however apparantly skyhigh kernel does http://forum.xda-developers.com/gal...ent/kernel-skyhigh-tw-kernel-synapse-t2854933
You also need the correct usb otg cable. This one works fine http://www.ebay.co.uk/itm/Dual-Powe..._MobilePhoneDataCables_JN&hash=item1c48b0c84a
Yes, as previously stated that my SkyHigh kernel does support NTFS r/w (amongst many other things).
You will require an app to mount r/w, paragon app is recommended. Else you can have r/o access with root type file explorer to /mnt/ntfs/.....
Thank you very much for your help, @ashyx, @UpInTheAir
But to tell you the truth I am quite afraid to flash a new kernel to my tablet, for 2 reasons mainly
1) I don't know the proccess of doing it
2) I am afraid that it might be too complicated workaround for a noob like me and I don't think I will complete
such a difficult task:crying:
Do you happen to know if with the upcoming Android - 5.0 Lollipop version, that matter will be solved?
So until further notice I will only buy the USB Hub that you recommended and I will keep my Asus tablet (which has has a keyboard with USB2.0 port that works) until Samsung finally decides to solve that matter once and for all for the millions of people out there.
Thank you very much for your time,
dinothenino said:
Thank you very much for your help, @ashyx, @UpInTheAir
But to tell you the truth I am quite afraid to flash a new kernel to my tablet, for 2 reasons mainly
1) I don't know the proccess of doing it
2) I am afraid that it might be too complicated workaround for a noob like me and I don't think I will complete
such a difficult task:crying:
Do you happen to know if with the upcoming Android - 5.0 Lollipop version, that matter will be solved?
So until further notice I will only buy the USB Hub that you recommended and I will keep my Asus tablet (which has has a keyboard with USB2.0 port that works) until Samsung finally decides to solve that matter once and for all for the millions of people out there.
Thank you very much for your time,
Click to expand...
Click to collapse
1) Read the relevant kernel thread, it has INSTRUCTIONS. ..
2) It's not a work-around. It's actually the only solution. I will be blunt, if you believe it's too difficult to follow my thread requirements, instructions and other info, then best you forget about NTFS.
LP probably won't solve NTFS support, because Samsung doesn't enable it in stock kernel.
Thank you very much UpInTheAir for your quick reply,
If it is the only solution, then I will read your kernel thread and your instructions and by the end
of that proccess I will have NTFS support on my tablet.
But nothing of this would have been possible for all of us without your precious work and help @UpInTheAir
Much obliged
dinothenino said:
Thank you very much UpInTheAir for your quick reply,
If it is the only solution, then I will read your kernel thread and your instructions and by the end
of that proccess I will have NTFS support on my tablet.
But nothing of this would have been possible for all of us without your precious work and help @UpInTheAir
Much obliged
Click to expand...
Click to collapse
Just make sure the correct kernel is flashed for your device model
kernel v2.5.0 is latest for T805 and use paragon app from Google Play ( give SU access )
I've implemented a lot of support into kernel for synapse app, you don't need it, but there are many kernel tweaks available by using it.
Best of luck and good reading
The process of installing the kernel is far easier than you probably imagine. However you will need to be rooted to install a custom kernel. Thankfully this process is also very simple with CF AUTO ROOT .
My advice is this : root your tablet, install flashify from play store, back up your stock kernel with it, then use it to install Sky High kernel. Done.
Thanks to UpinTheAir for the kernel. I have done a fair bit of kernel and Rom development myself in the past, so I know the time and effort that developers put into these things. :good:
dinothenino said:
Thank you very much UpInTheAir for your quick reply,
If it is the only solution, then I will read your kernel thread and your instructions and by the end
of that proccess I will have NTFS support on my tablet.
But nothing of this would have been possible for all of us without your precious work and help @UpInTheAir
Much obliged
Click to expand...
Click to collapse
go get one of thesse.
http://www.mymemory.co.uk/OTG-Micro-USB/SanDisk/SanDisk-64GB-Ultra-Dual-OTG-Micro-USB-Flash-Drive
i went pc world and they had them watiing in store. so easy just plug and play! can swap info on my stock tab s 8.4 , also works on my rooted oneplud and the stock nexus 9.
saves you the effort of flashing kernel and also messing up the secure kernel flag, ( i think flashing will make 0x1x show on boot?) KNOX i believe its called. my s4 had it, something to do with warranty flag at samsung
iamdarren said:
go get one of thesse.
http://www.mymemory.co.uk/OTG-Micro-USB/SanDisk/SanDisk-64GB-Ultra-Dual-OTG-Micro-USB-Flash-Drive
i went pc world and they had them watiing in store. so easy just plug and play! can swap info on my stock tab s 8.4 , also works on my rooted oneplud and the stock nexus 9.
saves you the effort of flashing kernel and also messing up the secure kernel flag, ( i think flashing will make 0x1x show on boot?) KNOX i believe its called. my s4 had it, something to do with warranty flag at samsung
Click to expand...
Click to collapse
He wishes NTFS .....
Thank you all for your interest and your kind advice regarding Android and NTFS compatibility,
After long thought I have decided to get rid of NTFS format which is not supported by my android tablet
and go for the new and much promising exFAT which is supported by many platforms.
So I took one of my USB sticks and formatted using exFAT, then copied all my files in and then I connected it with my
microUSB cable to my Samsung tablet. Voila!!! Everything worked like a charm! I "saw" my USB right away from my file
explorer and i was able to copy back and forth from it, even a couple of my bluray movies
So finally after taking into consideration everything you told me, and after reading a lot of posts on this forum I decided
to follow that course and I am very happy with my choice so far:fingers-crossed:
But the choice I made is a result of the precious knowledge and kind help that is provided by the members of this community to all of us noobs:cyclops: seeking help.From the bottom of my heart thank you all for your kindness that you showed me and the help that you provided:good:
God saves the xdadevelopers:good:
iamdarren said:
go get one of thesse.
http://www.mymemory.co.uk/OTG-Micro-USB/SanDisk/SanDisk-64GB-Ultra-Dual-OTG-Micro-USB-Flash-Drive
i went pc world and they had them watiing in store. so easy just plug and play! can swap info on my stock tab s 8.4 , also works on my rooted oneplud and the stock nexus 9.
saves you the effort of flashing kernel and also messing up the secure kernel flag, ( i think flashing will make 60x1x show on boot?) KNOX i believe its called. my s4 had it, something to do with warranty flag at samsung
Click to expand...
Click to collapse
The plugging in of a usb drive is not the issue. You can do that with a cheap otg cable and any storage device. As said its ntfs support, its silly that this isnt supported by default.
ashyx said:
The plugging in of a usb drive is not the issue. You can do that with a cheap otg cable and any storage device. As said its ntfs support, its silly that this isnt supported by default.
Click to expand...
Click to collapse
Yup, I couldn't agree more with that. It really sucks that NTFS is not supported and as all indications show will not be, at least in the near future
So for me exFAT is the second best option in order to bypass this lack of NTFS support on Android.
UpInTheAir said:
He wishes NTFS .....
Click to expand...
Click to collapse
You can format you usb stick, external hdd to exfat file sistem. No root neded, no kernel. Just a functional usb otg cable.
dinothenino said:
Hello everybody,
It's nearly my first week with my new Samsung Galaxy Tab S 10.5 LTE T805 and I have to admit that,
it is an AwEsOmE experience Great features, fantastic speed, Whoahow screen and colors, e.t.c
But to my also great surprise, I found out that although I have connected my USB stick to my tablet using a microUSB-to-USB
cable, there is no way to "see" it. The USB is formatted in NTFS and I know that there are issues between that and Android, but
I couldn't believe that there isn't a workaround to that problem. Before the Samsung tablet I had an Asus Transformer TF700 Pad with a matching keyboard which by the way had a USB 2.0 port and i could connect my USB sticks and USB HDDs without any issues. It was on JellyBean stock root and ofcourse rooted. Thank God i didn't give it away!!! Until there is a solution on the horizon, with my Samsung:crying: I am going to do all the downloads and transfers to USBs with my Asus.
So this where I need your experience and your knowledge.
Is there something wrong with my tablet, my microUSB cable or it is a known problem regarding the Android?
Is there a way to bypass this problem that anyone from the community might know?
So practically the microUSB port exists only to charge our tablet? What happens if someone wants to put a USB stick in the proccess, because that someone wanted to transfer a number of files from his tablet at home to the PC at work?
Please, I would appreciate it if you could help me out with your knowledge
Thank you in advance for your time,
P.S.
My Samsung is rooted with Stock root KitKat and TWRP custom recovery installed
Click to expand...
Click to collapse
calinormy said:
You can format you usb stick, external hdd to exfat file sistem. No root neded, no kernel. Just a functional usb otg cable.
Click to expand...
Click to collapse
I know that. ..
The OP specifically stated he was using NTFS. I gave him the only option if NTFS was required.
He's using an alternative, exFAT may not mount to some OS though. ...
I dont think some people are quite getting it here. I have several drives that are already ntfs and full of data, formatting is not an option. I'm guessing the op is the same.
ashyx said:
I dont think some people are quite getting it here. I have several drives that are already ntfs and full of data, formatting is not an option. I'm guessing the op is the same.
Click to expand...
Click to collapse
Yup, the OP remains the same, me
If you have as many disks as you have and with lots of data on them, then yes you are absolutely right, it gonna take lots of hours of copying and pasting files back and forth until you are done
But it is the only way I can think of, unless ofcourse you want to flash another kernel which supports NTFS
And I was told by the kind developer himself it comes by the name of SkyHigh kernel and supports NTFS r/w
My way is an easy workaround to a problem (By changing from one file system to another) and his way is a solution to the problem.(By keeping the same filesystem)
Ofcourse you can use the way that suits you best
Need desperate help with a MediaTek clone of S4
Hi everyone,
I will try and keep it short but last night I was badly scammed by a wonderful specimen of the human race, who wanted to sell his old Samsung S4. Turns out:
1. Its a mediatek clone
2. It has more issues than anticipated but all buttons work.
3. Seem to be soft bricked
Now I am facing nothing but patience to try and fix it. What works:
1. All buttons seem functional.
2. The phone boots into normal mode where I have only empty screen with a Phone app. The Phone app opens I can enter digits but cannot dial.
3. I can reboot into Factory mode - I performed all the tests of the device and all were a PASS. I heard the sounds, checked the cam, everything seems to be perfectly working. Touch scree, camera, sound etc. Even noticed it had FM.
I tried booting in Download Mode - no success. I get the dead Android image and it just hangs there. I can easy reboot though.
My PC recognizes the device and opens a media (empty) device folder.
I tried thus far to use SP Flash but....I dont know how to. Nothing is happening.
Of course I spent 6 hours waiting on different stock ROMs for S4 before realizing its a MediaTek device.
And now, here I am desperately asking if anyone could help me, if there is a chance to remedy that situation of mine. I dont need the phone to do anything special. The closer it is to a Samsung Android ROM - awesome. If its other, I dont mind at all. So long as it works and has access to Google Play Store.
Thank you geniuses and wonderful people for any hint you might have.
Hi
I had a similar issue couple of yrs ago with an S3 clone.
First thing u need to knw is the mtk version, memory details (RAM & ROM) and screen resolution to find a suitable OS version.
If ur lucky, ull get the stock ROM from the manufacturer on Google or else ull hafta search on xda, needrom, or the Chinese forums. Most of such devices don't have a lot of development so ull hafta port ROMs so a custom recovery will b helpful
Hope these points help
Sent from my YU5510 using Tapatalk
Ok.
So I need:
Device RAM
Device ROM
Mtk Version
I think I can extract these from the Factory Mode. Will check.
Then I need to get the stock ROM (hopefully) or search for a custom ROM. (Manufacturer I suppose we talk about MediaTek and not Samsung?)
Custom Recovery - yeah, usually this is the first thing I install but how do I do this on a cloned mtk? I suppose ODIN wont work. Can you lastly point me to a link or name of software to use instead of ODIN? (or will it work with ODIN?)
Hey guys,
sorry if my english isn't right but I am so tired so now and so frustrated that I don't know what I could do.
The story is simple: I have a android head unit, running allwinner t3 (aka R40) with stock rom and stock recovery.
So far, there isn't any custom recovery available (I would like to create/compile CWM but CWM-Builder have some 502 Bad Gateways...) and the only way to root on 4.4.2 is with 360Root (On 6.0.1 for the newer Models only with Kingroot).
So far not bad but it takes a lot of patience sometimes and sometimes you can try over 1 week every day many hours and it still don't work!
So where do I need help? I want to add Root/SuperSU/... manually but I have many limitation.
First one is that I can only modify the system.img without any chmod and else (Maybe because I am using windows? Maybe because the Firmware has to be flashed while the Head Unit is powered off aka "Dead flash")
Secondly, ADB is not working, to be honest, the head unit act only as a receiver! It accepts any devices like Keyboard, UMTS/WCDMA Stick, USB Stick, ... but MTP fom HeadUnit or ADB, ... don't work. The only way for ADB is ADB over Wifi but I don't know whether it's good or bad. I saw that the USB is plugged into a slot which seems to be bend out, maybe they plugged it in wrong? I don't know how I can test that but I heard that connecting two devices with wrong polarity will break at least one of them!
Thirdly is, that I can't notice a difference between a rooted stock rom and a unrooted stock rom.
According to WinMerge, the rooted ROM have two new files (/etc/install-recovery.sh and /bin/su) but that's it!
If I transfer those files to my custom ROM with the same rooting app, it wont recognize them! I can try and try until I die.
And last, maybe worst, I can't just update something over. Every change outside the Android OS is mainly done by flashing the whole firmware! They changed that policy a little bit after Android 6.0.1 but this Android have the worst stability, worst GPS Modules and completely bricked Bluetooth! Also the stock recovery on 4.4.2 is useless, touch isn't working and the touch-buttons are also not working. I also tried to use a usb keyboard but also useless. Only the 6.0.1 stock recovery recognizes the touch screen and the touch-buttons but as I said, the Android 6 is terribly made...
I know what it sound like a noob and I didn't provided much information but I want to know whether someone can help me or want to help me... maybe someone say that I have to provide information xyz so yeah, feel free to ask
Best regards
Pascal
At what point did you install the ADB device drivers (kinda important) for your device, so that when you plugged it into anything, the thing could register you were plugging in the HeadUnit......