March update is live - Google Pixel 2 Guides, News, & Discussion

Here is the ota : https://developers.google.com/android/ota#walleye

If you want to apply this without returning /boot and /dtbo to stock, check out my thread. This uses the system image from the factory zip, and will not wipe /data.

THREAD CLOSED as this is already being discussed here and here.
jafffar98 said:
Here is the ota : https://developers.google.com/android/ota#walleye
Click to expand...
Click to collapse

Related

Question about evo-x3[ROM]

do i need to install every OTA update? or just the latest
fflmarco said:
do i need to install every OTA update? or just the latest
Click to expand...
Click to collapse
every
opssemnik said:
every
Click to expand...
Click to collapse
Another question how to install the OTA update
fflmarco said:
Another question how to install the OTA update
Click to expand...
Click to collapse
Go to cwm .. clear dalvik chache (optional) Mount system & Flash ota . ond by one Means flash one ota in one time reboot ur fone . then again repeat same procedure

XT1052 India 4.4.4 OTA

I've captured the OTA zip for XT1052 India 4.4.4 update.
Instructions (You should be on android 4.4.2)
For both locked and unlocked bootloaders
1. Place the downloaded file in sdcard
2. Don't rename the file, it should be exactly as it is
3. Rooted users make sure you're as close to stock as possible
4. Go to settings-> about-> system updates
5. It will prompt to install the update
Download XT1052 India 4.4.4 OTA
Could you post the stock recovery image of the 4.4.2 ROM, please?
ron_gangte said:
Could you post the stock recovery image of the 4.4.2 ROM, please?
Click to expand...
Click to collapse
Sorry, I don't have that right now.
Thanks anyway. It'd be awesome if someone who has it posted. Anyone?
Yep, the update just popped up. How do you capture it by the way? What's the path?
devilsdouble said:
Yep, the update just popped up. How do you capture it by the way? What's the path?
Click to expand...
Click to collapse
/cache - find it w/Root Explorer, or similar.
samwathegreat said:
/cache - find it w/Root Explorer, or similar.
Click to expand...
Click to collapse
There are three folders under cache, backup, lost+found and recovery, none of them contain the update.
devilsdouble said:
There are three folders under cache, backup, lost+found and recovery, none of them contain the update.
Click to expand...
Click to collapse
You already installed it? Once you install it, the file is erased - forever. All OTAs are this way. You MUST extract it before you install it.
Confirm: Did you install it or not? Also, if not - has it downloaded completely?
EDIT: I'll take your lack of response as you confirming that you did install it...
I am downloading ota update my phone is rooted so should i unroot it first and remove xposed framework.. reply??
Hitesh1802 said:
I am downloading ota update my phone is rooted so should i unroot it first and remove xposed framework.. reply??
Click to expand...
Click to collapse
Yes, un-root, and remove all traces of having rooted. That includes any changes done to your System Files which Xposed might have done. You will have to flash the stock recovery too.
ron_gangte said:
Yes, un-root, and remove all traces of having rooted. That includes any changes done to your System Files which Xposed might have done. You will have to flash the stock recovery too.
Click to expand...
Click to collapse
thanks for the reply mate i have removed su by app option full unroot yes i am on stock recovery and uninstalled all modules and xposed framework..
after update i have to done that again..
Due to this i miss my old Samsung device just flash and you are on...
samwathegreat said:
You already installed it? Once you install it, the file is erased - forever. All OTAs are this way. You MUST extract it before you install it.
Confirm: Did you install it or not? Also, if not - has it downloaded completely?
EDIT: I'll take your lack of response as you confirming that you did install it...
Click to expand...
Click to collapse
No, my lack of response was because of the reading I was doing here on XDA as why I wasn't seeing the OTA zip file under cache. Then I realized that I did not download the OTA, I thought that it was downloaded already as I had data on and it was just asking me to whether it should install or not.
Now I downloaded the OTA, and it's there under cache folder, and now at a safe place on my desktop.
I would never install it on my phone without flashing back stock ROM again anyway. I like to do things fresh.
devilsdouble said:
No, my lack of response was because of the reading I was doing here on XDA as why I wasn't seeing the OTA zip file under cache. Then I realized that I did not download the OTA, I thought that it was downloaded already as I had data on and it was just asking me to whether it should install or not.
Now I downloaded the OTA, and it's there under cache folder, and now at a safe place on my desktop.
I would never install it on my phone without flashing back stock ROM again anyway. I like to do things fresh.
Click to expand...
Click to collapse
Good Deal. Thanks for clarifying, and glad you were able to extract it. :good:
I can relate -- I also prefer to always "do things fresh"
samwathegreat said:
Good Deal. Thanks for clarifying, and glad you were able to extract it. :good:
I can relate -- I also prefer to always "do things fresh"
Click to expand...
Click to collapse
Thanks. It's always nice to have the latest of Android. The new dialer is meaningless for me, again, it just changed it's viewing type, nothing else has been changed! Need to install ExDialer as usual. Will see if there's really something done with the camera, can't take any meaningful photos at 3:30 in the morning :laugh:
Just one thing, as I have taken the OTA after a fresh install of stock ROM, now I don't need to format it again from recovery right?
There is already a thread for the 4.4.4 rollout here, please use it instead of having two similar discussions going on in 2 separate threads. Thanks
Thread closed

