Related
Ok, so I've been working for a solid 2.5 days straight trying to repair an Eris I purchased on ebay.
I've flashed and re-flashed and done all sorts of crap and now it seems I'm in a pickle.
I was able to use RUU's just fine at the start of all this, additionally the phone's MIN showed up normally as well and also when I connected the phone to say QPST it showed up as a droid Eris.
Now the RUU's always give "error[130]: model id error," the MIN shows up as "0000009763" and the phone is recognized as a "FFA/SURF 7600 WinMob" phone of some sort.
My problem is that I'm trying to downgrade using an RUU to RUU_Hero_C_Sprint_2.27.651.5_R_signed_release in hopes that that will help me with the repair but I can't because of the RUU error.
Additionally, I feel like I may have just plain screwed up my phone with all this.
If anyone could please give some pointers or even just an encouraging word to lift my spirits I would be so appreciative as this is really starting to wear on me.
You guys are awesome even if there is no help for me..thanks for everything!
conradcliff said:
I was able to use RUU's just fine at the start of all this, additionally the phone's MIN showed up normally as well and also when I connected the phone to say QPST it showed up as a droid Eris.
Now the RUU's always give "error[130]: model id error," the MIN shows up as "0000009763" and the phone is recognized as a "FFA/SURF 7600 WinMob" phone of some sort.
My problem is that I'm trying to downgrade using an RUU to RUU_Hero_C_Sprint_2.27.651.5_R_signed_release in hopes that that will help me with the repair but I can't because of the RUU error.
Click to expand...
Click to collapse
I can not imagine even a single reason why you would ever attempt to flash firmware meant for one phone onto a different phone - especially if there was a bootloader replacement involved. The fact that the phone does anything at all after doing that is almost a miracle, frankly. (Yes, I realize that the Hero is a cousin of the Eris, but that doesn't also mean they share the same partitioning layouts, kernel load addresses, hardware interrupt structure, etc).
But, I suppose you are aware of that by now. It is probably also why no-one is offering any help - you are in territory where folks don't normally venture.
Personally, I would sell the phone on eBay described as a "for parts" unit and eat the difference between what was originally paid for the unit.
bftb0
Hmm, just following instructions I've gotten from several different sources.
I was leery as well, but after flashing that RUU a couple times prior with no ill effects it would seem that the information I received wasn't faulty.
Thanks for the input though.
If you did something meant for the hero and tried it on the eris then it is faulty. Just because something hasn't happened yet doesn't mean it won't
Sent from my FroyoEris using XDA App
I have since gotten back everything back pretty much to normal..though qpst still reads the phone as a SURF 7600 WinMob. I've got a 1.49.2000 S-OFF bootloader and eris radio and rom. Things are looking up from before but I stil haven't gotten it working on Metro..
Get it flashed over from a metro store then I can help you get the net on it
Sent from my FroyoEris using XDA App
Will a metro store flash this phone over? I thought they would flash data phones...
So here's my story, I am not entirely new to rooting as I have successfully rooted my Motorola Droid, My Droid X2, My Acer Iconia a500 (twice), My aunts Lg something, and my mothers Kindle Fire.
So a few days ago my Droid X2 started acting up, and would go hours on end sometimes without working.
I was very happy to find out that Verizon would replace it with no hassle as it was less than a year old. I got the replacement yesterday and it's working great... that is until I found out it came stock with 2.3.5 right out of the box.
Now I have always trusted XDA forums and have used them for a long time (although I finally just registered today to ask this)
The only root method I can find is to downgrade to 2.3.4 and then root, then install voodoo root protector, then upgrade.
Now I saw a few things about possibilities of bricking your phone when trying to read those tutorials (I have never had to downgrade before) and I was a bit concerned.
I was mainly wondering, I don't care about loosing data on the phone. I have a backup sd card I can use if I need to format that, and like I said, the phone is new and actually doesnt have a single app I have installed on it yet.
Is there any easy way to go back down to 2.3.4 for my situation? I just got the free phone and don't want to brick it a day later you know?
From what I gather, you can SBF back down to 2.3.4 with no problem. There may be a certain way you have to do it though. I have never been on stock 2.3.5 so I cant tell you from experience. But Everyone says it's possible.
That's my question in a nutshell
Yeah, I read a tutorial about how to do it using RSDlite, which I downloaded to my comp.
Now what I'm cautious about is white file to use. One of the tutorials had one, now while I know a tiny bit about rooting I know NOTHING about flashing it back, I wasn't sure if there was a way that this could screw up my phone, as it seems everything tested is with a phone that had already been rooted, or if there is anything phone specific in that file, or even if it actually is an OTA original (I'd rather not mess around with anything customized right now)
Whatever is the easiest method for getting be back down, I know how to take it from there as I've done it before.
Thanks for the response though!
Excolo said:
Yeah, I read a tutorial about how to do it using RSDlite, which I downloaded to my comp.
Now what I'm cautious about is white file to use. One of the tutorials had one, now while I know a tiny bit about rooting I know NOTHING about flashing it back, I wasn't sure if there was a way that this could screw up my phone, as it seems everything tested is with a phone that had already been rooted, or if there is anything phone specific in that file, or even if it actually is an OTA original (I'd rather not mess around with anything customized right now)
Whatever is the easiest method for getting be back down, I know how to take it from there as I've done it before.
Thanks for the response though!
Click to expand...
Click to collapse
So you have never used an SBF file? If you would have used it on your broken Droid X2 when it wasnt acting right, it might have fixed your phone. An SBF file simply wipes everything of your phone (excluding your SD card) and flashes brand new software on it. The SBF files are provided by Motorola so its not like you are using something made by a dev and can break your phone easily. You should be able to use RSD lite to flash the 2.3.4 SBF file and you should be fine. But then again, I have never SBF'd from 2.3.5 to 2.3.4 personally so I would feel bad saying go ahead with no worries and something bad happen. So wait for someone else to respond first.
Thanks!
Thanks for that info!
Also, I doubt that would have fixed my old phone, it seems pretty much like a hardware issue. The screen will display static for hours on end (think like an old tv if you didnt have cable plugged in) I think it's a loose connection somewhere or something. I didn't bother to really troubleshoot it myself though because I was like "lets see if Verizon will give me a new one" and they did, and because they didnt have any "replacements" i got a brand new one, with a brand new battery, so I wasn't going to argue the fact
Anyway, if the file is from Motorola where can I get it? I saw on a verizon forum that they were not allowed to post it there (or is it "from motorola" in the sense it was leaked?)
Thanks for all your help so far, you've been great!
Excolo said:
Thanks for that info!
Also, I doubt that would have fixed my old phone, it seems pretty much like a hardware issue. The screen will display static for hours on end (think like an old tv if you didnt have cable plugged in) I think it's a loose connection somewhere or something. I didn't bother to really troubleshoot it myself though because I was like "lets see if Verizon will give me a new one" and they did, and because they didnt have any "replacements" i got a brand new one, with a brand new battery, so I wasn't going to argue the fact
Anyway, if the file is from Motorola where can I get it? I saw on a verizon forum that they were not allowed to post it there (or is it "from motorola" in the sense it was leaked?)
Thanks for all your help so far, you've been great!
Click to expand...
Click to collapse
Yeah, it does sounds like it was a hardware problem. Actually, I never thought about if motorola had a list of sbf files somewhere or if they were just leaked or what. I always downloaded them from threads like these. I just know they are made by motorola. You got me curious now. hmmm...
Duh
forget about my question as to where to get them, just saw the sticky at the front of this forum.
Although, it would be interesting to know if they were officially given out by motorola or leaked
Excolo said:
forget about my question as to where to get them, just saw the sticky at the front of this forum.
Although, it would be interesting to know if they were officially given out by motorola or leaked
Click to expand...
Click to collapse
What's An SBF File?
• SBF Is A File Leaked By Motorola That Is The System Image Flashed By RSDLite.
Taken from the Motorola Droid X2 FAQ page here
Excolo said:
So here's my story, I am not entirely new to rooting as I have successfully rooted my Motorola Droid, My Droid X2, My Acer Iconia a500 (twice), My aunts Lg something, and my mothers Kindle Fire.
So a few days ago my Droid X2 started acting up, and would go hours on end sometimes without working.
I was very happy to find out that Verizon would replace it with no hassle as it was less than a year old. I got the replacement yesterday and it's working great... that is until I found out it came stock with 2.3.5 right out of the box.
Now I have always trusted XDA forums and have used them for a long time (although I finally just registered today to ask this)
The only root method I can find is to downgrade to 2.3.4 and then root, then install voodoo root protector, then upgrade.
Now I saw a few things about possibilities of bricking your phone when trying to read those tutorials (I have never had to downgrade before) and I was a bit concerned.
I was mainly wondering, I don't care about loosing data on the phone. I have a backup sd card I can use if I need to format that, and like I said, the phone is new and actually doesnt have a single app I have installed on it yet.
Is there any easy way to go back down to 2.3.4 for my situation? I just got the free phone and don't want to brick it a day later you know?
Click to expand...
Click to collapse
bro, you wont have any problems downgrading/sbfing back to 2.3.4, i did it without any problems
i used sbf_flash through linux though idk about RSDLite
Hi There,
I did search around and didn't find a specific answer to this, I did see someone was looking to modify some binary values but no confirmation if it worked. Anyways I have successfully used many roms on my phone and tablet but last night after using CWM and the rom flashed successfully I rebooted the device and then nothing. Blank screen. Nothing happens when I charge. Used the wife's battery fully charged to see if it would help. Tried three-button boot method. All nothing. It's just dead.
Now I'm guessing I must have missed a step somewhere and fully take responsibility for what happened, and would pay for a repair - but can Samsung even repair a device in this state? I talked to an agent on the phone last night and openly told them what happened and asked how much it would be to repair and he said he couldn't give me any information without sending the device in. This is my mistake to get my phone in this state so I don't want to sneak my way into a warranty replacement. Is it worth the wait as Samsung can fix this, or should I just buy a new phone?
Cheers and any information is much appreciated.
www.mobiletechvideos.com
They can repair bricked phones for a very reasonable cost. Samsung may see it and void your warranty. I'd go with Mobiletech. I've heard they do great work on bricked phones.
The above advice is good, assuming your device is truely hard bricked.
However, from your description, it's hard to figure how you bricked it. A true brick usually happens when an attempt to flash a bootloader partition gets interrupted in the middle. There are possibly other ways, but it's not very easy, actually. So, is there absolutely no sign of life? Nothing you can do will even get a flicker of light on the screen? You cannot enter download mode, or recovery mode. You have tried all of these? No point in spending $50 on a jtag repair if you can recover the phone yourself.
I would also be interested in a complete description of the steps that led up to the problem.
I'm a little embarrassed to post this but don't want to waste anyone's time. It is totally bricked but I know why.
I just noticed I downloaded a rom from the i777 forum, and my device is a i727.
Oooops! Guess I'm learning a valuable $50 (plus shipping) lesson.
Thanks for the help, my phone is off Mobile Tech.
Still might not be hard bricked. Mine did this a few weeks ago for no reason. Had been running fine then wouldn't boot one day. Wouldn't boot at all. Could not get into recovery.Nothing. Only thing that worked was connecting through Odin. Had to then flash original Gingerbread. Phone then booted fine. I have since rooted again and I'm now dual-booting SHOstock and Rootbox. Try Odin first.
SPatMobile said:
I'm a little embarrassed to post this but don't want to waste anyone's time. It is totally bricked but I know why.
I just noticed I downloaded a rom from the i777 forum, and my device is a i727.
Oooops! Guess I'm learning a valuable $50 (plus shipping) lesson.
Thanks for the help, my phone is off Mobile Tech.
Click to expand...
Click to collapse
I don't really know much about the I727 architecture, but I seriously doubt if your device is hard bricked. You should still be able to get into download mode via the normal procedure (maybe, or if not with a usb jig) for your phone, and then flash a good I727 rom, I believe. There are no bootloaders or partition information, or param files in any of the I777 roms, as far as I know, so there's really not much of anything that can do serious damage.
Try getting in to download mode by With your phone off and unplugged. Enter download mode by pressing and holding the power and volume down buttons and plugging in the USB cable before the lights blink. I don't know it will work on i727 but worth a try..GL
This is a good thread to help you read all you can....
http://forum.xda-developers.com/showthread.php?t=1652398
creepyncrawly said:
I don't really know much about the I727 architecture, but I seriously doubt if your device is hard bricked. You should still be able to get into download mode via the normal procedure (maybe, or if not with a usb jig) for your phone, and then flash a good I727 rom, I believe. There are no bootloaders or partition information, or param files in any of the I777 roms, as far as I know, so there's really not much of anything that can do serious damage.
Click to expand...
Click to collapse
Interesting. Well I suppose it is possible I had a legitamite hardware failure completely unrelated to the software issues. I did some searching around for hardware failures instead and found some very similar cases to this.
Exactly what happened. I downloaded the wrong rom, rebooted in cwm, wiped, then flashed the rom. It went successfully and I rebooted from cwm then during boot right after the samsung logo all the lights went off and the screen went black. I left it like this for about 45 mins to an hour and had dinner just in case it was still doing something. The battery was fully charged at the time I started the procedure, and I have tried using the wife's battery to make sure mine wasn't dead. My battery also functions without issues in her phone. I had done this successfully multiple times on my phone before and tablet, and successfully flashed two or three different roms on my wifes phone last night.
I tried every suggestion mentioned, and followed the guide as well. There is no glimar of life. If this is hardware I might be wasting my money with Mobile Tech but I suppose we'll know for sure soon. Phone is shipping off today.
Have you tried a jig?
Sent from my SGH-I777 using xda app-developers app
you're doing the right choice, mobile tech is your best bet
OP got his answer. And his device is an i727. Let's let this one die before we attract trolls
Sent from my SGH-I777 using Tapatalk 2
Ya good idea
Sent from my SAMSUNG-SGH-I777 using XDA
In case anyone was interested it looks like the device was a hardware failure.
"Unfortunately, I was not able to repair your device. The device's onboard EMMC controller was in a non-responsive state. It is advised to try out warranty replacement if possible or to search for a parts device and use it's mainboard for the swap."
*edit - I tried to use the thanks meter for everyone, but thanks for all the help!
Never was really a samsung fan until I got my i777. Blackjack? wth was that? Browsing with opera was off the hook though so the phone grew on me. Now I tried simply flashing a different i777 kernal because ICS constantly freezes and the phone bricks? Sent it to Mobile Tech Videos.... EMMC is in non responsive state for me too wtf Samsung? Had my nexus one twice as long and flashed twice as many times and its still rockin. Now will definitely think twice before going Sammy.
paulfrankie said:
Never was really a samsung fan until I got my i777. Blackjack? wth was that? Browsing with opera was off the hook though so the phone grew on me. Now I tried simply flashing a different i777 kernal because ICS constantly freezes and the phone bricks? Sent it to Mobile Tech Videos.... EMMC is in non responsive state for me too wtf Samsung? Had my nexus one twice as long and flashed twice as many times and its still rockin. Now will definitely think twice before going Sammy.
Click to expand...
Click to collapse
Did you wipe in ICS's stock recovery before flashing that different kernel? Because there's a well known brickbug with the I777's stock ICS kernel, where if you use it to do anything before you flash custom kernels, it'll mess up your EMMC and brick your phone. If this is what happened to you, I would suggest you do more reading before flashing anything again; different phones operate differently, and even if you're a pro at flashing stuff on a galaxy nexus that doesn't mean squat when it comes to flashing an I777. I don't mean to be harsh or offend you, I just want you to know that reading more is always a good idea, and that there's a chance that it wasn't Samsung's fault you wound up with a bricked device.
He could always try the jig to kick it into download mode. Read up about it. It may save you some money.
HTC = Hate The Consumer
Mobile tech will fix ya but in all seriousness, phones are way different from model to model. As previously stated. Read a lot before doing anything. may Atrix is way different than this phone,.
Sent from my SGH-I777 using Tapatalk 2
[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
Greetings all,
I had a Razr Maxx HD for about two years. loved it. Then one day the date and time stopped syncing. I spent weeks trying to fix it, scouring the internet and tried every possible fix I could find; from fiddling with airplane mode, soft/hard resets, replaced the screen (found several people who claimed this fixed the problem) and I even went so far as to flash a Verizon ROM onto the phone I grabbed from the net. (VZW_XT926_4.1.2_9.8.1Q_62_VQW_MR-2_VQW_CFC.xml)
I've been using a backup phone for a while now but would really like my razr back. I have nothing to lose at this point so I'm willing to try anything. Assuming this is a software glitch and not a hardware problem, I would like to completely wipe out the phone. Like EVERYTHING. I don't need anyone to hold my hand but would appreciate it if someone could post some resources that I can read through/follow. Googling the topic brings up alot of info on unlocking and rooting. I feel like those are things I might want to do on a healthy phone that I just want more control over. I want to do the equivalent to my phone of what I'm familiar with on a PC. (format HDD/creating partitions/loading OS) Don't know if this is even possible with a cell phone.
Any help would be appreciated.
Edit: so my understanding of a Kernel is that it manages communications between the hardware and software. I have wondered if something went wonky with that and if I can flash a basic android kernel/OS onto my phone to see if it fixes the problem. Forgive me if I'm not using terminology right.