Related
>>GUIDE<<
This guide will work to root the stock ROM. None of that automated stuff where you don't know what's going on. This guide will explain it step by step and you will actually know what's going on when you root a ROM
If you want to boot into a recovery image, simple use:
fastboot boot recovery.img
Note: You'll have to find the correct recovery.img file for your phone!!
Ok i unlocked the bootloader but when I input step 2 It says error: device not found? Everything worked normally?? What gives?
kp432 said:
Ok i unlocked the bootloader but when I input step 2 It says error: device not found? Everything worked normally?? What gives?
Click to expand...
Click to collapse
Make sure you have the correct drivers installed and you have USB debugging enabled.
If you are on Win 7 x64, hook up your phone to your computer, boot into the bootloader, and check out Device Manager (right click My Computer, Properties, Device Manager).
If you see in "Other Devices" a device called Android 1.0 (I can't remember off the top of my head), right click it, update drivers. Tell Windows you want to browse for the drivers, click to see the list of drivers you already have installed, and scroll down to find the Samsung Android Phone or whatever it's called.
kp432 said:
Ok i unlocked the bootloader but when I input step 2 It says error: device not found? Everything worked normally?? What gives?
Click to expand...
Click to collapse
your drivers probably arent installed properly. download PDA net and use it on your computer and it should install the drivers for you
Can't gain root after unlocking bootloader
xx
kp432 said:
Ok i unlocked the bootloader but when I input step 2 It says error: device not found? Everything worked normally?? What gives?
Click to expand...
Click to collapse
Same here. And I did install PDAnet prior to attemping this so that I would have the correct drivers.
I have tried this on 2 different computers and I keep getting the same error. When I try to do "adb root" it will start daemon and then it will fail.
It keeps saying "Error: Device Not Found"
same error as everyone else..
"adbd cannot run as root in production builds"
I noticed my bootloader says unlocked...is that good?
DenzelChurchill said:
Hey guys,
I can't seem to boot straight into boot.cdma.img. Soon after this command, the phone boots (doesn't make it to the ROM boot animation), then reboots, then goes into the ROM. When I try "adb root" I get the "production" error message. I have a Verizon CDMA/LTE Galaxy Nexus and I'm connecting it to Mac OS X. Thoughts?
Detailed explanation below for those curious...
Thanks everyone!
1. Boot phone into bootloader
2. Terminal: fastboot oem unlock (say yes to prompt, then return to bootloader)
3. Terminal: fastboot boot.cdma.img
4. Phone reboots, but doesn't make it to the ROM boot animation before it reboots again (I know this because it goes black for a second and vibrates slightly)
5. Phone boots into stock ROM, where I quickly dismiss all prompts and move to the settings menu to enable USB debugging
6. Terminal: adb root (Error message: "adbd cannot run as root in production builds")
7. I confirm that I don't have root by loading up Superuser and attempting to update binaries, where I'm told that it has failed the "Gain root..." step.
EDIT: Added phone / computer details.
Click to expand...
Click to collapse
remember, that command is supposed to be
fastboot boot boot.cmda.img
xx
hello I have unlocked the boot loader and rooted, installed cwm, my only problem is I do not have any 4g connectivity , I checked to see if its on lte cdma it is , powered off phone , battery pull ,reboot phone 4g shows up but will not stay connected. dont know if this has anything to do with root or what but my t-bolt has had 4g all day and nexus is right beside it. any ideas, thanks
Seaman24 said:
hello I have unlocked the boot loader and rooted, installed cwm, my only problem is I do not have any 4g connectivity , I checked to see if its on lte cdma it is , powered off phone , battery pull ,reboot phone 4g shows up but will not stay connected. dont know if this has anything to do with root or what but my t-bolt has had 4g all day and nexus is right beside it. any ideas, thanks
Click to expand...
Click to collapse
I know their network was down from around 6am EST to Noon EST. And last night on some cities on the west coast.
I actually lost 3g data for that time as well.
DenzelChurchill said:
Hey guys,
1. Boot phone into bootloader
2. Terminal: fastboot oem unlock (say yes to prompt, then return to bootloader)
3. Terminal: fastboot boot boot.cdma.img
4. Phone reboots, but doesn't make it to the ROM boot animation before it reboots again (I know this because it goes black for a second and vibrates slightly)
5. Phone boots into stock ROM, where I quickly dismiss all prompts and move to the settings menu to enable USB debugging
6. Terminal: adb root (Error message: "adbd cannot run as root in production builds")
7. I confirm that I don't have root by loading up Superuser and attempting to update binaries, where I'm told that it has failed the "Gain root..." step.
Click to expand...
Click to collapse
I had the exact same problem where the phone reboots before it loads into boot.cdma.img, followed by the "production builds" error (as in your steps 4-6)
What worked was going back to bootloader, and running "fastboot boot boot.cdma.img" again
It loaded very quickly. When i ran "adb root" it actually said that the device was already rooted or something similar. The proceeding steps went very smoothly.
Hope this helps
---------- Post added 22nd December 2011 at 12:05 AM ---------- Previous post was 21st December 2011 at 11:59 PM ----------
aznxk3vi17 said:
Make sure you have the correct drivers installed and you have USB debugging enabled.
If you are on Win 7 x64, hook up your phone to your computer, boot into the bootloader, and check out Device Manager (right click My Computer, Properties, Device Manager).
If you see in "Other Devices" a device called Android 1.0 (I can't remember off the top of my head), right click it, update drivers. Tell Windows you want to browse for the drivers, click to see the list of drivers you already have installed, and scroll down to find the Samsung Android Phone or whatever it's called.
Click to expand...
Click to collapse
I can confirm this. You need to be in bootloader to see the device driver error. It will show a Android 1.0 with an exclamation mark over it. I believe the device is a labeled as a storage drive or something similar (its not under "Android Phone")
Follow the above instructions to apply the SAMSUNG drivers
Just wanted to say thanks for this. I am fairly new to this but this seemed a lot less complicated.
Just one thing, I couldn't figure out why I couldn't run the adb root command until reading some more and finding that I had to enable USB debugging then reboot again. Hope that helps someone.
Thanks again all.
Also, how do you unroot the phone after using this method?
How to do on mac
I am new to doing this on Mac. I know that it is kind of the same but what is different when I am doing this on a Mac as apposed to a PC?
numbskill said:
I had the exact same problem where the phone reboots before it loads into boot.cdma.img, followed by the "production builds" error (as in your steps 4-6)
What worked was going back to bootloader, and running "fastboot boot boot.cdma.img" again
It loaded very quickly. When i ran "adb root" it actually said that the device was already rooted or something similar. The proceeding steps went very smoothly.
Hope this helps
Click to expand...
Click to collapse
any idea why this happens? I rooted 3 phones with this method. The first one went smoothly. The second two went through the reboots. In one case, I actually loaded an odin to get it back to the boot animation, otherwise I was stuck on the unlocked Google screen. Would be nice to know what I might be doing before I root someone else's phone.
xx
Does following this guide erase your phone? When it says boot the CDMA.img, I'm thinking it's going to replace the already installed image with a stock version that has root.
Or am I completely missing the mark here? I read what the guide wrote, but it doesn't really say if it's going to replace my stock image or what's going to happen.
BUMP?
The file linked on that thread is 404'd. Also, does this work on 4.0.4? I want to root but learn at the same time so I want to avoid using the toolkit. Does the toolkit work on 4.0.4? Thanks.
i ran into a little problem idk what it is this is the first time i run into this problem. i enter the first command prompt into terminal i think its
./fastboot-mac oem unlock and all it says is:
./fastboot-mac: operation not permitted
i don't know what I'm doing wrong help??
Model: GT-I9250T
Original Android version 4.04.
Root method: Gained root without having to unlock or overwrite the vanilla boot-loader and used OTA RootKeeper to backup su.
Long story short: My phone recently updated to 4.2.1 OTA. I restored root using OTA RootKeeper without issue. However when I went to restore The LBE Privacy app service, it caused my Nexus to enter a loop the moment it finishes booting and the lock screen appears.
Behavior:
After booting to the lock screen, the screen flashes and goes black then gets back to desktop and starts all over again in a loop. Once it does that about 3 or 4 times, it'll eventually get to a totally black screen except for the Android robot guy lying down with his belly open and an exclamation mark coming out. It'll then sit like that for about a minute and then the phone will reboot from scratch and the whole process repeats.
Apparently i'm not the only one either: url = badappreviews.com/apps/23315
From the linked site it looks like someone fixed it by using clockworkmod. However I don't see how that's possible as there is no way to enable usb debugging or copy any files to the sdcard as you can't boot the phone properly in the first place. I also noticed that I can no longer get into fastboot using the volume up and power button. However I can get into Odin mode.
Any ideas???
Install CWM or TWRP, wipe it clean, mount sdcard from there or adb sideload a ROM.
Sent from my Galaxy Nexus using Tapatalk 2
iLeopard said:
Install CWM or TWRP, wipe it clean, mount sdcard from there or adb sideload a ROM.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
But how do I do that if I can't get usb debugging or get it connected to a computer or fastboot as mentioned?
Edit: nvm, looks like i am able to get into fastboot after all.Now here's hoping I can install it without having usb debugging enabled.
.DCCXVIII said:
But how do I do that if I can't get usb debugging or get it connected to a computer or fastboot as mentioned?
Edit: nvm, looks like i am able to get into fastboot after all.Now here's hoping I can install it without having usb debugging enabled.
Click to expand...
Click to collapse
Just flash the android stock image through adb and go from there. You don't need debugging access when you're in fast boot
Have I helped? Don't forget to make love to that "Thanks" button!
Download stock images and flash em via fastboot, but you will lose everything. Its the freshest start you can get.
Sent from my Nexus Prime
Seriously, do you need to 'enable debugging' to be able to use adb in recovery?? It's a completely different and independent partition.
And fastboot doesn't need any enabling at all.
So, boot to recovery
mounts and storage
mount sd card
open up a DOS box (or terminal if you're on a mac or linux)
<path to adb>/adb shell
...
profit
The ... is where you go and uninstall the app/service, like the example you found mentioned above.
Usually this would be removing a .apk from either /system/app or /data/app
Thanks for all the help, however i am unable to get the adb drivers installed. I tried both Samsung's and Google's and they both fail (Windows doesn't even recongise a driver even after pointing it to: \sdk\extras\google\usb_driver. Anyone got any other sources for a working driver? Win7 64bit.
Edit: Managed to connect it using the pdanet drivers. Then proceeded to try to load CWM using: "fastboot flash recovery *file name*.img", but just got an error: "FAILED (remote: invalid argument)". I noticed that on my fastboot menu, it says lock state: Locked. Is this why it's failing? The boot loader is still locked? Because I tried "fastboot oem unlock" and that didn't work: "FAILED (unknown status code)".
Edit: Looks like my phone just needed a reboot. Because once I did, I was able to use the fastboot oem unlock command with success! However, before I proceed with unlocking the bootloader, can someone please confirm for me that I need to do so in order to install CWM? Many thanks.
Yes, but unless you have a play store gnex, this will probably wipe your phone anyway.
Sent from my brain using telepathy
m.is.for.michael said:
Yes, but unless you have a play store gnex, this will probably wipe your phone anyway.
Sent from my brain using telepathy
Click to expand...
Click to collapse
OK, i've managed to successfully unlock the bootloader, flash CWM and used the "fix permissions" function. I lost all my data/apps etc but I now have a working phone! Many thanks to all that helped!
Good night.
I have to ask for help when trying to install custom recovery on this awesome machine.
I have done all steps and wen good, but when doing the final steps:
6) Use fastboot to boot CWM by running "fastboot boot /path/to/OuyaCWMrecovery6.0.3.2.img". This boots from our CWM recovery without writing to any partitions.
When writing this, says "wating for device" and dont advance.
I searched into ouya forums but i could not find the solution.
Also, drivers,sdk and su files are correctly installed.
Thanks for help
asanz00 said:
Good night.
I have to ask for help when trying to install custom recovery on this awesome machine.
I have done all steps and wen good, but when doing the final steps:
6) Use fastboot to boot CWM by running "fastboot boot /path/to/OuyaCWMrecovery6.0.3.2.img". This boots from our CWM recovery without writing to any partitions.
When writing this, says "wating for device" and dont advance.
I searched into ouya forums but i could not find the solution.
Also, drivers,sdk and su files are correctly installed.
Thanks for help
Click to expand...
Click to collapse
Usually that happens when the device isn't at the bootloader. Did you run "adb reboot bootloader" to get to the bootloader?
Sent from my Nexus 7 using xda premium
Yes, i followed all steps, including "adb reboot bootloader" and then waited 30 seconds, just the way its written
At this stage, ouya its switched on but not image, so i suposed i am into bootloader
MIght be a driver issue. On mine the first time I booted into fastboot mode I had to go into device manager, found the android device with a yellow triangle, and had to install the drivers manually with "have disk". Hope this helps.
asanz00 said:
Yes, i followed all steps, including "adb reboot bootloader" and then waited 30 seconds, just the way its written
At this stage, ouya its switched on but not image, so i suposed i am into bootloader
Click to expand...
Click to collapse
Same thing happened to me, I never saw anything until I fastbooted the .img. And then I had to try it on 3 displays before one would show CWM. However after I flashed the .zip I have since tried all the displays and they all have worked every time.
Wow problem solved!
In devices administrator, there was one small called "fastboot" with yellow triangle.
I manually installed a driver called "android bootloader interface" and now it is working
thanks a lot!!!
No problem, always glad to help.
Now im fighting to get multi usb support via using a 5 ports usb-hub, i will write if i can ge througt
Can you post about that in the USB thread ? I just bought an active USB cable and 4 port hub, I hope they weren't a waste. I'll still get some use on my laptop, but not enough to justify the purchase.
Sent from my GT-P3113 using Tapatalk 4 Beta
Hey all,
So I seem to have soft bricked my tablet (Nexus 7 2013 LTE). I can get into fastboot mode (but not into the recovery menu) then I am stuck on the Google logo. Does this mean the device is repairable?
Device manager on Windows shows the tablet as
- an unknown device (no drivers installed / Samsung (Wugfresh) / Google drivers)
- Android bootloader interface (Snoop05's tool)
- Android ADB Interface (PDAnet (Wugfresh)).
On all of them the driver is not correctly installed and I have the exclamation mark showing on device manager. I am unable to access the tablet via fastboot or ADB at this time.
I have tried every permutation I can think of so am turning to the hive mind for advice.
To compound matters I am in Turkey and I don't speak Turkish. I've been in an internet cafe for about 5 hours now and it's 1am (Turkish keyboards have an ı where i should be and you can imagine how many times I have mistyped). I am on a year long cycle tour and the tablet has my music, books, guidebooks and dictionaries on it so I am pretty hacked off. Especially given that I've only just arrived...
I did manage to connect via ADB yesterday but ran out of time as I was borrowing someone's computer and can't replicate the steps. Gah!
I have backups of all my data so essentially I would just like to factory reset. Any help gratefully received!
Thanks,
Don
Well, I found the right combination of drivers (Snoop05's tool then PDANet on Wugfresh) and can now see the device via fastboot so I have unlocked it. However whenever I try and flash boot / system / recovery, etc via fastboot I'm receiving an error 'remote: partition table doesn't exist'. Any ideas, people?
Probably useful to add that the problem was initially caused when I removed the SIM card whilst the unit was switched on. I received a message asking me to reboot and it has been bricked since. Also, I was runing stock unrooted.
Thanks
I have now tried every toolkit I can find but still no joy. I seem to have corrupted my partition table which is preventing me writing anything to the device.
To confirm - I can boot into fastboot mode and can see the device via fastboot using command line and can unlock it using 'fastboot oem unlock'. I have the images to write using 'fastboot flash boot/recovery/system [image location] but nothing will let me write to the device without receiving the error 'FAILED - remote: partition table doesn't exist'.
I have searched everywhere and can't find very much. Is the device recoverable or have I fecked it...? I need to get out of internet cafes and onto my bike...
Cheers in advance
Gulp! 100+ views and no replies...does no-one want to break it to me that my lovely tablet is beyond help! Is the only solution some wizardry using GParted or something? I'm already in way over my head.
I'm only bugging you all as I am running out of time in town and need to head off into the wilds. I have tonight and that's it for at least a week. It would be nice to have some company ie books and music...oh and a Turkish dictionary and translator...poor attempt to drum up sympathy I know.
I'll be honest, I've never seen such an issue as yours but it's worth a try since you got fastboot to do fastboot format of all your partitions and see if it helps to flash factory image. Something like fastboot format system for example.
Sorry I can't be more help
Nexus 7 LTE
Carbon Rom
Faux Kernel
dondelion said:
I have now tried every toolkit I can find but still no joy. I seem to have corrupted my partition table which is preventing me writing anything to the device.
To confirm - I can boot into fastboot mode and can see the device via fastboot using command line and can unlock it using 'fastboot oem unlock'. I have the images to write using 'fastboot flash boot/recovery/system [image location] but nothing will let me write to the device without receiving the error 'FAILED - remote: partition table doesn't exist'.
I have searched everywhere and can't find very much. Is the device recoverable or have I fecked it...? I need to get out of internet cafes and onto my bike...
Cheers in advance
Click to expand...
Click to collapse
Remove Wug's drivers and what ever other old drivers you have and follow this tutorial http://forum.xda-developers.com/showthread.php?t=2381582 make sure your getting for the data and not WiFi only. Get them old drivers out of there first.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
Raverbunny said:
I'll be honest, I've never seen such an issue as yours but it's worth a try since you got fastboot to do fastboot format of all your partitions and see if it helps to flash factory image. Something like fastboot format system for example.
Sorry I can't be more help
Nexus 7 LTE
Carbon Rom
Faux Kernel
Click to expand...
Click to collapse
Fastboot format still appears to require an intact partition table as I still receive an error - 'FAILED (command write failed (invalid argument))' but thank for the response.
LinearEquation said:
Remove Wug's drivers and what ever other old drivers you have and follow this tutorial http://forum.xda-developers.com/showthread.php?t=2381582 make sure your getting for the data and not WiFi only. Get them old drivers out of there first.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I tried this but same problem - no partition table so unable write anything to the device, thanks...
don, did you ever solve this?
I am having a similar problem but cannot unlock the device.
i have the same problem ....i just usedf flo-ebb clamours repartition and it wiped out all my partions i can only access fast boot but cant install anything as it says " no such partition "
Is your bootloader unlocked? If so, you should be able to flash the factory image in fastboot.
If not, you should be able to sideload the OTA in recovery.
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