Database Info

Sharp FX PLus/Capa ADS1 - Root, System Dump, ClockWorkMod Recovery, Device Info

EDIT 12/24/2014: Finally got back into my XDA account and finally updating this post with (hopefully) functionall links to the files I still have, Merry Christmas everyone!!
HI, found the misc development section so I'm putting all my findings on the Sharp FX Plus ADS1. Closest device I found that has cyanogenmod is the ZTE V9 (Theres a Z71 and some others also), I'm sure there are others but figure I'd post this in an appropriate spot incase anyone is curious. I'm attempting to get CyanogenMod of booting on this for a nice learning experience.
This phone has a Froyo 2.2.2 ROM, when "slimmed" or de-bloated the little thing is pretty snappy. Chainfire 3d Pro installed with no problems, ClockworkMod Recovery backups/restore work (updating to newer version doesnt "recognize" CWM installed, but older one allows reboot into recovery), Terminal and ADB dont give me any issues at all, logcat can be done from boot with the insecure boot.img. Hopefully this information is usefull to anyone curious.
Removed "links other information" - my old domain is not up.
Drivers:
-Sharp has them available from this site (for Windows/OSx)
Device:
Qualcomm MSM7x27 @ 600MHz
Adreno 200
512MB RAM, 512MB ROM (200-ish available to user).
Root:
-SuperOneClick 2.3.3 worked fine for me
ClockWorkMod Recovery:
-You should already be rooted before doing this.
-Made from the stock recovery.img processed on the CWM builder site. Its version 6.
-Only thing that doesnt work at the moment is mounting via USB mass storage. Aside from that, works like a charm.
-Download the files zip (attached to this post)
-Copy flash_image and the recovery.img of choice (stock is in root of archive, CWM folder contains the ClockWorkMod Recovery).
-Run these commands from terminal (on device or adb)
Code:
mount -o remount,exec /dev/block/vold/179:1 /sdcard
cd /sdcard
./flash_image recovery /sdcard/recovery.img
reboot
{
"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"
}
System Dump:
-I can try and make a "stock ROM" flashable zip, but I'll need a stock dump from a rooted ADS1. I only have the modified "stock ROM".
LINKS NOW AT DEV-HOST
Modified ROMS:
Stock 2.2.2 based (google apps pre-installed)
ADS1-2.2.2 test-acemod4x
CM6 Z71 port
CM6.1.2-ADS1 Z71 test-port
modded google apps for the CM6 port ONLY
Other info:
-output of mount
Code:
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
/dev/block/mtdblock1 /system yaffs2 ro,relatime 0 0
/dev/block/mtdblock9 /data yaffs2 rw,nosuid,nodev,relatime 0 0
/dev/block/mtdblock7 /persist yaffs2 rw,nosuid,nodev,relatime 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /tmp tmpfs rw,relatime 0 0
/dev/block/mtdblock3 /cache yaffs2 rw,nosuid,nodev,relatime 0 0
/dev/block/mtdblock5 /fotaup yaffs2 rw,relatime 0 0
/dev/block/vold/179:1 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0712,dmask=0700,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:1 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0712,dmask=0700,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/dm-0 /mnt/asec/com.keramidas.TitaniumBackup-1 vfat ro,dirsync,nosuid,nodev,noexec,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-1 /mnt/asec/com.adobe.reader-1 vfat ro,dirsync,nosuid,nodev,noexec,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-2 /mnt/asec/com.aol.mobile.aim-1 vfat ro,dirsync,nosuid,nodev,noexec,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
-output of cat /proc/mtd
Code:
$ cat /proc/mtd
dev: size erasesize name
mtd0: 00500000 00040000 "boot"
mtd1: 0a500000 00040000 "system"
mtd2: 00100000 00040000 "splash"
mtd3: 02800000 00040000 "cache"
mtd4: 00080000 00040000 "fota_state"
mtd5: 02100000 00040000 "fota_up"
mtd6: 00080000 00040000 "misc"
mtd7: 00280000 00040000 "persist"
mtd8: 00500000 00040000 "recovery"
mtd9: 0bcc0000 00040000 "userdata"
-Also BOARD_KERNEL_ stuff (when breaking the original kernel down)
Code:
BOARD_KERNEL_CMDLINE mem=458M console=ttyMSM2 androidboot.hardware=qcom
BOARD_KERNEL_BASE 13600000
BOARD_PAGE_SIZE 4096

Was stuck for a while trying to repack a insecure kernel, few "bricks" (thank goodness for CWM's backups lol).
Got it to work and boot! Its still the same original boot.img but I was able to repack it with ro.secure=0 and other changes to the default.prop (enabled adb, debugging etc..)
Heres a link with info on it, and heres the files (in zip this time) incase anyone wants to test.
Basically (if anyone wants to try this insecure.boot.img) for test (make sure you have CWM and a Nandroid backup first) - Phone should already be rooted (SuperOneClick 2.3.3), ADB Debugging on (I used a ADB shell to do this, you should be able to run the commands from the terminal on the device itself)
Open the archive, copy the flash_image (if you havent from the CWM Install), also copy the insecure.boot.img over to the sdcard (you can alsio do this with the original boot.img to restore)
Code:
su
mount -o remount,exec /dev/block/vold/179:1 /sdcard
cd /sdcard
flash_image boot insecure.boot.img
reboot
All goes well, the phone should reboot normally. MInes took a little longer on initial booting, but it went through using that boot.img and the stock rom.
Now onto the next hurdle (getting CyanogenMod to compile) - The problem I was having before was using a version of mkbootimg that did not support the --pagesize option.
I'll try repacking the zImage that was built into a CM7 ramdisk and see if I can get past the "Sharp" screen and try to boot..
If anyone has any thoughts on the subject it would be greatly appreciated, back to the terminal I go

CM6 Booted
Well, went back to trying to see what would "boot" in this phone. My attempt to port CM6 to this ADS1 is somewhat successful!!!!
Currently botted into a modified Z71 CM6 ROm, using the insecure.boot.img I repacked for the Sharp ADS1.
Compared the system structures side by side and added the ADS1 bits (also for the surf_keyboard and other stuff).
Removed Z71 specific files, made a hybrid build.prop with the ADS1 changes.
Result: Boots!! Pretty Usable!!!
Still Broken:
-No camera/camcorder (checking the libcamera files)
-WiFi
-keyboard backlight
-some keyboard buttons (@ key, everything else is good - onscreen and swype are in from stock rom)
Works:
-battery charging (even switches to the sharp charging screen when its off but plugged in)
-radio - H+ on the status bar, data, sync, sms, etc.. (havent tried MMS yet)
-bluetooth - enables fine, just need something to pair with
-boots (initial boot takes a while as it does its firstrun thing, reboots are very fast)
-sound works
-graphics seem smooth as butter (going through the UI, etc..)
-touchscreen
-qwerty keyboard
-screen rotation works
-CM6 gapps work
Anyways, I'm kinda excited that atleast CM6 booting and (aside from the broken stuff) somewhat usable! I'll attatch the logcat I made with adb as it booted, did some testing, etc.. Incase anyone wants to see.

CyanogenMod 6 ROM testing Updates.. (SO FAR SO GOOD!!)
(I accidentally posted this in the General thread I had, and it wouldnt let me delete it - so I put the information in this as its under the Misc Development section)
Update on "porting" CM6 for the Commtiva Z71 to the Sharp ADS1.
Not Working:
-WiFi - logcat shows an error when loading the libra.ko seems to load librasdioif.ko fine however
-Camera - logcat shows problem loading liboemcamera.so (using the ADS1 libs and Camera.apk)
-3d Acceleration - works, but has some hiccups (so it still needs *some* work - importing some Adreno200 EGL libs over improved greatly so far)
-USB Mounting - havent gotten to this yet, still working on WiFI/Camerea. ADB however works flawlessly (push, pull, reboot, lolcat/logcat, etc..)
[email protected] Key and SYM on physical keyboard arent mapped correctly (going to see if I can poll the keys and figure that out) also the Camera physical button does not map.
Working:
-Calls (speaker also, mute, normal, etc..)
-Data (uploaded my wordpress post from the device, market sync works, etc..)
-SMS/MMS
-SDCARD (can be browsed internally, SD-Ext for app2sd works, no USB Mounting yet)
-Bluetooth
-Audio
-Keyboard Backlight+Sensors (properly shuts off when screen is slid closed)
-Deep Sleep seems to be working (battery life seems to be decent, still gotta work other bugs out)
-Rotation sensor (open keyboard, screen rotates for you also)
-Auto brightness sensor looks to be working normally (even turns keyboard backlighting off it seems)
http://acebox.info/2012/07/sharp-fx-plus-ads1-z71-cm6-test-rom/
I'm a little stumped on the WiFi + Camera issue, both roms (CM6-Z71 and ADS1-Stock) are running similar Kernels, and the version of Froyo is almost identical; CM6-Z71 Is actually 2.2.1 and ADS1 is 2.2.2 as I recieved it (CyanogenMod runs sooo much better ).
wifi libs (in /system/lib/modules):
Code:
libra.ko
librasdio.ko
modules.dep.bb
If anyone has some time to help or atleast offer some insight, I can repost the stock dumps, nand backups, kernel, ramdisk, logcats - and even a cwm zip I've made for flashing a "slimmed" version of the stock 2.2.2 Froyo as well as any "working" version of the CM6 "port" I'm attempting). I've been comparing logcats from the stock rom and this to see what can possibly be stopping wifi/camera working..
The CM6 ROM IS EXPERIMENTAL AND NOT A DAILY DRIVER AT ALL - (I wouldnt consider it untill WiFI, Camera, etc.. are functional. It is usable - even updated my wordpress post from the device with screenshots, hower it is still an Development Work In Progress).
If anyone is feeling brave (or wants to help test), I've uploaded the CWM zips I used (experimental) onto my site (linked in this post). FLASH CLOCKWORKMOD RECOVERY AND DO A NAND BACKUP FIRST!! Then go nuts flashing away lol. Hope someone finds this usefull.
PS. THIS IS NOT A DAILY DRIVER ROM, ONLY FOR TESTING!
Info/ROM links - current ones posted here towards the bottom (so I only have to update one set of links lol)

