Develop Bugs

Rooting Arc on MacOSX

I'm an absolute noob and I therefore had to look on a couple of forums to understand what I was about to do. I don't wanna take any credit for this "guide" since I'm merely trying to summarize what I found in a noobish way.
Install the Android SDK
(Credit to Cyanogen Wiki)
Download the latest version of Android SDK : Android SDK
Extract the archive of Android SDK and copy/move it to the location of your choice (I moved it to my Desktop and renamed it android-sdk-macosx)
You need to indicate the path of platform-tools and tools to your terminal, so open your terminal.
Edit the ~/.profile file
Code:
open -e ~/.profile
And add at the end of the file :
Code:
export PATH=Users/Username/Desktop/android-sdk-macosx/platform-tools:Users/Username/Desktop/android-sdk-macosx/tools:$PATH
Save your new .profile (save a version on MacOSX Lion) and go back to terminal.
Load the new .profile :
Code:
source .profile
Execute the following command in the terminal and download the components and updates.
Code:
android
Now, you got a functional Android SDK and can work with ADB.
Test the connection between your Arc and the adb server
Enable USB debugging (Settings>Applications>Development);
Plug your USB cable to the phone and then the USB cable to your Mac;
Open a terminal and execute the following command :
Code:
adb devices
Your device should be listed.
Root your Arc
(Credit to DooMLoRD)
Go to this thread DooMLoRD's Easy Rooting Toolkit [v1.0](zergRush Exploit) and read the warnings.
Download this file DooMLoRD_v1_ROOT-zergRush-busybox-su.zip and this file runme.sh.zip listed on his thread.
Now, extract both on your Desktop and copy "runme.sh" in this folder "DooMLoRD_v1_ROOT-zergRush-busybox-su".
Before you start, check everything mentioned on DooMLoRD's thread (USB debugging, Unknown Sources, How-To connect the phone)
Once your Arc is connected to your Mac, open a terminal.
Move yourself to the folder "DooMLoRD_v1_ROOT-zergRush-busybox-su" (assuming the folder is on your Desktop)
Code:
cd /Users/Username/Desktop/DooMLoRD_v1_ROOT-zergRush-busybox-su
Execute the runme.sh script
Code:
sh runme.sh
And after your phone has rebooted, it should be rooted.
Like I said, in the beginning, I don't take any credit for this. All credit goes to DooMLoRD and all the people credited in his thread.
I wanna thank him again since it is the first method I tried and it worked on my Arc 2.3.3 Build .368

Thanks
Thanks for such precise condensation. :good:

Could you please upload the sh file somewhere?
The dropbox upload does not exist anymore.
laual said:
I'm an absolute noob and I therefore had to look on a couple of forums to understand what I was about to do. I don't wanna take any credit for this "guide" since I'm merely trying to summarize what I found in a noobish way.
Install the Android SDK
(Credit to Cyanogen Wiki)
Download the latest version of Android SDK : Android SDK
Extract the archive of Android SDK and copy/move it to the location of your choice (I moved it to my Desktop and renamed it android-sdk-macosx)
You need to indicate the path of platform-tools and tools to your terminal, so open your terminal.
Edit the ~/.profile file
Code:
open -e ~/.profile
And add at the end of the file :
Code:
export PATH=Users/Username/Desktop/android-sdk-macosx/platform-tools:Users/Username/Desktop/android-sdk-macosx/tools:$PATH
Save your new .profile (save a version on MacOSX Lion) and go back to terminal.
Load the new .profile :
Code:
source .profile
Execute the following command in the terminal and download the components and updates.
Code:
android
Now, you got a functional Android SDK and can work with ADB.
Test the connection between your Arc and the adb server
Enable USB debugging (Settings>Applications>Development);
Plug your USB cable to the phone and then the USB cable to your Mac;
Open a terminal and execute the following command :
Code:
adb devices
Your device should be listed.
Root your Arc
(Credit to DooMLoRD)
Go to this thread DooMLoRD's Easy Rooting Toolkit [v1.0](zergRush Exploit) and read the warnings.
Download this file DooMLoRD_v1_ROOT-zergRush-busybox-su.zip and this file runme.sh.zip listed on his thread.
Now, extract both on your Desktop and copy "runme.sh" in this folder "DooMLoRD_v1_ROOT-zergRush-busybox-su".
Before you start, check everything mentioned on DooMLoRD's thread (USB debugging, Unknown Sources, How-To connect the phone)
Once your Arc is connected to your Mac, open a terminal.
Move yourself to the folder "DooMLoRD_v1_ROOT-zergRush-busybox-su" (assuming the folder is on your Desktop)
Code:
cd /Users/Username/Desktop/DooMLoRD_v1_ROOT-zergRush-busybox-su
Execute the runme.sh script
Code:
sh runme.sh
And after your phone has rebooted, it should be rooted.
Like I said, in the beginning, I don't take any credit for this. All credit goes to DooMLoRD and all the people credited in his thread.
I wanna thank him again since it is the first method I tried and it worked on my Arc 2.3.3 Build .368
Click to expand...
Click to collapse

