Database Develop

Need help upgrading to 5.1, Tired of flashing all the things.

My nexus 6 is unlocked and is running stock 5.0.1, rooted. . It has twrp and is decrypted.
I tried to sideload the 5.1 ota but it doesnt work.
I tried flashing the new 5.1 factory image but that doesnt work.
I'm tired of all this now, I just want my phone running stock 5.1 , locked , encrypted ,unrooted so I can just get ota next time from Google whenever they send it out.
Any guidance on what I need to do would be appreciated.

Use Wug's Nexus Root Toolkit :good:
Edit : Now I'm currently "Optimising app..." loop.

I tried using tge NRT to flash it back to stock but it didn't work.

I would first make a TWRP backup, then I would flash the boot image (decrypted if you want and make sure its the new one), system, radio and then reboot. I flashed everything fine while keeping twrp on my phone but I didn't like not having a custom ROM plus it was a little laggy so I restored a TWRP backup. My phone did bootloop for a while but eventually it booted 5.1. I would be careful since 5.1 seems to be having some issues in general.

http://forum.xda-developers.com/nex...gs-nexus-root-toolkit-v1-9-8-t2947452/page101
Quote:
Originally Posted by baudi11
Same thing happened to me. Here's what I did.
1. Press and hold power, volume up, and volume down. Keep holding them down until the phone boots into bootloader mode.
2. Go back to the toolkit and click the radio button labeled "Soft bricked/bootloop"
3. Click "Flash stock plus unroot"
4. Check all the boxes under "Settings", including "Post-flash factory reset" then click OK.
5. Follow the toolkit instructions from there.
This got me out of the bootloop, successfully installed 5.1, and kept all my apps and settings. Good luck.
Click to expand...
Click to collapse
It worked for me after that. Now I'm booted in 5.1

When I try to flash the factory images directly from Google I get the following errors even though the MD5 checks out.
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 1778070480 bytes
error: update package missing system.img
Press any key to exit...

celeriL said:
http://forum.xda-developers.com/nex...gs-nexus-root-toolkit-v1-9-8-t2947452/page101
It worked for me after that. Now I'm booted in 5.1
Click to expand...
Click to collapse
Thanks so much! This worked perfectly. Exactly what I needed. The past couple days have been so annoying but now it's over. Thanks again!

Giuseppe1010 said:
Thanks so much! This worked perfectly. Exactly what I needed. The past couple days have been so annoying but now it's over. Thanks again!
Click to expand...
Click to collapse
Glad to help!

You also could have extracted the zip and manually flashed the images ing fastboot
fastboot flash recovery recovery.img
fastboot flash system system.img
Etc

rootSU said:
You also could have extracted the zip and manually flashed the images ing fastboot
fastboot flash recovery recovery.img
fastboot flash system system.img
Etc
Click to expand...
Click to collapse
HaHaa. Tried and true. Always works.

prdog1 said:
HaHaa. Tried and true. Always works.
Click to expand...
Click to collapse
rootSU said:
You also could have extracted the zip and manually flashed the images ing fastboot
fastboot flash recovery recovery.img
fastboot flash system system.img
Etc
Click to expand...
Click to collapse
I agree that always works without fail and is much easier than a tool kit. I don't like tool kits because people need to learn the correct way to flash things before using one because its better to understand what you are flashing should there be an error.

Pilz said:
I agree that always works without fail and is much easier than a tool kit. I don't like tool kits because people need to learn the correct way to flash things before using one because its better to understand what you are flashing should there be an error.
Click to expand...
Click to collapse
I totally agree. Have done successful manual flash when tool kits failed. Seen on Nexus 6 already.Saved my soft brick with manual flash when tool kit failed.

Pilz said:
I agree that always works without fail and is much easier than a tool kit. I don't like tool kits because people need to learn the correct way to flash things before using one because its better to understand what you are flashing should there be an error.
Click to expand...
Click to collapse
I don't have anything against toolkits on some devices, so long as it is not used as a shortcut to learning the basics. That said, on a nexus, I don't really see any need to be honest.

