Related
Patch a ROM for LG G2 d800!
---- Supports Model d800 ONLY! ----
Lollipop ONLY!
What this is:
This patch can be flashed after flashing a full non-d800 ROM (DO NOT REBOOT AFTER FLASHING A NON-D800 ROM, even into recovery!) It changes the appropriate system files to the d800 variant version, as well as makes the proper build.prop changes. Note: If you use a vs980, ls980, l01f, or f320 specific ROM, there may be additional build.prop changes that need to be made. I didn't add all those because most of the development is on d80* models. Even if it is specific to these other models, patch will likely work just fine.
I took the basic idea from @dev>null (see here) I had previously dumped all of our stock, d80030f partitions. I took those dumps and combined them with the basic gist of this other patch dev>null made.
What changes this makes:
(1) Your entire bootloader is replaced. (a hybrid of 20y and 30f is applied)
(2) Stock lollipop 30f modem/baseband is installed.
(3) Stock lollipop 30f boot image, that has been bumped, is installed.
(4) Variant specific /system files are deleted. Then they are replaced with the d800 30f version of those files.
Installation:
(1) Boot into recovery, flash your desired ROM. (for my test, I used a d802 ROM)
DO NOT REBOOT RECOVERY, DO NOT!!!! If your ROM asks you to reboot after install, DO NOT!!!!!
(2) Flash this patch.
(3) That's it, you're done! It is okay to reboot now.
Note: Some ROMs might replace your /recovery partition, in which case you should re-flash your recovery before rebooting.
Troubleshooting:
SELinux / Bootloop
This patch properly sets permissions on the files it replaces. That being said, the boot.img in this patch is set to selinux ENFORCING. This means if the ROM you flashed does not have proper support for selinux to begin with, you'll get a boot loop, or hang on the glowing notification LED. Go yell at your ROM dev to fix it, or flash a boot.img that has selinux PERMISSIVE.
ROMs for models other than d80*
There are some additional build.prop changes that might need to be made if the ROM you want to use is f320/ls980/vs980/l01f. There isn't much development on ROMs specific to those models. I'll probably release a version 2 of the patch, eventually, to make these extra tweaks. However, it should work fine as is! The big exception is l01f ROMs. These ROMs are missing NFC files, so either NFC won't work, or the whole thing won't fail.
Major Thanks to:
dev>null
Download:
Did you read EVERYTHING above? If so, proceed -
https://www.gregtwallace.com/lg-g2/d800-rom-patch/
Shameless plug for donations:
Venmo Preferred (No Fee)
Zelle, send to [email protected]
Backup (Charges Fee)
Paypal
XDA:DevDB Information
d800 Lollipop ROM Patch, ROM for the AT&T LG G2
Contributors
blastagator
ROM OS Version: 5.0.x Lollipop
Version Information
Status: Stable
Created 2015-06-01
Last Updated 2019-12-31
Change Log
July 29, 2015 (v1.5) (LP 5.0.x)
-Do not flash misc partition. Not needed.
-Overwrites MAC addresses and things.
June 23, 2015 (v1.4) (LP 5.0.x)
-If /data/media exists, set the proper permissions and context
-DONT use TWRP to wipe Internal Storage after running the patch/fix. If you want to wipe internal, do so BEFORE the patch/fix.
June 23, 2015 (v1.3) (LP 5.0.x)
-Change version number to be same for both files (so skipped v1.2 for permission fixer)
-Updated to latest file_contexts from dorimanx
-FIX!!! - ROM Patch and SELinux Context patch both fix ntcode_listing.sh context
++First boot was hanging on completely clean wipe, d800 does not support context: ubject_r:ntcode_listing_exec:s0
++ntcode file only executes on first boot
++Add build prop tweaks to remove lines that cause execution of ntcode_listing.sh
++In case build.prop tweaks fail and file is executed for some reason, fix its permissions so d800 can execute
June 12, 2015 (LP 5.0.x)
-Permission fixer v1.1
-Fixes a couple of contexts (thanks @dorimanx)
June 11, 2015 (LP 5.0.x)
-Created zip that should fix all SELinux Context and allow boot to ENFORCED mode.
-Posted on my site as "LP ROM SELinux Context Fixer"
-Flash after ROM, ONLY IF SELinux ENFORCE doesn't already work!
June 4, 2015 (v1.2) (LP 5.0.x)
-Added automatic flash of d800 recovery - TWRP 2.8.6.3 (in case ROM overwrote recovery)
-Also posted:
++Added a flashable zip containing devnull's permissive boot.
++Removed my permissive boot, it wasn't working right. Sorry!
June 1, 2015 (v1.1) (LP 5.0.x)
-Supports conversion for Stock Lollipop ROMs from any LG G2 variant, except l01f and lgl22.
-I will probably never add support for those two models since development is very minimal on them.
-Also added other flashable zips to easily switch between ENFORCING and PERMISSIVE.
-Replacement files come from Stock Lollipop d80030f.
June 1, 2015 (v1) (LP 5.0.x)
-Initial Patch
-Fully supports all d80* and f320 ROMs.
-Will do update shortly to add support for converting ls/vs ROMS
-Replacement files come from Stock Lollipop d80030f.
[]
res3
Dude!!! You rock
Sent from my LG-D800 using XDA Free mobile app
Yeah!
Bro thank you! Not only for this, but everything you do for the g2!
thank you.. thank you... thank you.. thank you
So could I use the stock system partition from the d800 lollipop and run it with this?
Thank you very much @blastagator!
Now I can flash any AOSP rom and back to stock easyly. :XXX
I dont think there are any lollipop for L22. L22 is the lonely baby in G2 family without lollipop.
thanks
vannhut07vn said:
thanks
Click to expand...
Click to collapse
You're welcome. Now please kindly delete your quote of the entire OP...
@blastagator
would this patch work with CloudyG2 3.0?
Abrilabr said:
@blastagator
would this patch work with CloudyG2 3.0?
Click to expand...
Click to collapse
It should. If it doesn't boot, permissive-boot flashable would be needed.
You are awesome...insane.. Go on man..!!
Thanks a lot...
Gonna try hunting some Lollipop roms
Nicely Done....
man U R just great.......
thanks for the excellent work....
Hello friends greetings from Venezuela, where I can find a tutorial to update my LG G2 to lollipop, possess a model D800 20Y
@blastagator it's a great idea.Thank you for test with SRKG2
Sent from my LG-H818
it'll work with this rom ?
http://forum.xda-developers.com/lg-g2/development/rom-lg-g2-pro2-v5-final-acura-d802-d805-t3095500
LG Stylo 2 Plus K550 Stock Rom Unrooted/Tweak-less
I AM NOT RESPONSIBLE FOR ANY BRICKED DEVICES, BOOTLOOPS, NUCLEAR ANNIHILATION, OR SPONTANEOUS
COMBUSTION! YOU ARE CHOOSING TO FLASH!!!
What you need -
1) TWRP
2)A brain
What is this ROM?
This is the Stock ROM for the K550 Variant of the Stylo 2 Plus. This ROM is completely Stock for the exception of having Adoptable Storage available Out of the box, and Kernel Fixes To be used on K550 ONLY (I mean, you can try on the MS550 but I'm not sure if It will SimLock to Tmobile
How is this different from [K55010r Stock Rooted Odex for T-Mobile LG Stylo 2 Plus by pvsgh]?
1) This is a purely stock ROM extracted directly from KDZ, no mods at all
2) Kernel and Security fixes that ROM by pvsgh doesnt have, fixing ADB (which doesn't work on his ROM, which was the main reason I had to make my own since ADB is crucially needed for speedy builds in my line of work)
Also, @pvsgh, DM me if you want the boot.img to use for your ROM so you can fix these issues
Will you make this for Andrioid N, when it comes out as well? Will there be a De-odexed version? What about for the MS550?
Yes, I am planning on also having a completely stock ROM built from KDZ as soon as Android N comes out. I will only make a De-odexed version if there is demand for one. In order to make one for the MS550, I need testers first as I only have K550.
Did you give up on LineageOS?
No, I'm just waiting for Android N
How Do I install this ROM?
First of All, Download the ROM and Place it in a Directory where you can find it. Then Boot into Recovery, and Go to Install, and select the Downloaded Zip File in your Selected Directory. When prompted to, Flash. IMPORTANT! - IT IS RECOMMENDED TO FORMAT DATA (USING THE BUTTON THAT LITERALLY SAYS "Format Data" IN TWRP) IF ATTEMPTING A COMPLETELY CLEAN BUILD OR YOU MAY BE LOCKED OUT OF YOUR DEVICE AND CONTENT LOCK WILL NOT WORK ANYMORE
FEATURES
- Literally Stock
- No Mods
- No Root, No Busybox, and No Xposed Out of the Box (User Install-able)
-Custom Stock Kernel with ADB and Security fixesTo be Included
-Nothing
DOWNLOADS
Download Here
Changelog
Version - 1
Code:
[LIST]
[*]Initial Release
[/LIST]
Known Bugs
None, all Stock
If you like you can Donate (On my Profile) or Hit that thanks Button!
JvaOneShotzXprX said:
LG Stylo 2 Plus K550 Stock Rom Unrooted/Tweak-less
I AM NOT RESPONSIBLE FOR ANY BRICKED DEVICES, BOOTLOOPS, NUCLEAR ANNIHILATION, OR SPONTANEOUS
COMBUSTION! YOU ARE CHOOSING TO FLASH!!!
What you need -
1) TWRP
2)A brain
What is this ROM?
This is the Stock ROM for the K550 Variant of the Stylo 2 Plus. This ROM is completely Stock for the exception of having Adoptable Storage available Out of the box, and Kernel Fixes To be used on K550 ONLY (I mean, you can try on the MS550 but I'm not sure if It will SimLock to Tmobile
How is this different from [K55010r Stock Rooted Odex for T-Mobile LG Stylo 2 Plus by pvsgh]?
1) This is a purely stock ROM extracted directly from KDZ, no mods at all
2) Kernel and Security fixes that ROM by pvsgh doesnt have, fixing ADB (which doesn't work on his ROM, which was the main reason I had to make my own since ADB is crucially needed for speedy builds in my line of work)
Also, @pvsgh, DM me if you want the boot.img to use for your ROM so you can fix these issues
Will you make this for Andrioid N, when it comes out as well? Will there be a De-odexed version? What about for the MS550?
Yes, I am planning on also having a completely stock ROM built from KDZ as soon as Android N comes out. I will only make a De-odexed version if there is demand for one. In order to make one for the MS550, I need testers first as I only have K550.
Did you give up on LineageOS?
No, I'm just waiting for Android N
How Do I install this ROM?
First of All, Download the ROM and Place it in a Directory where you can find it. Then Boot into Recovery, and Go to Install, and select the Downloaded Zip File in your Selected Directory. When prompted to, Flash. IMPORTANT! - IT IS RECOMMENDED TO FORMAT DATA (USING THE BUTTON THAT LITERALLY SAYS "Format Data" IN TWRP) IF ATTEMPTING A COMPLETELY CLEAN BUILD OR YOU MAY BE LOCKED OUT OF YOUR DEVICE AND CONTENT LOCK WILL NOT WORK ANYMORE
FEATURES
- Literally Stock
- No Mods
- No Root, No Busybox, and No Xposed Out of the Box (User Install-able)
-Custom Stock Kernel with ADB and Security fixes
To be Included
-Nothing
DOWNLOADS
Download Here
Changelog
Version - 1
Known Bugs
None, all Stock
If you like you can Donate (On my Profile) or Hit that thanks Button!
Click to expand...
Click to collapse
Does this include the stock recovery?
puzzimassa said:
Does this include the stock recovery?
Click to expand...
Click to collapse
No, but I can try to get that as well from KDZ.
JvaOneShotzXprX said:
No, but I can try to get that as well from KDZ.
Click to expand...
Click to collapse
If it's not too much trouble could you upload the stock recovery for the k550? I'm trying to flash it back so i can do the ota update for nougat. Thanks in advance.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is a Official Build of madOS ( based on AOSP Oreo ) for Wiko Fever (2gb ram and 3gb ram) with MTK 6753 SoC and its clones:
Micromax Canvas 5 E481
Blu Life One X
Myphone 36
Qmobilez10
madOS is based on pure A.O.S.P. with many additional customizations and MediaTek support.
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Working:
RIL (Calls /SMS, Data connection, etc)
Wifi
Bluetooth
FM Radio
All Sensors
Lights;
Both storages & MTP
HW de/encoding
Camera (photos and video)
GPS & aGPS
Audio
madOS Extras (the features ya'all used too), plus, some new features we added on Oreo)
Not working:
XDA:DevDB Information
madOS_O_FEVER, ROM for all devices (see above for details)
Contributors
DerTeufel1980, fire855, superdragonpt
Source Code: https://github.com/MediatekAndroidDevelopers
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.x
ROM Firmware Required: unlocked bootloader, twrp
Based On: AOSP
Version Information
Status: Stable
Stable Release Date: 2018-03-19
Created 2018-03-13
Last Updated 2018-03-22
First time Install Instructions
0) Preparation
0.1) Backup your important data to PC
0.2) Ensure you are running Wiko Fever Android 6 already (also/especially when your device is not wiko fever, but a clone). If you are not, please update to it, before continuing here (replace the preloader from the wiko rom with your stock one, then use 'firmware upgrade' mode in sp flashtool. NEVER use 'format all + download')
Extra steps, if you are on blu life one x:
https://forum.xda-developers.com/showpost.php?p=76003104&postcount=81
0.3) Download “twrp_wiko_fever_oreo.img“: [url]http://www.mediafire.com/file/e96x8ltlyka392e/twrp_wiko_fever_oreo.img[/URL]
0.4) Download “madOS_8.1.0_fever_2018xxyy.zip“ [url]https://www.facebook.com/MediatekAndroidDevelopers/[/URL]
0.5) Optional, Download “Google Apps (aka Gapps)“: [url]http://opengapps.org/[/URL]. Choose: “ARM64“, “Android 8.1“, “nano“ or “pico“ package
1) Unlock bootloader (if not done already):
1.1) Boot for first time your device. I recommend to NOT register/login/add Wifi/add accounts/etc., because the unlock process DELETES all your data in the device. So to go more fast, skip all, and go directly to SETTINGS. In section ABOUT DEVICE, enable the developer options with eight time picks over “Build number”. Then in SETTINGS/DEVELOPER OPTIONS, enable the option “OEM unlocking” and “USB debugging” (if not enabled already), and choose to alollow usb debugging in the popping up window.
1.2) Boot the device in the BOOTLOADER mode (using ADB: "adb reboot-bootloader"). Execute in your computer the command “fastboot oem unlock”, say YES with “vol+” and “power” buttons. Then select reboot. This ERASES completely your device (factory restore), but the bootloader will be UNLOCKED! Two reboots needed.
2) Flash the recovery and boot to it. (choose option a) if you don't have another TWRP already installed, else choose b))
2.1a) Boot in the BOOTLOADER mode (using ADB: "adb reboot-bootloader").
Then execute command “fastboot flash boot twrp_wiko_fever_oreo.img”;
and then “fastboot reboot” (this is a trick to directly bring you to the newly flashed recovery. You can't boot up your current/stock rom at this point anymore).
2.1b) Boot to your current TWRP. Choose install --> image, and select “twrp_wiko_fever_oreo.img“. Then choose “recovery“ as the target. After few seconds, and succesful installation, hit “back“ several times, then go to “reboot --> recovery“
3) Install
3.0) Optional, but recommended: Go to "Wipe --> Advanced Wipe", click "Cache" and then "Repair or Change File system". Then select "Change File system" and choose "F2FS". Swipe to confirm.
Hit "back" three times (you can again choose a partition to change now). Choose "Data" and do as above.
Hit "back" several times, to get back to the main menu. Choose "Reboot --> Recovery".
3.1) While already in recovery (TWRP), connect your phone to pc, and copy “madOS_8.1.0_fever_2018xxyy.zip“ and the Google Apps to your phone.
3.2) Go to "Wipe", and directly slide the slider to the right.
3.3) Get back to main menu with the "back" button
3.4) Go to "Install" and hit “madOS_8.1.0_fever_2018xxyy.zip“, then uncheck all boxes and hit "Add more zips", now choose the Google Apps.
Confirm installation by swiping the slider to the right.
3.5) Reboot System
Click to expand...
Click to collapse
Follow up Install Instructions
Download rom and gapps
boot to recovery
flash rom and gapps
optional: flash superSu/Magisk
reboot system
General F.A.Q.
Q: What the hell is madOS ?
A: madOS, (M.A.D. Team OS), is a ROM based on pure A.O.S.P. with extended capabilities and customizations made by or merge/adapted by M.A.D. Team.
Q: Which recovery should I use for this ROM?
A: Latest M.A.D. TWRP 3.2.1-0 recovery for OREO 8.1.0
Q: How do i flash new recovery ?
A:
1: You can flash it with a scatter file
2: You can simply flash it from the existing twrp recovery: Install> Install image> Select Oreo TWRP> Select "Recovery" as partition to flash.
Reboot to recovery to use new one
Q: Do i need to make full wipes?
A: YES, dont come crying at me, if you didn't .... ;p
Q: What is "full wipes" ?
A: To Wipe : Cache; System; DATA ...
Q: What should i use f2fs or ext4?
A: Both are supported, choose the one you desire
Q: Does this rom have any Theme support
A: Yup, We have working Theme Engine (madOS extras)
Update: On Oreo 8.1.0:
- We have extended Theme support even further ( madLauncher, messaging, etc)
- As well as many fixes
Q: Some translations are missing for my language, can I help?
A: Sure you can, please check our translations repo available here , you can either do a pull request, or if you don't know how to work with git, sent us the XML. Strings for your language ( Check Readme on repo).
Q: I want to report a bug(s) do you have an issue tracker?
A: Yeah... madOS issue tracker
Q: What's working ?
A: Check first Post for current status
Q: App "x" doesn't work, why?
A: Probably not compatible with OREO yet, feedback is welcome
Q: Is the rom rooted?
A: NO, But you can easily root with :
1: Magisk ( v14 onwards.)
2: Super SU ( v2.82 onwards)
IF there are problems in rooting, you need to report it to the root-threads...There's nothing we can do
Q: Should i root together with rom ?
A: Not advised.. mainly the Magisk that gives some weird issues...
Flash ROM and GAPPS (if you use gapps), after first boot get back to recovery and flash your desire rooting method
Q: Does xposed work?
A: Is there Xposed for O? ... then no ;p
Q: How is battery life with Oreo?
A: Pretty awesome
Q: Does this build support Vulcan?
A: No....duh! v
Q: Does doze work in this build?
A: Yup
Q: when will (feature/issue here) be fixed?
A: NO ETA , please
Porting F.A.Q.
No porting support, no port questions allowed on this thread, and porting PMs will be auto-deleted, porting replies will be reported as well
G.APPS F.A.Q.
Q:What GAPPS package should I use?
A: openGapps arm64 nano/pico
Q: How to properly install GAPPS?
A:Flash Rom + Flash Gapps at once
CREDITS and Thanks
madOS Team
Our translators, credits list here
A.O.S.P.
Pure Nexus
AOSPA
DU (Dirty Unicorns)
Omni
HELP supporting madOS
We do this on our free time, however we do have costs on maintaining this :/
Any donation is highly appreciated
You can donate by using
this link
If the above doesn't work in your country, then you can directly donate by using this e-mail adress: [email protected]
About madOS Proprietary Apps
You are NOT allowed by any means, to use our madOS apps on any other build, your rom
This is exclusively for OFFICIAL madOS ROM releases
@To Moderators: Feel free to clean the thread, whenever users start spamming, severe OT, or questioning about porting...
Changelog 19th March 2018:
fixed offline charging
fixed proximity and light sensor
fixed applying smartwake settings after reboot
Facebook release post: https://www.facebook.com/notes/mad/rom-810-official-mados-wiko-fever-mt6753/1640799096003857/
for whatever reason, devDB is not working (very well) at the moment...causing this thread to be shown up, hours after i created it....now it's finally here and updated...and can be used
Thank u so much sir...we owe you?
superdragonpt said:
Android Oreo released
https://forum.xda-developers.com/android/development/rom-official-mados-wiko-fever-clones-t3762804
Click to expand...
Click to collapse
superdragonpt said:
The ROM was made using an Wiko device in the bring up
I know very well this TINNO devices, that are rebranded to many OEMs
In case of baseband (ie: BLU,Qmobile, MMX, you should use your stock baseband modem and place it under vendor/etc)
Cheers
PS: can you, that have other clones ( non-wiko) send us your working baseband?
(This way, we could perhaps just made an flashable zip for baseband or so)
Click to expand...
Click to collapse
Here is firmware folder(baseband) from Life One X with MM update.
Opened an issue about some sensors
https://bitbucket.org/maadteam/mado.../103/some-sensors-light-proximity-not-working
mrmazak said:
Here is firmware folder(baseband) from Life One X with MM update.
Click to expand...
Click to collapse
FERRARI81 said:
Opened an issue about some sensors
https://bitbucket.org/maadteam/mado.../103/some-sensors-light-proximity-not-working
Click to expand...
Click to collapse
Great
This .zip is pushing to system/etc, so this .zip won't work here on Oreo, where everything is moved to vendor/etc
For the time being for the blu, you can either updated the updater-script to push to "vendor" instead of "system" or root it, and move your baseband manually to vendor/etc
About the alsps ( brightness ) what's the sensor used in blu?
We need to enabled it I suppose
Cheers
superdragonpt said:
Great
This .zip is pushing to system/etc, so this .zip won't work here on Oreo, where everything is moved to vendor/etc
For the time being for the blu, you can either updated the updater-script to push to "vendor" instead of "system" or root it, and move your baseband manually to vendor/etc
About the alsps ( brightness ) what's the sensor used in blu?
We need to enabled it I suppose
Cheers
Click to expand...
Click to collapse
So the sensor.lib from Blu?
I will pull it and share.
superdragonpt said:
About the alsps ( brightness ) what's the sensor used in blu?
We need to enabled it I suppose
Cheers
Click to expand...
Click to collapse
Ehm...I have not blue, I have original Wiko Fever
And...I'm noob ...in wich way I could check what's the sensor?
FERRARI81 said:
Ehm...I have not blue, I have original Wiko Fever
And...I'm noob ...in wich way I could check what's the sensor?
Click to expand...
Click to collapse
just because adaptive brightness is not working , does not mean it is the sensor.
If sensor was not working , there is another test (check) you can do.
make a call, then put phone to head and see if screen goes off.
I had before when light sensor was not set correctly, when making a call the screen went black as soon as start a call, then could not get screen back on till 30 seconds after other end hung up the call.
I am away from my LOX now and for few days , so cant give direct test of light sensor.
attached just in case is usefull here are sensor libs from BLU-LOX. They are in /system/lib/hw and /system/lib64/hw.
I believe on oreo they go into /vendor/
Can we flash it over stock Lollipop ROM of Micromax Canvas 5 ??
I have a question that Can I flash it over the stock Lollipop ROM ?? existing kernel is 3.10.65.
Thanks
mrmazak said:
just because adaptive brightness is not working , does not mean it is the sensor.
If sensor was not working , there is another test (check) you can do.
make a call, then put phone to head and see if screen goes off.
I had before when light sensor was not set correctly, when making a call the screen went black as soon as start a call, then could not get screen back on till 30 seconds after other end hung up the call.
Click to expand...
Click to collapse
It doesn't work in call too : the screen is always on.
QUIZILLA said:
I have a question that Can I flash it over the stock Lollipop ROM ?? existing kernel is 3.10.65.
Thanks
Click to expand...
Click to collapse
Please remove the quote of the whole FAQ. This is totally useless to ask your question...
You need to flash wiko mm rom first
FERRARI81 said:
It doesn't work in call too : the screen is always on.
Click to expand...
Click to collapse
I'll check it today
Hello, I write from Padova, Italy,
I have the WIKO FEVER 3GB,I have the problem that after upgrading to MM (Android 6.0), device not connects to PC and no charge. The device is recognized ONLY if it turns off.
Can I do this update procedure with this problem?
I can not connect to the PC because device is not recognized. Can you help me? Can I root through an app installed by the playstore without using pc? Thank you so much for the answers.
Riccardo
ianto:
Rikadoo said:
Hello, I write from Padova, Italy,
I have the WIKO FEVER 3GB,I have the problem that after upgrading to MM (Android 6.0), device not connects to PC and no charge. The device is recognized ONLY if it turns off.
Can I do this update procedure with this problem?
I can not connect to the PC because device is not recognized. Can you help me? Can I root through an app installed by the playstore without using pc? Thank you so much for the answers.
Riccardo
ianto:
Click to expand...
Click to collapse
Why root? To update to oreo, you don't need root... But you still need to copy the new rom to your phone, as well as unlock the bootloader and install the twrp recovery. This needs to be done in fastboot mode by pc. I'd suggest to just try it
Unfortunately I am not very experienced, but I am very interested in solving my problem. I want to install this ROM, but without having to connect the device to the PC.
If I copy the ROM on the SD card. Can I then install?
I am in process of installing new oreo twrp and MADOS.
During install of TWRP, I loose adb authorization. (adb session is "unathorized")
in "prop.default" it has
Code:
ro.secure=1
security.perf_harden=1
ro.adb.secure=1
ro.allow.mock.location=0
ro.debuggable=0
is this intentional?
additional question,
Adb authorize connection window comes up multiple times even after putting check mark on remember this choice.
I think the adb auth problem is my pc, my other phone just started to do this too.
edit:
I have tried couple times to use blu firmware inside vendor folder. But not able to get baseband to be known.
tried just adding blu files ontop of original rom files.
tried removing rom files and adding blu files
tried removing whole folder then adding blu folder
each time I get unknown baseband.
I checked permission and ownership each way I tried and I set it to rw:r:r and root:shell just like original rom version, but not working for me.
One and more questions,....
1. Our bootloader is blocked or already unlocked?
2. If is locked, to unlock the bootloader of our device wiko fever which app I have to install?
3 if isn't locked, how I install a custom recovery like twrp manager?
4 how I boot the custom recovery twrp manager? Maybe if I switch off the device and reboot it, starts automatically the custom recovery?
5 at the end, from twrp can I flash the ROM Oreo?
AHH , last question, can I flash this ROM from my phone with Android MM?
mrmazak said:
I am in process of installing new oreo twrp and MADOS.
During install of TWRP, I loose adb authorization. (adb session is "unathorized")
in "prop.default" it has
is this intentional?
additional question,
Adb authorize connection window comes up multiple times even after putting check mark on remember this choice.
I think the adb auth problem is my pc, my other phone just started to do this too.
edit:
I have tried couple times to use blu firmware inside vendor folder. But not able to get baseband to be known.
tried just adding blu files ontop of original rom files.
tried removing rom files and adding blu files
tried removing whole folder then adding blu folder
each time I get unknown baseband.
I checked permission and ownership each way I tried and I set it to rw:r:r and root:shell just like original rom version, but not working for me.
Click to expand...
Click to collapse
Someone already uploaded vendor files for his model... Was it you? If not, please upload it for us
Paranoid Android is a custom ROM aiming to extend the system, working on enhancing the already existing beauty of Android and following the same design philosophies that were set forward by Google for Android Open Source Project.
Code:
* Your warranty is now void.
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
Compatible device?:
Code:
[LIST]
[*]All devices that use hi6250 chipset and use kernel 4.1.
[/LIST]
Mandatory:
* hit thank buttons, it's free.
* want more roms for P8 Lite 2017/P9 Lite 2017, simply bring me up beers by the following button.
Requirements:
TWRP.
Unlocked bootloader.
Unlocked FRP.
vendor.img: you must be on stock one, so don't wipe it because with other custom vendor.img will never ever boot.
This ROM is provided by CodeOfHonor
Installation Guide:
Make sure to the stock backup saved on pc, I'm not responsible for any bricked or damage.
Reboot to TWRP.
Go to Wipe.
Choose Advance Wipe.
Check on Data and change file system to EXT4, will not ever boot with F2FS.
Wipe cache, data, dalvik and system.
Flash the rom.
Reboot and have fun then.
Working:
Audio.
Bluetooth.
Camera: it's fully works with stock or other apps .
Display.
Graphis: both gralloc & hwcomposer.
Lights.
NFC.
RIL.
Sensors.
Storages.
Wifi
Bugs:
Dual sim might will not work all variants, so don't waste your time by asking me to fix it.
You don't like it?, easy revert to Emui 5.x.
Downloads:
**13/05/2018**
pa_hi6250-7.3.1-EOL-20180513.zip|500.4 MB
Changelogs:
**13/05/2018**
Boot with F2FS without problems.
Fix Magisk.
Source Code:
Device Tree:
https://github.com/codeofhonor-dev/android_device_huawei_hi6250
Kernel GPL:
https://github.com/codeofhonor-dev/android_kernel_huawei_hi6250
Vendors:
https://github.com/codeofhonor-dev/android_vendor_huawei_hi6250
XDA:DevDB Information
AOSPA Paranoid for Hi6250, ROM for the Honor 6X
Contributors
haky 86, HassanMirza01, felix-development
Source Code: https://github.com/codeofhonor-dev, Meticulus and the stuff of CodeOfHonor.
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 4.x
ROM Firmware Required: Emiui 5.x
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: 7.3.1
Stable Release Date: 2018-04-27
Beta Release Date: 2018-04-27
Created 2018-04-27
Last Updated 2018-04-27
ROM stuck at animation boot?
this because you must change the file system from F2FS to EXT4 to done boot process
* reboot to TWRP.
* go to Wipe -> Advanced Wipe.
* check Data -> Change file system -> select EXT4.
* swipe the screen to wipe it .
How can I fix Sim?
* go to Settings -> Extras -> disable "Sim Card Slot2 " and reboot.
How can I enable Google Codecs
* go to Settings -> Extras -> enable "Use Google H264" (it's a bit laggy but better than nothing).
How to enable Double Touch To Wake?
* go to Settings -> Extras -> enable "Double Touch to Wake"
Should I reflash the vendor partition if come from other roms?
* if you coming from Emui 5.x, the answer is no because the custom rom are based on Emui 5.0 source code, so all you
have to is flashing your favorite custom rom
Audio and camera are not working?
* bring up a logcat to help us, instead of writing useless comments.
I got error 7, how can I fix that?
* use my own TWRP recovery. or you can simply remove the whole assert line in the updater-script file inside the META-INF folder save and re-flash.
How can I fix RIL Crashes
flash root.
Copy the phone.prop into /system/vendor and /vendor.
reboot, now you should able to do calls for more than 2 minuts
Calls still crash even with fix SIM
Run adb shell and type the following command xxd /sys/firmware/devicetree/base/hisi,modem_id .
the result will be something like the following out ( for single sim devices):
1|hi6250:/ $ xxd /sys/firmware/devicetree/base/hisi,modem_id
00000000: xxxx x000 ;xx.
Click to expand...
Click to collapse
Search for your xxxxx000, and setup the following flags .
ro.config.client_number=1
ro.config.modem_number=1
persist.dsds.enabled=false
persist.radio.multisim.config=dsds (remove it properly)
for dual sim devices just edit these 2 flags:
ro.config.client_number=1
ro.config.modem_number=1
Save and reboot.
I'm coming from EliteRom 7.5 and I love AOSPA but there are 2 little problems I have with this rom.
First of all fingerprint doesn't work correctly, no matter how often I press my finger on the sensor it stays at the ~10% mark.
The other problem is that I don't know how to root this rom. I tried installing magisk manager and flashing the zip but I get error 1 in TWRP.
Except this issues it's working very nicely on my device.
Thanks in advance for helping me out
MadMurl0c said:
I'm coming from EliteRom 7.5 and I love AOSPA but there are 2 little problems I have with this rom.
First of all fingerprint doesn't work correctly, no matter how often I press my finger on the sensor it stays at the ~10% mark.
The other problem is that I don't know how to root this rom. I tried installing magisk manager and flashing the zip but I get error 1 in TWRP.
Except this issues it's working very nicely on my device.
Thanks in advance for helping me out
Click to expand...
Click to collapse
10% mark?
Did you entirely remove all the fingerprints before flashing this Tom?
Go back to Elite or Stock, remove all fingerprints and reinstall the Rom
For Root, you can try changing recovery or using an older version of Magisk that worked for you
I am currently reverting back to stock and will try to flash the rom again, I guess I didn't remove the fingerprints before flashing.
I tried Magisk Version 15 and 16 which both worked on EliteRom, I even tried SuperSu which didn't gave me an error message in twrp but It didn't work tho. After flashing the zip there was no "SuperSu" App so I downloaded it from the playstore, the app told me "root not found". Do you know what the cause of this could be?
Edit: Fingerprints are working now But root still doesn't
After I downgrade from emui 8 to emui 5 in 5 minutes now I can fix this rom so expect a build within these days
hoping to try this rom , following for updates
Hey guys I just installed the rom, but I did notice that I don't have access to any Gapps. How to I install them? I'm using TWRP. I was just able to get my unlock code from Honor today, so I unlocked and rooted, and flashed your rom as the first thing, so I'm running a fresh flash of the latest version.
Flash package with Twrp: https://opengapps.org/
Thanks guys, I realized that yesterday right after I posted lol. So far I'm really loving the plain stock-ness of this rom, hopefully it give the device some more life so I won't have to upgrade soon.
MadMurl0c said:
I am currently reverting back to stock and will try to flash the rom again, I guess I didn't remove the fingerprints before flashing.
I tried Magisk Version 15 and 16 which both worked on EliteRom, I even tried SuperSu which didn't gave me an error message in twrp but It didn't work tho. After flashing the zip there was no "SuperSu" App so I downloaded it from the playstore, the app told me "root not found". Do you know what the cause of this could be?
Edit: Fingerprints are working now But root still doesn't
Click to expand...
Click to collapse
Yeah I'm having the same issue to, with no root.
Can someone tell me why this rom is different to all others ? Why is this one using stock vendor and can we easy revert to Emui ? Why don't all others ?
I'm on stock now.
How is the quality of the photos compared to stock rom? It is possible to install Emui camera or other huawei cameras?
** Note **
developments of hi6250 is end reason: switch to another phone, have phone.
** Note **
Developments for hi6250 has been resumed but just for this ROM, sorry for the inconvenience.
I'm already downloading the source for releasing new build but AOSPA will take a wile since have bigger source.
** Note **
Downloads:
**13/05/2018**
pa_hi6250-7.3.1-EOL-20180513.zip|500.4 MB
Changelogs:
**13/05/2018**
Boot with F2FS without problems.
Fix Magisk.
Had anyone tried installing Xposed yet?
Support BLL version? Honor 6X
The rom overall is great and smoorh, even F2FS works now
But somehow magisk still doesn't work. It says
Code:
! System installed root detected, mount rw :(
when I try to flash the magisk.zip file.
MadMurl0c said:
The rom overall is great and smoorh, even F2FS works now
But somehow magisk still doesn't work. It says
Code:
! System installed root detected, mount rw :(
when I try to flash the magisk.zip file.
Click to expand...
Click to collapse
Guys to flash magisk or superSU use Meticulus TWRP, other twrp like eliteTwrp show an error when it is recompilling the boot.img
Disclaimer:
LineageOS (Lineage Android Distribution) members or anyone else on this website is not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in the products you find here before flashing it! YOU are choosing to make these modifications, and if you point the finger at us for messing up your device, we will laugh at you. Your warranty will be void if you tamper with any part of your device / software.
How to Install:
1- BACKUP, BACKUP, BACKUP, All will be WIPED!
2 - Unlock bootloader instructions here
3 - Flash the new mandatory TWRP Recovery
4 - Move Rom & Gapps (optional) into device storage
5 - Full Wipes
6- Flash Rom & Gapps (gapps are OPTIONAL)
for GAPPS:
Choose Gapps Package "ARM" > "6.0" > "Pico" or "Nano" visit OpenGAPPS
Working:
Boots
Storages
Bluetooth
Wifi
GPS - GNSS
Audio
Charging
Offline Charging
Video decoding/ Playback (i.e.: Youtube) up to 720p
android marshmallow new features: Adoptable Storage / Multi Window / etc
DRM Widevine : For Netflix, Amazon Prime, etc
Sensor: magnetometer: akm8963
Front Camera: mt9m114_mipi_raw
Front camera: GC0339_RAW
etc ....
NOT Working:
Rear Camera: a5142_mipi_raw
Front Camera: GC0339_RAW (ME173X 8GB) Fixed on build 20220629
Sensors: accelerometer (autorotation)
You tell me
Special Thanks
OMNI Rom
LineageOS
DerTeufel1980 & fire855 ( my Team mates from M.A.D)
GPL Compliance:
GitHub - dragonpt/android_device_asus_me173x: ASUS ME173x device for LineageOS 12.1 & LineageOS 13
ASUS ME173x device for LineageOS 12.1 & LineageOS 13 - GitHub - dragonpt/android_device_asus_me173x: ASUS ME173x device for LineageOS 12.1 & LineageOS 13
github.com
GitHub - dragonpt/android_kernel_asus_me173x_new: ASUS ME173x [MT6589 - MT8125] Custom Kernel for LineageOS 12.1 / 13 / 14.1
ASUS ME173x [MT6589 - MT8125] Custom Kernel for LineageOS 12.1 / 13 / 14.1 - GitHub - dragonpt/android_kernel_asus_me173x_new: ASUS ME173x [MT6589 - MT8125] Custom Kernel for LineageOS 12.1 / 13 / ...
github.com
--> "asus_mm" branchs
FAQ
Small FAQ:
Q: How can i Unlock the Bootloader?
A: Instructions for Unlocking the Bootloader can be found here
Q: After locking the screen, the screen is all black, and/or flickering and I'm forced to reboot, how can I fix this?
A: If you have this issue, then your device uses the second screen/lcm hardware revision
( the lgld070wx3_dsi_vdo ), please use the second kernel.zip for this variant, it'll be added an second kernel . zip for people with this variant, on the download section with the ROM release
Q: how to flash this second kernel for the new hardware variant ?
A: After flashing the ROM, flash the second kernel afterwards
Q: Where are the Developer Options?
A: Go to Settings>About Tablet, and tap 7 times on the Build Number
Q: Where is the multi-window mode?
A: in the developer options, you can enable it there
Q: How can i root this rom?
A: you can use Magisk , or SuperSU
Magisk: v.23
SuperSu v2.82
note: Magisk builds v24.x and v25.x do NOT work.
Q: Do i really need to update recovery?
A: YES
Q: I can't flash this Rom on recovery, why?
A: You need to update your recovery to TWRP
Q: how to work with twrp?
A: in the first time TWRP boots, it'll ask if you want to allow modifications, slide to YES
Q: how to wipe and flash in twrp?
A: Go "mount" and mount "system"
then go "wipe" > and wipe dalvik / cache / data / System
Q: How can i flash the new recovery?
A: If you already have an custom recovery installed:
Download the new TWRP recovery zip
flash the new recovery
reboot to recovery again, TWRP should be now installed
If you don't have any custom recovery installed:
- You can extract the "recovery.img" from the .zip
- Open an terminal
- Boot to fastboot mode, and type:
Code:
fastboot flash recovery recovery.img
then reboot:
Code:
fastboot reboot
Q: I Love your work, how can i thank you?
A: You can press the "Thanks" button, and if you wish, you can pay me a beer
..
Changelogs
Build 20201221
First Release
Build 20210821
Kernel:
DCT / Power resolve more issues
LCM: nt35521_dsi_vdo: Add backlight enable ctrl function
Fix magnetometer sensor: akm8963
Battery: Corrections
Camera LENS AF (for the rear camera) fixed
Front Camera : mt9m114_mipi_raw ( ME173X 16GB Version) fixed
mmc: more handling fixs
msdc: more fixs
Touch Panel: GT927: Implement a proper suspend & resume
Some other small fixs.
LineageOS source and device:
LineageOS LiveWallpapers, Wallpapers are now included ( as per-user requests)
Gello browser removed, it's depricated and has security risks
Disable Live Display by default (not supported by this device)
Some device clean up
Fix some eGL crashs
Fix some core missing symbols
Added Front camera support ( Pictures )
Some other small fixs.
Build 20220629
Kernel:
Security: Fix the following security issues:
PG SU daemon security fix
CVE-2017-1000365
CVE-2017-2618
CVE-2017-2671
CVE-2016-10208
CVE-2016-10208
CVE-2013-4312
CVE-2016-2550
CVE-2017-9074
CVE-2017-9075
CVE-2017-9076
CVE-2017-9077
CVE-2017-9242
LVT-2017-0002
CVE-2012-6703
CVE-2015-8944
CVE-2016-3857
CVE-2016-9555
CVE-2017-8890
ARM: spectre-v1
ARM: spectre-v2
ARM: Merge some bug fixs
imgsensors:
mt9m114_mipi_raw: Enable NightMode & Improve NightMode handling (better handling of Low light pictures)
gc0339_raw support added (CMOS front camera used in some HW revisions)
Memory management / Others:
Merge ZRAM from Kernel 3.10 version, and backport K 3.10 ZRAM fixs
Merge zsmalloc from Kernel 3.10 version, and backport K 3.10 ZRAM fixs
Add support for LZ4 decompression in the Linux Kernel
Other minor fixs
LineageOS source and device:
device: Added 512 MB Virtual SWAP Memory
Fix GPU PowerVR blobs crash, leading to random reboots & wakeup reboots
Disable OpenGL preloading with PowerVR drivers
SHIM: Add UI shim lib to fix some other random crashs
Remove max app limit
ART: Increase and fine tune the heap limit
Camera & nvram blobs fixs
Other minor fixs
Build 20220718
Fixed Bluetooth, that got broken by mistaque on 20220629 release
Downloads
TWRP 3.1.1
TWRP_3.1.1_ME173X.zip | by superdragonpt for Generic Device/Other
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
Build 20220718
https://androidfilehost.com/?fid=15664248565197191338If you have the second hardware Screen revision by LG (check FAQ), flash this
kernel for the Build 20220718
https://androidfilehost.com/?fid=15664248565197191342
Old Builds
Build 20220629
https://www.androidfilehost.com/?fid=15664248565197184858If you have the second hardware Screen revision by LG (check FAQ), flash this
kernel for the Build 20220629
https://www.androidfilehost.com/?fid=15664248565197184860
Build 20201221
lineage-13.0-20201221-UNOFFICIAL-me173x.zip | by superdragonpt for Generic Device/Other
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
If you have the second hardware Screen revision (check FAQ), flash this
kernel for the Build 20201221
Kernel_rev2_Build_20201221.zip | by superdragonpt for Generic Device/Other
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
Build 20210821
https://www.androidfilehost.com/?fid=7161016148664790672If you have the second hardware Screen revision by LG (check FAQ), flash this
kernel for the Build 20210821
https://www.androidfilehost.com/?fid=7161016148664790675
Man, you're awesome
But I have issue with wifi. Cant turn it on and my mac adress is 02:00:00:00:00
Bluetooth also not working
gadom92 said:
Man, you're awesome
But I have issue with wifi. Cant turn it on and my mac adress is 02:00:00:00:00
Click to expand...
Click to collapse
Same here
Awesome work, thx and merry xmas
gadom92 said:
Man, you're awesome
But I have issue with wifi. Cant turn it on and my mac adress is 02:00:00:00:00
Bluetooth also not working
Click to expand...
Click to collapse
This seems to be the very same issue some users had with Lineage 12.1...
can** replicate this on my units.
EDIT: i meant, can't replicate this
please try this:
[ROM] [UNOFFICIAL] LineageOS 12.1 |ASUS Memo Pad HD 7 (me173x) [MT8125]
Disclaimer: LineageOS (Lineage Android Distribution) members or anyone else on this website is not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if...
forum.xda-developers.com
Settings > Backup & reset
superdragonpt said:
This seems to be the very same issue some users had with Lineage 12.1...
can replicate this on my units.
please try this:
[ROM] [UNOFFICIAL] LineageOS 12.1 |ASUS Memo Pad HD 7 (me173x) [MT8125]
Disclaimer: LineageOS (Lineage Android Distribution) members or anyone else on this website is not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if...
forum.xda-developers.com
Settings > Backup & reset
Click to expand...
Click to collapse
Did not solve the problem so far. Wifi is even broken after restoring the los 12.1 backup which worked before
Edit: uploaded logcat
Ok, i reflashed the old carliv recovery via fastboot after installing Los13 and i got wifi back ...
And afterwards i flashed twrp again via fastboot and wifi is still working...
Previously i flashed the twrp zip from carliv, i guess this was part of the problem
reflashing recoveries in fastboot not worked for me :/
I also wiped everything including internal storage before, and bootet into each of the two recoveries and to the system from there.
Maybe the carliv recovery changes some things on the system, idk.
Hi, I am so glad that this is still alive project
I upgraded recovery via mtk flesher. Just rename twrp 3.1.1... into recover.img and click "download".
My wifi and bluetooth are working. Sometimes bluetooth have conflict with wifi and plain reboot fix things.
It is strange that not a single one sensor work(acceleration and gravity, magnetic field, orientation and rotation. They all worked in 12.1 beside rotation. Hope thing are going to get fixed up.
Had a few freezes also(hard reset do the job)
Overall I have a feeling that this is smoother than 12.1.
EDIT: It was misleading about recovery flash. You need to extract from twrp_3.1.1_ME173X.zip "recovery.img" and replace in folder where scatter file with old "recovery.image" is.
Gronkdalonka said:
I also wiped everything including internal storage before, and bootet into each of the two recoveries and to the system from there.
Maybe the carliv recovery changes some things on the system, idk.
Click to expand...
Click to collapse
interesting... likely the wiping of internal storage fixed it..
if anyone is having this issue, please try and report back if the following fixs:
in twrp:
Flash this test kernel
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.
www.androidfilehost.com
cheers
Merry Xmas
superdragonpt said:
interesting... likely the wiping of internal storage fixed it..
if anyone is having this issue, please try and report back if the following fixs:
in twrp:
Flash this test kernel
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.
www.androidfilehost.com
cheers
Merry Xmas
Click to expand...
Click to collapse
not working :/
edit: Flashed old recovery trough Flash Tool, than TWRP in Flash tool wipe all what i can and then install LOS 13. Wifi working like a charm
Any chance you can help with source patches?
First of all thanks to snapdragon for the new LOS13 support.
I'm sorry to tell you that all of your mentioned ways to get WiFi back to work did not work for me. What I did and what I tried:
Normal installation way:
Flashed new recovery via old custom recovery
complete wipe
flashed new LOS13 via new TWRP recovery
WiFi not working!
Going back to old custom recovery and back to TWRP
Flashed old custom recovery via TWRP
complete wipe
flashed new TWRP custom recovery via adb sideload since my sd card can only be mounted via new TWRP recovery
complete wipe
flashed new LOS13
WiFi still not work!
This is all I did. I realized that fastbood mode is not working for my device, could be a driver problem since my device is installed as ùó something when plugging it into the pc in fastboot mode, so I tried the way via adb.
Hint: I have the model with the alternative hardware, so the second kernel is required to fix flickering display issue.
I realized that the new TWRP recovery has this issue aswell, so my display is flickering from the right side to the center sometimes in TWRP recovery.
Any ideas what could help getting WiFi back to work?
Thanks in advance!
Edit: Could it be that this WiFi problem has something to do with the following thread:
FIX FOR MAC 02:00:00:00:00(WiFi and hotspot not turning ON)
Important. Root required..... Hey everyone,I saw so many posts regarding Android & iOS that the Mac address is changing to 02:00:00:00:00 and WiFi is greyed out. None of the WiFi or hotspot not turning on.I get the same problem in my Condor and...
forum.xda-developers.com
I read over some postings and googled the mac address 02.00.00.00.00 and it seems that a lot of devices had this problem when updating from android 5 to 6. It seems that it could have something to do with the partitions where the info (mac address, IMEI) are stored, but in general I have not found a solution and a specific description of the problem.
Anyway: If the problem can be solved by doing the steps described in the thread I provided above I’m not able to solve this. I would not describe me as a noob, but it seems that I need root and knowledge of permission management for the fix, and I am not very familiar with Linux.
Could you do the following test:
In twrp:
Full wipes ( system, etc etc and internal storage) be sure you back up your stuff
Then reboot to recovery
( It'll warn there's no OS installed)
Back to recovery
Do full wipes again , plug the tab into pc and copy the rom to internal storage
Reboot to recovery again
( It'll warn again, there's no OS installed)
Proceed to flash the rom
This has worked with a user
Issue: for an unknown reason some devices seems to fail mounting / reading nvram
@ twrp I'll do a build for people with this second hardware revision, flickering is annoying...
Thanks for your fast reply.
I did two full wipes with rebooting into recovery after each wipe as you said, then I copied the OS zip file to internal storage and rebooted again to recovery.
After installing the ROM I rebootet to system and LineageOS was preparing the first start. I started without flashing the kernel for alternative hardware (2nd kernel) to check if it works first.
I'm sorry to tell you that I still got no WiFi and Bluetooth connections, Mac address still is shown as 02-00-00-00-00, WiFi cannot be turned on.
Edit: Seems that is has nothing to do with wipes (on my device). I've tried all kind of wipes via TWRP
Format Data -> yes -> reboot to recovery
Advanced Wipe -> check all (Davlik, Cache, Data, Internal Storage, System -> Again format data -> Yes -> reboot to recovery
flashed ROM, 2nd Kernel and GApps -> Reboot to recovery -> reboot to system
Still no WiFi. Perhaps I should try to go back to stock rom and see if WiFi works there? Do you think this could make the deal?
test this
full wipes
flash rom, then this kernel afterwards
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.
www.androidfilehost.com
Again, thanks for your efforts, it seems to be a really tough and bugging one, since the new kernel did also not fix the problem.
Edit: Just to keep u updated: I just flashed old recovery and afterwords old LineageOS 12, WiFi is working well. So there must be some problem with the update or the update process. I will try to wipe first and then install new recovery and again install new OS, perhaps this will do the job.
Edit2: BTW I forgot to tell you that I had problems with settings -> about tablet -> status on lineageos 12. Just remembered because i wanted to have a look to the mac address. I get an error telling me "unfortunately, settings has stop". Perhaps important for the update?
Important Edit3:
Guess what: I made it to work. I did the following to do it:
1. Format Data and do all wipes possible with TWRP recovery. Reboot to recovery and do the same again.
2. TWRP recovery -> install old recovery
3. In old recovery -> install via sideload (adb sideload) lineageOS12 and second Kernel (for me because of hardware)
4. Boot to system and check if WiFi works well (finish the initialization of the device and connect to a WiFi)
5. Boot to recovery (old recovery) -> WITHOUT WIPING install via sideload TWRP recovery
6. Boot to system. (Still lineageos12) check if WiFi still works
7. Boot to TWRP recovery -> WITHOUT WIPING install lineageos13.
8. Boot to system, finish initialization if necessary and check if WiFi still works.
9. Go to setting and do a factory reset from lineageos13 settings
10. Device will reboot to recovery and do the factory reset and automatically will boot back into system.
11. Finish. All should work now.
I don't know what exactly did the job, so I wanted to provide all steps I did.
Since I never flashed an android custom Rom over another without wiping I don't know what errors this procedure can cause. So if someone knows that please let me now that I can have a look if there are errors.
Thanks again for your assistance.