Weird error-normal-error-normal sequence on rooting using doomlord easyroot.

Hello, I'm new here, bought my Xperia Arc S rooted with 4.0.4 and .587 kernel, xda has helped me a lot but unfortunately I haven't been able to install Jelly Bean, no matter how hard I try... so, basically my problem is
After lots of failed tries to install JB, I ended up with a bricked phone, so I had to flash an official .ftf with its kernel, all okay. Now the bad thins is, I lost my root, and the phone came rooted so I have no idea how to do this, I've followed these steps:
-Install ADB drivers
-Flash/Downgrade kernel
-Debug mode checked
-Unknown sources checked.
then, when I try to do the root, this is what happens (this is the log of cmd).
Code:
---------------------------------------------------------------
Easy rooting toolkit (v4.0)
created by DooMLoRD
using exploit zergRush (Revolutionary Team)
Credits go to all those involved in making this possible!
---------------------------------------------------------------
[*] This script will:
(1) root ur device using latest zergRush exploit (21 Nov)
(2) install Busybox (1.18.4)
(3) install SU files (binary: 3.0.3 and apk: 3.0.6)
(4) some checks for free space, tmp directory
(will remove Google Maps if required)
[*] Before u begin:
(1) make sure u have installed adb drivers for ur device
(2) enable "USB DEBUGGING"
from (Menu\Settings\Applications\Development)
(3) enable "UNKNOWN SOURCES"
from (Menu\Settings\Applications)
(4) [OPTIONAL] increase screen timeout to 10 minutes
(5) connect USB cable to PHONE and then connect to PC
(6) skip "PC Companion Software" prompt on device
---------------------------------------------------------------
CONFIRM ALL THE ABOVE THEN
Press any key to continue . . .
--- STARTING ----
--- WAITING FOR DEVICE
error: more than one device and emulator
--- creating temporary directory
error: more than one device and emulator
--- cleaning
error: more than one device and emulator
--- pushing zergRush
error: more than one device and emulator
--- correcting permissions
error: more than one device and emulator
--- executing zergRush
error: device offline
--- WAITING FOR DEVICE TO RECONNECT
if it gets stuck over here for a long time then try:
disconnect usb cable and reconnect it
toggle "USB DEBUGGING" (first disable it then enable it)
error: more than one device and emulator
--- DEVICE FOUND
--- pushing busybox
error: device not found
--- correcting permissions
error: device not found
--- remounting /system
error: device not found
--- checking free space on /system
error: device offline
error: device not found
error: device not found
--- copying busybox to /system/xbin/
error: device not found
--- correcting ownership
error: device not found
--- correcting permissions
error: device not found
--- installing busybox
error: device not found
error: device not found
--- pushing SU binary
error: device not found
--- correcting ownership
error: device not found
--- correcting permissions
error: device not found
--- correcting symlinks
error: device not found
error: device not found
--- pushing Superuser app
error: device not found
--- cleaning
error: device not found
--- rebooting
error: device not found
ALL DONE!!!
Press any key to continue . . .
of course, that "ALL DONE!" is a lie and useless, and I'm still unrooted, no reboots, anything. I hope you guys can help!
My phone has unlocked bootloader, it's a SonyEricsson Xperia Arc S Lt18i with ICS 4.0.4 and kernel 4.1.B.0.587
Thanks in advance ^w^

