Related
Bought 2 refurbished Gear Live watches from Best Buy and both are User Debug builds of 4.4W1, meaning no updates for me. Anyone know how to change these to stock?
segura.org said:
Bought 2 refurbished Gear Live watches from Best Buy and both are User Debug builds of 4.4W1, meaning no updates for me. Anyone know how to change these to stock?
Click to expand...
Click to collapse
I am using one of these as well right now, I tried the gear live restore tool but the image its loaded wont let me connect to my phone
So now what? I'll call Corporate tomorrow as the stores can't exchange these. I'm sure they came from Samsung as Best Buy Geek Squad shouldn't have this build.
Turns out I have a solution.
1. Make sure you have the android sdk tools installed and make sure you have the fast boot driver installed as well
2. put the gear live(s) in to fast boot mode (Hold side button untill watch restarts then swipe down from top left to bottom right)
3. Leave it in this mode and go in to cmd so you can use fast boot
Grab only this firmware from this page: stock KMV78Y from http://forum.xda-developers.com/gear...sybox-t2834620
unzip those file into the directory in the android sdk tools Platform tools folder where fastboot is and run these commands without the quotes
"fastboot flash boot boot.img"
"fastboot flash system system.img"
after the cmd window says it finished go on the watch and go to recovery and select that.
on the recovery screen you will see an android on his back swipe down from the top left corner to the bottom right corner and on the menu that shows up select "wipe data/ factory reset"
it will then format the /data and /cache folders on the watch after which the menu will show up again at this point select reboot system now and that will restart the watch
and your done you can run through upgrades at this point till the newest one
ajgamer said:
Grab only this firmware from this page: stock KMV78Y from http://forum.xda-developers.com/gear...sybox-t2834620
Click to expand...
Click to collapse
Thanks! Can you confirm the link for the right firmware, your link is DOA. Also you have done these steps and working right?
Ok, got all the steps done, and in AW, I go to System Update. It downloads the update and after it reboots to apply the update, I get:
Verifying update package. . .
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted
Tried a Reset and then back to apply System Updates with the same result. Any clues?
segura.org said:
Ok, got all the steps done, and in AW, I go to System Update. It downloads the update and after it reboots to apply the update, I get:
Verifying update package. . .
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted
Tried a Reset and then back to apply System Updates with the same result. Any clues?
Click to expand...
Click to collapse
You need to flash the right recovery..
I posted this to SD and I'll post it here as well. This is just my fix
Tipps1269 guide From SD was good and helpful. Thx..
The hardest part is getting the computer to recognize the watch in fastboot mode. I used a Windows 8 and 7 machines. I used the ADB universal driver from the below.
1. Download FILES from V3 from http://forum.xda-developers.com/gear-live/development/utility-gear-live-watch-tool-t2846696 Gear live restore, I even watched the youtube video.. Good info Thx Tomsgt
You are only useing the file for ADB/Fastboot command , Universial ADB driver and the 42Nrecovery.img
Download the Stock Firmware for this watch here https://www.androidfilehost.com/?fid=23610159112653225
Now you have all the files a to unlock, and flash boot.img, recovery.img ,and sytem.img which are all stock.
Copy all the files to one Dir and CMD to that Dir.
Put you watch in fastboot mode. You Don't even need to do anything other then take it out of the Box put in fastboot mode.
Hold the Power button on the watch and keep holding it, till it reboot.
When you see the Samsung Logo, swipe from the top Left of the screen to the bottom Right.
Now your in fastboot
Run the Four fastboot commands
fastboot oem unlock
fastboot flash boot boot.img
fastboot flash recovery 42nrecovery.img
fastboot flash system system.img
Swipe Down and reboot,
You don't need to relock, or put in Debug mode. Just connect to you phone. You don't even need to update, once you have connected it will automatically start updating.
In Short
Install ADB drivers for fastboot
Put watch in fastboot mode
Unlock recovery
Flash three file
Reboot watch
ajgamer said:
I am using one of these as well right now, I tried the gear live restore tool but the image its loaded wont let me connect to my phone
Click to expand...
Click to collapse
I was in the same situation yesturday with a best buy refurb, used V3 of the gear live restore tool and couldn't connect to the phone. I tried again with V2 of the tool instead of the current V3. The older version worked like a charm first time. Give that a try. There were a few OTA's to get to 5.0.1 but I am there now
gunkle said:
I was in the same situation yesturday with a best buy refurb, used V3 of the gear live restore tool and couldn't connect to the phone. I tried again with V2 of the tool instead of the current V3. The older version worked like a charm first time. Give that a try. There were a few OTA's to get to 5.0.1 but I am there now
Click to expand...
Click to collapse
Worked like a charm on my 2 BestBuy units, Thank you
V2 is at http://www.rootjunky.com/backup-file-server/
you will have to select Samsung Gear Live Watch > Script Super Tool > Samsung Gear Live Restore Tool V2 (149.1 MiB)
Milimbar said:
Worked like a charm on my 2 BestBuy units, Thank you
Click to expand...
Click to collapse
glad to help.
so random.. glad u guys realized this i guess they are making us work for our resale profit..
Does anyone have a mirror for V2? The link is no longer working.
EDIT: Heres a working link Gear Live Restore Tool V2
Was anyone able to eat the recovery tool working on a Mac? I can't get it to recognize my watch in Windows.
tpierce89 said:
Was anyone able to eat the recovery tool working on a Mac? I can't get it to recognize my watch in Windows.
Click to expand...
Click to collapse
I was wondering the same thing at first. Download the recovery tool file and unzip it for the 42Nrecovery bundled with the tool. You don't need to use the tool. I followed godgib's instructions above.
domol said:
I was wondering the same thing at first. Download the recovery tool file and unzip it for the 42Nrecovery bundled with the tool. You don't need to use the tool. I followed godgib's instructions above.
Click to expand...
Click to collapse
Those instructions appeared to work, and now it downloads the update, but when it gets about halfway through the install, it goes to the android error image and I have to reboot.
Is it just me or does V2 not have 42nrecovery.img inside its zip..? I had to download V3 because that was the only one that had that file. I've successfully got to Android Wear version 4.4W now, but when i try to go to System Updates, it tries to download but then tells me that "something went wrong"...any ideas?
TIA
I used the instructions from post 7 and the files from post 9 to get my watch connected to my phone and auto-updated to version 5.0.1 build LWX48P.
so
Copy all the files to one Dir and CMD to that Dir.
Put you watch in fastboot mode. You Don't even need to do anything other then take it out of the Box put in fastboot mode. I was having a hard time getting into fastboot. The key is after rebooting the watch by holding down the power button, you NEED TO CONTINUE holding the power button WHILE you swipe from upper left hand side to lower right side...the motion look like this ---> \
Run the Four fastboot commands
fastboot oem unlock
fastboot flash boot 78Yboot.img
fastboot flash recovery 78Yrecovery.img
fastboot flash system 78Ysystem.img
Thank you godgib for the instructions and thank you Tomsgt for the recovery files
Thanks to everyone who contributed to this thread. Managed to use V2 to put on a stock image, which then allowed my watch to update to the latest OTA.
Is there a risk doing this? I do not recall reading in the BB description that this was the different version than the "stock"
Bluetooth problems?
Has anyone had trouble with bluetooth on their Samsung Gear Live after going back to stock? I did both the automated V3 method and the manual fastboot methods and when the watch reboots, the phone cannot detect the watch via Bluetooth.
---------- Post added at 09:34 PM ---------- Previous post was at 09:24 PM ----------
Nevermind, I figured out that I can't use the files in V3. I have to use the three *.img files from V2 (i.e. 4.4W).
samevo8 said:
Has anyone had trouble with bluetooth on their Samsung Gear Live after going back to stock? I did both the automated V3 method and the manual fastboot methods and when the watch reboots, the phone cannot detect the watch via Bluetooth.
Click to expand...
Click to collapse
Hello,
I have my G watch R for a week and because there was no update, i've tried to install it by myself after reading some posts on XDA.
I've tried that :
- Enter Bootloader (swipe top left-bottom right as soon as the LG logo pops up on boot)
- Unlock bootloader (fastboot oem unlock) and boot the watch normally once
- Turn off and re-enter bootloader
- Flash 5.0.1 Stock Recovery (fastboot flash recovery filename.img)
- Enter recovery and ADB sideload the update (tap the android, select install update from ADB and enter adb sideload filename.zip)
All this works until the "sideload" part because ADB can't see my watch when it's on recovery mode.
So i have locked again the bootloader and i thought to give up, when yesterday, OTA arrived...
But it hasn't worked : a bar has loaded and it arrived on a red triangle with an exclamation mark, i've clicked on it and i had the recovery mode menu (reboot, install from adb, etc)
What can I do to make work this OTA ?
Thanx for help !
have you tried to flash the original recovery?
Yes, I've tried several times, I think that is why i can't update with OTA.
But is there a solution ? Is it possible to reinstall original recovery and will it solve my problem ?
Or must I install the update with ADB ? Because I still don't know how make the watch recognized when in recovery mode (not even recognized with a yellow triangle, like it was unplugged )
I had the same problem but with 4.4w.2 and I solved it flashing the stock recovery. unfortunately I can not find your recovery version, I would have linked. to manually update do not know ... I'm sorry. Find your recovery and flash it!
Thanx for your answer,
I thought to do that, but I neither have found 44w1 stock, i'm trying with 44w2 stock and it doesn't work.
I'll try to find 44w1 stock, thanx for confirmation about this way.
So, while I can't find 44w1 stock (i think nobody has uploaded it on the internet because nobody wants to put 44w1 on his watch ^^ ), I've tried TWRP Recovery
When I try to launch the 5.5.1 zip install , I have this error message on the watch in TWRP Recovery :
"this package is for device: lenok. this device is dory"
I've made some research and found that Dory is for G Watch and not for G Watch R, so what ?
I don't understand...
Anyway, if someone knows where to find 44w1 stock...
Did you enabled the debugging mode and gave permission for it on the watch?
sounds like you are missing the ADB drivers on your PC
and be careful with sideloading the update to select the correct one, e.g. the last update is an incremental one and won't flash on 4.4 (or if you get it to flash, it will probably not worke)
good luck!
Have a look here... http://4pda.ru/forum/lofiversion/index.php?t647135-20.html.
It's not English, but the links are all there. I recently updated a watch from 4.4 to 5.11 using these images. Put the watch into Bootloader and install the ADB drivers, then start with 4.4w2 and work your way up. It takes time as you'll need to restart the watch each time.
Genna7 said:
Did you enabled the debugging mode and gave permission for it on the watch?
Click to expand...
Click to collapse
Yes I did : I could flash a recovery because I've given permission and enabled debugging mode
2k4ever said:
sounds like you are missing the ADB drivers on your PC
and be careful with sideloading the update to select the correct one, e.g. the last update is an incremental one and won't flash on 4.4 (or if you get it to flash, it will probably not worke)
good luck!
Click to expand...
Click to collapse
No I'm not, same answer : I could flash a recovery without any problem : it's only when I'm on recovery that I can't communicate with the watch : It's working when android wear is started and when I'm on bootload. Thanx for the warning
dunjamon said:
Have a look here... *url*
It's not English, but the links are all there. I recently updated a watch from 4.4 to 5.11 using these images. Put the watch into Bootloader and install the ADB drivers, then start with 4.4w2 and work your way up. It takes time as you'll need to restart the watch each time.
Click to expand...
Click to collapse
Thank you but i have all those images, I think I need 44w1 recovery and only this one
Thank you all
what happens if you just flash the 4.4w2 full image? I remember there being issues with the 4.4 recovery and I had to manually update to the 5.0.1 recovery before then upgrading further.
edit...what drivers are you using? I think you need the adb composite ones and not the normal adb ones.
I'm using the naked ones I think.
What image are you talking about ? System or recovery ?
Ze_Pend said:
I'm using the naked ones I think.
What image are you talking about ? System or recovery ?
Click to expand...
Click to collapse
The OTA ones from my link.
Ze_Pend said:
Yes I did : I could flash a recovery because I've given permission and enabled debugging mode
No I'm not, same answer : I could flash a recovery without any problem : it's only when I'm on recovery that I can't communicate with the watch : It's working when android wear is started and when I'm on bootload. Thanx for the warning
Click to expand...
Click to collapse
flashing a recovery happens in fastboot mode, which requires an unlocked bootloader, but not enabling the debugging mode
sideloading however happens (once the recovery has been loaded) through ADB - and ADB requires the right drivers on your PC as well as the right tools/developer environment
try to connect your normally booted watch to your PC and run
PHP:
adb devices
if that lists your watch, you are good to go, otherwise ADB isn't set up properly
The watch is listed by adb devices when on work mode or in bootloader mode, but not when in recovery mode.
That's what I said first
dunjamon said:
The OTA ones from my link.
Click to expand...
Click to collapse
Either I can't if with 44w2 recovery, or it says ""this package is for device: lenok. this device is dory" if with TWRP recovery.
Ze_Pend said:
Either I can't if with 44w2 recovery, or it says ""this package is for device: lenok. this device is dory" if with TWRP recovery.
Click to expand...
Click to collapse
Do you have the G Watch R (round) or the G Watch (Square)?
"The watch is listed by adb devices when on work mode or in bootloader mode, but not when in recovery mode."
I had this problem too. When you're in recovery mode you have to open the windows device manager and windows should tell you something about an uninstalled driver. You need to right click this device and install the adb drivers.
Hey everybody!
This is my first time posting something on XDA. This is really cool.
So I just bricked my fire, hard. Let's start from the top:
- I used the super tools rootjunkysdl.com/?device=Amazon%20Fire%205th%20gen&folder=SuperTool to get the google play store.
- Using the google play store, I got flashfire.
- Using flashfire, I flashed SlimLP onto my tablet successfully and quickly.
- I got a little cocky, and based on the comments on the youtube.com/watch?v=NaCBSuUuhRE video that I used to flash SlimLP I decided to try the flashfire technique with CM since it is my favorite ROM.
- I did everything properly and the same, but... it got stuck here... for about an hour...
imgur.com/QJvmRz3
So I decided to do the smartest thing ever and cancel it myself by turning it off, I wasn't able to do anything else anyway. Either way, my tablet is now stuck in the cyanogen 12 boot load animation, the one of the cute blue head with the radar effect.
I would of fixed this a long time ago, but for some reason I'm not able to adb sideload.
I go into fastboot, I can detect the device, but not adb sideload.
I go into adb sideload mode, I can't detect the device, so definitely not sideload. :/
I've tried updating my drivers, I don't know if I'm doing it right, but while it was in fastboot mode, I changed it to Android Composite ADB Interface, and that didn't change anything.
No matter what I'm doing, whenever I do adb devices, I always get:
List of devices attached
Blank. Nothing. Only when I'm in fastboot mode do I get:
fastboot devices
G0K0H40454261ARU fastboot
Something, but still no ADB. I can't even load TWRP here, tried that, I just install it and it just sits there dumbly saying it's installed.
I'm bricked just like my tablet. Could I please get some help here? I'm very desperate to get this tablet back up and running, and I feel so stupid for not having stuck with Slim and trying to install CM. I really don't want it to stay bricked like this.
Thank you, XDA!
Do you know if you had amazon FireOS version 5.0.1 or 5.1.1?
Just to be clear, you have actually selected the adb sideload option on your Fire when you try to connect with adb on you pc, correct? ADB is not even active until the adb sideload option has been selected.
drillster said:
I can't even load TWRP here, tried that, I just install it and it just sits there dumbly saying it's installed.
Click to expand...
Click to collapse
We can not "install" twrp. The bootloader is locked & won't allow it. We can only temporarily load twrp into memory. Each time we want to use twrp, we must connect usb to a pc, enter fastboot mode & load twrp. But this can only been done on 5.0.1 Fires. It's been blocked on 5.1.1. No way to load twrp at all on 5.1.1.
Just use this method: http://forum.xda-developers.com/ama...howto-how-to-restore-frimware-device-t3238740
hAtE NeVeR dIeS said:
Just use this method: http://forum.xda-developers.com/ama...howto-how-to-restore-frimware-device-t3238740
Click to expand...
Click to collapse
Do not follow the instructions in that thread! It will permanently brick you if you're have the FireOS 5.1.1 bootloader. The OP of that thread finds it too hard to add a note that it's outdated. See the page 4, post #36
blueberry.sky said:
Do not follow the instructions in that thread! It will permanently brick you if you're have the FireOS 5.1.1 bootloader. The OP of that thread finds it too hard to add a note that it's outdated. See the page 4, post #36
Click to expand...
Click to collapse
I have 5.1.1... yeah, thanks.
blueberry.sky said:
Do you know if you had amazon FireOS ve wrsion 5.0.1 or 5.1.1?
Click to expand...
Click to collapse
I have 5.1.1.
blueberry.sky said:
Just to be clear, you have actually selected the adb sideload option on your Fire when you try to connect with adb on you pc, correct? ADB is not even active until the adb sideload option has been selected.
Click to expand...
Click to collapse
Yeah I selected apply update from adb, adb devices was blank, didn't work.
blueberry.sky said:
We can not "install" twrp. The bootloader is locked & won't allow it. We can only temporarily load twrp into memory. Each time we want to use twrp, we must connect usb to a pc, enter fastboot mode & load twrp. But this can only been done on 5.0.1 Fires. It's been blocked on 5.1.1. No way to load twrp at all on 5.1.1.
Click to expand...
Click to collapse
I went into fastboot mode, installed twrp, and nothing happened because yes, its 5.1.1.
I've seen some other people who also have been unable to get adb to work (in custom recovery). I don't recall a solution.
There is an option in fastboot to flash firmware, I haven't seen anyone try that yet..
blueberry.sky said:
I've seen some other people who also have been unable to get adb to work (in custom recovery). I don't recall a solution.
There is an option in fastboot to flash firmware, I haven't seen anyone try that yet..
Click to expand...
Click to collapse
Do you have any ideas on how to do this? I would greatly appreciate it.
Thank you!
Since I haven't read anyone try it before, there would be some risk. I suppose you are already bricked, seemingly without a way to fix it, but you could brick it harder. You might be able to get adb working. I may not have any ideas on how to get adb working for you, but someone else might know. If you try flashing the stock OS via fastboot, there is a chance you could brick it in a different way.
The command would be
Code:
fastboot update <filename-of-stock-firmware.zip>
But we don't have a .zip stock firmware file. In twrp recovery you can just rename the .bin file to .zip & it works. Not sure if that will also work for fastboot. My guess is it won't work & might brick you.
Also be aware, on Fires that self-updated to FireOS 5.1.1 (or came with 5.1.1 new) you must only flash 5.1.1. Attempting to flash 5.0.1 will brick it 100% of the time & it's unrecoverable.
drillster said:
No matter what I'm doing, whenever I do adb devices, I always get:
List of devices attached
. . .
Click to expand...
Click to collapse
Just a shot in the dark here, but have you gone into device manager while in sideload mode and updated drivers for KFFOWI under Other devices? Windows needs drivers for every mode.
I have same issue.
[QUOTE=drillster;64617577]Hey everybody!
This is my first time posting something on XDA. This is really cool.
So I just bricked my fire, hard. Let's start from the top:
- I used the super tools rootjunkysdl.com/?device=Amazon%20Fire%205th%20gen&folder=SuperTool to get the google play store.
- Using the google play store, I got flashfire.
- Using flashfire, I flashed SlimLP onto my tablet successfully and quickly.
- I got a little cocky, and based on the comments on the youtube.com/watch?v=NaCBSuUuhRE video that I used to flash SlimLP I decided to try the flashfire technique with CM since it is my favorite ROM.
- I did everything properly and the same, but... it got stuck here... for about an hour...
imgur.com/QJvmRz3
So I decided to do the smartest thing ever and cancel it myself by turning it off, I wasn't able to do anything else anyway. Either way, my tablet is now stuck in the cyanogen 12 boot load animation, the one of the cute blue head with the radar effect.
I would of fixed this a long time ago, but for some reason I'm not able to adb sideload.
I go into fastboot, I can detect the device, but not adb sideload.
I go into adb sideload mode, I can't detect the device, so definitely not sideload. :/
I've tried updating my drivers, I don't know if I'm doing it right, but while it was in fastboot mode, I changed it to Android Composite ADB Interface, and that didn't change anything.
No matter what I'm doing, whenever I do adb devices, I always get:
List of devices attached
Blank. Nothing. Only when I'm in fastboot mode do I get:
fastboot devices
G0K0H40454261ARU fastboot
Something, but still no ADB. I can't even load TWRP here, tried that, I just install it and it just sits there dumbly saying it's installed.
I'm bricked just like my tablet. Could I please get some help here? I'm very desperate to get this tablet back up and running, and I feel so stupid for not having stuck with Slim and trying to install CM. I really don't want it to stay bricked like this.
Thank you, XDA![/QUOTE]
I did the same thing. Slim worked great, tried to flashfire CM12, ot bricked. Can get fastboot, but nothing else. Afraid to try update from fastboot.
I just want to say thanks to everybody who contributed, I'm really appreciative of the support, especially because I didn't expect it, haha! Listening to blueberry.sky I'm going to try the flashboot update, because it's either that or a bricked device. School just started so I got busy with that.
DoLooper said:
Just a shot in the dark here, but have you gone into device manager while in sideload mode and updated drivers for KFFOWI under Other devices? Windows needs drivers for every mode.
Click to expand...
Click to collapse
So when I have it in adb mode, the fire doesn't seem to show up anywhere in any of my devices, and I can only find it when it's in fastboot mode. So when it's in that mode, I've tried Android ADB Interface, Android ADB Composite Interface, and when I go back to adb sideload, it's just not there in device manager. I don't know what this means, so any speculation? But no matter what mode I'm in or what driver I'm using, I can't seem to get it to show up in adb when in sideload mode.
Again, thanks everybody, and I hope anybody else in the future with this issue can refer to this thread for a lead!
So I just tried to flash update the firmware from Amazon amazon.com/gp/help/customer/display.html?nodeId=201830180 which I renamed from .bin to .zip:
C:\path\to\SuperTool>fastboot update update-kindle-global-37.5.4.1_user_541112720.zip
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
I didn't rename the Slim and this is what I get:
C:\path\to\SuperTool>fastboot update Slim-ford-5.1.1.build.2.2b-20151210.zip
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
Is there anyway I can resolve this, so I can do SOMETHING?
Thank you!
drillster said:
So I just tried to flash update the firmware from Amazon amazon.com/gp/help/customer/display.html?nodeId=201830180 which I renamed from .bin to .zip:
Is there anyway I can resolve this, so I can do SOMETHING?
Thank you!
Click to expand...
Click to collapse
To be clear, you were able to, "adb sideload update-kindle-global-37.5.4.1_user_541112720.bin". To restore your Fire OS 5.1.1?
thekrakah said:
To be clear, you were able to, "adb sideload update-kindle-global-37.5.4.1_user_541112720.bin". To restore your Fire OS 5.1.1?
Click to expand...
Click to collapse
No, I did fastboot update in fastboot mode as suggested by blueberry.sky since ADB isn't working for reasons I stated before.
C:\path\to\SuperTool>fastboot update update-kindle-global-37.5.4.1_user_541112720.zip
drillster said:
No, I did fastboot update in fastboot mode as suggested by blueberry.sky since ADB isn't working for reasons I stated before.
C:\path\to\SuperTool>fastboot update update-kindle-global-37.5.4.1_user_541112720.zip
Click to expand...
Click to collapse
So when you say you go into "adb sideload mode. You selected "apply update from adb", and the Fire device is actively waiting for the sideload command, but you got nothing showing up in your device manager at that point?
I'm just clarifying because until the "apply update from adb" is activated, windows doesn't get a communication from the Fire device.
thekrakah said:
So when you say you go into "adb sideload mode. You selected "apply update from adb", and the Fire device is actively waiting for the sideload command, but you got nothing showing up in your device manager at that point?
I'm just clarifying because until the "apply update from adb" is activated, windows doesn't get a communication from the Fire device.
Click to expand...
Click to collapse
On my device, I can get fastboot, but not adb. if I reboot from fastboot, I only get the
CM logo and it sticks there permanently until I power off. When I boot to fastboot, the screen is blank but my Windows PC can see the device and return the SN. I can issue the command to reboot to bootloader, but reboots to fastboot with "fastboot" in small letters at the bottom of the screen. What else can I try? Thanks for all the help offered so far.
What happens when you try to get into recovery mode?
To get into recovery you start with the Fire off. Turn off by holding power button until it goes off (might take awhile). I just tried turning off from fastboot mode. Took only about 14 seconds of holding power.
To enter recovery: hold volume down button + hold power button.
blueberry.sky said:
What happens when you try to get into recovery mode?
To get into recovery you start with the Fire off. Turn off by holding power button until it goes off (might take awhile). I just tried turning off from fastboot mode. Took only about 14 seconds of holding power.
To enter recovery: hold volume down button + hold power button.
Click to expand...
Click to collapse
When I try to get into recovery, it boots with a blank screen. At that point, I can connect to my PC, type fastboot devices, and it will show me device. Then I try to reboot-bootloader, and it reboots to fastboot, but this time it says fastboot on the screen. I can't seem to get to recovery
watch this video to see if it helps.
https://www.youtube.com/watch?v=RQLoH-ahjy4
ok i have a bit of an issue.
simply put i was attempting to remove xposed, root, busy box. really just about any and all modifications. so i attempted to flash a stock 5.1.1 from google... i think i flashed the wrong one. because everything went fine through the flashing, but the phone wont boot past the google splash screen.... well as the derp i am. i locked the boot loader after because i was planning on sending it back to at&t. well now. im attempting to try a few different 5.1.1 images. (which in writing this im thinking... that isnt probably the best course of action.)
well i guess what this leads to is..... first.... which image do i use.
i was running 5.1.1 before all the modifications. so i just attempted to flash a 5.1.1 for all carriers cept T-moblie
i used shamu from this site https://developers.google.com/android/nexus/images#shamu
i also want to toss it out that the phone has been dropped....so internal damage might be a possibility, but i doubt thats it since it was fine before the flash.
so over what image should i flash? and is there a way to unlock the bootloader without going into the settings and chekcing the OEM box under dev options? because accessing the phone is basically limited to boot loader and recovery right now.
If you locked the bootloader, you cannot flash factory images. If you still have a custom recovery installed, install a custom ROM. Otherwise, you need to find the Android N Preview 1 OTA zip, which should be on these forums, and flash it through stock recovery. The OTA is a complete system image, and will update your system regardless of whether the bootloader is locked or not.
Regardless of which way you install a ROM, reveal the Developer Options menu and check "Enable OEM Unlock". Then you can unlock the bootloader and flash a fresh Android 6.0.1 factory image from Google, which is carrier agnostic.
Strephon Alkhalikoi said:
If you locked the bootloader, you cannot flash factory images. If you still have a custom recovery installed, install a custom ROM. Otherwise, you need to find the Android N Preview 1 OTA zip, which should be on these forums, and flash it through stock recovery. The OTA is a complete system image, and will update your system regardless of whether the bootloader is locked or not.
Regardless of which way you install a ROM, reveal the Developer Options menu and check "Enable OEM Unlock". Then you can unlock the bootloader and flash a fresh Android 6.0.1 factory image from Google, which is carrier agnostic.
Click to expand...
Click to collapse
ok well first i appreciate the reply
so basically the set up is i am running stock recovery with a locked boot loader.
if i use this Android N Preview 1 OTA zip. this will allow me access to the dev options which then i can boot up to check the bootloader box? then i can flash 6.0.1.
if that's right then awesome! i appreciate the help. so just so i don't fall back into this mistake. i have the AT&T version of the Nexus 6.
so if there is a specific Image i need, could you please point me to it?
I'd rather not have this happen again lol. the reason i ask is because the site i posted in my Original post has like 4 version of the 6.0.1 image that i can choose from. and since my track record of doing this hasn't panned out all that well so far i figured id just ask for specifics before attempting anything because clearly i messed up and have very little understanding of what im doing.
again. i really appreciate your advice
"Carrier agnostic" in my previous post means it doesn't matter what carrier you have. With Android 6.0.1, the system images no longer have carrier customization within them. The carrier-specific stuff is downloaded when the phone is set up with the SIM inserted.
As for your current setup, install the Android N preview OTA by sideloading it in recovery, boot into Android, enable developer options, and enable OEM unlock. From there, you need to make sure you have on the PC drivers for the Nexus installed, as well as Fastboot and ADB. Unlocking the bootloader as well as installing the Android 6.0.1 system image require it. If you need a walkthrough, there should be tutorials for both installing the Android N OTA as well as installing a system image in the General section of the Nexus 6 forums.
Strephon Alkhalikoi said:
"Carrier agnostic" in my previous post means it doesn't matter what carrier you have. With Android 6.0.1, the system images no longer have carrier customization within them. The carrier-specific stuff is downloaded when the phone is set up with the SIM inserted.
As for your current setup, install the Android N preview OTA by sideloading it in recovery, boot into Android, enable developer options, and enable OEM unlock. From there, you need to make sure you have on the PC drivers for the Nexus installed, as well as Fastboot and ADB. Unlocking the bootloader as well as installing the Android 6.0.1 system image require it. If you need a walkthrough, there should be tutorials for both installing the Android N OTA as well as installing a system image in the General section of the Nexus 6 forums.
Click to expand...
Click to collapse
well when using the adb devices command... my device wont show up. i can get it to show up when i reboot into bootloader and use fastboot devices, but it wont register in the recovery. could it be because i dont think i have ADB debugging checked? since i flashed new image on it and now i cant access the menus i cant chenc the debugging box either.
So where are you getting stuck? The OTA needs to be copied to internal storage and installed from there. You shouldn't need ADB or Fastboot until after you install the N preview.
Strephon Alkhalikoi said:
So where are you getting stuck? The OTA needs to be copied to internal storage and installed from there. You shouldn't need ADB or Fastboot until after you install the N preview.
Click to expand...
Click to collapse
ok so im lost now. i need to take the tgz file and put it on my phone then when i go to the recovery i need to sideload it?.. dont you do that by having it sideload the file from your PC? right? well my issue now is that i cant get it to show its storage on my PC. when booted into recovery the device wont even show up on my PC at all and when it boots into fastboot it regesters, but i cant do anything because the bootloader isnt unlocked i also cant unlock it via command because the OEM checkbox hasnt been checked. and i cant check the oem box via usb debugging because my device doesnt regester when in recovery.
so im not sure. where to go from here. is there a way to place the file on my phones storage via fastboot or usb debugging? preferably fastboot because ADB commands dont seem to regester to my phone at all.
You need to start reading, which I recommended if you needed a walkthrough.
http://forum.xda-developers.com/nexus-6/general/to-save-bricked-nexus-device-t3334660
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Age135 said:
well when using the adb devices command... my device wont show up. i can get it to show up when i reboot into bootloader and use fastboot devices, but it wont register in the recovery. could it be because i dont think i have ADB debugging checked? since i flashed new image on it and now i cant access the menus i cant chenc the debugging box either.
Click to expand...
Click to collapse
you can only use fastboot, while you're in the bootloader, to do anything.. unlock it, flash a factory image, flash a custom recovery. adb will do nothing and see nothing.
simms22 said:
you can only use fastboot, while you're in the bootloader, to do anything.. unlock it, flash a factory image, flash a custom recovery. adb will do nothing and see nothing.
Click to expand...
Click to collapse
yeah thats what i was thinking. the other guy was saying to sideload using recovery, but tbh i wasnt sure how to sideload and i didnt wanna be rude and act like you guys were my personal helpers. so i googled how to just to get a general idea. the idea that i got was that you needed to sideload anything by downloading it to your PC then using adb to install it.
apparently i dont know as much as i think. hes helping me out alot, but im not sure how to pull a file onto a phone that wont boot. i thought maybe i could transfer it via adb,but i think that boat is gone. since it seems i can only use fastboot, but idk of a way to transfer a file onto my phone via fastboot.
i appreciate the help though. thanks
Strephon Alkhalikoi said:
You need to start reading, which I recommended if you needed a walkthrough.
http://forum.xda-developers.com/nexus-6/general/to-save-bricked-nexus-device-t3334660
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Click to expand...
Click to collapse
ok. so all of these say i should download it to the phone so i can sideload it using the recovery.... well this is the issue. the phones storage wont register on my PC. so transferring a file normally isnt gonna be possible (unless im doing something wrong and theres a way to make it show up). is there a way i could transfer it onto the device via fastboot?
Edit:
after doing some reading. i have found out i may not have adb drivers installed... ive looking into how to install them, but the only option i found was through a downloader which seems to stop after a bit of the download saying its waiting for something... so im completely lost as to what to do from here.
Age135 said:
ok. so all of these say i should download it to the phone so i can sideload it using the recovery.... well this is the issue. the phones storage wont register on my PC. so transferring a file normally isnt gonna be possible (unless im doing something wrong and theres a way to make it show up). is there a way i could transfer it onto the device via fastboot?
Edit:
after doing some reading. i have found out i may not have adb drivers installed... ive looking into how to install them, but the only option i found was through a downloader which seems to stop after a bit of the download saying its waiting for something... so im completely lost as to what to do from here.
Click to expand...
Click to collapse
Try these drivers from Googles site.
https://developer.android.com/sdk/win-usb.html
Hi everyone,
I have retrieved a Samsung Tab 3.7.0 SM-T210. The OS was the old KitKat 4.4.2, very slow and buggy. I tried to flash a new recovery and OS and spent the 3 last days getting fails. I think I have read the all internet about this situation and would like to make a last try with your help.
When I got the tablet, I was surprised that in download mode it was indicated custom and custom binary and not official as it has not, I think, been flashed in the past by the people owning it. With HW rev 0x5 at the end.
The first thing I wanted to do was to unlock the bootloader, however, I could not find any option in developer mode talking about OEM bootloader, neither Auto Update. After reading some people on forumes saying that this device might not have a locked bootloader, I finally thought that this tablet did not have its bootloader locked. Then I decided to go further with the flash of a TWRP recovery.
At the beginning the stock recovery was working. I am under archlinux, I have fastboot and heimdall. To do it as right as possible I installed a VM with Windows 10 and tried to flash a custom TWRP corresponding to the tablet with Odin. But the process got stuck at the SetupConnection step. I installed Windows 7 too, tried 5 different Windows OS, tried 4 different USB cables, reinstalled the USB drivers, tried 5 different Odin versions, tried different archives, just recoveries and all stock system. Still getting stuck at the SetupConnection.
I finally decided to try heimdall thinking that the VM could be the problem. With heimdall I run flash commands such as heimdall flash --RECOVERY twrp-3.2.3-0-lt02ltespr.img --no-reboot and got it doing something, the shell was saying it's 100% done and the tablet, in download mode, was showing a complete blue bar. Then, the recovery was just broken. Could not access it anymore, the Samsung Tab3 logo showing up and staying when trying to access it. I tried to flash some others archives, I opened it off and remove the battery for 5 minutes, still the same thing.
The operating system was still accessible and buggy, applications saying connection issues, etc. I did a factory reset from the running KitKat android OS and now have the Samsung Tab3 logo showing up and staying when trying to access it.
Now, I can only access the download mode and that's all. I have the impression that I am not the first one having these kind of trouble with this tablet. Is it a hardware issue on all these tablets ? Should I try something more advanced with heimdall, dd ?
Does someone have a solution in this situation ?
Thanks for your time and help.
I finally used heimdall and was able to flash all the partitions with the stock images. Now I am back in stock version. I would like to flash a TWRP recovery.
Can someone tell me if I have to unlock the bootloader with this device ? If it is, how can unlock it ? I can not find anything in the settings developer section, and can not use a call number input in order to enter a system code as it's a tablet. Do I have to wipe something from the stock recovery in order to see it ?
Thanks for your time.
Hi -yo-.
You don't need to do OEM unlock as this device is so old.
Also twrp-3.2.3-0-lt02ltespr.img is NOT for this device.
For recovery look from here and for ROM here.
Thanks jonezy82 for the answer. Indeed, I figured all of that out.
I decided to get it back stock and not trying to flash anything custom.
Thanks for your time.