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?
Related
So, long story short, took the Phone into Sprint so they could look at my headphone jack (was cracked and left ear bud would constantly cut in and out) because its acting up.
Gave the Tech the phone without the battery in it (since he didn’t need to power up the device to clearly see the headphone jack has a huge crack in it) but I left my SD card installed. As he was walking away, I asked him if I could remove my SD card and he let me, then seen that I gave him the phone without a battery. So, I ended up giving it to him (praying he didn’t turn it on and see ViperBoys sick ass ROM booting up) and he accidently pressed the power button turning the phone on. Promptly short after, he removed the battery when the phone was on the HTC screen, didn’t even get the boot animation. I was like OHH $h!t, that gonna mess up my phone & sure as $h!t, it did… Just loops in and out of that screen resetting each time with a little vibrate then looping.
I can get into Fastboot and use ADB, I’ve flashed RUU’s, put Stock image on root of SD and let recovery restore (losing my CWM & my HBOOT 1.400), unlocked, relocked, wiped, thrown, and screamed at it with no luck.
I did do a CWM backup before even setting foot in the Store, so I do have a backup. The 1st thing I tried was restoring it through CWM recovery and that didn’t stop the looping. I can still get into fastboot via power + vol down and adb functionality is still there.
HBOOT is 1.50 and s-on is enabled..
Been reading through threads since lunch and tried many different solutions without success. It seems once a phone is this far gone, people stop responding.
Anyone have any ideas?
New phone will be here tomorrow (free of coarse courtesy of Sprint insurance) but I’ve been without a phone all day and most of yesterday. I’d like to get this one back to stock and booting before I trade it in for the replacement tomorrow
So you ran an RUU and it still didnt work? And you're sure the RUU SUCCESSFULLY ran without any parts of it failing right?
If that's true, there's no hope AFAIK. Try to get it not to show the bootanimation by bricking it further.
yousefak said:
So you ran an RUU and it still didnt work? And you're sure the RUU SUCCESSFULLY ran without any parts of it failing right?
If that's true, there's no hope AFAIK. Try to get it not to show the bootanimation by bricking it further.
Click to expand...
Click to collapse
Yup, RUU ran though fine and finished without error. Thing has been rooted since Revolutionary came out with the 1st rooting scheme for the 3D.. Flashed tons of ROM's never had this problem.
lessegr said:
Yup, RUU ran though fine and finished without error. Thing has been rooted since Revolutionary came out with the 1st rooting scheme for the 3D.. Flashed tons of ROM's never had this problem.
Click to expand...
Click to collapse
My only explanation is that while he removed the battery some of your hardware got borked. This can't possibly be a software issue.
yousefak said:
My only explanation is that while he removed the battery some of your hardware got borked. This can't possibly be a software issue.
Click to expand...
Click to collapse
BUMMER! In case the question comes up I ran "RUU_Shooter_S_Sprint_WWE_2.17.651.5_Radio_1.06.00.1216_NV_NV_spcs_1.42_release_233304_signed" and it ran just fine.
Hmm, hardware issue. Dont see how I can check for that if it doesnt boot.
Guess I'll just have to wait for the new Phone
try to fastboot oem lock it from fastboot. Then RUU, see if that works.
Why even get this one to work if you are getting a replacement?
Sprint is just going to put the phone back to stock....
jdeoxys said:
try to fastboot oem lock it from fastboot. Then RUU, see if that works.
Click to expand...
Click to collapse
The HTC unlock went as expected. Followed the directions to the "T", then relocked, checked in fastboot (not that I could check anywhere else, LOL) and the phone says "*** RELOCKED***". Ran 2.17.651.5 RUU successfully to the finish. Still looping
WEIRD!
DarkManX4lf said:
Why even get this one to work if you are getting a replacement?
Sprint is just going to put the phone back to stock....
Click to expand...
Click to collapse
Because I just want to know WTF happened!!! Had this Phone since release, abused\used the hell out of it by flashing ROMs constantly, restoring backups, tethering like crazy, emailing, texting, FBing...
No reason for it to crap out on me from a simple mistake, not even of my responsibility, lol!
The only issue I've had with this Phone is that damn headphone jack 1/2 way failing..
Got new phone, terrified to even think about trying to flash new ROM though
lessegr said:
Got new phone, terrified to even think about trying to flash new ROM though
Click to expand...
Click to collapse
LULZ
Same problem with me happened.. Except I had hboot 1.5 and I went one month or two without rooting because I was scared to brick it. I ended up rooting it with desperation and I found my one true love ZR3D rom.
BEAUTIFUL, FAST, plus 4.0 skins ;D. Do it man
Sent from my PG86100 using XDA
Threevo said:
LULZ
Same problem with me happened.. Except I had hboot 1.5 and I went one month or two without rooting because I was scared to brick it. I ended up rooting it with desperation and I found my one true love ZR3D rom.
BEAUTIFUL, FAST, plus 4.0 skins ;D. Do it man
Sent from my PG86100 using XDA
Click to expand...
Click to collapse
DONT TEMPT ME DAMMIT! lol! Just been without a phone for almost 3 days. I'm also seeing a lot of new threads about people experiencing what I've gone through.
Woops, sprint\HTC! once again rooted, and running viperROM.... SWWWWWET!
HBOOT 1.5 and s-on is a *****!
Not to mention... But in Linux, I never got revo recovery to flash... You can do it in windows just do it via fastboot.
Took my Orig cwm bsckup "recovery" & "boot" .img and threw them @ the phone via command prompt.
After cwm was restored, I restored my 4\29\2012 backup that I made before I entered the Sprint store, now my phone is back to the exact same way
It was. Pretty Damn sweet!
So much info here!! I'm truly thankful!!!
Sent from my PG86100 using xda premium
Hello everyone,
I seem to be facing a singular issue, but I imagine it is much my fault, and just wanted a confirmation from those more experienced with the device...
I bought an Incredible 4G from eBay, that already had the a copy of Avatar on it, I believe almost the latest update. So when I confirmed the device worked after charging the battery, I flashed the latest copy of Avatar and the JB Gapps, and everything seemed hunkydory.
So, after that, I put in my old SIM, deactivated as I was using a non-4g device, and put it in the Incredible 4G. I started the activation process on the phone, following prompts to reboot the phone (Note: I did not know about CM10.1's issue regarding activation at the time, so one of the possible problems.)
After seemingly failing to activate after the first reboot, I "tried again" and it went down for another reboot. And it stayed down. Completely. I cannot get the phone to start, after charging the battery separately, cannot get into bootloader, nothing. I get QHSUSB_DLOAD when plugged into a computer using USB, but that's it.
A few notes: first time I started up, the screen went to recovery. I didn't think that was an issue; I factory reset from there, and rebooted into Avatar. Second issue: I used ROM updater on the phone to download and install the recovery, as I imagined that there was an automatic checksum done in the process (perhaps it was imagined?), and so when it went to flash, it had some issue, which didn't seem like a problem with the download, and I went through flashing it normally through recovery. Sorry I can't provide more details on that, but everything seemed to work all right after rebooting.
Finally, and this may be irrelevant, I put a 64GB SDXC card in the phone, I had already realized that it could not natively support exFAT, and so left the card in the device until the next time I could boot to recovery to partition it, and went through the activation process with the card inserted and not recognized.
So, I imagine that I have a hard brick, but can't tell if it's completely my fault, because it bricked in a peculiar fashion, at least from what I can tell, as no one seems to have encountered a similar issue after searching for the last 5 days.
If there's any hope for recovery, I would really appreciate some help regarding the device. I'm willing to provide some more info if necessary, and I'd like to find out sooner rather than later if it's a lost cause.
Thanks for any help you guys can give. XDA devs are awesome.
Quite the predicament. Just to clarify, have you tried the following?
1) Remove that super-big MicroSD
2) Remove SIM
3) Remove battery and wait a few minutes; also press the power button while phone is off
4) Only re-inserting the battery, hold vol-down and then hold power until screen comes on (then release power but keep holding vol-down)
I have tried them all; no SIM or SD card has been in there since the issue started. I hadn't tried pushing the power button while the battery was out, but it doesn't seem to change anything. So far, no reaction whatsoever even when holding power + vol down for a few minutes.
ChiqOmar said:
I have tried them all; no SIM or SD card has been in there since the issue started. I hadn't tried pushing the power button while the battery was out, but it doesn't seem to change anything. So far, no reaction whatsoever even when holding power + vol down for a few minutes.
Click to expand...
Click to collapse
Looks like you have a very hard to solve brick, I would like to help, have you tried using fastboot, I mean connected to pc and on that screen issue a fastboot command, also upload a picture of it please since this is new kind of brick, also I found this, our device is supported,
http://unlimited.io/qhsusbdload.htm
Sent from my ADR6410LVW using xda app-developers app
jose51197 said:
Looks like you have a very hard to solve brick, I would like to help, have you tried using fastboot, I mean connected to pc and on that screen issue a fastboot command, also upload a picture of it please since this is new kind of brick, also I found this, our device is supported,
http://unlimited.io/qhsusbdload.htm
Sent from my ADR6410LVW using xda app-developers app
Click to expand...
Click to collapse
You can't do fastboot if you can't reach the bootloader, and I've been assured the unlimited.io tool will not help for DLOAD resulting from non-racun related procedures.
Reading forum posts about QHSUSB_DLOAD suggest either jtag is necessary (which might not be worth it considering the phone can be purchased for $150 on ebay) or some strange strokes of luck after letting the phone sit for a bit. ChiqOmar, sorry I don't have great advice; do all the reading you can about QHSUSB_DLOAD mode.
jose51197 said:
Looks like you have a very hard to solve brick, I would like to help, have you tried using fastboot, I mean connected to pc and on that screen issue a fastboot command, also upload a picture of it please since this is new kind of brick, also I found this, our device is supported,
http://unlimited.io/qhsusbdload.htm
Sent from my ADR6410LVW using xda app-developers app
Click to expand...
Click to collapse
yes sounds like he is stuck in QSHUSB_DLOAD mode, but i don't know if the resolutiion on unlimited.io will help him or not.they say it's not supported for other reasons other than from running their exploit. it might work though.
mdmower said:
You can't do fastboot if you can't reach the bootloader, and I've been assured the unlimited.io tool will not help for DLOAD resulting from non-racun related procedures.
Reading forum posts about QHSUSB_DLOAD suggest either jtag is necessary (which might not be worth it considering the phone can be purchased for $150 on ebay) or some strange strokes of luck after letting the phone sit for a bit. ChiqOmar, sorry I don't have great advice; do all the reading you can about QHSUSB_DLOAD mode.
Click to expand...
Click to collapse
Maybe port HTC unbricking project to our device, and try to help him using it, since he can't do nothing about it right now, ChiqOmar, you ok with testing it ?, btw download ubuntu connect phone and see if the partitions get mounted, btw looks like you need to flash hboot from that mode, that's all then ruu, I have all the tools to do it if you want to
Sent from my ADR6410LVW using xda app-developers app
mdmower said:
You can't do fastboot if you can't reach the bootloader, and I've been assured the unlimited.io tool will not help for DLOAD resulting from non-racun related procedures.
Reading forum posts about QHSUSB_DLOAD suggest either jtag is necessary (which might not be worth it considering the phone can be purchased for $150 on ebay) or some strange strokes of luck after letting the phone sit for a bit. ChiqOmar, sorry I don't have great advice; do all the reading you can about QHSUSB_DLOAD mode.
Click to expand...
Click to collapse
i was able to bring my rezound back after a hard brick with a hex edited hboot that went bad with this tool but ported for rezound. its worth a try?
Thanks for the help everyone. Yes, although it states quite clearly that the Unlimited.io tool is only meant for devices bricked using their tool, I tried it anyway; obviously, nothing changed.
Though JTAG sounds interesting, I have no idea how to get started with that...nor do I really know if I want to travel down that route just now.
The HTC Unbricking Project sounds promising, but also no idea how to get started as it has not been ported for our device. The partitions don't get mounted in Ubuntu, as I connected it to the computer to use the Unlimited.io tool.
Finally, regarding the nature of the brick itself, I really wish I could pinpoint the issue better to help others if a similar issue happens in the future.
I am actually waiting on a battery, (ordered before I got the phone) and so will try that to see if anything changes.
Thanks again everyone. I've got a feeling I might have to write this one off pretty soon.
ChiqOmar said:
Hello everyone,
I seem to be facing a singular issue, but I imagine it is much my fault, and just wanted a confirmation from those more experienced with the device...
I bought an Incredible 4G from eBay, that already had the a copy of Avatar on it, I believe almost the latest update. So when I confirmed the device worked after charging the battery, I flashed the latest copy of Avatar and the JB Gapps, and everything seemed hunkydory.
So, after that, I put in my old SIM, deactivated as I was using a non-4g device, and put it in the Incredible 4G. I started the activation process on the phone, following prompts to reboot the phone (Note: I did not know about CM10.1's issue regarding activation at the time, so one of the possible problems.)
After seemingly failing to activate after the first reboot, I "tried again" and it went down for another reboot. And it stayed down. Completely. I cannot get the phone to start, after charging the battery separately, cannot get into bootloader, nothing. I get QHSUSB_DLOAD when plugged into a computer using USB, but that's it.
A few notes: first time I started up, the screen went to recovery. I didn't think that was an issue; I factory reset from there, and rebooted into Avatar. Second issue: I used ROM updater on the phone to download and install the recovery, as I imagined that there was an automatic checksum done in the process (perhaps it was imagined?), and so when it went to flash, it had some issue, which didn't seem like a problem with the download, and I went through flashing it normally through recovery. Sorry I can't provide more details on that, but everything seemed to work all right after rebooting.
Finally, and this may be irrelevant, I put a 64GB SDXC card in the phone, I had already realized that it could not natively support exFAT, and so left the card in the device until the next time I could boot to recovery to partition it, and went through the activation process with the card inserted and not recognized.
So, I imagine that I have a hard brick, but can't tell if it's completely my fault, because it bricked in a peculiar fashion, at least from what I can tell, as no one seems to have encountered a similar issue after searching for the last 5 days.
If there's any hope for recovery, I would really appreciate some help regarding the device. I'm willing to provide some more info if necessary, and I'd like to find out sooner rather than later if it's a lost cause.
Thanks for any help you guys can give. XDA devs are awesome.
Click to expand...
Click to collapse
Just got same issue, though for me I installed avatar rom, then rebooted at some point, but instead it hard bricked, can't charge pull battery out/in boot back up removed sim sd card didn't help me either. Any progress yet, or help?
Ill try to get a working htc unbriking Project soon for you guys to try, both please use ubuntu and have a working USB cable, I'm gonna try to reinstall hboot, also have teamviewr installed, also please tell me if you guys are supercid, also no usb 3.0 cable or port please
Sent from my ADR6410LVW using xda app-developers app
Some Information
jose51197 said:
Ill try to get a working htc unbriking Project soon for you guys to try, both please use ubuntu and have a working USB cable, I'm gonna try to reinstall hboot, also have teamviewr installed, also please tell me if you guys are supercid, also no usb 3.0 cable or port please
Sent from my ADR6410LVW using xda app-developers app
Click to expand...
Click to collapse
I'm on Ubuntu 13.04 64 Bit, I have a usb cable, Anker Battery Expert separate battery charger. And my Phone is S-OFF DirtyRacun Currently still hard bricked (Not by the Racun though) don't have any 3.0's, i have a onn usb cable and the stock, I also have a Ubuntu 12.04.2 LTS 32 Bit Live DVD. Battery Charging using a battery pack charger. Won't charge through USB
OldNut5 said:
I'm on Ubuntu 13.04 64 Bit, I have a usb cable, Anker Battery Expert separate battery charger. And my Phone is S-OFF DirtyRacun Currently still hard bricked (Not by the Racun though) don't have any 3.0's, i have a onn usb cable and the stock, I also have a Ubuntu 12.04.2 LTS 32 Bit Live DVD.
Click to expand...
Click to collapse
pm me with gtalk email and ill see what i can do, also install teamviewr
OldNut5 said:
I'm on Ubuntu 13.04 64 Bit, I have a usb cable, Anker Battery Expert separate battery charger. And my Phone is S-OFF DirtyRacun Currently still hard bricked (Not by the Racun though) don't have any 3.0's, i have a onn usb cable and the stock, I also have a Ubuntu 12.04.2 LTS 32 Bit Live DVD. Battery Charging using a battery pack charger. Won't charge through USB
Click to expand...
Click to collapse
I lost my first Dinc 4G LTE after I installed CM10.1, was working great for a while and just blinked off, never to recover. No charge light, no response to power button. I also had an aftermarket battery (Hyperion), but it would get so hot charging I replaced it with an OEM HTC battery. I think that damaged the phone.
Since I work with analog electronics, I assume something in the power path physically burned out. I never tried to talk to it via USB, but just cabling it to a computer generates no response.
I went back to the Stock RUU.zip from the unlimited.io site to get the firmware update. During the update it just sort of died. Now I can't get it to charge or get into the bootloader. Help! Please!:crying:
Ok, so please forgive me for this. I'm used to Samsung devices, and rooting/custom recovery is as simple as "Download this, flash through Odin, Easy as pie".
So I have my brother's P769. He had rooted it, but was unsure how to install CWM on it. Me, being completely ignorant of unlocking the bootloader, was able to get CWM on it and flash CM10.2. Which, of course, gave me the LG Security Error. Been stuck for many a day trying to get back to V20F_00. It doesn't help that there is ABSOLUTELY NO WAY to install the omap4 drivers in Windows 8.1, and reserving USB devices to Virtualbox is a pain in the (insert desired graphical descriptor here:_______).
So, I am just trying to clarify the steps to get my brother the CyanogenMod he so desires.
From Stock:
Root device
Unlock Bootloader
Install CWM
Flash CM from CWM
Is this a correct assumption?
jparnell8839 said:
Ok, so please forgive me for this. I'm used to Samsung devices, and rooting/custom recovery is as simple as "Download this, flash through Odin, Easy as pie".
So I have my brother's P769. He had rooted it, but was unsure how to install CWM on it. Me, being completely ignorant of unlocking the bootloader, was able to get CWM on it and flash CM10.2. Which, of course, gave me the LG Security Error. Been stuck for many a day trying to get back to V20F_00. It doesn't help that there is ABSOLUTELY NO WAY to install the omap4 drivers in Windows 8.1, and reserving USB devices to Virtualbox is a pain in the (insert desired graphical descriptor here:_______).
So, I am just trying to clarify the steps to get my brother the CyanogenMod he so desires.
From Stock:
Root device
Unlock Bootloader
Install CWM
Flash CM from CWM
Is this a correct assumption?
Click to expand...
Click to collapse
Welcome JP,getting a break from the Blaze. I've had this beast for a week and I'm ready to crush the phone. So far I've been able to root and remove T-Mobile bloatware.
I've tried to unlock the boot loader many times and no luck. I've read thru the guides and the result is the same.
I sitting patiently to see if the devs can solve the mystery of the bootloader. I can't wait for the day so I can leave the stock Rom. Hope all is well
Sent from my LG-P769 using xda app-developers app
I've had this phone almost a year. As far as the unlocking bootloader goes, it seems like some p769s just aren't unlockable, no matter what method used. Mine is one of those. It may never be able to be unlocked. Just throwing that out there.
THIS link will show you the most common way to unlock the bootloader. It has simple directions and even a video. The only problem is that it doesn't work on some devices, such as mine, so just be wary. And many people in the thread have managed to get results by modifying the instructions, but others have not had any luck.
Good luck! Hope yours works
Welcome to the dark pits of xda hell....LMAO! :sly:
Sent from my LG-P769 using XDA Premium 4 mobile app
LaDY Vengeance said:
Welcome to the dark pits of xda hell....LMAO! :sly:
Sent from my LG-P769 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
This is as bad as when I had the Cliq XT , that was a beast as well. That was a replacement phone as well. Hopefully the devs can crack it
thehritzinator said:
I've had this phone almost a year. As far as the unlocking bootloader goes, it seems like some p769s just aren't unlockable, no matter what method used. Mine is one of those. It may never be able to be unlocked. Just throwing that out there.
THIS link will show you the most common way to unlock the bootloader. It has simple directions and even a video. The only problem is that it doesn't work on some devices, such as mine, so just be wary. And many people in the thread have managed to get results by modifying the instructions, but others have not had any luck.
Good luck! Hope yours works
Click to expand...
Click to collapse
That's the link I found, and thought "There's no way it's that complicated!"
HTC uses a dev key. I don't remember Moto's method, but it was simple. Samsung is ridiculously simple. Why is LG so complicated? This has only re-enforced my idea of "Never get an LG"
LaDY Vengeance said:
Welcome to the dark pits of xda hell....LMAO! :sly:
Sent from my LG-P769 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Lol thanks! I'm starting to believe it
flyers00 said:
This is as bad as when I had the Cliq XT , that was a beast as well. That was a replacement phone as well. Hopefully the devs can crack it
Click to expand...
Click to collapse
This is the worst phone, as far as modding goes, I've ever seen. I haven't experienced many devices, but geez. Heck, hacking a SGS2 i777 with a faulty USB board was easier than this, and I couldn't even access recovery without ADB commands (because it thought a USB cable was plugged in even when it wasn't, was going to download mode) and couldn't enable ADB (because it thought a cable was plugged). I had to use SQLite hacks to force ADB to enable.
However, I've never let anything stop me before. I'm a world-champion Googler, and so I will crack this will probably take me a while, but meh.
jparnell8839 said:
That's the link I found, and thought "There's no way it's that complicated!"
HTC uses a dev key. I don't remember Moto's method, but it was simple. Samsung is ridiculously simple. Why is LG so complicated? This has only re-enforced my idea of "Never get an LG"
Lol thanks! I'm starting to believe it
This is the worst phone, as far as modding goes, I've ever seen. I haven't experienced many devices, but geez. Heck, hacking a SGS2 i777 with a faulty USB board was easier than this, and I couldn't even access recovery without ADB commands (because it thought a USB cable was plugged in even when it wasn't, was going to download mode) and couldn't enable ADB (because it thought a cable was plugged). I had to use SQLite hacks to force ADB to enable.
However, I've never let anything stop me before. I'm a world-champion Googler, and so I will crack this will probably take me a while, but meh.
Click to expand...
Click to collapse
Congrats on coming into teh darkside. I know you are world class Googler and if you find something or come up with something, I am in to help the cause. I was a guinea pig with the Blaze so why not here. Good luck with your Google skills
I was given a htc DNA and it's been one headache after another. It had a cracked digitizer, s-off, eng hboot, unlocked boot loader and a custom recovery installed on it when it was given to me. Trying to make a long story short, I ended up having to replace the board with the sim card reader on it and immediately after putting the new board in the cameras quit working along with the speakers and microphone. I was able to get all but the cameras working, but then I bricked it, and here is how. I was attempting to return back to stock, relocked the boot loader, was attempting to use a ruu which wasn't working, so I decided to unlock my boot loader again. The story ends with me attempting the unlock with ez-unlock, and when I did it said successful and I was able to keep using the phone as normal, but after turning the phone off it wouldnt turn back on, and the only sign of life comes when I plug it into my computer. As soon as i connect it to my computer, htc sync manager opens up but says no phone connected, device manager will show the phone as my htc and android 1.0.. I've experienced similar signs of life from an htc vivid, but it's issues were due to a bad battery, so I am hoping for the best but expecting this to end with jtag. Can anybody help me out please, it would be great to not require jtag services, but it would be better yet if I could gain a better understanding of at least what went wrong. Thank you
TELE-FLASH said:
I was given a htc DNA and it's been one headache after another. It had a cracked digitizer, s-off, eng hboot, unlocked boot loader and a custom recovery installed on it when it was given to me. Trying to make a long story short, I ended up having to replace the board with the sim card reader on it and immediately after putting the new board in the cameras quit working along with the speakers and microphone. I was able to get all but the cameras working, but then I bricked it, and here is how. I was attempting to return back to stock, relocked the boot loader, was attempting to use a ruu which wasn't working, so I decided to unlock my boot loader again. The story ends with me attempting the unlock with ez-unlock, and when I did it said successful and I was able to keep using the phone as normal, but after turning the phone off it wouldnt turn back on, and the only sign of life comes when I plug it into my computer. As soon as i connect it to my computer, htc sync manager opens up but says no phone connected, device manager will show the phone as my htc and android 1.0.. I've experienced similar signs of life from an htc vivid, but it's issues were due to a bad battery, so I am hoping for the best but expecting this to end with jtag. Can anybody help me out please, it would be great to not require jtag services, but it would be better yet if I could gain a better understanding of at least what went wrong. Thank you
Click to expand...
Click to collapse
You can't boot into anything? Not even bootloader mode?
.torrented said:
You can't boot into anything? Not even bootloader mode?
Click to expand...
Click to collapse
Sadly no, I can't get it to boot at all. I also need to mention that the lights don't come on when it's plugged in either. I'm thrown for a loop by it all because my computers will still react to it if I hook it up to them with usb, but that's about all they will do. Why would sync manager open up when I plug it in, but then state that there is no device connected.
Ive seen where people have said to leave phone charging for 24 hours without trying to turn it on and it worked. I've also seen people run a calibration test on the battery but I forgot how to do it.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
EZ-Unlock is an unsupported method by the DNA hardware. It will always cause a hard-brick. Which you have done. I did this to myself at one point, too. I tried EZ-Unlock and it hard-bricked my DNA. Call Verizon. Tell them that it just randomly started doing this. Don't mention root or anything. They'll replace it for free. That's what I did.
Sorry about that bud. Try to do some more research before modding your phone next time.
TELE-FLASH said:
Sadly no, I can't get it to boot at all. I also need to mention that the lights don't come on when it's plugged in either. I'm thrown for a loop by it all because my computers will still react to it if I hook it up to them with usb, but that's about all they will do. Why would sync manager open up when I plug it in, but then state that there is no device connected.
Click to expand...
Click to collapse
Oh I see.
ryanguy426 said:
EZ-Unlock is an unsupported method by the DNA hardware. It will always cause a hard-brick. Which you have done. I did this to myself at one point, too. I tried EZ-Unlock and it hard-bricked my DNA. Call Verizon. Tell them that it just randomly started doing this. Don't mention root or anything. They'll replace it for free. That's what I did.
Sorry about that bud. Try to do some more research before modding your phone next time.
Click to expand...
Click to collapse
Or, he could so kindly ask Zarboz to jtag it for him and fix it possibly. I'm not saying he will jtag it but he does jtag work, so if you want to know more you should pm him about it.
Yeah I forgot Z could JTAG it... Thanks for posting that. I am sure that he will be more than happy to JTAG it for him.
Sent from my HTC Droid DNA using XDA Premium 4 mobile app
Can you get into the bootloader by holding power+volume down for any amount of time?
Have you let it sit on the charger over night?
Hold power down for at least 20 seconds to a minute?
Sent from my HTC Droid DNA using XDA Premium 4 mobile app
.torrented said:
Oh I see.
Or, he could so kindly ask Zarboz to jtag it for him and fix it possibly. I'm not saying he will jtag it but he does jtag work, so if you want to know more you should pm him about it.
Click to expand...
Click to collapse
Well thank you for your feedback, and assistance. I owe most everything I know about phones to XDA and it's members! Regarding my situation with the DNA, yup sure enough it is bricked. I figured it was, but have had similar reactions from a bad battery in the past, so.. Regarding the process of unlocking the boot loader, this is the first time I've ever directly seen anything regarding the cid. Not sure if maybe it has been part of the process in ways that I was unaware of in the past with other phones or if this is more device specific, but either way would anybody possibly know where I could find more in depth information regarding this and if there is anybody who is knowledgeable with this that wouldn't mind helping somebody out?
sorry for the run on sentences lol
oh, and thank you for the referral to Zarboz, I will definitely be getting in touch with him.
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.