Android Q beta for the 3a - Google Pixel 3a Guides, News, & Discussion

You can find the download for the Android Q beta here

When I go to the beta page, it says I don't have an eligible device. I have a 3a and PH-1. So is there a workaround/fix for this (besides flashing the ota myself)? Thanks.

cjbr0wn said:
When I go to the beta page, it says I don't have an eligible device. I have a 3a and PH-1. So is there a workaround/fix for this (besides flashing the ota myself)? Thanks.
Click to expand...
Click to collapse
You have to flash the image manually. OTA Android Q beta for Pixel 3a won't happen until June.

dhoang said:
You have to flash the image manually. OTA Android Q beta for Pixel 3a won't happen until June.
Click to expand...
Click to collapse
Oh, didn't know that. Thanks

Is this rootable yet? Any insight?
Sent from my Pixel 3a using Tapatalk

jmtjr278 said:
Is this rootable yet? Any insight?
Sent from my Pixel 3a using Tapatalk
Click to expand...
Click to collapse
No maybe in 1-2 months. Check out the magisk threads for details.

It seems the ROM can't be downloaded anymore, can it?

frandavid100 said:
It seems the ROM can't be downloaded anymore, can it?
Click to expand...
Click to collapse
All is OK.
https://dl.google.com/developers/an...ry/sargo-qpp3.190404.015-factory-29c0085a.zip

Okay, so... I downloaded this and tried to flash it, but fastboot tells me it can't flash system.img because there's no space left in the device, and quits. And then I get an unbootable phone
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Also, if I try to extract the zip file and then flash system.img manually, I get this:
Do you guys know how to fix this?

Ok, I fixed it. I had to install each file inside the zip manually, using the latest fastboot.
I was using an older one before, and that's why I got the error in the second screenshot.

I have same problem. Isnt the latest fastboot included in the canary channel Android sdk tools? I see the new fastbootd on the phone display during the fail of a flash-all procedure, but never attempted to find where the new fastboot file is located and try a manual flash of the failed file.

You can also grab the OTA image (and not the factory image) and boot into recovery and do ADB Sideload. That works fine as well.

Although the Android Version is 10, it still gives me the Pie animation after tapping on the version. Is this normal?

lordvoldemort said:
Although the Android Version is 10, it still gives me the Pie animation after tapping on the version. Is this normal?
Click to expand...
Click to collapse
Yep, of course.

Displax said:
Yep, of course.
Click to expand...
Click to collapse
Gotcha! And may I know the reason why? Afaik it is because google hasn't come up with a name for it
Sent from my SM-G973U1 using Tapatalk

dhoang said:
You have to flash the image manually. OTA Android Q beta for Pixel 3a won't happen until June.
Click to expand...
Click to collapse
uhh i definitely got the beta OTA both on 3a and 3a XL

laylovj said:
uhh i definitely got the beta OTA both on 3a and 3a XL
Click to expand...
Click to collapse
So you are on Android Q beta atm? How did you enroll in beta to receive OTA? I tried to enroll but my 3a is not eligible yet.

dhoang said:
So you are on Android Q beta atm? How did you enroll in beta to receive OTA? I tried to enroll but my 3a is not eligible yet.
Click to expand...
Click to collapse
what the that's strange it's not showing up right now that the 3a is eligible. however, I got the phone the day it came out and it had the option for the 3a when it did and I immediately signed up so I guess technically, yea? I don't really know how to prove this but I don't really have a reason to lie lol. Who knows maybe I have to re sign up later?

Here is a link to the Android Q Beta system images
https://developer.android.com/preview/download.html
engMTW said:
You can also grab the OTA image (and not the factory image) and boot into recovery and do ADB Sideload. That works fine as well.
Click to expand...
Click to collapse
Where are y'all finding the Android Q Beta OTA images?

