Database Info

[Q] Can't unbrick. Tried nigh everything.

Greetings! First of all, I would like to thank anyone who takes the time to help me diagnose and resolve this issues, let alone anyone who takes the time to read this thread.
I've been having issues with my Xoom (ICS 4.0.0) for about 3 weeks now.
A brief history of the issue's occurrence:
-I unrooted the device and returned it to stock.
-Everything was fine and dandy until one day it spontaneously said something along the lines of 'Android is upgrading..', and then performed a reset.
-Since resetting, it bootloops.
The device only turns on when plugged into a charger and hard reset.
The device only turns off when allowed to boot loop for minutes and then hard reset (it simply does not reset, and just turns off).
I'm not the most technically-savvy person with android devices but here are some things I've done/noted.
When trying to use adb commands, it does not recognize the device or properly issue commands.
I've tried wiping data/clearing cache to no avail.
EDIT: I've tried fastbooting, but the bootloader will not unlock. When trying to unlock, it simply resets and then acts as though it was never unlocked.
I have no idea how to return it to a stock image. All I know is that I have a micro-SD and some spare time.
Could anyone help me understand what exactly is going on with my Xoom?
If I can provide you with any more information, please let me know.
Thanks again. (=

If it was stock and spontaneously upgraded it sounds like a bad OTA upgrade. I've been rooted from the start so never have taken an OTA upgrade...don't you need to accept it or can it just upgrade on it's own?
Anyway, can you get it into fastboot mode?
Volume up and power, then at dual core screen, press volume down...if you see something like "entering fastboot mode" you're not bricked. You do not have to re lock your bootloader. Just make sure you have downloaded the correct stock files for your Xoom model to your PC and flash it.
If you haven't done so, just google 'recovering Xoom using fastboot' and you should get some good information.
Good luck!

Remember to grab the MZ604 files if you have the Wifi only version of the Xoom.
http://developer.motorola.com/products/software/ <------ Grab the files here. The files are for the US version of the Wifi Xoom only.
Instructions to return it to stock
1) First you need the Moto Drivers - Read this thread to START you - http://forum.xda-developers.com/showthread.php?t=981578
Should have these drivers installed if you have rooted your Xoom before.
2) Make sure you have the latest SDK - adb and fastboot should be in /platform-tools -
http://developer.android.com/sdk/index.html
Should have the android SDK if you have rooted your Xoom before.
3) Place all the downloaded stock image files into the SDK Tools folder.
4) If you are booting up from scratch, you can get the Xoom in fastboot mode by doing the following. Use command prompt to perform the rest of the steps
Hold VolDown and Power button will boot unit for fastboot mode
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
If you Xoom is booted up already follow the commands below using command prompt to perform the steps
adb reboot bootloader <---- reboots the Xoom into fastboot mode.
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
As Always If This Was Helpful Hit the Thanks!

Yeah, what Mjamocha said...

okantomi said:
Yeah, what Mjamocha said...
Click to expand...
Click to collapse
LOL Thanks.

okantomi said:
Anyway, can you get it into fastboot mode?
Click to expand...
Click to collapse
Yes, I can. But so far nothing has been successful in terms of fastboot commands.
okantomi said:
You do not have to re lock your bootloader. Just make sure you have downloaded the correct stock files for your Xoom model to your PC and flash it.
Click to expand...
Click to collapse
When I try to execute fastboot commands such as 'fastboot flash boot boot.img'.. it says the following:
Device still locked. Device must be unlocked first. Failed to process command error(0x8)
Whenever I try to unlock the bootloader, it appears to be successful at first and then the device reboots. But it just reboots to a bootloop, and the bootloader still says its locked. Perhaps I made a mistake in communication. The bootloader is currently locked and will not unlock, as just described.
When I try to unlock it and it reboots, even if I access the fastboot menu right away, it still says the device is still locked.
Thoughts?