rootSU said:
I don't have anything against toolkits on some devices, so long as it is not used as a shortcut to learning the basics. That said, on a nexus, I don't really see any need to be honest.
Click to expand...
Click to collapse
Thats how I feel because its so easy my wife could do it and she doesn't know anything about flashing. Toolkits are good for non Nexus devices, I just don't see a point when we need to learn things the correct way first.
I hope the bugs get sorted out so people don't hard brick their phones anyone

rootSU said:
You also could have extracted the zip and manually flashed the images ing fastboot
fastboot flash recovery recovery.img
fastboot flash system system.img
Etc
Click to expand...
Click to collapse
Im a complete fastboot novice since this is my first nexus device (always had samsung phones up until now) and although I managed to root and unlock the boot loader I want to make sure I learn all the basics including flashing (side loading?) subsequent updates.
So Im currently rooted, unlocked bootloader on a 5.01. custom rom. How would I go about flashing the 5.1 update manually?
Im assuming that once I extract the update zip file I will find all the images that need to be flashed....what order do i do them in? How do I take into account the boot loader locking issue people have been facing that results in a bricked device?
Thanks in advance.
EDIT: I found this thread which outlines what I need to do http://forum.xda-developers.com/nexus-6/general/using-image-to-update-nexus-6-data-loss-t3053158
I only have two question now:
1. Im assuming the system image will wipe out the custom rom im on but not the data will leaving the data cause a problem? whats the command line to wipe data?
2. This doesnt address the boot loader locking issue causing a brick that people have been facing. This process involves updating the boot loader what do i have to do to make sure I dont brick my device?
Thanks again

kingofkings11 said:
Im a complete fastboot novice since this is my first nexus device (always had samsung phones up until now) and although I managed to root and unlock the boot loader I want to make sure I learn all the basics including flashing (side loading?) subsequent updates.
So Im currently rooted, unlocked bootloader on a 5.01. custom rom. How would I go about flashing the 5.1 update manually?
Im assuming that once I extract the update zip file I will find all the images that need to be flashed....what order do i do them in? How do I take into account the boot loader locking issue people have been facing that results in a bricked device?
Thanks in advance.
EDIT: I found this thread which outlines what I need to do http://forum.xda-developers.com/nexus-6/general/using-image-to-update-nexus-6-data-loss-t3053158
I only have two question now:
1. Im assuming the system image will wipe out the custom rom im on but not the data will leaving the data cause a problem? whats the command line to wipe data?
2. This doesnt address the boot loader locking issue causing a brick that people have been facing. This process involves updating the boot loader what do i have to do to make sure I dont brick my device?
Thanks again
Click to expand...
Click to collapse
You could simply not update the bootloader. Bare minimum requirements is update system and boot (kernel). if you want to learn more about fastboot, go to general > All in one guide > Question 28.
If you do not update the bootloader, you'll never get an OTA but it doesn't seem like you're wanting that anyway.
In regards to data, yes it could cause a problem if you're using a custom rom. You can use fastboot erase data command. This also wipes your /sdcard though.

Wont boot to recovery after flashing

Hey,
I dont know how different things are now, i installed a RUU with lollipop and i've been trying to flash TWRP but after i try to get into recovery and i got stuck at the logo with "entering into recovery...", adb detects device and nothing happens, tried to delete cache still didnt work. I bet i'm missing something as stupid as a simple boot...

Terramoto said:
Hey,
I dont know how different things are now, i installed a RUU with lollipop and i've been trying to flash TWRP but after i try to get into recovery and i got stuck at the logo with "entering into recovery...", adb detects device and nothing happens, tried to delete cache still didnt work. I bet i'm missing something as stupid as a simple boot...
Click to expand...
Click to collapse
you flash the recovery for the m7wls.

Aldo101t said:
you flash the recovery for the m7wls.
Click to expand...
Click to collapse
what kind of statement was that? Or was it a question? Yep i flashed m7wls isn't that sprint version of TWRP?
EDIT: I think i know what you mean, TWRP is not working well with lollipop, is that it?

Terramoto said:
what kind of statement was that? Or was it a question? Yep i flashed m7wls isn't that sprint version of TWRP?
EDIT: I think i know what you mean, TWRP is not working well with lollipop, is that it?
Click to expand...
Click to collapse
no just checking you installed the correct recovery, for lollipop you should have the latest recovery, that's all

I can't either get root or flash a ROM without access to recovery?

what else can i do?

