Hi, really looking for any advice or pointers. I have only now got round to trying to root my moto G xt1032 which is a very limiting 8GB of internal memory and no SD.
I manged to gain root access and install superuser and TWRP. Everything seemed to be ok but before messing around more i wanted to try to backup in some way (a recovery image sounded ideal). And then i just kept hitting walls; the 8GB was not enough to do a backup of the system, boot AND data. It seemed to say when i opened a (3rd party?) app TWRP Manager, that backups to external drives were not possible due to TWRP no longer supporting this feature.
Anyway I decided to risk just a backup of system and boot (leaving out data) before trying out a new ROM. After backing up i tried a slimkat rom....unfortunately the screen had a line constantly cascading down the display (this looked similar to the TWRP line running down the screen but just being a recovery console it made no difference to me - obviously it's no good having a buggy display on your handset proper).
So i decided to see if going through TWRP to restore the backup i made (of boot and system, omitting data) would work. At first everything booted but then i realized something was seriously wrong - no WIFI for example being available. So i have now come full circle and now flashed back to a stock rom that took about 4 hours to download from filefactory. I seem to be back up and running on the stock 5.0.2 vers (without bootloader unlocked i think?)
So my question really is - is there a way to backup using TWRP in my scenerio of only having an 8GB version which alone is not enough to include data in the backup? I also was not able to interact between the PC and moto whilst in the bootloader menu (by which i mean the files were not visible on my pc i was still able to use fastboot commands).
Sorry for the convuleted post - mainly I'm doing this as an experiment - would rather not brick right away but no great loss if i do. I'm just wondering how i can overcome this issue with doing a proper backup in TWRP as all i could backup previously was the boot and system which turned out no use as a recovery.
I manged to gain root access and install superuser and TWRP. Everything seemed to be ok but before messing around more i wanted to try to backup in some way (a recovery image sounded ideal). And then i just kept hitting walls; the 8GB was not enough to do a backup of the system, boot AND data. It seemed to say when i opened a (3rd party?) app TWRP Manager, that backups to external drives were not possible due to TWRP no longer supporting this feature.
Anyway I decided to risk just a backup of system and boot (leaving out data) before trying out a new ROM. After backing up i tried a slimkat rom....unfortunately the screen had a line constantly cascading down the display (this looked similar to the TWRP line running down the screen but just being a recovery console it made no difference to me - obviously it's no good having a buggy display on your handset proper).
So i decided to see if going through TWRP to restore the backup i made (of boot and system, omitting data) would work. At first everything booted but then i realized something was seriously wrong - no WIFI for example being available. So i have now come full circle and now flashed back to a stock rom that took about 4 hours to download from filefactory. I seem to be back up and running on the stock 5.0.2 vers (without bootloader unlocked i think?)
So my question really is - is there a way to backup using TWRP in my scenerio of only having an 8GB version which alone is not enough to include data in the backup? I also was not able to interact between the PC and moto whilst in the bootloader menu (by which i mean the files were not visible on my pc i was still able to use fastboot commands).
Sorry for the convuleted post - mainly I'm doing this as an experiment - would rather not brick right away but no great loss if i do. I'm just wondering how i can overcome this issue with doing a proper backup in TWRP as all i could backup previously was the boot and system which turned out no use as a recovery.
Aucun commentaire:
Enregistrer un commentaire