Database Users

[Firmware] Flashable JSS15R 3,15 Bootloader&Firmware update

For those of us who are rooted, don't want to update parts of the OS, who want to stay on an older versions of updated OS files, or just are on a custom ROM, here is a flashable of the firmware updates (which include bootloader).
This updates your bootloader to version 3.15.

Freeza, you rule... Just saying
Sent from my Nexus 7 using Tapatalk 4

Nice work!
Quick question for you, will the bootloader and firmware updates persist after custom ROM updates or will I need to reflash each time?
for example, I'm running CarbonRom at the moment which is based on JSS15Q - I've flashed this zip without any problems but will I need to reflash it when I install the next nightly?
Cheers
Macca

It will persist. No need to reflash.

sfhub said:
It will persist. No need to reflash.
Click to expand...
Click to collapse
Cheers, that's what I thought but there was no harm in checking

BigMacca said:
Cheers, that's what I thought but there was no harm in checking
Click to expand...
Click to collapse
I should be more clear, in the example you gave, it will persist, but if you do something that will flash the bootloader like factory restore or its updates, the bootloader could change

sfhub said:
I should be more clear, in the example you gave, it will persist, but if you do something that will flash the bootloader like factory restore or its updates, the bootloader could change
Click to expand...
Click to collapse
Yeah, I should have been clearer as well - I was basically checking that custom roms don't flash the bootloader (I'd assumed that a factory restore / ota update would)

Nice to see ya here Freeza!
I am currently on [JSS15Q] - CleanROM 1.6 I am wondering if this would work with my current rom as a dirty flash? anyone tired while on CleanRom 1.6?

DC_MTP said:
Nice to see ya here Freeza!
I am currently on [JSS15Q] - CleanROM 1.6 I am wondering if this would work with my current rom as a dirty flash? anyone tired while on CleanRom 1.6?
Click to expand...
Click to collapse
No problems here DC.
D

everything seems to be going well (using FLO Kangs cm10.2 Sep 5 build) will update if anything bad happens

Does firmware mean the audio driver, sensor driver, wifi driver etc?

bland.life said:
Does firmware mean the audio driver, sensor driver, wifi driver etc?
Click to expand...
Click to collapse
No, it means bootloader, resource power manager, trusted zone.

Quick queastion , I was on JSS15J when stock, flashed ROM that says now JLS36C. If I flash this will it erase everything and do I even need to? Thanks for the help.

It won't erase any user data. Whether you want to flash is up to you. You'll get it automatically if you wait for jls36g ota.

Why is the 3.15 bootloader not available as .img file in the google recovery as always? I normally flash bootloader ONLY by using fastboot?!

Awesome!
I flashed this and my dead gold fish came back to life!
You're the man, OP!

freeza said:
For those of us who are rooted, don't want to update parts of the OS, who want to stay on an older versions of updated OS files, or just are on a custom ROM, here is a flashable of the firmware updates (which include bootloader).
This updates your bootloader to version 3.15.
Click to expand...
Click to collapse
Will this work on stock? I can't get the ota to install.

Still JSS15Q after flashing?
freeza said:
For those of us who are rooted, don't want to update parts of the OS, who want to stay on an older versions of updated OS files, or just are on a custom ROM, here is a flashable of the firmware updates (which include bootloader).
This updates your bootloader to version 3.15.
Click to expand...
Click to collapse
After successful flashing this zip-file on my rooted JSS15Q version with TWRP the Android version is still JSS15Q. That's right? I expected JSS15R.
Greetings
Zorro16

relaxxer said:
Why is the 3.15 bootloader not available as .img file in the google recovery as always? I normally flash bootloader ONLY by using fastboot?!
Click to expand...
Click to collapse
If you want the 3.15 bootloader .img to flash in fastboot, I added it to the download section of this thread:
http://forum.xda-developers.com/showthread.php?t=2448015

Zorro16 said:
After successful flashing this zip-file on my rooted JSS15Q version with TWRP the Android version is still JSS15Q. That's right? I expected JSS15R.
Greetings
Zorro16
Click to expand...
Click to collapse
This is just the bootloader that came with 15R. If you want 15R, download and flash the full rom package.
Sent from my Nexus 7 using XDA Premium 4 mobile app

