Related
A few days ago I bricked my phone. I performed a SPL flash which seemed to go ok, the phone rebooted and then just stuck at the first splash screen. I waited for 30 minutes and it was still there.
I then removed the battery, reinserted it, and tried booting into recovery mode. Nothing happened, it just stuck at the first splash screen.
So I removed the battery again, reinserted it, and tried booting into fastboot mode. Nothing happened, it just stuck at the first splash screen.
I repeated these steps a few times with the same result.
I tried booting it with the USB cable attached, the result was the same, and Windows showed the phone as an 'unrecognized device'.
At this point, I was nearly crying, my phone was a brick.
Then, for some reason I tried the following:
-On the PC, i ran the command 'fastboot boot recoveryimage.img'.
-At this point the command says 'waiting for device' (or something like that).
-I removed the battery.
-I Connected USB.
-I inserted the battery.
-I booted the phone while holding the HOME key.
-The phone still froze at the first splash screen, but then suddenly, the waiting fastboot command detected the phone and booted the recovery image! Yay!
That's it. I didn't test it any more thoroughly for obvious reasons, I just reflashed the SPL and everything was back to normal.
I hope this helps someone in the future....
Very nice..
wow seriously, didnt expected that..
good job mate!
btw wat did u do to cause the brick?
Just read the very first line of his post...
marcdbl said:
A few days ago I bricked my phone. I performed a SPL flash which seemed to go ok, the phone rebooted and then just stuck at the first splash screen. I waited for 30 minutes and it was still there.
[...]
Click to expand...
Click to collapse
mgear356 said:
btw wat did u do to cause the brick
Click to expand...
Click to collapse
As I said above, I had been flashing the SPL, and when I rebooted following the flash it was bricked (stuck at first splash screen).
It's weird, because once I managed to get back into fastboot, I simply flashed the same SPL again and it worked fine.
thats not really unbricking your phone. gotta be bricked meaning it wont even go to the splashscreen. and there is no way to unbrick it at that point. Still for those that end up in same situation as you this might help indeed.
goa200 said:
thats not really unbricking your phone. gotta be bricked meaning it wont even go to the splashscreen. and there is no way to unbrick it at that point. Still for those that end up in same situation as you this might help indeed.
Click to expand...
Click to collapse
Never seen someone say the splash screen isn't coming up without blaming the hardware. I didn't think that flashing the wrong SPL would case the splash to not come up. I bricked my first phone by stupidly flashing the wrong SPL first before loading an OS. I thought the whole point of using the word 'brick' was when referring to the phone failing to enter 'fastboot' and 'recovery mode'. At that point, the phone would technically be a 'brick'. This has to be the first post I've seen with a possible fix but I could be wrong since I gave up on fixing that phone awhile ago.
goa200 said:
thats not really unbricking your phone. gotta be bricked meaning it wont even go to the splashscreen. and there is no way to unbrick it at that point. Still for those that end up in same situation as you this might help indeed.
Click to expand...
Click to collapse
bricking means you can't get to fastboot or recovery no matter what you do.
so he counts as bricking.
this might be a fix for the haykuro spl bricked users..
Well done if we have HTC G1 user with brick phone who want to try this methode and give feedback
goa200 said:
thats not really unbricking your phone. gotta be bricked meaning it wont even go to the splashscreen. and there is no way to unbrick it at that point. Still for those that end up in same situation as you this might help indeed.
Click to expand...
Click to collapse
No, You can still get to your splashscreen when the phone is bricked, If you cant turn on the phone then thats called the phone is dead not bricked. As stated already if you can't fastboot, or get to recovery then thats a brick.
Just tried it does not work and I was flash the death spl from haykuro,I am getting a new one but wanted to see if this works and I did not think it would which it didnt.
imfloflo said:
Well done if we have HTC G1 user with brick phone who want to try this methode and give feedback
Click to expand...
Click to collapse
Posted the fix on the android community forums. I have none person in mind, bricked it applying a spl, but he hasn't relied yet. Keep you informed if he does.
Did you reflash ROM after applying spl..? If you did and it still didn't boot then that should most likely be a brick. Can you boot into recovery right now and tell us your SPL version and radio?
goa200 said:
thats not really unbricking your phone. gotta be bricked meaning it wont even go to the splashscreen. and there is no way to unbrick it at that point. Still for those that end up in same situation as you this might help indeed.
Click to expand...
Click to collapse
Yes bricking your phone is when it wont even turn on! In the case of the sapphire when you hold power the led will flsh red quickly once then nothing.
On the blackstone you dont even get the pleasure of the led flash if your phone will turn on there is a way to get it fixed.
When ive been stuck on the bootscreen i have managed to revert using sappimg.nbh (which is 32b in my case) dunno where i got it from but i have it!
sappimg.zip (which is 32A) i got from Amon_RA's post and also have that, ive managed to revert back with both images after being stuck on "red screen of death"
A bit of a personal opinion here:
"Dead" is when the phone doesn't respond to anything, at all.
The charging light does not come on, the power button does nothing, and there is not so much as a flicker in the screen. Also, it is completely inaccessible for hardware debugging (JTAG, serial, USB or otherwise). This usually happens from a hardware problem, or doing something stupid like zero'ing the IPL.
Examples:
- My brother dropped his Nokia N75 in water. It's dead.
- I dropped my Cingular 8125 (HTC Wizard) on the ground. It doesn't power on any more, and plugging it into the charger does nothing. Voltmeter shows a charge running through some areas of the device's motherboard once disassembled. It's dead.
Solutions: Replace, recycle or sell for parts.
"Bricked" is when a purely software problem causes the device to no longer respond.
This may happen on many levels, but usually results in the OS not booting, or booting and being completely unusable (e.g. stopped with kernel panic at OS splash). It may light up and/or show a splash screen, but it fails to enter the bootloader or recovery menus. Its recoverability may vary, but will usually involve a debugging tool and a computer, and likely a copmlete wipe of everything on the device. Even if it's heavily bricked, if it can be recovered via JTAG or similar, it's not "dead".
Examples:
- HTC Dream only goes as far as splash screen, and freezes there. Does not respond to ADB. Does not enter recovery, or bootloader, however fastboot responds.
- HTC Dream shows blank screen, but lights up as if it were powering on. Fastboot does not respond. I connect my HTC ExtUSB Serial dongle to it though, and I'm able to get a response to some commands.
- Western Digital MyBook World Edition NAS powers on, and spins up hard drive, but does not go any farther than that. Front lights do not light up, and no hard disk activity is heard. Networking is not yet enabled. Hard drive can, however, manually be connected to a PC with SATA, and the firmware image re-written to its partitions.
- XBOX (the original) was softmodded, but the dashboard.xbe (the OS shell) was overwritten. It now just stays at the Microsoft logo.
- iPhone was recently jailbroken and SIM unlocked, then Apple pushed an update on me, and my iPhone is in a state where it doesn't enter DFU/Recovery, and when it boots, it says "Emergency calls only."
Solutions: Be very careful not to further brick the device, but use any methods available. Be sure to check documentations, search forums, and then ask questions if unsure. Make sure you finish every process you start.
After this, might just be hardware "damage" (like a power button not working right) or software "errors", like the home screen failing to load because of "Process com.google.android.gapps quit unexpectedly." These are usually relatively easy to fix, or have fixed.
Again, this is just an opinion.
Back on topic though, I seriously wouldn't have probably thought of using fastboot while it's stuck at the G1 screen, unless mine were bricked. Kudos to you, and I hope this works on some other bricked G1's out there (At least ones with the Engineering/Hard/DangerSPL, the stock SPL doesn't support fastboot as far as I know.)
bonesy said:
Yes bricking your phone is when it wont even turn on! In the case of the sapphire when you hold power the led will flsh red quickly once then nothing.
On the blackstone you dont even get the pleasure of the led flash if your phone will turn on there is a way to get it fixed.
When ive been stuck on the bootscreen i have managed to revert using sappimg.nbh (which is 32b in my case) dunno where i got it from but i have it!
sappimg.zip (which is 32A) i got from Amon_RA's post and also have that, ive managed to revert back with both images after being stuck on "red screen of death"
Click to expand...
Click to collapse
Won't agree with that, what you describe as a brick is a DEAD mobile. A brick is a useless piece which wont get into any state of recovery. The only thing i will agree with is that if it'll turn on there is a way to get it fixed that's why we even got the word unbricking which is done with many other pieces than Android mobiles.
Hope this will get us closer to a unbricking method which works on all the BRICKED pieces out there.
Good job dude!
Yes, my phone is back!
I bricked my G1 about 2 months ago pretty much the same way marcdbl did.
I gave up on it and sit it aside getting a new MT3G.
Sweet, now I got 2 phones to play with.
Thank You marcdbl
wow sweet news
fishman0919 said:
Yes, my phone is back!
I bricked my G1 about 2 months ago pretty much the same way marcdbl did.
I gave up on it and sit it aside getting a new MT3G.
Sweet, now I got 2 phones to play with.
Thank You marcdbl
Click to expand...
Click to collapse
Very glad to hear that your dead or bricked or whatever-you-may-call phone is back to LIVE!!!
So I think this solution works for some certain people. So i think rather than arguing on terminology, better spread this good trick to people who had dead/bricked/whatevery-you-may-call phone. IMHO
Thanks for the solution.
Best,
Thihaz
marcdbl said:
A few days ago I bricked my phone. I performed a SPL flash which seemed to go ok, the phone rebooted and then just stuck at the first splash screen. I waited for 30 minutes and it was still there.
I then removed the battery, reinserted it, and tried booting into recovery mode. Nothing happened, it just stuck at the first splash screen.
So I removed the battery again, reinserted it, and tried booting into fastboot mode. Nothing happened, it just stuck at the first splash screen.
I repeated these steps a few times with the same result.
I tried booting it with the USB cable attached, the result was the same, and Windows showed the phone as an 'unrecognized device'.
At this point, I was nearly crying, my phone was a brick.
Then, for some reason I tried the following:
-On the PC, i ran the command 'fastboot boot recoveryimage.img'.
-At this point the command says 'waiting for device' (or something like that).
-I removed the battery.
-I Connected USB.
-I inserted the battery.
-I booted the phone while holding the HOME key.
-The phone still froze at the first splash screen, but then suddenly, the waiting fastboot command detected the phone and booted the recovery image! Yay!
That's it. I didn't test it any more thoroughly for obvious reasons, I just reflashed the SPL and everything was back to normal.
I hope this helps someone in the future....
Click to expand...
Click to collapse
where were you 2 months ago dude? I paid 270€ to change the board on my magic
Good Job! Thanks for the info
I've tried the "brick fixes" on this forum, but without luck so far... I can get into download mode, and I've tried flashing with odin from this post which says "passed" to me. After this is reboots into a black screen after the "galaxy S" screen, and nothing can be done except making the capasitive buttons light up...
All help is appreciated!!
FYI I don't have a SD card installed during odin...
Solutions in #6 and #7...
Thanks a ton
Novek said:
I've tried the "brick fixes" on this forum, but without luck so far... I can get into download mode, and I've tried flashing with odin from this post which says "passed" to me. After this is reboots into a black screen after the "galaxy S" screen, and nothing can be done except making the capasitive buttons light up...
All help is appreciated!!
FYI I don't have a SD card installed during odin...
Click to expand...
Click to collapse
Sounds like a boot loop, but I can't figure out why you would get one with the stock odin flash. Try doing a factory reset? it shouldn't be needed, but who knows?
how? tried the "hard reset" whitout luck
Novek said:
how? tried the "hard reset" whitout luck
Click to expand...
Click to collapse
In recovery.. there should be a factory reset option. I thought odin did that though.
when it is resetting I can read "mbr checksum error" or similar in yellow text before it's wiping data etc...
Try this ...turn you phone off but keep it plugged into you cpu usb cord and open oidin, next put your phone in download mode and put the needed files in oden and click start I had a hard time getting odin to work right for some reason this may not help but it worked for me. Good luck I don't think you bricked I think you can come out of this.
I assume that you used the partition in ROM Manager? If so I had the same problem as you. The phone would boot up to a black screen with only the buttons working. What I did was flash Eugenes 2.2 Froyo Rom, I surprised that it booted up and worked. After that I flashed back to stock rom and it work as it did before!
AustinKnight45 said:
Try this ...turn you phone off but keep it plugged into you cpu usb cord and open oidin, next put your phone in download mode and put the needed files in oden and click start I had a hard time getting odin to work right for some reason this may not help but it worked for me. Good luck I don't think you bricked I think you can come out of this.
Click to expand...
Click to collapse
Thanks for the help, but my problem occurs after odin... when it's rebooting and it says "passed!" i just end up with a black screen with only the capasitive buttons lighting up when pressed...
ElahC said:
I assume that you used the partition in ROM Manager? If so I had the same problem as you. The phone would boot up to a black screen with only the buttons working. What I did was flash Eugenes 2.2 Froyo Rom, I surprised that it booted up and worked. After that I flashed back to stock rom and it work as it did before!
Click to expand...
Click to collapse
that's my problem!! found it, downloading now... will report back for future accidents...
Froyo worked!! Thanks a ton! Now I just have to downgrade
sry... dubbel
I HAVE THE SAME PROBLEM. How did you get odin to detect your phone? I put it into download mode but no detection plzzz help
farrisizdaman said:
I HAVE THE SAME PROBLEM. How did you get odin to detect your phone? I put it into download mode but no detection plzzz help
Click to expand...
Click to collapse
I turned the phone off while the usb was connected when the phone if off open odin ounce its open boot up the phone and boot it into download mode from there odin will connect and you can put the files you need into it and click start. This worked well for me when I needed to revert back to factory vibrant after flashing the "Real lag FIX" kernel that made my ear piece not work and some of my buttons not work but boy was my phone snappy and my benchmarks were awesome but what good does that do when your girl calls you and you cant hear her and all she can hear is you saying hellllllllooooooo .
I"ve been trying to flash with odin now for about 2 hours. It gets stuck on DO NOT DISCONNECT. And never finishes.
farrisizdaman said:
I"ve been trying to flash with odin now for about 2 hours. It gets stuck on DO NOT DISCONNECT. And never finishes.
Click to expand...
Click to collapse
Ya it was like that for me until I did what I said in my last post, you do have the samsung drivers installed ?
Edit: And you are using this method or this thread HERE
farrisizdaman said:
I"ve been trying to flash with odin now for about 2 hours. It gets stuck on DO NOT DISCONNECT. And never finishes.
Click to expand...
Click to collapse
You have managed to get into download mode right? My device is up and running stock now, but gonna try some other ROM now =)
Glad to hear your phone is back up and running .
i know this is an old thread, but i figure this can help someone later... brick is a common search term, and i figure this will come up in a search and this will save time for others...
here's what happened to me. i was flashing back to stock and was in download mode. the blue bar was moving etc and murphy and his dumb law decided to kill my my usb port... i thought the phone was DEAD! nothing i did woke the phone up. no battery indicator, buttons didn't do anything... it was all black. holding up/down and power didnt turn the phone on and into recovery or download mode... the phone was DEAD...
then after scouring the forum forever, i finally got the phone into download mode...
NOTE: i don't recall if the usb wire was plugged into the computer or not... i think it was though...
NOTE2: samsung drivers should have been installed already...
- remove the battery
- hold vol up and vol down buttons
- reinsert battery
i thought WOO HOO!! I GOT INTO DOWNLOAD MODE!!!
the next issue i had was getting odin to recognize the phone... it didn't detect what com port i had. but after a lot of reading, i finally got it to work...
- open odin first
- then get into download mode using the steps above...
after odin recognized the port the phone was plugged into, i flashed back to stock rom using the instructions given on this site... and my dead phone works again...
i was able to fix a dead phone!! this phone could be un-brickable!!
i hope this helps...
farrisizdaman said:
I HAVE THE SAME PROBLEM. How did you get odin to detect your phone? I put it into download mode but no detection plzzz help
Click to expand...
Click to collapse
Open odin first, then plug in your phone.
hi,
yesterday i try to put a room on my Atrix 4G but then i got a loop on the motorola logo i wait for an hour, then i saw a post to unbrick my atrix, i did all the steps and now the phone doesnt turn on, just the led light in green sometimes. suggestions ?
thanks
For 1 the phone was only soft bricked you could of sorted it via recovery. We need more info what ROM what steps did you take?
Sent from my MB860 using Tapatalk
the rom was gingerblur. i follow the instructions but it failed, then i use the RSD to unbrick it but it failed too,
http://forum.xda-developers.com/showthread.php?t=991595 <--- gingerblur
instructions i followed
http://briefmobile.com/atrix-4g-rom-installation-guide
can somebody help me ?
You're using antiquated directions, from April of last year. There are much more ROMs and recovery software now that are better. Can you get into recovery mode or RSD mode by pressing the volume down when you see the motorola logo? hard to tell where you're at right now.
my phone is plug into my computer without the battery and the only thing on is a green led when i try to turn it on anything happen...
im affraid if i hard bricked my phone i just got it this week and i try to change gingerbread stock rom because i dont like it and now doesnt turn on...
i plug my phone with a wall cord and now i see
SVF: 105:1:2
Failed to boot 0x1000
entering NvFlash Recovery mode
battery is too low to flash
I'm not sure what you did to undo your original brick, but you likely flashed a SBF file that was a downgrade or something. If all you see is nvflash, you're hard bricked. From what you've told us in this thread, you used a pseudo ROM that hasn't been updated since June of last year, using a recovery that is ancient and irrelevant, and directions that did not apply to your situation. Sorry man.
Source: http://forum.xda-developers.com/showthread.php?t=1160408
it probably voided the warranty. So, you would have to pay to have it re-flashed. That might come in a little cheaper than buying a brand new one.
i actually messed it up too when i flashed my atrix for the first time but people are very helpful here n they helped me get it fixed. im trying to find that post n ill post it as soon as i find it. had a different account
Hi everyone, I'm a new member to the forum, but have been a follower for quite some time.
Let's start by introducing my device wich is:
EEEPad Transformer TF101G with ICS running the latest WW_9.2.2.6 firmware.
The device is rooted and running ASUS stock recovery.
Everything was working fine until I decided to do a Cold Boot.
It got stuck on the cold boot menu for like 3 hours and I decided to turn it off.
After that it got stuck on the inicial Asus splash screen. I forced it to turn off a couple a times and it eventually booted up.
I knew something wasn't right, so I backed up all my files and applications.
Then decided to do a factory reset through POWER + VOL-
After that it never booted again, and after a few seconds on the splash screen I hear a click noise, like the hard drive is turning off.
When I try force it to turn off, it starts up again automatically.
I've tried to flash it through nvflash, but being a TF101G it also means it is sbkv3, wich is not supported by nvflash.
Also tried boot recovery tools, but it won't even start, because as I try to connect it to the computer through adb mode, after that "click" noise, the device becomes disconnected.
I didn't try any dangerous applications and stuff like that, just decided to do a simple cold boot, the device is a week old.
If I'm posting this in the wrong section I apologize.
And hope someone can come up with a good idea.
Thanks in advance.
Obviously somethings corrupted and in my opinion the only way to fix it would be to reflash the rom in apx mode using nvflash but that doesn't seem to be possible for your device as of yet but if everything is still stock maybe you can unroot the device (or play dumb) and get it replaced under warranty?
I don't think I can unroot it, since it won't run abd mode.
I'm trying to find a way of not having to send it to warranty.
Saving it as a last resort...
Akusura said:
I don't think I can unroot it, since it won't run abd mode.
I'm trying to find a way of not having to send it to warranty.
Saving it as a last resort...
Click to expand...
Click to collapse
Eek.. since it was factory resetted I think you need to send it to warranty. Not much we can do now with just a splash screen on sbkv3
I don't consider myself an advanced user.
But I really did search everywhere and I got the idea that only with APX and without a compatible NVFlash I was screwed.
But I still had some hope.
Do you think they will give me trouble because of it being rooted?
I my opinion I don't think they will ever know, because It won't boot, It won't run recovery mode (stock) and nothing else at all, the only way to fix it is to flash it, but maybe I'm just being naive.
I treated it with all the care in the world, so only by divine intervention it is a hardware problem.
But you never now...
you should be ok (should)......
i done pretty much the same thing to a customers TF and Asus fixed it no problem.
The fact is that I actually didn't do anything wrong.
Just a cold boot that didn't work, followed by a a factory reset...
How long did it take for yours to get fixed?
So I have a Samsung Galaxy Gran Prime Duos G530BT and I was installing the TWRP recovery mode on it, the app asked for restart the phone to test the recovery mode, but when I restarted it the phone didn't boot anymore. He just vibrate and nothing appers on the screen.
I can't even get acess to the recovery mode to fix it. Can someone help me?
(I try to use the flash tool since he doesn't boot, but the stock room don't have any scatterd file...)
something similar happend to me..
rxxern said:
So I have a Samsung Gran Prime Duos GM-530BT and I was installing the TWRP recovery mode on it, the app asked for restart the phone to test the recovery mode, but when I restarted it the phone didn't boot anymore. He just vibrate and nothing appers on the screen.
I can't even get acess to the recovery mode to fix it. Can someone help me?
(I try to use the flash tool since he doesn't boot, but the stock room don't have any scatterd file...)
Click to expand...
Click to collapse
same as yours but mine has logo displayed and i cant turn on or put in recovery mode can you please message me if you find a way to fix it?
HyperVenoms said:
same as yours but mine has logo displayed and i cant turn on or put in recovery mode can you please message me if you find a way to fix it?
Click to expand...
Click to collapse
Yeah, sure!
This might be stupid, but did you try use Odin? Since your logo appears, I think you're in a better condicion then me, lol.
No but i found a solution
rxxern said:
Yeah, sure!
This might be stupid, but did you try use Odin? Since your logo appears, I think you're in a better condicion then me, lol.
Click to expand...
Click to collapse
ok so i couldnt put it into recovery mode or anything it was stuck so i took out the battery then held volume down power and home then pressed down to restart device and it came on successfully i hope this also works for you
rxxern said:
So I have a Samsung Gran Prime Duos GM-530BT and I was installing the TWRP recovery mode on it, the app asked for restart the phone to test the recovery mode, but when I restarted it the phone didn't boot anymore. He just vibrate and nothing appers on the screen.
I can't even get acess to the recovery mode to fix it. Can someone help me?
(I try to use the flash tool since he doesn't boot, but the stock room don't have any scatterd file...)
Click to expand...
Click to collapse
Try to download its stockrom boot it into download mode not recovery since recovery doesnt work any more i think its volume - if not + ,power button and Home button then dow load ODIN and flash the it so as to guarentee it to boot up again.
link for the devices stock rom
#https://docs.google.com/uc?id=0B7pEcClQW-2JenF1cW9jb05OVlk&export=download
thanks enjoy!!
No that lucky
HyperVenoms said:
ok so i couldnt put it into recovery mode or anything it was stuck so i took out the battery then held volume down power and home then pressed down to restart device and it came on successfully i hope this also works for you
Click to expand...
Click to collapse
So lucky! I can't do that to mine, when I put the battery out and try to do this, my phone has no response. ):
out of options
marwachacha said:
Try to download its stockrom boot it into download mode not recovery since recovery doesnt work any more i think its volume - if not + ,power button and Home button then dow load ODIN and flash the it so as to guarentee it to boot up again.
link for the devices stock rom
thanks enjoy!!
Click to expand...
Click to collapse
Thanks for the tip, but I really think I hard brick my phone, he just vibrate when the battery is on, when I try to turn him on just with the charger I get no response, my computer cannot ever reconize him. An since it's a national model there isn't much support for it on the internet (now I do regret getting him). I opened him to try force the reconization, but I don't find the force preloader mode test point and there is no way I can get a JTAG on Brazil.
TWRP Recovery Mode f*** me really hard this time.
Now if someone could help me finding the colo/kolo/whatever point on my phone I would really appreciated.
rxxern said:
Thanks for the tip, but I really think I hard brick my phone, he just vibrate when the battery is on, when I try to turn him on just with the charger I get no response, my computer cannot ever reconize him. An since it's a national model there isn't much support for it on the internet (now I do regret getting him). I opened him to try force the reconization, but I don't find the force preloader mode test point and there is no way I can get a JTAG on Brazil.
TWRP Recovery Mode f*** me really hard this time.
Now if someone could help me finding the colo/kolo/whatever point on my phone I would really appreciated.
Click to expand...
Click to collapse
Am not much sure if ti is hard bricked since you sayed that it vibrates lets look how much characteristics of a bricked device of which it posseses so as to conmfirm that it is hard bricked.
Soft Brick - Struck inBoot loop
2. Super Brick - Stuck atflashing Factoryfs.IMG in ODIN . Also called as EMMC Bug
3. Hard Brick -Dead / Costly Paper weights
4. Dead Brick - No chargingbattery sign also - Mostly = Hard Brick; But there is a window of possibilityby a USB JIG for SamsungPhones.
5. OTA Brick - Encountereddue to updating OTA on a rooted Stock ROM
6. CM12 Brick - when CM12encountered a /data write error. Worst is ODIN Flashing Fails
7. Pixel Salad: This is a problemof the graphics unit or the screen which fails to display correctly the imageand put instead random colored pixels on some areas of the screen or the wholescreen. It’s hard to even let the other members know what you are facing sinceyour screenshots would be just clean as it would have been. This also requiresa need for hardware checking if reflashing ROM doesn't work.
Soft brick means a temporary problem, which could be fixed. Soft brick usuallyoccurs after installing custom rom(s) or incorrect installation procedure whichinstallation/manipulation of files like permission settings, erasing systemfiles that is not compatible with each phone.
SOFT BRICKED
PHYSICAL CHARACTERISTICS TO MENTION FEW ARE
Phone struck on OEM logo.
Phone struck on a ROM logo "bootanimation"
The phone does not simply power up
or any other you can add up
HARD BRICKED
PHYSICAL CHARACTERISTICS TO MENTION FEW ARE
· No signs that can turn on directly
· The Charging won't work.
· Phone not detected when connected to a PC
· The LED's do not light up immediately
· No Sound / Vibrate
· Your phone completely off (Paper Weight)
Simply put it cannot be repaired using SEUS, FLASHTOOL, ODIN or even PC COMPANION.
marwachacha said:
Am not much sure if ti is hard bricked since you sayed that it vibrates lets look how much characteristics of a bricked device of which it posseses so as to conmfirm that it is hard bricked.
Soft Brick - Struck inBoot loop
2. Super Brick - Stuck atflashing Factoryfs.IMG in ODIN . Also called as EMMC Bug
3. Hard Brick -Dead / Costly Paper weights
4. Dead Brick - No chargingbattery sign also - Mostly = Hard Brick; But there is a window of possibilityby a USB JIG for SamsungPhones.
5. OTA Brick - Encountereddue to updating OTA on a rooted Stock ROM
6. CM12 Brick - when CM12encountered a /data write error. Worst is ODIN Flashing Fails
7. Pixel Salad: This is a problemof the graphics unit or the screen which fails to display correctly the imageand put instead random colored pixels on some areas of the screen or the wholescreen. It’s hard to even let the other members know what you are facing sinceyour screenshots would be just clean as it would have been. This also requiresa need for hardware checking if reflashing ROM doesn't work.
Soft brick means a temporary problem, which could be fixed. Soft brick usuallyoccurs after installing custom rom(s) or incorrect installation procedure whichinstallation/manipulation of files like permission settings, erasing systemfiles that is not compatible with each phone.
SOFT BRICKED
PHYSICAL CHARACTERISTICS TO MENTION FEW ARE
Phone struck on OEM logo.
Phone struck on a ROM logo "bootanimation"
The phone does not simply power up
or any other you can add up
HARD BRICKED
PHYSICAL CHARACTERISTICS TO MENTION FEW ARE
· No signs that can turn on directly
· The Charging won't work.
· Phone not detected when connected to a PC
· The LED's do not light up immediately
· No Sound / Vibrate
· Your phone completely off (Paper Weight)
Simply put it cannot be repaired using SEUS, FLASHTOOL, ODIN or even PC COMPANION.
Click to expand...
Click to collapse
Even if it's not hard bricked I had no idea on how bring him into life again, since the only signal of life he gives me is the vibration with the battery on.
It could make my computer detect him it would be much easier.
hmmm
rxxern said:
Even if it's not hard bricked I had no idea on how bring him into life again, since the only signal of life he gives me is the vibration with the battery on.
It could make my computer detect him it would be much easier.
Click to expand...
Click to collapse
this may sound dumb but maybe your screen is broke i highly doubt it because of what happened but if you can feel the vibrations but not see the screen then maybe its the screen. There will probably be a way to fix it but im unsure. Its funny how you call your phone him
HyperVenoms said:
this may sound dumb but maybe your screen is broke i highly doubt it because of what happened but if you can feel the vibrations but not see the screen then maybe its the screen. There will probably be a way to fix it but im unsure. Its funny how you call your phone him
Click to expand...
Click to collapse
I didn't mention this but the screen also blinks when is vibrating so... And if It was the screen the computer should reconized the phone, shouldn't?
Haha, english it's not my native language, so I get confuse sometimes, and i don't know calling it him sounds more right for me (?????).
rxxern said:
Even if it's not hard bricked I had no idea on how bring him into life again, since the only signal of life he gives me is the vibration with the battery on.
It could make my computer detect him it would be much easier.
Click to expand...
Click to collapse
rxxern said:
I didn't mention this but the screen also blinks when is vibrating so... And if It was the screen the computer should reconized the phone, shouldn't?
Haha, english it's not my native language, so I get confuse sometimes, and i don't know calling it him sounds more right for me (?????).
Click to expand...
Click to collapse
haha ok, i habe no idea what to do wiith your phone try searching other threads maybe ???
rxxern said:
I didn't mention this but the screen also blinks when is vibrating so... And if It was the screen the computer should reconized the phone, shouldn't?
Haha, english it's not my native language, so I get confuse sometimes, and i don't know calling it him sounds more right for me (?????).
Click to expand...
Click to collapse
also in advance try to change the usb cable which you are using to connect (him) with your computer as well as try different Pc's may Be yours might have some usb port drivers corrupted also try to install the ADB interface drivers in your pc so as you can enhance your Pc detect the devices even if they are powered off gues it will work still i have hope with your (him) buddy!!!
Nothing better than xda.
I am having the same problem with my G530BT. Managed to solve ?
rxxern said:
So I have a Samsung Galaxy Gran Prime Duos G530BT and I was installing the TWRP recovery mode on it, the app asked for restart the phone to test the recovery mode, but when I restarted it the phone didn't boot anymore. He just vibrate and nothing appers on the screen.
I can't even get acess to the recovery mode to fix it. Can someone help me?
(I try to use the flash tool since he doesn't boot, but the stock room don't have any scatterd file...)
Click to expand...
Click to collapse
I am having the same problem with my G530BT. Managed to solve ?
Raphaelfla said:
I am having the same problem with my G530BT. Managed to solve ?
Click to expand...
Click to collapse
Ow, one year latter I don't think this will help you anymore, but just in case someone has the same question: I didn't solve the problem, I took it to the Samsung assistence and discover that the motherboard was damaged, they would have to replace it.