Related
hello,
i rooted my Huawei and then used Root Tools to flash a font on it (don't remember which one it was).
Now my device seems to start, the hard buttons light up, but i get an infinite boot loop!
i can get into recovery, but i don't know how to get into fastboot.
I have already done a factory reset via recovery, but it keeps happening.
can anyone help me?
EDIT: also, since i cant get into the phone, i can't enable usb debugging to get to adb either... is there any way to force this or something?
Have you tried to wipe all phone-data and flash it with a rom?
Yeah, i've tried the flash all in recovery. i want the stock ROM though, do you have an update.zip for that? i'm pretty sure i can borrow a microSD card and put it on there.
jerry00 said:
Yeah, i've tried the flash all in recovery. i want the stock ROM though, do you have an update.zip for that? i'm pretty sure i can borrow a microSD card and put it on there.
Click to expand...
Click to collapse
So does it work with the rom you tried?
You can find the stock-rom on the huawei-device webpage if you haven't done a backup..
Edit: for ROMS check this:
http://wiki.modaco.com/index.php/Huawei_Firmware_U8800
sentiment said:
So does it work with the rom you tried?
You can find the stock-rom on the huawei-device webpage if you haven't done a backup..
Click to expand...
Click to collapse
oh, no, i have the stock recovery, i just did the "wipe data/factory reset"
i can't found the stock rom on the webpage... could you please link me to where it is?
jerry00 said:
oh, no, i have the stock recovery, i just did the "wipe data/factory reset"
i can't found the stock rom on the webpage... could you please link me to where it is?
Click to expand...
Click to collapse
you should install perfect recovery, you can find it here on the ideos x5 development section and then wipe data and apply the rom you wan't, i think that should fix your phone
sentiment said:
you should install perfect recovery, you can find it here on the ideos x5 development section and then wipe data and apply the rom you wan't, i think that should fix your phone
Click to expand...
Click to collapse
well, i'd want it to be as stock as possible, in case it needs to go to service once... but as for the stock rom, is that the kernel-2.6.32-U8800-Froyo file on huaweis website? should i just rename that to update.zip and use it?
EDIT: i saw your edit now, when i have downloaded the right .zip file(in this case the norway retail one), i'm going to rename that to be update.zip and upgrade with it, am i right?
EDIT2: okay, i'm just going to follow the instructions in the zip folder one final question: how do i check my build number?
yes you can rename it, but it's not even necessary because you can choose the file (rom) you want to install later in perfect recovery. Or are you using something else then perfect recovery?
I have no idea about the instructions in the zip folder, because i haven't installed any stock roms on my phone, and can't understand what you need the build number for?
I suggest you to try to install that stock rom because you have nothing to lose and it's easy to wipe data again and try with other roms again..
sentiment said:
for ROMS check this:
http://wiki.modaco.com/index.php/Huawei_Firmware_U8800
Click to expand...
Click to collapse
Thanks! i downloaded the corresponding zip file for my carrier, unzipped, and just followed the instructions in the pdf file
The phone works great now! i am very happy now
This happened to me this morning!! Is there anyway to fix this in Recovery mode by mounting /system or something and rename the backup of the font back?
I don't want to delete everything off the phone! I have been customizing it for the past 2 or 3 weeks.. and was getting it exactly how I wanted it.. Don't want to do it all over again
EDIT: PHEW.. I fixed it. All you have to do is rename every font back to how it was originally (hope you have a backup) and set the permissions back to how they were originally CHMOD 644
If you need more help let me know, tell me which OS you have.. if you have Ubuntu / Linux I can help you.. no problem, as for windows.. I don't know
for windows the procedure is pretty much the same, i guess you used adb
That is what I love about ubuntu.. no I did not have to use adb. It automatically mounted the drives when I booted in recovery mode, then browsed system partition as root user (using natalius script.. or you can use a terminal) then set the permissions of the fonts to 644, make sure all the fonts are named exactly (CASE SENSITIVE).
Reboot and it will work.
Hello. I just received my OTA notification, but when I clicked it, it rebooted and landed my on the TWRP recovery screen. Not knowing what to do, I just told it to reboot to the system.
Once rebooted, I was still on 4.2.1, and there was no update.
Any ideas why it booted to TWRP?
The OTA update requires stock recovery in order to be flashed. I recommend you just flash the update manually using fastboot, and you won't lose data.
MacHackz said:
The OTA update requires stock recovery in order to be flashed. I recommend you just flash the update manually using fastboot, and you won't lose data.
Click to expand...
Click to collapse
Maybe before you even answer, I'm sure I'll find a link on here to show me how?
One issue I have though, is that when I manually updated to 4.2.1 on my Nexus 7, I still got an OTA update a few days later, that actually ran.
I don't ever plan on flashing roms to any of my devices. Do I need to keep a custom recovery on my Nexus 4 or 7? If not, how to I revert back to the stock recovery?
If you saved the offical stock 4.2.1 images, to revert back to stock recovery, just use the 'fastboot flash recovery recovery.**************.img' command. If you haven't, you might have to flash the whole 4.2.2 rom which you can find on the google dev website. After this, if you only want to root then you don't need to flash a custom recovery, just use the 'boot' command instead of the 'flash' one.
MacHackz said:
The OTA update requires stock recovery in order to be flashed. I recommend you just flash the update manually using fastboot, and you won't lose data.
Click to expand...
Click to collapse
I flashed the OTA sideload file through TWRP and it installed succesfully.
jvbferrer said:
I flashed the OTA sideload file through TWRP and it installed succesfully.
Click to expand...
Click to collapse
How did you do that? Did you sideload wrinkle's file from this thread: http://forum.xda-developers.com/showthread.php?t=2145848?
I should let you know, that while I'm not afraid to install via the custom recovery, it doesn't mean I've done it via commands. I've always used toolkits, or one click methods of rooting and installing custom recoveries.
Well, this is crazy (weird?). I tried to flash it via TWRP by downloading the zip file in the thread referenced above, and it failed. By flashing, I mean, I chose 'Install' and pointed to the zip after moving it to my phone. After failing, I wiped the Dalvik cache and rebooted, and it's telling me 'Android is upgrading'. If it means it updated, so be it. But can anyone explain? Feeling a little confused here.
Edit: Ok, so it said it was upgrading, but it's still 4.2.1.
wvcadle said:
Well, this is crazy (weird?). I tried to flash it via TWRP by downloading the zip file in the thread referenced above, and it failed. By flashing, I mean, I chose 'Install' and pointed to the zip after moving it to my phone. After failing, I wiped the Dalvik cache and rebooted, and it's telling me 'Android is upgrading'. If it means it updated, so be it. But can anyone explain? Feeling a little confused here.
Edit: Ok, so it said it was upgrading, but it's still 4.2.1.
Click to expand...
Click to collapse
It 'upgrades' when you wipe the cache. It just means it's rebuilding the cache. Are you running an unmodified stock rom? Custom kernel?
MacHackz said:
It 'upgrades' when you wipe the cache. It just means it's rebuilding the cache. Are you running an unmodified stock rom? Custom kernel?
Click to expand...
Click to collapse
Yes, stock rom, rooted and unlocked. I did install Beats today. Could this be the problem? If so, I found a revert zip that I'm assuming is supposed to revert me back to stock audio codecs.
I don't think added files matter, but I'm guessing the Beats mod has overwritten something in system, so flash the revert zip, then try again.
MacHackz said:
I don't think added files matter, but I'm guessing the Beats mod has overwritten something in system, so flash the revert zip, then try again.
Click to expand...
Click to collapse
Flashing the revert zip failed. I'm starting to think that flashing anything with TWRP will fail.
How about this. I made a backup of all system data + apps with Titanium earlier today. Could I just reset my phone back to factory defaults, restore my apps + some system data, then re-root (*without a custom recovery*) and wait for the update again? Or will it come again?
Also, I've used Wugfresh's Nexus Toolkit. I don't remember checking the custom recovery button, but ended up with TWRP anyway. What's the easiest way to root without installing a custom recovery?
You could try that, and the update will come straiht away. You can root without flashing a custom recovery, just use the 'boot recovery' instead of 'flash recovery'
MacHackz said:
flash cwm and see if there's any difference
Click to expand...
Click to collapse
How do I do that with TWRP? Can I do it with Wug's Nexus toolkit?
wvcadle said:
How do I do that with TWRP? Can I do it with Wug's Nexus toolkit?
Click to expand...
Click to collapse
I'm not familiar with any toolkits, I would recommend flashing cwm using fast boot
MacHackz said:
I'm not familiar with any toolkits, I would recommend flashing cwm using fast boot
Click to expand...
Click to collapse
Ok, I'm surely not afraid to use the command prompt. Any tutorials you can point me to? I probably already have all of the drivers I need, as the toolkit had to download install them.
wvcadle said:
Ok, I'm surely not afraid to use the command prompt. Any tutorials you can point me to? I probably already have all of the drivers I need, as the toolkit had to download install them.
Click to expand...
Click to collapse
Check out this thread. Use flash to flash and overwrite TWRP, or boot just to test. http://forum.xda-developers.com/showthread.php?t=1995440
MacHackz said:
Check out this thread. Use flash to flash and overwrite TWRP, or boot just to test. http://forum.xda-developers.com/showthread.php?t=1995440
Click to expand...
Click to collapse
Where in that thread does it show me how to flash the stock recovery back onto my device?
wvcadle said:
Hello. I just received my OTA notification, but when I clicked it, it rebooted and landed my on the TWRP recovery screen. Not knowing what to do, I just told it to reboot to the system.
Once rebooted, I was still on 4.2.1, and there was no update.
Any ideas why it booted to TWRP?
Click to expand...
Click to collapse
The same thing happened to me. I was rooted running stock ROM with TWRP recovery (used wugfresh toolkit). The problem was I forgot I was using a modified kernel (for color correction) by molesarecoming. I flashed the stock kernel back, downloaded and flashed the OTA file from the help desk thread (http://forum.xda-developers.com/showthread.php?t=2145848&highlight=beats), and it worked. Oh, and I flashed the Superuser file immediately after the OTA did it's thing (while still in TWRP) to regain root. I didn't really like how after the initial failed install of the OTA, it took my into TWRP with no error message showing or anything.
I don't think TWRP is your problem -- I think beats is your problem. It may have modified something. Try searching the above-linked thread for answers. Honestly, there's no rush to get 4.2.2, so take your time finding the answer. It's better than wiping the phone just to install a small android update and having to redo everything on your phone again.
Ok, it must have been the Beats audio drivers. I restored a Nandroid backup from right before installing the beats audio drivers, then flashed the zip and it worked. Now running 4.2.2.
I would like to know, however, how to use fastboot via commands, so that I can learn how to flash TWRP, CWM, Stock recovery, etc.
wvcadle said:
Ok, it must have been the Beats audio drivers. I restored a Nandroid backup from right before installing the beats audio drivers, then flashed the zip and it worked. Now running 4.2.2.
I would like to know, however, how to use fastboot via commands, so that I can learn how to flash TWRP, CWM, Stock recovery, etc.
Click to expand...
Click to collapse
I need some help here - I have nexus 7 with 3G and Google (takju) with 4.2.1 installed.
I had it 'rooted" and installed TWRP .
AT the time I followed instructions to chand extension of some file to .bak - to prevent 'unrooting"
I do not remember which file I unfortunately changed.
Now I cannot install the 4.2.2 upgrade - the OTA fails because it boots into TWRP and after that I rrid several selections from TWRP screen (flash, reboot, etc) - but all attempts failed.
I have the upgrade files (bot .tar and .zip) on /sdcard directory but have no idea how to update to 4.2.2.
Tried manual flashing using adb command - all fails.
I do not have beats drivers installed
Can someone tell me how to uninstall TWRP? If the CWM recovery works with this upgrade, I would like to change from TWRP to CWM.
Or any other suggestion wold be appreciated.
I am really struggling with Android operating system the way it configured on Nexus 7 by Google - any simplest is a major pain!
Hope I can get out of this and operate the device instead of continuously meddling with operating system.
Thanks in advance
[email protected]
I have been having problems trying to flash a rom onto my 802d using LgFlashtool, it gets dtuck at 15% saying the phone isn't connectedvia USB. Is there a way to flash a kdz file using twrp, if so are there any tutorials on it.
Thanks.
A kdz file is more than just the rom, it is the recovery, partiontable and everything. Restoring a phone to stock with a kdz and flashing a stock rom is not the same thing. So the answer is no, it would not be possible to flash a kdz with twrp.
PedexGaming said:
A kdz file is more than just the rom, it is the recovery, partiontable and everything. Restoring a phone to stock with a kdz and flashing a stock rom is not the same thing. So the answer is no, it would not be possible to flash a kdz with twrp.
Click to expand...
Click to collapse
OK, thanks for the explaination.
Is there an alternate app to LgFlashTool that I could use as I am having connection problems with it?
JollyGiant said:
Is there an alternate app to LgFlashTool that I could use as I am having connection problems with it?
Click to expand...
Click to collapse
No - just follow the instructions to the letter. It works.
I would strongly suggest that you do a FULL factory reset/wipe FIRST.
No Windows OS
LenAsh said:
No - just follow the instructions to the letter. It works.
I would strongly suggest that you do a FULL factory reset/wipe FIRST.
Click to expand...
Click to collapse
How about if you only have Linux OS's on your laptop like me? I'm stuck in bootloops to TWRP over and over, data partition is gone and no backups have it. It was working (magisk - twrp root) for weeks, then I went to flash something with TWRP and when I rebooted, it gave me a message that although I entered the correct encryption password, it's unsafe or something and no choice but to delete all data. I rebooted a few times, then f-it and hit the button because I had backups (I thought). That's when the bootloops began.
Hi all
Got an I9505 on O2 and since lollipop update it restarted a few times by itself. Now it keeps going into a loop where it will restart and the home screen loads, you can use it for about 20-30 seconds and it will reboot again!
Initially when I researched I though it was an app problem but couldn't find the culprit. Then I took it into the Samsung repair centre and they said it needed a clean flash by them. This didn't work and they fitted a new mother board and this still hasn't worked.
I can say that it has twice happened when the Wifi hasn't been working properly so I have turned it off but other than that I have no idea!
Also I have tried rebooting into safe mode but it still does it, aaarrrggghhhh!!!
Any ideas where I can go from here please?
P
Return to kitkat if you can. Otherwise use a custom rom. These would be my suggestions. Since Samsung's repair couldn't fix it, warranty should not be a problem anymore.
Thanks, I am more than willing to try a Custom ROM. Any recommendations? And how easy is it as never done before!
PJBXDA said:
Thanks, I am more than willing to try a Custom ROM. Any recommendations? And how easy is it as never done before!
Click to expand...
Click to collapse
It's fairly easy. Depending on what S4 model you have. Some models have a locked bootloader and that makes the whole thing trickier.
This is what I did:
1) Root with CF-Auto-Root. Thread here.
2) Backup all my apps.
3) Install a custom recovery (TWRP). Download and instructions here.
4) Flash custom rom. Most roms have their own instructions.
You can skip 1 and 2 if you don't want to backup.
Installing a custom recovery can be done using Odin. I recommend TWRP since it's the only one I've used.
Lollipop GPE rom. I've used this rom and didn't have any issues. CM12 seems a bit faster, but the GPE was more stable and bug-free.
Thanks I tried to install the CM12 before you posted using the instructions there but it failed, I assume that it needs to be rooted.
PJBXDA said:
Thanks I tried to install the CM12 before you posted using the instructions there but it failed, I assume that it needs to be rooted.
Click to expand...
Click to collapse
You need a custom recovery to install any rom. It doesn't matter if it's rooted or not.
Get a custom recovery. Get all the necessary zip files (rom, gapps, etc). Place all the zip files on the external sd card. Boot into the custom recovery. Wipe /data, /cache and /dalvik-cache.
Go to Install (if on TWRP), go to the location where you saved the downloaded rom zip and select it. The swipe the slider to begin flashing. Afterwards flash the gapps zip. Reboot.
Also, don't use the recovery posted in the CM12 thread. It was specially made by the dev and will convert your file system to f2fs. What it basically means is that it will wipe your internal storage completely.
GDReaper said:
You need a custom recovery to install any rom. It doesn't matter if it's rooted or not.
Get a custom recovery. Get all the necessary zip files (rom, gapps, etc). Place all the zip files on the external sd card. Boot into the custom recovery. Wipe /data, /cache and /dalvik-cache.
Thanks, doing that now
Click to expand...
Click to collapse
PJBXDA said:
GDReaper said:
You need a custom recovery to install any rom. It doesn't matter if it's rooted or not.
Get a custom recovery. Get all the necessary zip files (rom, gapps, etc). Place all the zip files on the external sd card. Boot into the custom recovery. Wipe /data, /cache and /dalvik-cache.
Thanks, doing that now
Click to expand...
Click to collapse
On the CF-Root page it says to open Odin and click on the PDA button but I cannot find a PDA button!
Edit: It is the AP button on the newer version!
Click to expand...
Click to collapse
GDReaper said:
You need a custom recovery to install any rom. It doesn't matter if it's rooted or not.
Get a custom recovery. Get all the necessary zip files (rom, gapps, etc). Place all the zip files on the external sd card. Boot into the custom recovery. Wipe /data, /cache and /dalvik-cache.
Go to Install (if on TWRP), go to the location where you saved the downloaded rom zip and select it. The swipe the slider to begin flashing. Afterwards flash the gapps zip. Reboot.
Also, don't use the recovery posted in the CM12 thread. It was specially made by the dev and will convert your file system to f2fs. What it basically means is that it will wipe your internal storage completely.
Click to expand...
Click to collapse
When you say go to install, do you mean install update... in the recovery menu? I do not have an install from zip option
PJBXDA said:
When you say go to install, do you mean install update... in the recovery menu? I do not have an install from zip option
Click to expand...
Click to collapse
You don't have a custom recovery installed. That is probably the stock recovery. You can't flash a rom using the stock recovery.
You absolutely need a custom recovery if you want to flash a custom rom.
Custom recoveries are: TWRP (Team Win Recovery Project), CWM (ClockworkMod Recovery) and PhilZ Touch Recovery. Either one should work. But you necessarily need one.
GDReaper said:
You don't have a custom recovery installed. That is probably the stock recovery. You can't flash a rom using the stock recovery.
You absolutely need a custom recovery if you want to flash a custom rom.
Custom recoveries are: TWRP (Team Win Recovery Project), CWM (ClockworkMod Recovery) and PhilZ Touch Recovery. Either one should work. But you necessarily need one.
Click to expand...
Click to collapse
Thanks I have installed TWRP, then it asked me to install Busybox which I did. Tried to Install from Zip and it went back to the original recovery and now when I am trying to restart the phone I just get messages telling me things have stopped working (Google play, settings etc etc) and a black screen!
Currently factory resetting and will try again
PJBXDA said:
Thanks I have installed TWRP, then it asked me to install Busybox which I did. Tried to Install from Zip and it went back to the original recovery and now when I am trying to restart the phone I just get messages telling me things have stopped working (Google play, settings etc etc) and a black screen!
Currently factory resetting and will try again
Click to expand...
Click to collapse
Follow the link I gave you. They have several instrunctions on how to install TWRP. You can install TWRP with Odin too.
Here, There are 3 ways to install. Use Odin. It doesn't require root and should be the easier one. Just UNTICK auto-reboot in Odin before flashing. Once it's done, turn the phone off and use the key combo to get into TWRP recovery.
GDReaper said:
Follow the link I gave you. They have several instrunctions on how to install TWRP. You can install TWRP with Odin too.
Here, There are 3 ways to install. Use Odin. It doesn't require root and should be the easier one. Just UNTICK auto-reboot in Odin before flashing. Once it's done, turn the phone off and use the key combo to get into TWRP recovery.
Click to expand...
Click to collapse
I think I am in, got through to the TWRP recovery and flashed the files but now I have a blue face with a pulsing white light behind it and have had for about 10 minutes. Any idea what is happening please?
PJBXDA said:
I think I am in, got through to the TWRP recovery and flashed the files but now I have a blue face with a pulsing white light behind it and have had for about 10 minutes. Any idea what is happening please?
Click to expand...
Click to collapse
I guess that's the CM12 logo. First boot after flashing always takes some time because the rom is configuring stuff.
If you still don't get into android, turn off the device and turn it on again. If you've done everything correctly there is no reason why it shouldn't boot.
GDReaper said:
I guess that's the CM12 logo. First boot after flashing always takes some time because the rom is configuring stuff.
If you still don't get into android, turn off the device and turn it on again. If you've done everything correctly there is no reason why it shouldn't boot.
Click to expand...
Click to collapse
It is their logo but it seems to be taking forever, any idea how long a first boot should take?
PJBXDA said:
It is their logo but it seems to be taking forever, any idea how long a first boot should take?
Click to expand...
Click to collapse
It shouldn't take that long. For me it always took under 5 minutes. Tell me exactly what you did.
GDReaper said:
It shouldn't take that long. For me it always took under 5 minutes. Tell me exactly what you did.
Click to expand...
Click to collapse
Did as you said, in the end I tried flashing the other GPE ROM and that has worked but I do not really like it. Trying the Cynogen again by downloading direct to the SD card and not copying it over. I want to say a very big thank you GDReaper for all your help, it is and has been very much appreciated.
PJBXDA said:
Did as you said, in the end I tried flashing the other GPE ROM and that has worked but I do not really like it. Trying the Cynogen again by downloading direct to the SD card and not copying it over. I want to say a very big thank you GDReaper for all your help, it is and has been very much appreciated.
Click to expand...
Click to collapse
No problem. You could try a different build. Or you could try a CM12 based rom. SaberMod worked fine for me. And it's the closest to the actual CM12 you can get.
GDReaper said:
No problem. You could try a different build. Or you could try a CM12 based rom. SaberMod worked fine for me. And it's the closest to the actual CM12 you can get.
Click to expand...
Click to collapse
Cheers, I have CM12 up and running now. Downloaded the files straight to the SD card and they worked. Seems OK but might try others, how do I go about trying SaberMod, do I need to flash that? Sorry to keep asking what are no doubt pretty obvious questions but I'm pretty new to this!
Want to get rid of the google search box for starters!
PJBXDA said:
Cheers, I have CM12 up and running now. Downloaded the files straight to the SD card and they worked. Seems OK but might try others, how do I go about trying SaberMod, do I need to flash that? Sorry to keep asking what are no doubt pretty obvious questions but I'm pretty new to this!
Want to get rid of the google search box for starters!
Click to expand...
Click to collapse
SaberMod is a rom. SaberMod CM12.1.
They are very similar. The difference is how they tackle optimizations.
Yes, you will have to flash it. But you can also stick with normal CM12 if you don't have any issues.
The google search box from the home screen or the recents?
You can change the launcher to get rid of it from the home screen.
To remove it from the recents there is an option somewhere in the settings.
used to flash my phones back in the day, seems a bit has changed. If you could point me to a guide, maybe where to start?
I've flashed TWRP on a and b, and trying to figure out how to flash a ROM now.
blaczero said:
used to flash my phones back in the day, seems a bit has changed. If you could point me to a guide, maybe where to start?
I've flashed TWRP on a and b, and trying to figure out how to flash a ROM now.
Click to expand...
Click to collapse
It depends on how the Dev set up the rom to be installed. Typically if the rom is .zip, you can install it with TWRP. Once you have downloaded your rom, copy it to your phone to a folder so you can find it easily. Reboot to TWRP and hit the Install button. Then navigate to your folder that has the rom in it and click on it. It should go through the install process and when its done, go back to the main TWRP menu and hit WIPE. If you are changing roms, you have to wipe your data or it won't boot up.
Also when you flash a rom, you are also flashing recovery from that rom and wiping out your TWRP install for that slot. You can re-install if you want.
Usually if your installing an after market rom, the dev will give you installation instructions. Most of the time they use Fastboot & ADB for these double slot phones since TWRP has not been available since its inception until lately.
HolyHog said:
It depends on how the Dev set up the rom to be installed. Typically if the rom is .zip, you can install it with TWRP. Once you have downloaded your rom, copy it to your phone to a folder so you can find it easily. Reboot to TWRP and hit the Install button. Then navigate to your folder that has the rom in it and click on it. It should go through the install process and when its done, go back to the main TWRP menu and hit WIPE. If you are changing roms, you have to wipe your data or it won't boot up.
Also when you flash a rom, you are also flashing recovery from that rom and wiping out your TWRP install for that slot. You can re-install if you want.
Usually if your installing an after market rom, the dev will give you installation instructions. Most of the time they use Fastboot & ADB for these double slot phones since TWRP has not been available since its inception until lately.
Click to expand...
Click to collapse
Thanks for the reply. What is this a and b stuff anyway?
blaczero said:
Thanks for the reply. What is this a and b stuff anyway?
Click to expand...
Click to collapse
Here's a bit of a explanation..
[GUIDE] The Noob's Guide to A/B Partitions and Other OP6 Idiosyncrasies
If you've just arrived on the phone modding scene, or are coming from another phone that uses traditional approaches to flashing, you've likely come across people talking about the "A/B partitions." If you don't have any experience with this...
forum.xda-developers.com