Gear live update 5.0.2

I have the gear live and twrp. My watch got a notification that said that the update was downloaded and to update. When I start the update, my watch rebooted into twrp. I keep getting an error and the update doesn't install. Does anyone else have this problem, and know how to solve this issue?

I have the same problem, the watch becomes verry hot but I can't complete the update.
I am waiting for a solution. Other whise I have to visit a Samsung service point tomorrow.

Which version of twrp you guys have? I didn't got this error but I was unsuccessfully trying to install the 5.1.1 update trough modified zip I had lots of error that basically were stating that my watch was a different model and I suspect it could be due to last TWRP version. Still to confirm.
I solved using the recovery from tool here in forum to put the stock 4.4w image and did the updates OTA (the last 5.1.1 update was with sideload through original recovery butnI guess if i waited a few days it would be done OTA)
Sent from my SM-G920F using Tapatalk

han ree said:
I have the same problem, the watch becomes verry hot but I can't complete the update.
I am waiting for a solution. Other whise I have to visit a Samsung service point tomorrow.
Click to expand...
Click to collapse
Yea, I have a similar problem. Whenever I try to install using automatic update, it just fails with "something went wrong. Try again?".
insaned said:
Which version of twrp you guys have? I didn't got this error but I was unsuccessfully trying to install the 5.1.1 update trough modified zip I had lots of error that basically were stating that my watch was a different model and I suspect it could be due to last TWRP version. Still to confirm.
I solved using the recovery from tool here in forum to put the stock 4.4w image and did the updates OTA (the last 5.1.1 update was with sideload through original recovery butnI guess if i waited a few days it would be done OTA)
Sent from my SM-G920F using Tapatalk
Click to expand...
Click to collapse
Hmm so, that backup file I gave you didn't work for you? Could please check something on your watch for me please. I need to know what stock recovery build you have.Mine is stuck on the older version no matter what update I install. Thanks.

aligatro2010 said:
Yea, I have a similar problem. Whenever I try to install using automatic update, it just fails with "something went wrong. Try again?".
Hmm so, that backup file I gave you didn't work for you? Could please check something on your watch for me please. I need to know what stock recovery build you have.Mine is stuck on the older version no matter what update I install. Thanks.
Click to expand...
Click to collapse
Unfortunately no and thanks for yiur patience, I posted on the other thread.. I got so fed up that I flashed a stock image. And went from there since beginning and did it via sideload!
I used the gear live restore tool that is here from tomsgt if i remeber.i did all updates with everything stock . But after update to 5.1.1 i flashed again twrp (but not the latest version this time) and rooted the phone. I'm on travel until Tuesday and i didn't even brought watch. So incan check out ont Tuesday anything you need.
Sent from my SM-G920F using Tapatalk

insaned said:
Unfortunately no and thanks for yiur patience, I posted on the other thread.. I got so fed up that I flashed a stock image. And went from there since beginning and did it via sideload!
Sent from my SM-G920F using Tapatalk
Click to expand...
Click to collapse
Oh I didn't see that message. Did you install stock image from Samsung Gear Live Restore Tool v2? Thats the one I flashed and ota fails no matter what. Can you check if you stock recovery was updated when you did OTA update? It says the build name when you boot into it from bootloader. (where you did the sideloading)

aligatro2010 said:
Oh I didn't see that message. Did you install stock image from Samsung Gear Live Restore Tool v2? Thats the one I flashed and ota fails no matter what. Can you check if you stock recovery was updated when you did OTA update? It says the build name when you boot into it from bootloader. (where you did the sideloading)
Click to expand...
Click to collapse
Yup, I flashed full stock image and waited for 2 OTA updates until 5.0.2 and then sideloaded the original 5.1.1 in the original recovery, however I dunnl if this 2 first OTA have updated recovery too..
I can't check much right now because the watch is not with me until Tuesday, if even after twrp flash I did after the 5.1.1 update is still mentioned the original there in bootloader I will let you know as soon as I arrive on Tuesday.
Sent from my SM-G920F using Tapatalk

