Just as title says. Ive tried all the fixes for it with no luck.
I dont really care for the trackball anyway, but I cant load roms without being able to scroll down.
Any suggestions xda community.
i had that problem like a week ago,didnt find any answers, i went to verizon and told them my trackball wasnt working and they were going to try and make me pay for another under my warranty,i told them that I read on many forums that it was a hardware issue and after they researched it they exchanged my phone for free.thats the only thing i can tell you to do. hopefully they can do it for you also.
It's the infamous trackball issue. I had ignored it until my came down with it a few months ago, it was around 6 months old. I called Verizon and got a replacement phone, they shouldn't charge you for anything. I couldn't see any other way around it, since I too am a rooted user. Good Luck!
i agree. its a known crappy trackball issue. call verizon and they should sent a replacement. there was an ruu that was an exe ran from your computer that should (someone correct me if i'm wrong) allow you to go back to stock on your eris if you are worried about the verizon people asking about your root. it was posted here, but i just looked and couldn't find it. trying to reup now. will edit this post with a link.
uploaded file http://www.multiupload.com/0B4EAQE25I fyi i'm not responsible if you brick your phone blah blah blah. i actually had nothing to do with writing the file, i just couldn't find it so i reposted it. it is an exe to run on a windows based computer with your eris attached via usb.
gthirty6ptime said:
Just as title says. Ive tried all the fixes for it with no luck.
I dont really care for the trackball anyway, but I cant load roms without being able to scroll down.
Any suggestions xda community.
Click to expand...
Click to collapse
Here is a brutal hack from the Eris Root forum on AF.
I works, but you need to use adb from a PC, and be comfortable working at the command line.
bftb0
I actually sent my phone rooted with KaosFroyo on it and Verizon didn't say anything! I've heard of a handful of people that have done the same.
People have sent it back no problems, but if you're worried run the RUU.
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...
Hey all,
Just a couple days ago, my track ball stopped working when I use it to scroll down. In recovery, you need to be able to scroll down to do anything. Is there a way to flash things and do nands without the track ball? I know there is Clockwork, but I don't trust it with the stories of bricking. If anything, all I need to do is be able to flash the flashback ROM so I can send it in and get a new phone.
Any remedies?
Thanks
Have a read here.
chris22_2 said:
Hey all,
Just a couple days ago, my track ball stopped working when I use it to scroll down. In recovery, you need to be able to scroll down to do anything. Is there a way to flash things and do nands without the track ball? I know there is Clockwork, but I don't trust it with the stories of bricking. If anything, all I need to do is be able to flash the flashback ROM so I can send it in and get a new phone.
Any remedies?
Thanks
Click to expand...
Click to collapse
It happened to me. I was trying to flashback to send it back...no trackball. I found that pushing on the phone with my thumb above the trackball enabled the trackball enough to flash the zip. Keep in mind I was sending the phone back to Verizon for the broken trackball, though, so I wasn't worried about breaking it further.
Chevelle1768 said:
Have a read here.
Click to expand...
Click to collapse
DoubleByte said:
It happened to me. I was trying to flashback to send it back...no trackball. I found that pushing on the phone with my thumb above the trackball enabled the trackball enough to flash the zip. Keep in mind I was sending the phone back to Verizon for the broken trackball, though, so I wasn't worried about breaking it further.
Click to expand...
Click to collapse
Thank you and thank you!
By the way, you probably should grab the recovery-RA-eris-v1.6.2-trackball-optional.img 1.7.1 version (it has all of the functionality of the "original" 1.6.2 Amon_RA; the first "trackball-not-required" version I built was based on the 1.6.2 source that actually omitted some of the menu options).
Cheers!
i have the trackball not working during recovery issue as well
I have found, and I am almost certain this will work for you, plugging your phone into your charger will get your trackball to work
If I don't have my cord to plug into the usb, I've used a paper clip to press against the top of the usb port towards the trackball and have found this to work as well
if you have any questions on the process please don't hesitate to contact me
NPH- said:
i have the trackball not working during recovery issue as well
I have found, and I am almost certain this will work for you, plugging your phone into your charger will get your trackball to work
If I don't have my cord to plug into the usb, I've used a paper clip to press against the top of the usb port towards the trackball and have found this to work as well
if you have any questions on the process please don't hesitate to contact me
Click to expand...
Click to collapse
Actually, most people find out about the problem, or it's more severe when a cord/charger is plugged in.
roirraW "edor" ehT said:
Actually, most people find out about the problem, or it's more severe when a cord/charger is plugged in.
Click to expand...
Click to collapse
Does the problem worsen over time to the point at when it does it if it's not on the charger? Cuz mine's pretty bad on the charger.
I went through this as well. The various tricks to get it to work succeed on some phones and not others, but they're worth a try. In most cases the trackball will continue to deteriorate over time and mine got to the same point where I couldn't scroll down and therefore couldn't use RA to flash. But I needed to flash it back to stock so I could get a refurb from Verizon via my warranty. At that time, I don't think this RA that doesn't require a trackball was available. I asked about if there was and I couldn't find anything about it. Thought about trying to use the RA source and build a version myself but I just didn't have the time and lord knows, screwing that up might have really borked my phone for good, so I get it go. Now that RA without the trackball is out there, I'd use it if you can get that on your phone.
But there's another very easy solution. You can download ROM Manager from the market: ROM manager will let you flash ROMs without the trackball. It uses Clockwork Recovery for flashing and I was concerned at first about the stories of CR possibly bricking phones (in fact this not really a serious risk) or maybe making it harder to return the phone to unrooted stock or something else. But in fact, ROM manager uses Clockwork by only temporarily loading CR in memory, where you can use it to flash a ROM, and it does NOT replace RA! It leaves RA intact on your phone. If you reboot, RA is there. You can use ROM manager to flash any ROM and in my case I used it to flash the easy, return to stock zip that you can find here on the Eris forum. I brought it to the Verizon store and all I had to say was the trackball died and they traded me for a refurb.
BTW, this was a few months ago and there were several threads here with stories about people calling Verizon (not the stores) with tales of woe about their Eris and getting a free upgrade to Incredibles, Moto Droids, etc. if they were very nice about asking. This might have been a time when the inventory on the Eris was low. Anyway, I tried twice times and couldn't swing it - they only offered a refurb Eris. Found a local store with the Eris in stock and did it on the spot.
Now, if an Eris is out of warranty, then the best route is to replace the trackball. There are threads on XDA with all the step by step instructions you need. These are the same trackballs that are used in many of the Blackberrys and apparently those fail frequently and there are a LOT of options available on line for about $3-$5 via Amazon, etc. And hey, you can get them in kinds of whizzy colors ;-p
Hope this helps!
Good luck!
CPCookieMan said:
Does the problem worsen over time to the point at when it does it if it's not on the charger? Cuz mine's pretty bad on the charger.
Click to expand...
Click to collapse
That's my observation and experience.
Sent from my Eris using XDA App
Oh Man!
roirraW "edor" ehT said:
That's my observation and experience.
Sent from my Eris using XDA App
Click to expand...
Click to collapse
crap! that is what I thought and this just confirmed the fate and almost certain death
I think I'm being stalked but maybe I'm not the only one.
honestly, i just wrote a giant essay on what happened and it all got deleted when i tried to submit it so im not very happy right now and dont feel like retyping it so ill just keep it short
i (tried) to format my sd card with the clockwork mod app (not recovery) but it failed and when i rebooted my phone was soopah doopah ultra mega bricked³, i believe is the technical term
it "boots" to a black screen when the battery is inserted and none of the buttons, capactive or physical, work and the only way to power it off is to pull the battery
my computer only picks up some qualcomm-usb-whatever drivers (been a while since i plugged it) which according to the internet has to do with some sort of qualcomm download mode
i was hoping to jtag it, because according to the internet, its the ultimate recovery tool, but i have no clue how to use it and cant find a good guide on the internet specifically for an evo or something related
i have a board coming, so now i need your guys help using it and getting the software i need to reload my evo
i just wanna do a 100% total restore of the entire system, since id venture to guess thats the easiest and probably only option at this point
I AM SOOPAH DOOPAH ULTRA MEGA GRATEFUL FOR ANY HELP YOU GUYS CAN PROVIDE!!!
note: i would have probably gone to sprint to get a new one a day later, but right now im deployed to afghanistan so even if there was a sprint store here i dont wanna have to set up an entire convoy and send ied clearance and all that good stuff
edit: drivers are called "QHSUSB_DLOAD" although i was pretty close to guessing the name, atleast i think so
Its not possible without usbjtag.
However, there was also another port that was being experiemented with on this phone, but I don't think anything every resolved.
It is possible. You can be our guinea pig. Search for a thread already about this. It's probably at the beginning, I remember we were going to use this to nand write, before we had root.
But it's just easier to buy insurance.
sure anything to fix this thing
i posted on it that im willing to be a test subject (http://forum.xda-developers.com/showthread.php?t=1188510)
i did have insurance... but i bricked it over here lolz
you mean usbjtag as in a usb jtag board or a subjtag nt from usbjtag.com?
if possible or you run outa luck you could try just sending it to HTC...
Seems others had this issue too.
http://forum.xda-developers.com/showthread.php?t=1041153
Guys phone was rooted and had this same issue and got a new one from HTC within 3days...
though if you get the thing to work right yourself more power to ya, and im sure the whole community will love to see it happen!
Keep us updated. Read up on that thread in here you posted in, in the Dev section that TrevE was workin on Download mode. Think he was gettin with RevSkills to use that stuff somehow. my memory is foggy though on all that since it was so long ago...
i would, but im deployed to afghanistan, so it would take FOR FREAKIN EVER to get it there and back
im gonna email htc and just say i randomly booted it and its giving me this problem and see what they say. im not expecting much but you never know
daktah said:
i would, but im deployed to afghanistan, so it would take FOR FREAKIN EVER to get it there and back
im gonna email htc and just say i randomly booted it and its giving me this problem and see what they say. im not expecting much but you never know
Click to expand...
Click to collapse
yeah. just was thinking b/c itd be with HTC that they'd have to have more options for places to ship it to for fixing than the USA for ya.
i dont even have the ability to send out mail where im stationed at and plus i think the community is close to finding a jtag restore solution (hopefully)
so i think ill just stick it out and not abandon my 1 and only 3d baby just because its in a coma right now (if you guys cant tell i freakin love this phone )
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
My brother went and flashed a custom international rom. He doesnt remember which one, not that I think it matters at this point. Ive flashed many roms, I've even bricked a few phones, but with alot of reading on the xda site, and all the help from dev's have always unbricked my phone. His samsung doesnt turn on, does not go into recovery or into download mode. Ive tried taking the battery out holding both + - vol then usb then battery. nothing. When plugged into usb without battery, light turns on, when plugged into comp , comp starts looking for a driver, so i dont think its complety bricked yet, but it comes back with this message QHSUSb_dload. Ive read up on other phones on this message, any help with how to solve this. thanks
First slap him for not reading and then go to the development section of your carrier and look for fix thread for your issue I know attention has none not sure about the other carriers.
Sent from my SAMSUNG-SGH-I747 using xda app developers app
If he's seeing QHSUSB DLOAD its hard bricked. From what I've seen looking into this, I believe some HTC's have been able to be recovered from this mode but its not possible for us w/o JTAG. Someone correct me if I'm wrong and shed some light on the subject if they have any. Very intrigued by this and think that somehow an unbrick could be done with this with the right tools/knowloedge
Randomacts said:
First slap him for not reading and then go to the development section of your carrier and look for fix thread for your issue I know attention has none not sure about the other carriers.
Sent from my SAMSUNG-SGH-I747 using xda app developers app
Click to expand...
Click to collapse
I looked at my the dev section there is no fix that I could find. So I posted the question in the proper samsung galaxy section. I dont believe there is a solution yet aside from sending it in. A few posts here and there touched base on it but I dont think anyone yet on here has eff'd there phones up to this point. Ive went through every samsung section to see if there were any similar post and nothing has really touched base, on it or ive triied it.
billard412 said:
If he's seeing QHSUSB DLOAD its hard bricked. From what I've seen looking into this, I believe some HTC's have been able to be recovered from this mode but its not possible for us w/o JTAG. Someone correct me if I'm wrong and shed some light on the subject if they have any. Very intrigued by this and think that somehow an unbrick could be done with this with the right tools/knowloedge
Click to expand...
Click to collapse
Yes I found four posts about the similar qhsusb dload, and also read about jtag, already gave my brother the website url, to contact about sending the thing in. I just havent been able to find a solution on here.
well ill have to find and reread the stuff i saw abt the htc's cuz if im not mistaken some were actually made unbrickable because of this. i was able to install drivers, and talk to the phone with a couple of things, including odin but it just hung as i expected it to. I think something could be done with this, dont seem like the typical hardbrick. let a couple more people brick this thing, if its possible someone will figure it out
billard412 said:
well ill have to find and reread the stuff i saw abt the htc's cuz if im not mistaken some were actually made unbrickable because of this. i was able to install drivers, and talk to the phone with a couple of things, including odin but it just hung as i expected it to. I think something could be done with this, dont seem like the typical hardbrick. let a couple more people brick this thing, if its possible someone will figure it out
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1522351
I believe this is the post your talking about. Anyways I just can't believe the broski actually bricked his phone, I trully thought it was damn near impossible. amazing
It is never impossible to brick a device. This is why one should know what they are doing before they do it. I mean really, he doesn't even know what rom he flashed? Flashing a device is not for everyone nor should everyone do it. If you don't understand what your doing then don't do it.
Sent for a corner cell in Arkham
is that so??
zelendel said:
It is never impossible to brick a device.
Click to expand...
Click to collapse
Tell that to AdamOutler lol
zelendel said:
It is never impossible to brick a device. This is why one should know what they are doing before they do it. I mean really, he doesn't even know what rom he flashed? Flashing a device is not for everyone nor should everyone do it. If you don't understand what your doing then don't do it.
Sent for a corner cell in Arkham
Click to expand...
Click to collapse
Ya well If I would have not rooted his phone for him, he would have never have known about xda. He's 13. live and learn.
kendmclean said:
Ya well If I would have not rooted his phone for him, he would have never have known about xda. He's 13. live and learn.
Click to expand...
Click to collapse
Well, the best thing to do would be to go to the sprint section and look at mskip's sticky with his toolkit, and load the qualcomm drivers. it's an ugly situation, but that's your best lead.
teh roxxorz said:
Well, the best thing to do would be to go to the sprint section and look at mskip's sticky with his toolkit, and load the qualcomm drivers. it's an ugly situation, but that's your best lead.
Click to expand...
Click to collapse
Ya I did that about 4 hours ago, in my devices and printers, in now says QHSUSB_DLOAD is working properly. Yet I cant get it to connect to the toolkit, to odin, I cant even find the phone with cmd. it makes a noise everytime you plug it in to the comp, well the comp does and it searches for drivers and installs them, they all installed correctly the first time aside from the one above that was fixed. Thanks though for the help, I really appreciate it.
If no other solutions work, a JTAG repair WILL unbrick your device. MobileTech Videos (www.mobiletechvideos.com) offers JTAG repair for the SGS3. I've used them to purchase a download mode jig and they have fast turn around times, great customer service, and excellent service. You really can't go wrong using them. Hope it all works out and you can get your device unbricked.
Let us know how you hard bricked it so we can do that when we need to get our phone warranty replaced without customer service seeing the custom flashed counter!
aeakin said:
If no other solutions work, a JTAG repair WILL unbrick your device. MobileTech Videos (www.mobiletechvideos.com) offers JTAG repair for the SGS3. I've used them to purchase a download mode jig and they have fast turn around times, great customer service, and excellent service. You really can't go wrong using them. Hope it all works out and you can get your device unbricked.
Click to expand...
Click to collapse
Ya i gave the broski that website this morning.thanks for the info appreciate everyone whos taken the time to throw in some ideas.
CrimsinX said:
Let us know how you hard bricked it so we can do that when we need to get our phone warranty replaced without customer service seeing the custom flashed counter!
Click to expand...
Click to collapse
Either this is your weak attempt at humour or you never read the entire thread, like I said in on the first page, He flashed a international rom. I dont need to recap the entire 2 pages, the fact that you posted that comment, like why would anyone want to brick their phone for warrenty if its working fine. just stupid. I appreciate your meaningless contribution to a site where some people try to learn a thing or 2. I would suggest you try taking the site more seriously. And if you cant, have some respect for the people that do. thanks again. take care