Develop Bugs

[Q] Is it possible to flash the Android Lollipop Dev Preview without formatting?

I cant wait til the ota comes out to try out lollipop. I've read some articles that it can be flashed via the "official" way a.k.a. the fastboot way but i need to wipe all data. I already have a unlocked boot loader so maybe theres a way to skip the formatting? I found an article that i can edit the fastboot flash script to not wipe my device but its noted that its not guaranteed to work. Have anyone tried this yet? Maybe just like updating roms that dont need wiping the device?
The androidpolice webpage http://www.androidpolice.com/2014/1...ilable-for-the-2013-wifi-nexus-7-and-nexus-5/
And
http://www.howtogeek.com/176284/how...-without-waiting-by-flashing-a-factory-image/

Just did the update to Lollipop dev preview from the last "L" preview without wipe (via editing out the -w from the script). Haven't had a problem doing this before, aside from having to unfreeze stock Chrome (I use Chrome Beta) and uninstalling CF.Lumen drivers. So far, it's working fine for me. However, the boot animation stayed on quite a bit longer than usual before it reached the "Android is upgrading" screen. It was on the boot animation for a good 3-5 minutes, so don't consider hard resetting it so soon.
Update: I ended up having to do the "SetupWizard" fix to restore notification pull-down functions, and possibly Google syncing related features.
http://www.androidpolice.com/2014/0...at-refuses-to-pull-down-after-android-update/
Good luck with the upgrade without wipe.

divadkha said:
Just did the update to Lollipop dev preview from the last "L" preview without wipe (via editing out the -w from the script). Havent had a problem doing this before, aside from having to unfreeze stock Chrome (I use Chrome Beta) and uninstalling CF.Lumen drivers. So far, its working fine for me. However, the boot animation stayed on quite a bit longer than usual before it reached the "Android is upgrading" screen. It was on the boot animation for a good 3-5 minutes, so dont consider hard resetting it so soon.
Update: I ended up having to do the "SetupWizard" fix to restore notification pull-down functions, and possibly Google syncing related features.
http://www.androidpolice.com/2014/08/07/how-to-fix-missing-home-and-recents-buttons-and-notification-shade-that-refuses-to-pull-down-after-android-update/
Good luck with the upgrade without wipe.
Click to expand...
Click to collapse
Thank you for your information. But in your case its android l to android l which is not quite a huge jump. But I'm from kitkat to lollipop. Will that be any difference?

ImjuzCY said:
Thank you for your information. But in your case its android l to android l which is not quite a huge jump. But I'm from kitkat to lollipop. Will that be any difference?
Click to expand...
Click to collapse
You don't HAVE to wipe data before updating to a new OS version but from my personal experience I very strongly believe that wiping the data will give a more reliable update in the long term and have less chance of buggy user installed apps. One thing to think about is the fact that an OTA will NOT ever wipe data. With "minor" updates (like 4.4.3 to 4.4.4) I just fastboot flash the system image and whatever else is necessary which will keep all of the user apps installed and all the settings intact. With "major" OS updates I sometimes but not always do a factory reset from inside TWRP which will not wipe the storage then use TWRP to go into the bootloader and flash whatever from there. With the flash_all batch file modified you could flash the factory image (L preview) and have a clean install and not have your storage wiped. If you instead fastboot flash the bootloader, boot and system images separately instead of using the flash_all batch file you don't replace the custom recovery (TWRP) with the stock recovery. If you don't have a custom recovery installed and want a clean install you have no choice but to wipe everything. Save what you want from your storage to your computer. If you do have a custom recovery make a backup (nandroid) first. But... my personal opinion is that an OTA will not be as reliable as a clean install, again, not that I always do a clean install. Another thing to think about is how important is a clean install now anyway, the official 5.0 update isn't too far down the road. Do what feels comfortable for you, you have multiple choices.

wantabe said:
With "major" OS updates I sometimes but not always do a factory reset from inside TWRP which will not wipe the storage then use TWRP to go into the bootloader and flash whatever from there.
Click to expand...
Click to collapse
Thanks for your detailed explanation. But I have a question. You said you sometimes do a factory reset from TWRP *which will not wipe storage*. But according to TWRP's website, factory reset means wiping everything. Isn't it? Or you mean the sdcard partition?

