After not using my pace for a few months I decided to start wearing it again, but I'm having a problem, I can't install any apps.
In the time I had not been using the Pace, I uninstalled the Amazfit app, so I needed to factory reset the Pace to get it paired again.
After the reset I can no longer install apks. I have tried apk installer and just directly using ADB but both fail.
Whenever I try to install an app, I hear the windows USB disconnect/reconnect sounds and the install fails.
I have tried, rebooting the watch, factory resetting the watch again, rebooting the PC, reinstalling ADB drivers (several times) and so far none of it has helped
Below is the output from ADB. If anyone can tell me how to fix this I'd really appreciated it.
__________________________________________________________
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Minimal-ADB-and-Fastboot>adb devices
List of devices attached
adb server version (40) doesn't match this client (35); killing...
* daemon started successfully *
b3291104 device
C:\Minimal-ADB-and-Fastboot>adb install rl.apk
adb: error: failed to copy 'rl.apk' to '/data/local/tmp/rl.apk': couldn't read f
rom device
- waiting for device -
C:\Minimal-ADB-and-Fastboot>
__________________________________________________________
Just bumping this since I am still having this issue and am hoping someone has some idea how to fix it.
I have managed to install some apps, but most won't work, not sure if it is random or something to do with the apps themselves. However they are all apps that I have used in the past on my Pace so I'm really not sure whats going on.
Whenever I try to install an app ADB seems to disconnect then reconnect and the install fails.
Any help with this would be great.
I recommend you doing a factory reset in fastboot if you already have unlocked bootloader (sync all data before):
Code:
adb shell reboot bootloader
fastboot erase cache
fastboot erase data
fastboot reboot
If your bootloader is locked, just do a reset from the watch settings.
Saratoga79 said:
I recommend you doing a factory reset in fastboot if you already have unlocked bootloader (sync all data before):
Code:
adb shell reboot bootloader
fastboot erase cache
fastboot erase data
fastboot reboot
If your bootloader is locked, just do a reset from the watch settings.
Click to expand...
Click to collapse
I already tired a couple of factory resets but unfortunately it didn't help. I have not unlock or modified the watch so I'm not sure what else I can do.
Is there any kind of official tool to reflash the stock ROM on a locked device?
Related
So, I was messing some things up in safestrap and I decided I want to do a fresh start on my phone. So I went to the wipe section and wiped everything.. Now as I can tell, I have no /system folder, no OS, nothing. I can access bootloader. After intense reading and searching, I managed to connect my phone via adb, adb devices command shows the ID of my phone in a sideload state. Sideloading a rom never worked, tried many of them, at best I got an error about getprop file missing - tried to modify the updater-script using an editor after instructions but still nothing. My main issue is that while adb works fine, drivers are 100% fine, upon entering phone into fastboot mode, it disconnects and there is nowhere to be found under device manager. If I could get it to work in fastboot I could then use RSD lite to flash a stock rom. Also, the only command that works from adb is the # adb sideload filename, anything else returns error:closed. Even tried #adb usb #adb remount and so on. Is my phone a garbage at this point?
forgot to say also, tried to connect via fastboot under windows 7 sp1 / xp sp3 / ubuntu 14.04 .
bump
bump..
So recently, I downgraded to 13.3.1.0, and installed Safestrap (not the one for later versions). However, after restarting and adding a ROM slot, it wouldn't let me do anything with stock.
I restored stock, but still nothing.
The odd thing is, whenever I press the power button, it will still make noise.
I can access fastboot, Safestrap, and the default recovery.
What do I do?
Bump, need help ASAP
Alex311360 said:
So recently, I downgraded to 13.3.1.0, and installed Safestrap (not the one for later versions). However, after restarting and adding a ROM slot, it wouldn't let me do anything with stock.
I restored stock, but still nothing.
The odd thing is, whenever I press the power button, it will still make noise.
I can access fastboot, Safestrap, and the default recovery.
What do I do?
Click to expand...
Click to collapse
If you can enter safestrap recovery, check if you can establish adb access:
so enter safestrap and connect kindle to your pc or laptop. Then start cmd window or terminal if you using linux, and try:
adb devices
it should return:
list of devices attached
xxxxxxxxx recovery
if you can achieve that your kindle in safestrap recovery is recognized by win/linux, you can try this:
1. Download this 13.3.1.0 (Kindle HDX 7") update - pure amazon FireOS so OTA updates enabled - do not connect to wifi/register your kindle if you want root and use of custom recovery after flashing this
A. Now, since I am not expert for adb installing pushing repairing etc., read this thread [HOWTO] Unbrick your device
B. If that for whatever reason wont work, you can try sideload update-kindle-13.3.1.0_user_310079820.bin (rename .bin to .zip before sideloading) through safestrap recovery, but because Safestrap is only TWRP "based", I cant guarantee that this will work either (it should, but this is one way ticket, your working safestrap recovery will be destroyed in the process of update and if things dont go as they should, your kindle is bricked for good):
0. connect kindle to pc/laptop
1. enter Safestrap, tap Advanced -> ADB Sideload -> Swipe slider to start Sideload
2. on pc/laptop open cmd/terminal, type adb devices, you should see:
List of devices attached
XXXXXXXXXXXXXXXX sideload
3. type adb sideload update-kindle-13.3.1.0_user_310079820.zip
4. You will see a progress bar in the command prompt indicating that the Zip file is being copied to the device. Once the file is transferred, the Zip is automatically installed on your device.
OK fingers crossed, I hope something will work, but things can go wrong, so it is up to you if you try this or not ...
On a scale of 1 to worse, what happens if ADB sideload refuses to work? It just freezes at starting and does nothing afterwards, and I have to cancel.
Alex311360 said:
On a scale of 1 to worse, what happens if ADB sideload refuses to work? It just freezes at starting and does nothing afterwards, and I have to cancel.
Click to expand...
Click to collapse
You can also try to unlock your bootloader (since you have compatible FW) and proceed to flash cuber signed recovery (TWRP 2.8.5.0) through fastboot and then from TWRP you can do necessary steps to recover your kindle quite easily - if you are familiar with TWRP flashing...
Regarding sideloading I honestly dont know how it will react - never try it - it was developed exactly for quick system recovery, but you must be flashing 100% working rom ...
Personaly I would go for bootloader unlock and then flash TWRP 2.8.5.0 from which sideloading feature (If you want use that) must working... :good:
Do you require a factory fastboot cable for that?
Alex311360 said:
Do you require a factory fastboot cable for that?
Click to expand...
Click to collapse
No, standart USB cable is enough.
Can you give me a link on how to do this? I know I'm sounding very noobish, but I'm a tad new to this.
Alex311360 said:
Can you give me a link on how to do this? I know I'm sounding very noobish, but I'm a tad new to this.
Click to expand...
Click to collapse
Sure, here is original post from dpeddi.
... and here is how to for windows ... :good:
Hey, sorry it's taken me so long to reply. Was busy with school.
For some reason it won't connect to the device in fastboot, it just says "waiting for device", even the Kindle says "Ready." and does nothing.
What do I do?
Alex311360 said:
Hey, sorry it's taken me so long to reply. Was busy with school.
For some reason it won't connect to the device in fastboot, it just says "waiting for device", even the Kindle says "Ready." and does nothing.
What do I do?
Click to expand...
Click to collapse
If your OS is Windows 7, you can try install these drivers and then try again.
jeryll said:
If your OS is Windows 7, you can try install these drivers and then try again.
Click to expand...
Click to collapse
Still no dice. Doing fastboot devices or adb devices brings up nothing.
Please note I have done the following things:
- did a kindle fire system restore with safestrap restore still installed
- adb sideload doesn't work in safestrap
- fastboot drivers used installed does nothing
Still stuck.
Alex311360 said:
Still no dice. Doing fastboot devices or adb devices brings up nothing.
Please note I have done the following things:
- did a kindle fire system restore with safestrap restore still installed
- adb sideload doesn't work in safestrap
- fastboot drivers used installed does nothing
Still stuck.
Click to expand...
Click to collapse
On which FW you were before downgrading to 13.3.1.0?
Weird thing with windows and these drivers is it sometimes command fastboot -i 0x1949 devices does nothing, while actually direct commands like
fastboot -i 0x1949 getvar product
fastboot -i 0x1949 getvar version
fastboot -i 0x1949 getvar kernel
works as expected...
Anyway to restore system on your kindle you need working connection between kindle and PC/laptop, so you can use adb commands to restore your system, or after bootloader unlock, you can use fastboot commands to flash required/missing components. I have tested while in safestrap kindle is recognizable by adb devices, if you can achieve that, you can continue with how to unbrick thread I posted before.
You can also learn how to install/use Linux, where adb and fastboot device recognition/commands works 100%...
I must leave for work now ...
So, some kind of miracle happened, and I found the source of the problem.
Upon trying to update to 13.3.2.4, it reboots the phone instead of installing it. I try booting into Safestrap, and it does Open Recovery Script, causing it to boot to a black screen upon booting to the actual thing.
I don't know how to fix Open Recovery Script doing that, but all I had to do to get it back to normal was reflash the 13.3.1.0 amazon OS onto stock.
Symptoms
This is for a Nvidia Dreamtab NV08B. Due to a system change you made, or an official Nabi OTA update the tablet now no longer boots.This could be the tablet hanging/frozen/stuck from any point from when turning the tablet on up to the Dreamworks characters screen and never boots any further. You have attempted at least 2 factory reset through the stock recovery and it still does not boot.
NOTE: If your Dreamtab was recently working and you made no system changes, or system updates but is now hanging at the Dreamworks characters try this first: https://forum.xda-developers.com/nabi-2/general/guide-dreamtab-hangs-characters-t3528698
Solution
Restore the tablet to software version 1.3.12 stock condition: Unlock the bootloader to allow tablet modification. This will wipe ALL the data from the tablet. Format all ext4 partitions and check filesystem integrity. Reinstall recovery, boot, system and addon partitions. Optionally install the fsck binary that is missing on the tablet. Reinstall bootloader
Procedure
Only for Nvidia Dreamtab NV08B. Use this at your own risk, your warranty is void. You will lose all personal data on the device
To get an understand of how the device works with fastboot, ADB, and recovery read through this :http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119
You will need to install ADB and fastboot drivers yourself. I have included a copy of Nabilab drivers for 32bit and 64bit computers in the download in the driver folder. Refer to the link above to understand driver installation and booting the tablet to fastboot. This is a script driven restore of the tablet, most of these task are automated.
General flow:
-- Download the Dreamtab_NV08B_restore.zip
-- Extract the zip file to a location of your choosing on your computer.
-- Connect the Dreamtab powered off to your computer via USB cable.
-- If you want to install the driver provided in the zip do it now.
-- Open the file recover_dreamtab file
-- A command prompt opens and the script runs as below. The script has the instructions in it, the below is just a summary.
(automated = script will do it for you. User = you need to take action)
(automated) Extract the files you will need for recovery.
(user) Boot the tablet to fastboot pressing vol+ and power button. Use vol- to select fastboot protocol.
(automated) Check fastboot operational
(user) If script hangs here, user will need to check drivers)
(automated) Initiate bootloader unlocl
(user) Use vol- button to select yes, and vol+ to acknowledge
(automated) Wipes userdata and cache and unlocks bootloader
(automated) Formats data partition
(automated) Boot TWRP 3.0.0 recovery temporarily
(automated) Check data partition integrity
(automated) Format and check cache partition
(automated) Check CPU serial number for TWRP backup
(automated) Push the restore files, bootloader, and fsck patch to Nabi internal storage
(automated) Restore recovery, boot, system, and addon partition files.
(user) Prompt user to install fsck binary that the stock Nabi is missing. I recommend this. but there is a no option.
(automated) Install fsck patch if selected by user
(automated) Install 1.3.7 bootloader
(automated) Remove restore files from tablet
(automated) Reboot
Note: The boot loader is left unlocked. Sometimes you will get a google play service error during first boot.
Download
AHF Download Link: Dreamtab_NV08B_restore
___________________________________________
I'm having an issue when the script switches from fastboot to recovery. First, the TWRP 3.0 recovery.img isn't anywhere in the restore zip. So I put that in the install folder (I already had it installed on the DT but nothing was working so I tried this anyways). The ADB driver verifies and the script echos "ADB is functional. On tablet Swipe to Allow Modification." The script boots the device into TWRP just fine and I swipe past the Allow Modification screen. I press any key on the script to continue but every single task is followed by "error: device not found." I've triple checked that both the DT shows up as an ADB Interface in the Device Manager and I can use "adb devices" to see it, yet the script still returns the error. Any thoughts?
Also, how feasible would it be to simply do this by hand? I'm pretty well versed in fastboot/adb but dealing with partitions is something that I tend to shy away from for fear of bricking a device. Since I can get adb to see the device could I simply copy the commands from the script?
Alternatively, could I simply add the .win and .md5 files into the RESTORE folder myself via drag and drop and do a wipe and restore straight from TWRP?
CriticalComposer said:
I'm having an issue when the script switches from fastboot to recovery. First, the TWRP 3.0 recovery.img isn't anywhere in the restore zip. So I put that in the install folder (I already had it installed on the DT but nothing was working so I tried this anyways). The ADB driver verifies and the script echos "ADB is functional. On tablet Swipe to Allow Modification." The script boots the device into TWRP just fine and I swipe past the Allow Modification screen. I press any key on the script to continue but every single task is followed by "error: device not found." I've triple checked that both the DT shows up as an ADB Interface in the Device Manager and I can use "adb devices" to see it, yet the script still returns the error. Any thoughts?
Also, how feasible would it be to simply do this by hand? I'm pretty well versed in fastboot/adb but dealing with partitions is something that I tend to shy away from for fear of bricking a device. Since I can get adb to see the device could I simply copy the commands from the script?
Alternatively, could I simply add the .win and .md5 files into the RESTORE folder myself via drag and drop and do a wipe and restore straight from TWRP?
Click to expand...
Click to collapse
Sorry about that, I re-uploaded.
Yes you could copy the files over, or do the script by hand. Drop and drag is by far the easiest especially if you use external SD card. Part of me wants to know why the script isn't working for you though.
I just found something and I don't know if this is the issue. When TWRP is idle the device is showing up as "Google Nexus ADB Interface" and "adb devices" cannot see it. However, if I go to TWRP to initiate ADB Sideload then it shows up as "Android ADB Interface" and "adb devices" sees it no problem. I've tried changing the Google Nexus driver to the Android one but I can't seem to find it. Both the .inf from NabiLabs and the Universal Naked Drivers show up as Google Nexus ADB Interfaces.
Also, I grabbed your re-uped version and ran into a problem that I forgot I had to fix last time as well. ADB always hangs after starting the daemon. I had to use my personal adb (v32) to get it to stop hanging (your package uses adb v36). Alternatively, I found that when it hangs, I can start the v32 daemon and then go back to your script which will restart the v36 daemon and it seems to run fine...though it still doesn't see my tablet.
CriticalComposer said:
I just found something and I don't know if this is the issue. When TWRP is idle the device is showing up as "Google Nexus ADB Interface" and "adb devices" cannot see it. However, if I go to TWRP to initiate ADB Sideload then it shows up as "Android ADB Interface" and "adb devices" sees it no problem. I've tried changing the Google Nexus driver to the Android one but I can't seem to find it. Both the .inf from NabiLabs and the Universal Naked Drivers show up as Google Nexus ADB Interfaces.
Also, I grabbed your re-uped version and ran into a problem that I forgot I had to fix last time as well. ADB always hangs after starting the daemon. I had to use my personal adb (v32) to get it to stop hanging (your package uses adb v36). Alternatively, I found that when it hangs, I can start the v32 daemon and then go back to your script which will restart the v36 daemon and it seems to run fine...though it still doesn't see my tablet.
Click to expand...
Click to collapse
Go to the mount page in TWRP and disable MTP. When MTP is enabled it's really an ADB "composite device", when it's disabled it's a "single" interface.
To fix the ADB issue try adding
tools/adb kill-server
to the beginning of script.
Disabling the MTP worked like a charm. I would highly recommend adding that to the script as an echo so that others don't run into the same confusion. My tablet is up and working again. Thanks a ton for putting this script together. I would rather have had Nabi release factory images but this works just as well!
Thank you very much for the procedure.
is there any solution for Intel Version? (IN08A)
Thank You Thank You Thank You. This worked when everything else failed. Couple notes: Yes I had to Disable the MTP. No biggie. Then when I got to the Yes/No prompt to install fsck binary, I typed yes hit enter and the command prompt closed! I started over and and tried typing "No", same results. I actually tried the entire process a couple more times before I just used the TWRP to Reboot... all went well... I did see the Google Error but hit Ok and everything continued till it got to the setup page.. All in All an excellent script Thanks for your time and effort to do this.
Old thread, I know-
Thanks for this, but my nabi dreamtab 08B1 bootloader unlock doesn't work.
I installed your drivers, and the fastboot oem unlock reports:
Code:
C:\Users\me\Downloads\DTTWRPinstaller300>cd files
C:\Users\me\Downloads\DTTWRPinstaller300\files>fastboot oem unlock
...
(bootloader) Showing Options on Display.
(bootloader) Use device keys for selection.
(bootloader) erasing userdata...
(bootloader) erasing userdata done
(bootloader) erasing cache...
(bootloader) erasing cache done
(bootloader) unlocking...
FAILED (remote: ()
finished. total time: 4.916s
C:\Users\me\Downloads\DTTWRPinstaller300\files>
any ideas? I've tried this several times- this is after a factory reset, and the tablet bootloops from teh characters screen.
thanks again!
phil_socal said:
Old thread, I know-
Thanks for this, but my nabi dreamtab 08B1 bootloader unlock doesn't work.
I installed your drivers, and the fastboot oem unlock reports:
Code:
C:\Users\me\Downloads\DTTWRPinstaller300>cd files
C:\Users\me\Downloads\DTTWRPinstaller300\files>fastboot oem unlock
...
(bootloader) Showing Options on Display.
(bootloader) Use device keys for selection.
(bootloader) erasing userdata...
(bootloader) erasing userdata done
(bootloader) erasing cache...
(bootloader) erasing cache done
(bootloader) unlocking...
FAILED (remote: ()
finished. total time: 4.916s
C:\Users\me\Downloads\DTTWRPinstaller300\files>
any ideas? I've tried this several times- this is after a factory reset, and the tablet bootloops from teh characters screen.
thanks again!
Click to expand...
Click to collapse
Nothing comes to mind. The only time I have seen that failed message was on a tablet where the flash had gone bad, but the tablet wouldn't erase data and cache like it looks like yours did. Anything else plugged in, cables good? You could try the -i switch although I don't recall seeing a Dreamtab that needed it, I am mobile and cant remember. It's like fastboot -i 0x0489 oem unlock or something.
Hello, I have an Amazfit Stratos (details attached as a screenshot from AmazMod app) and I have a problem entering fastboot (I want to unlock the bootloader and start having fun with the watch )
What I've already tried:
- standard ADB mode, the watch is recognized and seen in ADB, but when I enter adb shell reboot fastboot - it just reboots back to the usual OS...
- the All In One Tool available on XDA - the same issue - watch is recognized but when I click reboot to fastboot - it just boots up normally...
- manual method described on the forum and shown on youtube - the issue is, when the screen goes dark I'm supposed to wait 4 seconds before releasing the power key - and my watch shows up the Amazfit logo after 2 seconds - the whole bootup process is different than on the video - I've been at it for 2 hours and did not manage to get it to fastboot once
- I've also tried using the AmazMod app - there's a section there that allows you to send direct commands to the watch shell - I've tried reboot fastboot and the watch also reboots back to the standard OS
- I tried the method with adb kill-server / adb start-server / adb wait-for-device and then rebooting the watch (method found on the forum as well) - no cigar.
I'm getting desperate - I wanted the stratos mostly because of the awesome job devs do making it better - now I'm left with the stock watch and to be honest I think Huawei Watch GT would be better for my needs if I'm comparing stock vs stock...
Did anyone have any similar issues?
Anyone? Getting desperate and still no solution in sight...
AmazMod widget also has a "Reboot to fastboot" option, but it is the same as the adb command, I think you are using the wrong command, the correct one is:
Code:
adb shell reboot bootloader
and not "reboot fastboot". Manually always works too, if watch turns on (you can see Amazfit logo) and button isn't broken.
Yeah I've tried both reboot fastboot and reboot bootloader with the same non result
maslosky said:
Yeah I've tried both reboot fastboot and reboot bootloader with the same non result
Click to expand...
Click to collapse
You must use exactly the same commands as I wrote, "adb reboot bootoloader" does not work.
ADB method just causes the watch to reboot regularly... Nobody is able to help?
If the adb command doesn't work for some weird reason, then the only way is doing it manually. It is very trick, but it works. You may want to flash a stock ROM first, as it is the only explanation why "adb shell reboot bootloader" does not work for you...
I do have a stock rom since I haven't been able to unlock bootloader (because I can't enter fastboot) - manual entry is not working, as I've mentioned my watch is acting differently than the watch presented in the YouTube video... I'm stuck
Did you try to facttory reset yet?
Code:
adb reboot wipe
OK so I finally managed to get the watch to fastboot mode, manual method is still not working, but after a factory reset and TOTAL removal of ALL adb drivers (total wipe of any adb/fastboot drivers from Win10) - it finally worked using the All In One Tool from the forum. This can be closed now. Thanks for all the suggestions - I'm not sure if the factory wipe helped or the Win10 drivers wipe - but it works I'm on to bigger and better things
maslosky said:
OK so I finally managed to get the watch to fastboot mode, manual method is still not working, but after a factory reset and TOTAL removal of ALL adb drivers (total wipe of any adb/fastboot drivers from Win10) - it finally worked using the All In One Tool from the forum. This can be closed now. Thanks for all the suggestions - I'm not sure if the factory wipe helped or the Win10 drivers wipe - but it works I'm on to bigger and better things
Click to expand...
Click to collapse
Can u elaborate on thr driver's removal?
I think I may have posted this initially on wrong forum here, so sorry for the repost:
Hi, I have MI7 and after wiping data (noticed at show 2% complete and just returns, saying wipe was done, so maybe that is a sign of something) and rebooting it keeps saying that there was a factory reset and I need to enter password. I keep going into MI 3 Recovery and choosing MI Connect and trying ADB but `adb devices` simply lists a sideload entry and adb shell keeps returning error:closed. So `adb shell rm /data/system/gesture.key` doesn't work as it returns `error closed`. The MI PC Console tool doesn't detect the phone.
If I type `adb reboot-bootloader` my phone shows Fastboot but no menu. Just hangs at fastboot. `fastboot devices` returns a fastboot device.
So seems like there are some signs my phone is able to be communicated with, but none of the usual commands are helping me get anywhere...
Really not sure how to totally reset this device so I can start all over again. This factory reset loop just doesn't want to go away.
Any ideas how to get this phone to behave like it is brand new, regardless how technical?
thanks,
Brian