Hello to all.
My phone is locked on by forcing me to remove the battery. I rebooted the phone and you are stuck at the loading screen.
I reloaded the OS (version JW7_JW2_JW1) and recovery(version CF-Root-v4.4-XX_OXA_JW4-CWM3RFS) through ODIN, but the phone still does not start.
I booted the phone into recovery and made a backup. I was able to manually copy all the documents.
From the backup of the recovery, through the tool unyaffs, I recovered the contact database (contacts2.db).
Now I started the trouble because I can not find the message database. I have read that you should find in the folder com.android.providers.telephony, but the folder is empty.
Fearful of losing these files, I used the tool ddrescue as follows:
Code:
sudo ddrescue -r 3 /dev/sdb /my_path/image /my_path/logfile
I then mounted the file image with the command:
Code:
sudo mount image /mnt
To my surprise, I do not see all the hidden files that is able to recover the recovery.
Do you think that I've lost forever the phone's message?
Thanks in advance for any help you will be able to provide me, hello to everyone.
PS: I apologize for any inaccuracies or technical errors, but they are new to this type of work.
===================================================================
Hello to all.
I was able to recover and restore the data of the Memo. The database is located in the folder com.sec.android.app.memo
No one has an idea on how to restart the phone and try to recover / export of SMS?
Thank you all.
Help revive my device.
After updating the tablet from the playmarket of the Youtube application, the tablet freezes, after a reboot, it hangs on the Asus logo and a spinning circle. I couldn’t enter the droidboot from the buttons and, following the instructions from the 4pda forum, after downloading the service firmware, unpacked it to drive C into the folder, then went to the firmware folder by pressing shift + the right mouse button opened the command window and launched the
droidboot with the fastboot boot droidboot.img
fastboot continue
commands booted into the droidboot and in the folder with the firmware clicked on the update_image file, the firmware process started which took a very long time about 7 hours, at the end the tablet rebooted but only until the first screen saver. I waited a long time, but it did not boot. I turned it off. After that, by pressing a combination of buttons, I was able to enter the droidboot, the serial number of the tablet was missing, through a dead robot I was able to enter the recovery.
Then, according to another instruction from 4pda, through a temporary twrp, I tried to install the Ul-KO13-WW-3.2.23.182-user firmware, the installation process started, but it did not install, but the serial number returned and the tablet again hung on the Asus logo and a spinning circle.
I checked the
fastboot oem start_partitioning
fastboot flash /tmp/patrition.tbl partition.tbl
fastboot oem partition /tmp/partition.tbl
commands after each command was OK. So the flash memory of the tablet is working.
After I checked the root, the rights remained. USB debugging in the developer menu was turned on even when the tablet was working. Then I decided to try installing the service firmware 201 again, as I wrote above, and again unsuccessfully, the serial number flashed again. . And again, through a temporary twrp, I began to install 182 firmware.
And the serial number failed, it was not restored, but the recovery now showed that it costs 182 firmware. After that, when checking, I found out that no root su. I got a complete crash. I tried again to install 201 firmware and now it costs WW 3.2.23.201 in recovery.
On the advice of a person from the 4pda forum, I tried to restore images of 201 firmware boot.img fastboot.img recovery.img via twrp v2.8.7.0 from the 4pda forum, but again unsuccessfully. I showed the person who helped me install the firmware images 201 that twrp gave me an installation error, it read:
Updating partition details ...
E: Unable to mount '/ factory'
E: Unable to mount '/ config'
E: Unable to mount '/ data'.
The person who helped me said that there was no markup table, or rather, the system section was written, but could not find the other sections, since he wrote this script for Android 5. And on KitKat version 4.4, he did not test this script. Now I'm desperate, I really need a tablet in working condition. Because I am very poor, and I do not have money to buy another tablet, I have been sick for 5 years. I live on disability benefits, they pay me $ 50 a month and I can’t buy another one. I beg everyone to help with tips and instructions on how to restore tablet firmware. I need a worker. I need your help.
Even when connecting to a laptop on a Windows 7 tablet in twrp 2.8.7.0 mode, the tablet is detected as K013, but it does not see the internal drive and only shows a microSD card, I suggest that this is because the firmware is installed incorrectly and there are no firmware sections? ? If Who knows, you can install any custom firmware that fits on my tablet.
If someone can write me instructions for restoring the firmware. If anyone has encountered a similar problem, give information and instructions for restoring partitions with links from where to download what and step-by-step instructions for restoring.
Sorry text wrote through translator. I hope the problem is described clearly and someone can help me with the firmware.
I thank everyone in advance who will respond and help restore the firmware.
P.S. I decided to try to flash through Intel Flash Tool Lite, I launched service 201 firmware, reached the 57% band and issued FAILED. I turned off the tablet, I decided to try running TWRP, running the script, and now there are only two errors:
E: Unabled to mount / and
E: Unabled to mount / config, and the amount of internal memory Internal Storage (3916MB) !!! And before that, it was zero and in the device k013 on the laptop it shows the storage along with the memory card. Here's an interesting process
Hello ,
i have a Teclast Tbook x16 Pro (i think smae hardware like X98) and accidentally deleted all partitions on flashdrive. Now i try to restore the original partition and software.
I Have installed iSocUSB-Driver-Setup-1.2.0 IntelAndroidDrvSetup1.5.0 andPhoneFlashTool_5.3.2.0_win32 and can boot to dnx mode but when i start the upload process it stops at 20% und the device boot to the efi shell. I also try the mirek-tool. There is the same. It upload the first .bin and then waiting for device, but the device boot to the efi shell. When i reboot the device to dnx mode, the tool continue but all operations return an error.
Do you have some help?
best regards
Oliver
i followed all the steps listed in on oxygen os thread but now i am stuck with twrp and can't install any os
so i tried to install my old os back but twrp install section i am not able to acess to .ozip file and also if i try to install anything or even clear cache it shows
E: Unhandled flags: 'wrappedkey'
E : Unable to decrypt FBE device
when i first installed twrp it asked me my screen password and i put the right password in but still its showing unable to decrypt FBE device
help me!:crying::crying:
Did you try to format data (the one where you need to type yes)? I once had the situation where I couldn't decrypt and couldn't format and reinstalling twrp solved that for me.
yes i also did that still nothing
now only thing left is unable to decrypt fbe device
Try putting your problem in the rom thread the dev may help you better
thanks its solved now just need to remove everything with the fastboot command and then reinstalling everthing again from twrp to os
Hi guys !
I tried to install Lineage OS 17.1 on my Xperia Z3 compact and everything went well until I installed the openGapps (before reboot like tutorial said). I'm now stuck on the recovery screen where this message appears :
"Can't load Android system. Your data may be corrupt".
as well as the following error:
"E: Failed to bind mount /mtn/staging/emulated/media/0 to /storage/emulated: No such file directory"
I can "Try again" or "Factory Data reset" but neither option works! In both cases I'm stuck here again. I can't even turn off the phone or reboot via adb shell either since it is now recognized as "unauthorized".
I read a lot of topics but I have not find an answer.
Can it be an hard brick ? Please help. Thx
Try reinstalling stock ROM using Flashtool.