Hi,
I updated this tablet using Lenovo Smart Upgrade Assistant - update to TB_8504F_USR_S001019_1909091114_Q12000_ROW seems fine except my Wifi/WLAN is totally dead.
If I turn it on, it looks turns back to off quickly, but never actually turns on, and sometimes tablet hangs for a while sometimes when I try to turn wifi on.
I saw a previous post where someone also had this problem and solved it by flashing a modded ROM then flashing the stock ROM and Wifi worked again (with a strange MAC address after that procedure)
But I am stuck because the option to enable OEM Unlocking in Developer Options is greyed out - underneath it says to Connect to the internet or contact your carrier.
I have tried unlocking via ADB but this does not work either.
If I go into settings, WLAN Preferences, it says my MAC Address is 02:00:00:00:00:00 which seems to match other people with this problem.
I tried installing a terminal emulator, "ip link show" returns request send failed: Permission denied, "ip link" says I have:
1: lo:
2: duumy0:
3: [email protected]:
I don't have wlan0 or wlan1, and lo/dummy0/[email protected] did not show the 02:00:00:00::00:00 address.
Please does anyone have any ideas for me?
If I cannot get wifi working, is there any way I can connect to internet using USB to my PC?
I eventually found a version of QFIL that works (part of the QPST package) https://droidfilehost.com/download/download-qpst_2-7-480/
I found a ROM https://drive.google.com/file/d/1C1Fd5m7BMLqrhURAj0kWdqeiZGIuU95k/view (password: https://firmware247.com)
It seems to have downgraded, but now when it starts, I get the screen where I can choose location, and after a few seconds it reboots.
RobinGill said:
I eventually found a version of QFIL that works (part of the QPST package) https://droidfilehost.com/download/download-qpst_2-7-480/
I found a ROM https://drive.google.com/file/d/1C1Fd5m7BMLqrhURAj0kWdqeiZGIuU95k/view (password: https://firmware247.com)
It seems to have downgraded, but now when it starts, I get the screen where I can choose location, and after a few seconds it reboots.
Click to expand...
Click to collapse
Please try to format data (if you don't have important data in the device) and reboot. If that doesn't help, download latest firmware (S001031). You can also try a custom ROM. Below are links to them:
LineageOS 16.0 (Android 9)
LineageOS 17.1 (Android 10)
Resurrection Remix OS (Android 10)
crDroid (Android 10)
adazem009 said:
Please try to format data (if you don't have important data in the device) and reboot. If that doesn't help, download latest firmware (S001031). You can also try a custom ROM. Below are links to them:
LineageOS 16.0 (Android 9)
LineageOS 17.1 (Android 10)
Resurrection Remix OS (Android 10)
crDroid (Android 10)
Click to expand...
Click to collapse
Thanks for the reply.
Unfortunately I can't load any custom ROM's because my bootloader is locked.
I downloaded twrp-3.2.3-0-tb_8504x.img and renamed that to recovery.img and put in the folder with the rest of stock ROM and reflashed the downgraded stock ROM (TB-8504F_S000029_170518_ROW_QFIL) but same problem, and I still have normal recovery, not TRWP so I can't load custom ROM's.
Any chance you can please share a link to S001031 please to see if that helps?
I just tried flashing stock ROM TB_8504F_USR_S130004_1902221150_Q12000_SCP and now OEM Unlocking is not greyed out, but I'm still stuck with Android Recovery instead of TRWP. Hopefully will have fun tomorrow.
Ok, today installed TWRP 3.3.1-0 and tried various ROM's but still no luck:
crDroidAndroid-10.0-20210731-TB8504-v6.20 Boot logo loop
RROS-Q-8.6.9-20210519-TB8504-Unofficial Boots but no wifi or bluetooth
RROS-Q-8.7.1-20210726-TB8504-Unofficial Boots but no wifi or bluetooth
lineage-16.0-20200319-UNOFFICIAL-TB8504 Boot logo then rebooting to TWRP
lineage-17.1-20210408-UNOFFICIAL-TB8504 Boot logo then rebooting to TWRP
All current official firmwares for TB8504F:
TB_8504F_S110006_181015_YZ Boots but no wifi or bluetooth
TB_8504F_S140008_190215_UK Boots but no wifi or bluetooth
TB_8504F_USR_S120010_1901181601_Q12000_HFT Boots but no wifi or bluetooth
TB_8504F_USR_S130004_1902221150_Q12000_SCP Boots but no wifi or bluetooth
TB_8504F_USR_S001019_1909091114_Q12000_ROW Boots but no wifi or bluetooth
Anyone got any ideas for me?
Damn, somehow ended up with tablet bricked and now I have 900E Diagnostics connection. Trying to use a deep flash cable to get it into EDL mode but doesn't seem to work for me.
Deep flash cable didn't work.
Found a Yourtubr clip about changing the Qualcomm driver from 900E to 9008 - didn't work.
But found a video on the internet that got me out of trouble.
In the clip it says to leave the battery unplugged - that did not work for me. I needed to short the test points, plug in USB, then connect battery and it's flashing again in 9008 mode.
After flashing I had to disconnect and reconnect the battery to get it to boot normally.
Looks like I will be back where I was a day or two ago.
Interesting - when I recovered using TB_8504F_S110006_181015_YZ I now have wifi again - I'm not sure if I'm going to just leave it like this or play around further.
RobinGill said:
Interesting - when I recovered using TB_8504F_S110006_181015_YZ I now have wifi again - I'm not sure if I'm going to just leave it like this or play around further.
Click to expand...
Click to collapse
can you post download link? I have the same problem with wifi
thanks
I have just found TB_8504F_S110006_181015_YZ, will be a day or two for me to upload and send you the link.
Here is the link - it will be active for one week, then I will take it down as I have limited storage.
3.24 GB folder on MEGA
145 files
mega.nz
thanks! I´ll try it later
RobinGill said:
Here is the link - it will be active for one week, then I will take it down as I have limited storage.
3.24 GB folder on MEGA
145 files
mega.nz
Click to expand...
Click to collapse
brother can you please re-upload it.
RobinGill said:
Here is the link - it will be active for one week, then I will take it down as I have limited storage.
3.24 GB folder on MEGA
145 files
mega.nz
Click to expand...
Click to collapse
bro pls can you upadated the link pls
3.24 GB folder on MEGA
145 files
mega.nz
Related
Hi everybody - any help with the following problem is appreciated, I've thrown everything I can find at it but I'm just over my head at this point!
My LG G watch worked great, up until one morning when it got stuck in a bootloop - if I had to guess, the battery must have run out at the exact wrong time, during an OTA update. Maybe. Anyway, stuck in a bootloop.
I managed to install TWRP bootloader, and apparently uninstalled everything but the TWRP bootloader, as it now has the 'no OS installed!' dialogue whenever I try to exit.
I had minimal success installing ADP drivers, but never managed to make a PC/watch connection past fastboot OEM unlock. At the moment (a few months after i had that working) my PC doesn't recognise the watch at all.
So I've bought an OTG cable, and the plan is to put a flashable ROM (hey, even the stock one if I can find it) on a USB stick, navigate to it on TWRP via install, and take it from there. Anyone know if that's what I should be trying / where I can find that particular ZIP file?
Also worth noting, I never toggled on ADP debugging when the original OS was working.
Here's the info from the fastboot screen- ANY help is appreciated!
Product Name = Dory
Variant = dory 4GB
HW Version - rev_11
Bootloader Version - Doryz11c
Serial Number - 03b1175b02a23642
MSN - 406KPMZ0096923
Signing - production
Secure boot - enabled
Lock state - unlocked
Have you tried the instructions of the thread about fixing adb after the update? May work for you. I don't think the watch supports OTG...
http://forum.xda-developers.com/showthread.php?t=3347122
Use this tool for flashing:
http://forum.xda-developers.com/g-watch/development/script-lg-g-watch-tool-t2820863
Should have asked months ago
MihaiSG said:
Use this tool for flashing:
http://forum.xda-developers.com/g-watch/development/script-lg-g-watch-tool-t2820863
Click to expand...
Click to collapse
Mate... worked a dream. Thanks so much!
World first recovery flashable ROM for android TV boxes!
WARNING: This rom is under heavy development. There are bugs, bootloops and internal issues.
STRICTLY A DEVELOPMENT THREAD.
For a stable rom check out PoisonRom
A lot of effort and research was put into this device and will be put into the Amlogic ROM tool(A tool for creating roms for Amlogic devices(any android version)) so consider making a donation to me or buying me a beer by clicking on my name a clicking the "Donate to me" button!
Our TV Boxes are finally treated like standard android devices from this point on!
So here it is, this ROM is for the T95Z Plus 2/16GB variant, its stock 7.1.2(not 7.1.1) ported from the 3/32GB variant!
MAKE SURE YOU HAVE THE TWRP RECOVERY!
Here are instructions to install TWRP if you havent already.
Recovery
So far we have a working recovery(TWRP) thanks to @rrvuhpg
You can download it from HERE for the 2/16GB T95Z variant(Mirrored and renamed custom-recovery.img for the sake of flashing instructions)
Flash instructions
1. Download ADB and install it on your pc(not explaining this, there are 5 second installers) then open a command prompt in the directory of the custom recovery
2. Enable USB debugging, go to settings>about and click build number about 10 times, then go back to the main settings menu and you will see developer options, enter it and check allow USB debugging.
3. Connect to your device via IP address. go to settings>about>status and get your IP address. it should be something like 192.168.25.19
4. In CMD type the following commands, replace YOURIPADDRESS with the address we got from step 3
Code:
adb connect YOURIPADDRESS
adb push custom-recovery.img /sdcard/
adb shell su -c dd if=/sdcard/custom-recovery.img of=/dev/block/recovery
adb reboot recovery
ROM
Instructions:
1. Download the 2_16GB_7.1.2.zip from HERE
and put it on a usb stick.
2. Reboot into recovery(not explaining this)
3. Go to mount and mount USB-OTG
4. Go back to the main menu and select install, then choose the 2_16GB_7.1.2.zip and swipe to install!
Reboot and enjoy!
NOTE: Remember to make a backup in recovery before flashing!
XDA:DevDB Information
T95Z Plus Stock 7.1.2 2/16GB Ported from 3/32GB, ROM for the Android Stick & Console Computers
Contributors
Ricky Divjakovski, whiteak
ROM OS Version: 7.x Nougat
Version Information
Status: Testing
Created 2018-02-05
Last Updated 2018-02-19
So witch wifi module is support?.
Will be work on sunvell t95k pro 2/16gb and LTM8830 wifi module?
rumunn95 said:
So witch wifi module is support?.
Will be work on sunvell t95k pro 2/16gb and LTM8830 wifi module?
Click to expand...
Click to collapse
Wifi module is not a factor anymore.
Aslong as your device is 2/16GB this could possibly work.
great to hear this i will be testing
I had no PC around (at least not in the same ip-range
So, i installed the Flashify app and used that instead...works great! So now i have TWRP 'loaded' i will give it a go in a few minutes....#fingerscrossed #yeah
Well...no USB-stick or microsdcard laying around at the moment and i also use 1 usb port for power and the other for remote control. So I ended up downloading the ROM directly to my T95Zplus.....no errore during flashing, wiped cache/dalvik and rebooting right now and so far so good...!
ZeroZorro said:
I had no PC around (at least not in the same ip-range
So, i installed the Flashify app and used that instead...works great! So now i have TWRP 'loaded' i will give it a go in a few minutes....#fingerscrossed #yeah
Well...no USB-stick or microsdcard laying around at the moment and i also use 1 usb port for power and the other for remote control. So I ended up downloading the ROM directly to my T95Zplus.....no errore during flashing, wiped cache/dalvik and rebooting right now and so far so good...!
Click to expand...
Click to collapse
Well...that did not work....rebooted and after 15 minutes still nothing except the boot-screen (and before that animation)...so gonna try to figure out what went wrong...
So be warned if you are gonna try it like i did and not following OP to the letter!
Sent from my Z1 PRO using Tapatalk
ZeroZorro said:
Well...that did not work....rebooted and after 15 minutes still nothing except the boot-screen (and before that animation)...so gonna try to figure out what went wrong...
So be warned if you are gonna try it like i did and not following OP to the letter!
Sent from my Z1 PRO using Tapatalk
Click to expand...
Click to collapse
Quite odd, if you flashed the rom in recovery, it should have worked :/
I did find a bug though, endless reboot if you try connecting wifi
So it's canned now
Ricky Divjakovski said:
...I did find a bug though, endless reboot if you try connecting wifi
So it's canned now
Click to expand...
Click to collapse
I didn't get a boot loop; however, attempt to activate wifi resulted in wifi switch button moving to on position and after ~3 seconds returning to the off position. Is it possible this needs to be debugged on a per-wireless-chipset basis? I'm on 8830 q201_6255....
Please advise and let me know if I can help out with logs, etc.
Thanks
LAX_2_TLV said:
I didn't get a boot loop; however, attempt to activate wifi resulted in wifi switch button moving to on position and after ~3 seconds returning to the off position. Is it possible this needs to be debugged on a per-wireless-chipset basis? I'm on 8830....
Please advise and let me know if I can help out with logs, etc.
Thanks
Click to expand...
Click to collapse
From which firmware did you flash?
I don't know if partitions are different sizes and maybe that did trigger the bootloop? I come from goo.gl/hWrmxY (Android 7.1.1 with root, 1013) and that did not work so far...
Sent from my Z1 PRO using Tapatalk
ZeroZorro said:
From which firmware did you flash?
I don't know if partitions are different sizes and maybe that did trigger the bootloop? I come from goo.gl/hWrmxY (Android 7.1.1 with root, 1013) and that did not work so far...
Sent from my Z1 PRO using Tapatalk
Click to expand...
Click to collapse
I flashed on top of stock 1013 rooted with magisk
LAX_2_TLV said:
I flashed on top of stock 1013 rooted with magisk
Click to expand...
Click to collapse
Well...gave it another shot. Flashed 1013 ROM with USB Card Maker. Flashed TWRP and after that this ROM. Same issue....
Sent from my Z1 PRO using Tapatalk
ZeroZorro said:
Well...gave it another shot. Flashed 1013 ROM with USB Card Maker. Flashed TWRP and after that this ROM. Same issue....
Sent from my Z1 PRO using Tapatalk
Click to expand...
Click to collapse
Im gonna update it tonight, ill need someone to PM me, im gonna need someone to test as i dont have my TV box with me and im away on buisness, i think i have found the wifi bug, but as you can tell with the ROM ram usage is ALOT less, framework is much smoother and alot of apps have been updated from the manufacturer
Ill also be basing it on the newest build 1075(Or if anyone has a newer build PM me)
This rom will be pretty stock with more features implemented and possibly some apps i might make ffor the device
Ricky Divjakovski said:
Im gonna update it tonight, ill need someone to PM me, im gonna need someone to test as i dont have my TV box with me and im away on buisness, i think i have found the wifi bug, but as you can tell with the ROM ram usage is ALOT less, framework is much smoother and alot of apps have been updated from the manufacturer
Ill also be basing it on the newest build 1075(Or if anyone has a newer build PM me)
This rom will be pretty stock with more features implemented and possibly some apps i might make ffor the device
Click to expand...
Click to collapse
Hi and thanks a lot for works.
i flashed my 3gb/32gb variant with a 2gb/16gb rom and it's done. but if i setup my wifi in a few seconds the startup animation appears on the screen and hang during animation.
When i start the set top box with lan cable inside, it's hang at the end of start animation and stay on T95z plus logo with the space behind but without any network it's start and the launcher appear...
can you put in the HDMI section in setting menu ? to have the CEC support?
papla83 said:
Hi and thanks a lot for works.
i flashed my 3gb/32gb variant with a 2gb/16gb rom and it's done. but if i setup my wifi in a few seconds the startup animation appears on the screen and hang during animation.
When i start the set top box with lan cable inside, it's hang at the end of start animation and stay on T95z plus logo with the space behind but without any network it's start and the launcher appear...
can you put in the HDMI section in setting menu ? to have the CEC support?
Click to expand...
Click to collapse
yes thats a bug, this is mean for 2/16GB variants, this is exactly like stock 7.1.2, if you have 3/32GB variant flash stock 7.1.2(build 1075)
Ricky Divjakovski said:
yes thats a bug, this is mean for 2/16GB variants, this is exactly like stock 7.1.2, if you have 3/32GB variant flash stock 7.1.2(build 1075)
Click to expand...
Click to collapse
if i flash it with the 3gb/32gb rom version the box doesn't boot. the 1075 is for 32gb and i allready tried with no success.
papla83 said:
Hi and thanks a lot for works.
i flashed my 3gb/32gb variant with a 2gb/16gb rom and it's done. but if i setup my wifi in a few seconds the startup animation appears on the screen and hang during animation.
When i start the set top box with lan cable inside, it's hang at the end of start animation and stay on T95z plus logo with the space behind but without any network it's start and the launcher appear...
can you put in the HDMI section in setting menu ? to have the CEC support?
Click to expand...
Click to collapse
The CEC support is found under Droid Settings in apps mate.
whiteak said:
The CEC support is found under Droid Settings in apps mate.
Click to expand...
Click to collapse
OK. Thanks. I'm waiting for an solution about the connection trouble.
Maybe you can consider to bake a little reboot app (i use Simple Reboot) into the ROM cause it makes it much easier to test and restore/backup especially when there is no internet with this ROM at the moment.
For now I have some apk's ready on a sdcard so I will get there but would make things a little easier...
ZeroZorro said:
Maybe you can consider to bake a little reboot app (i use Simple Reboot) into the ROM cause it makes it much easier to test and restore/backup especially when there is no internet with this ROM at the moment.
For now I have some apk's ready on a sdcard so I will get there but would make things a little easier...
Click to expand...
Click to collapse
will do!
adb connect not working
Hi,
Thank you very much for all your effort Ricky. I have T95Z Plus 2/16 variatnt. I am unable to connect to my TV box using adb. I have USB debugging enabled on my TV box. The TV box and my Mac from where I am trying to run adb commands are on the same wifi network. I have tried connecting my TV box to my Mac using USB cable but still adb connection fails with error "Host is down" and sometimes "Operation timed out".
I cannot proceed further without this step. Any help is much appreciated.
Apart from adb, can I copy the files into SD card or USB drive and install it? If so, what will be the steps?
Thanks again!
The Developer Preview has ended. The official release has been released and can be found here https://forum.xda-developers.com/moto-x4/development/rom-lineage-os-15-1-t3802265
The current (unofficial) Developer Preview is developed by @erfanoabdi This thread serves as a means to help folks from further discussing LOS16 within the Official Lineage 15.1 thread (to help prevent that thread from being both further hijacked and to prevent confusion from the two in conversation).
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Code:
/*
* 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.
*/
Please remember this is NOT a final release. There WILL be bugs. It is also very possible that you could end up bricking your phone by attempting to install, use, or upgrade LOS16 and you do so at your own risk.
How to install Lineage 16.0 Developer Preview
!! Please read in full before proceeding !!
Remember to submit logs when reporting any errors.
Remember to be as detailed and as clear as possible on what actions you took which resulted in any errors.
Download the latest Official TWRP https://dl.twrp.me/payton/. - You want the .img file.
Restart your phone to your bootloader. - You do this by pressing and holding both your phone's power button and the lower volume key at the same time.
Once at your phone's bootloader, from your Windows Command Prompt (as administrator) or from your Linux Terminal (as root) run the following command to load TWRP:
Code:
fastboot boot '/your_path_here/twrp-X.X.X-X-payton.img'
Note: Be sure to use your path on where you have the file on your computer. Be sure to replace and use the correct file name for your file (Do not just copy and paste example posted here).
!! You will be wiping everything because this is a developer preview and bug reports are most helpful on a clean, fresh install !!
Regardless of what ROM you are coming from (stock or not), format your DATA.
Reboot your device to bootloader and reuse the previous fastboot command to load TWRP listed above.
Regardless of what ROM you are coming from (stock or not), wipe your device (all partitions).
Reboot your device to bootloader and reuse the previous fastboot command to load TWRP listed above.
Download "Copy Partitions Zip" - courtesy of @filipepferraz https://drive.google.com/file/d/1oiry9UfP2tf-5A6nQBF7pn2t2eSGKt0F/view
Upload "Copy Partitions Zip" to your phone using the "ADB Push" command to /sdcard/ (run as admin if on windows or as root if on Linux).
Code:
adb push copy-partitions-payton.zip /sdcard/
Now INSTALL "Copy Partitions Zip"
Reboot to your bootloader. - Stay at the bootloader screen (do not load TWRP)
Download the firmware for your phone
XT1900-1 Android 8.0
firmware_27.251.12_payton_retail_xt1900-1.zip
Only tested on
XT1900-1
XT1900-2
XT1900-5 (https://forum.xda-developers.com/showpost.php?p=76934354&postcount=173)
XT1900-7 (https://forum.xda-developers.com/showpost.php?p=76779696&postcount=14)
feel free to test on other Moto X4 models running 8.0.
XT1900-6 Android 8.0 - courtesy @filipepferraz
https://www.androidfilehost.com/?fid=674106145207492371
XT1900-1 Android 8.1 - courtesy @ptn107
https://www.androidfilehost.com/?fid=890278863836292604
tested on XT1900-7 as well (https://forum.xda-developers.com/showpost.php?p=76816113&postcount=92)
Latest firmware for payton_fi android 9 from PPW29.69-26 - courtesy @ptn107
firmware-29.69-26_payton-fi_xt1900-1.zip
Unzip on your computer.
User flash_all.bat if on windows as administrator OR ./flash_all.sh if on Linux as root.
Reboot your phone to bootloader
Reboot your device to bootloader and reuse the previous fastboot command to load TWRP listed above.
Download and locate the latest developer preview: https://androidfilehost.com/?w=files&flid=281597
You will upload these files to your phone using the "ADB PUSH" command to your /sdcard/ directory (as admin in windows or root in Linux). For example:
Code:
adb push lineage-16.0-20180921-UNOFFICIAL-payton.zip /sdcard/
Install your ROM.
Congratulations! You're done!
NOTE: The point of using a developer preview is to test the ROM itself. You can attempt to install TWRP after installing your ROM, just as you can reboot back to recovery after, and install OpenGapps, followed by Magisk, but that is NOT the true point of testing this ROM. While it may be useful to know of issues with those commonly used tools, the primary concern is the ROM itself at this time.
Remember to submit logs when reporting any errors.
Remember to be as detailed and as clear as possible on what actions you took which resulted in any errors.
MotoX4 said:
Remember to submit logs when reporting any errors.
Remember to be as detailed and as clear as possible on what actions you took which resulted in any errors.
Click to expand...
Click to collapse
Excelent Rom very good accuracy of battery, but usb adb is not working
Hi @erfanoabdi, I am really enjoying this ROM.
Question: Is there any way to replicate the Retail X4's One Button Nav? It seems to have implemented a press/long-press/longer-press for the fingerprint scanner. Not sure if something like this is in the AOSP code or not. It is really awesome for locking screen AND keeping Google Assistant.
---------- Post added at 08:05 PM ---------- Previous post was at 07:18 PM ----------
I have played around a it with flashing Generic System Images (GSI) over this ROM, and it seems to be quit compatible most of the Android 9 ones that I have tried.
It is awesome that this phone suddenly has many options to toy with (yes, I said it, it is a toy) due to the hard work of the devs Trebelizing (or is it Treble-izing?) our Moto X4!
---------- Post added at 08:09 PM ---------- Previous post was at 08:05 PM ----------
vmmiguel said:
Excelent Rom very good accuracy of battery, but usb adb is not working
Click to expand...
Click to collapse
USB ADB seems to be working fine for me. I am on the 9/29 version.
jhedfors said:
Hi @erfanoabdi, I am really enjoying this ROM.
Question: Is there any way to replicate the Retail X4's One Button Nav? It seems to have implemented a press/long-press/longer-press for the fingerprint scanner. Not sure if something like this is in the AOSP code or not. It is really awesome for locking screen AND keeping Google Assistant.
---------- Post added at 08:05 PM ---------- Previous post was at 07:18 PM ----------
I have played around a it with flashing Generic System Images (GSI) over this ROM, and it seems to be quit compatible most of the Android 9 ones that I have tried.
It is awesome that this phone suddenly has many options to toy with (yes, I said it, it is a toy) due to the hard work of the devs Trebelizing (or is it Treble-izing?) our Moto X4!
---------- Post added at 08:09 PM ---------- Previous post was at 08:05 PM ----------
USB ADB seems to be working fine for me. I am on the 9/29 version.
Click to expand...
Click to collapse
For me doesn't work, nothing appears in notificacions bars or even in fastboot can´t recognize my device...
Actually i have running this rom, but i don´t have GAPPS installed, and the adb is not working so i cant flash via fastboot the twrp for install my gapps, any suggerency to do?:good::crying:
jhedfors said:
Hi @erfanoabdi, I am really enjoying this ROM.
Question: Is there any way to replicate the Retail X4's One Button Nav? It seems to have implemented a press/long-press/longer-press for the fingerprint scanner. Not sure if something like this is in the AOSP code or not. It is really awesome for locking screen AND keeping Google Assistant.
Click to expand...
Click to collapse
Thanks for using this rom but you can enable it from
Setting system buttons and disable on screen nav bar
I couldn't get long hold and longer hold to detect in custom roms but still it's usable for home recent and back buttons
You can set hold home button to action something else then assist (lockscreen)
erfanoabdi said:
Thanks for using this rom but you can enable it from
Setting system buttons and disable on screen nav bar
I couldn't get long hold and longer hold to detect in custom roms but still it's usable for home recent and back buttons
You can set hold home button to action something else then assist (lockscreen)
Click to expand...
Click to collapse
Thanks. I am using the fingerprint navigation as you describe. I am using an app that detects a double-tap, which I am using to lock the screen.
Sorry for OT:
Is there any way to take the long-press away from Google Assist (and be able to re-assign it) short of UN-installng Google? When I "disable" it in the Google App, or even change the default assist app, long press fingerprint only prompts to re-enable Google Assist. It seems those settings only apply to long-press Home, but not long-press fingerprint. Google Assist has hijacked my fingerprint button!
Thanks again.
jhedfors said:
Thanks. I am using the fingerprint navigation as you describe. I am using an app that detects a double-tap, which I am using to lock the screen.
Sorry for OT:
Is there any way to take the long-press away from Google Assist (and be able to re-assign it) short of UN-installng Google? When I "disable" it in the Google App, or even change the default assist app, long press fingerprint only prompts to re-enable Google Assist. It seems those settings only apply to long-press Home, but not long-press fingerprint. Google Assist has hijacked my fingerprint button!
Thanks again.
Click to expand...
Click to collapse
I disabled the "google" application and stopped bothering with activating it again, it was the only way I found, because if you deactivate the assistant only when you keep it pressed the sensor sends the message to activate it xD
vmmiguel said:
Excelent Rom very good accuracy of battery, but usb adb is not working
Click to expand...
Click to collapse
I hope somebody to help me, last night i tried to update mi Lineage OS 16 (from erfanoabdi).
My device is unlocked bootloader, and i used the rom from nightly build (2018-21-09), it works fine and everything, the issue becomes when i look what was avaible a new update, so downloaded and install the new rom.
I do full wipe, after that i install the new rom, at this point everything its working fine, but after that when i changed the partition slot from A to B.
When i started to install the gapps they closed because it says what i am running Android 8.0, but its a mistake so i think that reboot the phone without install the gapps. So the phone starts well, so i decide again to boot into recovery (TWRP) to install the missing gapps.
When the device reboot in fastboot and i chosee the recovery option, the surprise was that TWRP was reemplaced by the stock recovery, and when i tried to flash the TWRP.img my device wont appear in fastboot mode, stays finding device and Windows wont recognized my phone.
I think the rom still no have usb adb support, so i cant flash TWRP
My device its unlocked and i was running the rom (but another nightly) .. without issues for a week ago... until i flashed this one
Now i have Lineage OS without GAPPS, without USB mode... Like the update from OPW 27 or 28 idk remember.
Thanks for read this i hope somebody can help me.
My device its a XT1900-4 in Android 9.0 without google apps, only have the essencial apps like phone dialer , sms, the very very essencials app. Like an phone from 2008 jhaha
I attach some information photos from the Rom that im running:
(System Running) fine thanks
https://ibb.co/bXC7ye
(ADB is switched on, but no appears nothing)
https://ibb.co/exGpBz
(I tried with everyone of the opcions
https://ibb.co/ekv5jK
and this is my currently fastboot:
AP Fastboot Flash Mode (Secure)
BL: MBM-3.0-uefi-641a15b-180224
Baseband: M660_7042.27.01.74R PAYTON_LATAM_CUST
Product/Variant: payton xt1900-4 32GB P4
CPU: SDM630 1.0 (6)
Console [NULL]: null
Tools Mode Config: DISABLED
POWER OK
flashing_unlocked
Software status: Official
Transfer Mode: USB Connected
At this point my windows so says to my device is Error in a request for the USB device descriptor.
i tried last_usb_google driver.
Motorola Device manager 2.5.4
Minimal adb fastboot 1.4.2
and nothing works fine.
In my recovery appears this:
Android Recovery
motorola/payton/payton
8.0.0/OPW27.57.25-6-10/12
user/release-keys
Use volume to...etc and then i used the (Apply update from adb)
says:
Supported API: 3
Stopping adbd. . .
Now send the package you want to apply to the device with "adb sideload <filename>"
I tried to navigate in the device with the terminal app, so i put this command in terminal to make ADB run
command adbd, and this appears on terminal:
adbd E 10-04 23:01:31 3819 3819 adbd_auth.cpp183] Failed to get adbd socket: success
adbd E 10-04 23:01:31 3819 3819 adbd_auth.cpp183] Failed to get adbd socket: success
i try to run command logcat.txt, but terminal cant move to sdcard.
i try to adb over network and that connect but can´t do anything because stuck on <waiting device>, i look the blankflash but
didn´t works to me, and in the configurations usb settings looks greyed so cant switch between then.
when i run the command ls i saw this files:
init.usb.configfs.rc
init.usb.rc
init.recovery.qcom.usb.rc
maybe there is my problem? Thanks for read, thanks to @erfanoabdi he works very hard to make this possible, i hope somebody can
help me.
vmmiguel said:
I hope somebody to help me, last night i tried to update mi Lineage OS 16 (from erfanoabdi).
...
When the device reboot in fastboot and i chosee the recovery option, the surprise was that TWRP was reemplaced by the stock recovery, and when i tried to flash the TWRP.img my device wont appear in fastboot mode, stays finding device and Windows wont recognized my phone.
...
Click to expand...
Click to collapse
Not sure if I understood all of your post.
On the MotoX4 there is no separate partition for the recovery, it is build into the system boot image / ramdisk. If you flash a new LineageOS or a new kernel youre TWRP is gone. So before you boot, you have to reflash TWRP. If you forgot to do this, you have to bring your device to fastboot mode (Volume down + Power 'till it boots to fastboot mode). Then boot it by "fastboot boot twrp-3.2.3-1-payton.img" to TWRP. If it has booted to TWRP recovery only then you can "adb push twrp-install-xxxx-payton.zip /sdcard" and install it from recovery. After that you should be able to directly reboot to recovery and flash what you need.
I always have all required "xxx.zip" on my microSDcard, so that I can flash them from TWRP without sideload or adb push. Remember to reboot to recovery after every "xxx.zip" flashed because of the A/B design of the MotoX4.
---------- Post added at 09:46 PM ---------- Previous post was at 09:41 PM ----------
Anybody else?
WLAN for me does not connect on lineage-16.0-20180929-UNOFFICIAL-payton.zip, if you have a hidden network (SSID). It will be shown as "saved" but does not try to connect.
Worked on lineage-16.0-20180921-UNOFFICIAL-payton.zip.
vmmiguel said:
Excelent Rom very good accuracy of battery, but usb adb is not working
Click to expand...
Click to collapse
USB is working for me (09/29)
For testing I changed my wlan SSID to visible on my wlan router and a second later, wlan is connected. Setting it back to unvisible drops the connection. So I think its's a bug in 09/29 LOS preview.
Gesendet von meinem Moto X4 mit Tapatalk
Just got around to trying the FM Radio app, and it is not working for me - working for anyone else? I did not check if it worked on 15.1...
jhedfors said:
Just got around to trying the FM Radio app, and it is not working for me - working for anyone else? I did not check if it worked on 15.1...
Click to expand...
Click to collapse
I'm trying too, does not work
FM not working here also... build from 21.09. 2018. - Don't want to upgrade to 2909, waiting for October build, September builds look obsolete now
Demoniackers said:
Rom Pixel Experience unofficial TREBLE Android 9 ARM 64 A/AB (GSI) Working (TRY IT)
...
Running almost everything, in Moto x4
-Magisk, modules, Volte, bluetooth.
I have not tried, NFC, Hotspot
Bugs: Headphone Jack, Second camera, One Button (fingerprint gestures) It is not deactivated
Could you solve the errors?
Click to expand...
Click to collapse
Wrong thread/forum.
Edit: it is VERY bad form to spam all the different threads that you have posted to. If you annoy people, they are less likely to want to help you.
PLEASE HELP!
Unfortunately I do not know how to report error logs but I will describe my issue the best I can.
I am on a moto x4. XT1900-1, Android One edition. Bootloader Unlocked.
I followed the steps to a "T". Everything went smooth with rom install but I noticed a couple things. When running the flash_all.bat file, everything but flashing the modem completes successfully. It gives a failed message.
Code:
PS C:\platform-tools\firmware> .\fastboot flash modem_a modem.img
Sending 'modem_a' (112640 KB) OKAY [ 2.806s]
Writing 'modem_a' (bootloader) Preflash validation failed
FAILED (remote failure)
Finished. Total time: 2.830s
It does this for modem_a and modem_b.
When I boot to bootloader(fastboot), it shows Baseband: <not found>
I haven't finished setup to see if I get cellular service. My guess is NO. Can you please help? Why would it be failing to flash the modem. I am trying the 8.1 firmware for Project Fi.
Thank you.
reedc83 said:
PLEASE HELP!
Unfortunately I do not know how to report error logs but I will describe my issue the best I can.
I am on a moto x4. XT1900-1, Android One edition. Bootloader Unlocked.
I followed the steps to a "T". Everything went smooth with rom install but I noticed a couple things. When running the flash_all.bat file, everything but flashing the modem completes successfully. It gives a failed message.
Code:
PS C:\platform-tools\firmware> .\fastboot flash modem_a modem.img
Sending 'modem_a' (112640 KB) OKAY [ 2.806s]
Writing 'modem_a' (bootloader) Preflash validation failed
FAILED (remote failure)
Finished. Total time: 2.830s
It does this for modem_a and modem_b.
When I boot to bootloader(fastboot), it shows Baseband: <not found>
I haven't finished setup to see if I get cellular service. My guess is NO. Can you please help? Why would it be failing to flash the modem. I am trying the 8.1 firmware for Project Fi.
Thank you.
Click to expand...
Click to collapse
I once did a quick Google search on this issue as I too faced this problem. It is safe to ignore. Allow me to explain:
This is safe to ignore. All it means is that your device already has a new firmware at that particular base. I, personally, originally used, for my device, XT1900-1 Android 8.1 - courtesy @ptn107 https://www.androidfilehost.com/?fid=890278863836292604 and the first time I used it (coming from STOCK) everything flashed without any issues. A few updates later and if I attempt to use it again, it proceeds to flash everything and it skips (soft fails) on 1 point while proceeding to do everything else. This is because, on that particular point, I likely have a newer firmware.
You should be able to proceed as normal and safely ignore that small error.
MotoX4 said:
I once did a quick Google search on this issue as I too faced this problem. It is safe to ignore. Allow me to explain:
This is safe to ignore. All it means is that your device already has a new firmware at that particular base. I, personally, originally used, for my device, XT1900-1 Android 8.1 - courtesy @ptn107 https://www.androidfilehost.com/?fid=890278863836292604 and the first time I used it (coming from STOCK) everything flashed without any issues. A few updates later and if I attempt to use it again, it proceeds to flash everything and it skips (soft fails) on 1 point while proceeding to do everything else. This is because, on that particular point, I likely have a newer firmware.
You should be able to proceed as normal and safely ignore that small error.
Click to expand...
Click to collapse
Thank you for the information! I was able to proceed and most things seem to work fine.
I noticed a couple bugs to report so far.
- External SD not available.
- Project Fi will not get LTE on US Cellular or Sprint.
- Messages app will not allow dark mode. Option is there but it does nothing. (I noticed this in the latest official build of LOS 15.1 as well. 20181002 build of 15.1 worked fine.)(I did install OGAPPS so this may be my fault.)
- Settings > Display > Color? does nothing. On LOS 15.1, I could switch it to be more saturated. I put a question mark because I am back on stock at the moment and don't remember exactly what the color option was called.
Other than that I was loving the smoothness of the ROM. I want to go back but have a hard time living without my project fi working as I live in a remote location and drive back-roads and need for my service to work across carriers.
Question, do we need to install any of the stuff found on the GSI version like the FBE_Disable etc? I don't know what GSI stands for or how that differs from this. Sorry for the noob question.
Thank you so much for the OP and sharing this. Really hope to see an October build soon that address some of the bugs.
reedc83 said:
Thank you for the information! I was able to proceed and most things seem to work fine.
I noticed a couple bugs to report so far.
- External SD not available.
- Project Fi will not get LTE on US Cellular or Sprint.
- Messages app will not allow dark mode. Option is there but it does nothing. (I noticed this in the latest official build of LOS 15.1 as well. 20181002 build of 15.1 worked fine.)(I did install OGAPPS so this may be my fault.)
- Settings > Display > Color? does nothing. On LOS 15.1, I could switch it to be more saturated. I put a question mark because I am back on stock at the moment and don't remember exactly what the color option was called.
Other than that I was loving the smoothness of the ROM. I want to go back but have a hard time living without my project fi working as I live in a remote location and drive back-roads and need for my service to work across carriers.
Question, do we need to install any of the stuff found on the GSI version like the FBE_Disable etc? I don't know what GSI stands for or how that differs from this. Sorry for the noob question.
Thank you so much for the OP and sharing this. Really hope to see an October build soon that address some of the bugs.
Click to expand...
Click to collapse
Here the external SD works as portable storage with ou a problem.
The LTE is a known problem.
I don't know about the dark mode from message app.
In the stock rom you need to deactivate night mode to change the color, in Los 16 you change it at Live Display.
hello all,
yesterday i decide to root my old phone, to see if i could get spoofing working on pokemon go.
flashed it manged it to get superSU , installed magisk, passed the safetycheck, and got spoofing working. but since the phone was full of old apps, i decide to do a factory reset, but looks like this ruined everything, so i went did all steps again, at 1 point i forget to enable oem option.
so i get the msg, custom binary blocked by frp, once i turn my phone on. after hours of searching i found the right firmware, and i could fix this problem.
but now, no matter what i do, if i press volume down, home, power i keep getting in download modus, instant of recovery modus.
i need to get in twrp to install magisk from there.
because if i try, it from the magisk app manager, like i did it the first time, it say say failed to load boot.img
personally i think that i have flashed some wrong roms or something, but i am really stuck now on what do to, is there something easy to uninstall everything i have done? or anyone can point me in a direction of what do now?
Samsung j510fn(2016)
Build: nmf26xj510fnxxu2brb1
thanks, and sorry for my bad english
Hi , if your device is not boot properly try to flash this 4 file firmware:
http://www.mediafire.com/file/h884u0o8dy9va0l/J510FNXXU2BQJ8_7.1.1_4File.zip
Before you do that :
- Make sure that your battery is full charged !
- Put your device into Download mode.
- Load those files properly inside Odin flash tool.
- Connect your device with usb 2.0 port and once Odin detects your device click on Start .
If that doesn't help you to with latest firmware for your region :
https://updato.com/firmware-archive-select-model?q=j510fn&exact=1&r=&v=Nougat(Android+7.1.1)&rpp=15
Good luck
Teddy Lo said:
Hi , if your device is not boot properly try to flash this 4 file firmware:
Before you do that :
- Make sure that your battery is full charged !
- Put your device into Download mode.
- Load those files properly inside Odin flash tool.
- Connect your device with usb 2.0 port and once Odin detects your device click on Start .
If that doesn't help you to with latest firmware for your region :
Good luck
Click to expand...
Click to collapse
Thx my friend it worked
have other question maybe you can help me also? i need to deodex my system, but i read everywhere that i need more then 25% free space on my /system folder. currently i have 0,1mb free of the 3gb. while my internal storage have 8gb free space, is there a easy way to make /system bigger so i can deodex it?
greetz
I don't know , but maybe this can help you:
https://www.samsungdeodex.com/2017/08/rom-deodex-samsung-j510fn.html?m=1
or
https://4pda.ru/forum/index.php?showtopic=925236&st=140
You must to know that phone modification can brick your device permanently !!! So think twice before you do anything.
[original comment with links to ROMs is there: https://forum.xda-developers.com/t/root-possibility.4130739/post-83915657]
Hello
This is way to install AOSP rom with root (not Magisk, Superuser). All thanks to Wer99, he found this method
You need:
ROM:
http://www.mediafire.com/file/mdavroo9edpwveg/AP_AOSP_Android_10_A21s.tar/file > AOSP Android 10 ( only bug i found is not working auto-brightness [which is normal for GSI without overlay, but there is not working light sensor probably, i dont see values in CPU-Z or AIDA64 either])
http://www.mediafire.com/file/r6m7s99hs9d031e/AOSP_super.tar/file > AOSP Android 10
https://www.mediafire.com/file/wjhwnh3pags62fa/super.tar/file > HavocOS Android 10 (i use this rom on my daily phone, bug is the same as on AOSP)
Others:
Odin, you can found it on XDA
Samsung Mobile USB Drivers, or other drivers for Samsung Download Mode
Installation is easy.
Unlock your bootloader [it trips Knox and voids warranty!]
Power-off your phone, boot it in Download Mode with pushing volume down and up, and connect USB cable to PC simultaneously.
In Odin, push file with ROM to AP section, and click flash. Done!
After reboot, do factory reset of phone.
After installation, enable support of all cameras in phh-treble settings.
Didn't work for me, I tried with the AOSP_super.tar, which succeeded, but got a boot loop.
I tried with the AP_AOSP_.., but it fails, I got "Only official released binaries are allowed to be flashed (SUPER)". The same occurs with Havoc tar.
When I tried the AOSP_super.tar again, I got the same message, instead of a boot loop.
Steps:
Unlock bootloader (OEM unlock is also permanently triggered in developer settings)
Power off phone
Download mode (volume up + power on) and connect USB
Load tar file in AP slot (other slots are empty)
Factory reset and clear cache
Flashing back the stock rom still works. Stock rom: A217FXXU5BUB4
Any ideas?
KaroloBC said:
[original comment with links to ROMs is there: https://forum.xda-developers.com/t/root-possibility.4130739/post-83915657]
Hello
This is way to install AOSP rom with root (not Magisk, Superuser). All thanks to Wer99, he found this method
You need:
ROM:
http://www.mediafire.com/file/mdavroo9edpwveg/AP_AOSP_Android_10_A21s.tar/file > AOSP Android 10 ( only bug i found is not working auto-brightness [which is normal for GSI without overlay, but there is not working light sensor probably, i dont see values in CPU-Z or AIDA64 either])
http://www.mediafire.com/file/r6m7s99hs9d031e/AOSP_super.tar/file > AOSP Android 10
https://www.mediafire.com/file/wjhwnh3pags62fa/super.tar/file > HavocOS Android 10 (i use this rom on my daily phone, bug is the same as on AOSP)
Others:
Odin, you can found it on XDA
Samsung Mobile USB Drivers, or other drivers for Samsung Download Mode
Installation is easy.
Unlock your bootloader [it trips Knox and voids warranty!]
Power-off your phone, boot it in Download Mode with pushing volume down and up, and connect USB cable to PC simultaneously.
In Odin, push file with ROM to AP section, and click flash. Done!
After reboot, do factory reset of phone.
After installation, enable support of all cameras in phh-treble settings.
Click to expand...
Click to collapse
Is there a way to install Havoc OS prerooted?
To David112+ :
I've Been Looking Forward On How To Make A GSI For Samsung A217F,
But I'm Only Able To Create A Non Rooted GSI With "CherishOS"
I'm Looking For Every Help Possible On This Forum.
Although I Don't Even Have Any Android Knowledge,
But You Know I Tried To Make A Non Rooted GSI With "HavocOS".
The Result Was Bad...
Booting - Passed
Access First Start Pages - Passed
Access Settings - Passed
But...
There's A Problem With The GSI.
Problem :
Random Restart Within 10 Second
My Device Variant = International
LonelyCracker said:
To David112+ :
I've Been Looking Forward On How To Make A GSI For Samsung A217F,
But I'm Only Able To Create A Non Rooted GSI With "CherishOS"
I'm Looking For Every Help Possible On This Forum.
Although I Don't Even Have Any Android Knowledge,
But You Know I Tried To Make A Non Rooted GSI With "HavocOS".
The Result Was Bad...
Booting - Passed
Access First Start Pages - Passed
Access Settings - Passed
But...
There's A Problem With The GSI.
Problem :
Random Restart Within 10 Second
My Device Variant = International
Click to expand...
Click to collapse
Yeah I think I know why, There's a filesystem problem, the UUID and filesystem has to be the same as the system.img of OneUI
The UUID depends in the device binary that you have (in the firmware)
I'd help you but, all my steps just led to a dead end sadly
KaroloBC said:
[original comment with links to ROMs is there: https://forum.xda-developers.com/t/root-possibility.4130739/post-83915657]
Hello
This is way to install AOSP rom with root (not Magisk, Superuser). All thanks to Wer99, he found this method
You need:
ROM:
http://www.mediafire.com/file/mdavroo9edpwveg/AP_AOSP_Android_10_A21s.tar/file > AOSP Android 10 ( only bug i found is not working auto-brightness [which is normal for GSI without overlay, but there is not working light sensor probably, i dont see values in CPU-Z or AIDA64 either])
http://www.mediafire.com/file/r6m7s99hs9d031e/AOSP_super.tar/file > AOSP Android 10
https://www.mediafire.com/file/wjhwnh3pags62fa/super.tar/file > HavocOS Android 10 (i use this rom on my daily phone, bug is the same as on AOSP)
Others:
Odin, you can found it on XDA
Samsung Mobile USB Drivers, or other drivers for Samsung Download Mode
Installation is easy.
Unlock your bootloader [it trips Knox and voids warranty!]
Power-off your phone, boot it in Download Mode with pushing volume down and up, and connect USB cable to PC simultaneously.
In Odin, push file with ROM to AP section, and click flash. Done!
After reboot, do factory reset of phone.
After installation, enable support of all cameras in phh-treble settings.
Click to expand...
Click to collapse
Hi i flash havocos but not reboot in rom reboot in download mode help please
LonelyCracker said:
To David112+ :
I've Been Looking Forward On How To Make A GSI For Samsung A217F,
But I'm Only Able To Create A Non Rooted GSI With "CherishOS"
I'm Looking For Every Help Possible On This Forum.
Although I Don't Even Have Any Android Knowledge,
But You Know I Tried To Make A Non Rooted GSI With "HavocOS".
The Result Was Bad...
Booting - Passed
Access First Start Pages - Passed
Access Settings - Passed
But...
There's A Problem With The GSI.
Problem :
Random Restart Within 10 Second
My Device Variant = International
Click to expand...
Click to collapse
Can you make a unrooted gsi? If you could please use dot os 5.2 it would mean world for me. The community also i think.
Don't use this. The Method Doesn't work. You'll be stuck in Bootloop Even if it Shows it Succeeded.
EatABRick said:
Don't use this. The Method Doesn't work. You'll be stuck in Bootloop Even if it Shows it Succeeded.
Click to expand...
Click to collapse
It worked, but with older version of OneUI installed. I don't have this phone anymore but maybe i can help