[HOW-TO] [GUIDE] Fix "Cannot Connect To Camera" Error - Verizon Samsung Galaxy S III

I had just received a fresh new Galaxy SIII from Asurion and eagerly rooted and flashed my favorite AOSP ROM and found out my camera wasn't working. I search through these forums like a mad man trying to find a solution and I tried EVERYTHING but then I read someone's reply to troubleshooting and I admit I may have been overlooking the wording in some of these guides as to the path of my camera files but I fixed it and I want to share my findings so someone who is having a similar issue can get it fixed too. I'm also going to add the methods that didn't work but may work in other cases.
This fix ultimately replaces bad or missing firmware files. If you haven't tried Odin back to stock, re-rooting, or wiping data and getting a fresh start, I would recommend that first. This is more or less if sh** hits the fan.
THIS IS ONLY FOR THE GALAXY SIII
***MY FIX***
BACKUP ANYTHING IMPORTANT JUST IN CASE
Download this zip https://dl.dropboxusercontent.com/u/91693945/CameraFiles-signed.zip
Flash using Recovery
Wipe Cache & Dalvik (optional)
Fix Permissions
Reboot into Android
Start the camera app and cross your fingers
***MY FIX (Old Way)***
Download any TouchWiz based ROM to your phone or computer.
Unzip the ROM
Goto /system/cameradata and copy all the SlimISP files to your phone.
Goto /data and there should be another SlimISP bin file, copy that but don't mix it up.
Move these to the files to the corresponding areas of your phone.
Check permissions, I granted full access to Root, and User
Start the camera app and cross your fingers
Reboot if it didn't work immediately
I recommend keeping a copy of these on your ExtSD if you have one because you will have to do this if you flash a new ROM.
***Other Guides***
Same sort of directions also contains files you can download.
http://forum.xda-developers.com/showthread.php?p=40409206#post40409206
This is an explanation to what I put above and the guide that ultimately fixed my problems (Single-Post rest of thread is helpful too).
http://forum.xda-developers.com/showpost.php?p=37257851&postcount=11
For all you TouchWiz lovers, this might not be as relevant anymore but I'm putting it here anyway.
http://forum.xda-developers.com/showthread.php?t=2006128
SlimSnoopOS posted this below and I'll add it here.
http://rootzwiki.com/topic/100194-cant-connect-to-the-camera-again/page-2
If people have questions post them here or PM me I want to help anyone having this issue. Being as attached to my phone as I am I was really put out by all the trial and error.

Appreciate the guide, hope it helps someone down the road. I'm in the camp that has no issues going back and forth between AOSP 4.3 or TW. I'll add this Rootz link as well which provides some additional information and might be making its way into roms via Github. Seems like as good an opportunity to spread the wealth.

Zophone i5 v8?
dwibbles33 said:
I had just received a fresh new Galaxy SIII from Asurion and eagerly rooted and flashed my favorite AOSP ROM and found out my camera wasn't working. I search through these forums like a mad man trying to find a solution and I tried EVERYTHING but then I read someone's reply to troubleshooting and I admit I may have been overlooking the wording in some of these guides as to the path of my camera files but I fixed it and I want to share my findings so someone who is having a similar issue can get it fixed too. I'm also going to add the methods that didn't work but may work in other cases.
This fix ultimately replaces bad or missing firmware files. If you haven't tried Odin back to stock, re-rooting, or wiping data and getting a fresh start, I would recommend that first. This is more or less if sh** hits the fan.
***MY FIX***
Download any TouchWiz based ROM to your phone or computer.
Unzip the ROM
Goto /system/cameradata and copy all the SlimISP files to your phone.
Goto /data and there should be another SlimISP bin file, copy that but don't mix it up.
Move these to the files to the corresponding areas of your phone.
Check permissions, I granted full access to Root, and User
Start the camera app and cross your fingers
Reboot if it didn't work immediately
I recommend keeping a copy of these on your ExtSD if you have one because you will have to do this if you flash a new ROM.
***Other Guides***
Same sort of directions also contains files you can download.
http://forum.xda-developers.com/showthread.php?p=40409206#post40409206
This is an explanation to what I put above and the guide that ultimately fixed my problems (Single-Post rest of thread is helpful too).
http://forum.xda-developers.com/showpost.php?p=37257851&postcount=11
For all you TouchWiz lovers, this might not be as relevant anymore but I'm putting it here anyway.
http://forum.xda-developers.com/showthread.php?t=2006128
SlimSnoopOS posted this below and I'll add it here.
http://rootzwiki.com/topic/100194-cant-connect-to-the-camera-again/page-2
If people have questions post them here or PM me I want to help anyone having this issue. Being as attached to my phone as I am I was really put out by all the trial and error.
Click to expand...
Click to collapse
I am facing the same problem on my iphone clone - zophone i5 v8. These models do not have a "cameradata" folder in /system. Do you have a fix for these MTK phones?

shailendrachimade said:
I am facing the same problem on my iphone clone - zophone i5 v8. These models do not have a "cameradata" folder in /system. Do you have a fix for these MTK phones?
Click to expand...
Click to collapse
Me too had problem with camera, but it seems like i got fixed it finally... I have a Cubot One MTK6589 with Miui rom. The steps are:
1. http://d-h.st/BKA download this file and flash it. It will install jb camera for your mobile.
2. check it
3. if it works delete the old camera app with titanium backup because if u run the old bad camera app the problem will come back and u have to flash again.
4. install some good camera app like camera awesome because for me the jb camera doesn't detected my front camera.
I hope this will help you!

