Related
Hi all, i passed trough the bad experience of a phone with a broken screen, all my data was trapped inside the device and i couldn't see nothing on the screen :crying:
So i decided to develop a little app, in order to be able to break into my phone again and save the more stuff i could.
Gstreamer (aka Ghost streamer) is able to let you see your device screen once again (that was the primary purpose...) and deal with it by clicking and swiping with your mousepointer on your phone screen picture (yes, it's slow but it gets the job done )but without the need to install softwares like VNC and similars (Gstreamer only allows you to gain access your files in a way or another and try to save it),.
If your dead phone was rooted and with a custom recovery, then yur life will be easy in case of broken screen , but if not , then the music changes a lot, that's why i thought my software could help other people to solve theproblems i meet during my data rescue attempts.
No matter the device screensize, it will adapt to your device screensize and will make your life easier if you broken your phone screen.
I'm still adding features to it, and planning to organize it in a better way, correcting some bugs, testing it on different phones and android versions,but it's actually working and improving day by day
if someone is interested in testing it with me, and report then the experience i'd be happy to cooperate.
at the moment this is the pre-alpha stage for me , but this is how it looks now
{
"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"
}
if you are having bad times with your phone screen this may help you :fingers-crossed: just contact me if interested
use at your own risk it's still experimental, download it from the link below
http://www.filedropper.com/gstreamerv1000release
open for feature requests here , if you want me to add special functions, just ask here and i will see if it can be embedded or not.
get the latest nightly build on my git, just click on the "Download ZIP" button. (link below)
any advice is appreciated, thank you.
changelog!
new release, now the Apk operations are ok , now you can list, uninstall, pull, install apk from your PC.
always get the latest release from my git
https://github.com/TheBrainBooster/Gstreamer/archive/master.zip
BrainBooster said:
open for feature requests here , if you want me to add special functions, just ask here and i will see if it can be embedded or not.
get the latest nightly build here https://github.com/TheBrainBooster/Gstreamer just click on the "Download ZIP" button.
any advice is appreciated, thank you.
changelog!
new release, now the Apk operations are ok , now you can list, uninstall, pull, install apk from your PC.
always get the latest release from my git
https://github.com/TheBrainBooster/Gstreamer/archive/master.zip
Click to expand...
Click to collapse
new changelog! V1.2.1.0 release
added dpad navigation buttons
minor bugfixes
redesigned main panel
new changelog! V1.2.2 is available for the download
added swipe buttons
added memory info
minor bugfixex
check it out and let me know testers are welcome
01/02/2016
new changelog!
minur bug fixes
added file push , pull and sideload functions
...sadly i don't have feedback so i can't be sure it will work with all the android versions
...many changes heve been done, stay tuned for the next release
Hello,
tried you app, but it does not recognize my phone, because it has not debugging mode activated. I tried even "RSA ADB key inejection and..." but with no luck. For anther device, which has debugging mode active, I was able to get its data, but for the one with broken display and no debugging mode, it doesn't.
Any hints?
Regards,
can you provide some more informations about your device?
maybe you could try to repeat the procedure but in recovery mode
Hello,
Thanks for your time. So far you're the only one who gave me something as an information, or tip/hint.
My phone is an Samsung i9300i, with stock rom, only recently when trying to get the data through ADB, I have installed via ODIN an image named "CWM Recovery v6.0.3.6.tar", but still no effect in ADB.
Before replying to you I have tried recovery mode as well (power button, home, volume - and after 5 seconds volume up- as those were the steps required for my model to get into download mode). But I cannot get your up to recognize my phone. I tried with another one (HTC One M8s), with debugging mode on and the app recognize it in a flash. But with the broken one, no luck.
Are there necessary some custom drivers? Do you think some print screens could help?
a screenshot could help for sure
installing the proper adb drivers too, try with this --> http://forum.xda-developers.com/showpost.php?p=50008343&postcount=486
also installing the official kies software by samsung may help
whas the phone rooted?
can it boot normally?
do you see something on the screen?
what is the damage on you phone?
android version?
Hello and good morning (for me it's still morning),
No, the phone was not rooted, was "untouched". I gave up the idea I can retrieve data via software and I was thinking to try to open it and have a display temporary put, but it's time consuming and I'm short on time to recover the data (some business information for my boss).
I'll try the drivers you have wrote and I'll came back with screen shots as well.
Regards,
sorry for the late post edit, but it came to my mind after i wrote
by the way... are you sure you booted into recovery mode?
my software shoud see the phone anyway when you hit the test conection button
Hello and good morning (for me it's still morning),
No, the phone was not rooted, was "untouched". I gave up the idea I can retrieve data via software and I was thinking to try to open it and have a display temporary put, but it's time consuming and I'm short on time to recover the data (some business information for my boss).
I'll try the drivers you have wrote and I'll came back with screen shots as well.
LE: Yes, I'm booting in download/recovery mode (combination of pow+volume minus + home buttons and volume up after 5 -7 seconds - steps specific for Sam i9300i phones)
Regards,
miborion said:
Hello and good morning (for me it's still morning),
No, the phone was not rooted, was "untouched". I gave up the idea I can retrieve data via software and I was thinking to try to open it and have a display temporary put, but it's time consuming and I'm short on time to recover the data (some business information for my boss).
I'll try the drivers you have wrote and I'll came back with screen shots as well.
LE: Yes, I'm booting in download/recovery mode (combination of pow+volume minus + home buttons and volume up after 5 -7 seconds - steps specific for Sam i9300i phones)
Regards,
Click to expand...
Click to collapse
so you shoud see the phone connected maybe it will say: device-12345abcdefyourphoneID-(recovery) but if you have the drivers installed it should appear in the log window, moreover you said maybe you have a CWM recovery installed...
remember to reboot your pc ater the drivers setup
BrainBooster said:
so you shoud see the phone connected maybe it will say: device-12345abcdefyourphoneID-(recovery) but if you have the drivers installed it should appear in the log window, moreover you said maybe you have a CWM recovery installed...
remember to reboot your pc ater the drivers setup
Click to expand...
Click to collapse
Indeed I have had installed CWM (if by that you are referring to "CWM Recovery v6.0.3.6.tar" file - which I did, using ODIN (v.307)), as I thought the debugging mode would be activated, but it seem it doesn't. Please can you give me more details about what did you want to say by " moreover you said maybe you have a CWM recovery installed..."? Is it a bad thing? Should I flash to a stock rom?
And no, it does not show any devices like device-1234afsadsasdasd.
Regards,
what i mean is, if you installed a custom recovery and you also have your phone drivers properly installed you should have an adbd server running on the phone(provided by the custom recovery environment) and an adb client running on the pc, so they should see each other
BrainBooster said:
what i mean is, if you installed a custom recovery and you also have your phone drivers properly installed you should have an adbd server running on the phone(provided by the custom recovery environment) and an adb client running on the pc, so they should see each other
Click to expand...
Click to collapse
Ok, now I understand what is the purpose for that img.
So, bottom line is I cannot seem to install proper drivers. I'll try different combinations of uninstall plus install drivers from your link (i had used the ones from Samsung site, released this year), plus computer reboot, as so far I wasn't able to have ADB listener list my device (or your application).
Regards,
Root it! everything will be much more easy
http://androidmtk.com/root-samsung-galaxy-s3-neo-gt-i9300i
BrainBooster said:
Root it! everything will be much more easy
http://androidmtk.com/root-samsung-galaxy-s3-neo-gt-i9300i
Click to expand...
Click to collapse
I'll try, but, I'm not able to check what is my build number. As far as I know, I have only the stock image (exactly as the phone came with) and am sure it hasn't have the 4.4.4 version, but something like 4.3 something...I have a colleague, back at work which has some same device (Sam I9300i) and I could check the version on that terminal and try my luck.
Thanks again for your time and insight
miborion said:
I'll try, but, I'm not able to check what is my build number. As far as I know, I have only the stock image (exactly as the phone came with) and am sure it hasn't have the 4.4.4 version, but something like 4.3 something...I have a colleague, back at work which has some same device (Sam I9300i) and I could check the version on that terminal and try my luck.
Thanks again for your time and insight
Click to expand...
Click to collapse
anytime
if you need further help , just ask
BrainBooster said:
anytime
if you need further help , just ask
Click to expand...
Click to collapse
Hello,
I've just finished all leads meaning I have successfully rooted the phone by using your link; I got PASS message in ODIN using the exact image as the tutorial indicated. But, still I cannot connect to the phone with ADB, or by using your app.
If I boot normally I can hear the sound, see the top buttons lid and have the popup message in windows which tells me I can browse the mobile phone's content (onStdBoot.jpg).
If I boot in recovery mode (can see COM0 used in ODIN and can flash successfully) I get the devices on the second print screen (BootInDownloadMode.jpg) but cannot access it.
Could you please advise if there is anything else I can try?
Regards,
if you successfully rooted your device, booting it in recovery mode should make it show in my software
TWRP 331 Porting Thread for New UMIDIGI Power 4G
New thread for the new model UMIDIGI Power 4G Helio P35 Octa core Mtk 6765
Umidigi Power 4G MT6765 Octa Core 4G 4GB 64GB Android 9 Smartphone 6,3 inches
Everybody are Welcome!:good:
MANY THANKS TO OUR MODERATORS TO OPEN AGAIN THIS THREAD !
More attention to the Xda-developers Rules:
http://forum.xda-developers.com/announcement.php?f=256
Many thanks to "SUPER ADMIN" MR. MIKE
New twrp 331-test 1 for this device is builded!
Now need period of tests...
http://www.mediafire.com/file/cnqw8d2qkjqtp6k/Twrp_331_test1_Umi_Power.rar/file
reserved 1
Reserved 2
TWRP Not Working for Me
Finally received the phone today. Spent a few hours trying to get your TWRP port installed with no luck unfortunately. After flashing it via SP Flash Tool, I ran into an "Orange State" unlock warning (which I assume is normal). However it's followed by a bootloop. I can only get the phone to boot using the stock recovery.img. Any modifications to the recovery causes a loop.
On the other hand though, I was able to get root through Magisk (I'm using the latest 19.3 version), and patching the stock boot.img through the app, then flashing the patched boot.img to the phone with SP Flash Tool. I have Viper4Android working, which was my main reason for wanting root, so I'm satisfied for the most part. Can't wait to try this phone out as my daily driver!
SeekerofLight.iz said:
Finally received the phone today. Spent a few hours trying to get your TWRP port installed with no luck unfortunately. After flashing it via SP Flash Tool, I ran into an "Orange State" unlock warning (which I assume is normal). However it's followed by a bootloop. I can only get the phone to boot using the stock recovery.img. Any modifications to the recovery causes a loop.
On the other hand though, I was able to get root through Magisk (I'm using the latest 19.3 version), and patching the stock boot.img through the app, then flashing the patched boot.img to the phone with SP Flash Tool. I have Viper4Android working, which was my main reason for wanting root, so I'm satisfied for the most part. Can't wait to try this phone out as my daily driver!
Click to expand...
Click to collapse
I confirm the first part of this, same issue here... i'd like to flash a twrp for gsi purposes, but for now no luck
SeekerofLight.iz said:
On the other hand though, I was able to get root through Magisk (I'm using the latest 19.3 version), and patching the stock boot.img through the app, then flashing the patched boot.img to the phone with SP Flash Tool. I have Viper4Android working, which was my main reason for wanting root, so I'm satisfied for the most part. Can't wait to try this phone out as my daily driver!
Click to expand...
Click to collapse
Can you write how you got the root of the law? Instructions for inexperienced users.
Thank you in advance.
Root UMIDIGI Power with Magisk
mr A V said:
Can you write how you got the root of the law? Instructions for inexperienced users.
Thank you in advance.
Click to expand...
Click to collapse
Sure thing! Here's a Magisk root guide for anyone just getting started that I wrote up just now. (All mentioned files are provided in the zip.)
Step 0 - Download the Attached Zip File Below
Google Drive Mirror
Mediafire Mirror
MEGA Mirror
Step 1 - Drivers
Install the MediaTek drivers by running "DriverInstaller.exe". These are the drivers that worked for me. But if you have issues with them in Step 5, Google "Mediatek MT65xx USB VCOM Drivers" (or some variation of that) and try some others you can find.
-----------------------------------
Step 2 - Install ADB Interface
Install the Android SDK (ADB Interface). To do this drop the platform-tools folder (from the Step 2 folder) into your C:\ directory. Press the windows start button and search for "Environment Variables" and click on "Edit environment variables" from the results. Under SYSTEM VARIABLES on the bottom (not User variables above it) click on the "Path" variable, and click edit. In the new window that appears, hit "Browse..." and click on the "platform-tools" folder that you placed in your C:\ directory.
All this does is allows you to easily input adb commands into command prompt with no issues. This will be used to verify that the device is appearing properly and issue commands in case of emergency.
{
"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"
}
-----------------------------------
Step 3 - Install Magisk
Copy the Magisk.apk to your phone and install it.
(This is where you can then copy the boot.img to your device and patch it via the Magisk app to create the "magisk_patched_boot.img" file, however I have included the already patched file in Step 6 for the UMIDIGI Power so you don't need to.)
Also, this is the Magisk v19.3 Beta, but you can install another version.
-----------------------------------
Step 4 - OEM Unlocking/USB Debugging Mode
On your phone, go to Settings >> System >> Developer Options. (If you haven't activated Developer Options yet, do that by going to About Phone >> Build number, and tap it a bunch of times, but I'm sure you already know this lol)
In Developer Options, turn on "OEM Unlocking" to unlock the bootloader, and USB Debugging.
-----------------------------------
Step 5 - Verify That Your Phone is Detected with ADB
Connect your phone to your PC. Make sure you click "Allow USB debugging" on your phone. Then open up Command Prompt. (Protip: Type "color a" and press Enter if you want to feel like a REAL HACKERMAN.) Now, type in "adb devices" and verify that your phone is detected by your computer. If it's detected, then that's perfect you can move on to Step 6. If not, then uh... you may have to try and find some other MediaTek drivers mentioned in Step 1.
-----------------------------------
Step 6 - Set up SP Flash Tool
Open up SP Flash Tool on your computer by running "flash_tool.exe" in the SP Flash Tool Folder. (If at any time it shows a "Processing" window for some reason, just close and reopen the program if it doesn't go away on its own.)
On the first line choose "MTK_AllInOne_DA.bin". And the third line "Authentication File" can be left blank.
On the second line where it shows "Scatter-loading File", hit "choose" and find the "MT6765_Android_scatter.txt" file in the Step 6 folder. It'll load up and show a bunch of green/white rows in the space below.
Now this looked intimidating to me at first, but it's actually quite simple. As far as I understand (and I could be wrong but), the scatter file just tells the program where to place certain files, like a map for the program to follow. The scatter file I provided is for the UMIDIGI Power. The only thing we'll worry about for now is the boot.img file (but in the future, this is where you could also install a TWRP recovery once we get one that is confirmed to work.)
So in the white/green list, scroll down to where it says "boot" in the "Name" column, and click on the blank area in the "Location" column. It will bring up a window where you can browse to the "magisk_patched_boot.img" that I provided.
-----------------------------------
Step 7 - The Big Huzzah (Rooting)
Power off your phone and make sure it's UNPLUGGED. On SP Flash Tool, click "Download". This prepares the program to begin flashing your phone as soon as it is connected. Grab your phone with one hand, and with your other hand plug in the USB cable (if you only have one hand, use your mouth I guess). Your screen should not turn on at all throughout this process, but if it's successful, you should see that the program begins to flash your device after a second or two. Now just wait until it reaches 100% and says "Download Ok" with a green checkmark. And you're pretty much done!
You can then boot up your phone and check the Magisk app, as well as download a root checker from the Play Store to confirm that your phone has root access! Have fun!
Thank you, far-away friend from me, that you are such a sympathetic person! Thank you for writing everything so quickly and in detail. As soon as I receive my phone, I will definitely try to do everything as you wrote.
Tell me, do you plan to install any firmware on this device? For example, Miui. Or are you satisfied with the stock?
mr A V said:
Thank you, far-away friend from me, that you are such a sympathetic person! Thank you for writing everything so quickly and in detail. As soon as I receive my phone, I will definitely try to do everything as you wrote.
Tell me, do you plan to install any firmware on this device? For example, Miui. Or are you satisfied with the stock?
Click to expand...
Click to collapse
No problem! Unfortunately I don't see many custom ROMs coming to this phone, considering it's not a very popular device. I'd guess our best bet is to hope that the UMIDIGI F1 gets some support, and that anything on there can hopefully be ported over to this phone, but even that device isn't very popular either. For me though, that's not a huge issue because I'm actually quite satisfied with the stock firmware it has on board. It's basically stock Android Pie, and I've been able to add all the extra goodies I want into the phone through Magisk Manager and EdXposed with very minor issues. Most notably Viper4Android to fix the slightly tinny speakers and pump up the overall headphone experience too, and Gravity Box for some extra minor software customization.
Overall, I'd say the biggest downside to this device is the limited camera capabilities, and its somewhat limited performance for heavier tasks like 3D games / game streaming. But other than that, this feels like a very premium device. :good:
I thought about the fact that it is you who can transfer other firmware to this device. As a developer, let's say.
On the F1 already installing the firmware AOSP, LOS and other projects. But need to flash these firmware through TVRP recovery. For our device, there is no such recovery yet.
I have little understanding of the intricacies of the android. Sorry if my questions seem silly.
If we take the firmware for F1, for example AOSP, will it have to be somehow changed for our UD Power? Or can just take the archive, as it is, and flash it?
The processor of our smartphone is not very strong, so it is not for games. It is also not clear what RAM is installed. It looks like the manufacturer has installed a cheap part. Put single-channel LDDR 3. So he made a low price. At the expense of device performance.
mr A V said:
I thought about the fact that it is you who can transfer other firmware to this device. As a developer, let's say.
On the F1 already installing the firmware AOSP, LOS and other projects. But need to flash these firmware through TVRP recovery. For our device, there is no such recovery yet.
I have little understanding of the intricacies of the android. Sorry if my questions seem silly.
If we take the firmware for F1, for example AOSP, will it have to be somehow changed for our UD Power? Or can just take the archive, as it is, and flash it?
The processor of our smartphone is not very strong, so it is not for games. It is also not clear what RAM is installed. It looks like the manufacturer has installed a cheap part. Put single-channel LDDR 3. So he made a low price. At the expense of device performance.
Click to expand...
Click to collapse
I definitely consider myself to be a major noob with the more advanced Android development stuff. I only know enough to find my way around the internet and flash compatible software, haha. I've never looked into creating ports myself, but it's certainly something I think might be worth learning, especially with the limited device support on these phones.
And yeah, in terms of performance I don't expect much out of a phone at this price point, but for all the essentials - music, 1080p YouTube, web browsing, and mid to light gaming, it's surprisingly great considering the price. I haven't had any issues with the memory as of yet, so I wouldn't be too concerned, although you're definitely right in that they probably source some pretty cheap parts for these kind of phones.
SeekerofLight.iz said:
Sure thing! Here's a Magisk root guide for anyone just getting started that I wrote up just now. (All mentioned files are provided in the zip.)
"stubbed guide"
Click to expand...
Click to collapse
It works like a charm, thank you! by the way, were you able to boot that twrp or still nothing? and if you made it, were you able to flash a gsi over that too? i'm unable even to boot that twrp
---------- Post added at 09:30 AM ---------- Previous post was at 09:29 AM ----------
ghost45 said:
TWRP 331 Porting Thread for New UMIDIGI Power 4G
New thread for the new model UMIDIGI Power 4G Helio P35 Octa core Mtk 6765
Umidigi Power 4G MT6765 Octa Core 4G 4GB 64GB Android 9 Smartphone 6,3 inches
Everybody are Welcome!:good:
MANY THANKS TO OUR MODERATORS TO OPEN AGAIN THIS THREAD !
More attention to the Xda-developers Rules:
http://forum.xda-developers.com/announcement.php?f=256
Many thanks to "SUPER ADMIN" MR. MIKE
Click to expand...
Click to collapse
Can i ask you a guide on how were you able to boot it? i'm only getting a bootloop after flashing that from SPFlash
I will build one other version of recovery soon...
mg95tux said:
It works like a charm, thank you! by the way, were you able to boot that twrp or still nothing? and if you made it, were you able to flash a gsi over that too? i'm unable even to boot that twrp
Click to expand...
Click to collapse
Glad to hear it worked for you!
Still nothing. Unfortunately I haven't had any luck with booting into TWRP since I last tried it. Hoping ghost45 will be able to help us out with that when he gets the chance.
Bootloop - Secureboot
Nevermind, bootloader locked.
just type on CMD:
adb reboot bootloader
then
fastboot flashing unlock
Andre_Filho said:
Nevermind, bootloader locked.
just type on CMD:
adb reboot bootloader
then
fastboot flashing unlock
Click to expand...
Click to collapse
remember to allow oem unlock from developer settings in stock rom, otherwise it will fail!
SeekerofLight.iz said:
Finally received the phone today. Spent a few hours trying to get your TWRP port installed with no luck unfortunately. After flashing it via SP Flash Tool, I ran into an "Orange State" unlock warning (which I assume is normal). However it's followed by a bootloop. I can only get the phone to boot using the stock recovery.img. Any modifications to the recovery causes a loop.
On the other hand though, I was able to get root through Magisk (I'm using the latest 19.3 version), and patching the stock boot.img through the app, then flashing the patched boot.img to the phone with SP Flash Tool. I have Viper4Android working, which was my main reason for wanting root, so I'm satisfied for the most part. Can't wait to try this phone out as my daily driver!
Click to expand...
Click to collapse
How do you manage to work Viper.
Cause i'm having some problems, tested all versions and my Driver always stays on "Active: NO Format: Unsuported.... Abnormal"
BusyBox also don't seens to work.
:/
Some help?
Andre_Filho said:
How do you manage to work Viper.
Cause i'm having some problems, tested all versions and my Driver always stays on "Active: NO Format: Unsuported.... Abnormal"
BusyBox also don't seens to work.
:/
Some help?
Click to expand...
Click to collapse
The trick to getting Viper4Android to work is to make sure you have SELinux set to "PERMISSIVE" rather than "ENFORCING" on your phone. Here's a handy little app designed to automatically set it to permissive on boot!
https://forum.xda-developers.com/devdb/project/?id=1561#downloads
And for BusyBox, I was having issues too at first because I think with systemless root, BusyBox can only be installed in /sbin, which gets wiped after each boot. So I searched for "BusyBox" in the Magisk app and found a module called "BusyBox for Android NDK" which has worked perfectly for me.
One thing to note...
Sometimes SELinux doesn't always get changed automatically everytime you boot up. It's pretty consistent, but every once in awhile you may need to manually set it to permissive mode again if things don't seem to be working. But it's literally just pressing a single button, so not a big deal.
The other thing is with Viper itself- At times when I launch the app, the driver status says "abnormal" even after I've toggled SELinux to permissive. If you go into settings and toggle "compatibility mode" or "attach audio effects" on and then off that seems to refresh the driver status. Not sure why, but it works.
Let me know if you have any issues.
TWRP for UMIDIGI POWER
I ask for help in creating TWRP for UMIDIGI POWER firmaware ROM v1.5
Please make for this model TWRP
I am very grateful to you - I unlocked the phone and got the rights Root rights.
It remains only to create a TWRP for UMIDIGI POWER
At this forum, competent specialists and for other models everything is already done.
Maybe there is a website where you can make an order to create a TWRP?
Unfortunately, I do not know English and I do not know how to apply.
I would be very grateful and ready to test your work.
Hey guys! Today is a big day for Alcatel 1 owners, since the root is possible. Follow my steps to root your device!
NOTE: This is using a treble gsi rom
[DISCLAIMER] . I am not responsible for dead phones, SD Cards, Alarm clocks failing, etc. You have been warned!
WARNING: Your data will be lost during the process!
=====================================================================================
[Unlocking The Bootloader]
1 - Open Settings, go to About Device and tap Build Number 5 times
2 - Go back, tap on System, Advanced and Developer Options
3 - Check OEM Unlocking
4 - Turn off your phone
5 - Hold down the PWR and VOL+ buttons until the alcatel logo appears
6 - When the logo appears release the PWR button, while holding the VOL+ button
7 - In the recovery menu select reboot to bootloader
8 - In your pc with Minimal ADB and Fastboot installed type "fastboot oem unlock" (w/out the quotes)
9 - On the phone click the VOL+ button
10 - Reboot your phone and wait until the phone factory resets
=====================================================================================
[Installing LAge 16 (Android Pie)]
1 - Go to settings, and search factory
2 - Tap on Factory Reset
3 - When the factory reset is done, turn off the phone
4 - Hold down the PWR and VOL+ buttons until the alcatel logo appears
5 - When the logo appears release the PWR button, while holding the VOL+ button
6 - In the recovery menu select reboot to bootloader
7 - Download https://sourceforge.net/projects/an...910-UNOFFICIAL-treble_arm_avN.img.xz/download to your computer
8 - Open Minimal ADB and Fastboot and type "fastboot -u flash system filelocation.img" (w/out quotes and replace filelocation.img with your "lineage-16.0-20190910-UNOFFICIAL-treble_arm_avN.img" file location
=====================================================================================
[Rooting]
1 - Open Settings, go to About Device and tap Build Number 5 times
2 - Go back, tap on System, Advanced and Developer Options
3 - Tap in Root Access and select ADB and Apps
=====================================================================================
If you have reached this part, congrats! You have successfully rooted the Alcatel 1
{
"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 dude, that worked perfectly.
Any idea how to get GAPPs working?
What if I only want to root the phone without installing Lineage OS? I just want to remove the bloat apps that came with the phone e.g. Youtube Go, Asistent Go, etc.
I bought a cheap Alcatel 5033D-2BALWE1 from amazon warehouse deals and did not expect to be able to install a custom rom, very nice. But I do have few questions:
Does the rom you linked have some adjustments for this hardware or should any other GSI image work just as well?
Does all the important hardware work (basically LTE, wifi, bluetooth, gps, microphone + speaker + headphone jack, camera)?
Any trusted source for a stock rom that can be flashed with fastboot? There's one on alcatelfirmware.com but not sure how legit it is...
Because amazon warehouse deals sold them so cheap I bought 2, so after trying it I can answer some of my questions. First, my fastboot here (linux) doesn't have a -u switch, but it worked fine without it.
I tried andy yan's build first. Rotation sensor, display brightness, wifi, gps, audio output + micrphone + audio jack switching, camera works. I have not tried bluetooth yet, but the bluetooth settings are there, so there shouldn't be much of an issue. I have not tried a sim card yet.
I wanted something more well known, so I flashed system-quack-arm-aonly-vanilla.img.xz from https://github.com/phhusson/treble_experimentations/releases/tag/v204 and so far everything still seems to work fine. treble version is 27, so I guess all treble roms with support for this version should work. You will need the "aonly" variant, and not the ab one, and it probably has to be the arm (= all arm32?) variant, not the arm32_binder64 one.
ccxxx said:
Because amazon warehouse deals sold them so cheap I bought 2, so after trying it I can answer some of my questions. First, my fastboot here (linux) doesn't have a -u switch, but it worked fine without it.
I tried andy yan's build first. Rotation sensor, display brightness, wifi, gps, audio output + micrphone + audio jack switching, camera works. I have not tried bluetooth yet, but the bluetooth settings are there, so there shouldn't be much of an issue. I have not tried a sim card yet.
I wanted something more well known, so I flashed system-quack-arm-aonly-vanilla.img.xz from https://github.com/phhusson/treble_experimentations/releases/tag/v204 and so far everything still seems to work fine. treble version is 27, so I guess all treble roms with support for this version should work. You will need the "aonly" variant, and not the ab one, and it probably has to be the arm (= all arm32?) variant, not the arm32_binder64 one.
Click to expand...
Click to collapse
isnt the mediatek a 64bit cpu
Good question. /proc/cpuinfo says
Code:
Hardware: MT6739WA
which seems to be a Arm Cortex-A53, which seems to be a 64 bit cpu. I shall try the 64 bit variant of the rom.
ccxxx said:
Good question. /proc/cpuinfo says
Code:
Hardware: MT6739WA
which seems to be a Arm Cortex-A53, which seems to be a 64 bit cpu. I shall try the 64 bit variant of the rom.
Click to expand...
Click to collapse
right something going on after a few flashes, ive tried a few roms and my data in buggered cant get a mobile connection whatsoever ive tried getting into testing mode but no luck!
Any advice>?
---------- Post added at 05:48 PM ---------- Previous post was at 05:46 PM ----------
also getting this quite alot on lots of different roms -FAILED (remote: 'sparse image size span overflow.')
fastboot: error: Command failed
With the arm64 build from https://github.com/phhusson/treble_experimentations/releases/tag/v204 I get this too:
Code:
$ fastboot flash system system-quack-arm64-aonly-vanilla.img
Sending sparse 'system' 1/13 (131068 KB) OKAY [ 38.967s]
Writing 'system' FAILED (remote: 'sparse image size span overflow.')
fastboot: error: Command failed
I guess the system partition is just too big:
1.7G system-quack-arm64-aonly-vanilla.img
1.1G system-quack-arm-aonly-vanilla.img
Are the arm64 binaries really 50% bigger, or is there more stuff in the 64 bit build, or is there empty space in the image?
Anyway, I put my sim card into slot 1 and immediately got a decent 4G connection, I didn't have to do any fiddling (O2/Eplus in germany). I only tried the AOSP image I linked, not the one from andy yan. It seems there are some issues with that image though, alarms and messaging notifications are two things that don't seem to work yet.
I keep getting this:
Code:
fastboot oem unlock
FAILED (remote: 'unknown cmd.')
fastboot: error: Command failed
FYI i have enabled oem unlock. Any clues?
hello
can i have the source for this because i want to optimize it.
my reason is the boot time is very long.
Hi Guys,
I've been trying since yesterday and get a boot loop on the lineage os boot.
I haven't got past the boot animation.
I've tried to flash to stock with spflash tool. NO success so far.
I need help, please.
I'm running Linux i3.
Thanks a lot!
FNMONTEFALCONE said:
Hi Guys,
I've been trying since yesterday and get a boot loop on the lineage os boot.
I haven't got past the boot animation.
I've tried to flash to stock with spflash tool. NO success so far.
I need help, please.
I'm running Linux i3.
Thanks a lot!
Click to expand...
Click to collapse
Have you tried clearing the cache on the recovery menu and trying to boot again?
Sometimes the phone gets stuck on boot, any clues?
No success with rooting
Chinchila01 said:
Have you tried clearing the cache on the recovery menu and trying to boot again?
Click to expand...
Click to collapse
Dear Chinchila01,
Yes, and yes. I tried everything. The phone is now at my carriers tech support team. It's been more than a week and they can't fix it!!
I'm surprised, I must've really screwed it up somehow!
Well, I got a backup while they decide what to do and I've decided not to touch it.
I guess some phones are just not for fooling around with.
Hope this helps.
Best,
Facundo
I have much the same issues.
Lineage 16 works almost completely if it ever boots, sometimes you get lucky!
Lineage 17 usually boots but doesn't work really well, no gps, etc.
No GAPPS either way.
So close yet so far!
Solution
@caish5
@FNMONTEFALCONE
Hey guys, just to tell you:
Have been trying out this rom: https://github.com/phhusson/treble_experimentations/releases/tag/v32
And so far everything's good.
I installed system-arm-aonly-go-su.img.xz using the following method:
1. Extract it.
2. Reboot to fastboot.
3. fastboot flash system <file>
4. Reboot to recovery
5. Factory reset and cache clean.
6. Reboot.
Thanks, that worked. Even GAPPS!
Chinchila01 said:
@caish5
@FNMONTEFALCONE
Hey guys, just to tell you:
Have been trying out this rom: https://github.com/phhusson/treble_experimentations/releases/tag/v32
And so far everything's good.
I installed system-arm-aonly-go-su.img.xz using the following method:
1. Extract it.
2. Reboot to fastboot.
3. fastboot flash system <file>
4. Reboot to recovery
5. Factory reset and cache clean.
6. Reboot.
Click to expand...
Click to collapse
I've tried a lot of different GSI images, All Pie ones take a long time to boot or don't boot and have to restart until it does.
I got this phone few days ago, Surprised me that it can run GSI's been having a good time testing different roms.
Thought there would be a TWRP but haven't found one. Makes it hard to have a rom with play store and root.
That's what i'm trying to find.
Chinchila01 said:
@caish5
@FNMONTEFALCONE
Hey guys, just to tell you:
Have been trying out this rom: https://github.com/phhusson/treble_experimentations/releases/tag/v32
And so far everything's good.
I installed system-arm-aonly-go-su.img.xz using the following method:
1. Extract it.
2. Reboot to fastboot.
3. fastboot flash system <file>
4. Reboot to recovery
5. Factory reset and cache clean.
6. Reboot.
Click to expand...
Click to collapse
Does that rom have SuperSU ? it say's SU at the end but installed it and no SU app ?
Introduction
This is the LineageOS 17.0 (non-GSI) port for K-touch i9 a.k.a Anica i9. Due to the lack of kernel source code, this port comes with a prebuilt kernel image, but the ramdisk has been updated to support a proper System-as-Root system partition as is required by Android 10.
This is ONLY compatible with the MT6739 variant of this phone.
About the phone
The K-touch i9 is an ultra-mini phone produced by K-touch (Ktouch / Anica) based on the MT6739 SoC. I got the phone purely due to its interesting size (similar to the Palm phone) and the desire to port real custom ROMs to it to see if they can work well. I mainly use it as a backup phone, so this port might not be thoroughly tested enough for daily drive.
Known Issues
- Some particular animation / gifs will skip frames or repeat incorrectly
Images
{
"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"
}
Flashing instructions
1. Unlock the phone (reboot to bootloader by holding volume up on boot, run `fastboot flashing unlock` and confirm)
2. Flash TWRP image from here
3. Reboot to recovery (hold volume up and choose Recovery accordingly)
4. Backup all stock partitions whatever way you like (especially boot / vendor)
5. Flash this LOS 17 port image and format data
6. Reboot and enjoy
Please note that after flashing this LOS 17 image, you have to restore the stock boot.img before being able to install A-only Android 10 GSIs again. Although you MIGHT be able to boot phh A/B GSI 10 on the boot.img of this LOS 17 port, please note that this is not tested and you still need to shrink the image size before phh GSIs can work -- the same as the A-only situation.
Why not GSI
There is no reason why not to use a phh GSI on this phone, given that phh GSIs work pretty well and I have actually fixed a few bugs for it too and I absolutely love it. However we can't play with some certain things, for example, transitioning to System-as-Root, in a GSI, and that's why I started this port just for fun. Also this device has such a small system partition that GSIs won't work out-of-the-box and require some manual adjustments just for the device, which kind of defeats the purpose. Nevertheless, I will contribute my fixes to GSIs so that things will work as well on GSIs as on my device-specific ROM ports.
Downloads
20191025: https://www.androidfilehost.com/?fid=4349826312261605900
Alternatively, you may check the latest updates to both the TWRP and the LOS 17 port on my GitHub
Source code
https://github.com/PeterCxy/android_device_ktouch_i9
There is no kernel source code available for this device, unfortunately.
Credits
all the people that have worked on MTK devices before me.
twrp link does not work
theleftykid said:
twrp link does not work
Click to expand...
Click to collapse
It works here. It links to a GitHub release page where you can download recovery.img for TWRP
Hi,
I bought this phone, but with different CPU- MT6580, 5MP camera at the back, would this ROM be compatible with it well?
I've tried to flash the TWRP recovery, but it failed - "FAILED (remote: size too large)" so it mean the recovery image not compatible with my phone?
This device is really nice, but huge let down by the operation sys. The battery drain really fast, always "phone idle" take place at the top of battery consuming chart.
Thank you!
hi, i have tried to flash the twp from your github site. i get an error that flashing was FAILED, file is too large. my unit is Ktouch/anica i9s with October 2019 update.
is there any chance you can upload the original recovery.img as well pls.. thank you.
theleftykid said:
hi, i have tried to flash the twp from your github site. i get an error that flashing was FAILED, file is too large. my unit is Ktouch/anica i9s with October 2019 update.
is there any chance you can upload the original recovery.img as well pls.. thank you.
Click to expand...
Click to collapse
Based on the previous comment before you, you seem to have the MT6580 version of the phone. This means you have a different and smaller gpt than the one from the OP that uses MT6739. You can't flash this ROM or any recovery from the MT6739 since they have different hardware and different partition layout. If you flash something, it will end with a nice brick
Cheers!
Rortiz2 said:
Based on the previous comment before you, you seem to have the MT6580 version of the phone. This means you have a different and smaller gpt than the one from the OP that uses MT6739. You can't flash this ROM or any recovery from the MT6739 since they have different hardware and different partition layout. If you flash something, it will end with a nice brick
Cheers!
Click to expand...
Click to collapse
Well, I’m sending myne back to get the mt3739 so I could mount 128gb sd card and to try this buil. It look promissing.
theleftykid said:
hi, i have tried to flash the twp from your github site. i get an error that flashing was FAILED, file is too large. my unit is Ktouch/anica i9s with October 2019 update.
is there any chance you can upload the original recovery.img as well pls.. thank you.
Click to expand...
Click to collapse
You boot into the original OS and the recovery will be back.
Thank you for this ROM.
I used it on my K-touch i10. Its the same as the i9 but the shape is slightly different.
I have the 3gb - 64gb version and it seems OK.
I had to use BiTGApps-Q for Playstore to appear.
I also had to go into the USB developer options to set up file transfer from a PC.
And no wallpaper app from holding on home screen.
I hope you keep this up to date else I might have to try and work out how to apply security patches.
Thanks again
EDIT. Oh so are you saying I could just try and install the GSI?
Edit. OK so Wellbeing and problems with Gapps is to do with Android 10 and gapps.
I also found twrp hard to control. The swipe action and pressing near the edge was difficult.
I don't have face recognition to unlock, not sure if that's because lineage os doesn't have it or the i9 doesn't, but certainly possible on my i10.
The swipe action in lineage is also difficult.
Thanks again. Just want to let you know.
Edit. Also a problem for me is when it's charging, touch screen gives the odd ghost press when used.
Ive found forcedoze useful with this phone.
Works with K-Touch M16?
Theoretically speaking this Rom should work in the K-Touch M16 as it has the exact same specs, processors, etc. Being the only difference is that it has a fingerprint sensor.
So I was wondering does anyone know if this custom ROM and TWRP works on the K-Touch M16.?
how do i download this rom. there are no active links available!
PeterCxy said:
Downloads
20191025: https://www.androidfilehost.com/?fid=4349826312261605900
Alternatively, you may check the latest updates to both the TWRP and the LOS 17 port on my GitHub
Source code
https://github.com/PeterCxy/android_device_ktouch_i9
There is no kernel source code available for this device, unfortunately.
.
Click to expand...
Click to collapse
From the first post
m16 tried
I have tried this with my M16, which is very similar to i9, same cpu same spec, got fingerprint though... no luck, unable to boot into recovery, anyone successfully done?
It worked with my K-touch i10.
I guess you should start looking at TWRP. If you have the same processor you should be able to get TWRP going.
Sorry no help here, maybe try a TWRP forum or something.
chinese bootloader
hi, i just got the phone so i wanted to flash this rom. but my bootloader is in chinese and i don't speak/read chinese.
can anyone here please help me get trough the bootloader so i do all the steps correctly.
i attached the picture from bootloader and also what google translate offers for translation.
does volume up and down works correctly on your devices? on my it just jumps one step down and up on ether up key or down key when i press and hold the key ti gradually turns volume up on ether up or down key.
I have an i10 and am no expert.
When I reboot and hold up-volune I get 3 options. Recovery, Fastboot and Normal in that order.
Are you sure your phone is the mt3769. As I had an i10 which was was MT6580 and I got those options. I did have Fastboot though. Sorry don't still have it for reference.
I just found out on youtube this menu should pop up when you press volume down + power on. But on my phone it also boots to this menu when i press volume up + power on. Guess i received defective volume buttons on my phone. Too bad as it is such a nice little phone.
Are you able to use the volume keys to move up and down the menu you took a picture of? Moving in this menu and selecting should be the up and down volume keys. Guess then you could see for sure if you have a key problem.
I did manage to take my phone apart as when I dropped it I managed to disconnect the screen cable inside but was lucky to be able to fix it.
---------- Post added at 12:23 PM ---------- Previous post was at 11:44 AM ----------
PeterCxy said:
...you still need to shrink the image size before phh GSIs can work...
...
Also, this device has such a small system partition that GSIs won't work out-of-the-box and require some manual adjustments just for the device, which kind of defeats the purpose. Nevertheless, I will contribute my fixes to GSIs so that things will work as well on GSIs as on my device-specific ROM ports.
Click to expand...
Click to collapse
Hello I'd like to update this for myself. I thought I'd use the GSI image but you say it needs resizing before use. Can you give me any pointers as to how you do this?
free30 said:
Are you able to use the volume keys to move up and down the menu you took a picture of? Moving in this menu and selecting should be the up and down volume keys. Guess then you could see for sure if you have a key problem.
I did manage to take my phone apart as when I dropped it I managed to disconnect the screen cable inside but was lucky to be able to fix it.
Click to expand...
Click to collapse
i am unable to enter the correct bootloader that gives you three options you mentioned before. i already contacted the seller to see what we can do cause i just received the phone. on this chinese menu i can navigate only down (pressing volume up or down moves the selection down) and i can select the item via power button.
{
"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"
}
Amlogic G12*/SM1 Family Devices
Code:
- Your warranty is now void.
- You have been warned.
- Use at your own risk.
Introduction:
This is the Official Lineage OS 19.1 thread for the Amlogic G12*/SM1 SoC family of devices.
Downloads:
Please follow the install instructions in your device's Wiki page linked below exactly, and make sure your device's firmware matches the required firmware listed:
Official Builds:
deadpool - Google ADT-3
wade - Dynalink TV Box (4K)
Disclaimer: My unofficial builds have full Android TV Google Apps and some other goodies included. OTA's roll roughly once a month. Support not guaranteed or implied.
Unofficial Builds:
deadpool - Google ADT-3
dopinder - Walmart Onn UHD Box
sabrina - Chromecast with Google TV
wade - Dynalink TV Box (4K)
We also support a few development boards, but at least (for now, until we have time to write up instructions), you're on your own to figure out the install process and set things up:
m5 - Banana Pi M5
odroidc4 - Odroid C4
radxa0 - Rock Pi Radxa Zero
EDIT: The development boards don't boot on LineageOS 19.1 at the moment for some reason, we're looking into it.
If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.
Known Bugs:
Recent apps/Multitasking menu doesn't launch.
(sabrina only) The remote firmware sometimes gets hung up, you can reboot to solve this issue.
(dopinder/sabrina) L1 is currently broken, this is what is holding up official builds for these devices.
Notes:
GApps are baked in on Unofficial builds - No, I will not be building without GApps included for this device. These builds are built, packaged, and signed by me, and not affiliated with LineageOS whatsoever.
Firmware is shipped in the ROM package for this device, so you'll end up on the newest version of compatible firmware after install. Please don't touch firmware partitions after install.
On the unofficial OTA is provided the same way officials would have them.
Find any more on an official build? Report them according to this guide.
FAQ:
Does L1 Widevine DRM break when I unlock my bootloader?
Nope, it works fine. L1 certificates, and the mechanism that reports is all still exist and work as expected.
Can I haz Netflix?
Yup! Play Store has it for you. Unless you're on dopinder or sabrina, but that will be fixed soon hopefully.
Is this Android TV or Google TV?
Android TV, with some of the better components of Google TV.
Can I go back to stock and relock the bootloader?
Yeah, grab the factory image for your device and flash it just like you would for a Pixel device, you can find the factory images here. Don't know it I'd relock though, consider that process largely untested on these device. Especially on sabrina, where you can't necessarily re-unlock should you ever want to.
Are these the stock codenames for these devices?
Astute observation, no, they are not. The ADT-3 is actaully `adt3`, but earlier in production is was `deadpool`, which is much cooler. The Dynalink box internally is extremely similar to the ADT-3, so we coined it `wade` after Wade Wilson, AKA deadpool. The Onn box is in the same family, but different enough to coin it `dopinder`, after, well, go watch Deadpool the movie I guess. sabrina is actually the codename given by Google - no clue as to the reason.
Does it pass SafetyNet?
Maybe - the only sure fire way it Magisk, as our boot loader is unlocked and can't be relocked safely.
Does the stock remote work?
Yup, just like it would on stock, in-remote-microphone and all! If it's an IR remote like wade's, it will even work in recovery!
Can we we support higher resolution than 4K, higher FPS, or HDR on non-certified screens?
Nope.
I have a very similar device! Can I install these builds and use them?
No. Please don't do that. You will brick your device, as we include firmware and bootloader images.
If you're a developer looking to help port to a new device, contact me.
Kernel Source: https://github.com/LineageOS/android_kernel_amlogic_linux-4.9
Contributors:
npjohnson
bgcngm
stricted
webgeek1234
deadman96385
trautamaki
luca020400
aleasto
i probably will write up install instructions for the `BananaPi-M5` and `Odroid C4` Soon™
its a bit more complicated than just booting into recovery and flashing it unfortunately
I managed to install this on the onn 4k tv box (I used a usb keyboard and flash drive in the recovery) and everything went fine while installing but now I'm just stuck at the boot animation. I've left it on for at least 30 minutes and it never goes anywhere. Here's the serial log: https://paste.ee/p/7PAxS
It pretty much just stops there except for the occasional healthd battery message.
Do these builds support Signature Spoofing to replace GApps with MicroG?
Big Dumb Object said:
Do these builds support Signature Spoofing to replace GApps with MicroG?
Click to expand...
Click to collapse
No, as MicroG doesn't emulate what Android TV needs. Different GMSCore.
lmore377 said:
I managed to install this on the onn 4k tv box (I used a usb keyboard and flash drive in the recovery) and everything went fine while installing but now I'm just stuck at the boot animation. I've left it on for at least 30 minutes and it never goes anywhere. Here's the serial log: https://paste.ee/p/7PAxS
It pretty much just stops there except for the occasional healthd battery message.
Click to expand...
Click to collapse
yeah, aware of the issue, it's video firmware not loading, building new builds now.
But for what it's worth, you don't need a keyboard or drive - you can adb sideload it over usb - easiest method, just like the wiki describes.
npjohnson said:
No, as MicroG doesn't emulate what Android TV needs. Different GMSCore.
Click to expand...
Click to collapse
Sad. I vaguely recalled something about that, but couldn't find any concrete proof when asked.
Please consider releasing the full Android as it was with Shield TV. I believe it will be in demand, given the negative attitude of a lot of power users towards Android TV.
Big Dumb Object said:
Sad. I vaguely recalled something about that, but couldn't find any concrete proof when asked.
Please consider releasing the full Android as it was with Shield TV. I believe it will be in demand, given the negative attitude of a lot of power users towards Android TV.
Click to expand...
Click to collapse
Eh, maybe once we're in a more functional state (eg. Hardware OMX gets fixed).
npjohnson said:
yeah, aware of the issue, it's video firmware not loading, building new builds now.
But for what it's worth, you don't need a keyboard or drive - you can adb sideload it over usb - easiest method, just like the wiki describes.
Click to expand...
Click to collapse
I couldn't figure out how to navigate the recovery menu. I tried the button on the side like in the stock recovery but pressing it did nothing and holding it would change the highlight color to green but it didn't actually run the option that was highlighted. It was detecting the button presses (there were keyevents in the serial log) so it isn't just a broken button. I tried doing adb sideload without selecting the option but I just got `adb: sideload connection failed: closed`
lmore377 said:
I couldn't figure out how to navigate the recovery menu. I tried the button on the side like in the stock recovery but pressing it did nothing and holding it would change the highlight color to green but it didn't actually run the option that was highlighted. It was detecting the button presses (there were keyevents in the serial log) so it isn't just a broken button. I tried doing adb sideload without selecting the option but I just got `adb: sideload connection failed: closed`
Click to expand...
Click to collapse
okay, figured it out, you need to hand flash DTB before booting recovery, will update instructions
npjohnson said:
okay, figured it out, you need to hand flash DTB before booting recovery, will update instructions
Click to expand...
Click to collapse
Sounds good. One more question, is this build using a 64-bit kernel? I'd like to use the app for my drone on a big screen and this box would've been perfect if the stock kernel wasn't 32-bit.
lmore377 said:
Sounds good. One more question, is this build using a 64-bit kernel? I'd like to use the app for my drone on a big screen and this box would've been perfect if the stock kernel wasn't 32-bit.
Click to expand...
Click to collapse
64-bit kernel, 32-bit userspace - aiming to do 64 bit userspace someday.
Do you have an ETA for when the next builds will be done?
lmore377 said:
Do you have an ETA for when the next builds will be done?
Click to expand...
Click to collapse
they're uploaded now - sorry, got caught up putting out fires at work all day today lol
npjohnson said:
they're uploaded now - sorry, got caught up putting out fires at work all day today lol
Click to expand...
Click to collapse
I'll try it and flashing dtb for the button in recovery in a bit
lmore377 said:
I'll try it and flashing dtb for the button in recovery in a bit
Click to expand...
Click to collapse
DTBO/DTB - they need to be in sync.
npjohnson said:
DTBO/DTB - they need to be in sync.
Click to expand...
Click to collapse
I flashed the two (I got them from here) and now the button and usb otg don't work at all. I tried to flash back to stock but the box got stuck on the can't load android system screen and it was ignoring all my attempts at interacting with it (it was even ignoring Ctrl+C in uboot), but luckily I managed to boot into the lineage os recovery by putting it on a flash drive and holding down the button then wiping /misc thru the serial console.
lmore377 said:
I flashed the two (I got them from here) and now the button and usb otg don't work at all. I tried to flash back to stock but the box got stuck on the can't load android system screen and it was ignoring all my attempts at interacting with it (it was even ignoring Ctrl+C in uboot), but luckily I managed to boot into the lineage os recovery by putting it on a flash drive and holding down the button then wiping /misc thru the serial console.
Click to expand...
Click to collapse
I'll look into this... Can you try flashing the newest build through lineage recovery and wipe data?
npjohnson said:
I'll look into this... Can you try flashing the newest build through lineage recovery and wipe data?
Click to expand...
Click to collapse
Is there any way to activate sideload mode through adb shell or the serial console? Again, since the button isn't working (still works in uboot so it isn't a hardware issue) with the new dtb I can't navigate through the recovery menu.
lmore377 said:
Is there any way to activate sideload mode through adb shell or the serial console? Again, since the button isn't working (still works in uboot so it isn't a hardware issue) with the new dtb I can't navigate through the recovery menu.
Click to expand...
Click to collapse
Adb reboot sideload works, maybe just reboot sideload?
I'll go grab an Onn box at Walmart tmrw afternoon.
I know it works as 3 of our developers have and use it.
Just a matter of install process it seems...