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.

HELPPP!

So I feel like I am really screwed on this.... attempted flashing stock via RSDLite. It began flashing fine until about halfway through the system.img ...all of a sudden it loses fastboot and my computer freaks out saying that an unkown standard usb device is attached. I figured that I would just flash a batch through recovery, but now there is not recovery image either.
So... I have no fastboot mode and no recovery mode and an unrecognizable usb device. Please help me
Edit: I have a feeling its due to a driver issue... during the downgrade the required driver probably changed... and thus disconnected in the middle of flash. If this is the case, then I feel like an idiot

diabl0w said:
So I feel like I am really screwed on this.... attempted flashing stock via RSDLite. It began flashing fine until about halfway through the system.img ...all of a sudden it loses fastboot and my computer freaks out saying that an unkown standard usb device is attached. I figured that I would just flash a batch through recovery, but now there is not recovery image either.
So... I have no fastboot mode and no recovery mode and an unrecognizable usb device. Please help me
Click to expand...
Click to collapse
Try setting up another computer. You should be able to go into bootlader mode by pressing power and volume down buttons at the same time. Hopefully you have enought battery. If that doesnt work someone should be able to help you out.

Downgrading the bootloader on Motorola devices (Nexus 6 included) results in a permanent (well, unless you can upgrade the bootloader to what it was originally) brick.

r3pwn said:
Downgrading the bootloader on Motorola devices (Nexus 6 included) results in a permanent (well, unless you can upgrade the bootloader to what it was originally) brick.
Click to expand...
Click to collapse
Wow I hope that my edit was right instead... I know for a fact that it failed during the system image portion of the flash. all I did was follow the instructions posted somewhere on this forum which basically just said... download 21.12 firmware, go to fastboot, flash with rsdlite. Guess the fact that they left out remove bootloader image is no big deal.. NOT

diabl0w said:
Wow I hope that my edit was right instead... I know for a fact that it failed during the system image portion of the flash. all I did was follow the instructions posted somewhere on this forum which basically just said... download 21.12 firmware, go to fastboot, flash with rsdlite. Guess the fact that they left out remove bootloader image is no big deal.. NOT
Click to expand...
Click to collapse
It's nothing they did wrong. At the time of writing it, that was probably the latest version. Can you still flash things via rsdlite? If so, take a look at this copy of the latest update.

r3pwn said:
It's nothing they did wrong. At the time of writing it, that was probably the latest version. Can you still flash things via rsdlite? If so, take a look at this copy of the latest update.
Click to expand...
Click to collapse
Okay so good news... I installed the older sdk drivers and my phone will now connect to fastboot mode again. wooo!!! Now, to make sure I do this right, @r3pwn , the link you just sent me was a superuser image, right? Background story as to why I am doing this, I have root and I ended up breaking google play services pretty bad and reinstalling would not fix the problem and neither would cache clear or system.img flash. So I was just gonna try to start fresh. So, I attempted to flash 21.12 firmware and thats how I ended up here. What should I do next? Flash that SU firmware or flash the 21.12 firmware? Should I remove the bootloader and boot images from those .xml files? Thanks for your time, I should be good after that information

diabl0w said:
Okay so good news... I installed the older sdk drivers and my phone will now connect to fastboot mode again. wooo!!! Now, to make sure I do this right, @r3pwn , the link you just sent me was a superuser image, right? Background story as to why I am doing this, I have root and I ended up breaking google play services pretty bad and reinstalling would not fix the problem and neither would cache clear or system.img flash. So I was just gonna try to start fresh. So, I attempted to flash 21.12 firmware and thats how I ended up here. What should I do next? Flash that SU firmware or flash the 21.12 firmware? Should I remove the bootloader and boot images from those .xml files? Thanks for your time, I should be good after that information
Click to expand...
Click to collapse
That's not the root firmware, that's just plain stock. I would recommend you flash that image (the one I linked) then re-root.

