Database Info

cm-11.0 (Android 4.4) ROMs for Nexus Q: Amplifier, HDMI, and SPDIF

Hello,
Happy New Year!
Here are builds of Android 4.4 KitKat based on CM11 from repo sync on 1/3/2014 for Nexus Q. Please choose the correct one for your application depending on which audio output you need.
See the end of this post for details on issues and potential workarounds.
Please go easy on the downloads or mirror these files if desired. They are on my private server so bandwidth is limited.
TAS5713 (Audio Amplifier):
Download: https://www.androidfilehost.com/?fid=95784891001602454 (169MB)
MD5SUM: bca5d112bac1913e00635f658e149f5e *cm-11-20140103-UNOFFICIAL-steelhead_TAS5713.zip
SPDIF:
Download: https://www.androidfilehost.com/?fid=95784891001602452 (169MB)
MD5SUM: d11d8c67a89a411910b97e8979b51c4a *cm-11-20140103-UNOFFICIAL-steelhead_SPDIF.zip
HDMI:
Download: https://www.androidfilehost.com/?fid=95784891001602453 (169MB)
MD5SUM: 6a6d16839bb7451aa75dcfdecb6e7b5d *cm-11-20140103-UNOFFICIAL-steelhead_HDMI.zip
Recovery: https://www.androidfilehost.com/?fid=95784891001602454
MD5SUM: a37468b9dd990ce47ef406bd13c67c9b *cm-11.0-recovery.img
To install:
Boot into recovery mode:
Code:
fastboot boot cm-11.0-recovery.img
When Q has reached recovery mode:
1. choose "install zip"
2. choose "install zip from sideload"
From PC:
Code:
adb sideload cm-11-20140103-UNOFFICIAL-steelhead_TAS5713.zip
It is a good idea to wipe data and cache. If coming from my previous cm-11 image, it may be possible to avoid wiping data/cache.
Sideload gapps if desired:
pa_gapps-modular-full-4.4.2-20131230-signed.zip http://goo.im/devs/paranoidandroid/roms/gapps-full//pa_gapps-modular-full-4.4.2-20131230-signed.zip (208MB)
MD5SUM: 137dba382742312921ef7fa84585c62b
From within recovery, "install zip from sideload" and:
Code:
adb sideload pa_gapps-modular-full-4.4.2-20131230-signed.zip
If cm11 gets stuck in a boot loop, then you probably need to wipe. Reboot the Q back into fastboot as follows:
Unplug power for Nexus Q and wait about 10 seconds.
Plug Q back in. Do not put your hand on top of the Q until the small LED on top lights up.
When the LED lights up on the top of the Q, cover it with your hand until the LED ring turns red. This has to be done in less than one second. If you miss it, try again.
As soon as the ring is RED, remove your hand, and the Q should be in fastboot mode.
If you keep your hand on the Q while plugging it in, or if you put your hand on it too quickly, it will not enter the bootloader.​
Now, you can "fastboot -w" to wipe, or "fastboot boot recovery.img" to boot into recovery and wipe using the menu.
Please let me know how these work for you. I'm using these TAS5713 and CM 11 seems to be work, but there are some functional and stability issues.
FUNCTIONAL AND STABILITY ISSUES:
Chrome Browser in Google Play Store says it's not compatible with this device for some reason. Pulling the .apk off a phone and "adb install" to Nexus Q seems to work fine. Make sure you are using the latest Google Chrome update with KitKat support. The previous version will crash on KitKat.
If you find any other issues, please let me know.

Sorry but want to ask Google didn't release the code for auto switch audio output or something with license or others?
Another it is not recommend flash recovery into Q? As in your post use 'fastboot boot' not 'fastboot flash'.
Finally thanks for your work.

@maomao,
You don't want to flash recovery from fastboot. Just boot to recovery, flash CM, boot to system, then use flashify or rom manager or whatever to flash a recovery.
Sent from my Nexus 5 using Tapatalk

Hello, I tried installing via clockwork 6.0.3.7 but no luck. What version recovery is posted above? .....thank you for this!
Sent from my CM powered Nexus Q

Malnilion said:
@maomao,
You don't want to flash recovery from fastboot. Just boot to recovery, flash CM, boot to system, then use flashify or rom manager or whatever to flash a recovery.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
thx, but what's the difference between flash and boot the file from computer?
I used to flash the recovery use fastboot first and then flash the ROM on nexus, as the ROM manager also write the recovery partition, or I have something wrong?

which recovery is included in this post??
why is SPDIF and HDMI separate? aren't they usually together?
How is WLAN/WIFI speeds on this build? I know I had WIFI speed issues on other CM builds
Sent from my Nexus Q using Tapatalk 2
edit** : I have found out the hard way that this recovery needs to be first flashed before installing CM11
also WLAN/WIFI appears to be perfect and fast!
This has brought my Nexus Q back to life!!
Only thing needed now: Is a way to combine HDMI/SPDIF/AMP together, with a selectable output(s)

Let me clear up the recovery flashing vs booting. You can either flash or boot the recovery, it is up to you. If you flash it, it will persist across reboots/power cycles. If you just boot it, then it will load and run, but when you reboot, your device will still have whatever old recovery you had on it before. I got in the habit of booting rather than flashing the recovery, since I always start from fastboot. But feel free to flash the recovery if you want.
It is the stock Cyanogenmod recovery (clockwork, I think.)

hharte said:
Let me clear up the recovery flashing vs booting. You can either flash or boot the recovery, it is up to you. If you flash it, it will persist across reboots/power cycles. If you just boot it, then it will load and run, but when you reboot, your device will still have whatever old recovery you had on it before. I got in the habit of booting rather than flashing the recovery, since I always start from fastboot. But feel free to flash the recovery if you want.
It is the stock Cyanogenmod recovery (clockwork, I think.)
Click to expand...
Click to collapse
Why is SPDIF & HDMI not combined this time?

