Related
1. Do I need to restore the phone to rooted Stock prior to having Alejandrissimo unlock my phone?
2. With the locked bootloader, CWM installs itself to /system. Do I still use the same recovery, or is there a different one I'll need to use? Or do you no longer need to use the recovery?
3. Does unlocking the bootloader wipe the phone, requiring I install a new kernel and ROM right after?
4. How do I reinstall the stock kernel if I need to take my phone in for service? (Yes, I know about voiding the warranty.)
netizenmt said:
1. Do I need to restore the phone to rooted Stock prior to having Alejandrissimo unlock my phone?
2. With the locked bootloader, CWM installs itself to /system. Do I still use the same recovery, or is there a different one I'll need to use? Or do you no longer need to use the recovery?
3. Does unlocking the bootloader wipe the phone, requiring I install a new kernel and ROM right after?
4. How do I reinstall the stock kernel if I need to take my phone in for service? (Yes, I know about voiding the warranty.)
Click to expand...
Click to collapse
1) nope
2) all the kernels have a built in recovery, so that one doesn't really matter
3) nope, with testpoint, it just unlocks the bootloader, nothing else changes
4) Wotanserver or flashtool. I've used both multiple times on an unlocked bootloader.
Sent from my R800x using Tapatalk
Oh the wait is killing me. I feel like a kid waiting for Christmas to start!
netizenmt said:
Oh the wait is killing me. I feel like a kid waiting for Christmas to start!
Click to expand...
Click to collapse
Yupp, I completely understand the feeling
I'm gonna respond to your PM here, because it's general knowledge that should be for everybody
What you're gonna want to do is the following
1) Download this: http://www.mediafire.com/?bp6tlnv9r750rxr It's chevyowner's port of CM9
2) He does have a kernel included in his zip, but for some reason, my phone decided that it didn't like it so instead I used this one: http://forum.xda-developers.com/showthread.php?t=1541482
2) If you want the gamepad buttons mapped correctly, follow these instructions: http://forum.xda-developers.com/showpost.php?p=23507172&postcount=552
3) After you install the rom, but are still in Recovery, download this fine: http://www.mediafire.com/?su27w59c2qd25t1
Connect your phone, make sure /system is mounted, and enter adb shell, "mv /system/build.prop /system/build.prop.bak" exit and then "adb push C:\path\to\build.prop (or in you're in linux /path/to/build.prop) /system/"
4) Reboot, and enjoy!
Pax
How do you get one of these things unlocked? I see no option to pay.
And how fast does Alejandrissimo work at unlocking bootloaders?
paxChristos said:
Yupp, I completely understand the feeling
I'm gonna respond to your PM here, because it's general knowledge that should be for everybody
What you're gonna want to do is the following
1) Download this: http://www.mediafire.com/?bp6tlnv9r750rxr It's chevyowner's port of CM9
2) He does have a kernel included in his zip, but for some reason, my phone decided that it didn't like it so instead I used this one: http://forum.xda-developers.com/showthread.php?t=1541482
2) If you want the gamepad buttons mapped correctly, follow these instructions: http://forum.xda-developers.com/showpost.php?p=23507172&postcount=552
3) After you install the rom, but are still in Recovery, download this fine: http://www.mediafire.com/?su27w59c2qd25t1
Connect your phone, make sure /system is mounted, and enter adb shell, "mv /system/build.prop /system/build.prop.bak" exit and then "adb push C:\path\to\build.prop (or in you're in linux /path/to/build.prop) /system/"
4) Reboot, and enjoy!
Pax
Click to expand...
Click to collapse
Thanks, Pax. I've downloaded those now.... just waiting on Alejandrissimo to get on.
Mephikun said:
How do you get one of these things unlocked? I see no option to pay.
And how fast does Alejandrissimo work at unlocking bootloaders?
Click to expand...
Click to collapse
You go to the website http://unlock-bootloader.com/ and click on Unlock. There is a form you fill out with your contact info. Alejandrissimo will reply with an email and instructions. Payment is made through PayPal. My understanding is it only takes about 15 minutes or less once you get connected.
Well, I am unlocked - yay - but I cannot get fastboot to install a kernel. It's not seeing my device, even though the PC sees it other wise. <sighs> It's making me crazy!
netizenmt said:
Well, I am unlocked - yay - but I cannot get fastboot to install a kernel. It's not seeing my device, even though the PC sees it other wise. <sighs> It's making me crazy!
Click to expand...
Click to collapse
which of the following are you doing?
Code:
fastboot flash boot boot.img
or
Code:
fastboot -i 0x0fce flash boot boot.img
Do you have the fastboot drivers installed?
Pax
(hint: you wanna use the second one )
Starting over from scratch. I flashed the r800x ftf file so I'm starting fresh. Then I flashed the new kernel. When I powered up the phone, I see "SONY" instead of "Sony Ericsson" so I figure that's the new kernel. Then it goes blank and doesn't do anything else and I can't get into recovery. I'll keep working at it.
Oh yeah, almost forgot. Once I load that fastboot driver, when I connect the phone to my PC in normal mode it's prompting me for an Android driver and can't find one that matches.
Gee, this is fun ! Frustrating, but fun !
Yes, I see - it's the back button instead of the volume rocker now. That would explain my Recovery issue. On to the next step !!
netizenmt said:
Starting over from scratch. I flashed the r800x ftf file so I'm starting fresh. Then I flashed the new kernel. When I powered up the phone, I see "SONY" instead of "Sony Ericsson" so I figure that's the new kernel. Then it goes blank and doesn't do anything else and I can't get into recovery. I'll keep working at it.
Click to expand...
Click to collapse
(Yes, the new kernel is flashed.) Try spamming the back button/volume rocker when you first feel it vibrate turning on... sometimes my phone can be a little finicky, so I start spamming buttons right away (that should get you into recovery) and from there you can install Cm9
paxChristos said:
(Yes, the new kernel is flashed.) Try spamming the back button/volume rocker when you first feel it vibrate turning on... sometimes my phone can be a little finicky, so I start spamming buttons right away (that should get you into recovery) and from there you can install Cm9
Click to expand...
Click to collapse
Yeah, it was the Back button instead of the Volume Rocker that was getting me. I'm going to have to replace the build.prop from within CM9 though because once I put the fastboot driver in place, my PC now prompts me for an Android driver and doesn't like the ones that came with the phone.
Woot, CM9 booting! - Let's see how it goes. Back shortly!
Since you're using a pc, do this
1) adb pull /system/build.prop
2) download winmerge (http://winmerge.org/)
3) Open up both the downloaded build.prop and the pulled one in winmerge.
4) Use root explorer (or something similar) to add in the different lines
(Winmerge highlights where two files are different, making it extremely useful for this )
Pax
Can't do the adb pull now because of the PC wanting that Android driver
netizenmt said:
Can't do the adb pull now because of the PC wanting that Android driver
Click to expand...
Click to collapse
Goto the zergRush thread in my signature and use the drivers in that post, that should get adb working again.
Pax
paxChristos said:
Goto the zergRush thread in my signature and use the drivers in that post, that should get adb working again.
Pax
Click to expand...
Click to collapse
I don't see a link for drivers in particular. Is it part of the SDK maybe?
EDIT: NVM - I'm blind. I haven't been to bed since 6 PM Friday.
EDIT #2 - When I try to install that driver, it tells me there is nothing in that location for my hardware.
EDIT #3 - And now it's working just fine... I think my PC is as tired as I am about now, lol
THANKS FOR ALL YOUR HELP, PAX!!!
netizenmt said:
THANKS FOR ALL YOUR HELP, PAX!!!
Click to expand...
Click to collapse
No problem, its what I do
Welcome to freedom (and never having to worry about the next update breaking root )
Sent from my R800x using Tapatalk
So I tried using the wugfresh toolkit last nigh to root since from what I've read all the nexus devices use the same method to unlock the bootloader and such. This was likely a mistake. After figuring out I had to change the device to PtP I managed to get to the unlock bootloader screen on the device, at which point it became unresponsive. I turned it off completely, and at that point it wouldn't boot at all, it would just sit on the nexus logo forever. I also couldn't fastboot, holding down the power, volume up and volume down buttons seemed to do nothing. So I let it run down last night in hopes of starting on a fresh charge. Now the device doesn't seem to want to charge at all. I plugged it into both my computer and wall charger through the usual usb cable, and the screen isn't showing any indication of charging. All I saw was the notification light blinking in short bursts after initially plugging it in, and now not even that is happening.
Ideas?
Reboot to recovery and wipe dalvik, cache and system and reboot
Sent from my Nexus 7 using xda premium
Simer03 said:
Reboot to recovery and wipe dalvik, cache and system and reboot
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
If you wipe system, what exactly are you expecting to reboot into???
je
Simer03 said:
Reboot to recovery and wipe dalvik, cache and system and reboot
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Exactly....I can't reboot into recovery because I can't fastboot into anything. I'm not sure how this helps.
destructobob said:
Exactly....I can't reboot into recovery because I can't fastboot into anything. I'm not sure how this helps.
Click to expand...
Click to collapse
A few points.
First, this is why I highly discourage 'toolkits', especially on Nexus devices. There simply is no reason to use them and many reasons not. It is much wiser to learn how to do things manually, as it makes troubleshooting problems much easier and is less likely to cause a problem. For example, to unlock the bootloader, you could have issued a single command to accomplish it.
Second, as I don't use toolkits, I can't say exactly how the one you used works, but it most likely automates that 'fastboot oem unlock' command, which IS the same for both N7 versions. If so, it shouldn't have caused you any issues.
Third, assuming all you did was attempt to unlock the bootloader - and not flash any custom stuff, root the device, etc. - you should not be running into this issue. If you did try something else, that could certainly explain some of the problems you have. There is certainly a possibility that your device is defective. It it truly won't charge or function at all, I would highly recommend you return it for a new one. If it's dead, there should be no reason why they won't take it back.
Next time, I would recommend doing things the old fashioned way .
phonic said:
A few points.
First, this is why I highly discourage 'toolkits', especially on Nexus devices. There simply is no reason to use them and many reasons not. It is much wiser to learn how to do things manually, as it makes troubleshooting problems much easier and is less likely to cause a problem. For example, to unlock the bootloader, you could have issued a single command to accomplish it.
Second, as I don't use toolkits, I can't say exactly how the one you used works, but it most likely automates that 'fastboot oem unlock' command, which IS the same for both N7 versions. If so, it shouldn't have caused you any issues.
Third, assuming all you did was attempt to unlock the bootloader - and not flash any custom stuff, root the device, etc. - you should not be running into this issue. If you did try something else, that could certainly explain some of the problems you have. There is certainly a possibility that your device is defective. It it truly won't charge or function at all, I would highly recommend you return it for a new one. If it's dead, there should be no reason why they won't take it back.
Next time, I would recommend doing things the old fashioned way .
Click to expand...
Click to collapse
It turns on, it's on at the moment actually. It's been sitting at the nexus logo for about ten minutes. And I still can't load into fastboot, holding down those three buttons does nothing. I'm not even sure why the device froze at the unlock screen. I'm trying to start up the old fashioned way right now, following this link http://forum.xda-developers.com/showthread.php?t=2379618
I've managed to make my way to the platform tools folder in a command line, but running the reboot bootloader command there does nothing. It simply says device not found. I don't think my computer is even seeing the n7 properly so it can't reboot it. I don't think its defective, but I don't know where to begin to fix this using the old fashioned way either....
phonic said:
A few points.
First, this is why I highly discourage 'toolkits', especially on Nexus devices. There simply is no reason to use them and many reasons not. It is much wiser to learn how to do things manually, as it makes troubleshooting problems much easier and is less likely to cause a problem. For example, to unlock the bootloader, you could have issued a single command to accomplish it.
Second, as I don't use toolkits, I can't say exactly how the one you used works, but it most likely automates that 'fastboot oem unlock' command, which IS the same for both N7 versions. If so, it shouldn't have caused you any issues.
Third, assuming all you did was attempt to unlock the bootloader - and not flash any custom stuff, root the device, etc. - you should not be running into this issue. If you did try something else, that could certainly explain some of the problems you have. There is certainly a possibility that your device is defective. It it truly won't charge or function at all, I would highly recommend you return it for a new one. If it's dead, there should be no reason why they won't take it back.
Next time, I would recommend doing things the old fashioned way .
Click to expand...
Click to collapse
I second all that's been said here. While toolkits can seem attractive, it's really quite simple, and much safer to do it manually once your take an hour to learn your way around the Android-SDK (way easier than it sounds, I promise).
I like toolkits, seriously, but they hardly ever work. I usually have to drop to a shell prompt and run the commands manually anyway.
Sent from Nexus 7 XHD using XDA Premium HD
destructobob said:
It turns on, it's on at the moment actually. It's been sitting at the nexus logo for about ten minutes. And I still can't load into fastboot, holding down those three buttons does nothing. I'm not even sure why the device froze at the unlock screen. I'm trying to start up the old fashioned way right now, following this link http://forum.xda-developers.com/showthread.php?t=2379618
I've managed to make my way to the platform tools folder in a command line, but running the reboot bootloader command there does nothing. It simply says device not found. I don't think my computer is even seeing the n7 properly so it can't reboot it. I don't think its defective, but I don't know where to begin to fix this using the old fashioned way either....
Click to expand...
Click to collapse
To get into bootloader mode, you hold down POWER+VOLDOWN - not all three buttons. Make sure you turn off your device first (hold down power until it shuts off), then hold down those two buttons.
If it gets to the nexus logo, that means your bootloader should be OK, which means you can probably recover.
The 'adb reboot bootloader' command will not work until the device is booted up, your turned on developer mode and USB debugging, and you allowed your computer to connect.
Assuming you can get into bootloader, look to see if you did successfully unlock it or not. If you didn't, try the 'fastboot oem unlock' command.
If you continue to be unable to boot normally, you will likely need to flash the system image. There is one floating around here (system.img). You can do this in the bootloader as well (fastboot flash system system.img).
hadisious said:
I second all that's been said here. While toolkits can seem attractive, it's really quite simple, and much safer to do it manually once your take an hour to learn your way around the Android-SDK (way easier than it sounds, I promise).
Click to expand...
Click to collapse
I understand that and have absolutely learned my lesson. What's confusing me at the moment is installing the drivers listed in the link I posted. All that's there is a zip file, no exe or anything which is what I'm used to for installers. I was able to reboot my nexus 7 into bootloader before with the toolkit, so I know I had the drivers installed properly at some point. The toolkit installed a universal ADB set which I'm thinking should work. I don't know what to do to get the device into bootloader to follow the instructions.
phonic said:
To get into bootloader mode, you hold down POWER+VOLDOWN - not all three buttons. Make sure you turn off your device first (hold down power until it shuts off), then hold down those two buttons.
If it gets to the nexus logo, that means your bootloader should be OK, which means you can probably recover.
The 'adb reboot bootloader' command will not work until the device is booted up, your turned on developer mode and USB debugging, and you allowed your computer to connect.
Assuming you can get into bootloader, look to see if you did successfully unlock it or not. If you didn't, try the 'fastboot oem unlock' command.
If you continue to be unable to boot normally, you will likely need to flash the system image. There is one floating around here (system.img). You can do this in the bootloader as well (fastboot flash system system.img).
Click to expand...
Click to collapse
So I'm able to get into the bootloader, but its not responding to the command line entries. My computer brings a popup anytime the nexus tries to do a regular boot, where it just sits at the logo. The popup explains that the device is unrecognized. I've uninstalled any devices that resemble the nexus in device manager, and have tried repeatedly to update the driver manually by pointing it to the usb driver folder within the sdk. Doing that simply says windows is unable to locate the correct driver. So I think my device is where it needs to be, I just can't connect to it from the command line at the moment.
First of all, what made you try the toolkit(effective as it is) on the new Nexus...? Couldn't you just sit down for a day or two enjoying stock experience(abominative as it is)...?
alicarbovader said:
First of all, what made you try the toolkit(effective as it is) on the new Nexus...? Couldn't you just sit down for a day or two enjoying stock experience(abominative as it is)...?
Click to expand...
Click to collapse
Unlocking the bootloader will always result in your device getting wiped.
So it makes sense that you do this first, this way you don't need to setup your device twice.
It also has nothing to do with stock vs custom. I have an unlocked bootloader, custom recovery and am rooted. But my device is still completely stock as far as the OS goes. The only thing I might change in the future is a custom kernel, as I am usually fine with things 'stock' from a user perspective on Nexus.
phonic said:
Unlocking the bootloader will always result in your device getting wiped.
So it makes sense that you do this first, this way you don't need to setup your device twice.
It also has nothing to do with stock vs custom. I have an unlocked bootloader, custom recovery and am rooted. But my device is still completely stock as far as the OS goes. The only thing I might change in the future is a custom kernel, as I am usually fine with things 'stock' from a user perspective on Nexus.
Click to expand...
Click to collapse
Honestly I had completely forgot that the initial unlocking does the factory reset. I got caught up in booting up the device and installing a few apps to try it out, to the point that I completely blanked on the reset haha.
I tried a bunch of different roms and verions on my gnexus and old N7, jumping between CM and PA mostly, and I got used to just having a backup ready and not worrying about a data wipe. I've mostly stuck with PA because the pie controls are fantastic on both devices and I've come to get used to the added screen space. I'm perfectly fine with the stock experience outside of pie controls, but I do love customizing my device and the custom roms allow for so much freedom in that regard.
destructobob said:
I understand that and have absolutely learned my lesson. What's confusing me at the moment is installing the drivers listed in the link I posted. All that's there is a zip file, no exe or anything which is what I'm used to for installers. I was able to reboot my nexus 7 into bootloader before with the toolkit, so I know I had the drivers installed properly at some point. The toolkit installed a universal ADB set which I'm thinking should work. I don't know what to do to get the device into bootloader to follow the instructions.
Click to expand...
Click to collapse
Okay... so its a zip file.... go to device manager and it should show you some android driver or nexus 7 or something.... right-click on that and choose update drivers... choose manual method and select the folder hat you unzipped...
then use fastboot to flash factory image...
Q: is factory image for nexus 4 2013 available
??
shengovind said:
Okay... so its a zip file.... go to device manager and it should show you some android driver or nexus 7 or something.... right-click on that and choose update drivers... choose manual method and select the folder hat you unzipped...
then use fastboot to flash factory image...
Q: is factory image for nexus 4 2013 available
??
Click to expand...
Click to collapse
I actually got it successfully up and running, unlocked and rooted and everything. The screen and dual speakers alone justify the price for sure, and the speed difference is noticeable. Riptide 2 seems to run alot smoother on this than my old N7. I'm also aware that in general a clean install runs better than something that's been used for a while, so perhaps that's part of my percieved performance gains. In any case I'm more than happy with my purchase, and am looking forward to getting my chromecast tomorrow!
destructobob said:
I actually got it successfully up and running, unlocked and rooted and everything. The screen and dual speakers alone justify the price for sure, and the speed difference is noticeable. Riptide 2 seems to run alot smoother on this than my old N7. I'm also aware that in general a clean install runs better than something that's been used for a while, so perhaps that's part of my percieved performance gains. In any case I'm more than happy with my purchase, and am looking forward to getting my chromecast tomorrow!
Click to expand...
Click to collapse
:good::good::good:
phonic said:
Unlocking the bootloader will always result in your device getting wiped.
So it makes sense that you do this first, this way you don't need to setup your device twice.
It also has nothing to do with stock vs custom. I have an unlocked bootloader, custom recovery and am rooted. But my device is still completely stock as far as the OS goes. The only thing I might change in the future is a custom kernel, as I am usually fine with things 'stock' from a user perspective on Nexus.
Click to expand...
Click to collapse
Yes but you should've waited for a suitable toolkit.
alicarbovader said:
Yes but you should've waited for a suitable toolkit.
Click to expand...
Click to collapse
Why would I wait for a toolkit?
This is a Nexus device. You don't need a toolkit. All you need is two brain cells and a willingness to learn. You can unlock, flash custom recovery and root in a matter of minutes with nothing other than the Android SDK. Toolkits cause more problems than they solve.
phonic said:
Why would I wait for a toolkit?
This is a Nexus device. You don't need a toolkit. All you need is two brain cells and a willingness to learn. You can unlock, flash custom recovery and root in a matter of minutes with nothing other than the Android SDK. Toolkits cause more problems than they solve.
Click to expand...
Click to collapse
ok, not a toolkit.. I give you that, but was the stock experience too intimidating...?
personally, i'd nuked htc sense when i got thoroughly bored with its great buttery ui. i like the aosp experience, rooted or not.
and i didn't know that we don:t need toolkits fpr nexus devices, cuz i've never happened to own one.
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?
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.
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.