I'm trying to unlock the bootloader on my X10i but once I have downgraded to 2.1 (either via the downgrade ftf provided or a full 2.1 firmware) my X10 never gets detected as being plugged in.
I get to
* daemon started successfully *
on the qsd8250_semc tool and then plugging in the phone does nothing.
I can still use FlashTool to upgrade my firmware again so I'm not sure what's wrong.
http://forum.xda-developers.com/showthread.php?t=1254087
make sure flashtool is not on while cmd is running
Related
Hi all
I'm currently trying to root my x10i, I carried out the first step with no troubles however whenever I enter my device into usb debugging mode I get the following error when loading the step2.bat
* daemon not running. starting it now *
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon
* daemon not running. starting it now *
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon
"select option 6 SDCARD UPDATE"
Press any key to continue . . .
Click to expand...
Click to collapse
Has anyone else experienced this problem? I'm sure the correct driver is installed as the system knows the ADB driver is present.
Thanks
-Sean
Same exact thing .. stuck on HTC EVO white screen 4 G will nto go any further.
sur3sh0t said:
Hi all
I'm currently trying to root my x10i, I carried out the first step with no troubles however whenever I enter my device into usb debugging mode I get the following error when loading the step2.bat
Has anyone else experienced this problem? I'm sure the correct driver is installed as the system knows the ADB driver is present.
Thanks
-Sean
Click to expand...
Click to collapse
Moved as not android development
I went stock DI01 by Odin, and tried re-rooting by Superoneclick 1.7, but it doesn't respond at "Waiting for device". it freezes.
I tried the other way from terminal, and it keeps on saying that the device isn't connected.
******************************************************************************
* *
* Dirrk's EZ Root v0.2 (Sebastien Krahmers Exploit) *
* *
******************************************************************************
*
* Testing if your device is connected
*
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
*
* If you are NOT connected please follow these directions
* Install the correct drivers
* Turn On Debugging
* Check usb port, cable and phone
* Then rerun this application
*
Press any key to continue . . .
*
* Pushing the files to your phone
* rage.bin, busybox, Superuser.apk, su, com.sh
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
* Restarting your phone to ensure the exploit will work
* When your phone comes back on please unlock it if it is locked and then
* wait
error: device not found
I can access the SD card, but rooters are not working when I turn on usb debugging.
I have Samsung driver installed, android sdk installed, and tried turning on and off while connected to computer. still no root.
how can I get it working?
With the number of pre-rooted roms we have why even root? After odin restore boot but don't sign in and power down. Pull battery/Flash CWM_recovery.tar/ insert battery 3 finger salute to recovery flash desired (rooted) rom. Depending upon what package you used you might have to flash a current modem in odin. Continue to restore set up.
good day.
One Click doesn't work anymore. I did this yesterday, after going back to stock and doing an OTA update, works wonderfully and it's really easy, very low possibility of bricking your phone and having to go through the hassle of fixing that. Go to this thread and follow along. http://forum.xda-developers.com/showthread.php?t=913470 I recommend using the Clockwork Packages from here though they are the most recent and everything seems to be fixed on them. http://forum.xda-developers.com/showthread.php?t=1017817 Easiest way I have ever seen to root a phone.
Dear XDA Developers,
I recently purchased an xperia pro mk16i from china, through ebay.
When trying to unlock the bootloader through fastboot; it already was.
The phone came with android 2.3.4, (in dutch, my native language, which struck me as odd) I believe.
I followed a tutorial to install sailfish, and all was fine; but I skipped a step that asked for stock android ICS to make sure the partition layouts and firmware was correct.
Trying to go back to stock and flashing a ftf for my phone with flashrom is where the trouble started, I never managed to flash anything through flashrom, despite trying everything I could find. (no driver issues)
Where I am now:
-I can flash a boot.img through fastboot, and cyanogenmod just fine (everything boots) but my touchscreen won't work
-Flashrom mentions an unofficial bootloader, and gives an error relating to loader.sin when trying to flash anything.
-Trying 'repair my phone' in sony pc companion states at the last moment (when connecting phone in flashmode) that there is no software available for my phone
How can I fix my phone again?
I tried emma; which mentions my phone is locked; though the bootloader has to be unlocked for I have used a custom rom.
flashtool mentions a nonstandard loader as well.
I think I somehow have a strange nonstandard but patched bootloader.
How do I flash a stock bootloader so I can unlock it properly, and flash a stock rom/ftf?
This keeps getting worse; I can't enter fastboot anymore (and cwm too)
that happened after trying restore in s1tool.
since then, my bootloader version is in capital R, not small r, indicating it is locked.
trying the unlock method with testpoint appears to work, however after disconnecting the phone, it resets back to R4A069
trying to flash with s1tool flashes adsp.sin correctly, but gets stuck on the loader just like flashtool
FATAL ERROR [ SECURITY_CLASS: SIN_HEAD_VER, Failed_to_verify_sin_header ]
I removed loader.sin from the ftf archive and flashed it with s1tool and it worked!
I forgot about simlock.ta, so I flashed that too :/
anyways, phone boots now, touchscreen still doesn't work, I have usb debugging / can access adb now, but I still can't boot into fastboot.
Hello everyone.
*
I installed the 3.01 ROM without going through tools and official ROM. So I have a partitions problem and data network.
I will reinstall an older ROMi have dont access to Recovery 2.8.6 (by either the keys or by applying or by ADB).
I can not either throwing fastboot command in bootloader mode ... My phone seems yet to be recognized by the device manager. Drivers is ok.
impossible blow to flash a ROM or a recovery!
*
*
*
Someone should do a track for me going ??
Tku
I am not sure I should post my problem here, but it seemed approperate to me. If not, please tell me where to post this.
I try to install DualRecovery on my Tablet Z2 (SGP521). Up till step 2 everything is going fine. Deamon is running, device is found and it sends the recovery files. Step 3: creating target sockets.... OK! and then Done!
A lot of x's and then my device is rebooting and the following message:
=============================================
If your device now boots to recovery, reboot
it to system to continue and allow this script
to check and clean up. The script will continue
once your device allows adb connections again.
=============================================
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
But my device takes like 5 minutes to boot. Before my device is completely booted I get the message:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
=============================================
Unrooted installation failed, please press 1
once the device finished rebooting to retry.
Is the problem the boot time of 5 minutes or is it really failing regardless of the boot time??
Barium said:
I am not sure I should post my problem here, but it seemed approperate to me. If not, please tell me where to post this.
I try to install DualRecovery on my Tablet Z2 (SGP521). Up till step 2 everything is going fine. Deamon is running, device is found and it sends the recovery files. Step 3: creating target sockets.... OK! and then Done!
A lot of x's and then my device is rebooting and the following message:
=============================================
If your device now boots to recovery, reboot
it to system to continue and allow this script
to check and clean up. The script will continue
once your device allows adb connections again.
=============================================
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
But my device takes like 5 minutes to boot. Before my device is completely booted I get the message:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
=============================================
Unrooted installation failed, please press 1
once the device finished rebooting to retry.
Is the problem the boot time of 5 minutes or is it really failing regardless of the boot time??
Click to expand...
Click to collapse
You didn't mentioned your firmware version but Dualrecovery ain't compatible with your device latest stock firmwares.
kulvertti said:
You didn't mentioned your firmware version but Dualrecovery ain't compatible with your device latest stock firmwares.
Click to expand...
Click to collapse
Indeed... The tablet is on Android version 5.0.2; build number 23.1.A.1.28. So it should work, right?
Barium said:
Indeed... The tablet is on Android version 5.0.2; build number 23.1.A.1.28. So it should work, right?
Click to expand...
Click to collapse
Yes, it should work. After checking that there is no other adb (or Sony) -process runing in the backround try to install it again. Maybe several times.
kulvertti said:
Yes, it should work. After checking that there is no other adb (or Sony) -process runing in the backround try to install it again. Maybe several times.
Click to expand...
Click to collapse
And does it matter that the bootloader is locked? The service menu says: "Unlocking Bootloader Allowed:NO". Normally it says YES, but the DualRecovery should also work with a locked bootloader, right?
Barium said:
And does it matter that the bootloader is locked? The service menu says: "Unlocking Bootloader Allowed:NO". Normally it says YES, but the DualRecovery should also work with a locked bootloader, right?
Click to expand...
Click to collapse
Correct.