insaned said:
Yup, I flashed full stock image and waited for 2 OTA updates until 5.0.2 and then sideloaded the original 5.1.1 in the original recovery, however I dunnl if this 2 first OTA have updated recovery too..
I can't check much right now because the watch is not with me until Tuesday, if even after twrp flash I did after the 5.1.1 update is still mentioned the original there in bootloader I will let you know as soon as I arrive on Tuesday.
Sent from my SM-G920F using Tapatalk
Click to expand...
Click to collapse
Oh alright.

Can't Multirom with Android N DP4 !

Hello !
I'm actually on PureNexus (primary rom) and i installed multirom.
I tried to add DP4 rom (as secondary rom) 2 times:
- first time with the all-in-one zip file -> the phone is stuck on Google logo
- second time with a backup of DP4 that i've made earlier -> the phone is also stuck on Google logo
maybe i've missed something... Can someone help me ?

Raiden350 said:
Hello !
I'm actually on PureNexus (primary rom) and i installed multirom.
I tried to add DP4 rom (as secondary rom) 2 times:
- first time with the all-in-one zip file -> the phone is stuck on Google logo
- second time with a backup of DP4 that i've made earlier -> the phone is also stuck on Google logo
maybe i've missed something... Can someone help me ?
Click to expand...
Click to collapse
I learned through casual reading of the Multirom thread that developer previews must be flashed to primary then moved to secondary
Sent from my Nexus 5X using Tapatalk

Ok, i did it, i reflash Android N factory image, then Multirom and i add PureNexus as secondary rom.
Now Android N rom is booting fine, but it's PureNexus which is stuck at Google logo... Also tried with Uberstock rom, same result.
I don't understand why the secondary rom never boot...

Raiden350 said:
Ok, i did it, i reflash Android N factory image, then Multirom and i add PureNexus as secondary rom.
Now Android N rom is booting fine, but it's PureNexus which is stuck at Google logo... Also tried with Uberstock rom, same result.
I don't understand why the secondary rom never boot...
Click to expand...
Click to collapse
You must flash the Marshmallow Vendor that matches your Marshmallow roms before booting them. Have you been doing so? You must also flash the Android N vendor before booting into developer previews.
Sent from my Nexus 5X using Tapatalk

SlimSnoopOS said:
You must flash the Marshmallow Vendor that matches your Marshmallow roms before booting them. Have you been doing so? You must also flash the Android N vendor before booting into developer previews.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
No i don't... Okay, so if I flash marshmallow vendor, it will be fine ? Or i have to flash MM vendor each time i want to boot in this rom ??

Raiden350 said:
No i don't... Okay, so if I flash marshmallow vendor, it will be fine ? Or i have to flash MM vendor each time i want to boot in this rom ??
Click to expand...
Click to collapse
Yes it should. Each time you switch between MM and N, you must flash the Vendor that matches that MM or N rom. You don't have to do this between MM roms
Sent from my Nexus 5X using Tapatalk

SlimSnoopOS said:
Yes it should. Each time you switch between MM and N, you must flash the Vendor that matches that MM or N rom. You don't have to do this between MM roms
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Oh really ? So annoying But thanks a lot for your help !

Raiden350 said:
Oh really ? So annoying But thanks a lot for your help !
Click to expand...
Click to collapse
Lol yes it is but it's only a slight annoyance since you can flash the vendor.img while in TWRP or MR-TWRP as well before booting up. I do encourage you to follow the MultiRom thread just to be aware of subtleties like this
http://forum.xda-developers.com/showthread.php?t=3313291
Sent from my Nexus 5X using Tapatalk

Stock firmware for Moto g4+ XT1643

Hello all,
I am having the phone XT1643 with Build MPJ24.139-23.1 . I want to install stock recovery and firmware. I have gone through the links in other thread for downloads but all those are providing for other builds. I have seen for builds MPJ24.139-13.1, MPJ24.139-13.3 and MPJ24.139-63.
So, should I proceed with other builds or should I search for build with MPJ24.139-23.1?? Also, which one should I use and will I be able to update further using OTA updates??
Note: I am having TWRP at present, also my phone is showing OTA update with build MPJ24.139-63
Thanks in advance.

You have already provided the answer with your question. Your phone shows you an ota. You are already running the 23.1 build most probably. Check from Settings->About phone-> Build number.
Note that you have to be non rooted and have stock recovery to flash the ota successfully.
Sent from my Moto G4 Plus using Tapatalk

