Hello guys,
A few weeks ago i bought a samsung s4 clone 1:1 copy.Last days ive been reading allot on the forums but as a noob i cant see the trees through the wood ...im stuck... i did manage to root my divice but only after trying 10 -20 times.I used mtk droid tools.
My question is if anyone can tell me if there are other roms for this Phone and what Phone did i buy.
I hope someone can help me out. thanks .
Most people figure out which phone they are buying *before* handing over any money. Good luck.
Sent from my SCH-I605 using Tapatalk
Maybe a photo of the phone's rear side (without cover and battery) could help.. usually there is some sort of model code printed somewhere that you can google for.. hope this helps.
Thanks guys.
Sublimize,dont get me wrong but i have an original Samsung S3 and S4 and both are still under warranty.I just wanted a cheap android Phone to play with I looked on the internet for a Phone and found this one as the best S4 1:1. I do have to admitt that i didnt know anything about the specs of this Phone except what the shop wrote about them. http://www.cheaptech.nl/samsung-galaxy-s4-kloon-clone-android-1-op-1. its a dutch site. I just opened the Phone to look for anything to reveal about this Phone and i took some pictures about the inside.
now with pics i hope
Not sure if it'll help, but seeing you're rooted, you can use your file explorer and go into the folder "proc" and copy your "config" file to your PC (or you can open it in the file explorer.
This is the config file they used when compiling your kernel. Now, if you look,you may get a clue to what hardware they compiled it for. Maybe.
Seeing it's a MediaTek cpu, you probably could have use the "framaroot.apk" method for root.
use quadrant standard
download app named 'quadrant standard' from Google playstore. although it's a benchmark related app but it will tell you about your phone in detail.
prafull07 said:
download app named 'quadrant standard' from Google playstore. although it's a benchmark related app but it will tell you about your phone in detail.
Click to expand...
Click to collapse
Naw, it's a clone, and quadrant will take info from the build.prop which of course is false also.
Moscow Desire said:
Naw, it's a clone, and quadrant will take info from the build.prop which of course is false also.
Click to expand...
Click to collapse
ooh!
Moscow Desire said:
Not sure if it'll help, but seeing you're rooted, you can use your file explorer and go into the folder "proc" and copy your "config" file to your PC (or you can open it in the file explorer.
This is the config file they used when compiling your kernel. Now, if you look,you may get a clue to what hardware they compiled it for. Maybe.
Seeing it's a MediaTek cpu, you probably could have use the "framaroot.apk" method for root.
Click to expand...
Click to collapse
Thanks for the replay. I did what you wrote but couldnt find in the proc folder any config file. So i just started opening and reading anything what could have some info,such as driver system cpuinfo and other folders. I found allot about Media Tec hardware parts inside the Phone and "CHMOD" to me that must be China mod if im not mistaken. I will continue reading and hope il find more info on t he Phone.The Phone works good but that isnt the reason why i bought it for Lets hope il find what i need or maybe someone else finds anything about it.
adamir said:
Thanks for the replay. I did what you wrote but couldnt find in the proc folder any config file. So i just started opening and reading anything what could have some info,such as driver system cpuinfo and other folders. I found allot about Media Tec hardware parts inside the Phone and "CHMOD" to me that must be China mod if im not mistaken. I will continue reading and hope il find more info on t he Phone.The Phone works good but that isnt the reason why i bought it for Lets hope il find what i need or maybe someone else finds anything about it.
Click to expand...
Click to collapse
Actually, CHMOD stands for "Change Mode". It is a shell command used most often to change file permissions.
As an example of how we would use this command/tool in a terminal:
Code:
chmod +x your_file.ext
Good attempt with "China Mod" though. I like that
wildstang83 said:
Actually, CHMOD stands for "Change Mode". It is a shell command used most often to change file permissions.
As an example of how we would use this command/tool in a terminal:
Code:
chmod +x your_file.ext
Good attempt with "China Mod" though. I like that
Click to expand...
Click to collapse
Well if you try to find anything usefull about Phone details and you stumble uppon allot files written in Chinese (as a noob that is your mind plays trikcs on you and you would love to learn chinese so you can read these files hoping to find details about the Phone that are hidden in this language Well,il keep trying in any way i can...and il post it here to help others and myself
i want a phone
Related
Hi,
Im starting a new Thread *intentionally* because in the Issues thread the Problems seems to be igonored, also there are many other issues beeing discussed.
So i hope we can find a Solution quicker using an extra Thread.
Problem: After Root my X10 is not showing Copy-protected apps in the Market.
How to recreate: Search for "documents" on a untouched X10, it will give you ~99 results. Then root it (new method) it will only give you ~52 results.
I already tried it on an untouched R2BA023, and i got 99 results so its clear that the problem lies within root and not with the Firmare itself.
I dont know if this helps but it has worked for me!
I copied the default.prop from system folder(not root folder) of my original firmware,and replaced the one from root,and waited a while.Now I have all bought apps back!Only fancy widget isnt there !
anyone tryed market-enabler ?
We have a discussion on Market Enabler.
Forum Link
collider said:
I dont know if this helps but it has worked for me!
I copied the default.prop from system folder(not root folder) of my original firmware,and replaced the one from root,and waited a while.Now I have all bought apps back!Only fancy widget isnt there !
Click to expand...
Click to collapse
Apparently fancy widget been stopped.. I think something to do with htc? correct me if im wrong.. cause I'm just saying what I think I read earlier.
Anyways I've made a backup of my own.. Hope it helps
http://db.tt/T6r8Hi
Sent from my X10i using XDA App
collider said:
I dont know if this helps but it has worked for me!
I copied the default.prop from system folder(not root folder) of my original firmware,and replaced the one from root,and waited a while.Now I have all bought apps back!Only fancy widget isnt there !
Click to expand...
Click to collapse
I will try this and report back, thanks
I have only the top 3 lines of the root default.prop not changed.the rest is from my original one.
Sent from my X10i using Tapatalk
It is a little strange with market!
We havent touched the prop files (execpt on X10a version) but even if i flash clean R2ba023 market dont work correctly.
Then i rerooted and tried much and found nothing.
And tada it works. -> what i've done .... noting. it suddenly worked.
It could be that there is a major firmware problem like before on R1...016 @ SE
Regards
Bin4ry
Yes.its strange!!The greatest Problem is the Copy Protection and the Variables they used for that.
Sent from my X10i using Tapatalk
I get a Permission denied (yes i mounted /system as RW)
Ok, managed it now (didnt do it as root)
Still, no copy protected apps -.-
BTW, overwriting build.prop ->Brick
I've got the same problem. Got some paid apps but not all (Sling Player I miss you).
Collider do you think you can post a little more detail about what you did to get it working again?
I have done nothing special,keep the top three lines from default.prop
The whole lower text was changed with the same content from the default.prop
of my first original firmware.
copy this new default.prop to sdcard and then write it with
adb shell
mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
dd if=/sdcard/default.prop of=/system/default.prop
My new default.prop for my Country.
Dont know if the cut is needed,maybe you can change the whole default.prop
Hope this helps you with your own default.prop in your Country.
Many props i know
ro.semc.version.cust=1235-7379
ro.semc.version.cust_revision=R7A
ro.product.name=X10_1235-7379
*******cut here***********
ro.semc.country=Switzerland
ro.semc.product.brand=Orange
ro.product.brand=SEMC
ro.product.device=SonyEricssonX10i
ro.product.manufacturer=Sony Ericsson
ro.semc.content.number=PA23
ro.product.model=X10i
ro.semc.ms_type_id=AAD-3880056-BV
ro.email.domain.0=orangemail.ch
ro.email.incoming-protocol.0=pop3
ro.email.incoming-server.0=pop.orangemail.ch
ro.email.incoming-port.0=110
ro.email.outgoing-server.0=smtp.orangemail.ch
ro.email.outgoing-port.0=25
ro.semc.message_max_size=307200
ro.product.locale.language=en
ro.product.locale.region=US
ro.mmi.standby-ringtone-volume=6
ro.semc.install_non_market_apps=true
ro.ciphering-indication=false
ro.config.ringtone=sony_ericsson.ogg
ro.config.notification_sound=notification.ogg
ro.homepage.url=http://wap.sonyericsson.com/download/download.do?cmd=owp&appl=sehome
ro.browser.bookmark.title.0=Sony Ericsson
ro.browser.bookmark.title.1=Sony Ericsson Support
ro.browser.bookmark.title.2=Games
ro.browser.bookmark.title.3=News
ro.browser.bookmark.title.4=Orange World
ro.browser.bookmark.title.5=Pictures
ro.browser.bookmark.title.6=Ringtones
ro.browser.bookmark.title.7=Sport
ro.browser.bookmark.title.8=Video
ro.browser.bookmark.url.0=http://wap.sonyericsson.com/download/download.do?cmd=owp&appl=sehome
ro.browser.bookmark.url.1=http://wap.sonyericsson.com/download/download.do?cmd=owp&appl=contactus
ro.browser.bookmark.url.2=http://mobile.orange.ch/games
ro.browser.bookmark.url.3=http://mobile.orange.ch/news
ro.browser.bookmark.url.4=http://mobile.orange.ch
ro.browser.bookmark.url.5=http://mobile.orange.ch/logo
ro.browser.bookmark.url.6=http://mobile.orange.ch/ringtones
ro.browser.bookmark.url.7=http://mobile.orange.ch/sport
ro.browser.bookmark.url.8=http://mobile.orange.ch/video
ro.home-screen=com.android.launcher
ro.drm.whitelist.domain.0=musiwave.com
ro.drm.whitelist.domain.1=orange.ch
ro.drm.whitelist.domain.2=orange.com
ro.drm.whitelist.domain.3=purplecast.us
ro.drm.whitelist.domain.4=viaccess.fr
ro.facebook.enable=true
ro.twitter.enable=true
ro.picasa.enable=true
ro.flickr.enable=false
ro.youtube.enable=true
ro.semc.hidden_pull_interval=168
ro.com.google.clientidbase=android-sonyericsson
ro.com.google.clientidbase.yt=android-sonyericsson
ro.com.google.clientidbase.am=android-sonyericsson
ro.com.google.clientidbase.vs=android-sonyericsson
ro.com.google.clientidbase.gmm=android-sonyericsson
ro.semc.emanual.url_semc=http://www.sonyericsson.com/cws/support/
ro.email.num=1
ro.semc.ecclist.num=0
ro.browser.bookmark.num=9
ro.drm.whitelist.num=5
ro.build.fingerprint=SEMC/X10_1234-4768/SonyEricssonX10i/es209ra:1.6/R1FA014/1267616029:user/rel-keys
Click to expand...
Click to collapse
Hi @collider,
When, where, how you have got that file in the previous or first release? I need the file for Vodafone Spain. I should reinstall a shipped firmware like 014 or 016 and then copy the file? or There is another way?
Thanks in advance
I think its because Google haven't yet authorised R2BA023
Sent from my X10i using XDA App
acampada said:
Hi @collider,
When, where, how you have got that file in the previous or first release? I need the file for Vodafone Spain. I should reinstall a shipped firmware like 014 or 016 and then copy the file? or There is another way?
Thanks in advance
Click to expand...
Click to collapse
i installed the original firmware(first release) i've saved before root and backuped default.prop with astro,then rooted again.
Lot of work but it helped.
Another way is you can get your own original firmware from davinci team i think.
I can not guarantee that it works for all.
I read somewhere on the Internet that ro.build.fingerprint is the Problem,no idea.
collider said:
i installed the original firmware(first release) i've saved before root and backuped default.prop with astro,then rooted again.
Lot of work but it helped.
Another way is you can get your own original firmware from davinci team i think.
I can not guarantee that it works for all.
I read somewhere on the Internet that ro.build.fingerprint is the Problem,no idea.
Click to expand...
Click to collapse
Thanks. I'll try to get the file.
No Joy for me so far
Google indicates to me that the important information there is the fingerprint, and that we also need to be concerned about the fingerprint in the build.prop.
My build.prop did not have a a fingerprint.
Tried one that I was able to find from another phone on my carrier but no luck.
One of my friends has an unrooted unmodded xperia x10a on the same carrier as me, I'm going to try and hit him up so I can download his build.prop and his default.prop and see what happens.
I don't know if this will help... I am having a similar issue... but I am NOT ROOTED.
I tried to root - OH, how I tried! - but I got stuck on step 2, with "device not found, device not found, choose option 6, press any key" and nothing happening on the phone.
So I used SEUS on my PC.
Oddly, the one with the SE PC Companion said "You are on the latest version".
But, the standalone update software updated me to R2BA020 (I was on R1FA16 before, O2 UK version, and I assume from the working step 1 I had got R1FA16 generic UK).
So. Essentially, I went from R1FA16 O2 UK -> R2BA020 generic from my half-arsed attempts to root. But, battery life WAY more than doubled, so I was quite happy.
Until I noticed several of my apps weren't on the store anymore... they were just... missing. Two I know of are Death Star Clock (I LOVED that) and MyPlayer (not too bothered, I managed to install Beebplayer).
I contacted a dev of the Death Star clock to ask if he'd taken it off, but he checked and all was still there. He told me to search for his dev name on the market - diggidy.net - and even that came back with nothing for me.
This is on an UNROOTED R2BA020 phone. So... I am hoping the solution will not require rooting. Or else I am in trouble, because I have given up after getting stuck on step 2 time after bloody time!
All I wanted, all I ever wanted, was to improve my battery life and remove stupid bloody useless Moxier apps!
Good luck with finding a solution... I hope my info might narrow down the cause in some way. My phone never got to the rooting stage so surely it can't be that?
Ungruntled said:
I don't know if this will help... I am having a similar issue... but I am NOT ROOTED.
I tried to root - OH, how I tried! - but I got stuck on step 2, with "device not found, device not found, choose option 6, press any key" and nothing happening on the phone.
So I used SEUS on my PC.
Oddly, the one with the SE PC Companion said "You are on the latest version".
But, the standalone update software updated me to R2BA020 (I was on R1FA16 before, O2 UK version, and I assume from the working step 1 I had got R1FA16 generic UK).
So. Essentially, I went from R1FA16 O2 UK -> R2BA020 generic from my half-arsed attempts to root. But, battery life WAY more than doubled, so I was quite happy.
Until I noticed several of my apps weren't on the store anymore... they were just... missing. Two I know of are Death Star Clock (I LOVED that) and MyPlayer (not too bothered, I managed to install Beebplayer).
I contacted a dev of the Death Star clock to ask if he'd taken it off, but he checked and all was still there. He told me to search for his dev name on the market - diggidy.net - and even that came back with nothing for me.
This is on an UNROOTED R2BA020 phone. So... I am hoping the solution will not require rooting. Or else I am in trouble, because I have given up after getting stuck on step 2 time after bloody time!
All I wanted, all I ever wanted, was to improve my battery life and remove stupid bloody useless Moxier apps!
Good luck with finding a solution... I hope my info might narrow down the cause in some way. My phone never got to the rooting stage so surely it can't be that?
Click to expand...
Click to collapse
i searched for 'deathstar' and 'death star' from my generic r2ba020 uk generic and got no results either so if i searched correctly its not an issue related to your phone specifically
I was just on the Google Code website and noticed there's a Nexus S ICS 4.0.4 download. After I downloaded a program that reads TGZ format, I saw there is 4 or 5 img files for the bootloader, system and so on.
My question is, if I copied the zip file as it was will this be recognized by the handset and install as expected or will it just screw things up. The reason I ask is, the previous versions I installed were not like this.
Also I noticed there is some Linux shell files which obviously aren't intended for Windows.
Any helpful feedback would be good and reassuring.
OK I think after a little investigation, it seems this only the hardware binaries and not the actual complete android system. Unless somebody can tell me otherwise.
A quick look through the general nexus s forum would tell you what u want to know.
Hmmm......
So in order to ask a question, I have to check whether somebody asked the same one on my behalf.
Granted but I did do a quick check and never seen nothing jumping out at me. So is there any need to be patronising? As it happens I answered my own question. Just because I have less than 10 posts doesn't automatically make me a numpty.
I was not patronizing.
Being that you noticed the page on google code and are here on xda its just frankly common sense to not search but just look at the general forum
I told you where to get the answers man. There is no logical reason to explain it when it was all explained already this weekend on the same forum.
Patronizing by directing you towards all the info you need. Can't make this up.
interpolate said:
I was just on the Google Code website and noticed there's a Nexus S ICS 4.0.4 download. After I downloaded a program that reads TGZ format, I saw there is 4 or 5 img files for the bootloader, system and so on.
My question is, if I copied the zip file as it was will this be recognized by the handset and install as expected or will it just screw things up. The reason I ask is, the previous versions I installed were not like this.
Also I noticed there is some Linux shell files which obviously aren't intended for Windows.
Any helpful feedback would be good and reassuring.
Click to expand...
Click to collapse
http://www.androidpolice.com/2012/0...ady-to-flash-appears-to-be-the-final-version/
Sent from my Nexus S 4G using XDA
Whether or not you were condescending to me or not isn't a concern of mine. Anyway I have the GSM model as I live in the UK. Just need to check near the end of the month I guess.
Just flash these files on bootloader (while phone is connected to PC and its driver is installed and adb is running in cmd)
Fastboot (--blah,blah.....)
Hmmm...
I need to reinstall of those files. As I recently formatted my main drive. Still have hundreds of things to reinstate.
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
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!!
Hi every one
just need to confirm from professional people here , i need to edit build.prop on my A9 device without rooting so that i could make some connection with my car screen (stupid screen accept only Samsung and LG) , Is that possible?
amro ibrahim said:
Hi every one
just need to confirm from professional people here , i need to edit build.prop on my A9 device without rooting so that i could make some connection with my car screen (stupid screen accept only Samsung and LG) , Is that possible?
Click to expand...
Click to collapse
First, this question gets asked A LOT so a simple search here or google will show numerous others asking this and their findings. It doesn't matter if its not specifically referring to HTC A9 or in this specific forum either.
That being said....to answer your question.....NO! ^_^ You will most likely need root to even access the system root folder where your build prop. You may find it using some app possibly that doesn't require root, open it and change values, HOWEVER, you will never be able to save these changes without root, sorry.
If you are knowledgeable on unpacking system images or have firmware.zip/tar etc that you can dig through and find the build prop, edit it on windows/linux/mac repack or rezip and flash it successfully....thats one way.
Another way would be to use ADB to pull what you want and push it back to system afterwards.....but not to sure as my phone(s) usually are rooted and never tried to use ADB unrooted. Somethings tells me that this too won't work but go for it.
mcbright80 said:
First, this question gets asked A LOT so a simple search here or google will show numerous others asking this and their findings. It doesn't matter if its not specifically referring to HTC A9 or in this specific forum either.
That being said....to answer your question.....NO! ^_^ You will most likely need root to even access the system root folder where your build prop. You may find it using some app possibly that doesn't require root, open it and change values, HOWEVER, you will never be able to save these changes without root, sorry.
If you are knowledgeable on unpacking system images or have firmware.zip/tar etc that you can dig through and find the build prop, edit it on windows/linux/mac repack or rezip and flash it successfully....thats one way.
Another way would be to use ADB to pull what you want and push it back to system afterwards.....but not to sure as my phone(s) usually are rooted and never tried to use ADB unrooted. Somethings tells me that this too won't work but go for it.
Click to expand...
Click to collapse
Actually i searched a LOT but i have found the TWO answers "Yes you can" AND "No you can not" , also people says yes you can giving steps i have no idea about it like this one
1. Make a process which executes "getprop" from the "/system/bin/getprop" directory and initialize the String which we want to get (ro.board.platform in example).
2. Make a BufferedReader which gets the value (String) by retrieving the data from a inputStreamReader().
3.Convert the BufferedReader to String.
. That is why i asked here again to get clear answer which i get it and many thanks for you
amro ibrahim said:
Actually i searched a LOT but i have found the TWO answers "Yes you can" AND "No you can not" , also people says yes you can giving steps i have no idea about it like this one
1. Make a process which executes "getprop" from the "/system/bin/getprop" directory and initialize the String which we want to get (ro.board.platform in example).
2. Make a BufferedReader which gets the value (String) by retrieving the data from a inputStreamReader().
3.Convert the BufferedReader to String.
. That is why i asked here again to get clear answer which i get it and many thanks for you
Click to expand...
Click to collapse
LOL i understand the frustration. I also spend a ridiculous amount of time scouring forums and any other place online for the many questions i need help with only to get fractured/incomplete answers or conflicting ones like you stated where it seems like the answer is both yes and no or whatever....its a real pain. Truthfully, I said you wouldn't be able to do this without root due to the level of difficulty of the other options trying without root. Creating bufferedreader etc is all Java Programming. You will need a decent working knowledge of java programming to be able to do what that guide was talking about.....i figured you might not have that so I said that NO to your question here. I know some of what that guide was explaining enough to create some of that they described but still not enough to feel comfy attempting. Your best option, i think, will be to extract the build prop from a stock.img and repack the system.img after editing the build.prop. Use 7zip to unzip/rezip the system.img and notepad++ to open/edit the build.prop and flash image in your recovery. You could also use Android Kitchen if you can. Plenty of tutorials on this. I linked two below for ya though. '
What were you looking to edit in the Build.prop anyhow? I assume you are disinclined to root/unlock bootloader for warranty issues correct?
BTW, sorry for such a late response...I am not always here for days at a time usually so.....
dsixda's Android Kitchen - http://forum.xda-developers.com/showthread.php?t=633246
Super-Rs - http://forum.xda-developers.com/chef-central/android/kitchen-superrs-kitchen-t3202296
mcbright80 said:
LOL i understand the frustration. I also spend a ridiculous amount of time scouring forums and any other place online for the many questions i need help with only to get fractured/incomplete answers or conflicting ones like you stated where it seems like the answer is both yes and no or whatever....its a real pain. Truthfully, I said you wouldn't be able to do this without root due to the level of difficulty of the other options trying without root. Creating bufferedreader etc is all Java Programming. You will need a decent working knowledge of java programming to be able to do what that guide was talking about.....i figured you might not have that so I said that NO to your question here. I know some of what that guide was explaining enough to create some of that they described but still not enough to feel comfy attempting. Your best option, i think, will be to extract the build prop from a stock.img and repack the system.img after editing the build.prop. Use 7zip to unzip/rezip the system.img and notepad++ to open/edit the build.prop and flash image in your recovery. You could also use Android Kitchen if you can. Plenty of tutorials on this. I linked two below for ya though. '
What were you looking to edit in the Build.prop anyhow? I assume you are disinclined to root/unlock bootloader for warranty issues correct?
BTW, sorry for such a late response...I am not always here for days at a time usually so.....
dsixda's Android Kitchen - http://forum.xda-developers.com/showthread.php?t=633246
Super-Rs - http://forum.xda-developers.com/chef-central/android/kitchen-superrs-kitchen-t3202296
Click to expand...
Click to collapse
Thanks again for your replay , actually i still trying to proceed your way .. i think i am too close to do it , but you know after one or two hour of Trying&searching i say to my self let us unlock this phone and finish this matter .. any way i am using the Android Kitchen and i hope i could do it