Will Try
papp-david said:
Me too had problem with camera, but it seems like i got fixed it finally... I have a Cubot One MTK6589 with Miui rom. The steps are:
1. http://d-h.st/BKA download this file and flash it. It will install jb camera for your mobile.
2. check it
3. if it works delete the old camera app with titanium backup because if u run the old bad camera app the problem will come back and u have to flash again.
4. install some good camera app like camera awesome because for me the jb camera doesn't detected my front camera.
I hope this will help you!
Click to expand...
Click to collapse
Let me try..thanks!
---------- Post added at 05:33 PM ---------- Previous post was at 04:58 PM ----------
shailendrachimade said:
Let me try..thanks!
Click to expand...
Click to collapse
I flashed successfully...but I do not see any camera app installed? I can see the Galary app. Even tried deleting original camera app by Titanium, still same issue.

Thank you. I also had this problem with any aosp ROM but the fix stopped working for me with the kk ROMs did you have the same problem?

Uou need to patch the shared objects using your stock tom files
Sent from my SM-N9006 using xda app-developers app

remzej said:
Uou need to patch the shared objects using your stock tom files
Sent from my SM-N9006 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the reply.. Bit could you explain a little more?

evertking said:
Thanks for the reply.. Bit could you explain a little more?
Click to expand...
Click to collapse
shailendrachimade said:
Let me try..thanks!
---------- Post added at 05:33 PM ---------- Previous post was at 04:58 PM ----------
I flashed successfully...but I do not see any camera app installed? I can see the Galary app. Even tried deleting original camera app by Titanium, still same issue.
Click to expand...
Click to collapse
dwibbles33 said:
I had just received a fresh new Galaxy SIII from Asurion and eagerly rooted and flashed my favorite AOSP ROM and found out my camera wasn't working. I search through these forums like a mad man trying to find a solution and I tried EVERYTHING but then I read someone's reply to troubleshooting and I admit I may have been overlooking the wording in some of these guides as to the path of my camera files but I fixed it and I want to share my findings so someone who is having a similar issue can get it fixed too. I'm also going to add the methods that didn't work but may work in other cases.
This fix ultimately replaces bad or missing firmware files. If you haven't tried Odin back to stock, re-rooting, or wiping data and getting a fresh start, I would recommend that first. This is more or less if sh** hits the fan.
THIS IS ONLY FOR THE GALAXY SIII
***MY FIX***
BACKUP ANYTHING IMPORTANT JUST IN CASE
Download this zip https://www.dropbox.com/s/bt1ucpgb9xfmjbi/CameraFiles-signed.zip
Flash using Recovery
Wipe Cache & Dalvik (optional)
Fix Permissions
Reboot into Android
Start the camera app and cross your fingers
***MY FIX (Old Way)***
Download any TouchWiz based ROM to your phone or computer.
Unzip the ROM
Goto /system/cameradata and copy all the SlimISP files to your phone.
Goto /data and there should be another SlimISP bin file, copy that but don't mix it up.
Move these to the files to the corresponding areas of your phone.
Check permissions, I granted full access to Root, and User
Start the camera app and cross your fingers
Reboot if it didn't work immediately
I recommend keeping a copy of these on your ExtSD if you have one because you will have to do this if you flash a new ROM.
***Other Guides***
Same sort of directions also contains files you can download.
http://forum.xda-developers.com/showthread.php?p=40409206#post40409206
This is an explanation to what I put above and the guide that ultimately fixed my problems (Single-Post rest of thread is helpful too).
http://forum.xda-developers.com/showpost.php?p=37257851&postcount=11
For all you TouchWiz lovers, this might not be as relevant anymore but I'm putting it here anyway.
http://forum.xda-developers.com/showthread.php?t=2006128
SlimSnoopOS posted this below and I'll add it here.
http://rootzwiki.com/topic/100194-cant-connect-to-the-camera-again/page-2
If people have questions post them here or PM me I want to help anyone having this issue. Being as attached to my phone as I am I was really put out by all the trial and error.
Click to expand...
Click to collapse
The file is not available on dropbox for download , i am using AOKP on SG3 and the camera stops working if i open through whatsapp or any other app and when i go back to the camera it gives that error

Try the One+ One or AOSP modded cameras in the Apps and Themes section. One+ One camera is awesome!

Ahmadqatei said:
The file is not available on dropbox for download , i am using AOKP on SG3 and the camera stops working if i open through whatsapp or any other app and when i go back to the camera it gives that error
Click to expand...
Click to collapse
Link fixed, sorry I don't really keep up with this anymore, my bad

fix front camera
work for my mtk device
edit builtprop, open the editor and change or add
hw.cameras=1
ro.camera.dcim=1
explanation
# hw cameras
hw.cameras = 2 (1 only for the Front, 2 for the Front & Back)
# camera DCIM dir. 0: sd only; 1: nand only; 2, sd first
ro.camera.dcim = 1
This is likely to occur due to the use of internal memory is converted into ROM
while the external sdcard memory is converted into internal
hopefully work
:cyclops:

Just sharing:
flashing didn't work, used servicely and added camera service to hitlist.

can i use it on galaxy core

Related

[App][Mod]Google Wallet Installer

