My N9 seems to have an issue with it's port as it can charge but I cannot get a pc to recognize it via adb or fastboot. All my other devices work fine on that pc. I don't even get the prompt to choose what mode to use when hooked to the PC nor does my PC recognize anything is connected. Anyway I'm running Slimrom currently but am ready to get rid of this tablet. Is there a way to revert to stock without having pc access? I know some HTC devices used to be able to flash a rom by putting it in the root folder and renaming the file something specific (model number) and then boot into bootloader. Does the N9 have that? I couldn't find any info so I'm assuming not. I have TWRP/Magisk so I could just sell/pass it on rooted running a rom too. Just thought stock would be better.
henderjr said:
My N9 seems to have an issue with it's port as it can charge but I cannot get a pc to recognize it via adb or fastboot. All my other devices work fine on that pc. I don't even get the prompt to choose what mode to use when hooked to the PC nor does my PC recognize anything is connected. Anyway I'm running Slimrom currently but am ready to get rid of this tablet. Is there a way to revert to stock without having pc access? I know some HTC devices used to be able to flash a rom by putting it in the root folder and renaming the file something specific (model number) and then boot into bootloader. Does the N9 have that? I couldn't find any info so I'm assuming not. I have TWRP/Magisk so I could just sell/pass it on rooted running a rom too. Just thought stock would be better.
Click to expand...
Click to collapse
Have you tried different USB cables and/or different USB ports on your PC? I've had problems in the past myself, with fastboot/ADB connections, and changing the cable or port has sometimes resolved such issues - might be worth a shot, if you haven't already tried it.
Hi, henderjr...
This method...
henderjr said:
...I know some HTC devices used to be able to flash a rom by putting it in the root folder and renaming the file something specific (model number) and then boot into bootloader...
Click to expand...
Click to collapse
...only works for 'true' OEM HTC devices, and whilst the Nexus 9 is manufactured by HTC, it's ostensibly a Google device, built by HTC under license from Google. And only Google make factory stock images for it...
Nexus 9 - WiFi
https://developers.google.com/android/images#volantis
Nexus 9 - WiFi/LTE
https://developers.google.com/android/images#volantisg
The method you refer to, was applicable on my old HTC One M8, and apparently it works for other OEM HTC devices too, but with the Nexus 9 - a Google device - there are no such factory stock images that can be 'placed on the root' for the bootloader to auto-flash.
There is only one way of reflashing the N9 back to factory stock, and that's via fastboot (or with toolkits that use fastboot).
The only other possible way, and I suspect it to be fairly unlikely you'll be able to do... is if you have TWRP installed as your Custom Recovery, and a previously created Nandroid (bare-bones) backup of factory stock stored somewhere on the internal storage of your N9. And then it'd be a relatively simple matter of performing a Nandroid restore. But, as I say, I very much doubt you'll likely have a Nandroid backup floating around somewhere on the device, given the size of such things.
Other than that, I can only suggest you tinker around with different cables/ports, and see if you can get a response from your PC, or maybe even try another PC, if you have access to one.
Hope this helps, and best of luck
Rgrds,
Ged.
GedBlake said:
Have you tried different USB cables and/or different USB ports on your PC? I've had problems in the past myself, with fastboot/ADB connections, and changing the cable or port has sometimes resolved such issues - might be worth a shot, if you haven't already tried it.
Hi, henderjr...
This method...
...only works for 'true' OEM HTC devices, and whilst the Nexus 9 is manufactured by HTC, it's ostensibly a Google device, built by HTC under license from Google. And only Google make available factory stock images for it...
Nexus 9 - WiFi
https://developers.google.com/android/images#volantis
Nexus 9 - WiFi/LTE
https://developers.google.com/android/images#volantisg
The method you refer to, was applicable on my old HTC One M8, and apparently it works for other OEM HTC devices too, but with the Nexus 9 - a Google device - there are no such factory stock images that can be 'placed on the root' for the bootloader to auto-flash.
There is only one way of reflashing the N9 back to factory stock, and that's with Google's factory stock images, which can only be flashed with fastboot (or with toolkits that use fastboot).
The only other possible way, and I suspect it to be fairly unlikely you'll be able to do... is if you have TWRP installed as your Custom Recovery, and a previously created Nandroid (bare-bones) backup of factory stock stored somewhere on the internal storage of your N9. And then it'd be a relatively simple matter of performing a Nandroid restore. But, as I say, I very much doubt you'll likely have a Nandroid backup floating around somewhere on the device, given the size of such things.
Other than that, I can only suggest you tinker around with different cables/ports, and see if you can get a response from your PC, or maybe even try another PC, if you have access to one.
Hope this helps, and best of luck
Rgrds,
Ged.
Click to expand...
Click to collapse
Wow long reply! Thanks for that. I've tried various cables and pcs (2). I have a handful of android devices and my N9 is the only one I can't get to work anymore. I might dig around and try a couple more cables just to be sure. It used to work a year or so ago on this same PC (my work laptop). It was temperamental then as I couldn't touch it at all or it'd disconnect. I kind of figured the HTC autoflash method (I had a EVO, M8, and M10) wouldn't work on it since I couldn't find anything when searching but thought I'd ask since I knew it was made by HTC. I'll likely wipe in TWRP and put one of the available ROMs on it with root and sell/give to one of my somewhat android capable friends. Thanks!
henderjr said:
Wow long reply! Thanks for that. I've tried various cables and pcs (2). I have a handful of android devices and my N9 is the only one I can't get to work anymore. I might dig around and try a couple more cables just to be sure. It used to work a year or so ago on this same PC (my work laptop). It was temperamental then as I couldn't touch it at all or it'd disconnect. I kind of figured the HTC autoflash method (I had a EVO, M8, and M10) wouldn't work on it since I couldn't find anything when searching but thought I'd ask since I knew it was made by HTC. I'll likely wipe in TWRP and put one of the available ROMs on it with root and sell/give to one of my somewhat android capable friends. Thanks!
Click to expand...
Click to collapse
You can get a new usb daughterboard for like $10 us on eBay. It took me about 15-20 minutes to change, and I've never done it before. Couple screws and ribbon cables.
If that's your issue. Pretty easy. Daughterboard has the USB port on it.
https://rover.ebay.com/rover/0/0/0?mpre=https://www.ebay.com/ulk/itm/202105962464
madbat99 said:
You can get a new usb daughterboard for like $10 us on eBay. It took me about 15-20 minutes to change, and I've never done it before. Couple screws and ribbon cables.
If that's your issue. Pretty easy. Daughterboard has the USB port on it.
https://rover.ebay.com/rover/0/0/0?mpre=https://www.ebay.com/ulk/itm/202105962464
Click to expand...
Click to collapse
Awesome! I ordered one. Even found a little guide to help, https://www.ifixit.com/Guide/Nexus+9+USB+Daughterboard+Replacement/43021
henderjr said:
Awesome! I ordered one. Even found a little guide to help, https://www.ifixit.com/Guide/Nexus+9+USB+Daughterboard+Replacement/43021
Click to expand...
Click to collapse
Hope it helps your issue. Be careful around the rear camera when you take the back off, it sticks to the cover a little. The little silvery pieces of tape are a little troublesome too. I've replaced the board on 2 Nexus 9s now. They even charge a little better too
madbat99 said:
Hope it helps your issue. Be careful around the rear camera when you take the back off, it sticks to the cover a little. The little silvery pieces of tape are a little troublesome too. I've replaced the board on 2 Nexus 9s now. They even charge a little better too
Click to expand...
Click to collapse
Thanks I read about the camera and how it likes to stick to the back. I ended up getting a cheap Fire tablet (HD 8") just to have something but would be nice to be able to wipe this thing and see if I can get it running ok. Currently on Slim it freezes and needs to be rebooted frequently.
henderjr said:
Thanks I read about the camera and how it likes to stick to the back. I ended up getting a cheap Fire tablet (HD 8") just to have something but would be nice to be able to wipe this thing and see if I can get it running ok. Currently on Slim it freezes and needs to be rebooted frequently.
Click to expand...
Click to collapse
You certainly do have to be careful with the camera assembly, when removing the back.
Around 3 years ago, I removed the back of my Nexus 9, and not being aware of the camera 'sticking-in-the-hole' problem, I accidently ripped the camera assembly wires/connector from its socket. No real damage was caused, but reconnecting it would have required the removal of a circuit board in order to access the socket and reconnect it. In the end I decided it was more trouble than it was worth, so I've been running my N9 since then, without a working/connected camera. It's not something I've missed to be honest, but yeah... caution is required when removing the back.
Ged.
Sent from my moto g(6) using XDA Labs
GedBlake said:
You certainly do have to be careful with the camera assembly, when removing the back.
Around 3 years ago, I removed the back of my Nexus 9, and not being aware of the camera 'sticking-in-the-hole' problem, I accidently ripped the camera assembly wires/connector from its socket. No real damage was caused, but reconnecting it would have required the removal of a circuit board in order to access the socket and reconnect it. In the end I decided it was more trouble than it was worth, so I've been running my N9 since then, without a working/connected camera. It's not something I've missed to be honest, but yeah... caution is required when removing the back.
Ged.
Sent from my moto g(6) using XDA Labs
Click to expand...
Click to collapse
I don't think I've ever used my N9 camera either. Regardless I'll take my time
Indeed. Once you've gone around all of the edges (I used my fingernail) to prise/detach the back, I would suggest some light finger pressure on the camera to 'pop' it out of its hole, before lifting the back away.
Sent from my moto g(6) using XDA Labs
henderjr said:
Awesome! I ordered one. Even found a little guide to help, https://www.ifixit.com/Guide/Nexus+9+USB+Daughterboard+Replacement/43021
Click to expand...
Click to collapse
I ordered mine from there and they sent a toolkit with it too.
Related
I recently picked up a secondhand Fascinate for my father and have a desire to root it and flash CM for him. Unfortunately, I've run into a roadblock right off the bat: I cannot connect my computer to the phone via USB. The phone only recognizes it as a charger.
The phone is vanilla and is at latest firmware.
The cables I've tried are LG cables from my own phone.
The computer is Win7 64-bit and has Samsung drivers installed.
Help?
EDIT:
Derp. Perhaps the issue is the cable. I've ordered an OEM cable to test this theory. Thoughts?
Cable could be the issue, I know it has been for some that have used after market USB/data cables. Worth trying in order to rule it out.
I would also strongly suggest using Droidstyles guide. Look in General section. Also, on my device, I sometimes have to "jiggle" the connection to the phone. Sounds odd but it works. You will know right away, pull battery and with ODIN open, plug phone in. Should show up in YELLOW.
Sent from my SCH-I500 using XDA App
Ronjoe said:
I recently picked up a secondhand Fascinate for my father and have a desire to root it and flash CM for him. Unfortunately, I've run into a roadblock right off the bat: I cannot connect my computer to the phone via USB. The phone only recognizes it as a charger.
The phone is vanilla and is at latest firmware.
The cables I've tried are LG cables from my own phone.
The computer is Win7 64-bit and has Samsung drivers installed.
Help?
EDIT:
Derp. Perhaps the issue is the cable. I've ordered an OEM cable to test this theory. Thoughts?
Click to expand...
Click to collapse
Ouch, you may be in a jam. I bought a Fascinate on craigslist. I went home, and fired up Heimdall to install CWM [for cm7], and I got "No device found."
It was charging, but that was all. It would do nothing else. I did get it to connect just a few times, after cleaning the USB connector with a small brush [It was a dental brush actually ]. But it clammed up on me again.
I called up Samsung, they said "You need to have the OEM cable. If it's still not working with the OEM cable we will set up a repair." So I went on amazon and bought the cheapest OEM cable I could find [I think it was $2 or $3, it's OEM samsung, but it's shorter than I thought. :-S ]
I was lucky enough to have 1 month left on the warranty. Unfortunately, you might not be so lucky.
After the repair, my USB worked fine. But then, every morning, I would wake my phone up and it would be in a frozen state. [with about 1 frames per second on the Screen-on animation]
I sent it in again, they replaced the main board, and I have not had any problems since.
If you don't have any warranty [there is a 1-year warranty from the date of purchase], I really hope the OEM cable will work for you. If you're out of warranty, the the OEM cable doesn't work, I guess you might try cleaning the port with a brush, maybe you'll get lucky!
Gl
I've received the replacement cable and it seems to be working. My question is answered.
As a side question, what modifications you guys recommend for the phone in terms of stability and speed? Experience tells me to go for CM7 and CWM, but this phone's developer forum is quite a mess, with different variations of both.
I'd recommend either makelegs' CM7 kangs (in the dev section), or teamhacksung's ICS (find it at rootzwiki). Droidstyle's guide in the general section will get you up and running regardless of what rom you want to go for.
Thanks, k_niv, I've decided to go with makelegs's build. The ICS rom seems a bit... fresh. Keep in mind, this is actually for my father, who doesn't need to be dealing with bugs. He just wants his phone to work the way Android should: fast and Bingfree.
(I'm quite happy with my LG VS910, Gingervolt'd, but don't get me wrong, the Fascinate is damn nice for a year-old phone)
Thanks for the prompt help, my expectations were exceeded on this forum.
Hello guys!
For about 2 or 3 weeks now I have the problem that the speaker on my TF201 does not work anymore. Headphones are working fine.
It also does not recognize any USB Sticks anymore. The Dock is not dead, it works fine and also has current on the USB Port (the USB stick LED is activated but does not blink for accessing it). Also the SD Card slot does not work anymore. The MicroSD slot on the tablet itself works fine...
And the next thing: My PC does not recognize the tablet anymore when I connect it. It does load when I connect it to the adapter but I can't transfer files anymore via PC. Cable is not broken but to minimize this risk I already offered a new one just in case.
Do you guys have any idea what this maybe is caused from? Maybe broken hardware? Or maybe a not properly connected cable in the tablet? But if so why is USB and stuff not working?
Please help me, I don't wanna lose such an awesome tablet
And I may can't even RMA it cause I've unlocked and flashed a new ROM on it...
EDIT 12.06.2013: When the tablet is fully turned off and USB is plugged in (PC, not charger) it suddenly powers up. I still can't use USB ports...
EpicLPer said:
Hello guys!
For about 2 or 3 weeks now I have the problem that the speaker on my TF201 does not work anymore. Headphones are working fine.
It also does not recognize any USB Sticks anymore. The Dock is not dead, it works fine and also has current on the USB Port (the USB stick LED is activated but does not blink for accessing it). Also the SD Card slot does not work anymore. The MicroSD slot on the tablet itself works fine...
And the next thing: My PC does not recognize the tablet anymore when I connect it. It does load when I connect it to the adapter but I can't transfer files anymore via PC. Cable is not broken but to minimize this risk I already offered a new one just in case.
Do you guys have any idea what this maybe is caused from? Maybe broken hardware? Or maybe a not properly connected cable in the tablet? But if so why is USB and stuff not working?
Please help me, I don't wanna lose such an awesome tablet
And I may can't even RMA it cause I've unlocked and flashed a new ROM on it...
Click to expand...
Click to collapse
Do you have one of the Prime to USb connectors? I wonder if the issue is in the dock or the tablet connector.
poofyhairguy said:
Do you have one of the Prime to USb connectors? I wonder if the issue is in the dock or the tablet connector.
Click to expand...
Click to collapse
Sadly no. I never ever would have used that cause I have the dock. And Dock can't be broken, the problem appeared since the speaker is not working too.
I tested MicroHDMI output now. Works fine, audio is there too. Hm... Strange...
Hidden "Camera Version" function?
Sorry, wrong thread ^-^" Please delete this entry!
My first guess is that something may have gotten disconnected inside the Prime. It's unlikely, but worth a check. Have you ever opened your prime?
When you have a dock, you have two options of connecting it to your PC. You can put the Prime into the dock then connect the two to your PC or you can just set the dock aside and connect the Prime directly. Have you tried both ways?
Jgrimoldy said:
My first guess is that something may have gotten disconnected inside the Prime. It's unlikely, but worth a check. Have you ever opened your prime?
When you have a dock, you have two options of connecting it to your PC. You can put the Prime into the dock then connect the two to your PC or you can just set the dock aside and connect the Prime directly. Have you tried both ways?
Click to expand...
Click to collapse
Jup I tried both ways.
And no I never opened it up. May I should look for a tutorial. Does iFixIt have an tutorial for it?
I don't think that iFixIt has one. At least they didn't about 6 months ago when I needed to replace my glass. There should be links to tutorials buried in these forums. Also, a little Googling should find you something too.
Regarding the HDMI audio working: Not too much of a surprise. Remember that the micro-hdmi port is sending a data stream with the audio embedded/encoded as 1s and 0s. It seems like something may have (hopefully) come disconnected related to the built-in speaker.
Jgrimoldy said:
I don't think that iFixIt has one. At least they didn't about 6 months ago when I needed to replace my glass. There should be links to tutorials buried in these forums. Also, a little Googling should find you something too.
Regarding the HDMI audio working: Not too much of a surprise. Remember that the micro-hdmi port is sending a data stream with the audio embedded/encoded as 1s and 0s. It seems like something may have (hopefully) come disconnected related to the built-in speaker.
Click to expand...
Click to collapse
I opened it up but I saw no unconnected or partly connected cable. I only lifted up the touchscreen, about the other parts I was too afraid to ruin something... Didn't unscrew so I wasn't able to see the under connectors.
Anyway, I don't think it's an unconnected cable. But if it's a software fault why are suddenly without flashing anything like Kernel or Bootloader so many things not working? That's just... What the hell o-O
Also I don't want to RMA it again. It's flashed and unlocked so I may have to pay 100€ for it... I could easily spend that money on a Galaxy Tab or something. But would still be awesome to have that one as "backup tablet" then just in case so I don't want to just throw it away.
Good on ya for taking a look. If you disconnect the robbon cables that connect the digitizer and LCD to the mainboard, you can set the top part (the screen and glass) aside and take a much better look. I completly understand your reluctance for fear of damaging. I felt the same way when I took mine apart the first time to replace the digitizer glass.
In devices like this, the headphones and the built-in speaker have separate amplifiers. They're not like very old transistor radios where the headphone jack is connected to the speaker wires with an interlock. I found this out when my Viewsonic 4.5" video player had digitally garbled sound in the headphones but not in the built-in speakers. Weirdest thing that I wouldn't expect being old-school...
The upshot is that you simply may have failed components, which is a real bummer since these are (imho) still pretty sweeet tablets.
You *could* always contact ASUS support and describe the problem and see if they can share any familiarity or knowledge with you. Sadly, I've found ASUS support to be bag-of-hammers dumb and patently useless, despite having a decent product.
Jgrimoldy said:
Good on ya for taking a look. If you disconnect the robbon cables that connect the digitizer and LCD to the mainboard, you can set the top part (the screen and glass) aside and take a much better look. I completly understand your reluctance for fear of damaging. I felt the same way when I took mine apart the first time to replace the digitizer glass.
In devices like this, the headphones and the built-in speaker have separate amplifiers. They're not like very old transistor radios where the headphone jack is connected to the speaker wires with an interlock. I found this out when my Viewsonic 4.5" video player had digitally garbled sound in the headphones but not in the built-in speakers. Weirdest thing that I wouldn't expect being old-school...
The upshot is that you simply may have failed components, which is a real bummer since these are (imho) still pretty sweeet tablets.
You *could* always contact ASUS support and describe the problem and see if they can share any familiarity or knowledge with you. Sadly, I've found ASUS support to be bag-of-hammers dumb and patently useless, despite having a decent product.
Click to expand...
Click to collapse
Opened up again, tried to push a few connectors in a bit but nothing... Looks like I really have a hardware failure...
But what now? When I send it to ASUS (or the shop where I bought it) they might say "Nope, you opened that thing". Also flashing back Stock ROM is... Yeah... Many work... I already was on the 4.1.2 Bootloader, upgraded to 4.2.1 now. I don't know how seriously they take that whole hacking/flashing thing, maybe they even repair a flashed tablet.
I dont know if it helps anyone further pin-point the problem because i havent been able to but i have the same issues and for me the sound comes back once i have the screen separated from the tablet. i can restart the tablet many times and audio still works as long as the screen is not fully in its place. If i clip the screen back in its place audio still works until i turn off or restart the tablet.
Sent from my Transformer Prime TF201 using xda app-developers app
Hello i've got the same problem and i'm praying someone can help.
Since updating from Androwook Hairy Bean V2.11 to V2.2 RC1;
there is no sound from the external speaker; playing media, notifications, alarms etc
dock doesnt recognise usb stick
pc doesnt recognize the tablet
on V2.2 RC1 i got the update pad firmware message and i accepted it, not sure if this is the cause because others have done the sam and reported everything working fine.
Also starting getting a notification on startup "unable to detect driver for loudspeaker" on V2.2 RC1. So i downgraded to Hairy Bean V2.11 thinking it would solve the issue but it hasn't, nothings changed.
I've tried a factory reset, cold boot, downloaded dsp manager and not been successful.
Has anyone come across this problem and found a solution?
Please help me
Thanks
zillar5 said:
Hello i've got the same problem and i'm praying someone can help.
Since updating from Androwook Hairy Bean V2.11 to V2.2 RC1;
there is no sound from the external speaker; playing media, notifications, alarms etc
dock doesnt recognise usb stick
pc doesnt recognize the tablet
on V2.2 RC1 i got the update pad firmware message and i accepted it, not sure if this is the cause because others have done the sam and reported everything working fine.
Also starting getting a notification on startup "unable to detect driver for loudspeaker" on V2.2 RC1. So i downgraded to Hairy Bean V2.11 thinking it would solve the issue but it hasn't, nothings changed.
I've tried a factory reset, cold boot, downloaded dsp manager and not been successful.
Has anyone come across this problem and found a solution?
Please help me
Thanks
Click to expand...
Click to collapse
That is very strange mate.
The firmware update was just for the pad and if it had already installed on 2.11 and was working fine then that was done. The only person who ever had a problem with it happened as he was installing it and we fixed that.
Upgrading to 2.2 changed nothing from 2.11 except a slightly newer base and some newer kernels. Even if the kernels were not supporting your hardware when you downgraded back to 2.11 you would have been back on the old kernels and back to how you had it working before.
This does confuse me.. As a test because I cannot think of anything else except hardware failure at the moment can you try getting the downgrade zip from the hairybean thread that takes you back to 4.1.1 bootloader and compatible twrp and then try flashing hairybean 1.51 instead.
Read the instructions thoroughly under the downgrading section.
flumpster said:
That is very strange mate.
The firmware update was just for the pad and if it had already installed on 2.11 and was working fine then that was done. The only person who ever had a problem with it happened as he was installing it and we fixed that.
Upgrading to 2.2 changed nothing from 2.11 except a slightly newer base and some newer kernels. Even if the kernels were not supporting your hardware when you downgraded back to 2.11 you would have been back on the old kernels and back to how you had it working before.
This does confuse me.. As a test because I cannot think of anything else except hardware failure at the moment can you try getting the downgrade zip from the hairybean thread that takes you back to 4.1.1 bootloader and compatible twrp and then try flashing hairybean 1.51 instead.
Read the instructions thoroughly under the downgrading section.
Click to expand...
Click to collapse
Thanks for the assistance Flumpster and I've been following your thread, you've done some damn amazing work!
Just for the record 2.11 + that kernel had my prime running the best it ever has! after doing all the wipes, formats I flashed v2.2 and got the update pad firmware then and missing speaker driver notification? I dismantled my prime and checked for a loose connection on the speaker but it looks ok.
I'll try the downgrade tomorrow (going to bed now) and if that doesn't work, i still have audio through the headphone jack.
Thanks again
zillar5 said:
Thanks for the assistance Flumpster and I've been following your thread, you've done some damn amazing work!
Just for the record 2.11 + that kernel had my prime running the best it ever has! after doing all the wipes, formats I flashed v2.2 and got the update pad firmware then and missing speaker driver notification? I dismantled my prime and checked for a loose connection on the speaker but it looks ok.
I'll try the downgrade tomorrow (going to bed now) and if that doesn't work, i still have audio through the headphone jack.
Thanks again
Click to expand...
Click to collapse
Just to make sure... Are you saying this happened straight after the firmware update on the next reboot or are you saying it happened when updating the rom ?
flumpster said:
Just to make sure... Are you sayig this happened straight after the firmware update on the next reboot or are you saying it happened when updating the rom ?
Click to expand...
Click to collapse
Honestly I don't know because afer I flashed 2.2 the homescreen loaded and the update firmware message appeared straight away. I dont think the notificatipns were sounding as the apps were restoring? Sorry i'm not 100% sure it happened pretty quickly
zillar5 said:
Honestly I don't know because afer I flashed 2.2 the homescreen loaded and the update firmware message appeared straight away. I dont think the notificatipns were sounding as the apps were restoring? Sorry i'm not 100% sure it happened pretty quickly
Click to expand...
Click to collapse
Ok mate.. Well try the downgrade option first and if that doesn't work then first of all I want you to drain your battery completely and leave for an hour. After that charge it up a little and try ( I know this sounds crazy and I thought the same when I first read it in another thread but it fixed our one guy who had problems with the firmware upgrade )
If this still does not work then upgrade back to 2.2 and once you are in the OS I will try to talk you into downgrading that firmware update to see if that helps.
If that still doesn't work after downgrading the firmware update then it is hardware sorry.
flumpster said:
Ok mate.. Well try the downgrade option first and if that doesn't work then first of all I want you to drain your battery completely and leave for an hour. After that charge it up a little and try ( I know this sounds crazy and I thought the same when I first read it in another thread but it fixed our one guy who had problems with the firmware upgrade )
If this still does not work then upgrade back to 2.2 and once you are in the OS I will try to talk you into downgrading that firmware update to see if that helps.
If that still doesn't work after downgrading the firmware update then it is hardware sorry.
Click to expand...
Click to collapse
i did what the 1st page of the ROM says and rebooted into recovery, tried installing 4.1.1 bootloader and recovery zip from my external sd card and failed - unable to open zip? strange...
zillar5 said:
i did what the 1st page of the ROM says and rebooted into recovery, tried installing 4.1.1 bootloader and recovery zip from my external sd card and failed - unable to open zip? strange...
Click to expand...
Click to collapse
ok micro sd card was coming up write protected, so formated and downloaded new files and managed to downgrade to 4.1.1 bootloader and v1.51 - still no sound from external speaker, also sd slot and usb still not working on dock. Tried running the battery flat and leaving it for over an hour then charged a little and powered on still no change.
I'm leaving work now and have limited internet access tonight so i download the v2.2 zip tomorrow and see if that works, otherwise could be hardware hey.
Hi all! I could use a little help if ya'll don't mind. I'm new to the Amaze but not at all to Android.
I found an Amaze 4g on eBay for $65 that was in pretty good shape with one glaring problem: it wasn't fully functional. The seller explained that it would bootloop after hitting the HTC screen and, knowing what I know about Android, it sounded to me like this should be pretty simple to fix. And if I'm absolutely wrong, then I should be able to sell it for parts (perfect screen on it) to get some of my money back!
Well, it came in and sure enough, it bootlooped at the HTC screen and it was still S-On (yay for hoping nobody trashed its internals too hard!). So I slapped a factory image on the SD Card, loaded it up, and after a slow first boot I heard the T-Mobile jingle! Yay, all is good! Or so I thought...
On stock software, all is good. Everything functions as it should. And if I wanted to leave it stock, I would have never noticed a problem. However, when I went to go unlock it, that's when I began to run into problems. For the life of me, no matter what I do, I absolutely cannot get fastboot to work! ADB works great! I've transferred quite a bit over USB so the port itself seems fine. I've loaded up drivers (started out with universals, then went to HTC, then went to the toolkit stickied at the top of the forums here) and no matter what I use, it simply will not work. I can ADB to it all day, but I just cannot use fastboot.
Just going with the assumption that maybe I had bad/dirty/whatever drivers/conflicts, I actually installed Windows 7 64-bit from scratch, loaded up Windows Updates, and then ran the all-in-one toolkit (which takes care of drivers for me) and alas, absolutely nothing different. ADB works great but I can't get any response from fastboot with the device.
Have I done something wrong/dumb here? Is there something special about this device that could allow something required for fastboot to not work (damaged USB port in a special way) that would allow all other USB operations to function?
Thanks in advance, friends!
Jaxidian said:
Hi all! I could use a little help if ya'll don't mind. I'm new to the Amaze but not at all to Android.
I found an Amaze 4g on eBay for $65 that was in pretty good shape with one glaring problem: it wasn't fully functional. The seller explained that it would bootloop after hitting the HTC screen and, knowing what I know about Android, it sounded to me like this should be pretty simple to fix. And if I'm absolutely wrong, then I should be able to sell it for parts (perfect screen on it) to get some of my money back!
Well, it came in and sure enough, it bootlooped at the HTC screen and it was still S-On (yay for hoping nobody trashed its internals too hard!). So I slapped a factory image on the SD Card, loaded it up, and after a slow first boot I heard the T-Mobile jingle! Yay, all is good! Or so I thought...
On stock software, all is good. Everything functions as it should. And if I wanted to leave it stock, I would have never noticed a problem. However, when I went to go unlock it, that's when I began to run into problems. For the life of me, no matter what I do, I absolutely cannot get fastboot to work! ADB works great! I've transferred quite a bit over USB so the port itself seems fine. I've loaded up drivers (started out with universals, then went to HTC, then went to the toolkit stickied at the top of the forums here) and no matter what I use, it simply will not work. I can ADB to it all day, but I just cannot use fastboot.
Just going with the assumption that maybe I had bad/dirty/whatever drivers/conflicts, I actually installed Windows 7 64-bit from scratch, loaded up Windows Updates, and then ran the all-in-one toolkit (which takes care of drivers for me) and alas, absolutely nothing different. ADB works great but I can't get any response from fastboot with the device.
Have I done something wrong/dumb here? Is there something special about this device that could allow something required for fastboot to not work (damaged USB port in a special way) that would allow all other USB operations to function?
Thanks in advance, friends!
Click to expand...
Click to collapse
Hi,
I think that a USB port may be broken, but that would require soldering another USB port on it, so it might not be worth it.
Did you already try a RUU? If it's a software issue you may be in luck since RUU's fix those 90% of the time!
SuperAfnan said:
Hi,
I think that a USB port may be broken, but that would require soldering another USB port on it, so it might not be worth it.
Did you already try a RUU? If it's a software issue you may be in luck since RUU's fix those 90% of the time!
Click to expand...
Click to collapse
As I said, I recovered the soft-brick with an RUU. So getting to stock is fine, but I don't want to stay stock.
Are you saying it's possible that the USB port is broken even though ADB works perfectly and I can transfer a couple GB of data over it successfully?
Jaxidian said:
As I said, I recovered the soft-brick with an RUU. So getting to stock is fine, but I don't want to stay stock.
Are you saying it's possible that the USB port is broken even though ADB works perfectly and I can transfer a couple GB of data over it successfully?
Click to expand...
Click to collapse
Well that's just a guess... lol
It's probably not a USB problem then.
Yeah, unless there's something different about the Amaze compared to most other Android phones, I don't think this is a USB problem although it acts like it is. I'm really baffled on this. :-/
Jaxidian said:
Yeah, unless there's something different about the Amaze compared to most other Android phones, I don't think this is a USB problem although it acts like it is. I'm really baffled on this. :-/
Click to expand...
Click to collapse
Well good luck, but you at least got it on a stock ROM working fine. You could sell it and make a profit this time!
It could possibly be a hardware issue, but IDK.
What are you trying to fastboot? Make sure your in the correct window I mean you have to be in bootloader.. I forget it almost every time also if adb works it has to work.. Try the correct jbear hboot and see cuz if I'm right jbear hboot are fastboot enable or something like that
Sent from my HTC_Amaze_4G using XDA Premium 4 mobile app
ravike14 said:
What are you trying to fastboot? Make sure your in the correct window I mean you have to be in bootloader.. I forget it almost every time also if adb works it has to work.. Try the correct jbear hboot and see cuz if I'm right jbear hboot are fastboot enable or something like that
Click to expand...
Click to collapse
Simply running "fastboot devices" is my litmus test - I'm unable to get it to actually see the device. And yes, I have it booted into the bootloader and I have put it into fastboot mode.
@ Jaxidian
i m not an expert ! just giving advice
May be m completely wrong, just trying to help
have u tried in ubuntu ?
Check your fastboot script?
Sent from my HTC_Amaze_4G using XDA Premium 4 mobile app
So if you hook the phone up to the computer and at a command prompt type, "adb devices" it returns your device serial number; but, if you then type, "adb reboot recovery" and are then in the bootloader fastboot and type, "fastboot devices" it doesn't return the device serial number?
This device is EOL I realize but I would like to root it. Problem is I can't get any pc's to even acknowledge it is plugged in. Can I get this thing rooted again without ADB???
My bootloader is unlocked from when I first got the device.
EDIT: So it was the USB port that was bad. Ordered a daughter board from E-Bay and now I have working ADB. I'm going to leave this thread open in case someone does figure out a way to get root without adb...
andyroidking said:
This device is EOL I realize but I would like to root it. Problem is I can't get any pc's to even acknowledge it is plugged in. Can I get this thing rooted again without ADB???
My bootloader is unlocked from when I first got the device.
Click to expand...
Click to collapse
If you can't get the drivers set up, try Wug's NRT toolkit. He has a walk-through on setting up/removing/reinstalling drivers. You don't need ADB to root, but you do need to boot into a custom recovery to install a root program (I use SuperSu). You can boot a recovery via CMD from fastboot as long as the recovery is in your adb/fastboot data folder.
FWIW, NRT can do all.
Sent from my Nexus 9 using Tapatalk
ritchea said:
If you can't get the drivers set up, try Wug's NRT toolkit. He has a walk-through on setting up/removing/reinstalling drivers. You don't need ADB to root, but you do need to boot into a custom recovery to install a root program (I use SuperSu). You can boot a recovery via CMD from fastboot as long as the recovery is in your adb/fastboot data folder.
FWIW, NRT can do all.
Sent from my Nexus 9 using Tapatalk
Click to expand...
Click to collapse
I'm really thinking it is my connector. Sometimes it doesn't even charge. I guess I could try to boot one of my pc's into a live Linux distro. I never had issues when I ran Arch. Actually I could try it on my server. It is an Odroid XU4 though but it runs Arch... Thanks.
Cables are most often the cause.
ritchea said:
Cables are most often the cause.
Click to expand...
Click to collapse
Linux doesn't recognize it either. I assume it is the port/cable. The original cable is long gone but I have many brand new Anker and other brands but none work for connecting... Guess I'm screwed. Really wanted root because I'm having issues with battery drain again and the screen not coming on. I wanted to get a custom kernel running... Oh well.
I use off-brand cable exclusively. Have you tried uninstalling all Android USB connections then allowing an auto re-install? I've had to do that with my N9 at times. A few times, the driver showed up in device hardware but nothing further (connection). I right-clicked and updated driver-just went through the process with no new driver just basically re-install. Once, it was the cable but all others worked.
ritchea said:
I use off-brand cable exclusively. Have you tried uninstalling all Android USB connections then allowing an auto re-install? I've had to do that with my N9 at times. A few times, the driver showed up in device hardware but nothing further (connection). I right-clicked and updated driver-just went through the process with no new driver just basically re-install. Once, it was the cable but all others worked.
Click to expand...
Click to collapse
I tried removing everything. It never even acknowledges it is even plugged in. I also tried on 1 brand new Windows system. Same deal. I did a live boot of Linux and nothing. I tried on my Odroid and nothing. I'm not new to this and have many PC's and other devices but none work.
Only thing I noticed is under developer options it comes up as ptp or mtp but if I try changing it I will always say charging no matter what I pick.... So I never even get a USB permission dialog...
As this isn't new territory, you know some cables don't have pin config for data transfer.
Are you able to get recognition of your device with ADB devices command?--recognized but unauthorized?
[C:\Program Files (x86)\Android\sdk\platform-tools>adb devices
List of devices attached
007667324ccb229b unauthorized]
ritchea said:
As this isn't new territory, you know some cables don't have pin config for data transfer. Have you done a factory reset? That may be the only way to get proper permissions for PC again.
Click to expand...
Click to collapse
Yup... And I'm doing it again now. This time both in Android then from the bootloader (pwr+dn).
Also apparently when I flash stock back on this a year ago for my son to use I never flashed the recovery image, or not correctly because there is no recovery at all. Just hboot... When I select recovery I get the dead Android..
I altered my previous response. Andy lying on his back is the stock recovery portal. You have to hold power button then push/release vol+. It can be tricky, but pretty sure that's the sequence. I'll flash stock recovery to double check if needed.
ritchea said:
I altered my previous response. Andy lying on his back is the stock recovery portal. You have to hold power button then push/release vol+. It can be tricky, but pretty sure that's the sequence. I'll flash stock recovery to double check if needed.
Click to expand...
Click to collapse
I have to go do some other stuff right now... I think he had the triangle exclamation in his chest though... I'll try some more later. Thanks!
When you have time https://youtu.be/DuuSTnbQSlM
ritchea said:
When you have time https://youtu.be/DuuSTnbQSlM
Click to expand...
Click to collapse
Doh! I'm so spoiled with rooted devices and twrp I forget you have to jump through hoops to get into some recoveries... So, I did the Android reset, Hboot reset and stock recovery hard reset. And no changes. Still only charges. Oh, well. Thanks again.
Quick update... Ordered a usb daughter board from e-bay. Last $10 I'll spend on this device...
andyroidking said:
Quick update... Ordered a usb daughter board from e-bay. Last $10 I'll spend on this device...
Click to expand...
Click to collapse
My USB started acting up on mine too. Watching a movie with a USB otg and it just stopped. I then discovered the only way for it to work was to jiggle it then hold it in a certain angle. I'm guessing something is loose. I haven't opened her up yet. I'd like to grab a new USB port for mine. Is it soldered to the daughterboard? Seems like changing the daughterboard will be easier.
madbat99 said:
My USB started acting up on mine too. Watching a movie with a USB otg and it just stopped. I then discovered the only way for it to work was to jiggle it then hold it in a certain angle. I'm guessing something is loose. I haven't opened her up yet. I'd like to grab a new USB port for mine. Is it soldered to the daughterboard? Seems like changing the daughterboard will be easier.
Click to expand...
Click to collapse
A few screws... I had to fix my camera because I pulled the back off wrong trying to disconnect the battery a while ago. Just gotta be careful. When the part comes in I'll update.
Video:
https://www.ifixit.com/Guide/Nexus+9+USB+Daughterboard+Replacement/43021
eBay store:
http://www.ebay.com/itm/For-Google-...e=STRK:MEBIDX:IT&_trksid=p2057872.m2749.l2649
andyroidking said:
A few screws... I had to fix my camera because I pulled the back off wrong trying to disconnect the battery a while ago. Just gotta be careful. When the part comes in I'll update.
Video:
https://www.ifixit.com/Guide/Nexus+9+USB+Daughterboard+Replacement/43021
eBay store:
http://www.ebay.com/itm/For-Google-...e=STRK:MEBIDX:IT&_trksid=p2057872.m2749.l2649
Click to expand...
Click to collapse
I looked it up and saw it. I noticed the rear camera was attached. Thanks for the info. I changed the screen on my n7 2013, but never thought to change the port on this one. D'oh.
@madbat99 @ritchea
Got the daughter board from China. About 25 minutes to install (I'm getting real good at taking this device apart now...lol). Powered up and connected to my Windows machine. And... It is recognized now! Can't believe I fought so long thinking it was a driver/windows issue.
After taking it out I can see why it would wear out/break. Cheap plastic and it has such a large opening on the outside my son probably tried all the time to plug it in wrong...
@ritchea thanks for your help!
@andyroidking,
I did nothing but super glad you were able to fix it!...and share it with the community.
andyroidking said:
@[email protected]
Got the daughter board from China. About 25 minutes to install (I'm getting real good at taking this device apart now...lol). Powered up and connected to my Windows machine. And... It is recognized now! Can't believe I fought so long thinking it was a driver/windows issue.
After taking it out I can see why it would wear out/break. Cheap plastic and it has such a large opening on the outside my son probably tried all the time to plug it in wrong...
@ritchea thanks for your help!
Click to expand...
Click to collapse
I ordered one from the link you provided. Coming from China so I hope it doesn't take too long. Can't wait. The port is waaaay to big, too much room to jiggle around. Hope this fixed my problem too.
Hi there, I just got the 6P as my nexus 5x went into bootloop (not semi-bootloop from a bad flash, the one that is caused from one of the processors dying) and none of the fixes were working. I just wanted some general info, the do's, the do nots, etc. Does this phone also suffer from the same issue? I was rooted on 8.1 with Magisk. Does flashing / rooting put you more at risk to an unfixable bootloop? I would be planning on just flashing TWRP, and Magisk on a stock rom. Any tips, recommendations, etc would be highly appreciated!
notstevek said:
Hi there, I just got the 6P as my nexus 5x went into bootloop (not semi-bootloop from a bad flash, the one that is caused from one of the processors dying) and none of the fixes were working. I just wanted some general info, the do's, the do nots, etc. Does this phone also suffer from the same issue? I was rooted on 8.1 with Magisk. Does flashing / rooting put you more at risk to an unfixable bootloop? I would be planning on just flashing TWRP, and Magisk on a stock rom. Any tips, recommendations, etc would be highly appreciated!
Click to expand...
Click to collapse
Yes this phone will do it to in fact the message that I am writing is being sent from one that went into bootloop previously. Routing and such does not cause the boot loop. It is a processor malfunction. You can flash a kernel that will disregard the faulty processors in this situation should it become necessary. All you need to do is to make sure your bootloader is unlocked so you will have the ability to flash this kernel and go ahead and search for the fix so you will have it handy.
Sent from my Nexus 6P using Tapatalk
funnel71 said:
Yes this phone will do it to in fact the message that I am writing is being sent from one that went into bootloop previously. Routing and such does not cause the boot loop. It is a processor malfunction. You can flash a kernel that will disregard the faulty processors in this situation should it become necessary. All you need to do is to make sure your bootloader is unlocked so you will have the ability to flash this kernel and go ahead and search for the fix so you will have it handy.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Well that's a shame to hear, my Nexus 5x went into bootloop and I could not fix it, even with the patched files. I hope it doesn't happen to this. But I'm glad to hear it rooting/flashing will not induce a permanent bootloop and that it is indeed a processor malfunction. I just unlocked the device as we speak, I'm going to be flashing Magisk and TWRP soon. What kernel are you referencing, just so I can have it *just incase*.
Thanks for the info!
notstevek said:
Well that's a shame to hear, my Nexus 5x went into bootloop and I could not fix it, even with the patched files. I hope it doesn't happen to this. But I'm glad to hear it rooting/flashing will not induce a permanent bootloop and that it is indeed a processor malfunction. I just unlocked the device as we speak, I'm going to be flashing Magisk and TWRP soon. What kernel are you referencing, just so I can have it *just incase*.
Thanks for the info!
Click to expand...
Click to collapse
Sorry I don't have the URL handy but it's in here just search in the 6p forums and you should easily find it as there has been a lot of chatter about it
Sent from my Nexus 6P using Tapatalk
Unlock the bootloader on the 6p right off the bat. Activate the developer options, Turn on OEM unlocking, Adroid debugging and Debugging notify. Shut off "verify apps over USB". You'll have to connect the device to
the computer and do the fastboot command to achieve the final bootloader unlocking but once done, you're safe. Every time you boot, you'll see the stupidhead screen imploring you to lock the bootloader but ignore it.
Phone will boot evey time. I ultimately downloaded the 8.1.0 (OPM3.171019.013, Jan 2018) image used my Ubuntu laptop to get the rom in the phone, rooted it with Magisk, TWRP'd it and got the latest Lineage 15.1 kernel and
flashed that. Only problem I have is I can't get a USB stick to be read from the OTG socket. It's identified but it won't read the stick. Now that's O.K. with me because the phone will interface with a computer fine AND
if I boot into TWRP recovery, the file manager there does backups to an attached USB stick and can read and write to it perfectly fine. It's a quirk I can live with. I believe only 4 cores are used but it runs pretty nicely.
Battery swaps are a bear and I have a "good" 64Gb model and bought a "bootloop" 128gb special that looks immaculate. I've tried most of the tricks and it's gorked. I'm going to use it for a battery swap practice unit for when
I want to swap the battery on my good 64gb model. I also bought a new housing in case I dork some of the hardware getting the case open. Crappy design on the battery and they expect a $600.00 to $700.00 when new
phone is supposed to be "throwaway" after two years? Oh, don't buy a bootloop special unless it's dirt cheap. I'll not get the $100.00 I paid for the 128gb unit back or out of it. I don't think I'll be able to fix the one I got. When I open the case, I'll heat the CPU's directly and see if that will get it to start.
What is supposed to happen is one is to let the phone drain down to near nothing, plug it into the charger, let it bootloop for 5 minutes and they apply heat to the area between the camera and the fingerprint sensor.
When it gets to 50 degrees C, the phone supposedly shuts down the "bad" cpu's and will boot as a new phone on the "good" cpu's. One then is supposed to run into the menu, become the developer and do the steps I outlined above to allow OEM unlock. THEN it's safe to try and start loading a new ROM as the phone will communicate with a computer. I took the 128Gb unit and got it connected to an Ubuntu Linux laptop and "fastboot devices" shows the phone but since the bootloader is locked it won't do anything with it. I say the 6p is "ok" when compared to a $1000.00 Pixel 2 which of course is going to be a bear if one wishes to swap out the battery in the future. Lithiums only last so long (or any battery chemistry for that matter) then they need to be replace. Spend a grand on phone and it oughta last
more than two years. Kurt
ksaves2 said:
Unlock the bootloader on the 6p right off the bat. Activate the developer options, Turn on OEM unlocking, Adroid debugging and Debugging notify. Shut off "verify apps over USB". You'll have to connect the device to
the computer and do the fastboot command to achieve the final bootloader unlocking but once done, you're safe. Every time you boot, you'll see the stupidhead screen imploring you to lock the bootloader but ignore it.
Phone will boot evey time. I ultimately downloaded the 8.1.0 (OPM3.171019.013, Jan 2018) image used my Ubuntu laptop to get the rom in the phone, rooted it with Magisk, TWRP'd it and got the latest Lineage 15.1 kernel and
flashed that. Only problem I have is I can't get a USB stick to be read from the OTG socket. It's identified but it won't read the stick. Now that's O.K. with me because the phone will interface with a computer fine AND
if I boot into TWRP recovery, the file manager there does backups to an attached USB stick and can read and write to it perfectly fine. It's a quirk I can live with. I believe only 4 cores are used but it runs pretty nicely.
Battery swaps are a bear and I have a "good" 64Gb model and bought a "bootloop" 128gb special that looks immaculate. I've tried most of the tricks and it's gorked. I'm going to use it for a battery swap practice unit for when
I want to swap the battery on my good 64gb model. I also bought a new housing in case I dork some of the hardware getting the case open. Crappy design on the battery and they expect a $600.00 to $700.00 when new
phone is supposed to be "throwaway" after two years? Oh, don't buy a bootloop special unless it's dirt cheap. I'll not get the $100.00 I paid for the 128gb unit back or out of it. I don't think I'll be able to fix the one I got. When I open the case, I'll heat the CPU's directly and see if that will get it to start.
What is supposed to happen is one is to let the phone drain down to near nothing, plug it into the charger, let it bootloop for 5 minutes and they apply heat to the area between the camera and the fingerprint sensor.
When it gets to 50 degrees C, the phone supposedly shuts down the "bad" cpu's and will boot as a new phone on the "good" cpu's. One then is supposed to run into the menu, become the developer and do the steps I outlined above to allow OEM unlock. THEN it's safe to try and start loading a new ROM as the phone will communicate with a computer. I took the 128Gb unit and got it connected to an Ubuntu Linux laptop and "fastboot devices" shows the phone but since the bootloader is locked it won't do anything with it. I say the 6p is "ok" when compared to a $1000.00 Pixel 2 which of course is going to be a bear if one wishes to swap out the battery in the future. Lithiums only last so long (or any battery chemistry for that matter) then they need to be replace. Spend a grand on phone and it oughta last
more than two years. Kurt
Click to expand...
Click to collapse
Hi Kurt,
Wow, first off thanks for the indepth response. My Nexus 5x was unlocked, rooted with Magisk, allowed unlocking, usb debugging etc. Still can't fix it. I put it in the freezer and got it to boot into TWRP for 30 seconds before it boot looped. Bootloader always works, and can flash, but cannot boot into the rom or recovery. Anyway, I bought this 6P (128gb for $170, perfect condition with a Spigen case and glass screen protector.) because the Nexus 5x is dead, but wasn't aware this also has the same issue which sucks. I run Debian 32bit on my laptop, and it's a breeze compared to windows. Just had to grab the binaries for adb and fastboot, unlike windows where you gotta install crazy large sdk packs, make sure you got the correct drivers, etc. I unlocked the 6P, oem unlocking & usb debugging is checked on developer options. I flashed TWRP, and I'm on 8.1 OPM3.171019.014 (Feb 5th) because the newest one (8.1.0 OPM5.171019.015) won't pick up my Verizon simcard. I flashed Elemental X so I can underclock it, I'm running 4 cores at 1,200mhz and it still runs flawlessly. Any reason I should be using the LineageOS 15.1 kernel? I don't ever plan on using LineageOS or a custom rom. Just stock rooted for me. The battery life is kind of poor compared to the Nexus 5x. I'm a little confused, what do you mean by "Battery swaps are a bear"? If it's worth it, maybe I will put in a new battery. Lithiums life are extended if you don't charge 100% and don't let it die. If you keep it above 20% and charge to 90% max, you'll extend the lifespan by a lot. Some phone companies like Samsung already do this. Your 100% charge is actually only 95% or so in reality. Other things like Telsa cars also do this. I wouldn't have upgraded for a few years if my Nexus 5x didn't die, and honestly if I wasn't afraid of another bootloop, I would have gotten another, I loved that phone. The pixel 2 is great, my brother has one, but I'm not spending more than 250 on a phone ever again in my life, and 250 being the absolute max. I also don't want to sign a contract and do a device payment, I want to own it in full. I will upgrade to the pixel 1 XL when this phone requires me to do so, and hopefully that's at least 2 years from now. Thanks in advance!
Cheers.
Tore open the 128gb "bootloop" special using the variety of videos out there. Heated the CPU's directly although the battery
was I believe fully charged. No dice of breaking the bootloop to have it boot to a "clean" system and unlock the bootloader.
There were no anti tamper seals on this thing so I thing someone threw it out there for $94.00 and I stupidly bit. I caution
folks that unless one can buy a "bootloop" special for less than $20.00 and they have a "good" 6P they want to replace a battery on, don't buy a bootloop special unless it is dirt cheap. Use it to practice on for battery replacement before using
it on a "good" 6p.
I heated the CPU, case off while in a bootloop and no magic restoration was seen. The battery was from October 2015.
I dinged the edges of the glass but got the back half off pretty decently. If the thing booted up and I were able to restore it, I would have been happy with it as the dings aren't really noticeable.. I need to get some guitar opening picks without a lip on them as they are better to work with.
Last ditch attempt will be to drain it down to el "zippo" percent left, put it on a charger and see if I can make the $94.00 evaporate under the auspices of a 1000 watt heat gun with the back case off. Again, don't buy a "bootloop" special of a 6p unless it's dirt cheap. Kurt