Thanks for the rom, i just flashed from cm10.2. no problems, everything seems to work fine.
Pity Cheapcast still gets stuck at the end of each song

Does anyone have a mirror of the HDMI version? I've tried downloading twice and it fails after about a half hour.
When/if I do get it to download correctly I will mirror as well.

El Daddy said:
Does anyone have a mirror of the HDMI version? I've tried downloading twice and it fails after about a half hour.
When/if I do get it to download correctly I will mirror as well.
Click to expand...
Click to collapse
Here you go, but please mirror if you can because I need to take it down within 48 hours.
EDIT: Link removed

ddggttff3 said:
Here you go, but please mirror if you can because I need to take it down within 48 hours.
Link removed
Click to expand...
Click to collapse
Thank you!
Here is the mirror: cm-11-20140103-UNOFFICIAL-steelhead_HDMI.zip - 169.28 MB

OP, noticed there's a bit of graphical tearing now and then when orientation changes or GPU heavy applications are ran. Also, there's a lot of logcat spam for a missing audio device when media is played. I am using the HDMI audio ROM.
Code:
E/audio_hw_steelhead( 4017): cannot open pcm_out driver: cannot open device '/dev/snd/pcmC0D0p': I/O error

Noticed some graphical tearing when orientation changes.
I cant change desktop background, anybody else with this problem?
otherwise it seems to work just fine. I have only used my Q with Spotify for 1 day so I may have missed some issues.

mannberg said:
Noticed some graphical tearing when orientation changes.
I cant change desktop background, anybody else with this problem?
otherwise it seems to work just fine. I have only used my Q with Spotify for 1 day so I may have missed some issues.
Click to expand...
Click to collapse
Somehow I did manage to change the background, but you're right, it didn't work as it should. I think after changing it (seemingly with no result) I quickly rebooted the device, and then the chosen wallpaper was already set.
I noticed some graphical glitches too: when clicking on recents button, the preview windows seem distorted.
Anyway I'm very happy with the overall performance and stability.
Sent from my Nexus S using Tapatalk

stock nexus q
hello i just got a nexus q from ebay and i wanted to flash it with kit kit. i am kind of lost on how to install the recovery image and install kit kit.
I know i need to use adb and sideload it in but how do i install the recovery initially?''
i got this far
c:\adb>adb sideload cm-11hdmi.zip
it won't let me sideload the image in
C:\adb>adb usb
restarting in USB mode
C:\adb>adb push update.zip /sdcard/
3387 KB/s (177504805 bytes in 51.176s)
C:\adb>
i can push it in but when i go to sdcard the nexus q restarts itself

