Database Info

[APP] Google apps solution in progress help needed.

Hello all,
I am trying to make an application that will detect what actual hardware a user is using and then go out to google and download the official update for the device extract the google apps and install on the device. Right now I was wondering if someone could point me to an ota link for the MT3G and G1 for T-Mobile just for a starting purpose. I already found away to get hardware id and match so I am good there. Any help would be really appreciated.

I don't have them handy but I recommend you contact @wesgarner on here or Twitter and if I recall @Haykuro has them too. If @wesgarner doesn't hook you up right away let me know and I will look them up.

TheArtiszan said:
Hello all,
I am trying to make an application that will detect what actual hardware a user is using and then go out to google and download the official update for the device extract the google apps and install on the device. Right now I was wondering if someone could point me to an ota link for the MT3G and G1 for T-Mobile just for a starting purpose. I already found away to get hardware id and match so I am good there. Any help would be really appreciated.
Click to expand...
Click to collapse
Hi TheArtiszan,
I can tell you that the "OTA" update links change and are (of course) specific to the carrier in question. So for G1 and MT3G, we're talking T-Mobile, in which case I can inform you that the links and locations of the OTA updates rotate and change. By any specific pattern ? That eludes me completely and I would suggest it could/would be hard to track.
Also (and possibly even more challenging to what you are trying to accomplish), the OTA updates typically provide "patch sets" instead of the full blown system image you seek to extract "pure" files.
I'm sure not the answer you wanted, but I hope it helps.
~enom~

yeh I am starting with just T-Mobile ones first since they are my carrier and go from there. even a basic one would be good. I already have an app that will extract files from a file downloaded from my site (minus progress bar still working on that part lol) and extracts files so i have a good start I think. Just stinks that is not in C# would be done already.

Didnt get a response yet from them for thefiles. got app semi working from a rom on a private server any one know about google hosted packages

TheArtiszan said:
Hello all,
I am trying to make an application that will detect what actual hardware a user is using and then go out to google and download the official update for the device extract the google apps and install on the device. Right now I was wondering if someone could point me to an ota link for the MT3G and G1 for T-Mobile just for a starting purpose. I already found away to get hardware id and match so I am good there. Any help would be really appreciated.
Click to expand...
Click to collapse
I think you are taking the hard way to accomplish your goal. Farmatito has already developed a backup script that backs up the necessary files from your phone <HERE>. And redmdc already has a script that will take a backup file and insert the files into an update.zip file <HERE>. There is no need to go out to the providers to get these files. We all already have them.

How to hack the Home Screen Tips Widget?

How do we hack the Home Screen Tips Widget?
There seems to be one included with a few roms. I'd like to be able to change it so that I can use it to learn Japanese words. Is it just a question of editing an xml file or something? Does anyone know where it is stored? If it is baked in a rom, is it therefore impossible to edit?
Thanks.

Decompile the apk, and inside the /res/values/ directory look at the arrays.xml file
CM source -> HERE

Thanks a lot!
I'll get to it.