WiFi partially working
UPDATE:
Got wifi working, test release here more information here. I fixed a few things in the ramdisk and updater-script. Now to get the camera/video and USB mounting working (ADB is fully functional, push/pull/logcat/lolcat work).
Also the original Swype, Weather, SMS and Email widgets work. For the market, flash the CM6 20110501 MDPI gapps package from here (its persistent between full wipes, use a NAND backup to return to clean install, workingo n a updater-script that fully wipes and removes all traces of GAPPS (doesnt seem to currently).
Shots of About Phone and Storage (theres some room I think)

UPDATE (EGL and Camera fixed!) - Notes on swapping libs between roms
Saw a nice way of using readelf and it helped getting a lot of things sorted out.
Basically made a shell script and but it into my ~/bin folder and used that to manually check dependencies of the libraries. checked them and made sure they matched, flashed the phone and now its almost 100%!
I believe replacing libc.so from the CM6's /system/lib with the ads1 broke adb logcat - adb shell works, push/pull work fine. Gallery3d is now VERY smooth, Camera works fine now (tested snaps, etc..)
so, to recap lol..
STILL BROKEN:
-USB Mass Storage (going to check ramdisk)
-adb logcat/lolcat (cannot link executable since fixing EGL)
-Need to check GPS (noticed I've been checking with WiFI only)
WORKS:
-Phone/Data
-SMS/MMS
-WiFI/Bluetooth
-Camera/Video
-EGL smooth
-SD Internal mounting/browsing (SD-Ext also for APP2SD)
-CyanogenMod 6 settings
-ADWLauncher Settings
-Sharp Widgets (SMS/Email)
-Gapps (use the CM6 MDPI version)
-Slide out Keyboard (still going to look at the @, Sym and Camera button mappings)
-Keyboard Backlight (with light sensor adjusting)
-Rotation Sensor
I'll post a link to an updated version soon if anyone wants to test, just sorting out a few small things - progress is progress! Hopefully have USB mounting working.

test version cm6-z71 port beta1
Got the ROM somewhat stable, EGL seems to be working VERY smoothly (tracked back dependencies) and Camera/Video work (using CM6 camera apk, going to test with the Froyo/Sharp camera apk).
Link to test here - more information here.
Hope this is helpful to anyone testing.

Updated Ext3 ClockWorkMod - CyanogenMod 6.1.2 USB test.
Updated the ClockWorkMod Recovery from the builder site (generated using a dump of the stock.img)
Now it formats /sd-ext as Ext3 and not Ext4 (more info here). Also included the stock recovery image and tools.
Also got a test version of the CM6.1.2 port (more info here) - USB mass storage should work, no Google Apps (can be downloaded seperately - get CyanogenMod 6 MDPI version).
BUGS/TODO:
-Looking at a hardware keyboard "glitch" - Sym key brings up the "Select Input Method" menu (vs the Symbol menu). The @(AT) key also is unresponsive, using KeyTest.apk - shows as picking up #215 - but its not doing anything.
-Need to test the GPS
-Need to test Bluetooth pairing more
-Checking issue with init.d automounting sd-ext (running /system/etc/init.d/05mountsd works)
-If ADW Launcher stays stuck in Portrait mode (wont rotate), uncheck System Persistent from the ADW System options if its checked in and having problems.
DOWNLOADS:
CWM-EXT3-TEST (unpack to your SDCARD)
CM6.1.2-ADS1-B4a2 (flash with CWM, backup and data wipe prior to testing)

Notes on building CyanogenMod from source possibly..
Noticed when I got my initial zip back from the CM builder site, it had a device tree for the ads1. There isnt any "vendor" specific one matching, however I'm playing with one mocked from the Z71 tree (as they seem oddly similar).
I've already contacted Sharp about the sources, but not sure if I'm asking correctly . Maybe they'll respond. I was also asking about if they would have some kind of update.zip for the phone, theres a few other members that have "bricked" phones - a Sharp signed update.zip would work nicely for the stock recovery (unless theres another method)
However, just incase - testing this for a "proprietary mock up" to see if anything can work lol
-compared the extracted-files from the z71, removed the ones the ads1 did not have.
-ran a recursive diff between the bin, lib, etc folders between a Z71 cm6 rom (which I've based my test) and a system dump I made of the ADS1.
-added missing files for now (some might be for the Sharp UI Launcher)
-extract files works, copies the requested files off the phone (I've got a blend of a few ads1 froyo bits ontop of z71 cm6 atm)
-testing the local_manifest.xml to get it to work, experimenting
Still missing rild and libaudio sources (as well as some other ones I noticed in the Z71 tree) - going to experiment building a Froyo rom from source, using existing rild/audio libraries. Not entirely sure what I'm doing (as there is no real support for this device at all), just proceeding carefully and examining the surroundings as best as I can lol.

Z71-CM7.2.0 boots (needs work, but its something!)
Tested with a Z71 CM7 port that uses a similar kernel version to whats available for the ads1..
http://acebox.info/2012/07/sharp-fx-plus-ads1-cm7-test/

Hi Amaury,
I have been reading your posting these days. I am a new android device user, and I just bought a Sharp ADS1 to replace my old phone.
I would like to know which software did you use to root the ADS1, Can "SuperOncClick" root it?
And, do you have a back-up file of the original Stock ROM? or Can the "ClockwordMod" do the back-up for the original ROM?
Also, do you think it's possible to upgrade the Android 2.2 to Android 3.0 or even 4.0, 4.1 for this device?
This cell phone seems very nice and well functioned, but not many users or developers discuss about it.
Thanks for your answer and posting.

wisesoar said:
Hi Amaury,
I have been reading your posting these days. I am a new android device user, and I just bought a Sharp ADS1 to replace my old phone.
I would like to know which software did you use to root the ADS1, Can "SuperOncClick" root it?
And, do you have a back-up file of the original Stock ROM? or Can the "ClockwordMod" do the back-up for the original ROM?
Also, do you think it's possible to upgrade the Android 2.2 to Android 3.0 or even 4.0, 4.1 for this device?
This cell phone seems very nice and well functioned, but not many users or developers discuss about it.
Thanks for your answer and posting.
Click to expand...
Click to collapse
Hi, SuperOneClick 2.3.3 did the trick for me.
Unfortunately, dont have a backup of the stock system, The Clockworkmod custom recovery can backup the entire phone state to your sdcard, and you can restore the entire phone back to that exact state. Also if you can get a stock dump (all stock apps), let me know - I can probably try making a "flash to stock" cwm zip for it.
I'm not sure but think Sharp would have to release sources for the device? Or find sources that would be compatible with this device. Its pretty similar to a Commtiva Z71 as far as I can tell. I'd like to eventually try CM9 booting on this, so started with getting CM6/Froyo to work first - and found the Z71 worked with few modifications.
I found a Z71 Gingerbread 2.3.7 CM7.2 rom runs a similar 2.6.32.x kernel that boots (with modification) and somewhat works (no network, local/audio/touch/keyboard works). Would be nice to see something newer than froyo on this phone, so I'm posting whatever info on it while learning things in the process.
EDIT:
Not sure if Sharp will update the phone to Gingerbread, they havent released a update.zip for restoring the stock Froyo image yet. The device can definitely run Gingerbread, I'm playing with Z71 libs on a hybrid ROM that boots and (aside from phone/data/wifi/networking and screen timeout issue) runs rather quickly and smooth. I've been trying to contact Sharp about this device, but havent heard back yet. Guess I'm asking the wrong questions lol.

Kernel notes revisited
UPDATE: re-uploaded what was built with the modules for testing (previously only uploaded zImages)
Added some notes when I tried building the kernel incase anyone's interested - here. I've uploaded a test mock up of a device/vendor tree. The kernel config off the device as well as some test kernels (zImage only) built from the cm-kernel source. android-msm-2.6.35-unified and android-msm-2.6.33-ds
The device tree actually came from the ClockWorkMod builder site iirc, modded with some Z71 bits (to make the vendor side). Hopefully this helps anyone testing, as I havent had time to play with source building much (working on fixing bugs in the CM6 test port).

Updated ROMs (Froyo based)
DISCLAIMER: These are testing roms, they work pretty well for me - but always backup before flashing anything. Not responsible if sliding open the keyboard rips the fabric of time. WIth that out of the way...
I've uploaded 2 roms for the Sharp FX Plus (ADS1) - one is based off the stock 2.2.2 (Holo launcher, init,d, etc..) second rom is an updated version of the Z71 port I've been playing with (more on those here)
Downloads:
stock-based 2.2.2-acemod4
cm6.1.2-port-beta7
modified/slimmed google apps package

Found a user setting up official cyanogenmod support, thanks to rnorris. The github repo for the sharp fx plus ads1 is at.. more information here
https://github.com/rnorris97/sharp-ads1
I also set one up for testing unofficial device and vendor trees out for the ADS1
https://github.com/acebox/sharp_ads1_device_vendor_test
Good times for the little droid!!
Sent from my cm10-A500 using xda app-developers app

GPL Source?
Well, found out Sharp sold all rights to the FX Plus ADS1 to PCD Phones. In an email back form Sharp they refered me to asking PCD Phones about the source - PCD referred me back to Sharp. I've forwarded my emails from Sharp's support stating to ask PCD in hopes that they'll reply.
Hopefully they'll know something about the 2.6.32.9-perf kernel sources, that would definitely help with developing Android for this device from source.
More information on that here

AmauryRR said:
Well, found out Sharp sold all rights to the FX Plus ADS1 to PCD Phones. In an email back form Sharp they refered me to asking PCD Phones about the source - PCD referred me back to Sharp. I've forwarded my emails from Sharp's support stating to ask PCD in hopes that they'll reply.
Hopefully they'll know something about the 2.6.32.9-perf kernel sources, that would definitely help with developing Android for this device from source.
More information on that here
Click to expand...
Click to collapse
Any news? I'm interested in this phone.

deofavente said:
Any news? I'm interested in this phone.
Click to expand...
Click to collapse
Unfortunately none, I've been trying to get some information from either Sharp or PCD Phones on the modified kernel source and no dice. They were pointing to eachother, and being very helpful unfortunately.
It is a nice phone, and I would like to see what can be done from source vs porting roms. Definitely still some potential for the lil slider droid!
Hopefully something pops up, I've been moving around so if something pops up I'll dust mines off and get back to playing with it.

Rom Download Link ALL BROKEN....
i'm Try to download stock moded rom and cm6 rom.but download link all Broken...

all link broken please some upload sharp ads1 room and als its procedure to flash my phone have booting problem not starting sharp logo and restart i make the hardreset but still same problem.........

[Q] How to Create the CM10 ROM for Allwinner A13

Hi All,
I am newbie to the android ROM development, I got a cheap tablet to Learn how to create CM10 ROM for my tablet, it have already android 4.0.4( icecream sandwich)
Here is my tablet configuration.
kocaso m752
CPU: All Winner A13 Cortex A8 1.2GHz ;
Screen: Capacitive 7 Inch 16:9 full touch display 800 x 480
RAM: DDR III 512 MB
G-Sensor: 4 way G-Sensor
Screen Rotation: Support
Memory: 4GB
OS: Android 4.0
I rooted and installed the CWM
I extracted the following stuff from my tablet to get the system i followed this link
http://forum.xda-developers.com/showthread.php?t=1661770
system ---> folder
app
bin
vendor
etc
fonts
framework
lib
media
tts
usr
xbin
build.prop
Got boot and recover from the CWM backup option
boot -----> image
recovery---->image
Can you please help me with the steps/links to get the jellybean repo and build the CM10 ROM for my tablet or is there any compatible CM10 ROM for the Allwinner A13 Cortex A8 1.2GHz
What all need from my exsisting tablet, like firmware, framework, libraries etc. do i have to get from my tablet from system folder?
I followed this
http://forum.xda-developers.com/showthread.php?t=1821398
and didn't understand the compatibility.zip stuff.
Can you please suggest.
Thanks,
bhattu.

bhattu said:
Hi All,
I am newbie to the android ROM development, I got a cheap tablet to Learn how to create CM10 ROM for my tablet, it have already android 4.0.4( icecream sandwich)
Here is my tablet configuration.
kocaso m752
CPU: All Winner A13 Cortex A8 1.2GHz ;
Screen: Capacitive 7 Inch 16:9 full touch display 800 x 480
RAM: DDR III 512 MB
G-Sensor: 4 way G-Sensor
Screen Rotation: Support
Memory: 4GB
OS: Android 4.0
I rooted and installed the CWM
I extracted the following stuff from my tablet to get the system i followed this link
http://forum.xda-developers.com/showthread.php?t=1661770
system ---> folder
app
bin
vendor
etc
fonts
framework
lib
media
tts
usr
xbin
build.prop
Got boot and recover from the CWM backup option
boot -----> image
recovery---->image
Can you please help me with the steps/links to get the jellybean repo and build the CM10 ROM for my tablet or is there any compatible CM10 ROM for the Allwinner A13 Cortex A8 1.2GHz
What all need from my exsisting tablet, like firmware, framework, libraries etc. do i have to get from my tablet from system folder?
I followed this
http://forum.xda-developers.com/showthread.php?t=1821398
and didn't understand the compatibility.zip stuff.
Can you please suggest.
Thanks,
bhattu.
Click to expand...
Click to collapse
Hi Bhattu
I have just got an Allwinner A13 Cortex A8 1.0Ghz and I am wanting a CM10.1 on it as ICS is sluggish. I have done the CWM backup and have a full backup of the original ROM. I willspend some time looking into putting something together that should work, however this may take some time as I have never built a ROM from the ground up.

pcrepair said:
Hi Bhattu
I have just got an Allwinner A13 Cortex A8 1.0Ghz and I am wanting a CM10.1 on it as ICS is sluggish. I have done the CWM backup and have a full backup of the original ROM. I willspend some time looking into putting something together that should work, however this may take some time as I have never built a ROM from the ground up.
Click to expand...
Click to collapse
I have a cupple JB 4.2.2 ROMs I have Posted, They are Identical except that 1 supports The gt811_ts(touchscreen) the dmard06(gsensor) and the gc0308(camera) camera support is for single camera but multiple hardwares are compatible.
The other Mod supports many touchscreen and Gsensor combos but requires compatibility scripts which I have not posted and are located in a place I cannot post at this time, I will place them on my 4shared once I get them, but for now if you want to use it you could give me an lsmod from your tab and I will try and get a compat set posted for it.
I was/am working on a CM10.1 but at present I am still trying to get the repositories downloaded. If any interest in this feel free to contact me.
I have an idea that I might be able to create a compatibility script to make an existing A10 version work Using the uboot and kernel from this Rom.
Rom supporting gt811/dmard06/gc0308
http://www.4shared.com/archive/wVZvdH5A/CookedRom.html
Rom Supporting Multiple TS/Gsensors (Patch scripts Posted on request and lsmod Provided)
http://www.4shared.com/archive/bmZdzDuG/CookedROM_JB_422_v12.html

Hello
is it possible to make a comp zip for my tablet yarvik tab07-100
here is lsmod
8188eu 621096 0 - Live 0x00000000
mc32x0 7726 0 - Live 0x00000000
YFdecrypt 22267 0 - Live 0x00000000
byd693x_ts 9491 0 - Live 0x00000000
rtl8150 10305 0 - Live 0x00000000
mcs7830 7581 0 - Live 0x00000000
qf9700 9152 0 - Live 0x00000000
asix 24601 0 - Live 0x00000000
sun5i_csi0 34044 0 - Live 0x00000000
hi704 19680 1 - Live 0x00000000
videobuf_dma_contig 6243 1 sun5i_csi0, Live 0x00000000
videobuf_core 20242 2 sun5i_csi0,videobuf_dma_contig, Live 0x00000000
cedarx 11869 0 - Live 0x00000000
mali 113719 8 - Live 0x00000000
ump 33982 21 mali, Live 0x00000000
sw_ts 18447 0 - Live 0x00000000
nand 164126 8 - Live 0x00000000

dvucino said:
Hello
is it possible to make a comp zip for my tablet yarvik tab07-100
here is lsmod
8188eu 621096 0 - Live 0x00000000
mc32x0 7726 0 - Live 0x00000000
YFdecrypt 22267 0 - Live 0x00000000
byd693x_ts 9491 0 - Live 0x00000000
rtl8150 10305 0 - Live 0x00000000
mcs7830 7581 0 - Live 0x00000000
qf9700 9152 0 - Live 0x00000000
asix 24601 0 - Live 0x00000000
sun5i_csi0 34044 0 - Live 0x00000000
hi704 19680 1 - Live 0x00000000
videobuf_dma_contig 6243 1 sun5i_csi0, Live 0x00000000
videobuf_core 20242 2 sun5i_csi0,videobuf_dma_contig, Live 0x00000000
cedarx 11869 0 - Live 0x00000000
mali 113719 8 - Live 0x00000000
ump 33982 21 mali, Live 0x00000000
sw_ts 18447 0 - Live 0x00000000
nand 164126 8 - Live 0x00000000
Click to expand...
Click to collapse
I dont Know if any of the ones that have been converted have that combo... but here is a link to all of the ones I have currently:
http://www.4shared.com/dir/snrY5LKs/Compatability.html
You should be able to test all of them... and if you find one that works I would recommend re-flash the rom then load only that one... if you do not find one that works, Load a Working Rom... make sure it is Rooted, Uberizer can do this easily.. Do a Google on it.
then with the Tab Connected via ADB type the following in a cmd Window :
Note : Open a cmd window by going to a folder where you will store a couple of files in windows explorer, right click while pressing shift key then select open command window here from the menu (ensure that the explorer window is selected but no files are clicked and the Mouse is over a blank area)
adb shell su -c "cat /dev/block/nandc > /mnt/sdcard/nandc-root.img" (Press Enter Key)
adb pull /mnt/sdcard/nandc-root.img (Press Enter Key)
adb shell su -c "cat /dev/block/nanda > /mnt/sdcard/nanda-bootloader.img" (Press Enter Key)
adb pull /mnt/sdcard/nanda-bootloader.img (Press Enter Key)
Close the command window.
Now in the folder in which you started the command window you will find 2 files called nanda-booloader.img and nandc-root.
I need those files to make you a compatibility package.
Try the ones here first though... PM me or leave a post here and I will help if I can.
Thanks

can i use same CWM from samsung galaxy ace for my tablet?if not where to get it?this is my tablet specs:
model: A10_MID
hardware:sun4i
board: crane
device:crane-hra8
brand: Softwinners
build fingerprint : softwinners/crane_hra8:4.0.3/IML74K/20120505:eng/test-keys
CPU Description: ARMv7 Processor rev 2 (v7l)
CPU_ABI : armeabi-v 7a
android version name : ICE_CREAM_SANDWICH_MR1
android version code: 4.0.3
please help me get CWM for this device and better rom if possible,i really want to upgrade.

dnbxvrfx said:
can i use same CWM from samsung galaxy ace for my tablet?if not where to get it?this is my tablet specs:
model: A10_MID
hardware:sun4i
board: crane
device:crane-hra8
brand: Softwinners
build fingerprint : softwinners/crane_hra8:4.0.3/IML74K/20120505:eng/test-keys
CPU Description: ARMv7 Processor rev 2 (v7l)
CPU_ABI : armeabi-v 7a
android version name : ICE_CREAM_SANDWICH_MR1
android version code: 4.0.3
please help me get CWM for this device and better rom if possible,i really want to upgrade.
Click to expand...
Click to collapse
This Thread should have a CWM for you... :http://forum.xda-developers.com/showthread.php?t=2189640
Follow the directions to find out which version matches your ROM... the CWM installed will depend on the ROM Partitioning scheme...
For a custom ROM the A10 device should be readily Moddable... I have a How to on that on a different forum ... but will post a similar topic here on xda soon...
In the mean time check out this thread on CM10 for the A10 : http://forum.xda-developers.com/showthread.php?t=1821398
Combine that with the methods for modding a ROM and you will have it working in no time...
I do not have an a10 I have its child the A13 both share a lot of the same attributes however so methods used to mod one should work on the other ... Once I post a thread on a sort of how to here I will let you know where it is .. or just do a search on modding your a13 Rom... the title will include those words so you will be able to find it... I may even toss a10 into it as well since the 2 are so much alike in programming..
Be aware CWM is functional but not a perfect choice for our devices.. it can also mess up your ROM if used improperly... keep in mind most of those neat CWM Flashable programs, functions etc.. are Not aimed at our devices and our partitioning is nand .. almost everything else uses the standard Linux conventions for Block devices..... this means almost any CWM Flashable that directly reads or writes or mounts a Block device will either fail to work or cuase issues on your Tab. Any of the generic ones for instance the ones for beats audio or other programs will work... look at the installer script inside the zip of any you want to try... if it mounts a Block device it probable will not work ie. mmcblk0px
our device does not use this for the Tab internal partitioning.. it uses nandx where x is a-k depending on your device, the only mmcblk devices are the external sd card and the external usb block devices.
Almost any of the ones that Do Not address these directly will install on our devices but may not work as intended.. most will require init.d which you would have to install... there is an app on the market that will do this called universal init.d also your tab must be rooted... many apps/methods for rooting exist, the one i use is Uberizer it has many functions .. you can locate it by googling Uberizer.
I hope some of this is usefull to you.
Thanks.

Would you mind if you do a patch for my tab? I'm sure that you saw this LSMOD listing, but I'd like to have a JB ROM on it even if camera support for it would be sketchy.
{
"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"
}

blakegriplingph said:
Would you mind if you do a patch for my tab? I'm sure that you saw this LSMOD listing, but I'd like to have a JB ROM on it even if camera support for it would be sketchy.
Click to expand...
Click to collapse
Is that lsmod from an Alcatel OneTouch Glory X 918N or an A13 Tab ?
If your question relates to the Alcatel OneTouch this is the wrong Thread... this Thread is about the A13 devices... Anything I told you here would relate to those devices and anything I link here would be for those as well..
If this relates to an A13 Tab your post confused me because it refers to the alcatel... in any case first try flashing the ROM I posted with Livesuite
then use the patch files from my other post one by one... if none work we can work on a patch specifically for your Tab.In most cases to make the Mods for you I need the script.bin from the bootloader.img and the boot.img from your fully functional ROM. You can get those by doing a firmware Dump using a utility... I use Uberizer I do not currently have it on my 4shared and cannot link the source location here as the site requires registration, however if you do a Google on it you will find it, or look for Techknow.me that is the source Forum but does require registration.

Lulz the stuff on your sig must've confused you. I'm referring to an A13 tablet that I own. I'll give the ROM a try some time, as I'm quite bummed at the one that I'm running right now being that it lags quite a lot.

blakegriplingph said:
Lulz the stuff on your sig must've confused you. I'm referring to an A13 tablet that I own. I'll give the ROM a try some time, as I'm quite bummed at the one that I'm running right now being that it lags quite a lot.
Click to expand...
Click to collapse
OK I see it now... it was your sig line... sorry for the confusion.... I hope the suggestions helped. The JB 4.2.2 rom works well for me... and I intend
to attempt to port a CM10.1 rom using the kernel/bootloader from this rom with modification.
There is another thread on this forum dealing with a ROM called FaastJB that would be the v1 which is based on JB 4.1.1 ... My ROM is based on
a newer Factory ROM JB 4.2.2 and is also the basis of FaastJB V2 JB 4.2.2 ... I made my ROM compatible with the Faast JB V2 comatibility patches so patches from it will work on my ROM as well... I am still working on improving my ROM and am looking into a better patching method that will not tie TS G-sensor combos together and will also support camera drivers.
here is a link to the thread http://forum.xda-developers.com/showthread.php?t=2189569
I hope this helps.

tnx fsebentley for assitence
on my yarvikTAB007-100 (allwiner A13) i have stock JB 4.1.1 and i tried to port CM10.1 from this source CyanBook_JB_4.2.2_Beta1.zip which is for allwiner a10
i did some modifications and installed successfully but i have stucked on bootloop so do you have any clue how can i catlog boot so that i can see where i stucked?

dvucino said:
tnx fsebentley for assitence
on my yarvikTAB007-100 (allwiner A13) i have stock JB 4.1.1 and i tried to port CM10.1 from this source CyanBook_JB_4.2.2_Beta1.zip which is for allwiner a10
i did some modifications and installed successfully but i have stucked on bootloop so do you have any clue how can i catlog boot so that i can see where i stucked?
Click to expand...
Click to collapse
Do you have adb connect with the bootloop ?
If so you can open a adb terminal and get whatever info you want...
outside that the only thing I can think of is to write a script to log the progress of boot and write the log to an external MicroSD.

@fsebentley
I flashed your ROM to my A13 Tab and managed to get everything to work via a modified Script.bin and certain kernel modules.
However, I have this really weird issue where it would crash within 5 mins of booting, any ideas?

fsebentley said:
Do you have adb connect with the bootloop ?
If so you can open a adb terminal and get whatever info you want...
outside that the only thing I can think of is to write a script to log the progress of boot and write the log to an external MicroSD.
Click to expand...
Click to collapse
no, adb is disconnected in bootloop

programmargorp said:
@fsebentley
I flashed your ROM to my A13 Tab and managed to get everything to work via a modified Script.bin and certain kernel modules.
However, I have this really weird issue where it would crash within 5 mins of booting, any ideas?
Click to expand...
Click to collapse
I suspect the drivers you are using may not be compatible (they must come from a ROM using a 3.0.8+ kernel) or you may not have all the necessary files to use them... what drivers and peripheral files did you use ?
let me know... and if that doesnt look like the issue we can do the following...
Send me a copy of the script.bin and I will have a go at it... I have not had any issues with crashing...but others using the FaastJB V2 version of this have had the issue... the compatibility scripts come from there, i just added the method used by Faast to a version of my ROM to accommodate those who cannot make a compatibility modification themselves...
I could almost guarantee a compatible ROM for you if you sent me a copy of the script.bin and the boot.img from your OEM Rom... to get them the simplest way is to do the following with that ROM Loaded on your Tablet:
Create a folder call it whatever you like...
In explorer browse to that folder, hold the shift key and with your mouse over a blank area in the folder right click, select open command window here from the resulting menu..
Ensure the adb files are in your path or copy them to the folder you created.
then type the following:
adb shell su -c "cat /dev/block/nandc > /mnt/sdcard/nandc-root.img" (Press enter Key)
adb pull /mnt/sdcard/nandc-root.img (Press enter Key)
adb shell su -c "cat /dev/block/nanda > /mnt/sdcard/nanda-bootloader.img" (Press enter Key)
adb pull /mnt/sdcard/nanda-bootloader.img (Press enter Key)
you will get 2 files from that ... nanda-bootloader.img and nandc-root.img those have all the info I will need...

fsebentley said:
I suspect the drivers you are using may not be compatible (they must come from a ROM using a 3.0.8+ kernel) or you may not have all the necessary files to use them... what drivers and peripheral files did you use ?
let me know... and if that doesnt look like the issue we can do the following...
Send me a copy of the script.bin and I will have a go at it... I have not had any issues with crashing...but others using the FaastJB V2 version of this have had the issue... the compatibility scripts come from there, i just added the method used by Faast to a version of my ROM to accommodate those who cannot make a compatibility modification themselves...
I could almost guarantee a compatible ROM for you if you sent me a copy of the script.bin and the boot.img from your OEM Rom... to get them the simplest way is to do the following with that ROM Loaded on your Tablet:
Create a folder call it whatever you like...
In explorer browse to that folder, hold the shift key and with your mouse over a blank area in the folder right click, select open command window here from the resulting menu..
Ensure the adb files are in your path or copy them to the folder you created.
then type the following:
adb shell su -c "cat /dev/block/nandc > /mnt/sdcard/nandc-root.img" (Press enter Key)
adb pull /mnt/sdcard/nandc-root.img (Press enter Key)
adb shell su -c "cat /dev/block/nanda > /mnt/sdcard/nanda-bootloader.img" (Press enter Key)
adb pull /mnt/sdcard/nanda-bootloader.img (Press enter Key)
you will get 2 files from that ... nanda-bootloader.img and nandc-root.img those have all the info I will need...
Click to expand...
Click to collapse
I've sent you a PM with the requested dump files. Unfortunately XDA doesn't let me post it here
Thanks in advanced.

guys can you help me in my a13 t730_mainboard_v6.3 because I install AOKP that I found in Manta Forum but touch did not work

lenovo a1000 full details of flashing ,recovery, etc

i had got lenovo a1000-g for which i spend a lot of time for searching things like recovery , rom, flashing rom, back up rom , custom rom etc
so i thought to share the results with you for saving your time
as usual here disclaimener
I OR THIS SITE IS 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 the products you find in the thread here and the links given by me before flashing it! YOU are choosing to make these modifications, and if you point the finger at us for messing up your device, we will laugh at you. Your warranty will be void if you tamper with any part of your device / software." CONTINUE AT UR OWN RISK
rooting
PROCESS 1 . FOLLOW THE LINKS GIVEN BELOW FOR LINUX
http://forum.xda-developers.com/showthread.php?t=2406916
http://forum.xda-developers.com/showpost.php?p=40188901&postcount=275
ONLINE TOOL FOR CONVERTING HEX TO DECIMAL
http://www.binaryhexconverter.com/hex-to-decimal-converter
COMPARE THE ABOVE TWO PROCESS AND PROCEED ROOT
or
PROCESS 2. USING KINGO ROOT SOFTWARE ONE CLICK ROOT AND UNROOT IN WINDOWS
http://forum.xda-developers.com/showthread.php?p=46794736
2.EXTRACTING STOCK ROM , STOCK RECOVERY, STOCK KERNEL(LINUX) for rooted devices ( FOR NON ROOTED U CAN GET BY FOLLOW THE STEPS LIKE ROOTING METHOD IN PROCESS 1 )
BE SURE THAT UR SD CARD IS HAVING 1 GB OF FREE SPACE ATLEAST
EACH STEP TAKES SOME TIME UNTILL THE NEXT PREFIX ARRIVES DONT PROCEED TO NEXT STEP , FOR EG FOR EXTRACTING SYSTEM.IMG IT MAY TAKE NEARLY 1HOUR SO BE PATIENT
STEP 1
cd /home/balu/adt-bundle-linux-x86-20130729/sdk/platform-tools
(HERE HOME BALU IS WHERE I LOCATED THE ADT BUNDLE, SO CHECK URS AND GIVE CORRECT DIRECTORY)
STEP 2
sudo ./adb devices
IT WILL SHOW LIST OF DEVICES LIKE
XXXXXXXXXXXXXXXXX DEVICE (IF NOT SHOWN CHECK IN GOOGLE)
STEP 3
adb shell
if adb is installed ok if not install it by the command displays after giving the above command
STEP 4
su
(in ur tablet super su asks permission give permission)
STEP 5
cat /proc/dumchar_info
the above command gives below results
Part_Name Size StartAddr Type MapTo
preloader 0x0000000000040000 0x0000000000000000 2 /dev/misc-sd
dsp_bl 0x00000000005c0000 0x0000000000040000 2 /dev/misc-sd
mbr 0x0000000000004000 0x0000000000000000 2 /dev/block/mmcblk0
ebr1 0x0000000000004000 0x0000000000004000 2 /dev/block/mmcblk0p1
pmt 0x0000000000400000 0x0000000000008000 2 /dev/block/mmcblk0
nvram 0x0000000000500000 0x0000000000408000 2 /dev/block/mmcblk0
seccfg 0x0000000000020000 0x0000000000908000 2 /dev/block/mmcblk0
uboot 0x0000000000060000 0x0000000000928000 2 /dev/block/mmcblk0
bootimg 0x0000000000600000 0x0000000000988000 2 /dev/block/mmcblk0
recovery 0x0000000000600000 0x0000000000f88000 2 /dev/block/mmcblk0
sec_ro 0x0000000000600000 0x0000000001588000 2 /dev/block/mmcblk0p2
misc 0x0000000000060000 0x0000000001b88000 2 /dev/block/mmcblk0
logo 0x0000000000300000 0x0000000001be8000 2 /dev/block/mmcblk0
expdb 0x0000000000200000 0x0000000001ee8000 2 /dev/block/mmcblk0
android 0x0000000028a00000 0x00000000020e8000 2 /dev/block/mmcblk0p3
cache 0x0000000017800000 0x000000002aae8000 2 /dev/block/mmcblk0p4
usrdata 0x0000000020100000 0x00000000422e8000 2 /dev/block/mmcblk0p5
fat 0x0000000083718000 0x00000000623e8000 2 /dev/block/mmcblk0p6
bmtpool 0x0000000001500000 0x00000000ff9f00a8 2 /dev/block/mmcblk0
Part_Name:smileytongue:artition name you should open;
Size:size of partition
StartAddr:smileyfrustrated:tart Address of partition;
Type:Type of partition(MTD=1,EMMC=2)
MapTo:actual device you operate
STEP 6
if above partitions are same give the same values GIVEN BELOW ,if not convert them using the hex to dec tool given abovE
FOR RECOVERY
dd if=/dev/block/mmcblk0 bs=1 skip=16285696 count=6291456 of=/mnt/sdcard2/recovery.img
WAIT AFTER EVERY STEP IN ORDET TO COMPLETE U WILL GET RESULT LIKE BELOW AFTER EVERY STEP
681574400+0 records in
681574400+0 records out
681574400 bytes transferred in 5608.838 secs (121517 bytes/sec)
[email protected]:/ #
FOR BOOT OR KERNEL
dd if=/dev/block/mmcblk0 bs=1 skip=9994240 count=6291456 of=/mnt/sdcard2/recovery.img
FOR SYSTM.IMG OR ROM
dd if=/dev/block/mmcblk0 bs=1 skip=34504704 count=681574400 of=/mnt/sdcard2/recovery.img
STEP 7
exit
exit
exit

installing custom recovery, alegro rom
installing custom recovery
follow the link to get the recovery file
http://translate.google.co.in/trans...+lenovo+a1000&client=ubuntu&hs=guw&channel=cs
back up ur whole rom by using mtk droid tools and recovery as given in links below before doing any modifications even it is small
custom rom (allegro rom
follow the link
http://translate.google.co.in/trans...ent=ubuntu&hs=3dH&channel=cs&biw=1317&bih=637
changing frame work like changing colours of notification bar etc,
follow the link to change frame work to tablet, changing colours of notification bar, transparent status bar, colour of status bar , etc
http://forum.xda-developers.com/showthread.php?t=2316070
u can also ger tablet ui by installing tablet ui module
INCREASING INTERNAL STORAGE FROM 1.5 GB TO YOUR WISH
FOLLOW THE LINK
GET A MEMORY CARD ATLEAST OR ABOVE CLASS 6
http://forum.xda-developers.com/showthread.php?t=919326
mounting ntfs formated drive i.e hard drives
for mounting hard disks without externel power , i.e connecting directly to tablet without mediator connecting of externel power usb ur tab should pocess full charging atleast above 80 percent, never connect hard disks at low battery level if connected ur tab will heated up and there is a loss of mother board , if u r connecting using externel power source tab may have less charging ,complete as fast as possible ur work , dont let the power to drain below 50 or 60 percentage
1.root is required , so root first as mentioned in previous posts]
2. download the app https://play.google.com/store/apps/details?id=net.shajul.usbotg
3. open the app and give su permission ( first time is enough)
4. connect the otg cable to the tab first with out connecting hard disk to the cable
5.connect the hard disk to otg cable ,open usbotg helper app
6. press mount
7.open fileexplorer go to the sdcard u can find usbotg drives folder
8. open it explore the hard disk
9. after completion of usage go to usbotg app and press unmount
for errors in sp flash tool visit this page
http://forum.xda-developers.com/showpost.php?p=38369102&postcount=11
back up rom using sp flash tool before modify
http://forum.xda-developers.com/showthread.php?t=2160490
sp flash tool tutorial
http://forum.xda-developers.com/showthread.php?t=1982587
swaping internal memory with sd card for increasing memory to install big games
follow the link
http://forum.xda-developers.com/showthread.php?t=1991583
here the link for modified void http://www.4shared.com/file/4gPzUILT/vold.html
here the link for stock void http://www.4shared.com/file/y9RIoWNf/vold.html
original boot animation
http://www.4shared.com/folder/p1UDAQDy/boot_animation.html
system/lib/egl
http://www.4shared.com/folder/HAzPMsqA/lib.html
for now only this if i found more i will add
thanks xda for all this
press thanks if i saved ur time

drivers for lenovo a1000
drivers and installation of drivers
drivers link http://lenovo-forums.ru/Files/OS/A390/MTK65xx_Driver.zip
installation of driver link http://lenovo-forums.ru/topic/1120-установка-драйверов-на-пк-для-смартфонов-lenovo-ideaphone/
ok google command in tab
download launcher from here i.e google now launcher from here or u can download any where
http://forum.xda-developers.com/nexus-4/themes-apps/apps-google-experience-launcher-gel-app-t2529594
update google search to latest version
install xposed installer and app settings module u can get from here
http://forum.xda-developers.com/showthread.php?t=1574401
procede the procedure strictly as shown in the thread
install app settings module from xposed installer
open app settings go to launcher app
on first then u will see some settings
change screen dpi to 1000*1600
now save
check the clear defaults of default launcher
now press home button and select google now launcher and enjoy

trouble shooting of your tablet
some people are saying that tablet is switching off and doesnt startback , if u have same problem then try this methods
1. may be ur tablet drained the battery ,charge it for a day and try to restart, (dont press volume+ button along with power button that takes to recovery )
2. if u installed a crappy app which u thought will stop ur tab to restart then press power+(vol+)+(vol-) simultaneosly , tab will restart to safemode in which no app will start , go to apps and uninstall app , and restart
3. if tab is not starting after charging then pressreset button.jpg the small button which is in the hole below the memory card using pin , this is reset button ur tab will restart ,
{
"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"
}
4. if pc does not detects in low power stats and does not restart follow this link http://mobilesupport.lenovo.com/en-us/products/a1000_tablet/faq/ht079486
5. if that too doesnt work go to service centre, or else install stock rom as mentioned above post
stock rom for a1000g indian version
http://www.4shared.com/archive/-8BdLLFzba/system.html
stock recovery
http://www.4shared.com/file/aRPtmTDoce/recovery.html
all the best

that was really nice,thanks for the resources.:good:
But i need the original boot animation of a1000,please help :fingers-crossed:

i had given 4shared link for downloading boot animation
http://forum.xda-developers.com/showpost.php?p=48368459&postcount=2

i installed "Xposed TabletUI[1.0] and its works!!!, but when i press the task manager/switcher soft key, i get a force close from system ui, any help or advice?
is there another way to enable tablet ui? or any another mod, best regards

as i said in lenovo forum download xblast module and install

nameisbalu said:
as i said in lenovo forum download xblast module and install
Click to expand...
Click to collapse
oops, i bricked my device, i am stuck on the boot logo, is there any way to push build.prop from the stcok recovey? or flash twpr from the sock recovery? best regards

how does it bricked , what procedure you followed , if u say that i may help you

Source code compilation lenovo A1000 L-F
Hello All
Did Any one proceed with the compilation of source code for lenovo A1000, my version is A1000L-F but the source code on the lenovo site ,did not compile ,Missing Makefiles.
Any Ideas??
Thanks

it is not full , it will not compile, lenovo should release new source code which compiles

Lenovo A1000 G kernel config
I would like to try compile a kernel for my A1000-G but have so far unable to locate any appropriate .config file. I have downloaded kernel source and also searched my device root and /proc directories with no luck.
I have compiled and released kernels for my Samsung Galaxy Tab 7.7, so do have some knowledge, but none of MTK etc. It appears I'll require toolchain gcc version 4.6.x-google to compile.
This is my first Lenovo (portable) device, and seems they don't fully comply with Android GPL? config is part of source, and without it unable to build

A1000lf said:
Hello All
Did Any one proceed with the compilation of source code for lenovo A1000, my version is A1000L-F but the source code on the lenovo site ,did not compile ,Missing Makefiles.
Any Ideas??
Thanks
Click to expand...
Click to collapse
Guys any ideas about A1000L-F drivers? I want to use it with adb in win7 64bit. Tried the solution in the 1st post about the drivers but did'nt work. Any tips?

Hello everyone. My tablet's micro USB has some issues since almost a month ago (It's a Lenovo A1000-F). At the beginning it stopped charging the battery so I went to technical support and it was fixed, but unfortunately I didn't notice until a week ago, when I was flashing the Stock ROM, that my PC (with Windows 7 x32) doesn't recognize my tablet (via USB). I don't know why, maybe it's software or maybe hardware.
I've tried to create a flashable zip from the stock ROM. according to this XDA's tutorials:
http://forum.xda-developers.com/showthread.php?t=2276056
http://forum.xda-developers.com/showthread.php?t=2566243
But I've failed. TWRP always show me an Error message. My other option was found a Backup and restore it from TWRP, but I only found old backups.
So my main question, can anybody help me to build a TWRP Flashable ZIP from the lastest stock ROM or Allegro Custom ROM? Or can anybody upload your own backup so I can flash it from the microSD?
Please, I really would appreciate your help
P.S: Excuse me for any grammatical or spelling error, I'm not an english native speaker.

4106
llamero said:
At the beginning it stopped charging the battery so I went to technical support and it was fixed, but unfortunately I didn't notice until a week ago, when I was flashing the Stock ROM, that my PC (with Windows 7 x32) doesn't recognize my tablet (via USB). I don't know why, maybe it's software or maybe hardware.
Click to expand...
Click to collapse
I don't know if you are referring to the not-recognized device. I have the same tablet and used pdanet http://forum.xda-developers.com/showthread.php?t=1983470 to get the adb drivers. Hope it helps.

hi, i'm tried to port jb 4.2.2 to my A1000..
it BOOT successfully, but i got serious problem. the touchscreen axes Inverted. i used OTG to connect mouse to use my touchscreen and i found sd card failed to mounting. Please Help me :crying:

Any custom rom
Sir I'm a noob to android development..
I request any expert devs to post a custom rom for lenovo a1000..
There is no hope of receiving updates from lenovo. n
Is there any expert dev out there willing to help eagerly? :angel::laugh:

BSK.Bangali.Babu9188 said:
Sir I'm a noob to android development..
I request any expert devs to post a custom rom for lenovo a1000..
There is no hope of receiving updates from lenovo. n
Is there any expert dev out there willing to help eagerly? :angel::laugh:
Click to expand...
Click to collapse
Hi,, i had some custom rom for A1000 :highfive: but since I'm new on Xda, i can't post it to development thread
If you want it, you can join our group on Facebook : [UNofficial Lounge] Lenovo Ideatab A1000
i posted to this group some custom rom from JB 4.1.2 if you can't understand indonesian language, you can ask on english now i want to make 4.2.2 working but no body help me :crying:

still no body want to help me... :crying:

NuVision TM800A510L- General Info (Root, Recovery, Unbrick)

This thread intends to be a general thread for all things about the NuVision Tablet. The aim is to help other users of this tablet to be able to root their device, get a temporary recovery and to unbrick their device. I will add the guides for the following posts below in time. This would not have been possible without help from @andrei_kr.
{
"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"
}
Technical Specifications:
Display: 8-inch IPS HD capacitive touchscreen
Resolution: 1280 x 800
Operating System: Android 4.4 Kit Kat
Processor: Intel® Atom Processor
Memory: 1GB DDR
Storage: 16GB
Micro SD Card Slot: Yes, expandable up to 64GB
Camera - Rear: 2MP
Camera - Front: 2MP
Audio: 3.5mm stereo jack with microphone
Wireless: Wi-Fi 802.11 b/g/n
Bluetooth: Bluetooth 4.0
Battery Type: Rechargeable lithium-ion
Battery Life: 6+ hours; results will vary based on usage and settings
Port: Micro USB
Sensor(s): Accelerometer

Backup/Root/Recovery
DISCLAIMER:
Rooting your phone and using custom Recoveries and ROM's have risks and may result in bricking your device, and has nothing to do with Google or the device manufacturers. In case of any mishap I am not responsible if you brick/ruin your phone in any way.
Basic computer skills are required and minimal knowledge about the phone and phone utilities also.
Make sure that whatever you do, you are doing it at your own responsibility.
How to backup of your stock ROM, install CWM and Root your device.
Requirements
ADB/Fastboot Drivers
Intel Android USB Drivers
SDcard (8GB of higher)
Temp recovery script
SuperSU
Steps
Download and unpack IntelAndroid-FBRL-07-24-2015.7z
Power off tab.
Hold Vol+ and press Power on the tab 5-10 seconds
You can see logo about 10 sec and after that DROIDBOOT will load
Connect USB cable to PC
Run launch.bat from IntelAndroid-FBRL-07-24-2015 folder
Type ACCEPT and press Enter
Type 5 and ENTER (cwm.zip)
Type T3 and ENTER (or T4)
CWM will load after 10 sec.
Select backup to external sd card.
After the backup is complete, copy it to the PC to ensure it's safe.
Follow steps 1-10 again and go to install zip from sdcard or external and select the SuperSU zip file and flash it.
NOTE: DO NOT FLASH ANY ROMS WITH THIS RECOVERY IT IS ONLY TEMPORARY. I DID NOT TEST XPOSED SO BE CAREFUL.
Credits
@andrei_kr
@social-design-concepts
@vampirefo
@Chainfire

Unbrick your Tab!
To unbrick your device all you simply have to do is go back to the CWM and restore your backup that you created earlier. If you don't have one, here is a copy of a working backup ---> Google Drive. Credits to @andrei_kr, say thanks!

How to fix touch!
If you unbricked your tablet and your touch isn't working, there is no need to worry. @andrei_kr has provided a guide on how to fix that touchscreen. Credits to him.
NOTE: If your touch is working then do not try this, it will mess up your touch!!
You probably got this touchscreen issue by flashing a different kernel with incorrect drivers.
Now your configuration is likely to differ from the native. You can view the konifig in command prompt or in the terminal :
Code:
cat /proc/gt9xx_config
(only mtk) or using the gtp_tools apk (it is in the attached file below).
It starts with the byte sequence: 0x41 0x1C 0x02 0xC0 0x03
0x41 - 65 version
0x1C 0x02 - 540 horizontal resolution
0xC0 0x03 - 960 vertical resolution
Touch must somehow work to press the button, if there is support otg, then it's easier, you can connect a mouse.
1. Install the gtp_tools_v2.6_20140126_special.apk
2. Go to the option Firmware update. Click refresh, see IC Version: 913_1020 then touch GT913 firmware and 1020.
3. Go to the option Config Settings, press read, the data were considered. Under Normal Config we have:
65 version
540 horizontal resolution
960 vertical resolution
4. Click browse, select click browse to the native config.
5. Native configuration take from your device, in the same paragraph, press the save (saves the backup config file). Native configuration for Fly IQ446 in the attached file. Press send.
6. If nothing has changed, look at the version you have and native config. Then change the version of the file in the native config in your hex.
Example: 0x41 = 65 home, a stranger 0x49 = 73 => replace the 0x41 to 0x49.

Xposed does work
Make sure you're rooted and have a working backup.
Download and install Xposed but don't run yet.
Version name:
2.6.1
Release type:
Stable (low risk of bugs)
Download:
de.robv.android.xposed.installer_v32_de4f0d.apk (711.77 KB)
Number of downloads:
11,141,690 in total · 8,610 in the last 24 hours
MD5 checksum:
de4f0dc569f96dbcc5668d40fa76040b
Uploaded on:
Tuesday, May 20, 2014 - 21:59
Changes:
- Fixed a crash with some apps (Disa, Rdio)
- Some minor UI improvements
- A few translation updates
Now either use an android terminal emulator or ADB and run these commands
1. su
2. echo 148 > /data/data/de.robv.android.xposed.installer/conf/jit_reset_offset
3. chmod 664 /data/data/de.robv.android.xposed.installer/conf/jit_reset_offset
Now you can install the Xposed framework.

max0r4axor said:
Xposed does work
Make sure you're rooted and have a working backup.
Download and install Xposed but don't run yet.
Version name:
2.6.1
Release type:
Stable (low risk of bugs)
Download:
de.robv.android.xposed.installer_v32_de4f0d.apk .
Click to expand...
Click to collapse
Thanks for report.

First want to say much thanks for this thread, it was getting frustrating trying to find a solution.
I have encountered a slight issue trying to unstuck 2 of these devices.
neither have been rooted and are stock devices.
i cant seem to get cwm to locate the backup that you supplied.
do i need to copy it to the cwm backup folder on my sd card?

Jingbadguy said:
First want to say much thanks for this thread, it was getting frustrating trying to find a solution.
I have encountered a slight issue trying to unstuck 2 of these devices.
neither have been rooted and are stock devices.
i cant seem to get cwm to locate the backup that you supplied.
do i need to copy it to the cwm backup folder on my sd card?
Click to expand...
Click to collapse
Yes you do. Copy it to your sd card. Btw if your device is stock why do you want to restore this one?

kirito9 said:
Yes you do. Copy it to your sd card. Btw if your device is stock why do you want to restore this one?
Click to expand...
Click to collapse
both are stuck in bootloader.
i was assuming i could just just reflash...
cant find a stock copy anywhere...

Jingbadguy said:
both are stuck in bootloader.
i was assuming i could just just reflash...
cant find a stock copy anywhere...
Click to expand...
Click to collapse
Oh I thought they were working. Follow the procedure above to fix.

NuVision TM101A510L
Will this method work with the NuVison TM101A510L. It seems like a lot of work to do if I'm not sure about this model. Also I have a problem with this model overheating and crashing when I play Pixel Gun 3d and it's pissing me off. I just fired off a curse filled missive to NuVision support. They don't even list this model on their registration page and it seems they have no faith in this model. I will never buy this brand again, in fact I would recommend against it to my customers. I've used Azpen tablets with no problem rooting or playing Pixel Gun 3d. I took a chance and I'm so damned sorry I did.
;angry

Thank you so much for this thread!!! I have been looking for a recovery for a few months now and cant believe I didn't find this until now...

ok so a minor problem... I cant seem to flash the recovery... Not sure if ive placed the recovery file on my sd card properly or not cause i locate a few backup files none of which have any effect. I gave up in frustration untill now. ( Currrently working on a few androids one rooting one imea changing so figured id take a crack at these devices again. THe layer of dust on these things are getting a bit thick.)

williamglick said:
Will this method work with the NuVison TM101A510L. It seems like a lot of work to do if I'm not sure about this model. Also I have a problem with this model overheating and crashing when I play Pixel Gun 3d and it's pissing me off. I just fired off a curse filled missive to NuVision support. They don't even list this model on their registration page and it seems they have no faith in this model. I will never buy this brand again, in fact I would recommend against it to my customers. I've used Azpen tablets with no problem rooting or playing Pixel Gun 3d. I took a chance and I'm so damned sorry I did.
;angry
Click to expand...
Click to collapse
I think the models numbers are specific so I can't say for certain that this will work with your tab. Try the fastboot/rooting procedure first and then maybe you can just restore the system partition only not corrupting the boot/kernel.

Unidave199 said:
Thank you so much for this thread!!! I have been looking for a recovery for a few months now and cant believe I didn't find this until now...
Click to expand...
Click to collapse
You're welcome. I waited months also before finding a working backup.

Jingbadguy said:
ok so a minor problem... I cant seem to flash the recovery... Not sure if ive placed the recovery file on my sd card properly or not cause i locate a few backup files none of which have any effect. I gave up in frustration untill now. ( Currrently working on a few androids one rooting one imea changing so figured id take a crack at these devices again. THe layer of dust on these things are getting a bit thick.)
Click to expand...
Click to collapse
You are using the fastboot method correct? If the recovery script says finished as in no errors show on the screen then it could be the device itself. What do you see?

kirito9 said:
You are using the fastboot method correct? If the recovery script says finished as in no errors show on the screen then it could be the device itself. What do you see?
Click to expand...
Click to collapse
ill let you know just as soon as i can get back to working on those devices... im prety sure if memory serves correctly, that I was getting some errors regarding unable to mound sd or ext sd. I could be wrong but thats what comes to mind.
Im up to my neck in jobs on other devices. (rooting galaxy S5, changing imei on another S5, IMEI change on a LG Stylo 2 plus, Galaxy Tab 2 system issues need to diagnose, and several screen and lcd replacments)

STUCK
ok so i have a little time to work on these....
When i run the launch.bat and get to fastboot, it goes through the instalation and everything checks ok till the very end where it says failed cause too many links.
included the screenshot so you can see.
At this point im unsure if i just need to try flashing the supersu zip like it instructs but having tried befor it had no luck.
can I not just flash twrp on this thing then su like with most root methods?

after ive flashed super su, when i go to restor the working backup i see a list of backups... including yours but when i select it i always get :
checking md5 sums...
md5 mismatch!
what now?
(i tried just flashing the boot but even that comes back with same error)
I know on other devices the recovery is an img file any the one you provide is a rar... i extracted to my desktop and was gonna try flashing with abd/fastboot but since its not an img file, im thinking it wont work...
any thoughts?
Im still unsure how to flash the recovery that u supply in the section for fixing bootloop....

Jingbadguy said:
ok so i have a little time to work on these....
When i run the launch.bat and get to fastboot, it goes through the instalation and everything checks ok till the very end where it says failed cause too many links.
included the screenshot so you can see.
At this point im unsure if i just need to try flashing the supersu zip like it instructs but having tried befor it had no luck.
can I not just flash twrp on this thing then su like with most root methods?
Click to expand...
Click to collapse
The too many links error is common for this device. Touch doesn't work with TWRP on this device so CWM is out only go. You can root and using cwm like any other root method.

SailfishOS 3 for Photon Q and siblings

Code:
* 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!
SailfishOS 3 for Photon Q
Continuation from 2.0 thread to keep most important information in first post. Thanks to vevgeniev for initial port, without it I would never buy Photon Q.
Repo with my apps is added to image. Packages can by installed via terminal:
Code:
devel-su zypper in "package name"
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"
}
Click to expand...
Click to collapse
Installation
Download and flash cm-11-20150626-SNAPSHOT-XNG3CAO1L8-moto_msm8960_jbbl.zip via twrp-3.0.2-0-asanti_c.img according to ordinary cm instruction. Use ext4 filesystem for /data partition. Boot to android and make sure everything works.
Download SailfishOS 4 image (open browser in private mode if onedrive ask you to login) and flash it over cyanogenmod. It's compressed tarball so installation may take even 10 minutes.
OTA
Read about Stop Releases and make backup using TWRP
Code:
/usr/share/sfos-moto_msm8960_jbbl-adaptation/upgrade.sh
# after reboot execute pkcon refresh to update all repositories
For any issues with upgrade.sh script download more up-to-date version, add --verbose argument or execute commands from real-upgrade.sh manually: https://build.sailfishos.org/packag...bl:4.4.0.68/sfos-moto_msm8960_jbbl-adaptation
At first boot tracker might slow down phone and eat a lot of storage. If it's too resource hungry move your media files out of device or create .nomedia empty file to exclude particular directory from tracker. Then force reset it:
Code:
tracker reset --hard
Custom Bootlogo
vevgeniev created a custom bootlogo:
Instruction how to use it
Known issues
Half screen mirror glitch occurs sometimes. Blank/unblank display fixes it
Sometimes removing files does not have any effect, i.e. free space doesn't increase and sdcard can't be unmounted. Could be easily triggered by mtp or dd usage. For sdcard access use FileZilla (SFTP).
QProcess:startDetached can hang randomly. Workaround added to fingerterm. Looks like it's bug in Qt and it is not photon q specific: https://together.jolla.com/question/202337/bug-fingerterm-terminal-freezes-after-opening-new-window
There are no 2.XG, 3.XG network indicators.
glReadPixels() return empty content in some cases. This means no screen recording, screenshots and thumbnails in browser. Workaround for screenshots added to lipstick.
All bugs at first boot are features.
FAQ
Q: How to run apk?
A: It's not android, you can't
Q: Can I switch between hardware keyboard layouts?
A: Default xkb layout switch shortcut: "shift + sym". You need to also set second keyboard layout:
dconf write /desktop/lipstick-jolla-home/layout "'us,ru'"
Click to expand...
Click to collapse
In newer releases layouts can be enabled in settings and switched via "shift + space"
Tips
Fast way to restart lipstick:
shift + tab + k
Alt + Tab like switching (if you have sailfishos-alttab-patch installed):
OK + tab
To disable volume media keys:
dconf write /apps/photonq-helper/mediaKeysEnabled 0
batt_health can cause reported battery capacity decrease which I am not sure works correctly at least on my aging battery. It's disabled since 3.3.0 in 2 places in /init.target.rc. Therefore btry will not report Aged Capacity anymore.
To use h264 (hardware accelerated) decoder in youtube set in about:config media.mediasource.webm.enabled to false
user name is still 'nemo' instead 'defaultuser' even for latest releases
Changelog
4.4.0.68
* Partially usable browser. Javascript doesn't cause crash on almost all sites like in 4.0-4.3 sfos. Tabs in landscape mode are unusable.
* Using browser probably breaks video encoding/decoding ('vid_dec_open() max number of clientslimit reached' in dmesg). Killing minimediaservice/browser usually helps.
* Disabled sailjail, and enabled start up boosters back.
* Few general sfos bugs more (see patchmanager catalogue for my patches)
4.3.0.15 - No for daily use, just required Stop Release
4.2.0.21 - No for daily use, just required Stop Release
4.1.0.24 - No for daily use, just required Stop Release
4.0.1.48
Broken browser
3.4.0.24 - Latest usable version
Fix memory leak when taking screenshot
Add workaround for remembering wlan state after reboot in airplane mode
Media keys works only in locked screen
3.3.0.16
NFC pn544 plugin added
batt_health disabled in /init.target.rc
glibc 2.30, gcc 8.3
3.1.0.12
kernel: hold volume up/down to select next/previous song
droid-hal-init: disable mpdecision due to constant cpu usage
3.0.3.9
Patch glibc for 3.0 kernel
3.0.2.8
Handle system and data partition automatically
New methods to wake up sensors
3.0.1.11
kernel: Fix crashes caused by new firewall rules
kernel: Experimental multi LUNs support
droidmedia: Fix random audio/video fail in browser
usb-moded: Mass storage was dropped in upstream. Use patched one
Click to expand...
Click to collapse
XDA:DevDB Information
SailfishOS 3 for Photon Q, ROM for the Motorola Photon Q 4G LTE
Contributors
elros34, vevgeniev
Source Code: https://github.com/elros34?utf8=✓&tab=repositories&q=msm8960&type=&language=
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.0.x
Based On: CyanogenMod
Version Information
Status: Alpha
Created 2018-11-23
Last Updated 2019-08-20

Thanks for maintaining this for our devices @elros34
I have been meaning to try Sailfish for some time on my RAZR HD (xt926) and i finally got around to it the other day only to find that it wont boot up.
As per the 2.0 thread i can flash CM11 and that will boot and work fine but once i flash Sailfish over the top it wont boot past the bootloader unlocked logo. I have tried both the xt907 and photonq zips but neither will boot.
The xt907 zip did shown some signs of something happening since the led would light up either orange or white but after leaving it for 45 mins with no other signs of life i gave up on it.
Please find attached a list of my device drivers using the following command:
Code:
ls -alR /dev
Are there any chances of this running on my xt926 ?

Thanks, so it has xt907 like partition table, you can't use photon q image. LED glowing means system is booting.
Boot to TWRP then:
Code:
rm /data/.stowaways/sailfishos/init_disable_telnet
Now reboot, connect phone to usb and telnet to it:
Code:
telnet 192.168.2.15 2323
In windows you can use putty but it's hard to copy logs from it.
Then wait a while so logs are complete and run:
Code:
dmesg
journalctl --no-page
logcat
evdev_trace -I

elros34 said:
Thanks, so it has xt907 like partition table, you can't use photon q image. LED glowing means system is booting.
Boot to TWRP then:
Code:
rm /data/.stowaways/sailfishos/init_disable_telnet
Now reboot, connect phone to usb and telnet to it:
Code:
telnet 192.168.2.15 2323
In windows you can use putty but it's hard to copy logs from it.
Then wait a while so logs are complete and run:
Code:
dmesg
journalctl --no-page
logcat
evdev_trace -I
Click to expand...
Click to collapse
Thanks @elros34
Please find attached the various logs from my xt926.
Note i'm still running Sailfish 2.1.3.7, i figured it would be easier to start with that but if needed i can re-run these on 3.0.0.8
I have no idea what most of it means for the most part but a few errors did stand out to me in particular
Code:
Dec 12 20:20:16 Sailfish systemd[1407]: Failed to start The lipstick UI.
Could this possibly explain why its not booting any further?

Lipstick fails to start because xt926 use different touchscreen driver. Change "/dev/touchscreen" to "/dev/input/event1" in /var/lib/environment/compositor/droid-hal-device.conf
Also paste output of:
Code:
udevadm info -a /dev/input/event1

elros34 said:
Lipstick fails to start because xt926 use different touchscreen driver. Change "/dev/touchscreen" to "/dev/input/event1" in /var/lib/environment/compositor/droid-hal-device.conf
Also paste output of:
Code:
udevadm info -a /dev/input/event1
Click to expand...
Click to collapse
Thanks @elros34 its working now after changing the touchscreen driver boots up fine. I'm not seeing any immediate issues but will see how i get on with it. First impressions are very good, a really nice os i'm actually surprised at how fast and fluid it is.
Here is the output of
Code:
udevadm info -a /dev/input/event1
Code:
sh-3.2# udevadm info -a /dev/input/event1
Udevadm info starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.
looking at device '/devices/i2c-3/3-0048/input/input1/event1':
KERNEL=="event1"
SUBSYSTEM=="input"
DRIVER==""
looking at parent device '/devices/i2c-3/3-0048/input/input1':
KERNELS=="input1"
SUBSYSTEMS=="input"
DRIVERS==""
ATTRS{name}=="melfas-ts"
ATTRS{phys}=="3-0048/input0"
ATTRS{properties}=="2"
ATTRS{uniq}==""
looking at parent device '/devices/i2c-3/3-0048':
KERNELS=="3-0048"
SUBSYSTEMS=="i2c"
DRIVERS=="melfas-ts"
ATTRS{drv_debug}=="Debug Setting: 0"
ATTRS{drv_reset}=="Reset: HIGH"
ATTRS{hw_irqstat}=="Interrupt line is HIGH."
ATTRS{ic_reflash}=="No firmware loading in progress."
ATTRS{irq_enabled}=="Interrupt: 1"
ATTRS{latency_debug}=="Latency Debug Setting: 0"
ATTRS{latency_times}==""
ATTRS{latency_values}=="Touch Latency Time: Average 0uS, High 0uS,0 interrupts of 0 were slow"
ATTRS{name}=="melfas-ts"
looking at parent device '/devices/i2c-3':
KERNELS=="i2c-3"
SUBSYSTEMS=="i2c"
DRIVERS==""
ATTRS{name}=="QUP I2C adapter"
I'll also see if i can convert some of the other xt925 and xt926 users for testing.

Absolutely love this - haven't had a single problem yet. Thank you so much elros34.

Could somebody check what "getprop ro.product.device" returns for xt926 or xt907 with sailfish installed?

mounting /dev/mmcblk0p39 on /data failes
Hi,
at first i would like to thank you for building SFOS3 for the Photon Q series, i bought another XT907 to finally get SF running on this pretty nice and tiny handset.
As @drkdeath5000 i stuck at the bootloader unlocked screen but with another problem as the touchscreen driver for his XT926.
I think it's a problem with the partition table here the error from /init.log
mount: mounting /dev/mmcblk0p39 on /data failed: No such file or directory
I followed the installation instructions you provided and flashed cm11, which is booting without issues. I already tried it with and without wiping dalvik/cache, with and without booting to cm11 first. So i would really appreciate your help. If i can provide some more detail just tell me.
Best regards
André

rkdeath5000 get further because he used old xt907 image, you can't use photon q image in XT907.
I have tried to support all devices in one image. I even prepared untested script to update kernel but need a nice way to distingnues between devices. No feedback so far.
Few days ago I came up with different an idea how to auto detect correct partitions in all devices but so far I am struggling with some serious issue in 3.0.2 so I am not sure when I will release it.

elros34 said:
Could somebody check what "getprop ro.product.device" returns for xt926 or xt907 with sailfish installed?
Click to expand...
Click to collapse
On my XT907 it returns scorpion_mini

Thank you for your fast response,
as you recommended Version Alpha3 is running but of course i would like to run SFOS3 So i would like to help you in any way possible.
Best regards
André

If you could test whether this image works (boots without issue and touchscreen works) then it would be great. This is image I just built with new method to detect correct partitions but without all needed patches for middleware so other bugs are not important for now.

Thank you so much! I can hardly tell you how happy you made me I always wanted i tiny handset running on SFOS and finally after i already had given up on that your rom make it happen.
I just started some basic testing on it, as i want to wait for the screen protector before starting to really use it so i'll give you a feedback on the rom later.

3.0.2.8 Released as OTA and new image probably for all moto_msm8960_jbbl devices.
Also I created new patch for Alt+Tab (OK + Tab key) like switching between windows. It's added to my obs repo.

So far the new version alpha9 installs without issues on the XT907. Right now i have just one problem, as in version alpha8 I'm not able to send text messages (SMS). I tried different sim cards from two different networks, so i think it's a problem within the ROM. How could i help you on this? Maybe collecting some logs?

What about Alpha3 or android? To boot android you don't have to flash whole system, just boot cm11 kernel via fastboot. Have you tried to set "Prefer 3G" in cellular settings?
To get most basic logs, reboot phone and try to send sms, then:
Code:
dmesg
journalctl --no-page
logcat -b radio
If it's something more serious then you will need to follow:
https://jolla.zendesk.com/hc/en-us/articles/203761078-How-to-collect-SMS-logs-

Thanks so much for 3.0.2.8 - works great. Really hope you're able to give us a 3.0.3 with the updated browser.
Don't know if you have any interest/knowledge on Maemo Leste or PMOS, but since you're the most knowledgeable person on the Photon Q, just wondered if you could hazzard a guess as to how possible it might be to get them working on this device further down the line?
Thanks again.

Yes, updated browser is tempting so I will definitely bring 3.0.3 when it will be available for ported devices.
Unfortunately I have never ported Leste or Postmarketos so I have limited knowledge here.
With Photon there are several issue like: no sim without modification and no flex cable to buy. Also we are stuck with android drivers and ancient 3.0 kernel with no chance for upstream. It means to run anything (in usable form) other than android we need libhybris. I think there are better devices with more active developers for these systems: droid 4 - have ongoing upstream efforts, Fxtec pro1 for sure will have 4.x or even 5.x kernel. That's why you will not find photon in actively supported devices in postmarketos or leste site.
- Leste use hildon-desktop (x window manager) so it would be probably not trivial to get libhybris based ui acceleration if it's possible at all. Is that os even daily usable?
- After a quick read of Postmarketos wiki looks like it support wayland based compositor like weston so it is a good sign. I was able to run libhybris accelerated weston in ubuntu chroot in sailfish. It has some touch issues but it may be because I run it nested in lipstick. From what I understand if device doesn't have upstream kernel then postmarketos requires ported halium and lxc containers. That might be not possible because of 3.0 kernel but you will never know until you try.
Take everything I said with a grain of salt and start porting. For halium you will probably need newer base than cm11. There are few important commits which are needed otherwise kernel will not work.

SMS issue could be general ofono bug: https://together.jolla.com/question...installing-3028/?answer=205366#post-id-205366
Jolla is focused on android8 base so older bases are neglected. Upstream libhybris is also broken for hybris-11 base.