Related
So today my Rooted Eris running nonsensikal started just randomly shutting off. If I let it sit for 15 minutes or so I can turn it back on and get it to run for a while. I used one of my old, very stable nandroid restores and still had the same problem.
So... phone must go in for warranty. I have it back to 1.5 stock. My question is how do I get it upgraded to the latest OTA 2.1? I have the 2.36.605.1 RUU .exe but it won't work Won't reboot to bootloader and says there's a USB problem (there's not).
Thanks in advance.
Since you already have the phone back to 1.5, I'll suggest a strategy which minimizes the amount of flashing which needs to be done. Note also: the stock recovery partition must be installed on the phone for any OTA update procedure to work - it will not work if Amon_RA recovery is still installed.
If your phone is having hardware troubles, it is quite possible that your phone will "glitch" in the middle of a flashing operation, and you will end up with a brick. There is little you can do to prevent that from happening, so ... you want to do as few flashing operations as possible before you turn the phone over to VZW.
For that very reason, I will suggest that you do not use the 1.5 to 2.1 OTA upgrade - it takes a LONG time to run. If the problem that your phone is having is related to the phone warming up, you want something which runs quickly.
I'll suggest that you flash the Leak-V3 PB00IMG.ZIP ROM using the HBOOT method. You know the one, right?
- download the Leak-V3 "PB00IMG.ZIP" file to the root folder of the SD card
- charge the phone to 100%
- shut down
- reboot by holding down Vol-Down+End
- accept all the prompts as they occur.
This will get you back to 100% stock (prior to the July 17 OTA). If your phone dies in the middle of the July OTA update (which is quite a bit smaller and completes faster), no big deal, the phone has been wiped and only has factory code on it.
You mentioned something similar to "letting the phone sit" for 15 minutes. Perhaps you want to charge the phone to 100%, and let it sit for an hour or two before running any flashing operation, so that it will have cooled down as much as possible before you flash anything.
Please also educate us: there have been a few users who have literally burned up their Eris by incautious overclocking; what profiles were you using for overclocking, and what Temperature settings were you using for the Safety setting? Were you using the Eris for sustained tethering operations?
bftb0
Hey thanks for the reply!
In regards to your last question, I've been running it at 806 for a couple of months without issues. Yesterday morning I followed the guide here: http://forum.xda-developers.com/showthread.php?t=761940 and I ran into problems a few hours later. My settings were:
DEFAULT 19MIN---806 on demand
SCREEN OFF 19MIN---480 MAX on demand 95 priority
TEMP <40 19MIN---528MAX 90 priority
BATT <40 19MIN---604MAX
SAMPLING RATE---100000
UP THRESHOLD---98
ignore nice ---0
power save bias---0
I guess it's also noteworthy I installed SetCPU 2.0.2 yesterday morning as well.
I'm not blaming the OP of that thread, it doesn't seem others are having problems. I wasn't using tethering or anything out of the ordinary. Nothing but text messages and Facebook for the most part.
I have ran leak V3 before. My only question, I thought that changed the bootloader and the OTA didn't? Please correct me if I'm wrong, I don't want to get hit with a bill for the phone if they notice that lol
Also noteworthy, my phone was on a charger all night and didn't die! It was dying all day yesterday, regardless of charging status.
joebob213 said:
In regards to your last question, I've been running it at 806 for a couple of months without issues.
Click to expand...
Click to collapse
That's precisely what I was getting at. Because the supply voltage to the CPU is stepped up as frequency is stepped up, it generates a lot more heat when running at high clock rates. Way more than you would expect. There have been users over on AF that burned their phones up in as little as one week by aggressively overclocking. I wouldn't recommend to any of my friends that they OC an Eris to 806. (I have mine peaking at 729, and I have never even tried to see how high it would go.)
joebob213 said:
Yesterday morning I followed the guide here: http://forum.xda-developers.com/showthread.php?t=761940 and I ran into problems a few hours later.
Click to expand...
Click to collapse
Well, your first post indicated you were also having problems with "old, very stable nandroid restores" - I suppose that they were not OC'ed to 806, and also didn't have these new tweaks applied. So, there is no reason to believe those older ROMs would be affected unless physical damage had occurred to your Eris.
joebob213 said:
I guess it's also noteworthy I installed SetCPU 2.0.2 yesterday morning as well.
Click to expand...
Click to collapse
Same comment as above - why would a software change in one ROM affect the behavior of a completely different ( "old, very stable nandroid restores" ) ROM? If the 1.5 ROM is also crashing, remember that it isn't even overclocked!
joebob213 said:
I have ran leak V3 before. My only question, I thought that changed the bootloader and the OTA didn't? Please correct me if I'm wrong, I don't want to get hit with a bill for the phone if they notice that lol
Click to expand...
Click to collapse
You are correct that the OTA doesn't touch the bootloader, but if you have run the Leak-V3 before, doesn't that would mean that you already have the 1.49.000 S-ON bootloader on your phone? (unless you were you able to change the bootloader back to 1.47 when you "went back to 1.5").
In any event, you might be getting overly anxious about it for several reasons. While you are absolutely correct that a team of forensic experts hired by Verizon to examine your phone might be able to look up the date of purchase and customer history to determine that you shouldn't have the 1.49.0000 S-ON bootloader on your phone, the chances of them taking that kind of interest in your phone is essentially zero - they get thousands of returned phones every day (all makes and models). There have been posters on this forum that reported returning multiple rooted Eris without making any effort to clean them up, and were never contacted or charged by VZW. So, the chances of them taking an interest in your phone because it has a 1.49.0000 S-ON bootloader is pretty small, especially considering that they have been shipping phones for a couple of months now with that bootloader installed.
Still, if you want to try returning it to absolute stock, you probably need to perform Jcase's "Flash any RUU" technique (which modifies the "misc" partition so that you prevent those "Main Version is Older" lock-outs by the bootloader.) That would also allow you to use the PB00IMG.ZIP file from the MR2, along with Toastcfh's "battery pull trick" to only flash the bootloader.
The thing to bear in mind is that the OTA process relies on having a stock recovery partition and the exact version of HTC software that the OTA expects to be upgrading - you didn't say exactly what state your phone was in when you restored to 1.5. Does it have the stock 1.17.605.1 recovery installed, too? Manually downloading the 1.5 -> 2.1 OTA and installing it as an "update.zip" will work - so long as your phone doesn't decide to crap its' shorts in the middle of that update. And after that, one more OTA (July 2010) to put it back to "current" stock status.
But as I said, if you think your phone has bad hardware and could fail at any moment, doing a lot of flashing just increases the chances that you will have a disaster right in the middle of flashing. Flashing the Leak-V3 ROM takes about 5 minutes including the first boot; but applying the 1.5 -> 2.1 OTA takes considerably longer - it goes in and manually patches 600+ files. It burns less than 100 MB to the phone, but it spends a lot of time running when it does so.
joebob213 said:
Also noteworthy, my phone was on a charger all night and didn't die! It was dying all day yesterday, regardless of charging status.
Click to expand...
Click to collapse
I don't know that makes me feel any better. If it is crashing with 1.5 on it, it is damaged goods.
bftb0
bftb0 said:
Since you already have the phone back to 1.5, I'll suggest a strategy which minimizes the amount of flashing which needs to be done. Note also: the stock recovery partition must be installed on the phone for any OTA update procedure to work - it will not work if Amon_RA recovery is still installed.
If your phone is having hardware troubles, it is quite possible that your phone will "glitch" in the middle of a flashing operation, and you will end up with a brick. There is little you can do to prevent that from happening, so ... you want to do as few flashing operations as possible before you turn the phone over to VZW.
For that very reason, I will suggest that you do not use the 1.5 to 2.1 OTA upgrade - it takes a LONG time to run. If the problem that your phone is having is related to the phone warming up, you want something which runs quickly.
I'll suggest that you flash the Leak-V3 PB00IMG.ZIP ROM using the HBOOT method. You know the one, right?
- download the Leak-V3 "PB00IMG.ZIP" file to the root folder of the SD card
- charge the phone to 100%
- shut down
- reboot by holding down Vol-Down+End
- accept all the prompts as they occur.
This will get you back to 100% stock (prior to the July 17 OTA). If your phone dies in the middle of the July OTA update (which is quite a bit smaller and completes faster), no big deal, the phone has been wiped and only has factory code on it.
You mentioned something similar to "letting the phone sit" for 15 minutes. Perhaps you want to charge the phone to 100%, and let it sit for an hour or two before running any flashing operation, so that it will have cooled down as much as possible before you flash anything.
Please also educate us: there have been a few users who have literally burned up their Eris by incautious overclocking; what profiles were you using for overclocking, and what Temperature settings were you using for the Safety setting? Were you using the Eris for sustained tethering operations?
bftb0
Click to expand...
Click to collapse
That's what I did when I had my trackball ball problem and had to take my phone in
Sent from my FroyoEris using XDA App
I've followed all of the instructions. I'm stuck on android stock 1.5 and every time I try to get the leakv3 to run it doesn't recognize it or something, I've tried formatting my SD card and renaming it correctly but nothing.
I need to send in my phone in a couple of days, so I need this to get fixed....
please help.
EDIT: Nevermind, leakv3 finally working.
TheDoctor1177 said:
I've followed all of the instructions. I'm stuck on android stock 1.5 and every time I try to get the leakv3 to run it doesn't recognize it or something, I've tried formatting my SD card and renaming it correctly but nothing.
I need to send in my phone in a couple of days, so I need this to get fixed....
please help.
EDIT: Nevermind, leakv3 finally working.
Click to expand...
Click to collapse
Please report what you discovered so that others will benefit from your experience - corrupted PB00IMG.ZIP file?
bftb0 said:
That's precisely what I was getting at. Because the supply voltage to the CPU is stepped up as frequency is stepped up, it generates a lot more heat when running at high clock rates. Way more than you would expect. There have been users over on AF that burned their phones up in as little as one week by aggressively overclocking. I wouldn't recommend to any of my friends that they OC an Eris to 806. (I have mine peaking at 729, and I have never even tried to see how high it would go.)
Click to expand...
Click to collapse
I knew what you were getting at, I was answering your question.
bftb0 said:
Well, your first post indicated you were also having problems with "old, very stable nandroid restores" - I suppose that they were not OC'ed to 806, and also didn't have these new tweaks applied. So, there is no reason to believe those older ROMs would be affected unless physical damage had occurred to your Eris.
Click to expand...
Click to collapse
The nandroid restore I used was also overclocked to 806, albeit without the tweaks. If I didn't think it was a hardware issue. I wouldn't be wanting to send the phone in.
bftb0 said:
Same comment as above - why would a software change in one ROM affect the behavior of a completely different ( "old, very stable nandroid restores" ) ROM? If the 1.5 ROM is also crashing, remember that it isn't even overclocked!
Click to expand...
Click to collapse
Same comment as above.
bftb0 said:
You are correct that the OTA doesn't touch the bootloader, but if you have run the Leak-V3 before, doesn't that would mean that you already have the 1.49.000 S-ON bootloader on your phone? (unless you were you able to change the bootloader back to 1.47 when you "went back to 1.5").
Click to expand...
Click to collapse
Yes, the bootloader is back to 1.47.
bftb0 said:
In any event, you might be getting overly anxious about it for several reasons. While you are absolutely correct that a team of forensic experts hired by Verizon to examine your phone might be able to look up the date of purchase and customer history to determine that you shouldn't have the 1.49.0000 S-ON bootloader on your phone, the chances of them taking that kind of interest in your phone is essentially zero - they get thousands of returned phones every day (all makes and models). There have been posters on this forum that reported returning multiple rooted Eris without making any effort to clean them up, and were never contacted or charged by VZW. So, the chances of them taking an interest in your phone because it has a 1.49.0000 S-ON bootloader is pretty small, especially considering that they have been shipping phones for a couple of months now with that bootloader installed.
Click to expand...
Click to collapse
I remember leakers getting charged $400 on their Verizon bill after sending in their phones.
bftb0 said:
The thing to bear in mind is that the OTA process relies on having a stock recovery partition and the exact version of HTC software that the OTA expects to be upgrading - you didn't say exactly what state your phone was in when you restored to 1.5. Does it have the stock 1.17.605.1 recovery installed, too? Manually downloading the 1.5 -> 2.1 OTA and installing it as an "update.zip" will work - so long as your phone doesn't decide to crap its' shorts in the middle of that update. And after that, one more OTA (July 2010) to put it back to "current" stock status.
Click to expand...
Click to collapse
I got the phone back to bone stock 1.5, OS, recovery, bootloader, etc...
Now the rest of the story. My phone is working fine now! Saturday morning I was still running 1.5 but I hadn't been using the phone at all and it still hadn't died again. I did a *228 option 1 and after the phone rebooted I got the OTA notification. I went for it. It actually didn't take very long! 10 minutes maybe? The phone was running fine after that... for a few hours. When I was at work I had it plugged in all day but I used it quite a bit. About an hour before I went home the phone died. I booted it back up and unplugged it. As soon as I took it off the charger I got the "plug in your charger" message. Said battery was less than 2% charged! Anyway, I let it die and took it home. Plugged it in at home and as soon as I turned it on it said the battery was full! I left it there for a while, then went to my other job and the battery meter drained FAST! Like, 2 hours fast with very little use. I plugged it back in yesterday morning, let it fully charge, and I haven't had any issues since! I unplugged it at about 10:00 yesterday morning and I've still got about 75% of my charge now.
So I have no idea what the issue was lol. Phone and battery lost communication with each other?
I'm going to go ahead and keep it stock for a while just in case I have to send it in but everything seems to be working fine after the battery freak out!
Maybe the problem was the battery all along?
I would ask VZW if they will swap out a battery with you to see if the problem persists.
BTW, I hope you didn't think I was "talking down" you - I provided all those "extra" details because you didn't mention them. From across the Internet, it is impossible to know whether someone doesn't mention something because they are completely aware of the details (and consider them not worth mentioning) - or because they aren't aware of them. No doubt you've seen the wide range of sophistication that posts in here.
bftb0
How many times we can flash our phone? like custom roming,rooting,kernel etc
I guess till it dies ..I have tested almost every rom n kernel in xda nd android world.it ,over fifty to hundred probably almost for 2 months now and keep changing no problems till now ..
Sent from my LG-P500 using xda premium
alxbsl96 said:
How many times we can flash our phone? like custom roming,rooting,kernel etc
Click to expand...
Click to collapse
you can flash it as many times as you can before it get bricked(from BRICKED i mean it cannot be reapaired by any way....
As many times as you wish.
^ Not completely true. At some point, the flash ROM will die on you. It's a natural event when it comes to flash memory, although it should take a good number of rewrites for that to happen.
metalboy94 said:
^ Not completely true. At some point, the flash ROM will die on you. It's a natural event when it comes to flash memory, although it should take a good number of rewrites for that to happen.
Click to expand...
Click to collapse
Flash memory gets deleted if u delete everything so theres no worry for that, so its almost,
unlimited flash times, as told until u cant start phone (hard bricked)
not soft bricked, l0l
however hard brick is kinda hard, (at least as we often cant flash other rom's also if we do so it wont boot properly to prevent phone from hard brick, so its kinda a good safety)
I'm not talking about bricking here, rather about the physical resistance of the memory. Why don't you check out the back of the packaging from a USB drive or memory card, you will notice an attribute named "Maximum Number of Cycles".
The Optimus One has EEPROM
http://en.wikipedia.org/wiki/EEPROM
Taken from Wiki:
The manufacturers usually specify the maximum number of rewrites being 10 to the 6th power or more.[2]
During storage, the electrons injected into the floating gate may drift through the insulator, especially at increased temperature, and cause charge loss, reverting the cell into erased state. The manufacturers usually guarantee data retention of 10 years or more.
In other words, don't worry about it
I just got a galaxy note for my galaxy nexus last night (traded) and I took it home and install goomanager and downloaded a rom that was "compatible" it saved to the directory that goomanager puts it in so I rebooted into CWMR and cleared cache / data etc then proceeded to install zip from SD Card. it started by saying flashing kernel 4% or whatever and then came back with an error. me being as bright as I am recently...I fixed permissions and rebooted thinking that it would at least let me back into recovery.
I now have a "Dead" note sitting on the floor infinitely "charging" so to speak its just plugged into the wall, Will not boot. Is there a way I can at least get it into Download mode? Hell stick a magnet on it to erase everything even?
I don't need another paper weight..I have an iPhone for that.
Can you boot into download? If so, use Odin to flash the correct kernel.
Can you boot into recovery? If so, flash the correct kernel.
If you can't do either one, your phone is bricked and you will need to send it for a repair. $50 and one week later you will have your phone back with stock 4.0.4 ICS rom. Its called a JTAG service, from www.mobiletechvideos.com. Many note user have gone there, from just this thing.
The jig that works with other phones 99% of the time won't work with the note.
Don't trust CWR. Get your roms from our developers.
Jig 99% Of the time won't work... you made that statistic up. If button combos aren't working it's definitely worth a shot, resistors are super cheap, especially compared to jtag which doesn't sound needed here yet.
And what do you mean. "Don't trust cwr get your roms from the devs here"?
That is a recovery... he didn't download anything with it, he used goomanager.
And even if he downloaded it from here...he would've flashed it in cwm... xda isn't a custom recovery...
So you tried holding the down volume button+ power to get it into download? Flashing a kernel will not remove your recovery/download mode unless you flashed a Rom not made for your device that installed something on said partition(s).
As for the jig...don't know statistics, but I am a one percenter. Worth a shot imo.
https://www.youtube.com/watch?v=6K-lvaAop2w&feature=youtube_gdata_player
Sent from my SAMSUNG-SGH-I717 using Xparent Gray Tapatalk 2
Volume down and power, then when prompted volume up, for download mode.
And I'm also a "1% er" and my jig isn't homemade. Josh from mobile tech gave me one of his he sells on the site.
As nun said, the combos should work, they are in the bootloaders, flashing a kernel won't effect those unless says kernel is for a different device, then you wouldn't get a single thing outta the device at all, no charging screen, no bootloop. Nothing. Whatsoever.
studacris said:
Volume down and power, then when prompted volume up, for download mode.
And I'm also a "1% er" and my jig isn't homemade.
Click to expand...
Click to collapse
Right amigo 99% + 1% = 100%. You and Nunhugger are the only ones who said a jig worked for them. So actually its way higher than 99%. . . But you guys are ninjas. Your phone would probably reboot if you just told it to. I just wanted to kill the eventual jig question early.
And my response about CWR was because it sounded like he used the old app Rom Manager to see what was available. Clearly it was wrong so I told him not to trust it, and put in a plug for our developers.
When an update is released the forum gets slammed with complaints about bad flashes of incorrect kernels, and I have seen several members heal their phone by flashing the correct kernel. I just figured he was not accustomed to the button combos of the note and would get to that eventually. But if it was for the wrong device I wanted him to get his mind around the $50 and week wait.
Sheesh. . . decaf.
Well seeing that I can't Get into either mode and no button combos will work, I am assuming I need the JTAG. I figured an app like GooManager would have at least gave me the right roms for my device. it did say i717 but that could just be my memory playing tricks on me.
Man, I'm real sorry. But the JTAG service has been used by many, and with lots of positive comments. Good luck.
hahah thats okay, I mean its a great phone, definately not worth keeping in a draw collecting dust so I will go with the JTAG service. Thanks Guys!
You still have signs of life, it shows the charging animation, therefore your phone isn't bricked.
Do some searching on making a jig, I personally think it's well worth a try.
You could very well fix your phone for under $10 and have the satisfaction of accomplishing this yourself And have the know how to do it again...
It doesn't have the charging animation. just a dead black screen.
Then why did you say this?:
leveliv said:
I now have a "Dead" note sitting on the floor infinitely "charging" so to speak its just plugged into the wall, Will not boot.
Click to expand...
Click to collapse
That's more than a little misleading...
Will not boot...could mean many things.
From a easily fixed bootloop down to a brick.
Saying it was infinitely charging made it sound less severe.
if it weren't for that line, I wouldn't have bothered to tell you to use a jig.
JTAG it is
cris, why do you need to experiment with finding the proper resistance? Why should there be any variability in that circuit? Perhaps that is why some users have used up as many as six usb port replacement parts.
By the way, my 99% statistic is, like my entire post, just my opinion, and strictly a figure of speech. If it were a fact I was quoting I would have included a footnote. Remember those painful things? Do we have to include disclaimers for any figure we use? Sorry to mislead anyone!
I said "dead" because its not necessarily dead because a JTAG thing can fix it..and I said "charging" because to the normal person who didn't know anything was wrong with said device it would look like it was charging. But anyhow. I'm sending the phone out this week. I just don't understand why all the phones can't be as open as the devices straight from google.
You're phone is dead.
JTAG is akin to zombie, the phone needs disassembled and a special rig is needed to hook to the motherboard and flash EVERYTHING back to the nand at the prebootloader level.
The I717 is pretty much just as open as a nexus as far as easily modified and rooted...
No locked bootloader even which nexus have though it's a single line in a terminal to unlock, that step isn't needed on this device.
Only thing that isn't as open is the hardware drivers.
You may have flashed an incompatible kernel for a DIFFERENT device... and that on any phone will brick you.
And ranger not sure if it's the circuits within the phones that vary from device to device, ands seem to require a more specific voltage across those pins to trigger download mode
Or, if It's the resistors that are the variable. They are only rated within a certain +/- tolerance the cheaper ones having a larger margin of error.
And lol yes I am a ninja, but I didn't do anything special to my jig at all, I got mine from mobiletechvideos, funny enough it's worked on 4 captivates, a vibrant, 2 note 1s, and an s3, but didn't work on an s2 I was fixing.
the one I got from Goomanager was probably for the i700 which shouldn't even be able to happen.
They have video proof of them fixing phones with dead black screens from exactly what happened to mine using the JTAG Method. As far as I am concerned this thread can be closed cause I got the answer to my question.
the JTAG rewrites basically everything anyways so it is being sent out later this week. Till then I'll use a blackberry or something...Take care guys hopefully next time you see me post it will be to help someone and not asking for help
You'll be up and running by next weekend. By then, lots of exciting development will be happening on the released rom.
I doubt it, I live in Canada and have to send it to the states. It probably be closer to the weekend. Unless I expedite everything.
[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
Hi there, I just got the 6P as my nexus 5x went into bootloop (not semi-bootloop from a bad flash, the one that is caused from one of the processors dying) and none of the fixes were working. I just wanted some general info, the do's, the do nots, etc. Does this phone also suffer from the same issue? I was rooted on 8.1 with Magisk. Does flashing / rooting put you more at risk to an unfixable bootloop? I would be planning on just flashing TWRP, and Magisk on a stock rom. Any tips, recommendations, etc would be highly appreciated!
notstevek said:
Hi there, I just got the 6P as my nexus 5x went into bootloop (not semi-bootloop from a bad flash, the one that is caused from one of the processors dying) and none of the fixes were working. I just wanted some general info, the do's, the do nots, etc. Does this phone also suffer from the same issue? I was rooted on 8.1 with Magisk. Does flashing / rooting put you more at risk to an unfixable bootloop? I would be planning on just flashing TWRP, and Magisk on a stock rom. Any tips, recommendations, etc would be highly appreciated!
Click to expand...
Click to collapse
Yes this phone will do it to in fact the message that I am writing is being sent from one that went into bootloop previously. Routing and such does not cause the boot loop. It is a processor malfunction. You can flash a kernel that will disregard the faulty processors in this situation should it become necessary. All you need to do is to make sure your bootloader is unlocked so you will have the ability to flash this kernel and go ahead and search for the fix so you will have it handy.
Sent from my Nexus 6P using Tapatalk
funnel71 said:
Yes this phone will do it to in fact the message that I am writing is being sent from one that went into bootloop previously. Routing and such does not cause the boot loop. It is a processor malfunction. You can flash a kernel that will disregard the faulty processors in this situation should it become necessary. All you need to do is to make sure your bootloader is unlocked so you will have the ability to flash this kernel and go ahead and search for the fix so you will have it handy.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Well that's a shame to hear, my Nexus 5x went into bootloop and I could not fix it, even with the patched files. I hope it doesn't happen to this. But I'm glad to hear it rooting/flashing will not induce a permanent bootloop and that it is indeed a processor malfunction. I just unlocked the device as we speak, I'm going to be flashing Magisk and TWRP soon. What kernel are you referencing, just so I can have it *just incase*.
Thanks for the info!
notstevek said:
Well that's a shame to hear, my Nexus 5x went into bootloop and I could not fix it, even with the patched files. I hope it doesn't happen to this. But I'm glad to hear it rooting/flashing will not induce a permanent bootloop and that it is indeed a processor malfunction. I just unlocked the device as we speak, I'm going to be flashing Magisk and TWRP soon. What kernel are you referencing, just so I can have it *just incase*.
Thanks for the info!
Click to expand...
Click to collapse
Sorry I don't have the URL handy but it's in here just search in the 6p forums and you should easily find it as there has been a lot of chatter about it
Sent from my Nexus 6P using Tapatalk
Unlock the bootloader on the 6p right off the bat. Activate the developer options, Turn on OEM unlocking, Adroid debugging and Debugging notify. Shut off "verify apps over USB". You'll have to connect the device to
the computer and do the fastboot command to achieve the final bootloader unlocking but once done, you're safe. Every time you boot, you'll see the stupidhead screen imploring you to lock the bootloader but ignore it.
Phone will boot evey time. I ultimately downloaded the 8.1.0 (OPM3.171019.013, Jan 2018) image used my Ubuntu laptop to get the rom in the phone, rooted it with Magisk, TWRP'd it and got the latest Lineage 15.1 kernel and
flashed that. Only problem I have is I can't get a USB stick to be read from the OTG socket. It's identified but it won't read the stick. Now that's O.K. with me because the phone will interface with a computer fine AND
if I boot into TWRP recovery, the file manager there does backups to an attached USB stick and can read and write to it perfectly fine. It's a quirk I can live with. I believe only 4 cores are used but it runs pretty nicely.
Battery swaps are a bear and I have a "good" 64Gb model and bought a "bootloop" 128gb special that looks immaculate. I've tried most of the tricks and it's gorked. I'm going to use it for a battery swap practice unit for when
I want to swap the battery on my good 64gb model. I also bought a new housing in case I dork some of the hardware getting the case open. Crappy design on the battery and they expect a $600.00 to $700.00 when new
phone is supposed to be "throwaway" after two years? Oh, don't buy a bootloop special unless it's dirt cheap. I'll not get the $100.00 I paid for the 128gb unit back or out of it. I don't think I'll be able to fix the one I got. When I open the case, I'll heat the CPU's directly and see if that will get it to start.
What is supposed to happen is one is to let the phone drain down to near nothing, plug it into the charger, let it bootloop for 5 minutes and they apply heat to the area between the camera and the fingerprint sensor.
When it gets to 50 degrees C, the phone supposedly shuts down the "bad" cpu's and will boot as a new phone on the "good" cpu's. One then is supposed to run into the menu, become the developer and do the steps I outlined above to allow OEM unlock. THEN it's safe to try and start loading a new ROM as the phone will communicate with a computer. I took the 128Gb unit and got it connected to an Ubuntu Linux laptop and "fastboot devices" shows the phone but since the bootloader is locked it won't do anything with it. I say the 6p is "ok" when compared to a $1000.00 Pixel 2 which of course is going to be a bear if one wishes to swap out the battery in the future. Lithiums only last so long (or any battery chemistry for that matter) then they need to be replace. Spend a grand on phone and it oughta last
more than two years. Kurt
ksaves2 said:
Unlock the bootloader on the 6p right off the bat. Activate the developer options, Turn on OEM unlocking, Adroid debugging and Debugging notify. Shut off "verify apps over USB". You'll have to connect the device to
the computer and do the fastboot command to achieve the final bootloader unlocking but once done, you're safe. Every time you boot, you'll see the stupidhead screen imploring you to lock the bootloader but ignore it.
Phone will boot evey time. I ultimately downloaded the 8.1.0 (OPM3.171019.013, Jan 2018) image used my Ubuntu laptop to get the rom in the phone, rooted it with Magisk, TWRP'd it and got the latest Lineage 15.1 kernel and
flashed that. Only problem I have is I can't get a USB stick to be read from the OTG socket. It's identified but it won't read the stick. Now that's O.K. with me because the phone will interface with a computer fine AND
if I boot into TWRP recovery, the file manager there does backups to an attached USB stick and can read and write to it perfectly fine. It's a quirk I can live with. I believe only 4 cores are used but it runs pretty nicely.
Battery swaps are a bear and I have a "good" 64Gb model and bought a "bootloop" 128gb special that looks immaculate. I've tried most of the tricks and it's gorked. I'm going to use it for a battery swap practice unit for when
I want to swap the battery on my good 64gb model. I also bought a new housing in case I dork some of the hardware getting the case open. Crappy design on the battery and they expect a $600.00 to $700.00 when new
phone is supposed to be "throwaway" after two years? Oh, don't buy a bootloop special unless it's dirt cheap. I'll not get the $100.00 I paid for the 128gb unit back or out of it. I don't think I'll be able to fix the one I got. When I open the case, I'll heat the CPU's directly and see if that will get it to start.
What is supposed to happen is one is to let the phone drain down to near nothing, plug it into the charger, let it bootloop for 5 minutes and they apply heat to the area between the camera and the fingerprint sensor.
When it gets to 50 degrees C, the phone supposedly shuts down the "bad" cpu's and will boot as a new phone on the "good" cpu's. One then is supposed to run into the menu, become the developer and do the steps I outlined above to allow OEM unlock. THEN it's safe to try and start loading a new ROM as the phone will communicate with a computer. I took the 128Gb unit and got it connected to an Ubuntu Linux laptop and "fastboot devices" shows the phone but since the bootloader is locked it won't do anything with it. I say the 6p is "ok" when compared to a $1000.00 Pixel 2 which of course is going to be a bear if one wishes to swap out the battery in the future. Lithiums only last so long (or any battery chemistry for that matter) then they need to be replace. Spend a grand on phone and it oughta last
more than two years. Kurt
Click to expand...
Click to collapse
Hi Kurt,
Wow, first off thanks for the indepth response. My Nexus 5x was unlocked, rooted with Magisk, allowed unlocking, usb debugging etc. Still can't fix it. I put it in the freezer and got it to boot into TWRP for 30 seconds before it boot looped. Bootloader always works, and can flash, but cannot boot into the rom or recovery. Anyway, I bought this 6P (128gb for $170, perfect condition with a Spigen case and glass screen protector.) because the Nexus 5x is dead, but wasn't aware this also has the same issue which sucks. I run Debian 32bit on my laptop, and it's a breeze compared to windows. Just had to grab the binaries for adb and fastboot, unlike windows where you gotta install crazy large sdk packs, make sure you got the correct drivers, etc. I unlocked the 6P, oem unlocking & usb debugging is checked on developer options. I flashed TWRP, and I'm on 8.1 OPM3.171019.014 (Feb 5th) because the newest one (8.1.0 OPM5.171019.015) won't pick up my Verizon simcard. I flashed Elemental X so I can underclock it, I'm running 4 cores at 1,200mhz and it still runs flawlessly. Any reason I should be using the LineageOS 15.1 kernel? I don't ever plan on using LineageOS or a custom rom. Just stock rooted for me. The battery life is kind of poor compared to the Nexus 5x. I'm a little confused, what do you mean by "Battery swaps are a bear"? If it's worth it, maybe I will put in a new battery. Lithiums life are extended if you don't charge 100% and don't let it die. If you keep it above 20% and charge to 90% max, you'll extend the lifespan by a lot. Some phone companies like Samsung already do this. Your 100% charge is actually only 95% or so in reality. Other things like Telsa cars also do this. I wouldn't have upgraded for a few years if my Nexus 5x didn't die, and honestly if I wasn't afraid of another bootloop, I would have gotten another, I loved that phone. The pixel 2 is great, my brother has one, but I'm not spending more than 250 on a phone ever again in my life, and 250 being the absolute max. I also don't want to sign a contract and do a device payment, I want to own it in full. I will upgrade to the pixel 1 XL when this phone requires me to do so, and hopefully that's at least 2 years from now. Thanks in advance!
Cheers.
Tore open the 128gb "bootloop" special using the variety of videos out there. Heated the CPU's directly although the battery
was I believe fully charged. No dice of breaking the bootloop to have it boot to a "clean" system and unlock the bootloader.
There were no anti tamper seals on this thing so I thing someone threw it out there for $94.00 and I stupidly bit. I caution
folks that unless one can buy a "bootloop" special for less than $20.00 and they have a "good" 6P they want to replace a battery on, don't buy a bootloop special unless it is dirt cheap. Use it to practice on for battery replacement before using
it on a "good" 6p.
I heated the CPU, case off while in a bootloop and no magic restoration was seen. The battery was from October 2015.
I dinged the edges of the glass but got the back half off pretty decently. If the thing booted up and I were able to restore it, I would have been happy with it as the dings aren't really noticeable.. I need to get some guitar opening picks without a lip on them as they are better to work with.
Last ditch attempt will be to drain it down to el "zippo" percent left, put it on a charger and see if I can make the $94.00 evaporate under the auspices of a 1000 watt heat gun with the back case off. Again, don't buy a "bootloop" special of a 6p unless it's dirt cheap. Kurt