Related
Short version of question: How can I unbrick my ONEPLUS 3 (A3000) if I cannot boot to Android and OEM Unlock AND USB Debugging both have not been enabled?
Long version: Phone was recently purchased second hand from a third-party market (Kijiji, kind of like craigslist for Canadians). Person I bought it from claimed in the ad that the device was in a bootloop and couldn't access the OS. I had in the past successfully saved a ONEPLUS 1 from bricked status, so I didn't feel a simple bootloop would pose much of an issue. That, and at the price he was selling I really couldn't turn it down.
I tried various different methods of restoring the phone's partitions, OS, and firmware to stock/custom, but had no real luck with any (I will list below what I have attempted). If there was a root cause of this, I believe it's due to the fact that some part of the phone's storage partition (boot or system if I had to guess) had become corrupted at some point. Given the volume of threads I've seen here and elsewhere online, I wouldn't rule out a bad OTA flash, but doesn't really matter. What does matter, however, is that the Android OS is inaccessible despite my best efforts, and the bootloader is set to locked and ADB Debugging remains off.
Generally speaking, is there a way to access Developer Options to correct both these issues through terminal or a tool? I'm confident that I can get my device working again if I could access this menu, but as of yet I have had no luck.
Methods used to restore/info worth mentioning
While I don't doubt their effectiveness at large, for whatever reason I have yet to find a tool/guide that yields the anticipated results upon completion. MSM Download Tool (V3 and V4) have both been downloaded, executed, and completed numerous times, but will still not boot past the loading screen upon completion.
According to Unified Android Toolkit, my device build is being detected as "OnePlus3 7.0 NRD90M" and All-in-One Toolkit is showing that Android 6.0.1 is installed.
Drivers are all installed correctly, as proven both via tools downloaded and through Windows CMD terminal (adb devices, fastboot devices, adb get-state, etc)
Stock recovery and bootloader modes can both be reached through both hardware keys and software commands. I will note that it seems to take longer than I'd expect to boot to either of these modes using hardware keys.
I have utilized multiple USB ports, Type-C cables, different OS' on two laptops (MS Windows 10 and 7, FWUL Linux). I usually have no problem with the device being detected by the system. When I have, it usually involved one pesky USB cord.
common commands used and their effects:
fastboot OEM unlock: fails, cannot be done remotely
fastboot flash x: fails, remote: flashing partitions not allowed
ADB push: fails. cannot access partition
ADB devices: device is seen by system with serial and state
fastboot devices: device is seen by system with serial
ADB sideload: varying results. Some will fail at 0% citing "total xfer: 0.00x", some will reach 47% and fail (always exactly 47% oddly). Generally if the sideload operation passes 47% it will complete.
fastboot format/erase x: fails, partition formatting/erasing not allowed
fastboot continue: executes, but does not help with android bootloop issue as I had hoped
While I searched for an answer online, I did come across an infosec whitepaper regarding ONEPLUS 3 vulnerabilities, though it was over a year old. To my surprise, the command they had been entering works on my device, but I'm not sure how to properly use it effectively. The command used was fastboot OEM boot_mode [rf/wlan/ftm/normal]. Now, I was unable to determine what each of the triggers does, but what I did discover is that with boot_mode set to rf, my device would display chinese/korean lettering in lieu of the usual ONEPLUS logo with "powered by Android" below. This is also how I managed to have my device show up in CMD terminal for ADB commands to be issued. To the best of my knowledge though, there doesn't seem to be much point to it as I couldn't push/pull any files. Does anybody know where I could find more info on this command, as I'd like to know what the other triggers accomplish.
I've just about exhausted every available resource looking for an answer, but im still coming up short. I've gone as far as contacting ONEPLUS directly, but without proof of purchase they can't (more accurately won't) help me. And while it's not a business practice I would personally support, I can understand why they have it implemented. I've contacted a few phone shops in the area, but none have been able to assist me further than I've already gotten in this process.
I apologize again for creating a new thread about this, but I felt my circumstances warranted a new thread due to the bulk of the others having either an unlocked bootloader or TWRP installed, neither of which I do.
So, can anybody offer their help or suggest something I haven't already tried? Or should I be on EBAY looking for motherboards? Thanks in advance.
Calgary84 said:
Short version of question: How can I unbrick my ONEPLUS 3 (A3000) if I cannot boot to Android and OEM Unlock AND USB Debugging both have not been enabled?
Long version: Phone was recently purchased second hand from a third-party market (Kijiji, kind of like craigslist for Canadians). Person I bought it from claimed in the ad that the device was in a bootloop and couldn't access the OS. I had in the past successfully saved a ONEPLUS 1 from bricked status, so I didn't feel a simple bootloop would pose much of an issue. That, and at the price he was selling I really couldn't turn it down.
I tried various different methods of restoring the phone's partitions, OS, and firmware to stock/custom, but had no real luck with any (I will list below what I have attempted). If there was a root cause of this, I believe it's due to the fact that some part of the phone's storage partition (boot or system if I had to guess) had become corrupted at some point. Given the volume of threads I've seen here and elsewhere online, I wouldn't rule out a bad OTA flash, but doesn't really matter. What does matter, however, is that the Android OS is inaccessible despite my best efforts, and the bootloader is set to locked and ADB Debugging remains off.
Generally speaking, is there a way to access Developer Options to correct both these issues through terminal or a tool? I'm confident that I can get my device working again if I could access this menu, but as of yet I have had no luck.
Methods used to restore/info worth mentioning
While I don't doubt their effectiveness at large, for whatever reason I have yet to find a tool/guide that yields the anticipated results upon completion. MSM Download Tool (V3 and V4) have both been downloaded, executed, and completed numerous times, but will still not boot past the loading screen upon completion.
According to Unified Android Toolkit, my device build is being detected as "OnePlus3 7.0 NRD90M" and All-in-One Toolkit is showing that Android 6.0.1 is installed.
Drivers are all installed correctly, as proven both via tools downloaded and through Windows CMD terminal (adb devices, fastboot devices, adb get-state, etc)
Stock recovery and bootloader modes can both be reached through both hardware keys and software commands. I will note that it seems to take longer than I'd expect to boot to either of these modes using hardware keys.
I have utilized multiple USB ports, Type-C cables, different OS' on two laptops (MS Windows 10 and 7, FWUL Linux). I usually have no problem with the device being detected by the system. When I have, it usually involved one pesky USB cord.
common commands used and their effects:
fastboot OEM unlock: fails, cannot be done remotely
fastboot flash x: fails, remote: flashing partitions not allowed
ADB push: fails. cannot access partition
ADB devices: device is seen by system with serial and state
fastboot devices: device is seen by system with serial
ADB sideload: varying results. Some will fail at 0% citing "total xfer: 0.00x", some will reach 47% and fail (always exactly 47% oddly). Generally if the sideload operation passes 47% it will complete.
fastboot format/erase x: fails, partition formatting/erasing not allowed
fastboot continue: executes, but does not help with android bootloop issue as I had hoped
While I searched for an answer online, I did come across an infosec whitepaper regarding ONEPLUS 3 vulnerabilities, though it was over a year old. To my surprise, the command they had been entering works on my device, but I'm not sure how to properly use it effectively. The command used was fastboot OEM boot_mode [rf/wlan/ftm/normal]. Now, I was unable to determine what each of the triggers does, but what I did discover is that with boot_mode set to rf, my device would display chinese/korean lettering in lieu of the usual ONEPLUS logo with "powered by Android" below. This is also how I managed to have my device show up in CMD terminal for ADB commands to be issued. To the best of my knowledge though, there doesn't seem to be much point to it as I couldn't push/pull any files. Does anybody know where I could find more info on this command, as I'd like to know what the other triggers accomplish.
I've just about exhausted every available resource looking for an answer, but im still coming up short. I've gone as far as contacting ONEPLUS directly, but without proof of purchase they can't (more accurately won't) help me. And while it's not a business practice I would personally support, I can understand why they have it implemented. I've contacted a few phone shops in the area, but none have been able to assist me further than I've already gotten in this process.
I apologize again for creating a new thread about this, but I felt my circumstances warranted a new thread due to the bulk of the others having either an unlocked bootloader or TWRP installed, neither of which I do.
So, can anybody offer their help or suggest something I haven't already tried? Or should I be on EBAY looking for motherboards? Thanks in advance.
Click to expand...
Click to collapse
Thanks for the exhaustive description. You seem to have covered every known method. If the MSM Tool also fails, I think that it is a hardware issue and you are better off searching for a new motherboard instead of wasting further time on trouble-shooting.
Best of luck!
tnsmani said:
Thanks for the exhaustive description. You seem to have covered every known method. If the MSM Tool also fails, I think that it is a hardware issue and you are better off searching for a new motherboard instead of wasting further time on trouble-shooting.
Best of luck!
Click to expand...
Click to collapse
I was afraid of that..... is there a way to test a given hardware component?
Have you tried the unbrick tool FULL updated: https://mega.nz/#!NmhhgZyB!CM7Fw8VjECiMIhh4gRXUx24QVCiE599_ZFAPDf08AiM
acetone802000 said:
Have you tried the unbrick tool FULL updated: https://mega.nz/#!NmhhgZyB!CM7Fw8VjECiMIhh4gRXUx24QVCiE599_ZFAPDf08AiM
Click to expand...
Click to collapse
Indeed I have, dozens of times between the full and mini versions. I've even gone as far as running the toolkits featuring MSMDownloadTool v4.0 to see if it achieved different results (it did not). The mini tool would finish doing its thing (turned the text green upon completion),but I would face varying partitions not being flashed correctly. The full version completes and does not have these varying partitions missing, but the device would then be either stuck in a bootloop where it will eventually reboot itself, or would hang indefinitely on the "swirling dots" loading screen. I tried the remedy of deleting cache in recovery, but this did not help.
deleted
***UPDATE*** - As I mentioned in this thread earlier, I noticed a discrepancy between the variant type listed on my actual device and the variant type returned when queried via fastboot. This got me thinking, and to make a long story somewhat shorter, I found that while most stock Oxygen images I attempt to sideload onto the device fail (at precisely 47%, oddly), I was able to sideload two different Hydrogen images without any resistance at all. I'm guessing something to do with the eMMC vs UFS file storage systems and how each OS uses them.
So I got Hydrogen flashed onto my my device. Smooth sailing, right? Afraid not. Despite fastboot's output clearly stating it was a successful transfer, and the stock recovery on the device echoing this, I still cannot get the OS to load. Now i' stuck with the loading screen hanging indefinitely prior to animation occurring, so basically the static ONEPLUS logo. Factory resets and cache wipes have done nothing to help the situation along. Conventional wisdom from the threads here seem to say using the MSMTool is the right answer..... and thus the circle of frustration is complete with me arriving back where I started. Does anybody have another suggestion I can try out? Still can't flash/boot to TWRP, unlock bootloader, or access Android to activate USB Debug/OEM Unlock either btw.
Have you tried flashing just the firmware, i havent flashed in years but i would assume you could sideload the firmware as well?
voodooline said:
Have you tried flashing just the firmware, i havent flashed in years but i would assume you could sideload the firmware as well?
Click to expand...
Click to collapse
Guess who didn't read? And after a year without flashing + a lack of reading skills, you still think you could solve this case? That's a spirit.
===
You better do pm some devs in dev section and point them to this thread and see if they can help, if you are still curious.
My guess is dead emmc, it can be replaced without buying the whole board.
150208 said:
Guess who didn't read? And after a year without flashing + a lack of reading skills, you still think you could solve this case? That's a spirit.
===
You better do pm some devs in dev section and point them to this thread and see if they can help, if you are still curious.
My guess is dead emmc, it can be replaced without buying the whole board.
Click to expand...
Click to collapse
I did read it, its funny always someone who has to be a **** about things. I should have been more specific. He was able to flash h2os. So he could try to flash the firmware for h2os to see if that gets it to boot.
voodooline said:
I did read it, its funny always someone who has to be a **** about things. I should have been more specific. He was able to flash h2os. So he could try to flash the firmware for h2os to see if that gets it to boot.
Click to expand...
Click to collapse
Magnificent, bro.
You're a truly genius.
Hello,
I'm not sure if this goes here or where actually. When I did a search on the site " LineageOS MicroG Drivers / LineageOS Essential PH-1 / Essential PH-1 Drivers" only LineageOS popped up. If this isn't supposed to be posted here, please inform me and I'll remove it, and please tell me or suggest where this post should live.
So, I'm 100% new to this. I have a Essential PH-1 that now has LineageOS MicroG Mata 16.0 on it. I was walked through the installation from a helpful hand on reddit. I learned alot and Life was GREAT !! I recently ( yesterday ) had some PC issues, and completely wiped the entire system. Now, with my very very limited knowledge I'm trying to put adb - fastboot and TWRP back on my computer, so when updates come around or whatnot I will be ready.
I've achieved having getting adb and fastboot to work or so it seems that way when I execute the commands .\adb.exe devices the output is the same from before. This is where I assume its the drivers bc when I execute .\adb.exe reboot bootloader I do reboot into the bootloader but my phone in windows goes from the connection of PH-1 to disconnected and MATA is connected, but says there are no drivers. So, my phone simply sits in the bootloader mode and I'm stuck there. When I go into device manager in Windows I the little yellow caution sign under other devices on Mata / PCI Serial Port / PCI Simple Communications Controller.
I have searched and there are so many sites that pop up, I'm not sure which one is legit or not. I hope I was clear explaining all of this. I really need any help, suggestions, or anything at this point. Its that frustrating feeling that I can't find that one simple thing ( assuming it drivers) to fix this issue.
Thanks Everyone !!
No problem here, but you will get more response in https://forum.xda-developers.com/android/software/lineageos-microg-t3700997
If you installed https://download.lineage.microg.org/manta/ you don't need a computer for update. Settings system advanced update
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been modified before it was cool.
Hi everyone, similar to the previous threads for
OP3, OP3T, OP5, OP5T, OP6, OP6T, OP7, OP7PRO, regular OP7T, T-Mobile OP7T, regular OP7TPRO and T-Mobile OP7TPro 5G here are the EDL packages (also known as MSM tools or unbrick tools) that can revive a bricked OnePlus 8 Pro.
You should also be able to rollback your phone to a previous release of OOS with them if for some reason you want to go back to an older firmware
You can download the following versions:
IN11BA tools (european firmware):
ANDROID 10:
OOS 10.5.4
OOS 10.5.6
OOS 10.5.8
OOS 10.5.10
OOS 10.5.11
ANDROID 11:
OOS 11.0
OOS 11.0.1.1
OOS 11.0.2.2
OOS 11.0.3.3
OOS 11.0.4.4
Mirror for first and last MSMs per Android version: https://onepluscommunityserver.com/
IN11AA tools (international firmware):
ANDROID 10:
OOS 10.5.4
OOS 10.5.5
OOS 10.5.10
OOS 10.5.11
OOS 10.5.12
ANDROID 11:
OOS 11.0
OOS 11.0.1.1
OOS 11.0.2.2
OOS 11.0.4.4
Mirror for first and last MSMs per Android version: https://onepluscommunityserver.com/
IN11DA tools (indian firmware):
ANDROID 10:
OOS 10.5.4
OOS 10.5.5
OOS 10.5.8
OOS 10.5.9
OOS 10.5.10
OOS 10.5.11
OOS 10.5.12
OOS 10.5.13
ANDROID 11:
OOS 11.0
OOS 11.0.1.1
OOS 11.0.2.2
OOS 11.0.3.3
OOS 11.0.4.4
Mirror for first and last MSMs per Android version: https://onepluscommunityserver.com/
Warning:
It is advised to take backup of /persist partition before crossflashing (eg going from International to Indian build) as fingerprint reader may give an error related to enrollment issue. You can do so by using dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img (you must have root access, which is not something I'm going to explain here) and moving it to your computer/cloud.
Instructions:
Launch MsmDownloadTool V4.0.exe.
On Android 11 MSMs and up Windows 7 users may need to launch MsmDownloadTool V4.0_Win7.exe instead, but it hasn't been tested
On the login prompt select "Other" in the dropdown menu and click on Next.
Wait a few seconds until main window shows up.
Click on Target button and select O2 while using international tool or India while using indian tool or EU when using european tool.
Power your device off.
Maintain volume up and volume down keys to get into Qualcomm EDL mode.
Plug your device to your computer using stock OnePlus cable. (You may let volume keys go once done.)
Click on Enum to be sure your device is detected and press Start.
Wait ~300 seconds.
Enjoy your brand new device.
FAQ:
Does this work on Mac or on Linux?
Unfortunately no, tool is Windows only. You should need at least Windows 7.
Why is my antivirus freaking out when unzipping the archive or running the tool?
In an effort to protect reverse engineering from being done (and by extension prevent conversion process like it was done on 6T and 7Pro), OnePlus now use VM Protect V3 in their MSM tools. As this tries to detect debug environment, this is seen as malicious behaviour by some antivirus.
My device isn't detected when I click on "Enum" button
Go to device manager and make sure your phone shows up as QDLOADER 9008.
If it shows up as QHUSB_BULK, it means Qualcomm driver wasn't installed automatically by Windows Update. Download the latest one from Microsoft website at http://download.windowsupdate.com/c..._fba473728483260906ba044af3c063e309e6259d.cab (source https://www.catalog.update.microsoft.com/Search.aspx?q=qualcomm hs usb 9008 ) and install it manually by right clicking on QHUSB_BULK and selecting "Update driver software" and "Browse my computer for driver software" to where you downloaded CAB file.
MSM tool is stuck on "Param pre-processing"
Ensure you're using the Qualcomm drivers linked above.
MSM tool is stuck on "Sahara communication failed"
Unplug your phone, get in fastboot mode, turn off phone, wait 15 secondes and get back in Qualcomm EDL mode. You can also try using a USB 2.0 port instead of a 3.0 one.
What is SMT Download mode?
Just don't try to unlock that mode, it will wipe your IMEI and your Widevine certificate if you use it.
How can I fix "SMT config not found" error?
Please refer to https://forum.xda-developers.com/showpost.php?p=83448961&postcount=61, all credits to @Shadow12347 for finding it out.
Credits:
@LL Starks for getting 10.5.4 IN11AA and 10.5.4 IN11DA links from OnePlus
@pysklona for testing 10.5.4 international and indian versions
@Titokhan for being a friend and providing inspiration in writing
@headsh0t95 for being a friend and suggesting me to request an access to upload files on AndroidFileHost now one year ago for my previous threads
@AndroidFileHost for the hosting
@Zer0De8th for OOS 11.0/11.0.1.1/11.0.2.2/11.0.3.3/11.0.4.4 MSMs.
OnePlus for the device and OS
Related: [OnePlus 8 Pro][ROM][OTA][Oxygen OS] Repo of Oxygen OS Builds
That was quick! Great thank you.
i see oneplus 8 is IN21 ? 8Pro : IN11
empty.cad said:
i see oneplus 8 is IN21 ? 8Pro : IN11
Click to expand...
Click to collapse
Fixed typo in thread thanks, ironically enough I didn't have it in the title, guess that's what I get for making threads at the hour where people normally sleep in my timezone...
I've installed the global version of Oxygen OS on OP8 Pro but I definitely bricked it because it's stuck on the boot screen. Tried using your software to unbrick but the phone is not showing up at all, even after using the power button + volume up. Also unable to switch the phone off with the power button. Any advice?
jaques1979 said:
I've installed the global version of Oxygen OS on OP8 Pro but I definitely bricked it because it's stuck on the boot screen. Tried using your software to unbrick but the phone is not showing up at all, even after using the power button + volume up. Also unable to switch the phone off with the power button. Any advice?
Click to expand...
Click to collapse
As said in the OP, the key combination to get in EDL mode is volume up and down, not power and volume up.
How come your device doesn't turn off? It normally should after maintaining power button for 30 seconds.
太好了谢谢。
Thanks! Nice work, tool for op 8 vanilla coming soon?
Some_Random_Username said:
Fixed typo in thread thanks, ironically enough I didn't have it in the title, guess that's what I get for making threads at the hour where people normally sleep in my timezone...
Click to expand...
Click to collapse
Tested Done , thank bro
Wow, that was quick!
Thanks for the posting the msm tool and for your due diligence.:good:
Added EU 10.5.4 IN11BA to go back to EU build directly.
Hi,
I bought a Chinese Version, tried to install international rom, didn't know oneplus started locking their phones, and I believe I bricked it.
Any version to unbrick the Chinese version?
Thank you
kniaz759 said:
Hi,
I bought a Chinese Version, tried to install international rom, didn't know oneplus started locking their phones, and I believe I bricked it.
Any version to unbrick the Chinese version?
Thank you
Click to expand...
Click to collapse
You should be able to use any of the tools present in the OP but I would advise that you backup your /persist partition before (in main window of tool, press F8, tick "persist", input "oneplus" as password, press "ok" and click on the readback button).
Partition will be at the root of your system drive.
Some_Random_Username said:
You should be able to use any of the tools present in the OP but I would advise that you backup your /persist partition before (in main window of tool, press F8, tick "persist", input "oneplus" as password, press "ok" and click on the readback button).
Partition will be at the root of your system drive.
Click to expand...
Click to collapse
When I click to launch MsmDownloadTool V4.0.exe, nothing happens, just a small window comes up stating "program has been started but nothing happens...
EDIT: I got it working, driver needed restart.
I cannot enter EDL mode. I can reboot between system, recovery and bootloader but cannot enter EDL mode. I help vol+ and - for a while several times, nothing.
Another EDIT: I got into EDL via adb, it's doing it's thing now.
Some_Random_Username said:
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been modified before it was cool.
Hi everyone, similar to the previous threads for
OP3, IN11BA tools (european firmware):[/B]
ANDROID 10:
[URL="https://androidfilehost.com/?fid=4349826312261777331"]OOS 10.5.4
IN11AA tools (international firmware):
ANDROID 10:
OOS 10.5.4
IN11DA tools (indian firmware):
ANDROID 10:
OOS 10.5.4
Click to expand...
Click to collapse
I have not been able to determine the different 8 Pro devices, and since you seem to be on top of everything, I would like to ask a question.
OnePlus is calling the 8 Pro they are selling here a "US" version, and i don't see anything like that here or elsewhere. The overseas versions are "Global" which I would guess is the same as your "international" above. Since I am looking at a possible Global version, I am not sure if it will have the same frequencies as the OnePlus one.
If you can help - thanks. After I get an 8, I will be using your tool and firmware to take My 7 McLaren 5G back to stock.
Can I unlock a T-Mobile device to install an International version??
gpompeus said:
Can I unlock a T-Mobile device to install an International version??
Click to expand...
Click to collapse
From previous posts elsewhere (if you look), no international working on that. If it could be, I would not be looking at a non-carrier replacement.
t-mizzle said:
When I click to launch MsmDownloadTool V4.0.exe, nothing happens, just a small window comes up stating "program has been started but nothing happens...
EDIT: I got it working, driver needed restart.
I cannot enter EDL mode. I can reboot between system, recovery and bootloader but cannot enter EDL mode. I help vol+ and - for a while several times, nothing.
Another EDIT: I got into EDL via adb, it's doing it's thing now.
Click to expand...
Click to collapse
Can you explain how?
I am also stuck between fastboot and recovery, can't seem to enter EDL
any guide how to do it?
Pressing Vol up + Vol down + power gets me to fastboot mode not EDL
Thanks.
kniaz759 said:
Can you explain how?
I am also stuck between fastboot and recovery, can't seem to enter EDL
any guide how to do it?
Pressing Vol up + Vol down + power gets me to fastboot mode not EDL
Thanks.
Click to expand...
Click to collapse
Are you trying to use the unbrick tool? Also I think EDL is just vol+ and vol-, no power button for that. It did not work for me with buttons, I got into EDL via adb, adb fastboot EDL, I believe.
I would like to thank everyone for trying to help me out. It was a mentally exhausting day, I must have wiped my phone at least 15 times. I'm giving it a break for now, will get back into it over the weekend.
LineageOS is a free, community built, aftermarket firmware distribution of Android 10 (Q), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
Known issues:
You tell me
Instructions :
1. Boot into twrp
2. Advanced -> ADB Sideload -> Swipe
3. adb sideload copy-partitions.zip
4. Go back into sideload mode
5. adb sideload lineage.zip
6. Wipe Data
7. Reboot to bootloader
8. fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
Downloads :
https://build.lolinet.com/file/lineage/ginna/
Source Code: https://github.com/motoe7
ROM OS Version: LineageOS 17.1
ROM Kernel: Linux 4.9
Version Information
Status: Stable
Credits:
Electimon - The entire device bringup
Rohan Hasabe - TWRP bringup, helped with device bringup
betaxab - Gave devices, helped with TWRP and device bringup
2/6/2021:
Fixed random crashes - https://build.lolinet.com/file/lineage/ginna/lineage-17.1-20210206-UNOFFICIAL-ginna.zip
Thanks to everyone who contributed to these bits, I'm hopeful that by the end of the year I will be using my new moto-e-2020 as my main phone to replace my aging moto-g-2015. I've got a couple first bugs/issues/showstoppers to report, but first I think it's important to note-
Finally I'm able to go to walmart (in the usa) and buy a sub $100 ($70) 'roid (boostmobile) phone (meeting some other criteria as well) which I can immediately install a (mostly?/sdks/tools) non-google-built os on. I erred a bit by doing lots of research (to avoid paying more for a moto g7) and forgetting that the moto-e-2020 is *not* at the moment on motorola's list of models their registered (free) dev program will give bootloader unlock codes for. However after thinking I was going to have to return the phone, I parsed the verbiage on their page and decided to just try 'fastboot oem get_unlock_data'. Then tried going through motorola's unlock code process. To my pleasant surprise, they did give me an unlock code. My next hiccup happened when I was disappointed to discover the 'allow oem unlucking' option was greyed out. I netsearched and found a similar samsung issue that was resolved on phones that hadn't been updated/activated by setting their date back a week. That didn't work here, but what did work was giving my new phone access to wifi and letting it start an update. After a few minutes, while it was still updating, the 'allow oem unlocking' was no longer greyed out, and the rest of the install was straightforward enough (getting used to a and b slots for recovery).
Anyway, as for the first glaring issues-
1) random reboots, seemed at first yesterday it would average less than 10 minutes of uptime and rarely an hour. Seems a bit better right now, I'm seeing if I can get some adb logcat output of interest. Let me know if there are other tests/logs I should do. I haven't yet tried the modded lineageos18. The image I used was lineage-17.1-20210119-UNOFFICIAL-ginna.zip.
2) mobile data won't work. I note that I first activated after installing this rom. I wonder if it would have helped to activate with stock android like I probably did long ago with my moto-g-2015. Note that it shows up as 't-mobile', however given my moto-g with boost showed up as 'sprint' and boost using sprint infra which merged with t-mobile recently...? My aboutphone:simstatus shows 'network:t-mobile', 'mobile network state:disconnected' (but mobile data enabled). If I uncheck automatic network selection, I can click on 'boost' by name on a list (that doesn't include t-mobile) and it will say 'connected' right away, but with no change I see otherwise. There was a weird thing with activation as an additional line, boost first charged me $20, then later charged me $30. And the confirmation sms for the activation happened hours later, but mobile data still isn't working.
3) I'd like to know if twrp is really necessary. I noticed a recovery.img in the download directory, guessing that might be the lineageos17.1 version I was happy to see available for my moto-g-2015. I'm guessing I could try it myself, but I would like to avoid brick-risky things.
4) I wonder if the 'your phone has an unlocked bootloader / can't be trusted' post unlock splash screen can be changed (with the same?) images that are available for the moto-g-2015 (that I read can be used on some other models as well). At least with the moto-e-2020 the splash has a black background.
Feel free to let me know if there are tests I can do or logs I can provide to help. Looks very promising, but not quite usable for me so far.
hi yes please do
adb logcat > logcat.txt
and send me the logcat.txt after around 10 seconds of it running
i've fixed the random crashes.
2/6/2021:
Fixed random crashes - https://build.lolinet.com/file/lineage/ginna/lineage-17.1-20210206-UNOFFICIAL-ginna.zip
Electimon said:
2/6/2021:
Fixed random crashes - https://build.lolinet.com/file/lineage/ginna/lineage-17.1-20210206-UNOFFICIAL-ginna.zip
Click to expand...
Click to collapse
Confirmed (so far, but I'm optimistic). Also I'm quite happy to report that mobile data is now working for me as well (maybe just a reinstall would have fixed?).
The most glaring (new?, not sure) issue/bug now is that speaker output doesn't seem to work except during calls. If I plug in headphones I do get output. Jacksensing failure could be an explanation?
Then after that, I'm getting the sense that the microphone level/gain is not good. Testing by leaving a vmail on my moto-g-2015 the level of the audio on the message seems too low. That is seperate from the longstanding issue I have had with the moto-g-2015/lineage output level. Long ago there was a known issue with a mixer_paths.xml workaround, though I've just lived with seeming lower, but barely tolerable, level since then. I've always planned on going full aosp rebuild with removing whatever softvol max limits are in place whereever. But the mote-e-2020 definitely doesn't have that problem (side by side comparison of same vmailbox checking). But it does seem with this rom the mote-e-2020 has too low mic/gain level. Seems like there could be a standardized testrig used for lineageos qa that could report expected decibel levels/metric on the devices wiki so people know what to expect.
In any event this update will definitely let me get to more serious testing.
Also worth noting, I did the upgrade by repeating the install steps. I noticed that on the copy partitions sideload it ends with an error after doing a lot of partitions fine, then ending with vendor(_b) "dd /dev/block/dm-2: write error: no space left on device". I think that may have happened on my initial install and I just ignored it, and it doesn't seem to matter (yet, afaict).
Ok, can you post a logcat while trying to play audio? Thanks
also, perhaps canceling what I said about in-call output levels, I discovered I'm only getting audio during calls with headphones(jack or usb) or when speakerphone is on. I.e. what I was interpreting as good in-call audio output level in non-speakerphone mode seems to really be a not very loud speakerphone mode output. And interesting to note that the default(?remembered?) setting after installing the rom is speakerphone-on. And to what I mentioned about the mic level, I tried a set of bluetooth earbuds with mic and left equivalent voicemails, and it was clear the bluetooth mic was at standard level, while the phone mic was quite low. That led me to want to try the same test with the default soundrecorder app, but curiously it seems unable to record from (this) bluetooth mic, getting input from the phone mic even when earbuds are connected. I noted the bt/dev settings have on/off for 'phone calls' and 'media audio'. Maybe it's just not supported by these earbuds/headset. I'll check 18.1 when I go back next. Though the mic level on the recorded audio there sounded acceptable compared to the low in-call voicemail test.
Also, is there any difference and a way to install the lineage-17.1-20210207-0753-ginna-25.zip. I'm testing with 0206-UNNOFFICIAL.
Not gonna lie, super excited about this! I never thought that this device would gain traction on XDA due to it being a very low budget device but boy am I glad it's getting some love.
I'm having some trouble here. I can flash Lineage no problem in TWRP the phone just won't boot. So then I try to follow the instructions exactly and get this...
So my moto e booted into Lineage unexpected (I didn't think it would). Nevertheless I'm going to share the command lines I followed since some suggest they failed and I find that strange since Lineage is thus far working.
V:\Everything Android\platform-tools>fastboot devices
ZY227J63CQ fastboot
V:\Everything Android\platform-tools>fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta_a' (8 KB) OKAY [ 0.001s]
Writing 'vbmeta_a' OKAY [ 0.016s]
Finished. Total time: 0.049s
V:\Everything Android\platform-tools>fastboot devices
ZY227J63CQ fastboot
V:\Everything Android\platform-tools>adb sideload copy-partitions.zip
serving: 'copy-partitions.zip' (~47%) adb: failed to read command: No error
V:\Everything Android\platform-tools>adb sideload lineage-17.1-20210206-UNOFFICIAL-ginna.zip
adb: sideload connection failed: closed
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: closed
V:\Everything Android\platform-tools>adb sideload lineage-17.1-20210206-UNOFFICIAL-ginna.zip
Total xfer: 1.00x
V:\Everything Android\platform-tools>fastboot devices
ZY227J63CQ fastboot
V:\Everything Android\platform-tools>fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta_a' (8 KB) OKAY [ 0.001s]
Writing 'vbmeta_a' OKAY [ 0.015s]
Finished. Total time: 0.023s
V:\Everything Android\platform-tools>
Also, about half the internal storage is apparently taken, I must've done something wrong in the flashing process?
Cyb3rSl4v3 said:
also, perhaps canceling what I said about in-call output levels, I discovered I'm only getting audio during calls with headphones(jack or usb) or when speakerphone is on. I.e. what I was interpreting as good in-call audio output level in non-speakerphone mode seems to really be a not very loud speakerphone mode output. And interesting to note that the default(?remembered?) setting after installing the rom is speakerphone-on. And to what I mentioned about the mic level, I tried a set of bluetooth earbuds with mic and left equivalent voicemails, and it was clear the bluetooth mic was at standard level, while the phone mic was quite low. That led me to want to try the same test with the default soundrecorder app, but curiously it seems unable to record from (this) bluetooth mic, getting input from the phone mic even when earbuds are connected. I noted the bt/dev settings have on/off for 'phone calls' and 'media audio'. Maybe it's just not supported by these earbuds/headset. I'll check 18.1 when I go back next. Though the mic level on the recorded audio there sounded acceptable compared to the low in-call voicemail test.
Also, is there any difference and a way to install the lineage-17.1-20210207-0753-ginna-25.zip. I'm testing with 0206-UNNOFFICIAL.
Click to expand...
Click to collapse
Also not getting audio from speakerphone, just headphones. I cannot comment on calls as I'm not using the device as a phone.
Lahpyrcopa said:
Also not getting audio from speakerphone, just headphones. I cannot comment on calls as I'm not using the device as a phone.
Click to expand...
Click to collapse
This morning my first recompile from source finally finished (took a solid couple days and an impressive swap storm on an 8G system (and cough 18G of swap used that I saw. perhaps mka -j 2 will help (default -j left 4 massive java processes running, metalava something or other)). I'll post more as I progress. I had to comment most of device/motorola/ginna/libshims/Android.mk to get it to compile. I was guess/expecting wifi tethering not to work, it seems to say no sim / phone service, though I had let my plan lapse.
But the cool thing is that I do now get speaker out. Another issue is that the recovery.img doesn't want to flash (preboot verification failed, I'll see if I can still reflash twrp next). And now that I've verified I can can compile moto-e-2020/17.1 (after having gotten moto-g-2015/17.1, with CPU_SSE42=false and JAVA_TOOL_OPTIONS=-Xmx6g, kept for e-2020), I'll go try 18.1 again to see if I can get it built without gapps (though I did recently renotice a /d/gapps app on f-droid). I had an issue with libllvm_android/LegalizeIntegerTypes there on my last attempt, but perhaps a fresh start (and reposync) will help me there as it did on 17.1 (which I'm quite optomistic I'll be happy enough with if need be soon enough).
also, I discovered that MotoBootLogoMaker from another xda thread does work (on linux/debian/mono to boot), and while I haven't tried replacing the untrusted/orange unlocked bootloader warning yet, I was able to extract that image with the tool, so I'm hopeful it can be replaced (perhaps excepting the small 'N/A' rendered font text which could perhaps be obscured by some whiter pixels in a custom logo/splash/background, or maybe the font/color is tweakable with that tool too).
Damn, it must take a very beefy machine to operate on android to take days to compile the system.
Well like I said before I only really need the headphone jack working for audio and that creepy message that Moto gives about having an unlocked phone that can't be trusted is absolutely hilarious . Look, I get it Motorola if you read this, you don't want to be liable for jack all nor do any of these even bigger empires. Just tone the scare tactics down a smidge so I can breathe!
To the developer, thanks for your effort. I thought that given the price of the device no one would bother with it.
clarifying a few points above-
- i had forgotten the twrp install step of via .zip (including magiskboot and ramdisk-recovery.cpio stuffs). I.e. I was just able to use the lineage171 recovery to install its build, but just not to install itself as twrp can (perhaps an a/b magisk thing, not sure maybe I saw that was a known thing until lineage adds that functionality? Perhaps I could reuse the twrp zip, or presumably better start building twrp from github now that I'm past the point of having a building lineage tree to use for that purpose)
- indeed MLBM can replace the orange bootloader unlocked splash/logo (which unlike moto-g-2015, is shown after a few milliseconds of the normal seperate logo image). But it doesn't look like there is a way (yet?) with MLBM to effect the 'N/A' text/font/color which remains (again, presumably obscurable if you put an area of white pixels over it on your custom replacement)
- my specific 17.1(and 18.1) build issue with device/motorola/ginna/libshims/Android.mk not-so-much-of-a-workaround-because-simdetection/calling-no-longer-works was a result of this-
"
FAILED: finishing build rules ...
Error: makefile error
Output:
ESC[1mdevice/motorola/ginna/libshims/Android.mk: ESC[31merror:ESC[0mESC[1m "libqsap_shim (SHARED_LIBRARIES android-arm64) missing libqsap_sdk (SHARED_LIBRARIES android-arm64)" ESC[0m
You can set ALLOW_MISSING_DEPENDENCIES=true in your environment if this is intentional, but that may defer real problems until later in the build.
ESC[1mdevice/motorola/ginna/libshims/Android.mk: ESC[31merror:ESC[0mESC[1m "libqsap_shim (SHARED_LIBRARIES android-arm) missing libqsap_sdk (SHARED_LIBRARIES android-arm)" ESC[0m
You can set ALLOW_MISSING_DEPENDENCIES=true in your environment if this is intentional, but that may defer real problems until later in the build.
ESC[1mbuild/make/core/main.mk:972: ESC[31merror: ESC[0mESC[1mexiting from previous errors.ESC[0m
"
At one point, still even earlier in noob mode, I guessed and tried treating (iirc) /vendor/{lib,lib64}/libqsap_sdk.so as perhaps missing device blobz, and/or went with ALLOW_MISSING_DEPENDENCIES=true. Maybe I'll try again now that I've otherwise got a successful build. I'm doing all this just using the 3 android_ repos from github.com/motoe7. Let me know if I should be using any of the other repos.
Cyb3rSl4v3 said:
I'm doing all this just using the 3 android_ repos from github.com/motoe7. Let me know if I should be using any of the other repos.
Click to expand...
Click to collapse
github.com/LineageOS/android_system_qcom seems to be the answer to my libshims/libqsap_sdk.so issue. I now have a build that at first glance at least is a good reproduction with the addition that speaker out now works for me. Still no in-call volume control. Though as I typed that I see that I seem to be getting crashes similar to what I first reported here but were fixed with the update build. I'll skim my logs a bit...
and seeing the recent git commits and motog7/17.1/nightlies thread (and my log) it seems I can live without MotoActions for the timebeing. I may try toggling some of the recentish audiofx things at some point to see if that gets the in-call volume control working. Also, /d/gapps seems to not apply without root, but I'll try building 18.1 again.
Is this ROM mostly functional? RE: Voice, data, sms? Is it Gapps free?
Just got this phone yesterday & want to start w/ an aged, working build before experimenting further. Open to other suggestions, just want to be free of Goog apps & framework...
Thanks to all who have taken the time to make this affordable phone tweekable.
googleverifysux said:
Is this ROM mostly functional? RE: Voice, data, sms? Is it Gapps free?
Just got this phone yesterday & want to start w/ an aged, working build before experimenting further. Open to other suggestions, just want to be free of Goog apps & framework...
Thanks to all who have taken the time to make this affordable phone tweekable.
Click to expand...
Click to collapse
From my experience it is 80% stable with certain glitches that occur.
I've tried flashing multiple different build of this ROM, and everything is working great, except when I try to flash GAPPS (anything besides pico) and I get an error about having no space on my /system partition.
When flashing PICO gapps, the installation finishes, but the OS fails to boot afterwards.
Any ideas? I've tried Lineage 17 and 18 now and can't get either to work.
googleverifysux said:
Is this ROM mostly functional? RE: Voice, data, sms? Is it Gapps free?
Just got this phone yesterday & want to start w/ an aged, working build before experimenting further. Open to other suggestions, just want to be free of Goog apps & framework...
Thanks to all who have taken the time to make this affordable phone tweekable.
Click to expand...
Click to collapse
It is gapps free, and everything is working on my Moto E. Can't get GAPPS to flash for the life of me though.
THIS IS OUTDATED
BOOTMOD - Root your Shield In 1 minute (2015, 2017, & 2019)
Hello Friends~! We now have a working method to achieve ROOT on STOCK Firmware! A script has been made that can boot your shield into the bootloader, erase the old boot, flash the new boot, and install your choice of Magisk apk for you. The...
forum.xda-developers.com
REPLACES THIS IF YOU WANT ANDROID OR USE THIS GUIDE
How To Install Lineage OS and Optionally, Build Lineage From Scratch
Hello Friends! Today I wanted to re-write a guide for installing Lineage OS on the 2019 Pro. This guide will be more to the point and have only the needed tools. The SOURCE for the Lineage zip shared in the download section below. [/SPOILER]...
forum.xda-developers.com
FOR LINEAGE
THIS GUIDE USES LINEAGE OS AS IT'S BASE, BC I HAD NO IDEA WHAT I WAS DOING WHEN I FIRST STARTED. I WENT THROUGH A LOT OF UNNECESSARY STEPS.
PLEASE USE ONE OF THE LINKS ABOVE FOR DOWNLOADING AND ROOTING LINEAGE OR ANDROID.
*Hi Friends!*
Today I want to show you how to root your Nvidia Shield, for development purposes, as well as for repairing a soft-bricked system.
Spoiler: DOWNLOAD SHIELDROOT
https://drive.google.com/file/d/13pnW5eiO70b4JIvmbgqNRMhI5g1YHlzG/view?usp=sharing
Spoiler: THE SETUP
Plug your usb hub into the port next to your hdmi.
Plug a usb-c cable into the other port.
You will need an Nvidia Controller, a USB Hub, Portable Drive.
As well as a mouse and controller or a usb 3.0 keyboard
Spoiler: GETTING TO THE BOOTLOADER
Unplug the power cord from the Shield, then reapply it.
Using your Nvidia Controller or USB 3.0 keyboard, hold A and B until the Bootloader shows.
Select Unlock the bootloader.
Select Factory Data Reset.
Hit Reboot and remove the power cord, then unplug the usb from PC.
Wait a few seconds then add the power cord to the Shield.
Leave the USBC unplugged from your PC.
Hold A and B to post back into the bootloader.
Spoiler: INSTALLING THE USB DRIVER
Open Device Manager on your PC.
Plug the USBC cable into your PC.
Right click on the new fastboot device and hit update driver.
Browse Manually to Shield Drivers.
Then hit, "let me pick from a list".
Select I have a Disk.
Then install the andriod.usb file.
Spoiler: FLASHING THE ROOTED IMAGES
In SHIELDROOT, Run OEMUnlock.
Unplug the USB-C From the PC and Reapply.
(Must do to fix broke fastboot after unlock)
Run ShieldRoot.
This will flash the NVIDIA Developer Rooted images.
This will also flash TWRP for us, to recovery as well as boot.
This purposely bricks the system to run TWRP on boot until we finish
Spoiler: FLASHING THE OS AND OPTIONAL GAPPS
Have Lineage and Gapps saved to a portable drive.
Plug the drive into your usb hub.
Select Install in TWRP and start with Lineage.
Do the same thing for GAPPS If you want to have your playstore. RECOMMENDED.
Unless you know what you're doing...
GAPPS Version is the mini TV build so it runs much smoother.
Spoiler: SIDELOADING THE ROOT
----edit, please Know I believe you don't need to do both steps,
-----i had a problem with the flash on either the apk or the zip
------so i just put them both in.
------ ALSO NOTE THERE ARE A MILLION WAYS TO GAIN ROOT WITHOUT
--------MAGISK, THIS WAS JUST THE EASIEST WAY TO PROVE CONCEPT
Go into Advanced on TWRP.
Select Sideload ADB.
Then run the SideloadRootApp.bat file.
Lastly SideloadRootManger.bat file.
Select Reboot system.
Setup your system how you please.
Spoiler: UNLOCK DEVELOPER OPTIONS
Go into settings.
Device preferences.
About.
Build, hit build 7 times.
Spoiler: SETTING UP ADB
Go into developer options.
Enable USB Debugging, all 4 options including Network debugging.
Take note of your IP address.
Right click AdbConnect.bat and select edit.
Add your IP address there.
Run AdbConnect and select *Allow* on the Shield.
Run AdbConnect again and you will be successfully connected.
You can then get Root Access in ADB by running AdbR00t.bat if you need it.
Otherwise you have full access to push files, read and write over system partitions, etc.
Spoiler: EASIEST WAY TO INSTALL APPS
- YouTube
Enjoy the videos and music you love, upload original content, and share it all with friends, family, and the world on YouTube.
www.youtube.com
HOW TO OPEN SHIELD FOLDER ON YOUR PC- BOOT INTO FASTBOOT AND RUN TWRP, WHEN TWRP IS OPEN, YOUR SHIELD WILL POST TO YOUR PC!!! THEN YOU CAN DRAG AND DROP FILES NO CODE!!!
Thank you to the community for always sharing their knowledge.
Love, Jen
Spoiler: REFERENCES <3
Youtube Vids:
FULL PLAYLIST: https://www.youtube.com/playlist?list=PLErzGEIjyUlyiOLVl4aWDYRW-CJd6yF-N
How To Root Andy MANUAL Windows Setup Andyroid 0.45.5.0 LATEST
Safely Backup and Restore FULL ROM using TWRP Recovery (4K)
How to fix "Zip Treble compatibility error!" Invalid zip file format! in TWRP custom recovery
Linux File System/Structure Explained!
Linux System Administration Full Course
Easily Run Linux On Android With AndroNix - Linux Distro on Android without root
New Way to turn you PC into an Android TV Box with FydeOS - Bye Bye Android X86
Nvidia Shield TV Pro 2015 SSD Swap out + Regrease The APU!
Android multi-boot demo
Nvidia Shield Pro unlocked bootload, twrp and more
How to Download & Install GApps and Magisk on LineageOS 18.1 with LOS Recovery
Nvidia shield TV users MUST watch - 10 Hidden features you did not know existed
LineageOS Custom Rom on Shield Android TV (2015)
Nvidia Shield TV Pro (2021)｜Watch Before You Buy
Recovery OS Nvidia Shield TV installation
[HOW-TO] Install Full Android Nougat on Nvidia Shield TV 2015 - TWRP - ROOT [Bye Bye Android TV]
https://www.youtube.com/watch?v=LQaYb4oVHVc&list=PLErzGEIjyUlyiOLVl4aWDYRW-CJd6yF-N&index=16
Nvidia Shield TV Pro 2019 Boot Loop Repair (Recovery Image)
https://www.youtube.com/watch?v=qc4m2Hfd4HY&list=PLErzGEIjyUlyiOLVl4aWDYRW-CJd6yF-N&index=18
HOW TO ROOT NVIDIA SHIELD 16GB ON OREO UPDATE
https://www.youtube.com/watch?v=x893ajy9YVo&list=PLErzGEIjyUlyiOLVl4aWDYRW-CJd6yF-N&index=19
Website Links:
Install Wolf Launcher on Firestick/Android and Remove Ads (2022)
This step-by-step guide will show you how to install the Wolf Launcher on Firestick, Fire TV, or Android TV Box to upgrade your interface. Wolf Launcher
troypoint.com
Download Android Studio & App Tools - Android Developers
Android Studio provides app builders with an integrated development environment (IDE) optimized for Android apps. Download Android Studio today.
developer.android.com
TeamWin - TWRP
This is the Team Win website and the official home of TWRP! Here you will find the list of officially supported devices and instructions for installing TWRP on those devices.
twrp.me
Explorer - Apps on Google Play
Fast, lightweight and easy to use file manager.
play.google.com
SHIELD Developer OS Images
As a service to developers, NVIDIA makes "beta", "rooted" and "early access" versions of certain SHIELD system images available for download. These packages are for software developers only and may provide: root level access by default; non-certified preview graphics drivers; beta system device...
developer.nvidia.com
Download Magisk Manager Latest Version 26.1 For Android 2023
Magisk Manager is an app which helps users to root their phone. With the help of Magisk you can run banking apps and also pass SafetyNet tests.
magiskmanager.com
LineageOS Downloads
download.lineageos.org
The Open GApps Project
OpenGApps.org offers information and pre-built packages of The Open GApps Project. The Open GApps Project is an open-source effort to script the automatic generation of up-to-date Google Apps packages. All Android versions and platforms supported.
opengapps.org
https://www.reddit.com/r/xdacirclej...to_use_a_mouse_and_keyboard_on_stadia_google/
ADB : unable to connect to 192.168.1.10:5555
I cannot use adb connect to connect via WiFi to my device (Nexus 5, Android 6), but since I'm developing a cordova plugin using USB OTG, I really need to connect via WiFi. I tried to adb kill-serve...
stackoverflow.com
https://www.reddit.com/r/AndroidTV/comments/jnxlmw/guidenatively_use_custom_launcher_on_chromecast/
[HOW-TO] [PICTURES] ADB Working On the Google Chromecast
Hey everyone, I got the Android Debugging Bridge (ADB) working on the Google Chromecast. A video is currently uploading. A how-to will follow shortly after. Videos have been uploaded! Thanks! Part 1...
forum.xda-developers.com
How to Root and install Magisk on NSTV 2019 Pro v8.2.0
Can I flash these mdarcy.dtb.img and vbmeta_skip.img from on an updated 8.2.1 SHIELD?
forum.xda-developers.com
How to skip(bypass) Google sign-in NSTV Pro 2019 with any firmware versions!
Let me share my working build.prop file with you. Make sure the permission of this file is proper too. Hey buddy.. I have not had time until now to try this again.. My shield has been semi-bricked since last try and have not been able to use...
forum.xda-developers.com
[GUIDE] 8.2.3 + Magisk root + MagiskHide + TWRP
Based on the work done in https://forum.xda-developers.com/t/how-to-root-and-install-magisk-on-nstv-2019-pro-v8-2-0.4189567/ User friendly guide written for Windows. Bash script for Linux flashing edited as well, but guide is focused on Windows...
forum.xda-developers.com
For anyone who downloaded the toolset early, the 1.5 gb version, my apologies, the full file hadn't downloaded. The correct google drive link is now listed. It is 3 gb in total
I'm still studying everything android, apk, linux, etc. I thought about cracking big name emulators last night, like "Nox, andy. bluestacks" with custom OS full Root, etc, but then it occurred to me what these programs actually are, and it's so simple.
It's just like building androidx86 in a virtual machine, except the programs I mentioned, figured out how to manipulate the machines within the virtual environment, doing their best to shut sudo down, and Sold Out to Corporations, uploading $hitware, on top of their independent, emulated kernels.
So I thought "Why not install a headless (just terminal, no gui at boot version) linux" and then construct the android emulator from scratch?" Well I started researching more based off that train of thought, which emulators work on linux and I learned about the most Special One. https://anbox.io/#collapse2
The logic Is flawless, beautiful, brilliant, but not unique! Thankfully for me, as I am a female that prefers Windows, in a world ran by men that love Linux <3 no Hate. I understand. It is akin to apple vs android, but I digress. I was initially going to install a virtual machine with ubuntu to test out anbox, which I absolutely am going to do, as well as I plan to do everything in my power to get it to work on the shield, muahahhaa, butttttt.....
For Us Windows Users.... THERE IS AN AMAZING NEW DEVELOPMENT WITH WIN 11. I must investigate further, I'm updating my OS now... and hopefully in a few days I can prove my current theory, and share with you guys something Truly Magical in the World of Android, for both Windows and Linux Users. EMULATORS, BEWARE..... MUAHAHAHHAHA. <3 NOOBSTACKS RIP
Thread has been updated with an alternative download site, MEGA. It seems some folks were experiencing an error on Google drive due to the tools being downloaded too quickly.. Never had this happen before, so my apologies. https://mega.nz/file/oypjQChD#wjSfCChkLN6uLQtiEtHrnGbevCsU7pW7KODb9sEqzOQ
Hi jen, sorry i cannot reply on your youtube comment. Not sure the reason. https://www.google.com/amp/s/m.apkp...ating-widget/com.spencerstudios.ramlogger/amp here the link to download the ram monitor and install from usb drive. Will wait for the result.Thank you.
mkhainizam said:
Hi jen, sorry i cannot reply on your youtube comment. Not sure the reason. https://www.google.com/amp/s/m.apkp...ating-widget/com.spencerstudios.ramlogger/amp here the link to download the ram monitor and install from usb drive. Will wait for the result.Thank you.
Click to expand...
Click to collapse
Perfect ty hun I will look at it here shortly, I promise!
mkhainizam said:
Hi jen, sorry i cannot reply on your youtube comment. Not sure the reason. https://www.google.com/amp/s/m.apkp...ating-widget/com.spencerstudios.ramlogger/amp here the link to download the ram monitor and install from usb drive. Will wait for the result.Thank you.
Click to expand...
Click to collapse
Level up your Knowledge from this guide. See How It All Comes Together In Windows 11, Subscribe for more guides, tools, and virtual machine images! https://forum.xda-developers.com/t/root-windows-11-hard-mode.4371611/
Guys we are getting so close! https://renegade-project.org/#/en/edk2/Overview
Does anyone know these folks? If I'm reading correctly they are programming a custom bootloader or a recovery image that currently allows certain cpus to run win 11 arm. Is this akin to an arm translation tool like on genymotion or can Anyone help explain this to me better. I'll reread it several more times and research more. Just dropping bread crumbs for deh pidgeons....
He uses a lot of jargon I'm trying to familiarize myself with https://www.kernel.org/doc/html/latest/arm64/acpi_object_usage.html
*ALSO A KNOWLEDGE BOMB*
anyone else who finds themselves on this Journey... I stepped on my shield and in doing so it bent the usb on for my nvidia controller. It also somehow shorted out the system. Lol. Anywho, In doing so, I tried to replace the usb cable with a crappy one I just had lying around and it did not work. I found a newer usb cable and it triggered the controller, so I theorized that since the ports are USB 3.0 or 3.1, not sure, the bootloader will only post with a usb 3.0+ Device. So in theory, any keyboard or controller usb 3.0 should work by holding a + b down
more knowledge.......
How to enable UEFI and Secure Boot for Windows 11?
The UEFI BIOS Mode and the enabled Secure Boot State are minimum requirements for Windows 11 support. Change the Legacy BIOS Mode to UEFI, convert the partition type to GPT, and turn on the Secure Boot State.
easywebfixes.com
Let's keep diving deeeeeperrrr
I'm starting to understand....
What’s the Difference Between GPT and MBR When Partitioning a Drive?
Set up a new disk on Windows 10 or 8.1 and you’ll be asked whether you want to use MBR (Master Boot Record) or GPT (GUID Partition Table). Today we’re explaining the difference between GPT and MBR and helping you choose the right one for your PC or Mac.
www.howtogeek.com
The Best Thing Ive read in 7 years
[CLOSED]HaHaHack Dis: No Magisk REQUIRED!!!!
Magisk is no more... I present a new fool proof method of flashing su to Android 10_Q and above!! I ranted and ranted about variant=user/user-debug/eng builds that I got no-where... people thinkin am dissin john wu, nah, I respect what I've...
forum.xda-developers.com
I think I'm Really starting to understand, that conversation was sosososo Enlightening
Hello.
Here is where I am at in "thinking outside the box".
So instead of trying to flash windows or ubuntu directly onto the nvidia's system partition, why not flash it to a portable drive?
So I am researching UEFI, Bootloaders, flashing, and volumes, particularly how they store and load data.
So I understand that windows requires it's hard disk to be formated to GPT.
My USB stick is MBR. I have a partioning software that can change the USB to GPT.
If anyone understands what I am talking about, can you reach out? I know this is possible, I know the answer is out there,
IT IS JUST ALL THIS JARGON SOME OF YALL USE <3 GOD LOVE YOU ITS HARD TO UNDERSTAND
AND WHAT IM TALKING ABOUT IS DUAL BOOT FOLKS!!! LEGIT DUAL BOOT, NO SECOND PC REQUIRED
AN OS FOR FUN , AND AN OS FOR WORK.....
CAN YOU IMAGINE
KNOWLEDGE BOMBS
ShieldTV/AddPartition.md at master · na6an/ShieldTV
Projects on Nvidia's Shield TV. Contribute to na6an/ShieldTV development by creating an account on GitHub.
github.com
""Nvidia uses its own proprietary disk structure on its devices, which look like a modification of GUID partition table(GPT) with protective MBR. Most disk partitioning softwares are unable to read Shield TV's partitions because its primary header is overwritten with non-standard GPT format.
Here are list of disk paritioning software I tried and couldn't even read the disk at all: fdisk, GParted, KDE Partition manager, diskpart and Disk Management on windows. Of course, you may format the disk and rebuild partitions, but then it won't boot from Shield TV at all.
There are two softwares can read partially:
GNOME Disks - the default partition software for Ubuntu, however, could read the partitions IF you boot L4T from Shield TV. It won't work if you try from another computer. Also, it is still unable to modify partitions.
gdisk (GPT fdisk) - gdisk can read partition 2~33 from backup header. As you can see, 33rd partition is the one that holds most of 500GB storage. (462.5 GiB out of 465.66 GiB)""""
END QUOTE FROM ARTICLE
A gdisk Walkthrough
What we need to do is GET A NEW BOOTLOADER! Idk how but I will find out! If you know how reach out pl0x
I'm just going to keep dumping knowledge bombs until I or someone elsse figures this out!
How A/B Partitions and Seamless Updates Affect Custom Development on XDA
You may have heard of Seamless Updates before. It involves something called "A/B partitions." What is it and how does it affect custom development on XDA?
www.xda-developers.com
system – holds the Android OS, system libraries, system apps, and other system media like bootanimations, stock wallpapers, ringtones, etc.
boot – holds the kernel, ramdisk, and on A/B devices also the recovery as well
recovery – holds the recovery, where TWRP is most commonly flashed on A-only devices (A/B devices don’t have a dedicated recovery partition)
userdata – holds all of your app, system, and internal storage data
vendor – holds platform and device-specific HALs, the files necessary for the Android OS to communicate with the underlying hardware
vbmeta – the partition for Android Verified Boot 2.0 which verifies the integrity of the boot process
gdisk(8) - Linux man page
The gdisk program employs a user interface similar to that of Linux's fdisk, but gdisk modifies GPT partitions. It also has the capability of transforming ...
linux.die.net
Going to play with this toy:
GPT fdisk
Download GPT fdisk for free. GPT fdisk is a disk partitioning tool loosely modeled on Linux fdisk, but used for modifying GUID Partition Table (GPT) disks. The related FixParts utility fixes some common problems on Master Boot Record (MBR) disks.
sourceforge.net
Cause GDISK is for LINUX and I don't like using Linux. No hate but GUI will win over MBR, Mah nerds. Cause GUI IS CMD!! GUI Is Just Easier For Some People! Different Strokes, for Different Folks!
"Upon start, gdisk attempts to identify the partition type in use on the disk. If it finds valid GPT data, gdisk will use it. "
"gdisk" or whatever bootloader you are playing with...
So my only question is how do I make the WIN 11 Arm version bootable... ?? On the USB ?
WAITING ON MY USB DRIVE TO WIPE UGH. '
GNU GRUB - GNU Project - Free Software Foundation (FSF)
Site for GNU GRUB
www.gnu.org
Android Verified Boot 2.0
Hi friends I don't sell anything I only teach but I wanted to share with you guys that don't already own a shield or want to purchase one for a gift that they are on sale at Newegg
https://www.reddit.com/r/buildapcsales/comments/rfdi26
Thanks for your work, very well explained guide. I only have one question, if i root my device, could lose some function like dolby vision/atmos?
locust10000 said:
Thanks for your work, very well explained guide. I only have one question, if i root my device, could lose some function like dolby vision/atmos?
Click to expand...
Click to collapse
All the apps that originally worked, will still work. However, since this process involves flashing a new operating system, lineage, as opposed to the base, stock, operating system, android, you may have to reinstall your favorite apps like dolby
---There are many ways to flash your favorite apps, perhaps the easiest being a program called "send files to tv" you can install that on your phone and tv, then DL the app you want to send to the tv, like dolby, and within SFTTV, You can easily send the app.
You can also use my tools in the shieldrooot but SFTTV is a lot simpler for beginners
Hello,
I am trying to figure out how to either inject a custom bootloader like Clover onto my Nvidia Shield, or to Modify the existing EFI bootloader itself or with a modification to a Recovery program such as TWRP in order to be able to use a custom bootloader to select "Boot From Usb"
I figure I oughta make a backup, but I do not know how to backup my bootloader either....
I think I understand how to look at the shield's partitions now to find the one with the bootloader, I'm just nervous to proceed...
I have been researching for a week and have learned amazing tidbits of knowledge on the sublayers of the shield, and a lot of its partitions...
I was able to install a custom OS, modified GAPPS, and root on my shield, I am just hung up on this final part....
If anyone who understands this would care to share even a bread crumb where to start, I Would Be Ever So Grateful
Download Clover EFI Bootloader - MajorGeeks
Clover EFI Bootloader can boot OS X, Windows, and Linux on Mac or PC with UEFI or BIOS firmware.
www.majorgeeks.com
Hi @jenneh I know you're in the middle of a different train of thought, but since you are one of the most active members recently, I was hoping I could reach out for your help on two really important issues I'm having. I don't think that anyone has been able to get AI Upscaling to function after rooting, and it's one of my favorite features of the device. If you ever have time and are in the mood to crack this nut, I'd be both incredibly grateful and also willing to send like $30 your way.
On that note, I am also having a hell of a time trying to get the AdGuard CA certificate installed. I have tried every method I could find, but none of them seem to be compatible methods for this device. I will both send you an AdGuard lifetime license, and another $30 for this bounty. Any help at all would be greatly appreciated! (Oh, and if you're interested in attempting these feats, please DM me. I'll reply with the AdGuard license in advance.)
One final important note: My device is running the new 9.0.0 update.
Even the new update 9.0.0 AI Upscaling not working after rooting...NSTV 2019 Pro
I tested but same problem Demo mode work only Enhanced Mode
Here's where I'm at now! I am in the Kernel! Not through ADB But instead On the shield Using Root Explorer to learn all of the shield's directories to find out where the hell the EFI drivers are to inject my new bootloader. I see many options pertaining to the upscaling that I can modify but I haven't got the slightest, what it is yall are trying to do. If someone can explain it better we can totally solve this.
----i'm a little weirdo and i have been dreaming about this,, or rather, dreaming in Operating Systems for Months Now~
ODM Partitions | Android Open Source Project
source.android.com
A NEW WAY TO PUSH APP~z!1!
HOW TO OPEN SHIELD FOLDER ON YOUR PC- BOOT INTO FASTBOOT AND RUN TWRP, WHEN TWRP IS OPEN, YOUR SHIELD WILL POST TO YOUR PC!!! THEN YOU CAN DRAG AND DROP FILES NO CODE!!!
---WHERE I'M AT TODAY!
Learning about BUSYBOX~!
Come along for the ride!
"
"boot.img contains the kernel and ramdisk, critical files necessary to load the device before the filesystem can be mounted. You have to generate the boot.img yourself using mkbootimg, a tool provided by AOSP. "
What is boot.img file in android?
I am building the android source code and getting new system.img . I try to flash the new system.img on a device and I see that I need another file called boot.img. What is this file ? what is used...
stackoverflow.com
To Do List:
Will be reuploading the shieldroot tools with wipe all partitions code, updated lineage, etc, as well as including options for folks on other versions of the nvidia shield, all with ammended code. This will take some time to upload / craft, but I will let y'all know when it's done.
Please note, there is nothing wrong with the current shield tools, I am just making them Better! Peace and love
This set me off track for about an hour, if anyone has any ideas https://forum.xda-developers.com/t/a-strange-fastboot-problem.4380579/