Keep trying - root arc s 587

As i can see of your log, it dont detect phone. Probably driver issue
Try this
Download thr superuser.zip from their site. Put it on sd card.
Now find a stockbased kernel with cwm.
Hotboot it
Fastbootcode
Fastboot boot yourkernelnamehere.img
Phone will boot itself
Repeatly press volume down on blue led
In cwm install the superuser.zip
Reboot
Sent from my LT15i using xda premium

TheHaso said:
As i can see of your log, it dont detect phone. Probably driver issue
Try this
Download thr superuser.zip from their site. Put it on sd card.
Now find a stockbased kernel with cwm.
Hotboot it
Fastbootcode
Fastboot boot yourkernelnamehere.img
Phone will boot itself
Repeatly press volume down on blue led
In cwm install the superuser.zip
Reboot
Sent from my LT15i using xda premium
Click to expand...
Click to collapse
I couldn't find a superuser.zip anywhere.. and, how am I supposted to hotboot? o3o, thanks in advance D:

AW: Weird error-normal-error-normal sequence on rooting using doomlord easyroot.
To avoid the driver problem, deinstall pc companion, get the latest Version of flashtool and install the drivers that comes with it. Then try again.
Sent from my LT15i using xda app-developers app

Code:
error: more than one device and emulator
Maybe you should concentrate on one device connected at a time... or disable your emulator!
Follow the other hints and use the search function...
There are some bullet proof how-to's already which will guide you to root, if you read them :angel:
Regards,
scholbert

scholbert said:
Code:
error: more than one device and emulator
Maybe you should concentrate on one device connected at a time... or disable your emulator!
Follow the other hints and use the search function...
There are some bullet proof how-to's already which will guide you to root, if you read them :angel:
Regards,
scholbert
Click to expand...
Click to collapse
Actually the problem is somewhere on my PC, I was able to flash custom ROM and root using my grandpa's laptop.. :l I've already tried having ONLY my phone connected to my pc, still no result or anything.

Did you closed flashtool before starting the rootkit?

HUGE BUMP, but someone may be facing this problem too so.. I want to report my solution
I was using a 3.0 USB port all the time, all I had to do is use a normal USB port and it worked.

[Q] Root failure - remount permission denied

