Need system.img, boot.img and recovery.img - Asus ZenWatch 2

Hello there,
can someone please provide a system.img, recovery.img and boot.img from a WI501Q? I've derped something up quite hard by backing up the system partition while the bootloader was still locked, now I tried to flash it and the filesystem seems to be corrupted...
I tried reflashing a TWRP backup made from someone else but even transfering the backup to the watch fails at some point with "protocol error"... The watch reboots then and no files were saved to the watch.
Thanks already!
See Post #4 on how I resolved this (kinda).

[del]

ranf said:
[del]
Click to expand...
Click to collapse
What did you mean by using ext2simg?

Okay, after some derping around, trying, failing and more I managed to restore it...
I had a TWRP backup from my still OEM locked bootloader (I booted TWRP via fastboot boot twrp3.img), via fastboot I formated the system, userdata, cache and so on partitions and something along those lines seemed to work.
Before that the /data partition seemed to be corrupt for whatever reason, not even TWRP was able to display the free space. After doing the above it suddenly was able to display it again but the /data/media folder was missing, I created it manually, pushed the TWRP folder onto it, Restored and it worked!
So yeah, not sure what exactly went wrong here or how to fix it... Sorry...

EpicLPer said:
What did you mean by using ext2simg?
Click to expand...
Click to collapse
In Ubuntu it is in this package:
http://packages.ubuntu.com/xenial/amd64/android-tools-fsutils/filelist
Works better than img2simg.

Related

CWM Recovery Test for MediaPad

