I feel terrible about the camera always suddenly broken down after I unlock bootloader/install custom ROM/root. I want go back to official stock, and maybe lock it again. Here is the thought:
1.fastboot format (this will clean all apps and files in sd card for sure, but does it clean the system to?)
2.fastboot flash all imgs
Or above steps go wrong? Any thoughts on install/flash clean official stock?
Thanks.
fastboot format data, cache, system and then fastboot flash boot, system, vendor
przemcio510 said:
fastboot format data, cache, system and then fastboot flash boot, system, vendor
Click to expand...
Click to collapse
Thanks, try it later.
Normally the bat/sh script delivered in the factory image will do everything for you, except re-locking the bootloader.
https://developers.google.com/android/nexus/images?hl=en#bullhead
faytuu said:
I feel terrible about the camera always suddenly broken down after I unlock bootloader/install custom ROM/root. I want go back to official stock, and maybe lock it again. Here is the thought:
1.fastboot format (this will clean all apps and files in sd card for sure, but does it clean the system to?)
2.fastboot flash all imgs
Or above steps go wrong? Any thoughts on install/flash clean official stock?
Thanks.
Click to expand...
Click to collapse
Not sure what trouble you're having with your camera, but my camera under CM13 is loading wayyy faster than stock, and the quality and stability is exactly the same.
In anyway, if you want to return to stock, just run flash-all.bat under fastboot mode.
Related
Hi! I went into the latest TWRP recovery with unlocked bootloader, and I wiped system, cache, dalvik and data. Then I flashed the proper vendor image, the ROM zip, Gapps and then Elemental X kernel. However, when I reboot, it just boots me into TWRP recovery. I have tried wiping dalvik cache and cache. I then tried restoring a nandroid, but it just got stuck on the Google screen. Didn't even get to the colored dots screen. I ended up flashing factory image, but I would like to get my Nandroids working and this ROM. Please help! Thanks
I'm no expert but I think it might be happening because of encryption. Did you disable encryption before doing all this stuff?
Aman301582 said:
I'm no expert but I think it might be happening because of encryption. Did you disable encryption before doing all this stuff?
Click to expand...
Click to collapse
Encryption in stock Android? As far as I know, I can't turn it off. It says that the device is encrypted in settings. I think nougat forces encryption.
Unless maybe there's a patched kernel that can do that?
NateDev473 said:
Encryption in stock Android? As far as I know, I can't turn it off. It says that the device is encrypted in settings. I think nougat forces encryption.
Unless maybe there's a patched kernel that can do that?
Click to expand...
Click to collapse
I dont think is your problem , im encrypted and never have issues with twrp! Never!! What version of twrp you running? Theres an unofficial kicking around that is much better than official! Maybe you got a bad download! I would redownload all, find and download unofficial twrp 3.0.2.3 I believe. Let your phone boot before you flash custom kernel, thats always worked great for me. The latest official twrps 3022 and 3021 both have nandroid restore issues as well efs restore issues that could ruin your day
Format data and system (format, not wipe) and try installing it again. Should work
OK, thanks
neth15 said:
Format data and system (format, not wipe) and try installing it again. Should work
Click to expand...
Click to collapse
Only data and system? Not cache and dalvik like the purenexus install guide says?
NateDev473 said:
Only data and system? Not cache and dalvik like the purenexus install guide says?
Click to expand...
Click to collapse
Ofc wipe all partitions, but these two also format.
neth15 said:
Ofc wipe all partitions, but these two also format.
Click to expand...
Click to collapse
What's the difference between wipe and format? On TWRP there is only WIPE for all partitions, but a format data button.
NateDev473 said:
What's the difference between wipe and format?
Click to expand...
Click to collapse
Wipe just deletes all data on the partition. Format makes the partition again, therefore it removes encryption, repairs potential problems etc. Format data has dedicated button in TWRP, for formatting System go to Advanced Wipe, check system, tap on Partition details, check EXT4 and perform format.
neth15 said:
Wipe just deletes all data on the partition. Format makes the partition again, therefore it removes encryption, repairs potential problems etc. Format data has dedicated button in TWRP, for formatting System go to Advanced Wipe, check system, tap on Partition details, check EXT4 and perform format.
Click to expand...
Click to collapse
There is no Partition details button. Just fix partition or something like that.
NateDev473 said:
There is no Partition details button. Just fix partition or something like that.
Click to expand...
Click to collapse
Repair or Change filesystem? Yeah, it should be that.
neth15 said:
Repair or Change filesystem? Yeah, it should be that.
Click to expand...
Click to collapse
OK, I will do that. Thanks Just to clarify, I format data and system, and wipe cache and dalvik?
A Thought
Dunno if this will help, but whenever I flash a ROM/kernel combo, I always flash the ROM/gapps, boot up with whatever kernel is included in ROM to make sure it boots properly, and then after successful boot flash EX kernel through TWRP.
OK, so I formatted DATA and SYSTEM, and I wiped CACHE and DALVIK. I then flashed the proper vendor image, pushing it to the device with adb push, and then adb sideload for the pure nexus ROM. It's currently installing. Then, I will adb sideload the gapps ZIP file. Then I'll reboot and see if it worked
EDIT: It just said "No OS installed"
EDIT 2: Just flashed the ROM again, and it is showing the boot animation. This time I did not do Gapps. I also wiped and formatted everything again. Hope all goes well.
EDIT 3: The ROM booted fine. Glad all is working now
NateDev473 said:
OK, so I formatted DATA and SYSTEM, and I wiped CACHE and DALVIK. I then flashed the proper vendor image, pushing it to the device with adb push, and then adb sideload for the pure nexus ROM. It's currently installing. Then, I will adb sideload the gapps ZIP file. Then I'll reboot and see if it worked
EDIT: It just said "No OS installed"
EDIT 2: Just flashed the ROM again, and it is showing the boot animation. This time I did not do Gapps. I also wiped and formatted everything again. Hope all goes well.
EDIT 3: The ROM booted fine. Glad all is working now
Click to expand...
Click to collapse
Good job You're welcome
neth15 said:
Good job You're welcome
Click to expand...
Click to collapse
So I had flashed the ROM with no Google Apps or anything, just the ROM. But when I add a Google Account, I can't because it says Google Play Services has stopped. I just noticed that the build number is one of a Nexus 6P, and the vendor image is different, the one I manually flashed.
I finally got PN on my PixelXL and just looked at storage and it says the system uses 19.9 GB and I'm wondering if I can clean the alternate slot to free up this space
My 128gb XL on latest update only use 6.79gb system
Sent from my Pixel XL using XDA-Developers Legacy app
You need to flash a factory image which will wipe all data as I had the same issue I believe its the only fix as you need a full wipe to fix and if your going to full wipe your better off to just flash a full factory image and be 100% factory fresh.
M9guy said:
You need to flash a factory image which will wipe all data as I had the same issue I believe its the only fix as you need a full wipe to fix and if your going to full wipe your better off to just flash a full factory image and be 100% factory fresh.
Click to expand...
Click to collapse
I had the same issue. This ^^^ was the only fix.
toknitup420 said:
I had the same issue. This ^^^ was the only fix.
Click to expand...
Click to collapse
Did you try > fastboot format userdata
cam30era said:
Did you try > fastboot format userdata
Click to expand...
Click to collapse
Formatting didn't work for me. I needed fresh system image too
What I did was flash the new Google image then I locked the boot loader then unlocked it again. When I booted up, my storage was back to normal. After that I flashed the custom ROM. This has happened to me often.
Yamalito said:
What I did was flash the new Google image then I locked the boot loader then unlocked it again. When I booted up, my storage was back to normal. After that I flashed the custom ROM. This has happened to me often.
Click to expand...
Click to collapse
If you are on Verizon, DO NOT LOCK BOOTLOADER! Just a friendly reminder.
Yamalito said:
What I did was flash the new Google image then I locked the boot loader then unlocked it again. When I booted up, my storage was back to normal. After that I flashed the custom ROM. This has happened to me often.
Click to expand...
Click to collapse
That's a silly way of wiping data. Factory reset from os or fastboot erase userdata will accomplish the same thing.
tiny4579 said:
That's a silly way of wiping data. Factory reset from os or fastboot erase userdata will accomplish the same thing.
Click to expand...
Click to collapse
If someone is going to format user data they might as well flash the newest factory image. It just makes sense its also preventative maintenance and can keep your phone running at top performance.
M9guy said:
If someone is going to format user data they might as well flash the newest factory image. It just makes sense its also preventative maintenance and can keep your phone running at top performance.
Click to expand...
Click to collapse
Flashing the image is fine. Locking and unlocking the bootloader is unnecessary and should not be done if you're just trying to format. Locking th bootloader while playing around with a messed up system is the perfect storm for a bricked device.
toknitup420 said:
Flashing the image is fine. Locking and unlocking the bootloader is unnecessary and should not be done if you're just trying to format. Locking th bootloader while playing around with a messed up system is the perfect storm for a bricked device.
Click to expand...
Click to collapse
Oh definitely, I never would recommend to relock the bootloader that would be just asking for trouble. I replied to the guy saying to just wipe user data, which if your going to do that it just makes sense to flash the newest factory image and make good use of wiping user data and get back to factory fresh in the process that is just a no brainer.
I agree that locking and unlocking bootloader is silly, it can cause trouble, I'm aware of that, however that was the ONLY thing that worked for me in this case. I tried everything and the storage was still at 19 GB. I'm sorry if the method that worked for me is silly and unorthodox but for me that is all that worked. It's happened to me three times.
So, I'm not new to custom ROMs and I have been a Nexus user for years, but the new dual partition system has me a bit confused and I'm trying to sort of stick to guides to avoid breaking anything.
In all of the Pixel XL specific guides I've read about flashing custom ROMs it says to first wipe the device with TWRP (except internal storage obviously), but wouldn't wiping system wipe it on the active slot and the ROM is going to flashed on the opposite slot, so do I need to switch slots within TWRP, wipe, switch back to the other slot and then flash the ROM?
admiralspeedy said:
So, I'm not new to custom ROMs and I have been a Nexus user for years, but the new dual partition system has me a bit confused, so I'm trying to sort of stick to guides to avoid breaking anything.
In all of the Pixel XL specific guides I've read about flashing custom ROMs, it says to first wipe the device with TWRP (except internal storage obviously), but wouldn't wiping system wipe it on the active slot, but the ROM is going to flashed on the opposite slot, so do I need to switch slots within TWRP, wipe, switch back to the other slot and then flash the ROM?
Click to expand...
Click to collapse
Yes when you wipe from TWRP it wipes what you are currently on. I never wipe system always just been doing factory reset from TWRP and haven't had a problem yet. Last time I wipe system it went okay I just had a heck of a time getting back to the bootloader. I know for the factory reset it wipes data on both slot so maybe the same thing for system
When you boot to twrp the current slot system is wiped.
So if you are on slaot A and wipe for a clean install you have to reboot to the other non active slot. I always hold down vol - so I get right back to bootloader. Than reboot to twrp. Now install rom and twrp and reboot again while holding vol -. Back to twrp and install vendor. Than install gapps if necessary and reboot to system. Once in system reboot into twrp and install su.
mikaole said:
When you boot to twrp the current slot system is wiped.
So if you are on slaot A and wipe for a clean install you have to reboot to the other non active slot. I always hold down vol - so I get right back to bootloader. Than reboot to twrp. Now install rom and twrp and reboot again while holding vol -. Back to twrp and install vendor. Than install gapps if necessary and reboot to system. Once in system reboot into twrp and install su.
Click to expand...
Click to collapse
So after you wipe the system and do a factory reset you boot to the other slot then reboot to recovery and that doesn't ever put you in a loop. I know for a fact the factory reset wipes​ the data and both slots. I quit doing system wipes because I always keep everything on one slot and every time I tried to reboot to recovery or bootloader it would put me into a loop after a system wipe
Never once in a reboot. That's why I hold vol- before I reboot to another slot. Always right away to bootloader. And from there back to twrp.
I had problems multiple times when I didn't wipe system.
BTW if I want to flash dirty I'll do nearly the same.
In TWRP reboot to the non active slot and than install rom twrp and so on.
I really don't know if that's all necessary but never had a problem doing so.
Same thing with flashing factory. I always flash it to both slots.
mikaole said:
Never once in a reboot. That's why I hold vol- before I reboot to another slot. Always right away to bootloader. And from there back to twrp.
I had problems multiple times when I didn't wipe system.
BTW if I want to flash dirty I'll do nearly the same.
In TWRP reboot to the non active slot and than install rom twrp and so on.
I really don't know if that's all necessary but never had a problem doing so.
Same thing with flashing factory. I always flash it to both slots.
Click to expand...
Click to collapse
I'll give it a shot again I was just curious if there was something that I was doing different. someone else was telling me whenever you install a ROM it wipe system anyway for you so you don't even really have to do it maybe next time I'll try it again
Thanks
mikaole said:
When you boot to twrp the current slot system is wiped.
So if you are on slaot A and wipe for a clean install you have to reboot to the other non active slot. I always hold down vol - so I get right back to bootloader. Than reboot to twrp. Now install rom and twrp and reboot again while holding vol -. Back to twrp and install vendor. Than install gapps if necessary and reboot to system. Once in system reboot into twrp and install su.
Click to expand...
Click to collapse
Could you not just change the active slot in TWRP and wipe? Or just change the active slot in TWRP, then tap "Reboot bootloader" and then go back into the recovery if it needs to be restarted for the slot change to take effect?
mac796 said:
So after you wipe the system and do a factory reset you boot to the other slot then reboot to recovery and that doesn't ever put you in a loop. I know for a fact the factory reset wipes​ the data and both slots. I quit doing system wipes because I always keep everything on one slot and every time I tried to reboot to recovery or bootloader it would put me into a loop after a system wipe
Click to expand...
Click to collapse
How do you know that factory reset does both? It doesn't tell you any info when you do it and I'm not convinced it does both at all.
I never tested that.
Don't have time to do so, but will at weekend.
This would make things way easier. Thx for that hint.
Will try with 2 different roms to see if that works.
admiralspeedy said:
How do you know that factory reset does both? It doesn't tell you any info when you do it and I'm not convinced it does both at all.
Click to expand...
Click to collapse
Because when I was running dual slots if I did a wipe on one slot. If I booted to other I had to re setup. They share same data partition so it makes sense
You can also tell when you do it it takes a few seconds if you switch slots and do factory reset again it's already done
mac796 said:
Because when I was running dual slots if I did a wipe on one slot. If I booted to other I had to re setup. They share same data partition so it makes sense
You can also tell when you do it it takes a few seconds if you switch slots and do factory reset again it's already done
Click to expand...
Click to collapse
I'm talking about the system partition, not data. Data is shared between both slots, so obviously wiping it on one is all that is needed.
admiralspeedy said:
I'm talking about the system partition, not data. Data is shared between both slots, so obviously wiping it on one is all that is needed.
Click to expand...
Click to collapse
I said factory reset did both slots I never said system did that's why I asked the other member about it but I've been testing ROMs I have flashed just about every one of them some of them several times and I haven't had to do a system wipe at all so I don't really think it's needed. Only ever caused me problems for me. But obviously I was doing something wrong that's why I asked
mac796 said:
I said factory reset did both slots I never said system did that's why I asked the other member about it but I've been testing ROMs I have flashed just about every one of them some of them several times and I haven't had to do a system wipe at all so I don't really think it's needed. Only ever caused me problems for me. But obviously I was doing something wrong that's why I asked
Click to expand...
Click to collapse
I started this thread by asking about the system partition, so I kind of assumed you were also referring to the system partition.
admiralspeedy said:
I started this thread by asking about the system partition, so I kind of assumed you were also referring to the system partition.
Click to expand...
Click to collapse
Was referring to them both. I don't think it's needed
I have not yet received the phone, but when I do I will boot loader unlock/root. (If I don't intend to stay with Oxygen OS at all, should I even root or just flash the new ROM?) Also, is dirty flashing ok with this? Can I just flash it without wiping?
ZVNexus said:
I have not yet received the phone, but when I do I will boot loader unlock/root. (If I don't intend to stay with Oxygen OS at all, should I even root or just flash the new ROM?) Also, is dirty flashing ok with this? Can I just flash it without wiping?
Click to expand...
Click to collapse
When you unlock the bootloader it will wipe the device so dirty flashing is not in the equation.
If you are flashing CM then you dont need to root first but you will need to root after. (last I knew) Most roms these days dont come with root by default.
zelendel said:
When you unlock the bootloader it will wipe the device so dirty flashing is not in the equation.
If you are flashing CM then you dont need to root first but you will need to root after. (last I knew) Most roms these days dont come with root by default.
Click to expand...
Click to collapse
Yeah it will wipe it, but the system files are still there right? I was watching a video of someone installing a new ROM, and they deleted
Dalvik/ ART Cache
System
Data
Cache
Or am I wrong? Do I not need to wipe all those partitions before flashing? Really sorry for being a bother, fairly new to this.
ZVNexus said:
Yeah it will wipe it, but the system files are still there right? I was watching a video of someone installing a new ROM, and they deleted
Dalvik/ ART Cache
System
Data
Cache
Or am I wrong? Do I not need to wipe all those partitions before flashing? Really sorry for being a bother, fairly new to this.
Click to expand...
Click to collapse
That is what is called a clean flash. (always the best bet when flashing a rom rom and even suggested by all devs. You will be told that you can "dirty" flash (wiping only system and both caches) so your app data and settings stay after the flash but to be honest that is just being lazy as you will have to clean flash before you can post a bug report anyway, so why not do it from the start)
Yes when you unlock the bootloader the system will be fine. What the unlock does is pretty much a factory reset. So make sure to back up any pic, music or what ever.
I have a Mi 9 se and i don't understand how the partitions work on this device (coming from mi 5) If i wipe system or cache or formate data from recovery after first flashing twrp it reboots into fastboot and i need to do a full rom flash again via mi flash tool. Can someone please explain to me what the go is?
Ok so after more attempts. Obviously you need to let it boot the rom before flashing twrp, but wiping system causes twrp not to boot still, can someone explain? thanks.
Thanks
System is where android is installed. If you wipe this it can't boot into android because it's not there so it boots into twrp instead. What are you trying to do?
briandarrel said:
System is where android is installed. If you wipe this it can't boot into android because it's not there so it boots into twrp instead. What are you trying to do?
Click to expand...
Click to collapse
I do realise that but wiping system shouldn't be an issue as the new rom will install the system right? The issue is that wiping system causes it to reboot to fastboot not recovery and i can't get into recovery again without reflashing the rom from mi flash and installing twrp again.
morgs640 said:
I do realise that but wiping system shouldn't be an issue as the new rom will install the system right? The issue is that wiping system causes it to reboot to fastboot not recovery and i can't get into recovery again without reflashing the rom from mi flash and installing twrp again.
Click to expand...
Click to collapse
That is odd, you can can flash the rom without wiping system though I think as the rom will overwrite system anyway
briandarrel said:
That is odd, you can can flash the rom without wiping system though I think as the rom will overwrite system anyway
Click to expand...
Click to collapse
Does it matter if system isn't wiped when moving between a MIUI based rom and an AOSP based rom?
@morgs640, it does: wipe is necessary. Some install-scripts contain a 'wipe system', otherwise you've to do it.