Related
Hi everybody, I searched everywhere for a solution but no luck
i love my note so much that if i couldnt fix it i think im gonna kill myself.
let me tell you the whole story, maybe you can revive my note again.
im a daily rom flasher, sometimes even 2 or 3 roms a day,
i wanted to flash ics stunner rom so i went into cwm recovery,flashed the zip file and wanted to format data\factory reset, but while the phone was formatting i accidently pressed the power button, the phone was stuck and didn't complete formatting, i took the battery out, put it back in and powered the phone, it was stuck at the bootscreen GTn7000 Galaxy Note.
I got into download mode and flashed a stock rom, but it was the same.
i downloaded and flashed other stock roms but it was stuck at the bootscreen.
then i wanted to flash a stock rom that came with a Pit file, i did everythig correctly, and Odin was stuck at the partition thing, for more than 15 minutes.
i unpluged the phone i pressed the power button, NOTHING!!
i officially bricked my phone which i worked so hard for months to get it.
i tried everything,even the jig thing, i couldn't buy so i had to make one.
maybe i did somethig wrong with the jig or maybe because i didnt solder it or the usb plug im using isnt working.
this may be relevant, i pluged the usb OTG in the phone and in the OTG was a bluetooth peice for computers, the piece had a light, and the light was ON.
Another thing that if i leave the battery in the phone for a while, the camera area in the back gets a little hot, my phone always did that meaning its still alive.
i may have written too much, forgive me but im really desperate.
Thanks in advance.
You probably end up going to Samsung. Pay €200 and get a new motherboard.
Good luck.
Sent from my CM9 GT-N7000 using XDA premium
hav0c said:
You probably end up going to Samsung. Pay €200 and get a new motherboard.
Good luck.
Sent from my CM9 GT-N7000 using XDA premium
Click to expand...
Click to collapse
WOW...
the problem is that i live in a fu**ed up country and we dont have samsung here.
all phones come without warranty and by smuggling from other countries
You mentioned killing yourself. Bro it's just a phone... Hang in there!!!
Sent from my GT-N7000 using Tapatalk 2
First thing donot flash Ics now untill you are craze about it.2nd donot use CWM as much as possible.Read this.
Ok to the problem now.Since you say it gets hot,it might be still alive.Remove the battery and insert it after 10 secs and insert the jig and after few secs press vol up button.Now connect the phone to computer and see if its detected if it does try flashing abyy's kernel.I dont know which kernel for sure.Somebody might help you.People were able to get into DL mode when there screen were not showing anything.
There are situations when your phone is working, but your screen is black.
Let's hope yours is one of those...Try this:
1. Don't flash Abyss. Download a stock GB Rom instead.
2. Charge your phone for a couple of hours. You need your battery for the
following steps.
3. After charging, take out your battery and wait 1 minute
4. Put it back in
5. Boot into Download mode (Volume Down+Home+Power) (you will see only black screen)
6. Count to 10
7. Press Volume Up
8. Count to 10
9. Start your PC Odin
10. Connect your phone to PC
11. Wait untill PC installs the necessary drivers
12. If all goes well, your PC Odin will flash the yellow light with COM info in it
13. Flash your stock GB Rom
If this doesn't work, you'll need to think of the ways of getting your phone JTagged or where to get a new motherboard.
Dude, if you have no way of repairing a bricked phone in your country then stay away from flashing custom ROMs!!!
Sent from my superior GT-N7000 using Tapatalk
Bro as u mentioned already that u flashed stock once...all root and cmw will be wiped... i would prefer going to samsung service center and tell them that u were updating your phone through kies and after the update completed ur phone stopped working... they will fix it for free... and act innocent
Edit::: dint see the other post where u mentioned that there is no samsung center at your place... in that case theres only one thing u can do... buy the motherboard and fix it urself.... sorry that ur beast is dead
izzmohamed said:
Hi everybody, I searched everywhere for a solution but no luck
i love my note so much that if i couldnt fix it i think im gonna kill myself.
let me tell you the whole story, maybe you can revive my note again.
im a daily rom flasher, sometimes even 2 or 3 roms a day,
i wanted to flash ics stunner rom so i went into cwm recovery,flashed the zip file and wanted to format data\factory reset, but while the phone was formatting i accidently pressed the power button, the phone was stuck and didn't complete formatting, i took the battery out, put it back in and powered the phone, it was stuck at the bootscreen GTn7000 Galaxy Note.
I got into download mode and flashed a stock rom, but it was the same.
i downloaded and flashed other stock roms but it was stuck at the bootscreen.
then i wanted to flash a stock rom that came with a Pit file, i did everythig correctly, and Odin was stuck at the partition thing, for more than 15 minutes.
i unpluged the phone i pressed the power button, NOTHING!!
i officially bricked my phone which i worked so hard for months to get it.
i tried everything,even the jig thing, i couldn't buy so i had to make one.
maybe i did somethig wrong with the jig or maybe because i didnt solder it or the usb plug im using isnt working.
this may be relevant, i pluged the usb OTG in the phone and in the OTG was a bluetooth peice for computers, the piece had a light, and the light was ON.
Another thing that if i leave the battery in the phone for a while, the camera area in the back gets a little hot, my phone always did that meaning its still alive.
i may have written too much, forgive me but im really desperate.
Thanks in advance.
Click to expand...
Click to collapse
Your phone is pretty much dead I'm afraid
Why didn't you bother to read stickies first?
It has been known for several weeks now that doing a wipe from CWM in a leaked recovery (I.e all ICS ROMs except cm9 official) will lead to a corrupted emmc drive ,thus a dead phone
And no ,you pressing the power button had nothing to do with it being stuck
The moment you hit wipe from ICS stunner's recovery your phone was dommed.
Anyway what's done is done ,now find an unofficial repair shop and replace your motherboard.
I hope this makes it clear ,and good luck to you.
izzmohamed said:
Hi everybody, I searched everywhere for a solution but no luck
Click to expand...
Click to collapse
Try this : http://forum.xda-developers.com/showthread.php?t=1257434
To force your phone into Download mode !
octavian90 said:
You mentioned killing yourself. Bro it's just a phone... Hang in there!!!
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
if you had gone through what i went through to get the phone, you would probably do the same.Thanks for the reply, any thing would help me right now.
vijai2011 said:
First thing donot flash Ics now untill you are craze about it.2nd donot use CWM as much as possible.Read this.
Ok to the problem now.Since you say it gets hot,it might be still alive.Remove the battery and insert it after 10 secs and insert the jig and after few secs press vol up button.Now connect the phone to computer and see if its detected if it does try flashing abyy's kernel.I dont know which kernel for sure.Somebody might help you.People were able to get into DL mode when there screen were not showing anything.
Click to expand...
Click to collapse
Thanks man, i will definitely try it right away.
mother board
mother board is gone due to kernel harm of ics leak
sorry
this is the fact...
chasmodo said:
There are situations when your phone is working, but your screen is black.
Let's hope yours is one of those...Try this:
1. Don't flash Abyss. Download a stock GB Rom instead.
2. Charge your phone for a couple of hours. You need your battery for the
following steps.
3. After charging, take out your battery and wait 1 minute
4. Put it back in
5. Boot into Download mode (Volume Down+Home+Power) (you will see only black screen)
6. Count to 10
7. Press Volume Up
8. Count to 10
9. Start your PC Odin
10. Connect your phone to PC
11. Wait untill PC installs the necessary drivers
12. If all goes well, your PC Odin will flash the yellow light with COM info in it
13. Flash your stock GB Rom
If this doesn't work, you'll need to think of the ways of getting your phone JTagged or where to get a new motherboard.
Click to expand...
Click to collapse
kvsandeepreddy said:
Bro as u mentioned already that u flashed stock once...all root and cmw will be wiped... i would prefer going to samsung service center and tell them that u were updating your phone through kies and after the update completed ur phone stopped working... they will fix it for free... and act innocent
Edit::: dint see the other post where u mentioned that there is no samsung center at your place... in that case theres only one thing u can do... buy the motherboard and fix it urself.... sorry that ur beast is dead
Click to expand...
Click to collapse
kvsandeepreddy said:
Bro as u mentioned already that u flashed stock once...all root and cmw will be wiped... i would prefer going to samsung service center and tell them that u were updating your phone through kies and after the update completed ur phone stopped working... they will fix it for free... and act innocent
Edit::: dint see the other post where u mentioned that there is no samsung center at your place... in that case theres only one thing u can do... buy the motherboard and fix it urself.... sorry that ur beast is dead
Click to expand...
Click to collapse
MR.change said:
Your phone is pretty much dead I'm afraid
Why didn't you bother to read stickies first?
It has been known for several weeks now that doing a wipe from CWM in a leaked recovery (I.e all ICS ROMs except cm9 official) will lead to a corrupted emmc drive ,thus a dead phone
And no ,you pressing the power button had nothing to do with it being stuck
The moment you hit wipe from ICS stunner's recovery your phone was dommed.
Anyway what's done is done ,now find an unofficial repair shop and replace your motherboard.
I hope this makes it clear ,and good luck to you.
Click to expand...
Click to collapse
pvillasuso said:
Try this : http://forum.xda-developers.com/showthread.php?t=1257434
To force your phone into Download mode !
Click to expand...
Click to collapse
You guys are awesome, im gonna do everything you said and get back with the results, fingers crossed.
I have a friend who's going to Dubai,UAE in a week or so. if nothing worked i'll send the phone with her to repair it at samsung,does anybody know if there's a samsung service center in Dubai and give me the location ?
i cant thank you enough,really appreciate all the help.
firasusman said:
mother board is gone due to kernel harm of ics leak
sorry
this is the fact...
Click to expand...
Click to collapse
OK, how much will it cost me ?
by the way i forgot to mention that before i bricked the note, it had a charging problem, saying voltage too high,charging stopped,and when the phone is turned off the battery icon keeps appearing and disapearing, could it be that the jig is not working because of that??
Try a different USB cable?
Sent from my SPH-D710 using XDA
izzmohamed said:
OK, how much will it cost me ?
by the way i forgot to mention that before i bricked the note, it had a charging problem, saying voltage too high,charging stopped,and when the phone is turned off the battery icon keeps appearing and disapearing, could it be that the jig is not working because of that??
Click to expand...
Click to collapse
You're not going to like this: I had to send my phone back to Samsung to get that fixed. Basically the charging port was shorting out, happens when stuff gets inside it (dirt, moisture, etc, from what I read). You could try cleaning it, but for me the port didn't break, it just acted like it was charging when there was nothing plugged in. So the JIG will work if it's supposed to.
jeffrey567 said:
Try a different USB cable?
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
I did, still the same.
jayshah said:
You're not going to like this: I had to send my phone back to Samsung to get that fixed. Basically the charging port was shorting out, happens when stuff gets inside it (dirt, moisture, etc, from what I read). You could try cleaning it, but for me the port didn't break, it just acted like it was charging when there was nothing plugged in. So the JIG will work if it's supposed to.
Click to expand...
Click to collapse
Hmmm,i'll try cleaning it.I had the same situation, so the jig should work fine despite this problem ?
jayshah said:
You're not going to like this: I had to send my phone back to Samsung to get that fixed. Basically the charging port was shorting out, happens when stuff gets inside it (dirt, moisture, etc, from what I read). You could try cleaning it, but for me the port didn't break, it just acted like it was charging when there was nothing plugged in. So the JIG will work if it's supposed to.
Click to expand...
Click to collapse
Just out of curiosity: Are you in the US and had to send your international Note somewhere? I am wondering how one can get a support for an International Note if you're in the US.
I don't mind sending it to another country, but which Samsung center will accept it?
lanwarrior said:
Just out of curiosity: Are you in the US and had to send your international Note somewhere? I am wondering how one can get a support for an International Note if you're in the US.
I don't mind sending it to another country, but which Samsung center will accept it?
Click to expand...
Click to collapse
I am wondering the same thing, mine got bricked about a week ago and I don't really know what to do with it
Hello!
During flashing leaked kernel my phone was on soft brick, I wiped cache partition and data in CWM. This was the end of my beloved Note, it is 100% dead and none of the possible fixes posted works so far.
I have heard there is a possible fix by re partitioning and connection the phone in Linux environment, this way the computer reads the phone and can be fixed by repartitioning and could get into download mode. Please let me know if anybody confirms this.
Alternatively, what is the next step. My phone is still under warranty but I am scared if Samsung would find out the history of rooting or as my Phone is 100% dead they would not be able to find out, confused.......
If the motherboard needs to be replaced, how much would it cost, where should I take and most important if my phone recovers can I still play around with custom ROMs?
Look forward to suggestions bring my phone live as I purchased it on loan and it brings immense pain to pay emi for a dead phone.
Regards,
AK
Even it bricked by emmc bug, there shud be download mode still available
-First try to get other charged battery (or charge yours) and try to put in download mode, and look to Lt upper corner what is your flash score. If it is zero, simply reclain warranty.
-Otherwise try this
http://forum.xda-developers.com/showthread.php?p=26285877
dr.ketan said:
Even it bricked by emmc bug, there shud be download mode still available
-First try to get other charged battery (or charge yours) and try to put in download mode, and look to Lt upper corner what is your flash score. If it is zero, simply reclain warranty.
-Otherwise try this
http://forum.xda-developers.com/showthread.php?p=26285877
Click to expand...
Click to collapse
Thanks. I tried using charged batteries but still does not get into Download Mode also after reading somewhere I tried to connect using Odin assuming screen would be black but Odin detects. Even this did not work
So, no way of getting DM or looking at binary count.
Regards.
AK
Your phone is under warranty yet you are asking for costs? Those "recovery" method will give you a "crippled" device in terms of mem capacity.
So go and claim warranty. They wont know anything since your phone is totally dead anyway.
Sent from my GT-N7000 using xda app-developers app
praetorius said:
Your phone is under warranty yet you are asking for costs? Those "recovery" method will give you a "crippled" device in terms of mem capacity.
So go and claim warranty. They wont know anything since your phone is totally dead anyway.
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
Hey, I just cam back from SS service. they said it could be a motherboard issue and they are replacing the motherboard.
Does that mean they would install the Stock Rom from fresh, I am sure yes.
Waiting for my recovered phone and educating myself to safely play around with custom ROMs.
One last question, which is the best stable custom ROM available for Galaxy Note, in terms of UI and better battery life?
Many Thanks.
AK
avinay4you said:
Hey, I just cam back from SS service. they said it could be a motherboard issue and they are replacing the motherboard.
Does that mean they would install the Stock Rom from fresh, I am sure yes.
Waiting for my recovered phone and educating myself to safely play around with custom ROMs.
One last question, which is the best stable custom ROM available for Galaxy Note, in terms of UI and better battery life?
Many Thanks.
AK
Click to expand...
Click to collapse
Congrats on the replacement;
Custom ROM's are kind of personal preference, Best bet is to do your research now while you wait and you can decide for yourself which features you like / want / need in a ROM..
Suggestions to check would be ParanoidAndroid / CleaNote from my point of view, I've tried both but still run Stock ICS with custom Kernel.. Suits my needs...
while gaming, my phone suddenly hang and i decide to restart the device itself. upon booting, i am stuck at the "samsung" logo. I have tried flashing stock rom and kernel but to no avail. i can still go into download mode and recovery mode. Anybody know whats gone wrong?
And if i send for waranty, it is a one to one exchanged?
driftkids said:
while gaming, my phone suddenly hang and i decide to restart the device itself. upon booting, i am stuck at the "samsung" logo. I have tried flashing stock rom and kernel but to no avail. i can still go into download mode and recovery mode. Anybody know whats gone wrong?
And if i send for waranty, it is a one to one exchanged?
Click to expand...
Click to collapse
what is the current rom on your phone? have you tried going to recovery and wiping dalvik cache? still same thing? If it is, worst case you can try (since both Recovery and Download works still) is to wipe data in recovery and restart your phone again(Don't try doing this if your using an infected kernel and/or in ICS Rom)
Going back,
You have a soft bricked phone.. Why would you exchange it for warranty? you can easily fix your issue without returning it to Samsung.
letters_to_cleo said:
what is the current rom on your phone? have you tried going to recovery and wiping dalvik cache? still same thing? If it is, worst case you can try (since both Recovery and Download works still) is to wipe data in recovery and restart your phone again(Don't try doing this if your using an infected kernel and/or in ICS Rom)
Going back,
You have a soft bricked phone.. Why would you exchange it for warranty? you can easily fix your issue without returning it to Samsung.
Click to expand...
Click to collapse
i am currently using stock ics 4.0.4 with GL NOTECORE kernel. i have tried wipe dalvik cache but still didnt solve it. i will try wipe date later. thanks
ya, format data does solved it. i am wondering whether will soft brick cause any damage to the hardware?
help
hello
Same problem...pls HELP !!!
I tried to install a custom rom and then the horror began. I can't turn it on geto to download or recovery mode.. I sent it to service because I still have a warranty but I don't know will they see the history of installed roms. The man I talked to said to me that they can do it but I read a comment that it is impossible to see so I got a hope. They also told me that it could be about motherboard and that they will do everything they can to save it. I am really afraid of losing my Note. I hope you guys will help me and tell me sth good.. I am also interested is it possible to fix it with usb jig. ?
thanks, my regards..
Already it's with samsung. If they cant do anything to revive, its a motherboard replacement.
Sent from my GT-N7000 using xda app-developers app
ive been trying to get my note n7000 fixed now way to get it to work jtag just doesn't work boot loader wont go in the phone at all new phone it is
nedzad95 said:
I tried to install a custom rom and then the horror began. I can't turn it on geto to download or recovery mode.. I sent it to service because I still have a warranty but I don't know will they see the history of installed roms. The man I talked to said to me that they can do it but I read a comment that it is impossible to see so I got a hope. They also told me that it could be about motherboard and that they will do everything they can to save it. I am really afraid of losing my Note. I hope you guys will help me and tell me sth good.. I am also interested is it possible to fix it with usb jig. ?
thanks, my regards..
Click to expand...
Click to collapse
Don't worry, if it is with samsung alrd. They'll sure give you replacement of the motherboard if they can't do anything to your existing one. This is considered as the "manufacturing fault", and therefore, they must be able to replace it.
1st few batches, N7000 came out under gingerbread 2.3.6 technology, and it worked very well without the eMMC brick bug. It is happened only when they upgrade to ICS, with their own stock kernel, which triggered the brick bug.
So long as they are delaying the fix for their own stock kernel with the eMMC brick bug removed, I think samsung is still liable to give replacement to user, no matter what you did to your device. As long as it is eMMC brick bug, and you have your warranty.
Why ?
very simple... Even most of the samsung sales person on their respective outlets, they know a lil bit or perhaps don't know at all about this bug. Unless the sales person is those who likes to play with handphone like most of us here.
And if they do know... they won't tell you as well about this bug. Otherwise, will you buy it ? :fingers-crossed:
So as a consumer, we have the right to be replaced if the bug has been triggered due to factory reset / wipe of data, since no one told us about this. **peace**.
Really do hope you get your replacement once they call you to take your phone.
Good Luck !
Sent from the corner of this rounded earth.
antique_sonic said:
Don't worry, if it is with samsung alrd. They'll sure give you replacement of the motherboard if they can't do anything to your existing one. This is considered as the "manufacturing fault", and therefore, they must be able to replace it.
1st few batches, N7000 came out under gingerbread 2.3.6 technology, and it worked very well without the eMMC brick bug. It is happened only when they upgrade to ICS, with their own stock kernel, which triggered the brick bug.
So long as they are delaying the fix for their own stock kernel with the eMMC brick bug removed, I think samsung is still liable to give replacement to user, no matter what you did to your device. As long as it is eMMC brick bug, and you have your warranty.
Why ?
very simple... Even most of the samsung sales person on their respective outlets, they know a lil bit or perhaps don't know at all about this bug. Unless the sales person is those who likes to play with handphone like most of us here.
And if they do know... they won't tell you as well about this bug. Otherwise, will you buy it ? :fingers-crossed:
So as a consumer, we have the right to be replaced if the bug has been triggered due to factory reset / wipe of data, since no one told us about this. **peace**.
Really do hope you get your replacement once they call you to take your phone.
Good Luck !
Sent from the corner of this rounded earth.
Click to expand...
Click to collapse
Thanks man.. you really encouraged me.. So they should give me a replacement.. I am still worried because the man that I talked to told that this kind of problem where I installed a bad rom is not under warranty so that is what scares me the most..
thanks for help...
Just to say:
Galaxy Note GT-N7000, ICS 4.0.4
regards...
driftkids said:
while gaming, my phone suddenly hang and i decide to restart the device itself. upon booting, i am stuck at the "samsung" logo. I have tried flashing stock rom and kernel but to no avail. i can still go into download mode and recovery mode. Anybody know whats gone wrong?
And if i send for waranty, it is a one to one exchanged?
Click to expand...
Click to collapse
seems to be peculiar issue.. they should exchange for sure.. Sorry, I don't have much idea on this..
i'm very impatient..
Hey guys,
I just want to inform you that my Note is at service for 3-4 days... I am contacting them every day and they say it's not done yet.. So I hope it means that they're working on it... I will write if something new happens..
My Regards, Nedzad
Hey
I contaced service and they told they couldn't do anything yet.. Repairman told me that they will get a new JTAG repair box in 20 days and then they will fix it for free.. I think it is a good news
gr8
Hi
i had paranoid android installed but the baseband was the wrong one..
(I installed iHackers 4.1 without flashing kernel + baseband because then i landed in a bootloop)
When on ihackers i installed paranoid android 4.4.4 over it and it worked. But also like in ihackers
i could not connect to my network because of the wrong baseband.
So i downloaded C6903_14.4.A.0.108_Generic_DE.ftf and flashed only the baseband without wiping anything..
Restarted .. baseband hasn't changed but the system booted and everything was fine.
Than i flashed only the kernel and the baseband without flashing anything else and wiping anything.
The phone went dead. Really dead. Power + vol+ which allways worked (3xvibrate) not working.
LED not working .. Just dead!!! i have it on the charger because before the last flashing it was @ about 15 - 20 % accu.
But even when i connect the charger .. no led .. nothing .. its playing dead.
Any Idea? (it is .. now that i remember .. not the first time a z1 went that dead on me.. I had a z1 before which did the same. now in retrospective I remember flashing kernel and baseband (ONLY) also on that phone.. and it went dead.
If somebody likes to trash his/her z1 try flashing only baseband and kernel. (I am sure the kernel and the baseband are the correct one for the firmware.)
Any ideas how to reanimate my z1?
vG
Thomas
You have flashed a stock kernel to a custom rom, so of course you will get a bootloop.
Solution, flash a stock FTF, after leaving the phone on charge for a few hours
and post your questions in the Q&A section
Cant get into flashmode or fastboot mode.. it does not react on any button combination
gregbradley said:
You have flashed a stock kernel to a custom rom, so of course you will get a bootloop.
Solution, flash a stock FTF, after leaving the phone on charge for a few hours
and post your questions in the Q&A section
Click to expand...
Click to collapse
Leave it for a few hours....
gregbradley said:
You have flashed a stock kernel to a custom rom, so of course you will get a bootloop.
Solution, flash a stock FTF, after leaving the phone on charge for a few hours
and post your questions in the Q&A section
Click to expand...
Click to collapse
gregbradley said:
Leave it for a few hours....
Click to expand...
Click to collapse
Thank you for your answer. =) I have unlearned to read messages till the end. Sorry =)
Have you tried the red button on the SIM tray slot?
Also refer to this thread:
http://forum.xda-developers.com/showthread.php?t=2574764
Poesini said:
Have you tried the red button on the SIM tray slot?
Also refer to this thread:
http://forum.xda-developers.com/showthread.php?t=2574764
Click to expand...
Click to collapse
yes .. i pushed it several times and also for ab 12 sec. nothing happens.
This happened to me when I first got my Z1. Unfortunately I had to send my phone back to Sony which they ended up replacing the motherboard.
They won't be able to detect any custom firmwares. Waiting time is unfortunately about 14 business days once they receive it...
If you phone is unlocked be sure to let them know so you get an nck unlock code. You will have a new imei.
khhhhris said:
This happened to me when I first got my Z1. Unfortunately I had to send my phone back to Sony which they ended up replacing the motherboard.
They won't be able to detect any custom firmwares. Waiting time is unfortunately about 14 business days once they receive it...
If you phone is unlocked be sure to let them know so you get an nck unlock code. You will have a new imei.
Click to expand...
Click to collapse
This is not a motherboard issue, it just needs charging for a few hours and then reflashing. Also he has lost his warranty due to unlocking so since this happened as a direct result of flashing custom roms he wont e able to claim on warranty
I understand this is not a motherboard issue, however the exact same problem happened to me months ago. Even after waiting overnight and trying to enter flash mode again it would not respond properly.
Sony's solution is to replace the motherboard at the repair facility I'm assuming because it is the easiest method.
I can almost guarantee this is what will happen when you send it in and they won't deny you warranty.
If you cannot get your phone into flash mode after a few hours, try again overnight. If not I would send it in, or get your carrier to replace it.
Repeat this magic phrase: "I updated my phone and it wouldn't turn on"
gregbradley said:
This is not a motherboard issue, it just needs charging for a few hours and then reflashing. Also he has lost his warranty due to unlocking so since this happened as a direct result of flashing custom roms he wont e able to claim on warranty
Click to expand...
Click to collapse
khhhhris said:
it.
Repeat this magic phrase: "I updated my phone and it wouldn't turn on"
Click to expand...
Click to collapse
Please do not condone fraud on XDA
Now you are deviating from the original intention of this thread. This is absolutely not fraud. It is a vague statement at best.
Your "Recognized Contributor" status and high post count does not give you authority to belittle other users.
Just trying to spread community support which is the purpose of xda, is it not?
Unsubscribed.
gregbradley said:
Please do not condone fraud on XDA
Click to expand...
Click to collapse
Well that excalated quickly...
Sent from my C6903 using XDA Premium 4 mobile app
TommyX235 said:
yes .. i pushed it several times and also for ab 12 sec. nothing happens.
Click to expand...
Click to collapse
Did you try the guide posted there?
http://forum.xda-developers.com/showthread.php?t=2646405
Well you flashed a stock kernel on a CM based rom and thought it would work?
Don't come for Greg as he's the nicest member on here.
Need help
Hi,
I've run pac-rom on my Z1. Now I want to flash from the current .109 firmware only the base band. In Flash Tool under exclude everything except I labeled baseband. Then the flash process starts without error message. When I start the phone is still the old baseband version. What am I doing wrong?
Thank you
[email protected] said:
Hi,
I've run pac-rom on my Z1. Now I want to flash from the current .109 firmware only the base band. In Flash Tool under exclude everything except I labeled baseband. Then the flash process starts without error message. When I start the phone is still the old baseband version. What am I doing wrong?
Thank you
Click to expand...
Click to collapse
Maybe its the same baseband?
No,
old version is .39, and the new from .108 is .51
Hey thanks for your answers @ all!!
The failure was that i flashed roms / ftf with very low battery. Than i charged for a few hours and flashed again .. and on and on.
At some point the accu seems to got broken.
I send it to a repair facility used by sony and they confirmed that the accu is dead.
It seems that i get a replacement. (on warranty)
Thank you again. ! SO!!! What we learn from this is "Only flash your device when its charged!"
dear, sorry the English, but I need a help from you.
I made the installation of IMG extracted the KDZ and did flash the recovery, however, now my machine not the sign of life, the computer does not detect the device, the device does not turn on, not of any sign of life. already tried in various corners anything to help me have some solution. I did the procedure based on the stock rom flash D405 with img extracted files. After that the only active device the display if I put to load without the battery, which displays the battery with a question mark. The device does not enter download mode, does not go into recovery, does not display anything, as if completely dead. Does anyone have aware and know any solution to the problem? Note: I've tried the LG flahs tools, it does not detect the device.
You have probably the worst case of them all. I suggest you to take your phone to warranty and see if they can replace it (because there probably isn't any way to fix it). If your warranty is void, then, I'm afraid, you will have to get a new device. I have had this issue myself, and it was solved only by replacing whole internals of the phone. Good thing that I still had my warranty, so it didn't cost anything. Good luck.
linasj said:
You have probably the worst case of them all. I suggest you to take your phone to warranty and see if they can replace it (because there probably isn't any way to fix it). If your warranty is void, then, I'm afraid, you will have to get a new device. I have had this issue myself, and it was solved only by replacing whole internals of the phone. Good thing that I still had my warranty, so it didn't cost anything. Good luck.
Click to expand...
Click to collapse
but this happened to you because of flash ROMS? How long on average it took for you to get the unit back?
wmosquini said:
but this happened to you because of flash ROMS? How long on average it took for you to get the unit back?
Click to expand...
Click to collapse
Yes. I tried to flash a ROM (which requires an unlocked bootloader), but for some reason the bootloader wasn't actually unlocked, and flashing a ROM caused the device to be bricked. This is probably what you would call a hard-brick.
In my case, replacement took a little more than a week. But this could differ from country to country.
linasj said:
Yes. I tried to flash a ROM (which requires an unlocked bootloader), but for some reason the bootloader wasn't actually unlocked, and flashing a ROM caused the device to be bricked. This is probably what you would call a hard-brick.
In my case, replacement took a little more than a week. But this could differ from country to country.
Click to expand...
Click to collapse
But in time to take the assistance, you said what about it? The unit stopped working alone?
wmosquini said:
But in time to take the assistance, you said what about it? The unit stopped working alone?
Click to expand...
Click to collapse
Exactly. Since the device cannot be turned on, I don't think they have any way of checking if it was rooted or tampered with in any way. So your best bet is to just play dumb and tell them your phone doesn't boot up. That helped me to get it fixed for free.
linasj said:
Exactly. Since the device cannot be turned on, I don't think they have any way of checking if it was rooted or tampered with in any way. So your best bet is to just play dumb and tell them your phone doesn't boot up. That helped me to get it fixed for free.
Click to expand...
Click to collapse
Legal, tomorrow I will even take the guarantee to solve as fast as possible. Really the device not the sign of life at all. I will inform you that the device was carrying at night and just when I catch him in the morning, he was like that.
Thank you for your help. : D
My first L90 didn't have a functional GPS, was brand new (1 week), problem was I rooted in the first day
Factory reset, hid superuser app, got a new l90
Gud luck
bacitoto said:
My first L90 didn't have a functional GPS, was brand new (1 week), problem was I rooted in the first day
Factory reset, hid superuser app, got a new l90
Gud luck
Click to expand...
Click to collapse
hard reset does not remove all traces of root. There is RCT checking. u can be sure that have no traces of root when RCT was reset. On kit kat we have chance to reset it without reflashing. But on 5.0 only reflash
---------- Post added at 11:17 ---------- Previous post was at 11:11 ----------
wmosquini said:
dear, sorry the English, but I need a help from you.
I made the installation of IMG extracted the KDZ and did flash the recovery, however, now my machine not the sign of life, the computer does not detect the device, the device does not turn on, not of any sign of life. already tried in various corners anything to help me have some solution. I did the procedure based on the stock rom flash D405 with img extracted files. After that the only active device the display if I put to load without the battery, which displays the battery with a question mark. The device does not enter download mode, does not go into recovery, does not display anything, as if completely dead. Does anyone have aware and know any solution to the problem? Note: I've tried the LG flahs tools, it does not detect the device.
Click to expand...
Click to collapse
Did u flash it from 5.0 or 4.4? This problem may have solve without service center. But if u have warranty, it must not worry u.
@linasj
Hello, I just want to know that while booting, did your phone show the message "Secure booting error"?
I am getting this message at the LG logo and then device just shuts off.
No, I don't think I ever got this message.
Sent from my LG-D405N using XDA Free mobile app.
pick.orion said:
@linasj
Hello, I just want to know that while booting, did your phone show the message "Secure booting error"?
I am getting this message at the LG logo and then device just shuts off.
Click to expand...
Click to collapse
In my case, the device did not care and neither carried, gave no sign of life. I sent him for assistance in less than one week they made the repair by warranty.
Hey guys, second time this issue has happened now for me but seems worse now. I used posts from here to resolve back in March when device got stuck in a boot loop after an OTA update, I managed to use Odin and a firmware from Sams Mobile to flash the phone and get it working again.
This time seems different though, I haven't tried the above steps yet, but none of the drives are mounting in the android recovery menu, which makes me think the device is going to need replacing. Anyone else come across this?
Seems different?
Well I would try Odin and an official ROM anyway, no pain no gain right?
What exactly were you doing before this occured?
You try the old delete usb driver, restart computer, install usb driver then restart computer and restart phone and try again.
SirDigbyCC said:
Hey guys, second time this issue has happened now for me but seems worse now. I used posts from here to resolve back in March when device got stuck in a boot loop after an OTA update, I managed to use Odin and a firmware from Sams Mobile to flash the phone and get it working again.
This time seems different though, I haven't tried the above steps yet, but none of the drives are mounting in the android recovery menu, which makes me think the device is going to need replacing. Anyone else come across this?
Click to expand...
Click to collapse
there is never a bricked device for good just keep searching using very device speacific info, check on youtube and search the names exactly as the ypop up there will always be something
flairepathos.info said:
there is never a bricked device for good just keep searching using very device speacific info, check on youtube and search the names exactly as the ypop up there will always be something
Click to expand...
Click to collapse
Looks like he bricked his bootloader's storage access driver, which AFAIK is unrecoverable unless download mode / sahara / etc is fine, but if the board is refusing to mount data while in the bootloader, it's safe to bet the rest of the modes are ****ed.
To answer a few of your questions in one go:
When I flashed it before it was back in end of Feb so a good while ago.
Just before it went into this boot loop it was working normally playing music in my pocket while doing gardening.
Using ODIN this time failed as I don't think it could access any of the drives.
SapphireEX said:
Looks like he bricked his bootloader's storage access driver, which AFAIK is unrecoverable unless download mode / sahara / etc is fine, but if the board is refusing to mount data while in the bootloader, it's safe to bet the rest of the modes are ****ed.
Click to expand...
Click to collapse
Oh I see the issue now you need to wipe all and re-flash full firmware when flashing the device using Odin
if that doesn't work flash the partitions with the kernel drivers and system partition
I had a similar issue with my current mtk phone and it was because the boot/preloader partition bilieved i had flashed the wrong firmware for my device(it was just a different firmware release for my phone
Just to be safe some ota updates break wehn the bootloader is not unlocked (when updationg from say android 8(oreo) -9(pie)...)
especially because of code errors in the update, cache/vendor partition being too full after downloading update
SirDigbyCC said:
To answer a few of your questions in one go:
When I flashed it before it was back in end of Feb so a good while ago.
Just before it went into this boot loop it was working normally playing music in my pocket while doing gardening.
Using ODIN this time failed as I don't think it could access any of the drives.
Click to expand...
Click to collapse
If you're telling the truth, and it wasn't a bad module / firmware / etc, it is possible your eMMC got too hot and melted some solder. I've seen it happen before.
You'll want to diagnose everything you can. If you're on Windows, does it recognize a USB device or a COM device? If linux, does lsusb return anything useful about it?
If it's not being detected, and multiple wires doesn't change anything, are you able to access sahara mode / download / DFU? If so, go to those and try again.
If you are lying, and this is a bad firmware flash / OTA brick, you'll need to tell us otherwise we'll be going in circles.
So ODIN does recognise the device when in android recovery mode i choose the bootloader, but when starting it, it fails. I'll give it longer tomorrow but my inclination is it's a chip failure. I don't know hot to tell if it was a bad firmware flash, but the first (and only) time I flashed it was back in late Feb / Early March, and I have been using it fine with many OTA updates since then using the phone normally since. Before the boot loop I was playing music via Bluetooth speaker but the battery died while gardening, which the battery died on so played music directly on the phone (no update or anything) and the music stopped halfway through the song and it was in a boot loop.
I am taking the phone in for repair on Wednesday but it's really frustrating because I legitimately want to get to the route cause of the issues. I am covered by Samsung Care +, but I feel like if I screwed up the first flash, it's still only as a result of that first OTA update going wrong in the first place. Does that make sense?
SirDigbyCC said:
So ODIN does recognise the device when in android recovery mode i choose the bootloader, but when starting it, it fails. I'll give it longer tomorrow but my inclination is it's a chip failure. I don't know hot to tell if it was a bad firmware flash, but the first (and only) time I flashed it was back in late Feb / Early March, and I have been using it fine with many OTA updates since then using the phone normally since. Before the boot loop I was playing music via Bluetooth speaker but the battery died while gardening, which the battery died on so played music directly on the phone (no update or anything) and the music stopped halfway through the song and it was in a boot loop.
I am taking the phone in for repair on Wednesday but it's really frustrating because I legitimately want to get to the route cause of the issues. I am covered by Samsung Care +, but I feel like if I screwed up the first flash, it's still only as a result of that first OTA update going wrong in the first place. Does that make sense?
Click to expand...
Click to collapse
I'm going to call hardware failure. It's extremely rare that any device will do what yours is doing without a bad firmware flash.. It's possible you had an OTA and it auto updated, then broke, but I doubt it.
SapphireEX said:
I'm going to call hardware failure. It's extremely rare that any device will do what yours is doing without a bad firmware flash.. It's possible you had an OTA and it auto updated, then broke, but I doubt it.
Click to expand...
Click to collapse
I appreciate the vote of confidence, I don't think it was an OTA update that did it this time, it usually requests to do updates which I highly doubt I would have pocket approved through a flip case only short after pressing play on Spotify.
So I have taken it into Samsung for repair and they have confirmed it's a hardware issue that feels vindicating!
SirDigbyCC said:
So I have taken it into Samsung for repair and they have confirmed it's a hardware issue that feels vindicating!
Click to expand...
Click to collapse
how much are they charging for the repair though? probably a motherboard replacement ? boy thats not going to be cheap!
shriom_manerker said:
how much are they charging for the repair though? probably a motherboard replacement ? boy thats not going to be cheap!
Click to expand...
Click to collapse
It was free, turned out to be a hardware issue internally so I think covered by warranty as I have Care+ which has an excess of £40 which they didn't make me pay. They also replaced the screen due to some dead pixels, and the battery! Happy days!
Thanks all for your suggestions!