Database Users

My solution for bootloop in 3.1

I rooted the tablet and it updated fine. I then reboot it and it is now stuck in boot loop. It says bootloader version unknown when I press power and volume button. What do I do?
Update. I have been able to successfully make my tab bootloop three times and three times have brought it back to life. All three times it has been because of an app that I guess is not compatible with 3.1. Because of my low thread post count I can't provide links or post into the development forum but my method has worked all 3 times.
A little background. First time I hadn't changed recovery and it was a bit easier. Second and third times I had cwm recovery and it was harder because adb wasn't recognizing my tablet.
First you need to have adb installed into your computer. I installed the sdk and then added the adb option. I then went into this post in the development forum: Re: [Solution] HC 3.1 OTA Difficulties 13% + Stock ODIN. In that post you'll find the Odin application for your computer and the appropriate PDA file for your tab. The PDA file contains the stock recovery, bootloader, and rom.
Whether you have stock recovery or cwm the next instructions are the same.
1. Connect the tab to computer.
2. Holding power button and volume down button, get into screen where you can choose fastboot or download mode. Choose download mode.
3. Once in download mode, on your computer open the Odin application.
4. Where it says PDA file, click the browse option to look for the PDA file you downloaded. Open it and it will be listed in the PDA section. Also the box next to PDA will be checked. Don't change any other settings.
5. Now you can press the button to run Odin. Don't touch tablet until it's done.
6. Now you can try rebooting it but it will still bootloop. Difference now is that you can adb into it.
7. With tab connected, go into cmd mode on your computer and type: adb reboot recovery
8. The tablet should reboot into stock recovery. From there wipe data and cache.
9. Reboot tablet and it should work! The tablet will be reverted back to 3.0.1. Just run the update again and enjoy.
Couple of notes. I tried the fastboot method mentioned in some posts but it never worked for me. This method that I've done has been flawless for me. I do have I/O version so I'm not sure if it is different from retail version. I think bootloops occur because some apps are not ready, stable, or compatible with 3.1. Something in the bootloader and recovery has changed in 3.1, whether it is changed via the apps or the update itself I'm not sure. I do know that the problem apps work great in 3.0.1, never causing bootloops, thus my conclusions.

Same thing happened to me. Fastboot -w did the trick. It wipes the tablet though.

Thanks. It's weird. My tablet was rooted but I hadn't changed anything. I ended up connecting it to my pc, adb'd into recovery. I wiped cache and data and it eventually worked. Only thing was that it went back to 3.0.1. I then did the update again and now it's working flawlessly with 3.1
Sent from my PC36100 using XDA Premium App

Help needed Samsung galaxy tab 10.1 stuck in boot loop
Hi,
I faced a similar situation, I upgraded by Samsung Galaxy Tab 10.1 to HC 3.1 and it had been working fine .
Unfortunately I did not use it for the past 2 days, the battery drained out and after that I tried to recharge and start itup.
It goes in a boot loop .
And also display's Entering upload mode, cause undefined .
Is fastboot the only way to recover the system now .

saviressej said:
Thanks. It's weird. My tablet was rooted but I hadn't changed anything. I ended up connecting it to my pc, adb'd into recovery. I wiped cache and data and it eventually worked. Only thing was that it went back to 3.0.1. I then did the update again and now it's working flawlessly with 3.1
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
How did you ADB it while it was in a bootloop?..

I'm stuck with this same issue! Everything was fine, I was on version 3.1 and I had rebooted it several times. Then one time it just got stuck on a bootloop and I can't figure out how to fix it. This is the google i/o version and I haven't done anything to it other than update to version 3.1.
I've been googling for an hour or so, but I have no idea what i'm suppose to be looking for. =\

you can recover.
i have posted detailed instructions in the OTA thread on xda.

sramasub said:
Hi,
I faced a similar situation, I upgraded by Samsung Galaxy Tab 10.1 to HC 3.1 and it had been working fine .
Unfortunately I did not use it for the past 2 days, the battery drained out and after that I tried to recharge and start itup.
It goes in a boot loop .
And also display's Entering upload mode, cause undefined .
Is fastboot the only way to recover the system now .
Click to expand...
Click to collapse
+1, i have the same problem. drained battery, recharged, stuck in boot loop. also got the "entering upload mode; cause undefined" message too.