ImjuzCY said:
Thanks for your detailed explanation. But I have a question. You said you sometimes do a factory reset from TWRP *which will not wipe storage*. But according to TWRP's website, factory reset means wiping everything. Isn't it? Or you mean the sdcard partition?
Click to expand...
Click to collapse
Yes and no! Doing a factory reset from your device settings "Settings/Backup & reset" will absolutely wipe Everything on your device. If you do a factory reset from inside TWRP it will Not wipe your device storage. When you open TWRP and tap on "Wipe" the screenshot shows what you will see. Excuse the screenshot, it's hard to get the camera to focus on a shiny screen. The only way to do a factory reset/wipe data that I know of without wiping the storage is with a custom recovery.

wantabe said:
Yes and no! Doing a factory reset from your device settings "Settings/Backup & reset" will absolutely wipe Everything on your device. If you do a factory reset from inside TWRP it will Not wipe your device storage. When you open TWRP and tap on "Wipe" the screenshot shows what you will see. Excuse the screenshot, its hard to get the camera to focus on a shiny screen. The only way to do a factory reset/wipe data that I know of without wiping the storage is with a custom recovery.
Click to expand...
Click to collapse
Oh! Thank you very much for the explanation. Wiping data partition means clearing all user installed apps right? If its true then I rather wait for the ota. I don't wanna waste too much time on backing up and restoring apps. Thanks anyway

ImjuzCY said:
Oh! Thank you very much for the explanation. Wiping data partition means clearing all user installed apps right? If its true then I rather wait for the ota. I don't wanna waste too much time on backing up and restoring apps. Thanks anyway
Click to expand...
Click to collapse
Correct! Wiping the data will always remove the user installed apps. Wiping from inside your device settings or from inside TWRP will determine if your storage gets wiped. Don't forget... there is more than one way to flash a factory image, in this case the Android L preview, without wiping any data.
1. Modify the flash_all.bat that is inside the factory image with a text editor (notepad) removing the text -w. Takes like 5 seconds to modify the text.
fastboot flash bootloader bootloader-flo-flo-04.04.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot -w update image-razor-lpx13d.zip
fastboot flash bootloader bootloader-flo-flo-04.04.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot update image-razor-lpx13d.zip
2. Fastboot flash the bootloader, boot and system images.
Either way it takes longer for android L to boot up the first time than it does to flash the images. Just saying!

Backup it all! (Before execution of some operations that can cause data loss)
You just need to download this tool.
If your bootloader is really unlocked, then they'll be no problems out there!
Make sure your Nexus Device is connected to your Computer with a MicroUSB-Cable!
But do never use a slack joint cable! They'll cause many problems there!
Launch the Toolkit and it should detect your Tablet!
Go to the Installation-Guide on the Main-Menu and then install the GoogleADB-Driver.
That's the 1st(2nd?) ever time i'm using the USB-Icon on a Post!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
Go to the BackUp-Menu and execute a full-Android ADB-Backup
Make sure your device is connected to the Computer!
And after the backup then make sure the BackupFile is there to make sure that to avoid a Blank 0B-File or no file at all!
If you've got any questions left then ask me anytime! Anytime you ever want!
All the best!
❤Hannah(❤❤❤!)
---------- Post added at 07:41 PM ---------- Previous post was at 07:39 PM ----------
Hannah Stern said:
Go to the BackUp-Menu and execute a full-Android ADB-Backup
Click to expand...
Click to collapse
Sorry! What i mean is the Full N'Android /W/ Backup!
All the best,
Hannah:laugh:

How to install cyanogenmod on HTC One M8?

Hi,
I searched online for 2 hours but I see a lot of mixed, outdated articles, videos. For example Hasoon's app link doesn't work, or the cyanogenmod installer link for your phone is giving me 404.
I don't want to do something stupid so can someone tell me or show me a guide on how to install this?
My phone is from Rogers (contract ended). I just want a fast and light weight android without bloatware and nice features.
Will I have to find a cyanogenmod release from someone who use Rogers, or can you use the same build on that's built for M8 regardless of your phone company?
Thanks a lot.