ateam201 said:
hello i just got a nexus q from ebay and i wanted to flash it with kit kit. i am kind of lost on how to install the recovery image and install kit kit.
I know i need to use adb and sideload it in but how do i install the recovery initially?''
Click to expand...
Click to collapse
A quick guide.
Boot the Q to fastboot mode. Plug in the power cord, as soon as the center led on top of the Q lights up place your hand on the Q. When the led ring turns red remove it. You are now in fastboot. You need to unlock the bootloader, you can do this by using these commands from the command promt (cmd.exe in windows) I assume you have a usb connection between PC and your Nexus Q.
Code:
fastboot devices
it should show one device, if not switch usb port and try again. Or reinstall the drivers (Im using linux so I dont know if you need drivers on windows but I assume that)
Code:
fastboot oem_unlock
then directly after executing that command
Code:
fastboot oem_unlock_accept
Now you bootloader should be unlocked and you can boot to recovery. If you are not fast enough between these command, execute oem_unlock again and be faster this time. You boot to recovery with this command
Code:
fastboot boot cm11.0-recovery.img
Your Q reboots to recovery. Now select install zip -> install zip from sideload and execute
Code:
adb sideload cm-11-20140103-UNOFFICIAL-steelhead_HDMI.zip
wait for the installation to complete, sideload gapps if you need Play Store and apps like that from Google
Code:
adb sideload pa_gapps-modular-full-4.4.2-20131230-signed.zip
After the installation is completed, reboot your Q to fastboot again (Pull the power cord, place your hand over the Q and so on.... You need to do this to wipe data and cache. When the Q is in fastboot mode, execute
Code:
fastboot -w
Now you are done, reboot your Q and start setting it up. I hope I didn't miss anything but this should theoretically work

THE_KINGDOM said:
Why is SPDIF & HDMI not combined this time?
Click to expand...
Click to collapse
Anybody???

Trouble using adb / fastboot in windows 8
Problem solved.... appears to have problems with drivers....reinstalled and changed the usb port - installation went off without a glitch.
Thank you!
:good:
---------------
Is there a way for me to flash the cm11.0-recovery.img without using a pc? Having trouble using the PC to go through the process - fastboot does not recognize the - but adb does.
I am currently running cm10.1.....
Thank you.
mannberg said:
A quick guide.
Boot the Q to fastboot mode. Plug in the power cord, as soon as the center led on top of the Q lights up place your hand on the Q. When the led ring turns red remove it. You are now in fastboot. You need to unlock the bootloader, you can do this by using these commands from the command promt (cmd.exe in windows) I assume you have a usb connection between PC and your Nexus Q.
Code:
fastboot devices
it should show one device, if not switch usb port and try again. Or reinstall the drivers (Im using linux so I dont know if you need drivers on windows but I assume that)
Code:
fastboot oem_unlock
then directly after executing that command
Code:
fastboot oem_unlock_accept
Now you bootloader should be unlocked and you can boot to recovery. If you are not fast enough between these command, execute oem_unlock again and be faster this time. You boot to recovery with this command
Code:
fastboot boot cm11.0-recovery.img
Your Q reboots to recovery. Now select install zip -> install zip from sideload and execute
Code:
adb sideload cm-11-20140103-UNOFFICIAL-steelhead_HDMI.zip
wait for the installation to complete, sideload gapps if you need Play Store and apps like that from Google
Code:
adb sideload pa_gapps-modular-full-4.4.2-20131230-signed.zip
After the installation is completed, reboot your Q to fastboot again (Pull the power cord, place your hand over the Q and so on.... You need to do this to wipe data and cache. When the Q is in fastboot mode, execute
Code:
fastboot -w
Now you are done, reboot your Q and start setting it up. I hope I didn't miss anything but this should theoretically work
Click to expand...
Click to collapse

I'd love to see what changes you've made, Hharte. Any chance you'll post the source?

Unbrickable tf300t

Hello everyone. I am new around here and totally new with android devices. I got my tf300t, installed twrp and flashed to the newest android version. Then my dad suddendly pressed something like restore to the manufactory setting and after that it rebooted and just keep booting with teamwin logo. I can not access twrp recovery mod, it is just in boot loop. I managed to get adb to work, but no fastboot since it does not boot into recovery mode. When I am in adb I can browse the device but the adb reboot bootloader does not work at all. It just hangs there. I can not power off the device because it does not let me, I can not boot into recovery mode with powerbutton and volume down button. After a long power button press it only reboots. I even tried with hard reset button but still the same. Could You please help me somehow? I really need that device for school and I would like to get back into the stock android. Thank you so much for any help.
//edit : I also forget to mention, when I execute adb deviced it shows:
List of devices attached
0123456789ABCDEF recovery
Also the device is unlocked.

Did you tried: adb reboot recovery ?
Did you tried to flash recovery again?
Be sure to use the right recovery for your bootloader. Did you upgraded bootloader to latest ASUS one? One then you're able to flash current recoveries like TWRP like 2.8.5.0 oder 2.8.7.0.
Edit: Also take a look here -> http://droidmodderx.com/prime/?page_id=74

Hello sir. Thank you for answering. I tried adb reboot recovery and it just hangs to be executed... But the tablet is still flashing the teamwin logo. I have the same bootloop as the guy on youtube called Francis Domingo and video called Samsung s5 stuck at TWRP Recovery boot loop (unfortunately I can not add link here).
//edit: Thank you for the link. It look like I have to use option 1a. Is it safe to use that command and I will not make it even more bricked? Thank you so much
//edit2: Now I just realized how to turn off the device to stop from rebooting. I just long pressed power button and up volume button and after the screen went black I kept holding the up volume button. I didn't work with down volume button or if I stopped holding the up volume button after black screen it rebooted again.
//edit3 : Let's say if I get to the twrp mode with option 1a from the link, what do I have to do next to get back to the stock rom (I think it was something like 4.0.3) ? Thank you

What the guy does in 1a is wiping mmcblk0p3.
Afaik mmcblk0p3 is the staging partition. That would be my guess anyway if you had access to fastboot. Usally when you can't boot into recovery, something is wrong in staging. I got the same problem 2 days ago. In this case you usually wipe staging partition via fastboot.
Since you got no fastboot access, you have to try with adb.
After cleaning the staging partition you can flash any recovery you want back again.
The recovery must be flashed to mmcblk0p4 <- 4!!! is the recovery partition. (but you should wipe mmcblk0p3 (3!!!) before)
So I would say, try what solution 1a suggests.
Edit: You can go back to stock android if you want, but there is no reason for this. My advice would be to unlock and root your device, upgrade to latest boot loader (which is done by upgrading to latest stock rom), then flash TWRP 2.8.5.0 and then a useful ROM on top. I'm using the one from timduru which is very nice. You can find it here: http://forum.xda-developers.com/transformer-tf300t/development/rom-t2932783

Thank you for the answer. Could you please write a step by step to get out of brick and to get the stock version, because the newer one I installed was many times slower. The reason why I would like to have step by step is because I don't wanna mess it even more than it is. Thank you so much.
//the stock rom was much more faster than the one I have installed, I mean... the boot time wad unbelievable slow, same with responses and wifi problem. If there is any other faster rom than stock I would be happy but I don't wanna mess with any bugs or slow boot speed and I can not wait minutes until it boots.

Hm, try the Option 1a from the link.
If done, boot into current recovery. Tell me which version and which recovery do you have.
Top on this we can decide what to do to flash a good ROM.

I had the exact same thing happen to me yesterday. Option #1 worked for me.
I did the steps from option #1 and powered down using the volume up + power. I then tried to boot into TWRP recovery, which only reproduced the same issue.
I redid the option #1 steps, and this time powered down using the power + volume down. I powered back up normally, and it rebooted normally into the ROM.
The tablet now works normally, and I can also boot back into TWRP recovery with no issues.
Thanks for the thread and the link.

Thank you so much Catscratch! After I executed both command from option 1a I can get into the screen, where it shows three options: RCK, Android, Wipe Data
In the top left corner, there is written:
Key driver not found.. Booting OS
Android cardhu-user bootloader <1.00 e> released by "WW_epad-10.6.1.27.5-20130902" A03
Starting Fastboot USB download protocol
The tablet can boot into the last ROM but as I said, I would like to have the faster and less buggy rom than this. When I open the settings and click about button there is written: CyanongenMod: 12.1-20150814-NIGHTLY-tf300t and Android version 5.1.1.
If I start RCK it just brings me back to the loop, but now I have fastboot available as it said above and I can list the fastboot devices on computer, which I couldn't before. Should I just execute this command from the computer "fastboot -i 0x0B05 flash system blob" and then "fastboot reboot" or should I download ROM from asus.com/Tablets/ASUS_Transformer_Pad_TF300T/HelpDesk_Download/ -> OS Android -> Firmware and now I don't know which should I choose: If JP or CN or WW or US or TW (Probably US right?). After that should I execute "fastboot -i 0x0B05 flash recovery firmware.img" and then "fastboot reboot" ? Or which ROM should I download to make it even faster and less buggy than stock ROM? Thank you so much again, You saved my tablet
//After I unzipped downloaded US ROM there is no img file. If I remember right the img file is only recovery to reflash the actual one and then when I start the twrp recovery I will select zip file with rom right?

OK, first of all to continue...I assume you got root access. (I think you should have, because you already got CM installed)
Next. Downloads.
Download: https://twrp.me/devices/asusTF300T.html
Also Download ROM+SuperSU: http://forum.xda-developers.com/transformer-tf300t/development/rom-t2932783
And GApps: http://forum.xda-developers.com/android/software/app-minimal-gapps-gapps-lp-20150107-1-t2997368
Push all files to sdcard with "adp push" or in CM. Like you want.
Flash TWRP. (you can skip this step if you already got TWRP 2.8.5.0 or higher version). You don't need latest one.
fastboot -i 0x0b05 flash recovery twrp.img
fastboot reboot
- or -
adb reboot recovery
Now, go into recovery and wipe everything:
- cache
- dalvik
- system
- data
After that flash ZIPs from sdcard. (use "add more zips" option)
1. ROM
2. Gapps
3. SuperSU
Next: Wipe cache and dalvik again (only these two).
Reboot and wait. First boot can take some minutes.

Thank you so much again. Everything work perfectly The rom looks a lot faster than the older one I had there. No issues yet at all. Just awesome. Thank you so much. Really appreciate your kindness and help. You have a nice day !

Thanks. Have fun with your tf300.

[TREBLE][Oreo][How-To] Install any Generic System Image (GSI) on the Razer Phone

Hello everyone,
I've been tinkering around with Generic System Images since the Oreo Developer Preview 1 came out for the Razer Phone. I'm glad to say I got it to work, with lots of help from @MishaalRahman, @P4Block and indirect help of @phhusson and @TheCrazyLex.
What's working as of right now:
- GPS
- Rear Camera (only one of the lenses, needs further testing/pulling the Razer camera app apk)
- Front camera
- Microphones
- Sensors, each and every of them
- Speakers, sound playback, videoplayback (needs further testing)
- Fingerprint scanner
- WiFi, Bluetooth, NFC
- 120Hz screen features
- Color adjustments from the Oreo DP1 by Razer
- 4G LTE
- In-Call audio
What needs further testing:
- 4G/LTE FIXED check out post #77!
- Once the above is confirmed to work => VoLTE on any carrier, and also testing on certain carriers like 3 UK (since they sold a version with different software).
What's broken:
- Audio in phone calls (works properly in VoIP/3rd party apps) FIXED check out post #48!​
What ROMs can be booted with this (as of 30-03-2018):
AOSP 8.1
Lineage OS 15.1
Resurrection Remix
More to come...
Setting up your device:
You'll need:
Code:
To [URL="https://forum.xda-developers.com/razer-phone/how-to/guide-to-unlocking-bootloader-t3706462"]fully unlock your bootloader[/URL] and [URL="https://forum.xda-developers.com/showpost.php?p=74607352&postcount=8"]unlock flashing capabilities[/URL] on your device.
[URL="https://eu.dl.twrp.me/cheryl/twrp-3.2.1-0-cheryl.img.html"]TWRP image[/URL] + [URL="https://eu.dl.twrp.me/cheryl/twrp-installer-3.2.1-0-cheryl.zip.html"]TWRP injector[/URL]
[URL="http://tiny.cc/latestmagisk"]Magisk flashable zip[/URL]
A GSI of your preference from the ones listed [URL="https://forum.xda-developers.com/project-treble/trebleenabled-device-development"]here[/URL]. PS: Use the Gapps+SU one if you choose AOSP ;)
0. Make sure you're running the Android O DP1 from Razer, or any future update to it.
THIS WON'T WORK ON NOUGAT
1. Properly install TWRP on your device: (I'll be using @Dees_Troy's guide with a few modifications to make very sure everything will work as intended)
- fastboot flash the twrp image as explained by him, in your currently active boot partition. PS: After flashing the Android O DP1, it will always be A.
Dees_Troy said:
Once you have adb working, run this command: adb shell getprop ro.boot.slot_suffix
It should say: [ro.boot.slot_suffix]: [_a] Or: [ro.boot.slot_suffix]: [_b]
Make note of whether you are currently using slot A or B. Next power off the device and boot to the bootloader using your USB cable and volume down. You want to switch to the other boot slot. If you are currently on slot A, type this: fastboot --set-active=_b Or on slot B type this: fastboot --set-active=_a
You should see something like this: Setting current slot to 'a'... OKAY [ 0.042s] finished. total time: 0.042s
I found the bootloader on the Razer Phone to be extremely finicky and I had to run the command multiple times until I got it to run successfully. You may have to hold the power button for 15 seconds to force power off the device and then re-enter fastboot mode. Keep trying until it works. Once it's on the right boot slot, type this: fastboot flash boot twrp-3.2.1-0-cheryl.img && fastboot reboot
Click to expand...
Click to collapse
2. Once you're in TWRP, DO NOT SLIDE to allow modifications, but tap on Mount as Read Only. Plug in your USB cable, and adb push the boot image from the Android O DP1 factory image to your sdcard, as well as the TWRP injector and the Magisk zip. That can be done with the following commands:
Code:
adb push twrp-installer-3.2.1-0-cheryl.zip /sdcard
Code:
adb push path/to/the/factoryimage/boot.img /sdcard
Code:
adb push Magisk-16.0.zip /sdcard
3. Go into Reboot, then make sure you're on partition A. Else, tap on the button to set A as the active partition.
Now go back, tap Install, then tap on 'Install Image' then choose the boot.img you just pushed, and flash it as boot image.
Now go back, into Reboot, and move to partition B and repeat the step above.
Once you're sure both partitions only contain the unmodified boot images, set the partition A as active, go into Install, choose the twrp-installer-3.2.1-0-cheryl.zip and flash it.
Once it finishes, do the same with the Magisk zip file.
4. Go into Reboot, press on Bootloader.
5. Connect the usb cable, and flash the GSI system image onto your system_a partition through fastboot from your pc. This can be done with the command:
Code:
fastboot flash system_a system-arm64-ab.img
5.b If you wish, you can install a different GSI onto your system_b partition, and that can be done with the following commands:
Code:
fastboot set_active b
Code:
fastboot flash system_b system-arm64-ab-gapps-su.img
5.c If you wish to go back to the system_a partition, you can execute:
Code:
fastboot set_active a
6. Reboot and enjoy.​Prebuilt boot image:
If doing the steps from 1-4 seems messy or you don't get it to work properly, I've published the image I made following them with the latest Magisk and TWRP versions available as of April 20th 2018.
You can download it from here. You can then flash it from fastboot by using the commands:
Code:
fastboot flash boot_a boot_linuxct_20180420_cheryl_omr0.img
Code:
fastboot flash boot_b boot_linuxct_20180420_cheryl_omr0.img
SHA-2: 2f0c7348ac906f2f81fa39df7b24b69392783bd2379d5da357777be444c67d97​
Old version (from ODP1 - may experience the bootloader issues):
You can download it from here. You can then flash it from fastboot by using the commands:
Code:
fastboot flash boot_a boot_linuxct_20180330_cheryl_odp1.img
Code:
fastboot flash boot_b boot_linuxct_20180330_cheryl_odp1.img
SHA-2: 8f763162415167b2e919a450654f9a46f69b81f6853013bcabf362dfeb2a115e
Many thanks to everyone that helped me today to get this to work properly!

Want some screenshots?

Thanks for all the hard work!
I've followed the guide but after flashing the GSI I get stuck at the Android logo and the system never boots?
Any help would be appreciated

PupPupG said:
Thanks for all the hard work!
I've followed the guide but after flashing the GSI I get stuck at the Android logo and the system never boots?
Any help would be appreciated
Click to expand...
Click to collapse
Did you follow all the steps carefully? Did you make sure you flashed Magisk?
Magisk is needed since it disables DM-Verity, which is what IMO gets the device stuck at first boot.
Oh, and also, sometimes during first boot your device gets encrypted. Mine took a bit extra that time (specifically booting the LineageOS image).
If you can't still get it to work, try with the prebuilt boot image.

This is awesome!!!
I'd love to have a fully working resurrection remix build working on my cheryl!!!!! =D <3
KEEP UP THIS AWESOME WORK!!!!!!!!!

linuxct said:
Did you follow all the steps carefully? Did you make sure you flashed Magisk?
Magisk is needed since it disables DM-Verity, which is what IMO gets the device stuck at first boot.
Oh, and also, sometimes during first boot your device gets encrypted. Mine took a bit extra that time (specifically booting the LineageOS image).
If you can't still get it to work, try with the prebuilt boot image.
Click to expand...
Click to collapse
I tried again using all of the info but they closest I've gotten to a boot is the Android logo and then a prompt to decrypt but no matter what I enter I get "Decryption Unsuccessful" and it just brings me back to TWRP

PupPupG said:
I tried again using all of the info but they closest I've gotten to a boot is the Android logo and then a prompt to decrypt but no matter what I enter I get "Decryption Unsuccessful" and it just brings me back to TWRP
Click to expand...
Click to collapse
Flash the Oreo DP1 image and start over.

linuxct said:
Flash the Oreo DP1 image and start over.
Click to expand...
Click to collapse
From what I can tell, TWRP cannot format the data partition properly which is what causes LOS to appear as encrypted and won't finish booting. I was able to successfully able to get it to boot by flashing the stock boot.img and booting to stock recovery and factory reset that way. After doing that, flash your ROM of choice and Magisk and it should be usable.

ThatGuy94 said:
From what I can tell, TWRP cannot format the data partition properly which is what causes LOS to appear as encrypted and won't finish booting. I was able to successfully able to get it to boot by flashing the stock boot.img and booting to stock recovery and factory reset that way. After doing that, flash your ROM of choice and Magisk and it should be usable.
Click to expand...
Click to collapse
Flashing the Oreo DP1 image actually flashes an empty, non-encrypted userdata image. That's why I requested to start over.
That can also be another solution, bit messier than starting over but it's good.

Does anyone have Magisk fully working with this? I still get ctsprofile:false
Aside from this, excellent work!

M1cky said:
Does anyone have Magisk fully working with this? I still get ctsprofile:false
Aside from this, excellent work!
Click to expand...
Click to collapse
I do. Try installing the latest beta of Magisk and then, if that didn't solve it, try setting a new Build fingerprint with a tool like MagiskHide Props Config (PS. Just to be sure, set the Google Pixel 2 XL one since that's the only 8.1.0 build fingerprint provided by that tool).