Marshmallow

Gave up waiting for Lollipop from LG and went for Marshmallow. Rooted with Kingo root and installed TWRP from terminal emulator. Wiped and formatted /data. Flashed Marshmallow (MDB08M) and SuperSU. Rebooted and installed apps. Everything worked like a dream, no hassles or snags.
So far ROM is stable, smooth and nice to use. Battery life is good. A definite improvment.
I wasn't aware there was a 6.0 ROM. Link please.
Are you on the V500 or V510?
I'm on V500. Link http://forum.xda-developers.com/lg-...rom-android-6-0-marshmallow-20151028-t3235794
Good luck!
nilssongrey said:
I'm on V500. Link http://forum.xda-developers.com/lg-...rom-android-6-0-marshmallow-20151028-t3235794
Good luck!
Click to expand...
Click to collapse
Thanks! I'll flash later today!
I tried to flash this ROM and I'm having issues with doing that. Anyone knows what am I doing wrong here?
I had CM12.1 from @fefifofum earlier but I wanted to try something Marshmallow based.
I updated TWRP to the most recent stable version (2.8.7.1) and all I got trying to install zip from mentioned thread is:
Error flashing zip '/external_sd/aosp_v500-eng.adrianomartins-20151107.zip'
Updating partition details...
...done
No other errors. I wiped Dalvik Cache, Cache, Data and even System. Nothing has changed.
What else can I try to fix it? Cause in fact right now I've got unusable tablet
regards
Bartek
Sounds like a bad download. Did you check the MD5 hash of what you downloaded and compared it to what the download page said the original hash was, if it gives that info? Android File Host does, I didn't check where your file came from.
[VK810.4G] [altev] [ViKtory810ROM] official LG G Pad 8.3 Lollipop 36B_00 5.0.2
[VK810.4G] [altev] official LG G Pad 8.3 Lollipop 36B_00 5.0.2 DEBLOAT SCRIPTS and copies of all the files they remove
[VK810.4G] [altev] OTAs, .IMGs and KDZs, oh my
MD5 is correct. I think something went wrong with wipes. Maybe I wiped too much but I'm not sure how to check it.
Maybe current partition layout is broken and needs to be fixed somehow but I'm not sure how to check what's wrong.
Any way to turn on more debugging info during install?
Current message isn't very helpful :/
regards
Bartek
fenio said:
MD5 is correct. I think something went wrong with wipes. Maybe I wiped too much but I'm not sure how to check it.
Maybe current partition layout is broken and needs to be fixed somehow but I'm not sure how to check what's wrong
regards
Bartek
Click to expand...
Click to collapse
I wiped dalvik and cache. I formatted /data and then I flashed.
Regards/Hakan
nilssongrey said:
I wiped dalvik and cache. I formatted /data and then I flashed.
Regards/Hakan
Click to expand...
Click to collapse
Well it doesn't work for me. I'm still getting "Error flashing zip".
Maybe there are some additional steps to do when I'm moving from CM to AOSP?
regards
Bartek
fenio said:
MD5 is correct. I think something went wrong with wipes. Maybe I wiped too much but I'm not sure how to check it.
Maybe current partition layout is broken and needs to be fixed somehow but I'm not sure how to check what's wrong.
Any way to turn on more debugging info during install?
Current message isn't very helpful :/
regards
Bartek
Click to expand...
Click to collapse
For what it's worth, I don't think it's possible to wipe too much. At least, in TWRP, I commonly wipe everything: data, cache, dalvik, system, and internal storage with no trouble.
roirraW "edor" ehT said:
For what it's worth, I don't think it's possible to wipe too much. At least, in TWRP, I commonly wipe everything: data, cache, dalvik, system, and internal storage with no trouble.
Click to expand...
Click to collapse
Thanks for confirmation. But then I have no idea why it doesn't flash.
It fails almost instantly so it looks like it gives up at the beginning but file size and its checksum are fine.
What else can I try to do?
regards
Bartek
fenio said:
Thanks for confirmation. But then I have no idea why it doesn't flash.
It fails almost instantly so it looks like it gives up at the beginning but file size and its checksum are fine.
What else can I try to do?
regards
Bartek
Click to expand...
Click to collapse
Can you post a log from recovery? Go to TWRP's Advanced menu and choose Copy Log to SD Card, then upload it somewhere. Feel free to put it in a zip.
What did you use to check the hash of the file from the phone itself?
What filsystem do you have on /data? I have a vauge recollection from a Lollipop thread that there were problems coming from CM if /data was formatted F2FS
/Hakan
Ok forget the topic. Apparently you can't choose random directory to put your image before flashing.
For some TWRP complains and clearly states that something is wrong (/root if I recall correctly) but for some it just blindly fails (/external_sd or /recovery).
I had to move my image to /sdcard directory and TWRP flashed it with no issues.
Hope that helps someone
Thanks a lot for your help.
regards
Bartek
fenio said:
Ok forget the topic. Apparently you can't choose random directory to put your image before flashing.
For some TWRP complains and clearly states that something is wrong (/root if I recall correctly) but for some it just blindly fails (/external_sd or /recovery).
I had to move my image to /sdcard directory and TWRP flashed it with no issues.
Hope that helps someone
Thanks a lot for your help.
regards
Bartek
Click to expand...
Click to collapse
Happy to know that you solved it. Happy Marshmallow!
/Hakan
nilssongrey said:
Happy to know that you solved it. Happy Marshmallow!
/Hakan
Click to expand...
Click to collapse
Thanks. Works like a charm so far. Looking forward to see more apps supporting asking for permissions on demand not on installation time
regards
Bartek
nilssongrey said:
Rooted with Kingo root and installed TWRP from terminal emulator. Wiped and formatted /data. Flashed Marshmallow (MDB08M) and SuperSU. Rebooted
Click to expand...
Click to collapse
Hi nilssongrey
I have installed TWRP, wiped all, flashed Marshmallow (MDB08M) and SuperSU
But now I have not root permission.
I don't know what's wrong.
How can I have root access?
Thanks
peppomcr said:
Hi nilssongrey
I have installed TWRP, wiped all, flashed Marshmallow (MDB08M) and SuperSU
But now I have not root permission.
I don't know what's wrong.
How can I have root access?
Thanks
Click to expand...
Click to collapse
I don't think you're in the correct forum.
I suggest you read a whole lot more before you break your new phone.
peppomcr said:
Hi nilssongrey
I have installed TWRP, wiped all, flashed Marshmallow (MDB08M) and SuperSU
But now I have not root permission.
I don't know what's wrong.
How can I have root access?
Thanks
Click to expand...
Click to collapse
High,
You should download the latest edition from that thread. There were some problems with the previous one. Even a second attempt by the OP didn't resolve all issues. The latest MRA58V is stable and complete. Personally however I flashed a more loaded version of the OpenGapps project. Running smooth etc since 20 November... Don't flash the latest SU, but the version before (2.51 ).
Cheers
Cluey said:
I don't think you're in the correct forum.
I suggest you read a whole lot more before you break your new phone.
Click to expand...
Click to collapse
It's not a new phone but an old tablet.
dirlan2001 said:
High,
You should download the latest edition from that thread. There were some problems with the previous one. Even a second attempt by the OP didn't resolve all issues. The latest MRA58V is stable and complete. Personally however I flashed a more loaded version of the OpenGapps project. Running smooth etc since 20 November... Don't flash the latest SU, but the version before (2.51 ).
Cheers
Click to expand...
Click to collapse
I've used the latest version: MRA58V, 2015-11-18
I need root because I have the external sd issue and I want to try to solve it: sd not recognized and so on...
I've flashed SU 2.46: is it better another version?
I'll take a look at OpenGapps project.
Thanks for your reply,
cheers.