Have you done anything to the phone yet (unlock bootloader, s-off, root, etc.) or still just fully stock?
Is the phone currently on Lollipop? You'll want updated hboot to run current CM12.1.
Don't bother with toolkits and the like. The toolkits haven't been updated in over a year, contain obsolete files, and that will cause you more problems than anything. The steps are not that hard to do "manually", and that is a much better learning process. The toolkits shortcut that learning process; putting you in a position to get into a jam, with no knowledge of how to get out of it.

Thanks a lot for replying. I unlocked the bootloader, s is off, but I don't know how to root. I think it's superSU right? If so, I assume I will do this by installing this zip after I flash the cyan mod?
I downloaded these to my phone:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I assume I just have to format/adv format everything and install these zip files using TWRP, right? If so, that wasn't hard
But I have another problem. I don't have an SD card or OTG cable to store these zip files outside the phone. I have usb flash memory/stick, HDDs but AFAIK I need OTG cable to use them with my phone.
Also another thing that concerns me is the new Android version is coming next week, right? So should I wait for it and use that cyan mod?
Are you able to get OTA updates with cyan as easily without having to flash your phone every time?
Thanks again

lachdanan said:
Thanks a lot for replying. I unlocked the bootloader, s is off, but I don't know how to root. I think it's superSU right? If so, I assume I will do this by installing this zip after I flash the cyan mod?
Click to expand...
Click to collapse
No need to flash SuperSU to root after flashing CM.
Go into Developer's Options in phone's settings (may need to tap version number 7 times to make Dev Options appear) then turn on root there.
lachdanan said:
I assume I just have to format/adv format everything and install these zip files using TWRP, right? If so, that wasn't hard
Click to expand...
Click to collapse
Before doing anything, make a TWRP backup of your current (presumably stock Sense) ROM.
Then backup any user data you want to keep, by method of your choice (Titanium Backup, cloud, copy to PC, etc).
Then do a wipe. I would only recommend the default Wipe option (user data, cache and Dalvik) in TWRP. Right in TWRP, it says "most of the time, this is the only wipe you will need" (or words close to that effect) and it says that for good reason.
You certainly don't want to wipe "everything". If you wipe internal storage, you will lose the TWRP backup I just told you to make. Plus you will wipe the ROM and gapps zips you are going to flash, if you put them on internal storage.
Some folks swear by wiping system when flashing ROMs. I don't like this, since if for some reason the ROM fails to flash, you are then stuck with no OS (although you will have a TWRP backup, that I just told you to make). If you run into problems, you can always wipe system later and flash again. But honestly, after many ROM flashes on several different devices, and I've never once had to wipe system, that I recall. Unless of course the ROM instructions require to wipe system. If that is the case, follow the instructions.
After default wipe, flash the ROM, and flash gapps. Then reboot.
lachdanan said:
But I have another problem. I don't have an SD card or OTG cable to store these zip files outside the phone. I have usb flash memory/stick, HDDs but AFAIK I need OTG cable to use them with my phone.
Click to expand...
Click to collapse
I don't follow what the problem is. It looks like you have the files on a PC. Just connect your phone by USB, then copy and past the files to the phone's internal storage.
Don't know why you want to store the files "outside the phone" (and not on the PC) unless you are talking about wiping internal storage. Again, it isn't necessary to do that.
lachdanan said:
Also another thing that concerns me is the new Android version is coming next week, right? So should I wait for it and use that cyan mod?
Click to expand...
Click to collapse
It usually takes a bit of time for a new Android version to be ported over to a respective device. Than a bit more time, for it to be fairly stable. So its up to you, but I say why wait. You can always flash again when CM13 (or whatever its going to be called) is released on the M8.
One of the things about flashing ROMs, is it can be addictive. So if you have the urge and time to do it now, just do it!
lachdanan said:
Are you able to get OTA updates with cyan as easily without having to flash your phone every time?
Click to expand...
Click to collapse
I actually don't use CM on the M8, so check the CM thread for any discussion on this.
Even if OTA updates aren't functional (no idea if they are or not), you can often download and "dirty flash" new updates (like nightlies). Dirty flash, means you just wipe cache and Dalvik and flash the ROM, keeping user data. Its very fast, since you don't need to setup the phone again.
Although, sometimes a dirty flash won't work, and you need to do a full flash. When CM13 comes out, you will probably need to do a full wipe before flashing it. And likewise, you probably won't want to do an OTA update to CM13 either.

