Bricked Gear Live? - Samsung Gear Live

Hi, I was wondering if anyone could please help. I have a gear live, always running on stock firmware. Randomly without me doing anything to the device, it got stuck on the boot logo. So I decided to see if I could boot into recovery mode, but I get the error
"mmc_read fail" and "movinand checksum confirmation fail"
The bootloader also seems to be locked, so is there any way I can recover this device?
EDIT: The only thing I can do is boot into Fastboot, can't enable USB Debugging for adb to work
Thanks

Please help, i can only access fastboot with a locked bootloader

Related

[Q] "Process system isn't responding"

Hello! I'm needing some help.
My M7 currently will not boot, keeps saying "process system isn't responding". I can access bootloader and stock recovery. It has a LOCKED bootloader. All im wanting is to either flash stock or find a way to unlock the bootloader to flash something that works! I've been attempting to unlock it, have tried multiple drivers. My pc keeps saying the phone "isnt working properly" when i go to the fastboot screen. It shows a yellow traingle next to it in device manager. Oddly i can access the storage of the device when it's attempting to boot up at the htc logo screen. I managed to get the stock rom zip on the device. But the recovery wont flash it, it also says sd read failed in the recovery.
I hope I can get some constructive help on this. I've flashed many phones before usually with external sd. Please let me know any ideas you have. I'm somewhat at a loss.
Also, i received the phone this way, i'm not sure what has or hasn't been done to it.

[Q] TWRP Looping *Mac User

Hey guys, so I'm currently in a bit of a bad situation. My Nexus 6 was recently rooted, then I tried unrooting the device back to stock. Upon the process I have gotten myself to the point to where from the boot loader screen selecting START or RECOVERY MODE will send the device to the TWRP screen which shows TEAMWIN, but it bootlegs at this point. I am only able to access to the Bootloader screen which displays that my Device is Unocked, Status Code 3, Transfer Mode USB Connected... If someone can please help me out o just getting this device to start again I would greatly appreciate it thank you
Brandonsablan said:
Hey guys, so I'm currently in a bit of a bad situation. My Nexus 6 was recently rooted, then I tried unrooting the device back to stock. Upon the process I have gotten myself to the point to where from the boot loader screen selecting START or RECOVERY MODE will send the device to the TWRP screen which shows TEAMWIN, but it bootlegs at this point. I am only able to access to the Bootloader screen which displays that my Device is Unocked, Status Code 3, Transfer Mode USB Connected... If someone can please help me out o just getting this device to start again I would greatly appreciate it thank you
Click to expand...
Click to collapse
found myself in the same situation after trying to unroot and lock the n6. new at this so not really sure what happened but was trying to get it to stock and locked so i could get to 5.0.1 twrp on win using wugs tools.

[Q] BootLoader unlocked, Flashed TWRP successfully, Recovery Boot up failed though.

As it says in the title I've already unlocked and flashed several times (downloaded multiple versions of TWRP to see if it was just the download itself, as well as checking the MD5 to see if it was corrupt.) I flash it it gives the usual partition message when I go to boot recovery I just get a Bootup failed. Lost as to what to do from here. Trying to root my phone. My phone still works as I'm able to use it atm but I don't know what else to do.
It seems if I reboot, and try going into recovery then it doesn't give me a bootup failed message but I get the android icon where he fell over and has the red triangle coming out of his chest.
Dunno if this is part of the issue but my phone isn't being detected as a adb device either, and there's not ADB debugging option to enable under developer setting just usb debugging which is enable. The drivers are install so I know it's not a driver issue.

Xiaomi MI A2, is stuck in bootloop