Don't use the full Factory image, as a lot of people are taking advantage of carrier specific promotions, most of these devices cannot yet be OEM Unlocked until they are SIM unlocked. So you will not be able to install the Factory Image unless that condition is met.
You can Sideload the OTA.
As most of you know if you try to enroll your 3A device into the Preview Program, it will not show up and will see that Google is preventing them until June. However you can still install the official build directly from Google now which includes the May 5th, 2019 Security Patch.
Keep in mind you will be installing Beta software on your device and doing so at your own risk.
I will be writing this guide in the perspective for someone who has never installed a custom rom or used ADB before on a PC.
Ensure your device is setup and you can access the home screen.
Swipe down from the top to access the settings menu.
Scroll down to and click "About Phone."
Scroll to "Build Number", tap on it 6 times in a row until it says developer options enabled.
Click back in the setting menu.
Click on "System"
Click the "Advanced" Dropdown.
Click "Developer Options"
Scroll down to "USB Debugging" and enable it, accept the warning.
Download the "SDK Platform Tools" from here: https://developer.android.com/studio/releases/platform-tools.html
Unzip them to a folder on your desktop.
Download the latest "Full OTA Image" from here: https://developer.android.com/preview/download-ota
Pixel 3A: sargo-ota-qpp3.190404.015-dde326a4.zip
Pixel 3A XL: bonito-ota-qpp3.190404.015-d4e9922f.zip
Move that ZIP file into the Platform Tools folder on your desktop, do not unzip it.
Connect your Pixel to your PC via the USB A to C cable, the driver should automatically install.
A popup will appear on your pixel to grant debugging access to the connected computer, allow it.
Open the "Platform Tools" folder on your desktop, click the file explorer bar where it says "This PC>..." and type "CMD" and click enter, it will open the command prompt with access to that folder.
Enter the following command
Code:
adb reboot recovery
The phone will reboot, when it goes to a screen with the android mascot and exclamation mark hold the power button and click volume up this will access the recovery menu.
Select "Apply update from ADB." and hit the power button to choose it.
Enter this command into command prompt on the PC
Pixel 3A:
Code:
adb sideload sargo-ota-qpp3.190404.015-dde326a4.zip
Pixel 3A XL:
Code:
adb sideload bonito-ota-qpp3.190404.015-d4e9922f.zip
It will take a couple minutes, once done hit "Reboot System Now"
Congratulations, you are now on the official Android Q Beta 3 software for Pixel 3A!

Related

[How to] The dummies guide to unlocking the bootloader and rooting the R800x

