Related
hi guy,
when wanted to start flashing my xperia play using flashtool 2.9 beta it was asking for s1boot download driver in my window xp and now i stuck at this stage before the flashtool wanted to flash my phone. Please help to advice.
Thanks
Open your eyes! You can get the drivers in the first sticky in the development section.
Sent from my R800i using Tapatalk
yes fixed it.
thanks
Where?
I can't find it either..
Edit:
Found this:
3*w.
<remove>
binnersoft.
<remove>
com/?p=1935
SE has removed it from support site. Will fix missing driver error.
Tags:
S1Boot Driver Not Found download
StuartStardust said:
I can't find it either..
Edit:
Found this:
3*w.
<remove>
binnersoft.
<remove>
com/?p=1935
SE has removed it from support site. Will fix missing driver error.
Tags:
S1Boot Driver Not Found download
Click to expand...
Click to collapse
I can confirm this works, I tried EVERYTHING else but no S1Boot Download driver could be found, until I tried the file linked above. Cheers!
Duddyroar said:
I can confirm this works, I tried EVERYTHING else but no S1Boot Download driver could be found, until I tried the file linked above. Cheers!
Click to expand...
Click to collapse
You should know that you can install any driver by YES OR YES method, just path to .inf file
thanks bro for this zip file
Alejandrissimo said:
You should know that you can install any driver by YES OR YES method, just path to .inf file
Click to expand...
Click to collapse
a thousand times THANKS! this saved my phone NEO, I was unable to install any drivers, so I could not flash my FW.
hi,i have the same problem,but with live with walkman phone,my laptop get stuck when i connected into the flash mode,could this fix worked on my LWW too?how to use it?
sorry for my noob..
Thank You
thank you for the driver, he served for my Xperia Arc successfully!
Alejandrissimo said:
You should know that you can install any driver by YES OR YES method, just path to .inf file
Click to expand...
Click to collapse
I need the 64-bit.
ty for zip file buddy
Alejandrissimo said:
You should know that you can install any driver by YES OR YES method, just path to .inf file
Click to expand...
Click to collapse
thank alot for ur zip.this is work in sony ericsson lt18i.
Awesome
Alejandrissimo said:
You should know that you can install any driver by YES OR YES method, just path to .inf file
Click to expand...
Click to collapse
Your link works perfect
Setup is not compatible with 64 bit win 7 ultimate
But all you need to do is:
0. Extract the Zip file to any folder
1. Goto Device manager
2. Right click the s1bootdownload icon (which will have an exclamation mark in a yellow triangle)
3. Click update driver
4. Use manual install from computer option
5. select the folder where you extracted the zip file
6. Hit ok
7. Works like charm
---------- Post added at 09:09 AM ---------- Previous post was at 08:53 AM ----------
KeanuC said:
I need the 64-bit.
Click to expand...
Click to collapse
Check the Link: http://forum.xda-developers.com/showpost.php?p=30236997&postcount=14
The driver not found icon might still appear in your desktop,
But Sony phone will we detected for flash/ software update after its switched off, just press the volume down key while inserting the usb in your phone (phone should be switched off)
I use an Sony Ericsson ST17i Active Phone
Worked for me
Alejandrissimo said:
You should know that you can install any driver by YES OR YES method, just path to .inf file
Click to expand...
Click to collapse
my pc cant find the S1 fastboot drivers in there. and it may be a bit random but thanks again for unlocking my xperia play a couple a months back :good:
rupinkarani said:
Your link works perfect
Setup is not compatible with 64 bit win 7 ultimate
But all you need to do is:
0. Extract the Zip file to any folder
1. Goto Device manager
2. Right click the s1bootdownload icon (which will have an exclamation mark in a yellow triangle)
3. Click update driver
4. Use manual install from computer option
5. select the folder where you extracted the zip file
6. Hit ok
7. Works like charm
---------- Post added at 09:09 AM ---------- Previous post was at 08:53 AM ----------
Check the Link: http://forum.xda-developers.com/showpost.php?p=30236997&postcount=14
The driver not found icon might still appear in your desktop,
But Sony phone will we detected for flash/ software update after its switched off, just press the volume down key while inserting the usb in your phone (phone should be switched off)
I use an Sony Ericsson ST17i Active Phone
Worked for me
Click to expand...
Click to collapse
i cant find s1 boot in device manager
The best version is the one provided as part of flashtool
(Then you don't need the -i 0xfce each time you execute fastboot)
Alejandrissimo said:
You should know that you can install any driver by YES OR YES method, just path to .inf file
Click to expand...
Click to collapse
20 thanks !
This post is very precious to us xperia users
Thank you for the driver
i have a question
once my sony xperia sl boot into fastboot mode the s1 tool driver is installing ... but after 10 sec my phone become normal boot and this cause the driver is not install completely what can i do...?
I've made a fully compatible 64 bit package.
It's the same package as "USBFlash_driver" but than with 64 bit compatibility
*should also work on WIN8 couldn't test it tho, let me hear! otherwise ill make it compatible
MOD EDIT: This host is not allowed, and even looks like a scam. Rehost on d-h.st or goo.im.
Many thanks to my friend rootdefyxt320 who told me:
rootdefyxt320 said:
1. Patch adbd by using adbd insecure. http://forum.xda-developers.com/showthread.php?t=1687590
(ADB will refuse to push things through /system if adbd is secure).
2. Download BootMenu_v2.0.2.zip. http://forum.xda-developers.com/show....php?t=1997638. (Tried the apk, it doesn't work.)
3. Unzip it.
4. Double click on the .bat file and it should install.
5. Reboot and press vol- right after moto logo.
Click to expand...
Click to collapse
Well, ADB insecure is not really needed. If you have init.d support (if not, see http://www.xda-developers.com/android/init-d-support-for-any-rooted-phone/) you just have to :
I ARE DOING THIS AT YOUR OWN RISKS. I AM NOT RESPONSIBLE FOR ANY DAMAGE YOU MAY CAUSE TO YOUR PHONE (but I can help you repair it )
MAKE A FULL BACKUP BEFORE GOING ANY FURTHER
Your phone has to be rooted.
I made a flashable zip
It comes with init.d support.
This one come with this http://forum.xda-developers.com/showthread.php?t=2190758 2ndInit.
For now 2ndInit is for dev only. Don't try anything foolish.
0 - download the attached zip
1 - push the XT320_bootmenu.zip on your sdcard
Code:
> adb push XT320_bootmenu.zip /sdcard/XT320_bootmenu.zip
2 - Reboot with a CWM... (recovery.img attached)
Code:
>adb reboot bootloader
> fastboot boot recovery.img
3 - Flash XT320_bootmenu.zip thorough CWM
4 - Reboot and enjoy !
What I did (if you are interested):
In /system/bootmenu/script/pre_bootmenu.sh, I replace (line 9)
PART_CACHE=/dev/block/mtdblock10 by PART_CACHE=/dev/block/mtdblock9
and (line 64)
button-backlight by keyboard-backlight (this is not a major issue, I think but it is still raising errors)
same in stock.sh (line 24)
button-backlight by keyboard-backlight
and finally in _config.sh (line 6-7-8)
PART_SYSTEM=/dev/block/mtdblock8
PART_CACHE=/dev/block/mtdblock10
PART_DATA=/dev/block/mtdblock11
by
PART_SYSTEM=/dev/block/mtdblock11
PART_CACHE=/dev/block/mtdblock9
PART_DATA=/dev/block/mtdblock12
So what you have to do if it is not working, is to check which block correspond to which partition and then adapt the values.
In shell:
Code:
$mount
Check if init.d support is working:
In shell:[/COLOR][/B]
Code:
$cat /data/Test.log
You should be careful before trying 2ndInit and 2ndBoot functionality of bootmenu. They are NOT viable.
Thanks to aweosomeabhijeet
Code:
CHANGELOG
V2:
If booting on stock, the amber led is lightening up
If booting on 2ndInit, the red led is lightening up
I repack a more recent version of CWM Recovery (V6.0.9)
Clean the /system/bootmenu folder before install
Hey has anyone tried cwm from fire xt? It might work on our phone
http://forum.xda-developers.com/showthread.php?t=1997638
Guitwo2 said:
I'm trying, using : http://forum.xda-developers.com/showthread.php?t=1600805
But with the small /system partition it seems impossible to have a fully deodexed ROM. Maybe a few apps...
---------- Post added at 11:27 AM ---------- Previous post was at 11:20 AM ----------
A few post earlier, we add a similar discussion. There was the final answer :
Click to expand...
Click to collapse
This one doesn't use logwrapper, it uses 97bootmenu to hijack the boot process. The Moto Fire XT 530 has a MSM7227T-1 chipset.
rootdefyxt320 said:
This one doesn't use logwrapper, it uses 97bootmenu to hijack the boot process. The Moto Fire XT 530 has a MSM7227T-1 chipset.
Click to expand...
Click to collapse
Then I am interested ! I will have a closer look. You tried it already ?
---------- Post added at 10:08 AM ---------- Previous post was at 09:29 AM ----------
I just get the apk. Installation seems successful. However, no led is going blue on boot to let me enter bootmenu (V2.3)
I tried V1.4.2, but it was more like if I reset my phone. Still no bootmenu. [EDIT] : I think it just cleared my /etc partition (at least), that's why it messed up. [EDIT2] Or maybe it was working ? I am not sure about how to check if it was.
If the trick were explained somewhere, I could have a closer look...
[EDIT3]
Well I tried http://forum.xda-developers.com/showthread.php?t=1026853 which shall be the same thing as the apk, but no success.
It seems that this method replaces /system/bin/mount_ext3.sh by an other one. But this file does not exist in the in the stock version of my ROM. So I guess the trick cannot work. Or I don't understood how it works.
Guitwo2 said:
Then I am interested ! I will have a closer look. You tried it already ?
---------- Post added at 10:08 AM ---------- Previous post was at 09:29 AM ----------
I just get the apk. Installation seems successful. However, no led is going blue on boot to let me enter bootmenu (V2.3)
I tried V1.4.2, but it was more like if I reset my phone. Still no bootmenu. [EDIT] : I think it just cleared my /etc partition (at least), that's why it messed up. [EDIT2] Or maybe it was working ? I am not sure about how to check if it was.
If the trick were explained somewhere, I could have a closer look...
[EDIT3]
Well I tried http://forum.xda-developers.com/showthread.php?t=1026853 which shall be the same thing as the apk, but no success.
It seems that this method replaces /system/bin/mount_ext3.sh by an other one. But this file does not exist in the in the stock version of my ROM. So I guess the trick cannot work. Or I don't understood how it works.
Click to expand...
Click to collapse
Use adbd insecure.
http://forum.xda-developers.com/showthread.php?t=1687590
Patch adbd to run as root.
Then use the Batch installer. The last time I did it, it installed, but it was about to boot into bootmenu, then it exited. Make use the Fire XT 2nd-Init. Not the Defy One.
rootdefyxt320 said:
Use adbd insecure.
http://forum.xda-developers.com/showthread.php?t=1687590
Patch adbd to run as root.
Then use the Batch installer. The last time I did it, it installed, but it was about to boot into bootmenu, then it exited. Make use the Fire XT 2nd-Init. Not the Defy One.
Click to expand...
Click to collapse
I'll try that !
Guitwo2 confirmed that bootmenu worked. Go to the link to see it.
http://forum.xda-developers.com/showthread.php?t=1997638
Moved to http://forum.xda-developers.com/showpost.php?p=39961127&postcount=1
Here is 2nd-boot for fire xt:
http://forum.xda-developers.com/showthread.php?t=2190758
You must have 2ndinit CWM for it to work.
If FireXT CWM works on our phone then 2nd-Init/2nd-boot should work on our phone.
The one you download doesn't include 2nd-boot
rootdefyxt320 said:
Here is 2nd-boot for fire xt:
http://forum.xda-developers.com/showthread.php?t=2190758
You must have 2ndinit CWM for it to work.
If FireXT CWM works on our phone then 2nd-Init/2nd-boot should work on our phone.
The one you download doesn't include 2nd-boot
Click to expand...
Click to collapse
I tried the 2nd init that were here originally, and it seems tp work. But I donot really know what I should expect.
Sent from my XT320 using xda app-developers app
Guitwo2 said:
I tried the 2nd init that were here originally, and it seems tp work. But I donot really know what I should expect.
Sent from my XT320 using xda app-developers app
Click to expand...
Click to collapse
The bootmenu doesn't seem to work for me. I check the mtdblocks and it matches yours. I have busybox installed, init.d support. The blue led loads up after the bootloader, but when it tries to boot into bootmenu, it exits.
rootdefyxt320 said:
The bootmenu doesn't seem to work for me. I check the mtdblocks and it matches yours. I have busybox installed, init.d support. The blue led loads up after the bootloader, but when it tries to boot into bootmenu, it exits.
Click to expand...
Click to collapse
Try to run in shell
Code:
$su
#sh /etc/init.d/97bootmenu
and see what you get.
Im a noob. Can someone tell me what is bootmenu?
Sent from my XT320
junk031 said:
Im a noob. Can someone tell me what is bootmenu?
Sent from my XT320
Click to expand...
Click to collapse
It's a way to run CWM on locked bootloaders, it is 2nd-Init basically.
---------- Post added at 06:39 PM ---------- Previous post was at 06:35 PM ----------
Guitwo2 said:
Try to run in shell
Code:
$su
#sh /etc/init.d/97bootmenu
and see what you get.
Click to expand...
Click to collapse
It still doesn't boot into bootmenu
rootdefyxt320 said:
It still doesn't boot into bootmenu
Click to expand...
Click to collapse
Nothing prompting ?
Try then (in shell with root) :
Code:
exec /system/bootmenu/binary/bootmenu
How can i change the Permissions ?
Tubii said:
How can i change the Permissions ?
Click to expand...
Click to collapse
Code:
chmod XXX /filepath/filename
http://en.wikipedia.org/wiki/Chmod
What am I doing wrong?
http://www7.pic-upload.de/09.04.13/ogq36obcugkw.jpg
Defy is Rootet.
USB Debugging is enable.
Tubii said:
What am I doing wrong?
http://www7.pic-upload.de/09.04.13/ogq36obcugkw.jpg
Defy is Rootet.
USB Debugging is enable.
Click to expand...
Click to collapse
You forgot to "su" before "exec"
If you are not root when executing 97bootmenu, it will not work.
Guitwo2 said:
You forgot to "su" before "exec"
If you are not root when executing 97bootmenu, it will not work.
Click to expand...
Click to collapse
Ok then my screen darker
http://www7.pic-upload.de/09.04.13/ta1rsvpkl1sk.jpg
So I decided to try to run ubuntu touch on my Samsung Galaxy Nexus(verizon). All went well, but now it seems I cant start the phone, can only get into fastboot mode. Can anyone please walk me through the steps of putting stock android back on my phone? I have adb and fastboot installed on my computer. There's a guide here that walks you through the process of returning the phone to stock software/firmware, but it requires USB debugging to be on, which I can't turn on because the phone won't boot up. I greatly appreciate any help!!!
Phone Info(what's written in fastboot):
PRODUCT NAME-Tuna
VARIANT- toro 32GB
HW VERSION- 9
BOOTLOADER VERSION: PRIMELC03
BASEBAND VERSION- I515.FK02 CDMA-I515.FK01
CARRIER INFO- NONE
SIGNING- production
LOCK STATE- UNLOCKED
You dont need USB debug on in order to use fastboot
---------- Post added at 05:39 PM ---------- Previous post was at 05:38 PM ----------
Debugging is only needed if using adb.
But if u already in fastboot bootloader mode then u don't need to do "adb reboot bootloader" command
ashclepdia said:
You dont need USB debug on in order to use fastboot
---------- Post added at 05:39 PM ---------- Previous post was at 05:38 PM ----------
Debugging is only needed if using adb.
But if u already in fastboot bootloader mode then u don't need to do "adb reboot bootloader" command
Click to expand...
Click to collapse
Thanks for the pretty fast response! I'm still lost as to how I can make everything go back to the way it is (i.e, get rid of ubuntu and get android back on ) . Definitely my last time trying to muck around with roms and such D;
vsp3317 said:
Thanks for the pretty fast response! I'm still lost as to how I can make everything go back to the way it is (i.e, get rid of ubuntu and get android back on ) . Definitely my last time trying to muck around with roms and such D;
Click to expand...
Click to collapse
Don't give up!
Once you've done it once or twice it becomes easier, everything starts to make sense
Did you download one of the Google factory img for toro to your computer? Get it from here
https://developers.google.com/android/nexus/images
(It will be under the Mysid/toro name) any of the available ones will work that are for toro.
---------- Post added at 06:19 PM ---------- Previous post was at 06:17 PM ----------
Then you just uncompress the file, open command prompt(aka terminal) in that folder/directory , put device into fastboot mode(bootloader), and then execute the flash all script that comes with the factory IMG download.
---------- Post added at 06:26 PM ---------- Previous post was at 06:19 PM ----------
Oh, and to easily open a command prompt in that directory, uncompress the factory img download file from that site linked above, then open the folder to view it's contents. Hold shift and right click within the folder and choose "open command prompt"
Then all you should need to do is put "flash-all.exe" and hit enter in the command prompt that pops up once device is connected and in fastboot(bootloader)mode. (No quotes...just enter the text) and then be patient. The flashing of the radio files might seem to take a long time especially the CDMA radio. Do NOT unplug or anything before it is completed fully)
If need anymore info ask away
ashclepdia said:
Don't give up!
Once you've done it once or twice it becomes easier, everything starts to make sense
Did you download one of the Google factory img for toro to your computer? Get it from here
(It will be under the Mysid/toro name) any of the available ones will work that are for toro.
---------- Post added at 06:19 PM ---------- Previous post was at 06:17 PM ----------
Then you just uncompress the file, open command prompt(aka terminal) in that folder/directory , put device into fastboot mode(bootloader), and then execute the flash all script that comes with the factory IMG download.
---------- Post added at 06:26 PM ---------- Previous post was at 06:19 PM ----------
Oh, and to easily open a command prompt in that directory, uncompress the factory img download file from that site linked above, then open the folder to view it's contents. Hold shift and right click within the folder and choose "open command prompt"
Then all you should need to do is put "flash-all.exe" and hit enter in the command prompt that pops up once device is connected and in fastboot(bootloader)mode. (No quotes...just enter the text) and then be patient. The flashing of the radio files might seem to take a long time especially the CDMA radio. Do NOT unplug or anything before it is completed fully)
If need anymore info ask away
Click to expand...
Click to collapse
Wow, I can't thank you enough man!!! :highfive: That worked like a charm , no problems at all . And oh it's "flash-all.bat" not .exe, for the people that might come across this thread later. Thanks again though, I really don't know what I would've done. Definitely going to do a **** ton more research next time I decide to go and flash a rom haha.
vsp3317 said:
Wow, I can't thank you enough man!!! :highfive: That worked like a charm , no problems at all . And oh it's "flash-all.bat" not .exe, for the people that might come across this thread later. Thanks again though, I really don't know what I would've done. Definitely going to do a **** ton more research next time I decide to go and flash a rom haha.
Click to expand...
Click to collapse
No problem buddy
That's what these forums are for, learning, helping, development, all that good stuff! Just happy it went smoothly for ya.
I think it used to be named .exe, at least it shows as exe on my laptop but I use Linux so it could just be seeing it differently(since I have wine installed)
There is usually a windows executable and a Linux .sh script that can be executed from the terminal to start the process.
See, it's not all THAT bad now is it? Especially since now you know how to do it, messing up the device isn't such a daunting thing anymore lol.
As for keeping status 7 from happening again I highly recommend bookmarking the TWRP or CWM official sites so that before flashing things in the future, you can make sure you have the most up to date custom recovery installed by comparing what is available vs what you have installed(booting into recovery mode will usually have the version info somewhere on the main screen) and of course having a recent nandroid backup made within your current custom recovery. I prefer TWRP but it's a personal choice to each user which they use
Just don't be afraid to play around
Congrats again on your first soft brick&restore! Lol
It's such a relieving feeling once you bring device back from the dead ain't it?
Root is no longer working on MM update.
Don't suppose anybody knows how to get to recovery with hardware button?
hecksagon said:
Don't suppose anybody knows how to get to recovery with hardware button?
Click to expand...
Click to collapse
Swipe from top-left to bottom-right at the Asus logo. That gets you to fastboot mode, then swipe up and down to change menu items, swipe right to select.
Or you can enable debug mode and use adb reboot recovery.
CSX321 said:
Swipe from top-left to bottom-right at the Asus logo. That gets you to fastboot mode, then swipe up and down to change menu items, swipe right to select.
Or you can enable debug mode and use adb reboot recovery.
Click to expand...
Click to collapse
You are a hero. I have looked for the better part of 2 hours for this. Anyway I'll sideload the LP update and start over. Hopefully somebody can make use of the recovery and boot pulls and get us a working recovery.
I would be very interested in REMOVING the Wellness app. This is the only reason I want root. Guess I will need to wait until we have a root enabled file manager. Alas, I can write in C++ fairly well, but know nothing of coding for android. Be glad to test any recoveries and operating systems on my ZenWatch.
nethead72 said:
I would be very interested in REMOVING the Wellness app. This is the only reason I want root. Guess I will need to wait until we have a root enabled file manager. Alas, I can write in C++ fairly well, but know nothing of coding for android. Be glad to test any recoveries and operating systems on my ZenWatch.
Click to expand...
Click to collapse
It can be done without a file manager. If you have root, you can enable debugging, connect to a PC by USB, use adb to get a root shell, then adb uninstall package_name.
Edit...Which Benton are you in, BTW. I'm not far from Benton, IL.
CSX321 said:
It can be done without a file manager. If you have root, you can enable debugging, connect to a PC by USB, use adb to get a root shell, then adb uninstall package_name.
Edit...Which Benton are you in, BTW. I'm not far from Benton, IL.
Click to expand...
Click to collapse
Es File Explorer works fine and has an OK interface when on the watch. Also the KingRoot app that gets pushed has an uninstaller too for system apps. The biggest issue I've had is that when the prompt to allow root comes up you can not select allow. You have to cover the screen to back out, then go into KingRoot and open the log, then select the app you want to allow and set it to always allow. You have to do this after the initial failed prompt.
Edit: Freeport, IL here. Worlds a small place.
File Types?
hecksagon said:
The latest Windows version of kingroot works on the zenwatch. I currently have root that persists after reboot and I am working on pulling the boot.img and recovery.img. Not sure what to do after that, hope somebody can pick up on this.
Recovery.img
https://drive.google.com/file/d/0BxOsuCVqSlnfVzVGRWo4bmZZZHc/view?usp=docslist_api
Boot.img
https://drive.google.com/file/d/0BxOsuCVqSlnfLVp4Z19EQ0owdTQ/view?usp=docslist_api
Click to expand...
Click to collapse
Am I looking at .iso files here, tarballs, or some other kind of binary? I need to add file extensions to make them useful.:good:
---------- Post added at 09:30 PM ---------- Previous post was at 09:28 PM ----------
Benton Arkansas.
---------- Post added at 09:32 PM ---------- Previous post was at 09:30 PM ----------
hecksagon said:
Es File Explorer works fine and has an OK interface when on the watch. Also the KingRoot app that gets pushed has an uninstaller too for system apps. The biggest issue I've had is that when the prompt to allow root comes up you can not select allow. You have to cover the screen to back out, then go into KingRoot and open the log, then select the app you want to allow and set it to always allow. You have to do this after the initial failed prompt.
Edit: Freeport, IL here. Worlds a small place.
Click to expand...
Click to collapse
I use ES File Explorer on my Nexus 6, CyanogenMod 12.1
I do not have a wearable app on my ZenWatch. Is it in settings somewhere?
nethead72 said:
Am I looking at .iso files here, tarballs, or some other kind of binary? I need to add file extensions to make them useful.:good:
---------- Post added at 09:30 PM ---------- Previous post was at 09:28 PM ----------
Benton Arkansas.
---------- Post added at 09:32 PM ---------- Previous post was at 09:30 PM ----------
I use ES File Explorer on my Nexus 6, CyanogenMod 12.1
I do not have a wearable app on my ZenWatch. Is it in settings somewhere?
Click to expand...
Click to collapse
You have to download the normal phone apk from apkmirror or some other site and use adb to sideload it. Google sideloading apps to Wear, should work the same for any watch. Otherwise you can buy Apps2Wear on the play store. I have done that because its more convenient.
Ok, went through the whole process, is there a way to check root access using ADB?
You should have KingRoot app installed on your watch. That will tell you if you have root. I imagine you could try to pull some files from /system or something that would normally not be accessible. I wouldn't recommend writing to system yet. I soft bricked by watch just by pasting a modified build.prop over the original, trying to turn off low bit depth ambient mode.
Root confirmed, having issues side-loading the ES File explorer apk, though. I'm using the App2Wear method. Still trouble shooting.
nethead72 said:
Root confirmed, having issues side-loading the ES File explorer apk, though. I'm using the App2Wear method. Still trouble shooting.
Click to expand...
Click to collapse
Make sure you have adb debugging and adb bluetooth debugging enabled on watch. Make sure you have usb adb debugging turn on on phone. Then make sure you have bluetooth debugging turn on in Wear app. Make sure you do these in that order because the toggle in the wear app wont show up unless you have debugging enabled on phone first.
This is the KingRoot file you need for windows.
https://onedrive.live.com/redir?res...3077&authkey=!AA2AI4RkRdiA4tg&ithint=file,exe
Attached is the latest ES File Explorer APK
EDIT: I rebooted everything, and worked fine. Funny how rebooting fixes so many issues... Will test when side-load is completed.
EDIT 2: Looks like its gonna take a long time. Gonna go do dishes and whatnot and be patient.
nethead72 said:
Am I looking at .iso files here, tarballs, or some other kind of binary? I need to add file extensions to make them useful.:good:
Click to expand...
Click to collapse
Sorry, they are .img. They were pulled using Flashify. The extension must have been stripped when I uploaded them to Drive.
nethead72 said:
This is the KingRoot file you need for windows.
https://onedrive.live.com/redir?res...3077&authkey=!AA2AI4RkRdiA4tg&ithint=file,exe
Attached is the latest ES File Explorer APK
EDIT: I rebooted everything, and worked fine. Funny how rebooting fixes so many issues... Will test when side-load is completed.
EDIT 2: Looks like its gonna take a long time. Gonna go do dishes and whatnot and be patient.
Click to expand...
Click to collapse
Sometimes it fails once and works when you retry. Not sure why.
hecksagon said:
Sometimes it fails once and works when you retry. Not sure why.
Click to expand...
Click to collapse
ES is 28 MB when installed, according to App2Wear, that should be 45-60 minutes to install.
nethead72 said:
ES is 28 MB when installed, according to App2Wear, that should be 45-60 minutes to install.
Click to expand...
Click to collapse
Maybe 10-15 mins when I did.
hecksagon said:
Maybe 10-15 mins when I did.
Click to expand...
Click to collapse
Seems like its taking way too long (going on 1 hour+). Gonna reboot and try again.
---------- Post added at 11:55 PM ---------- Previous post was at 11:25 PM ----------
If it fails this time, I will connect it to ADB with command line and manually push the apk onto the watch. I will give it until after dinner to complete the process.
Cant get it to install, and adb says its an invalid apk file when i try to push it. I suppose its not really necessary anyway. Ill just use KingRoot app if I need to do file management.
nethead72 said:
Seems like its taking way too long (going on 1 hour+). Gonna reboot and try again.
---------- Post added at 11:55 PM ---------- Previous post was at 11:25 PM ----------
If it fails this time, I will connect it to ADB with command line and manually push the apk onto the watch. I will give it until after dinner to complete the process.
Cant get it to install, and adb says its an invalid apk file when i try to push it. I suppose its not really necessary anyway. Ill just use KingRoot app if I need to do file management.
Click to expand...
Click to collapse
Did you confirm the apk was good? I'd try installing it on your phone. I don't think KingRoot has file management capabilities.
On a side note, I would advise against uninstalling anything. I just went to flash the previous OTA and it failed because I didn't have Jawbone installed.
I've just got a LG G4 after owning a G3 for ages.
It's LG G4 H815 UK.
I'm trying to unlock bootloader and root + install recovery.
It was easy on G3....but i'm having HUGE problems with the G4.
All the steps in the how to guide from here, go well, until I attempt to get device ID.
It just keeps coming up with the same old errors as you can see below.
Please, help me out...i've literally been trying for the last 3 hours non stop...lol.Hey, i'll even send a donation to beer money if somebody can pleeeeeezzz help me out.:good:
**********************************************
C:\adb\LG Root>adb.exe devices
List of devices attached
C:\adb\LG Root>adb.exe devices
List of devices attached
LGH8159460c7f1 device
C:\adb\LG Root>adb.exe push busybox /data/local/tmp/ && adb.exe push lg_root.sh
/data/local/tmp && adb.exe push UPDATE-SuperSU-v2.46.zip /data/local/tmp
2958 KB/s (1048328 bytes in 0.346s)
1137 KB/s (9319 bytes in 0.008s)
3711 KB/s (4017098 bytes in 1.057s)
C:\adb\LG Root>Send_Command.exe \\.\COM4
Author : blog.lvu.kr
SPECIAL COMMAND : ENTER, LEAVE
Couldn't open the port \\.\COM4
C:\adb\LG Root>Send_Command.exe \\.\COM5
Author : blog.lvu.kr
SPECIAL COMMAND : ENTER, LEAVE
#id
FAIL
#
FAIL
#^C
C:\adb\LG Root>id
'id' is not recognized as an internal or external command,
operable program or batch file.
C:\adb\LG Root>#ID
'#ID' is not recognized as an internal or external command,
operable program or batch file.
C:\adb\LG Root>#id
'#id' is not recognized as an internal or external command,
operable program or batch file.
C:\adb\LG Root>dd if=/data/media/0/system.rooted.H81510c-EU.img bs=8192 seek=552
96 count=529920 of=/dev/block/mmcblk0
'dd' is not recognized as an internal or external command,
operable program or batch file.
C:\adb\LG Root>sh /data/local/tmp/lg_root.sh dummy 1 /data/local/tmp/UPDATE-Supe
rSU-v2.46.zip /data/local/tmp/busybox
'sh' is not recognized as an internal or external command,
operable program or batch file.
C:\adb\LG Root>
*******************************************
Many thanks
Matt
Your port is closed, please check device manager>port and instead of com4 that being request why send command on com5?
Not entirely sure what you mean?
When I click on ports.bat in my adb folder it says it sees the device on port 5.
I'm lost.....please help:crying:
Here's another screenshot with it showing port 4....but still it fails to get the ID of the phone to enter into LG website to get code.
I get to this point in the screenshot below, where i have to enter "id" but nothing happens...just a blinking cursor when i enter id and press enter.
Any ideas?
thanks
Matt
fails on the last line....
matthew33 said:
fails on the last line....
Click to expand...
Click to collapse
Hi buddy are you using the right com port because you need to choose the diag1 com port not the other one , also ignore what it says in device manager just use the com port from the lg root tool which is diag1... And one last thing are you on marshmallow or lollipop??
matthew33 said:
fails on the last line....
Click to expand...
Click to collapse
try this
Code:
Send_Command.exe \\.\COM4
Xceeder said:
Hi buddy are you using the right com port because you need to choose the diag1 com port not the other one , also ignore what it says in device manager just use the com port from the lg root tool which is diag1... And one last thing are you on marshmallow or lollipop??
Click to expand...
Click to collapse
I'm using diag1 and am using the com port from lg root tool.
My phone has Android 6.0 installed.
Any ideas?
thanks
Matt
This is the latest error i got....
I get to the point where i see
"Type "id" and press enter (no quotes)."
But when I type in the word "id" on the next line comes up the word "Fail"
wtf??
matthew33 said:
I get to the point where i see
"Type "id" and press enter (no quotes)."
But when I type in the word "id" on the next line comes up the word "Fail"
wtf??
Click to expand...
Click to collapse
You are doing it the wrong way , if you are on MM then you just unlock your bootloader then flash a pre rooted kernel i will find the links for you in a few minutes
---------- Post added at 10:18 AM ---------- Previous post was at 10:12 AM ----------
Xceeder said:
You are doing it the wrong way , if you are on MM then you just unlock your bootloader then flash a pre rooted kernel i will find the links for you in a few minutes
Click to expand...
Click to collapse
Can i just ask which version of MM are you on is it 20a , 20b , 20c etc ?? You can find out this information by going into settings/about phone/software info/software version...
Xceeder said:
You are doing it the wrong way , if you are on MM then you just unlock your bootloader then flash a pre rooted kernel i will find the links for you in a few minutes
---------- Post added at 10:18 AM ---------- Previous post was at 10:12 AM ----------
Can i just ask which version of MM are you on is it 20a , 20b , 20c etc ?? You can find out this information by going into settings/about phone/software info/software version...
Click to expand...
Click to collapse
Thanks mate...really would appreciate it if you could find the links.
Below is screenshot of my phone info:
free uploader
matthew33 said:
Thanks mate...really would appreciate it if you could find the links.
Below is screenshot of my phone info:
free uploader
Click to expand...
Click to collapse
Okay you are on 20g the links that i had are for a b c and d so just give a few minutes while i find the right link for your software version , back soon ...
---------- Post added at 12:14 PM ---------- Previous post was at 12:03 PM ----------
Xceeder said:
Okay you are on 20g the links that i had are for a b c and d so just give a few minutes while i find the right link for your software version , back soon ...
Click to expand...
Click to collapse
Right if you haven't already flashed twrp then do that first then download the file on this page and flash it in recovery
https://download.chainfire.eu/696/supersu/
If you need help to install twrp just quote my post , this method should work ....
---------- Post added at 12:27 PM ---------- Previous post was at 12:14 PM ----------
P.s if this method does not work then just flash this kernel in recovery
https://www.androidfilehost.com/?w=files&flid=46800
Flash the 1.4.7 version...
Xceeder said:
Okay you are on 20g the links that i had are for a b c and d so just give a few minutes while i find the right link for your software version , back soon ...
---------- Post added at 12:14 PM ---------- Previous post was at 12:03 PM ----------
Right if you haven't already flashed twrp then do that first then download the file on this page and flash it in recovery
https://download.chainfire.eu/696/supersu/
If you need help to install twrp just quote my post , this method should work ....
---------- Post added at 12:27 PM ---------- Previous post was at 12:14 PM ----------
P.s if this method does not work then just flash this kernel in recovery
https://www.androidfilehost.com/?w=files&flid=46800
Flash the 1.4.7 version...
Click to expand...
Click to collapse
Thnaks for taking the time to help me mate....I really genuinely appreciate it.
If you could tell me exactly how to flash TWRP etc, it would be super appreciated.
I can't enter recovery on my phone.
thanks
Matt
Download twrp 3.0.2.0 and save it in the same place as your adb files , then open a command window by holding shift and right mouse click and do these commands -
adb devices
(This will check if the device is connected you should see a number next to device)
adb reboot bootloader
(This simply reboots your phone ready to flash)
fastboot flash recovery twrp-3.0.2-0-h815.img
(Make sure the twrp name is the same as the command)
Hit enter and you should have twrp installed on your device...
Xceeder said:
Download twrp 3.0.2.0 and save it in the same place as your adb files , then open a command window by holding shift and right mouse click and do these commands -
adb devices
(This will check if the device is connected you should see a number next to device)
adb reboot bootloader
(This simply reboots your phone ready to flash)
fastboot flash recovery twrp-3.0.2-0-h815.img
(Make sure the twrp name is the same as the command)
Hit enter and you should have twrp installed on your device...
Click to expand...
Click to collapse
Done exactly what you said, and this is what i got...see screenshot.....
imageupload
matthew33 said:
Done exactly what you said, and this is what i got...see screenshot.....
imageupload
Click to expand...
Click to collapse
Go to the settings of your phone and press on build number around 8 times until it says you are a developer then enable USB debugging and tick the box that says enable OEM unlock and try again , also make sure when you connect the phone to the PC select mtp connection for USB ...
Xceeder said:
Go to the settings of your phone and press on build number around 8 times until it says you are a developer then enable USB debugging and tick the box that says enable OEM unlock and try again , also make sure when you connect the phone to the PC select mtp connection for USB ...
Click to expand...
Click to collapse
Well, I'm getting somewhere....after hours of trying i've definitely 100% unlocked the bootloader.
BUT, how do i install TWRP and superuser plus how do i boot into recovery?
thanks
Matt
I tried to reboot into recovery using adb fastboot command reboot recovery.....it renooted to a black screen with a green android laying down with, i think a red mark??
Any ideas?
thanks
Matt