CWM 5.8.0.9 for Huawei MediaPad
WARNING !!! DON'T FORMAT AND DON'T WIPE PARTITIONS USING THESE CWM !
I don't know how much this CWM version improves over the existing one by segler11.
However these build were more aimed at compiling and testing the new kernel sources.
I have tested compiling with both arm-eabi-4.4.0 and arm-eabi-4.4.3 with success on Ubuntu 10.04.
This is experimental, however with the new kernel sources it will just be a matter of time.
I have compiled the kernel included in this CWM recovery image but I didn't recompile the complete image.
I took as base Pyramid CWM 5.8.0.9 and I replaced the files from those found on a stock C232B005 kernel.
As the default build configuration I have used the /proc/config.gz of a C232B005 running kernel.
I have tested this CWM to be able to backup these partitions (I have not tested "restore" yet, just checked the tar archives):
boot.img - 12.582.912 (match 12Mb)
recovery.img - 16.777.216 (match 16Mb)
data.ext4.tar
cache.ext4.tar
system.ext4.tar
custom.ext4.tar
as you can see my hand tweaks to "recovery" require the name of "cust" partition to be "custom" instead but I believe this is a no issue while you backup and restore with the same CWM. Suggestions welcome.
BUGS:
data & time on archives are wrong
mount USB storage does not work
adb not enabled in recovery mode
Formats and Wipes do not work don't use them
The "busybox hwclock" applet doesn't work to set the hardware clock of our device.
The "adb shell" is not active while in CWM recovery, I don't know why and this was my objective so if you have suggestion please help.
As usual flash both "recovery" and "recovery2" partitions using "fastboot" and one of the attached CWM recovery:
Code:
fastboot flash recovery recovery-5.8.0.9-HWMOD-eabi-4.4.3.img
fastboot flash recovery2 recovery-5.8.0.9-HWMOD-eabi-4.4.3.img
fastboot reboot
WARNING !!! DON'T FORMAT AND DON'T WIPE PARTITIONS USING THESE CWM !
.:HWMOD:.
.
Reserved CWM HWMOD
This version seemed to work better for me.Tnx dude!
john9 said:
This version seemed to work better for me.Tnx dude!
Click to expand...
Click to collapse
Thank you for trying it.
Remember to absolutely avoid formatting or wiping partitions.
If you need to format/wipe do it ONLY after reinstalling the original "recovery.img" in both "recovery" and "recovery2" partitions and then reset the device from:
"Settings -> Backup and reset -> Factory reset"
ATTENTION !!! You can safely do a wipe or factory reset only after reinstalling the original recovery image.
Sorry for insisting but I don't want to create problems on users devices and I know those operations will create problems.
.:HWMOD:.
Just a note: I used your 4.4.3 version to try making a nandroid backup last night. Good news and bad news.
This morning I inspected the result using the app Nandroid Browser.
Good: Your CWM does successfully backup /data/data. The other CWM that had been posted here did not do so properly.
Bad: Your CWM also backs up the entire internal SD storage contents inside the folder /data/share. It is customary *not* to include this in a nandroid backup because a) you don't want to inflate the file size unnecessarily, and b) you don't want to overwrite the internal SD on a restore.
Idea: After you fix it, and until you manage to get ADB over USB working, maybe you could add a menu option to make a separate backup archive of internal SD to external SD. This would allow a route to save the internal storage if the device becomes unbootable and requires a data wipe.
cmstlist said:
Just a note: I used your 4.4.3 version to try making a nandroid backup last night. Good news and bad news.
This morning I inspected the result using the app Nandroid Browser.
Good: Your CWM does successfully backup /data/data. The other CWM that had been posted here did not do so properly.
Bad: Your CWM also backs up the entire internal SD storage contents inside the folder /data/share. It is customary *not* to include this in a nandroid backup because a) you don't want to inflate the file size unnecessarily, and b) you don't want to overwrite the internal SD on a restore.
Idea: After you fix it, and until you manage to get ADB over USB working, maybe you could add a menu option to make a separate backup archive of internal SD to external SD. This would allow a route to save the internal storage if the device becomes unbootable and requires a data wipe.
Click to expand...
Click to collapse
Thank you for trying it. I wanted to compile/test a kernel with new sources in a CWM.
Yes, in our device the internal memory "/mnt/sdcard" is also mapped under "/data/share".
Unfortunately I don't have the skills (yet) to build a complete recovery image from scratch,
so what I did was just compiling the kernel part of the recovery image, using the new sources.
Then I simply hex tweaked the "recovery" executable of a 5.8.0.9 Pyramid CWM (HTC Sensation).
So, in conclusion, I have no control over what is copied during the backup process of those partitions.
Though I could control which partition is processed by removing them from "fstab", but there is no gain into it.
We will have to wait somebody with the specific knowledge, or maybe I will have some time to learn once I return from holidays.
.:HWMOD:.
Today i have builded bootable CWM 5.5.0.4 from sources, so now we can adjust all what we need
after_silence said:
Today i have builded bootable CWM 5.5.0.4 from sources, so now we can adjust all what we need
Click to expand...
Click to collapse
well done
HI, can anyone share buckup from working device created by CWM.?
Thanks to all.
Hi,
Is it possible to flash update zips from this CWM recovery (like Beats Audio which is in flashable zip format)?
I don't want to use it for backup-recovery.
...and how about doing wipe cache and wipe dalvik cache?
.dredd. said:
Hi,
Is it possible to flash update zips from this CWM recovery (like Beats Audio which is in flashable zip format)?
I don't want to use it for backup-recovery.
...and how about doing wipe cache and wipe dalvik cache?
Click to expand...
Click to collapse
Haven't tried installing a ".zip" archive from CWM but it should work.
Avoid "wiping" and/or "formatting" partitions, they will be messed up.
hwmod said:
Haven't tried installing a ".zip" archive from CWM but it should work.
Avoid "wiping" and/or "formatting" partitions, they will be messed up.
Click to expand...
Click to collapse
The main reason for use of CWM would be to have the possibility of flashing update zips from CWM... but I am afraid of messing up my device... to understand: no problem if I have to reflash the rom but I would not want to cause mistake which could be repaired only by service.
fastboot is always available if something goes wrong and if you flash cwm you wont be able to install official roms because cwm will overwrite stock recovery
so i was stupid and wiped data and cache - then remembered that it said not to - how do i fix this paperweight? i tried fastbooting all the usual partitions (system, boot, userdata, cache, etc) but still nothing - i can get to fastboot but i cant flash any dload updates. any suggestions are greatly appreciated.
flash stock recovery (2 files) from zipped rom via fastboot and then you should be able to flash stock rom
flashed three different stock recoveries to recovery and recovery2 - still only get the media pad logo twice (flashed androidani intl rom before bricking) cant boot to recovery - think the partition table is screwed. is there a way to create partitions from fastboot, and if so, still would be nice to know the names of the partitions to flash as referenced in tmo stock thread.
byt3b0mb said:
flashed three different stock recoveries to recovery and recovery2 - still only get the media pad logo twice (flashed androidani intl rom before bricking) cant boot to recovery - think the partition table is screwed. is there a way to create partitions from fastboot, and if so, still would be nice to know the names of the partitions to flash as referenced in tmo stock thread.
Click to expand...
Click to collapse
The time needed to reformat and rewrite all the firmware partitions (the first time) will be between 10-15 minutes.
Be patient and give enough time to the device to execute all the needed processes.
When the device finally boot it need to completely regenerate dalvik-cache (the first time).
So try again as instructed above, rewrite "BOTH" partitions named "recovery" and "recovery2", both using the same "recovery.img" file found in the latest stock Huawei firmware.
Now extract the stock Huawei firmware archive on your PC and copy the "dload" folder on an empty formatted SDCard, then insert the SDCard in the MediaPad reboot it and wait until success or failure message.
If you wiped partitions you will have to wait more time (20-30m). It may be that after waiting a while a message about "Encryption not possible" could appear, just say no to encryption and let it reset the device.
It already happened to some of us so hope you are also able to recover your tablet.
thanks i will give it a shot - while it is rewriting partitions, should it be on the huawei logo? or should i see the android / gears turning?
byt3b0mb said:
thanks i will give it a shot - while it is rewriting partitions, should it be on the huawei logo? or should i see the android / gears turning?
Click to expand...
Click to collapse
First time restoration takes time on both moments during the 1st Huawei log and even during animation.
Trying to recover a partition that was wiped takes much longer for the OS to show the error.
When I tried wiping "data" and rebooted the device I recall I went for a long walk and when I returned the device was showing the "Encryption failure / Reset" message (about half an hour later).
So I can only suggest that when you retry you wait at least that amount of time (30 min.) with charger connected, whatever happens leave it alone until it display or ask you do something. Let me know if it works when you have tried.
Download links do not work for me. Can you upload in mediafire please?

