so i managed to soft brick an hdc note 3 clone , to my surprise the boot menu that came with it was upside down (you read that right) and while the option to factory reset it was there, no button gave the OK confirmation needed .
so next option was finding a suitable rom and doing the flash which came after hours of researching where needrom.com had few to test with and found drivers somewhere but would want to leave that as a final resort since this could brick it for good
now there was another option i came across yet need the assistance of an adb geek to help me with.
i originally bricked the device by copying build.prop to build.prop.bak in system folder then edited build.prop which lead it to soft brick, now the question, is there a way to use adb to access the device and delete old build.prop, then rename .bak one to build.prop?
please bare my noobness
night-mayor said:
so i managed to soft brick an hdc note 3 clone , to my surprise the boot menu that came with it was upside down (you read that right) and while the option to factory reset it was there, no button gave the OK confirmation needed .
so next option was finding a suitable rom and doing the flash which came after hours of researching where needrom.com had few to test with and found drivers somewhere but would want to leave that as a final resort since this could brick it for good
now there was another option i came across yet need the assistance of an adb geek to help me with.
i originally bricked the device by copying build.prop to build.prop.bak in system folder then edited build.prop which lead it to soft brick, now the question, is there a way to use adb to access the device and delete old build.prop, then rename .bak one to build.prop?
please bare my noobness
Click to expand...
Click to collapse
This forum is not about clones - there are other places on xda where there are threads specific to certain clones and you can ask there.
Actually, regardless of clone or not, this is a standard ADB question.
However, it's in the wrong forum, so I'll move it to the Android General. Some folks there should be able to help you.
MD
Moved....
Related
Hey xda. Sorry if this post has been misplaced, but I noticed there is no device forum for the tablet I am asking about today, and that is understandable. My girlfriend recently got an eMatic eGlide Pro II XL tablet for her birthday and it is running Android Ice Cream Sandwich 4.0.3. I noticed that it had a lot of bloatware and no google play store on it, and she wanted the play store, so I rooted the device for her and installed the play store and it works like a charm. The only problem I seem to have run into is this read only folder called "oem". The path for this partition is /oem/ and there are a few bloatware apps in there. For some reason though, I cannot edit or delete anything in that partition as it says it is read only even though i am using the root functions of ES File Explorer. I am able to modify other system apps though root explorer. I even tried using terminal emulator commands to remove the items but it still didn't work. Is there a way I can mount this folder as read/write? If I can, that would be a blessing, as I could delete the crapware that came with the tablet and the old version of YouTube that is buggy and not updateable thanks to being placed in the oem folder. Thanks for reading all this guys, I know it's a wall of text, haha.
Ematic: What is the browser?
What is the browser that is install from factory.. on Ematic devices ..as it is not "Chrome" [It almost looks like Dolphin], when I tried to do a regular .apk install of "Chrome" from the Google store it dies which almost tells me that it need to be pushed into the device. So am I correct that I need to find a downloadable .apk of "Chrome" for Android 4.0.3 ?
bfrench1990 said:
Hey xda. Sorry if this post has been misplaced, but I noticed there is no device forum for the tablet I am asking about today, and that is understandable. My girlfriend recently got an eMatic eGlide Pro II XL tablet for her birthday and it is running Android Ice Cream Sandwich 4.0.3. I noticed that it had a lot of bloatware and no google play store on it, and she wanted the play store, so I rooted the device for her and installed the play store and it works like a charm. The only problem I seem to have run into is this read only folder called "oem". The path for this partition is /oem/ and there are a few bloatware apps in there. For some reason though, I cannot edit or delete anything in that partition as it says it is read only even though i am using the root functions of ES File Explorer. I am able to modify other system apps though root explorer. I even tried using terminal emulator commands to remove the items but it still didn't work. Is there a way I can mount this folder as read/write? If I can, that would be a blessing, as I could delete the crapware that came with the tablet and the old version of YouTube that is buggy and not updateable thanks to being placed in the oem folder. Thanks for reading all this guys, I know it's a wall of text, haha.
Click to expand...
Click to collapse
How did you root the tablet? it seems there are several Ematic tablets being sold at wal-mart and I think people would like to know how you rooted it. (I know I would.)
fsuinnc said:
How did you root the tablet? it seems there are several Ematic tablets being sold at wal-mart and I think people would like to know how you rooted it. (I know I would.)
Click to expand...
Click to collapse
I used a tool called Root with Restore by Bin4ry. It took me a couple times. The first time I did it, all it managed to do was slow the tablet down, then i just performed a factory reset and tried again using the same process until it worked. It didn't take all that long. The hardest part is getting the adb drivers to recognize the tablet. I will attach my adb drivers so you don't have to go through all the rigamarole.
Navigate to wherever your android sdk folder is. Mine is at C:\Program Files (x86)\Android\android-sdk
Within the android-sdk folder, look for extras, then google, then usb_driver. Make a backup of everything in your usb_driver folder, just in case.
Next just extract the contents of the zip I attached to this post. Make sure USB debugging is on, and plug it in. It should be recognized assuming there isn't some other problem i haven't encountered or forgot to mention.
Once your computer recognizes the adb interface for your tablet, use the Root with Restore tool until it works.
bfrench1990 said:
I used a tool called Root with Restore by Bin4ry. It took me a couple times. The first time I did it, all it managed to do was slow the tablet down, then i just performed a factory reset and tried again using the same process until it worked. It didn't take all that long. The hardest part is getting the adb drivers to recognize the tablet. I will attach my adb drivers so you don't have to go through all the rigamarole.
Navigate to wherever your android sdk folder is. Mine is at C:\Program Files (x86)\Android\android-sdk
Within the android-sdk folder, look for extras, then google, then usb_driver. Make a backup of everything in your usb_driver folder, just in case.
Next just extract the contents of the zip I attached to this post. Make sure USB debugging is on, and plug it in. It should be recognized assuming there isn't some other problem i haven't encountered or forgot to mention.
Once your computer recognizes the adb interface for your tablet, use the Root with Restore tool until it works.
Click to expand...
Click to collapse
Thanks, that's great info. I will try it out. (I have a Ematic egs005 7" on it's way to me. they seem to be very cheap right now at under $60)
fsuinnc said:
Thanks, that's great info. I will try it out. (I have a Ematic egs005 7" on it's way to me. they seem to be very cheap right now at under $60)
Click to expand...
Click to collapse
I'll bet that you can get it rooted. You may have to edit those drivers though since I don't think my girlfriend's tablet isn't the same as the one you mentioned.
If the drivers I posted don't work for you, then open up "android_winusb.inf" from that zip file in your favorite text editor.
Somewhere under the "[Google.NTx86]" and "[Google.NTamd64]" sections, add this:
;eMatic egs005
Remember where you put those, cause what goes under those entries is the hardware ID of your tablet. You can get that by going under device manager and right clicking on your tablet, if it is unrecognized it should have a yellow triangle on it or something like that. Go to properties and go to the details tab, then from the drop down menu, select hardware IDs. In my case, two came up. Just pick one. If that one ends up not working later, use the one you didn't try.
Now, your entries should look like this:
;eMatic egs005
%CompositeAdbInterface% = USB_Install, (your hardware ID)
Next, try to update the drivers on your tablet via device manager. Right click on your tablet like we did last time, and click properties. Go to the driver tab, and hit the update driver button. You'll have to manually navigate to where your drivers are. Select the folder where you extracted the zip to (make sure you have the edited file in there!) and follow the procedure to update the driver.
Next, open up an adb window and type in adb devices. If you have something showing up, congrats! You should be able to try the root tool now. As always, be careful!
eglide pro ll xl
I just bought the eglide pro ll xl also. From what I have read and done to my tab so far, it is already rooted from the factory. It sounds like a lot of the ematic tabs are. I've been researching different operating systems to put on my tab but there isn't anything that says it is specifically for mine. They pretty much just list the types of tablets the ROMS will work for. The question I have is what type of tablet is this. Allwinner a10? LY F1? TREQ? I would really like to know this and a good way to back up my current system so if I screw it up I can go back and try again.
-Z
Livinbad said:
I just bought the eglide pro ll xl also. From what I have read and done to my tab so far, it is already rooted from the factory. It sounds like a lot of the ematic tabs are. I've been researching different operating systems to put on my tab but there isn't anything that says it is specifically for mine. They pretty much just list the types of tablets the ROMS will work for. The question I have is what type of tablet is this. Allwinner a10? LY F1? TREQ? I would really like to know this and a good way to back up my current system so if I screw it up I can go back and try again.
-Z
Click to expand...
Click to collapse
I didn't add most of those entries in the drivers file, it originated as a sort of "fix all" driver that was posted on xda to connect many many types of different devices to adb without hassle. I added a few of the entries using the hardware ID method I described above to accommodate some less popular devices that my friends and family asked me to root.
I think I heard talk somewhere about custom roms for the eGlide, but I have no clue how to flash them, and seeing as how that tablet wasn't mine, I did not want to try to flash one and brick it, lol. I couldn't find any recoveries or any other tool to flash things to it. If you do find a way, all I can say is be careful.
As far as backing up goes, root with restore supports unrooting as well. I never performed that function though, since root hasn't done anything bad for the tablets I put them on, haha. I'm not certain there is an easy backup method since as I said a second ago, no custom recoveries. To be safe, I would recommend a factory data reset before attempting any rooting/unrooting of this tablet.
I hope I helped with my feedback.
bfrench1990 said:
I didn't add most of those entries in the drivers file, it originated as a sort of "fix all" driver that was posted on xda to connect many many types of different devices to adb without hassle. I added a few of the entries using the hardware ID method I described above to accommodate some less popular devices that my friends and family asked me to root.
I think I heard talk somewhere about custom roms for the eGlide, but I have no clue how to flash them, and seeing as how that tablet wasn't mine, I did not want to try to flash one and brick it, lol. I couldn't find any recoveries or any other tool to flash things to it. If you do find a way, all I can say is be careful.
As far as backing up goes, root with restore supports unrooting as well. I never performed that function though, since root hasn't done anything bad for the tablets I put them on, haha. I'm not certain there is an easy backup method since as I said a second ago, no custom recoveries. To be safe, I would recommend a factory data reset before attempting any rooting/unrooting of this tablet.
I hope I helped with my feedback.
Click to expand...
Click to collapse
I actually installed CWM 6.0.1.2 by Flowish on to my tab and it works great except for the process he has to get in to the recovery. I have to use the terminal emulator to launch it. That's why I am leery about installing a different ROM. If I can't get the thing to boot up properly I then can't get to the terminal emulator to get to recovery to restore my backup. I'm still searching and learning though. I'll figure it out eventually.
Livinbad said:
I actually installed CWM 6.0.1.2 by Flowish on to my tab and it works great except for the process he has to get in to the recovery. I have to use the terminal emulator to launch it. That's why I am leery about installing a different ROM. If I can't get the thing to boot up properly I then can't get to the terminal emulator to get to recovery to restore my backup. I'm still searching and learning though. I'll figure it out eventually.
Click to expand...
Click to collapse
Check if there's fastboot for this tablet. There's a fastboot command to boot into the recovery. If not, then I would just not flash a Rom
Hi everyone. Long-time reader, first time poster here.
Well, I've gotten myself in a bit of a jam. My Relay is rooted and has CWM 6.0.1.2 running the stock ROM per one of the awesome devs working on this phone. In a bout of zeal, I found a guide for installing Google Wallet on unsupported devices that involved editing the build.prop file to have the device identify itself as another. I dove in head first... My first mistake was not doing a CWM backup and my second mistake was that I backed up the build.prop file to the internal memory rather than the external SD card (seems pretty inaccessible there). After rebooting, the device black-screened after the Relay 4G splash and can only be brought back up by pulling the battery, though it still gets stuck at startup.
I had a look around and found these very similar threads, but they are for the S3:
http://forum.xda-developers.com/showthread.php?t=1895631
http://forum.xda-developers.com/showthread.php?t=1830191
I can also get into CWM and Odin mode, but Odin3 and adb don't see the device for some reason and CWM doesn't appear useful without a backup. From what I've gathered, the easiest way to recover from this is a flashable zip with the stock build.prop file.
Would anyone be able to make one of those or otherwise bail me out? Any help would be greatly appreciated!
Edit: If it helps any, I used ES File Explorer to do this, which apparently doesn't do permissions quite right. I'm not sure if it affects this, but I figured I'd throw it in here anyway.
Bumping in desperation here! Can anyone just paste in their build.prop? I'm on UVLJ1 (haven't had time to do the latest update due to root).
hmm... you should be able to go into download mode and flash the stock rom to recover the phone i think?
I think this is the answer. Flashing stock will give you what you need, it can be done through CWM (gee one's flashable zip for instance).
Wipe system/data through the format menu.
I wish I knew what a build.prop was.
installed it and rebooted my Samsung Relay and the screen went black. I pressed the power button and nothing happened.
The phone is now officially a paperweight. Also I had root privileges.
Can you help me please, I do not know what to do?:crying:
tacoman3148 said:
Hi everyone. Long-time reader, first time poster here.
Well, I've gotten myself in a bit of a jam. My Relay is rooted and has CWM 6.0.1.2 running the stock ROM per one of the awesome devs working on this phone. In a bout of zeal, I found a guide for installing Google Wallet on unsupported devices that involved editing the build.prop file to have the device identify itself as another. I dove in head first... My first mistake was not doing a CWM backup and my second mistake was that I backed up the build.prop file to the internal memory rather than the external SD card (seems pretty inaccessible there). After rebooting, the device black-screened after the Relay 4G splash and can only be brought back up by pulling the battery, though it still gets stuck at startup.
I had a look around and found these very similar threads, but they are for the S3:
http://forum.xda-developers.com/showthread.php?t=1895631
http://forum.xda-developers.com/showthread.php?t=1830191
I can also get into CWM and Odin mode, but Odin3 and adb don't see the device for some reason and CWM doesn't appear useful without a backup. From what I've gathered, the easiest way to recover from this is a flashable zip with the stock build.prop file.
Would anyone be able to make one of those or otherwise bail me out? Any help would be greatly appreciated!
Edit: If it helps any, I used ES File Explorer to do this, which apparently doesn't do permissions quite right. I'm not sure if it affects this, but I figured I'd throw it in here anyway.
Click to expand...
Click to collapse
I'm not very good at this also,but...Can you connect your phone to your computer and mount your phone from cwm and get the build.prop file that way?Or maybe do a factory reset?
Hello,
I'm Using a Rooted Starmobile Up has an MediaTek MT6582M
well, it started when i was changing the bootanimation of my phone with an marvelboot.zip using ES File Explorer, i forgot to set the permissions so after i restart it, my phone stucked at boot animation.
i copied the marvelboot.zip at the /Device > system > media folder as far as i can remember.
i think it will be solved if i am able to delete the bootanimation.zip from that media folder using computer or something else.
i am wondering how can i delete that file from the system folder, or perhaps change permission? and is there a way to browse the system folder from android to computer?? i just wonder if theres such, but i will go with your answers.
i have no CWM installed and i dont know how, i dont know ADB, or SDK and all
when i tried installing CWM from recovery menu, it says installation aborted and thats my only way.
can someone help me?
another thing is i forgot to backup the firmware, and ofcourse warranty is voided as it is rooted, i cannot get it's firmware anywhere.
thanks again
I need your help, thank you.
OK so you can post your question here: http://forum.xda-developers.com/showthread.php?t=2257421&page=1
However, I urge you to keep searching for the stock firmware. This is a rare device that has practically no support.
If you had adb support which is highly unlikely you could use the command "adb push bootanimation.zip/system/media"
But I very much doubt you will be able to get adb to communicate.
I wish you all the best in searching, but I think you may have just learned a very costly lesson on always having a backup before tinkering.
Good luck
hello, hmm what if i buy a new unit of this model? lets say another starmobile up, and i backup its firmware, is it possible to do that?
and is it possible to copy the back up on this device?
whateverwhenever said:
hello, hmm what if i buy a new unit of this model? lets say another starmobile up, and i backup its firmware, is it possible to do that?
and is it possible to copy the back up on this device?
Click to expand...
Click to collapse
I honestly don't think it would work. You really need a custom recovery or a way to access your bootlooping phone's system.
You can check this thread out on adb http://forum.xda-developers.com/showthread.php?t=2588979
If you're successful in getting adb to work you may have a shot at fixing it. But the odds are against you.
This is why we are all encouraged to read and be careful.
A while back i decided to downgrade my stock 4.3 to 4.1.1 in order to try to unlock it from carrier... the thing is i lost my IMEI and Serial Number
The good news is i have a backup of my EFS folder (only copy-paste with "root explorer" app though... no ".img" file sadly), but I understood that the most important file is "nv_data.bin"
So... my problem seems to be like this: http://forum.xda-developers.com/galaxy-s3/help/successful-imei-repair-i9300-backup-t2544109
but only the last step (put back the nv_data.bin, delete backups of bad nv_data.bin, reboot and magic)
The sad part: it doesn't resolve anything because everytime I reboot the phone it recreates the "nv_data.bin" even if I restore the original one (the one i had before downgrading)
Can anyone help me please :angel: ?
I have also tried as seen in other posts to change it's owner into radio:1001, unfortunately it still recreates the file after reboot.
I am currently trying to go back on 4.3 to try to restore the nv_data.bin on that verison (but i don't think it has anything to do with the android version)
Anyone encountered this problem or knows a solution ? Thank you !
Hi,
I see you've already asked about this in the appropriate section for your device. Xda Assist is here to help navigate the site, not for support.... And you found your way already. ?
Thread closed.
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!!