Hey, writing for a friend of mine with that device having a problem to start from scatch. Initially a problem with titanium backup restore, he then tried to restore a twrp backup and now he did want to flash via fastboot. But as soon as you do anything in miflash the device simply turns off.
I did recognize in twrp that internal storage is gone (ni data/media folder, also several other root folders are gone).
Any tipp what to do now?
(Edit after formating data the 3rd time Internal storage is back again. Trying to restore the backup 'data' halts with error 255, and after restart tough system restore was successfull twrp reports unable to find system. Still not booting and fastboot shuts diwn, though now with msg "press any key to shutdown")
Edit2 partly solved. After additional tries it woul restore more and more, could boot into system, but no data restore, and then data too. So the system is working again, but the problem with miflash resides which might be needed some time.
The problem is that you're trying to access fastboot from a USB 3 port. You must use a 2.0 or lower port (it is a limitation of the fastboot interface itself). Good luck
Related
Hello.
My Samsung Galaxy S I9000, which runs on the GamerzRom (can't specify the version, sorry for that) doesn't want to turn on properly anymore - it just stays on the blinking "X" screen, so I guess it has problems with running the system. Normally, I'd just wipe data and cache and reinstall the whole system, but now I have some important files on my phone and I can't lose them. I'd like to backup my files and reinstall the system, but I don't know how to do the proper backup (it would be easier if I was able to do it when the phone loads system properly, but it doesn't).
How to backup these things? For example, notes are important and I need to have them when I reinstall my system.
I can only run the phone on the ClockWorkMod or Download mode.
You can make a backup with CWM and later pull out files from the backup with 7-zip.
If you don't know; you can mount USB mass storage with CWM (Mount and storage = > Mount USB storage).
rooted, stock lollipop 5.0.2, problem started out of nowhere this afternoon...
camera won't let me take photos as it asks for an SD card. even after i insert an SD card, the error persists.
opening quickpic gives me the following errors...
Code:
not an error (code 0) could not open the database in read / write mode
Code:
unable to open database file (code 14)
can't delete ANY files manually in ES file explorer even with root explorer enabled.
booted into TWRP and cleared cache and dalvik to no avail.
seems like the phone can't read or write any data, except installing/uninstalling apps via google play still works. seems to be the same problem addressed in this thread http://forum.xda-developers.com/galaxy-s2/help/read-write-errors-advice-solved-t2323801 although i don't know how to identify the corrupt file(s) and delete them or fix permissions...
help!!
...bump?
basically wen that happens is because a file or folder is corrupted, it maybe in any place on your phone really difficult to find. That usually happens after you flash some (app, script), restore a TWRP backup, or a app that have root access doing the wrong thing.
i had this problem two times.
In the 1°, i fix by going in the TWRP, and erased my internal memory, after reboot all good.
this case was very simple i copy every file to pc, erase, after restore the one i need, and everything was fine...
In the 2°, i try that and was not successful, i need to re install the stock rom via fastboot from xml rom file to completed clean my OS.
In both cases, i was not able to make a Titaniumbackup, so i lost some data of a fill apps in the second (because i make a backup every week, if i didn't have it i probably lost everything).
If you don't use titanium, and don't wanna to loose things and app files etc, you can try copy everything on internal and external memory, by plugin on the device to a PC, after a TWRP backup of yours data, after wipe, dalvik cache, data, internal storage, cache, system, re flash the same rom you are now, and after test and see if you can write, restore the data backup.
But that data may corrupted your phone again, because the problem maybe in that.
So if after restore the data all goes bad, redo everything and do not restore data, you will lose app and data, but app can be reinstated.
:good:
baybutcher27 said:
basically wen that happens is because a file or folder is corrupted, it maybe in any place on your phone really difficult to find. That usually happens after you flash some (app, script), restore a TWRP backup, or a app that have root access doing the wrong thing.
Click to expand...
Click to collapse
thank you, i used this as an opportunity to wipe and flash cyanogen. so far so good (seems much smoother too).
Hello and greetings from germany,
I have a problem with my Moto G 2014 XT1068. I'm coming from rooted stock KitKat (Xposed) with open bootloader and TWRP 2.8.6.0. Everything seemed fine until yesterday, when the phone just went off (0% battery) and stayed at boot animation.
I've tried a lot of things, but the phone seems to be hardbricked:
- I can access recovery, but restoring does "FAIL" (restoring boot partition works, though). Restoring "system" aborts at about 18%, "data" immediately.
- I can access the phone through fastboot, but cannot flash anything. Whatever I do, the phone isn't changed. Tried reverting to stock (getting error when flashing gpt.bin, everything else seemed to work without errors, but no changes), tested flashing other recoveries (partition size mismatch, but that seems to be normal, whatever I flash, it keeps being TWRP 2.8.6.0), or even upgrade the bootloader (no errors reported at all, but no changes made to the phone).
- I can access the phone by MTP from TWRP, but cannot write to or delete anything from the internal SD.
Do you have any further ideas or is it an hardbrick?
Thanks in advance
René
Seems like the internal SD card is damaged, or there's a faulty partition table. Have you tried repairing and formatting /system and /data partitions with TWRP? Does it read external sd cards? If yes you could try flashing CM11 (because lollipop roms need an updated bootloader) from an external sdcard and see what happens. Also your backup could be corrupted, that's why it doesn't let you restore it at all.
As for the recovery, try updating your twrp to the latest version available (3.0). You can update twrp from twrp itself, just to see if it's fastboot's fault.
Wiped /system and /data. Didn't help. Wiping /data/media led to an error.
Is there anything beyond "wipe" to repair and format those partitions?
Thanks for the hints, will try updating TWRP and installing 11 this weekend, as external SDs can be accessed.
Greetings from Germany
René
After formatting data partition, I am unable to restore backed-up data directly as I get an error (255?). I have to always let the phone boot to the welcome setup screen before going back into TWRP to restore my backup.
Is there something I can do to avoid this lengthy step?
I found the same. It's almost as if twrp doesn't format correctly.
I typically use fastboot -w, flash, then boot into the ROM, then restore from backup.
Today I wanted to root my phone. So I flashed twrp to later flash supersu. After i flashed twrp the phone worked fine, I could boot normally and go into recovery to access twrp. However, after I flashed supersu I couldn't boot back into android. After several tries of recovering the data its been a mix between bootlooping twrp or being stuck in the splash screen. I could format the partitions to clean everything, but I can't do that because I need to recover my 2FA codes (cause I didn't backup them up) so I dont lose access to my accounts. I tried unencrypting the storage from twrp but it always failed, even though it was the correct password (I use a pattern to unlock but I converted it to a code). Is there any way I can recover my data or do I have to reset everything?
Goto recovery and copy internal storage to pc
Sadman Fahad said:
Goto recovery and copy internal storage to pc
Click to expand...
Click to collapse
I cant find an option that lets me do this, since the partition is encrypted. Can you help me further?