just bought 'open box' Nexus 10 - Bricked? - Nexus 10 Q&A, Help & Troubleshooting

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.

Related

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.

Stuck on google logo

Hey guys
i just wiped all my data and tried to reboot my nexus, but now it's been stuck on the google logo for ages...
trying to flash to stock + unroot with nexus toolkit doesn't work, any way to unbrick it?
please help...
do you have fastboot driver installed?
Step 1: Power down your Nexus 4 (hold the power button until it shuts off) before rebooting into fastboot mode. You can do this by holding down the the Volume Down and Power buttons simultaneously.
Step 2: Connect your device to your computer. Open up a terminal or command prompt, and navigate to the folder containing the fastboot program.
Step 3: Type fastboot devices into the command line, and you should then see your device’s ID, which means fastboot is setup correctly.
now go back to Nexus 4 toolkit. Flash back to stock.
badboy47 said:
do you have fastboot driver installed?
Step 1: Power down your Nexus 4 (hold the power button until it shuts off) before rebooting into fastboot mode. You can do this by holding down the the Volume Down and Power buttons simultaneously.
Step 2: Connect your device to your computer. Open up a terminal or command prompt, and navigate to the folder containing the fastboot program.
Step 3: Type fastboot devices into the command line, and you should then see your device’s ID, which means fastboot is setup correctly.
now go back to Nexus 4 toolkit. Flash back to stock.
Click to expand...
Click to collapse
works
thank you very much
fabian.m said:
works
thank you very much
Click to expand...
Click to collapse
Then, press on his THANKS button. That's the way we have to measure who contributes or not in xda-developers. Please, let's follow rules...
luiseteyo said:
Then, press on his THANKS button. That's the way we have to measure who contributes or not in xda-developers. Please, let's follow rules...
Click to expand...
Click to collapse
well.. technically thanking isn't in the rules.
exb0 said:
well.. technically thanking isn't in the rules.
Click to expand...
Click to collapse
It is in the good behaviour and politeness rules. Not everything is written.
Hi guys i got a similar problem, i flashed a walkman .zip wiped cache and dalvik cache. Then the phone booted into google logo, and it went all black. The display is on but its all black. The problem is i cannot power off the device. Holding all buttons just restarts the phone. What can i do?
I was on latest PA rom
Qbsti said:
Hi guys i got a similar problem, i flashed a walkman .zip wiped cache and dalvik cache. Then the phone booted into google logo, and it went all black. The display is on but its all black. The problem is i cannot power off the device. Holding all buttons just restarts the phone. What can i do?
I was on latest PA rom
Click to expand...
Click to collapse
reflash your rom. reboot your device, hold volune down before it reboots to get into the bootloader then recovery.
simms22 said:
reflash your rom. reboot your device, hold volune down before it reboots to get into the bootloader then recovery.
Click to expand...
Click to collapse
Thanks simms, i managed to get into fast boot between the reboots, and I flashed the rom and gapps.
Damn it scared me even more then the red light issue that happened to me last month.
Qbsti said:
Thanks simms, i managed to get into fast boot between the reboots, and I flashed the rom and gapps.
Damn it scared me even more then the red light issue that happened to me last month.
Click to expand...
Click to collapse
not booting after flashing something or modding something is the easiest of all to fix, just reflash the rom(gapps and kernel too if need be), no need to wipe anything. since i test all the trinity kernels before any get released, and pre-kernels, i get many that dont boot my device or bootloop(among some other funky behaviors), reflashing a good kernel always works
I left my phone for a few minutes, and when I picked it up it was bootlooped again, and i had to use fastboot again. What should I do now? Maybe a factory reset would help me. I don't want more unexpected bootloops. :/
swyped from my nexus 4
Qbsti said:
I left my phone for a few minutes, and when I picked it up it was bootlooped again, and i had to use fastboot again. What should I do now? Maybe a factory reset would help me. I don't want more unexpected bootloops. :/
swyped from my nexus 4
Click to expand...
Click to collapse
Try another rom. You might have downloaded corrupted zips. Also, make sure you flash the things you need first. Eg, flash rom and gapps. Don't restore anything if you're using titanium backup. Try restarting the phone, see if it gets into a bootloop. If it doesn't, then try restoring apps from TB. (if you use TB.)
Hi!
I´ve got a big problem. Today i flashed the new PA version, but it seems that the download had some issue. I could install it but after a while, I wanted to reboot the phone and it got stuck at the Google logo. I can only access fastboot mode and recovery.
So the problem is, i made a full wipe, so i have no rom on the sdcard anymore. Also I am now able to enable the debbuging mode. I tried every toolkit i couzld find, but everyone needs debugging mode enabled. windows doesnt recognize the phone ( it says unkown device). So i tried to install the adb drivers, but nothing happens.
i wanted to try to push a rom with adb on the phone but it says no device found. i am such a noob, i hope some can help me.
thx