ThatGuy94 said:
From what I can tell, TWRP cannot format the data partition properly which is what causes LOS to appear as encrypted and won't finish booting. I was able to successfully able to get it to boot by flashing the stock boot.img and booting to stock recovery and factory reset that way. After doing that, flash your ROM of choice and Magisk and it should be usable.
Click to expand...
Click to collapse
Could you please tell me how you flash Magisk? After I flash a ROM I'm not able to boot into TWRP to flash Magisk

Happy to see people making use of Treble on Razer Phone this quickly.
Good job! @linuxct

Have no idea where I went wrong but after I had RR up and running I rebooted and It went into download mode.

RUNNERX said:
Have no idea where I went wrong but after I had RR up and running I rebooted and It went into download mode.
Click to expand...
Click to collapse
Yes, it happens sometimes. Let me explain this briefly:
1. This bootloader seems to forget what the active partition was when it was told to reboot the device instead of turning itself off, and I don't know why yet. It happens 1/5 times I press on "Reboot", more or less.
2. You need to re-set the active partition to the one you were using, in my case A, so with a cable and my pc I run
Code:
fastboot set_active a && fastboot reboot
Tired of typing, I made myself a script named razer in my /usr/bin
Code:
#!/bin/zsh
fastboot set_active a && fastboot reboot
So, be careful when rebooting the device if you don't have a close-by PC with fastboot to make it work again, instead, fully turn it off and turn it back on.

