Hi,
the Nexus 5X is my first encrypted phone and I intend to flash the newest MDB08M factory image via fastboot. I wanted to perform a full wipe before flashing the update. My routine for a full wipe to get rid of everything on the phone is:
Wipe Dalvik
wipe cache
factory reset/data
boot into fastboot
fastboot erase boot
fastboot erase system
fastboot erase userdata
fastboot erase cache
fastboot erase webtop
fastboot erase preinstall
fastboot reboot
flash factory image
...
Can I still full wipe my phone this way with encryption?
If you use flash-all.bat script included with factory image it will do it for you. To get list of partitions on your device use "fastboot getvar all".
Thank you for your answer. I did not know that the "flash-all.bat" performs the same routine erasing all partitions. So it is also safe to erase the partitions manually?
Related
I have 2 questions now,
I saw this guide: http://forum.xda-developers.com/showthread.php?t=1626895
But I did understand it but isn't a guide with a Galaxy Nexus Root Toolkit? I saw that in this guide: http://webtrickz.com/guide-to-updat...oid-4-0-4-and-get-future-updates-from-google/
It looks like the same, only is this with a gui, so I won't type things wrong, would this be wrong to use?
And...
If I change to yakju and lock the bootloader ( I just want to have everything stock again after that ), can you see then anywhere if you changed to yakju? So if I send it in for warrenty they won't know it?
Marc. said:
I have 2 questions now,
I saw this guide: http://forum.xda-developers.com/showthread.php?t=1626895
But I did understand it but isn't a guide with a Galaxy Nexus Root Toolkit? I saw that in this guide: http://webtrickz.com/guide-to-updat...oid-4-0-4-and-get-future-updates-from-google/
It looks like the same, only is this with a gui, so I won't type things wrong, would this be wrong to use?
And...
If I change to yakju and lock the bootloader ( I just want to have everything stock again after that ), can you see then anywhere if you changed to yakju? So if I send it in for warrenty they won't know it?
Click to expand...
Click to collapse
1) use the first link you posted. dont use the toolkit. http://forum.xda-developers.com/showthread.php?t=1626895
2) no, they wont be able to really tell anything.
Zepius said:
1) use the first link you posted. dont use the toolkit. http://forum.xda-developers.com/showthread.php?t=1626895
2) no, they wont be able to really tell anything.
Click to expand...
Click to collapse
Why not use the toolkit? It looks much easier.
And do I have to do all the optional things also?
Then it would be this?
1) Make sure your computer recognizes your device by typing: fastboot devices
2) Unlock your bootloader (if you have not already done so): fastboot oem unlock
3) You will see a prompt on your device. This will wipe your entire device (including the /sdcard folder). Accept.
4) Reboot by typing: fastboot reboot-bootloader
9) Flash the system partition: fastboot flash system system.img
10) Flash the data partition: fastboot flash userdata userdata.img Note: this command will wipe your device (including /sdcard), EVEN if your bootloader is already unlocked.
11) Flash the boot partition: fastboot flash boot boot.img
12) Optional (but recommended) -- Flash the recovery partition: fastboot flash recovery recovery.img
13) Erase the cache partition: fastboot erase cache
15) Reboot: fastboot reboot
16) Done! The first boot will likely take quite a bit longer than you are used to, as Android builds the Dalvik cache.
Marc. said:
Why not use the toolkit? It looks much easier.
And do I have to do all the optional things also?
Then it would be this?
1) Make sure your computer recognizes your device by typing: fastboot devices
2) Unlock your bootloader (if you have not already done so): fastboot oem unlock
3) You will see a prompt on your device. This will wipe your entire device (including the /sdcard folder). Accept.
4) Reboot by typing: fastboot reboot-bootloader
9) Flash the system partition: fastboot flash system system.img
10) Flash the data partition: fastboot flash userdata userdata.img Note: this command will wipe your device (including /sdcard), EVEN if your bootloader is already unlocked.
11) Flash the boot partition: fastboot flash boot boot.img
12) Optional (but recommended) -- Flash the recovery partition: fastboot flash recovery recovery.img
13) Erase the cache partition: fastboot erase cache
15) Reboot: fastboot reboot
16) Done! The first boot will likely take quite a bit longer than you are used to, as Android builds the Dalvik cache.
Click to expand...
Click to collapse
if something happens in the middle of you doing it the way in the link i mentioned, its easier to figure out how to fix items when you're on a certain step.
the toolkit is easier, but if something messes up, its hard to tell where since you have no idea what it is doing
the only other step is once everything is booted back up on yakju and is working properly, go back to fastboot and relock the bootloader with fastboot oem lock
So you say these steps will be right?
1) Make sure your computer recognizes your device by typing: fastboot devices
2) Unlock your bootloader (if you have not already done so): fastboot oem unlock
3) You will see a prompt on your device. This will wipe your entire device (including the /sdcard folder). Accept.
4) Reboot by typing: fastboot reboot-bootloader
5) Flash the system partition: fastboot flash system system.img
6) Flash the data partition: fastboot flash userdata userdata.img Note: this command will wipe your device (including /sdcard), EVEN if your bootloader is already unlocked.
7) Flash the boot partition: fastboot flash boot boot.img
8) Optional (but recommended) -- Flash the recovery partition: fastboot flash recovery recovery.img
9) Erase the cache partition: fastboot erase cache
10) Reboot: fastboot reboot
11) Done! The first boot will likely take quite a bit longer than you are used to, as Android builds the Dalvik cache.
12) Lock bootloader again with: fastboot oem lock
And how could I see when its finished flashing for example system.img?
And this would work on doesn't matter what firmware you're on?
Marc. said:
I have 2 questions now,
I saw this guide: http://forum.xda-developers.com/showthread.php?t=1626895
But I did understand it but isn't a guide with a Galaxy Nexus Root Toolkit? I saw that in this guide: http://webtrickz.com/guide-to-updat...oid-4-0-4-and-get-future-updates-from-google/
It looks like the same, only is this with a gui, so I won't type things wrong, would this be wrong to use?
And...
If I change to yakju and lock the bootloader ( I just want to have everything stock again after that ), can you see then anywhere if you changed to yakju? So if I send it in for warrenty they won't know it?
Click to expand...
Click to collapse
Yes, if they check build.prop (unlikely that they will if you relock bootloader), they will be able to see the yakju fingerprint.
Marc. said:
So you say these steps will be right?
1) Make sure your computer recognizes your device by typing: fastboot devices
2) Unlock your bootloader (if you have not already done so): fastboot oem unlock
3) You will see a prompt on your device. This will wipe your entire device (including the /sdcard folder). Accept.
4) Reboot by typing: fastboot reboot-bootloader
5) Flash the system partition: fastboot flash system system.img
6) Flash the data partition: fastboot flash userdata userdata.img Note: this command will wipe your device (including /sdcard), EVEN if your bootloader is already unlocked.
7) Flash the boot partition: fastboot flash boot boot.img
8) Optional (but recommended) -- Flash the recovery partition: fastboot flash recovery recovery.img
9) Erase the cache partition: fastboot erase cache
10) Reboot: fastboot reboot
11) Done! The first boot will likely take quite a bit longer than you are used to, as Android builds the Dalvik cache.
12) Lock bootloader again with: fastboot oem lock
And how could I see when its finished flashing for example system.img?
And this would work on doesn't matter what firmware you're on?
Click to expand...
Click to collapse
Why don't you download yakju factory image from Google? It has a bash script that can flash everything for you, in the right order. If you edit flash-all.sh, you'll see the fastboot commands it runs. That's the order you need to run them.
Sent from my i9250
I did install Blues Marshmallow GPE rom that i found here.I installed it without root/s-off.Now i want to install cyanogenmod 13 but when i try to enter to recovery mode it says Error with an Android logo.Nothing else,just "Error." and can't enter to twrp recovery mode.How do i fix this?
Try fastboot erase cache, and fastboot flash TWRP again.
redpoint73 said:
Try fastboot erase cache, and fastboot flash TWRP again.
Click to expand...
Click to collapse
I'm not that good at this kind of stuff.Is there any guide videos of how to do erase cache and flash twrp? i don't remember how did i do it.
burakby35 said:
I'm not that good at this kind of stuff.Is there any guide videos of how to do erase cache and flash twrp? i don't remember how did i do it.
Click to expand...
Click to collapse
Instructions on how to flash TWRP via fastboot are on the TWRP page: https://twrp.me/devices/htconem8gsm.html
Before you flash TWRP, erasing cache (which can often clear up problems with TWRP not installing or booting properly), is a simple fastboot command: fastboot erase cache
Hello there,
I own a N5X with 32 GB of storage. After some failed flashing I reflashed stock, which works fine except that only 10.55 GB of storage are being shown in the settings.
I do not have any modifications at the moment other than TWRP and an unlocked bootloader.
I did some research and found that erasing and reflashing all these Android compenents should fix it (this example is for the N5):
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
flash boot boot.img
...which it didn't.
Does anyone have a solution? Is there any way to extend the partitions, maybe without wiping everything?
Thank you in advance
Tuxcraft32 said:
Hello there,
I own a N5X with 32 GB of storage. After some failed flashing I reflashed stock, which works fine except that only 10.55 GB of storage are being shown in the settings.
I do not have any modifications at the moment other than TWRP and an unlocked bootloader.
I did some research and found that erasing and reflashing all these Android compenents should fix it (this example is for the N5):
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
flash boot boot.img
...which it didn't.
Does anyone have a solution? Is there any way to extend the partitions, maybe without wiping everything?
Thank you in advance
Click to expand...
Click to collapse
None of those would fix the GPT partition table.
Try flashing the beta Android N OTA. That has fixed the GPT table for people who use 32GB TOT file on 16GB so perhaps it'll do the same for your reverse situation.
try fastboot format userdata. This will wipe everything tho. That should get you back to 32gb
Im not sure if there is a way to do it without wiping. Maybe flash twrp recovery and use the advanced menu to extend partition.
This worked for me:
Boot into TWRP
Choose "Wipe" -> "Advanced Wipe"
Select your "data" partition and choose "Repair or Change File System"
Select "Resize File System" - it should automatically expand your storage to fill the empty space.
Tuxcraft32 said:
Code:
fastboot flash userdata userdata.img
...which it didn't.
Does anyone have a solution? Is there any way to extend the partitions, maybe without wiping everything?
Thank you in advance
Click to expand...
Click to collapse
Your internal storage was downsized to 16 GB because of this command. The userdata.img formats the userdata partition to the base 5X storage size of 16 GB. Do not flash the userdata partition since you have a 32 GB phone.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Your internal storage was downsized to 16 GB because of this command. The userdata.img formats the userdata partition to the base 5X storage size of 16 GB. Do not flash the userdata partition since you have a 32 GB phone.
Click to expand...
Click to collapse
If that is what caused it (and the partition table is still fine), then he can probably do
fastboot erase userdata
fastboot format userdata
and it should be back to normal.
just do dalvik and cache reset from recovery
First, thank you for all of your replies <3.
TheBurgh said:
This worked for me:
Boot into TWRP
Choose "Wipe" -> "Advanced Wipe"
Select your "data" partition and choose "Repair or Change File System"
Select "Resize File System" - it should automatically expand your storage to fill the empty space.
Click to expand...
Click to collapse
Worked for me as well! I now have 24.89GB free (which is normal, isn't it?). Thanks a lot.
To you:
SlimSnoopOS said:
Your internal storage was downsized to 16 GB because of this command. The userdata.img formats the userdata partition to the base 5X storage size of 16 GB. Do not flash the userdata partition since you have a 32 GB phone.
Click to expand...
Click to collapse
and you:
beady_uk said:
try fastboot format userdata. This will wipe everything tho. That should get you back to 32gb
Click to expand...
Click to collapse
as well as you:
sfhub said:
If that is what caused it (and the partition table is still fine), then he can probably do
fastboot erase userdata
fastboot format userdata
and it should be back to normal.
Click to expand...
Click to collapse
– I think this is what I got wrong. The flash-all.sh reported an error and stopped after flashing the first couple of components so I flashed all the components manually, including the userdata.img. I will stay away from that next time.
sfhub said:
None of those would fix the GPT partition table.
Try flashing the beta Android N OTA. That has fixed the GPT table for people who use 32GB TOT file on 16GB so perhaps it'll do the same for your reverse situation.
Click to expand...
Click to collapse
Thank you for the suggestion, luckily this was not necessary.
ikyeye said:
just do dalvik and cache reset from recovery
Click to expand...
Click to collapse
I did that, with no effect.
TheBurgh said:
This worked for me:
Boot into TWRP
Choose "Wipe" -> "Advanced Wipe"
Select your "data" partition and choose "Repair or Change File System"
Select "Resize File System" - it should automatically expand your storage to fill the empty space.
Click to expand...
Click to collapse
THANK YOU! I'm glad I didn't listen to the advice to factory reset, etc. This fixed the size without losing anything.
All,
I am not a noob by any means, but when I attempted to manually flash the img files via fastboot for the latest N build from the factory images coming from the last 6.0.1 build I get stuck on the Google logo. I checked the commands and re-flashed again and the same result happened ( i did flash radios and BL ) .
I even tried to format data ( i had backed everything up ) , still no go and stuck at google logo still. I could access BL and able to access TWRP.
I got frustrated and flashed the 6.0.1 images including BL and radio via fastboot and booted up just fine. I then rooted, installed flashfire and used the OTA and Android N installed just fine.
Does anyone have any idea what could be causing this. I am currently on N, but wanted to do a clean install .
Thanks in Advance
Did you flash vendor.img?
Why don't you list the exact commands you used to flash, then people can comment.
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash boot boot.img
fastboot erase cache
fastboot flash cache cache.img
fastboot flash recovery twrp-3.0.2-2-bullhead.img
fastboot reboot-bootloader
fastboot flash recovery twrp-3.0.2-2-bullhead.img
Flashing mtc20k works successfully
Using the same commands to flashing npf10c results in stuck the google logo
In order for me to even get on N I have to me on 6.0.1 then either use the bullhead-ota-npf10c-d1785fea.zip on the root of the SD card and use flashfire OR use the following command from stock recovery
adb sideload bullhead-ota-npf10c-d1785fea.zip
The later is what I did recently, but both will work to get to N.
So why can I not simply flash the factory images like for 6.0.1?
carm01 said:
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash boot boot.img
fastboot erase cache
fastboot flash cache cache.img
fastboot flash recovery twrp-3.0.2-2-bullhead.img
fastboot reboot-bootloader
fastboot flash recovery twrp-3.0.2-2-bullhead.img
Flashing mtc20k works successfully
Using the same commands to flashing npf10c results in stuck the google logo
In order for me to even get on N I have to me on 6.0.1 then either use the bullhead-ota-npf10c-d1785fea.zip on the root of the SD card and use flashfire OR use the following command from stock recovery
adb sideload bullhead-ota-npf10c-d1785fea.zip
The later is what I did recently, but both will work to get to N.
So why can I not simply flash the factory images like for 6.0.1?
Click to expand...
Click to collapse
What happens when you flash a Nougat factory image that is NOT a developer preview? Try flashing NRD91N from here:
https://developers.google.com/android/images?hl=en
Sent from my Nexus 5X using Tapatalk
carm01 said:
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash boot boot.img
fastboot erase cache
fastboot flash cache cache.img
fastboot flash recovery twrp-3.0.2-2-bullhead.img
fastboot reboot-bootloader
fastboot flash recovery twrp-3.0.2-2-bullhead.img
Flashing mtc20k works successfully
Using the same commands to flashing npf10c results in stuck the google logo
In order for me to even get on N I have to me on 6.0.1 then either use the bullhead-ota-npf10c-d1785fea.zip on the root of the SD card and use flashfire OR use the following command from stock recovery
adb sideload bullhead-ota-npf10c-d1785fea.zip
The later is what I did recently, but both will work to get to N.
So why can I not simply flash the factory images like for 6.0.1?
Click to expand...
Click to collapse
I don't usually flash cache or user.
Try this instead and see if it works.
Instead of flashing cache.img
fastboot erase cache
fastboot format cache
(if you want to reset user)
fastboot erase userdata
fastboot format userdata
sfhub said:
I don't usually flash cache or user.
Try this instead and see if it works.
Instead of flashing cache.img
fastboot erase cache
fastboot format cache
(if you want to reset user)
fastboot erase userdata
fastboot format userdata
Click to expand...
Click to collapse
SlimSnoopOS said:
What happens when you flash a Nougat factory image that is NOT a developer preview? Try flashing NRD91N from here:
https://developers.google.com/android/images?hl=en
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I have tried fastboot erase userdata and fastboot format userdata and fastboot erase cache
fastboot format cache and that never worked.
I tried that factory image before and resulted in the same, however, I will at sometime attempt to do the final of 7.1.1 once it is available sometime in December 2016 and hopefully will resolve the issue.
I will stay on DP1 right now as i find the battery extremely excellent, the Visual VM is back now, and i notice some notifications are coming through better than in 7.0. (I read an article earlier today about notifications and the pixel not coming through)
Thanks in Advance for the people that did come through so far and wanted to thank you for your input on the matter and if i don't have a pixel by December I will try this out.
Hello everyone.
I'm trying to install Oreo rom but I need to decrypt my data partition. (The "Wipe Data" with TWRP does not work)
I tried with the rom stock. (Reset via the menu)
The phone restarts it is already encrypted ...
Can someone give me some advice?
Go into twrp
Wipe data
Select format data (option on the right hand side)
Reboot to twrp
Wipe data
Advanced wipe (option on the left hand side)
Wipe system data cache delvik/art cache
Now flash rom gapps & magisk
HEy thank's but, I still have this problem.
Can not Format Data.
I am under twrp-3.2.1-0-cedric.img
(same as previous versions)
Go into twrp // ok
Wipe data // ok
Select format data (option on the right hand side) // Fail
SuperUtilisateur said:
HEy thank's but, I still have this problem.
Can not Format Data.
I am under twrp-3.2.1-0-cedric.img
(same as previous versions)
Go into twrp // ok
Wipe data // ok
Select format data (option on the right hand side) // Fail
Click to expand...
Click to collapse
Did you decrypt data in twrp first - when you boot into twrp it will pop up with enter your password to decrypt data
If you don't decrypt data in twrp it won't be able to mount it to format it
The other option is flashing stock rom via fastboot without flashing the bootloader or partition parts & erasing user data then do a full boot
Once you have downloaded firmware these are the commands
Code:
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
Ignore some parts that may not be in the firmware that will produce an error if ran
Thank you for your reply
--
Edit : Here is the solution:
It is necessary to restart Recovery to "Mount Data".
Thank you for your help