Can't boot, tried flashtool, not going well, help

So heres my issue, ATT G2. Installed clean rom xe 1.1 then was dumb and used titanium to restore my app data, not system, just app. but someone that caused a system ui to keep crashing, so I got into recovery mode by holding down and power button (white screen that asks to reset to factory). Did that and it booted to TWRP ran a script and then went back to LG screen and then blank screen with flashing led and that's where it stayed, won't go any further.
I've put it in download mode now and am using LG flash tool but when I plug the phone in the box for COM41 in the flash tool just says waiting for connection and thats it. then when I unplug it it says failed, obviously. Is my phone a brick or can it be saved?
I think it's getting a model information check fail in lg flashtool, ugh this sucks.
bova80 said:
So heres my issue, ATT G2. Installed clean rom xe 1.1 then was dumb and used titanium to restore my app data, not system, just app. but someone that caused a system ui to keep crashing, so I got into recovery mode by holding down and power button (white screen that asks to reset to factory). Did that and it booted to TWRP ran a script and then went back to LG screen and then blank screen with flashing led and that's where it stayed, won't go any further.
I've put it in download mode now and am using LG flash tool but when I plug the phone in the box for COM41 in the flash tool just says waiting for connection and thats it. then when I unplug it it says failed, obviously. Is my phone a brick or can it be saved?
Click to expand...
Click to collapse
LOL, i just went through the same thing. I'll be posting a fix tonight I worked out with Scott.
"There is a "back door" method. This is why they updated TWRP by the way...
Download this: https://dl.dropboxusercontent.com/u/...with cmd.zip
Extract it to desktop. open the command.bat file.
Type "adb reboot recovery" then press enter. You need to keep doing this during the factory reset.
This assumes you have drivers installed. If you have no drivers installed for recovery mode then just select generic Google Nexus ADB drivers.
You kinda have to hammer the reboot recovery command. Its all timing... To hammer it... press the up arrow in the dos prompt and that will repeat the line. then press enter.
Keep doing it until you see it reboot to twrp and you should be able to sideload or load from storage.
It may take 10 or 15 minutes to get the exact right timing so dont give up.
And of course, this is all dependent upon you having the drivers already installed."
- Scott
For timing, you'll need to wait right when TWRP starts writing the script and start hammering it out. Timing is everything so when you see the TWRP screen starting hitting the up cursor and enter. It should load recovery. Don't bother using the tool, it won't work as it thinks your device is a D802 and won't be compatible with the dll. This will get you back to normal and from here you can just wipe and reinstall the rom again fresh with out losing media/data on the your drive.
I tried to download the file since I am in the same boat, but the dropbox is giving errors... Could you please repost the link to get the file? It would be greatly appreciated
MkV05 said:
I tried to download the file since I am in the same boat, but the dropbox is giving errors... Could you please repost the link to get the file? It would be greatly appreciated
Click to expand...
Click to collapse
When I get home to my personal desktop I'll be able to upload the link again. It's not my drop box but I have the files to upload to drop box and repost.
SamsungGalaxyStig said:
When I get home to my personal desktop I'll be able to upload the link again. It's not my drop box but I have the files to upload to drop box and repost.
Click to expand...
Click to collapse
Awesome, been waiting for this! Just to confirm, will the same file work for someone with a Verizon G2 who's having the same problem?
ccmbr002 said:
Awesome, been waiting for this! Just to confirm, will the same file work for someone with a Verizon G2 who's having the same problem?
Click to expand...
Click to collapse
I haven't tested it on VZW unfortunately. Check with scrosler. However, I assume it should be similar if not the same, but don't quote me on that.
Updated Link guys: https://www.dropbox.com/s/qsjwguwtlyczwdh/adb with cmd.zip
so I got it right when it said teamwin to reboot but everytime it reboot it tried to run the script and would never actually go into twrp. att is sending me a new phone but I'm worried when I send this one back they'll get me for being rooted.
SamsungGalaxyStig said:
I haven't tested it on VZW unfortunately. Check with scrosler. However, I assume it should be similar if not the same, but don't quote me on that.
Updated Link guys: https://www.dropbox.com/s/qsjwguwtlyczwdh/adb with cmd.zip
Click to expand...
Click to collapse
I just messaged him to double check - I don't have access to my phone for a few days (out of town) but if he hasn't responded by the time I get home I'll just go ahead and try it and post here if it works or not. Thanks again for sharing this file!
Got the file... and MANY THANKS!!! It allowed me to un-softbrick my G2 finally
this just isn't working for me, so hard to get it to get that command and when I do it still just reboots to the wiping partition script and reboots again. Think I'm screwed. Anything I can do in download mode or any other commands I can send? @SamsungGalaxyStig
video clip of what is happening
http://youtu.be/8U_mgYYxIpQ
here is what the script says
updating partition details
Running boot script....
Finished running bootscript,
Processing AOSP recovery commands....
----Wiping Data Partition----
Wiping data without data/media...
Done.
Removing all files under '/cache'
---- data partition wipe complete!
Done processing script file
Click to expand...
Click to collapse
bova80 said:
this just isn't working for me, so hard to get it to get that command and when I do it still just reboots to the wiping partition script and reboots again. Think I'm screwed. Anything I can do in download mode or any other commands I can send? @SamsungGalaxyStig
video clip of what is happening
http://youtu.be/8U_mgYYxIpQ
here is what the script says
Click to expand...
Click to collapse
The minute you see the twrp screen pop up start hammering away at the adb command listed before. after you type it once, you can keep pressing the up cursor and it will just replicate the previous command. You are opening up the cmd in the adb folder right?
SamsungGalaxyStig said:
The minute you see the twrp screen pop up start hammering away at the adb command listed before. after you type it once, you can keep pressing the up cursor and it will just replicate the previous command. You are opening up the cmd in the adb folder right?
Click to expand...
Click to collapse
yeah just tried it again and as soon as I hit it it starts rebooting again goes to TeamWin screen and then runs the same script I posted before and when it is done it reboots and then goes to blank screen. I had just put the latest twrp on the day before too so I don't understand why it isn't booting to it.
My biggest thing is will ATT freak and send the phone back once they get it and go to download mode and see it says rooted or if they try the hard reset and see it goes to a TeamWin screen.
side note, if I can type adb shell and get it to prompt me there, is there anything I can try and type quickly to have it do anything else?
bova80 said:
yeah just tried it again and as soon as I hit it it starts rebooting again goes to TeamWin screen and then runs the same script I posted before and when it is done it reboots and then goes to blank screen. I had just put the latest twrp on the day before too so I don't understand why it isn't booting to it.
My biggest thing is will ATT freak and send the phone back once they get it and go to download mode and see it says rooted or if they try the hard reset and see it goes to a TeamWin screen.
side note, if I can type adb shell and get it to prompt me there, is there anything I can try and type quickly to have it do anything else?
Click to expand...
Click to collapse
Are you constantly doing the adb recovery reboot? or once or twice?
SamsungGalaxyStig said:
Are you constantly doing the adb recovery reboot? or once or twice?
Click to expand...
Click to collapse
I did it a bunch of times continuously and it would just keep rebooting. Am I supposed to just keep doing that for 10-15min straight? How will I know if it gets into recovery if it just keeps rebooting when ever I keep doing that?
bova80 said:
I did it a bunch of times continuously and it would just keep rebooting. Am I supposed to just keep doing that for 10-15min straight? How will I know if it gets into recovery if it just keeps rebooting when ever I keep doing that?
Click to expand...
Click to collapse
Keep doing it, watch your phone as it will eventually boot into recovery itself without running script.
SamsungGalaxyStig said:
Keep doing it, watch your phone as it will eventually boot into recovery itself without running script.
Click to expand...
Click to collapse
when I'm sending that command though it never actually runs the script, it just reboots.
I'll try this out when I get home, hopefully my fingers don't get tired, lol. How long did it take you?
bova80 said:
when I'm sending that command though it never actually runs the script, it just reboots.
I'll try this out when I get home, hopefully my fingers don't get tired, lol. How long did it take you?
Click to expand...
Click to collapse
like 5-10 min at most. it's literally timing. and based on what i saw on the youtube video you were having the exact same problem. btw, you have your drivers installed correctly right? you can check that under device manager. BTW, are you using a PC or mac?
SamsungGalaxyStig said:
like 5-10 min at most. it's literally timing. and based on what i saw on the youtube video you were having the exact same problem. btw, you have your drivers installed correctly right? you can check that under device manager. BTW, are you using a PC or mac?
Click to expand...
Click to collapse
on a pc. when i go under device manager I think it says something like lg modem, I'll know for sure when I get home.
omg it finally worked! thanks, I eventually just gave up with the command prompt and it went in.

