I spent several DAYS getting this watch to work properly (and by properly, I mean rooted and with a new mod).
You DO NOT need an approved phone for this to work! This will allow your watch to work with virtually any phone.
All you need is a Windows PC (with Odin and the Samsung ADB drivers, although these may not be necessary...), your watch, the charging cradle, USB cord and Wondershare (although there are alternatives to this...).
Because I am a new user and can't submit links, this next part is going to SUCK for you:
Here are things to download:
Samsung ADB Drivers - Google!
The Latest Version of Odin - Google!
Wondershare MobileGo for Andoid - Google it!
V700XXUAMK7 Firmware (Build Date: 13.11.2013 -> Region: BTU (United Kingdom) PDA: V700XXUAMK7 Changelist: 2124806 Android: 4.2.2 ) - Easy to Google
Null TWRP (You can find on this forum)
SuperSU ZIP FILE (Do not open) - (Google for "SuperSU Flashable Zip" )
THE REAL NULL ROM 23!!!! Working as of 1/10/2017 - THANKS TO dbest1010
There are several pitfalls that are introduced because of how OLD most of the information on here is.
First, when you turn on your watch, you may be wondering, how can I get into USB Debugging mode?
If you are stuck on a screen that is looking for a phone to connect to the device (and this may happen more than once during this process), then you need to know this VERY SIMPLE TRICK:
Press your finger over the area where the bottom of the screen is. An orange and black box should appear with some numbers/letters in it. Do this repeatedly. A LOT. Keep pressing it. Sometimes swipe up a little or down a little, it doesn't matter, just keep rubbing it like it was your lover. Before long (sometimes it takes a couple of minutes, seriously, do not give up), the phone will go to semi-normal operation.
This will allow you to go into the settings and hammer near the version area several times (unlocking developer mode), which on the previous screen will allow you to select for USB debugging.
I'm not sure why this trick is not explained very well elsewhere on these forums. Really, if you want pretty much zero functionality from the watch, you can stop here.
You may not have the "stock ROM" loaded on this watch. Fortunately, these are still easy to find. You want the BTU version if you are in the United States.
This step is important, because even if you do not NEED to do this, knowing how to do this may help you recover from a "soft brick", and get back on track.
Put the watch into Download Mode.
To do this, hold the power button until the "Rebooting" menu appears.
Now, press the power button several times (4 or more)
A new menu appears, use the power button to move down to "Download"
Hold power button for 3 seconds, then release it
Download mode will appear
Connect the USB to your PC, then the cradle, then add the watch to the cradle
Open Odin
Leave everything as normal, and click on "AP"
Select the V700XXUAMK7 file/image
Run the process
This should get you the stock firmware rom loaded.
Here are some problems you may encounter during this phase:
When you connect the watch to the cradle, sometimes it shuts off or does something unintended. Make sure the cradle and usb are connected to the PC *before* trying to add the watch, rather than trying to plug the USB into the cradle once the watch is attached.
Odin may not "see" the watch as a device, or the installation process may not complete as desired.
MAKE SURE that Kies, Wondershare, ADB and all that other stuff is NOT RUNNING. By not running, I mean ctrl+alt+del and go to task manager in Windows and kill ALL instances of them, especially Wondershare. Do this before you think you got a bad image or something. This particular step gave me a headache for a while.
The watch should be booted with the regular firmware now. You may need to do that pressing trick on the main screen again to get it to do much else.
For installing the custom recovery ROM (this is NOT the custom ROM, but is needed and recommended to install null on your watch), you follow almost the same exact procedure as before.
EXCEPT,
1.) UNCLICK in the options for Odin "Auto Reboot"
2.) When you get to the part where you add the V700XXUAMK7 image file, instead, when you click "AP", add the Null TWRP file you downloaded previously.
After a successful install ,the watch will still be on the "downloading" screen. It is safe to restart it now, however, and you can hold the power button down and then press it a few times during the "Rebooting" phase to change to recovery mode.
If you did this right, after a brief Samsung Logo, you will see the Null TWRP screen which has several nice options on there for you.
Now, what you should do, since you know that it worked, is you need to ROOT THE DEVICE.
Don't worry about no Impactor stuff or any of that crap. If you're like me, it will not work. Don't worry about ADB or any of that either.
Use your free trial of Wondershare (or your alternative method), and add the SuperSU ZIP file to the ROOT DIRECTORY of your SD card. With Wondershare, you do this by opening Wondershare, and then connecting the device via USB. Remember what I say, put USB to PC, then to cradle, then add the watch.
Why come your Wondershare no see the watch? Make sure you did the trick on the home screen (pressing the stupid box a thousand times) to get into the Settings and enable Developer mode (keep clicking the version) and USB Debugging.
DO NOT BOOT THE WATCH INTO DOWNLOAD MODE! What are you doing?! Just open the watch up and run it regular so you can see the time, make sure USB Debugging mode is turned on, and Wondershare should see the watch. Still having problems? Try for install those drivers I linked at the top for Samsung devices. You may not need to do this.
You are STILL having problems?! Make sure no other process similar is running. No Odin. No ADB. No Kies. No Impactor. Nadda! Ctrl+alt+del and get rid of all those type processes. Then try it again.
Now, to finish the root.
Once the file is transfer over, disconnect the watch again, and reboot into recovery mode.
Go to install and select that SuperSU zip file, it will install right from the zip.
As an extra added measure, go down into the advanced options of TWRP, the recovery mode, and press on the "fix permissions". I don't know, maybe this does not help, but it does not hurt it either.
Restart the watch regular, run the SuperSU program from the "apps" section, and everything should look fine, and your watch is now rooted.
Power back down and go into recover mode again.
NOW, important! Go to TWRP again and go to BACKUP. Create a backup.
This backup is useful from this point so you can recover a fully working stock version that is rooted, because the next step may cause you a lot of frustration.
DO NOT GO TO SOURCEFORGE!!! F0mey has a page on there for the NULL ROM, and it is not even for the same device! It has version all the way to 27. It doesn't matter if you download the oldest version on there is almost 1GB and it is NOT THE CORRECT THING FOR THIS WATCH.
Do not waste your time! I kept flashing all kinds of bogus stuff on my watch trying to get it to work. Some other guy has a Galactus Mod. Don't bother! It will not work!
If you're sitting there trying to install some bogus ROM, and getting stuck in reboot mode and everything, just use that recovery you made and then come back to this thread when you have some sense in your head.
Go back to the top and get the REAL Null Rom 23. This is a mirror somebody found hosted by Kent. it is only about 300MB, not no 900MB file like the stuff on F0mey Sourceforge page.
How to install it?
Well, the same way you moved that SuperSU file over to the SD card with Wondershare, what you can do, is move the null rom over to the SD card using Wondershare. Just move the ZIP, same way as with the SuperSU. Do not open it! Once it is on the watch, this is the easy part, go into the recovery mode again, go to install, and install it.
You'll know it is correct because on the very first screen, it will say the device it is made for before it installs. The other roms say i398 or something, which is NOT THIS WATCH.
It will have all kinds of options you can tap on with your grubby finger. The recommended settings are fine, you may want to tick some of the Google stuff, like the Play Store.
Anyhow, now the whole thing will take a few minutes to install/flash onto your device.
When it starts to boot up, what is this?! It gets stuck in a loop! Galaxy logo, over and over!
No!!! After so much work! This can't be happening!!
Don't worry, this sound stupid, but just connect the watch to the cradle with the USB connected to the PC. Don't do anything else. For some reason, now it will work and boot fine and you'll be able to unplug it later and do what you like with it.
You will have to do the trick of rubbing the main screen again, with the orange and black box. Sorry, it takes forever, I know. Don't give up. Once you are done, you can connect it with your phone or whatever device.
Make sure to turn on Bluetooth on your phone, and you should be able to see the device (if not play with the bluetooth settings on the watch). Pair the devices, which requires tapping something on both screens.
Most likely, your phone also has an option under "hotspots and tethering" to allow bluetooth sharing of the internet with the watch. Once you enable that, go to the watch, and go to the bluetooth settings where the phone is connected to it, there is options in there for internet sharing with the device over bluetooth (just enable it, it is an on/off toggle).
What did I forget? This is only version 0.01 of this tutorial for you. If you need some more advices, you can write me. I may not check often, but that is life. You can find my email probably from my profile, also.
Dude..... I love you !!!! I thought id never see the gear null rom ever again. Thx bro
Awesome write up made my watch very happy!!
Thanks for all that,
Help
Good post, i have a question, this only work in android 4.3? i have 6.0 and the gear say error connection, thanks and sorry for the bad english
the recovery mode text is so small i cant read it. its stuck at the top portion of the screen. any help? i feel like i wasted money buying this. there is zero support here.
Thank you for this! This is very helpful!
Bad news, though... The Null 23 link isn't being hosted again. Anyone know a valid link to the VALID Null 23 rom?
I need the Null_23.zip too!
tamcswain said:
Thank you for this! This is very helpful!
Bad news, though... The Null 23 link isn't being hosted again. Anyone know a valid link to the VALID Null 23 rom?
Click to expand...
Click to collapse
I have same situation!! That link is not working anymore so i'm waiting the Null_23.zip custom rom for Galaxy Gear 1 which i got it 2 days ago!
Anyone have the Null_23.zip Samsung galaxy Gear's custom rom for share it to us?
Jc Lee said:
I have same situation!! That link is not working anymore so i'm waiting the Null_23.zip custom rom for Galaxy Gear 1 which i got it 2 days ago!
Anyone have the Null_23.zip Samsung galaxy Gear's custom rom for share it to us?
Click to expand...
Click to collapse
If you find something, let me know! I will do the same. I message fOmey (the Null 23 rom creator) and he confirmed he doesn't have it anymore or any links. I also asked to confirm the Null 23 roms on sourceforge.net are incorrect since they are almost 1gb in size and states in the rom installation "i9300" which is the galaxy s III phone.
https://drive.google.com/drive/folders/0B_ka0GfEx6wOMmVfb2tQblJmTmc?usp=sharing
KcajBoy said:
I spent several DAYS getting this watch to work properly (and by properly, I mean rooted and with a new mod).
...
Because I am a new user and can't submit links, this next part is going to SUCK for you:.
Click to expand...
Click to collapse
My gen 1 still works on null 23, but I got a nostalgic kick out of reading your write up. Nice job. Took me back to some good - although often frustrating - days. F0mey did nice to infuse new life back into this classic.
I came to see if anything better was out here since I last visited a good while ago; but not really. Maybe it's time to finally buy something new, and retire this one to a time capsule. (Next to the Casio calculator, $1 g-shock, nelsonic pacman/frogger, stainless mickey mouse, blue gobot/transformer, and gray fighter jet. I wish. Those didn't survive.)
Gear 1 won't connect with Samsung S8
I don't know if I am in the right place but I try and hope you wil tell if I am or not.
My watch Gear 1 always worked with my Samsung S7Edge. No problems. Now I have a Samsung S8 and it won't connect. My Sansung S8 finds my Gear1, but when I have to confirm on my Gear1 it tells me to reset the Gear 1 to its factory settings. It resets, but only starts and I cannot confirm anywhere the number that appeared on the phone. Somebody can help me?
Thanks in advance.
Only acknowledge on phone not on watch
Idebutterpiep said:
I don't know if I am in the right place but I try and hope you wil tell if I am or not.
My watch Gear 1 always worked with my Samsung S7Edge. No problems. Now I have a Samsung S8 and it won't connect. My Sansung S8 finds my Gear1, but when I have to confirm on my Gear1 it tells me to reset the Gear 1 to its factory settings. It resets, but only starts and I cannot confirm anywhere the number that appeared on the phone. Somebody can help me?
Thanks in advance.
Click to expand...
Click to collapse
You just have to acknowledge on the phone not on the watch. Just had that issue with an old S3
Battery life is terrible in null did that last year and went back to tizen
Sent from my SM-G950F using Tapatalk
A very Simple Trick - access debug mode without phone
Great guide, feels like im getting somewhere now. Slightly easier way of accessing Samsung Gear without pairing with another phone is to- On the install Samsung Gear screen(on your watch) try tapping 10-15 times on the white gear watch picture on the top left. This will bring up some message at the bottom about 'bluetooth 3 second press' whereafter you long press for 3 seconds on same picture. Watch is unlocked much easier than 'making love' and swiping up and down to get into settings haha
One question though. After installing stock rom should my software version not change in gear information settings?It seems that I am having trouble with 100% correct drivers because wondershare cant connect to my device, although it shows up in my file explorer is official latest samsung drivers fine or should i download fastboot drivers?. (any reliable links to stock rom,recovery,usb drivers and custom rom would be greatly appreciated,feels like im having trouble with the correct zip files)
I had a hard time getting all the files together so I have made a zip up and it has every file you need,even the firmware V700XXUAMK7,I added that cos on the Samsung Firmware website on slow download it took me 2 hours to download it and it like only 411 mb.
Super SU v2.85 in it there and works fine ,use Impactor_0.9.14,run Impactor.exe and click start and wait for it to finish then connect using Wondershare MobileGo and install the supersu-2-82.apk,Google play on Wondershare MobileGo don't work cos it can't find the device cos Google Play is not on the Gear 1 ,click on supersu app on the Gear 1 and it will ask you to update root files,just click on normal and it will update it and done,you have root on Gear1 now..
Here is the files in a zip.. Hope this helps sommeone,it would of helped me.. its on Mega.. here https://mega.nz/#!sAxinCDa!GR47wt4cQ6g74Ya_9An0bfmf2mel1o8dV0sNiqK3A6M
spannernick said:
I had a hard time getting all the files together so I have made a zip up and it has every file you need,even the firmware V700XXUAMK7,I added that cos on the Samsung Firmware website on slow download it took me 2 hours to download it and it like only 411 mb.
Super SU v2.85 in it there and works fine ,use Impactor_0.9.14,run Impactor.exe and click start and wait for it to finish then connect using Wondershare MobileGo and install the supersu-2-82.apk,Google play on Wondershare MobileGo don't work cos it can't find the device cos Google Play is not on the Gear 1 ,click on supersu app on the Gear 1 and it will ask you to update root files,just click on normal and it will update it and done,you have root on Gear1 now..
Here is the files in a zip.. Hope this helps sommeone,it would of helped me.. its on Mega.. here https://mega.nz/#!sAxinCDa!GR47wt4cQ6g74Ya_9An0bfmf2mel1o8dV0sNiqK3A6M
Click to expand...
Click to collapse
Is not available anymore
Related
i have trying to sync my gear with my note 10.1 2014 but the gears stay in paring mode and when i try to connect with bluethoot it's disconnect after 2-3 sec... i reboot the gear and she stay always in the pairing mode ( in the screen i see a phone who touch the gears case in NFC ) and i can do nothing, my only other solution is wainting to have 4.3 in my canadian S4 for open the gears manager to exit this mode ???
nicgsxr said:
i have trying to sync my gear with my note 10.1 2014 but the gears stay in paring mode and when i try to connect with bluethoot it's disconnect after 2-3 sec... i reboot the gear and she stay always in the pairing mode ( in the screen i see a phone who touch the gears case in NFC ) and i can do nothing, my only other solution is wainting to have 4.3 in my canadian S4 for open the gears manager to exit this mode ???
Click to expand...
Click to collapse
Make sure you have both GearManager 1.4 installed and the stub. Apk (check this forum for the stub app). After you've tried once, check /sdcard/gear/ for any .apks and install them. When you try to pair, if you don't see a prompt on your device, hit home and check notifications for a pairing prompt then if you have to approve that way, go right back to Gear Manager using task switcher (don't launch from main shortcut).
I'm available tomorrow during the day to assist via TeamViewer if you'd like. I'm almost done with my tutorial that should work with any device running >4.2 and working BT4.0. It will include files too. Just trying to get weather working first.
Running PACman (Paranoid Android [Cyanogen Mod]) on Galaxy S4.
rainabba said:
Make sure you have both GearManager 1.4 installed and the stub. Apk (check this forum for the stub app). After you've tried once, check /sdcard/gear/ for any .apks and install them. When you try to pair, if you don't see a prompt on your device, hit home and check notifications for a pairing prompt then if you have to approve that way, go right back to Gear Manager using task switcher (don't launch from main shortcut).
I'm available tomorrow during the day to assist via TeamViewer if you'd like. I'm almost done with my tutorial that should work with any device running >4.2 and working BT4.0. It will include files too. Just trying to get weather working first.
Running PACman (Paranoid Android [Cyanogen Mod]) on Galaxy S4.
Click to expand...
Click to collapse
for pairing with my S4 or my note 10.1 2014 ?
if you can me a stepb by step clear to translate in french ahahah
i have a s4 no root with 4.2
and note 10.1 2014
i waiting for the 4.3 update this month with bell canadian
I had this problem yesterday. Reflashing via Odin was the only way I could resolve it.
Mi|enko said:
I had this problem yesterday. Reflashing via Odin was the only way I could resolve it.
Click to expand...
Click to collapse
what i need exactly and where i find it to make it, it's a galaxy gear canadian i dont know if it change something for the flash ??
i want use them before i have my update on my S4
can you make me little how to ???
nicgsxr said:
what i need exactly and where i find it to make it, it's a galaxy gear canadian i dont know if it change something for the flash ??
i want use them before i have my update on my S4
can you make me little how to ???
Click to expand...
Click to collapse
I'm in the US and flashed the UK version for myself. What do you need to know? Grab the FW you need from the FW thread and then follow the instructions to flash in the "rooting" thread (follow the steps to unroot/recover).
Hi,
I got my Galaxy Gear. I have a Galaxy Nexus, but I found I cannot pair it with the gear. So the gear has never been paired with a phone.
Can I put a new ROM on it? Will it ask for pairing again after I put a new ROM on?
Or do I need to find someone to at least remove the annoying pairing request?
Best
Tom
Have you tried manually syncing it by going to the phone's bluetooth setting and syncing it there instead of using the Gear cradle against the back of the phone?
Ian B
I wonder if manually install the Gear manager on your phone if that will give you the functions. It should connect to Bluetooth fine.
That did not work. I installed apk from gear manager one by one (except the ones that didn't install), started gear manager and tried to pair manually. Galaxy Nexus indicated a paired gear device, but syncing did not work. So it was back to start..
http://forum.xda-developers.com/showthread.php?t=2539082
Here is a link to making it happen
OK, thank you. Will try that and report.
datomm said:
OK, thank you. Will try that and report.
Click to expand...
Click to collapse
try this link it works
http://forum.xda-developers.com/showthread.php?t=2540627&highlight=cradle
Suter argimpr
Sorry, I did not understand.
How does writing the NFC tag help?
Also, I tried to flash the new MK7 rom with odin but after I brought the watch into download mode and started odin, selected firmware and clicked start, odin quickly returns and reports "succeed 0/ failed 0".
datomm said:
Sorry, I did not understand.
How does writing the NFC tag help?
Also, I tried to flash the new MK7 rom with odin but after I brought the watch into download mode and started odin, selected firmware and clicked start, odin quickly returns and reports "succeed 0/ failed 0".
Click to expand...
Click to collapse
i had the same problem. i had s4 and new gear but upon using the cradle it always show faile. so i connect it manually then after succesful connection. i used the witer. and disconnect the gear. connect to new gear. then it works.
maybe the cradle dont have yet the id of the gear that why the writer has been release.
it works for me.
datomm said:
OK, thank you. Will try that and report.
Click to expand...
Click to collapse
After a lot of trying, I finally managed to install the NULL_13 rom on the gear.
The last step of flashing the rom in recovery mode was especially difficult, since windows suddenly did
not recognize the watch like before, but only a Samung Android device and the driver did not work.
I had to switch to MacOS to use "adb push ..". That worked.
Thanks for all the hints.
Hi !
I'm running into an issue here.
After trying to install Null_27 on the gear, then let letting it reboot, i was sent back to download mode. I can access the screen where you choose between "continue" "download" and "recovery". The later works just fine (TWRP2.7, if i got it right) with the fancy slinding lock and such, but selecting "continue" or "download", or rebooting without interruption just lead to the same "Downloading... Do not turn off target" screen.
The gear isn't seen by the phone (Note 3), and my computer doesn't seems to know what this is : Kies3 tries to connect, but finally give up, WonderShare recognize it as a LGE Nexus 4 while in recovery mode, GT-S5690 in download mode, and fails when trying to update drivers.
Window make a weird bleep when plugging it, and Odin doesn't even see it.
I followed theunlockr and xperiahtcrootingrom tutorials. I had to do a step involving a few minimal_adb_fastboot commands found at forum-generationmobiles.net/t73015-recoverysm-v700-null_-twrp-recovery-v03-gear-edition-mk7-beta-22122013" at some point, but globally everything worked out fine (i was able to install and play Fruit Ninja and a random flappy bird clone, that was cool, i should have stopped there) before trying to install Null.
The file is Null_27, and seemed to install flawlessly, but the last log line reads "assert failed : write_raw_image("/tmp/boot.img"."/dev/block/mmcblk0p5").
It might be useful to know that I said yes when prompted to wipe things before install.
So i'm basically stuck without an OS to load (I believe), but failing to install a new, or communicate with my computer. Is there anything I can do to make the install succed, or turn the watch back to its useless stock state ?
I'm willing to provide any useful piece of information, and can browse the files to see exactly what's gone, if someone guides me.
You can guess i don't have much knowledge about coding and such, so please keep it as simple as possible !
Thank you for reading, and please forgive my grammar, i'm not a native speaker.
i have the exact same problem
i'm normally pretty good with rooting my devices but i did something tonite that i cannot figure out. i have done the same thing as the original poster and am at a total loss. please if anyone has any advice please help.
thanks.
Mnddbbl said:
Hi !
I'm running into an issue here.
After trying to install Null_27 on the gear, then let letting it reboot, i was sent back to download mode. I can access the screen where you choose between "continue" "download" and "recovery". The later works just fine (TWRP2.7, if i got it right) with the fancy slinding lock and such, but selecting "continue" or "download", or rebooting without interruption just lead to the same "Downloading... Do not turn off target" screen.
The gear isn't seen by the phone (Note 3), and my computer doesn't seems to know what this is : Kies3 tries to connect, but finally give up, WonderShare recognize it as a LGE Nexus 4 while in recovery mode, GT-S5690 in download mode, and fails when trying to update drivers.
Window make a weird bleep when plugging it, and Odin doesn't even see it.
I followed theunlockr and xperiahtcrootingrom tutorials. I had to do a step involving a few minimal_adb_fastboot commands found at forum-generationmobiles.net/t73015-recoverysm-v700-null_-twrp-recovery-v03-gear-edition-mk7-beta-22122013" at some point, but globally everything worked out fine (i was able to install and play Fruit Ninja and a random flappy bird clone, that was cool, i should have stopped there) before trying to install Null.
The file is Null_27, and seemed to install flawlessly, but the last log line reads "assert failed : write_raw_image("/tmp/boot.img"."/dev/block/mmcblk0p5").
It might be useful to know that I said yes when prompted to wipe things before install.
So i'm basically stuck without an OS to load (I believe), but failing to install a new, or communicate with my computer. Is there anything I can do to make the install succed, or turn the watch back to its useless stock state ?
I'm willing to provide any useful piece of information, and can browse the files to see exactly what's gone, if someone guides me.
You can guess i don't have much knowledge about coding and such, so please keep it as simple as possible !
Thank you for reading, and please forgive my grammar, i'm not a native speaker.
Click to expand...
Click to collapse
---------- Post added at 05:48 AM ---------- Previous post was at 05:11 AM ----------
i was able to download a original firmware for the galaxy gear and used odin to get it back to the orignal state. sucks i lost all the work i put in tonite but at least my watch is working again. i'll mess around more tomorrow and try and get null 27 to work. hope this helps you
Null_22.1 is the latest
That null27 is an old test firmware (more than 6mths old)
Just get the latest from the website: http://nullproject.net/
Check the tutorial threads here on how to fix
No os fix: flash stock firmware (suggest mk7, then start again with root, twrp, null)
Did you fix your issue??
gtrain16 said:
i'm normally pretty good with rooting my devices but i did something tonite that i cannot figure out. i have done the same thing as the original poster and am at a total loss. please if anyone has any advice please help.
thanks.
---------- Post added at 05:48 AM ---------- Previous post was at 05:11 AM ----------
i was able to download a original firmware for the galaxy gear and used odin to get it back to the orignal state. sucks i lost all the work i put in tonite but at least my watch is working again. i'll mess around more tomorrow and try and get null 27 to work. hope this helps you
Click to expand...
Click to collapse
I'm having the same problem. I've gone back to stock ROM via Odin, but I can't get null ROM to work. If you solved your issue, please let me know how.
Thanks,
Josh
stuck in download mode
gtrain16 said:
i'm normally pretty good with rooting my devices but i did something tonite that i cannot figure out. i have done the same thing as the original poster and am at a total loss. please if anyone has any advice please help.
thanks.
---------- Post added at 05:48 AM ---------- Previous post was at 05:11 AM ----------
i was able to download a original firmware for the galaxy gear and used odin to get it back to the orignal state. sucks i lost all the work i put in tonite but at least my watch is working again. i'll mess around more tomorrow and try and get null 27 to work. hope this helps you
Click to expand...
Click to collapse
Can you explain how you did it?
same problem
having same problem as above, where do i find the mk7 file .md5 since only thing i think i can do is run that with odin correct. as null 27 does not load.
stuck null 27 after reboot issue
mmerculieff said:
having same problem as above, where do i find the mk7 file .md5 since only thing i think i can do is run that with odin correct. as null 27 does not load.
Click to expand...
Click to collapse
hi guys
I installed null 0.27 then in the end of process the statement was assert failed write raw image /tmp/boot.img
/dev/block/mmcblk0p5 I clicked next and reboot it stucks in download mode for while?
null27 seems to crash my gear
I reinstalled null23 it works ...
thecliq said:
Can you explain how you did it?
Click to expand...
Click to collapse
mmerculieff said:
having same problem as above, where do i find the mk7 file .md5 since only thing i think i can do is run that with odin correct. as null 27 does not load.
Click to expand...
Click to collapse
proslash said:
hi guys
I installed null 0.27 then in the end of process the statement was assert failed write raw image /tmp/boot.img
/dev/block/mmcblk0p5 I clicked next and reboot it stucks in download mode for while?
null27 seems to crash my gear
I reinstalled null23 it works ...
Click to expand...
Click to collapse
null 23 is latest. null 27 is very old
null 23
gtrain16 said:
i'm normally pretty good with rooting my devices but i did something tonite that i cannot figure out. i have done the same thing as the original poster and am at a total loss. please if anyone has any advice please help.
thanks.
---------- Post added at 05:48 AM ---------- Previous post was at 05:11 AM ----------
i was able to download a original firmware for the galaxy gear and used odin to get it back to the orignal state. sucks i lost all the work i put in tonite but at least my watch is working again. i'll mess around more tomorrow and try and get null 27 to work. hope this helps you
Click to expand...
Click to collapse
How can I fix my Samsung gear watch from downloading mode please
azizurali12 said:
How can I fix my Samsung gear watch from downloading mode please
Click to expand...
Click to collapse
Check the thread about tizen downgrade... If you follow it you will have your watch up again.
Mnddbbl said:
Hi !
I'm running into an issue here.
After trying to install Null_27 on the gear, then let letting it reboot, i was sent back to download mode. I can access the screen where you choose between "continue" "download" and "recovery". The later works just fine (TWRP2.7, if i got it right) with the fancy slinding lock and such, but selecting "continue" or "download", or rebooting without interruption just lead to the same "Downloading... Do not turn off target" screen.
The gear isn't seen by the phone (Note 3), and my computer doesn't seems to know what this is : Kies3 tries to connect, but finally give up, WonderShare recognize it as a LGE Nexus 4 while in recovery mode, GT-S5690 in download mode, and fails when trying to update drivers.
Window make a weird bleep when plugging it, and Odin doesn't even see it.
I followed theunlockr and xperiahtcrootingrom tutorials. I had to do a step involving a few minimal_adb_fastboot commands found at forum-generationmobiles.net/t73015-recoverysm-v700-null_-twrp-recovery-v03-gear-edition-mk7-beta-22122013" at some point, but globally everything worked out fine (i was able to install and play Fruit Ninja and a random flappy bird clone, that was cool, i should have stopped there) before trying to install Null.
The file is Null_27, and seemed to install flawlessly, but the last log line reads "assert failed : write_raw_image("/tmp/boot.img"."/dev/block/mmcblk0p5").
It might be useful to know that I said yes when prompted to wipe things before install.
So i'm basically stuck without an OS to load (I believe), but failing to install a new, or communicate with my computer. Is there anything I can do to make the install succed, or turn the watch back to its useless stock state ?
I'm willing to provide any useful piece of information, and can browse the files to see exactly what's gone, if someone guides me.
You can guess i don't have much knowledge about coding and such, so please keep it as simple as possible !
Thank you for reading, and please forgive my grammar, i'm not a native speaker.
Click to expand...
Click to collapse
Search YouTube file that trasfer files to non os android device (sorry new user cannot post link)
Please See this Videos might Help
Without Have to flash old stock firmwire
Just copy null 23 to gear
And install it..
Hope hellps
BUMP
husaini_ said:
Search YouTube file that trasfer files to non os android device (sorry new user cannot post link)
Please See this Videos might Help
Without Have to flash old stock firmwire
Just copy null 23 to gear
And install it..
Hope hellps
Click to expand...
Click to collapse
Hi, so how to install that rom, I always getting stuck on download mode after successful install rom from TWRP. old thing but no solutions??
Well
Your problem is that you are flashing the wrong rom. Check my post elsewhere, I made a thread explaining how to root the Gear and everything to get Null on there.
The Null rom available from Sourcefroge, F0mey's page, is NOT FOR GALAXY GEAR WATCHES.
Finding the actual rom is very difficult, but if you read my thread, there is a link in there.
Ok i will explain clearly
what i did...
Firstly i tried to follow all videos to root custom my galaxy gear when the first hour when i bought,
i was succesfull. I installed null 23 i root it and then i upload null 23 in my sd card part in my gear with the wondershare mobile go application.
Then i didnt like it and i tried to unroot my gear. And i followed the steps correctly. But..
Activation screen which is connecting with nfc or bluetooth, never let me pass. Even i tried to do nfc, it says try to bluetooth and bluetootg couldnt connect. But they see eachother
and also when i try to root again, odi says success but nothing happening on my screen after i root it.
And now wondershare doesnt work because i am not able to reach usb debug mode settings on my gear. Because i couldnt pass connection screen on gear.
Now i really f....d up
please help me almost 20 times i tried to root and unroot.
I just want my gear as like as first minute of my device.
Please help me asap
thanks...
Try flash stock rom via odin and start again
i tried many times... i found the file name is V700XXUBNA6_V700OXABNA6_HOME.tar
Brendo said:
Try flash stock rom via odin and start again
Click to expand...
Click to collapse
tried hundred times (
i downloaded UK stock rom tried. and nothing happened. like just i restart the device.
it doesnt effect anything
i tried to XAR version
again it is coming the same screen which is connect the bluetooth
but it is unsuccesfull
MAIN PROBLEM IS
THE DEVICE DOESNT ACCEPT THE ROMS
JUST KEEPING THE SAME THING INSIDE.
http://forum.xda-developers.com/showpost.php?p=48323895&postcount=2
Also try clearing cache and data for gear manager, uninstall, reboot, reinstall
Found my fire tablet with a black screen and in Amazon system recovery <3e> this morning - not sure how it got into that state & how to get out of it. To my knowledge I didn't press any combination of keys that would get me into that state. It had been only very low battery when I plugged it into the electrical socket last night but I didn't touch it until the morning when I found it in this black screen state.
From searching I think this is the Amazon version of Android System Recovery screen. The exact options are:
-------
Amazon system recovery <3>
Volume up/down to move highlight;
enter button to select.
reboot system now
apply update from ADB
wipe data/factory reset
wipe cache partition
reboot to bootloader
power down
view recovery logs
----------
I haven't rooted the tablet although I did apply the "Installing Google Framework/Playstore without Root (5th Gen Amazon Fire 2015)"
(http://forum.xda-developers.com/amazon-fire/general/installing-google-framework-playstore-t3216122)
I've had it for about a month without problems although a couple of days ago it kept trying to update several times in succession.
It has attempted to update a couple of times in the past, which put me into a panic at the time but when I'd check afterwards it would still show 5.0.1. firmware. Also the difference this time was that in the past it would only attempt to update the once, not several times in succession.
I'd assumed that installing "Installing Google Framework/Playstore without Root (5th Gen Amazon Fire 2015)" doesn't stop the fire downloading updates but prevents them being installed. So when it happened in the past I didn't worry.
I'm not sure what to do (logically I'd assume I should just select the 1st option and reboot) but I'm not sure how I even got into this screen and if there's a reason for it so hoped someone might be able to advise me.
With thanks & crossed fingers
Frankie
Sorry - one other question!
Which key is the "enter button"?
FrankieChen said:
Sorry - one other question!
Which key is the "enter button"?
Click to expand...
Click to collapse
I've not used it but as we only have three buttons I'm going with the power button.
Pond-life said:
I've not used it but as we only have three buttons I'm going with the power button.
Click to expand...
Click to collapse
That's what I suspected!
Update
Well I ran out of power so the tablet switched off.
When I plugged it into an electricity socket, I decided to try the "reboot system now" option but it just rebooted and cam back to the same screen. I tried it about 4 times with the same result so I tried the "power down" option but it still returned to the same screen when switched back on.
Would really appreciate anyone's help.
Hmm, is there anything in the recovery logs?
Maybe reboot to bootloader, and see if it'll let you twrp to it from a pc, head to the twrp thread and grab the files.
fastboot boot TWRP_Fire_2.8.7.0.img
If it'll do that it's not on 5.1.1 at least, if not it might have tried to get there.
I haven't followed your instructions yet as after I posted last, it started to flash an error message along the lines of battery was too low to "factory reset" and something else - I don't recall what though. I didn't actually select any options apart from reboot and power down.
It was plugged in at the time but I unplugged it & replugged it in, in case for some reason it wasn't charging.
Since then the error message has stopped flashing and I just have a blank screen although you can see it is backlit. Pressing the power button has no effect
And that's on the charger it came with?
It's not looking good.
FrankieChen said:
...I haven't rooted the tablet although I did apply the "Installing Google Framework/Playstore...
...I'd assumed that installing "Installing Google Framework/Playstore without Root (5th Gen Amazon Fire 2015)" doesn't stop the fire downloading updates but prevents them being installed....
Click to expand...
Click to collapse
I know this doesn't help your current situation, but just FYI, neither root nor google framework have anything to do with OTA updates. Only hiding/disabling/deleting the OTA related apks will prevent updates.
julianpaul said:
I know this doesn't help your current situation, but just FYI, neither root nor google framework have anything to do with OTA updates. Only hiding/disabling/deleting the OTA related apks will prevent updates.
Click to expand...
Click to collapse
True but the thread he's referring to does offer that function as an option in the batch file.
http://forum.xda-developers.com/amazon-fire/general/installing-google-framework-playstore-t3216122
Tomsgt has put together a little install bat (Amazon-Fire-5th-Gen-Install-Play-Store.zip)
Now includes Removing Advertising and Blocks Over the Air System Updates (02 Nov 2015)
Click to expand...
Click to collapse
julianpaul said:
I know this doesn't help your current situation, but just FYI, neither root nor google framework have anything to do with OTA updates. Only hiding/disabling/deleting the OTA related apks will prevent updates.
Click to expand...
Click to collapse
It's still useful information - thanks
It's on the charger it came with and it has finally returned to the same Amazon system recovery screen.
In regards to preventing the updates - I think I did that when I installed the google apps but it was the 1st time i ever did this (it's my 1st tablet), and as it was over a month ago I can't be sure - this is all very new to me.
There are 4 recovery logs, completely meaningless to me.
/cache/recovery/last_kmsg
/cache/recovery/last_log
/cache/recovery/last_log1
/cache/recovery/last_log2
the kmsg log zooms past too fast to read with endless pages dealing with "swapper/0"
the last_log seems to have stuff reffering to tzdata, build, product.cpu, ro.product, dalvik and so on . Log1 and log2 seem to be similar stuff but shorter.
Any idea what I should be looking for?
I hoped it would be readable, build number might yield clues.
Given it will show something seems worth trying to see if twrp can see it in bootloader.
It may not have any thing to do with the updates as it was working after the updates had tried to install though I have to admit I only used it for a few minutes and I didn't check it before I plugged it in to charge the night before I found the black screen.
I don't actually have a clue what you mean when you say "twrp can see it in bootloader." so I will have to spend some time reading the forums to figure out what to do.
In desperation this morning I took the wipe data/factory reset option but it didn't work. It returned with the same screen and the error message
E:Error in /cache/recovery/dropbox_last_kmsg (Read-only file system)
I had installed the dropbox app but I had never actually signed in so there wouldn't be any data there.
After rebooting and being returned to the same screen, I attempted again to wipe data/factory reset.
This time it gave the message "data wipe complete" but still returned to the Recovery screen.
I've read the term "bricked" in several of the forums - is this what has happened to my device?
I wondered if I should contact Amazon about it as it's still under warranty but wondered if by installing gapps (and most likely having prevented updates as I followed all the instructions), whether I'd have invalidated my warranty.
FrankieChen said:
After rebooting and being returned to the same screen, I attempted again to wipe data/factory reset.
This time it gave the message "data wipe complete" but still returned to the Recovery screen.
I've read the term "bricked" in several of the forums - is this what has happened to my device?
I wondered if I should contact Amazon about it as it's still under warranty but wondered if by installing gapps (and most likely having prevented updates as I followed all the instructions), whether I'd have invalidated my warranty.
Click to expand...
Click to collapse
At this point, if you have adb drivers (or are comfortable installing them) you may as well try sideloading an update bin file. Links are here. I'd get the 3820 file.
If you want to do this, post back and I or someone will give you the steps. Otherwise, Amazon has been good about replacing tablets if you just describe what you say in the 1st paragraph of your post.
FrankieChen said:
It may not have any thing to do with the updates as it was working after the updates had tried to install though I have to admit I only used it for a few minutes and I didn't check it before I plugged it in to charge the night before I found the black screen.
I don't actually have a clue what you mean when you say "twrp can see it in bootloader." so I will have to spend some time reading the forums to figure out what to do.
Click to expand...
Click to collapse
use the reboot to bootloader option
set pc up with fastboot and see if it can be booted into twrp by fastboot
http://forum.xda-developers.com/showpost.php?p=63635664&postcount=9
http://forum.xda-developers.com/amazon-fire/orig-development/twrp-recovery-t3242548
Thank you for the replies. Sorry not to have responded earlier, I had a busy few days and although I have spent a lot of hours trying to read through the forums and find out about twrp, this is the 1st opportunity I have had to get back to trying to resolve the problem.
If I understand correctly, DoLooper has suggested sideloading an update bin file. (3820). I just started trying to do this but as the file to be downloaded is over 600MB and I am on a very slow connection it's showing it's going to take between 7-8 hours to download. If I take this option I will need to wait until tomorrow when I can get to a faster internet.
Pond-life, you have suggested that I
1. "use the reboot to bootloader option"
I'm presuming that this means that I have to select this option from the recovery screen on the tablet - does the tablet have to be attached to the pc via the USB cable when I select the option?
What should I expect once I have selected this option?
Would the tablet not need to be rooted to access the bootloader (as it isn't)?
2. "set pc up with fastboot and see if it can be booted into twrp by fastboot"
When I 1st got the tablet I had difficulties getting the adb drivers to install on my pc and after several days of trying I ended up doing it on another pc which I no longer have access to.
I have tried again to reinstall the drivers using rootjunkies file but again without success. I tried doing it using that method as I remember trying to do it that way (what felt like a billion times) though I don't remember if I finally ended up succeeding with that method or another.
I followed your link "http://forum.xda-developers.com/showpost.php?p=63635664&postcount=9" and tried the 1st method
"[TOOL] [WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3 by Snoop05"
running the "adb-setup-1.4.3.exe" I get "0 files copied" after selecting "Yes to install ADB system-wide" which I recall was the problem (zero files copied) that I had previously.
Openning Device Manager after this does show any Fire or Android devices even when the tablet is connected so I'm assuming that the adb driver installation is failing.
I tried again with "adb-setup-1.3.exe". This time I had 4 files copied and got fire listed in the device manager but when I tried to update the driver I am not given the Android option in the list when I select the option to install driver.
I googled to see if anyone else had this error and I found that some peoplehad difficulties installing on XP but seems that MTP not being supported is the reason and it is resolved by installing WMP v10 and above. I have v11 so presume that's not the problem.
I don't have access to another computer at the moment to try and install the adb drivers but should be able to use another one tomorrow. Last time when I got the drivers to install it was on a vista machine so I wondered if that might have something to do with it.
The other thing that occurred to me was maybe there is something wrong with the cable as I only get the fire shown in the device manager for a few moments before it refreshes and then the fire is no longer shown.
I wondered if I should try to use USBDeview (as per http://www.inlovewithandroid.com/android-usb-connection-problems.html) to see if that is the problem. Certainly if I can the drivers installed on another pc it might suggest that there's a problem with mine.
Anyway, if I get the adb drivers to install successfully on another pc, could you explain what I am trying to do by "booted into twrp by fastboot"? Sorry to be so useless!
Huge thanks
Yeah the files needed will all be pretty hefty. So if thinking about going to a custom rom this would be a good time. Though wouldn't download one or the stock until you've seen if you can use it.
1. Yeah I did mean choose that option on that menu you have onscreen. Doesn't need to be attached to go to the screen technically, but won't be able to do anything there until it is connected so no benefit in not waiting until you are. No doesn't need to be rooted. You'd expect it to go to an almost blank screen with =>FASTBOOT mode.... on it in landscape.
2. On plus side you wouldn't need the adb drivers... But the fastboot ones are probably similarly tricky. These ones worked for me https://developer.amazon.com/appsan...etting-up-your-kindle-fire-tablet-for-testing
Though I've not used XP.
If it will fastboot into twrp then you can put the original stock rom on or either of the custom ones from there, so it's not dead and can get to downloading. (or 5.1.1 stock using the safe twrp method)
Did you use a different cable on the machine you got it to work on then? If not probably not the cable.
Pond-life said:
Yeah the files needed will all be pretty hefty. So if thinking about going to a custom rom this would be a good time. Though wouldn't download one or the stock until you've seen if you can use it.
1. Yeah I did mean choose that option on that menu you have onscreen. Doesn't need to be attached to go to the screen technically, but won't be able to do anything there until it is connected so no benefit in not waiting until you are. No doesn't need to be rooted. You'd expect it to go to an almost blank screen with =>FASTBOOT mode.... on it in landscape.
2. On plus side you wouldn't need the adb drivers... But the fastboot ones are probably similarly tricky. These ones worked for me https://developer.amazon.com/appsan...etting-up-your-kindle-fire-tablet-for-testing
Though I've not used XP.
If it will fastboot into twrp then you can put the original stock rom on or either of the custom ones from there, so it's not dead and can get to downloading. (or 5.1.1 stock using the safe twrp method)
Did you use a different cable on the machine you got it to work on then? If not probably not the cable.
Click to expand...
Click to collapse
Thanks for all your help Pond Life.
I had such difficulties get the files to download that in the end I gave up and rang Amazon and they offered to send me a replacement.
Sorry to bail out, this is all new to me and most of what everyone has said has me completely baffled so I've decided to take the easy way out.
Thank you again - I really appreciated all your advice.
FrankieChen said:
Thanks for all your help Pond Life.
I had such difficulties get the files to download that in the end I gave up and rang Amazon and they offered to send me a replacement.
Sorry to bail out, this is all new to me and most of what everyone has said has me completely baffled so I've decided to take the easy way out.
Thank you again - I really appreciated all your advice.
Click to expand...
Click to collapse
Better luck with the new one