Database Info

Captivate and a Hackintosh

Hey guys...I have a spare PC that I just converted to a Hackintosh. Everything went flawless with the install of OSX, but when I plug my Captivate in, it forces OSX to tell me I need to power it off and power it back on. I've tried this multiple times. I've even set the phone to have USB debugging on, and the same problem continues. Anyone have a suggestion?

Hmmmm
Ive never herd of this problem. It could be because its a hackintosh. I have a macbook pro and the captivate connects and does everything perfect. If you used a custom rom on the phone that can be an issue. It could be a bad flash. If you have stock then im not sure what the problem could be.
Sorry hope you fix this problem!

Probably not going to be much help but I have a hackintosh and my phone and PC play nice together
OSX is telling you the phone needs to be rebooted? Am I understanding that right? I can fiddle around and see if some settings make mine do the same thing

Are you using a pure vanilla untouched OS X build, or one of those crappy thrown together modded kernel deals.
Used to triple boot Windows, Linux, and OS X on my laptop before it fell off a table.

if you're running a vanilla build then it should work but you probably aren't. what version of OSX and what distro are you using? I suggest posting over at insanelymac since this is most likely a hackintosh issue.

How did you make your hackintosh? Feel free to PM me.
Ethere said:
Hey guys...I have a spare PC that I just converted to a Hackintosh. Everything went flawless with the install of OSX, but when I plug my Captivate in, it forces OSX to tell me I need to power it off and power it back on. I've tried this multiple times. I've even set the phone to have USB debugging on, and the same problem continues. Anyone have a suggestion?
Click to expand...
Click to collapse
Sent from my SGH-I897 using XDA App

seclm193 said:
How did you make your hackintosh? Feel free to PM me.
Sent from my SGH-I897 using XDA App
Click to expand...
Click to collapse
google can be your best friend.

I have no PC. I use XP with Parallels and Bootcamp, and It still is very finicky. Never had a Hackintoch but the newer Macs are Intel. Not sure where I'm going with this, but, yeah.

i dont have any problems with my captivate and my hackintosh. using the vanilla kernel.

Thanks for all the replies everyone. Here's the rundown:
I installed OSX directly following this guide:
http://tonymacx86.blogspot.com/2010/04/iboot-multibeast-install-mac-os-x-on.html
I am running Cognition 3.04 on my phone. And the minute I plug the phone into USB, this is what I see on the screen. This is not my computer, but it's an image I found on google images, but that's the exact error. I guess it's a kernel panic.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Doesn't matter if I have USB debugging on, or not. I've pretty much exhausted everything I can think of at this point, unless someone else has a suggestion. On my Windows computer, the phone is seen just fine btw...not sure what the problem could be.

Ethere said:
Thanks for all the replies everyone. Here's the rundown:
I installed OSX directly following this guide:
http://migre.me/3JFmQ
I am running... is not a phone issue but a hackintosh issue.
Click to expand...
Click to collapse

"Telling me to reboot" and "kernel panic" are two very different things.
Now it's definitely a problem for these guys:
http://www.insanelymac.com/forum/

Yeah, I posted a thread right on TonyMac's website too and they had no clue as to why that happened. Thanks for the link Mike. I'll check it out with them and see what they suggest.