Sorry to say, but please read my query once again. I know my build number. Also, I am having TWRP but not rooted and it is showing OTA update. That's why I want to install stock recovery.
Silesh.Nair said:
You have already provided the answer with your question. Your phone shows you an ota. You are already running the 23.1 build most probably. Check from Settings->About phone-> Build number.
Note that you have to be non rooted and have stock recovery to flash the ota successfully.
Sent from my Moto G4 Plus using Tapatalk
Click to expand...
Click to collapse

ankit.hinsu said:
Hello all,
I want to install stock recovery and firmware. I have gone through the links in other thread for downloads but all those are providing for other builds. I have seen for builds MPJ24.139-13.1, MPJ24.139-13.3 and MPJ24.139-63.
So, should I proceed with other builds or should I search for build with MPJ24.139-23.1??
Click to expand...
Click to collapse
Look at your thead title "stock-firmware-moto-g4-xt1643".
Well, if you only wanted the stock recovery, what was this info about? Additional info is not useful info if it's irrelevant.
I was under the impression that you were looking for the ota zip file.
Wouldn't a simple " can someone provide me the stock recovery from the 23.1 build of xt1643" been enough?
Anyways, you can download it from the link below.
http://cloud.tapatalk.com/s/580de287223ae/recovery.img.zip
Sent from my Moto G4 Plus using Tapatalk

Thanks Silesh,
I have downloaded it. But while I was flashing it using fastboot, it showed "Image is not signed or Corrupt".
However, TWRP is also gone.
Is it normal?
Silesh.Nair said:
Look at your thead title "stock-firmware-moto-g4-xt1643".
Well, if you only wanted the stock recovery, what was this info about? Additional info is not useful info if it's irrelevant.
I was under the impression that you were looking for the ota zip file.
Wouldn't a simple " can someone provide me the stock recovery from the 23.1 build of xt1643" been enough?
Anyways, you can download it from the link below.
http://cloud.tapatalk.com/s/580de287223ae/recovery.img.zip
Sent from my Moto G4 Plus using Tapatalk
Click to expand...
Click to collapse

That's OK. Its just a warning. If it says OKAY, you are good to go.
Obviously you won't have twrp. You just replaced twrp with the stock recovery.
Sent from my Moto G4 Plus using Tapatalk

OTA Updates on a custom setup?

Hello,
I have a rooted Nexus 6P with the Stock Android ROM, Nougat 7.1.1 (NMF26O), NetHunter kernel, TWRP and some features of Pixel XL flashed (Pixel launcher, Google Assistant, Dynamic Navigation bar, Black Bootanimation etc.).
Can I keep my phone up to date with Google's OTA updates? If yes, how? Will it ruin my setup?
Thank you in advance,
Elias

The OTA update will not flash .
If u want/need OTA updates to work you need to be stock.
Sent from my Pixel XL using Tapatalk

i am fully stock ,, only rooted ,, tried to flash January update and it failed .
how can i flash the update ????
phone : nexus 6p
version 7.1.1

hwoarang626 said:
i am fully stock ,, only rooted ,, tried to flash January update and it failed .
how can i flash the update ????
phone : nexus 6p
version 7.1.1
Click to expand...
Click to collapse
Update manually using fastboot. Follow section 9 of the guide below:
https://forum.xda-developers.com/showthread.php?t=3206928
Sent from my Nexus 5X using Tapatalk

hwoarang626 said:
i am fully stock ,, only rooted ,, tried to flash January update and it failed .
how can i flash the update ????
phone : nexus 6p
version 7.1.1
Click to expand...
Click to collapse
You can also update via FlashFire if you are rooted with SuperSu. It unroots your phone, restores standard recovery, flashes OTA, restores custom recovery and restores root. All automatically.

thank you so much , i tried with flashfire but for some reason it does not detect my OTA

hwoarang626 said:
thank you so much , i tried with flashfire but for some reason it does not detect my OTA
Click to expand...
Click to collapse
If you don't know where the OTA is you can download it from the Google images website. Then you will be able to locate it easily. But I don't know what's going to happen with your mods. They might need to be reinstalled.

Thanks for the info guys.