Can anybody help?
My HTC U11 still run on Nougat.
Yesterday I want to update with the newer version of Nougat (Not Oreo)
I already make a data backup with TWRP, big backup 22Gb.
Then I update the new stock Rom from PC, it had no problem.
Go to download mode, and then install TWRP again with ADB from PC.
Go to TWRP Recovery, it still works.
The last thing I do is to try to restore the 22Gb data back to my phone.
And it always get error on 9% with "extractTarFork() process ended with ERROR: 255"
I already change with difference TWRP from 3.1.1.0 to 3.2.3.0, still the same.
Restore to previous version of Nougat with TWRP (system, system image, boot image, recovery). Try to restore backup data again with no luck.
Try to check MD5 with the backup data, and it said matched, no corrupt.
Already try searching in the web, but with no solution too.
Do anyone ever have the same problem and solved it?
Not me here, but you can try RUU manually flash Oreo
Related
I'm currently at pixel npf26j (canadian version), now I can't update through the OS because it results in an error.
I want to go back to stock, keeping twrp recovery and i've tried to flash (using twrp) one of the full factory stock images from developers.google.com/android/images -> This one: 7.1.1 (NMF26V, Jan 2017, Europe/O2). But it gives me the error: Could not find 'META-INF/com/google/android/update-binary' in the zip. Error installing zup file....
I can't install without TWRP because i don't have a usb c cable that fits with my Macbook through USB.
How do i flash this zip? Do I have to wipe through TWRP first before installing this full factory zip? Or is this zip not flashable?
please help!
there is a full unroot option somewhere its either in the twrp boot menu or its in superSU. But its supposedly erases everything and takes you back to stock.
twilk73 said:
there is a full unroot option somewhere its either in the twrp boot menu or its in superSU. But its supposedly erases everything and takes you back to stock.
Click to expand...
Click to collapse
I kind of having same issue. I tried flashing my full nandroid backup in twrp. Im on pure nexus. Got all the way to the vendor and gave me an error. So I wiped data and tried to flash pure nexus again and now I get cannot Mount storage. Is this because my nandroid backup is on the u vendor and in on v now. I ended up switching slots in twrp and was able to flash pure nexus again. How can I restore my backup?
tim2301 said:
I'm currently at pixel npf26j (canadian version), now I can't update through the OS because it results in an error.
I want to go back to stock, keeping twrp recovery and i've tried to flash (using twrp) one of the full factory stock images from developers.google.com/android/images -> This one: 7.1.1 (NMF26V, Jan 2017, Europe/O2). But it gives me the error: Could not find 'META-INF/com/google/android/update-binary' in the zip. Error installing zup file....
I can't install without TWRP because i don't have a usb c cable that fits with my Macbook through USB.
How do i flash this zip? Do I have to wipe through TWRP first before installing this full factory zip? Or is this zip not flashable?
please help!
Click to expand...
Click to collapse
To go back to stock and be on the latest factory image you need a USB cable. You cannot flash factory images with twrp. And you cannot take the ota with twrp installed.
Hi guys i was trying to install a custom rom on my mate 9 (MHA-L29C432-156)so i followed the instructions ; unlocked the bootloader; then installed twrp 3.1.0-0; on twrp formated data; then full wiped and try to install AurRom from SD; but get a message that zip file is corrupted; so I tried with S.H.I.E.L.D ROM and it flashed , but then when boot goes to eRecovery, and give me 3 options download latest version and recovery; reboot and shutdown. So now I cant boot the phone, when I restarted, followed same steps , format data, full wipe and trying to installing again but getting a message about all zip files of the roms are corrupted; then i try to restore backup; and same again get the huawei logo, then the android logo , phone restarts and eRecovery again.
Please someone HELP, I use this phone for my work...........!!!!!!!!!
How did you full wipe?
Also try with Twrp 3.0.2-2
Here:www.androidfilehost.com/?fid=745425885120697579
dannytgt said:
on twrp formated data
Click to expand...
Click to collapse
Something went wrong here. You can run 'adb logcat' to see the crash details while starting.
If you have a backup on twrp then restore to get phone working. You may need to flash the public and hw-data zips afterwards though.
If you don't have a backup then you could try flashing the C636 off line firmware and then use firmware finder to go back to your original firmware
Sent from my MHA-L09 using XDA-Developers Legacy app
you may just flash the modified recovery ( See Guide subforum ) ) to bypass the update certification and authorization and reflash an original firmware. your stored files will be lost anyway in most cases.
I would bet superuser ( shield ) and SuperSU ( Aurom) messed your boot image. Both are incompatible to each other and, afaik both are incompatible to twrp 3.1.
Flash TWRP 3.0.2.2, reboot to recovery again to change version, flash the rom ( f.e. shield rom), boot once up, reboot to recovery and THEN you may flash twrp 3.1
Thanks all of you guys, I've solved the problem, it seems that's something related to the sd card, I've formated the sd and transfer the files trough another phone and then put the sd on the mate 9, I follow the steps as followed before and works successfully, now I'm on AurRom and 182 firmware.
Hi all,
A couple of days ago I flashed the OTA image for 8.1. Realising I don't have root and not finding a way to root 8.1 yet, I figured, hey, I'll go back to 8.0. Luckily I did a full backup using TWRP before upgrading.
TWRP 3.1.1 was unable to decrypt the filesystem and therefore restore anything (which I've read is a known issue). Neither could 3.2.1, and 3.2.1 couldn't see the OTG drive I have the backup on, either.
At this point I'd already wrecked the OS by trying to restore without first decrypting the filesystem (figured it'd just overwrite it so who cares). So I flashed the latest 8.0 factory image, started it up to make sure it boots, went back into TWRP and restored the full backup from the OTG drive.
This succeeds - but when rebooting all I get is the initial Google logo. Nothing else. No loop, no progress meter, nothing.
Am I missing a step? Anyone?
jethro1138 said:
Hi all,
A couple of days ago I flashed the OTA image for 8.1. Realising I don't have root and not finding a way to root 8.1 yet, I figured, hey, I'll go back to 8.0. Luckily I did a full backup using TWRP before upgrading.
TWRP 3.1.1 was unable to decrypt the filesystem and therefore restore anything (which I've read is a known issue). Neither could 3.2.1, and 3.2.1 couldn't see the OTG drive I have the backup on, either.
At this point I'd already wrecked the OS by trying to restore without first decrypting the filesystem (figured it'd just overwrite it so who cares). So I flashed the latest 8.0 factory image, started it up to make sure it boots, went back into TWRP and restored the full backup from the OTG drive.
This succeeds - but when rebooting all I get is the initial Google logo. Nothing else. No loop, no progress meter, nothing.
Am I missing a step? Anyone?
Click to expand...
Click to collapse
Had you ever tried restoring the backup before to verify it was stable? Perhaps there was some corruption in the backup file?
Well, it is able to restore the whole thing without an error. I think that counts as verifying that it's not corrupt...
I'm facing the same exact issue. I've got several previous backups of my Pixel, all of 8.1, and if I try restoring any partition except /data they restore successfully and boot as a fresh phone.
Now of course I need my data, but when I try to restore any of my previously backed up /data partitions, they either freeze during restoration or restore successfully. However if they do restore successfully, my phone won't boot anymore. After showing the Google logo, then animated G, it reboots back to recovery.
I tried most things as of now but to no avail. This really sucks!
Tried to clean flash unlocked and rooted OP6 from OOS 9.05 to 10.3 and got stuck in "bootloader unlocked" (only later learned that I should have gone via 9.09 to 10). Tried to restore Nandroid, but this did not work either and even lost the recovery.
Now I can go to recovery only via "fastboot boot" and only using twrp-3.3.1-18-enchilada-Q-mauronofrio.img (none of the other recoveries I tried will boot). I tried to restore the backup (with and without reflashing twrp-3.3.1-18-Q zip afterwards) but never manage to boot back to system (maybe because the restore is 9.05 and the above TWRP is OOS10; it starts up with the ASOP10 log ?)
Is there a way to restore 9.05 with the nandroid without wiping the user data ?
(like flashing the nandroid twice on slot A and B and flashing the correct TWRP and/or Magisk afterwards) ?
ebar3 said:
Tried to clean flash unlocked and rooted OP6 from OOS 9.05 to 10.3 and got stuck in "bootloader unlocked" ?
Click to expand...
Click to collapse
Problem solved!
I followed this post https://forum.xda-developers.com/showpost.php?p=78915106&postcount=2
(reflash same ROM and Magisk versions as those originally installed, then restore nandroid backup).
3 things to note which were not obvious to me:
- Unzipp ALL files into one single folder (same ROMs have zips within zips)
- use the "flash-all-partitions-fastboot.bat" file,
- answer NO to the first question "Wipe all data (recommended)". If not, the internal data (data/media) will be wiped as well, including your nandroid backup and other info (music, photo..). If you have to wipe, make sure the backup is on the PC
Hi there, Thaught, I was on the save side for 2 years, having my TWRP, made a backup after every change on the 12+, now I had to recover it...
Steady installed TWRP 3.3.1.0 on 1.68.401.6 does a restore without errors, restart ends with bootloop.
So I flashed new with 1.53.401.5, tried to fastboot boot twrp.3.2.3.3 and restore my backup -> bootloop
Flashed 1.53.401.5 again, made a backup of that fresh system with booted TWRP, to test that restore, brings the same bootloop.
Have to say, the twrp versions are the right ones for the used SW versions. Decryption is working.
Where is the blind spot in my brain??
Please delete my ask here, I'll try my luck in TWRP thread. Still my problem.