this may be related
From the Heimdall ( http://www.glassechidna.com.au/products/heimdall/ ) FAQ:
What platforms does Heimdall run on?
Linux, OS X and Windows (XP, Vista, 7 etc.)
Although Heimdall runs on OS X all Galaxy S devices tested thus far contain a bug in the secondary boot loader that prevents the device registering itself with OS X. This may change if Samsung release an updated secondary boot loader.
Update: Samsung have released an updated secondary bootloader that corrects the issue. The correct bootloader is included in the official Froyo release. Obviously you have to get Froyo on your device somehow, but from then on it’s smooth sailing.
Note: Keep in mind if the version of Froyo you’re running is not official then the updated Sbl.bin may not have been included.

Hrm, you may have something there. I'll flash back to stock tonight and see if the Captivate works after that.

[GUIDE] ZTE Warp N860 (Boost Mobile) Diag Mode

I needed to connect a ZTE Warp to CDMA Workshop and QPST on my pc, so I did some searching to find out how to put the phone into Diag Mode. Easy enough. Well, It took me longer than a few minutes with google to find the info I was looking for, but I did eventually find it. Hopefully this post will help others. I can confirm this works to get the Boost Mobile ZTE N860 (Warp) into diagnostic mode so it can be read by CDMAWS, qxdm, etc.
1. Install the ZTE handset usb drivers: https://www.dropbox.com/s/thf4ctjee960mnt/ZTE_Android_Driver.zip
2. Turn on the phone and connect to pc via usb (make sure you enable usb debugging in settings>applications>development)
3. On the phone go to Dialer and enter *983*87274#
4. A new window will open on the screen with a list of choices. Choose the first item on the list only.
5. Wait a minute or two while the necessary drivers are installed on your computer.
6. Now look in device manager, under ports you should see ZTE Handset Diagnostic Interface (com#).
7. On the phone press home to return to your home screen.
8. Make note of the com port # and you're all set.
You can now connect to qpst, qxdm, and so on. Don't forget to hit the Thanks button below if you found this useful.

Just want"d to say thanks....cause I needed that code...:good:

6thgear76 said:
Just want"d to say thanks....cause I needed that code...:good:
Click to expand...
Click to collapse
Cool. I'm glad it helped you! :good:

Works wonderful on ZTE Avail Z990 as well
You can now connect to qpst, qxdm, and so on. Don't forget to hit the Thanks button below if you found this useful.[/QUOTE]
The above steps work for ZTE Avail z990 (ATT) as well. Works like a charm, ready to connect to QPST/QXDM in a breeze. Thanks.

I can't get qpst to recognize the warp n870. I have all the drivers. Cdma workshop is working just fine but I need to be able to use qpst.
I read somewhere that u have to put the port which is com11 in before it will recognize the phone in device programming. But I dont think im inputting the port in right cuz it wont accept it. Does anyone have some imput?
Sent from my SPH-D710 using Tapatalk 2

Found my Own answer. For those stuck in the future here's the link to a guide on setting up qpst to see your phone. It's how to add you're Ports I was stuck on
http://forum.xda-developers.com/showthread.php?t=1180211
Sent from my SPH-D710 using Tapatalk 2

SelfElevated2 said:
Found my Own answer. For those stuck in the future here's the link to a guide on setting up qpst to see your phone. It's how to add you're Ports I was stuck on
http://forum.xda-developers.com/showthread.php?t=1180211
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
Cool, glad you figured it out. I didn't post any info on configuring qpst because it would've been off topic. I'm sure there are people that will appreciate the link you provided. Thanks.

Does anyone have a copy of the USB Drivers, since ZTE took them down?

gadgetdaddy said:
Does anyone have a copy of the USB Drivers, since ZTE took them down?
Click to expand...
Click to collapse
Did you find the drivers? Updated OP with new link.

Good！:good:

budgreen24 said:
Did you find the drivers? Updated OP with new link.
Click to expand...
Click to collapse
It says no files at the new link?

gadgetdaddy said:
It says no files at the new link?
Click to expand...
Click to collapse
Fixed. Try it now.

Bad zip file. Can someone update this download link with a good file please?
Thank you,
John

pede69 said:
Bad zip file. Can someone update this download link with a good file please?
Thank you,
John
Click to expand...
Click to collapse
I just downloaded it to check, and it worked fine for me.

budgreen24 said:
I just downloaded it to check, and it worked fine for me.
Click to expand...
Click to collapse
Worked that time.
However... are you someone that can help me?
Followed your instructions until step 5.
I was a bit confused about which button to push. You said "first item"
So I pushed the FIRST item. The "all functions" button.
Windows came up with it's 3 choice dialog window.
Windows found new hardware.
Locate and install driver software.
Ask me again later.
Do not show this message again for this device.
So then I tried the second one (mass storage+adb) thinking that
maybe since it did a specific thing, you may have meant that one
as the "first item".
Windows did nothing at that point.
No port listing in Device Manager.
Now I'm lost and stuck.
Can you offer any help here?
Thank you,
John
---------- Post added at 01:39 AM ---------- Previous post was at 12:41 AM ----------
When I plug in the phone now and have Windows search for the driver, I get the following...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks...
J
---------- Post added at 02:24 AM ---------- Previous post was at 01:39 AM ----------
OS is Vista 64 Home Pre.

Ok, first item on the list = "All functions".
Then if you see:
pede69 said:
Windows found new hardware.
Locate and install driver software.
Ask me again later.
Do not show this message again for this device.
Click to expand...
Click to collapse
Choose "locate and install driver software". Windows should then install the drivers for you within a minute or so.
If you run into the same message as you did before:
Then I can only guess that it's a compatibility problem with Vista? But like I said, it's a guess. Never tried on Vista, but maybe someone else has? I've had no driver problems using Windows 7 or 8.

Hi...
Thank you for your reply.
Tried clicking on "Locate and install driver software"
Does the exact same thing on my Win 7 64 laptop.
Been going at this since 9am. Very frustrated. About to give up for tonight.
Thanks again,
John

Hi Guys...
Really could use some help here. Have same problem except
Device Manager shows some entries with the yellow triangle
sign. below is a pic of it.
Does the same thing with Win 7 64. Think this could be a 32
vs. 64bit issue? I have several computers but no 32bit OS.
Thanks very much to anyone willing to help me out with this.
J

Today I ran thru this whole procedure on a friend's laptop (windows 8 64-bit) and I didn't have any of the issues you've explained. Windows automatically installed the necessary drivers. The new ports should show up in device manager like this screenshot.
Maybe someone else can help you out..?

Thanks for the reply.
Does not show up in mine because the driver/drivers never install. I get the wrong platform error message.
I have decided to put the ZTE issue aside for now and try and do my wifes phone. And of course I'm having issues...
In DFS on the Mobile ID tab, DFS does not pull the aaa and ha data. And also I get the following errors:
get ds_mip_ss_user_prof cps_error bad_param
get ds_mip_dmu_mn_auth cps_error bad_param
S2 D-710 connects just fine and DFS accepts my SPC/MLS number and 16 digit password. And states
Unlocked in the console.
Going at this three days now. Worn out and pretty much sleep deprived. Sure wish I could get some TeamViewer
help from someone here
Have been laid off so funds are a bit short right now but would be more than happy to give a unlimited webhosting
account complete with Softaculous. Google it if you do not know what it is You would need to get your own
domain name though.
Anyway... thanks again for your reply.
John

Bricked after installing Beats Audio on TF101

Hello,
Today I rooted my TF101 and though, lets install beats audio and check it out. The rooting process with 1 click root was really easy, but 5 minutes later after beats audio installing - the system stopped like that: it just spins all the time and does nothing
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
My pc (WIN7 64) recognize the usb but only for few moments and then it's unknown so I cant do anything through USB atm (at least that's what I guess)
So i started trying everything what I could (power up+volume down and up) and everything I could do is going to the menu (and saw the system info - which is weird cause I'm living in Poland and my System is US )
So I went farther and If I press vol up - it makes soft boot Linux *which doesnt even rs anything just back to loading screen
But when I wait - I can choose between recovery mode and wipe. If I pick wipe - "living" android loads something, tablet restarts and everything is the same, and if I choose recovery mode - it goes into living android pic for a sec and then to the "dead" android with the sign on him (like on the photo) for a long time and then nothing happenes.
And I can choose between those 2 in this menu:
I honestly dont know what is happening. Please for any help, its the only "pc" I got in my house. (Sorry for bad English, hope U can understand me in general)
P.S I found this on yt, what do you think about this vid?
How to Unbrick, Unroot, or Downgrade the Asus Transformer (on YT, cant post link)

try easyflasher by whitekidney from the development section.

i tried that and I cant get into apx mode, I guess im doing it right but just cant. it's power and vol down wright?

Same situation
Im in exactly the same situation
Im an extreem NOOB and i guess i got a little ahead of myself... actualy i think now i'm in a bigger hole that you are. I did the wipe before the restore and now i lost the ability to pick a Zip file from the SD.
I'm at a loss I've downloaded the factory firmware and loaded that to the SD card I hold the power and Vol down and get the two options to wipe or the little android guy when I select wipe it goes throgh the process then I get the android guy standing in front of the box then it shows the ASUS splash screen then I get the white dots running in the circle forever.
If anyone can offer any suggestions I'll try anything
Thanks Ryan

You will have to reflash using whillie(if on SBK2)
Go into APX mode and reflash the whole image.
Just press and hold the power + UP button. The computer will detect it.

whats whillie Ive searched google and this site and cant find anything
Im trying to use Brk's Transformer root kit but when I try to install the drivers it says "The directory name is invalid" Ive tryed the 64 and 32 bit versions on two computers (i'm not alowed to post in that thread?????)

ok, so how exactly should i get into apx mode?
lets assume my tablet is turned off and connected to wp, what now?
oh and another question:
on the picture you can see my soft is US while im in Poland and had Polish menu etc. so now, when im downloading new soft to install. should i get WW or US one?

PROBLEM SOLVED!
IT turned out that i had to instal other apx drivers and now i did it well with easyflasher.
got a question for you guys, can i instal other than custom roms with that easyflasher?

ryfoste said:
whats whillie Ive searched google and this site and cant find anything
Im trying to use Brk's Transformer root kit but when I try to install the drivers it says "The directory name is invalid" Ive tryed the 64 and 32 bit versions on two computers (i'm not alowed to post in that thread?????)
Click to expand...
Click to collapse
Whoops, It's Wheelie not whillie. My bad. Sorry.

