Related
DISCLAMER and WARNING: I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or the current economic crisis. Please do some research if you have any concerns about this app.
Click to expand...
Click to collapse
Story:
Just received Sony Smartwatch 3 and decided to oem unlock for future so once root available I would not need to reset device.
Enabled adb
manually specified correct drivers in device manager
rebooted to bootloader using adb reboot bootloader
entered fastboot oem unlock twice and watch rebooted
but got stuck on boot for whatever reason.
I tried all the methods to get into fastboot (Swiping diagonal as on LG watch, and together with power button as on samsung ) to no avail.
The only other mode I was able to get into - s1 flash device w/o drivers.
Found Sony Emma software to work with unlocked Xperia, and after its installation it said that bootloader is locked and I need to either update from sony site or unlock bootloader first!
Installed Sony PC Companion software, but software update while listing smartwatch 3 said that there is no firmware for it.
After googling random forums on bootlooping sony xperias found that to reset device you need to click "repair my phone/tablet" in Phone/Tablet Software Update section
Click to expand...
Click to collapse
Guide to unbrick bootlooping SWR50 that is able to get into s1 bootloader/flash mode:
1. Power off device by holding power key until it reboots and then switches off with few vibrations
2. Connect to computer and check device manager - you should see unknown device
3. Install Sony PC Companion from this website http://www.sonymobile.com/us/tools/pc-companion/
Check if driver appeared in the Device Manager, e.g. unknown device will disappear and something like SEFLash will appear under usb controllers
If driver is still not found - try to install Emma (http://developer.sonymobile.com/services/flash-tool/) and get this driver to work
4. Go into PC Companion and click on "Support Zone", it will be downloaded
5. Then click on "Accessories software update" and try to update Smartwatch 3 (We might get new versions in the future, so it will be easiest to do so)
UPDATE: Now you can reflash from Accessories page, it will ask if you want to refrlash. Keeping steps bellow for information purposes.
6. If #5 not working:
Click on "Phone/Tablet Software Update" (yes, silly), click on "repair my phone/tablet", click Continue and Agree to all licenses, etc....
7. Once presented by the list of phones - Select anything I guess, but I selected Xperia Z2, it should start downloading and then updating.
8. Once done it will say build number watch was flashed, in my case it was KNX01V
9. Disconnect watch and boot it.
P.S. I guess they show phone selection just to provide instructions how to get into download mode and then flash based on the versions from bootloader.
P.P.S I'm glad I tried this last resort thing after being ready to deal with verizon support and waiting for new watch...
I've found that formatting cache and userdata partition like it says in the link below makes the device boot as expected:
source.android.com -> /source/building-devices.html#unlocking-the-bootloader
(sorry for faulty link, new user)
Good to know, I decided to wait a bit as I was eager to play with new toy.
Will unlock tomorrow if it is still locked after Sony reset.
And looks like I would have to write my own apps to test GPS and sensors performance.
And the good news is fastboot state unlocked after stock reflash.
XorZone said:
manually specified correct drivers in device manager
Click to expand...
Click to collapse
Can you please elaborate on which driver you used to get access to the Smartwatch 3 via ADB? I am trying to use the latest google USB driver, but the device is showing up as offline listed under "adb devices". Just tried the latest ADB v1.0.32 and it seems the watch shows up as "unauthorized". Did you see an ADB notification on the watch that you had to accept, because I am not seeing anything like that.
NVM, it started working after I restarted adb server like 25 times...
Device offline usually is not about driver. But I hit on device and manually picked google-adb composite device
OK, bricked watch today with corrupted /system and boot process hanged with non responsive power button. Had to wait for discharge and it was pita to get into flashmode with enough juice, because after black screen charging it boots instead of going into kernel charging.
Anyway it is up and running and has ROOT now!
Will upload files and create guide as soon as I will be with good internet.
See my sig!
*delete*
*deleted*
Well, there are different levels of bootloaders
At least Sony s1 flash, fastboot, kernel...
To flash with PC companion you need to boot into s1 by powering off and then hold power and connect to USB once sony logo shown (you should see black screen with backlight on). Make sure you sit on PC companion update screen and that watch had enough juice.
With charging there are different levels of charging:
1. Battery dead
2. Boot loader charging (about 4 min from USB port) with black screen
3. Kernel charging either offline (if you powered off before) or boot and operational charging.
When #2 charges it will boot kernel and if kernel or system is broken it might hang and discharge.
But you can force into s1 flash mode before it boots into kernel. Or if you lucky you could power on and power off before it boots and hang.
In my case I had not enough juice to flash it and watch didn't react to button in kernel mode, so I had to wait for discharge, then plugged into USB and start timer, figured it boots after ~3min 55sec. So I opened PC companion update screen, waited 3:53 and disconnected watch, then hold power button and connect to PC after 5 sec and was able to flash.
To power off - just hold power button until it reboots and continue holding until it vibrates 3 times.
Good luck
XorZone said:
Story:
Guide to unbrick bootlooping SWR50 that is able to get into s1 bootloader/flash mode:
1. Power off device by holding power key until it reboots and then switches off with few vibrations
2. Connect to computer and check device manager - you should see unknown device
3. Install Sony PC Companion from this website http://www.sonymobile.com/us/tools/pc-companion/
Check if driver appeared in the Device Manager, e.g. unknown device will disappear and something like SEFLash will appear under usb controllers
If driver is still not found - try to install Emma (http://developer.sonymobile.com/services/flash-tool/) and get this driver to work
4. Go into PC Companion and click on "Support Zone", it will be downloaded
5. Then click on "Accessories software update" and try to update Smartwatch 3 (We might get new versions in the future, so it will be easiest to do so)
UPDATE: Now you can reflash from Accessories page, it will ask if you want to refrlash. Keeping steps bellow for information purposes.
6. If #5 not working:
Click on "Phone/Tablet Software Update" (yes, silly), click on "repair my phone/tablet", click Continue and Agree to all licenses, etc....
7. Once presented by the list of phones - Select anything I guess, but I selected Xperia Z2, it should start downloading and then updating.
8. Once done it will say build number watch was flashed, in my case it was KNX01V
9. Disconnect watch and boot it.
P.S. I guess they show phone selection just to provide instructions how to get into download mode and then flash based on the versions from bootloader.
P.P.S I'm glad I tried this last resort thing after being ready to deal with verizon support and waiting for new watch...
Click to expand...
Click to collapse
This method is windows only. Is there no cross-platform way to do it?
I did the stupid thing.. and ended up with a softbricked phone.
Sony PC Companion did the trick for me!
I tried doing it through VMWare on my macbook, but didn't seem to work at all.
On windows it was plug'n'Pray
Sony companion will not let me restore my SW50. Detects it and tells me that the software is updated. If I try from the menu to repair phone, it makes me accept all agreements and finally tells me the same thing no updates.
Is in bootloop and do not start after open bootloader
My sw3 is in bootloop.I uesd your guide but still can't repair my watch. I tried many time to use pc companion but always got the same wrong message,wrong code(100) which couldn't connect to the Internet.
@swidon @KONG8691
I find myself in the same situation, you have found a solution to the problem?
Thanks for your help
best regards
jerry_italia said:
@swidon @KONG8691
I find myself in the same situation, you have found a solution to the problem?
Thanks for your help
best regards
Click to expand...
Click to collapse
Yes!, follow these instructions and you can enter in fastboot or recovery and flash a new firmware:
Detach any USB cable connected to the watch
Turn it off holding the power button and keep holding the button until the watch vibrates three times and then switches it off
Press the power button and keep holding. A blue screen that prompts to insert an USB cable will display
Double tap the power button
A black menu will display, with on-screen instructions
Move to Fastboot or Recovery Mode pressing the power button, once a time
Select Fastboot (or Recovery) by double pressing the power button
Good luck bro.
swidon said:
Yes!, follow these instructions and you can enter in fastboot or recovery and flash a new firmware:
Detach any USB cable connected to the watch
Turn it off holding the power button and keep holding the button until the watch vibrates three times and then switches it off
Press the power button and keep holding. A blue screen that prompts to insert an USB cable will display
Double tap the power button
A black menu will display, with on-screen instructions
Move to Fastboot or Recovery Mode pressing the power button, once a time
Select Fastboot (or Recovery) by double pressing the power button
Good luck bro.
Click to expand...
Click to collapse
you are my hero... stock recovery flashed and sw3 reboot! thankyou so much bro
jerry_italia said:
you are my hero... stock recovery flashed and sw3 reboot! thankyou so much bro
Click to expand...
Click to collapse
How do you go about getting stock recovery back at the moment I'm on 5.0.1 and I can't ota update to 5.1.1 because it thinks its on 5.1.1 when it's not the only way I can think of updating it is to get stock recovery then sideload the ota zip on stock recovert but I can't do that with TWRP can someone help?
Hi,
My watch boot loops on the marshmelow boot animation after I Got marshmelow
I tried XorZone instractions and it said it re-updated image. but it will boot looped.
I tried to factory reset from the menu (double tap at download screen then go factory reset).... didn't work. still boot loops.
I see I can go to fastboot or recovery, but what do I do there? Any instructions I can follow to try to revive my watch please? thanks.
wonderfull!
XorZone said:
Well, there are different levels of bootloaders
At least Sony s1 flash, fastboot, kernel...
To flash with PC companion you need to boot into s1 by powering off and then hold power and connect to USB once sony logo shown (you should see black screen with backlight on). Make sure you sit on PC companion update screen and that watch had enough juice.
With charging there are different levels of charging:
1. Battery dead
2. Boot loader charging (about 4 min from USB port) with black screen
3. Kernel charging either offline (if you powered off before) or boot and operational charging.
When #2 charges it will boot kernel and if kernel or system is broken it might hang and discharge.
But you can force into s1 flash mode before it boots into kernel. Or if you lucky you could power on and power off before it boots and hang.
In my case I had not enough juice to flash it and watch didn't react to button in kernel mode, so I had to wait for discharge, then plugged into USB and start timer, figured it boots after ~3min 55sec. So I opened PC companion update screen, waited 3:53 and disconnected watch, then hold power button and connect to PC after 5 sec and was able to flash.
To power off - just hold power button until it reboots and continue holding until it vibrates 3 times.
Good luck
Click to expand...
Click to collapse
hello
i searched the whole internet but there are not much informations about this Phone so i thought i make a new Thread
about the panasonic DCM-CM1 Factory Reset.
please write here any informations and experience you have about the Panasonic DMC-CM1
i never saw someone on youtube google or any other side or anyone who can tell me how to do a Factory Reset with this phone
today i called 5 Panasonic service numbers but noone can help, i also called about 10 Phone Service points for repair no one can help.
i tryed so much with this phone and i finaly found that the CM1 have a Secret key combination to connect it with USB as a Android ADB Interface without having acces to the phone cause it is screen locked.
1 .Turn Phone off
2. press Camera + Volume-up + Power ( Hold )
3. while Holding connect USB. (Hold)
4 .the LED should go green for maybe 2 seconds release all bottons while the led is green before it turns off and then the LED must still green.
then windows found a Android ADB Interface
if im in android SDK Tools i the phone will be found in fastboot!
if i type Fastboot Devices
the other thing i know is how to start in Save mode.
but this is nothing to help with a lost pin.. it only starts the phone without apps that have been installed by the user.
maybe for deinstalling a app or a buggy app.. dont know..
start phone at the screen for the pin or at the home menu..press the power botton hold for 2-4 seconds or so it ask for Shut down Restart and so.. just press and hold Shut down. and then it ask you if you want to start in Save mode. then press yes.
2 weeks ago i wanted to make a Screen lock with a pin for more secure.. i cant remeber the pin anymore thats why i want to make a Factory reset i think im not the only one. so any information would be nice
if there is someone who made Factory Reset with this phone or was able to start in fast boot or anything.. please share the infos with us!
thank you.
Hi.
I have a Xiaomi mi5s 64/3 GB in an endless bootloop. Here are the details:
The phone is:
rooted
bootloader unlocked
developer mode enabled
internal storage *not* encrypted
no MIUI account activated
USB debugging on
running the last EU MIUI 9.x development version (don't remember the exact version) with Android 7.0
has TWRP 3.2.1.0 and supersu 2.82
no password is set for unlocking the screen etc.
For some unknown reason the phone suddenly rebooted yesterday and got into an infinite bootloop cycle. I haven't changed any roms recently or done any such flashing. My google play automatic updates were disabled, but a few days ago I manually updated all the apps.
The only odd thing that happened prior to this bootloop, was that when shooting some photos with the google camera mod (same one I've been using for the past few weeks), 2 images were saved as corrupt unreadable files. But that happened a few hours before the bootloop suddenly started.
The current status is:
1. I cannot turn the power off (tried holding the power button, or power button + vol up and down for a very long time --> nothing).
2. I cannot enter recovery mode using vol up + power.
3. I cannot enter EDL using all 3 buttons.
4. If I hold volume down, it enters fastboot but automatically exits from it within 4 seconds (ADB and miflash cannot detect the device in this short period of time). holding the volume down button for a long time has a repating enter-exit-after-4-seconds from the fastboot graphics.
I waited until the battery was completely dead, than started charging it and the status described above was unchanged.
QUESTION 1 - restoring the internal data is my number one priority - does it seem possible here?
To be exact: I want the DCIM folder with the photos+ videos. What should I try now?
QUESTION 2 - I ordered an EDL cable, but am unsure if it supported for my MIUI version. if the EDL cable works, can I force the phone to enter recovery mode from within EDL?
If so - I guess I can copy the internal data to an external USB OTG flash drive I have (that works well with the phone).
If my data is restored, I will then move onto trying to reflash the phone, but at this point this is the least of my worries...
Thanks all.
Anyone?
Maybe it's a problem with the button? I would disassembly the phone and check the hardware.
bedson87 said:
Maybe it's a problem with the button? I would disassembly the phone and check the hardware.
Click to expand...
Click to collapse
I don't know - the buttons don't seem like they are stuck in any way. When I push them, they click back out as usual.
Update - I created an EDL flash cable by stripping the cable gently, exposing the green and black wires, and looping them together - connecting this cable to the phone didn't help either.
Maybe I need to wait for the battery to die so the phone will turn off, connect this cable to the phone, keep the power button pressed while I connect it to the usb port in my PC... what do you think?
I have the same problem with mi 5s which started after update. Don't know what to do.
Took the phone to a local lab - it was all due to a faulty power button module.
Hi there,
I am looking for some guidance on my bricked Pixel 6 Pro.
I transfered the data from my old pixel, but then decided to do a full flash to refresh. Downloaded the stock image from google, used the fastboot-all script to flash the phone, but as soon as it was done, I never reboot. my phone is looking completely dead since.
Attempt # 1
- black screen, with no sound to any actions of response to any key combination (power or volume keys).
- tried holding the power button for 60 secs, no response
- tried holding power and volume down, no response
- tried holding power and volume up, no response
- when I plug the phone on charge, no response. neither the charging display.
Atempt # 2
- Only time the phone shows some sign of life, is when I connect the phone to my PC, it makes a sound of detecting a device, but then instantly it get a disconnect sound, (in 2-3 sec).
- I tried holding the power button, while plugged in. it makes a sound of usb detection, (but no visual response on the phone) after holder for 30 secs, it makes another sound of usb detach.
- While I am experimentating with PC connection, I also tried fastboot reboot command, it only shows waiting for a device and nothing happens, either on the console or phone.
Not sure, if I have bricked the bootloader, and if yes, what can be done? Any guidance in this regards will be highly appreciated.
Thanks
Call whoever you bought the phone from and do warranty claim.
I struggled with a soft bricked / bootlooping phone after removing Magisk. Although my phone at least booted to bootloader and a connection via fastboot was working, the factory images wouldn't flash properly. Google support couldn't help me and I thought I had to send it to repair.
In the end I could solve the issue by switching to the Android SDK 31. I know your case is different, because your phone is bricked worse than mine was, but you could give it a try.
Baumhouse said:
I struggled with a soft bricked / bootlooping phone after removing Magisk. Although my phone at least booted to bootloader and a connection via fastboot was working, the factory images wouldn't flash properly. Google support couldn't help me and I thought I had to send it to repair.
In the end I could solve the issue by switching to the Android SDK 31. I know your case is different, because your phone is bricked worse than mine was, but you could give it a try.
Click to expand...
Click to collapse
rao_hamza said:
Hi there,
I am looking for some guidance on my bricked Pixel 6 Pro.
I transfered the data from my old pixel, but then decided to do a full flash to refresh. Downloaded the stock image from google, used the fastboot-all script to flash the phone, but as soon as it was done, I never reboot. my phone is looking completely dead since.
Attempt # 1
- black screen, with no sound to any actions of response to any key combination (power or volume keys).
- tried holding the power button for 60 secs, no response
- tried holding power and volume down, no response
- tried holding power and volume up, no response
- when I plug the phone on charge, no response. neither the charging display.
Atempt # 2
- Only time the phone shows some sign of life, is when I connect the phone to my PC, it makes a sound of detecting a device, but then instantly it get a disconnect sound, (in 2-3 sec).
- I tried holding the power button, while plugged in. it makes a sound of usb detection, (but no visual response on the phone) after holder for 30 secs, it makes another sound of usb detach.
- While I am experimentating with PC connection, I also tried fastboot reboot command, it only shows waiting for a device and nothing happens, either on the console or phone.
Not sure, if I have bricked the bootloader, and if yes, what can be done? Any guidance in this regards will be highly appreciated.
Thanks
Click to expand...
Click to collapse
rao_hamza said:
Hi there,
I am looking for some guidance on my bricked Pixel 6 Pro.
I transfered the data from my old pixel, but then decided to do a full flash to refresh. Downloaded the stock image from google, used the fastboot-all script to flash the phone, but as soon as it was done, I never reboot. my phone is looking completely dead since.
Attempt # 1
- black screen, with no sound to any actions of response to any key combination (power or volume keys).
- tried holding the power button for 60 secs, no response
- tried holding power and volume down, no response
- tried holding power and volume up, no response
- when I plug the phone on charge, no response. neither the charging display.
Atempt # 2
- Only time the phone shows some sign of life, is when I connect the phone to my PC, it makes a sound of detecting a device, but then instantly it get a disconnect sound, (in 2-3 sec).
- I tried holding the power button, while plugged in. it makes a sound of usb detection, (but no visual response on the phone) after holder for 30 secs, it makes another sound of usb detach.
- While I am experimentating with PC connection, I also tried fastboot reboot command, it only shows waiting for a device and nothing happens, either on the console or phone.
Not sure, if I have bricked the bootloader, and if yes, what can be done? Any guidance in this regards will be highly appreciated.
Thanks
Click to expand...
Click to collapse
Bootloader unlocked?
cultofluna said:
Bootloader unlocked?
Click to expand...
Click to collapse
If I remeber correctly flashing factory images forces you to unlock the device. So yes, the bootloader of rao_hamza's device should be unlocked.
From memory you can revive it through QPST and orher Qualcomm utilities, however hard part is to get the files. the phone is too new and many shops dont have the unlock tools yet.
" While I am experimentating with PC connection, I also tried fastboot reboot command, it only shows waiting for a device and nothing happens, either on the console or phone. " - this is still good news, as phone is being detected by windows, try to install Qualcomm drivers and see if you can get it to boot into EDL. GOOD LUCK.
Pixel 6 uses Google's own new Tensor chip - so no Qualcomm tools
Like @Baumhouse I went through something similar. Two things for me: it took way longer to hold power and volume down than any other phone I've owned. I was seriously concerned I wasn't going to get there. Two, the factory images all made it to fastbootd and then failed all because I hadn't updated to the latest SDK.
Just throwing this out in hopes you don't have to send it back.
What @ridobe said. Make sure you're using the latest official Google Platform Tools (there's a link in my thread at the top of my signature below if you need it, or just Google for it). If I had a nickel every time someone didn't update the tools when they went to use them...
roirraW edor ehT said:
What @ridobe said. Make sure you're using the latest official Google Platform Tools (there's a link in my thread at the top of my signature below if you need it, or just Google for it). If I had a nickel every time someone didn't update the tools when they went to use them...
Click to expand...
Click to collapse
This and a bad/wrong cable seem to be the most common culprits
ridobe said:
Like @Baumhouse I went through something similar. Two things for me: it took way longer to hold power and volume down than any other phone I've owned. I was seriously concerned I wasn't going to get there. Two, the factory images all made it to fastbootd and then failed all because I hadn't updated to the latest SDK.
Just throwing this out in hopes you don't have to send it back.
Click to expand...
Click to collapse
Any idea how long you had to hold that button combinaiton? I tried longer, maybe 60 sec, but still no response from the phone.
tids2k said:
From memory you can revive it through QPST and orher Qualcomm utilities, however hard part is to get the files. the phone is too new and many shops dont have the unlock tools yet.
" While I am experimentating with PC connection, I also tried fastboot reboot command, it only shows waiting for a device and nothing happens, either on the console or phone. " - this is still good news, as phone is being detected by windows, try to install Qualcomm drivers and see if you can get it to boot into EDL. GOOD LUCK.
Click to expand...
Click to collapse
What is EDL? and had the Google usb drivers installed, to get the fastboot working.
Baumhouse said:
I struggled with a soft bricked / bootlooping phone after removing Magisk. Although my phone at least booted to bootloader and a connection via fastboot was working, the factory images wouldn't flash properly. Google support couldn't help me and I thought I had to send it to repair.
In the end I could solve the issue by switching to the Android SDK 31. I know your case is different, because your phone is bricked worse than mine was, but you could give it a try.
Click to expand...
Click to collapse
Yes, I don't know who to get into a bootloader in this situation, if that were working I would have some hope.
If you can get to the bootloader you can use google's flashing website, flash.android.com. I just use that to go back to stock, even with an unlocked bootloader.
pysklona said:
If you can get to the bootloader you can use google's flashing website, flash.android.com. I just use that to go back to stock, even with an unlocked bootloader.
Click to expand...
Click to collapse
Thanks @pysklona. you are right, but the problem is I can't get into the bootloader. This is what I am seeking help for.
rao_hamza said:
Thanks @pysklona. you are right, but the problem is I can't get into the bootloader. This is what I am seeking help for.
Click to expand...
Click to collapse
Sorry, misread the post.
@pysklona came here because I'm in the same boat, hard-bricked my device after running the flash-all script. Was using the most recent version of platform tools and the brand new cable that came with the phone.
Was getting the same result, attaching it to a windows pc makes the attached device chime, but disconnects after a few seconds. It came up first as "Setting up Pixel ROM Recovery". I let it sit overnight and now it doesn't auto-disconnect and I get a serial device under com3 on windows. Attaching it to macos gives me a "Pixel ROM Recovery" device. Despite "recovery" in the name, I think it's actually in EDL mode, not recovery mode. No devices come up for adb or fastboot on windows, linux or macos. Screen is completely blank no matter what.
Not being a Qualcomm chip makes this whole process from here a bit of an unknown, but will assume the process for recovery is more or less the same. Looking into QPST/MsmDownloadTool/OpenPST, although as pointed out, I'm not sure any of those tools will work since this isn't a qualcomm chip. MsmDownloadTool is for oneplus, but maybe something can be modded.
ootri said:
@pysklona came here because I'm in the same boat, hard-bricked my device after running the flash-all script. Was using the most recent version of platform tools and the brand new cable that came with the phone.
Was getting the same result, attaching it to a windows pc makes the attached device chime, but disconnects after a few seconds. It came up first as "Setting up Pixel ROM Recovery". I let it sit overnight and now it doesn't auto-disconnect and I get a serial device under com3 on windows. Attaching it to macos gives me a "Pixel ROM Recovery" device. Despite "recovery" in the name, I think it's actually in EDL mode, not recovery mode. No devices come up for adb or fastboot on windows, linux or macos. Screen is completely blank no matter what.
Not being a Qualcomm chip makes this whole process from here a bit of an unknown, but will assume the process for recovery is more or less the same. Looking into QPST/MsmDownloadTool/OpenPST, although as pointed out, I'm not sure any of those tools will work since this isn't a qualcomm chip. MsmDownloadTool is for oneplus, but maybe something can be modded.
Click to expand...
Click to collapse
Thanks for sharing your experience. I just returned the device and got myself a new one.
anyways, i am not sure what is causing this hard brick. thats is something we all should be careful about it.
same thing here. pixel 6 from google store. magisk installed on the december update and i downgraded to the november one using the flash-all.bat script. phone reboots and am told the software is corrupt
reboot back into fastboot mode, run the script again. and get this software is corrupt message again
this time I cant' even boot into fastboot/bootloader mode. and plugging the phone into windows gives me the "pixel rom recovery" message
phone seems dead (black screen, not responding to hardware buttons)
any other solutions than to get it replaced?
Hmm, maybe plug it in to a PC via USB to supply it with power (maybe the battery is down) and just do a very long press of the power button - at least 30 seconds - until the phone starts up. If it does and isn't in fastboot you could try "Power-VolDown" to get into fastboot...
If it just doesn't react to all of this and waiting a bit (in case the battery was at 0% and needs some minimal charge) I think a replacement is the only way to go....
Enddo said:
same thing here. pixel 6 from google store. magisk installed on the december update and i downgraded to the november one using the flash-all.bat script. phone reboots and am told the software is corrupt
reboot back into fastboot mode, run the script again. and get this software is corrupt message again
this time I cant' even boot into fastboot/bootloader mode. and plugging the phone into windows gives me the "pixel rom recovery" message
phone seems dead (black screen, not responding to hardware buttons)
any other solutions than to get it replaced?
Click to expand...
Click to collapse
You could try Official Google Android Flash Tool. It's merely another method of doing what you effectively tried, but from what I've read, it's helped some folks. Sadly, others have reported that the Official Google Pixel Update and Software Repair hasn't been updated for the P6P yet.
If that doesn't help, hang in there. There are others in here who will likely have even better advice.
roirraW edor ehT said:
You could try Official Google Android Flash Tool. It's merely another method of doing what you effectively tried, but from what I've read, it's helped some folks. Sadly, others have reported that the Official Google Pixel Update and Software Repair hasn't been updated for the P6P yet.
If that doesn't help, hang in there. There are others in here who will likely have even better advice.
Click to expand...
Click to collapse
appreciate the links. right now, I can't even get into fastboot/bootloader mode. so neither of those tools detect the phone.
@s3axel the battery definitely isn't low. I charged it up before all this specifically so that I know it had plenty of juice (was at 93% or something).
I'm thinking maybe after letting the battery die, charging it back up will let me boot into a special boot mode
but any other ideas, please, I'm all ears
Hi - I was installing some external memory, a 16gb Sandisk USB memory stick. The fire cube recognised it straight away & I proceeded to format it as ‘internal storage’. I got a msg to say that the format was complete. The TV screen then flashed & the next thing the fire cube re-booted & all I have is an Android Recovery screen. I’ve tried the mute + the volume down for 60 secs. None of the keys on the remote are doing anything nor are any of the buttons on the fire cube.
Can anybody help or is this bricked due to the software version?
All there is for recovery options on stock 2nd gen Cube's is safe mode and fastboot. Holding vol down on the Cube (not remote) during boot up during the second animated Amazon logo puts it in safe mode.
Fastboot is useless for anyone that's not Amazon because they blocked all the useful fastboot commands like flash and boot.
Did you try using the Cube buttons to select factory reset? If the cube buttons don't work, plug in a keyboard and use that.
Finnzz said:
All there is for recovery options on stock 2nd gen Cube's is safe mode and fastboot. Holding vol down on the Cube (not remote) during boot up during the second animated Amazon logo puts it in safe mode.
Fastboot is useless for anyone that's not Amazon because they blocked all the useful fastboot commands like flash and boot.
Did you try using the Cube buttons to select factory reset? If the cube buttons don't work, plug in a keyboard and use that.
Click to expand...
Click to collapse
Hi - Yes, I’ve tried the mute & volume down button on the cube & held down for 60+ seconds. Nothing happened. It does seem to know when a key is pressed because if I press the right hand button with a circle on it, the ‘try again’ turns green. I’ve tried a keyboard attached via a OTG cable & that didn’t do anything…
Clubcard said:
if I press the right hand button with a circle on it, the ‘try again’ turns green.
Click to expand...
Click to collapse
Does the device reboot after you release the button after 'try again' turns green? If so, that means that 'try again" was selected and executed. If not, did you try not only pressing that button, but also holding it (long press) after the selection turns green? The typical way the recovery menu works is that the first moments of the button being pressed highlights the selection (by turning the selection green), and then the continued (without interruption) holding of the button (and eventual release of the button) actually selects and executes the highlighted selection.
Navigation of the recovery menu is usually done using a short press of the same button. You'll need to navigate to the other menu selection 'factory data reset', and then use a long press (and eventual release) to select and execute that selection.
Clubcard said:
I’ve tried a keyboard attached via a OTG cable & that didn’t do anything…
Click to expand...
Click to collapse
Try the keyboard both with and without an OTG cable, and in each of those cases, externally powering the keyboard (using some sort of split usb cable) because power may not be supplied to the usb port while in the recovery menu.
Functioner said:
Does the device reboot after you release the button after 'try again' turns green? If so, that means that 'try again" was selected and executed. If not, did you try not only pressing that button, but also holding it (long press) after the selection turns green? The typical way the recovery menu works is that the first moments of the button being pressed highlights the selection (by turning the selection green), and then the continued (without interruption) holding of the button (and eventual release of the button) actually selects and executes the highlighted selection.
Navigation of the recovery menu is usually done using a short press of the same button. You'll need to navigate to the other menu selection 'factory data reset', and then use a long press (and eventual release) to select and execute that selection.
Try the keyboard both with and without an OTG cable, and in each of those cases, externally powering the keyboard (using some sort of split usb cable) because power may not be supplied to the usb port while in the recovery menu.
Click to expand...
Click to collapse
Hi - It’s unplugged as all the cube is doing is flashing blue all the time. When I apply power, I get the FireTv logo & then the Android recovery screen comes up. The cube doesn’t do anything. When the ‘try again‘ hightlights green, nothing I do will make it reboot. I’ve pressed every button on the remote & all the buttons on the cube.
The USB on the back is a micro USB & all I have is a USB keyboard which is why I had to connect it via the OTG I had. I’ve attached a photo. I do have a different OTG cable which has a micro USB input for a power supply. I’ve tried that & the keyboard has power but I still can’t select the factory reset..
I will corrupt the data partition on my spare gen2 cube device so that I can check what it takes to make navigation of the recovery menu work.
Functioner said:
I will corrupt the data partition on my spare gen2 cube device so that I can check what it takes to make navigation of the recovery menu work.
[/QUOTE
It’s very good of you to do that but it’s rather extreme. What if you brick yours?
Click to expand...
Click to collapse
My raven device has DFU functionality. Yours most certainly does not. It would be very unlikely that I wouldn't be able to recover it.
Functioner said:
My raven device has DFU functionality. Yours most certainly does not. It would be very unlikely that I wouldn't be able to recover it.
Click to expand...
Click to collapse
Hi - Have you managed to sort anything out yet?
tengo el mismo caso lograste resolverlo?
Clubcard said:
Hi - Have you managed to sort anything out yet?
Click to expand...
Click to collapse
I was able to reproduce the issue on my device. My device booted to the recovery menu as shown in the OP.
Unfortunately, you're quite correct. There is no way to navigate the menu or execute either of the options shown in the menu. You should ask amazon to replace your device.
Functioner said:
I was able to reproduce the issue on my device. My device booted to the recovery menu as shown in the OP.
Unfortunately, you're quite correct. There is no way to navigate the menu or execute either of the options shown in the menu. You should ask amazon to replace your device.
Click to expand...
Click to collapse
Unfortunately it’s 18 months old & all Amazon are prepared to offer is 15% discount..
Clubcard said:
Unfortunately it’s 18 months old & all Amazon are prepared to offer is 15% discount..
Click to expand...
Click to collapse
The fact that the device could boot to this unrecoverable mode at all is a programming mistake that is the fault of amazon or its agents. The probability of it happening seems to have increased with the newest firmware version, as a few others have posted to xda recently with claims of the same issue. If it becomes more widespread, amazon may be forced to address the matter with something other than a trivial discount. You may want to consider holding on to your device in the event that this happens.
I'm still investigating the matter. There is some evidence in the recovery code of infrared remote code support for the recovery menu, but I blasted a wide range of codes, and there is no evidence in the log that any of them are even being received. I have tested the keyboard possibilities thoroughly, but not exhaustively. I may turn up something later but my confidence level is not high.
Functioner said:
The fact that the device could boot to this unrecoverable mode at all is a programming mistake that is the fault of amazon or its agents. The probability of it happening seems to have increased with the newest firmware version, as a few others have posted to xda recently with claims of the same issue. If it becomes more widespread, amazon may be forced to address the matter with something other than a trivial discount. You may want to consider holding on to your device in the event that this happens.
I'm still investigating the matter. There is some evidence in the recovery code of infrared remote code support for the recovery menu, but I blasted a wide range of codes, and there is no evidence in the log that any of them are even being received. I have tested the keyboard possibilities thoroughly, but not exhaustively. I may turn up something later but my confidence level is not high.
Click to expand...
Click to collapse
OK, thanks. The standard control/alt/delete as used on a PC works in that it reboots the cube. I couldn’t get anything else to work..
Clubcard said:
OK, thanks. The standard control/alt/delete as used on a PC works in that it reboots the cube. I couldn’t get anything else to work..
Click to expand...
Click to collapse
What happens if you hold the volume up key on the Cube during boot, to boot to fastboot, connect your computer via USB, and type fastboot continue?
Pro-me3us said:
What happens if you hold the volume up key on the Cube during boot, to boot to fastboot, connect your computer via USB, and type fastboot continue?
Click to expand...
Click to collapse
Hi - Will check that out later when I finish work. Thanks..
Clubcard said:
Hi - Will check that out later when I finish work. Thanks..
Click to expand...
Click to collapse
Hi - When I re-read your Instructions I couldn’t figure out how to do what you advised. Anyway I made what must have been my 10th phone call to Amazon. It went from them offering me 15% discount, then 20% & then 30%. I said no to all & finally after a lot of polite badgering, they have allowed to me buy a new one & I have an email from Amazon stating that I will get a full refund when my cube is delivered tomorrow
Clubcard said:
they have allowed to me buy a new one
Click to expand...
Click to collapse
Are they giving you a 3rd gen Cube I didn't think Amazon had any more new 2nd gen Cubes?
@Functioner is right, there does't appear to be any navigation options in that menu. Amazon didn't fully implemented the standard Android recovery menu WITH navigation, which effectively bricks the device.
Amazon is at fault here, however getting them to admit to it is another thing.
Regarding my previous instructions. Holding down the volume up button on the Cube (not the remote) during boot will put the Cube in fastboot mode.
You then need to use your computer with ADB/fastboot installed on it, and issue the fastboot command fastboot continue to the Cube over USB.
I don't know if activation of that recovery menu will prevent the device from booting into fastboot, you'll have to see.
Since you are getting a new Cube, I'd advise you skip the mandatory registration firmware update.
Pro-me3us said:
Are they giving you a 3rd gen Cube I didn't think Amazon had any more new 2nd gen Cubes?
@Functioner is right, there does't appear to be any navigation options in that menu. Amazon didn't fully implemented the standard Android recovery menu WITH navigation, which effectively bricks the device.
Amazon is at fault here, however getting them to admit to it is another thing.
Regarding my previous instructions. Holding down the volume up button on the Cube (not the remote) during boot will put the Cube in fastboot mode.
You then need to use your computer with ADB/fastboot installed on it, and issue the fastboot command fastboot continue to the Cube over USB.
I don't know if activation of that recovery menu will prevent the device from booting into fastboot, you'll have to see.
Since you are getting a new Cube, I'd advise you skip the mandatory registration firmware update.
Click to expand...
Click to collapse
Hi - Yes, it’s a 3rd Gen I’m getting. I had the downloader app & had kodi & few other apps on my 2nd Gen. Will this 3rd Gen not allow me to have any of these 3rd party apps on?