r3pwn said:
That's not the root firmware, that's just plain stock. I would recommend you flash that image (the one I linked) then re-root.
Click to expand...
Click to collapse
I realized that after I downloaded the file and took a look at it further... thanks for your help and for bearing with me. It worked!

[ROM] Stock Rooted 5.1.1

Since pepole have no knolege of what they are doing and kind of blame me for it i will not provide the images anymore.
Please lock this thread.

Thank you so much!
Question: Do we have to flash the stock recovery after flashing the rooted system image? I prefer to have TWRP recovery anyways.

akarol said:
Thank you so much!
Question: Do we have to flash the stock recovery after flashing the rooted system image? I prefer to have TWRP recovery anyways.
Click to expand...
Click to collapse
worst case just reflash TWRP =]

akarol said:
Thank you so much!
Question: Do we have to flash the stock recovery after flashing the rooted system image? I prefer to have TWRP recovery anyways.
Click to expand...
Click to collapse
You can use whatever recovery you would like, the system image does not affect the recovery in any way.

Thanks - flashed your bootloader files which got me out of a never ending boot animation issue

j32olger said:
Thanks - flashed your bootloader files which got me out of a never ending boot animation issue
Click to expand...
Click to collapse
The bootloop have nothing to do with my bootloader files, they are completley stock from the ota file!
If you installing the new bootloader files on older roms you are asking for troubles.
Boot the watch in bootloader mode and flash the files as described and you watch will work.
Af if it bootlooping run a "Fastboot -w" after flashing.

Greetings, Is the newly released OTA compatible with your rom?

drmcatchr said:
Greetings, Is the newly released OTA compatible with your rom?
Click to expand...
Click to collapse
No ota files will only work with stock untouched rom.

bunny0007 said:
No ota files will only work with stock untouched rom.
Click to expand...
Click to collapse
Are you planning on releasing a pre-rootet image of the latest ota?
Would be greatly appreciated!

2k4ever said:
Are you planning on releasing a pre-rootet image of the latest ota?
Would be greatly appreciated!
Click to expand...
Click to collapse
Have added it today.

I tried this using the update (LCA44B) and now the watch doesn't even turn on. No LG logo or anything.

GuiyeC said:
I tried this using the update (LCA44B) and now the watch doesn't even turn on. No LG logo or anything.
Click to expand...
Click to collapse
And you did follow the instuctions?7
Flash bootloader stuff
Flash system image
Flash boot image
Have testet it serval times without errors.

bunny0007 said:
And you did follow the instuctions?7
Flash bootloader stuff
Flash system image
Flash boot image
Have testet it serval times without errors.
Click to expand...
Click to collapse
Yep, just like in the steps, the thing did show a FAILED (anti-rollback) when flashing the 'aboot'. I just used everything that was on the zip, now the watch doesn't even show the LG logo, I've tried plugging it on and off and keeping the reset button pressed for a while. I really don't know what else to try.
I'm waiting for it to run out of battery, but I don't even know if it's "on".

GuiyeC said:
Yep, just like in the steps, the thing did show a FAILED (anti-rollback) when flashing the 'aboot'. I just used everything that was on the zip, now the watch doesn't even show the LG logo, I've tried plugging it on and off and keeping the reset button pressed for a while. I really don't know what else to try.
I'm waiting for it to run out of battery, but I don't even know if it's "on".
Click to expand...
Click to collapse
Did just ran it on my own watch and everything working.
If you aboot fails flashing your watch might have another problem, i assume that your watch have an unlocked bootloader??

bunny0007 said:
Did just ran it on my own watch and everything working.
If you aboot fails flashing your watch might have another problem, i assume that your watch have an unlocked bootloader??
Click to expand...
Click to collapse
Yes, it had the boot loader unlocked, and I can't try again flashing the aboot because I can't get it to recovery mode or fast boot mode or anything.

Who can I get the images from?