I experienced the "upload mode / boot loop" problem a couple days ago and wrestled with it for hours. I finally found a combination of things to do that would allow me to enter fastboot to fix the issue, see the following post:
http://forum.xda-developers.com/showpost.php?p=14832831&postcount=122
Some of the steps may not be required, but what I listed should get you into the bootloader without issue. Once inside, simply do a "fastboot -w" to fix the bootloop. Interestingly, after doing a fastboot wipe I am now able to enter the bootloader without all of the complicated gymnastics listed in my post above. It doesn't quite make sense to me, but it's certainly the case.

_avatar said:
I experienced the "upload mode / boot loop" problem a couple days ago and wrestled with it for hours. I finally found a combination of things to do that would allow me to enter fastboot to fix the issue, see the following post:
http://forum.xda-developers.com/showpost.php?p=14832831&postcount=122
Some of the steps may not be required, but what I listed should get you into the bootloader without issue. Once inside, simply do a "fastboot -w" to fix the bootloop. Interestingly, after doing a fastboot wipe I am now able to enter the bootloader without all of the complicated gymnastics listed in my post above. It doesn't quite make sense to me, but it's certainly the case.
Click to expand...
Click to collapse
Yeah, I found your post a couple days ago, but couldn't get it to work. Once plugged into the wall charger, I couldn't get the charging icon to show up. I've tapped the power button, held it down for half a second, a full second, several seconds... it either does nothing, or tries to boot up.
I was able to get into Odin3 download mode and flash a ROM (see this thread: http://forum.xda-developers.com/showthread.php?t=1130216#2), but now my USB doesn't work and adb won't recognize it, so as a development device it's not very useful to me. I can't seem to get into the bootloader so I can't flash with adb or fastboot (when I boot into USB mode, adb doesn't recognize the device). I need to figure out how to flash an original I/O image, but can't seem to figure it out...

I've also had some difficulty getting to the "charging" screen, the trick is to be patient. Make sure the device is really off, plug it in, and walk away for a good while -- like 5 minutes.
When you say you're able to get it into USB mode what does that mean? Sounds like you are actually able to get it into fastboot mode. What operating system are you running? On my Mac the fastboot binaries I found floating around the net didn't work, I had to compile one from source. If you're able to get into fastboot mode but it's not detecting your device, and you have a Mac, I can send you the version I compiled from AOSP and you can try that. Let me know...

Try this...
http://forum.xda-developers.com/showthread.php?p=14791689#post14791689
Works for this guys.

I have a solution for the bootloop in my first post.
Sent from my GT-P7510 using XDA Premium App

I had a similar problem. Looks like Clockwork recovery can sometimes trash your /data partition and its format/wipe option won't fix it. I recovered by booting into stock recovery and formatting /data from there. Be forewarned that you'll lose your "sdcard," which really lives on /data.

Nice guide, thanks!

Nexus 4 Boots Only in recovery

Hi,
Please help out
Was using your Nexus 4 rootkit.. Everthing was done and phone was rooted .
Now i wanted to update the CWM. I chose the option 11 boot or flash .img files to device. I chose the cwm mako version
and decide to flash it.
Now i am asked options such as boot, bootloader, radio etc.
Here I choose Boot..(This I think I have done wrong.)
Now. Phone only boots to recovery... No matter I with on , Off I cannot go anywhere.. I go directly to CWM.
I tried your toolkit again and this said Phone needs to go in adb .. It says waiting for device..
I cannot also mount the SD card so that i can put some images in the phone...
Hence I cannot do anyhting
Plz help.
Regards

Reflash a rom
Wipe first tho

mark manning said:
Reflash a rom
Wipe first tho
Click to expand...
Click to collapse
How can i flash a rom,When the fact is that i am not able to mount sd card via recovery.
if the nexus had external SD card things would have been easier. I could have just used my SC card reader..

XX-RAZOR-XX said:
How can i flash a rom,When the fact is that i am not able to mount sd card via recovery.
if the nexus had external SD card things would have been easier. I could have just used my SC card reader..
Click to expand...
Click to collapse
Do you not already have one downloaded to the phone?
Sent from my Nexus⁴

mark manning said:
Do you not already have one downloaded to the phone?
Sent from my Nexus⁴
Click to expand...
Click to collapse
No.. I dont have an image on the phone..

XX-RAZOR-XX said:
No.. I dont have an image on the phone..
Click to expand...
Click to collapse
You are going to have to flash the stock image with fastboot. There is a good guide to do so here. Just an FYI this is why you should stay away from toolkits
http://forum.xda-developers.com/showthread.php?t=2010312
Let me know if you can't find the stock image and I'll help you out
Sent from my Nexus⁴

mark manning said:
You are going to have to flash the stock image with fastboot. There is a good guide to do so here. Just an FYI this is why you should stay away from toolkits
http://forum.xda-developers.com/showthread.php?t=2010312
Let me know if you can't find the stock image and I'll help you out
Sent from my Nexus⁴
Click to expand...
Click to collapse
I have a stock image. occam-jop40d
but I cannot go into the bootloader. Pressing that volume keys + power .. The nexus goes out and the red light appears. its not flikering.

XX-RAZOR-XX said:
I have a stock image. occam-jop40d
but I cannot go into the bootloader. Pressing that volume keys + power .. The nexus goes out and the red light appears. its not flikering.
Click to expand...
Click to collapse
I don't know man. With what you have said there is no reason you shouldn't be able to get into your bootloader. If you can't you might be screwed. I flagged your thread in the RC forum. Hopefully some of them will stop by with some other ideas.
Sent from my Nexus⁴

mark manning said:
I don't know man. With what you have said there is no reason you shouldn't be able to get into your bootloader. If you can't you might be screwed. I flagged your thread in the RC forum. Hopefully some of them will stop by with some other ideas.
Sent from my Nexus⁴
Click to expand...
Click to collapse
I am now trying the ADB commads.. in the thread you provided. Lets hope something good comes out..
Till then anyone else can help , will be appreciated.

Can you do
Fastboot flash recovery (name).img
Then fastboot flash boot (boot).img
And then access recovery? If you are in recovery img pretty sure you can use adb. Just a suggestion.
Whatever is in your boot partition (recovery in your case) will be booted when you turn the phone on. This is why you see recovery.
Edit: you cant get into bootloader *at all?* no fastboot then?
Sent with from my Asus Nexus Unicorn

Hi RAZOR, I read your story and it looks like it's not ALL big problems there. I'm willing to help you with that, if you want send me a PM and we talk with GTalk (give you it there), but let's see...
I would plug my cellphone on the PC (hope it works like my Xoom, as they are very similar in some points - Xoom is GED, N4 is Nexus...)
(You said it is booting on recovery), now I would use adb to continue easily...
If you are on Windows:
1 - Open a cmd
2 - cd to adb place
3 - now type adb reboot bootloader, then it would go to fast boot
Now you flash the images you downloaded
On Linux
1 - Open Terminal
2 - Download LAIOT (my tool on signature ) (only to get adb and fast boot ready for use)
3 - Now open terminal and type adb reboot bootloader, then flash the images you downloaded with fastboot
If nothing this work, send me a PM and we'll talk
"This Story Ends Where It Began"

markj338 said:
Can you do
Fastboot flash recovery (name).img
Then fastboot flash boot (boot).img
And then access recovery? If you are in recovery img pretty sure you can use adb. Just a suggestion.
Whatever is in your boot partition (recovery in your case) will be booted when you turn the phone on. This is why you see recovery.
Edit: you cant get into bootloader *at all?* no fastboot then?
Sent with from my Asus Nexus Unicorn
Click to expand...
Click to collapse
Thanks for reply.the first challenge here is actually start the phone. i am not able to start. Read somewhere battery might be depleted. hooked a chafer. its 1 hr but still no start

XxLordxX said:
Hi RAZOR, I read your story and it looks like it's not ALL big problems there. I'm willing to help you with that, if you want send me a PM and we talk with GTalk (give you it there), but let's see...
I would plug my cellphone on the PC (hope it works like my Xoom, as they are very similar in some points - Xoom is GED, N4 is Nexus...)
(You said it is booting on recovery), now I would use adb to continue easily...
If you are on Windows:
1 - Open a cmd
2 - cd to adb place
3 - now type adb reboot bootloader, then it would go to fast boot
Now you flash the images you downloaded
On Linux
1 - Open Terminal
2 - Download LAIOT (my tool on signature ) (only to get adb and fast boot ready for use)
3 - Now open terminal and type adb reboot bootloader, then flash the images you downloaded with fastboot
If nothing this work, send me a PM and we'll talk
"This Story Ends Where It Began"
Click to expand...
Click to collapse
hi ..thanks.. will surely let you know

Not able to start..
Red light comes for a split second and then goes..
Phone is cool even after 3 hrs .. Not to forget.. It cannot even start

XX-RAZOR-XX said:
Not able to start..
Red light comes for a split second and then goes..
Phone is cool even after 3 hrs .. Not to forget.. It cannot even start
Click to expand...
Click to collapse
Not going to lie it is starting to sound pretty grim for you. Keep us informed as to what happens please
Sent from my Nexus⁴

I had a field day this morning with my phone also when trying to flash the stock image back. Finally got it working. The only similarity we had is that I could not mount my data or sdcard either after flashing the stock image.
However, I WAS able to get into fastboot. Should you be able to get into fastboot then RE-LOCK and UN-LOCK your bootloader and everything should work again (fixed my data and sdcard mount issue). I was then able to boot into Android and carry on.
Fastboot oem lock
fastboot oem unluck
Or use the Toolkit.
My only other suggestion would be to take off the back case and try pull the battery (haven't seen it done and not even 100% sure it can be). Maybe the battery just needs a time-out from the phone.
Hope that's some useful information for you.
Good luck.

Well hooking in charger for 6+ hours.. nothing worked...
I think it got screwed

XX-RAZOR-XX said:
Well hooking in charger for 6+ hours.. nothing worked...
I think it got screwed
Click to expand...
Click to collapse
This all still sounds very strange. Wish we could help you get it working but it doesn't look like any of the suggestions have helped. To bad you don't live in the same area as me I'd offer to try and help more.
If you're within the 15 day period perhaps Google can RMA the phone...

asawoszc said:
This all still sounds very strange. Wish we could help you get it working but it doesn't look like any of the suggestions have helped. To bad you don't live in the same area as me I'd offer to try and help more.
If you're within the 15 day period perhaps Google can RMA the phone...
Click to expand...
Click to collapse
And also , adding to this..
I live in India( was shipped here via mail forward sites).. . and 15 days grace is almost over.. (2 days).. even sending it to google from india will take at least 10 days

Try This
Originally Posted by faux123
I got into many red LED situations, I was able to come out of it everytime by using the procedure I posted above (that post was from pure experience I had).
red led bootloop unbrick procedure
1. plug phone into USB cable connected to computer
2. wait for it to go into charge animation
3. unplug, then press power button to boot, immediately press vol up + vol down.
4. hopefully you booted into bootloader mode (rinse and repeat steps 1~4 if you can't get to this point)
5. chose recovery (if your recovery is corrupted, repeat steps 1~4 and do fastboot flash recovery cwmxxx.img)
6. from recovery choose restart system
if you can't get to step 2, because N4 has a bug with battery capacity, plug your phone into AC charge and let it charge for a few mins. then restart from step 1...
Click to expand...
Click to collapse

Nexus 10 stuck in boot loop.. please help!!!

So, I was using Zedomax's how to root N10 tutorial (http://www.youtube.com/watch?feature=player_embedded&v=wVlI-gWppCA#at=261)... I had everything working fine up until about 4:15 in the video when his restarts mine just gets stuck in boot loop and displays the nexus bootloader for an unlimited amount of time. My device does however show that it is unlocked because when I go back through the process it says it is already unlocked as you can see in the pictures. the first is the cmd I used and the second is what the N10 shows after "fastboot oem unlock"... I am completely lost and have tried over and over to find the problem... I have tried to unroot and restore but I cant even find a working file that isnt malicious... ANY AND ALL HELP OR SUGGESTIONS WOULD BE APPRECIATED...

Andrololol said:
So, I was using Zedomax's how to root N10 tutorial (http://www.youtube.com/watch?feature=player_embedded&v=wVlI-gWppCA#at=261)... I had everything working fine up until about 4:15 in the video when his restarts mine just gets stuck in boot loop and displays the nexus bootloader for an unlimited amount of time. My device does however show that it is unlocked because when I go back through the process it says it is already unlocked as you can see in the pictures. the first is the cmd I used and the second is what the N10 shows after "fastboot oem unlock"... I am completely lost and have tried over and over to find the problem... I have tried to unroot and restore but I cant even find a working file that isnt malicious... ANY AND ALL HELP OR SUGGESTIONS WOULD BE APPRECIATED...
Click to expand...
Click to collapse
I can help you get back to stock, that should fix everything. You will erase everything and have to start whatever you were working on again. So back it up before hand if you can.
So first you need to be sure you have TODAYS latest updates to the fastboot.exe program, do this by installing the SDK from Google, then launching the update manager and doing all updates. See this post:
http://forum.xda-developers.com/showpost.php?p=38961605&postcount=5
Then you need to do what styckx says. Be sure to click 'Thanks' under his posts. The only thing that you may find is hard to understand is, if you download that from Google and it end up as .tar you have to rename it to .tgz to have it extract correclty. See this post:
http://forum.xda-developers.com/showpost.php?p=38091931&postcount=210
EDIT - If you did oem unlock and were stuck at the X bootlogo then there is an easier fix than what I describe. You state you are stuck at bootloader. Just FYI
Good luck!

bigmatty said:
I can help you get back to stock, that should fix everything. You will erase everything and have to start whatever you were working on again. So back it up before hand if you can.
So first you need to be sure you have TODAYS latest updates to the fastboot.exe program, do this by installing the SDK from Google, then launching the update manager and doing all updates. See this post:
http://forum.xda-developers.com/showpost.php?p=38961605&postcount=5
Then you need to do what styckx says. Be sure to click 'Thanks' under his posts. The only thing that you may find is hard to understand is, if you download that from Google and it end up as .tar you have to rename it to .tgz to have it extract correclty. See this post:
http://forum.xda-developers.com/showpost.php?p=38091931&postcount=210
EDIT - If you did oem unlock and were stuck at the X bootlogo then there is an easier fix than what I describe. You state you are stuck at bootloader. Just FYI
Good luck!
Click to expand...
Click to collapse
yes, it is stuck at nexus symbol "X" loading screen.. you say there is an easier fix for that?

Andrololol said:
yes, it is stuck at nexus symbol "X" loading screen.. you say there is an easier fix for that?
Click to expand...
Click to collapse
yes. that is common w/ these after oem unlock. on that fastboot screen you posted, the one you get to by holding the certain key sequence at boot - use the volume keys to select Recovery, then use the start button to boot to that mode. This confuses people because at that point it looks broken - all you see is a triangle with an error X in it (or something like that.) BUT from that screen you access another menu, do this by briefly pressing power volume up and volume down in little spurts. it sounds wierd, but you do that for up to 20 seconds and you'll finally get it. its just hard to enter so you have to do it like that otherwise you go crazy trying. once you've accessed that menu you will know because its all text. using the navigation choose 'factory wipe' and wipe it. after that your N10 will boot like normal. be aware - navigation on that text only menu is tricky.

[Q] Stock Nexus 4 bad install of 4.3 OTA

Hello, I tried searching for this but came up empty. I have a completely stock Nexus 4, received the OTA push for 4.3. Phone has never been rooted. After going through the install process it showed the android on it's back with a red triangle and said error. After a restart the phone just sits at the Google screen!!! I'm I boned or is there a fix for this? Any info would be greatly appreciated! Thank you!

Jesmuris said:
Hello, I tried searching for this but came up empty. I have a completely stock Nexus 4, received the OTA push for 4.3. Phone has never been rooted. After going through the install process it showed the android on it's back with a red triangle and said error. After a restart the phone just sits at the Google screen!!! I'm I boned or is there a fix for this? Any info would be greatly appreciated! Thank you!
Click to expand...
Click to collapse
Try going into fastboot and flashing the stock rom from google.

gmaxpwnage said:
Try going into fastboot and flashing the stock rom from google.
Click to expand...
Click to collapse
Not sure what mode I entered, Held vlm down + power. Says Fastboot Mode in red with a big green Start at the top. Options it gives me is Start, restart bootloader, recovery mode, and power off. If I try to enter Recovery mode it says no command. Don't see anything that allows me to reinstall

Jesmuris said:
Not sure what mode I entered, Held vlm down + power. Says Fastboot Mode in red with a big green Start at the top. Options it gives me is Start, restart bootloader, recovery mode, and power off. If I try to enter Recovery mode it says no command. Don't see anything that allows me to reinstall
Click to expand...
Click to collapse
Ok, found out on the no command screen I can hold power and hit vlm up and it brings me to system recovery with these options. Reboot system, apply update from ADB, wipe data/factory reset, wipe cache partition.
Not sure what to do sadly

Try following step:
1. Press Vol up and down and powerbutton same time to get to the fastboot mode as you mention.
2. Choice Recovery Mode and press power button. If you got luck you will see an android guy with red mark on the screen.
3. Press Vol Up and Power button same time for while don't let go it will pop up a list of option clean the cache and do factory reset, then reboot system.
If this method not working. Then hard method is flash your Nexus 4 with fastboot. Search the forum there few people already post how to flash 4.3 ROM with fastboot

Johnsonyc said:
Try following step:
1. Press Vol up and down and powerbutton same time to get to the fastboot mode as you mention.
2. Choice Recovery Mode and press power button. If you got luck you will see an android guy with red mark on the screen.
3. Press Vol Up and Power button same time for while don't let go it will pop up a list of option clean the cache and do factory reset, then reboot system.
If this method not working. Then hard method is flash your Nexus 4 with fastboot. Search the forum there few people already post how to flash 4.3 ROM with fastboot
Click to expand...
Click to collapse
Ok thank you, trying this now will update:good:

Didn't work Will try other method

Jesmuris said:
Didn't work Will try other method
Click to expand...
Click to collapse
Sorry to hear this bad news Hope the other method work for you!

Well, first try, couldn't get my PC to recognize fastboot in adb. Was getting frustrated beyond hell and had to walk away for a bit. Came back about an hour later and for some reason it finally recognized it... Back to the start screen like when I first bought the phone. So far working ok, except for being able to log into my google account... 2-step verification giving me issues now lol. Thank you again for your assistance. Very much appreciated!!:good::good:

Jesmuris said:
Well, first try, couldn't get my PC to recognize fastboot in adb. Was getting frustrated beyond hell and had to walk away for a bit. Came back about an hour later and for some reason it finally recognized it... Back to the start screen like when I first bought the phone. So far working ok, except for being able to log into my google account... 2-step verification giving me issues now lol. Thank you again for your assistance. Very much appreciated!!:good::good:
Click to expand...
Click to collapse
I had a similar experience (kind of). I had issues side-loading 4.2.2 -> 4.3 on my N4. After it finished update and rebooted I got a black screen and nothing more. I ran through it and tried to update to 4.3 again, and then it worked.
Even though it worked I've been noticing issues with it. For example, I now can no longer uninstall anything. When I attempt to uninstall any app, the phone reboots. I'm backing up now with Titanium and am about to flash. I was hoping there would be a quick fix here, but such is life. Viva la impatience.

I have same problem my stock 4.2.2 stuck x boot load , did vol up+dwn +power now stuck in "Download Mode" do not unplug the device until the process is complete .

oneguy77 said:
I have same problem my stock 4.2.2 stuck x boot load , did vol up+dwn +power now stuck in "Download Mode" do not unplug the device until the process is complete .
Click to expand...
Click to collapse
This is what I eventually followed to get mine working. I just did scenario 2 and that worked perfectly for me, so far no issues, just having to get things back to where I had them before. The second link is actually more detailed. Just make sure you follow step by step. I guess i could have not done step D10 but wanted to make sure this route worked for me. Thank you again for those who pointed me in the right direction
http://www.androidpolice.com/2013/0...-to-android-4-3-jwr66v-and-root-it-right-now/
http://forum.xda-developers.com/showpost.php?p=34552123&postcount=1

Jesmuris said:
Well, first try, couldn't get my PC to recognize fastboot in adb. Was getting frustrated beyond hell and had to walk away for a bit. Came back about an hour later and for some reason it finally recognized it... Back to the start screen like when I first bought the phone. So far working ok, except for being able to log into my google account... 2-step verification giving me issues now lol. Thank you again for your assistance. Very much appreciated!!:good::good:
Click to expand...
Click to collapse
I have the exact same problem but not sure how to get my PC to recognize fastboot in adb mode...

FYI if you flash to stock android 4.3 and you have the 16 GB Nexus 4, make sure that after you re-flash you have the full 16 GB and not 8 GB (unless you want to re-setup your phone twice like me). If you get this problem you can wipe cache and data from recovery and voila, all of your free space is back.
---------- Post added at 10:52 PM ---------- Previous post was at 10:44 PM ----------
zpilot said:
I have the exact same problem but not sure how to get my PC to recognize fastboot in adb mode...
Click to expand...
Click to collapse
If this is what I think it is, I was having the same problem. If I went into Control Panel on my PC and it would say that the driver is failing to load. To fix this I uninstalled the driver, rebooted, reinstalled Google USB Driver from the Android SDK Manager, restarted, and all was well after that.
I really have no explanation for why this fixed it, or it didn't work before, because other than fastboot, everything was working flawlessly with getting my phone to communicate with my PC.

just bought 'open box' Nexus 10 - Bricked?

HI all,
I have just bought an open box nexus 10 which means its new but has been opened and apparently been tested to be working. the company i bought it off say they tested it working before sending it out to me..
I got it today and started it, it loaded fine then asked for me google details and wifi..
Once done it loaded fine and i was on the home screen, it then rebooted itself and then since then it has not been able to reboot, it says the white google then some colours start to come in from the sides and it reboots again..
I have tried to go into recovery and factory reset both cache and data but that didnt work..
I am just trying the nexus toolkit now but i have no idea of which version of android it is actually running right now or have any idea if USB debugging is activated but i assume it isnt as i have not had a chance to do it..
Any help would be greatly appreciated, i dont really want to return it as it is from a friends company and i got it at cost price and he has no stock left!

device information
Prod Name - Manta
H/W - 8
bootloader - MANTAMF01
Carrier info - none
Lock state - locked
Roboot mode flag - None
if any of that helps?

device information
Prod Name - Manta
H/W - 8
bootloader - MANTAMF01
Carrier info - none
Lock state - locked
Roboot mode flag - None
if any of that helps?

Do the colors make 4 circles and twirl around in a circle? If so your on KitKat. If it names an x shape your on jelly bean. Just use the toolkit select the version your on. I'm guessing your on 4.4 or 4.4.2 KitKat. Then select flash back to stock or whatever the option is. IRS all the way on the right.
Sent from my white Nexus 5 using xda-developers app.
Please press the thanks button if I help you.

I have managed to go through one full cycle of trying to flash the 4.4.2 from the toolkit but it says failed remote - locked use fastboot oem unlock. then after that it simply says booting up your freshly flashed device...
But if i try to reboot it does the same thing, problem i am having is that the bootloop doesnt even allow the colours to merge from the sides it reboots even before they meet in the middle of the screen??
ANy idea what to do now?
ps thanks for the reply!

talboy said:
I have managed to go through one full cycle of trying to flash the 4.4.2 from the toolkit but it says failed remote - locked use fastboot oem unlock. then after that it simply says booting up your freshly flashed device...
But if i try to reboot it does the same thing, problem i am having is that the bootloop doesnt even allow the colours to merge from the sides it reboots even before they meet in the middle of the screen??
ANy idea what to do now?
ps thanks for the reply!
Click to expand...
Click to collapse
OK. Open up the folder with the downloaded factory image from the toolkit. You'll find it under data/factory images I think in the toolkit files. Extract it. Are you familiar with adb? Because you'll need it. Copy the system, userdata, boot, and recovery images that we just extracted and paste them in the data folder. From there (I'm assuming you use windows) open a command window by holding shift and right clicking and you'll see the option. After that type "fastboot devices" then enter without the quotations and you should see you're device listed. (It needs to be connected in fast boot mode via USB cable). From there you need to use the commands "fastboot flash system system.img" repeat this with the boot, recovery, and userdata. But replace the system and system.img with the appropriate word fur example "fastboot flash boot boot.img" without quotes. That is a manual way of resetting. it should fix any soft ware issues. If that Durant work it might be a hard ware problem b and you might need to return it but in pretty sure it should.
Good luck and of you need any help or explanations just ask.
Sent from my white Nexus 5 using xda-developers app.
Please press the thanks button if I help you.

abdel12345 said:
OK. Open up the folder with the downloaded factory image from the toolkit. You'll find it under data/factory images I think in the toolkit files. Extract it. Are you familiar with adb? Because you'll need it. Copy the system, userdata, boot, and recovery images that we just extracted and paste them in the data folder. From there (I'm assuming you use windows) open a command window by holding shift and right clicking and you'll see the option. After that type "fastboot devices" then enter without the quotations and you should see you're device listed. (It needs to be connected in fast boot mode via USB cable). From there you need to use the commands "fastboot flash system system.img" repeat this with the boot, recovery, and userdata. But replace the system and system.img with the appropriate word fur example "fastboot flash boot boot.img" without quotes. That is a manual way of resetting. it should fix any soft ware issues. If that Durant work it might be a hard ware problem b and you might need to return it but in pretty sure it should.
Good luck and of you need any help or explanations just ask.
Sent from my white Nexus 5 using xda-developers app.
Please press the thanks button if I help you.
Click to expand...
Click to collapse
Massive thanks for this explanation..
I am not sure what ADB is? do i need to have any specific software or do i simply follow the instructios that you have given?

Just follow the instructions. Normally you'd need to download a package but that comes with the wug tool kit so your all ready to go.
Also If you want to unlock the bootloader beforehand type in "fastboot oem unlock" it'll make it easier if you ever want to flash a custom rom or recovery later because it wipes all your days and since you have no data you might as well do it now. But if your not interested in ROM then don't bother.
Also please press thee thanks Button if it helps. Thanks
Sent from my white Nexus 5 using xda-developers app.
Please press the thanks button if I help you.

abdel12345 said:
Just follow the instructions. Normally you'd need to download a package but that comes with the wug tool kit so your all ready to go.
Also If you want to unlock the bootloader beforehand type in "fastboot oem unlock" it'll make it easier if you ever want to flash a custom rom or recovery later because it wipes all your days and since you have no data you might as well do it now. But if your not interested in ROM then don't bother.
Also please press thee thanks Button if it helps. Thanks
Sent from my white Nexus 5 using xda-developers app.
Please press the thanks button if I help you.
Click to expand...
Click to collapse
ok so i am stuck right at the start, im sorry! So to open the command prompt i hold shift and right click, there is no option for command prompt? Should i just open CMD as normal?

talboy said:
ok so i am stuck right at the start, im sorry! So to open the command prompt i hold shift and right click, there is no option for command prompt? Should i just open CMD as normal?
Click to expand...
Click to collapse
You need to be in the folder. Open the folder then hold shift then open it. Is that what you did?
Sent from my white Nexus 5 using xda-developers app.
Please press the thanks button if I help you.

abdel12345 said:
You need to be in the folder. Open the folder then hold shift then open it. Is that what you did?
Sent from my white Nexus 5 using xda-developers app.
Please press the thanks button if I help you.
Click to expand...
Click to collapse
Sorry i got it, right click when in the data folder.. command open with the wugfresh development

just going through the process now as i type.. first one failed saying invalid partition but then said about flashboot oem unlock so i have done that first and it now seems to be allowing the system.img to be flashed..
fingers crossed it works!

ok flashed all of the .img resterted it and now it just says google on the screen with an unlocked padlock at the bottom, been like that for 30 secs so far, seems to have done somehting as previously it was just going into the animation and restarting..
Should i be doing a factory reset?

talboy said:
ok flashed all of the .img resterted it and now it just says google on the screen with an unlocked padlock at the bottom, been like that for 30 secs so far, seems to have done somehting as previously it was just going into the animation and restarting..
Should i be doing a factory reset?
Click to expand...
Click to collapse
If it shows the Google image then there's a kernel so the boot image was successful but if it doesn't go past it means you have no ROM so the system flash must have failed. Terry flashing system again. Sorry for the late response
Sent from my white Nexus 5 using xda-developers app.
Please press the thanks button if I help you.

no problem thanks for the help so far!! just reflashed system this time it it is coming up with the google sign and unlocked pad and its doing the same as before now...
its just starting the animation for a milisec then rebooting...
any idea?

talboy said:
no problem thanks for the help so far!! just reflashed system this time it it is coming up with the google sign and unlocked pad and its doing the same as before now...
its just starting the animation for a milisec then rebooting...
any idea?
Click to expand...
Click to collapse
I'm not sure why it isn't working
Well now that your boot loader is unlocked you can try the toolkit again and see of it works. Use the option that says factory reset or unbrick or whatever it says and choose stuck in bootloop. Then follow the instructions if that v doesn't work is recommend locking the bootloader using "fastboot oem lock" and trying to return it.
Or you could wait a little and see if someo else has ideas. Try the toolkit again first though
Sent from my white Nexus 5 using xda-developers app.
Please press the thanks button if I help you.

thanks man you have been super helpful an di appreciate it a lot, hopefully it starts to work if not at least we gave it a chance.
Ill try the toolkit again and see if that does anything if not then back it goes!

retried the toolkit same thing, no joy still doesnt work...
thanks for the help..
does anyone else have any ideas? if not back it goes tomorrow

talboy said:
retried the toolkit same thing, no joy still doesnt work...
thanks for the help..
does anyone else have any ideas? if not back it goes tomorrow
Click to expand...
Click to collapse
Make sure if you return it to do the lock bootloader command first.
Sent from my white Nexus 5 using xda-developers app.
Please press the thanks button if I help you.