Develop Bugs

[Q] I think I messed up manual update, please help

Hi all,
My OTA update kept failing so I attempted a manual update to 4.04.
I missed updating the boot.img file. I did the system, recovery and radio then relocked the bootloader.
When I turn it on, it stays on the google splash screen. When I go into bootloader mode and try recovery mode, I get the red triangle. My computer does not seem to be recognizing the phone, I get the error: device not found.
Is there something I might try?
Thanks in advance

AV8ing said:
Hi all,
My OTA update kept failing so I attempted a manual update to 4.04.
I missed updating the boot.img file. I did the system, recovery and radio then relocked the bootloader.
When I turn it on, it stays on the google splash screen. When I go into bootloader mode and try recovery mode, I get the red triangle. My computer does not seem to be recognizing the phone, I get the error: device not found.
Is there something I might try?
Thanks in advance
Click to expand...
Click to collapse
In fastboot mode (obviously), unlock the bootloader, flash the boot image, and leave the bootloader unlocked. Done.

Thanks for the quick repy efrant! A big question is how do I unlock the bootloader if my computer doesn't recognize the phone. I am getting "device not found" so I seem to be unable to unlock the bootloader in the first place.

AV8ing said:
Thanks for the quick repy efrant! A big question is how do I unlock the bootloader if my computer doesn't recognize the phone. I am getting "device not found" so I seem to be unable to unlock the bootloader in the first place.
Click to expand...
Click to collapse
So your GNex is booted in fastboot mode and your computer does not recognize it? If this is the case, it is likely a driver issue, and you should re-install.
It is normal that your GNex is not recognized by your computer when booted not in fastboot mode, when you can't boot.

efrant said:
So your GNex is booted in fastboot mode and your computer does not recognize it? If this is the case, it is likely a driver issue, and you should re-install.
It is normal that your GNex is not recognized by your computer when booted not in fastboot mode, when you can't boot.
Click to expand...
Click to collapse
Hey efrant ^^ I'll sort it out ^^ (if you don't mind)
Dude, chec my sig, all the drivers and tutorials needed, can be found in the Win8 thread.
Follow that tut. then the phone should be recognized. Then erase the phone With:
Code:
fastboot erase system
fastboot erase boot
fastboot erase recovery
This ensures, that the flash is successful. If you don't erase first, it's likely, that the phone won't correctly write the files.
Then flash the files, with these codes:
Code:
fastboot flash boot (Always do this first) <Fille directory\file name.img>
fastboot flash system <Fille directory\file name.img>
fastboot flash recovery <Fille directory\file name.img>
DO NOT ERASE/FLASH userdata!! Do that, and you WILL lose ALL of your data!
If you want, I can help you, with tamviewer. I've helped a few people, this way It has always worked

Normally it does recognize the phone, but it doesn't seem to since I messed this up. I will try to re-install the drivers to see if that works. It is in fastboot mode, I hear the tone from the computer that something has connected when I reboot the fastboot, but it doesn't get recognized.

AV8ing said:
Normally it does recognize the phone, but it doesn't seem to since I messed this up. I will try to re-install the drivers to see if that works. It is in fastboot mode, I hear the tone from the computer that something has connected when I reboot the fastboot, but it doesn't get recognized.
Click to expand...
Click to collapse
Go into the dev manager, and look for: Android 1.0
If you see that, then Update devuice drivers -> Select from a list -> Samsung ADB Interface
That should do the trick

Thanks much, familyguy59. I'll try this now.

AV8ing said:
Thanks much, familyguy59. I'll try this now.
Click to expand...
Click to collapse
No prob. That's what some of us, have made to a "quest" Instead of flaming n00bs, help them, and make sure, they find their place, in this community

Thanks so much efrant and familyguy59! There were a couple of bumps in the road, but I flogged my way through them. I thought I had bricked my phone for sure. Once again, thanks so much.

AV8ing said:
Thanks so much efrant and familyguy59! There were a couple of bumps in the road, but I flogged my way through them. I thought I had bricked my phone for sure. Once again, thanks so much.
Click to expand...
Click to collapse
No prob, dude! That's what we're here for

familyguy59 said:
No prob. That's what some of us, have made to a "quest" Instead of flaming n00bs, help them, and make sure, they find their place, in this community
Click to expand...
Click to collapse
+1 to this guy XD
Sent from my Galaxy Nexus using XDA

jzero88 said:
+1 to this guy XD
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
And the "xD" was neccessary... in what way? ^^ It is true, though.
If you aren't feeling the same, then it's your thing. I'm here, to help others, and help them understand, what, what features do, and what is needed, to do what....