Question about flashing updates on a rooted phone

I have a rooted 6P running the stock rom on the February security update with a bunch of Xposed modules and the Franco kernel. I know I won't get OTAs this way. Can I just flash the March security patch (MMB29V) and do nothing else? Or do I have to wipe data or factory reset? Do I have to do anything with the Franco kernel?
For the future, what would I need to do to flash Android N when it comes out on my rooted phone? Thanks a bunch!
Soundtallica said:
I have a rooted 6P running the stock rom on the February security update with a bunch of Xposed modules and the Franco kernel. I know I won't get OTAs this way. Can I just flash the March security patch (MMB29V) and do nothing else? Or do I have to wipe data or factory reset? Do I have to do anything with the Franco kernel?
For the future, what would I need to do to flash Android N when it comes out on my rooted phone? Thanks a bunch!
Click to expand...
Click to collapse
Most likely you cannot. An OTA update will do a check on your system and see that you have modified things and terminate install. You can leave your data alone but you will have to flash your boot and system partitions with the factory image
Sent from my Nexus 6P using Tapatalk
funnel71 said:
Most likely you cannot. An OTA update will do a check on your system and see that you have modified things and terminate install. You can leave your data alone but you will have to flash your boot and system partitions with the factory image
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I know OTA updates are impossible, so I plan to flash the factory image from the Google developers website via fastboot. Does that change anything?
Soundtallica said:
I know OTA updates are impossible, so I plan to flash the factory image from the Google developers website via fastboot. Does that change anything?
Click to expand...
Click to collapse
Don't flash the entire factory image or you will lose data. / only the boot and system images to their respective partitions. Once you complete that you can Flash the OTA update zip file and you will still have your data you can extract the boot and system images from the main factory image you download from Google using WinRAR
Sent from my Nexus 6P using Tapatalk
funnel71 said:
Don't flash the entire factory image or you will lose data. / only the boot and system images to their respective partitions. Once you complete that you can Flash the OTA update zip file and you will still have your data you can extract the boot and system images from the main factory image you download from Google using WinRAR
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
It's easier to just flash all of the images (except userdata) top to update, rather than flashing two and then messing around with OTA.
So is there anyway to flash the update without losing my data/apps??
Thanks!
cattel said:
So is there anyway to flash the update without losing my data/apps??
Thanks!
Click to expand...
Click to collapse
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Heisenberg said:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
Thank you very much!
Enviado de meu Nexus 6P usando Tapatalk
Step 9, right @Heisenberg ?
joooe said:
Step 9, right @Heisenberg ?
Click to expand...
Click to collapse
Yep. Probably would be a good idea to wipe data and the caches in TWRP first.
i used fastboot to install march update on my nexus 6p but now when trying to install twrp through fastboot it during writing it says permission denied. why is this?
mystertom said:
i used fastboot to install march update on my nexus 6p but now when trying to install twrp through fastboot it during writing it says permission denied. why is this?
Click to expand...
Click to collapse
Can you provide a screenshot of your attemp to flash the recovery? Also you might want to try opening the command prompt as administrator, right click on the command window in start menu and select open as administrator.
Heisenberg said:
Yep. Probably would be a good idea to wipe data and the caches in TWRP first.
Click to expand...
Click to collapse
Not at all a good idea @Heisenberg, as I just experienced. We were talking about keeping the apps and system as it was. Just wiped data and got an hardreset.
Clear cache only.
joooe said:
Not at all a good idea @Heisenberg, as I just experienced. We were talking about keeping the apps and system as it was. Just wiped data and got an hardreset.
Clear cache only.
Click to expand...
Click to collapse
Where did you say that? I know that wiping data will remove apps, but it's the right way to go about it to ensure no problems occur.
cattel said:
So is there anyway to flash the update without losing my data/apps??
Thanks!
Click to expand...
Click to collapse
It all went after this post.
But no problem.
joooe said:
It all went after this post.
But no problem.
Click to expand...
Click to collapse
Surely you were aware that wiping data was going to remove your apps? So all you needed to do was back them up first and restore them after you flashed. Apologies if I should have made that clear in my previous posts.
No problem. It was my stupid mistake.:good:
fastboot flash bootloader bootloader-angler-angler-02.45.img
fastboot reboot-bootloader
sleep 5
fastboot flash radio radio-angler-angler-02.50.img
fastboot reboot-bootloader
sleep 5
fastboot update image-angler-mmb29v.zip
Normally in the last line there is an option "-w" this wipes the data.
Don't do that and modify the script so the option is gone, like I did.
Uh, my phone just downloaded a system update of some sort, but I haven't installed it. Is this supposed to happen on a phone that's rooted and on the stock ROM? Can I install it safely or should I still flash the factory image instead?
And @Heisenberg, in your guide do you type in all the fastboot commands at once or do you do it line by line? Thanks again, your guide is super useful for rooting noobs like me :thumbup:
Soundtallica said:
Uh, my phone just downloaded a system update of some sort, but I haven't installed it. Is this supposed to happen on a phone that's rooted and on the stock ROM? Can I install it safely or should I still flash the factory image instead?
And @Heisenberg, in your guide do you type in all the fastboot commands at once or do you do it line by line? Thanks again, your guide is super useful for rooting noobs like me :thumbup:
Click to expand...
Click to collapse
Don't install it, it'll fail, you must flash the factory images. Each command is entered individually (press enter key to send the command), wait for flash to finish then enter the next command.