Thanks ok I had plenty of other things to try.
I did manage to get clockwork recovery on my 101. but everytime i try to load a rom with it it just says file not found. So I guess im kinda at an impass

maciekiel said:
PROBLEM SOLVED!
IT turned out that i had to instal other apx drivers and now i did it well with easyflasher.
got a question for you guys, can i instal other than custom roms with that easyflasher?
Click to expand...
Click to collapse
Is the APX driver the USB drivers??
I think that's what I'm missing. I don't even get the acknowledgment that my tf101 has even been plugged into my computer, no ding, no trying to install software , no nothing.
I've tried googling some usb drivers but couldn't figure out what they were trying to do
I also seemed to have lost access to my SD card when i try to install a ROM or anything from the SD card in clockwork i get the file not found error
Any help would be greatly appreciated. I'd like to think I'm fairly computer literate but the whole android thing is very new to me
Ryan
---------- Post added at 06:05 AM ---------- Previous post was at 05:45 AM ----------
it accualy reads
E:cant open /sdcard/update.zip
(no such file or directory)
Installation aborted
Thanks again guys

ryfoste said:
Is the APX driver the USB drivers??
I think that's what I'm missing. I don't even get the acknowledgment that my tf101 has even been plugged into my computer, no ding, no trying to install software , no nothing.
I've tried googling some usb drivers but couldn't figure out what they were trying to do
I also seemed to have lost access to my SD card when i try to install a ROM or anything from the SD card in clockwork i get the file not found error
Any help would be greatly appreciated. I'd like to think I'm fairly computer literate but the whole android thing is very new to me
Ryan
---------- Post added at 06:05 AM ---------- Previous post was at 05:45 AM ----------
it accualy reads
E:cant open /sdcard/update.zip
(no such file or directory)
Installation aborted
Thanks again guys
Click to expand...
Click to collapse
I think you should use universal naked drivers. it installs most drivers for most of your device. be it APX or USB
Sent from my Desire S using Tapatalk 2