HTC Desire 610 ROM help

Basically, I deleted system on my Desire 610 and I have no idea what to do now, so I came to ask you guys for help. Cheers.
I have actually found the stock system.img, recovery.img and boot.img by jmz, but every time I try to flash the system.img in via fastboot I get the following error: load_file: could not allocate -1879048192 bytes
error: cannot load 'system.img'
Can anyone please help me ASAP? I really need to get my phone up running soon. Thanks!
terminator54 said:
I have actually found the stock system.img, recovery.img and boot.img by jmz, but every time I try to flash the system.img in via fastboot I get the following error: load_file: could not allocate -1879048192 bytes
error: cannot load 'system.img'
Can anyone please help me ASAP? I really need to get my phone up running soon. Thanks!
Click to expand...
Click to collapse
Where did yoy buy the phone. We need to no which variant you have to be of any help.
MiniBlu
I bought it in Croatia, so I guess it'd be East Europe or just Europe. I've downloaded many RUU's so far and neither got past sending or updating signature...
EDIT: I tried to flash the system.img with different fastboot files and now I get the following error: invalid sparse file format at header magi.
terminator54 said:
I bought it in Croatia, so I guess it'd be East Europe or just Europe. I've downloaded many RUU's so far and neither got past sending or updating signature...
EDIT: I tried to flash the system.img with different fastboot files and now I get the following error: invalid sparse file format at header magi.
Click to expand...
Click to collapse
There is no ruu for european devices available but the buckup linked in this post http://forum.xda-developers.com/showpost.php?p=63189341&postcount=112 should work.
MiniBlu
MiniBlu said:
There is no ruu for european devices available but the buckup linked in this post http://forum.xda-developers.com/showpost.php?p=63189341&postcount=112 should work.
MiniBlu
Click to expand...
Click to collapse
Thanks alot. I'll try it out and then get back to you with the results.
E: Could you be more specific? Where do I need to extract it?
No need to extract it flash with twrp, if u don't have it you can flash it via adb, I made a thread to flash updates on rooted device u can use it as a guide to flash twrp only
porozex said:
No need to extract it flash with twrp, if u don't have it you can flash it via adb, I made a thread to flash updates on rooted device u can use it as a guide to flash twrp only
Click to expand...
Click to collapse
Actually the link I posted is to a rar compressed twrp backup. It needs to be extracted to an sdcard in /twrp/backup folder then use the restore function in twrp to restore it. Last time I checked all the links I could find to flashable zips for eu devices have gone dead. Also It would be a good idea to do a factory reset in twrp(in Wipe menu) before restoring the backup.
MiniBlu
MiniBlu said:
Actually the link I posted is to a rar compressed twrp backup. It needs to be extracted to an sdcard in /twrp/backup folder then use the restore function in twrp to restore it. Last time I checked all the links I could find to flashable zips for eu devices have gone dead. Also It would be a good idea to do a factory reset in twrp(in Wipe menu) before restoring the backup.
MiniBlu
Click to expand...
Click to collapse
So, pretty much I need to create a new folder on an sdcard and name it twrp and then make another folder in the twrp one and name it backup and then just extract the folder from the .zip file in there?
terminator54 said:
So, pretty much I need to create a new folder on an sdcard and name it twrp and then make another folder in the twrp one and name it backup and then just extract the folder from the .zip file in there?
Click to expand...
Click to collapse
Yes except the folder names are actualy TWRP and BACKUPS . Then in twrp hit restore button. and select external sd as backup location. Then select the backup and swipe to restore. This is a UK backup but it should work ok except if you need languages that aren't there you can install "more locales 2" from play store. I hope this works for you.
MiniBlu
MiniBlu said:
Yes except the folder names are actualy TWRP and BACKUPS . Then in twrp hit restore button. and select external sd as backup location. Then select the backup and swipe to restore. This is a UK backup but it should work ok except if you need languages that aren't there you can install "more locales 2" from play store. I hope this works for you.
MiniBlu
Click to expand...
Click to collapse
I did everything alike, but when I enter restore it appears empty.
EDIT: I found a solution for that aswell. Apparently, I have to copy the backup folder to data/media/0 to be able to see it in restore, but I don't have data/media/0, I only have data/media. Anything I can do about that?
EDIT 2: I managed to fix everything. I owe you alot, man. Thanks a bunch, bunch, bunch!

Messed up partitions & unable to flash

