Hi everyone ! I'm here after a long time. I am really ashamed of asking many noob questions here. But now I might be bringing something useful.
So I bought the piece of useless brick Asus Zenpad C 7.0. it's pretty useless. Can't even watch a movie without the battery draining down to 0.
Anyway..So @AwesomeLewis24 posted a method to unlock the bootloader and root this device. Right after he made that thread, Asus started rolling out updates every 10 days. I updated my device to the newest and now that method was no longer working. It really pissed me off because I really wanted to uninstall the bloatware.
But today...After a lot of headbanging and bargaining with Kim Jong un..I finally rooted the Tablet.
But before we start, please go through this thread. https://forum.xda-developers.com/an...-zenpad-c-7-0-z170c-p01z-root-method-t3311752
Read this incase anything goes wrong. But I'm pretty sure it won't. So let's start.
First, download this file and put it on desktop. https://forum.xda-developers.com/attachment.php?attachmentid=3640170&d=1455053113
Now download adb and fastboot tools. https://forum.xda-developers.com/attachment.php?attachmentid=3640175&d=1455053186
Extract them into a folder. Open that folder with the files and shift+right click there. Choose open command window here.
In the cmd window, type this
Code:
adb reboot fastboot
Now your tablet will boot into fastboot mode. It will be a running android with green background.
Now in the same cmd window type
Code:
fastboot devices
It should list a device. If not then comment.
After your device is listed you have to type these command. NOW PLEASE PAY ATTENTION !! ONLY TYPE THESE COMMANDS . DO NOT TYPE THE "adb format userdata" and "adb format cache" COMMANDS. IT WILL RESULT IN A BRICKED DEVICE.
So, type these commands.
Code:
fastboot oem asus-go
fastboot oem asus-go confirm
Now the bootloader will be unlocked. Now reboot the device by typing this
Code:
fastboot reboot
This will now start your tablet like normal an d you won't see any difference. Now go back Into fastboot by doing
Code:
Adb reboot fastboot
Now in fastboot, do this
Code:
fastboot boot "C:\Users\{your PC user name here}\Desktop\root-z170c_cg.img"
Now reboot again as we did earlier and you are done. You have rooted your asus Zenpad C 7.0 without loosing any of the data.
Make sure you use SuperSU.
I really don't know where you can mess this up but in case of brick do what @AwesomeLewis24 did.
Firstly, leave fastboot by powering off the
thanks!!!!!!!!
do you have the stock rom? it would be amazing
You are the best! This was driving me crazy, and it worked!!!
very simple:good::good:.. not like a long ago i must downgrade the firmware to root
thenewgengamer said:
Hi everyone ! I'm here after a long time. I am really ashamed of asking many noob questions here. But now I might be bringing something useful.
So I bought the piece of useless brick Asus Zenpad C 7.0. it's pretty useless. Can't even watch a movie without the battery draining down to 0.
Anyway..So @AwesomeLewis24 posted a method to unlock the bootloader and root this device. Right after he made that thread, Asus started rolling out updates every 10 days. I updated my device to the newest and now that method was no longer working. It really pissed me off because I really wanted to uninstall the bloatware.
But today...After a lot of headbanging and bargaining with Kim Jong un..I finally rooted the Tablet.
But before we start, please go through this thread. https://forum.xda-developers.com/an...-zenpad-c-7-0-z170c-p01z-root-method-t3311752
Read this incase anything goes wrong. But I'm pretty sure it won't. So let's start.
First, download this file and put it on desktop. https://forum.xda-developers.com/attachment.php?attachmentid=3640170&d=1455053113
Now download adb and fastboot tools. https://forum.xda-developers.com/attachment.php?attachmentid=3640175&d=1455053186
Extract them into a folder. Open that folder with the files and shift+right click there. Choose open command window here.
In the cmd window, type this
Code:
adb reboot fastboot
Now your tablet will boot into fastboot mode. It will be a running android with green background.
Now in the same cmd window type
Code:
fastboot devices
It should list a device. If not then comment.
After your device is listed you have to type these command. NOW PLEASE PAY ATTENTION !! ONLY TYPE THESE COMMANDS . DO NOT TYPE THE "adb format userdata" and "adb format cache" COMMANDS. IT WILL RESULT IN A BRICKED DEVICE.
So, type these commands.
Code:
fastboot oem asus-go
fastboot oem asus-go confirm
Now the bootloader will be unlocked. Now reboot the device by typing this
Code:
fastboot reboot
This will now start your tablet like normal an d you won't see any difference. Now go back Into fastboot by doing
Code:
Adb reboot fastboot
Now in fastboot, do this
Code:
fastboot boot "C:\Users\{your PC user name here}\Desktop\root-z170c_cg.img"
Now reboot again as we did earlier and you are done. You have rooted your asus Zenpad C 7.0 without loosing any of the data.
Make sure you use SuperSU.
I really don't know where you can mess this up but in case of brick do what @AwesomeLewis24 did.
Firstly, leave fastboot by powering off the
Click to expand...
Click to collapse
It will be a not running android with green background.
thenewgengamer said:
Now in the same cmd window type
Code:
fastboot devices
It should list a device. If not then comment.
Click to expand...
Click to collapse
I've arrived upto this point flawlessly, however computer cannot list my device after that command.
what could be the problem?
thank you in advance for your reply.
cheers
braveguy said:
I've arrived upto this point flawlessly, however computer cannot list my device after that command.
what could be the problem?
thank you in advance for your reply.
cheers
Click to expand...
Click to collapse
I had to do this on a windows machine to get it working.
Download Intel usb driver: software.intel.com/en-us/android/articles/intel-usb-driver-for-android-devices
Manually select "Intel Android ADB Interface" driver for the unrecognized device in Device Manager.
Good luck!
---------- Post added at 07:13 AM ---------- Previous post was at 06:47 AM ----------
Rooted two ZenPads just now using this guide, confirmed working. Note you need to install the Intel adb drivers to access fastboot and "fastboot oem asus-go confirm" can be omitted, it doesn't do anything.
Thank you thenewgengamer! :highfive:
hi
I did according to the manual, but in the Root test, I was told that the device did not have a root
What can I do?
i dont see the device listed.
it is unknown device in the device manager.
tried to install with intel usb but it doesn't work still unknown and it's connecting and disconnecting every 5 seconds.......
so anyone knows why is this happening? is this asus protection????
the device connects and disconnects every 5 seconds when in fastboot.....
is there a way to flash the img without fastboot or pc?
Hello everyone and thank you thenewgengamer for the tutorial.
I am stuck too with fastboot.
The device is not seen anymore by the computer. I tried to install all the drivers but it's the same.
If anyone has a clue to resolve it, it'll be very helpfull
Cheers !
But when i do that why i see no command on my recovery ?
I'm also stuck because my device isn't showing up. Was there an update that broke this method? I've tried this on PC and Mac.
I finally got a computer to recognize my device, and with adb devices there was actually a device listed for the first time. However, I am now having the same disconnect after 5 seconds problem. This is so frustrating. WTF am I doing wrong?
sorry, i have a problem. can we istall magisk in this tablet?
will this work on 5.0.2 P01Y version 12.26.4.57 WW?
Thank you very much
I rooted my P01y device.
But by driver in this page:
h*ttps*://*phoneusbdrivers.*com/*asus-zenpad-c-7-0-z170cg-usb-driver/*
download link:
htt*ps://*dl-ssl.*google.com/an*droid/rep*ository/late*st_usb_driver_windows.*zi*p
I just register to thanks and write usb driver download link
Remove all *
---------- Post added at 10:58 AM ---------- Previous post was at 10:55 AM ----------
shayx said:
i dont see the device listed.
it is unknown device in the device manager.
tried to install with intel usb but it doesn't work still unknown and it's connecting and disconnecting every 5 seconds.......
Click to expand...
Click to collapse
I rooted my P01y device by driver in this page:
h*ttps*://*phoneusbdrivers.*com/*asus-zenpad-c-7-0-z170cg-usb-driver/*
download link:
htt*ps://*dl-ssl.*google.com/an*droid/rep*ository/late*st_usb_driver_windows.*zi*p
Remove all * signs
---------- Post added at 11:06 AM ---------- Previous post was at 10:58 AM ----------
Result:
C:\Users\aztbkhz\Desktop\p01y>adb reboot fastboot
C:\Users\aztbkhz\Desktop\p01y>fastboot devices
G8NPFP1221649S8 fastboot
C:\Users\aztbkhz\Desktop\p01y>fastboot oem asus-go
...
(bootloader) Unlocking the bootloader means the following:
(bootloader) All user data will be deleted
(bootloader) Any securely stored data will be inaccessible
(bootloader) Warranty will be void
(bootloader) After unlocking you have to execute
(bootloader) > fastboot format userdata
(bootloader) > fastboot format cache
(bootloader) or carry out a factory reset from recovery
(bootloader) To confirm the unlock, please execute the command
(bootloader) > fastboot oem unlock confirm
OKAY [ 0.047s]
finished. total time: 0.047s
C:\Users\aztbkhz\Desktop\p01y>fastboot oem asus-go confirm
...
(bootloader) Unlocking and rebooting into unlocked state
OKAY [ 0.125s]
finished. total time: 0.125s
C:\Users\aztbkhz\Desktop\p01y>fastboot reboot
rebooting...
finished. total time: -0.000s
C:\Users\aztbkhz\Desktop\p01y>Adb reboot fastboot
C:\Users\aztbkhz\Desktop\p01y>fastboot boot "C:\Users\aztbkhz\Desktop\p01y\root-
z170c_cg.img"
downloading 'boot.img'...
(bootloader) Ready to receive: 0x0078b000 size of data
OKAY [ 0.281s]
booting...
OKAY [ 0.546s]
finished. total time: 0.842s
C:\Users\aztbkhz\Desktop\p01y>
---------- Post added at 11:11 AM ---------- Previous post was at 11:06 AM ----------
Result in device manager is here:
htt*p://s8.picofile.com/file/8323156284/Untitled.png
remove all * , I can't insert link
Puzzled
Hiii You re unclear, working on p01y or z170c?
Tittle P01Y, link and how to flash z170c , this how to root is for p01y or z170c? I don't wanna brick!!
---------- Post added at 01:53 AM ---------- Previous post was at 01:47 AM ----------
Working on P01Y?
sirlancillot said:
Hiii You re unclear, working on p01y or z170c?
Tittle P01Y, link and how to flash z170c , this how to root is for p01y or z170c? I don't wanna brick!!
---------- Post added at 01:53 AM ---------- Previous post was at 01:47 AM ----------
Working on P01Y?
Click to expand...
Click to collapse
P01Y is the same as Z170C. P01Y is the model listed on the device.
lookup the link : https://www.asus.com/Tablets/ASUS_ZenPad_C_70_Z170C/
Worked like a charm on 5.0.2. This is the only rooting method available for this tablet.
Thank you very much!
Related
I got a relocked HoX and now it says: [Preload] Failed to open usb master mode.
Problem is, it doesn't boot, I can't run RUU and I can't unlock it because adb does not find the device.
So it this state it is unusable.
Can anyone please help me?
Thanks in advance
Edit: ADB can't find the phone, so I can't flash files or unlock the phone. However it does react on getvar and reboot commands...
Amicushia said:
I got a relocked HoX and now it says: [Preload] Failed to open usb master mode.
Problem is, it doesn't boot, I can't run RUU and I can't unlock it because adb does not find the device.
So it this state it is unusable.
Can anyone please help me?
Thanks in advance
Edit: ADB can't find the phone, so I can't flash files or unlock the phone. However it does react on getvar and reboot commands...
Click to expand...
Click to collapse
hold power+volume down until you get in white bootloader screen
then use fastboot oem unlock command
---------- Post added at 01:20 AM ---------- Previous post was at 01:18 AM ----------
You don't need adb at all to do flash anything
You can use: fastboot oem rebootRUU
Also to reboot: fastboot reboot
Flashing is done in recovery btw.
Vcek said:
hold power+volume down until you get in white bootloader screen
then use fastboot oem unlock command
---------- Post added at 01:20 AM ---------- Previous post was at 01:18 AM ----------
You don't need adb at all to do flash anything
Click to expand...
Click to collapse
tomascus said:
You can use: fastboot oem rebootRUU
Also to reboot: fastboot reboot
Flashing is done in recovery btw.
Click to expand...
Click to collapse
Thanks for the replies guys, fixed it thanks ! Awesome!
These are the boot and system images as dumped from my moto360. They can be useful for returning to stock if something goes wrong with your device. As far as I can tell, they're good, and I have tested them in my device, but I'm not responsible if they break your device or anything else. Use them at your own risk.
They can be flashed from fastboot.
- turn off the watch
- press and hold the power button until you feel the third vibration, display will show "Bootloader version..."
- connect the jig to your watch and secure it so it will not move accidentally.
- connect the USB cable to your computer. Displaty will show "Transfer mode: USB Connected..."
- Launch a terminal session in your computer and issue the commands:
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot reboot
https://drive.google.com/folderview?id=0BxTLcy78OveNWDI4d1IyZHY4RUU&usp=sharing
Code:
boot.img md5: f1837f04639b9372191387632d8bf537
system.img md5: 64d028f8dc800b8ca0c716c2feacc837
Big thank you to jcase and beaups, it wouldn't have been possible without their help!
Enjoy.
To encourage more research and developments, use the donate button on the right! thanks!
Is @jcase working on a rooted boot image at this time?
Sent from my XT1049 using XDA Free mobile app
Cyphir said:
Is @jcase working on a rooted boot image at this time?
Sent from my XT1049 using XDA Free mobile app
Click to expand...
Click to collapse
Already done, I worked with @dproldan and gave him a set. Since I dont have the watch, I am leaving it up to him to publish them, or not
jcase said:
Already done, I worked with @dproldan and gave him a set. Since I dont have the watch, I am leaving it up to him to publish them, or not
Click to expand...
Click to collapse
Thanks man, and thanks for all the work you have done and continue to do for this community.
Sent from my XT1049 using XDA Free mobile app
@dproldan do you have the MD5s for those files? Google Drive doesn't seem to show them and i just want to be sure the downloads are good before I go messing with stuff.
dproldan said:
These are the boot and system images as dumped from my moto360. They can be useful for returning to stock if something goes wrong with your device. As far as I can tell, they're good, and I have tested them in my device, but I'm not responsible if they break your device or anything else. Use them at your own risk.
They can be flashed from fastboot.
- turn off the watch
- press and hold the power button until you feel the third vibration, display will show "Bootloader version..."
- connect the jig to your watch and secure it so it will not move accidentally.
- connect the USB cable to your computer. Displaty will show "Transfer mode: USB Connected..."
- Launch a terminal session in your computer and issue the commands:
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot reboot
https://drive.google.com/folderview?id=0BxTLcy78OveNWDI4d1IyZHY4RUU&usp=sharing
Code:
boot.img md5: f1837f04639b9372191387632d8bf537
system.img md5: 64d028f8dc800b8ca0c716c2feacc837
Big thank you to jcase and beaups, it wouldn't have been possible without their help!
Enjoy.
Click to expand...
Click to collapse
Hey Bro, can you pull the recovery.img from the device? I want to begin work on CWMT/TWRP, but I need the recovery.img. I'm getting the watch tomorrow, and I want to have a build of TWRP ready for it
EDIT: Appears I also need a recovery.fstab for this device.
---------- Post added at 10:59 PM ---------- Previous post was at 10:49 PM ----------
jcase said:
Already done, I worked with @dproldan and gave him a set. Since I dont have the watch, I am leaving it up to him to publish them, or not
Click to expand...
Click to collapse
Got a question for you. I know that according to the instructions in the Bootable rooted image thread, it says just to "fastboot boot boot.img" and that will root the device... why does that root the device/why wouldn't you flash it? If you just boot it, won't you loose it on reboot?
Also, I know that there was some hubbub about the fact that you can "fastboot boot" a kernel without an unlocked BL, does that mean that we can use the rooted boot.img without unlocking our BL?
Thanks a billion,
dproldan said:
These are the boot and system images as dumped from my moto360. They can be useful for returning to stock if something goes wrong with your device. As far as I can tell, they're good, and I have tested them in my device, but I'm not responsible if they break your device or anything else. Use them at your own risk.
They can be flashed from fastboot.
- turn off the watch
- press and hold the power button until you feel the third vibration, display will show "Bootloader version..."
- connect the jig to your watch and secure it so it will not move accidentally.
- connect the USB cable to your computer. Displaty will show "Transfer mode: USB Connected..."
- Launch a terminal session in your computer and issue the commands:
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot reboot
https://drive.google.com/folderview?id=0BxTLcy78OveNWDI4d1IyZHY4RUU&usp=sharing
Code:
boot.img md5: f1837f04639b9372191387632d8bf537
system.img md5: 64d028f8dc800b8ca0c716c2feacc837
Big thank you to jcase and beaups, it wouldn't have been possible without their help!
Enjoy.
To encourage more research and developments, use the donate button on the right! thanks!
Click to expand...
Click to collapse
has anyone tested these images on there device yet or have they just been pulled and posted?
Tomsgt said:
has anyone tested these images on there device yet or have they just been pulled and posted?
Click to expand...
Click to collapse
came up with a little something http://www.rootjunky.com/motorola-moto-360-super-tool/ will make a post on this when i get some time.
I am trying to root my moto360 but it gets stuck on downloading boot.img . Any solutions?
i tried to flash these today, got FAILED bad file descriptor. now my moto 360 won't boot ): haha, time to try and fix this thing
edit: got it to flash, but it boots into the android laying on it's back with the red exclamation point. any help would be appreciated
come over to #moto360 on freenode ( you can use http://webchat.freenode.net/) and we'll see what happened.
beats4x said:
i tried to flash these today, got FAILED bad file descriptor. now my moto 360 won't boot ): haha, time to try and fix this thing
edit: got it to flash, but it boots into the android laying on it's back with the red exclamation point. any help would be appreciated
Click to expand...
Click to collapse
You have to use the mfastboot.exe to flash system.IMG to this device or you will end up in a recovery bootloop. Also try using my tool linked 2 post above.
---------- Post added at 12:06 PM ---------- Previous post was at 12:06 PM ----------
vincenzo697 said:
I am trying to root my moto360 but it gets stuck on downloading boot.img . Any solutions?
Click to expand...
Click to collapse
Make sure the moto 360 has at least 80% battery before flashing.
dproldan said:
come over to #moto360 on freenode ( you can use http://webchat.freenode.net/) and we'll see what happened.
Click to expand...
Click to collapse
thanks, i will definitely stop by if i need to in the future
Tomsgt said:
You have to use the mfastboot.exe to flash system.IMG to this device or you will end up in a recovery bootloop. Also try using my tool linked 2 post above.
---------- Post added at 12:06 PM ---------- Previous post was at 12:06 PM ----------
Make sure the moto 360 has at least 80% battery before flashing.
Click to expand...
Click to collapse
Your tool got it up and running for me. thank you so much dude! much appreciated. as i love learning the why behind the how, how come it causes a bootloop unless you use that specific variant of fastboot? is mfastboot a motorola variant of fastboot that's needed with their boot.img's?
i've had nexus, htc, and lg devices before, so this is my first run with motorola.
beats4x said:
thanks, i will definitely stop by if i need to in the future
Your tool got it up and running for me. thank you so much dude! much appreciated. as i love learning the why behind the how, how come it causes a bootloop unless you use that specific variant of fastboot? is mfastboot a motorola variant of fastboot that's needed with their boot.img's?
i've had nexus, htc, and lg devices before, so this is my first run with motorola.
Click to expand...
Click to collapse
Yes it is a Motorola fastboot file. The normal fastboot.exe is limited a certain size. The moto fastboot let's you flash bigger images its more or less a upgraded fastboot file.
Tomsgt said:
Yes it is a Motorola fastboot file. The normal fastboot.exe is limited a certain size. The moto fastboot let's you flash bigger images its more or less a upgraded fastboot file.
Click to expand...
Click to collapse
forsure, makes since. If i move mfastboot to my adb/fastboot directory, and use mfastboot commands, will that work? I prefer not to use toolkits when i don't have to (not that i'm not thankful for yours, it rescued my device lol)
beats4x said:
forsure, makes since. If i move mfastboot to my adb/fastboot directory, and use mfastboot commands, will that work? I prefer not to use toolkits when i don't have to (not that i'm not thankful for yours, it rescued my device lol)
Click to expand...
Click to collapse
Yes that should work just fine. I also like the manual commands but for the noons I make these fun super tools
Tomsgt said:
Yes that should work just fine. I also like the manual commands but for the noons I make these fun super tools
Click to expand...
Click to collapse
and i'm sure they help out quite a bit :silly: thanks for your help, it's much appreciated
Tomsgt said:
You have to use the mfastboot.exe to flash system.IMG to this device or you will end up in a recovery bootloop. Also try using my tool linked 2 post above.
---------- Post added at 12:06 PM ---------- Previous post was at 12:06 PM ----------
Make sure the moto 360 has at least 80% battery before flashing.
Click to expand...
Click to collapse
I tried with fully charged battery and still it gets stuck on downloading boot.img I follow exactly the tutorial and everything on my Moro360 is the same as the video until it sticks on the downloading boot.img
vincenzo697 said:
I tried with fully charged battery and still it gets stuck on downloading boot.img I follow exactly the tutorial and everything on my Moro360 is the same as the video until it sticks on the downloading boot.img
Click to expand...
Click to collapse
my super tool thread can be found here now please try it. http://forum.xda-developers.com/moto-360/development/script-motorola-moto-360-super-tool-t2897690
dproldan said:
These are the boot and system images as dumped from my moto360. They can be useful for returning to stock if something goes wrong with your device. As far as I can tell, they're good, and I have tested them in my device, but I'm not responsible if they break your device or anything else. Use them at your own risk.
They can be flashed from fastboot.
- turn off the watch
- press and hold the power button until you feel the third vibration, display will show "Bootloader version..."
- connect the jig to your watch and secure it so it will not move accidentally.
- connect the USB cable to your computer. Displaty will show "Transfer mode: USB Connected..."
- Launch a terminal session in your computer and issue the commands:
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot reboot
https://drive.google.com/folderview?id=0BxTLcy78OveNWDI4d1IyZHY4RUU&usp=sharing
Code:
boot.img md5: f1837f04639b9372191387632d8bf537
system.img md5: 64d028f8dc800b8ca0c716c2feacc837
Big thank you to jcase and beaups, it wouldn't have been possible without their help!
Enjoy.
To encourage more research and developments, use the donate button on the right! thanks!
Click to expand...
Click to collapse
im havving this problem, any advice??
sending 'boot' (16384 KB)...
FAILED (remote: unsupported command)
finished. total time: 0.006s
same with system
sending 'system' (49152 KB)...
FAILED (remote: unsupported command)
finished. total time: 0.006s
help please
Hi, i have searched the forum before posting this.
my phone is stuck at the logo and i have tried pressing all possible key bindings (power + up, power + down, power + up + down) but still i can only see the log. I also tried to use adb fastboot but when i search for my device (adb devices) it says my phone is offline. And right now i can't even turn off my phone, so the battry is draining right now.
please help me as fast as possible as i dont think i can charge my phone
have you pressed the three buttons longer than 10seconds?
if not,try it..hold them until the screen changes (might take up to a full minute!!!!)..be patient..
to reach the bootloader (where adb can find your phone),hold power and vol. down until the huawei logo apears and stays (looks like it seems to be stuck)..then connect to the pc and wait for a few seconds..in adb cmd type "fastboot devices" (without "")..you should see many "?" and weird things in a line - thats ok! - your phone is recognized then..
from there you can start the adb cmds you want to (and can be found en masse here in this forum)..
hope this helps
blueIBI said:
have you pressed the three buttons longer than 10seconds?
if not,try it..hold them until the screen changes (might take up to a full minute!!!!)..be patient..
to reach the bootloader (where adb can find your phone),hold power and vol. down until the huawei logo apears and stays (looks like it seems to be stuck)..then connect to the pc and wait for a few seconds..in adb cmd type "fastboot devices" (without "")..you should see many "?" and weird things in a line - thats ok! - your phone is recognized then..
from there you can start the adb cmds you want to (and can be found en masse here in this forum)..
hope this helps
Click to expand...
Click to collapse
Thanx for they reply, i tried pressing the 3 buttons for 2 min but nothing,
i also tried fastboot devices and i found the ???????
Now what do i need to do to fix my phone?
Never mind, solved big thanx for your help
bobalyafeai09 said:
Hi, i have searched the forum before posting this.
my phone is stuck at the logo and i have tried pressing all possible key bindings (power + up, power + down, power + up + down) but still i can only see the log. I also tried to use adb fastboot but when i search for my device (adb devices) it says my phone is offline. And right now i can't even turn off my phone, so the battry is draining right now.
please help me as fast as possible as i dont think i can charge my phone
Click to expand...
Click to collapse
Bro. i have the same problem with you. and sadly my phone too cant recognize the adb. i mean the adb cant detect my phone. so if your phone fix please tell me. hope that your phone can fix so that i will do the same thing. :good:
Help999 said:
Bro. i have the same problem with you. and sadly my phone too cant recognize the adb. i mean the adb cant detect my phone. so if your phone fix please tell me. hope that your phone can fix so that i will do the same thing. :good:
Click to expand...
Click to collapse
My phone is fixed now, first i was using windows 8 to solve my problem but there was something wrong with driver for the phone, so i tried using my friend PC windows 7 and the driver installed automatically.
Now you need to connect your phone to the PC and hold power + volume down together until the phone restarts and the Acsend logo appears, now you can relase the buttons.
After that you need to type "fastboot devices" in the command promote, you should see a message like this "????/??,,? <>??????".
if you get the message let me know, i will tell you what you need to do next
bobalyafeai09 said:
My phone is fixed now, first i was using windows 8 to solve my problem but there was something wrong with driver for the phone, so i tried using my friend PC windows 7 and the driver installed automatically.
Now you need to connect your phone to the PC and hold power + volume down together until the phone restarts and the Acsend logo appears, now you can relase the buttons.
After that you need to type "fastboot devices" in the command promote, you should see a message like this "????/??,,? <>??????".
if you get the message let me know, i will tell you what you need to do next
Click to expand...
Click to collapse
Bro. Please give the link of all tools that you use like adb like that . and the complete process i will follow your instructions. Advance Thanks Bro. :good::highfive:
Help999 said:
Bro. Please give the link of all tools that you use like adb like that . and the complete process i will follow your instructions. Advance Thanks Bro. :good::highfive:
Click to expand...
Click to collapse
For the adb, i installed it long time ago and i dont remember from which website but you can search in this forum and find plenty of useful posts.
After I checked my device using this command 'fastboot devices', i downloaded boot.img and recovery.img for "Stock Firmware Huawei B506 CN KitKat" from this link: http://forum.xda-developers.com/showpost.php?p=51718316&postcount=2
and followed the steps.
after that i installed twrp by following the steps from this link: http://techbeasts.com/2014/04/29/in...3-7-or-twrp-2-7-recovery-on-huawei-ascend-p6/
then i used this link: http://forum.xda-developers.com/showthread.php?t=2739825
to install AOSP 4.4.4. but i think you can download other roms and follow the same steps
for custom roms yes..there you need twrp..
if you want to stay on stock roms you have always to reflash the respective recovery from the firmware (stock rom) you actually have running..
bobalyafeai09 said:
For the adb, i installed it long time ago and i dont remember from which website but you can search in this forum and find plenty of useful posts.
After I checked my device using this command 'fastboot devices', i downloaded boot.img and recovery.img for "Stock Firmware Huawei B506 CN KitKat" from this link: http://forum.xda-developers.com/showpost.php?p=51718316&postcount=2
and followed the steps.
after that i installed twrp by following the steps from this link: http://techbeasts.com/2014/04/29/in...3-7-or-twrp-2-7-recovery-on-huawei-ascend-p6/
then i used this link: http://forum.xda-developers.com/showthread.php?t=2739825
to install AOSP 4.4.4. but i think you can download other roms and follow the same steps
Click to expand...
Click to collapse
Thank you for this bro. i will follow this steps when my phone fix too. well thank you very much! :good: :highfive:
---------- Post added at 06:44 AM ---------- Previous post was at 06:31 AM ----------
bobalyafeai09 said:
For the adb, i installed it long time ago and i dont remember from which website but you can search in this forum and find plenty of useful posts.
After I checked my device using this command 'fastboot devices', i downloaded boot.img and recovery.img for "Stock Firmware Huawei B506 CN KitKat" from this link: http://forum.xda-developers.com/showpost.php?p=51718316&postcount=2
and followed the steps.
after that i installed twrp by following the steps from this link: http://techbeasts.com/2014/04/29/in...3-7-or-twrp-2-7-recovery-on-huawei-ascend-p6/
then i used this link: http://forum.xda-developers.com/showthread.php?t=2739825
to install AOSP 4.4.4. but i think you can download other roms and follow the same steps
Click to expand...
Click to collapse
Bro , AOSP 4.4.4 Rom is better? i will use the same rom bro Thanks again.
---------- Post added at 07:11 AM ---------- Previous post was at 06:44 AM ----------
HEY GUYS! MY COMPUTER RECOGNIZE MY PHONE , BUT .
WHEN I TRY TO FLASH A BOOT.IMG I GET THIS ERROR .
C:\Users\ASUS\Desktop\adb>fastboot flash boot boot.img
target reported max download size of 838860800 bytes
sending 'boot' <8192 KB>...
OkAY [ 0.281s ]
writing 'boot'...
FAILED <remote: flash failure, ErrNo:2>
finished. total time: 0.286s
THAT ERROR I GET WHEN I FLASH BOOT.IMG. (SORRY I DONT KNOW HOW TO PUT A IMAGE SO THATS WHY I TYPE THE ERROR)
Help999 said:
Thank you for this bro. i will follow this steps when my phone fix too. well thank you very much! :good: :highfive:
---------- Post added at 06:44 AM ---------- Previous post was at 06:31 AM ----------
Bro , AOSP 4.4.4 Rom is better? i will use the same rom bro Thanks again.
---------- Post added at 07:11 AM ---------- Previous post was at 06:44 AM ----------
HEY GUYS! MY COMPUTER RECOGNIZE MY PHONE , BUT .
WHEN I TRY TO FLASH A BOOT.IMG I GET THIS ERROR .
C:\Users\ASUS\Desktop\adb>fastboot flash boot boot.img
target reported max download size of 838860800 bytes
sending 'boot' <8192 KB>...
OkAY [ 0.281s ]
writing 'boot'...
FAILED <remote: flash failure, ErrNo:2>
finished. total time: 0.286s
THAT ERROR I GET WHEN I FLASH BOOT.IMG. (SORRY I DONT KNOW HOW TO PUT A IMAGE SO THATS WHY I TYPE THE ERROR)
Click to expand...
Click to collapse
Is this boot.img for the twrp or the stock pu-506?
bobalyafeai09 said:
Is this boot.img for the twrp or the stock pu-506?
Click to expand...
Click to collapse
i just downloaded the boot.img here http://forum.xda-developers.com/show...16&postcount=2
and follow the instutions. my phone stuck on logo and i want to fix it. but the first step flashing a boot.img
i got a failed message. how do i fix it? please help. :crying:
Help999 said:
i just downloaded the boot.img here http://forum.xda-developers.com/show...16&postcount=2
and follow the instutions. my phone stuck on logo and i want to fix it. but the first step flashing a boot.img
i got a failed message. how do i fix it? please help. :crying:
Click to expand...
Click to collapse
i cant open the link, what is the boot.img for?
bobalyafeai09 said:
Is this boot.img for the twrp or the stock pu-506?
Click to expand...
Click to collapse
i download the boot.img from "Stock Firmware Huawei B506 CN KitKat" here's the link.
http://forum.xda-developers.com/showpost.php?p=51718316&postcount=2
---------- Post added at 08:12 AM ---------- Previous post was at 07:50 AM ----------
GUYS PLEASE HELP , ABOUT MY ERROR ON FLASHING A BOOT.IMG I GET THIS ERROR .
C:\Users\ASUS\Desktop\adb>fastboot flash boot boot.img
target reported max download size of 838860800 bytes
sending 'boot' <8192 KB>...
OkAY [ 0.281s ]
writing 'boot'...
FAILED <remote: flash failure, ErrNo:2>
finished. total time: 0.286s
HOW I FIX IT?
---------- Post added at 08:31 AM ---------- Previous post was at 08:12 AM ----------
OMG! I FINALLY FIX MY PHONE BRO
FIRST I ESCAPE FLASHING BOOT.IMG AND TRY
TO FLASH A RECOVERY.IMG THEN ITS SUCCESS TO FLASH . THEN I HOLD THE POWER BUTTONG AND MY PHONE BOOTED THEN BOOOM! MY PHONE IS COMPLETE BOOTED ITS NOT STOCK ON LOGO AND IM HAPPY AS HELL! THANKS BRO FOR SHARING SOME IDEAS NOW I HARD RESET MY PHONE AND INSTALL NEW GAMES AND APPS THANKS BROOOOOOOOOOO! :good: :highfive:
Hey, sorry for not replying, i was sleeping
Congratulations on fixing your phone too :highfive:
All, I have an Unlocked, S-Off, Rooted HTC One M8 w/ Verizon that I was running Cyanogenmod 12.1, their latest snapshot.
Today the screen was black w/ the notification light blinking as I had a message. I couldn't get the screen to come on. I held in power + volume up until the phone rebooted. It rebooted to the boot loader. I told it to reboot & when it did the HTC splash screen didnt have the normal warnings that I'm used to seeing; warning something about developer options maybe; I can't remember. Anyways it just keeps booting to the bootloader & when I try to boot to recovery; it just reboots back into the bootloader. I've tried to flash to the lastest version of twrp via ADB on my pc, the flash is successful; but doesn't work when i try.
I've also ran...
fastboot erase cache
as i found that suggestion online.
Nothing is working for me. Any suggestions?
Thanks
AndroidJason said:
All, I have an Unlocked, S-Off, Rooted HTC One M8 w/ Verizon that I was running Cyanogenmod 12.1, their latest snapshot.
Today the screen was black w/ the notification light blinking as I had a message. I couldn't get the screen to come on. I held in power + volume up until the phone rebooted. It rebooted to the boot loader. I told it to reboot & when it did the HTC splash screen didnt have the normal warnings that I'm used to seeing; warning something about developer options maybe; I can't remember. Anyways it just keeps booting to the bootloader & when I try to boot to recovery; it just reboots back into the bootloader. I've tried to flash to the lastest version of twrp via ADB on my pc, the flash is successful; but doesn't work when i try.
I've also ran...
fastboot erase cache
as i found that suggestion online.
Nothing is working for me. Any suggestions?
Thanks
Click to expand...
Click to collapse
Download this RUU & install on cp, then power on & volume down to fastboot & run RUU
http://forum.xda-developers.com/verizon-htc-one-m8/development/exe-zip-ruu-m8vzw-5-0-1-s-off-onlynewest-t3047103
Then reinstall twrp & rom of choice.
crackerjack1957 said:
Download this RUU & install on cp, then power on & volume down to fastboot & run RUU
http://forum.xda-developers.com/verizon-htc-one-m8/development/exe-zip-ruu-m8vzw-5-0-1-s-off-onlynewest-t3047103
Then reinstall twrp & rom of choice.
Click to expand...
Click to collapse
Thanks, I will give this a try. Since it will take me back to stock, will I have to root again before installing TWRP & custom ROM?
crackerjack1957 said:
Download this RUU & install on cp, then power on & volume down to fastboot & run RUU
http://forum.xda-developers.com/verizon-htc-one-m8/development/exe-zip-ruu-m8vzw-5-0-1-s-off-onlynewest-t3047103
Then reinstall twrp & rom of choice.
Click to expand...
Click to collapse
No luck. Even though I can run fastboot commands, the RUU exe package reboots the phone, then eventually fails at waiting for bootloader, even though the bootloader is ready. I get error 171 USB Connection Error, from the RUU exe on my pc.
Thoughts?
AndroidJason said:
No luck. Even though I can run fastboot commands, the RUU exe package reboots the phone, then eventually fails at waiting for bootloader, even though the bootloader is ready. I get error 171 USB Connection Error, from the RUU exe on my pc.
Thoughts?
Click to expand...
Click to collapse
Found an SD card that would fit & am now trying option 1 of the RUU.
Fingers crossed, updating just completed successful. Two steps were bypassed. Step 8, SBL1 (8) & Step 13 TP.
No change... Dang
Still same loop, boots to bootloader, selecting recovery reboots to bootloader.
Am I missing something?
AndroidJason said:
Found an SD card that would fit & am now trying option 1 of the RUU.
Fingers crossed, updating just completed successful. Two steps were bypassed. Step 8, SBL1 (8) & Step 13 TP.
No change... Dang
Still same loop, boots to bootloader, selecting recovery reboots to bootloader.
Am I missing something?
Click to expand...
Click to collapse
I guessing you have used this cp before for commands or flashing on m8.
What OS on cp?
Using USB2 port, not USB3?
HTC drivers installed?
ADB commands recognize m8?
---------- Post added 29th December 2015 at 12:01 AM ---------- Previous post was 28th December 2015 at 11:49 PM ----------
crackerjack1957 said:
I guessing you have used this cp before for commands or flashing on m8.
What OS on cp?
Using USB2 port, not USB3?
HTC drivers installed?
ADB commands recognize m8?
Click to expand...
Click to collapse
Also remember I had a problem with one, had to download and flash the L hboot from sdcard 1st then run RUU from pc.
Run L hboot the same way as option2.
Option2 did not work for me.
Good Luck!!!
crackerjack1957 said:
I guessing you have used this cp before for commands or flashing on m8.
What OS on cp?
Using USB2 port, not USB3?
HTC drivers installed?
ADB commands recognize m8?
---------- Post added 29th December 2015 at 12:01 AM ---------- Previous post was 28th December 2015 at 11:49 PM ----------
Also remember I had a problem with one, had to download and flash the L hboot from sdcard 1st then run RUU from pc.
Run L hboot the same way as option2.
Option2 did not work for me.
Good Luck!!!
Click to expand...
Click to collapse
This is the first time for me using a computer to flash my m8 or any other phone. I've always rooted, unlocked bootloader & then used TWRP.
OS on pc is Windows 7.
USB 2
HTC Drivers are installed
Im not sure is ADB commands work. I can get the Fastboot commands to work.
Nothing is listed after I run ADB Devices
I do get a device when I run fastboot devices.
The L hboot is an image, did you mean to say run it the same way as option 1?
AndroidJason said:
This is the first time for me using a computer to flash my m8 or any other phone. I've always rooted, unlocked bootloader & then used TWRP.
OS on pc is Windows 7.
USB 2
HTC Drivers are installed
Im not sure is ADB commands work. I can get the Fastboot commands to work.
Nothing is listed after I run ADB Devices
I do get a device when I run fastboot devices.
The L hboot is an image, did you mean to say run it the same way as option 1?
Click to expand...
Click to collapse
Yes, my bad, got option 1 & 2 mixed from memory
crackerjack1957 said:
Yes, my bad, got option 1 & 2 mixed from memory
Click to expand...
Click to collapse
Ok, so i ran the L hboot by renaming it & putting on an SD card, option 1. That worked fine.
Powered off.
Ran the RUU by renaming it & putting on an SD card, option 1. That worked and had the same two bypasses as before.
Rebooted & pulled out the SD card, but sadly; same results.
I think Im going to bed, its late here on the East Coast.
I'll check back in the morning. Thank you for your continuing help.
AndroidJason said:
Ok, so i ran the L hboot by renaming it & putting on an SD card, option 1. That worked fine.
Powered off.
Ran the RUU by renaming it & putting on an SD card, option 1. That worked and had the same two bypasses as before.
Rebooted & pulled out the SD card, but sadly; same results.
I think Im going to bed, its late here on the East Coast.
I'll check back in the morning. Thank you for your continuing help.
Click to expand...
Click to collapse
Sorry it did not work for you, maybe try the L hboot again & run RUU from pc.
If that does not work I'm out of ideas, maybe someone else could give some suggestions.
crackerjack1957 said:
Sorry it did not work for you, maybe try the L hboot again & run RUU from pc.
If that does not work I'm out of ideas, maybe someone else could give some suggestions.
Click to expand...
Click to collapse
Still up, wanted to give you time to respond.
I can't get the RUU update to run from pc, so it looks like this could be a dead end for me. Thank you again for trying.
I hate to get a new phone, none of the new Verizon phones can be rooted or an unlocked bootloader.
Can't get the new Nexus phones as we purchase directly through Verizon & not Google. (this is my company phone & HAS to be purchased through Verizon)
I'll retrace some steps in the morning.
AndroidJason said:
No luck. Even though I can run fastboot commands, the RUU exe package reboots the phone, then eventually fails at waiting for bootloader, even though the bootloader is ready. I get error 171 USB Connection Error, from the RUU exe on my pc.
Thoughts?
Click to expand...
Click to collapse
Looked back at the error you were getting trying to flash ruu with pc.
I'm not going to try to tell you to do the sdcard method because that did not work for me.
Here is a link that worked for some, even though this is not for the htc m8.
Think you may need to uninstall htc manager & clean with cc cleaner & reinstall.
Also try re downloading ruu incase it got corrupt.
http://androidforums.com/threads/ruu-error-170-171-solution-for-windows-7.161463/
---------- Post added at 10:14 AM ---------- Previous post was at 10:04 AM ----------
Remove Htc drivers in win7 program uninstaller also along with HTC sync then run cc cleaner.
Reinstall HTC sync then uninstall leaving drivers only, this is how my pc is setup & working.
http://www.htc.com/us/software/htc-sync-manager/
https://www.piriform.com/ccleaner
crackerjack1957 said:
Looked back at the error you were getting trying to flash ruu with pc.
I'm not going to try to tell you to do the sdcard method because that did not work for me.
Here is a link that worked for some, even though this is not for the htc m8.
Think you may need to uninstall htc manager & clean with cc cleaner & reinstall.
Also try re downloading ruu incase it got corrupt.
http://androidforums.com/threads/ruu-error-170-171-solution-for-windows-7.161463/
---------- Post added at 10:14 AM ---------- Previous post was at 10:04 AM ----------
Remove Htc drivers in win7 program uninstaller also along with HTC sync then run cc cleaner.
Reinstall HTC sync then uninstall leaving drivers only, this is how my pc is setup & working.
http://www.htc.com/us/software/htc-sync-manager/
https://www.piriform.com/ccleaner
Click to expand...
Click to collapse
Thanks will do, I'm actually trying to use a complete different computer as we speak. Will update the results.
AndroidJason said:
Thanks will do, I'm actually trying to use a complete different computer as we speak. Will update the results.
Click to expand...
Click to collapse
Same results from another pc (which had previously installed HTC drivers) I am now trying the suggestions from the last link you provided w/ uninstalling HTC software/drivers & running cc cleaner program.
AndroidJason said:
Same results from another pc (which had previously installed HTC drivers) I am now trying the suggestions from the last link you provided w/ uninstalling HTC software/drivers & running cc cleaner program.
Click to expand...
Click to collapse
Don't forget to uninstall htc sync before doing anything with ruu, it may interfere, the drivers remain behind.
What about the usb cable you are using, is it a data cable that came with m8 or spare that mainly used for charging.
AndroidJason said:
Same results from another pc (which had previously installed HTC drivers) I am now trying the suggestions from the last link you provided w/ uninstalling HTC software/drivers & running cc cleaner program.
Click to expand...
Click to collapse
Still not working.
Followed all the instructions, re-downloaded the RUU. I've uninstalled the HTC sync & drivers; ran cc cleaner, rebooted, reinstalled HTC snyc & drivers.
I've even tried this on two different Windows 7 pc's. One I left the HTC Sync on, the other I uninstalled & just left the HTC drivers behind. (as one person suggested)
Should the RUU installer app say updated to version & then it instead of a version it list odd characters that I dont even know how to type on a keyboard?
I think I've got my first true brick.
crackerjack1957 said:
Don't forget to uninstall htc sync before doing anything with ruu, it may interfere, the drivers remain behind.
What about the usb cable you are using, is it a data cable that came with m8 or spare that mainly used for charging.
Click to expand...
Click to collapse
I will try another cable, I have a ton of these & just grabbed one; & thats the one I've been using.
AndroidJason said:
I will try another cable, I have a ton of these & just grabbed one; & thats the one I've been using.
Click to expand...
Click to collapse
Using a different cable, I get the same problem.
I dont think its the cable, because the RUU can read the current version of firmware thats on the phone, then issues the phone to reboot. Then the RUU app just sits & says waiting for bootloader.
AndroidJason said:
Using a different cable, I get the same problem.
I dont think its the cable, because the RUU can read the current version of firmware thats on the phone, then issues the phone to reboot. Then the RUU app just sits & says waiting for bootloader.
Click to expand...
Click to collapse
Grab this:http://forum.xda-developers.com/showthread.php?t=2588979
---------- Post added at 12:52 PM ---------- Previous post was at 12:40 PM ----------
Grab stagefright zip:http://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845
Option 3
Fastboot RUU mode . This method assumes you have a working ADB/Fastboot directory on your PC. Download RUUish file and place in your working fastboot/adb directory. Boot your phone to fastboot mode and connect to PC. Issue the following commands.
fastboot oem rebootRUU
###while in this mode your phone will display an HTC logo on the screen
fastboot flash zip 0P6BIMG.zip
##while in this mode you will see an HTC logo on the screen and a green status bar across the bottom of the screen. When command output ##completes it may say reboot required to flush etc... if that's the case issue a "fastboot reboot-bootloader" command and restart option 1 again.
example
## assuming flash completes and no further flushing/reboots are requested from the cmd output you can now reboot IF you simply wish to reboot the system you can issue "fastboot reboot" which will reboot system.
## expect a good 5 minute plus first boot!
---------- Post added at 01:03 PM ---------- Previous post was at 12:52 PM ----------
If that fails go here to reinstall firmware 1st (4.17.605.5):
---------- Post added at 01:06 PM ---------- Previous post was at 01:03 PM ----------
Instructions
Download firmware zip
reboot your phone to bootloader
Place your firmware zip in your fastboot folder
Open CMD terminal on pc in your file you fastboot from.
Plug phone into pc
In terminal first cmd you need is
Fastboot oem rebootRUU
fastboot flash zip nameofyourfile.zip
It should ask you to reflush immediately in your cmd terminal,when it does proceed to next cmd
fastboot flash zip nameofyourfile.zip
Once all is good on your end an your ready to reboot phone use this final cmd
Fastboot reboot-bootloader
crackerjack1957 said:
Grab this:http://forum.xda-developers.com/showthread.php?t=2588979
---------- Post added at 12:52 PM ---------- Previous post was at 12:40 PM ----------
Grab stagefright zip:http://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845
Option 3
Fastboot RUU mode . This method assumes you have a working ADB/Fastboot directory on your PC. Download RUUish file and place in your working fastboot/adb directory. Boot your phone to fastboot mode and connect to PC. Issue the following commands.
fastboot oem rebootRUU
###while in this mode your phone will display an HTC logo on the screen
fastboot flash zip 0P6BIMG.zip
##while in this mode you will see an HTC logo on the screen and a green status bar across the bottom of the screen. When command output ##completes it may say reboot required to flush etc... if that's the case issue a "fastboot reboot-bootloader" command and restart option 1 again.
example
## assuming flash completes and no further flushing/reboots are requested from the cmd output you can now reboot IF you simply wish to reboot the system you can issue "fastboot reboot" which will reboot system.
## expect a good 5 minute plus first boot!
---------- Post added at 01:03 PM ---------- Previous post was at 12:52 PM ----------
If that fails go here to reinstall firmware 1st (4.17.605.5):
---------- Post added at 01:06 PM ---------- Previous post was at 01:03 PM ----------
Instructions
Download firmware zip
reboot your phone to bootloader
Place your firmware zip in your fastboot folder
Open CMD terminal on pc in your file you fastboot from.
Plug phone into pc
In terminal first cmd you need is
Fastboot oem rebootRUU
fastboot flash zip nameofyourfile.zip
It should ask you to reflush immediately in your cmd terminal,when it does proceed to next cmd
fastboot flash zip nameofyourfile.zip
Once all is good on your end an your ready to reboot phone use this final cmd
Fastboot reboot-bootloader
Click to expand...
Click to collapse
I get the following when I attempt to flash using this method...
C:\adb>fastboot flash zip 0P6BIMG.zip
target reported max download size of 1826414592 bytes
sending 'zip' (1683272 KB)...
OKAY [ 63.976s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 63.991s
My phone also doesnt do what is described by staying at an HTC splash screen; it just boots right to the bootloader like it always does.
I've seen that remote: not allowed trying some of my own method during this whole process; not sure what that means.
So, I have read several threads and feel that a solution is there, but I just can't seem to find the detailed instructions on how to fix it. Apologies if I have missed it and you can direct me to that one.
I have tried the xperia companion software recovery and the software update two different times. Both times they said it was successful. However, the watch would still get stuck on the 4 symbols or dots.
I tried doing the factory reset on the watch itself, but that did not help the booting process.
When I press the recovery, I get the android guy laying down with a red exclamation mark in a red triangle.
It appears that fixing it can not be done on win 10, but I do have access to a pc with ubuntu/linux that I have used.
Since I'm getting the red triangle, I'm guessing the OS is corrupt.
Any detailed instructions or pointing me to a proper thread would be appreciated.
That's a bootloop.
In recovery: swipe the guy away (from top to bottom works best). Then you should see the menu.
ranf said:
That's a bootloop.
In recovery: swipe the guy away (from top to bottom works best). Then you should see the menu.
Click to expand...
Click to collapse
Hey, thanks. So, I see the menu. I did the wipe data factory refresh and still nothing except the 4 symbols grinding away.
So, is see a "mount" option. I'm guessing that is where the watch is then mounted as a drive to a pc where where one could have files transferred from the pc to the watch. Would that be the next step or do I need to perform the partition option on the watch?
Sorry, I just am trying to get detailed instructions. BTW, I did notice that the OS is 6.0.1. I have read that many have downgraded to 5.1.1 as it may have been better for gps and battery life. Also, that is when this watch crashed was during the update.
Any detailed instructions from here would be greatly appreciated...again. Thanks
When a factory reset doesn't help it, the easiest way is the "repair" option in Xperia Companion. Basically it downloads the complete firmware (200-250MB) and flashes all the partitions. Very much like a factory image for a Nexus.
I don't know what mount actually does.
ranf said:
When a factory reset doesn't help it, the easiest way is the "repair" option in Xperia Companion. Basically it downloads the complete firmware (200-250MB) and flashes all the partitions. Very much like a factory image for a Nexus.
I don't know what mount actually does.
Click to expand...
Click to collapse
Thanks. As mentioned in the original post, that was tried...now three times to no avail. I did both options in the repair area of xperia. So, I'm guessing there is a more serious hardware issue or I need to somehow use something other than the xperia companion to remedy the situation. I had also tried the update again and it said it was successful, but there was not difference in the behavior of the watch...just the 4 dots/symbols going on forever.
I'm willing to root the device, but I just have not seen or probably better stated, understood how to do it. I am sort of a newbie and thus need detailed instructions. If the watch is bricked after that, then so be it. It is not doing any good right now anyways. Can some even point me to such a thing or help in writing it down?
Perhaps a stupid question, but after doing the repair thru xperia, I let it sit and grind for a good 20 minutes. I presume that is ample time for it to repair itself. Is that reasonable?
Repair is not the same as update in XC.
ranf said:
Repair is not the same as update in XC.
Click to expand...
Click to collapse
Thanks. Agree which is why I mentioned both the repair and the update were done on the watch and of course separately on XC.
So, basically, I have tried every option in xperian companion (repair and update) and the factory reset, clear cache and the partition option that come up on the watch itself. So, my next thougt was the to root it and try either downgrading the os or repairing in thru the root process. If someone could provide either a link or help with very detailed directions (for the complete idiot) on how to root it with that idea of replacing or repairing the os, that would be very much appreciated.
golfnut22 said:
Thanks. Agree which is why I mentioned both the repair and the update were done on the watch and of course separately on XC.
Click to expand...
Click to collapse
That wasn't so clear for me.
golfnut22 said:
So, basically, I have tried every option in xperian companion (repair and update) and the factory reset, clear cache and the partition option that come up on the watch itself. So, my next thougt was the to root it and try either downgrading the os or repairing in thru the root process. If someone could provide either a link or help with very detailed directions (for the complete idiot) on how to root it with that idea of replacing or repairing the os, that would be very much appreciated.
Click to expand...
Click to collapse
You can install this (Lollipop):
http://forum.xda-developers.com/smartwatch-3/orig-development/rom-sony-smartwatch-3-rom-t3367728
or this (Marshmallow):
http://forum.xda-developers.com/sma...sony-smartwatch-3-marshmallow-mec24h-t3382450
In Ubuntu you install fastboot this way:
Code:
sudo apt-get install android-tools-fastboot
You may want to create an udev rule, so that a normal user can access the watch in fastboot mode:
https://ranf.wordpress.com/2015/02/21/ubuntu-udev-rule-for-sony-smartwatch-3-swr50/
Otherwise you have to run fastboot with sudo.
I'd start with formatting cache and userdata:
1. get into recovery
2. from there get into fastboot (maybe it is called bootloader here, can't remember)
3. check connection
Code:
fastboot devices -l
4. format
Code:
fastboot format cache
fastboot format userdata
fastboot reboot
---------- Post added at 06:10 PM ---------- Previous post was at 06:07 PM ----------
golfnut22 said:
Since I'm getting the red triangle, I'm guessing the OS is corrupt.
Click to expand...
Click to collapse
Can you post a photo of that?
ranf said:
That wasn't so clear for me.
You can install this (Lollipop):
http://forum.xda-developers.com/smartwatch-3/orig-development/rom-sony-smartwatch-3-rom-t3367728
or this (Marshmallow):
http://forum.xda-developers.com/sma...sony-smartwatch-3-marshmallow-mec24h-t3382450
In Ubuntu you install fastboot this way:
Code:
sudo apt-get install android-tools-fastboot
You may want to create an udev rule, so that a normal user can access the watch in fastboot mode:
https://ranf.wordpress.com/2015/02/21/ubuntu-udev-rule-for-sony-smartwatch-3-swr50/
Otherwise you have to run fastboot with sudo.
I'd start with formatting cache and userdata:
1. get into recovery
2. from there get into fastboot (maybe it is called bootloader here, can't remember)
3. check connection
Code:
fastboot devices -l
4. format
Code:
fastboot format cache
fastboot format userdata
fastboot reboot
---------- Post added at 06:10 PM ---------- Previous post was at 06:07 PM ----------
Can you post a photo of that?
Click to expand...
Click to collapse
Thank you. And, sorry for the senior memory moment. I could not remember if it was recovery or repair in XC. Anyway, I think it is fair to say that I have tried every "canned" option in either XC or on the watch for recovery, repair and update to no avail.
Nice and thanks for the coding. I will also take a hard look at the links to see if I can proceed. When I fixed my HP Touchpad, there was a nice little toolbox that one could use to easily do a complete data reset, then load the three files and it would do the rest. That was all done in Ubuntu.
I'll report back once I get going.
Is it fair to say that as long as you do not mess with the bootloader, that you cannot brick the watch? After reading 12 or 13 threads, that seemed to be one of the comments. I did look at all the thread titles...17 pages to try and find things that were similar and they pointed to what we have already discussed in using XC, etc. So, I'll try another way that is outlined above.
I have attached the picture of the android guy with exclamation mark. Hopefully you will be able to see it.
golfnut22 said:
Thank you. And, sorry for the senior memory moment. I could not remember if it was recovery or repair in XC. Anyway, I think it is fair to say that I have tried every "canned" option in either XC or on the watch for recovery, repair and update to no avail.
Nice and thanks for the coding. I will also take a hard look at the links to see if I can proceed. When I fixed my HP Touchpad, there was a nice little toolbox that one could use to easily do a complete data reset, then load the three files and it would do the rest. That was all done in Ubuntu.
I'll report back once I get going.
Click to expand...
Click to collapse
Yes please do so.
golfnut22 said:
Is it fair to say that as long as you do not mess with the bootloader, that you cannot brick the watch?
Click to expand...
Click to collapse
You can play a lot with the watch without bricking. Doesn't mean it's impossible.
golfnut22 said:
After reading 12 or 13 threads, that seemed to be one of the comments. I did look at all the thread titles...17 pages to try and find things that were similar and they pointed to what we have already discussed in using XC, etc. So, I'll try another way that is outlined above.
I have attached the picture of the android guy with exclamation mark. Hopefully you will be able to see it.
Click to expand...
Click to collapse
A bit small but that's just the recovery droid?
To me that means more like "proceed with caution" than denoting a serious error condition.
ranf said:
That wasn't so clear for me.
or this (Marshmallow):
http://forum.xda-developers.com/sma...sony-smartwatch-3-marshmallow-mec24h-t3382450
Ok, so I downloaded 4 files. 2 of them were for two different cores: one was for 2 core and the other for 4 cores. Which one is proper or what's the difference for this watch?
In Ubuntu you install fastboot this way:
Code:
sudo apt-get install android-tools-fastboot
Yes, got it and that was easy.
You may want to create an udev rule, so that a normal user can access the watch in fastboot mode:
https://ranf.wordpress.com/2015/02/21/ubuntu-udev-rule-for-sony-smartwatch-3-swr50/
I tried the first command on the link two different times and I get vim: command not found. So I continued on.
Otherwise you have to run fastboot with sudo.
I'd start with formatting cache and userdata:
1. get into recovery
If this procedure is done on the watch by holding the power button until you get the "insert usb" connection screen, then quickly tapping the power button twice to bring up the next four screens possible screens by pressing the power button 1 time to move to the next screen (fastboot, recovery, normal boot, factory reset), I went into the recovery screen and did the wipe cache partition first and then the wipe data/factory refresh.
However, if those steps above are to be done on the ubuntu, then I'm lost already.
2. from there get into fastboot (maybe it is called bootloader here, can't remember)
If this is to see fastboot on the watch as one of the 4 screens noted above, that is easy. If it is to double press the power button while on the fastboot screen, I did that, but don't know what you mean by the next step..."check connection"
3. check connection
Code:
fastboot devices -l
4. format
Code:
fastboot format cache
fastboot format userdata
fastboot reboot
So assuming that I can eventually get thru step 4, how and do I get the watch to recognize or get the 3 files (assuming I do not need both the 2 and 4 core files)?
---------- Post added at 06:10 PM ---------- Previous post was at 06:07 PM ----------
Can you post a photo of that?
Click to expand...
Click to collapse
So, in the "previewing of my response or comments based on the instructions, it looks like I did not do the "multi-quote" correctly. I hope you can decipher what I said, as I have commented on the steps so far in your comment back to me and what I was able to do and not do at this point. I would appreciate any help you can further offer.
I went thru the whole process again or at least starting with the command "sudo -s". I got thru it all except when I tried to install the rom file with the signature check box checked, it failed. The first time I did it, I did not check the box, but when rebooting as noted above is just cycled thru twice then went to the android recovery guy.
"vim" is an editor. You can use any other (like nano or even gedit).
with "fastboot devices -l" you either get "offline" which means the udev rule doesn't work,
or you get an output starting with fastboot.
Most likely much easier:
Code:
sudo -s
fastboot devices -l
fastboot format cache
fastboot format userdata
fastboot reboot
exit
ranf said:
"vim" is an editor. You can use any other (like nano or even gedit).
with "fastboot devices -l" you either get "offline" which means the udev rule doesn't work,
or you get an output starting with fastboot.
Most likely much easier:
Code:
sudo -s
fastboot devices -l
fastboot format cache
fastboot format userdata
fastboot reboot
exit
Click to expand...
Click to collapse
OK, so not sure what the editor comment fix is, but I'll look into that later.
So, as mentioned I was able to get fastboot on the pc. However, the first time I entered "fastboot devices -1", it said waiting for device.
This morning when I read your new message, I did the sudo command to get fastboot again on the pc (I had already got the watch "running fastboot" per its screen), then entered "fastboot devices -1", and I get "invalid option -- '1'.
Also, after entering the first command "sudo -s", the next command line changed with the first word "root" and the end on the command line changed from ":~$" to ":~#".
golfnut22 said:
OK, so not sure what the editor comment fix is, but I'll look into that later.
So, as mentioned I was able to get fastboot on the pc. However, the first time I entered "fastboot devices -1", it said waiting for device.
This morning when I read your new message, I did the sudo command to get fastboot again on the pc (I had already got the watch "running fastboot" per its screen), then entered "fastboot devices -1", and I get "invalid option -- '1'.
Click to expand...
Click to collapse
That's a lowercase L (for longer output).
ranf said:
That's a lowercase L (for longer output).
Click to expand...
Click to collapse
I got vim working or at least loaded.
Yep, was using number 1 instead of small letter l. Thanks.
I ran thru the commands and on the writing cache at the end, it said "Failed (remote: Device locked)" . The same failure message was on the userdata command at the end. What should I do next
Edit: I found where you have to start with command "fastboot oem unlock" and enter it twice. Now I was able to wipe cache and userdata.
After performing the above fastboot commands and disconnecting watch. I powered up the watch and it is still cycling thru or stuck on the 4 dots or symbols. Sooooo,
I hate to keep asking, but is it correct to say I now need to repair/replace/update the OS? And if so, I'm not sure exactly how to do that. Can you advse?
Here I think are the next steps: (this was copied from your link above for MM)
Quote:
Installation:
Put ROM to your virtual SDCard
I don't know how to do this first step. Can you advise?
Boot into TWRP recovery
I don't know how to put TWRP on the watch unless it is part of the first step. Can you advise?
Select "Install", and choose ROM zip file
This appears easy after the step 1 and 2 above are complete.
After installation completed- reboot watch
If necessary - make full wipe
Quote:
Downloads
MWD49B
How would I know this is my watch? I have seen several different ones for the SW3.
I have downloaded all of the below files, but there are two that are similar. One is 4 cores and the other is for 2 cores. Do you know which one I should use or what the differences would be?
SWR50_6.0.1_MWD49B.zip v3
MEC24H
SWR50_6.0.1_MEC24H v2 (4 cores version)
SWR50_6.0.1_MEC24H v2 (2 cores version)
Recovery
TWRP recovery
1. boot TWRP: if it is a .zip unzip it. If it already is an .img file proceed.
2. sudo fastboot boot twrp.img
We don't install, only boot into it temporarily.
3. I usually see a new Nautilus (ubu filemanager) window pop up on my Ubuntu box (because MTP is enabled in TWRP)
4. you could now drag and drop the ROM.zip you want into that window.
5. now on the watch in TWRP select install
MWDxx MECxx are the build numbers. MWDxx being the newest.
2 or 4 cores doesn't make much of difference. The stock Sony kernel disables 2 cores (for powersaving reasons I suppose).
---------- Post added at 04:21 PM ---------- Previous post was at 04:18 PM ----------
golfnut22 said:
Also, after entering the first command "sudo -s", the next command line changed with the first word "root" and the end on the command line changed from ":~$" to ":~#".
Click to expand...
Click to collapse
You ran a root shell. The prompt shows this with a #.
ranf said:
That wasn't so clear for me.
You can install this (Lollipop):
http://forum.xda-developers.com/smartwatch-3/orig-development/rom-sony-smartwatch-3-rom-t3367728
or this (Marshmallow):
http://forum.xda-developers.com/sma...sony-smartwatch-3-marshmallow-mec24h-t3382450
In Ubuntu you install fastboot this way:
Code:
sudo apt-get install android-tools-fastboot
You may want to create an udev rule, so that a normal user can access the watch in fastboot mode:
https://ranf.wordpress.com/2015/02/21/ubuntu-udev-rule-for-sony-smartwatch-3-swr50/
Otherwise you have to run fastboot with sudo.
I'd start with formatting cache and userdata:
1. get into recovery
2. from there get into fastboot (maybe it is called bootloader here, can't remember)
3. check connection
Code:
fastboot devices -l
4. format
Code:
fastboot format cache
fastboot format userdata
fastboot reboot
---------- Post added at 06:10 PM ---------- Previous post was at 06:07 PM ----------
Can you post a photo of that?
Click to expand...
Click to collapse
ranf said:
1. boot TWRP: if it is a .zip unzip it. If it already is an .img file proceed.
2. sudo fastboot boot twrp.img
We don't install, only boot into it temporarily.
3. I usually see a new Nautilus (ubu filemanager) window pop up on my Ubuntu box (because MTP is enabled in TWRP)
4. you could now drag and drop the ROM.zip you want into that window.
5. now on the watch in TWRP select install
MWDxx MECxx are the build numbers. MWDxx being the newest.
2 or 4 cores doesn't make much of difference. The stock Sony kernel disables 2 cores (for powersaving reasons I suppose).
---------- Post added at 04:21 PM ---------- Previous post was at 04:18 PM ----------
You ran a root shell. The prompt shows this with a #.
Click to expand...
Click to collapse
Again, thank you for being very patient with some very basic questions. Ok, so I think I'm getting close. However, here are more basic questions before proceeding.
1. The watch has been disconnected since the previous steps where I wiped cache and userdata and exited fastboot. I also used XC to see if it would repair and update. To my surprise, now both of those functions failed. Do I need to start all over with the "sudo -s" command and proceed to make sure? If not, where would I start?
2. What status is the watch in when I do your #2 instruction? Is it in the connect usb screen or in fastboot. I'm guessing fastboot.
3. The file I have downloaded is the img file. On your #2 instruction, in Ubuntu, where should the img file be located when I enter "sudo fastboot boot twrp.img". I'm guessing the desktop, but wanted to make sure.
4. After your step #4 of dragging the file, do I need to exit out of Linux fastboot, then disconnect the watch, then power down then up the watch to see "install" in TWRP?
2. yes "fastboot running"
3. my Downloads land in ~/Downloads.
just run
Code:
cd
cd Downloads
to go there and fastboot boot from there. If it's in ~/Desktop well then go there.
4. stay in TWRP
Twrp screen is on the watch.
However,on the pc, I did not get the new file manager to place the new rom zip file. So, I'm not sure where or how to get the zipped file in the "install" folder. Any ideas? Thanks.
With TWRP visibly on the watch now, at the same time, can I use the command in ubuntu "sudo adb sideload <rom.zip>? I've been trying to find ways to get the rom.zip file in the watch...although I have not tried anything yet.
golfnut22 said:
Twrp screen is on the watch.
However,on the pc, I did not get the new file manager to place the new rom zip file. So, I'm not sure where or how to get the zipped file in the "install" folder. Any ideas? Thanks.
Click to expand...
Click to collapse
Ideas? Always.
AFAIK you can adb into a running TWRP.
Try this:
Code:
sudo apt-get install android-tools-adb
adb devices -l
# if you "see" your watch
adb push ROMfilename.zip /sdcard/
Oh BTW: what's your Ubuntu version?
Code:
lsb_release -a
is telling you that.