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.
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'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
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 . . .
Hello people! The truth did not know where to put this but if it's wrong because there is no problem and relocated!
I have a x900 LeTV I bought several months ago! Two weeks ago you installed a beta version of android 6.0.1. and I was working fine few days and one night, suddenly he went out and caught no more! Hard has a brick because no load, does not light, does not enter or fasboot recovey mode, any PC with any version of Windows recognizes it and have been for days following guidelines to resuscitate through QPST.2.7.429.msi without but although follow the steps one by one PC with Windows 7 simply does not recognize me! I am in despair and can not think of anything else! Some genius of the community could help me? There is a guide for x800 that is very similar to x900, yet still do not achieve much !!!
Same
Same issue, did u manage to fix it?
Hello dear all,
after a long time of rush*around different solutions I finally figure it out how to hard brick Indian le max x900
(note hard brick means ur phone is completely dead no charging,no restart, *no fastboot etc....becoz of may be wrong rom flashing)
1. Install qualcom driver and latest qpst 2.7*(link:*https://androiddatahost.com/np4wq)(qualcomm driver present in qfil file for x800 link in step4)
2. Installed qpst*will be present at c:/program files(x86)/qualcomm/qpst/bin....inside it find qfil flashing*application...open it
3. connect ur dead indian le max to computer and see if qualcomm usb driver can detect it(u may notice qfil flashing appln will also show some com no connected)....if u r unsuccessful just press both volume key/or power key and both vol key at a time for around 1 min when phone is connected to pc.*(in any case u failed no big issue try to install it manually by searching in google, well I have used win10 and it simply worked for me)
4. Download the qfil file for x800 and extract it somewhere, it also have qualcomm driver inside it so once extracted install that driver too (link:*https://mega.nz/#!G0ozxZwb!vowHBNjQGC1AtVOx2ThrWpYt6yHEnAACFvq90XDF4n0)....actually i tried qfil for x900,x1, line brush tutorials etc but none of those worked for me and x800 aks le 1 pro have the same processor so it can make x900 alive....sahara error all the time...*( a big thx to*UNBRICK X800 X900*Started by*mxmax)
5. if all done correctly u can see ur dead indian lemax*phone connected to qualcomm mode with some com no, that u can notice in qfil flashing appln.
6.in the flashing appln select Flat Build,
* * * * * * * * * * * * * * * * * * * * *in browse select ur extracted qfil x800 folder (path\qfil x800\x1_na_dvt1_fastboot\prog_emmc_firehose_8994_lite.mbn,
* * * * * * * * * * * * * * * * * * * * *in load xml select rawprogram_unsparse (present inside folder x1_na_dvt1_fastboot)....after that patch0 that automatically comes,
* * * * * * * * * * * * * * * * * * * * than finally click on download....u can see process started and once completed exit it.
7. So now ur phone have qfil of x800 flashed, try to boot it by pressing power button for 1 min.....u can see blue led blinked and ur phone start to boot (if not means ur phone's battery is very less simply connect it with charger by pressing power button u can see phone starts to show orange led flashing after some time....ie it start charging)
8. once it start in step 7 the phone show chinese letv logo...but it doesn't boot becoz it is for x800 not x900....phone simply tries to boot again and again...so once the phone start to reboot by itself simply press power button and vol down key at a time....u can see small penguin that means ur phone is in fastboot mode.
9. its time now to install twrp 3.0 to ur x900 connected to pc in fastboot mode(link:*https://www.androidfilehost.com/?fid=24533103863139522)...simply install twrp from link extract it open the twrp installer appln ....and install it by pressing backspace key that u find during instrution)....great thing about twrp recovery is it can charge ur phone too while connected to power source.
10.So after step 9 ur phone should be in twrp 3.0 recovery mode....u can see internal storage of it shows in pc of around 10 gb not 52 gb.....so inside twrp\wipe\format data...type yes, and advanced wipe select all and wipe......once done u have 52 gb avail in internal storage that u can see in ur pc too.
11. put indian version any rom inside ur internal storage and flash it...once done ur phone will successfully rebooted links for roms are below...simply download any as per ur choice
* * * * *https://drive.google.com/file/d/0B6m-wM0vYiL8U0U4cUhUM2NlMGc/view*(this is stock 12s rom)
* * * **https://www.androidfilehost.com/?fid=24533103863139959* (this is also stable 12s rom made bu cuoco with extra settings and dolby presinstalled)
* * * **http://evolutionletvx900.blogspot.in/* *(this will give u link for 12s and 13s rom which have nova and google launcher preinstalled)
* * flash any rom and if any any file after flashed make big vibrate ur phone with blue led on...don't panic...simply press power button for long time it will reboot ur phone
A big thx to memerbers of leeco.re for proving international support for leeco becoz it had gone from India, and I request u to make support for Indian x900 also since we cant able to install eui 5.8 based roms....tried to install several roms by deleting lines for check in update-script...even though it installed make it brick/dea again...so plz help for android 6*
Hi, I'm a x900 user
I have the same issue than some of you guys, my phone is detected in Qualcomm mode in QFIL, I have to charge the phone like an hour or two, I can tell its chargin because It has the blue led on, when it has no charge the led is blinking red and after sometime it becomes blue.
Put the phone in Qualcomm mode, download finish succesfully, pressed Vol Up + Power, my phone starts but with blue led and black screen, although its detected as a hard drive (LeTV), it'srecognized as an adb device (serial number ----- recovery). I ran the command "x1_na_fastboot" in command prompt inside folder CEXCNFN590......zip., I got rebooting in fast mode device, but it stops in "awaiting devices".
Thats were I'm stuck. Got any ideas?
2 Rahulraj2012
Thanks bro it is work exactly as you say !!! X900 Unbriked for now ;-)
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.