[GUIDE/TUTORIAL/HOWTO] HTC One M7 Stock to Android 11 / LineageOS 18.1
[GUIDE/TUTORIAL/HOWTO] HTC One M7 any version (m7, m7ul, m7spr, m7vzw) stock to Android 11 R / LineageOS 18.1
This detailed step-by-step guide helps you transform your HTC One M7 (any version) to a powerful one with Android 11.
Make sure you have the One M7 model, in Android, go to Settings > About phone and check the model.
CHANGELOG
v8. Upgrade to Android 11, improve readability, update pack
v7. Updated pack with MagiskManager 8.0.7 and Magisk 21.4
v6. Infos in case of Simlock
v5. Moved to Android 10 thanks to @tarkzim, updated pack with Magisk 20.4
v4. Moving to Android 9. I was wrong in v3 ;- Thx @tarkzim), good for all M7 versions
v3. Reverted back to Android 7.1. No stable ROM for Android 8 or 9 (and will never be)
v2. Tutorial updated for Android 8.1 Oreo, updated pack with TWRP 3.3.1-0
v1. Initial release
1) DOWNLOAD
- djibe HTC One M7 pack (44.3 Mo) v2 : http://bit.ly/djibe-onem7-v1
(includes HTC drivers, recovery TWRP 3.6.1_9-0 for all m7 by Xeno1, Magisk Root 23 adb & fastboot.exe).
Unzip the djibe folder from the zip on root folder of C: drive.
- ROM Unofficial Lineage OS 18.1 for M7: https://forum.xda-developers.com/t/rom-11-0-unofficial-m7-all-lineageos-18-1-stable.4454219/
Download latest build for M7 here: https://androidfilehost.com/?w=files&flid=334598&sort_by=date&sort_dir=DESC
+ BitGApps ARM 11 v1.4+: https://github.com/BiTGApps/BiTGApps-Release/releases/
+ Charge phone to 100 %
WARNING. This tutorial uses Microsoft Windows.
WARNING. Warranty is now void.
WARNING. Read carefully the sentences starting with ###.
2) BACKUP DATA AND INSTALL DRIVERS
Disable Antivirus.
Install drivers from my pack:
right click on HTCDriver.exe -> click on Run as administrator and continue the setup.
Then install HTC_BMP_USB_Driver_x64.msi (or *_x86 if you have a 32bits Windows edition).
### Install doesn't work ? Try these drivers for Win10 : https://htcusbdriver.com/download/htc-usb-driver-v4-02-0-001
Now go to my folder flash, and right click the adb 15seconds installer > Run as administrator.
During install, every time the command asks you a confirmation, enter Y and confirm with Enter.
Connect HTC One (while phone on) to PC, let drivers install.
In Windows explorer, HTC One should be available.
### If not make sure phone connection is in File transfer mode (see Android notifications).
Collect all personal photos, videos, etc ... and copy these on PC.
Use an app like Backupyourmobile to backup texts, contacts, etc.
Check that backup is located on microSD card.
Then copy the backup on your PC.
Disconnect phone.
### If your phone is Simlocked/carrier locked/Network locked, don't go further.
Visit official website of your network carrier (or call their support) to retrieve your desimlock code.
Ask them for details on how to remove simlock.
How do I know my phone is simlocked ? When you insert a SIM card from another operator, network is not accessible.
Only a stock ROM can remove simlock.
To go back from custom ROM to stock in 1 zipfile flash, follow this tutorial: https://tcg96.github.io/m7gurureset
3) UNLOCK BOOTLOADER
In Android, go to Settings > About > Software information > More.
Tap 7 times on Build number. It unlocks Developer options.
Go back to the About menu, you can see the new Developer options menu.
Tap on it, accept the warning.
Toggle on the USB debugging option.
Connect phone, a message appears on phone : Allow USB debugging?
check Always allow and confirm by tapping on OK.
Now, open a Windows command on my "flash" folder (hold Shift + right click on folder -> Open a windows command here).
### Then navigate to my flash folder (if it is on desktop) with this command :
Code:
cd /d C:\djibe\flash
Enter command :
Code:
adb devices
, confirm by pressing Enter.
Command returns :
Code:
List of devices attached
HT35****** device
### If no device is found, uninstall and reinstall properly the drivers while antivirus is off.
### Or start fresh on another PC.
Now type :
Code:
adb reboot bootloader
Authorize ADB commands on phone.
Phone restarts in Fastboot mode. Wait till phone screen is blank in fastboot mode.
Type :
Code:
fastboot devices
Command returns :
Code:
HT35**** fastboot
Type :
Code:
fastboot oem get_identifier_token
, confirm by pressing Enter.
Command returns multiple lines.
Select with your mouse all the lines from
Code:
<<<< Identifier Token Start >>>>
(included)
to the line
Code:
<<<<< Identifier token end >>>>>
(included).
Now on keyboard copy (Ctrl + C combo), then open Notepad.
In Notepad, paste those lines (Ctrl + V combo).
Now manually remove all the (bootloader) strings from each line.
Your notepad should now look like this :
<<<< Identifier Token Start >>>>
37A5DBF4FE5F0D9F4425E54AA91AFDBF
2A20E9C67C3BB4FAE60263F76BDEC6AC
847BF9FFB11DAEA4AB88AC8710435449
9BC12E93DF4C54FFE3D064C4C810C49A
2CDAF2E0CD3A164FED4A568CB0FD2AC6
C01AA991733D949C00987062D691DE91
8AA1C97CEBC3ACE83FECE75A1D03CE72
62414C7DC36A73AFCBF433E1EBE2EDC7
E272F73309632D3EF8C86E472B65E8EF
37E46B52FE3F94FC69D1854CA3DE6F48
C3E10001B233A70B1EAF35134F51FCC6
353E0CC98534E6E60A241A7063D0BE2F
A5B752E75C1C47E6F739BDBE67D024DA
3292A14278247557632639802722A86C
E61424F7666AE085AA9905096FEED1AD
5ECBBD867544E95ABDDA277690B8CB55
<<<<< Identifier Token End >>>>>
Now visit this website : https://www.htcdev.com/bootloader/
Register on the site. Confirm registration with your email.
In the select menu, chose HTC One (M7), click Begin unlock Bootloader button.
Agree to legal terms.
Next page, go to the bottom and click continue to step 5.
In the bottom of this page, in the lower textarea "My Device Identifier Token",
copy and paste the multiple lines you just edited (my example is just above).
Click Submit.
HTC tells you : Token Submitted Successfully.
Open your mailbox (associated to your HTC account).
Copy the Unlock_code.bin file attached to email in my "flash" folder you unzipped.
In Windows command, type :
Code:
fastboot flash unlocktoken Unlock_code.bin
, confirm with Enter.
Command should return :
Code:
unlock token check successfully
Back to phone, press Volume+ to select "Yes, unlock bootloader", then Power button to confirm flash.
Now wait while phone is going to Factory reset.
Don't let Android restart by holding both Power + Volume- to enter bootloader immediately.
FASTBOOT menu is overlined in red.
4) FLASH TWRP RECOVERY
Using the same Windows command prompt, enter :
Code:
fastboot devices
to make sure phone is still available.
Then
Code:
fastboot flash recovery twrp-3.6.1_9-0-m7univ.img
Command returns :
Code:
finished. total time: x.xxxxs
##€ If it fails, tries with a Windows Powershell shell.
Now on phone, press Volume- to select Bootloader, confirm with Power button.
You are back to the booloader screen (UNLOCKED is written on top line), press Volume- to navigate to RECOVERY, and confirm with Power button.
Phone reboots in TWRP recovery.
5) WIPE PARTITIONS
In TWRP, check Never show this screen and Swipe to Allow Modifications.
You land on TWRP Home screen.
Go to Wipe > Advanced wipe.
Select Dalvik, Cache, System, Data, Internal Storage then Swipe to Wipe, go back to Wipe menu.
6) FLASH ROM, GAPPS AND ROOT (OPTIONNAL)
We first have to get our zips on the phone.
Still on TWRP Home screen, tap on Mount > deselect all partitions except Data, then connect phone to PC.
In Windows Explorer, you can see MTP Device, copy the zips of ROM, GApps, Magisk + Magisk Manager right in the Internal Storage folder.
Tap on Disable MTP once copy is finished.
Then back to Home screen, tap on Install > choose lineage*.zip,
(if you don't see the files, tap on Select Storage and make sure Micro SDCard is active)
then Add more Zips -> Magisk*.zip,
then Add more Zips -> bitgapps*.zip,
then Swipe to confirm Flash.
Wait for operation to end (can be long).
When completed successfully, tap on Reboot.
Tap on Do not install when TWRP asks for the app install.
Wait during long first boot.
Setup Android.
7) You can use Backupyourmobile to restore data,
use GPS Status & Toolbox app to enhance GPS fix.
That's it.
Enjoy,
djibe
THANKS --------------
Teams of : TWRP, LineageOS team, tarkzim, zsoerenm, alray, ., Flyhalf205, icxj1, R1ghtC, gimmeitorilltell, All M7/MSM8960 contributors.
Just my 2 cents
Just my 2 cents if it can help
djibe89 said:
- a microSD card (FAT32 format). Copy the zips of ROM, GApps, addonsu and deviceid*.apk (both in my pack) on the root folder of microSD, then insert it in phone.
Click to expand...
Click to collapse
The M7 is not equipped with a mircoSD card slot, only a virtual /sdcard (symlink to /data/media/0) ... So they'll either have to adb sideload or adb push the files to internal memory which is pointless at this stage since it will be wiped during bootloader unlock. Or drag n drop the files using mtp from twrp once it's installed on the phone.
3 ) UNLOCK BOOTLOADER
[...]
Now wait while phone is going to Factory reset.
Setup Android again on next boot.
4 ) FLASH RECOVERY
Now re-enable USB debugging in Android.
Using the same Windows command prompt, type
Code:
adb reboot bootloader
again.
Click to expand...
Click to collapse
You could save a lot of time just force rebooting to bootloader (power + vol down) right after BL unlock/factory reset are completed so you don't have to setup the system you're going to wipe 2 steps later. USB debug anyway isn't required to fastboot flash recovery so it's not like booting back in system is mandatory before flashing recovery.
:good:
@alray : Thank you so much for help.
I'm lazy with baby waking up every night and did some awful copy-paste.
I correct all these right now.
Thanks.
I would highly recommend to use the official downloads of twrp, HTC drivers, roms and so on, you uploaded these files to your google drive and there is stuff in it nobody will ever need. And nobody knows if those files are in original condition. Strange thats the third time this year someone tries to get users to use their stuff (for a five years old device) there are already a lot of guides out there and several thousand people did it several thousand times without problems. Also you wrote that this would be official lineage but its unofficial, and for that there is already a thread here. The other two threads got deleted by mods because they tried to get users to use files from unknown suspects sources. Use android file host and maybe tell in los thread where those files are stored, whats the source and who made it.
saturday_night said:
I would highly recommend to use the official downloads of twrp, HTC drivers, roms and so on, you uploaded these files to your google drive and there is stuff in it nobody will ever need. And nobody knows if those files are in original condition. Strange thats the third time this year someone tries to get users to use their stuff (for a five years old device) there are already a lot of guides out there and several thousand people did it several thousand times without problems. Also you wrote that this would be official lineage but its unofficial, and for that there is already a thread here. The other two threads got deleted by mods because they tried to get users to use files from unknown suspects sources. Use android file host and maybe tell in los thread where those files are stored, whats the source and who made it.
Click to expand...
Click to collapse
Because you are a senior member you know where to download everything.
But everyone is not like you.
So I tried to compile a ready-to-go pack for the newcomers, like I did for many devices by know.
This allows noobs to profit from custom ROMs and don't keep it esoteric.
Like you say, many downloads are just hacks, so I tried to bundle lowest size safe files.
saturday_night said:
I would highly recommend to use the official downloads of twrp, HTC drivers, roms and so on, you uploaded these files to your google drive and there is stuff in it nobody will ever need. And nobody knows if those files are in original condition. Strange thats the third time this year someone tries to get users to use their stuff (for a five years old device) there are already a lot of guides out there and several thousand people did it several thousand times without problems. Also you wrote that this would be official lineage but its unofficial, and for that there is already a thread here. The other two threads got deleted by mods because they tried to get users to use files from unknown suspects sources. Use android file host and maybe tell in los thread where those files are stored, whats the source and who made it.
Click to expand...
Click to collapse
For the official LOS ROM, tell LOS to store official builds. As they don't do it anymore, we must rely on personnal builds.
A lot of guides out there ? Made extensive search for cracking this phone, never found a step by step one.
Five year old device ? Still so good once unleashed. Custom ROMs are for these devices isn't it ?
@djibe89 Might be useful to point out in your opening post that the 20180420 build has DT2W enabled, but I'd like feedback from people with a functional battery if it makes their device reboot or not, similar to issues reported in the original kernel thread. I suspect my battery is on its way out. The 20180416 build is completely stock upstream LineageOS, no DT2W.
Thanks for the credit .
.:B:. said:
@djibe89 Might be useful to point out in your opening post that the 20180420 build has DT2W enabled, but I'd like feedback from people with a functional battery if it makes their device reboot or not, similar to issues reported in the original kernel thread. I suspect my battery is on its way out. The 20180416 build is completely stock upstream LineageOS, no DT2W.
Thanks for the credit .
Click to expand...
Click to collapse
Thanks for your explanations.
Any trouble following this tutorial guys ? How to enhence it ?
802D device supported?
M.Z.F said:
802D device supported?
Click to expand...
Click to collapse
Hi, no idea, does your model has another model name/code ?
djibe89 said:
Hi, no idea, does your model has another model name/code ?
Click to expand...
Click to collapse
Model name & code like?
PRI Version= 4.22_001
PRL Version = 10012
Getting this message: Updater process ended with ERROR: 7 Error installing zip file '/sdcard/lineage-14.1-20180520-UNOFFICIAL-m7.zip'
any help would be appreciated, thank you
I have tried all the custom roms mentioned above i.e. lineage os , Xenonhd and slim7. But non of them installed. It always shows error either this is not for your device , this device is cdwg or unable to mount. Please give me a link for custom rom for my device that is htc one 802d cdwg
Rafay106 said:
I have tried all the custom roms mentioned above i.e. lineage os , Xenonhd and slim7. But non of them installed. It always shows error either this is not for your device , this device is cdwg or unable to mount. Please give me a link for custom rom for my device that is htc one 802d cdwg
Click to expand...
Click to collapse
All the custom roms mentioned above are NOT for your phone variant.There were almost no development for the 802 branch at the peak of it's popularity and I didn't see anything new for this variant in the past 2 years or so. I wouldn't expect a 7.1 roms for this variant...
Maybe you'll have better luck searching on Asian forums
skovatov said:
Getting this message: Updater process ended with ERROR: 7 Error installing zip file '/sdcard/lineage-14.1-20180520-UNOFFICIAL-m7.zip'
any help would be appreciated, thank you
Click to expand...
Click to collapse
Here you have answer:
https://forum.xda-developers.com/showthread.php?t=2522762
---------- Post added at 05:30 PM ---------- Previous post was at 05:20 PM ----------
Hi.
After installing Android 7.1 Google Pay stop working on my phone. I have torn on NFC communication but terminal don't read my card from app. I don't turn on access to root. Any aidia how to solve this issue?
I have an M7 that I would like to update Android on however the above is a bit over my head. I have seen other sites and video showing this to only take a few minutes and not requiring a PC. Am I missing something? I just don't quite understand the process of it all.
Bazooka said:
I have an M7 that I would like to update Android on however the above is a bit over my head. I have seen other sites and video showing this to only take a few minutes and not requiring a PC. Am I missing something? I just don't quite understand the process of it all.
Click to expand...
Click to collapse
Flashing without a PC can be done but not recommended. If something goes wrong (and thrust me, it happens pretty often) you'll be stuck with a bootlooping phone.
The guide at post #1 is all you need, what part exactly do you have problem understanding?
alray said:
Flashing without a PC can be done but not recommended. If something goes wrong (and thrust me, it happens pretty often) you'll be stuck with a bootlooping phone.
The guide at post #1 is all you need, what part exactly do you have problem understanding?
Click to expand...
Click to collapse
Thanks for that. I tried to go through it nice and slow making sure I understood each step. I got to where I needed to open a command window on the "flash" folder to which I must have powershell(?) installed as it gave me that option. After inputting 'adb devices' it listed a device but stated it was offline. This is where I am stuck as the steps after this do not work.
drivers win10
Hi, I have a basic ask. Do you know where to get Win 10 drivers? I can't run the installer HTCDriver_4.2.0.001 on my Windows 10 (version 1803).
It gives me the error: The driver installer is not supported for your operating system. Thanks for your help.
Related
Code:
/*
*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
*/
IMPORTANT: Read the ENTIRE instructions set before starting, make sure you know what you are getting into. I have been as straight forward as possible with my instructions to assist noobs with the procedure.
Mission Statement
The purpose of this post is to combine the following 4 guides, in an easy to read manner to help people get from a stock Note 4 Version running 6.0.1 to a fully rooted Note 4 running CM13.0
Guides Referenced and Summarized:
[Guide] A noob's guide to Perm Root & TWRP on Verizon Note 4 Retail 5.1.1 (BPA1) http://forum.xda-developers.com/note-4-verizon/general/guide-noobs-guide-to-perm-root-twrp-t3360883
[HOWTO] Bootloader Unlock and Upgrade to Marshmallow [N910V] http://forum.xda-developers.com/not...t/howto-bootloader-unlock-upgrade-to-t3398144
(no title, sub post #1403, describes going from CPD1 to Jasmine with CPF3 and Firmware/Kernel Patch) http://forum.xda-developers.com/showpost.php?p=67481370&postcount=1403
[ROM] [6.0.1] [UNOFFICIAL] CyanogenMod 13.0 [Jul 24, 2016] http://forum.xda-developers.com/note-4-verizon/development/cyanogenmod-t3253973
I will use large chunks from some of these guides, skip some parts not necessary and/or extrapolate/modify on the instructions given within.
Thankx & Achnologments
Main Contributors (I plagiarized, quoted, or sourced)
Robots_Never_Die
hsbadr
Tech Support
BickNasty
Feel like I missed you, it wasn't intentional....PM me and I'll consider adding you, if I feel you actually contributed in some way or I copied your work.
Satisfied Customers (Did my method work for you? Post a reply and let us know, I'll add you to the list)
jwp1299 - 1 hour
Viper-Link
keviinese - 1.5 hours
pfcland - 1.5 hours
Required Apps (Google Play) All Free
Search for and install these apps
eMMC Brickbug Check (free)
Required Downloads (note on version numbers: version numbers I specify are ones available at the time I wrote this guide. For most tool grab the newest version, such as Odin/ADB)
NOTICE Total size of Downloads is approximately 7 GB, some of the links may be slow! Time required may vary due to your network speeds, and luck with speeds from file hosts. (expect several hours)
ADB – minimal_adb_fastboot_v1.4.0_setup.exe
Odin - newest version (3.12.3 at time of writing)
Kingroot - Grab latest stable version, only grab NewKingroot(XXXXX).apk
Samsung USB drivers (windows) - newest version
Bootloader Unlock - samsung_unlock_n4-fix
TWRP - twrp-3.0.2-0-trltevzw.tar.md5
N910VVRU2BPA1_N910VVZW2BPA1_VZW.tar.md5
N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar.md5 (Alternate Torrent if slow: Torrent started by pfcland)
JasmineROM_v7.0_N910VVRU2CPF3.7z
N910VVRU2CPF3_PartialFirmware_PatechedKernel.tar.m d5.7z
Gapps For ARM SDK23 (Android 6.0) (mini version is recommended)
UNOFFICIAL CyanogenMod 13.0 Builds for Verizon Samsung Galaxy Note 4 (SM-N910V) (grab newest from top)
Xposed framework for ARM SDK 23 (NOTE: Grab both the xposed23.zip and XposedInstaller****.apk)
XPosed is OPTIONAL, but there are a lot of rooted apps that use the XPosed framework to get more control over your phone. Such as hiding mock locations for example.
NOTE: Internet is REQUIRED for KingRoot to function (grants temporary root, so ADP commands can be executed to unlock bootloader), at one point WiFi will NOT function but internet is still required. So a valid SIM with internet is required (Verizon will definitely work, others might[/] work)
NOTE: The entire installation will take an estimated 1-2 hours. (Not including time spent downloading) All steps are MANDATORY, do not SKIP anything....You've been warned
Install eMMC Brickbug Check (free) on your phone, and RUN IT. Your CID MUST start with 15. If it doesn't I can't help you, and this guide is not for you.
Install the Samsung USB drivers on your windows PC
Backup your phone, if you don't know how.....google it...And learn how, you will want to backup frequently. Every time you get to a point you can boot up into Android, backup...it's safer for you...I will not remind you again, this is on your head.
Disable Encryption on your phone, both the SD card and Device
Disable Samsung Phone Lockout. YOU MUST DO THIS OR ELSE!!!! (Settings > Security > Reactivation Lock)
Do 2 factory resets on your phone, one after another (hold volume up, home button, power when starting to enter recovery mode where you can reset phone). Not required but if you don't, you'll spend an extra hour or two doing this because Kingroot will crash/fail more often.
Boot up your phone in Download Mode (hold volume down, home button, power)
Open Odin3, Click the AP button and select the file N910VVRU2BPA1_N910VVZW2BPA1_VZW.tar.md5, once it checks it, goto options and make sure the Re-Partition is NOT selected. Now click start to flash and downgrade to Android 5.1.1.
Turn on your phone, and let it boot up.
Skip everything possible when setting up your phone. Don't even put in a google account, not necessary
Goto Setings and set the following
Settings > Security > Reactivation Lock = Disabled (EXTREMELY IMPORTANT, VERIFY)
Settings > Security > Unkown Sources = Enabled
Settings > Developer Options > USB debugging = Enabled
Developer options are unlocked by going to Settings > About Phone. Find "Build Number", and start clicking it till you get a message that Developer Options have been unlocked (about 10 clicks I believe, never counted).
Settings > Developer Options > Verify App via USB = Enabled (should be by default, CHECK)
Settings > Lock Screen = None
Settings > Display > Turn off Display = 10 Minutes
Plug your phone into your computer via USB, copy the NewKingroot****.apk to your download directory (samsung-sm-N910V\Phone\Download)
Install ADB onto your Windows PC. Select an easy directory such as c:\ADB
Copy the following file directly into the ADB directory
samsung_unlock_n4-fix
Open up command line interface. Hold windows key & press R key for run, type in "cmd" press enter. Will open a terminal window for you. Type the following commands:
cd\
cd adb (or whatever you named your directory where you installed ADB)
adb devices
This should return a list of devices you have connected, something like:
Code:
List of devices attached
SerialNum device
If no devices are displayed, check you have the Samsung USB drivers installed properly.
Type the following command
adb push samsung_unlock_n4-fix /data/local/tmp/
Got an error? check your spelling (or copy/paste from me), check you put the file into the ADB directory (not just a link), your phone must be on and screen not locked and check you have usb debugging enabled.
BTW: Do NOT CLOSE the window unless I instruct you to!
Install Kingroot on your phone, which you previously moved into your downloads folder, you can find it via My Files app that comes with phone.
Now run KingRoot. Flip down to the bottom and click "Try It", it will run some quick test then give you a button to try to root your phone.
Wait...Wait...Do not worry if your phone restarts, it will go back into KingRoot automatically on reboot. Just sit back and wait, it may fail multiple times and you may have to re-run Kingroot. Just keep trying . Once it succeeds you must do the following IMMEDIATELY AND AS FAST AS POSSIBLE. Kingroot is HIGHLY UNSTABLE.
On the windows PC, back in the command window you left open. Start Typing.
adb shell
su
cd /data/local/tmp/
chmod 777 samsung_unlock_n4-fix
chown root.root samsung_unlock_n4-fix
./samsung_unlock_n4-fix
After the last command it may prompt you to type yes, do so immediately. it won't write on the screen but type yes anyway for it to continue. Once it's done it should automatically start to reboot your phone. Unplug it and pull the battery, wait 5 seconds, put battery back in and plug the phone back in.
This was the initial setup for unlocking your bootloader, you now have to run it AGAIN so turn your phone back on. Repeat steps 22-24, after the 2nd time PULL OUT YOUR SD CARD BEFORE TURNING ON YOUR PHONE
Congratulations you now have an unlocked bootloader, you can close the command window on your PC.
The SD card has a restore point for your phone prior to removing your bootlock. Save it if you want, or plug into your phone and format the 18mb partition you are able to. You must format it on a PC before you can use it again in a phone!!!! Will shut your phone off immediately if you put the SD in without formatting that 18mb partition.
Now reboot your phone into download mode (hold volume down, home and power buttons when turning on)
Open Odin App on your PC, Click the "AP" button and select the file twrp-3.0.2-0-trltevzw.tar.md5 (which you downloaded earlier). Once it does it's check, verify that re-partition is NOT selected in options. Now click start to flash twrp bootloader.
Your phone will restart, re-enter download mode. If you missed it pull cable/battery and try again.
Now extract and flash N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar.md5 via Odin, same as you did with twrp. VERIFY THAT RE-PARTITION IS NOT SELECTED IN OPTIONS.
Boot up in recovery mode (hold volume up, home and power when turning on) (note: no longer TWRP since you flashed firmware, will look different again)
"Wipe data/factory reset ", then reboot your phone.
Now repeat steps 9-12 (NewKingRoot should still be in your downloads, but verify anyway) (NOTICE: wifi will NOT work with the CPD1 firmware, but Verizon internet should in case you need internet for some reason, wifi will restore later in guide - Other internet from other providers MIGHT work with proper APN settings)
Install a clean SD card into the phone.
Now repeat steps 15-25. This time you should only need to run the samsung_unlock_n4-fix file once to break your boot. This is what it typically says on successful bootloader unlock: (if you got this message, pull the battery, cable and SD card.)
Code:
[email protected]:/ # cd /data/local/tmp/
[email protected]:/ # chmod 777 samsung_unlock_n4-fix <
[email protected]:/ # ./samsung_unlock_n4-fix
============================== samdunk unlock 0.0.1 ==============================
NOTE 3 BETA UNLOCK!!!!!!!!!!!!!
this application comes with NO WARRANTY (express or implied)
this binary may not be rehosted, repackaged, one-clicked, etc.
there is no support provided for this application
this application has been tested on the Verizon Galaxy S5 only
it may work on the AT&T Galaxy S5, and possibly other similar Galaxy devices
there are no compatibility checks, do your research first
if run on an incompatible phone, it will likely permanently ruin the device
we STRONGLY advise against running any binary not obtained from the official source
official source is available at http://github.com/beaups/SamsungCID
SD card is required, all data on the SD card will be destroyed
changing to this developer CID may have other implications
the psn derived from the CID may be used for critical services
changing this psn may cause unexpected behavior or loss of services
continue at your own risk, you've been warned
aboot dev signature research credit to ryanbg
http://forum.xda-developers.com/member.php?u=766721
eMMC vulnerability, exploit, and the code you are running by beaups (sean beaupre)
http://forum.xda-developers.com/member.php?u=711482
Do you understand the implications of these warnings?
(Yes/No)
[+] CID at boot time is/was: 150100523231384d4100657e54fc1200
[+] dev CID matching, proceeding to unlock
[+] backing up loaders, this will take a few minutes
[+] loaders successfully backed up
[+] success! powering off device, hopefully its not bricked!
Now boot back into download mode
Flash TWRP via Odin again (I'm summarizing greatly now, as you should by now understand this kind of shorthand)
Ok, now boot up into TWRP recovery mode (vol up, home, power)
Navigate through TWRP menus to create a Backup. Click Backup Button, and swipe to create backup. (this is just so that it creates the directory structure on your phone)
Click the Reboot System button, skip all the setup you can again. (DO NOT INSTALL SUPERSU!!! will cause bootloop)
Extract the "JasmineROM_v7.0_N910VVRU2CPF3.7z" file it will create a directory called "JasmineROM_v7.0_N910VVRU2CPF3".
Plug USB into phone and to computer. Copy the JasmineROM_v7.0_N910VVRU2CPF3 folder into \Internal storage\TWRP\BACKUPS\Phone SN\
Reboot into TWRP recovery
Click the Restore button (DONT start the restore yet!!!), and check that your JasmineROM is listed as a recovery option. (don't recover YET) If it's not there you copied it into the wrong directy, try again before proceeding.
Go back to the main menu, Click the Wipe button. Click the 'Advanced Wipe' button, and wipe the following cache/dalvik/system/data
Go back to Restore (from 2 steps ago) and run the JasmineROM_v7.0_N910VVRU2CPF3 recovery, return to main menu afterwards
Go to wipe, and wipe the cache/dalvik only this time.
Reboot into download mode
Flash the N910VVRU2CPF3_PartialFirmware_PatechedKernel.tar.m d5.7z file via Odin
Reboot the system, this will take a LONG TIME. WAIT for it. (if reboot takes >10 min, pull battery and restart)
Once it boots up, skip all the setup again. Copy the CM13, Gapps and XPosed (both zip and apk) to your downloads. Don't unzip anything, not necessary.
Now reboot into recovery go to WIPE and do a factory reset by swiping.
Then goto Install (still in recovery) and install CM13, then Install Gapps.
Reboot your phone, this time you are setting up properly reboot will take a while to optimize your apps depending on Gapps version used. So do all your setup as you want your phone setup. Once that's done, restart the phone in recovery. (if reboot takes > 5 min, pull battery and restart)
Install via TWRP the XPossed.zip file.
Reboot your phone, once on. Navigate via My Files, to downloads and install XPosed.apk
CONGRATULATIONS. You now have a fully Unlocked, Rooted Note 4 Verizon with CryanogenMod 13.0 installed and XPosed Installed.
Suggested Apps
Kernel Auditor [ROOT], will allow you to adjust kernel settings. Such as CPU clock speeds and thermal throttling, if your phone is too hot.
Note: About ROOT[/], you will have root once you finish this guide. But it is disabled by default, you can enable root in developer options (no reboot required when changing). Unlock your developer options again, and scroll down you will see an option to enable/disable root. This allows you to keep turn off during normal use, and only enable it when you need to install an app that requires root. You can always just leave it on all the time, that is your choice.
Note: Some apps on Google PlayStore will become unavailable due to incompatibility (according to google, HA). Such as YouTube Music, you will no longer be able to install it through the store. But you can install it by using an APK site, such as APK Downloader. On this site you find the app you want on play.google.com, copy the HTTP link and put it into the APK Downloader and it will generate a direct download link to the APK file. Copy onto your phone and sideload (ie. install) through file explorer. I don't endorse them, they are just one of many places you can get APK files.
Change Log
7/28/2016
Another success story :good:
Added note about how root works in CM 13.0
Corrected Step 34
Minor text adjustments, for clarification
Made note that wifi doesn't work with CDP1 flash
Added note that you MUST HAVE a valid sim card with internet access for step 35! KingRoot requires internet to function, and Wifi will NOT WORK after flashing CPD1 firmware (incomparable drivers).
Added another note about internet at the top of the instructions, to make sure people are aware.
7/27/2016
Added Bicknasty to the Contributors list - helped resolve issues I had with CM 13.0 kernel & modem.
Added a note to downloads section regarding total size of files downloaded and expected time.
Re-wrote steps 40-48 to make it easier to understand. Adding some steps and explaining in more detail.
Added note at the top to read ALL the instructions once before starting
Added note with the estimated time to perform all the steps
Added note suggesting Kernel Auditor app, and made reference to the fact that some apps on playstore will NOT install from playstore. Suggested APK Downloader for apps not available from store
Added a Success Story Section
Added note on how to enable developer options
Any faster source for N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar.md5
jwp1299 said:
Any faster source for N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar.md5
Click to expand...
Click to collapse
Probably, but that's the only one I know which is a free download that I'd trust.
JacekRing said:
Probably, but that's the only one I know which is a free download that I'd trust.
Click to expand...
Click to collapse
Alright, still works just a little long. Thanks so much for the guide, working great so far!
jwp1299 said:
Alright, still works just a little long. Thanks so much for the guide, working great so far!
Click to expand...
Click to collapse
How far are you now?
And let me know when you finish, critique my guide. If parts weren't clear enough let me know.
And finally if you run into any issues let me know.
Great guide (I honestly haven't read it, it's too long but it looks thorough, and I know you were annoyed with the tedious process), glad I was able to help you figure things out!
Bicknasty said:
Great guide (I honestly haven't read it, it's too long but it looks thorough, and I know you were annoyed with the tedious process), glad I was able to help you figure things out!
Click to expand...
Click to collapse
Yea I do appreciate the help Bicknasty. I'll add you to contributors list later as helping with cyanogen issues I was having.
Bicknasty said:
Great guide (I honestly haven't read it, it's too long but it looks thorough, and I know you were annoyed with the tedious process), glad I was able to help you figure things out!
Click to expand...
Click to collapse
You know it wasn't so much that it annoyed me it's that there was no concrete guide telling me what to do. It's a thread here, a post there to do a specific thing but they aren't coordinated in a logical way for users to easily find.
Alright ignore what I said before this edit, I just skipped a step.
I must say though, steps 41-43 are very confusing. What is the ROM folder?
jwp1299 said:
Alright ignore what I said before this edit, I just skipped a step.
I must say though, steps 41-43 are very confusing. What is the ROM folder?
Click to expand...
Click to collapse
The ROM folder I'm referring too is the folder inside the Jasmine zip file. I only reference it so people wouldn't try to take just the files inside the folder which is inside the zip file. Lol yea that's confusing....I'll think about how to rewrite those and make adjustments in a couple hours to make it clearer.
But basically when you extract the Jasmine zip file it creates a folder with files in it. Copy the whole folder not just the files to where it makes your recovery folders.
JacekRing said:
The ROM folder I'm referring too is the folder inside the Jasmine zip file. I only reference it so people wouldn't try to take just the files inside the folder which is inside the zip file. Lol yea that's confusing....I'll think about how to rewrite those and make adjustments in a couple hours to make it clearer.
But basically when you extract the Jasmine zip file it creates a folder with files in it. Copy the whole folder not just the files to where it makes your recovery folders.
Click to expand...
Click to collapse
Okay, awesome. Also I think the TWRP part could be explained a little clearer.
Other than that, 100%
oh also, at the start I would say to read the entire thing before starting, and give a warning that downloads will take like 4 hrs
jwp1299 said:
Okay, awesome. Also I think the TWRP part could be explained a little clearer.
Other than that, 100%
oh also, at the start I would say to read the entire thing before starting, and give a warning that downloads will take like 4 hrs
Click to expand...
Click to collapse
Lol yea, didn't think to mention reading the whole thing first. To me that's a given I always read everything before starting. I'll add a note to read everything.
As to download time, well it is like what 12 gigs in total? Basically 4 full versions of the Android OS at 2 gigs reach plus all the extras.
I'll try to see if I can't explain the twrp recovery of Jasmine better. Only reason you need to do Jasmine is for the 6.0.1 device drivers (such as modem).
jwp1299 said:
Okay, awesome. Also I think the TWRP part could be explained a little clearer.
Other than that, 100%
oh also, at the start I would say to read the entire thing before starting, and give a warning that downloads will take like 4 hrs
Click to expand...
Click to collapse
I've modified the guide appropriately, to resolve all of the issues (I think) you mentioned. And to make some steps easier to understand and follow.
I also added a recommended app on the bottom, and mentioned a site you can use to get PlayStore apps which will now list as incompatible with our phones.
Finally, question: Did you succeed using this Guide? Just curious if everything is working as expected after following my guide. I wrote the thing from memory, after spending 3 days rooting my phone and figuring everything out from various sources. Hopefully this saves people some time where they don't have to piece a dozen sources together to figure out how to do it. I only mentioned the main 4 I referenced, but there were other lessons learned from various places that aren't covered in those posts.
JacekRing said:
I've modified the guide appropriately, to resolve all of the issues (I think) you mentioned. And to make some steps easier to understand and follow.
I also added a recommended app on the bottom, and mentioned a site you can use to get PlayStore apps which will now list as incompatible with our phones.
Finally, question: Did you succeed using this Guide? Just curious if everything is working as expected after following my guide. I wrote the thing from memory, after spending 3 days rooting my phone and figuring everything out from various sources. Hopefully this saves people some time where they don't have to piece a dozen sources together to figure out how to do it. I only mentioned the main 4 I referenced, but there were other lessons learned from various places that aren't covered in those posts.
Click to expand...
Click to collapse
I was quite successful with the root. Even though I messed up a few times (skipping steps), it all works out and now it's working lovely. It only took an hour of actual work, plus a lot of download time because of slow hosts.
Thanks so much for the guide, the only issue was with the slow hosts, and that's hardly your fault. I do wonder if maybe setting up a torrent of the heavier files might help though.
Edit: I will say, this is a wonderfully tedious root effort.
jwp1299 said:
I was quite successful with the root. Even though I messed up a few times (skipping steps), it all works out and now it's working lovely. It only took an hour of actual work, plus a lot of download time because of slow hosts.
Thanks so much for the guide, the only issue was with the slow hosts, and that's hardly your fault. I do wonder if maybe setting up a torrent of the heavier files might help though.
Edit: I will say, this is a wonderfully tedious root effort.
Click to expand...
Click to collapse
An hour..........I spent 2 hours watching kingroot try and root my damb phone, LOL because I didn't wipe before trying to get temporary root the first time you use it (before I read in a post that wiping twice will make it MUCH more successful). Took me 10+ hours of actual work to get my phone rooted and CM 13.0 setup, because I didn't have steps to follow, LMAO. Made it up as I went.
As to the Torrent, I'd be the only one sharing and my upload speeds are not that great. maybe 500 kbps, I live in a rural area. At least my download speed is 40 mbps.
And it is hellofa tedious root for the Note 4, I haven't seen any other phone as crazy tedious to root.
Edit: Mind if I add a 'success story' section and add you to it?
JacekRing said:
An hour..........I spent 2 hours watching kingroot try and root my damb phone, LOL because I didn't wipe before trying to get temporary root the first time you use it (before I read in a post that wiping twice will make it MUCH more successful). Took me 10+ hours of actual work to get my phone rooted and CM 13.0 setup, because I didn't have steps to follow, LMAO. Made it up as I went.
As to the Torrent, I'd be the only one sharing and my upload speeds are not that great. maybe 500 kbps, I live in a rural area. At least my download speed is 40 mbps.
And it is hellofa tedious root for the Note 4, I haven't seen any other phone as crazy tedious to root.
Edit: Mind if I add a 'success story' section and add you to it?
Click to expand...
Click to collapse
Oh of course, go ahead and add me.
Also, if you do end up making a torrent, i'd be happy to help seed at least for a while. I have pretty good upload and no data caps or anything so it would probably help a bit (anything is faster than that 100 kbps that xda was giving)
You called N910VVRU2BPA1_N910VVZW2BPA1_VZW.zip, "N910VVRU2BPA1 Full Firmware". Which kinda got me confused, (maybe its just me trying to do this at 1 am >_>) but might want to edit that. Other then that Iv'e had a pretty easy time following this guide. Thanks! (still doing it fyi, I got an infinite bootloop, so figured I messed up somewhere after reflashing TWRP, now im starting from scratch.)
I have a Very weird problem , I followed your instructions correctly i was on step 25 did exactly what you said pulled the unpluged the USB and pulled the battery and and waited 5 seconds and put the battery back in and rebooted the phone only problem is now it is stuck in a boot loop of the image Samsung galaxy note 4 and just keeps rebooting . I haved tryed doing a factory reset and wiping cache and reinstalling 5.1..1 via odin and it is still doing the boot loop i am not sure what i did wrong or what to do . I know its not hard brick because i can get into recovery and download but just wont boot the past the Samsung not 4 logo
---------- Post added at 05:05 AM ---------- Previous post was at 04:57 AM ----------
Ok so i went and wiped and factory rest like 10 times and now it got past the screen So that is a relief lol
Viper-Link said:
You called N910VVRU2BPA1_N910VVZW2BPA1_VZW.zip, "N910VVRU2BPA1 Full Firmware". Which kinda got me confused, (maybe its just me trying to do this at 1 am >_>) but might want to edit that. Other then that Iv'e had a pretty easy time following this guide. Thanks! (still doing it fyi, I got an infinite bootloop, so figured I messed up somewhere after reflashing TWRP, now im starting from scratch.)
Click to expand...
Click to collapse
Not sure what to tell you viper as not enough info. Hope you figured it out...
pfcland said:
I have a Very weird problem , I followed your instructions correctly i was on step 25 did exactly what you said pulled the unpluged the USB and pulled the battery and and waited 5 seconds and put the battery back in and rebooted the phone only problem is now it is stuck in a boot loop of the image Samsung galaxy note 4 and just keeps rebooting . I haved tryed doing a factory reset and wiping cache and reinstalling 5.1..1 via odin and it is still doing the boot loop i am not sure what i did wrong or what to do . I know its not hard brick because i can get into recovery and download but just wont boot the past the Samsung not 4 logo
---------- Post added at 05:05 AM ---------- Previous post was at 04:57 AM ----------
Ok so i went and wiped and factory rest like 10 times and now it got past the screen So that is a relief lol
Click to expand...
Click to collapse
Was this after the first time you inputted the adb commands our second? Make sure you pull the SD card after the second time, as it will cause reboots after the second time until you reformat the SD card on your PC. Size will be wrong on PC but size will fix when you reformat the SD card a second time on your phone.
Edit it creates like 20 partitions on the ad card when you do adb, it creates a backup of your phone os.
OK, so there's a post nearly identical to this, with the CLEAR exception of it being specific to Android 6.x (Marshmallow). For that thread, go HERE.
DO NOT ATTEMPT ANY OF THE BELOW STEPS ON MARSHMALLOW. THIS IS FOR ANDROID 7.X (NOUGAT ONLY)
OK, quick backstory. Like the other link, none of this is my work and all the people whom I've worked with and confirmed each step of these instructions are working and validated are here:
spotting, clsA, Atarii, faizalotai, BonezMontana, schluk and Sheldd. This is NOT my work, this is the combination of all these guys help. Thank them! If you need any help, please post here. I'll help the best I can, but I've got a 15 month old and between changing diapers and RAGING FITS due to lack of Cheddar Goldfish, I spend my side time flashing like crazy. PLEASE assume all risk and responsibility when following the instructions below. If you mess up, ask for help. I'm not liable. Neither are the guys you should be thanking above for this!
Cheers!
This process assumes the following: You're on stock Android 7 (Nougat) with no modifications.
Basic steps are:
1. Unlock the bootloader
2. Flash TWRP
3. Flash SuperSU
4. Fix your BT/NFC (if you have issues)
5. There is extra instruction here as well for AdAway and V4A (Viper4Android)
Unlock the bootloader
Follow this link to unlock your bootloader.
1. Go to Huawei's EMUI site and log in. If you need to create a new account, do so. Link here: http://www.emui.com/en/plugin/hwdownload/download
2. Click on the DOWNLOAD link at the top of the site.
3. Underneath the search field you will see a green link that says "Unlock Bootloader". Click it and follow the instructions. You will be asked to enter in several pieces of information about your phone.
4. Once you've filled out all the information, you will receive your unlock code at the bottom of the screen. Write this down and save it. This number will NEVER change.
5. On your Honor 8, go to Settings > About and tap on the Build Number seven times until you unlock the Developer Settings.
6. In Developer Settings, check Enable OEM Unlock.
7. Scroll down a bit more and check USB Debugging.
8. Go to Huawei's site and download their HiSuite and install it. This installs the OFFICIAL Honor 8 USB driver. Link here: http://consumer.huawei.com/minisite/..._en/index.html Once the app is installed, you can unselect start with Windows under settings.
9. Plug in your Honor 8 with the provided USB cable. Give it about 45 seconds to install the driver and recognize it. You may need to go to your phone and tap on "Allow File Access". You will be presented with a question asking if you'd always like to trust the computer you just connected to. Select yes, if this is your primary computer you will be working with.
10. Now download the most up to date ADB drivers. A Google employee has created one link to get that and make it easy. Link here: https://developer.android.com/studio...orm-tools.html
11. Open the zip file you just downloaded and create a folder on your computer easy to get to (I recommend c:\ADB) and paste those files there so they are extracted.
12. Now open the folder up in Windows Explorer if you closed it and hold down the Shift key and RIGHT click in the open area and click "Open command window here"
13. Type adb devices and hit enter. You should see a device ID as a response in the window.
14. Type adb reboot bootloader and hit enter. Give it a couple of seconds and the phone will load the bootloader.
15. Now type fastboot devices and hit enter. You should see your device ID appear again.
16. LAST CHANCE before it wipes everything and unlocks the booloader!!! Type fastboot oem unlock XXXXXXXXXX (where XXXXXXXXXX is the unlock code you received on step 4) and hit enter. It will ask if you're sure. Once this is done, the phone will wipe your data, unlock the phone and reboot. Your Honor 8's bootloader is now unlocked.
Click to expand...
Click to collapse
Flash TWRP
Grab a working copy of TWRP here.
1. Download TWRP into the same folder you used in the steps above (where you're keeping all your files)
2. Navigate in Windows Explorer to this location and hold down the Shift key and RIGHT click in the open area and click "Open command window here"
3. Type adb devices and hit enter. You should see a device ID as a response in the window.
4. Type adb reboot bootloader and hit enter. Give it a couple of seconds and the phone will load the bootloader.
5. Now type fastboot devices and hit enter. You should see your device ID appear again.
6. Type fastboot flash recovery frd-twrp.img and hit enter.
7. Once this is complete, unplug your phone.
8. Hold Volume UP and Power at the same time. Release ONLY the Power button after the blue Honor logo appears.
9. You now are booted into TWRP and it's been successfully flashed.
Click to expand...
Click to collapse
Flash SuperSU
Download the SuperSU SPECIFICALLY FOR NOUGAT here.
1. Boot into TWRP
2. Once there, when asked to keep system read only? - swipe to allow modifications
3. Tap Install
4. Tap Select Storage - Select your SD card
5. Select the supersu file "SuperSU-v2.79-201612051815-EMUI5.0.zip"
6. Swipe to confirm flash
7. Ignore the multiple errors: "Failed to mount '/data' (Invalid argument)
8. Go back to the main menu
9. Select Reboot to Recovery
10. When asked to keep system read only? - swiped to allow modifications (again)
11. Tap Wipe
12. Tap Format Data
13. Type YES then hit enter
14. It will format data using make_ext4fs..
15. When finished, tap Reboot System
16. Reboot back into TWRP
17. Swipe to allow modifications (You can check the box to never show this again)
18. Tap Install
19. Select storage
20. Select your SD card
21. Select the supersu file "SuperSU-v2.79-201612051815-EMUI5.0.zip"
22. Swipe to confirm flash
23. You should see NO ERRORS now when installing SuperSU
24. Wipe cache/dalvik
25. Swipe to wipe
26. Reboot system
Click to expand...
Click to collapse
Fix your BT/NFC (if you have issues)
Some people are stating that after flashing this fix that they lose their keyboard. I'm throwing up a link here to get the latest GBoard.apk file.
Follow these instructions to fix BT/NFC issues.
This file is for the FRD-L04 ONLY.
Instruction for AdAway
Follow these instructions to get AdAway working. This is only instruction, NOT where to download. I suggest F-Droid. Use Google.
Instruction for V4A (Viper4Android)
Follow these instructions to get Viper working on Nougat.
How multiple people have successfully gone back to MM if they have too many issues with Nougat.
Follow these instructions to get back to MM. Breathe.. it's actually not that bad at all.
You can find the OFFICIAL files to download on the Honor Support site located HERE.
Hi, i suggest removing the code tags and add the quote one instead so that people wont have to scroll down and scroll sideways too
Thanks for the sum-up! This thread gave me enough confidence to tweak my Honor8 on Nougat.
I'll try to get Adaway tonight, and will report any problems
EDIT: After flashing the update_data_full_hw_usa.zip to get BT and NFC, I only got NFC back. Can't turn on BT.
I reformated data to f2fs and reflashed supersu then update_data_full_hw_usa.zip but it's even worse, I don't have NFC. @joesee, any idea what went wrong?
=> considering a rollback now...
I already have 2 zips for viper which just needs to install and then set selinux to permissive and no struggle with installation if u have busy box
Sent from my NATASHA using Tapatalk
LastStandingDroid said:
I already have 2 zips for viper which just needs to install and then set selinux to permissive and no struggle with installation if u have busy box
Sent from my NATASHA using Tapatalk
Click to expand...
Click to collapse
Yeah, there were a lot of people including myself that had issues with that not working unless we renamed that audio_effects.conf file. To test, I even tried the standard apk file to try to install because I really hate the new EQ layout of the version 2.5. It is such a pain in the butt to scroll over just to adjust a frequency!
trainpunk said:
Hi, i suggest removing the code tags and add the quote one instead so that people wont have to scroll down and scroll sideways too
Click to expand...
Click to collapse
That's the one I was actually trying to do but I've never posted anything extravagant like that on here haha. Thanks!
takichiman said:
Thanks for the sum-up! This thread gave me enough confidence to tweak my Honor8 on Nougat.
I'll try to get Adaway tonight, and will report any problems
EDIT: After flashing the update_data_full_hw_usa.zip to get BT and NFC, I only got NFC back. Can't turn on BT.
I reformated data to f2fs and reflashed supersu then update_data_full_hw_usa.zip but it's even worse, I don't have NFC. @joesee, any idea what went wrong?
=> considering a rollback now...
Click to expand...
Click to collapse
Well I've went through this process three times myself back when I was trying to figure it out. There's at least two other threads that say the data partition needs formatted to f2fs. I don't know if the formatting of the data partition has anything to do with it or not to be honest because right now my data partition is ext4 and I don't have issues. Before you roll back, try doing a factory reset and just letting that process reformat on it's own and see if that resolves. If it does, I'll update the OP and just take that part out.
It was only put there because several people said that it was a better format and more efficient, so I'm not sure!
joesee said:
Well I've went through this process three times myself back when I was trying to figure it out. There's at least two other threads that say the data partition needs formatted to f2fs. I don't know if the formatting of the data partition has anything to do with it or not to be honest because right now my data partition is ext4 and I don't have issues. Before you roll back, try doing a factory reset and just letting that process reformat on it's own and see if that resolves. If it does, I'll update the OP and just take that part out.
It was only put there because several people said that it was a better format and more efficient, so I'm not sure!
Click to expand...
Click to collapse
After the factory reset, NFC is back, but BT cannot be turned on.
From what I understood, do I need to make sure to have an ext4 data partition to rollback to MM ?
Thanks for the answer
takichiman said:
After the factory reset, NFC is back, but BT cannot be turned on.
From what I understood, do I need to make sure to have an ext4 data partition to rollback to MM ?
Thanks for the answer
Click to expand...
Click to collapse
I had a conversation with the guy in this thread: https://forum.xda-developers.com/ho...ing-nougat-t3550015/post70859564#post70859564 While he says you really should - I didn't, and had no problems at all with it. Your mileage may vary.
joesee said:
I had a conversation with the guy in this thread: https://forum.xda-developers.com/ho...ing-nougat-t3550015/post70859564#post70859564 While he says you really should - I didn't, and had no problems at all with it. Your mileage may vary.
Click to expand...
Click to collapse
Okay thank you.
Just for information, it looks like my firmware version is now B320 while I had the B360 before. Probably due to the flashing of update_data_full_hw_usa.zip
Regarding the rollback procedure (which I'm doing for the 1st time), while everybody mention that i should put the dload folder in the sdcard, the huawei pdf document indicates that I should put it in the internal storage
Is huawei mistaken or am I mixing things?
takichiman said:
Okay thank you.
Just for information, it looks like my firmware version is now B320 while I had the B360 before. Probably due to the flashing of update_data_full_hw_usa.zip
Regarding the rollback procedure (which I'm doing for the 1st time), while everybody mention that i should put the dload folder in the sdcard, the huawei pdf document indicates that I should put it in the internal storage
Is huawei mistaken or am I mixing things?
Click to expand...
Click to collapse
Right now there's too many version of data full.zip, your's because of older version of full data.zip..
Just make sure its around 0.88mb for b360..
takichiman said:
Okay thank you.
Just for information, it looks like my firmware version is now B320 while I had the B360 before. Probably due to the flashing of update_data_full_hw_usa.zip
Regarding the rollback procedure (which I'm doing for the 1st time), while everybody mention that i should put the dload folder in the sdcard, the huawei pdf document indicates that I should put it in the internal storage
Is huawei mistaken or am I mixing things?
Click to expand...
Click to collapse
Either or will work for the dload folder. I've flashed both actually. Might be better to put it on the SD instead of internal so it's easier to format. Your choice, really.
Regarding the firmware versions, I think the OTA brought it up to 360 and that update data is a zip created from 320. Don't quote me on that, though.
joesee said:
Either or will work for the dload folder. I've flashed both actually. Might be better to put it on the SD instead of internal so it's easier to format. Your choice, really.
Regarding the firmware versions, I think the OTA brought it up to 360 and that update data is a zip created from 320. Don't quote me on that, though.
Click to expand...
Click to collapse
faizalotai said:
Right now there's too many version of data full.zip, your's because of older version of full data.zip..
Just make sure its around 0.88mb for b360..
Click to expand...
Click to collapse
Following what @faizalotai said, I will find a data update for the B360 and try and flash it and see what happens.
takichiman said:
Following what @faizalotai said, I will find a data update for the B360 and try and flash it and see what happens.
Click to expand...
Click to collapse
I'd be curious to know because I'm on b320 right now. I haven't tried making a backup of my current ROM yet. I hope it doesn't fail. I've never been able to backup MM.
joesee said:
I'd be curious to know because I'm on b320 right now. I haven't tried making a backup of my current ROM yet. I hope it doesn't fail. I've never been able to backup MM.
Click to expand...
Click to collapse
Sadly, it didn't work. I was in that case in which I have no keyboard, no apps and so on...
So I rollbacked to MM using Huawei's official packages.
If anyone needs the B360 data file, refer to this thread
takichiman said:
Sadly, it didn't work. I was in that case in which I have no keyboard, no apps and so on...
So I rollbacked to MM using Huawei's official packages.
If anyone needs the B360 data file, refer to this thread
Click to expand...
Click to collapse
Did you get BT back?
joesee said:
Did you get BT back?
Click to expand...
Click to collapse
Yes,
when rolling back to MM, I also noticed that TWRP was replaced by the stock recovery. I'm not yet certain but the bootloader is probably locked now.
I think I lost BT because i flashed a data zip prior to the firmware version I was using.
But I remain curious, I think i'll try to update to Nougat again and retry all of this again.
Please, link downloadable files directly. If You write a complete tutorial, the peoples won't need to read another one, to point a final link, where he at least download the suggested files.
Please, short this way.
For what it's worth, I only had to flash this file from TWRP to get the apps back and fix nfc and bt on my l04. It's the data file for the newest b360. http://update.hicloud.com:8180/TDS/...09/f1/full/hw/usa/update_data_full_hw_usa.zip
Oh, the keyboard wasn't working... So I texted myself my email and password from my lady's phone, copied and pasted that in to get into the Play Store, opened up my apps and installed my favorite keyboard. Now to mess it up some more...
Skeletor916 said:
For what it's worth, I only had to flash this file from TWRP to get the apps back and fix nfc and bt on my l04. It's the data file for the newest b360. http://update.hicloud.com:8180/TDS/...09/f1/full/hw/usa/update_data_full_hw_usa.zip
Oh, the keyboard wasn't working... So I texted myself my email and password from my lady's phone, copied and pasted that in to get into the Play Store, opened up my apps and installed my favorite keyboard. Now to mess it up some more...
Click to expand...
Click to collapse
Thanks for sharing this. I'll update the OP with the newer b360 data file. I'm curious what the difference is between b320 and b360. Wonder if it's worth the effort to try to upgrade.
Introduction
XDA members devil188, nailyk and Dobsgw created an Omni ROM for Xperia Z3 Compact. https://goo.gl/omqsSP
A great job.
It works, still has some bugs (20171213) but it is good enough to use as replacement for MM as it is now.
Many are afraid to root their device.
- Warranty void
- Device going black
- Not familiar with the steps to take.
Now is the moment to upgrade your device to Oreo
- Warranty is void anyway because your device is more than 2 years old. (test by clicking on the Support app on your device)
- Device going black ( that is your own risk and I take no responsibility whatever if you brick your device)
- This guide takes you by the hand (step by step)
- The rewards are manifold.
Your devices will be as new.
- Oreo has the latest security updates
- You can allways revert to stock MM
The biggest risk in my opinion is unlocking the device and losing DRM keys which affects low-light photo quality.
This risk can be overcome by making a backup of the TA partition and in case that does not work it can partly be repaired.
Let's start.
STEP 1 Backup
You don't want to lose important stuff, so you want to make a backup first.
Method 1
Use Xperia Companion and make a backup to your PC
Method 2
Use the Xperia Transfer Mobile app
Make a backup to the cloud or to SD card.
Method 3
Use Google.
A good explanation can be found here.
Method 4
Use adb
With adb you cannot restore on a non rooted device but we will go rooting the device anyway.
To read about adb look here.
When begin your backup take some extra safety precautions.
- Whatsapp -> settings -> chats -> backup, for a fresh backup
- Whatsapp extra security copy the Whatsapp directory from device memory to SD card or to PC
- Signal -> Import and Export and copy SignalPlaintectBackup.xml to SD card renaming it to SignalPlaintextBakup-201712XX.xml
- Copy DCIM (your pictures) from internal memory to SD card or to PC
- Google backup settings -> accounts & sync -> sync everything
- Copying can be done with TotalCommander
I suggest to try the different methods of backing up and don't forget to test restoring.
STEP 3 Install and use ADB
Because you will root your device and need to make a backup of the ta partition it is important that you are able to use adb.
I made a post on that subject here.
Most of you probably are on Windows 10.
In this ADB and Fastboot for dummies is explained how to install the drivers for Windows 10 (and 8)
When you read it carefully it will be no problem to set it up.
Warning!
Flashtool, which is mentioned in the setup for installing the drivers on Windows, can be polluted on some download sites with virus and/or malware.
Take care!
Drivers from Sony can be downloaded from here.
STEP 4 Root your Locked device
You can root your locked device by following the steps from this thread carefully.
I did'nt manage so I unlocked my device.
STEP 5 Backup DRM keys & TA partition.
As I said, I didn't manage to root the locked device.
It didn't restart into recovery and I couldn't install Superuser.
The original thread for TA backup can be found here.
STEP 6 Unlocking the device
Now that the problem of backing up the TA partition no longer exists the rest of the steps are rather easy.
Go to the Sony website to unlock your device and follow the instructions carefully.
The link on how to unlock is here.
STEP 7 Get the necessary files
You will need:
- TWRP to have recovery from here.
- The Oreo ROM from here.
- Gapps from OpenGapps. (choose ARM, 8.0 and stock)
- TA partition repair from here. Choose the Z3C version and download from Mediafire.
Download everything in one directory.
Websites where information can be found:
How to Root And Install Official TWRP Recovery For Sony Xperia Z3 Compact
Restore Lost Functionality on Your Unlocked Xperia Device
STEP 8 Putting it all together
We are almost finished.
- Connect your (running) device to your computer and copy OmniROM, SuperUser, OpenGapps and DRM Function Restore V3 to the Download directory on your device.
- Goto settings -> developer options -> switch USB debugging on (you have done this long before)
- Copy TWRPxxxx.img to your adb directory on your PC
- Find the adb directory (Minimal ADB and Fastboot), press the Shift key and right-click on the directory -> choose Open PowerShell window here.
- In the command window type <./adb devices> (without the ./ it won't work) (without the < and the> of course)
- On your Phone you have to permit adb debugging from your PC (you have done this long before)
- Device connected, positive answer on your screen
- issue the command <./adb reboot bootloader> to go into fastboot mode
- type <./fastboot devices> to see if all goes well
- type <./fastboot flash recovery twrp.img> or whatever the name of the twrp image is. twrp-3.0.2-1-z3c.img
- It takes just as sec and the screen shows its OK
- Boot up your phone by pushing vol-down and on/off together to go into recovery mode and TWRP will show.
- TWRP asks to change the system partition from read only -> Swipe to allow modification
- Choose WIPE -> Swipe to factory reset (patience)
- Go back twice (do NOT reboot) to goto the main menu and choose Install
- Goto the Download directory and choose
-> omni -> add more zips -> superuser -> add more zips -> open gapps -> add more zips -> DRM function restore
-> Swipe to confirm flash
- If you only install Omni and forget superuser and gapps you will end up with a non-system. DRM function restore is luxury.
- Wipe cache and Dalvik cache
- Automagic reboot will follow
- Unplug
- Be patient , the first boot of your Oreo loaded Z3 Compact will take a while.
Step 9 Hurray
You did it!
You ended up with a superb Z3 Compact!
@HvdW Please check your PMs
Also, there is some inaccuracies in your advice and statements in the above guide.
Thanks for your step-by-step guide. I think you don´t need the drm fix if you aren´t using a stock rom with unlocked bootloader.
Omni-ROM will bypass the loss of camera quality.
Since nougat (lineageOS, omni, carbon) developers found a way to have the camera working with the same picture quality as in stock rom.
SkyHigh76 said:
Thanks for your step-by-step guide. I think you don´t need the drm fix if you aren´t using a stock rom with unlocked bootloader.
Omni-ROM will bypass the loss of camera quality.
Since nougat (lineageOS, omni, carbon) developers found a way to have the camera working with the same picture quality as in stock rom.
Click to expand...
Click to collapse
Yes you do. Once you unlock the bootloader DRM functionality is gone. So on a stock ROM with unlocked bootlader you will need the DRM fix in order to fix the DRM functionality. If you use a custom kernel with the DRM fix already incorporated into it then you do not need to add it again as you are already using it. In either case, it is needed though...
@HvdW
I tidied up your OP. The missing step 2 is down to you. The original posts did not have a step 2, it went from step 1 to step 3.
Nice, I will try this early January, after Christmas
Thank You!
HvdW said:
Introduction
XDA members devil188, nailyk and Dobsgw created an Omni ROM for Xperia Z3 Compact. https://goo.gl/omqsSP
A great job.
It works, still has some bugs (20171213) but it is good enough to use as replacement for MM as it is now.
Many are afraid to root their device.
- Warranty void
- Device going black
- Not familiar with the steps to take.
Now is the moment to upgrade your device to Oreo
- Warranty is void anyway because your device is more than 2 years old. (test by clicking on the Support app on your device)
- Device going black ( that is your own risk and I take no responsibility whatever if you brick your device)
- This guide takes you by the hand (step by step)
- The rewards are manifold.
Your devices will be as new.
- Oreo has the latest security updates
- You can allways revert to stock MM
The biggest risk in my opinion is unlocking the device and losing DRM keys which affects low-light photo quality.
This risk can be overcome by making a backup of the TA partition and in case that does not work it can partly be repaired.
Let's start.
STEP 1 Backup
You don't want to lose important stuff, so you want to make a backup first.
Method 1
Use Xperia Companion and make a backup to your PC
Method 2
Use the Xperia Transfer Mobile app
Make a backup to the cloud or to SD card.
Method 3
Use Google.
A good explanation can be found here.
Method 4
Use adb
With adb you cannot restore on a non rooted device but we will go rooting the device anyway.
To read about adb look here.
When begin your backup take some extra safety precautions.
- Whatsapp -> settings -> chats -> backup, for a fresh backup
- Whatsapp extra security copy the Whatsapp directory from device memory to SD card or to PC
- Signal -> Import and Export and copy SignalPlaintectBackup.xml to SD card renaming it to SignalPlaintextBakup-201712XX.xml
- Copy DCIM (your pictures) from internal memory to SD card or to PC
- Google backup settings -> accounts & sync -> sync everything
- Copying can be done with TotalCommander
I suggest to try the different methods of backing up and don't forget to test restoring.
STEP 3 Install and use ADB
Because you will root your device and need to make a backup of the ta partition it is important that you are able to use adb.
I made a post on that subject here.
Most of you probably are on Windows 10.
In this ADB and Fastboot for dummies is explained how to install the drivers for Windows 10 (and 8)
When you read it carefully it will be no problem to set it up.
Warning!
Flashtool, which is mentioned in the setup for installing the drivers on Windows, can be polluted on some download sites with virus and/or malware.
Take care!
Drivers from Sony can be downloaded from here.
STEP 4 Root your Locked device
You can root your locked device by following the steps from this thread carefully.
I did'nt manage so I unlocked my device.
STEP 5 Backup DRM keys & TA partition.
As I said, I didn't manage to root the locked device.
It didn't restart into recovery and I couldn't install Superuser.
The original thread for TA backup can be found here.
STEP 6 Unlocking the device
Now that the problem of backing up the TA partition no longer exists the rest of the steps are rather easy.
Go to the Sony website to unlock your device and follow the instructions carefully.
The link on how to unlock is here.
STEP 7 Get the necessary files
You will need:
- TWRP to have recovery from here.
- The Oreo ROM from here.
- Gapps from OpenGapps. (choose ARM, 8.0 and stock)
- TA partition repair from here. Choose the Z3C version and download from Mediafire.
Download everything in one directory.
Websites where information can be found:
How to Root And Install Official TWRP Recovery For Sony Xperia Z3 Compact
Restore Lost Functionality on Your Unlocked Xperia Device
STEP 8 Putting it all together
We are almost finished.
- Connect your (running) device to your computer and copy OmniROM, SuperUser, OpenGapps and DRM Function Restore V3 to the Download directory on your device.
- Goto settings -> developer options -> switch USB debugging on (you have done this long before)
- Copy TWRPxxxx.img to your adb directory on your PC
- Find the adb directory (Minimal ADB and Fastboot), press the Shift key and right-click on the directory -> choose Open PowerShell window here.
- In the command window type <./adb devices> (without the ./ it won't work) (without the < and the> of course)
- On your Phone you have to permit adb debugging from your PC (you have done this long before)
- Device connected, positive answer on your screen
- issue the command <./adb reboot bootloader> to go into fastboot mode
- type <./fastboot devices> to see if all goes well
- type <./fastboot flash recovery twrp.img> or whatever the name of the twrp image is. twrp-3.0.2-1-z3c.img
- It takes just as sec and the screen shows its OK
- Boot up your phone by pushing vol-down and on/off together to go into recovery mode and TWRP will show.
- TWRP asks to change the system partition from read only -> Swipe to allow modification
- Choose WIPE -> Swipe to factory reset (patience)
- Go back twice (do NOT reboot) to goto the main menu and choose Install
- Goto the Download directory and choose
-> omni -> add more zips -> superuser -> add more zips -> open gapps -> add more zips -> DRM function restore
-> Swipe to confirm flash
- If you only install Omni and forget superuser and gapps you will end up with a non-system. DRM function restore is luxury.
- Wipe cache and Dalvik cache
- Automagic reboot will follow
- Unplug
- Be patient , the first boot of your Oreo loaded Z3 Compact will take a while.
Step 9 Hurray
You did it!
You ended up with a superb Z3 Compact!
Click to expand...
Click to collapse
Thank you! Excellent step by step baby guide. However <b><i>do</b></i> wish to point out to future people unlocking their bootloader that it is HIGHLY essential that you backup your TA before unlocking the bootloader.
What i did is: unlocked bootloader before i ever sow this post, installed custom stock based rom, red this post, backuped DRM, and DRM found and successfully backuped intact just like it was before unlocking on Z3Compact
OpenGapps 8.0 not working, you need 8.1.0 gapps.
Thanks for posting this guide. Is it ok to ask questions in this thread? Because I'm kind of stuck
I successfully completed every step until #6 "Unlocking the device". For some reason I can't get into fastboot mode anymore. The device shows a black screen, the LED is lighting up blue. Kernel version is 291. Phone has root access and SuperSU installed.
adb recognizes the device, fastboot does not - see attached image.
Any advice?
vinc9876 said:
Thanks for posting this guide. Is it ok to ask questions in this thread? Because I'm kind of stuck
I successfully completed every step until #6 "Unlocking the device". For some reason I can't get into fastboot mode anymore. The device shows a black screen, the LED is lighting up blue. Kernel version is 291. Phone has root access and SuperSU installed.
adb recognizes the device, fastboot does not - see attached image.
Any advice?
Click to expand...
Click to collapse
If u see blue led u are on fastboot.
Try adb fastboot comand after mast see same help comand, now try fastboot device.
Don't worry, take,it easy. GL
Maybe u are flashtool open, close flashtool.
yo7fb said:
Try adb fastboot comand after mast see same help comand.
Click to expand...
Click to collapse
I don't think I understand what you mean.
I think the bootloader is stuck somehow. Maybe something to do with the .291 ROM being incompatible with the bootloader? I'm pretty sure I should see the fastboot screen like so:
EDIT: Got it working!
Had to reinstall adb/fastboot drivers from the flashtool installation.
HvdW said:
Introduction
-> omni -> add more zips -> superuser -> add more zips -> open gapps -> add more zips -> DRM function restore
-> Swipe to confirm flash
- If you only install Omni and forget superuser and gapps you will end up with a non-system. DRM function restore is luxury.
- Wipe cache and Dalvik cache
- Automagic reboot will follow
- Unplug
- Be patient , the first boot of your Oreo loaded Z3 Compact will take a while.[/hide]
Step 9 Hurray
You did it!
You ended up with a superb Z3 Compact!
Click to expand...
Click to collapse
Thanks a lot for the detailed tutorial. I have a question because I stuck in the last steps. When says "superuser" refers to the superuser_238_291.zip file??? because I take that and I waited for more than 1 hour with following Oreo starting screen and never overcome that screen.
Hi guys! Thanks for the manual. I've followed all steps and I upgraded to 8.1.0
All is ok, but when I recive a call doesn't appear anything in screen. Only sound the ring, but I can't answer the call.
jhalvico said:
Thanks a lot for the detailed tutorial. I have a question because I stuck in the last steps. When says "superuser" refers to the superuser_238_291.zip file??? because I take that and I waited for more than 1 hour with following Oreo starting screen and never overcome that screen.
Click to expand...
Click to collapse
Hello.
I'm sadly in same situation as you are (or was). Did everything according to guide but it is 1.5 houre since it started booting.
Do any of you guys have tip what to do?
Btw: thanks for this guide
Edit:
So i managed to get it working by following steps from the Oreo rom page.
the battery on which version lives more?
probably google dialer?
uilino said:
Hi guys! Thanks for the manual. I've followed all steps and I upgraded to 8.1.0
All is ok, but when I recive a call doesn't appear anything in screen. Only sound the ring, but I can't answer the call.
Click to expand...
Click to collapse
Did you install google dialer? if so, go to
Settings--> Apps¬ifications -->Advanced-->Default apps --> Phone app --> Select "Phone"
Error 7/6 when I try to install ZIP File via TWRP
Hey there, thank you very much for that easy install guide. Unfortunately I get stuck in my TWRP when I try to install the omnirom Zip. It showed error 7, then i edited the binary script file and it changed to error 6. Any kind of solutions here?
Hovenzius said:
Hey there, thank you very much for that easy install guide. Unfortunately I get stuck in my TWRP when I try to install the omnirom Zip. It showed error 7, then i edited the binary script file and it changed to error 6. Any kind of solutions here?
Click to expand...
Click to collapse
hi, i have got the same problem and i found this solution : https://forum.xda-developers.com/showthread.php?t=2522762
Restore with Xperia Companion
HvdW said:
STEP 1 Backup
You don't want to lose important stuff, so you want to make a backup first.
Method 1
Use Xperia Companion and make a backup to your PC
Click to expand...
Click to collapse
First thank you for your great post!
I try to restore my data after a successful upgrade and after having saved them with Xperia Companion but I can't succeed to make it detect my phone, so I can't use restore function... Do you know how can I achieve that? Is there some apk to install on the phone in order to make Xperia Companion recognize my phone and make restore function work?
Thanks!
Hi guys,
I have successfully followed this step-by-step:
How-to: root, keep and backup DRM keys, etc. [KitKat/Lollipops/Marshmallow/etc.]
and I also have unlocked the BL.
So, my Z3c has
- DualRecovery installed
(Z3C-lockeddualrecoveryX.Y.Z-RELEASE.installer.zip)
- superSU
- pre-rooted D5803 23.5.A.1.291
- backed-up TA
- unlocked BL
My question:
Do I still need to install Twrp or could I just boot into DualRecovery and flash CARBON-CR-6.1 + gaps from internal storage of phone?
Btw, if it isn't already blatantly obvious, I'm a total noob and without all the fine tutorials wouldn’t have a clue what I was doing.
Thanks for reading.
So I got sick of Oreo constantly crapping out, being buggy and decided to give 7.1.2 a whirl again just because I remember it working so much better and it's been announced there are no more updates. After fighting with it for a while, I finally got it downgraded and staying there. I found another post detailing some of this but wanted to write a howto from scratch.
Here's how I did it:
Download the factory image for fugu 7.1.2 from here: https://developers.google.com/android/images
Download the latest version of Magisk from here: https://github.com/topjohnwu/Magisk/releases
Download ADB/Fastboot of your choice and install it. I use this on windows: https://forum.xda-developers.com/showthread.php?t=2317790
Download TWRP for fugu here: https://dl.twrp.me/fugu/twrp-3.2.2-0-fugu.img.html
Reboot your nexus into bootloader mode (hold button on bottom while plugging in, light turns on, then blinks, release button) Connect it to your computer with a MicroUSB cable.
First thing you need to do is ensure your player is unlocked. When in the fastboot screen it should show the lock state. If it's locked, you need to run this command twice from your computer: "fastboot oem unlock"
Okay, now you're ready to go, you need to extract the factory firmware and use adb to flash it. Extract the main firmware file. Inside is another large zip file with the broken out recovery and system images. Extract that file also.
First flash the 7.1.2 bootloader: fastboot flash bootloader bootloader-fugu-fugu-02.13.img
Reboot into the flashed bootloader: fastboot reboot-bootloader (If it doesn't reboot in the bootloader, unplug and use the hold button and plug in to get back to the bootloader screen)
There is usually another ZIP in the factory images archivce, you can flash all with the included script or I usually just unzip that archive and flash one at a time.
Flash System: fastboot flash system system.img
Flash Boot: fastboot flash boot boot.img
You can skip flashing the recovery because you are going to flash TWRP with: fastboot flash recovery twrp-3.2.2-0-fugu.img
Okay, now you need to go into TWRP. You can press the button once on the player and it will say recovery mode, then hold the button for a few seconds and let go and it should boot int TWRP.
You need a mouse to control TWRP unfortunately and I had to use a USB OTG adapter to get a mouse connected to the NexusPlayer MicroUSB port.
TWRP Might ask if you want to keep system Read Only. Push the button that says Keep Read Only.
Once you are in TWRP, you need to sideload the Magisk ZIP file. Go to Advanced, select USB sideload and swipe to start it.
Now you need to hook the player up to the computer again with MicroUSB.
On your computer do: adb sideload Magisk-v17.3.zip (Or whatever version of Magisk you happened to download)
It should load Magisk and patch everything for you. I have found that I need to then hook the mouse back up, go back to the main menu, and perform a wipe/factory reset of the Data partition before it will allow it to boot for some reason.
Once that is done, boot up the Nexus Player. It will ask you to connect Wifi and register. If you have non 5g Wifi, connect to that first as you are racing against the clock to install Magisk Manager before the Oreo Update downloads and installs.
The first thing you need to do is allow Unknown Sources from Settings -> Security & Restrictions -> Enable Unknown Sources
Next install Magisk Manager -> Go to Settings -> Apps -> Magisk and hit Open, it should download the Magisk Manager application and ask you to install.
Once that is done, immediately go to network settings and disable WiFi, this will stop the download of the Oreo Update and you have time to finish up.
Now you need to go to About and click 5 times on Build version to become a developer. Go to Settings -> Developer options and enable USB debugging. It
Connect the Nexus Player back to your computer (it should ask if you want to allow developer access, select yes) and do:
adb shell
Once in the shell type: su
It should pop up a dialog asking you to approve root, say yes.
Okay, now you are going to disable the otacerts.zip This will disallow updates to be applied.
Remount the system partition as readwrite
cd /
mount -o rw,remount /system
Disable otacerts.zip
cd /system/etc/security
mv otacerts.zip otacerts.disabled.zip
exit
exit
Okay, now your nexus player will no longer to able to apply updates. If you are happy here, you are good to go. The nexus player will still continue to try to download updates though so if you want, you should be able to disable it with this script: https://pastebin.com/E7QuvFdQ
Save as disupdate.sh on your computer
You put this script on your nexus player by using adb
adb push disupdate.sh /sdcard/disupdate.sh
You should then use adb shell again and move the script into place
adb shell
su (accept request on screen if it asks to become root)
mv /sdcard/disupdate.sh /sbin/.core/img/.core/service.d/disupdate.sh
chmod 755 /sbin/.core/img/.core/service.d/disupdate.sh
This will automatically disable the update service when the box boots. If there is no directory /sbin/.core/img/.core/service.d then Magisk isn't likely properly installed. You might need to reboot or something to get it to load.
That's it, enjoy Nougat, IMO the best running rom for the Nexus Player.
Thank you! My player started random reboots then lost wifi on android 8. This worked great and she seems to be running properly again.
The final step fails for me. I run adb push to move the script and it looks like it does it, no error message but the file doesn't copy. Not a big deal, I can watch netflix again.
---------- Post added at 12:32 PM ---------- Previous post was at 11:47 AM ----------
I worked around it. What I did was push the file to a location I had permission to write to on the nexus.
Then I copied the file using a root powered file manager, Solid Explorer in this case, to /sbin/.core/img/.core/service.d/
Hopefully this helps others to keep their nexus player alive. 7.1.2 runs very nice.
Update: After running great for the past week my nexus player how just sits at the black google screen.
You lost me at the "USB OTG adapter"
I wonder if your problem with Ver. 8 (which is Oreo?) has to do with unplugging or losing power to the device? - After I lost power for just a second (blink) the unit partially bricked and finding your post got me to a different page that showed how to sideload (via ADB) the ver. 8 OTA onto the device.
That worked OK until the unit lost power again (I unplugged it to move it). The problem returned and since I don't have the mouse adapter, I just tried to sideload a ver. 7.1.2 OTA but that refused to load with an error message that I didn't grok but probably meant that it was incompatible with stuff that Ver. 8 had on the filesystem.
So I restored again the latest Ver. 8 ota.zip and for now (until the next power off) it is working.
-----
Seems like they have a problem serious enough thought that another update will have to happen.
-----
Thanks!
snowzach said:
So I got sick of Oreo constantly crapping out, being buggy and decided to give 7.1.2 a whirl again just because I remember it working so much better and it's been announced there are no more updates. After fighting with it for a while, I finally got it downgraded and staying there. I found another post detailing some of this but wanted to write a howto from scratch.
Here's how I did it:
Download the factory image for fugu 7.1.2 from here: https://developers.google.com/android/images
Download the latest version of Magisk from here: https://github.com/topjohnwu/Magisk/releases
Download ADB/Fastboot of your choice. I use this on windows: https://forum.xda-developers.com/showthread.php?t=2317790
Download TWRP for fugu here: https://dl.twrp.me/fugu/twrp-3.2.2-0-fugu.img.html
Reboot your nexus into bootloader mode (hold button on bottom while plugging in, light turns on, then blinks, release button) Connect it to your computer with a MicroUSB cable.
Once you are in fastboot mode, you need to extract the factory firmware and use the minimal adb to flash it.
First flash the 7.1.2 bootloader: fastboot flash bootloader bootloader-fugu-fugu-02.13.img
Reboot into the old bootloader: fastboot reboot-bootloader
There is usually another ZIP in the factory images archivce, you can flash all with the included script or I usually just unzip that archive and flash one at a time.
Flash System: fastboot flash system system.img
Flash Boot: fastboot flash boot boot.img
You can skip flashing the recovery because you are going to flash TWRP with: fastboot flash recovery twrp-3.2.2-0-fugu.img
Okay, now you need to go into TWRP. You can press the button once on the player and it will say recovery mode, then hold the button for a few seconds and let go and it should boot int TWRP.
You need a mouse to control TWRP unfortunately and I had to use a USB OTG adapter to get a mouse connected to the NexusPlayer MicroUSB port.
Once you are in TWRP, you need to sideload the Magisk ZIP file. Go to Advanced, select USB sideload and swipe to start it.
Now you need to hook the player up to the computer again with MicroUSB.
On your computer do: adb sideload Magisk-v16.7.zip
It should load Magisk and patch everything for you. I have found that I need to then hook the mouse back up, go back to the main menu, and perform a wipe of the Data partition before it will allow it to boot for some reason.
Once that is done, boot up the Nexus Player. It will ask you to connect Wifi and register. If you have non 5g Wifi, connect to that first as you are racing against the clock to install Magisk Manager before the Oreo Update downloads and installs.
The first thing you need to do is allow Unknown Sources from Settings -> Security & Restrictions -> Enable Unknown Sources
Next install Magisk Manager -> Go to Settings -> Apps -> Magisk and hit Open, it should download the Magisk Manager application and ask you to install.
Once that is done, immediately go to network settings and disable WiFi, this will stop the download of the Oreo Update and you have time to finish up.
Now you need to go to About and click 5 times on Build version to become a developer. Go to Settings -> Developer options and enable USB debugging. It
Connect the Nexus Player back to your computer (it should ask if you want to allow developer access, select yes) and do:
adb shell
Once in the shell type: su
It should pop up a dialog asking you to approve root, say yes.
Okay, now you are going to disable the otacerts.zip
This will disallow updates to be applied
cd /system/etc/security
mv otacerts.zip otacerts.disabled.zip
Okay, now your nexus player will no longer to able to apply updates. If you are happy here, you are good to go. The nexus player will still continue to try to download updates though so if you want, you should be able to disable it with this script: https://pastebin.com/E7QuvFdQ
Save as disupdate.sh on your computer
You put this script on your nexus player by using adb
adb push disupdate.sh /sbin/.core/img/.core/service.d/disupdate.sh
You may also need to use adb shell again and run:
chmod 755 /sbin/.core/img/.core/service.d/disupdate.sh
This will automatically disable the update service when the box boots.
That's it, enjoy Nougat, IMO the best running rom for the Nexus Player.
Click to expand...
Click to collapse
First off great starting point to get nougat back on nexus player but a few points...
a) I had to do "mount -o rw,remount /system" after SU to get write on /system
b) The method you outlined for running script on boot didn't work for me and i ended up having to use https://play.google.com/store/apps/details?id=com.k2.bootshellprokey with the script you provided
Other than those two points worked great and staying on 7.1.2
Questions:
"cd /system/etc/security mv otacerts.zip otacerts.disabled.zip" is this typed in the adb shell?
Where on the computer should I save this "Save as disupdate.sh on your computer"?
Thanks
texasjmzmd said:
Questions:
"cd /system/etc/security mv otacerts.zip otacerts.disabled.zip" is this typed in the adb shell?
Where on the computer should I save this "Save as disupdate.sh on your computer"?
Thanks
Click to expand...
Click to collapse
I answered these questions. However I get an error of failed to copy when I adb push the sh file.
Had to do this 4 times to get it to stick. The second to the last step preventing the update is what was difficult. It kept upgrading to Android 8. I couldn't get the script part to work. So far so good this has worked for me. Kibmcz's "a)" suggestion allowed me to stop the automatic upgrade. So far it's sticking and working really well. I did this to prevent the black screen of death that everyone's getting with Android 8.0 upgrade.
Got the OTG adapter - questions & comments
Finally got an adapter to run that allowed a mouse hookup to run TWRP. Followed the directions and have a couple of questions and deviations that I had to take.
1. Now that TWRP takes the place of Recovery, does a manual backup of the changed version of what we have here have to be done in order to restore if something compromised the system again?
2. TWRP shows up in the Player app and if you launch it tells you to download as it is only a placeholder?
3. The script disupdate.sh wouldn't copy to the required destination even if I ran "adb root" so I had to push it to /sdcard then shell in, become su and mv it to ~/service.d Then chmod worked and I rebooted.
4. Turned back on the wifi and saw items updating. I went to About > Update and saw that Vers. 8 was downloading. At the end it claims that 489.2 MB downloaded but then - Verification failed. That shows that the moving of the 'cert' file worked but perhaps not the script? Is that space recoverable? What directory is it put in?
Otherwise, seems to be working - Many thanks to you !
A couple of days later, the 4 balls animation returned. Brought up Restore, TWRP and attempted to revert to a backup made with it but it would not restore it. So... Flashed boot and Flashed system and it came back to life for another couple of days. TWRP doesn't load anymore though so the un-altered system without the script still doesn't want to load Oreo as there is a copy of Oreo still there that didn't pass verification.
Still busted every couple of days though.
ggregor said:
Finally got an adapter to run that allowed a mouse hookup to run TWRP. Followed the directions and have a couple of questions and deviations that I had to take.
1. Now that TWRP takes the place of Recovery, does a manual backup of the changed version of what we have here have to be done in order to restore if something compromised the system again?
2. TWRP shows up in the Player app and if you launch it tells you to download as it is only a placeholder?
3. The script disupdate.sh wouldn't copy to the required destination even if I ran "adb root" so I had to push it to /sdcard then shell in, become su and mv it to ~/service.d Then chmod worked and I rebooted.
4. Turned back on the wifi and saw items updating. I went to About > Update and saw that Vers. 8 was downloading. At the end it claims that 489.2 MB downloaded but then - Verification failed. That shows that the moving of the 'cert' file worked but perhaps not the script? Is that space recoverable? What directory is it put in?
Otherwise, seems to be working - Many thanks to you !
Click to expand...
Click to collapse
I couldn't get the script to work either.
Did this August 21st. Still working today [Sept 2].
For those of you still having trouble, it seems like you are having an issue with installing Magisk. When you have Magisk installed, it actually creates linked directories in the system partition. You aren't making changes to system. I am going to update the original post to push the script and then move it to a directory that Magisk manages. That hopefully fixes everyone else.
Thanks for posting and updating your instructions. I used my own workaround for keeping my 3 Nexus Players alive and locked on Nougat 7.12...
Do you have a theory on how to make the LED light work again on those NPs that have gone dark and unresponsive to the OTG connection from a laptop or PC?
Instead of rooting or using Magisk, just use TWRP and its file manager to rename the ota certs file. You can also use it to put in the script if you want, or use it to remove gms and gsf to stop GPS from updating which actually is more the problem - people on lineage 15.1 are still bricking.
Did this August 21st. Still working today [Sept 20].
Mine is dead now.... No light on powerup, quickboot screen or any other sign of life. Forced to move on to a non-branded Android box. Boot loop even started after using LineageOS 15.1 (which required starting with 8.0 Oreo)
thanks for the guide, I did this and it worked great. Used the script as well and all 3 of my players are still working 2+ weeks after doing this.
I did notice I can't stream anything from some apps anymore though. Is there a way to remove root, so I can stream from certain apps again?
Triumph said:
I did notice I can't stream anything from some apps anymore though. Is there a way to remove root, so I can stream from certain apps again?
Click to expand...
Click to collapse
Which specific streaming apps are you referring to and what do the error msgs say?
growsonwalls said:
Which specific streaming apps are you referring to and what do the error msgs say?
Click to expand...
Click to collapse
They are HGTV, Travel Channel, Cooking Network, and ABC.
When I open them up they show a "Live Channel" option, and I enter in my online information for the channel (That has always worked in the past, and works on my Nvidia Shield device that isn't rooted.)
If I choose the Live Channel quick enough it tries to play then times out and says "There was an error playing this content."
If I open the app, and stay at the main screen for a minute or so, the Live Channel option disappears from the header, and I don't see it again, until I reboot the player.
I can play previous show episodes, just not the live stuff.
Triumph said:
They are HGTV, Travel Channel, Cooking Network, and ABC.
I can play previous show episodes, just not the live stuff.
Click to expand...
Click to collapse
In order to recreate this, I am still missing vital information.
Is this happening inside of Kodi or did you download these 4 apps (channels) through the Google Play Store?
In Kodi, I've never seen a "Live Channel" option for these channels, just several old episodes listed.
As for the 4 channels from the Play Store, they each have a stream live option where you sign in to your tv provider. My tv provider isn't on that 'sign in' list so can't watch it live.
If in Kodi, were they installed from the Kodi repo or did you install a 'build' that came with them already installed?
Or is there a different streaming app that is hosting these apps?
DON'T DO THIS ON A RAZER PHONE 1 OR IT WILL BE OMEGA BRICKED! ONLY DO THIS ON A RAZER PHONE 2!
This was just an experiment to see if i could cobble together some GSI install guides (that on their own are kinda confusing) to make something moderately more cohesive and understandable. Here's my moderately usable guide!
-----------------------------------------------------------------
VIDEO!
-----------------------------------------------------------------
-----------------------------------------------------------------
Things that work and don't work:
-----------------------------------------------------------------
This section will update periodically as issues arise or fixes arise for said issues.
Note: Things that work: Bluetooth*, all sensors, audio, LTE/SIM/phone stuff, 120hz (you need to go into the settings > Phh treble settings > Misc features > Force FPS > [email protected])
Things that probably work: N/A
Things that don't work for some reason: SafteyNet with Magisk. All modules that I've used work tho...??! Verizon.
Remember, you can always flash back to stock if something doesn't work properly.
-----------------------------------------------------------------
FIXES!!!
-----------------------------------------------------------------
AUDIO FIX!!! GO TO Phh Treble Settings > Qualcomm features > Use alternate audio policy.
Bluetooth audio stops working with this enabled. Disable it for Bluetooth audio. The audio fix doesn't apply to Bluetooth audio ether way.
BLUETOOTH FIX!!! Download a root file browser from the google play store and allow it to have root access. Delete BluetoothCommonRes.apk which is found in the overlay folder which is found in the vendor folder. After you delete BluetoothCommonRes.apk, rename the RazerAuraBluetoothRes.apk to BluetoothCommonRes.apk.
-----------------------------------------------------------------
Important notes
-----------------------------------------------------------------
THIS IS ASSUMING YOU HAVE ALREADY UNLOCKED THE BOOTLOADER OF YOUR DEVICE AND HAVE GOTTEN A SERIAL NUMBER OUTPUT FROM CMD AFTER TYPING IN "fastboot devices" AND MAKE SURE YOU HAVE TYPED IN "fastboot flashing unlock" AND "fastboot flashing unlock-critical".
***NOTE: I AM NOT RESPONSIBLE FOR ANY HARD BRICKED DEVICES OR ANGRY PARENTS. PLEASE DO NOT COME BACK AT ME SAYING I AM STUPID AND BRICKED YOUR PHONE. YOU DECIDED TO DO THIS. PLEASE PROCEED WITH CAUTION AND DON'T SKIM***
ANOTHER IMPORTANT NOTE: The stock firmware is actually really good for unbricking devices. Razer made it easy to fix your bricked device. So basically, if you can get in to fastboot mode, (which you basically always can do) you can unbrick your device super easily.
AGAIN JUST PLEASE, MAKE SURE TO FOLLOW ALL THESE INSTRUCTIONS CAREFULLY AND DONT SKIM OR ELSE YOU MIGHT BREAK SOMETHING!!!
-----------------------------------------------------------------
Introduction
-----------------------------------------------------------------
This is a quick and easy guide for how to install Android 11 on the Razer Phone 2. I'm kind of a noob here myself but I did this and it worked flawlessly. (also if you do run into any issues PLEASE don't count on me for troubleshooting tips (I'm not that great at that))
-----------------------------------------------------------------
Pre-requisites/Downloads
-----------------------------------------------------------------
Get the factory firmware for your phone. It's a good failsafe in case of a bootloop or a bad case of the phone not booting up. Download it here: P-SMR6-RC001-RZR-201022 (latest build at the time of writing)
Extract this with 7zip or WinRar (or windows. You will need 7zip or WinRar for the rest of this)
First you need the actual GSI. Get the latest version. (Make sure its not a pre-release). system-roar-arm64-ab-vndklite-gapps.img.xz is the version that you should get. The vndklite release will allow you to modify the system partition making it possible to get magisk. Note: If you want magisk, MAKE SURE TO COMPLETELY follow the magisk section of this guide aswell or else magisk will NOT install correctly and will NOT work.
This version also has GApps. It will give you Gmail, the google play store, google play services, etc.
Use 7zip or WinRar to extract this.
Your also gonna need the Trinity Kernel (v2). This gives you TWRP and I'm pretty sure you also need this to have the ability to boot up the phone (I may be wrong but it's required.)
use 7zip or WinRar to extract this.
You will also need this zip file made by arter97 I don't really know what it does but you need it. here is the download: Download.
Don't extract this.
Put all these in a known folder that you can access later.
Alright. Now that we're done with the downloads, time to test to make sure your ready to put this on your phone.
-----------------------------------------------------------------
Making sure your computer is ready
-----------------------------------------------------------------
First things first. Go open your platform tools folder, shift-right click and open a PowerShell, or command prompt window there. Shut down your Razer phone 2 and turn it back on with the power and volume down buttons.
Plug it into your PC and type in
Code:
fastboot devices
you should end up with the serial number of the device. if you don't, follow Razer's instructions on how to install USB drivers and then come back here. Link to PDF.
If you get a serial number, close that and flash stock firmware by going into the aura-p-release-etc. folder, then opening flash_all.bat.
When it finishes and the screen goes black, hold the power and volume down buttons again to get back in to fastboot mode.
open back up the CMD/PowerShell platform tools window thing again.
-----------------------------------------------------------------
Installing/Flashing
-----------------------------------------------------------------
In your CMD or PowerShell window, (while in fastboot mode on the phone) type
Code:
fastboot flash system <file name>
in the <file name> area, just drag and drop the system-roar-arm64-etc.img file into your command line. your command will look a little something like this:
Code:
fastboot flash system C:\Users\user\Desktop\system-roar-arm64-ab-gapps.img
Wait until it says complete or something similar like done or something and has no errors.
Then, time to flash the kernel. it should just be called boot.img.
We will be typing in:
Code:
fastboot flash boot <file name>
Do the same thing that you did for the last command which is drag and drop the boot.img file for the file name.
Again, wait until it says done or complete and has no errors.
After that is done, use the volume buttons to select reboot bootloader with your power button on your phone.
Go to recovery mode and swipe where it says to swipe.
Go to the wipe menu and then tap on format data. Type yes and then press enter/ok.
Go back to your computer and open file explorer.
Put the last zip file that I was talking about earlier (the f2fs thing) on the razer phone 2's internal storage. Head back to your phone, and press install.
Scroll down until you find the zip file and press it and install it. (ignore the errors that may or may not be there) After that, go back to the TWRP home screen (with the 8 options)
Go to the reboot menu, then reboot into recovery
Tap on format data and type in "yes" and tap ok. click on "don't install" because you don't need the TWRP app on your phone.
The phone will shut down. Turn it on normally and everything will work!
----------------------------------------------------------------------------------------------------------------------------------
GET THESE THINGS IF YOU WANT 120Hz, GCam, and a SNAZZY RAZER LOGO.
----------------------------------------------------------------------------------------------------------------------------------
To get 120Hz, you need to go into the settings > Phh treble settings > Misc features > Force FPS > [email protected].
If you want your Razer logo to light up again, use Logo+. here is a download: Logo+ APK
The default camera app sucks. Make sure to get GCam 7.4 from Cyanogen Mods (v8.0 is broken). you can get it here.
Download a root file browser from the google play store and allow it to have root access. Delete BluetoothCommonRes.apk which is found in the overlay folder which is found in the vendor folder. After you delete BluetoothCommonRes.apk, rename the RazerAuraBluetoothRes.apk to BluetoothCommonRes.apk.
-----------------------------------------------------------------
Magisk
-----------------------------------------------------------------
So this part was pretty long-awaited. It half-passes SafteyNet and modules work! (at least all the modules that I've used.)
Make sure you have the vndklite variant. That is the only way that this will work.
1. Open up an adb/fastboot powershell/cmd/windows terminal window.
2. Type adb root and hit enter.
3. Type adb shell and hit enter.
4. Type mount -o remount,rw / and hit enter.
5. Type mv /bin/resetprop_phh /bin/phh-resetprop and hit enter.
6. Type phh-securize.sh and hit enter.
The phone should reboot after you approve the request (if there is one) and you are now able to install magisk!
MAKE SURE THAT THE SUPERUSER APP IS NOT THERE AFTER RUNNING phh-securize.sh.
Get specifically this version of Magisk. Download the zip file.
Boot into TWRP and tap on mount, and select everything (usb storage doesn't matter in this case. it never mounts either way.)
Transfer over your zip file via file explorer, and go back to your phone.
Tap install, then scroll down until you find the zip file and tap it. Swipe to flash and wait. After it is done, you can reboot!
You should see Magisk manager in your app drawer. Open that. It might ask you to install it, if so, install it. Allow apps from this source then install. Open it up. You should see that Magisk is installed. Update it and turn on Magisk hide.
If it passes SafteyNet, it's a miracle.
-----------------------------------------------------------------
In case of failure
-----------------------------------------------------------------
If it starts bootlooping or is perpetually stuck at the razer logo, powered by android screen, go back into fastboot mode and run the flash_all.bat stock firmware thing. it will unbrick your phone automatically. Really make sure you don't skim if you try it again. If it did work (which it probably did), then have a good time with android 11!
There is one bug that has stopped me from going GSI. On every one I've tried, there is a game music bug that is common in many of the games I own. If the volume is set to below 50%, the music will cut in and out constantly. It resolves itself if you keep media volume above 50%. It may not be a deal breaker for everyone, but it was for me, as I use my RP2 heavily for games. Other than that, GSIs work beautifully. Thanks for the comprehensive guide!
Reznor7 said:
There is one bug that has stopped me from going GSI. On every one I've tried, there is a game music bug that is common in many of the games I own. If the volume is set to below 50%, the music will cut in and out constantly. It resolves itself if you keep media volume above 50%. It may not be a deal breaker for everyone, but it was for me, as I use my RP2 heavily for games. Other than that, GSIs work beautifully. Thanks for the comprehensive guide!
Click to expand...
Click to collapse
Just curious, what games have that issue?
Marcos8760 said:
Just curious, what games have that issue?
Click to expand...
Click to collapse
All of The Room games, Battle Chasers: Night War, and most premium games that I've bought. For some reason, Monster Hunter Stories doesn't. It seems like mostly games that have more complex audio/music.
Reznor7 said:
All of The Room games, Battle Chasers: Night War, and most premium games that I've bought. For some reason, Monster Hunter Stories doesn't. It seems like mostly games that have more complex audio/music.
Click to expand...
Click to collapse
Thanks for the info. I added that to the top of the thread.
EDIT: Fix at the top of the thread
Ultimately at the end of the day I could not get Dolby Atmos and the RGB lighting on the back of the phone to work on GSI 10. Hopefully someone will come up with a work around for those 2 items in GSI 11.
RJR
rrusek said:
Ultimately at the end of the day I could not get Dolby Atmos and the RGB lighting on the back of the phone to work on GSI 10. Hopefully someone will come up with a work around for those 2 items in GSI 11.
RJR
Click to expand...
Click to collapse
I got the Razer logo working flawlessly with logo+. I didn't really see the appeal for Dolby Atmos as all it did was made it louder and made the audio clip more.
I did have success getting Atmos to work with this module: https://github.com/reiryuki/Dolby-Atmos-Razer-Phone-2-Magisk-Module
Reznor7 said:
I did have success getting Atmos to work with this module: https://github.com/reiryuki/Dolby-Atmos-Razer-Phone-2-Magisk-Module
Click to expand...
Click to collapse
How can I get magisk on the phone though? it has Superuser pre-installed but it doesn't have support for modules and stuff (as far as I can tell). I really would like some info on how to install magisk if possible.
Marcos8760 said:
How can I get magisk on the phone though? it has Superuser pre-installed but it doesn't have support for modules and stuff (as far as I can tell). I really would like some info on how to install magisk if possible.
Click to expand...
Click to collapse
Actually, I may be misremembering. That may have been on a 10 GSI. I don't think I ever did get Magisk to work on an 11.
Reznor7 said:
Actually, I may be misremembering. That may have been on a 10 GSI. I don't think I ever did get Magisk to work on an 11.
Click to expand...
Click to collapse
Alright good to know. like the other info I've gathered, ill put that at the top of the thread until further notice.
The unofficial LOS GSI just got updated with supposed Magisk support. I'm going to give it a try in a few.
Reznor7 said:
The unofficial LOS GSI just got updated with supposed Magisk support. I'm going to give it a try in a few.
Click to expand...
Click to collapse
Nope, Magisk doesn't work.
Thank you. I got it all set up and mostly working well. I was wondering if you could try Minecraft and let me know if it will let you get to the actual login screen.
I cannot get flashing the Android 11 GSI to work.
I downloaded the latest factory image (MR6) and proceeded to install it. To do that, I had to copy the "fastboot.exe" from the SDK platform tools download to the "aura-p-release..." folder with the factory image.
I open a CMD line and type in "fastboot devices" which get me a string of numbers. Then I type in "fastboot flash system system-roar-arm64-ab-gapps.img.xz" which tries to install it but concludes with an error message, being 'Error: Last flash failed : Bad Buffer Size'.
I tried using different computers and cables, but I end up with the same thing. I'm able to flash the factory image just fine, but can't flash Android 11.
AgentXGhost said:
I cannot get flashing the Android 11 GSI to work.
I downloaded the latest factory image (MR6) and proceeded to install it. To do that, I had to copy the "fastboot.exe" from the SDK platform tools download to the "aura-p-release..." folder with the factory image.
I open a CMD line and type in "fastboot devices" which get me a string of numbers. Then I type in "fastboot flash system system-roar-arm64-ab-gapps.img.xz" which tries to install it but concludes with an error message, being 'Error: Last flash failed : Bad Buffer Size'.
I tried using different computers and cables, but I end up with the same thing. I'm able to flash the factory image just fine, but can't flash Android 11.
Click to expand...
Click to collapse
You forgot to extract it with winrar or 7zip. make sure it is a .img file and not a .xz file.
Wow. I spent close to 7 hours trying and trying again. But that's what I get when I don't read all the instructions. -____-
Thanks very much. It works perfectly.
AgentXGhost said:
Wow. I spent close to 7 hours trying and trying again. But that's what I get when I don't read all the instructions. -____-
Click to expand...
Click to collapse
oh noes!
When in TWRP, the system is not mounted, and I cannot see it on my PC nor in TWRP itself. Any ideas what I did wrong?
Gurcharan5 said:
When in TWRP, the system is not mounted, and I cannot see it on my PC nor in TWRP itself. Any ideas what I did wrong?
Click to expand...
Click to collapse
Try going to wipe, then format data. That might fix the problem. If not, try everything again.