Related
So there are two populair methods of rooting the galaxy s3:
- The Samsung galaxy s3 toolkit
- Chainfire's CF-ROOT
My questions are as follows:
What are the technical differences between the two rooting methods?
Do the methods have any drawbacks? (cf-root for example is incompatible with rommanager)
disclaimer:
I am not interested in what you think is the best method, I want to know the technical differences between the two methods used.
I know that the toolkit itself is not a rooting method, it does however include 4 different methods you can use, I am referring to those.
The toolkit uses cfroot I think. Not sure if it's as up to date as the latest cfroot via Odin. They both work well enough. There is no other method I know of. And I haven't had any drawbacks.
That's all I can say really
Sent from my GT-I9300 using xda premium
Also The toolkit uses Odin too. It has other options and clear instructions. Drivers. Modems etc so this would be the best option for an casual user.
Latest cfroot via Odin is probably your best option if u know what your doing
But it's up to you mate, it doesn't really need analyzing so deeply...
Sent from my GT-I9300 using xda premium
slking1989 said:
But it's up to you mate, it doesn't really need analyzing so deeply...
Click to expand...
Click to collapse
Well it is personal but I like to know or at least have a general idea of what I am doing to my phone. So yes it does
Tnx for the reply
Anyone else who can give me some more insight?
Unfortunately I don't have an answer for you, but I also am interested in the answer to your question..
I think certain methods of rooting use SuperSU (is this the CF one?) and then another method uses Superuser. I think both install busybox (that seems to be the same?)
In my experience, using the Superuser.apk app was faster than SuperSU..
I don't even have the Busybox app installed (but I am sure my phone has busybox, so this also confuses me??)
CF root gets the job done in 20-25 seconds. It installs superSU, busybox and cwm recovery. I would allways recommend rooting with CF Root over the Toolkit.
But that`s my opinion off course
gee2012 said:
CF root gets the job done in 20-25 seconds. It installs superSU, busybox and cwm recovery. I would allways recommend rooting with CF Root over the Toolkit.
But that`s my opinion off course
Click to expand...
Click to collapse
Yes go with the CFroot if u just want to root ur phone.
Sent from my GT-I9300 using Tapatalk 2
'K, I'll bite. I'm not going to give an overall recommendation - at the end of day, they both install an APK and put a new binary in /system/xbin.
Note: I used CF-Root to root my phone. When I talk about how the the toolkit does what it does, I'm basing my words on this image. I've seen the things in that image before, even though I haven't used the toolkit. This also means that my toolkit observations may not be entirely accurate but it's a batch script, anyway; you can just read through it and find out how it works. I'm also primarily a Windows user, but I used to use GNU/Linux quite a bit to write programs for a phone that I once had.
Rooting is, when broken down, the installation of a "su" binary installed to /system/xbin, that is owned by root and carries the setuid flag. This flag is important as the Linux kernel will then run the process whenever it's invoked as the person who owns it, root. This process can then, in turn, start other programs and they inherit the user ID (something like this - I'm taking my time reading TLPI...) so they are then running as root. There's also a "manager" app (Superuser or SuperSU) that will be installed; this app is talked to by the su binary (through the Android Binder AFAIK, though Superuser's source is available so if you really wanted to find out you could read that) to see, for example, if the program that is invoking "su" is allowed to do so. CF-Root installs the SuperSU apk to /system/app, which means that it survives factory resets. The toolkit, from a quick look at the Superuser ZIP in its folder and its batch file, also installs the Superuser apk to /system/app. When sideloading apps or installing from the Google Play Store, they usually get installed to /data/app.
Not all "su" implementations for Android need a manager app, I've seen implementations where su does not place restrictions on who is allowed to run it; uid=0 for everyone without discrimination! (Yes, that also includes you, Super Smilies Pack 3000 with boob smilies) Thankfully, neither the toolkit nor CF-Root do this. I lie a little. Superuser's su binary will automatically reject any request to become root if the Superuser.apk is not installed but SuperSU's su binary will automatically accept all requests to become root if the SuperSU apk is not installed. Personally, I prefer SuperSU's behaviour as there have been too many times with my old phones where I'd have to sign into Google Play after wiping /data just to install the Superuser APK when all I wanted was to run a simple command.
ext* filesystems along with other *NIX filesystems have the concept of file permissions, a concept shared by other *NIX filesystems. In order to actually place this su binary owned by root into a folder owned by root, you need to be root. (Actually, the folder is also owned by the shell group so a user which is a member of that group could do it too, but they wouldn't be able to set the all-important setuid flag as they're not the user root [perhaps a member of group root could do it but I don't know]) Usually, exploits in other programs running/can run as root or in the kernel are searched for so that you can temporarily root in order to install the su binary correctly. The GSIII (with the exception of Verizon's) has an unlocked bootloader, though, so programmers don't need to search for any of these: it's able to flash unofficial, unsigned recoveries and kernels.
CF-Root does this:
* it flashes a new CWM-based recovery in the recovery partition of the phone. If you've seen the stock Android recovery, you'll know that it just can't match the features of CWM. The important thing about CWM is that it runs as root, just like the stock recovery, but it also lets you place any file anywhere on the phone without requiring that the the ZIP file containing the files are not signed with a Samsung private key. Remember what I said about file permissions?
* there's also a param.bin file. I don't know anything about this file, but I suspect it's flashed to get the phone to boot up into recovery mode the next time it's started so that CWM runs before anything else
* it also flashes the cache partition (I'm not sure whether it overwrites or appends as I don't know how [and probably never will] know how ODIN works with two ZIP files: SuperSU, which contains the su binary, the SuperSU apk and a script that is run by CWM to set the required permissions on the su binary among other things, and the CWM app which lets you tell the recovery what actions you want it to perform in Android without having to navigate through the awkward interface of CWM itself. While I don't know how to do this myself, CWM recovery can be told to automatically run commands from an external source. I'm not talking about random websites on the Internet, but (I think) through files that have to be placed somewhere by root. This is what apps like the CWM app and ROM Manager do. This is also what CF-Root does to tell the recovery that the next time it's booted that it should install both the CWM ZIP and SuperSU ZIP. That's it in the case of CF-Root: you now have a phone with the two files required for root access, and a CWM recovery and an app to control it.
The toolkit:
(I only talk about the "insecure boot" options as I imagine the recovery option does something similar to the above and do remember that I haven't used the toolkit to root my phone so some assumptions are made. I also assume you know what ADB is as I won't be explaining it)
* it gets you to flash a kernel image with a patched adbd that runs as root, so adb on your computer, in turn, is able to place files anywhere on the phone's /. File permissions make it so you can't just place adbd in its expected place (/sbin) as any user and /sbin is also mounted on a ramdisk part of the flashable kernel image so it would be replaced on the next reboot, anyway.
* When the phone is running again with the new kernel, it then tells adb (now running as root) to push the Superuser APK and the su binary into their rightful place and sets the correct permisions on the su binary so that it runs as root
* if you've told it to install busybox, busybox is pushed and a bunch of symlinks for all the applets that BusyBox supports are set up
CF-Root installs, naturally, Chainfire's SuperSu whereas the toolkit installs Superuser. I much prefer SuperSU (and I bought a pro license for Superuser long before I did for SuperSu). Superuser's interface is much better than SuperSU's and it's also open-source but I find that SuperSU works much quicker for me (Root Explorer actually popped up a message on my sister's freshly-flashed Xperia Arc S saying that Superuser can be slow if Superuser hasn't granted it root access quick enough - I've never encountered that on my Huawei U8800pro with SuperSU which has pretty much the same specs as the Xperia) and it can also log the commands an app is running as root if you're suspicious of an application.
You'll notice that ADB still runs as a normal user with CF-Root. You can use Chainfire's adbd Insecure app which will replace /sbin/adbd everytime the phone is started with his patched adbd which always runs as root, or you can just flash one of the many kernels available that already include a patched /sbin/adbd.
CF-Root also does not install BusyBox. You can grab one of the installers from the Play Store but what I do personally is kang a CM9 nightly build for the I9300 and take the META-INF folder and the /system/xbin/busybox binary and strip out most of the lines in the update-script leaving only the lines that mount, extract and create the symlinks for busybox and place the result in a new ZIP which is then flashed with CWM.
Your "cf-root for example is incompatible with rommanager" gripe is easily solved - just flash another recovery. CF-Root just packages a CWM Recovery, an app to control CWM and SuperSU. CF-Root itself is not a resident component, but the recovery and SuperSU etc. are, if that makes sense.
qwerty12 said:
A long story with a lot of interesting and valuable information
Click to expand...
Click to collapse
Tnx! This is precisely what I have been looking for! A lot of the information I already found in seperate pieces but this made it click in my head. I used cf-root to root the phone and am currently deciding if I want to work with the included tools and cwm recovery or flash CWM touch
I got a busybox installer from the market and it works like a charm (Well Titanium backup seems to do its job anyway).
I must say I think was over analyzing this a bit since I owned a HTC desire before this phone where rooting has a lot more risks involved and a lot more steps.
The only advantage i can see to using toolkit is it will get updated quicker and it has loads of other options. If you just want to Root and flash a Rom cf root is way to go
Sent from my GT-I9300 using xda app-developers app
creesch said:
Tnx! This is precisely what I have been looking for! A lot of the information I already found in seperate pieces but this made it click in my head. I used cf-root to root the phone and am currently deciding if I want to work with the included tools and cwm recovery or flash CWM touch
Click to expand...
Click to collapse
Glad it helped
I must say I think was over analyzing this a bit since I owned a HTC desire before this phone where rooting has a lot more risks involved and a lot more steps.
Click to expand...
Click to collapse
Yeah, HTC's locked bootloaders and the S-ON/S-OFF rubbish is one of the reasons I decided to skip the One X and go for the Galaxy S3.
creesch said:
I must say I think was over analyzing this a bit since I owned a HTC desire before this phone where rooting has a lot more risks involved and a lot more steps.
Click to expand...
Click to collapse
Its fair to say that unlike many people on this forum you did your research. Searched.. and asked a valid question. Whereas the majority of people just ask questions without being bothered to figure it out themselves. So thanks. Over analyzing? Maybe a little... but its better than flashing any old thing like many other have done and continue to do. Big thanks to qwerty who has filled me in on some useful info also.
Sent from my GT-I9300 using xda premium
You should have thanked him tho maaan
Sent from my GT-I9300 using xda premium
creesch said:
Tnx! This is precisely what I have been looking for! A lot of the information I already found in seperate pieces but this made it click in my head. I used cf-root to root the phone and am currently deciding if I want to work with the included tools and cwm recovery or flash CWM touch
I got a busybox installer from the market and it works like a charm (Well Titanium backup seems to do its job anyway).
I must say I think was over analyzing this a bit since I owned a HTC desire before this phone where rooting has a lot more risks involved and a lot more steps.
Click to expand...
Click to collapse
Stick with 5.x.x.x recovery, touch(6.x.x.x) has some instability issues afaik
Sent from my GT-I9300 using xda premium
slaphead20 said:
Stick with 5.x.x.x recovery, touch(6.x.x.x) has some instability issues afaik
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Alright well since it was only the touch aspect that made me consider it i'll leave it just like it is
Hey guys
Hey guys i have the internationa galaxy s3 running 4.1.2, i haven't done anything to my phone yet and im about to root it is the boot loader unlcoked and if not how do i unlock it :good:, could someone please help me:crying::crying: and give me clear instructions and links please :fingers-crossed: thanks you so much,
BTw i know this is the wrong thread but i cant find the right one, thanks alot guys
regards nick
When I switched over from Blackberry to Android , I was wandering literally all over forums trying to get all these information.
Initially I was very hesitant to even root my phone as I thought I will Brick it !!! Then I went through a lot of articles on linux , android , and follwed developers like hashcode , dtrail1 , pedrotorresfilho , hsdpilot and llearnt more from them.
Even now I see a lot of posts by beginners asking How to Root ? How to Flash ? ..I wanted to help and encourage these beginners to explore the exciting world of open source with no limits ... This is a comprehensive guide with videos . Trust me guys Rooting and flashing is not that complicated provided you follow the steps given by the developers ...
Disclaimer : This is not intended to people who fear their warranty is lost after flashing !!! :laugh:
ASSUMPTION : I am assuming you have stock Razr without root or custom ROMs.
ALL THE STEPS AND PROCEDURES IN MY GUIDE ARE TRIED AND TESTED ON MY RAZR SO THEY ARE 100% WORKING
What is Rooting ? What are the benefits ?
I can go all day explain about rooting , in simple words it gives you admin access to all your file system on your android device.
There are several applications out there which helps you to customize , tweak your device which is otherwise blocked by your stock ( factory installed) android OS.
How to Root ?
There are several methods to do it . But I suggest you to use Easy One click root by EternityProject. Very easy and safe for beginners .
If you feel you want to unroot , just single click and your back to stock / factory condition
Just follow the step by step instruction listed.
http://forum.xda-developers.com/showthread.php?t=1710871
Video tutorial : http://www.youtube.com/watch?v=qaVJyxv0Kd0
How do I install ( will now be referred to as flash ) custom ROM's ?
Before you flash any ROM's you need to have a custom recovery to help to flash these ROM's.
Again there are many Custom recovery out there like Clock work Mod recovery , Boot menu manager ( gaining popularity ) , and the most safest " Safestrap recovery" . Why I like this is because it helps to Instal ROM's on different partition and your stock ROM remains safe , and very less chances to brick your phone. Boot Menu also works on a similar logic and is also very good , the learning curve is slightly higher. Yes there are limitation that certain ROM's are not supported on SafeStrap , but as I said this is just a NOOB's guide and to start, so SafeStrap is a better option.
Safestrap is developed by HashCode :
1. Download the latest Safestrap APK from here. http://blog.hash-of-codes.com/downloads/safestrap/
2. Find the APK using a Filemanager tool and open it on your device, then click “Install”.
3. Once installed, open up the Safestrap application as you would any other app.
4.Then use the “Install Recovery” button. You should see the current version down in the lower left corner of the window. And the “Status:” should say “Installed” when you’re done.
5. From there you can reboot and you *should* see a new splash screen during the boot up. While this is showing you can enter Safestrap Recovery using the [ menu ] button.
Video tutorial : http://www.youtube.com/watch?v=PAqphCaein0
Once you have installed Safestrap your all good to go and play with your Razr by installing custom ROM's.
word of caution : Make sure the ROM you are installing is compatible with your Razr CDMA/GSM
BEFORE YOU FLASH ANY ROM/FILES DO A COMPLETE PHONE BACK UP USING ANY OF THE METHODS IN THE NEXT THREAD
One of my favorite ICS ROM is Eclipse 1.5 because its a very stable , smooth and has good battery performance.
Here's the link on how to instal it :
http://forum.xda-developers.com/showthread.php?t=1795493
Quick summary on Instal using safestrap :
a) Download the latest ( non beta ) version of Eclipse ROM to your SD card
d) Reboot to recovery mode.
c) Goto Boot Options , Click on ROM slot 2 , choose size ( 2 GB is ok) and create a partition and give it a nickname if u need ( ex eclipse)
d) Now you must see ROM slot 2 as Active , so all your future operations will be affected on this slot.
e) Come back to main menu , goto wipe : wipe cache , dalvik cache , and then factory reset
d) Come back to main menu again goto instal , choose the file from your SD card . You instal will start.
e) For GSM users only : after instal of ROM , instal this patch http://forum.xda-developers.com/showthread.php?t=1805380
f) Reboot , this will take longer than usual as your file system is getting setup for first use.
g) Your dome !!!
h) If you want to go back to your stock , just reboot into recovery and activate your stock ROM slot . Reboot
Video Tutorial : http://www.youtube.com/watch?v=4YYuQ1fw0a8 ( this is for bionoc but the steps are same for Razr/Maxx)
FAQ section :
Q: How do I back up my apps so that i can use them once I flash custom ROM ??
A :Instal titanium backup , and backup Apps + data . Once your done flashing your new ROM restore backup * Refer the next post to do a full phone backup without root.
Q: I am selling my mobile / exchanging it how do I bring it back to factory condition ???
Step 1: Boot to Safestrap recovery , Make your Moto rom as active . Goto your Custom ROM slot , wipe cache , dalvik cache , factory reset. Reboot.
Step 2: Goto Safestrap , uninstall recovery , Uninstall Safestrap.
Step 3: Goto Super user app , unroot. , uninstall Super User app.
Done !
If you have any questions feel free to ask
******************************************* Level 2 training guide *********************************************************************************
Full backup of Stock ROM Using Safestrap
1. Boot into recovery
2. Select ( activate) your stock ROM
3. Goto Back up , set backup name as Stock
4. Choose external SD , swipe to backup .
To restore :
1. Select and Activate Stock ROM slot
2. Goto Restore , choose file from SD and restore.
Same steps can be followed for Custom ROM also , but be careful when you restore you choose the correct ROM slot or else you will brick your phone.
Your Backup will be found on : SDcard/TWRP/BACKUPS/.....
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
FULL Phone backup without using ROOT
Before beginning, you need to setup your ADB and have your device detected. You must also running Android version 4.0 and above. Also, make sure you have a file manager installed. You can use ES File Explorer.
Connect your device and make sure its listed with the following command:
adb devices
Run a FULL backup with the following command:
adb backup -f FullBackup.ab -apk -all
This will create a “package” called “FullBackup.ab” on the current location in your command prompt. This is your backup package.
Now you can root your phone.
Once finished rooting, insert the “FullBackup.ab” package on your sdcard
Hit the menu button and look for “Extract from ADB backup” option. This will prompt you to search for the file. Use the file manager that you installed earlier and navigate to the directory and select the FullBackup.ab file.
Now restore like as if the backup was made with Titanium Backup. Don’t forget to make a fresh copy of the backup using Titanium Backup. You’re Done!
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Setting Up ADB
1. Dowload the Motorola USB drivers for your model from the Moto website.
2. Download the Latest Android SDK EXE from Google( make sure you select the exe version only): http://developer.android.com/sdk/index.html
3. Once downloaded, double click the exe file to open it and change the directory that it is installing everything to to c:\android-sdk\
4. Click on the SDK Manager and it will ask you to install packages. Select the following and leave all others unchecked:
- Android SDK Tools ( by default it would be installed )
- Android SDK Platform Tools
-Google USB Driver Package
5. Then click continue and follow the on screen prompts until all of the packages are installed and it finishes.
6. On your phone, click Settings > Applications > Development and make sure USB Debugging is on.
7. Plug your phone into your computer via USB cable (it needs to be on). It should say installing drivers if using Windows.
8. Open Windows File Explorer and look for the android-sdk folder inside of the C : drive.
- Then open the platform-tools folder inside that. Now, hold the shift key down on your keyboard and right click in any blank area inside that folder.
- This will give you the option to open a command window here.
- Select that and a command prompt will open saying c:\android-sdk\platform-tools\
*if using windows XP, this won’t work. So instead open command prompt first by going to Start > Run > then typing in cmd and hitting enter. Then type cd c:\android-sdk\platform-tools\ and hit enter, then continue.
8. Type the following into the command prompt window (hitting enter at the end of every line):
adb devices
You should see a serial number pop up, it’s the serial number of your phone. This means you are all set!
If you do NOT see a serial number, then you have not installed the moto usb drivers correctly. try reinstalling them from PDAnet .
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
UNBRICKING GUIDE FOR ICS
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Bricked your device ??? Dont worry
Pre -Requisites :
1. Download the latest RSD lite : http://forum.xda-developers.com/showthread.php?t=1539192
or
use EPRL Flash it : http://forum.xda-developers.com/showthread.php?t=1453660
2. Download the ICS fastboot file for your region from here : http://sbf.droid-developers.org/
Steps :
1. Power off device and enter into BP tools and select AP fastboot mode ( volume up + volume down + power button at same time , select 3rd option by using volume down key and use volume up for selecting it )
2. Connect your phone to PC using USB.
3. Open RSD lite/EPRJ Flash it , select the Fastboot XML , and start flashing. ( follow instruction from the above links for RSD or EPRJ )
4. Reboot and enter to stock recovery ( press volume up + volume down) , Clear Cache and data
5. Reboot.
Video tutorial thanks to theRazrGuy : http://www.youtube.com/watch?v=krFmfMMLeWM
SAJdroid said:
******************************************* reserved for level 2 training guide *********************************************************************************
Click to expand...
Click to collapse
Great guide, thank you very much! A much needed resource!
FrankPlummer said:
Great guide, thank you very much! A much needed resource!
Click to expand...
Click to collapse
Thanks.. I will be updating this guide with more information on custom recovery apps , Razr compatible stable roms , unbricking ur device etc..
That will be on level 2.
Great Guide except you left out the most important part. Doing a full backup of your phone before modifying it. A FULL backup, not just your apps and data with TiBu.
85gallon said:
Great Guide except you left out the most important part. Doing a full backup of your phone before modifying it. A FULL backup, not just your apps and data with TiBu.
Click to expand...
Click to collapse
How to do a FULL BACKUP?
85gallon said:
Great Guide except you left out the most important part. Doing a full backup of your phone before modifying it. A FULL backup, not just your apps and data with TiBu.
Click to expand...
Click to collapse
Are you referring using ADB before root ? If yes , I left it out intentionally for Level 2 training , as this is beginner level many will not be comfortable using ADB . I will need to give a tutorial on setting up ADB first .. I am updating on full phone back up now for everyone who are aware of ADB . ADB tutorial will be added soon.
[ EDIT ]
Full back method updated - based on 85Gallon's suggestion -
I'll try again (first time I just delete everything from the phone)
I had not seen so detailed explanations at first attempt .
thanks
SAJdroid said:
Are you referring using ADB before root ? If yes , I left it out intentionally for Level 2 training , as this is beginner level many will not be comfortable using ADB . I will need to give a tutorial on setting up ADB first .. I am updating on full phone back up now for everyone who are aware of ADB . ADB tutorial will be added soon.
[ EDIT ]
Full back method updated - based on 85Gallon's suggestion -
Click to expand...
Click to collapse
No. adb is too complicated LOL. I am talking about doing a backup with CWM Recovery that you install per your guide. I believe it now does a Nandroid backup. It will do a single backup that has your ROM, settings, data , and apps. Make sure you have enough room on your SD card for the backup. It will take a snapshot of your phone (less sd card) so you can do a full restore if something goes awry. It is similar to restoring a hard drive with an image if your hard drive crashes on your computer. Just restore and it is good to go. No need to change settings, add apps, set up accounts. Just restore, reboot, and you are where you were when you made the backup.
full backup can be done with Titanium Backup?
all saving to SD card? (installed programs, pictures, music, data)?
thanks and sorry for questions
monkteo said:
full backup can be done with Titanium Backup?
all saving to SD card? (installed programs, pictures, music, data)?
thanks and sorry for questions
Click to expand...
Click to collapse
full backup can be done with custom recovery (BMM, safestrap)
monkteo said:
full backup can be done with Titanium Backup?
all saving to SD card? (installed programs, pictures, music, data)?
thanks and sorry for questions
Click to expand...
Click to collapse
No TiBu does not do a full backup. It backs up data and apps. It doesn't do the ROM.
When I connect the phone to the PC after installed the motorola drivers and doing the ADB I get the noise that the win 7 sees the usb device but then it pops up that the usb device is bad etc. And I dont even get anything when from motorola when I connect up. No icon on the tray, nothing. Ive restarted several times.. ANy idea?
editeD: It was the cable...
monkteo said:
full backup can be done with Titanium Backup?
all saving to SD card? (installed programs, pictures, music, data)?
thanks and sorry for questions
Click to expand...
Click to collapse
ROM -> refer my second post , try the safestrap method
installed programs, data ( app profiles, save data )-> Yes , just select : backup system + data
Suggestion : Keep ur Music/Pics on SD card , u dont need to back them up Save time & space . Also its better your move your APPS to SD to save space on your internal storage if you are a heavy APP user. This also can be done by Titanium Backup ...
when i wipe cache , dalvik cache , and then factory reset i erase data only on slot 2?
not the whole phone?(
thx
monkteo said:
when i wipe cache , dalvik cache , and then factory reset i erase data only on slot 2?
not the whole phone?(
thx
Click to expand...
Click to collapse
Yes , it will affect only that slot ... make sure u have selected the 2nd slot .
Just imagine it as different drives on your PC ( C: , D: , E:.. ) your formatting will affect only that partition...
SAJdroid said:
Yes , it will affect only that slot ... make sure u have selected the 2nd slot .
Just imagine it as different drives on your PC ( C: , D: , E:.. ) your formatting will affect only that partition...
Click to expand...
Click to collapse
thanks, perfect example, today I will try installing eclipse rom.
I'll be back with impressions.:laugh::good:
Everything worked perfectly , now I'm on Eclipse ROM and xdadeveloper was the first program installed .
Sent from my XT910 using xda app-developers app
monkteo said:
Everything worked perfectly , now I'm on Eclipse ROM and xdadeveloper was the first program installed .
Sent from my XT910 using xda app-developers app
Click to expand...
Click to collapse
GOOD :good: now you can experiment with different ROM's on the other slots ( can give 1 GB per slot if used for experiments) ... Hope u have backed up your Stock using Safestrap..
SAJdroid said:
GOOD :good: now you can experiment with different ROM's on the other slots ( can give 1 GB per slot if used for experiments) ... Hope u have backed up your Stock using Safestrap..
Click to expand...
Click to collapse
Oh yes, I did backup, but I make 2g/slot (Eclipse) and works perfectly .
many thanks
Intro
This is a guide for people who want to make some modifications to config files, or other files, on System partition but do not want to root their phone or install custom recovery in order to keep OTAs and some apps, which don't play nicely with rooted phones, working. Examples of those config mods could be changing DPI or changing volume levels etc, which you would only do once and forget about it.
While root allows you to do those kinds of changes from within android, this methods would require a PC.
If you are familiar with temporary booting into a custom recovery, skip to step 5.
The usual i am not responsible for any of your actions / bricked phones disclaimer applies.
Prerequisites
- A working adb / fastboot environment. Please use Android SDK, if you installed your adb and fastboot using other tools, things might not work, so please just install SDK, install Google USB Driver from SDK manager, install Platform-Tools from SDK manager (should be installed by default) and then add your sdk platform-tools path to your PATH environment variable to have it available in cmd in every path.
- Unlocked bootloader
- TWRP image for you phone (.img) https://twrp.me/devices/huaweinexus6p.html
Follow the [GUIDE] Unlock/Root/Flash for Nexus 6P for that.
Instructions
Here is an example of modifying DPI. I prefer build.prop method of modifying DPI because using the adb wm density command usually caused some issues for me, but modifying via build.prop didn't.
1 - With you phone ON, connect it to the PC and make sure adb is working by running
Code:
adb devices
and making sure that device is listed
2 - Reboot into bootloader. and make sure fastboot is good to go too. Run commands one at a time:
Code:
adb reboot bootloader
fastboot devices
3 - Place your TWRP image file in some easily accessible folder, for the sake of this example i will use C:\Mods.
4 - Temporary boot into TWRP (we are not flashing it here at all).
Code:
fastboot boot c:\Mods\twrp-2.8.7.0-angler.img
Here is where things may not work. If you don't see your phone boot into TWRP then either your adb / fastboot environment not setup correctly (installed via a tool instead of SDK) or your img file is corrupt.
One thing that works for me when TWRP refuses to boot is to restart cmd and issue the command again this closes and reopens adb/fastboot daemon.
5 - Once TWRP is up on your phone it may display a warning saying "TWRP has detected an unmounted system partition". Swipe to allow modifications at the bottom. This screen may not come up at all.
6 - Go to Mount >>> Tick System >>> Make sure "Only Mount System Read Only" is unticked >>> Press Back button
7 - Back on your PC check if your device is listed
Code:
adb devices
8 - Pull the file you need to modify from system partition to your PC. Please note the direction of the slashes:
Code:
adb pull /system/build.prop c:/Mods
9 - Now you should see build.prop in your c:\Mods folder. Use Notepad++ or something like that to edit the file. Find the line with lcd_density= and change it's value to whatever you need and save the file.
10 - Push the file back to your phone:
Code:
adb push c:/Mods/build.prop /system
11 - Reboot
Code:
adb reboot
12 - Profit.
Hope this will help anyone who is looking to do some mods without installing custom recovery and rooting your phone.
Cheers.
Would this work for adding the tethering bypass line in the build prop?
Yes it will. What's the line again I was looking for it the other day and couldn't find it...
Works are per OP's original post, tested and boosted the headphone volume without a problem.
Headphone path is /system/etc/mixer_paths.xml
So as per OP's example to pull: adb pull /system/etc/mixer_paths.xml c:/Mods
push: adb push c:/Mods/mixer_paths.xml /system/etc
I'm using the OP's "Mods" folder to demonstrate the file path but this may vary on your PC.
Can I use this to push SuperSU / etc to my device without having to permanently flash TWRP?
skrowl said:
Can I use this to push SuperSU / etc to my device without having to permanently flash TWRP?
Click to expand...
Click to collapse
You can certainly push the files to system partition and they will retain there after reboot. So if you know which files have to be pushed for SuperSU then give that a go. It shouldn't break anything.
I haven't tried pushing SuperSU files to system partition before so I can't guarantee that OTAs will work after this. The only way to find out is to try it i guess...
Can you run nandroids?
not sure if it's allowed or not.. but with this can i push hosts file onto the phone as well for ad-blocking...?????
I will say thanks now and try it later. These are the type of tweaks I would like to make to my phone. Do you know if changing the DPI cause any stock applications to show up broken like they do on the Samsung phones?
NCguy said:
Can you run nandroids?
Click to expand...
Click to collapse
Im not sure what you mean?
rohit25 said:
not sure if it's allowed or not.. but with this can i push hosts file onto the phone as well for ad-blocking...?????
Click to expand...
Click to collapse
If it's on the system partition then I yes you can.
locolbd said:
I will say thanks now and try it later. These are the type of tweaks I would like to make to my phone. Do you know if changing the DPI cause any stock applications to show up broken like they do on the Samsung phones?
Click to expand...
Click to collapse
I've never had a problem with changing DPI using this method on a nexus phone if that helps.
denk said:
Im not sure what you mean?
Click to expand...
Click to collapse
Can you run nandroids backups from TWRP by just booting into it?
okay so after i did this i get the following during boot up
"Your device is corrupt. It can't be trusted and may not work properly". Does this mean i will not get Securty Updates any more? I saw i had an update before i performed this however, now i do not see that update notifications any more.
locolbd said:
okay so after i did this i get the following during boot up
"Your device is corrupt. It can't be trusted and may not work properly". Does this mean i will not get Securty Updates any more? I saw i had an update before i performed this however, now i do not see that update notifications any more.
Click to expand...
Click to collapse
I got this too when I flashed MOAB via adb sideload. I'm just wondering if the same warning appears with the adb push method. Also, the file's permissions don't need to be set after adb push?
My main concern is if Android Pay still works with the red triangle warning. Anyone?
FYI Flashing back to stock is no issue for me.
NCguy said:
Can you run nandroids backups from TWRP by just booting into it?
Click to expand...
Click to collapse
I think if you get the latest TWRP which supports decryption of data partition (where all your stuff is) you should be able to back it up.
Edit: backup works on nexus 5 with temporary TWRP boot. Sorry I'm still waiting for my 6p to arrive.
locolbd said:
okay so after i did this i get the following during boot up
"Your device is corrupt. It can't be trusted and may not work properly". Does this mean i will not get Securty Updates any more? I saw i had an update before i performed this however, now i do not see that update notifications any more.
Click to expand...
Click to collapse
Thanks for trying it out! Sometimes OTA notifications take a little while to come up after reboot. But based on the warning Im afraid that they might be disabled now. It looks like it runs some sort of a check on the system partition to verify its legitimacy. So modifying files would be fine on it using this method but looks like adding them won't work.
TWRP just released their recovery with decryption support so you can just follow the standard procedure or just temporary booting into TWRP and rooting from there which works as well.
denk said:
I think if you get the latest TWRP which supports decryption of data partition (where all your stuff is) you should be able to back it up.
Edit: backup works on nexus 5 with temporary TWRP boot. Sorry I'm still waiting for my 6p to arrive.
Click to expand...
Click to collapse
On your Nexus5 I assume you are also unrooted? And have you tried a Nandroid restore, booted TWRP, no root?
NCguy said:
On your Nexus5 I assume you are also unrooted? And have you tried a Nandroid restore, booted TWRP, no root?
Click to expand...
Click to collapse
Just ran a restore to test it for you. Works fine as well.
My N5 is unrooted.
.
denk said:
Just ran a restore to test it for you. Works fine as well.
My N5 is unrooted.
.
Click to expand...
Click to collapse
Thanks a lot for that. I didn't unlock the bootloader. Ugh. Time to start over. To me nandroids alone make it worth the effort.
Hello ive not done any guides before but since i had to search all over to try find out what i was looking for and stumbled across a lot of good information and thought id share it. None of this was my findings but there isn't anything clear on how to actually accomplish this on a Fire stick.
Im going to attempt to share how i have managed.
This guide assumes you already know how to transfer files to your stick.
First off, current Fire stick os is 5.2.1.0 and is rootable with Kingoroot.
https://root-apk.kingoapp.com
1. Download Kingoroot and ADB to your Fire stick, do this whichever way you normally get apk/files onto your Fire stick.
2. Download Kingoroot superuser and ADB to your Fire stick.
3. Run the Kingoroot tool and let it finish, when you have root, install Kingo roots Superuser. (If you install this before rooting it wont make any difference).
Now you should have a rooted Fire stick on 5.2.1.0 with Kingoroots SuperUser.
Now its time to downgrade your Fire stick. This file was provided by AFTVnews over at another thread and cuki3r3k83bln accomplished downgrade on the thread also so please leave thanks for them as before he posted the file and information i had no idea it was possible. Im suggesting to download the 5.0.5 file as i did because this was when firestarter worked with home button detection.
Download Fire Stick os 5.0.5
http://amzdigitaldownloads.edgesuit...te-kindle-montoya-54.5.3.7_user_537174420.bin
Once you have it downloaded rename the downloaded file to update.bin.
Im going to explain how i did it, i know there is many other variations on how to accomplish this and im not too familiar with adb commands but the way i will show is the way it worked for me.
We need to transfer the downloaded and renamed update.bin to the Fire stick so if you would like to transfer it with apps to fire or through command or any other variation thats fine but ill show commands used from windows laptop using adbLink.
Please note, if your using a different method to transfer you will have to slightly modify step 5 on where your update.bin is stored so cd /sdcard/download. if your update.bin is stored in download folder.
Another note is to make sure your file name is correct, mine was named update.bin.bin rather than update.bin this was fine just make sure to name it correctly or you will have to modify step 6 and step 8.
1. Open up adbLink and connect your device.
2. Push the update.bin to the sdcard. (this takes quite alot of time as your pushing 311mb file so be patient)
3. Once pushed you need to open up ADB Shell.
4. Run the command: su
5. Run the command: cd /sdcard
6. Run the command: mv ./update.bin /cache/
If you get an error about no space on device do the following:
Run the command rm -f /cache/*.bin
Run the command rm -f /cache/*.zip
Run the command exit
Run the command exit then reopen ADB Shell in adbLink repeat step 6.
7. Run the command cd /cache/recovery
8. Run the command echo --update_package=/cache/update.bin > command
9. Run the command reboot recovery
Your Fire stick should automatically start the downgrade and take 10 minutes or so.
As soon as its finished go back to your Kingoroot app and re-root your Fire stick. Then block updates (method 1) using AFTVnews guide at:
http://www.aftvnews.com/how-to-block-software-updates-on-the-amazon-fire-tv-or-fire-tv-stick/
You should now be on 5.0.5 rooted and have updates blocked
All your apps should be still intact. Make sure you uninstall appstarter/firestopper and reinstall firestarter 3.2.3 (if you use it)
Then follow AFTVnews guide on how to re-enable it here:
http://www.aftvnews.com/how-to-cont...v-and-fire-tv-stick-software-version-5-0-5-1/
Please give the credit deserved to @AFTVnews.com and @cuki3r3k83bln
Its suggested all over to hold off before doing anything that could brick the device until rbox releases a recovery.
Please do not use any type of Su modifying tool/script/apk eg: SuperSume as these do not work and you will end up with a small brick.
Also its been pointed out to me by @deanr1977 that if your going to use this guide and decide to update Fire Stick os in the future, it maybe safer to unroot it first.
With that out of the way please excuse the bad layout of the guide as im no expert and would like to just share my experience.
Would I be able to go back to 5.2.1.0 once custom recovery and rom is released?
FireTho1 said:
Would I be able to go back to 5.2.1.0 once custom recovery and rom is released?
Click to expand...
Click to collapse
i cant see any reason why not, either grab the 5.2.1.0 .bin file and follow the guide using that or let it automatically update after re-enabling updates.
Are there any reasons for downgrading to 5.0.5? Does it have any advantages?
Bierfreund said:
Are there any reasons for downgrading to 5.0.5? Does it have any advantages?
Click to expand...
Click to collapse
As far as im aware upto now, it seems that Firestarter home button detection works as it should, and firmware after this Firestarter will not work with home button detection.
Which is a big thing for me personally as i only use Firestick for netflix and kodi and its much easier to launch from within Firestarter.
Its good to know that the process of upgrading/downgrading is applicable to Fire stick as you never know what Amazon will try to take from you.
You sir are my hero. Kudos for the tutorial!
sconnyuk said:
i cant see any reason why not, either grab the 5.2.1.0 .bin file and follow the guide using that or let it automatically update after re-enabling updates.
Click to expand...
Click to collapse
Its not recommended to let it auto update from root, unroot first then re-enable the update progress.
Also please can you note in your guide that its not recommended to try to swap the Su for Chainfires Su with the Super Sume or Super Sumepro app because so many people on this forum have bricked with this method & if any new users try your way & after want to unroot/swap method after the first boot they could have a non working device.
Ive not tried this guide myself (i dont need too) but if its working fine this info would be good to have here.
deanr1977 said:
Its not recommended to let it auto update from root, unroot first then re-enable the update progress.
Also please can you note in your guide that its not recommended to try to swap the Su for Chainfires Su with the Super Sume or Super Sumepro app because so many people on this forum have bricked with this method & if any new users try your way & after want to unroot/swap method after the first boot they could have a non working device.
Ive not tried this guide myself (i dont need too) but if its working fine this info would be good to have here.
Click to expand...
Click to collapse
Fair point about pointing out about the brickable and dangerous su swapping methods with supersu me etc.
I will add a mention about it after the line that reads:
'Its suggested all over to hold off before doing anything that could brick the device until rbox releases a recovery.'
As for not recommended to auto update while rooted, ive had 2 sticks and a Fire Tv 2 auto update from 5.0.5 to 5.0.5.1 and then to 5.2.1.0 when my router was reset, (im sure im not the only one from what ive read either).
But since im a helping type of guy ill add this also.
Ok mate, just going by what's been said from the AFTVNews & Amazon Firestick forums. Glad you are including this thanks, Its just some only skim through the threads & read only the parts they want to so if this is included it may cut down on the "I've bricked my Amazon device please help threads" which clog up the forum.
Sent from my SM-G900F using Tapatalk
i'm trying to downgrade to the point where display mirroring worked on windows devices, this is before 5.0.5, can i use this method to downgrade to another bin before 5.0.5?
sins07 said:
i'm trying to downgrade to the point where display mirroring worked on windows devices, this is before 5.0.5, can i use this method to downgrade to another bin before 5.0.5?
Click to expand...
Click to collapse
Id take a stab and say if your stick originally came with a firmware below 5.0.5 but I honestly do not know as ive not tried but I cant see why it wouldnt work. You can go from 5.2.1.0 to 5.0.5.1 or to 5.0.5 so id imagine so.
What features have been removed by 5.0.5? Im interested myself and may try this myself if there is features I could use.
Amazing! I can't believe this was hard to find as all the news out there say you can only root the stick using a hardware mod.
I downgraded and rooted both my Sticks. Installed Firestarter 3.2.3, installed Seeder, removed unneeded processes from running and these things are super quick now. You still have to load the crappy slow Amazon launcher to keep the settings but oh well. Nicely done, now I hope a recovery option comes out and I can mess around further . Heatsink and overclocking anyone? lol
@vulcan4d recovery & prerooted rom is being worked on at the moment by rbox in this forum
Sent from my SM-G900F using Tapatalk
vulcan4d said:
Amazing! I can't believe this was hard to find as all the news out there say you can only root the stick using a hardware mod.
I downgraded and rooted both my Sticks. Installed Firestarter 3.2.3, installed Seeder, removed unneeded processes from running and these things are super quick now. You still have to load the crappy slow Amazon launcher to keep the settings but oh well. Nicely done, now I hope a recovery option comes out and I can mess around further . Heatsink and overclocking anyone? lol
Click to expand...
Click to collapse
Can I ask what processes you removed/stopped and how you accomplished this?
Id like to do the same on 2 of my sticks.
sconnyuk said:
Can I ask what processes you removed/stopped and how you accomplished this?
Id like to do the same on 2 of my sticks.
Click to expand...
Click to collapse
I would like to give credit to this post for removing unneeded services:
http://forum.xda-developers.com/fire-tv/help/root-disabling-apps-services-bloat-t3325333
I only found a few from the list but that list was meant for a Fire TV so I'm sure there is more running. Just launch ADB Shell in ADBFire/Link and type pm disable <service_name>
vulcan4d said:
I would like to give credit to this post for removing unneeded services:
http://forum.xda-developers.com/fire-tv/help/root-disabling-apps-services-bloat-t3325333
I only found a few from the list but that list was meant for a Fire TV so I'm sure there is more running. Just launch ADB Shell in ADBFire/Link and type pm disable <service_name>
Click to expand...
Click to collapse
Thanks ive disabled them as per the guide you linked to. Can I further ask what the program seeder does and whether to have it set to aggressive or not?
Thanks for the info.
@sconnyuk i've downgraded successfully kingo root'ed stick 5.2.1->5.0.5 . But funny thing was under root shell command "wipe data " .It wiped device clean but root still stays on . Got OTA disabled and my other king root 5.0.5 stick will have similar treatment .
nicefile said:
@sconnyuk i've downgraded successfully kingo root'ed stick 5.2.1->5.0.5 . But funny thing was under root shell command "wipe data " .It wiped device clean but root still stays on . Got OTA disabled and my other king root 5.0.5 stick will have similar treatment .
Click to expand...
Click to collapse
You will need to unroot it for root to go.
Kingoroot has the option to do this if its what you want.
You need mouse toggle for fire tv to navigate to the 'in app' menu icon if not plug fire stick into pc and run Windows version of Kingoroot to unroot.
Interesting, I just bought a 3rd Amazon stick to root. After running KingRoot, I've noticed I did not need to install KingUser at all. If you launch KingRoot again it allows you to launch KingoUser which is the same thing. I'm assuming that KingUser is just an updated version of what KingRoot already installs.
Sconnyuk, I checked all the boxes and chose Moderate. This was also mentioned in the XDA forums however sadly I cannot find the post anymore. Seeder is an application that has been around for a while which improves the response time on Android devices. There is a lot of technical details into how it works, but the point is the Amazon stick is not the fastest thing in the world and anything helps. Give it a try and see for yourself.
sconnyuk said:
Id take a stab and say if your stick originally came with a firmware below 5.0.5 but I honestly do not know as ive not tried but I cant see why it wouldnt work. You can go from 5.2.1.0 to 5.0.5.1 or to 5.0.5 so id imagine so.
What features have been removed by 5.0.5? Im interested myself and may try this myself if there is features I could use.
Click to expand...
Click to collapse
Miracast display mirroring became non-compliant with windows systems, it still works fine with android.
Not sure my question in subject is clear, so here's the thing...
I have dual-boot tablet with Android 5.0.1 and Windows 10 installed, and the model is Onda V80 Plus (32GB), if that matters at all.
I'm really having hard time rooting this device using standard methods (even with much of background knowledge and experience), so I was about to take a different route.
I installed Paragon ExtFS windows app which gives me read/write access to /system and /data android partitions (which have ext4 filesystem).
I was wondering if anyone knows if it's possible to gain root access in Android just by copying some files and changing some permissions or whatever from within Windows OS?
Basically, for those not familiar with ExtFS app, I can assign a drive letter to /system and /data partitions, and do whatever I want with them just like with any other drive or volume.
I'm aware that modifying ext4 partitions can render my Android OS unbootable, but I have a backup and would like to try it anyway as this is my last option.
When I look into SuperSU.zip file (which I always flashed through CWM/TWRP recovery to gain root access), I see many files which some lengthy script is copying all around, so I stopped after analyzing about hundred lines of code lol.
I really didn't find any method like this on the internet, so I wonder if that's even possible, and if it is, how would I go about it?
Thanks everyone.
Burs said:
Not sure my question in subject is clear, so here's the thing...
I have dual-boot tablet with Android 5.0.1 and Windows 10 installed, and the model is Onda V80 Plus (32GB), if that matters at all.
I'm really having hard time rooting this device using standard methods (even with much of background knowledge and experience), so I was about to take a different route.
I installed Paragon ExtFS windows app which gives me read/write access to /system and /data android partitions (which have ext4 filesystem).
I was wondering if anyone knows if it's possible to gain root access in Android just by copying some files and changing some permissions or whatever from within Windows OS?
Basically, for those not familiar with ExtFS app, I can assign a drive letter to /system and /data partitions, and do whatever I want with them just like with any other drive or volume.
I'm aware that modifying ext4 partitions can render my Android OS unbootable, but I have a backup and would like to try it anyway as this is my last option.
When I look into SuperSU.zip file (which I always flashed through CWM/TWRP recovery to gain root access), I see many files which some lengthy script is copying all around, so I stopped after analyzing about hundred lines of code lol.
I really didn't find any method like this on the internet, so I wonder if that's even possible, and if it is, how would I go about it?
Thanks everyone.
Click to expand...
Click to collapse
Root needs a custom kernel. Not something you are gonna do with a Windows setup the way you have it. Also you will most likely not find anything as that is most likely not an official version of Android as Google doesn't allow dual booting.
Thanks for a reply. But I don't see what does custom kernel have to do with what I try to achieve? If I could, in my Windows environment, replicate the modifications that script inside SuperSU zip does to /system partition, I should gain root access, right? In theory that is, since I'm aware lots of things can go wrong. I was hoping someone could explain a bit what SuperSU script is doing when run inside custom recovery, so I try to do the same thing. Again, if it's possible, and if it's worth the time spent. But I have time, and I'm always willing to learn something new.
Burs said:
Thanks for a reply. But I don't see what does custom kernel have to do with what I try to achieve? If I could, in my Windows environment, replicate the modifications that script inside SuperSU zip does to /system partition, I should gain root access, right? In theory that is, since I'm aware lots of things can go wrong. I was hoping someone could explain a bit what SuperSU script is doing when run inside custom recovery, so I try to do the same thing. Again, if it's possible, and if it's worth the time spent. But I have time, and I'm always willing to learn something new.
Click to expand...
Click to collapse
what su is doing is pulls the kernel and patches it. root access is defined in the kernel. what itnis doing in system is flashimg just the apk
Ok, I see. So if I ask someone who rooted the same model successfully to send me patched kernel, I could easily flash it in fastboot mode (my bootloader is unlocked). So only thing left to do would be to copy apk inside /system/app, and cross my fingers? I'll post my findings if I manage to do something worth writing about. Thanks.
I have same problem with you. I can't root my Onda V80 plus. I unlock bootloader, flash recovery for my device. Then, i put it into recovery mode and install supersu.zip over recovery. When i reboot this onda, it has stopped in onda logo.
bahuy2003 said:
I have same problem with you. I can't root my Onda V80 plus. I unlock bootloader, flash recovery for my device. Then, i put it into recovery mode and install supersu.zip over recovery. When i reboot this onda, it has stopped in onda logo.
Click to expand...
Click to collapse
I managed to root my Onda few days after my last post, but forgot to post my findings, sorry. I didn't used any of my hacker's skills lol, but I researched a bit more and found out what I was missing. The same issue is with you, so you have to disable verity before flashing recovery by typing in these commands:
Code:
adb root
adb remount
adb disable-verity
adb reboot
After rebooting install supersu.zip, and the next boot won't hang on Onda logo anymore. Hope this helps you.
btw, note that not just any adb version has verity command line switch. You have to download newer adb version!
Thank you! I trie a lots times, but i can't make successfully!
Basic root procedure would be: unlock BL -> disable verity -> flash (temp) recovery -> install SuperSU
Here are the links containing all the files neccessary for rooting Onda V80 Plus: Mega | MediaFire
Note the ReadMe.txt inside archive. It contains list of adb/fastboot commands needed to be executed in order to successfully root the device.
Thank you very much! I download your file and root successfully my Onda V80 plus! It works well for me.