OK ... Dumb Question(s) - How do I update to the current Project Fi Build LVY48E?
- I have downloaded the posted Zip File (LVY48E from LVY48C - https://android.googleapis.com/packa...rblock-fix.zip)
- Does this affect the LVY48C Radios? - Prior instructions said to just flash the system image if the radios were not changed but this is not a factory image .zip file? - It looks like the update mainly affects the system but there is a boot.img.p patch that concerns me?
I am rooted, unlocked, decrypted (Stock Rom w/Hells Core Kernel), and have TWRP recovery installed and I don't want to lose any data, get encrypted, change the bootloader or lose my custom recovery.
Any help is appreciated
Here's the process I went through
1) Back a TWRP backup of your current system
2) Download the official LVY48C factory image from Google
3) Extract all the files out the factory image
4) Using fastboot flash system, recovery and boot with the factory image ones
5) Reboot into recovery which is the stock recovery
6) While in the stock recovery hold down the power button and tap the volume up button
7) Select apply update from USB or sideload mode
8) On your computer run adb sideload <name of ota>
9) Reboot back into the bootloader and flash TWRP again
I recommend simply waiting though until the factory image for LVY48E is posted by Google as it will be a much simpler process
Thanks for the information ... I thought I might be able to rename the zip to update.zip and sideload it through twrp. You are defintely right about the factory image, I can just pull the system image and flash that. I wonder if they will release a factory image since it was just a system patch?
Deckard_9732 said:
Thanks for the information ... I thought I might be able to rename the zip to update.zip and sideload it through twrp. You are defintely right about the factory image, I can just pull the system image and flash that. I wonder if they will release a factory image since it was just a system patch?
Click to expand...
Click to collapse
They've already posted the factory images for the standard build and the T-Mobile build so I imagine that they'll release the Fi one soon.
FYI, an OTA needs to be flashed from a stock recovery AND must be 100% stock rom and kernel...
samstudent said:
They've already posted the factory images for the standard build and the T-Mobile build so I imagine that they'll release the Fi one soon.
Click to expand...
Click to collapse
Its out now
Related
All,
I'm coming from a nexus environment where I've been able to do fastboot boot twrp-2.6.3.1-ghost-4.4.img rather than fastboot flash recovery twrp-2.6.3.1-ghost-4.4.img since I'm hoping to keep the stock recovery while installing supersu. It complains about "(bootloader) Command restricted" with the MotoX even though my bootloader is unlocked. Is this typical of Moto devices? Do I actually need to flash twrp, then supersu and then the stock recovery if that's the final result I want? FWIW, I want SU on it but I'd like to also receive future OTA updates w/o too much dorking around of at all possible.
thanks peterb
Are you using mfastboot or just regular fastboot?
I fastboot twrp no problem. I did however mfastboot the system.img . But to answer your question twrp will ask you if you want to root when you go to reboot.
Fastboot flash recovery twrp 2.6.3.1-ghost-4.4.img is the command, when you flash do not reboot the device to the system but boot into recovery instead, you should be good to go and twrp should ask if you wish to root, if not just download the flashable supersu zip
Sent on my Moto X
I understand that you should flash if you want to have TWRP installed on your phone but that's not what I want. I'd like to just boot into TWRP, install the SuperSU.zip and then boot back up as normal leaving the stock recovery in place so that I will continue to get OTA updates. I get that this is likely not the norm but it's what I did with my N4 to get SuperSu so that I could update boot.prop for flashing a hybrid radio. Doing this made it easier to get the phone back to OTA ready w/o having to flash the stock recovery back.
I found a couple of posts in the N4 where the fastboot command failed and you needed to start using the "-c" command. I was wondering if this was the problem I was running into. The argument for -c is a bit cryptic so I worry that the one I found is likely N4 specific:
fastboot -c "lge.kcal=0|0|0|x" boot customrecovery.img
Basically what I'm wondering is if anyone has been able to just boot into TWRP w/o actually flashing it to the recovery partition.
If this is not possible then I'll flash TWRP, root and then flash the stock recovery back on since I did get the stock 4.4 image from Motorola.
thanks peterb
flashallthetime said:
Fastboot flash recovery twrp 2.6.3.1-ghost-4.4.img is the command, when you flash do not reboot the device to the system but boot into recovery instead, you should be good to go and twrp should ask if you wish to root, if not just download the flashable supersu zip
Sent on my Moto X
Click to expand...
Click to collapse
Interested in this as well, for booting kernels. Device support has been hit-or-miss for me in the past.
And folks, he's asking about fastboot's ability to launch an image _without_ flashing. This is a somewhat esoteric/advanced use.
I'm interested in this too even though I have a locked Moto X.
I didn't know this was possible, huh. As for our device, it'll probably help if we can figure out what that -c command means.
Sent from my Moto-X (GSM DE) using the xda-developers app
thehockeydude44 said:
I didn't know this was possible, huh. As for our device, it'll probably help if we can figure out what that -c command means.
Sent from my Moto-X (GSM DE) using the xda-developers app
Click to expand...
Click to collapse
If I'm remembering right, google took the ability to boot a recovery without loading one away in 4.2. We tried to do this on the HTC 1 Google edition when we pulled its partitions to make a system dump. It failed.
OTA fails when the device is rooted, even if you have the stock recovery.
The OTA zip checks the system partition. If there is any single modification, it fails.
you can just:
- flash twrp to recovery partition
- reboot into recovery
- install supersu
- reboot into fastboot
- flash stock recovery
- reboot to system
you have installed supersu and still have stock recovery -> you can take OTAs
edit: i just read that even with stock recovery, if u are rooted the ota won't work
Yea, this is the other way to do it. It's just a bummer if one can't use the flexibility to just boot into recovery. Note that I still seem to be able to boot into custom recovery on my Nexus 4 that's running KitKat. I'm curious about the comment about not getting an OTA with su installed. I know that with a modified build.prop and radio, the N4 wouldn't update but I could adb sideload successfully once I put build.prop back and the stock radio on. I figured the OTA would just unroot and then I'd have to do the process again.
Anyway, this was my plan B, just would have preferred to boot recovery.
peterb
waiflih said:
you can just:
- flash twrp to recovery partition
- reboot into recovery
- install supersu
- reboot into fastboot
- flash stock recovery
- reboot to system
you have installed supersu and still have stock recovery -> you can take OTAs
edit: i just read that even with stock recovery, if u are rooted the ota won't work
Click to expand...
Click to collapse
if u want to "unroot" to take otas, u can just flash stock system
waiflih said:
you can just:
- flash twrp to recovery partition
- reboot into recovery
- install supersu
- reboot into fastboot
- flash stock recovery
- reboot to system
you have installed supersu and still have stock recovery -> you can take OTAs
edit: i just read that even with stock recovery, if u are rooted the ota won't work
Click to expand...
Click to collapse
I am interested in this as well. How do we get a copy of the stock recovery to reflash?
Also, I have had rooted stock and custom recoveries and have received OTA's before (but they were on Nexus devices).
droiddog said:
I am interested in this as well. How do we get a copy of the stock recovery to reflash?
Also, I have had rooted stock and custom recoveries and have received OTA's before (but they were on Nexus devices).
Click to expand...
Click to collapse
you can take it from the the file used in rsdlite, according to you fw version
The only reason I want the stock recovery is because I think you can't remotely lock or erase your device on a custom recovery. Does anyone know anything to the contrary? Thanks.
I got a NExus 7 wifi 2012 that was running 5.0. It was rooted, and used TWRP.
I got info about the updated and pressed install. Booted in to TWRP and nothing happened. I then pressed install in TWRP and in cache found the .zip and tried to install. Got an error.
I then booted in to android again, and flashed the stock recovery 5.0.2 (I guess it's like the stock 5.0?) and later I tried the OTA install again. Got an error.
I then read about the new "feature" in 5.0 about not allowing OTA if rooted, and I then in SuperSU completely uninstall the root and rebooted.
Later when I got the OTA update again, I thought it should work, but I still got the error.
What can I do? Right now I'm on a MAC. Can I in some way flash only the good stuff from the factory image, and in some way NOT have to factory reset the Nexus 7?
/Söder
Even when you unroot, your file system is tampered. Only way to update is using factory images.
I think you can flash the factory image without user data to prevent factory reset.
theliquid said:
Even when you unroot, your file system is tampered. Only way to update is using factory images.
I think you can flash the factory image without user data to prevent factory reset.
Click to expand...
Click to collapse
How is it I do that then? What files from the factory images (unpacked) is it that I need to flash? Is it fastboot or ADB I use to flash?
/Söder
soder said:
How is it I do that then? What files from the factory images (unpacked) is it that I need to flash? Is it fastboot or ADB I use to flash?
/Söder
Click to expand...
Click to collapse
I have done this with my rooted N5 and N7. You need to re-flash system.
Unpack the 5.0 factory image and
fastboot flash system system.img
goraps said:
I have done this with my rooted N5 and N7. You need to re-flash system.
Unpack the 5.0 factory image and
fastboot flash system system.img
Click to expand...
Click to collapse
I managed to do this now to. My biggest problem is now to root the device again. I've switched back to stock recovery, before I removes root, when I was trying to apply the ota.
Now when I try to flash twrp recovery, I get an error about the size. I can flash the stock recovery though, the same way I flashed system.img and boot.img.
What can be wrong? I do I get root now again?
/Söder
/Söder
soder said:
I managed to do this now to. My biggest problem is now to root the device again. I've switched back to stock recovery, before I removes root, when I was trying to apply the ota.
Now when I try to flash twrp recovery, I get an error about the size. I can flash the stock recovery though, the same way I flashed system.img and boot.img.
What can be wrong? I do I get root now again?
/Söder
/Söder
Click to expand...
Click to collapse
Are you saying you can't flash the TWRP recovery now? So are you now completely stock 5.0.2?
goraps said:
Are you saying you can't flash the TWRP recovery now? So are you now completely stock 5.0.2?
Click to expand...
Click to collapse
Yes, system, boot, recovery flashed with fastboot.
When in fastboot mode, I get error, something with size, when flashing twrp. I found a CWM recovery I could flash, but it didn't boot to recovery correctly.
The twrp file is not corrupt. Tried it again and also a different version.
/Söder
OMG. I'm so f-ing stupid. Blaming all the x-mas food.
Was trying to flash the Oneplus One recovery. Not the one for Nexus 7.
Hope it works better now...
/Söder
Hi all.
This is a moment that I'm disconnected hacks because I am in stock (6.0.401.11) and satisfied. I had OTA updates without problems until this kitkat version but today after receiving and downloading 2 times the OTA lollipop I can not install it because installation starts well and some moments later, the screen is stuck on the phone with red triangle and I have this in the recovery:
Verifying current system ...
"/ System / bin / reboot" has unexpected content
Installation aborted
Even when I do it manually, it's the same. Yet I have just manually switch successfully 6.0.401.12 that I missed somehow.
What's the trouble?
kamso said:
Hi all.
This is a moment that I'm disconnected hacks because I am in stock (6.0.401.11) and satisfied. I had OTA updates without problems until this kitkat version but today after receiving and downloading 2 times the OTA lollipop I can not install it because installation starts well and some moments later, the screen is stuck on the phone with red triangle and I have this in the recovery:
Verifying current system ...
"/ System / bin / reboot" has unexpected content
Installation aborted
Even when I do it manually, it's the same. Yet I have just manually switch successfully 6.0.401.12 that I missed somehow.
What's the trouble?
Click to expand...
Click to collapse
this says to me, in system/bin you have modified files, you must be 100% stock so flash TWRP recovery then use this: https://www.androidfilehost.com/?fid=95864024717072880 to retore full stock rom.
DO NOT try and root or anything, 100% pure stock required.
Full Reboot into android
boot back to recovery and flash this pre-load data here: https://www.androidfilehost.com/?fid=95864024717072879
Full reboot into android
You will need TWRP recovery for both of the above files, but you will also need to flash stock recovery afterwards to update which is here: https://www.androidfilehost.com/?fid=95864024717072472
fastboot flash recovery
fastboot erase cache
fastboot reboot-bootloader
full reboot into android, then update.
DO NOT try and root or anything, 100% pure stock required.
Seanie280672 said:
this says to me, in system/bin you have modified files, you must be 100% stock so flash TWRP recovery then use this: https://www.androidfilehost.com/?fid=95864024717072880 to retore full stock rom.
DO NOT try and root or anything, 100% pure stock required.
Full Reboot into android
boot back to recovery and flash this pre-load data here: https://www.androidfilehost.com/?fid=95864024717072879
Full reboot into android
You will need TWRP recovery for both of the above files, but you will also need to flash stock recovery afterwards to update which is here: https://www.androidfilehost.com/?fid=95864024717072472
fastboot flash recovery
fastboot erase cache
fastboot reboot-bootloader
full reboot into android, then update.
DO NOT try and root or anything, 100% pure stock required.
Click to expand...
Click to collapse
Ok, thank you. But what I don't understand is that there's a long time I'm no more root, I'm full stock (Rom, recovery...), only S-off and Unlocked. So Why for previous OTA updates I have not had this problem? Why I have to manually update successfully from 6.09.401.11 version to 6.09.401.12 one? Why it is only the upgrade to the Lollipop which has problem?
What is the preload data? I already have this: https://www.androidfilehost.com/?w=...0f40a2a319761577a4c3f1e723594b05669cb009e9d00
Can I flash it and the stock recovery only?
Your problem is the lack or corruption of the file /bin/reboot
2 solutions:
Flash a custom recovery and reflash the rom
Flash a custom recovery and replace the file
migascalp said:
Your problem is the lack or corruption of the file /bin/reboot
2 solutions:
Flash a custom recovery and reflash the rom
Flash a custom recovery and replace the file
Click to expand...
Click to collapse
Ok thanks. I'm downloading the Rom and I have to flash it through TWRP, flash stock recovery and try OTA update again.
kamso said:
Ok thanks. I'm downloading the Rom and I have to flash it through TWRP, flash stock recovery and try OTA update again.
Click to expand...
Click to collapse
preload data is HTC's little hidden way of stopping you getting OTA's if you unlock your bootloader, and yes it is required to update, without it, updates will fail.
Seanie280672 said:
preload data is HTC's little hidden way of stopping you getting OTA's if you unlock your bootloader, and yes it is required to update, without it, updates will fail.
Click to expand...
Click to collapse
Ah Ok I understand. These are applications that disappear when we unlock the bootloader. I had already installed them there's a long time. As I said my OTA updates passed without problem.
Problem flashing stock Rom in TWRP:
"- Zip signature verification failed
- Error flashing zip"
I don't understand anything, what's happen?
Problem solved and phone updated. Thank you!!!
So I've received an OTA notification that will NOT go away for the last 3 days.
I'm currently on N6F27E build (June 5th build)
I download the update & it reboots to TWRP & then does nothing...
I've tried using twrp's sideload mode, but that too does nothing...
So I need to know where to get the latest stock recovery.img & how to flash it, so I can update everything.
Additional info:
- unlocked bootloader
- stock / no-root
To take an OTA you must be on stock, as you probably have guessed by now. Download a system image from Google, extract it, and inside will be a recovery image you can flash. An easier way to go here would be to simply download the latest system image and flash everything but the recovery image using fastboot commands.
Strephon Alkhalikoi said:
To take an OTA you must be on stock, as you probably have guessed by now. Download a system image from Google, extract it, and inside will be a recovery image you can flash. An easier way to go here would be to simply download the latest system image and flash everything but the recovery image using fastboot commands.
Click to expand...
Click to collapse
Thank you for the help.
I have had no issues flashing OTA's until last month...
Then something messed up. Idk...
Now they're forcing the OTA...
You're likely having issues because Google is offering Android 7.1.1 again via OTA and you're likely still on 7.0. Thus flashing a stock image via fastboot is likely a better bet than the OTA, even though doing so will wipe data.
Hi I bring you how to root and install twrp on A70 any version ,I think its work on all new samsung device:good:
note :
1-first unlock your bootloader https://forum.xda-developers.com/galaxy-a70/development/recovery-twrp-galaxy-a70-t3955984
2-in all step Remove auto reboot in odin
requirement files :
PeaZip
https://www.peazip.org/download-installer-p-windows.html
TWRP recovery.img mack it tar with PeaZip
https://github.com/Grarak/android_device_samsung_a70q-twrp/releases
vbmeta.tar Vbmeta.img- https://www.androidfilehost.com/?fid...26312261811717
Stock recovery.img from your stock rom [ you can download your device rom and extract stock recovery ] and mack it tar with PeaZip
Magisk 20.1- https://www.androidfilehost.com/?fid...26312261797449
Odin3- https://www.androidfilehost.com/?fid...26312261811763
Samfirm- https://www.androidfilehost.com/?fid...26312261811762
Lets start
1- in stock roms maybe work on custom roms
2-boot in to download mode and flash vbmeta.tar via odin in ap
3-after that reboot to recovery by pressing vol+ and power and clear data and cache in stock recovery
4- reboot again in to download mod and now flash twrp via odin in ap
5-reboot to twrp recovery by pressing vol+ and power and slide right to modify. Click wipe, click format data, type yes after that go back and reboot to recovery. slide right to modify, click mount, if mount system partition read-only is checked, back out and reboot back to recovery and check mount again, it should now be unchecked. . Now click Vendor so its checked and system should be unchecked, back out.
6- Copy Magisk 20.1 to the External sd card. In TWRP click install, select storage and choose micro sd card, click on magisk and slide right to confirm. (you must have vendor checked in mount or it wont flash properly). when done, click all way back click reboot to download.
7- now flash stcok recovery tar file via odin and reboot your device to system
8-after your device start run Magisk and update it by install options
well done you have twrp and rooted device :fingers-crossed::good::fingers-crossed:
i think this method work on all new samsung device and just you have own your device file like
twrp /stock recovery /vbmeta
note : if your twrp Stuck on twrp logo you have to install stock recovery and repeat from step 2
tested device A705FN:fingers-crossed:
thanks to :good:
MarvinMod
Grarak
and other to help me in this method
thanks a lot. i will test it today and check back here tomorrow
edit: i cant flash twrp via odin. download mode says "only official released binaries are allowed"
bootloader unlocked
oem unlock grayed
vmeta flashed
wipe data cache
but cant flash twrp. tried to download latest version but still no joy
i have 705FN with A705FNXXU5BTC2 rom installed
thewalekk said:
thanks a lot. i will test it today and check back here tomorrow
edit: i cant flash twrp via odin. download mode says "only official released binaries are allowed"
bootloader unlocked
oem unlock grayed
vmeta flashed
wipe data cache
but cant flash twrp. tried to download latest version but still no joy
i have 705FN with A705FNXXU5BTC2 rom installed
Click to expand...
Click to collapse
Hi i think you have to first flash 4file rom on your device
Plez check this maybe help you
https://forum.xda-developers.com/sa...torial-root-november-security-update-t3715661
Your bootloader must be updated
seli1987 said:
Hi i think you have to first flash 4file rom on your device
Plez check this maybe help you
https://forum.xda-developers.com/sa...torial-root-november-security-update-t3715661
Your bootloader must be updated
Click to expand...
Click to collapse
Hi thanks for the reply. But the day before i read this post, i flashed the latest firmware from sammobile which is the rom i told in the post (BTC2). Doesnt latest firmware include latest BL? Where can i find the current version of my BL in my phone?
thewalekk said:
Hi thanks for the reply. But the day before i read this post, i flashed the latest firmware from sammobile which is the rom i told in the post (BTC2). Doesnt latest firmware include latest BL? Where can i find the current version of my BL in my phone?
Click to expand...
Click to collapse
Try again flash 4 file frimware and let device start to system after that reboot to download mod and flash vbmeta.tar and let your device start to system
After that reboot to stock recovery and wipdata and cach and reboot to download mod and now flash twrp
The wrong is with your bootloader if you cant fix it try to search your problem in google
You are not only one have this problem
I did every thing from scratch. Even lock and unlock the bootloader.
I am tring to make sence. Vbmeta is "verified boot". So the idea is trick the phone with our own bootloader so that we can flash twrp.
Since i cant flash twrp, vbmeta should be updated.
Am i right?
thewalekk said:
I did every thing from scratch. Even lock and unlock the bootloader.
I am tring to make sence. Vbmeta is "verified boot". So the idea is trick the phone with our own bootloader so that we can flash twrp.
Since i cant flash twrp, vbmeta should be updated.
Am i right?
Click to expand...
Click to collapse
Unlock bootloader, factory reset, unsure oem is unlocked and grayed out in settings >developer options.
Then flash vbmeta, manual reboot to download mode, flash twrp, boot to twrp, factory reset in twrp , flash magisk zip then factory reset again, now boot system.
The vbmeta you flash is empty and allows flashing third party zips.
Hiii, i did almost everthing, but when i boot in recovery and go to mount, system partition read-only is checked. already tried 4 for times reboot to recovery but still checked.
Yes, i slide right to allow to modify. Any suggestion ?
BubSystemS said:
Hiii, i did almost everthing, but when i boot in recovery and go to mount, system partition read-only is checked. already tried 4 for times reboot to recovery but still checked.
Yes, i slide right to allow to modify. Any suggestion ?
Click to expand...
Click to collapse
Go ahead with the steps. Ignore mount system.
Let's see what happens
Worst scenario, you soft brick the phone or bootloop which can be fixed by flashing stock rom again.
Make sure you have stock rom and you backup your data
Any way to pass SatefyNet?
Instal this path in Magisk:
https://github.com/kdrag0n/safetynet-fix/releases/download/v1.1.0/safetynet-fix-v1.1.0.zip