[Q] Install multiple Galaxy Tab 3 10.1s exactly the same - SOLUTION - Galaxy Tab 3 Q&A, Help & Troubleshooting

Hi,
Is it possible to clone a device and rollout this 'disk-image' to other devices?
I've to install 16 tablets, exactly the same ones. They have to be exactly the same as well.
They are used in museum lessons.
Thnx
Got it to work using this steps:
- make sure installation is oke
- get TWRP recovery on device
- Boot in TWRP recovery
- Make backup using TWRP
- Save backup on PC (TWRP/Backups folder)
- Take new device using same rom
- Get TWRP on device
- Make smallest backup possible of new device using TWRP (in order to get specific backup folder names from new device)
- Also save this on pc
- Now copy the first complete backup to the tablet in the TWRP/Backups folder, alongside the small one just created.
- Rename this folder containing complete backup to the name of the small one created
- Reboot in TWRP
- Go to restore
- Select restore file
- Swipe to restore
Thnx for putting me in right direction.

E,
probably the best way for only 16 devices, is to establish your "prototype" with the complete rom, then
make a full backup of the rom and pull a copy of that to your pc, then push the back up to the other tabs
and restore the backup. All 16 tabs must run the same recovery.
m

Hi, thnx for the answer..
I'm very new to all this.
Can you be a bit more specific?

Related

[Q] Rooting&Flashing Important questions

i have readed this guide http://forum.xda-developers.com/showthread.php?t=824396
but i got some questions
i understand rooting good but i got some questions
What will rooting do to my phone
will it affect anything i have?
and now flashing first rom
do i need to connect my phone to my computer while i use titanium backup???
and while i use nan droid
do i need to connect my phone to pc
and is it a android app?????????
and do i have to get a linux to flash or root???
and what do he mean with
(Ensure you have downloaded a ROM and it is on the root (Not in any folders) of your SD card)
what do he mean with on the root
and do i have to make a folder or paratiton in memory card to use it
i have a 8 GB memory card
will it use much space
and if i mess up my phone how can i repair it???????????????????
?????????????????????????????????????????
???????????????????????????????
???????????????????
???????????
??????
???
?
What's with the ton of question marks at the end?
First and foremost, that guide is applicable only if you are on Android 2.1 (Eclair). If your Wildfire has the official Froyo Update, it wont work anymore, in which case, read this post here:
http://forum.xda-developers.com/showthread.php?t=1029318
- No, Rooting wont affect anything you have. You can always get back to stock
- No, you need not connect your phone to your computer when using Titanium backup. It will create a backup on your SDCard
- The same holds for a Nandroid Backup. You need not connect your phone to your computer. It will create a backup on your SDCard
- No, Windows will do fine. Linux is not a necessity
- 'root of your sdcard' means just that. Simply paste the ROM's ZIP file to your SDCard. Do not place it any folders or subfolders on your SDCard.
- No, its not necessary to partition your SDCard to use and flash Custom ROMs
- Yes, 8GB is certainly more than sufficient. The bundled 2GB card does the job as well.
- There are two ways to repair your phone:
a) Perform a Nandroid Restore. (It can be found just below Nandroid Backup. When you take a backup, you will know it)
b) Flash an RUU. It's an EXE file containing the stock ROM Image. All RUU's can be found here:
http://shipped-roms.com/index.php?category=windows mobile&model=Buzz
Good Luck

I think CWM screwed me

