Related
Hi guys, I have a big problem with my Asus Zenfone 2 ze551ml. I bought it from china so I didnt have Google Play and I used to download every app I needed from Aptoide. But yesterday I decided to give it a try and change the firmware. I read every article on "how to", most of them were saying the same steps, so I started by downloading everything I needed, the WW firmware from asus site, the usb drivers, the adb program etc. Everything was going great, and I came to that point that you just have to send via adb the package with the WW firmware and... my laptop(which is an Asus, lol) stopped recognising my phone. Then I started reading tons of threads on how to fix that problem but nothing. I did everything.
Download the intel usb drivers for android- done
Manually install the usb drivers from Asus- done
Uninstall everything and trying one driver at a time- done
Usb debugging-MTP, all these things again and again- done
Tried every single usb cable and port- done
Tried 3 different computers- done
Wipe cache partioning and try all the above steps again- done
Wipe all user data back to default- done
And nothing.. I mean nothing, my phone is invisible to any computer. Is anything else I can do? What's left? To throw my phone away? Now everything in my phone is tiny, the app icons are tiny, the fonts are tiny, even the fb messenger bubble is tiny.. pls help me.. :crying:
my problems and solution for you
Hellooo, not all hope i lost...
Firstly the problem I have similar to you is that my ZF2 runs on CN firmware, which is the biggest struggle ever trying to find the only working APK app files, I was happily trying to install WW firmware (even though it had the playstore, as it was some sort of modded brand new phone front eBay) and I accidely pressed the button which wipes everything :') So I go 3 days figuring out how to make my phone start as another issue had arrised, I fix it with some 3rd party bootloader...and ever since January I've been living this almighty stuggle.
FUNNY THING IS...I KNOW EXACTLY HOW TO FIX IT...but my Acer laptop has an old version of the ADB driver which I cannot get rid of OR UPDATE and I have no access to another pc
As for your issue, by some miracle you read this...
1) make sure you're using a data cable (one that shows you're phone in the Windows library list n all)
2) if you're not seeing or hearing what I said...go in your phones setting punch the fu...I mean tap the "about " option right at the bottom 7 times, and you should now have unlocked the Dev Options...
Now, back to the settings list, press Dev Options which is above the about option, scroll down a little and enable "USB Debugging" press yes/allow...what ever the **** comes up and looks good and wulluh.
3) Now, if actually you've already done step 2 and have tried 3 laptops :0...try step 1 again
4) If you followed step 3s very very complex instructions to a level of hope that binning the phone or suicide are options then by all means set it on fire then throw it at your ex gf...if you have one...concidering you bought an Asus phone lol, mug
5) try this other thing that works but is just as hopeless by finding it on YouTube, searching "Asus ZenFone2 Flash" with the "past month" filter there should be a video with the thumbnail of an Indian man with a blue shirt and glasses, click on it...watch closely n stuff.
Hope it works out and that you found my profecional instructions helpful - Lewis
Make sure your driver's are installed properly.. Check drivers on your pc by going to device manager and check
NiTesh said:
Make sure your driver's are installed properly.. Check drivers on your pc by going to device manager and check
Click to expand...
Click to collapse
That's his issue, same for me, ADB does not show in device manager. Unless you mean installing the driver by right clicking on the phones name?
Since this Defy Forum is getting a bit old, I thought I'd give my recent experience with my defy. This is quite a lengthy thread but there is so much information on this forum that it becomes confusing so thought I'd share my experience so you can cut through a lot of the information. I've had my defy for over 5 years with the stock froyo 2.2.2 and its served me well until recently its beginning to bug me with how laggy it is. Also I wasn't sure if the battery was running out a faster than it used to.
The first thing I thought I'd do is do a factory reset which I successfully did however when I went to put back on some of the apps that I had before such as Runkeeper, Telstra 24/7 and RSA Security token, none of them were compatible with my old phone. I was able to find old versions of some of the apps but not Telstra 24/7 which I use to recharge. At this point I decided on installing a custom rom which I'd done before on other devices. If it didn't work out then phones with the same specs were selling for $29 at a local supermarket so no real damage if I get it wrong.
The first thing was to root the phone which I found something called Superoneclick. I had to turn off my antivirus on my PC use it as there are some files that appear corrupt but doing some searching gave me confidence it was just an overzealous AVG and appeared safe.
Once this was done it was a matter of picking a Rom which I went for CM11 Kit Kat it seemed ok but not heaps better. The thing was I'd now picked up a real battery problem. I tried various Calibration apps to no avail. My battery was experiencing quite large drops of 20% ie it would go from 89% to 50% and then later from about 35% to 20%. It would then stay on 1% for quite some time.
Thinking this was due to the ROM, I tried several ROMs but they all had the same problem. Eventually i found a thread on the battery problem and although I didn't change all the permissions as advised I did so some of the other stuff to no avail.
At this stage I thought my main issue was now the battery and thought I'd read someone that perhaps a stock based rom might sort it out. I installed MS4Ginger which was really smooth however was still a bit laggy at times. Also I noticed that it wasn't able to support various apps being Android 2.3. After a bit more reading, my minimum requirement was Jellybean 4.1 and I'd read that the more recent the ROM the more RAM intensive so I decided to try ROMs with my minimum requirement ie 4.1
I'm not a fan particularly the way the Cyanogen type rom look so was looking for something with a different look and feel. The main ones were:-
Miui based ones (Wiui, Jiui) which I quite liked however lag was still there and the occasional sudden reboot. Battery problem still there.
Xperia ROM which was also nice but also did a sudden reboot then stuck in a bootloop.
There was still lag which I couldn't really understand.
Last Rom I tried was Motor Gun Ice 4.1, it still had the Cyanogen look about it but seemed to run pretty smooth. One thing I had to do was change the Baseband to Telstra in the 'Advanced' section of settings. This made the phone and internet connection work faster.
At this point I ordered a new battery. While I was waiting for that to arrive I read that Facebook app is really bad at taking up RAM. In found another app called Facebook lite and uninstalled the standard Facebook app. All of a sudden Lag Fixed.
This got me searching other 'Lite' apps. Now for web browsing i use Opera Mini and the launcher I now use is Holo Launcher. I also tried to find a replacement for Messenger but no luck and its not been an issue.
So now my phone is running better than ever. Web searching is fast and apps are running well, not that I use my phone for much more than a phone.
A few days later my new battery arrived and comparing to the old one, it appeared that the old one had a slight bulge. I charged the new one right up, discharged and charged again and now no more battery drops.
One last tweak I wanted was to try change the status bar icons. I found Xposed Installer and was able to change the icon colours to white but not the icon pictures. Good enough for me.
So now I'm very happy with my 5 year old defy, took a bit of trial and error but got there in the end. So in a nutshell: -
- If your battery is dropping upon installation of a Rom, likely need a new battery.
- If you phone is lagging, look what is taking all the Ram and look for a lite option or uninstall. Facebook is bad for that.
Note that there are many old links to roms and other mods so finding things that work was at times a challenge but here's the process that I found worked for me and works if bricked as well, which I did a couple of times.
If Bricked or to get back to stock
Download RSD Lite
Install drivers for the phone
Download an SBF for your region, I used Telstra with 2.2.2
To install custom rom
Install and use Superoneclick to root (may need to turn off antivirus)
Install 2ndinit.apk then run it. May need to reboot phone first
Download the Rom and Gapps and put on SD card of phone
Get into custom recovery
Wipe Data and Cache
Install Rom and Gapps
Wipe Cache and Dalvik Cache (for all but one Rom, I forget which one, read instructions)
Reboot and enjoy.
the gun rom link is down, where you downloaded it?
That was one of the few that worked. I accessed from the defy wiki page then I think downloaded from the XDA thread.
Yep, there some links in the last post of the MG ROM thread. Post #222.
Good someone still use defy. I give up after digitizer gone mad. Time run over this device... Uuuh, just if it had 1 gb ram and dual core...
Good to hear that someone else still have this cute little thing. I have too, as my second device. The ROMs I tried on this device! Man, it's countless. I had dropped it on all the different terrains you can think of, yet it's still fully healthy (save the jack and usb covers - they are loose now) without a single crack. I didn't have any covers or screen guards. It stayed true to its name. I will never regret spending money to buy this, it is one of Moto's legendary devices. I think I'm drunk, but it feels good to say all this. I'll keep this device forever with me - a product from a time when smartphones weren't made in an oven, but carefully and delicately cooked up.
Digitizer gone mad me too, the upper line is not working, but it is a good phone, for kids.
Which seller you order the battery?
Can you suggest ROMs to watch videos on Kodi, or Youtube?
I liked this phone, this is the best size phone, what i ever had.
Why the companys not make phone like this size, one hand controlled, with 2GB/32GB, and quad cpu??
Now i have Samsung S4 mini, and it is big for me
Battery was off eBay, can't remember seller but was Australian selling genuine batteries.
Just try all the roms possible, that's part of the fun
Sent from my SM-T210 using Tapatalk
I've been wanting to play around w/ my old defy again. This thread may have got the ball rolling. What do you all use as your daily driver? I've got a xperia z3 compact, but want a new phone. unfortunately, I think my best bet is to just get another z3 compact cheap and save it as a backup?
Hi tronjojo, I was still using my Defy until recently I found an old 4 year old Samsung Galaxy SII of my wife's. The problem for her was that it was switching off all the time so she got an S5. I've now flashed various roms and fixed the random reboot issue. The only thing I wish it has is the notification LED.
Sent from my SM-T210 using Tapatalk
I bougnt a Defy + battery on my Defy Red Lens, made my own BL7 fixed SBF and nandroid with 720p patch which made it a Defy Plus, then I rooted it and repartitioned to install CM11 and has made it very usable in 2016.
Make that Defy in 2018
I'm still using a Defy, since 2011. The battery still lasts longer than that in my wife's new Sony Experia X Compact, about as long as in my daughter's Xiaomi Redmi 4X. I will probably have to move to another device somewhere in 2018 as one of the more important apps - the Swedish BankID app - will cease support for Android 4.4 but that is more or less the only reason. For the rest the thing still does what it did 7 years ago so were it not for this I'd keep on using it until it gave up from sheer old age or electron migration or whatnot.
Make that Defy in 2020
I've recently tried if my Defy+ could learn some new tricks and I thought I'd share my findings.
CM11 build
I tried to build CM11 from Quarx repository, but it seems that many of its dependencies no longer exist and whole project is no longer buildable.
3.0 kernel
This one builds fine, however I was unable to boot it - there's one frame or random pixels followed by a reboot. I checked many branches and put the output into most probable directories. I wish there were any instructions as to what actually do with a built kernel. TWRP zips found here didn't work either. Anyone?
SD card size
Defy supposedly shouldn't work with SD cards larger than 32GB. But did anyone try bigger cards? My Defy mounts 256GB cards without any problems.
Debian on chroot
I set up a Debian environment with debootstrap. Unfortunately outdated kernel puts a limit on a Debian version that could be run. For 2.6.32.9 it is Debian Jessie.
With XServer XSDL it is possible to run a full graphical environment.
2.6.32.9 kernel modules
I also succeeded with building kernel modules for the old kernel. These are mostly filesystem modules and cryptographic ciphers. Now I could use whole Debian Jessie repository (49GB) locally from a squashfs filesystem.
Another nice feature is encryption with dm-crypt/LUKS.
I uploaded modules that insmod loads without any error.
CA certificates
These should be updated with system updates, but we won't have new CM/Lineage/stock releases anymore, so I did it by hand. If you want to try it for yourself, remount /system as writable, remove contents of /system/etc/security/cacerts/ (they could be expired) and copy certificates from the archive. Certificates are same as Debian's ca-certificates version 20200601.
Mirror
I also uploaded tools and images - self contained with instructions to go back and forth between stock and CM11, because many links here are spread across many threads or simply dead. Kernel modules and certificates are for CM11. I didn't try them with anything else.
I can't post a link to these files, because this is my first post. Search for ybea in Motorola Defy section at AndroidFileHost.
Another 2020 Defy warrior
ybea said:
3.0 kernel
This one builds fine, however I was unable to boot it - there's one frame or random pixels followed by a reboot. I checked many branches and put the output into most probable directories. I wish there were any instructions as to what actually do with a built kernel. TWRP zips found here didn't work either. Anyone?
Click to expand...
Click to collapse
Hello! Did you check on /bootstrap/bootstrap/binary and other folders? There seem to be a zImage (and the recovery one).
I tried to flash and boot the ROM at http://blechdose-live.de/download/kernel/3.0.x/:
Tried flashing from TWRP 2.8: failed.
Extracted the update-binary, copied it to /tmp and executed it from ADB shell (/tmp/update-binary 3 0 /sdcard/cm11-blah.zip) and flashed with some things, mostly partition related errors. After rebooting, it stays on black screen (turned on), ADB available but unauthorised (just look on Github how to enable ADB from recovery to solve that) and that's all; the ROM doesn't work. I'll try debugging this to check if I can do something.
ybea said:
CM11 build
I tried to build CM11 from Quarx repository, but it seems that many of its dependencies no longer exist and whole project is no longer buildable.
Click to expand...
Click to collapse
What a sad thing, this year even quarx2k.ru became offline...
MaicoLinuX said:
Hello! Did you check on /bootstrap/bootstrap/binary and other folders?
Click to expand...
Click to collapse
Files extracted from 20131213 version did not work for me. I tried swapping /bootstrap/ (and /system/bootstrap/) zImages, binaries, edited cmdline, anything I could think of. Always with the same outcome - black screen.
Flashing in TWRP (v2.6.3.0) initially also failed. Fix_TWRP_and_boot_kernel3.0_v2.zip (on AndroidFileHost) makes it succeed. It is 3.0.8 kernel. It froze during the boot, restarted and finished eventually.
ybea said:
Files extracted from 20131213 version did not work for me. I tried swapping /bootstrap/ (and /system/bootstrap/) zImages, binaries, edited cmdline, anything I could think of. Always with the same outcome - black screen.
Yeah, it did the same for me. Did you read the logcat while device was in that screen? I saw something crashing there (can't remember), anyway that's not so useful if you need a whole new ROM just for the new kernel version. Maybe modules are causing problems?
Pretty offtopic, did you try the OTG function? I can't get it to work, most people say it should work out of the box but I wasn't able to use my USB mouse. Didn't check dmesg, though.
Click to expand...
Click to collapse
MaicoLinuX said:
ybea said:
Always with the same outcome - black screen.
Click to expand...
Click to collapse
Did you read the logcat while device was in that screen?
Click to expand...
Click to collapse
How could I? Android isn't running yet. It it Linux that either fails to load or silently panics. That is my understanding anyway.
The right thing to do would be to check how cm11 build compiles the kernel and the 2nd-init (or whatever it is), but I am not knowledgeable enough, nor keen enough to do that.
OTG is buggy, but usable. If it doesn't work, unplug and plug it again. It is quite normal for my defy to recognize a device on a second or third attempt. No problems with mice, keyboards, flash drives, usb hubs. On the picture in the previous post you can see it with a wireless keyboard+touchpad. If I remember correctly, the driver is set to output 200mAh max. Maybe you mouse draws more (rather unlikely for a mouse). It works for me with cm11-20161124. Also, I think the port outputs 5V even after a device is disconnected, so it unnecessary drains power, but I am not so sure about it.
dmesg should definitely log any new device. Even if android stays quiet. If there's silence, perhaps your cable may of wrong type. USB A to USB micro varies with resistancy across two pins. I don't remember the details. If it is OTG cable, then it should work.
Or simply you have dirty socket/plug pins.
ybea said:
How could I? Android isn't running yet. It it Linux that either fails to load or silently panics. That is my understanding anyway.
Click to expand...
Click to collapse
AFAIK 2ndInit keeps adbd running so you can take a logcat/dmesg from there, also faced the same issue while flashing CM10.2 OTG kernel on CM11 (what was I thinking?) and from there was able to see that something was crashing.
ybea said:
The right thing to do would be to check how cm11 build compiles the kernel and the 2nd-init (or whatever it is), but I am not knowledgeable enough, nor keen enough to do that.
Click to expand...
Click to collapse
Nah, I think just taking some time to understand the 2ndInit boot process is enough, anyway when I get some free time I'll check about this all.
About OTG things, now will install CM11 3.0 kernel and see how it works (I expect some unstability) but don't really need to use the Defy, it's just there for experiments
Anyway, my main goal now is to install Debian natively (on /data partition because of the size) and get X running. As you said, the 2.6.32 kernel puts the limit at Jessie, but that's not a problem as it's still mantained IIRC. I'm using a prebuilt rootfs but it keeps throwing Segmentation Fault whenever I try to chroot there, don't know what happens with this.
I'm doing the same on other 2 phones (Galaxy Y and Pocket Plus, ARMv6 and v7 respectively) but one doesn't boot my compiled kernels (?) and the other complains about the buggy framebuffer driver (thanks Samsung/Broadcom). I went pretty offtopic...
PD: tried to flash some JB Ice Gun Edition v2.02 from CWM and after reboot the phone just is stuck on boot splash, but WIUI runs fine. Maybe the JB IGE BootMenu is broken or something like that.
MaicoLinuX said:
About OTG things, now will install CM11 3.0 kernel and see how it works (I expect some unstability)
Click to expand...
Click to collapse
I didn't have any luck with flashing zips with only the kernel. This 20131213 rom is the only way i know of. But frankly, there's more instability then stability in it. For example only home and power buttons work. OTG also non functional.
MaicoLinuX said:
As you said, the 2.6.32 kernel puts the limit at Jessie, but that's not a problem as it's still mantained IIRC. I'm using a prebuilt rootfs but it keeps throwing Segmentation Fault whenever I try to chroot there, don't know what happens with this.
Click to expand...
Click to collapse
Jessie is no longer maintained. It stopped being oldstable about a month ago. AFAIK it changes little - apt continues to work; unless your applications have dependencies to newer libc, they should at least compile.
I build Debian root with debootstrap. On host machine:
Code:
debootstrap --arch armhf --foreign stable /debian http://http.debian.net/debian
Then mounting on Defy:
Code:
# Mount an sd card partition
mount -o remount,rw /
mkdir -p /debian
mount -o remount,ro /
mount -t ext3 -o noatime,suid,exec /dev/block/mmcblk0p2 /debian
mkdir -p /dev/shm
mount -t tmpfs -o rw,nosuid,nodev,noexec none /dev/shm
mount -t proc proc /debian/proc
mount -t sysfs sysfs /debian/sys
mount -o bind /dev /debian/dev
mount -o bind /dev/pts /debian/dev/pts
mount -o bind /dev/socket /debian/dev/socket
mount -o bind /dev/shm /debian/dev/shm
Then debootstrap second stage:
Code:
LD_PRELOAD= TMPDIR= PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin HOME=/root SHELL=/bin/bash /system/bin/chroot /debian /debootstrap/debootstrap --second-stage
Done. To login:
Code:
chroot /debian /bin/su -
Don't chroot into bash. It will leak Android's shell environment into Debian's.
Android has its own groups and users. To make Debian adapt:
Code:
dpkg -i android-permissions_0.2_all.deb
Edit /etc/group, so that it contains:
Code:
inet:x:3003:root,_apt
net_raw:x:3004:root
Edit /etc/passwd/:
Code:
-_apt:x:104:65534::/nonexistent:/bin/false
+_apt:x:0:65534::/nonexistent:/bin/false
Edit /etc/adduser.conf:
Code:
-LAST_SYSTEM_UID=999
+LAST_SYSTEM_UID=99900
-LAST_SYSTEM_GID=999
+LAST_SYSTEM_GID=99900
-FIRST_UID=5000
+FIRST_UID=500000
-LAST_UID=8999
+LAST_UID=899900
-FIRST_GID=5000
+FIRST_GID=500000
-LAST_GID=8999
+LAST_GID=899900
Then:
Code:
apt-get update
apt-get install dialog
apt-get install locales
dpkg-reconfigure locales
apt-get install less man
If apt can't resolve hostnames select a nameserver in /etc/resolv.conf.
This how I setup Debian on chroot. Some of these steps may be unnecessary - they got accumuated over the years and I don't fully remember reasoning behind them. Debian inside /data/ should work too. I can imagine there would be problems with permissions on fat32 /sdcard, but /data/ is ext3.
For me and some users, while typing, or even scrolling up and down, time to time we see black virtual cursor for 0.5 sec
It's show ups for me about 10-100 times a day, very annoing!
I have seen this bug on every custom roms like RR 5.8.2, lineage os 14.1, Purenexus, etc, installed by TWRP 3.1.0-1 by nijel8/3.1.0.0 official one by strix
Changing different firmwares 7.2.9-7.3.16 - not helped.
Did a clean install throuth Mi flash tool - not helped.
Any ideas, how to fix this bastard?
Could it be recovery or even hardware problem?
If it were indeed a hardware issue, wouldn't we be seeing it on stock miui as well?
I suppose we need a common denominator - something that the custom roms have, but miui doesn't.
1) could it be related to root permissions? Has it been seen on both rooted and non-rooted devices?
2) Does it depend on how the ROM is flashed?
3) Has it been seen on other xiaomi phones? I assume both hydrogen and helium are impacted
just thinking out loud, what if we disable HID client drivers or the entire mouse support in kernel?
lukacsp said:
just thinking out loud, what if we disable HID client drivers or the entire mouse support in kernel?
Click to expand...
Click to collapse
Already tried and not helping.
Let start by taking some setup info and logs, guys. Make sure you have ran phone for a while and have seen cursor appearing at least few times. Run these commands on PC with phone USB connected:
Code:
adb shell dumpsys > c:\dumpsys.txt
Code:
adb shell dmesg > c:\dmesg.txt
Code:
adb shell logcat -d > c:\logcat.txt
or run their respective equivalents on phone terminal emulator...
Zip those files and post them here.
Haha I just saw the black mouse cursor pop up for a split second on my Helium running Pure Nexus. It's really not a big deal though. I'm sure it will eventually be fixed. It only pops up for like one tenth of a second. I'ts not even annoying but kind of funny.
Never seen it on my helium , on any Rom but then again i don't really stare at the screen looking for a cursor haha
Sent from my Mi Max using Tapatalk
Happening on Hydrogen RR5.8.2 - been happening on a few builds every now & again; annoying but not a deal breaker.
never seen on NitogenOS, but I saw it last day when I was trying nijie8's lineage, scroll up/down on the settings' About phone when back from about lineage.
Helium 3G/64G.
nijel8 said:
Already tried and not helping.
Let start by taking some setup info and logs, guys. Make sure you have ran phone for a while and have seen cursor appearing at least few times. Run these commands on PC with phone USB connected:
or run their respective equivalents on phone terminal emulator...
Zip those files and post them here.
Click to expand...
Click to collapse
I decided to clean flash your latest lineage 14.1 rom build 27.03.17 via your latest twrp 3.1.0-1, with latest firmware 23.03.17, and latest pico gapps 01.04.17
magic is happen, idk how, but for 3-4 days, I didn't see this mouse cursor bug at all... only one app that I didn't install is Google app for Google now (don't think that is a reason). BTW mb last kernel setup with hot plugging small cores give us instability and bugs ?
Will check for a while and get feedback if something changes.
It's a bug reported on Lineage's Jira. Here it is https://jira.lineageos.org/plugins/servlet/mobile#issue/REGRESSION-214
nijel8 said:
Already tried and not helping.
Let start by taking some setup info and logs, guys. Make sure you have ran phone for a while and have seen cursor appearing at least few times. Run these commands on PC with phone USB connected:
or run their respective equivalents on phone terminal emulator...
Zip those files and post them here.
Click to expand...
Click to collapse
After a free week of mouse cursor bag, I decided to reboot device..
After rebooting this bug coming back in 2-3 minute... WTF )
It happens to me on Pure Nexus which leads me to believe it's not a Lineage bug.
ajsmsg78 said:
It happens to me on Pure Nexus which leads me to believe it's not a Lineage bug.
Click to expand...
Click to collapse
We should to get some logs to nigel to fix this bastard
Get notice it on NitrogenOS v20170330...
Who used Android 7.1.2, bug still there ?) For a while, im coming back to MIUI Android 7, coz of this annoying bug
Resurrection Remix 7.1.2 Helium. BLACK VIRTUAL CURSOR CONFIRMED
Lineage OS 7.1.1-7.1.2 Helium. BLACK VIRTUAL CURSOR CONFIRMED
i noticed a battery drain since i first noticed the black cursor problem.
i started to think it is a stuck background process that kills battery. ( am i being so psychopath ? )
No cursor here. RR 5.8.3 on Helium. 7.4.13 firmware.
I have not seen the cursor in the last 11 days after enabling Settings -> Accessibility -> Large mouse pointer.
No i m not infected on any rom
I also occasionally see it. I am on stable MiUi 10 stock rom, but rooted with twrp & magisk
Hi,
I'm wanting to try Lineage OS on this device, to see if I can get the default (or change) media player to play LATM AAC.
Anyway's, I've flashed a few phones in my time, so easy I thought.
However, I 'cannot' get this thing into TWRP.
I've enabled USB debugging, and can reboot the device into 'bootloader'....
It's unlocked and when I issue the 'fastboot flash recovery twrp-........img it appears to go ok.
But I cannot get the device into the GUI for twrp.
The best I've been able to do, is to get the device into some other sort of recovery mode.
It doesn't go straight into it, instead goes into the droid robot, flat on his back, tummy open and underneath 'no command'.
By fluke, I can press every key on the controller and eventually I enter a 'text based', which has options for adb and usb uploading etc, but any attempts to install from this fail.
Someone 'please' put me out of my misery and tell me where I'm going wrong.
This overpriced junk is doing my suede in now.
Thanks
Neil
Not any help but just because you can't make it do something it is not intended to do doesn't make it "over priced junk"
Huawei P30 Pro (VOG-L29) using Tapatalk
Yea, perhaps my statement is a 'little' rash, but its annoying how a premium product cannot play AAC_LATM using the native media player, when cheaper Xiaomi units can.
And yes, I've contacted Nvidia about this and they think I should contact Freeview UK and ask them to change their encoding profiles.
If you're wondering, 'native' decoding is required for google live channels to be able to play 'said' streams
i have not used twrp on the shield in years, but instead of flashing twrp, have you tried just booting to it?
fastboot boot recovery twrp-xxxx.img
also, my shield tv was always a little finicky on which usb port i used on my computer, so try different ones. original cable is only one that works for me as well.
skiv71 said:
Hi,
I'm wanting to try Lineage OS on this device, to see if I can get the default (or change) media player to play LATM AAC.
Anyway's, I've flashed a few phones in my time, so easy I thought.
However, I 'cannot' get this thing into TWRP.
I've enabled USB debugging, and can reboot the device into 'bootloader'....
It's unlocked and when I issue the 'fastboot flash recovery twrp-........img it appears to go ok.
But I cannot get the device into the GUI for twrp.
The best I've been able to do, is to get the device into some other sort of recovery mode.
It doesn't go straight into it, instead goes into the droid robot, flat on his back, tummy open and underneath 'no command'.
By fluke, I can press every key on the controller and eventually I enter a 'text based', which has options for adb and usb uploading etc, but any attempts to install from this fail.
Someone 'please' put me out of my misery and tell me where I'm going wrong.
This overpriced junk is doing my suede in now.
Thanks
Neil
Click to expand...
Click to collapse
Better to fastboot twrp not flash it on the shield, also twrp will not show up on a 4k tv this is a limitation of twrp on the shield. I personally stopped using twrp after software version 6 of the shield, just too many headaches and I just use adb
Hi all!
Some days ago I urooted my TV android tv box with superSU and then I restarted it. From that moment when I plug the device it only reach the T9 logo (not the android one) and don't go further.
I've tried different ways to try to unstuck it, but nothing has worked.
I tried:
- enter recovery boot by holding the button in the av hole -> nothing happens
- install new firmware with adb sideload with both ubuntu and windows 10 -> always get errors (often error: closed, sometime other errors that at the moment don't remember)
- install new firmware with sd card using SDCard Installer -> the device doesn't boot when the sd is inserted
Moreover, with adb in ubuntu sometimes it recognises the device and I can enter the adb shell (but obtain errors when try any tipe of command), and sometimes don't (after adb devices I see list of attached devices: ??????????????? offline)
Now I'm thinking to try to install an ubuntu like on an usb pendrive...
I will be very grateful of any help/suggestion to how to revive my device :fingers-crossed:
Thank you!!!
Does this happen to be a pendoo model? I have a pendoo x10 MAX and i actually simply just installed supersu while it was rooted. Since then, I haven't gotten this thing to boot. Just stays on the boot screen the entire way. I wiped in recovery, knew that'd do nothing. I just wanted a root MANAGER. I tried Magisk, my favorite.. no go.. so then I went a bit old school.. so I tried ChainFire's SuperSU.. and THAT updated the SU binary! It said it succeeded.. it asked to do recovery install or normal install.. on phones, I've always done normal.. so I chose normal. Plus.. this thing has no custom recovery. I found it on Amazon. Overpriced, but great with the controller it had. It looks like I'll need a replacement and maybe a request to ask this guy if he could possibly NOT use something like KingRoot/KingoRoot/AmaraRoot or ANY One click root tool.. they just cause more bloatware, inciting boot issues and problems within the Android box itself. These One Click Root tools are out of control. It's to the point where I need to find a way in to adb and find the firmware for the latest version of this thing... X10Max from Pendoo.. I have not found a thing anywhere regarding firmware, and their website is ****. NOTHING *anywhere* on these things.. hell I'm about to return it as I bought it for $72. I have another one, same model.. wondering if the root method was different. About to boot that up and find out. I'll even swap the board. At this point.. he rooted it.. the WRONG way.. you can MOUNT THE /SYSTEM PARTITION IN RECOVERY. THIS IS ANDROID 9 we're talking about--the recovery supported by API v3.
This can and should have a TWRP custom recovery. If none exists, don't bother. As long as you can mount /system then you have a chance, at least, to root the damn thing.. which is why I'm still messing with it. I have another two weeks to return it. I'll give it another couple of days before I call it off and just switch out the good board for the bad one, return it, then return the other one and just use it until I find a way to use a custom recovery on this thing. There has to be.. unless there is no firmware available in sight (for an RK3318 or 3328, can't tell.. recovery mode says 3328, model name says RK3318. I see no difference at the moment aside from processor naming at this point--maybe speed?)
I'm still a nub with Android TV boxes so don't hold it against me for updating the damn root binary. If I could find a way to just reinstall the entire firmware and delete all previous stuff, I would. It would be worth it to learn. I would then mount /system in recovery and soldier on.
One little issue with this thing.. there's only one USB port that actually works. Same applies for the same exact product, a replication of the same thing.. was a "replacement" that still have/has the same qualities.
I've ranted enough. I vote more research into RK33xx processors and possible custom recoveries. I'm about to look for it based on only the device itself.
Note: Been stuck at boot screen ever since the binary was updated. I felt it was necessary to have a boot manager. I don't know where to even find the firmware. Can.. anyone point me in any direction? Something that MIGHT work on this thing? Android 6 or 7 would even suffice, return or no return, as "stuck on boot screen" will be my complaint. That's.. the actual complaint. I can't just *flash it* like the old days.. and maybe the original Android 9.0 firmware would suffice.. I don't know, but Pendoo.. wouldn't that be preferred?
You will need an SDcard to recover this box. I think the T9 32GB 4GB rom will do the job since its a cut down version.
Make a update SDcard and pop it in and power on the box. It will start the recovery on its own.
hello, sorry for my English I live in France I would have a question about the box: TV T9 RK3318, 4gb / 64gb. the problem is that the time is desynchronized on restart and creates problems to connect to applications when the time is out of order, I tried everything changed the time zone to deactivate and entered the time Manual it goes out of order all the time . is there a custom version or a version 10?
Very cook did I checked this out awhile back alot of good information that's for your contribution