Hi
I had the day off, and decided to have a play with the Kitchen to see what I could come up with. After following the instructions on theunlockr.com I decided to base my rom on the OpenFire v.2.3 rom. Any issues that rom had, mine will have.
I have added a few things and changed a couple of things, but in the end, this is my first rom for a device I do not have myself. I have an HTC Desire, but noticed that the Wildfire isn't getting as much love, hence that choice. I hope to get a better understanding of what it takes to make a proper custom rom at some time in the future.
Removed:
Launcher2
Added:
Launcher Pro
Titanium Backup
Rom Manager
Fancy Widget
From the OpenFire v.2.3 post:
NO HTC APPS DO NOT WORK ON THIS ROM AND I WONT TRY TO PORT THEM (but if you try and suceed please tell me and I will maybe include them!)
This ROM is from the android source there is no HTC apps or extra apps from the start it do come with spareparts and dev tools from android source. At the moment it seems a bit slow I think that is due to animations, animations can be turned of in spareparts or in the settings menu.
Features:
- Froyo aosp 2.2.1
- Root + superuser app
- Busybox
- No htc apps!
- Some google apps
- Multi language
- Darktremor Apps2SD
- Patched market
- Usb & WIFI-thetering
- JIT
- 3 in 1 reboot menu
- It may make your phone explode! (You have been warned)
Bugs / Not working:
- Video recording working (but, bad quality)
- Cant import contacts from SIM ? no read/write acess to SIM ? (can anyone confirm or deny this?)
TODO:
- Get rid of above bugs
- HTC-camera (maybe)
Thanks to:
HCDR.Jacob - for the kernel and vendor
Yopsi - for sharing package with google apps.
danne_jo - for APN stuff, and for hosting to my ROM
Sympnotic - For his patched market app
AnantK123 - For pointing out a fix for the camera app
acavella - For hosting / making a homepage dedicated just for OpenFire
Notes:
NO HTC APPS DO NOT WORK ON THIS ROM AND I WONT TRY TO PORT THEM (but if you try and suceed please tell me and I will maybe include them!)
To get app2sd to work you need an ext partition when you have that you might have todo a full wipe and reflash the ROM to get app2sd to work
When you boot up first time choose "com.android.provision"
Anything you want to know about OpenFire can be found at the OpenFire website.
CFH [Wildfire] v1.0 Fault Log
Download:
CFH [Wildfire] v1.0.zip (58 MB)
Due to posting restrictions, I am unable to post links to the Rom. I will post it as soon as possible.
In the mean time, please leave comments below.
Thanks
Chronicfathead
Reserved for future use
Reserved for future use
What did you change? We don't need roms like those. Everyone can customize his installed rom like he wants.
Why don't you stick to a phone you have and help projects that just need help instead of reinventing the wheel over and over again?
no offense, just my personal oppinion
bl1nkk said:
What did you change? We don't need roms like those. Everyone can customize his installed rom like he wants.
Why don't you stick to a phone you have and help projects that just need help instead of reinventing the wheel over and over again?
no offense, just my personal oppinion
Click to expand...
Click to collapse
None taken.
I've had my desire for a while, and decided to root it about a month ago. I have now installed a custom rom, and I'm enjoying the fiddling around. I don't have too much knowledge, apart from experiences gained in the last week or so.
I tried talking a colleague into installing a custom rom, but he said there weren't too many for the Wildfire, so I said I'd have a play. I'm treating it as a learning curve, as I've always been interested in programming, but never really had the time. I have created a (very) small program for the Mac, and have written a few batch files but thats as far as I've taken it.
In an afternoon I've set up a Linux VM, installed all the needed software and had a play to see what I can realistically do. I see this as a first step. I'm trying to talk the wife into a Wildfire so I can have one to play with!
If the consensus is I should delete the thread, then so be it.
Chronicfathead.
I have been using aosp's rom v13, within it there are the googleemail and googleexchange apk's
within rom v21 those have been replaced with email and exchange apks
i have ran CRC checksums on those two versions and they're both the email and exchange apks are different between them. The v21 file sizes are substantially bigger but nothing in the change log tells us why.
the gapps from koushes ics thread has different crc's for those apks than aosp's v13 or v21; they don't match either of aosp's included apks.
This could all be nothing but I think we need an answer here.
Can someone talk about what's going on here? Since these are GAPPS they are the most sensitive apps, I'm sure people will get mad for me making a thread about this but I'm honestly surprised no one has questioned this earlier. I trust the dev's, otherwise I wouldn't be here flashing their roms, but that doesn't mean I shouldn't be able to question something like this openly either. I just want to understand why the email apk and exchange apk are so different from rom to rom within the same dev as well as why they're different from dev to dev when they share the same version.
Thanks
You have my support. I would like to know what the explanation is. I don't assume any I'll intent but it is a valid concern.
I looked at each apk content and there are some extra images in aosp version and the manifest file also but I don't think it was him putting it there. My best guess would be that he compiled it using different options.
If I'm not mistaken, email.apk is part of android os and therefore source is available. When compiling from source, not all files will come through the same.
I would still prefer that Jim stops by this thread and explain why his version is different. I'm sure he has a reason.
...and still no reply? Can anyone reach out?
I'd suggest going to the dev's thread, asking the question and linking to this thread.
Did that to no avail. I'm back to gingerbread.
Will someone get access to my emails, etc.? Some fill me up on this? Please.
You can set different levels of compression when making the APK files. Some devs remove stuff and others add, no two will be exactly the same.
Use apktool to decompile the packages and then beyond compare to compare to see the difference.
Most devs deodex the packages so they will be larger when compared to a Nexus dump from Google that has the odex files.
I have checked out most ICS ROMs in this forum and nothing fishy like that is going on. I always look at the ROMs before installing just to be safe.
AndroidUser00110001 said:
You can set different levels of compression when making the APK files. Some devs remove stuff and others add, no two will be exactly the same.
Use apktool to decompile the packages and then beyond compare to compare to see the difference.
Most devs deodex the packages so they will be larger when compared to a Nexus dump from Google that has the odex files.
I have checked out most ICS ROMs in this forum and nothing fishy like that is going on. I always look at the ROMs before installing just to be safe.
Click to expand...
Click to collapse
Thank you! I don't know how to use apktools so I just want to be clear...you've looked at the apk for email and exchange for both the v13 and v19 vs what's included in the gapps from koush and you've determined that they're all actually the same?
For what it's worth, if the dev uses a different system key to sign everything, it will cause the checksums to be off. ODex vs DeODex (Optimized vs nonoptimized) can very easily double things in size. Nothing creepy about that.
In addition, Mail and Exchange are not part of GAPPs, they're part of system apps, meaning the source for them are released (as opposed to GAPPs). This means they go through the compilation steps just the same as the rest of ICS.
Hi, I'm a Korean Developer.
Recently Samsung has released android 5.0 lollipop for our devices.
But most of you may be ambarrased because the lollipop upgrade changed lots of things in system.
So I researched few days about it, and I've got several informations.
All of what I explain here is the result of my experiments.
In developers discussing forum, famous developers were discussing about "How we can mod lollipop system files".
Thanks to qwerty123258, Softdx's lollipop de-odexing tool has been known to here. But the problem is that how to re-odex the de-odexed apps,frameworks.
As our common sense, ART doesn't support de-odexed apks,jars so we have to re-odex them. But many of you may think we can't re-odex animore with the way we have used.
I agreed it at first.
So I've heard that de-odexed SecSettings,SystemUI apk with Softdx's tool don't work and have FCs. Thinking like this, we can think there is no solution. Especially, lots of custom ROM developers cannot make ROM without smali modding.
BTW, I saw that mods for nexus devices' lollipop are mostly de-odexed. But there is no problem.
Hold on, the ART definitely doesn't support de-odexed mods, but why mods for nexus doesn't have matter? You may think this doesn't make sense.
So I had doubt to this 'common thinks'.
And one day, I was putting Galaxy Note3's apps into my system that worked on KK.
FlashAnnotate app had FC, and Action memo popup also had FC. But the main app and widget of Action memo worked well.
Moreover, SuperSU that I used when rooting my S5 was also de-odexed app.
Isn't it strange to say "ART doesn't support de-odexed"? So I thought that Google didn't fully removed dalvik, they just inactivated it.
So I replaced the FlashAnnotate app with the one for Note4, and it worked well.
Then I put Note4's apps like S Note, Weather Widget, etc. As I expected, all of them worked with no FC!
Thus, it is wrong to say that the ART doesn't support de-odexed. It is the problem of that app.
What problem?
I asked to one of my friend, a Note3 mod-developer. He said that stock Note3 doesn't support ART natively.
This means that the developers of Note3's stock apps didn't care ART.
It has the same principle with the issue that the old version of stock apps like S health have FC on Galaxy S5 lollipop.
The structure of app's source code have to match with ART's structure.
In short, de-odexing have no relation with ART. FC issue is the compatibility issue of that app.
So the apps of after-KK-released-devices can be worked whether it is de-odexed or not.
Is this mean apps with FC cannot be used on lollipop? No. We can modify it to match with ART's structure. I mean, we can port it as API21(lollipop).
Let me pass to the other subject.
Most of you may think that re-odexing as the way we used, extracting dalvik-cache in the phone cannot be used and we must convert it as oat.
But, I re-odexed the main app of Action memo,what worked well even it was de-odexed, as the way we used.
It also works well while it is re-odexed.
Therefore, we can re-odex apps with the way we used.
BTW, as mentioned before, stock Settings and SysUI don't work when they're de-odexed and re-odexed.
It doesn't make sense according to the theories before. Then, what's the problem?
There is one that most of you may overlooked.
When you're de-odexing with Softdx's tool, generally most of you may think converting oat to dex is important and baksmaling/smaling process must be worked well.
But the problem was in baksmaling/smaling process.
When I was de-odexing stock settings app with Softdx's tool,
(look at the attached 1.png because I cannot insert image)
There were errors on smaling process. But I've never modded any smali of it.
When I looked the codes that made errors, not recognizing the '+'s on the pswitch code.
(look at the attached 2.png because I cannot insert image)
like this.
Many smali modders may know that there was no '+' on pswitch code when modding smali of KK or lower versions.
But after I remove all that '+', it can be compiled well but it has FC. Why? literally "It was modded".
It is reasonable to have FC because it was "modded", not compiled without modifications.
We can think of these two cases:
1. The structure of app's source code was entirely changed, so the last (bak)smali tool cannot recognize changed codes.
2. The structure of app's dex was entirely changed, so vanished parts are made when baksmaling with last tool.
We can conclude with these two cases.
After the release of (bak)smali tool that can completely baksmali/smali, we can do modifications.
I've heard that the developer of apktool is going to release new version for lollipop. So we have to wait a little bit.
Although we cannot do smali modding yet, we can put apks in system.
Why don't you put several apps in system and confirm what works or not?
Anyway, Thank you for reading my bad English...ahaha
If you have another opinion for my think, reply it.
Wow really much thnx for this!!
Presently: T-Mobile-Polska ROM (4.4.2 KitKat, Build ID: KOT49H) flashed 24-03-2015y.
Well customized, rooted, well tuned up with Xpose instaler modules etc., frozen bloatware
For several months it is proposed to update for a reason: Security Fix!
Is it worth updating at all? As such a "security fixes" used to mean user couldn't customize or tune OS, you could hardly detect any other difference!
However, what is the latest or simply the best ROM for the 64bit device?
(And where to download from?)
No matter stock or custom, just it needs fully work and has some nice "state of the art" builtin functionality
The other facilities will be acquired through the means above mentioned: root, Xpose, 3Ctools and some neat tools available on the market.
Possibly half of the stock system apps are just bloatware, so 3Ctools will help to cleanup them
You might try to ask the tech support what is in this update for example the MMS fix surely feels like must have (well known by now mms bug allowing to execute a code send by mms) but if that something you could manage to dodge on your own then just ignore it.
About the ROM with some nice looks n feels well we don't have any TBH we don't have any so called "daily driver" at all but I can suggest installing a custom launcher some of the more liked ones were on sale not so long ago you just have to track the app sales
I don't suggest any cause I don't know the forum rules regard the advertising.
Edit: There's Cyanogenmod 12 but it's bugged, not something u want to use daily.
ioy said:
Presently: T-Mobile-Polska ROM (4.4.2 KitKat, Build ID: KOT49H) flashed 24-03-2015y.
Well customized, rooted, well tuned up with Xpose instaler modules etc., frozen bloatware
For several months it is proposed to update for a reason: Security Fix!
Is it worth updating at all? As such a "security fixes" used to mean user couldn't customize or tune OS, you could hardly detect any other difference!
However, what is the latest or simply the best ROM for the 64bit device?
(And where to download from?)
No matter stock or custom, just it needs fully work and has some nice "state of the art" builtin functionality
The other facilities will be acquired through the means above mentioned: root, Xpose, 3Ctools and some neat tools available on the market.
Possibly half of the stock system apps are just bloatware, so 3Ctools will help to cleanup them
Click to expand...
Click to collapse
There's only 1 rom available for the 64 bit and that's the one patrik made the cm12 and it has a good amount of bugs so it's not suggested as a daily driver yet. Nothing else but that and stock.
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?