Axon 7 Bootloop

This morning I flashed through bootloader the new TWRP that was available for my ZTE Axon 7. After flashing it, I did a backup of Boot, Data and System, which is the default backup. Then I flashed SuperSU. When I tried testing my backup by restoring it through TWRP, it simply bootlooped after I restarted. I am frustrated because I have no idea what to do next. I cannot find a stock firmware for my US version Axon 7. PLEASE HELP!!!
B4oE said:
This morning I flashed through bootloader the new TWRP that was available for my ZTE Axon 7. After flashing it, I did a backup of Boot, Data and System, which is the default backup. Then I flashed SuperSU. When I tried testing my backup by restoring it through TWRP, it simply bootlooped after I restarted. I am frustrated because I have no idea what to do next. I cannot find a stock firmware for my US version Axon 7. PLEASE HELP!!!
Click to expand...
Click to collapse
Try Wipe Cache - Dalvik - Data on TWRP
I know you'll need to reinstall everything but hey may fix your bootloop problem
And so it begins...
@DrakenFX, did you have a typo in your instructions? I assume you meant Data rather than Daproblem.
TeutonJon78 said:
And so it begins...
@DrakenFX, did you have a typo in your instructions? I assume you meant Data rather than Daproblem.
Click to expand...
Click to collapse
LoL, so dislike auto-correct , Thanks for the mention
DrakenFX said:
LoL, so dislike auto-correct , Thanks for the mention
Click to expand...
Click to collapse
My early morning phone typing always look like I've had a stroke.
I wonder if we really need to wipe "Cache" anymore. I haven't seen any phone even using it lately. It just sits there basically empty since they moved everything to be stored in the Davlik one on the Data partition. I know on my Nexus 4 it basically just takes up 560 MB doing nothing but storing one recovery log file. Does TWRP use it for something during install?
TeutonJon78 said:
And so it begins...
@DrakenFX, did you have a typo in your instructions? I assume you meant Data rather than Daproblem.
Click to expand...
Click to collapse
Man people are so impatient, yes here we go, first bootloop....
---------- Post added at 07:39 PM ---------- Previous post was at 07:32 PM ----------
B4oE said:
This morning I flashed through bootloader the new TWRP that was available for my ZTE Axon 7. After flashing it, I did a backup of Boot, Data and System, which is the default backup. Then I flashed SuperSU. When I tried testing my backup by restoring it through TWRP, it simply bootlooped after I restarted. I am frustrated because I have no idea what to do next. I cannot find a stock firmware for my US version Axon 7. PLEASE HELP!!!
Click to expand...
Click to collapse
You are gonna have to wait until someone provides a working (flashable) backup of B20_boot, I'm guessing yours is corrupted or had user error, here I summon:
 @DrakenFX @jkuczera @swehes @peramikic
