Related
I have no clue how this started. Last thing I did was flash Amon_RA 2.3 recovery on FEB 9th then the newest CM7 nightly, 32 I believe. Everything was fine with my phone up until an hour ago. I was on the phone with Sprint, they screwed up my sign-up date. But thats a whole other story. My phones battery was getting low during the call. Once I ended the call I set my phone down then noticed it started going into a boot cycle. Now all it will do is boot to the splash screen then reboot again, and again, and again. I tried to pull the battery and boot to recovery. It does the same thing. It will let me get to the bootloader and select recovery. Once I select recovery, it starts its damn boot loop. Any ideas? PLEASE HELP!
Well since you can't get into recovery, try pushing a recovery via adb or fastboot...
teh roxxorz said:
Well since you can't get into recovery, try pushing a recovery via adb or fastboot...
Click to expand...
Click to collapse
Its been soo long since I had to do any adb. Actually since launch using toasts root methods. Can you explain the commands please? On another note I do not have any recovery.img's saved to my pc. I dl'd them directly to my phone and flashed from a terminal app.
http://forum.xda-developers.com/showthread.php?t=705026
this thread can help you out especially the OP
download the amon-ra p36img.zip and place it onto your sdcard somehow, pull the battery, boot into bootloader, flash the pc36img and then reboot. they you'll have recovery and can load any rom you want again
t3project said:
download the amon-ra p36img.zip and place it onto your sdcard somehow, pull the battery, boot into bootloader, flash the pc36img and then reboot. they you'll have recovery and can load any rom you want again
Click to expand...
Click to collapse
^ Do exactly that [basically what I was saying/] But take out the battery and put the SD card in your computer via adapter to put the file on there.
Ok, the PC36IMG.ZIP is on the root of my sd and the bootloader is not seeing it? Now what?
if you're using windows make sure to not have the file as PC36IMG.zip.zip
mich11128 said:
if you're using windows make sure to not have the file as PC36IMG.zip.zip
Click to expand...
Click to collapse
Ok, I got it to see it. I ran the update, once it rebooted I selected recovery. It first asked me if I want to delete data? Or something on those terms. I chose no, and it will not let me boot to recovery still.....Back to the boot loops
Edit: First time I must have selected clear storage by mistake. Anyway I hit no at that point. I just re-dl'd the pc36img.zip file to make sure. It does run in the boot loader but will not reboot to recovery. Still endless loop????
splink7007 said:
Ok, I got it to see it. I ran the update, once it rebooted I selected recovery. It first asked me if I want to delete data? Or something on those terms. I chose no, and it will not let me boot to recovery still.....Back to the boot loops
Click to expand...
Click to collapse
Considering you can't get into recovery still, I would suggest reflashing the recovery and erasing the data when prompted.
Did you do a nandroid backup? I only ask cause once you get back into recovery you can just restore that.
so the bootloader read the file, then you ran the update and then it asked you to delete data? I don't remember that being a part of the process. Try it again and as soon as it's done updating try to get into the recovery again. If not then try to use adb.
sekigah84 said:
Considering you can't get into recovery still, I would suggest reflashing the recovery and erasing the data when prompted.
Did you do a nandroid backup? I only ask cause once you get back into recovery you can just restore that.
Click to expand...
Click to collapse
Ya I hit clear storage at first by mistake. I believe if I hit that it will wipe my entire sd card and will loose my nand backup?
mich11128 said:
so the bootloader read the file, then you ran the update and then it asked you to delete data? I don't remember that being a part of the process. Try it again and as soon as it's done updating try to get into the recovery again. If not then try to use adb.
Click to expand...
Click to collapse
Re-ran the update and still loops. The first time I ran it I hit clear storage instead recovery by mistake. Im sitting at the bootloader screen. I cant remember the adb commands. Can you refresh my memory? Thanks
Copy recovery-RA-supersonic-v2.3.img to the root of your sdcard
start the terminal app or launch adb shell
su(press enter)
flash_image recovery /sdcard/recovery-RA-supersonic-v2.3.img(press enter)
reboot recovery(press enter)
I find it strange that all this happened after getting off the phone with Sprint lol.
Does it still say S-OFF at the top of your bootloader?
I copied this from the amon ra recovery thread
Copy recovery-RA-supersonic-v2.3.img to the root of your sdcard
start the terminal app or launch adb
su(press enter)
flash_image recovery /sdcard/recovery-RA-supersonic-v2.3.img(press enter)
reboot recovery(press enter
now whenever I am about to start adb I use the command "./adb devices" without quotations of course, to make sure adb recognizes my evo oh and ignore the ./ that's just for mac users. When you enter that command you should see the serial number for your evo. after that I use
./adb shell
that should lead to
#
Then you type
su
and then you enter the rest of the commands. Sorry I didn't really organize it but that's pretty much it.
sekigah84 said:
Copy recovery-RA-supersonic-v2.3.img to the root of your sdcard
start the terminal app or launch adb shell
su(press enter)
flash_image recovery /sdcard/recovery-RA-supersonic-v2.3.img(press enter)
reboot recovery(press enter)
I find it strange that all this happened after getting off the phone with Sprint lol.
Does it still say S-OFF at the top of your bootloader?
Click to expand...
Click to collapse
lol you beat me to it and I was also about to ask if the phone was still rooted. READ MY MIND hahaha
sekigah84 said:
Copy recovery-RA-supersonic-v2.3.img to the root of your sdcard
start the terminal app or launch adb shell
su(press enter)
flash_image recovery /sdcard/recovery-RA-supersonic-v2.3.img(press enter)
reboot recovery(press enter)
I find it strange that all this happened after getting off the phone with Sprint lol.
Does it still say S-OFF at the top of your bootloader?
Click to expand...
Click to collapse
I totally agree!! Crazy....Yes it still says S-OFF. How do I launch adb shell from the bootloader? Im sorry, I havent used adb or fastboot since launch rooting using toasts method.
Wish I could help you there but I haven't ran adb on a windows since my G1 lol I'll see if I find a thread with some help for adb and windows.
EDIT: Maybe this will help. http://forum.xda-developers.com/showthread.php?t=694250
Ok, if I run fastboot devices, it sees my device. But if I run adb devices, it doesnt see my device anymore. Im soo lost now.
sorry I forgot adb runs through recovery, what you have to use I believe is fastboot flash to flash the recovery image
here try this page better...I used this when I had to root my nexus one the hard way (before that crappy 1-click method was devised) this is the best guide I'd ever used as far as adb/fastboot commands.
http://forum.xda-developers.com/showthread.php?t=694250
Hi Guys,
I was facing some issues with Virtuous Infinity v1.33 so I decided to do a full wipe. Although after doing a full wipe, I accidently rebooted the device instead of flashing the ROM again. Now my volume down button is a little dodgy and doesn't come in handy if I have to boot into the Bootloader/Recovery.
Is there any alternative to this?
Any help is appreciated.
Edit: If I power the device on, I see the white screen with the HTC logo and then it goes to a blank screen with nothing but the backlight on. I can charge my device if it's off. Oh & i've done a format - system, boot, data, all partitions except SD card.
Thanks in advance!
Have you removed the battery for a sec and then tried going into hboot? Regardless of all your partitions hboot should always be accessible, unless it has been wiped or corrupted, sometimes only a battery pull will let you access hboot again. If you absolutely can't get into hboot because of a bad volume rocker then you could try adb shell, but getting the pc to read phone is going to be tricky. If you hold volume up and power I think it goes into fastboot with a black screen.
did you try to boot in recovery mode with adb?
http://www.crocko.com/18FF41A02AB045FB8E821F6A614DEF0A/fastboot.zip
extract zip, open command prompt, go to the extraction directory an type: "adb reboot recovery" while phone is connected to your PC.
Good luck!
Gizmoe said:
Have you removed the battery for a sec and then tried going into hboot? Regardless of all your partitions hboot should always be accessible, unless it has been wiped or corrupted, sometimes only a battery pull will let you access hboot again. If you absolutely can't get into hboot because of a bad volume rocker then you could try adb shell, but getting the pc to read phone is going to be tricky. If you hold volume up and power I think it goes into fastboot with a black screen.
Click to expand...
Click to collapse
kinggizmo said:
did you try to boot in recovery mode with adb?
http://www.crocko.com/18FF41A02AB045FB8E821F6A614DEF0A/fastboot.zip
extract zip, open command prompt, go to the extraction directory an type: "adb reboot recovery" while phone is connected to your PC.
Good luck!
Click to expand...
Click to collapse
Thanks guys! the battery trick did it. I will save that file for any future references though.
It was 2AM and I was bored out of my mind at work :silly: If i knew how to close this thread I would. This is solved.
Thanks again!! :good:
Thank God i found this thread,
With fastboot finally i can manage running my DHD again using Blackout ROM. Honestly this is my 1st time flashing DHD and quite long night i spent off, thankfully it's done very well at last
Thank you a lot for all thread's participants :good:
Hello !
Here's my prob :
I installed CWM Recovery on my OUYA, and then i wanted to flash a ROM via recovery.
Unfortunately, i've done a full wipe while in recovery, and restarted the console.
Now it's turning on, with the power button on, black screen, and identifyed as an MTP USB device.
I tried the alt + Sysreq + i trick, but it doen't seems to work here ...
Any chance to get it back to life in other way ?
Keep trying alt + sysreq + i trick my takes about 50 times before the light on the ouya flashes then i have to hit the home key some times to see anything
imerrn said:
Keep trying alt + sysreq + i trick my takes about 50 times before the light on the ouya flashes then i have to hit the home key some times to see anything
Click to expand...
Click to collapse
What timing of button's hitting have you used ?
The light of the OUYA is flashing when in recovery mode ?
ElMeteK said:
What timing of button's hitting have you used ?
The light of the OUYA is flashing when in recovery mode ?
Click to expand...
Click to collapse
Try these timings. I had the same issue and these worked for me. The keyboard trick is currently your only hope.
I keep pressing alt + sysreq + i keys at the same time takes me about 30 times to get to recovery the light will flash one time then i know im in recovery some times iget the ouya smile with a ! mark some time a black screen then i press home button to get to recovery push the home button again it goes away i have done about three ouya.
Problem solved.
My ouya doesn't loved my Microsoft Keyboard...
I used a generic on, and it works directly
Ouya saved
Another advice : if it doesn't work, try another keyboard !
Ouya Bricked Need Help Reward For The Fixer
Here is my Issue I installed The CWM and flashed over a few ROMS but really wanted to try out the CM10. I had all my files backed up but some how they were all deleted and when I turn on my machine I get the Cyanogen boot loop and I can do the keyboard trick print screen/ Alt / I but there is no files to recover and I have no way to load any ROM directly to my internal nand flash unless there is something I am missing.
I am so upset I with thy would have put a sd card slot on this thing. Can anyone help me to try to recover putting any stock ROM back on my machine or is there a way to get my PC to read my device to load the ROM to my internal HD?
Please any help and instructions would be greatly appreciated.
I need some serious help here. Thanks to anyone who can get me back up and running again I will even send the person who has the solution one of my devices that run XBMC like a champ. Here is my site for anyone who is up for the challenge. www.xbmcandroidtv.com the EXOON Q2 Plus is the device I will send to the person who solves my dilemma.
I have tried the keyboard trick but all I get it to do is load into CWM and there is nothing to load. Am I doing something wrong?
Thanks in advance and eager to get my OUYA back up and running.
labossiere said:
Here is my Issue I installed The CWM and flashed over a few ROMS but really wanted to try out the CM10. I had all my files backed up but some how they were all deleted and when I turn on my machine I get the Cyanogen boot loop and I can do the keyboard trick print screen/ Alt / I but there is no files to recover and I have no way to load any ROM directly to my internal nand flash unless there is something I am missing.
I am so upset I with thy would have put a sd card slot on this thing. Can anyone help me to try to recover putting any stock ROM back on my machine or is there a way to get my PC to read my device to load the ROM to my internal HD?
Please any help and instructions would be greatly appreciated.
I need some serious help here. Thanks to anyone who can get me back up and running again I will even send the person who has the solution one of my devices that run XBMC like a champ. Here is my site for anyone who is up for the challenge. www.xbmcandroidtv.com the EXOON Q2 Plus is the device I will send to the person who solves my dilemma.
I have tried the keyboard trick but all I get it to do is load into CWM and there is nothing to load. Am I doing something wrong?
Thanks in advance and eager to get my OUYA back up and running.
Click to expand...
Click to collapse
You have to fastboot the "boot.img" supplied with CM10. I had the same issue so pm me if you need help.:good:
Never, ever ever ever ever ever wipe the boot.img, if you want to be safe, never replace it either, you can always 'fastboot boot boot.img" it.
Sent from my SAMSUNG-SGH-I317 using xda premium
at what point does your Ouya connect back to your pc so you can do a fastboot command? do you have to be in CWM?
glitchhawk said:
at what point does your Ouya connect back to your pc so you can do a fastboot command? do you have to be in CWM?
Click to expand...
Click to collapse
You can do it from CWM, but you don't have to be there. Depends on what you've done to your system. If you flashed CM10 and now it's detected as an MTP device your best bet is to reboot into recovery and 'adb reboot bootloader' then use fastboot commands. That's what worked for me.
BUS DR1V3R said:
You can do it from CWM, but you don't have to be there. Depends on what you've done to your system. If you flashed CM10 and now it's detected as an MTP device your best bet is to reboot into recovery and 'adb reboot bootloader' then use fastboot commands. That's what worked for me.
Click to expand...
Click to collapse
ok, cuz im basically in the same boat as everyone else. i flashed CM10 and now its hanging at the CM boot screen. so i guess its time to sit there and tap keys for hours lol.
BUS DR1V3R said:
You can do it from CWM, but you don't have to be there. Depends on what you've done to your system. If you flashed CM10 and now it's detected as an MTP device your best bet is to reboot into recovery and 'adb reboot bootloader' then use fastboot commands. That's what worked for me.
Click to expand...
Click to collapse
in stock recovery am i suppose to go into sideload sub menu? my pc doesn't detect the ouya in the main recovery menu
glitchhawk said:
in stock recovery am i suppose to go into sideload sub menu? my pc doesn't detect the ouya in the main recovery menu
Click to expand...
Click to collapse
How does the Ouya show up in device manager? Is there an exclamation point beside it?
If the drivers are fine then try mounting /data in recovery.
BUS DR1V3R said:
How does the Ouya show up in device manager? Is there an exclamation point beside it?
If the drivers are fine then try mounting /data in recovery.
Click to expand...
Click to collapse
sorry, how do i mount it? the only options i have in stock recovery is
Reboot system now
Apply update from ADB (if i go into this menu i have the driver installed on pc and it comes up adb composite device)
wipe data/factory reset
wipe cache partition
glitchhawk said:
sorry, how do i mount it? the only options i have in stock recovery is
Reboot system now
Apply update from ADB (if i go into this menu i have the driver installed on pc and it comes up adb composite device)
wipe data/factory reset
wipe cache partition
Click to expand...
Click to collapse
Ah, stock recovery.... You could go into Apply Update From ADB. Then type "adb reboot bootloader" then you can type "fastboot boot boot.img" to boot successfully into CM10.
You can put the boot.img for CM10 in the same folder as fastboot.exe to make things easier.
BUS DR1V3R said:
Ah, stock recovery.... You could go into Apply Update From ADB. Then type "adb reboot bootloader" then you can type "fastboot boot boot.img" to boot successfully into CM10.
You can put the boot.img for CM10 in the same folder as fastboot.exe to make things easier.
Click to expand...
Click to collapse
well this is lame.. it keeps telling me Error: Closed
glitchhawk said:
well this is lame.. it keeps telling me Error: Closed
Click to expand...
Click to collapse
What keeps telling you that? What are you doing? I need more information.
BUS DR1V3R said:
What keeps telling you that? What are you doing? I need more information.
Click to expand...
Click to collapse
I put the Ouya on sideload from adb.
Then i open adb on my pc, check to make sure it finds the Ouya and then i try to adb reboot bootloader. and that error comes up. if i try to load an .img file from the same place it just says <waiting for device> and doesn't ever move.
glitchhawk said:
I put the Ouya on sideload from adb.
Then i open adb on my pc, check to make sure it finds the Ouya and then i try to adb reboot bootloader. and that error comes up. if i try to load an .img file from the same place it just says <waiting for device> and doesn't ever move.
Click to expand...
Click to collapse
If it says <waiting for device> then its probably a driver issue with fastboot. When you reboot into the bootloader go into device manager and check the driver again. I also had this issue.
hey guys,
i was bored and flashed a .zip on my phone and now I'm no longer bored. Long story, short... I'm booted into the os (almost) with constant errors popping up. I can't get the power button down for 10 seconds to reboot phone and i want to get back to recovery to flash by back up. How can I use terminal (mac) to force back into recovery if phone is not in mode for adb to recognize phone?
Thanks in advance.
Try hold power button + volume up to force reboot. Once the screen goes black release those buttons and hold volume down button to go to hboot
Thanks for your reply. Seems the power + volume is not be recognized. Is there a way with fastboot or adb?
Otherwise, I guess I wait until power drain.
andason said:
Thanks for your reply. Seems the power + volume is not be recognized. Is there a way with fastboot or adb?
Otherwise, I guess I wait until power drain.
Click to expand...
Click to collapse
Power + Volume Up should work. But as you asked for adb/fastboot
1) "adb devices" to check if device is recognized
2) "abd reboot bootloader" so the phone reboots into bootloader
3) go to recovery and try a reflash
andason said:
Thanks for your reply. Seems the power + volume is not be recognized. Is there a way with fastboot or adb?
Click to expand...
Click to collapse
This should always work as long as the screen is on. It might take 10 seconds or more, so you may not be holding the buttons long enough.
Alternately, you can use:
adb reboot bootloader
or
adb reboot recovery
There is no required more for adb commands, as long as the screen is on. Fastboot on the other hand, requires the phone to be in fastboot mode.
What did you flash? Was it a ROM, and if so did you do a full wipe (data, cache and Dalvik) before flashing?
Thanks for all the replies. It finally died and I was able to jump back into recovery. I was trying to flash a .zip (one+ one theme) to my rom and some things about it (audiofx) was not liked. I guess adb could not recognize the phone since it was basically booted into the os. I just thought there was a way to still use adb or fast boot to push it into recovery. I did not get to try adb reboot boot loader, but would adb recognize phone even with this command?
andason said:
Thanks for all the replies. It finally died and I was able to jump back into recovery. I was trying to flash a .zip (one+ one theme) to my rom and some things about it (audiofx) was not liked. I guess adb could not recognize the phone since it was basically booted into the os. I just thought there was a way to still use adb or fast boot to push it into recovery. I did not get to try adb reboot boot loader, but would adb recognize phone even with this command?
Click to expand...
Click to collapse
Glad it worked and that we could help a
adb reboot bootloader should be recognized nearly any time.
Sent from my HTC One_M8 using XDA Free mobile app
Hello,
Something interesting happened... I have rebooted to fastboot, unlocked, jumped back to fastboot, and there were few thing to select "reboot" "shutdown" "reboot bootloader" "reboot recovery". I thought to myself, well lets look how does the stock recovery looks like... And now I'm stuck with this.
https://youtu.be/ea1gZ_KohAw
It doesn't matter how long I press the power button... It still reboots into this nonsense...
So... Anyone encountered the same problem?
Should I just wait until the battery will drain?
On the screen it says:
E:failed to mount /cache (invalid argument)
E:Can't mount /cache/recovery/last_locale
EDIT: SOLVED
Ereniemis said:
Hello,
Something interesting happened... I have rebooted to fastboot, unlocked, jumped back to fastboot, and there were few thing to select "reboot" "shutdown" "reboot bootloader" "reboot recovery". I thought to myself, well lets look how does the stock recovery looks like... And now I'm stuck with this.
https://youtu.be/ea1gZ_KohAw
It doesn't matter how long I press the power button... It still reboots into this nonsense...
So... Anyone encountered the same problem?
Should I just wait until the battery will drain?
On the screen it says:
E:failed to mount /cache (invalid argument)
E:Can't mount /cache/recovery/last_locale
EDIT: SOLVED
Click to expand...
Click to collapse
how did you solve??
xlylegaman said:
how did you solve??
Click to expand...
Click to collapse
Okay...
1) booted to fastboot through http://forum.xda-developers.com/huawei-watch/development/guide-boot-fastboot-mode-t3225382
2) booted to recovery, not with "FLASH" just with "fastboot boot twrp.img" (e.g. http://forum.xda-developers.com/hua...p-twrp-2-8-7-0-recovery-huawei-watch-t3224714 )
3) went to "reboot" in TWRP and clicked "reboot to recovery", since I haven't flashed the recovery, just booted into it, it rebooted to the stock recovery.
4) In stock recovery I have done factory reset and it started to work again.
PS: I rebooted from TWRP to stock recovery, because the TWRP couldn't mount any of my /system/ /cache/ /data/, but the stock worked flawlessly.
Won't work
Ereniemis said:
Okay...
1) booted to fastboot through http://forum.xda-developers.com/huawei-watch/development/guide-boot-fastboot-mode-t3225382
2) booted to recovery, not with "FLASH" just with "fastboot boot twrp.img" (e.g. http://forum.xda-developers.com/hua...p-twrp-2-8-7-0-recovery-huawei-watch-t3224714 )
3) went to "reboot" in TWRP and clicked "reboot to recovery", since I haven't flashed the recovery, just booted into it, it rebooted to the stock recovery.
4) In stock recovery I have done factory reset and it started to work again.
PS: I rebooted from TWRP to stock recovery, because the TWRP couldn't mount any of my /system/ /cache/ /data/, but the stock worked flawlessly.
Click to expand...
Click to collapse
I tried the above but after the bootloop adb won't recognize my device, so after entering bootloader I can't flash twrp. Any solutions?
Check your drivers, if you have eg. windows 7/8/8.1/10 you will have to install proper driver... which is not-official driver for hwatch, and I had to restart windows in "developer mode" "disable driver signatures" and then I have succesfully installed drivers and the computer recognized it.
To install hwatch drivers I've used this https://www.reddit.com/r/hwatch/comments/3n9ckp/how_to_get_adb_access_over_usb/
and maybe you can use this, but I'm not sure http://forum.xda-developers.com/huawei-watch/general/unlocking-easy-t3205219
Ereniemis said:
Check your drivers, if you have eg. windows 7/8/8.1/10 you will have to install proper driver... which is not-official driver for hwatch, and I had to restart windows in "developer mode" "disable driver signatures" and then I have succesfully installed drivers and the computer recognized it.
To install hwatch drivers I've used this https://www.reddit.com/r/hwatch/comments/3n9ckp/how_to_get_adb_access_over_usb/
and maybe you can use this, but I'm not sure http://forum.xda-developers.com/huawei-watch/general/unlocking-easy-t3205219
Click to expand...
Click to collapse
I tried installing the drivers from the above link, and disable signature verification too. Tried the second method suggested to force the drivers also and still no success.
Is it possible that my watch sin't allowing ADB access?
When the new update came, I factory reset my watch, unlocked bootloader, tried rebooting into recovery so i could flash and this happened.
Will I have to replace the watch?
Doesn't work. Makes me think my partitions are f**ked. In the past, I was able to odin myself out of this. I have no idea what to do guys.
Any idea?
FIXED: By doing what he said before by booting to TWRP. But when you do, do this. WIPE -> Advanced wipe -> Select Cache -> tap "Repair or change File System" -> Repair. After this, I had no more bootloops when going to stock recovery. Now to figure out why I keep throwing the error 7 when updating to MM.
hi
i managed to get mine working as well ! (Thanks to abhanli, pkt_lnt and skin180)
make sure you are in fastboot menu on your watch (holding the power button till switches off and the pressing again after vibrates)
most important thing next is to press shift and right click anywhere in the adb folder on your computer, and then run command prompt from there, otherwise adb will not load up and you will think that you have just run a dodgy script !
unlock your bootloader (typing "Fastboot Oem Unlock" in the command prompt in adb folder)
then you can use steps of skin180 (link above)
OR
https://developer.android.com/wear/preview/downloads.html
scroll down to huawei watch and choose second download option (non preview image for after testing) (thanks pkt_lnt)
extract into your adb folder (located in c:\)
then using the command prompt in adb folder, navigate to that extracted folder (using dos commands)
then if you are on windows, type "flash-all.bat"
hey presto - will work !
when it reboots, you may think "darn it still has spinning dots !" but if you wait about 5-10 mins it progresses past that stage and comes up with welcome screen !
My watch is working again !
HUAWEI customer services are a pile of POO. Their repair centre in UK is waste of time. They never answer the phone and never reply to messages.
If the Huawei watch wasnt so beautiful, i'd never bother with them !
Good luck and thanks all.
Good work poorak!
But, you only need to post this information once, not several times on different threads....
galaxys said:
Good work poorak!
But, you only need to post this information once, not several times on different threads....
Click to expand...
Click to collapse
thought id help as many people as i can for which ever thread they get to whilst searching for a solution !
Hwatch bootloop issue
Hi i have hwatch with bootloop too, tried to do everything i could and i can't get my computer to recognise hwatch, i only get "unknown device" in manager, i have stock recovery, locked bootloader and bricked device i've tried to force instal drivers, dissabling signed drivers, and manually from "naked drivers" post above, no success, PLEASE help
Recovery bootloop
titus1001234 said:
Hi i have hwatch with bootloop too, tried to do everything i could and i can't get my computer to recognise hwatch, i only get "unknown device" in manager, i have stock recovery, locked bootloader and bricked device i've tried to force instal drivers, dissabling signed drivers, and manually from "naked drivers" post above, no success, PLEASE help
Click to expand...
Click to collapse
Hi, i have the same problem. My watch has an infinite recovery bootloop. I tried to turn on the watch in fastboot mode but it isn' t recognized by the pc, no feedback sounds or unrecognized driver, it's like it isn"t connected. Did you solve the problem?
Ereniemis said:
Hello,
Something interesting happened... I have rebooted to fastboot, unlocked, jumped back to fastboot, and there were few thing to select "reboot" "shutdown" "reboot bootloader" "reboot recovery". I thought to myself, well lets look how does the stock recovery looks like... And now I'm stuck with this.
https://youtu.be/ea1gZ_KohAw
It doesn't matter how long I press the power button... It still reboots into this nonsense...
So... Anyone encountered the same problem?
Should I just wait until the battery will drain?
On the screen it says:
E:failed to mount /cache (invalid argument)
E:Can't mount /cache/recovery/last_locale
EDIT: SOLVED
Click to expand...
Click to collapse
this thing happen to me but not in my watch in my phone, Im currently using huawei gr5 2017, what should i do? please help me
poorak said:
hi
i managed to get mine working as well ! (Thanks to abhanli, pkt_lnt and skin180)
make sure you are in fastboot menu on your watch (holding the power button till switches off and the pressing again after vibrates)
most important thing next is to press shift and right click anywhere in the adb folder on your computer, and then run command prompt from there, otherwise adb will not load up and you will think that you have just run a dodgy script !
unlock your bootloader (typing "Fastboot Oem Unlock" in the command prompt in adb folder)
then you can use steps of skin180 (link above)
OR
https://developer.android.com/wear/preview/downloads.html
scroll down to huawei watch and choose second download option (non preview image for after testing) (thanks pkt_lnt)
extract into your adb folder (located in c:\)
then using the command prompt in adb folder, navigate to that extracted folder (using dos commands)
then if you are on windows, type "flash-all.bat"
hey presto - will work !
when it reboots, you may think "darn it still has spinning dots !" but if you wait about 5-10 mins it progresses past that stage and comes up with welcome screen !
My watch is working again !
HUAWEI customer services are a pile of POO. Their repair centre in UK is waste of time. They never answer the phone and never reply to messages.
If the Huawei watch wasnt so beautiful, i'd never bother with them !
Good luck and thanks all.
Click to expand...
Click to collapse
problem is i can't find that download