Need to return to stock w/out functioning power button

OK here's the quick version of what happened.
Last night, before leaving work, I was playing a game (dice w/buddies) and when I was finished I put the phone to sleep. Picked it up after my 45 min drive home and the screen wouldn't turn on at all. Pulled the battery and as soon as I put it back in the phone vibrated and started the boot process. I didn't even hit the power button. I let it do it's thing and just watched. The screen was all kinds of jacked!! Vertical banding and discoloration to say the least. Well it took about 10 min to boot but when it did the touchscreen was unresponsive. After about 10 min of batt pulls to reboot and check the screen, I called VZW for a replacement.. (They overnighted one and it will be here this morning) So after that call, I just put the phone down and fed my daughter and did a few things around the house. Went back about 2 hrs later and pulled the battery and rebooted the phone to find that the screen now works! BUT the power button does not. It won't wake the phone up,put it to sleep, nothing. It's dead. So I thought I would unroot/relock and take it back to stock so I can send it back. Here is the problem with that; with the power button broken, fastboot won't recognize the phone. I can get into the bootloader via rom toolbox lite (JRummy app) and that works fine. But whether I try it thru adb or WugFresh's toolkit, as soon as the phone hits "Checking fastboot status", it fails. When you go to the device manager in Win7 and try to update the drivers, it fails. It comes up as something like INTF7 or something like that.
So how can I return to stock without a working power button? Even if I was to get it back to stock somehow, I can't relock it as I would have to hit the power button to accept the warning. Is there any other way?

I heard there was some issues with adb on 4.2. You might want to try updating your adb on your comp and then retry fastboot. There was a post on here about what steps to take to troubleshoot adb.

eqjunkie829 said:
I heard there was some issues with adb on 4.2. You might want to try updating your adb on your comp and then retry fastboot. There was a post on here about what steps to take to troubleshoot adb.
Click to expand...
Click to collapse
SDK was updated last night to the newest version. I don't think it's an adb/sdk issue. They are not connecting (I think) because the power botton is broken and the phone turns on as soon as the battery is put in. It's almost like it thinks the power button is being held in.
Once you get it to reboot into fastboot mode, it doesn't do anything. None of the buttons work then. Volume or power. And all adb says is "waiting for device."

cubsfan187 said:
SDK was updated last night to the newest version. I don't think it's an adb/sdk issue. They are not connecting (I think) because the power botton is broken and the phone turns on as soon as the battery is put in. It's almost like it thinks the power button is being held in.
Once you get it to reboot into fastboot mode, it doesn't do anything. None of the buttons work then. Volume or power. And all adb says is "waiting for device."
Click to expand...
Click to collapse
ADB doesn't work in the bootloader (fastboot mode). It will work in a custom recovery, or once boot into Android though.
When in the bootloader the only commands that will work will be fastboot commands, and they should be all you need to get back to stock and lock your bootloader up.

cupfulloflol said:
ADB doesn't work in the bootloader (fastboot mode). It will work in a custom recovery, or once boot into Android though.
When in the bootloader the only commands that will work will be fastboot commands, and they should be all you need to get back to stock and lock your bootloader up.
Click to expand...
Click to collapse
The fastboot commands don't work. Once you get into bootloader mode, nothing works. The volume keys,power key, nothing. When you type in a fastboot command it sits at "waiting for device" and never does anything. If you look in device manager (Win7) is shows a strange INFT2 (or something like that) driver that needs to be installed. I have searched for hours and found nothing on that. Even the toolkits stall at fastboot commands.

cubsfan187 said:
The fastboot commands don't work. Once you get into bootloader mode, nothing works. The volume keys,power key, nothing. When you type in a fastboot command it sits at "waiting for device" and never does anything. If you look in device manager (Win7) is shows a strange INFT2 (or something like that) driver that needs to be installed. I have searched for hours and found nothing on that. Even the toolkits stall at fastboot commands.
Click to expand...
Click to collapse
This sounds like a driver issue with your PC. I recommend that you start fresh. Uninstalling the current drivers, and installing new ones. http://forum.xda-developers.com/showthread.php?t=1379875 <-- I recommend the Naked Driver. http://forum.xda-developers.com/showpost.php?p=29044502&postcount=735 <-- guide there on how to install them.
If you used fastboot on this PC successfully in the past, you could also just do some tinkering to figure out why, but this may take more work to diagnose than actually just nuking the current setup and setting up new ones.