el4nimal said:
Could you please tell me how you flash Magisk? After I flash a ROM I'm not able to boot into TWRP to flash Magisk
Click to expand...
Click to collapse
Just fire up a terminal with ADB and type in
Code:
adb reboot recovery
It should be more than enough, no need for root privileges or anything.

linuxct said:
Just fire up a terminal with ADB and type in
Code:
adb reboot recovery
It should be more than enough, no need for root privileges or anything.
Click to expand...
Click to collapse
I'm trying to boot into LineageOS 15.1 but it keeps saying "Decryption Unsuccessful". I followed your guide step by step, and I also tried the pre-built image you provided.
I started over from Oreo DP1 image many times and I've been getting the same error over and over again.
Then, I noticed that @ThatGuy94 mentioned he was able to get it to boot, by flashing stock boot.img and factory reset it that way, and then install the ROM and Magisk.
But I can't figure out how to install Magisk without installing TWRP, is there any fastboot command to install Magisk from the command line?

Resurrection Remix Intensifies

el4nimal said:
I'm trying to boot into LineageOS 15.1 but it keeps saying "Decryption Unsuccessful". I followed your guide step by step, and I also tried the pre-built image you provided.
I started over from Oreo DP1 image many times and I've been getting the same error over and over again.
Then, I noticed that @ThatGuy94 mentioned he was able to get it to boot, by flashing stock boot.img and factory reset it that way, and then install the ROM and Magisk.
But I can't figure out how to install Magisk without installing TWRP, is there any fastboot command to install Magisk from the command line?
Click to expand...
Click to collapse
Unless you have overwritten it, boot to download mode and use fastboot to switch to the other slot which will allow you to boot into TWRP and install Magisk. If you have overwritten TWRP, flash it on the other slot (for example if you have LOS installed in A, flash TWRP into B).

