Bootloop after Flashing Custom Rom - Samsung Galaxy Gear

Hi Guys,
today I got an old Samsung Gear V1 (SM-V700) and as I had some problems pairing it with my HTC 10 I tried rooting it and flashing a custom rom.
To be honest: Nothing worked as expected. I tried jodin3 (not working), Impactor (not working), sdb bridge (sure, not working as the "SU" command was not present at the gear). s
As I'm a mac user, the last thing I did was installing heimdall and used the command
Code:
heimdall flash --RECOVERY ~/null_03_TWRP2.7.tar.md5 --no-reboot
to flash TWRP to the Samsung Gear.
Everything worked fine and finished and I tried to boot into recovery mode.
BUT: When I enter recovery mode, it says "Downloading... Do not turn off target !!".
When I try to boot, it stucks at the Samsung Logo.
When I start Download Mode, I can flash other firmware to the device. But not matter what I do and what I flash: It always stucks and Recovery Mode always talls me "Downloading... Do not turn off target".
Any ideas would really be appreciated.
I'm freaking out already, I already tried to flash mostly everyhing flashable
EDIT: This post solved my problem: h**ps://*ww.usp-forum.de/samsung-galaxy-gear-forum/108927-samsung-galaxy-gear-flashen-anleitung.html

Related

[Q] only recovery mode acces

Hi
I am not sure if there is someone who can help me but here is my problem. I have tried to upgrade my Galaxy S to froyo via Odin without the 3 buttons combo available(Now I know this is stupid:| ). I've used adb to enter the download mode and while Odin tried to install the upgrade I got a green freeze screen on my phone and Odin has freeze too. After rebooting the phone it always stuck in the recovery mode and displays the following error:
E:/Can't mount/dev/block/stl11
Right now I can only connect to my phone trough adb console and Odin but only in recovery mode. When I run the "adb reboot download" command the phone only reboot in recovery mode, not in download mode.
Is there something I can do to bring my phone in download mode?
Any help on this issue will be much appreciated
Thanks!

[Q] Stuck in endless bootloop and recovery is not working either.

Hi everyone
Since I restarted my phone last night, my phone has been in a endless bootloop and I can't even enter recovery, without it rebooting again and going into the same endless bootloop again, around 2 seconds after showing the "Teamwin" logo.
I'm using ARHD, and if I remember correctly it's version 71.1. TWRP is "openrecovery-twrp-2.6.3.3-m7" and running ElementalX kernel.
I expect my partition is somehow corrupted, but I'm at a loss of ideas as to how I can recover my phone again. I would apreciate if I could somehow manage to make a backup of my data, but it that's totaly hopeless, I'm thinking of going for the ArtMOD ROM instead and starting fresh.
Is there a helpfull soul out there, that could maybe give me some insights as to what I can do from here? Thanks in advance!
I was hoping I could install a stock ROM and start from scratch again, but I somehow suspect having used a modified ROM has gotten me in trouble now and the ROM Upgrade utility sees this as a downgrade. I've not been able to find a newer ROM for the .401. series than "RUU_M7_UL_K44_SENSE55_MR_HTC_Europe_4.19.401.9_R_Radio_4A.23.3263.28_10.38r.1157.04L_release_353069_signed_2-1.exe". Although the updater believes I'm updating from 4.19.401.11 (the ARHD ROM).
I can get into FASTBOOT USB and the phone goes to the black HTC logo screen when trying to update, but quickly fails on the PC during the process at "Updating 1/5". When unplugging the USB cable the phone shows:"
RUU
Security fail!
Update Fail!
I've attached two screenshots, to better explain
Can some kind soul out there please help me getting a working phone again? What ROM I'll end up with doesn't really matter
Since you're using unlocked bootloader, why don't you try RUU to get back on Stock ROM.
Here is the collection of ROMS
Download your ROM.
from Windows Command prompt
adb reboot bootloader #
If it didn't work, Press and Hold Power button along with Volume down of your phone,
When you reach to bootloader, get into fastboot mode.
Now follow the following commands to restore the STOCK Rom. (make sure your downloaded ROM are in the same directory where you have fastboot.exe, abd, and abdwin.api etc)
1) fastboot erase cache
2) fastboot oem rebootRUU
3) fastboot flash zip RUU.zip (RUU.zip is of course your downloaded Stock ROM). If it says Failed, try again.
4) fastboot erase cache
5) fastboot reboot-bootloader
6) fastboot reboot
Good Luck
Hope that helps.
Thank you so much for helping out!
After several tries, tries and retries, I finally managed to get the phone back up and running with the stock ROM. I believe what finaly did the trick, was to use "fastboot oem lock" to get the stock ROM installed. From here, I'm now able to unlock it again and install a custom recovery (TWRP) and ROM (I went for ARTMOD). Thanks again!!!

My phone keeps rebooting, even when trying to flash it with Flashtool.