I'm unable to get it to work at the moment. I've been following this video tutorial too. Are there any obvious things I could be doing wrong please?
I can decompile the apk and rebuild it after changing it. The apk will run but fail to install. Or if I install it in a zip file and via Recovery it seems to install but doesn't show up in System/Apps. (I'll try pushing it with adb)
How do we disable verification? (10:40)
(I'm using CM7 7.02)
Thanks for any help.

Grant Barker said:
I'm unable to get it to work at the moment. I've been following this video tutorial too. Are there any obvious things I could be doing wrong please?
I can decompile the apk and rebuild it after changing it. The apk will run but fail to install. Or if I install it in a zip file and via Recovery it seems to install but doesn't show up in System/Apps. (I'll try pushing it with adb)
How do we disable verification? (10:40)
(I'm using CM7 7.02)
Thanks for any help.
Click to expand...
Click to collapse
You cannot replace a "system" app with an apk which is not signed as a "system app". I had the same issue when I started fixing the DCIM incompatibility in the stock Camera app.
My question for you is: do you have the arrays.xml file already compiled to suit your needs? What phone do you have (HDPI, MDPI, LDPI)? I can make you a custom widget and send it to you.

That's very kind of you hrk.
The phone is an HTC Desire HD.
I should keep trying to learn to do it myself to be honest because I'll be changing it every couple of weeks hopefully, once I learn certain words etc.
Maybe you could talk me through the steps you take or maybe you use different methods or a different program compared to the video?
Anyway thanks for your kind offer.

Grant Barker said:
the steps you take or maybe you use different methods or a different program compared to the video?
Anyway thanks for your kind offer.
Click to expand...
Click to collapse
I set up a build environment (read "I can cook ROMs"). This way I can modify the original Protips project, and then build the apk with the AOSP signing key. If you are running a Stock ROM or a customROM which has not changed the signing keys (e.g.: CyanogenMod uses the same key AOSP uses), the Protips.apk will work flawlessly.
Setting up a build environment requires a bit of time and around 5 GB of hard disk, but it's something everybody can do. The beauty and winning point of Android Open Source Project.

That's great. Thanks hrk.
I'll follow your advice and set up a build environment..

hrk said:
....
Setting up a build environment requires a bit of time and around 5 GB of hard disk, but it's something everybody can do. The beauty and winning point of Android Open Source Project.
Click to expand...
Click to collapse
It's good fun. I just finished the example project Hello World.
I'm pleased I listened to you.

Grant Barker said:
It's good fun. I just finished the example project Hello World.
I'm pleased I listened to you.
Click to expand...
Click to collapse
That's good to hear, but when I wrote "build environment" I meant the entire platform.
With the Android SDK you can build apps, but you won't be able to properly sign them: you can have your own signature and publish them in the Market, but you can't "re-sign" system apps.
Good work!

Ah. I see what you mean.
Maybe that will be the next step in the near future.
In the meantime I'm inspired to make a similar app/widget from scratch which will do what I need..
Thanks.

Grant Barker said:
Ah. I see what you mean.
Maybe that will be the next step in the near future.
In the meantime I'm inspired to make a similar app/widget from scratch which will do what I need..
Click to expand...
Click to collapse
I've had the same idea for a while now! That widget is pretty nice and could be transformed in something pretty cool

Hi did you manage to edit the homescreen tips widget,
I'm finding all over the internet and can't find a solution

_Sparks said:
Hi did you manage to edit the homescreen tips widget,
I'm finding all over the internet and can't find a solution
Click to expand...
Click to collapse
I have the same problem... im trying to hack it (changed te arrays.xml) but it still needs that damn system signing could anyone help?
Is there any other way than installing 5gb of stuff just to sign one .apk

jazux said:
I have the same problem... im trying to hack it (changed te arrays.xml) but it still needs that damn system signing could anyone help?
Is there any other way than installing 5gb of stuff just to sign one .apk
Click to expand...
Click to collapse
dude could we use apk signer or any other stuff?

_Sparks said:
dude could we use apk signer or any other stuff?
Click to expand...
Click to collapse
I think no because we need the system signing key

Any signer should work. But depending on how you edit and build the apk, you might not be able to "install" it, but have to push it instead
Sent from my HERO200 using XDA App

kyouko said:
Any signer should work. But depending on how you edit and build the apk, you might not be able to "install" it, but have to push it instead
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
I decompiled it, replaced arrays.xml compiled it TRIED to sign but i got error "unable to sign system application" or something like that

Hmm, I'll check it out and see..once the power is back on in my area
ComEd said it could be up to two days because of the storms lol
Sent from my HERO200 using XDA App

jazux said:
I decompiled it, replaced arrays.xml compiled it TRIED to sign but i got error "unable to sign system application" or something like that
Click to expand...
Click to collapse
Read my previous posts on this very topic.
You can't sign a system app without using the system key. It can't be easier than that.

[Q] CF-Auto-Root for Nexus 5 - How it works?

Hey guys,
I couldn't find it anywhere and I don't really know if this is the right place to ask, but I'll give it a try...
I wonder how does the CF-Auto-Root for the nexus 5 works?
I can see in the windows batch file that it unlocks the bootloader (that's the easy part) and than boot with some image file.
It seems that this tool is not installing any custom recovery which I always saw is a necessary tool for rooting.
What exactly is this image file? what does it do? Where does it come from? What it contains?
Why it's device related (different image files for different nexus devices running the same stock version).
Thanks,
Casteel.

Casteel said:
Hey guys,
I couldn't find it anywhere and I don't really know if this is the right place to ask, but I'll give it a try...
I wonder how does the CF-Auto-Root for the nexus 5 works?
I can see in the windows batch file that it unlocks the bootloader (that's the easy part) and than boot with some image file.
It seems that this tool is not installing any custom recovery which I always saw is a necessary tool for rooting.
What exactly is this image file? what does it do? Where does it come from? What it contains?
Why it's device related (different image files for different nexus devices running the same stock version).
Thanks,
Casteel.
Click to expand...
Click to collapse
Unlocking and rooting is a piece of cake with CF Auto Root for the N5, i never xperienced issues with it. Download CF Root for the Nexus 5, unzip it with 7-zip. Enable usb debugging in developer options, then go into bootloader/fastboot mode, open the uznipped CF Root folder and press Root_windows.bat and follow instructions. Takes 30 seconds - 1 minute all in all.

Thanks, but...
gee2012 said:
Unlocking and rooting is a piece of cake with CF Auto Root for the N5, i never xperienced issues with it. Download CF Root for the Nexus 5, unzip it with 7-zip. Enable usb debugging in developer options, then go into bootloader/fastboot mode, open the uznipped CF Root folder and press Root_windows,bat and follow instructions. Takes 30 seconds - 1 munute all in all.
Click to expand...
Click to collapse
First, thanks for your response.
I don't have a problem with making it work.
As you said, it is super simple and no question it's a great tool.
My question is about how it works? What exactly does it do behind the scene?

Casteel said:
First, thanks for your response.
I don't have a problem with making it work.
As you said, it is super simple and no question it's a great tool.
My question is about how it works? What exactly does it do behind the scene?
Click to expand...
Click to collapse
It unlocks the BL and injects superSU in one go without having to flash a seperate superSU.zip with a custom recovery. Thats all.

gee2012 said:
It unlocks the BL and injects superSU in one go without having to flash a seperate superSU.zip with a custom recovery. Thats all.
Click to expand...
Click to collapse
What do you mean by "injects SuperSU" ?
It sounds very simple from the way you say it. Why can't I do this myself?
I believe it doesn't just mean copy it to the right place.
Does it also include putting the su binary in the right system path with the right permissions?
How does the root privilage is gained?
Does only unlocking the BL let me write to the system partition?
I would really appreciate some technical details to understand this rooting process and what this image file contains.
Thanks again!

Read this http://forum.xda-developers.com/showthread.php?t=2507211 and this http://forum.xda-developers.com/showthread.php?t=1980683. You can also do the root yourself manualy if that more comfortable for you.

gee2012 said:
Read this http://forum.xda-developers.com/showthread.php?t=2507211 and this http://forum.xda-developers.com/showthread.php?t=1980683. You can also do the root yourself manualy if that more comfortable for you.
Click to expand...
Click to collapse
gee2012, I really appreciate your help.
I've already read (most of) these two threads before posted here, and couldn't find an answer to my questions,
only general explanations about how to make it work and how to solve problems,
nothing about HOW it works and what it actually does.
I have already rooted my device with this tool, I don't have any discomfort with is,
just pure technological curiosity about how it works.
Sure, I can also root myself manually, but all the guides I read about it mentioned installing custom recovery, and that tool does it with out it.

Casteel said:
gee2012, I really appreciate your help.
I've already read (most of) these two threads before posted here, and couldn't find an answer to my questions,
only general explanations about how to make it work and how to solve problems,
nothing about HOW it works and what it actually does.
I have already rooted my device with this tool, I don't have any discomfort with is,
just pure technological curiosity about how it works.
Sure, I can also root myself manually, but all the guides I read about it mentioned installing custom recovery, and that tool does it with out it.
Click to expand...
Click to collapse
Look here https://www.google.com/search?q=how+root+works&ie=utf-8&oe=utf-8&aq=t and other sites how root works http://stackoverflow.com/questions/...hat-are-the-pre-requisites-for-it-to-work-wha.
With Google you can find anything

Actually, I read this also...
It only talks about gaining root privilage using some system exploit.
So, you're telling that CF-Auto-Root is running some script in its bootable image file that is using some kind of exploit to gain root access?
Shouldn't it be less "hacky" thing in nexus devices?
And how can it be that the image file is related to specific devices and not to specific stock versions?
What prevents from other apps to use this so called "exploit"?

This is probably what you are looking for...
Embedded in the boot image a folder cfroot with the SuperSU apk file, the su binary and the necessary init scripts and there is a binary under sbin does the remaining steps of copying the files to the respective places. It is not an exploit, it merely uses the boot image and the boot process to "install" SuperSU. You do not need a custom recovery to root your phone, merely the capability to copy the superuser files to the /system partition.
In more detail:
1. Embedded in the ramdisk is a folder "cfroot" with "99SuperSUDaemon, install-recovery.sh, su and Superuser.apk".
2. In the sbin folder in the ramdisk is a binary "cfautoroot" which does stuff like copy the above files to the correct locations and set the appropriate permissions, etc.
3. This file is called through the "recovery" script/binary in the sbin folder
4. The "recovery" script/binary is executed as a startup server via the init system in "init.rc" within the ramdisk
The result:
When you boot up, the superuser files are copied to the respective locations with the right permission, thereby rooting the system

OK! Now we're getting closer
Thank you very much.
But I still have some confusions...
You said:
craigacgomez said:
there is a binary under sbin does the remaining steps of copying the files to the respective places.
You do not need a custom recovery to root your phone, merely the capability to copy the superuser files to the /system partition.
Click to expand...
Click to collapse
How did the "cfautoroot" got to my phone sbin folder?
How do I get the capability to copy the superuser files to the system partition?
Putting things in these folders and set their appropriate permissions doesn't require root from the first place?
How is the init.rc calling the recovery script to run the cfautoroot? shouldn't I need root access to modify init.rc?
[Is the CF-Auto-Root source code available somewhere to see all these files you're talking about?]
It sounds like only unlocking the bootloader is giving me some sort of "root" capabilities to do all these stuff. is it true?
Will this method work in non Nexus devices either?
And what are all those "exploits" that so many rooting guides are talking about?
I'm guessing it desn't have anything with rooting Nexus devices since rooting them is kind of part of their existence, isn't it?
Thanks again! :good:

Casteel said:
OK! Now we're getting closer
Thank you very much.
But I still have some confusions...
You said:
How did the "cfautoroot" got to my phone sbin folder?
How do I get the capability to copy the superuser files to the system partition?
Putting things in these folders and set their appropriate permissions doesn't require root from the first place?
How is the init.rc calling the recovery script to run the cfautoroot? shouldn't I need root access to modify init.rc?
[Is the CF-Auto-Root source code available somewhere to see all these files you're talking about?]
It sounds like only unlocking the bootloader is giving me some sort of "root" capabilities to do all these stuff. is it true?
Will this method work in non Nexus devices either?
And what are all those "exploits" that so many rooting guides are talking about?
I'm guessing it desn't have anything with rooting Nexus devices since rooting them is kind of part of their existence, isn't it?
Thanks again! :good:
Click to expand...
Click to collapse
"cfautoroot" is a binary created by Chainfire which is embedded in the sbin folder in the kernel ramdisk. It's in the CF Auto Root boot image. Android kernels are essentially Linux kernels and have an init process which is basically a bootstrap/startup process. init.rc is part of this process. It is run when the kernel boots up. Anything within the init process is low-level and essentially run as "root". It kick-starts various other processes like zygote which is the Android process management system. This will help you understand the init process a bit better (http://www.mekya.com/blog/2012/03/android-initialization-from-init-rc-to-third-party-code/). In the init.rc file is a line which "executes" the file /sbin/recovery (which is embedded in the ramdisk along with cfautoroot). This in turn "executes" cfautoroot which takes care of copying the superuser files to the correct locations and setting the correct permission. All this is done within the init process and has elevated (root) permission.
Unlocking the bootloader does not root your phone. It simply allows you to flash "unsigned" (custom) boot images.
Any phone with the ability to flash a custom boot image can make use of this process.
Exploits make use of holes or workarounds to either flash a custom boot image or inject files into the system partition without unlocking the bootloader and are only needed if you cannot unlock the phone bootloader.
Hope this helps!

Casteel said:
Hey guys,
I couldn't find it anywhere and I don't really know if this is the right place to ask, but I'll give it a try...
I wonder how does the CF-Auto-Root for the nexus 5 works?
I can see in the windows batch file that it unlocks the bootloader (that's the easy part) and than boot with some image file.
It seems that this tool is not installing any custom recovery which I always saw is a necessary tool for rooting.
What exactly is this image file? what does it do? Where does it come from? What it contains?
Why it's device related (different image files for different nexus devices running the same stock version).
Thanks,
Casteel.
Click to expand...
Click to collapse
Thank you for asking the question and being polite yet persistent about getting your answer. I have been trying to get to this answer myself for some time now.
Sent from my Nexus 5 using Tapatalk

Great! now we're even closer :victory:
So in the boot process I have elevated privilages, that basically what I was missing.
But this bootable image file is not an image of the OS, isn't it?
It is an image of the kernel?
It is some sort of pre-handled file system that the device is booted into and than startup the OS?
Or something like that...?
Thanks for your patient and the very quiqc responses!
We're almost there...

Casteel said:
Great! now we're even closer :victory:
So in the boot process I have elevated privilages, that basically what I was missing.
But this bootable image file is not an image of the OS, isn't it?
It is an image of the kernel?
It is some sort of pre-handled file system that the device is booted into and than startup the OS?
Or something like that...?
Thanks for your patient and the very quiqc responses!
We're almost there...
Click to expand...
Click to collapse
The boot image is not the OS image. It contains the kernel and the ramdisk. The ramdisk is the basically the root filesystem (/) which the kernel mounts, after which the init process begins and init.rc is called. Nothing is ever persisted or modified in the root filesystem unless it is done during the init process or it is embedded in the ramdisk

craigacgomez said:
The boot image is not the OS image. It contains the kernel and the ramdisk. The ramdisk is the basically the root filesystem (/) which the kernel mounts, after which the init process begins and init.rc is called. Nothing is ever persisted or modified in the root filesystem unless it is done during the init process or it is embedded in the ramdisk
Click to expand...
Click to collapse
Nice.
I thought the root file system is part of the OS image.
So basically, I can have the same OS installed on my devices with different file systems according to what is defined in boot?
One last question and I will stop bother you
Why is the image file device related?
Meaning, why nexus 4, 5 and 7 have different CF-Auto-Root?
(Nexus 7 even got several).
Thanks again!

Casteel said:
Nice.
I thought the root file system is part of the OS image.
So basically, I can have the same OS installed on my devices with different file systems according to what is defined in boot?
One last question and I will stop bother you
Why is the image file device related?
Meaning, why nexus 4, 5 and 7 have different CF-Auto-Root?
(Nexus 7 even got several).
Thanks again!
Click to expand...
Click to collapse
Yes, you could theoretically change the way your filesystem is defined via the boot image, but Android as an OS expects some things.
And each device has different autoroot files because they have different kernels and some differences in some init scripts specific to the hardware. Some devices like the Nexus 7 have multiple version (LTE & non-LTE for example) and there are hardware differences and different kernels.

craigacgomez said:
Yes, you could theoretically change the way your filesystem is defined via the boot image, but Android as an OS expects some things.
And each device has different autoroot files because they have different kernels and some differences in some init scripts specific to the hardware. Some devices like the Nexus 7 have multiple version (LTE & non-LTE for example) and there are hardware differences and different kernels.
Click to expand...
Click to collapse
A thousand thanks, Craig Gomez!
You really helped.
I truely appreciate the patient and the kindful responses.
It was a nice first experience in this forum.
Thank you very much!

Casteel said:
A thousand thanks, Craig Gomez!
You really helped.
I truely appreciate the patient and the kindful responses.
It was a nice first experience in this forum.
Thank you very much!
Click to expand...
Click to collapse
Glad I could help you... It's what communities are all about... Sharing knowledge and experiences.
Sent from my Nexus 5

Excellent thread. Thanks to OP and members who responded.

SM-T116bu Kernel?

I just bought a Samsung tab 3v then I successfully rooted it using this: ( www 4shared com/get/4sFqkNODba/ ) but after I did that I could no longer use the camera (error then force close) so I'm asking if anyone could help me with that please? I did few research they said it's something about the kernel so anyone could provide me with one for my phone?

Someone please help me with this? At least provide me with an already rooted rom.

Stanwar said:
Someone please help me with this? At least provide me with an already rooted rom.
Click to expand...
Click to collapse
have a look through these and see if you can find a kernel :
https://www.google.com/search?q=SM-...es_sm=93&ie=UTF-8#q=SM-T116bu+return+to+stock
i didnt see any promising leads on google for a rom, so your only alternative may be to return to stock. have a look through these for a possible way to do that :
https://www.google.com/search?q=SM-...es_sm=93&ie=UTF-8#q=SM-T116bu+return+to+stock
one small tip for future reference.
you should figure out how to fix your phone and have the tools and files on hand before making any modifications.
personally, i never do anything to my phone before thoroughly learning how to fix it, and if i cant find a way, then i dont mod it.
i see all the time on here, people frantic because they broke their phone and dont have a clue how to fix it.
in some cases there is no way to fix it because the files are not available, its really important to know that before you break it.

bweN diorD said:
one small tip for future reference.
you should figure out how to fix your phone and have the tools and files on hand before making any modifications.
personally, i never do anything to my phone before thoroughly learning how to fix it, and if i cant find a way, then i dont mod it.
i see all the time on here, people frantic because they broke their phone and dont have a clue how to fix it.
in some cases there is no way to fix it because the files are not available, its really important to know that before you break it.
Click to expand...
Click to collapse
Didn't you actually 'think' that I already searched for that on Google? Please try to 'think' that if you don't do mistakes you will never learn so yeah not breaking your phone doesn't mean you're smart OR intelligent.

Stanwar said:
Didn't you actually 'think' that I already searched for that on Google? Please try to 'think' that if you don't do mistakes you will never learn so yeah not breaking your phone doesn't mean you're smart OR intelligent.
Click to expand...
Click to collapse
There's no need to be rude... He was trying to help you

Stanwar said:
Didn't you actually 'think' that I already searched for that on Google? Please try to 'think' that if you don't do mistakes you will never learn so yeah not breaking your phone doesn't mean you're smart OR intelligent.
Click to expand...
Click to collapse
i never implied that you or anyone else wasnt "smart or intelligent"
i have broken my phones many times. the difference between me and a lot of users i see posting here is, i think about what would happen if i do something and it breaks the phone, before i actually do it. then i go and find out how to restore stock, and gather the files and tools first. then i actually restore stock, just so im sure i know how to do it first.
i see and help countless users here on xda, and frequently see people run to flash things they think they have to have right away. frequently that is followed by post pleading for help, because they failed to understand the journey, and chose to jump right to the finish line.
so yes, i agree, not breaking your phone doesnt make you smart or intelligent. knowing how to fix it, and helping others to fix theirs for many years, at minimum should gain those of us who help others a little respect, because we dont get paid to, nor have any obligation to, help anyone.

sdeepb said:
There's no need to be rude... He was trying to help you
Click to expand...
Click to collapse
How come? Posting a Google link is actually helping? Then next time someone asks who's that guy, you tell him Google it. I did come here for a reason, which is finding a developer who can make a prerooted rom for me since it doesn't exist anywhere in the Web.
Anyway I found a solution I will post it here in case someone needed it:
1- Flash the tablet with stock rom (the one of your SM-T116bu) skip to 2 if you already have the stock rom and you only want to root the tablet.
2- Get a file explorer (ES explorer or root explorer).
3- Browse to system/lib and copy the whole lib folder and put it somewhere you can access it later.
4- Flash your tablet using the prerooted SM-T116nu rom (link is above).
5- Using the root explorer replace all files in the system/lib which has a 'camera' word in their name with the same files name from the lib folder of the stock rom, do the same with the files in system/lib/hw6- Reboot your device and the camera should work again.

Stanwar said:
How come? Posting a Google link is actually helping? because believe it or not, some people dont know the best key words to get the results that would actually be helpful, and a lot of times, they dont try at all. so occasionally i try to point them in the right direction, in the hope that they will actually try to help themself, because i cant be of further assistance. Then next time someone asks who's that guy, you tell him Google it. I did come here for a reason, which is finding a developer who can make a prerooted rom for me i can tell you right away, thats not going to happen. this site isnt a place where devs sit waiting for people to make request, so they can make stuff for them. xda is a place where you come to learn how to make it yourself, if you dont already know how, and support the community with it. since it doesn't exist anywhere in the Web.
Anyway I found a solution I will post it here in case someone needed it:
1- Flash the tablet with stock rom (the one of your SM-T116bu) skip to 2 if you already have the stock rom and you only want to root the tablet.
2- Get a file explorer (ES explorer or root explorer).
3- Browse to system/lib and copy the whole lib folder and put it somewhere you can access it later.
4- Flash your tablet using the prerooted SM-T116nu rom (link is above).
5- Using the root explorer replace all files in the system/lib which has a 'camera' word in their name with the same files name from the lib folder of the stock rom, do the same with the files in system/lib/hw6- Reboot your device and the camera should work again.
Click to expand...
Click to collapse
^^^^^

Stanwar said:
How come? Posting a Google link is actually helping? Then next time someone asks who's that guy, you tell him Google it. I did come here for a reason, which is finding a developer who can make a prerooted rom for me since it doesn't exist anywhere in the Web.
Anyway I found a solution I will post it here in case someone needed it:
1- Flash the tablet with stock rom (the one of your SM-T116bu) skip to 2 if you already have the stock rom and you only want to root the tablet.
2- Get a file explorer (ES explorer or root explorer).
3- Browse to system/lib and copy the whole lib folder and put it somewhere you can access it later.
4- Flash your tablet using the prerooted SM-T116nu rom (link is above).
5- Using the root explorer replace all files in the system/lib which has a 'camera' word in their name with the same files name from the lib folder of the stock rom, do the same with the files in system/lib/hw6- Reboot your device and the camera should work again.
Click to expand...
Click to collapse
1. First respect others, no one gets paid or forced to do anything here
2. What kinda help you want ? if you want the most perfect thing all the times than I'm sorry as we only have humans here, not super computers with everything stored on them !

T116BU Tab E Rooted Without Camera or Unrooted? I want neither... Can anybody help?
Stanwar said:
How come? Posting a Google link is actually helping? Then next time someone asks who's that guy, you tell him Google it. I did come here for a reason, which is finding a developer who can make a prerooted rom for me since it doesn't exist anywhere in the Web.
Anyway I found a solution I will post it here in case someone needed it:
1- Flash the tablet with stock rom (the one of your SM-T116bu) skip to 2 if you already have the stock rom and you only want to root the tablet.
2- Get a file explorer (ES explorer or root explorer).
3- Browse to system/lib and copy the whole lib folder and put it somewhere you can access it later.
4- Flash your tablet using the prerooted SM-T116nu rom (link is above).
5- Using the root explorer replace all files in the system/lib which has a 'camera' word in their name with the same files name from the lib folder of the stock rom, do the same with the files in system/lib/hw6- Reboot your device and the camera should work again.
Click to expand...
Click to collapse
Thanks, but your method soft bricks (black screen, can't operate the phone at all after booting) the phone until I flash the rooted or the official ROM again. There's no hw6 folder either, just hw and even changing only the lib files with camera in their names will also soft brick the phone.
I found a solution!!!
Restored my phone to the latest official ROM, then flashed the tiny file from the topic below using ODIN.
http://forum.xda-developers.com/devdb/project/?id=10223#downloads
Worked like a charm!

Fdamaral said:
Thanks, but your method soft bricks (black screen, can't operate the phone at all after booting) the phone until I flash the rooted or the official ROM again. There's no hw6 folder either, just hw and even changing only the lib files with camera in their names will also soft brick the phone.
I found a solution!!!
Restored my phone to the latest official ROM, then flashed the tiny file from the topic below using ODIN.
http://forum.xda-developers.com/devdb/project/?id=10223#downloads
Worked like a charm!
Click to expand...
Click to collapse
The solution was so nice that I even made a short video explaining what I did with my Samsung Galaxy Tab E SM-T116BU from Brazil!!

Pre-Installing APKs on Nexus Player Oreo stock rom

This really should be asked in the dev forum, But my post count is not high enough or worthy!
I have several Nexus Players I plan on selling with the oreo update pre installed, There are 2 addl non playstore apps I need to include as part of the package.
I'm trying to avoid "profiling" the devices to add the 2 extra apps. I have flashed the oreo upgrade to all 8 of them.
I cannot push the apks without profiling to enable adb nor can I seem to find a good zip template to make use the bootloader recovery adb function.
I have tested a few and they all fail with footer and signature failures? I'm only left with a few ideas. Please comment if you can help with any of the options below or suggest a better one..
1. Find a proper update.zip template that works with nexus player..Oreo 8.0 or can bypass the check..
2. Can apps installed in a profiled device be preserved thru a reset method that would allow the device to startup with the first run screens re-instated? Remote setup, WiFi, User account.. Out of the box experience?
3. Can an APK or ZIP be copied to a location on the Nexus Player that would allow it to be installed on first run? (I seem to think Youtube does this)
4. Least popular... Modify the Oreo upgrade img to have the 2 apps pre installed? <--This option looks messy..
Any suggestions appreciated!! Thanks

I suppose #2 is possible if you install as a system app.
Sent from my KFFOWI using Tapatalk

rufy93 said:
I suppose #2 is possible if you install as a system app.
Sent from my KFFOWI using Tapatalk
Click to expand...
Click to collapse
After careful examination, #2 and #4 are really the same thing. Without root, I would have to mount the oreo system.img file in linux and add the 2 apks to root/system/app then repack the img file to re-burn the rom. Not exactly sure if that would be enough, I assume there is some checksum or signing in the image file to prevent guys like me from modifying it. Also what would happen after google hits it with an update? would these apps survive? Finding the answer to why the stock Oreo bootloader recovery adb fails to accept the typical update zip format will end up being the right solution.

If you wish to flash using the stock recovery, the update zip must be properly signed. This usually means by the oem private keys.
I haven't been following the modding scene for a long time, but I'm sure these are still inaccessible.
Sent from my KFFOWI using Tapatalk