Does anyone has a clean flashable B20_boot from your TWRP backups? This guy bootlooped after trying to restore his. I would give him mine, but will probably not get my Axon 7 Gray shipped until wednesday from B&H.
---------- Post added at 07:40 PM ---------- Previous post was at 07:39 PM ----------
B4oE said:
This morning I flashed through bootloader the new TWRP that was available for my ZTE Axon 7. After flashing it, I did a backup of Boot, Data and System, which is the default backup. Then I flashed SuperSU. When I tried testing my backup by restoring it through TWRP, it simply bootlooped after I restarted. I am frustrated because I have no idea what to do next. I cannot find a stock firmware for my US version Axon 7. PLEASE HELP!!!
Click to expand...
Click to collapse
And did you already tried clearing cache and data?
B4oE said:
When I tried testing my backup by restoring it through TWRP, it simply bootlooped after I restarted. I am frustrated because I have no idea what to do next. I cannot find a stock firmware for my US version Axon 7. PLEASE HELP!!!
Click to expand...
Click to collapse
Do you see the ZTE logo?
I have the backups already made up, I believe this might be what you need:
jcadduono said:
heres some STOCK fastboot flashables 4 funsies: https://idlekernel.com/flash-tools/firmware/ailsa_ii_A2017U/B20/
Click to expand...
Click to collapse
jkuczera said:
Do you see the ZTE logo?
I have the backups already made up, I believe this might be what you need:
Click to expand...
Click to collapse
Is "system.img" the stock, out-of-the-box OS?
daneoleary said:
Is "system.img" the stock, out-of-the-box OS?
Click to expand...
Click to collapse
No, it would be based on B20. And if B20-boot modified the system partition, those modifications would be in there as well.
I apologize for not responding sooner. I was busy at work. Someone sent me a zip to flash through TWRP, which I will upload later, and then my bootloop issue was resolved. Apparently, the problem is with TWRP. Hopefully, everything will get ironed out soon. Other than that, I'm still having a good time (although frustrating at times) tinkering with my Axon 7.
B4oE said:
I apologize for not responding sooner. I was busy at work. Someone sent me a zip to flash through TWRP, which I will upload later, and then my bootloop issue was resolved. Apparently, the problem is with TWRP. Hopefully, everything will get ironed out soon. Other than that, I'm still having a good time (although frustrating at times) tinkering with my Axon 7.
Click to expand...
Click to collapse
Looking forward for your fix to help other members down the road! THANK YOU!
Jose-MXL said:
Looking forward for your fix to help other members down the road! THANK YOU!
Click to expand...
Click to collapse
Attached is the file I flashed.
jkuczera said:
No, it would be based on B20. And if B20-boot modified the system partition, those modifications would be in there as well.
Click to expand...
Click to collapse
B20_Boot only makes changes to boot.img and recovery.img
B4oE said:
Attached is the file I flashed.
Click to expand...
Click to collapse
Who sent it to you?
rczrider said:
Who sent it to you?
Click to expand...
Click to collapse
I honestly do not remember their name. Someone I spoke to through Freenode (http://webchat.freenode.net/?channels=twrp) simply told me to flash that zip. I just renamed it before flashing because I have a huge collection of zips for various devices. Hopefully, the one that has it can respond to my post. He/She was very helpful too!
jkuczera said:
No, it would be based on B20. And if B20-boot modified the system partition, those modifications would be in there as well.
Click to expand...
Click to collapse
xtermmin said:
B20_Boot only makes changes to boot.img and recovery.img
Click to expand...
Click to collapse
No, it modifies system:
From the updater script:
Code:
ui_print("Patching system image after verification.");
show_progress(0.550000, 0);
block_image_update("/dev/block/bootdevice/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat") ||
abort("Failed to update system image.");
show_progress(0.050000, 10);
ui_print("Patching fastboot.img image...");
package_extract_file("fastboot.img", "/dev/block/bootdevice/by-name/fbop");
ui_print("Patching boot image...");
apply_patch("EMMC:/dev/block/bootdevice/by-name/boot:45946154:b5154bbd9bf32de3d1e2a287df025a483bf3c50f:45942058:c31f24136f92263b578c19356df513650a12befc",
"-", c31f24136f92263b578c19356df513650a12befc, 45942058,
b5154bbd9bf32de3d1e2a287df025a483bf3c50f, package_extract_file("patch/boot.img.p"));
ui_print("Patching recovery image...");
apply_patch("EMMC:/dev/block/bootdevice/by-name/recovery:44545326:5ce0d08c1e4efdaf65879574d74611d569fa036f:44541230:a13824adb7464c22637b70ddb8b0991ff365ab4c",
"-", a13824adb7464c22637b70ddb8b0991ff365ab4c, 44541230,
5ce0d08c1e4efdaf65879574d74611d569fa036f, package_extract_file("patch/recovery.img.p"));
set_progress(1.000000);
It alters system.img, fastboot.img, boot.img, and recovery.img. By the looks of it, it modifies system.img a fair amount. Just fixing fastboot wouldn't be a 50+ MB patch.
TeutonJon78 said:
No, it modifies system:
From the updater script:
It alters system.img, fastboot.img, boot.img, and recovery.img. By the looks of it, it modifies system.img a fair amount. Just fixing fastboot wouldn't be a 50+ MB patch.
Click to expand...
Click to collapse
I'm blind. I stand corrected.
B4oE said:
I honestly do not remember their name. Someone I spoke to through Freenode (http://webchat.freenode.net/?channels=twrp) simply told me to flash that zip. I just renamed it before flashing because I have a huge collection of zips for various devices. Hopefully, the one that has it can respond to my post. He/She was very helpful too!
Click to expand...
Click to collapse
it might have been me that linked it (i'm the maker of the zip as it shows you in the console flash ) but yeah that's our go-to when someone says they flashed twrp and their system won't boot. it means they swiped to enable system modifications. we should probably go about extending the warning on the swipe to enable modifications page since devices that come with marshmallow out of factory will bootloop after swiping if you don't flash supersu or the no-verity-opt-encrypt zip. (the zip disables system integrity verification in your boot image, allowing you to boot after making modifications)
you can find the original, and updates if/when i make them at https://idlekernel.com/fun-stuff-trust-me/no-verity-opt-encrypt/
you can also follow history at https://github.com/jcadduono/lazyflasher/commits/no-verity-opt-encrypt
jcadduono said:
it might have been me that linked it (i'm the maker of the zip as it shows you in the console flash ) but yeah that's our go-to when someone says they flashed twrp and their system won't boot. it means they swiped to enable system modifications. we should probably go about extending the warning on the swipe to enable modifications page since devices that come with marshmallow out of factory will bootloop after swiping if you don't flash supersu or the no-verity-opt-encrypt zip. (the zip disables system integrity verification in your boot image, allowing you to boot after making modifications)
you can find the original, and updates if/when i make them at https://idlekernel.com/fun-stuff-trust-me/no-verity-opt-encrypt/
you can also follow history at https://github.com/jcadduono/lazyflasher/commits/no-verity-opt-encrypt
Click to expand...
Click to collapse
Awesome! Well, THANK YOU because I was bootlooped for several hours. You helped me so much!
Does anyone has TWRP backup ? I tried the stock fastboot backups and manage to flash system.img and boot.img files but I am still stuck on ZTE Logo Screen.

Categories

Resources