Related
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've been working on this for the past week. Every exploit I've tried just hangs after a while. I've gotten much further manually. I've got unbuntu and been working using various manual methods. The thing I've noticed is that there is no system folder in root. There is a system partition in which app and bin folders exist. Later today I'm going to have time to try some more. If it weren't for these silly rules id reply to somebody elses post, but I guess reading in forums for 3 years as a registered user doesn't count. Never a need to post as I've always found something using a search. And now I've got a phones that's been out for a week and there's no info out on it so I guess I get to develop myself. Not a hard thing...just time consuming and I've got better things to do, but these pink apps gotta go and I need wired or wireless tehter again. Hopefully I have succcess later today and can post how I accomplished it.
I'll be waiting anxiously. please post updates in this thread with your progress!
Any progress on this? I have been attempting but no luck.
update on progress
jb0ne said:
I'll be waiting anxiously. please post updates in this thread with your progress!
Click to expand...
Click to collapse
ok so here's what i've learned so far from trying every method that i can find...
when you boot the phone into the pink screen (volume up and volume down plus power) there is a partition containing 1 folder with 5 files. That folder is called image and the file inside are amss.mbn, boot.img, cust.img, emmcboot.mbn, and recovery.img
The Ascend G300 is a similar phone to the G312 and there is a filed called superrecovery which changes the recovery to set ADB with root priveliges and installs SU in system. If we use the recovery from that batch file made by PauloBrien and push it to the device while in pink screen mode and then reboot into recovery the phone won't power on. You can return to the pink screen and change back to the original recovery, but you can not boot the device into recovery nor regularly. Now this gave me an idea as i'm typing. what if i change it and issue the command in ADB as ADB works during the pink screen. I'm going to try that now.
But this can't be done when in bootloader, only in pinkscreen which makes me think it's fastboot USB mode, but fastboot commands dont work uless you are in the bootloader with the huawei logo which you can only get into by issuing the reboot-bootloader command through adb. once you enter bootloader mode via ADB reboot command then you are able to issue some fastboot commands.
ok so that didn't work...basically when the files in the imge folder are changed the device won't boot into anything but the pink screen mode.
the original recovery file size is 6340KB and the one from PauloBrien is smaller at 5074KB. I'm wondering if file size has something to do with why it won't boot, however, i'm not familiar with what's inside of these files. So...as i reasearch how to build our own clockworkmod recovery i'm wondering if there's a way to change the ADB command inside from not root to root. if it's a on off selecton i'm not sure how i'd affect file size. this is where we get into the realm of knowledge that i don't possess.
so if anybody can offer up some knowledge from where i stand now... please do so.
on a side note, when running exploits, (gingerbreak, zergrush, doomsomething, psneuter, etc)...they all hang.
in linux when trying to drop a file into /system/bin the terminal read out says something about failing to cycle power, not certain what this means.
as i learn a bit more, i'll go ahead and add more...
I am hopeful to hear back from you with a successful root method for this device. I myself just purchased this phone for myself and would really love to see more development on it. Seems like a solid phone with a low entry price. Look forward to seeing what you come up with.
I'm also waiting anxiously for someone to figure this out. I just got this phone and while I really like it, there is just so much packed on this thing that I want to get rid of before I can really enjoy the phone.
I'll be watching this thread as well hopefully OP or someone else will figure out the trick to rooting this phone, like others I have used the usual methods but no luck. I've counted no less than 13 programs I'd uninstall right off the bat.
For what its worth the phone seems to not be considered part of the Ascend models of phones although they are quite similar our model is called the Unite U8680 and the Unite Q U8730 (the slider version). I've sent a email to Huawei lets see if they respond at all.
It's pretty much useless but this is all I can find on the G312 on the Huawei website:
http://www.huaweidevice.com/worldwide/technicaIndex.do?method=gotoProductSupport&productId=4086&tb=0
I'll be watching this thread as well. According to a post on another forum regarding a different Huawei model, dialling *#*# 2846579 #*#* and making some changes in the log file settings suddenly made their phones rootable for some reason. However while the same # gets you into the service mode on this phone, the log file changes made no difference.
I wonder, though, there are quite a few other options in that service mode. Maybe something in there that could be useful.
Edit: There's one menu that looks interesting, the USB one. You can change it to all sorts of modes including "Manufacture mode" whatever that is. Afraid to try it, don't want to brick my wife''s new phone
I've been playing with this menu as well and some of the USB modes do seem interesting. I was hoping this would let me find the product ID for the phone cause I found a link on the Huawei homepage to register to get an unlock code for the boot loader on this phone. If anyone is interested here is a link to the page and sadly the method they say to find the product ID doesn't work on our phone.
http://www.huaweidevice.com/worldwide/servicePolicy.do?method=toApplyUnlock
huawei says the product ID is an 8 digit number. I've been trying to dump the log files so i can scan them for some kind of 8 digit number. i've also tried all the different USB modes as well as a few other changes in the project menu that we're able to access. These haven't given me any success in changing the ownership of the folders needed to gain root access. i've not had any time to tear apart the recovery image to figure out what it's doing. but all in due time somebody will figure this out. still haven't been able to get fastboot to work properly either. am running through the usb modes on that now.
Yes please help i cannot figure out out either
builder.clockworkmod.com
so i've been working on building a recovery image for this devices using koush's site and have been able to build it, but the device won't boot into recovery yet. not sure how to fix this, gonna mess around and keep on trying. i can get it to boot back up and can get it to respond to adb commands when in the mode that just shows the android 4g logo. but i can't get into recovery. not through adb and not through using the power and volume buttons.
still working on it... any body else have anything yet?
No info on rooting this phone but Huawei just posted on their website the open source gingerbread kernel for the G312 U8680 here is a link to it:
http://www.huaweidevice.com/worldwi...=toDownloadFile&flay=software&softid=NDY3MzU=
It's been rooted!
Yep, it's a simple one too. Happy to have my wife's phone rooted Removing bloat, however, is tricky -- it's hidden in an inaccessible partition and when you erase it, it restores it on next reboot.
http://forum.xda-developers.com/showthread.php?p=31237225#post31237225
http://www.droidrzr.com/index.php/topic/4276-how-to-root-huawei-mytouch-4g/
Big thanks to mattlgroff for cracking this nut!
jb0ne said:
Yep, it's a simple one too. Happy to have my wife's phone rooted Removing bloat, however, is tricky -- it's hidden in an inaccessible partition and when you erase it, it restores it on next reboot.
http://forum.xda-developers.com/showthread.php?p=31237225#post31237225
http://www.droidrzr.com/index.php/topic/4276-how-to-root-huawei-mytouch-4g/
Big thanks to mattlgroff for cracking this nut!
Click to expand...
Click to collapse
When you install an update to one of these apps lets use the, yahoo mail on for example, it will show in the /system/app or /data/app. The problem is the apk before the update is in /cust/t-mobile/us/app which is read only and unable to be mounted as R/W and that is why Titanium backup is unable to uninstall it.
I have tried moving it and deleting it manually with no luck. I have not tried through ADB yet but may give that a try next.
jamonthis said:
When you install an update to one of these apps lets use the, yahoo mail on for example, it will show in the /system/app or /data/app. The problem is the apk before the update is in /cust/t-mobile/us/app which is read only and unable to be mounted as R/W and that is why Titanium backup is unable to uninstall it.
I have tried moving it and deleting it manually with no luck. I have not tried through ADB yet but may give that a try next.
Click to expand...
Click to collapse
If you figure it out and find anything out I would love to know about it. Where should I watch for an update in case someone does get that sorted out?
Recovery mode
There is an accessible recovery mode, at least on my querty version of the phone. You have to completely pull the battery first. Put the battery back in, hold Volume up, and then hit power. I held the power button for a couple seconds, and volume up for maybe 6-8 seconds, then started hitting volume up repeatedly. The key is to pull the battery each time you try, I think. It looks like powering off from the phone's power menu just puts it in a suspend sort of mode. (Compare boot times when rebooting, and when pulling battery)
Apparently the bootloader is locked, so not sure how useful it is yet.
For anyone with a T-Mobile MyTouch Q (Huawei U8730), I created a wiki page for it, and we should post in the New Device Forum Requests thread so we have a specific place to post info.
I just purchased a U8730 today and will definitely be figuring out how to root it at some point.
For anyone that cares here's a link in case you haven't registered at the other site.
http://j.gs/1U5q
I'm hoping we can get some development going for this phone. I just picked one up for my daughter a month ago and it's giving her memory filled messages already. It'd be great if we can get it permanently rooted and remove bloat to start... then possibly move onto Cyanogen... considering she had the horrible Comet (also by Huawei) previously and it had development for CM7. I may be taking a leap from my contract soon, but can't go to Straight Talk with her phone unless it's unlocked
A brief history:
Several weeks ago my stock Gingerbread G2's touchscreen started dying. Replacing the touchscreen didn't solve the problem. I was able to continue using it via the keyboard for a little while and, in the meantime, enabled USB Debugging (thank the stars!) while I waited for a replacement phone to arrive. I could still access some functions using the keyboard & thumbpad, although usability was limited due to the inability to back out of an application. Cue lots of battery pulls to restart at the homescreen (a pox on designers who forget one of the fundamental rules of UI: It should always be possible to go back using the current input device!).
Then the screen started a somewhat frazzled HTC image loop during boot, shortly after I started testing ADB & fastboot. Curiously it was still booting the underlying OS, as evidenced by the various chimes telling me I had messages etc, and I could still access it via ADB.
My new phone arrived (a Sony Xperia Z3 Compact. I still would prefer a proper keyboard though. Another pox on designers/manufactures who focus on marketing fads instead of functionality. I don't give a rat's arse if my phone is only 2.48291mm thick and has a screen the size of my 1st laptop. I want something small enough to use in one hand, and that has a hardware keyboard) & happily downloaded my contacts from the Borg....I mean, Google, but not notes or SMS/MMS etc. Leading to today....
I tried Sony's transfer app, but without screen viewing let alone touchscreen ability it wouldn't work (PC version, due Android version on the problem phone wasn't acceptable). Ditto problems with other root exploits. Even trying to use a recovery image on the SD card wouldn't work due to the non-root status. The recovery menu would only accept a stock image. An overriding consideration was that I didn't want to just gain root by what ever method, but I wanted to preserve my notes & sms/mms data, so fastbooting a factory image wasn't satisfactory - as far as I could tell, that would delete everything. After over a week of 0300, 0400, 0530 bed times while reading & trying the methods given in some huuuge number of XDA threads and some other websites, last night I was able to get temp root using the fre3vo exploit! Yay! At one point I had 70 threads open. It was an XDA-dev. thread that gave me the exploit though. Still couldn't do a simple Linux/Unix cp command in ADB shell to save the data but at least the file system was accessible now. Bloody frustrating!
Anyway, a bit more Googling & XDA-ing to find file locations & command formats and tonight I was able to use the ADB pull command to download the whole of the /data directory to my PC. Data saved! Even better, the Linux distro on my PC already has SQlite software to open the files. Even more yay!
I haven't tried to upload to my Xperia Z3C, but I will soon. Meanwhile my data is now available in my PC so phone access isn't as important anymore.
Some thoughts on what I went through:
Manufacturers: You do your customers a vast dis-service by making it so hard to salvage the data.
Service providers: Ditto, due to your insistance on locking down the system on the phones you sell
XDA contributers: I couldn't have done this without you, however.....it would have been easier if you *always* specified what would change/be wiped when you describe your exploit/change/recovery process. I was hesitant to try some methods due to not knowing if my data would be wiped in the process.
And after all that: Who the hell would ever want a phone that wasn't rooted? I don't even install Linux OS on my systems unless root can be gained (Ubuntu & Mint, I'm looking at you! Sudo isn't sufficient...) so I've learnt a lesson on my phone. If only I'd rooted it while it was still fully functional!
Next task? Rooting my Z3C before something goes ' bzzzzt!' on it!
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
So I bought a new phone since my old Onyx (One+ X) died (cracked screen and charging port is getting iffy). And finally I decided on this one, a cheap Chinese docomo branded one off Ebay.
I was so exited when it arrived, the UPS truck was at my gate when I got home that day, ready to leave, but the driver was nice enough to wait and give me my package then and there. Pheew.
Well, now to my, bootloader unlocking, recovery flashing, after market os installation and rooting story...
Bootloader:
The phone was supposed to be unlocked, and I guess that only meant SIM unlocked, because the service menu read "Bootloader unlock allowed: no". Damn.
A few Duckduckgo searches later, turned up I needed the "S!Unlock tool" which I found a copy off online, but username/password fields needed to be filled in, and I think I found a pirated s/n which didn't seem to work, (might have if I had tried harder).
But since it was just over £22 at https://networkunlocking.com/ I thought I could spare that on the off chance it worked. I was very surprised when it finally did, truth, I needed a few tries. And it actually did turn that service menu's pesky "no" to a thumbs-up "yes". Yay!
So now, pulling the cable, holding "volume up" and inserting cable for that blue light goodness, and running the "flashtool.exe -i 0x???? oem unlock bootloader 0x????????????" comand.
Not so fast, that doesnät work with newer flashtool versions...
Finding the old one from my Xperia Arc days and runnning it again, Yay!
(Wish I had read ahead and done that temporary root trick to rip my DRM codes off my phone first. But I don't plan to revert to stock, and I gather (might be wrong) that the DRM is only needed for stock roms, and not Lineage OS and such.)
Recovery (TWRP):
Now the problems start for real, getting into recovery was a **** and a half. Most guides for the phone says to push "volume up" multiple times during the boot-process. This turns out to be plain wrong. The actual button combo is holding "volume down" and "power" button together atleast until the screen goes blank after the unlocked bootloader warning.
Now, I wanted 17.1 on the phone and the recommended TWRp is 3.1.1 or something, and this works to install lineage fine, but don't forget to erase /data partition as I did. Stupid mistake that made wifi fail miserably, and probably a lot of other stuff, that I never tried before noticing my mistake.
However trying to get my own set of ringtones on the phone turned out to be another issue, going back into recovery when I noticed my ringtone.zip had failed. Obviously the media folder had moved since los 15.1,so no wonder right? Turns out it wasn't the only problem. TWRP 3.1.1 (or something) failed to unencrypt the root partition, so changing anything via recovery was a lie. fortunately the latest recovery, 3.5.2_9 did. So after installing that everything was rosy peaches.
Rooting:
SuperSU? forget it.
Magisk? yeah, but how? No really good step by step guide out there, except download from the github page, but what version?
A little trial and error, tried with the arm64 version and it turned out to be the right one. (Sometimes you just get it right on the first try...)
Renamed the apk to .zip put it on the phones memory, entered recovery and installed the zip, et voi effing la, Magisk root installed.
Root checker verifies root status, TitaniumBackup and RootExplorer works. Yes, my phone is playing ball.
Final notes:
This above looks simple right? In fact this was a two day process since the guides are surely lacking for this phone, a lot of trial and error, the greatesthurdle was getting into Recovery, until I found the right button combo I accidently managed to enter it once making me believe I had the right combo and something was wrong with the phone. 4 hours or so wasted trying different versions rebooting and flashing. Getting back my Viber messages turned out to be a problem to, TitaniumBackup got the messages back, but the db had references to my old images on my old phone, and probable pointed at the wrong directory so trying to send images either from gallery or take new photos crashed the app. Solution, backup the messages to my google account, uninstall and reinstall viber and restore from that backup. TitaniumBAckup is good but no magic bullet, it's a ***** that we have to rely on Google for backups though, I am allergic to the cloud, something about it makes my skin crawl.
Otherwise I like the phone, it says docomo on the back, something I can live with. The Chinese vendor even supplied one glass screen protector for the phone and a clear soft plastic case, in case I wanted some extra protection. I only wish there was a screen protector that had the same surface as the one that was on the phone in the box, that slightly opaque cloudy feel was so nice on my finger.
Can I recommend this phone? Nah, if noone writes a step by step guide that will cut down the time I spent on making this phone palpatable, I can't. But if you, like me, don't mind to tinker and don't want a phablet or spend way too much for the privilege to get a screen size you don't want, then sure. But why do we have to get them from China?
My trusty xz1 compact is slowly dieing on me and i am looking for a replacement how much did you pay for yours and is a really new or just refurbished ?
"Final notes:
This above looks simple right? In fact this was a two day process since the guides are surely lacking for this phone, a lot of trial and error, the greatesthurdle was getting into Recovery, until I found the right button combo I accidently managed to enter it once making me believe I had the right combo and something was wrong with the phone"
This Phone is in the mobile Sphere already ancient. Don't expect to get any help here or newer hot to guides.
my biggest problem is the fastboot recognition of my Windows. If this would work reliable i could better flash the phone but getting the right driver is a kind of roulette for this phone.
muhschaf said:
my biggest problem is the fastboot recognition of my Windows. If this would work reliable i could better flash the phone but getting the right driver is a kind of roulette for this phone.
Click to expand...
Click to collapse
Also had a non-connecting fastboot issue on Windows until I ran into this guide showing me it was not about a driver but an installation method:
How to install Sony Xperia Drivers Manually (Super Easy Guide)
Step-by-Step guidelines to install Sony Xperia Drivers Manually (this method can be used on Windows XP, Vista, Windows 7, Windows 8, 8.1 and Windows 10).
xperiausbdriver.com
4qx said:
Also had a non-connecting fastboot issue on Windows until I ran into this guide showing me it was not about a driver but an installation method:
How to install Sony Xperia Drivers Manually (Super Easy Guide)
Step-by-Step guidelines to install Sony Xperia Drivers Manually (this method can be used on Windows XP, Vista, Windows 7, Windows 8, 8.1 and Windows 10).
xperiausbdriver.com
Click to expand...
Click to collapse
Handy cannot boot now anyway so i would probably not able to recover anyway.
muhschaf said:
cannot boot now anyway so i would probably not able to recover anyway.
Click to expand...
Click to collapse
The phone completely refuses to boot?
Do you have recovery installed? If not, are you able to install it via fastboot on linux?
4qx said:
The phone completely refuses to boot?
Do you have recovery installed? If not, are you able to install it via fastboot on linux?
Click to expand...
Click to collapse
okay i will explain.
i had this common issue with this running out of internal space (13GB pictures i could not find, only 300MB left) and after looking into it i figured, that, due to my constant app installing and deinstalling, i had literrally thousends of little images (thumbnails, icons, you name it) that got not deintalled for whatever reason and clogged up my internal memory. So i made a Backup and decided to completly wipe and flash the newest lilac from Modpunk (18.1) and did a big Mistake here. i go into recovery and wiped EVERYTHING...without checking that recovery is untouched. then during the same session i installed the ROM and rebooted...so far all nice and dandy. Setting up the Phone, then get the newsest Gapps and then try to reboot into recovery to install them...well did i mentioned that i had wiped EVERYTHING? Well, there was no recovery anymore. Not my first rodeo i headbutt myself into the desk and spun up ADB/fastboot...only to run into the same problem i run everytime due to improper intalled driver i forgot already about. Longs story short: after some time handy refused to boot also into system.
Phone is now unbootable into any state, but Black screen fastboot over hardware buttons...
i COULD still try to make a blind fastboot flash after following the driver install instruction from above, but consider my lucky or clumsyness i will **** this up too and only waste time. and due to my current covid recovery i have not the energy nor the patient to diddle around with this sorry excuse of an absolute restrictive Phone and rather get me a S5 mini or something else that has no bootlock whatsoever and let you flash it from the very start.
i am plain running out of patient with sonys harassment.
/€: Also the constant "cannot get root" on a rooted phone is plain BS³. having permanent trouble to install adaway or use my sdcard proper is so friggin annoying that i now will search for a android version that got rid of this bull**** and will buy any phone that is suported by that ROM.
It is MY phone, and not Goolge nor the the phone company will dictade what i can or cannot install on it. i decide and i carry the risk, period. and the biggest security reason holds the phone anyway.
@muhschaf okay so it doesn't seem bricked. Pretty sure you just need to flash the recovery through fastboot and flash a ROM. Try that on Windows with the driver method; if that fails boot a Linux distro e.g. EndeavourOS, even from a USB without installing no adb/fastboot driver is necessary for Linux, it just works. You can do it.
4qx said:
@muhschaf okay so it doesn't seem bricked. Pretty sure you just need to flash the recovery through fastboot and flash a ROM. Try that on Windows with the driver method; if that fails boot a Linux distro e.g. EndeavourOS, even from a USB without installing no adb/fastboot driver is necessary for Linux, it just works. You can do it.
Click to expand...
Click to collapse
i known, the question is more "i really want that?" like i said i struggle with this phone ever since. and i realized yesterday the problem is not the phone itself, it's the bull**** of androids security architecture. Google seems to be very prone to make sure that they can shove any amount of advertisements down your throat. Given that they earn their money with ad network it doesn't surprise me.
i came to the conclusion that in reality i want to have a reliable way to install ad away on any given phone i own. i archive similar things on my desktop with Firefox and umatrix and ublock. And what can is say: Having Advertisment fee Internet is a bliss and i not care a bit about "but the free stuff" and i incrisingly fury about my inability to archive similar things on my phone i rely quite a bit.
@muhschaf I get it but you know what they say: good things require effort. But I find that once I set my Android up, I'm happy to have done it.
In regards to ads, you can actually install uBO on Android Firefox now, and many other addons also.
So i gave it a try again and the result was that it detects now a "?" under fastboot but ADB can't see anything failing sucsequently to flash recovery. i am also seemingly unable to get even into hardware fastboot anymore. But could be quite possible that the battery is already drained again. so i recharge it the night.
4qx: i was going away from uBO several years ago. Wonder that he has survived the drain after his "whitelist" decision, but it seems like.
Adaway block advertisement in apps and this is mainly the feature i wanted, see advertisment have gotten out of the browser itself into the Base/apps systems (Android, Windows) and therefore the Adblocker have to go with it. under windows i can control the System itself pretty easy and throughoutly with Powershell and package debloating scripts or regedit. under Android i haven't this option and have to rely on app like adaway. This shortcoming is pretty frustraing for an "Open Source" OS
After nearly a Year i stumble upon something windows related and now i have finally my xz1c back:
Windows USB Hubs of ANY kind (Monitor USB Hubs, Powers external USB Hubs, hell sometimes even the PCH, that is technical also a USB Hub), can and sometime WILL prevent proper lowlevel access to devices like...USB Headsets (Logitech Pro X) and Mobile Phones in fastboot mode (xz1c).
To circumvent this you have to connect the phone to a USB Port on the Back of your PC Motherboard DIRECTLY. every other Port can have an USB Hub in between that alters your write or readout and therefore failed the flashing.