Related
Hello everyone.
By being stupid, I formatted every partition on my N4, except the bootloader and the recovery. I want to recover some images and videos. I found this tutorial. But the trick is not to touch the data partition because it may overwrite the deleted files.
I need to install some custom ROM or system image.
Since I can't put anything on the sdcard, I was going to use fastboot, and flash factory system image. However, in order to dump the partition, I need to have BusyBox installed. So the question is, can I install busybox with fastboot, or push it with adb push?
Or another question is, do I even need to install factory image. I do have the TWRP recovery installed, can I just push the busybox binaries? I don't know if I need any other files...
Your help is very appreciated.
Thank you very much.
vitya said:
Hello everyone.
By being stupid, I formatted every partition on my N4, except the bootloader and the recovery. I want to recover some images and videos. I found this tutorial. But the trick is not to touch the data partition because it may overwrite the deleted files.
I need to install some custom ROM or system image.
Since I can't put anything on the sdcard, I was going to use fastboot, and flash factory system image. However, in order to dump the partition, I need to have BusyBox installed. So the question is, can I install busybox with fastboot, or push it with adb push?
Or another question is, do I even need to install factory image. I do have the TWRP recovery installed, can I just push the busybox binaries? I don't know if I need any other files...
Your help is very appreciated.
Thank you very much.
Click to expand...
Click to collapse
If you have TWRP, try pushing busybox from adb and then run the commands
It worked.
moxtrom, thanks for your reply.
So yesterday I got home and tried the steps.
First I pushed busybox and su as instructed in this tutorial:
http://dottech.org/87443/how-to-root-nexus-4-guide/
The last step says to do busybox -install, and that didn't work for me. But it didn't matter because the rest of the steps worked fine.
From there I followed the steps from the tutorial on how to recover the files and everything worked perfectly, except now I have bunch of files with weird file names that I have sort through.
I'll see if I can find a tool that maybe can restore the whole partition, because the data partition should be all good, it's just been formatted.
moxtrom said:
If you have TWRP, try pushing busybox from adb and then run the commands
Click to expand...
Click to collapse
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
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.
I friend and his girlfriend both have identical Mi A1 (stock, unmodified, except bootloader unlocked).
Both always successfully OTA upgraded in the past (up to Oreo July Android security patch level V9.6.4.0).
Now both were presented with the August security patch level V9.6.5.0 OTA upgrade.
One of the devices upgraded successfully.
The other one downloaded upgrade successfully, but gets an error during install.
Style "something went wrong". My friend tried twice.
Does this ring any bell?
I can always try to help him with fastboot or twrp V9.6.5.0 stock zip or with V9.6.4.0 to V9.6.5.0 OTA zip
(all posted in other thread in MiA1 forum) .
But, I thought about asking for potential similar experiences here first.
Have a nice day.
Unmodified but did he ever boot twrp?
Be sure to check both partition A/B. For example, It is possible to have TWRP Recovery in Partition A and Stock recovery in Partition B.
Assuming current active partition is in Partition B, then while updating the OTA, it'll build the image in Partition A, then it'll reboot and try to flash via Recovery, but the Recovery is TWRP, and error is thrown.
For my case, my failed case is because I did not uninstall Magisk, be sure to uninstall Magisk
@myself379 and @.:Addicted:.
I thought about non stock recovery partition too (be it in A or B or both).
I once booted TWRP recovery-3.2.1-2-oreo.img over USB to make a TWRP backup. I did not allow TWRP to install itself, but maybe it did, one never knows there is a bug ... I will soon have opportunity to check next time my friend comes to visit me again with his device.
Keep you informed.
Dior DNA said:
@myself379 and @.:Addicted:.
I thought about non stock recovery partition too (be it in A or B or both).
I once booted TWRP recovery-3.2.1-2-oreo.img over USB to make a TWRP backup. I did not allow TWRP to install itself, but maybe it did, one never knows there is a bug ... I will soon have opportunity to check next time my friend comes to visit me again with his device.
Keep you informed.
Click to expand...
Click to collapse
If you booted twrp & mounted system rw & not read only, thqt may be the cause.
Reflash system & boot partition to both slot through fastboot.
.:Addicted:. said:
If you booted twrp & mounted system rw & not read only, thqt may be the cause.
Reflash system & boot partition to both slot through fastboot.
Click to expand...
Click to collapse
Correct, I always ignore the system rw warning with TWRP.
Not sure though how that would influence stock recovery to not flash OTA, if, say, that system rw mount happened weeks ago in TWRP booted over USB from fastboot. Would TWRP have written something in system?
I can indeed flash system & boot partition through fastboot. I guess you mean: flash old system & boot partition right?
In the future, when booting TWRP over USB from fastboot, I will disallow system rw mount (which indeed is not needed just for taking TWRP backup),
Thanks for help.
Dior DNA said:
Correct, I always ignore the system rw warning with TWRP.
Not sure tough how that would influence stock recovery to not flash OTA, if, say, that system rw mount happened weeks ago in TWRP booted over USB from fastboot. Would TWRP have written something in system?
I can indeed flash system & boot partition through fastboot. I guess you mean: flash old system & boot partition right?
In the future, when booting TWRP over USB from fastboot, I will disallow system rw mount (which indeed is not needed just for taking TWRP backup),
Thanks for help.
Click to expand...
Click to collapse
As soon as you mount system as R/W, OTA will fail. It doesn't matter if you write something to the partition or not.
Also first reconfigure TWRP and then reflash the stock system, as TWRP remembers its settings and next time you boot into TWRP, your system partition will be mounted as R/W and you are in the same situation again..
_mysiak_ said:
As soon as you mount system as R/W, OTA will fail. It doesn't matter if you write something to the partition or not.
Also first reconfigure TWRP and then reflash the stock system, as TWRP remembers its settings and next time you boot into TWRP, your system partition will be mounted as R/W and you are in the same situation again..
Click to expand...
Click to collapse
Thanks for reaction.
It must be my poor understanding or imagination .
I have never flashed TWRP : the recovery is stock, in fact everything is stock. I only booted device once via fastboot over USB in TWRP (to make a TWRP backup). If just during that TWRP boot system was mounted rw, how would that affect OTA update weeks, months or years later on an otherwise always stock device?
Dior DNA said:
Thanks for reaction.
It must be my poor understanding or imagination .
I have never flashed TWRP : the recovery is stock, in fact everything is stock. I only booted device once via fastboot over USB in TWRP (to make a TWRP backup). If just during that TWRP boot system was mounted rw, how would that affect OTA update weeks, months or years later on an otherwise always stock device?
Click to expand...
Click to collapse
Mounting system as R/W will change some parameters, resulting in different hash than OTA update engine expects, hence it will abort the installation and show "installation error" message. User can easily verify if system was mounted, from terminal emulator with commands "sudo tune2fs -l /dev/block/mmcblk0p25" for system_a and "sudo tune2fs -l /dev/block/mmcblk0p26" for system_b. Look for "last mount time" - any recent date is "wrong". So even if you did not flash TWRP, but mounted system partition as R/W, your next OTA will fail and the only solution is to reflash stock system image. Once you're back to fully stock, consequent updates should not fail (at least not due to this reason).
_mysiak_ said:
Mounting system as R/W will change some parameters, resulting in different hash than OTA update engine expects, hence it will abort the installation and show "installation error" message. User can easily verify if system was mounted, from terminal emulator with commands "sudo tune2fs -l /dev/block/mmcblk0p25" for system_a and "sudo tune2fs -l /dev/block/mmcblk0p26" for system_b. Look for "last mount time" - any recent date is "wrong". So even if you did not flash TWRP, but mounted system partition as R/W, your next OTA will fail and the only solution is to reflash stock system image. Once you're back to fully stock, consequent updates should not fail (at least not due to this reason).
Click to expand...
Click to collapse
Thanks for explanation!.
OK one can figure out if system was ever mounted rw and fail. Fair enough.
Still a bit curious about which hash you talk, but probably some 'meta' hash.
Dior DNA said:
Thanks for explanation!.
OK one can figure out if system was ever mounted rw and fail. Fair enough.
Still a bit curious about which hash you talk, but probably some 'meta' hash.
Click to expand...
Click to collapse
If you're really interested, I would advise checking OTA update engine's source code. I don't know such details (just too lazy to dig through source code myself)
_mysiak_ said:
If you're really interested, I would advise checking OTA update engine's source code. I don't know such details (just too lazy to dig through source code myself)
Click to expand...
Click to collapse
I had already checked, of course, there are indeed meta hashes, that is where I got the word from, not that I understand it completely
Thanks all for help. My friend came by and:
I fastboot flashed F 9.6.4.0 system img onto a/b and then OTA to 9.6.5.0 went well..
I fastboot-ed into TWRP again (and made backup) but question to mount system rw was not asked.
I guess next OTA may fail again as I had not first reconfigured TWRP to disallow system rw (will do next time).
Have a nice day