I've managed to softbrick my nexus 10 by trying to disable extra services (was getting about 1.5 hours battery life with media services running the processor 100% all the time). It worked wonderfully (no negative side effects, went back to 10+ hours with the screen on, or days on standby) until I reboot it and now it won't load past the moving colors (Android 4.4.3, unlocked and all that).
I have TWRP, I was hoping to backup everything possible via usb, but it seems it's incapable of doing so. ADB backup can't be done using TWRP since there's no unlock function (reaaal useful there, recovery mode that doesn't support backups) and adb pull fails if I try to pull everything since there are files and folders with invalid file names (who puts ":" in folder names? they should be shot), and I don't know specifically what to pull, I was just going to get everything put back what I found was missing that I needed. There's no room to do a backup onto the device, and since the N10 has to sd/microsd, well... Useless options are useless.
Is there anyway to just do a proper backup with TWRP over USB? Or is the "recovery" mode as useless as I think it is when it comes to backups? (I'm aware I can get the tablet back to working order if I disregard the data on it, this is a question about backing things up before doing so)
Edit: Also, I have a pro version of SkipSoft ToolKit, but unless you can actually load into the OS the toolkit can't do anything at all.
Just really frustrated with the lack of doing something as basic as copying files from one place to another. Been messing with this all morning.
Diet6 said:
I've managed to softbrick my nexus 10 by trying to disable extra services (was getting about 1.5 hours battery life with media services running the processor 100% all the time). It worked wonderfully (no negative side effects, went back to 10+ hours with the screen on, or days on standby) until I reboot it and now it won't load past the moving colors (Android 4.4.3, unlocked and all that).
I have TWRP, I was hoping to backup everything possible via usb, but it seems it's incapable of doing so. ADB backup can't be done using TWRP since there's no unlock function (reaaal useful there, recovery mode that doesn't support backups) and adb pull fails if I try to pull everything since there are files and folders with invalid file names (who puts ":" in folder names? they should be shot), and I don't know specifically what to pull, I was just going to get everything put back what I found was missing that I needed. There's no room to do a backup onto the device, and since the N10 has to sd/microsd, well... Useless options are useless.
Is there anyway to just do a proper backup with TWRP over USB? Or is the "recovery" mode as useless as I think it is when it comes to backups? (I'm aware I can get the tablet back to working order if I disregard the data on it, this is a question about backing things up before doing so)
Edit: Also, I have a pro version of SkipSoft ToolKit, but unless you can actually load into the OS the toolkit can't do anything at all.
Just really frustrated with the lack of doing something as basic as copying files from one place to another. Been messing with this all morning.
Click to expand...
Click to collapse
Do you still need help? What about mtp mounting? You can pull * for a whole folder
Why not adb sideload a new rom?
I don't think I can MTP mount a Nexus 10, at least not in recovery mode. What I ended up doing was buying a OTG usb drive and making a backup to that. Problem was it split the tar over 4 files, which corrupted them (or at least made them not work with 7zip or tartool) fortunately I was able to get them to work with cygwin enough to get the files I wanted. I didn't want to sideload a new rom until I had backed up certain application data just in case it removed it.
All in all, had to buy a OTG usb drive (I would have just bought a cable but all the stores around here had was this "Dane 16gb OTG drive". So 20 bucks later I had the files I needed. Still annoyed that you can't do a ADB backup from fastboot or recovery mode, it seems like those would be the best places because no system files are in use, but who knows maybe the developers know something I don't.
In summary:
TWRP recovery cannot confirm a ADB backup over USB. ADB backups can only be done from the operating system.
TWRP recovery mode can only backup to OTG (if your device supports it, Nexus 10 does), but if the backup is larger than 2gb it will split the file and you will need some form of linux to extract it.
ADB cannot copy every file in recovery mode over USB due to certain file names being invalid for NTFS (this is probably not a problem on other file system types), this is problematic since the "pull" command has no skip option, it just fails when it hits one of these files.
Well you can easily flash latest rwrp that does well on my Linux mount internal storage but another solution is just flashing a rom with abd sideload and the'the back up from pc the content
---------- Post added at 04:24 AM ---------- Previous post was at 04:23 AM ----------
Or that will just un brick your tablet
Diet6 said:
Still annoyed that you can't do a ADB backup from fastboot or recovery mode
Click to expand...
Click to collapse
adb doesn't work in fastboot mode, only recovery or Android itself.
Diet6 said:
In summary:
TWRP recovery cannot confirm a ADB backup over USB. ADB backups can only be done from the operating system.
Click to expand...
Click to collapse
Maybe because /data (not talking about /data/media) wasn't mounted?
Diet6 said:
TWRP recovery mode can only backup to OTG
Click to expand...
Click to collapse
Huh?
Diet6 said:
ADB cannot copy every file in recovery mode over USB due to certain file names being invalid for NTFS (this is probably not a problem on other file system types), this is problematic since the "pull" command has no skip option, it just fails when it hits one of these files.
Click to expand...
Click to collapse
That's NTFS' problem, not TWRP's.
beekay201 said:
1. adb doesn't work in fastboot mode, only recovery or Android itself.
2. Maybe because /data (not talking about /data/media) wasn't mounted?
3. Huh?
4. That's NTFS' problem, not TWRP's.
Click to expand...
Click to collapse
1. I was just covering that you can't actually do a ADB backup unless you have access to android OS, in case anyone else came across this. (I didn't know when I started, and it took awhile to find it said concretely anywhere)
2. I made sure everything was mounted, the issue is when you send a backup command over ADB it says the "Now unlock your device and confirm the backup operation" message in terminal which you can't do from recovery mode on the device, thus you cannot do a ADB backup command over TWRP (or other recovery modes I'd imagine).
3. I should have been more specific. TWRP can do a backup to the device itself (built in storage), SD card (if your device has one and you mount it), or a OTG (on the go) device via usb directly to media like a flash drive. It cannot issue a backup over USB to a computer.
4. Completely agree it's a NTFS issue, but it could be mostly avoided by allowing files that error to be skipped or renamed rather than terminating the process. (I understand that's on the android devs since pull is made by them, and I doubt they would care to improve the command for a file system I doubt they use). Again I mostly included that so if anyone else is trying to figure it out they can stop looking for "a way" and just accept it can't be done.
Ultimately Khaon is right in that sideloading a rom would have unbricked it and I could have done the ADB backup then, I just wasn't sure how that might affect the app data storage so I was looking for a way to back it up before doing that.
Diet6 said:
1. I was just covering that you can't actually do a ADB backup unless you have access to android OS, in case anyone else came across this. (I didn't know when I started, and it took awhile to find it said concretely anywhere)
2. I made sure everything was mounted, the issue is when you send a backup command over ADB it says the "Now unlock your device and confirm the backup operation" message in terminal which you can't do from recovery mode on the device, thus you cannot do a ADB backup command over TWRP (or other recovery modes I'd imagine).
3. I should have been more specific. TWRP can do a backup to the device itself (built in storage), SD card (if your device has one and you mount it), or a OTG (on the go) device via usb directly to media like a flash drive. It cannot issue a backup over USB to a computer.
4. Completely agree it's a NTFS issue, but it could be mostly avoided by allowing files that error to be skipped or renamed rather than terminating the process. (I understand that's on the android devs since pull is made by them, and I doubt they would care to improve the command for a file system I doubt they use). Again I mostly included that so if anyone else is trying to figure it out they can stop looking for "a way" and just accept it can't be done.
Ultimately Khaon is right in that sideloading a rom would have unbricked it and I could have done the ADB backup then, I just wasn't sure how that might affect the app data storage so I was looking for a way to back it up before doing that.
Click to expand...
Click to collapse
I'd just 'tar' what I wanted on the device and then pull that with adb.
Yeah, I just had no idea what I wanted. I'm not 100% familiar with how the system stores application data, I figured if I copy everything than anything I "miss" after I formated it I'll be able to just research where it was and dig in the backup and pull it out.
Yeah adb sideload a rom will only affect system partition thus your data would not have been modified in any way. So you are done with your issue?
Sent from my Xiaomi MI2s
Khaon said:
Yeah adb sideload a rom will only affect system partition thus your data would not have been modified in any way. So you are done with your issue?
Sent from my Xiaomi MI2s
Click to expand...
Click to collapse
Yes, sorry for the slow reply. I've completed my update, just wanted to follow up on everything I did incase the information is useful for anyone else new to this like I am.
Related
IN MY INFINITE WISDOM, I replaced my build.prop with the one from a Motorola Xoom in an attempt to get Sketchbook Pro to show up in the market. Now my tablet is boot looping.
I backed the original up in the same directory, as build.prop.OLD. If I could mount system and replace the file with a PC, I'd imagine that the tablet would work again. How could I do that?
However, THERE IS ANOTHER COMPLICATION! I used the 'Acer Phone Disabler' app to remove the telephony drivers, which means that I cannot flash a rom or the tablet will brick. I'm not sure what this means for Nandroid backups.
The tablet has the leaked stock 3.1 rom installed, it's rooted, and it has Clockworkmod recovery.
Thanks in advance for any help!
Oh god.
I used ADB to pull my build.prop.OLD, renamed it to build.prop, and pushed it back. Now... the tablet boots up, and it shows the Android "Welcome" screen. Clicking the only button available doesn't work. It just highlights as if it is selected, and doesn't do anything when I lift my finger up.
I DO have a Nandroid backup from several weeks ago of the same rom, but from BEFORE I removed the telephony drivers. I am only going to try restoring it as a last resort; does anyone have any ideas? Remember, flashing a rom would result in a brick because I used Acer Phone Disabler. Is a nandroid backup safe?
Thanks guys. I'm really hoping this tablet isn't too screwed.
I'm hoping someone else chimes in here but I am under the impressing that the nandroid backup would override any changes you could make as long as you don't break recovery. As far as my experience goes if you had a backup of your current configuration you could do an "advanced restore" and only restore your "system"
Sent from my A500 using Tapatalk
Restoring just system worked! My homescreen is back to stock but all my apps are still installed, so I don't really care. Thanks a bunch, I was so worried.
COOL!!!
Glad I could help.
Sent from my A500 using Tapatalk
Help needed for a boot loop
Well as said in the video, i reuse an existing thread about bootloop...
I'm stuck in a bootloop with an iconia A500... but let's look at the steps that got me there...
The First mistake was to answer yes to my friend who asked me to connect his Vodafone k3565 to his iconia A500, but as i read Android was linux based and i did use linux a lot as a student, i didn't even imagine it could go wrong...
Tablet was stating to run :
Android 3.1
Bernel 2.6.36.3-00009-9dddf6f2
Build 4.015.05-EMEA-CUS3
i did root with iconia root 1.3
then added Busybox and a terminal program.
reboot, try a SU and could access the devices
Here is the second mistake... i should have wondered how to restore to normal state before starting, because i don't have any SD card that suit the device ( mine are normal sized ones, you know.. Stamp sized :/ )
Then i got to the thread
http://forum.xda-developers.com/showthread.php?t=1058846&page=7
and i used an usb key to transfer it to the device, but before applying the files i took a look to them and found 3 of them would overwrite actual system files, so i did a backup of them :
/system/build.prop
/system/etc/apns-conf
/system/bin/rild
and looking at the build.prop i saw differences in the values of the one on the A500 and the one in the package so i decided to get only the missing lines from the new system.zip file and add them to the original file
And here is the 3rd mistake, and i guess the reason of the problem : i did that merge on a windows computer, and i fear it did add those pesky CRLF at the end of lines, turning my build.prop into a build.prob(lem).
I'm not sure, as i didn't check before it was too late.
rebooted and... boot loop, with 1 times out of 2, the little android with yellow triangle and exclamaition mark.
Cried, runned in circles, then looked on forums to find a solution.
Reboot with Power+Volume gives :
"Erasing cache before SD update...
SD update cmd:recovery
--update_package=sdcard:update.zip
Booting recovery kernel image"
Then i get the android with gears for a few seconds, then below him is a bar like the one in the android store when you download a file, then half a second later, again the exclaimation mark.
I also tried plugging a keyboard to hit the home key...
( in fact two : Logitech G110 and trust easy scroll silverline )
no difference, maybe because those are gaming keyboards and they arent loaded soon enough by the tab, or maybe it crashes before keyboard loading.
Tried then to install ADB using post
http://forum.xda-developers.com/showthread.php?t=1155664
hoping i could use the USB cable to put the backup files back in place but when i plug the device into the windows host, it recognises an unavailable USB MTP device, whose properties say "Acer iconia tab a500" in the "signaled bus description"(translated from french display, may be something else in english)
I manually force added the Acer ADB interface, but both the devices are unavailable to windows, with a warning sign, stating "this device cannot start (code 10)"
"Adb shell" answers "Error:device not found",which is expected, as windows can't see the devices properly
the strange thing is that, with USB plugged from A500 to PC, the Android with exclaimation stays forever, while without the cable, the system boot-loops
so i'm at this point :
i have a boot looping device, and the backup of the modified files on an USB key, and no way to put them back on device.
I found on the forums a lot of different .imgs that could be put on the /system to reload the device but none with EMEA-CUS3. So if i overwrite the files, i can't go back
I read you need a SD card to patch the device but not all of them work...
And my only computer with a SD slot uses a big one, not micro one, so i also need an adapter to write on the sd card.
Is someone near me (belgium/postcode 4000) having a SD ward working with the device who could lend it or help me doing the job ?
else
i saw in a nearby store ad "Sigma SDHC 4Go" or "Sigma SDHC 8Go", with apparently an adaptor for a normal sized SD slot, can anyone confirm it works or it don't work for sure ?
else
Can anyone tell me an SD card know to work, and being sold currently with an adapter so i have a chance to find one in a store near me ?
Is there a way to create an update.zip that will only update the files i did overwrite ?
if not, has someone an image for the same system i have ?
Well... lots of questions, but i'm very worried, especially as the device is not mine and not working anymore atm.
-> update
Looking closer at the modem (Vodafone k3565) it has a trap that says "SD card" so i guess i won't need an adapter... still need the reference of a SD card known to work for the restoring.
[bump] and more :
this thread http://forum.xda-developers.com/showthread.php?t=834144
lists working SD cards, but don't tell with which device. i'd take the guess it applies to the iconia A500 and take the list to the shop to see if anyone is available...
Did you install the Acer USB driver, found here? http://www.acer.co.uk/ac/en/GB/content/drivers
You might need to go into device manager after installing and right click/update drivers on the tablet, then manually direct it to the Acer driver folder. That's what I did, then ADB worked.
Haemdaer said:
Well as said in the video, i reuse an existing thread about bootloop...
I'm stuck in a bootloop with an iconia A500... but let's look at the steps that got me there...
The First mistake was to answer yes to my friend who asked me to connect his Vodafone k3565 to his iconia A500, but as i read Android was linux based and i did use linux a lot as a student, i didn't even imagine it could go wrong...
Tablet was stating to run :
Android 3.1
Bernel 2.6.36.3-00009-9dddf6f2
Build 4.015.05-EMEA-CUS3
i did root with iconia root 1.3
then added Busybox and a terminal program.
reboot, try a SU and could access the devices
Here is the second mistake... i should have wondered how to restore to normal state before starting, because i don't have any SD card that suit the device ( mine are normal sized ones, you know.. Stamp sized :/ )
Then i got to the thread
http://forum.xda-developers.com/showthread.php?t=1058846&page=7
and i used an usb key to transfer it to the device, but before applying the files i took a look to them and found 3 of them would overwrite actual system files, so i did a backup of them :
/system/build.prop
/system/etc/apns-conf
/system/bin/rild
and looking at the build.prop i saw differences in the values of the one on the A500 and the one in the package so i decided to get only the missing lines from the new system.zip file and add them to the original file
And here is the 3rd mistake, and i guess the reason of the problem : i did that merge on a windows computer, and i fear it did add those pesky CRLF at the end of lines, turning my build.prop into a build.prob(lem).
I'm not sure, as i didn't check before it was too late.
rebooted and... boot loop, with 1 times out of 2, the little android with yellow triangle and exclamaition mark.
Cried, runned in circles, then looked on forums to find a solution.
Reboot with Power+Volume gives :
"Erasing cache before SD update...
SD update cmd:recovery
--update_package=sdcard:update.zip
Booting recovery kernel image"
Then i get the android with gears for a few seconds, then below him is a bar like the one in the android store when you download a file, then half a second later, again the exclaimation mark.
I also tried plugging a keyboard to hit the home key...
( in fact two : Logitech G110 and trust easy scroll silverline )
no difference, maybe because those are gaming keyboards and they arent loaded soon enough by the tab, or maybe it crashes before keyboard loading.
Tried then to install ADB using post
http://forum.xda-developers.com/showthread.php?t=1155664
hoping i could use the USB cable to put the backup files back in place but when i plug the device into the windows host, it recognises an unavailable USB MTP device, whose properties say "Acer iconia tab a500" in the "signaled bus description"(translated from french display, may be something else in english)
I manually force added the Acer ADB interface, but both the devices are unavailable to windows, with a warning sign, stating "this device cannot start (code 10)"
"Adb shell" answers "Error:device not found",which is expected, as windows can't see the devices properly
the strange thing is that, with USB plugged from A500 to PC, the Android with exclaimation stays forever, while without the cable, the system boot-loops
so i'm at this point :
i have a boot looping device, and the backup of the modified files on an USB key, and no way to put them back on device.
I found on the forums a lot of different .imgs that could be put on the /system to reload the device but none with EMEA-CUS3. So if i overwrite the files, i can't go back
I read you need a SD card to patch the device but not all of them work...
And my only computer with a SD slot uses a big one, not micro one, so i also need an adapter to write on the sd card.
Is someone near me (belgium/postcode 4000) having a SD ward working with the device who could lend it or help me doing the job ?
else
i saw in a nearby store ad "Sigma SDHC 4Go" or "Sigma SDHC 8Go", with apparently an adaptor for a normal sized SD slot, can anyone confirm it works or it don't work for sure ?
else
Can anyone tell me an SD card know to work, and being sold currently with an adapter so i have a chance to find one in a store near me ?
Is there a way to create an update.zip that will only update the files i did overwrite ?
if not, has someone an image for the same system i have ?
Well... lots of questions, but i'm very worried, especially as the device is not mine and not working anymore atm.
-> update
Looking closer at the modem (Vodafone k3565) it has a trap that says "SD card" so i guess i won't need an adapter... still need the reference of a SD card known to work for the restoring.
Click to expand...
Click to collapse
The reason "some" SD cards don't work is down purely to formatting. Normally, reformatting them in an Android phone sorts it out. Not always, but normally. Don't worry about the GEN3 stuff too much, it's just regional variations anyway... More important to get the tab working again, no?
Yes i did ( on 2 different computers, just to be sure )...
and still the device is not recognised as "adb device".
Windows shows a "USB MTP Device"
Tried to manually add the "ACER Composite ADB Interface" and "ACER Fastboot Interface" to the installed peripherals, it shows with yellow exclaimation mark, never shows up running.
Without any useable answer about one week later, i did buy a Traxdata 2Gb SD card with adapter ( the cheapest i found with an adapter from micro SD to normal SD ) and flashed with the Emea_Gen3 ROM from http://forum.xda-developers.com/showthread.php?t=1113878.
Now the tablet works, but is telling me 4.010.42-COM-GEN1 instead of the previous 4.015.05-Emea-Cus3.
Seems to work correctly, so i go on with the modem connexion.
I am sick of MTP USB connection and I want to know if there's any way to use normal mass storage.
Today I tried to copy nandroid backups to my PC and I can't.. It just won't copy my files. (Windows 7)
adb pull will recursively grab the contents of a remote folder if you use a trailing /
e.g.
C:\foo> cd MyBackups
C:\foo\MyBackups> adb pull /sdcard/TWRP/BACKUPS/device-serial-num/
You may need to move your CWM/TWRP backups out of /data/media and into /data/media/0 if you are using lightly-rooted stock (as ro.secure = 1 and therefore the adb shell does not get root privs)
Other alternatives are mounting a drive or USB stick via OTG and shuttling files.
I use Win 7 Pro x64, and it is my impression that MTP seemed to behave better after I completely uninstalled the Google & XDA Universal Naked USB drivers, and used only the Asus N7 USB driver for everything (with a .inf file hack). TBH, though, I don't know why that would be the case though, as a generic MS driver handles the MTP connection. Perhaps 4.2.2 fixed something, I dunno - MTP seems to work OK for me now.
good luck
Thank you, that helped.
I also have related question for you, I had stock rom and now I am using PA ROM. Everything what saved after flashing PA is on storage/sdcard0 but there is also folder storage/sdcard0/0 where all stock rom data are... why? and can i merge them?
(also apps access only sdcard0, so for example Gallery doesn't see pics from sdcard0/0)
Tomaco said:
Thank you, that helped.
I also have related question for you, I had stock rom and now I am using PA ROM. Everything what saved after flashing PA is on storage/sdcard0 but there is also folder storage/sdcard0/0 where all stock rom data are... why? and can i merge them?
(also apps access only sdcard0, so for example Gallery doesn't see pics from sdcard0/0)
Click to expand...
Click to collapse
(TL;DR I don't know)
I've seen similar reports before, but I haven't experienced it myself, nor have I followed the issue. Do some more searching on this forum, I guess. I don't know if it's custom recoveries that have been causing that behavior, or if it has something to do with the ROMs being flashed, or whether it is a 4.1.x/4.2.x multi-user conversion issue. There probably should be some traffic in the custom recovery threads about it.
I've been using TWRP and sticking with lightly-rooted stock and haven't observed such behavior. About the closest thing that I experienced was that initially TWRP put its stuff at /data/media/TWRP, but after I manually moved it to /data/media/0/TWRP, it seemed happy enough with that (and started putting new Nandroid backups into the moved folder location). That makes it easy enough to get backup copies off the tablet using MTP, even though it is irritating that timestamps don't get preserved doing things either of these ways.
good luck
For some reason I cannot move files via Windows 7 file explorer to the Nexus. I can and have done this on every other mobile device that I've had before. What's the difference? Why can't I place pics and videos on it?
A few more details would be super helpful to give you a good answer. Start with if you are running a custom ROM and what if anything you have tried to solve the problem.
When you plug in your usb look under settings - storage and see if there is the option to mount storage.
Note 2 - Nexus 7 - Charge - Player 5.0 - Fascinate
<><><><><><><><><><>
Read twice, flash once
For some reason, now it's letting me even though I didn't change anything. Mods can delete this if they want. And thank you ezas for your reply.
Glad you got it sorted out.
Note 2 - Nexus 7 - Charge - Player 5.0 - Fascinate
<><><><><><><><><><>
Read twice, flash once
Brian Gove said:
For some reason, now it's letting me even though I didn't change anything. Mods can delete this if they want. And thank you ezas for your reply.
Click to expand...
Click to collapse
In my limited experience using MTP (rooted stock N7 4.2.2 + Win 7 x64), what seems to work well is:
- copying files FROM the N7 which were already in the /sdcard mount point when the N7 last booted,
- copying files TO the N7 into a folder which already existed inside the /sdcard mount point when the N7 last booted.
(I should also point out that moving files this way seems to be 5-7 times faster than using "adb push" or "adb pull")
What seems to only work sporadically is trying to copy or write to things which were "recently created" in the /sdcard mount point. For instance, if you generate a large set of files using Android, you won't be able to find them from the PC until a seemingly random ? amount of time later. Similarly, if you create a folder on the N7 (let's say by using a file manager) with the intent of pushing some files there from the PC, you won't see that folder show up in a reasonable amount of time.
This behavior actually does make sense - in principle, it is impossible to allow instantaneous write access to a file system from two independent hosts without running risks of filesystem corruption. In previous versions of Android, external SD cards could be accessed using USB Mass Storage drivers, but only exclusively by either the Android device or the PC - never at the same time. The SD card had to be unmounted from Android in order to be seen by the PC.
But, what is curious is the delays involved. I wanted to do something similar to this the other day (copying a nandroid backup from the PC to a "new" folder on the N7), and thought that by correctly disconnecting from the PC followed by reconnecting to the PC would allow the newly-created folder to "show up" via MTP on the PC. No such luck however; I needed to reboot the N7 for that to happen.
Bottom line is that MTP will work (and quickly, too! - better than 10 MB/sec) - but only with the above limitations in mind. When in doubt, reboot the N7.
When I plugin my Samsung Galaxy J7 Prime and then select recovery module and it show as connected and then I select android data recovery option and then select recover documents only and then click next. Then it show and detected device model, downloading package and it went like that till 99% uncertain if it hit 100% or not and then it caused my device to reboot and after it reboot now it is asking for a password to start up device but I tried device screen password, google account password and samsung account password but all didnt work. Thus it shows have 7 attempts left before factory reset itself.
The boot up looks a bit different from normal too, unsure if it is coming through a different type of boot and if there is a way to reverse to how it was earlier?
In recovery mode it shows in recovery log pid 2064 ran. where first line filesystem table code was;
0/ efs ext4/ dev/block/platform/1354000.dwmmc0/by-name/EFS(/dev/block/mmcblk0p3) 0
and in following
#ls /cache/recovery
ksmg
-rw------root root 8190724 2022-04-02 11:19 last_ode_dumpstate_err_check_password.log
From what I could see further in log it seems like maybe dr fone tried to root phone since I see files seem to have been overwritten probably as same file name shown where earlier recorded in time stamp as either 2017 or 2008 and underneath that dst is run with today tim stamp.
What would be method to solve to get back to normal working state without any data loss?
It seems when check via dr fone transfer showing as mem capacity 2797mb and 1362mb used whereas it should show as 32Gb, also when start up it says Enter your password to start up your device but I am certain I enter correct passwords but it is not verifying. Also in recovery mode it shows No support single sku supported api:3.
And when try backup option no files come up on scan does that mean the Dr fone recovery package that it installed wiped out the data? Or is it like in another different boot system for recovery? How to solve this problem?
Also any backup software you think could backup stuff before applying any drastic fixes
I think your phone internal storage is corrupted because of Dr. Fone and this is caused by the data encryption inside the phone and I think that it requires the encryption password, and to solve this problem, you must flash a modified recovery like TWRP or CWM and then pull all the data by making a MOUNT of the internal storage it will only works on old Android version 6.x or 7.x but you can try
My android is 6.0.1 so I think it should work, do you have any video tutorials or a thread with stepwise instructions to get twrp or cwm to backup current data and later restore?
Also any idea if use the dr fone repair device feature it might fix?
Dr.Fone only one thing do transfer WhatsApp chat between android and iOS all else features not work perfect so try another way, ask google how mount internal storage on android phones by twrp it’s easy and not need a tutorial just flash a custom recovery and don’t let device to boot enter recovery mode immediately and go to mount and press mtp or mount storage
Looks like the device name has got renamed as well best try to see if have a file explorer or manager for android so can see if files still intact? Any pc softwares that can be used to clarify without need to unlock screen since it is asking for a pass saying Enter your password to start up your device but I am certain I enter correct passwords but it is not verifying.
If the files are intact then I can try twrp or odin cf root flashing to see if can flash home version file so files possibly stay intact. Or if they are anyways not then will try factory reset via recovery mode and then will need recommendation of good software to recover data for free
Any ideas?
That app is trashware. Do Not use!
If a factory reset doesn't clear it you'll need to reflash the stock rom.
The data is lost... that's my opinion.
Always backup all critical data redundantly to at least two hdds that are physically and electronically isolated from each other and the PC... or you will lose data, eventually!
NEVER encrypt a data backup drive.
Do copy/paste file transfer, verify file size and folder count match. Test for readability.
NEVER clone music data bases, copy/paste only.
Do not use compression or apps like SmartSwitch to backup critical data, they can fail you miserably.
You can never have too many backup data drive. Avoid using flash memory; quality hdds have better memory retainment. Store in more than one location. Near lightning strikes can wipe them; a metal earth grounded box or safe is best.
blackhawk said:
That app is trashware. Do Not use!
If a factory reset doesn't clear it you'll need to reflash the stock rom.
The data is lost... that's my opinion.
Always backup all critical data redundantly to at least two hdds that are physically and electronically isolated from each other and the PC... or you will lose data, eventually!
NEVER encrypt a data backup drive.
Do copy/paste file transfer, verify file size and folder count match. Test for readability.
NEVER clone music data bases, copy/paste only.
Do not use compression or apps like SmartSwitch to backup critical data, they can fail you miserably.
You can never have too many backup data drive. Avoid using flash memory; quality hdds have better memory retainment. Store in more than one location. Near lightning strikes can wipe them; a metal earth grounded box or safe is best.
Click to expand...
Click to collapse
Can you recommend a free pc software that could possibly backup device in current state? Or a free pc software that could do data recovery without need to root phone so if I do go ahead with flash and it wipes data or i do factory reset then I could try to get backup data.
NW_Work said:
Can you recommend a free pc software that could possibly backup device in current state? Or a free pc software that could do data recovery without need to root phone so if I do go ahead with flash and it wipes data or i do factory reset then I could try to get backup data.
Click to expand...
Click to collapse
Not on an unrooted phone. You can try this.
If you used Drfone it has likely already encrypted the data with their own encryption key.
Hopefully some of your data is backed up somewhere else because this is a dead horse... I believe.
I be more concerned about salvaging the phone at this point. It's a tough lesson from the U of hard knocks... don't repeat it. Sorry.
I have a Samsung Galaxy Tab 10.1" SM-P580 and started working to root it so I could install more apps using a micro SD card. It was a long time ago with Android 7 or so and a while back I thought I would upgrade so I tried upgrading it to Android 11 and Lineage 18.1 and bare bones Google apps. This has been only partially successfully as the system runs but I cannot install any apps at all and have been unable to make any further progress. So I am looking to go back to the drawing board here. What recommendations do you have with regard to what to use that will allow me to install more apps? Thank you very much!
JR1979 said:
I have a Samsung Galaxy Tab 10.1" SM-P580 and started working to root it so I could install more apps using a micro SD card. It was a long time ago with Android 7 or so and a while back I thought I would upgrade so I tried upgrading it to Android 11 and Lineage 18.1 and bare bones Google apps. This has been only partially successfully as the system runs but I cannot install any apps at all and have been unable to make any further progress. So I am looking to go back to the drawing board here. What recommendations do you have with regard to what to use that will allow me to install more apps? Thank you very much!
Click to expand...
Click to collapse
I assume you got the basic stuff out of the way - unlocked bootloader, installed TWRP, etc.
Did you install a Gapps package?
If you prefer something more vanilla, without the LineageOS customizations, you can try an Android GSI, which is like turning your device into a Pixel tablet. Check out my guide here.
JR1979 said:
I have a Samsung Galaxy Tab 10.1" SM-P580 and started working to root it so I could install more apps using a micro SD card. It was a long time ago with Android 7 or so and a while back I thought I would upgrade so I tried upgrading it to Android 11 and Lineage 18.1 and bare bones Google apps. This has been only partially successfully as the system runs but I cannot install any apps at all and have been unable to make any further progress. So I am looking to go back to the drawing board here. What recommendations do you have with regard to what to use that will allow me to install more apps? Thank you very much!
Click to expand...
Click to collapse
There are differences between Android 7,8,9 and now, especially eg.the use of sd-cards and permissions for users in general. Maybe you have to check such things as "Allow Installing apps from unknown ressources" in Settings, or you ckeck magisk modules that could help.
abagm said:
There are differences between Android 7,8,9 and now, especially eg.the use of sd-cards and permissions for users in general. Maybe you have to check such things as "Allow Installing apps from unknown ressources" in Settings, or you ckeck magisk modules that could help.
Click to expand...
Click to collapse
Thanks for the input. I have it upgraded to Android 11. Yhe unknown resources shouldn't matter AFAIK, in this case, as I am only trying to install via Play Store. I was trying to work with Magisk - I have it installed. I was going to try the ExSD module but I haven't been able to add it.
V0latyle said:
I assume you got the basic stuff out of the way - unlocked bootloader, installed TWRP, etc.
Did you install a Gapps package?
If you prefer something more vanilla, without the LineageOS customizations, you can try an Android GSI, which is like turning your device into a Pixel tablet. Check out my guide here.
Click to expand...
Click to collapse
Thank you. I will look into that. I will look into what the differences are between that and LineageOS. Question: will the pen/stylus work under this configuration? Thank you again.
JR1979 said:
Thank you. I will look into that. I will look into what the differences are between that and LineageOS. Question: will the pen/stylus work under this configuration? Thank you again.
Click to expand...
Click to collapse
In theory, yes - because GSIs are meant to be used with the stock kernel, and the system image doesn't have to have any specific hardware support.
LineageOS is built from AOSP, with added tweaks and customizations. I used it for a while, but grew tired of the Magisk issues I was having (PHH builds have built in SuperSU) so I just went straight vanilla with GMS.
So I looked at your guide and decided to give it a shot. With Multidisabler, when I tried pushing that to the tablet with sideload, it failed. I have also been unable to move system.img to the tablet. I'm at a loss. I know I am missing something here but just can't figure out what I am doing wrong. I just want to get this tablet up and running with Android and being able to use the 400GB SD card.
Thanks.
JR1979 said:
So I looked at your guide and decided to give it a shot. With Multidisabler, when I tried pushing that to the tablet with sideload, it failed. I have also been unable to move system.img to the tablet. I'm at a loss. I know I am missing something here but just can't figure out what I am doing wrong. I just want to get this tablet up and running with Android and being able to use the 400GB SD card.
Thanks.
Click to expand...
Click to collapse
Does MTP work for you in TWRP? ADB sideload is only for installing zips from your computer; the correct command to send files to device storage is adb push. Still, if you're able to get storage access over USB in TWRP just move the files that way because it's simpler.
I'm honestly not sure if the multidisabler is necessary when using custom firmware or GSIs. I think most likely not.
V0latyle said:
Does MTP work for you in TWRP? ADB sideload is only for installing zips from your computer; the correct command to send files to device storage is adb push. Still, if you're able to get storage access over USB in TWRP just move the files that way because it's simpler.
I'm honestly not sure if the multidisabler is necessary when using custom firmware or GSIs. I think most likely not.
Click to expand...
Click to collapse
Sorry - I just saw this response from you. So MTP is enabled but my laptop was unable to see the tablet. I connected the SD card to my laptop and placed the system.img file on it and then dropped the SD card back into the tablet. I was able to see it in the File Manager. As you said to, I wiped /system and flashed the system.img file. It showed "[IMAGE FLASH COMPLETED]". But when I went to reboot from the main TWRP menu, it said there was no OS installed and asked if I was sure if I wanted to reboot. So I took a gamble and selected Reboot and System again. And I guess I lost on the gamble. It now just loops on the "Samsung Galaxy Tab A with S Pen" splash screen. Well, game over... for tonight.
JR1979 said:
Sorry - I just saw this response from you. So MTP is enabled but my laptop was unable to see the tablet. I connected the SD card to my laptop and placed the system.img file on it and then dropped the SD card back into the tablet. I was able to see it in the File Manager. As you said to, I wiped /system and flashed the system.img file. It showed "[IMAGE FLASH COMPLETED]". But when I went to reboot from the main TWRP menu, it said there was no OS installed and asked if I was sure if I wanted to reboot. So I took a gamble and selected Reboot and System again. And I guess I lost on the gamble. It now just loops on the "Samsung Galaxy Tab A with S Pen" splash screen. Well, game over... for tonight.
Click to expand...
Click to collapse
Don't worry about the No OS warning, I get the same thing on my Tab A after installing a GSI.
You formatted data, yes?
You did NOT wipe /boot or /product I hope?
Something I noticed with the LineageOS GSIs is that the securized ones bootlooped, and I had to flash one of the pre-rooted builds. Can you link the image you tried to flash?
As a test to ensure a GSI runs properly, download one of the Android Developer Preview GSIs and try installing that. Let me know how it goes.
I didn't wipe /boot or /product.
I did format data.
I used the system.img from the aosp_arm64-exp-T2B2.221216.006-9443277-e508d63f.zip file on this page, from the Android Developer Preview GSIs: https://developer.android.com/topic/generic-system-image/releases
I'm guessing I didn't select the right build ?
Thanks again!
JR1979 said:
I didn't wipe /boot or /product.
I did format data.
I used the system.img from the aosp_arm64-exp-T2B2.221216.006-9443277-e508d63f.zip file on this page, from the Android Developer Preview GSIs: https://developer.android.com/topic/generic-system-image/releases
I'm guessing I didn't select the right build ?
Thanks again!
Click to expand...
Click to collapse
I also just tried the system.img from gsi_gms_arm64-exp-T2B2.221216.006-9443277-12a8e193.zip file. I get the same results - the splash screen loop.
JR1979 said:
I also just tried the system.img from gsi_gms_arm64-exp-T2B2.221216.006-9443277-12a8e193.zip file. I get the same results - the splash screen loop.
Click to expand...
Click to collapse
And so I tried the system.img files from the 2 zip files that are in the Android 13 (stable) folder:
aosp_arm64-exp-TP1A.220624.014-8819323-996da050.zip
gsi_gms_arm64-exp-TP1A.220624.014-8819323-8a77fef1.zip
Neither of these work. I still get the splash screen boot loop.
One thing I noticed is when I wipe system, it shows:
========================================
Updating partition details...
...done
Full SELinux support is present.
MTP Enabled
Failed to mount '/system_root' (Invalid argument)
Formatting system using mke2fs...
Done.
Updating partition details...
...done
=========================================
It's almost tablet frisbee time.