I did the update to 4.0.4 and my phone is running like crap; laggy, radio doesn't perform well, and occasional crashes.
That said, I'm thinking it would be best to wipe it clean and start again. I was curious if doing the boot loader lock or unlock just wipes data that's been added, or if it would reset the entire phone to 4.0.1. I'm assuming it just wipes the data, but wanted to know for sure.
On a related note, would I be better off downloading the 4.0.4 image from google and just reflashing the phone with the Galaxy Nexus Toolkit if I'm seeing performance issues?
If you want a reinstall, just re-flash the images.
Locking then unlocking the bootloader wipes the entire device, and you have to reinstall the OS. Might as well just skip that step and completely re-flash the images. Using the bootloader is just an unnecessary step. Re-flashing the images will accomplish the same thing of reloading the OS from scratch.
Everything.
Sent from my Galaxy Nexus using XDA
martonikaj said:
If you want a reinstall, just re-flash the images.
Locking then unlocking the bootloader wipes the entire device, and you have to reinstall the OS. Might as well just skip that step and completely re-flash the images. Using the bootloader is just an unnecessary step. Re-flashing the images will accomplish the same thing of reloading the OS from scratch.
Click to expand...
Click to collapse
Really??? I haven't heard anything about having to reinstall the entire os from relocking and unlocking the boot loader...
I'll probably just reflashing the 4.0.4 build on the google nexus builds page
pr3cision said:
Everything.
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
So does that mean it would go back to 4.0.1 and lose the 4.0.2 and 4.0.4 patches?
It does not wipe the is partition. When ur firmware is updated its updated. It won't revert back unless u flash a different image or stock ruu or image. It wipes all the data. Allll the data, not the os. You can't delete the os.
Sent from my Galaxy Nexus using XDA
ChazzMichaelMichaels said:
Really??? I haven't heard anything about having to reinstall the entire os from relocking and unlocking the boot loader...
I'll probably just reflashing the 4.0.4 build on the google nexus builds page
Click to expand...
Click to collapse
What I'm saying is it won't wipe the update. If you want to go back to 4.0.1 or 4.0.2 you have to flash images. Locking then Unlocking won't just put you back to 4.0.1. Sorry if it was a little confusing.
Unlocking the bootloader wipes the user data partition only, which includes /sdcard. It does not wipe the system partition where the OS resides.
Sent from my Galaxy Nexus using Tapatalk
Related
Hey Guys..Verizon GN here. I was curious if someone who is rooted with a custom ROM goes to the Backup and Restore menu and clicks Factory Data Reset, what happens?I'm assuming it wouldnt go back to a factory rom.
you would assume incorrectly. it wipes user data, but does not restore stock images.
Zepius said:
you would assume incorrectly. it wipes user data, but does not restore stock images.
Click to expand...
Click to collapse
I said "wouldn't" assume
Sent from my Galaxy Nexus using XDA
it just factory resets.... deleting all logged in saved info/apps/etc.
Is it beneficial to flash the factory image if you have flashed lots of ROMs recently?
I was thinking of doing this when 4.2 is released but was curious if it would actually make a difference.
Nah.
Just factory reset + clear cache in cwm will do.
Mach3.2 said:
Nah.
Just factory reset + clear cache in cwm will do.
Click to expand...
Click to collapse
However, a true fresh start would be reflashing factory images, custom recovery, etc
bk201doesntexist said:
However, a true fresh start would be reflashing factory images, custom recovery, etc
Click to expand...
Click to collapse
Actually, flashing a stock image doesn't take 5 minutes lol.
Mach3.2 said:
Actually, flashing a stock image doesn't take 5 minutes lol.
Click to expand...
Click to collapse
So we both agree. OP, start fresh from factory images.
Sent from my i9250
Thanks for the replies. Backing up and restoring the SD card after flashing the factory image shouldn't cause any problems either correct? I don't want to lose all my pictures and other files.
KnappyRoot said:
Thanks for the replies. Backing up and restoring the SD card after flashing the factory image shouldn't cause any problems either correct? I don't want to lose all my pictures and other files.
Click to expand...
Click to collapse
Back up everything you need on your computer. Re-lock & then unlock the bootloader, that will wipe everything clean. Then follow procedure to flash factory image, look for efrant's post in general.
Vangelis13 said:
Back up everything you need on your computer. Re-lock & then unlock the bootloader, that will wipe everything clean. Then follow procedure to flash factory image, look for efrant's post in general.
Click to expand...
Click to collapse
no need to relock/unlock, either pass '-w' to have fastboot wipe userdata partition or just 'fastboot erase userdata'.
userdata is at /data, i think.
I use the fastbook -w update command and it deletes all information.
Sent from my Galaxy Nexus using xda app-developers app
Well I flashed 4.0.4 factory image and restored my SD card. When I try to move files on the SD card I keep getting message that file can't be moved. Am I missing a check box somewhere?
My next idea was to re-flash factory image, root, then manually restore files from my computer. Any other easier suggestions?
Sent from my Galaxy Nexus using xda app-developers app
Howdy y'all!
I'm currently running a 4.1.1 ROM, and would like to get on to MMuzzy's 4.2, but there are a ton of things I think I need to flash and want to make sure I get the order right. Your help will be much appreciated!
I am already using the latest version of TWRP.
I would like to flash the latest JB bootloader, and latest JB radios, but have never flashed either. Should I do these before flashing the ROM, or after? Should I do these before formatting cache? Should I format system or factory reset before flashing these, too?
I am planning to do factory reset, format cache and dalvik before flashing ROM, gapps and kernel. Do I need to do anything else to prep for flashing the ROM? Also, is it okay to flash all three at once, or should I do rom and gapps, let everything boot and restore from market, and only then flash kernel?
My main concern is the differences in file system between 4.1 and 4.2. I'm aware of the /0 subdirectory thing already, but I'd there anything else?
Thanks much!
Jamie
I wouldn't bother with the bootloader, but if you insist then you can flash the bootloader and the radios before or after. Doesn't matter.. Other than that, you do them ROM, gapps, kernel and I've done all three at once. Mmuzzy's is a good ROM. Enjoy.
First make a backup in TWRP
Factory reset
Wipe both caches
Install ROM, gapps, then kernel and reboot. (All at the sometime in that order)
I have heard its better to flash the kernel with the new ROM so just do it all in one flash.
Set everything up and let your phone sit for 15 minutes untouched and go for it.
Sent from my Galaxy Nexus using xda app-developers app
jrbedford said:
My main concern is the differences in file system tree between 4.1 and 4.2. I'm aware of the /0 subdirectory thing already, but I'd there anything else?
Thanks much!
Jamie
Click to expand...
Click to collapse
Just a small correction; file system change would mean switching from ext4 to f2fs, for example. That's not the case.
MartianCeo said:
First make a backup in TWRP
Factory reset
Wipe both caches
Install ROM, gapps, then kernel and reboot. (All at the sometime in that order)
I have heard its better to flash the kernel with the new ROM so just do it all in one flash.
Set everything up and let your phone sit for 15 minutes untouched and go for it.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Watch out with restoring backups. Don't restore app/system data. OP is switching major versions.
sent from my Google Galaxy Nexus
currently running pure nexus rom 6.0.1 on my n5x and want to upgrade to android n
any way to flash android n update without any data or app loss?
ps: n5x rooted with twrp recovery
Sent from my Nexus 5X
Download the N factory image and extract it. Use fastboot to first flash the bootloader. Then re-boot into the bootloader. Then flash the boot, system, radio, and vendor images. It's always good to back everything up first, just in case. You might have to uninstall then re-install some apps. You'll have to re-flash twrp and SU.
Sent from my Nexus 9 using XDA-Developers mobile app
but i guess
flashing factory image will wipe my internal storage too?
if not then how?
Sent from my Nexus 5X
gtsfreak said:
but i guess
flashing factory image will wipe my internal storage too?
if not then how?
Click to expand...
Click to collapse
He literally just explained step by step how to do it. You can do it this way or use ADB sideload like I did. Some apps needed to be reinstalled, but all of my internal storage was kept.
Okay thanks
Sent from my Nexus 5X
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.