Hey everyone,
A few days ago, I decided to downgrade from AICP 11 back to 10 (Android 6.0.1 to 5.1.1), wiped everything but internal storage. When flashing, I got an error, saying that the /vendor partition was missing, and indeed, while it existed, I could only mount it forcefully, because the device was busy.
This lead to a complete wipe, as after a reboot, TWRP asked for an encryption password, which I didn't set. Here, I did a factory reset & wiped everything. After that, I tried flashing again (5.1.1), but after it was completed, I got a line, which said "Couldn't unmount /system", which is true, as it's already unmounted. But when I mount it, all the files that are supposed to be installed seem to be there.
When I reboot the device, it gets stuck on the Google logo.
Frankly, I'm afraid to even flash back to stock, so I was hoping that someone more experienced could help me out.
It should be noted, that I still have access to fastboot, and TWRP.
Thanks in advance,
DecentM
How did you force mount /vendor?
Can you clarify where you are seeing these problems? (TWRP or within Android)
Do you have any nandroid backups to test and see if they work?
dmantilal said:
How did you force mount /vendor?
Can you clarify where you are seeing these problems? (TWRP or within Android)
Do you have any nandroid backups to test and see if they work?
Click to expand...
Click to collapse
I used mount -f and umount -f in the TWRP terminal
I see all these problems in TWRP, since I can't boot/get past the initial Google logo.
I do have a nandroid backuip on my laptop (as I had to wipe the tablet clean), but that's currently unavailable for me to use, I'll reply back when I tried it.
I doubt it will work, because it just extracts data to a predefined path, which seems like the same thing an installer zip does.
DecentM said:
I used mount -f and umount -f in the TWRP terminal
I see all these problems in TWRP, since I can't boot/get past the initial Google logo.
I do have a nandroid backuip on my laptop (as I had to wipe the tablet clean), but that's currently unavailable for me to use, I'll reply back when I tried it.
I doubt it will work, because it just extracts data to a predefined path, which seems like the same thing an installer zip does.
Click to expand...
Click to collapse
Why did you need /vendor mounted in TWRP?
I thought flashing used dd (command) or similar to copy the *.img file to the partition (or, more accurately, the block device). If /vendor is mounted during *.img copy, that would most likely cause errors.
dmantilal said:
Why did you need /vendor mounted in TWRP?
I thought flashing used dd (command) or similar to copy the *.img file to the partition (or, more accurately, the block device). If /vendor is mounted during *.img copy, that would most likely cause errors.
Click to expand...
Click to collapse
I mounted it, because when I initially restored the 5.1.1 rom, I got an error, saying that the /vendor partition wasn't mounted.
DecentM said:
I mounted it, because when I initially restored the 5.1.1 rom, I got an error, saying that the /vendor partition wasn't mounted.
Click to expand...
Click to collapse
You are sure it was complaining about "unmounted", rather than "mounted"?
Do these roms include a vendor.img? You may need to flash the stock 5.1.1 vendor.img.
Either way, unless you mkfs'ed or resize2fs'ed the partitions, they should be fine. Full wipe & go.
dmantilal said:
You are sure it was complaining about "unmounted", rather than "mounted"?
Do these roms include a vendor.img? You may need to flash the stock 5.1.1 vendor.img.
Either way, unless you mkfs'ed or resize2fs'ed the partitions, they should be fine. Full wipe & go.
Click to expand...
Click to collapse
I'm not sure.
I already did a full wipe, but it still had issues. I'll try again tomorrow, and report back on how it went.
DecentM said:
I'm not sure.
I already did a full wipe, but it still had issues. I'll try again tomorrow, and report back how it went.
Click to expand...
Click to collapse
Having a mismatched vendor.img could be your problem.
No ROM I know of includes a vendor.img. I think it is a legal issue, like including GApps with a ROM.
dmantilal said:
Having a mismatched vendor.img could be your problem.
No ROM I know of includes a vendor.img. I think it is a legal issue, like including GApps with a ROM.
Click to expand...
Click to collapse
I don't think that the issue is with the vendor image anymore, but with the partitions in general. I always had a mismatched vendor image, as it only results in a modal box after boot.
My problem is again, with the /system partition not being visible to flashable zip files.
Mismatched vendor.img can also cause bootloops and other quirks like battery-charge percentage inaccuracies.

Zero support Zenwatch 2 WI502Q

