Develop Bugs

Someone, please help me! :(

When I boot up my tablet, I get nonstop error messages telling me things have stopped working. I tried getting help from someone else on a different site, and this is what they told me to say: I flashed the GROUPER lollipop ROM onto a FLO. Someone please help me!!! It's a totally clean tablet. no files on it except android.

Go to Google's Nexus firmware page, download the appropriate firmware, follow the instructions: https://developers.google.com/android/nexus/images
Only thing I don't know is whether or not you'll have to repartition the internal flash.

I'm a dummy.
nhizzat said:
Go to Google's Nexus firmware page, download the appropriate firmware, follow the instructions:
Only thing I don't know is whether or not you'll have to repartition the internal flash.
Click to expand...
Click to collapse
i don't understand how to do all that though I'm not good with command prompts... and nexus root tool kit has done me no good. Could you dumb down the instructions for me?

Then it's time for you to learn. The page has step-by-step instructions. There isn't any way too dumb down the instructions.
You have to start somewhere. Now is a good time. If you had learned before, you wouldn't be in this predicament.
So sit down, take a couple deep breaths, then read the instructions a few times. Download the Android SDK and factory image, then get everything set up. Don't panic, it's not nearly as difficult as you're making it out to be. Stop psyching yourself out. Take it step by step. If you get stuck, leave the cmd prompt and post the issue you've run into here.
Might help if you type out the instructions here after you've read them over several times. I'm glad to help but you gotta take ownership of your tablet and put in some effort to learn and educate yourself.
Just try, I'm sure you'll understand it by the end of tonight or the end of the weekend. You don't have to be a master of fastboot and adb, I sure as hell am not. I never recommend the use of toolkits, especially by those with no understanding of fastboot and adb. Once you have a basic understanding of fastboot and adb, go ahead and use any toolkit you want because by then you'll know how to get yourself out of any jams using those 2 tools.

It is almost impossible to hard brick this device, even if you flash the wrong ROM on this device..
Download this utility and it will bring your Nexus back to life....
http://www.wugfresh.com/nrt/

Giving up
nhizzat said:
Then it's time for you to learn. The page has step-by-step instructions. There isn't any way too dumb down the instructions.
You have to start somewhere. Now is a good time. If you had learned before, you wouldn't be in this predicament.
So sit down, take a couple deep breaths, then read the instructions a few times. Download the Android SDK and factory image, then get everything set up. Don't panic, it's not nearly as difficult as you're making it out to be. Stop psyching yourself out. Take it step by step. If you get stuck, leave the cmd prompt and post the issue you've run into here.
Might help if you type out the instructions here after you've read them over several times. I'm glad to help but you gotta take ownership of your tablet and put in some effort to learn and educate yourself.
Just try, I'm sure you'll understand it by the end of tonight or the end of the weekend. You don't have to be a master of fastboot and adb, I sure as hell am not. I never recommend the use of toolkits, especially by those with no understanding of fastboot and adb. Once you have a basic understanding of fastboot and adb, go ahead and use any toolkit you want because by then you'll know how to get yourself out of any jams using those 2 tools.
Click to expand...
Click to collapse
I'm officially giving up. Nothing works. It boots into the OS and then pops up a bunch of error messages. I've tried lollipop, kitkat, cyanogenmod, locked bootloader, unlocked bootloader, and I'm done. GR! Thank you though, for your help.

Boucherwayne78 said:
I'm officially giving up. Nothing works. It boots into the OS and then pops up a bunch of error messages. I've tried lollipop, kitkat, cyanogenmod, locked bootloader, unlocked bootloader, and I'm done. GR! Thank you though, for your help.
Click to expand...
Click to collapse
So that means you will sell it to me for $20?

Boucherwayne78 said:
I'm officially giving up. Nothing works. It boots into the OS and then pops up a bunch of error messages. I've tried lollipop, kitkat, cyanogenmod, locked bootloader, unlocked bootloader, and I'm done. GR! Thank you though, for your help.
Click to expand...
Click to collapse
Nothing works? Just flash the factory image. Flashing Roms in recovery isn't going to help you. Before you give up, just use wugs toolkit to save it. If you give up without even trying the right procedure (fastboot flash factory image) then i recommend you not root again after you fix it. But wugfresh toolkit will fix it for you with a couple clicks.

I tried NRTK
madbat99 said:
Nothing works? Just flash the factory image. Flashing Roms in recovery isn't going to help you. Before you give up, just use wugs toolkit to save it. If you give up without even trying the right procedure (fastboot flash factory image) then i recommend you not root again after you fix it. But wugfresh toolkit will fix it for you with a couple clicks.
Click to expand...
Click to collapse
The toolkit doesn't work. I tried that 9 times, both downloading my own OS to flash, and letting the toolkit download it. Every time it either boot loops it or does the error message spam thing again. That's why I was trying to use SDK... And that didn't work either. And my drivers NEVER INSTALL RIGHT, so it's all just slowly killing me inside...

Make sure fastboots working first. Put the tablet in bootloader mode by shutting it off then holding power and volume down (or up I forget, you want the screen that says start at the top and has device info at the bottom left.)
Connect to computer then go into the platform-tools folder in the SDK folder, hold shift and right click over the window>open command prompt here.
Type fastboot devices and hit enter. Does it show a serial number or does it show nothing? (waiting for device or something like that) If nothing you should uninstall all drivers for the tablet in device manager and install the google usb driver from the sdk manager in the sdk you installed.
Once you see the serial number you're almost done. If your bootloader is locked type fastboot oem unlock
Now from the factory image copy the image-razor.zip, bootloader.img and flash-all.bat to the platform-tools folder.
Double click flash-all.bat
That's it.

I think that it will be beneficial for you to look into using virtual machines (VM's). It allows you to run different operating systems directly from your computer.
The second half to this equation is learning to use Linux (Ubuntu is my choice). Since Android is built from Linux, you don't need special drivers to recognize your devices.
Another option to run Ubuntu is to create a Virtual Hard Drive on your PC, and install Ubuntu onto it (YouTube it, and follow the directions carefully).
Lastly, you can always get a flash drive that is 8gb or greater (16gb or 32gb is recommended), and install Ubuntu onto it was well. It will move little slower than your PC, but your issues will be solved and manageable.
Why am I advocating for Ubuntu? Because it works. PM me if your are interested in learning more, but don't expect me to do all of the work. You need to educate yourself a bit to actually follow my instructions.
____________________________
Please remember to:
Check Q & A forums before asking!
Search forum for similar post before creating!
Hit "thanks" to everyone who may have helped you (it costs nothing)!
Read the OP!!!!

Boucherwayne78 said:
The toolkit doesn't work. I tried that 9 times, both downloading my own OS to flash, and letting the toolkit download it. Every time it either boot loops it or does the error message spam thing again. That's why I was trying to use SDK... And that didn't work either. And my drivers NEVER INSTALL RIGHT, so it's all just slowly killing me inside...
Click to expand...
Click to collapse
First off, let me explain that this device is almost impossible to destroy by flashing the wrong rom. Your over reacting due to inexperience, your Nexus is fine as long as you can boot into Fastboot. When the device is powered down, press the power button and the Volume down key for about 30 seconds, if you can boot into Fastboot, your device is just fine.. Nexus devices are extremely hard to hard brick.. RELAX and realize this is a good time to learn something new, this device is the perfect device to experiment with... You seem to not have the patients and you just need to relax watch a few youtube videos.. No one is going to do it for you.. About 5 years ago I was in the same place you are right now, and I took the time to figure how to fix what ever I did to mess it up.. Its not hard once you realize what your doing. The Toolkit is a swiss army knife of tools that can fix, repair and flash stock roms. Did you unlock the bootloader? Take a breather, give it some time and figure it out like we all did at one time or another, none of us here had our hands held during the learning process with Android devices..
Edit: I'm almost sure you did not unlock your device, to know for sure if your device is unlocked you would see a small padlock that appears to be in the unlocked position at the bottom of your screen while powering on.. If you power your Nexus on, and you DO NOT see a unlocked symbol at the bottom of your screen, you DID NOT unlock your device, thus meaning you have to unlock it to flash it properly.. There are dozens of people in this forum right now that would be more than happy to buy your device cheap and fix it themselves.. If they can do it, you can too..

^Yeah like my last post, those are perfectly fine instructions. If that don't work, stuck at "erasing user data" or something you're ****ed. Most likely.Try a different cord/usb 2.0/computer

Tried a few things. Got any other ideas?
Zaphodspeaks said:
First off, let me explain that this device is almost impossible to destroy by flashing the wrong rom. Your over reacting due to inexperience, your Nexus is fine as long as you can boot into Fastboot. When the device is powered down, press the power button and the Volume down key for about 30 seconds, if you can boot into Fastboot, your device is just fine.. Nexus devices are extremely hard to hard brick.. RELAX and realize this is a good time to learn something new, this device is the perfect device to experiment with... You seem to not have the patients and you just need to relax watch a few youtube videos.. No one is going to do it for you.. About 5 years ago I was in the same place you are right now, and I took the time to figure how to fix what ever I did to mess it up.. Its not hard once you realize what your doing. The Toolkit is a swiss army knife of tools that can fix, repair and flash stock roms. Did you unlock the bootloader? Take a breather, give it some time and figure it out like we all did at one time or another, none of us here had our hands held during the learning process with Android devices..
Edit: I'm almost sure you did not unlock your device, to know for sure if your device is unlocked you would see a small padlock that appears to be in the unlocked position at the bottom of your screen while powering on.. If you power your Nexus on, and you DO NOT see a unlocked symbol at the bottom of your screen, you DID NOT unlock your device, thus meaning you have to unlock it to flash it properly.. There are dozens of people in this forum right now that would be more than happy to buy your device cheap and fix it themselves.. If they can do it, you can too..
Click to expand...
Click to collapse
Thank you for your reply. Do you have any suggestions though for my situation? My bootloader was unlocked. I did try locking it then unlocking it several times though. I've tried two seperate stock ROMs, different usb cables, different usb ports, and it now tells me that fastboot is not working. even a link is greatly appreciated. I think it is a driver problem. My tablet does boot into the OS though. I can use the ui for about 10 seconds, then a notification pops up mid-screen: "unfortunately, the process android.process.acore has stopped." Please, even a link is greatly appreciated. I've tried just about everything to get these drivers working, and to get this tablet working. I will continue to research as well. Wish me luck!

Wug's tool has been invaluable to me in the past. I have gone from KitKat to Lollipop, back and forth, different ROMS, stuck boots, bad flashes. Like Zap says if you can get it to Bootloader then get Wug's tool to connect in fastboot, it will do the rest.
A couple times I have ran into problems where my computer has not seen my Nexus 5 because of the drivers, just google nexus usb drivers and install the latest ones.

azsgolf said:
Wug's tool has been invaluable to me in the past. I have gone from KitKat to Lollipop, back and forth, different ROMS, stuck boots, bad flashes. Like Zap says if you can get it to Bootloader then get Wug's tool to connect in fastboot, it will do the rest.
A couple times I have ran into problems where my computer has not seen my Nexus 5 because of the drivers, just google nexus usb drivers and install the latest ones.
Click to expand...
Click to collapse
Got any ideas on Fastboot.exe stopping working when the flash process begins? it fails sending bootloader and then fastboot.exe fails. It says on the screen when i close the error message it's booting into bootloader, but the tablet never restarts. it stays on bootloader(where i had it in the first place.) It should turn off the screen and go back into bootloader. Please, any feedback is appreciated.

Have you tried selecting the option of hardbrick on the tool?

Woke up to a phone in recovery... help!

So... my alarm went off this morning. I hit snooze. I woke up again an hour or so later because it didn't go off again, only to see my phone in recovery mode.
I restarted and never got past the amazon screen... then right back into recovery. Cleared cache - recovery mode. Factory reset - recovery mode. Help!
Installed the Android SDK and got adb set up, but it won't recognize my device.
What is the best course of action?

ediebol said:
So... my alarm went off this morning. I hit snooze. I woke up again an hour or so later because it didn't go off again, only to see my phone in recovery mode.
I restarted and never got past the amazon screen... then right back into recovery. Cleared cache - recovery mode. Factory reset - recovery mode. Help!
Installed the Android SDK and got adb set up, but it won't recognize my device.
What is the best course of action?
Click to expand...
Click to collapse
I'm in a similar position. I found the latest bin in another thread but I get the * cannot read 'update.bin' * error when trying to sideload. Path variables have been set and the bin is in my adb folder.

Same exact thing happened to me today! ;_; Anyone found a solution?

Same issue here on a rooted 4.6.1 phone. Not even detected in adb to push update either. Trying on a different pc now. Guess I'll have to turn off updates on my other phone

Fixed
drewb0y said:
Same issue here on a rooted 4.6.1 phone. Not even detected in adb to push update either. Trying on a different pc now. Guess I'll have to turn off updates on my other phone
Click to expand...
Click to collapse
Well that was a huge pain in the rear. Following the instructions here http://forum.xda-developers.com/fire-phone/help/fire-phone-hang-to-booting-t3131037 I was able to sideload the update bin file and install it. Unfortunately this is after I had already done the erase bit so will have to restore apps etc.
Perhaps this time I'll either skip the rooting or follow the steps listed elsewhere here to disable the updates.

drewb0y said:
Well that was a huge pain in the rear. Following the instructions here http://forum.xda-developers.com/fire-phone/help/fire-phone-hang-to-booting-t3131037 I was able to sideload the update bin file and install it. Unfortunately this is after I had already done the erase bit so will have to restore apps etc.
Perhaps this time I'll either skip the rooting or follow the steps listed elsewhere here to disable the updates.
Click to expand...
Click to collapse
Disable the updates. If an update is necessary or preferable, eventually someone will post the link to update it manually. That way you'd get the update only when you want it

Ugh. I have not had any luck on sideloading... Called Amazon and they are sending a new phone. Will be turning off updates from now on!!

ediebol said:
Ugh. I have not had any luck on sideloading... Called Amazon and they are sending a new phone. Will be turning off updates from now on!!
Click to expand...
Click to collapse
Well done. You haven't done anything that would void the warranty, so it's only natural that Amazon should take the blame.

Pay for Root of Pixel XL - NYC

apologies if this is being put in the wrong forums, but I'm wondering if I could at all pay one of you folk who are more knowledgable in rooting than I am. I'd gladly pay for your time and expertise.. ideally someone in the New York City area.
Cheers.

We can do this for you for free. What kind of Pixel XL do you have? Did you buy it from the Google Store online or from Verizon?

You'll never learn by having someone else do it for you. It's not too difficult if someone gives you some step by step advice and you follow it precisely

https://forum.xda-developers.com/pixel-xl/how-to/guide-how-to-unlock-root-flash-pixel-xl-t3507886

Root
xocomaox said:
We can do this for you for free. What kind of Pixel XL do you have? Did you buy it from the Google Store online or from Verizon?
Click to expand...
Click to collapse
I have a Google store online XL. I am interested in what you have to say. I just got mine but due to commitments have not had time to sift through all of the information available here. I've had Nexus 4 & 5x rooted w/custom roms but Idon't feel comfortable diving into the XL yet. Most of all I am afraid I will miss some thing on page 20 of a multi-page thread that will cause me pain later on.
Thanks

ahunter said:
I have a Google store online XL. I am interested in what you have to say. I just got mine but due to commitments have not had time to sift through all of the information available here. I've had Nexus 4 & 5x rooted w/custom roms but Idon't feel comfortable diving into the XL yet. Most of all I am afraid I will miss some thing on page 20 of a multi-page thread that will cause me pain later on.
Thanks
Click to expand...
Click to collapse
This thread will be the guide you'll want to follow, which assumes you have a Windows PC to connect the phone to:
https://forum.xda-developers.com/pixel-xl/how-to/guide-how-to-unlock-root-flash-pixel-xl-t3507886
Here is my own condensed version of it:
You'll first want to download and install the SDK for the correct tools from here: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Then you should probably turn on USB Debugging from Developer Settings on the phone, and connect it to your computer. Check to see if it is talking to your phone correctly by opening a command prompt from the folder your fastboot/ADB installed to (typically C:\Program Files (x86)\Android\Android SDK\Platform-Tools\) and type: adb devices and hit enter. You should get your device listed.
Next, type adb reboot bootloader and hit enter. Your phone should reboot to the Android guy laying down with his chest open.
The following step ERASES the whole phone!!!
Now type fastboot flashing unlock. This will unlock the bootloader. I would never recommend re-locking this again.
Now type fast boot reboot and your phone will be back to the OS, but if you did it right you get a warning each time you boot up before the boot animation.
Now you can install TWRP. This is easy. Download both the .IMG and the zip from here and put the IMG in that fastboot/ADB folder and put the zip on your phone in the download directory: https://dl.twrp.me/marlin/
Make sure you get the ones that say RC1.
Keep the phone connected after downloading those files, type adb reboot bootloader again to get back to the Android guy.
Then type the following and hit enter: fastboot boot twrp-3.0.2-0-RC1-fastboot-marlin.img
This will boot up TWRP and get you to the menu.
Go to install and browse to the zip you put on the phone and install the TWRP zip. It will do it's thing and complete. You can then reboot to make sure you get into the OS okay. You can disconnect the phone from the PC since you can do everything from TWRP alone.
Now you can root. Just DL the SuperSU zip found here on your phone and put it in the download directory again. https://download.chainfire.eu/1021/SuperSU/SR3-SuperSU-v2.79-SR3-20170114223742.zip
You can now do a restart on your phone and once the screen goes black HOLD the volume down button. You should see the android guy again. You can let go, then cycle thru the options with the volume key until you see recovery on the right in red. Press power to get to TWRP. Then Install, search for SuperSU zip you downloaded, install and reboot.
It will reboot on it's own several times. Just wait a few minutes until you get to the OS again. Congrats you're now rooted.
You can get the kernel of your liking and install the same way as you did with SuperSU.
Hope this helps.

If you can't be bothered to read a thread on rooting, where 99.9% of the important stuff is on the first page and/or post, then you probably can't read the do's and don'ts of using the phone rooted. That just makes me think that you're going to end up with a paperweight at some point that you have zero clue how to fix.
Sent from my Pixel XL

imnuts said:
If you can't be bothered to read a thread on rooting, where 99.9% of the important stuff is on the first page and/or post, then you probably can't read the do's and don'ts of using the phone rooted. That just makes me think that you're going to end up with a paperweight at some point that you have zero clue how to fix.
Sent from my Pixel XL
Click to expand...
Click to collapse
I have rooted and used my paper weights successfully previously and will continue to do so. I can recognize when I need and am willing to ask for help.

xocomaox said:
Now type fastboot flashing unlock. This will unlock the bootloader. I would never recommend re-locking this again.
Click to expand...
Click to collapse
This should be in bold and caps. Having the bootloader kept unlocked may help you out of a bind in the future if you add further tweaks.
Please do not re-lock the bootloader.

It seems that the OP has money instead of patience, he has alreaday gone leaving every warm-hearted guys behind.

Bricked?!?

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.

Help with Rooting Kindle Fire Generation 1

Today I picked one of these up for 3 bucks, since it was 3 bucks. Didn't realize that it was running on Android 2.2 which runs nothing at this point.
I'm trying to both install Google Play and a custom ROM for Android 4.4 if not higher.
However, whenever I follow the guides online, for version 6.3.4 which I am on, it doesn't work. I get to the point where you are in the adb and tell it to boot into fastboot. It never does. However, when I power down and restart, I end up in fastboot.
Noticing this, I decided to just install the TWFP recovery file at this time from KFU, and it claimed it worked.
I then repeated this process to flash FireFireFire.
However, I don't think it worked. I cannot seem to boot into recovery using KFU at all, which makes me believe that TWFP isn't there.
I am rooted, have SuperSU. But I try and update the binaries and that locks up.
Any help appreciated. If it doesn't work out, I'll just use it for reading and nothing much else.

CeruleanDragon37 said:
Today I picked one of these up for 3 bucks, since it was 3 bucks. Didn't realize that it was running on Android 2.2 which runs nothing at this point.
I'm trying to both install Google Play and a custom ROM for Android 4.4 if not higher.
However, whenever I follow the guides online, for version 6.3.4 which I am on, it doesn't work. I get to the point where you are in the adb and tell it to boot into fastboot. It never does. However, when I power down and restart, I end up in fastboot.
Noticing this, I decided to just install the TWFP recovery file at this time from KFU, and it claimed it worked.
I then repeated this process to flash FireFireFire.
However, I don't think it worked. I cannot seem to boot into recovery using KFU at all, which makes me believe that TWFP isn't there.
I am rooted, have SuperSU. But I try and update the binaries and that locks up.
Any help appreciated. If it doesn't work out, I'll just use it for reading and nothing much else.
Click to expand...
Click to collapse
[6.3.4] Flashing FFF and TWRP without Fastboot Cable

sd_shadow said:
[6.3.4] Flashing FFF and TWRP without Fastboot Cable
Click to expand...
Click to collapse
I have followed this, as well as watched the video. Everything is the same until I reach the command
Code:
./fbmode
After this command, I never get a # symbol to show I am still in the su, and the code begins to repeat as so. Written EXACTLY like this, including all symbols beforehand. I commented it to clarify where things were coming from.
Code:
./fbmode
exit //input
exit //output cmd
exit //2nd input
exit //output by cmd
adb reboot //input
adb reboot //output by cmd
And nothing happens

CeruleanDragon37 said:
I have followed this, as well as watched the video. Everything is the same until I reach the command After this command, I never get a # symbol to show I am still in the su, and the code begins to repeat as so. Written EXACTLY like this, including all symbols beforehand. I commented it to clarify where things were coming from.
And nothing happens
Click to expand...
Click to collapse
Skip to the part were it's in Fastboot mode
Sent from my sailfish using XDA Labs