Related
IF I'M USING YOUR RESOURCES.ZIP, LET ME KNOW SO I CAN CREDIT YOU!
I didn't see anyone having done this before on a search, and I apologize if it's been done already. I put together all the audio resources I could find for ringtones, alarms, notifications, and ui, converted them all to very small .ogg's and put them in a new zip. It's a little over 9 megs and has a LOT of stuff. Enjoy.
Oh, and if you have more to add, post them. I'll convert them it and add it to the zip
DIRECTIONS FOR USE:
1. Unzip
2. IF you are using a media2sd script, put the media folder on your ext partition. If not, use it to replace the one on your phone. I recommend using adb, or just mounting the thing in linux. It'll make it simpler.
3. REBOOT and give your phone some time to index all the ringtones. It'll take some time.
AudioResources.zip:
http://www.lighthousesolutions.info/AudioResources.zip
EDIT:
A LOT of people are downloading and nobody is posting additional links, which means (I hope) that I didn't miss any sound files. I'm glad I could help people out, and if anybody else has anything to contribute please POST! Thanks.
Also, I forgot to post this the first time. Themers and rom developers (hell anyone) feel free to use the converted .ogg's in whatever you want. They aren't mine to start with, but I figure I better make the statement clear.
Enjoy
Dead link above
My compilation is on page 3 ~Mikey~
Thanks! Can't have too many random ringtones to choose from I say. Already got the giant mega audio resource list from the other topic that includes all the various android phones, this will just help more.
prash said:
Thanks! Can't have too many random ringtones to choose from I say. Already got the giant mega audio resource list from the other topic that includes all the various android phones, this will just help more.
Click to expand...
Click to collapse
I think this includes all of those, although if you find some that I'm missing, please post them. The main draw of this is that all of sound files are as tiny as possible, making it so you can fit them on internal memory if you want to, or just use less space. The entire thing is only 9.4 mb, and it includes the ringtones from the hero and magic.
Post any ringtones it doesn't contain so I can squish them down to tiny size too.
I can't find any media2sd scripts on the forum. Can any one point me in the right direction?
superGOAT said:
I can't find any media2sd scripts on the forum. Can any one point me in the right direction?
Click to expand...
Click to collapse
You don't have your rom in your sig, so my help will have to be very basic. I run cyanogen's experimental rom (not for the faint of heart) and huanyu's user customizable script. Other than that I can't offer much help. What I can say is that if you push the ENTIRE contents of this zip to your ext partition on your sd card and use huanyu's script with media2sd activated, you'll be fine.
Huanyu also has a version of his script for the stable series of cyanogens roms.
I have NO idea how to do media2sd on hero. I don't support hero as an os and will never use it unless the ENTIRE android community decides to go that route.
If you are using another rom let me know and I'll see what I can do.
I'm currently on Drizzy's newest hero build, but the guts are the same. I went back and did some research and that script is working thanks for the help.
superGOAT said:
I'm currently on Drizzy's newest hero build, but the guts are the same. I went back and did some research and that script is working thanks for the help.
Click to expand...
Click to collapse
No problem, and I'm glad they're working out for you. So far I've got over 100 downloads, so it seems people like this.
Anybody with any additional tones to be added? I'd really like to beef it up!
I'd love to give you some of miine but I don't have any that don't have a copyright next to it but if you want them anyway I'll upload them for you.
Thank you mate!
superGOAT said:
I'd love to give you some of miine but I don't have any that don't have a copyright next to it but if you want them anyway I'll upload them for you.
Click to expand...
Click to collapse
Are any of them for a released or soon to be released android phone? I could put together a "legal" and a "questionable" vesion, although the latter might have to be off the forum (hint hint). I'd like to keep the one on here being full of nothing but official android and htc ringtones for released and soon to be released (ie leaked) android devices.
Noob Question...
I'm running CyanogenMod-4.0.4 + Recovery 1.4 and the community hero rom and was wondering how I should go about implementing this audio resources zip. Do i apply the update from the recovery? Or is there some other way of getting them on?
You can push them to /system/media....but I'd recommend using hyanu's userinit.sh script instead. media2sd is FAR superior for the number of sound files were talking about here.
any chance of this being posted elsewhere? Was looking to download this, but the site doesn't seem to exist.
Can't use my host for any more hosting of FREE ringtones
awesome..! thanks
i may use it for DarkDream theme
Barina said:
awesome..! thanks
i may use it for DarkDream theme
Click to expand...
Click to collapse
I take no credit for creating these............
the #.ogg files in the notification folder are made by moonspoon.
BTW i just installed your theme..WOW
I couldn't get CMupdater to download it but i got it from your site
thanks im glad you like it
i tried the new cmupdater in 1.6 and i cant add my theme server without FC
I'f i was you till cmupdater is fixed, place a direct link to the file on your site
thanks for posting this stuff! very nice
Sorry for being such a noob. But could I bother someone to give me steps on pushing this to my phone? (mytouch).
My Hero is running Damages 2.09.1 and it works perfectly in every respect. But when I was considering the update it was mentioned that this version was "deodexed" and this was a better file. What is deodex? What does it mean? Is it better then a version that is not deodexed?
Thanks for the education. I see the term and want to know what it means.......
Lisa
◦An odex file is basically a chunk of source code that has already been extracted from the apk and put on /system/. This is done to speed up the first boot of a rom (you know how your first boot takes a long time… that’s while it is extracting all of these dex files) and also to save space on /data/. Our stock sprint rom comes with this odex files to give you those benefits, however it also prevents us from “hacking” those files and modifying them. This build has taken all those odex files and injected them back in the apk’s. So expect a slower first boot, and more space taken up on /data/, but you get benefits from it such as the vanilla lock screen being fixed and live wallpapers in Rosie.
Taken from Flipz' website
Great explanation!
I so appreciate you taking your time to explain this....
Lisa
No problem....
Thank you Brian M!
jesus not again............
how the hell do yall even find these ancient threads to bump serously i want to know.
This is actually good. It's showing that he's learning and willing to go deep in our forum to find a solution. Bravo pimpin.
I also found this right now and it answered my question very well. Thanks biran m. =)
yea me to. Thanks brian m
Yah me 2, Thanks mr brian M
You can search it by google.：D
Google Search brought me here
Hello, i'm a web developer and have no experience in developing android roms. Anyways, i'm planning to develop a free website which will let any developer create an online kitchen for his rom, where users like me can come and bake rom according to their needs. Now as i don't have any experience with cooking roms, i would like a little help from the developers. Help i am seeking in is, what features a fully customizable kitchen has, how to change the update.zip for the changes, and adding applications to the zip. I have a little bit idea, but want a clear process.
you will get flamed for this
shararti said:
Hello, i'm a web developer and have no experience in developing android roms. Anyways, i'm planning to develop a free website which will let any developer create an online kitchen for his rom, where users like me can come and bake rom according to their needs. Now as i don't have any experience with cooking roms, i would like a little help from the developers. Help i am seeking in is, what features a fully customizable kitchen has, how to change the update.zip for the changes, and adding applications to the zip. I have a little bit idea, but want a clear process.
Click to expand...
Click to collapse
This really is an admirable goal, but you're attempting to bite & chew WAY more than your mouth can handle!!!
You're a web developer, good.
You have no experience in developing android roms, bad.
You want to develop a free kitchen, good.
You have no experience with cooking roms, bad.
You want developers to help you in exchange for a free kitchen for their rom, bad & good.
You don't know how to update the "update.zip" file and re-sign it, bad.
You don't know how to add an APK to the above mentioned "update.zip" file and re-sign it, bad.
You have a little bit of an idea, but want a clearer process, bad.
All of the above noted BAD points, have been discussed, referenced, and linked on these forums countless times shararti.
You really need to search, read, search some more, and apply what you've learned.
I too am a Web Developer/Designer. I've been in the business of creating websites since 1999 (off & on). And the above mentioned project it something I WON'T EVEN DARE ATTEMPT.
Good luck!
I did search, countless times, everywhere. But as lack of my experience with rom development, it was quite confusing. Well I do know signing and adding apk part, and the rest, i agree, i need some help. I'm willing to give my summer to this project and develop this kitchen for the xda community (i'm also willing to give it away to xda). Now if anyone is willing to help me, please pm me.
Actually, it isn't that difficult.
There are quite a few scripts and programs that you could simply employ on your website. I'm sure those developers wouldn't mind
You would have to tier your ROM baking based on the major ROM cores, and the features swappable between flavors of those cores.
It's simply letting the user choose what he wants in his base ROM, pushing the files into the zip, and running the script to sign them.
I'd be glad to guide you in the structure of ROMs, and showing you what can be mixed and matched.
PM me. We'll get started.
Sounds like a very cool idea and I wish you all the best and hope you find some programmers willing to teach you about roms, and you can do the web coding and make your idea a reality.
I'd use it for sure, would be wicked. Imagine going to this web page on your N1 customizing a ROM, building it and then flashing it. All without going near a computer. Sounds unreal!
APrinceAmongMen said:
I'd be glad to guide you in the structure of ROMs, and showing you what can be mixed and matched.
PM me. We'll get started.
Click to expand...
Click to collapse
Perhaps, share the information here once you two have things worked out?!
shararti said:
I did search, countless times, everywhere. But as lack of my experience with rom development, it was quite confusing ...
... I'm willing to give my summer to this project and develop this kitchen for the xda community ...
Click to expand...
Click to collapse
XDA is such a huge resource, full of solutions, bricked devices and lost newbs LOL.
After trolling for a few months, I was ready to flash my first WinMo SmartPhone a few years ago. I haven't used a 'regular phone' ever since.
This would be an ideal summer project. As I said, I'm also a Web Developer.
Hit me up for some theme/template ideas. I do most of my work with Notepad++ and Adobe Fireworks CS4.
Goonish said:
I'd use it for sure, would be wicked. Imagine going to this web page on your N1 customizing a ROM, building it and then flashing it. All without going near a computer. Sounds unreal!
Click to expand...
Click to collapse
hhmm, never thought of that!
You're right ... sounds unreal!
Something the iFans would never be able to attain.
Even better, how about, instead of flashing some large file, only the ones affected by an update are flashed, resulting in a much SMALLER file (thus saving on data usage) and a FASTER flashing (saying on battery life).
shararti said:
Hello, i'm a web developer and have no experience in developing android roms. Anyways, i'm planning to develop a free website which will let any developer create an online kitchen for his rom, where users like me can come and bake rom according to their needs. Now as i don't have any experience with cooking roms, i would like a little help from the developers. Help i am seeking in is, what features a fully customizable kitchen has, how to change the update.zip for the changes, and adding applications to the zip. I have a little bit idea, but want a clear process.
Click to expand...
Click to collapse
Well it all depends on what you want. I would suggest you have a base rom without the boot.img stored with minimal capability in a folder. then allow the user to choose what type of kernel and capabilities they would like with it. That will be the minimum amount for a rom. Then you can follow it up with additions such as extra scripts and applications that can be added and moved to the appropriate directories. at the end, you would zip up the selection and sign it, with the appropriate update-script (which should be the same as the stock rom's unless the additions require something drastic)
So the folder tree should look something like this for one specific ROM:
ROM/ROM Core Files (this is the base rom without boot.img)
ROM/ROM Core Files/META-INF (this is for the update zip)
ROM/ROM Core Files/system (this is where the system apps go)
ROM/ROM Core Files/data (this is where certain apps go)
ROM/ROM Kernels (this is where kernels are/boot.img)
ROM/ROM Kernels/boot.img.1 etc
ROM/Modifications (this is where apps and other mods go)
ROM/Custom Build (this is where the baked rom should go)
Then all you need to figure out is how to move everything to the custom build directory
Move the core to custom directory and a boot.img (rename it from whatever it is to boot.img) and then move and modifications to the appropriate directory inside the custom build folder. Then zip the custom build folder and sign it
That should be about right. its 3 am here lol so i may be missing something. pm me if you need more help or post here
Exactly.
The great thing about it. The ROM core files can be optional. You can bake a kernel or you can bake CM w/ custom kernel and custom mods, i.e. modded phone.apk. You can bake anything and everything.
Mmm baking never sounded so good.
Check this website out:
http://theunlockr.com/2010/03/26/ho...om-for-android-part-1-setting-up-the-kitchen/
My small contribution to this project
The basic kitchen:
forum.xda-developers.com/showthread.php?t=633246
Sorry it's not a link, apperantly new users cannot post links
flybyme said:
So the folder tree should look something like this for one specific ROM:
ROM/ROM Core Files (this is the base rom without boot.img)
ROM/ROM Core Files/META-INF (this is for the update zip)
ROM/ROM Core Files/system (this is where the system apps go)
ROM/ROM Core Files/data (this is where certain apps go)
ROM/ROM Kernels (this is where kernels are/boot.img)
ROM/ROM Kernels/boot.img.1 etc
ROM/Modifications (this is where apps and other mods go)
ROM/Custom Build (this is where the baked rom should go)
Then all you need to figure out is how to move everything to the custom build directory
Move the core to custom directory and a boot.img (rename it from whatever it is to boot.img) and then move and modifications to the appropriate directory inside the custom build folder. Then zip the custom build folder and sign it
Click to expand...
Click to collapse
Ok so after reading it 3 times carefully, this is what i got to:
All roms have same common files, which are:
1. the META-INF folder.
2. the system folder.
3. the data folder.
This is a basic skeleton of any rom, and every rom has these exact files.
Now what i have to do is, when a user cooks a rom, i have to pick the required boot.img and put it into the basic skeleton, in addition to any apps/modifications user want. Then zip the whole package and sign it.
Is that it?
PS: you also said that i may need to change update-script, in what cases that would be required?
PPS: Do i have to make changes to some other files too? cause it sounds too easy to be true =p
shararti said:
Ok so after reading it 3 times carefully, this is what i got to:
All roms have same common files, which are:
1. the META-INF folder.
2. the system folder.
3. the data folder.
This is a basic skeleton of any rom, and every rom has these exact files.
Click to expand...
Click to collapse
They usually have the same folders, not files
the META-INF has the signature files but most importantly the update-script which tells the phone what to do when your flashing the update.
shararti said:
Now what i have to do is, when a user cooks a rom, i have to pick the required boot.img and put it into the basic skeleton, in addition to any apps/modifications user want. Then zip the whole package and sign it.
Is that it?
PS: you also said that i may need to change update-script, in what cases that would be required?
PPS: Do i have to make changes to some other files too? cause it sounds too easy to be true =p
Click to expand...
Click to collapse
that SHOULD be it but remember that you may have to remove some apps from the core files of the rom such as amazon mp3 that people may not want, so you will have to see what apps can be removed and decide whether you want users to be able to remove it or not.
You MAY have to change the update-script if for example you want to put some things in the data partition and symlink them or change the data partition to include the ext partition instead of just for apps. Changes like that are usually for ROMs that are too big to fit properly on the nexus ( youll also have to check the size of the system and data folders to make sure they fit on the phone without modification)
Most of this stuff will be figured out in testing haha but ya at the very basicee its what you have here. You really have to know what you actually want users to be able to cook and then build the kitchen to that effect
flybyme said:
They usually have the same folders, not files
the META-INF has the signature files but most importantly the update-script which tells the phone what to do when your flashing the update.
Click to expand...
Click to collapse
So does that mean i can use same core for all custom baked roms? Except for the update-script, which in rare cases, may need to be altered.
flybyme said:
that SHOULD be it but remember that you may have to remove some apps from the core files of the rom such as amazon mp3 that people may not want, so you will have to see what apps can be removed and decide whether you want users to be able to remove it or not.
Click to expand...
Click to collapse
I took a look at system folder and it's quite populated. Can you tell me what are the basic files that are common for all roms? For the rest of the files, i guess i'll give the user choice to include them or not.
Also can you tell me what is zipalign? Will that be required in baking process?
And to let everyone know, I have already started the working on the kitchen =]
shararti said:
So does that mean i can use same core for all custom baked roms? Except for the update-script, which in rare cases, may need to be altered.
I took a look at system folder and it's quite populated. Can you tell me what are the basic files that are common for all roms? For the rest of the files, i guess i'll give the user choice to include them or not.
Also can you tell me what is zipalign? Will that be required in baking process?
And to let everyone know, I have already started the working on the kitchen =]
Click to expand...
Click to collapse
Well it really depends on what ROM's your looking at. Some devs change the apps to their liking. For example, CyanogenMod has a modified Settings.apk that has features specific to his rom. However, all ROMs have Settings.apk. As such, you will probably have to have a Core ROM folder for each specific rom.
I would suggest looking at other online kitchens and see what features they offer, come up with a specific feature set and then decide what direction that you want to take.
zipalign is a compression technique that optimizes how .apk files are accessed in android. it makes things faster and is not required but would be nice to have. you lose the benefits if you open and modify any files from a zipaligned apk
Let's clear some things up here.
First, core files are not interchangeable between main roms but only flavors of those main roms.
As of now, we have 3 main roms for the nexus one.
CyanogenMod, Modaco Custom ROM, and Desire/Sense Roms.
Each of these roms have their own unique cores amd features and are not interchangeable.
There are flavors of each of these roms.
Flavors of CM has parts that are interchangeable with other flavors but use Cyans core.
Say there is one CM flavor that has some themieing and a few other changes you don't want. You can take the themed files and put them into your CM base and leave the rest out.
You can't put that themeing into a Modaco Custom ROM though.
Kernels I believe are the only things can be put into any ROM base. Most apps are as well.
Now that I look at it. Doing a Nexus One kitchen isn't that difficult but making a full featured HTC kitchen would be a mountainous task. There are so many mods, roms and themes to keep track of. We'd have to designate people from each device forum to feed us the ROMs and parts that are active and functional.
P. S. Lectures are over at 7 today. ill be able to crack down on it with you then
Kitchens are for the Food Network...
well thanks flybyme and APrinceAmongMen, these 2 posts really cleared up somethings. I'm in the process and will keep you guys updated.
QUESTION: how do i change the radio and boot animations in a rom?
PS: the good news is, i'm done with all the hard part, and just few small things remaining. Probably if anything else doesn't comes up, you guys should have a n1 kitchen within few days =D
shararti said:
QUESTION: how do i change the radio and boot animations in a rom?
PS: the good news is, i'm done with all the hard part, and just few small things remaining. Probably if anything else doesn't comes up, you guys should have a n1 kitchen within few days =D
Click to expand...
Click to collapse
boot animations are located either in /data/local or /system/media
radio flash will require you to change the update-script
you can look at the FRF50 update with the radio to figure it out ( or pm me if thats too difficult, its a little late else id do it myself)
Just make sure the radio is excluded by default.
Another thing about radios, the newest radio usually works on older roms, but old radios don't work on the roms released with and after the newest radio.
So, I have put together an actual Windows program for a lot of Rom Builders. I used to build a lot of Roms, but really don't do much of it any longer. What I know though, is the tool I built is extremely easy to use and very effective. I thought some of you would very much enjoy this tool. It will also allow a lot more people to start theming and tinkering It has built in Draw9 support and will automatically detect what versions of Java you have and allow you to select which one you would like to use.
So I am going to post it here for now in the Note 4 forum for a few of you to install it and check it out. It will support many phones, if not all. All you have to do is make sure you have some type of Java program installed on your PC. The rest is all self-contained and updated.
The first thing you are going to need to do after install is to go into setup and setup the paths accordingly, to your liking. Once this program is setup it runs great. I have built it with threading, so it won't lag as you are working along.
I will post some screen shots for you all to check out.. I would use these as examples of what your environment should look like. Also, make sure you pull the system, from the adb options tab, from your phone as the first step before doing anything else, it will use the framework files as needed to work. This path is also where your deodex setup paths of originals should point to, the pulled files for app and framework.
Enjoy !!!
Link: https://drive.google.com/file/d/0B31X8bH_5Gl-eUtJODBhcUdPRDg/view?usp=sharing
Update: ** Updated file to fix a small issue.. ** EST: 10:24 p.m.
Thank you for this! Going to take a look into it here tonight!
Updated OP..
Made some modifications to the build..
Very Cool, thank you for creating this tool, I'm going to give it a try tonight after a few Christmas parties this evening.
Sounds like a useful tools. I will check it out when my retail phone gets rooted.
za33ck said:
Very Cool, thank you for creating this tool, I'm going to give it a try tonight after a few Christmas parties this evening.
Click to expand...
Click to collapse
Oh great, it will be even better after a few drinks in you..
Can you post source code as well ?
This looks awesome, so what do we use? Do we take a Odin flash able ROM....I don't understand how to use it?
Sent from my Definitive v1.4 Note 4 using Tapatalk
bdorr1105 said:
This looks awesome, so what do we use? Do we take a Odin flash able ROM....I don't understand how to use it?
Sent from my Definitive v1.4 Note 4 using Tapatalk
Click to expand...
Click to collapse
You just plug your phone in and wait for it to detect it.
From there you need to setup the program, look at the screen shots.
gatesjunior said:
You just plug your phone in and wait for it to detect it.
From there you need to setup the program, look at the screen shots.
Click to expand...
Click to collapse
So basically whatever mods you currently have you then make flushable?
I guess what I am asking is should we Odin the stock base that's odex, pull the folders with your program, deodex it and make whatever mods?
Biggest question, how do we make it flushable, I am extremely new to this
Sent from my Definitive v1.4 Note 4 using Tapatalk
Normal
Normal ? when selecting device? See attached Picture
bdorr1105 said:
So basically whatever mods you currently have you then make flushable?
I guess what I am asking is should we Odin the stock base that's odex, pull the folders with your program, deodex it and make whatever mods?
Biggest question, how do we make it flushable, I am extremely new to this
Sent from my Definitive v1.4 Note 4 using Tapatalk
Click to expand...
Click to collapse
So, I am assuming, you mean flashable. Look around for update.zip files associated with Android. You need to make sure you are rooted / dev edition in order to even pursue this. If you are then do some research on update.zip files and understanding our partition table for our phone or your phone, etc..
Wifi tethering unlock
I have my Note 4 DE ordered/shipped by Samsung. I have never used this program before, how easy is it to do your own Native WiFi Hotspot modification? Or is there any step by step I have missed somewhere? Basically, I am wanting to root, TWRP and then change a few things on my own.
Thanks!
gatesjunior said:
So, I have put together an actual Windows program for a lot of Rom Builders. I used to build a lot of Roms, but really don't do much of it any longer. What I know though, is the tool I built is extremely easy to use and very effective. I thought some of you would very much enjoy this tool. It will also allow a lot more people to start theming and tinkering It has built in Draw9 support and will automatically detect what versions of Java you have and allow you to select which one you would like to use.
So I am going to post it here for now in the Note 4 forum for a few of you to install it and check it out. It will support many phones, if not all. All you have to do is make sure you have some type of Java program installed on your PC. The rest is all self-contained and updated.
The first thing you are going to need to do after install is to go into setup and setup the paths accordingly, to your liking. Once this program is setup it runs great. I have built it with threading, so it won't lag as you are working along.
I will post some screen shots for you all to check out.. I would use these as examples of what your environment should look like. Also, make sure you pull the system, from the adb options tab, from your phone as the first step before doing anything else, it will use the framework files as needed to work. This path is also where your deodex setup paths of originals should point to, the pulled files for app and framework.
Enjoy !!!
Link: https://drive.google.com/file/d/0B31X8bH_5Gl-eUtJODBhcUdPRDg/view?usp=sharing
Update: ** Updated file to fix a small issue.. ** EST: 10:24 p.m.
Click to expand...
Click to collapse
Nice,
I just pulled my /system/
Thanks!!!
radionerd said:
Nice,
I just pulled my /system/
Thanks!!!
Click to expand...
Click to collapse
Great..
Hey there interweb!
This thread is meant as a general area to organise the mess of files scattered across the internet for the original Wi-Fi version of the Samsung Galaxy Tab S 8.4.
This Google Drive folder contains the following:
Stock Odin TAR/MD5 firmware files
ROMs, and their accompanying files + install instructions that have been confirmed to boot,
Kernels that have been confirmed to boot,
Useful mods which are confirmed to work and add genuine capability to your device;
and anything else which I think is useful to those wishing to mod their Tab S.
Link:
androiddev - Google Drive
drive.google.com
If you know of any files which you think should be included, and are not already here, please feel free to either reply to this thread or DM me. If you want any assistance at all, please feel free to do the same, and I will try to assist you to the best of my ability.
All the best,
Cessna
I must reiterate, as always, that although I have tested each of these mods, I am not responsible for bricks, loss of data, or permanent damage to your device. You yourself are choosing to make these modifications, and although they have my quality assurance, I can not guarantee their 100% safety. Just because they worked on my device, does not necessarily mean they will work on yours.
CessnaBroon said:
Hey there interweb!
This thread is meant as a general area to organise the mess of files scattered across the internet for the original Wi-Fi version of the Samsung Galaxy Tab S 8.4.
This Google Drive folder contains the following:
Stock Odin TAR/MD5 firmware files
ROMs, and their accompanying files + install instructions that have been confirmed to boot,
Kernels that have been confirmed to boot,
Useful mods which are confirmed to work and add genuine capability to your device;
and anything else which I think is useful to those wishing to mod their Tab S.
Link:
klimtwifi - Google Drive
drive.google.com
If you know of any files which you think should be included, and are not already here, please feel free to either reply to this thread or DM me. If you want any assistance at all, please feel free to do the same, and I will try to assist you to the best of my ability.
All the best,
Cessna
I must reiterate, as always, that although I have tested each of these mods, I am not responsible for bricks, loss of data, or permanent damage to your device. You yourself are choosing to make these modifications, and although they have my quality assurance, I can not guarantee their 100% safety. Just because they worked on my device, does not necessarily mean they will work on yours.
Click to expand...
Click to collapse
Good idea to gather everything on one place and make the mess a bit easier to handle..
I helped myself with the TWRP and the LOS17, much obliged. Don't really need help otherwise.
That is, unless you know why my t705 (i have one of those too) keeps messing with me and losing charge even when switched off...
prkfsz said:
Good idea to gather everything on one place and make the mess a bit easier to handle..
I helped myself with the TWRP and the LOS17, much obliged. Don't really need help otherwise.
That is, unless you know why my t705 (i have one of those too) keeps messing with me and losing charge even when switched off...
Click to expand...
Click to collapse
I'll be honest, my Tab s battery has decreased to about 2100 mAh from 4900 so it's probably just age I'm afraid. If you use it more, you could do a battery transplant, but I don't have ROMs for klimtlte. Thanks for using my mirror
CessnaBroon said:
I'll be honest, my Tab s battery has decreased to about 2100 mAh from 4900 so it's probably just age I'm afraid. If you use it more, you could do a battery transplant, but I don't have ROMs for klimtlte. Thanks for using my mirror
Click to expand...
Click to collapse
Not battery. Changed it. And the same battery works fine on T700 and does not lose charge when off. Tried flashing other ROM as well, but i can't find solution.
prkfsz said:
Not battery. Changed it. And the same battery works fine on T700 and does not lose charge when off. Tried flashing other ROM as well, but i can't find solution.
Click to expand...
Click to collapse
That's odd. Have you tried flashing a custom kernel in TWRP? If not, I'll upload one to the Google Drive in the /androiddev/klimtlte folder. Will create it soon, along with instructions.
CessnaBroon said:
That's odd. Have you tried flashing a custom kernel in TWRP? If not, I'll upload one to the Google Drive in the /androiddev/klimtlte folder. Will create it soon, along with instructions.
Click to expand...
Click to collapse
Odd indeed. And really frustrating. :-/
Have not tried with custom kernel but can of course do that, if it's simple. But, like i said - it's a T705, you mean there is one already made or are you just going to make one on a coffee break?
prkfsz said:
Odd indeed. And really frustrating. :-/
Have not tried with custom kernel but can of course do that, if it's simple. But, like i said - it's a T705, you mean there is one already made or are you just going to make one on a coffee break?
Click to expand...
Click to collapse
There's one already made I think. I'll see if I can find one and alert you when it's up. Obvs I can't do a check for safety without the hardware so make a full backup of the boot partition just in case. I'll make sure to find one with good reviews
CessnaBroon said:
There's one already made I think. I'll see if I can find one and alert you when it's up. Obvs I can't do a check for safety without the hardware so make a full backup of the boot partition just in case. I'll make sure to find one with good reviews
Click to expand...
Click to collapse
Not sure if i have the time to do it tonight or this weekend, but i will try as soon as i get the chance.
Very gratefull for all the help. I actually have two of them, with the same behaviour and i almost written them off, so..
prkfsz said:
Not sure if i have the time to do it tonight or this weekend, but i will try as soon as i get the chance.
Very gratefull for all the help. I actually have two of them, with the same behaviour and i almost written them off, so..
Click to expand...
Click to collapse
kernel - Google Drive
drive.google.com
Shouldn't take more than 5 minutes. Good luck!
CessnaBroon said:
kernel - Google Drive
drive.google.com
Shouldn't take more than 5 minutes. Good luck!
Click to expand...
Click to collapse
Thank you kindly, sir.
Will try right away, but can't really see if had any effect untill morning.
I thought first to ask you if it is possible to use this on stock too, but then it struck me how stupid idea that is, since it's not the same Android version. Because one of them is on stock and behaving the same way. Which basically leads me to believe that it actually is a hardware fault...
prkfsz said:
Thank you kindly, sir.
Will try right away, but can't really see if had any effect untill morning.
I thought first to ask you if it is possible to use this on stock too, but then it struck me how stupid idea that is, since it's not the same Android version. Because one of them is on stock and behaving the same way. Which basically leads me to believe that it actually is a hardware fault...
Click to expand...
Click to collapse
This should work on stock marshmallow too. I will give it a go and get back to you.
Thank you kindly!
lafinjack said:
Thank you kindly!
Click to expand...
Click to collapse
You're very welcome!
CessnaBroon said:
This should work on stock marshmallow too. I will give it a go and get back to you.
Click to expand...
Click to collapse
Sorry for delay in answering..
Unfortunatelly the error is still present. Like i said, probably a software issue.
Bit thanx anuway!
Thanks for creating a section specifically for the SM-T700! I hope that I can get some practical help on moving forward
On my post here (https://forum.xda-developers.com/t/...d-but-ok-with-resurrection-remix-why.4332701/) I describe my attempt to install a variation of LineageOS 17.1 on my device -- always running into 'E1001'. I eventually settled on an older Resurrection Remix, since someone mentioned that it would ultimately make it possible to move to LineageOS (I have not tried that yet).
Here are some of my questions:
1) In a much larger/older thread (https://forum.xda-developers.com/t/...t700-sm-t705-sm-t800-sm-t800-sm-p600.4270943/) the first step is "Flash latest official Samsung Firmware with ODIN". Is this even relevant to me?
2) In preparation for successfully installing LineageOS, what TWRP clearing/formatting options should I be using? On a completely different device, the instructions were to delete *everything*. Could my wrong choices when doing this for my SM-T700 have contributed to my failures?
3) Now that I (currently) have Resurrection Remix on my SM-T700, can I expect -- with the binaries mentioned in this new subgroup -- to be able to install LineageOS 17.1 *without* running into the 'E1001' problem?
Thanks for any help!
darethehair said:
Thanks for creating a section specifically for the SM-T700! I hope that I can get some practical help on moving forward
On my post here (https://forum.xda-developers.com/t/...d-but-ok-with-resurrection-remix-why.4332701/) I describe my attempt to install a variation of LineageOS 17.1 on my device -- always running into 'E1001'. I eventually settled on an older Resurrection Remix, since someone mentioned that it would ultimately make it possible to move to LineageOS (I have not tried that yet).
Here are some of my questions:
1) In a much larger/older thread (https://forum.xda-developers.com/t/...t700-sm-t705-sm-t800-sm-t800-sm-p600.4270943/) the first step is "Flash latest official Samsung Firmware with ODIN". Is this even relevant to me?
2) In preparation for successfully installing LineageOS, what TWRP clearing/formatting options should I be using? On a completely different device, the instructions were to delete *everything*. Could my wrong choices when doing this for my SM-T700 have contributed to my failures?
3) Now that I (currently) have Resurrection Remix on my SM-T700, can I expect -- with the binaries mentioned in this new subgroup -- to be able to install LineageOS 17.1 *without* running into the 'E1001' problem?
Thanks for any help!
Click to expand...
Click to collapse
Hey there! I'll take a closer look once I'm home. Speak to you then
darethehair said:
Thanks for creating a section specifically for the SM-T700! I hope that I can get some practical help on moving forward
On my post here (https://forum.xda-developers.com/t/...d-but-ok-with-resurrection-remix-why.4332701/) I describe my attempt to install a variation of LineageOS 17.1 on my device -- always running into 'E1001'. I eventually settled on an older Resurrection Remix, since someone mentioned that it would ultimately make it possible to move to LineageOS (I have not tried that yet).
Here are some of my questions:
1) In a much larger/older thread (https://forum.xda-developers.com/t/...t700-sm-t705-sm-t800-sm-t800-sm-p600.4270943/) the first step is "Flash latest official Samsung Firmware with ODIN". Is this even relevant to me?
2) In preparation for successfully installing LineageOS, what TWRP clearing/formatting options should I be using? On a completely different device, the instructions were to delete *everything*. Could my wrong choices when doing this for my SM-T700 have contributed to my failures?
3) Now that I (currently) have Resurrection Remix on my SM-T700, can I expect -- with the binaries mentioned in this new subgroup -- to be able to install LineageOS 17.1 *without* running into the 'E1001' problem?
Thanks for any help!
Click to expand...
Click to collapse
Hey! Sorry for the delay. You should flash the latest firmware (it's on updato.com) Using Odin, and then twrp with Odin, and then the custom ROM from twrp, wiping data dalvik and cache before rebooting. Other two are in the mirror.
CessnaBroon said:
Hey! Sorry for the delay. You should flash the latest firmware (it's on updato.com) Using Odin, and then twrp with Odin, and then the custom ROM from twrp, wiping data dalvik and cache before rebooting. Other two are in the mirror.
Click to expand...
Click to collapse
Just an FYI...I was reluctant to start everything over again with Odin and latest Samsung firmware, so I opted to take a chance and merely 'adb push' the LineageOS and GApps that you have on your Google drive (along with some cache erasures as you suggested) and everything seemed to upgrade properly from Resurrection Remix to LineageOS 17.1
A few minor problems so far: camera doesn't work, and initial signon to the tablet with a PIN doesn't work so well (seems to take multiple attempts). In any case, now running Android 10!
These were issues that I faced too - I never found a way to fix them. Neither did the original Dev, but apparently updating to the latest webview fixes chrome crashes. PIN you need to wait 30seconds after boot. Camera works only with clean install and even then sometimes doesn't work.
Hope this helps,
Cessna
I was trying to install TWRP but after reboot when I go to the Recovery mode there is no TWRP. I installed the LOS on my Tab Pro 8.4 and wanted to install LOS on Tab S 8.4 but can't flash the TWRP. Any ideas what I'm doing wrong?
Thanks