Related
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
I woke up this morning and my Pixel is dead. Completely unresponsive, can not get into bootloader from the phone.
Any ideas?
I got a replacement ordered through Google, and am using my Nexus 6 for now. It's a little frustrating that they authorize the replacement cost of the phone to process the order when I've got multiple credit cards on file with my Google account (which goes back to when Gmail was invite only) but I'll deal with it.
Just went through this yesterday. Put a hold on my card to replace even though I paid in full for the first one. So now I'm out the cost of 2 and have no phone.
Are you guys still stock?
magnumtripod said:
Are you guys still stock?
Click to expand...
Click to collapse
Yes. Stock. Bootloader unlocking enabled in developer settings but not unlocked. Running the latest OTA.
This is precisely why I always unlock the bootloader immediately after I pull my Nexus (now Pixel) devices from the packaging.
Sorry to hear about the issues. Hope you get your replacements soon.
sn0warmy said:
This is precisely why I always unlock the bootloader immediately after I pull my Nexus (now Pixel) devices from the packaging.
Sorry to hear about the issues. Hope you get your replacements soon.
Click to expand...
Click to collapse
Having the bootloader unlocked would not help in this case, since the phone is completely dead. It will not connect to the computer at all. If I could connect it I could unlock the bootloader through adb and try reinstalling the software. With a complete unresponsive brick, I'm pretty much out of ideas.
atlp99 said:
Having the bootloader unlocked would not help in this case, since the phone is completely dead. It will not connect to the computer at all. If I could connect it I could unlock the bootloader through adb and try reinstalling the software. With a complete unresponsive brick, I'm pretty much out of ideas.
Click to expand...
Click to collapse
Having the bootloader unlocked very well could have helped in this situation, even if the screen won't turn on. There have been a few times that I had phones go completely unresponsive on me and appear to not turn on at all. But following the procedure of booting the phone into the bootloader (power/volume down), allowed me to connect the phone to the computer and communicate with it using fastboot commands. Even with nothing appearing on the phones screen.
This allowed me to fastboot wipe everything and flash a new factory image. The phone booted up just fine afterwards.
Obviously, I can't say with 100% certainty that this would have worked in your case but I've been in your exact situation, more than once, with a phone that was nothing more than a paperweight. Having the bootloader unlocked did solve the problem each time.
sn0warmy said:
Having the bootloader unlocked very well could have helped in this situation, even if the screen won't turn on. There have been a few times that I had phones go completely unresponsive on me and appear to not turn on at all. But following the procedure of booting the phone into the bootloader (power/volume down), allowed me to connect the phone to the computer and communicate with it using fastboot commands. Even with nothing appearing on the phones screen.
This allowed me to fastboot wipe everything and flash a new factory image. The phone booted up just fine afterwards.
Obviously, I can't say with 100% certainty that this would have worked in your case but I've been in your exact situation, more than once, with a phone that was nothing more than a paperweight. Having the bootloader unlocked did solve the problem each time.
Click to expand...
Click to collapse
I didn't say it but I tried that.
The phone doesn't show up at all on the computer. No USB connection at all. If it connected, I could unlock the bootloader through adb and reflash.
atlp99 said:
I didn't say it but I tried that.
The phone doesn't show up at all on the computer. No USB connection at all. If it connected, I could unlock the bootloader through adb and reflash.
Click to expand...
Click to collapse
What? The phone is unresponsive and the screen won't turn on. So there is no way you could unlock the bootloader through ADB because you need the phone's screen functioning in order to check "Yes" for the final prompt of unlocking the bootloader.
With that said, even though the computer doesn't recognize the phone as a USB connection, that doesn't mean it wouldn't communicate with the phone using fastboot commands. Like I said, myself (and many others on this forum) have been in your EXACT situation with a completely unresponsive phone which the computer wouldn't recognize as a connected USB device. However, that didn't stop the computer from recognizing/communicating with the phone via fastboot commands.
It's a moot point now that your replacement is on the way. But I'm still convinced that if your bootloader was unlocked you could have saved the phone.
sn0warmy said:
What? The phone is unresponsive and the screen won't turn on. So there is no way you could unlock the bootloader through ADB because you need the phone's screen functioning in order to check "Yes" for the final prompt of unlocking the boot loader.
With that said, even though the computer doesn't recognize the phone as a USB connection, that that doesn't mean it wouldn't connect to the phone using baseline fastboot commands. Like I said, I've been in your EXACT situation with a completely unresponsive phone and the computer would not prompt me that a new USB device was connected even when the phone was plugged into it. However, that didn't stop the computer from recognizing/communicating with the phone via fastboot commands.
It's a moot point now that your replacement is on the way. But I'm still convinced that if your bootloader was unlocked you could have saved the phone.
Click to expand...
Click to collapse
If it would connect through adb (even if the phone was unresponsive) fastboot OEM unlock would work. I forget off the top of my head what the new command is, but at this point it doesn't respond to that at all.
atlp99 said:
If it would connect through adb (even if the phone was unresponsive) fastboot OEM unlock would work. I forget off the top of my head what the new command is, but at this point it doesn't respond to that at all.
Click to expand...
Click to collapse
"fastboot oem unlock" is just the first part. You still need a responsive phone to unlock the bootloader by hitting 'volume up' and then 'power' as the final step to unlock the bootloader. The computer won't recognize the phone via ADB because the phone is unresponsive and won't power up fully. But just because the computer won't recognize/communicate with the phone via ADB commands, doesn't mean it wouldn't recognize/communicate with it via fastboot commands.
It's pretty common that people have run into an issue where their phone won't recognize ADB commands but still recognizes fast boot commands, especially with bricked phones.
https://www.google.com/search?clien...not+working+but+fastboot+is&ie=UTF-8&oe=UTF-8
I'm telling you, if your bootloader was unlocked, I'd bet money that you would still be able to communicate with your bricked phone using fastboot commands. The inability to communicate with your phone using ADB commands does not negate that.
Possible workaround...
Try holding the power and volume down for 20 seconds no matter what the phone does, or whether you even see anything on the screen, and if you get nothing, then try to do the same with volume up. I have had phones get stuck "in between" modes, for example trying to leave bootloader, recovery, or whatever else, and got stuck on a black screen, when the phone was in fact on. Everyone else's responses here were legit, though. I agree totally on the communicating with the phone via fastboot etc. If you can get it to bootloader even with the screen off, you can flash the entire phone. Of course this means you may lose items saved on the device.
I had this same issue happen...black screen but could hear the phone connect to the computer but fastboot wouldn't work...tried every possible combination oh buttons to get into anything and could...had to replace
http://forum.xda-developers.com/pix...ader-total-t3503963/post69713209#post69713209
Me too.
Well I got the replacement from Google on Wednesday and everything is running fine.
They did send a new phone, in retail packaging with all new chargers and cables. At least it wasn't a refurbished one.
Hi All,
First, thanks for clicking into my question! This is my first post, but I've been lurking here since I used to flash new roms on my original Nexus on a frequent basis, and a Gen1 Kindle Fire before that.
My fiancee is in a bind with her Pixel 2, so I'm hoping you all can help me out.
Her Pixel 2 threw a bunch of app errors over the course of two days, so she opted to reboot -- unfortunately it now locks up at the loading screen, with the Google 'G' and a loader bar (she's running the latest 8.1, pre-Pie) and hangs there, overheating until the battery runs out and we shut it down. We can get into the Recovery menu, but none of the reboot options there seem to help, and there is only the Factory Reset option remaining that we haven't tried.
This happened in the middle of a huge camping excursion as her Bachelorette, so there was limited WiFi and data access to back anything up -- so locked behind that endless boot sequence is a lot of irreplaceable images and video.
What are my options to pull the user data out of there before a factory reset? Is it possible on a (stock, non-root, Google sourced) phone to flash the Pie update? Would that restore functionality?
Can I get to the data somehow through ADB without the phone booting up and unlocked?
Maybe something crazy, like a take a full image of the phone that I then shove on the replacement Pixel 2 that Google is sending us?
Any guidance would be much appreciated!
You could try booting to TWRP with "fastboot boot <filename here>". Then copy the files from there. I'm not sure if this will work if she had the screen locked beforehand though. You could also try flashing the latest factory image but make sure your remove the "-w" from the flash-all.bat file before running the script so it will not wipe user data. Both of these options might not be possible though if you do not have the boot-loader unlocked.
cynnican said:
Hi All,
First, thanks for clicking into my question! This is my first post, but I've been lurking here since I used to flash new roms on my original Nexus on a frequent basis, and a Gen1 Kindle Fire before that.
My fiancee is in a bind with her Pixel 2, so I'm hoping you all can help me out.
Her Pixel 2 threw a bunch of app errors over the course of two days, so she opted to reboot -- unfortunately it now locks up at the loading screen, with the Google 'G' and a loader bar (she's running the latest 8.1, pre-Pie) and hangs there, overheating until the battery runs out and we shut it down. We can get into the Recovery menu, but none of the reboot options there seem to help, and there is only the Factory Reset option remaining that we haven't tried.
This happened in the middle of a huge camping excursion as her Bachelorette, so there was limited WiFi and data access to back anything up -- so locked behind that endless boot sequence is a lot of irreplaceable images and video.
What are my options to pull the user data out of there before a factory reset? Is it possible on a (stock, non-root, Google sourced) phone to flash the Pie update? Would that restore functionality?
Can I get to the data somehow through ADB without the phone booting up and unlocked?
Maybe something crazy, like a take a full image of the phone that I then shove on the replacement Pixel 2 that Google is sending us?
Any guidance would be much appreciated!
Click to expand...
Click to collapse
ADB sideload the latest OTA zip in stock recovery, that should get you up and running again without needing a wipe
crixley said:
ADB sideload the latest OTA zip in stock recovery, that should get you up and running again without needing a wipe
Click to expand...
Click to collapse
Thank you! I'll be giving this a try as soon as she's home on Monday.
Does recovery mode automatically enable the USB Debugging that ADB uses?
cynnican said:
Thank you! I'll be giving this a try as soon as she's home on Monday.
Does recovery mode automatically enable the USB Debugging that ADB uses?
Click to expand...
Click to collapse
Yep you can sideload without needing it toggled in developer mode
crixley said:
Yep you can sideload without needing it toggled in developer mode
Click to expand...
Click to collapse
This worked perfectly, thank you!
cynnican said:
This worked perfectly, thank you!
Click to expand...
Click to collapse
I'm glad to hear! Nothing worse than having to wipe and losing important things you can't get back. I've had that happen a few times. Happy to help.
I'm not very technical - please keep this in mind with my query below.
I have a Pixel 2 which overnight stopped working - my guess is that it rebooted due to an automated software update.
I now only get the page with the robot on it's back.
Options in green on this page are Barcodes, Power Off, and Start.
After reading a lot online I've tried all the usual key press combinations to no avail.
I've also downloaded ADB and FASTBOOT to my Mac.
ADB doesn't see the phone when plugged in via USB (ie. ADB DEVICES doesn't return anything)
FASTBOOT DEVICES does, however, show the serial number as listed on the page with the robot on it's back (and the -l option adds "usb:" plus an 8 digit number and the letter "X"
FASTBOOT REBOOT restarts the phone and brings me back to the robot on it's back page.
Other information on the Robot on it's back page include -
Product Revision: walleye MP1
Boot-slot: b
Console: DISABLED
Secure Boot: yes (PRODUCTION)
Device State: locked
Advice online suggests I need to unlock the phone, so I've tried FASTBOOT FLASHING UNLOCK, and FASTBOOT OEM UNLOCK but neither work.
When I try these I get "FAILED (remote: Flashing Unlock is not allowed)"
An article on Android Police suggests this may have been a bug on the Pixel 2 originally and that it's now resolved.
Unfortunately, my cat 22 situation seems to be that I need to do a factory reset, but the steps I've found as to how to do a factory reset all lead back to the Robot on it's back page, so I can't see how to move forward to with recovering my phone?
Can anyone help please?
Really frustrated that my new phone can put itself into this state without me having done anything and that it's seemingly impossible to recover from this state now that it's in it.
At very least I'd like to wipe all data from the phone so I can send it off for repair.
Thanks in advance.
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.
My GW4 recovery is broken after tried to reboot to recovery via ADB.
I tried to sideload pixel watchface apk using "adb reboot recovery sideload" to enter sideload mode as per ADB syntax guide...
It didn't work and just show big red circle with white exclamation mark.
After that, i managed to boot the watch using HW button reset method, but looks like my recovery is damaged and now i cannot update the watch anymore.
I have tinkering with ADB on phone many times before, and from my experience this kind of command is harmless (at worse it just reboot the phone).
Appreciate if anyone have experience on this and advice if there is any workaround....
Should have used simple sideloader app with debugging over wifi. Anyway damage is done but you can flash same firmware which your watch having right now and set it up as new.
If you can hold both Hardware Keys to reach Reboot Mode/Menu...
And you see:
Bootloader unlock
Then do this.
It makes some kind of Factory Reset....
Not forget lock again... in this menu:
Bootloader lock
It not kill Knox... NOT flash something...
Only unlock... lock... to do some Reset... which fixes few things...
Good Luck.
Bootloader menu not inside US LTE devices like SM-R875UUUUUUU like USA...
Best Regards
ReX-Hell2heAven said:
Should have used simple sideloader app with debugging over wifi. Anyway damage is done but you can flash same firmware which your watch having right now and set it up as new.
Click to expand...
Click to collapse
Tried to enter "Download (Wireless)" mode but same error appears... Dont think i can flash anything from the bootloader now... will try @adfree suggestions and see if it can save me a trip to Samsung Customer center...
adfree said:
If you can hold both Hardware Keys to reach Reboot Mode/Menu...
And you see:
Bootloader unlock
Then do this.
It makes some kind of Factory Reset....
Not forget lock again... in this menu:
Bootloader lock
It not kill Knox... NOT flash something...
Only unlock... lock... to do some Reset... which fixes few things...
Good Luck.
Bootloader menu not inside US LTE devices like SM-R875UUUUUUU like USA...
Best Regards
Click to expand...
Click to collapse
Works like a charm!!
Thanks for the suggestion....