Hello. I have a sony tablet s wifi only, which had rooted ICS, installed with condi's AIO.
Today it got stucked on boot screen, so after many tries of soft reset I went to recovery mode(which btw is rev.29 <3e>) and wiped all data.
Now, I'm trying to install a new software using AIO and Flasher but the app gets stucked on this message:
Code:
[*] Waiting for device...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Please! Can someone help me?
bycxc said:
Hello. I have a sony tablet s wifi only, which had rooted ICS, installed with condi's AIO.
Today it got stucked on boot screen, so after many tries of soft reset I went to recovery mode(which btw is rev.29 <3e>) and wiped all data.
Now, I'm trying to install a new software using AIO and Flasher but the app gets stucked on this message:
Code:
[*] Waiting for device...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Please! Can someone help me?
Click to expand...
Click to collapse
1. recovery.
2. make sure that you have correct adb driver installed.
3. download prerooted doubleFLASH fw from my signature.
4. flash via AiO - flash custom [straight from recovery] option.
br
condi
message
condi said:
1. recovery.
2. make sure that you have correct adb driver installed.
3. download prerooted doubleFLASH fw from my signature.
4. flash via AiO - flash custom [straight from recovery] option.
br
condi
Click to expand...
Click to collapse
Thank you, condi, for your answer.
1.Recovery - can reach it - rev.29 <3e> with some errors becuase of the system and data wipe.(errors like: "E:Fail to read boot logo flag" , "E::Can't open /dev/block/mmcblk0p5(No such file or directory)" , "E:Can't mount /cache/recovery/command" , "E:Fail to mount /sdcard(No such file or directory)" );
2.adb is installed using "Sony Tablet ADB Driver Automated Installer", Composite Adb Interface in recovery and looks fine;
3.
4.Well , here is the real problem. AiO is displaying this
Code:
[*] Enter recovery (power + vol-up) and run _hack_recovery.zip
Wait for assert error..
The problem is that as you can see from "1) Recovery errors", my memory card can't be mounted so I can't use that _hack_recovery.zip from recovery. Also I don't have that hack_recovery file.
Here is a screenshot with the recovery screen, dropbox link: /u/43085866/20130223_140402.jpg
Related
This is a simple tutorial on how to root your phone and install CWM recovery and then flash a custom ROM to you X10 mini Pro:
I'M NOT RESPONSIBLE BY ANY WAY IF YOU MISS-USED THIS TUTORIAL AND YOU BRICKED YOUR DEVICE! PLEASE BE CAREFUL USING IT AND BE SURE TO FOLLOW THE STEPS CORRECTLY.
1. Download CWMInstaller-Windows-v4-dl.zip (Credits go to nobodyAtall & D4rKn3sSyS for the actual CWM files. Other credits in the README.txt file) and extract it. Original Post for this tool is at:
http://forum.xda-developers.com/showthread.php?t=1257701
please say thanks to rect2409 too for the above post.
2. Inside the settings menu in your phone go to Application then go to development then select “USB Debugging Mode”
3. Connect your phone to the PC via USB and select “Charge the Phone”. DO NOT MOUNT THE SD CARD.
4. Inside CWMInstaller-Windows-v4-dl already extracted, double click on Install.Bat
5. Follow the questions as per below for non rooted phones:
a. Is your device ROOTed? (Y/N): press Y then enter. SuperOneClick will launch now, you will only need to press “Root” wait till the process ends then this application will ask you to test the root press yes for it.
b. Once finished and returned back to the cmd window, just press enter to continue and install the CWM recovery.
c. Once done the phone will reboot and you will be successfully rooted and installed CWM recovery on your phone.6. Now time to install a custom ROM:
a. Choose a custom ROM from the forum here in the Development section of your device.
b. Download the ROM and put it in your Memory Card.
c. Turn off or reboot your phone.
d. Once Sony Ericsson Logo on a black screen shows up press the back button several time till the CWM recovery console is displayed.
e. You can navigate between option of this console by using the volume keys up and down and to select an option press the home key and to go back to a previous page press the back key.
f. From this console you should backup your existing ROM by choosing backup and restore then backup.
g. Now when the backup is finished select install zip from SD Card
h. Navigate to your Custom rom you Already put on your sd card and select it by pressing the home button on your phone
i. Now the console will ask you do you want to continue, press yes.
j. Wait the Rom flashing to end.
k. Once finished go back to the main screen select “wipe data/factory reset” then press yes. Then select “wipe cache partition” and select yes. Then go to “advanced” then select “Wipe Dalvik Cache” press yes.
l. Now you can reboot you phone.
m. The first reboot usually takes time to finish.7. After full boot and configuration you will be successfully rooted/installed recovery/and flashed a new ROM to your phone.
RESERVED ...
Reserved too...
Big thanks to you man!
Question about the guide because I'm confused. Do you wipe data/factory reset (and so on) before or after flashing the ROM? Because from what I've read from other post you do it before flashing not after. Please enlighten a n00b like me.
It is preferable to be after the flashing as the rom
Sent from my U20i using XDA App
That's the reason why I'm getting lots of buggy installs. I will try that the next time I install a rom. Or maybe later when i install the new nAa kernel and ROM.
Thanks once again. Maybe ill do it before and after. LOL
demoniacs said:
That's the reason why I'm getting lots of buggy installs. I will try that the next time I install a rom. Or maybe later when i install the new nAa kernel and ROM.
Thanks once again. Maybe ill do it before and after. LOL
Click to expand...
Click to collapse
Making a complete wipe/factory reset should be after flashing the ROM.. N wiping before flashing the ROM dosn't make a difference.. N the bugs u feel are only if they are in the ROM/kernel n not the way u make a wipe.. So I guess it might have cleared your question well..
Sent from my U20i using xda premium
Fantastic!
Thanks a lot, my x10 is rooted!
But it only worked for me when I didn't press on "Charge phone": I left the screen like that.
Before, when I pressed "charge phone" the adb couldn't find my phone...
just let you know that, it could help someone else.
Again, thank you!
Inji.
Ps: I'm also a rooting addict now: just rooted my iconia a501 recently from the same great forum!
Thanks, worked great !
ClockWorkMod Recovery Installer for X10 Mini Pro by rect2409.
Requirements and credits are listed in the README.txt file.
Please make sure requirements are met before continuing.
Please make sure that your phone is connected to your PC and USB debugging
abled.
Press any key to continue . . .
Is your device ROOTed? (Y/N):Y
Starting ADB Server.
adb server is out of date. killing...
* daemon started successfully *
Pushing exploit to gain ROOT access.
adb server is out of date. killing...
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Mount system as R/W.
Do you already have a recovery installed? (Y/N):N
Pushing recovery tar file.
protocol failure
Pushing chargemon.
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon
Pushing busybox.
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
519 KB/s (735308 bytes in 1.382s)
Setting permissions for recovery tar file.
Unable to chmod /system/bin/recovery.tar: No such file or directory
Setting permissions for chargemon.
Setting permissions for busybox.
Mount system as read only.
Reboot phone.
Stopping ADB Server.
* server not running *
If no errors are listed above then CWM has been installed.
Finished.
Press any key to continue . . .
Hi All !
I have a Samsung Galaxy Note 10.1 GSM 3G tablet [N8000 model]. Right now it comes with stock Samsung Android 4.1 and stock Android recovery.
I have a trouble installing ClockWorkMod and root it.
What I did ?
1. Installed Samsung USB drivers + ADB + fastboot + Odin.
2. Enabled USB debug
3. adb devices
E:\Smartphones\Android\GalaxyNote_10.1\ADB_Fastboot>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
4107764d436ccf47 device
4. fastboot devices
E:\Smartphones\Android\GalaxyNote_10.1\ADB_Fastboot>fastboot devices
[empty]
5. fastboot flash recovery [imagefile]
E:\Smartphones\Android\GalaxyNote_10.1\ADB_Fastboot>fastboot flash recovery E:\S
martphones\Android\GalaxyNote_10.1\recovery-clockwork-6.0.4.6-n8000.img
< waiting for device >
...
Basically adb "sees" my device, but fastboot does not see it.
I tried this procedure when Android is booted ans also when it is in "download" mode.
Host is: Windows 7 x64, Intel Core i7 4770. I have installed
Another problem: Odin 3.0.9 sees my device, and it does not accept *.img files from CWM, but requires .tar instead. Why so ?
Any ideas ?
Please help.
-Technologov
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
Hello,
I tried to flash the viper one x+ rom on my device but it turned out terrible. I folowed the process but finally i couldn't flash the rom i don't know why. After a few tries my phone started to not get signal and i couldn't turn on wifi. Somehow i made it work but after that i got a very stupid idea. I wanted to copy the files of the rom on my phone using the venom recovery (TWRP). Now there is no OS on my phone and from my storage everything is missing escept the TWRP folder. I thought there will be my backup but it disappeared. Can anyone help me please?
http://forum.xda-developers.com/showthread.php?p=35897865#post35897865
this post might help you a bit
read post #4
also try to search hasoon toolkit to help you fix you prob
:fingers-crossed:
It didn't work. When I'm trying now it sais that my phone is not connected but it must be connected because I could flash the recovery.
so my computer is recognizing my phone as an adb device but the adb sideloader can't find the device. And writes this: * daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
i dont know what to do :/
I made it! Using just cmd. If you put the rom in the sdk platform tools and start there a cmd and in twrp recovery on your phone go to advanced adb sideload start it and in cmd write adb devices it should write that your device is in sideload then write adb sideload <rom name>.zip (that must be put in the sdk folder) and it will sideload your rom. If adb devices cant find your phone or it writes that it is in recovery reply the command a few times until it writes sideload. After that you are ready to go. I hope it will help somone.
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.