Thanks a lot man, you cleared many of my questions. Regarding the storage, sorry they are already on my phone, so the phone has internal storage and another separate storage? I thought HTC One M8 had a single storage inside so if you delete things, everything is deleted.
But since you said don't delete system, then this is not an issue?
Also by system, does it mean actual stock android system files? Won't these files conflict with CM's own system files? Or if they are bloated with time, usage etc, then this will leave these unnecessary files behind?
Thanks again

lachdanan said:
Regarding the storage, sorry they are already on my phone, so the phone has internal storage and another separate storage? I thought HTC One M8 had a single storage inside so if you delete things, everything is deleted.
Click to expand...
Click to collapse
Nope, the storage is actually partitioned into something like 41 separate partitions: system, hboot, recovery, radio, data, boot, and (of course) many more.
So when you say you want to wipe "everything" I said you don't want to do this, and I really mean it.
Plus, one of the Advanced wipe options in TWRP is the removable SD, which most folks will not want wiped, most of the time.
So again, use the default wipe option in TWRP. Only pick the Advanced options, if you know exactly what you are doing, and fully understand the result of wiping that selection.
The "default" TWRP wipe just wipes user data, cache and Dalvik. Internal storage (which is data/media) is actually not touched, and that is most likely where you placed the ROM and gapps files (plus its the default location for TWRP backups, Titanium Backup and some other things).
lachdanan said:
But since you said don't delete system, then this is not an issue?
Click to expand...
Click to collapse
Correct.
lachdanan said:
Also by system, does it mean actual stock android system files?
Click to expand...
Click to collapse
If you are still on the stock ROM (haven't flashed any ROM yet, was I assume is the case) then YES, system partition is where the actual stock ROM (stock Android system files) are currently located.
lachdanan said:
Won't these files conflict with CM's own system files? Or if they are bloated with time, usage etc, then this will leave these unnecessary files behind?
Click to expand...
Click to collapse
Nope, when a ROM is successfully flashed, it will wipe system, then install the new ROM on the system partition.
This is another reason why I say its not necessary to manually wipe system in TWRP. It will happen anyway when you flash the ROM. But if for some reason the ROM fails to flash (not unheard of, for various reasons), you will still have have a working phone if you didn't wipe system.

Thanks. I made a stupid mistake before reading your last post, now it seems like my phone's data storage is completely empty I restarted into bootloader and added TWRP to it again using Windows. But then I chose restart on that bootloader menu and now the phone screen is stuck in HTC android boot screen. I couldn't turn the phone off or restart. Do you know how to fix this?

I managed to fix it and now I am in cyan Looks really good, I will be customizing it now but it feels snappy
Thanks again man

TWRP restore error, anyone else with issues

I had done a nandroid back up with system data and boot, I tried to restore and getting 255 error, never had issues with OPO, 3 and 3T, I made 2 backups one before updating and one after updating and getting everything set up, and neither work, using blu_spark, again used on previous devices and no issues ever restoring

can someone please help me, has anyone had to restore a nandroid backup yet, i have done 5 back ups and all 5 give me the error when restoring data. Never had any issues with other devices, Oneplus one, 3/3T never came across this data restore issues. thank you. using Blu_spark TWRP

im in the same boat i had made a stock back up and i went to use it and it gave me the same error, i flashed freedomos and im on that now.

slaya811 said:
im in the same boat i had made a stock back up and i went to use it and it gave me the same error, i flashed freedomos and im on that now.
Click to expand...
Click to collapse
I guess u and I are the only ones, I even tried asking bluespark and no answer, I am stumped, I have clean flashed my phone every day since I have had it the op3 and t were so easy to mod this thing bootloop on everything

Bradl79 said:
I guess u and I are the only ones, I even tried asking bluespark and no answer, I am stumped, I have clean flashed my phone every day since I have had it the op3 and t were so easy to mod this thing bootloop on everything
Click to expand...
Click to collapse
when i flashed Freedomos i ran into problems with that saying insufficient storage in the system partition. its been a very weird flashing experience for me on the 5T. i have been flashing since my touch slide 3g lol

slaya811 said:
when i flashed Freedomos i ran into problems with that saying insufficient storage in the system partition. its been a very weird flashing experience for me on the 5T. i have been flashing since my touch slide 3g lol
Click to expand...
Click to collapse
lol right, i have never had so many problems with a device, especially with TWRP, never had any issues, i was never decrypted on my Oneplus One, 3 and 3T, never any issues, and this is a pain, i could easily extract the apks mod them and move them back most of the times no issues, with this thing i can't even do that b/c it will bootloop, i hope once official TWRP comes out we won't have the flashing issues.

Bradl79 said:
can someone please help me, has anyone had to restore a nandroid backup yet, i have done 5 back ups and all 5 give me the error when restoring data.
Click to expand...
Click to collapse
I have restored multiple times from different backups without issue using blu_spark as well....sorry you're having issues
Bradl79 said:
i could easily extract the apks mod them and move them back most of the times no issues, with this thing i can't even do that b/c it will bootloop
Click to expand...
Click to collapse
Totally unrelated, but this is my 6th or 7th rooted device yet the first one where root uninstaller cannot remove system apps. I get a message that says "rooted, but cannot grant RW on system " There's definitely some quirky stuff with this device.

Dazed No More said:
I have restored multiple times from different backups without issue using blu_spark as well....sorry you're having issues
Click to expand...
Click to collapse
are u decrypted?

My backup and restore process went fine, but I am using the TWRP by blu spark in his kernel thread. Also I am encrypted

Bradl79 said:
are u decrypted?
Click to expand...
Click to collapse
Nope....just to be sure you mean decrypted as in format data correct? Still nope.

Bradl79 said:
are u decrypted?
Click to expand...
Click to collapse
Have you had any luck yet??

slaya811 said:
Have you had any luck yet??
Click to expand...
Click to collapse
i haven't tried yet, i had clean flashed the 1st 5 days i had the device, i just gave up right now until a new update comes out, i did make some changes to my twrp settings that may work, if u would like i will share them with u and see if they work

As far as I know, you have to remove screen lock before backup

bgumble said:
As far as I know, you have to remove screen lock before backup
Click to expand...
Click to collapse
No lock here, still no luck here
Backup = error 255, restore = incomplete

Pfeffernuss said:
No lock here, still no luck here
Backup = error 255, restore = incomplete
Click to expand...
Click to collapse
yeah same here
here are the settings i got from my Oneplus 3 and 3T, have yet to see if it works b/c i was getting tired of clean flashing, but let me know if works
Under Backup - compression optional
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Under Settings

bgumble said:
As far as I know, you have to remove screen lock before backup
Click to expand...
Click to collapse
This is true, but the error they are getting is not related to this.
I have not yet done a backup/restore in TWRP.

Also getting this error on every backup I try and restore. The latest doesn't have security and it still errors out. I found a video on YouTube that states to unmount data to fix the error, but then I don't have access to the backup file.
Can a backup be restored from the PC via ADB?

What if u perform a factory reset in TWRP, then try to restore just the system and boot from your backup? If it boots, u can try restoring data from TWRP. Was your backup encrypted, and when u performed the backup, did u remove fingerprint security first? These can all cause issues with backup & restore.

Maybe it's because you used parallel apps. A new user is created and this causes the error while backing up.
Try this:
Deactivate parallel apps,
in terminal type
su
pm remove-user

Development [ROM] PixelExperience [UNOFFICIAL] [12.1.0] [raven]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
PixelExperience for Google Pixel 6 Pro[raven]
What is this?
PixelExperience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher mod, wallpapers, icons, fonts, boot animation)
Our mission is to offer the maximum possible stability and security, along with essential and useful features for the proper functioning of the device
Based on Android 12.1
Whats working?
Everything I believe
Known issues
Not sure, none so far
DON'T FLASH GAPPS, IT IS ALREADY INCLUDED
Download
Install instructions
From custom recovery
** If not already installed, please download vendor_boot.img & flash via fastboot ( fastboot flash vendor_boot "location to downloaded file" ), then select boot recovery in fastboot after flash in finish.
vendor_boot.img
1. Factory Reset
2. Apply Update via ADB, sideloading the downloaded file
3. Reboot to bootloader
4. Apply Magisk Boot ( Patched Magisk Boot v25.2 )
5. Start
Donate
Not needed but always welcomed
Keep in touch
Telegram channel
PixelExperience blog
Android OS version: 12.1
Kernel Source