bunny0007 said:
Since pepole have no knolege of what they are doing and kind of blame me for it i will not provide the images anymore.
Please lock this thread.
Click to expand...
Click to collapse
By people, do you mean 1 person ???
Pretty unfair for other, isn't it ?

I am looking for bootloader files for the G Watch R to flash over what I believe to be a corrupt bootloader on my device. It will only boot when on the charging stand, and so far I have only been able to get it to boot to 5.0.1 successfully. Once the device tries to pull down the OTA update it reboots and proceeds to run the update and then it fails and powers off.
Currently I can access fastboot and I can get it to boot a stock recovery and twrp with the 5.0.1 boot.img flashed to my device.

Can anyone who has downloaded the original package from this thread PM me the files? I need to reflash my bootloader files to attempt to fix a booting issue with my watch. Any help would be appreciated and I will not hold anyone accountable if I hard brick my device.

fnj00 said:
Can anyone who has downloaded the original package from this thread PM me the files? I need to reflash my bootloader files to attempt to fix a booting issue with my watch. Any help would be appreciated and I will not hold anyone accountable if I hard brick my device.
Click to expand...
Click to collapse
Hi there ,
Why don't you try this one ??
http://forum.xda-developers.com/g-w...edroid-r-urbane-port-v1-0-0-june-6th-t3128850

Corrupt Message after Dirty Stock Flash - MRA58K to MRA58N

I am fully stock since MRA58K came out. I applied the security update today via the factory images but left user data alone. I am now getting the Corrupt Message during Boot. I accidentally booted TWRP 2.8.7.1 from Fastboot but did not flash it. Just selected reboot. Any Ideas on ways to get rid of it without a factory reset?

what's the exact message?

jj14 said:
what's the exact message?
Click to expand...
Click to collapse
Sorry, I thought it was inherently known with the phrase corrupt during boot. But this with the Red Status
https://support.google.com/nexus/answer/6185381?p=verified_boot

GMoGoody said:
Sorry, I thought it was inherently known with the phrase corrupt during boot. But this with the Red Status
https://support.google.com/nexus/answer/6185381?p=verified_boot
Click to expand...
Click to collapse
So your device is still booting ok . That message shows up if your device is rooted or has some other changes (recovery perhaps).
If you want to stay stock, just reflash the factory images using fastboot (all files skip userdata)

jj14 said:
what's the exact message?
Click to expand...
Click to collapse
jj14 said:
So your device is still booting ok . That message shows up if your device is rooted or has some other changes (recovery perhaps).
If you want to stay stock, just reflash the factory images using fastboot (all files skip userdata)
Click to expand...
Click to collapse
Which I have tried three times and I am still getting this message. The second and third time I tried Flashing MRA58N over itself it did not optimize or anything. I guess I will wait for the next security update, or flash back to MRA58K reboot and try flashing MRA58N again

Did you flash everything? bootloader/boot/recovery/system/radio/cache? (reboot bootloader after flashing radio and bootloader)

flash a custom kernel and it should go away

GMoGoody said:
.>....... the Corrupt Message during Boot. I accidentally booted TWRP 2.8.7.1 from Fastboot but did not flash it. Just selected reboot. Any Ideas on ways to get rid of it without a factory reset?
Click to expand...
Click to collapse
Flash a custom kernel like Franco's kernel

jj14 said:
Did you flash everything? bootloader/boot/recovery/system/radio/cache? (reboot bootloader after flashing radio and bootloader)
Click to expand...
Click to collapse
Yes I flashed everything but the userData even though some things like the radio and bootloader didn't change

Strange. Hopefully somebody else will chime in.

NLBeev said:
Flash a custom kernel like Franco's kernel
Click to expand...
Click to collapse
I want to use android Pay. So I am staying stock. I am trying to figure out why this message suddenly started appearing between MRA58K and MRA58N. If Others are seeing it and potentially how to recover from this state with staying stock but not doing a factory reset. Seems like factory reset may be in order