Hope I'm not stepping on any toes, but here goes.
Are you these guys?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
but you want to be these guys?
Okay, so you've read Mills' instructions and sort of understand them.
1. Download the CWM recovery from multiupload
2. Boot off of that file (DO NOT FLASH): fastboot boot recoveryPLAY.img
3. Copy this to your memory card and flash it with the booted recovery
4. Reboot and test root
Click to expand...
Click to collapse
Right? Okay, let me translate all that for you.
First things first, you need to unlock your bootloader. To do so
Mills00013 said:
Obtain a bootloader unlock code. Right now the only way to get one is through ashergray or myself. This will change soon but for now its limited in release.
Once you have your code, follow the unlock instructions on either Sony's website directly or by following the instructions here. Please note that you already have your code at this point so if you follow the instructions please disregard anything telling you to obtain a code. These are for GSM models.
Click to expand...
Click to collapse
So kindly ask one of them for your unlock code, and my best suggestion would be to get everything ready so you can unlock the bootloader and flash the booted recovery all in one go.
So download the recoveryPLAY.img and set it aside.
Then download the RootXperia.zip and set it on your SD card in the root directory. So in the main F:\ folder.
Download the drivers and fastboot.exe here http://www.multiupload.com/RS6367SQMT
Okay, we got everything. Follow these instructions http://www.theandroidsoul.com/how-to-unlock-bootloader-xperia-arc-play-neo-pro/ starting at step 6 but please read my notes below also
at step 7, you will hold down the SEARCH button and plug the USB cable into your phone.
When you go to look for the Driver in Step 10 of the guide look for the one on the list that says "Android Bootloader Interface 2.0.10.2 Google, Inc. c:\?????\oem28.inf", that's the one I used.
Once the drivers installed you can locate fastboot and run it, but do this in the command prompt. So you know, go to Start > Run..> type in "cmd" and your command prompt comes up. Type in "cd\" to get to your root directory, then type in "cd c:\documents and settings\.....whateverfolder you have fastboot.exe sitting in"
So Step 13 of the guide, you're in the ...\fastboot\ folder, you can now type in fastboot.exe -i 0x0fce getvar version and that will tell you if you're connected. If you get a <waiting for device> you probably loaded the wrong driver. </life>
If not, then you got the 0.3, so continue with unlocking your bootloader in step 15. Put in your command and the key you got from some really helpful people.
Okay, so you just unlocked the bootloader, awesome. Don't close any windows. Now remember that "recoveryPLAY.img" we set aside? Go get it and move it into the same folder that you have fastboot.exe in.
# Boot off of that file (DO NOT FLASH): fastboot boot recoveryPLAY.img
Click to expand...
Click to collapse
Okay, with your command prompt still open and your recoveryPLAY.img in the same folder as fastboot.exe, type in "fastboot.exe boot recoveryplay.img"
Copy this to your memory card and flash it with the booted recovery
Click to expand...
Click to collapse
In about 10 seconds the screen on your phone will change, you will now see the recovery screen on your PLAY. The volume buttons are UP and DOWN, the power button is ENTER or SELECT. So navigate through the menus to install .zip from SD card, and look for the RootXperia.zip (we put it on your SD card earlier remember?). So you found it, Select it, it will run, the phone will tell you life is great, so scroll up to the top and back out until you see the option to reboot your phone.
Reboot and test root
Click to expand...
Click to collapse
Select Reboot and once you come up, go to the Android market and download something that requires Root, such as Titanium Backup or ROM Manager.
Finally, thank everyone involved for making this happen. Here http://forum.xda-developers.com/showthread.php?t=1098131
I did this on Windows XP, so I'm not sure if everything is exactly the same for any other Windows OS. Mods, feel free to move, delete or what you please with this thread.
Thanks a lot!!
Sent from my R800i using XDA App
Oh, my, gosh! THANK YOU SO MUCH! You don't know how much this means to me!
Thanks 4 dummie guide for noob people like me!!!!!
“S1Boot Fastboot” under the head “Other devices” i dont have that in my device manager
i cant seem to find "Android Bootloader Interface 2.0.10.2 Google, Inc. c:\?????\oem28.inf"
either...
my device manager says:
Android ADB interface under Android Phone
and
PCI input Device under "Other Devices"
To find s1 boot, you need the BLUE LED on
Sent from my Xperia PLAY R800i using XDA App
yea, i know
blue led light is still on
Thank you very very much for this simple and easy to follow guide. I have a very basic knowledge of all of this and many of the guides posted required I fill in gaps I didn't know how to fill.
Thank you!
Android ADB interface under properties says 2.0.10.2 Google
but i tried to update it with the folder and it said it was up to date....
In the cmd windows type in fastboot.exe -i 0x0fce getvar version
If a value is returned, it means the phone is correctly connected
Sent from my Xperia PLAY R800i using XDA App
dont know wtf i was doing but it finally connected to the phone, bootloader unlocked! just installed rootxperia.zip file bout to see what happens next.
hmm
i hit the power button (select) to reboot system but nothing happens. just momentarily turns screen off and on. i cant select anything now... stuck in clockworkmod recovery app
should i just unplug battery and replug?
KGB920 said:
hmm
i hit the power button (select) to reboot system but nothing happens. just momentarily turns screen off and on. i cant select anything now... stuck in clockworkmod recovery app
should i just unplug battery and replug?
Click to expand...
Click to collapse
to clarifie things - the search button is [select] on the play
FYI, the original method for obtaining unlock codes from Ashergray or Mills has been blocked by Sony. Now, the only way to unlock has to be done through Allejandrissimo, and costs money.
A free solution is being worked on, but we are nearly back to square one as far as unlocking goes.
crono141 said:
FYI, the original method for obtaining unlock codes from Ashergray or Mills has been blocked by Sony. Now, the only way to unlock has to be done through Allejandrissimo, and costs money.
A free solution is being worked on, but we are nearly back to square one as far as unlocking goes.
Click to expand...
Click to collapse
how much money?
because I'm getting so tired of running out of space every time I download an app
Halfway down the page Androhero has a (non-rooted) way to free up space (it works, I have anout 100 apps with 100mbs free)
http://forum.xda-developers.com/showthread.php?t=1194570
Sent from my R800x using XDA App
Bump for helpfullness and newbie R800X'ers.
does this still work?
thirday_95 said:
does this still work?
Click to expand...
Click to collapse
No.
tq mates, such info