Hello,
I tried to search for the solution for this but wasn't able to, so posting as a new thread..
I have been trying Root_with_Restore_Bin4ry_v33 to root my Kindle Fire 8.9 HD running firmware 8.4.8, and had no success in rooting the device.
The error I am getting is
"mount: permission denied (are you root?)"
which comes out from the command
./stuff/adb shell "/data/local/tmp/busybox mount -o remount,rw /system"
I ran the command with sudo (in my Mac) but it did not help. It seems that only very few people had the same problem but did not find the solution.
FYI, I did turn on (1) USB debugging and (2) Allow installtion from unknown sources before trying to root the device.
Here are possible suspects:
(1) I wonder this problem is specific to Mac OS X. I replaced ./stuff/adb to the version from adt-bundle-mac-x86_64-20131030. Did anyone have success in rooting KFHD in Mac OS X?
(2) I wonder this problem is specific to newer version of firmware (8.4.8), but I do see people without having problems with this version.
(3) Any other possible reasons?
Thanks for your help - H
(Below is the full message from running 'sudo sh RunMe.sh')
==================================================================================================
= This script will root your Android phone with adb restore function =
= Script by Bin4ry(converted to shell by jamcswain) (thanks to Goroh_kun and tkymgr for the idea) =
= Idea for Tablet S from Fi01_IS01 =
= (14.12.2013) v33 =
===================================================================================================
Device type:
0) Xperia Root by cubeundcube
1) Normal
2) Special (for example: Sony Tablet S, Medion Lifetab)
3) New Xperia Root by Goroh_kun
G) Google Glass Root (thx to Saurik for the ab file)
x) Unroot
Make a choice:
Please enter a valid number(1 to x):
1
Checking if I should run in Normal Mode or special Sony Mode
Please connect your device with USB-Debugging enabled now
Waiting for device to shop up, if nothing happens please check if Windows ADB-drivers are installed correctly!
remote object '/system/app/Backup-Restore.apk' does not exist
remote object '/system/bin/ric' does not exist
Normal Mode enabled!
Pushing busybox....
5309 KB/s (1165484 bytes in 0.214s)
Pushing su binary ....
5054 KB/s (104576 bytes in 0.020s)
Pushing Superuser app
5266 KB/s (2139595 bytes in 0.396s)
Making busybox runable ...
Now unlock your device and confirm the restore operation.
Please look at your device and click RESTORE!
If all is successful I will tell you, if not this shell will run forever.
Running ...
Successful, going to reboot your device in 10 seconds!
RunMe.sh: line 222: wait: pid 10 is not a child of this shell
Waiting for device to show up again....
RunMe.sh: line 225: wait: pid 10 is not a child of this shell
Going to copy files to it's place
mount: permission denied (are you root?)
You can close all open command-prompts now!
After reboot all is done! Have fun!
Bin4ry

Solved!
I finally was able to solve it.
Instead of selecting 1 (Normal Mode), selecting 0 (Xperia Root by cubeundcube) actually made it work seamlessly with Kindle Fire HD 8.9. So I guess it would be great to update the instruction this way (select 0 instead of 1 for Kindle Fire 8.9 running firmware 8.4.8)
hmkcs said:
Hello,
I tried to search for the solution for this but wasn't able to, so posting as a new thread..
I have been trying Root_with_Restore_Bin4ry_v33 to root my Kindle Fire 8.9 HD running firmware 8.4.8, and had no success in rooting the device.
The error I am getting is
"mount: permission denied (are you root?)"
which comes out from the command
./stuff/adb shell "/data/local/tmp/busybox mount -o remount,rw /system"
I ran the command with sudo (in my Mac) but it did not help. It seems that only very few people had the same problem but did not find the solution.
FYI, I did turn on (1) USB debugging and (2) Allow installtion from unknown sources before trying to root the device.
Here are possible suspects:
(1) I wonder this problem is specific to Mac OS X. I replaced ./stuff/adb to the version from adt-bundle-mac-x86_64-20131030. Did anyone have success in rooting KFHD in Mac OS X?
(2) I wonder this problem is specific to newer version of firmware (8.4.8), but I do see people without having problems with this version.
(3) Any other possible reasons?
Thanks for your help - H
(Below is the full message from running 'sudo sh RunMe.sh')
==================================================================================================
= This script will root your Android phone with adb restore function =
= Script by Bin4ry(converted to shell by jamcswain) (thanks to Goroh_kun and tkymgr for the idea) =
= Idea for Tablet S from Fi01_IS01 =
= (14.12.2013) v33 =
===================================================================================================
Device type:
0) Xperia Root by cubeundcube
1) Normal
2) Special (for example: Sony Tablet S, Medion Lifetab)
3) New Xperia Root by Goroh_kun
G) Google Glass Root (thx to Saurik for the ab file)
x) Unroot
Make a choice:
Please enter a valid number(1 to x):
1
Checking if I should run in Normal Mode or special Sony Mode
Please connect your device with USB-Debugging enabled now
Waiting for device to shop up, if nothing happens please check if Windows ADB-drivers are installed correctly!
remote object '/system/app/Backup-Restore.apk' does not exist
remote object '/system/bin/ric' does not exist
Normal Mode enabled!
Pushing busybox....
5309 KB/s (1165484 bytes in 0.214s)
Pushing su binary ....
5054 KB/s (104576 bytes in 0.020s)
Pushing Superuser app
5266 KB/s (2139595 bytes in 0.396s)
Making busybox runable ...
Now unlock your device and confirm the restore operation.
Please look at your device and click RESTORE!
If all is successful I will tell you, if not this shell will run forever.
Running ...
Successful, going to reboot your device in 10 seconds!
RunMe.sh: line 222: wait: pid 10 is not a child of this shell
Waiting for device to show up again....
RunMe.sh: line 225: wait: pid 10 is not a child of this shell
Going to copy files to it's place
mount: permission denied (are you root?)
You can close all open command-prompts now!
After reboot all is done! Have fun!
Bin4ry
Click to expand...
Click to collapse

