Related
For those who flashed the 1.29 RUU and are boot looping and a wipe isn't fixing it:
Go into the recovery.
Go to wipe.
Go to advanced.
Tell it to reformat your cache partition.
I've only tested it on one phone but it may be that the RUU is corrupting the cache partition before failing and thus leaving you with a boot looping phone.
Or, since you're already in fastboot...
Code:
fastboot erase cache
CNexus said:
Or, since you're already in fastboot...
Code:
fastboot erase cache
Click to expand...
Click to collapse
Yep, if you have access to a computer, you can also do that as well.
I am trying to back out everything I've done to the phone and start fresh with 5.1. I had rooted, decrypted, and installed TWRP. To undo this, I did a factory reset, downloaded the shamu-lrx22c factory image from google, and used adb/fastboot to put it all back the way I found it. These are the commands I used :
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
fastboot flash radio radio-shamu-d4.0-9625-02.55.04.img
fastboot reboot-bootloader
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
It appeared to all work. Now when I try to get back into recovery, the phone sits at the android with the red triangle and !. The bootloader logs state "Mismatched partition size (recovery)."
Did I do a bad thing somewhere along the way? Thanks in advance.
Try flashing the recovery again. I think if I was you I would also fastboot -w to format the userdata and cache since you already did a factory reset or use google's images by using "fastboot flash userdata userdata.img", "fastboot erase cache" and then "fastboot flash cache cache.img".
Also, check the md5 of the image you downloaded to make sure it was not corrupt.
Evo_Shift said:
Try flashing the recovery again. I think if I was you I would also fastboot -w to format the userdata and cache since you already did a factory reset or use google's images by using "fastboot flash userdata userdata.img", "fastboot erase cache" and then "fastboot flash cache cache.img".
Also, check the md5 of the image you downloaded to make sure it was not corrupt.
Click to expand...
Click to collapse
I used fastboot -w to format the userdata/cache. And I also tried the three fastboot commands you listed. They all seem to work, but the reflashing of the recovery still throws the same error.
MD5 checksum of the whole zip is the same. I re-extracted the recovery.img file just to be sure and it still throws the same error.
Kramit said:
when I try to get back into recovery, the phone sits at the android with the red triangle and !.
Click to expand...
Click to collapse
Thats normal though isn't it? With Stock recovery you have to press Volume up and power to get into the recovery menu from that screen
rootSU said:
Thats normal though isn't it? With Stock recovery you have to press Volume up and power to get into the recovery menu from that screen
Click to expand...
Click to collapse
Sadly, that doesn't do anything. Pressed repeatedly, held down for a while, nothing. up until the point where it reboots from the power button being held long enough.
rootSU said:
Thats normal though isn't it? With Stock recovery you have to press Volume up and power to get into the recovery menu from that screen
Click to expand...
Click to collapse
yes, thats norml
cmh714 said:
yes, thats norml
Click to expand...
Click to collapse
Hmm. And if it doesn't work?
Kramit said:
I am trying to back out everything I've done to the phone and start fresh with 5.1. I had rooted, decrypted, and installed TWRP. To undo this, I did a factory reset, downloaded the shamu-lrx22c factory image from google, and used adb/fastboot to put it all back the way I found it. These are the commands I used :
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
fastboot flash radio radio-shamu-d4.0-9625-02.55.04.img
fastboot reboot-bootloader
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
It appeared to all work. Now when I try to get back into recovery, the phone sits at the android with the red triangle and !. The bootloader logs state "Mismatched partition size (recovery)."
Did I do a bad thing somewhere along the way? Thanks in advance.
Click to expand...
Click to collapse
I have the same problem here but maybe i have found a solution for it:
what i did was i left the 5.1 bootloader.img and took all the other stuff from a 5.0 factory image such as: radio.img, system.img..... fastbooted everything and i was with a 5.0 LP stock out of the box, then i have rooted it, installed twrp with f2fs support and voila i'm now good to go
hope this will help you out
Kramit said:
Sadly, that doesn't do anything. Pressed repeatedly, held down for a while, nothing. up until the point where it reboots from the power button being held long enough.
Click to expand...
Click to collapse
When you see the android with the red triangle and !, you need to hold the power button, and while you are holding it down, press volume up. Pushing them both together, or one after the other, or holding them down together or whatever else won't work.
Sent from my Nexus 6 using Tapatalk
I would bring my Nexus 6 to the stock...to have a phone completely clean, can I do (with the toolkit) the various erase boot, cache, recovery, system, userdata? And then flash, even with the tool, the stock ROM? I would not make mistakes
hollywood_jack said:
I would bring my Nexus 6 to the stock...to have a phone completely clean, can I do (with the toolkit) the various erase boot, cache, recovery, system, userdata? And then flash, even with the tool, the stock ROM? I would not make mistakes
Click to expand...
Click to collapse
Or do it manualy with adb, look here as a guide http://forum.xda-developers.com/nexus-6/general/guide-properly-prepare-nexus-6-resale-t3104504 method 2. Toolkits will always bite you in the ass at some point in the future
gee2012 said:
Toolkits will always bite you in the ass at some point in the future
Click to expand...
Click to collapse
Sorry but I not have understood this
hollywood_jack said:
Sorry but I not have understood this
Click to expand...
Click to collapse
If you use automated software to flash or alter the OS or parts of it you don`t understand whats going on and if something goes wrong you will not be able to solve the issue because you don`t know what went wrong
gee2012 said:
If you use automated software to flash or alter the OS or parts of it you don`t understand whats going on and if something goes wrong you will not be able to solve the issue because you don`t know what went wrong
Click to expand...
Click to collapse
Ok :good:
But in this page http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008 I read only erase cache...can I do, in the same way, all erase (boot, cache, recovery, system, userdata)?
hollywood_jack said:
Ok :good:
But in this page http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008 I read only erase cache...can I do, in the same way, all erase (boot, cache, recovery, system, userdata)?
Click to expand...
Click to collapse
Some more info please: do you have stock rom, recovery, kernel and are you rooted?
If the answer is yes to the above just:
- fastboot erase system
- fastboot flash system system.img
- data factory reset in recovery
- reboot and you`re done.
gee2012 said:
Some more info please: do you have stock rom, recovery, kernel and are you rooted?
If the answer is yes to the above just:
- fastboot erase system
- fastboot flash system system.img
- data factory reset in recovery
- reboot and you`re done.
Click to expand...
Click to collapse
I have stock rom with TWRP recovery...then I have multirom app with (I think) modified kernel
hollywood_jack said:
I have stock rom with TWRP recovery...then I have multirom app with (I think) modified kernel
Click to expand...
Click to collapse
Then after you flash system.img (look in my previous post)you also flash boot.img and recovery.img
gee2012 said:
Then after you flash system.img (look in my previous post)you also flash boot.img and recovery.img
Click to expand...
Click to collapse
Thanks gee2012...you are very exhaustive :good:
Only another little question: can I erase cache and userdata? Or is better to use the format command? What is the difference between format and erase?
hollywood_jack said:
Thanks gee2012...you are very exhaustive :good:
Only another little question: can I erase cache and userdata? Or is better to use the format command? What is the difference between format and erase?
Click to expand...
Click to collapse
I always use the erase command, but i guess format will work too. The outcome should be the same And if you flash userdata it will erase userdata before the flash automaticaly, so no need to erase/format.
gee2012 said:
I always use the erase command, but i guess format will work too. The outcome should be the same And if you flash userdata it will erase userdata before the flash automaticaly, so no need to erase/format.
Click to expand...
Click to collapse
Sorry my friend for a new question but I have many doubts about the factory image flash, I'm a newbie
I would flash also the original bootloader and now my question is this: after the flash the original bootloader and after reboot-bootloader (http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008 method 2) I have a locked bootloader or unlocked bootloader? If the bootloader is locked might I end up in a boot loop with the following flash (always method 2)?
hollywood_jack said:
Sorry my friend for a new question but I have many doubts about the factory image flash, I'm a newbie
I would flash also the original bootloader and now my question is this: after the flash the original bootloader and after reboot-bootloader (http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008 method 2) I have a locked bootloader or unlocked bootloader? If the bootloader is locked might I end up in a boot loop?
Click to expand...
Click to collapse
First you have to unlock the bootloader and then you can flash the factory image in parts (system, boot, recovery, cache).
Fastboot command in cmd and bootloader/fastboot mode: fastboot oem unlock. Only flash the bootloader and radio if you don`t have the correct BL/radio installed, if you have there os no need to flash it again.
gee2012 said:
First you have to unlock the bootloader and then you can flash the factory image in parts (system, boot, recovery, cache).
Fastboot command in cmd and bootloader/fastboot mode: fastboot oem unlock. Only flash the bootloader and radio if you don`t have the correct BL/radio installed, if you have there os no need to flash it again.
Click to expand...
Click to collapse
Ok, all clear but if I need to flash also the bootloader what would be the correct steps?
hollywood_jack said:
Ok, all clear but if I need to flash also the bootloader what would be the correct steps?
Click to expand...
Click to collapse
Extract the rom and flash the bootloader first (fastboot flash bootloader namebootloader.img) and fastboot reboot-bootloader, then the radio and also reboot and then the rest in one go. Good luck an if you have doubts/problems post it here. Plenty of helpfull members around
But after flash and reboot bootloader can I flash the other factory image parts? The original bootloader that I just flashed not is locked?
Inviato dal mio Nexus 6 utilizzando Tapatalk
hollywood_jack said:
But after flash and reboot bootloader can I flash the other factory image parts? The original bootloader that I just flashed not is locked?
Inviato dal mio Nexus 6 utilizzando Tapatalk
Click to expand...
Click to collapse
Once you unlock the BL it stays unlocked unless you lock it manualy. Even if you flash a new bootloader.
Thanks my friend...thanks alot
with my Nexus 6
hollywood_jack said:
Thanks my friend...thanks alot
with my Nexus 6
Click to expand...
Click to collapse
Good luck, its only a bit stressfull the first time
gee2012 said:
Good luck, its only a bit stressfull the first time
Click to expand...
Click to collapse
Can I flash directly a no force encryption boot.img like this http://forum.xda-developers.com/showpost.php?p=61203588&postcount=913?
Then
- fastboot erase system
- fastboot flash system system.img
- fastboot flash userdata userdata.img
- fastboot erase boot
- fastboot flash boot "no force encryption boot".img
- fastboot erase recovery (optional if I want the original recovery)
- fastboot flash recovery recovery.img (optional if I want the original recovery)
- fastboot erase cache
- fastboot flash cache cache.img
- data factory reset in recovery (it's necessary?)
- reboot system.
Then...root with WugFresh toolkit...
It's correct?
hollywood_jack said:
Can I flash directly a no force encryption boot.img like this http://forum.xda-developers.com/showpost.php?p=61203588&postcount=913?
Then
- fastboot erase system
- fastboot flash system system.img
- fastboot flash userdata userdata.img
- fastboot erase boot
- fastboot flash boot "no force encryption boot".img
- fastboot erase recovery (optional if I want the original recovery)
- fastboot flash recovery recovery.img (optional if I want the original recovery)
- fastboot erase cache
- fastboot flash cache cache.img
- data factory reset in recovery (it's necessary?)
- reboot system.
Then...root with WugFresh toolkit...
It's correct?
Click to expand...
Click to collapse
- You don`t have to erase boot and recovery
- Yes you can flash a non encryped kernel but you`ll have to factory reset after you flashed and the N6 is booting or your storage will say its 32GB.
- Rooting is easiest by placing the latest 2.8.7.1 TWRP recovery in the sdk-platform-tools folder, reboot in bootloadermode and fastboot boot namerecovery.img and boot up and flash the latest superSU.zip (Beta 2.49 afaik) or use a toolkit if want to.
After following the directions to the T i restarted my phone and now the only thing that is happening is my moto x blinks the android figure. Is my phone bricked? i can get into recovery. How do it fix my phone? Thanks ahead!!!
D.A.N. said:
After following the directions to the T i restarted my phone and now the only thing that is happening is my moto x blinks the android figure. Is my phone bricked? i can get into recovery. How do it fix my phone? Thanks ahead!!!
Click to expand...
Click to collapse
You need to be more specific. Hopefully you didn't downgrade the bootloader or partition table. Can you put the phone in bootloader mode and type this?
fastboot getvar all
You need to find the latest stock firmware for your variant and region, and flash it like this (example from my variant):
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.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 system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
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
Hello, I just tried that and it's stuck at boot loader unlocked screen. Thank you for the advice. Am I able to get past this screen or is it bricked?
D.A.N. said:
Hello, I just tried that and it's stuck at boot loader unlocked screen. Thank you for the advice. Am I able to get past this screen or is it bricked?
Click to expand...
Click to collapse
I don't think it's bricked, it wouldn't show the bootloader unlocked screen. Can you power it off by long pressing the power button, then getiing into bootloader by pressing power and volume down at the same time. then do:
fastboot getvar all
Gus Ghanem said:
I don't think it's bricked, it wouldn't show the bootloader unlocked screen. Can you power it off by long pressing the power button, then getiing into bootloader by pressing power and volume down at the same time. then do:
fastboot getvar all
Click to expand...
Click to collapse
Yes, i type that in and i get the long list of options. Once i restart the phone I get the blinking android guy again.
D.A.N. said:
Yes, i type that in and i get the long list of options. Once i restart the phone I get the blinking android guy again.
Click to expand...
Click to collapse
Can you flash TWRP 3.1.1-0 and boot into it.
fastboot flash recovery twrp-3.1.1-0-victara.img
If you can, then it's not bricked.
https://dl.twrp.me/victara/
Gus Ghanem said:
Can you flash TWRP 3.1.1-0 and boot into it.
fastboot flash recovery twrp-3.1.1-0-victara.img
If you can, then it's not bricked.
https://dl.twrp.me/victara/
Click to expand...
Click to collapse
I just did that and it worked, but an error at the bottom says "mismatched partition size (recovery)
it does go into recovery now. Tried to install rom and it reboots over and over into recovery. Weird.
D.A.N. said:
I just did that and it worked, but an error at the bottom says "mismatched partition size (recovery)
it does go into recovery now. Tried to install rom and it reboots over and over into recovery. Weird.
Click to expand...
Click to collapse
The "mismatch" is normal because you're flashing a non-stock recovery.
In TWRP, tap wipe, advanced, and do repair for each partition, then do format data. In case you have corrupt partitions.
Gus Ghanem said:
The "mismatch" is normal because you're flashing a non-stock recovery.
In TWRP, tap wipe, advanced, and do repair for each partition, then do format data. In case you have corrupt partitions.
Click to expand...
Click to collapse
It says fails to mount data, dalvik, cache and storage. invalid arguement for each is the reason. unable to repair.
D.A.N. said:
It says fails to mount data, dalvik, cache and storage. invalid arguement for each is the reason. unable to repair.
Click to expand...
Click to collapse
What storage type should i have?EXT4 or something else?
D.A.N. said:
What storage type should i have?EXT4 or something else?
Click to expand...
Click to collapse
I think it's normally ext4, not sure if it's for all partitions. Data might be f2fs.
Gus Ghanem said:
The "mismatch" is normal because you're flashing a non-stock recovery.
In TWRP, tap wipe, advanced, and do repair for each partition, then do format data. In case you have corrupt partitions.
Click to expand...
Click to collapse
It wont let me wipe or repair anything. it just is red all over the place with errors. I seem to be stuck.
D.A.N. said:
It wont let me wipe or repair anything. it just is red all over the place with errors. I seem to be stuck.
Click to expand...
Click to collapse
Even if you reboot TWRP?
Is your stock firmware MPES24.49-18-7
Gus Ghanem said:
Even if you reboot TWRP?
Click to expand...
Click to collapse
yes, i am attempting to restore from twrp a from a folder i have. It seems to be working but said when it started it failed to mount storage so i don't know if it will work? Do you know how to wipe everything completely and start all over again or have I screwed it up to much? Thanks for your help.
D.A.N. said:
yes, i am attempting to restore from twrp a from a folder i have. It seems to be working but said when it started it failed to mount storage so i don't know if it will work? Do you know how to wipe everything completely and start all over again or have I screwed it up to much? Thanks for your help.
Click to expand...
Click to collapse
Your stock firmware files, are they MPES24.49-18-7
I have a XT1097 RETCA
You could try reflashing the partition table and bootloader if you're absoluitely sure you have the latest firmware.
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
D.A.N. said:
yes, i am attempting to restore from twrp a from a folder i have. It seems to be working but said when it started it failed to mount storage so i don't know if it will work? Do you know how to wipe everything completely and start all over again or have I screwed it up to much? Thanks for your help.
Click to expand...
Click to collapse
I am wondering if its because I changed the file system type to ext4 and it should be something else. Do you know what the normal file system should be?
D.A.N. said:
I am wondering if its because I changed the file system type to ext4 and it should be something else. Do you know what the normal file system should be?
Click to expand...
Click to collapse
It is ext4 except data, which is f2fs
File system
\
Gus Ghanem said:
It is ext4 except data, which is f2fs
Click to expand...
Click to collapse
it was the file system types. I changed them to what you said and it wiped them. attempting to reinstall rom and if it works i can try to go to stock again i guess. Thank you Gus for taking time to help.
Gus Ghanem said:
File system
Click to expand...
Click to collapse
I installed stock rooted rom. It booted backed into recovery. I had to reboot into bootloader, rebooted from there and it is turning on. I think something is still screwed up though because it always boots back into recovery.
How to install stock rom after formatting all partitions like "adb fastboot format userdata" (including system, boot), download mode won't work, right?
I will do this process on an unrooted device.
Use Odin to flash the firmware in download mode.
V0latyle said:
Use Odin to flash the firmware in download mode.
Click to expand...
Click to collapse
"I think the download mode feature will not work because I will use the following commands to format the partitions:
fastboot format userdata
fastboot format cache
fastboot format system
fastboot format boot
fastboot format recovery
since I am formatting the boot partition."
V0latyle said:
Use Odin to flash the firmware in download mode.
Click to expand...
Click to collapse
Basically, does the download mode get damaged?
FATDROIDA said:
Basically, does the download mode get damaged?
Click to expand...
Click to collapse
no, you didnt erase the bootloader(hope you didnt)
FATDROIDA said:
"I think the download mode feature will not work because I will use the following commands to format the partitions:
fastboot format userdata
fastboot format cache
fastboot format system
fastboot format boot
fastboot format recovery
since I am formatting the boot partition."
Click to expand...
Click to collapse
It is a Samsung device. The proper way to flash firmware is by using Odin. Samsung does not use the same fastboot command procedure as AOSP model devlices such as the Pixel. You use Odin to flash partitions on the device, including recovery. If you flash a custom recovery such as TWRP, you can then install custom boot and system images.
If you don't know what you're doing, or what effect it will have, you probably shouldn't be doing it.
Hichem2006 said:
no, you didnt erase the bootloader(hope you didnt)
Click to expand...
Click to collapse
I want to clean all the disk space on my device and install a fresh stock ROM. I'm still in the planning stage and haven't done anything yet. My device is unrooted.
V0latyle said:
It is a Samsung device. The proper way to flash firmware is by using Odin. Samsung does not use the same fastboot command procedure as AOSP model devlices such as the Pixel. You use Odin to flash partitions on the device, including recovery. If you flash a custom recovery such as TWRP, you can then install custom boot and system images.
If you don't know what you're doing, or what effect it will have, you probably shouldn't be doing it.
Click to expand...
Click to collapse
oh yeah totally forgot about it, Samsung phones don't have a fastboot interface