Awesome to see PE on the 6 Pro! Any chance it becomes Raviole or if there will be a Pixel 6 Oriole build as well?

Pixel-ception right there, experiencing Pixel on a Pixel lol

Always wanted to get a pixel experience on my pixel!

device and kernel source ?
@alvin14
​

Can someone who's tested this post a couple of screenshots of any special settings this might have over stock? I mostly want to compare those against DerpFest that was released a couple of days ago and to avoid flashing again since we don't have a way to backup and restore a rom at this point. Unless - could Slot B be used to dual boot two different roms?

Ulyaoth said:
Can someone who's tested this post a couple of screenshots of any special settings this might have over stock? I mostly want to compare those against DerpFest that was released a couple of days ago and to avoid flashing again since we don't have a way to backup and restore a rom at this point. Unless - could Slot B be used to dual boot two different roms?
Click to expand...
Click to collapse
Currently, you cannot dual boot multiple roms. I remember with OP6T, there was a guy/gal that provided us with a recovery that allowed dual boot for two different roms. It was a wip, but functioned pretty well. Can't recall the Dev's name.
Concerning screenshots of custom settings, I'm sure it's similar to other Pixel Experience roms for other devices. I can't provide any, because I'm not using this particular custom rom at the moment.

@alvin14 Please check your PM inbox. Thank you.
-Regards: Badger50

