yashsingh1/xdaforums huggingface dataset:
[General Questions and Answers] techpowering:
Devices One Touch 4011x MT6575

Flashing CMW V5.5.0.4 and do nandroid backup for safety....im wrong edit some word in build.prop ,restart devices then got stuck at animations boots,im trying restore but still stuck at animations boots..btw the backup has work before..how to fix this problem in cmw?btw my devices still can go cwm..

Starting recovery on Sun Jan 1 01:24:30 2012
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (320 x 480)
ioctl(): blank: Invalid argument
ioctl(): blank: Invalid argument
CWM automade 24.07.2013 04:48:02
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /misc emmc /dev/misc (null) 0
2 /data ext4 /dev/block/mmcblk0p7 (null) 0
3 /system ext4 /dev/block/mmcblk0p5 (null) 0
4 /cache ext4 /dev/block/mmcblk0p6 (null) 0
5 /boot emmc /dev/bootimg (null) 0
6 /recovery emmc /dev/recovery (null) 0
7 /sdcard vfat /dev/block/mmcblk1p1 (null) 0
8 /sd-ext auto /dev/block/mmcblk1p2 (null) 0

W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /emmc during fstab generation!
I:Completed outputting fstab.
I:Processing arguments.
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"

ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.sys.usb.config=mass_storage,adb
ro.build.id=IMM76L
ro.build.display.id=full_MTK-eng 4.0.4 IMM76L eng.rua1.20130129.114933 test-keys
ro.build.version.incremental=eng.rua1.20130129.114933
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.4
ro.build.date=Ð’Ñ‚Ð¾ Ð¯Ð½Ð² 29 11:51:46 MSK 2013
ro.build.date.utc=0
ro.build.type=eng
ro.build.user=rua1
ro.build.host=rua1-desktop
ro.build.tags=test-keys
ro.product.model=Full Android on Emulator
ro.product.brand=Android
ro.product.name=full_MTK
ro.product.device=MTK
ro.product.board=MTK
ro.product.cpu.abi=armeabi
ro.product.manufacturer=unknown
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=unknown
ro.build.product=MTK
ro.build.description=full_MTK-eng 4.0.4 IMM76L eng.rua1.20130129.114933 test-keys
ro.build.fingerprint=Android/full_MTK/MTK:4.0.4/IMM76L/eng.rua1.20130129.114933:eng/test-keys
ro.build.characteristics=default
ro.cm.device=MTK
keyguard.no_require_sim=true
ro.com.android.dateformat=MM-dd-yyyy
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.adb.qemud=1
ro.kernel.android.checkjni=1
ro.setupwizard.mode=OPTIONAL
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.factorytest=0
ro.serialno=
ro.bootmode=unknown
ro.baseband=unknown
ro.carrier=unknown
ro.bootloader=unknown
ro.hardware=mt6575
ro.revision=1710983680
ro.emmc=0
sys.usb.vid=0BB4
init.svc.recovery=running
sys.usb.config=mass_storage,adb
service.adb.root=1
init.svc.adbd=restarting
sys.usb.state=mass_storage,adb