[Toolkit] Wug's Nexus Root Toolkit v2.1.4 [Updated 01/16/16]: Nexus 7 (2013) Thread

Unlocking, rooting, relocking and unrooting simplified! (and much more!)
VERSION 2.1.4 - This program will automatically bring together all the files you need to unlock and root your device in a few clicks, or flash it back to stock and re-lock it. You can also use this program to backup/restore all your important data, flash zips, set file permissions, push and pull files, install apps, generate logcats/bugreports, and much more! With the included file association options, you can perform tasks like flashing zips, installing apps, restoring android backup files, and flashing/booting img files with just a double click! The program includes a full featured interface for automating tasks in TWRP, enhanced restore features, an in-built auto-updater/notification system, ‘any build’ mode, advanced restore features,’NRT- Live Log’ for viewing the adb/fastboot cmds that are run in the background, quick tools utilities, and tools for taking screenshots/screen-recordings. All the latest official Android builds and Nexus devices are supported. The program intelligently and selectively downloads the files it needs for your device and makes sure you are using the latest files available. The program can even auto-detect your device and build. This release brings full Marshmallow root support plus all automated features by utilizing a new system that no longer requires modified boot.imgs. Check out the updated changelog for a more comprehensive breakdown of the feature set and changes in this release.
~ my goal for this project is make the entire process as smooth and simple as possible ~
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Please read the FAQs before posting questions: http://www.wugfresh.com/nrt/faqs/
Looking for a walk-through? >> Excellent Instructional/How-To Videos: http://www.wugfresh.com/videos/
More information & Download Links: http://www.wugfresh.com/nrt/
Changelog: http://www.wugfresh.com/nrt/changelog/
Enjoy! ^_^
{{ WugFresh }}