@alvin14, to sideload you'll need to provide both the boot.img and vendor_boot.img, otherwise we can't use adb sideload since stock recovery will reject it and it's looking pretty unlikely we'll get twrp anytime soon. For those of us who are technically minded, grabbing the 2 .img files I mentioned isn't too hard, but I'm guessing there's some who likely can't.
Also, you might want to provide your kernel source as per XDA rules like the mod has likely PMed you about. This thread will likely get removed/locked and your links taken down if you don't.

Sorry, have not done this since the S4. Kernel source added, forked from PE-Raven. Other files added as well. Not much options added to pixel experience, I personally prefer stock android which i did some development on about 8 years ago. Just light modifications added, very stable.

alvin14 said:
Sorry, have not done this since the S4. Kernel source added, forked from PE-Raven. Other files added as well. Not much options added to pixel experience, I personally prefer stock android which i did some development on about 8 years ago. Just light modifications added, very stable.
Click to expand...
Click to collapse
For the vendor_boot.img to even boot recovery, you need the boot.img from your build as well. Stock boot.img won't work in almost all cases of custom roms.
Appreciate the work, and newer devices are kind of a pain to know what to do. So I feel ya there.

dragynbane222 said:
For the vendor_boot.img to even boot recovery, you need the boot.img from your build as well. Stock boot.img won't work in almost all cases of custom roms.
Appreciate the work, and newer devices are kind of a pain to know what to do. So I feel ya there.
Click to expand...
Click to collapse
Boot not needed. After flashing vendor_boot via fastboot you can select boot bootloader and it goes straight in. Magisk Boot is also provided should anyone still need the boot image.

Ulyaoth said:
Can someone who's tested this post a couple of screenshots of any special settings this might have over stock? I mostly want to compare those against DerpFest that was released a couple of days ago and to avoid flashing again since we don't have a way to backup and restore a rom at this point. Unless - could Slot B be used to dual boot two different roms?
Click to expand...
Click to collapse
Isn't most things backed up online lately? Before every custom ROM flash, backup your data to Google & restore after flash. Don't really use much apps however I would believe they all offer online backup via Google. Signing back into everything should be a breeze since your passwords are also backed up wether to Google or whichever backup app used for that with auto sign in activated.

