Introduction:
This is a list of all known OTA's for the Nexus Player
Click to expand...
Click to collapse
File List:
LRX21M → LRX21V
LTW87L → LRX21V
See ASUS Nexus Player # Official ROMs - XDA Wiki for a list of files
Click to expand...
Click to collapse
How to flash:
Requirements:
Stock recovery
Unmodified /system
Unmodified /oem
Unlocked bootloader
Basic understanding of command line/shell
Unlock your bootloader
Download and set up adb and fastboot
Reboot into fastboot mode
Open up a command prompt/shell where you saved fastboot
enter into command prompt/shell: "fastboot oem unlock"
Enter recovery mode via onscreen buttons
Enable recovery ui
(How do you do this for this device?)
Set up adb
Select apply update from adb
enter into command prompt: "adb sideload <path to saved update.zip>
Click to expand...
Click to collapse
FAQ:
How to find the ota?
If you're rooted, wait for the device to prompt you to update, then check /cache for the file
If you're not rooted, wait until the same time and do an adb logcat and look for a line with .zip in it
Why isn't the latest ota listed?
We can only list what we have, if the ota from Build X to Build Y isn't listed, we dont have the file for it yet.
How do you setup adb/fastboot
Please read the stickies in the general subforum, this is not a formal guide
Do I need to unlock the bootloader to flash the update zip?
Yes, if you wish to do it manually.
If you allow android to prompt for the update, you do not need to unlock
Can I flash this if I have a custom rom?
No, you must be on a unmodified rom
Can I flash this if I'm rooted?
No, rooting modifies /system.
Click to expand...
Click to collapse
Credits:
Click to expand...
Click to collapse
Changelog:
Nov 29, 2014: Added LRX21V
Nov 18, 2014: Added LTW87L → LRX21M
Oct 15, 2014: Initial page
Click to expand...
Click to collapse
2char
Can Nexus Player images be loaded and bootted on a similarly specced Intel Atom based PC?
kettal said:
Can Nexus Player images be loaded and bootted on a similarly specced Intel Atom based PC?
Click to expand...
Click to collapse
It's too soon to tell and it depends on what the bootloader allows for it.
Just because goog might include one that isnt locked down, it doesnt mean it's automatically bios or uefi complient.
Loading linux on it is one thing, but expecting it to work like a normal pc with linux or even windows isnt something you can assume.
Goog's bootloaders are not all universally uefi complient even though other similar devices include them (winrt/wp8/assorted android devices have complient bootloaders)
Also, this is off topic for this thread.
https://groups.google.com/forum/?hl=en&nomobile=true#!topic/android-building/bm3iwCrjO2s said:
Hi all,
Builds for Android 5.0 have been released.
The following are the builds, tags, and devices supported:
- LRX21M, android-5.0.0_r2, Nexus Player fugu
- LRX21L, android-5.0.0_r1, Nexus 9 volantis
Additional devices support are coming soon.
Thanks!
bill
Click to expand...
Click to collapse
The NP will also have an ota before release.
Factory image posted:
https://developers.google.com/android/nexus/images#fugu
Version: 5.0 (LRX21M)
Download: Link
MD5 Checksum: b5380180959cdf8b99a24339b4800b64
SHA-1 Checksum: aeed3bef8331aba50c94c188ce3753d3ae9afd83
TheManii said:
The NP will also have an ota before release.
Click to expand...
Click to collapse
There is an ota from LTW87L → LRX21M, I do not have the ota yet.
Also: the NP is unlockable without having to go to setting first, unlike the N6/N9: PSA: OEM Unlock On The Nexus 6 And 9 Requires Checking A Box In Developer Options
Update: PSA: New Lollipop OTA Procedure On Nexus Devices Means Your Update Will Fail If Your System Is Modified In Any Way At All
For future otas, rooting will not break your ability to ota (rooting itself wont, if you modify files you will still break ota due to that)
The NP's kernel does not have dm-verity / secure /system enabled, and it must be enabled prior to the first OTA to stay consistant. (technical note, it's still possible to deploy consistant/secure /systems without it, but the kernel itself wont bother checking, so it's unlikely an issue at all)
Goog can still deploy it after the fact, but it would require a full rom ota instead of merely a delta/patch ota, this is highly unlikely to happen.
This will be reconfirmed once I have the file and url for the first ota.
Edit: see below
Update: LTW87L → LRX21M
The NP does use secure /system otas, ROOTING WILL BREAK OTAS.
If you are rooted or have modified your /system in any way, you will need to use factory images to update
LTW87L → LRX21V
LRX21M → LRX21V
URL for the 5.1.1 OTA
http://android.clients.google.com/p...6.signed-fugu-LMY47V-from-LMY47D.99b5efed.zip
MPZ44Q to MPZ79N OTA zip
Here is the zip for upgrading the first Android M preview to the Dev preview
Sorry for sort-of breaking the rules. Links are in the attached text file.
doesn't sound like this ota url thread is really being maintained anymore, but anyways....Nov security patch:
https://android.googleapis.com/pack...d2918bc567.signed-fugu-MRA58N-from-MRA58K.zip
Sourced from jduck:
https://android.googleapis.com/pack...5af.signed-signed-fugu-MMB29U-from-MMB29T.zip
MMB29U-from-MMB29T
MMB29V-from-MMB29U
Code:
https://android.googleapis.com/packages/ota/google_fugu_fugu/8793bbdb81c005f5cb0f2a224b20e03365e0a974.signed-fugu-MMB29V-from-MMB29U.zip
MOB30D from MMB29V
https://android.googleapis.com/pack...afd.signed-signed-fugu-MOB30D-from-MMB29V.zip
MOB30W from MOB30P
https://android.googleapis.com/pack.../0825452c453e9fa32a2988c6fce122c530e8654d.zip
by Jduck
Related
Recovery BootStrap (TWRP) - Motorola Defy\Bravo
Version: 4.0
Install Recovery BootStrap (TWRP) for Motorola Defy\Bravo via a USB cable. For computers running the Windows\Linux (port version) operating system.
Download: (Windows: MEGA / Google Drive) | (Linux: port by nastys post>>)
Install Recovery BootStrap (TWRP) you can right out stock firmware (without custom recovery) with superuser.
Recovery BootStrap (TWRP) - for the recovery say thank Quarx, after installation, you can install the rom CyanogenMod from Quarx for December 2014 (but do not forget about resize.zip).
Can be installed on Defy (MB525), Defy Plus (MB526), Bravo (MB520).
Requirements for smartphone:
Enable USB debugging
Superuser (ROOT)
Free space on the memory card of 100 megabytes
Instructions:
1. Download the archive
2. Unpack it somewhere else with a short path, for example D:\andro
3. Connect your phone via USB cable ("debugging on USB" should be included)
4. Run the install_bootstrap.cmd
5. When you see the label "Let's Start? =)", press any key
6. If the superuser ask permission for full access "ADB Shell", allow.
7. After installing the smart phone will automatically restart
!IMPORTANT! after restarting the Stock firmware will not start!, but you will have BootStrap (TWRP) so you can safely install custom firmware\rom
Change log:
V3:
Changed how the script
Fixed installation errors recovery on Android 4.x and later
V4:
The script changed drastically
After installation removes trash from the memory card (so far only on Android 4.x and later)
Made for normal (mortals) users , before you start the installation script checks (by model) which smartphone connected to the computer, if your smartphone is not supported script report it and stop installation, if supported will give something "Device: MB525".
Serviceability checked on the Chinese 231 (Defy) firmware with superuser (what say thank borndead), and on the Asian 231 (Defy)
Questions\FAQ:
Error "[ERROR] Verify device!", what to do?
Error "[ERROR] Verify device!", it is may mean the following:
1. You have not enabled USB debugging
2. Your smartphone does not support this Recovery. (only for MB525, MB526, MB520)
3. You need to confirm the action ADB on your smartphone
4. Or you have some other connection problems
Stock transition to CyanogenMod 11 of Quarx
Stock transition to CyanogenMod 11 (firmware and find all necessary files can be here) of Quarx in short (generally as described on the website Quarx, only simpler and under Windows)
1. Install Recovery BootStrap (TWRP) via USB
2. Enter Recovery install resize.zip
3. Restart your smartphone
4. Install CyanogenMod 11 and GApps
Good work, comrade! I flashed CM11 on the Moto Defy - everything works!
We did observed some cases, where a "new life (resized)" Defy is not booting anymore. Only solution was to reflash SBF and start from scratch.
Does this mean, it is possible to recover TWRP from PC? That would be a step a head!
This is amazing! Everytime I needed to reflash the stock ROM I needed to install cm10, then cm11, then new bootsrap etc...
Unfortunately I don't use Windows...
@Octanium91 Would you mind if I port your script to GNU/Linux?
starbright_ said:
We did observed some cases, where a "new life (resized)" Defy is not booting anymore. Only solution was to reflash SBF and start from scratch.
Does this mean, it is possible to recover TWRP from PC? That would be a step a head!
Click to expand...
Click to collapse
I tried to do something like that, is not yet happened. Perhaps in the future even try
nastys said:
This is amazing! Everytime I needed to reflash the stock ROM I needed to install cm10, then cm11, then new bootsrap etc...
Unfortunately I don't use Windows...
@Octanium91 Would you mind if I port your script to GNU/Linux?
Click to expand...
Click to collapse
Maybe. If Iunderstand with GNU/Linux scripts
The new version, V4
The new version, V4
Changes:
The script changed drastically
After installation removes trash from the memory card (so far only on Android 4.x and higher)
More debugging: Now the script itself is not closed, and tells the user exactly what happened.
Sorry debris removal only works on Android 4.x and later.
Linux port done!
@Octanium91 I ported it to C++ (for Linux only at the moment). Please add it to the first post . Here is the link: MediaFire | MEGA
On Ubuntu just mount the ISO as image (not archive) then click 'Run' (or you can also extract the ISO and run the executable directly). It works on x86 (32 bit) and x86_64 (64 bit) CPUs. The source code is also included in the ISO. Tested on Ubuntu 14.10 and 16.04 (64 bit).
I tested it with both stock 2.3.6 rooted and CM11. It seems that the stock ROM won't boot after flashing the new bootstrap, but the recovery works fine
Also your version has a very bad bug: it flashes Defy bootstrap even on Bravo!!! It should flash Motorola Bravo specific bootstrap instead. My version only works for Motorola Defy and Defy+ at the moment, but you can edit the source code. EDIT: they are the same file with different names. I updated my version to support MB520.
After run the command script, when i boot in TWRP SDcard shows 0mb.
Already tried flashing the SBF recommended by quarx and after that the root SBF, but the result is always the same.
With CM recovery i can see the SDcard properly, but after the resize, or bootstrap, i always get 0mb at SDcard.
Any help?
Thanks!
evilinheaven said:
After run the command script, when i boot in TWRP SDcard shows 0mb.
Already tried flashing the SBF recommended by quarx and after that the root SBF, but the result is always the same.
With CM recovery i can see the SDcard properly, but after the resize, or bootstrap, i always get 0mb at SDcard.
Any help?
Thanks!
Click to expand...
Click to collapse
Format your SD card (to FAT32) or use another one.
Octanium91 said:
The new version, V4
Changes:
The script changed drastically
After installation removes trash from the memory card (so far only on Android 4.x and higher)
More debugging: Now the script itself is not closed, and tells the user exactly what happened.
Sorry debris removal only works on Android 4.x and later.
Click to expand...
Click to collapse
nastys said:
@Octanium91 I ported it to C++ (for Linux only at the moment). Please add it to the first post . Here is the link: https://www.mediafire.com/folder/candnhxj8aovj/Defy_Bootstrap_Installer_for_Linux
On Ubuntu just mount the ISO as image (not archive) then click 'Run'. It works on x86 (32 bit) and x86_64 (64 bit) CPUs. The source code is also included. Tested on 14.10 x86_64.
I tested it with both stock 2.3.6 rooted and CM11. It seems that the stock ROM won't boot after flashing the new bootstrap, but the recovery works fine
Also your version has a very bad bug: it flashes Defy bootstrap even on Bravo!!! It should flash Motorola Bravo specific bootstrap instead. My version only works for Motorola Defy and Defy+ at the moment, but you can edit the source code.
Click to expand...
Click to collapse
Greetings guys, I'm a user from the Atrix 2 section and a part of the current device supporters there. It's a pleasure to finally post here, 'the domain of Quarx' haha.
I was wondering if this recovery is able to flash and boot android Lollipop 5.0 roms yet? If so, then is there some way to port it from source to my or other similar Moto devices in the OMAP bracket with locked bootloaders?
I'm an Android novice, but I'm experienced in building custom recoveries and roms, as well as beginner git commands, so no need to hold anything back, lol. I appreciate the work you're all doing here, please continue to make the difference. Thanks for reading this and take care!
answer
Aceofzeroz said:
Greetings guys, I'm a user from the Atrix 2 section and a part of the current device supporters there. It's a pleasure to finally post here, 'the domain of Quarx' haha.
I was wondering if this recovery is able to flash and boot android Lollipop 5.0 roms yet? If so, then is there some way to port it from source to my or other similar Moto devices in the OMAP bracket with locked bootloaders?
I'm an Android novice, but I'm experienced in building custom recoveries and roms, as well as beginner git commands, so no need to hold anything back, lol. I appreciate the work you're all doing here, please continue to make the difference. Thanks for reading this and take care!
Click to expand...
Click to collapse
Hi!
flash and boot android Lollipop 5.0 roms - just can not say, but it is theoretically possible (need to check).
If so, then is there some way to port it from source to my or other similar Moto device - No, this is not possible (specifically, in this case). BUT this method you can set recovery to another smartphone (it is theoretically, need to try)
Here recovery that are in the public domain, I think that they can install Lollipop 5.0 roms - TWRP2 \ Safestrap
Moto devices in the OMAP bracket with locked bootloaders? - Most likely will not work, but no one stops to try
Octanium91 said:
Hi!
flash and boot android Lollipop 5.0 roms - just can not say, but it is theoretically possible (need to check).
If so, then is there some way to port it from source to my or other similar Moto device - No, this is not possible (specifically, in this case). BUT this method you can set recovery to another smartphone (it is theoretically, need to try)
Here recovery that are in the public domain, I think that they can install Lollipop 5.0 roms - TWRP2 \ Safestrap
Moto devices in the OMAP bracket with locked bootloaders? - Most likely will not work, but no one stops to try
Click to expand...
Click to collapse
Many thanks for the prompt and well ordered reply! I'll look into your suggestions and I'm aware that there aren't many available recovery software for our locked bootloader phones.
We were actually trying to get Safestrap working on our device since last month, but it's failing to work correctly in booting our kexec roms. So I thought I'd ask here since the Defy works by using the 2nd boot like us, but it's still under investigation. Thanks again for your assistance, we're not out of the game yet and we'll get things rolling eventually. Take care!:thumbup:
Sent from the Ace's MB865 using Tapatalk
Error. More than one device and emulator
what am i doing wrong?
LoeWn said:
Error. More than one device and emulator
what am i doing wrong?
Click to expand...
Click to collapse
Perhaps you have not enabled USB debugging
Requirements for smartphone:
Enable USB debugging
Superuser (ROOT)
Free space on the memory card of 100 megabytes
I did enable usb debugging
LoeWn said:
I did enable usb debugging
Click to expand...
Click to collapse
You can send us a screenshot?
I had a successful installation of a december build and twrp 2,6x installed, everything ran just fine. But when the CM tells me there is a update and i download it does not install from recovery, get errormsg. Also apps like rom manager pro tells my phone is not compatible with any updates, and that i should install CWM recovery. So is it possible to install a real CWM on a defy mb526?
Hi, I flashed Recovery BootStrap v4 on the Defy MB525, but its not working. After flash and reboot, phone starts booting, but it ends up with the following screen.
Doesn't matter if I choose Recovery or continue. I can press the menu button (to choose recovery) and nothing happen, till the 3rd press. Than display goes black and thats all .
Any idea where could be the problem or what I'm doing wrong?
Edit: maybe its related to the bootloader version, which is 09.10
Haldy said:
Hi, I flashed Recovery BootStrap v4 on the Defy MB525, but its not working. After flash and reboot, phone starts booting, but it ends up with the following screen.
Doesn't matter if I choose Recovery or continue. I can press the menu button (to choose recovery) and nothing happen, till the 3rd press. Than display goes black and thats all .
Any idea where could be the problem or what I'm doing wrong?
Edit: maybe its related to the bootloader version, which is 09.10
Click to expand...
Click to collapse
Based on first screenshots, Recovery installed. Now you need to install system.
Than display goes black and thats all - maybe have to wait
marcooleo said:
I had a successful installation of a december build and twrp 2,6x installed, everything ran just fine. But when the CM tells me there is a update and i download it does not install from recovery, get errormsg. Also apps like rom manager pro tells my phone is not compatible with any updates, and that i should install CWM recovery. So is it possible to install a real CWM on a defy mb526?
Click to expand...
Click to collapse
In principle it is possible, but it does not make sense.
Code:
/*
* Your data will be lost! Backup before doing this.
* You'll still get OTA updates.
*/
Prerequisites
December 2017 OTA - Download links: TA-1021, TA-1025, TA-1033, TA-1039
OST LA - Download link
China variant's Firmware - Download D1C-562F-0-00CN-B01_Exploit.7z from here
Step 1:
Copy the December OTA to your SDcard or PC.
Once you have taken a backup of your data, reboot to recovery. If you have the December OTA in your SDcard, select "Apply update from SD card" and select the file. Else if you have it your PC, select "Install update from ADB" and use "adb sideload <filename>" to flash it. The installation will fail. Reboot once. Now your bootloader will be downgraded to Nougat.
Step 2:
Extract D1C-562F-0-00CN-B01_Exploit.7z.
Step 3:
Extract OST LA properly. In the extracted folder right click on setup.bat, run it with administrator privileges. After the procedures are completed, open "OST 604 FIH Mobile" in the start menu. Connect your phone to PC and select "Reboot to bootloader" from recovery. Load the .mlf file from D1C-562F-0-00CN-B01_Exploit folder. Uncheck "Check System AP Status" and click next. You'll get a warning that the software versions don't match. Click OK and continue. OST will prompt you to erase data, accept that too. The OST will now flash the software. Wait for it to complete.
Step 4:
Once it is complete, the phone will reboot. Complete the initial setup. Congrats! You have successfully converted your Nokia 6 into a China variant. You can install the Google Play store apk from here.
Some cool features you'll be getting:
Code:
[LIST]
[*]Long Screenshot
[*]Screen recording
[*]Smart alert
[*]Double tap status bar to sleep
[*]Direct call and answer
[*]One hand mode
[*]Network speed indicator
[*]and more ...
[/LIST]
To revert back to global, you can flash TA1021_PLE-558B-0-00WW-B01.7z
Credits: @hikari_calyx
No link
Bit hard with no file link
krankedcaraudio said:
Bit hard with no file link
Click to expand...
Click to collapse
Which link? All links are working. I just checked...
China variant's Firmware - Download link
This file has been removed.
krankedcaraudio said:
China variant's Firmware - Download link
This file has been removed.
Click to expand...
Click to collapse
https://ibb.co/mv2gvK
Try refreshing or use a different browser
Sorry for ftm file missing.
I'm reuploading D1C-562C and D1C-562D (September 2018) firmwares.
Speaking of that, I've replaced the bootloader to older version to create following exploits:
- dm-verity command for flashing recovery and phone easily
- qualcomm EDL mode access possible
- accept bootloader unlock key
hikari_calyx said:
Sorry for ftm file missing.
I'm reuploading D1C-562C and D1C-562D (September 2018) firmwares.
Speaking of that, I've replaced the bootloader to older version to create following exploits:
- dm-verity command for flashing recovery and phone easily
- qualcomm EDL mode access possible
- accept bootloader unlock key
Click to expand...
Click to collapse
:good:
FTM file is not a big deal. It's just a matter of copy-pasting it to the extracted folder
Continue uploading new firmwares!
i do not recommend you guys do this, the chinese version doesn't have google location services and instead uses some chinese location provider which doesn't work with google location history and apps like google fit
Can we convert nokia 6 china to golbal and have NFC working?
No SIM card
Flashed this on my TA-1021. Still no SIM card detected on neither of slots. Problem started after flashing the "homebrew" Oreo firmware. Can anyone help please?
Fakkurai said:
i do not recommend you guys do this, the chinese version doesn't have google location services and instead uses some chinese location provider which doesn't work with google location history and apps like google fit
Click to expand...
Click to collapse
Rlly? which nokia 6 model were you using when you did it? I was thinking to do this on my nokia 6 TA 1039...
---------- Post added at 03:13 PM ---------- Previous post was at 03:05 PM ----------
Akilesh T said:
Code:
Some cool features you'll be getting:
[LIST]
[*]Long Screenshot
[*]Screen recording
[*]Smart alert
[*]Double tap status bar to sleep
[*]Direct call and answer
[*]One hand mode
[*]Network speed indicator
[*]and more ...
[/LIST]
Click to expand...
Click to collapse
Does this Chinese version allow miracast screen mirroring?
I can convert my Chinese version to global variant?
tvi_vladutz said:
I can convert my Chinese version to global variant?
Click to expand...
Click to collapse
Yes. Download TA1021_PLE-558B-0-00WW-B01.7z from here. Rest of the process is the same.
Does this Chinese version allow miracast screen mirroring?
Click to expand...
Click to collapse
Yes. Casting can be done. Am I right @singhnsk?
Akilesh_15 said:
Yes. Download TA1021_PLE-558B-0-00WW-B01.7z from here. Rest of the process is the same.
Click to expand...
Click to collapse
Ok, thank you, I'll try, in case of anything happens, I can rollback that?
tvi_vladutz said:
Ok, thank you, I'll try, in case of anything happens, I can rollback that?
Click to expand...
Click to collapse
Yes, you can switch between CN and WW easily.
But I will receive the future updates?
Help! It's broken... Is stuck at Powered by Android....
Error 7
Error in /sideload/... something...
I have acces to Recovery but i'm noob in phone recovering,I'm into pc's
Sorry for double post.
I really need some help.
Update: I resolved, now i have TA-1025 instead TA-1000, I hope things will be better now, thank you for help.
Update2: I've lost some of the features like the design itself, call recording, screen recording, doube tap to lock but the main problem from CN is fixed, I can use both sim's.
Akilesh_15 said:
Yes. Casting can be done. Am I right @singhnsk?
Click to expand...
Click to collapse
Not sure of Miracast. But it does work with a ton of devices. Not being able to cast to Windows 10 PC since the past few updates. It used to work in the past.
After converting, the OTA work, right?
Hello everybody, I'm sharing this tutorial to how to force Android Pie installation on retail moto x4.
Warning: read all the steps carefully. I'm not responsible for your actions and you're on your own on this..
What you need to do this
At first, follow the commandments to change the firmware of a mobile phone:
You will need an SD card (minimum 2gb of memory) !!! IMPORTANT !!! - See step 3.1 if you don't have a SD Card
Check if the battery is above 80%
Make sure you have ADB + Fastboot drivers installed AND YOU CAN ACCESS IT FROM YOUR COMMAND PROMPT
Make sure you have the latest Motorola Drivers installed on your computer.
Tested on:
- XT1900-1 - Ok
- XT1900-4 - Ok
- XR1900-5 w/ Android 8.0 - Ok
- XT1900-6 w/ Android 8.1 - Ok
- XT1900-7 w/ Android 8.0 - Ok
Not working for:
- XT1900-2 Indian Variant
Let's do this.
Step 1
Understand that this Pie update zip does not work on devices running Android One (google_fi) or Amazon (AMZ), only Retail phones. No matter if you have already installed other systems on it, you have to be in a retail (better with locked bt).
If you are not in retail, I picked up the latest retail firmware to install. Flash it on your device before proceeding.
Warning: note If your actual version number (OPWS 99.999.99-99) is lower than you will download below. If your current version number is higher, the procedure will not work and you will have to abandon this tutorial unless you unlock your bootloader, and I do not recommend doing this since rollback can cause brick your device permanently.
For Retail Android 8.1
Firmware: https://moto.netlib.re/payton/PAYTON_OPWS28.46-21-16_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
For Retail Android 8.0 devices (devices which never updated to 8.1) -- thanks to Comby_sk
Firmware: https://moto.netlib.re/payton/PAYTON_OPWS27.57-40-25_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Android Pie Firmware: https://moto.netlib.re/payton/OTAs/ab_delta-Blur_Version.27.301.32-29.11.36.payton.retail.en.US.zip (don't download the step 2's file if you're downloading this. THIS IS ONLY FOR ANDROID 8.0 NOT 8.1)
-------
You will need this file too. Copy all text, create a notepad file with it's content and name it "Flash-all.bat".
Flash-all.bat: https://pastebin.com/pZ9ZteGX
Step 2
Skip to step 3.1 if you don't have a SD Card
After installing the Android 8.1 firmware on your device, download this ROM and place it at the root of your SD card.
Android Pie Firmware: https://moto.netlib.re/payton/OTAs/ab_delta-Blur_Version.28.271.24-29.11.36.payton.retail.en.US.zip
Step 3
Reboot your device to Fastboot, and start it on recovery mode (hold power button and press volume + -- don't hold both buttons simultaneously). When done, select "Apply update from SD card" and select the update package. The update is slow and it took more than 1 hour with me. Then sit back and relax while it's installed.
Step 3.1
If you don't have a SD Card, you should upload the file with a ADB command.
Download the file from Step 2 and put the file in the same directory where your adb is installed.
Restart your payton to recovery mode (hold power button and press volume + -- don't hold both buttons simultaneously). When done, select "Apply update from ADB" and them run this command from CMD:
HTML:
adb sideload path_to_your_file
this command can take about 40 to 60 minutes for the speed of uploading and installing the update.
Note: path_to_your_file should be the full file name where your downloaded zip are.
Step 4
To work everything perfect and with no bug after the upgrade:
I) Go to settings -> System -> Advanced -> Reset options -> Factory reset the device
II) If the phone stucks on motorola boot screen, soft reset it. (hold power button for ~15 seconds)
III) Do all the initial setup procedures, then update the all the pending Play Store apps, and restart the device.
After that, your device will be with the stock Android Pie installed. Congratulations.
Have you tried it with the bootloader blocked?
Just did it on my XT1900-6, working fine but i had to install the update via adb.
[XT1900-7][STOCK][PIE] Install stock Android Pie without unlocked bootloader
It looks that guide from OP can be used for installing stock Pie on XT1900-7 reteu model.
Step 1.
Install OPWS27.57-40-25 fastboot package (Blur_Version.27.301.32.payton.retail.en.US with october 2018 security patch) instead from OP
Step 2.
Install PPW29.69-26 OTA (Blur_Version.29.11.36.payton.retail.en.US) instead from OP
Will try tonight.
al3al3al3jandr0 said:
Have you tried it with the bootloader blocked?
Click to expand...
Click to collapse
this tutorial is for locked/blocked bootloader
-
Sorry i was wrong.
SebastKae said:
@Comby_sk The last one is linked to the same file than the OP?
Click to expand...
Click to collapse
No, it is different. OP file is "28.xx.xx" to "29.xx.xx". My file is "27.xx.xx" to "29.xx.xx".
27 = 8.0
28 = 8.1
29 = 9.0
XT1900-7 never had 8.1, only 8.0. For XT1900-7 upgrade from 27 to 29 is needed.
What is the process for xt1900-2? I am on latest october patch OPWS 27.57-40-3-15
Prinjal Dave said:
What is the process for xt1900-2? I am on latest october patch OPWS 27.57-40-3-15
Click to expand...
Click to collapse
No one, your blur version "27.306.16" hasn´t Pie OTA yet.
Comby_sk said:
No one, your blur version "27.306.16" hasn´t Pie OTA yet.
Click to expand...
Click to collapse
So i can't update to pie yet.... Right?
Prinjal Dave said:
What is the process for xt1900-2? I am on latest october patch OPWS 27.57-40-3-15
Click to expand...
Click to collapse
I've updated the thread with Android 8.0 options.
CypherPotato said:
I've updated the thread with Android 8.0 options.
Click to expand...
Click to collapse
Thanks
CypherPotato said:
I've updated the thread with Android 8.0 options.
Click to expand...
Click to collapse
I have XT1900-2 OPWS27.57-40-3-15
How to flash/update PIE using these files? both files through SD Card or manually using fastboot method?
Code:
For Retail Android 8.0 devices (devices which never updated to 8.1) -- thanks to Comby_sk
Firmware: https://moto.netlib.re/payton/PAYTON...LT_CFC.xml.zip
Android Pie Firmware: https://moto.netlib.re/payton/OTAs/a...tail.en.US.zip (don't download the step 2's file if you're downloading this. THIS IS ONLY FOR ANDROID 8.0 NOT 8.1)
Prinjal Dave said:
So i can't update to pie yet.... Right?
Click to expand...
Click to collapse
Right
zlebors said:
I have XT1900-2 OPWS27.57-40-3-15
How to flash/update PIE using these files? both files through SD Card or manually using fastboot method?
Code:
For Retail Android 8.0 devices (devices which never updated to 8.1) -- thanks to Comby_sk
Firmware: https://moto.netlib.re/payton/PAYTON...LT_CFC.xml.zip
Android Pie Firmware: https://moto.netlib.re/payton/OTAs/a...tail.en.US.zip (don't download the step 2's file if you're downloading this. THIS IS ONLY FOR ANDROID 8.0 NOT 8.1)
Click to expand...
Click to collapse
Same thing as the post says. Flash Firmware using fastboot and flash Android Pie Firmware from recovery
CypherPotato said:
I've updated the thread with Android 8.0 options.
Click to expand...
Click to collapse
I think, it won't work on all 8.0 versions. E.g. XT1900-2 OPWS 27.57-40-3-15 has different blur version "27.306.16", but Pie OTA needs "27.301.32".
Is this for xt19-1 or what
boonemeat said:
Is this for xt19-1 or what
Click to expand...
Click to collapse
for all devices
This doesn't work with large SD cards since recovery mode can't mount the external sd card. I tried with a 128gb one and it failed, luckily I had a 4GB one lying around.
Comby_sk said:
I think, it won't work on all 8.0 versions. E.g. XT1900-2 OPWS 27.57-40-3-15 has different blur version "27.306.16", but Pie OTA needs "27.301.32".
Click to expand...
Click to collapse
CypherPotato said:
for all devices
Click to expand...
Click to collapse
any suggestions?
**** Disclaimer: I'm not responsible if you destroy your device. Use at your own risk!!! ****
GrapheneOS is an open source privacy and security focused mobile OS with Android app compatibility. It's focused on the research and development of privacy and security technology including substantial improvements to sandboxing, exploit mitigations and the permission model. Currently it is based on AOSP.
Link: (Mod Edit: Link removed)
Important information:
1. This ROM does NOT include Gapps or Google Play Service and hasn't Signature Spoofing Support. If you rely on the mentioned things this Rom isn't for you.
2. I take the official releases, modify the install script and include a pre-patched Magisk boot image. I'm not in contact with the GrapheneOS dev which is the reason why i mark this ROM as Unofficial.
3. Due of point two: Please don't ask questions on the official channels as reddit. Leave comments etc here on this thread.
4. You need a unlocked bootloader to flash this rom and must have adb+fastboot installed on your computer. If this is not the case download it from here: https://developer.android.com/studio/releases/platform-tools
I plan to make unofficial releases when new official builds are available.
Features:
AOSP 10
Built-in Firewall
Built-in local backup function (it's not working on all Apps; some doesn't support it)
Improved MAC Randomization
Hardened Kernel
Expanded Permissions (sensors)
Force calls to 4G only
Bugs
- Receiving text over verizon sim doesn't work reliable. Thx @wolfu11 for reporting.
Download: (Mod Edit: Link removed)
Installation:
Notice 1: The First-time installation will wipe your data. Backup first (i recommend this too when you follow the update instructions to be safe)
Notice 2: I recommend to have the newest stock firmware before the First-time installation
First-time installation:
1. Download the zip from the linked download page and unzip it on your computer
2. Copy the following files into the plattform-tools folder:
-> coral zip
-> bootloader img
-> radio img
-> flash-all_first_install.bat for Windows or flash-all_first_install.sh for Linux
3. Boot your phone into fastboot mode and verify that the phone is recognized from your computer
4. In Terminal (Linux) or Powershell (Windows): Run the appropriate script
5. Install the Magisk Manager App
10. Be happy with a rooted GrapheneOS
Update:
Notice: I assume that fastboot+adb is still installed on your computer.
1. Download the newest zip from the linked download page and unzip it on your computer
2. Copy the following files into the plattform-tools folder:
-> coral zip
-> bootloader img
-> radio img
-> flash-all.bat for Windows or flash-all.sh for Linux
If your computer asks you to overwrite the current files in the plattform-tools folder, confirm it.
3. Boot your phone into fastboot mode and verify that the phone is recognized from your computer
4. In Terminal (Linux) or Powershell (Windows): Run the appropriate script
5. Start the system once. This need a few more time than the first installation cause the data partition remains. Be patient.
6. Install the Magisk Manager App
7. Be happy with a rooted GrapheneOS
Sources:
https://github.com/GrapheneOS
https://grapheneos.org/releases
https://github.com/GrapheneOS/kernel_google_coral
https://github.com/GrapheneOS/device_google_coral-kernel
All Credits go to:
- The GrapheneOS team
- wolfu11 for reporting the verizon bug and testing the windows scripts
- and topjohnwu for his amazing Magisk
Created: 09.08.2020
Based on: Android 10
Updated: 21.08.2020
Current Version: 2020.08.07.01
Changelog from 09.08.2020
New Release: 2020.08.03.22
SHA3-512 Hash for Complete zip:
Code:
773c67b8571927c6f884a98ee67a10f96c3a759e34f925f7a8aaab7c19a4ca6b1ff53bb6dc500b4fe7c306b73853189a1c559889df6d9b4f2e8a90258d3d26c9
SHA3-512 Hash for Unpatched boot.img:
Code:
9b584f6941d37f60a7ed17ec4108b7bf484c3cbf1b63f2be6af1e59f452ed1d06e1b64704785d6ca3b38a3c09c8f29657f88c757bda993df509ef001d9842f00
Changes:
full 2020-08-01 security patch level
full 2020-08-05 security patch level
rebased onto QQ3A.200805.001 release
fix secondary stack hardening when a non-page-size multiple stack size is specified
fix picking up previous build date when doing incremental builds
Vanadium: update Chromium base to 84.0.4147.89
Vanadium: update Chromium base to 84.0.4147.105
Vanadium: update Chromium base to 84.0.4147.111
Vanadium: remove Chromium logo in chrome://version
kernel (Pixel 4, Pixel 4 XL): read-only data expansion
Changelog from 11.08.2020:
Updated the OP with some more informations
Rewrite the instruction cause i believe that they were not fully correct.
Reupload the 2020.08.03.22 unofficial release with new structure. I patched the boot.img which come with GrapheneOS in the zip with Magisk and then replaced the original GrapheneOS boot.img in the zip with the patched version.
Hi good evening to all,
Can somebody try to install this Rom with the updated instructions? I think they should work now (at least on Linux) but i would appreciate a confirmation to be safe.
dhacke said:
Changelog from 11.08.2020:
Updated the OP with some more informations
Rewrite the instruction cause i believe that they were not fully correct.
Reupload the 2020.08.03.22 unofficial release with new structure. It isn't needed anymore to flash Magisk separately from the zip. I replaced the stock boot.img in the zip with the pre-patched one.
Click to expand...
Click to collapse
Just a heads up - you really aren't meant to pre-patch a boot image for Coral/Flame, as you are only meant to patch the boot image from your own individual device, as per the man topjohnwu himself
See: https://twitter.com/topjohnwu/status/1272136975022084097?s=19
Can you supply the unpatched boot img?
Thank you
wolfu11 said:
Can you supply the unpatched boot img?
Thank you
Click to expand...
Click to collapse
Done. Look here: (Mod Edit: Link removed)
I added an SHA3-512 Hash for file checking,too (see changelog from 11.08.2020).
Changelog from 15.08.2020
New Release: 2020.08.07.01
SHA3-512 Hash for Complete zip:
Code:
f3a2b088e0ec503296d5a2527a3766951cb2a3ccd1955ced14d304222e76ed3f341dd9d84b6e186a534eddac335065b756c1fdc89d0f1db3985314424e7f9eea
SHA3-512 Hash for unpatched boot image:
Code:
11abb901511ce8e39911bc951be4b1a349158c5d8389e74766942159c0f83aa9730ed39d8c8ae6c3cc66be559e3c165b5d4f35e0962d20a7be0b1532673a0287
Changes:
SELinux policy: fix executing apk libraries as executables for third party applications
Installation Notices:
From 2020.08.03.22 => No wipe needed. Just take the update scripts and let the right one running (see OP).
From Stock Rom => Use the install_first scripts. Be aware: This will wipe your data
Apart from that i recommend to make a backup first always (to be safe).
Wireguard Kernel integration
dhacke said:
Hi good evening to all,
Can somebody try to install this Rom with the updated instructions? I think they should work now (at least on Linux) but i would appreciate a confirmation to be safe.
Click to expand...
Click to collapse
Hi, great work!! It was exactly what I was looking for, GrapheneOS with root. Are you able to integrate wireguard into the kernel?
[email protected] said:
Hi, great work!! It was exactly what I was looking for, GrapheneOS with root. Are you able to integrate wireguard into the kernel?
Click to expand...
Click to collapse
Hi Cryptt33,
first thx for your praise.
Regarding wireguard integration:
You should be able to use Wireguard independently from the kernel if i understand the description from the wireguard f-droid app right (https://f-droid.org/en/packages/com.wireguard.android/).
Then Wireguard runs in a userspace version. Apart from that i have found a xda thread already regarding wireguard integration. I guess i will at least try it and mayby i will be successful with the help of the thread. But i can't give a eta. I built roms from sources in the past but i until now i didn't try to modify them before the compiling step.
Best regards
dhacke
dhacke said:
Hi Cryptt33,
first thx for your praise.
Regarding wireguard integration:
You should be able to use Wireguard independently from the kernel if i understand the description from the wireguard f-droid app right (https://f-droid.org/en/packages/com.wireguard.android/).
Then Wireguard runs in a userspace version. Apart from that i have found a xda thread already regarding wireguard integration. I guess i will at least try it and mayby i will be successful with the help of the thread. But i can't give a eta. I built roms from sources in the past but i until now i didn't try to modify them before the compiling step.
Best regards
dhacke
Click to expand...
Click to collapse
Just need to add this to local_manifest for WG support
If unfamiliar with local_manifest, it's located in /.repo/local_manifests/ - it'll be the only file in that dir, often it's called room service.xml but it could be something like graphene_manifest.xml. Either way, it'll be the only file there and it'll be an XML - add those lines above to it and sync and you should have WireGuard support.
<remote name="zx2c4" fetch=https://git.zx2c4.com/>
<project remote="zx2c4" name="android_kernel_wireguard" path="kernel/wireguard" revision="master" sync-s="true" />
dhacke said:
Hi good evening to all,
Can somebody try to install this Rom with the updated instructions? I think they should work now (at least on Linux) but i would appreciate a confirmation to be safe.
Click to expand...
Click to collapse
I've tried this several time with a windows computer with no luck the shell opens briefly with red writing on the top and closes.
i must be doing something wrong but can't put my finger on it..... i run windows ltsb but i don't have any issues up and downgrading my p4 xl on it i am running the latest platform tools but get this message:
C:\Users\Wolf's laptop\Desktop\platform-tools_r30.0.4-windows\platform-tools>flash-all_first_install
fastboot : The term 'fastboot' is not recognized as the name of a cmdlet, function, script file, or operable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:10
+ $version=fastboot --version; try { $verNum = $version[0].substring(17 ...
+ ~~~~~~~~
+ CategoryInfo : ObjectNotFound: (fastboot:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
fastboot too old; please download the latest version at https............
wolfu11 said:
I've tried this several time with a windows computer with no luck the shell opens briefly with red writing on the top and closes.
i must be doing something wrong but can't put my finger on it..... i run windows ltsb but i don't have any issues up and downgrading my p4 xl on it i am running the latest platform tools but get this message:
C:\Users\Wolf's laptop\Desktop\platform-tools_r30.0.4-windows\platform-tools>flash-all_first_install
fastboot : The term 'fastboot' is not recognized as the name of a cmdlet, function, script file, or operable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:10
+ $version=fastboot --version; try { $verNum = $version[0].substring(17 ...
+ ~~~~~~~~
+ CategoryInfo : ObjectNotFound: (fastboot:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
fastboot too old; please download the latest version at https............
Click to expand...
Click to collapse
Hi wolfu11,
i know this message in similar way on Linux. To fix it on linux i need to run all fastboot commands and scripts with './' before.
So for example:
./fastboot devices instead of fastboot devices or ./flash-all.sh instead of flash-all.sh.
I done this in the scripts for linux already cause i know it is needed there but didn't thought that it is needed on windows, too.
So please go into the script and make this before all fastboot commands:
./
Save it and execute it in the plattform-tools folder with ./ again in the shell. Hopefully it runs then.
If this fixes your issue, i will update the windows scripts.
dhacke said:
Hi wolfu11,
i know this message in similar way on Linux. To fix it on linux i need to run all fastboot commands and scripts with './' before.
So for example:
./fastboot devices instead of fastboot devices or ./flash-all.sh instead of flash-all.sh.
I done this in the scripts for linux already cause i know it is needed there but didn't thought that it is needed on windows, too.
So please go into the script and make this before all fastboot commands:
./
Save it and execute it in the plattform-tools folder with ./ again in the shell. Hopefully it runs then.
If this fixes your issue, i will update the windows scripts.
Click to expand...
Click to collapse
I will try it when I get home today thank you
wolfu11 said:
I will try it when I get home today thank you
Click to expand...
Click to collapse
that didn't work either i downloaded the latest platform tools so im at a loss about the fastboot issue.
I'm going keep trying
Update: I was able to get the official Graphene to work via putting the image into a working stock update platform tools folder and renaming it to the stock image. it wouldn't work per instruction on the website very strange.
wolfu11 said:
that didn't work either i downloaded the latest platform tools so im at a loss about the fastboot issue.
I'm going keep trying
Update: I was able to get the official Graphene to work via putting the image into a working stock update platform tools folder and renaming it to the stock image. it wouldn't work per instruction on the website very strange.
Click to expand...
Click to collapse
Well it was worth a shot texts don't work on verizon so i guess i'll just give up.
thank you
wolfu11 said:
Well it was worth a shot texts don't work on verizon so i guess i'll just give up.
thank you
Click to expand...
Click to collapse
Hi wolfu11,
i tested the bat script (more precisely flash-all.bat) with './' on my dedicated gaming machine with win 10 2004 education, too. First i got the same problem as you: It didn't run whether i made './' before all fastboot commands in the scripts.
Then i removed all the './' before all fastboot command except at this line:
Code:
$version= fastboot --version; ^
So the line looks now:
Code:
$version=./fastboot --version; ^
And hurray the script worked without problems on my machine (see attached screenshots).
Only as reminder: The bat scripts are from the 2020.08.07.01 unofficial release so you need the radio, bootloader and image files from that release.
i attached the new scripts with my mentioned modification, too. Xda doesn't allow bat files so i made them into a zip file. Please test once more. Thx in advance.
dhacke said:
Hi wolfu11,
i tested the bat script (more precisely flash-all.bat) with './' on my dedicated gaming machine with win 10 2004 education, too. First i got the same problem as you: It didn't run whether i made './' before all fastboot commands in the scripts.
Then i removed all the './' before all fastboot command except at this line:
Code:
$version= fastboot --version; ^
So the line looks now:
Code:
$version=./fastboot --version; ^
And hurray the script worked without problems on my machine (see attached screenshots).
Only as reminder: The bat scripts are from the 2020.08.07.01 unofficial release so you need the radio, bootloader and image files from that release.
i attached the new scripts with my mentioned modification, too. Xda doesn't allow bat files so i made them into a zip file. Please test once more. Thx in advance.
Click to expand...
Click to collapse
That script worked thanks
wolfu11 said:
That script worked thanks
Click to expand...
Click to collapse
Yeah finally. I'm happy to read that. Then i will update the OP & scripts in the next days and take you on the credit section. Thx very much for your windows testing.
Now the next on the to-do list is the building of this rom from source and adding Wireguard support into the kernel
dhacke said:
Yeah finally. I'm happy to read that. Then i will update the OP & scripts in the next days and take you on the credit section. Thx very much for your windows testing.
Now the next on the to-do list is the building of this rom from source and adding Wireguard support into the kernel
Click to expand...
Click to collapse
No problem i'm happy to test. unfortunately the still is an issue with texting on verizon which is what i use this phone on. the texts send but receiving them is not reliable. I tested on an att sim and it didn't have an issue so it's something on verizon's end.
Blu G90 device shipped from factory with Android 10
as with other devices from blu they do not have a public download of there roms. So here is the stock rom pulled from the device with SP-Flash tool.
Both the shipped rom build fingerprint
Code:
ro.bootimage.build.fingerprint=BLU/G90/G0310WW:10/QP1A.190711.020/1585383273:user/release-keys
And the ota update from June fingerprint
Code:
ro.system.build.fingerprint=BLU/G90/G0310WW:10/QP1A.190711.020/1592848714:user/release-keys
are in android file host flash-able with spflash tool, if needed.
I know the first thing to have before modifying android is the method to recover from bad edits. So here they are.
Other works will be stored in this same folder.
https://www.androidfilehost.com/?w=files&flid=315927
First stock rom is Dumped to github, If you need or want specific files, without needing to download whole rom.
https://github.com/mrmazakblu/blu_g0310ww_dump
Stock kernel source:
https://github.com/mrmazakblu/Blu_G90_G0310WW_stock_kernal
Device INFO
*******Above links are pulled firmware. Below is an official firmware file, w/ verified images.********
https://www.mediafire.com/folder/ocmvgrcd73bqy/G90
**
.
Bootloader unlock is same as past devices.
1. enable develper options
2. enable OEM unlock , from inside developer options
3. Reboot to bootloader (adb reboot bootloader, or button combo)
4. fastboot flashing unlock
5. Select confirm on device
6. fastboot reboot (causes factory reset)
Flashing GSI
few more steps than Pie devices, but not too complicated.
You will need recent fastboot tools as tested these steps were done with V30.0.4
https://developer.android.com/studio/releases/platform-tools
Verified boot is enabled on device. The verity key is stored into 3 section.
vbmeta.img
vbmeta_system.img
vbmeta_vendor.img
All found in stock rom. Shared in first post.
1. Unlock bootloader. (see last post)
2. Reboot to bootloader to disable verity
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_system vbmeta_system.img
fastboot --disable-verity --disable-verification flash vbmeta_vendor vbmeta_vendor.img
3. Reboot from bootloader to fastboot(new interface for android 10)
Code:
fastboot reboot fastboot
4. flash sysem from "fastbootd"
Code:
fastboot flash system **gsi-system.img**
Use 64 bit AB GSI
5. Wipe data so the new system will work
Code:
fastboot -w
ROOT::
Not yet confirmed yet. Magisk patched_boot has not provided root as of yet.
Currently looking into pre-rooting the system.img, but not success yet.
TWRP;;
https://forum.xda-developers.com/android/development/twrp-twrp-3-4-0-0-blu-g90-g0310ww-t4163497
.
I have been able to edit the stock /system and flash it back to phone.
--I have added adaway host file
--Removed the SIMO app
-- Removed the IGNITE adware app (dti.blu)
--Removed The Verizon Remote SIM lock app
--Removed Blu-Privacy app
--Removed Opera browser app
--Deodexed Rom (rom would not boot past splash screen without this)
Uploaded edited sysem.img to device folder listed in OP.
Flash with same instructions as How to flash GSI
--Attempting to add SU binary makes rom fail to boot. So still no stock rooted.
Maybe soon.
/
Blu released kernel source today. 8-27. The tar.hz is dated April, eh, whatever.
I added the source files to the wip twrp tree, it compiles without error. (Not my normal experience , on first time out with Blu kernel).
But as mentioned before, the twrp will not pack the image correctly. Because of the need for new dtb commands that twrp 9.0 build environment does not accept.
And when building in the twrp 10.0-wip tree, the results have not booted for me yet. (I'm on build attempt 12, or so)
I'm rambling, sorry.
When I repack the twrp using the built kernel, twrp has only blank screen, and adb is active. So kernel is slightly off.
Build did not output separate dtb or dtbo.
Well I confirmed it, the screen on this phone is not the one the kernel is building for.
I compared the defconfig from source, the one that matches the name in build prop, to the one I pulled from /proc. And they are different, and the kernel errors out during build when using right defconfig. So, waiting again for Blu to provide the files.
There does not appear to be any interest in this phone, other than my own.
Well maybe it will catch on
It's been advertised on many mm ore locations than the average BLU phone.
Amazon
Ebay
Walmart
Newegg
Best buy
B&H photo
Time will tell.
mrmazak said:
Well I confirmed it, the screen on this phone is not the one the kernel is building for.
I compared the defconfig from source, the one that matches the name in build prop, to the one I pulled from /proc. And they are different, and the kernel errors out during build when using right defconfig. So, waiting again for Blu to provide the files.
Click to expand...
Click to collapse
Any luck with Blu providing the correct kernel files?
Ivisibl3 said:
Any luck with Blu providing the correct kernel files?
Click to expand...
Click to collapse
Not yet. They acknowledged my email, but as yet have not updated there posted source.
Root is half way achieved.
Factory rom was found. It included a boot-debug.img
When this image is used in boot partition, adb root is allowed.
It is only limited root. Example: blockdev command , used to allow remount / to rw, is not permitted. Bit is start.
Factory flashtool rom shared on Blu developers mediafire page.
Will add link to debug-boot.img soon
added to device folder listed in OP
google information on debug-boot.img
https://source.android.com/compatibility/vts/vts-on-gsi
if you have the stock boot.img, and magisk manager, why cant you patch the boot.img and then disable dm-verity by flashing vbmeta.img/vbmeta_system.img/vbmeta_vendor.img and then flash the boot.img via sp flash tool to give you root access?
aryanhington said:
if you have the stock boot.img, and magisk manager, why cant you patch the boot.img and then disable dm-verity by flashing vbmeta.img/vbmeta_system.img/vbmeta_vendor.img and then flash the boot.img via sp flash tool to give you root access?
Click to expand...
Click to collapse
because magisk init is not starting on a patched image. have no sign on magisk in the any of the logs.
the issue is posted on magisk github issue tracker. no solution as of yet.
mrmazak said:
because magisk init is not starting on a patched image. have no sign on magisk in the any of the logs.
the issue is posted on magisk github issue tracker. no solution as of yet.
Click to expand...
Click to collapse
why this that occurring, because for umidigi devices on android 10 work fine https://community.umidigi.com/forum.php?mod=viewthread&tid=19114 and they also use a mediatek chipset?
aryanhington said:
why this that occurring, because for umidigi devices on android 10 work fine https://community.umidigi.com/forum.php?mod=viewthread&tid=19114 and they also use a mediatek chipset?
Click to expand...
Click to collapse
different brand, so built differant. just like ther are redmi (xiamoi) devices with mtk, but fastboot unlock doe not work, it needs redmi app to unlock. and flash tool not work on all devices with MTK, like amazon fire device , they have mtk and do not work with fastboot unlock, or spflash.
mrmazak said:
I have been able to edit the stock /system and flash it back to phone.
--I have added adaway host file
--Removed the SIMO app
-- Removed the IGNITE adware app (dti.blu)
--Removed The Verizon Remote SIM lock app
--Removed Blu-Privacy app
--Removed Opera browser app
--Deodexed Rom (rom would not boot past splash screen without this)
Uploaded edited sysem.img to device folder listed in OP.
Flash with same instructions as How to flash GSI
--Attempting to add SU binary makes rom fail to boot. So still no stock rooted.
Maybe soon.
/
Click to expand...
Click to collapse
which steps did you take to modify the stock /system?
aryanhington said:
which steps did you take to modify the stock /system?
Click to expand...
Click to collapse
used superr script to unpack stock super.img and continued to extract system.img
manually went through the extracted system/system/app folder and deleated the aps I did not want (adware// bloate)
used the rom tools option / deodex
then repacked the system.img
aryanhington said:
why this that occurring, because for umidigi devices on android 10 work fine https://community.umidigi.com/forum.php?mod=viewthread&tid=19114 and they also use a mediatek chipset?
Click to expand...
Click to collapse
This is not entirely true.
Many Umidigi phones have been upgraded from 9 to 10. So the partitions would be very similar and considerably easy to root.
But for new phones coming with 10 the story changes. Read the last pages of your link's article. In addition, I know why and effect on Umidigi Power 3 still has limitations on root.
So this BLU G90 is not very different and depends on a lot of experimentation and tests. I believe that the OP is doing a great job mainly taking everything to github and trying to compile the kernel and firmware.
DragonPitbull said:
This is not entirely true.
Many Umidigi phones have been upgraded from 9 to 10. So the partitions would be very similar and considerably easy to root.
But for new phones coming with 10 the story changes. Read the last pages of your link's article. In addition, I know why and effect on Umidigi Power 3 still has limitations on root.
So this BLU G90 is not very different and depends on a lot of experimentation and tests. I believe that the OP is doing a great job mainly taking everything to github and trying to compile the kernel and firmware.
Click to expand...
Click to collapse
can you elaborate what you mean by this?