I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
[General Questions and Answers] techpowering:
hello someone please help
[General Questions and Answers] FSadino:
you can't go to cwm?
[General Questions and Answers] techpowering:
thank for replying...im really need help? my devices still can in cwm..did you know what cause problem about my devices? trying restore still stuck at boot animation...btw backup was working before..:( please help
[General Questions and Answers] FSadino:
1. Go to CWM

2. Do a Factory Reset

3. Clear cache and dalvik-cache

3. Restore your backup

3. Clear cache and dalvik-cache (again)

4. Reboot and wait. (may take some time to start)

If it still does not, you have to install adb shell on pc and replace the original file build.prop

I hope it was usefull

greetings
[General Questions and Answers] techpowering:
Thank for Reply i have a question can we replace the original file build.prop in update.zip?because my devices has damage usb port ( some small damage on board i/c ) so my devices cant be detected anymore at computer..it because im plug charger usb on car..:( btw i was doing factory reset,clean cache,davlik,restore ,clean again now reboot and wait..i will update how it work...uuh i hope build.prop can replace with zip file
[General Questions and Answers] techpowering:
seems not work how to replace build.prop zip file?
[General Questions and Answers] HadpeH:
i believe there is not much you can do without usb connection. you have to get your usb working again before you can fix the phone.
[General Questions and Answers] FSadino:
I agree with [MENTION=5860247]HadpeH[/MENTION], without USB we can not do anything. First fix this problem then it will be easier to help you
[General Questions and Answers] techpowering:
im request the stock build.prop for devices One Touch 4011x ( alcatel )..my usb devices cannot repair because the small i/c board has broken
[General Questions and Answers] HadpeH:
you can try to extract the file you need from the stock rom here - sourceforge(dot)net/projects/alcatel/files-

i think you can replace build.prop using updater script.
[General Questions and Answers] moonbutt74:
hey

if you have an sdcard remove it put in card reader connect card reader to pc, download aromafm to card and the build.prop

replacement put card back into device, boot into cwm, install aromafm.zip start file manager nav to proper build.prop and copy,

nav to /system and paste, long pres on newly pasted build prop and set perm to 644. reboot.

m
[General Questions and Answers] techpowering:
Thank you i will try as soon...and will update how works
[General Questions and Answers] techpowering:
Bump! already replace with new build.prop using Aroma file manager...and set to rw-r--r-- still not work..stuck at animation boots..tried nandroid restore..and reboot still stuck on animations boots what the problem of this? can someone help read this log what cause problem on my devices

Starting recovery on Sun Jan 1 01:00:47 2012
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (320 x 480)
ioctl(): blank: Invalid argument
ioctl(): blank: Invalid argument
CWM automade 24.07.2013 04:48:02
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /misc emmc /dev/misc (null) 0
2 /data ext4 /dev/block/mmcblk0p7 (null) 0
3 /system ext4 /dev/block/mmcblk0p5 (null) 0
4 /cache ext4 /dev/block/mmcblk0p6 (null) 0
5 /boot emmc /dev/bootimg (null) 0
6 /recovery emmc /dev/recovery (null) 0
7 /sdcard vfat /dev/block/mmcblk1p1 (null) 0
8 /sd-ext auto /dev/block/mmcblk1p2 (null) 0

W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /emmc during fstab generation!
I:Completed outputting fstab.
I:Processing arguments.
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"

ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.sys.usb.config=mass_storage,adb
ro.build.id=IMM76L
ro.build.display.id=full_MTK-eng 4.0.4 IMM76L eng.rua1.20130129.114933 test-keys
ro.build.version.incremental=eng.rua1.20130129.114933
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.4
ro.build.date=Вто Янв 29 11:51:46 MSK 2013
ro.build.date.utc=0
ro.build.type=eng
ro.build.user=rua1
ro.build.host=rua1-desktop
ro.build.tags=test-keys
ro.product.model=Full Android on Emulator
ro.product.brand=Android
ro.product.name=full_MTK
ro.product.device=MTK
ro.product.board=MTK
ro.product.cpu.abi=armeabi
ro.product.manufacturer=unknown
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=unknown
ro.build.product=MTK
ro.build.description=full_MTK-eng 4.0.4 IMM76L eng.rua1.20130129.114933 test-keys
ro.build.fingerprint=Android/full_MTK/MTK:4.0.4/IMM76L/eng.rua1.20130129.114933:eng/test-keys
ro.build.characteristics=default
ro.cm.device=MTK
keyguard.no_require_sim=true
ro.com.android.dateformat=MM-dd-yyyy
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.adb.qemud=1
ro.kernel.android.checkjni=1
ro.setupwizard.mode=OPTIONAL
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.factorytest=0
ro.serialno=
ro.bootmode=unknown
ro.baseband=unknown
ro.carrier=unknown
ro.bootloader=unknown
ro.hardware=mt6575
ro.revision=1710983680
ro.emmc=0
sys.usb.vid=0BB4
init.svc.recovery=running
sys.usb.config=mass_storage,adb
service.adb.root=1
init.svc.adbd=restarting
sys.usb.state=mass_storage,adb

I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
[General Questions and Answers] techpowering:
bump for help :(
[Sony Xperia S, Acro S, Ion] adek89:
Hi there. As with the few I have ske and yesterday I broke I

decided to browse xda for kernels and roms. I found a

whole bunch of kernels. some in GB ics and jb. and chose a

few interesting Roma. What kernel is the best in Romy cm

4.1 and 4.2?

Wysyłane z mojego Xperia S za pomocą Tapatalk 2
[Sony Xperia S, Acro S, Ion] Gold_Phenix:
If you want super kernel you must unlock bootloader and using fastboot flash kernel doomkernel v06 for JB.

Wysłane z mojego LT26i przy użyciu Tapatalka
[Sony Xperia S, Acro S, Ion] adek89:
im have unlock bootloader . search kerlel for good battey live
[Android Q&A, Help & Troubleshooting] delltech1:
Guys maybe you can help me, my phone is behaving very strange. It is a Tianhe H920+ with 4gb ROM, identical with Mlais MX58 Pro, Auxus Nuclea N1 and others.

Roms for Auxus Nuclea N1 are working perfectly, but, first of all i have problems with the rear camera, i am not getting any error messages, but just only the front camera is working and the switch camera option is missing, after i install some third party camera app it freezes.

Phone was suited with Tianhe ROM, build march 2014, for sure i made backup. What i have found out, when i flash the original BOOT.IMG, camera works fine, but the old kernel will be installed. I have unpacked it, checked also init, init.project files, they are totally the same, no change there, just the Zimage differs / Kernel.

All works fine but i have the old known wake up bug, i must remove the battery and start the phone again. I was searching everywhere, but i couldnt find any fix for it. I know flash firmware, but like i already mentioned rear camera is not working with other kernels, all other functions are ok. Is there any possible solution? Framework fix or something please?

Till now i have tried almost 10-15 roms, from MX58 Pro, Star, Tianhe, but non of them is suited with a kernel with working rear camera :crying:. Thank you very much.
[Android Q&A, Help & Troubleshooting] ryan2nice:
Heyy delltech1.. I've also facing similar issue...have you found any solution to your problem?
[Android Q&A, Help & Troubleshooting] Eleichstetten:
Tianhe H920+ Wake up issue

Hello DellTech1.

I am facing the same issue with the pnone not waking up after it has gone to deep sleep.

I found out, that it only happens, when WLAN (WIFI) is switched on.

(For tests I had no SIM installed and the phone was reset to factory setup)

When WIFI is switched off it starts up as it should.

Could this issue be related to baseband?

Do you have more informations now?

Additional infos:

It showed, that the wakeup issue occured, when the phone was logged into a Network with WPA2 security.

Because I did not believe this, I did trials on 3 different networks with 3 different routers.

In each case, the phone did not wake up, if WLAN was active and the security settings in the router have been WAP2.

If I changed the settings in the routers to WPA, wake up was fine.

Anyway: an active WLAN connection (either WPA2 or WPA) does not allow the phone to go into Deep Sleep.

(according to CPU SPY at WPA, and my fingers touching the warm back of the phone with WPA2)
[Android Q&A, Help & Troubleshooting] delltech1:
Tianhe

Hi,

i have flashed the "new rom" from pandawillforum. But be carefull, after flashing i wasnt able to start the phone, it softbricked the phone, but i was able to unbrick it. Before you will flash it, take the PRELOADER file from a good known working rom and replace it. Then try to flash it, it will work now.

I have used the phone without the simcard, Wifi was enabled, Gmail synchronization also, i have used the phone for about 5 days, wakeup issue didnt reappeared. Camera is working also. Just search in the forum for H920 and you will find many topics, but i can also post the link here:

4GB version:

http://androidxda.com/flash-stock-rom-using-smart-phone-flash-tool

8GB version:

http://www.pandawillforum.com/soft/12J36_S131WT_H920+_8P64_20140329_JB2V1.2.V02.MP.EN.rar

Like i said, use a good working preloader, you can take it also from an older ROM, doesnt matter.
[Android Q&A, Help & Troubleshooting] Eleichstetten:
Could you recommend a good preloader?
[Android Q&A, Help & Troubleshooting] delltech1:
Tianhe

Yes you can use one from this ROM, i was using it everytime:

http://www.needrom.com/mobile/tianhe-star-h920-2/
[Android Q&A, Help & Troubleshooting] validoican:
Camera still not working

I have tryed all roms from needrom and pandavile..nothing.
[Android Q&A, Help & Troubleshooting] Eleichstetten:
Now I tried the ROM that was offered in the Pandawill Forum for 8GB Version.

This ROM does include a working preloader (maybe has been changed?)

Anyway, when I flash this ROM, it works, but problems persist.

No change.
[Android Q&A, Help & Troubleshooting] Hanyxx:
CWM 8gb ver. ROM

HI guys, Please could some one upload the 8GB rom flashable with CWM recovery I can not do it with flashtools my usb conenctor is damaged...

PLEASE HELP and save my ass I am starting to be despaired with this phone :(

THANK YOU for any support and have a nice day :)
[Android Q&A, Help & Troubleshooting] Hanyxx:
Modified version of Note 3 yasuu ROM.

Just for the case that someone do not know how to replace boot.img (kernel 2014) and replace camera drivers I am uploading modified version of Note 3 yasuu ROM.

No flickering screen,No back camera bug or green camera,No unlock freez yet.

Only bad thing is battery usage, maybe because my USB connector is damaged.I do not know try it out and share your results about the baterry please.

LINK (CWM zip file) :

mediafire.com/download/v3n65fltmwka52z/ROM_NOTE3_Kernel_2014_H920+.+Cam.Drivers.HanyxX.zip
[Android Q&A, Help & Troubleshooting] Eleichstetten:
Gave it a try.

Installation did work, but I missed keyboard.

Did install keyboard from APK.

Then tried to root. Framaroot said "ok", but Superuser did not work.

Tried to install Superuser by CWM method, but that ended in a startup-loop.

Had to Flash back Stock-ROM to recover.

Maybe try tomorrow again.
[Android Q&A, Help & Troubleshooting] Eleichstetten:
OK, Gave it a second try. This time without trying to root.

Well, the wake up issue does not exist anymore.

Unfortunately, it´s just because the phone does not start to Deep Sleep anymore.

It reduces processor rate, but does not start Deep Sleep.

That´s the cause for higher battery consumption.

By the way:

- The package of my phone is not labeled "Tianhe", but "CGC".

- Both cameras did work with this Rom.

- My phone has 8GB of memory and stock ROM is 03/2014
[Android Q&A, Help & Troubleshooting] validoican:
Hello

I have tried your rom but camera still not working for me...i have 8GB version.

---------- Post added at 01:03 PM ---------- Previous post was at 12:59 PM ----------

Hello,

I have tried the last modified version of this rom but the camera is not working for me..not frontal one,not the back one..i have tried all roms from needrom(tianhe,mlais or star...)..no one is proper to have working camera...any advice
[Android Q&A, Help & Troubleshooting] Eleichstetten:
I did reset my phone with this firmware from Pandawill Forum (8GB version). The firmware is for H920+ that are produced after March 2014.

It seems, that there has been a change of camera hardware.

http://www.pandawillforum.com/showthread.php?25569-ROM-ROM-for-Tianhe-H920&p=136188&viewfull=1#post136188

This seems to be real stock.

If your phone is produced after March, 2014 and this firmware does not solve the problem, there is a high probability that it is defective.
[Android Q&A, Help & Troubleshooting] validoican:
How to find out?

How can i find out what is the date manufacture of my phone?
[Android Q&A, Help & Troubleshooting] iliev2:
about Tianhe H920+ turbo /pandawill/, rear camera problems

Hello,

After trying all firmwares from panda and needrom i find that there is a hardware problem. BAD CONNECTION between board and camera conector! :rolleyes:

Try to open the phone and press firmly camera connector to the board. Then put above something thick 1 mm (non metal) to hold the connector in same position.

It's worked fine for me. Good luck to you!:good:
[Android Q&A, Help & Troubleshooting] drskam:
How do you unbrick your phone... ??? Please advise !!!
[Android Q&A, Help & Troubleshooting] sabh:
can anyone give update.zip file of su binary i had deleted my su binary by update.zip unroot method but now i can't get the root even i have superuser icon
[Android Q&A, Help & Troubleshooting] aditya.kamble:
Root your device again by update.zip Superuser apk only manages permission . It cant do anything without su binary

So root your device again to install su binary
[G2 Q&A, Help & Troubleshooting] Energy-X:
Hey all , im trying to enter fastboot mode for flashing custom recovery img but it wont go.. need instructions (im on 4.2.2 stock)

all i cant find is people stuck in it and similar posts but no real answer. i wonder if there is even a fastboot in G2 and modern LG phones at all
[G2 Q&A, Help & Troubleshooting] basti2909:
Try to use this for recovery

http://xdaforums.com/showthread.php?t=2633941

There is no classic fastboot mode on g2 as u maybe known from other device
[Moto X Android Development] Dusty tears:
full name:TeamWin Recovery Project

TWRP official began support motox,very good!

model:

msm8960dt devices with unlocked bootloader.

- moto x

- moto droid mini/ultra/maxx

Download Link:

http://techerrata.com/browse/twrp2/ghost
[Moto X Android Development] Dusty tears:
I have some questions for the motox, CM source can't be used..who can share the devicetree source code for the msm8960dt??Thanks!!
[Moto X Android Development] herny66:
openrecovery-twrp-2.7.1.1-ghost.img

this file is for the moto x http://teamw.in/project/twrp2/234
[Moto X Android Development] Dusty tears:
thanks for the reminder...
[Moto X Android Development] slydog43:
will this work with the Verizon developer edition?

edit: I flashed it and it seems ok, thanks
[Moto X Android Development] t1.8matt:
Yes, recoveries are not carrier dependant. That's great to be getting official support from another great dev for this phone.
[Moto X Android Development] jeikei4life:
4.4.3 support

Will this work for 4.4.3?
[Moto X Android Development] kenosis:
Yes, it works.
[Moto X Android Development] jeikei4life:
Hmm. And you don't need to unlock your bootloader to flash this, do you?

Edit: im wondering if I could just flash this, install super su through it, and root my phone that way (without unlocking the bootloader).
[Moto X Android Development] rebretz000:
You must have an unlocked bootloader. Otherwise there would be no reason to ever complain about not having an unlocked bootloader. There would be no reason for root exploits or safestrap.
[Moto X Android Development] jakereeves31:
Preach it.
[Moto X Android Development] rebretz000:
Wasn't trying to be ****. Was typing reply in a work meeting. Trying to get as much info in with as little words as possible
[Moto X Android Development] rebretz000:
Updated TWRP for Ghost

http://techerrata.com/browse/twrp2/ghost
[Moto X Android Development] CsR0501:
Can you use it? It's stable? :confused:

Sorry but my pc is dead and i can't restore nothing for 1 or 2 weeks :crying:
[Moto X Android Development] rebretz000:
Its the official so I'd assume it's stable. I haven't been able to fastboot it in yet.
[Moto X Android Development] ConstantHero:
Flashed it through the TWRP manager app all seems fine and OTG does work. 2.8.0.1 from 2.7.1.1
[Moto X Android Development] CsR0501:
OK... I flashed it... Everything looks fine... I'm gonna play with it a little more! [emoji6]
[Moto X Android Development] Travisdroidx2:
Been stable for me so far.

Update:

Made a back up

Flashed a aosp ROM

Restored my back up of eclipse.

Everything worked perfect with 2.8.0.1
[Moto X Android Development] Jexx11:
Does anyone else notice that since version 2.7.1.1 and even this new 2.8.0.1 it seems to take a long time for the recovery to load? It seems to hang on the TWRP boot image for about 30 to 45 seconds before it loads the recovery. This was never the case on the old 2.6 versions for me.
[Moto X Android Development] Travisdroidx2:
Yes, noticed the same thing.
[Moto X Android Development] electron.hTcpico:
The twrp2.8 recovery still is not suitable for xt1052 the Indian variant ..! The Roms are still not optimized for them it still gets error while flashing any ROM even the new cm11 Roms
[Moto X Android Development] maxou88:
You can't flash the new CM11 with TWRP 2.8 ? like 2.7.1.1 ?

I have xt1052 too.

But i have see CM11 have add the xt1052 .

Sorry i use slimroms
[Moto X Android Development] smohanv:
Thanks for sharing.

Flased on my moto x xt1052 (European version). Works fine..
[Moto X Android Development] orky87:
The latest one takes 10 seconds + to load during a twrp splash. Xt1052
[Xperia Z Q&A, Help & Troubleshooting] androidtweaker1:
Guys need your help on this one.

I flashed CM11, Kitkat 4.4.3 yesterday.

Device is Xperia Z C6603 bootloader unlocked and rooted

I enabled USB debugging but when i connect to PC its not giving me RSA key prompt.

Can anyone help me out?

Edit:Have resolved the issue creds [MENTION=2452820]kingvortex[/MENTION]
[Xperia Z Q&A, Help & Troubleshooting] sathiel:
Hi there

First of all this is not the right forum to ask questions like that.

I would start with checking drivers on your PC, the ones from flashtool - fastboot, flashmode and Xperia Z specific are ok. The prompt may appear only when debug mode is being used by your PC so if you are not doing anything that requires it (like flashing recovery etc.) it can never appear.
[Xperia Z Q&A, Help & Troubleshooting] androidtweaker1:
I had asked the question in Xperia Z Android development the moderator moved the question here.

I am aware about posting in right forum! :rolleyes:
[Moto G General] hrazib:
We are very excited about 4.4.3 update in the air rolling, but i found in Motorola forum, after updating in 4.4.3 user experiencing a major problem of dropping signal in WiFi rapidly. GPS satellite tracking is very slow around 10 min. of spotting satellite & sometimes battery draining quickly than before. So anyone knows any known bugs about 4.4.3, please share....
[Moto G General] diecast:
Omg are you kidding me???i dont know what to say i will w8 till i get mine(europe) and then report

Στάλθηκε από το XT1032 μου χρησιμοποιώντας Tapatalk
[Moto G General] hrazib:
yes this is true, you can find it posted by several users in Motorola forum...

https://forums.motorola.com/hives/3ba9b2429c/summary
[Moto G General] knizmi:
Those issues apparently only affect only a minority of users. For me the battery is better than on 4.4.2, I don´t have any wifi drops and GPS is as fast and accurate as ever.
[Moto G General] vkk178:
People are so crazy to get the update . I hope Motorola is looking into this and even though it affects few devices , rolls out another patch or patch further updates .
[Moto G General] bozzykid:
Also, if you previously disabled the messaging app and use hangouts, hangouts will be unusable after the update (constant crashes). This happens on the Moto G and Moto X 4.4.3 updates. The only fix is reset all your app preferences and keep the messaging app enabled.
[Moto G General] hrazib:
Thanks buddy, this info will help us.
[Moto G General] hrazib:
I found this should be the proper way of upgrading os probably it will help escaping bugs also.

perform a factory data reset before and after an OS upgrade. And wipe the cache a few times, too.

This advice have been taken from Motorola forum.

https://forums.motorola.com/posts/7c4f0aa2c4
[Moto G General] hrazib:
It is true, but we should aware of this for taking update decision, isn't it?