I can't find 1.6.6 it still says "Version 1.6.6 coming soon, ETA = 07.28.2013"
Thanks.

ashik992 said:
I can't find 1.6.6 it still says "Version 1.6.6 coming soon, ETA = 07.28.2013"
Thanks.
Click to expand...
Click to collapse
Maybe try clearing browser cache. Here are some external mirrors:
Mediafire: [redacted]
Dev-host: [redacted]
Enjoy! ^_^
{{ WugFresh }}

Thx Wug! I was wondering if you were going to update the toolkit to work with flo, and BAM! Here it is! Love your work, hope you keep at it. :good:

I did not chose twrp
I use 1.66 to root my nexus 7 (2012) and I did not check the (also flash custom recovery) first pass was pushing temporary twrp, and second it flash the twrp.
Why? I get a real problem with twrp with the 4.3 update, so I did not want it in my device.
Is this a bug in the toolkit? or there is a reason why the twrp is push without asking to flash?
Still the best toolkit I ever use.

You may want to change the main body font. It's almost impossible to read on the xda app with the dark theme selected
prshosting.org

Thanks for your work. I first ran and used the "raw driver" install. Went to step 3 and ran the "check". "Success"! When installing Root & Recovery, it gets to the point where it says pushing root files to device, but when it's supposed to boot into TWRP, it boots into system "android man with red exclamation mark on his belly" mode. Tried it twice with the same result. Any ideas? I did notice that in Device Mgr "portable devices" isn't showing at all. However in Prompt mode, an "adb devices" shows device serial #. It's as if TWRP wasn't flashed correctly.

melfunn said:
Thanks for your work. I first ran and used the "raw driver" install. Went to step 3 and ran the "check". "Success"! When installing Root & Recovery, it gets to the point where it says pushing root files to device, but when it's supposed to boot into TWRP, it boots into system "android man with red exclamation mark on his belly" mode. Tried it twice with the same result. Any ideas? I did notice that in Device Mgr "portable devices" isn't showing at all. However in Prompt mode, an "adb devices" shows device serial #. It's as if TWRP wasn't flashed correctly.
Click to expand...
Click to collapse
Same issue I'm having.

Thanks for the app! Unlocking went fine, I'm hesitant to root if it's going to leave me with TWRP even if I leave that field unchecked, anyone else have the same problem as Lachaine? Or has anyone successfully gained root and maintained stock recovery with this?

funkbucket007 said:
Same issue I'm having.
Click to expand...
Click to collapse
Please try enabling this option:
Cheers.
{{ WugFresh }}

Thanks for all your hard work on this, and for sharing it with the community!! It's great having multiple options!!! I didn't use this, but just wanted to say thanks for building this and freely sharing it!!!! It's devs like you that make XDA such a great community to be a part of!!!
SwiftKey'ed from my White Sprint Note 2 using XDA Premium

WugFresh said:
Please try enabling this option:
Cheers.
{{ WugFresh }}
Click to expand...
Click to collapse
Check that option and start over with the root process?

I'm having the same problem. Made the changes in setting and no difference.

jsnietka said:
I'm having the same problem. Made the changes in setting and no difference.
Click to expand...
Click to collapse
Same here.
Sent from my SAMSUNG-SGH-I317 using xda premium
---------- Post added at 02:50 PM ---------- Previous post was at 01:53 PM ----------
k5mitch said:
Same here.
Sent from my SAMSUNG-SGH-I317 using xda premium
Click to expand...
Click to collapse
jsnietka said:
I'm having the same problem. Made the changes in setting and no difference.
Click to expand...
Click to collapse
Third time is a charm.:good:

k5mitch said:
Same here.
Sent from my SAMSUNG-SGH-I317 using xda premium
---------- Post added at 02:50 PM ---------- Previous post was at 01:53 PM ----------
Third time is a charm.:good:
Click to expand...
Click to collapse
Are you saying it finally worked?
I've done it twice same lil dead android with the red triangle.
Guess I'll try again

Unlocked, rooted and installed TWRP. No problems.
Thanks!

feron said:
Are you saying it finally worked?
I've done it twice same lil dead android with the red triangle.
Guess I'll try again
Click to expand...
Click to collapse
ODD.. third time it worked... lol

feron said:
ODD.. third time it worked... lol
Click to expand...
Click to collapse
Well after I checked the option wug suggested I closed the program and re-started it. Walah it worked.
Sent from my SAMSUNG-SGH-I317 using xda premium