Unfortunatelly I haven't found any support for this watch (system img, or saved full Twrp backup, factory img...) to repair the softbrick. I have found the ota.zip file, but I can't use it because of the system7 error. I have a Twrp on my watch, but I can't find any way to restart my wach. I'm so sad because I can't use my watch.
me too. I stuck with the smaller model because I thought that it looked much better with my Nemesis leather cuff band than the larger model. But no one seems to have the original system image or a recovery I could use for it since I bricked mine. I've gone back to my Misfit Shine, which is not even close to being a smartwatch
Take a look to my thread, I uploaded a twrp backup, but for WI501Q (system+boot)
TWRP BACKUP
https://www.dropbox.com/s/6d51x7mkub6e5ag/TWRP-2016-03-08.zip?dl=0
matze19999 said:
Take a look to my thread, I uploaded a twrp backup (system+boot)
---------- Post added at 21:25 ---------- Previous post was at 21:16 ----------
TWRP BACKUP
https://www.dropbox.com/s/2dcjdeen58kz0qy/asus2.zip?dl=0
Click to expand...
Click to collapse
I downloaded the file and unzipped it. I booted to twrp recovery and used ADB PUSH to send the files to /sdcard/ on the watch. I then used Install in twrp to install the recovery and boot img files (there is no option in twrp to install system.img). After all of this I still cannot boot the watch, it goes to CSC Fastboot.
Am I doing something wrong?
Yeah, its a twrp backup file. Create a random backup ( for example only Boot.IMG ) in twrp. It will create a folder in /sdcard/twrp/ which is named XXXX-XXXX. Its different from device to device. In this folder you can move my twrp backup folder. Then reboot again to twrp. Now you will find a backup item in restore tab. Thats my backup
matze19999 said:
Yeah, its a twrp backup file. Create a random backup ( for example only Boot.IMG ) in twrp. It will create a folder in /sdcard/twrp/ which is named XXXX-XXXX. Its different from device to device. In this folder you can move my twrp backup folder. Then reboot again to twrp. Now you will find a backup item in restore tab. Thats my backup
Click to expand...
Click to collapse
Thank you for all the steps.
I tried the steps and I noticed that when I selected the restore option only BOOT was able to restore. So I looked at the backup that twrp made and the filenames were actually boot.emmc.win, recovery.emmc.win, and system.emmc.win. So I took your three files and renamed the img extensions to emmc.win extensions and moved them directly to the backup folder that twrp created. This allowed me to be able to select all three options for restore (boot, recovery and system). The restore completed without errors. However when I reboot the watch it continues to quickly show "Recovery Mode!" and go to "CSC Fastboot Mode!"
Am I still doing this wrong?
download the backup file again and test it
matze19999 said:
download the backup file again and test it
Click to expand...
Click to collapse
I downloaded it again using the same method I described earlier, but I get the same result.
I have the wren device WI502Q.
Backup file is only for sparrow
I guess this thread really does prove there is no support for wren, as the title states. Too bad..
Welp i'll just buy a new watch. My CAVS just won!!!! Wooooo!!!!!!
cland216 said:
I guess this thread really does prove there is no support for wren, as the title states. Too bad..
Click to expand...
Click to collapse
https://r3---sn-h0j7snel.gvt1.com/p...9A6B905E737F34D1021CDEC6AED82CB6617A&key=cms1
stock rom for small version
matze19999 said:
https://r3---sn-h0j7snel.gvt1.com/p...9A6B905E737F34D1021CDEC6AED82CB6617A&key=cms1
stock rom for small version
Click to expand...
Click to collapse
I get an Error 7:
"this device has omni_wren wren:6.0.1/MHC19J"
I updated the watch to MM before I bricked it. Where can I find MHC19J image?
I have a stock Wren on mm, you still need a backup?
couchlock said:
I have a stock Wren on mm, you still need a backup?
Click to expand...
Click to collapse
I am thinking of rooting and would really appreciate a backup just in case. I really would appreciate it and I know others would appreciate it as well.
I'll be off in a couple days. I'll post a link from my mega account when I get it.
https://forum.xda-developers.com/zenwatch-2/general/wi502q-how-unbricked-watch-twrp-backup-t3521916
Unbrick guide I made.
So what do you need a back up of and how do I make the backup. Sorry so long but I finally have time. And a PC again

Need help saving data from bootloping S2

