Related
READ IN ENTIRETY BEFOR INSTALLING
I have procured a new Nexus Q. Work has resumed on Android 7.0, from a hardware and specs standpoint, there is no reason to think that this device is not capable of running Nougat if the Galaxy Nexus can. Stay tuned for a build in the coming weeks, I will also be uploading this project to github shortly
AOSP 7.0 Nougat for Nexus Q
Code:
Quote:
DISCLAMER
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in this ROM before flashing it! YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
Working:
TBD
Not Working:
TBD
Recovery
https://drive.google.com/file/d/0B7WYr1U8sRRAM1d3czhER0RoTGM/view?usp=sharing
./fastboot flash recovery
MAKE A BACKUP BEFORE INSTALLING AND SEND ME A LOGCAT WHEN YOU ENCOUNTER ISSUES SO I CAN TRY TO RESOLVE THEM
DL Link (Google Drive):
***LINK REMOVED*** -
Anyone interested in an early build send me a PM
Nice! Thanks very much for this! I'll try it when I'm back home in a few days. I was planning to try and work on this myself but perhaps I can transfer some efforts over to Android TV. Do you have the source for this on GitHub as that could also be really helpful - that way a few of us can contribute to help fix things etc.
New build coming soon with proper sources and fixes posted to GitHub. Also, if anyone would be interested, I believe that it may be possible to use an OTG webcam for Skype/etc.
Great stuff, thanks for doing this. Should be able to get android TV then since it's just a separate launcher.
Hmm, not having any luck flashing this. I get an "Installation aborted" error. What recovery are you using?
New build. Testing needed.
jyeley5 said:
New build. Testing needed.
Click to expand...
Click to collapse
What are the changes?
jyeley5 said:
New build. Testing needed.
Click to expand...
Click to collapse
This one seems to flash now (although it completes suspiciously quickly) but attempting to boot results in just a black screen over HDMI. I can't take a logcat because of the device permissions but is does show up with ADB so it presumably it is at least booting the kernel and a some core system but seemingly nothing past that - not even a boot animation.
wollac11 said:
This one seems to flash now (although it completes suspiciously quickly) but attempting to boot results in just a black screen over HDMI. I can't take a logcat because of the device permissions but is does show up with ADB so it presumably it is at least booting the kernel and a some core system but seemingly nothing past that - not even a boot animation.
Click to expand...
Click to collapse
Updated the CM base and merged some changes that I've been porting over. Did you install over another build or wipe fresh?
jyeley5 said:
Updated the CM base and merged some changes that I've been porting over. Did you install over another build or wipe fresh?
Click to expand...
Click to collapse
It was a fresh install, cleaned system, data and cache.
wollac11 said:
This one seems to flash now (although it completes suspiciously quickly) but attempting to boot results in just a black screen over HDMI. I can't take a logcat because of the device permissions but is does show up with ADB so it presumably it is at least booting the kernel and a some core system but seemingly nothing past that - not even a boot animation.
Click to expand...
Click to collapse
Try installing over a working CM11 build. Can you get me a logcat if that still doesn't resolve the issue?
jyeley5 said:
Try installing over a working CM11 build. Can you get me a logcat if that still doesn't resolve the issue?
Click to expand...
Click to collapse
I just tried flashing over Cm11 and nothing so far. Seems also to not boot. The speed at which it flashes in recovery says to me something isn't right with the updater script. There is no way it is copying the 255MB contents onto the Nexus Q in that time. Cm11 (which is smaller) takes far longer.
I tried to get a logcat but as before I am not able to get one of the boot attempt as the device appears as offline (because I can't authorise the PC RSA keys with adb as that would need Android to finish booting at least once). I can get you a recovery log or a logcat while flashing the Zip from recovery if you like but that's about it.
Have you actually had this booting on a Nexus Q then at all yet? And if so, how exactly did you install it, with which recovery and if over another ROM which one was it?
Possibly stupid question...
I'm new to this forum, at least posting here. So, since the Nexus Q app is no longer supported, how does one enable USB debugging on the Q? Any redirects and help would be greatly appreciated! I just got a brand new Q today for $10 at a local Goodwill (accompanied by fellow Q's). I was very sad to see these are no longer factory-functional.
If this is the wrong place to post, I apologize in advance, and would gladly accept on where-to-post details.
Thanks!
Natodroid1 said:
I'm new to this forum, at least posting here. So, since the Nexus Q app is no longer supported, how does one enable USB debugging on the Q? Any redirects and help would be greatly appreciated! I just got a brand new Q today for $10 at a local Goodwill (accompanied by fellow Q's). I was very sad to see these are no longer factory-functional.
If this is the wrong place to post, I apologize in advance, and would gladly accept on where-to-post details.
Thanks!
Click to expand...
Click to collapse
You've replied to a post about a specific custom ROM in the development section (which is completely the wrong place) and failed follow the XDA rule of searching before asking a question, because if you had you'd find the answer has already posted multiple times. Not trying to be harsh or rude - just letting you know!
If you have general questions or need help you should really go to the the "Nexus Q Help, Q&A and troubleshooting" section.
However, the situation is that you can't enable debugging on the stock ROM, but you can boot the Nexus Q into fastboot mode by holding your hand over the Q while you turn it on - this will make the led turn and stay red if successful (nothing will be shown onscreen). From there you can unlock your Q and boot a custom recovery image by issuing the correct fastboot commands from your PC. The custom recovery allows you to flash a custom ROM. The stock ROM is no use without the app which cannot be registered anymore since the servers are down.
Huge update, let me know how it's working
jyeley5 said:
Huge update, let me know how it's working
Click to expand...
Click to collapse
How to install this? Please give us some instruction.
Recovery added to original post, flash in fastboot. An amplifier build will be posted as soon as I finish it.
I keep getting "Installation aborted" when trying to flash. Not sure what I'm doing wrong. Used the recovery you just posted.
jyeley5 said:
Huge update, let me know how it's working
Click to expand...
Click to collapse
Tried to flash this latest version but it seems that there is an error in the updater-script. I get a status 6 error in recovery: "Installation Aborted".
Edit: So I edited the updater-script to remedy the status 6 error and then it progressed through most of the way before giving a status 7. I managed to fix the status 7 with a further edit to the updater-script but it still won't boot anything at all. I cannot take a logcat because it isn't booting anything at all and so there is no adb server.
I presume that you have this running on your Q but if you do then you clearly did not use the ZIP that was provided as that doesn't work. Do you have the system images which you just flashed from the bootloader with fastboot? If so perhaps you could share those so I could have a go flashing those instead and see if it will boot then.
wollac, you are correct in stating that I posted the wrong build (uploaded the wrong zip from my dev folder. However, the build I MEANT to post is booting on my Q, though BT and the Amp are not working yet. I'm a tad scatterbrained with finals, but I am compiling a new build that should hopefully resolve the bluetooth issues at least, and I will upload as soon as it's done.
WARNINGS:
1.) THIS IS FROM blinoff82's Guide:
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.
*/
Click to expand...
Click to collapse
2.) I'm explaining how I got EVOLUTION X to work. However, this applies to other ROMS I have mentioned below. Just without the GAPPS step. I might include guides on those in the future and videos.
Hello,
This is a quick prequel to what I am actually posting about.
PREQUEL:
I tried to install these ROMS: Lineage 16, Lineage 17, SyberiaOS, and ElementalX.
None of them would work with any of the INSTALLATION instructions provided.
I researched a lot of different guides, I read about Slots, etc. I have been a Computer Science Undergraduate for almost a year now(I know this has nothing to do with this. All it shows is that I know how to follow simple rules of Logic).
I decided I was going to figure it out myself. This is what worked for my device. IF anyone can tell me why this is the only way it works for me, please inform me(Just for the first time installation. Not for updates). Thank you.
Guide:
1.) Wipe everything(check all the options in the WIPE category in TWRP) and format data after that.
2.) switch to the other slot(slot you currently aren't in) without rebooting through the settings menu
3.) Repeat step 1
4.) USE the MSM tool to get to 9.0.8
4a.) How I get this to work is, connect the phone to USB, open MSM tool with admin, Click Start, try to power off the phone. Eventually, the MSM tool will start, leave the phone alone.
5.) After the reboot, go through settings skipping everything and agreeing to everything. SET UP A PIN OR A PATTERN .
6.) Go to settings, spam the build number in About Device until Developer Mode is given.
7.) uncheck update system, check advanced reboot and debug, and switch the USB connection mode from CHARGE to FILE TRANSFER.
7a.) PUT OOS 9.09 INTO INTERNAL
8.) Go to Fastboot through the phone's power menu. Unlock Bootloader.
8a.) Boot into the OFFICIAL TWRP MENU by following the steps in the Bootloader guide.
9.) Factory Reset. Wipe system
10.) Install Full ROM (9.09), Wipe Dalvik, Install Twrp and Wipe Dalvik
11.) Reboot Recovery, Repeat Step 10
12.) Factory Reset, and FORMAT(NOT WIPE) Data
13.) Reboot into Recovery
14.) Put 9.09, TWRP, EVO X ROM, and MAGISK 20.1 (OR Most Up-To-Date Version 20.1+) on Internal
15.) Factory Reset
16.) Repeat Step 10, Reboot Recovery, Repeat Step 10
17.) Flash Evo and TWRP
18.) Factory Reset, Wipe Data and Cache
19.) Reboot System
20.) Set the phone up and Set up a pin
21.) Reboot into Recovery after making sure you have Dev Mode and Debugging enabled
22.) Flash Magisk
23.) Reboot
24.) BE HAPPY!
I hope you guys take the time to appreciate my Guide and Let me know of any way I can make this guide better.
Thank you.
For real bro? I guide for something average user here knows to do? Lol, thanks i guess
J0nhy said:
For real bro? I guide for something average user here knows to do? Lol, thanks i guess
Click to expand...
Click to collapse
Thanks for that worthy contribution to this thread.
I appreciate OP's guide. I've had nothing but problems installing a custom ROM on my 6. I've been installing custom ROMs since my Galaxy S2, so I'm familiar with the process. Nothing has worked so far though. I'll give this a shot.
J0nhy said:
For real bro? I guide for something average user here knows to do? Lol, thanks i guess
Click to expand...
Click to collapse
I'm not trying to be mean, however, I have been rooting and putting ROMs on my phones for nine years now.
I kept up with the whole Slot A/Slot B update. However, after a while of running stock OOS, I ran into the issue of NOT A SINGLE GUIDE or A SINGLE ROM working on my phone.
I am just sharing what I thought people would find helpful. Every once in a while I see people posting, "This Guide/ROM didn't work for me. I have followed all the steps to the LETTER".
I figured it out for myself, and I am sharing it with our community on XDA. I really hope this helps. It's my first post.
Thank you for your comment.
Yippee38 said:
Thanks for that worthy contribution to this thread.
I appreciate OP's guide. I've had nothing but problems installing a custom ROM on my 6. I've been installing custom ROMs since my Galaxy S2, so I'm familiar with the process. Nothing has worked so far though. I'll give this a shot.
Click to expand...
Click to collapse
Thank you for your comment, what you are describing is my exact issue with what I have been dealing with. I really hope this helps.
If it doesn't, I will try and upload a video for this too. Good luck!
I'm pretty sure your issue has to do with firmware mismatch, (also maybe not factory resetting), nothing more. The steps you have provided are really for beginners who have no idea what is wrong with their installation procedure. Also, some ROMs are still on 9.0.9 fw where other ROMs are on 10.0.x, so for ROMs that require OOS 10 fw, you should upgrade to OOS 10 instead of 9.0.9.
EDIT: I'm pretty sure the part where you need to set up a PIN or pattern is only required for older builds of Syberia (and maybe current builds also).
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Install guide:
Boot :
Code:
fastboot boot <twrp.img>
Install :
Code:
fastboot flash recovery <twrp.img>
Download:
twrp-3.5.0-0-nairo.img
drive.google.com
Source code:
Device Tree
XDA:DevDB Information
TWRP, Tool/Utility for the Moto G 5G Plus
Contributors
vache
Source Code: https://github.com/TeamWin/android_bootable_recovery
Version Information
Status: Beta
Beta Release Date: 2020-08-27
Created 2020-08-27
Last Updated 2020-08-27
Excellent, can't wait to get a modding community for this device.
Looking forward to see how long I can get this to be used, I hope 3-4+ years.
after i booted into recovery using
fastboot boot twrp.img
i recieved the decryption message with one letter already written inside if i try it it says decryption fail ... and i cannot use sd card also because it cannot be accessed as well
what should i do to bypass encryption ? i tried format data and ended up reflashing stock rom via rescue and smart backup application ... i only want to root via magisk
Everytime you want to boot into TWRP you have to boot using fastboot flash recovery. Is there anyway around this as flashing doesn't seem to work.
What is working and what isn't.?Also, did anyone try to use GSIs on this device? Cheers
shanere51 said:
Everytime you want to boot into TWRP you have to boot using fastboot flash recovery. Is there anyway around this as flashing doesn't seem to work.
Click to expand...
Click to collapse
I've a feeling it's because there are two recovery partitions (A/B) and the flashing tools expect to see one:
Code:
nairo:/ $ ls -l /dev/block/by-name/ | grep recovery
lrwxrwxrwx 1 root root 16 1970-04-21 02:32 recovery_a -> /dev/block/sdd20
lrwxrwxrwx 1 root root 16 1970-04-21 02:32 recovery_b -> /dev/block/sdf20
nairo:/ $
@vache: Does twrp-3.4.0-0-nairo-test1.img work for Moto G 5g Plus XT2075-3?
New build :
-Updated to TWRP 3.5
-Fix slot switching
-Added fastbootd support
-Fix boot when flashed
-Fix sideload feature
Download : https://drive.google.com/file/d/1soSNdeYuvU0-P-QAJPuAoVnmWSQS8JmD/view?usp=sharing
vache said:
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Install guide:
Boot :
Code:
fastboot boot <twrp.img>
Install :
Code:
fastboot flash recovery <twrp.img>
Download:
twrp-3.5.0-0-nairo.img
drive.google.com
Source code:
Device Tree
XDA:DevDB Information
TWRP, Tool/Utility for the Moto G 5G Plus
Contributors
vache
Source Code: https://github.com/TeamWin/android_bootable_recovery
Version Information
Status: Beta
Beta Release Date: 2020-08-27
Created 2020-08-27
Last Updated 2020-08-27
Click to expand...
Click to collapse
Would it work for motog 5g indian varient
Yangasto said:
Would it work for motog 5g indian varient
Click to expand...
Click to collapse
No, they're completely different. This is for moto g power, g8 power, g fast, g8 and g stylus. If not more. Lol.
Edit lol nevermind I'm just a complete idiot. I got distracted by the vache qui rit smoking weed profile picture, it's perfect
vache said:
New build :
-Updated to TWRP 3.5
-Fix slot switching
-Added fastbootd support
-Fix boot when flashed
-Fix sideload feature
Download : https://drive.google.com/file/d/1soSNdeYuvU0-P-QAJPuAoVnmWSQS8JmD/view?usp=sharing
Click to expand...
Click to collapse
Can this TWRP work on the Moto 5G Ace. We need a lot of help over on our side. From the specs it looks like the exact same phone branded differently. We have root but we're on the A/B system with Super Sparschunks. Thanks.
Articul8Madness said:
Can this TWRP work on the Moto 5G Ace. We need a lot of help over on our side. From the specs it looks like the exact same phone branded differently. We have root but we're on the A/B system with Super Sparschunks. Thanks.
Click to expand...
Click to collapse
I also have the Metro 5G Ace, ran into same issues. Willing to help anyway I can tho not as well versed in recovery.
dagey said:
I also have the Metro 5G Ace, ran into same issues. Willing to help anyway I can tho not as well versed in recovery.
Click to expand...
Click to collapse
I think we are going to have to be hands on. Step one is creating the device tree. I don't have my linux live usb with me but I found this. https://github.com/SebaUbuntu/TWRP-device-tree-generator
Once we get our device tree maybe we can get a more experienced DEV to build the TWRP.
dagey said:
I also have the Metro 5G Ace, ran into same issues. Willing to help anyway I can tho not as well versed in recovery.
Click to expand...
Click to collapse
Flashing it did not work. Flashing it did not work. Been trying everything to get this POS to R/W.
We need a delete post button around here.
Articul8Madness said:
I think we are going to have to be hands on. Step one is creating the device tree. I don't have my linux live usb with me but I found this. https://github.com/SebaUbuntu/TWRP-device-tree-generator
Once we get our device tree maybe we can get a more experienced DEV to build the TWRP.
Click to expand...
Click to collapse
Nice way to encourage Vache. It's not like he's getting paid to do this, or owes us anything.
I'm considering buying this phone, and appreciate any and all work people are doing on it.
Pheckphul said:
Nice way to encourage Vache. It's not like he's getting paid to do this, or owes us anything.
I'm considering buying this phone, and appreciate any and all work people are doing on it.
Click to expand...
Click to collapse
What are you speaking of? Vache doesn't even HAVE my variant. And FYI I'm not getting paid either for all the work I've done on the variant, so you can dial that back.
If you get the phone just know TWRP isn't working on it right now (that I happened to have built). It is rootable and I do have R/W access finally.
Articul8Madness said:
What are you speaking of?
Click to expand...
Click to collapse
Perhaps it's a language issue, but I thought you were being very harsh on him without reason.
Thank you for the info on rooting. I've decided to buy this phone, and will be picking it up later today.
Pheckphul said:
Perhaps it's a language issue, but I thought you were being very harsh on him without reason.
Thank you for the info on rooting. I've decided to buy this phone, and will be picking it up later today.
Click to expand...
Click to collapse
Nah, not being harsh. Welcome to the Moto brave new 5G world.
I have a SM-A125M that I'm trying to use with Visible. The officially supported device is the SM-A125U. This one seems to work on the network (download speed is even good), except for VoLTE and texts. These work very strangely. They will work for a short time after a reboot or turning airplane mode on then off. Then they both fail to work.
Any suggestions? I'm wondering if I can flash the CSC from the U variant and maybe that will help? The M and U variants seem to be identical hardware wise (the U variant actually seems to even physically have 2 sim slots on the motherboard, from the pictures I've seen). Maybe I can flash the U firmware on it? How likely is it that I permanently brick it if I do that? What can I look at to make sure that I could try that without permanently bricking it (as long as I can recover it by some means, I'm fine)? Or maybe you have another idea?
Disclaimer
* 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 blame me in any way for what happens to your device, I will laugh at you.
* BOOM! goes the dynamite
Maybe flash a a125u ROM at www.samfw.com . In most of the time you can still boot into download mode and recover to a a125m ROM in case anything is wrong.
Yeah, I was considering doing just that. I figured as long as it wasn't likely to nuke the bootloader, I'd probably be OK. I'll give it a try and report back.
So, I just gave that a try. It says:
CADDIER_ID: TPA
Only official released binaries are allowed to be flashed: pit
Click to expand...
Click to collapse
Odd, since I unlocked the bootloader. I'm wondering if maybe this post is helpful: https://forum.xda-developers.com/t/...d-binaries-are-allowed-to-be-flashed.3893592/
In particular:
You must have forgot to flash the RMM fix. You either have to flash the RMM disabler or flash a custom Kernel that disables it that way before the first reboot after flashing TWRP. It's a new safety feature Samsung has introduced that locks the device after anything gets flashed or modified. Unfortunately, your only option is to re-odin stock files and then wait 7 days again for OEM unlock to appear.
After you get TWRP flashed again, mke sure you flash the fix or a custom Kernel.
Click to expand...
Click to collapse
So, maybe I just need to wait? Or maybe i just need to wait for TWRP to become available for this device before I can try this.
{
"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"
}
Disclaimer
Code:
/*
* Your warranty is... still valid?
* 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 the one choosing to make these modifications.
*/
IMPORTANT
This ROM is only for the Amazon Fire HD 10 2019 (maverick) Do not try to flash it on any other device.
This ROM requires the temporary bootloader unlock found here. Read the instructions carefully and come back once you have a working temporary unlock.
This thread will be updated should another unlock method be available.
This ROM requires that you be on the 7.3.1.0 launch firmware. If you have temp unlocked your device, you should already be on this firmware.
LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance and reliability over stock Android for your device. All the source code for LineageOS is available in the LineageOS Github repo. If you would like to contribute to LineageOS, please visit our Gerrit Code Review.
This is a custom build of LineageOS for the Amazon Fire HD 10 9th generation (maverick) which is 64-bit, allowing you to run 64-bit applications and benefit from better performance, unlike the stock OS which is 32-bit.
Working
Audio
Bluetooth
Camera
DRM L1 (playback not tested)
DT2W (double-tap-to-wake)
Media Playback (Hardware OMX)
Sensors
SDcard
USB (MTP, PTP, etc)
Wi-Fi
Not Working
SELinux is Permissive
Deep Sleep (?)
Hotspot
Notes
The stock gallery app has some issues playing media which is higher than 1920x1080, if you face this issue please try a third-party gallery app.
If you have flashed GApps, you should wait for the device to "settle" after completing setup wizard. During the first 10-ish minutes of use, the tablet could heavily lag and freeze.
Since this is a beta build, you should be prepared to face bugs and issues, along with possible stutters and lags.
You are free to use any recovery to flash this ROM, however, I recommend using the attached recovery (Lineage Recovery) to flash this ROM in order to avoid any potential issues.
How to Flash?
Spoiler: Flashing Instructions
It's important to note that you will have to boot your device with mtkclient every time you reboot!
First of all, boot the device into fastboot mode. Once you see something like => FASTBOOT mode... appear on your devices display, you can flash the Lineage Recovery image with the following fastboot command:
Code:
fastboot flash recovery lineage-18.1-XXXXXXXX-UNOFFICIAL-maverick-recovery.img
fastboot reboot recovery
This flashes the custom recovery to the devices recoverypartition, and then tells it to reboot into recovery mode.
To make sure the device boots into recovery upon the next reboot, hold the volume up button on the device after sending the preloader again with mtkclient.
DO NOT let the device boot back into FireOS at this point, as it will flash the old recovery back to the device, and you will need to start from the beginning again.
The unlocked LK indicates which mode the device will boot into, you should see something like lk boot mode = 2 on the devices display, meaning it is booting into recovery mode.
Once in Lineage Recovery, tap on "Apply Update", and then tap on "Apply from ADB". There are also options to apply updates from external storage if you wish.
Now, it's time to actually install the ROM. We are going to sideload the Lineage ZIP to our device using adb with the following command.
Code:
adb sideload lineage-18.1-XXXXXXXX-UNOFFICIAL-maverick.zip
At this point, all you need to do now is wait for the flashing process to complete.
Once finished, you will be brought back to the apply update menu. Simply press the back button to go back to the main menu.
Now, tap on factory reset and tap on the option Format data/factory reset. This is going to erase all of the old FireOS userdata from the device.
If you do not wish to install GApps, skip to the finishing up process below the GApps flashing instructions.
Optional: Flashing GApps
To install Google Services to your new ROM, you will want to start by downloading the recommended GApps package (see Downloads section).
Once downloaded, you can follow a similar process that you did for installing the ROM ZIP.
Tap on "Apply Update" again, and "Apply from ADB".
Once you have done that, you can sideload the GApps package with the following command:
Code:
adb sideload MindTheGapps-11.0.0-arm64-XXXXXXXX_XXXXXX.zip
If you wish to install other addons (e.g. Magisk), repeat the same steps, substituting the GApps package file name with the Magisk zip file name.
Finishing Up
Once you have done everything you need to do in Lineage Recovery, it's time to boot into the new ROM.
It's important to note that the reboot system now option does not work correctly, so follow these steps to workaround it.
Tap on Advanced, and then tap on Reboot to bootloader.
Once you see => FASTBOOT mode... on the devices display once again, type the following fastboot command to reboot.
Code:
fastboot reboot
After a short while, you should see the LineageOS boot animation on your device. First boot usually takes 5-10 minutes, especially if you have installed Google Services.
Wait for the device to boot and you should be presented with the setup wizard. Enjoy!
Downloads
ROM
Recommended GApps
Source Code
Device
Kernel
Vendor
Screenshots attached below.
Reserved #3
Amazing job.
@bengris32 - great to see this post, thanks!
I see you've put vendor and kernel on github already.
Is there a maverick device tree you could recommend for a lineage self-build? (Maybe: https://github.com/PQEnablers/android_device_amazon_maverick ?)
JJ2017 said:
@bengris32 - great to see this post, thanks!
I see you've put vendor and kernel on github already.
Is there a maverick device tree you could recommend for a lineage self-build? (Maybe: https://github.com/PQEnablers/android_device_amazon_maverick ?)
Click to expand...
Click to collapse
The device tree is currently private for whatever reason. I will let bengris know through Telegram.
JJ2017 said:
@bengris32 - great to see this post, thanks!
I see you've put vendor and kernel on github already.
Is there a maverick device tree you could recommend for a lineage self-build? (Maybe: https://github.com/PQEnablers/android_device_amazon_maverick ?)
Click to expand...
Click to collapse
Hey, currently the new device tree is not open source yet, I will make it open source once I fix the remaining issues (mainly getting SELinux Enforcing). Kernel tree is open due to the GPL license.
Hi there, I'm having issue with this ROM as it is bootlooping after install with TWRP or provided LOS Recovery. For what it's worth, I have a maverick that is permanently bootloader unlocked, so as far as I know I do not have to use mtkclient. I'm not sure if this is a hard requirement. Flashing via TWRP or provided LOS recovery does not work for me. Am I missing something?
I will pay $1,000 or more to anyone who can open bootloader to the new systems amazon
jasonjohn95 said:
Hi there, I'm having issue with this ROM as it is bootlooping after install with TWRP or provided LOS Recovery. For what it's worth, I have a maverick that is permanently bootloader unlocked, so as far as I know I do not have to use mtkclient. I'm not sure if this is a hard requirement. Flashing via TWRP or provided LOS recovery does not work for me. Am I missing something?
Click to expand...
Click to collapse
Hello, interesting to say you have "a maverick that is permanently bootloader unlocked", is it an engineering unit? Could you provide more details such as the firmware version you are on? Also, which kind of boot loop, does it at least get past the Amazon logo or just reboot? Or do you see LineageOS boot animation which never ends?
JJ2017 said:
@bengris32 - great to see this post, thanks!
I see you've put vendor and kernel on github already.
Is there a maverick device tree you could recommend for a lineage self-build? (Maybe: https://github.com/PQEnablers/android_device_amazon_maverick ?)
Click to expand...
Click to collapse
FYI, I have open sourced the device tree, so feel free to build it yourself! You SHOULD be able to compile a booting build this time, just make sure to sync the device tree, kernel tree and vendor tree.
Hello, how are you? I have a question regarding the installation of the ROM. If I have the OS in the Fire OS 7.3.2.7 version, can I still install the ROM without any problem? Greetings from Chile, sorry for use google translate
ＤＥＭＯＮ said:
Hello, how are you? I have a question regarding the installation of the ROM. If I have the OS in the Fire OS 7.3.2.7 version, can I still install the ROM without any problem? Greetings from Chile, sorry for use google translate
Click to expand...
Click to collapse
no, you have to be on 7.3.1.0. Only the first 3-4 months of release of the device was rootable and available to any exploits. Before jan 2020.... If your was bought before that, you might be able to downgrade...
Michajin said:
no, you have to be on 7.3.1.0. Only the first 3-4 months of release of the device was rootable and available to any exploits. Before jan 2020.... If your was bought before that, you might be able to downgrade...
Click to expand...
Click to collapse
I have installed many ROMs in the past, it is my first time downgrading one of these tablets, as if that were not enough, I barely understand the tutorial, it is that I have never used mtkclient and I do not understand the "temporary bootloader unlock" please... Can you help me?
ＤＥＭＯＮ said:
I have installed many ROMs in the past, it is my first time downgrading one of these tablets, as if that were not enough, I barely understand the tutorial, it is that I have never used mtkclient and I do not understand the "temporary bootloader unlock" please... Can you help me?
Click to expand...
Click to collapse
Depends on when you bought your tablet.... When released it had a exploit. The bootrom was available to do some things..... If the device was released from amazon after about jan 2020, you are probably out of luck. The biggest problem here is even if you have the root access, you have to plug it in to a PC and run the script to get it to boot every time. It is still partially locked down.... Temp unlock (and temp root, which you have to run after boot every time) means you can get access but have to run the script every time....
ＤＥＭＯＮ said:
I have installed many ROMs in the past, it is my first time downgrading one of these tablets, as if that were not enough, I barely understand the tutorial, it is that I have never used mtkclient and I do not understand the "temporary bootloader unlock" please... Can you help me?
Click to expand...
Click to collapse
that being said, i hope you have updates disabled, because there might be another root option coming.
bengris32 said:
Hello, interesting to say you have "a maverick that is permanently bootloader unlocked", is it an engineering unit? Could you provide more details such as the firmware version you are on? Also, which kind of boot loop, does it at least get past the Amazon logo or just reboot? Or do you see LineageOS boot animation which never ends?
Click to expand...
Click to collapse
I'm not sure exactly what you're looking for (or how to find it on the current ArrowOS 13 build I'm running), so I'm attaching my entire getprop dump. Sorry!
The Maverick I have is a retail Maverick, but has been bootloader unlocked by "official" means for development as I am an Amazon employee/engineer on some of their Android products, so I guess I'm cheating on that front
The device will get to the Amazon logo, and then reboot after some time back again to the Amazon logo. I am able to boot into recovery with the vol+ key.
Another thing that might be an issue, I failed to check if I was originally on 7.3.1.0 before flashing, which could be the cause of the issues...oops
Michajin said:
Depends on when you bought your tablet.... When released it had a exploit. The bootrom was available to do some things..... If the device was released from amazon after about jan 2020, you are probably out of luck. The biggest problem here is even if you have the root access, you have to plug it in to a PC and run the script to get it to boot every time. It is still partially locked down.... Temp unlock (and temp root, which you have to run after boot every time) means you can get access but have to run the script every time....
Click to expand...
Click to collapse
Thank you very much for your answers, I don't know when I bought the Tablet, I forgot, but I imagine that it is possible to downgrade to Fire OS 7.3.1.0 in some way which I don't know, apart from I don't understand the tutorials that I found on XDA, I really have 2 days and my head hurts a lot because I do not understand the explanations of the users, if there was even the slightest possibility that you could contact me and tell me step by step what I should do and I will show you with screenshots how I progress and do everything to have a guide, I promise to pay you if I succeed in installing this ROM by PayPal
jasonjohn95 said:
I'm not sure exactly what you're looking for (or how to find it on the current ArrowOS 13 build I'm running), so I'm attaching my entire getprop dump. Sorry!
The Maverick I have is a retail Maverick, but has been bootloader unlocked by "official" means for development as I am an Amazon employee/engineer on some of their Android products, so I guess I'm cheating on that front
The device will get to the Amazon logo, and then reboot after some time back again to the Amazon logo. I am able to boot into recovery with the vol+ key.
Another thing that might be an issue, I failed to check if I was originally on 7.3.1.0 before flashing, which could be the cause of the issues...oops
Click to expand...
Click to collapse
Let's try to dump pstore from the device when it's trying to boot then.
Wait for the device to reboot after being on the amazon logo, immediately on the next boot up, go into recovery mode. Then, enable ADB.
You can dump pstore with the following adb command (adbd should run as root in recovery):
adb pull /sys/fs/pstore
Hopefully there should be some logs in there which you can attach here, if not, keep retrying until you get something in there. If you are 100% nothing is being dumped to pstore, just let me know.
As a side note, I am using the kernel source and blobs from the 7.3.2.7 firmware, so I'm not sure why it's not seeming to boot on later firmware.
bengris32 said:
FYI, I have open sourced the device tree, so feel free to build it yourself! You SHOULD be able to compile a booting build this time, just make sure to sync the device tree, kernel tree and vendor tree.
Click to expand...
Click to collapse
It works!
Completed a Lineage build using the info on "amazon-mt8183-devs" repo - now installed & working fine.
Many Thanks