OTA "JLS36C" - Now for Nexus 7 LTE

Hey guys.
I just wanted to inform you that new update for Nexus 7 is out.
Unfortunately I was not able to catch the ota link.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Gesendet von meinem Nexus 7 mit Tapatalk 4
i uploaded it here
be careful
This update disabled TWRP and broke root on my tablet.
Does not update my deb....
Sent from my Nexus 4 using XDA Premium 4 mobile app
I received the update OTA on my rooted (deb) N7/2, booted to TWRP and flashed the .zip, that is in /cache. Update runs fine. I didn't use the recovery option to fix SU permissions.
Just rebooted to OS, went to recovery and flashed the SU.zip afterwards.
Root and TWRP are working fine.
I received the update too and installed it via twrp.
All went fine exept for root. I just had to install chainfires root package (1.55) again.
is it a sign to get a factory image in a short time?
noonecanhide said:
Does not update my deb....
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
might wanna install the deb version of twrp...
OTA URL > http://android.clients.google.com/p...signed-razorg-JLS36C-from-JSS15J.7003a71d.zip
Thanks to kendong2 for the file name.
Does the update solve the following touchscreen problem: the tablet lies on a table and the screen does not recognize your tabs...
Elting said:
Does the update solve the following touchscreen problem: the tablet lies on a table and the screen does not recognize your tabs...
Click to expand...
Click to collapse
You have touchscreen problems on a LTE version? I don't have any problems on my LTE version with 08.2013 build date.
If the update is for fixing touchscreen problems, then I'm not sure if I should update...
No, I have the FLO but I think, that FLO will get this update, too... sooner or later...
poisike said:
OTA URL > http://android.clients.google.com/p...signed-razorg-JLS36C-from-JSS15J.7003a71d.zip
Click to expand...
Click to collapse
Slightly OT here, but since it might still be useful for future OTA updates: How does one catch/find out the OTA URL of an update? I understand that the update itself gets downloaded to /cache and there you can find the filename, but what about the URL?
dasmanul said:
Slightly OT here, but since it might still be useful for future OTA updates: How does one catch/find out the OTA URL of an update? I understand that the update itself gets downloaded to /cache and there you can find the filename, but what about the URL?
Click to expand...
Click to collapse
simplest way is a proxy in your wifi network, which handles all http/https requests for the phone/tablet.
dasmanul said:
Slightly OT here, but since it might still be useful for future OTA updates: How does one catch/find out the OTA URL of an update? I understand that the update itself gets downloaded to /cache and there you can find the filename, but what about the URL?
Click to expand...
Click to collapse
If you know the update file name then it's easy. Address is android.clients.google.com/packages/ota/google_devicecodename/filename so in our case android.clients.google.com/packages/ota/google_razorg/filename
if i am not mistaken the url is also visible in logcat.
So just to make sure I`m getting this right, I have a rooted DEB with TWRP installed:
1. Flash the zip from recovery
2. Flash SuperSU.zip
3. Reboot
4. Done
Or is a reboot needed in between between steps 1. and 2.? Does anyone have a working link to the SuperSU files needed (thanks in advance!).
Jacktheskipper said:
So just to make sure I`m getting this right, I have a rooted DEB with TWRP installed:
1. Flash the zip from recovery
2. Flash SuperSU.zip
3. Reboot
4. Done
Or is a reboot needed in between between steps 1. and 2.? Does anyone have a working link to the SuperSU files needed (thanks in advance!).
Click to expand...
Click to collapse
No need to reboot between 1&2, at least not on the wifi model.
http://download.chainfire.eu/346/SuperSU/UPDATE-SuperSU-v1.55.zip
sfhub said:
No need to reboot between 1&2, at least not on the wifi model.
http://download.chainfire.eu/346/SuperSU/UPDATE-SuperSU-v1.55.zip
Click to expand...
Click to collapse
Thanks for the quick reply and the direct link!
Hope this goes down without trouble, will give it a try later! :good:
xdacinq said:
simplest way is a proxy in your wifi network, which handles all http/https requests for the phone/tablet.
Click to expand...
Click to collapse
Even more simple is:
1) just allow a USB developer mode in the settings (no root needed)
2) fire up your ubuntu linux
3) run adb lolcat | grep http in the terminal
and take a look for something like
I/SystemUpdateService( 3997): starting download of hxxp://android.clients.google.com/packages/ota/google_razorg/...