kindle fire hd 8.9 8.4.8
hmkcs said:
I finally was able to solve it.
Instead of selecting 1 (Normal Mode), selecting 0 (Xperia Root by cubeundcube) actually made it work seamlessly with Kindle Fire HD 8.9. So I guess it would be great to update the instruction this way (select 0 instead of 1 for Kindle Fire 8.9 running firmware 8.4.8)
Click to expand...
Click to collapse
I am running windows 8.1 and a kindle fire hd 8.9 running 8.4.8 ive tried running option 0 but its telling me cant find path specified if i run as a non administrator it just says please connect device and sits there. Please a little help ive tried i think every procedure out there and the farthest i ve gotten is at boot never really fully boots so i had to restore to factory settings about 5 times / helllp

[Q] No Chance to root :/

So whats up guys,
I've got my new LG G-Pad 8.3 2 days ago and now.
I only want to root it. No Custom-Roms and CWMR etc.
The problem is:
No matter what I try, I can't root the device and I absolutely hv no Idea why.
Ofc I followed exact the instructions in the XDA-Developer thread.
The ERROR msg says:
Mounting system RW and pushung SU, then remounting system RO again
mount: Operation not permitted
failed to copy 'su' to '/system/xbin/su' : Read-only file system
Unable to open /system/xbin/su: No such file or directory
Unable to open /system/xbin/su: No such file or directory
mount: Operation not permitted
Installing superuser
4083 KB/s <2025538 bytes in 0.484s>
pkg: /data/local/tmp/superuser.apk
Success
Screenshot is also attached.
Any solutions

