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!
Related
hello all
i have ZTE AXON 7 U model.
i did bootloader unloock and instaled TWRP 3041 and did this "Once you booted to TWRP , Tap Mount and Check "Mount, System as Read-only", this is very important".
now im on the A2017UV1.1.0B15_systemstock_by_DrakenFX.zip. all works great.
in twrp when i do backup and want to restore it i get this massage: " cannot restore system--mounted read only".
how can i backup and restore in the wright way?
ty all
le011 said:
hello all
i have ZTE AXON 7 U model.
i did bootloader unloock and instaled TWRP 3041 and did this "Once you booted to TWRP , Tap Mount and Check "Mount, System as Read-only", this is very important".
now im on the A2017UV1.1.0B15_systemstock_by_DrakenFX.zip. all works great.
in twrp when i do backup and want to restore it i get this massage: " cannot restore system--mounted read only".
how can i backup and restore in the wright way?
ty all
Click to expand...
Click to collapse
"Mount and Check "Mount, System as Read-only", this is very important".
What you have quoted is only to complete the installation Flash. Go ahead and uncheck 'Mount System Read-Only' for normal operation and you are ready to go!
amphi66 said:
"Mount and Check "Mount, System as Read-only", this is very important".
What you have quoted is only to complete the installation Flash. Go ahead and uncheck 'Mount System Read-Only' for normal operation and you are ready to go!
Click to expand...
Click to collapse
To for your replay.
When I unchecked the System read only and trying to restore the phone from the backup I made in Twrp the phone stucks after reboot on the screen that says the bootloader is unlocked and that's it.
le011 said:
To for your replay.
When I unchecked the System read only and trying to restore the phone from the backup I made in Twrp the phone stucks after reboot on the screen that says the bootloader is unlocked and that's it.
Click to expand...
Click to collapse
You should see that screen and the phone should continue to boot after 5 seconds.
To recap:
1. You stated all was fine in B15 after following the upgrade steps.
2. You made a TWRP backup (system, data & boot) of your new B15
3. When attempting to TWRP restore the B15 backup it could not as system was still mounted "read only"
4. You unchecked "read only" and then did the restore
5. Now system does not boot (hangs on bootloader unlocked warning screen)
If that is correct it sounds as if you have a bad or incomplete B15 backup or you are attempting to restore a B29 backup to a B15 bootstack.
amphi66 said:
You should see that screen and the phone should continue to boot after 5 seconds.
To recap:
1. You stated all was fine in B15 after following the upgrade steps.
2. You made a TWRP backup (system, data & boot) of your new B15
3. When attempting to TWRP restore the B15 backup it could not as system was still mounted "read only"
4. You unchecked "read only" and then did the restore
5. Now system does not boot (hangs on bootloader unlocked warning screen)
If that is correct it sounds as if you have a bad or incomplete B15 backup or you are attempting to restore a B29 backup to a B15 bootstack.
Click to expand...
Click to collapse
All correct.
After Im making backup, I'm wiping, and trying to restore the backup I just did.
No luck.
le011 said:
All correct.
After Im making backup, I'm wiping, and trying to restore the backup I just did.
No luck.
Click to expand...
Click to collapse
Confusing to me. How are you using phone after a bad restore?
What revision TWRP did you flash? Did you flash SU 2.79 after flashing ROM?
Perhaps someone w/ more knowledge can chime in, but sounds as if you are a candidate to begin again following the steps carefully
Goodluck
amphi66 said:
Confusing to me. How are you using phone after a bad restore?
What revision TWRP did you flash? Did you flash SU 2.79 after flashing ROM?
Perhaps someone w/ more knowledge can chime in, but sounds as if you are a candidate to begin again following the steps carefully
Goodluck
Click to expand...
Click to collapse
hi
i have TWRP version 3041.
after i'm trying to restore and wont succeeded , i flash the rom again. the rom im flashing is : A2017UV1.1.0B15_systemstock_by_DrakenFX.
then the phone boot up and work great.
im not flashing supersu because i dont want root.
le011 said:
hi
i have TWRP version 3041.
after i'm trying to restore and wont succeeded , i flash the rom again. the rom im flashing is : A2017UV1.1.0B15_systemstock_by_DrakenFX.
then the phone boot up and work great.
im not flashing supersu because i dont want root.
Click to expand...
Click to collapse
Interesting. How long are you waiting on the Bootloader unlocked warning screen?
Next time in TWRP look at the data partition and verify it is formatted as ext4 not f2fs. I might also download a different version of TWRP and reflash the IMG file from within TWRP. I reference @DrakenFX here as he may have the easy solution.
amphi66 said:
Interesting. How long are you waiting on the Bootloader unlocked warning screen?
Next time in TWRP look at the data partition and verify it is formatted as ext4 not f2fs. I might also download a different version of TWRP and reflash the IMG file from within TWRP. I reference @DrakenFX here as he may have the easy solution.
Click to expand...
Click to collapse
How i check in TWRP how the data partition formated?
I trayid the new version of TWRP 3100 and same thing.
after restoring the phone stuck on the Bootloader unlocked warning screen -last time i waited for 5 min before i
shut down whit power button.
le011 said:
hi
i have TWRP version 3041.
after i'm trying to restore and wont succeeded , i flash the rom again. the rom im flashing is : A2017UV1.1.0B15_systemstock_by_DrakenFX.
then the phone boot up and work great.
im not flashing supersu because i dont want root.
Click to expand...
Click to collapse
amphi66 said:
Interesting. How long are you waiting on the Bootloader unlocked warning screen?
Next time in TWRP look at the data partition and verify it is formatted as ext4 not f2fs. I might also download a different version of TWRP and reflash the IMG file from within TWRP. I reference @DrakenFX here as he may have the easy solution.
Click to expand...
Click to collapse
Easy fix, go back to TWRP,
* Wipe Data (if you are in different ROM a or version) - Dalvik- Cache
* Check MOUNT SYSTEM AS READ-ONLY
* Reflash B15 system
Happy reboot
If you Previously were using B15 , you may restore data only, other wise is a no go.
DrakenFX said:
Easy fix, go back to TWRP,
* Wipe Data - Dalvik- Cache
* Check MOUNT SYSTEM AS READ-ONLY
* Reflash B15 system
Happy rebokt
Click to expand...
Click to collapse
hi
i did that for 3 tomes ending whit the same result :
the rom working great after clean instal...restoring from TWRP....ending whit stuck phone.
le011 said:
How i check in TWRP how the data partition formated?
I trayid the new version of TWRP 3100 and same thing.
after restoring the phone stuck on the Bootloader unlocked warning screen -last time i waited for 5 min before i
shut down whit power button.
Click to expand...
Click to collapse
You may not have seen this on another thread with a similar issue:
"did find something else out. Under [TWRP] settings, if I enabled the "Use rm -rf instead of formatting", then I can restore successfully."
Goodluck
amphi66 said:
You may not have seen this on another thread with a similar issue:
"did find something else out. Under [TWRP] settings, if I enabled the "Use rm -rf instead of formatting", then I can restore successfully."
Goodluck
Click to expand...
Click to collapse
OK ty
i will try that and post if sucssed.
History of what I did:
I first installed the first small OTA Update to 4.5.1 then unlocked the Bootloader and flashed TWRP v46 from xdvs23. And made a full TWRP Backup and flashed Magisk afterwards.
Everything worked fine until I debloated the System and wanted to make the OTA Update to 4.5.2 (1,5 GB), which didn't work. After I flashed it, the phone didnt boot anymore. So I restored the TWRP Backup, which doesn't work either.
Current status:
TWRP v58 is flashed and works. I can flash ExcperienceOS from Jamal, which works fine, too. But flashing the OTA file doesn't work and restoring my backup wont work either -_-
I would really appreciate help to get back to an OTA updatable version of OxygenOS!
If you still have the TWRP installed I would download the full 4.5.2 zip (Listed elsewhere on these forums) and use adb sideload to install it, then proceed again from there.
djsubterrain said:
If you still have the TWRP installed I would download the full 4.5.2 zip (Listed elsewhere on these forums) and use adb sideload to install it, then proceed again from there.
Click to expand...
Click to collapse
I did that several times. It doesn't work sadly... I get into a bootloop
You didn't erase your userdata partition by mistake did you? You could try going into fastboot mode and use the command:
fastboot format userdata
Obviously this will wipe the userdata partition but the phone is acting like there's no userdata partition anyway
djsubterrain said:
You didn't erase your userdata partition by mistake did you? You could try going into fastboot mode and use the command:
fastboot format userdata
Obviously this will wipe the userdata partition but the phone is acting like there's no userdata partition anyway
Click to expand...
Click to collapse
I might have, I will try that, thanks
Or just wipe everything, flash stock recovery, and flash Full OxygenOS zip.
https://forum.xda-developers.com/showpost.php?p=72799046&postcount=2
I formated the userdata and flashed the .zip from the link, but I still get a bootloop...
I still don't understand what I am doing wrong...
How about trying to wipe everything from wipe menu except internal storage and then flash the oos zip followed by lazy flasher zip from here - bit.ly/lazyflasher
If this doesn't work then try changing to a different version of TWRP!
Casual_Max said:
I formated the userdata and flashed the .zip from the link, but I still get a bootloop...
I still don't understand what I am doing wrong...
Click to expand...
Click to collapse
You didn't do these steps wrong by any chance?
Steps To Disable Forced Encryption i.e, Decrypt Data
1. At first time when you open twrp, it will ask you to allow system modification.
2. Allow it and then flash the no-verity-opt-encrypt.zip file .
3. Then Go to Wipe-->Format Data.
4. Type Yes to confirm wiping of Internal Storage.
5. Now you have decrypted the data sucessfully.
Note: Dont try to restore the nanodroid backup which you have taken before. It may end in bootloop.
Click to expand...
Click to collapse
From here:
https://forum.xda-developers.com/on...der-intall-t3626122/post72777899#post72777899
ok, there I see what caused my first bootloop. Thanks
But why doesn't flashing the Stock ROM .ZIP work on an wiped (fastboot format userdata) phone? What else do I have to do?
EDIT:
*** solved ***
I failed hard. Luckily the OnePlus Support is excellent and was able to fix my issue with a remote session using their official tools. The Phone and I are both happy again.
Thanks for all the help, though. I learned quite a lot while dealing with this issue. It's a very kind and nice community here
I have installed FreedomOS on my OnePlus 5. I'm not sure if this is related to FreedomOS, but when I try to make a backup in TWRP with data, system, and boot, it has an error with createTarFork() shortly after it gets to backing up data. It also says 'read only filesystem' when I try to open Terminal from Advanced and run 'cd /data/media/0/TWRP/BACKUPS/bad7d639 && rm -rf backup-name'. What can I do to fix this and why is this happening?
EDIT: I have 32GB storage left
I had error 255 when restoring the data partition on my elephone p9000, for me it was because it was a bad data write and it was corrupt.
Pro4TLZZ said:
I had error 255 when restoring the data partition on my elephone p9000, for me it was because it was a bad data write and it was corrupt.
Click to expand...
Click to collapse
What was corrupt? How did you fix it?
keeganjk said:
What was corrupt? How did you fix it?
Click to expand...
Click to collapse
Something in the partition, so I didn't restore that
Pro4TLZZ said:
Something in the partition, so I didn't restore that
Click to expand...
Click to collapse
Which partition? I just wiped my device and reinstalled FreedomOS.
keeganjk said:
Which partition? I just wiped my device and reinstalled FreedomOS.
Click to expand...
Click to collapse
Userdata partition
Pro4TLZZ said:
Userdata partition
Click to expand...
Click to collapse
OK.
Pro4TLZZ said:
Userdata partition
Click to expand...
Click to collapse
I wiped my device and reinstalled FreedomOS, it still shows up with the same error.
keeganjk said:
I wiped my device and reinstalled FreedomOS, it still shows up with the same error.
Click to expand...
Click to collapse
I'm sorry I can't help you more
Hi guy, i had the problem, try to flash blue spark recovery and retry restore, if rom bootloops, try to dirty flash your rom
I just wiped and reinstalled OxygenOS http://downloads.oneplus.net/oneplus-5/oneplus_5_oxygenos_4.5.10/. Once I reconfigure all my settings, files, etc, I'm going to see if it works.
dago said:
Hi guy, i had the problem, try to flash blue spark recovery and retry restore, if rom bootloops, try to dirty flash your rom
Click to expand...
Click to collapse
What's the difference between TWRP and bluspark TWRP?
dago said:
Hi guy, i had the problem, try to flash blue spark recovery and retry restore, if rom bootloops, try to dirty flash your rom
Click to expand...
Click to collapse
I can't restore; I deleted all my backups in an attempt to free up space.
I think I found the solution!
1. Go to Wipe in TWRP, swipe to factory reset
2. Download:
OnePlus Recovery: http://oxygenos.oneplus.net.s3.amazonaws.com/OP5_recovery.img
OxygenOS: http://oxygenos.oneplus.net.s3.amaz...3_OTA_015_all_1708252353_e6d7756780064352.zip
3. Rename recovery image as recovery.img, boot phone into fastboot, plug into computer, run these commands on the computer:
fastboot devices
fastboot flash recovery recovery.img
fastboot boot recovery.img
4. Open recovery on phone
5. Select Forgot Password, will wipe all leftover files in SD Card.
6. Boot back into recovery, select reload, select Install over ADB or Install Over USB or something similar and plug phone into computer.
7. Run 'adb sideload oxygen-os-filename' without quotes on computer.
8. Let it install OxygenOS, it may appear to be frozen at some points; it probobaly isn't, so don't shut it off or unplus USB.
9. Download Bluspark TWRP: https://forum.xda-developers.com/devdb/project/dl/?id=26601&task=get
9. Reboot into fastboot, plug into computer and run these commands on the computer:
fastboot devices
fastboot flash recovery bluspark-twrp-filename-location.img
fastboot boot bluspark-twrp-filename-location.img
10. Success (hopefully)
Oh. Wait. Now it has the same error when I try to make a backup. (I feel like it might be from installing https://forum.xda-developers.com/android/software-hacking/kali-nethunter-magisk-t3676681, but they say it's unrelated). Doors anyone know why this is happening again?
the solution to this was to boot to your previous rom that u have made nandroid backup with and then setting up the same password/pin in settings > security. When you then boot into twrp it will ask you for the pin/password to decrypt your data partition and then you can flash the nandroid backup(you have to have the same password there). here it is obvious that you are trying to flash data partition that uses different encryption password (in case of stock rom there is non) and this obviously wont happen.
maybe another solution would be to connect externally usb and unmounting data partition and then restoring from usb...
I'm having the exact same issue, but trying to create a Nandroid, not restoring one. Happened on Codeworkx TWRP 20180414. I always remove my passwords, fingerprint, pattern, and face data before I backup, update, etc. since I'm encrypted to avoid issues, and it still happened. I flashed the latest blu_spark TWRP and got the exact same error in the same spot in the data partition backup.
Never had an issue like this before. I even tried saving the data partition separately and still got the same error. Very strange indeed.
All other partitions backup without issue.
I'm on xXx v10.5 w/ ElementalX v3.04, Encrypted
If anyone has any insight, it would be greatly appreciated.
Thanks much!
?
Need4Sneed said:
I'm having the exact same issue, but trying to create a Nandroid, not restoring one. Happened on Codeworkx TWRP 20180414. I always remove my passwords, fingerprint, pattern, and face data before I backup, update, etc. since I'm encrypted to avoid issues, and it still happened. I flashed the latest blu_spark TWRP and got the exact same error in the same spot in the data partition backup.
Never had an issue like this before. I even tried saving the data partition separately and still got the same error. Very strange indeed.
All other partitions backup without issue.
I'm on xXx v10.5 w/ ElementalX v3.04, Encrypted
If anyone has any insight, it would be greatly appreciated.
Thanks much!
?
Click to expand...
Click to collapse
For me flashing normal oxygenos with magisk 16 and formatting data and trying to make it boot with the new flash and then rebooting into recovery and restoring made it work. I guess it has to do with the right filesystem having to be made first.
hi guys,
i've read all the thread in XDA related to ERROR 255, can't find anything to solve my problem trying to backup on TWRP ending with this error 255.?
I'm not using any parallel apps, not using Apps Locker, don't have any folder 999 (searched using Root Browser).
I've tried deleting all fingerprint, face unlock and screenlock as well.
No joy.
I'm using latest TWRP 3.2.2-1, OOS 5.1.7, Rooted.
Appreciate any help or sharing experience.
My phone was stuck in a bootloop where it could only get to recovery. Using the recovery I created a nandroid backup to the a USB stick using an OTG cable. I flashed the stock firmware and got things setup but I can't restore individuals apps from the nandroid. I copied the nandroid from the usb to sd card but it still doesn't work. I tried restoring apps using Nandroid Manager but when the app is launched it gives the error "app has stopped, close app". For some reasons sms succesfully restored but no user apps. I tried restoring with AppExtractor but it gives the error "unable to generate apk listing"
I also have titanium backup pro but couldn't get it to find the location of the nandroid to try extracting with it.
Any ideas? I really just want my messages back from Whatsapp.
My phone had stock Nougat with busybox installed and elementalx kernel. It should be the same environment now as when the backups were made.
@twoplustwo can you tell us why your phone went into bootloop ? If you know then you can restore /data from TWRP and revert the cause of bootloop..
Also can you confirm it's in capital letters as you have mentioned in small letters in another thread that twrp/backups rename them to TWRP/BACKUPS or move them to internal storage.. (in stock ROM if i am not wrong, TWRP folder is not accessible, so try to install custom ROM for temporary purpose, then move backup to internal and then try with titanium backup..)
____Mdd said:
@twoplustwo can you tell us why your phone went into bootloop ? If you know then you can restore /data from TWRP and revert the cause of bootloop..
Also can you confirm it's in capital letters as you have mentioned in small letters in another thread that twrp/backups rename them to TWRP/BACKUPS or move them to internal storage.. (in stock ROM if i am not wrong, TWRP folder is not accessible, so try to install custom ROM for temporary purpose, then move backup to internal and then try with titanium backup..)
Click to expand...
Click to collapse
yes it was in capital letters
the problem in the first place that sent the phone into a bootloop was I installed the OTA security update. I'm running stock rom but I guess because it was rooted and had busybox, that made it incompatible with the update?
twoplustwo said:
yes it was in capital letters
the problem in the first place that sent the phone into a bootloop was I installed the OTA security update. I'm running stock rom but I guess because it was rooted and had busybox, that made it incompatible with the update?
Click to expand...
Click to collapse
If you have TWRP and take update, it don't cause bootloop, but it cause your device to boot into recovery when you turn on your device.. can you confirm if it was bootloop or problem of booting to TWRP ?
I am unable to copy the nandroid to internal storage. I tried using usb to computer and it just does nothing. I tried root explorer and it says 'copy failed' and file manager says 'cannot load'. This only happens with the TWRP folder inside the internal memory specifically.
____Mdd said:
@twoplustwo can you tell us why your phone went into bootloop ? If you know then you can restore /data from TWRP and revert the cause of bootloop..
Also can you confirm it's in capital letters as you have mentioned in small letters in another thread that twrp/backups rename them to TWRP/BACKUPS or move them to internal storage.. (in stock ROM if i am not wrong, TWRP folder is not accessible, so try to install custom ROM for temporary purpose, then move backup to internal and then try with titanium backup..)
Click to expand...
Click to collapse
____Mdd said:
If you have TWRP and take update, it don't cause bootloop, but it cause your device to boot into recovery when you turn on your device.. can you confirm if it was bootloop or problem of booting to TWRP ?
Click to expand...
Click to collapse
I can confirm it was only booting TWRP. So even when I tried to boot to system it just booted to TWRP again.
twoplustwo said:
I can confirm it was only booting TWRP. So even when I tried to boot to system it just booted to TWRP again.
Click to expand...
Click to collapse
You don't need to worry,
Do you have any important data for any app currently ?
Take backup of new important data with titanium.. (and then again take backup from TWRP, for safety )
And then simply restore /data from TWRP backup, it will give you older data back without any bootloop but you will loose new data/messages that you got after flashing/ on current running ROM..
____Mdd said:
You don't need to worry,
Do you have any important data for any app currently ?
Take backup of new important data with titanium.. (and then again take backup from TWRP, for safety )
And then simply restore /data from TWRP backup, it will give you older data back without any bootloop but you will loose new data/messages that you got after flashing/ on current running ROM..
Click to expand...
Click to collapse
Thank you sir! To confirm, when backing up to USB stick with OTG, does the format of the USB matter? Is fat32 safe?
twoplustwo said:
Thank you sir! To confirm, when backing up to USB stick with OTG, does the format of the USB matter? Is fat32 safe?
Click to expand...
Click to collapse
Not familiar with different formats, it should work.. bu t
You can backup to internal storage too, since you don't have to flash fastboot ROM again..
____Mdd said:
Not familiar with different formats, it should work.. bu t
You can backup to internal storage too, since you don't have to flash fastboot ROM again..
Click to expand...
Click to collapse
Just want to confirm everything is working perfect now. Thank you again!
[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?