b390 available for PLK-L01 (EU).

Hey there, just a heads up for you guys.
If you check on Firmware Finder app, you will find a new firmware available, there's both an OTA incremental update (around 220mb) and the full 1.6gb package.
Personally I went with the latter, forced the update (volume up+down + power on buttton), and the installation went on smoothly and flawlessly.
Now the device is on EMUI 4.0.3, always MM of course, but the security patch is now April 2017
about time!! :good:
anyway the change log was pretty short, basically just a bunch of enhancements to a few apps like mail, calendar... you can find it on Firmware Finder as well.
I have a new function: "Eyesight protection" in the Settings.
Although the schedule doesn't seem to work...
Edit: yesterday evening it has turned on automatically... not sure why, but it's working now
Installation error here on both update and full.
One of promised Nougat features...
One small hint, I cannot update via UPDATE.APP file so i updated it with fastboot with full package and huawei extractor.
Also SuperSU V2.62 doesn't work, but SuperSU v2.79 works, and recovery image is TWP v3.1.0.0.
Well, for me, with update.app, it says that it does install and it goes all the way with "success" but after restart nothing changes, it's still B380.
Hello.
How can I update my Honor 7? I'm stuck on B371 version. Update feature in settings app says "No updates".
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download Firmware Finder, click on refresh button and you will get list with updates,download latest, put on sdcard into dload folder and then turn off the phone, press volume + and volume - at the same time and turn on phone, you will get update wizzard and update will start.
And when you download zip, unzip it to have update.app file and other files will be there, all that put in dload on sdcard, if there is no dload folder, make it.
Sent from my PLK-L01 using Tapatalk
It went for me successfully (B380->B390) but i had to unpack full package and it went from update.app after rebooting with vol up+vol down+power. Same didn't work with update.app from OTA update pack (small one) and also didn't work with update.zip files (it tried but failed).
So, long story short - it worked only with update.app (moved to dload folder on sdcard) taken from full package zip.
And it was not worth waiting and updating as changes are so small that it hurts that it took them 6 months. They could at least enable multi window that is available on Honor 7 in other regions...
lakistrike95 said:
Download Firmware Finder, click on refresh button and you will get list with updates,download latest, put on sdcard into dload folder and then turn off the phone, press volume + and volume - at the same time and turn on phone, you will get update wizzard and update will start.
And when you download zip, unzip it to have update.app file and other files will be there, all that put in dload on sdcard, if there is no dload folder, make it.
Sent from my PLK-L01 using Tapatalk
Click to expand...
Click to collapse
Thanks! It worked.
supervixen said:
It went for me successfully (B380->B390) but i had to unpack full package and it went from update.app after rebooting with vol up+vol down+power. Same didn't work with update.app from OTA update pack (small one) and also didn't work with update.zip files (it tried but failed).
So, long story short - it worked only with update.app (moved to dload folder on sdcard) taken from full package zip.
And it was not worth waiting and updating as changes are so small that it hurts that it took them 6 months. They could at least enable multi window that is available on Honor 7 in other regions...
Click to expand...
Click to collapse
yes... I guess the only reason for this update was providing us with the latest security patch... which I'm thankful for.
but this should tell us quite clearly that we don't need to expect much from the future. like we thought, development for this phone is over.
It was all over the moment they couldn't tell us straight in the face that we won't get Nougat/EMUI5. I remember exactly how they (in mails from support) were trying to deal with that... Some said we will get updated, some said we will not. There was also an interview where some official was saying that even if some devices will not get EMUI5 users should not worry as EMUI4 will be still developed and get some features (we got now eye protecting filter which is like u fist in the face - we could get that thing long time ago as there are tons of apps doing same thing). Sure, there was EMUI4.1 (it featured a better organized camera app) but not for us. I agree, it's just a security patch, we have to live with all problems specific to EMUI4.0.x until we get new devices. Hopefully not from Huawei and Honor.
anyone have full ROM link?
thermalboyz said:
anyone have full ROM link?
Click to expand...
Click to collapse
I have on my MEGA files:
B390 full rom
Thanks @kac222
Sent from my PLK-L01 using Tapatalk
.
Yes, v2.79 and twrp 3.1.0.0
.
redzieu said:
Thanks! It worked.
Click to expand...
Click to collapse
not worked for me
Martin213 said:
And that Eye comfort feature available from B386,so nothing​ new for me I dont use App twin feature but that are on B388 too,did they implement on B390?
Click to expand...
Click to collapse
As for eyes comfort - third party apps were killed from memory but that's biggest issue with EMUI and they didn't fixed it so having this feature built in might be useful. However, as someone already stated, you can set on and off hours for the filter but it doesn't work. It works only while being manually switched. What's the point of adding broken feature after 6 months after last update?
As for app twin feature - are you talking about split screen? There never was such option in PLK-L01C432 and they didn't add it with B390 (there was no B382, 386 and 388 for us, just B380 and now B390).

