Related
Searched all over and google yada yada yada. So i end up opening a thread here.
Hello guys/babes/kids/oldfags/ifags in disguise . I have a galaxy nexus here that will only boot into
-download mode,
- fastboot (not working at all, pc wont detect its fastboot and buttons all dead when in recovey/fastboot)
- safe mode - will boot into safe mode if i did combo buttons when attached to charger/pc
The story :
When i booted it from batt pull via only power button press, it will go into download mode straight and if i power off or factory reset in safe mode, it will reboot back into safe mode.
I cant flash anything since fastboot is broken. Ive tried Odin back to factory image of Galaxy Nexus GSM ICS and Jellybean but the prob isnt solved and fastboot is still broken. Tried repartition and bootloader update in ODIN yet still fail. And after every successful flash of repackaged stock, it will directly boot into safe mode (for both ICS and JB factory image). Why i didnt flash using fastboot? Fastboot is broken that is. Lets continue...
Other hardwares are still fine as in safe boot, ive tested all the buttons, display, calls, speaker etc. This is fastboot relate i believe as no matter what pc ive tried and all types of gnex drivers i tried. It wont even fart when connecting to pc(win7 x86). ADB works fine though when i booted into the safe mode. Im able to do adb stuffs but whenever i query it to reboot to fastboot or recovery, a dead end again. OMAPflash the tuna edition for omap4460? Tried yet still the same.
Additional facts : The phone was not unlocked and tempered by any way before the prob happened but now the bootloader is unlocked after i flashed the repackaged ODIN (chainfire posted it)
So XDA Gnex'ers, LET THE HUNT BEGIN!
Sent from my GT-I9100 using xda premium
Reserved for updates
Have you stumbled across this yet?
http://forum.gsmhosting.com/vbb/f63...-i9100g-via-usb-cable-freeeeeeeeeeee-1465412/
iowabowtech said:
Have you stumbled across this yet?
http://forum.gsmhosting.com/vbb/f63...-i9100g-via-usb-cable-freeeeeeeeeeee-1465412/
Click to expand...
Click to collapse
thats omapflash, to be more precise.
op, try that. also, might want to read something more, efrant has a link on it on one of his threads.
sent from my i9250
bk201doesntexist said:
thats omapflash, to be more precise.
op, try that. also, might want to read something more, efrant has a link on it on one of his threads.
sent from my i9250
Click to expand...
Click to collapse
Yup, tried it but its still the same. Fastboot still dosent work and relashing packaged factory images in odin dosent fix the fastboot
Sent from my GT-I9100 using xda premium
Saw a Jtag service nearby and thinking of sending it in. Its roughly after conversion from RM(Malaysian Ringgit) around USD$90. Possible recovery from the issue?
Sent from my GT-I9100 using xda premium
does it try to create an error log? or are you able to pull bug report?
it boots into download mode and safemode so, there's hope.
override182 said:
Searched all over and google yada yada yada. So i end up opening a thread here.
Hello guys/babes/kids/oldfags/ifags in disguise . I have a galaxy nexus here that will only boot into
-download mode,
- fastboot (not working at all, pc wont detect its fastboot and buttons all dead when in recovey/fastboot)
- safe mode - will boot into safe mode if i did combo buttons when attached to charger/pc
The story :
When i booted it from batt pull via only power button press, it will go into download mode straight and if i power off or factory reset in safe mode, it will reboot back into safe mode.
I cant flash anything since fastboot is broken. Ive tried Odin back to factory image of Galaxy Nexus GSM ICS and Jellybean but the prob isnt solved and fastboot is still broken. Tried repartition and bootloader update in ODIN yet still fail. And after every successful flash of repackaged stock, it will directly boot into safe mode (for both ICS and JB factory image). Why i didnt flash using fastboot? Fastboot is broken that is. Lets continue...
Other hardwares are still fine as in safe boot, ive tested all the buttons, display, calls, speaker etc. This is fastboot relate i believe as no matter what pc ive tried and all types of gnex drivers i tried. It wont even fart when connecting to pc(win7 x86). ADB works fine though when i booted into the safe mode. Im able to do adb stuffs but whenever i query it to reboot to fastboot or recovery, a dead end again. OMAPflash the tuna edition for omap4460? Tried yet still the same.
Additional facts : The phone was not unlocked and tempered by any way before the prob happened but now the bootloader is unlocked after i flashed the repackaged ODIN (chainfire posted it)
So XDA Gnex'ers, LET THE HUNT BEGIN!
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
First of all, bricked mean there is nothing beside a black screen. Nowaday device are hard to brick. second, One does not simply flash a gnex with odin. It's simply a big wtf that is shining through my head. 3rd, if fastboot is not working, it's because it need a special driver that i suppose you didnt install. If you can boot your phone in fastboot but can connect to it, it's because you have a broken USB port, which is not the case since you can access adb. 4th, i'm still trying to know how you achieved this. It look to me you were following some instruction and it either ended, tl;dr i will skip a few step, hope it will work which didnt or you missed electricity. Install Kies, get your phone in download and recover your phone from it. Never attempt again to play on custom rom. Man, how can someone derp a galaxy nexus, it is like the easiest device to work with.
chadouming said:
First of all, bricked mean there is nothing beside a black screen. Nowaday device are hard to brick. second, One does not simply flash a gnex with odin. It's simply a big wtf that is shining through my head. 3rd, if fastboot is not working, it's because it need a special driver that i suppose you didnt install. If you can boot your phone in fastboot but can connect to it, it's because you have a broken USB port, which is not the case since you can access adb. 4th, i'm still trying to know how you achieved this. It look to me you were following some instruction and it either ended, tl;dr i will skip a few step, hope it will work which didnt or you missed electricity. Install Kies, get your phone in download and recover your phone from it. Never attempt again to play on custom rom. Man, how can someone derp a galaxy nexus, it is like the easiest device to work with.
Click to expand...
Click to collapse
Thx for the reply.
Some clarification here, im not the owner of this phone. Im using 9100 and im just helping a friend to recovery. Ive tried few pcs and it wont even fart when i plugged in during fastboot or recovery (i read someone that in recovery you can do some commands) but the pc(s) wont even detect a hardware being plugged in.
Plus, in fastboot, i cant press any of the hardware keys. No vol up or vol down and the power button dosent work in recovery. I only got to the 3e stock recovery via 'adb reboot recovery' during in fast mode where it booted into the relaxing chillin android with the triangle + red exclamation mark on its tummy. Pressed all buttons and it went to the 3e recovery.
At the 3e, only power button works. I cant toggle a bit using the vol keys. Note that the vol buttons work to boot the phone into fastboot and download mode and also during safe mode, all the keys works flawlessly.
So, i tried the odin method to recovery this living Gnex but with a faulty heart and kidney but it will still boot to safe mode regardless of ICS or Jellybean.
How did this happen?
I have no idea. The owner of the phone claimed that he has never rooted or tempered it in any way. Plus it was still on ICS when i first got the phone (all data was still intact but it was in safe mode at that time).
Regarding drivers, ive attempted many pcs with almost every drivers available. Shall i list em here:
- KIES
- Naked Nexus drivers
- PDA.net
- the 'official' gnex verizon driver set which is said working on GSM devices etc.
Tried those and adb+download mode works fine. Pcs detect em and tried to install the hardware n search for the drivers but not in fastboot. Its just dead.
killersloth said:
does it try to create an error log? or are you able to pull bug report?
it boots into download mode and safemode so, there's hope.
Click to expand...
Click to collapse
Adb works fine so im able to pull anything when its booted. Im not sure if we can pull anything in download mode. Adb/fastboot didnt work in download mode. Am i correct? Mind to share some light here on this. And in fastboot, none. No vol keys to operate and the 4-5 pc ive tried wont even fart a sound or hint anything saying a hardware connected. Its like its a dead circuit plugged only in fastboot.
This is quite a super rare case here. Most of the dead gnex i found on the next and also in XDA has a working fastboot that only needs drivers to make it working but on this unit, even the vol keys is dead. Awkwarddddd
Sent from my GT-I9100 using xda premium
override182 said:
Thx for the reply.
Some clarification here, im not the owner of this phone. Im using 9100 and im just helping a friend to recovery. Ive tried few pcs and it wont even fart when i plugged in during fastboot or recovery (i read someone that in recovery you can do some commands) but the pc(s) wont even detect a hardware being plugged in.
Plus, in fastboot, i cant press any of the hardware keys. No vol up or vol down and the power button dosent work in recovery. I only got to the 3e stock recovery via 'adb reboot recovery' during in fast mode where it booted into the relaxing chillin android with the triangle + red exclamation mark on its tummy. Pressed all buttons and it went to the 3e recovery.
At the 3e, only power button works. I cant toggle a bit using the vol keys. Note that the vol buttons work to boot the phone into fastboot and download mode and also during safe mode, all the keys works flawlessly.
So, i tried the odin method to recovery this living Gnex but with a faulty heart and kidney but it will still boot to safe mode regardless of ICS or Jellybean.
How did this happen?
I have no idea. The owner of the phone claimed that he has never rooted or tempered it in any way. Plus it was still on ICS when i first got the phone (all data was still intact but it was in safe mode at that time).
Regarding drivers, ive attempted many pcs with almost every drivers available. Shall i list em here:
- KIES
- Naked Nexus drivers
- PDA.net
- the 'official' gnex verizon driver set which is said working on GSM devices etc.
Tried those and adb+download mode works fine. Pcs detect em and tried to install the hardware n search for the drivers but not in fastboot. Its just dead.
Adb works fine so im able to pull anything when its booted. Im not sure if we can pull anything in download mode. Adb/fastboot didnt work in download mode. Am i correct? Mind to share some light here on this. And in fastboot, none. No vol keys to operate and the 4-5 pc ive tried wont even fart a sound or hint anything saying a hardware connected. Its like its a dead circuit plugged only in fastboot.
This is quite a super rare case here. Most of the dead gnex i found on the next and also in XDA has a working fastboot that only needs drivers to make it working but on this unit, even the vol keys is dead. Awkwarddddd
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Great to know you are not the one who did that . So if i understand correctly, you say download mode work ? If yes, flash another stock rom from chainfire using odin. No one wan't to flash with odin, but if fastboot is not working, you shall at least try it. Also, when you are putting the phone in download mode and connecting it to kies, it should detect it has to be restored. i would say the main reason for it to not work is that android debugging is not ticked in developer options. But that would be strange that adb work on safe mode. There is probably a way to that with adb but you will have to google it. Tell your friend to follow instruction next time. And ffs, do not use odin ! (Little idea too, try to get in fastboot not connected on PC and wait a few minutes then see if you can move with the volume button, then try to connect it on pc)
chadouming said:
Great to know you are not the one who did that . So if i understand correctly, you say download mode work ? If yes, flash another stock rom from chainfire using odin. No one wan't to flash with odin, but if fastboot is not working, you shall at least try it.
Click to expand...
Click to collapse
Yes i have already did that few times. Few times of ICS factory image and few with JB. All are repacked version provided by chainfire. Its the full package not the software only with stripped bootloader n recovery. Its still the same
Sent from my GT-I9100 using xda premium
http://forum.xda-developers.com/showthread.php?t=1392310
download and install toolkit from that thread ^^^^^^
uninstall all gnex drivers you installed
reboot pc, open gnex toolkit, with phone unplugged install the drivers
fastboot should work
killersloth said:
http://forum.xda-developers.com/showthread.php?t=1392310
download and install toolkit from that thread ^^^^^^
uninstall all gnex drivers you installed
reboot pc, open gnex toolkit, with phone unplugged install the drivers
fastboot should work
Click to expand...
Click to collapse
Thx, tried it on a few pcs but it still wont work. Even the volkeys in fastboot didnt work :8
Sent from my GT-I9100 using xda premium
override182 said:
Thx, tried it on a few pcs but it still wont work. Even the volkeys in fastboot didnt work :8
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
did you try flashing google's factory image in odin??
my fastboot once was unresponsive, but rebooting into it fixed it
from safemode, if you adb reboot bootloader it is unresponsive?
killersloth said:
did you try flashing google's factory image in odin??
my fastboot once was unresponsive, but rebooting into it fixed it
from safemode, if you adb reboot bootloader it is unresponsive?
Click to expand...
Click to collapse
Yes i had, still boots to safe mode and the fastboot is still dead. Yes ive tried adb reboot bootloader but its dead in fastboot, again.
Sent from my GT-I9100 using xda premium
only suggestion left is to just boot into fastboot, leave it alone for awhile (5-10 mins), then try and plug it in and mess with it.
Try doing the whole driver thing mentioned above but instead of flashing a Google image just do the boot loader portion, what settings are you using to flash in Odin?
Sparx639
killersloth said:
only suggestion left is to just boot into fastboot, leave it alone for awhile (5-10 mins), then try and plug it in and mess with it.
Click to expand...
Click to collapse
Tried yesterday, nothing happened
Sparx639 said:
Try doing the whole driver thing mentioned above but instead of flashing a Google image just do the boot loader portion, what settings are you using to flash in Odin?
Sparx639
Click to expand...
Click to collapse
First tried pda only with auto reboot, no gooding. The i tried with booloader, no good. Then bootloader only, still no good. Then i tested all including pit file, still no good.
Update, sent in for Jtagging few min ago. The phone is not with me now and ill get it back in 3days working or not. I shall report in back after 3 days. Thanks to all by giving suggestion and ideas. See u guys again in 3 days
Sent from my GT-I9100 using xda premium
chadouming said:
Also, when you are putting the phone in download mode and connecting it to kies, it should detect it has to be restored. i would say the main reason for it to not work is that android debugging is not ticked in developer options.
Click to expand...
Click to collapse
adb does not work in download mode/bootloader. adb only works when adbd (adb service) is started, and that happens in android boot process. it means android debug bridge.
sent from my i9250
Sorry for the long delay to anyone waiting for the answer/status.
Jtag cant fix it. Returned the device to a friend. Prolly a mobo replacement is the solution but its damn pricy here in Malaysia. It costs 80% of the price to get a new Gnex.
Hell yeah and thx to everyone supporting this.
Sent from my GT-I9100 using xda premium
I own a HTC One V. And I did something at the TWRP menu like installing this CARBON-JB-UNOFFICIAL-20131022-1552-primoc thing.. and ever since then the phone doesn't boot.. it won't even go to that menu where it says FASTBOOT{ I think it's called the recovery menu :3 }
But, I charge it.. And then I plug it into the comp, it just connects and disconnects, like it's giving a faint indicator of life :3
Please help. I was on Ignorance V5..
Installing a rom can't hard brick your device.
Try to shut it down by holding the power button and immediately press vol down + power to enter your bootloader. Then you can select recovery and install a backup of your ignorance rom or do whatever you want.
BTW: It looks like you forgot to install the kernel for the custom rom.
ManishByatroy said:
I own a HTC One V. And I did something at the TWRP menu like installing this CARBON-JB-UNOFFICIAL-20131022-1552-primoc thing.. and ever since then the phone doesn't boot.. it won't even go to that menu where it says FASTBOOT{ I think it's called the recovery menu :3 }
But, I charge it.. And then I plug it into the comp, it just connects and disconnects, like it's giving a faint indicator of life :3
Please help. I was on Ignorance V5..
Click to expand...
Click to collapse
Most likely you flashed the wrong ROM.
PrimoU <> PrimoC
Boot loader should still work as expected I guess:
<vol.down>+<power> should get you to the hboot menu.
kvestas said:
Most likely you flashed the wrong ROM.
PrimoU <> PrimoC
Boot loader should still work as expected I guess:
<vol.down>+<power> should get you to the hboot menu.
Click to expand...
Click to collapse
It's not going into Boot Loader. If it did, I would flash back Ignorance.
Please help
ManishByatroy said:
It's not going into Boot Loader. If it did, I would flash back Ignorance.
Please help
Click to expand...
Click to collapse
Did you try fastboot command to reboot into bootloader?
The command might be accepted by phone during it's initial loading stage:
* connect phone to a computer
* run command (e.g. fastboot reboot-bootloader), must be waiting for response from device
* reboot your phone
* if you are lucky enough the command will be accepted on load.
jonas2790 said:
Installing a rom can't hard brick your device.
Try to shut it down by holding the power button and immediately press vol down + power to enter your bootloader. Then you can select recovery and install a backup of your ignorance rom or do whatever you want.
BTW: It looks like you forgot to install the kernel for the custom rom.
Click to expand...
Click to collapse
It isn't going to bootloader when i press power+volume down button.. :\
If I could enter the bootloader menu, I wouldn't have been this worried. :3
kvestas said:
Did you try fastboot command to reboot into bootloader?
The command might be accepted by phone during it's initial loading stage:
* connect phone to a computer
* run command (e.g. fastboot reboot-bootloader), must be waiting for response from device
* reboot your phone
* if you are lucky enough the command will be accepted on load.
Click to expand...
Click to collapse
Can you please tell me where to run this Command? I'm a noob sorry. :/
ManishByatroy said:
Can you please tell me where to run this Command? I'm a noob sorry. :/
Click to expand...
Click to collapse
This command has to be run on a computer.
Similar as you are running fastboot commands to root phone or install custom recovery.
Please google if you are not familiar with fastboot commands at all.
Make sure you have installed proper phone usb drivers to make your phone "visible" from computer.
Btw how did you get running Ignorance?
kvestas said:
Did you try fastboot command to reboot into bootloader?
The command might be accepted by phone during it's initial loading stage:
* connect phone to a computer
* run command (e.g. fastboot reboot-bootloader), must be waiting for response from device
* reboot your phone
* if you are lucky enough the command will be accepted on load.
Click to expand...
Click to collapse
kvestas said:
This command has to be run on a computer.
Similar as you are running fastboot commands to root phone or install custom recovery.
Please google if you are not familiar with fastboot commands at all.
Make sure you have installed proper phone usb drivers to make your phone "visible" from computer.
Btw how did you get running Ignorance?
Click to expand...
Click to collapse
My friend got ignorance running for me.. Like I don't know what and where to enter these fast boot commands.. Any link to learn or you explaining will be appreciated.
phone is blank. hasnt lighted a pixel in a week
phone is charged. how do i know this? because i charged it for 3 days :3
tried all combinations of buttons to get to bootloader. i just cant!!!
i connect it to a comp, it connects and disconnects simultaneously.. :/
pls tell me what to do
ManishByatroy said:
phone is blank. hasnt lighted a pixel in a week
phone is charged. how do i know this? because i charged it for 3 days :3
tried all combinations of buttons to get to bootloader. i just cant!!!
i connect it to a comp, it connects and disconnects simultaneously.. :/
pls tell me what to do
Click to expand...
Click to collapse
You may download and try this tool:
http://forum.xda-developers.com/showthread.php?p=46202420
This might be easier to start from.
kvestas said:
You may download and try this tool:
http://forum.xda-developers.com/showthread.php?p=46202420
This might be easier to start from.
Click to expand...
Click to collapse
Just tried it. I selected device but stuck on downloading drivers
Thanks for the help tho mate
ManishByatroy said:
Just tried it. I selected device but stuck on downloading drivers
Thanks for the help tho mate
Click to expand...
Click to collapse
You can download HTC drivers from almost any other hOV thread.
Like this one in example:
http://forum.xda-developers.com/showthread.php?t=1996665
Basic Requirements. 4th item.
Remember, all you need to try with this tool is to reboot into bootloader. Try to click the tool button while your phone is starting to load.
By the way, you may find fastboot files in that thread as well (Basic Requirements. 5th item).
kvestas said:
You can download HTC drivers from almost any other hOV thread.
Like this one in example:
http://forum.xda-developers.com/showthread.php?t=1996665
Basic Requirements. 4th item.
Remember, all you need to try with this tool is to reboot into bootloader. Try to click the tool button while your phone is starting to load.
By the way, you may find fastboot files in that thread as well (Basic Requirements. 5th item).
Click to expand...
Click to collapse
Yes, I have the HTC Sync installed which gives the necessary drivers for the recognition of HTC phones.. ( My ONE V)
But, the computer just sounds that music when a USB device is connected, the phone is dead. Not even lighting up..
The WinDroid isn't recognizing my device as well..
ManishByatroy said:
Yes, I have the HTC Sync installed which gives the necessary drivers for the recognition of HTC phones.. ( My ONE V)
But, the computer just sounds that music when a USB device is connected, the phone is dead. Not even lighting up..
The WinDroid isn't recognizing my device as well..
Click to expand...
Click to collapse
The computer should not recognize your phone because it is not loaded completely (neither os, neither recovery).
But it might be recognized for a few seconds only while trying to load os. And you might be able to supply reboot command at that particular moment.
Just try what I said.
kvestas said:
You may download and try this tool:
http://forum.xda-developers.com/showthread.php?p=46202420
This might be easier to start from.
Click to expand...
Click to collapse
kvestas said:
The computer should not recognize your phone because it is not loaded completely (neither os, neither recovery).
But it might be recognized for a few seconds only while trying to load os. And you might be able to supply reboot command at that particular moment.
Just try what I said.
Click to expand...
Click to collapse
Yeah.. I tried that.. But nothing is working.. The OS too isn't booting up. So I don't really know when my phone is on or off
ManishByatroy said:
Yeah.. I tried that.. But nothing is working.. The OS too isn't booting up. So I don't really know when my phone is on or off
Click to expand...
Click to collapse
Do you mean led is always off?
---------- Post added at 04:17 PM ---------- Previous post was at 04:14 PM ----------
Try holding power button down for 30s.
kvestas said:
Do you mean led is always off?
---------- Post added at 04:17 PM ---------- Previous post was at 04:14 PM ----------
Try holding power button down for 30s.
Click to expand...
Click to collapse
Tried. Ain't working. LED ain't even turning on while charging too.. So there's really no way to find out whether it's charging..
Update : Still haven't fixed my phone. Any help would be appreciated. Can't enter Bootloader menu. Phone when connected to computer, gives "sound" that every normal USB when connected gives.. So the phone isn't completely dead. After connecting, the computer doesnt react in any way :crying:
I'm quite perplexed. I was using my p600 today, and it worked fine like normal. Tonight I took it out to do some reading, and noticed some flickering streaks across the screen. I thought nothing of it, and did a reboot.
It turned off, but never rebooted. The back and menu buttons flashed once, and then went dark.
I've been trying without success to get it to boot for a half hour, nothing. There is no response to plugging it into a charger, and my computer does not recognize it as being plugged in. (Currently have no access to windows, so unsure of ODIN).
I was running Tamasek's unnoficial 18.1 build at the time.
Any ideas. Would greatly appreciate any help, even just to get some notes off if it is indeed dead.
while plugged into charger (to rule out it hasnt died while youve been messing with it) long hold power button... i forget if its 10 seconds or 30 seconds. same sorta thing happened to me on temasek, flicker screen but then it died itself, and i got a response from my tablet by long power button hold. not sure if we had same cause but thats what worked for me
diabl0w said:
while plugged into charger (to rule out it hasnt died while youve been messing with it) long hold power button... i forget if its 10 seconds or 30 seconds. same sorta thing happened to me on temasek, flicker screen but then it died itself, and i got a response from my tablet by long power button hold. not sure if we had same cause but thats what worked for me
Click to expand...
Click to collapse
Doesn't seem to work for me.
Update:
Holding the power button gives no response, no matter the length of press. However, apparently randomly it will turn on, as the back and menu buttons will light up. If this happens I am able to successfully connect to a computer and view files. I was able to connect to ODIN, however since I am unable to get into download mode I am unable to do anything.
If it is in the state where the buttons are lighting up and I then try to boot it it turns off and is completely unresponsive.
Any ideas? Is there a way to remotely boot into download mode?
Cheers
greenmatrix said:
Update:
Holding the power button gives no response, no matter the length of press. However, apparently randomly it will turn on, as the back and menu buttons will light up. If this happens I am able to successfully connect to a computer and view files. I was able to connect to ODIN, however since I am unable to get into download mode I am unable to do anything.
If it is in the state where the buttons are lighting up and I then try to boot it it turns off and is completely unresponsive.
Any ideas? Is there a way to remotely boot into download mode?
Cheers
Click to expand...
Click to collapse
When lights come on, attach to computer and run the command adb devices... if you dont know about adb then there is plenty of info on the net about it. If adb devices gives you a response (which it will if yoi are able to view files on yoir device then that means you will get and adb response as long as you set up the adb program correctly) then run adb reboot download and then youll be in download mode and flash with odin
diabl0w said:
When lights come on, attach to computer and run the command adb devices... if you dont know about adb then there is plenty of info on the net about it. If adb devices gives you a response (which it will if yoi are able to view files on yoir device then that means you will get and adb response as long as you set up the adb program correctly) then run adb reboot download and then youll be in download mode and flash with odin
Click to expand...
Click to collapse
Thanks, I'll let you know how it goes.
diabl0w said:
When lights come on, attach to computer and run the command adb devices... if you dont know about adb then there is plenty of info on the net about it. If adb devices gives you a response (which it will if yoi are able to view files on yoir device then that means you will get and adb response as long as you set up the adb program correctly) then run adb reboot download and then youll be in download mode and flash with odin
Click to expand...
Click to collapse
I am unable to get the p600 to show under adb devices. However, adb does work successfully for my nexus 6 so it appears to be generally working.
This is on mac, so I don't believe it could be a driver issue. I spent a good while trying to get adb working on windows with no success for either device (killed and restarted adb server, tried reinstalling drivers, different cables, etc).
Frustrating, because the p600 will connect fine to the computer, and I can view files and interact with it. Odin also recognizes it.
I appreciate the help, and any further ideas.
if odin recognizes it then why dont you just try to flash stock again?
diabl0w said:
if odin recognizes it then why dont you just try to flash stock again?
Click to expand...
Click to collapse
I've tried, every time it gets hung up on SetupConnection. Running Odin 3.07. Perhaps a different version of Odin?
greenmatrix said:
I've tried, every time it gets hung up on SetupConnection. Running Odin 3.07. Perhaps a different version of Odin?
Click to expand...
Click to collapse
what version did you use last time... hold on ill get you a link to a dif one you should use 3.07 is kinda old
diabl0w said:
what version did you use last time... hold on ill get you a link to a dif one you should use 3.07 is kinda old
Click to expand...
Click to collapse
Thanks, can't remember what I used when I last flashed with odin, I want to say it was around 1.8x.
greenmatrix said:
Thanks, can't remember what I used when I last flashed with odin, I want to say it was around 1.8x.
Click to expand...
Click to collapse
i meant what did you use to flash twrp so that you were able to flash temasek's? ... use 3.10.7
http://forum.xda-developers.com/showthread.php?t=2711451
diabl0w said:
i meant what did you use to flash twrp so that you were able to flash temasek's? ... use 3.10.7
http://forum.xda-developers.com/showthread.php?t=2711451
Click to expand...
Click to collapse
Yeah, when I flashed TWRP a few weeks ago I believe i used odin 1.8x, can't remember. However I know that it wasn't 3.10.7. I'll see how 3.10.7 works.
It appears to still be hanging on SetupConnection.
greenmatrix said:
It appears to still be hanging on SetupConnection.
Click to expand...
Click to collapse
Hmm i guess its not in download mode then... the only thing i could think of is that for some reason it keeps booting to recovery mode which would make both adb and odin not work. Although idk why youd have a blank screen cuz that doesnt tend to happen for recovery. When the menu buttons light up, do they give you haptic feedback (do they vibrate)? If so, maybe you recently dropped it and the ribbon cable for screen beca,e disloged. Id stilll see if you get any responses from ppl who know more than me before you go pulling your tablet apart tho.
The only other thing i could think of to tell you to do is to keep trying to access download mode by holding the appropriate buttons during boot and then try to flash stock with odin. Sorry, i dont know enough to give any more advice from here
diabl0w said:
Hmm i guess its not in download mode then... the only thing i could think of is that for some reason it keeps booting to recovery mode which would make both adb and odin not work. Although idk why youd have a blank screen cuz that doesnt tend to happen for recovery. When the menu buttons light up, do they give you haptic feedback (do they vibrate)? If so, maybe you recently dropped it and the ribbon cable for screen beca,e disloged. Id stilll see if you get any responses from ppl who know more than me before you go pulling your tablet apart tho.
The only other thing i could think of to tell you to do is to keep trying to access download mode by holding the appropriate buttons during boot and then try to flash stock with odin. Sorry, i dont know enough to give any more advice from here
Click to expand...
Click to collapse
ITS ALIVE!!
Thanks man, you may have just solved it, I feel like an idiot. I hadn't considered that the ribbon cable might be loose, and as I was examining it with a bright light I could see items on the screen. Was successfully able to boot into download mode and flash the stock rom, the screen issue was not solved, but I think it flashed alright.
When I have some time I'm going to take off the back and check out the ribbon cable.
greenmatrix said:
ITS ALIVE!!
Thanks man, you may have just solved it, I feel like an idiot. I hadn't considered that the ribbon cable might be loose, and as I was examining it with a bright light I could see items on the screen. Was successfully able to boot into download mode and flash the stock rom, the screen issue was not solved, but I think it flashed alright.
When I have some time I'm going to take off the back and check out the ribbon cable.
Click to expand...
Click to collapse
im glad you were able to figure it out
greenmatrix said:
ITS ALIVE!!
Thanks man, you may have just solved it, I feel like an idiot. I hadn't considered that the ribbon cable might be loose, and as I was examining it with a bright light I could see items on the screen. Was successfully able to boot into download mode and flash the stock rom, the screen issue was not solved, but I think it flashed alright.
When I have some time I'm going to take off the back and check out the ribbon cable.
Click to expand...
Click to collapse
The ribbon cable coming loose is a very common issue on this tablet (even without dropping it) as it's connected rather poorly. Fortunately it's also relatively easy to fix as per the below:
Fixing Note 10.1 2014 ribbon cable
Especially the screen flickering when it "died" sounds familiar.
epithetic said:
The ribbon cable coming loose is a very common issue on this tablet (even without dropping it) as it's connected rather poorly. Fortunately it's also relatively easy to fix as per the below:
Fixing Note 10.1 2014 ribbon cable
Especially the screen flickering when it "died" sounds familiar.
Click to expand...
Click to collapse
This was exactly it. 15 minute fix and everything was golden.
i installed cm14.1 today from the cyanogenmod website i had everything running fine until i reboot into recovery. i got a black screen and it didnt bot into recovery at all so i held my power button and volume down and nothing happens. i cant even boot up into fast boot or anything. nothing is turning my phone on. when i connect it to my pc nothing happens. is there anything i can do?
There's a mega unbrick guide for the OnePlus 3, use that then install the correct firmware and install the custom TWRP and re flash the ROM
i tried that method but the device doesnt even show up on my pc
envious86 said:
i tried that method but the device doesnt even show up on my pc
Click to expand...
Click to collapse
Get this sorted yet? You'll need a modified TWRP recovery for the newest CM based builds. I went through the same thing yesterday or the day before. Try holding volume down and power for like 30 seconds until you feel it vibrate that it is rebooting. Then hold volume *UP* while it reboots or if you see the "your device is not safe..." flash screen hurry and press volume down and go into fastboot. From there you can fastboot flash a new recovery.
I had the same problem as well, in device manager go to ports (com & LPT) and it will show up there under qualcum device. Don't forget to go and turn off certificate verification
Thanks guys I'll try this after work. Hopefully it works. If not sure oneplus are hopefully releasing a new phone soon
No it didn't work. I have a feeling I deleted something I shouldn't have because I was clearing out my files before I restarted and that was that.
you gotta use special twrp recovery for cm14.1...
https://www.androidfilehost.com/?fid=385035244224394867
Just use the recovery rahditzz provided you with a link, if your phone is stuck on black screen with white led hold your power button until it turns off, then boot to fastboot and flash the recovery and you will boot...
rahditzz said:
you gotta use special twrp recovery for cm14.1...
https://www.androidfilehost.com/?fid=385035244224394867
Click to expand...
Click to collapse
thanks didnt work. when i fastboot flash recovery and boot again it just goes into a black screen again
Then use unbrick method 2..
rahditzz said:
Then use unbrick method 2..
Click to expand...
Click to collapse
neither method works. all i can do is get into fastboot mode thats it. it wont show up on my pc at all
Method 2 workshop 100%, unless its a hardware fault..
Are you pushing volume up while plugging in cable?
I am. To be honest its very complex too me. I'm new to android and all this is so hard. I follow steps but I'm not 100% sure what I doing. Also my computer isn't great. Do these methods work on vista? Is there a video tutorial or anything? Sorry for annoying you and you don't understand how thankful i am for your help.
I jeep getting the sahara communication failed error
envious86 said:
I am. To be honest its very complex too me. I'm new to android and all this is so hard. I follow steps but I'm not 100% sure what I doing. Also my computer isn't great. Do these methods work on vista? Is there a video tutorial or anything? Sorry for annoying you and you don't understand how thankful i am for your help.
Click to expand...
Click to collapse
Your running vista???? Good god update your OS!!
Maybe your fastboot drivers got updated? There were some reports around this. You could try reinstalling the drivers and following the unbrick guide without an internet connection.
Sent from my ONEPLUS A3003 using Tapatalk
Cool u can boot into Fastboot, what error do you get when you type Fastboot devices? Nothing shows up?
So I've got into a big trouble... I wanted to manually update my Pixel 6 Pro to the latest version using an official OTA (since the update wasn't available yet for my country and I wanted to stay up-to-date). It was all fine until it said 74 % done... and the power in my house has completely turned off... The device hasn't given me any error and rebooted, hower it got stuck on a Google logo. I rebooted to the recovery mode how it was suggested and did a clean factory reset, then rebooted again... and nothing changed, only the logo background has changed (white vs black). The BIGGEST problem is, the device OEM is NOT unlocked I tried entering the fastboot mode and flashing the device with a recovery image but it obviously didn't work as it required OEM to be unlocked... I am in a big depression now, somehow I fear that it's not fixable... But if some awesome soul could suggest a way to try out, that would be great! Thanks in advance.
I would try the android flash tool and flash the whole full ROM onto the phone. Expect to lose your data though.
mkhcb said:
I would try the android flash tool and flash the whole full ROM onto the phone. Expect to lose your data though.
Click to expand...
Click to collapse
Doesn't your phone have to be unlocked to use the flash tool?
The data is all backed up so it's not a problem to lose it. The problem is actually making the phone to boot past the logo... I will try that Android Flash Tool but I fear that the phone should be unlocked first
Try this tool: https://pixelrepair.withgoogle.com/carrier_selection
Not sure if its any different to the android flash tool.
As expected, Android Flash Tool requires you to to have the device unlocked. At this point I am out of ideas and is truly disappointed. The tool mentioned above probably works the same way.
Maybe try sideloading OTA again. Are you able to do that?
mclarence said:
Try this tool: https://pixelrepair.withgoogle.com/carrier_selection
Not sure if its any different to the android flash tool.
Click to expand...
Click to collapse
McNaccken said:
As expected, Android Flash Tool requires you to to have the device unlocked. At this point I am out of ideas and is truly disappointed. The tool mentioned above probably works the same way.
Click to expand...
Click to collapse
Unfortunately, someone else in another thread reported that the Pixel Repair site (not the Android Flash Tool) hasn't been updated for the P6P.
McNaccken said:
So I've got into a big trouble... I wanted to manually update my Pixel 6 Pro to the latest version using an official OTA (since the update wasn't available yet for my country and I wanted to stay up-to-date). It was all fine until it said 74 % done... and the power in my house has completely turned off... The device hasn't given me any error and rebooted, hower it got stuck on a Google logo. I rebooted to the recovery mode how it was suggested and did a clean factory reset, then rebooted again... and nothing changed, only the logo background has changed (white vs black). The BIGGEST problem is, the device OEM is NOT unlocked I tried entering the fastboot mode and flashing the device with a recovery image but it obviously didn't work as it required OEM to be unlocked... I am in a big depression now, somehow I fear that it's not fixable... But if some awesome soul could suggest a way to try out, that would be great! Thanks in advance.
Click to expand...
Click to collapse
If you can still get into recovery mode, maybe try sideloading the OTA again?
EDIT: Ninja'd by @znel52
Lughnasadh said:
If you can still get into recovery mode, maybe try sideloading the OTA again?
EDIT: Ninja'd by @znel52
Click to expand...
Click to collapse
Yeah I'm afraid since he did a factory reset debugging got disabled. Worth a shot though.
znel52 said:
Yeah I'm afraid since he did a factory reset debugging got disabled. Worth a shot though.
Click to expand...
Click to collapse
Oh crap, didn't think about that.
I know not everyone has access to a laptop but if you do always use that over a desktop. In the event of something like this you will have the battery power to carry you through.
I'm sorry this happened to you. The only option may be to send it to Google for repairs.
Sorry for your phone. I experienced this on a nexus 6 that didn't have USB debugging or OEM unlock enabled. I tried sideload, put the update package on the phone storage, try to update with Android recovery. Nothing worked. Stuff happens with phones. I hope you can get a new phone.
God bless.
Sorry to hear this. It seems that I need to open USB debugging option just in case for my Pixel 6, which finally arrived across the ocean after a month.
McNaccken said:
So I've got into a big trouble... I wanted to manually update my Pixel 6 Pro to the latest version using an official OTA (since the update wasn't available yet for my country and I wanted to stay up-to-date). It was all fine until it said 74 % done... and the power in my house has completely turned off... The device hasn't given me any error and rebooted, hower it got stuck on a Google logo. I rebooted to the recovery mode how it was suggested and did a clean factory reset, then rebooted again... and nothing changed, only the logo background has changed (white vs black). The BIGGEST problem is, the device OEM is NOT unlocked I tried entering the fastboot mode and flashing the device with a recovery image but it obviously didn't work as it required OEM to be unlocked... I am in a big depression now, somehow I fear that it's not fixable... But if some awesome soul could suggest a way to try out, that would be great! Thanks in advance.
Click to expand...
Click to collapse
Since the Repairtool has not been updated for your needs and considering that your device is not unlocked, your only option is to contact Google (/your seller). Maybe they can offer you an updated version of the tool (unlikely) or replace your device.
You just described, btw, my horror scenario when updating the BIOS of my PC. The lights going out, when doing a firmware update o.o
Oh my. I'm so sorry for you to have experienced that.
Ok, so I did a CMOS reset on my main PC, since it also failed to load after the lost power accident. Loaded my PC then just fine and tried connecting the phone again. Got to recovery mode and tried "adb devices" command... and it listed my Pixel device !! I tried the "adb sideload" command but it's stuck at 5% for at least 20-30 mins. The phone's last message is "Verifying update package". Not sure if it's a good sign, but afaik if USB debugging is off etc, you can not use adb commands. What would you guys suggest, try waiting for another 30 mins or unplug the phone, restart PC and try again? I am using USB-A to USB-C cable btw, maybe I could use USB-C to USB-C.
McNaccken said:
Ok, so I did a CMOS reset on my main PC, since it also failed to load after the lost power accident. Loaded my PC then just fine and tried connecting the phone again. Got to recovery mode and tried "adb devices" command... and it listed my Pixel device !! I tried the "adb sideload" command but it's stuck at 5% for at least 20-30 mins. The phone's last message is "Verifying update package". Not sure if it's a good sign, but afaik if USB debugging is off etc, you can not use adb commands. What would you guys suggest, try waiting for another 30 mins or unplug the phone, restart PC and try again? I am using USB-A to USB-C cable btw, maybe I could use USB-C to USB-C.
Click to expand...
Click to collapse
My apologies for asking the obvious - did you select "adb sideload" in the recovery menu ? At least I was blind enough to oversee that I need to select this option first
Can you boot into fastboot from the recovery ? If yes you could also try installing a factory image instead of the update package.... I read you cannot because your device is locked, but you can unlock in fastboot (you can always relock later).... only downside is that this will clear all data on the phone for sure....
McNaccken said:
So I've got into a big trouble... I wanted to manually update my Pixel 6 Pro to the latest version using an official OTA (since the update wasn't available yet for my country and I wanted to stay up-to-date). It was all fine until it said 74 % done... and the power in my house has completely turned off... The device hasn't given me any error and rebooted, hower it got stuck on a Google logo. I rebooted to the recovery mode how it was suggested and did a clean factory reset, then rebooted again... and nothing changed, only the logo background has changed (white vs black). The BIGGEST problem is, the device OEM is NOT unlocked I tried entering the fastboot mode and flashing the device with a recovery image but it obviously didn't work as it required OEM to be unlocked... I am in a big depression now, somehow I fear that it's not fixable... But if some awesome soul could suggest a way to try out, that would be great! Thanks in advance.
Click to expand...
Click to collapse
I had a similar issue with applying ota updates and have seen quite a few reports of users having trouble. Not sure what the deal is, but for some reason this phone seems super finicky with updates. Are you still in the return window? You may want to reach out to Google support or one of their "authorized repair shops".
For me, I ran the flash all bat, rebooted, got a message saying my device can't be trusted. So I rebooted, wiped data, rebooted again and got the same thing. So I rebooted, ran the flash all bat file again, rebooted phone, and screen went black and it never powered on again. Suspect circuit board may have fried some how. Anyways, long story short, contacted Google and had a replacement sent out with minimal hassle.
McNaccken said:
Ok, so I did a CMOS reset on my main PC, since it also failed to load after the lost power accident. Loaded my PC then just fine and tried connecting the phone again. Got to recovery mode and tried "adb devices" command... and it listed my Pixel device !! I tried the "adb sideload" command but it's stuck at 5% for at least 20-30 mins. The phone's last message is "Verifying update package". Not sure if it's a good sign, but afaik if USB debugging is off etc, you can not use adb commands. What would you guys suggest, try waiting for another 30 mins or unplug the phone, restart PC and try again? I am using USB-A to USB-C cable btw, maybe I could use USB-C to USB-C.
Click to expand...
Click to collapse
so you can get through this... you'll be fine. pick adb sideload and it will say waiting, then run the command.
you can also change slots at the bootloader menu or try running the unlock oem command to see if it will allow you to unlock..... not sure if you can change slots without unlocking bootloader. try different USB ports on your computer (and restart your computer just in case) along with using the latest platform tools (adb/fastboot) and USB driver directly from Google (not third party apps or websites.
download the OTA zip again (and just open and close it quickly to verify it isn't corrupt).. and also make sure you have 5-10GB of space free on your computer.
usually the boot slot is changed whenever an OTA is flashed. it will tell you what slot you're in at the bootloader menu (where it says fastboot and device state locked).
can you try holding power button (when it's not plugged in) and as soon as you see then Google logo, hold volume down. that will get you to safe mode. and as quickly as you can, enable "OEM Unlocking" - which will allow you to flash a full factory image.
sorry for this comment being all over the place. if you need help, just reply, and I'll be more methodical next time
s3axel said:
I read you cannot because your device is locked, but you can unlock in fastboot (you can always relock later).... only downside is that this will clear all data on the phone for sure....
Click to expand...
Click to collapse
I don't think the problem is that his bootloader is locked - it's unlocked, however, they factory reset the device which likely caused USB Debugging to be turned off, as it defaults to after a factory reset.
I'm so glad years ago I swore to use Uninterruptible Power Supplies (UPS) for all the PCs I build for myself or my wife.