Related
As most of you know, the bootloader unlock server for the rest of the world is down and Lenovo is not fixing it and even worse they are not even giving us updates on the issue. This has been going on for 1 month and 10 days now, longer than most of us are willing to wait. A lot of users already sold their phones and bought new ones but for us who decided to stay, we are at the mercy of Lenovo. This is why the petition is started, we want to unlock the bootloader and at least an official statement.
Even if you already unlock your device, please help us, by taking 5 minutes to sign this petition so we can apply pressure on Lenovo. The more the better so please share this post with your friends, family and the internet (Reddit, web forums, etc.)
https://www.change.org/p/lenovo-lenovo-deny-possibility-of-unlocking-phone-s-bootloader
Any help is welcomed.
Personal note :
As a broke student, I can't afford to buy a new phone so this is the only way for me to try to get Lenovo to fix the issue as soon as possible. I really do appreciate any help we receives.
Done ✌
ykcmaster said:
As most of you know, the bootloader unlock server for the rest of the world is down and Lenovo is not fixing it and even worse they are not even giving us updates on the issue. This has been going on for 1 month and 10 days now, longer than most of us are willing to wait. A lot of users already sold their phones and bought new ones but for us who decided to stay, we are at the mercy of Lenovo. This is why the petition is started, we want to unlock the bootloader and at least an official statement.
Even if you already unlock your device, please help us, by taking 5 minutes to sign this petition so we can apply pressure on Lenovo. The more the better so please share this post with your friends, family and the internet (Reddit, web forums, etc.)
https://www.change.org/p/lenovo-lenovo-deny-possibility-of-unlocking-phone-s-bootloader
Any help is welcomed.
Personal note :
As a broke student, I can't afford to buy a new phone so this is the only way for me to try to get Lenovo to fix the issue as soon as possible. I really do appreciate any help we receives.
Click to expand...
Click to collapse
why were u a lazy azz when u had time to unblock ,whose responsibility was it to unblock??
isnt it a unwritten rule or a rule of thumb that mobile enthusiasts or custom ROM lovers to root their phone after 30-40 days of use . there is no way that lenovo is going to keep servers on again ....enough said i done my part have signed up for petition
CHAMUNDA RAM said:
why were u a lazy azz when u had time to unblock ,whose responsibility was it to unblock??
isnt it a unwritten rule or a rule of thumb that mobile enthusiasts or custom ROM lovers to root their phone after 30-40 days of use . there is no way that lenovo is going to keep servers on again ....enough said i done my part have signed up for petition
Click to expand...
Click to collapse
Warranty my friend, not everyone have the money to repair their phone if it breaks. Plus I didnt think of unlocking because there arent many trusted source of rom but since lineageos was released I wanted to unlock it.
Thanks btw
Done
it's online again
tested from Egypt
and finally I'm able to unlock the bootloader
ykcmaster said:
Warranty my friend, not everyone have the money to repair their phone if it breaks. Plus I didnt think of unlocking because there arent many trusted source of rom but since lineageos was released I wanted to unlock it.
Click to expand...
Click to collapse
"Trusted sources of roms"
What's that meant to mean? Subham and firelord have made many stable Oreo roms already
b50corei5 said:
"Trusted sources of roms"
What's that meant to mean? Subham and firelord have made many stable Oreo roms already
Click to expand...
Click to collapse
It meant what it meant. Stable != secure. I am just taking possible security steps. If it was an android expert I would have read the code and compile the roms myself if it wasn't bothersome.
ykcmaster said:
It meant what it meant. Stable != secure. I am just taking possible security steps. If it was an android expert I would have read the code and compile the roms myself if it wasn't bothersome.
Click to expand...
Click to collapse
-_-
Mate, these roms are all 100 percent stable
Why lenovo do that **** bootloader server unblock, it's bad for us it's bad for them, more people who unlock bootloader is less people with warranty.
Maybe someone have a method to force unlock the bootloader, infortunately I can't help mine is already unlocked.
Petition signed, hope it help !
b50corei5 said:
-_-
Mate, these roms are all 100 percent stable
Click to expand...
Click to collapse
Hey, no they are not. Are you claiming that every ROM ever posted on this forum is 100% stable? If so I'd like to see you support your claim.
Silliarse said:
Why lenovo do that **** bootloader server unblock, it's bad for us it's bad for them, more people who unlock bootloader is less people with warranty.
Maybe someone have a method to force unlock the bootloader, infortunately I can't help mine is already unlocked.
Petition signed, hope it help ![/QUOTE
The issue is already fixed
Click to expand...
Click to collapse
ykcmaster said:
Hey, no they are not. Are you claiming that every ROM ever posted on this forum is 100% stable? If so I'd like to see you support your claim.
Click to expand...
Click to collapse
Yes I am.
Los 14.1 is the same if not worse stable then roms from firelord/subham
b50corei5 said:
Yes I am.
Los 14.1 is the same if not worse stable then roms from firelord/subham
Click to expand...
Click to collapse
https://forum.xda-developers.com/lenovo-p2/development/7-1-2-beanstalk-rom-lenovo-p2-t3614921
This rom is in beta not stable. You lose.
oh and just incase, here is the latest rom from subham
https://forum.xda-developers.com/lenovo-p2/development/rom-lineageos-15-1-t3787299
Surprise, surprise, it is beta not stable.
stable != secure
and
there is never a 100% in everything, even if all the roms here are in stable status, it will never achieve 100% stability.
LineageOS 14.1 is better than the rest of the unofficial roms here because
1. The code have been audited.
2. The images are compiled by a trusted source (LineageOS team), unlike the rest of the rom here which is mostly compiled on someone's computer then uploaded to a hosting site.
3. It is stable enough to be an official rom.
ykcmaster said:
https://forum.xda-developers.com/lenovo-p2/development/7-1-2-beanstalk-rom-lenovo-p2-t3614921
This rom is in beta not stable. You lose.
oh and just incase, here is the latest rom from subham
https://forum.xda-developers.com/lenovo-p2/development/rom-lineageos-15-1-t3787299
Surprise, surprise, it is beta not stable.
stable != secure
and
there is never a 100% in everything, even if all the roms here are in stable status, it will never achieve 100% stability.
LineageOS 14.1 is better than the rest of the unofficial roms here because
1. The code have been audited.
2. The images are compiled by a trusted source (LineageOS team), unlike the rest of the rom here which is mostly compiled on someone's computer then uploaded to a hosting site.
3. It is stable enough to be an official rom.
Click to expand...
Click to collapse
Mate, I don't think you get how it works. Beta does not affect stability or not. Everything that works in los 14.1 works in subham/firelords roms.
Point 1 is absolutely bullcrap, I suggest you do some research.
Point 2 is bullcrap too. The thing that complied the rom doesn't affect the rom. Mike compiles on a computer as well. You think he has a supercomputer or what?
Point 3 doesn't matter. Official is just a tag.
b50corei5 said:
Mate, I don't think you get how it works. Beta does not affect stability or not. Everything that works in LOS 14.1 works in subham/firelords ROM.
Point 1 is absolutely bullcrap, I suggest you do some research.
Point 2 is bullcrap too. The thing that complied the ROM doesn't affect the ROM . Mike compiles on a computer as well. You think he has a supercomputer or what? Point 3 doesn't matter. Official is just a tag.
Click to expand...
Click to collapse
The status does mean something. It means that is is not stable enough to have the status stable. How could a buggy software be considered stable?
Point 1 : What do you think Gerrit and Open Source is for? https://wiki.lineageos.org/usinggerrit-howto.html
Point 2 : You missed the point here. It is not what compiles it. It is who. Just because the source is clean doesn't mean the build is clean. Assuming you trust the developer, A lot of the ROM here don't even provide PGP keys for you to check if the ROM is unmodified in transit! How could that be secure? https://android.stackexchange.com/questions/189063/how-can-i-trust-roms
Point 3 : There are requirements to be an official ROM. One of it is be stable enough. https://wiki.lineageos.org/submitting_device.html
Please do some research and have some common sense before you open your mouth.
So far you have not supported your claims that all the ROM on this forum are 100% stable. You can never prove that point because nothing is ever 100% even if all ROM here are stable.
I know the first comments on this post will be the pessimistic "if you are asking all these questions, then you will not be able to do this" type.. however, if that is the case, how did all the developers learn to build custom ROMs for their devices? They must have learnt from somewhere or by their own trial and error.. therefore they can share their knowledge if willing to do so.
My question is about the building of a custom ROM e.g. LineageOS for an unsupported device which has no device tree or anything of the sort, such as a BLU Studio X Plus.
I know the basic commands.. But I'm not sure of the full process for creating the necessary blobs for my device(s).
I am aspiring to be a developer myself, but need someone to teach me. If any of you are willing to assist me in my endeavour, comment down below, or you can even privately message me.
Any assistance will be greatly appreciated!
Alando123 said:
I know the first comments on this post will be the pessimistic "if you are asking all these questions, then you will not be able to do this" type.. however, if that is the case, how did all the developers learn to build custom ROMs for their devices? They must have learnt from somewhere or by their own trial and error.. therefore they can share their knowledge if willing to do so.
My question is about the building of a custom ROM e.g. LineageOS for an unsupported device which has no device tree or anything of the sort, such as a BLU Studio X Plus.
I know the basic commands.. But I'm not sure of the full process for creating the necessary blobs for my device(s).
I am aspiring to be a developer myself, but need someone to teach me. If any of you are willing to assist me in my endeavour, comment down below, or you can even privately message me.
Any assistance will be greatly appreciated!
Click to expand...
Click to collapse
They started by starting with smaller, less complicated developments/modifications to get some basic understanding. Then they started spending more time doing more diligent research, reading, reading again then reading again than they did spending time asking questions.
As for the "sharing their knowledge" for others to learn.... Well, that is exactly why there are hundreds or even thousands of guides and threads on the various types of android custom development on many different websites and forums. The issue you are having is based in the fact that all of the guides are written with an assumption that the reader already has some form of intermediate programming knowledge, they are not written for the proverbial "noob". Another factor is that none of the guides are an "all-in-one, everything you need to know from start to finish" type of guide, this is because there are too many differences in the various android versions, hardware architectures, SDK versions, APIs and etc. to make a guide complete enough for general usage on every type of device, there are specific things involved that make that an impossible task. So don't get your hopes up about some kind of miracle answer that takes the pain and hard work out of your journey.
Study the guides, start small, get good at what you start with, then work your way up, starting with trying to build something like a ROM with no previous programming experience, is not a good idea for a starting point.
There is no shortage of people coming to XDA wanting to be developers and asking for someone to help teach them, it just doesn't work that way, you gotta be willing to put the time into learning and figuring out at least 95% of it on your own, that is how they learned, why should it be any different for you. The cold reality is, those that truly desire it, seek it diligently without reaching out for a hand to do the "real" work for them, the ones that succeed and excel are the ones that climb the ladder themselves with very little help from the outside because they reach inside of themselves and apply themselves to their goal without quitting or losing heart or saying "this is too hard, help me".
First of all, it depends on whether the stock source code is available for your device, if there is no stock source code available to the public(no, I'm not talking about the stock firmware file), then you will not be able to build a custom ROM from source for your device, which means that you won't be able to build anything like LineageOS because setting up the device tree requires the stock source code. No source code=no device tree, no device tree=no LineageOS or AOSP ROMs. Devices that do not have a source code available can only get ROMs if someone chooses to port a ROM from a similar device with similar hardware, that is the only way to get a ROM without stock source code. The stock firmware would be required in order to port a ROM from a similar device, if the stock firmware is not available, you can't port a ROM.
Sent from my LGL84VL using Tapatalk
Droidriven said:
They started by starting with smaller, less complicated developments/modifications to get some basic understanding. Then they started spending more time doing more diligent research, reading, reading again then reading again than they did spending time asking questions.
As for the "sharing their knowledge" for others to learn.... Well, that is exactly why there are hundreds or even thousands of guides and threads on the various types of android custom development on many different websites and forums. The issue you are having is based in the fact that all of the guides are written with assumption that the reader already has some form of intermediate programming knowledge, they are not written for the proverbial "noob". Another factor is that none of the guides are an "all-in-one, everything you need to know from start to finish" type of guide, this is because there are too many differences in the various android versions, hardware architectures, SDK versions, APIs and etc. to make a guide complete enough for general usage on every type of device, there are specific things involved that make that an impossible task. So don't get your hopes up about some kind of miracle answer that takes the pain and hard work out of your journey.
Study the guides, start small, get good at what you start with, then work your way up, starting with trying to build something like a ROM with no previous programming experience, is not a good idea for a starting point.
There is no shortage of people coming to XDA wanting to be developers and asking for someone to help teach them, it just doesn't work that way, you gotta be willing to put the time into learning and figuring out at least 95% of it on your own, that is how they learned, why should it be any different for you. The cold reality is, those that truly desire it, seek it diligently without reaching out for a hand to do the "real" work for them, the ones that succeed and excel are the ones that climb the ladder themselves with very little help from the outside because they reach inside of themselves and apply themselves to their goal without quitting or losing heart or saying "this is too hard, help me".
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Thanks for the advice.. I was hoping for something along the lines of a "I found a formula, you can use it to solve your problem" kind of answer.. But I understand your point of view. I was by no means asking for anyone to do the "real" work for me, just for a helping hand to point me in the correct direction. Most of the guides I see are just to create some basic files using the boot.img of my device.
Alando123 said:
Thanks for the advice.. I was hoping for something along the lines of a "I found a formula, you can use it to solve your problem" kind of answer.. But I understand your point of view. I was by no means asking for anyone to do the "real" work for me, just for a helping hand to point me in the correct direction. Most of the guides I see are just to create some basic files using the boot.img of my device.
Click to expand...
Click to collapse
I added to my post above, it might give you an idea of what is possible and what isn't.
Go to the LineageOS website and read the basic guide for setting up an android build environment, then read some guides for building ROMs for other similar Blu Studio devices.
Also, another important factor in whether or not a custom ROM is possible for your device is thst your bootloader must be unlocked or at least "can" be unlocked.
You also need a custom recovery such as TWRP(which you'd probably have to build for yourself, which is yet another task to learn in development along with learning to build a ROM, not to mention learning how to get the kernel right) in order to flash a LineageOS custom ROM or any other ROM that is not based on stock, TWRP is easier to learn how to build than a ROM, but still a task in itself. Modified stock ROMs can be customized and flashed without root or custom recovery but they aren't "true" custom ROMs, they are still fully stock underneath with some tweaks "on the surface".
Sent from my LGL84VL using Tapatalk
Droidriven said:
I added to my post above, it might give you an idea of what is possible and what isn't.
Go to the LineageOS website and read the basic guide for setting up an android build environment, then read some guides for building ROMs for other similar Blu Studio devices.
Also, another important factor in whether or not a custom ROM is possible for your device is thst your bootloader must be unlocked or at least "can" be unlocked.
You also need a custom recovery in order to flash a LineageOS custom ROM or any other ROM that is not based on stock. Modified stock ROMs can be customized and flashed, but they aren't custom, they are still fully stock underneath with some tweaks "on the surface".
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Yes.. I have made a TWRP for my device.. I also created a modified (rooted, debloated, updated) stock ROM.. But want to reach a stage where I'm able to make an actual custom ROM. I am currently flying through many guides to get an idea of what is needed.
I've set up build environments and built ROMs for Samsung Galaxy Grand Prime (grandprimeve3g) but that device already had proprietary blobs made for it.
Alando123 said:
Yes.. I have made a TWRP for my device.. I also created a modified (rooted, debloated, updated) stock ROM.. But want to reach a stage where I'm able to make an actual custom ROM. I am currently flying through many guides to get an idea of what is needed.
I've set up build environments and built ROMs for Samsung Galaxy Grand Prime (grandprimeve3g) but that device already had proprietary blobs made for it.
Click to expand...
Click to collapse
Ok, so you have a decently basic understanding, that is in your favor. As for the blobs, is the stock source available for your specific device? That would help increase your chances of success. Are their any other models of Blu Studio or other device with similar hardware that have custom ROMs already available? If so, you may can put something together using some blobs from those devices and then filling in the blanks.
@Alando123
Can you get a ROM dump or system dump from your device?
I'm going to assume that you've read this and experimented with it?
https://wiki.lineageos.org/proprietary_blobs.html
Sent from my LGL84VL using Tapatalk
Droidriven said:
Ok, so you have a decently basic understanding, that is in your favor. As for the blobs, is the stock source available for your specific device? That would help increase your chances of success. Are their any other models of Blu Studio or other device with similar hardware that have custom ROMs already available? If so, you may can put something together using some blobs from those devices and then filling in the blanks.
@Alando123
Can you get a ROM dump or system dump from your device?
I'm going to assume that you've read this and experimented with it?
https://wiki.lineageos.org/proprietary_blobs.html
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
No, BLU rarely releases source for any of their devices, however I made a system dump using MTK Droid Tools. I also just stumbled upon the link to the LineageOS page about blobs right before you replied ?
Alando123 said:
No, BLU rarely releases source for any of their devices, however I made a system dump using MTK Droid Tools
Click to expand...
Click to collapse
You should be able to use the system dump to generate vendor blobs by extracting them from the system dump or from a system dump pulled from a similar BLU studio or MTK device running a current LineageOS ROM as described in the first portion of the guide in the link that I gave you.
Also, there is a Lineage forum and a place to comment/ask questions on their github page.
Sent from my LGL84VL using Tapatalk
Droidriven said:
You should be able to use the system dump to generate vendor blobs by extracting them from the system dump or from a system dump pulled from a similar BLU studio or MTK device running a current LineageOS ROM as described in the first portion of the guide in the link that I gave you.
Also, there is a Lineage forum and a place to comment/ask questions on their github page.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Hey, I currently ported several ROMs for my device.. the only problem I have with all of the ROMs are auto-focus and front camera (though camera is an issue for almost all ROMs, developed or ported at first). Most of the devices are similar, so, I'll do some digging and see what I can do about this. Or if I can develop a ROM, with some kanged blobs and some of my own, that will work, then fix camera piece by piece.
Alando123 said:
Hey, I currently ported several ROMs for my device.. the only problem I have with all of the ROMs are auto-focus and front camera (though camera is an issue for almost all ROMs, developed or ported at first). Most of the devices are similar, so, I'll do some digging and see what I can do about this. Or if I can develop a ROM, with some kanged blobs and some of my own, that will work, then fix camera piece by piece.
Click to expand...
Click to collapse
Yes, stock camera is always an issue when building ROMs because stock camera is proprietary, this means the camera is a closed source software instead of open source software.
Generally, the "quick fix" is to use a 3rd party camera app from PlayStore such as Google Camera or A Better Camera(ABC camera). Try some 3rd party camera apps and see if any work.
Sent from my LGL84VL using Tapatalk
Droidriven said:
Yes, stock camera is always an issue when building ROMs because stock camera is proprietary, this means the camera is a closed source software instead of open source software.
Generally, the "quick fix" is to use a 3rd party camera app from PlayStore such as Google Camera or A Better Camera(ABC camera). Try some 3rd party camera apps and see if any work.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Yeah.. replacing libcameracustom.so results in the same issue with front camera, also even Footej closed when trying to use the front camera.
Alando123 said:
Yeah.. replacing libcameracustom.so results in the same issue with front camera, also even Footej closed when trying to use the front camera.
Click to expand...
Click to collapse
Try more than just a few camera apps, try many, try several, try them all, one of them might work. It's aggravating and time consuming, but with patience, it might work out for you.
You might need to try an app and then if it doesn't work, uninstall the app then boot into recovery and wipe cache and dalvik cache then reboot and try another camera app, you might also need to try a factory reset along with wiping cache from recovery before trying another camera app because some things might be left behind from the non working app that you tried and it might interfere with the next app that you try. Factory resetting and wiping cache before trying the next app might increase the chances that it will work. If you try an app and it doesn't work, just uninstalling it before trying the next app might not be "enough" if it leaves something behind that prevents the next app from working.
Sent from my LGL84VL using Tapatalk
Droidriven said:
Try more than just a few camera apps, try many, try several, try them all, one of them might work. It's aggravating and time consuming, but with patience, it might work out for you.
You might need to try an app and then if it doesn't work, uninstall the app then boot into recovery and wipe cache and dalvik cache then reboot and try another camera app, you might also need to try a factory reset along with wiping cache from recovery before trying another camera app because some things might be left behind from the non working app that you tried and it might interfere with the next app that you try. Factory resetting and wiping cache before trying the next app might increase the chances that it will work. If you try an app and it doesn't work, just uninstalling it before trying the next app might not be "enough" if it leaves something behind that prevents the next app from working.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
I don't think that any camera app would have helped.. I replaced libcameracustom.so from a different device, and front camera works, but no both cameras have a blue hue on them
I am having problems with building lineageOS for my "Unsupported" Device I have made themed ROMS, Themes for cyanogenmod, Themes for substratum, basic apps for my ROM, and customized recovery and ported ROMS to my device but I need a small headstart to actually "Build" lineageOS for my device. Thats It
Regards
Manav Harsana
Here I will post useful info, firmwares, etc for Teclast T8 master. You can ask any related questions here.
Official Stock firmware
Link: http://www.teclast.com/en/
TWRP+ROOT
Link: https://forum.xda-developers.com/android/help/twrp-root-custom-recovery-teclast-t8-t3892647
Custom ROMs (for TWRP only)
Modified stock ROM: https://forum.xda-developers.com/android/help/firmware-modified-stock-rom-v2-01-t3894124
ASUS ZenUI ROM: https://forum.xda-developers.com/android/help/firmware-asus-zenui-rom-teclast-t8-t3898591
MIUI 10 ROM (stable!): https://forum.xda-developers.com/android/help/firmware-miui-10-rom-teclast-t8-beta-t3910219
Pixel Experience ROM: https://forum.xda-developers.com/android/help/firmware-pixel-experience-rom-teclast-t8-t3919512
Tricks and tips
Messengers (Facebook, Twitter etc) crush problem solutions: https://forum.xda-developers.com/android/help/solution-solving-problem-messengers-t3994365
Facebook login issue fix: https://forum.xda-developers.com/t/solution-facebook-login-issue-in-teclast-t8-e8c1.4169035/
Spare Parts
Battery (tested - suits and works fine): https://aliexpress.ru/item/10050030...earchweb0_0,searchweb201602_,searchweb201603_
Hey man, thanks for your works for this tablet! I've got one in the mail...
What ROM is your your favourite and recommend trying out first?
Sword900 said:
Here I will post useful info, firmwares, etc for Teclast T8 master. You can ask any related questions here.
Official Stock firmware
Link: http://www.teclast.com/en/
TWRP+ROOT
Link: https://forum.xda-developers.com/android/help/twrp-root-custom-recovery-teclast-t8-t3892647
Custom ROMs (for TWRP only)
Modified stock ROM: https://forum.xda-developers.com/android/help/firmware-modified-stock-rom-v2-01-t3894124
ASUS ZenUI ROM: https://forum.xda-developers.com/android/help/firmware-asus-zenui-rom-teclast-t8-t3898591
MIUI 10 ROM (BETA): https://forum.xda-developers.com/android/help/firmware-miui-10-rom-teclast-t8-beta-t3910219
Pixel Experience ROM: https://forum.xda-developers.com/android/help/firmware-pixel-experience-rom-teclast-t8-t3919512
Click to expand...
Click to collapse
_jonte said:
Hey man, thanks for your works for this tablet! I've got one in the mail...
What ROM is your your favourite and recommend trying out first?
Click to expand...
Click to collapse
Just try any you like. Both ASUS and PIXEL Roms are stable
Sword900 said:
Here I will post useful info, firmwares, etc for Teclast T8 master. You can ask any related questions here.
Official Stock firmware
Link: http://www.teclast.com/en/
TWRP+ROOT
Link: https://forum.xda-developers.com/android/help/twrp-root-custom-recovery-teclast-t8-t3892647
Custom ROMs (for TWRP only)
Modified stock ROM: https://forum.xda-developers.com/android/help/firmware-modified-stock-rom-v2-01-t3894124
ASUS ZenUI ROM: https://forum.xda-developers.com/android/help/firmware-asus-zenui-rom-teclast-t8-t3898591
MIUI 10 ROM (BETA): https://forum.xda-developers.com/android/help/firmware-miui-10-rom-teclast-t8-beta-t3910219
Pixel Experience ROM: https://forum.xda-developers.com/android/help/firmware-pixel-experience-rom-teclast-t8-t3919512
Click to expand...
Click to collapse
Sword900 said:
Just try any you like. Both ASUS and PIXEL Roms are stable
Click to expand...
Click to collapse
Do these ROMs have the slight but constant micro-stuttering that the stock ROM has?
I guess all these ROMs are loaded with Google's stuff?
With the exception of Play Store I'd like to be free of the Google fleet of useless apps.
It's great that you've been able to port these ROMs. I hope a lot of people use them. I just have different needs! Tx.
_jonte said:
Do these ROMs have the slight but constant micro-stuttering that the stock ROM has?
Click to expand...
Click to collapse
What do you mean exactly?
doktorspin said:
I guess all these ROMs are loaded with Google's stuff?
With the exception of Play Store I'd like to be free of the Google fleet of useless apps.
It's great that you've been able to port these ROMs. I hope a lot of people use them. I just have different needs! Tx.
Click to expand...
Click to collapse
Yes, all of them. You can "freeze" or delete unwanted Google apps. Do it manually or try to find scripts which can do this automatically.
Hi, I was thinking to buy this tablet.
Can these ROMs fix the issue of too high brightness even at the lowest level?
If not can you recommend a free application to solve the problem?
Better this or teclast m89 pro? Thanks.
dr.Dobermann said:
Hi, I was thinking to buy this tablet.
Can these ROMs fix the issue of too high brightness even at the lowest level?
If not can you recommend a free application to solve the problem?
Better this or teclast m89 pro? Thanks.
Click to expand...
Click to collapse
To solved this brightness issue I use the sFilter app or any other blue light filter app.
But to tell the truth, I wouldn't recommend to buy any Teclast tablet. I have a problem where he doesn't accept the installation of Instagram or Facebook app. I saw that many people have the same problem.
Anyone else with this problem or know how to solve?
Vox.Irae said:
To solved this brightness issue I use the sFilter app or any other blue light filter app.
But to tell the truth, I wouldn't recommend to buy any Teclast tablet. I have a problem where he doesn't accept the installation of Instagram or Facebook app. I saw that many people have the same problem.
Anyone else with this problem or know how to solve?
Click to expand...
Click to collapse
I added solution, check it and let me know if it works for u
It's possible to change brightness limits manually by editing firmware files, If there's a big problem for u and other users I can change its' range sometime. Just let me know what firmware u are using.
Hello dev!
Are you still working on this device firmware? I bought it this month and not even on official site could find updates for, so I don't know if there is any firmware that I should update before using these that you made...
I'm using Pixel Experience and found it great. But I had problems with the initial setup, which always had trouble trying to recover the configuration of another device. When I checked to set up as a new device it work fine.
I could not open Magisk too, but i wanted to disable it and remove, but always shows error when trying. I'll try MIUI in sequence to see if I can.
Another question: The modified Stock has gapps included? (and can I remove root?)
Thank you so much for your work, I was happy to know that have other firmware for this tablet.
PS.: sorry for the "google translator english", my english is poor. lol
the.password said:
Hello dev!
Are you still working on this device firmware? I bought it this month and not even on official site could find updates for, so I don't know if there is any firmware that I should update before using these that you made...
I'm using Pixel Experience and found it great. But I had problems with the initial setup, which always had trouble trying to recover the configuration of another device. When I checked to set up as a new device it work fine.
I could not open Magisk too, but i wanted to disable it and remove, but always shows error when trying. I'll try MIUI in sequence to see if I can.
Another question: The modified Stock has gapps included? (and can I remove root?)
Thank you so much for your work, I was happy to know that have other firmware for this tablet.
PS.: sorry for the "google translator english", my english is poor. lol
Click to expand...
Click to collapse
I use the modified rom and it comes with gapps. And with another very interesting option "PC mode"
DrZocato said:
I use the modified rom and it comes with gapps. And with another very interesting option "PC mode"
Click to expand...
Click to collapse
I used the modified rom too and liked a lot, but I couldn't install some apps through the playstore and had problems to remove root (Magisk). So I installed ASUS ROM and it is very stable and everything is working great. I'll leave it and see what happens!
Thanks!
the.password said:
Hello dev!
Are you still working on this device firmware? I bought it this month and not even on official site could find updates for, so I don't know if there is any firmware that I should update before using these that you made...
I'm using Pixel Experience and found it great. But I had problems with the initial setup, which always had trouble trying to recover the configuration of another device. When I checked to set up as a new device it work fine.
I could not open Magisk too, but i wanted to disable it and remove, but always shows error when trying. I'll try MIUI in sequence to see if I can.
Another question: The modified Stock has gapps included? (and can I remove root?)
Thank you so much for your work, I was happy to know that have other firmware for this tablet.
PS.: sorry for the "google translator english", my english is poor. lol
Click to expand...
Click to collapse
Hello!
1) There is no more firmwares to port for our device. Also I don't know much about modding firmwares, so Pixel was my first successful experiment.
2) Latest official firmware for our device is TOS v2.1 which can be found in appropriative thread here. Seems no more updates will be released for our device.
3) Restoring function is bad idea esp on custom ROM. You should always make clean installation.
4) Custom ROMs can only boot with root access (e.g. Magisk). You cant uninstall it. In other case your device wont boot (Android 7.0 classical issue). P.S Magisk is not like "classic" root, so you can "hide" it for apps that don't work on rooted device.
5) Of course stock ROM includes Gapps. All made changes are listed in topic. Root can'f be removed on any custom ROM (see p.4).
Sword900 said:
Hello!
1) There is no more firmwares to port for our device. Also I don't know much about modding firmwares, so Pixel was my first successful experiment.
2) Latest official firmware for our device is TOS v2.1 which can be found in appropriative thread here. Seems no more updates will be released for our device.
3) Restoring function is bad idea esp on custom ROM. You should always make clean installation.
4) Custom ROMs can only boot with root access (e.g. Magisk). You cant uninstall it. In other case your device wont boot (Android 7.0 classical issue). P.S Magisk is not like "classic" root, so you can "hide" it for apps that don't work on rooted device.
5) Of course stock ROM includes Gapps. All made changes are listed in topic. Root can'f be removed on any custom ROM (see p.4).
Click to expand...
Click to collapse
Thank you!
I gave the tablet to my son, the Stock ROM that came on it is'nt good and so I put the ASUS ZenUI ROM. (After testing all others)
I hide Magisk and the ROM is working perfectly.
Thank you so much for the great work.
Happy 2020.
fix login facebook in Teclast T8
Failed to enter An unexpected error has occurred. Try again later. (IllegalArgumentException: Unknown URL content://com.facebook.katana.provider.UserValuesProvider/user_values)
https://forum.xda-developers.com/android/help/solution-facebook-login-issue-teclast-t4169035
Hi all, just wonder if anyone have some kind of t8 teardown? my t8 volume button is kinda broken like 2 years ago and now its stop functioning. Also the battery is starting to swollen..
wanna try to see part number for it.
alveox said:
Hi all, just wonder if anyone have some kind of t8 teardown? my t8 volume button is kinda broken like 2 years ago and now its stop functioning. Also the battery is starting to swollen..
wanna try to see part number for it.
Click to expand...
Click to collapse
Hi, man! I disassembled our device a year ago. So here you can see batteries photos, btw we have 2 here. I tried to find batteries by their part number but not succeded in it... If you will find it, please let the community know.
Screenshot
Captured with Lightshot
prntscr.com
Screenshot
Captured with Lightshot
prntscr.com
i need flat cable lcd to motherboard
Could you please share the download link of MIUI and Pixel Experience ROM again, the link of Mega has been lost. Thank you
Quannis said:
Could you please share the download link of MIUI and Pixel Experience ROM again, the link of Mega has been lost. Thank you
Click to expand...
Click to collapse
Links were updated. Check it out!
Here was a Guide. Someone said people don't care about Me or My Work so...
does it require an unlock bootloader?is it prerooted?does it have drm keys? sorry for the questions.
nolihowell said:
does it require an unlock bootloader?is it prerooted?does it have drm keys? sorry for the questions.
Click to expand...
Click to collapse
Yes, You need to be unlocked, otherwise is there no chance to flash with fastboot. Besides the rooting of the Kernel is everything Stock. Everything works so far even with GSIs
Where did you get the Customized EU 55.1.A.0.748 J9210 ?? I does not appear on XperiFirm.
nreuge said:
Where did you get the Customized EU 55.1.A.0.748 J9210 ?? I does not appear on XperiFirm.
Click to expand...
Click to collapse
My Bad, it is the UK one... I'm also still waiting for customized EU which was always My Choice for Xperia Sources and Development. I'm currently working with GSIs on My Xperia 5 but think i will Release some Stock work soon since i prefer Xperia Android actually over AOSP...
Users will be able to use any Base Firmwares (Android 10) for it but i will personally Test on Custom EU :fingers-crossed:
@Miustone will you be releasing a boot.img for the latest security patch?
fcb13 said:
@Miustone will you be releasing a boot.img for the latest security patch?
Click to expand...
Click to collapse
Just downloaded J9210_Customized EU3_1320-1208_55.1.A.3.49_R2B. I will release a Update after getting it running on My X5 this Weekend alongside with a Magisk Module Update for XPIXELERIA https://github.com/Miustone/XPIXELERIA
BR
Miustone said:
Just downloaded J9210_Customized EU3_1320-1208_55.1.A.3.49_R2B. I will release a Update after getting it running on My X5 this Weekend alongside with a Magisk Module Update for XPIXELERIA https://github.com/Miustone/XPIXELERIA
BR
Click to expand...
Click to collapse
@Miustone Sorry to bother you here, but I am struggling with patching the Xperia 1 .sin boot image with any current version of Magisk. I've tried a few versions but they all fail to create the image from the .sin file. Any help you can provide is greatly appreciated!
I should add, I was trying to use these instructions: https://forum.xda-developers.com/xperia-1/how-to/xperia-1-root-guide-t3938304
charlatan01 said:
@Miustone Sorry to bother you here, but I am struggling with patching the Xperia 1 .sin boot image with any current version of Magisk. I've tried a few versions but they all fail to create the image from the .sin file. Any help you can provide is greatly appreciated!
I should add, I was trying to use these instructions: https://forum.xda-developers.com/xperia-1/how-to/xperia-1-root-guide-t3938304
Click to expand...
Click to collapse
Just read the first Post of this Thread and You will get everything You'll need.
EDIT: Since You just need a .img File for Magisk is there no need to share it with Me actually. Just patch it in the Magisk Manager App and flash it with fastboot afterwards.
Miustone said:
Just read the first Post of this Thread and You will get everything You'll need.
EDIT: Since You just need a .img File for Magisk is there no need to share it with Me actually. Just patch it in the Magisk Manager App and flash it with fastboot afterwards.
Click to expand...
Click to collapse
Ah, okay. Thanks. One last stupid question.. for the firmware, does it matter if the img file comes from the Android 10 firmware? I am planning to flash my Xperia 1 with PE, which is still Pie.
charlatan01 said:
Ah, okay. Thanks. One last stupid question.. for the firmware, does it matter if the img file comes from the Android 10 firmware? I am planning to flash my Xperia 1 with PE, which is still Pie.
Click to expand...
Click to collapse
Prefer a newer Base Firmware over a newer GSI. A Android 9 GSI will run better with Android 10 Kernel as vice versa. Pie will be no Problem if You run Android 10 Vendor and Kernels. Happy flashing! :fingers-crossed:
EDIT: There are also PE Android 10 Builds out there... https://forum.xda-developers.com/pr...iscussion/gsi-expressluke-built-gsis-t4003457
help me
hi i need a boot.img for my xperia 1 j8170 please help me 10 (55.1.a.3.107)
This method has always been magisk module not friendly. audio compat worked. But once i through more at it it bricked device and had to reflash with new flasher
Hi
Can you please patch this file for me (Device = J9210 Dual | Firmware = 55.1.A.3.149)
boot_X-FLASH-ALL-A2CD.7z
Kind Regards
After I get root, can I completely deGoogle my phone? Since there is no Lineage OS for XPERIA 5, can I manually get rid of all of Google's stuff?
Help is greatly appreciated.
Thank you.
BuyXRPnow! said:
After I get root, can I completely deGoogle my phone? Since there is no Lineage OS for XPERIA 5, can I manually get rid of all of Google's stuff?
Help is greatly appreciated.
Thank you.
Click to expand...
Click to collapse
Yes You can. But You can also install LOS 17.1 from the GSI Forums. I also did Instructions for flashing GSI Treble ROMs in the Xpiera 5 Guides Forum :good:
After that You may want to have Magisk to pass safetynet and to install MicroG or NanoDroid to get everything working. I'm actually running PHHs AOSP with My SOM Module and it's one of My Favorites so far. You may also like Havoc OS Official which also comes as no Google Apps Version. You can do the same on Havoc like You can on LOS but + endless Costomization
Miustone said:
Yes You can. But You can also install LOS 17.1 from the GSI Forums. I also did Instructions for flashing GSI Treble ROMs in the Xpiera 5 Guides Forum :good:
After that You may want to have Magisk to pass safetynet and to install MicroG or NanoDroid to get everything working. I'm actually running PHHs AOSP with My SOM Module and it's one of My Favorites so far. You may also like Havoc OS Official which also comes as no Google Apps Version. You can do the same on Havoc like You can on LOS but + endless Costomization
Click to expand...
Click to collapse
I really appreciate your reply, but I am a complete noob and all this is extremely overwhelming.
"PHHs AOSP with My SOM Module" - this alone gives me terrors
I know nothing about these things but I understand you, it's just everyday business for you coz you are a developer. I tried reading your guides and there are so many things I don't understand. I also was traumatized by rooting my S10, which I sold and got Xperia 5 instead. I read here people said I will permanently lose DRM keys after rooting. This is my biggest problem. With S10 I knew I could go back to stock and not worry. Here, if I go all the way and deGoogle my Xperia and it doesn't work the way it should I won't be able to go back and on top of that selling it will be harder and I will lose money since not everyone is willing to buy a phone which can't get Netflix and other DMR-dependent garbage.
Maybe I could sponsor you to help me flashing all the stuff. I just don't know if it's a crazy idea. Also, asking you to rewrite your guides for idiots like me is asking too much, given how busy you are.
If you have some advice I would greatly appreciate it.
BuyXRPnow! said:
I really appreciate your reply, but I am a complete noob and all this is extremely overwhelming.
"PHHs AOSP with My SOM Module" - this alone gives me terrors
I know nothing about these things but I understand you, it's just everyday business for you coz you are a developer. I tried reading your guides and there are so many things I don't understand. I also was traumatized by rooting my S10, which I sold and got Xperia 5 instead. I read here people said I will permanently lose DRM keys after rooting. This is my biggest problem. With S10 I knew I could go back to stock and not worry. Here, if I go all the way and deGoogle my Xperia and it doesn't work the way it should I won't be able to go back and on top of that selling it will be harder and I will lose money since not everyone is willing to buy a phone which can't get Netflix and other DMR-dependent garbage.
Maybe I could sponsor you to help me flashing all the stuff. I just don't know if it's a crazy idea. Also, asking you to rewrite your guides for idiots like me is asking too much, given how busy you are.
If you have some advice I would greatly appreciate it.
Click to expand...
Click to collapse
First of all. Good choice to get rid of a Samsung Device Like i did with My S9+! Sammy is pushing Android into a Appleish Edge that shouldn't exist...
Just like Huawei. But different Story...
Out of My View with Years of expierence with different Brands is SONY one of the Most supporting OEM in Views of Android Development besides the Fact they Always excluded some functionality of the included Smartphone Hardware. For example:
-Xperia Z1 lost the Complete Camera Function after unlocking (Got fixed with a Update later after Claims from Customers) and lost Display enhancements + Camera Noise reduction
-Xperia Z3 lost the Vibrant Display Colors after unlocking (Aka Bravia Engine) which ended Up in washed Out Colors and was still loosing Noise reduction
-Xperia XZ Premium still loosing enhancements after unlocking plus the loss of Camera Noise reduction
And now the Xperia 5...
Sony used for the First Time Samsung Sensors for the Cameras instead of own ones with High Resolution. So no Noise Reduction needed anymore. Finally OLED, so no washed Out colors without Display Enhancements.
I'm quite Happy with this One since you don't loose Something Essential. Besides that have i Always Managed since the Z3 to fix almost all Problems on Xperias with native Android functionalities that is used on other Devices. Eg. For the Display, Audio, Camera, Mics and so on.
And thats the final Point. While older Devices Had the Chance to Backup and restore the TA Partition or even to use a Recovery on locked Bootloader (I've also worked with this for some Time) which allowed to make Your Device Complete Stock again. We don't really have that Options anymore. So i would say an Unlock is a final Step. But to be honest. I sold many Devices claimed as unlocked and rooted and it hasn't Cut the Price at all. And even if You Don't. I don't think a normal Person will See a difference after unlocking and relocking
Is it worth it? For Me a clear Yes! I never looked back after unlocking any of My "Hundreds" of Devices i used. Magisk and GSIs alone are really worth the Unlock Out of My View actually. You can do so much with Android and it finally doesn't feels Bad anymore on Xperias. My SOM (Magisk based ROM (Systemless-On-Memory) will do a lot of awesome Things with Our Xperias (1 & 5). Another good Reason maybe...
It could be smart to make a Video which explains how to get My Work on Your Xperias. From unlocking to Flashing... Would really like to do that after some preparing for it. Possible that there are a lot of People who don't even know about Bootloader unlocking so it really could be cool. I already did some Videos in the Past; https://www.youtube.com/user/TheMarius517
Think i got a bit lazy since the Software alone takes so much time These days. But i will do My best to get People in Touch and to Show everything step by step.
Lot of Text but Hope i made Your decision to Unlock or not easier... Don't think about the Future of Your Device. Think about what You want from it right now...:good:
Btw. Not Sure but You could try ADB to remove Apps. But idk. If IT IS possible with Google Apps (Locked Bootloader Method)
All the Best,
Miu
Thank you! You are a hero. I will be waiting for your updated guides and possibly a video for noobs. Appreciate your time!
Peace.
Optimized the Thread Structure and Instructions. Optimized Thread Title. Updated Boot Image / Kernel to latest EU .149
PROBLEM:
1. I need to find a forum where I can learn about rooting in a general way, not just a phone specific way. There are too many overlapping problems with my phone and issues that I am too undereducated to pinpoint. I thought learning how to root and flash stock-roms might be the best place to start. Book references or YouTube channels would also be wonderful.
2. I would also like to be pointed in the direction of what the problem might actually be if I am out in left field, and where to find that on this site as well.
HERE'S SOME OF WHAT I WANT TO LEARN IN THE FORUMS:
What is the difference between Rooting and Unlocking the Bootloader? Are they the same thing?
Will re-locking the bootloader resolve the certification issue like I read?
How do I lock the bootloader again?
Can you fix UI crashes by re-flashing a phone's stock ROM?
How is a Factory reset different from a fresh stock-rom flash?
If factory reset doesn't stop the UI Crashes, will re-flashing the stock rom have a different effect?
Etc.
DETAILS:
I purchased a Razer 2 Phone and unlocked the bootloader but it was a long time ago and I don't remember what I did. I did some research and it looks like when I did that my Google Play Store lost its certification. I think that it is causing app bugs and failures but I am not sure because the phone's UI sytem, bluetooth and Wi-fi have been crashing before I tampered with anything when I first bought the phone online. Bluetooth and Wi-fi don't stay on and toggle themselves off. There is also no Bluetooth or Wi-Fi address in the system info. It makes me think that my Door Dash app bugs might be more than one thing.
I work for Door Dash and it's my main income so I need my app to work and I think that the bad certification is causing problems with my Door Dash App. But the Razer also needs a software repair.
Pernilex said:
PROBLEM:
1. I need to find a forum where I can learn about rooting in a general way, not just a phone specific way. There are too many overlapping problems with my phone and issues that I am too undereducated to pinpoint. I thought learning how to root and flash stock-roms might be the best place to start. Book references or YouTube channels would also be wonderful.
2. I would also like to be pointed in the direction of what the problem might actually be if I am out in left field, and where to find that on this site as well.
HERE'S SOME OF WHAT I WANT TO LEARN IN THE FORUMS:
What is the difference between Rooting and Unlocking the Bootloader? Are they the same thing?
Will re-locking the bootloader resolve the certification issue like I read?
How do I lock the bootloader again?
Can you fix UI crashes by re-flashing a phone's stock ROM?
How is a Factory reset different from a fresh stock-rom flash?
If factory reset doesn't stop the UI Crashes, will re-flashing the stock rom have a different effect?
Etc.
DETAILS:
I purchased a Razer 2 Phone and unlocked the bootloader but it was a long time ago and I don't remember what I did. I did some research and it looks like when I did that my Google Play Store lost its certification. I think that it is causing app bugs and failures but I am not sure because the phone's UI sytem, bluetooth and Wi-fi have been crashing before I tampered with anything when I first bought the phone online. Bluetooth and Wi-fi don't stay on and toggle themselves off. There is also no Bluetooth or Wi-Fi address in the system info. It makes me think that my Door Dash app bugs might be more than one thing.
I work for Door Dash and it's my main income so I need my app to work and I think that the bad certification is causing problems with my Door Dash App. But the Razer also needs a software repair.
Click to expand...
Click to collapse
Welcome to XDA,
I would recommend this>
1. Type your desired device for rooting
2. Hit search
3. Once located your device, head to Upgrading and Modifying sub section
4. Be prepared to read a loooot!
5. Practice in your device (try not to brick it)
6. Done!
For this questions there is no general rule you can apply, it will always depend on the device you try to root
What is the difference between Rooting and Unlocking the Bootloader? Are they the same thing?
Will re-locking the bootloader resolve the certification issue like I read?
How do I lock the bootloader again?
Can you fix UI crashes by re-flashing a phone's stock ROM?
How is a Factory reset different from a fresh stock-rom flash?
If factory reset doesn't stop the UI Crashes, will re-flashing the stock rom have a different effect?
Enjoy your stay
Pernilex said:
I need to find a forum where I can learn about rooting in a general way, not just a phone specific way.
Click to expand...
Click to collapse
@Pernilex
Regarding your request. There're quite a few tutorials available like e.g. the ones of @AlaskaLinuxUser. Just use the search function:
[Guide][Video Tutorial] How to build Custom ROMs and Kernels![10,P,O,N,M,L]
Hey everyone! There is also a telegram channel where you can drop in for some help: https://t.me/joinchat/HR_8JgyDBdw_DvmndPl0kg I really hope that you have enjoyed the series, and that it was helpful to you in your Android career! Praise...
forum.xda-developers.com
[Guide][Video Tutorial] Intermediate to Advanced Custom Rom and Kernel Building
Hey everyone! There is also a telegram channel where you can drop in for some help: https://t.me/joinchat/HR_8JgyDBdw_DvmndPl0kg I really hope that you have enjoyed the series, and that it is helpful to you in your Android career! Praise God...
forum.xda-developers.com
[Video Tutorials] XDA Etiquette, Compiling Custom Roms/Kernels
Praise God! A video tutorial about XDA etiquette! These videos express my personal opinion, and are not necessarily the opinion of XDA. I am not speaking on their behalf. This is just a video series that I put together based on a recommendation...
forum.xda-developers.com
or
[GUIDE] [how to] CREATE OWN ROM [FOR ANY ANDROID DEVICE] [FOR N00B] [EASIEST METHODS]
NOTE: THIS GUIDE WILL WORK ANY ANDROID DEVICE BUT HAS FEW EXTRA PRE-SUGGESTED LINKS FOR GALAXY ACE PLUS USERS. Special Thanks to - dsixda for his awesome kitchen. Please Hit Thanks button for him. inspired by isidromxz's thread. Please kindly...
forum.xda-developers.com
The XDA University might also be helpful:
XDA-University
Tutorials, How-To Guides and More. Learn about mobile phone development, hacking, flashing, rooting and many other topics!
forum.xda-developers.com
Regards
Oswald Boelcke
Senior Moderator