Related
Hi, I was flashing a new rom but I accidentally select the sideload option and now I'm stuck there,
I tried to hold power button 30 seconds, even more,(also volume down + power button) but nothing happens.
Any idea?
It says:
"ClockworkMod Recovery v6.0.2.3
Sideload started...
Now send the package you want to apply
to the device with "adb sideload <filename>"
Please help I'm n00b -.-
I did that once and I didnt know how to get out of it either. Just pull the battery and restart.
jsgraphicart said:
I did that once and I didnt know how to get out of it either. Just pull the battery and restart.
Click to expand...
Click to collapse
Thank you so much man, that worked!
ARMIGUER said:
Thank you so much man, that worked!
Click to expand...
Click to collapse
No problem. Dont try that when something is running though. That might mess things up. But the sideload thing isnt running anything. Its just waiting for a command. They need to put a back or a cancel button on that.
jsgraphicart said:
No problem. Dont try that when something is running though. That might mess things up. But the sideload thing isnt running anything. Its just waiting for a command. They need to put a back or a cancel button on that.
Click to expand...
Click to collapse
Thanks for the advice but now I'm installing the crossbones ROM 2.3.0 but I'm stuck installing it,
I used to flash roms in my other phone a galaxy s3 and I've never had this kind of problems...
It says this:
Formatting system
Installing Crossbones ROM
that's all
What would you recommend me in this case?
Should I remove the baterry again? I've been waiting for almost 15 minutes and nothing again :/
ARMIGUER said:
Thanks for the advice but now I'm installing the crossbones ROM 2.3.0 but I'm stuck installing it,
I used to flash roms in my other phone a galaxy s3 and I've never had this kind of problems...
It says this:
Formatting system
Installing Crossbones ROM
that's all
What would you recommend me in this case?
Should I remove the baterry again? I've been waiting for almost 15 minutes and nothing again :/
Click to expand...
Click to collapse
I'm going to assume your phone is unlocked and rooted already. Are you using the latest version of whatever recovery you are using? Are you using the ROM made specifically for your phone?
but rdleye
jsgraphicart said:
I'm going to assume your phone is unlocked and rooted already. Are you using the latest version of whatever recovery you are using? Are you using the ROM made specifically for your phone?
Click to expand...
Click to collapse
The phone is unlocked and rooted,and yes, I'm using the Clockworkmode v6.0.2.3 latest version.
My phone is the galaxy nexus (sprint)
And I download the ROM from here
http://forum.xda-developers.com/showthread.php?t=2101334
I wiped, data,cache and dalvik.
But I don't know what happens, I'm pretty n00b but I flash 4 roms before in my galaxy s3 and all is fine.
Thanks for your help man.:good:
ARMIGUER said:
The phone is unlocked and rooted,and yes, I'm using the Clockworkmode v6.0.2.3 latest version.
My phone is the galaxy nexus (sprint)
And I download the ROM from here
http://forum.xda-developers.com/showthread.php?t=2101334
I wiped, data,cache and dalvik.
But I don't know what happens, I'm pretty n00b but I flash 4 roms before in my galaxy s3 and all is fine.
Thanks for your help man.:good:
Click to expand...
Click to collapse
You did everything right then. I dont know why it would hang. Id say pull the battery but like I said, it could mess something up if its actually doing something. Especially if it says it already wiped the system. If that happens, you're going to have to restore a factory image and start all over again. Its up to you if you want to take the chance. A ROM flash shouldnt take that long.
jsgraphicart said:
You did everything right then. I dont know why it would hang. Id say pull the battery but like I said, it could mess something up if its actually doing something. Especially if it says it already wiped the system. If that happens, you're going to have to restore a factory image and start all over again. Its up to you if you want to take the chance. A ROM flash shouldnt take that long.
Click to expand...
Click to collapse
Well I took the risk and removed tha battery after waiting for almost 30 minutes,
and I will try again all the process.
Once again thanks for your help man :good:
ARMIGUER said:
Well I took the risk and removed tha battery after waiting for almost 30 minutes,
and I will try again all the process.
Once again thanks for your help man :good:
Click to expand...
Click to collapse
No problem. I hope you get it working. Or at least to boot up again.
Supposedly sideload in cwm is a bug with no way to back out unless you pull the battery or have usb connected [exit in command prompt?]. I was starting to like the touch recovery option, but recently i've accidentally pressed a couple of things i shouldnt have.
Sorry to hijack, but I'm attempting to sideload the 4.2.2 update from stock, and my sideload command seems to do nothing. I'm sure i'm connected as it displays my device number and "sideload" next to it. Using the sideload command simply displays the "help" list of the adb commands.
Is it a driver issue perhaps? Something else? (i noticed my batter was low just before attempting this).
Now i'm stuck in the waiting for adb sideload file.
hippochris: update your adb, or look in the help output to see if the sideload command is there. Also, i did this via stock recovery, selecting it in there.
bodh said:
hippochris: update your adb, or look in the help output to see if the sideload command is there. Also, i did this via stock recovery, selecting it in there.
Click to expand...
Click to collapse
I do NOT see the sideload option in the help output. I have all the latest updates from the SDK manager. Maybe i need to reinstall the SDK. I will give that a go. Thanks.
Edit: Downloaded the latest SDK/ADB and that worked. From 1.0.29 to 1.0.31
I've messed my phone with SideLoad, please help
I booted my Galaxy Nexus into custom recovery (CWM) for some other task but mistakenly gone into sideload menu!
Got no option to get back to main menu or reboot, i took the battery out and re-inserted. Now, my cell is not turning on since then!
Tried another time, took battery off but no luck..... what to do?
I've custom ROM, MIUI V5 4.2.2. My cell is unlocked and rooted, of course.
Please help.
What if the battery is non-removable?
Had stuck in that *** sideload on my SM-E500H and been waiting for the battery to drained it up all.
Yep, tried hardware button combinations as many times as I could.
if you can't take out the battery of your device and if longpressing whatever does not solve it
1. install adb on pc.
2. connect device with usb cable to pc
3. enter following command
Code:
adb sideload /dev/null
the device will complain that file is not valid but it will come out of the sideloading state
lesmanaz said:
if you can't take out the battery of your device and if longpressing whatever does not solve it
1. install adb on pc.
2. connect device with usb cable to pc
3. enter following command
Code:
adb sideload /dev/null
the device will complain that file is not valid but it will come out of the sideloading state
Click to expand...
Click to collapse
What if I'm still in sideload and get this error?
Code:
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
Hi,
it is the second time my Gnex went into endless reboot loop sessions.
It will boot, load crash after few seconds and reboot again.
I had it unlocked in the store i bought it, and had stock rom (Not sure about the version).
Tried to do factory reset from fastboot, from recovery, and from android. Also tried to flash custom boot loader, Nothing works.
Although fastboot writes it successfuly completed the action so does the factory reset. The phone will work for few seconds but no more.
Also tried using WugFresh, for factory reset and for Flash Stock + unroot in soft-break status
I have no ideas what to do next,
Please help.
Mike
Hi Mike, I think more information is required.
- What action did you take immediately prior to having your phone get stuck in the bootloop? Were you trying to install a Custom Recovery or ROM?
- You mention that this is the second time this has happened. Do you know what caused it to bootloop the first time, and if yes what fixed it?
- When your Gnex is in Fastboot/Bootloader mode, and using a tool like Minimal ADB and Fastboot on your computer, does the tool recognize the Device ID after using the fastboot devices command?
You may also want to read through this thread.
AvidPhisherman said:
Hi Mike, I think more information is required.
- What action did you take immediately prior to having your phone get stuck in the bootloop? Were you trying to install a Custom Recovery or ROM?
- You mention that this is the second time this has happened. Do you know what caused it to bootloop the first time, and if yes what fixed it?
- When your Gnex is in Fastboot/Bootloader mode, and using a tool like Minimal ADB and Fastboot on your computer, does the tool recognize the Device ID after using the fastboot devices command?
You may also want to read through this thread.
Click to expand...
Click to collapse
Hi thanks for the reply, i am a simple user, prior to the bootloop i was using whatsapp, actually the android crashes few seconds after getting a whatsaap message (i recieve notification and it goes down). Previous time also i didn't do anything special. i never installed custom recovery or roms... previous time it was fixed by a lab the phone was on warranty.
And yes the tool recognize the device.
So your device receives a WhatsApp message/notification, restarts, and then gets stuck in a bootloop?
That is very strange, as personally I've only ever encountered bootloops after bad ROM flashes (usually after I accidentally skipped a step somewhere during the process). Bootloops usually don't happen to regular users who are just using their phone purchased as-is from a store/carrier.
If you can get it to boot back into Android, try uninstalling WhatsApp and see if that helps. Hopefully it's still under warranty, as you may have to take it back to the store and have them look at it.
AvidPhisherman said:
So your device receives a WhatsApp message/notification, restarts, and then gets stuck in a bootloop?
That is very strange, as personally I've only ever encountered bootloops after bad ROM flashes (usually after I accidentally skipped a step somewhere during the process). Bootloops usually don't happen to regular users who are just using their phone purchased as-is from a store/carrier.
If you can get it to boot back into Android, try uninstalling WhatsApp and see if that helps. Hopefully it's still under warranty, as you may have to take it back to the store and have them look at it.
Click to expand...
Click to collapse
Tried to uninstall whatsapp but it crashes before i manage to do so.
even managed to access memory via TWRP and delete whatsaap manually but somehow it appears again after restart.
Something is terribly wrong
Have you tried using Odin to repartition and restore to stock? Could be a corrupted partition. Check out this guide
nthnlee said:
Have you tried using Odin to repartition and restore to stock? Could be a corrupted partition. Check out this guide
Click to expand...
Click to collapse
Why???
Just use fastboot, Odin is evil. Nexus aren't Touchwiz crap phones.
beekay201 said:
Why???
Just use fastboot, Odin is evil. Nexus aren't Touchwiz crap phones.
Click to expand...
Click to collapse
When fastboot didn't work. i had to try something else. But, odin didn't work either.
mishkap said:
When fastboot didn't work. i had to try something else. But, odin didn't work either.
Click to expand...
Click to collapse
Let's see then. Be prepared to spend at least 30min reading, and re-reading, until you actually feel comfortable in what you're doing/typing in. If you're not sure about the technical terms and what lies behind them, read this thread's #1 First Post.
What's your device variant? maguro? toro? toroplus? This will tell which factory image you need to flash.
You need to flash latest factory image, which is (for maguro variant) Android Build 4.3 (JWR66Y). Read #1 First Post on this thread. And I mean, READ IT! Do not do anything else to your device until you do.
After you flash the factory image, that first boot will take a while to reach Android. Chill out. Go get yourself a drink. Take your time. It should have booted into Android already when you get back. It should be fine, but if not, you need to enable USB debugging under Settings > Developer Options, to check the system log.
If after 15min, it still has booted yet, pull the battery out, wait a few secs, put it back in.
Use the 3bc (3-button combo) to reach fastboot mode again. Flash a custom recovery. That's done by downloading the latest TWRP or CWM (i'll leave that choice up to you, be mindful that you might wanna try them both in the future), and running on the host (the PC):
Code:
fastboot flash recovery recovery_filename_here.img
Don't reboot the device. Use the volume keys to "Reboot to recovery" straight from fastboot. After a few seconds, you should be seeing the custom recovery you've flashed with the fastboot command above.
Now comes the part where ADB is required. I hope you've already read the answers to questions "Where do I get the driver for my PC?" and "Why do I need to install the driver twice?". If not, read them now. Also, read "What is ADB?". TIP: When a custom recovery is actually running on the device, ADB mode is already active by default, so when hooking up to the pc the device will show as an ADB interface, so installing the driver (if needed/not done yet) is piece of cake.
After you get ADB to recognize your device (like, you see your device's SN on the output of command `adb devices`).. You need to copy a custom ROM to your device, and flash it. That will get you, most likely than not, Android's USB debugging by default (read answer to "What is an insecure boot image?" on the first link), and that will allow you to see the system log, WHILE Android is booting up. Why do we wanna do this? Cos we want to see if any errors show up, something that may tell us what's failing.
When choosing a ROM from the Android Development section, ask around in the thread if the ROM has USB debugging enabled by default.
Read "What are the ADB commands?" in the thread I first linked to. You'll need to learn at least `adb push` for now.
Once you get the ROM in your /sdcard/ or whatever folder you like, disconnect the USB cable, wipe data/factory reset, then install zip from sdcard (that zip you pushed before).. Forget about gapps for now.
Connect the usb cable, reboot, and once you see padlock screen go away, start trying to run `adb devices`. Do you see your SN in the output? Once you see it, good, it already connected to adb on the device. Run `adb logcat` and try to look out for errors. Logcat is the system log.
To know how to grab that output to a text file so that you can share it with us.. Google it, my fingers hurt.
Thanks beekay201,
As a matter a fact. shortly before you posted this answer i gave up and gave my phone to a local lab.
But unfortunately they were useless and didn't manage to do anything claiming they don't have spares for my phone, tried to explain that it is not a hardware issue, but all in vain .
Anyway, ill go over your instructions and ill update the results soon.
When I got home I turned on the FTV and briefly saw an update prompt, ands then I must of accidentally hit the accept button on the remote and the device started to remote and update but I immediately pulled the power cord to prevent the update.
Now I have no idea what to do next. Is there anyway to stop the update when I plug it in ands if not, will I able to get root again?
Thanks for all the help everyone.
madtork said:
When I got home I turned on the FTV and briefly saw an update prompt, ands then I must of accidentally hit the accept button on the remote and the device started to remote and update but I immediately pulled the power cord to prevent the update.
Now I have no idea what to do next. Is there anyway to stop the update when I plug it in ands if not, will I able to get root again?
Thanks for all the help everyone.
Click to expand...
Click to collapse
Do you have cwm recovery? If so you could boot to it and do a factory reset, then be sure to pm disable updates. For now I'd block amazon domains on your router but that's not a 100% guarantee. Aftvnews should have any info you need.
I don't think I installed CMW. Is there anyway to tell at this point, and if it's installed, how do I boot into it? I blocked Amazon updates with my router but recently connected with my phone's hotspot without thinking and it must of downloaded the update then.
Anyone have any other recommendations at this point? If I don't have CWM am I out of luck?
madtork said:
Anyone have any other recommendations at this point? If I don't have CWM am I out of luck?
Click to expand...
Click to collapse
If you do have ClockworkMod, then you're safe because it will prevent the update from installing. A Fire TV with ClockworkMod that gets an OTA update will download the update, then restart the Fire TV in recovery mode. Since stock recovery has been replaced with ClockworkMod, it will just ignore the stock update.
If you don't have ClockworkMod, you can use the ALT+PrintScreen+i method to hopefully get into stock recovery without installing the update. From there, I would clear the cache partition and do a factory reset. More info on how to do that can be found here: http://www.aftvnews.com/how-to-unbr...ry-mode-and-factory-reset-the-amazon-fire-tv/
I don not know if that will work, but it's your best bet.
AFTVnews.com said:
If you do have ClockworkMod, then you're safe because it will prevent the update from installing. A Fire TV with ClockworkMod that gets an OTA update will download the update, then restart the Fire TV in recovery mode. Since stock recovery has been replaced with ClockworkMod, it will just ignore the stock update.
If you don't have ClockworkMod, you can use the ALT+PrintScreen+i method to hopefully get into stock recovery without installing the update. From there, I would clear the cache partition and do a factory reset. More info on how to do that can be found here: http://www.aftvnews.com/how-to-unbr...ry-mode-and-factory-reset-the-amazon-fire-tv/
I don not know if that will work, but it's your best bet.
Click to expand...
Click to collapse
That's what I was hoping for. Thanks for the information!
So I connected a keyboard and tried for an hour or better to get this thing into recovery but with no success. I tried the ALT+PRT SCRN+I and it just won't work. It keeps going into the update screen and I keep unplugging the box. If someone can help me get this going I will PAYPAL YOU $20!
Otherwise I am giving this thing away.
madtork said:
So I connected a keyboard and tried for an hour or better to get this thing into recovery but with no success. I tried the ALT+PRT SCRN+I and it just won't work. It keeps going into the update screen and I keep unplugging the box. If someone can help me get this going I will PAYPAL YOU $20!
Otherwise I am giving this thing away.
Click to expand...
Click to collapse
It's thankfully never happened to me but just from reading here, it can be incredibly hard to get to recovery. They're mostly trying to get to cwm (which I believe you don't have?) But in theory I think it should work with stock...
If possible, try a different keyboard. If using a hub then connect it directly. Change your timing (when you actually press the keys) Alter between holding them down the keys and tapping them. And just for the heck of it, try working in the remote at some point (back button and right arrow for 15 seconds performs reset)
Sorry. It sounds silly but many people have needed to get to recovery and no one can definitively say what works for everyone. At least I don't think anyone can??? Good luck
AFTVnews.com said:
If you do have ClockworkMod, then you're safe because it will prevent the update from installing. A Fire TV with ClockworkMod that gets an OTA update will download the update, then restart the Fire TV in recovery mode. Since stock recovery has been replaced with ClockworkMod, it will just ignore the stock update.
If you don't have ClockworkMod, you can use the ALT+PrintScreen+i method to hopefully get into stock recovery without installing the update. From there, I would clear the cache partition and do a factory reset. More info on how to do that can be found here: http://www.aftvnews.com/how-to-unbr...ry-mode-and-factory-reset-the-amazon-fire-tv/
I don not know if that will work, but it's your best bet.
Click to expand...
Click to collapse
KLit75 said:
It's thankfully never happened to me but just from reading here, it can be incredibly hard to get to recovery. They're mostly trying to get to cwm (which I believe you don't have?) But in theory I think it should work with stock...
If possible, try a different keyboard. If using a hub then connect it directly. Change your timing (when you actually press the keys) Alter between holding them down the keys and tapping them. And just for the heck of it, try working in the remote at some point (back button and right arrow for 15 seconds performs reset)
Sorry. It sounds silly but many people have needed to get to recovery and no one can definitively say what works for everyone. At least I don't think anyone can??? Good luck
Click to expand...
Click to collapse
That's the best reply yet. Your correct, I don't have Clock work recovery. I'll try to add in the remote to the equation. Thank you for your input.
Anyone want a free Amazon FTV? I can't get it into recovery.
I'll take it!
madtork said:
Anyone want a free Amazon FTV? I can't get it into recovery.
Click to expand...
Click to collapse
I'll take it!!!! I dont know how to fix, but will try my damnedest!
Can you email [email protected]?
---------- Post added at 01:04 AM ---------- Previous post was at 01:00 AM ----------
Lowaek said:
I'll take it!!!! I dont know how to fix, but will try my damnedest!
Can you email [email protected]?
Click to expand...
Click to collapse
I will also pay shipping!
Preface: I am an Android app developer who has had an Apple phone for quite some time, but recently made the switch to stop using work devices.
So I recently purchased my Pixel XL, and tried to run the iPhone transfer thing upon first start. Unfortunately, I was met with a terrible fate of the Pixel dying! Now, with a dead Pixel, I was able to charge it and run it again. I ran the transfer, it worked, great!. Now, all was well and dandy until I restarted the device. After restarting the device, my phone was stuck in a boot loop, bummer. I researched it and found something along the lines of unlocking the phone or something of that nature in order to fix my problem, so I followed the steps. Then it says to run "fastboot continue." Would have been great if that worked, but it didn't. So then I resorted to entering the recovery mode and choosing to factory reset the device, as per advice from another source. Now, by resetting the device, it removed developer options, so I am no longer able to sideload the OTA file AND the phone still won't boot! I waited for 30 minutes praying it would boot, but alas, no results. I'm thinking about taking the phone back to Verizon and seeing what I can get done. I would like to avoid this if at all possible, but if I don't have a solution within 12 or so hours, I'm going to be forced to consulting with Verizon. Any advice is greatly appreciated.
Attempting to sideload the device...
adb sideload '/home/caw0086/Downloads/marlin-ota-nde63x-3c8add4e.zip'
loading: '/home/caw0086/Downloads/marlin-ota-nde63x-3c8add4e.zip'
error: insufficient permissions for device
Further Attempts:
adb kill-server
sudo adb start-server
NICE
sudo adb sideload '/home/caw0086/Downloads/marlin-ota-nde63x-3c8add4e.zip'
serving: '/home/caw0086/Downloads/marlin-ota-nde63x-3c8add4e.zip' (~7%)
....
It stopped.
I think the phone legitimately died during the sideload..
Turns out it did......
WE HAVE LIFE, MAYBE.
sudo adb sideload '/home/caw0086/Downloads/marlin-ota-nde63x-3c8add4e.zip'
Total xfer: 2.00x
It sideloaded, apparently. And now we wait.
AAAAAND dots.
Just going to reiterate, I have no idea what the hell I'm doing, but there's a solid effort being made here.
The dots seem to be endless... I really wish this wasn't happening right now. I tried so hard. I got so far.
But in the end,
It doesn't even matter. :'(
HOLY **** I FIXED IT.
Thanks to anyone who read this. I fixed my problem without you guys. When Google doesn't help, **** with it until it works. That's my motto now.
Solution:
Recovery mode, get into the options, adb update, then pop open your terminal of choice, kill the current adb service (adb kill-server), then run adb as root (sudo adb start-server), then run adb sideload {PATH_TO_OTA_FILE}. Then you wait for what seems like 5-10 minutes for the dots to stop being indecisive and finally decide to become the Google 'G'. When that happens, you're golden. If you have a similar problem, you're in luck, because I just figured this **** out for you. Otherwise, just keep screwing with the options in Recovery mode until something just works. That's what I did. Now I have a phone again.
What a rollercoaster of emotions this was.
I'm simultaneously the smartest and dumbest individual on this planet.
Corey5Star said:
What a rollercoaster of emotions this was.
I'm simultaneously the smartest and dumbest individual on this planet.
Click to expand...
Click to collapse
Whoa
Sent from my sailfish using XDA Labs
Holy crap man, I was attempting to install Weta on my Pixel and ended up not being able to fastboot the device. Flash-all kept giving me an error of the image being too large, and everyone else's recommendations kept making things worse; one ven broke the twrp on my phone. I tried what you said and boom. It booted first try!
Thanks from a college student who thought he just threw 600$+ away
scarface0311 said:
Holy crap man, I was attempting to install Weta on my Pixel and ended up not being able to fastboot the device. Flash-all kept giving me an error of the image being too large, and everyone else's recommendations kept making things worse; one ven broke the twrp on my phone. I tried what you said and boom. It booted first try!
Thanks from a college student who thought he just threw 600$+ away
Click to expand...
Click to collapse
Is your SDK up to date. A lot of people getting that error say it was fixed by updating the SDK.
It was not. I'll take that as what was hopefully causing the issue, as I don't want to repeat it and not get as lucky next time. Thanks for the direction
Google Pixel boot loop after installing the wrong SuperSu version
I was able to installed twrp and I flashed the wrong supersu version on my Google Pixel. Now my phone is stock in boot loop. I can't get go to recovery mode. I tried to sideload ota but adb doesn't recognize my device. Any idea what I can do? Help please. Thanks
pabsoul said:
I was able to installed twrp and I flashed the wrong supersu version on my Google Pixel. Now my phone is stock in boot loop. I can't get go to recovery mode. I tried to sideload ota but adb doesn't recognize my device. Any idea what I can do? Help please. Thanks
Click to expand...
Click to collapse
Hello,
What SuperSU version did you install?
Good luck...
Corey5Star said:
Preface: I am an Android app developer who has had an Apple phone for quite some time, but recently made the switch to stop using work devices.
Solution:
Recovery mode, get into the options, adb update, then pop open your terminal of choice, kill the current adb service (adb kill-server), then run adb as root (sudo adb start-server), then run adb sideload {PATH_TO_OTA_FILE}. Then you wait for what seems like 5-10 minutes for the dots to stop being indecisive and finally decide to become the Google 'G'. When that happens, you're golden. If you have a similar problem, you're in luck, because I just figured this **** out for you. Otherwise, just keep screwing with the options in Recovery mode until something just works. That's what I did. Now I have a phone again.
Click to expand...
Click to collapse
Could you point a non-developer willing to follow instructions to a source that can provide step-by-step instructions for how to do what you did? I have a Pixel XL that I cannot return/warranty claim, and no matter what I do I cannot get it to keep from going in boot circles. I cannot get it to go into recovery mode. Selecting that option doesn't work.
I didn't use a source, I just tinkered with it until it worked. If I remember correctly, you need to hold down power button and the volume up button when turning on the device. Go into that option, connect your phone to the computer, either open up a terminal or Android Studio and type the things I said in the OP.
Just got the XL on Friday. Loved it.
Unlocked the bootloader about 45 minutes ago. Wiped upon reboot (as normal). Google logo displayed with progress bar but the animation never stopped.
Downloaded the factory image from Nov. Ran the flash-all.bat from bootloader. No errors. Rebooted. Got a "Your device is corrupt" error. Phone stuck on the Google boot screen. Going into recovery just gives me a dead droid.
Attempting to flash the 8.1 developer preview results in the same issue. As of right now, nothing seems to boot at all. I've changed USB-C cables, since I've read about those causing issues, but still the same.
derekr44 said:
Just got the XL on Friday. Loved it.
Unlocked the bootloader about 45 minutes ago. Wiped upon reboot (as normal). Google logo displayed with progress bar but the animation never stopped.
Downloaded the factory image from Nov. Ran the flash-all.bat from bootloader. No errors. Rebooted. Got a "Your device is corrupt" error. Phone stuck on the Google boot screen. Going into recovery just gives me a dead droid.
Attempting to flash the 8.1 developer preview results in the same issue. As of right now, nothing seems to boot at all. I've changed USB-C cables, since I've read about those causing issues, but still the same.
Click to expand...
Click to collapse
I have no experience with your issue but it sounds like a soft brick. Im sure if you follow this guide ypu can fix it. https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418 hopefully this helps until someone who really knows can help you.
Dielahn said:
I have no experience with your issue but it sounds like a soft brick. Im sure if you follow this guide ypu can fix it. https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418 hopefully this helps until someone who really knows can help you.
Click to expand...
Click to collapse
That simple thread actually gave me an idea. I grabbed the latest SDK tools. Presto!
Note to anyone else with this issue...
derekr44 said:
Just got the XL on Friday. Loved it.
Unlocked the bootloader about 45 minutes ago. Wiped upon reboot (as normal). Google logo displayed with progress bar but the animation never stopped.
Downloaded the factory image from Nov. Ran the flash-all.bat from bootloader. No errors. Rebooted. Got a "Your device is corrupt" error. Phone stuck on the Google boot screen. Going into recovery just gives me a dead droid.
Attempting to flash the 8.1 developer preview results in the same issue. As of right now, nothing seems to boot at all. I've changed USB-C cables, since I've read about those causing issues, but still the same.
Click to expand...
Click to collapse
By the way, the dead Droid is recovery, from that screen, hold power and press up for recovery menu, in case you ever get stuck again
And just for future reference for others who may be in a similar issue and stumble across this thread...
As long as you've successfully unlocked your bootloader and "fastboot devices" successfully pulls up your device, you'll be just fine. You just gotta take a step back, breath and then make sure your SDK tools are updated before moving forward.
if the flash tool isn't working, use my script:
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
i know this is probably going to sound really stupid but somehow i bricked my phone as well....not exactly sure what happened but it had to do with something after installing/booting TWRP. anyway, i am stuck with nothing on my phone and can't seem to do anyting....derek, how did you use sdk to fix???
*edit I can't even have fastboot devices pull my phone....am i really f'ed?
warlord1352 said:
i know this is probably going to sound really stupid but somehow i bricked my phone as well....not exactly sure what happened but it had to do with something after installing/booting TWRP. anyway, i am stuck with nothing on my phone and can't seem to do anyting....derek, how did you use sdk to fix???
*edit I can't even have fastboot devices pull my phone....am i really f'ed?
Click to expand...
Click to collapse
If you cannot get the Bootloader to load, then you are seriously SOL. You have a hard bricked device.
Only thing you can do now is raise a support case with Google and hope that allow you to get a replacement with the only explanation being, "The phone restarted on it's own and never came back up." Or something similar and vague without expressly telling them what you did.
warlord1352 said:
i know this is probably going to sound really stupid but somehow i bricked my phone as well....not exactly sure what happened but it had to do with something after installing/booting TWRP. anyway, i am stuck with nothing on my phone and can't seem to do anyting....derek, how did you use sdk to fix???
*edit I can't even have fastboot devices pull my phone....am i really f'ed?
Click to expand...
Click to collapse
Make sure you try a different cable to connect your phone to your PC.. I had the same issue, and I try two different cable before my device accepted the flash-all
Okay, so somehow fortunately I was able to get back into my TWRP 1 last time and able to push my files I needed to boot it back up...
Raistline said:
If you cannot get the Bootloader to load, then you are seriously SOL. You have a hard bricked device.
Only thing you can do now is raise a support case with Google and hope that allow you to get a replacement with the only explanation being, "The phone restarted on it's own and never came back up." Or something similar and vague without expressly telling them what you did.
Click to expand...
Click to collapse
The funny thing is I was able to and was in bootloader but I couldn't use any commands from my computer (as far as I know) which is why I was freaking out.
I should've but I didn't actually try using other cables. I did try other usb ports but that didn't do anything.
I still kind of believe that my phone (somehow) got messed up from loading TWRP. I don't know if it's because it is still beta or what but I am like 99% sure it was from that as I can't see anything else being the problem.
warlord1352 said:
i know this is probably going to sound really stupid but somehow i bricked my phone as well....not exactly sure what happened but it had to do with something after installing/booting TWRP. anyway, i am stuck with nothing on my phone and can't seem to do anyting....derek, how did you use sdk to fix???
*edit I can't even have fastboot devices pull my phone....am i really f'ed?
Click to expand...
Click to collapse
just install the lastest fastboot and adb drivers from google and flash the factory image using commands or use any script .
after that everytime my phone got stuck on google logo .
how i fixed - Temporary boot twrp beta2 recovery using cmd (fastboot boot abc.img) "here abc refers to the correct name of the img file" and once booted into recovery go to advanced and select Partition A and reboot.
It will boot up just fine
Here is the link for a script that will flash both partitions with stock image
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
derekr44 said:
Just got the XL on Friday. Loved it.
Unlocked the bootloader about 45 minutes ago. Wiped upon reboot (as normal). Google logo displayed with progress bar but the animation never stopped.
Downloaded the factory image from Nov. Ran the flash-all.bat from bootloader. No errors. Rebooted. Got a "Your device is corrupt" error. Phone stuck on the Google boot screen. Going into recovery just gives me a dead droid.
Attempting to flash the 8.1 developer preview results in the same issue. As of right now, nothing seems to boot at all. I've changed USB-C cables, since I've read about those causing issues, but still the same.
Click to expand...
Click to collapse
Something similar for me but with different reason for starting all this. When I did sideload of 8.1 all went well but my camera wasn't working (I saw the same thing in 8.1 DP) so I needed to go back to 8.0 but you can't sideload downgrade. I went to Google to get replacement sent and figure I might try to sort things out with this one in the meantime. I had to unlock to be able to just flash the factory 8.0 image so did that with both the unlock commands, then after that and after update I just got hung on the white screen with google logo. I was able to get back to bootloader with the power button + volume from off and from there I would get to the screen with the android and the exclamation point - I think you hold volume up and then power to go to sideload. Once there I just sideloaded 8.0 and all was good. I do still get the warning about corrupt whatever and have to hit power on reboot or fresh power up but I could redo the locks and whatnot and all seems fine now with camera working.
At the least I got camera back while waiting for replacement.
b4db0ys said:
just install the lastest fastboot and adb drivers from google and flash the factory image using commands or use any script .
after that everytime my phone got stuck on google logo .
how i fixed - Temporary boot twrp beta2 recovery using cmd (fastboot boot abc.img) "here abc refers to the correct name of the img file" and once booted into recovery go to advanced and select Partition A and reboot.
It will boot up just fine
Here is the link for a script that will flash both partitions with stock image
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Click to expand...
Click to collapse
This cleaned things up for me - still no camera in 8.1 but I got the replacement coming.
So I'm in the same boat as the OP but my bootloader is locked. Am I totally screwed? Is there a way to do any of this when the device won't show up in ADB?
Deuces said:
if the flash tool isn't working, use my script:
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Click to expand...
Click to collapse
can you just develop some scripts that working on locked bootloader ?
i have a bricked Pixel xl with locked bootloader and oem locked
If you can boot twrp but can't connect to a pc, a type c flash drive comes in handy. Load it with the needed ota, twrp installer zip and Just mount it and you're good to go.