Hello, new to XDA and hope I can get some solutions for this goddamn phone!
It's been a few weeks since my phone is in a useless state, and whenever I open my phone, the screen stays completely black and for some odd reason, the blue light on the top corner is on. The phone gets warmer, and it just stays in that state. For hours. Unless I hold volume down + home button, then start button altogether for 20-25 secs. Now, you can tell me to go to recovery mode by holding volume up + start, it doesn't work, I tried SEVERAL times. Phone cannot start. Nothing. There are no physical damages.
I did some research and it's most likely hardbrick, but since I can't even get to recovery mode or anything, it's not like I can even un-brick the phone. The only solution I see now is to send my phone to Samsung. I bought it online last December, so Samsung might tell me to buy a new phone with a discount, which is something I don't want to do, since there's still pics, notes and phone numbers in it. Is there any solution? Keep in mind the phone won't start or go in recovery mode. I'm dead srsly
Hard-Brick ------ Bootloader is corrupted, your device is permanently dead and unusable.
Only solution is to use JTAG to force your device to download mode.
Soft-Brick ------ Freezes to "Samsung . . . powered by Android" or Bootloops to samsung logo. .Can be recovered via Odin or restored via NANROID backup (if any).
Hard-Bricked phones are very difficult to recover. .
Azhero said:
Hard-Brick ------ Bootloader is corrupted, your device is permanently dead and unusable.
Only solution is to use JTAG to force your device to download mode.
Soft-Brick ------ Freezes to "Samsung . . . powered by Android" or Bootloops to samsung logo. .Can be recovered via Odin or restored via NANROID backup (if any).
Hard-Bricked phones are very difficult to recover. .
Click to expand...
Click to collapse
That sounds annoying. So it is hardbricked. Do you think I'm better off just sending it to Samsung? What are the chances for them to be able to activate my phone again?
Thanks.
Related
Hello All,
Hoping someone will be able to assist me, though I'm starting to lose hope.
I have spent all day so far reading threads, and trying various suggestions and fixes, but nothing has really helped and I'm beginning to think the phone may just be kaput.
Initial issue was nothing out of the ordinary; woke up to find the phone was not responding so pulled the battery. After putting the battery back in, the phone would no longer turn on. Uh oh. Did the obvious, repull the battery, try again. Nothing. Connect to charger (nothing happens, no charging icon on screen). At this point I think the battery has died so I bought a new one. No change, phone still won't turn on and nothing happens when I plug it in to charge.
So now I connect it to my PC, and I get the installing hardware message trying to install the APX stuff which fails. After some research, I manage to get the APX drivers installed such that the phone is detected when I plug it in. More research, decide to try the AOI Toolkit to backup everything first. This works ok.
So now I try and enter recovery mode via Power key + Volume Down key. Nothing. Ok, change the recovery image then. Device is not detected via ADB method. NVFlash method instead then. The bootloader loads fine, the screen wakes up and shows the S/W Download... message. I figure this is a hopeful sign. I try all 3 (ics-cwm-5, ics-cwm-6, twrp-2.5). They all flash successfully. However, I can't enter recovery mode with any of them. Once I disconnect the phone, insert the battery and then hold down the Power + Volume Down buttons, nothing ever happens.
I've also tried the LG Update Tool and the Smartflash options, but the phone is never detected.
As a last resort I repartitioned. This also worked ok, but still no recovery mode.
tl;dr
Phone won't turn on, show as charging, or enter recovery mode. Works when connected as APX with AOI Toolkit.
Am I missing something? Doing something wrong? Any assistance is greatly appreciated. Thx.
Bump
Okay, I'm bumping this thread myself (mostly because I'm an idiot and this could happen to me, too), but to give you my two cents: Have you tried the Full Brick Repair tool? You flash it through NVFlash and apparently "it cures any brick". Try it and tell us how it went.
NoDze said:
Okay, I'm bumping this thread myself (mostly because I'm an idiot and this could happen to me, too), but to give you my two cents: Have you tried the Full Brick Repair tool? You flash it through NVFlash and apparently "it cures any brick". Try it and tell us how it went.
Click to expand...
Click to collapse
Thanks for the suggestion. The flash process itself completed without issue, but still nothing once the battery is inserted and the power button is pressed. I'm going to assume there is some sort of hardware issue at this point and consider the phone officially dead. Now, where's my hammer...?
xda_fanboy said:
Thanks for the suggestion. The flash process itself completed without issue, but still nothing once the battery is inserted and the power button is pressed. I'm going to assume there is some sort of hardware issue at this point and consider the phone officially dead. Now, where's my hammer...?
Click to expand...
Click to collapse
Don't give up yet. Try smartflash and flash stock, or whatever. Seriously. Just keep on trying. I had a Samsung Captivate a year back and something similar happened where I woke up one beautiful morning, tried to unlock my phone: no response. I thought I had an SOD, so I pulled the battery out, reinserted: bootloop. Entered recovery, can't flash anything, unable to mount system/data partitions. Turns out my internal memory/ROM got fried. Yay. But until then, I tried every possible option. Wow, this turned out to be a bit depressing. Just try more stuff. After you've tried everything, and I mean everything, declare the phone dead.
I think i have a similar problem. Just woke up to find my phone to be dead. Tried the usual methods, nothing. Best it could do was from time to time show me a battery sign with a red triangle and a whtie exclamation mark in it. Then sometimes i manage to get into the recovery mode, there i tried practically everything. Used restore, it shows that restore was a success, but when i reboot my phone i get into an endless circle of bootloader icon appearing and dissappearing,
EDIT: somehow from the countless attempt it fired up.
Make sure to have the right bootloader before nvflashing unbrick roms....
xda_fanboy said:
Hello All,
Hoping someone will be able to assist me, though I'm starting to lose hope.
I have spent all day so far reading threads, and trying various suggestions and fixes, but nothing has really helped and I'm beginning to think the phone may just be kaput.
Initial issue was nothing out of the ordinary; woke up to find the phone was not responding so pulled the battery. After putting the battery back in, the phone would no longer turn on. Uh oh. Did the obvious, repull the battery, try again. Nothing. Connect to charger (nothing happens, no charging icon on screen). At this point I think the battery has died so I bought a new one. No change, phone still won't turn on and nothing happens when I plug it in to charge.
So now I connect it to my PC, and I get the installing hardware message trying to install the APX stuff which fails. After some research, I manage to get the APX drivers installed such that the phone is detected when I plug it in. More research, decide to try the AOI Toolkit to backup everything first. This works ok.
So now I try and enter recovery mode via Power key + Volume Down key. Nothing. Ok, change the recovery image then. Device is not detected via ADB method. NVFlash method instead then. The bootloader loads fine, the screen wakes up and shows the S/W Download... message. I figure this is a hopeful sign. I try all 3 (ics-cwm-5, ics-cwm-6, twrp-2.5). They all flash successfully. However, I can't enter recovery mode with any of them. Once I disconnect the phone, insert the battery and then hold down the Power + Volume Down buttons, nothing ever happens.
I've also tried the LG Update Tool and the Smartflash options, but the phone is never detected.
As a last resort I repartitioned. This also worked ok, but still no recovery mode.
tl;dr
Phone won't turn on, show as charging, or enter recovery mode. Works when connected as APX with AOI Toolkit.
Am I missing something? Doing something wrong? Any assistance is greatly appreciated. Thx.
Click to expand...
Click to collapse
Try to flash a new recovery image in apx mode.
And edit the /dev/block/mmcblk0p3 partition your self.
seek=6144 count=75 bs=1 / boot-recovery
Thanks for the added input and encouragement folks.
Just reporting an update:
Having been unsuccessful more times than I could count, I decided to physically disassemble the phone (normally Engineering fix #2, but performed out of order on this occasion). I have zero idea why it should have made a difference, as all I did was take it apart and then put it back together, but the phone has groaned back to life.
Of course, then sausage-fingers here managed to tear the digitizer cable when doing the final reassambly... /facepalm
Anyhow, I have a replacement on order, so I'm hopeful that when I receive that in a few days I'm back to a fully functional Optimus 2x!!
Greetings,
My internal sd card died slowly over time. It failed to mount on some occasions at first. After a few weeks I had massive app crashes.
Everything I did on the phone (installing apps, deleting files, even doing a factory reset) seemed to revert back after rebooting the phone. I mean I delete some files, and after reboot, the files came back from the dead. Same thing for factory reset.
Installing other roms made the situation even worse, and I had to revert back to stock 2.3 rom.
And since last week, the phone is on permanent bootloop. It won't go into download or recovery mode (it used to activate those modes with 3 button combo before).
I tried the USB JIG method. Built a 301k resistor, connected pins to the usb thingie. It did power the phone on, but failed to trigger the download mode. The phone still goes into a boot loop.
Anyone has any ideas? I don't know what more information I can provide about the issue.
Regards,
No download mode?
If your phone won’t enter download mode, you can try three things:
A USB jig. Don’t pin your hopes on this, they rarely succeed in this scenario.
‘Jump starting’ – You might need someone else to give you a hand for this. Take the battery out of your phone and wait 30 seconds. Now, press the button combination to enter download mode, and with this combination still depressed, get someone to put the battery back in. Hopefully this will jolt your phone into download mode.
Take out the phone battery, and re-insert it, but don’t turn the phone on. Now, plug in the charger while holding the volume down button. Keep holding volume down till you enter download mode.
If your phone won’t enter download mode, and will do nothing but get hot when you attempt to do anything to it (charge it, turn it on), then your motherboard is in need of replacement.
Your options
I’ve seen a lot of people, when their Odin flash fails, either:
Give up. Not a good option.
Flash a .pit file. That should be used as an absolute last resort. There’s a lot to try before getting to that stage! If a flash of a .pit file fails in Odin, your phone is well and truly unrecoverable, and you will need a motherboard (MB) replacement.
Quoted from a quite by Hopper8, try these steps. Can't really do anything since recovery/download mode is dead. If you can get into download mode, flash a .pit file (get all the files ready beforehand). Be quick, since you don't know when your device will die again.
N7105 rocking AOSB with AGNi kernel,
Click "Thanks" if I was of any help!
FraggyDav said:
Greetings,
My internal sd card died slowly over time. It failed to mount on some occasions at first. After a few weeks I had massive app crashes.
Everything I did on the phone (installing apps, deleting files, even doing a factory reset) seemed to revert back after rebooting the phone. I mean I delete some files, and after reboot, the files came back from the dead. Same thing for factory reset.
Installing other roms made the situation even worse, and I had to revert back to stock 2.3 rom.
And since last week, the phone is on permanent bootloop. It won't go into download or recovery mode (it used to activate those modes with 3 button combo before).
I tried the USB JIG method. Built a 301k resistor, connected pins to the usb thingie. It did power the phone on, but failed to trigger the download mode. The phone still goes into a boot loop.
Anyone has any ideas? I don't know what more information I can provide about the issue.
Regards,
Click to expand...
Click to collapse
My little sister had the same problem.
But now the phone is complete dead.
Not booting after bootloop.
No customroms ever installed.
Hey guys
Samsung Galaxy Mini 5570 is a pretty old device now and definitely not worth to talk about, but It's for my aunt and she said i HAVE to fix it otherwise she will kick my butt.
This is the whole story:
Phone was running a very low android version (it was 2.1 or something) that i could barely install apps on it (Just installed WhatsApp), I decided to upgrade it to a higher version so i could install other applications like Line and Telegram for her, so basically i had to flash CWM file first because it was required, I flashed it using this link:
http://www.droidthunder.com/root-install-clockworkmod-cwm-recovery-samsung-galaxy-minipop-gt-s5570/
They said flash the cwm file and factory reset your phone but i flashed the cwm file and rebooted my phone without factory reset, everything was working fine :good: but i decided to follow the instruction so i rebooted into the recovery mode and factory reseted my phone (by my phone i mean her phone, but i'm gonna say my phone instead) and guess what, it never booted up again. stuck on Samsung logo.
But i could go into the download and recovery mode, so basically i followed this instruction:
http://www.droidthunder.com/update-samsung-galaxy-minipop-gt-s5570-android-4-2-1-cyanogenmod-10-1/
which is from the same guy, I flashed it using recovery mode and flashed gapps too, everything went normal without any errors. So i rebooted my phone and ............
a black screen poped up, I was really worried because i couldn't boot my phone, nor could i go into the recovery or download mode. I don't know if i could or not but the only thing I'm getting right now is a black screen or a backlight.
The only thing that seems to be working is when i hold Power+Volume UP button, my laptop can detect my phone (as Samsung CDMA Technologies) but can not flash anything using Odin, it stucks on "setup connection" message. Nothing else is working, I tried:
Home+power+volume down
Home+power+volume down+volume up
Power+volume down
Power+home
etc
I also tried a hundred different ways like completely uninstalling the drivers (with or without kies) pulling battery out, try those key combination while battery is out and reinsert battery while holding them but nothing is working.
I found this article yesterday which is for unbricking the hard bricked phones, but ADB can not detect my phone:
http://www.engineerthink.com/blog/2015/11/how-to-unbrick-hard-bricked-android-phone/
Please help me guys, And do not suggest me to take it in Customer Service because i would if i could.
Thanks in advance
So I have this phone (SM-N920P) that a few days ago just went black in the midst of operation... the power button alone would not turn it back on... eventually the power and volume down did power it back up (if it was ever really even off) but at that point it stuck at the boot screen.
So I have went though what I think is every possible option... but I willing to see if there is anything else..
I have used Odin to load various flavors of stock ROMS (it was stock when it went into this condition so it was locked down before it "died:
no developer tools and FRP lock is on.... I tried some Roms that said they could bypass the FRP lock and allow some custom Rom.. thinking that would help but at this point I am not sure that would even matter considering where I am with this unit, regardless they would not load.. or get past the FRP lock..
there are tons of files out there and some seem to come from questionable repositories.. this is my first foray into android issues.. but no one makes it really easy or "safe" feeling..
Anyway the last thing I tried was loading one of the frp unlock roms which fail and cause the phone to boot to a bad load blue screen... then I unpacked an md5 file and took just the recovery.img out... renamed as tar and loaded that...
At that point the phone does boot past the bad load, but I am right back to just that splash screen.. and no matter what I cannot get it to go to an Android screen to use the recovery.img I believe I just loaded.
I loaded fastboot and adb but at this point they do not see a device.. so something beyond Odin.. or some "special" file may be the only hope? Or it is just shot? seems like it should be able to be fixed though... I have spent like 12 hours trying different things so far.
I did get one ROM to load that showed some android output at the top of the boot screen.. and when I did the normal vol up, power, home.. it did go into another screen.. which looked like Recovery... but it just said turn off auto reboot and the Hard Reset the device...
but I could not do anything but reset the device using vol down and power...
The power alone still never does anything... those are the 2 keys.. power alone does nothing... and I cannot get into the android recovery screen.. any help would be great.. thanks.:good:
Hold the power + home + vol down buttons for 7-10 seconds until screen goes off. Then boot into download mode and flash TWRP which you'll then use to flash a working ROM.
Blocked by FRP Lock
duckynawal said:
Hold the power + home + vol down buttons for 7-10 seconds until screen goes off. Then boot into download mode and flash TWRP which you'll then use to flash a working ROM.
Click to expand...
Click to collapse
I can get to that point... but load fails with the Custom Binary(Recovery) Blocked by FRP Lock.. I tried every version of twrp available..
and since the phone cannot get to anything except the download and boot screen I cannot alter any normal usb debug or OEM setting...
MagicNote said:
I can get to that point... but load fails with the Custom Binary(Recovery) Blocked by FRP Lock.. I tried every version of twrp available..
and since the phone cannot get to anything except the download and boot screen I cannot alter any normal usb debug or OEM setting...
Click to expand...
Click to collapse
Since you can boot into download mode, flash TWRP using Odin, then boot into recovery.
Hope this brings some clarity to your current predicament. Wish I had good news.
I've ran into this problem twice now either using .img to .tar tool that isn't set up properly with an incompatable version of stock rom or a corrupt dump of a stock rom or even using a proper stock rom. Or if you just so happen to accidently turn off O..E.M unlock... and your phone died or you restarted it.... Download mode spits out some red code usually or fails or even can complete but not in any case I've ever seen and boot sucessfully.... usually if you try to many times with odin you'll end up with a blue screen that comes up stating something went wrong during update process and to use Samsung's smart switch program on a pc. Only problem is at this point you've already tripped Knox and your warranty is now void so downloading smart switch and typing in your serial and one I will only give you another error stating that your phone is not comparable with smart switch due to Knox being tripped at 0x1......
At that point there are a couple options claim insurance if you have it, $200 or if you don't have insurance. Samsung will give you a spill about how your 1yr warranty is over and even if it isn't when they get your phone they will see your Knox status of 0x1 and tell you sorry your warranty is void due to end user tampering. So they offer a reflash for a cool $80 without warranty and that will reset your phone back to O.E.M specs with a Knox of 0x0 fix it for a mere $80. Smartswitch won't reflash firmware do to Knox being tripped. Sorry. You are more than welcome to try....
COLOR="red"]NEVER, I REPEAT, NEVER TURN OFF O.E.M. UNLOCK UNDER ANY CIRCUMSTANCES IF YOU HAVE ROOTED YOUR PHONE, OR PUT A CUSTOM KERNEL OR FLASH A CUSTOM RECOVERY OR YOUR FAIL TO BOOT.[/COLOR]If you turned off O.E.M unlocking. Basically O.E.M unlocking is telling your phone it's okay that Knox is tripped. O.E.M unlock allows the skipping verified samsung signature checks on the first rom based bootloade rduring the boot sequence alowing it to bypass into the secondary bootloader and kernel.
O.E.M. stands for "Original Equipment Manafacturer" i.e. being Samsung in this case so when you have not done anything to your phone when it comes brand new out of the package. Developer mode is hidden and unacessable for a reason.... O.E.M unlock means that in download mode you can flash unofficial code, i.e. C.W.M., TWRP, Other unsigned code from various developers. With no hassle due to Samsung being so kind to us developers and allowing us the option to manually unlock our bootloaders.
Usually what happens specifically is Samsung has a secure bootloader which uses digital certificates to ensure that the software loaded before the operating system is trusted to boot the linux kernel shell we all know and love as android OS when you load a custom bootloader such as anything not signed by Samsung it fails to pass the signature checks and that's exactly what turning off O.E.M unlock did.
But with us all being blessed with the option to manually unlock our Bootloaders through O.E.M unlock now so many options are open to us so as but not limited to.: Roms, MODS, Hacks, Busybox, Root, Xposed, Various Root Applications, Magisk, Kingoroot, GeoHots stuff, HashCodes stuff, even have the oppourtunity to create and test various of our own creations.
Once upon a time Bootloaders were locked, meaning, No Roms, No kernels, etc, etc... Very, Very difficult to even root phone's. The reason I go into all of that is Because with great power comes great responsibility. Always back up your eds partition, and always always if you root and like to run custom rom Roms and all the development for this scene that only continues to grow and evolve Make sure you do one thing if nothing else and that is to read, read, read and know your phone inside and out. I am a developer and I work with software as much as I do hardware. I can afford to make mistakes as these aren't my daily drivers. I suggest if you like to unlock the full potential of your devices then please heed my warning about reading and knowing all the dos and dont's for what your devices is capable of and what will turn it into a very expensive paper weight. I'm not being a **** I'm trying to help. Because you have now tripped your Knox counter meaning it is permanently stuck in the state of your phone now having a void warranty and there is no going back.
Once you turn O.E.M mode off you lock your bootloader and if you've already tripped Knox you can't flash a stock bootloader or Rom because your phone's hardware is preventing anything unauthorized from making it past the kernel checks..... clear some things up for You? I don't care the people say they have work around forCOLOR="red"]"custom binary frp lock"[/COLOR]because I have yet to see a phone recover. P.S. word to the wise that is one error you never, and I mean never want to see on your boot screen...
I came back from it once with a zeroed out serial number and a null one I. Once and that's a whole nother ball of wax. Claim warranty, play stupid if still covered if not Sammy will know so just shell out the $80 send it to them. They will reflash it and that's the end of that.
P.S. MODS, Why can't I just indent the first letter or word of my paragraphs? It's really bothering me. I tried for like 20 minutes. Everything from highlighting my whole paragraph, to highlighting the first word or letter. Even went as far as editing the hypertext php to no avail...COLOR="red"]What Am I Doing Wrong?[/COLOR]
---------- Post added at 03:11 AM ---------- Previous post was at 02:29 AM ----------
[/COLOR]
MagicNote said:
So I have this phone (SM-N920P) that a few days ago just went black in the midst of operation... the power button alone would not turn it back on... eventually the power and volume down did power it back up (if it was ever really even off) but at that point it stuck at the boot screen.
So I have went though what I think is every possible option... but I willing to see if there is anything else..
I have used Odin to load various flavors of stock ROMS (it was stock when it went into this condition so it was locked down before it "died:
no developer tools and FRP lock is on.... I tried some Roms that said they could bypass the FRP lock and allow some custom Rom.. thinking that would help but at this point I am not sure that would even matter considering where I am with this unit, regardless they would not load.. or get past the FRP lock..
there are tons of files out there and some seem to come from questionable repositories.. this is my first foray into android issues.. but no one makes it really easy or "safe" feeling..
Anyway the last thing I tried was loading one of the frp unlock roms which fail and cause the phone to boot to a bad load blue screen... then I unpacked an md5 file and took just the recovery.img out... renamed as tar and loaded that...
At that point the phone does boot past the bad load, but I am right back to just that splash screen.. and no matter what I cannot get it to go to an Android screen to use the recovery.img I believe I just loaded.
I loaded fastboot and adb but at this point they do not see a device.. so something beyond Odin.. or some "special" file may be the only hope? Or it is just shot? seems like it should be able to be fixed though... I have spent like 12 hours trying different things so far.
I did get one ROM to load that showed some android output at the top of the boot screen.. and when I did the normal vol up, power, home.. it did go into another screen.. which looked like Recovery... but it just said turn off auto reboot and the Hard Reset the device...
but I could not do anything but reset the device using vol down and power...
The power alone still never does anything... those are the 2 keys.. power alone does nothing... and I cannot get into the android recovery screen.. any help would be great.. thanks.:good:
Click to expand...
Click to collapse
Hi,
So I had a Problem that my huawei (Working Phone) soft bricked himself over night. It was on his charger over night and worked fine on this evening... on the next morning I want to check my calender and the phone was already on the huawei logo... I think ok it does a reboot and locked himself. Than I forced off the device with power + volume up. Reboot instant after that and still stucked so ok I am soft bricked now. After searching a bit on Google it sad delete your cache via recovery. Problem I can't enter recovery or eRecovery only fastboot is available. Going into fastboot try the hisuit from huawei with the result phone not supported. But after that try on the white fastboot screen stand's "entering recovery mode..." so i let it do his thing... After many hours I came back and there it was the emui recovery. I decided to only clear the cache and boot. Again soft lock on logo... After that I tried again fastboot -> hisuit that doesn't work that the phone says entering recovery mode... -> but nothing happened...
I came back after the next work day...
The screen was black and I can't boot it anymore (still lie on my desk since first soft brick so yeah I am 100% proof the display will work) I plugged it in in my pc and it says now USB SER typical driver not found error code from windows...
IT will react when I force it with power + volume up only with dc from pc and reconnect in USB SER
Anyone any ideas to fix this hard brick?
Model: SNE-LX1
FRP and Phone locked
Stock Rom on it !
And If it possible I will let it as stock as possible (as I said it's only a work phone!)
Thanks for all the help !
@Blade8895
F
Huawei phones just aren't what they used to be... Some time ago their unlock policy vanished into thin air, then came alligations of spying, a trade ban in the US, and I've even heard rumors about them trying to make phones brick themselves after installing custom software. ?
Sadly, I can only recommend to stay clear of their devices until this whole situation improves...
I actually have the same issue, my phone downloaded the latest update and I scheduled it to auto update at midnight,next morning when I woke up,was surprised coz my regular alarm (from phone) didnt woke me up,so I grab my phone and saw it was dead,but it was full charge, then it didnt open anymore,and I tried to do all the reset or hard recovery technics on the net but it still is bricked. If I plug it on a computer it only says usb ser.. I guess its how the company makes money by destroying their own system,so you'd buy a new one,coz you cant access your data or all your files from the old one,so you would buy a new huawei again,to retrieve your files.
USB SER is testpoint mode. Idk how, but you have closed the service mode contacts. In general, this is solvable, in the service it should not cost a lot of money.