Database Info

Issues sideloading 5.0.1

So ive been racking my brain for the last 2 hours trying to figure this out and im still stuck. I just finished unlocking my boot loader on a completely stock nexus 5 running 4.4.4
i used this methodfor unlocking my bootloader
https://www.youtube.com/watch?v=2cOUseflKNE
I then downloaded 5.0.1
785a2f7af3718dba7e569decde8b6c4dc476a309.signed-hammerhead-LRX22C-from-LRX21O.785a2f7a.zip
i then tried side loading the zip using this method
https://www.youtube.com/watch?v=uvch38KDmTk
but i get one of 2 messages, no device found or waiting on device. nothing happens either way
i then tried
http://www.androidcentral.com/how-manually-upgrade-your-nexus?pg=4#content
and got the same message
what am I doing wrong or missing. My boot loader is showing as unlocked

You have to upgrade to 5.0, and then sideload 5.0.1 on top of 5.0. Or you can flash the 5.0.1 factory image.
EDIT: The messages you're getting are probably because you don't have the correct ADB drivers: http://forum.xda-developers.com/showthread.php?t=2588979

I re downloaded that version of adb and im currently downloading 5.0

I got it! I did what u said and download 5.0 and restarted my pc and everything worked, Ill try to sideload 5.01 later

Why flash the 5.0 image just to flash the 5.0.1 OTA when you can just flash the 5.0.1 image?

Wakamatsu said:
Why flash the 5.0 image just to flash the 5.0.1 OTA when you can just flash the 5.0.1 image?
Click to expand...
Click to collapse
Because its so easy, we must insert unnecessary steps to get a feeling of achievement

Wakamatsu said:
Why flash the 5.0 image just to flash the 5.0.1 OTA when you can just flash the 5.0.1 image?
Click to expand...
Click to collapse
Don't think he flashed the image. I think he applied the 5.0 OTA via sideload, then he's going to apply the 5.0.1 OTA in the same manner. Doing that will allow him to not wipe his data. Kinda makes sense since that's how Google intends for it to progress if he just waits for the updates.

Yaz75 said:
Doing that will allow him to not wipe his data.
Click to expand...
Click to collapse
He unlocked his bootloader in fastboot. The phone is wiped.
Yaz75 said:
Kinda makes sense since that's how Google intends for it to progress if he just waits for the updates.
Click to expand...
Click to collapse
Google intended things to be easy with OTA, not optimal, imo.

[Q] Back to stock

I was running cm12 on my nexus 5 and I had unlocked the boot loader and was asking xposed framework aplha version .
But then I decided to go back to stock android and I flashed the flashed the factory image of android 5.1 build number lmy47I . I wiped the data and even relocked the boot loader and now my phone is running smoothly and is on stock android.
But is there a way by which I can check if I flashed it correctly or not?
I mean nothing is broken but I heard android 5.1.1 update is around the corner so I was worried will I be able to apply the ota

Huh what? If it booted and is running smoothly its fine. If you didnt mod anything you'll get the ota
Sent from my Nexus 5 using Tapatalk

If you've flashed the factory image and everything is stock you should be fine for the OTA!

Thanks for the help

Lol....

