Related
This is a TWRP backup of the stock firmware for V510 GPE GPAD 8.3. They have already been updated. It is completely stock no mods, no root, no busybox. This should ensure that you are able to take future OTAs without issue. Many GPE users have been having problems with the OTAs. The reason is that the OTA does a system verification and any type of modification causes it to fail.
How to flash this:
1. Reboot into bootloader
2. Flash TWRP if you don't already have it. Current version is 2.8.1.0 fastboot flash recovery xxxxxxxxxxxxx.img (where xxxxx is the filename)
3. Reboot System
4. Copy the entire contents of the zip file to your TWRP/BACKUPS/LG0000XXXXXXXX folder. Make sure you copy the folder 2014-11-30--23-35-25 LRX21P.L004 or 2014-06-26--18-41-18 KTU84P.L002. If you don't have a backups folder, create one in TWRP by choosing Backup, then backup something like the boot partition.
5. Reboot to Recovery Vol Dwn+Pwr or adb reboot recovery.
6. Choose Restore and select 2014-11-30--23-35-25 LRX21P.L004 or 2014-06-26--18-41-18 KTU84P.L002
7. Once finished Reboot System.
8. Upon boot you should be greeted with the usual Setup screens.
9. Reboot into bootloader
10. (Optional for Kit Kat) Flash stock recovery: fastboot flash recovery 17-recovery.img
11. Reboot into system
.
Flashing the stock recovery is optional however if you want a completely stock experience and ensure future OTAs, you probably want to do so. Also note that you must unroot to take any future OTAs.
To reroot flash latest version of TWRP.
Download Links:
LMY47O.L008 with Stock Recovery
TWRP Backup 5.1 LMY47O.L005 with Stock Recovery
TWRP Backup 5.1 LMY47O Thanks @rocket321 for providing the image.
TWRP BACKUP 5.0 LRX21P.L004
TWRP BACKUP 4.4.4 KTU84P.L002
KK Stock Recovery
You did an excellent job on this thread. Thanks for doing this for our small community.
BTW: regarding recovery for our device, the latest (and in fact only) that I see is TWRP 2.7.0.1 in the Original Android Development section.
Agreed. I wasn't able to flash 4.4.4 any other way. Tried everything, kept getting errors. This finally worked!
cam30era said:
You did an excellent job on this thread. Thanks for doing this for our small community.
BTW: regarding recovery for our device, the latest (and in fact only) that I see is TWRP 2.7.0.1 in the Original Android Development section.
Click to expand...
Click to collapse
Figured it will come in handy to have this online for everyone in the future...when I bought the device when it was announced thought there would be more dev on it...but that hasn't been the case. Luckily we at least have twrp.
No partitions selected for restore.
djkinetic said:
This is a TWRP backup of the stock firmware for V510 GPE GPAD 8.3. It has already been updated to 4.4.4. It is completely stock no mods, no root, no busybox. This should ensure that you are able to take future OTAs without issue. Many GPE users have been having problems with the OTA for 4.4.4 The reason is that the OTA does a system verification and any type of modification causes it to fail.
How to flash this:
1. Reboot into bootloader
2. Flash TWRP if you don't already have it. Current version is 2.7.0.1 fastboot flash recovery xxxxxxxxxxxxx.img (where xxxxx is the filename)
3. Reboot System
4. Copy the entire contents of the zip file to your TWRP/BACKUPS/LG0000XXXXXXXX folder. Make sure you copy the folder 2014-06-26--18-41-18 KTU84P.L002. If you don't have a backups folder, create one in TWRP by choosing Backup, then backup something like the boot partition.
5. Reboot to Recovery Vol Dwn+Pwr or adb reboot recovery.
6. Choose Restore and select 2014-06-26--18-41-18 KTU84P.L002
7. Once finished Reboot System.
8. Upon boot you should be greeted with the usual Setup screens.
9. Reboot into bootloader
10. (Optional) Flash stock recovery: fastboot flash recovery 17-recovery.img
11. Reboot into system
.
Flashing the stock recovery is optional however if you want a completely stock experience and ensure future OTAs, you probably want to do so. Also note that you must unroot to take any future OTAs.
Download Links:
TWRP BACKUP 4.4.4 KTU84P.L002
Stock Recovery
Click to expand...
Click to collapse
When I flash this in twrp it fails to flash and i get an error message: No partitions selected for restore. Have twrp 2.7.0.1 installed. Thank you.
Do I unzip the folder before I move it to the backup folder?
1barlog17 said:
Do I unzip the folder before I move it to the backup folder?
Click to expand...
Click to collapse
Delete
Figured out what was going on. finally got it to flash in TWRP. Works great. Thank you for this.
Thanks for this image - was the only way I was able to update.
Sent from my LG-V510 using Tapatalk
I was not able to update using your image and I don't know why. Everything was done correctly as far as I know. I downloaded and unpacked the zip and placed it in the back apps folder of TWRP and rebooted into recovery and tried restore with no success during the system restore it stops halfway through and says failed.
I tried downloading the file twice, installing the file from my computer, changing my SD card, deleting everything and trying, deleting just dalvik cache a,updating the partition separately, and was able to update the boot partition but not system and data. I honestly don't know what the trouble is as I was able to restore my own back up several times.if anybody has any insight into what is happening here please tell me. I would really like to install the update! I don't know why it is not allowing me to.
sleekmason said:
I was not able to update using your image and I don't know why. Everything was done correctly as far as I know. I downloaded and unpacked the zip and placed it in the back apps folder of TWRP and rebooted into recovery and tried restore with no success during the system restore it stops halfway through and says failed.
I tried downloading the file twice, installing the file from my computer, changing my SD card, deleting everything and trying, deleting just dalvik cache a,updating the partition separately, and was able to update the boot partition but not system and data. I honestly don't know what the trouble is as I was able to restore my own back up several times.if anybody has any insight into what is happening here please tell me. I would really like to install the update! I don't know why it is not allowing me to.
Click to expand...
Click to collapse
First off, I use solid explorer, dual pane. Very easy to navigate for me.
I only copied system. I didn't even wipe. All my data and settings were intact. As close to an OTA I could get. The system backup was 790.95mb
It sounds like you did everything right to me. I included a screen shot of what it looked like after i clicked the backup.zip and moved the unzipped backup to the TWRP backup folder.
Sent from my LG-V510 using XDA Premium 4 mobile app
sleekmason said:
I was not able to update using your image and I don't know why. Everything was done correctly as far as I know. I downloaded and unpacked the zip and placed it in the back apps folder of TWRP and rebooted into recovery and tried restore with no success during the system restore it stops halfway through and says failed.
I tried downloading the file twice, installing the file from my computer, changing my SD card, deleting everything and trying, deleting just dalvik cache a,updating the partition separately, and was able to update the boot partition but not system and data. I honestly don't know what the trouble is as I was able to restore my own back up several times.if anybody has any insight into what is happening here please tell me. I would really like to install the update! I don't know why it is not allowing me to.
Click to expand...
Click to collapse
im not sure if this would work
did u try restoring from the internal sd instead of external. as far as I know the backup file should have no issues.
djkinetic said:
im not sure if this would work
did u try restoring from the internal sd instead of external. as far as I know the backup file should have no issues.
Click to expand...
Click to collapse
That was it!! Thank you!
Do I need to uninstall Xposed Framework, unroot, restore the stock kernel, etc., before restoring this system back up TWRP? I assume the answer is no, though I'll need to reinstall those afterward, but I figured I'd check first!
UPDATE: Never mind. I just went ahead and restored it successfully and am in the process of restoring my apps from TiBu now. Thanks again for providing this for those of us who couldn't upgrade to 4.4.4 any other way!
Hey guys,
first off thank you for posting this tutorial, I was able to perform the backup0 and am currently on 4.4.4.
I did, however, run into a slight hiccup when I was trying to flash the stock recovery. I kept getting messages about partitions and so forth. I entered in the following commands from beginning to end:
adb devices
adb reboot bootloader
fastboot flash recovery 17-recovery.img
but as I said I can't get the job done lol.
Any ideas?
ephayzee said:
Hey guys,
first off thank you for posting this tutorial, I was able to perform the backup0 and am currently on 4.4.4.
I did, however, run into a slight hiccup when I was trying to flash the stock recovery. I kept getting messages about partitions and so forth. I entered in the following commands from beginning to end:
adb devices
adb reboot bootloader
fastboot flash recovery 17-recovery.img
but as I said I can't get the job done lol.
Any ideas?
Click to expand...
Click to collapse
A few things to check:
you need to have usb debugging checked on phone
you need the recovery image in same folder as your fastboot.exe/adb files
you need to cd to that directory/folder
TWRP source
Hi,
Can you please tell me where to find TWRP 2.7.x for the V510. I currently have 2.6.3.0, I believe?
Thanks
techinv said:
Hi,
Can you please tell me where to find TWRP 2.7.x for the V510. I currently have 2.6.3.0, I believe?
Thanks
Click to expand...
Click to collapse
It worked fine for me with TWRP 2.6
techinv said:
Hi,
Can you please tell me where to find TWRP 2.7.x for the V510. I currently have 2.6.3.0, I believe?
Thanks
Click to expand...
Click to collapse
Here > http://forum.xda-developers.com/showthread.php?t=2682606
However, download link in OP is currently broken. I PMed the OP about it.
Has anyone gotten the error "E: No partitions selected for restore." when trying to flash the recovery?
Thanks to @peramikic and @rczrider for fulfilling the request. I will post the compressed unmodified system.img if no one (@Unjustified Dev) beats me to it.
Just a note that I was successful in making my A2017U a stock B20. I first relocked my bootloader, then flashed the 4 images from TWRP. I was then able to reapply B20_boot update.
Keeping the request procedure below for archival purposes:
Code:
Hoping someone is still stock running B20 and willing/able to help. You'll need a micro-SD formatted exFAT with at least 8GB, and working ADB.
Following [URL="http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204"]tenfar's method[/URL], please backup both your stock boot and recovery using axon7backup.
Using axon7root, only apply the recovery included in tenfar's package (-r).
Reboot into recovery (volume up and power button). [U]KEEP READ ONLY! Do not slide the slider to make modifications![/U] Make sure under mount button that Micro SDCard is mounted.
On your PC, use the following commands:
[CODE]
adb shell
cd external_sd/
dd if=/dev/block/sde13 of=system.img
This will take a while as it copies ~6GB to your SD card (at least 10 minutes). When it's done, you should be returned to the prompt.
Using tenfar's method again, restore your recovery backup only. (-r)
Compress that file and upload it somewhere.[/CODE]
jkuczera said:
Hoping someone is still stock running B20 and willing/able to help. You'll need a micro-SD formatted exFAT with at least 8GB, and working ADB.
Following tenfar's method, please backup both your stock boot and recovery using axon7backup.
Using axon7root, only apply the recovery included in tenfar's package (-r).
Reboot into recovery (volume up and power button). KEEP READ ONLY! Do not slide the slider to make modifications! Make sure under mount button that Micro SDCard is mounted.
On your PC, use the following commands:
Code:
adb shell
cd external_sd/
dd if=/dev/block/sde13 of=system.img
This will take a while as it copies ~6GB to your SD card (at least 10 minutes). When it's done, you should be returned to the prompt.
Using tenfar's method again, restore your recovery backup only. (-r)
Compress that file and upload it somewhere.
Click to expand...
Click to collapse
@Unjustified Dev is getting his Axon 7 probably Monday and I told him to give us a hand about pulling system_image from untouched b20 , but if someone else can do it before him that will rock too.
DrakenFX said:
@Unjustified Dev is getting his Axon 7 probably Monday and I told him to give us a hand about pulling system_image from untouched b20 , but if someone else can do it before him that will rock too.
Click to expand...
Click to collapse
That's great to hear. Hopefully it's still B20 My attempt to go back to B20 stock failed on the system image. I really don't want to miss out on the next update!
Would be great if the next one was a full image!
jkuczera said:
That's great to hear. Hopefully it's still B20 My attempt to go back to B20 stock failed on the system image. I really don't want to miss out on the next update!
Would be great if the next one was a full image!
Click to expand...
Click to collapse
After all the jumbo-monbo we have giving them about factory images I bet there's be one for us waiting hehehe well hope so lol,
Probably UDev A7 still on B20 and he can give is a hand on this matte or Anyone else who want to help with this request will be great..
EDIT : @jkuczera
Out of my curiosity, i downloaded the Stock B20 backup from Here which you already have + a2017u b20 (inside there is a boot.img) and what i just did was,
- Move / Copy the System B20 Stock to my TWRP backup directory
- Move / Copy the Boot.img to SDCard (which was inside of the a2017u b20 zip file)
- Boot to TWRP
- Wipe Cache - Dalvik - Data - System ( twice as usual , well for me it is )
- Tap Restore > Select to B20 Stock Folder > Restore System
- Tap Install > Tap Install Image > go to where B20 Stock Boot.img is located > Flash Boot image
- Reboot (here is where i was crossing all my finger hehehe)
- Waited for about 10 min. or so and Booted
NOTE : i don't know if this Stock B20 backup is Untouch / UnModified as you request but , restoring the b20 stock backup + boot.img (Wiping all the above / mention partitions) work for me, WIFI - DATA working by the way and TWRP still bootable either by adb or manually
DrakenFX said:
NOTE : i don't know if this Stock B20 backup is Untouch / UnModified as you request but , restoring the b20 stock backup + boot.img (Wiping all the above / mention partitions) work for me, WIFI - DATA working by the way and TWRP still bootable either by adb or manually
Click to expand...
Click to collapse
Try doing a B20_Boot update; it should fail on verifying system. Otherwise you found the golden ticket.
DrakenFX said:
After all the jumbo-monbo we have giving them about factory images I bet there's be one for us waiting hehehe well hope so lol,
Probably UDev A7 still on B20 and he can give is a hand on this matte or Anyone else who want to help with this request will be great..
EDIT : @jkuczera
Out of my curiosity, i downloaded the Stock B20 backup from Here which you already have + a2017u b20 (inside there is a boot.img) and what i just did was,
- Move / Copy the System B20 Stock to my TWRP backup directory
- Move / Copy the Boot.img to SDCard (which was inside of the a2017u b20 zip file)
- Boot to TWRP
- Wipe Cache - Dalvik - Data - System ( twice as usual , well for me it is )
- Tap Restore > Select to B20 Stock Folder > Restore System
- Tap Install > Tap Install Image > go to where B20 Stock Boot.img is located > Flash Boot image
- Reboot (here is where i was crossing all my finger hehehe)
- Waited for about 10 min. or so and Booted
NOTE : i don't know if this Stock B20 backup is Untouch / UnModified as you request but , restoring the b20 stock backup + boot.img (Wiping all the above / mention partitions) work for me, WIFI - DATA working by the way and TWRP still bootable either by adb or manually
Click to expand...
Click to collapse
Like jkuczera said, the B20_Boot will fail since your system is not hash consistent (and recovery partition in not stock) and so will MR2 OTA . While all the right files are there, they are not in the right order (think file layout on the partition). TWRP can supposedly do a system image backups and if you take it with /system read-only when you run TWRP (i did), it is supposed to be a hash consistent. Restoring it where it get's iffy i guess. You are supposed to mount /system read-only and restore system image so TWRP will not modify it when you are done, but someone said did not restore (could be user error). It is also fastboot flashable but i think the fastboot images we have are limited in payload file size, someone i think tried and got the max payload error. I'll zip mine up and see if i can upload it somewhere once i get home. The image will have stock boot and system and TWRP rec, so all that would be needed is to flash stock rec to get correct sigs.
jkuczera said:
Try doing a B20_Boot update; it should fail on verifying system. Otherwise you found the golden ticket.
Click to expand...
Click to collapse
peramikic said:
Like jkuczera said, the B20_Boot will fail since your system is not hash consistent (and recovery partition in not stock) and so will MR2 OTA . While all the right files are there, they are not in the right order (think file layout on the partition). TWRP can supposedly do a system image backups and if you take it with /system read-only when you run TWRP (i did), it is supposed to be a hash consistent. Restoring it where it get's iffy i guess. You are supposed to mount /system read-only and restore system image so TWRP will not modify it when you are done, but someone said did not restore (could be user error). It is also fastboot flashable but i think the fastboot images we have are limited in payload file size, someone i think tried and got the max payload error. I'll zip mine up and see if i can upload it somewhere once i get home. The image will have stock boot and system and TWRP rec, so all that would be needed is to flash stock rec to get correct sigs.
Click to expand...
Click to collapse
what actually fails when i try to apply the zip using Stock Recovery is when check for boot, which System been the first partition to check and pass, boot.img i'm using is the one from tenfar for the whole reason of booting, but what i didn't Test was using a Full stock Boot.img even if i don't boot but to see if pass,
omw to try that report back,
DrakenFX said:
what actually fails when i try to apply the zip using Stock Recovery is when check for boot, which System been the first partition to check and pass, boot.img i'm using is the one from tenfar for the whole reason of booting, but what i didn't Test was using a Full stock Boot.img even if i don't boot but to see if pass,
omw to try that report back,
Click to expand...
Click to collapse
The first check you pass is the fingerprint, which is fine since you have restored stock system. The comes the sha1 check for boot, recover and system. You failed the hash check on the boot partition. Was the boot.img root mod one? that's not going to work.
What's the best way to pull it.... I got mine today. I haven't touched anything.
Sent from my ZTE A2017U using Tapatalk
shoman94 said:
What's the best way to pull it.... I got mine today. I haven't touched anything.
Click to expand...
Click to collapse
Check the OP. I can give you a place to upload to if you need it.
shoman94 said:
What's the best way to pull it.... I got mine today. I haven't touched anything.
Sent from my ZTE A2017U using Tapatalk
Click to expand...
Click to collapse
Just like JK said in first post, dump your boot and recovery with tenfars tool, then flash modded TWRP only. Make sure you stay in read only in TWRP on the first prompt
I would the do full TWRP backup including system image. then use the dd command above to dump /system part by itself.
Put it all on SD Card. Then flash back the stock recovery with tenfar's tool. You will have the stock backup of main partitions and phone ready for the MR2 OTA.
The main quirk of course is that the current BL unlock zip will most likely not work after MR2 OTAs until someone requests one. So trick is to see if the MR2 can be flashed with BL unlocked but going back to B20 boot, system and recovery
jkuczera said:
Check the OP. I can give you a place to upload to if you need it.
Click to expand...
Click to collapse
Yea, kinda ballsy.... I'll think about it. I can't afford to mess something up at the moment. Lol
Sent from my ZTE A2017U using Tapatalk
peramikic said:
The first check you pass is the fingerprint, which is fine since you have restored stock system. The comes the sha1 check for boot, recover and system. You failed the hash check on the boot partition. Was the boot.img root mod one? that's not going to work.
Click to expand...
Click to collapse
@jkuczera
yeah i take all that back, fails after 40% system fault , was turning things around getting apply from sdcard using stock recovery to work but well we need that system_img unmodified then ...
@jkuczera @DrakenFX check your PM
peramikic said:
@jkuczera @DrakenFX check your PM
Click to expand...
Click to collapse
check your PM
DrakenFX said:
check your PM
Click to expand...
Click to collapse
Done, also check this link on how it should be used
https://github.com/Lrs121/android_resources/wiki/Take-OTA-on-Block-Devices
peramikic said:
Done, also check this link on how it should be used
https://github.com/Lrs121/android_resources/wiki/Take-OTA-on-Block-Devices
Click to expand...
Click to collapse
got it thanks man,
DrakenFX said:
@Unjustified Dev is getting his Axon 7 probably Monday and I told him to give us a hand about pulling system_image from untouched b20 , but if someone else can do it before him that will rock too.
Click to expand...
Click to collapse
I have the system.img 6.4GB I did modified my system file a bit by installing busybox...
Is it ok for you?
If yes I will upload it through MEGA
manu7irl said:
I have the system.img 6.4GB I did modified my system file a bit by installing busybox...
Is it ok for you?
If yes I will upload it through MEGA
Click to expand...
Click to collapse
Needs to be 100% unmodified to pass signature checks. Thanks though!
I@jkuczera I can get back to stock with the untouched twrp backup, then save it for you.
I just restored my system patition from the B20 untouched twrp backup.
But still, I first restored the default recovery then made a factory rest. Then I flashed twrp again also made a format data, then backed up my current system and restored the system backup form the untouched B20.
but still after reboot twrp is asking for a password... I'm on twrp 3.0.2-2.
If I do:
Code:
do if=/dev/zero of=/dev/block/bootdevice/by-name/userdata bs=1m
This will be completely wipe the data partition...
Am I right? @DrakenFX
Could it help with this F***ing encryption??
hello,
I have installed cm13 and I want to get back to aosp 5.1,
I have twrp backup but when I click to restore there is information that firmware partition is in read-only mounted...
Is there any solution to fix it?
Read only mode is unclicked.
cvallo2 said:
hello,
I have installed cm13 and I want to get back to aosp 5.1,
I have twrp backup but when I click to restore there is information that firmware partition is in read-only mounted...
Is there any solution to fix it?
Read only mode is unclicked.
Click to expand...
Click to collapse
There is a mount option in twrp. Tick firmware and other relevant things there.
Alternatively restore everything except partition. Then flash the aosp rom again without any wipes. Boot it up. You shouldn't lose any data at all.
Sent from my kenzo using Tapatalk
cvallo2 said:
hello,
I have installed cm13 and I want to get back to aosp 5.1,
I have twrp backup but when I click to restore there is information that firmware partition is in read-only mounted...
Is there any solution to fix it?
Read only mode is unclicked.
Click to expand...
Click to collapse
Hi, which cm13 you used? Some of them will relock bootloader when you flashed it. So, check it via fastboot, type "fastboot oem device-info". You might need to re-unlock.
Sent from my Redmi Note 3 using Tapatalk
Thanks for answers.
It was cm13 official...and probably it locked my bootloader again - thanks for tip, then i've install aosp again and next my backup and voila it works
TLDR: It's here and it may eat your data, and you will lose SuperSU root if currently installed. READ the install instructions carefully!
Pixel XL
Pixel
DO NOT RESTORE DATA FROM alpha builds of TWRP using RC1. You will probably lose all data including internal storage. If you need to restore a data backup from an alpha build, reinstall the alpha and restore using the alpha and make a new backup using RC1.
Note: Do not use if you have multiple users (including a guest user)
File Based Encryption (FBE) can be a bit tricky. If a restore doesn't work correctly, it can trigger an automatic wipe of your data. Sometimes TWRP will fail to prompt you to enter your password or otherwise fail to set up decrypt properly. If this happens, reboot TWRP. It seems to be some kind of timing issue and I haven't had time to track it down yet.
Pixel devices have 2 "slots" for ROMs / firmware. TWRP will detect whichever slot is currently active and use that slot for backup AND restore. There are buttons on the reboot page and under backup -> options to change slots. Changing the active slot will cause TWRP to switch which slot that TWRP is backing up or restoring. You can make a backup of slot A, switch to B, then restore the backup which will restore the backup of A to slot B. Changing the slot in TWRP also tells the bootloader to boot that slot.
The zip install method installs TWRP to both slots.
Installation:
If you already have TWRP installed: Download the latest zip and install the zip using TWRP.
If you do not already have TWRP installed: Download both the img and the zip. Copy the zip to your device. You will need to have fastboot binaries and the correct drivers installed. Power off your device completely. Hold volume down and turn on the device. Your device should now be in the bootloader. Connect the device to your PC. Open a command window and run the following command from the proper location:
fastboot boot path/to/twrp.img
This will temporarily boot TWRP on your device. If you are using a lockscreen pin/pattern/password and do not get prompted to enter your passord, reboot to the bootloader and try again. Go to install and browse to the zip and install the zip. If you are currently rooted with SuperSU, you will need to reflash the stock boot image before installing TWRP. After installing the stock boot image, follow the instructions for installing TWRP. Once TWRP is installed, grab the very latest SuperSU released on 2015-11-15 or later and install SuperSU.
If you accidently flash TWRP to your device using fastboot instead of temporarily booting the image, you will need to download the latest factory image for your device and reflash the boot image.
NOTE about 3.2.1-0: This version will decrypt Android 8.1, however the new image is built in Android 8.1 and may not be compatible with SuperSU and/or Magisk until they update their stuff. I have not tested. Good luck.
3.2.1-1 has working decrypt with the February security patch!
3.2.1-2 fixes some zip install errors
3.2.3-1 supports decrypting Android 9.0 Pie even with a pin / pattern / password set
How to install SuperSU SR5 on TWRP RC1: In TWRP tap on Advanced -> File Manager and scroll to and select the fstab.marlin or fstab.sailfish file and then delete it.
You're the man! Props for all the hard work you've put into this.
TY!!!!
Awesome. I might have to wait a bit to install but glad to see the Pixel getting twrp.
Sent from my Pixel XL using Tapatalk
Wow, and so it begins. Thanks!
Thank you!!
Nice!!! Awesome job @Dees_Troy
Sent from my Pixel XL using Tapatalk
I just installed the IMG w/out issue.
I can't find the zip in TWRP file manager to flash though.
Everything looks encrypted.
EDIT: It went through on the 4th try of flashing the IMG, now I can see my /sdcard and install the zip.
But somehow this killed my OS.
Just flashed the flash-all.bat after removing -w so it doesn't wipe.
Now I'll try TWRP install again.
EDIT 2: Okay, after restoring to stock, the TWRP install went fine.
Maybe it didn't like my elementalx kernel or the existing root. The OP did mention something about root conflicts, I guess it may prevent TWRP installs too? But now I have OS *and* TWRP.
And I'm getting "Unspecified Error" when trying to copy my EFS backup from /sdcard/twrp/backup to my local computer. I am able to copy other non-TWRP files though.
.
.
.
Does a full backup on Pixel include System Image and Vendor Image? I don't recall seeing these on other devices.
Or do I just back up boot, system and data like usual?
***Hey ya'll, don't forget to back up EFS at least once and copy it to your computers!
Yea! Worked perfect!!!
Would the flashable SuperSU v2.78 SR3 zip work?
Looked it up and because of conflicting init binaries between TWRP and the current root method, it just wouldn't work.
While we're still on or near the first page of the thread, I'd like to clarify the whole EFS backup thing.
It's completely unnecessary. You don't need to do it. But the option is there (so no one asks where it went!)
Both the modemst1 and modemst2 partitions are merely a caching area for your modem firmware. They do not contain sensitive data like IMEI, or anything important. You can wipe them and they will be regenerated from scratch! Have no fear, your IMEI cannot be destroyed through means of bad flashes!
The issue with these partitions however is that should they ever become corrupt, the modem firmware will panic and fail to load - this is why you see your IMEI missing in such a case. The modem firmware simply refused to load due to encountering corrupt data. By clearing your modemst partitions (writing zeros to them), your modem firmware would happily load and regenerate the partitions, bringing back full call support & a visible IMEI.
Okay, I have TWRP + OS working fine after restoring to stock (getting rid of kernel + root).
Now to just wait for custom ROM's to drop. Thanks guys.
The ability to restore EFS was pretty important on some older phones.
Yep just want to let ya guys know might want return to stock before doing this. Besides that all good. Good job TWRP team! :good:
CZ Eddie said:
Okay, I have TWRP + OS working fine after restoring to stock (getting rid of kernel + root).
Now to just wait for custom ROM's to drop. Thanks guys.
The ability to restore EFS was pretty important on some older phones.
Click to expand...
Click to collapse
Are you rerooting after getting TWRP to work? Have you tried a backup and restore yet?
kirschdog1 said:
Are you rerooting after getting TWRP to work? Have you tried a backup and restore yet?
Click to expand...
Click to collapse
FYI on OP - A SuperSU update will be required to allow TWRP and SuperSU to co-exist.
kirschdog1 said:
Are you rerooting after getting TWRP to work? Have you tried a backup and restore yet?
Click to expand...
Click to collapse
yes
no
I stubbornly flashed v2 root and got boot hang so I put the phone up for the night.
delete
CZ Eddie said:
yes
no
I stubbornly flashed v2 root and got boot hang so I put the phone up for the night.
Click to expand...
Click to collapse
Do we still flash root the same way after we install TWRP? Or is there an su zip to flash?
Hooray! Cheers!
I've put everything into one zip file for the E5823. If you're reading this and don't have the Z5C and you try to get this working... you won't get it working... it'll just close.
This is for the users that are currently having issues with SuperSU + TWRP and Restore functions on Nougat. This works best if you have your Original TA partition saved as a DK.ftf. Disregard this post if you have everything working.
I can't guarantee anything working if you don't have your TA partition backed up, and I'm not going to test it - because I've already lost and had to retrieve my IMEI trying to get this TWRP working.
Use the Stock Sony ROM from 6.0, 6.0.1, 7.0.
When you try to restore - Only Restore the "Data" partition, and you'll only need to Backup the Data partition. I'm still working on TWRP 3.1/Android Bootable Recovery with Rootkernel for Nougat.
https://forum.xda-developers.com/z5...m-fix-twrp-t3560135/post71704926#post71704926
https://forum.xda-developers.com/attachment.php?attachmentid=4099322&d=1491209962
why not just used traditional recovey method since this is to complicate and risky of hard brick
in my experience i couldn't have this rootkernel woking properly ...since the biggining has restore issues flashing issues mount points not mounting properly and worse soft bricks if u dont have recovery on fota kernel.. and if you like to flash aosp base rom you will lose rootkernel recovery so indeed you will still need fota recovery
in fact i have developed i have twrp 3.0 working 100% on fota recovery also planing to update it to 3.2
yes im aware that the tool is good to fix drm and dm
but for flash ,recovery is useless at this point
I only started Android stuff about 4 weeks ago, so I didn't have a build environment ready.
But also this https://twrp.me/devices/sonyxperiaz.html
NeoBeum said:
I only started Android stuff about 4 weeks ago, so I didn't have a build environment ready.
But also this https://twrp.me/devices/sonyxperiaz.html
Click to expand...
Click to collapse
just in time
https://forum.xda-developers.com/crossdevice-dev/sony/patched-magisk-v12-sony-devices-t3582331
way better and even more safe
I wasted my weekend... Fml
altvolt74 said:
just in time
https://forum.xda-developers.com/crossdevice-dev/sony/patched-magisk-v12-sony-devices-t3582331
way better and even more safe
Click to expand...
Click to collapse
I had a quick play with it - but if it's flashed installed in the same way as SuperSU.zip in Recovery- people that are currently having restore errors, will have the same restore errors with MagiskSU.
It did give me a new recovery log to go through. There's some Case sensitive problems too now I think in TWRP.
I have Ubuntu going now too... I had to keep remaking a new virtual drive, because I thought 16GB was enough... then 32... then 64.... so I took it off my scratch SSD and put it on my storage drive as 200GB. The AOSP Sony tutorial said I'd need 100GB.