Related
Hi guys,
Since today Huawei delivers the open sourcecode for the drivers, I guess.
Anyone in here capable to create a nice clean AOSP ROM or anything else good for our tablet?
Search link for LTE version:
http://m.huawei.com/enmobile/consum...roid=M2-A01L&proKey=Tablets_T/Tablets/M2-A01L
Direct download for LTE version:
http://download-c.huawei.com/downlo...oadId=89345&version=347349&siteCode=worldwide
Search link for WiFi version:
http://m.huawei.com/enmobile/consum...roid=M2-A01w&proKey=Tablets_T/Tablets/M2-A01w
Direct download for WiFi version:
http://download-c.huawei.com/downlo...oadId=89346&version=347353&siteCode=worldwide
I do not have the experience with ROM building, forking, ... etc. here.
One good room would be good.
Edit. Nevermind
Anyone with the LTE version of this can you upload to a cloud link so that I can download? I would rather not waste my time having to send an email to [email protected] just to get it. Thanks
Huawei Open Source Released
Hey,
maybe it is late, i have found the open source.
the link: consumer.huawei.com/en/opensource/
and we can find m2-a01l in the tablet part, and it is on page 4.
Emm...i dont know how many people use this tablet because it is out of date.:laugh:
and i dont know if it is everything we want
whatareyou007 said:
Huawei Open Source Released
Hey,
maybe it is late, i have found the open source.
the link: consumer.huawei.com/en/opensource/
and we can find m2-a01l in the tablet part, and it is on page 4.
Emm...i dont know how many people use this tablet because it is out of date.:laugh:
and i dont know if it is everything we want
Click to expand...
Click to collapse
Hi! Thank you, i'll do an AOSP for our poor tablet, the only problem in my case, I'm unable to unlock the bootloader because i haven't in dev options "OEM unlock". If I'll pass this issue, I'll immediately start to develop the ROM.
Crypto18 said:
Hi! Thank you, i'll do an AOSP for our poor tablet, the only problem in my case, I'm unable to unlock the bootloader because i haven't in dev options "OEM unlock". If I'll pass this issue, I'll immediately start to develop the ROM.
Click to expand...
Click to collapse
Hi! Have you able to develop for our poor table? 1 stable ROM should be enough
and0ng said:
Hi! Have you able to develop for our poor table? 1 stable ROM should be enough
Click to expand...
Click to collapse
The only problem in this moment still remain unlocking bootloader. I'm searching solutions
Crypto18 said:
The only problem in this moment still remain unlocking bootloader. I'm searching solutions
Click to expand...
Click to collapse
Yeah it's a pain to unlock the bootloader. But since I need to install Google Workspace device policy I have no other option
@Crypto18 - There is a possibilty to unlock the bootloader by using dc-unlocker - amount about 4 Euro. I had success in doing so a year ago. It would be very nice to get an AOSP-ROM für the tablet.
I think, I unlocked it with dc-unlocker, too, four years ago or so.
I would be happy to have any clean/empty/fresh AOSP ROM for this tablet, as up to today it is still fast and really usable.
If you need any help, I would also be eager to learn how to do it (building a ROM). @Crypto18
Crypto18 said:
Hi! Thank you, i'll do an AOSP for our poor tablet, the only problem in my case, I'm unable to unlock the bootloader because i haven't in dev options "OEM unlock". If I'll pass this issue, I'll immediately start to develop the ROM.
Click to expand...
Click to collapse
I did the DC-unlocker thing today as described in the sticky, so it still works. Somebody in this thread mentioned that it worked for him without the OEM unlock option (it disappeared in EMUI 4), but to be on the safe side I had done a downgrade to EMUI 3 before (the oldest one I found didn't have a working dialer, I didn't try the landscape calculator trick to activate the manufacturere mode, but updated to a later EMUI 3 version that had a a working dialer: "Huawei MediaPad M2-801L Android 5.1.1 EMUI 3.1 B007.zip").
I am now looking for a working TWRP (see my post in the sticky thread a few minutes ago).
If you manage to unlock your bootloader, I would be willing to go the "build your own version from scratch" way with you. I have experience as embedded Linux developer one decade ago, but never did it for Android. Would be more fun to have a second person interested in this "classic" tablet.
@coocooc , @Crypto18 ,
Have you made any progress with developing a custom rom?
@coocooc - Please search for "TWRP-3.1.0-recovery-MediaPadM2-10.0-LISZT-A01L-A01W.img" in TWRP. That's the TWRP you're looking for.
rotter99 said:
@coocooc , @Crypto18 ,
Have you made any progress with developing a custom rom?
Click to expand...
Click to collapse
Crypto18 so far did not come back, and I didn't start the journey yet.
I am on the way to prepare a Linux laptop for building Android and SBC stuff, but family life does not allow to spend many hours on my pet projects.
I wrote a mail to Huawei to get the latest sources (EMUI 4), but the first level support shown on their GPL site couldn't fulfill the wish. They gave me a developer address to apply to; let's see how this ends.
gelrav said:
@coocooc - Please search for "TWRP-3.1.0-recovery-MediaPadM2-10.0-LISZT-A01L-A01W.img" in TWRP. That's the TWRP you're looking for.
Click to expand...
Click to collapse
Thanks for the hint! I will try this TWRP version tonight. Which EMUI version are you using with this TWRP (EMUI 3 or 4)? Is there something to check in the flash layout first, to succeed with this TWRP?
@coocooc - I'm using a Huawei Mediapad M2 10.W with Emui 3.1., Android 5.1.1.
If you're on Mediapad 801L, the above mentioned TWRP will not work for you!
I am using “TWRP-3.1.0-recovery-MediaPadM2-10.0-LISZT-A01L-A01W.img“ om my M2-A01W and it working without any problems.
gelrav said:
@coocooc - I'm using a Huawei Mediapad M2 10.W with Emui 3.1., Android 5.1.1.
If you're on Mediapad 801L, the above mentioned TWRP will not work for you!
Click to expand...
Click to collapse
@gelrav Oh that might be the reason for my problems as I do use the 801L version. What alternative TWRP ist available then?
coocooc said:
@gelrav Oh that might be the reason for my problems as I do use the 801L version. What alternative TWRP ist available then?
Click to expand...
Click to collapse
Funny, the name of the TWRP file suggests that it is valid for both the L and the W versions of the M2-A01.
What is exactly the problem with this file?
I unlocked both the phone und FRP on my device before installing this file.
I am on EMUI 3.1. and Android 5.1.1.
@coocooc
Maybe this link can help you getting further:
Downloads for : Huawei -All-General-Generic- | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Dear reader,
since a couple of days my device (samsung S7: SM-G930F) is running low on battery really quick. So I thought; it has been a while since my device asked me to update the new Lineage version. So I gave the app the instruction to look for updates, and it gave me the following notification.
Can't connect to download site. Please retry later.
When actually
You device is supported by the lineageOS team, but there are no versions that support this type of publication: Nightly. (this is translated from Dutch, so actual English sentece might be different).
Switching to Snapshot instead of Nightly in the Settings didn't help.
Then when searching again for updates it gave me the message:
No source file
Request for file: lineage-14.1-20181124-nightly-herolte-signed.zip To reconstruct the last update, the zip of the app should actually be installed. Do you want to select this file manually from storage, or download the last full zip-version?
When I press: download full zip-file it gives the following:
Error during implementation. Try to refresh.
When I click on select file (from storage), and select lineage-14.1-20180927-nightly-herolte-signed.zip, it gives me the message:
You should select the right source file. But I don't have that one on my storage; it's froma different date.
Can anyone help me please?
Kind regards,
Chris
Joheee said:
Dear reader,
since a couple of days my device (samsung S7: SM-G930F) is running low on battery really quick. So I thought; it has been a while since my device asked me to update the new Lineage version. So I gave the app the instruction to look for updates, and it gave me the following notification.
Can't connect to download site. Please retry later.
When actually
You device is supported by the lineageOS team, but there are no versions that support this type of publication: Nightly. (this is translated from Dutch, so actual English sentece might be different).
Switching to Snapshot instead of Nightly in the Settings didn't help.
Then when searching again for updates it gave me the message:
No source file
Request for file: lineage-14.1-20181124-nightly-herolte-signed.zip To reconstruct the last update, the zip of the app should actually be installed. Do you want to select this file manually from storage, or download the last full zip-version?
When I press: download full zip-file it gives the following:
Error during implementation. Try to refresh.
When I click on select file (from storage), and select lineage-14.1-20180927-nightly-herolte-signed.zip, it gives me the message:
You should select the right source file. But I don't have that one on my storage; it's froma different date.
Can anyone help me please?
Kind regards,
Chris
Click to expand...
Click to collapse
S7 is no longer officially supported by lineageOS. You can search here in XDA for unofficial ROMs.
I have no big hope that a new ROM will really solve your battery issue. Most of the the success stories are a result of a clean ROM installation.
Joheee said:
Dear reader, since a couple of days my device (samsung S7: SM-G930F) is running low on battery really quick. So I thought; it has been a while since my device asked me to update the new Lineage version.........
Click to expand...
Click to collapse
In addition to the outstanding information that @kurtn had provided...
There's no Official LineageOS Updater Apps on the Play Store.
The reason is that they have an implemented LineageOS Updater built into the Firmware and has no need to provide any such app separately from the firmware. That would just be counterproductive to the built in Updater.
The LineageOS Updater App(s) on the Play Store is via a 3rd party developer. I'm not stating that any/all of them are either good or bad but, individuals need to know that their Unofficial and is in no way supported by the Official Lineage Team Maintainers.
Just a few (so to speak) words of advice to keep in mind. I remember asking about them (quite a while ago) and those were the types of words/thoughts by @invisiblek and @haggertk (whose a part the Official Lineage Lead Maintainers).
No lectures here... Just some friendly information for you My Friend!
Good Luck!
~~~~~~~~~~~~~~~
Unless asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX1 Forum App on my Sanyo Juno device.
Hi Kurt and Ibuprophen, thanks for your answers!
Now I have finally holiday and time to actually fix things it's time to continue this
So current situation;
Phone running out of battery within half a day without frequent using, apps crashing > update definitely required.
Phone model: Samsung S7 SM-930F
LineageOS version: 14.1-20181124-NIGHTLY-herolte (so last update is over a year old)
Android version 7.1.2
Options:
1. Just reset to factory settings? Most easy option, but I think it will have negative influence when I use the phone for another year?
2. I found this unoficcial ROM https://forum.xda-developers.com/galaxy-s7/development/beta-lineageos-16-0-s7-herolte-t3842465, however, it doesn't include instructions and it is very technical and it speaks of Android 9 as base, which I don't have; just 7.1.2. Would that be a problem?
3. Update to 15.1 instead if that is easier?
So what would be your advice? Please bear in mind that I am a technical noob and can only follow instructions that are extremely clear & correct
Until now I haven't found instructions I felt comfortable with unfortunately.
By the way my laptop has Linux Mint Cinnamon 19.2
Joheee said:
Hi Kurt and Ibuprophen, thanks for your answers!
Now I have finally holiday and time to actually fix things it's time to continue this
So current situation;
Phone running out of battery within half a day without frequent using, apps crashing > update definitely required.
Phone model: Samsung S7 SM-930F
LineageOS version: 14.1-20181124-NIGHTLY-herolte (so last update is over a year old)
Android version 7.1.2
Options:
1. Just reset to factory settings? Most easy option, but I think it will have negative influence when I use the phone for another year?
2. I found this unoficcial ROM https://forum.xda-developers.com/galaxy-s7/development/beta-lineageos-16-0-s7-herolte-t3842465, however, it doesn't include instructions and it is very technical and it speaks of Android 9 as base, which I don't have; just 7.1.2. Would that be a problem?
3. Update to 15.1 instead if that is easier?
So what would be your advice? Please bear in mind that I am a technical noob and can only follow instructions that are extremely clear & correct
Until now I haven't found instructions I felt comfortable with unfortunately.
By the way my laptop has Linux Mint Cinnamon 19.2
Click to expand...
Click to collapse
Oh, looks like ivan does a good job. I think it is a good idea to install his rom.
But be aware: whatever it is, that eats your battery, it can come back.
Edit: be aware: from the threads it looks like 15.1 and 16.0 are not SELinux enforcing. So the gain of security is not as high as one would expect from security patch level. So you can try a factory reset of 14.1 as well.
Do you think there is an easy, technical-illiterates-friendly way to install this version of ivan? I am not that keen to have the highest possible security.
When I am emptying the phone anyway, it seems best to me to have the most recent version (if it doesn't matter that I have android 7.1 and not android 9).
Joheee said:
Do you think there is an easy, technical-illiterates-friendly way to install this version of ivan? I am not that keen to have the highest possible security.
When I am emptying the phone anyway, it seems best to me to have the most recent version (if it doesn't matter that I have android 7.1 and not android 9).
Click to expand...
Click to collapse
Download the zip files for rom (and GApps if needed) boot into twrp wipe system, data and caches (not internal: there are your pictures and downliads etc)
Install: navigate to downloads folder select the zip file and hipe it works.
If not: ask in the thread you linked.
How to use lineage downloader app
Hello sir,
I have redmi note 4 (mido) device which is officially supported by lineage team and I heard about lineage downloader app and (Delta Update) so please guide me how to use this app.
My latest built is 2020-01-15 (pie).
Thanks.
Waiting....
[email protected] said:
Hello sir,
I have redmi note 4 (mido) device which is officially supported by lineage team and I heard about lineage downloader app and (Delta Update) so please guide me how to use this app.
My latest built is 2020-01-15 (pie).
Thanks.
Waiting....
Click to expand...
Click to collapse
Don't use that app. Use the procedures described in wiki.lineageOS.org
I just recently know about GSI (Generic System Name). So, I'm wandering if Google drop support for Pixel device, we still can have stock android via GSI right? And why didn't ROM developer just resolve to use this method? I am a dumbass, please educate me!
aL_09 said:
I just recently know about GSI (Generic System Name). So, I'm wandering if Google drop support for Pixel device, we still can have stock android via GSI right? And why didn't ROM developer just resolve to use this method? I am a dumbass, please educate me!
Click to expand...
Click to collapse
https://forum.xda-developers.com/pr.../rom-blissroms-9-0-official-4-4-2019-t3918303
because gsis are ****, use roms that are actually tailored for your device, not hard to flash
@aL_09
Start going in these telegram groups that are linked in some of the ops where our roms are. Google search "Marlin afh" and check out what's out there. There are still a few people building for Marlin. And we have LOS17 and Pixel Dust 10 that are active and some bad ass pie roms that aren't that old... You can use GSIs. I've flashed a few but all the ones I've tried seem to have issues with ril and have SIM card unavailable and no data and I haven't found a work around yet. But I just started crackflashing GSI's on this device.. If and when I find some solid ones I'll shoot you a message. But download telegram app and subscribe to the devs on our rom sections groups and look around from time to time. You'll find some good stuff!
flash713 said:
@aL_09
Start going in these telegram groups that are linked in some of the ops where our roms are. Google search "Marlin afh" and check out what's out there. There are still a few people building for Marlin. And we have LOS17 and Pixel Dust 10 that are active and some bad ass pie roms that aren't that old... You can use GSIs. I've flashed a few but all the ones I've tried seem to have issues with ril and have SIM card unavailable and no data and I haven't found a work around yet. But I just started crackflashing GSI's on this device.. If and when I find some solid ones I'll shoot you a message. But download telegram app and subscribe to the devs on our rom sections groups and look around from time to time. You'll find some good stuff!
Click to expand...
Click to collapse
Hey there!
Because Android 11 Beta 1 was released yesterday there are new GSI builds available. The OG Pixel XL is supposed to support GSIs. Can you explain me how I flash that onto my old Marlin (Pixel XL) device?
Help The Peace said:
Hey there!
Because Android 11 Beta 1 was released yesterday there are new GSI builds available. The OG Pixel XL is supposed to support GSIs. Can you explain me how I flash that onto my old Marlin (Pixel XL) device?
Click to expand...
Click to collapse
You should be able to find the information that you're looking for here https://developer.android.com/topic/generic-system-image/releases#android-gsi-11
If I were you I'd wait. While there's no guarantee I'm pretty sure android 11 roms will be available at some point made for the XL. The Pixel XL is an A/B partition device. Just always make a backup and transfer it on to a thumb drive or your computer before you start installing anything and always have your factory image handy and know how to use fastboot and adb so you can recover if something goes wrong. This whole Android thing is all about reading and searching. Just installing things without knowing what's really going on and how to recover is risky and I would not suggest it.
flash713 said:
You should be able to find the information that you're looking for here https://developer.android.com/topic/generic-system-image/releases#android-gsi-11
If I were you I'd wait. While there's no guarantee I'm pretty sure android 11 roms will be available at some point made for the XL. The Pixel XL is an A/B partition device. Just always make a backup and transfer it on to a thumb drive or your computer before you start installing anything and always have your factory image handy and know how to use fastboot and adb so you can recover if something goes wrong. This whole Android thing is all about reading and searching. Just installing things without knowing what's really going on and how to recover is risky and I would not suggest it.
Click to expand...
Click to collapse
I actually checked out that thread already. I followed the link what to do when the partition size isn't big enough initially. But it didn't work for me. So I guess you're right. I shouldn't flash the GSI and instead wait for Android 11 builds for Marlin. <3
Gsi don't boot on marlin
Also marlin not caf devices either
Join lunarixus chat on telegram and few build for marlin,sailfish,taimen
Sean
---------- Post added at 06:20 PM ---------- Previous post was at 06:19 PM ----------
I'm on bliss myself
Times are changing for oneplus. Seems like software support will be worse in the years coming.
I love my oneplus 7T. It's nearly the perfect phone for me. Right now I'm on the latest open beta, rooted with arter97 kernel. Amazing experience. Could easily keep this phone for many more years to come..
But.. If official updates is lacking, we need proper ROMs, and a functional twrp and good dev support. Is there any chance this will change in the future? Or is official twrp dead?
To the developer community out there, please correct me if I'm wrong.
The biggest obstacle to a "functional TWRP" is the decryption issue that OnePlus will hopefully address. If that gets resolved, we should see the ROM community take off. I agree that the 7T is a phenomenal phone and damned near perfect. That being said, I'd give almost anything to see Paranoid Android on this phone!
Twrp works to flash roms. Try looking into GSI for now since the twrp we have now does not support oos backup but we have a few roms guys.
What is a proper ROM according to you?
There are very stables ROM in the development section.
And you don't need TWRP at all. Convenient sure, but absolutely not needed.
brisseau said:
To the developer community out there, please correct me if I'm wrong.
The biggest obstacle to a "functional TWRP" is the decryption issue that OnePlus will hopefully address. If that gets resolved, we should see the ROM community take off. I agree that the 7T is a phenomenal phone and damned near perfect. That being said, I'd give almost anything to see Paranoid Android on this phone!
Click to expand...
Click to collapse
You can push the zip to /cache and flash fine. TWRP is not the reason for 'lack' development. An *actual* dev would have been able to build a ROM without any need of TWRP.
There are already good ROMs here in XDA, and you can find more on Telegram.
That being said, TWRP has made lots of progress on Android 10 and 11. Dynamic partitions should be fully handled, and fastbootd tools should be working too.
Just sync the sources alongside mauronofrios tree and test away.
As said upper, twrp is not an issue for devs, neither for us to flash roms
Amount of roms simply relies on the amount of people having this device. As OP released several phones (7, 7T, 7 pro), it seems normal we have less roms.
As a counterpart, Android's updates make it more easy to port roms, and most devices now share bigger part of dev tree.
AFAIK Paranoid Android 11 was just released on 8 & 8T.
7 & 7T will follow pretty soon, just be patient. Not every dev team has all devices to build up roms.
By the way, such topic won't change anything, maybe try financially supporting devs or learning to port roms by yourself.
I've been around a while so I'm not new to Android or to tech in general but I am new to this Slot A/B stuff and also new to using Verizon 5G/LTE.
After soft-bricking my new phone by flashing TWRP and crDroid 8.2 based on Android 12, everything seems to be working well except I noticed that I'm not receiving MMS. I went to APN settings but I'm not able to edit the existing ones and if I add a new one, I can't change any settings there except the APN field. I also noticed that my build.prop identifies my phone as LE2123. I confirmed before I modified anything that I have LE2125. Any thoughts on this?
Resolution:
It looks like All LOS based roms as well as TWRP and crDroid recovery are going to show a model of LE2123. It also looks like my MMS issues were caused by YAATA. It's either not compatible with Android 12 or with 5g/VoLTE etc. I ended up restoring back to factory using MSM tools and then installed one thing at a time until I narrowed it down to YAATA. Uninstalled and problem resolved
If I'm not mistaken crDroid is
LOS based where Derpfest is AOSP based
Why would you post an issue with crDroid in a separate post instead of reporting it in the actual rom's thread?
ive had that happen on occasion. the latest bug i seem to have acquired is that during the phone connection where and when the person making the call (me) in said scenario wait's for the other party to answer does not hear anything until either some one answers or their voicemail does.
I've got the same issue with the no ringing during a call on Derpfest rom but doesn't really bother me much I've gotten used to it
Elrey567 said:
I've got the same issue with the no ringing during a call on Derpfest rom but doesn't really bother me much I've gotten used to it
Click to expand...
Click to collapse
i have noticed that whenit says LE2125, and not 2123, both issues do not exist.
oneszero said:
i have noticed that whenit says LE2125, and not 2123, both issues do not exist.
Click to expand...
Click to collapse
just now read your previous post. DERP!
djsubterrain said:
Why would you post an issue with crDroid in a separate post instead of reporting it in the actual rom's thread?
Click to expand...
Click to collapse
I actually did post in the crDroid thread and got no response so then I made a separate thread
0siribix said:
I actually did post in the crDroid thread and got no response so then I made a separate thread
Click to expand...
Click to collapse
upon further testing,it only happens after cRDroid is flashed. Think it might have to do with the boot..img? Under the Model tab, I'm curious, what Platform does your phone say your is?
oneszero said:
upon further testing,it only happens after cRDroid is flashed. Think it might have to do with the boot..img? Under the Model tab, I'm curious, what Platform does your phone say your is?
Click to expand...
Click to collapse
It says lahaina
0siribix said:
I actually did post in the crDroid thread and got no response so then I made a separate thread
Click to expand...
Click to collapse
Opening multiple threads like this won't help but make this place worse. Did you try contacting the Developer in the device group chat? The majority of the devs nowadays use Telegram groups for communication between users/devs. Also, without providing proper LOGS, don't expect any kind of support or reply from a developer. Friendly advice.
ekin_strops said:
Opening multiple threads like this won't help but make this place worse. Did you try contacting the Developer in the device group chat? The majority of the devs nowadays use Telegram groups for communication between users/devs. Also, without providing proper LOGS, don't expect any kind of support or reply from a developer. Friendly advice.
Click to expand...
Click to collapse
In my defense, I opened a single thread, not multiple. When I didn't get a response for two days in the crDroid thread, I assumed that if I was going to get any support that a dev would ask for the logs or other info they need. I mean, what's the point of going through the trouble of obtaining logcat and uploading it just to be ignored
Also, FWIW, I searched around this forum and google for a while before I started this thread precisely to avoid this situation.
Anyway from what I'm gathering, it sounds like maybe LOS 19 for this phone is not quite ready. I think I'll flash TWRP and go back to crDroid 7 for a bit. I might try one of the AOSP variants but I've always leaned toward the LOS flavors in the past
It looks like All LOS based roms as well as TWRP and crDroid recovery are going to show a model of LE2123. It also looks like my MMS issues were caused by YAATA. It's either not compatible with Android 12 or with 5g/VoLTE etc. I ended up restoring back to factory using MSM tools and then installed one thing at a time until I narrowed it down to YAATA. Uninstalled and problem resolved