Related
I was running a Desire Rom on my Incredible when the phone reset vibrated 5-times and would not reboot..after plugging into charger I was able to get the phone to boot , but lost root and phone was s= on. After reading other threads I was able to use hboot and load the 2.2 stock rom back on the device. Currently the phome is S=on , .092 Hboot I tried to use unrevoked3.2 but fails to push the file when connected. I also have tried to use the fastboot oem enable qxdm 0 command but I get malformed error...Since I cannot connect to adb I will reformat my computer and reinstall the drivers seems to have gotten messed up somehow.
Tried ubuntu just hangs and unrevoked doesn't work with MacOs 10.58
any help would be appreciated
Reboot and 5x vibe indicates Qualcomm Diagnostics. Not sure what it does, but it screwed up a few friends phones.
Sent from my ADR6300 using XDA App
happened to two of my phones, if you have it plugged in to A/C charging, and pull it out from charge while on the boot logo it should stay on. little trick thats been learned. call for a refurb, they wont have any prob replacing it. 1800-922-0204
ACD168 said:
happened to two of my phones, if you have it plugged in to A/C charging, and pull it out from charge while on the boot logo it should stay on. little trick thats been learned. call for a refurb, they wont have any prob replacing it. 1800-922-0204
Click to expand...
Click to collapse
Thanks was hoping to be able to fix it....
I rooted my fire a couple weeks ago. Used the KFU and everything worked perfectly. I have the android marketplace. I even downloaded the OTA something that allows you to temporally disable so I can still watch prime videos.
But tonight it powered off on its own and got stuck on the yellow triangle screen. I tried using the KFU and change it to normal boot mode. which seemed to work. It got to the Kindle fire screen and booted up. As soon as the carousel popped up it shutdown immediately and got stuck on the yellow triangle screen. It keeps doing this. Any ideas.
I tried reading many of the other threads, but I got majorly confused. So any help is appreciated. Thanks
edit: I noticed i had a few seconds before it would shutdown on me. I was able to open OTA rootkeeper and turn the root back on before it shutdown. As soon as I click restore root, it shutdown again, but it booted up fine. Im thinking the issue was caused by the root temporally being disabled. Is this a known problem. Seems to be working fine, will update tomorrow.
Edit: seems I have to changed it no normal boot everytime. Is there a way to unroot my fire. Hopefully its not too complicated.
Thanks for anything guys.
And I think the root is disabled at the moment, but not a %100 sure. NOt sure if that matters.
Mine's doing the same thing. I think it has something to do with the new OTA update? Mine will start up then reboot into recovery...any thoughts guys?
I'd start here, since it appears many others had similar problems with the OTA push:
http://forum.xda-developers.com/showthread.php?t=1634075&page=2
Supposedly KFU rooting still works. You may need to try this method again. Check this thread and see what others had to say as far as what worked for them. Good luck!
How do I unroot it completely. Its still getting stuck on yellow triangle. I used it for 30 minutes last night. Now unless I make it boot up normally, it gets stuck. getting frustrated.
Now when I use KFU to start it in normal mode, it gets to the Kindle fire screen, and occasionally the screen where I typed in my code to unlock it and it turns off, black screen, It will only turn on when plugged in.
edit: I guess my battery somehow died overnight. Swear it was full when I went to bed
Would updating my fire with the usb get rid of the root? I just want it back to normal. What is easiest way to do that?
Now its stuck on this cycle where it says theres an error and the kindle fire must reset to its original factory settings its does this. Reboots I think and does it again. Its stuck like this.
To break root and restore everything back to original:
http://forum.xda-developers.com/showthread.php?p=25681034
soupmagnet said:
To break root and restore everything back to original:
http://forum.xda-developers.com/showthread.php?p=25681034
Click to expand...
Click to collapse
Thanks but I cant get out of the cycle of what I said in my last post. I think my Fire is broken for good.
Can you boot into recovery? Do you know how?
soupmagnet said:
Can you boot into recovery? Do you know how?
Click to expand...
Click to collapse
I was able to before. My computer doesn't recognize the Kindle anymore
Guess I will be buying a new one.
TURBO1112 said:
I was able to before. My computer doesn't recognize the Kindle anymore
Click to expand...
Click to collapse
Your computer doesn't need to be recognized by the computer to boot into recovery.
soupmagnet said:
Can you boot into recovery? Do you know how?
Click to expand...
Click to collapse
I *think* I'm having the same issue. When the fire is not plugged in, it's a black screen. No method of pressing the power button does anything (length of time, number of times, etc.). When it IS plugged in, the standard kindle fire/android logo just blinks. Again, power button has no effect whatsoever.
KFU shows ADB offline and Boot unknown.
Just some background info, I had a rooted working Fire. Out of the blue (likely the OTA update) it got stuck at the triangle logo screen and was able to get it into recovery mode. The first time I just reset it to factory.
Rooted again using KFU, said successful root, but installing Google apps kept saying failed or error until finally saying "All done!"
Then tried to install TWRP, and KFU got stuck at trying to put the fire into fast boot mode then <waiting for device>. Recovery screen came up again, and (here's where I made a bonehead decision) figuring I would help things along, I selected fast boot mode. It was stuck on the kindle fire screen for hours. I even tried reinstalling the drivers but that failed. I left it plugged in to my PC and when I woke up this morning I found it in the state it is in now that I first described above.
I will continue to search more threads for an answer, but if I don't update this one that I've found one, it means I haven't.
fzdolfan said:
I *think* I'm having the same issue. When the fire is not plugged in, it's a black screen. No method of pressing the power button does anything (length of time, number of times, etc.). When it IS plugged in, the standard kindle fire/android logo just blinks. Again, power button has no effect whatsoever.
KFU shows ADB offline and Boot unknown.
Just some background info, I had a rooted working Fire. Out of the blue (likely the OTA update) it got stuck at the triangle logo screen and was able to get it into recovery mode. The first time I just reset it to factory.
Rooted again using KFU, said successful root, but installing Google apps kept saying failed or error until finally saying "All done!"
Then tried to install TWRP, and KFU got stuck at trying to put the fire into fast boot mode then . Recovery screen came up again, and (here's where I made a bonehead decision) figuring I would help things along, I selected fast boot mode. It was stuck on the kindle fire screen for hours. I even tried reinstalling the drivers but that failed. I left it plugged in to my PC and when I woke up this morning I found it in the state it is in now that I first described above.
I will continue to search more threads for an answer, but if I don't update this one that I've found one, it means I haven't.
Click to expand...
Click to collapse
The "blinking" boot logo is indicative of a dead battery, probably caused by leaving it in fastboot mode for so long.
http://forum.xda-developers.com/showthread.php?p=25400963
http://www.droidforums.net/forum/droid-labs/146492-how-why-make-your-own-motorola-factory-cable.html
http://forum.xda-developers.com/showthread.php?p=20317299
Your best bet is to follow the first link and do what you can to install FFF1.4 and that will allow you to charge your battery from such a low power state.
You'll have to use the fastboot flash command for this so be sure that the file you use to flash your bootloader is in a .bin format. Simply renaming a .zip to .bin will not work. You have to extract the u-boot.bin from the FFF1.4.zip, otherwise you will hard-brick your device. If you're unsure of what you're doing, ask for help.
On the chance you can't get FFF1.4 installed, you'll need to acquire a factory cable to keep the device powered on long enough to install your bootloader.
Another user recently had a problem that required a factory cable to fix. Take a look at that thread so you have an idea of what needs to be done and how to fix your problem. His problem was different from yours but the solution is the same. http://forum.xda-developers.com/showthread.php?p=25693109
soupmagnet said:
The "blinking" boot logo is indicative of a dead battery, probably caused by leaving it in fastboot mode for so long.
http://forum.xda-developers.com/showthread.php?p=25400963
http://www.droidforums.net/forum/droid-labs/146492-how-why-make-your-own-motorola-factory-cable.html
http://forum.xda-developers.com/showthread.php?p=20317299
Your best bet is to follow the first link and do what you can to install FFF1.4 and that will allow you to charge your battery from such a low power state.
You'll have to use the fastboot flash command for this so be sure that the file you use to flash your bootloader is in a .bin format. Simply renaming a .zip to .bin will not work. You have to extract the u-boot.bin from the FFF1.4.zip, otherwise you will hard-brick your device. If you're unsure of what you're doing, ask for help.
On the chance you can't get FFF1.4 installed, you'll need to acquire a factory cable to keep the device powered on long enough to install your bootloader.
Another user recently had a problem that required a factory cable to fix. Take a look at that thread so you have an idea of what needs to be done and how to fix your problem. His problem was different from yours but the solution is the same. http://forum.xda-developers.com/showthread.php?p=25693109
Click to expand...
Click to collapse
Even after reading the posts regarding the factory cable, I'm still not sure what the difference is. I have been (successfully) using a Motorola Android phone cable that when plugged into the Fire (when it was working) would say that USB is connected and I can now transfer files. I also successfully rooted it once before and installed all the apps and such with the KFU. What would be different that would make this cable only now insufficient?
Btw, I was able to charge it using the stock wall charger. At least I assume it is charged because it is no longer blinking the kindle fire logo, and I am able to shut it down by holding the power button even when plugged into the USB cable.
However, it still won't do anything but show the android/kindle fire logo (static, not flashing/oscillating) whether it's turned on with or without a cable plugged in. Opening the KFU and trying boot modes does nothing. There is no acknowledgment whatsoever that it is connected to the PC either from the fire or the PC. I don't even get the sound effect from the PC that something has been connected via USB.
fzdolfan said:
Even after reading the posts regarding the factory cable, I'm still not sure what the difference is. I have been (successfully) using a Motorola Android phone cable that when plugged into the Fire (when it was working) would say that USB is connected and I can now transfer files. I also successfully rooted it once before and installed all the apps and such with the KFU. What would be different that would make this cable only now insufficient?
Btw, I was able to charge it using the stock wall charger. At least I assume it is charged because it is no longer blinking the kindle fire logo, and I am able to shut it down by holding the power button even when plugged into the USB cable.
However, it still won't do anything but show the android/kindle fire logo (static, not flashing/oscillating) whether it's turned on with or without a cable plugged in. Opening the KFU and trying boot modes does nothing. There is no acknowledgment whatsoever that it is connected to the PC either from the fire or the PC. I don't even get the sound effect from the PC that something has been connected via USB.
Click to expand...
Click to collapse
A "factory cable" is specially made to interact with the device in a way that is different from the OEM Motorola USB cable you are currently using. With a little research and a little more reading you'll be able to find out what the difference is and why it works for fixing dead battery issues.
Using the stock charger was one of the very first things covered in the first link that I gave you. I'm trying to help you fix your problem so please try to pay attention to the information I'm giving you.
So now that your battery issue is resolved, you have to fix the next part of the problem which is resetting your bootmode. By far the easiest way to do this is by flashing the latest 1.4 version of FireFireFire in recovery. Be sure to use recovery to install it or you may find yourself in more trouble than you started.
The thread for the new version along with important information on how to install and use it can be found here: http://forum.xda-developers.com/showthread.php?t=1632375
soupmagnet said:
Using the stock charger was one of the very first things covered in the first link that I gave you.
Click to expand...
Click to collapse
I realize that, and I acknowledged it in my post by stating that it solved the drained battery issue. I also gave thanks on your post.
Accusing me of not paying attention is not necessary.
I only said that I don't see the difference in the factory cable because a) my drained battery was resolved by other means and b) I did read in the factory cable thread that "Seems like you have power and this cable is maininly for when your ... battery is dead and you need to ... fastboot with no battery life left.... So the cable does not matter in your case since your battery has power you can use any usb cable."
soupmagnet said:
So now that your battery issue is resolved, you have to fix the next part of the problem which is resetting your bootmode. By far the easiest way to do this is by flashing the latest 1.4 version of FireFireFire in recovery. Be sure to use recovery to install it or you may find yourself in more trouble than you started.
The thread for the new version along with important information on how to install and use it can be found here: http://forum.xda-developers.com/showthread.php?t=1632375
Click to expand...
Click to collapse
I also looked at this thread, but the initial post seems to imply that I already know how to "Apply this flash.zip from recovery just like any other ROM or kernel .zip file.", which I do not.
As I said, my fire is currently stuck at the kindle fire logo and does not respond to being plugged in to the PC (other than turning on to the kindle fire screen).
Admittedly, I only went about 4 pages deep into the thread, but it seemed to be all posts of thanks (for the most part) to the original post. I will continue reading the thread if you're saying that it indeed contains more helpful information.
I apologize if my post came across as ignorant or lazy, but the fact is that I've been researching this for the better part of the day, and I see plenty of info on what to do if I can get my PC to communicate with my Fire, but the first problem is that I cannot find out how to hurdle that first very important obstacle.
Just to save us both some time (and I do appreciate your patience and willingness to help), are you saying that I need a factory cable regardless of the state of the battery? Because if that's the case, then my first priority is to figure out how to get one, because my knowledge, means, and experience in soldering and inner workings of electronics is zero, so making one myself is not an option.
Forgive my impatience but playing twenty questions with other, less motivated to learn users, gets kind of old after a while (not to say that you fall into that category). Not to mention, I'm a prick and have very little patience to begin with.
With a good charge on your battery there is no longer a need for a factory cable.
Most of the users here are fairly proficient with the use of recovery so its easy to overlook those who aren't. That's why it's important to know up front what your level of experience is, to avoid such assumptions.
Your recovery (TWRP or CWM) has a mount function for mounting certain partitions as external drives onto your computer. Your computer will recognize it in the same way it does a thumb drive. Use it to mount your sdcard and transfer the FFF1.4 so it can be installed while in recovery.
Once installed, reboot and hold the power button as if you were trying to enter recovery again and you will be able to select which mode to boot with. Choose "Normal Boot".
So I have had this device since February and finally decided I wanted to Unlock the bootloader, install a custom recovery and get some cool new roms on it. I have the GPE by the way.
Anyways so I unlocked the bootloader and flashed TWRP and then rooted the device by flashing a zip file for root. I assumed the tablet got rooted so I then decided to try the multi window hack and flashed that. Well it caused some apps to corrupt (the phone app in particular) and they would keep crashing preventing me from doing anything. I decided to go back into recovery and try to do a data and cache wipe but that did not help. Eventually I wiped the entire OS which was a mistake. I was still able to get into recovery mode but I have no SD card to load up with a rom to flash and it was late to go buy one. I also tried ADB through the recovery mode that did not seem to work.
I did some searching and found out that I could download the LGMlauncher and it could get me back to stock but to use that I needed my serial number which is on the box (which I had at the office). So I plugged it in (and got the little battery icon) and a few hours ago went to the office to get the box. I tried the LGMlauncher and it keeps on crashing while trying to update and now I am not able to get into recovery mode. What are some other steps I can take to try and recover it?
Thanks.
Edit: I tried the LGMlauncher again and it said my battery was low so I plugged it back in. is there a trick to charging it while it is off? I assume that could be why recovery mode wont work.
Hi, if you have twrp recovery and it is working you can install your missing system by following this post
http://forum.xda-developers.com/showthread.php?p=53744333
Good luck
Sent from my LG-V510 using Tapatalk
schalmers said:
Hi, if you have twrp recovery and it is working you can install your missing system by following this post
http://forum.xda-developers.com/showthread.php?p=53744333
Good luck
Sent from my LG-V510 using Tapatalk
Click to expand...
Click to collapse
Yeah It appears as though the battery was not charging even though I had plugged it in and now it is dead. I cannot seem to get it to go into recovery or anything. Is it safe to say it is bricked?
When my HP Touchpads battery was to low to take a charge from the wall charger, the only way it could get enough charge to be able to use the wall charger was to trickle charge it from my computer usb port for a couple of days.
Jubeldum said:
When my HP Touchpads battery was to low to take a charge from the wall charger, the only way it could get enough charge to be able to use the wall charger was to trickle charge it from my computer usb port for a couple of days.
Click to expand...
Click to collapse
Yeah it has been plugged into my PC for a few days and nothing.
I'm quite perplexed. I was using my p600 today, and it worked fine like normal. Tonight I took it out to do some reading, and noticed some flickering streaks across the screen. I thought nothing of it, and did a reboot.
It turned off, but never rebooted. The back and menu buttons flashed once, and then went dark.
I've been trying without success to get it to boot for a half hour, nothing. There is no response to plugging it into a charger, and my computer does not recognize it as being plugged in. (Currently have no access to windows, so unsure of ODIN).
I was running Tamasek's unnoficial 18.1 build at the time.
Any ideas. Would greatly appreciate any help, even just to get some notes off if it is indeed dead.
while plugged into charger (to rule out it hasnt died while youve been messing with it) long hold power button... i forget if its 10 seconds or 30 seconds. same sorta thing happened to me on temasek, flicker screen but then it died itself, and i got a response from my tablet by long power button hold. not sure if we had same cause but thats what worked for me
diabl0w said:
while plugged into charger (to rule out it hasnt died while youve been messing with it) long hold power button... i forget if its 10 seconds or 30 seconds. same sorta thing happened to me on temasek, flicker screen but then it died itself, and i got a response from my tablet by long power button hold. not sure if we had same cause but thats what worked for me
Click to expand...
Click to collapse
Doesn't seem to work for me.
Update:
Holding the power button gives no response, no matter the length of press. However, apparently randomly it will turn on, as the back and menu buttons will light up. If this happens I am able to successfully connect to a computer and view files. I was able to connect to ODIN, however since I am unable to get into download mode I am unable to do anything.
If it is in the state where the buttons are lighting up and I then try to boot it it turns off and is completely unresponsive.
Any ideas? Is there a way to remotely boot into download mode?
Cheers
greenmatrix said:
Update:
Holding the power button gives no response, no matter the length of press. However, apparently randomly it will turn on, as the back and menu buttons will light up. If this happens I am able to successfully connect to a computer and view files. I was able to connect to ODIN, however since I am unable to get into download mode I am unable to do anything.
If it is in the state where the buttons are lighting up and I then try to boot it it turns off and is completely unresponsive.
Any ideas? Is there a way to remotely boot into download mode?
Cheers
Click to expand...
Click to collapse
When lights come on, attach to computer and run the command adb devices... if you dont know about adb then there is plenty of info on the net about it. If adb devices gives you a response (which it will if yoi are able to view files on yoir device then that means you will get and adb response as long as you set up the adb program correctly) then run adb reboot download and then youll be in download mode and flash with odin
diabl0w said:
When lights come on, attach to computer and run the command adb devices... if you dont know about adb then there is plenty of info on the net about it. If adb devices gives you a response (which it will if yoi are able to view files on yoir device then that means you will get and adb response as long as you set up the adb program correctly) then run adb reboot download and then youll be in download mode and flash with odin
Click to expand...
Click to collapse
Thanks, I'll let you know how it goes.
diabl0w said:
When lights come on, attach to computer and run the command adb devices... if you dont know about adb then there is plenty of info on the net about it. If adb devices gives you a response (which it will if yoi are able to view files on yoir device then that means you will get and adb response as long as you set up the adb program correctly) then run adb reboot download and then youll be in download mode and flash with odin
Click to expand...
Click to collapse
I am unable to get the p600 to show under adb devices. However, adb does work successfully for my nexus 6 so it appears to be generally working.
This is on mac, so I don't believe it could be a driver issue. I spent a good while trying to get adb working on windows with no success for either device (killed and restarted adb server, tried reinstalling drivers, different cables, etc).
Frustrating, because the p600 will connect fine to the computer, and I can view files and interact with it. Odin also recognizes it.
I appreciate the help, and any further ideas.
if odin recognizes it then why dont you just try to flash stock again?
diabl0w said:
if odin recognizes it then why dont you just try to flash stock again?
Click to expand...
Click to collapse
I've tried, every time it gets hung up on SetupConnection. Running Odin 3.07. Perhaps a different version of Odin?
greenmatrix said:
I've tried, every time it gets hung up on SetupConnection. Running Odin 3.07. Perhaps a different version of Odin?
Click to expand...
Click to collapse
what version did you use last time... hold on ill get you a link to a dif one you should use 3.07 is kinda old
diabl0w said:
what version did you use last time... hold on ill get you a link to a dif one you should use 3.07 is kinda old
Click to expand...
Click to collapse
Thanks, can't remember what I used when I last flashed with odin, I want to say it was around 1.8x.
greenmatrix said:
Thanks, can't remember what I used when I last flashed with odin, I want to say it was around 1.8x.
Click to expand...
Click to collapse
i meant what did you use to flash twrp so that you were able to flash temasek's? ... use 3.10.7
http://forum.xda-developers.com/showthread.php?t=2711451
diabl0w said:
i meant what did you use to flash twrp so that you were able to flash temasek's? ... use 3.10.7
http://forum.xda-developers.com/showthread.php?t=2711451
Click to expand...
Click to collapse
Yeah, when I flashed TWRP a few weeks ago I believe i used odin 1.8x, can't remember. However I know that it wasn't 3.10.7. I'll see how 3.10.7 works.
It appears to still be hanging on SetupConnection.
greenmatrix said:
It appears to still be hanging on SetupConnection.
Click to expand...
Click to collapse
Hmm i guess its not in download mode then... the only thing i could think of is that for some reason it keeps booting to recovery mode which would make both adb and odin not work. Although idk why youd have a blank screen cuz that doesnt tend to happen for recovery. When the menu buttons light up, do they give you haptic feedback (do they vibrate)? If so, maybe you recently dropped it and the ribbon cable for screen beca,e disloged. Id stilll see if you get any responses from ppl who know more than me before you go pulling your tablet apart tho.
The only other thing i could think of to tell you to do is to keep trying to access download mode by holding the appropriate buttons during boot and then try to flash stock with odin. Sorry, i dont know enough to give any more advice from here
diabl0w said:
Hmm i guess its not in download mode then... the only thing i could think of is that for some reason it keeps booting to recovery mode which would make both adb and odin not work. Although idk why youd have a blank screen cuz that doesnt tend to happen for recovery. When the menu buttons light up, do they give you haptic feedback (do they vibrate)? If so, maybe you recently dropped it and the ribbon cable for screen beca,e disloged. Id stilll see if you get any responses from ppl who know more than me before you go pulling your tablet apart tho.
The only other thing i could think of to tell you to do is to keep trying to access download mode by holding the appropriate buttons during boot and then try to flash stock with odin. Sorry, i dont know enough to give any more advice from here
Click to expand...
Click to collapse
ITS ALIVE!!
Thanks man, you may have just solved it, I feel like an idiot. I hadn't considered that the ribbon cable might be loose, and as I was examining it with a bright light I could see items on the screen. Was successfully able to boot into download mode and flash the stock rom, the screen issue was not solved, but I think it flashed alright.
When I have some time I'm going to take off the back and check out the ribbon cable.
greenmatrix said:
ITS ALIVE!!
Thanks man, you may have just solved it, I feel like an idiot. I hadn't considered that the ribbon cable might be loose, and as I was examining it with a bright light I could see items on the screen. Was successfully able to boot into download mode and flash the stock rom, the screen issue was not solved, but I think it flashed alright.
When I have some time I'm going to take off the back and check out the ribbon cable.
Click to expand...
Click to collapse
im glad you were able to figure it out
greenmatrix said:
ITS ALIVE!!
Thanks man, you may have just solved it, I feel like an idiot. I hadn't considered that the ribbon cable might be loose, and as I was examining it with a bright light I could see items on the screen. Was successfully able to boot into download mode and flash the stock rom, the screen issue was not solved, but I think it flashed alright.
When I have some time I'm going to take off the back and check out the ribbon cable.
Click to expand...
Click to collapse
The ribbon cable coming loose is a very common issue on this tablet (even without dropping it) as it's connected rather poorly. Fortunately it's also relatively easy to fix as per the below:
Fixing Note 10.1 2014 ribbon cable
Especially the screen flickering when it "died" sounds familiar.
epithetic said:
The ribbon cable coming loose is a very common issue on this tablet (even without dropping it) as it's connected rather poorly. Fortunately it's also relatively easy to fix as per the below:
Fixing Note 10.1 2014 ribbon cable
Especially the screen flickering when it "died" sounds familiar.
Click to expand...
Click to collapse
This was exactly it. 15 minute fix and everything was golden.
So I've got into a big trouble... I wanted to manually update my Pixel 6 Pro to the latest version using an official OTA (since the update wasn't available yet for my country and I wanted to stay up-to-date). It was all fine until it said 74 % done... and the power in my house has completely turned off... The device hasn't given me any error and rebooted, hower it got stuck on a Google logo. I rebooted to the recovery mode how it was suggested and did a clean factory reset, then rebooted again... and nothing changed, only the logo background has changed (white vs black). The BIGGEST problem is, the device OEM is NOT unlocked I tried entering the fastboot mode and flashing the device with a recovery image but it obviously didn't work as it required OEM to be unlocked... I am in a big depression now, somehow I fear that it's not fixable... But if some awesome soul could suggest a way to try out, that would be great! Thanks in advance.
I would try the android flash tool and flash the whole full ROM onto the phone. Expect to lose your data though.
mkhcb said:
I would try the android flash tool and flash the whole full ROM onto the phone. Expect to lose your data though.
Click to expand...
Click to collapse
Doesn't your phone have to be unlocked to use the flash tool?
The data is all backed up so it's not a problem to lose it. The problem is actually making the phone to boot past the logo... I will try that Android Flash Tool but I fear that the phone should be unlocked first
Try this tool: https://pixelrepair.withgoogle.com/carrier_selection
Not sure if its any different to the android flash tool.
As expected, Android Flash Tool requires you to to have the device unlocked. At this point I am out of ideas and is truly disappointed. The tool mentioned above probably works the same way.
Maybe try sideloading OTA again. Are you able to do that?
mclarence said:
Try this tool: https://pixelrepair.withgoogle.com/carrier_selection
Not sure if its any different to the android flash tool.
Click to expand...
Click to collapse
McNaccken said:
As expected, Android Flash Tool requires you to to have the device unlocked. At this point I am out of ideas and is truly disappointed. The tool mentioned above probably works the same way.
Click to expand...
Click to collapse
Unfortunately, someone else in another thread reported that the Pixel Repair site (not the Android Flash Tool) hasn't been updated for the P6P.
McNaccken said:
So I've got into a big trouble... I wanted to manually update my Pixel 6 Pro to the latest version using an official OTA (since the update wasn't available yet for my country and I wanted to stay up-to-date). It was all fine until it said 74 % done... and the power in my house has completely turned off... The device hasn't given me any error and rebooted, hower it got stuck on a Google logo. I rebooted to the recovery mode how it was suggested and did a clean factory reset, then rebooted again... and nothing changed, only the logo background has changed (white vs black). The BIGGEST problem is, the device OEM is NOT unlocked I tried entering the fastboot mode and flashing the device with a recovery image but it obviously didn't work as it required OEM to be unlocked... I am in a big depression now, somehow I fear that it's not fixable... But if some awesome soul could suggest a way to try out, that would be great! Thanks in advance.
Click to expand...
Click to collapse
If you can still get into recovery mode, maybe try sideloading the OTA again?
EDIT: Ninja'd by @znel52
Lughnasadh said:
If you can still get into recovery mode, maybe try sideloading the OTA again?
EDIT: Ninja'd by @znel52
Click to expand...
Click to collapse
Yeah I'm afraid since he did a factory reset debugging got disabled. Worth a shot though.
znel52 said:
Yeah I'm afraid since he did a factory reset debugging got disabled. Worth a shot though.
Click to expand...
Click to collapse
Oh crap, didn't think about that.
I know not everyone has access to a laptop but if you do always use that over a desktop. In the event of something like this you will have the battery power to carry you through.
I'm sorry this happened to you. The only option may be to send it to Google for repairs.
Sorry for your phone. I experienced this on a nexus 6 that didn't have USB debugging or OEM unlock enabled. I tried sideload, put the update package on the phone storage, try to update with Android recovery. Nothing worked. Stuff happens with phones. I hope you can get a new phone.
God bless.
Sorry to hear this. It seems that I need to open USB debugging option just in case for my Pixel 6, which finally arrived across the ocean after a month.
McNaccken said:
So I've got into a big trouble... I wanted to manually update my Pixel 6 Pro to the latest version using an official OTA (since the update wasn't available yet for my country and I wanted to stay up-to-date). It was all fine until it said 74 % done... and the power in my house has completely turned off... The device hasn't given me any error and rebooted, hower it got stuck on a Google logo. I rebooted to the recovery mode how it was suggested and did a clean factory reset, then rebooted again... and nothing changed, only the logo background has changed (white vs black). The BIGGEST problem is, the device OEM is NOT unlocked I tried entering the fastboot mode and flashing the device with a recovery image but it obviously didn't work as it required OEM to be unlocked... I am in a big depression now, somehow I fear that it's not fixable... But if some awesome soul could suggest a way to try out, that would be great! Thanks in advance.
Click to expand...
Click to collapse
Since the Repairtool has not been updated for your needs and considering that your device is not unlocked, your only option is to contact Google (/your seller). Maybe they can offer you an updated version of the tool (unlikely) or replace your device.
You just described, btw, my horror scenario when updating the BIOS of my PC. The lights going out, when doing a firmware update o.o
Oh my. I'm so sorry for you to have experienced that.
Ok, so I did a CMOS reset on my main PC, since it also failed to load after the lost power accident. Loaded my PC then just fine and tried connecting the phone again. Got to recovery mode and tried "adb devices" command... and it listed my Pixel device !! I tried the "adb sideload" command but it's stuck at 5% for at least 20-30 mins. The phone's last message is "Verifying update package". Not sure if it's a good sign, but afaik if USB debugging is off etc, you can not use adb commands. What would you guys suggest, try waiting for another 30 mins or unplug the phone, restart PC and try again? I am using USB-A to USB-C cable btw, maybe I could use USB-C to USB-C.
McNaccken said:
Ok, so I did a CMOS reset on my main PC, since it also failed to load after the lost power accident. Loaded my PC then just fine and tried connecting the phone again. Got to recovery mode and tried "adb devices" command... and it listed my Pixel device !! I tried the "adb sideload" command but it's stuck at 5% for at least 20-30 mins. The phone's last message is "Verifying update package". Not sure if it's a good sign, but afaik if USB debugging is off etc, you can not use adb commands. What would you guys suggest, try waiting for another 30 mins or unplug the phone, restart PC and try again? I am using USB-A to USB-C cable btw, maybe I could use USB-C to USB-C.
Click to expand...
Click to collapse
My apologies for asking the obvious - did you select "adb sideload" in the recovery menu ? At least I was blind enough to oversee that I need to select this option first
Can you boot into fastboot from the recovery ? If yes you could also try installing a factory image instead of the update package.... I read you cannot because your device is locked, but you can unlock in fastboot (you can always relock later).... only downside is that this will clear all data on the phone for sure....
McNaccken said:
So I've got into a big trouble... I wanted to manually update my Pixel 6 Pro to the latest version using an official OTA (since the update wasn't available yet for my country and I wanted to stay up-to-date). It was all fine until it said 74 % done... and the power in my house has completely turned off... The device hasn't given me any error and rebooted, hower it got stuck on a Google logo. I rebooted to the recovery mode how it was suggested and did a clean factory reset, then rebooted again... and nothing changed, only the logo background has changed (white vs black). The BIGGEST problem is, the device OEM is NOT unlocked I tried entering the fastboot mode and flashing the device with a recovery image but it obviously didn't work as it required OEM to be unlocked... I am in a big depression now, somehow I fear that it's not fixable... But if some awesome soul could suggest a way to try out, that would be great! Thanks in advance.
Click to expand...
Click to collapse
I had a similar issue with applying ota updates and have seen quite a few reports of users having trouble. Not sure what the deal is, but for some reason this phone seems super finicky with updates. Are you still in the return window? You may want to reach out to Google support or one of their "authorized repair shops".
For me, I ran the flash all bat, rebooted, got a message saying my device can't be trusted. So I rebooted, wiped data, rebooted again and got the same thing. So I rebooted, ran the flash all bat file again, rebooted phone, and screen went black and it never powered on again. Suspect circuit board may have fried some how. Anyways, long story short, contacted Google and had a replacement sent out with minimal hassle.
McNaccken said:
Ok, so I did a CMOS reset on my main PC, since it also failed to load after the lost power accident. Loaded my PC then just fine and tried connecting the phone again. Got to recovery mode and tried "adb devices" command... and it listed my Pixel device !! I tried the "adb sideload" command but it's stuck at 5% for at least 20-30 mins. The phone's last message is "Verifying update package". Not sure if it's a good sign, but afaik if USB debugging is off etc, you can not use adb commands. What would you guys suggest, try waiting for another 30 mins or unplug the phone, restart PC and try again? I am using USB-A to USB-C cable btw, maybe I could use USB-C to USB-C.
Click to expand...
Click to collapse
so you can get through this... you'll be fine. pick adb sideload and it will say waiting, then run the command.
you can also change slots at the bootloader menu or try running the unlock oem command to see if it will allow you to unlock..... not sure if you can change slots without unlocking bootloader. try different USB ports on your computer (and restart your computer just in case) along with using the latest platform tools (adb/fastboot) and USB driver directly from Google (not third party apps or websites.
download the OTA zip again (and just open and close it quickly to verify it isn't corrupt).. and also make sure you have 5-10GB of space free on your computer.
usually the boot slot is changed whenever an OTA is flashed. it will tell you what slot you're in at the bootloader menu (where it says fastboot and device state locked).
can you try holding power button (when it's not plugged in) and as soon as you see then Google logo, hold volume down. that will get you to safe mode. and as quickly as you can, enable "OEM Unlocking" - which will allow you to flash a full factory image.
sorry for this comment being all over the place. if you need help, just reply, and I'll be more methodical next time
s3axel said:
I read you cannot because your device is locked, but you can unlock in fastboot (you can always relock later).... only downside is that this will clear all data on the phone for sure....
Click to expand...
Click to collapse
I don't think the problem is that his bootloader is locked - it's unlocked, however, they factory reset the device which likely caused USB Debugging to be turned off, as it defaults to after a factory reset.
I'm so glad years ago I swore to use Uninterruptible Power Supplies (UPS) for all the PCs I build for myself or my wife.