Google Wallet Installer for Verizon, AT&T, T-Mobile, and US Cellular Samsung Galaxy S3.
Requires ROOT, an UNLOCKED BOOTLOADER, and BUSYBOX!(A deodexed ROM is just recommended)
My newest project, RemoteFlash, was just released! Take a look and give it a try!
Wallet Installer Is Now Available For Free To All Supported Carrier Models On XDA! (Donations Appreciated)
My application, "Wallet Installer", will install Google Wallet on almost any US based Samsung Galaxy S3. It simply edits your build.prop and then places the correct modifications into your system. It downloads all the files from my personal server, which is pretty quick. Just select the appropriate Rom type: AOSP, JB Touchwiz, or ICS TouchWiz, and then your carrier: Verizon, AT&T, T-Mobile, or US Cellular. I also added a restore option for your build.prop, so you can restore it after you setup Google Wallet. Hopefully this helps you out and makes the process easier!
Wallet Installer has been updated on the server side. The credit goes to Paul Obrien for the new version! To install it, simply reset Google Wallet, delete it, and then rerun Wallet Installer! Make sure to also have BusyBox installed/updated!
Please donate if my work helps you : )
V3: No Recovery/More Stable
And as always: I take no responsibility for bricked devices, whether a soft brick or a full on brand new coffee coaster.​
Dude. You are awesome. I was just in the official wallet thread and was hesitant on going through with it because it seemed daunting having to change the build prop. I'm about to flash slim Bean 3.1 and then try this out. Will update this post once I finish trying it out . Hopefully all goes well!!!
Well I ended up lagging on the install but just wanna say thanks again because it worked perfectly. First try and not a single problem as of yet. Awesome!!
Glad to help! Hopefully all goes well! If the download stalls just give it a while, my server is a retired galaxy nexus hooked up to WiFi lol. My WiFi sucks sometimes.
Internal SDcard Corrupt?
Prl91 said:
Google Wallet Installer for Verizon Samsung Galaxy S 3's(d2vzw)​
My application, "WalletInstaller", will install Google Wallet on any Verizon S3. It simply swaps out your build.prop with a modified one and then flashes an open recovery (TWRP 2), and in the open recovery flashes the latest version of Google Wallet along with the required NFC libs for your rom. It downloads all the files from my personal server, which can be somewhat slow, but I'll be upgrading soon. Hopefully there won't be any download issues. Just select the appropriate rom type: AOSP, JB Touchwiz, or ICS TouchWiz. Hopefully it helps you out and makes the process easier! It has been tested on my device, which is running CM10, but the other options haven't been tested, but they should work great. I will also hopefully make it to support all US carrier based S3's after the weekend is over.
My application will be in the market for 99 cents if you feel like supporting the cause(will post link once uploaded), or you can download it here for free. Please don't post links to my application without my personal consent. Thank you!
And as always: I take no responsibilty for bricked devices, whether a soft brick or a full on brand new coffee coaster.
Click to expand...
Click to collapse
So I installed the app and set it all up just fine, in fact, I was about to test out wallet at a locat establishment but I noticed something was a little weird. I tried to change my wallpaper to a picture in my gallery. For some reason I got an error that "Not enough space. Delete photos, music, etc." Last time I checked I had plenty of space. I opened up setting and storage to find my device storage has a total of 4GB of space (with close to 2GB's of free space remaining). My S3 is a 16GB unit. Obviously things are a bit haywire. I'm running CleanROM 5.0 at the moment so I'm not sure if your app would conflict with that but things were fine prior to this. What do you think?
when i choose ics touchwiz install it loads terminal emulator and says rm failed for /system/build.prop no such file or directory
I'm not sure if my app would interfere quite like that. It shouldn't, but when messing with the build.prop and a custom ROM you can never be positive. If anything else odd happens, pm me and I'll look into it.
brusslesprouts said:
when i choose ics touchwiz install it loads terminal emulator and says rm failed for /system/build.prop no such file or directory
Click to expand...
Click to collapse
It's possible that your system didn't mount properly, or that your ROM is using some sort of mod that moved the build.prop, or it may have been removed or altered by another application.
Got mine installed and all looks good but same thing about the wallpaper..........says no space even though it has space.
Ronin09 said:
Got mine installed and all looks good but same thing about the wallpaper..........says no space even though it has space.
Click to expand...
Click to collapse
That's odd. What ROM type are you running?
CleanROM 5 also
I mean it installed great. I even put a new debit card on it. Going to try it out in just a hour or so but no space when using the gallery to change wallpaper
Ronin09 said:
CleanROM 5 also
I mean it installed great. I even put a new debit card on it. Going to try it out in just a hour or so but no space when using the gallery to change wallpaper
Click to expand...
Click to collapse
Maybe it's just an issue with CleanRom. Still really weird though. I won't know til more people give it a shot. Anyways, let me know if wallet works! Thanks for trying it.
Hope your bugs get worked out I'll gladly buy/donate to this app
Sent from my SCH-I535 using xda premium
Hulk0069 said:
Hope your bugs get worked out I'll gladly buy/donate to this app
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Thanks Hulk! I'm sure I can get it all ironed out, it'll just take some time ; )
Same wallpaper issue. Also now I cannot access internal sd card via root explorer.
Sent from my Galaxy Nexus using xda app-developers app
Same here, I can't access Internal Card........if not a fix soon, I will probably have to redo flash of ROM and just wait for better wallet. This worked too btw
---------- Post added at 07:50 AM ---------- Previous post was at 07:08 AM ----------
Here's one question for you...
Why does your installation include TWRP 2.3.1.0.
I already had a CWM Recovery...that was strange to me.....when I get to work I am going to try to flash over that to see if that's the problem. Could be that. But right now I can't access my internal drive let alone the backups if I were to start over.......LOL.....I wouldn't be able to get to.
Live and Learn I guess.
Ronin09 said:
Same here, I can't access Internal Card........if not a fix soon, I will probably have to redo flash of ROM and just wait for better wallet. This worked too btw
---------- Post added at 07:50 AM ---------- Previous post was at 07:08 AM ----------
Here's one question for you...
Why does your installation include TWRP 2.3.1.0.
I already had a CWM Recovery...that was strange to me.....when I get to work I am going to try to flash over that to see if that's the problem. Could be that. But right now I can't access my internal drive let alone the backups if I were to start over.......LOL.....I wouldn't be able to get to.
Live and Learn I guess.
Click to expand...
Click to collapse
I'm sorry that you're having trouble. I included TWRP because it uses an open, unencrypted script file to pass commands to recovery. CWM, from my understanding, requires an encrypted, not so universal script file called extended commands. Depending on what recovery someone was running, flashing a script would not work, or it would possibly brick their device. I wanted to make sure everything was done correctly.
Also... I will take a look at all my server side files today and the app. I can't make changes from where I am, since I don't have ftp setup and I'm out of town, but I can download them and see where I may have gone wrong. My best guess is the build.prop swap causing issues, if any of you have possible leads, post them here and I can attempt a fix later today or tomorrow.
BTW...Wallet worked like a charm in 7-11 and Whole Foods
Taking pictures is a little harder too...have to switch to external to save the pictures....the Camera 4.2 doesn't even allow you to switch to external card.
Would be a shame to scrap this working wallet for these issues
Ronin09 said:
BTW...Wallet worked like a charm in 7-11 and Whole Foods
Taking pictures is a little harder too...have to switch to external to save the pictures....the Camera 4.2 doesn't even allow you to switch to external card.
Would be a shame to scrap this working wallet for these issues
Click to expand...
Click to collapse
I'm getting ready to attempt a flash on CleanRom in a few minutes to see if that's the only ROM having issues. Hopefully you guys can stick this out until everything's working great ; )
I flashed wallet and libs using my app on CleanRom 5. I was able to replicate the same error as you guys posted. Also, I don't know if you guys checked, but in recovery it mounts the internal sdcard perfectly, so that tells me it may have something to do with CleanRom in specific. I'm going to flash through some stock touchwiz ROMs with Odin and see what results I get in that area. Hopefully it's just a ROM specific ordeal. Sorry for the long posts, just trying to keep you all updated!