alvin14 said:
Isn't most things backed up online lately? Before every custom ROM flash, backup your data to Google & restore after flash. Don't really use much apps however I would believe they all offer online backup via Google. Signing back into everything should be a breeze since your passwords are also backed up wether to Google or whichever backup app used for that with auto sign in activated.
Click to expand...
Click to collapse
Yeah but there's still things that are either not backed up or not restored. For example call logs and device settings are backed up but they've never successfully restored on any of my devices. Then there are things like the pixel launcher home screen layout, signing in to apps, setting my ringtone etc., setting up a multilingual keyboard and so on. The ideal scenario for me is to be able to switch roms without wiping data, but I need to have a backup fallback or else it's going to take me hours of tweaking and setting management to be comfy(not to mention any ROM-specific settings that have crazy amounts of time-consuming customizations)

Ulyaoth said:
Yeah but there's still things that are either not backed up or not restored. For example call logs and device settings are backed up but they've never successfully restored on any of my devices. Then there are things like the pixel launcher home screen layout, signing in to apps, setting my ringtone etc., setting up a multilingual keyboard and so on...
Click to expand...
Click to collapse
I had to comment here because this is both true and not true. The backups seem to work, however, they usually don't restore ALL of said data when you restore from a backup onto a wiped phone. Oddly enough, when I wiped my phone yesterday and updated to the final Android 13 beta build (A13B4.1), I was able to restore my data and it kept all of my settings intact... So, not only did I get all of my apps back (and put onto the home screen in the correct locations), but I also got my home screen wallpaper set again; I got my QS tile's arranged how I had previously customized them and I got my other settings restored to how they were...
I'm not entirely sure why this occured, however, with a few past beta updates I had lost all of the settings that I had mentioned... I would usually only get my apps restored (without them being placed on the home screen at all)...
One thing to note is that I happened to do this update differently than a bunch of my previous updates. I did this update manually over adb instead of using the Android Flash Tool site. Of course, take this with a grain of salt as I'm not entirely sure if this is what made my backup restore yesterday so perfect. But my only thought is that by doing the update manually, you won't be missing out on any of the fastboot commands that may be dismissed via the Android Flash Tool

Wifi calling is missing in action..

yyz71 said:
Wifi calling is missing in action..
Click to expand...
Click to collapse
I don't have that feature in my country so I never looked into that.
Thanks will look into it.

alvin14 said:
I don't have that feature in my country so I never looked into that.
Thanks will look into it.
Click to expand...
Click to collapse
Thanks great ROM

BMHater12 said:
Pixel-ception right there, experiencing Pixel on a Pixel lol
Click to expand...
Click to collapse
dex2grigg said:
Always wanted to get a pixel experience on my pixel!
Click to expand...
Click to collapse
Awesome contribution! For all you give to the community i would like to buy you both lunch!
What is it exactly that trolls eat by the way?

NippleSauce said:
I had to comment here because this is both true and not true. The backups seem to work, however, they usually don't restore ALL of said data when you restore from a backup onto a wiped phone. Oddly enough, when I wiped my phone yesterday and updated to the final Android 13 beta build (A13B4.1), I was able to restore my data and it kept all of my settings intact... So, not only did I get all of my apps back (and put onto the home screen in the correct locations), but I also got my home screen wallpaper set again; I got my QS tile's arranged how I had previously customized them and I got my other settings restored to how they were...
I'm not entirely sure why this occured, however, with a few past beta updates I had lost all of the settings that I had mentioned... I would usually only get my apps restored (without them being placed on the home screen at all)...
One thing to note is that I happened to do this update differently than a bunch of my previous updates. I did this update manually over adb instead of using the Android Flash Tool site. Of course, take this with a grain of salt as I'm not entirely sure if this is what made my backup restore yesterday so perfect. But my only thought is that by doing the update manually, you won't be missing out on any of the fastboot commands that may be dismissed via the Android Flash Tool
Click to expand...
Click to collapse
I recommend Swift Backup. I've been using it for quite awhile and it backs up everything!! Call logs, messages, apps and their data. You can backup to the device and transfer to pc for safe keeping or you can even have the option to backup and restore from the cloud. You can also do what I do and get a OTG cable and backup and restore right from that which is much faster.

