Custom Android ROM

[Mindovermaster Moderator]

I know there are several out there.

 

But everything I see is shady, I don't get what this or that means.

 

Here is the phone I am trying to customize. ASUS Z00TD: http://specdevice.com/showspec.php?id=4868-a306-3855-870856b0f887

 

I see Lineage guides, but they do not tell you EVERYTHING you need to know.

 

https://forum.xda-developers.com/zenfone-2-laser/orig-development/rom-lineageos-15-0-t3666743

 

Can someone run me through this, or maybe I can just send it to you to get modded. (Did for a PSP once, friend installed like 100 enulation games on it, from NES, SNES, GB...)

Edited August 29, 2019 by Mindovermaster

[DKAngel]

https://forum.xda-developers.com/zenfone-2-laser/development/rom-lineageos-15-1-t3771376

maybe read that as that thread is dead

 

[Nick H. Supervisor]

4 hours ago, Mindovermaster said:

Can someone run me through this

You're going to need to be a bit more specific. Are you asking for a step-by-step guide, or is there a particular part that you need help with? When you say that it looks shady, which aspect are you referring to? You say that they do not tell you everything you need to know, what exactly do you need to know?

 

I've not installed Lineage on a phone before, but it's pretty much the idea that if you've installed one custom ROM you can install any others, so if you can provide more details I'd be happy to help.

[Dick Montage]

Nothing "shady" at all there?

[Mindovermaster Moderator]

Make sure your computer has working adb and fastboot. Setup instructions can be found here.

 

I am currently on ArcoLinux (based on Arch). I don't see adb and fastboot in AUR/Pacman.

 

https://wiki.lineageos.org/devices/bacon/install

[+InsaneNutter MVC]

Generally before you can flash a custom rom you need to do the following:

 

1. Backup your data

2. Unlock the boot loader (will usually wipe your device, hence backing up first)

3. Flash a custom recovery, this is TWRP for most devices.

4. Backup your stock rom

5. Flash a custom rom

 

The process will vary from device to device, however usually fastboot will be used to unlock your bootloader and flash a recovery.

 

You want to install the android-tools package which includes fastboot would seem: https://wiki.archlinux.org/index.php/Android#Flashing

 

After that you should be able to follow the tutorials on XDA for your device, the process can vary a bit depending on the device. However you generally need an unlocked bootloader and custom recovery.

 

Once you have both of these you can load the recovery on your device and flash a new rom any time you desire.

 

You have many choices for custom roms, generally i stick to the official LineageOS builds, however if these don't exist for your device then unofficial builds by trusted people in the XDA community are usually fine and well used.

[Brandon H Supervisor]

44 minutes ago, Mindovermaster said:

Make sure your computer has working adb and fastboot. Setup instructions can be found here.

 

I am currently on ArcoLinux (based on Arch). I don't see adb and fastboot in AUR/Pacman.

 

https://wiki.lineageos.org/devices/bacon/install

the 'android-tools' package is what you should look for; that is what includes those two tools 

 

https://wiki.archlinux.org/index.php/Android

[Mindovermaster Moderator]

I can't find this on my phone.

 

Quote

Setting up adb

To use adb with your device, you’ll need to enable developer options and USB debugging:

Open Settings, and select “About”.

Tap on “Build number” seven times.

Go back, and select “Developer options”.

Scroll down, and check the “Android debugging” or “USB debugging” entry under “Debugging”.

Plug your device into your computer.

On the computer, open up a terminal/command prompt and type adb devices.

A dialog should show on your device, asking you to allow usb debugging. Check “always allow”, and choose “OK”

There's no "build number", and there is no option to change "developer options" or debugging.

 

When I plug my USB in the computer, it asks me on my phone if I want to set it to charging, file storage, picture storage, or MIDI.

 

I ran "abd devices" on my computer, in terminal, doesn't find anything.

[Circaflex]

https://www.syncios.com/android/how-to-enable-usb-debugging-on-asus-zenfone.html or https://www.asus.com/support/FAQ/1009474/

 

To be frank, if you cant bother to research a little bit and find this option, I would not recommend trying to flash a 3rd party ROM on your device. You're likely to brick it.

 

Setting up ADB and allowing USB debugging are some of the more basic tasks with Android and custom ROMs. You can easily brick your device, or bootloop your device by performing some of the initial tasks, fairly easily.

 

You'll need to:

Unlock the bootloader (Without using official ASUS app: https://forum.xda-developers.com/zenfone-2-laser/general/guide-unlock-bootloader-asus-unlock-app-t3405850 or ASUS official tool: https://www.asus.com/us/Phone/ZenFone-2-Laser-ZE551KL/HelpDesk_Download/) and yes, that is the correct link ASUS_Z00TD = ZE551KL = Z00T

Install a custom recovery (TWRP official https://forum.xda-developers.com/zenfone-2-laser/orig-development/recovery-twrp-3-0-0-0-touch-recovery-t3317513)

flash ROM of choice

Root (option, but generally needed for Lineage) (Root if running Marshmellow: https://forum.xda-developers.com/zenfone-2-laser/general/guide-marshmallow-root-guide-ze500kl-t3380461)

Edited August 30, 2019 by Circaflex

[Mindovermaster Moderator]

Well, I would have looked this up, if I knew WHAT was involved. Like all you just said I had no idea about.

 

So you know about this? Teach me, my friend! (yeah, I know you already did, but...)

[Mindovermaster Moderator]

I got the USB Debug stuff working. Thanks to your link.

 

I ran this in terminal:

 

[mind@mind-Arco ~]$ adb devices
List of devices attached
FCAZCY153947	device

and

[mind@mind-Arco ~]$ adb shell
shell@ASUS_Z00T:/ $ 

Does that mean I am logged into my phone? I might do the command they have in this guide (that you posted)

 

[Mindovermaster Moderator]

I did the long "state:locked" command, it doesn't do anything... Am I missing something?

[Circaflex]

You need to be rooted to use that method.

 

su (switch user) essentially routes through super user, which is only available when you are rooted. 

[Christopher Andreason]

without the knowledge of bootloader what this
and how to unlock the bootloader
and closing bootloader if required, the rest is probably completely useless
 

but is primarily aimed at developers who want to test their own programs or similar

nothing that ordinary users should do as the warranty can be lost if you make a mistake

[Christopher Andreason]

5 hours ago, Circaflex said:

https://www.syncios.com/android/how-to-enable-usb-debugging-on-asus-zenfone.html or https://www.asus.com/support/FAQ/1009474/

 

To be frank, if you cant bother to research a little bit and find this option, I would not recommend trying to flash a 3rd party ROM on your device. You're likely to brick it.

 

Setting up ADB and allowing USB debugging are some of the more basic tasks with Android and custom ROMs. You can easily brick your device, or bootloop your device by performing some of the initial tasks, fairly easily.

 

You'll need to:

Unlock the bootloader (Without using official ASUS app: https://forum.xda-developers.com/zenfone-2-laser/general/guide-unlock-bootloader-asus-unlock-app-t3405850 or ASUS official tool: https://www.asus.com/us/Phone/ZenFone-2-Laser-ZE551KL/HelpDesk_Download/) and yes, that is the correct link ASUS_Z00TD = ZE551KL = Z00T

Install a custom recovery (TWRP official https://forum.xda-developers.com/zenfone-2-laser/orig-development/recovery-twrp-3-0-0-0-touch-recovery-t3317513)

flash ROM of choice

Root (option, but generally needed for Lineage) (Root if running Marshmellow: https://forum.xda-developers.com/zenfone-2-laser/general/guide-marshmallow-root-guide-ze500kl-t3380461)

i have tried the official application which is an apk file that unlocks the bootloader but then no way to return to being able to close the bootloader

 

I give you a tip leave the bootloader locked then you might possibly regret it then it will not be possible to lock the bootloader again myself also and I have been looking pretty good ASUS ZE520KL

[PGHammer]

On 8/30/2019 at 2:34 AM, Christopher Andreason said:

i have tried the official application which is an apk file that unlocks the bootloader but then no way to return to being able to close the bootloader

 

I give you a tip leave the bootloader locked then you might possibly regret it then it will not be possible to lock the bootloader again myself also and I have been looking pretty good ASUS ZE520KL

I have actually found a custom ROM (based on Android 10, oddly enough) that has displaced stock; however, it displaced stock by being a better stock - Havoc OS 3.1 (unofficial for Pixel 3a). I have it set up the same way (and with the same apps) that I did with stock - in short, I changed nothing compared to stock.

 

The big win for Havoc compared to stock is a common feature - VoLTE support.  As I said; this is something that is dead-stock in Android 10.  However, VoLTE in Havoc has better detection for users (in fact, it has a nice large flag to show it being active; stock doesn't do that).  Further, stock VoLTE has issues with telephony modems in stock Android - which means that you wind up turning it off. So far, I haven't had to turn it off - at all, which is despite the nearest wi-fi AP being a telephony modem in my own house.  VoLTE includes VoWifi (which is why telephony modem support can be critical); Monday will be a real "acid test"; I have chemotherapy that day which runs over five hours; if I have to make calls (or anyone needs to call me), VoWifi is the ONLY way I can be reached - standard LTE sucketh that bad.

[PGHammer]

On 1/25/2020 at 9:02 PM, PGHammer said:

I have actually found a custom ROM (based on Android 10, oddly enough) that has displaced stock; however, it displaced stock by being a better stock - Havoc OS 3.1 (unofficial for Pixel 3a). I have it set up the same way (and with the same apps) that I did with stock - in short, I changed nothing compared to stock.

 

The big win for Havoc compared to stock is a common feature - VoLTE support.  As I said; this is something that is dead-stock in Android 10.  However, VoLTE in Havoc has better detection for users (in fact, it has a nice large flag to show it being active; stock doesn't do that).  Further, stock VoLTE has issues with telephony modems in stock Android - which means that you wind up turning it off. So far, I haven't had to turn it off - at all, which is despite the nearest wi-fi AP being a telephony modem in my own house.  VoLTE includes VoWifi (which is why telephony modem support can be critical); Monday will be a real "acid test"; I have chemotherapy that day which runs over five hours; if I have to make calls (or anyone needs to call me), VoWifi is the ONLY way I can be reached - standard LTE sucketh that bad.

Followup: When I needed to be picked up from my infusion center, I called home.  (Remember, I mentioned that I have to use VoWifi, because standard LTE sucks from that particular location.)  VoWifi, however, works - when connecting to a cell phone - it would NOT connect to a landline at the same location as the cell phone in question.  Therefore, advantage: Havoc - even over stock Android 10.

[Forum staff Moderator]

This topic was automatically locked because it did not receive any replies for a year. If you want to have this topic reopened

• please contact any staff moderator or
• report the first post of the topic with the reason why it should be reopened.

Thank you.