Gear live watch tool V3 use restore and relock and factory reset
after that not use bluetooth but Gear live watch tool V2 use try unauthorized open
not use bluetooth.... help :crying:
I'm in the same boat, I currently have no solution.
To be honest, I dont think the outlook is good. Unless we can find a way to authorize a connected device some other way than bluetooth, I think the devices may be soft bricked.
I tried using a USB OTG cable to connect the watch to handset via cables, but no luck. Running adb commands from the device itself (via terminal) was also a no go.
It maybe we need a JTAG interface to push a fixed firmware to the device, but I'm giving up before that....
Still not fixed, but I can get the watch into download/odin mode as follows:
http://forum.xda-developers.com/gear-live/help/download-fastboot-debug-mode-guide-t2839323
But what I can't do, is get odin to flash a valid tar to the watch. I've only tried 'tar-Tool_Odin3-v3.07_by_mkh.mourad' to make tars of various system images I've downloaded, each one comes up with the following error on the device: 'Unsupport dev_type'
I now feel the watch can be rescued if we have a valid system and boot tar.. but I'm too tired to try anything else tonight.
Woops
Same thing happened to me after I flashed all stock. Seiously, wtf?
So far there's no way to fix this? And also, why does Bluetooth turn off?
I have twrp installed also, but it didn't see an option to turn on bluetooth
It can be rescued, it's just complicated, here's the outline what I did:
Used factory mode to flash twrp (had to package the twrp as a tar image first)
Pulled the /system/misc/adb/adb_keys file from my rooted handset to my computer. This handset has been authorized for debugging on my computer
Used twrp and it's adb support to push the adb file from my handset to the watch. Reset the owner, group, and permissions on the new replacement adb_keys file on the watch.
Rebooted the watch into wear, connected it to PC, confirmed that the computer now sees it as authorized in the adb devices list
Used adb to reboot it to fastboot mode, flashed version 2 of the stock images of the rom that caused this mess, rebooted, connected via Bluetooth, let system updates work their magic
Sorry for the brief description, on mobile
Hey thanks man I'll try it out, updating coming
Sent from my Galaxy Note 4 via XDA app
Wait a second, couldn't you have just held the button on the watch down as it's booting up and swiped top left to down right? That puts it in fastboot. I've been able to flash system images, but I don't have version 2...
Download link?
Sent from my Galaxy Note 4 via XDA app
Fastboot only works from adb autorized computers, I'd done a factory reset, which meant my computer was no longer authorized. And without bluetooth, I had no way of re-authorizing my pc.
But you raise a good point! If anyone else in this situation already has ADB authorized, all they need to do is the fastboot restart and flashing. Heres the link I used for v2:
http://forum.xda-developers.com/showpost.php?p=58022711&postcount=56
Thanks so much, I'm trying it now. Strangely enough, I'm not authorized and I can flash.
Sent from my Galaxy Note 4 via XDA app
---------- Post added at 02:40 AM ---------- Previous post was at 02:03 AM ----------
Edit: device is working and I'm updating to the latest aw version! Awesome.
But something weird is I was using the restore tool v3 and it didn't work. I did the exact same thing with v2 and it worked. Strange.
Sent from my Galaxy Note 4 via XDA app
Anyone know why builds older than KNX01Q don't have bluetooth support for my watch? My watch came with either 4.4W.2 or 5.0.1. Did Samsung change the bluetooth module on their newer batches?
Related
Hi all, I have scoured the web for similar issues and can't find any answers
-Captivate I897 running 2.1 formerly mounted to my MAC just fine, rooted using Galaxy-S one click root. Root was successful, mostly just removed bloatware, etc.. but alas my phone is no longer recognized by the computer, although the phone recognizes that it is connected, when I click "mount" nothing happens on the computer's end.
-Appears to be a problem with the phone, I have tried Win7 w/ Kies mini and installed/reinstalled drivers, dev mode, etc...nada. And here's the kicker - these machines will recognize and mount my GF's unrooted Vibrant just fine.
-I have a separate micro SD card reader that can read the SD card out of the phone that way.
-So, I am hoping for some help to either
1 - fix the computer recognition issue, or
2- find steps to manually update to 2.2 or unroot, etc, any ideas that will get me running 2.2 and hopefully mount to Mac or PC, using files manually loaded to the SD and installed during recovery mode, this looks like flashing, would Andromeda or Cognition fix the connectivity issue?
Thanks in advance!!
If you're rooted and can get into download mode (power off+2 volume buttons+plug usb in) then you can use this link ----> http://www.megaupload.com/?d=QL6NX702 to flash stock 2.2 firmware. Note: This WILL break your root. Here's the thread on Odin One Click as well---->http://forum.xda-developers.com/showthread.php?t=731989. You probably want to read the information there before flashing to 2.2.
Good Luck!
Thanks for the suggestion, I've tried multiple drivers, but since my PC doesnt recognize my phone, both Odin or Superoneclick dont recognize my phone also.
I was able to manually unroot by copying the One Click Root Update.zip to my phone via Wifi File-sharing app. Unroot was successful, but still no connection to PC or Mac.
I'm stuck for now, It appears that any type of flashing requires a PC connection, unless there is some way to flash completely with Wifi-copied files and using the 'reinstall packages' option?
Well, if you have a dropbox, you could drag and drop a rom (say cognition) onto your phone's dropbox. Then you'd need to find a CWM recovery (make sure it's not 3.0) update.zip and reinstall packages. This will give you CWM recovery, from which you could install Cognition from your dropbox. No guarantees it will work, but it's worth a shot.
Can't help on the Mac and I only have a dim memory of 2.1, but what are your setting under Settings/Applications for USB settings and Development? Do you have USB debugging checked (on)? Do you have the Development settings set to something weird like Kies update?
My recommendation is to put USB debugging on (checked). In that case I think the USB settings choice is disabled and therefore ignored. Then when you connect to the computer you will get a message in the notification bar on your phone saying something like "select to copy files to/from the computer". Click that, then click the mount button. You should then be able to see the extra drives on your computer by looking under My Computer or whatever (on a PC). On mine they are F and G, no special indications that they are drives on an attached phone. I also do get an automatic pop-up for the new drives, like when you insert a USB stick, but I imagine that setting could be disabled so look for the drives manually.
If you can get a com port try to do a master clear with the phone plugged in and on the entire time, then do various methods of getting into download mode if you got a com port when the phone booted up, future references I would use Odin to flash speedmod kernel to get cwm and then flash a rom or leave it as is, when I first started rooting I used the same software and got the same problem
Try installing all the drivers beforehand just to make sure
Sent from my I897 using XDA App
do u have the drivers installed?
Mr.AdAbsurdum said:
If you can get a com port try to do a master clear with the phone plugged in and on the entire time, then do various methods of getting into download mode if you got a com port when the phone booted up, future references I would use Odin to flash speedmod kernel to get cwm and then flash a rom or leave it as is, when I first started rooting I used the same software and got the same problem
Try installing all the drivers beforehand just to make sure
Click to expand...
Click to collapse
+1
My wife's phone has the exact same issue as OP. Suggestions like above are useless unfortunately as the phone does not recognize that it is connected to a computer. Instead it acts as though it is connected to a charger. The oddest thing is that if I plug it in to a computer while the phone is turned off, the phone will turn on! However, still no recognition that it is connected to a PC.
Initially when I connected the phone the first time, Win7 said driver failed to install. Then my working cappy would not connect to Win7. I had to uninstall and reinstall the drivers and restart. My working cappy connected as it should, but my wife's phone from that point refused to recognize anything but charging.
Attempts to fix Via external SD: (1) I transferred Continuum 4.1 and reinstalled. Still not recognized. (2) Transferred my recovery images from January for stock, but just became stuck on boot screen for Continuum. I am uneasy about transferring the update-recovery.zip and download folder from original backup as I do not know whether it will screw up attempts to re-enter recovery if it does not work. (3) Attempted download mode, but only works via CWM 2 (not extended menu or three button or by inserting battery with odin up trick). Even when in DL mode odin does not recognize the COM port. (4) Attempted different orders for connecting to Odin in DL mode. By orders I mean rearranging the order I connect (i.e. open odin then connect cable then go to DL). (5) transferred andromeda3 and reinstalled, still same issue.
So, I am left thinking a hardware failure occurred at some point, so I will need to open it up and check connectors to solder it possibly.
Possible non-hardware solution is to restore to stock somehow WITHOUT Odin via CWM. Anyone know if this is possible or have a link to a flashable zip?
Thanks!
edit: I am on Win7 and always made sure USB debugging was checked. Also I tried to connect via One-Click Root for the heck of it and kies mini. No luck.
flashed without a cable
Thanks for the tip jomeister 15, I was able to flash new roms dropped over wifi with CWM recovery. This got me onto 2.2 which was the main purpose of this whole adventure. I just loaded Andromeda3 and it's pretty darn impressive.
My PC and Mac still do not recognise my phone, I troubleshot extensively like Snowake and nothing is recognized. I'm convinced its a hardware issue but who cares with wireless flashing and file transfer.
snowake said:
+1
My wife's phone has the exact same issue as OP. Suggestions like above are useless unfortunately as the phone does not recognize that it is connected to a computer. Instead it acts as though it is connected to a charger. The oddest thing is that if I plug it in to a computer while the phone is turned off, the phone will turn on! However, still no recognition that it is connected to a PC.
Initially when I connected the phone the first time, Win7 said driver failed to install. Then my working cappy would not connect to Win7. I had to uninstall and reinstall the drivers and restart. My working cappy connected as it should, but my wife's phone from that point refused to recognize anything but charging.
Attempts to fix Via external SD: (1) I transferred Continuum 4.1 and reinstalled. Still not recognized. (2) Transferred my recovery images from January for stock, but just became stuck on boot screen for Continuum. I am uneasy about transferring the update-recovery.zip and download folder from original backup as I do not know whether it will screw up attempts to re-enter recovery if it does not work. (3) Attempted download mode, but only works via CWM 2 (not extended menu or three button or by inserting battery with odin up trick). Even when in DL mode odin does not recognize the COM port. (4) Attempted different orders for connecting to Odin in DL mode. By orders I mean rearranging the order I connect (i.e. open odin then connect cable then go to DL). (5) transferred andromeda3 and reinstalled, still same issue.
So, I am left thinking a hardware failure occurred at some point, so I will need to open it up and check connectors to solder it possibly.
Possible non-hardware solution is to restore to stock somehow WITHOUT Odin via CWM. Anyone know if this is possible or have a link to a flashable zip?
Thanks!
edit: I am on Win7 and always made sure USB debugging was checked. Also I tried to connect via One-Click Root for the heck of it and kies mini. No luck.
Click to expand...
Click to collapse
You could try to send a ROM, kernel, and update.zip(CWM flash) and attempt to get another ROM over it. Format the system, wipe dalvik, I don't think its a hardware issue, I had the same problem first time I tried using 1 click rooting, I just waited patiently and got a com port after about two days, so that just leads me to believe some configuration file was corrupted during flash to stock, possibly flashing a ROM or reflashing the ROM you're on with a complete wipe of the system and user data and whatnot, or possibly just doing a backup up from cwm and immediately restore it, if its charging I highly doubt its hardware
Sent from my I897 using XDA App
please help me anyone.my flex after install rom hardbricked.it boot only in download mode and now its unrooted.no recovery menu.but i cant back to stock with usb debuging off.not conecting with my phone in kdz installation.any solution any idea?my flex is really dead
tomtsigg said:
please help me anyone.my flex after install rom hardbricked.it boot only in download mode and now its unrooted.no recovery menu.but i cant back to stock with usb debuging off.not conecting with my phone in kdz installation.any solution any idea?my flex is really dead
Click to expand...
Click to collapse
Regardless if you have USB debugging on or off if you plug up to your PC in download mode you can use the LG PC SUITE software that comes on your phone, or download it from lg, to revive your phone.
You'll need your PC connected to the internet for this
Just put in download mode
Plug into PC
Open pc suite
At the top click mobile devices tab
In drop down click "restore upgrade error"
If it doesn't recognize your phone you will need your serial number and your device model number I.e D959, D950, D955, D958, etc.
Sit back and relax this takes about 10 mins
This is the only method I use now to restore my device. Works like a charm for me.
when the phone is softbricked and usb debugging is off you cant install all drivers my friend.and phone no connected with anything.thanks for your intresting
mattwheat said:
Regardless if you have USB debugging on or off if you plug up to your PC in download mode you can use the LG PC SUITE software that comes on your phone, or download it from lg, to revive your phone.
You'll need your PC connected to the internet for this
Just put in download mode
Plug into PC
Open pc suite
At the top click mobile devices tab
In drop down click "restore upgrade error"
If it doesn't recognize your phone you will need your serial number and your device model number I.e D959, D950, D955, D958, etc.
Sit back and relax this takes about 10 mins
This is the only method I use now to restore my device. Works like a charm for me.
Click to expand...
Click to collapse
KDZ is over 1.5GB. How it takes 10 minutes?
Sent from my LG G Flex F340K on LTE network, Stock KitKat 4.4.2 Rooted
using XDA mobile app
Once it downloads the kdz it only takes 10 mins.
mattwheat said:
Once it downloads the kdz it only takes 10 mins.
Click to expand...
Click to collapse
Is there an option in LG suite to manually place already downloaded KDZ in the specific folder.
So it wont downloading it..
Sent from my LG G Flex F340K on LTE network, Stock KitKat 4.4.2 Rooted
using XDA mobile app
When phone is hard bricked it wont boot. USB debug does work only when system is up and running.
Sent from my LG-D955 using XDA Free mobile app
Murshad007 said:
Is there an option in LG suite to manually place already downloaded KDZ in the specific folder.
So it wont downloading it..
Sent from my LG G Flex F340K on LTE network, Stock KitKat 4.4.2 Rooted
using XDA mobile app
Click to expand...
Click to collapse
Yes. There is a folder on your c:\program data\lg ....something or other folder. go into it and into mobile phone folder I think its called. I'm not in front of my PC right now. But you'll find the folder you need in there. Just put the stock .kdz file in there. It must be the same version or newer than you're on. Or was on when it bricked.
I've even actually pulled the .kdz files from there after I used PC suite the first couple of times. Used them in the lg flash tool.
---------- Post added at 10:47 PM ---------- Previous post was at 10:39 PM ----------
robdevil said:
When phone is hard bricked it wont boot. USB debug does work only when system is up and running.
Sent from my LG-D955 using XDA Free mobile app
Click to expand...
Click to collapse
I've noticed, by accident, when I did the factory reset method \ steps to get into twrp, but for some reason twrp wasn't installed and it actually reset my phone.... And caused it to boot loop due to what ever i did to FUBAR it. Factory reset defaults USB debugging back to off but when in download mode it didn't stop PC suite from "restoring upgrade errors" and flashing my flex back to stock. I've used it so much I now make sure my PC at work has it and the .kdz on it. My laptop has it and I have a flash drive in my truck with PC suite & .kdz on it. Lmao. Yeah I get a little ballsy sometimes and try just about anything. OK a lot but I always have a way back now.
my friend try this with pc suite and it stop in 0%.not run.and my interner connection is very good.why?
I have no clue. Try different usb cable if you don't have the one the one that came with it. I've noticed my flex and nexus 7 don't like some cheaper no name brand cables when transferring files or using adb. They seem to be fine with just charging. I use mostly my usb cable that came with my moto razr hd maxx. Only cuz it stays connected in the micro end better. And I have no clue what happened to the original.
Also make sure you have the latest LG drivers installed.
Sometimes to get the old "offline method" to work I would have to make sure no Samsung drivers were installed or Motorola drivers, Kies, or moto device manager. If any were I would have to uninstall them and the LG drivers. Restart Windows. And re install the latest LG drivers.
So not sure what exactly did the trick but I did all of it just to make sure and something helped. Try that. Don't plug in your flex till after LG drivers are installed and you have restarted Windows. I don't know but seems like what ever sequence or install or uninstall of drivers I've done now works all the time. Before we got bump I would go from 4.2.2 to 4.4.2 a couple times a week just to fool around a few days till something I modified or themed would bootloop me and I would get passed and go back to 4.2.2 and swear I'm not leaving JB till we have a custom recovery on KK. But my A.D.D. would get the better of me and I ,..... oh yeah I gotta run get some,.... oh never mind I'll .... huh oh yeah my A.D.D. it causing crack flashing syndrome. Lmao
I am on F340K Rooted Stock recovery Kitkat 4.4.2 V20D.
after changing my build.prop I forgot to set permissions.
Now I am unable to fix permissions through adb... although I succesfully Pushed the Original backup file from my PC..
I have two backups of Build.prop in my phone also.. One in system directory with the name of Build.prop.bak and 2nd is external sd card.
please advise me what to do?. I can access phone though Volume+Power = LG service Manaual (which is shown in ADB as Recovery device)
whereas Original Stock recovery Volume down+Power have an Android Logo with Red Triangle...
Is there a way I can install/ Push Some custome recovery Like Freedom Flex Bumped cwm or twrp to my phone? Fixing permissions through ADB Operation not Permitted or Permission denied error
Hi,
Am a novice when it comes to rooting, unlocking android devices. So please excuse my ignorance and my long-winded style of writing. I want the expert users to educate me on this issue and so I don't want to miss any trivial (or not so trivial) information.
1) So, I got Samsung gear live from ebay. It came with a sprat-userdebug 5.0.1. After googling I found out that it's a user/refurb build and can't be updated to 5.1.1
2) Thanks to rootjunky! I used Gear live restore tool V3 and unlocked the bootloader (option 2). Faced few issues in getting the driver. However, fixed everything and unlocked it. Flast TWRPd it (option 8). Flashed recovery (option 4) and bootimage (option 5). Then I sideloaded stock image from 4.4W.2 (using boot.img and system.img). That was the version I found after googling.
3) Then I tried to update it via OTA download. Download completed and it went back to recovery mode and did't apply the download. There was an error message that said something like "Unable to verify the download"
4) Tried multiple times and no luck with that
5) Then tried to sideload new version 5.1.1 LCA43 from xda wiki page. However, when my device went to recovery mode, my pc lost the connection and i wasn't able to sideload (received - device "null" not found" - error from adb command)
6) Until this point I was able to pair my device with my samsung S5 phone and only problem was not able to install the update
7) Then I reset my watch to factory setting, restarted multiple times, went to recovery mode to boot as a new device etc. No luck
8) Then I did something I shouldn't have done (or I think I shouldn't have done). Used option 7 root gear live. When the system went to SH mode, I panicked and closed the cmd prompt and hard reset the device by holding power button
9) After this step, I was not able to pair my device with my phone. Now the version says 4.4W.1 - KGW42N
10) Tried resetting my device, restarted it, used recovery mode to restart it, revoked all debug access, deleted adbkey from my PC, uninstalled android SDK, all drivers, etc. Reinstalled it again with no help.
11)Suddenly android wear in my phone sees my wifirouter as a device (strange)
11) When I plug in the device to my Pc, I could see it in my device manager. When I use recovery tool it says unregistered device and asking me to register it via my phone. Where as am not able to pair it with my phone. Tried to pair it with a new phone (moto e) and no help either
12)Somewhere read that disabling wifi in the phone before pairing works. Tried that and no luck
So here am with a bricked device that stays in the screen where it says "install android wear in your phone" and detects nothing else. Am able to go to bootloader mode, recovery mode from the device. However when it's in recovery mode, my PC doesn't detect it. Even the recovery tool says unregistered device.
Please help in unbricking this device and thank you for reading thru the whole problem. Any help would be much appreciated!
Use Gear live restore tool v2. Lots of known issues with v3
Thanks for the reply. I will try this. However, how will I make my device discoverable? Now, none of my phones detect my device.
So I guess I will get "Unauthorized Device" error when I use recovery tool. Could you please let me know if there's other way around? Or am i missing something?
I've never used it
Pretty sure all the info you need is in the thread
http://forum.xda-developers.com/gear-live/development/utility-gear-live-watch-tool-t2846696
No luck. Tried V2. Tool doesn't recognize my watch. It says 'Device Unauthorized. Please check the confirmation dialog on your device'. My device is stuck in 'Install Android wear on your phone' screen.
unbricked using v2 of the tool. Now trying to update the os version. Will see if I can get lucky this time. Thanks for the help!
All is good now. Now my gear live is running on 5.1.1 with latest updates.
Good work
Please can you tell what exactly you done, as I'm on the same root.. and I'm using win 10... but without any luck so far..
darwchprish said:
Please can you tell what exactly you done, as I'm on the same root.. and I'm using win 10... but without any luck so far..
Click to expand...
Click to collapse
Simple procedure.
Just download v2 of this tool
Make sure to install USB drivers
Unlock bootloader - option 2
Then use option 6 to flash it. Then you'll get new OTA updates.
Refer rootjunky video - https://www.youtube.com/watch?v=x7oRjESQh_o
I'm not able to pair my device with my phone. Now the version says 4.4W.1 - KGW42N,
and ... I tried V2 and V3. Tool but doesn't recognize my watch. It says 'Device Unauthorized. My device is stuck in 'Install Android wear on your phone' screen.
darwchprish said:
I'm not able to pair my device with my phone. Now the version says 4.4W.1 - KGW42N,
and ... I tried V2 and V3. Tool but doesn't recognize my watch. It says 'Device Unauthorized. My device is stuck in 'Install Android wear on your phone' screen.
Click to expand...
Click to collapse
Follow this procedure.
1)Make sure all drivers are installed properly in your PC
2) Make sure when you connect your device to your PC, it's discovered as unauthorized device. It's ok
3) Long press power button in the device and swipe from top left to botom right corner when you see samsung gear live logo
4)This will get the device to bootloader mode
5)Now connect the device to your PC and run V2 of the tool. Your device will be discovered in fastboot mode
6)Now select option 6 to flash the device to stock. It'll flash it
7) Now swipe down to highlight start and swipe from right to left to start. If it goes to Raw dump code = 6. do a hard restart by long pressing power button. You'll get back your device in original setting.
Check rootjunky youtube video to get the live demo of this procedure.
noviceinandroid said:
No luck. Tried V2. Tool doesn't recognize my watch. It says 'Device Unauthorized. Please check the confirmation dialog on your device'. My device is stuck in 'Install Android wear on your phone' screen.
Click to expand...
Click to collapse
How did you get past this? I'm stuck here now too.
-- update after trying that procedure again, it worked to get to fastboot mode. Now I'm doing that 'option 6' to flash it.
mike061215 said:
How did you get past this? I'm stuck here now too.
-- update after trying that procedure again, it worked to get to fastboot mode. Now I'm doing that 'option 6' to flash it.
Click to expand...
Click to collapse
Good luck.
It worked -- and I finally got the OS to update an all that and now I finally have a functional Gear Live. Phew!
My Gear Live was bricked a lot... Computer detect device as RELINK HS-USB QDLoader 9008. Has anyone any idea how fix it?
lamik91 said:
My Gear Live was bricked a lot... Computer detect device as RELINK HS-USB QDLoader 9008. Has anyone any idea how fix it?
Click to expand...
Click to collapse
sounds like USB driver issue. Please install correct drivers and follow the steps mentioned above. It should be unbricked.
Where can i find correct drivers? Additionally my Gear Live doesn't turn on and has only black screen.
I am confused on how to use the tool. My watch is stuck at the Install Android Wear App and won't do anything short of turning it off. How do I enable developer mode \ debugging without being able to get to the watch settings. Please help! Thanks
pedalquickly said:
I am confused on how to use the tool. My watch is stuck at the Install Android Wear App and won't do anything short of turning it off. How do I enable developer mode \ debugging without being able to get to the watch settings. Please help! Thanks
Click to expand...
Click to collapse
You need to factory reset first of all. After that let connect to your wifi, the updates will download on their own. They put a new one out today. I can't go into how but if you look at the forum and search the answers are there. There's even a tool to use.
Sent from my SM-N910T3 using XDA-Developers mobile app
PLEASE NOTE the tab will not do a factory reset, when I try that it tells me it has successfully erased all the data but when I reboot it it still comes up with the same screens as described below
Got a new S2 8 inch from Sprint but couldn't remember my password so I never activated it ... it worked fine. Great. No activation fee, no monthly access charge, no running up excess minutes accidently.
Truth is all I ever wanted was a pure WiFi tab to replace a Nexus 9. I just bought from Sprint because they were having a sale. Without activation I had exactly the tablet I wanted.
Than I got greedy ... decided to streamline performance by tossing out all the superfluous phone apps and system stuff ... this seemed to work well to ... or at least it did before I rebooted the phone. Now I get a black screen with a flashing red message: Kernel is not SE Android enforcing. Custom binary blocked by FHP block.
All this is Greek to me, but that aside when I try to boot up I get one of two options depending on what hard key compos I hold. One is an endless download loop, the other is the standard Android mini recovery boot page. Of all the options, the seemingly easiest delete cache and restore default system doesn't work. The other potentially useful items .... update from file, update via download, etc. require an ADB connection to work. I have tried to establish an ADB connection using many different cables on both a Win 19 and a Win 7 PC ... in each case I get the dread "wouldn't open Code 10) message .... I have tried it with specific adb drivers and generic ones ... the results are always the same.
A fw other tips, the Android System Recovery LMY47x.T817PVPS2A0L1 screen says:. in yellow at the bottom of the screen, dm-verification failed ... update from ADB blocked and gives similar messages under"apply update from external storage, and and apply update from cache
Meanwhile, back at the downloading loop page we are told:
ODEN MODE
DOWNLOAD SPEED : FAST
PRODUCT NAME SM T817P
CURRENT BINARY: SAMSUNG OFFICIAL
FAP LOCK: ON
Secure Download: Enabled
Knox Warranty Void: ZERO
HP: SWHEV: B:2 K:8 S:0
So please, please, please does anyone have any idea what's going on here and how I can fix it ... would it, for example., be possible to reinstall the ROM and OS via a USB stick and OTR cable ... if so how would you do it .......
Thank you, thank you, thank you
Forgot to mention Samsung G6 phone connects to PC correctly through same cable ... Device Manager shows Code 10 message when nothing Android is connected to a USB port or when the S2 is connected does not show Code 10 and works perfectly when G6 is connected .... would it be possible to boot and restore the tablet via a USB stick and OTR cable? Thanks again
Hi, Guys, girls, men and women ... I'm not to proud to beg ... one of you must have an answer to this puzzle ... if you do and it works I'll use the my G6 to send you a video of me pushing a peanut around with my nose. Is there really no way to bot or restore this thing via a USB flash drive?
this seems like it could definitely help you
If you can boot into download mode (press volume down and home button as you power on the tablet. Continue holding the buttons down until you get the download warning message).
If successful, download the latest version of Odin to your computer. Also go to sammobile.com and search for your device in the firmware section. Download the appropriate firmware to your computer. You will also need the Samsung drivers for your device on your computer as well.
You should be able to flash it back to stock with Odin. There several threads on xda that give instructions on how to use Odin.
Introduction
This tool is for returning the Kindle Fire back to stock automatically. This is for Windows ONLY. If you can spare about 1 GB on your hard drive, you're good to go.
Code:
Disclaimer:
By using this tool, you accept that you're taking full responsibility if anything bad happens.
Blame any of us (me, XDA Devs, etc) and I'll ask you to read the licence agreement slowly &
carefully.
You have been warned.
Requirements
A fastboot/factory cable (They can go for as cheap as $2)
A Kindle Fire 2
ADB and Fastboot drivers
A PC running Windows
Time
Download
Installer
Google Drive: Installer
MediaFire: Installer
Zip & & 7z files
MEGA
ZIP format
7z format
Google Drive
7z format
Rootjunky's DL Server (thanks Tomsgt.)
ZIP format
Android File Host
ZIP format
NOTICE: I am not developing this anymore. If any download links go down, I will not be able to help. Sorry. ¯\_(ツ)_/¯
Does this work? Has anyone tried it?
Please help!!! MODS PLEASE READ !!!!
Ok Ive tried searching and Ive tried everything on this site, I have a Kindle Gen 2 I can get into Fastboot but everything else was deleted off the Kindle, EVERYTHING !!! I just want to restore it for my daughter to use in the car Windows 10 does not reconize it but it shows up in device manager as OTTER2 with no drivers when i plug it in with fastboot cable. anyone who can point me in a direction please help.
Bwangster12 said:
Does this work? Has anyone tried it?
Click to expand...
Click to collapse
I know I'm over a year late in this reply, but I accidentally bricked my Kindle with the red triangle screen, but didn't have a fastboot cable, so I ordered a cheap one on Amazon which arrived an hour ago. Immediately I took it to my computer, plugged in my powered off Kindle, and it went straight into fastboot mode. I opened disaster recovery from this thread ran it with the fastboot cable plugged in, swapped for a regular cable on the step it tells you to, did the factory reset it told me to do, and sure enough my KF2 is back in the state it was fresh out of the box. I'm mostly just going to be using it for my e-books and audible purchases, but it's nice to have it working again. Going to try installing the prime video app on it since on stock it will try to use silk+flash for prime video and I'm not sure that will even work anymore. If it does, cool, but if not I should be able to install the apk for prime video as a user app without having to dig up old root methods by using the internet archive on dead links.
---------- Post added at 05:42 PM ---------- Previous post was at 05:35 PM ----------
Panettaone said:
Ok Ive tried searching and Ive tried everything on this site, I have a Kindle Gen 2 I can get into Fastboot but everything else was deleted off the Kindle, EVERYTHING !!! I just want to restore it for my daughter to use in the car Windows 10 does not reconize it but it shows up in device manager as OTTER2 with no drivers when i plug it in with fastboot cable. anyone who can point me in a direction please help.
Click to expand...
Click to collapse
Don't know what to tell you, my dude. Worked fine with Windows 10 for me with a fastboot cable. Might have to manually download the drivers if you haven't already, but my computer straight up recognized it.
Do you have any USB2.0 ports available? I find that with older devices, 2.0 is the way to go and 3.x tends to either not detect the device or causes errors during critical data transfers.
This tool, when you get your Kindle detected, will fix exactly your problem. I'd say try right clicking the .bat file, go to properties, then in the compatibility tab make sure it's running as administrator. That insures the fastboot and adb processes will have the proper permissions to write to the Kindle. Might even work now even with it coming up as OTTER2.
Panettaone said:
Ok Ive tried searching and Ive tried everything on this site, I have a Kindle Gen 2 I can get into Fastboot but everything else was deleted off the Kindle, EVERYTHING !!! I just want to restore it for my daughter to use in the car Windows 10 does not reconize it but it shows up in device manager as OTTER2 with no drivers when i plug it in with fastboot cable. anyone who can point me in a direction please help.
Click to expand...
Click to collapse
Had this problem just now actually! I went and grabbed the official driver files from amazon and installed them (can't link since I'm a new user but you'll find it if you search "Kindle Fire ADB Drivers").
Then I clicked on the device otter2-prod4 in device manager and manually assigned it to Amazon ADB Device and that solved the issue for me.
It's now discoverable via fastboot and I'm running this recovery script right now!