Related
For anyone searching this problem, the easiest solution (all thanks to Fallen4u) is to purchase ($4), download, and install Camera 360 Ultimate (Pro version no longer available on Market, afaik). This will basically replace your broken camera software (where it just sits on "please wait" - until the cows come home after jumping over the moon) with working software that brings camera back to life. This solution does not require resetting phone which does NOT guarrantee camera software will work with the Froyo 2.2 (I think it's called Froyo, anyway. I know it's the 2.2 update). So, if you have lots of software, don't want to mess with flashing this that or whatever, just save yourself the time and trouble and download the above mentioned software. Problem fixed. It also gives you many more fun possibilities from what my lady friend showed me this evening.
If the camera firmware update failed, the best thing to do is follow adrynalyne's thread to rewrite the firmware instead of purchasing an app.
AlgorithmX said:
Try this before rolling back.
http://forum.xda-developers.com/showthread.php?t=951636
Click to expand...
Click to collapse
Like this suggestion which you seemed to ignore completely.
Sent from my ADR6350 using XDA App
times_infinity said:
If the camera firmware update failed, the best thing to do is follow adrynalyne's thread to rewrite the firmware instead of purchasing an app.
Like this suggestion which you seemed to ignore completely.
Sent from my ADR6350 using XDA App
Click to expand...
Click to collapse
I didn't ignore it, I let her know about it, and she said no. Other than that, 1) It wasn't my phone to mess with and I have no familiarity whatsoever with Android phones. Like I said in my original post, the issue belonged to a lady friend. And, 2), like most people, she's not comfortable with doing anything of the nature described unless she fully understood it first and that it was a verifiable fix. 3), What may appear simple and easy to you, may not appear simple and easy to her. Or, me. One mistake and who knows? Poof goes your phone? So, 4), for the many people like her, where Verizon's 2.2 update broke their camera (and there are many!) simply downloading different software may seem the best/only solution for them. They should at least know it is an alternative. And finally, 5), I hoped for a fix that someone who actually had this problem found and offered. My impression was that the poster, who you say I ignored, did not have that problem himself. As such, I had no way of knowing or verifying that "fix" worked and wasn't a case where the "cure is worse than the disease."
How do I reverse encryption on gtab10.1 lte vzw. I know it said you can't go back but is there like a root privelaged way?
OK I'm serious about the question.. can anyone help plz.
Sent from my Galaxy SII T-mobile using xda premium
I think the reason for encryption is that you cannot simply reverse it
Well, encryption exists so you can't get in, and since it's a mobile device, there's a reason to /not/ add a "backdoor" or "root override" to it.
Sorry bud. I might be mistaken (and I hope I am) but I don't think there's a way to "go around it"
Can't you just wipe the device?
Sent from my GT-N7000 using Tapatalk 2
RavenY2K3 said:
Can't you just wipe the device?
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
I tried to wipe it. Just booted right back up. Even tried through recovery and cannot mount sd
Maybe you are able to wipe it with ODIN - I remember I have read something similar before, one guy claimed he regained access when he wiped it that way.
What about flashing replacement firmware if it's available? http://www.sammobile.com/firmware/
ultratek said:
How do I reverse encryption on gtab10.1 lte vzw. I know it said you can't go back but is there like a root privelaged way?
Click to expand...
Click to collapse
You can reverse this by performing a factory reset through the settings (settings>security>backup and reset)...It is stated clearly at the time you perform the encryption - don't you guys read before doing anything to your tabs? Anyway if you try to reset though recovery then I think the tab hangs. So odin is the only way. In the following thread someone claims he fixed it.
http://forum.xda-developers.com/showthread.php?t=1152623
Good luck!
Sent from my amazing 10.1 galaxy tab
What? Me worry?
Panos_dm said:
It is stated clearly at the time you perform the encryption - don't you guys read before doing anything to your tabs?
Click to expand...
Click to collapse
You mean -gasp- reading manuals? And BEFORE switching the thing on? Nah.
RTFM is only a last-resort-measure...
Part of the fun is reading the manual before first switching the thing on. You should have all the time while the first charge completes anyhow... But then again, this is a general flaw in humanity nowadays. Lacking Common Sense...
Ah well, flames all around now for speaking out in Jest...
Just_Another_N00b said:
You mean -gasp- reading manuals? And BEFORE switching the thing on? Nah.
RTFM is only a last-resort-measure...
Part of the fun is reading the manual before first switching the thing on. You should have all the time while the first charge completes anyhow... But then again, this is a general flaw in humanity nowadays. Lacking Common Sense...
Ah well, flames all around now for speaking out in Jest...
Click to expand...
Click to collapse
Yeah...that's one thing I'm saying....I like reading the manual and I believe that - either printed or in electronic form - a good and sufficient documentation is always critical and needed.
But in this case what I mean is that at the moment you choose the encryption option IN the settings, you get a warning message. Samsung wants to make sure that when you encrypt the device you have knowledge of all the risks involved.
Sent from my amazing 10.1 galaxy tab
Panos_dm said:
But in this case what I mean is that at the moment you choose the encryption option IN the settings, you get a warning message. Samsung wants to make sure that when you encrypt the device you have knowledge of all the risks involved.
Click to expand...
Click to collapse
Not only in the settings and in the manual do you get bold lettering warnings, most of the fora handling this subject warn clearly on the issue.
On the other hand, it is good to encrypt your device, just making it one-directional is kinda non-logic, compared to all other options/settings/behaviour of Android and tablets.
Therefore it would be simple to misinterpret or ignore the big bold-letter warnings.
Again: Common Sense is slowly going down the drain in humanity.
Just_Another_N00b said:
Not only in the settings and in the manual do you get bold lettering warnings, most of the fora handling this subject warn clearly on the issue.
On the other hand, it is good to encrypt your device, just making it one-directional is kinda non-logic, compared to all other options/settings/behaviour of Android and tablets.
Therefore it would be simple to misinterpret or ignore the big bold-letter warnings.
Again: Common Sense is slowly going down the drain in humanity.
Click to expand...
Click to collapse
I'm not sure what you mean by one-directional. The whole point of encrypting your device is to make it secure from third party people, correct? So in order to reverse it you have to ended a pin code. If the encryption was removed by recovery wipe it wouldn't be so "secure". Thus the decryption is possible only if you wipe from the settings, and it requires the code in order to do so. Now yes, it is possible apparently to remove it by odin flash but few people know that (yes, xdaers are "few" to the majority of users).
And, finally, I totally agree with you. Common Sense is not so "common"
Sent from my amazing 10.1 galaxy tab
You guys got a manual with yours? I bought mine refurbished and I didn't receive a manual
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Thanks ✟
Moving to Q&A
Panos_dm said:
You can reverse this by performing a factory reset through the settings (settings>security>backup and reset)...It is stated clearly at the time you perform the encryption - don't you guys read before doing anything to your tabs? Anyway if you try to reset though recovery then I think the tab hangs. So odin is the only way. In the following thread someone claims he fixed it.
http://forum.xda-developers.com/showthread.php?t=1152623
Good luck!
Sent from my amazing 10.1 galaxy tab
Click to expand...
Click to collapse
This did not work on my tab at all. The system reboots, appears to be installing something, but then goes to the password prompt and boots as if nothing had happened. Would appreciate it if anyone could provide some suggestions.
Maybe this question belongs in the general android dev section, if so then sorry. What makes a phone "brick". I know what it means, but why can't we in brick them. If everything is wiped, what keeps us from accessing the wiped partition with a pc and doing what we want to with it. We do it with computers all the time. I know its not exactly the same, but its very similar isn't it? Is it like the BIOS going bad on a pc that causes them to brick?
Sent from my ADR6425LVW using xda app-developers app
From what I have heard, at least on the Rezound, bricks are generally caused by bad hboots. People do often compare hboots to BIOSs, but when they do, they always qualify their statements, adding that the two actually have little in common, but it's the best comparison between Android and PC. I'm sure someone else can explain that a lot better than I can. I believe a brick can also, theoretically, be caused by a bad kernel/boot partition, since it is what tells the phone where to get the information needed to boot (or something like that).
People also sometimes call it bricking when they just mess up the hardware in some way, like while replacing the digitizer.
Their are methods to unbrick from an hboot related brick, but they do not always work.
What Max said.
Just wanted to say you did indeed post this in the correct section. Even if it's a development related question, questions belong in the questions section
Sent from my ADR6425LVW using XDA Premium.
I always thought the same thing why can't you just wipe everything and reinstall if the brick is caused by a software issue then what's the stop you from removing that software and putting working stuff on.
The only thing I can think of to answer my own question would be, for example, you know how you can adjust the voltages to the CPU, well lets say you install some bad or damaged software which controls the Hardware say you send too much voltage to a component such as the CPU and you fry the component by sending too much voltage or maybe its even possible by sending not enough voltage.
Just a thought anyways . I could be way off I have no idea really.
Sent from my HTC One S using xda premium
Bad hboot brick is the most common common and it is irreversible because you need a functional hboot to flash anything. So a corrupted hboot leaves you with a catch 22. Your hboot is bad, you want to flash a working hboot but your bad hboot can't flash anything so your stuck.
A kernel or bootlooping brick is a soft brick because you can still boot to hboot or recovery and flash a working kernel
Sent from my ADR6425LVW using xda app-developers app
Can't a bad radio brick it too? I know on a pc you can start with nothing, no boot partition or mbr, and the kernel is flashed with the os (windows, linux), and you boot from a cd or floppy. The only thong you start with is BIOS. Is being incapable of booting from another source like USB or sd card the main reason we can't unbrick most phones? I guess I'm just looking for deeper detailed nerd answers for a better understanding. I'm a nerd as most of you would probably claim to be too lol and I just want to get a better understanding of how it all works.
Sent from my ADR6425LVW using xda app-developers app
There are three main parts to phone firmware. You have the boot loader, which handles very low level stuff and generally doesn't touch partitions, but provides a boot environment for other software such as recovery and system...which is why, in Broad com routers, it is called the CFE or Common Firmware Environment. Think of it as the BIOS of the phone. If the boot loader is corrupt or damaged, chances are there will be no way to recover the phone via normal methods; JTAG must be used to directly interface with the hardware and force reflash of the boot loader.
Recovery is in a way like DOS. It has the ability to create, mount, change, and delete partitions, but can't touch low level stuff like the radio or bootloader. It can modify and remove files on partitions and change specific things such as the kernel. A damaged recovery can usually be fixed without any special tools as the phone will boot but won't go into recovery mode. In the case of the Rezound, a PH98IMG flash would fix it.
The operating system of the phone is as Windows or Linux GUI is to a computer. It provides the user with an easy to use environment as well as tools and software to help the user do what he wants to do. A damaged OS may boot, and problems may be limited to a few specific apps, or the problem may be system wide to the point of unusability...or if there is something wrong with the kernel, the OS will not start at all, and will be stuck in a boot loop. Easily fixable via recovery.
socal87 said:
JTAG must be used to directly interface with the hardware and force reflash of the boot loader.
Click to expand...
Click to collapse
What's JTAG?
feralicious said:
What's JTAG?
Click to expand...
Click to collapse
A lot of devices have JTAG ports that allow us to use another piece of hardware to access the deeper levels of the hardware and software.
This makes it possible to unbrick by fixing those deep files that are required for the device to work.
Also, Wikipedia is your friend.
Here's the nerdiest answer you're going to get. Your phone is ultimately just a large hunk of copper and silicon. It contains all sorts of microchips and connections and are necessary for literally every function of the phone. Literally... From the LEDs to the audio components. Everything. If youve heard of a schematic that's what I, talking about. Each one of these microchips must be programmed form its specific function. Were literally talking hardware level here. No Android OS no hboot etc.
Point of explaining all of that being that there are all sorts of programmable parts of the phone that you will never modify, access, or even think about. If you manage to access and screw up the wrong thing.. You can quickly go from functioning phone to just a hunk of copper and silicon. Hboot is the lowest layer software that devs will modify. If you screw up the hboot.... You are left with a brick. Is it ultimately possible to unbrick in any situation? Yeah of course. How else would HTC have made the phone in the first place. But if you screw up the hboot... You're gonna need an engineering degree to fix that thing. And at the cost/effort that that would take.. You'd be better off buying a new phone. Thus your phone is totaled and its best use just because a paperweight.
Sent from my Nexus 7 using Tapatalk 2
I think it's important to note that most of the phones people post about being "bricked" aren't actually bricked. A lot of times people panic and if they can't fix their phone, they call it a brick. It's kind of a common, often used slang term. Now there's terms like hardware brick, hard brick, software brick, and soft brick and probably some more.
But if it's fixable in my opinion using a computer and commands, or if you can see it's getting power, it's usually not really bricked.
For example, when the s off process came out the forums were over run by people who "bricked" their phones while trying to attain s off. What actually happened in a big number of these cases was that the windows script replaced the boot.img that was on their phone with a custom boot.img for the service mode. When there was a windows error with the software which was newly developed and released, and the windows app hung up or the computer went weird mid process, they had a black screen with a funny image, like a disk and arrow maybe, and when they turned the phone on it only went to that screen. In fact it happened to me which is why I figured out how to fix it and what caused the problem.
Now all they would have had to do is run a fastboot command from their computer, "fastboot flash boot boot.img" to flash the boot.img that matched whatever rom was installed on their phone, and they would be back up and running. But for a large number of users, when they phone was unresponsive and turning it on took them straight to the black screen, they considered it "bricked."
When in fact the phone was doing exactly what it had been commanded to do, and it was the person who was expecting something unreasonable, when you think of it in 1's and 0's, or black and white. Of course this isn't always the case, there are some real bricks, just not as many as one would first believe if they scanned through forum topics for the word bricked in the title.
I am certain that by now (over) half of the (normal) Archos G9 users really only want one thing and NOBODY (including Archos) seems to care at all about doing it!
Very few need/want 'rooted' firmware (not to mention it wastes valuable memory space because the original Archos firmware is still leftover).
What MOST of us actually want (and in many cases need) is a simple way to just remove the totally idiotic restriction that Archos has put in their firmware that prevents us from ever installing an older firmware version (that is KNOWN to work correctly on our specific device).
At one point, somewhere during the problems with the 4.0.x firmware releases Archos did actually provide a way for users to go back to 3.2.80. WHY they have not provided us with a way to go back from the the 4.0.2x (worthless garbage) firmware releases to older firmware that we KNOW actually works makes no sense at all. Seems like they just hope you will be stupid enough to by a newer Archos model (something I sure will never ever do with that kind of idiot way of dealing with us users).
It's bad enough that Archos does not care at all about us users, but... there are some really sharp and smart people here on XDA that SHOULD be able to hack around things. Yet, it seems like none of them have any interest in doing so. WHY???
firmware
55mls said:
It's bad enough that Archos does not care at all about us users, but... there are some really sharp and smart people here on XDA that SHOULD be able to hack around things. Yet, it seems like none of them have any interest in doing so. WHY???
Click to expand...
Click to collapse
Because the most likely result would be a bricked tablet. It is not an easy thing to do and people who could do this are not wanting to use older firmware. Not that I'm one of the sharp and smart people but I think archos has keys you would need and they don't release them to the public.
stevemp said:
Because the most likely result would be a bricked tablet.
Click to expand...
Click to collapse
At this point I would be happy to brick my 101 G9 since it's of absolutely no use to me now anymore without having to install SDE and rooted 4.0.7 firmware (I've come close to bricking it a few times with all the various rooted/custom/alternative firmwares and other crazy things I've tried myself already). In other words, if NOBODY ELSE finds a way... I'll just keep trying things myself until it either works or ends up bricked. Not like it really matters now to me now anymore
It is not an easy thing to do and people who could do this are not wanting to use older firmware.
Click to expand...
Click to collapse
Although I'm no expert on things, I actually think that it really is NOT all that hard to do (if anybody that actually knows what they are doing would care to do it). I think you are dead on with how all the so-called 'developers' simply only care about whatever the next thing they can do instead of about actually fixing anything with the actual Archos firmware. Seems rather foolish to me though when they could actually PROVE how good they are by actually doing something instead of just adding all kinds of extra fluff (most of which can be downloaded/installed from Google Play for anyone with a stock rooted ROM if they really wanted that junk).
Not that I'm one of the sharp and smart people but I think archos has keys you would need and they don't release them to the public.
Click to expand...
Click to collapse
And that brings us right back to my original question... WHY? By now, Archos has already totally ruined their reputation. They've gone out of their way to totally trash as many G9 tablets as they could, then hoped people would just buy their newer devices... and NONE of their newer devices actually work right either. So, WHY would a company want to continue running their reputation down the toilet when they COULD actually do something that MIGHT actually improve it?
In other words, the one single thing that Archos COULD have done for us G9 users was to provide a way to install whatever older 'official' firmware version that we KNOW actually did work on our devices? So, again we're right back to WHY had Archos not done what us G9 users actually need/want instead of locking us into crap we NEVER WANTED?
I suppose I COULD live with rooted stock 4.0.7 if I ABSOLUTELY HAVE TO, but...
Installing SDE and the kernel files for rooted firmware use up some RAM space. And, with only 512MB to start with, well every single bit (pun intended) alters the capabilities and performance of the device. Heck, just going from official Archos 3.2.80 to official 4.0.7 already was at a cost of both RAM and system memory space.
On top of that, installing a 'rooted' firmware always uses up even more of the system flash memory. Depending which ROM, that ranges from 300MB to 500MB. When you only have an 8GB device, that really only ever had a little over about 6GB of usable flash left with official Archos firmware...
Well, when installing a 'rooted' ROM, that uses up more space for the ROM on top of the space that the original Archos firmware. And, that's the part that really bugs me!!! I had already been suckered into that the device had 8GB of Flash, then found out only really had about 6GB of "usable" memory, then had to install SDE and a 'rooted' ROM to ever get it to work right again ending up with only about 5GB of flash in the end (even deleting the leftover archos.ext4.backup file does not get back to what the device originally had).
Now, if somebody could tell me how to remove/delete ALL of the supposed 'official' Archos firmware so that I would actually have what I originally would have with the 'official' Archos firmware... well, I MIGHT just be happy enough to live with it (even though it DO NOT WANT 'root').
Anyway, I just don't care anymore!!! I simply want ALL TRACES of that horrible crappy Archos official 4.0.2x firmware TOTALLY REMOVED from my device!!! I'd prefer that it be totally reset to something close to whatever it came with (maybe something like 3.2.79) and then be able to upgrade to whatever higher firmware I want from there.
Oh, wait a minute, there ARE companies that actually do repair/refurbish these G9 tablets and CAN reset them... so, it would cut into their profit making if anybody else ever told us how they do it. Sure, now I get it... paid $250, now pay another $200 to get it to work again. NOT GOING TO HAPPEN!!!!!!!!!!!!!!!!!
I'll totally brick this thing and throw it into the garbage before paying to have it fixed now anymore. Damn LiThion batteries only last 2 years before the drop way down in usage, and I'm already coming up on a year and a half since this piece of Archos crap came out. Now I get it, just throw it away and NEVER buy another Archos procduct again!!!
I called up Archos today and had a stock answer when I asked about this.
I didn't give up and they have passed the issue to the tech department. (my hopes aren't high) however the bloke I spoke to said he hadn't had any calls or feedback regarding this.
he suggested formatting then loading up the older firmware, after instructing me how to download older firmwares by copying link then pasting, then editing build number for firmware I wanted.
I told him that Archos doesn't allow for this and everyone else does, so it isn't software from google but from archos that is blocking the install.
he took my number and said I would get a callback....
will update if I ever get one
y2grae said:
he took my number and said I would get a callback....
Click to expand...
Click to collapse
Welcome to a group of thousands that will very likely never get any response back from Archos!
Pretty clear that is not going to happen simply because of the totally idiot instructions that gave you. Seems like EVERYBODY ELSE except the people at Archos already KNOWS FOR A FACT that you can not install any older firmware version. Why they ever told you to even try to do that is just pure stupidity on there part.
Of course, if they actually do call you back an provide any USEFUL information I'm all ears, but I don't expect anything from Archos on this matter at all now anymore, or they WOULD have already told us how to do it. After all, it was about 3 months before they got around to putting out 4.0.28... and even then the screwed it up and there are actually 3 different versions of 4.0.28 they put out (am I the ONLY one that caught that and actually cares about it?... Seems surdu_petru has NOT bothered to update his rooted ROMS to the last of what Archos put out).
Really sick of Archos trying to con people over and over and over and over and over and over (am I repeating myself of is Archos?).
[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