Hi, i´ve been trying to finally build Android M following Sony´s instructions. I have had several errors duringthe process, but i could solve them. Now I´m at the point that i finished building Android M (with an error, but it can be fixed), and when i want to see if Ubuntu detects my phone in fastboot mode, the list appears empty:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I think i have installed correctly the adb and fastboot drivers, because when i type adb version, it shows normally its version. It´s sstrange, because when i type lsusb, it ``recognizes´´ my phone:
I´m using Ubuntu 14.04 LTS 64-bit on virtual machine, VMWare, and my PC specs are:
-Asus A550LD
-Windows 8.1 64-bit
-Intel Core (TM) i7-4500U @ 1.80 Ghz 2.40 Ghz
-Nvidia GeForce 820M
-4GB of RAM (i know it´s low)
If someone could help me, i would really aprecciate it.
Thanks in advance.
Supercharlie25 said:
Hi, i´ve been trying to finally build Android M following Sony´s instructions. I have had several errors duringthe process, but i could solve them. Now I´m at the point that i finished building Android M (with an error, but it can be fixed), and when i want to see if Ubuntu detects my phone in fastboot mode, the list appears empty:
I think i have installed correctly the adb and fastboot drivers, because when i type adb version, it shows normally its version. It´s sstrange, because when i type lsusb, it ``recognizes´´ my phone:
I´m using Ubuntu 14.04 LTS 64-bit on virtual machine, VMWare, and my PC specs are:
-Asus A550LD
-Windows 8.1 64-bit
-Intel Core (TM) i7-4500U @ 1.80 Ghz 2.40 Ghz
-Nvidia GeForce 820M
-4GB of RAM (i know it´s low)
If someone could help me, i would really aprecciate it.
Thanks in advance.
Click to expand...
Click to collapse
You must write "sudo fastboot devices"
Not adb devices...your first pic is wrong
Sent from my D2403 using XDA Free mobile app
konstantinosj77 said:
you must write "sudo fastboot devices"
not adb devices...your first pic is wrong
sent from my d2403 using xda free mobile app
Click to expand...
Click to collapse
thousands of thanks!!! Thanks thanks thanks thanks thanks thanks!!!!:d:d:d:d:d:d:d
Related
Hi there,
I'm fairlyy knew to android. Since I updated my Phone before attempting to root, I can't root is so I cant exactly take screenshots any easier. ( I think ). My Desire HD is strugling to get recognized by the ddms Batch file. I downloaded the SDK thing. I am on Windows 7 64-Bit, So from what I know and learnt, I cant exactly install the USB drivers for ADB. I am getting an error code:
09:42:23 E/adb: Failed to get the adb version: Cannot run program "adb": CreateP
rocess error=2, The system cannot find the file specified
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Any more information you need I'll be more than happy to provide you with it. After all your trying to help
Anyone know where I went wrong? And If so I'd be grateful to be pointed in the right direction. Cheers.
Desire HD OTA 1.72.405.3
1.72 can't be rooted yet and which sdk are you using if its sdk r8 you need to take copy everything out of platform tools and move to tools folder
Sent from my leedroid v1.3a DhD via xda app
Download the zip file and extract, I face the same issue.
guys take a deep breath and follow these instruction
http://forum.xda-developers.com/showthread.php?t=502010
I use them instructions every time I format a pc, and did so on this my current 64bit windows 7 machine.
Its a whole world of pain however to get the signer for update.zip's to work 64bit machines because of the way java installs
leith51 said:
1.72 can't be rooted yet and which sdk are you using if its sdk r8 you need to take copy everything out of platform tools and move to tools folder
Sent from my leedroid v1.3a DhD via xda app
Click to expand...
Click to collapse
This solved my Problem. Thanks alot!
Have you tried using the ADB shell from windows?? Are you as frustrated as I am??
Here is the answer.
Introducing FakeShell for ADB - the ultimate terminal emulator for android power users
Features:
* The closest you will ever get to a Linux Terminal on a windows machine
* Most of the features of adb shell which were only available to linux users (like tab completion, termio support etc ) are available on windows
* Uses the core components of Konsole terminal emulator from linux. So linux users will feel right at home
* Has built in adb, so no need to install Android SDK
* Apps like vi, which were not working correctly in windows version of adb-shell due to lack of termio support, works flawlessly.
<more features to come>
Credits:
Google, for ADB source code
QTermWidget - https://github.com/qterminal/qtermwidget
mman-win32 library - http://code.google.com/p/mman-win32/
Download
Latest Version: http://d-h.st/9kB
Changelog 09/04:
* Fixed there issue where application was not starting in windows 7 and windows 8..
Installation:
Just unzip the file and run the FakeShell.exe file
Make sure that you have installed the usb driver for your phone. (If you have not installed, i recommend installing this )
Note:
This application is still in the beta version. Please use with caution.
Also, let me know the comments.
Screenshots
Start Screen
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Shell using Tab Completion
Different Color Scheme
Vi using FakeShell
reserved again...
This does not run on Windows 7
---------------------------
Microsoft Visual C++ Runtime Library
---------------------------
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
---------------------------
OK
---------------------------
Click to expand...
Click to collapse
shardul_seth said:
This does not run on Windows 7
Click to expand...
Click to collapse
same here on win7 SP1 x64
edit:
reinstalling c++ redist 2005,2008,2010,2012 did not help.
Thanks for the comments. I have identified the issue. Will fix soon..
fake_japanese_guy said:
Thanks for the comments. I have identified the issue. Will fix soon..
Click to expand...
Click to collapse
I'm waiting patiently to try this... I hate the adb shell but have to use it often. Once you get this fixed, I will be downloading it immediately
i have updated the application. The new binary is tested on windows 7 and windows 8..
please try and let me know the results..
fake_japanese_guy said:
i have updated the application. The new binary is tested on windows 7 and windows 8..
please try and let me know the results..
Click to expand...
Click to collapse
Now it works perfectly! Thank you for the great work!
How about ability to change font type & font size on the next release?
By the way, the settings dialog still shows "PTPTestApp Settings" on it's title.
Keep up the good work!
Hi amazing devs,
I’m trying to root my new device by few days. I can’t do it. So I have request about help with that. In previous firmware worked Framaroot, but I want stay in new one because there is a big difference with previous. I’m looking for solution already the third day. I was looking for at this forum&others and with using google translator the Russian and Chinese forums.
I will try to describe all:
Phone: GoClever Insignia 5 (Polish smartphone, made in China (of course))
Android: Android JB 4.2.1
Recovery: <3e> stock
CPU: MT6589T Cortex A7 (ARMv7)
GPU: PowerVR SGX544 @ 357 MHz
ROM with which I have the problem: http://www.mediafire.com/download/kz94puhk86od568/Insignia_5_718.rar
Alone Boot.img: http://www.mediafire.com/download/j6qg4zvlere8p1r/boot.img
Scatter from update.zip: http://www.mediafire.com/view/pjztjddcl89sc9b/scatter.txt
Scatter from MtkDroidTools: http://www.mediafire.com/view/c35npp25adacpp7/MT6589_Android_scatter_emmc.txt
À propos– with this tool, there is a problem:
--->>> Connect to device <<<---
ATTENTION! File /system/recovery-from-boot.p which restore factory recovery in case of phone switching on in a normal mode Is Found!
Click to expand...
Click to collapse
recovery-from-boot.p : http://www.mediafire.com/download/b99edcr5mvtdah6/recovery-from-boot.p
Block info:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
*.pk8 and *.pem: http://www.mediafire.com/download/2rfc2l5nd141i69/tosign.zip (the same – .pem check with \META-INF\com\android\otacert & .pk8 check with ‘keytool –printcert –file CERT.RSA’)
I’ve a win7pro & Ubuntu 13.10 64bit, on both installed drivers, adb, etc. I tried a lot of different tools and packages. I can prepare flashable package to CWM recovery, but to <3e> I can’t. I can’t mount system and every time ‘installation aborted’.
I don’t know what I can write more…
Maybe someone can help me and another users
Any idea?
Thanks in advance and sorry for my English
Tools which I tried:
-z4root
-Root_with_Restore_by_Bin4ry_v33
-unlockroot3
-SRSRoot
-Framaroot
-SuperOneClick v2.3.3
-1SuperOneClick233a
-fbrom1_ENU
-Any_Device_Rooter
-DooMLoRD_v4
-Cydia Impactor
-OneClickROOT 3.7
-ROOT_mtk2000
-RootTool_setup.exe
-Rootx For android
-UniversalAndroot-1.6.2-beta5
-Kingo Android ROOT
-VRoot_1.5.0.3423_Setup
-Automated Android Root Access Granter 2.00
-WMShua2.0.1
-motochopper
-some Chinese
And besides, a lot of different packages via recovery and always installation aborted
I still have that tin can. Don't know if I should be worried or what. Rooted, JB 4.2.1, modded, Carliv touch recovery 2.2 (CWM 6.0.4.4). Simply nightmarish.
I installed the android sdk and the fastboot drivers via automatic driver installing (via windows update) but whenever i try to use 'adb devices' no devices are showing, i already tried reistalling but nothing seems to work, any solutions?
Info
Syzew said:
I installed the android sdk and the fastboot drivers via automatic driver installing (via windows update) but whenever i try to use 'adb devices' no devices are showing, i already tried reistalling but nothing seems to work, any solutions?
Click to expand...
Click to collapse
and u enabled ADB in Dev Option in Android Setting?
+ you can use
Code:
adb kill-server
adb start-server
and also tell me about ur OS?
:good:
I already did, i need to fastboot, is software really important?
Sent from my D6603 using XDA Free mobile app
Geeks Empire said:
and u enabled ADB in Dev Option in Android Setting?
+ you can use
Code:
adb kill-server
adb start-server
and also tell me about ur OS?
:good:
Click to expand...
Click to collapse
Anyway, this is my os.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Info
Syzew said:
I already did, i need to fastboot, is software really important?
Sent from my D6603 using XDA Free mobile app
Click to expand...
Click to collapse
I mean OS on Computer
there is lots of problem on Windows8 for instance. but if u r Ubuntu user u can use single command to install required packages and ...
:good:
Windows XP 32 bit, sp3
Sent from my D6603 using XDA Free mobile app
How do i do that on ubuntu?
Sent from my D6603 using XDA Free mobile app
Hello,
i searching and trying now since 2months to get my library to run. Im using the free emulator NOX, MEMU, LD to test it.
Current emulator (MEMU) starting the app (ARM) now alot of other libraries (x86 and also ARM) getting loaded, but as soon the library i use mylib.so (ARM) gets loaded by the x86 process
houdini is not catching it (yes it has the correct elf magic code in it so which is used for identifying the elf and everything should go over houdini) but instead i get e_machine 40 error for
not supporting ARM on x86. Houdini is ignoring my lib.
Is it not possible to start an ARM library from a x86 process by using houdini? is it not the purpose of it, to make it work?
i placed the mylib.so in [ /system/lib/ ] is it maybe the case i need to put it in [ /system/lib/arm ] ?
What i am doing wrong.
Thank you.
AFAIK MEMU can run in 64-bit mode ( means run a 64-bit Android image ).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
xXx yYy said:
AFAIK MEMU can run in 64-bit mode ( means run a 64-bit Android image ).
Click to expand...
Click to collapse
thank you for answering but what would be different it is still the same architecture (x86 system) and ARM lib and also Android64bit is using houdini.
maybe a few more words about your thoughts would help me to understand.
LIBHOUDINI.SO ( the Intel-ARM translator what isn't freely available , means it isn't open source ) only is used on x86/x86_64 emulators like MEMU, and only if "native-bridge" is enabled in Android's build.prop file, AFAIK.
Yes, and its also working for other ARM libs but simply not for mine, and i would just like to understand. Why houdini is not starting my mylib.so from a x86 compiled process.
the normal output from houdini is:
C++:
10-05 12:08:57.325 3744 3744 D houdini : [3744] Added shared library /data/app/com.test.me/lib/arm/libqop.so for ClassLoader by Native Bridge.
but only mylib.so is not recongnized by it.