linuxct said:
So, be careful when rebooting the device if you don't have a close-by PC with fastboot to make it work again, instead, fully turn it off and turn it back on.
Click to expand...
Click to collapse
It has happened after a power off also, would putting the same rom in a&b slot stop it? system_other is not bootable so the phone enters download mode? I don't understand the working of the a/b system.
And THANK YOU so much for working on this, so nice to be back on custom roms!

[FINAL][RECOVERY][Z010D]ASUS Zenfone Max ZC550KL Marshmallow

Introduction
I've been researching on how to install TWRP on Zenfone Max with Final Marshmallow update for a long time, and finally found and gathered information on how to do so without any consequences. So if you're on final Marshmallow update and want to install TWRP on your phone, then this guide is for you! P.S. This is for Z010D only.
How To Install TWRP
1. Download this APK on your phone to unlock your bootloader : https://drive.google.com/open?id=0B-0qEY9zypslUTFKRE5CQUU5OFk
The app says it will wipe all data, but with my experience it doesn't wipe any data at all. However, I still recommend you to take a backup.
2. Download this zip to your computer and extract it : https://drive.google.com/file/d/0B2kFletApi72QkRLZnFURDUyZk0/view
3. Download this TWRP 3.2.3-0 image : https://sourceforge.net/projects/an...covery/TWRP-3.2.3-Z010D-20180729.img/download
4. Merge the TWRP 3.2.3 image to the extracted zip
5. Make sure you have USB Debugging on and put your phone into Fastboot mode [Hold Volume Up + Power] and connect it to the computer
6. In the extracted zip folder search bar, type 'cmd' and press Enter
7. Type 'fastboot devices' and press Enter, to see if your phone is detected
8. Type 'fastboot flash recovery TWRP-3.2.3-Z010D-20180729.img' and press Enter
9. Disconnect the phone and Hold 'Volume Down + Power', when you see the ASUS logo let go the Power, but keep holding Volume Down until you see the TWRP logo
Congratulations, you've successfully installed TWRP!
Video
If you're too lazy to read like me, here's the video : https://www.youtube.com/watch?v=EwuiHBIts7M

WhatzIt2Ya said:
Introduction
I've been researching on how to install TWRP on Zenfone Max with Final Marshmallow update for a long time, and finally found and gathered information on how to do so without any consequences. So if you're on final Marshmallow update and want to install TWRP on your phone, then this guide is for you!
Before We Get Started
Download these files on your phone and move it to the root of the storage :
1. Magisk 17.1 : https://github.com/topjohnwu/Magisk/releases/download/v17.1/Magisk-v17.1.zip
2. (Optional) TWRP 3.1.1 image : https://androidfilehost.com/?fid=745849072291687209
How To Install TWRP
1. Download this APK on your phone to unlock your bootloader : https://drive.google.com/open?id=0B-0qEY9zypslUTFKRE5CQUU5OFk
The app says it will wipe all data, but with my experience it doesn't wipe any data at all. However, I still recommend you to take a backup.
2. Download this zip to your computer and extract it : https://drive.google.com/file/d/0B2kFletApi72QkRLZnFURDUyZk0/view
3. Make sure you have USB Debugging on and put your phone into Fastboot mode [Hold Volume Up + Power] and connect it to the computer
4. In the extracted zip folder search bar, type 'cmd' and press Enter
5. Type 'fastboot devices' and press Enter, to see if your phone is detected
6. Type 'fastboot flash recovery Z010_3.0.0.t1_without_su.img' and press Enter
7. Disconnect the phone and Hold 'Volume Down + Power', when you see the ASUS logo let go the Power, but keep holding Volume Down until you see the TWRP logo
Congratulations, you've successfully installed TWRP!
Optional If you've downloaded TWRP 3.1.1 image, headover to 'Install' and select 'Install Image', then select the TWRP 3.1.1 image, then select Recovery and finally swipe to flash to update TWRP. To reboot back into recovery, press home, select reboot, and then recovery. You should see the TWRP version 3.1.1 upon reboot.
How To Root with TWRP
1. Boot into recovery and select 'Install'
2. Select Magisk zip and swipe to flash
3. Reboot to your OS, you should see a new app that is Magisk
Congratulations, you've successfully installed TWRP and Magisk!
Video
If you're too lazy to read like me, here's the video : https://www.youtube.com/watch?v=EwuiHBIts7M
Click to expand...
Click to collapse
Hey bro , seems you've been in mars and just arrived on Earth ! There's no issue whatsoever with installing twrp and rooting ZC550KL, there are lots of threads and video on YouTube about this for more than a year now.