Nexus 6P black screen will not boot into OS

Okay, so there is no screen protector or anything. Not rooted or unlocked or tampered in any way. I've had the phone for 26 hours and then the following happened:
EDIT: YouTube video added https://youtu.be/yAVmTz7MQbQ
I pulled the phone out of my pocket to unlock it. I see the lock screen and put in my pin (yes, I see the actual screen and stuff on it. Let me make that clear.) after I enter my pin successfully the screen locks itself. I contacted Google support and they said to factory reset it. I did the full factory data reset in the recovery mode (again, the screen works. I can see everything to do a FDR and I can see the boot animation) and it starts to boot up. Once I see the "welcome" screen it instantly locks itself. I can hear the audible "latch" locking sound that it makes when you press the power button. I know the buttons are not malfunctioning because they work perfectly fine in bootloader / recovery mode to scroll up and down and select things. I've tried multiple things but nothing seems to work. The problem here is that I want to try and do a factory image but my computer will NOT recognize my Nexus 6P when in recovery mode / bootloader mode. I have all the drivers installed but since I can't access the OS and enable OEM UNLOCKING there is no way to factory flash a factory image is there? Can someone maybe help point me in the right direction? Again, I can NOT access the OS at all whatsoever.
You just need the bootloader unlocked to flash a factory image, you can't enable that from settings o.0 so I guess your down to RMA now.
The command is now "fastboot flashing unlock"
Hey downloading a tool kit from this devices tools sections. Install the latest adb / fastboot binarys and try again
Good luck !
hutzdani said:
You just need the bootloader unlocked to flash a factory image, you can't enable that from settings o.0 so I guess your down to RMA now.
The command is now "fastboot flashing unlock"
Hey downloading a tool kit from this devices tools sections. Install the latest adb / fastboot binarys and try again
Good luck !
Click to expand...
Click to collapse
Hi Hutzdani, when I try to run the command it says "remote: oem unlock is not allowed". I have the RMA in progress but 3-5 days with no phone is going to become grueling unfortunately and I want to try everything I can. :S
xandr00 said:
Hi Hutzdani, when I try to run the command it says "remote: oem unlock is not allowed". I have the RMA in progress but 3-5 days with no phone is going to become grueling unfortunately and I want to try everything I can. :S
Click to expand...
Click to collapse
Can you run fastboot format cache and format user data? Then will anything happen ?
Sounds like you need to edit the partition that holds the data change for allow OEM unlock - there's a few threads about this on XDA for the N9 and N6 as far as I can remember.
It would seem the ability to flash a fresh system.img would solve this

Categories

Resources