jj14 said:
Strange. Hopefully somebody else will chime in.
Click to expand...
Click to collapse
My thoughts exactly. When I get home from work I will go back to MRA58K , reboot, then reflash MRA58N. Hopefully this fixes the issue. I will report back tonight. In other threads I saw people were having to go all the way back to 5.1.1 when they saw this when first upgrading to MRA58K
Edit:
This worked. I flashed back to MRA58K, Let it optimize, Verified no corrupt message. then Flashed MRA58N and did the same. So far so good. Also note there is an update to platform-tools in the SDK

GMoGoody said:
I want to use android Pay. So I am staying stock. I am trying to figure out why this message suddenly started appearing between MRA58K and MRA58N. If Others are seeing it and potentially how to recover from this state with staying stock but not doing a factory reset. Seems like factory reset may be in order
Click to expand...
Click to collapse
I think it has to do with TWRP. You used it temporary with fastboot, but it is pushed to the phone's memory. You could try to fastboot flash stock recovery.

SOLVED
I'm getting the same as OP. flashed manually bl/reboot/radio/reboot/system/boot/recovery/cache then tried again with a fresh D/L through Wug's NRT. No joy. Maybe there is something different between the OTA and factory image that would require a data wipe with the latter. Is there an OTA in the wild that I could dissect? Also having bluetooth problems after dirty flashing MRA58N as stated above.
EDIT: Flashed back MRA58K, all is better.
Also noted that after flashing MRA58N the cache didn't rebuild. Hmmm.
SOLUTION: Update platform-tools in your SDK. Just updated and manually dirty flashed, no corrupt message and app cache is rebuilding. :good:

[TWRP][EXPERIMENTAL] suzuran twrp 3.0

