Related
I'm having trouble getting this POS rooted. Got it unlocked with little problem, but now that it comes to rooting, it's extremely confusing to follow the tutorials. Is there any working one-click methods? I'm no stranger to Android OS, I had my Dinc2 rooted in about 5 minutes after unboxing. But this abomination is really working my nerves. Help please?
There is no "One-Click Root"
But rooting using the given instructions is not difficult at all.
Its as simple as downloading a few files, and typing a few codes.
what have you tried so far? and what firmware are you running?
Since you unlocked your bootloader,here is how you get Root
http://forum.xda-developers.com/sho...m.xda-developers.com/showthread.php?t=1130639
download the .img ,put it in your fastboot folder
download the rootxperia.zip to your SD card
Turn phone off,plug into your PC/Laptop and hold search button ( might take some tries) ,you should get BLUE LED
SHIFT+RIGHTCLICK on fastboot folder and open in command window (assuming your usiing vista/win7) and type
fastboot boot recoveryPLAY.img
wait 2 minutes,it takes time.
Apply zip from SDcard and you are rooted
Cat_On_Droid said:
Since you unlocked your bootloader,here is how you get Root
http://forum.xda-developers.com/sho...m.xda-developers.com/showthread.php?t=1130639
download the .img ,put it in your fastboot folder
download the rootxperia.zip to your SD card
Turn phone off,plug into your PC/Laptop and hold search button ( might take some tries) ,you should get BLUE LED
SHIFT+RIGHTCLICK on fastboot folder and open in command window (assuming your usiing vista/win7) and type
fastboot boot recoveryPLAY.img
wait 2 minutes,it takes time.
Apply zip from SDcard and you are rooted
Click to expand...
Click to collapse
the wait for recovery to load is HORRIBLE!! lol. push the menu button once in a while if you are unsure. i did. it makes the wait (for me) less painful but installing the .zip and rebooting successfully with a rooted phone is AWESOME!!
Thanks for simplifying it for me Cat. I'm sitting here with my blue LED, my blank screen and my command window that now says "waiting for device" so that's what I'm doing. Waiting. Smoke break time.
chattguy said:
Thanks for simplifying it for me Cat. I'm sitting here with my blue LED, my blank screen and my command window that now says "waiting for device" so that's what I'm doing. Waiting. Smoke break time.
Click to expand...
Click to collapse
God this is painful. It's doing nothing. Should I unplug and try it again? it's been over 10 minutes.
chattguy said:
God this is painful. It's doing nothing. Should I unplug and try it again? it's been over 10 minutes.
Click to expand...
Click to collapse
are you sure that you installed the "S1Boot Fastboot" driver completely ?
cause i had some problem like yours ... just go to my computer=> right clik => manage=> devicce manager
and check if it's already install or not (( other devices ))
mehdi.moha said:
are you sure that you installed the "S1Boot Fastboot" driver completely ?
cause i had some problem like yours ... just go to my computer=> right clik => manage=> devicce manager
and check if it's already install or not (( other devices ))
Click to expand...
Click to collapse
Sony Ericsson sa0102 is installed, but I'm not seeing anything in my device manager about S1 Fastboot. Hmm...how would one go about installing it? I have the fastboot folder on my desktop. It has two subfolders, Fastboot and USB_drivers .
chattguy said:
God this is painful. It's doing nothing. Should I unplug and try it again? it's been over 10 minutes.
Click to expand...
Click to collapse
In this case if it's either still 'waiting for device' or trying to boot recoveryPLAY.img, then you're safe to try again since nothing is being flashed
When connected next time, in fastboot mode, before booting the .img, type this:
fastboot devices 'enter'
It will show a list of devices attached.
It might be that your missing some drivers so fastboot is not working correctly and won't detect your device. Have you pc companion installed? I don't remember if there came any drivers with the fastboot download but check that, there might be some drivers you didn't install.
Regards Dousan...
This is what happens. I just get another prompt. Here's a screenshot of that, along with the drivers folder.
chattguy said:
This is what happens. I just get another prompt. Here's a screenshot of that, along with the drivers folder.
Click to expand...
Click to collapse
That means no device is connected. Unlike ADB, fastboot does not return the usuall "list of attached devices" line. Have you installed fastboot drivers?
Sent from my R800i using Tapatalk
AndroHero said:
That means no device is connected. Unlike ADB, fastboot does not return the usuall "list of attached devices" line. Have you installed fastboot drivers?
Sent from my R800i using Tapatalk
Click to expand...
Click to collapse
I don't know, I just installed what the guy told me to when he did the remote bootloader unlock. Fastboot IS in my device manager, however, it says there are no drivers installed. I've got the blasted things on my desktop with some DPInst.exe installer, but it says I need the 64-bit version, which I can't find. Microsoft tried to have me download some silly .ISO file but I really think there must be an easier way than to burn some DVD installation disk.
chattguy said:
I don't know, I just installed what the guy told me to when he did the remote bootloader unlock. Fastboot IS in my device manager, however, it says there are no drivers installed. I've got the blasted things on my desktop with some DPInst.exe installer, but it says I need the 64-bit version, which I can't find. Microsoft tried to have me download some silly .ISO file but I really think there must be an easier way than to burn some DVD installation disk.
Click to expand...
Click to collapse
Ok these are the x32/x64 fastboot drivers.
http://www.multiupload.com/0XZV1LXRVA
Download them and unpack them. Connect your device in fastboot mode. Then navigate to device manager on windows, Find the S1 Fastboot thats not installed correctly. go to update driver and navigate to the driver package you just unpacked. Done
AndroHero said:
Ok these are the x32/x64 fastboot drivers.
http://www.multiupload.com/0XZV1LXRVA
Download them and unpack them. Connect your device in fastboot mode. Then navigate to device manager on windows, Find the S1 Fastboot thats not installed correctly. go to update driver and navigate to the driver package you just unpacked. Done
Click to expand...
Click to collapse
Mother. Of. God.
I did it. No, f**k that, you did it. All of you, thank you so much. You guys really helped me out bigtime, without berating me and calling me a noob lol. I sincerely appreciate it.
Also a special thanks to Alejandrissimo for unlocking the bootloader. Without you, this wouldn't have even been possible. Yay this blasted phone is finally rooted...
...and nobody had to die in the process.
That's what we are all here for. Learning about things through each other. We were all without knowledge at one point
Sent from my R800i using XDA App
I dropped my SIII and broke the screen, windows recognises it fine so i want to completely erase all my phone data as i have too much email data to send it back to the insurance company as it is, Any pc program that will let me erase the data safely
Heat and reps
Kies should be able to do that.
Sent from my SPH-L710 using Tapatalk 2
cant seee that option on KIES i want to completely format it from the pc really
get into adb and do a format google search for command
thatd be ideal but i have tried to get into download mode with no joy unfortunately
speed_bot said:
get into adb and do a format google search for command
Click to expand...
Click to collapse
sussed with reboot download
is any interaction required to take it into download mode? not showing in devices list
Cheers
keirmccann said:
sussed with reboot download
is any interaction required to take it into download mode? not showing in devices list
Cheers
Click to expand...
Click to collapse
is adb working or not see if you have sdk installed ....
Anyone help with this?
I cant get into Download mode for some reason one of the keys maybe broke
The screen is locked so i cant access anything using a screen streaming app
I cant get into recovery to try and get it to factory reset!
HELP!
speed_bot said:
is adb working or not see if you have sdk installed ....
Click to expand...
Click to collapse
I can access ADB from recovery mode but download doesnt appear to be working
keirmccann said:
I can access ADB from recovery mode but download doesnt appear to be working
Click to expand...
Click to collapse
Odin seems to recognise the device but cant execute any adb commands via shell?
Did you try adb reboot bootloader?
Sent from my SPH-L710 using Tapatalk 2
you are able to boot into recovery wipe the data from there that should do it...
I'm trying to update my G Watch by sideloading a zip file.
I installed the sdk tools and usb driver as usual.
On debugging mode and bootloader, the watch is detected as an ADB device normally. 'adb devices' command works.
But when I reboot and get on recovery mode, the watch disappears on the device manager and never get detected again. So I cannot use 'adb sideload' command.
I've never experienced this kind of issue with smartphones.
Do you have any solutions?
osikiri said:
I'm trying to update my G Watch by sideloading a zip file.
I installed the sdk tools and usb driver as usual.
On debugging mode and bootloader, the watch is detected as an ADB device normally. 'adb devices' command works.
But when I reboot and get on recovery mode, the watch disappears on the device manager and never get detected again. So I cannot use 'adb sideload' command.
I've never experienced this kind of issue with smartphones.
Do you have any solutions?
Click to expand...
Click to collapse
My watch is now bricked because I have no way to get out of "adb sideload" mode...how did you get out of that mode? please tell me.
TjPhysicist said:
My watch is now bricked because I have no way to get out of "adb sideload" mode...how did you get out of that mode? please tell me.
Click to expand...
Click to collapse
I pushed the reset button on the back(the silver one right above the charging connectors) with a pen for about 10 seconds, and it rebooted.
osikiri said:
I pushed the reset button on the back(the silver one right above the charging connectors) with a pen for about 10 seconds, and it rebooted.
Click to expand...
Click to collapse
Wow ok, that's a LOT longer than I'm used to with other devices...THANK GOD I thought I had bricked it completely.
Anyway, now i have to figure out a way to get adb to work in sideload,...i mean CLEARLY it's possible lots of others doing it..
---------- Post added at 08:26 AM ---------- Previous post was at 07:41 AM ----------
TjPhysicist said:
Wow ok, that's a LOT longer than I'm used to with other devices...THANK GOD I thought I had bricked it completely.
Anyway, now i have to figure out a way to get adb to work in sideload,...i mean CLEARLY it's possible lots of others doing it..
Click to expand...
Click to collapse
Ok, does anyone know how to get my computer to recognise my watch in recovery mode? It's not about 'driver' the computer plain doesn't recognise that anything is plugged in at all.
I know the post is quite old already, but I experience exactly the same phenomenon...
I tried multiple PCs Linux and Windows,but non of them recognized the watch (neither on 4.4W1 nor on 4.2W2).
Anyone any idea?
Wikiwix said:
I know the post is quite old already, but I experience exactly the same phenomenon...
I tried multiple PCs Linux and Windows,but non of them recognized the watch (neither on 4.4W1 nor on 4.2W2).
Anyone any idea?
Click to expand...
Click to collapse
I believe u need to update the drivers.....I always go-to device manager...update driver..hit select from list..and choose android adb....
Sent from my LGLS990 using XDA Free mobile app
mrkrabs said:
I believe u need to update the drivers.....I always go-to device manager...update driver..hit select from list..and choose android adb....
Sent from my LGLS990 using XDA Free mobile app
Click to expand...
Click to collapse
The problem, as @osikiri stated, is that the device does not get recognized at all (no unknown devices in devicemanager and the sound that comes on plugging in a device does not come as well). Furthermore, afaik Linux does not even need any drivers
Had the same issue today... and the only way out way battery death and recharge
JaceAlvejetti said:
Had the same issue today... and the only way out way battery death and recharge
Click to expand...
Click to collapse
If this really helps (seems weird): I guess the exact setting could be necassary:
You simply ran out of battery while the watch was running(not recovery or fastboot) and then plugged it in and went directly (or not?) to the recovery?
Thanks in advance, would be really great to fix this!
Anyone ever find a fix to this? I'm trying to manually install the 5.0 update and I'm having the same issue. Every post I find with search tells me to update drivers but I'm on a Mac that doesn't even use ADB drivers. I've updated the SDK.
MSigler said:
Anyone ever find a fix to this? I'm trying to manually install the 5.0 update and I'm having the same issue. Every post I find with search tells me to update drivers but I'm on a Mac that doesn't even use ADB drivers. I've updated the SDK.
Click to expand...
Click to collapse
I'm doing the same thing and having the same issues!
Yeah, same issue for me as described.
Windows (Win7 x64 for me) doesn't even realise that the device is connected when it is in recovery mode. Although it will connected properly when booted normally.
+1 Any ideas?
Same issue for me. I've tried removing and replacing it on the cradle, killing and restarting the adb server, entering recovery by the touchscreen or by the adb/fastboot commands, clearing debugging keys, etc... Anybody have any other ideas?
---------- Post added at 07:25 PM ---------- Previous post was at 06:46 PM ----------
Ok, so it appears that the recovery img on 4.4w2 broke adb support or something. There are a few threads that suggest you can root and flash it or just wait for the OTA. We'll see whether I get the OTA before I have time to try this out.
Lollipop OTA Update: Download and How-To (Root Required)
I made a script that roots and updates your watch to 5.0.1 in a click.
[UTILITY][RESTORE][UNLOCK][ROOT] LG G Watch Tool
My way of doing it
osikiri said:
I'm trying to update my G Watch by sideloading a zip file.
I installed the sdk tools and usb driver as usual.
On debugging mode and bootloader, the watch is detected as an ADB device normally. 'adb devices' command works.
But when I reboot and get on recovery mode, the watch disappears on the device manager and never get detected again. So I cannot use 'adb sideload' command.
I've never experienced this kind of issue with smartphones.
Do you have any solutions?
Click to expand...
Click to collapse
I've similar problem, and I've spent almost 3 hours to find the solution. I found that following solution work for me:
http://forum.xda-developers.com/g-watch-r/development/manual-ota-update-root-t2969845
I've changed the step slightly according to the comments inside the thread:
- Enter Bootloader (swipe top left-bottom right as soon as the LG logo pops up on boot)
- Unlock bootloader (fastboot oem unlock) and boot the watch normally once
- Turn off and re-enter bootloader
- Flash 5.0.1 Stock Recovery (fastboot boot recovery.img)
// Do Not Flash 5.0.2 stock recovery
- Enter recovery and ADB sideload the update (tap the android, select install update from ADB and enter adb sideload filename.zip)
//you might have to reinstall the ADB drivers, just follow the simple step to install ADB driver
Done.
fi thought it was finally the solution, but fastboot oem unlock bricked my sony smartwatch3. I see tomorrow if with my windows pc i can fix with sony companion, otherwise i'll have to use the warranty
willisc said:
I've similar problem, and I've spent almost 3 hours to find the solution. I found that following solution work for me:
http://forum.xda-developers.com/g-watch-r/development/manual-ota-update-root-t2969845
I've changed the step slightly according to the comments inside the thread:
- Enter Bootloader (swipe top left-bottom right as soon as the LG logo pops up on boot)
- Unlock bootloader (fastboot oem unlock) and boot the watch normally once
- Turn off and re-enter bootloader
- Flash 5.0.1 Stock Recovery (fastboot boot recovery.img)
// Do Not Flash 5.0.2 stock recovery
- Enter recovery and ADB sideload the update (tap the android, select install update from ADB and enter adb sideload filename.zip)
//you might have to reinstall the ADB drivers, just follow the simple step to install ADB driver
Done.
Click to expand...
Click to collapse
Hi, I tried root on my phone, I was on android nougat and I installed twrp, then perform a data factory reset and restart does not go from the boot screen and shows the legend "bad key", custom recovery works but not I get nothing, please help me!
Check this out
rolas96 said:
Hi, I tried root on my phone, I was on android nougat and I installed twrp, then perform a data factory reset and restart does not go from the boot screen and shows the legend "bad key", custom recovery works but not I get nothing, please help me!
Click to expand...
Click to collapse
I had the same problem and this post helped me.
samvictorino said:
I had the same problem and this post helped me.
Click to expand...
Click to collapse
Cmd does not recognize fastboot mode, usb debugging is disabled and I can not find a way to activate it, adb sideload from twrp works but will work from there?
rolas96 said:
Cmd does not recognize fastboot mode, usb debugging is disabled and I can not find a way to activate it, adb sideload from twrp works but will work from there?
Click to expand...
Click to collapse
Sorry, actually when I did it I accidentally wiped the system partition and this post helped me, not the previous one.
I didn't need to enable unknown sources or usb debug because there was no system to begin with. I hope it helps you.
rolas96 said:
Cmd does not recognize fastboot mode, usb debugging is disabled and I can not find a way to activate it, adb sideload from twrp works but will work from there?
Click to expand...
Click to collapse
Fastboot doesn't need USB debugging to be enabled. You have some other issue.
Sent from my XT1650 using Tapatalk
In twrp just ignore encrypt pass and not modify system allowed (slider)
Hey, I'm french so if I do mistake, it's normal, sorry
Here is a way to root this Wiko, finally!
Before doing this, i want to say that me, XDA or nobody exept you is responsible of what you can do on your phone, this method work for me, surely for you, but this operation will delete all your data, so remember to backup your data.
Now, you Have to go to Developper options, enable "OEM Unlocking", "USB Debugging" and disable "Verify apps over USB"
After, set "Select USB Configuration" to MTP. After That, download file (https://mega.nz/#!ioBQDZra!z6ntj85aM-mjg4dnscPaPBjvd-qpSY9HQiDkKuYbxcU) and extract it
Connect your phone to your Computer, Copy and Paste the SuperSU zip file in your SD card, and reboot your phone in fastboot mode (shutdown, and boot it by pressing Power and Vol+, then, when you have a choice between recovery and fastboot, select fastboot by clicking Vol-)
Open a command prompt in the extracted file, and type: fastboot oem unlock
Here, all your data will be lost by a factory reset.
When the phone restart, in the command prompt, type:
adb root
adb shell
cat /proc/partitions
ls -l /dev/block/platform/soc/7825900.sdhci/by-name/ (7825900.sdhci may be different, so use tab to find the correct file)
in the list, you will have a file with "recovery -> /dev/block/XXX" (XXX may be like mmcblk0p22)
cat /dev/block/XXX > /data/local/tmp/recovery.img
exit
adb pull /data/local/tmp/recovery.img
adb reboot-bootloader
fastboot flash recovery "CUSTOM recovery.img"
fastboot reboot
if there is no problems, you phone restart normally, so stop it, and boot to the recovery (Power and Vol+ and whene the choice appear, Select recovery with Vol+)
if your phone don't want to boot to the TWRP recovery, try to flash the stock recovery, reboot and flash again the custom one. if the problem persist, leave a comment.
In TWRP, swipe the button, and go to Install, Up a level, select external_sd and then, select the SuperSU file, select "Reboot after installation is complete, and swipe to flash.
When it's done, install or not the TWRP app, and reboot. The device can start twice before finally boot, and can be longer than usual, but don't do anything, it's normal.
When the phone finally boot, SuperSU may be installed, so go check if it's true, and if it is, go to the play store and install BusyBox (by Stephen (Stericson))
After the installation is complete, open it, and click install.
If there is no problem, the root acces will be request, so accept it and all is done.
If you have a problem, or any question, ask me.
Anyone a idea how to root a Wiko View 3 Lite?
give me the link, pls
greenverdy said:
give me the link, pls
Click to expand...
Click to collapse
Ok
Root Wiko View
Hi,
Can you send the link for rooting Wiko view.
Thanks in advance.
give me the link Please.
can you send me the link as well?
Please if someone has the package already, kindly posted it on the forum.
zerking said:
can you send me the link as well?
Please if someone has the package already, kindly posted it on the forum.
Click to expand...
Click to collapse
Ok, no problem
thank you for the link. I got both TWRP and SU installed but the device is not rooted? How can it be?
zerking said:
thank you for the link. I got both TWRP and SU installed but the device is not rooted? How can it be?
Click to expand...
Click to collapse
Do you have an error message ? Or something else ?
Oh, well, it figured my way out! First SU installation, the phone isn't rooted (I don't know why, either). But I factory reset the phone, set the phone up, then go to TWRP and re-install SU and it worked. Now the phone is rooted!
Thank you very much for your guide and files.
By the way, I guess most people will get stuck at "adb root" command.
Simply dial *#*#84666364#*#* (this launches TinnoEngineerMode)
- go to "Tinno Debug Feature"
- tap on "persist.tinno.debug" and choose 1
Then you can go on with "adb root" command
Hope this helps!
zerking said:
Oh, well, it figured my way out! First SU installation, the phone isn't rooted (I don't know why, either). But I factory reset the phone, set the phone up, then go to TWRP and re-install SU and it worked. Now the phone is rooted!
Thank you very much for your guide and files.
By the way, I guess most people will get stuck at "adb root" command.
Simply dial *#*#84666364#*#* (this launches TinnoEngineerMode)
- go to "Tinno Debug Feature"
- tap on "persist.tinno.debug" and choose 1
Then you can go on with "adb root" command
Hope this helps!
Click to expand...
Click to collapse
It's a good think to say it, because it don't work without dialing this number. Thanks
zerking said:
Oh, well, it figured my way out! First SU installation, the phone isn't rooted (I don't know why, either). But I factory reset the phone, set the phone up, then go to TWRP and re-install SU and it worked. Now the phone is rooted!
Thank you very much for your guide and files.
By the way, I guess most people will get stuck at "adb root" command.
Simply dial *#*#84666364#*#* (this launches TinnoEngineerMode)
- go to "Tinno Debug Feature"
- tap on "persist.tinno.debug" and choose 1
Then you can go on with "adb root" command
Hope this helps!
Click to expand...
Click to collapse
On latest wiko view update, tinoo debug feature was gone, we can't use adb root again after update
guys where i can download official rom for the wiko view 2 and extract?
ola and in french plz ?
don´t work on my wiko view 32GB
please help me to root my wiko view 32gb+3gb. i place fastboot oem unlock in pront comand i see waiting for device, and nothing. please creat a apk our anything for root
Would it work on k-Kool ?
We'll this sounds horrifying, just to get root permission, you have to accept to get rid of all your data and parms ? It must be another way.
I'll explain my real need for rooting my Wiko k-Kool. I bought a 64GB SD card, to be used normally as external storage, not for apps install. However I want to be able to backup my phone onto that card, just in case. I use Helium to backup my data without needing root (uses internally adb) ! However non-rooted Helium as a 3d party application has no permission to write to the SD card ! The reason I want to root is just to give Helium the permission to wirte into a backup directory.
Therefore I dont want to put my data at risk just to get root permission, but found no other way to change heliums permissions.
Thanks for any help.
This can work for the Wiko view 2 ? I can't find anything for my phone [emoji24]
Envoyé de mon W_C800 en utilisant Tapatalk
Can this work for view 2?
This work forse Wiko view max?
nothing for wiko view go?
Hello
Is there anyone who did root the wiko view go hier please?