EASY UNLOCK AND 8.1 Developer Preview Install

First of all, thanks Deuces and Northmendo for the idea to help people.
I have created a pretty easy all in one that will install the lasted adb and fastboot system wide and fastboot flash unlock and unlock_critical. It will install the latest 8.1 developer preview for the Pixel 2 XL for you as well with all the necessary files included. I did not inlcude the lock and lock_critical function as most do not use it.
As the instructions state, please use a usb 2.0 port and and usb-c to usb-a cable that supports data. Also enabling debugging and oem unlock is a must.
It includes a menu driven batch file that is super easy to use.
For those that want to use this same batch file on the pixel 2 itself, please extract the zip from google and then extract the zip within the zip. Next pull the bootloader and radio img file from the root of the zip to the FILES folder included in this program. Then copy all the contents from the zip within the zip to the same FILES folder. It should contain about 22 files in total. We really don't need the android-info.txt file.
I will also be including a batch file with a semi empty FILES folder that does not include any Google related 8.1 files for those that want to download it quicker and copy their own contents to it for flashing. Like Pixel 2 owners that already have the 8.1 preview downloaded.
If anyone needs any help please feel free to ask. This post was rushed so please excuse my grammatical errors.
FOR PIXEL 2 and PIXEL???? ----NO IMG's inlcuded
http://www.mediafire.com/file/eksn04aiaeqvvia/PXEL_2_&_PIXEL_SAUCE_NO-IMGS.zip
FOR PIXEL 2 XL ---- IMG's included
http://www.mediafire.com/file/1wde39mj7ssbxb3/PIXEL_2_XL_SAUCE_V1.zip
Oh btw. In the credits they are listed as well as their profile page.
Forgot to mention your phone needs to be in the bootloader. Duh!
Sent from my Nexus 6 using Tapatalk
Great tool bro, thank you.
samteeee said:
Great tool bro, thank you.
Click to expand...
Click to collapse
No problem. I'll prolly update it to lock the bootloader and have some useful adb commands.
Sent from my Nexus 6 using Tapatalk
so we need unlock_critical
which they said we need only for non signed bootloader
did google not signed the bootloader img by mistake
or this is intentional for dev previews
You can install the Dev 8.1 ROM without unlocking though. Just go to Android's site and enroll your phone in the beta program like you would an iPhone, and it just sends it to you as an OTA and installs it without wiping or unlocking your phone...
abogrhen said:
so we need unlock_critical
which they said we need only for non signed bootloader
did google not signed the bootloader img by mistake
or this is intentional for dev previews
Click to expand...
Click to collapse
Not sure but it could be as it is a manual flash. Have you tried stock 8.0 flash with critical locked?
Sent from my Nexus 6 using Tapatalk
bryantjopplin said:
Not sure but it could be as it is a manual flash. Have you tried stock 8.0 flash with critical locked?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
i did not receved my pixel 2 yet
still using my nexus 6
but i will try first
I'm having issues flashing this. I ran the .bat file but when I choose "Flash All", I can get to this final screen where it says "THERE IS NO GOING BACK. PRESS ANY KEY TO CONTINUE" except nothing happens when I hit any key. Is this happening for anyone else?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Huawei Updater & HiSuite to update Mate 9 to Oreo?

