Dear users, some time ago during some web searching, my device screen has turned off and phone gets froze. Then I forced it to reboot but it finished with bootloop. When I boot device in twrp it looks like it doesn't have an internal memory I tried almost everything to flash anything, repair, erase, format etc.. (fastboot/adb/windroid/spflashtool/flashtool/mitool) always gets the same response: "flash write failure" or "failed to write partition". Is there any other software method to resolve this issue or I have no other way than send device to professional service to replace damaged component(s)?
Related
I got my phone less than a year ago. Ran the 1 click root thing worked flawlessly since then and about a week ago my phone just decided to not work. All the applications i would open would force close and you couldn't do anything. So i turned it off and when i turned it on i got my problem.
The phone boots into the "S" and then it hangs at the loading screen until i pull the battery out.
I google searched a few times and i determined it was an SD card failure. The guide i followed told me to go into the 3 button combo thing and when i go to do a factory reset it gives me this "E:Can't mount /dev/block/mmblkOp1 (I/O error)
E:Can;t mount SDCARD:update.zip"
It's still on stock firmware, froyo i think?
Any help please?
Myhm... sometime happens.
It may be some issue.. try to flash clocworkmod 2.5.1.8.. if you are on Froyo, it may help. another solution may be (and I'd try it first) to apply Click
Hi everybody.
TL;DR
Recovery hangs upon booting and fastboot mode doesn't show up ADB interface on my PC. How to flash the phone?
Long version:
I wonder if you can help me. My old faithful Note 3 is badly misbehaving. Yesterday I filled almost all its internal memory with some movies before heading out on a trip, but some time later when I reset the phone after unusually long boot all user settings were lost. Well, something went wrong, couple of hours later there was reset after reset so I wanted to restore previous backup... but couldn't. TWRP was showing error messages (TAR something something, 255) very shortly into restoring process. It couldn't restore backup but also couldn't make new one as well (similar error with TAR and code 255 when trying to backup user data).
Something was very wrong, so I thought maybe I will flash newer TWRP 3.0 and give it a try but suddenly after next reset I couldn't even get into recovery anymore - TWRP gives me black screen after several seconds into booting it. No icons, no reaction to key presses, nothing. Even holding power button does nothing.
Ooooookay, it's time to enter fastboot mode then and flash new recovery manually. So I enter it, connect phone to my laptop and... nothing! No ADB interface. Some kind of samsung driver is installing, but the most important one, for ADB, just doesn't show up. It's really weird. Reinstalling drivers doesn't help, only the same one device that shows up gets different names, but that's it - no ADB interface, and, effectively, I can't flash anything because fastbot and ADB can't see any device. Odin can't see the phone too.
What's going on? Is the internal flash dying or what? But if so what does it have to do with ADB not showing up? Do you have any ideas that I can try out in this situation? I checked my laptop with a tablet that I have on hand and it shows up its ADB interface without problem in fastboot mode even though it's the first time I connect it to this laptop, so laptop and it's system are fine.
If nothing helps then, well, One+ 3, here I come.
EDIT: Problem solved. Turns out f2fs on data partition crashed and therefore TWRP couldn't start at all. I managed to flash Philz CWM via Odin somehow (after messing with drivers for some more time) which told me there is something wrong with /data because it couldn't mount it at all. It couldn't format it either. Fortunately SlimLP managed to start and after throwing up some errors I managed to do factory reset which formatted the internal memory back to ext4. Then flashing TWRP, formatting data back to f2fs, restoring backup and voila! It works again. Good, I'll wait until Note 8 if there ever will be one.
Hi,
two weeks ago, my Storm received an OTA update with Android 7, moving away from CyanogenOS to something with a Wileyfox label. The phone continued to work for two days, and then simply stopped dead in its tracks. Rebooting brought me to the point where I could enter the unlock PIN, but immediately after my home screen is displayed, the device stops dead and eventually reboots after a few minutes. Lather, rinse, repeat.
I opened a ticket with Wileyfox support ten days ago, and have never heard back from them other than the automated message that a ticket was opened. So i need to help myself. To make things worse, I haven't done a backup in months. The bootloader also is still the default one from Wileyfox, as I was unable to unlock the boot loader to install TWRP when I got the device a year ago and never bothered again. Therefore the prioriy is to get the device into a state that allows me to back up my data before doing a factory reset (and probably moving on to lineage OS in the process).
I can get the device into the bootloader (kipper-N-g2253387) and into an "Android Recovery Wileyfox/Storm/kipper 7.1.1/N6F27C/83dbe1d738", and the device seems to be fine in this state. So I reckon that the hardware seems generally fine and that I have a software problem.
As I haven't been able to find the original factory image on the Wileyfox site and my question has stayed unanswered, I did some research and found a file named kipper-7.1-TOS125B (fastboot).zip on the network. When I unpack this, it looks like an Android image. Flashing from an SD card didn't work ("Failed to mount /sdcard: No such file or directory"). adb sideload makes the device spew a few messages including "E: footer is wrong".
So I tried fastboot erase system, fastboot flash system system.img, which did something that took the appropriate time to flash the device, but the behavior didn't change: Bootup until the lock screen, displaying the home screen after entering the PIN, and then dead, eventually a reboot.
I did not try anything more radical since I'd really really like to save my data first. Is there any way to do so?
Please advise, thanks in advance.
Greetings
Marc
have you notice about this problem?
I saved my data with TWRP booted to RAM and then upgraded to LineageOS. That solved the issue for me.
Zugschlus said:
I saved my data with TWRP booted to RAM and then upgraded to LineageOS. That solved the issue for me.
Click to expand...
Click to collapse
Sure, i do the same but lineage have more problem or no feature...like
BT problems in whatsapp audio recording and bt disconnect when using second sim
Haven't switch for turn on/off single sim ( important for me because second sim is only for work )
Battery drain, with lineage my battery dead at middle afternoon ( using 2 sim, bt, data connection ON, Moderate use ).
Sometimes reboot....
Actually with wileyfox os 7.1.1 have no problem but no root and no twrp
Inviato dal mio Wileyfox Storm utilizzando Tapatalk
Hey all.
I've created a problem with my S8, don't know what to do from here.
Simply put, i had the encryption before booting on, always worked fine. I also clear the phones cache once a year.
I went into recovery, and cleared the cache partition, then on reboot it just keeps rebooting, shows the S8 screen, goes black, buzzes twice and repeats.
I've tried factory resetting in recovery, which worked, but still bootlooping. (At the bottom of the Recovery Menu, i also see the message: dm-verity verification failed)
I called Samsung about the issue, they told me to take it to the nearest authorized repair facility, which i did and they said it would be hardware without even diagnosing it. So i took it back home, and tried a few things myself, i loaded up Odin, with the exact firmware version i am on, and it will unpack it all, but always fail. Odin sees the phone fine, and download mode works. Ill provide a picture of it for reference below.
tl;dr cleared cache, sent it into bootloop, tried repair shop and flashing with odin, no avail.
Not looking to void warranty or trip anything also. It is out of its one year warranty period of course, but i've had Samsung honour a S7edge screen and battery at about 1.8 year out of warranty.
Whats my best option? Is the encryption lock preventing Odin from flashing? I have the code, as it is my phone, wondering if there is another way to enter it as the prompt won't come up due to the bootloop
Nortonic said:
Hey all.
I've created a problem with my S8, don't know what to do from here.
Simply put, i had the encryption before booting on, always worked fine. I also clear the phones cache once a year.
I went into recovery, and cleared the cache partition, then on reboot it just keeps rebooting, shows the S8 screen, goes black, buzzes twice and repeats.
I've tried factory resetting in recovery, which worked, but still bootlooping. (At the bottom of the Recovery Menu, i also see the message: dm-verity verification failed)
I called Samsung about the issue, they told me to take it to the nearest authorized repair facility, which i did and they said it would be hardware without even diagnosing it. So i took it back home, and tried a few things myself, i loaded up Odin, with the exact firmware version i am on, and it will unpack it all, but always fail. Odin sees the phone fine, and download mode works. Ill provide a picture of it for reference below.
tl;dr cleared cache, sent it into bootloop, tried repair shop and flashing with odin, no avail.
Not looking to void warranty or trip anything also. It is out of its one year warranty period of course, but i've had Samsung honour a S7edge screen and battery at about 1.8 year out of warranty.
Whats my best option? Is the encryption lock preventing Odin from flashing? I have the code, as it is my phone, wondering if there is another way to enter it as the prompt won't come up due to the bootloop
Click to expand...
Click to collapse
Whats the error displayed in odin mode
kpwnApps said:
Whats the error displayed in odin mode
Click to expand...
Click to collapse
No error other than saying (Successful: 0 / Failed: 1)
Nortonic said:
No error other than saying (Successful: 0 / Failed: 1)
Click to expand...
Click to collapse
Try different cable. Sometimes its cable fault
kpwnApps said:
Try different cable. Sometimes its cable fault
Click to expand...
Click to collapse
Tried 5 different cables, OEM, and off-brand.
I've contacted samsung again.
Hi, I have a Samsung Galaxy A52s 5G that goes into the following loop for two days:
boots up, waits for me to unlock the phone through the draw pattern, I unlock the phone, "Phone Starting" pops up, phone starts, I am able to navigate the phone and phone apps for something like 20 seconds and then it freezes.
Model Number: SM-A528B/DS
The firmware shown in recovery mode is the following: A528BXXS1CVI6
Why I am trying all this
This is my wife's phone. I thought she was backing up photos through google photos and she told me that she was doing it. Unfortunately, she was only uploading them on the local app and the backup was not working since her storage was full for several months. So, if there is a way to access her stuff from any Operating System please let me know. The problem, I think, is that I can't without unlocking the phone (of course).
Note
If I don't unlock the phone, the phone does not freeze but of course, I cannot do anything. Therefore, I suspect it is some thread that starts by default as soon as the phone is unlocked.
What I tried
I tried the following things:
Remove the SD/SIM card tray (just because it was easy)
I tried to boot my phone in Safe mode. I correctly entered in safe mode, the third-party apps were disabled but then the phone froze again.
I connected the phone to a laptop (running Ubuntu 22.04) and entered in recovery mode. Once in recovery mode, I tried basically all the options without any luck so far:
Reboot system now
Reboot to bootloader
Apply update from ADB:
I tried to download a firmware for my phone and then send it through ADB with the following command
`$ ./adb sideload ~/Downloads/A525FXXS4CVK4_A525FOXM4CVJB_HUI.zip`
and I got stuck at
`serving: '/PATH_TO/Downloads/A525FXXS4CVK4_A525FOXM4CVJB_HUI.zip' (~0%)" `
I don't know why
I did not try "Apply update from SD Card" yet
I did not try "Wipe data/factory reset" yet
I tried "Mount /system" but it got me the following error:"Error updating for slotselect"
I tried "Repair apps"
I tried "Run Graphics test"
I tried "Run Locale test"
I tried and then did "./adb reboot recovery" to test that I was able to reboot through adb and it did reboot the phone indeed.
Let me know if you have any ideas on what to try next.
Having a similar issue right here, please notify me what you did afterwards and if you managed to solve it
I am in the same situation and same try outs. Only one slight different. Phone does not start at all. Only "SAMSUNG" and "powered by android" logos. Then starts to bootloop again.
Did you find a solution?
@minidiable did you try to flash with Odin? You should have a try using CSC that avoid erasing data.
In any case, I'm coming back here to give my result after several try-outs and finally going to a Samsung Center.
My phone, entering in recovery mode, had from the begining a message at the bottom saying " E:[libfs_mgr]Error updating for slotselect ".
At Samsung Service Center they told me that this error may probably warn about motherboard failure. And after tearing down the phone and checked it, they changed the moterhboard. Sadly, All data lost. That's all.