Related
I was going to wait for this device to be added to devdb to make a release thread, but that's being delayed, if it'll ever happen. So, I'm making this thread as a placeholder. No big fancy text, just a known problem list and the release. If you're looking for this, you probably know what to do with it. Everything should work from flashing to backup and restore from all external media. If it doesn't, please report it.
KNOWN PROBLEMS:
1. This is a multirom edition of twrp, but there's no multirom support yet.
2. My wireless keyboard / mouse combo (an old Logitech MX something or another) fails to initialize the mouse on boot. I have to unplug and replug the USB receiver for the mouse to work. My wired mouse doesn't do this. I'm curious if anyone else sees a similar problem or if there's something weird with my hardware.
SOURCE:
device (branch cm-12.1-mrom)
kernel
vendor
CURRENT RELEASE:
For Android M:
twrp-20160222-UNOFFICIAL-foster.img
Known Issue: This release does not work on 4K displays. It boots to a black screen. Please use a 1080p display for TWRP until this is fixed.
For Android L:
twrp-multirom-20151112-UNOFFICIAL-foster.img
OLD RELEASES:
twrp-multirom-20150630-UNOFFICIAL-foster.img
twrp-multirom-20150624-UNOFFICIAL-foster.img
twrp-multirom-20150613-UNOFFICIAL-foster.img
MultiRom will be a must have on this device.
I really appreciate your work, and reading the various thread on xda I found out that you're one of the best developers for Nvidia Shield devices.
Without people like you we would all be locked in a large digital cage.
Compliments
Thanks Steel01!
I'm starting to slowly look at what I can disable in the kernel to shrink it down enough to fit in the recovery partition. Unfortunately, my first two ideas, network and sound, can't be unilaterally removed due to the android USB gadget (used for adb) depending on them. I've got it down to 26 MB, but iI dont know if it still boots. I'll try a few more things and hopefully have something working in the next couple days. I'm also hoping Tasssadar merges the 2.8.7.0 changes soon, the resize functionality will be useful (in testing I somehow shrunk my user data partition to 11 GB and had to reformat it get the full 4?? GB back).
Or it could be quicker than I thought. Todays test was successful. It's small enough to barely fit in the partition and appears to work correct. The link is in the OP. The next update to the multirom TWRP will probably make it too big again and I'll have to rip some more stuff out...
I want to install twrp recovery on my 16gb Shield, but i have no need for multirom. Is there an option to bypass the boot option or should I wait for a standard TWRP?
You didn't take much of a break before going back at it again. Thanks for your dedication!
Well, I'm not going back at it fully yet. Next week and a half will likely be pretty busy. I'm just doing a piece here and there.
This TWRP has multirom support, but does not require it or even set it up by default. In fact, to enable multirom, you have to install a separate zip (which I haven't released because it doesn't work). So no, you won't see any extra boot screens with this.
A standard TWRP build should be simple to make with the sources I've linked in the OP. I haven't released one here (or on any device I support) because I don't want to support it directly (basically, I'm supporting what I use myself). If no one else makes one, I might make a one time build for those that want it.
Hi Steel01, thanks for your efforts. I am a rookie at best at this, however, I managed to get this installed to my 16 gb shield tv, all appears to work fine, except I am unable to pair the shield remote, the shield game controller paired fine, but not the remote, just curious is this is expected, or maybe something wrong on my end. Also, If I wanted to load another rom at some point, is it as simple as booting to the twrp screen and selecting install? Hope that doesn't sound like a dumb question, I'm just a little unsure of that exact process. thanks
Remote controller fix
cdsn99 said:
Hi Steel01, thanks for your efforts. I am a rookie at best at this, however, I managed to get this installed to my 16 gb shield tv, all appears to work fine, except I am unable to pair the shield remote, the shield game controller paired fine, but not the remote, just curious is this is expected, or maybe something wrong on my end. Also, If I wanted to load another rom at some point, is it as simple as booting to the twrp screen and selecting install? Hope that doesn't sound like a dumb question, I'm just a little unsure of that exact process. thanks
Click to expand...
Click to collapse
Do not worry and follow these simple steps to fix your remote controller problem:
This is quite normal after a system reset or wipe.
If the remote did not connect:
If the microphone symbol is not flashing, hold down the back and home buttons at the same time until it flashes (3 seconds).
If the microphone symbol does not flash after holding for 3 seconds, charge the remote and try again.
To charge the remote, connect it to one of the USB ports on the back of your SHIELD with the included USB cable or connect it to another USB power source.
---------- Post added at 06:08 AM ---------- Previous post was at 06:01 AM ----------
cdsn99 said:
Hi Steel01, . Also, If I wanted to load another rom at some point, is it as simple as booting to the twrp screen and selecting install? Hope that doesn't sound like a dumb question, I'm just a little unsure of that exact process. thanks
Click to expand...
Click to collapse
Yes with TWRP it is very easy to flash a new rom, it is also recommended to use the recovery roms for updating your system.
Instead of running the OTO updates because this will undo your Root modification and reinstall the original recovery partition.
Download the correct firmware from this forum from the nvidia developers network, place it on a SD card boot to recovery and flash.
As a final suggestion have a look at the Flashify utllity (not compatible yet) or similar from the appstore, that a simple front end for flashing & backing up boot and recovery partitions. And it will enable you to boot to recovery in one click.
I have TWRP running on my Shield Portable / Shield Tablet without any problems.
Enjoy
Josti-Band said:
Do not worry and follow these simple steps to fix your remote controller problem:
This is quite normal after a system reset or wipe.
If the remote did not connect:
If the microphone symbol is not flashing, hold down the back and home buttons at the same time until it flashes (3 seconds).
If the microphone symbol does not flash after holding for 3 seconds, charge the remote and try again.
To charge the remote, connect it to one of the USB ports on the back of your SHIELD with the included USB cable or connect it to another USB power source.
---------- Post added at 06:08 AM ---------- Previous post was at 06:01 AM ----------
Yes with TWRP it is very easy to flash a new rom, it is also recommended to use the recovery roms for updating your system.
Instead of running the OTO updates because this will undo your Root modification and reinstall the original recovery partition.
Download the correct firmware from this forum from the nvidia developers network, place it on a SD card boot to recovery and flash.
As a final suggestion have a look at the Flashify utllity (not compatible yet) or similar from the appstore, that a simple front end for flashing & backing up boot and recovery partitions. And it will enable you to boot to recovery in one click.
I have TWRP running on my Shield Portable / Shield Tablet without any problems.
Enjoy
Click to expand...
Click to collapse
Thanks Josti-Band , that fixed my remote, I appreciate it greatly. Thanks also for the info on flashing, I'm still have one more question, when I flashed the img file from this thread TWRP, did I change the rom or just the recovery? It seems like the rom is the original that was on the shield tv, If rom was not changed do you or anyone else have a recommendation. Thanks again for the assistance.
cdsn99 said:
Thanks Josti-Band , that fixed my remote, I appreciate it greatly. Thanks also for the info on flashing, I'm still have one more question, when I flashed the img file from this thread TWRP, did I change the rom or just the recovery? It seems like the rom is the original that was on the shield tv, If rom was not changed do you or anyone else have a recommendation. Thanks again for the assistance.
Click to expand...
Click to collapse
No Problem, Your Shield TV has basically 3 partitions (to keep it simple)
1) Boot
2) Recovery
3) OS/Data (Rom)
With the steps you have followed
a) you unlocked your 1) bootloader, to enable the installation of unsigned packages to make this possible your personal data was erased/wiped from the 3) OS/Data partition.
b) Then you applied a new TWRP image to the recovery partition an replacing the old one.
So your 3) OS/Data (Rom) is still the original one you only wiped the personal data clean when unlocking the bootloader, this also the partition you will write your updated recovery images to. And stay updated.
I have TWRP running on my Shield Portable / Shield Tablet without any problems.
Enjoy[/QUOTE]
Josti-Band said:
No Problem, Your Shield TV has basically 3 partitions (to keep it simple)
1) Boot
2) Recovery
3) OS/Data (Rom)
With the steps you have followed
a) you unlocked your 1) bootloader, to enable the installation of unsigned packages to make this possible your personal data was erased/wiped from the 3) OS/Data partition.
b) Then you applied a new TWRP image to the recovery partition an replacing the old one.
So your 3) OS/Data (Rom) is still the original one you only wiped the personal data clean when unlocking the bootloader, this also the partition you will write your updated recovery images to. And stay updated.
Click to expand...
Click to collapse
Thank you, that makes better sense, I will try and load a rom and gapps and see how it goes. thanks again for the assistance
Steel01 said:
2. My wireless keyboard / mouse combo (an old Logitech MX something or another) fails to initialize the mouse on boot. I have to unplug and replug the USB receiver for the mouse to work. My wired mouse doesn't do this. I'm curious if anyone else sees a similar problem or if there's something weird with my hardware.
Hi Steel01 , I have a logitech k400r wireless keyboard and mouse, it seemed to work ok, except was very laggy, had to wait for it a few seconds each time I went to move the mouse, and sometimes mouse would freeze.
Click to expand...
Click to collapse
I have edited and deleted the orginal text from this post,and moved it to it's own thread. I realized I was beginning to hijack steels thread, I couldn't find a way to just delete the whole post, sorry.
Tassadar merged TWRP 2.8.7.0 into his multirom twrp fork today. So I ran new builds for everything I support. Unfortunately, I have not been able to test this device (TV's been busy all night), so YMMV. The other builds came off fine, so I don't see why this one should have any problems the last build didn't. Of interest in this build is the partition resize feature. So if someone does something weird like I did and ends up with an 11 GB data partition on the pro, it'll be *much* easier and quicker to fix now. Build is in the OP.
Steel01 said:
Tassadar merged TWRP 2.8.7.0 into his multirom twrp fork today. So I ran new builds for everything I support. Unfortunately, I have not been able to test this device (TV's been busy all night), so YMMV. The other builds came off fine, so I don't see why this one should have any problems the last build didn't. Of interest in this build is the partition resize feature. So if someone does something weird like I did and ends up with an 11 GB data partition on the pro, it'll be *much* easier and quicker to fix now. Build is in the OP.
Click to expand...
Click to collapse
What about the kexec-hardboot patch ? Do you have already tried it ?
The others binary for multirom execution are the same for all arm64 devices like the nexus 9 or we need a specific build for shield ? I never played with multirom stuff. There are specific problems to solve ? In case i can help you with experiments if you don't have much time.
P.S.
I tried your patch for the framework and all others new Nvidia binary + resigned private apk like blakepairing and others. But this year Nvidia added many others things to the framework. You can see by yourself with dex2jar.
It's a shame that for a stupid controller there are all this bloatware inside the firmware. Very bad behaviour, that a so big company not publish drivers for an hardware that we have bought. Fortunately we can use also better wireless controllers. But this fact really remove 10000 points from Nvidia as good company.
I've worked very little on the multirom side of things. The kernel repo has a mrom branch with a kexec patch, which still boots to stock. However, there's something getting triggered in the multirom init program that is skipping the boot screen. I haven't tried to track that down yet.
The controller part is off-topic, but there isn't really anywhere else to discuss it yet. Maybe I'll open a CM thread for discussion and put not working in bold at the top. Anyways, the framework patches work with the blakepairing shipped with the Shield TV, that's what I ship with my portable and tablet builds. But you have to deodex and stuff the class file back in the apk. Or easier, use the one in my vendor repo and just resign it. That should at least run. On a side note, the underlying technologies are all open source. WiFi Direct, wps, hid, etc. It just a standard USB hid controller with a WiFi chip and USB sound card. It's driven by an xmega (iirc) as well, those are all pretty open. It's obfuscation atm that stops me from completely reimplementing the pairing open source.
Steel01 said:
I've worked very little on the multirom side of things. The kernel repo has a mrom branch with a kexec patch, which still boots to stock. However, there's something getting triggered in the multirom init program that is skipping the boot screen. I haven't tried to track that down yet.
The controller part is off-topic, but there isn't really anywhere else to discuss it yet. Maybe I'll open a CM thread for discussion and put not working in bold at the top. Anyways, the framework patches work with the blakepairing shipped with the Shield TV, that's what I ship with my portable and tablet builds. But you have to deodex and stuff the class file back in the apk. Or easier, use the one in my vendor repo and just resign it. That should at least run. On a side note, the underlying technologies are all open source. WiFi Direct, wps, hid, etc. It just a standard USB hid controller with a WiFi chip and USB sound card. It's driven by an xmega (iirc) as well, those are all pretty open. It's obfuscation atm that stops me from completely reimplementing the pairing open source.
Click to expand...
Click to collapse
Already tried all. deodexed and resigned stock stuff, also used your framework patch and your (resigned) apks . not work in shield console. as i write above in shield console there are others proprietary things in the framework. Tested also with your wpa_supplicant and hostapd but the result does not change.
In any way i will retry
We can discuss in a separate thread. sorry for off-topic. can be useful also for others developers
This is very interesting, please continue with this work! Would be great to get the remote working on other ROMs.
Thanks!
Steel01 said:
I've worked very little on the multirom side of things. The kernel repo has a mrom branch with a kexec patch, which still boots to stock. However, there's something getting triggered in the multirom init program that is skipping the boot screen. I haven't tried to track that down yet.
The controller part is off-topic, but there isn't really anywhere else to discuss it yet. Maybe I'll open a CM thread for discussion and put not working in bold at the top. Anyways, the framework patches work with the blakepairing shipped with the Shield TV, that's what I ship with my portable and tablet builds. But you have to deodex and stuff the class file back in the apk. Or easier, use the one in my vendor repo and just resign it. That should at least run. On a side note, the underlying technologies are all open source. WiFi Direct, wps, hid, etc. It just a standard USB hid controller with a WiFi chip and USB sound card. It's driven by an xmega (iirc) as well, those are all pretty open. It's obfuscation atm that stops me from completely reimplementing the pairing open source.
Click to expand...
Click to collapse
Steel01 said:
I
KNOWN PROBLEMS:
1. This is a multirom edition of twrp, but there's no multirom support yet.
2. My wireless keyboard / mouse combo (an old Logitech MX something or another) fails to initialize the mouse on boot. I have to unplug and replug the USB receiver for the mouse to work. My wired mouse doesn't do this. I'm curious if anyone else sees a similar problem or if there's something weird with my hardware.
Click to expand...
Click to collapse
I have a logitech K830 keyboard with trackpad and have exactly the same issue as you. I have to unplug and replug the usb receiver before it will work with the recovery.
The recovery itself is working great for me. I can access my external usb hd from the file manager, and I did a TWRP backup to the external usb drive last night :good: Ive sideloaded this app to boot straight into the recovery from the TV.. https://play.google.com/store/apps/details?id=gt.reboot.utility
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.
Here' s my general experience with Remix OS (v 3.0.206) on my Asus T100. Not surprisingly, it's much the same to my Android x86 experience.
First, a big thanks to the team members at Jide and Anroid x86! And now on to my experience...
The install to my hard drive didn't proceed smoothly. I'm not sure it was because I already had Android x86 installed or because I have my Z drive mapped to my LAN and the install program tries (and fails) to mount my EFI partition there in order to install grub. To get past the failed install, I manually modified my EFI partition to add a menu item for Remix OS alongside Android x86.
After resolving the installation woes, Remix booted fairly quickly and the setup option worked fine. The OS works pretty well and seems to allow all my Android apps to run. I haven't installed and tried them all yet though.
Not all the hardware works. Here's what works and doesn't:
Working
Touchscreen - works
WiFi - 2.4 and 5 GHz both work. WiFi seems to stop working and can't be re-enabled if the tablet sleeps.
Track pad - works, but can't be disabled using the keyboard function key
Keyboard function key volume up and down
Keyboard function key brightness up and down
Dock USB
GPS
Suspend. (The notification light did not go out, so it wasn't fully suspended.) I didn't fully test suspend, so it may or may not be working properly.
Battery icon
External speakers
Accessing my dock hard drive
Not working
Auto brightness
Camera. It doesn't work at all.
HDMI Out. Video displayed does not fully fill width of screen. Audio still comes out of the T100. Booting will not complete if HDMI is connected; it stalls at the command line.
Notification/camera on light - stuck permanently on.
Auto rotate (and no manual rotate either)
Keyboard function key volume mute
Keyboard function key to disable/enable the track pad
Esc key doesn't always behave as the back key.
After putting the tablet into the keyboard dock, Remix launches its File Manager *every time*. It's annoying.
Not tested
Bluetooth
I had freezing issues with a previous Release Candidate of Remix, so this version is usable by comparison. However, with so many non-working items, Remix on the T100 is just passable and not quite ready for a daily driver for me. v 3.0.206 fixed an issue with not being able to use WiFi after it was turned off (and back). If auto-rotate was working, I'd consider using it as a daily driver...
Can you please share your installation procedure?
awyeong said:
Can you please share your installation procedure?
Click to expand...
Click to collapse
Hi, I must have missed the notification of your reply...
I purposefully omitted the installation procedure because it was a pain, I started with android-x86, and I don't really recall the exact steps. Are you having a specific issue?
Hi,
I also have a T100ha & was thinking about putting Remix on it. Actually i was debating buying a Chuwi hibook pro 2 to play with (windows 10 + remix). But its really identical to the T100HA I already have in terms of hardware specs (or at least close).
I am a little fuzzy on if the remix os plays with the partition for a dual boot experience or if this runs on top of the windows 10 OS.
For those starting from scratch, what would you suggest on a Remix OS install - or is it not even close to usable?
RichTJ99 said:
I am a little fuzzy on if the remix os plays with the partition for a dual boot experience or if this runs on top of the windows 10 OS.
For those starting from scratch, what would you suggest on a Remix OS install - or is it not even close to usable?
Click to expand...
Click to collapse
You don't need to create a new partition or resize an existing partition. It gets installed on your C Drive, most of it being installed in C:/RemixOS or whereever you choose. Your MBR will be modified to allow it to boot to WIndows or Remix.
Remix does not "run on top of" WIndows 10, like an emulator or VM. It is installed on the same hard drive, but is booted separately. But that reminds me...if you power on your tablet, it will boot straight to Windows. In order to boot to Remix, you have to a) hold power/Volume down to get to grub where you can select Remix, or b) Use Advanced Startup within Windows 10 to boot to Remix. It would be better if the Grub menu was presented on boot without the button mashing. Thanks, Microsoft/Asus!
You can/should try out a USB install to test it out. You can see what works/doesn't work for yourself and judge whether you want to install it to your hard drive or not. I still have it installed, but only use it occassionally.
So this isnt like Bluestacks which runs within windows? What I dont like about Bluestacks is the resources it uses even when its not running. The T100HA has very limited ones.
I see a number of posts on reddit with people trying to figure out how to install this on the T100HA.
Because I am a little fuzzy - Can you live install the ISO on a USB drive (like Ubuntu) for testing?
Anything not working for you on Remix?
So with the bootable ISO & usb. I power up, hit escape, choose the usb drive. I get the option of resident or guest - i choose guest, it says android-686, a black screen with a border pops up, then the system reboots & ends up in windows.
RichTJ99 said:
So with the bootable ISO & usb. I power up, hit escape, choose the usb drive. I get the option of resident or guest - i choose guest, it says android-686, a black screen with a border pops up, then the system reboots & ends up in windows.
Click to expand...
Click to collapse
This is the part that I don't exactly remember what I did to get it working.
You've probably disabled Secure Boot in Windows (required). I used Rufus to make my USB stick. I had problems when I made it with LiLi. So, if you didn't use Rufus, give it a whirl. Try the resident mode too.
Also, I think I used the Android-x86 USB install and copied the RemixOS files over top of it. Alternatively, go to http://www.jfwhome.com/2016/01/04/latest-steps-to-install-ubuntu-on-the-asus-t100ta/ and follow Step 1 only... First Steps: Prepairing for the Ubuntu Install
I'm stuck on logo...can you put your grub.cfg file here?
or al least the remix os entry...in other PCs, changing parameter I solve that...but now I can't in my asus T100taf...thanks.
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
Yes you heard it right!
It's finally done!
Its a custom ROM for the WIKO RAINBOW JAM!
The porting community for this phone is so small that the phone isn't even listed at this site. (Thanks XDA)
!Sorry that I posted that thread at the Wiko Rainbow Forum!
I don't know if this works on the 8gb version of the phone, which means only the 16gb variant is supported now.
____________________________________________________________________________________________________________
UPDATE !
Android MM (6.0) has some really annoying porting bugs(especially camera) which cause bootloops for example and I would even say, that porting Nougat to this phone is a LOT easier than fixing these bug(which doesnt mean, I'm not going to fix them)
Even newer update:
I tried like 2 months getting the camera to work and NONE of my builds worked out.
I think I have to accept, that the camera drivers are just stuck on Android 5.1 or even just the original Stockrom.
So now there is a VERY experimental build of the Ressurection Rom for the Wiko Rainbow Jam.
(Bluetooth, Camera, and a lot of Apps like CM-Audio dont work correctly
+ phone sometimes randomly reboots)
Yeah , this build can be installed exactly the same like the other one (exept the MM-Gapps)
v.01 = "https://mega.nz/#!E51imQgZ!FfoRt1kltg7_qkXSa2lAQTlK8Q2m1Mg6zs4E9WnQb54" (This has a bootloop!)
v.02 = https://mega.nz/#!gp1ATSCA!dJcc6YvSp-9ZFkv1sfETZpU_623mj9SrvvGiq6Y18ks (Known bugs mentioned earlier)
DONT FORGET TO WIPE DALVIK AND REFORMAT THE DATA PARTITION!
___________________________________________________________________________________________________________________
This is for the 3G version ONLY!
This rom is nearly completly untested and bugs shouldn't be a rarity.
PRE-REQUIREMENTS:
-A working WIKO RAINBOW JAM
-A Internet Connection
-Enough time to read my Instructions
-A USB-OTG Cable + USB MOUSE !IMPORTANT!
-Windows PC (Windows 7 or above)
-At least 80% Battery
What works?
WIFI / BT
Dual-Sim detection
SMS/MMS
Vibration
All of the buttons
Every app i tested till now...
Calling someone
Screen (Brightness / Pixel / Touchscreen ...)
Voice recording
720p YouTube playback ( The phone has a 50 hz display which means 60fps videos are experimental!)
Regular internet browsing via Chrome
+ The new Lineage OS 13 Features
Doesn't work
Camera ... fix will come soon!
Wrong Internal Storage detection ( only shows 1.45 gb in total)
UPDATE : to fix this problem you have to boot into recovery mode > wipe > Advanced wipe > check data > confirm
+ go to advanced wipe again > FS options > Repair FS > THEN RESIZE the partition
The Rom has still the build.prop from the phone I took the PortRom from ( INFINIX X510)
Feel free to post Feedback !
Modifications to the rom are welcome!
I WILL TAKE NO WARRANTY IF YOU BRICK YOUR PHONE . ALWAYS MAKE A BACKUP
HOW TO INSTALL.
1. : Download the zip file I uploaded : "https://mega.nz/#!dh9S2K4D!WsZlBayDdI-kIAj0bgJp5f9xUEtQWZU63WDGKcnM_rY"
2. : Extract everything and open the SmartPhoneFlashTool (SPFT) . Now search for the flashtool.exe ( YES this guide is for Windows)
3. Go to the Download tab and select the Android scatter file from the "Files for flashing" folder.
4. You should see that all of the fill the boxes up automaticaly.
5. Say goodbye to your old Lollipop rom and to your internal storage. Then shut the phone down!
6. Click the "Download" button first! and then connect your phone via USB to your computer.
7. If your drivers are setup correctly the bar below should start blinking and the phone is about to be flashed (DON'T UNPLUG THE PHONE NOW)
8. If the green "check" shows up you can safely disconnect your phone from the PC
YOU NEED A USB-OTG Cable now because the TWRP recovery has a broken touchscreen support
9. Boot into Recovery Mode via pressing "POWER BUTTON" + "VOL-UP". (Thanks to the creator of the Recovery!)
10. Use the USB Mouse to wipe the Dalvik Cache ( Wipe/Advanced Wipe/"now check only Dalvik Cache" ) and confirm you action
11. Reboot and optionally install GAPPS ( ARM Marshmellow Android 6.0) and root via SuperSU if you want
Proceed with the phone setup and you are ready to go...
I added all my source as a .txt file to the downloadable zip I mentioned earlier.
_______________________________________________
Is it hard to instal im a boob with phones and computer s :silly:
I would recommend a bit of knowledge on the whole flashing thematic. Just following the the instructions should be fine.
Just be sure that you have enough time to download the file properly and have at least 20 min of your time for the flashing process.
Camera fix
great rom, thanks. for when camera bug fix?
I dont know when this feature will work again. I tried so many bugfixing tutorials that i don't know where to start. It will probably be fixed in a few weeks, but from know on i need to wait until summer vacation because of school . That means that the project isn't dead yet
Dunno if someone is still interested in this device, anyway here's an interesting directory for those who are able to port ROMs:
https://androidfilehost.com/?a=show&w=files&flid=247444
...hope that inspires !
Hello,
Mega is asking for a key ??
Friendly,