Hey I've got a huge problem.
I think I just accidently flashed a ROM for a different phone and now the phone doesn't turn on anymore.
Is there anything I can do? Oh god I'm freaking out.
Thanks
rest0ck said:
Hey I've got a huge problem.
I think I just accidently flashed a ROM for a different phone and now the phone doesn't turn on anymore.
Is there anything I can do? Oh god I'm freaking out.
Thanks
Click to expand...
Click to collapse
Does it go into bootloader or recovery? If no try LG flashtool and if that doesn't work. You bricked it
I'm not sure if I did that right. I installed the driver + the Tool .. hold down volume up + plug cable in = nothing happens.
Can't boot into recovery either. Nothing happens.
Oh man I'm an Idiot
Is there any way to get to the data? Even if it's opening the device?
rest0ck said:
I'm not sure if I did that right. I installed the driver + the Tool .. hold down volume up + plug cable in = nothing happens.
Can't boot into recovery either. Nothing happens.
Oh man I'm an Idiot
Is there any way to get to the data? Even if it's opening the device?
Click to expand...
Click to collapse
You need it to power up to get the data
Sent from my Nexus 5 using Tapatalk
@rest0ck
Hold down power + vol down button for about 30 seconds and see if the bootloader shows up? if not, you can try accessing the secondary bootloader by holding Power + Vol Up and Down simultaneously..
vin4yak said:
@rest0ck
Hold down power + vol down button for about 30 seconds and see if the bootloader shows up? if not, you can try accessing the secondary bootloader by holding Power + Vol Up and Down simultaneously..
Click to expand...
Click to collapse
Absolutely nothing happens
How can I .zip completely broke the recovery etc.? Isn't that supposed to be "unbreakable"? I did this mistake on another phone before (You would think I learned...) and I was able to unbrick it. But on a nexus it is impossible? :/
rest0ck said:
Absolutely nothing happens
How can I .zip completely broke the recovery etc.? Isn't that supposed to be "unbreakable"? I did this mistake on another phone before (You would think I learned...) and I was able to unbrick it. But on a nexus it is impossible? :/
Click to expand...
Click to collapse
Flashing stuff meant for other devices can brick your device permanently due to partitioning being different. You'll have to RMA, sorry. What ROM did you flash?
rest0ck said:
Absolutely nothing happens
How can I .zip completely broke the recovery etc.? Isn't that supposed to be "unbreakable"? I did this mistake on another phone before (You would think I learned...) and I was able to unbrick it. But on a nexus it is impossible? :/
Click to expand...
Click to collapse
1. Other phones have kernels with different voltages that can fry the insides.
2. Other phones use different partition numbers. The script may flash flash a kernel to the bootloader - bye bye phone
3. a brick is a brick. You cannot unbrick. If you "unbricked" something, then it wasn't bricked.
Sent from my Nexus 5 using Tapatalk
Oh okay. Do you think RMA is possible when it's my fault?
This one: http://forum.xda-developers.com/oneplus-one/development/rom-stock-rooted-4-4-4-xnph30o-t2845100
You can send it to LG. RMA to Google is not possible.
Sent from my Nexus 5 using Tapatalk
Not possible because they know I bricked it?
rest0ck said:
Not possible because they know I bricked it?
Click to expand...
Click to collapse
Not possible because the warranty doesn't cover user error.
Lethargy said:
Not possible because the warranty doesn't cover user error.
Click to expand...
Click to collapse
rest0ck said:
Not possible because they know I bricked it?
Click to expand...
Click to collapse
This. When they find out its your fault, they charge you for a new phone. If you send to LG they will hopefully just quote you for repair of existing phone.
Sent from my Nexus 5 using Tapatalk
I had something similar...
keep your phone plugged....but use its charger, no other version...and keep press power for 60/90 seconds...
Hm I tried but it doesn't work.
Do they even test the phones? I did an RMA once and they said if they see a broken display or anthing they let me know and send it back to me + I send the new phone back to them again. Would they really charge me?
rest0ck said:
Do they even test the phones? Would they really charge me?
Click to expand...
Click to collapse
The answer to both those questions is; why wouldn't they?
rest0ck said:
Hm I tried but it doesn't work.
Do they even test the phones? I did an RMA once and they said if they see a broken display or anthing they let me know and send it back to me + I send the new phone back to them again. Would they really charge me?
Click to expand...
Click to collapse
Here's the deal. RMA to Google is for manufacturing defects ONLY. When you RMA, Google freeze the cost of the phone in your account. When they find out its not a defect, they will take that money. Sending a phone to Google, knowing its your fault, hoping to get it replaced for free is fraud.
Sending to LG shows you are willing to pay for the repair. LG will repair manufacturing defect for free. They should charge you to repair user error. Sending a phone to LG, knowing its your fault, hoping to get it repaired for free is fraud.
Here is my advice. Send it to LG. Tell them what you did. Ask them for a price to repair.
Sent from my Nexus 5 using Tapatalk
There is no reason not to but maybe it's just not what they usually do
rest0ck said:
There is no reason not to but maybe it's just not what they usually do
Click to expand...
Click to collapse
Just send it to LG, and tell tgem what you did. You bricked it so you need to take responsibilty for it
I read a lot of horrible storys about LG's RMA :|
It's not my phone by the way. I think I will try an RMA and buy a new one at the same time ... does anyone know what that could cost me?
Related
I am completely stumped. My wife's phone quit working today. It won't turn off without pulling the battery, if the screen times out you can't turn it back on without plugging it in.
I did a factory reset, same problem. I was going to try to root it and install a new ROM and kernel, but when I boot into fastboot the phone is not recognized on my computer (fastboot devices doesn't list anything) and the volume buttons are not responsive at all in the fastboot menu. I plugged my phone into the computer (another nexus s) and it is listed when I type fastboot devices so it is the phone, not a driver problem, etc.
I am out of ideas here. I have essentially a bricked stock Nexus S and a working CM7 Nexus S. Is there anything I can do or is this an issue I have to deal with samsung warranty?
Gonna have to put it in "download mode"(HOLD both volume buttons and PRESS power button)
Then.....
If its a Sprint CDMA version use SWUpdater: http://forum.xda-developers.com/showthread.php?t=1072698
If its a gsm, use odin and the correct firmware for your model
snandlal said:
Gonna have to put it in "download mode"(HOLD both volume buttons and PRESS power button)
Then.....
If its a Sprint CDMA version use SWUpdater: http://forum.xda-developers.com/showthread.php?t=1072698
If its a gsm, use odin and the correct firmware for your model
Click to expand...
Click to collapse
It's the original tmobile one. Any idea where I can get Odin and the correct firmware?
Also I have tried to get into download mode, but can't.
I am running out of ideas... At this point I am really starting to think it is a hardware issue
chrlswltrs said:
It's the original tmobile one. Any idea where I can get Odin and the correct firmware?
Also I have tried to get into download mode, but can't.
I am running out of ideas... At this point I am really starting to think it is a hardware issue
Click to expand...
Click to collapse
Take it for repair then
snandlal said:
Take it for repair then
Click to expand...
Click to collapse
Yeah I have to call samsung tomorrow, not looking forward to that process
Sent from my Nexus S using xda premium
Sorry to hear it. Hope they take care of you asap
snandlal said:
Sorry to hear it. Hope they take care of you asap
Click to expand...
Click to collapse
I do to. At least my daughter doesn't need a phone (she is only 9) so my wife can use her MT4G for a few days until we get a replacement NS. Just hope it doesn't turn into a bigger hastle than it needs to be.
chrlswltrs said:
I do to. At least my daughter doesn't need a phone (she is only 9) so my wife can use her MT4G for a few days until we get a replacement NS. Just hope it doesn't turn into a bigger hastle than it needs to be.
Click to expand...
Click to collapse
sad that you got a bad NS! ,but please use the correct section to post !
Sent from my Google Nexus S using xda premium
1 pull the battery
2 replace battery
3 hold volume up and down at the same time
4 plug into a usb cable connected to your pc while holding the volume + and -
now you have download mode
I just wanted to use revolutionary to root my phone, but nothing happened. After that the phone just rebooted and then turned off. Now I can't turn it on and it even doesn't charge!
help please
Your phone is not brick, can you still boot into HBOOT? Volume down key and press hold power button.
Sent from my HTC Sensation 4G using XDA Premium App
no, it seems completely dead. Even when I connect it to the charger the charging light doesn't turn on!
did you have cwm installed on your phone already and if so what version
remove battery.. then try powering the phone.. if nothing happens.. follow this thread...
http://forum.xda-developers.com/showthread.php?t=1198585
and if still nothing happens..then I would say that it's bricked...
william1985 said:
did you have cwm installed on your phone already and if so what version
Click to expand...
Click to collapse
I don't have CWM, because the problem happened when I tried to root it!
Quakeworld said:
remove battery.. then try powering the phone.. if nothing happens.. follow this thread...
http://forum.xda-developers.com/showthread.php?t=1198585
and if still nothing happens..then I would say that it's bricked...
Click to expand...
Click to collapse
I tried another battery but it didn't work
at least someone tell me if I can return it or report it as lost phone? I am on tmobile
"make sure" there is no way to boot on then just bring back to T-mobile to get a new one; Just say "I got no cure" "whatever they asked.
kai2314 said:
"make sure" there is no way to boot on then just bring back to T-mobile to get a new one; Just say "I got no cure" "whatever they asked.
Click to expand...
Click to collapse
it wont boot, is there anyway they can read any logs or something from the phone memory to see what happened?
mzangui said:
it wont boot, is there anyway they can read any logs or something from the phone memory to see what happened?
Click to expand...
Click to collapse
Same happened to me (exactly) and after being advised by network provider rang HTC repairs, phone picked up next day, returned to me repaired 6 days later, no charge, hassle at all!
Hi! I've got a sticky situation here, my g3 is in a bootloop, not the normal bootloop, i'm in a "yup, you're f***ed" situation. Lets start here shall we?
The condition of my phone currently:
Volume buttons broken (not able to get into recovery/download mode)
Stuck at "GT-I5800" logo
Adb says no device connected (not being able to get into recovery/download mode, AGAIN)
Maybe i'm too ambitious but can my device be saved?
I think it's time to replace your phone if half the buttons are broken :|
Sent from my GT-I5800 using XDA
Smonic said:
I think it's time to replace your phone if half the buttons are broken :|
Sent from my GT-I5800 using XDA
Click to expand...
Click to collapse
I already have, i bricked the g3 like 2 months ago, tried to fix myself but can't so i'm asking for advice here. I like my gio though, i'm just striving to revive my old friend that taught me almost everything i know about android today.
Hmmmm. Check this - http://forum.xda-developers.com/showthread.php?t=1554266
Same situation like yours.
ak700 said:
Hmmmm. Check this - http://forum.xda-developers.com/showthread.php?t=1554266
Same situation like yours.
Click to expand...
Click to collapse
Not really, my adb doesn't recognize the g3, it works fine with my gio though
All you can do now is take the battery out.......and you'll need to fix the volume keys
J.Purungrit said:
All you can do now is take the battery out.......and you'll need to fix the volume keys
Click to expand...
Click to collapse
I've visited a friend that repairs phones, he says it's no use to try fix the volume keys, they are broken from the mainboard.
iok1 said:
I've visited a friend that repairs phones, he says it's no use to try fix the volume keys, they are broken from the mainboard.
Click to expand...
Click to collapse
well, then I guess it's over.....without those keys, there is no way to fix it
I am so sad as I write this...:crying:
I had TWRP custom recovery and running the ARHD 9.0 rom.
I was tempted to try the other roms so I played around with Omega and ReVolt rom..they worked fine...
Then, when I tried to reflash ARHD 9.0, I could get to TWRP recovery but it just reboots even before any of the buttons appear.
So, I went into download mode and flashed HighOnAndroid custom recovery.
It seem to work fine....so I went ahead and flashed ARHD 9.0....It installed fine and completed successfully.
But when I rebooted the device...sigh...no power, not even the charging animation when I plug it into the charger...
So, if anyone has a solution on what I should do, please do tell me or I am really sad...so so sad...:crying:
Try a different charger, cable and wall outlet. Leave the n8000 there for a while. Hold the power button for a while, then let it go. Listen closely to the speakers for the little samsung sound when it turns on. Idk if the rom you installed has a boot sound tho. Anyways, if you still dont have an answer after that.. I would maybe start to think the power button is dead. Its a last ditch option but plausible i suppose lol.
Beyond that, you might have to think about sell it for parts.
Oh and i remember from my time with the Samsung vibrant that sometimes, even if nothing comes up on the screen, the device might be picked up by Odin after doing the dl mode button combo
Sent from my Nexus 4 using xda app-developers app
younix258 said:
Try a different charger, cable and wall outlet. Leave the n8000 there for a while.
Click to expand...
Click to collapse
I brought a friend's Note and charged using my usb charger/cable...it is working ok.
I would maybe start to think the power button is dead. Its a last ditch option but plausible i suppose lol.
Beyond that, you might have to think about sell it for parts.
Click to expand...
Click to collapse
My Note is about 2 months old and is still under warranty period. As a last resort, I can send it to them.
Oh and i remember from my time with the Samsung vibrant that sometimes, even if nothing comes up on the screen, the device might be picked up by Odin after doing the dl mode button combo
Click to expand...
Click to collapse
I will try and post back here.
Thanks for sharing your thoughts though.
freelancer81 said:
I brought a friend's Note and charged using my usb charger/cable...it is working ok.
My Note is about 2 months old and is still under warranty period. As a last resort, I can send it to them.
As you have root and custom rom then warranty is void .
If Samsung cannot tell that you have root and custom rom is a different matter .
Click to expand...
Click to collapse
Have you tried plugging in to your pc, see if odin recognizes it? If so try flashing stock samsung rom.
Sent from my GT-N8013 using XDA Premium App
rail205 said:
Have you tried plugging in to your pc, see if odin recognizes it? If so try flashing stock samsung rom.
Click to expand...
Click to collapse
I tried it....not detected...
It's very strange...no backlit or sound even when pressing power, power+vol up/vol down combos.
There was no error at all while flashing the ARHD 9.0.....and when I click on the finish and restart/reboot button at the end, boom..it shutdowns and dies on me...
I have googled it but no one has ever come across this kind of problem.
Since it is completely dead, there is a chance that sammy will not know it's rooted and running custom firmware.
Thanks to you and JJEgan for your concerns and suggestions.
As it sounds like a hardware issue, Samsung will likely fix it under warranty. At least that was my experience with Asus on my previous tablet.
Sent from my Vivid 4G using xda app-developers app
Do you know.if your battery was almost dead when flashing that last. Rom? I've heard that can brick ur device if it dies in flashing process. (Even tho you said flash completed) but who knows?
trevor7428 said:
Do you know.if your battery was almost dead when flashing that last. Rom? I've heard that can brick ur device if it dies in flashing process. (Even tho you said flash completed) but who knows?
Click to expand...
Click to collapse
I am not very sure about the exact battery percentage but yeah, it was low...somewhere about 10%~30%.
So, does that mean there is no way to revive it?
:crying:
freelancer81 said:
I am not very sure about the exact battery percentage but yeah, it was low...somewhere about 10%~30%.
So, does that mean there is no way to revive it?
:crying:
Click to expand...
Click to collapse
Unfortunately not without a new motherboard it seems like. If the is no sign of life, no recovery, no download mode and can't flash via oden or kies on computer with proper drivers installed. Then it sounds like a hard brick. Not recoverable unless new motherboard or JTAG. :/
Sorry man. But in future never flash if less than 30% battory. I've heard some pple say not below 50%
I don't know if your 10.1 died while flashing, but if so it could hard brick
50% is the suggested level of battery because flashing actually uses a large amount of battery. Also the tablets seem to power down things at 10%power.
Could be it shut off if the power dropped below 10%. This is why we suggest to not flash below 50%...
trevor7428 said:
Unfortunately not without a new motherboard it seems like. If the is no sign of life, no recovery, no download mode and can't flash via oden or kies on computer with proper drivers installed. Then it sounds like a hard brick. Not recoverable unless new motherboard or JTAG. :/
Sorry man. But in future never flash if less than 30% battory. I've heard some pple say not below 50%
I don't know if your 10.1 died while flashing, but if so it could hard brick
Click to expand...
Click to collapse
ultramag69 said:
50% is the suggested level of battery because flashing actually uses a large amount of battery. Also the tablets seem to power down things at 10%power.
Could be it shut off if the power dropped below 10%. This is why we suggest to not flash below 50%...
Click to expand...
Click to collapse
so sad....lesson learnt too late....the hard way :crying:
But I guess I have learnt one more way of hardbricking a device.
dude, seems like maybe a problem with your "main board"... i had the same issue at my galaxy tab 2, and i sent it to the shop ( because its passed warranty period already)...
Hey ,
im having a problem with my friend nexus 5.
when im turning on the device, it's just stuck on the google logo in the booting.
when im trying to access Recovry mode, i can go to the boot options and see all the device info, but when pressing the recovery mode there is a black screen and nothing happens.
please help me.
thanks
Download recovery.img & put in your platform tools folder.
fastboot flash recovery recovery.img
Sent from my Nexus 5 using XDA Premium 4 mobile app
SketchyStunts said:
Download recovery.img & put in your platform tools folder.
fastboot flash recovery recovery.img
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
is there any guide for doing it?
i dont really know what to do.
asafisraelit said:
is there any guide for doing it?
i dont really know what to do.
Click to expand...
Click to collapse
Hello,
Is the device rooted? Is it using custom recovery? Or is it fully stock??
vin4yak said:
Hello,
Is the device rooted? Is it using custom recovery? Or is it fully stock??
Click to expand...
Click to collapse
fully stock.
in the condition that it came from google.
thanks
asafisraelit said:
fully stock.
in the condition that it came from google.
thanks
Click to expand...
Click to collapse
If you're not able to go past the Google screen, Switch off the phone and then Press and Hold down the Power Button+vol down button till you feel a vibrate.. The bootloader will open... Use the volume buttons and navigate to Recovery and and then press the power button to go into the recovery... You can perform a factory reset from there...
But, if you aren't able to access the recovery and as you are fully stock, there isn't much you can do about it...
You could try unlocking the bootloader and then performing a factory flash but since it's fully stock you can RMA it...
asafisraelit said:
fully stock.
in the condition that it came from google.
thanks
Click to expand...
Click to collapse
Since you are on 100% stock, I think your emmc (flashchip) got faulty like in many other nexus 5 bootloop topic around in xda.
But you can try to reflash the factory images again. Read the first 3-4 sticky thread in the general forum.
Tapatalk-kal küldve az én Nexus 5-el
Do what Mr Stunts says. If it's new and that doesn't work, and it should, take it back. You shouldn't need to be unlocking this and that just to get a new phone up and running.
From my mobile telephony device.
same problem
bitdomo said:
Since you are on 100% stock, I think your emmc (flashchip) got faulty like in many other nexus 5 bootloop topic around in xda.
But you can try to reflash the factory images again. Read the first 3-4 sticky thread in the general forum.
Tapatalk-kal küldve az én Nexus 5-el
Click to expand...
Click to collapse
Hello, I have similar problem, bought new put it out of my country, and I have no way to send him Warranty, worked one week then stopped at the google screen. and do not go out anymore. I saw that there are several procedures to try, however, there is a possibility however that does not have a solution? because you mensionou "EMMC (flashchip) got faulty Like in many" if it has solution?
andrelg3 said:
Hello, I have similar problem, bought new put it out of my country, and I have no way to send him Warranty, worked one week then stopped at the google screen. and do not go out anymore. I saw that there are several procedures to try, however, there is a possibility however that does not have a solution? because you mensionou "EMMC (flashchip) got faulty Like in many" if it has solution?
Click to expand...
Click to collapse
Please give us more info? Are you fully stock? or using a Custom rom?
No, there's nothing you can do with a fried eMMC! The motherboard needs to be replaced...
vin4yak said:
Please give us more info? Are you fully stock? or using a Custom rom?
No, there's nothing you can do with a fried eMMC! The motherboard needs to be replaced...
Click to expand...
Click to collapse
fully stock a week of use, and this happened during a normal daily use.
andrelg3 said:
fully stock a week of use, and this happened during a normal daily use.
Click to expand...
Click to collapse
Can you access the bootloader? Switch off the device and hold down Power+Vol. Down button simultaneously till you get to the bootloader.. Select recovery by hitting the Volume keys and then perform a factory reset and reboot...
However, if you can't access the bootloader, there's nothing you can do...
vin4yak said:
Can you access the bootloader? Switch off the device and hold down Power+Vol. Down button simultaneously till you get to the bootloader.. Select recovery by hitting the Volume keys and then perform a factory reset and reboot...
However, if you can't access the bootloader, there's nothing you can do...
Click to expand...
Click to collapse
I access the bootloder normally, but when accessing the recovery mode it does not continue, break in the google logo
andrelg3 said:
I access the bootloder normally, but when accessing the recovery mode it does not continue, break in the google logo
Click to expand...
Click to collapse
Well, I don't think there's anything you could do.. If the eMMC is fried, motherboard needs to be replaced..