Related
I didn't to a NANDROID backup before trying to flash a new ROM (fail I know). I had factory reset my phone before flashing the new ROM, but the ROM that was flashed hasn't installed correctly and the phone no longer powers completely on. I would like to just throw a different ROM/gapps on the SD card, but I can no longer access it on my computer since the phone will not completely boot up.
Someone suggested somewhere that I mount the USB Storage from recovery, but in the mount + storage recovery section all I see is mount /data, mount /system, and mount /cache, none of which make the GNEX storage available on my computer.
Any suggestions for fixing this problem, or for simply accessing the SD card on my computer without the phone turning completely on?
Thank you.
You can adb push a ROM while booted in a custom recovery. You should check out the stickies in this forum & the general forum.
Download the factory image from google for your phone. Extract it and get system.img from it (you have to extract it a few times). Get adb/fastboot setup by installing the correct drivers and the android sdk (there may be files posted here at xda with just the files needed for adb/fastboot). Then put system.img in the same folder as fastboot.exe (assuming you use windows).
Connect your phone while in bootloader (both volume keys + power) and from a command prompt in that directory, type:
1) fastboot flash system system.img
2) fastboot reboot
It won't wipe anything other than /system.
I'm getting < waiting for device > when executing the first command (fastboot flash system system.img)
I tried a few solutions for this error based on information I could find, such as reinstalling the drivers from Samsung, but nothing seems to have worked. Any help here? I really just need to get any form of a working ROM installed so I can boot the phone.
Paybacks1 said:
I'm getting < waiting for device > when executing the first command (fastboot flash system system.img)
I tried a few solutions for this error based on information I could find, such as reinstalling the drivers from Samsung, but nothing seems to have worked. Any help here? I really just need to get any form of a working ROM installed so I can boot the phone.
Click to expand...
Click to collapse
You need to get your phone to be recognized by your pc. It is a driver problem. Try following some of the steps in this thread.
mwalt2 said:
You need to get your phone to be recognized by your pc. It is a driver problem. Try following some of the steps in this thread.
Click to expand...
Click to collapse
Paybacks1 said:
I'm getting < waiting for device > when executing the first command (fastboot flash system system.img)
I tried a few solutions for this error based on information I could find, such as reinstalling the drivers from Samsung, but nothing seems to have worked. Any help here? I really just need to get any form of a working ROM installed so I can boot the phone.
Click to expand...
Click to collapse
I have the same problem. Going to take a look at what mwalt suggested tomorrow. Paybacks, if you find a solution, can you please post it here? Thanks.
mwalt2 said:
You need to get your phone to be recognized by your pc. It is a driver problem. Try following some of the steps in this thread.
Click to expand...
Click to collapse
I was finally able to flash the system.img from Google, but see no change. What is expected to happen once this .img has been pushed?
EDIT: Ended up flashing the entire .zip installation instead of just the system.img file and I have a stock install atm. Thank you for the help!
To Man_Utd, I ended up just re-executing the superboot r5 while in bootloader and it seemed to help recognize the phone..-shrug-.
I have a nexus 7 2013 LTE build KOT49H
I initially managed to unlock and root using nrt 1.8...everything was perfect...there was some confusion getting adb setup though..
(for WugFresh...your instructions are fantastic but you should add a line to "check your device for the message to accept a connection for adb and select ok"...I found myself waiting and waiting, staring at my computer screen thinking that the nrt was hanging when all I needed to do was press "ok" on my device.)
Like I said...everything was perfect but I had to go one step further...
I then installed cyanogenmod 10.2 using twrp...tihs also went fine but I hated it and wanted to get back to my original google os. I had a really hard time getting adb set up once cyanogen was installed but once I finally did I was able to get back to stock again using nrt 1.8.
So now I'm back to stock image KOT49H. Everything runs fine and I see the unlocked logo when I boot so I assume I'm still unlocked.
Here's the problem..
When I try to root now, (I always run the NRT driver test until I get "success" message first) my device hangs on the "Booting modified boot.img to enable..." message.
And I mean hangs...can't even power it down without popping the cover and disconnecting the battery! Thankfully this gets me back to a running device but I still want to root this thing.
Any idea what might be wrong or where I should go to from here?
Thanks for any help you can suggest!
Did you re-enable USB debugging? Another thing is to switch to PTP mode instead of MTP. If none of that is the issue, it may be drivers, fire up wugs toolkit, hook up your device, and click the button "Full Driver Installation Guide", skip to Step 3 tab, and run the "Full Driver Test", if it fails then you're going to need to run through the steps in that "Full Driver Installation Guide, going through each step.
Well all you need to do for root is flash supersu.zip binary. If you have twrp on your device, boot to recovery. When you power on, hold down the volume down button also. When in boot loader mode, select recovery. If its not booting, you could just wipe to factory reset. Flash your supersu zip you'll be good.
Sent from my Nexus 7 using xda app-developers app
mdamaged said:
Did you re-enable USB debugging? Another thing is to switch to PTP mode instead of MTP. If none of that is the issue, it may be drivers, fire up wugs toolkit, hook up your device, and click the button "Full Driver Installation Guide", skip to Step 3 tab, and run the "Full Driver Test", if it fails then you're going to need to run through the steps in that "Full Driver Installation Guide, going through each step.
Click to expand...
Click to collapse
Thanks for the response...
All these check...I do have to switch to PTP to get adb functional and I do get success on the full driver test before I try rooting...device still hangs at "Booting modified boot.img to enable running privileged commands" message and then wont power down without disconnecting battery...
Which recovery are you on stock or still on twrp? If still on twrp, you might want to try flashing the supersu.zip yourself, just get the latest SuperSU put it on your device, and boot into twrp and manually flash it like datallboy suggests, this eliminates the PC/drivers/usb connection as a possible issue.
If you are on stock recovery either flash twrp, or if you want to keep stock recovery, you can boot into twrp temporarily without replacing the stock recovery.
datallboy said:
Well all you need to do for root is flash supersu.zip binary. If you have twrp on your device, boot to recovery. When you power on, hold down the volume down button also. When in boot loader mode, select recovery. If its not booting, you could just wipe to factory reset. Flash your supersu zip you'll be good.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the suggestions...
I lost twrp when I went back to stock build.
Sorry...I'm real green at all of this...
You think I should:
power up to fastboot mode...select boot loader mode...then select recovery to see if it boots?
You need to be real clear for me, I'm a total newb
I would need a link to thorough instructions for wiping to factory reset and flashing the supersu.zip...I do have adt installed and have my path modified so that I can run instructions like "adb devices" in a command window but I'm unclear as to where to place files so they will be seen if I try to flash them via adt. (like I say...this is all new to me and I'm not even sure if that last sentence makes sense)
mdamaged said:
Which recovery are you on stock or still on twrp? If still on twrp, you might want to try flashing the supersu.zip yourself, just get the latest SuperSU put it on your device, and boot into twrp and manually flash it like datallboy suggests, this eliminates the PC/drivers/usb connection as a possible issue.
If you are on stock recovery either flash twrp, or if you want to keep stock recovery, you can boot into twrp temporarily without replacing the stock recovery.
Click to expand...
Click to collapse
Thanks for responding!
TWRP was wiped when I went back to stock build...I'm assuming I have stock recovery now but when your device freezes in fastboot mode and wont power down without pulling the battery you cable you gotta wonder if you have any recovery at all!!!
I'll need instruction on how to flash twrp again...but I believe that this is the step that WugFresh's NRT is trying to do when the device freezes.
SMELZBAD said:
Thanks for responding!
TWRP was wiped when I went back to stock build...I'm assuming I have stock recovery now but when your device freezes in fastboot mode and wont power down without pulling the battery you cable you gotta wonder if you have any recovery at all!!!
I'll need instruction on how to flash twrp again...but I believe that this is the step that WugFresh's NRT is trying to do when the device freezes.
Click to expand...
Click to collapse
I typed this up on the fly so pardon any mistakes, there's more than one way to do this, but I'm basing this on already having wugs toolkit installed and updated and configured for your device on the PC you're going to do this on.
Plug device in, enable USB debugging mode, connect to PC, verify you can access your device through the PC, get the latest UPDATE-SuperSU-v1.XX zip, save it to your device (in the root of the sdcard).
EDIT: OR, even better, you can just boot the device and download it with chrome or whatever and save it to the sdcard, then you can continue:
Open windows explorer and navigate to (assuming you picked the default install directory):
C:\Program Files (x86)\WugFresh Development\data
...in that window, hold down shift, right click, select "Open command windows here", in it, type:
adb devices
...if nothing shows up post back (screenshot would be nice), if your device shows up, then open another windows explorer window and navigate to:
C:\Program Files (x86)\WugFresh Development\data\Recovery_Custom\TWRP\
...and copy the img (mine is openrecovery-twrp-2.6.3.1-flo.img) file you see in there to the other explorer window I told you to open earlier, now assuming you put the SuperSU file on your device in the root folder of the device, you should be able to do:
fastboot boot openrecovery-twrp-2.6.3.1-flo.img
This should reboot your device and boot twrp (this method does not replace whatever recovery you have on there now).
If you want to flash twrp and replace your current recovery you'd want to do:
fastboot flash recovery openrecovery-twrp-2.6.3.1-flo.img
Then once in twrp recovery you can select flash file, navigate to the UPDATE-SuperSU-v1.XX.zip file on your device, select it, and swipe to flash, reboot, run/install busybox and see what happens..it will let you know if there is a problem with root.
mdamaged said:
I typed this up on the fly so pardon any mistakes, there's more than one way to do this, but I'm basing this on already having wugs toolkit installed and updated and configured for your device on the PC you're going to do this on.
Plug device in, enable USB debugging mode, connect to PC, verify you can access your device through the PC, get the latest zip, save it to your device (in the root of the sdcard).
Open windows explorer and navigate to (assuming you picked the default install directory):
C:\Program Files (x86)\WugFresh Development\data
...in that window, hold down shift, right click, select "Open command windows here", in it, type:
adb devices
...if nothing shows up post back (screenshot would be nice), if your device shows up, then open another windows explorer window and navigate to:
C:\Program Files (x86)\WugFresh Development\data\Recovery_Custom\TWRP\
...and copy the img (mine is openrecovery-twrp-2.6.3.1-flo.img) file you see in there to the other explorer window I told you to open earlier, now assuming you put the SuperSU file on your device in the root folder of the device, you should be able to do:
fastboot boot openrecovery-twrp-2.6.3.1-flo.img
This should reboot your device and boot twrp (this method does not replace whatever recovery you have on there now).
If you want to flash twrp and replace your current recovery you'd want to do:
fastboot flash recovery openrecovery-twrp-2.6.3.1-flo.img
Then once in twrp recovery you can select flash file, navigate to the UPDATE-SuperSU-v1.XX.zip file on your device, select it, and swipe to flash, reboot, run busybox and see what happens.
Click to expand...
Click to collapse
Thanks a ton for the instruction!
I'm starting to make sense of this.
Found some other instruction for getting twrp back on the device which I think I'll try before flashing the superSU:
They're exactly what you're describing. I've also figured out where the flashboot.exe stuff is on my computer and added twp.img file there. I'' try getting twrp on and then I'll flash the superSU via twrp.
It'll probably be tomorrow before I get a chance to try all this but I'll be sure to post back once I do.
I'm still in the dark as to why missing this superSU thingy would be causing the device to freeze up the way it does when I try to root using WugFresh's NRT...I thought that flashing twrp and superSU is what the NRT is trying to do when it tries to root my device???
Anyway gtg...thanks all for assisting...I'll post back after the flash attempts...hopefully with happy news!
SMELZBAD said:
Thanks a ton for the instruction!
I'm starting to make sense of this.
Found some other instruction for getting twrp back on the device which I think I'll try before flashing the superSU:
They're exactly what you're describing. I've also figured out where the flashboot.exe stuff is on my computer and added twp.img file there. I'' try getting twrp on and then I'll flash the superSU via twrp.
It'll probably be tomorrow before I get a chance to try all this but I'll be sure to post back once I do.
I'm still in the dark as to why missing this superSU thingy would be causing the device to freeze up the way it does when I try to root using WugFresh's NRT...I thought that flashing twrp and superSU is what the NRT is trying to do when it tries to root my device???
Anyway gtg...thanks all for assisting...I'll post back after the flash attempts...hopefully with happy news!
Click to expand...
Click to collapse
Wug's toolkit is doing exactly that, the main difference in doing it manually is we get to see where the problem is.
If this fails then I would probably say you should backup anything on your device you don't want wiped, and try one click restore and try rooting again.
Good luck.
mdamaged said:
I typed this up on the fly so pardon any mistakes, there's more than one way to do this, but I'm basing this on already having wugs toolkit installed and updated and configured for your device on the PC you're going to do this on.
Plug device in, enable USB debugging mode, connect to PC, verify you can access your device through the PC, get the latest UPDATE-SuperSU-v1.XX zip, save it to your device (in the root of the sdcard).
EDIT: OR, even better, you can just boot the device and download it with chrome or whatever and save it to the sdcard, then you can continue:
Open windows explorer and navigate to (assuming you picked the default install directory):
C:\Program Files (x86)\WugFresh Development\data
...in that window, hold down shift, right click, select "Open command windows here", in it, type:
adb devices
...if nothing shows up post back (screenshot would be nice), if your device shows up, then open another windows explorer window and navigate to:
C:\Program Files (x86)\WugFresh Development\data\Recovery_Custom\TWRP\
...and copy the img (mine is openrecovery-twrp-2.6.3.1-flo.img) file you see in there to the other explorer window I told you to open earlier, now assuming you put the SuperSU file on your device in the root folder of the device, you should be able to do:
fastboot boot openrecovery-twrp-2.6.3.1-flo.img
This should reboot your device and boot twrp (this method does not replace whatever recovery you have on there now).
If you want to flash twrp and replace your current recovery you'd want to do:
fastboot flash recovery openrecovery-twrp-2.6.3.1-flo.img
Then once in twrp recovery you can select flash file, navigate to the UPDATE-SuperSU-v1.XX.zip file on your device, select it, and swipe to flash, reboot, run/install busybox and see what happens..it will let you know if there is a problem with root.
Click to expand...
Click to collapse
Followed your instructions...everything went as it should until I got to:
fastboot boot openrecovery-twrp-2.6.3.1-deb.img
instead of rebooting the device I only got waiting for device message in command window...
is device supposed to be put in bootloader mode before entering this instruction maybe???
okay I got twrp to flash...took like .7 seconds so I guess it was already on there...
when I tried to flash UPDATESuperSU (and by flash I assume you mean install???)
I get:
Updating partition details...
E: Unable to open zip file.
Error flashing zip ' /sdcard/UPDATE-SuperSU-v1.89.zip
Updating partition details...
and the in red underneath: Failed
and the 3 twrp button choices of home Wipe cache/davlik and Reboot System
I selected reboot system and then got message "this device is not rooted swipe to install SuperSU now
I swiped...and the system has rebooted and I now have SuperSU installer app icon in apps bit after running root checker I get device is not properly rooted message
I then ran the SuperSU installer app and it gave me an option to update via the play store...which I did...then ran SuperuserSU which was now updated and installed and it completed rooting...after rebooting the device Root Checker now shows device properly rooted!
THANKS A TON GUYS!!!
SMELZBAD said:
okay I got twrp to flash...took like .7 seconds so I guess it was already on there...
when I tried to flash UPDATESuperSU (and by flash I assume you mean install???)
I get:
Updating partition details...
E: Unable to open zip file.
Error flashing zip ' /sdcard/UPDATE-SuperSU-v1.89.zip
Updating partition details...
and the in red underneath: Failed
and the 3 twrp button choices of home Wipe cache/davlik and Reboot System
I selected reboot system and then got message "this device is not rooted swipe to install SuperSU now
I swiped...and the system has rebooted and I now have SuperSU installer app icon in apps bit after running root checker I get device is not properly rooted message
I then ran the SuperSU installer app and it gave me an option to update via the play store...which I did...then ran SuperuserSU which was now updated and installed and it completed rooting...after rebooting the device Root Checker now shows device properly rooted!
THANKS A TON GUYS!!!
Click to expand...
Click to collapse
Curious. It sounds like a permissions problem, not sure if fix permissions would have helped (no need to try if it's working as it should).
Oh well, glad to help and that it's sorted.
mdamaged said:
Curious. It sounds like a permissions problem, not sure if fix permissions would have helped (no need to try if it's working as it should).
Oh well, glad to help and that it's sorted.
Click to expand...
Click to collapse
Ya...something likely still abit wacky...I'll be sure to post if anything weird starts happening but for now all is good...I'm definitely rooted though...I was just able to mount a flash drive via Stick Mount and run a video off of it!
Please help! I am new to this and am worried I bricked my phone.
I successfully rooted my Verizon Samsung Galaxy Nexus using a toolkit. It was then working fine with 4.2.2. I wanted to install Shiny Rom 4.4.2. I thought I successfully backed up apps and data using Titanium Backup.
I successfully moved the correct zip files to my phone, and realized I needed Clockworkmod recovery. I followed a procedure to get this on my phone by using my computer's command prompt. I successfully booted into Clockworkmod recovery and followed the process of wiping data/factory reset, successfully installed radio and bootloader recommended to install with ShinyROM but got stuck and could not install the ShinyROM itself. I think it is because it requires a later version of Clockworkmod. The one I downloaded using the procedure was 5.5.0.4, but I think I need a later version. I tried following the same procedure using my computer's command prompt and it got stuck at "waiting for device". I cannot get out of Clockworkmod recovery now (even battery pull, etc.). I then found some threads saying I need to restore my old ROM first. (I think) the only ROM on my phone is ShinyROM. I am stuck and stressed out because I do not know of a way of "pushing" the new version of Clockworkmod to my phone.
Can I fix this, or do I need to start shopping?
[email protected] said:
Please help! I am new to this and am worried I bricked my phone.
Can I fix this, or do I need to start shopping?
Click to expand...
Click to collapse
i think u already wiped data partition at first, that why your Rom installation aborted bcoz recovery cant mount any partition.
still got your old system partition here.
from recovery ~ try adb sideload your shinyRom. can your pc detected bootloader (fastboot)/recovery?
memaro_maro said:
i think u already wiped data partition at first, that why your Rom installation aborted bcoz recovery cant mount any partition.
still got your old system partition here.
from recovery ~ try adb sideload your shinyRom. can your pc detected bootloader (fastboot)/recovery?
Click to expand...
Click to collapse
Regarding partition, I have an option to wipe cache partition. Should I do this?
Update
Well, I went ahead and tried this, and still could not install ShinyROM.
I tried to follow a procedure in the link to use ADB sideload.
I downloaded (full) SDK and updates and updated the drivers. When I get to the following steps from the procedure...
-Boot your device in recovery mode (Android logo with a exclamation mark) and connect your device to PC
-Hold down "power" button first, followed quickly by "volume up" button. You should now see the recovery menu
I only boot to CWM and there is no Android with Exclamation mark. Holding down power button only selects whichever option is highlighted within CWM.
Also, it seems within CWM, there is supposed to be an option to sideload a zip file. This option does not exist in my version of CWM.
[email protected] said:
Regarding partition, I have an option to wipe cache partition. Should I do this?
Update
Well, I went ahead and tried this, and still could not install ShinyROM.
I tried to follow a procedure in the link to use ADB sideload.
I downloaded (full) SDK and updates and updated the drivers. When I get to the following steps from the procedure...
-Boot your device in recovery mode (Android logo with a exclamation mark) and connect your device to PC
-Hold down "power" button first, followed quickly by "volume up" button. You should now see the recovery menu
I only boot to CWM and there is no Android with Exclamation mark. Holding down power button only selects whichever option is highlighted within CWM.
Also, it seems within CWM, there is supposed to be an option to sideload a zip file. This option does not exist in my version of CWM.
Click to expand...
Click to collapse
set up fastboot and flash twrp then.
xzilem said:
set up fastboot and flash twrp then.
Click to expand...
Click to collapse
Thanks. I found another thread that led me to the same conclusion, except I was able to do it with CWM and fastboot the latest version using ADB sideload. I still haven't posted enough to link, but here were the details from user camblue.
"
If you know how to use ADB you can always fastboot a recovery.img,,,,this thing is almost impossible to truly brick. IN order to get into fastboot just connect to your computer and run adb with these commands
adb reboot bootloader
once in fastboot mode write this
fastboot devices
that will tell you if your device is connected and reading in fastboot mode if it is you will see something like fastboot and some numbers next to it. If nothing you do not" have the fastboot drivers installed.
then to fastboot flash a recovery.img write this
fastboot flash recovery r3-recovery-clockwork-touch-6.0.0.4-nexus7-modaco.img (or whatever recovery.img you are using or have in your tools folder of you SDK location).
and in order to get right into CWM if you cant boot write this
fastboot boot r3-recovery-clockwork-touch-6.0.0.4-nexus7-modaco.img
hope that helps
"
Hello. I need your help. I have the LG E980 with 4.4.2. I was trying to set this up as a spare phone but for some reason could not get an email program to work with my companies "Notes Traveler" program. I'm able to achieve syncing with my S4 active though. I oulled the email APK off of the S4 active and that resolved the problem temporarily. I read up and found out that the CM11 ROM would resolve this issue. Anyway, I installed a recovery program and did a nanodroid back up only to realize that my EXT_SD card was not being recognized. Si I did a factory reset now I get a boot error and can only get to the recovery program.
It will not recognize my external SD card and I'm afraid that possibly I corrupted the boot image or recovery? Any suggestions how to get out of this boot? Is there a way I can drag a Update.Zip to the internal SD card and it will completely over write boot and all files?
mikelets456 said:
Hello. I need your help. I have the LG E980 with 4.4.2. I was trying to set this up as a spare phone but for some reason could not get an email program to work with my companies "Notes Traveler" program. I'm able to achieve syncing with my S4 active though. I oulled the email APK off of the S4 active and that resolved the problem temporarily. I read up and found out that the CM11 ROM would resolve this issue. Anyway, I installed a recovery program and did a nanodroid back up only to realize that my EXT_SD card was not being recognized. Si I did a factory reset now I get a boot error and can only get to the recovery program.
It will not recognize my external SD card and I'm afraid that possibly I corrupted the boot image or recovery? Any suggestions how to get out of this boot? Is there a way I can drag a Update.Zip to the internal SD card and it will completely over write boot and all files?
Click to expand...
Click to collapse
This Fix solved my boot only to recovery bug, but if your cwm is not reading your external, you could try sideloading it through adb if your cwm version has that. Copy the fix to your adb folder, connect your phone to pc, select install zip through sideload in the recovery, open adb, type adb sideload fix.zip or if nothing works just use lgflashtool and kdz back to stock.
spirallingspiral said:
This Fix solved my boot only to recovery bug, but if your cwm is not reading your external, you could try sideloading it through adb if your cwm version has that. Copy the fix to your adb folder, connect your phone to pc, select install zip through sideload in the recovery, open adb, type adb sideload fix.zip or if nothing works just use lgflashtool and kdz back to stock.
Click to expand...
Click to collapse
Thanks for your reply. I'm not good at all with ADB would you mind telling me exactly what to type (spacing, etc)? I've tried ADB before and must have been entering the wrong sequence or spacing. On my S4 I simply used ODIN and loaded a Deodexed version.
mikelets456 said:
Thanks for your reply. I'm not good at all with ADB would you mind telling me exactly what to type (spacing, etc)? I've tried ADB before and must have been entering the wrong sequence or spacing. On my S4 I simply used ODIN and loaded a Deodexed version.
Click to expand...
Click to collapse
Click install zip by sideload on cwm, copy the zip i linked before to the your adb folder,. Open Adb, and type "adb devices" to see if your device is detected. If it isnt. click here and download the naked drivers. If your device is detected, type "adb sideload filename.zip" . Just copy the filename and paste it after "adb sideload" in the command prompt, which is "adb sideload Zero_Misc_fix_factory_data_reset_recovery.zip"
spirallingspiral said:
Click install zip by sideload on cwm, copy the zip i linked before to the your adb folder,. Open Adb, and type "adb devices" to see if your device is detected. If it isnt. click here and download the naked drivers. If your device is detected, type "adb sideload filename.zip" . Just copy the filename and paste it after "adb sideload" in the command prompt, which is "adb sideload Zero_Misc_fix_factory_data_reset_recovery.zip"
Click to expand...
Click to collapse
Worked like a charm...thank you very much!
EDIT: however mr SD card is not being shown. When I boot up it says SD card installed, but it's not showing up anywhere. Any suggestions?
mikelets456 said:
Worked like a charm...thank you very much!
EDIT: however mr SD card is not being shown. When I boot up it says SD card installed, but it's not showing up anywhere. Any suggestions?
Click to expand...
Click to collapse
Glad it worked The sd card is not getting detected atall or just recovery? if its just recovery, some recoveries wont see the sd card, you can just flash another recovery to fix that. If its not being detected once it boots up too then i have no clue what the problem is. Try flashing another rom and see if it detects it.
spirallingspiral said:
Glad it worked The sd card is not getting detected atall or just recovery? if its just recovery, some recoveries wont see the sd card, you can just flash another recovery to fix that. If its not being detected once it boots up too then i have no clue what the problem is. Try flashing another rom and see if it detects it.
Click to expand...
Click to collapse
In recovery it shows "external sd card" then when I tried to flash it says " can't mount sd card". Also, I've tried my 64 gb card that's in my samsung and that does not work either. When it boots up it says "sd card inserted".
How do I flash another recovery or go back to stock recovery? I think something is corrupted in recovery because when I did a factory reset again to clear things up I got the boot error and had to do the process all over that you posted.
This is the recovery i always use, its philz touch. You can flash it the same way u flashed the fix, copy the zip to adb folder and sideloading it using adb sideload filename.zip. I cant guarantee that everything will work but if everything goes downhill, you will have to kdz back to stock using the steps from here . If the sd card isnt getting detected after boot too, i really have no idea what the issue is.
spirallingspiral said:
This is the recovery i always use, its philz touch. You can flash it the same way u flashed the fix, copy the zip to adb folder and sideloading it using adb sideload filename.zip. I cant guarantee that everything will work but if everything goes downhill, you will have to kdz back to stock using the steps from here . If the sd card isnt getting detected after boot too, i really have no idea what the issue is.
Click to expand...
Click to collapse
Flashed "TOT" file and all is good. I believe the bootloader is either locked or was corrupted somehow. Thanks again
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.