You didn't need to relock the bootloader though. I tend to not ever want to relock it after unlocking it since that's about he only way you could potentially brick the device I think (Like if you relocked the bootloader and then for some reason the phone would not boot or something I am not sure how you'd unlock the bootloader again but whatever)

Evo_Shift said:
... I am not sure how you'd unlock the bootloader again but whatever)
Click to expand...
Click to collapse
Good to know. Btw, can you tell me, I'm on stock 5.1 unlocked bl, twrp, rooted. Will I be able to apply 5.1.1 over OTA when it comes out ?

jazzh said:
Good to know. Btw, can you tell me, I'm on stock 5.1 unlocked bl, twrp, rooted. Will I be able to apply 5.1.1 over OTA when it comes out ?
Click to expand...
Click to collapse
No, you're rooted.

Will I be able to flash the 5.1.1 image ?

jazzh said:
Will I be able to flash the 5.1.1 image ?
Click to expand...
Click to collapse
Yes

Someone will make a zip file of the update
SENT BY ENTANGLEMENT

Can't update with OTA zip.

I'm on the XT1540 and I got my OTA notification and went back to stock recovery (still rooted and unlocked bootloader) but it fails halfway through flashing everytime. I reflashed TWRP and captured the OTA into a zip but get an error about updating binary or something when flashing it. Is there something I need to delete from the OTA zip to allow it to flash in twrp?
Sent from my MotoG3 using xda premium

You cannot update your systems software using the OTA update if you are rooted and have modified the system in any way as there are checks of original system during the auto update over the OTA. This means having the original recovery too. Wont work on TWRP or CWM. So no root and no custom recovery for OTA. Unlocked bootloader is okay.
In case you want to try the OTA update then what I have noticed on my XT1550 dual sim APAC version is that even unrooting it using the SuperSu unroot option is not going to help. In my case I could download the OTA and waited till it replaced the system software but got stuck midway of the boot animation.
I had to flash the 23.72-33 version of the stock ROM and opt for the OTA update. This time though I was successful.
Hope this info helps.

Yes, what arunhebbare says. you need to back up al your data and restore your stock firmware and than update via ota.
that is the best way of doing it

HelpMeruth said:
Yes, what arunhebbare says. you need to back up al your data and restore your stock firmware and than update via ota.
that is the best way of doing it
Click to expand...
Click to collapse
This...do a full factory image restore, then adb sideload the ota file. It's signed. TWRP can't install it.

Just use fastboot to flash the factory image for the version you want ... screw wiping your user partition like the above recommends.

nikon120 said:
Just use fastboot to flash the factory image for the version you want ... screw wiping your user partition like the above recommends.
Click to expand...
Click to collapse
This...I can't understand, for the life of me, why everyone is wiping userdata with fastboot....that wipes your android data, and internal storage in one shot. Cache erasing is another totally unnecessary step. All that's necessary, at the most, is a factory reset with TWRP to wipe the android data and both caches....but even that shouldn't technically be necessary for an update like this. It's not like this is the marshmallow update!!

arunhebbare said:
You cannot update your systems software using the OTA update if you are rooted and have modified the system in any way as there are checks of original system during the auto update over the OTA. This means having the original recovery too. Wont work on TWRP or CWM. So no root and no custom recovery for OTA. Unlocked bootloader is okay.
In case you want to try the OTA update then what I have noticed on my XT1550 dual sim APAC version is that even unrooting it using the SuperSu unroot option is not going to help. In my case I could download the OTA and waited till it replaced the system software but got stuck midway of the boot animation.
I had to flash the 23.72-33 version of the stock ROM and opt for the OTA update. This time though I was successful.
Hope this info helps.
Click to expand...
Click to collapse
@arunhebbare I've got the APAC version of the G3 as well, which ROMs are you flashing? I could only find images of the India version, did you use those?

my maxx xt1225 br is hard brick help please!!!

hi guys i'm brasilian and my english is pretty poor but lets try. i was flash 4.4.4 rom br retail. and i update via ota for lollipop.. and brick .. i search in forums here ... and i go it to put in boot loader without robot.. already try many ways to recovery my boot loader but always get error remote failure.. and already used 6.0.1 stock .. maybe i need to files atualy for this? i'm very sad my maxx is dead .. someone give me light .. help me fix this ... thank you guys

Is your bootloader locked or unlocked?

ChazzMatt said:
Is your bootloader locked or unlocked?
Click to expand...
Click to collapse
unlocked

kenedi jr said:
unlocked
Click to expand...
Click to collapse
Good.
What version Android was your phone on before the problem?
Were you on stock (factory) or on custom ROM?
Surely you weren't on Kitkat for almost 3 years?

ChazzMatt said:
Good.
What version Android was your phone on before the problem?
Were you on stock (factory) or on custom ROM?
Surely you weren't on Kitkat for almost 3 years?
Click to expand...
Click to collapse
I was in a custom rom and went to 4.4.4 and tried to upgrade via ota .. and brinck so I was able to make boot loader appear more without the robot

kenedi jr said:
I was in a custom rom and went to 4.4.4 and tried to upgrade via ota .. and brinck so I was able to make boot loader appear more without the robot
Click to expand...
Click to collapse
When you downgrade back to lower stock, you have to omit gpt.bin command. Because you have a newer bootloader.
This is also why you can't take OTA. Because it tries to install a different bootloader (which is probably still older than what you had with custom ROM). If you wanted stock 5.0.2 again, you have to flash full stock image and omit the gpt.bin command.
Are you able to use volume and power button to the bootloader screen?

ChazzMatt said:
When you downgrade back to lower stock, you have to omit gpt.bin command. Because you have a newer bootloader.
This is also why you can't take OTA. Because it tries to install a different bootloader (which is probably still older than what you had with custom ROM). If you wanted stock 5.0.2 again, you have to flash full stock image and omit the gpt.bin command.
Are you able to use volume and power button to the bootloader screen?
Click to expand...
Click to collapse
So I'm stuck on the bootloader. If I connect charger or pc it will already pro boot loader without the robot. I have already tried to pass stock 4.4.4 and 6.0 and more etc always from the failure remote failure in bootloader appears in the log something with gt bin downgrade

ChazzMatt said:
When you downgrade back to lower stock, you have to omit gpt.bin command. Because you have a newer bootloader.
This is also why you can't take OTA. Because it tries to install a different bootloader (which is probably still older than what you had with custom ROM). If you wanted stock 5.0.2 again, you have to flash full stock image and omit the gpt.bin command.
Are you able to use volume and power button to the bootloader screen?
Click to expand...
Click to collapse
My question is if I crashed from 4.4.4 trying to upgrade to 5.1 which version files do I need to adapt to my bootloader that seems to be corrupted?

kenedi jr said:
My question is if I crashed from 4.4.4 trying to upgrade to 5.1 which version files do I need to adapt to my bootloader that seems to be corrupted?
Click to expand...
Click to collapse
Before this trouble, were you ever on stock Marshmallow 6.0.1? If so, you can flash back to full firmware of that, but needs to be the very latest. I'll find a link for you.
Also, do you have TWRP installed and did you have a backup you can restore?

ChazzMatt said:
Before this trouble, were you ever on stock Marshmallow 6.0.1? If so, you can flash back to full firmware of that, but needs to be the very latest. I'll find a link for you.
Also, do you have TWRP installed and did you have a backup you can restore?
Click to expand...
Click to collapse
Yes before this problem I was in the latest 6.0.1 and the stock I have here when I installed had a security update

ChazzMatt said:
Before this trouble, were you ever on stock Marshmallow 6.0.1? If so, you can flash back to full firmware of that, but needs to be the very latest. I'll find a link for you.
Also, do you have TWRP installed and did you have a backup you can restore?
Click to expand...
Click to collapse
I do not have twrp backup and I can not even install the recovery stock

kenedi jr said:
Yes before this problem I was in the latest 6.0.1 and the stock I have here when I installed had a security update
Click to expand...
Click to collapse
OK, then that's the bootloader you were on and will always be on. You need to reflash that latest version (with the security update) to repair. Just reflash the entire full firmware.
There's a link to it here in this forum. I'll find it when I get home, if you don't have it.
Then in the future, if you try to downgrade, you always have to flash full stock version EXCEPT you omit the gpt.bin file. Whether 4.4.4 Kitkat or 5.0.2 Lollipop.
And you can never take OTA.
Because you really have 6.0.1 bootloader.

ChazzMatt said:
OK, then that's the bootloader you were on and will always be on. You need to reflash that version to repair. Just reflash the entire full firmware.
Click to expand...
Click to collapse
This is the most likely because all the methods say so old and not one was and when I try to pass any old stock also will not always get that error in the bootloader in the gptbin downgrade logs

ChazzMatt said:
OK, then that's the bootloader you were on and will always be on. You need to reflash that latest version (with the security update) to repair. Just reflash the entire full firmware.
There's a link to it here in this forum. I'll find it when I get home, if you don't have it.
Then in the future, if you try to downgrade, you always have to flash full stock version EXCEPT you omit the gpt.bin file. Whether 4.4.4 Kitkat or 5.0.2 Lollipop.
And you can never take OTA.
Because you really have 6.0.1 bootloader.
Click to expand...
Click to collapse
thanks bro you saved me

kenedi jr said:
This is the most likely because all the methods say so old and not one was and when I try to pass any old stock also will not always get that error in the bootloader in the gptbin downgrade logs
Click to expand...
Click to collapse
You can not flash any older gpt.bin files. You have to omit (leave out) that flash command.
Your gpt.bin file is 6.0.1, and you cannot downgrade. Even on 4.4.4, trying to accept the 5.0.2 OTA update is still older gpt.bin file in that OTA than your 6.0.1.

ChazzMatt said:
OK, then that's the bootloader you were on and will always be on. You need to reflash that latest version (with the security update) to repair. Just reflash the entire full firmware.
There's a link to it here in this forum. I'll find it when I get home, if you don't have it.
Then in the future, if you try to downgrade, you always have to flash full stock version EXCEPT you omit the gpt.bin file. Whether 4.4.4 Kitkat or 5.0.2 Lollipop.
And you can never take OTA.
Because you really have 6.0.1 bootloader.
Click to expand...
Click to collapse
i don't have link .. i will wanting you so

kenedi jr said:
i don't have link .. i will wanting you so
Click to expand...
Click to collapse
https://forum.xda-developers.com/showthread.php?p=72846593

ChazzMatt said:
https://forum.xda-developers.com/showthread.php?p=72846593
Click to expand...
Click to collapse
I was a bit confused with this link which is the last one? I discovered because I am Brazilian and my English was developed only by playing

http://ftpeil.eil.com.br/vip/motoro...S24.107-70.2-7_cid12_subsidy-DEFAULT_CFC.xml/

ChazzMatt said:
http://ftpeil.eil.com.br/vip/motoro...S24.107-70.2-7_cid12_subsidy-DEFAULT_CFC.xml/
Click to expand...
Click to collapse
Face first you're a myth. I just passed gpt.bin and got the bootloader ... I'm very happy. Do I need to pass the entire rom ??
:good::laugh:

Question: If I update to the newest firmware, will I lose root?

Just got a alert to update firmware. Will I lose Root if I Update?
Thanks...

you can't install it if you are rooted, you have to unroot and install stock recovery no twrp for it to work.
it might also lock your bootloader meaning factory reset again to unlock.

jefffisher said:
you can't install it if you are rooted, you have to unroot and install stock recovery no twrp for it to work.
it might also lock your bootloader meaning factory reset again to unlock.
Click to expand...
Click to collapse
Not necessarily. I have an FRD-L04, I was running unlocked bootloader with TWRP and Magisk, rooted on B385. Flashed just the stock b360 recovery through fastboot, and then downloaded the full update package in the updater.
When it booted back up after the update, my bootloader had been locked. I uninstalled Magisk once I got back into Android. All seems to be working so far (except for my finicky SD card reader).

Install stock recovery and proceed with update.
You wont lose root

I lost root and got a locked bootloader since the new update (B394)

zimmen said:
I lost root and got a locked bootloader since the new update (B394)
Click to expand...
Click to collapse
It was GB update or MBs?
Can root again

shashank1320 said:
It was GB update or MBs?
Can root again
Click to expand...
Click to collapse
It was the GB
I downloaded the full package, only way to update for me.

zimmen said:
It was the GB
I downloaded the full package, only way to update for me.
Click to expand...
Click to collapse
Oops then it will restore the recovery, lock the bootloader, remove root

shashank1320 said:
Oops then it will restore the recovery, lock the bootloader, remove root
Click to expand...
Click to collapse
Yes, but that was the only way to get the update to install.
Not that I loos so much when I unlock it again, it's only apps they i have to install again.

Has anybody tried to flash magisk in the new B394? I get an "Process error" when trying to install/download modules
Update: just be sure to create a folder in internal storage named MagiskManager