Hi,
I'm running the last cyanogenmod 12.1 ROM on my S2. There is no custom kernel or recovery. The only thing I did was a repartition to 1GB system. This setup ran since 2016 feb. without problems. Tuesday morning got a notification from the play store, that there are updates to some of my apps, so I set my phone to update them all and left it there. I came back after 20min and then came the problem:
The phone is bootlooping. The booting animation finishes, then it starts optimizing my apps, every time different amount of apps. After it finishes it starts booting again... rinse and repeat. I tried to leave it there for a very long time, with no success. The phone is very hot in the CPU area and the battery gets hot too when it's bootlooping.
I am able to go in recovery and download mode. My recovery is the stock cyanogen recovery unfortunately. I tried putting it in download mode and since I have Android Studio installed on my pc, I tried to establish an adb shell (with adb shell command) with the adb tool that came it. Unfortunately it does not find my device (neither with adb devices). I might do it wrong though. Fortunately Odin 3.04 seems to recognize my phone, so I might be able the flash something, but I'm afraid that my internal memory is starting to fail and that is causing all these issues, so the flash would fail. First I'd like to try to save data without flashing if possible.
I have most of my user data on my sd card, so the most important thing would be to save is my contacts, messages and call history. No, I don't sync it with google, yes I know it's stupid. It used to mess up my contact list so I dropped using it.
Any help and advice would be appreciated, thanks in advance!
N7Gabe said:
Hi,
I'm running the last cyanogenmod 12.1 ROM on my S2. There is no custom kernel or recovery. The only thing I did was a repartition to 1GB system. This setup ran since 2016 feb. without problems. Tuesday morning got a notification from the play store, that there are updates to some of my apps, so I set my phone to update them all and left it there. I came back after 20min and then came the problem:
The phone is bootlooping. The booting animation finishes, then it starts optimizing my apps, every time different amount of apps. After it finishes it starts booting again... rinse and repeat. I tried to leave it there for a very long time, with no success. The phone is very hot in the CPU area and the battery gets hot too when it's bootlooping.
I am able to go in recovery and download mode. My recovery is the stock cyanogen recovery unfortunately. I tried putting it in download mode and since I have Android Studio installed on my pc, I tried to establish an adb shell (with adb shell command) with the adb tool that came it. Unfortunately it does not find my device (neither with adb devices). I might do it wrong though. Fortunately Odin 3.04 seems to recognize my phone, so I might be able the flash something, but I'm afraid that my internal memory is starting to fail and that is causing all these issues, so the flash would fail. First I'd like to try to save data without flashing if possible.
I have most of my user data on my sd card, so the most important thing would be to save is my contacts, messages and call history. No, I don't sync it with google, yes I know it's stupid. It used to mess up my contact list so I dropped using it.
Any help and advice would be appreciated, thanks in advance!
Click to expand...
Click to collapse
Ok, did you try dirty flashing the ROM using CyanogenMod recovery?
And then wiping cache and dalvik cache?
MigoMujahid said:
Ok, did you try dirty flashing the ROM using CyanogenMod recovery?
And then wiping cache and dalvik cache?
Click to expand...
Click to collapse
First of all, thanks for the advice, I didn't think of that. I assume this means there is probably no solution without flashing. Do I need to flash gapps too?
N7Gabe said:
First of all, thanks for the advice, I didn't think of that. I assume this means there is probably no solution without flashing. Do I need to flash gapps too?
Click to expand...
Click to collapse
No, no need for that, just the ROM, and it won't delete anything.
MigoMujahid said:
No, no need for that, just the ROM, and it won't delete anything.
Click to expand...
Click to collapse
So, I went to recovery, pressed apply update, searched for the cm12.1-20160203-nightly rom (same I had installed), flashed it without error messages, then I pressed wipe cache partition, then reboot system now. Now the phone starts to boot, the boot animation is playing for a few minutes, then the phone turns off. Tried it multiple times, with and without charging. I can still get into recovery.
N7Gabe said:
So, I went to recovery, pressed apply update, searched for the cm12.1-20160203-nightly rom (same I had installed), flashed it without error messages, then I pressed wipe cache partition, then reboot system now. Now the phone starts to boot, the boot animation is playing for a few minutes, then the phone turns off. Tried it multiple times, with and without charging. I can still get into recovery.
Click to expand...
Click to collapse
Ok, we will try another thing, can your phone be recognized using adb in recovery?
If so you can pull the data(contacts, sms) using adb pull command.
The data usually is stored there:
/data/data/com.android.providers.telephony/databases/mmssms.db
And there:
/data/data/com.android.providers.contacts/databases/contacts.db
If you were able to do it then fine, if not, there is luckily another solution!!
You have the latest cm12.1 build which is Feb 3rd build, so your build support iso-rec TWRP recovery, so you can flash TWRP recovery zip provided by the.gangster using CM recovery and reboot recovery so it will replace the CM recovery with TWRP, in TWRP you can mount system and data using "mount", and using the file manager there you can access the above mentioned directories and copy the files manually in the external sdcard(or the internal sdcard), then you can clean flash and copy them again after that.
That would be the ultimate solution
MigoMujahid said:
Ok, we will try another thing, can your phone be recognized using adb in recovery?
If so you can pull the data(contacts, sms) using adb pull command.
The data usually is stored there:
/data/data/com.android.providers.telephony/databases/mmssms.db
And there:
/data/data/com.android.providers.contacts/databases/contacts.db
If you were able to do it then fine, if not, there is luckily another solution!!
You have the latest cm12.1 build which is Feb 3rd build, so your build support iso-rec TWRP recovery, so you can flash TWRP recovery zip provided by the.gangster using CM recovery and reboot recovery so it will replace the CM recovery with TWRP, in TWRP you can mount system and data using "mount", and using the file manager there you can access the above mentioned directories and copy the files manually in the external sdcard(or the internal sdcard), then you can clean flash and copy them again after that.
That would be the ultimate solution
Click to expand...
Click to collapse
In recovery I can see my device with adb, but every command runs into a device unauthorized error.
Code:
D:\Android\sdk\platform-tools>adb devices
List of devices attached
0009bd0863c43f unauthorized
Code:
D:\Android\sdk\platform-tools>adb shell
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
etc.
So I assume I flash TWRP with odin. Is it possible to save data to a PC through USB connection with TWRP? I'm asking, because I'd still prefer a full backup if possible (I don't have the space for it on my external sd). Second question, if I'm able to save mmssms.db and contacts.db, how do I extract the data from it, or maybe reimport it (even to a different phone/ROM)? I don't entirely understand isorec, but let's say I manage to flash TWRP and save my data. Can I flash the latest LOS 14.1 and keep the isorec TWRP? Or after the LOS flash, I need to flash TWRP again? As I mentioned I already have the 1GB system partition, so that shouldn't be an issue. It would be a nice two birds with one stone, saving my data and updating my obsolete ROM to a isorec TWRP+LOS 14.1 combo.
Lastly, this is the recovery you mentioned, right?: recovery-the.gangster-IsoRec-TWRP-3.1.0-0-i9100.zip
N7Gabe said:
In recovery I can see my device with adb, but every command runs into a device unauthorized error.
etc.
So I assume I flash TWRP with odin. Is it possible to save data to a PC through USB connection with TWRP? I'm asking, because I'd still prefer a full backup if possible (I don't have the space for it on my external sd). Second question, if I'm able to save mmssms.db and contacts.db, how do I extract the data from it, or maybe reimport it (even to a different phone/ROM)? I don't entirely understand isorec, but let's say I manage to flash TWRP and save my data. Can I flash the latest LOS 14.1 and keep the isorec TWRP? Or after the LOS flash, I need to flash TWRP again? As I mentioned I already have the 1GB system partition, so that shouldn't be an issue. It would be a nice two birds with one stone, saving my data and updating my obsolete ROM to a isorec TWRP+LOS 14.1 combo.
Lastly, this is the recovery you mentioned, right?: recovery-the.gangster-IsoRec-TWRP-3.1.0-0-i9100.zip
Click to expand...
Click to collapse
First, TWRP won't be flashed with Odin, it will be flashed with CM recovery that you already have, and yes i meant the one you mentioned.
Second, the contacts.db and mmssms.db won't take that much space, and anyway it's OK to copy them to internal sdcard, not obligated to external, and no need to access them, after you flash another ROM like LOS 14.1, you can re copy them back to their directories.
Third, if you flash the latest LOS 14.1, you can keep the iso-rec TWRP it won't be removed.
MigoMujahid said:
First, TWRP won't be flashed with Odin, it will be flashed with CM recovery that you already have, and yes i meant the one you mentioned.
Second, the contacts.db and mmssms.db won't take that much space, and anyway it's OK to copy them to internal sdcard, not obligated to external, and no need to access them, after you flash another ROM like LOS 14.1, you can re copy them back to their directories.
Third, if you flash the latest LOS 14.1, you can keep the iso-rec TWRP it won't be removed.
Click to expand...
Click to collapse
Okay, so I need to find an SD card reader then, to put the recovery on it. Or is there another way to get it on the phone?
By the way, thank you for taking your time and helping me, I'm really grateful!
N7Gabe said:
Okay, so I need to find an SD card reader then, to put the recovery on it. Or is there another way to get it on the phone?
By the way, thank you for taking your time and helping me, I'm really grateful!
Click to expand...
Click to collapse
No pb bro, you're welcome.
Yes, you will need to get the recovery in the phone somehow, or you can put your memory card in another phone and use the phone to put the recovery in the sdcard, then place it in your phone again.
That would be an alternative if you don't have a sdcard reader.
MigoMujahid said:
No pb bro, you're welcome.
Yes, you will need to get the recovery in the phone somehow, or you can put your memory card in another phone and use the phone to put the recovery in the sdcard, then place it in your phone again.
That would be an alternative if you don't have a sdcard reader.
Click to expand...
Click to collapse
I managed to get it on the phone and flashed it. The phone was plugged in to my pc, and I could acces my internal SD so I managed to back that up. But here's the thing, TWRP file manager showed my /data to be empty, and not long after, the phone just shut down. My battery is only a few months old, so that should not be the issue, and the phone was also charging from the PC.
After this shutdown, I had a very hard time to get into recovery, because the phone thinks the battery is dead. I couldn't start booting normally either. Only download mode was available, but it only said, it can't get into download mode, because the battery is low. (when I plug in the charger the phone shows 100% battery) I changed my battery to my old weak one, I managed to get into recovery with it, after multiple tries. (I think it had nothing to do with the battery but was lucky) Now I check my /data through adb and it shows empty aswell:
Code:
D:\Android\sdk\platform-tools>adb pull /data/data/com.android.providers.telephony/databases/mmssms.db
adb: error: remote object '/data/data/com.android.providers.telephony/databases/mmssms.db' does not exist
D:\Android\sdk\platform-tools>adb shell
~ # 
~ # ls
and-sec init.recovery.service.rc selinux_version
boot init.recovery.smdk4210.rc sepolicy
boot.txt init.recovery.usb.rc service_contexts
cache license sideload
charger mnt supersu
data proc sys
default.prop property_contexts system
dev recovery tmp
etc res twres
file_contexts sbin ueventd.rc
fstab.smdk4210 sdcard0 ueventd.smdk4210.rc
init sdcard1 usbotg
init.rc seapp_contexts
~ # cd data
/data # ls
/data # 
Do I have to mount it somehow maybe? (Oh and twrp always ask at start to mount sys in read-only or R/W. I always mounted it in R/W.) I'm afraid if I start moving in TWRP the phone will shut down as it always did. If I use adb or windows explorer to acces the phone it does not shut down.
N7Gabe said:
I managed to get it on the phone and flashed it. The phone was plugged in to my pc, and I could acces my internal SD so I managed to back that up. But here's the thing, TWRP file manager showed my /data to be empty, and not long after, the phone just shut down. My battery is only a few months old, so that should not be the issue, and the phone was also charging from the PC.
After this shutdown, I had a very hard time to get into recovery, because the phone thinks the battery is dead. I couldn't start booting normally either. Only download mode was available, but it only said, it can't get into download mode, because the battery is low. (when I plug in the charger the phone shows 100% battery) I changed my battery to my old weak one, I managed to get into recovery with it, after multiple tries. (I think it had nothing to do with the battery but was lucky) Now I check my /data through adb and it shows empty aswell:
Do I have to mount it somehow maybe? (Oh and twrp always ask at start to mount sys in read-only or R/W. I always mounted it in R/W.) I'm afraid if I start moving in TWRP the phone will shut down as it always did. If I use adb or windows explorer to acces the phone it does not shut down.
Click to expand...
Click to collapse
You should go to "mount" in TWRP, and tick "data" and "system", i said that already earlier.
MigoMujahid said:
You should go to "mount" in TWRP, and tick "data" and "system", i said that already earlier.
Click to expand...
Click to collapse
After I sent the message and before I read yours just now, I managed to mount, save and even make LOS run. So I was wrong, the battery is probably dead. I guess the lot of heat it produced while bootlooping killed the battery. I switched back to my old original wore out battery which is humpy and everything, but I managed to do everything with the phone. Now my problem is after I put back the .db files in their place, when the phone start it constantly crashes android.process.acore, the messaging app and the caller app. I think it might be a permission issue, but I have no idea how to fix it.
N7Gabe said:
After I sent the message and before I read yours just now, I managed to mount, save and even make LOS run. So I was wrong, the battery is probably dead. I guess the lot of heat it produced while bootlooping killed the battery. I switched back to my old original wore out battery which is humpy and everything, but I managed to do everything with the phone. Now my problem is after I put back the .db files in their place, when the phone start it constantly crashes android.process.acore, the messaging app and the caller app. I think it might be a permission issue, but I have no idea how to fix it.
Click to expand...
Click to collapse
Download ES file explorer from play store and grant root access for root explorer and set permissions to the 2 files as (rw- rw- ---) as described in screenshot, then reboot.
MigoMujahid said:
Download ES file explorer from play store and grant root access for root explorer and set permissions to the 2 files as (rw- rw- ---) as described in screenshot, then reboot.
Click to expand...
Click to collapse
This method worked with the contacts db, but not with the messages db. Actually I did not find any databases when I first copied it there, even made the databases folder. Thanks though, I'm almost done!
N7Gabe said:
This method worked with the contacts db, but not with the messages db. Actually I did not find any databases when I first copied it there, even made the databases folder. Thanks though, I'm almost done!
Click to expand...
Click to collapse
Ok, i seem to know the problem here, i looked at my own mmssms.db file and found it in this path:
/data/data/com.android.providers.telephony/databases/mmssms.db
(not the same path for the contacts.db file)
So you should move it there and add the same permissions that you added to the other file, that will do the job for you
MigoMujahid said:
Ok, i seem to know the problem here, i looked at my own mmssms.db file and found it in this path:
/data/data/com.android.providers.telephony/databases/mmssms.db
So you should move it there and add the same permissions that you added to the other file, that will do the job for you
Click to expand...
Click to collapse
This is the path you told me the first time, and this is where it doesn't work. That databases folder was not even there, until I made it. I don't even have any other files in the folder but the mmssms.db that I copied there.
N7Gabe said:
This is the path you told me the first time, and this is where it doesn't work. That databases folder was not even there, until I made it. I don't even have any other files in the folder but the mmssms.db that I copied there.
Click to expand...
Click to collapse
I don't know what is the problem...I've ran out of ideas here
At least you got your contacts back :silly:
MigoMujahid said:
I don't know what is the problem...I've ran out of ideas here
At least you got your contacts back :silly:
Click to expand...
Click to collapse
No problem, I got lucky, run a search in the data partition for mmssms.db and it appears that now it is located in /data/user_de/0/com.android.providers.telephony/databases. I backed it up, then overwrote it, fixed the permission, rebooted and now it seems to work, so all is well.
In the end I managed to not only save my data, but to fix my phone and even upgrade it to the latest LineageOS, thanks to you! I wish you a good life!
N7Gabe said:
No problem, I got lucky, run a search in the data partition for mmssms.db and it appears that now it is located in /data/user_de/0/com.android.providers.telephony/databases. I backed it up, then overwrote it, fixed the permission, rebooted and now it seems to work, so all is well.
In the end I managed to not only save my data, but to fix my phone and even upgrade it to the latest LineageOS, thanks to you! I wish you a good life!
Click to expand...
Click to collapse
Thanks for the tip, i have a marshmallow ROM right now, it seems that the location was changed in Nogut, I'll keep that in mind.
Have a good life too.

Categories

Resources