"Couldn't Capture Screenshot."

I've had the opo for about two weeks now & have flashed a couple of different on my device looking for a daily driver. I'm having issues taking screenshot. Idk if this is new because I haven't tried until this morning to take a screenshot on my device. I constantly get an error stating "can't take screenshot due to limited storage space, or it isn't allowed by the app or your organization." Has anyone else experienced this error with cyanogenmod or Android lollipop in general?
Att.Fan1982 said:
I've had the opo for about two weeks now & have flashed a couple of different on my device looking for a daily driver. I'm having issues taking screenshot. Idk if this is new because I haven't tried until this morning to take a screenshot on my device. I constantly get an error stating "can't take screenshot due to limited storage space, or it isn't allowed by the app or your organization." Has anyone else experienced this error with cyanogenmod or Android lollipop in general?
Click to expand...
Click to collapse
Nopes.
Try clearing cache/dalvik cache via recovery.
I hope your internal memory is not full.
Try to take the screenshot using any third party app. Also try hardware buttons method.
If still it doesn't works out for you, provide us your ROM information, like it's build date and try to find out the users who are on same nightly and whether they are facing same issue or not.
I hope this helps you
Mr hOaX said:
Nopes.
Try clearing cache/dalvik cache via recovery.
I hope your internal memory is not full.
Try to take the screenshot using any third party app. Also try hardware buttons method.
If still it doesn't works out for you, provide us your ROM information, like it's build date and try to find out the users who are on same nightly and whether they are facing same issue or not.
I hope this helps you
Click to expand...
Click to collapse
None of the above methods solved the problem. I've experienced this same issue on a few different roms(blisspop v2.1, cyanide 8.0, sabermod 3/23/15 build).
Att.Fan1982 said:
None of the above methods solved the problem. I've experienced this same issue on a few different roms(blisspop v2.1, cyanide 8.0, sabermod 3/23/15 build).
Click to expand...
Click to collapse
Flash back to kitkat than
I am on CyanideL 8.0, no such issues.
I was on BlissPop 2.1, no such issues.
If you face same issue on KitKat, then there is some hardware issue
Mr hOaX said:
Flash back to kitkat than
I am on CyanideL 8.0, no such issues.
I was on BlissPop 2.1, no such issues.
If you face same issue on KitKat, then there is some hardware issue
Click to expand...
Click to collapse
Thanks, I'm restoring my stock root backup now in twrp recovery & will post my results if this solved the issue or not
Edit: No luck on the stock root screenshot either, guess I'll just have to live with the fact I can't take a screenshot on my device, at least until a definitive solution is found
Okay, latest update..........I did a factory restore + unroot using bacon root toolkit then re-rooted my device using the same toolkit & restored my nandroid of my last rom and................................................................................................................................................great news screenshots are working now! :good:
Mr hOaX said:
Nopes.
Try clearing cache/dalvik cache via recovery.
I hope your internal memory is not full.
Try to take the screenshot using any third party app. Also try hardware buttons method.
If still it doesn't works out for you, provide us your ROM information, like it's build date and try to find out the users who are on same nightly and whether they are facing same issue or not.
I hope this helps you
Click to expand...
Click to collapse
Even I am facing the same problem after updating CM12 latest version yesterday. Please help
I had this tonight on COS 12.1. A reboot cleared it for now.
I am having the same problem but got fed up searching a fix , I felt a waste of time searching for it too afterall how many times do we use that feature. i downloaded a third party app for the same & its working like a charm. Problem solved
Screenshot Issue
I am facing the same problem
---------- Post added at 08:21 PM ---------- Previous post was at 07:59 PM ----------
hey guys,
You gotta follow these steps to get your screenshots up and running.
1. Open file manages
2. Look for PICTURES folder.
3. Rename it to PICTURES2 or something
That's It.... Screenshots up and running....
Now Why is that ? Thats becausethe folder PICTURES is actually supposed to be Pictures. When you try to capture a screenshot, the screenshot app looks for a folder called Pictures but since it doesn't exist, it tries to create it. But File Manager doesn't differentiate between Pictures and PICTURES. Hence the error. When you do the rename and capture a screenshot you can actually see a folder called Pictures created. Now you can move the data from PICTURES2 to Pictures(Only the important one and without deleting anyexisting content in Pictures). It is safe to delete the PICTURES2 folder after this.
For now, screenshots work after renaming pictures to pictures 2 but I am unable to delete my pictures 2 now. There is a file name screenshot inside(not image). Any suggestions how to delete this?
Thank you.
saqlainsyed007 said:
I am facing the same problem
---------- Post added at 08:21 PM ---------- Previous post was at 07:59 PM ----------
hey guys,
You gotta follow these steps to get your screenshots up and running.
1. Open file manages
2. Look for PICTURES folder.
3. Rename it to PICTURES2 or something
That's It.... Screenshots up and running....
Now Why is that ? Thats becausethe folder PICTURES is actually supposed to be Pictures. When you try to capture a screenshot, the screenshot app looks for a folder called Pictures but since it doesn't exist, it tries to create it. But File Manager doesn't differentiate between Pictures and PICTURES. Hence the error. When you do the rename and capture a screenshot you can actually see a folder called Pictures created. Now you can move the data from PICTURES2 to Pictures(Only the important one and without deleting anyexisting content in Pictures). It is safe to delete the PICTURES2 folder after this.
Click to expand...
Click to collapse
Hi Guys,
Seems the internal memory permission has been jumbled up and you need to fire the following command to restore the same. Connect with adb while booted in recovery and run the following commands to correct the permissions. After that your problem might get solved:
Code:
chown -R media_rw:media_rw /data/media/
find /data/media/ -type d -exec chmod 775 {} ';'
find /data/media/ -type f -exec chmod 664 {} ';'
Thanks

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!!