I found this here:
Method 2 – Update Mate 9 to EMUI 8.0 using HiSuite
1) First you need to download two files.
Download Huawei Updater 2.0 – Download
Download Huawei HiSuite Tool – Download
2) Run Huawei Updater, check the box “Custom ROM” and “Custom Port”
3) In Custom ROM enter the correct ROM version for flashing [for example: MHA-L29 8.0.0.321 (C432log)]
4) In Custom ROM enter correct ROM URL (For example: http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1819/g1699/v100248/f1)
5) Now click on “Start” button and accept waiting alert messages.
6) Now connect your phone to HiSuite. Make sure device recognized by HiSuite and connected properly.
7) In HiSuite windows, open Settings –> General –> Custom Proxy and configure below changes –
Address: 127.0.0.1
Port: 41279
8) Go back to main HiSuite windows and click on “System update”
9) Press Update and wait for download firmware.
10) Your device will reboot and start upgrading.
Click to expand...
Click to collapse
But 127.0.0.1 gives a "no internet connection" error and 192.168.1.1 (from ipconfig) times out also with an error.
Is this a legitimate way of updating? If so why the errors?
i try update and no internet conection too
and, after says the device no have update, my rom is 8.0.0.321 (C432log), BUT have in FF a new 321C432log day 27 and no update
pardus said:
I found this here:
But 127.0.0.1 gives a "no internet connection" error and 192.168.1.1 (from ipconfig) times out also with an error.
Is this a legitimate way of updating? If so why the errors?
Click to expand...
Click to collapse
I'm getting no errors, it downloads it all and reboots to recovery. But since I have TWRP it doesn't get past that.
I will backup everything and try a full install.
I wonder if anyone got that second method working and if you need UBL for that.
ante0 said:
I'm getting no errors, it downloads it all and reboots to recovery. But since I have TWRP it doesn't get past that.
I will backup everything and try a full install.
Click to expand...
Click to collapse
Are you using 127.0.0.1? And what ROM and address in Huawei Updater?
My current version is MHA-L09C900B186 unlocked international version so I've used "MHA-L09 8.0.0.324(C900)" and "http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1819/g1699/v99803/f1" gathered from the PC version of Firmware Finder but no luck, 127.0.0.1 just gives no internet connection error.
pardus said:
Are you using 127.0.0.1? And what ROM and address in Huawei Updater?
My current version is MHA-L09C900B186 unlocked international version so I've used "MHA-L09 8.0.0.324(C900)" and "http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1819/g1699/v99803/f1" gathered from the PC version of Firmware Finder but no luck, 127.0.0.1 just gives no internet connection error.
Click to expand...
Click to collapse
Tested with the same as you now:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Edit: You get internet connection errors if the URL you input is wrong.
Edit 2: It doesn't matter, it needs to authenticate anyway.
ante0 said:
Edit: You get internet connection errors if the URL you input is wrong.
Click to expand...
Click to collapse
Weird, I used exactly this: "http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1819/g1699/v99803/f1"
pardus said:
Weird, I used exactly this: "http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1819/g1699/v99803/f1"
Click to expand...
Click to collapse
It fails in recovery anyway, so doesn't matter much.
ante0 said:
It fails in recovery anyway, so doesn't matter much.
Click to expand...
Click to collapse
I'm stock though, no TWRP so it might work.
ante0 said:
It fails in recovery anyway, so doesn't matter much.
Click to expand...
Click to collapse
Install patched recovery from Hwota first, then try again.
Every update goes through following steps:
Initiate update
Download
Authorization
Install
This method with Huawei Updater replaces first step. But you are right, that authorization blocks installation.
pardus said:
I'm stock though, no TWRP so it might work.
Click to expand...
Click to collapse
Try to use previous HiSuite 5.0.1.300. It does not work with the current HiSuite version 5.0.1.301
jogefo said:
Try to use previous HiSuite 5.0.1.300. It does not work with the current HiSuite version 5.0.1.301
Click to expand...
Click to collapse
Thanks, got a link perhaps? I can't seem to find the older version.
Edit: Nevermind, I think I got it.
Edit 2: Nope, not working, v5.0.1.300 doesn't recognize my device.
I tried this method.. failed everytime.
Ended up unlocking bootloader and using Hwota method to flash and install ROM.. i had to rebrand my device to europe for it to work, else was stuck on boot loop.. Luckly managed to resolve
pardus said:
Thanks, got a link perhaps? I can't seem to find the older version.
Edit: Nevermind, I think I got it.
Edit 2: Nope, not working, v5.0.1.300 doesn't recognize my device.
Click to expand...
Click to collapse
Try turning on Usb debugging in dev options.
Did you guys try THIS method?
https://www.androidblog.gs/how-to-update-huawei-mate-9-to-android-8-0-oreo-official-firmware/
ante0 said:
Try turning on Usb debugging in dev options.
Click to expand...
Click to collapse
Thanks, yeah, it's on, as is "Allow HiSuite to use HDB", still no luck.
mad.nexus said:
Did you guys try THIS method?
https://www.androidblog.gs/how-to-update-huawei-mate-9-to-android-8-0-oreo-official-firmware/
Click to expand...
Click to collapse
Yes, one of the steps is: "Next, navigate to the Settings app and go into Update option. Press the menu key and chose Local update."
I have no "Local update", will follow up further though.
pardus said:
Yes, one of the steps is: "Next, navigate to the Settings app and go into Update option. Press the menu key and chose Local update."
I have no "Local update", will follow up further though.
Click to expand...
Click to collapse
same here, no such "Local update"
Press the menu key and chose Local update.
Click to expand...
Click to collapse
FFS! Can't find it either? Can anyone talk to that guy from the blog? :/
mad.nexus said:
FFS! Can't find it either? Can anyone talk to that guy from the blog? :/
Click to expand...
Click to collapse
Maybe we should try this
Now on your phone, Open the dialer and call ->enter: *#*#2846579#*#* ->ProjectMenu->Software Upgrade->SDCard Upgrade->OK,
Click to expand...
Click to collapse
Ps. To initiate update, dload has to be in SD card directory. Yet Software update fails with url to emui.com/...

Categories

Resources