Hi Guys,
My MI-A2 is stuck in bootloop ( When I turn on my phone it shows its Android One logo and then it shutdown itself ).
In my phone, I didn't turn on any USB Debugging or and OEM unlocking. and now it is possible as the phone is not starting.
I am able to access fastboot and recovery options
I tried to do factoryReset the device from the recovery option but it is just wiping the data.
here are the following things which I have tried with fastboot.
- I tried to unlock the fastboot with MiFlashUnlock but it stops at 99% and gives me the error of unable to verify the device,
- flashing the Stock ROM isn't working with MiFlashTool. giving random errors.
- tried changing the drive partition. it gives error to unlock the device first.
- tried tried to flash TWRP but it also gives me the error of unlocking the device first.
Almost every command of Fastboot is giving me some kind of error
But I am able to access the ADB Sideload from the recovery option.
- I tried to load the April OTA update from ADB Sidelode. The update is Successfully installed. But the device is still in bootloop.
Saving User data is not my priority. I just want the device to be working anyhow. As per my assumption, Fastboot is not an option for me unless it unlocked. I think something from the ADB sideload can be done.
Any help will be appreciated.
Is it a Guide?
Oh, now, its a Great News!
Please delete this post from this forum.
As I have already wrote to you, questions should go to "Questions and Answers" forum.
And as I have already wrote to you, Search works here, and if you've used it, you'd get answers (in mentioned above forum):
1. MiA2 having A/B slots architecture, - is supposed to recover to the other slot X when OTA corrupts ROM is slot Y, - after numerous boot attempts.
2. In case you have tampered phone with try-and-see operations without knowing what you were doing - the only way to recover phone is: TEST Point / EDL. Search these keywords in this forum for appropriate Guide.
try the "fastboot continue" command
dillu12 said:
Hi Guys,
My MI-A2 is stuck in bootloop ( When I turn on my phone it shows its Android One logo and then it shutdown itself ).
In my phone, I didn't turn on any USB Debugging or and OEM unlocking. and now it is possible as the phone is not starting.
I am able to access fastboot and recovery options
I tried to do factoryReset the device from the recovery option but it is just wiping the data.
here are the following things which I have tried with fastboot.
- I tried to unlock the fastboot with MiFlashUnlock but it stops at 99% and gives me the error of unable to verify the device,
- flashing the Stock ROM isn't working with MiFlashTool. giving random errors.
- tried changing the drive partition. it gives error to unlock the device first.
- tried tried to flash TWRP but it also gives me the error of unlocking the device first.
Almost every command of Fastboot is giving me some kind of error
But I am able to access the ADB Sideload from the recovery option.
- I tried to load the April OTA update from ADB Sidelode. The update is Successfully installed. But the device is still in bootloop.
Saving User data is not my priority. I just want the device to be working anyhow. As per my assumption, Fastboot is not an option for me unless it unlocked. I think something from the ADB sideload can be done.
Any help will be appreciated.
Click to expand...
Click to collapse
you need to flash the phone in edl mode
**just be careful there is a timeout ..when you put it into edl you need miflash and rom.loaded
*** download a stock fastboot stable pie for jasmine
**** unzip amd select revelant xml from within miflash
*****on phone manually boot to fastboot mode with buttons
****** run command "fastboot oem.edl"
*******device will boot to black screen ... immediately go to miflash and press the button to start flashing
___BE CAREFUL__ select clear all tick box at bottom of miflash screen
this should be enough to rescue your device regardless of what you've done or whether you unlocked bootloader or not

[Help][James][Sprint] Need help to force EDL mode

Hi i have a model XT1921-5. It got stuck in the logo screen and couldnt boot into recovery so i tried a rescue with the RSA, it detected the phone in fastboot and found the firmware but failed flashing it. Now it only boots into fastboot.
When flashing the firmware manually only gpt.bin fails but the phone is still stuck in fastboot (failed to validate hab image - failed to validate boot image. same with recovery image). I tried everything i could but nothing worked out.
I think my only "chance" is to try a blankflash. The problem is that my bootloader is locked (never unlocked) so i cant do fastboot oem edl, i cant find anything about test points for this model.. So im looking for a way to maybe hard brick the phone to force it boot into EDL mode and try the blankflash. Unless there's a way to set the OEM unlock option via fastboot..
I appreciate any help.
Thanks in advance.
I was able to put my phone on QDL mode via test point.
Now i tried to flash the blankflash but it throws the error "XML (0 bytes) not validated"..
Does anyone knows what this error means? If is a version mismatch then i cant find a newer version of this blankflash..
Any help is always appreciated.
For anyone interested this is the test point you need to short to boot into QDL mode

Categories

Resources