Hey there!
Here's the thing. I was using MIUI v7, which I figured to install after doing a hard-brick to my phone and resurrecting it from death.
I wanted to try a Lollipop AOSP ROM I found here, but seems I screwed it up. No, actually I f***ed it up. I guess the TWRP version I had was incompatible, or something. Even seemed the flashing was successful, every time I tried to turn off the device it rebooted. I couldn't reboot it into recovery either, seems the flashing deleted it or screwed it up. Now all I got is the infamous red blinking light. No Sony logo. Nothing.
So I tried to flash a stock ROM with flashtool, but even in flash mode the phone keeps rebooting like each minute! So it's impossible to flash it.
The only state the phone is not auto-rebooting is when I reboot it into fastboot mode. I was looking for flash the stock firmware with fastboot, but I dont' find there a boot file (I mean, inside the .ftf files) and I'm unsure about the procedure to flash it, if there's even one... Can someone give me an advice? Thanks!
Nevermind, I flashed CM's recovery via fastboot and although I couldn't flash CM ROM with fastboot (It said 'command not found') once on CM's recovery I flashed CM ROM! If needed, please remove this thread.
Stuck in the same state (using SP Flash Tool) but unfortunately no custom recovery available for my phone (Nokia 1 ta-1056).
Phone goes to fastboot mode upon connecting USB to flash stock ROM via SP Flash Tool, making it impossible to flash
Any advice?

[SOLVED] Samsung Tab 3.7.0 SM-T210 recovery and OS broken

Hi everyone,
I have retrieved a Samsung Tab 3.7.0 SM-T210. The OS was the old KitKat 4.4.2, very slow and buggy. I tried to flash a new recovery and OS and spent the 3 last days getting fails. I think I have read the all internet about this situation and would like to make a last try with your help.
When I got the tablet, I was surprised that in download mode it was indicated custom and custom binary and not official as it has not, I think, been flashed in the past by the people owning it. With HW rev 0x5 at the end.
The first thing I wanted to do was to unlock the bootloader, however, I could not find any option in developer mode talking about OEM bootloader, neither Auto Update. After reading some people on forumes saying that this device might not have a locked bootloader, I finally thought that this tablet did not have its bootloader locked. Then I decided to go further with the flash of a TWRP recovery.
At the beginning the stock recovery was working. I am under archlinux, I have fastboot and heimdall. To do it as right as possible I installed a VM with Windows 10 and tried to flash a custom TWRP corresponding to the tablet with Odin. But the process got stuck at the SetupConnection step. I installed Windows 7 too, tried 5 different Windows OS, tried 4 different USB cables, reinstalled the USB drivers, tried 5 different Odin versions, tried different archives, just recoveries and all stock system. Still getting stuck at the SetupConnection.
I finally decided to try heimdall thinking that the VM could be the problem. With heimdall I run flash commands such as heimdall flash --RECOVERY twrp-3.2.3-0-lt02ltespr.img --no-reboot and got it doing something, the shell was saying it's 100% done and the tablet, in download mode, was showing a complete blue bar. Then, the recovery was just broken. Could not access it anymore, the Samsung Tab3 logo showing up and staying when trying to access it. I tried to flash some others archives, I opened it off and remove the battery for 5 minutes, still the same thing.
The operating system was still accessible and buggy, applications saying connection issues, etc. I did a factory reset from the running KitKat android OS and now have the Samsung Tab3 logo showing up and staying when trying to access it.
Now, I can only access the download mode and that's all. I have the impression that I am not the first one having these kind of trouble with this tablet. Is it a hardware issue on all these tablets ? Should I try something more advanced with heimdall, dd ?
Does someone have a solution in this situation ?
Thanks for your time and help.
I finally used heimdall and was able to flash all the partitions with the stock images. Now I am back in stock version. I would like to flash a TWRP recovery.
Can someone tell me if I have to unlock the bootloader with this device ? If it is, how can unlock it ? I can not find anything in the settings developer section, and can not use a call number input in order to enter a system code as it's a tablet. Do I have to wipe something from the stock recovery in order to see it ?
Thanks for your time.
Hi -yo-.
You don't need to do OEM unlock as this device is so old.
Also twrp-3.2.3-0-lt02ltespr.img is NOT for this device.
For recovery look from here and for ROM here.
Thanks jonezy82 for the answer. Indeed, I figured all of that out.
I decided to get it back stock and not trying to flash anything custom.
Thanks for your time.

Question [Help] I Can't Reflash back to Stock! (Can boot to fastboot mode, have TWRP and is working.)

Hi, everyone! I flashed another custom ROM and this time, while I was going to clean all and start fresh, I encountered an annoying problem. If I put my phone into Fastboot mode, and flash the latest and global ROM, MiFlash keeps saying: "error:FAILED (remote: "Check device console.") and it will stop. I already tried reflashing the custom ROM (using TWRP); Restarted my PC; and finally, Reinstalled the drivers but nothing seems to work please help me.

Categories

Resources