jide1 said:
Hey bro , seems you've been in mars and just arrived on Earth ! There's no issue whatsoever with installing twrp and rooting ZC550KL, there are lots of threads and video on YouTube about this for more than a year now.
Click to expand...
Click to collapse
Yes, but some comments have issues where will it work with different versions (or updates), as the last update ASUS pushed was around Dec 17/Jan 18 with November 2017 security patch, some of the guides I've tried have failed, or had some issues. Also, some guides tell you to downgrade to marshmallow beta. Anyways, I just thought to do a final guide to root. ?

WhatzIt2Ya said:
Yes, but some comments have issues where will it work with different versions (or updates), as the last update ASUS pushed was around Dec 17/Jan 18 with November 2017 security patch, some of the guides I've tried have failed, or had some issues. Also, some guides tell you to downgrade to marshmallow beta. Anyways, I just thought to do a final guide to root.
Click to expand...
Click to collapse
so basically, is it all about unlocking the bootloader something to root the phone or what?

Singhisme said:
so basically, is it all about unlocking the bootloader something to root the phone or what?
Click to expand...
Click to collapse
Obviously, you need an unlocked bootloader to do any modifications! The only issue is, Asus phones don't show whether you have an unlocked bootloader or not. Sometimes the bootloader unlocker fails.

Jt380p said:
Obviously, you need an unlocked bootloader to do any modifications! The only issue is, Asus phones don't show whether you have an unlocked bootloader or not. Sometimes the bootloader unlocker fails.
Click to expand...
Click to collapse
Then how to be sure my device is locked or unlocked then?

Singhisme said:
Then how to be sure my device is locked or unlocked then?
Click to expand...
Click to collapse
Theres no sign. You just have to trust the app, unfortunately.

Urgent
Hi sir same way i did but TWRP is not showing.only black screen is displaying and i cant restart my phone please help me sir

twrp not showing

Jt380p said:
Theres no sign. You just have to trust the app, unfortunately.
Click to expand...
Click to collapse
I figure it out somehow.. there's something to do with ADB to check by this far it is the only way I know. thanks for the TWRP btw.. Good works!

Jt380p said:
Introduction
I've been researching on how to install TWRP on Zenfone Max with Final Marshmallow update for a long time, and finally found and gathered information on how to do so without any consequences. So if you're on final Marshmallow update and want to install TWRP on your phone, then this guide is for you! P.S. This is for Z010D only.
How To Install TWRP
1. Download this APK on your phone to unlock your bootloader : https://drive.google.com/open?id=0B-0qEY9zypslUTFKRE5CQUU5OFk
The app says it will wipe all data, but with my experience it doesn't wipe any data at all. However, I still recommend you to take a backup.
2. Download this zip to your computer and extract it : https://drive.google.com/file/d/0B2kFletApi72QkRLZnFURDUyZk0/view
3. Download this TWRP 3.2.3-0 image : https://sourceforge.net/projects/an...covery/TWRP-3.2.3-Z010D-20180729.img/download
4. Merge the TWRP 3.2.3 image to the extracted zip
5. Make sure you have USB Debugging on and put your phone into Fastboot mode [Hold Volume Up + Power] and connect it to the computer
6. In the extracted zip folder search bar, type 'cmd' and press Enter
7. Type 'fastboot devices' and press Enter, to see if your phone is detected
8. Type 'fastboot flash recovery TWRP-3.2.3-Z010D-20180729.img' and press Enter
9. Disconnect the phone and Hold 'Volume Down + Power', when you see the ASUS logo let go the Power, but keep holding Volume Down until you see the TWRP logo
Congratulations, you've successfully installed TWRP!
Video
If you're too lazy to read like me, here's the video :
Click to expand...
Click to collapse
anyone have working oem unlock tool for asus zenfone max (zc550kl).
tried so many tools,nothing worked for me

Android_Rom_OTA for ASUS Zenfone Max ZC550KL[Z010D]​

Android_Rom_OTA: ​
Released /LineageOS-OMS/Z010D/lineage-14.1-20180821-UNOFFICIAL-Z010D-OMS.zip​
Released /OreoTest/lineage-15.1-20180817-UNOFFICIAL-Z010D.zip​
Released /TWRP_Recovery/TWRP-3.2.3-Z010D-20180729.img​
Released /LineageOS/Z010D/lineage-14.1-20180729-UNOFFICIAL-Z010D.zip​
Download Android_Rom_OTA​

[RECOVERY][STOCK]TWRP 3.3.1-0 UNOFFICIAL

Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
THIS RECOVERY IS FOR STOCK ROM AND WILL NOT WORK ON CUSTOM ROMS
Code:
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this recovery
* before using it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Bugs:
- The "fastboot boot twrp.img" doesn't work, if you use the hardware buttons to open the blue fastboot bootloader mode. Only use adb, twrp or the android system to reboot into blue fastboot bootloader mode or flash the twrp.img, boot the device, reboot into bootloader and flash the original boot.img back, before booting into twrp.
You can also "fastboot reboot bootloader" in the blue fastboot mode.
This is a bootloader bug, maybe it gets fixed with the stock Q bootloader.
- Decrypt is not working for now (Is probably because the current stock firmware is still on May security patch - will be fixed with June/July patch)
- Touch not working when installed
- Please report any other bugs
Install guide:
Installing is currently not recommended because touch is not working on the installed version!
1. Install fastboot tools from google's sdk on your PC
2. Enter fastboot mode from adb
3. Unlock your bootloader
4. Run "fastboot boot twrp.img" in command line
6. Enjoy it
Optional (if you want to install it):
1. Boot from it (see the guide above)
2. Go to advanced -> Install recovery ramdisk
3. Choose the twrp img
4. Wait
5. You can now boot it with vol- and power button
If it keeps booting into TWRP and not System try
Code:
adb shell dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc
Download
Changelogs:
3.3.1-0 03.08.2019
- Initial Release
Source code:
https://github.com/Schritti/device-sony-mermaid
https://github.com/Schritti/device-sony-ganges
If you like my work, press thanks
I would appreciate your Donation
Thanks to:
@MartinX3 for helping me developing the TWRP
@Oshmoun for providing device trees for Ganges and Mermaid
@naoki2010 for Testing
XDA:DevDB Information
TWRP, ROM for the Sony Xperia X10 Plus
Contributors
Schritti, MartinX3, Oshmoun, Marijn
ROM OS Version: 9.x Pie
ROM Firmware Required: Stock Pie Firmware
Version Information
Status: Beta
Current Beta Version: 3.3.1-0
Beta Release Date: 2019-08-03
Created 2019-08-03
Last Updated 2019-08-05

