Related
So, I'm messing about with building android from the source, just as a learning process and for my own personal satisfaction at this point.
I've come most of the way under my own steam.. got a build up and running from the donut-plus-aosp branch, all google apps included and working.. but I don't actually know how to include root access in the build.. I know this is probably an embarrasingly simple question for a dev, and I feel suitably stupid for having to ask.
Also.. now you're here.. apps2sd.. do I need to compile anything special for that or is it just a bunch of symlinks in init.rc?
Muchos gracias.
I believe the root access is located in the kernel (boot.img)
You would also want to include the SU binaries and busybox.
For the apps2sd, the apps2sd script is run from the init.rc IIRC
Do not hold me up on this because I have not even looked at Android yet, but this is what I gather from reading the forums. I'm hoping it may give you a little direction while someone who has actually built from the source steps in
Thanks. I've already included the su binary and superuser apk but couldn't launch them, so I thought I must be missing something either in the kernel or init.rc.
I was hoping not to have to build the kernel manually just yet.. walk before you can fly and all that, but maybe it's time to grow some wings.
You should just compile cyanogen's kernel. he has it on his github. btw.. did you add busybox? i think apps2sd requires it but im not sure.(check logcat on startup, see what errors its throwing)
I've just added busybox in, but I can't do anything with apps2sd until I get root sorted.
I'm sticking with the 2.6.29-donut kernel for now.. cyan's includes loads of patches that I don't understand yet.. I'll compile it and see what happens purely as an experiment but I reckon it'll give me problems...
Just looking at the configuration options for cyan's kernel makes me feel like a dad trying to program a vcr
This post was infected with retardation. Please ignore.
goldenarmZ said:
This post was infected with retardation. Please ignore.
Click to expand...
Click to collapse
LOL
btw if your building from ASOP, it should already have root. I think you only need to add it to T-mobile OTA's
I know I hate looking at kernels. Liquefies my mind
B-man007 said:
btw if your building from ASOP, it should already have root. I think you only need to add it to T-mobile OTA's
Click to expand...
Click to collapse
It's not working for me.. I just get "permission denied"
Well I've got root by running chmod 4777 on /bin/sh, but this leaves root access wide open to everything and bypasses the confirmation check from superuser.apk... Come on devs, I could really do with a few tips here!
I think I've got it now... thanks to all the devs, you were a real help here.
goldenarmZ said:
I think I've got it now... thanks to all the devs, you were a real help here.
Click to expand...
Click to collapse
XD
i know, they are so helpful right?
Actually they never come by here anymore because of the supernoob questions
I suggest you try to pm,twitter, or website the devs. many of them are very helpful, but cannot stand noobs. as long as you do your research (like u did) you should get help
Hmmm, as I'm also building AOSP from scratch, I would have liked you to have at least posted the conclusion. I feel like several pages were ripped out of my copy of the story.
10 charact
..........
Also reserved please
This sounds like something that can kill a lot if time while I'm in the office.
What are we looking for when doing this?
Sent from my DROID BIONIC using xda premium
ROB281 said:
This sounds like something that can kill a lot if time while I'm in the office.
What are we looking for when doing this?
Sent from my DROID BIONIC using xda premium
Click to expand...
Click to collapse
Well, I'll get to the point soon. still modifying the post. but basically the gist of it is to check ALL of motorola's update servers for updates, not just the one that comes programmed into the device. If we're lucky and we find a hidden update, we may be able to get an unlocked bootloader (or other goodies?), which will allow us to use our device as we please (new kernels, better mods, etc)
Thanks for writing this up, I've been hesitant to try it since some of the paths/files in other posts did not exist on the Bionic.
Sent from my DROID BIONIC using XDA App
karthakon said:
Thanks for writing this up, I've been hesitant to try it since some of the paths/files in other posts did not exist on the Bionic.
Sent from my DROID BIONIC using XDA App
Click to expand...
Click to collapse
Well, I was bold and basically just created the files. When I ran the *#*#4636#*#* test, I found that it did indeed change my could update server.
also the com.motorola.blur.setup was in /data/data/ and not the system/etc/motorola.
Thank you.
Sent from my ADR6400L using xda premium
Thank you for this. The previous directions were based on the Atrix so there were a lot of files listed that I never saw so I felt unsafe just making them up and moving things around. I'll get on this sometime in the very near future.
K.AuthoR said:
Thank you for this. The previous directions were based on the Atrix so there were a lot of files listed that I never saw so I felt unsafe just making them up and moving things around. I'll get on this sometime in the very near future.
Click to expand...
Click to collapse
I actually have been testing some methods that may not even req a wipe in between or possible before
Sent from my DROID BIONIC using Tapatalk
Apparently someone found an update somewhere. Good sign. I'm going to check it out in an hour or two. Don't have my hands on it yet.
Sent from my DROID BIONIC using Tapatalk
Looking at these right now. I'll go ahead and update the main thread with your corrections. Thank you for figuring it out!!!!
kennethpenn said:
Looking at these right now. I'll go ahead and update the main thread with your corrections. Thank you for figuring it out!!!!
Click to expand...
Click to collapse
when I hit the server, it says it's a 5.5.886 -> 5.5.891 update
phydo said:
when I hit the server, it says it's a 5.5.886 -> 5.5.891 update
Click to expand...
Click to collapse
Just so everyone can see it: the update label will always be for the build ID that the zip is supposed to be installed over. That means if you've got an update:
Blur_Version.1.XT875.Verizon.en.US.zip --> This means the zip should be installed over devices running Build number "1."
Blur_Version.5.5.886.XT875.Verizon.en.US.zip --> This means the zip should be installed over devices running Build number "5.5.886."
Was anyone ballsy enough to attempt to install the update? It doesn't have a bootloader inside, but it may still be dangerous.
P3 flashed it and it does absolutely contain a bootloader update.
The critical pieces are the mbm.bin, mbmloader_hs.bin and mbmloader_ns.bin.
HS and NS refer to Hardware Secure and Non Secure parts and both are included in these updates because both types of hardware are present in the test groups or whomever is the intended recipient of these files.
There is not an unlock, per se, but both secured and unsecured mbmloaders are present and the updater script has a check for the ro.secure status and loads the appropriate file for the target device.
The D3 update and assumedly this file as well cannot be reverted to stock release version, so this file must be regarded very carefully and assessed before any decision to flash or not is made.
There is a LOT more discussion we need to have about these files and OMAP SoCs I think regarding the differences between them and the Tegra II SoCs and fuse arrays!
Edit: This breaks the djrbliss root method using the tcmd exploit. We need to look further and discuss with him other possibilities for root. Reverting has not been established yet and may brick since we dont have a complete XML.zip.
WARNING!!!! This is a very dangerous file to flash at this stage!!! Please do not rush into testing it yet!!!
Thanks to those who got the file and thanks to P3Droid for guinea pigging.
Oh and I have to add that clarified cheescake is an oxymoron...you garnish cheesecake with wonderful things!
cellzealot said:
P3 flashed it and it does absolutely contain a bootloader update.
The critical pieces are the mbm.bin, mbmloader_hs.bin and mbmloader_ns.bin.
HS and NS refer to Hardware Secure and Non Secure parts and both are included in these updates because both types of hardware are present in the test groups or whomever is the intended recipient of these files.
There is not an unlock, per se, but both secured and unsecured mbmloaders are present and the updater script has a check for the ro.secure status and loads the appropriate file for the target device.
The D3 update and assumedly this file as well cannot be reverted to stock release version, so this file must be regarded very carefully and assessed before any decision to flash or not is made.
There is a LOT more discussion we need to have about these files and OMAP SoCs I think regarding the differences between them and the Tegra II SoCs and fuse arrays!
Edit: This breaks the djrbliss root method using the tcmd exploit. We need to look further and discuss with him other possibilities for root. Reverting has not been established yet and may brick since we dont have a complete XML.zip.
WARNING!!!! This is a very dangerous file to flash at this stage!!! Please do not rush into testing it yet!!!
Thanks to those who got the file and thanks to P3Droid for guinea pigging.
Oh and I have to add that clarified cheescake is an oxymoron...you garnish cheesecake with wonderful things!
Click to expand...
Click to collapse
So I decided that I just couldn't sleep not knowing if the root patch had been fixed. So I decided to flash the update.zip. And what I expected to happen, happened, it zapped the local.prop exploit.
So here I sit on the new build unrooted and stock. I'm fairly certain that if I try to revert back to the OG build I will have a paper weight on my desk until a full xml fastboot file can be found. I would suggest you all wait and don't flash this yet.
jimmydafish said:
So I decided that I just couldn't sleep not knowing if the root patch had been fixed. So I decided to flash the update.zip. And what I expected to happen, happened, it zapped the local.prop exploit.
So here I sit on the new build unrooted and stock. I'm fairly certain that if I try to revert back to the OG build I will have a paper weight on my desk until a full xml fastboot file can be found. I would suggest you all wait and don't flash this yet.
Click to expand...
Click to collapse
thats what i call takin one for the team!!! thanks bro!!! You'll be rooted again in no time, maybe even s-off!!!
Enzopreme said:
thats what i call takin one for the team!!! thanks bro!!! You'll be rooted again in no time, maybe even s-off!!!
Click to expand...
Click to collapse
S-off doesn't apply to Moto products...
Sent from my DROID BIONIC using xda premium
cellzealot said:
P3 flashed it and it does absolutely contain a bootloader update.
The critical pieces are the mbm.bin, mbmloader_hs.bin and mbmloader_ns.bin.
HS and NS refer to Hardware Secure and Non Secure parts and both are included in these updates because both types of hardware are present in the test groups or whomever is the intended recipient of these files.
There is not an unlock, per se, but both secured and unsecured mbmloaders are present and the updater script has a check for the ro.secure status and loads the appropriate file for the target device.
The D3 update and assumedly this file as well cannot be reverted to stock release version, so this file must be regarded very carefully and assessed before any decision to flash or not is made.
There is a LOT more discussion we need to have about these files and OMAP SoCs I think regarding the differences between them and the Tegra II SoCs and fuse arrays!
Edit: This breaks the djrbliss root method using the tcmd exploit. We need to look further and discuss with him other possibilities for root. Reverting has not been established yet and may brick since we dont have a complete XML.zip.
WARNING!!!! This is a very dangerous file to flash at this stage!!! Please do not rush into testing it yet!!!
Thanks to those who got the file and thanks to P3Droid for guinea pigging.
Oh and I have to add that clarified cheescake is an oxymoron...you garnish cheesecake with wonderful things!
Click to expand...
Click to collapse
I suppose I was looking for the wrong things. On other devices, "ap20bl.img" was responsible for bringing such goodies as an unlock capability.
Has anybody taken a look at the new official JB release that popped up at http://sbf.droid-developers.org/cdma_maserati/list.php ? (Although, I can't access it currently)
It's been mentioned on another thread (http://forum.xda-developers.com/showthread.php?t=2277830 ) regarding the ability to root, but it doesn't look like it's been looked at in any depth whether it includes any fixes, etc. The build date has changed to the 5th April, and the version is 9.8.20-72_VZW-18-2.
Cheers,
Steve.
This should probably be in q&a section... but yeah I wonder what is in it too... either way, I'm pretty happy sitting on eclipse 1.0.6 right now
Xoom'd using the XDA-Developers Android app
alex94kumar said:
This should probably be in q&a section... but yeah I wonder what is in it too... either way, I'm pretty happy sitting on eclipse 1.0.6 right now
Xoom'd using the XDA-Developers Android app
Click to expand...
Click to collapse
You could be right regarding the location, apologies if people object - I just thought the ROM guys would probably be the ones most likely to be all over it.
File Mirror
FWIW - I found that droid-developers.org seemed a little hit and miss, so I've set up a private file mirror for this new release. If somebody wants access to it, then just PM me. I'm trying to sort out a public mirror too, and will update this post when/if I get that sorted out.
Cheers,
Steve,
I am uploading cdma_maserati/cdma_maserati_9.8.2O-72_VZW-18-2_1ff.xml.zip
to my http://d-h.st/users/sd_shadow/?fld_id=12041#files
via remote url upload, usually doesn't take very long, quite a bit faster than uploading from my pc
This same version upgrade for XT926 HD appeared and was said to be a bugfix for the 4.1.2 OTA and that another more significant update would appear shortly for all devices but still remain 4.1.2 and would include Isis.
So we should expect to see a couple of OTAs pushed out on accelerated schedule that will match this XML file and the subsequent update.
sd_shadow said:
I am uploading cdma_maserati/cdma_maserati_9.8.2O-72_VZW-18-2_1ff.xml.zip
to my http://d-h.st/users/sd_shadow/?fld_id=12041#files
via remote url upload, usually doesn't take very long, quite a bit faster than uploading from my pc
Click to expand...
Click to collapse
Nice one - I'm currently 66% of the way through uploading to FileDropper (which I've never used before, but it was free, and didn't require sign up).
cellzealot said:
This same version upgrade for XT926 HD appeared and was said to be a bugfix for the 4.1.2 OTA and that another more significant update would appear shortly for all devices but still remain 4.1.2 and would include Isis.
So we should expect to see a couple of OTAs pushed out on accelerated schedule that will match this XML file and the subsequent update.
Click to expand...
Click to collapse
So is the "more significant update" meant to be coming after this April 5th release?
Cheers,
Steve.
It's safe for now...
StevePritchard said:
Nice one - I'm currently 66% of the way through uploading to FileDropper (which I've never used before, but it was free, and didn't require sign up).
So is the "more significant update" meant to be coming after this April 5th release?
Cheers,
Steve.
Click to expand...
Click to collapse
Yes, and I just flashed the boot, system and radio images from the MR2 XML and then rerooted using razr_blade.
So, we are safe to use this file to upgrade the firmware without any loss of root or any other issues.
The secure version did not increment so it is also possible to revert to the prior -18 release without risk of soft bricking.
This follows the pattern of the update for the HD and will likely be the same for the other devices that just recieved 4.1.2 in this cycle.
The next update is the one the will include ISIS and may also have security enhancements that will need to be carefully scrutinized.
That is conjecture on my part, at this stage, we don't know.
It would be nice to know what changes the release addresses. My hope is that it sorts out the hardware keyboard problem of unsticky shift keys in some applications.
Cheers,
Steve
Hi,
Here is CM-11 (Android 4.4.4) for the kindle fire hdx 7" (THOR). You need a rooted hdx 7" (Thor) device with a firmware < 3.2.4 (3.2.3.2 ideally) and a signed recovery.
Todo
Bluetooth not working
Wifi won't correctly load when disabled at boot, a reboot is required
Minimal headphone volume too loud -> fixed
Incorrect color format in some scenario's ? (YouTube) -> fixed
Changelogs/Downloads
cm-11-20150226-UNOFFICIAL-thor.zip
Updated to amazon 4.5.3 binaries
Fully disable radio for now (thanks Andy-Voigt)
Fix twrp fstab (enabling twrp was breaking system rom to boot)
CM sources updated to 20150226
cm-11-20150219-UNOFFICIAL-thor.zip
CM sources updated to 20150219
cm-11-20150219-UNOFFICIAL-thor.zip
fix minimal video/media volume too high (youtube...)
switch back to tablet build
CM sources updated to 20150110
cm-11-20150108-UNOFFICIAL-thor.zip
Fix thermal engine (should give better battery life and performances)
Fix a lot of proprietary services (proprietary logs, acdb-loader, ril loading ...)
Set media volume steps to 100 instead 15 (allow finer volume control essentially for jack output)
Lowered minimal screen brightness
CM sources updated to 20150108
cm-11-20150107-UNOFFICIAL-thor.zip
Build without "hacks" (add Cuber signing and custom updater-script generation)
CM sources updated to 20150107
Enable telephony (will probably not work)
cm-11-20150101-UNOFFICIAL-thor.zip
use patched boot/recovery, thanks to @vortox
fix wrong color format ! (major bug resolved)
switch to kernel sources
cm-11-20141218-UNOFFICIAL-thor.zip
minors fixes
cm-11-20141217-UNOFFICIAL-thor.zip
fix wifi not reloading
fix overlay/rotation screen tearing
cm-11-20141216-UNOFFICIAL-thor.zip
updated binaries to amz 4.5.2
properly use precompiled kernel and headers (amz 4.5.2)
fix minimal audio volume too high
add safestrap compatibility
Sources
android_device_amazon_thor
android_device_amazon_hdx-common
hardware_qcom_display-caf-hdx
hardware_qcom_audio-caf-hdx
hardware_qcom_media-caf-hdx
I'm sure the community here respects all of the work that you do. My post in the other thread was not intended to "get you in trouble". There are a set of rules that every user has to follow, regardless of their contributions to the community. That being said, when I was a newer member, I accidentally broke the rules a couple of times (nothing major) and didn't want the same to happen to someone else. (I never contacted @Divine_Madcat about your other thread, in case you were thinking I did.)
r3pwn said:
I'm sure the community here respects all of the work that you do. My post in the other thread was not intended to "get you in trouble". There are a set of rules that every user has to follow, regardless of their contributions to the community. That being said, when I was a newer member, I accidentally broke the rules a couple of times (nothing major) and didn't want the same to happen to someone else. (I never contacted @Divine_Madcat about your other thread, in case you were thinking I did.)
Click to expand...
Click to collapse
Yep i was tinking to that... so I'm also sorry. The thing is i spent a lot, lot of time on this port, and Divine_Madcat didn't even give me the time to update the first thread with the needed files/informations and ignore my pm which was an offense to me. Well i have to complies to the rules too but was a little chocked on how the thread got mad. Well, let's hope it won't be the same here. So that said i have no problem with you !
Cpasjuste said:
Yep i was tinking to that... so I'm also sorry. The thing is i spent a lot, lot of time on this port, and Divine_Madcat didn't even give me the time to update the first thread with the needed files/informations and ignore my pm which was an offense to me. Well i have to complies to the rules too but was a little chocked on how the thread got mad. Well, let's hope it won't be the same here. So that said i have no problem with you !
Click to expand...
Click to collapse
While i am sorry you are upset, it was not a slight at you at all. While i do try to keep an eye on XDA while at work, my job does come first and foremost, and i was unable to handle anything here yesterday (what can i say, 12 hour work days suck). As it was, i have literally nothing against you; to be frank, the report on the thread was the first i had even seen.
From my perspective, we had a placeholder thread, which is not allowed, so it was closed. I fully intended to reopen it, but gave my reasons above...
Anyway, i do wish you luck, and i really dont have any ill will to you...
So....
Do we have unlocked bootloader or a root exploit for amazon firmware 4.5.2 soon? And do you have plan to release another for Apollo?
Thanks
tuanda82 said:
So....
Do we have unlocked bootloader or a root exploit for amazon firmware 4.5.2 soon? And do you have plan to release another for Apollo?
Thanks
Click to expand...
Click to collapse
Nobody knows. But there are a few people working on "unlocks" (at least booting an unsigned kernel). Maybe also jcase releases his unlock (which I doubt because of legal issues).
Hi!
I have rooted Kindle Thor. How do I install this nice piece of software?
Like the Nexus rom? Currently I am on 3.2.7...
Thanks
URBANsUNITED
URBANsUNITED said:
Hi!
I have rooted Kindle Thor. How do I install this nice piece of software?
Like the Nexus rom? Currently I am on 3.2.7...
Thanks
URBANsUNITED
Click to expand...
Click to collapse
You need to be on 4.5.2 and rooted.
cyablo said:
You need to be on 4.5.2 and rooted.
Click to expand...
Click to collapse
Mmmmmhhh
Than this rom is basically usless
Who has a 4.5.2 Base and Rooted??? I would do it if I'll get the tools, no fear of a brick
Too bad. But Nevertheless Many thanks for the work and effort!
URBANsUNITED said:
Mmmmmhhh
Than this rom is basically usless
Who has a 4.5.2 Base and Rooted??? I would do it if I'll get the tools, no fear of a brick
Too bad. But Nevertheless Many thanks for the work and effort!
Click to expand...
Click to collapse
There are a few Users which do have an unlocked Bootloader, this Rom is only for these Users, as stated in the first Post.
I decided to make the rom available in case i loose interest in this device (or if i ever die soon). This way when (if) a root exploit is available then you'll be ready to use it.
Ok... So if there IS a possibility to unlock the actual fireos, please give some hints, instead of publishings Roms that one or two users can install, the rest is completely helpless...
Sent from my Nexus HDX 7 using XDA Free mobile app
openWeb74 said:
Ok... So if there IS a possibility to unlock the actual fireos, please give some hints, instead of publishings Roms that one or two users can install, the rest is completely helpless...
Sent from my Nexus HDX 7 using XDA Free mobile app
Click to expand...
Click to collapse
Sharing hundreds of hours of work is helpless/useless for you ?
You know what ? I actually spent the whole day on porting cm-10 to current exploitable kernel for YOU :/
Everybody chill , @openWeb74, i see your point @Cpasjuste , first let me thank you for all your work, I'm pretty sure its a great Rom!
What openweb said was that maybe we should concentrate our efforts in unlocking the bootloader so even greater support can come.
Unfortunately we, the rest of us common mortals (with locked bootloaders) cannot use it.
As you said, this would work if somebody would release the bootloader-unlock , so lets play the waiting game...
The thing is I'm a common mortal like you :/ Like its said on first post, unfortunately, I do not have the tools nor the knowledge to reproduce the unlock, so I share what I can.
I really have to say sorry, if you dont know how to reproduce the hack... Mea culpa. It sounded like the hack is known, but cant be made public because of copyright issues or something like that... Then we have to wait. Nothing is secure when the right person gets a hdx... I have to say, that my actual hdx was rooted with towelroot, even easier than the nexus (less button combinations ) so i didnt expect amazon to be such a **** with newer firmwares.
Sent from my LG-D802 using XDA Free mobile app
Cpasjuste said:
The thing is I'm a common mortal like you :/ Like its said on first post, unfortunately, I do not have the tools nor the knowledge to reproduce the unlock, so I share what I can.
Click to expand...
Click to collapse
Sorry for nagging you about it, but — genuinely asking — how did you do it on your device in the first place?
dear Cpasjuste, thanks for your great work, and how to install this Rom ? I am newbie, so..
OK... So you are a newbie in reading too?
Sent from my Nexus HDX 7 using XDA Free mobile app
I may eventually move to another tablet as I'm loosing interest in this device (because cm is working fine [emoji14]). Would someone be interested to get my device (not for free )?
Hello everyone. Those days I feel some to root my phone (ALE-L21 6.0 Dual SIM) to install custom ROMs like LineageOS with Android Nougat and use apps like WPS WPA Tester but other some I feel not because I'm still in warranty time (it ends after 1 year + the warranty isn't in my country) and I never rooted any device or even used Android (my lase phone was Nokia 110) so today I wanna to know why root is useful and why not and what can I use it for and what's the root dangerous? I need all informations about root. :laugh:
Edit: Is all custom ROMs has bugs? Like Radio FM doesn't work, screen recorder doesn't work or even has a bug?
AmirGTX said:
I need all informations about root. :laugh:
Edit: Is all custom ROMs has bugs?
Click to expand...
Click to collapse
Root was a good thing on earlier versions of Android. Now I don't think it's a necessity.
Custom ROM's seems a good idea, but if you don't have official version from the developers I myself don't recommend it.
You can try deoxed, modified or trimmed versions of stock ROM, to get more features.
If you have a branded phone I recommend to unbrand it to obtain ROM updates easily.
I recommend to keep stock for now because we get security patches from time to time.
I think main reasons for rooting and unlocking bootloader.
1. Devices with small memory you can install apps in to SD-card.
2. If you realy hate ads you can use Adblocking.
3. Install custom ROM or kernel to get better battery life/performance (with some devices these are only stuff that isn't perfectly stable but sill stable enoughfor daily use).
4. Uninstall unessesary system apps.
5. More customizing possibilities like change screen dpi(dots per inch --> smaller value gives smaller icons and text so you can fit more stuff in screen at the same time).
6. There is more things to do but this was of the top of my head.
IMO root yes, of course, many reasons pick the ones you like most: uninstall bloatware, tweak kernel parameters, activate hidden options, xposed, greenify...
keikari said:
I think main reasons for rooting and unlocking bootloader.
1. Devices with small memory you can install apps in to SD-card.
2. If you realy hate ads you can use Adblocking.
3. Install custom ROM or kernel to get better battery life/performance (with some devices these are only stuff that isn't perfectly stable but sill stable enoughfor daily use).
4. Uninstall unessesary system apps.
5. More customizing possibilities like change screen dpi(dots per inch --> smaller value gives smaller icons and text so you can fit more stuff in screen at the same time).
6. There is more things to do but this was of the top of my head.
Click to expand...
Click to collapse
1. I use my device currently and needn't more space.
2. I already have Adguard, it's enough for me.
3. Yes, I've bored from the stock Android theme and want to change it.
4. I needn't to remove system apps because I don't even use them.
5. IDK what's this obviously. :laugh:
6. What else?
fosco_ said:
IMO root yes, of course, many reasons pick the ones you like most: uninstall bloatware, tweak kernel parameters, activate hidden options, xposed, greenify...
Click to expand...
Click to collapse
What's IMO? What's bloatware? What's tweak kernel? What's all this? :silly:
AmirGTX said:
1. I use my device currently and needn't more space.
2. I already have Adguard, it's enough for me.
3. Yes, I've bored from the stock Android theme and want to change it.
4. I needn't to remove system apps because I don't even use them.
5. IDK what's this obviously. :laugh:
6. What else?
Click to expand...
Click to collapse
Well I forgot to tell most important reason, because you can : D
Nowdays that's prety much all the stuf that matters for regular user.
Maybe bagroundplayback for youtube if it isn't already possible with regular app.
And it's kind of a plus that you can back backup your full system in TWRP, thought main reson for backups is that you are testing something unstable or new stuff which you can only do with unlocked bootloader.
PS. Your logic in 4 is kind of weird XDD
And dpi is kind of like resolution of screen but still very different but you can think of it as a weird resolution setting
Azzureux said:
Root was a good thing on earlier versions of Android. Now I don't think it's a necessity.
Custom ROM's seems a good idea, but if you don't have official version from the developers I myself don't recommend it.
You can try deoxed, modified or trimmed versions of stock ROM, to get more features.
If you have a branded phone I recommend to unbrand it to obtain ROM updates easily.
I recommend to keep stock for now because we get security patches from time to time.
Click to expand...
Click to collapse
Can you explain more? I didn't got it :cyclops:
AmirGTX said:
What's IMO? What's bloatware? What's tweak kernel? What's all this? :silly:
Click to expand...
Click to collapse
Are you kidding?
IMO = In My Opinion
bloatware = preinstalled apps you don't want but can't remove
tweak kernel = change kernel parameters such as min/max speed, governor, i/o scheduler, gpu speed and so
AmirGTX said:
Can you explain more? I didn't got it :cyclops:
Click to expand...
Click to collapse
I'll try to be brief.
First I rooted my Samsung Galaxy S plus, android version was 2.3.6. Was a good thing? Yes, I had good devs who not only made Rom's up to Lollipop (I use now KitKat on it) but also repartitioned the space available through Twrp giving me more space for apps.
My next one was Galaxy S3 mini, android version was 4.1. I rooted it. Was a good thing? Yes and No.
Yes was good because I could use apps for backup, to remove bloatware, and posible to try custom ROMs.
No... Because I didn't had good developers, every custom ROMs had issues. That made me feel cautious and only installed stock ROM's that gave me more personalization and stable use of the phone (that doesn't mean I don't have problems with it, but it's mostly caused by apps who are not 100% compatible with KK ROM's).
Now let's talk about P8 Lite.
1. Can I squeeze more time of use from battery? Yes, we got the option <Ultra battery>.
2. Can I disable bloatware? I can't remove apps but I can disable them (MM has an option for it).
3. Can I backup apps and data? Yes. We got an option for it.
4. Can I get security updates for my ROM? Yes, for now we get security updates from Huawei.
5. Can I customize my ROM? To a point... Yes, you can customize the interface through themes, and the theme itself using other apps.
6. Can I get Nougat (version 7 of Android).
No, and you can start blaming Google for the requirements asked for it.
Yes, if you buy the 2017 version of the phone.
Sorry I was not brief. :good:
fosco_ said:
Are you kidding?
IMO = In My Opinion
bloatware = preinstalled apps you don't want but can't remove
tweak kernel = change kernel parameters such as min/max speed, governor, i/o scheduler, gpu speed and so
Click to expand...
Click to collapse
Oh alright +1, why I need root else? (I'm just collecting info b4 rooting my device)
Azzureux said:
I'll try to be brief.
First I rooted my Samsung Galaxy S plus, android version was 2.3.6. Was a good thing? Yes, I had good devs who not only made Rom's up to Lollipop (I use now KitKat on it) but also repartitioned the space available through Twrp giving me more space for apps.
My next one was Galaxy S3 mini, android version was 4.1. I rooted it. Was a good thing? Yes and No.
Yes was good because I could use apps for backup, to remove bloatware, and posible to try custom ROMs.
No... Because I didn't had good developers, every custom ROMs had issues. That made me feel cautious and only installed stock ROM's that gave me more personalization and stable use of the phone (that doesn't mean I don't have problems with it, but it's mostly caused by apps who are not 100% compatible with KK ROM's).
Now let's talk about P8 Lite.
1. Can I squeeze more time of use from battery? Yes, we got the option <Ultra battery>.
2. Can I disable bloatware? I can't remove apps but I can disable them (MM has an option for it).
3. Can I backup apps and data? Yes. We got an option for it.
4. Can I get security updates for my ROM? Yes, for now we get security updates from Huawei.
5. Can I customize my ROM? To a point... Yes, you can customize the interface through themes, and the theme itself using other apps.
6. Can I get Nougat (version 7 of Android).
No, and you can start blaming Google for the requirements asked for it.
Yes, if you buy the 2017 version of the phone.
Sorry I was not brief. :good:
Click to expand...
Click to collapse
Awesome, that's why I want to root it but I'm still waiting until LineageOS be available and stable without bugs for me. I bought my phone last year and updated it to MM 6.0 at 7 month of last year, now I have UPDATE.APP (got it from here) it has no bugs and too stable for me. So I saw tutorials here for rooting my device but it were too much big and I need to use my computer. NP if I used my computer but can't I root it using apps suck as KingRoot and then install the ROM? Also I want to know all thing about bootloader and unlocking it and all thing in this operation. I want to know to be deep for such as problems. Thanks for info
AmirGTX said:
Also I want to know all thing about bootloader and unlocking it and all thing in this operation.
Click to expand...
Click to collapse
Few years ago, when we could not imagine that phones can get ROM updates, no one bothered about bootloaders. But after few years they were shocked to see old clients use same depleted phones with new ROM's.
If you look back, when Google started to release Android 3 and up, we can see that the manufactures didn't try to much to improve "the smartphones", the selling ideology was the same as before, manufactures imagined just few improvements for the new models.
But then iPhone appeared, Samsung Galaxy smartphone line appeared and rules changed. Everyone tried to sell smarter phones on the market, Apple had a closed system so everyone looked at Google and android delivered.
So after the "Wild West" period, manufactures wanted more control over their devices, don't forget that devices had hardware in many configurations, so to prevent bricked phones, to try to stop clients from destroying their devices and after ask for guaranty, bootloaders were invented. It's a compromising way for users to obtain root access and avoid warranty claims.
Now, we see that Google stepped a bit, with Android 7, by limiting the compatibility asking for minimum hardware from manufactures. It's a way to make clients buy new devices. Same thing we saw at Microsoft when it released Vista and up. It's a good way for manufactures to stop companies like CM to make unwanted ROM's updates. At the beggining CM ROM's where 100% bug free, but now we can't say the same. Manufactures don't release drivers for hardware so developers to implement new versions of Android on old devices.
For me the only viable option for ROM updates is stock modifications that try to remove restrictions in the software available thru all the world.
But why is Huawei giving a legal way to unlock the bootloader? It's a very easy way to see who still got guaranty and who is out of guaranty. And also it's a way to keep clients close by getting ROM updates faster, it's basically a removal of the middle man (manufactures can't live without firms that do installment sales) a way to increase the overall sales.
Imagine a person who needs a smartphone but can't afford it. Carriers can give devices for less, manufactures get the full price, and carriers get the whole price with interest over a limited period. And now manufactures have a problem, they need to keep clients of carriers happy, and need to push updates on the devices. Carriers see this as a loss of control, but can't make the manufacturer to keep the system closed. So for legal requirements bootloaders were invented.
You can ask for root, but manufactures and Google is giving secure control over the devices, that basically do same thing as apps that required root.
My final advice: if you don't plan to learn about android ROM development, if you don't plan to be a developer, then don't root. Wait until you get a new device, maybe with the new iteration of ROM. If you see something you like, then you can start learning and start developing.
:silly: can't believe i wrote so much. Happy reading and good luck.
Azzureux said:
Few years ago, when we could not imagine that phones can get ROM updates, no one bothered about bootloaders. But after few years they were shocked to see old clients use same depleted phones with new ROM's.
If you look back, when Google started to release Android 3 and up, we can see that the manufactures didn't try to much to improve "the smartphones", the selling ideology was the same as before, manufactures imagined just few improvements for the new models.
But then iPhone appeared, Samsung Galaxy smartphone line appeared and rules changed. Everyone tried to sell smarter phones on the market, Apple had a closed system so everyone looked at Google and android delivered.
So after the "Wild West" period, manufactures wanted more control over their devices, don't forget that devices had hardware in many configurations, so to prevent bricked phones, to try to stop clients from destroying their devices and after ask for guaranty, bootloaders were invented. It's a compromising way for users to obtain root access and avoid warranty claims.
Now, we see that Google stepped a bit, with Android 7, by limiting the compatibility asking for minimum hardware from manufactures. It's a way to make clients buy new devices. Same thing we saw at Microsoft when it released Vista and up. It's a good way for manufactures to stop companies like CM to make unwanted ROM's updates. At the beggining CM ROM's where 100% bug free, but now we can't say the same. Manufactures don't release drivers for hardware so developers to implement new versions of Android on old devices.
For me the only viable option for ROM updates is stock modifications that try to remove restrictions in the software available thru all the world.
But why is Huawei giving a legal way to unlock the bootloader? It's a very easy way to see who still got guaranty and who is out of guaranty. And also it's a way to keep clients close by getting ROM updates faster, it's basically a removal of the middle man (manufactures can't live without firms that do installment sales) a way to increase the overall sales.
Imagine a person who needs a smartphone but can't afford it. Carriers can give devices for less, manufactures get the full price, and carriers get the whole price with interest over a limited period. And now manufactures have a problem, they need to keep clients of carriers happy, and need to push updates on the devices. Carriers see this as a loss of control, but can't make the manufacturer to keep the system closed. So for legal requirements bootloaders were invented.
You can ask for root, but manufactures and Google is giving secure control over the devices, that basically do same thing as apps that required root.
My final advice: if you don't plan to learn about android ROM development, if you don't plan to be a developer, then don't root. Wait until you get a new device, maybe with the new iteration of ROM. If you see something you like, then you can start learning and start developing.
:silly: can't believe i wrote so much. Happy reading and good luck.
Click to expand...
Click to collapse
Extremely awesome and thanks a lot. I want to start to learn about root but IDK from where can I start! There are no way to root any Android emulator and learn from it or executing on main device would be more stable?
IMO, root device it's a personal choice, the important question is:
There's something that you want to do and you can't because you need root?
To install custom rom you don't need root, you have to unlock bootloader, install a custom recovery (TWRP) and finally you can flash you custom rom (generally already rooted!)
ItalianWolf said:
IMO, root device it's a personal choice, the important question is:
There's something that you want to do and you can't because you need root?
To install custom rom you don't need root, you have to unlock bootloader, install a custom recovery (TWRP) and finally you can flash you custom rom (generally already rooted!)
Click to expand...
Click to collapse
Ciao amico mio ? (some Italian from school ?) can you give me a tutorial for this? I need to try. Also why there are a lot of stuffs to root ALE-L21? What if I used apps such as KingRoot?
Ciao!
Kingroot, if it's working again, isn't a good root solution; i've tried (we were with lollipop) but messed up a lot of things so i had to re-flash stock firmware.
https://forum.xda-developers.com/p8lite/general/mega-thread-root-unbricking-updating-t3400994
Yes for :
Tweak kernel, install AdAway and remove preinstalled apps.
personally for me is a must, i just do much things with root, anyways you could say i'm an advanced user of android so i need root, if you are good with your phone as it is, or a newer user of android, you don't need to root
panchovix said:
personally for me is a must, i just do much things with root, anyways you could say i'm an advanced user of android so i need root, if you are good with your phone as it is, or a newer user of android, you don't need to root
Click to expand...
Click to collapse
I don't like normal things, I need to be special that's why I think to root my device. I'm neither pro nor newer. So I need to know if I rooted my device what will I do else custom ROMs and block ads and remove system apps?