I recently bought an Elephone S7 3GB model.
After charging, I flashed a stock 3GB rom onto the device.
Now it is completely bricked.
SP Flash tool will show the "Downloading DA" until 100%, then hang there for a long time, and then throw a semi-random error message. Generally it's never the same error twice in a row. Most of the errors are just random negative numbers. Sometimes it will do something outlandish like claim that the phone uses NOR instead of EMMC flash (which makes no sense at all).
Any idea what I can do to fix this?
any luck, got the same issue
Related
I messed up with my LG G2 D802 and i need help because i believe it's a software problem.
When i was installing the latest cm12.1 nightly, after trying a few other roms, i also installed, by mistake, an old jb bootloader/bootstack.
As result the phone entered in Bootloop, but not a normal bootloop, on the screen start appearing some crazy interferences and then the phone boot up, but the screen not. The phone made sounds and the touchscreen work, but the screen was black/off.
I've managed to solve the problem with an unbrick method, but now i have a huge problem: the screen, on the rigth side, from the top to the botton has 6/7 black lines. I have no idea how to solve this and if is a hardware problem ... I've read it's an kernel problem, not hardware, but don't know how to solve the problem :/
Picture:
https://meocloud.pt/link/58d13900-ffa8-4114-8957-8c4b973bad1a/IMG_20150916_020454.jpg/
I feel your pain
Hi mate
Same thing happened to me.
Background info: I had successfully upgraded to CM12.1 , was running fine for a few days then I wanted to update my TWRP, updated the recovery and just went to check that I had OTG cable support then boom, boot loop.
It didnt just loop it just loaded loaded loaded, then the screen made some funny sounds. and then shut down. I hard reset to recovery and reinstalled CM12.1 and was able to successfully exit the loop. but damage to screen had occurred in the exact same place, and method right side of the screen.
Tried rinstalling original jellybean software from my backup. no success, and also flashing other versions of CM12.1 nothing.
After some research I saw that this is a manufacturing fault and that this occured quite often. it appears that the best solution is to buy a new screen as it is the actual hardware that is damaged in the screen digitizer. I might be wrong, and I pray that I am because I want to fix it too. in the end I just bought a new note 4 (not note 5 as i wanted SDcard storage). Phone was 2 years old and a new screen costs a fortune. But i miss my little G2 and its super fast speed and simpleness. :crying::crying:
If someone else has the solution to this problem on the forum we are all ears.
Hello,
my Galaxy S4 got soft bricked recently and I am looking for a solution for 5 days now and now I decided to ask you guys for help since I can't find anyone with the same problem.
I had Albe95 LolliROM 9.0 (15/05/16) [HPA1] flashed on my phone for about 3 weeks and everything was perfect.
I was using my phone when it suddenly restarted itself and it got stuck in a bootloop (SAMSUNG animation). After many attempts I could boot into recovery (TWRP) but it would freeze there and I had to remove the battery...
I could also boot into Download Mode so I decided to flash a stock rom (I9505XXUHOJ2_I9505OXAHOJ2_I9505XXUHOJ2_HOME.tar) which I downloaded from Sammobile. Odin would always stuck at system.img.ext4 but again after many attempts it workted and I had success. When it was booting my phone froze at "optimizing apps". So I had to turn it off and restart again, but this time the phone was always freezing at the first samsung logo and wouldn't go further.
I can still go into Download mode but can't flash anything because eather Odin fails (complete(write) operation failed) or my phone freezes. Sometimes when I boot my phone into Download Mode the screen would do strange things like flickering and weird colors would show in DL Mode.
So my problem:
- booting into Download mode after works though it freezes sometimes
- can't flash roms because phone is freezing all the time
The model # in download mode is 9505? Was the phone ever dropped? You're using the original Samsung USB cable to flash?
audit13 said:
The model # in download mode is 9505? Was the phone ever dropped? You're using the original Samsung USB cable to flash?
Click to expand...
Click to collapse
Thanks for the reply.
-yes modelnr is 9505.
-i have not dropped my phone recently. I mean its over 3 years old so of course I've dropped it but never really bad and it has no scratches or anything.
-I've tried different cables and samsung cable was one of them.
I also tried all ports of my laptop even tried another pc
Maybe flash the stock rom with a pit file?
audit13 said:
Maybe flash the stock rom with a pit file?
Click to expand...
Click to collapse
I didn't try this pit file thing because I don't understand the meaning of it exactly..
But after many many Odin flash attempts I got a success with a stock rom 5.0.1.
I think I figured out what the problem is but I can't really tell why it's happening (Hardware broken maybe, but which one?)
So after the flashing the stock rom successfully the phone restarted and started the first boot but it froze during the samsung animation again...
I thought maybe if I try a lot of times eventually it will work, so I tried and tried and it always got stuck at samsung animation. (before every boot I had to remove the battery and wait ca 10 sec because otherwise the phone would not start booting at all)
I did not come further than the samsung animation so I removed the battery and placed the phone (I almost gave up).
But after one hour I tried again and this time it passed the samsung animation and got to the Optimization part of the apps. aaaaand it froze there again.
I thought maybe if I wait again for 1 hour I can pass the optimization part. So I did and it really worked. I got to the startscreen.
So the current problem is:
- The phone boots and makes it to the homescreen and freezes after ca 10 seconds. And also I have to wait for about half an hour or one hour to get that far. If I try again right after the freezing I can't get passed the Samsung logo.
What could cause this freezing? Maybe the cpu has to "cool down" in the one hour of waiting and freezes because it gets to hot? I really don't know what it could be.
Something on the motherboard, likely either CPU, EMMC chip, or GPU, is failing. Why or how I don't know, but I'd have a tech look at it.
Hello,
I suddenly started to have big problems with my Note4.
Everything went fine for about a half year (I bought the device from ebay).
Then, suddenly without reason, the phone rebooted.
Each day I got more and more reboots (it starts with freezings and then turns off), and eventually the device rebooted every 5-10 minutes.
From time to time, I got the message "kernel panic!" with "emmc read fail".
So I tried my best with google, nearly everyone said that the emmc flash is corrupted and has to be fixed by Samsung - but because my decive has knox 0x1 triggered, this is no option for me.
I already flashed the Stock Rom again with Odin, after a full wipe of everything.
This didnt change the problem.
So I've read about PIT files and repartitioning, and flashed the PIT file for my SM 910F DBT. The reboots cycles changed from every 5-10 minutes to every 30-60 minutes, sometimes everything was fine for some hours, but there still were these suddenly reboots, and everytime I had to remove the battery to got android booting up again.
I cant remove the battery so many times a day, I thought, so I searched for another solution again - thinking of something like checkdisk, to find the corrupted flash cells and maybe exclude them from use, so they couldnt crash the phone.
I found a description with android adb and "fsck" and thought that this may fix my problem - I tried and it failed, because I needed to root my phone again (maybe).
This is why i flashed twrp again. My phone booted in the new, custom recovery automatically. I wanted to put the zip file for superSU and the file for the custom Kernel (think I need that for root?) on my internal SD, so I wanted to shut down and boot normally - TWRP said "heey you dont have root, should we root your phone now? swipe for yes!" or something like that, so I did as they said.
From now on, I werent able to boot into normal android again. Neither into the recovery mode, the screen just stays black.
I can still boot into download mode - but everytime when I try to flash something with odin, odin starts and after a few minutes, he gives a red line : "flash write failure".
I'm totally upset and dont know what to do anymore. Is my note4 dead now, forever?
If you have any suggestions, please write something. I will be very thankfull, I need my phone very badly :/
Edit:
If I try to boot normalley, I got the message "Firmware upgrade encountered an issue. Please select recovery mode in Keis & try again."
Kies troubleshooting says that it doesnt support my device..
Chocsy
no idea, everyone? still stuck
Look at http://forum.xda-developers.com/note-4/help/note-4-freezing-restarting-t3348821 , installing wake lock worked for me
Update 2018: emmc chip died later.... Needing wakelock is an indication emmc is going south appearantly
Hi
I am stuck with Pulsing blue LED and the "Powered by Android" screen,
have access to both the recovery and the download Mode,
I also have Odin (version 3.13) on my computer along with TWRP (3.1.1 trlte and 3.2.1 version)
My device is a Samsung Galaxy Note 4 N910F bought in shop, no special carrier. It was bought in the Netherlands.
I have tried everything that I have read. The furthest that I can go is the Second Samsung Logo with the Flashing Light
Whenever I try to Flash the stock Firmware for my N910F, everything goes well in Odin but then when the phone reboots, it (sometimes) install the system update until 30% then shows erasing then either crashes right there and then or load the system update bar, completes it then shuts down.
I have tried multiple firmwares, even recovery firmwares. All the same problem. I can see the firmware is flashed, because when I enter recovery mode after I flashed a different ROM, it shows the version I flashed.
I cannot seem to install TWRP because it was never rooted.
Whatever I do, at some point, my phone either gets stuck in a bootloop, freezes with the LED light or shuts down.
And I have also proceeded to use different batteries.
Do you have any options?
Thank you
Heat????
I'm far from an expert here, but I've just experienced a similar problem where my N910F started boot looping / freezing within 15s to 2 min after unlocking. Unfortunately my micro Sd (SanDisk 256GB) was corrupted a week ago, so before doing anything else I did some research (XDA/YouTube) and probably found pretty much what you've found. I frequently change batteries so I could discount that as an issue. Someone suggested using the Samsung Smart switch here https://www.samsung.com/uk/getting-started/smart-switch/, but I haven't used it (yet) so I can't tell. I presume you had the latest firmware from Sams https://www.sammobile.com/firmwares/galaxy-note4/SM-N910F/.
My issue was that I needed to recover data, docs, photos, phone numbers etc. When boot looping the note 4 got very hot . In particular around and to the left of the camera (looking at the rear). Thinking it could possibly be the dreaded eMMC problem which also manifests itself by creating heat, I thought cooling the device might help. I placed the Note on a cooler box freezing block and voilà! No boot loop. I was able to remove all, but necessary apps and do a full copy to my PC. Storage was reduced from around 90% to 50% and memory 80% to 60%. It's now been stable for 12 hours, but the jury is still out. Next will be full reset with he latest available firmware 6.0.1 as mine was still on 5.1.1.
Good luck and hope this may be of some help.
I've got this problem, too, when using the unofficial Lineage 15.1 rom. SIM death and boot loop. After flashing the latest stock rom through odin, it passed but the screen was black and no system was installed. The blue notification light was constantly stuttering, though. And I couldn't even go to recovery!
When flashing, a 910F can get hot - use a cool temperature room and/or a fan blowing onto the device.
If it's not too late...
I am having a big problem with A2017G. What happened is since the battery was ready for replacement, I took it to a service shop and the man did it in front of me, opened the phone, replaced the battery and put it back together. However, when we turned it on, it went to bootloop showing only ZTE logo and that is it. He told me that he can't help with that. So, I used the Axon 7 Tool to flash Full EDL and it was successful, but the phone works like it is severely down-clocked, it is so slow you can see where you touched the screen, and it takes 3-4 seconds for it to respond to a touch. I tried at least 7-8 different full EDL ROMs (MM, N, O) always with same result. I unlocked bootloader and installed TWRP (last version available for Axon 7) but never managed to boot into any custom ROM (flashing goes fine, but no boot). Does anyone have any ideas or suggestions, or is it probably hardware problem? Any help is appreciated !