Reserved

Reserved

Woohooo!
First!

My computer is down at the moment but I have a question does this supports the North American unlocked variant i3223? I looked at your sources and I don't see the i3223 variant.

sickkside13 said:
My computer is down at the moment but I have a question does this supports the North American unlocked variant i3223? I looked at your sources and I don't see the i3223 variant.
Click to expand...
Click to collapse
All variants are supported

I am having the worst time trying to get this device (i3223 variant) into recovery or into fastboot mode so I can boot into recovery via adb. The device is pattern locked and wasnt adb enabled before hand. I can get to where the light flashes blue after holding vol up while inserting usb but screen is blank then goes to a charging screen. I want to erase and test on this device. Its been a couple days and drivers are correct emma doesnt work and the sony companion wont recognize the device only that its locked. any help?

clothtalklp said:
I am having the worst time trying to get this device (i3223 variant) into recovery or into fastboot mode so I can boot into recovery via adb. The device is pattern locked and wasnt adb enabled before hand. I can get to where the light flashes blue after holding vol up while inserting usb but screen is blank then goes to a charging screen. I want to erase and test on this device. Its been a couple days and drivers are correct emma doesnt work and the sony companion wont recognize the device only that its locked. any help?
Click to expand...
Click to collapse
It's normal, that the screen is black in fastboot mode. If the LED is Blue then it's alright.
When you're in fastboot mode (Blue LED) check the windows device manager, you might install the driver again for fastboot. If it shows a device called "Android" you have to right click it and install the correct driver.

I just got the phone unlocked so i will boot into TWRP and install it and debug the touch. I have the feeling that it might be just missing file.

I just tested the installed version of TWRP and touch works just fine. The TWRP on itself is little slow. Decryption is broken and we see just bunch of junk folders in internal storage as expected.
But decryption shoudlnt be an issue after i bake TWRP into my AOSP images.
Rebooting into OS is totally broken and even cleaning misc doesnt help. Boots to TWRP all the time. Again most likely just an issue that it was not installed in boot.img right away but had to be added.

So about unlocking - my device/version isn't supported to unlock. Any hints?

mad-murdock said:
So about unlocking - my device/version isn't supported to unlock. Any hints?
Click to expand...
Click to collapse
You cant unlock bootloader. Thats just it. Did you buy the device from carrier ? If so they have usually not unlockable devices.

Haxk20 said:
You cant unlock bootloader. Thats just it. Did you buy the device from carrier ? If so they have usually not unlockable devices.
Click to expand...
Click to collapse
bought it used super cheap, wanted to play with it and maybe help a bit with development. but määä - seems like not.
do you think the device might become unlockable with a future firmware update? i am more a oneplus user and have little experience with sony.

mad-murdock said:
bought it used super cheap, wanted to play with it and maybe help a bit with development. but määä - seems like not.
do you think the device might become unlockable with a future firmware update? i am more a oneplus user and have little experience with sony.
Click to expand...
Click to collapse
Sadly I do not think so. We would love another dev helping on SonyOpenSourceDevices or even custom ROMs but sadly if the phone is not unlockable there is nothing you can do sadly. I heard stories of people having carrier phones sim locked and after unlocking that they were able to unlock BT so you could possibly try that if the phone is locked to 1 carrier. If not then there i s really nothing you can do. I'm sorry.

Hi,
first off a big thank you!
I would like to root my xperia 10 plus I4213. I tried to do my homework before posting here, but since I am not knowledgeable on the subject, can someone confirm that these are the right steps:
1. Enable in phone third party apps, unlock developer settings, enable adb.
2. Boot in fastboot mode. That can be done in terminal, not by using buttons as it used to.
3. unlock bootloader . My understanding if that now, that can be achieved either via terminal or via windows newsflasher program.
4. Flash recovery from this thread
4. Boot into system and install magisk manager .
5. Install via recovery Magisk zip.
6, Boot into system and use magisk manager to enable root and set settings.
Should I install latest magisk 20.1 or an earlier version?
Thank you.

Problem with TWRP
Why is the device memory data encrypted even though the device doesn 't have a password?

reintal said:
Why is the device memory data encrypted even though the device doesn 't have a password?
Click to expand...
Click to collapse
That is how your internal storage looks like when encryption is just Ffkjgh up.
This recovery dont have any updates and well its just broken for now. sadly.

Haxk20 said:
That is how your internal storage looks like when encryption is just Ffkjgh up.
This recovery dont have any updates and well its just broken for now. sadly.
Click to expand...
Click to collapse
It sounds sadly 'cause in that case it is not possible for me to install magisk on the standard firmware and I cannot use gpay anyway.

reintal said:
It sounds sadly 'cause in that case it is not possible for me to install magisk on the standard firmware and I cannot use gpay anyway.
Click to expand...
Click to collapse
We are mainly focus on making AOSP 10 stable now and TWRP is not on top of the list to fix now. And TWRP doesn't support Android 10 yet so we can't even begin.