Related
I might ruined my defy+
When I bought it, it was in German, i changed it to dutch and had android 2.3.6
Flashed it with the all-in-one Defy beginners guide
Had a working android version afterwards, only calling/sms/2g and 3g didn't work. Didn't try to fix it because i wanted to flash the latest cm7.2.
Don't know what i did after that (afterwards we went to carnaval, so i drank to much). I know I installed a uk rom 2.3.6 version and here it went wrong. It went into a bootloop. Got the M logo and spinning white thing around. Tried installing differnt roms, none worked. And now my phone doesnt do anything, wont start or go in to bootloader. RDS light find it but white led wont go on.
IMEI/ESN/MEID: N / A
Technology: N / A
Software Version: N / A
Flex Version: N / A
Bootloader Version: v0x000910
DRM Version: N / A
AP Die ID: 1040020f1fab3a0a0000d8ff0100
BP Die ID: 0000000000000000000000000000
AP Public ID: 9aff8fe986ef65565a0a1e805942bbeaa8460f87
BP Public ID: 0000000000000000000000000000000000000000
Tried different roms, didn't work. Tried the following
"Common Problems/Questions
Black Screens when booting up: (!) Tried to install a version of Android with a lower CG Version than the one currently on the phone.
Weird behavior after installing a Fixed SBF: Install a matching Nandroid backup with your SBF, and remember to clear Cache/Dalvik Cache using Recovery.
Installed full Gingerbread SBF and can’t go back to another rom: (!) aha! We have a issue here!, latest Stock Gingerbread full SBFs comes with a Version 5 of the CG, meaning until not long ago you were pretty much screwed. But wait, there is hope! A one kind Éclair has been found in China Defys that comes with Version 5 CG!.
How to fix it:
Download this SBF and Flash it
Root your Phone
Download 2nd Init 1.4.2 and Install ClockworkMod Recovery
Download and install this Nandroid Backupwent wrong here, multiupload is gone so couldnt continue
Enter Recovery, Wipe Data/Cache
After wiping, turn off your phone
Turn it on and get immediately into Bootloader mode
Flash this Fixed SBF
Delete Data/Cache again and reboot"
Anyone got a answer for this? I am searching this forum for over 6 hours in the last days.
Mate, when you say it doesn't start... Nothing happens when you hold the power button? Not even the M logo (bootscreen) shows up?
Can you access stock recovery? When your phone is off, press and hold Volume UP button and power button. Does anything happen?
When you enter the bootloader, what does it say? Please write everything down.
I'm 99% sure that your phone isn't dead, you've just flashed some wrong stuff. First of all, CM7.2 is not compatible with 2.3.6. There is a CM7.2 DEFY+ version, but it works with 2.3.4 only. If you used a normal defy CM7.2, it's for Froyo only. Anyway, whatever version you used, it's not strange that it wasn't successful.
P.S I've done the same thing first time I've tried to update to some custom ROM
One more thing. After CM7.2 flashing resulted in a frozen bootscreen (M logo), please write down all the steps you did? It's kinda hard to figure out from that guide you've posted..!
niksy+ said:
Mate, when you say it doesn't start... Nothing happens when you hold the power button? Not even the M logo (bootscreen) shows up? Yes nothing shows, looks like the batt is empty but that isn't the case
Can you access stock recovery? When your phone is off, press and hold Volume UP button and power button. Does anything happen?
No nothing
When you enter the bootloader, what does it say? Please write everything down.
I'm 99% sure that your phone isn't dead, you've just flashed some wrong stuff. First of all, CM7.2 is not compatible with 2.3.6. There is a CM7.2 DEFY+ version, but it works with 2.3.4 only. If you used a normal defy CM7.2, it's for Froyo only. Anyway, whatever version you used, it's not strange that it wasn't successful.
P.S I've done the same thing first time I've tried to update to some custom ROM
One more thing. After CM7.2 flashing resulted in a frozen bootscreen (M logo), please write down all the steps you did? It's kinda hard to figure out from that guide you've posted..!Didn't came to that
Click to expand...
Click to collapse
Do you have a good link witch describes how to go from 2.3.6 to 2.3.4? For when my phone works again.
thank you.
taarmen said:
Do you have a good link witch describes how to go from 2.3.6 to 2.3.4? For when my phone works again.
thank you.
Click to expand...
Click to collapse
Not really, buddy :-/
You should have answered my questions, that way I could have written you a step-by-step guide
What you should do:
0. Phone's off
1. Enter stock recovery
2. Wipe data and wipe cache
3. Turn off phone
4. Enter bootloader
5. Flash full stock 2.3.4 sbf - http://www.mirrorcreator.com/files/1HLS00W4/
6. Your phone should boot up normally after the process is done
If you can not enter stock recovery, then just enter bootloader and flash the sbf. The thing is, those fixed sbf's don't have all the codegroups, so some stuff from CM7.2 has probably remained in your system. Full sbf should do a much better job. But, it would be great if you can enter stock recovery. That way the flashing must be successful.
Note, I haven't tried that 2.3.4 sbf! But it's the only one I could find. I need it too and I will test it tomorrow morning, so if you want, you can wait for me to test it first. (I need it cause my defy+ is on Froyo now, and Froyo and defy+ don't really like each other ) I have tested one 2.3.5 sbf, I can point it to it if you wish so. (It doesn't matter which android version it is, as they all have version 6 signed codegroups, so you can switch between them without worrying! Only some latest 2.3.6 ROM's are signed as version 7, but it's highly unlikely that you have flashed your phone with one such)
I Agree with niksy+, can't help, I have a Green Lens Defy, so all i have to say is good luck, and a step-by-step would have been nice
Thank you for the effort, my defy+ is braindead. When i connect it to my pc the white top led goes on. And that is it, nothing on RSD, wont boot, wont go in the bootloader
There's a trick for that i think i remeber it's:
Plug phone it with rsd ready (the phone should be dead with white led)
Pull battery out and press vol up + down
Put battery back in
It might not be exactly that but i can assure you i read somewhere what to do with your issue
Sent from my 1Ghz CM7 + CM9 Defy
crakeron said:
There's a trick for that i think i remeber it's:
Plug phone it with rsd ready (the phone should be dead with white led)
Pull battery out and press vol up + down
Put battery back in
It might not be exactly that but i can assure you i read somewhere what to do with your issue
Click to expand...
Click to collapse
That process is called "force bootloader method" and it can be done on any and every Motorola, as far as I know..! (I've done it on my previous E398, ROKR E1 and ROKR E8 phones (yeah, I've killed all my phones dozens of times )) and, yes, sometimes it does get you into the bootloader when the normal way doesn't!
So, as crakeron said:
1. Battery out
2. Wait couple of seconds (to make sure the phone goes completely out of power > completely off)
3. Start up RSDlite (v5.3.1 minimum!)
4. Connect your phone to the usb (yes, without the battery)
5. Now, you need to press and hold a combination of buttons and insert the battery WHILE holding the buttons pressed and keep them pressed for couple of seconds.
*I'm not sure what the combination of keys is it, but I would try:
a) Volume UP and Volume Down
b) Volume UP and Power Button
c) Volume Down and Power Button
d) Volume UP and Volume Down and Power Button (this one is the least likely, I think)
6. Your phone should show up in RSDlite and you can flash it then. The bootloader maybe won't show up on the phone screen, but if it shows up in RSDlite - it's all that you need!
This forcebootloader thing isn't quite easy and it may take couple of tries to hit the exact needed timing, so try all combinations a couple of times. Let us know if you pull this off!
i have the popcorn out for this one - fun thread! will the defy be rescued??? tune in next time, same bat board, same bat sub board!
taarmen said:
I know I installed a uk rom 2.3.6 version and here it went wrong. It went into a bootloop. Got the M logo and spinning white thing around. Tried installing differnt roms, none worked. And now my phone doesnt do anything, wont start or go in to bootloader. RDS light find it but white led wont go on.
Click to expand...
Click to collapse
If the UK 2.3.6 ROM you installed was this one then you will not be able to downgrade to any other 2.3.6 ROM (except I think this one), let alone 2.3.5, 2.3.4 or Froyo (it does say that in the thread you linked).
You should still be able to flash either of those 2.3.6 ROMs with RSD Lite. But no other ROM - until some more with CG 7 or above become available - and it's currently not rootable either. So no chance of CM7 or other such like goodies. At least you should be able to get a working phone that you can sell on eBay if you desperately don't want to be stuck with the T-Mobile 2.3.6 ROM.
Morals of the story:
1) Read before you flash
2) Keep a written record of what you did (I know, boring)
Good luck, let us know how you get on.
niksy+ said:
That process is called "force bootloader method" and it can be done on any and every Motorola, as far as I know..! (I've done it on my previous E398, ROKR E1 and ROKR E8 phones (yeah, I've killed all my phones dozens of times )) and, yes, sometimes it does get you into the bootloader when the normal way doesn't!
So, as crakeron said:
1. Battery out
2. Wait couple of seconds (to make sure the phone goes completely out of power > completely off)
3. Start up RSDlite (v5.3.1 minimum!)
4. Connect your phone to the usb (yes, without the battery)
5. Now, you need to press and hold a combination of buttons and insert the battery WHILE holding the buttons pressed and keep them pressed for couple of seconds.
*I'm not sure what the combination of keys is it, but I would try:
a) Volume UP and Volume Down
b) Volume UP and Power Button
c) Volume Down and Power Button
d) Volume UP and Volume Down and Power Button (this one is the least likely, I think)
6. Your phone should show up in RSDlite and you can flash it then. The bootloader maybe won't show up on the phone screen, but if it shows up in RSDlite - it's all that you need!
This forcebootloader thing isn't quite easy and it may take couple of tries to hit the exact needed timing, so try all combinations a couple of times. Let us know if you pull this off!
Click to expand...
Click to collapse
Wel I hope that iolinux333 has enough popcorn because non of the mentioned forced bootloader steps works
When i put my + on the usb nothing happens for a few minutes after that a withe led will shine. Thats all.
Thank you all!
I asked you already on tweakers.net, but I'll ask the same questions here:
What's the status of your battery? (Full, empty, half-full?) What version of RSD-lite did you use? What version of drivers are installed on your computer? How many times did you try the different key combinations after pulling out battery, connecting to your computer? What did you see at each step?
Fotogravin said:
I asked you already on tweakers.net, but I'll ask the same questions here:
What's the status of your battery? (Full, empty, half-full?) What version of RSD-lite did you use? What version of drivers are installed on your computer? How many times did you try the different key combinations after pulling out battery, connecting to your computer? What did you see at each step?
Click to expand...
Click to collapse
Been away for a few days. Back and ready to repair, I appreciate all your help.
no sim and sd-card
win7 64-bit
Battery is Full
RSD Lite version 5.6
motorola 5.4.0 usb drivers 64-bit
Tried all combinations at least 10 times. First I disconnect usb -> take out bat -> make combination and count to ten -> put in bat -> holds for minimum of 10seconds -> click on "show device" on RSD -> Nothing show
Nothing ever shows.
You really should give us more... What happens when you try to power it on? I think you only get black so, does power+vol(+) give you something or do you get a white led when you plug it in the pc?
If yes, it should be recognizable. I don't think you can get into bootloader mode when power-on gives nothing. Maybe by putting the battery back while holding the volume(+) I think and the power button. (like stated earlier) But I thought the white led was enough.
If you don't get the white LED and you only get black screen, maybe try to borrow a battery from someone...
If you get the white LED but RSD doesn't find it: try a few ports, maybe other PC, ....
I also think a Win7 window should pop up first with something like: 'Motorola diag... device found' (or maybe something completely different)
Then I think the easiest = warranty. I'm from Belgium. Had to send it to a repair center in the Netherlands (for a totally different reason) and it took them a while to fix it (it needed to be send elsewhere, .. ).
Just tell them you tried to update your rom and it wend wrong. Anyway, it takes about a month I think...
labsin said:
You really should give us more... What happens when you try to power it on?
Compleet black nothing happens
I think you only get black so, does power+vol(+) give you something
Still nothing
or do you get a white led when you plug it in the pc?
Yes I got that
If yes, it should be recognizable. I don't think you can get into bootloader mode when power-on gives nothing. Maybe by putting the battery back while holding the volume(+) I think and the power button.
Still nothing, not even the white led
(like stated earlier) But I thought the white led was enough.
If you don't get the white LED and you only get black screen, maybe try to borrow a battery from someone...
If you get the white LED but RSD doesn't find it: try a few ports, maybe other PC, ....
Haven't been able to trie different pc's. Tried differt usb ports, even those of my mouse and keyboard so I know they fully function, only white led
I also think a Win7 window should pop up first with something like: 'Motorola diag... device found' (or maybe something completely different)
nothing to show
Then I think the easiest = warranty. I'm from Belgium. Had to send it to a repair center in the Netherlands (for a totally different reason) and it took them a while to fix it (it needed to be send elsewhere, .. ).
Just tell them you tried to update your rom and it wend wrong. Anyway, it takes about a month I think...
Think i got to trie it,what can hapen if they found out i lied?
Click to expand...
Click to collapse
Thank you for helping me, I just tried RSD Lite 5.7 and also nothing.
Sorry a bit late. You didn't lie
I should be recognizable. Especially with a full battery. If not, you might have had a bad install and they might have to replace the botherboard.
If you don't mind waiting a couple of days longer, bring it to the place you bought it. Then the delivery costs are free. But could take 1-2 weeks longer.
IF they do conclude it is your fault then you have to pay an amount of money to deliver it back or you can pay for repairing it (for motherboard could be 80-100 or more, actually don't know). Again when you went trough shop this takes a week or so. (motorola => shop => 3 days nothing => you => 3 days nothing => motorola).
They are not that picky at motorola except for water damage maybe (check for a red sticker below the battery. If it is still white => no prob)
Thank you all. I've sent my phone to the store where i bought it, on friday and the next friday i got it back. With a fresh stock rom.
Hi all,
First off thanks in advance- typically I'm able to come on here and find the answer to my issues without having to post and just using the search functionality.. this time however, I'm stumped.
I am trying to flash the ROM on my phone(I'm having issues w the phone sporadically rebooting every few hours, and sometimes I cant hear or the person on the other line cant hear me either, and the only way to resolve is 3-6 reboots/resets, which can get frustrating), however, I cannot get to download OR recovery mode- the specs are as follows :
SGH-T989
4.1.1
kernel - 3.0.42 Cyanogenmod-g3da3f01
CyanogenMod version - 10.0.0- RCO-hercules
Paranoid Android Version 2.13
Basically, ever since flashing (months ago) if I want the phone to reboot, I have to hold the power button, and let it do that short vibration twice-then let go, then it boots normally. However if I try to use the key shortcuts to boot right into either mode, it boots normal. If I try to open cmrecovery, and select boot into recovery mode, it says ok, locks for a second, then does the equivalent of a hard reset and either reboots normal, or just turns off ( and when i turn back on it boots normally). Does this via the goomanager app as well, same behavior.
I even went as far as to try to use the adb reboot recovery and it sends the command to the phone but ultimately the same thing happens.
Any suggestions? I recall a long time ago reading of some method where you pull the batter w it plugged in via USB but when I do that it just shuts off immediately.
I'm pretty tech savvy(so I think) and most of the time can work through the issue by research and trial and error but this is frustrating.
I'm assuming there's no way to flash the rom without it being IN recovery mode, correct? I should add download mode exhibits the same exact behavior(or lack thereof). Thanks!!!
otownbuckeye said:
Hi all,
First off thanks in advance- typically I'm able to come on here and find the answer to my issues without having to post and just using the search functionality.. this time however, I'm stumped.
I am trying to flash the ROM on my phone(I'm having issues w the phone sporadically rebooting every few hours, and sometimes I cant hear or the person on the other line cant hear me either, and the only way to resolve is 3-6 reboots/resets, which can get frustrating), however, I cannot get to download OR recovery mode- the specs are as follows :
SGH-T989
4.1.1
kernel - 3.0.42 Cyanogenmod-g3da3f01
CyanogenMod version - 10.0.0- RCO-hercules
Paranoid Android Version 2.13
Basically, ever since flashing (months ago) if I want the phone to reboot, I have to hold the power button, and let it do that short vibration twice-then let go, then it boots normally. However if I try to use the key shortcuts to boot right into either mode, it boots normal. If I try to open cmrecovery, and select boot into recovery mode, it says ok, locks for a second, then does the equivalent of a hard reset and either reboots normal, or just turns off ( and when i turn back on it boots normally). Does this via the goomanager app as well, same behavior.
I even went as far as to try to use the adb reboot recovery and it sends the command to the phone but ultimately the same thing happens.
Any suggestions? I recall a long time ago reading of some method where you pull the batter w it plugged in via USB but when I do that it just shuts off immediately.
I'm pretty tech savvy(so I think) and most of the time can work through the issue by research and trial and error but this is frustrating.
I'm assuming there's no way to flash the rom without it being IN recovery mode, correct? I should add download mode exhibits the same exact behavior(or lack thereof). Thanks!!!
Click to expand...
Click to collapse
Hey, didn't see what recovery you were using...Might be a good idea to reflash.. The new TWRP is apparently having issues, but you can try an older version and flash that (You can do this directly from goo.im, but I'd wait until the newest version has the kinks worked our since you can't get into recovery or download mode)
smokinjoe2122 said:
Hey, didn't see what recovery you were using...Might be a good idea to reflash.. The new TWRP is apparently having issues, but you can try an older version and flash that (You can do this directly from goo.im, but I'd wait until the newest version has the kinks worked our since you can't get into recovery or download mode)
Click to expand...
Click to collapse
I tried from both goo.im(which I believe is TWRP) and CMRecovery... same results with both. I'm a bit at a loss. help!! lol
otownbuckeye said:
I tried from both goo.im(which I believe is TWRP) and CMRecovery... same results with both. I'm a bit at a loss. help!! lol
Click to expand...
Click to collapse
I would, at that point, get fed up and just go back to stock and reroot from scratch.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Hi,
I don't know if it's a proper place for this, so sorry if not.
I have (or had) android tablet "Scroll Engage" from storageoptions.com. It was slow as hell so i decied to put there cyanogenmod. I couldn't find dedicated one, so i've try with the rom here: http://forum.xda-developers.com/showthread.php?t=1821398
The rom itself installed without the problems, but after booting it the touchpad was not working ... so i've decied to try patches from same site... i don't have much knowledge about android, so i started to check one after another .... and at some point one of them replace gpu drivers with the wrong one, and after couple more boot was overwrited ... so now i can't see anything on the screen, and even when i boot device with vol + power i can't see device with adb (but windows see that device is connected)... so my question to you guys ... is there anything i can do, or i can use it as a glowing flying disc?
So first i'll tell you everything from the start,
I was to a party when a girl pushed me into the pool but i had my phone with me I instantly threw it out of the pool but it doesn't wan to boot ... So i put it in rice and wait 4h, then it want to start but arrived to the main OS he crashed and shutdown himself alone. I thought it was a problem of my ROM (CM13) so i gone into my custom Recovery (TWRP) and the tactile is working and also all buttons. I decided to clear all my phone and let just TWRP. After that, i tried to push my CM13 zip file into my phone but any PC want to reconnize my phone so i can't do anything. I tried many reboots but nothing and the last one deleted my Custom Recovery so, i'm now in the menu with manipulation (Power + Down) and i have that :
FASTBOOT MODE
PRODUCT_NAME : XXXXXXXX
VARIANT - bullhead LGH791F 16GB
HW VERSION - rev1.0
BASEBAND VERSION - M8994F-2.6.30.0.68
CARRIER INFO - N/A
SERIAL NUMBER : XXXXXXXXX
SIGNING - production
SECURE BOOT - enabled
DEVICE STATE - unlocked
I downloaded a stock rom with NRT but i can't etablished a FASTBOOT / ADB connection... I have downloaded SDK ANDROID and intalled GOOGLE DRIVERS INC. thanks to NRT. I'm now installing ANDROID ADB INTERFACE but i don't know if it will help me :/
So if someone have a solution it will be sooooo nice
Thank you all !
EDIT : I don't know how; but i still can acces to TWRP but impossible du etablished a ADB / FASTBOOT connection ... Device unreconized by windows ...
If you are using windows 10 try to disable driver signature enforcemen. It worked for me.
samu_cappe said:
If you are using windows 10 try to disable driver signature enforcemen. It worked for me.
Click to expand...
Click to collapse
I had already the signature enforcement disable but in fact I have fix my phone now, it's working fine. I had to plug onto USB 2.0 ports and also clean the port where I charge it (some oxidation i think)
Sorry for my bad english i'm French ^^
Now i figure out an other issue, my battery level is stuck at 50%, i have charged it full and let it shutdown himslef but nothing changed. if someone have a solution for this ? on any kind of way to know my real bettry level with an external app it will be great
IsatiX said:
in fact I have fix my phone now, it's working fine.
Click to expand...
Click to collapse
Can't help you with your battery problem, but just wanted to say I'm impressed your phone works at all.
sfhub said:
Can't help you with your battery problem, but just wanted to say I'm impressed your phone works at all.
Click to expand...
Click to collapse
Erf, so i can't fix this issue ?
IsatiX said:
Erf, so i can't fix this issue ?
Click to expand...
Click to collapse
You can try draining the battery completely and recharging a couple of times repeatedly, but if that doesn't work you probably need to replace the battery.
You can get instructions here:
https://www.ifixit.com/Guide/Nexus+5X+Battery+Replacement/60275
The battery part is LG BL-T19.
Someone posted you can buy the parts from here:
http://www.repairsuniverse.com/
Wow such an amzing answer ! Thank you a lot ! So i'll try to see if my battery will come back in a real representatif level of battery. Your links are very helpful for me thank you once again ^^
Hello xda,
as the title says: a friend brought me a sm-r800(don't know the branding; it's from Europe, Germany) to repair because it would shut down after the Samsung logo (logo appears around ~10s). Inside the download mode (wireless) everything is okay for hours.
I've flashed now around (today is my second and last try) 8 different ROMs (https://4pda.ru/forum/index.php?showtopic=978373&st=80#entry92121314 and other). 3part, 1part ROMs without success. Still the same behavior.
I'm done /shrug
Do you have an idea or some advice to me?
Thank you
/nepixl
If Combination Firmware not work...
Are you able to post Photo or Screen text from Odin Mode aka Download Mode?
Example...
Please help, bricked Gear S3 SM-R765S
Hello, I have a SM-765S (SM-R765SDAASKC). Unfortunately it is bricked, completely stuck in the ODIN mode. In the recovery non of the options are working (except for the power off). I managed to connect to the pc using a usb cable, but the...
forum.xda-developers.com
Best Regards
To be honest, I was never been there(normal downloadmode) before (tried directly the wireless mode) but the same result (Odin tells me always a green "pass!" after the flash process).
Happy to read your feedback!
Best Regards,
/nepixl
Photo looks good to me...
No Knox dripped...
Bootloader sboot.bin is SM-R800 from ASL2 Combination Firmware...
So next Question is...
ASL2 Combination firmware can boot or do the same?
Best Regards
Edit 1.
I mean exact this file:
COMBINATION-FT40_R800XXU1ASL2.tar.md5
You flashed this allready?
Appreciate your help, thanks for this.
adfree said:
Photo looks good to me...
No Knox dripped...
Bootloader sboot.bin is SM-R800 from ASL2 Combination Firmware...
So next Question is...
ASL2 Combination firmware can boot or do the same?
Best Regards
Edit 1.
I mean exact this file:
COMBINATION-FT40_R800XXU1ASL2.tar.md5
You flashed this allready?
Click to expand...
Click to collapse
Yes, the last flashed ROM was the COMBINATION-FT40_R800XXU1ASL2 from 4pda and its the same behavior.
Shows Samsung logo for ~10 seconds afterwards display goes black for hours. (my guess: its complelety shutting down/dies.) If I hit the "Power button" the same starts again. -If it helps, I could record a video about this.
I'm really running out of ideas and I'm happy for your feedback.
Any ideas what I could try?
Thank you and best regards
/nepixl
Okay, I guess I've missed an essential step while or after flashing.
Update firmware with NetOdin
Hi all, I noticed that the BSA4 update has been released everywhere except Australia. I've been able to get my hands on the firmware files but do not know how to get the watch to connect with NetOdin. Has anyone been able to do this? I've seen...
forum.xda-developers.com
" 7. After the files are downloaded, the Watch will reboot. Again, hold Home and highlight & select Recovery in the Reboot menu. "
This is something I've never done before.
I tried this now. Watch reboots 3x times after that ⇾ shutdown. -_-
Will it make a difference if I "reset" the watch right after the flashing process (after reboot?)?
/nepixl
A
Use Standard Settings in netOdin.
NOT change something...
B
Normally after flashing 1 file Combination Firmware... you have nothing to do... only wait for finish... booting...
After few Seconds Combination Firmware should start proper...
C
In theory... you could dump Logfiles from Watch... to see why it not proper...
Require USB cable...
D
It is possible to flash CSA or other files additional... but this increase risk to damge more...
E
Maybe with other Combination Firmware more luck...
No idea of Samsung changed something... maybe with newer Version more luck... or older...
Forgotten where ASL2 is in this chain of """Evolution"""...
Best Regards
Thank you very much for your effort on me. Really appreciate!
A:
Had always stock settings in (net)Odin - Check
B:
Okay, means to me: try more combination fw! - Sure, sometimes net Odin fails - repeat flash until Odin show a green file and SW reboots - Check
C:
Yea - will be my next step - To be honest, this is my first smartwatch flash (and first time flash via Wi-Fi ever). Flashed tons of smartphones but not a single Smartwatch yet. Usually I pull a logcat via USB. In theory that could work also on a SW? I mean: I'm connected by Wi-Fi in the same network - so adb could work? But I don't know if SW have the same android features like ADB or ability to pull logcat. -Aw, logcats requires rootaccess afaik ...
D:
Will stick to your suggest -> combination fw
E:
Okay - will search for more combination fw
Awesome community. Thanks, @adfree
Best regards, stay healthy.
/nepixl
SM = Smartwatch #lazy
ASL2 seems "latest" leak...
You allready checked this Version?
File-Upload.net - COMBINATION-FT40_R800XXU1ASG1.tar.md5.7z
Datei: COMBINATION-FT40_R800XXU1ASG1.tar.md5.7z. Die Datei wurde von einem User hochgeladen. Laden Sie auch kostenlos Dateien hoch mit File Upload.
www.file-upload.net
ASG1?
List of leaked FT40 files...
SM-R800 | Easy Firmware
easy-firmware.com
Best Regards
I guess not, will do it the next time and give feedback after
Thank you again.
/nepixl
Edit: Nice source! Been there too but the fact that I have to pay scares me (sure - the devs have alot of effort to grab that software). To be honest: Prefer to donate someone (you! ) from xda before I pay this page.
But this page is a good start to have a feeling what firmware could work for me.
Hi
I had same issue multiple times, I've tried to go to boot menu and did factory reset, after multiple reboot trials, it works but this is a workaround and very frustrating that I'm looking for a solution to fix permanently.
Hi,
Thanks for your reply!
okay, I tried the same now for some minutes with the suggested firmware (ASG from @adfree)
Seems I have no luck again :/
I tried as you said: factory reset (which is factory command here?) and reboot some times but nothing..
Do you think this could be more a hardware issue?
thankyou
Okay I guess there is more screwed than expected.
I've seen in a video that a screen with "resetting..." should appear after selecting recovery mode, which has never happened on this watch. 3 Reboots and the watch will showdown/displayoff
Any ideas?!
Hi guys
add me as onw how is suffering this problem, i had this problem long time ago , after so many tries to use the guarantee with no hope, now i had to fine a solution my self
tried deferent roms nothing changed
thank you for efforts beforehand
Hi everyone. Same problem here. the watch was bought in France, but i live in Brazil and it worked well for 2 years. The issue happened just after an update. i could install a combination file, but it's limited and i could not get access to anyother function but configs. if any of you have a tutorial step by step on how to fix it, i would really appreciate it! thanks
Hi all,
I created an account just to add my comment. I FOUND A LOOPHOLE I think...
My SM-R810 did the EXACT same thing!
I was in the middle of a work day and spun my wrist up to see the time. Black, hmmm... I held the power button and saw the Samsung logo, figured I might have accidentally not turned it on that morning. no biggie. Lunch time I check it out again, off. I turn it on and watch this time. 10 seconds and the "Samsung Galaxy Watch" screen turns back off. Hold the power button continuously and get into Recovery successfully, select Recovery to format the watch. It restarts like it's going to do it in the youtube videos I had just referenced, turns off after Samsung logo again. Now I'm pissed...
I know for sure I was at 87% battery when I walked into work this morning! Even the charging screen shuts off before it "loads up" the correct charge position, 87%. I brought my charger in and noticed that after 2 minutes of charging, the charger starts blinking red? So my next thought is maybe the battery is unstable or setting off some type of digital alarm.
THE SOLUTION THAT CLEARED MY PROBLEM:
Everything i did shuts off after 10 seconds EXCEPT for Download (Wireless) mode. So I left it in wireless mode for an hour and it successfully drained to 24%. I placed it on the charger and brought it up to 46% then turned it on. It immediately started formatting the watch as i requested 5 different times lol
FIXED!!!!!
I'm an EET but have spent little time tinkering with this watch. I know the battery is fully removable but does anyone out there know if this all could have been caused by a voltage instability that auto-triggered a safe shutdown - something like that? I'd like to make sense of the situation so that I may prevent it. I.E., overcharging the battery, watching its temperature, etc.
Thanks all!
-General