Database Develop

[Q] Bricked Galaxy Gear

Hi guys! I have a big problem, because in the past I installed null rom on my gear, but today I wanted to update it to Tizen. So, I tried it with Odin, but it stuck and show a message Setup Connection... So I tried it again and again and again. Maybe 2x it skipped this message, but then it stucked I think in zImage or something like this. Then I unplug the cable from PC (when it showed me zImage) and now it is showing an error message on my Gear: Firmware update encountered an issue. Please select recovery mode in Kies and try again.
But the problem is that Kies didnt connect to my gear, it is "Connecting" non-stop. So it recognise that something is in PC, but it didnt recognize that is my Gear. In Odin I have the same problem that i mentioned earlier in this post. Setup Connection and it is completely frozen. I tried everything. Other USB ports (I think 7 different ports), I tried to flash stock rom on another PC, I reinstalled the Samsung USB drivers, I tried to flash custom recovery, I tried different versions of Odin, maybe 10 alternatives from 1.5.2 to 3.09... So I dont know what should I do. Please help me an sorry for my terrible english, but I hope you understand me.
Thank you!
//PROBLEM SOLVED
I downloded stock android 4.2.2 and flash it with odin 3.09 on Windows 7 without problems.

Bricked Samsung Gear Live - Please help.

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

I have tab 2, i was trying to install firmware but die to some issues had to remove u

I have tab 2, i was trying to install firmware but die to some issues had to remove usb from system. Now it is showing firmware upgrade encountered an error try connecting to kies... And odin recognises it but i can flash stock firmware again plz help

xyzabc123456789 said:
I have tab 2, i was trying to install firmware but die to some issues had to remove usb from system. Now it is showing firmware upgrade encountered an error try connecting to kies... And odin recognises it but i can flash stock firmware again plz help
Click to expand...
Click to collapse
Very similar situation with mine. However Odin won't operate on my Windows 7 Computers and the Tab won't accept anything from either the Computer, SdCards or any other way. Even when I can access firmware according to the Boot Mode Screen. I'm stuck as well. But hope you solve your problem...

Odin stuck on "system.img.ext4" Help please?

Hi All,
I tried to flash my phone from VZW firmware to unlocked firmware and my odin3b has been stuck on system.img.ext4.
I realized I hadn't installed the samsung drivers the first time around. I attempted to restart the phone as it was stuck on system.img.ext4 - following that my phone shows the screen:
"Software Update Failed Your device didn't update successfully. Use the Verizon Software Upgrade Assistant on a computer to repair your device and complete the update."
I'm unable to re-boot or do anything, when I hold power, bixby, volume down it presents me the warning screen before entering download mode. If I press Volume Up or Volume Down - I hit the same warning screen I typed up above. I am able to view the barcodes by pressing the bixby screen...
When I went back to Odin it still showed as "Added" when I plugged in the phone. I attempted the process again but it's still stuck on the same part.
Anybody have any suggestions of what I should attempt? I've been reading but have been unable to see any solutions.
Thanks for reading.

I Havnt played with the note 9 in terms of flashing or rooting as I have the SM-N960W Canadian Snapdragon version and there is no way yet. I've used Odin many times to flash and it can be fussy for a few reasons, I rooted my Galaxy S7 and nexus 5 and a few others. My tips would be....
First Uninstall Samsung driver.
Then Download "usbdeview" on your pc and Uninstall any previous USB connections labeled Android or Samsung or related, as this will allow you to start off as if it's a fresh connection.
Re-Install Samsung USB drivers, then....
Plug in Using stock OEM Samsung Note USB cord and wait for it to connect.
If no luck try a different USB port. USB 2.0 May work if your using USB 3.0 and it isn't.
Try a different version of odin, there are many, also running odin as administrator may help but not necessarily for sure.
If all this fails try on another computer or laptop. Make sure you only select the proper/necessary options in odin.
It sucks when things don't go as planned but that's the risk you take when you don't stay stock & update OTA. The steps I've written for you have fixed any issues I have ever run in to with odin & flashing but if yours was an incomplete flash and disconnected or interrupted mid way you may be stuck with an expensive paperweight I'm sad to say. Try contacting Samsung for proper odin version & odin settings, I wish you the best of luck. I am in no way a mobile phone technician but I've rooted many phones and always made it work. I hope you can too!
Best of luck!

flash back your official firmware to get back access to fone
if none of this works use smartswitch( it will reinstall drivers)
then tey again with odin 13.3 b using u1 firmware
also to get to dl mode power off the fone. if you have access to recovery ( reboot fone with vol down Bixby and power and quicly change to vol up bixy and pwr when you see it reboot)go there and choose shutdown phone. or let battery die and charge it for 10 mins and do while phone is off :
hold vol down and Bixby with one had and with the other plug the usb cable from rhe pc to fone.