Terramoto said:
what else can i do?
Click to expand...
Click to collapse
Reflash latest firmware from here http://forum.xda-developers.com/showthread.php?t=2795856 (i recommend Modified Firmware....removed hboot, recovery & boot (fastboot flashable))
Then flash latest recovery twrp-2.8.6.0-m7wls..

crazykas said:
Reflash latest firmware from here http://forum.xda-developers.com/showthread.php?t=2795856 (i recommend Modified Firmware....removed hboot, recovery & boot (fastboot flashable))
Then flash latest recovery twrp-2.8.6.0-m7wls..
Click to expand...
Click to collapse
Didnt work, it tries to enter recovery but its like there's no recovery. The phone's not letting me flash the recovery only the stock one

Terramoto said:
Didnt work, it tries to enter recovery but its like there's no recovery. The phone's not letting me flash the recovery only the stock one
Click to expand...
Click to collapse
Did you flash the firmware first?

crazykas said:
Did you flash the firmware first?
Click to expand...
Click to collapse
yeah, i flashed the modified first then tried to flash recovery, it just wont go into recovery. Is there a way to downgrade back to kitkat? Everything was working good with kk, i had to replace the display, camera and battery so i flashed lollipop RUU thinking there wouldnt be any difference... Now i can't even get root

Terramoto said:
yeah, i flashed the modified first then tried to flash recovery, it just wont go into recovery. Is there a way to downgrade back to kitkat? Everything was working good with kk, i had to replace the display, camera and battery so i flashed lollipop RUU thinking there wouldnt be any difference... Now i can't even get root
Click to expand...
Click to collapse
Was there any error when you flashing recovery?It just doesn't boot to recovery?Then you should flash FULL RUU..It should be the fix

crazykas said:
Was there any error when you flashing recovery?It just doesn't boot to recovery?Then you should flash FULL RUU..It should be the fix
Click to expand...
Click to collapse
no error, everything went smooth its just the boot part, funny thing is im able to flash and boot twrp 2.5.0.0 but im not able to use it because it doesnt respond to touch. I'm currently with stock recovery but i'd like to root and remove crappy apps from my phone :\

Terramoto said:
no error, everything went smooth its just the boot part, funny thing is im able to flash and boot twrp 2.5.0.0 but im not able to use it because it doesnt respond to touch. I'm currently with stock recovery but i'd like to root and remove crappy apps from my phone :\
Click to expand...
Click to collapse
i faced that prob too,but i just had to update to latest firmware & recovery.Flash twrp 2.6.0 & try.

crazykas said:
i faced that prob too,but i just had to update to latest firmware & recovery.Flash twrp 2.6.0 & try.
Click to expand...
Click to collapse
I think i did that, isnt that what RUU's suppose to do?
Anyway, here's the log and last_kmsg if anyone knows how to trace this
log:
http://www.pastebin.ca/2978960
Last_kmsg:
http://pastebin.ca/2978961
@mdmower

I was told that since i replaced parts i might have replaced a part thats not the same as the original one and that i would need to make a custom recovery. I've already download the kmsg report (http://pastebin.com/USayUFqx) i just need some eyes that understand whats happening.

[Q] Possibly bricked N6, bootloop, no recovery, locked bootloader . Help me

Hello guys,
This is possibly the first ever phone I have bricked. Since I moved from Chroma to Euphoria my Nexus 6 was reporting 23GB of total available storage, that's 3GB less than what I was getting with Chroma.
So I decided to revert back to stock hoping that would have sorted the partition layout but found myself in a bootloop. I tried several factory versions with no go, bootloop was still persisting. At that point I was like I am going to relock the bootloader to see if that makes any difference, and when I realized it did not and I tried to unlock it again, from that point on I realized I was very much screwed.
The current situation. I flashed a 5.0.1 factory stock that is in bootloop, bootloader is locked, no access to the stock recovery.
I have made a ton of researches and it seems I will have to send the device on repair.
Any idea of what else I could possibly try to rescue this phone?
How's that there's not a way to force unlocking the bootloader from fastboot when the system is not in a operational state?
I will appreciate any help.
Thanks