I should be able to flash a backup I made with CWM recovery in CWM recovery, correct? Or would I have to adb push it?
I moved to 4.2.1 but not a fan of it at this point and want to go back using a backup (4.1.2) I made with CWM, but it won't flash. So at this point I'm trying to save my photos, notes, texts, and my titanium backup of apps and do a complete wipe using wugs (unroot/relock then reroot/unlock). Or should I be able to get away with just doing a format on my sdcard/system/cache/data and data/media (options in CWM)? Since going to 4.2.1 I have also lost a significant amount of free space.
BTW I have tried TWRP before and went back because I didn't like the layout but damn if your recovery can't even handle its own backups what the hell is it good for? TWRP here I come again.
you know it moves everything to a folder called 0 on the internal memory, right...?
A lot of the following is probably overkill but what I'd do is...
1. Backup everything I wanted to keep when in Android 4.2.1 onto my PC (Nandroid backups, photos, music, etc.)
2. Flash the factory 4.1.2 image
3. Boot up to make sure it's working
4. Restore nandroid in CWM
Chances are there are easier ways of doing this but I'd be happy knowing that is 100% right then have the potential for it going wrong
derekwilkinson said:
you know it moves everything to a folder called 0 on the internal memory, right...?
Click to expand...
Click to collapse
Bud I have tried to flash it out of every folder I have access to in CWM Recovery
The folder's I have tried, after choosing install zip from sdcard:
sdcard/0/clockworkmod/backup/ - 4 backups in here but wont flash any of them - says no files found when I try to flash one
sdcard/clockworkmod/backup/ - can actually see 2 backups in here (ones I don't want, just wanted to see where they were placed in 4.2)
sdcard/legacy/ - no files found
But stupid me did just realize the CWM backups I have been creating aren't zips? So I need to figure out how to get to sdcard/clockworkmod/backup and place my backup folders here. So I will be able to see them when I choose Backup and Restore - Restore
CWM can't see the backups in the '0' folder, it stores them on /data/media (or is it /media/data??) so unless you have a file manager with root access you won't get them back
EddyOS said:
CWM can't see the backups in the '0' folder, it stores them on /data/media (or is it /media/data??) so unless you have a file manager with root access you won't get them back
Click to expand...
Click to collapse
My my my you are the man. It looks like it is data/media/clockworkmod/backups.
I am going to try to Restore my latest 4.1.2 nandroid tonight, after I had a chance to back every thing up, but I'm guessing it's going to keep the current file structure though.
The best way to upgrade to 4.2.1 from 4.1.2 is
1.Flash all factory images from fastboot apart from recovery,@ recovery step flash twrp 2.3.3.0 and you are all set to no '/0' bug,
2. Downgrade to 4.1.2 ? Flash factory images of 4.1.2 , just keep the recovery as twrp 2.3.3.0, at present it is the best possible recovery for maguro for handling the '/0' bug , it doesnot delete the layout file.
And restoring nandroids in between the versions can make every file very clumsy, take some time and flash stock images to get rid of that.
BaMaDuDe87 said:
My my my you are the man. It looks like it is data/media/clockworkmod/backups.
I am going to try to Restore my latest 4.1.2 nandroid tonight, after I had a chance to back every thing up, but I'm guessing it's going to keep the current file structure though.
Click to expand...
Click to collapse
After downgrading you will still have the /0/ folder with all data. So many apps wont recognize that the backups are there available to be restored. You can just point to the "new" backup location that now exists in the /0/ directory.
Example: Titanium backup will tell you there is no restore data unless you go into preference and point it to the right folder in /0/.
Example 2: Nova launcher will not see the backups. Manually move them via Root explorer or similar from the /0/data/ to the /data/
..and so on.
I guess I will be flashing the factory image then.
1. Backup everything I need/want (photos, notes, sms, and grab latest copy of titanium backup folder)
2. Format system/cache/sdcard just because
3. fastboot - factory image (4.1.2)
4. Phone should still be unlocked/rooted (on current bootloader/radios correct?)
5. fastboot - twrp
5. Restore everything else
Or use Wugs to take back to stock, then fastboot unlock, root, add CWM recovery might be the easier way at this point. Restore nandroid and everything else. Then add TWRP and remove CWM.
Sorry trying to talk this out with you guys and wrap my head around what I am in for. I know it's not hard, just frustrating to think I could possibly lose some things.
Better Recovery TWRP
BaMaDuDe87 said:
I guess I will be flashing the factory image then.
1. Backup everything I need/want (photos, notes, sms, and grab latest copy of titanium backup folder)
2. Format system/cache/sdcard just because
3. fastboot - factory image (4.1.2)
4. Phone should still be unlocked/rooted (on current bootloader/radios correct?)
5. fastboot - twrp
5. Restore everything else
Click to expand...
Click to collapse
Not to be bossy but the latest version of TWRP seems to do a better job handling user folder /0. Its also touchscreen and [email protected]$$ so there is really no comparison....:highfive:
Yea I tried it, thought I was more comfortable with CWM and this bit me in the ass, so TWRP it is when I get everything straightened out

[Q] Copying a TWRP backup to a new device

I made a TWRP backup after setting my device up, now I want to copy this image to new devices. I made a backup of the wanted config inside TWRP and copied it to a PC. I factory reset the device to restore onto, rooted it, made a TWRP backup of boot only so I have the hashcode folder ready to roll to place the main backup into. Now when I connect the device to my PC and try to copy into this hashcode folder, I get errors like 'folder has been removed' or something, which I expect is to do with permissions. In TWRP in advanced, filesystem management, I apply chmod 777 to the hashcode folder, I still can't copy the backup into that folder from the PC, same message. Ideally I don't want to go through a full setup of the new device in order to install root explorer and change permissions etc., I have 8 of these units and want to make the process painless, not a multi-hour job.
Sooo, is there a process via TWRP whereby I can make the backup hashcode folder writeable from the PC so I can simply copy my backup across to the new device and proceed with the restore? If I must use ADB I can probably live with that, just if someone can help me out with a set of commands that can 'make it so'. Ideally I just want to change settings in TWRP with the "right" commands, reboot it and copy my backup across, before rebooting back into TWRP and running the restore.
I'm doing this so I can quickly setup a standard configuration for some specific software we use, replicate that across to units, have people access the apps via a restricted profile, then after field use, be able to return the unit back to a standard config via a TWRP restore using the minimum number of steps.
The way I got it working was to copy the backup folder to a temporary location on the new device from the PC, then move it to TWRP's backup folder using the TWRP file management tools.

GT-N7105 TWRP Restore can't see backup

My phone is GT-N7105 (Samsung Note 2)
I had a nandroid backup before, then I copied the backup to PC, still have it. Then I flashed lineage 14 (nougat), then flashed lineage 13 (marshmallow). I deleted the nandroid backup on the phone storage sometime during that period. Now I want to restore the backup (stock rom) so I copied the backup files from the PC to phone storage.
Now when I go to TWRP Restore mode, no backups are found.
I already searched through the internet and found the renaming method but there's a problem:
this is my original backup:
TWRP/backups/42f7491d7b409fc7/2017-03-01--05-28-34_JZO54K.N7105XXDMB
I tried to make a new backup of my current lineage (just to see if the folder name changed based on the new folder the backup process will create), here is what the resulting folder was:
TWRP/backups/42f7491d7b409fc7/2017-07-05--09-27-29_lineage_tOlte-userdebug_6.0.1_MOB31K_ab972c
As you can see, only the innermost folder name changed. So from what I found through searching, it said to rename the old backup folder to the new backup folder's name, meaning :
I changed
2017-03-01--05-28-34_JZO54K.N7105XXDMB2
to
2017-07-05--09-27-29_lineage_tOlte-userdebug_6.0.1_MOB31K_ab972c
TWRP still can't see the original backup.
I already tried renaming only part of the orignal backup folder name, specifically the 6 character code (found 2, JZO54K and XXDMB2) to the 6 char code from new backup (MOB31K and ab972c) but TWRP still can't recognize the original backup.
So what should I rename the original backup folder for TWRP to recognize it and make it appear? I really need to restore it back to stock rom. help please. Thanks
EDIT:
TWRP I used before was 2.8.0 but I just updated the TWRP to 3.1.0 and still can't recognize original backup
Also, If I made the thread in wrong section, please move it and I apologize in advance. Thanks.

Downgrade and restore from other Bullhead

Hi all,
I have my 5x back from repair and a want to restore from my old trwp backup. What roadmap do i need to follow?
The phone has a new serialnummer so i expect the board is replaced.
I know how to unlock and install twrp.
Twrp backup is from 7.1.2. New phone is on 8.1.
Possible steps:
1. Unlock bootloader
2. Install factory image 7.1.2
3. Install twrp
4. Push twrp backup from pc to nexus
5. What partitions to restore?
@Rexylian: if you want to step up to Oreo (recommendable imo), you shouldn't restore Nougat-stuff. So this may be the moment.
Otherwise choose the factory-image which matches to your backup, and restore (boot&)data&system.
@rp158: Thank for the quick replay.
I copied the twrp backup to my phone. (adb push)
Booted into twrp but i can see the folder in trwp but cant select any partition to restore....
What i'm doing wrong?
NP: I found it already: different serialnumber
twrp looks for a folder named after the serialnumber.
Renaming the folder to the correct serialnumber works....
@Rexylian: Move your backup to /sdcard. Make any dummy backup to let TWRP create its favourite folder. Move your backup there. Then you should see and be able to choose the dummy and your real backup (the folder names) in TWRP.
@rp158: thanks for your replies. It's up and running now! So happy
The only bump i had was to remove the old password files via twrp...
The reason i downgraded to 7.1.2 was that i could not get safetynet to pass on the latest oreo..

Categories

Resources