Hey,
the title is a little confusing but I'll help you understand it. What I would want is to perform all three operations, or only root and debloating, if possible or only debloating. I have a Samsung Smart TV with model UA43NU7470 (Samsung 7 Series, it is what it's called) and I searched SamyGO for the forum for it's specific series, but in vain. Back to the main point: Has anyone tried to root this device or tried modifying it or does anyone have the link, to which I could use to debloat the OS? This specific series runs on Tizen OS, so nno worries.
Hope you have a good day
Mr. Noob.
Use this repo:https://github.com/AnantMishra01/UIBloatwareRegistry
Unfortunately it requires ADB and USB debugging and I have no idea on how to navigate it on the TV. Can you please explain with some more steps?
Related
anybody knows how to make a ROM customized and make a "update.img" to run on a un-rootable device? I know when you backup a linux image for example ubuntu, this image will run on all other PCs, the image will automatically knows the new PC's drivers and adapt everything with that, is it what happening to an android too ?
It's not clear what exactly you mean by "un-rootable" device, but one cause an Android device cannot be rooted is that it requires signed updates. This signing happens using a special private key, which only device manufacturer knows. So, answering your question, if a device is truly un-rootable, it's likely impossible to make install custom update.img (because otherwise you could just include superuser binary in that custom image, and it wouldn't be unrootable in first place ;-) ).
---------- Post added at 03:20 PM ---------- Previous post was at 03:12 PM ----------
Answering second question, no, it's not the same for Android. Most Android device use ARM processor, and in ARM world you usually need to know addresses and other characteristics of every peripheral device (RAM, display, camera, etc.) to make it work, and those are different for different devices. So, full system image made for one device most likely won't work for another device (unless they're very similar).
But there're also those "partial updates", which doesn't have complete system image, but only some components, e.g. a theme or some application. Such partial updated might be possible to install on different devices. (But if such update comes from a vendor, it is usually locked for a particular device anyway).
let me make it clear, I have a MSI tablet, I tried all rooting ways like z4, Gingerbreak v1.20 and superoneclick nothing's working for it (so it's un-rootable at least because of I couldn't find any way for that!) .
I found an official "update.img" from msi website, i upgraded the ROM to the new version, it was when i found we can make root access by editing of the "update.img".
Well, "a MSI tablet" still doesn't sound too specific ;-). I guess, you might have more specific responses if you'd write the exact model name you have (did you also try to search forum for it?).
As an example, I can tell about Nook Tablet - its boot loader is exactly locked, requiring signed updates. But folks here at XDA devels still found a hole in it and described how to get root on it and how to install custom updates for it (and are working on CyanogenMod for it). I personally bought Nook because I knew there's a great, active community behind it, so there would be custom hacks and updates for it.
"MSI Windpad Enjoy 10" it's the exact model name. unfortunately this one is not a famous model and there's no useful information for this device
Goldiecalypso,
I do not know if it will work for you.
I have an Aishuo A816 which I could not get rooted, what I did was find a ROM that was pre rooted and forced an upgrade with that. Everthing is now fine and if I change rom I can now root with superoneclick.
Keith
we are also discussing on this matter:
http://forum.xda-developers.com/showthread.php?t=1453613
we have the official ROM, but nobody's here to make it rooted.
try to rooting msi enjoy windpad
hi goldiecalypso
can you to try learning how to rooting ?and rooting the msi windpad,together?
(excuse me for my bad English)
I want to, but I have no idea how to start!
Hi,
I wonder if someone can help.
I have a Pioneer Dreambook, i dont know the model number. It is similar in appearance to the Dreambook F10 but has different specs and hard buttons.
If you need the specs i can give them to you, but it currently runs windows 7.
I have been able install android on to it using andoid - x86, and tried multiple versions of the x86s, but all seem to unstable, the OS doen't control the hardware buttons correctly and doesn't rotate the screen unless an app forces it to rotate. Also I cannot put the tablet into "sleep" mode, only use a software option to turn the device off.
Once the device is off it is virtually impossible to restart the device and load android without using the x86 debugger.
I have seen on the web that devices like the hp tablet running web os is possible it install android effectively and that it is possible to install android onto a windows device, but surely there must be a better solution than what i currently have.
I tried to install Cyanogen but the windows installer wouldn't detect the tablet, presumably because it is not a support device, but i did read that it is possible to install Cyanogen on an non supported device.
If there is anymore information i can give please let me know, and any help or advice you can give me would be greatly appreciated.
Thanks,
Sam
Hi guys,
After reading very helpful post about how to write good posts/questions I realise that my issue maybe too specific.
I understand that with android the os needs to have some sort of tailoring to different devices.
But there are examples out there of similar applications of android on non android devices.
As I said earlier I already have installed android using android x86.
Let me then rephrase my question...
The issues described earlier, are they a result of the x86 method of installing android or are they the device simply incompatible with android (which I find hard to believe)?
Thank you to all the people who took the time to read my post and once again, any help would be invaluable.
Thanks,
Sam
Sent from my HTC_0P6B6 using XDA Free mobile app
Hello friends!
I have a Chinese BML One mini phone (I know it's crappy, but I had no choice), and I'm trying to start an android development with it.
I was aware that it might be hard to find any drivers for that phone, so I decided to use linux (opensuse 13.1) as a development machine (hopefully it requires no extra drivers).
The problem is that device seems to be invisible for the eclipse.
When I do in eclipse "run as - android application" - it says that there is no suitable device found and suggests to create a virtual one.
Usb debugging is on. Phone keyboard is unlocked.
The project is created to run on android 2.2. (The phone says that it is 4, but while digging here on the forum I found that it is really 2.3.5)
Is there any special way of connecting that phone to the PC? Hold secret combination of buttons maybe?
(As far as I know galaxy nexus for example is also invisible for eclipse when you connect it as a flash drive, so you have to connect it as camera.)
The problem is even worse as my laptop is too weak for the development on emulator, so that mobile was the only chance to start android development.
I would be grateful for any answers and links.
Thank you.
Hej hej! Please share any thoughts why it could be? Any suggestion of what to try? Does anyone experienced any device recognition problems with Chinese mobiles on any OS? Is there something special with connection MocorDroid to PC?
What would you try?
Please give me at least a direction to dig.
Thanks
The main issue is that it's not an official Android version and the fact that they modded it to read the wrong Android version there is almost nothing you can do. Mix in the fact that there IS no kernel source code there will not be much you can do at all with development for that device.
Hello, thank you for the answer. You inspired me to search in Chinese internet using google translate, and that is what I've found:
One need to find the vendor and device id using lsusb command
Bus 001 Device 002: ID 1782:5d04 Spreadtrum Communications Inc
These 1782:5d04 is actually a device and vendor id.
Then we need to write it to /etc/udev/rules.d/51-android.rules file in that way:
SUBSYSTEM=="usb",ATTRS{idVendor}=="1782",ATTRS{idProduct}=="5d04",MODE="0666"
And also add "0x1782" without quotes to /home/XXX/.android/adb_usb.ini file.
If you don't have any of these files, create it. Note that 51-android.rules should have 644 permissions.
Than I googled for "0x1782" and found these two links, so I think that problem is not only chinese-fake-android-specific:
stackoverflow. com/questions/9210152/set-up-device-for-development-no-permissions
sudotask. wordpress.com/2013/10/30/how-to-adb-on-open-suse
It could be also problem with permissions like described here:
stackoverflow. com/questions/6484279/detecting-device-for-debugging-adb-does-not-work
So, now I able to use my mobile for Android development! Wait for more garbage in play market!
Thank you!
Q&A for Intel Android Devices Root / Temp CWM Session
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for Intel Android Devices Root / Temp CWM Session. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Will this root method work with ASUS devices?
The thread title (Intel Android Devices Root / Temp CWM Session) suggests this is a generic rooting method for tablets with Intel SoCs. Is there any reason why this shouldn't work with the newer Intel Atom-based Asus tablets such as the MeMO Pad ME176CX? The current and as far as I know, only rooting method, for the ME176X uses an app called RootZenPhone.
RootZenPhone appears to use the same exploit as your script-based root method, but wraps it up in a APK with obfuscated asset names. (Note: I ran clamscan on both the APK and your files, and both tested positive for the exploit). I prefer your method because it has a cleaner, more opensource design. I can basically read what it's going to do, at least up to the point where you run the exploit.
usenametaken said:
The thread title (Intel Android Devices Root / Temp CWM Session) suggests this is a generic rooting method for tablets with Intel SoCs. Is there any reason why this shouldn't work with the newer Intel Atom-based Asus tablets such as the MeMO Pad ME176CX? The current and as far as I know, only rooting method, for the ME176X uses an app called RootZenPhone.
RootZenPhone appears to use the same exploit as your script-based root method, but wraps it up in a APK with obfuscated asset names. (Note: I ran clamscan on both the APK and your files, and both tested positive for the exploit). I prefer your method because it has a cleaner, more opensource design. I can basically read what it's going to do, at least up to the point where you run the exploit.
Click to expand...
Click to collapse
It should work I've tested it on Medfield, Clovertrail, and Baytrail devices, from the Asus fastboot.imgs I've looked at trigger 2 and 3 should work.
the apk you refer to i believe actually uses a function Asus only seems to of built into thier droidboot binary on the Asus when you start droidboot it looks at /factory for a file called .addon and then triggers it Asus uses it for automating things under droidboot I believe and several recoverys have been built to take advantage of it.
As for the exploit the exploit is the the script the binarys are nothing really special just responsible for setting up and starting the recovery session. recovery.trigger is a simple daemon to launch recovery.launcher and recovery.launcher is basically a small subset of cwm recovery its self.
Sent from my XT907 using XDA Free mobile app
Hi,
this worked on an odys intellitab 7, now i got finnaly root . BIG THX!
Btw I trird trigger 2 and 3 and both worked for me
How can i see if the bootloader is locked on my device?
Another possible device
Hello,
in Czech forum where I compiled a native-language short guide how to use your tethered CWM recovery to root Op3n Dott (I see that somebody confirmed that both T2 and T3 triggers work] one Slovak user reported that he was able to use the tool to root Prestigio MultiPad Thunder 7.0i http://www.prestigio.sk/catalogue/M...NDER_7.0i#/product-specs?article=PMT3377_WI_C. I sent him a question concerning which trigger did he use so if he replies I will send more info. Sorry for the Q&A thread, but I got kicked here because of the low post count.
Succesfully rooted Tesla L7 Tablet
Using the method described successfully rooted Tesla L7 tablet. The method used is T3 and supersu used is UPDATE-SuperSU-v2.40
Is the recovery built from source?
Hello, one more question - is the recovery built from source by you, or is it a ready-made recovery from someone else? Because if you have your own tree an are building it from scratch, it might be possible to include the call of my tool used for dumping images (dump_images from merrifield_bin of dell-venue-boot-tools for signed images and possibly a renamed one from zte_gxi_boot_tools for unsigned images) to /sbin/nandroid-md5.sh script and add the tool(s) to /sbin. I know it is not the best solution but at least it would be possible to backup the images if not restore them from CWM.
pm-cz said:
Hello, one more question - is the recovery built from source by you, or is it a ready-made recovery from someone else? Because if you have your own tree an are building it from scratch, it might be possible to include the call of my tool used for dumping images (dump_images from merrifield_bin of dell-venue-boot-tools for signed images and possibly a renamed one from zte_gxi_boot_tools for unsigned images) to /sbin/nandroid-md5.sh script and add the tool(s) to /sbin. I know it is not the best solution but at least it would be possible to backup the images if not restore them from CWM.
Click to expand...
Click to collapse
The actual recovery is built by @vampirefo but i am very interested in adding that feature in and was actually going to ask you about that.
Also have you looked at any of the older update_osip source?
Can you please tell me an easier to understand method.
Because even though i understand what you're talking about, i don't know where to put the files. I understand flashing the session and all but coukd you pleeease explain how to root. Because this the first time i'm rooting a device
Thanks
rooting without voiding warranty
Can you please tell me how to root my dwll venue 8 3830 without voiding the warranty?
Yay, i rooted my tab Dell Venue 7340!
But when i'd like to install some optimization script like: http://forum.xda-developers.com/android/software-hacking/mod-projct-mod-boost-nitro-x-edition-t2809443 recovery (cwm) said error 255... there is any chance to install this?
Getting Windows 7/8 to Recognize Dell Venue 3740
Fajfie said:
Yay, i rooted my tab Dell Venue 7340!
But when i'd like to install some optimization script like: http://forum.xda-developers.com/and...mod-projct-mod-boost-nitro-x-edition-t2809443 recovery (cwm) said error 255... there is any chance to install this?
Click to expand...
Click to collapse
Thanks to Social Design Concepts for the great work. It is appreciated!
Fajfie, thanks for posting. That's awesome. If you used Windows, how did you get Device Manager to identify the Dell Venue 3740? I've downloaded all recommended driver files in this and the previous thread and I can't get Windows to identify the device. When I run launcher.bat I get DEVICE: UNKNOWN.
Any ideas?
Another rooted
Great work, this worked to gain root on Medion (Lenovo) Lifetab S10346 tablet.
Intel Z3735F cpu
2GB ram, 32 GB storage.
I used trigger T3 and it went through smoothly, a Great bit of work.
Works perfectly on the Asus Padfone X Mini. I referenced this thread over in the device specific forum. I used the T3 command in step 3.
Thanks!!!
Worked on my ASUS Padfone X mini (TOOS) used T3 option.
Thanks!
Thanks you. The procedure works with method 3 to GoClever Insignia 700 PRO , Android 4.4.2.
I just installed IntelAndroidDrvSetup 1.5.0 with the drivers for my pc.
hi im having the same problem as GeeKerGurL
" Try to manually boot to droidboot
Anyways... everything was going ok, I selected trigger 3 to try first, reboots to droidboot (with "waiting for fastboot command") then I select recovery and get android dude laying down with a red exclamation point coming out his belly and it just said "no command" now I am soft bricked, only getting the USB symbal with the white line under it. Please help! "
i have a Acer Iconia A1830
Problems with the update surpeuser zip
I followed your guide to rooting Acer iconia tab 8 A1-840FHD with intel chip, (Wich is great by the way thanks) and evrything goes to plan until, i get to Install Zip. I get, E:Can't mount /sdcard/ Update-superSu-v2.40(1).zip Installation aborted. I've downloaded the zip from your link by desk top (windows 7) and transferred it over. Also downloaded from the tablet and just used a file manager to move it over to sd. Same msg for each. I used the T3 option. any ideas how to get the zip to install?
Zip copy to folder on your tablet (download,...) and install from recovery install. zip.
Send from my Samsung Galaxy S2 - RR Lollipop v. 5.2.7
Verified with Acer Iconia A1-830
Firstly, big thanks to the dev, social-design-concepts for making this thing work on Intel device. Thumb up~
It works wonders with my Acer Iconia A1-830 android 4.4.2.
I used option T1 and it works without any problem.
Thanks again.
P/s: Hope this will work on the latest Intel devices like Asus Zenfone 2 ;p
Hello Droids
I have a strainge special problem Im working on for several weeks. I bougth the 64GB version of the S6 Edge after a few days with the plan to cut just 40GB as a bootable USB storage using DriveDroid or something similar.
Now Im not able to get my device G925FXXU2COH2 with Android 5.1.1 rooted (or am not willing to for loosing KNOX waranty) so I thought about several possibilities to not just get the device rooted in general but simply give the App (DriveDroid or something else) enougth rights to modify the USB channel.
Is it possible in any way to give the App that rights?
Would it help just to move it into System directory in any way?
Could i just go into recovery mode and pl,ace it there while in ADB shell?
Would it especialy possible to place it anyway into the recovery partition and then tell the phone to make a factory reset?
Could that for example be done using the service menu build into the Samsung Galaxy?
Im a developer with more or less good knowledge of working an Android and while developing I often need to stay at someone elses PC (company, presentation at customer and so on) so I thought if it would be nice to cary a bootable version of Ubuntu at my phone as my working environment. Thats all, no more no less
I would be very happy if someone could solve this for me
Best Regards