Related
Seems a few are having the same problem as me after trying to flash 5.0
My Nexus will no longer boot past the Google Logo (White one). I can only access the Bootloader. When I try to go to recovery I see the TWRP logo but stays stuck there. I tried flashing a new image a few times but always had the same problem.
I then tried to relock the bootloader and unlock again again to prepare a fresh install. This is where it gets worse. I managed to lock the bootloader but I can no longer unlock. I get to the screen warning that data will be wiped if I choose "YES", but when I do proceed, I stay stuck on "Erasing userdata...". I left it for 5 hours and was still stuck with the same message.
I cant see what else I can do now.
Ive read a few threads saying its a motherboard issue. Seems weird that it appeared when I tried to install Lollipop. Also seems Im not the only one.
this worked for me
I'm sure someone wiser will respond to you later but ..... I've been in a similar situation.
I use Windows 7 64bit and always connect device with usb 2 port (i.e. not usb3).
I was getting stuck on the google logo with an open lock symbol low on the screen - indicating unlocked bootloader. Like you could get into recovery but unable to get any further once there.
Try using Wugfresh's Nexus Root Tool. Look in the development thread. I'd suggest reading his faq's.
Download and install the latest version 1.9.6 (as I recall) - I had problems when using the earlier versions.
Get an stock image downloaded.
Then you should be able to flash the image using the force flash method he mentions in his faq. You set it in the options menu.
Set USB debugging on the device and usb options for storage to ptp rather than mtp - that's what worked for me.
You'll probably see repeated "installing driver" messages and new "open location" popups as you go through it.
(if your bootloader is locked you'll need to unlock it first. - just re-read your original post and I'm hoping that the latest NRT version will get you unlocked OK.)
If you have problems with this at first try going through the driver installation section of the tools.
After that you can use the same tool to root it. That didn't work completely but did allow me to use an OTG flash drive. If you need full root there's a patch you need to flash - Key Pie patch - took me a while to find it but it's somewhere on these forums.
After the problems I had everything went smoothly in the end. Just be prepared to watch it go through various rebootings while the magic is being done.
Apologies if this is a bit haphazard - I tend to try and rush through things and then forget what it was exactly I did!
I have tried NRT but cant do anything as I cant unlock the bootloader. I have tried both Fastboot and NRT, they both block at "erasing userdata".
Just a thought
Sorry to hear that.
Have you tried "Flash Stock + unroot" with the "Soft-bricked/Bootloop" option in NRT? I now recall that's something that helped me get mine recovered. Just a thought.
I recall reading forum posts that suggested I might have motherboard issues - but I didn't believe it was likely to be the case so I kept trying.
Tried all NRT options including force flash.
Problem is none work with the locked bootloader.
Nexus Root Toolkit v1.9.7 out now
Change log:
What’s new in Nexus Root Toolkit 1.9.7: November 16th, 2014
· Included the latest Masterlists to prevent users who never utilized the “Update” in the kit from getting the AutoIt error (for KTU84P Nexus 7 2013). This error was due to the modified boot.img for that build being accidentally removed from the server. Its was then reuploaded and the masterlists were updated, but those users who never updated would still get the error.
· No longer will the “Force Flash” recommendation be made to N4 users, because it seems to cause a bootloop – however factory resting will fix that either way.
IDEM
I spent exactly the same as you, I also lock the bootloader and now I can not do anything, always get "write failure" and when I try to unlock stays forever "erase ..."
There will be some way to revive it?
Cursed Android 5.0!
If the problem is confirmed to be Android 5.0, Google can help solve these problems?
Use the instructions to reflash your bootloader.
http://blog.laptopmag.com/how-to-hard-reset-a-bricked-nexus-7-with-your-pc
Note replace the instructions to download 4.1.1. with the correct version of the ROM you want to flash. Make sure you grab the correct version for your device. Flashing the wrong bootloader can hard brick your NEXUS with no chance of recovery. Also don't relock your bootloader unless you are certain that you will never want to flash again. Unlocking wipes all of your data and you also can't be rooted if you lock it again.
Doesnt work. Cant get passed the first step. After 1 hour its still "erasing boot..."
I flashed 5.0 successfully... You can't send it to Google with warranty? Try on other computer, do it manually using fastboot and don't give up!
As long as you can still boot into Fast Boot..
Your device can be restored..
I suggest using Wugfresh's Nexus toolkit
http://www.wugfresh.com/nrt/
The issues coming from the latest upgrade are common problems when ever we upgrade..
Its always better if you know how, just use the Nexus Toolkit and install the factory image..
Then it will sit at bootup for about 5-7 mins, then restore your apps... Profit
OTAs will always cause issues with some devices..
Zaphodspeaks said:
As long as you can still boot into Fast Boot..
Your device can be restored..
I suggest using Wugfresh's Nexus toolkit
http://www.wugfresh.com/nrt/
The issues coming from the latest upgrade are common problems when ever we upgrade..
Its always better if you know how, just use the Nexus Toolkit and install the factory image..
Then it will sit at bootup for about 5-7 mins, then restore your apps... Profit
OTAs will always cause issues with some devices..
Click to expand...
Click to collapse
Again.. I cant unlock the bootloader whether manually trying with fastboot or running NRT. Flashing a stock image is not possible.
tigerdim said:
Again.. I cant unlock the bootloader whether manually trying with fastboot or running NRT. Flashing a stock image is not possible.
Click to expand...
Click to collapse
If you have not tried the latest version of NRT, you may of fried your locked bootloader..
Regardless, don't give up... Someone will come to the rescue.. Nexus devices are pretty robust..
Try using another cable, make sure you have the correct driver, double check in Device Manager...
Then try again with the lastest NRT.. Mine just updated.. As a rule of thumb its better not to use a USB hub if thats the case.. Try swapping out your cable, make sure you have the Nexus drivers... I had to re install mine..
tigerdim said:
Doesnt work. Cant get passed the first step. After 1 hour its still "erasing boot..."
Click to expand...
Click to collapse
I'm in the exact same spot. Also, I know that I don't have USB debugging enabled, so not sure if I'm blocked out because of that. Very frustrating.
The computer sees the tablet though. If I click on List Devices in NRT Advanced Utilities, it shows my serial # fastboot.
update: I tried the Unlock command and it goes to the Unlock Bootloader screen. I click Yes, but then the device just hangs on that screen (I let it sit for 30-40 minutes). Ideas?
dayz3r0 said:
I'm in the exact same spot. Also, I know that I don't have USB debugging enabled, so not sure if I'm blocked out because of that. Very frustrating.
The computer sees the tablet though. If I click on List Devices in NRT Advanced Utilities, it shows my serial # fastboot.
update: I tried the Unlock command and it goes to the Unlock Bootloader screen. I click Yes, but then the device just hangs on that screen (I let it sit for 30-40 minutes). Ideas?
Click to expand...
Click to collapse
It hangs because its probably stuck at "erasing userdata". If you do it manuall with fastboot oem unlock you will see this in the cmd window.
tigerdim said:
It hangs because its probably stuck at "erasing userdata". If you do it manuall with fastboot oem unlock you will see this in the cmd window.
Click to expand...
Click to collapse
yep, it does
I ve given up . Bought a Nexus 9. Wasted too much time on this.
Having the same problem
My Nexus 7 (2013 32gb wifi) was working just fine on Monday. Had an unusual freeze up when I was reading something on Adobe Acro., but a quick reboot had it running again. I remember a notification about a system update but didn't pay it much mind. Later that evening I went to pick the N7 up and it was stuck on the Google loading screen. Freezes at Google loading screen when I attempt Recovery mode from Fastboot. Fastboot OEM unlock gives me the same stall at 'erasing user data' as mentioned above (left it on for this for 12+ hours yesterday and nothing). I haven't tried a different cable other than stock yet but I have tried multiple ports and two different machines to unlock the bootloader so I can flash the OS. No other functions with NRT (1.9.9) work including forced flash+unroot. I can't even flash the bootloader or erase or format any partitions. Feeling a little SOL here and I think it has something to do with Lollipop update.
N7 was unrooted and used for reading for the past couple weeks, so pretty vanilla use over the recent past.
4 months out of warranty with Asus and they want an est. $100 for RMA. Google tossed me to them after dragging me through the basic stuff I've been doing the past few days. Going to keep messing with it I suppose once exams are over but feel like I'm running out of things to try. If anyone has any suggestions, questions or a solution, posting them here would be much appreciated.
My upgrade from 4.4.4 to 5.0.1 took ages. It was like bouncing the four small balls for perhaps 5 minutes. Just have patience.
I would recommend not to use xposed or titanium backup as I expect those programs mess with /system files and that can break the android upgrade script. Just disable any unwanted bloatware in regular application control. At least all my updates have been successful so far. Yes, I am rooted.
Good luck.
---------- Post added at 12:51 AM ---------- Previous post was at 12:45 AM ----------
For Wugfresh excellent "Nexus Root Toolkit" to work you need to enable usb debugging in developer menu. You enable the developer menu by tapping a lot on your version information.
The usb debugging gets reset on every upgrade.
Mordecai253 said:
My Nexus 7 (2013 32gb wifi) was working just fine on Monday. Had an unusual freeze up when I was reading something on Adobe Acro., but a quick reboot had it running again. I remember a notification about a system update but didn't pay it much mind. Later that evening I went to pick the N7 up and it was stuck on the Google loading screen. Freezes at Google loading screen when I attempt Recovery mode from Fastboot. Fastboot OEM unlock gives me the same stall at 'erasing user data' as mentioned above (left it on for this for 12+ hours yesterday and nothing). I haven't tried a different cable other than stock yet but I have tried multiple ports and two different machines to unlock the bootloader so I can flash the OS. No other functions with NRT (1.9.9) work including forced flash+unroot. I can't even flash the bootloader or erase or format any partitions. Feeling a little SOL here and I think it has something to do with Lollipop update.
N7 was unrooted and used for reading for the past couple weeks, so pretty vanilla use over the recent past.
4 months out of warranty with Asus and they want an est. $100 for RMA. Google tossed me to them after dragging me through the basic stuff I've been doing the past few days. Going to keep messing with it I suppose once exams are over but feel like I'm running out of things to try. If anyone has any suggestions, questions or a solution, posting them here would be much appreciated.
Click to expand...
Click to collapse
They quote you $100 RMA, but once you send it in they will send you an invoice for $200. $165 for the motherboard, $25 labor and $10 return shipping. I fought it and they eventually dropped $10 for the return shipping. Last time I ever deal with Asus.
Sent from my Nexus 9 using Tapatalk
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?
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.
Hello,
I'm a complete noob with this. Been a long time since I've been doing any sort of android modifications but I recently got an old desire z to mess around with and I really want to install some custom roms. I'm in the process of trying to unlock the bootloader on HTC dev and I'm just having an absolute nightmare at the moment. Been searching everywhere for answers but couldn't find anything that worked, so I thought I'd ask here.
Basically, I'm stuck at a point where I'm supposed to be entering some commands in command prompt. I'm on the fastboot screen but my pc doesn't seem to recognize my device. Leaving me with 'waiting for device' in the command prompt window. My phone is recognized with no issues when it's turned on and being used normally. I have downloaded HTC sync and installed it.
Would highly appreciate some suggestions as it's slowly turning me crazy haha
Thanks
moose.splash1 said:
Hello,
I'm a complete noob with this. Been a long time since I've been doing any sort of android modifications but I recently got an old desire z to mess around with and I really want to install some custom roms. I'm in the process of trying to unlock the bootloader on HTC dev and I'm just having an absolute nightmare at the moment. Been searching everywhere for answers but couldn't find anything that worked, so I thought I'd ask here.
Basically, I'm stuck at a point where I'm supposed to be entering some commands in command prompt. I'm on the fastboot screen but my pc doesn't seem to recognize my device. Leaving me with 'waiting for device' in the command prompt window. My phone is recognized with no issues when it's turned on and being used normally. I have downloaded HTC sync and installed it.
Would highly appreciate some suggestions as it's slowly turning me crazy haha
Thanks
Click to expand...
Click to collapse
You need the right fastboot drivers.. also don't go the HTC devices route, use gfree method
See here for more info
http://forum.xda-developers.com/showthread.php?t=2348266&page=16
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