Segnale007 said:
Hello guys,
This is possibly the first ever phone I have bricked. Since I moved from Chroma to Euphoria my Nexus 6 was reporting 23GB of total available storage, that's 3GB less than what I was getting with Chroma.
So I decided to revert back to stock hoping that would have sorted the partition layout but found myself in a bootloop. I tried several factory versions with no go, bootloop was still persisting. At that point I was like I am going to relock the bootloader to see if that makes any difference, and when I realized it did not and I tried to unlock it again, from that point on I realized I was very much screwed.
The current situation. I flashed a 5.0.1 factory stock that is in bootloop, bootloader is locked, no access to the stock recovery.
I have made a ton of researches and it seems I will have to send the device on repair.
Any idea of what else I could possibly try to rescue this phone?
How's that there's not a way to force unlocking the bootloader from fastboot when the system is not in a operational state?
I will appreciate any help.
Thanks
Click to expand...
Click to collapse
Do you have TWRP or stock recovery?

cam30era said:
Do you have TWRP or stock recovery?
Click to expand...
Click to collapse
Nope I do not. I don't even have access to the stock recovery. For some reason when I select the stock recovery the recovery menu does not appear. It just comes up a dead android with a question mark and nothing else..

Segnale007 said:
Nope I do not. I don't even have access to the stock recovery.
Click to expand...
Click to collapse
I'm sorry to tell you that the only thing you can do is return it for repair/replacement. FWIW: if you had left the bootloader unlocked, we could have helped you.

cam30era said:
I'm sorry to tell you that the only thing you can do is return it for repair/replacement. FWIW: if you had left the bootloader unlocked, we could have helped you.
Click to expand...
Click to collapse
I kinda knew it.. This Nexus 6 was bought outside of the Play Store. Will Motorola either replace it or repair it?
I am just gonna say I woke up in the morning and found the phone in bootloop..

Segnale007 said:
I kinda knew it.. This Nexus 6 was bought outside of the Play Store. Will Motorola either replace it or repair it?
I am just gonna say I woke up in the morning and found the phone in bootloop..
Click to expand...
Click to collapse
You have nothing to loose by contacting them and asking.

What 5.0.1 factory stock file did you flash?

Mega Montana said:
What 5.0.1 factory stock file did you flash?
Click to expand...
Click to collapse
This one right here https://dl.google.com/dl/android/aosp/shamu-lrx22c-factory-ff173fc6.tgz

Flashing that file following the correct steps should not have sent the phone in a bootloop. Gonna need a bit more info to know what got screwed up. Also, have you connected your phone to your PC to see if it recognizes it? You said you can't boot into recovery but what about the bootloader, power + vol down?

Mega Montana said:
Flashing that file following the correct steps should not have sent the phone in a bootloop. Gonna need a bit more info to know what got screwed up. Also, have you connected your phone to your PC to see if it recognizes it? You said you can't boot into recovery but what about the bootloader, power + vol down?
Click to expand...
Click to collapse
Depends if he had a 5.1 bootloader before or not. Attempts to downgrade the BL from 5.1 will result in a loop.
If it appears when connecting to the PC as qhsusb mode, then it's fixable. If it appears normally as a fastboot device, then it needs repairing.

Guys after 6 hours of nightmare I am glad to say it all ended up in a big scare.
Here is how I managed to get around the bootloop and get android to boot up.. http://forum.xda-developers.com/showpost.php?p=61079544&postcount=312
Thanks for the help

Segnale007 said:
Guys after 6 hours of nightmare I am glad to say it all ended up in a big scare.
Here is how I managed to get around the bootloop and get android to boot up.. http://forum.xda-developers.com/showpost.php?p=61079544&postcount=312
Thanks for the help
Click to expand...
Click to collapse
How did you do that with a locked bootloader?

cam30era said:
How did you do that with a locked bootloader?
Click to expand...
Click to collapse
I have reason to believe that the procedure outlined in the link I posted did not help me. What rather helped me must have been that I flashed userdata an cache from 5.1.1 factory stock to the 5.0.1 factory stock I had bootlooping.
I just felt to mention that I followed that procedure, but I bet its not what managed to help me booting back in android.

Segnale007 said:
I have reason to believe that the procedure outlined in the link I posted did not help me. What rather helped me must have been that I flashed userdata an cache from 5.1.1 factory stock to the 5.0.1 factory stock I had bootlooping.
I just felt to mention that I followed that procedure, but I bet its not what managed to help me booting back in android.
Click to expand...
Click to collapse
Well, I'm glad for you. But I still don't understand how you could flash anything with a locked bootloader.

