Hello xda members,
I have a 6.0.1 GALAXY S5 with a broken screen, and used adb to make a TWRP backup.
Next, I tried using adb to retrieve Android ID in TWRP, and I get sh/bin/ not found error.
Nandroid manager successfully decompressed the backup, but it crashes when looking for the Android id.
Is there any method to find out the id of my broken phone, I only have access to the backup.
Related
We are a large urban school district located in southern California that will be soon be distributing approximately 11,000 android tablets to our first grade classrooms. The biggest challenge we’ve had with this project so far is coming up with a way to quickly and reliably clone the devices with all the apps and settings. The approach we’ve been attempting to take is the same as how we would handle PC’s by creating a master image that then gets copied to all the other devices.
Our first attempt at doing this was by using adb backup/restore. This process was less than ideal as it didn’t copy all the settings/preferences that we wanted and still required a lot of manual configuration to get the devices in to our ideal state. The bigger problem we had here was that sometimes it would just hang during the restore. Most of the time it did work but we’ve run in to this restore problem enough that we need something more reliable.
So our current cloning method is using Clockworkmod Recovery. Basically we flash CWM on to the device, make our backup, copy that backup to the destination devices and restore it with CWM. Seems to work great. And it copies everything on the devices so there’s virtually no manual configuration that needs to be done.
However there’s a few caveats with this process. At first we found that it was also cloning the MAC address which of course caused havoc on our wireless network. Through a whole lot of trial and error I found that if I delete /data/nvram/RestoreFlag from the data backup tar the MAC address no longer gets cloned. Thought we were good, but…
The next problem we found when attempting to enroll the devices in to our MDM system. They end up replacing each other because they all show the same UDID and GUID. The MDM app is installed in the backup image but we are waiting until after it is restored to complete the enrollment. I’m not sure if the UDID and GUID is something specific to the MDM or if that’s a global Android thing.
So does anyone know if there something else I can delete from the backup to prevent this? This also raises the question, are there any other items in a CWM backup that should not be copied between devices? Or is there a better method we could use to clones the devices?
The device we are currently using is a Lenovo A1000 (MTK MT8317). After creating the backup I’ve been removing the system and cache tars entirely and only the file mentioned above from within the data tar. So the only parts that get restored are data and boot. Any suggestions are welcome.
ttttttttttttttttt said:
We are a large urban school district located in southern California that will be soon be distributing approximately 11,000 android tablets to our first grade classrooms. The biggest challenge we’ve had with this project so far is coming up with a way to quickly and reliably clone the devices with all the apps and settings. The approach we’ve been attempting to take is the same as how we would handle PC’s by creating a master image that then gets copied to all the other devices.
Our first attempt at doing this was by using adb backup/restore. This process was less than ideal as it didn’t copy all the settings/preferences that we wanted and still required a lot of manual configuration to get the devices in to our ideal state. The bigger problem we had here was that sometimes it would just hang during the restore. Most of the time it did work but we’ve run in to this restore problem enough that we need something more reliable.
So our current cloning method is using Clockworkmod Recovery. Basically we flash CWM on to the device, make our backup, copy that backup to the destination devices and restore it with CWM. Seems to work great. And it copies everything on the devices so there’s virtually no manual configuration that needs to be done.
However there’s a few caveats with this process. At first we found that it was also cloning the MAC address which of course caused havoc on our wireless network. Through a whole lot of trial and error I found that if I delete /data/nvram/RestoreFlag from the data backup tar the MAC address no longer gets cloned. Thought we were good, but…
The next problem we found when attempting to enroll the devices in to our MDM system. They end up replacing each other because they all show the same UDID and GUID. The MDM app is installed in the backup image but we are waiting until after it is restored to complete the enrollment. I’m not sure if the UDID and GUID is something specific to the MDM or if that’s a global Android thing.
So does anyone know if there something else I can delete from the backup to prevent this? This also raises the question, are there any other items in a CWM backup that should not be copied between devices? Or is there a better method we could use to clones the devices?
The device we are currently using is a Lenovo A1000 (MTK MT8317). After creating the backup I’ve been removing the system and cache tars entirely and only the file mentioned above from within the data tar. So the only parts that get restored are data and boot. Any suggestions are welcome.
Click to expand...
Click to collapse
You can try use adb from Android SDK but this method needs root
We did initially try adb but it was inconsistent during the restore phase. Sometimes it would just stop in the middle and never complete. Didn’t try it on a rooted device. So maybe that would have helped…
Anyhow I found the solution to my immediate problem. Figured out what our MDM vendor refers to as the UDID is really the Android_ID. So by deleting that row from the settings database in our master backup image it’ll generate a new one the first time the OS starts after restoring with CWM.
I’m still a little concerned we’re going to find other issues cause by this cloning method later on but I guess we’ll just have to roll with the punches as they come.
In case someone else ever needs to clone devices like this and in the interest of sharing here’s the basic steps we’re following.
1.) Setup the master device as you like with all the apps and settings.
2.) Install Clockworkmod Recovery on to the master device
3.) Boot into CWM Recovery
4.) Mount /data and connect to adb
5.) Delete /data/nvram/RestoreFlag (this step prevents duplication of MAC address)
6.) Using sqlite open the database (this prevents duplication of Android_ID): \data\data\com.android.providers.settings\databases\settings.db
execute: delete from secure where name='android_id';
7.) unmount /data
8.) Create a backup
9.) Boot the device back in to normal mode and copy the clockworkmod folder to your computer. This the backup image you’ll restore on the other devices.
10.) [OPTIONAL] I deleted the system and cache backup files from this folder and also removed them from the nandroid file. There didn’t seem to be anything in these we cared about so removing those speeds up the restore process.
Once you have the backup image here’s how to restore it on the other devices:
1.) Install CWM Recovery
2.) Copy the clockworkmod folder from your computer on to the device
3.) Boot in to CWM Recovery
4.) Restore the backup
5.) Reboot the device back in to normal mode
6.) [OPTIONAL] Complete MDM enrollment
Sorry for the thread grave dig, but thanks for posting info on how to do this. I have attempted cloning in the past and ran into similar issues. My question - is this process the same for Android Lollipop 5.0/5.1? I have some Lenovo K3 Notes I'd like to deploy and cloning would save a lot of time.
Haven’t had the need to do any devices running 5.x versions so can’t say for sure. I would imagine a similar process would work.
But I will provide a bit of an update. Our initial deployment of 11,000 Lenovo A1000 devices have been out in the field since February/March of 2014 and no trouble has come to light using this cloning method. These devices run 4.1.2
Sometime around May 2014 we did another round that was about 300 Lenovo A3000 devices. Don’t have one of these handy and I don’t remember the exact Android version but it was 4.x something.
Then starting in October 2014 we put out another 9000 or so Lenovo A3500 devices. These run 4.4.2
All around so far so good.
For the A3000 and A3500 there were two changes to the process. For step 5 in creating the backup I had to clear the entire nvram directory instead of just the one file. I don’t remember what exactly but there was something undesirable getting copied over. The result of clearing this directory is the first boot after the restore takes a little longer as each app runs through the “update” process at startup. The second change was I could not get CWM to backup and restore to/from the internal memory so instead did it from a micro-sd card. This ended up speeding up the restore process since we didn’t have to copy the backup to each device and instead just moved the sd card with the files already there.
this should be pinned in android dev
also sorry for grave digging? except this should be a maintained topic. why isnt this an ongoing thread?
Hello,
I recently got a new phone OnePlus3 and trying to move my old messages from viber to the new one. The application doesn't support this process so I'm using a backup of the two applications along with the help from Android Backup Extractor. The process is described in the web so a google search would provide some more information.
The problem lies on the adb backup command as the package which is extracted from the device is kinda empty.
The old phone is a Nexus 4 with stock Android (rooted) version 5.1.1. The commands I'm using are:
Code:
adb backup com.viber.voip -f ./viber-old.ab
The resulting file is 54 bytes in size and when I unpack it with Android Backup Extractor it's an empty tar file.
I've tried with adb version matching the one on the phone (version 32) and with latest (36) downloaded from the android SDK. I've also tried setting a password for backups and not use empty one.
Since I've been trying with no success I tried on OnePlus3 and on Nexus 5X with no results either. The final size might be different but it's the same issue either 0 bytes or 54 bytes. (which includes just the manifest file). Previously around X-mas I have done the process successfully and moved my messages from Nexus 4 to my Nexus 5X so it's either a new permission policy in Android or Viber application doesn't allow backups?
Happy to debug further if one has some suggestion.
Thanks
The backup to Google Drive option doesn't work to restore on another device? Seems silly...
https://www.youtube.com/watch?v=anMx7W2-gLk
Truth to be told I didn't try that. I'll give it a go when at home - thanks
Sent from my Nexus 5X using Tapatalk
Hi everyone, forgive me for my bad english...in this day i'm freaking out because it happend an unexpected thing. 4 days ago in the evening i looked that was an error message about whatsapp in the home screen, then i open the app and appeared that chat list got problem and to solve that i need to restore backup or i get lost chat. The device was connected to wifi house, but i had whatsapp backup on my phone. I searched on internet and on official whatsapp page i red it was possible as an error. To solve that need to restore last backup. I done it but while the loading has started, after a few minutes the devices shut down and reboot. It's arrived to the logo of the ROM and then shut down again and reboot. i undestand it was a bootloop. Two years ago i install android kitkat because the device can't received android 4.4 and i don't want stay with 4.3. Everything fine. After an year the device goes in the bootloop, but i don't know why, so i decided to format data ad restore kitkat again. Before that i can transfered some data because i saw that if device was connected on the pc it not gone in bootloop. This year another problem but more little. The device sometimes reboots so i do a backup with titanium backup and then wipe everything including internal storage because on the boot after flashing the ROM the device can't memorized anything. In that occasion i don't reboot the device because i wiped internal storage so everything. Connected usb-device to the phone, copy gapps, rom, twrp and super su. Reboot and the smartphone was reborn. Whit titanium backup i restored all data. This time the thing is very very different and more difficult. In my opinion probably i could download a virus with whatsapp, usually it is connected to a link into a message sended by a contact in whatsapp, or happened something during the restore of backup of whatsapp. The device goes constantly in bootloop but i can entry in recovery mode. i noted that can't see the gapps, rom e supersu file in the sdcard like the other times. They are only in the data\media\0 folder. Everythime i try to copy something not in the sdcard, it goes on an error about a netstat file i found in the data\system\netstats folder. It's a file short, different by the others. I red that netstat files can be deleted but this file can't be deleted by using twrp>advanced mode>file manager>name of the file>delete. Before try to do another format data or again a total format of internal storage like the other time, i need to know if this procedure can resolve the problem. This time i was not prepared so the last backup is about six months ago. In this months i inserted new contacts and this time i don't sincronized my contact list with my google account like the other times because i couldn't image to be in this situation. I try to delete the file using adb but my phone is not recognized so the serial number doesn't appear. List of deviced attached is empty. In this case i can't activate the developer funcstions by tipping in the device information into the phone because it goes in bootloop. On the pc i have usb-drivers, but now into the phone there's android 4.4 not 4.3 like the first time i do the procedure to unlock the device. So with adb don't see serial number but the pc just see the device like google nexus adb interface. Copying file as contact or dialer or data about apps because are all in the data folder, appears an always an error about netstat and the red failed written. just copy from sdcard folder to usb external device this not happen, what can i do?
I done a nandroid backup because i know that with titanium backup i can restore data i want to restore, but also in this case could appear the same message error about netstat file? All data are been copied on the external usb deviced and then on the pc, but i don't know if the problem will be present again. so if i try to restore data with titanium backup and the problem reappers i don't know what to do.
Here we are some information about my phone. I hope someone in this fantasctic and big community about android developers can help me to solve this very big problem. if i thinking about i've done i feel so stupid because probably i could avoid this problem.
i forget to say also i tried to fix permission, wipe davilk cache and cache, copy log to sd (to see if there's another error but i don't know how to do). After all of this passages, everytime appears the same error.
Fastboot Mode:
Product name: tuna
Variant: maguro 16gb
hw version: 9
Bootloader version: primemd04
basedband version: i9250xxlji
carrier info: none
serial numeber: xxxxxxxxxxxx
signing: production
lock state: unlocked
Rom: omnirom maguro nightly 4.4.2, kernel stock of omnirom. gapps stock 4.4.2
Error: E: unable to stat ' /data/system/netstats/dev.1480018034937_' appears then "updating partition details..."
after error: ....done Full SELinux support is present. Mtp enabled
Update
pc see the device in fastboot mode launching cmd fastboot devices. Get out the serial number. It doesn't work launching cmd adb devices. List of device is empty. On the pc i have two file about usb drivers downloaded by samsung support site. If i change the usb driver folder in sdk with the new samsung usb driver i just download, may i permit to see the phone with adb? or should i try to unistall device recognized as google galaxy nexus adb interface and repeat the installation of google usb drivers with an unknown device?
update
i'm losting hope. I tried also nexus root toolkit (NRT) by wugfresh. Before the programme i can't see the phone with adb, after unistall and reinstall the driver i can se the device. But here the bad news... i can't copy from the pc into the sd folder using windows and i don't know why because pc see the device, i can see the folder inside sdcard internal storage but can't copy from the pc to the phone. Fastboot and adb mode work. I've done a flash stock + unroot using NRT. Everything fine but then phone goes in bootloop and not with the stock logo so Nexus, with the Rom logo intalled instead. The NRT message says that the bootloop could appen so wait. After 20 minutes power off the device. So i try to do format data from TWRP; procedure works with blu written succesfull but there's the same problem E (encrypted or error?) unable to stat data/system/netstat file and the number of the file. So i try to wipe the internal storage. Succesfull but again red written E: same up. Everything i try to do nothing change. Internal storage stuck always the same MB, TWRP 2.8.7 always present, i can't flash 3.0.2. Can't also remove enctrypted data with NRT because is uncheck. Have i throw away the phone? The E unable to stat data/system/netstat with the number of the file goes out everytime because during the process for example about format data check out updating data partition and then E: blablabla also with succesfull written, not failed.
Goodday,
I have been looking into rooting my android device for over a week now and was still not able to find how it can be done for an unidentified tablet.
I have an Allwinner T8 tablet (headunit) that runs oreo 8.1.0, theres no info availlable on this unit whatsoever, all i have is a detailled system information gathered by root checker, i can post the detaills if its required.
I've managed to make a full backup of my device using the adb backup command incase something goes wrong it can be reverted easily.
No custom recovery option availlable to flash.
Is it possible to root my device using the supersu zip without a custom recovery for example with adb using the command "adb flash"?
The most usefull guide for my situation i have come across is the magisk manager installation guide: ht tps://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
This method requires me to have the stock boot image from my device, seeing i don't have root and cant just copy that file, where exactly can i find this file(whats the path to it)?
Is it possible to use adb command "adb root; adb pull ... " to retrieve this file? If not how can i get my hands on this file?
Please help me, i have spend many houres searching google and watching videos but all of wich are the easy methods that don't work for my tablet or require root or a custom recovery wich i cant install... pretty frustrating...
I think magisk manager is the only correct way to go for my problem
Also, if i remount my system or root with read&write rights using adb shell, is that the same as rooting my device?
if i can read and write into the system directory on my device then i should be set.
So what exactly is the diffrence between rooting my device and remounting my device/system as read/write?
anyone??
Hi, few day ago I made a videos with a modded version of Google Camera 8.1,
the first one was not saved properly and was in .pending????????.mp4 state, and I erased it by mistake,
because it was first time, I was using this tool, and I didn't knew that it is a temporary file.
I tried to recover, using many tools, but I was unable to recover it, so I decided to Root my phone using Magisk,
I made some mistake and testing some FastBoot command I relocked my Unlocked phone.
I had to Unlock again by using "miflash_unlock.exe", with advertising that all my data’s will be deleted.
After I managed to patch my phone, he restarted (I don’t installed any previous apps prom store, to avoid my video to wiped by new data,
and I tried with Ult Data, Dr Phone to recover the file, but Root access was not accepted.
Then I tested lot of android tool, nothing worked, after searching a lot I found this page :
https://drfone.wondershare.com/android-recovery/phone-memory-data-recovery.html
And I tried but some command didn’t work, since I didn't have FDISK, FTPPUT on my phone file system,
after some other search I found this ancient page (2014) who seemed to be the source,
https://sudonull.com/post/108208-Recovering-data-from-internal-memory-on-Android-for-dummies
and after installing BusyBox Pro,
I managed to get missing Linux tools.
I tried the command, all worked fine,
but now I’m unable to access this one :
Code:
ftpput -v -u sally -p able -P 40 192.168.1.4 sde55.raw /cache/myfifo
because my FileZilla does not get any information.
And I receive this message :
Code:
can't connect to remote host (192.168.1.4): Connection timed out
The article is old and that guy was using U.S.B. MoDem on CyanogenMod 11.
I use Magisk pro rooting and I do not know what tool I should use to get U.S.B. link with FileZilla Server to get proper connection.
I tried many things, changing protocols, P.T.P., M.T.P., and I do not know what to do,
so I thought may be here, someone with experience could point me to a tool to use in Android 12 / 11 with my Magisk and link to FileZilla Server,
to get image of internal memory back‑up‑ed ?
Thank you in advance.
No one knows how to ?
Someone knows an other methodic to extract partition totally & perfectly ?
forum.xda-developers.com/t/guide_making_dump-files_out_of_android_device_partitions/