Hi guys,
Hope someone can give me some light about diagnosing flash memo device hardware damage.
I have an OnePlus 6 A6003 that entered for sudden in CrashDump Mode. It stopped to run the OS, although the bootloader mode still worked.
Guided by some tutorials I tried to unlock trough fastboot and adb in CMD panel without success in unlocking the device.
After that, I started trying Msm Downloading tool to flash a Oxygen firmware and make it brand new. I couldn't.
The process stopped somehow in the middle of downloading to system_a. I lost hope big time here and went to SMT flashing. The tutorial advised that i could lose IMEI if i did not backed up my EFS. I didn't, but i figured i could use some downloaded backup and change my IMEI back to original, as I have the original box and data of the phone. I did it and the process of flashing the device stopped the same spot it did before.
From there I repeated the process in loop until finally I got it done. Once the original oxygen firmware was succefully flashed I was happy, till i discovered the phone still doesn't turn on. it always blurs the initial logo screen after some seconds and freezes.
At this point I think there is some hardware problem at the flashdrive device. Anyone have any idea if this still can be a software problem or can assure me how i could definitly diagnose it?
I 'd be thankful with any help.
Related
Hi all new here,
Just got my OnePlus One and updated to cyanaogen 12, while simply using the phone it crashed forcing me to reboot the device, after this the phone would not turn on (asssuming it was hard bricked), luckily following some guides on this forum I was able to get it back up and running again.
I reflashed 12 after and exactly the same thing has happened this time, unfortunately I am unable to unbrick it using the ColorOS method like before, the phone just remains dead and I cannot get it into fast boot mode to rectify the problem.
I am out of luck already? OnePlus seem absolutely useless over support and just plain rude.
EDIT:
I am now able to get into fastboot, but still cannot see it on screen, but fastboot is appearing in device manager as windows ADB, what can I do from here?
Let me start by addressing I know this isn't the sprint thread but there's a lot more development here which equals more help. Plus this issue seems to be able to happen to any variant.
Second, this isn't my device I'm trying to see if it can be fixed for a friend. I'm not that familiar with Samsung devices but I have been able to get them working in the past via Odin or kies but this time I need some help.
So this is what's going on, my friend recently rooted his S6(SM-920P) not sure which method he used (don't think it matters at this stage) and was on stock rom (LP5.0.2) with xposed framework installed. He hadn't changed the kernel AFAIK oh but I did install TWRP for him and everything was working. Long story short he woke up a couple days ago to his phone being unable to turn back on. I told him how to get to download mode and I asked him what did it say on the top left corner it said something like "system binary not SEandroid locked" underneath that it said fac lock
So I had him give me the phone thinking somehow it did a OTA update while he was asleep or something either way I was confident using Odin to flash the firmware would solve the issue. Had the firmware finished flashing I'm confident it would have but halfway through Odin simply froze on installing system. I figured its just gonna take a while 45 mins later it was still stuck at the same spot.
Not really thinking about it I figured I will just reboot the phone back into download mode restart the process it should be fine. Not a good idea. Now all I get is a green screen saying to access the smart switch emergency recovery system. But it gets better.
My computer isn't recognizing the device now. I installed smart switch software and it's not recognizing it. I even installed Kies and it's not recognizing either.
Is his phone toast or what? I tried emergency system recovery but I need the S/N of his phone to possibly get this thing working again, but it boot into anything anymore except the screen that says Samsung switch...
PLEASE HELP ME if it's bricked it's bricked I get that but if there's a way to figure out what to do I'm all ears. Thanks in advance
Hello there. I own a Z3 model D6603. It is unlocked bootloader and Before it had got the bootloop i had Lineage OS 16 custom rom installed on it (Android 9). I was watching some videos on chrome and then the phone heated a little and then restarted. I thouhgt it was maybe some sort of instability but then it started just bootlooping.
Current Status right now is :
Once connected to pc goes to flash mode.
I can get it to fastboot.
When connected to charger just goes into endless bootloop where only SONY logo appears and then quickly restarts
In attempt to fix it I flashed stock FTF using multiple versions of Flashtool which was fruitless. I also Tried with EMMA but nothing helped still. And then after looking I think it might be damaged TA and I've seen so many say that if that's the case then the phone is bricked forever unless you have had a backup from a previous working state which I actually do. The problem is that I don't know how to flash this TA back since the phone doesn't boot to restore it through ADB. I saw that S1tool works with older devices and doesn't work with Z3 models so I wonder if there is a way to fix this. Thank you for your time.
PS : My power button doesn't work I used to use fastboot to boot it when necessary
Issues of that kind may be a hint for a dead battery, this should be ruled out first. Note: In that case your phone might not boot even if connected to a charger!
After that is ruled out, one should try to install LineageOS 16 or later following the official installation routine from scratch.
Hey everyone,
Up until recently, I've had no issues with my Zenfone 6. However last night the camera started acting up when I was trying to take a picture and the app suggested I restart my device inorder to rectify the problem. I followed the prompt and ever since last night my phone has been stuck in a boot loop. I have stock everything on this phone, I have experimented with roms and kernels in the past but didn't feel the need on this phone. I followed deadman96385 guide on how to unbrick your Zenfone but still have the same problem. I can't enter my recovery instead it just kicks me back to the boot screen. Unforchuntly, it is not unlocked so I have no way to flash twrp and install a fresh version of Android. I contacted Asus and their support suggested I find a local technician but I'm hoping git won't have to come to that. Any help would be greatly appreciated!
Hi,
My oneplus 6 appears to have either died or bricked itself during the night, I got the qualcomm crash dump mode screen on my device when I woke up this morning. My device isn't Rooted or flashed. I have since discovering this this morning I have been panic trying to sort out a solution I have tried MSM that gets to the download complete status. I remove the cable the device displays a splash screen and the screen stays black. Going into fast boot the bootloader and baseband are blank. Hoping someone would have a solution.
Thanks in advance.
I have the exact same issue, I've tried multiple MSM tools without any luck. Sometimes I can reach Fastboot mode, but most of the time it seems to be stuck in EDL mode. My phone was unrooted and stock.
Yep, happened for me too.. Still figuring out to fix this issue.