cam30era said:
Well, I'm glad for you. But I still don't understand how you could flash anything with a locked bootloader.
Click to expand...
Click to collapse
Maybe he had the downgrade "brick" as i suggested a page back. Only way I know to flash when locked.
Or maybe the format part of a flash fixed itm

rootSU said:
Maybe he had the downgrade "brick" as i suggested a page back. Only way I know to flash when locked.
Or maybe the format part of a flash fixed itm
Click to expand...
Click to collapse
Aahh. That makes sense. I'm still amazed that recovery was this easy.

cam30era said:
Well, I'm glad for you. But I still don't understand how you could flash anything with a locked bootloader.
Click to expand...
Click to collapse
rootSU said:
Maybe he had the downgrade "brick" as i suggested a page back. Only way I know to flash when locked.
Or maybe the format part of a flash fixed itm
Click to expand...
Click to collapse
I am not sure whether I had a softbrick or a downgrade brick, all I know is that with a locked bootloader I was able to format and flash only cache and userdata, and btw while googling I have also found other people in the same situation as the one I have been that were also able to format and flash userdata and cache partitions with a locked bootloader.
I am just surprised to see the phone booting with a userdata and cache files from a newer version of android. That's what probably saved my butt.

Segnale007 said:
I am not sure whether I had a softbrick or a downgrade brick, all I know is that with a locked bootloader I was able to format and flash only cache and userdata, and btw while googling I have also found other people in the same situation as the one I have been that were also able to format and flash userdata and cache partitions with a locked bootloader.
Btw I was surprised to see the phone booting with a userdata and cache files from a newer version of android.
Click to expand...
Click to collapse
Most of those who were able to successfully format cache and userdata still had TWRP installed. You are very lucky. Should buy a lotto ticket today.

Segnale007 said:
I am not sure whether I had a softbrick or a downgrade brick, all I know is that with a locked bootloader I was able to format and flash only cache and userdata, and btw while googling I have also found other people in the same situation as the one I have been that were also able to format and flash userdata and cache partitions with a locked bootloader.
I am just surprised to see the phone booting with a userdata and cache files from a newer version of android. That's what probably saved my butt.
Click to expand...
Click to collapse
You can format cache and userdata with a locked bootloader. You cannot flash cache or userdata with a locked bootloader... Unless your bootloader is "bricked" as per the thread you linked to ultimately.
FYI formatting has the exact same result as flashing userdata and cache. So the options are:
1) you formatted which fixed it
2) you were bootloader bricked and had to use a gpt.bin to fix it.

official signed 28.2 Fastboot flashable firmware

My phone is bricked, need the complete Fastboot flushable signed 28.2 firmware, Oreo 8.1 May Update for the USA retail model of x4
Mod edit: no trading/payments on XDA please... edited.

I have the OTA. Would you be able to use that?

Why not just flash 28.1 full firmware and just take the ota to 28.2 that it offers immediately?

I thought it was possible to downgrade via the fastboot method with any firmware. Doesn't have to be 28.2 to at the very least get your phone back working.

try flashing OTA. adb sideload it.
https://forum.xda-developers.com/moto-x4/help/moto-x4-patch-captured-opw28-2-t3807679

my phone is boot loader locked, with OEM locking option set to OFF, and it does not boot into anything. just Fastboot works. I cannot get recovery to work.

jpolster2005 said:
my phone is boot loader locked, with OEM locking option set to OFF, and it does not boot into anything. just Fastboot works. I cannot get recovery to work.
Click to expand...
Click to collapse
Flash this: https://androidfilehost.com/?fid=962339331458997429
All you need is fastboot.

ptn107 said:
Flash this: https://androidfilehost.com/?fid=962339331458997429
All you need is fastboot.
Click to expand...
Click to collapse
I tried that, validation failed.

does ANYBODY have the Fastboot complete version of 28.2? Please? I need to unblock my phone!

jpolster2005 said:
does ANYBODY have the Fastboot complete version of 28.2? Please? I need to unblock my phone!
Click to expand...
Click to collapse
Are you not able to flash 28.1?

when I try, it says image validation failed. I NEED 28.2 or higher

