Related
Well, i ****ed up my phone.
Trying to bring it back alive failed, so I'm going to bring it
back to T-Mobile.
Does someone know a very good lie I can tell them, so I don't have to pay for the repair.
When i try to start my phone, i see a HTC splashscreen, and thats it. Normally it start with a T-Mobile splashscreen. Can they see i tried flashing my phone, or is that an assumption they make.
CCRDude said:
I don't think using bold letters and the clear word "lie" will help you a lot... you just highlight that you ask for illegal help
Maybe you should take a look at the bricked-devices topic for a chance to revive it?
Click to expand...
Click to collapse
I have spent the last 3 days 30 hours orso fixing my phone. Revive is something my dead baby won't do.
vayip said:
I have spent the last 3 days 30 hours orso fixing my phone. Revive is something my dead baby won't do.
Click to expand...
Click to collapse
enter the bootloader; try to flash a regular update from your provider to it.
vayip said:
Well, i ****ed up my phone.
Trying to bring it back alive failed, so I'm going to bring it
back to T-Mobile.
Does someone know a very good lie I can tell them, so I don't have to pay for the repair.
When i try to start my phone, i see a HTC splashscreen, and thats it. Normally it start with a T-Mobile splashscreen. Can they see i tried flashing my phone, or is that an assumption they make.
Click to expand...
Click to collapse
I did the same with my Vodafone (UK). I just told them I'd hard reset and this is all I can see on the screen (don't get stroppy etc).
Mine will be back Tuesday, warranty repaired.
Vod UK use an outside repair centre so will probably be the same as T-Mobile if you are in UK. Mine needed a new motherboard, but there is a bit of a shortage in the UK (too many bricks???). I guess it depends on the outside service centre contract whether they charge you or T-mobile (and maybe also because I had warranty and Insurance)..
Just go in and plead ignorance, but if they want to charge you, ultimately it was you that ****ed it and not them
Toast it in the microwave for 5 seconds!
boz said:
Toast it in the microwave for 5 seconds!
Click to expand...
Click to collapse
That's a new one - when car radio codes first came out they always said to put them in the freezer then stroke the chips legs to erase the cmos... never worked for me, but I'd probably get away with the microwave thing with 3 kids at home!!!
@ Olipro
If you mean the SD-card flashing, T-Mobile Holland doesn't have an update available. There is an T-Mobile Holland ROM available, but the image is older than the image installed on my phone. When checking the ROM in the white screen, it says not allow. I think i need ROM 1.21.114.3 from T-Mobile if I want to do the SD-card flash.
I only have access to the bootloader, I have bootloader 1.04, and I have access to KITL mode, but the Windows CE Platform Builder fix also doesn't work
@ ach2
I was thinking also something like that. That I hard reset my phone and now it's broke. I was also thinking something like I left my phone on the charger for the weekend, and when I came back I did a soft reset because it wouldn't go on and know I only see a HTC splash screen.
vayip said:
When i try to start my phone, i see a HTC splashscreen, and thats it. Normally it start with a T-Mobile splashscreen. Can they see i tried flashing my phone, or is that an assumption they make.
Click to expand...
Click to collapse
Can you think of a good reason whey the boot screen has changed from the normal T-Mobile one... just hope they don't turn on the phone. Did you try Olipro's suggestion?
@ Wam7
The T-Mobile splash screen is in the extended ROM. If the extended ROM is ****ed up like mine is, it probably goes back to its embedded splash screen, and that's the one from HTC. But thats not what I'm going to say, I'm going to say how should I know.
If I remember correctly a guy has managed to dump the ROM from a Hermes and flash it to the phone... saw a thread somewhere here. If that's the case then you should just need a ROM from a fellow dutch T-Mobile owner with the newer ROM. I take it your phone is not SuperCID
vayip said:
@ Olipro
If you mean the SD-card flashing, T-Mobile Holland doesn't have an update available. There is an T-Mobile Holland ROM available, but the image is older than the image installed on my phone. When checking the ROM in the white screen, it says not allow. I think i need ROM 1.21.114.3 from T-Mobile if I want to do the SD-card flash.
I only have access to the bootloader, I have bootloader 1.04, and I have access to KITL mode, but the Windows CE Platform Builder fix also doesn't work
Click to expand...
Click to collapse
if you have 1.04; run the RUU on your computer; you will get a "Vender ID Error" immediately ignore this and run the updater AGAIN (do not touch or unplug your PDA) after doing this a second time it will begin to flash
vayip said:
Well, i ****ed up my phone.
Trying to bring it back alive failed, so I'm going to bring it
back to T-Mobile.
Does someone know a very good lie I can tell them, so I don't have to pay for the repair.
When i try to start my phone, i see a HTC splashscreen, and thats it. Normally it start with a T-Mobile splashscreen. Can they see i tried flashing my phone, or is that an assumption they make.
Click to expand...
Click to collapse
seriously this is why MS and Carriers HATE us
Olipro said:
if you have 1.04; run the RUU on your computer; you will get a "Vender ID Error" immediately ignore this and run the updater AGAIN (do not touch or unplug your PDA) after doing this a second time it will begin to flash
Click to expand...
Click to collapse
I did what you said. I connected the phone to my laptop in bootloader. I started the RUU from WMXL 0.20. My phone goes to the white screen and at 0% i get a message on my laptop the connection got disconnected. So i start the RUU again, but again the message my connection got disconnected.
So still working on a good lie.
@vayip: sounds like a problem with the USB on your laptop. Try using a different computer. BL1.04 will let you flash any OS provided your NAND isn't full of bad blocks. You're a long way away from returning your device to Tmo IMO.
On the new computer:
direct USB connect to rear port only no usb hubs
pc running windows XP
turn off screensaver/Powersave mode
close all other apps
hands off the computer for the 25 minutes or so that it takes
Sleuth255 said:
@vayip: sounds like a problem with the USB on your laptop. Try using a different computer. BL1.04 will let you flash any OS provided your NAND isn't full of bad blocks. You're a long way away from returning your device to Tmo IMO.[/list]
Click to expand...
Click to collapse
Does it matter if the phone is simlocked or not. My phone is not SuperCID.
The strange thing than is, i have 2 laptops. Doing the upgrade don't work on both.
Will try a normal pc then. Maybe more luck.
Follow Oli's advice about retrying the update if you get an initial vendor ID error. BL1.04 will flash any rom without SuperCID due to a bug.
You might want to jump in with mtty first to see if your NAND is full of bad blocks. If it is then your device is toast fttb.....
spiritofseth said:
seriously this is why MS and Carriers HATE us
Click to expand...
Click to collapse
I completely agree! If you ****ed up your device, than you should have the courage to stand up for it and if it was not your fault, than just tell them the truth! But suggestions like "put it in the microwave for 5secs".... come on
And just a small hint: If you (for example) really put it in the microwave, than you'll better pray that no technician ever analyses your device - if so you could get into serious trouble, mate.
Btw, if you microwave it, you probalby need a new microwave too.
Edit: And i dont think its warranty would cover "I just put my Phone in there"
"So still working on a good lie."
Doesn't breaking your phone through your own actions and then getting it repaired/ replaced for free by telling lies make you a liar and a thief?
I trashed 8525, and that sucks, but it was my fault so I have to pay for it.
In my adventures flashing Roms, I've only bricked 1 Hermes (Cingular 8525). I actually told the local Cingular shop that I broke it 2 weeks after I bought it. The manager told me to bring it in and she replaced it under the 30 day in-store return policy. I was suprised because I had caused the bad NAND Block problem on the device but she said that since I was able to get an official Cingular Rom flashed onto it and it booted into WM5 (just wouldn't do anything because of memory errors).
Now I also have a very good working relationship with this store. I've gotten a phone about every 6 months from them over tha past 2 years and have given them some great info regarding WM5 devices (reccomendations on screen protectors, software & cases etc). I have 3 lines (2 with Data) and even if they don't know me by name eveyone in the store knows me by reputation.
Tomorrow I will have my spare Hermes (also 8525) so we can begin experimenting with getting some additional storage memory without risking bricking my primary phone.
The way I see it, we are taking a chance when we modify our devices.
I've had to return 2 Wizards for Warranty replacement to Cingular, both were CID Unlocked but the problems were unrelated to flashing Roms (One was because the touch screen developed a dead spot the other was because of Radio hardware issues).
The problem: I flashed a radio to my device that is (obviously) incompatible with my device (if you really want the details, its embarassing, but I'll post if necessary). My phone freezes on bootup, and never initializes the Radio/ROM (and for good reason).
This is what happens now: If my phone is off, I can turn it on, but I only get the first boot up screen, and the red numbers in the bottom right-hand corner never appear. At that point, I cannot turn off my phone without taking out the battery. If I take out the battery and put it back in, and attach the phone to a charger (or USB cable), the light on the phone will "breathe", as if its charging. However, if I then disconnect the phone, the light will CONTINUE breathing.
I also cannot turn on the phone while its connected to either the charger or USB cable.
My phone is Hard-SPL'ed and Security Unlocked. But the real issue I'm having is that I can't get into Bootloader to flash something else. Apparently, I've corrupted the Bootloader. When I turn the phone on, and press the reset button while holding Vol-down, the phone just goes black.
I might be okay getting a warranty exchange if not for this: I can still hard reset my phone. It doesn't make any sense to me, but when I turn it on, I can do the soft-reset-button, Vol-down, Action button combo, and my phone flashes through Bootloader to give the the hard reset menu. It flashes that screen just long enough to see that my phone has 1.90Olinex as the SPL. So, I think I may be screwed, unless someone here can help.
My wife is very . . . upset . . . about this, and is worried that we'll have to spend money because of my continuous "tinkering" with my phone.
Any help anyone can offer is greatly appreciated.
I know this is my own stupid fault, and I should've known better, but it would be nice to get confirmation from the experts here that I'm just going to have to chalk one up in the "L" column at this point.
Q
Have you tried to flash from the SD card?
Hi Captain_Throwback,
Try copying Raph Radio 1.11.25.01 to the root of a FAT32 SD Card ... you'll need to rename the .NBH to RAPHIMG.NBH.
Pull the SIM out of the phone and power it back on as per usual; I've noticed that the phone "blacks out" for a bit but then switches to flash mode.
Good luck.
PS: suggest getting the large carry-on with the wheels for the guilt trip - heaven knows it's come in handy for me
That's a bummer, man. You gotta at least 'fess up part of the story to prevent someone else from falling into the same trap (however unlikely that may be). And maybe, just maybe, it will help someone else figure out how to fix your problem.
What radio did you try and flash.
Hopefully it wasn't the new Rhodium radio? Or a Rose radio?
I have done this a few times on my tilt, all I did was put it into the boot loader, it worked from hard reset screen as well, and flashed the rom via activesync. I am assuming that you are not able to get a sync, or have you tried yet? I know my fize will also sync [to flash] from bootloadr.
Captain_Throwback said:
The problem: I flashed a radio to my device that is (obviously) incompatible with my device (if you really want the details, its embarassing, but I'll post if necessary). My phone freezes on bootup, and never initializes the Radio/ROM (and for good reason).
This is what happens now: If my phone is off, I can turn it on, but I only get the first boot up screen, and the red numbers in the bottom right-hand corner never appear. At that point, I cannot turn off my phone without taking out the battery. If I take out the battery and put it back in, and attach the phone to a charger (or USB cable), the light on the phone will "breathe", as if its charging. However, if I then disconnect the phone, the light will CONTINUE breathing.
I also cannot turn on the phone while its connected to either the charger or USB cable.
My phone is Hard-SPL'ed and Security Unlocked. But the real issue I'm having is that I can't get into Bootloader to flash something else. Apparently, I've corrupted the Bootloader. When I turn the phone on, and press the reset button while holding Vol-down, the phone just goes black.
I might be okay getting a warranty exchange if not for this: I can still hard reset my phone. It doesn't make any sense to me, but when I turn it on, I can do the soft-reset-button, Vol-down, Action button combo, and my phone flashes through Bootloader to give the the hard reset menu. It flashes that screen just long enough to see that my phone has 1.90Olinex as the SPL. So, I think I may be screwed, unless someone here can help.
My wife is very . . . upset . . . about this, and is worried that we'll have to spend money because of my continuous "tinkering" with my phone.
Any help anyone can offer is greatly appreciated.
I know this is my own stupid fault, and I should've known better, but it would be nice to get confirmation from the experts here that I'm just going to have to chalk one up in the "L" column at this point.
Click to expand...
Click to collapse
Damn I'm sorry to hear about your issue and i feel for ya because I did some stupid **** myself a lil' while back if you remember. Your advice to reflash the oem rom worked for me 100%. Have you tried hard resetting and then trying to get into bootloader mode?
AllTheWay said:
What radio did you try and flash.
Hopefully it wasn't the new Rhodium radio? Or a Rose radio?
Click to expand...
Click to collapse
Ok, I'll tell you . . . it wasn't a Rose radio (I know P1Tater bricked his phone that way) . . . but I figured, the Rhodium, its got the same hardware, right? I mean, T-Mobile is a GSM carrier . . . If I patch it for Raph, it may work . . . even though the radio number is so much different . . . I should still be able to get into Bootloader if it doesn't work, because I'm HardSPL'ed . . .
But no. I can't get into Bootloader. Believe me, I've tried. Every time I try, the phone just goes black. And I have a nice stock AT&T ROM on my Storage Card ready to flash, if only I could get it onto the phone.
I tried plugging into the computer, but it won't recognize the phone at all.
I wish it was REALLY bricked, but the fact that I can still hard reset it is very disappointing.
Captain_Throwback said:
Ok, I'll tell you . . . it wasn't a Rose radio (I know P1Tater bricked his phone that way) . . . but I figured, the Rhodium, its got the same hardware, right? I mean, T-Mobile is a GSM carrier . . . If I patch it for Raph, it may work . . . even though the radio number is so much different . . . I should still be able to get into Bootloader if it doesn't work, because I'm HardSPL'ed . . .
But no. I can't get into Bootloader. Believe me, I've tried. Every time I try, the phone just goes black. And I have a nice stock AT&T ROM on my Storage Card ready to flash, if only I could get it onto the phone.
I tried plugging into the computer, but it won't recognize the phone at all.
I wish it was REALLY bricked, but the fact that I can still hard reset it is very disappointing.
Click to expand...
Click to collapse
This happened to me (sort of.) I flashed a diamond radio to my fuze... without security unlocking it first. Symptom wise, Exact same thing happened. I was able to (after days of tinkering) get it into bootloader from the hard reset screen. I just kept pressing the Hard rest sequence over and over while connected to USB. I noticed, one time, I got the USB at the bottom. Don't know how, don't know why, it just happened, I was then able to flash the Stock Cing ROM. Wierd stuff, But lucky. Hope you get it back on board. Is it insured? Because it would really suck if someone stole your bricked fuze.
Intertrochanterica said:
This happened to me (sort of.) I flashed a diamond radio to my fuze... without security unlocking it first. Symptom wise, Exact same thing happened. I was able to (after days of tinkering) get it into bootloader from the hard reset screen. I just kept pressing the Hard rest sequence over and over while connected to USB. I noticed, one time, I got the USB at the bottom. Don't know how, don't know why, it just happened, I was then able to flash the Stock Cing ROM. Wierd stuff, But lucky. Hope you get it back on board. Is it insured? Because it would really suck if someone stole your bricked fuze.
Click to expand...
Click to collapse
It is insured, and paying $125 is better than having to buy a brand new phone, but if I can avoid spending money, my wife would be much happier .
I can hard reset just fine . . . if only the phone would stay on the bootloader screen when doing that . . . but it doesn't. I assume the bootloader has been corrupted, which is why the phone blacks out when trying to enter bootloader mode. I'll keep trying, I guess. I can't make it any worse. Actually, if I could, I'd be better off, so that way they can't find out my phone is Hard-SPL'ed.
Captain_Throwback said:
I can hard reset just fine . . . if only the phone would stay on the bootloader screen when doing that . . . but it doesn't. I assume the bootloader has been corrupted, which is why the phone blacks out when trying to enter bootloader mode. I'll keep trying, I guess. I can't make it any worse. Actually, if I could, I'd be better off, so that way they can't find out my phone is Hard-SPL'ed.
Click to expand...
Click to collapse
Try plugging it into a car battery, or something like that, and fry the sucker. That's my only piece of advice.
Captain_Throwback said:
I can't make it any worse. Actually, if I could, I'd be better off, so that way they can't find out my phone is Hard-SPL'ed.
Click to expand...
Click to collapse
You could make it worse if you get the white sticker wet and make it turn pink, but that would be very bad for you.
You are at the point to where you cant move beyond your current predicament in wither way. Im afraid I see no other alternative than to pay the $125.
Maybe you could sell your Fuze on Ebay for 125 to cover your insurance cost and you could make a notation on the Ebay site saying something like 'PARTIALLY USED FUZE' like that Carfax commercial does.
update
My phone is still bricked, but I'm taking it to a repair shop after work, where I'll find out whether I'll be getting a free warranty replacement, or paying $125 for an insurance replacement. At least I've been able to successfully determine that a Rhodium radio cannot be flashed to a Raphael. So no one else has to try it .
Keep us updated dude. Also, if you slip the guy $50 he may do the free warranty replacement for you... it might save you $75 and you wont have to use up one of your insurance claims.
Captain_Throwback said:
My phone is still bricked, but I'm taking it to a repair shop after work, where I'll find out whether I'll be getting a free warranty replacement, or paying $125 for an insurance replacement. At least I've been able to successfully determine that a Rhodium radio cannot be flashed to a Raphael. So no one else has to try it .
Click to expand...
Click to collapse
Crap, sorry to hear that. HAAH, just walk into the ATT store and say," I tried turning the phone on and this is what happened." And that you have never heard of XDA forums, roms, and though a radio was only for people in trucks or that wear camo.
iceman4357 said:
Crap, sorry to hear that. HAAH, just walk into the ATT store and say," I tried turning the phone on and this is what happened." And that you have never heard of XDA forums, roms, and though a radio was only for people in trucks or that wear camo.
Click to expand...
Click to collapse
That might work, if I hadn't bought the phone from my best friend, who just happens to manage an AT&T store. He actually knows that I had a custom ROM on my phone, and called ahead to the repair shop to let them know I was coming, and he said hopefully they won't notice the SPL in my bootloader if they try and hard reset it. So it is possible they'll just give the phone a cursory look to make sure its really not working, and then go ahead with a warranty replacement. I'll be sure to let everyone know what happens. In the meantime, the word of the day is "dumbass", LOL.
Farmer Ted said:
Try plugging it into a car battery, or something like that, and fry the sucker. That's my only piece of advice.
Click to expand...
Click to collapse
That's what I would do.
Captain_Throwback said:
My phone is still bricked, but I'm taking it to a repair shop after work, where I'll find out whether I'll be getting a free warranty replacement, or paying $125 for an insurance replacement. At least I've been able to successfully determine that a Rhodium radio cannot be flashed to a Raphael. So no one else has to try it .
Click to expand...
Click to collapse
Honestly I would not take it to the repair shop.
Here is what I would do. Call the warranty replacement department at AT&T. 1-800-801-1101. Tell them that you woke up and now your phone won't turn on. Once you go through all the steps they have to do to fix it, then they will ship you a replacement Fuze right away. The refurbished Fuze will have everything except for a battery and a back cover. Typically when I did this I received a new one the next day that I called.
Now take your battery out of your phone and your SIM card and microSD card. Put your phone in the microwave for 2 seconds. Walla. Now it's bricked and AT&T will have no way to tell if you have HardSPL or a cooked ROM on your phone. Trust me. It will work.
When you get your new phone just send the phone back in packing material that they provide to you and you won't have to spend any money to get a new phone or spend money to fix a phone.
Just do what I told you about. I promise it will work. Just trust me. I've done it before and it worked like a charm. No worries. Trust me, I'm not trying to lead you down the wrong path. I'm trying to get you a replacement just like I got when I bricked my last fuze trying out different radios. And use the phone number that AllTheWay posted just above me once you do what I told you.
P1Tater said:
Just do what I told you about. I promise it will work. Just trust me. I've done it before and it worked like a charm. No worries. Trust me, I'm not trying to lead you down the wrong path. I'm trying to get you a replacement just like I got when I bricked my last fuze trying out different radios. And use the phone number that AllTheWay posted just above me once you do what I told you.
Click to expand...
Click to collapse
I'm curious what it is you told him, in case i'm in a similar position at any point !!
Lemme kno please here or PM is cool!
Thx
JFlitt
AllTheWay said:
That's what I would do.
Honestly I would not take it to the repair shop.
Here is what I would do. Call the warranty replacement department at AT&T. 1-800-801-1101. Tell them that you woke up and now your phone won't turn on. Once you go through all the steps they have to do to fix it, then they will ship you a replacement Fuze right away. The refurbished Fuze will have everything except for a battery and a back cover. Typically when I did this I received a new one the next day that I called.
Now take your battery out of your phone and your SIM card and microSD card. Put your phone in the microwave for 2 seconds. Walla. Now it's bricked and AT&T will have no way to tell if you have HardSPL or a cooked ROM on your phone. Trust me. It will work.
When you get your new phone just send the phone back in packing material that they provide to you and you won't have to spend any money to get a new phone or spend money to fix a phone.
Click to expand...
Click to collapse
Agree with this. If your friend works at the store and knows what you have done, I wouldnt go there. Call the number, fry the damn phone and get a new one. We need you back on your feet to help solve ROM issues my friend.
the touchscreen on my eris has been going unresponsive until i wack the side of the phone with my palm, anyone else have this happen or know of a fix?
Yea dude, contact verizon for a warranty exchange.
well the phone has some case damage because of a bicycle crash, but this problem started before that
It happens...
My first Eris lost the ability to sense anything on the bottom row...and the Verizon rep that I talked to even mentioned that it was a pretty common theme with the Eris.
Thankfully, the second one has been great, but replacement was the only real option. For a while I was using a different homescreen that didn't require hitting the bottom left, but ultimately, it was just a kludge.
ended up getting a lg ally second hand to hold me over till my upgrade in november. not a bad phone but theres only really one custom rom for it. i miss my eris though, and im going to miss the custom rom community.
Sadrak86 said:
My first Eris lost the ability to sense anything on the bottom row...and the Verizon rep that I talked to even mentioned that it was a pretty common theme with the Eris.
Thankfully, the second one has been great, but replacement was the only real option. For a while I was using a different homescreen that didn't require hitting the bottom left, but ultimately, it was just a kludge.
Click to expand...
Click to collapse
Holy crap thats exactly what mine is doing, however it does respond I just have to push harder and hope it detects the right letter... for example I try to push C and it will detect F or the space bar. annoying. Dont think I can get a warranty on it though, its rooted and flashed to cricket.
PimpTwzt said:
Holy crap thats exactly what mine is doing, however it does respond I just have to push harder and hope it detects the right letter... for example I try to push C and it will detect F or the space bar. annoying. Dont think I can get a warranty on it though, its rooted and flashed to cricket.
Click to expand...
Click to collapse
If it's still under one year old you can use the FlashBack21 v2 ROM in the Development forum and probably return it under warranty. Of course, check with the manufacturer first.
First make a nandroid because if you warranty the phone they'll probably have you keep your old SD card, so you can restore that nandroid to your new phone and pick up as if nothing happened. If under Amon RA instead of Clockwork Mod you'll need to rename the folder that the nandroid is in to the serial # of the new phone.
FlashBack21 v2 is actually an unrooted ROM that'll restore any Eris back to the latest (March) OTA release of 2.1. It's your choice if you want the version that flashes the radio or not. Technically, with the radio flashed it's even closer to stock. The ROM does not touch the bootloader. It will restore the stock recovery, so for all intents and purposes, it'll most likely be close enough. You can restore an S=ON bootloader, AFAIK, although I don't know the details off the top of my head, but it really shouldn't be necessary.
I did a warranty return still with Amon RA recovery on it, and others have had similar luck, so FlashBack should be more than enough.
Top and bottom
Yeah, I got my Eris from my brother for free because he was having an issue with the top and bottom portions of the screen not registering. I ordered a 44 dollar replacement screen from EBay, took it all apart, replaced it and all was good. Don’t know if that’s what's going on with yours though.
If you have the guts to open it up (and void the any warranty you might have), that might be an option.
Hello everyone,
Firstly, I did not find a board dedicated to the S5660. So I posted it here.
Today, I tried to backup my current installation of Android to my SD. I used
a guide on androidpolice(dot)com, while searching for "complete android backup" in Google.
My phone had to be rooted, which it was, so I went on to download and install Clockworkmod's ROM Manager. I opened it up, fixed the permissions and made a backup. Before I could make one, I had to pick a phone model. However, these were all very strange types or brands I never even heard of.
I randomly picked one, and my phone NOT being listed should have served as a warning but alas, and the app started backing up. After it was done, it all seemed normal so I pressed "home" to go back to my main screen and pressed the "lock/power" button so my screen would turn off. I put the phone in my pocket.
Exactly 2 minutes later, I pull out my phone and I notice the screen is black, I push the lock/power button: nothing happens. I hold the lock/power button in the expectation that the phone will boot up since it might have been shut down accidentally. Nothing happens.
I remove battery, re-insert battery. I repeat this over a dozen or so times to no avail. I try the download or safe boot key-combinations (volume down + home + power) and nothing helps.
It's as if either all the keys are broken, something went seriously wrong in the interior hardware or hopefully, (the most simple possibility) my battery gave the ghost.
I went to the shop where I bought the Galaxy Gio and told them about the issues I had, they said they were going to send it to a Samsung Service Center for repairs. After I went home and had browsed the Internet for some possible solutions, I returned to the shop to try out several of the tricks that were listed (inserting battery on the exact same time when you press the buttons), nothing worked.
Does this smell to bricking or just a dead battery?
Before any conclusions are made (it sounds like its bricked though)...dead battery?... Did you try charging it?
Theonew said:
Before any conclusions are made (it sounds like its bricked though)...dead battery?... Did you try charging it?
Click to expand...
Click to collapse
It happened while I was at school, I immediately went to the shop and the guy helping me said he had plugged it in for a short while. I guess I believe him since I did not see it but he said the phone did nothing.
But how come a software malfunction can mess up the physical buttons like the power/volume or lock buttons?
Darmvlinder said:
But how come a software malfunction can mess up the physical buttons like the power/volume or lock buttons?
Click to expand...
Click to collapse
If the software of a device is corrupted, then the hardware won't work properly (if at all). Example: you flash a rom for a device with one button and your device has five, then of course the software wouldn't recognize the other buttons (this is just an example of the hardware part cause if you actually did that, your device wouldn't even start). Also, you said that you just randomly chose one made for another device, for future reference: NEVER flash a kernel, rom, etc. not made for your device or atleast not stated to work on your device.
Theonew said:
If the software of a device is corrupted, then the hardware won't work properly (if at all). Example: you flash a rom for a device with one button and your device has five, then of course the software wouldn't recognize the other buttons (this is just an example of the hardware part cause if you actually did that, your device wouldn't even start). Also, you said that you just randomly chose one made for another device, for future reference: NEVER flash a kernel, rom, etc. not made for your device or atleast not stated to work on your device.
Click to expand...
Click to collapse
Yes, I figured this when I tried to do the actual backup but it seems I was too stupid to stop the entire process.
I have already given it to the store as they will send the phone to a Samsung Service Center. Do you know how the processes of repairing for such phones work?
Also, if the phone is a total brick, it cannot be recovered whatsoever?
Darmvlinder said:
Yes, I figured this when I tried to do the actual backup but it seems I was too stupid to stop the entire process.
I have already given it to the store as they will send the phone to a Samsung Service Center. Do you know how the processes of repairing for such phones work?
Also, if the phone is a total brick, it cannot be recovered whatsoever?
Click to expand...
Click to collapse
The best thing to do is hope they can't repair it . If they happen to get it to work and find out you rooted it, they will just return it to you the way it is now. I hope you didn't tell the guy how this happened...
P.S. - No, I don't know the process they use to recover something like this. I'm no expert in recovering hard bricks (know a few stuff, but not in this case).
Theonew said:
The best thing to do is hope they can't repair it . If they happen to get it to work and find out you rooted it, they will just return it to you the way it is now. I hope you didn't tell the guy how this happened...
P.S. - No, I don't know the process they use to recover something like this. I'm no expert in recovering hard bricks (know a few stuff, but not in this case).
Click to expand...
Click to collapse
The guy asked me whether I had ever let the phone come into contact with water or fluids or if I ever let it fall down to the floor, neither of which have happened in the past. I also told him an update through Kies went awry and caused the system to be unstable till the crash of today.
The dude seemed pretty confident in that the warranty would cover. I don't know. I feel like a giant moron, to be honest.
Darmvlinder said:
The guy asked me whether I had ever let the phone come into contact with water or fluids or if I ever let it fall down to the floor, neither of which have happened in the past. I also told him an update through Kies went awry and caused the system to be unstable till the crash of today.
The dude seemed pretty confident in that the warranty would cover. I don't know. I feel like a giant moron, to be honest.
Click to expand...
Click to collapse
Another future reference (although you dodged the bullet here): never tell your manufacturer (or whoever is supposed to look after the warranty of your device,etc.) that you rooted (or even tried to root) your device. Well, you just have to hope for the best now .
Theonew said:
Another future reference (although you dodged the bullet here): never tell your manufacturer (or whoever is supposed to look after the warranty of your device,etc.) that you rooted (or even tried to root) your device. Well, you just have to hope for the best now .
Click to expand...
Click to collapse
I just sat through a Live Chat session with Samsung. Even though Google does not oppose rooting, Samsung effectively makes a deal out of it. I told him the same story, that an update through Kies made several things pop up on my phone which I did not understand etc. etc.
I am hoping for the best. But I am befriended with someone working in the store that sold the phone to me. He said most techs won't bother with low-budget smartphones (as in trying to grab you by the balls) and will much rather flash the phone with Samsung stock ROM.
Ok so, I'm bumped and this morning my screen cracked, and became unresponsive to touch, but was acting as if I was making selections. (as in Pandora started playing on its own because I had the widget on my homescreen and I couldn't get it to stop without a battery pull). I have insurance on the phone so I can get a replacement, but its on backorder.
Now before I send it in for a replacement, I'm wondering if anyone has any ideas as to how to remove the bumped TWRP, and go back to stock recovery, without a touchscreen lol. I can't even unlock my phone on my own...sometimes it will do it itself, but that's only if I'm lucky :/ I think right now as it is, I'm stuck. But I'd really like to send it back without it being bumped, in case of voided warranty purposes and me not getting a phone, or even worse, them finding the method to achieve the bumped unlock, and then them end up patching it!!
What do you guys think? Any ideas or feedback would be greatly appreciated! Thank you!
You're going to have to try and do this blind, but how about tot city to reflash everything to stock?
Here's a link: http://forum.xda-developers.com/verizon-lg-g3/development/tot-vs985-10b-share-t2832488
There are instructions on how to go into download mode on the flash tool by using your volume & power key. The flash tool will probably tell you when/if you have a connection. Just make sure you have the lg drivers installed and you should be able to flash the tot file and get your phone back to stock. Good luck
startswithPendswithOOH said:
You're going to have to try and do this blind, but how about tot city to reflash everything to stock?
Here's a link: http://forum.xda-developers.com/verizon-lg-g3/development/tot-vs985-10b-share-t2832488
There are instructions on how to go into download mode on the flash tool by using your volume & power key. The flash tool will probably tell you when/if you have a connection. Just make sure you have the lg drivers installed and you should be able to flash the tot file and get your phone back to stock. Good luck
Click to expand...
Click to collapse
Thank you so much for that suggestion! I'll be sure to give that a shot in a bit and see how it goes! No screen selections will have to be made in the process, other than signing in once its up and running, correct?
Yes. It should just flash once you get it connected and hit a button on the flash tool.
Take a look at this link as well just in case the other link doesn't help. It has good visuals to help you out some more:
http://www.androidrootz.com/2014/07/how-to-unroot-lg-g3-all-variants.html
FYI- at step 2, hold your vol up button for @ 5 sec and then plug in your USB - it should vibrate when it connects... I believe. Doing it blind sucks but I'm sure you'll get it.
startswithPendswithOOH said:
Yes. It should just flash once you get it connected and hit a button on the flash tool.
Take a look at this link as well just in case the other link doesn't help. It has good visuals to help you out some more:
http://www.androidrootz.com/2014/07/how-to-unroot-lg-g3-all-variants.html
FYI- at step 2, hold your vol up button for @ 5 sec and then plug in your USB - it should vibrate when it connects... I believe. Doing it blind sucks but I'm sure you'll get it.
Click to expand...
Click to collapse
Man thanks again for that suggestion!!! I knew about it but figured since I had an unresponsive screen, that I wouldn't be able to complete the process and because I've never had to reset this particular phone before, I just wasn't 100% sure it would work. Thankfully to your suggestion it did and is now sitting on the starting screen. Just what I needed.:good::good::highfive::victory:
nlysurferdude03 said:
Ok so, I'm bumped and this morning my screen cracked, and became unresponsive to touch, but was acting as if I was making selections. (as in Pandora started playing on its own because I had the widget on my homescreen and I couldn't get it to stop without a battery pull). I have insurance on the phone so I can get a replacement, but its on backorder.
Now before I send it in for a replacement, I'm wondering if anyone has any ideas as to how to remove the bumped TWRP, and go back to stock recovery, without a touchscreen lol. I can't even unlock my phone on my own...sometimes it will do it itself, but that's only if I'm lucky :/ I think right now as it is, I'm stuck. But I'd really like to send it back without it being bumped, in case of voided warranty purposes and me not getting a phone, or even worse, them finding the method to achieve the bumped unlock, and then them end up patching it!!
What do you guys think? Any ideas or feedback would be greatly appreciated! Thank you!
Click to expand...
Click to collapse
If you have insurance then your G3 being bump'd should not make a bit of difference. I have returned several unlocked and rooted phones to Asurion with no problem. You're paying for insurance mainly for physical damage. Your screen is obviously cracked and damaged due to that so there should be no worries. Also, if your insurance provider wanted to try and figure out how the Bump method works they could easily get their own G3 and Bump it. Having your Bump'd phone is not going to give them any more of an inside look into Bump than if they got their own device and did what everyone else has done.
acparker18 said:
If you have insurance then your G3 being bump'd should not make a bit of difference. I have returned several unlocked and rooted phones to Asurion with no problem. You're paying for insurance mainly for physical damage. Your screen is obviously cracked and damaged due to that so there should be no worries. Also, if your insurance provider wanted to try and figure out how the Bump method works they could easily get their own G3 and Bump it. Having your Bump'd phone is not going to give them any more of an inside look into Bump than if they got their own device and did what everyone else has done.
Click to expand...
Click to collapse
Ahhh thank you for that bit of info that would have been great to know earlier (for my own sanity's sake lol) but at the very least, I have wiped all my data clean which I would have preferred to do anyways before sending it back
I've returned 3 Samsung captivate phones to att that still had Cyanogenmod or MIUI on them, same with the 7 or 8 Samsung Galaxy S 3 phones I brought back on my insurance plan with Best Buy Mobile. They request it be stock, but if the screens broke they can't check it until the screen is fixed, at which point they will just flash it anyway.
Sent from my VS985 4G using XDA Free mobile app
Doesn't the insurance cover it, if it's lost or stolen? Sounds to me like you lost it.
It's good to know that they accept devices with 3rd party/modified software. I was never sure if the insurance companies did or not. If you send it to a factory service center they'll tell you your warranty is void for sure. Its all about finding a way to charge you $.
But I do think it's wise to wipe your device if you can. I used to do phone repairs for a large anonymous Korean company and I've seen a lot of amateur porn, credit card info, social security #'s and other personal info that really shouldn't be out there. People forget what is on their phones a lot of the time. Definitely take the time to wipe your device before you send it somewhere. Its ok to be a little paranoid sometimes