cubsfan187 said:
When you go to the device manager in Win7 and try to update the drivers, it fails. It comes up as something like INTF7 or something like that.
cupfulloflol said:
This sounds like a driver issue with your PC. I recommend that you start fresh. Uninstalling the current drivers, and installing new ones. http://forum.xda-developers.com/showthread.php?t=1379875 <-- I recommend the Naked Driver. http://forum.xda-developers.com/showpost.php?p=29044502&postcount=735 <-- guide there on how to install them.
If you used fastboot on this PC successfully in the past, you could also just do some tinkering to figure out why, but this may take more work to diagnose than actually just nuking the current setup and setting up new ones.
Click to expand...
Click to collapse
I already tried to mess with the drivers. They won't update while in fastboot mode. It comes up as INTF7 (or whatever it was) and they cannot be found. As long as I can lock the bootloader I will send it back rooted and maybe even on a close-to-stock rom. That's probably the best I can do.
Click to expand...
Click to collapse
Click to expand...
Click to collapse

cubsfan187 said:
I already tried to mess with the drivers. They won't update while in fastboot mode. It comes up as INTF7 (or whatever it was) and they cannot be found. As long as I can lock the bootloader I will send it back rooted and maybe even on a close-to-stock rom. That's probably the best I can do.
Click to expand...
Click to collapse
You can get back to stock as long as you are at least rooted. You can do this, which will allow you to do it all as long as the device can boot into Android.

cupfulloflol said:
You can get back to stock as long as you are at least rooted. You can do this, which will allow you to do it all as long as the device can boot into Android.
Click to expand...
Click to collapse
This is exactly what I am gonna try after getting the new phone set up. :good:

[Q] Possibly hard bricked my phone?

After flashing a nightly of CM10.2, my phone never booted and instead got stuck in fastboot. My power button has also been broken for months, so it's impossible to navigate the menus in the fastboot ui. When I take my battery out, it automatically boots into fastboot on its own.
Additionally, I found a way to boot into recovery without a power button, but the device is not being recognized as plugged in by my computer.
Any help??? It'd be greatly appreciated, I'm without a phone until I can find a way to fix this.

Its simple, you need to setup the drivers for your computer to connect via fastboot. Then you can simply flash the stock images by google.

mortenmhp said:
Its simple, you need to setup the drivers for your computer to connect via fastboot. Then you can simply flash the stock images by google.
Click to expand...
Click to collapse
How??? I've tried to already from the toolkit

sinaisinai43 said:
How??? I've tried to already from the toolkit
Click to expand...
Click to collapse
sigh.
dont use the toolkit.
there's a nice thread in general about how to return to stock. even gives a section on how deal with drivers.

[Q] Can my N7(2013) still be saved?

Hi, my N7 is bricked and I wanted to fix it.
I tried to flash ROM but couldn't do it since my computer wont recognize my N7 (except in Recovery Mode-> Sideload).
I think it has something to do with the "developer options -> need to check USB Debugging", however, I can't do that since my phone when turned on, Google Logo appears, then afterwards, BLACK SCREEN (and now in a loop, but there is no X logo just plain black).
My phone is rooted & unlocked. Out of curiousity (My fault), I bricked my N7.
I've read a lot of article on how to unbrick my N7 and I think I now know how to do it- through Android SDK/ADB Tool. I've also read the a guide on how to change drivers (and tried it in all possible ways I can think of), and it did install the driver. However searching my N7 through ADB Tool doesn't go through.
adb devices
List of devices attached
(**nothing follows**)
But if I turn my N7 to Recovery Mode->apply update from adb:
will show the result:
adb devices
List of devices attached
**serial number** sideload
I don't know what other ways in order to unbrick my N7.
I hope you can help me with it.

You can enter bootloader, right? Then try to use fastboot to flash a new rom.

Use wugs program but tick tablet is in bootloop.

Can you boot a brick in to recovery mode? No...so you aren't bricked...

Thanks for the info man!
AnarchoXen said:
Can you boot a brick in to recovery mode? No...so you aren't bricked...
Click to expand...
Click to collapse
Hi, thanks for the info... I already solved my problem.. If only I have read your post earlier I could've saved xx hours in my research!! LOL
donb1 said:
Use wugs program but tick tablet is in bootloop.
Click to expand...
Click to collapse
I tried, but N7 isn't recognized by PC. So the main problem is really how to make my N7 recognized by PC (ADB/bootloader).
But problem fixed now. Thanks!
Calvin Gross said:
You can enter bootloader, right? Then try to use fastboot to flash a new rom.
Click to expand...
Click to collapse
Before I fixed my N7, this is what I tried. But the problem is, PC wont recognize/find my N7 when I do:
adb devices nor fastboot devices
But, I already fixed my problem. Thanks for the response! Greatly appreciate it!

I cant boot my oneplus 3 at all

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?