The same problem happened with me. I wonder if anyone knows how to solve it?

Sukrus said:
The same problem happened with me. I wonder if anyone knows how to solve it?
Click to expand...
Click to collapse
Try your luck with different odin versions, different cable, different pc, different firmwares

As above first step Samsung USB drivers and Samsung USB cable .

Alcatel Idol 4 6055K problem with firmware

Hello,
I have a somewhat aged Idol 4 lying here.
This no longer boots or it hangs in the boot loop.
So I tried to install an update via a stock rom from the network via the recovery menu and ADB sideload and always got the error status 7. (Alcatel_Idol_4_6055K_01001_01002_OTA)
Resetting the system didn't help here either.
Then I tried to install TWRP on the device.
But unfortunately both methods that I tried failed.
Once via Sahara & firehose-test and the second was Suger QCT via the download mode.
But both of them got the error message NPRG Error 5002.
I have installed suitable USB drivers.
So my question, does anyone have a tip for me on how I could get the device revived?
And Sorry for my bad english

Hm.. said:
Hello,
I have a somewhat aged Idol 4 lying here.
This no longer boots or it hangs in the boot loop.
So I tried to install an update via a stock rom from the network via the recovery menu and ADB sideload and always got the error status 7. (Alcatel_Idol_4_6055K_01001_01002_OTA)
Resetting the system didn't help here either.
Then I tried to install TWRP on the device.
But unfortunately both methods that I tried failed.
Once via Sahara & firehose-test and the second was Suger QCT via the download mode.
But both of them got the error message NPRG Error 5002.
I have installed suitable USB drivers.
So my question, does anyone have a tip for me on how I could get the device revived?
And Sorry for my bad english
Click to expand...
Click to collapse
Hello, I deleted my system from twr without realizing what I was doing, the result is that I stay on the Alcatel logo. My steps were, the installation of sugar, when it starts not to update the application. Choose the 6055 model, since the 6055P model that is mine does not appear in the drop-down. Before starting sugar, turn off the mobile completely and connect it off to the usb of the pc, check if when connecting it the pc does not detect it, use another cable (there are many cables that only serve to charge and not to read on the pc) Now start sugar, choose the model and click on the Udgrade tab. You will surely get several messages saying that the mobile has been modified and that you lose the guarantee, go ahead accepting the message, in a few minutes you will have it ready. Greetings.

Perdigon55 said:
Hello, I deleted my system from twr without realizing what I was doing, the result is that I stay on the Alcatel logo. My steps were, the installation of sugar, when it starts not to update the application. Choose the 6055 model, since the 6055P model that is mine does not appear in the drop-down. Before starting sugar, turn off the mobile completely and connect it off to the usb of the pc, check if when connecting it the pc does not detect it, use another cable (there are many cables that only serve to charge and not to read on the pc) Now start sugar, choose the model and click on the Udgrade tab. You will surely get several messages saying that the mobile has been modified and that you lose the guarantee, go ahead accepting the message, in a few minutes you will have it ready. Greetings.
Click to expand...
Click to collapse
Hello, thanks for the answer and the download.
I've tried the same way. I still downloaded your file and tried as you described.
Unfortunately I got the same error NPRG Error 5002 again.
Unfortunately I have no idea where the problem could be.

I found out that it could be a memory error.
As if a flash process had failed and there is no longer a correct series of partitions.
So I would need a complete original rom and would have to flash it via fastboot.
I could also try it via twrp, but I don't get this flashed.
And I don't have a complete original rom either.

Hello,
So I have now been able to flash the phone with another PC with Sugar QCT after it suddenly started up after the battery was completely empty and I charged it again.
But unfortunately the boot problem persists after turning off the phone again.
Even after replacing the battery with a new one.
Then I tried to flash TWRP via the Alcatel Flasher.
The flash process was successful but there was no TWRP on it after the reboot.
So the problem could still be somewhere else than just the firmware.

Hm.. said:
Hello,
So I have now been able to flash the phone with another PC with Sugar QCT after it suddenly started up after the battery was completely empty and I charged it again.
But unfortunately the boot problem persists after turning off the phone again.
Even after replacing the battery with a new one.
Then I tried to flash TWRP via the Alcatel Flasher.
The flash process was successful but there was no TWRP on it after the reboot.
So the problem could still be somewhere else than just the firmware.
Click to expand...
Click to collapse
Hello, it may be that you are making the same mistake that I made when installing recoveri. When selecting the recovery, note that the twr is the one that weighs about 14 mb and the original one about 24 mb. I think that when you make a copy with the recovery program and then install the twr you select it wrong. In the program, do not make the copy of the recovery, skip that step and go directly to install and select the 14 mb file. You will see that this is the problem. Cheers