SOLVED!
The known Root methods in the Forum are working only for the LG G-Pad 8.3 Android 4.2.2!
If people updated it to 4.4.2 before rooting, have to use the following rooting method:
Note: I am not responsible if you make any mistakes or this does not work for you. Don’t forget to backup! I backed up my entire SD card.
Recommended:
Backup your data
Battery charged more than 50%
All things you will need:
Installed USB Drivers
IOroot25 (can be found here in the Forum!)
Rootchecker [Download]
How to Root LG G Pad 8.3 Steps:
1. Download and extract the IOroot25
2. Make sure your phone is in USB Debugging mode. Plug phone to PC.
3. Set USB mode to Charging only
4. Make sure ADB has been installed, and ADB has the proper permission
5. Run script and follow the onscreen instructions. (you can skip the Airplane part, because theres no thing such airplane mode on
our LG G-Pad 8.3
6. Windows: Double-click on root.bat
Linux: cd into IOroot folder -> chmod +x root.sh -> ./root.sh
Mac: cd into /IOroot/mac folder -> chmod +x root.sh -> ./root.sh
Confirm root with rootchecker.
Screenshot is attached ^_^. Enjoy.

[Q] Have I bricked my Arc S?

Hi,
I got a Sony Ericsson Arc S that I tried(4 hours) to update to Android KitKat without any success.
I tried to follow this guide : http://techglen.com/2013/12/04/update-xperia-arcarc-s-android-4-4-kitkat-cm-11-custom-rom/
But to not lose the Bravia function it states that I need to do a TA partition backup first and to do this the phone needs to be ROOTed. To get the phone ROOTed I tried this : DooMLoRD's Easy Rooting Toolkit [v4.0](zergRush Exploit) but it gave me this errors :
--- DEVICE FOUND
--- pushing busybox
1926 KB/s (1075144 bytes in 0.545s)
--- correcting permissions
--- remounting /system
mount: permission denied (are you root?)
--- copying busybox to /system/xbin/
/system/xbin/busybox: cannot open for write: Read-only file system
--- correcting ownership
Unable to chmod /system/xbin/busybox: No such file or directory
--- correcting permissions
Unable to chmod /system/xbin/busybox: No such file or directory
--- installing busybox
/system/xbin/busybox: not found
--- pushing SU binary
failed to copy 'files\su' to '/system/bin/su': Read-only file system
--- correcting ownership
Unable to chmod /system/bin/su: No such file or directory
--- correcting permissions
Unable to chmod /system/bin/su: No such file or directory
--- correcting symlinks
rm failed for /system/xbin/su, Read-only file system
link failed Read-only file system
--- pushing Superuser app
failed to copy 'files\Superuser.apk' to '/system/app/./Superuser.apk': Read-only
file system
--- cleaning
--- rebooting
ALL DONE!!!
Press any key to continue . . .
(Firewall and antivirus off)
The phone was on the next to latest official version so I tried to update it with the PC Companion from Sony Ericsson. It said that I hade to press down the back button at the same time as I connected the USB and then on the next step when it hade began the update it stated that I did not need to hold the key anymore so I released it and then the update stoped with error. After this the phone can´t be booted? When starting upp the phone I see the Sony logo and then a image with a phone and a warning triangle!? Nothing more happens, the screen goes black. I have tried to remove the batteri and I have tried to do the update again(the PC Companion do not recognize it).
Is it possible to fix it or is it forever bricked?

http://talk.sonymobile.com/t5/Andro...y-Bean-ICS-Ice-Cream-Sandwich-and/td-p/154389
Flash stock ftf using flashtool...and there's no use of backing up ta of xperia 2011 phones...
Follow this for installing cm11:
https://github.com/LegacyXperia/Wiki/wiki/Installing-LegacyXperia-for-Dummies
Sent from my D5503 using Tapatalk 2

You can't backup TA partition on 2011 Xperia phones (including Arc and Arc S).
Just unlock the bootloader and install custom kernel. Don't bother rooting your phone, you don't need to.

Okay,
I am now trying to follow : https://github.com/LegacyXperia/Wiki/wiki/Installing-LegacyXperia-for-Dummies and this is what I have done :
Install Mobile Flasher by Androxyde
Start Flasher
Hold the menu button at the same time as I put in the USB
The Flasher will responde with this :
07/042/2014 18:42:26 - ERROR - Drivers need to be installed for connected device.
07/042/2014 18:42:26 - ERROR - You can find them in the drivers folder of Flashtool.
I have runned the Flashtool-drivers.exe in C:\Flashtool\drivers folder, checked the Sony Ercisson Xperia Arc, Xperia neo, Xperia PLAY... but at about 80% completion a new wizard is shown(Device Driver Installation Wizard) and this will fail :
Sony Ericsson (WinUSB)... Install failed
Sony Ercisson NET Install failed
I have also tried download the Arc S drivers from this site : http://developer.sonymobile.com/downloads/drivers/ but Im not sure how to install these drivers? there is no setup?
When connecting the phone to the USB a Other Devices > S1Boot Fastboot will show up in the Device Manager with a exclamation mark?
There is problems where ever I go with this?

I have tried this :
Start Sony Mobile Flasher
Connect the USB without doing anything else
Flasher says that the phone is connected
I click the flash button in flasher and choose Flashmode, then OK
Choose the folder where the firmware is(LT18i_4.1.B.0.587_Generic_Global.ftf)
Click Flash
A dialog open and closes
It ends with error
07/005/2014 19:05:51 - INFO - Reading device information
07/005/2014 19:05:54 - INFO - Unable to read from phone after having opened it.
07/005/2014 19:05:54 - INFO - trying to continue anyway
07/005/2014 19:05:54 - INFO - Start Flashing
07/005/2014 19:05:54 - INFO - Processing loader.sin
07/005/2014 19:05:54 - INFO - Checking header
07/005/2014 19:05:54 - ERROR - Processing of loader.sin finished with errors.
07/005/2014 19:05:54 - INFO - Ending flash session
07/005/2014 19:05:54 - ERROR - Error in processHeader : 2 : The system cannot find the file specified.
07/005/2014 19:05:54 - ERROR - Error flashing. Aborted

Okay, I have now restarted Windows 8.1 and the stock flash was successfull. The phone is now starting up as it should.
I have also reinstalled fastboot according to this : http://techglen.com/2013/10/01/abd-and-fastboot-guide/
When connecting the turned on phone to the USB it is found as a ARC S in the Windows Explorer. So far so good.
But when doing this :
Turn off phone
Start fastboot(admin) in cmd
Holds the menu button and connects the USB so the led goes blu
Type fastboot flash boot boot.img and enter
It will no just show < waiting for device >
I also notice that when I connect the USB Windows sais that it does not recognize the device anymore. Probably becouse its in fastboot mode?
So what do I do now? I suspect that Im missing some USB driver for the fastboot mode on the phone?

Windows 8 and 8.1 have signature verification, which does not allow the installation of fastboot drivers.
Use this guide to install them - http://forum.xda-developers.com/showthread.php?t=2095087
EDIT: or this, if the first one doesn't - http://forum.xda-developers.com/showthread.php?t=2633904

Someguyfromhell said:
Windows 8 and 8.1 have signature verification, which does not allow the installation of fastboot drivers.
Use this guide to install them - http://forum.xda-developers.com/showthread.php?t=2095087
EDIT: or this, if the first one doesn't - http://forum.xda-developers.com/showthread.php?t=2633904
Click to expand...
Click to collapse
Tried the first example but that did not work. Feels like I invested to much time in this already so I will place this on hold and see if I will ever come back to fix it.
I have a Samsung S3 on service so my thought was to use the old Sony Ericsson ARC S instead of the HTC Titan but it is a bit to much work to get latest android running on this phone and even if it is done there will be buggs.
So Thanks so far for your help.

Okay, I tried on a Windows 7 64Btis as well and with the help of this video : https://www.youtube.com/watch?v=dUsA9HxZjJE I got the drivers installed so the S1Boot Fastboot driver dont got a warning.
But when running the fastboot it is still waiting for device. The blue led is active so the phone is in fastboot mode and I can see in activity field that it is connected to computer. Yet the fastboot will not find the phone? This feels all but unstable.

SnowJim said:
Okay, I tried on a Windows 7 64Btis as well and with the help of this video : https://www.youtube.com/watch?v=dUsA9HxZjJE I got the drivers installed so the S1Boot Fastboot driver dont got a warning.
But when running the fastboot it is still waiting for device. The blue led is active so the phone is in fastboot mode and I can see in activity field that it is connected to computer. Yet the fastboot will not find the phone? This feels all but unstable.
Click to expand...
Click to collapse
install android skd also (you said you installed allready the fastboot drivers.) also connect the phone onec powered on, may win installs some drivers. (in sdk just leave it like it is & press on install packages)