Hi , i made one mistake now am stuck, whilst rooting i went to flash the zip file in recovery and noticed the put the folder of it instead of the actual zip file.so obviously its not working. how do i access internal storage , mount usb isnt workin in team recovery,and its stuck in loop if try to power on tablet. any ideas am fumin whats point of havin mount when it doesnt work ????
Make sure recovery it ok. if not re-flash TWRP via fastboot again.
so if u can boot in TWRP use install by sideload (TWRP->Advance->ADB Sideload) via PC and USB Cable
attach USB Cable and make sure you Windows was detect device as ADB mode.
open cmd use command "adb sideload path-to-working-image-file.zip"
good luck
phukao said:
Make sure recovery it ok. if not re-flash TWRP via fastboot again.
so if u can boot in TWRP use install by sideload (TWRP->Advance->ADB Sideload) via PC and USB Cable
attach USB Cable and make sure you Windows was detect device as ADB mode.
open cmd use command "adb sideload path-to-working-image-file.zip"
good luck
Click to expand...
Click to collapse
yeh i can get in recovery TWRP ,i did as u say i heard laptop make a sound when ADB sideload started
i have no idea what to type into cmd tho , the zip file in on desktop what exactly do i type ?
thanks
Hi everyone!
I was trying to install Cyanogenmod on my LGOG F180S, Im new to everything T_T
I already installed TWRP/freegee... but I forgot to insert the custom rom ZIP on the internal storage... And then the back ups I made was took out, and there is no backup currenty on the internal storage. And also the system folder was erased, the main reason why there is no OS....
How do I access the internal storage so I can put in the ZIP for custom rom? I can still boot to recovery for TWRP by pressing vol up+down.
PLEASE HELP! Thanks for all the reply. I just need a tool to access the internal storage to put the custom ROM zip file into the internal storage.
lancelotconquista said:
Hi everyone!
I was trying to install Cyanogenmod on my LGOG F180S, Im new to everything T_T
I already installed TWRP/freegee... but I forgot to insert the custom rom ZIP on the internal storage... And then the back ups I made was took out, and there is no backup currenty on the internal storage. And also the system folder was erased, the main reason why there is no OS....
How do I access the internal storage so I can put in the ZIP for custom rom? I can still boot to recovery for TWRP by pressing vol up+down.
PLEASE HELP! Thanks for all the reply. I just need a tool to access the internal storage to put the custom ROM zip file into the internal storage.
Click to expand...
Click to collapse
I'm also new to android but i believe the only option you have now is to restore to stock and then re-root and put zip in storage.
see if you can go into download mode
----> turn off your phone, press both "Volume Up and Volume Down" button simultaneously
then plug in the usb cable into your phone n computer.
Sent from my LG-F180K using Tapatalk
lancelotconquista said:
How do I access the internal storage so I can put in the ZIP for custom rom? I can still boot to recovery for TWRP by pressing vol up+down.
Click to expand...
Click to collapse
If you are able to ge to TWRP recovery, then the easiest thing for you is to use ADB. Two options: adb push, and adb sideload. Learn about it - there is a lot of info here on XDA on how to set up and use it. This is not specific to a particular phone; it's a very handy tool you can use with any Android device.
Another option would be to flash a stock KDZ, and start the whole process all over again.
kt-Froggy said:
If you are able to ge to TWRP recovery, then the easiest thing for you is to use ADB. Two options: adb push, and adb sideload. Learn about it - there is a lot of info here on XDA on how to set up and use it. This is not specific to a particular phone; it's a very handy tool you can use with any Android device.
Another option would be to flash a stock KDZ, and start the whole process all over again.
Click to expand...
Click to collapse
Thanks very much I'll try the sideload method first, but if worst comes to worst ill try to flash it.
This will be a veeeery steep learning curve for me :v
kt-Froggy said:
If you are able to ge to TWRP recovery, then the easiest thing for you is to use ADB. Two options: adb push, and adb sideload. Learn about it - there is a lot of info here on XDA on how to set up and use it. This is not specific to a particular phone; it's a very handy tool you can use with any Android device.
Another option would be to flash a stock KDZ, and start the whole process all over again.
Click to expand...
Click to collapse
tried to use adb sideload / push:
http://forum.xda-developers.com/showthread.php?t=2317986 <-for HTC One, but the idea is the same
to be sure I also followed this: http://forum.xda-developers.com/showthread.php?t=2272266
When I try to connect ADB sideload on cmd, and type 'adb device', its saying 'List of Devices Attached' but its not displaying my device
I have all the latest drivers for my F180S, including LG United Mobile Drivers... etc etc.
But when I check my device manager, it says 'LG-180S' (no F, weirdly) so its being detected
When I saw that its not working, I tried to re-flash it with official ROM, I followed instructions here:
http://forum.xda-developers.com/showpost.php?p=44874388&postcount=36
it says to 'press vol up+down then connect to computer'
when I try to do it, nothing happens, first its showing that its charging, then it flashes 'LG logo' for 0.5 sec, then its showing a fully charged battery, then a blank screen (the screen is lit up, but theres nothng, just black)
HELP T_T
lancelotconquista said:
tried to use adb sideload / push:
http://forum.xda-developers.com/showthread.php?t=2317986 <-for HTC One, but the idea is the same
to be sure I also followed this: http://forum.xda-developers.com/showthread.php?t=2272266
When I try to connect ADB sideload on cmd, and type 'adb device', its saying 'List of Devices Attached' but its not displaying my device
I have all the latest drivers for my F180S, including LG United Mobile Drivers... etc etc.
But when I check my device manager, it says 'LG-180S' (no F, weirdly) so its being detected
When I saw that its not working, I tried to re-flash it with official ROM, I followed instructions here:
http://forum.xda-developers.com/showpost.php?p=44874388&postcount=36
it says to 'press vol up+down then connect to computer'
when I try to do it, nothing happens, first its showing that its charging, then it flashes 'LG logo' for 0.5 sec, then its showing a fully charged battery, then a blank screen (the screen is lit up, but theres nothng, just black)
HELP T_T
Click to expand...
Click to collapse
Reboot to TWRP and connect your device to your PC.
Open device manager.
Right click at the unknown device (LG-180S), choose "update driver software"
Choose "Browse my computer for..."
Click "Let me pick from a list..."
Choose "ADB Interface", click next
Choose "Android Sooner Single ADB Interface"
continue until the driver installation complete.
Now you can use adb push, or sideload to fix your phone.
When you check using adb devices, it will list your device as recovery
kt-Froggy said:
If you are able to ge to TWRP recovery, then the easiest thing for you is to use ADB. Two options: adb push, and adb sideload. Learn about it - there is a lot of info here on XDA on how to set up and use it. This is not specific to a particular phone; it's a very handy tool you can use with any Android device.
Another option would be to flash a stock KDZ, and start the whole process all over again.
Click to expand...
Click to collapse
arasyi said:
Reboot to TWRP and connect your device to your PC.
Open device manager.
Right click at the unknown device (LG-180S), choose "update driver software"
Choose "Browse my computer for..."
Click "Let me pick from a list..."
Choose "ADB Interface", click next
Choose "Android Sooner Single ADB Interface"
continue until the driver installation complete.
Now you can use adb push, or sideload to fix your phone.
When you check using adb devices, it will list your device as recovery
Click to expand...
Click to collapse
Thanks! Now another question...
Ive pushed the TWRP backups back (The TWRP folder, which includes a file named ".twrps" and then a folder named backups. But when i click restore on TWRP recovery, theres nothing displayed on restore :/ How can I restore it at least?
EDIT: nevermind, I put a name on the .twrps file (changed it to test.twrps) and it worked
Thanks anyway for the device manager trick! I would have not done it witout your help T_T Thanks thanks!
hi people,i wanna share a fix solution for any smartwatch 3 with working fastboot mode...
so,presuming u already have adb drivers installed lets proceed
https://drive.google.com/open?id=0B14BmzmcIZ4cVDBjRnliUDVXU1k is link to a shared folder with all needed files,inside folder are :
repacked rom 5.0.1 - swr50.zip
stock recovery image - swr50.img
twrp recovery image for old rom version - twrp.img
twrp recovery image for new rom version - twrpnew.img
update packages that can also be sideloaded if watch dosent update itself after first flash
updatep-k.zip -its from verison lwx48p tp lwx48k
then k to d and d to lca43(5.1.1)
so,boot into fastboot and fastboot boot twrp.img (that will boot twrp image on watch).then,adb push swr50.zip /sdcard/swr50.zip
in twrp push install and select the newly copied swr50.zip flashable rom...flash it,then adb reboot
let watch reboot,presuming all went fine,ull watch will boot in 5.0.1 rom,let it connect to phone.inside settings,open options/about,and push built version until u get dev mode...in dev mode enable usb debug,confirm also on phone
so right now u have watch connected to pc with usb debug on....write adb reboot bootloader ,so watch goes in fastboot again
now,flash stock recovery...fastboot flash recovery swr50.img (watch will get the stock recovery),after u can fastboot continue
right now u can update watch,connected to phone,via own update ota service,settings/about/system update,it will download and install next version,the update again and again.if u dont wanna wait thatu can adb sideload files i provided,its actualy stock ota update
so....
adb reboot recovery,select adb sideload,and adb sideload updatep-k.zip,reboot watch and let update,then sideload again updatek-d.zip,reboot and let it update,then again last update
AFTER THIS UPDATE TWRP.IMG NO LONGER WORK,DONT BOOT IT,WATCH WILL ENTER BOOT LOOP,WE WILL BOOT TWRPNEW.IMG.....becouse 5.1.1 updated also boot image,so fastboot twrpnew.img if u wanna use twrp in some way.....
i hope its was helpfull,any questions fell free to leave,im no developer,i just like to play with things
BIG thanx to those who packed,repacked flashes and recovery images!!!!
l
alex_SW said:
hi people,i wanna share a fix solution for any smartwatch 3 with working fastboot mode...
so,presuming u already have adb drivers installed lets proceed
https://drive.google.com/open?id=0B14BmzmcIZ4cVDBjRnliUDVXU1k is link to a shared folder with all needed files,inside folder are :
repacked rom 5.0.1 - swr50.zip
stock recovery image - swr50.img
twrp recovery image for old rom version - twrp.img
twrp recovery image for new rom version - twrpnew.img
update packages that can also be sideloaded if watch dosent update itself after first flash
updatep-k.zip -its from verison lwx48p tp lwx48k
then k to d and d to lca43(5.1.1)
so,boot into fastboot and fastboot boot twrp.img (that will boot twrp image on watch).then,adb push swr50.zip /sdcard/swr50.zip
in twrp push install and select the newly copied swr50.zip flashable rom...flash it,then adb reboot
let watch reboot,presuming all went fine,ull watch will boot in 5.0.1 rom,let it connect to phone.inside settings,open options/about,and push built version until u get dev mode...in dev mode enable usb debug,confirm also on phone
so right now u have watch connected to pc with usb debug on....write adb reboot bootloader ,so watch goes in fastboot again
now,flash stock recovery...fastboot flash recovery swr50.img (watch will get the stock recovery),after u can fastboot continue
right now u can update watch,connected to phone,via own update ota service,settings/about/system update,it will download and install next version,the update again and again.if u dont wanna wait thatu can adb sideload files i provided,its actualy stock ota update
so....
adb reboot recovery,select adb sideload,and adb sideload updatep-k.zip,reboot watch and let update,then sideload again updatek-d.zip,reboot and let it update,then again last update
AFTER THIS UPDATE TWRP.IMG NO LONGER WORK,DONT BOOT IT,WATCH WILL ENTER BOOT LOOP,WE WILL BOOT TWRPNEW.IMG.....becouse 5.1.1 updated also boot image,so fastboot twrpnew.img if u wanna use twrp in some way.....
i hope its was helpfull,any questions fell free to leave,im no developer,i just like to play with things
BIG thanx to those who packed,repacked flashes and recovery images!!!!
l
Click to expand...
Click to collapse
Thanks for putting this together. My sw3 has been stuck on the MM dots / symbols for some time. After several attempts of running various roms, img, simg, XC, etc, I could get no further than the original software issue. With your post, I was able to get it to the LCA43 update. Although, for some reason I could not use the twrp.img in your file list (I found another one) and I could not adb the recovery file (I had to flash it), nevertheless, it provided a way for me to update the sw3. I did not flash the updates, but just let the watch do it. While that was a slow process, it was working so I continued...until.
I could not get the MM update to work though. It downloaded and installed on the sw3. But when booting up, I got the dreaded 4 dots / symbols again. If you are still around and have any ideas of updating this procedure to include the MM updates, it would be much appreciated. Again, the XC does not work for me even though both the repair and update options in the software said they were successfully installed.
Hi!
I really need to do this for activate the NFC and use to check glicemia on the watch.
But i'm stuck almost at the first point.
I already activate the adb on the watch and put him "runnig fastboot".
On the pc I write on command prompt "adb reboot bootloader" and returns: "error: device '(null)' not found"
Anyone can helps?
Regards,
Same position as Moitas
Realy would appreciate if somebody could help me and at the same time moitas. I run windows10 and have the same problem. The device is called Tetra when it shows up in fastboot and I can´t get any driver to work with it. Have tried several differet ones but none seem to fit. Any clever one with a solution I would salute you
@moitas @tobas70 you need to install the correct drivers - http://forum.xda-developers.com/attachment.php?attachmentid=2480396
ajolly said:
@moitas @tobas70 you need to install the correct drivers - http://forum.xda-developers.com/attachment.php?attachmentid=2480396
Click to expand...
Click to collapse
Thanks Ajolly! I finally managed to get it done. As new to this rooting buisness there were a lot of steps that where more complicated than the manual I followed applied
Hi! i have problem after downgrade...
After I push SWR50.zip and reboot, my devices is unauthorized. When i enter in fastboot manually there's any devices (null). I install drivers like You said, and form adb, google. If somebody can help me this i will be very grateful
any one can help me. After failed up SW3 by sideload, they ignored PC conncetion. Try "adb devices", fastboot mode, recovery mode, MTP, - anything happend in device manager.
ajolly said:
@moitas @tobas70 you need to install the correct drivers - http://forum.xda-developers.com/attachment.php?attachmentid=2480396
Click to expand...
Click to collapse
I just got a new SWR50 for the sole purpose of using NFC (with FreeStyle Libre).
On the Win10 PC I don't have "Android Device" as a hardware type. -- I'm not sure if this is causing the problem that in Fastboot (white background) I cannot communicate with the watch from the PC anymore.
Also, when turned on for the first time watch automatically upgrades to M1D64T and I don't seem to be able to stop that and don't seem to be able to downgrade to be able to use this package.
Any suggestions? Thanks
Restore to the latest firmware
After downgrading to LCA43, what would be the easiest way to restore the watch to the latest firmware, is there a real factory reset?
Not pair after downgrade
I have downgraded from version M1D64T to LWX48P and now my phone do not see the watch in bluetooth devices. I tried few things to start BT working like:
- remove Android Wear from phone
- clear Google Play Services
- send few intent through adb like bluetooth.REQUEST_DISCOVERABLE
- return to M1D64T by Sony PC Companion
Bluetooth still not works and I cannot connect to any phone.
Maybe somebody have an idea how to repair my watch?
Ok, I've got another issue when downgrading the watch.
When I get to the Install the swr50.zip it starts to complain.
It says, Unable to mount /cache, Unable to mount data and so on. So clearly something is not going right at this point (or earlier more likely).
What's going wrong and how do I fix it?
Same thing here - /data can't be mounted read/write
I'm seeing the same thing. I can use "adb shell" and "mount -r /data" (readonly) which works, but when I try to mount it normally ("mount /data") I get an error about a bad argument. This is certainly related to the errors re. not being able to mount /data, which I see when I try using twrpnew.img to install the SWR50.zip image.
I'm stuck!
Maybe a solution...
(I'm still going through applying updates, but this looks hopeful!)
I found that apparently the "unable to mount data" seems to have to do with the /data partition (in my case, "/dev/block/mmcblk0p32") having some internal flag which seemed to not allow it to be mounted read/write. I could do "adb shell" to get to the watch and then to "mount -r /data" and that worked just fine. I decided to rebuild the entire /data partition. Use "adb shell" to get a shell prompt on the watch, do "mount" to make sure /data is NOT mounted. If it is, do "umount /data", which should unmount it. you can see what's being mounted where via "cat /etc/fstab". You want to rebuild the disk partition which will be mounted on /data. On my watch this was "/dev/block/mmcblk0p32", so "/sbin/make_ext4fs /dev/block/mmcblk0p32". Then "exit" to get back to your system where you're running adb.
So, I followed the "How to install NFC on Sony Smartwatch3" instructions (I'm not allowed to post a link or else I would, but you probably have these instructions already.)
(I'm doing the "downgrade" part of the instructions, which is where the "install" failed.)
Just after "fastboot boot twrpnew.img", I inserted the above work to rebuild the /data partition. DO NOT mount /data after having rebuilt it! You should also should see that /cache is NOT mounted at this time. Do "exit" to get back to your adb system and continue following instructions at "adb push SWR50.zip /sdcard/", and the "install" worked for me after this!
frippegubben said:
Ok, I've got another issue when downgrading the watch.
When I get to the Install the swr50.zip it starts to complain.
It says, Unable to mount /cache, Unable to mount data and so on. So clearly something is not going right at this point (or earlier more likely).
What's going wrong and how do I fix it?
Click to expand...
Click to collapse
Sony Smartwatch SWR50 unable to install SWR50.zip
Hello Friends,
Iam trying to configure NFC on my Sony Smart Watch 3. After command adb push SWR50.zip /sdcard/, I try to intall SWR50.zip, It's not flashing.
It says Failed with message " UNABLE TO MOUNT" etc
Can you kindly help please
KIR71 said:
Hello Friends,
Iam trying to configure NFC on my Sony Smart Watch 3. After command adb push SWR50.zip /sdcard/, I try to intall SWR50.zip, It's not flashing.
It says Failed with message " UNABLE TO MOUNT" etc
Can you kindly help please
Click to expand...
Click to collapse
I was working with a Sony Smartwatch 3 a few years ago (using the NFC to read a Blood Glucose sensor) and encountered this same error during installation of some of the code. Here are my notes on the solution, in case it helps:
I found that apparently the "unable to mount data" seems to have to do with the /data partition (in my case, "/dev/block/mmcblk0p32") having some internal flag which seemed to not allow it to be mounted read/write. I could do "adb shell" to get to the watch and then to "mount -r /data" and that worked just fine. I decided to rebuild the entire /data partition. Use "adb shell" to get a shell prompt on the watch, do "mount" to make sure /data is NOT mounted. If it is, do "umount /data", which should unmount it. you can see what's being mounted where via "cat /etc/fstab". You want to rebuild the disk partition which will be mounted on /data. On my watch this was "/dev/block/mmcblk0p32", so "/sbin/make_ext4fs /dev/block/mmcblk0p32". Then "exit" to get back to your system where you're running adb.
Hope this helps! Good luck!
Thank you for this tutorial, I'm having the same problem. My swr50 stuck on the dots screen after battery replacement. I tried to follow the steps above but my system does not see the device at all.
I tried to add legacy device drivers but it come back with code 10.
After connecting swr50 device manager don't detect any device and I can't install drivers. So when I run ADB I get message "device null" Did someone had the same problem? Is there any solution?
Help please, When I plug in my watch to the charger sometimes it gets stuck on sony logo and sometimes doesn't display anything also tried connecting to pc but it keeps on booting also tried pressing the power key to get into the fastboot mode but doesn't work.
Hi all,
It seems I come back a n00b every few years.
I rooted my Zenfone 2 to remove some clutter and guess what I did today? I updated. Didn't know that would brick my phone but well here I am.
I followed these steps:
http://www.asus-zenfone.com/2015/06/how-to-update-ota-without-bootloop-on-rooted-zenfone2.html
Only to find that it wouldn't boot.
Went into recovery and tried to factory reset... went on for more than 15 minutes (I didn't want to stop the process....). I then had to hard reset then boot into recovery and tried to wipe cache which yielded nothing...
BTW, I think the failed wipe and reset messed up permissions as fastboot yields an error (even though the "flash recovery" bit seems to work).
I tried installing TWRP and it only boots back into fastboot. Reinstall the recovery from the link above and I can go back into recovery but can't seem to use any of the functions.
Any ideas?
p.s. I did do a few searches. Can't find anything specific about
I also tried using the adb sideload to sideload official firmware but it yields "error: device not found" and then goes back into regular recovery...
adramelch said:
I also tried using the adb sideload to sideload official firmware but it yields "error: device not found" and then goes back into regular recovery...
Click to expand...
Click to collapse
Have you installed all your drivers correctly?
In TWRP, have you gone into advanced and selected ADB Sideload? I've also had issues with sideloading, I think it's a TWRP issue though.
Here's what you can try:
Boot into TWRP and make sure the phone is detected on the PC.
open up adb
type: adb devices
hit enter
your device should be listed
type: adb push -p rom.zip /sdcard0/
-for push, it's just the command to push files to your phone. Alternatively, pull is for taking files from your phone (in the event you can't boot up and need a certain file)
-for -p, it just means show progress, so in CMD you'll see a percentage sign which is always a good thing to know
-for rom.zip you type in the location of the file
-for /sdcard0/ you can leave that, as that is the send destination and should land right in your main folder.
And once the file is transferred over, install through TWRP.
Wipe Dalvik/Cache.
Reboot system.
Profit.
If all this doesn't work, try a microsd card with the file on it.
EDIT: I just realized you meant you meant stock recovery. In that case...it should still allow you to adb sideload, but I'm not sure. As long as you can still use ADB, you can follow my instructions above.
adb push yields "error: closed"
adb sideload says it needs adb 1.0.32 to do operation...
Try using microSD, download the latest firmware on asus website, then rename the zip to MOFD_UPDATE.zip and copy it to your microSD then go to recovery mode and it'll install the update. it took sometime be patient
badaboomBURP said:
Try using microSD, download the latest firmware on asus website, then rename the zip to MOFD_UPDATE.zip and copy it to your microSD then go to recovery mode and it'll install the update. it took sometime be patient
Click to expand...
Click to collapse
Recovery doeasn't have option "Update from zip" but this time, the adb sideload command worked for some reason...
adramelch said:
Recovery doeasn't have option "Update from zip" but this time, the adb sideload command worked for some reason...
Click to expand...
Click to collapse
in my experience, it automatically install the zip if i go to recovery
Update: Sideload worked and I've been back to stock since. Didn't want to flash because I was ok with stock but didn't want the clutter. Will find another stable firmware if need be.
Thanks again for the help!
Good afternoon, I need help in TWRP mode I can not mark usb-otg in mount.
My terminal does not have a rom because I mistakenly delete all the data.
My idea was to put the rom in a pendrive otg and intalarla from TWRP but I can not check the corresponding box.
In Fastboot mode either since my pc does not recognize the terminal, I have tried all the ports of the pc and all the cables that I have.
The drivers are well installed and adb and others work correctly.
I need your help, since the phone works very well and I changed the battery recently.
Thanks in advance.
can you mount mtp in twrp? perhaps you could try loading a rom from your pc to your phone via adb sideload in twrp.
NightRaven49 said:
can you mount mtp in twrp? perhaps you could try loading a rom from your pc to your phone via adb sideload in twrp.
Click to expand...
Click to collapse
thanks, there is some tutorial to do this. I'm pretty new in these things
to mount mtp, boot twrp, then go to mount. there will be a button on the bottom right that says enable mtp (if mtp is disabled) and tap it. if mtp is already enabled, the button will say disable mtp, so you don't have to do anything here. just plug your phone into your computer and see if it gets detected. if it doesn't get detected, again try the different ports on your computer or switch cables.
once your phone is detected, you have 2 options.
1) mtp allows files to be copied over from your pc to your phone while in twrp. so you can just copy a rom file into your internal storage and flash normally.
2) you can also flash the rom through adb sideload. first, place the rom in an easily accessible directory, such as directly on C:\. next, you can start adb on your computer by opening up terminal/powershell and typing
Code:
adb start-server
you should get a message saying adb daemon is now running on port xxx. next, open up the adb sideload dialog in twrp through advanced >> adb sideload, then swipe to start the service. just to be sure your phone is detected by your pc, type
Code:
adb devices
your phone should show up on the terminal with its serial number. now navigate to the folder where your rom is and flash it.
Code:
cd C:\
adb sideload rom.zip
make sure your phone doesn't get disconnected during the process of flashing.
I'd recommend 1) since it's a more familiar method of flashing.
Try formatting your Usb pen drive as FAT32, it worked for me. My pen drive was formatted as NTFS previously and twrp did not allow me to check box the "usb otg" option, but after formatting as FAT32 it worked like a charm.
Good luck