Hello to all,
I create this post, because I have a tablet CEM111 or Flytouch, which does not want to start any more after the change of the Rom, and I do not know any more what to make; thank you for your assistant.
I summarize
Tablet CEM111 ARM11 x220, screen of starting up infotmic " 0.6.1.5 ( 587 ) " when she(it) worked!
Already installed Rom:
- 1-android_2.1_2-6-32-9_infomix_Flytouch II " OK, nothing to say as about origin "
Installed with cable USB M/M and the tool Burntool_75
- 2 - then the Rom Android 2.1 v2.2-v3245 froyo " OK, work, except the webcam "
Installed with microSD and the tool win32diskimager
- 3-la Rom flash10.1-android2.2-20110416-v1001 " flash works, but problem of Ethernet, WiFi and more webcam "
Installed with microSD
- 4-Et the last Rom who in blocked the tablet Zenithink ZT-180 Android 2.2 zt-update
Installed(Settled) with the tool burntool_7.41
I installed files below:
System.pack.img
userdata.pack.img
zImage (1024x600
ZT_Bx.boot
ZT_Bx.spl " I think that his(her,its) this file which my raised by the problems? "
Results : in the started, the screen remains black, the tablet begins vibrating continues only a RESET stops it.
She no boot not any more on the SD
Function menu + power for usb does not work any more the recovery: to power + home either buttons: Home + Round Button of the face of the touch-sensitive screen + Power, nothing either
I tested all the buttons in combination with power no result.
And last attempt, defused(unsettled) the tablet and disconnected the alim. (24 hours) absolutely nothing.
Thank you in advance for all your ideas, I stall ….
Anybody cannot help me??????
On others forum, I found the same problem, but no solutions.
Thus, needs he(it) to conclude tablet from it HS or too technical ??
Guys this is an off topic about the newest kernel.
TheWhisp has done some GREAT JOB with putting effort on our device , if you haven't looked on his GitHub yet , here you are :
https://github.com/TheWhisp/android...mmit/970d42f9c57f405f0f90638ffcd07294c6a44e87
(I don't have any info about it , just wanted to share it :silly: )
blinqipa said:
Guys this is an off topic about the newest kernel.
TheWhisp has done some GREAT JOB with putting effort on our device , if you haven't looked on his GitHub yet , here you are :
https://github.com/TheWhisp/android...mmit/970d42f9c57f405f0f90638ffcd07294c6a44e87
(I don't have any info about it , just wanted to share it :silly: )
Click to expand...
Click to collapse
Thnx for the whisp and for you for publishing this i wasn't know untill now . hope they upload it soon
blinqipa said:
Guys this is an off topic about the newest kernel.
TheWhisp has done some GREAT JOB with putting effort on our device , if you haven't looked on his GitHub yet , here you are :
https://github.com/TheWhisp/android...mmit/970d42f9c57f405f0f90638ffcd07294c6a44e87
(I don't have any info about it , just wanted to share it :silly: )
Click to expand...
Click to collapse
khaledreno said:
Thnx for the whisp and for you for publishing this i wasn't know untill now . hope they upload it soon
Click to expand...
Click to collapse
there is a development build of cm 10.2
but it dosent boot
give kmsg here if anyone can
vickyg.coolest said:
there is a development build of cm 10.2
but it dosent boot
give kmsg here if anyone can
Click to expand...
Click to collapse
@TheWhisp thanks for the CM10.2 build , however :
*The ROM boots , but it takes about 5-7min. to boot
*The Buttons work (Power and Home) , wake the device , but the screen doesn't react to a touch , you touch but nothing happens
*Of course the phone is stuck on "Welcome to CyanogenMod"
*I can see the battery charging when screen is ON , but simply cannot touch anywhere
*There is a LINE on the Bottom of screen (IDK for what it is) , even on ROM booting ,even when the ROM booted , (on the "Welcome to CyanogenMod" screen (Simply , the line is permanently there )
*I tried taking logcat / last_kmsg , but adb cannot detect any device , as I think , the USB Debugging is Turned OFF .
*If you can give us something to do , I'll try
Thank you again for this perfect ROM
Edit' I took this photo from file_contexts on the ROM .zip , everything here is s0 , does that mean that adb , log , kmsg is disabled , or am I wrong :silly:
blinqipa said:
@TheWhisp thanks for the CM10.2 build , however :
*The ROM boots , but it takes about 5-7min. to boot
*The Buttons work (Power and Home) , wake the device , but the screen doesn't react to a touch , you touch but nothing happens
*Of course the phone is stuck on "Welcome to CyanogenMod"
*I can see the battery charging when screen is ON , but simply cannot touch anywhere
*There is a LINE on the Bottom of screen (IDK for what it is) , even on ROM booting ,even when the ROM booted , (on the "Welcome to CyanogenMod" screen (Simply , the line is permanently there )
*I tried taking logcat / last_kmsg , but adb cannot detect any device , as I think , the USB Debugging is Turned OFF .
*If you can give us something to do , I'll try
Thank you again for this perfect ROM
Edit' I took this photo from file_contexts on the ROM .zip , everything here is s0 , does that mean that adb , log , kmsg is disabled , or am I wrong :silly:
Click to expand...
Click to collapse
it doesnt boot for me
its stuck on gts7500 logo
edit-
ohk it did booted after 10 min
vickyg.coolest said:
there is a development build of cm 10.2
but it dosent boot
give kmsg here if anyone can
Click to expand...
Click to collapse
There's no touch response ,right? And can you get logs kmsg's?
Sent from my GT-S7500 using xda premium
blinqipa said:
There's no touch response ,right? And can you get logs kmsg's?
Sent from my GT-S7500 using xda premium
Click to expand...
Click to collapse
pull the battery from the mobile and then boot and then again pull the battery
do this 2-3 times
and then go to recovery and there do this command
Code:
adb shell
cat /proc/kmsg > /sdcard/k.txt
vickyg.coolest said:
pull the battery from the mobile and then boot and then again pull the battery
do this 2-3 times
and then go to recovery and there do this command
Code:
adb shell
cat /proc/kmsg > /sdcard/k.txt
Click to expand...
Click to collapse
submitted to cm thread :laugh:
thanks for the tip
I pulled "dropbox" "tombstones" folders from cwm backup data.ext4.tar.a .
As trying boot remove battery 3 times didnt produce a kmsg log . the only kmsg was from recoverys kernel
Tried a forth time and made a cwm backup to see if that captured anything
tombstone logs seem to be about problems with "/system/bin/mediaserver"
E AudioHardwareMSM76XXA: audioeq library open failure
I AudioHardwareMSM76XXA: failed to set audpp parameters, exiting
E AudioHardwareMSM76XXA: audioeq library open failure
W AudioFlinger: Thread AudioOut_2 cannot connect to the power manager service
E AudioFlinger: int android::load_audio_interface(const char*, audio_hw_device_t**)
couldn't load audio hw module audio.usb (No such file or directory)
I AudioFlinger: loadHwModule() error -2 loading module usb
W AudioPolicyManagerBase: could not open HW module usb
F libc : Fatal signal 11 (SIGSEGV) at 0x0000005a (code=1), thread 119 (mediaserver)
I have a Digiflip ET701 tab, which initially had android 4.2.2. It got updated to a new firmware(build number ET701_V1_20141023), and then to android 4.4.2(kernel version 3.10.20) through system update. Ever since, the wifi doesn't turn on. Whenever I try to turn on wifi, the button stays greyed out. The right pane keeps up the old message "to see available networks, turn wifi on". After any amount of time, it never turns on. The button stays (unresponsive) in the on position, and greyed out.
I restored it to factory settings, both through android settings and the recovery software(which is accessed by pressing power button+volume down), but it didn't solve the problem.
To understand what was happening, I installed adb on my laptop, and tried to look for occurrences of "wifi", "wlan", "net" etc. in the logcat outputs.
Here are some (I think) relevant results:
When I try to turn on wifi from settings, it gives:
D/WifiService( 477): setWifiEnabled: true pid=822, uid=1000
When I turn airplane mode off and then on, it shows this:
E/WifiHW ( 477): wifi_get_vendor: prop wlan.driver.vendor is not set!
And when I reboot the device, it gives this:
W/InterfaceController( 141): Warning (dlopen failed: library "/system/lib/libnetcmdiface.so" not found) while opening the net interface command library
Any help/ideas?
Thanks in advance.
Do you still use this device?
A humble request from all ET701 users, please upload TWRP/cwm backup to Dropbox or Google drive..
My device is stuck in bootloop and there's no stock firmware available anywhere
Note. For taking backup please refer to the thread in XDA for temporary recovery for Intel devices
I ported an aosp ROM (6.0.1) to my mt6580 phone following the online porting guides.everything works fine except that the screen sometimes flicker,and sometimes screen turns on 10-20 sec late after I press the power button I replaced opengles lib files,replaced zimage and vendor files but problem persists.what other files drive the display and how can I solve this problem?
What is name of your device? Do you have twrp recovery?
Sorry guys, newbie here.
Device: Micromax Canvas Hue 2 (A316)
Porting ROM: http://forum.xda-developers.com/a310/development/rom-cyanogenmod-13-micromax-a311-t3365783
Stock ROM: (Basically screwed) using: http://firmwarefile.com/micromax-a316 > Works
Recovery: Custom ported CTR. (Works but onscreen touch buttons don't.)
Achievements:
Used: http://forum.xda-developers.com/android/development/guide-how-to-port-lollipop-based-roms-t3223938
SUCCESS ! IT BOOTS!
Major Issues (known so far):
1. No softkeys/hardkeys work after booting. Tried /usr. Tried ueventd.rc in bootimg.
adb gives emojialtphysicalkeydetector: onkeyup() not mapped
2. Seems like the phone crashes when the lockscreen is triggered. Unable to confirm as lock key doesn't work.
Minor Issues (known so far)(will prioritize later):
1. Sound
2. Camera
3. IMEI invalid > Cannot test SIM
4. MAC changes every boot
What Works:
1. Touch Screen
2. Recovery
3. Radio (never tried FM tho)
4. WIFI (except the MAC issue)
5. Vibrations
Any fixes? I think I know how to fix the minor ones, I think.
Will update when possible.
nbrockz said:
Sorry guys, newbie here.
Device: Micromax Canvas Hue 2 (A316)
Porting ROM: http://forum.xda-developers.com/a310/development/rom-cyanogenmod-13-micromax-a311-t3365783
Stock ROM: (Basically screwed) using: http://firmwarefile.com/micromax-a316 > Works
Recovery: Custom ported CTR. (Works but onscreen touch buttons don't.)
Achievements:
Used: http://forum.xda-developers.com/android/development/guide-how-to-port-lollipop-based-roms-t3223938
SUCCESS ! IT BOOTS!
Major Issues (known so far):
1. No softkeys/hardkeys work after booting. Tried /usr. Tried ueventd.rc in bootimg.
adb gives emojialtphysicalkeydetector: onkeyup() not mapped
2. Seems like the phone crashes when the lockscreen is triggered. Unable to confirm as lock key doesn't work.
Minor Issues (known so far)(will prioritize later):
1. Sound
2. Camera
3. IMEI invalid > Cannot test SIM
4. MAC changes every boot
What Works:
1. Touch Screen
2. Recovery
3. Radio (never tried FM tho)
4. WIFI (except the MAC issue)
5. Vibrations
Any fixes? I think I know how to fix the minor ones, I think.
Will update when possible.
Click to expand...
Click to collapse
Hello,
XDA Assist is for newbies finding their way around XDA Developers.
Please post your thread here Miscellaneous Android Development forum, the users looking for the same could use your help.
Good luck!
Closing the thread here.
Regards
Vatsal,
Forum Moderator.