StreakDroid FroYo v1.5.3 - ReleaseThread - Streak 5 Android Development

This ROM is heavily updated and still being developed at a fairly rapid pace.
The update process is now very simple to do
PLEASE NOTE: THEIR ARE NOW 2 BUILDS BEING RELEASED FOR EACH UPDATE, ONE IS A NEWBASEBAND VERSION WHICH WILL WORK WITH ANY BASEBAND AFTER 1.2 OR ANY OFFICIAL DELL FROYO BASEBAND, THE OTHER IS A NO-BASEBAND UPDATE DESIGNED FOR REBELSIM USERS AND REQUIRES THE 2.1 8105 BASEBAND
The recommended Update requires you to upgrade your device baseband, this is a simple procedure via fastboot.
rebelsim users should use only the nobaseband update file and use the 2.1 baseband or they will encounter problems
We now have a nice new website blog for streakdroid - check it out and help me populate the wiki with faqs and get in the forums sites @ http://www.streakdroid.com
Most Recent Version: v1.5.3
Known Issues:
Accelerometer is dodgy at times but i cant pin down the issue - usually going into settings > display and toggling auto rotate on and off fixes
-----------------
Changelogs
-----------------
UPDATE 6/1/2011
Version 1.5.3 AKA Biscuit Madness
Added new Transparent statusbar and gingerbread style theme (based off quikt's transparent theme on xda)
Removed setcpu due to issues with it being preinstalled
Updated streakradio
Readded front camera support to cam app - fring support removed
Played with audio libs a little. probably wont fix anything
Added new bootanimation courtesy of darksmurf
Added BatteryWidget app to allow seeing battery percentage as its not easily possible on the gingerbread battery icon (add The widget to a desktop somewhere) - also allows quick access to some settings
UPDATE 2/1/2011
Version 1.5.2 AKA Insect Roadkill
Added Gingerbread Style battery Icon with Percentage(looks SOO much nicer than the stupid looking circle icon)
Changed some Colors in status bar
Updated Google Maps, Twitter, G-Mail, Launcher Pro, Miren Browser And Market to Latest versions according to my device.
Added Some more TCP/networking tweaks
Reduced the level of audio boost set in kernel, may help the volume issues.
Added Fixed Email.apk for exchange 2010 sp1 support
Fixed Twist Rotate & Two Finger altitude adjust in Google maps
Streak Light Pre-installed (untested)
SetCPU Preinstalled
Music App Replaced With version Suggested in this topic to fix the pause error.
MIUI Music app Added
Universal Androot removed, Rom is PRE-ROOTED
UPDATE 15/12/2010
Version 1.5.1 AKA Animadness
Fixed Wifi Tethering
Fixed Settings Force Closes
Reverted market as official update will be pushed to device soon
Kernel From perfmod added, (1.267ghz max oc)
New Fonts Courtesy Of Kang-O-Rama rom for nexus one
New Window Animations
GPS SHOULD be sorted - remember to update baseband
UPDATE 11/12/2010
Version 1.5.0 AKA FaceTime Edition
Fixed USB Tethering - works properly now
Fixed Notifications Settings
Reverted Camera Frameworks and app to 1.1.1 version to allow front cam in fring etc (works and tested in fring)
Added GingerBread Market
Added GingerBread KB
Added Miren Browser
Probably Loads Of Other Things I Have Forgotton
Reckon this is pretty much 100% stable now
UPDATE 25/11/2010
Version 1.4.6 AKA Swappable Goodness
Fixed USB Tethering
Reverted Market App due to force Closes
Removed Check for Rear Panel Placement(Device WILL run with no panel in place - also see Note 2)
Added Fards Data Tweaks(see Note 1 below)
Removed 128Mhz Clock speed due to reports of crashes
Reenabled 1.19 ghz clock
---------------------
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Please feel free to donate to my work if you find it useful - any amount is appreciated
GBP Donate | USD Donate
-------------------
Required Files
-------------------
Rom Download Links:
New BaseBand Version
Primary Download Site: http://downloads.streakdroid.com/djsteve/update-1.5.3.zip
Mirror 1: http://www.android-roms.com/downloads/upda...pdate-1.5.3.zip
Mirror 2: http://mirror2.streakdroid.com/update-1.5.3.zip
IT IS HIGHLY RECOMMENDED TO UPDATE TO THE BELOW BASEBAND FOR 1.5.1+
Baseband File Download:
Primary Download Site: http://downloads.streakdroid.com/djsteve/amss.mbn
Mirror 1: http://www.android-roms.com/downloads/updates/amss.mbn
Mirror 2: http://mirror2.streakdroid.com/amss.mbn
NOBASEBAND Version
Primary Download Site: http://downloads.streakdroid.com/djsteve/u...-1.5.3-nobb.zip
Mirror 1: http://www.android-roms.com/downloads/upda...-1.5.3-nobb.zip
Mirror 2: http://mirror2.streakdroid.com/update-1.5.3-nobb.zip
VPN USERS: TUN.KO for you is below.
http://build.streakdroid.com/tun.ko
if you have NOT already flashed the dell 2.2 pkg or my 720p fix you need this to fix 720p video - otherwise ignore
http://downloads.streakdroid.com/testing/dsp1.mbn
flash this using the fastboot command fastboot -i 0x413c flash dsp1 dsp1.mbn
-------------------
Other Requirements
-------------------
Some Common Sense
Pinch of Good Luck
Patience
Ability to read and follow instructions
Fastboot Setup and Working
ClockworkMod Recovery Flashed and working
-------------------
Level Of Difficulty
-------------------
8/10 - Easy level, should be simple enough for 99% of users to complete
-------------------
How-To
-------------
1. Copy the update zip to your memory card first
Steps 2-4 are only needed if you are coming from a build OLDER than 1.2
2. Power down your streak and boot into fastboot
do this by pressing power until the keypad lights come on then HOLD camera until you get to a white screen, then tap on the fastboot text in top right corner,
3. Connect your streak to pc - the text on streak should change to FASTBOOT_MODE.
you should place the amss.mbn file into the same folder as fastboot on your pc
run the following commands from command prompt on your pc
Windows:
Code:
fastboot -i 0x413c flash amss amss.mbn
Linux
Code:
fastboot flash amss amss.mbn
4. Type the following commands to reboot your streak - again alow it to boot into the main ui - you will lose network connection for the moment, this is fine, also streak WILL reboot twice before booting, again this is normal
Windows:
Code:
fastboot -i 0x413c reboot
Linux
Code:
fastboot reboot
5. Once your device has booted shut down again and boot into clockwork recovery by doing the following
boot to recovery as per step 1 then choose option 2.
6. Flash the 1.5 update zip
7. reboot
Thanks to:
Everyone for suggesting things they want adding
android-roms for the mirror
Vinokirk for helping diagnose and sort out 2.1 baseband ril support and gps
Andycap & fards for providing modified Gps.conf
homeiss forthe excellent upgrade/downgrade guide
everyone else for just jumping in and helping each other, thats the true community sprit that makes me do this sort of dev for android and not some other mobile os.
everyone else who helped/is helping
hopefully thats everything
any issues theirs me and a few of my tech head irc helpers keeping an eye on the posts. or just jump in the irc channel #dellstreak on freenode for help.
also please feel free to donate to my work if you find it useful - any amount is appreciated
GBP Donate | USD Donate

Congrats Steve! This guy has put a *lot* of hours into getting this working for us. Give a small gift or donation if you like the ROM.

Im on Uk bought Dell unlocked currently with 6941 2.1 rom
will this work on my streak?
thanks

well im on a uk o2 streak and it works fine here

so it should work on any streak?

well we have tested it on a few streaks now and its worked fine,

ok cheers will give it a bash......................ps where do u live if it fubars and i need a refund on my fone?

Nice work Steve much appreciated you have worked hard on this project i will give it a sticky

lufc said:
Nice work Steve much appreciated you have worked hard on this project i will give it a sticky
Click to expand...
Click to collapse
cheers buddy

how do you install the driver on windows 7 x64? i tried going into the devices panel and updating the driver to the stuff in the folder, but none of them would work. any suggestions?
sorry, i think i need to be a little more clear. i read through the pdf, but the info is mostly for xp and doesn't apply to 7 at all. when i'm done adding the unknown device to device manager as android composite device, i don't get com ports like they do, so i cant flash it at all. any thoughts?

i would highly suggest people use windows xp or 7 32bit for flash as 64bit is a pain, win xp mode is avail for 7

Worked great on my US streak with 8105 rom.
For people having problems with Win 7, try running QDLtool.exe as administrator and also try different USB port.

I assume that flashing back the baseband to the stock version is not possible, right? If so, will the Android 1.6 stock FW work with that new baseband? In other words: Is it or is it not possible to go back to the stock FW (just in case) after performing this 2.2 update?

does tha front facing camera working in this build?

how would I do this using Ubuntu 10.4
how would I do this using Ubuntu 10.4, dell streak I also have already "bricked" 1 streak. well kinda, it won't go pass the dell logo, but I can get to fastboot. Really feel like I own a Lamborghini but can only drive it 15mph.

lrevell8 said:
how would I do this using Ubuntu 10.4, dell streak I also have already "bricked" 1 streak. well kinda, it won't go pass the dell logo, but I can get to fastboot. Really feel like I own a Lamborghini but can only drive it 15mph.
Click to expand...
Click to collapse
that streakflash only works in windows. so you will need to get a machine with xp or run a live distro. the rest of the rom is flashed through fastboot so you can recover it.

hey steve glad to see you managed to get froyo on it, iv donated a small amount but hey every little goes a long way huh? just wanted to ask, now that you have succeeded with this, does it open the doors for more custom froyo roms? like i would really like to see a htc skinned froyo with the 30fps cap removed, im not asking you to do it (before i get flamed), m just asking is it now possible?

lol im working on cyanogenmod
oh i forgot to mention folks THIS BUILD IS FPS UNLOCKED !!!!!!!!

DJ_Steve said:
lol im working on cyanogenmod
oh i forgot to mention folks THIS BUILD IS FPS UNLOCKED !!!!!!!!
Click to expand...
Click to collapse
God bless you stevy
I shall wait for once its done but fantastic work.
/manlove

Wow great work!!!
Sorry about this question but what do I have to do with the boot system and userdata images to flash it with fastboot?
Sorry had only wm devices before

Related

[Q] Android bootloader interface - cant start

THIS IS ALL SORTED...DESPITE HAVING A STOPPED ANDROID BOOTLOADER DEVICE...I DISCOVERED THAT I HAD TO USE THE CORRECT FASTBOOT COMMAND AND NOT THE ONE SHOWN....IE I HAD TO USE fastboot -i 0x413c flash recovery recovery.img
SO I JUST HAD THE ANDROID COMPOSITE ADB INTERFACE RUNNING AND BY USING THE 0X413C IN THE COMMAND IT WORKED...
hope somebody can stop me pulling my hair out!
Ive just taken posession of a Dell Streak. Came with the 1.6 android.
Have successfully done the OTA upgrade to Froyo 2.2. NICE
Successfully rooted using SuperOneClick 1.7 rageagainst the cage and allow nonmarket apps.
Want to put clockwork mod on..so can make full backups and perhaps try a rom or two!!
Have downloaded the latest dell drivers (R291096) and Sync Suite(R290209)...
Android Phone - ADB Inteface drivers all good
But i cant for the life of me get the Android Bootloader Interface going so I can use Fastboot commands.
Have tried XP 32bit and & Windows 7 64Bit with same result...have read lots n lots...but whatever i do i cannot get the Android Bootloader Interface to start....advice please my dear experts..
Baseband GAUWB 1A131921-EU
Kernel 2.6.32.9-perf
Build 12792
Thanks in advance...please dont shout out me ive read stuff all over the place and think this is to do with the official 2.2 =OTA upgrade problem...
Dell keepin me out of fastboot and messing with clockwork etc !!
hi there just been having the same problem for the last 2 days i was told that clock work mod wont work with dell streak ?????? look @ this line http://forum.xda-developers.com/showthread.php?t=840326
to boot in fast mode hold the camera button in and press the power button in @ the same time then tap fast boot mode also i have attached a file witch help me also here is a link what helped me 2 n8 when i bricked it in some way lol
http://streakdroid.com/?page_id=78
thanks for that info...i have just started reading through the streakdroid forums and QDL Tool (with drivers) sections...been at it a few hours...am really tired now...time for a rest before i do BRICK it lol......tried some other dell driver but no joy....usually always stick to my flashing in windows XP..for 32 bit and USB compatability but this is driving me nuts....thanks again....ive read read read and reread the pdf file.....
No worries i know what its like i was up till 2a, yesterday trying to do the same and 2 n8 got things working put a file on and it sort of bricked it and i have just sorted it out 20 mins ago
You have XP 64 bit? Isn't that a bit like a mythological beast OS that only exists in fairy tails and Redmond?
Hope you got this sorted out.
sorry should have read windows 7 64bit..only use xp in 32bit mode...all updates installed.
just trying again now...have uninstalled everything dell / drivers...used USBdeview to uninstall already set Android ports and old Qualcom ports from where i flashed my 3 usb stick, and the 3 drivers and software....downloading, again, the android 2.2 drivers and pc suite from dell.....will try again....i see 2.1 users and 1.6 users seem to have fastboot drivers working and clockwork mod....so will start playing all over again ..... at least the night is young!!!
oh bugger this im tired of going over things..guess the 319 version wont let you have proper drivers to "mess" around with the bootloader..ill revisit some time in the future
oh great decided to start again using a factory reset.....now all i get is process com.android.setupwizard has stopped unexepectedly. please try again..
cant get anything but a blank screen cos the setupwizard did not complete..
groan...
UPDATE 1345GMT.....downloaded Streak_319_12792_21.pkg .... renamed to update.pkg.....copied to root of sd card....booted into recovery and selected update from package.....am now back at 2.2 update and screen working...phew....now to spend rest of day setting it up again lol...wonder why doing a factory reset wont clear the caches?
I'm assuming you have sdk setup? If not give this a go great write up.
http://www.addictivetips.com/mobile/what-is-adb-and-how-to-install-it-android/
Sent from Re-Engineered dInc
no not used the sdk files...just the official update which is downloadable....no probs..
Also..update....i have managed to follow the instructions and install StreakMod even though my Android Bootloader device is still not started..Different commands there than what i was using to try n put CWM on.....ill see how that goes...at least im making progress and have saved the Official 319 update package in case i need it another day!! thanks for comments and help on this irritating buisiness...
ALL SORTED NOW..APPARENTLY TO USE FASTBOOT YOU MUST INCLUDE THE DEVICE CODE SO THAT FASTBOOT KNOWS WHAT IT IS TALKING TO!
IE THE FULL PROPER COMMAND LINE IS fastboot -i 0x413c flash recovery recovery.img
CONSIDER THREAD CLOSED..THANKS TO ALL

A13 Boxchip CM9/CM10 Development

I now know the Allwinner A13 is a stripped down version of the Allwinner A10, to be clearer the specifications of my Tablet (from UniFlash and AnTuTu Benchmark) are as follows:
Manufacturer: None
Brand: softwinners
CPU hardware: sun5i
CPU model: ARMv7 Processor (VFPv3, NEON)
CPU frequency: 60.0 ~ 1008.0 MHz
Screen resolution: 800 x 444
GPU vendor: Mali-400 MP
GPU version (OpenGL): OpenGL ES 2.0
RAM size: 512 MB DDR2 RAM
Knowing this, I used UniFlash to make a backup of the firmware bt after using UniFlash to try and load a CM9 Rom on to the Tablet, the Tablet died. After alot of googling I discovered AllWinner based chipsets use Live Suite (sometimes called LiveSuit) to flash firmwares on to the device.
To Flash firmware on to the device you need to follow the attached instructions ((http://dragondevs.com/viewtopic.php?f=159&t=390):
Download LiveSuite (http://www.softpedia.com/get/System/System-Miscellaneous/Live-Suit-Pack.shtml)
Install Live Suite
Start Live Suite
Select the Live Suite image file (folder icon
Turn device off (to be sure hold power button for 12 - 20 seconds)
Hold "Volume Up" button down
Connect the device to your PC (while still holding "Volume Up" down)
Start pressing the power button (you may need to do this once a second for 5/6 seconds)
If you haven't installed windows will ask to install a driver for a device (Dive Id will be something like Vf73465789123465435_Id, if the device is in the right mode, A13-MID, ADB-Interface indicates the tablet has connected in anouther mode).
Once this has finished LiveSuite will detect the device and a wizard will flash the firmware for you.
I have found a working firmware which according to AnTuTU Benchmark gives my tablet a rating of 3047 (see firmware section), this is on the higher end of reported A13-MID tablets
I have found out how to install CWM on to the device via SaussageMod (http://www.slatedroid.com/topic/29916-scriptmod-for-allwinner-a1x-platforms/). This solution is untested, further more it may be unnessary futher investigation has shown this website (https://www.miniand.com/forums/forums/2/topics/73) has developed a way of create Live Suite images. This is simplier than installing clockworkmod recovery,
I tried to load the following images on to my tablet and failed completely: http://forum.xda-developers.com/showthread.php?p=31043317 It didn't work and forced me to do a firmware refresh.
My other step for the day was to create Ubuntu 10.10 installation then I began following this guide to construct an Xperia Play CM9 Rom/Kernel. once I have created a working ROM (I own an Xperia Play). I'm hoping to be able to modify the kernel to include the relevent A13 drivers, but one step at a time.
TODO
Create Ubuntu Partition
Follow Xperia Play CM9 Rom/Kernel Guide and create working rom (test on my Xperia Play)
Download CT repository (https://github.com/christiantroy) and compare with Xperia Play CM9 rom
Find the relevent drivers from https://github.com/amery/linux-allwinner leaked source
Retrieve offical MALI 400 MP drivers (parts of it have been released) compare with leaked source
Use UniFlash backup of original Rom along with LiveSuite image creation to try and restore original firmware (see If I understand it properly)
Examine Build.prop find out why original firmware displayed ina phone layout and new one is in tablet mode (potentially reference CM supported Tablets).
Attempt to compile a A13 (Sun5i) based rom
Create a google code page to hold all of these thoughts properly.
Left blank will include rom/firmwares here for future reference
Firmware
https://www.dropbox.com/sh/bzjt7mzuftwz79f/nt7mRMPDj1 - My public Dropbox
http://www.azhuo.net/en/products_A13B_Allwinner-A13_7_inch_Android_4.0_Upgrade.html - password is: tabletpc
http://dragondevs.com/viewtopic.php?f=159&t=390 - McPad F1 firmware
Novo 7 Tools
https://dl.dropbox.com/u/74970692/Novotools_v1.0.apk
SausageMod
http://www.slatedroid.com/topic/29916-scriptmod-for-allwinner-a1x-platforms
Gapps - http://goo.im/gapps/
I have the same tablet and it would be very cool if you succeeded in your attempt to create a CM9 rom for it. I tried ROM made by Tragidy from this thread but there is a problem with touchscreen driver, ROM booted successfully but I could not even unlock the screen cause touchscreen did not work. I finaly flashed rom DCPAD2121.zip using livesuite which I belive is the original ROM that came with tablet and it worked.
I installed clockwordmod using sausagemod successfully, but there is a big problem - no hardware "back" key and only volume up works.
novo7tools.apk works OK for reboot, reboot to recovery or shutdown.
syncing
Thanks, it's slow going at the moment, I only spending ~1 hour each day on it and at the moment trying to sync the CM9 source is painful (it keeps timing out, due to "remote side corruption").
I figure I would start there as all the firmware images I can find are ICS roms (meaning the drivers must be ICS).
Hi, I have the same tablet but I cannot find the firwmare DCPAD2121.zip
Could you upload it please? From dropbox has been deleted
Thanks
You should check this topic:
http://forum.xda-developers.com/showthread.php?t=1861445
WillingMagic said:
You should check this topic:
http://forum.xda-developers.com/showthread.php?t=1861445
Click to expand...
Click to collapse
I tried that ROM, on my tablet after flashing the ROM it got stuck in a boot loop. It might be an idea to steal the config he created. The ROM is pre CM9 release. The A10 Flash kitchen software seems to work. I was hoping on producing a complete Live Suit image that people could flash (figuring our what CT has done on the A10 took a while).
Still having fun trying to sync the repositories, given up on trying to use a Debian VM, I'll will install full Ubuntu on a drive tomorrow, hopefully that will help fix things. It doesn't help most of the guides I can find are out of date and I keep having to make corrections.
I've also uploading all firmware I can find to my dropbox (at 200mb each they will take a while), I won't with tools simply because others ask you not too.
The Dropbox firmware was out of date when I tried to download it sun5i_android_a13-pfdq88_en_D06 firmware worked well for me, the firmwares are located at: https://www.dropbox.com/sh/bzjt7mzuftwz79f/nt7mRMPDj1
Cyanogenmod 9 in not working for you. Did you made data and cache wipe? Can you send me logcat and dmesg output?
You can`t steal my config, you have to remember about credits, and other stuff.
Creating a wiki is useless, there is already wiki for allwinner products, so better update info on it.
Github is better than google code to keep sources.
Using Livesuit=Windows, I hate dual booting just for flashing, Clockwork Recovery or modified SDcard with uboot is better solution.
Current kernel is not working well, with sun5i.
Using VM is stupid, because building rom takes a lot of time on quad core pc without it.
WillingMagic said:
Cyanogenmod 9 in not working for you. Did you made data and cache wipe? Can you send me logcat and dmesg output?
You can`t steal my config, you have to remember about credits, and other stuff.
Creating a wiki is useless, there is already wiki for allwinner products, so better update info on it.
Github is better than google code to keep sources.
Using Livesuit=Windows, I hate dual booting just for flashing, Clockwork Recovery or modified SDcard with uboot is better solution.
Current kernel is not working well, with sun5i.
Using VM is stupid, because building rom takes a lot of time on quad core pc without it.
Click to expand...
Click to collapse
I wiped the caches I couldn't send a logcat or dmesg as the device simply boot looped.
I've been providing links to threads whenever I come across others work, I'm new to android rom development for me this is a research effort which will hopefully produce something cool for my £50 tablet. Basically my day job has switched to developing UI's and I am looking for something new to learn (instead of why is Vaadin, Guice, SWT, Javascript, etc... is putting that button there).
Said dev career has also made me hate Git with a passion (not as bad as perforce but still) since Git integrates poorly with Visual Studio and Eclipse and you end up getting everyone overwriting each others changes. The idea of google code is simply because it makes a good platform for projects and you can use things like git with it. I didn't know about an Allwinner wiki, with all of my Googling I haven't come across it, where is it?
I don't care about build times I'm just researching, alas Debian has caused me enough problems so I've installed ubuntu on to a old disk I had lying around. Considering I've just tried to install Ubuntu via a Net install CD and it has screwed up the GRUB installation (nicely taking out my windows partition as well) can you blame me?
The reason for nabbing the config (and the Xperia Play and Christian Troys) is to understand how they work. Over the years I've found most Open Source software documentation is poor unless you have a set level of knowledge about it already.
Lastly I like automation, I want things to just work. Livesuit does that since I am normally a windows user, I as hoping in the distant future once I understand the build process to set up a Jenkins server to do it and create the whole lot automatically (via the Allwinner flash kitchen). In the even longer term I would like to update FlashTool to do what LiveSuit does. In the near term (next couple of months) I just want to be able to build a CM9 image.
All android and kernel source are keep on git, so changing it is stupid.
This is allwinner wiki: http://rhombus-tech.net/allwinner_a10 you can also update http://elinux.org/Hack_A10_devices
Everyone use CWM and it's standard for unofficial firmware/ROMS
brandonlee2 said:
Hi, I have the same tablet but I cannot find the firwmare DCPAD2121.zip
Could you upload it please? From dropbox has been deleted
Thanks
Click to expand...
Click to collapse
Here's my upload, I packed it in rar format: http://www.mediafire.com/?we4zhgop29bg3dj
I also found it here: https://docs.google.com/open?id=0BzQuMwoMQqvba1VtQ1p1ZWJkR2M
from this forum post: http://www.slatedroid.com/topic/35314-a13-generic-tablet/page__view__findpost__p__421128
I built a CM10 rom for A13 from sources. It boots fine but hangs either at the Android setup wizard or sometimes even at the CM animation.
myfluxi said:
I built a CM10 rom for A13 from sources. It boots fine but hangs either at the Android setup wizard or sometimes even at the CM animation.
Click to expand...
Click to collapse
Mind sharing your repo ?
Trying 4.1.2
Hi all,
So I've tried compiling from 4.1.2 source for my A13 Emgeton Consul 3
It boots up and gets to the CM10 boot animation but it doesn't get past it.
I can adb at first boot until adb stops.
logcat from boot attempt:
http://pastebin.com/gLTrieHm
My build.prop:
http://pastebin.com/Ap9M1tjW
Any pointers as to why it doesn't get past the boot animation?
Hello guys! I know it's not he proper place here to pose my question, but I am definitely at loss!
Do you happen to know if there is a way of rooting this tablet? And if so, does everything work properly after that?
phoivos86 said:
Hello guys! I know it's not he proper place here to pose my question, but I am definitely at loss!
Do you happen to know if there is a way of rooting this tablet? And if so, does everything work properly after that?
Click to expand...
Click to collapse
Mine came pre-rooted.
Just received my MID A13 Tablet. Is this thread dead?
koodiifin said:
Just received my MID A13 Tablet. Is this thread dead?
Click to expand...
Click to collapse
I've gone a bit quiet on the development front, setting up a file/media server & samba domain server to power my home network is eating up my time.
My dropbox contains every image I could find for the tablet, as mentioned previously you can root the device using saussage mod, although my device and every one of those images is already rooted. You can prove this by installing super user.
Sassage mod's clockworkmod recovery doesn't work for me and I was looking at the backup tool in order to generate my own one. If you are aimed at any development, let me know and I will update the main thread
Many have said that they have "lost" "forget" to take backup from original rom. So, i'd like to have backup from my original to go back if/when something goes wrong. How do i do that? What software i need. Do i need to root?
This is from my info sheet:
Model TWD_MID
android version 6.0.1 ?????
Baseband 1.5
Kernel 3.0.8+
Buildnumber: nuclear_evb-eng6.0.1 IMM76D 20120917 test keys
I am in a desperate need for some help:
My tablets specs are these:
Phone model: A13-MID
Brand: softwinners
CPU hardware: sun5i
CPU model: ARMv7 Processor (VFPv3.NEON)
CPU frequency: 60.0 - 1008.0 MHz
Screen Resolution: 800 x 444
GPU vendor: ARM
GPU render: Mali-400 MP
GPU version (OpenGL): OpenGL ES 2.0
Memory size: 353.5 MB
Android version: 4.0.4
Build number: nuclear_pfdq88c-eng 4.0.4 IMM76D 20120821 test-keys
Kernel: Linux version 3.0.8+
I just installed OpenVPN installer and installed the OpenVPN binary in the system/xbin
After that I tried to connect to my university's VPN but when it tried to connect, the tablet lost wifi connection and ever since it doesnt connect to any available wifi network!! I manually deleted the OpenVPN binary, but problem remains!
Do you know where could I find the stock ROM for this tablet in order to re-flash it?
Do you have any other proposals? Anything will help!
Thank you very much!!

[ROM][KK][4.4.2][STOCK]Omate TrueSmart IRONMAN Firmware

KitKat for the Omate TrueSmart
Congratulations, you made it this far and managed to keep your unit alive long enough to upgrade it to the next level!
4.4.2 Changelog:
================
Fixed glitch in boot animation to make it smoother
BTLE profile and PAN profiles added
Full Settings Menu
Functional Accessibility Menu
Updated Wi-Fi Drivers, now supports ip6, ip4, and low-power mode
Updated GPS Drivers, lock-on after initial lock and AGPS update should be quicker
Kernel updated from 3.4.5 to 3.4.67, supports SELinux
Unlocked bootloader and insecure kernel allows for root access through SU
Google Play Services included
Google Talkback/Voice Search integrated
Fixed glitch where Voice Search would not complete spoken sentences
TWRP updated to 2.8.3.0 with full features and MTP support
Camera now operates at 5MP/720P without force closing
Security holes have been closed
MALI 400 drivers updated
Battery management integrated; after first boot battery readings should be accurate
Sound issues fixed; microphone should no longer sound muffled
Soft reset implemented, holding both buttons for 10-15 seconds should power down or reset unit
ART mode implemented, allowing for faster and more efficient performance
Known Issues:
=============
Sensors are non-functional until updated drivers are available (if they become available)
Settings is not accessible from status bar icon
1900MHz units are unable to access 3G data currently (if a modem becomes available this should change)
Bluetooth connectivity may occasionally drop out depending on data load
APNs are not automatically added
IMEI may be lost or corrupted after installation
Instructions:
=============
REQUIRED PROGRAMS:
1) SP FLASH TOOL
2) MTK DROID TOOL
3) WINDOWS OS XP or HIGHER
The All Tools suite for MTK devices can be found here:
MTK All Tools Suite
****** You must install the preloader drivers for your device using the 32-bit or 64-bit installer (dpinst) for your operating system before you continue. ******
I suggest making a full backup of your device either in TWRP or in MTK DROID TOOLS (1:1) to preserve valuable data or in case of a failed upgrade. You should always back up your IMEI/NVRAM in DROID TOOLS for safe-keeping and this is no different.
Download the full set of factory images here:
Omate 4.4.2 Factory Image RAR
Extract the contents of the ZIP file to a known directory and proceed to the next step.
Next, navigate to the Settings menu on your Omate TrueSmart and, under Accessibility, disable Quick Boot. This is the only way to enter Download mode reliably. With that completed, power down your watch.
Finally, open the scatter file (mt6572_scatter_emmc.txt) found in the directory you extracted the ZIP file to in SP FLASH TOOL and check to make sure each file is present. You may need to manually add the system.img and recovery.img. To do this, double click on the empty box and select the file.
Once you've made sure each file matches, go to the drop-down menu where it says "Download" and select "Firmware Upgrade". Take one last look to make sure every file is selected and press the Download button on the top left of the screen.
With the watch powered off, go ahead and plug it in. THEN WAIT. It will take between 5-10 minutes to fully upgrade your unit. You should see a red bar, then green, then purple, then yellow. If you get any error that says "BROM DLL ERROR" note down the error number and send me a message. If it gives you a green checkbox, you're done with this step.
Now you're ready to boot the watch. Press and hold the power button until it powers on. The first boot will take approximately 5 minutes to complete while it assembles all of the information. Once it finishes, power down the watch. Hold the home (bottom) button and press and hold the power (top) button simultaneously (at the same time). You'll see a recovery menu. Press the power button to boot into TWRP. From there, select "Wipe" followed by "Factory Reset". You will want to reset the watch to factory settings. You can either make a backup or go ahead and reboot the system.
Congratulations! You should now be on Android 4.4.2 for your Omate TrueSmart.
NOTES
=====
If you're missing APN information I suggest you either restore previously saved APNs or add them manually if they disappear. Currently 3G data will not work on 1900MHz units.
This firmware was designed for UMEOX smart watches operating on the x201-series MT6572 chipset. I am not responsible if you damage your watch because you flashed the firmware incorrectly or to the incorrect watch.
If you have any questions as to whether your watch is compatible, please message me.
It is IMPOSSIBLE to brick your watch if you are flashing this firmware. If for some reason you think your watch is bricked or you feel uncomfortable flashing this firmware you are welcome to send your unit to me (if you pay shipping) or I am available to help over Chrome Remote Desktop to flash it for you.
If you are having issues getting the firmware to work, please send the following information to me:
Watch Manufacturer
Date Received
Last Known Firmware
Case Material
And I will answer on a case-by-case basis to help you troubleshoot. I never make guarantees but I promise to help as much as I am able.
Finally, please take the time to thank the brave soul who voided his warranty to get me the prototype firmware for this. I won't reveal his name for security's sake, but he obtained a developer unit from another company who uses the x201 chipset and was kind enough to upload the system dump in September of last year. I would have presented this sooner to you guys, but until the method for flashing the S8 firmware was released I had no idea why I couldn't get it to work.
SPECIAL THANKS
==============
Laurent LePen, for giving me the tools from UNOVA to make this possible
@Dees_Troy, for having the patience to flash the firmware, assemble a system image, and update TWRP
Derek Serianni, for flashing his watch 42 times to test the firmware
Christos Vorkas, for testing SIM functions and the early firmware
@AdamOutler, for advice operating Linux and troubleshooting errors
The Anonymous Firmware donor, who voided his warranty and bravely e-mailed me about 1.5GB worth of files
XDA, for always having that clinch moment where someone has a breakthrough that helps the rest of us
KNOWN COMPATIBLE UNITS:
IconBit:
Callisto 100, 300
SimValley:
Pearl AW414, AW420/1
UMEOX
X201
Omate
TS-1/TrueSmart 512MB/4GB Edition
TS-1/1900MHz 1GB/8GB Extreme Edition
TS-1/2100MHz 1GB/8GB Extreme Edition
For Root, download Chainfire's latest SuperSU package and flash in TWRP:
SuperSU 2.44
Derek Serianni, for flashing his watch 42 times to test the firmware
Click to expand...
Click to collapse
I think that number is a lot higher actually..... but, 42 is quite fitting as this is now the answer to the ultimate question...
It has been an exciting couple of days testing and flashing.
Despite all the trial and errors, not once did the watch become unrecoverable.
If you load Google Now Launcher and the latest Google Search APK (and setting it up properly) you can use the "Ok Google" feature from the lock menu as well as in the OS.
I stopped wearing my LG G and am now wearing the TS daily....
Kudos for all the hard work!
I knew there was light at the end of the tunnel!
D.
Great job!
hi dan,
i have tried to flash this to my EU 1/8G Pre May Omate TS.
Watch Manufacturer - Omate
Date Received - Pre May
Last Known Firmware - EU Ensec Stock 0706
Case Material - Steel
A few questions:
1) the downloaded KK Omate rar file does not include UBOOT.BIN or a BOOT.IMG file. Am I supposed to leave it blank or use the UBOOT / BOOT IMG from my current Omate's backup?
EDIT: I have tried using the UBOOT.bin and BOOT.IMG from another KK thread but still run into the same "CheckSum Failed" error i mentioned below: http://forum.xda-developers.com/showpost.php?p=57433563&postcount=189.
2) under FLash Tool: the ANDROID file is usually blank - i have selected system.img from the rar file for the file to be flashed for this. Is this correct?
3) When flashing via FlashTool, about 27 seconds into the flash (i see a RED Bar, then it changes to a couple of BLUE "Read Back" bars), I keeping getting a error saying "CheckSum Failed". I have tried redownloading the KK Omate rar file and trying again but to no avail.
EDIT: I have tried with different ports, different cables, including cleaning the Omate TS's ports with no luck. Just prior to the flash, i was able to do a full backup so it does seem strange and does not seem specific to the cables/ports/contacts on the TS.
UPDATE: Seems to be working - TRY Flash Tool v3.1332 instead of the latest V5.1352. It is now flashing fine as mentioned by Dan.
FINAL: My TS boots up fine with KK now! If you face the checksum error as i did, try using SP Flash Tool v3.1332 instead! - LINK HERE: http://androidxda.com/smart-phone-flash-tool
Any advice on the above?
NO UBOOT
Trying to flash this on my Omate 2100 unit but the UBOOT is missing for me? Got the system.img and recovery.img added but no uboot.
I am also not sure what to select as "BOOTIMG".
Watch Manufacturer - Omate
Date Received - Pre May
Last Known Firmware -ZGPAX S8
Case Material - Steel
I have made it.
But Attention:
No baseband is included.
Baseband for EU, 2100 is not included in this ROM.
So you can not use the phone to call.
I am back to ZGPAX S8.
Watch Manufacturer - Omate
Date Received - Pre May
Last Known Firmware - RSR 0.8
Case Material - Steel
Same as aeron16 with the KK Omate rar file not including UBOOT.IMG or a BOOT.IMG and using system.img for the ANDROID file.
I've tried via Win7 & Win 8.1, Win7 didn't install the preload drivers but Win8 did..
..could anyone that has sucessfully installed it create a flashable image we could use directly in TWRP?
Caboose1979 said:
Watch Manufacturer - Omate
Date Received - Pre May
Last Known Firmware - RSR 0.8
Case Material - Steel
Same as aeron16 with the KK Omate rar file not including UBOOT.IMG or a BOOT.IMG and using system.img for the ANDROID file.
I've tried via Win7 & Win 8.1, Win7 didn't install the preload drivers but Win8 did..
..could anyone that has sucessfully installed it create a flashable image we could use directly in TWRP?
Click to expand...
Click to collapse
Mike? hehe did you get the same error i had? with the CheckSum failed as well?
Isn't the baseband included under "0 Needed files -> NA/World Baseband"?
I can not check if valid files. My TS is not booting/reacting to Flash tool anymore...
Not sure if I did it correctly but because I could not find the boot.img within the supplied files I took the boot.img from the other kitkat rom here on xda. Have at least a working TS now .
Only problem right now is that the home button is not functioning as the home button. It sets the volume to max.
seppen said:
Watch Manufacturer - Omate
Date Received - Pre May
Last Known Firmware -ZGPAX S8
Case Material - Steel
I have made it.
But Attention:
No baseband is included.
Baseband for EU, 2100 is not included in this ROM.
So you can not use the phone to call.
I am back to ZGPAX S8.
Click to expand...
Click to collapse
I had the same issue as well!
Thanks. Works well like the other early ROMs and is a bit better prepared including Google Play etc. Can we remove the extra apps like QQ etc from the image for a future release? Edit that might have been my fault from not wiping after flashing although I was pretty sure I had already removed them from the ROM whilst creating a flashable zip.
When turning on Wifi I do get an NVRAM error initially in the list of Wifi items. It fairly quickly finds real ones and it connects fine to my AP.
I have the issue with the second button turning up the volume too. There is a fix in the other thread for this.
Also I had to manually select system.img, the recovery, uboot.img and boot.img (the latter two weren't in the archive so I took from the X202 image in the original KK thread).
Glad to see Omate somewhat taking credit on Facebook. It seems I'm banned on Facebook from recently posting after commenting that they probably shouldn't be taking credit for this. The initial announcement a few days back has 14 missing/hidden comments. Oh so childish LLP - I'm sure you're reading.
I'd like the sensors if possible, mainly for a shake/rotate to wake up function..
---------- Post added at 11:43 PM ---------- Previous post was at 11:38 PM ----------
Caboose1979 said:
could anyone that has sucessfully installed it create a flashable image we could use directly in TWRP?
Click to expand...
Click to collapse
I'm going to take a look at doing this when I get a chance in the next couple of days. I had a basic one working with just system and boot images of the KK ROMs. It should be possible but I'm kinda new to this so not sure if there are any limitations when flashing everything like this. I do need to make sure I know all of the device names to flash.
Hi Guys,
Not sure where I am going wrong, can't make head nor tails so far.
Truesmart doesn't look to be detected in SPFlash, is SPflash what is meant about mtktools? i can find an application in that folder..
On from that i am also missing the .img files that the others are.
sorry to be a hassle, i will do my best to work it out, but just need a bit of help getting off in the right direction please,
also i haven't done any other flashing etc with my truesmart, is there anything i should be doing prior for brick protection?
it is a 2100mhz model
Cheers
burlyoaf said:
Truesmart doesn't look to be detected in SPFlash, is SPflash what is meant about mtktools? i can find an application in that folder..
Click to expand...
Click to collapse
MTKDroidTools is different to SP Flash Tool. They are 1 and 2 respectively in the All Tools folder.
Follow the instructions exactly particularly the order. Turn the watch completely off (disable Quick boot), click download and *then* plug the cable in.
Quick Update:
My EU 1/8G Omate TS-1 Pre-May is up and running fine (see my earlier post for some tips / advice based on the issues i had).
1 major issue as below:
However, under Baseband - it shows unknown, and similarly in IMEI - it also shows unknown.
i tried to flash the old 2100 World Baseband.zip in TWRP, but no luck,
tried to use MKT Tools to restore my NVRAM but no luck either (just shows install\data\nvram) and then nada.
minor issue: home button is defaulting to UP Volume instead of HOME function. I will try to flash the FIX_HOME.zip in the other thread and report back.
any advice Dan or anyone else who has theirs working?
If it says uboot, that's the lk.bin.
seppen said:
Watch Manufacturer - Omate
Date Received - Pre May
Last Known Firmware -ZGPAX S8
Case Material - Steel
I have made it.
But Attention:
No baseband is included.
Baseband for EU, 2100 is not included in this ROM.
So you can not use the phone to call.
I am back to ZGPAX S8.
Click to expand...
Click to collapse
Stop with the attentions. The baseband is included. I've had at least 5 people flash it with no issues.
IF you are missing a baseband, sit tight. Try flashing the UNOVA system image, then flash this again.
IF you are having checksum issues, either use an older version of flash tool OR format and flash the stock firmware.
The LK and Kernel must have been a goof on my part. I'll fix that.

[Q] Ubuntu Phone on Nexus 4 not updating

Hello. My phone will not receive automatic build updates, still on 4.4.2 as opposed to the current 5.0.1 version .
adb will not find my phone when it's plugged in either. Thus why I am creating this post. Any help is appreciated.
Ubuntu is still using code from 4.4 for accessing the phone's hardware and the developers have said that they won't switch too soon due to the amount of bugs in 5.0.
Normal system updates should work fine though. Which channel are you on?
Sent from my awesome Ubuntu Touch device using the Forum Browser app
nikwen said:
Ubuntu is still using code from 4.4 for accessing the phone's hardware and the developers have said that they won't switch too soon due to the amount of bugs in 5.0.
Normal system updates should work fine though. Which channel are you on?
Sent from my awesome Ubuntu Touch device using the Forum Browser app
Click to expand...
Click to collapse
Oh OK. Perhaps my phone was up to date. I was on the devel channel I think. I just reflashed to stable and forgot how to do it, it's quite easy for any future readers:
1. Turn off phone, then press [+ -] volume buttons and power button at same time, you will see android with belly open.
2. Install Android SDK studio on Ubuntu
3. Run this code from Ubuntu with the phone usb plugged in:
ubuntu-device-flash touch --channel=ubuntu-touch/stable--bootstrap
4. Don't touch a thing, including the blck & wht question screen; it will boot itself into ubuntu
Note: This also fixed the issue of my phone not ringing or making any noise when receiving calls and texts
Xinthose said:
Oh OK. Perhaps my phone was up to date. I was on the devel channel I think. I just reflashed to stable and forgot how to do it, it's quite easy for any future readers:
1. Turn off phone, then press [+ -] volume buttons and power button at same time, you will see android with belly open.
2. Install Android SDK studio on Ubuntu
3. Run this code from Ubuntu with the phone usb plugged in:
ubuntu-device-flash touch --channel=ubuntu-touch/stable--bootstrap
4. Don't touch a thing, including the blck & wht question screen; it will boot itself into ubuntu
Note: This also fixed the issue of my phone not ringing or making any noise when receiving calls and texts
Click to expand...
Click to collapse
Yes, the builds from the devel channel are about 3 months old, if not more. I wouldn't recommend to use them.
Instead, it's best to go with stable.
Are the Stable Build newer than the devel builds?
Reading the channel selection guide I tought that the devel builds would be newer.
jonny-boy said:
Are the Stable Build newer than the devel builds?
Reading the channel selection guide I tought that the devel builds would be newer.
Click to expand...
Click to collapse
Oh, that page needs to be adjusted. I'll mention it on the mailing list.
The stable builds are much more up to date. In fact, they do not push updates to the devel channel anymore. If you really want to get the latest and (possibly not) greatest, you need to install devel-proposed. However, please notice those builds may not even boot. That just happened three days ago again.

[ROM] [unofficial] Lineage 16.0 Developer Preview

The Developer Preview has ended. The official release has been released and can be found here https://forum.xda-developers.com/moto-x4/development/rom-lineage-os-15-1-t3802265
The current (unofficial) Developer Preview is developed by @erfanoabdi This thread serves as a means to help folks from further discussing LOS16 within the Official Lineage 15.1 thread (to help prevent that thread from being both further hijacked and to prevent confusion from the two in conversation).
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Please remember this is NOT a final release. There WILL be bugs. It is also very possible that you could end up bricking your phone by attempting to install, use, or upgrade LOS16 and you do so at your own risk.
How to install Lineage 16.0 Developer Preview
!! Please read in full before proceeding !!
Remember to submit logs when reporting any errors.
Remember to be as detailed and as clear as possible on what actions you took which resulted in any errors.
Download the latest Official TWRP https://dl.twrp.me/payton/. - You want the .img file.
Restart your phone to your bootloader. - You do this by pressing and holding both your phone's power button and the lower volume key at the same time.
Once at your phone's bootloader, from your Windows Command Prompt (as administrator) or from your Linux Terminal (as root) run the following command to load TWRP:
Code:
fastboot boot '/your_path_here/twrp-X.X.X-X-payton.img'
Note: Be sure to use your path on where you have the file on your computer. Be sure to replace and use the correct file name for your file (Do not just copy and paste example posted here).
!! You will be wiping everything because this is a developer preview and bug reports are most helpful on a clean, fresh install !!​
Regardless of what ROM you are coming from (stock or not), format your DATA.
Reboot your device to bootloader and reuse the previous fastboot command to load TWRP listed above.
Regardless of what ROM you are coming from (stock or not), wipe your device (all partitions).
Reboot your device to bootloader and reuse the previous fastboot command to load TWRP listed above.
Download "Copy Partitions Zip" - courtesy of @filipepferraz https://drive.google.com/file/d/1oiry9UfP2tf-5A6nQBF7pn2t2eSGKt0F/view
Upload "Copy Partitions Zip" to your phone using the "ADB Push" command to /sdcard/ (run as admin if on windows or as root if on Linux).
Code:
adb push copy-partitions-payton.zip /sdcard/
Now INSTALL "Copy Partitions Zip"
Reboot to your bootloader. - Stay at the bootloader screen (do not load TWRP)
Download the firmware for your phone
XT1900-1 Android 8.0
firmware_27.251.12_payton_retail_xt1900-1.zip
Only tested on
XT1900-1
XT1900-2
XT1900-5 (https://forum.xda-developers.com/showpost.php?p=76934354&postcount=173)
XT1900-7 (https://forum.xda-developers.com/showpost.php?p=76779696&postcount=14)
feel free to test on other Moto X4 models running 8.0.
XT1900-6 Android 8.0 - courtesy @filipepferraz
https://www.androidfilehost.com/?fid=674106145207492371
XT1900-1 Android 8.1 - courtesy @ptn107
https://www.androidfilehost.com/?fid=890278863836292604
tested on XT1900-7 as well (https://forum.xda-developers.com/showpost.php?p=76816113&postcount=92)
Latest firmware for payton_fi android 9 from PPW29.69-26 - courtesy @ptn107
firmware-29.69-26_payton-fi_xt1900-1.zip
Unzip on your computer.
User flash_all.bat if on windows as administrator OR ./flash_all.sh if on Linux as root.
Reboot your phone to bootloader
Reboot your device to bootloader and reuse the previous fastboot command to load TWRP listed above.
Download and locate the latest developer preview: https://androidfilehost.com/?w=files&flid=281597
You will upload these files to your phone using the "ADB PUSH" command to your /sdcard/ directory (as admin in windows or root in Linux). For example:
Code:
adb push lineage-16.0-20180921-UNOFFICIAL-payton.zip /sdcard/
Install your ROM.
Congratulations! You're done!
NOTE: The point of using a developer preview is to test the ROM itself. You can attempt to install TWRP after installing your ROM, just as you can reboot back to recovery after, and install OpenGapps, followed by Magisk, but that is NOT the true point of testing this ROM. While it may be useful to know of issues with those commonly used tools, the primary concern is the ROM itself at this time.
Remember to submit logs when reporting any errors.
Remember to be as detailed and as clear as possible on what actions you took which resulted in any errors.
MotoX4 said:
Remember to submit logs when reporting any errors.
Remember to be as detailed and as clear as possible on what actions you took which resulted in any errors.
Click to expand...
Click to collapse
Excelent Rom very good accuracy of battery, but usb adb is not working
Hi @erfanoabdi, I am really enjoying this ROM.
Question: Is there any way to replicate the Retail X4's One Button Nav? It seems to have implemented a press/long-press/longer-press for the fingerprint scanner. Not sure if something like this is in the AOSP code or not. It is really awesome for locking screen AND keeping Google Assistant.
---------- Post added at 08:05 PM ---------- Previous post was at 07:18 PM ----------
I have played around a it with flashing Generic System Images (GSI) over this ROM, and it seems to be quit compatible most of the Android 9 ones that I have tried.
It is awesome that this phone suddenly has many options to toy with (yes, I said it, it is a toy) due to the hard work of the devs Trebelizing (or is it Treble-izing?) our Moto X4!
---------- Post added at 08:09 PM ---------- Previous post was at 08:05 PM ----------
vmmiguel said:
Excelent Rom very good accuracy of battery, but usb adb is not working
Click to expand...
Click to collapse
USB ADB seems to be working fine for me. I am on the 9/29 version.
jhedfors said:
Hi @erfanoabdi, I am really enjoying this ROM.
Question: Is there any way to replicate the Retail X4's One Button Nav? It seems to have implemented a press/long-press/longer-press for the fingerprint scanner. Not sure if something like this is in the AOSP code or not. It is really awesome for locking screen AND keeping Google Assistant.
---------- Post added at 08:05 PM ---------- Previous post was at 07:18 PM ----------
I have played around a it with flashing Generic System Images (GSI) over this ROM, and it seems to be quit compatible most of the Android 9 ones that I have tried.
It is awesome that this phone suddenly has many options to toy with (yes, I said it, it is a toy) due to the hard work of the devs Trebelizing (or is it Treble-izing?) our Moto X4!
---------- Post added at 08:09 PM ---------- Previous post was at 08:05 PM ----------
USB ADB seems to be working fine for me. I am on the 9/29 version.
Click to expand...
Click to collapse
For me doesn't work, nothing appears in notificacions bars or even in fastboot can´t recognize my device...
Actually i have running this rom, but i don´t have GAPPS installed, and the adb is not working so i cant flash via fastboot the twrp for install my gapps, any suggerency to do?:good::crying:
jhedfors said:
Hi @erfanoabdi, I am really enjoying this ROM.
Question: Is there any way to replicate the Retail X4's One Button Nav? It seems to have implemented a press/long-press/longer-press for the fingerprint scanner. Not sure if something like this is in the AOSP code or not. It is really awesome for locking screen AND keeping Google Assistant.
Click to expand...
Click to collapse
Thanks for using this rom but you can enable it from
Setting system buttons and disable on screen nav bar
I couldn't get long hold and longer hold to detect in custom roms but still it's usable for home recent and back buttons
You can set hold home button to action something else then assist (lockscreen)
erfanoabdi said:
Thanks for using this rom but you can enable it from
Setting system buttons and disable on screen nav bar
I couldn't get long hold and longer hold to detect in custom roms but still it's usable for home recent and back buttons
You can set hold home button to action something else then assist (lockscreen)
Click to expand...
Click to collapse
Thanks. I am using the fingerprint navigation as you describe. I am using an app that detects a double-tap, which I am using to lock the screen.
Sorry for OT:
Is there any way to take the long-press away from Google Assist (and be able to re-assign it) short of UN-installng Google? When I "disable" it in the Google App, or even change the default assist app, long press fingerprint only prompts to re-enable Google Assist. It seems those settings only apply to long-press Home, but not long-press fingerprint. Google Assist has hijacked my fingerprint button!
Thanks again.
jhedfors said:
Thanks. I am using the fingerprint navigation as you describe. I am using an app that detects a double-tap, which I am using to lock the screen.
Sorry for OT:
Is there any way to take the long-press away from Google Assist (and be able to re-assign it) short of UN-installng Google? When I "disable" it in the Google App, or even change the default assist app, long press fingerprint only prompts to re-enable Google Assist. It seems those settings only apply to long-press Home, but not long-press fingerprint. Google Assist has hijacked my fingerprint button!
Thanks again.
Click to expand...
Click to collapse
I disabled the "google" application and stopped bothering with activating it again, it was the only way I found, because if you deactivate the assistant only when you keep it pressed the sensor sends the message to activate it xD
vmmiguel said:
Excelent Rom very good accuracy of battery, but usb adb is not working
Click to expand...
Click to collapse
I hope somebody to help me, last night i tried to update mi Lineage OS 16 (from erfanoabdi).
My device is unlocked bootloader, and i used the rom from nightly build (2018-21-09), it works fine and everything, the issue becomes when i look what was avaible a new update, so downloaded and install the new rom.
I do full wipe, after that i install the new rom, at this point everything its working fine, but after that when i changed the partition slot from A to B.
When i started to install the gapps they closed because it says what i am running Android 8.0, but its a mistake so i think that reboot the phone without install the gapps. So the phone starts well, so i decide again to boot into recovery (TWRP) to install the missing gapps.
When the device reboot in fastboot and i chosee the recovery option, the surprise was that TWRP was reemplaced by the stock recovery, and when i tried to flash the TWRP.img my device wont appear in fastboot mode, stays finding device and Windows wont recognized my phone.
I think the rom still no have usb adb support, so i cant flash TWRP
My device its unlocked and i was running the rom (but another nightly) .. without issues for a week ago... until i flashed this one
Now i have Lineage OS without GAPPS, without USB mode... Like the update from OPW 27 or 28 idk remember.
Thanks for read this i hope somebody can help me.
My device its a XT1900-4 in Android 9.0 without google apps, only have the essencial apps like phone dialer , sms, the very very essencials app. Like an phone from 2008 jhaha
I attach some information photos from the Rom that im running:
(System Running) fine thanks
https://ibb.co/bXC7ye
(ADB is switched on, but no appears nothing)
https://ibb.co/exGpBz
(I tried with everyone of the opcions
https://ibb.co/ekv5jK
and this is my currently fastboot:
AP Fastboot Flash Mode (Secure)
BL: MBM-3.0-uefi-641a15b-180224
Baseband: M660_7042.27.01.74R PAYTON_LATAM_CUST
Product/Variant: payton xt1900-4 32GB P4
CPU: SDM630 1.0 (6)
Console [NULL]: null
Tools Mode Config: DISABLED
POWER OK
flashing_unlocked
Software status: Official
Transfer Mode: USB Connected
At this point my windows so says to my device is Error in a request for the USB device descriptor.
i tried last_usb_google driver.
Motorola Device manager 2.5.4
Minimal adb fastboot 1.4.2
and nothing works fine.
In my recovery appears this:
Android Recovery
motorola/payton/payton
8.0.0/OPW27.57.25-6-10/12
user/release-keys
Use volume to...etc and then i used the (Apply update from adb)
says:
Supported API: 3
Stopping adbd. . .
Now send the package you want to apply to the device with "adb sideload <filename>"
I tried to navigate in the device with the terminal app, so i put this command in terminal to make ADB run
command adbd, and this appears on terminal:
adbd E 10-04 23:01:31 3819 3819 adbd_auth.cpp183] Failed to get adbd socket: success
adbd E 10-04 23:01:31 3819 3819 adbd_auth.cpp183] Failed to get adbd socket: success
i try to run command logcat.txt, but terminal cant move to sdcard.
i try to adb over network and that connect but can´t do anything because stuck on <waiting device>, i look the blankflash but
didn´t works to me, and in the configurations usb settings looks greyed so cant switch between then.
when i run the command ls i saw this files:
init.usb.configfs.rc
init.usb.rc
init.recovery.qcom.usb.rc
maybe there is my problem? Thanks for read, thanks to @erfanoabdi he works very hard to make this possible, i hope somebody can
help me.
vmmiguel said:
I hope somebody to help me, last night i tried to update mi Lineage OS 16 (from erfanoabdi).
...
When the device reboot in fastboot and i chosee the recovery option, the surprise was that TWRP was reemplaced by the stock recovery, and when i tried to flash the TWRP.img my device wont appear in fastboot mode, stays finding device and Windows wont recognized my phone.
...
Click to expand...
Click to collapse
Not sure if I understood all of your post.
On the MotoX4 there is no separate partition for the recovery, it is build into the system boot image / ramdisk. If you flash a new LineageOS or a new kernel youre TWRP is gone. So before you boot, you have to reflash TWRP. If you forgot to do this, you have to bring your device to fastboot mode (Volume down + Power 'till it boots to fastboot mode). Then boot it by "fastboot boot twrp-3.2.3-1-payton.img" to TWRP. If it has booted to TWRP recovery only then you can "adb push twrp-install-xxxx-payton.zip /sdcard" and install it from recovery. After that you should be able to directly reboot to recovery and flash what you need.
I always have all required "xxx.zip" on my microSDcard, so that I can flash them from TWRP without sideload or adb push. Remember to reboot to recovery after every "xxx.zip" flashed because of the A/B design of the MotoX4.
---------- Post added at 09:46 PM ---------- Previous post was at 09:41 PM ----------
Anybody else?
WLAN for me does not connect on lineage-16.0-20180929-UNOFFICIAL-payton.zip, if you have a hidden network (SSID). It will be shown as "saved" but does not try to connect.
Worked on lineage-16.0-20180921-UNOFFICIAL-payton.zip.
vmmiguel said:
Excelent Rom very good accuracy of battery, but usb adb is not working
Click to expand...
Click to collapse
USB is working for me (09/29)
For testing I changed my wlan SSID to visible on my wlan router and a second later, wlan is connected. Setting it back to unvisible drops the connection. So I think its's a bug in 09/29 LOS preview.
Gesendet von meinem Moto X4 mit Tapatalk
Just got around to trying the FM Radio app, and it is not working for me - working for anyone else? I did not check if it worked on 15.1...
jhedfors said:
Just got around to trying the FM Radio app, and it is not working for me - working for anyone else? I did not check if it worked on 15.1...
Click to expand...
Click to collapse
I'm trying too, does not work
FM not working here also... build from 21.09. 2018. - Don't want to upgrade to 2909, waiting for October build, September builds look obsolete now
Demoniackers said:
Rom Pixel Experience unofficial TREBLE Android 9 ARM 64 A/AB (GSI) Working (TRY IT)
...
Running almost everything, in Moto x4
-Magisk, modules, Volte, bluetooth.
I have not tried, NFC, Hotspot
Bugs: Headphone Jack, Second camera, One Button (fingerprint gestures) It is not deactivated
Could you solve the errors?
Click to expand...
Click to collapse
Wrong thread/forum.
Edit: it is VERY bad form to spam all the different threads that you have posted to. If you annoy people, they are less likely to want to help you.
PLEASE HELP!
Unfortunately I do not know how to report error logs but I will describe my issue the best I can.
I am on a moto x4. XT1900-1, Android One edition. Bootloader Unlocked.
I followed the steps to a "T". Everything went smooth with rom install but I noticed a couple things. When running the flash_all.bat file, everything but flashing the modem completes successfully. It gives a failed message.
Code:
PS C:\platform-tools\firmware> .\fastboot flash modem_a modem.img
Sending 'modem_a' (112640 KB) OKAY [ 2.806s]
Writing 'modem_a' (bootloader) Preflash validation failed
FAILED (remote failure)
Finished. Total time: 2.830s
It does this for modem_a and modem_b.
When I boot to bootloader(fastboot), it shows Baseband: <not found>
I haven't finished setup to see if I get cellular service. My guess is NO. Can you please help? Why would it be failing to flash the modem. I am trying the 8.1 firmware for Project Fi.
Thank you.
reedc83 said:
PLEASE HELP!
Unfortunately I do not know how to report error logs but I will describe my issue the best I can.
I am on a moto x4. XT1900-1, Android One edition. Bootloader Unlocked.
I followed the steps to a "T". Everything went smooth with rom install but I noticed a couple things. When running the flash_all.bat file, everything but flashing the modem completes successfully. It gives a failed message.
Code:
PS C:\platform-tools\firmware> .\fastboot flash modem_a modem.img
Sending 'modem_a' (112640 KB) OKAY [ 2.806s]
Writing 'modem_a' (bootloader) Preflash validation failed
FAILED (remote failure)
Finished. Total time: 2.830s
It does this for modem_a and modem_b.
When I boot to bootloader(fastboot), it shows Baseband: <not found>
I haven't finished setup to see if I get cellular service. My guess is NO. Can you please help? Why would it be failing to flash the modem. I am trying the 8.1 firmware for Project Fi.
Thank you.
Click to expand...
Click to collapse
I once did a quick Google search on this issue as I too faced this problem. It is safe to ignore. Allow me to explain:
This is safe to ignore. All it means is that your device already has a new firmware at that particular base. I, personally, originally used, for my device, XT1900-1 Android 8.1 - courtesy @ptn107 https://www.androidfilehost.com/?fid=890278863836292604 and the first time I used it (coming from STOCK) everything flashed without any issues. A few updates later and if I attempt to use it again, it proceeds to flash everything and it skips (soft fails) on 1 point while proceeding to do everything else. This is because, on that particular point, I likely have a newer firmware.
You should be able to proceed as normal and safely ignore that small error.
MotoX4 said:
I once did a quick Google search on this issue as I too faced this problem. It is safe to ignore. Allow me to explain:
This is safe to ignore. All it means is that your device already has a new firmware at that particular base. I, personally, originally used, for my device, XT1900-1 Android 8.1 - courtesy @ptn107 https://www.androidfilehost.com/?fid=890278863836292604 and the first time I used it (coming from STOCK) everything flashed without any issues. A few updates later and if I attempt to use it again, it proceeds to flash everything and it skips (soft fails) on 1 point while proceeding to do everything else. This is because, on that particular point, I likely have a newer firmware.
You should be able to proceed as normal and safely ignore that small error.
Click to expand...
Click to collapse
Thank you for the information! I was able to proceed and most things seem to work fine.
I noticed a couple bugs to report so far.
- External SD not available.
- Project Fi will not get LTE on US Cellular or Sprint.
- Messages app will not allow dark mode. Option is there but it does nothing. (I noticed this in the latest official build of LOS 15.1 as well. 20181002 build of 15.1 worked fine.)(I did install OGAPPS so this may be my fault.)
- Settings > Display > Color? does nothing. On LOS 15.1, I could switch it to be more saturated. I put a question mark because I am back on stock at the moment and don't remember exactly what the color option was called.
Other than that I was loving the smoothness of the ROM. I want to go back but have a hard time living without my project fi working as I live in a remote location and drive back-roads and need for my service to work across carriers.
Question, do we need to install any of the stuff found on the GSI version like the FBE_Disable etc? I don't know what GSI stands for or how that differs from this. Sorry for the noob question.
Thank you so much for the OP and sharing this. Really hope to see an October build soon that address some of the bugs.
reedc83 said:
Thank you for the information! I was able to proceed and most things seem to work fine.
I noticed a couple bugs to report so far.
- External SD not available.
- Project Fi will not get LTE on US Cellular or Sprint.
- Messages app will not allow dark mode. Option is there but it does nothing. (I noticed this in the latest official build of LOS 15.1 as well. 20181002 build of 15.1 worked fine.)(I did install OGAPPS so this may be my fault.)
- Settings > Display > Color? does nothing. On LOS 15.1, I could switch it to be more saturated. I put a question mark because I am back on stock at the moment and don't remember exactly what the color option was called.
Other than that I was loving the smoothness of the ROM. I want to go back but have a hard time living without my project fi working as I live in a remote location and drive back-roads and need for my service to work across carriers.
Question, do we need to install any of the stuff found on the GSI version like the FBE_Disable etc? I don't know what GSI stands for or how that differs from this. Sorry for the noob question.
Thank you so much for the OP and sharing this. Really hope to see an October build soon that address some of the bugs.
Click to expand...
Click to collapse
Here the external SD works as portable storage with ou a problem.
The LTE is a known problem.
I don't know about the dark mode from message app.
In the stock rom you need to deactivate night mode to change the color, in Los 16 you change it at Live Display.

Categories

Resources