Related
Hey guys,
I've searched the forum for like 5 hours or so
to find a thread that could help me solve this solution...
I've tried everything that had something to do with "dead"
in the BlueAngel and Blueangel Update etc. section
What it does:
- The screen stays black
- If I try to charge, the Red 'Charging' LED doesn't become red
unless I take the battery out of the Qtek and charge..
Then it gets red (WEIRD)
- No connection with activesync or rom update utilities
What happened:
- Rom update stopped after a few percentages...
If i try to get a new rom in it with or without cradle
with the following rom update utilities:
- BaUpgradeUt.exe:
then I get a Connection Error (101) when I try to update
- MaUpgradeUt_noID.exe:
ERROR 150: ROM UPGRADE UTILITY ERROR
(Rom Utility not designed for this device)
or "Finished" immediately (but it's not finished)
(Depends on the rom I use, and I used like 10 different roms)
Soft reset / Hard reset doesn't work,
I even tried to Hard Reset by holding the
Voice Record button + Power button + Reset button for 2 minutes
(I tried Camera + Power + Reset too) with the battery,
and I tried these without the battery...
No reaction...
If someone can help me, please do...
Thnx in advance
Maybe you can try thingds from this
http://forum.xda-developers.com/viewtopic.php?p=291989#291989
sep said:
Maybe you can try thingds from this
http://forum.xda-developers.com/viewtopic.php?p=291989#291989
Click to expand...
Click to collapse
Nope,
I've tried that too, but I don't get the USB or WCEUSB in mtty...
The COM ports don't react.
I know how to use it, because I used it like 10 times or somethin'
But I think the problem is, that I can't get in the bootloader mode
(or any other mode)... So there's no response from my Angel..
Thanks anyway..
have you tryed to remove battery, leave it without battery fo an hour or two then put the battery back and power on the device ?
this method may boot your device. If it worked go imediately in bot loader mode and reflash your favorite rom
If it does not helps maybe it is hardware problem ... and you should leave your device in service center
Tried this too
Isn't there any solution except for service center?
I want to know how I can solve this problem,
'cause it could happen again when I update the rom later.
And I know I'm not the only one with this problem.
It would help me and a lot of other BlueAngel owners..
Is it possible to make a serial connection with the bottom I/O port and issue the necessary commands with mtty? could be that there is some logic powered on the board but not enough to make the "USB" section powered up.. similar to serial a console cable on network gear etc. OR.. is there any known secrets such as a hardware debug mode initiated with certain pin(s) on the I/O connector.. such as grounding one or two.. any HTC tech documents floating around for troubleshooting?
You are not one with this problem. The same happens with me too.
Let searching for solution together.
If you want you can contact with me by icq: 190812766
Hi Guys,
I have a HTC Desire with Defrost 6.1 + Data2SD.
However whenever I connect it to USB it always has USB debugging turned on, I can turn this on and it will work as normal until I reboot then it will be turned on again and I have to turn it off.
Why does it do this? Can I turn it off permanently (not totally remove it just have it set to off by default when I reboot) ?
Many thanks,
Stephen
I'd imagine that, with most other AOSP/CM-built ROM's, it has the following set in the default.prop file (contained in the boot image with the kernel)
ro.debuggable=1
persist.service.adb.enable=1
Both helps to debug/test/check ROM's when they are made, as devs/users can get straight into adb from boot of a freshly wiped & installed ROM to either view logcat output or fiddle about to resolve & sort out any issues which may be present after each release.
Hmmm ok so how can I disable this?
I have tried editing the file in the root of the phone but it seems to get overwritten, I'm guessing this is from the file contained in the boot image like you said.
Please bear with me, I'm new to android.
Hi XDA geeks , pros and fans !
I'd like to start this new threadline concerning the freshly-appeared TCT MOVE handheld device marketed for the budget segment.As i understand it appeared in march or later this year and has quite good specs for the approx. 100 euro category.
Some details can be found on
http://alcatelonetouch.com/products/smartphones/move
Contrarily to some beliefs IT IS NOT a branded OT-908 ,rather a cosmetized one .It comes in black or silver / white , a bit heavy for it's size , and higher specs than the OT-908.
Concerning the hardware specs, i'll be coming back later with some accurate chipset and sensor details.For now
OS is Android Froyo v2.2.2.Looks like there will be official ROM updates,at the time being there is the OneTouch Upgrade v1.2 ,which downloads about 540 Mb chunked firmware files, and exits with error.
Memory is 512 Mb RAM , for user space is available about 300 Mb
512 Mb ROM flash, available to user about 160Mb.
SD card slot supports up to 32Gb MicroSD, the phone comes with a 2Gb one.
Camera is a 2.1Mpixel one.There is no secondary one,but the main camera is available for video calls,with Yahoo! Messenger i tested it myself.How to use it this way i will explain later.
GPS is amazing , if assistance software is used , the lock-on takes only seconds.
Sensors - linear acceleration sensor
- 3 axis orientation sensor
- 3 channel magnetic field sensor (digital compass)
- light sensor for illuminance detection
- optical proximity sensor , it seems not in use by operating system(or rather poorly)
Processor - 600 MHz Qualcomm ARMv6 compatible, min frequency is 122 Mhz, and deep sleep capability.Qualcomm MSM 7627 chipset
rooting ?
hi djada80.i should like to ask if you managed to root your phone ?
Yeah , it's quite simple.There are in the Android Market some free apps , i think the best which i also use is the one named Ginger Break.Just download and install it.Detailed usage info can be found here
http://forum.xda-developers.com/showthread.php?t=1044765
firmware upgrade
it seems that the branded ones somehow cannot be upgraded ! at this point i need assistance , so PLEASE , if there is anybody experienced in debranding Acatel smartphones, then YOU ARE MOST WELCOME !.I saw guys having problem with debranding T-Mobile Move , so let's DO IT !
cannot sync with windows
i cannot sync my tmobile move with windows.have a toshiba satellite c665 with win 7 .pls help !
connect phone to computer,enable usb tethering.install alcatel android manager on computer. Can be found here
alcatelonetouch.com/contents/download/T-Mobile_AndroidManager_2.2.1108.1645.rar
This should work,instead of Android Sync Manager WiFi ,the last has some issues with this phone ,do not use it.
Yahoo! messenger front camera
Contrarily to some beliefs THERE IS POSSIBLE TO MAKE VIDEO CALLS with front camera only on Froyo 2.2.It is quite simple:
1.) if you have any version of yahoo apps , remove them all
2.) install Y!Messenger v1.3.2 , the afferent audio and video plugin and
optionally Y!Mail v1.3.2
Nothing fancy with it , just works.Remember, DO NOT UPDATE from Market.
Might also check this,if it doesn't work
http://forum.xda-developers.com/showthread.php?t=1087769
remove bundled apps ?
Hi !
Is there a way to remove some of the unnecessary factory shipped apps ?
RE
Yes , there is. So the smart method vould be to remove them from phone memory , and eventually install it on SD Card , if they are (and they are) UNMOVABLE.
Or just leave them ,anyway a factory reset will restore all the shipped applications.
1.) [optional] install Android SDK with platform 2.2 , sdk tools and eventually drivers.Enable USB debugging on device.On PC launch command prompt and change directory to \Android\android-sdk\platform-tools\.Run command
adb shell pm setInstallLocation 2
This enables SDCARD installation by default.Prerequisits to have ROOT ACCESS.
2.) with RootExplorer simply delete unwanted applications from \custpack\apps\ on device.Optionally you can make backups.
3.) if you made backups , the backed-up apk can be used to be reinstalled , NOW ON SD CARD
Good luck.
RE again
A reboot of the device is required to cleanup the junk after a forced delete.Or it can be done manually , BUT USE CAUTION.
i have an alcatel move branded Cosmote Move, i like this phone very much but i`ve managed to brick it the second time, first time i bricked and took it to waranty, they reinstall the software free of charge, now it has the same simptoms (pass the carrier logo and get stuck to carrier animation) and i need to send it to waranty again. i dont manage to get it unbricked. i`ve root it with gingerbreak but this phone doesnt go to recovery mode. i`ve searched the internet and google it for hours, but nothing.
if anyone knows how to do it please tell me, in the user manual says hard reset vol - and power, get stuck whit touch buttons light up and screen black!!
thanks in advance
re Themaster
it's not a brick yet i suppose , though you didn't specify how you managed to "brick" your phone.a nice clean reflash would solve the problem , probably you deleted some system files while in root mode.again did you use root explorer or something similar ?
try a factory reset as it follows:
1.) turn off the phone
2.) press vol up and the power on and hold the buttons pressed for about 1 minute
3.) the phone boots up , android logo appears and then an animation with some sort of thrashcan or whatever
4.)wait until it finishes , then the phone shuts down automatically.power on the phone and it will be restored
Beware ,battery must be at least 70 % charged or kept in charger , NOT USB connected to PC.
This restores phone to factory state , but not all the applications from /custpack/apps
Best regards !
Useful Key Combinations
These keypress modes apply on a shut down phone
Hard Reset - reinstalls android core system from ROM , deletes user data and misconfig
key combo : vol up + power on long pressed until trashcan animation appears
Flash Mode - used for ROM update , useless momentarily
key combo: vol down + power on long pressed , black screen appears and touch buttons lit up
Root access , mount filesystem with root access ,DANGEROUS !
key combo : home + power on long pressed until boot
build environment under Ubuntu
Lately, there has been some problems setting up an Android build environment under Lucid Lynx, as i've seen many have been complained for the missing java5 jdk.
For Romanian users: seems to be a problem with the Romtelecom DNS servers , when adding Jaunty or Dapper repositories to Lucid.
Use Google DNS as alternatives 8.8.8.8 and 8.8.4.4.This works.
From what I've been able to determine. The move and 908(s) are the same hardware with with only cosmetic differences. Something is different in software, I've been unable to root my 908s with ANY tools I've found.
I was also unable to use ADB under windows. The handset apparently requires four drivers, I was only able to find three of them. I got the Alcatel tools to work, as well as tethering, but no ADB. i didn't have any such issues under Ubuntu, but without root it isn't helpful.
I could not locate a stock rom or source anywhere on the Alcatel sites, so I sent a GPL request, i'm waiting to hear back.
UPDATE
After a long night I managed to root my 908s. I'll write out the jist of it, but I was flying by the seat of my pants, fueled by caffeine and sleep depervation. DON'T consider this a HOWTO.
First off, to the best of my knowlage there is no one click solution as of yet. As I said before still missing the driver that makes ADB work in windows, and handset based solutions didn't pan out. A little reasearch showed that the OT-990 has the same chip/ram and ROM space as ours. The screen is bigger, and I don't know what board is in it, but on a hunch I figured it was close enough. So I went here: http://forum.xda-developers.com/showthread.php?t=1164391 in the hopes that some sort of combined effort in future ROM development would be possible.
Yes that's right folks its a guide to MANUALLY root you handset with ADB. So not for the faint of heart. I didn't have high hopes, as issuing ls -l on either the sqlite folder or data threw a permission denied. So blindly I tried to push psneuter, busybox and su to /data/local. I almost fell off my chair when it worked! from there I used psneuter to get ADB into root, and managed to get the su binary to /system/xbin, and Superuser into /system/app. Superuser was installed, but still no root. So I checked out Root Checker to see what was going on. There are three places that su typically lives; /system/xbin, /system/bin, and /sbin. So I tried to put su in those folders. I got it into /system/bin but sbin is mounted read-only. I did not remount any directories, as the instructions are lacking syntax (I'm a little rusty with advanced mounting commands). I think things are mapped a little differently anyway. I still did not have root on the handset, so I then fired up Superuser to see what it could see. It saw the su binary, even though it wasn't working right. Then I thought well if it can see it, then maybe it can update and fix it. Sure enough after running the update to su in Superuser, (drumroll please...) I had working root.
So that's my story so far, I'm gonna give Alcatel a week or so to reply to my request. Then we'll take it from there. (Hey it worked on Huewei right?)
If a real dev should come across this, feel free to jump in. Its a solid little phone and has the potential to work on a range of handsets.
Gratitude
Thanks snkiz for your attention ! I am pleased that someone 'heavy' noticed my efforts of dedicating this threadline to the newcomer ! Indeed a small little phone with potential , maybe in time we get it gingerbread , cupcake ( or whatever ),even wm6.5 or 7 ...
As of ADB drivers , i had ADB from the first by these steps:
1.) http://www.alcatelonetouch.com/contents/download/move upgrade 1.2 Setup.rar , package contains the drivers
Now i noticed that when i try firmware upgrade , the utility downloads about half a giga of *.bin files and then exits with 'download failed error'.
2.) installed Android SDK , platform tools and Google drivers (i am not sure if necessary), the 2.2 platform (api 8)
Under Win7 cmd in platform tools , adb shell , su and on device pops up 'unknown has been granted superuser rights' and voila! in cmd shell i have '#'.Previously installed Gingerbreak.
My device is a Cosmote Move.
Ya, no I got that file too. I think they are "consumer drivers" because like I said I got all the Alcatel tools running but on my win 7 one driver was still missing, and I have pretty good googlefu. effin hate windows, this is why. I'm by no means a "heavy" but I am comfortable in a Linux environment, that helps alot. As to you being able to get gingerbreak to work, i'd bet that comes down to carrier firmware.
---------- Post added at 06:53 PM ---------- Previous post was at 06:39 PM ----------
djada, seeing as your the op could you please re-tag the thread with the model numbers to make it easier to find? cosmote, 908, 908s, and qualcom should do.
perhaps a mod could move this thread to the android hacking forum where it can get the proper attention please?
ADB driver
Driver files are from WHATEVER.\android-sdk\extras\google\usb_driver\ , if does not install automatically , can be forced.Anyway Win$ux 7 detects ADB interface , installs some sh.t from windows update server , and you'll have an ADB interface in Device Manager (working or not).Try to force the google drivers.
On the other hand ,i'm sorry but dunno how to move the thread , maybe i should start a new one in
http://forum.xda-developers.com/forumdisplay.php?f=565&order=desc&page=552
Just looked at it and they don't have Alcatel
Mod
Just started workin on a Cyanogen build , if i manage to build at least a kernal img , maybe i can lure in the Koush guy from github.We are in need of flash , backup , recovery tools.Not as lucky as the Samsung or HTC guys ...
I recently was given an lg g3 that was supposed to have a damaged kernel, and it being my second g3 I thought I could simply flash a new kernel and OS no problem, WRONG! I worked on it for two days, I found that it has different screens with different crashes but all handled by a program called DEMIGOD CRASH HANDLER.I am able to access the recovery but nothing on there seems to do anything but reboot back to crash screen. I have been able to get win 10 to recognize the device (recent drivers already installed), but none of my linux distros will mount it! I have tried LGFlashtool, adb on CMD admin, i have tried many combinations of button pushes and battery pull/cord unplug, replug maneuvers! I am stuck! I have realized this problem may be bigger than I am able to handle, so I registered with lg and requested repair, I just hate giving up! So I am reaching out hoping someone has dealt with this problem before and knows how to take care of this mess before I raise the white flag! there isn't much back story on the device but as far as i know it has never been modified! LG Flash tool said "model check error" it seems like there is no esn imei or p# is available or downloaded. I have considered it being a case of misplaced data on the partitions, but I am not completely sure how to rearrange or reinstall the partition tables to make it work! Most of the threads that talked about this problem, the author gave up and sent it in. I also heard that this was a prevalent case in older lg models (g2, optimus, etc.) but was also a problem on nexus 6. Help please, frustrated and cold in Colorado.
still no results
To no avail I have tried everything! I have seen some changes but nothing that tells me that its fixed! I have tried qpst, but either I don't know how to run it or it wont connect properly, as a matter of fact I dont think it connects properly to any of the programs I run on it. It doesn't help that the only way the computer recognizes it is when it is on demigod mode.has anyone out there in android land had some experience or any idea of how to format the internal sd and start over from scratch?
shiftykidd said:
I recently was given an lg g3 that was supposed to have a damaged kernel, and it being my second g3 I thought I could simply flash a new kernel and OS no problem, WRONG! I worked on it for two days, I found that it has different screens with different crashes but all handled by a program called DEMIGOD CRASH HANDLER.I am able to access the recovery but nothing on there seems to do anything but reboot back to crash screen. I have been able to get win 10 to recognize the device (recent drivers already installed), but none of my linux distros will mount it! I have tried LGFlashtool, adb on CMD admin, i have tried many combinations of button pushes and battery pull/cord unplug, replug maneuvers! I am stuck! I have realized this problem may be bigger than I am able to handle, so I registered with lg and requested repair, I just hate giving up! So I am reaching out hoping someone has dealt with this problem before and knows how to take care of this mess before I raise the white flag! there isn't much back story on the device but as far as i know it has never been modified! LG Flash tool said "model check error" it seems like there is no esn imei or p# is available or downloaded. I have considered it being a case of misplaced data on the partitions, but I am not completely sure how to rearrange or reinstall the partition tables to make it work! Most of the threads that talked about this problem, the author gave up and sent it in. I also heard that this was a prevalent case in older lg models (g2, optimus, etc.) but was also a problem on nexus 6. Help please, frustrated and cold in Colorado.
Click to expand...
Click to collapse
You managed to fix it?
am facing the same issue.
Not yet i am thinking about just sending it back to lg. It's mixed up partitions, due to power surge from unauthorized power cords.
Do you have your phone rooted and with a custom recovery?
If yes,
Give this a try:
1.Enter recovery
2.Wipe data
3.Wipe cache
4.Wipe dalvic cache
5.Reboot
I've had the same problem with an LG L9 ii and this one fixed it.
So i really hope this will help. Inform me after doing this.
Greetings.
About five months ago I was able to access recovery but nothing was functional, now I cant even turn it on, if you left it on a different charger, kernal crash handler popped up half the time. Before it quit turning on the lg boot logo started going fuzzy, logic leads me to believe its a messed up Q C mother and the partitions are scrambled due to me using a non-oem charging cord and block, I also suspect the power button mounted to the back, on top of mother might have caused some hw problems. But those are just theories, it could simply be a bad battery!
I have hit dead end after dead end, after many hours, just want to get copy of text messages off this phone somehow, and then erase all data. I have spent many hours on this, my level of experience with all this is beginner/intermediate, as I'm sure you will be able to tell by the ramble below. Skip to the last paragraph **** with the asterisks to get to the important part of my inquiry. if you don't want to read about what I have tried already.
Before you suggest the obvious, replace lcd, let me say that the motherboard lcd connector is damaged beyond repair. water damage, but the phone boots normally and seems to run fine. phone calls ring and other sounds indicate the phone is able to function but no display or touch function obviously. the usb port works. Also there is no samsung account on the phone so that option to bypass screen lock does not help. Kies, smart switch, etc don't help due to the "screen lock"
ie... There is a basic swipe to unlock "lock" on the phone, so otg cable options also hit a dead end. There are workarounds to bypass other lockscreens, but no way to do the swipe over otg that I can find. And even if/once I am able to swipe to unlock over otg, there are other obstacles to get around that may not be possible (click ok, navigate to enable usb debugging). If I am wrong here and there is an obvious solution I am missing, let me know (explain in detail if you can) and I will get the hub & cable back out and try again!
Dr.phone android recovery (data recovery/damaged device option) looks like the most promising, and here I have also run into trouble. Dr phone will put the phone into download mode but then always seems to fail "flash recovery package failed" at some percentage. dr.phone downloads the recovery package (I am selecting the correct model n910v) successfully, but the percentage before flash recovery package fails changes. It hasn't made it past 85%. the dr.phone log files don't reveal anything to my untrained eye.
Before running dr.phone, adb "permission denied"...after using dr phone, however, while the phone is still powered on and in download mode, once I close dr phone, I am able to start to get somewhere with adb! adb devices shows the phone as an emulated device, and (some) adb commands start to work! I think if I just am able to find the exact location of the stock messaging log, I will be very close.
If anyone can suggest some commands to try in adb to grab just the sms log I would be very grateful!
I can run "adb backup", and have tried a few other adb commands, but none of the standard backup commands actually contain a sms log.
***Anyway, I think the best option might be to flash a custom recovery after getting the phone in download mode & adb working successfully (showing as an emulated device) with dr.phone as described above... However I have no way to tell what firmware version the phone is running (don't want to brick it or loose data), and I am really looking for specific directions on which clockworkmod or twrp recovery file to try for n910v, that will allow me to get a sms backup, and/or a recovery that will have usb debugging enabled.
Thanks for the input! sorry for the rambling post, I hope it's possible to make sense of it.. ANY help greatly appreciated!
beefriendly said:
I have hit dead end after dead end, after many hours, just want to get copy of text messages off this phone somehow, and then erase all data. I have spent many hours on this, my level of experience with all this is beginner/intermediate, as I'm sure you will be able to tell by the ramble below. Skip to the last paragraph **** with the asterisks to get to the important part of my inquiry. if you don't want to read about what I have tried already.
Before you suggest the obvious, replace lcd, let me say that the motherboard lcd connector is damaged beyond repair. water damage, but the phone boots normally and seems to run fine. phone calls ring and other sounds indicate the phone is able to function but no display or touch function obviously. the usb port works. Also there is no samsung account on the phone so that option to bypass screen lock does not help. Kies, smart switch, etc don't help due to the "screen lock"
ie... There is a basic swipe to unlock "lock" on the phone, so otg cable options also hit a dead end. There are workarounds to bypass other lockscreens, but no way to do the swipe over otg that I can find. And even if/once I am able to swipe to unlock over otg, there are other obstacles to get around that may not be possible (click ok, navigate to enable usb debugging). If I am wrong here and there is an obvious solution I am missing, let me know (explain in detail if you can) and I will get the hub & cable back out and try again!
Dr.phone android recovery (data recovery/damaged device option) looks like the most promising, and here I have also run into trouble. Dr phone will put the phone into download mode but then always seems to fail "flash recovery package failed" at some percentage. dr.phone downloads the recovery package (I am selecting the correct model n910v) successfully, but the percentage before flash recovery package fails changes. It hasn't made it past 85%. the dr.phone log files don't reveal anything to my untrained eye.
Before running dr.phone, adb "permission denied"...after using dr phone, however, while the phone is still powered on and in download mode, once I close dr phone, I am able to start to get somewhere with adb! adb devices shows the phone as an emulated device, and (some) adb commands start to work! I think if I just am able to find the exact location of the stock messaging log, I will be very close.
If anyone can suggest some commands to try in adb to grab just the sms log I would be very grateful!
I can run "adb backup", and have tried a few other adb commands, but none of the standard backup commands actually contain a sms log.
***Anyway, I think the best option might be to flash a custom recovery after getting the phone in download mode & adb working successfully (showing as an emulated device) with dr.phone as described above... However I have no way to tell what firmware version the phone is running (don't want to brick it or loose data), and I am really looking for specific directions on which clockworkmod or twrp recovery file to try for n910v, that will allow me to get a sms backup, and/or a recovery that will have usb debugging enabled.
Thanks for the input! sorry for the rambling post, I hope it's possible to make sense of it.. ANY help greatly appreciated!
Click to expand...
Click to collapse
This tool might work for you. Ive never used it myself but it looks promising. It supposed to be able to control your phone on your pc.
For the custom recovery, it should tell you what model you have when you boot into download mode but the TWRP for the note 4 has been unified so it should work either way. This link is for the most recent version. Get the .tar file if you're looking to use ODIN to install it.
Thanks for the reply! The tool you inked to requires USB debugging switched on. I was looking at it previously but didn't consider it because of this. I have USB debugging off, and the process I described with the dr phone windows application /download mode, doesn't turn usb debugging on.
Is there a way that I can flash a recovery for the note 4 that has USB debugging enabled from the start? If anyone knows please describe the process or post the link.
I think I need step by step instructions or screen shots for what to do with the Note 4 twrp recovery. I am trying to acquire a second phone so I can view the screen and know what buttons to press, but so far it is not looking like I have enough information to do sms backup from the twrp menus..on the device when I can't see the screen.
I see reference to being able to use adb commands to control the twrp recovery / backup process, but so far I haven't found anything that will help for my particular situation. If anyone knows what adb commands to use to pull the note 4 sms files , or a backup that includes them, PLEASE let me know.
thanks again