{GUIDE} Flashing the SM-935U firmware onto your Verizon S7 Edge and Rooting

Alright here is a guide to installing the unlocked S7 Edge firmware onto your Verizon S7 edge. I will also be giving some tips on setting up specific parameters to get the best battery and performance towards the end of this guide. A list of credits for all the folks who actually discovered and wrote about all these topics will be at the end of the guide as well. All credit goes to those guys!!!!
I am not responsible for anything that occurs to your phone. Period. Use this Guide at your own risk.
Part 1: Installing the 935U firmware
WARNING: YOU WILL LOSE ALL DATA ON YOUR PHONE (except SD card)! BACKUP EVERYTHING BEFORE YOU START THIS PROCESS.
Before you start, make sure you have the Samsung phone USB drivers installed. If you do not have them installed ODIN will not recognize your phone. Here is a link to the drivers installation package: http://downloadcenter.samsung.com/c...G_USB_Driver_for_Mobile_Phones_v1.5.45.00.exe
Note: I personally had success with this version of Odin: https://www.dropbox.com/s/6a2xg2frrin92o6/odin_3.12.3.rar?dl=0 (MD5 - 9C878DB69273148F01910D1CBCB1ABBD)
However another user couldn’t get it to work and used this version: https://www.dropbox.com/s/hfe8zn2adnwdtuw/ODIN .zip?dl=0 (MD5 - 136E707B39C2E4CDC47820C68065CD5C)
How to install:
Step 1. Put your phone in download mode. You do this by having the phone off and pressing the power button, the home button, and the volume down button at the same time, holding them until the download screen comes up. Sometimes there will be a prompt that says press the home button to continue to download mode. In that case press the home button as well.
Step 2. Flash the 4 files in this zip (https://www.androidfilehost.com/?fid=24588212152304771)(MD5 - BB4D013B3B6D7638484A4B0F56953BFA) to your phone using Odin, all 4 of them at the same time. Unzip the files into the folder that contains your ODIN installation, or a folder where they are easy to find. Open up ODIN and put the BL file in the BL slot, AP file in the AP slot, and so on. Then flash all 4 at once.
I have flashed the U firmware multiple times in experimentation and at one point the flash failed. I simply forced the phone to reboot into download mode (by the normal method listed above) and tried reflashing. It went through just fine. So don't panic, just retry.
Part 2: Rooting the U firmware
NOTE: This guide is mostly taken from an excellent guide already made by @Argyrus. The only reason I am posting it here is to keep the flow of the overall guide together.
First off download these files (https://www.dropbox.com/s/x4yymhbthn6nmqp/Root Files.zip?dl=0) and extract all the files to one main folder. Make sure all the files that are in the "SuperSU-v2.76-S7QC" folder are moved to the main folder.
- Folder named "SuperSU-v2.76-S7QC" contains the SuperSU and thing needed to root the phone
- ADB Setup EXE called "adb-setup-1.4.3.exe", needed to install ADB and the Drivers
- Special patched Odin that skips the SHA 225 called Odin PrinceComsy.exe (Mainly for AT&T) including an .ini file named "Odin3.ini"
- file named "Samsung_G935x_QC_Rooted_BOOT.TAR", this is the engBoot for the phone that will allow rooting
NOTE: Some users have experienced endless boot loop; this seems to be caused by using a package disabler that disabled certain services. If you used one and end up getting an endless boot loop try wiping the cache and factory reset the phone.
1. Install ADB by running adb-setup-1.4.3.exe (select YES to all options, especially system wide ADB)
2. Make sure to put your phone into downloading mode (Power off--- Hold Down arrow + Home + Power button)
3. Open up Odin and click AP and mount Samsung_G935x_QC_Rooted_BOOT.TAR, then flash it
4. Once restarted put the phone into USB debugging mode, if it is not already enabled (need Developer options for this)
4b. To get developer mode, go to "About" then tap "build number" about 6 or 7 times
4c. Go back to settings and you should now see developer options, turn on USB debugging
5. Now back on your PC, double click on the file called "root.bat" (it should be in the main folder with ALL the other files, aka no subfolders)
6. Wait for the CMD to finish and then your phone should restart
7. Once your phone has finally restarted you will notice that SuperSU was installed and root should be working, download root checker to find out for yourself.
Part 3: Implementing all the Verizon specific fixes (enable Verizon volte, fix wifi password saving issues, doze issues, cpu issues, VVM, etc.)
1. Download the Verizon s7 edge fix zips (there are two zips that will be flashed together in a certain order) (File 1 - http://dl.psouza4.com/android/S7_or_S7Edge_Fixes_V15.zip)(File 2 - https://www.androidfilehost.com/?fid=24591023225178488)
2. Use Flashfire (https://play.google.com/store/apps/details?id=eu.chainfire.flash&hl=en) to flash both zips, keep the standard options that are already selected in Flashfire. Arrange the zips so that S7_or_S7Edge_Fixes_V15.zip is flashed first, and Verizon_VVM_Volte_Wifi_Calling_G935U_Fix.zip is flashed second. It will auto reboot after flashing both files.
3. Profit
Also it is always a good idea to change all the animation speeds to .5, which you can find under the developer options. This speeds up the phone visually, providing for a faster user experience.
Part 4: Setting up xposed and additional battery life saving tools (optional)
These are some steps that I have taken to see great battery life results. Feel free to try them out and see if they work for you.
1. Install xposed using Flashfire (only use the modified xposed zip below or else you will have serious issues)
Here is the modified xposed zip to flash through Flashfire (https://www.dropbox.com/s/67aujyog5...arm64-custom-build-by-wanam-20160709.zip?dl=0)
Note: It takes a while to boot after flashing this due to the cache rebuild. Do not panic, let it do its thing.
Also you will need to install the Xposed apk to be able to use Xposed: (https://www.dropbox.com/s/euqp5ofg32gjspj/XposedInstaller_3.0_alpha4.apk?dl=0)
2. Install Greenify (xposed module) and enable all the additional features (donate only), including aggressive doze. Add any apps that are running in the background that seem to be battery hogs and enable auto-hibernation.
I also went through the system files and removed or froze any Samsung files I did not want with Titanium. But that's just a personal preference of mine, I'm OCD about files I have enabled on my phone lol.
Note: By request I have posted screenshots of all the files I have frozen, as well as a screenshot of all the apps I have greenifyed. I decided to Greenify more apps than disable this time to see if I get the same battery life as disabling everything. Time will tell.
That's about it. Hopefully this is helpful to us Verizon users who are trying to comb through multiple forums trying to find all the pieces to the puzzle in regards to flashing and rooting the U firmware. I am simply putting everything into one guide, along with any additions which I learned from my personal experience flashing and rooting my S7E onto the U firmware.
If there is any questions or comments hit me up, i'd be happy to help anyway I can.
Cheers!
Credits: 
 @Misterxtc for the U firmware link (and firmware updates in general)
@wanam for the modified xposed installation for samsung phones
@psouza4 for the fix zip that cures many issues
@gtg465x for providing info on the U files
@Symphony0fLife for his excellent AT&T guide which I used a lot of here
@jrkruse for his CSC and ims hacks and the U fix zip
@Argyrus for his guide on how to root our Verizon phones
@Mastajeff for his original T-mobile guide that helped Argyrus and I with our guides
@br3w3r, @Chainfire and @princecomsy for making the root possible and guiding us towards the light of freedom
@Syn Ack for posting a guide with all the fixes he had collected from other forums
@lahegry for originally posting the modified xposed zip
@Snoop05 for his awesome system wide ABD installation package
NOTE: If I have forgotten anyone on the credits list please let me know and I will add them.
Thank you. Great guide!
Nicely done!
I would love for someone who uses wifi calling on Verizon to try out the CSC file replacement I have posted here. I want to see if that file fixes that function but i personally don't use Wi-Fi calling so I can't test out out.....
Sent from my Verizon S7 Edge (U firmware / rooted)
This is outstanding. Thank you so much!
I've yet to go through the whole process, as I want to set aside some time to prepare everything, etc. But I was wondering whether you'd be willing to share a list of the packages you froze or removed with Titanium. I am also a minimalist when it comes to what files I keep around on any device. If you'd prefer to share via PM, that's fine too. I know those kinds of lists elicit a variety of reactions from a variety of users.
Sent from my SM-G935V using XDA Labs
TheWu-Wei said:
This is outstanding. Thank you so much!
I've yet to go through the whole process, as I want to set aside some time to prepare everything, etc. But I was wondering whether you'd be willing to share a list of the packages you froze or removed with Titanium. I am also a minimalist when it comes to what files I keep around on any device. If you'd prefer to share via PM, that's fine too. I know those kinds of lists elicit a variety of reactions from a variety of users.
Sent from my SM-G935V using XDA Labs
Click to expand...
Click to collapse
No prob! Glad I could help in a small way. I'll post the screenshot of what I have disabled to the main thread..... let the haters hate, it don't bother me ??
Sent from my Verizon S7 Edge (U firmware / rooted)
Md5s to check downloads please and thank you for posting this can't wait to try it out
Quick question
I already rooted us8ng adb
-So to flash U firmware
I use regular Odin for that
-Then is modded Odin for Eng g935x_qc_rooted_boot.tar. is that right?
- then adb and root.bat?
Sent from my SM-G935V using Tapatalk
TheWu-Wei said:
This is outstanding. Thank you so much!
I've yet to go through the whole process, as I want to set aside some time to prepare everything, etc. But I was wondering whether you'd be willing to share a list of the packages you froze or removed with Titanium. I am also a minimalist when it comes to what files I keep around on any device. If you'd prefer to share via PM, that's fine too. I know those kinds of lists elicit a variety of reactions from a variety of users.
Sent from my SM-G935V using XDA Labs
Click to expand...
Click to collapse
Screenshots are posted ?
Sent from my Verizon S7 Edge (U firmware / rooted)
[email protected] said:
Quick question
I already rooted us8ng adb
-So to flash U firmware
I use regular Odin for that
-Then is modded Odin for Eng g935x_qc_rooted_boot.tar. is that right?
- then adb and root.bat?
Sent from my SM-G935V using Tapatalk
Click to expand...
Click to collapse
Yea it actually does not matter that you are rooted. You are basically starting over from scratch by using ODIN to flash the U firmware. So start at the beginning and follow all the steps and you should be good!
Sent from my Verizon S7 Edge (U firmware / rooted)
dajmanjt said:
Yea it actually does not matter that you are rooted. You are basically starting over from scratch by using ODIN to flash the U firmware. So start at the beginning and follow all the steps and you should be good!
Sent from my Verizon S7 Edge (U firmware / rooted)
Click to expand...
Click to collapse
Okay thank you.
Sent from my SM-G935V using Tapatalk
Thanks so much for this!
What's your reasoning for leaving greenify aggressive doze off?
zachchen1996 said:
Thanks so much for this!
What's your reasoning for leaving greenify aggressive doze off?
Click to expand...
Click to collapse
No worries! I leave aggressive doze off because I use Force Doze to control doze instead. It does a much better job than Greenify at dozing quickly, as long as you use xposed to manage it. Force Doze screws up auto rotate and auto brightness bad if you don't use xposed settings in it.
Sent from my Verizon S7 Edge (U firmware / rooted)
spiderbolt said:
Md5s to check downloads please and thank you for posting this can't wait to try it out
Click to expand...
Click to collapse
I will post the md5 files when I get back to my house tonight. Also it appears that the ODIN files mediafire link is down. I will replace all links in my guide with files linked to my Dropbox to ensure they stay live and reliable.
Sent from my Verizon S7 Edge (U firmware / rooted)
Can someone repost the vzw files? It won't let me view them keeps taking me to file manager. Weird.
Sent from my SM-G935V using Tapatalk
---------- Post added at 02:31 AM ---------- Previous post was at 02:26 AM ----------
ykjae said:
Can someone repost the vzw files? It won't let me view them keeps taking me to file manager. Weird.
Sent from my SM-G935V using Tapatalk
Click to expand...
Click to collapse
Nevermind I got it thank you.
Sent from my SM-G935V using Tapatalk
ykjae said:
Can someone repost the vzw files? It won't let me view them keeps taking me to file manager. Weird.
Sent from my SM-G935V using Tapatalk
---------- Post added at 02:31 AM ---------- Previous post was at 02:26 AM ----------
Nevermind I got it thank you.
Sent from my SM-G935V using Tapatalk
Click to expand...
Click to collapse
Yea I'll repost all the files hosted from my own Dropbox when I get home, so that I know the files won't get deleted or moved. I don't like mega download anyways lol
Sent from my Verizon S7 Edge (U firmware / rooted)
dajmanjt said:
Yea I'll repost all the files hosted from my own Dropbox when I get home, so that I know the files won't get deleted or moved. I don't like mega download anyways lol
Click to expand...
Click to collapse
What's your battery life looking like?
spiderbolt said:
Md5s to check downloads please and thank you for posting this can't wait to try it out
Click to expand...
Click to collapse
ykjae said:
Can someone repost the vzw files? It won't let me view them keeps taking me to file manager. Weird.
Sent from my SM-G935V using Tapatalk
---------- Post added at 02:31 AM ---------- Previous post was at 02:26 AM ----------
Nevermind I got it thank you.
Sent from my SM-G935V using Tapatalk
Click to expand...
Click to collapse
All files (except the U firmware files) have been uploaded to my Dropbox and posted with md5 info. The U firmware has also been updated with md5 info. If the mediafire link ever goes down for the U firmware I will share a Dropbox link to that file as well.
2swizzle said:
What's your battery life looking like?
Click to expand...
Click to collapse
I am getting 5 to 6 hours screen on time with medium to heavy usage (navigation, maps, streaming music, YouTube, Tapatalk, internet browsing, etc)
Sent from my Verizon S7 Edge (U firmware / rooted)
Hi, I need help with one of the step to root the phone. So i was able to flash the .tar file on the phone using the custom Odin but I couldn't flash SU on the phone. Whenever I tried to run the root.bat file the cmd return this:
C:\adb\super>adb wait-for-device
'adb' is not recognized as an internal or external command, operable program or batch file.
Please help!
Thanks again for this. So, If I have the actual unlocked phone which already has the U firmware, I can skip a few steps and just root, do the cpu fixes, etc., right? The only thing I don't like about this phone is lack of voicemail notifications since the U firmware is stripped of that function.
Or is it better for me to perform all of the steps knowing I can flash the full U firmware to get back to the original state if I have to?

Redmi Note 5 Pro Stock Camera APK

Hi,
I was able to fetch APK file of Camera of Redmi Note 5 Pro, I was not rooted so I wasn't able to fetch library files and odex file.
But still I believe sharing is caring,
And some Devs might find it useful
I tried putting in system/priv-app/MiuiCamera, giving it permission rw-r-r, and after reboot it shows the app but force closes when tapped.
It won't be installed as normal APK ..
So just sharing it, it might help someone
Not Able to upload via XDA labs app, telling me network issue every time. So here is the,
Google Drive Link : https://drive.google.com/file/d/1v5bBrRnISL3x4ZdV5uqPzEQFiB5dUbL0/view?usp=drivesdk
Thanks
-The Tech Star
magicweapons said:
Hi,
I was able to fetch APK file of Camera of Redmi Note 5 Pro, I was not rooted so I wasn't able to fetch library files and odex file.
But still I believe sharing is caring,
And some Devs might find it useful
I tried putting in system/priv-app/MiuiCamera, giving it permission rw-r-r, and after reboot it shows the app but force closes when tapped.
It won't be installed as normal APK ..
So just sharing it, it might help someone
Not Able to upload via XDA labs app, telling me network issue every time. So here is the,
Google Drive Link : https://drive.google.com/file/d/1v5bBrRnISL3x4ZdV5uqPzEQFiB5dUbL0/view?usp=drivesdk
Thanks
-The Tech Star
Click to expand...
Click to collapse
Its never need to be rooted to get system dump . You can always fetch whole system partition through adb .check adb guides,so with any good file explorer ,there is nothing important available at data partition .so don't fool around here .
When you get handson of this device, Someone pls share the setup to replicate pixel/stock android system wide appearence without root.
Camlin3 said:
Its never need to be rooted to get system dump . You can always fetch whole system partition through adb .check adb guides,so with any good file explorer ,there is nothing important available at data partition .so don't fool around here .
Click to expand...
Click to collapse
Bro, Calm Down, Nobody is Fooling you here, I didn't had the device for a longer period of time, so in that little time I was able to fetch camera APK, why I did this? It's because its Version 2 of Miui Camera, older devices uses Version 1, and there is a lot of difference between them.
If the device would have been with me for much longer time I could fetch system dump through ADB or I could have rooted it and fetched everything, but as you know the device hasn't been sold yet, so what I did what I could have done.
Talking about fetching file with file explorer without root, Sorry it's not possible, Redmi Note 5 Pro uses Emulated partitions, so you can't just "SEE" root folders without root.
So keep Calm, and wait for the device to be sold and get it on hands to provide system files, in the little time, I did, what I could.
Thank you.
PS : I'm not Pro's like you guys, still I shared the camera APK having the Nooby Knowledge.
magicweapons said:
Bro, Calm Down, Nobody is Fooling you here, I didn't had the device for a longer period of time, so in that little time I was able to fetch camera APK, why I did this? It's because its Version 2 of Miui Camera, older devices uses Version 1, and there is a lot of difference between them.
If the device would have been with me for much longer time I could fetch system dump through ADB or I could have rooted it and fetched everything, but as you know the device hasn't been sold yet, so what I did what I could have done.
Talking about fetching file with file explorer without root, Sorry it's not possible, Redmi Note 5 Pro uses Emulated partitions, so you can't just "SEE" root folders without root.
So keep Calm, and wait for the device to be sold and get it on hands to provide system files, in the little time, I did, what I could.
Thank you.
PS : I'm not Pro's like you guys, still I shared the camera APK having the Nooby Knowledge.
Click to expand...
Click to collapse
Appreciate what u have done... Expecting more after u get the device:good:
Hey..im noob here can you tell me the procedure to extract camera apk from redmi note 5 pro.. i may get it in a day or 2.
Someone pls port this camera for other phones as well, as it has got portrait mode in front camera as well.
can we install this apk on lineage os and use portrait mode?
willi9070 said:
When you get handson of this device, Someone pls share the setup to replicate pixel/stock android system wide appearence without root.
Click to expand...
Click to collapse
I do have the device, if only you could guide me how to do the procedure.
iSirCasm said:
I do have the device, if only you could guide me how to do the procedure.
Click to expand...
Click to collapse
I don't know if they kept camera libs the same as the ones on old devices, but here's the list of the files needed (requires access to /system, so rooted device):
from /system/etc
the folder "device_features"
age_gender_bg
android_model_facea.dat
android_model_faceg.dat
face_goodly_***_***
face_ravishing_***_***
face_splendid_***_***
lf_facerank_model.bin
people_gender.dat
watermark_font_****_****.dat
from /system/priv-app
The folder "MiuiCamera"
If you (or anyone else) can, just try to pack them all together and upload them! That will be very helpful!
danypava said:
I don't know if they kept camera libs the same as the ones on old devices, but here's the list of the files needed (requires access to /system, so rooted device):
from /system/etc
the folder "device_features"
age_gender_bg
android_model_facea.dat
android_model_faceg.dat
face_goodly_***_***
face_ravishing_***_***
face_splendid_***_***
lf_facerank_model.bin
people_gender.dat
watermark_font_****_****.dat
from /system/priv-app
The folder "MiuiCamera"
If you (or anyone else) can, just try to pack them all together and upload them! That will be very helpful!
Click to expand...
Click to collapse
Sorry brother, but I have been unable to unlock the bootloader because of this stupid method to unlock BL by Xiaomi. All the Made in India variants are facing 86006 error because of which no one has been able to unlock and root, including me. Bugs have been raised and Xiaomi reported that their developers are working on it.
I hope someone with a rooted device reads this and tries to help.
Is it possible to port redmi note 5 pro's stock camera for other devices, like for redmi note 4?? as it got a good EIS and front portrait mode, will it work on mido??
App not installed on RR
rahulk096 said:
App not installed on RR
Click to expand...
Click to collapse
Same here. Though the app was installed but the camera goes black on opening. Thr camera UI is there but black screen. I'm on RR and could not get any other cameras working than Footej or the one included with my stock gapps
promiscuss said:
Same here. Though the app was installed but the camera goes black on opening. Thr camera UI is there but black screen. I'm on RR and could not get any other cameras working than Footej or the one included with my stock gapps
Click to expand...
Click to collapse
I m back on stock rom
rahulk096 said:
I m back on stock rom
Click to expand...
Click to collapse
On stock it will work like a charm after enabling Camera2API. Need to get this working on RR
not working in custom rom.
guys, is anyone rooted ?? if yes, please extract the required files so that this camera can be used in other phones too...
Goood
aneesh12 said:
guys, is anyone rooted ?? if yes, please extract the required files so that this camera can be used in other phones too...
Click to expand...
Click to collapse
My Phone is rooted, china/global ver
What file do you need? Maybe I can help

Categories

Resources