Hello people,
I was able to successfully build twrp 3.0 for suzuran (our device, duh!) and thought I'd share the recovery.img so you can test and see what works and what doesn't.
The recovery was built in a CM13 similar environment (PAC), so there might be some issues when working with stock kernel.
Since this is an experimental build (I tested main functionalities and they work, but didn't get down to the nitty-gritty), here's a small disclaimer:
By flashing or booting the attached recovery you're risking damaging you device, or losing the data on your device!
Neither I nor anyone else but YOU is responsible should any bad unintended problems appear!
If you're feeling adventurous then feel free to flash the recovery.img (along with Androplus kernel) and try the sweetness that is TWRP 3.0 :good:
Download link:
April 3, 2016 (3.0.1)
March 25, 2016
March 21, 2016
March 12, 2016
Known issues:
Temperature reading is botched
Crypto might not be working, like AT ALL
usb connection doesn't work (only if you use this recovery with Androplus kernel)
There could be more problems, which is why this is EXPERIMENTAL for now
And now let's get to the sources!
kernel:
[url]https://github.com/oshmoun/kernel/tree/aosp/LA.BF64.1.2.2_rb4.7[/URL]
device sources:
[url]https://github.com/oshmoun/device-sony-suzuran/tree/master[/URL]
[url]https://github.com/oshmoun/device-sony-kitakami/tree/master[/URL]
[url]https://github.com/SonyCM/device-sony-common/commits/cm-13.0[/URL]
And now to thank the people who helped in this endeavor:
TWRP team for the awesome recovery!
@nilezon for the TWRP flags (which I still need to go through to check if I missed/need anything, especially crypto flags...)
FXP team for device sources, Especially @adfad666
All of the Sony AOSP contributors, they're awesome people!

It doesn't work on my Android 6.0 device:crying:

doesn't work on sony mm, stuck at sony logo

iMaeGoo said:
It doesn't work on my Android 6.0 device:crying:
Click to expand...
Click to collapse
tanto124 said:
doesn't work on sony mm, stuck at sony logo
Click to expand...
Click to collapse
Could you tell me if you have E5823 or E5803, I have an E5823 and it's working fine.
Also, are you sure you're not FLASHING the recovery.img? You need to just BOOT it directly from fastboot

oshmoun said:
Could you tell me if you have E5823 or E5803, I have an E5823 and it's working fine.
Also, are you sure you're not FLASHING the recovery.img? You need to just BOOT it directly from fastboot
Click to expand...
Click to collapse
E5823, version 32.1.A.1.163, bootloader unlocked, in fastboot mode, using command "fastboot boot TWRP3.img".
And it stucks at SONY logo.

iMaeGoo said:
E5823, version 32.1.A.1.163, bootloader unlocked, in fastboot mode, using command "fastboot boot TWRP3.img".
And it stucks at SONY logo.
Click to expand...
Click to collapse
this is really weird, did the MM update also change something in the bootloader in an inconvenient way?
Could you try the other recovery.img from nilezon's thread? If that boots using "fastboot boot recovery.img" then we'll know the problem is somewhere in the .img itself
EDIT: oh, also could you please check if your download wasn't corrupt? Here's the md5 hash of the file so you can check
69650eaccdd8b24a3efc0ef1b4bdffb8

oshmoun said:
this is really weird, did the MM update also change something in the bootloader in an inconvenient way?
Could you try the other recovery.img from nilezon's thread? If that boots using "fastboot boot recovery.img" then we'll know the problem is somewhere in the .img itself
EDIT: oh, also could you please check if your download wasn't corrupt? Here's the md5 hash of the file so you can check
69650eaccdd8b24a3efc0ef1b4bdffb8
Click to expand...
Click to collapse
69650eaccdd8b24a3efc0ef1b4bdffb8
The img's MD5 is right.
I'll try to boot Z5C_TWRP_152_v2_nilezon on my device later.
It worked before I upgraded to MM.

oshmoun said:
this is really weird, did the MM update also change something in the bootloader in an inconvenient way?
Could you try the other recovery.img from nilezon's thread? If that boots using "fastboot boot recovery.img" then we'll know the problem is somewhere in the .img itself
EDIT: oh, also could you please check if your download wasn't corrupt? Here's the md5 hash of the file so you can check
69650eaccdd8b24a3efc0ef1b4bdffb8
Click to expand...
Click to collapse
I have no idea.
Z5C_TWRP_152_v2_nilezon doesn't work on MM.
I flash Android 5.1 and try your TWRP3.0, still stuck at SONY logo(with no LED light).
Z5C_TWRP_152_v2_nilezon can work on 5.1.
Now I'm flashing MM again.

iMaeGoo said:
I have no idea.
Z5C_TWRP_152_v2_nilezon doesn't work on MM.
I flash Android 5.1 and try your TWRP3.0, still stuck at SONY logo(with no LED light).
Z5C_TWRP_152_v2_nilezon can work on 5.1.
Now I'm flashing MM again.
Click to expand...
Click to collapse
Thanks! Guess the issue lies in the MM update somewhere.
You just said that nilezon's recovery works on 5.1, but did you try it after flashing 5.1, or are you basing that statement on previous tests?
The issue here might be that you didn't downgrade the bootloader when you flashed 5.1 again, which would mean the issue will persist.

Hello,
I tried booting(didn't flash) with MM and it seemed to boot into recovery fine. Used it to do a cache wipe, but afterwards phone is stuck on boot screen. I can turn it off with power + volume, but it doesn't seem like I can go back to fast boot.

t4656 said:
Hello,
I tried booting(didn't flash) with MM and it seemed to boot into recovery fine. Used it to do a cache wipe, but afterwards phone is stuck on boot screen. I can turn it off with power + volume, but it doesn't seem like I can go back to fast boot.
Click to expand...
Click to collapse
You should be able to go into fastboot mode by turning device off, holding vol+ button, then connecting the device to your computer through usb

oshmoun said:
You should be able to go into fastboot mode by turning device off, holding vol+ button, then connecting the device to your computer through usb
Click to expand...
Click to collapse
Yeah thanks. Took something like 10 tries before it finally went into fastboot. Not sure what went wrong there. Also on my first try I was able to boot into your build of twrp. But afterwards when I try it just gets stuck on the logo again.

t4656 said:
Yeah thanks. Took something like 10 tries before it finally went into fastboot. Not sure what went wrong there. Also on my first try I was able to boot into your build of twrp. But afterwards when I try it just gets stuck on the logo again.
Click to expand...
Click to collapse
This is so freaky what the heck!!!
Could you flash bootloader from 5.1 ftf and see if it works properly then?
I'll (finally) update to MM today , so I'll witness the issues first hand.

oshmoun said:
Thanks! Guess the issue lies in the MM update somewhere.
You just said that nilezon's recovery works on 5.1, but did you try it after flashing 5.1, or are you basing that statement on previous tests?
The issue here might be that you didn't downgrade the bootloader when you flashed 5.1 again, which would mean the issue will persist.
Click to expand...
Click to collapse
I tried nilezon's recovery after flashing 5.1 and it worked.
I use FlashTool to write FTF file to my phone fully, include kernel.
Maybe it's my problem...
Thank you for your patience!

iMaeGoo said:
I tried nilezon's recovery after flashing 5.1 and it worked.
I use FlashTool to write FTF file to my phone fully, include kernel.
Maybe it's my problem...
Thank you for your patience!
Click to expand...
Click to collapse
nope, not your problem, it's everyone's
seems like my twrp version just refuses to boot sometimes.
Was able to successfully replicate the fastboot issue on 5.1 bootloader, so it's definitely this recovery.
Now the question is if it's a TWRP 3 issue, or just in the way I built it
EDIT: I guess this post answers my question
http://forum.xda-developers.com/showpost.php?p=65808636&postcount=137
another twrp 3 recovery is having the same issue
guess I'll have to make this recovery flashable in order for it to work properly
EDIT 2: wow, Androplus kernel seems to go well with TWRP 3. Updated first post with new instructions on how to use this.

oshmoun said:
nope, not your problem, it's everyone's
seems like my twrp version just refuses to boot sometimes.
Was able to successfully replicate the fastboot issue on 5.1 bootloader, so it's definitely this recovery.
Now the question is if it's a TWRP 3 issue, or just in the way I built it
EDIT: I guess this post answers my question
http://forum.xda-developers.com/showpost.php?p=65808636&postcount=137
another twrp 3 recovery is having the same issue
guess I'll have to make this recovery flashable in order for it to work properly
EDIT 2: wow, Androplus kernel seems to go well with TWRP 3. Updated first post with new instructions on how to use this.
Click to expand...
Click to collapse
Can not detect external SD or USB OTG (yet)
Can not detect external SD or USB OTG (yet)
Can not detect external SD or USB OTG (yet)
This will do the job until a proper dev makes a better version.
Maybe I had better wait...:crying::crying::crying:

iMaeGoo said:
Can not detect external SD or USB OTG (yet)
Can not detect external SD or USB OTG (yet)
Can not detect external SD or USB OTG (yet)
This will do the job until a proper dev makes a better version.
Maybe I had better wait...:crying::crying::crying:
Click to expand...
Click to collapse
ummm, my sdcard is getting detected :|
I'll post screenshots soon
EDIT: attached screenshots

oshmoun said:
ummm, my sdcard is getting detected :|
I'll post screenshots soon
EDIT: attached screenshots
Click to expand...
Click to collapse
Can external storages be found in Android system?

iMaeGoo said:
Can external storages be found in Android system?
Click to expand...
Click to collapse
everything concerning external sdcard function is working here as far as i tested (both in Stock mm rom and twrp3)

oshmoun said:
Could you tell me if you have E5823 or E5803, I have an E5823 and it's working fine.
Also, are you sure you're not FLASHING the recovery.img? You need to just BOOT it directly from fastboot
Click to expand...
Click to collapse
it's E5823 running 32.1.A.1.163 . I am sure that I was just booting , downloaded file is okay .