k5mitch said:
Well after I checked the option wug suggested I closed the program and re-started it. Walah it worked.
Sent from my SAMSUNG-SGH-I317 using xda premium
Click to expand...
Click to collapse
Yes don't forget to restart the toolkit before trying again. Worked for me when I did. Thanks wug!

Having an issue. Stock build# is JWR66N but is not listed, so i choose the closest one, JWR66V. So far it installed the adb drivers but fails on the Full Driver Test and Checking ADB Status. The device shows up perfectly now in DM, as a Nexus7, so the drivers have a clean install. Rebooted 2-3 times already. I can go to the adb command line and its installed but not sure why the app or PC doesn't see it setup right? I cant continue to the next steps if adb is not right...lol

LineageOS on Zenfone 3 Max! (ZC553KL)

I've got LineageOS 15.1 to (kind of) work on the Zenfone 3 Max.
Pics:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
We are nowhere near ready for real-world use, as currently very few things work. Nevertheless, I figure some of you might be interested in developing for the Zenfone 3 Max ZC553KL. I myself will continue to work on getting more features functional. Any help is welcome, and so is any question!
Right now, mobile (call & network), Wi-Fi, USB transfer (or ADB), camera, and probably nearly everything else don't work. Bluetooth works.
See what works and what doesn't here: https://github.com/wishawa/android_device_asus_X00D/blob/lineage-15.1/README.md#progress
So far, Audio, USB, 2.4GHz Wi-Fi, Camera, sensors (gyro, light, etc.), GPS are working.
Telephony (call) is not working.
Details and source on Github: https://github.com/wishawa/android_device_asus_X00D/
Download the ROM: https://github.com/wishawa/android_device_asus_X00D/releases
I couldn't get TWRP working so use this older version here: https://forum.xda-developers.com/zenfone-3/how-to/zenfone-3-max-zc553kl-bootloader-unlock-t3691837
For builders:
To extract proprietary blobs, use official ROM image downloaded from ASUS here: https://www.asus.com/Phone/ZenFone-3-Max-ZC553KL/HelpDesk_Download/
Also, install will fail (with error 7) with this old TWRP version. Follow this guide https://forum.xda-developers.com/showthread.php?t=2522762

I am very interested in what you do to make lineageos work on this phone.
Actually I own two of them, I just bought a secondary one to try to give tries to alternate OS.
Let us know about your progresses, and I also may help (I do not know Android very well, but I know far more about Linux!).

i love you

nbercher said:
I am very interested in what you do to make lineageos work on this phone.
Actually I own two of them, I just bought a secondary one to try to give tries to alternate OS.
Let us know about your progresses, and I also may help (I do not know Android very well, but I know far more about Linux!).
Click to expand...
Click to collapse
Thank you!
I have a problem that I believe might be related to Linux.
I've been trying to build TWRP for the device, but I couldn't get touchscreen to work. TWRP seems to interpret holding down finger as touching and lifting quickly, making it impossible to slide ('slide to unlock', 'slide to adb sideload', etc).
I suspect this might be related to this warning I get when building the kernel:
Code:
drivers/input/touchscreen/ft5436/Kconfig:2:warning: ignoring type redefinition of 'TOUCHSCREEN_FT5436_DRIVER' from 'boolean' to 'tristate'
If I am wrong, or you know how this might be fixed or need any more information, please tell me. Thanks!

vaanish said:
I suspect this might be related to this warning I get when building the kernel:
Code:
drivers/input/touchscreen/ft5436/Kconfig:2:warning: ignoring type redefinition of 'TOUCHSCREEN_FT5436_DRIVER' from 'boolean' to 'tristate'
If I am wrong, or you know how this might be fixed or need any more information, please tell me. Thanks!
Click to expand...
Click to collapse
Your question looks driver-specific but the problem seems generic. You may try to clean up your compilation environment and rerun make again.
You may also grep your kernel config file against TOUCHSCREEN_FT5436_DRIVER to enable/disable features about this driver.
I can't help much more on this topic!

nbercher said:
Your question looks driver-specific but the problem seems generic. You may try to clean up your compilation environment and rerun make again.
You may also grep your kernel config file against TOUCHSCREEN_FT5436_DRIVER to enable/disable features about this driver.
I can't help much more on this topic!
Click to expand...
Click to collapse
Cleaning the environment didn't help.
TOUCHSCREEN_FT5436_DRIVER is set to y in the config. But does this warning mean the driver is not being built?

