Hello all, has anyone attempted to install the YT-X703 TWRP/ROOT/ROM on the ZA1N US varient of the yoga tab 3 Plus? I have been wanting to get one but I can't find the YT-X703 models here in the US. However, not having Nougat on my tablet is a deal breaker for me. So if I can't use the YT-X703 files, ill pass on it. Thanks for any info anyone can provide.
glitchhawk said:
Hello all, has anyone attempted to install the YT-X703 TWRP/ROOT/ROM on the ZA1N US varient of the yoga tab 3 Plus? I have been wanting to get one but I can't find the YT-X703 models here in the US. However, not having Nougat on my tablet is a deal breaker for me. So if I can't use the YT-X703 files, ill pass on it. Thanks for any info anyone can provide.
Click to expand...
Click to collapse
You could test it yourself and return the device if it doesn't support it. Not sure what kind of return policy you have in the US but you could restore the device to its original state. On the YT-X703 model the bootloader is relockable. So once you have the tablet you could do the following:
check if the device can be unlocked in the developer options
if yes unlock the device
try to boot TWRP
if it boots you can send me some hardware details to see if the US version matches the ROW version
if that's the case backup partitions modified by Lineage OS (it has to be the right partitions)
Install Lineage
if it doesn't work well go back to TWRP and restore the backed up partitions and relock the bootloader and you're back to original state
Of course this would have to be done very carefully since you don't have a factory firmware image as a fail safe.
If it works you would probably be the first to have TWRP and Lineage on the US model
matshias said:
You could test it yourself and return the device if it doesn't support it. Not sure what kind of return policy you have in the US but you could restore the device to its original state. On the YT-X703 model the bootloader is relockable. So once you have the tablet you could do the following:
check if the device can be unlocked in the developer options
if yes unlock the device
try to boot TWRP
if it boots you can send me some hardware details to see if the US version matches the ROW version
if that's the case backup partitions modified by Lineage OS (it has to be the right partitions)
Install Lineage
if it doesn't work well go back to TWRP and restore the backed up partitions and relock the bootloader and you're back to original state
Of course this would have to be done very carefully since you don't have a factory firmware image as a fail safe.
If it works you would probably be the first to have TWRP and Lineage on the US model
Click to expand...
Click to collapse
good plan, I may have to try this out. Thanks! I might grab one tomorrow
matshias said:
You could test it yourself and return the device if it doesn't support it. Not sure what kind of return policy you have in the US but you could restore the device to its original state. On the YT-X703 model the bootloader is relockable. So once you have the tablet you could do the following:
check if the device can be unlocked in the developer options
if yes unlock the device
try to boot TWRP
if it boots you can send me some hardware details to see if the US version matches the ROW version
if that's the case backup partitions modified by Lineage OS (it has to be the right partitions)
Install Lineage
if it doesn't work well go back to TWRP and restore the backed up partitions and relock the bootloader and you're back to original state
Of course this would have to be done very carefully since you don't have a factory firmware image as a fail safe.
If it works you would probably be the first to have TWRP and Lineage on the US model
Click to expand...
Click to collapse
Ordered one today. Should be here Wednesday. I'm excited.
glitchhawk said:
Ordered one today. Should be here Wednesday. I'm excited.
Click to expand...
Click to collapse
Good stuff. When you try to boot TWRP after bootloader unlock make sure you just boot and don't flash.
The partitions you have to backup are "System Image", boot and recovery. I'd recommend to do a second backup via command line dd tool to be sure you have a valid backup. The backup should be done onto an external SD card so you can't accidentally wipe it.
Then wipe data before flashing Lineage and hopefully all goes well.
Optionally you could upload your partition backups done with dd so others have them in case something goes wrong.
matshias said:
Good stuff. When you try to boot TWRP after bootloader unlock make sure you just boot and don't flash.
The partitions you have to backup are "System Image", boot and recovery. I'd recommend to do a second backup via command line dd tool to be sure you have a valid backup. The backup should be done onto an external SD card so you can't accidentally wipe it.
Then wipe data before flashing Lineage and hopefully all goes well.
Optionally you could upload your partition backups done with dd so others have them in case something goes wrong.
Click to expand...
Click to collapse
Sorry, command line dd tool? That is something I haven't ever done before. Is that something I need to download or is it embedded in adb?
glitchhawk said:
Sorry, command line dd tool? That is something I haven't ever done before. Is that something I need to download or is it embedded in adb?
Click to expand...
Click to collapse
You just connect with ADB shell in TWRP and then you can use it like that
Code:
dd if=/dev/block/bootdevice/by-name/partition of=/sdcard1/partition.img bs=4096
Replace "partition" with system, boot or recovery to make a raw backup of the respective partition.
Make sure that the external SD card is mounted in TWRP and has lots of free space.
Note that the system partition is stored in raw format. If you want to restore it later with fastboot it has to be in sparse format. For that you need the tool img2simg. If you want to restore with dd, the raw format is used.
Since the system partition is very large you have to check that the IMG file you get has the right size. Should be around 3.8 GB.
When you restore it can happen that it doesn't work in which case you just try again until it works.
Again all this is meant as a fail safe if TWRP backup has problems.
matshias said:
You just connect with ADB shell in TWRP and then you can use it like that
Code:
dd if=/dev/block/bootdevice/by-name/partition of=/sdcard1/partition.img bs=4096
Replace "partition" with system, boot or recovery to make a raw backup of the respective partition.
Make sure that the external SD card is mounted in TWRP and has lots of free space.
Note that the system partition is stored in raw format. If you want to restore it later with fastboot it has to be in sparse format. For that you need the tool img2simg. If you want to restore with dd, the raw format is used.
Since the system partition is very large you have to check that the IMG file you get has the right size. Should be around 3.8 GB.
When you restore it can happen that it doesn't work in which case you just try again until it works.
Again all this is meant as a fail safe if TWRP backup has problems.
Click to expand...
Click to collapse
Okay awesome. Thanks. So if I make up a dd backup for myself or others to use in the future, it's best to convert to sparse? Unless its only for myself then I could leave it in raw basically? Thanks again for all the info.
matshias said:
You just connect with ADB shell in TWRP and then you can use it like that
Code:
dd if=/dev/block/bootdevice/by-name/partition of=/sdcard1/partition.img bs=4096
Replace "partition" with system, boot or recovery to make a raw backup of the respective partition.
Make sure that the external SD card is mounted in TWRP and has lots of free space.
Note that the system partition is stored in raw format. If you want to restore it later with fastboot it has to be in sparse format. For that you need the tool img2simg. If you want to restore with dd, the raw format is used.
Since the system partition is very large you have to check that the IMG file you get has the right size. Should be around 3.8 GB.
When you restore it can happen that it doesn't work in which case you just try again until it works.
Again all this is meant as a fail safe if TWRP backup has problems.
Click to expand...
Click to collapse
turns out when you buy a ZA1N, it still comes as a YT-X703F. so.. looks like im probably set to start TWRPing
Related
Hello,
i need help. I messed up my phone while trying to repair my only read mode system partition after boot.
Current state:
Phone CAN-L11 with EU Firmeware and working TWRP Recovery.
I did a full wipe, but have no data partition to restore, because this couldn´t be saved with twrp while i made my first nand backups during no read access to data partition.
My phone always shows 2 times the huawei logo and then boot in erecovery from huawei where i tried to restore, but it shows always "fail to get data" (wifi works).
When i restore all partitions backups that i own via twrp i miss the data partition (is the cause why it wont boot - isn´t it?)
Now i searched for any img that i can use to get my phone working again - anyone has a tip what img i could use (i have a huawei update extractor) - through twrp or fastboot.
Could anyone help me with a twrp backup or a img file of data partition - or has another tip how to get my phone working again?
Thanks for tips!
merlin21 said:
Hello,
i need help. I messed up my phone while trying to repair my only read mode system partition after boot.
Current state:
Phone CAN-L11 with EU Firmeware and working TWRP Recovery.
I did a full wipe, but have no data partition to restore, because this couldn´t be saved with twrp while i made my first nand backups during no read access to data partition.
My phone always shows 2 times the huawei logo and then boot in erecovery from huawei where i tried to restore, but it shows always "fail to get data" (wifi works).
When i restore all partitions backups that i own via twrp i miss the data partition (is the cause why it wont boot - isn´t it?)
Now i searched for any img that i can use to get my phone working again - anyone has a tip what img i could use (i have a huawei update extractor) - through twrp or fastboot.
Could anyone help me with a twrp backup or a img file of data partition - or has another tip how to get my phone working again?
Thanks for tips!
Click to expand...
Click to collapse
I think that you need a system.img, so you can flash. This system imagem would write everything you need, so you can boot normally.
Have you tried to dowload @bluesmoothie backup from dropbox from the Root and Recovery post?
Here is the link, in case you don't find it https://www.dropbox.com/sh/qrk0fbpn5rnukxn/AAAmhFwBTNoqq0sWfCH-VMHLa?dl=0
Sent from my victara using XDA Labs
Here the full Backup for the CAN-L11:
https://drive.google.com/open?id=0B134drJ4-Ed0R3VSY3A5NGpjVWc
Format /data, reboot recovery and than restore from backup. After the restore is complete make a wipe.
I restored my system from twrp (original first save). But that did not help.
After that i loaded the can-L11c432 update.zip from huawei and extracted with others the system.img - that also did not help to boot.
Tomorrow i flashed the orignal recovery.img from c432 but i did not find an update.zip wich works to manually flash in stock recovery.
@Vinnom the link you shared leads to twrp.img (no system.img).
@-=MoRpH=- thanks, i will try and report back. Is this anyway a chinese version in there? I think i have the same struggle you had days back. Is your phone completely working again?
So sick that my phone did not work. Now working with my "old" LG G2...
I report back later - first family dinner
merlin21 said:
I restored my system from twrp (original first save). But that did not help.
After that i loaded the can-L11c432 update.zip from huawei and extracted with others the system.img - that also did not help to boot.
Tomorrow i flashed the orignal recovery.img from c432 but i did not find an update.zip wich works to manually flash in stock recovery.
@Vinnom the link you shared leads to twrp.img (no system.img).
@-=MoRpH=- thanks, i will try and report back. Is this anyway a chinese version in there? I think i have the same struggle you had days back. Is your phone completely working again?
So sick that my phone did not work. Now working with my "old" LG G2...
I report back later - first family dinner
Click to expand...
Click to collapse
Inside the folder twrp and its subfolders there it is system.img. I'm downloading it myself.
Sent from my victara using XDA Labs
Share if you have another workarounds for me
Gesendet von meinem LG-D802 mit Tapatalk
@merlin21 yes it sounds like my problem after I tried to flash the emui5 beta.
My phone is fully working again with the backup I posted.
This is not the Chinese version, if nothing works, you can try the caz ROM. But there are massive problems with the gapps, they are not included in the rom.
Gesendet von meinem HUAWEI CAN-L11 mit Tapatalk
@ -=MoRpH=-
i just flashed the twrp.img with fastboot from xelfmade v22.12. and then rebooted twrp.
Then formated data and confirmed with yes - rebooted recovery and tried to restore your twrp. It did not restore and aborted instantly with the error message
during restoreing cust...
extractTarFork() proecess ended with ERROR: 255
what could that be?
IT WORKS! Thanks @murph... I had to use the cust from my backup, but with your data partition it successfully booted again. Locking forward if i now have still the problem with read only system partition. I am away setting up phone again (and of course rooting, modifying etc.. but FIRST do a full backup after basic setup and safe in PC !!!)
Thanks!
P.S. how did you manage to back up data partition in recovery? I thought this wouldn't be possible?! What is the cost for having this full working twrp?
PPS. Somehow knock on screen for screenshot does not work - could be, that i have to log in with huawei id... does it work for you morp?
Somehow knock on screen for screenshot does not work - could be, that i have to log in with huawei id... does it work for you morp?
Click to expand...
Click to collapse
That only work if the is not rooted... Idk whats up with that, but for now i use the quicksetting screenshot function.
Somehow it worked with my rooted device before. Must be the decrypted data partition?
With the recovery of your backup I could not access data or change memory from data to sd. What version do you use?
I flashed xelfmades v22 and now have rw access and could backup all partitions and restore. Root and xposed modules everything works, just the knock on screen to capture don't...
merlin21 said:
IT WORKS! Thanks @murph... I had to use the cust from my backup, but with your data partition it successfully booted again. Locking forward if i now have still the problem with read only system partition. I am away setting up phone again (and of course rooting, modifying etc.. but FIRST do a full backup after basic setup and safe in PC !!!)
Thanks!
P.S. how did you manage to back up data partition in recovery? I thought this wouldn't be possible?! What is the cost for having this full working twrp?
PPS. Somehow knock on screen for screenshot does not work - could be, that i have to log in with huawei id... does it work for you morp?
Click to expand...
Click to collapse
I have the same problem! What do you mean by "I had to use the cust from my backup" ? Sadly i dont have any data from my own backup..
can you tell me what to do to get the backup from @murph to work without error?
--solved.
P1xl said:
--solved.
Click to expand...
Click to collapse
May I ask how?
I'm kinda stuck personnaly. I have tried both Nand backups but no cigar. Still can't boot. I had the Data issue which I managed to get rid of.
I still end up with a ExtTarFork 255 kind of error. I tried to change the files attributes via adb shell, but it failed so I've got an OS-Less phone...
Any help would be greatly appreciated.
rak500 said:
May I ask how?
I'm kinda stuck personnaly. I have tried both Nand backups but no cigar. Still can't boot. I had the Data issue which I managed to get rid of.
I still end up with a ExtTarFork 255 kind of error. I tried to change the files attributes via adb shell, but it failed so I've got an OS-Less phone...
Any help would be greatly appreciated.
Click to expand...
Click to collapse
I copied the backup, which is linked somewhere in this thread, to my sdcard and restored it on my Nova using twrp. The extractfork issue showed up while restoring '/cust' so i disselected cust in the restoring menu. After that the restoring worked and my nova was able to boot.
Hope this is any help to you.
P1xl said:
I copied the backup, which is linked somewhere in this thread, to my sdcard and restored it on my Nova using twrp. The extractfork issue showed up while restoring '/cust' so i disselected cust in the restoring menu. After that the restoring worked and my nova was able to boot.
Hope this is any help to you.
Click to expand...
Click to collapse
That didn't do the trick for a while, or I might have forgotten a step, but deselecting CUST did the trick.
Thanks for the tip!
Although, maybe flashing the Cust partition I found in one of the two upgrade zips via fastboot might have helped? I dunno...
But in short, for those who haven't followed through, here's what I did, but I'm not sure this is why it worked:
1. Bricked my device : be sad;
2. DLed all the posted Nandroid backup on this thread and others;
3. With fastboot, reflashed TWRP from Xelfmade using "fastboot flash recovery twrp.img";
4. Flashed the CUST.img I found in the UPDATE.APP of the update_data_full_CAN-L11_hw_eu.zip; or maybe the other, only one of the two seem to have it; I extracted it using Huawei Firmware Extractor; using "fastboot flash cust cust.img";
5. Created a "fake" backup to create the right folder structure on my SD (TWRP Couldn't see the backups) and put the Nandroid Backups I DLed earlier in it;
6. Reboot in TWRP and Restore all partitions except CUST;
7. Reboot, sweat, wait, cry, roll on the floor in fear, heard the huawei startup sound, cried as if it was my first born child;
8. Setup the fone and profit; then enjoy Nova goodness;
92.324. and probably most important, TWRP BAAAACKUUUUP!!!!!
All done!
Thanks for your help my phone is saved with your method!!!
i downgraded my MLA-L03 variant with this, but now im stuck in french language with no other languages to choose from
Vinnom said:
I think that you need a system.img, so you can flash. This system imagem would write everything you need, so you can boot normally.
Have you tried to dowload @bluesmoothie backup from dropbox from the Root and Recovery post?
Here is the link, in case you don't find it https://www.dropbox.com/sh/qrk0fbpn5rnukxn/AAAmhFwBTNoqq0sWfCH-VMHLa?dl=0
Sent from my victara using XDA Labs
Click to expand...
Click to collapse
someone please make this thread sticky!!!!!!!
there are some guides in internet how to get nougat for nova and that is were I broke my phone. I was searching solutions for a week, DLed Flahsed tons of things nothing worked. this one fully worked!!!!!!!!!!!!!!!!!!!!
rak500 said:
That didn't do the trick for a while, or I might have forgotten a step, but deselecting CUST did the trick.
Thanks for the tip!
Although, maybe flashing the Cust partition I found in one of the two upgrade zips via fastboot might have helped? I dunno...
But in short, for those who haven't followed through, here's what I did, but I'm not sure this is why it worked:
1. Bricked my device : be sad;
2. DLed all the posted Nandroid backup on this thread and others;
3. With fastboot, reflashed TWRP from Xelfmade using "fastboot flash recovery twrp.img";
4. Flashed the CUST.img I found in the UPDATE.APP of the update_data_full_CAN-L11_hw_eu.zip; or maybe the other, only one of the two seem to have it; I extracted it using Huawei Firmware Extractor; using "fastboot flash cust cust.img";
5. Created a "fake" backup to create the right folder structure on my SD (TWRP Couldn't see the backups) and put the Nandroid Backups I DLed earlier in it;
6. Reboot in TWRP and Restore all partitions except CUST;
7. Reboot, sweat, wait, cry, roll on the floor in fear, heard the huawei startup sound, cried as if it was my first born child;
8. Setup the fone and profit; then enjoy Nova goodness;
92.324. and probably most important, TWRP BAAAACKUUUUP!!!!!
All done!
Click to expand...
Click to collapse
Hi. First of all, thanks for the tutorial. I've tried it but I have one problem. My /data particion is ext4. Should be f2fs. The thing is I can't convert coz my /data particion is unvisible
Can any help, please?
Bunkier said:
Hi. First of all, thanks for the tutorial. I've tried it but I have one problem. My /data particion is ext4. Should be f2fs. The thing is I can't convert coz my /data particion is unvisible
Can any help, please?
Click to expand...
Click to collapse
Frankly, I don't know. I had not modified the partitions prior to bricking my phone, so I think the partitioning was OK. However, I think one of the TWRP availble in this forum can format Data partition properly, which would utlimately allow you to select which File Format you want. I haven't tried it myself, and I haven't been able to do much with TWRP since I flashed Lineage unfortunately. Most of my Mods were just upgrading and I had to ADB Sideload pretty much everything since I flashed Lineage...
Sorry I couldn't be more helpful than that!
So I recently factory reset my phone and flashed update.zip from official ZTE website because the phone had been stuck on the ZTE screen. The system flashed successfully and the phone is booting up fine. I haven't yet gone through the setup process because I was hoping to run
dd if=/dev/sda conv=sync,noerror bs=64K | split -b 2000m - <YOURSDCARD>/system_drive_backup.img.gz
while booted in the signed TWRP so that I can get a raw device image without encryption. But, when I flashed the signed TWRP and booted into it, TWRP asked me for a encryption password, which is weird because the phone has not been setup in anyway so there shouldn't be an encryption right? If there is, is there some obvious password that it can be? I've tried default_password but that didn't work.
I'm assuming if I do the dd command while in TWRP it will just dump an encrypted image which would be useless for data recovery. Any way to do dd of unencrypted image?
If I boot into system, setup the phone, run adb in usb debugging mode, and then say adb root, will this give me enough permissions to fire the dd command while booted into system? Would this produce an unencrypted image if successful? If not is there any known way to decrypt device dump images?
On a sidenote, is anyone aware of which partition is the user_data partition on the axon 7? When I do cat /proc/partitions the largest partition is sda so this is presumably flash memory but it is hard to figure out which is the user data partition. When I do ls -al, there is a sdcard directory and an external_sd directory. Presumably this means that the former is the directory for user_data. Can anyone confirm this?
Thanks in advance.
Which version of the bootloader are you running and which update.zip did you try to install? I've flashed the wrong /boot on different Android devices to find the system "encrypted." Best way for me to fix it has always been to ensure compatibility between /system and /boot.
I can neither confirm nor deny your assumptions later in the original post. Sorry.
PiArc said:
Which version of the bootloader are you running and which update.zip did you try to install? I've flashed the wrong /boot on different Android devices to find the system "encrypted." Best way for me to fix it has always been to ensure compatibility between /system and /boot.
I can neither confirm nor deny your assumptions later in the original post. Sorry.
Click to expand...
Click to collapse
Thats no problem. I'm pretty sure I'm running stock Nougat version of everything. I downloaded the official B15 zip from the ZTE website and extracted the update.zip from that. Then flashed that to system. I never even touched my bootloader so that should still be stock B15 as well. Is there any way to check this compatibility?
I recently rooted my Moto G5 plus and would like to check out a a few custom ROMs. However, from reading the instructions on a few custom ROM threads it isn't clear to me what to backup in TWRP to be able to recover or go back to the stock ROM if I want to later.
I've read that I should backup Data, logo, and boot, and internal storage, plus all apps and data with Titanium Backup, but what about System, System Image, Recovery, OEM, and EFS? What about persist?
Can someone give me a quick summary of what I need to backup to go back to my current state if I want to experiment with some other ROMs?
Thanks.
Splice_9 said:
I recently rooted my Moto G5 plus and would like to check out a a few custom ROMs. However, from reading the instructions on a few custom ROM threads it isn't clear to me what to backup in TWRP to be able to recover or go back to the stock ROM if I want to later.
I've read that I should backup Data, logo, and boot, and internal storage, plus all apps and data with Titanium Backup, but what about System, System Image, Recovery, OEM, and EFS? What about persist?
Can someone give me a quick summary of what I need to backup to go back to my current state if I want to experiment with some other ROMs?
Thanks.
Click to expand...
Click to collapse
Back up everything available in TWRP, including efs and persist. Then store it all on the cloud. You can never have too much backed up.
Too many people have screwed their devices in this forum by not backing up persist and then applying bad modifications. It is unique to your device and you can't use someone else's to guarantee full functionality.
I backed up all 53 partitions and stored in my harddisk. It's less than 5GB.
I left out only the data partition because for that I use Titanium Backup and RSync.
Yet I haven't backed up the partition table, also this is important...
NZedPred said:
Back up everything available in TWRP, including efs and persist. Then store it all on the cloud. You can never have too much backed up.
Too many people have screwed their devices in this forum by not backing up persist and then applying bad modifications. It is unique to your device and you can't use someone else's to guarantee full functionality.
Click to expand...
Click to collapse
if i backup my efs and persist in a custom rom 64 bits that backup won't work in stock right? it is intact
Backup everything... although it may be too late already, but any working backup is better than nothing.
What you should REALLY do is unlock the bootloader, then before you do anything at all one-time boot TWRP, NOT install it, and backup everything and move it off the device and to the cloud. Once you have rooted or modified your device, even installing TWRP, you are not getting a clean backup.
nicolap8 said:
Yet I haven't backed up the partition table, also this is important...
Click to expand...
Click to collapse
acejavelin said:
What you should REALLY do is unlock the bootloader, then before you do anything at all one-time boot TWRP, NOT install it, and backup everything and move it off the device and to the cloud. Once you have rooted or modified your device, even installing TWRP, you are not getting a clean backup.
Click to expand...
Click to collapse
Have anyone backed up and successfully restored a full partition backup before? I mean running dd if=/dev/block/mmcblk0p* of=/sdcard/*.img for all partitions before installing TWRP. Would restoring it later (after flashing roms and such) return your phone to 100% stock state, being able to re-lock BL, take updates and everything?
prokaryotic cell said:
Have anyone backed up and successfully restored a full partition backup before? I mean running dd if=/dev/block/mmcblk0p* of=/sdcard/*.img for all partitions before installing TWRP. Would restoring it later (after flashing roms and such) return your phone to 100% stock state, being able to re-lock BL, take updates and everything?
Click to expand...
Click to collapse
No... there are some things you cannot write to, period, but the OS can (has to do with encrypted files/partitions I believe), bootloader unlock is one of these things. Many of the mmcblk0 partitions cannot be written to, you can really one write to about 8 or 10 of them via software without having an external writer (for the life of me I can't remember what it's called).
acejavelin said:
No... there are some things you cannot write to, period, but the OS can (has to do with encrypted files/partitions I believe), bootloader unlock is one of these things. Many of the mmcblk0 partitions cannot be written to, you can really one write to about 8 or 10 of them via software without having an external writer (for the life of me I can't remember what it's called).
Click to expand...
Click to collapse
I see. Wasn't expecting to be able to return the bootloader status to untampered, but what matters most is being able to return to a fully working stock rom and take OTAs without bricking the device. There's also all the issues people keep getting in this forum - such as losing their IMEI, 4G, VoLTE - can be those be avoided (and even fixed) by restoring the right backed up mmcblk0 partitions?
prokaryotic cell said:
I see. Wasn't expecting to be able to return the bootloader status to untampered, but what matters most is being able to return to a fully working stock rom and take OTAs without bricking the device. There's also all the issues people keep getting in this forum - such as losing their IMEI, 4G, VoLTE - can be those be avoided (and even fixed) by restoring the right backed up mmcblk0 partitions?
Click to expand...
Click to collapse
Yes, you can restore your efi folder to correct this most of the time, if you have a clean backup. Otherwise you need to get it JTAG programmed
prokaryotic cell said:
I see. Wasn't expecting to be able to return the bootloader status to untampered, but what matters most is being able to return to a fully working stock rom and take OTAs without bricking the device.
Click to expand...
Click to collapse
Just to clarify that you understand, you can't return your bootloader status to untampered but you can lock it again. However it really isn't necessary to do that just to get OTAs. All you need to do is return to your stock with stock recovery and no-root (fastboot method not TWRP flashable.) OTAs work fine once you have done so. I have restored a TWRP backup just by booting into TWRP but it seems like I had some issue unrelated to OTA, although I don't recall what they were and is was on my previous phone (Moto G4).
[Solved (look at bottom of post)]
so, hopfully this is in the right place.
Following the procedure I've done on my nexus 6p many times over; I created a TWRP backup on my 6t then tried restoring the backup I made with twrp and when it finished I pressed reboot to system. The device then only booted into twrp. I saw it was on the "a" partition and I knew I was previously on the b partition so I manually switch partitions and now I'm stuck in fastboot boatloader I have tried flashing a temp twrp.img but im getting an error "FAILED (remote: 'Failed to load/authenticate boot image: Load Error')" in fastboot
After that I switched active partition in fast boot and got into twrp but my data appears to be encrypted and after restoring sys,data,efs,vendor (skipping boot as it holds the recovery now) I only have fast boot in both a/b partitions. I'm going to try to fast boot twerp then install twerp permanently and see if i can get a wotking twrp if not then ill have to get a factory image to get back to stock but was hoping to get some data off but whatever..
I'm kind of new to this a/b partition setup. any help is appreciated.
Edit: for future reference All I was doing was trying to restore a backup? how do I restore a backup on an a/b partition system? As far as I know I did it right...
1) remove lockscreen pin ect..
2) backup boot,sys,ven,data
When restoring
1) mount partitions
2) select restore backup and restore all .....
What am I missing?
____
Solved:
twrp for 6t is borked when it comes to backing up/ restoring...
The version in question: twrp-installer-fajita-3.2.3-1.zip
I restored my 6t to stock with msmdownloadtool and reinstalled twrp then made a test backup. After restoring it I was left in a twrp bootloap and encrypted data partition.
I don't think you should ever need to manually switch slots.
If you are on slot A, and flash an update, it will install to slot B. When you restart your phone, it will automatically switch to B for you.
Also, you shouldn't be flashing the TWRP.img, but booting it instead.
You could try starting fresh with the msmdownloadtool which is found in these forums.
fireeyeeian said:
[Solved (look at bottom of post)]
so, hopfully this is in the right place.
Following the procedure I've done on my nexus 6p many times over; I created a TWRP backup on my 6t then tried restoring the backup I made with twrp and when it finished I pressed reboot to system. The device then only booted into twrp. I saw it was on the "a" partition and I knew I was previously on the b partition so I manually switch partitions and now I'm stuck in fastboot boatloader I have tried flashing a temp twrp.img but im getting an error "FAILED (remote: 'Failed to load/authenticate boot image: Load Error')" in fastboot
After that I switched active partition in fast boot and got into twrp but my data appears to be encrypted and after restoring sys,data,efs,vendor (skipping boot as it holds the recovery now) I only have fast boot in both a/b partitions. I'm going to try to fast boot twerp then install twerp permanently and see if i can get a wotking twrp if not then ill have to get a factory image to get back to stock but was hoping to get some data off but whatever..
I'm kind of new to this a/b partition setup. any help is appreciated.
Edit: for future reference All I was doing was trying to restore a backup? how do I restore a backup on an a/b partition system? As far as I know I did it right...
1) remove lockscreen pin ect..
2) backup boot,sys,ven,data
When restoring
1) mount partitions
2) select restore backup and restore all .....
What am I missing?
____
Solved:
twrp for 6t is borked when it comes to backing up/ restoring...
The version in question: twrp-installer-fajita-3.2.3-1.zip
I restored my 6t to stock with msmdownloadtool and reinstalled twrp then made a test backup. After restoring it I was left in a twrp bootloap and encrypted data partition.
Click to expand...
Click to collapse
I'm currently stuck in TWRP with encrypted data after restoring a backup. I didn't know you couldn't restore backups on this phones. That sucks. I guess I'm going to have to start over now. That really really sucks.
imucarmen said:
I'm currently stuck in TWRP with encrypted data after restoring a backup. I didn't know you couldn't restore backups on this phones. That sucks. I guess I'm going to have to start over now. That really really sucks.
Click to expand...
Click to collapse
Yup, I felt the same.. it's a huge bummer especially when you get it all set up and perfect. Use msm to fix it if you can't use twrp. Hopefully twrp gets fixed soon (I'm really surprised I can't find more people who have noticed this or even twrp team talking about it) for now Im waiting for proof it works on the op6t. I even tried to use Chainfire's flashfire to make a backup and.. no it doesn't work.
fireeyeeian said:
Yup, I felt the same.. it's a huge bummer especially when you get it all set up and perfect. Use msm to fix it if you can't use twrp. Hopefully twrp gets fixed soon (I'm really surprised I can't find more people who have noticed this or even twrp team talking about it) for now Im waiting for proof it works on the op6t. I even tried to use Chainfire's flashfire to make a backup and.. no it doesn't work.
Click to expand...
Click to collapse
I think I just hard bricked my phone. https://forum.xda-developers.com/oneplus-6t/help/bricked-phone-t3914413
imucarmen said:
I think I just hard bricked my phone. https://forum.xda-developers.com/oneplus-6t/help/bricked-phone-t3914413
Click to expand...
Click to collapse
Use Msm download tool:
https://www.google.com/amp/s/forum....-msmdownloadtool-v4-0-oos-9-0-5-t3867448/amp/
I think that's the right post but make sure it matches your device. I used msmdownloadtool around 6 time just testing twrp and only had one hiccup where Msm wasn't detecting my one plus 6t but I eventually got it working.
use the other twrp unofficial but problem you had with would be fixed with big file system fat32 can't do it right
ecompton59 said:
use the other twrp unofficial but problem you had with would be fixed with big file system fat32 can't do it right
Click to expand...
Click to collapse
Could you post a link to it and are you sure? I used the unofficial version so which one are you talking about? I'd really not like to have to re-setup my daily driver from scratch.
https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482 your using early version of twrp the black one is made by same guy download unofficial twrp.zip not twrp.img reboot recovery flash twrp.zip then magisk it may work if not then format data (erases phone) then twrp,magisk reboot recovery to see if it stuck I flash magisk again when it starts up go to magisk thread get the manager 18.1 don't insall it
ecompton59 said:
https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482 your using early version of twrp the black one is made by same guy download unofficial twrp.zip not twrp.img reboot recovery flash twrp.zip then magisk it may work if not then format data (erases phone) then twrp,magisk reboot recovery to see if it stuck I flash magisk again when it starts up go to magisk thread get the manager 18.1 don't insall it
Click to expand...
Click to collapse
Which one? I've tried the 3.2.3.28 last and restoring didn't work. Should I try the most recent installer in the list? And can you confirm that backup&restoring works on the one plus 6t? Also is there anyway to backup my phone without twrp before I try this? I'd really would not like to have to use msm again?
sorry that didn't help format data then flash twrp then magisk should boot without msm
---------- Post added at 01:06 PM ---------- Previous post was at 12:52 PM ----------
i had to use extfat format on htc 8gb backup to get it to work maybe devs will fix that
Has there been an improvement on twrp for the 6t yet? Just curious if I can rely on a backup is there any updates?
I have a completely stock Moto G5 Plus (XT1683 - 2GB of RAM) on stock Oreo 8.1 and I want to use the Pixel Experience 10. I've watched some tutorials online but I still have some questions:
1. I've seen many people complaining that they lost their IMEI and 4G, but I still couldn't figure out if that only happened with people that downgraded from a custom Oreo rom to a stock Nougat or if there's a chance of that happening by installing any custom ROM. My phone has the latest official Oreo version and I've never messed with the system before. Is my phone still at risk of losing its IMEI if I install Pixel Experience 10? What did those people do wrong?
2. Now let's talk about the procedures I have to take. After unlocking the bootloader it will wipe my system, right? If that's so, should I let it boot again into Android and turn off or should I immediately get into fastboot and flash TWRP? Will it make a difference? Will the persist and efs partitions be there on TWRP to be backed up or do I need to let Android boot so it can make them first?
3. After everything, if I get into TWRP and it asks for a password, should I just cancel and wipe the partitions to remove the encryption (can I keep the internal storage?) or do I need to install that dm-verity file instead? As I understand the dm-verity if only for when rooting the phone while keeping the stock system, right? (I don't plan to root my phone, only install a custom ROM. It would also be good if I could keep my files, but if I can't, that's fine too.)
My original plan was the following, please take a look to see if i'll do things correctly.
1. Unlock the bootloader
2. Install TWRP immediately, before it even has a chance to restart
3. If TWRP asks for a password, skip and wipe all the partitions, if it doesn't, wipe them anyway to install the new ROM.
4. Backup efs and persist to my SD Card (will they even be there after I wipe the partitions?)
5. Right after that install the custom ROM
6. Reboot, not get into a bootloop and still have my IMEI. Profit.
Is everything right or did I misunderstand something?
Thanks!
Raploz said:
I have a completely stock Moto G5 Plus (XT1683 - 2GB of RAM) on stock Oreo 8.1 and I want to use the Pixel Experience 10. I've watched some tutorials online but I still have some questions:
1. I've seen many people complaining that they lost their IMEI and 4G, but I still couldn't figure out if that only happened with people that downgraded from a custom Oreo rom to a stock Nougat or if there's a chance of that happening by installing any custom ROM. My phone has the latest official Oreo version and I've never messed with the system before. Is my phone still at risk of losing its IMEI if I install Pixel Experience 10? What did those people do wrong?
2. Now let's talk about the procedures I have to take. After unlocking the bootloader it will wipe my system, right? If that's so, should I let it boot again into Android and turn off or should I immediately get into fastboot and flash TWRP? Will it make a difference? Will the persist and efs partitions be there on TWRP to be backed up or do I need to let Android boot so it can make them first?
3. After everything, if I get into TWRP and it asks for a password, should I just cancel and wipe the partitions to remove the encryption (can I keep the internal storage?) or do I need to install that dm-verity file instead? As I understand the dm-verity if only for when rooting the phone while keeping the stock system, right? (I don't plan to root my phone, only install a custom ROM. It would also be good if I could keep my files, but if I can't, that's fine too.)
My original plan was the following, please take a look to see if i'll do things correctly.
1. Unlock the bootloader
2. Install TWRP immediately, before it even has a chance to restart
3. If TWRP asks for a password, skip and wipe all the partitions, if it doesn't, wipe them anyway to install the new ROM.
4. Backup efs and persist to my SD Card (will they even be there after I wipe the partitions?)
5. Right after that install the custom ROM
6. Reboot, not get into a bootloop and still have my IMEI. Profit.
Is everything right or did I misunderstand something?
Thanks!
Click to expand...
Click to collapse
Answer for your questions
1) losing of IMEI no is possible on custom ROM too, but taking the backup of EFS and persist will retrieve them, so no problem. And losing of IMEI is random occur when moving from one rom to other.
2) just let the android boot once, so everything get loads up with unlock bootloader (no need to setup).
3)after installing the twrp, it won't ask for password since your device got format when unlocking bootloader, so it won't ask. If you want to remove encryption then format< type yes. It will remove your encryption.
4) for talking backup of EFS and persist use this method.
Code:
Use the following command to create a backup and save it at /sdcard/persist.img:
dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img
To restore use the following command:
dd if=/sdcard/persist.img of=/dev/block/bootdevice/by-name/persist
If you have saved a backup using different name then use that name instead.
And seeing your plan, everything seem good, you can continue with your plan.
Note:- for some user PE won't work for them with 2gb version, so I suggest you to take a backup of stock ROM or keep an other rom file in case it needed.