Hello,
Where is the OFFICIAL (Google, Android, Motorola, etc) factory Android image for these devices? I do not want to install somebody's version, I want the factory image with SHA/MD5 hash to verify. Where can this be found?
Thanks,
Seattle3D said:
Hello,
Where is the OFFICIAL (Google, Android, Motorola, etc) factory Android image for these devices? I do not want to install somebody's version, I want the factory image with SHA/MD5 hash to verify. Where can this be found?
Thanks,
Click to expand...
Click to collapse
Here is the link to firmware jelly bean to kitkat: https://www.androidfilehost.com/?a=show&w=files&flid=44742
Related
Has any one got, or could make, a fully signed GPE Rom?
Not yet.
Surely the official GPE Firmware image (KOT49H.M004) here is signed:
http://sbf.droid-developers.org/phone.php?device=14
lost101 said:
Surely the official GPE Firmware image (KOT49H.M004) here is signed:
http://sbf.droid-developers.org/phone.php?device=14
Click to expand...
Click to collapse
Many have problems with that on non gpe. I don't think it is signed.
denzel09 said:
Many have problems with that on non gpe. I don't think it is signed.
Click to expand...
Click to collapse
I haven't been following the flashing thread, but I had no issues flashing it on a XT1032 non-GPE GB handset.
lost101 said:
I haven't been following the flashing thread, but I had no issues flashing it on a XT1032 non-GPE GB handset.
Click to expand...
Click to collapse
No no buddy, i am talking to relock bootloader. I think for this he asked about signed.
lost101 said:
Surely the official GPE Firmware image (KOT49H.M004) here is signed:
http://sbf.droid-developers.org/phone.php?device=14
Click to expand...
Click to collapse
I have a stock 4.4.2 ROM which using mfastboot will install with no errors or warnings.
the KOT49H.M004 ROM has several warnings and one system image is stated to be unsigned.
robin0800 said:
I have a stock 4.4.2 ROM which using mfastboot will install with no errors or warnings.
the KOT49H.M004 ROM has several warnings and one system image is stated to be unsigned.
Click to expand...
Click to collapse
I'm more inclined to believe the errors arise from flashing the official GPE firmware onto a non-GPE device. KOT49H.M004 came from a Motorola / Google server, it's not just hacked together.
lost101 said:
I'm more inclined to believe the errors arise from flashing the official GPE firmware onto a non-GPE device. KOT49H.M004 came from a Motorola / Google server, it's not just hacked together.
Click to expand...
Click to collapse
Would it be logical to assume the GPe stock rom can only be flashed onto an XT1032 ? I would like to go the other way, from GPe to the Motorola version, so I can try out some roms. ANyone try this?
I bought a GPe because I thought there would be more custom than the Motorola... turns out the opposite is true. For now, at least.
lost101 said:
I'm more inclined to believe the errors arise from flashing the official GPE firmware onto a non-GPE device. KOT49H.M004 came from a Motorola / Google server, it's not just hacked together.
Click to expand...
Click to collapse
Its on sbf-droid and is supposedly a leaked firmware from Motorola. It is not officially released by Motorola and does not come from a Motorola or Google server.
It could contain alterations if one of the system images is not signed.
scott_doyland said:
Its on sbf-droid and is supposedly a leaked firmware from Motorola. It is not officially released by Motorola and does not come from a Motorola or Google server.
It could contain alterations if one of the system images is not signed.
Click to expand...
Click to collapse
It's hard to say anything for sure. I only said what I did because of this comment from a 'Firmware Team' member:
I use Filefactory because I can remotely upload files to my account directly from Motorola's servers using Filefactory's bandwidth, which is considerably faster than I can upload from my PC.
Click to expand...
Click to collapse
[source]
EDIT:
These are original and official source files from Motorola's server.
Click to expand...
Click to collapse
[source]
@dgauze, try flashing this and let us know: (Before flashing, replace the recovery file included with a custom one (i.e CWM Advanced))
Android 4.4.2 - Blur_Version.172.44.4.falcon_umts.Retail.en.US
US_retail_XT1032_KXB20.9-1.8-1.4_CFC.xml.zip
http://sbf.droid-developers.org/phone.php?device=14
Also perhaps to be extra safe, delete or don't flash the motoboot.img included. Maybe you should start a new thread on this.
Hi all,
I know that AOSP is Android Open Source Project.
So, when TWRP says that version 2.8.6.1 includes a "Update AOSP base to 5.1", what does it exactly mean?
Does it mean that the device OS will be upgraed to Android 5.1 ?
BTW, I ask it here just because I have N5...
Thank you
dushkin said:
Hi all,
I know that AOSP is Android Open Source Project.
So, when TWRP says that version 2.8.6.1 includes a "Update AOSP base to 5.1", what does it exactly mean?
Does it mean that the device OS will be upgraed to Android 5.1 ?
BTW, I ask it here just because I have N5...
Thank you
Click to expand...
Click to collapse
No, it doesn't mean that.
So,
1. Can you explain to me please what does it mean exactly?
2. TWRP does not let me install the OTA upgrade to 5.1. how can I overcome that?
Thank you!!
dushkin said:
So,
1. Can you explain to me please what does it mean exactly?
2. TWRP does not let me install the OTA upgrade to 5.1. how can I overcome that?
Thank you!!
Click to expand...
Click to collapse
It means that TWRP base has been updated to Android 5.1. TWRP is based on the open source Android recovery, with each release of Android (4.4, 5.0, 5.1 etc) Google update everything to the new base. So currently everything in Googles repo is a 5.1 base. TWRP updates itself to the latest android recvoery base which is 5.1. It allows for the flashing of latest ROMs, bug fixes and any new features (although in Google stock recovery, new features are very rare)
To update to 5.1 you will need to flash an unoffcial stock version in the development secion or you can grab the OTA zip and 'adb sideload' it.
Thank you Matt
1. Can you just point me to the place where I can select the files to flash?
2. Which one would you recomment me to use?
3. Can I flash them with TWRP?
Many thanks!
dushkin said:
So,
2. TWRP does not let me install the OTA upgrade to 5.1. how can I overcome that?
Thank you!!
Click to expand...
Click to collapse
What's the exact error when installing OTA on TWRP, please.
dushkin said:
Thank you Matt
1. Can you just point me to the place where I can select the files to flash?
2. Which one would you recomment me to use?
3. Can I flash them with TWRP?
Many thanks!
Click to expand...
Click to collapse
You cant apply ota updates above 5.x.x with twrp. Use stock recovery instead.
It is not an error. Aftert the upgrade is downloaded it reboots into the TWRP screen and there I do not know what to do.
So, I simply choose to reboot into system from there, and thus, there is no upgrade.
dushkin said:
It is not an error. Aftert the upgrade is downloaded it reboots into the TWRP screen and there I do not know what to do.
So, I simply choose to reboot into system from there, and thus, there is no upgrade.
Click to expand...
Click to collapse
Oh, so it's exactly like @bitdomo said, and I quote, "You cant apply ota updates above 5.x.x with twrp. Use stock recovery instead."
Tried to re-flash my factory boot image to my Pixel 2, and am now stuck in bootloader. I cannot find my old factory image anymore and need help. Please let me know what I can do. I already downloaded the newest platform tools, but still nothing. Here is what I can see on my phone right now.
Are or were you on the latest software and trying to flash the latest?
Stuck
enzyne said:
Are or were you on the latest software and trying to flash the latest?
Click to expand...
Click to collapse
I was on android version 8.0.0, and I tried flashing the factory 8.0.0, but no luck. now I'm just trying to figure out what to do.
solved
FoolishMove said:
I was on android version 8.0.0, and I tried flashing the factory 8.0.0, but no luck. now I'm just trying to figure out what to do.
Click to expand...
Click to collapse
Finally figured it out, just downloaded the wrong factory software. Got the right one, did the flash all and it worked.
Hello! I'm looking for the original firmware: is it possible to download that? I have the 4G version of Huawei Watch 2.
shishimaru1000 said:
Hello! I'm looking for the original firmware: is it possible to download that? I have the 4G version of Huawei Watch 2.
Click to expand...
Click to collapse
it depends on which version of watch you got.
If You have LEO-DLXX you can use firmware from this reddit post ( i used it on my watch which is LEO-DLXX)
https://www.reddit.com/r/WearOS/comments/9lnwu4/for_those_wanting_to_force_the_new_ui_on_the_hw2/
If You have another varsion of Watch You can check this post, but if you flash wrong firmware you will brick your watch:
https://forum.xda-developers.com/watch-2/development/rom-huawei-watch-2-4g-l-09s-global-t3602205
Thank you! I can see the one with TWRP and the kernels. It's the only way to flash it?
I was looking for the older firmware, the one with Android Wear before it became Wear OS.
shishimaru1000 said:
Thank you! I can see the one with TWRP and the kernels. It's the only way to flash it?
I was looking for the older firmware, the one with Android Wear before it became Wear OS.
Click to expand...
Click to collapse
I flashed it manually, without twrp.,
I had previousli opened bootloader,
i had extracted the archive and manualy flashed it using fastboot, after that, I re-locked bootloader (fastboot oem lock) and device boot fine.
I also did not found older firmware.
I recently unlocked the bootloader on my pixel. It has 8.1 on it and I want to update it to 9.0. Can I flash the regular factory Pie image or do I have to flash the Verizon variant? Full image or OTA?
Also, I'm assuming all OTAs will fail to install once the bootloader is unlocked?
Thanks.
If you're going from stock ROM to stock ROM, you can install the OTA, regardless of bootloader being unlocked. I think it's easier to install the OTA, and there's no risk of losing data. The OTA is also a smaller download than the full factory image.
Only install the Verizon variant of the ROM if you have the Verizon Pixel. Do not mix ROM variants.
All OTA Images
All Full Factory Images
post-mortem said:
If you're going from stock ROM to stock ROM, you can install the OTA, regardless of bootloader being unlocked. I think it's easier to install the OTA, and there's no risk of losing data. The OTA is also a smaller download than the full factory image.
Only install the Verizon variant of the ROM if you have the Verizon Pixel. Do not mix ROM variants.
All OTA Images
All Full Factory Images
Click to expand...
Click to collapse
You know there is no such thing as verizon specified ROMs on Pixel forum ryt??. Unless it is project treble he can flash any sailfish rom
---------- Post added at 02:00 AM ---------- Previous post was at 01:42 AM ----------
rumi409 said:
I recently unlocked the bootloader on my pixel. It has 8.1 on it and I want to update it to 9.0. Can I flash the regular factory Pie image or do I have to flash the Verizon variant? Full image or OTA?
Also, I'm assuming all OTAs will fail to install once the bootloader is unlocked?
Thanks.
Click to expand...
Click to collapse
I do have a unlocked Verizon pixel. You have two options
1. update via OTA (if you haven't installed TWRP or Magisk yet)
2. Go to google factory images> download latest full factory images file. Last I remember there is no Verizon specified one, so I downloaded latest one and works fine.
crazykas said:
You know there is no such thing as verizon specified ROMs on Pixel forum ryt??. Unless it is project treble he can flash any sailfish rom
Click to expand...
Click to collapse
Hmmm... as the OP is specifically talking about Stock Firmwares I'm wondering why - if, as you're affirming, Verizon-specific ones don't exist - Google is listing Verizon-specific stock firmwares on that page : https://developers.google.com/android/images#sailfish
Could you please enlighten me?
bafforosso said:
Hmmm... as the OP is specifically talking about Stock Firmwares I'm wondering why - if, as you're affirming, Verizon-specific ones don't exist - Google is listing Verizon-specific stock firmwares on that page : https://developers.google.com/android/images#sailfish
Could you please enlighten me?
Click to expand...
Click to collapse
Yes this one is the latest android P which also for verzion model as for others 9.0.0 (PPR2.181005.003, Oct 2018). FYI: i have verzion model and i flashed those
crazykas said:
Yes this one is the latest android P which also for verzion model as for others 9.0.0 (PPR2.181005.003, Oct 2018). FYI: i have verzion model and i flashed those
Click to expand...
Click to collapse
Are you saying you flashed the PPR2.181005.003, Oct 2018 build on your unlocked Verizon pixel without issues?
Also, when you sideload an OTA using TWRP, does it overwrite the recovery partition?
Thanks.
rumi409 said:
Also, when you sideload an OTA using TWRP, does it overwrite the recovery partition?
Click to expand...
Click to collapse
These phones don't have a recovery partition. When you "boot to recovery," it actually loads a portion of the boot.img file, which is part of any ROM flash. When you "install" TWRP, the installer actually patches the boot.img file. This means you can recover from a bad flash by using fastboot to flash the stock boot.img file. Get the boot.img from the full stock image or custom ROM, and flash it in bootloader mode with fastboot flash boot boot.img
rumi409 said:
Are you saying you flashed the PPR2.181005.003, Oct 2018 build on your unlocked Verizon pixel without issues?
Also, when you sideload an OTA using TWRP, does it overwrite the recovery partition?
Thanks.
Click to expand...
Click to collapse
1. Yes. Flashed PPR2.181005.003, Oct 2018 on my unlokced verzion without issues. FYI: read this post , this also applicable for non-xl (sailfish) https://forum.xda-developers.com/showpost.php?p=71822255&postcount=13
2. No. As i repeated before, i was on stock ROM (8.1) and fupdate to 9.0 via system OTA. FYI. sideload won't work TWRP, you must do it on stock recovery
crazykas said:
1. Yes. Flashed PPR2.181005.003, Oct 2018 on my unlokced verzion without issues. FYI: read this post , this also applicable for non-xl (sailfish) https://forum.xda-developers.com/showpost.php?p=71822255&postcount=13
2. No. As i repeated before, i was on stock ROM (8.1) and fupdate to 9.0 via system OTA. FYI. sideload won't work TWRP, you must do it on stock recovery
Click to expand...
Click to collapse
Got it. Thanks.