DISCLAIMER:
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
* 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.
INTRODUCTION
This thread is mainly intended for devs (pro devs don't really belong here because they're pro and this thread is useless), for someone who need help to continue the work for Nova and fix the bugs on Pie (not many left). I'll help as long as you can speak English xD (no google translate because it can cause misunderstandings). However, don't expect me to spend the same time into this as i''ve did when i've had the phone. Yes, i no longer have the phone (it's still dead) and if you're not up to date with that, then you can read the announcement here and i've mentioned that i've got a new phone here. On top of this, i can't build anymore because i can't sign up on Google Cloud Platform anymore. I've wrote about this here at the hidden content (below as a side note).
Users can also help with doing researches, testing things and logs.
I don't know if i'll consider to continue working on it myself alone without the phone. I'd need at least to be able to build and then i'd need people to test new builds / flashable zips. At some point i might consider that because i'm missing this phone and the community xD.
SOURCES
Device: https://github.com/skinzor/android_device_huawei_hwcan/tree/lineage-16.0-last
Vendor: https://github.com/skinzor/proprietary_vendor_huawei/tree/lineage-16.0-last
Kernel: https://github.com/skinzor/android_kernel_huawei_msm8953-1/tree/lineage-16.0-last
Click to expand...
Click to collapse
There's two branches:
1) lineage-16.0: those ones were used when i've booted Pie the first time. Remember that i've wrote about it here? Those ones were updated from mido's ones.
2) lineage-16.0-last. those ones are the last ones and updated, which i've used in my last build. Those ones were continued from previous branch and updated from tissot ones which were / are updated by another dev (not the same dev as on mido). I recommend to continue with this branch, but it's up to you. You might not be able to get a successful or bootable build anymore with lineage-16.0 branch anyway because lineage's sources were updated since then.
I've used mido's trees as reference for lineage 14 and 15 trees too. You can figure that yourself if you check mido's trees and then Nova's ones, as i've cherry-picked the commits. Why did i use mido's trees? Because:
1) It has the same qcom chipset as Nova.
2) It is a popular phone.
3) A good dev was working on it.
4) It has official lineage support.
Now you might ask why i haven't did myself everything from scratch. Well, as a newbie dev, it would've been much harder and would've took much more time. Also, i'd say that there's no point at all to do something from scratch when it was already done unless you want to go the "hard" way, assuming you have time and want to learn more. I've still learnt a lot since i've started.
There are "universal" commits which are about fixes / improvements that can be related to e.g. the android version or the qcom chipset and those commits are usually found in many device trees, so you just cherry-pick them. A good example would be this commit: hwcan: Use mke2fs to create ext4 images.
FIXING THE BUGS OF LINEAGE 16 / PIE
I assume that you've used lineage-16.0-last branch as i've recommended. I no longer remember what bugs had my last build, but i think that the bluetooth was working, while it wasn't working in the build made from old lineage-16.0 branch. However, i remember that it had a new bug and as far as i remember, it was the RIL, but the baseband was showing up. I think i've tried to fix it and i've got it working (i remember that it was about the blobs), but i don't remember how. As of typing now, i've looked into the logcat which i still have and i've seen this:
Code:
F linker : CANNOT LINK EXECUTABLE "/vendor/bin/tftp_server": library "liboemaids_vendor.so" not found
That kind of error is self explanatory: the blob / lib is missing. After i've seen this, i've remembered that it's a new blob which got added in the original commit and which i've cherry-picked here. I didn't include that blob for a reason, but i don't remember that reason lol (it's not that i've forgot it, but i've skipped it for a reason). I remember that back then i've added the blob manually after i've seen the error, but i don't remember if that's what fixed the RIL, so you can try that and let me know.
As i've said already, i don't remember what bugs had that build besides the RIL, so you can try it and let me know.
At the introduction i've mentioned that i can help. I'll help only here on XDA in this thread because it may help other people too if they're having the same error / problem and after all, it's nice to have a thread like this in my opinion.
You can attach the log or paste it to gist github, pastebin, del.dog or any pasting website, but don't paste it in the XDA post because it just sucks.
Click to expand...
Click to collapse
DOWNLOADS
MEDIAFIRE | ANDROIDFILEHOST
As i've recommended to use lineage-16.0-last branch to build / continue the development, i also recommend to flash that build.
The build from lineage-16.0 branch folder doesn't boot. Back then, when i've seen that it doesn't boot and took a look at the logcat, i've tried the graphic blobs from the tree of zenfone 3 and that one was using them from nokia 7 plus (based on the commit). I had two zips in my PC and i've uploaded both. The first one created is graphic_pie_blobs_zenfone3_nokia_7_plus.zip and the second one sdm_blobs_zenfone3_nokia7_plus.zip, so you flash them in that order. As i've mentioned in that post in which i've said that i've booted Pie, there is some lag / glitches while scrolling, due the display / graphic blobs.
ENDING
As i've promised, i've pushed the tree sources and uploaded my first and last build. The reason i'm willing to help in fixing the bugs is because i'm missing this phone and this community here on XDA (as i've expected xD). It was fun and thanks to this phone and y`all for your support and kind words, i've learnt so many things in this journey. That's simply unforgettable for me.
Hopefully someone will jump on and continue the development further. I'll be here to help.
XDA:DevDB Information
[DEV][9.0] LineageOS 16, ROM for the Huawei Nova/Nova Plus
Contributors
#Henkate
Source Code: https://github.com/skinzor/android_kernel_huawei_msm8953-1/tree/lineage-16.0-last
ROM OS Version: 9.x Pie
ROM Firmware Required: Unlocked bootloader, TWRP
Version Information
Status: Testing
Created 2019-01-02
Last Updated 2019-01-05
Reserved
Reserved
Thank you for all the hard work you put into this. I would try to follow the leads, but for me this phone is dead now. I had hoped it would be something, but naw, just a hunk of something. Maybe someone can pick it up and go with it, encouraged everyone to try. If you are thinking about it Robert @#Henkate will help you. Great person, and this phone got me to know him so boom, good phone.
Maybe this should be in off topic thread, but I will post here.
Thank you for the great work that you have done. You gave us nougat, oreo, almost a pie. LineageOS 15.1 is the best firmware I have ever used. EmUi far behind. Thanks again a lot. Pie is full of bugs (I have already tried), counted a huge list of 10 items, but I think it's time to relax. You gave nova a second life and for that I am grateful to you. I found out that you are switching to another phone. Good luck in developing it, you are a good developer, the main thing is to believe in yourself!
Hi enkate... does wifi calling work on 16 ?
thanks
virusdunil said:
Hi enkate... does wifi calling work on 16 ?
thanks
Click to expand...
Click to collapse
He has no way to check. Maybe someone who has flashed it could test.
wow！thx a lot，I will try it now！
Hey Henkate !, Yesterday I installed LOS16, the last build that you compiled, botched and everything, but at the moment of continuing with the initial configuration, the screen does not give an image, the touch works, but it runs out of image: /
Alee.se said:
Hey Henkate !, Yesterday I installed LOS16, the last build that you compiled, botched and everything, but at the moment of continuing with the initial configuration, the screen does not give an image, the touch works, but it runs out of image: /
Click to expand...
Click to collapse
With the first build go two files, except for the firmware, responsible for the display. Flash them after flash lineage 16 last build and everything will work
Logcats
Hey there!
Finally tried it. I flashed just the latest build and there is what I got:
After flashing only ROM, it booted, but nothing was drawn at the display. Ok, that was expect
Then I wiped system and data again, flashed the build and both of the other zips (from the first build folder)
It booted fine, RIL was working at start, wifi ok. Many other things couldn't be tested, because randomly (one time taking photos, other when scrolling settings, other when trying to test bluetooth) screen went black the blue led got lit up.
I took a logcat only with errors and it seems there is a lot to fix. Still today (just a lot later today, I have to work) I'm gonna fetch los 16 trees, but I still have no idea how to solve any of the bugs. I'll do a lot of search though.
Here is the gist I made with the logcat I took. Any help would be appreciated.
EDIT
just forgot to mention that besides RIL working, I couldn't make a call (display went black and blue led). When rebooted it, I had no signal reception at all
Vinnom said:
Hey there!
Finally tried it. I flashed just the latest build and there is what I got:
After flashing only ROM, it booted, but nothing was drawn at the display. Ok, that was expect
Then I wiped system and data again, flashed the build and both of the other zips (from the first build folder)
It booted fine, RIL was working at start, wifi ok. Many other things couldn't be tested, because randomly (one time taking photos, other when scrolling settings, other when trying to test bluetooth) screen went black the blue led got lit up.
I took a logcat only with errors and it seems there is a lot to fix. Still today (just a lot later today, I have to work) I'm gonna fetch los 16 trees, but I still have no idea how to solve any of the bugs. I'll do a lot of search though.
Here is the gist I made with the logcat I took. Any help would be appreciated.
EDIT
just forgot to mention that besides RIL working, I couldn't make a call (display went black and blue led). When rebooted it, I had no signal reception at all
Click to expand...
Click to collapse
Also to the list of bugs: personally, my phone did not work with a SIM card, constant crash of applications. The YouTube crash, the camera does not take a photo (camera stock), after restarting, the fingerprint disappears (it is not deleted from memory, but it can only be unlocked if you make a new fingerprint) Any heavy application will crash after a while
Thx for u work, I have a reboots after few mins the system starts
nova canL11, cant reply link to adb bugreport logs x_x
penk3 said:
Thx for u work, I have a reboots after few mins the system starts
nova canL11, cant reply link to adb bugreport logs x_x
Click to expand...
Click to collapse
Disable out sim card
AssasinAkindinov said:
Disable out sim card
Click to expand...
Click to collapse
ye, phone in airmode workrd normally,
AssasinAkindinov said:
Also to the list of bugs: personally, my phone did not work with a SIM card, constant crash of applications. The YouTube crash, the camera does not take a photo (camera stock), after restarting, the fingerprint disappears (it is not deleted from memory, but it can only be unlocked if you make a new fingerprint) Any heavy application will crash after a while
Click to expand...
Click to collapse
penk3 said:
Thx for u work, I have a reboots after few mins the system starts
nova canL11, cant reply link to adb bugreport logs x_x
Click to expand...
Click to collapse
Sorry guys, no mean to be rude here, but this thread is for development purposes. My point in posting was to give a logcat and receive help to try and fix the bugs I found. I know that when possible, #Henkate gonna take a look and give some directions, so work can be done. So, if you wanna test and see if the rom works for you, that's fine, but provide logs, please. It's good to have other logs and be able to compare if the bugs are the same and I think it can help development a lot (no need to flood with logs either, be reasonable).
Unbrick no screen.
To repair the phone (when there is more image) it must start in fastboot mode and then flash boot image) wait for the phone to go off or remove the battery. When it is off plug the usb cable c on your huawei nova and the phone will show that the phone is charging. Now you can reflash another rom but not lineage os 16. Sorry i use google translation
Android 9 with jdi screen
Android 9 with jdi screen
Amazing near.
As it is known, custom firmware was not friends with the jdi screens.
And here came LOS16 on Android 9. Read reviews that it is now not usable even on smartphones with "normal" screens, what can we say about JDI
But from the realization that he had bought a new phone and having a lot of time, the thought crept in to try to put a fresh custom for total disappointment in his smartphone and quiet use of the new.
However, not everything is so simple. After the first launch, the screen began to flicker well, I thought everything had arrived, now it will get dark and the sensor will fail. Cured with just one reboot. more of this did not happen.
Sim cards did not pull out (I have 2 of them), some wrote that because of them there were some problems crashing and rebooting the system (I don’t have that)
After a night out, the interface began to respond with a delay of 0.5 seconds. (It was cured by a complete reboot) ..
Quickstep launcher is often closed with an error
The camera does not remove the drain, installed from the playlist of the market works without comments.
The navigation bar disappeared after a telephone conversation, when the interlocutor first completed the call (It was decided to reboot)
Vkontakte application crashes, but I use Kate Mobile, it flies with a bang.
YouTube crashes
The sound from the conversational dynamics is quiet, I think you can fix it in the mixer_paths but this is not exactly
Waiting for the moment until the screen fails.
All right, testing 9 android is over!
Discharged the battery to 0, the phone turned off, when turned on, the painfully familiar symptom with the diagnosis "JDI", no image, the screen backlight is on.
Hope no more. I return the phone to the stock and sell it, turn to Meizu pro 7. Thank you all!
R0mi4 said:
All right, testing 9 android is over!
Discharged the battery to 0, the phone turned off, when turned on, the painfully familiar symptom with the diagnosis "JDI", no image, the screen backlight is on.
Hope no more. I return the phone to the stock and sell it, turn to Meizu pro 7. Thank you all!
Click to expand...
Click to collapse
Ты все посты будешь переводить и сюда кидать?) (It is joke)
Related
{
"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"
}
Code:
#include <std_disclaimer.h>
/*
* 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.
*/
About this Q&A thread for LineageOS
Use this area to ask anything you want related to LineageOS,
but try not to spam everyone, always search for an answer before.
LineageOS 14.1 for Sony Xperia Blue
Xperia T (Mint) : http://forum.xda-developers.com/-/-/-t3529554
Xperia TX (Hayabusa) : http://forum.xda-developers.com/-/-/-t3529555
Xperia V (Tsubasa) : http://forum.xda-developers.com/-/-/-t3529556
General Questions & Answers
Is root access included into LineageOS ?
No longer included by default to improve user security.
An addon is shared to add SuperUser features : https://download.lineageos.org/extras.
It will survive to updates the same way GApps do.
Go into Settings, About Phone. Tap "Build number" 7 times.
Go back, open Developer options. Change "Root access" option.
Do not use SuperSU unless you are sure, creates booting issues.
Read more about it : Here.
Is the ROM suited for daily usage ? Google Apps compatible too ?
Yes but work in progress. OpenGApps recommended.
Can I flash LineageOS on official and development builds, or even on CM without wipes ?
Migrations from unofficial to official, and from CM builds, are allowed with an experimental migration.
Read more about it here : http://lineageos.org/Update-and-Build-Prep/
Always remember to do backups before doing such changes.
Is the device encryption supported ?
State unknown. If you're coming from an older ROM
please read the details here : a07afb9660a86f702066003b8e81ab63789d1660
When USB connected to a computer, I can't access the storage ?
The phone is in charge-only mode by default on Nougat,
due to a stronger security logic regarding unauthorised data access.
Swipe down the notifications and change the USB mode.
I can't access the ROM's recovery with Volume-
You can either flash the boot.img from the newer Releases with "fastboot flash boot boot.img" or FlashTool,
or follow the instructions of the TWRP Recovery installation to update from TWRP.
Due to an unknown issue in data, the partition still looks like a 2GB
Although very unlikely, it may be possible that your data had an error
that could not be fixed automatically by the time you did the UserData Unification.
Read the ROM instructions and check downloads links on the device's LineageOS Wiki page.
Export the resize_userdata.zip from the unify_userdata zip (from UserData Unification),
and flash it from your recovery. If it works, problem solved.
Against advice, I upgraded without GApps and now it crashes. Any way without factory reset ?
Yes there is, but nothing assures you'll manage to do it fully & preserve all your data...
Once booted, keep saying Ok to all "Unfortunately, ... has stopped",
pull-down the notifications panel, press the Settings icon,
go in Apps, menu, Show System, scroll to Setup Wizard (green Android logo),
Permissions, and activate Contacts + Telephone.
Later, some Play Store apps may need reinstalling.
If not working, then I advise a clean factory-reset reinstallation...
About the battery failure on the Xperia T
If you experience battery issues, please read this : https://forum.xda-developers.com/showpost.php?p=70640214&postcount=8
The AOSP Keyboard does not support swipe gestures ?
Unfortunately the sources for swipe gestures are not available
and Google still requires their prebuilt library to be there for AOSP Keyboard.
Download the following libjni_latinimegoogle.so API 23 from OpenGApps
and push it to /system/lib/libjni_latinimegoogle.so using root access,
or use my one-time install zips : https://mega.nz/#F!ThEAkCRa!byhSwuoTbf6lnC1JxgKrig.
@Adrian DC will the ROM already Support OTA?
@ all
btw. this nice [MOD][SOUND][CM,AOSP][6.0+]SonySoundEnhancement&ViperAudio works with this first Build (Screenshots)
Sina Pack said:
Hello everyone
Which on better?!?!
CM13.snapshat or this ROM
Click to expand...
Click to collapse
Depends what is important for you :silly:
Both working Flawless. :good:
If you want to run MODs like Xposed you have to run Android 6.x (CM13) because the most MODs have no integration for Android 7 until now
If you want the new feautres of Android 7.x you shoud run LinageOS
First of all, a HUGE thank you for your work! Your ROM builds for the Xperia T brought my phone back to life, better than before. Now, I have installed the latest version of LineageOS 14.1, but I am experiencing a small problem. The ROM flashes TWRP 2.8.5 if I recall correctly, but that version does not have an F2FS option for file system. Can you please upgrade the TWRP to the newest version or skip flashing of recovery partition? Also, the TWRP in the AOSP build seems to play better with the device recognizing that Unified UserSpace thing Sony did to the Xperia T. My other problem is, that when I flash the LineageOS ROM, even though I formatted the /system and /cache partitions to F2FS with TWRP 3.0.2.0 after flashing the ROM, the /system partition reverts back to Ext4. Can you convert the ROM to have full F2FS support, maybe even including /data partition?
Also, does anyone have a problem, where you can make and receive calls, use Data connection but can not import contacts from SIM card? The contacts app and various SIM managers find 0 contacts on SIM card.
Your ROM is so awesome, thanks for this. But I see that Root Access options in my Developer Options include only "Disabled" and "ADB only", "App and ADB" option is missing. Can I ask you that this missing option is missing because of your setup ? And can I use your BootBridge to flash SuperSU for this ROM ?
First off thanks Adrian DC for keeping the Xperia T relevant! When I first hear that CM was going offline I immediately started looking for another phone, but I was elated to find out you had decided to work on Lineage OS. I flashed the latest ROM 2 nights ago and I can say that this update is much more quicker and stable for me at least than the last CM 14.1 that I was running from the Christmas night upload. I did notice the Root issue and am not concerned about that right now. The one thing I am concerned with is that I seem to be running through some battery. Is anyone else seeing this issue, my battery life is terrible right now. Thanks again for the great work!!
About battery failures and instant power-offs
Here's a small report about the Xperia T battery failure that I also experienced :
As a few of you reported already, it is quite known that the Xperia T
has a battery that does not survive nicely to years of heavy usage.
Released and sold in 2012, the Xperia T has an inbuilt battery that is not meant to be replaced,
the model is a 3.7V 1780mAh 6.6Wh battery with integrated controller and 3 pins clip plug.
The issues seen when the battery is about to die are random battery drops during reboots
(20+% disappear randomly, reappear later sometimes), below 15% the device goes off fast,
and recharging the device with a wall charger goes high quite (too) fast.
When the battery is truly dead, the device powers off randomly under heavy usage,
for example while taking a picture and the autofocus starts moving or using an USB drive.
Random power-offs also occur while using the device a lot like charging + GPS and such.
The biggest issue is that under a very low level of battery depletion, the device won't power on anymore
even if plugged to offline charge it, only 3 red lights will flash and the device will never boot again.
A solution I found to work multiple times with that situation is to open the device's back (really easy on the T),
unplug the battery plug, connect the USB cable from a wall charger, wait 1-2 seconds,
then directly replug the battery in place to see the device boot in offline charger.
Then leave the phone charge to 100% without interaction.
Small unsure side-effect, after 2 weeks of these mentioned issues, I stopped reviving it,
and ordered a new battery, but the MicroSD was fried. Likely related to the failure but no proof.
About replacing the battery on the Xperia T :
I ordered a "brand" new battery for the Xperia T, the goal is to absolutely avoid fake copies
and try to find a battery identical and original from Sony, otherwise results are unknown.
I bought my battery for 9€ therefore it stays a decent revival of a device that runs properly.
Replacing the battery involves removing the main motherboard flex that goes over the battery,
slightly bend it away from the battery without harming the triple flex plugs on the base of the battery.
Then removing the battery with a bank card takes some work but goes fine with patience.
Harming the flex at the base has to be avoided at all costs, battery can be removed slowly
with an angle to avoid unplugging the flex or touching it in any way.
Boot the battery with my technique and let it charge to 100%.
Then rebuild the device, it should be back to normal usable status.
Posted this as small hints for those experiencing the Xperia T battery issues.
Hi, think my problem fits better in here than in the XT-LineageOS-thread:
Since upgrading to LineageOS14.1 (29.1.17) I can't access the external SD-Card; Lineage-FileManager tells me to try it with root-rights (yea...)
Pretty sure it must be one little "Switch" to trigger, but I have no idea... Thanks for any hints
----------
As for the Battery-Issue:
I had that one several times, but no need to replace it:
First time I encountered it, I installed PacmanROM (think based on Android 5; nothing to loose when the battery is dying, right?) - battery worked well again, for another year - then showed the same "drop to 20% and gone"-symptoms; to revive, I installed CM12 - solved the problem; again one year later (last summer), again the battery... Installed CM13 (thanks Adrian - solved the problem again.
(...thinking about it, maybe I installed CM14.1 too early? ) Everytime, the XT had its old "run-time" (of about 4 days) back it had when first activating it in 2012; before upgrading, the battery hardly lasted one day...
I always made a clean-install including TWRP-upgrades... Maybe a change to a higher version triggers a setting in/for the battery? (eg. "planned obsolency")
---------
Edit:
took a shortcut with the SD-Card; as I could access it via USB I copied all data from it, inserted it back to the XT and initialized it (as external). With the newly possible access, I copied the files back. Seems to be working...
Have a problem with Wi-Fi on Xperia T (mint)
Status bar and settings say "connected, no internet", PlayStore "Check your connection an try again", so I can't install an application.
But Browser is working fine, searching for updates in "About Phone" too, means I have internet.
Have official Lineage Nightly 31st january.
I have already installed it for three times and tried another Wi-Fi, but doesn't work.
ArmW said:
Have a problem with Wi-Fi on Xperia T (mint)
Status bar and settings say "connected, no internet", PlayStore "Check your connection an try again", so I can't install an application.
But Browser is working fine, searching for updates in "About Phone" too, means I have internet.
Have official Lineage Nightly 31st january.
I have already installed it for three times and tried another Wi-Fi, but doesn't work.
Click to expand...
Click to collapse
Seems like your phone can't connect to the preferred DNS server at the moment.
try changing that.
Camera touch focus not working
I recently installed latest build of Lineage OS for xperia Tx. Touch focus for default lineage camera is not working. I am not sure if it is my phone or the lineage os?
farooq666 said:
I recently installed latest build of Lineage OS for xperia Tx. Touch focus for default lineage camera is not working. I am not sure if it is my phone or the lineage os?
Click to expand...
Click to collapse
It was missing for me too, reverting back to the lineage-14.1-20161231-UNOFFICIAL-mint build fixed it, but it did not fix my issue with the SIM contacts Did you try the builds from the official Lineage OS website?
What about battery life in TX? I'm planning switch back to Xperia T or TX cuz by now I'm using a Moto E 2nd Gen LTE and it doesn't work with the 3G/4G band of my carrier and Moto E's cameras sucks
Btw I saw that in Amazon (See attachment)
As far I'm concerned change the battery of T is a pain in the ass, So is better try again with a TX, isn't it?
farooq666 said:
I recently installed latest build of Lineage OS for xperia Tx. Touch focus for default lineage camera is not working. I am not sure if it is my phone or the lineage os?
Click to expand...
Click to collapse
jkristof94 said:
It was missing for me too, reverting back to the lineage-14.1-20161231-UNOFFICIAL-mint build fixed it, but it did not fix my issue with the SIM contacts Did you try the builds from the official Lineage OS website?
Click to expand...
Click to collapse
It's works in '20170214' build
Hi,
I am experiencing recently SoDs again.
I am using a Xperia V (tsubasa) just as a music player.
So only pure LinOS 14.1 without GApps.
It happens always during the night and if it is not charged.
Last night the battery was below 20% when it happened. The other times before I did not pay attention to the battery.
Battery was chenged in 10/2017 and was a new one.
Also I must say the RAM usage is very high. The Android system alone consumes 325MB. But I am not sure if it is related to the SoD.
AdrianDC,
Is there a way to extract the cast feature from the ROM and install it on other devices? Cast in Lineage OS is awesome and works flawlessly, and Samsucks screen mirroring doesn't even work on my same brand TV from my tablet, but Cast works every time.
Gallery shows images twice
After upgrading to lineage-14.1-20170310 (Xperia V), every Gallery-App (Stock, Gallery from F-droid) or Apps with access to images are showing every image twice. Properties of the "gemini-images" will show different paths,
i.e.
/sdcard/Pictures
/storage/emulated/0/Pictures
or
/sdcard/Download
/storage/emulated/0/Download
Has anyone else encountered this issue, too?
unifying the user data trouble guide
I wrote this in the hope this will soon be obsolete. I never succeeded installing lineageOS the official way. I had reproducible errors unifying the user data. I also hard bricked a Xperia V. I wrote a workaround step by step guide which will hopefully work not just for me. I know it sounds a bit crazy but as I did it quiet often and always succeeded by miracle, I wanted to find a reliable way. Everybody interested in the trouble which happens sometimes see attached recovery logs. This guides logs are in the folder UnifySucess. To find the interesting part search for mmcblk0p14. Perhaps it's also useful for diagnostics.
this is made on XPERIA V, if you want to follow this guide for another model you have to replace the files with tsubasa in its name.
EDIT: this is obsolete now
files used:
twrp-3.0.3-20170224-boot-tsubasa.img
recovery-13.0-20161221-SNAPSHOT-ZNH5YAO3Y8-tsubasa.img
lineage-14.1-20170303-nightly-tsubasa-signed.zip
unify_userdata-20170128.zip
restore_sdcard-20170128.zip
cleaner-fota-tsubasa.zip
coming from stock
fastboot flash boot twrp-3.0.3-20170224-boot-tsubasa.img
fastboot reboot
in TWRP
wipe System, Cache, Data, Legacy SD
flash unify_userdata-20170128.zip twice
if there is a failure ignore & flash lineage-14.1-20170303-nightly-tsubasa-signed.zip , gapps (optional)
reboot system ( not sure if necessary )
look into settings if storage is OK, you are done if not reboot bootloader
fastboot flash boot twrp-3.0.3-20170224-boot-tsubasa.img
fastboot reboot
in TWRP
flash restore_sdcard-20170128.zip twice
reboot to bootloader
fastboot flash boot recovery-13.0-20161221-SNAPSHOT-ZNH5YAO3Y8-tsubasa.img
fastboot reboot
in CWM
full factory reset
flash unify_userdata-20170128.zip twice
reboot to bootloader
fastboot flash boot twrp-3.0.3-20170224-boot-tsubasa.img
fastboot reboot
in TWRP
Internal Storage should now be bigger than 2GB, if so
flash lineage-14.1-20170303-nightly-tsubasa-signed.zip , twrp-3.0.3-20170224-fota-tsubasa.zip, gapps (optional)
If you are stuck and already installed the twrp-fota-tsubasa.zip there is a tool from AdrianDC to remove TWRP called cleaner-fota-tsubasa.zip
this is written in the hope to be useful, I'm not responsible for any failures.
guide update
I tried once with TWRP 3.1.0-0 and it did the trick - not initial but instead of CWM.
I am happily hoping not to need the recovery-13.0-20161221 and the cleaner-fota anymore.
@xperanto: I took a short look into the gallery after a clean install and there were no doubles
Its not too early to think about 9. We need 9 for Cool1 as soon as possible. How we gone get it ? We just need to get it -porting , working with source codes mmmm i dont know on this one but yeah. I want to ask those with the know how into Android to help build us an atleast stable 9. Thank you mr SimbyOS for all your work, i know am mounting pressure on you, pressure is good @ times ? damn i feel like a poet.
Ok i know the Le2 Pixel Experience boots on our Cool1-i booted it yesterday
Bugs
sim card not detected
Sd not mounted
And Camera disappeared
Fingerprint doesnt work
What i did was all dirty to make it boot but i think it might be useful to spit it.. If somebody working on 9 already in the shadows well and good but if none, this might be the gum that drops from your mouth that you pick and eat..
So download Le2 bootleggers, ported the boot.img with base being Cool1s Lineage. - bootleggers boots and sim works just messed finger print and camera.. am not a developer ? to fix these things but i want to learn
So after,i booted to Cuocos TWRP 3.1.1 if am not mistaken and cleared data, cache, system and then flashed the bootleggers ..
Turn it on..success boot..
After, i went and downloaded the Le2 PixelExperience, ported its boot.img with JUI 7.1.1. Then DIRTY flashed on bootleggers, then a reboot to system..boom i was in 9-feeling all snappy but then those bugs up there....
Hope this will push people to port for us , where is that crying emoji?
dmilz said:
Its not too early to think about 9. We need 9 for Cool1 as soon as possible. How we gone get it ? We just need to get it -porting , working with source codes mmmm i dont know on this one but yeah. I want to ask those with the know how into Android to help build us an atleast stable 9. Thank you mr SimbyOS for all your work, i know am mounting pressure on you, pressure is good @ times ? damn i feel like a poet.
Ok i know the Le2 Pixel Experience boots on our Cool1-i booted it yesterday
Bugs
sim card not detected
Sd not mounted
And Camera disappeared
Fingerprint doesnt work
What i did was all dirty to make it boot but i think it might be useful to spit it.. If somebody working on 9 already in the shadows well and good but if none, this might be the gum that drops from your mouth that you pick and eat..
So download Le2 bootleggers, ported the boot.img with base being Cool1s Lineage. - bootleggers boots and sim works just messed finger print and camera.. am not a developer ? to fix these things but i want to learn
So after,i booted to Cuocos TWRP 3.1.1 if am not mistaken and cleared data, cache, system and then flashed the bootleggers ..
Turn it on..success boot..
After, i went and downloaded the Le2 PixelExperience, ported its boot.img with JUI 7.1.1. Then DIRTY flashed on bootleggers, then a reboot to system..boom i was in 9-feeling all snappy but then those bugs up there....
Hope this will push people to port for us , where is that crying emoji?
Click to expand...
Click to collapse
When I tried to boot pixel experience in cool 1 dual. It shows error 7. Please help me.
sk ray said:
When I tried to boot pixel experience in cool 1 dual. It shows error 7. Please help me.
Click to expand...
Click to collapse
Guess you mean when flashing...
In updater script remove the lines that mention device details on top (from assert remove everything and end where ifelse starts from)
Then try flash again..
Hope you made a backup
Got a new Moto X4 1900-7 two days ago (reteu channel). Unlocked and rooted with MAGISK 17. Yesterday installed LineageOS 15.1 (Android 8.1 was shown) as described here. AddonSU and MindTheGApps did not work as install from the LineageOS Recovery. So installed them via TWRP.
Today it showed there is a new update for LineageOS. It seemed a good idea to test the update channel. LineageOS downloaded, installed and I pressed the reboot button. Since then the device does not switch on anymore. Just nothing. No lights, no booting screen. Looks fairly hard bricked now.
It is a bit frightening since I made good experiences with LineageOS on Moto X Play for years. But this time it did not work as seamless. As a side note, the second sim slot was disabled. I did not find out, where and how to enable it. This would be issues to be sorted out, before I support the project again.
I appreciate all your efforts about these devices and free software! :good:
Is there a reason you are not posting (and reading) in the proper thread?
https://forum.xda-developers.com/moto-x4/development/rom-lineage-os-15-1-t3802265
You will find all your answers there.
The developer specifically advised not to use the OTA updater.
Same issue here. Got a brand new Moto X4 delivered today. Verified nothing was obviously broken (tried WLAN, Cell, Dual SIM from stock). All fine.
Then I installed last night's nightly "lineage-15.1-20181017-nightly-payton-signed.zip" from within TWRP. After installing the nightly, I went with reboot recovery.
Since then, the phone appears hard-bricked as described by halori above.
No lights, no activity. Had it on charger most of the afternoon and all evening (it is 22:13 in Germany now). No signs of life. No matter how long I pressed VOLUMEDOWN+POWER. Same thing if I only press POWER. Same thing if I try charging it for 10-20 minutes, then try switching it one. Neither of the methods works.
Update:
- Similar symptoms, but different way of getting there
- Installed nightly 2018-10-17 via TWRP, *NOT* via OTA
Please post in proper thread.
jhedfors said:
Please post in proper thread.
Click to expand...
Click to collapse
That's a 64-page monster thread. Loads of different topics are "cross-talked". On the last two pages alone there are people
asking whether particular variants can be unlocked,
asking about issues with SIM2,
asking about storage requirements,
responding to those questions and
responding to questions from the pages before.
That thread is pure chaos. Web forums got threads, subjects and all that stuff for a reason: to keep things tidy and on-topic.
No offense meant. It is just very hard to grasp how merging all sorts of topics into one massive thread helps anybody keeping an overview.
Anyways, I posted in the thread, as you asked.
This Lineage is obviously crime with this device - it is just too sensitive to anything than 100% unmodified stock.
Exactly the same here. Today's 10/23 OTA update bricked it. :-/ No lights or anything. Not even from charging. Trying to figure out what to do at this point.
If you've already bricked your device you'll need to restore to stock ( https://forum.xda-developers.com/moto-x4/how-to/guide-how-to-flash-official-factory-t3808348 ) and then reinstall LOS.
From there you can apply updates without bricking your device by following this procedure: https://forum.xda-developers.com/showpost.php?p=77861941&postcount=616
As for finding specific things in the threads, there is a search function within each thread that is your friend.
Hi All.
I trust you well. I was wondering if I could request your assistance with updating my TF701T to a new version of android. I have tried many methods and none has worked. I am actually more confused now as to where to start and what to download and install. :silly:
If possible maybe direct me where I could get a step by step guide with the links to the correct downloads/procedure.
I imported the pad from USA to South Africa and barely used it.
Kind Regards
Rob
(h-tee-tee-pee-s) androidbiits.com/root-asus-transformer-pad-tf701t-easily/
probably use the versions of magisk + twrp that are linked at the site, as they are tested with that hardware -- the latest versions may not work. i do not own that particular device and am not a programmer -- just trying to help you out. search the web for info if anything is confusing in the instructions -- i can't really walk you through it, but the person at that site may be able to help you out if you get stuck.
you'll need to connect the asus pad to a computer, so you'll need the usb data cable & adb installed on the computer.
you will likely also need open gapps to get the play store + apps working. select processor type, android version, then variant. you can find it here ==> (h-tee-tee-pee-s) opengapps.org <== but i'm not sure how long that will be functional, as hosting is apparently migrating to sourceforge.
please note that there are no w's in either address mentioned previously.
here's an explanation of gapps ==> (h-tee-tee-pee-s + w's) androidfreeapks.com/apk/download-gapps-for-android/
...and there are also download links for various variations at that last address too. cheers!
you will not be able to install *the latest* version of android (it's just plain not out there as a mod for a device this old) but you *can* get something a bit newer than the stock version on it.
best of luck!
one last thing (pertaining to the very first thing you have to do) is unlock the bootloader.
(h...s + w's) asus.com/us/Tablets/The_New_ASUS_Transformer_PadTF701T/HelpDesk_Download/
you will find the utility to do so at the above site. select Android, then under "Utilities"
click "See All Downloads" - therein, the 2nd thing from the bottom in that section is the unlock tool,
which says: Unlock Device App. V1.o (there's only one thing with that name. size is 448.82 kb)
and it will only work from the stock Android version, which i assume is still functional on your device.
Magisk is apparently a newer replacement for SuperSU, which doesn't flag the system as altered...
therefore you *may not* need to install Gapps if using Magisk - that seems logical to me, but i am not certain.
thanks for the assistance Dorkus.........this is killing me....but I will keep the faith and try again
I am trying myself and cannot get the unlock tool to work, performed wipe data reset without google account and still "network error occurred" . Android version 4.4.2
bobwho said:
I am trying myself and cannot get the unlock tool to work, performed wipe data reset without google account and still "network error occurred" . Android version 4.4.2
Click to expand...
Click to collapse
Same here. I tried to contact Asus but no hope... We're completely blocked unless they do something? No other way to unlock?
greetings all, it is i, dorkus, of the house of mallorcus. haha. my name is actually reni.
xda keeps locking me out for some reason. i've now created 2 accounts (3 including the one from which this comment is posted) one even with a dedicated e-mail address just for this, but if i try to log in with either one, i get some "invalid" whatever message. admins: what have i said that was grossly incorrect? those links may not be presented in absolutely the most coherent way, but they're the best reasonable explanations of the procedure involved that i could find with about an hour or 2 of research, which i did because of intending to get one of these devices myself (which has now occurred! yay). besides that, who else with greater experience has chimed in on this thread? yes, i've reset my password, on both accounts. after i do so, both times: same "invalid" message. it's wasted over an hour of my time, when i'm just trying to help these people. it's highly annoying & if it continues, well, they'll just have to go it on their own.
to the point:
as luck would have it,
i was able to acquire one of these devices, still in superb condition, for a great deal from ebay. i have been in contact with Asus support & the word is: it's an EOL product, so the unlock servers have been shut down & there is currently no recourse end users have for unlocking their devices. i feel it's doubtful that they'll fire up a server again, but maybe we can pester them enough to develop a fastboot unlock tool? it sure would have been nice if it worked like that in the first place, but oh well, like the song says:
you can't always get what you want.
i will surely let you all know if am able to make any progress on unlocking my TF701T.
footnote: i also have a TF700 model which is in fact unlocked, has TWRP installed, and is running Android 5.1.1 {zombie-pop} which works a bit better than the Cyanogen mod flavor that it came to me with: somewhat improved user experience, maybe a little snappier too, but speed improvement is fairly minimal. most importantly, almost all of my apps work on it - a few don't even have an installer for Android 4 at the Play Store. the 701 is noticeably more responsive than the 700 model, even running 4.2.2 - the main issue with it for me is not being able to run all of my apps, some of which are purchased. i'd probably sell the 700 if i could get everything on the 701. oh well. it's an excellent reader + portable video viewing device even at stock. it's definitely worth what i paid in the condition received, but it'd be even better if i could unlock the bootloader & get a newer version of Android on it! i could possibly even be so happy that i'd float a couple bux Tim Duru's way, the guy primarily responsible for porting Android 6+7 (the latter of which apparently does not have a working camera) to this device.
footnote #2: the first day i got the 701, i tried to do a firmware update (proper region, latest available. full battery charge. the battery in the one i picked up is in fantastic condition, the thing is practically brand new + functions nicely... but now Asus won't let me unlock it, even though it's well out of warranty! grrrrr) which crashed mid-way & then it proceeded to get into an update / crash boot loop. i was pretty sad for a while, but did not give up & found a way to restore the original firmware (which turned out to be a very minor upgrade) from the SD card, thanks to information in a post here in the xda forums. that post is the link which follows. my thing would still go into fastboot (albeit slightly corrupted) + recovery mode, which enabled an SD card firmware flash to happen {...and lo, my little slab of Jelly Bean was resurrected...} so i did not require the NvFlash tool at all... but it's still there at the provided links in that thread.
to summarize the procedure:
1) format an SD card to fat32
2) download the appropriate firmware from Asus [**please note the region: if you flash the firmware from a wrong region onto your device, you will -hard- brick it + will then be required to use the NvFlash tool**]
3) un-zip the firmware (not completely, just remove nesting - so you have only one zip file)
4) rename the one remaining zip file: t4_sdupdate.zip
5) put that file on the root directory of SD card, then into the tablet (while turned off)
6) invoke recovery mode (power + vol down) & choose the recover [RCK] box (hit volume up, while it's the selected of the 3 choices) and from there the firmware update happens automatically. you can apparently upgrade to any official firmware by this method, but **cannot** downgrade... so i'd suggest leaving it at 4.2.2 until we are 100% sure that there are zero bootloader unlock options, because apparently the unlock tool, from what i understand, only works from the original 4.2.2
without further ado:
https://forum.xda-developers.com/transformer-tf701/tf701t-nvflash-unbrick-solutiontested-t3742848
it's now a few hours later from my original post, near bedtime for me, and the xda gods let me log into this account to make this edit... and it's even allowing URLs now! will wonders never cease? not sure what the problem was earlier, but it was quite annoying. anyway, if it lets me log into the account with the dedicated xda e-mail address, that's the one i'll use in future. username is renigade.
fly a kite said:
...
Click to expand...
Click to collapse
Hello @fly a kite @dorkus mallorcus @renigade
Please consult the inbox of your private messages. Thanks for your cooperation!
Stay safe and stay healthy!
Regards
Oswald Boelcke
Disclaimer
Code:
/*
* 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 the products you find here before flashing it!
* YOU are choosing to make these modifications.
*/
- EVEN MORE IMPORTANT: This ROM only works on devices using the bootloader hack.
- IMPORTANT: Do not update Magisk via the Magisk Manager App, your device will enter a bootloop if you do. Instead update Magisk via TWRP only. If you do this by accident then it is recoverable by just flashing the latest version of the ROM again (with gapps etc as required). This will be fixed in a later update.
Rules
- Please search the thread before asking questions
- Please try to stay on topic, I know it's not always possible
- Please report bugs here
- Report only one issue per bug report
- When reporting bugs please post a logcat and/or dmesg where possible
- Saying something isn't working without proper explanation will not attract any attention.
Downloads
- Lineage-16.0 for Amazon Fire 7 (mustang)
Source Code
https://github.com/lineage16-mustang/kernel_amazon_mustanghttps://github.com/lineage16-mustang/device_amazon_mustang
Thanks
- @k4y0z and @xyz` for the bootloader hack
- LineageOS
⏱ Change log / Release Notes
29 January 2022
- [Build] Dated 25 January 2022
- [fixed] Cameras not working at all
12 March 2021
- [fixed] Can't sign into google
- [fixed] Built in browser does not work
15 February 2021
- Initial Release
🛠 Worklist / Tasks
- [fixed] Bluetooth works
- [fixed] WiFi working
- [fixed] Audio works
- [done] Sensors working
- [fixed] Touch sounds are working
- [done] Test audio format playback - mp3 working
- [done] Tested video playback with NewPipe which is working
- [fixed] No adb during boot
- [done] Wired headphones working
- [fixed] Built in browser does not work
- [fixed] Can't sign into google
- [todo] Magisk update by app
- [todo] Support aptX-HD encoder for bluetooth
- [todo] Cameras not working at all
- [todo] Youtube, NewPipe, video playback
New Build is Up
15 February 2021
- Initial Release
- Stable with no crashes
- Change log on Post #2
- Task list on Post #3
- Cameras do not work for the moment
- Uses pie blobs from fireos 7
- Factory reset from TWRP is required
Will be checking this out! Let you know if I see any bugs
So far everything seems to be working perfectly. The only issues i can find are for some reason the default browser will not work and connection to google servers when signing in fails, which may very well be my crappy wifi but who knows. Well done @ggow good to see you back
Not sure if it is your problem with signing in to Google but when I do older equipment sign ins I need to go to Google with another device and there is a place where Google gives you a code or something to sign in with - I forget now but have had to do it when setting up various things like old phones, or registering thing to connect to google and send email, etc.
YodaDude2011 said:
So far everything seems to be working perfectly. The only issues i can find are for some reason the default browser will not work and connection to google servers when signing in fails, which may very well be my crappy wifi but who knows. Well done @ggow good to see you back
Click to expand...
Click to collapse
Thanks for the feedback. The default browser is borked on this build for some reason, noted on tasklist. Are you saying you couldn't sign in to google play services at all?
I don't use gapps so wouldn't have picked this up.
I was just about to load this and then I realized - Mustang is newer version of the Fire ? Does this mean I cannot load this on Austin Fire 7 ?
Thanks
platypoid said:
Not sure if it is your problem with signing in to Google but when I do older equipment sign ins I need to go to Google and there is a place where it gives you a code or something to sign in with - I forget now but have had to do it when setting up various things like old phones, or registering thing to connect to google and send email, etc.
Click to expand...
Click to collapse
Alright, I might have to push the apk for Chrome or something
platypoid said:
I was just about to load this and then I realized - Mustang is newer version of the Fire ? Does this mean I cannot load this on Austin Fire 7 ?
Thanks
Click to expand...
Click to collapse
No, this rom is for the 2019 fire 7
ggow said:
Thanks for the feedback. The default browser is borked on this build for some reason, noted on tasklist. Are you saying you couldn't sign in to google play services at all?
I don't use gapps so wouldn't have picked this up.
Click to expand...
Click to collapse
Yes, I cannot sign in at all. I even tried installing chromium and trying to sign in and it still failed. It'll pull up like the android setup thing and say checking for updates. After sitting like that for a couple minutes It'll say connection to Google server failed
YodaDude2011 said:
Yes, I cannot sign in at all. I even tried installing chromium and trying to sign in and it still failed. It'll pull up like the android setup thing and say checking for updates. After sitting like that for a couple minutes It'll say connection to Google server failed
Click to expand...
Click to collapse
Try going to your google account then security and look for App Passwords
It will let you set up devices that can't support two factor authorization and generate a passcode.
platypoid said:
Try going to your google account then security and look for App Passwords
It will let you set up devices that can't support two factor authorization and generate a passcode.
Click to expand...
Click to collapse
I can't even get into my account. I haven't been able to even log in, it fails before the long in screen
YodaDude2011 said:
Yes, I cannot sign in at all. I even tried installing chromium and trying to sign in and it still failed. It'll pull up like the android setup thing and say checking for updates. After sitting like that for a couple minutes It'll say connection to Google server failed
Click to expand...
Click to collapse
I just installed 14.1 on my Austen Fire. I was getting the same thing of endless checking for updates.
I restarted device, then checked setup as new, then it went through and asked for my google email and then the password. It then sent a message to gmail on my other fire and asked if it was okay for new device. Soon as I checked okay on the other Fire it made my Austen log in work .
YodaDude2011 said:
I can't even get into my account. I haven't been able to even log in, it fails before the long in screen
Click to expand...
Click to collapse
I'll check that here, maybe the same issue as why the stock browser is not working.
YodaDude2011 said:
I can't even get into my account. I haven't been able to even log in, it fails before the long in screen
Click to expand...
Click to collapse
platypoid said:
I just installed 14.1 on my Austen Fire. I was getting the same thing of endless checking for updates.
I restarted device, then checked setup as new, then it went through and asked for my google email and then the password. It then sent a message to gmail on my other fire and asked if it was okay for new device. Soon as I checked okay on the other Fire it made my Austen log in work .
Click to expand...
Click to collapse
I just checked, and can't complete the setup wizard successfully. Stuck at the Error couldn't sign in screen without option to do anything but going back for retry. I'll look into this and add it to the list.
I upgraded my old Mustang tablet today from the old Lineage 14.1 without a data wipe and everything seems to work. I'll wipe data if I have any weird problems.
I have noticed that my wifi unexpectedly turned itself off in two instances and seemed like it was having trouble associating with the AP in another. If I get a logcat of what is going on I'll post it.
@ggow sorry to be offtopic but you seem to be of experience with Mustang.
I have a new fire 7 version 6.3.1.5 shipped and I assume won't work with the known hardware exploit?
Looking at a unrelated bootloader unlock thread from years ago that makes me want to attack from a hardware perspective on the PCB.
Do you know if anyone has tried accessing SPI/JTAG/UART for the Mustang specifically?
Also a alternative could be to cross reference a CVE list with the Linux kernel version or the CPU or the bootloader or the libc or something to gain temp root to flash TWRP?
There's got to be something that could be utilized. Stagefreight for example has been patched for years on mainline android and linux kernels but since fireos is a fork it might not always have applied every patch so there's probably a gaping hole somewhere left untouched.
Maybe one of the spectre exploits as some of the variants affected ARM CPUs
(meant version 6.3.1.5 not 6.1.3.5)
-ANDROlD- said:
@ggow sorry to be offtopic but you seem to be of experience with Mustang.
I have a new fire 7 version 6.1.3.5 shipped and I assume won't work with the known hardware exploit?
Looking at a unrelated bootloader unlock thread from years ago that makes me want to attack from a hardware perspective on the PCB.
Do you know if anyone has tried accessing SPI/JTAG/UART for the Mustang specifically?
Also a alternative could be to cross reference a CVE list with the Linux kernel version or the CPU or the bootloader or the libc or something to gain temp root to flash TWRP?
There's got to be something that could be utilized. Stagefreight for example has been patched for years on mainline android and linux kernels but since fireos is a fork it might not always have applied every patch so there's probably a gaping hole somewhere left untouched.
Maybe one of the spectre exploits as some of the variants affected ARM CPUs
Click to expand...
Click to collapse
Read here on how to here to unlock your device:
Fire 7 (2019, mustang) unbrick, downgrade, unlock & root
Make sure to read this guide completely before starting. You will lose all data on the tablet, make a backup of important data before you start. What you need: - a Linux installation. Don't use a VM! Use a live USB, if you don't have Linux...
forum.xda-developers.com
ggow said:
Read here on how to here to unlock your device:
Fire 7 (2019, mustang) unbrick, downgrade, unlock & root
Make sure to read this guide completely before starting. You will lose all data on the tablet, make a backup of important data before you start. What you need: - a Linux installation. Don't use a VM! Use a live USB, if you don't have Linux...
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks for response.
The software route is patched. I'll keep trying with the hardware method but I think that's patched too so I'm trying to find another path if possible