Can you get into recovery? With the Xoom off (to make sure it's really off, hold volume up + power for a few seconds), hit the power button and when you see the M logo, wait a very brief moment (like a fraction of a second) and hit the volume down button. When it says "recovery" on the top left, hit the volume up. If you can get in there, either restore a nandroid (if you have one) or do a factory reset.

slacka-vt said:
Can you get into recovery? With the Xoom off (to make sure it's really off, hold volume up + power for a few seconds), hit the power button and when you see the M logo, wait a very brief moment (like a fraction of a second) and hit the volume down button. When it says "recovery" on the top left, hit the volume up. If you can get in there, either restore a nandroid (if you have one) or do a factory reset.
Click to expand...
Click to collapse
Yes, I can get into android recovery. However, within a second of switching into recovery mode, the robot falls down and there appears to be a red triangle caution sign containing an exclamation point.
When trying to do a factory reset, it says all data is wiped (as normal). Upon rebooting, it continues to bootloop. So essentially the factory reset and cache clear options in the Android Recovery menu do not produce the expected results.
Pretty odd. I didn't mess with the Xoom at all prior to this issue.

Try flashing just a recovery img to hopefully get your recovery working again. I think you can flash a custom recovery even if the bootloader is locked (i could be wrong but worth a shot) I attached the Rogue "recovery-rogue-1.3.0.img". Try a "fastboot flash recovery recovery-rogue-1.3.0.img"
EDIT: Sorry, I guess you can't flash a custom recovery with a locked bootloader.

slacka-vt said:
Try flashing just a recovery img to hopefully get your recovery working again. I think you can flash a custom recovery even if the bootloader is locked (i could be wrong but worth a shot) I attached the Rogue "recovery-rogue-1.3.0.img". Try a "fastboot flash recovery recovery-rogue-1.3.0.img"
EDIT: Sorry, I guess you can't flash a custom recovery with a locked bootloader.
Click to expand...
Click to collapse
Yeah, just tried it to no avail. Thanks so much for your help anyway. (=
I'm not sure what to do now.

I would keep trying to unlock it using different USB cables and different USB ports on your computer. I've had unlocks fail a bunch of times and for some reason, it was because of a $hity USB cable and/or a bad port on my computer.

slacka-vt said:
I would keep trying to unlock it using different USB cables and different USB ports on your computer. I've had unlocks fail a bunch of times and for some reason, it was because of a $hity USB cable and/or a bad port on my computer.
Click to expand...
Click to collapse
I hear ya. I've tried 2 different cords and 3 different computers. I'm using a Mac (10.6.8) right now, but have used 2 PCs (Vista + 7).

Out of curiosity, when you tried to flash the custom recovery, did you get the same "device still locked" error or did it appear to flash but then recovery failed?

slacka-vt said:
Out of curiosity, when you tried to flash the custom recovery, did you get the same "device still locked" error or did it appear to flash but then recovery failed?
Click to expand...
Click to collapse
I got the 'device still locked' error. Weird, huh?

How about trying to lock it again even though it says it's locked -maybe it's stuck in an "in-between state"? Try a "fastboot oem lock" and if it finishes then try a "fastboot oem unlock". I know, I'm grabbing at straws here. I thought I bricked my Xoom last week. All I did was an "adb reboot bootloader" and the device went to a black screen. Volume Up + Power did nothing. I ended up buying a T5 (Torx 5) bit at the store, removed the back cover and disconnected the battery for 30 seconds using a piece of paper to separate the contacts. The Xoom booted right up after that.

slacka-vt said:
How about trying to lock it again even though it says it's locked -maybe it's stuck in an "in-between state"? Try a "fastboot oem lock" and if it finishes then try a "fastboot oem unlock". I know, I'm grabbing at straws here. I thought I bricked my Xoom last week. All I did was an "adb reboot bootloader" and the device went to a black screen. Volume Up + Power did nothing. I ended up buying a T5 (Torx 5) bit at the store, removed the back cover and disconnected the battery for 30 seconds using a piece of paper to separate the contacts. The Xoom booted right up after that.
Click to expand...
Click to collapse
Yeah I tried that. Won't lock or unlock successfully. Locking produces no difference, and unlocking produces the same 'device still locked' error. This is getting out of hand! Thanks so much for your advice. You think I should open it up?

I hate to be so persistently annoying about this, but could anyone possibly suggest a method of working around the locked bootloader?
Is there anything I can do with an SD card to remedy the device's stubborn foolery?

I think you should give it a try, I have bricked my xoom a few times and have always been able to flash the stock imagine to recover. You really have nothing to lose by pulling the battery pin just be careful.
Sent from my Xoom using xda premium

I don't know if I'm technically-equipped enough to do that. )=
Sounds easy, but I imagine it would be rather easy to screw something up? Essentially what I should do is unseat the battery, right?

cherlamperter said:
I don't know if I'm technically-equipped enough to do that. )=
Sounds easy, but I imagine it would be rather easy to screw something up? Essentially what I should do is unseat the battery, right?
Click to expand...
Click to collapse
I have looking for a utube how to guide but no luck, I just might make one for you so you will know what to expect. Give me a few and I will get back to ya.
Sent from my Xoom using xda premium

Huawei Watch 2

I have bought a Huawei Watch 2 on Ebay. It has arrived with a pattern lock on with no response from the seller. When trying to hard reset through fastboot loader it comes up with a large red circle with an exclamation mark in it then restarts. Anyone know how I can flash a stock sawshark onto it without being in developer mode or any other suggestions to get it working? thanks

LDVincenzo said:
I have bought a Huawei Watch 2 on Ebay. It has arrived with a pattern lock on with no response from the seller. When trying to hard reset through fastboot loader it comes up with a large red circle with an exclamation mark in it then restarts. Anyone know how I can flash a stock sawshark onto it without being in developer mode or any other suggestions to get it working? thanks
Click to expand...
Click to collapse
In fastboot mode, Did you enter Recovery?

LDVincenzo said:
I have bought a Huawei Watch 2 on Ebay. It has arrived with a pattern lock on with no response from the seller. When trying to hard reset through fastboot loader it comes up with a large red circle with an exclamation mark in it then restarts. Anyone know how I can flash a stock sawshark onto it without being in developer mode or any other suggestions to get it working? thanks
Click to expand...
Click to collapse
I just ran into this same issue with mine after not wearing it for so long I forgot the PIN.
What worked for me was the following:
Install Android tools. You'll need to use `fastboot` for this to work.
Set the device in the dock and plug the USB into your computer.
Put the watch into fastboot mode the same way you have been, but don't select any options yet.
Run
Code:
fastboot oem unlock
Choose Yes on the watch when prompted. Note: Apparently this voids the warranty, but in our cases I think we're well past that anyway.
Run these commands:
Code:
fastboot erase cache
fastboot erase userdata
I still can't get into recovery, but it did factory reset the watch so I can use it again. I'm going to just lock it back up and use it as-is probably, but I assume from here you could now enable developer tools and flash whatever you want on there.

Just a quick question does unlocking the bootloader kill off GPay? Because I thought that I read something about it that said that it did. Or can you just relock the Bootloader again later. Also does does this leave a permanent mark on the device?

Got locked out of my watch after losing the phone it was connected to and not using the watch for a while. Downloaded the fastboot thing (I am inept at coding and the only cmd experience I have is running files in FDS fire simulators.) Couldnt get fastboot to work properly. Super easy way to reset the watch:
1.Keep input the wrong pattern or input to get locked out for 30s.
2. After the 30s, keep inputting wrong until it asks you if you want to reset the watch.
3. Wait for it to complete its reset!
Hope this helps someone!!!!

SM-A207F - How to fix bootloop?

I was following the instructions from here trying to root my s20+ Plus sm-a207f and everything going fine until I had to do a reboot and now my phone is a bootloop and a I keep getting a error message about flashing the wrong binarie . Can someone tell me how to bypass this message to get into recovery to do a factory reset and wipe the cache? Is there a tool that I can install on my pc that would do a reset... Would a abd command do it? I am a very sick man that has rapidly progressing COPD with about 25% of my lungs that is still working. So any and all help i will be truly grateful for...tyvm. I really need my phone.

Hint: Replace this thread's absolutely senseless title by SM-A207F - How to fix bootloop ?

jwoegerbauer said:
Hint: Replace this thread's absolutely senseless title by SM-A207F - How to fix bootloop ?
Click to expand...
Click to collapse
I would love to tell u something but my Lord and Savior wouldn't like it to good.... But I WILL SAY THIS.... YOU ARE A TRUE WITCH

harleyusa59 said:
I was following the instructions from here trying to root my s20+ Plus sm-a207f and everything going fine until I had to do a reboot and now my phone is a bootloop and a I keep getting a error message about flashing the wrong binarie . Can someone tell me how to bypass this message to get into recovery to do a factory reset and wipe the cache? Is there a tool that I can install on my pc that would do a reset... Would a abd command do it? I am a very sick man that has rapidly progressing COPD with about 25% of my lungs that is still working. So any and all help i will be truly grateful for...tyvm. I really need my phone.
Click to expand...
Click to collapse
Have you tried to do a hard reset with the device itself?

paulhauth25 said:
Have you tried to do a hard reset with the device itself?
Click to expand...
Click to collapse
Sorry for the late reply but I just got out of the hosptail again how can I do a hard reset when it wont even turn off ? And how do I get into recovery without a bixby button? Tyvm for your time and help.

harleyusa59 said:
Sorry for the late reply but I just got out of the hosptail again how can I do a hard reset when it wont even turn off ? And how do I get into recovery without a bixby button? Tyvm for your time and help.
Click to expand...
Click to collapse
If a Bixby button isn't present then it should be obvious that you can't boot phone into recovery by means of additionally pressing the Bixby button - 3 buttons press method.
You have to boot into phone's recovery by means of ADB
Code:
adb devices
adb reboot recovery
what requires phone is connected to PC via USB and USB-debugging got enabled on phone.

jwoegerbauer said:
If a Bixby button isn't present then it should be obvious that you can't boot phone into recovery by means of additionally pressing the Bixby button - 3 buttons press method.
You have to boot into phone's recovery by means of ADB
Code:
adb devices
adb reboot recovery
what requires phone is connected to PC via USB and USB-debugging got enabled on phone.
Click to expand...
Click to collapse
Tyvm for your help and time

jwoegerbauer said:
Hint: Replace this thread's absolutely senseless title by SM-A207F - How to fix bootloop ?
Click to expand...
Click to collapse
TYVM for your adb/fast file now maybe I can get my phone back.

Question I can't access the download mode

So here is the deal.
This device (Galaxy A32 5G - SM A326B - Android 12) does not let me boot into the download mode in order to unlock bootloader and for eventually rooting it.
OEM unlock has been selected in the dev options.
No button pressing configuration is working.
Trying to access the fastboot mode in the recovery mode only shows a black screen with a red writing on top that fastboot mode is being loaded, but nothing is happening and Odin doesn't recognize the device.
I just want that turquoise, blueish download mode screen, but for the love of it, it just doesn't work getting there.
This is my backup device and I just want to root it. Coming from OnePlus I am spoiled but the fact that I can't access this mode with all kinds of button tryouts is just nagging on me.
Anyone experienced something similar?
Some help would be greatly appreciated.
Cheers

mrjuniork said:
OEM unlock has been selected in the dev options.
Click to expand...
Click to collapse
I have the SM A326U but unfortunately I tried to see if I had the OEM Unlock options in the Developer Options Activity, and it's not there.
Do you know what the hidden activity might be when you click on the OEM Unlock? Maybe we can bring it up with an Activity Launcher?

mrjuniork said:
So here is the deal.
This device (Galaxy A32 5G - SM A326B - Android 12) does not let me boot into the download mode in order to unlock bootloader and for eventually rooting it.
OEM unlock has been selected in the dev options.
No button pressing configuration is working.
Trying to access the fastboot mode in the recovery mode only shows a black screen with a red writing on top that fastboot mode is being loaded, but nothing is happening and Odin doesn't recognize the device.
I just want that turquoise, blueish download mode screen, but for the love of it, it just doesn't work getting there.
This is my backup device and I just want to root it. Coming from OnePlus I am spoiled but the fact that I can't access this mode with all kinds of button tryouts is just nagging on me.
Anyone experienced something similar?
Some help would be greatly appreciated.
Cheers
Click to expand...
Click to collapse
Did you try plugging into usb while holding down the buttons?

TimmyP said:
Did you try plugging into usb while holding down the buttons?
Click to expand...
Click to collapse
Yes, among other things. It just never enters that mode. It either restarts, goes into charging mode or reboots to recovery.
It's weird

maybe try "Samsung 300k Tool?" It looks like its designed specifically to reboot Samsungs into Download mode

TimmyP said:
maybe try "Samsung 300k Tool?" It looks like its designed specifically to reboot Samsungs into Download mode
Click to expand...
Click to collapse
Thx for this useful information. I could enter the download mode with this program but interestingly there is no way to use volume up button for proceeding to unlock the bootloader. Odin recognized the device properly but no way to unlock the bootloader. Isn't that strange? Also I did not see the warning screen, it went straight to the download mode screen.
I did not expect this to be such a pain...

Glad it worked! Samsungs always seem to have some sort of strange issue. I was recently stuck in a bootloop for a half hour until I finally got the key combo for recovery to work. Since it never turns off it becomes a pain!

TimmyP said:
Glad it worked! Samsungs always seem to have some sort of strange issue. I was recently stuck in a bootloop for a half hour until I finally got the key combo for recovery to work. Since it never turns off it becomes a pain!
Click to expand...
Click to collapse
I actually figured it out without the need of any 3rd part software.
There was obviously one option that I haven't tried yet. Pressing both volume buttons and then plugging in the USB cable till the warning screen shows up. That's it
Anyway, thx for taking your time to reply.
Cheers

mrjuniork said:
I actually figured it out without the need of any 3rd part software.
There was obviously one option that I haven't tried yet. Pressing both volume buttons and then plugging in the USB cable till the warning screen shows up. That's it
Anyway, thx for taking your time to reply.
Cheers
Click to expand...
Click to collapse
Hello Pal, were you able to root the device? I have bought an A33 5G, not sure if I will be able to root it. Extracting the boot.img file from original rom, patching it with Magisk and flashing back to the phone works? Can you use fastboot for it or do you need ODIN?

GauchoTche said:
Hello Pal, were you able to root the device? I have bought an A33 5G, not sure if I will be able to root it. Extracting the boot.img file from original rom, patching it with Magisk and flashing back to the phone works? Can you use fastboot for it or do you need ODIN?
Click to expand...
Click to collapse
Hello again.
Yes, I managed to root the device.
I used Odin for flashing the patched boot image. AFAIK, using fastboot isn't possible, hence Odin.
But make sure you have a backup in place, coz in my case, initially applying a patched image, led to another factory reset (the second one after unlocking the bootloader).

mrjuniork said:
Hello again.
Yes, I managed to root the device.
I used Odin for flashing the patched boot image. AFAIK, using fastboot isn't possible, hence Odin.
But make sure you have a backup in place, coz in my case, initially applying a patched image, led to another factory reset (the second one after unlocking the bootloader).
Click to expand...
Click to collapse
Hello, I need help with unlocking the bootloader as well. I can't find the Oem option and there is no unlock the bootloader option in download mode.

Question Forgot unlock pattern on GW 4

Hi All
I had long time to use my smartwatch and "managed" to forget my unlock pattern
It's not inside my Find my device Samsung service and the only way is via offline hard reset
I can't turn it off or restart.
As I have the purchase receipt I can do at Samsung repair center but I was wondering if any flash tool or way available to avoid the cost
Thanks

If you have US LTE device... then no idea...
But if you see in Reboot Menu...
Bootloader unlock....
This makes FAC Reset.
Then you can in same menu Bootloader lock...
NOT Flashing!
Only unlock/lock...
Good Luck.
Best Regards

adfree said:
If you have US LTE device... then no idea...
But if you see in Reboot Menu...
Bootloader unlock....
This makes FAC Reset.
Then you can in same menu Bootloader lock...
NOT Flashing!
Only unlock/lock...
Good Luck.
Best Regards
Click to expand...
Click to collapse
I have a EU non LTE version, my problem is that I cant reboot to Bootloader . still I need to put the correct pattern to turn off or restart

Only to be sure...
You can not hold both keys to enter Reboot Menu?
Btw.
Maybe if not Top Secret... why not tell complete Model Name?
Like SM-R860 or SM-R870 or?
Best Regards
Edit 1.
User with SM-R890 confirmed this as working...
Because I am not set Security crap like this. Not self tested...
Edit 2.
Visual help... look at 40 seconds... he enters Reboot Menu...
And I see at bottom:
Bootloader unlock...
This is possible with your mystiries Watch?

I did it and worked
I feel kinda stupid but on my previous attempts wasn't working
Many thanks for your support

Not forget to lock again...
Bootloader lock
This makes again FACtory Reset...
But then all "normal" settings...
Best Regards