Question TWRP / Orangefox (nandroid) backup & restore on a/b device (munch) possible?

Hello,
I ran into a couple of problems, because my last phone was an LG G5 and had no a/b slots, so I'm new to this. I did read lots, and found that some folks say things about data encryption etc. But the version of orangefox we have for munch (thanks! @iscle for ofox and @M1LL3R for twrp) supports (de)crypt DATA. I managed to do a full backup of all partitions. But I am asking now if someone tried to restore a backup, yet? Somehow I messed up the OS, I got to "rescue party" reboot loop / boot to recovery - twice - no fun, google it. Sort of fixed it 2nd time by choosing other slot to boot, but magisk is gone. So now, because I need the phone in the next few weeks daily and don't have time to do a full new flash of OS, I don't dare to restore the backup right now in case something goes wrong.
When I have time, I will flash Poco firmware and do full reset and flash custom rom again, but I can't right now. So any information is very much appreciated!

DidierMoulin said:
So any information is very much appreciated!
Click to expand...
Click to collapse
I made backup using and twrp and orangefox: System, boot, data. Then immediately restored the data - the phone did not turn on. Made backup else time. Format data - restore data, don't turn on. Phone freezes on the miui logo. I don’t know what is the problem, I couldn’t restore using backup copy.

Thank you @Dimon909. I found time and trried it, too. Just freezes at boot screen (in this case the evo x boot logo) with strange colors at logon screen. Maybe something wrong with DATA. Recovery works afterwards, though. Maybe it's necessary to switch slots after restoring? Or before, but wouldn't make any sense, I guess.

DidierMoulin said:
Maybe something wrong with DATA. Maybe it's necessary to switch slots after restoring?
Click to expand...
Click to collapse
Backup of data was made several times. There cant be errors.
If I saw that the system was installed at slot A, I installed backup in the same partition. If in B - switched to B. It did not help. Seems TWRP has not been completed. And i cant move, delete system fails (ex. any .apk in system_root/system/app). System is only read. Some protection installed ?
Maybe it's all because data is encryption?

That's what I ment, some problems with restoring data (not because of wrong backup) but while restoring or booting, maybe because of encryption, like you said. though after I flashed the same rom or an update of it several times, both slots (a/b) should have contained the same decryption key, I guess.
I didn't pay attention to that, but if you switched to the right slot, then there's a different problem. Next time I'll check if it's slot related, by using both slots to restore, one after another and try to boot either.
What surprises me, is that twrp (or ofox) work with encryption and that I restored whitout changing encryption key on data (at least I think so, maybe even a new dirty rom flash does something?).

it's a problem of recovery

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Yes, I read that, too. But it says:
* Restoring data backup in MIUI will result in a bootloop 100% of times.
Click to expand...
Click to collapse
I didn't have MIUI left on my device, afaik. So did you restore DATA from any custom rom, yet?

DidierMoulin said:
Yes, I read that, too. But it says....
Click to expand...
Click to collapse
maybe the creator of orangefox tried to restore data only on miui?
I tried on evolution ROM - bootloop.
But new SparkOs data can restore from backup.

Dimon909 said:
maybe the creator of orangefox tried to restore data only on miui?
I tried on evolution ROM - bootloop.
But new SparkOs data can restore from backup.
Click to expand...
Click to collapse
Ha ha, so I am on evolution now, but don't want to try really if it works ...

DidierMoulin said:
Ha ha, so I am on evolution now, but don't want to try really if it works ...
Click to expand...
Click to collapse
And don't need try. After restoring data of SparkOS the phone turned on, but the data became encrypted (hieroglyphs)

Dimon909 said:
And don't need try. After restoring data of SparkOS the phone turned on, but the data became encrypted (hieroglyphs)
Click to expand...
Click to collapse
Here https://orangefox.download/release/634aea7f3c05f43c193c2c92/buildnotes it says to restart the phones once or twice via power button. If I remember correctly it did it even three times (reboot), but that was with an older version of ofox and evolution, still didn't work.