Related
I have a Sprint Mogul running DCD 3.3.4, which I've been using for months. I was listening to a podcast (Buzz Out Loud) via BT headset last night. I paused the podcast via the headset and when I tried to restart it found my Mogul to be in Bootloader (Olipro 2.40). hard, soft resets and puled battery did nothing. Since getting home I tried to connect via usb and get a Windows failed device warning, so titan_exitbl is out. I tried to flach DCD 3.3.4 via sd and the grey loading screen comes on briefly then it returns to the bootloader screen. I also tried re flashing the radio and that doesn't even get a loading. Is there anything I'm missing that I haven't already tried? I'm out of warrenty and I don't have insurance. I've had good success with Sprint, getting 2 replacements when the junk usb port in this phone failed, but I fear I'm pushing my luck. I really hoped that this unit would last till at least the TP2 came out! Andy assistance is greatly appreciated!!!
are you trying to flash with an SD card?
You may be able to flash the current stock Rom from Sprint via sd card as it includes bootloader. It would wipe your device clean and you can start from scratch.
Hope something works for you.
jph8tr said:
I have a Sprint Mogul running DCD 3.3.4, which I've been using for months. I was listening to a podcast (Buzz Out Loud) via BT headset last night. I paused the podcast via the headset and when I tried to restart it found my Mogul to be in Bootloader (Olipro 2.40). hard, soft resets and puled battery did nothing. Since getting home I tried to connect via usb and get a Windows failed device warning, so titan_exitbl is out. I tried to flach DCD 3.3.4 via sd and the grey loading screen comes on briefly then it returns to the bootloader screen. I also tried re flashing the radio and that doesn't even get a loading. Is there anything I'm missing that I haven't already tried? I'm out of warrenty and I don't have insurance. I've had good success with Sprint, getting 2 replacements when the junk usb port in this phone failed, but I fear I'm pushing my luck. I really hoped that this unit would last till at least the TP2 came out! Andy assistance is greatly appreciated!!!
Click to expand...
Click to collapse
Make sure the MicroSD card is less than or equal to 2GB, formatted for FAT, and that the file is titled TITAIMG.nbh
My mistake - it should be formatted FAT32.
serfboreds said:
You may be able to flash the current stock Rom from Sprint via sd card as it includes bootloader. It would wipe your device clean and you can start from scratch.
Hope something works for you.
Click to expand...
Click to collapse
Thanks, it got me close but no cigar. I was able to get the update (3.37) to complete, but it reboots to the SPL-2.40 screen. I'm having the sad revilation that this Mogul is a brick and I'll have to throw myself at the mercy of Sprint support. wish me luck! Anyone know how to revert to a stock (2.07?) bootloader without usb or fully functioning device?
Have you tried to flash back to 2.07 bootloader yet?
I've recommended that friends have unlocked their phone and their biggest concern is usually that if the bootloader install bricks the phone then they can't get the stock software on there again so that they can bring it in for repair.
Personally, I suggest that they just bring me their phone if that happens and I'll hook it up to the DC generator in my workshop and the device will experience an electrical problem. I guess with the new insurance changes, that you don't want to just throw it and show any physical damage.
Luckily I've never needed to do this, as we haven't made any bricks. However, there are so many ways to ensure that the carrier doesn't boot the device into some non-stock boot loader.
It sounds to me like your device's memory has failed. I doubt they'll be able to fix it anyway. However, have you tried the TITAIMG.nbh from the nueSPL Relocker on your FAT formatted SD card?
bitserve said:
I've recommended that friends have unlocked their phone and their biggest concern is usually that if the bootloader install bricks the phone then they can't get the stock software on there again so that they can bring it in for repair.
Personally, I suggest that they just bring me their phone if that happens and I'll hook it up to the DC generator in my workshop and the device will experience an electrical problem. I guess with the new insurance changes, that you don't want to just throw it and show any physical damage.
Luckily I've never needed to do this, as we haven't made any bricks. However, there are so many ways to ensure that the carrier doesn't boot the device into some non-stock boot loader.
It sounds to me like your device's memory has failed. I doubt they'll be able to fix it anyway. However, have you tried the TITAIMG.nbh from the nueSPL Relocker on your FAT formatted SD card?
Click to expand...
Click to collapse
I think the problem was caused by the usb port, it had been flaky for over a month, though no bent pins this time. I could get the update via sd to complete, but it would return to the bootloader. I went into a Sprint repair center, they didn't even look too closely at the screen. Unfortunately, they had Moguls so no TP for me. This is now my 4th Mogul, all have had white spots, 1 had a failing keyboard and right now 3 out of 4 have had failed usb ports. I've owned ~8 PDA's and maybe 14 cell phones in my time and the Mogul is officially the worst made electronic device I have ever owned.
Well I'm on my first Mogul and I use it quite a lot, including the USB. Haven't had any problems except for the low memory.
jph8tr said:
Thanks, it got me close but no cigar. I was able to get the update (3.37) to complete, but it reboots to the SPL-2.40 screen. I'm having the sad revilation that this Mogul is a brick and I'll have to throw myself at the mercy of Sprint support. wish me luck! Anyone know how to revert to a stock (2.07?) bootloader without usb or fully functioning device?
Click to expand...
Click to collapse
also, if you have not figured it out already, you MUST set the allocation size to 1024. leaving it on DEFAULT will not work.
In windows XP you might have to go into the disk management settings to do this, as a "quick format" from the right contextual menu will NOT work. I struggled with this several days ago, and located that solution. At that point the TITAIMG in the SD card loaded properly.
At the "Default" allocation size, it would brielfy flash a "loading" screen, then go back to the rainbow flag screen.
anthonyandrews said:
also, if you have not figured it out already, you MUST set the allocation size to 1024. leaving it on DEFAULT will not work.
In windows XP you might have to go into the disk management settings to do this, as a "quick format" from the right contextual menu will NOT work. I struggled with this several days ago, and located that solution. At that point the TITAIMG in the SD card loaded properly.
At the "Default" allocation size, it would brielfy flash a "loading" screen, then go back to the rainbow flag screen.
Click to expand...
Click to collapse
Thank you for your help! For the record, I'm moderately adept at the upgrade thing, I've flashed off this card at least 15-20 times. My best guess (and it is pure guess!) is that the loose USB port dislodged while the phone was charging caused something to fry. I had some indications that all was not right, the phone was hard to sync (had to get the plug inserted just right), it had rebooted a few times for no reason recently and the upper "mail" and "net" button back lights would sometimes stay on even when the phone was off. I was able to get a stock rom to appear to go through a flash, but it would return to the bootloader. I had the Mogul swapped out and used the same card to flash the "new" phone without issue. Fortunately, I use Sprite Backup nightly making restoration a snap, Unlock> radio> ROM> carrier CAB> b/u restore. I did have to re connect my BT devices, for some reason they don't completely reconnect after a b/u restore. My phone was back to normal in less than 15 min. It's nice to have my phone back, but my opinion of it now is that it's a unreliable piece of crap that I can't wait to replace. Thanks again for the assistance!
Some days ago, my o1 fell down but it doesn't semmed to have broke anything. The phone was acting perfectly normal.
Yesterday, i tried to charge it via AC and USB but none of those had any effect. I tried diferrect cables, different computers and wall sockets. None worked. Also, no computer detected the phone.
I tried different roms (G-T-R and PerfectPeso). Adb didn't recognized it neither did the kdz updater (was trying to get back to stock rom).
However, i discovered that the battery can be charged if the phone is in emergency mode, and this is why i haven't lose my hope yet (if it can be charged this way it means it might not be a hardware problem, right?)
Help, guys, don't know what else i can try.
Sorry about my English.
Thank you.
Renan_S said:
Some days ago, my o1 fell down but it doesn't semmed to have broke anything. The phone was acting perfectly normal.
Yesterday, i tried to charge it via AC and USB but none of those had any effect. I tried diferrect cables, different computers and wall sockets. None worked. Also, no computer detected the phone.
I tried different roms (G-T-R and PerfectPeso). Adb didn't recognized it neither did the kdz updater (was trying to get back to stock rom).
However, i discovered that the battery can be charged if the phone is in emergency mode, and this is why i haven't lose my hope yet (if it can be charged this way it means it might not be a hardware problem, right?)
Help, guys, don't know what else i can try.
Sorry about my English.
Thank you.
Click to expand...
Click to collapse
best solution: lg service center
Sent from my LG-P500
Well, i went to the nearest authorized technical support and after some time waiting i was told that it may be a software problem and that it would cost me a value that ive calculated to be greater than 25% of the money i've originally paid to buy the phone. Also, for "some reason" the technician couldn't run his repair software.
Tried flashing a rom with a different version of android (CM9), it didn't work. Discovered that i can't restore, in a nadroid backup, the cache partition or the sd-ext partiton (i'm not sure of wich one), or i'll have bootloops.
Really, should i give up?
WHATEVER HAPPENS INSIDE YOU PHONE DOESNT MATTER AT ALL MAIN POINT IS THAT IT SHOULDNT BE VISIBLE
IF THIS IS YOUR CASE GO ,GO TO LG PEOPLE AND SAY please repair it
This is the best method adopted by any dev to overcome any majour problem in our beloved optimus one
njoy
EDIT :
I think you shouldnt get it repaired if its costing more than 25% as its technology is now very old and its not worth that much
Save some money and buy a new android phone
Well, i'm kinda out of options now, since i was stolen today and my O1 was taken from me =\
Btw, tha Plan B app really works???
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:
[Q] "Retroactive Bricking" or "spontaneous" hardware fault? [Xpost One X/X+ Help]
*PSA: This will be crossposted in xda GenerAL Q&A and HTC One X+ forums, I hope cross posting is allowed, haven't seen it mentioned in rules.*
Hi all,
Quick disclaimer: I've been lurking parts of xda now and again for a couple years now, have flashed a couple of phones and tablets now and again for mainly practical reasons, recently getting more interested in it as a ""fun" interest or "hobby".
SO: I am very aware that this is my first post, the rules, search function, etc. ..
BUT: After extensively searching both google and specifically xda to help me resolve this issue *myself*, I decided to create an account and post. I'm sorry if this Q should have been put in the newbie thread, my assessment was that it probably has no place there.
ALSO PLZ NOTE: What was meant to be a succinct summary and question somehow turned into a condensed but complete rundown of events, so here is a...
TL;DR:
- Replaced HTC One X+ display/digitizer unit myself, ran fine for 5 weeks.
- Then: flashed twrp 2.7x or 2.8, not sure anymore, before installing Android HD Revolution 33.1 by mike1986, and following the official instructions, which ran great for about week until my phone spontaneously BRICKED THE F*CK OUT COMPLETELY.
(yes, true brick, paperweight, robot-corpse, whatever)
=> Question: IS "RETROACTIVE/RETROGRADE BRICKING POSSIBLE/A "THING"??
If so, what could I have done wrong? (POSSIBLY something to do with a bootimage of firmware that I was sure I had the up to date version of... dunno though).
=========================================================================
About 6 weeks ago:
- Cracked the display of my HTC One X+ badly by dropping it onto concrete-type floor at a rave/party
=> Decided to try and replace it myself, researched for a good while (talking several days here, 90s/00s kids),
=> Decided to replace the display/digitizer unit myself to save money and gain knowledge.
Repair process was challenging and nearly as nerve wracking as playing the WSOP (not kidding, have played it three times), had an issue immediately after putting it back together where it suddenly wouldn't charge AT ALL anymore (NO LED), and overheated, and had unusually fast battery drain of its remaining charge (which never ran out completely before resolving that issue, since I kept turning it off whenever possible).
=> Took it apart and put it together again XX times until realizing the power switch flex cable kept slipping out of its two (jawbone?) connectors during putting it back together (I was doing something wrong with the flex positioning).
=> This resolved the issue.
=> Felt like a hero and that I win at life (since this phone has a rep as being hard to meddle with, and this was my first time even opening, let alone taking apart a smartphone).
=> Continued joyful phone shenanigans for over one month.
=> THEN: Decided to root it, mainly because there was a particular app I wanted that required root ("Quick reply for Whatsapp/Pushbullet", for the curious).
My previous, very limited rooting/flashing experiences =
- Google Nexus One (CWM/Cyanogen) a few times, years ago
- Galaxy Tab 10.1 (CWM/Cyanogen 10.1 ages ago, TWRP/Omnirom Kitkat 4.4.4 recently) a couple times.
So, did my research (or so I thought..?) for this particular custom ROM, decided to go for Android Revolution HD for HTC One X/+ 33.1 by mike 1986 (because it looked fckin awesome, and it was, while it ran) and loved the sh*t out of my "new" phone for about a week. Especially the vastly improved battery life seemed almost surreal, a big deal for a fixed-battery phone.
Then, ONE FATFUL EVENING in a bar, I remember looking at my phone and seeing 35% left, (days before it would've been an amazing 70-80% on an avg. day), which may not be relevant as it was my birthday, so had been using it a lot that day => may be a moot point
- Next time I looked at the phone ( < 1 hour without active use for sure) it was dead.
"Hmmmm," thought slightly drunk me. Whatever, charge it later, weird sh*t happens.
- Got home later, charged it over night after booting it with usb cord attached (mains).
Seemed normal, I even set an alarm.
=> Alarm never rang because it was in a powered-off state again come morning, despite all-night charging.
=> It booted to HTC logo. Seconds later, it turned off again. Held down power again, all I saw was the soft touch buttons flashing red a few times. After this it unexpectedly became (or was secretly crowned):
!! COMPLETE AND UTTER FCKNG KING BRICK OF BRICK COUNTRY AND ATTACHED TERRITORIES !!
No power on with or without volume up/down held for whatever amount of time;
No charging, no heating up when "charging";
No LED in any colour or flashing frequency, ever;
No response after hours and days of charging on different USB cables on PC/wall socket;
PCs and laptops don't register a sign of anything when it penetrates their port parts, etc etc...
...
.Even that semi-mystical bright-light-exposure-while-charging "light sensor manipulation" thing (which apparently worked for a lo of people with similar issues) did nothing for the cause.
Promotion: *Paperweight status successfully acquired.* Yay.
=====================================================
Now, obviously my first thought was that the power flex that gave me trouble during display replacement probably slipped again., somehow (I had taped it down solidly I thought).
=> SO I opened it once again, flex position seemed ok, but I wasn't sure of its functionality as it did look kind of battered from the somewhat unprofessional repair I had conducted on it (which I openly admit to, though I really did try my absolute best).
- Spontaneously took mainboard/battery combo to a local independent phone/accessory shop after being told they'd take a look for free
(I was in there was in there buying a microsim adapter so I could use my ancient Nexus One, since my GF has my old S2 now, which she kindly offered back, but its hers now, so nah. Great phone though.)
=>Shop's advice echoed my thoughts: Flex cable may be screwed, I may have damaged it by bending in the wrong direction/too often, and that damage somehow didn't manifest until much later. I didn't mention the recent rooting + flashing as I deemed it irrelevant at the time.
Their secondary thoughts: Battery or mini-usb port fukt, (which would require soldering, which they don't even offer).
=> SO, feeling confirmed in my layman's assessment, I cheaply got a pristine new replacement flex on ebay, double checked all videos/tutorials, implemented the damn thing with considerably more skill/experience and even higher anticipation. What happened next was shocking:
Absolutely nothing, obv.
=> Did an additional epic f*ckton of internet/forum research, found similar problems and some resolutions, but no real answers, probably because my main problem translates to a kind of hybrid question.
So here I am now am with my core question:
Is it possible to FULLY brick an HTC/any smartphone but not become aware of this until one week later, when the device dies OVER ONE WEEK of reliable and amazing performance?
(and if yes, what aspect/stage of the flashing process is this likely related to?)
If the answer is NO, it must be a hardware fault with probability rank (I think)
:
1.) Battery dead for whatever reason
2.) Mini USB OR mainboard/integral component (equal rank as not sure), possibly caused by incompetent repair, but why or how would this express itself over a month later??
3.) Other, which I'm not aware of.
While researching new ROMS for the N1, I realized that I may have messed up on the "bootimg part" of the flashing process of the Revolution ROM, a part I found v. confusing in the instructions, even after rereading them many, many times. It was about the most recent firmware, which I was pretty sure I had anyway, since it was unrooted before and I do remember installing some firmware updates over the air.
I still did my best to follow the instructions though.
=> Maybe this has something to do with it, i.e. the hardware can't accept a charge because the software allowed it to become too uncharged (a fairly paradox concept to me, but apparently it can happen. Guess it's like a BIOS-type thing).
Thank you for anyone who read this far!
As it stands, I refuse to give up hope so soon after experiencing that rush of having fixed it myself.
Any specific or general help, tips, hints, pointers, replacement phones (One M8 or S5 plz., Iphones will go straight on ebay) would and will be greatly appreciated!!
The obvious choice is to get a new battery and see what happens, but I'm not sure if I wanna sink any more money into this phone, only to later find out the mainboard is at fault (not worth the money replacing), AKA "get a new phone without a contract", which would more than suck for me financially atm (Im ignoring my N1 here, which I love, but don't wanna be stuck with, esp. as it has the standard-issue broken power button (which I actually had repaired once under warranty, back in the ol' days of yore some prefer to refer to as 2009.
So guys: What's my move, if there is one, besides going to a local/online service centre (I live in Germany btw.) and probably paying unproportionate cash money to even have it looked at?
Cheers, thanks, merci, danke
PS: Just saw the polling function, so I attached one just for the hell of it, to see what happens (never used one before).
If you feel both qualified AND so inclined as to pass judgement on this here serious business, please indicate what you think may be the cause of my issue.
Poll is in "General QA" Forum original post: http://forum.xda-developers.com/general/help/retroactive-bricking-spontaneous-t2948954
*BUMP 1*
Come on guys, I know it's a wall of text, but can't someone at least answer the TL;DR?
=> Is is possible to flash a custom rom which then (possibly because of improper installation) causes the phone to brick about a week later?
Simple question surely!
bear.are.cool. said:
*BUMP 1*
Come on guys, I know it's a wall of text, but can't someone at least answer the TL;DR?
=> Is is possible to flash a custom rom which then (possibly because of improper installation) causes the phone to brick about a week later?
Simple question surely!
Click to expand...
Click to collapse
Oh yea I was meant to reply to this... Reading what I can of this, sounds like offmode charging wasn't working (Sounds like to me not 100% is it)
You can try this http://forum.xda-developers.com/showthread.php?t=2576405 <--- Windows only
That is a last ditch attempt at charging....Which is what it sounds like to me, please tell me If I'm wrong.
And NO, providing your device is S-ON you CANNOT BRICK IT
thanks
Lloir said:
Oh yea I was meant to reply to this... Reading what I can of this, sounds like offmode charging wasn't working (Sounds like to me not 100% is it)
You can try this http://forum.xda-developers.com/showthread.php?t=2576405 <--- Windows only
That is a last ditch attempt at charging....Which is what it sounds like to me, please tell me If I'm wrong.
thanks
Click to expand...
Click to collapse
Thanks for the reply!
I believe I actually ran into that (linked) post during my previous research, but just as is the case now, I don't get how I'm supposed to run a .bat from windows that influences the phone when windows doesn't recognize a thing when I plug the device in. Not in device manager, NADA.
EDIT: I do have S-ON, yes. BTW thanks for trying to help, but again, my fundamental question: Is "retroactive bricking" as I call it possible in theory?
bear.are.cool. said:
Thanks for the reply!
I believe I actually ran into that (linked) post during my previous research, but just as is the case now, I don't get how I'm supposed to run a .bat from windows that influences the phone when windows doesn't recognize a thing when I plug the device in. Not in device manager, NADA.
EDIT: I do have S-ON, yes. BTW thanks for trying to help, but again, my fundamental question: Is "retroactive bricking" as I call it possible in theory?
Click to expand...
Click to collapse
To get it working you need the android sdk tools. You also need to install HTC SYNC + Drivers then uninstall HTC sync leaving the drivers behind.
And In answer to your Q. No
After reading the TL;DR
Lloir said:
To get it working you need the android sdk tools. You also need to install HTC SYNC + Drivers then uninstall HTC sync leaving the drivers behind.
And In answer to your Q. No
After reading the TL;DR
Click to expand...
Click to collapse
Hmm, ok. I'll give it a go. So essentially, if I manage to implement this method correctly and I still get nothing, theres gotta be a hardware fault, correct?
bear.are.cool. said:
Hmm, ok. I'll give it a go. So essentially, if I manage to implement this method correctly and I still get nothing, theres gotta be a hardware fault, correct?
Click to expand...
Click to collapse
Probably
Sent from my Nexus 7 using Tapatalk
Lloir said:
Probably
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
I'm trying to find a good guide on how to go through with this, as the post you linked is helpful but a bit vague.
One more question: When you say "offmode charging" is that synonymous with "offline charging"?
EDIT: Also, what I really do not get about the procedure outlined in the post is the following line
"Run the following script as a batch file while your phone is in USB fastboot mode."
=> How do i put this brick into anything mode?? It's in constant brick mode!
bear.are.cool. said:
I'm trying to find a good guide on how to go through with this, as the post you linked is helpful but a bit vague.
One more question: When you say "offmode charging" is that synonymous with "offline charging"?
EDIT: Also, what I really do not get about the procedure outlined in the post is the following line
"Run the following script as a batch file while your phone is in USB fastboot mode."
=> How do i put this brick into anything mode?? It's in constant brick mode!
Click to expand...
Click to collapse
Just a question. When you replaced the display, did you tamper with brightness control? I mean were you able to change the brightness after your repair?
And secondly, logically, I think its a hardware fault. Whatever happened, might have happened over the week or happened that specific day. Maybe the wire connecting the charger socket to the phone's board got cut/damaged during repair but worked for a while, then it imght have touched another wire and short circuited maybe?
Or maybe something inside was loose, and something happened to the phone, it fell or something, and a component got broken?
I would suggest comparing your internals to the internals of another HOX+ whether on youtube or whatever. And try to check the wire connecting the charger socket to the board. Another possibility is the battery got damaged as you stated. The last idea is, (And I hope it didn't get to that), the wire short circuited and fried the board.
All my theories are just as stated.. Theories, which may or may not be true. If there is an HTC Care center, I would suggest that you go to them, atleast for debugging.
Best of luck
Title says it all. I can't download any large apps, download from the browser. I can sideload my apps straight from google drive. I need a physical SD card to download files from the internet, and to download large apps, like VOEZ. Moving on, there is another issue I have with my unit. USB. I plugged it into my computer many times, and it just never finds it. I was once able to look at the files on the device with ADB enabled, but when I opened up a Windows VM (I run Ubuntu) and fired up Kingroot but could not find it, so I unplugged, and plugged it in again, only to lose the data connection over USB, and only charged from then afterwards. After this, I knew that the USB port was perfectly OK, so there was no damage or any issue to the port itself. When I had this phone as my sole daily driver before I had switched to my iPhone, it was neglected heavily (by me) because of these abhorrent issues that drove me insane. I now want to put some life back into this thing by rooting it, which was my goal from day 1 when I had gotten it, but these issues made such practically impossible. So, with the ramble out of the way, can someone find a way to fix this this internal storage and USB issue? I'd love to give it a chance once again. Oh, and I got this phone for free from a "government lifeline" program, which has its Androids completely restricted in a way where rooting is hard to achieve, but possible.
Model #: PG86100
Before this phone, or even my 6 Plus, I had a N5, which now has a broken display/speaker ZIF connector on the mainboard. I just wanted to point out that this was not my first android, and would really love to relive the days that I had with my N5 before it died.