see, my boot loader was locked when I tried to flash a different rom. I didn't know I needed to unlock the boot loader I thought that step was optional. now im stuck with a phone that only boots to Fastboot, will ONLY accept SIGNED STOCK 28.2 or higher.

Can try https://androidfilehost.com/?w=files&flid=229118 or https://firmware.center/firmware/Motorola/Moto X4/Stock/XT1900-1/
See if it will accept an earlier version. Couldn't hurt in your situation.

I remember some people helped this file: https://forum.xda-developers.com/showpost.php?p=76918099&postcount=7
Haven't tried myself but just do it. Nothing to lose

I have successfully unlocked my Project Fi phone (Moto X4) and would be happy to share the firmware which is OPW28.2 on the build number... If anyone can tell me how to obtain (extract) it from the phone?
( Motorola version: OPW28.46-18 )

I am in the same boat
jpolster2005 said:
when I try, it says image validation failed. I NEED 28.2 or higher
Click to expand...
Click to collapse
I will also sell mine as well

I have tried flashing every firmware and tried to blank flash but could not

jpolster2005 said:
I have tried flashing every firmware and tried to blank flash but could not
Click to expand...
Click to collapse
Have you tried using a different computer or USB port?
Have you ever unlocked the bootloader before? If not, you could send it to Motorola for replacement.

jpolster2005 said:
I have tried flashing every firmware and tried to blank flash but could not
Click to expand...
Click to collapse
Not sure what to tell you from here. Just make sure not to rush any steps due to frustration or impatience.
I was able to return my first Moto X4 on warranty due to playing around with flashing. I'm sticking 100% stock till we get official lineage.
---------- Post added at 04:29 AM ---------- Previous post was at 04:25 AM ----------
jpolster2005 said:
how long before we see one. I have been relegated to using an iPhone 6 32GB! I really NEEEEEEED my phone to not be bricked. I tried to do the blank flash and boot off sd card and all that to no avail. none of it worked. meow I am getting so frustrated.
Click to expand...
Click to collapse
Bad eticate to post about your issue on multiple threads especially when you have your own. I'm sorry, there is no timetable. Could be tomorrow, could be months. This is the risk in flashing, end even worst in our case since Lenovo has not released factory images.

jpolster2005 said:
see, my boot loader was locked when I tried to flash a different rom. I didn't know I needed to unlock the boot loader I thought that step was optional. now im stuck with a phone that only boots to Fastboot, will ONLY accept SIGNED STOCK 28.2 or higher.
Click to expand...
Click to collapse
What fastboot version use? Use Minimal version, maybe works

Phone stuck on color lines at bootup

Hello i tried to flash new roms but i think my phone is bricked now. i have tried to unbrick. Every time i flash a rom it says done after 1 second. So i know its not flashing properly. before i go buy a new phone can someone help me out please.
Thank you so much

lonster27 said:
Hello i tried to flash new roms but i think my phone is bricked now. i have tried to unbrick. Every time i flash a rom it says done after 1 second. So i know its not flashing properly. before i go buy a new phone can someone help me out please.
Thank you so much
Click to expand...
Click to collapse
Tell us what exactly you did and what exactly fastboot is outputting

Benjamin_L said:
Tell us what exactly you did and what exactly fastboot is outputting
Click to expand...
Click to collapse
i unlocked it which worked and i could still get back into the phone. Then i installed twrp recovery on the phone and then installed from there DM verity disabler. after that is was bricked. now i can not even get back into twrp i just freezes. i am still able to get into fastboot that is all.

lonster27 said:
i unlocked it which worked and i could still get back into the phone. Then i installed twrp recovery on the phone and then installed from there DM verity disabler. after that is was bricked. now i can not even get back into twrp i just freezes. i am still able to get into fastboot that is all.
Click to expand...
Click to collapse
Then you can still flash the fastboot roms. Guides are found here. Or use the included script.
Why would I want to disable dm verity after all?

Benjamin_L said:
Then you can still flash the fastboot roms. Guides are found here. Or use the included script.
Why would I want to disable dm verity after all?
Click to expand...
Click to collapse
thanks can you please maybe provide a link for me please for both methods.

i got the same result when i rebooted the phone after trying to clear the cache in chrome browser ...