vaanish said:
Cleaning the environment didn't help.
TOUCHSCREEN_FT5436_DRIVER is set to y in the config. But does this warning mean the driver is not being built?
Click to expand...
Click to collapse
No, a warning is not a failure to build.
Your driver should be available and loadable with modprobe.
PS: Please contact me by e-mail (cf. PM) since I cannot spend so much time on validating reCAPTCHA for each post.

Wi-Fi is somewhat working! (some networks won't connect; don't know what's with my home wifi, but another phone's hotspot works well)
Now that I can ADB over network (USB still broken), development should be faster!

2.4GHz Wi-Fi now working well, and camera and USB are working.
Flashable zip available for anyone wanting to try: https://github.com/wishawa/android_device_asus_X00D/releases/tag/pre-alpha-0.0.1

I have a problem: com.android.phone has crashed every second and reboot. On my zc553kl this firmware doesn't work.

do the fingerprint really won't work??

I have found a newer version of twrp 3.2.3 on twrp builder site. hope this helps. Credits to the owner. Looking forward for the development of this rom.

pipneogen said:
I have a problem: com.android.phone has crashed every second and reboot. On my zc553kl this firmware doesn't work.
Click to expand...
Click to collapse
Thankyou for reporting! I'm working on fixing the telephony features, but has been quite busy lately.
By 'reboot' do you mean the whole OS crash and reboot? or just the com.android.phone restarts.
Also, if it isn't too much trouble would you mind getting a logcat? (tutorial, if you need; https://forum.xda-developers.com/showthread.php?t=1726238) It would allow me to verify that we are running into the same problems.

arzenralph said:
do the fingerprint really won't work??
Click to expand...
Click to collapse
Sadly not yet. It should be possible, I just haven't got to it.

DimeSlime said:
I have found a newer version of twrp 3.2.3 on twrp builder site. hope this helps. Credits to the owner. Looking forward for the development of this rom.
Click to expand...
Click to collapse
Thank you very much. Will test it out. Do you know if the owner provide the source tree for building anywhere?

vaanish said:
I've got LineageOS 15.1 to (kind of) work on the Zenfone 3 Max.
Pics:
We are nowhere near ready for real-world use, as currently very few things work. Nevertheless, I figure some of you might be interested in developing for the Zenfone 3 Max ZC553KL. I myself will continue to work on getting more features functional. Any help is welcome, and so is any question!
Right now, mobile (call & network), Wi-Fi, USB transfer (or ADB), camera, and probably nearly everything else don't work. Bluetooth works.
See what works and what doesn't here: https://github.com/wishawa/android_device_asus_X00D/blob/lineage-15.1/README.md#progress
So far, Audio, USB, 2.4GHz Wi-Fi, Camera, sensors (gyro, light, etc.), GPS are working.
Telephony (call) is not working.
Details and source on Github:https://github.com/wishawa/android_device_asus_X00D/
Download the ROM:https://github.com/wishawa/android_device_asus_X00D/releases
I couldn't get TWRP working so use this older version here: https://forum.xda-developers.com/zenfone-3/how-to/zenfone-3-max-zc553kl-bootloader-unlock-t3691837
For builders:
To extract proprietary blobs, use official ROM image downloaded from ASUS here: https://www.asus.com/Phone/ZenFone-3-Max-ZC553KL/HelpDesk_Download/
Also, install will fail (with error 7) with this old TWRP version. Follow this guide https://forum.xda-developers.com/showthread.php?t=2522762
Click to expand...
Click to collapse
Is there any update?

error "com.android.phone has stopped"
After flashing my phone with this ROM I boot into system and i get constant error messages "com.android.phone has stopped" I have asus zenfone 3 max zc553kl silver. Is there something i can do to fix it ? (I didnt install gapps)

idirtb15 said:
Is there any update?
Click to expand...
Click to collapse
Same question. I really like it but I really hope the telephony thing would work. Although bluetooth works fine with my wireless speaker.
---------- Post added at 06:06 PM ---------- Previous post was at 06:03 PM ----------
sindibad363 said:
After flashing my phone with this ROM I boot into system and i get constant error messages "com.android.phone has stopped" I have asus zenfone 3 max zc553kl silver. Is there something i can do to fix it ? (I didnt install gapps)
Click to expand...
Click to collapse
That's probably because of the telephony not working.

Any updates on the rom?