Related
Official updates for our M2 tablet,
although having installed another
recovery and root access, already.
- Disclaimer
Well, whatever you do with this guide is all up to you and in your own responsibility. You
should have basic knowledge about ADB and flashing, which is explained in many other
threads here on our beloved XDA.
- Issue
When you used this guide (https://goo.gl/r04XjJ) or any other one to give your M2 tablet
another recovery and therefore root rights, you have now the problem, that EMUI will show
you new updates, but you are not able to install them, because of the missing stock recovery,
of course.
- Solution
So, you have to flash back the original stock recovery, getting the official update and then you
can flash back your TWRP recovery.
- Guide
1. You should start your EMUI update programme/app and start the download of your update.
When it is finished, it will ask you to reboot into recovery and install automatically. As you have
no stock recovery I strongly advise not to do so. Usually nothing happens, but there is one case
reported, where it somehow ****ed up the guy's tablet. I am not sure, if that story is true, but
well, I have warned you.
2. Just turn your tablet off after you have finished downloading the update (it will wait now in
the directory "HwOUC" on your tablet and it is called "update.zip" - just let it sleep there).
3. Start the tablet in the fastboot recovery mode, meaning plugging in the USB cable (connected
to the computer) and hold the buttons "power" and "volume down", immediately, until a white
screen appears, which is the fastboot recovery screen. It should tell you, it has the bootloader
unlocked, which is normal, because you did that earlier on with any of the other guides (see above).
4. Copy the downloaded stock recovery of your choice to your ADB directory. In my case this is
"c:\ADB", but this depends on your way of installation.
5. Now open up a command line in Windows (with Windows key + R) and type "cmd") and go to
your ADB directory, using commands like "cd .." and "cd adb".
6. When having arrived in the ADB directory, you have to enter these commands one after the other:
fastboot flash recovery stock-recovery.img
fastboot reboot
If you renamed the recovery file, then you have to consider that in the command, of course.
7. The device will reboot directly into the recovery, because it "sees" the update in the update
directory et voila ... you are getting your awaited update. Sometimes it will boot not into the EMUI
recovery directly, but then you hast have to start the tablet normally, open up the EMUI app and
download the update again and do the OTA update properly with the reboot it tells you to do,
when it is finished.
8. Okay, now you have received your update, but if you want to have back your TWRP, you just
have to turn off your tablet and boot into the fastboot recovery again (see 3.).
9. You have to copy your TWRP recovery to your ADB directory (in my case "twrp.img" in "c:\ADB").
10. Now open up a command line in Windows (with Windows key + R and type "cmd") and go to
your ADB directory, using commands like "cd .." and "cd adb".
11. When having arrived in the ADB directory, you have to enter these commands one after the other:
fastboot flash recovery twrp.img
fastboot reboot
12. The tablet will reboot and you are back to a working lovely updated M2 tablet.
- Root:
If you want to have root rights, I strongly recommend flashing Magisk within TWRP, because it is
just a nice and more modern approach to having root. It works very fine on my M2 10 tablet. The
link for the files and guide is here:
https://goo.gl/UXYk4d
It is very easy. You just flash Magisk 12 in TWRP and then install the Magisk Manager app from the
Play store.
- Files for M2-802L and M2-A01L:
https://ufile.io/0df492 (all four recoveries here)
https://files.fm/u/aajdmadr (all four recoveries here)
https://www.file-upload.net/download-12438839/HuaweiM2recoveries.rar.html (all four recoveries here)
Have fun with your updated tablet. ... and I am happy, if I could help you - any coffee appreciated.
...
..
.
+++ saved +++
Additionally, I can offer you the updates B007 and B010 (most current one) for the
M2 10 LTE (M2-A01L), because I managed to save them/back them up. These are the
European versions of B007 and B010 with all language files, I believe.
So, who is having a M2-A01L and is still sitting on B006 or B007, might try a manual
update, which is as easy as pie. It is just one simple step.
Also, an update from B009 to B010 might be possible.
Of course, I cannot give any guarantee for Huawei's update files, which you will
understand, I guess.
what android version ?? M2-801L, thanks
Eagle-no1 said:
what android version ?? M2-801L, thanks
Click to expand...
Click to collapse
M2-A01L, not M2-801L. For all 8 models you find your ROMs here:
https://forum.xda-developers.com/me...om-8-0-models-stock-marshmallow-roms-t3535466
or
https://forum.xda-developers.com/me...-b207-android-6-0-marshmallow-emui-4-t3533572
or
https://forum.xda-developers.com/mediapad-m2/development/rom-stock-rooted-xposed-t3519031
xsycox said:
Additionally, I can offer you the updates B007 and B010 (most current one) for the
M2 10 LTE (M2-A01L), because I managed to save them/back them up. These are the
European versions of B007 and B010 with all language files, I believe.
So, who is having a M2-A01L and is still sitting on B006 or B007, might try a manual
update, which is as easy as pie. It is just one simple step.
Also, an update from B009 to B010 might be possible.
Of course, I cannot give any guarantee for Huawei's update files, which you will
understand, I guess.
Click to expand...
Click to collapse
I'd greatly appreciate it, if you could share. Got the problem that my A-01L got corrupted. The only official ROM I've been able to find has been B005 what is somewhat old. As it seems to be a pre-release version the tablet doesn't find any updates. Thus I'd like to try to upgrade to B007, or even B010 manually when I'm back home. Currently I'm on a weekend trip as friends of mine are going to marry tomorrow. Thus I'd be able to download them on Sunday evening if you'd provide them.
Regards
Sent from my htc_pmeuhl using XDA Labs
Tried Magisk but can't pass Safetinet test even with Magisk hide enable...
is it working for you?
5m4r7ph0n36uru said:
I'd greatly appreciate it, if you could share. Got the problem that my A-01L got corrupted. The only official ROM I've been able to find has been B005 what is somewhat old. As it seems to be a pre-release version the tablet doesn't find any updates. Thus I'd like to try to upgrade to B007, or even B010 manually when I'm back home. Currently I'm on a weekend trip as friends of mine are going to marry tomorrow. Thus I'd be able to download them on Sunday evening if you'd provide them.
Regards
Click to expand...
Click to collapse
https://forum.xda-developers.com/me...om-official-manual-updates-m2-tablet-t3595211
zedoc said:
Tried Magisk but can't pass Safetinet test even with Magisk hide enable...
is it working for you?
Click to expand...
Click to collapse
I have Magisk running on several devices, including the M2-A01L, but I must admit,
I never got the Safetynet passed, even with Magisk hide enabled.
I just use it as systemless root and with systemless Xposed, which is great.
zedoc said:
Tried Magisk but can't pass Safetinet test even with Magisk hide enable...
is it working for you?
Click to expand...
Click to collapse
xsycox said:
I have Magisk running on several devices, including the M2-A01L, but I must admit,
I never got the Safetynet passed, even with Magisk hide enabled.
I just use it as systemless root and with systemless Xposed, which is great.
Click to expand...
Click to collapse
After enabling magisk hide, you have to reboot your device. Got the 801L working with that and safetynet passes.
Noob Question on recovery files
Hi, and thanks for a incredible well detailed guide for updating. Came here because I haven't found any good recovery files for the wifi model. I've been trying (unsuccessfully may I add...) to install TWRP and magisk. So, my question is: can the recovery files for the LTE model be used on the wifi model? (M2-A01w). Thanks for your help!
myst771 said:
Hi, and thanks for a incredible well detailed guide for updating. Came here because I haven't found any good recovery files for the wifi model. I've been trying (unsuccessfully may I add...) to install TWRP and magisk. So, my question is: can the recovery files for the LTE model be used on the wifi model? (M2-A01w). Thanks for your help!
Click to expand...
Click to collapse
Sorry, I have been on vacation.
To be honest, I am not sure, if the recovery for M2-A01L works on M2-A01w, too, but you can just try it.
I think, there should not be that big a problem, because the recovery has nothing to do with Wi-Fi or LTE, at all. It is just important, that partition tables and drives are accessible the same way and well, I really think, there is not much difference in between the M2 10 models.
From M2 8 to 10 there is a difference, of course. That is why I uploaded both recoveries (for 802L and A01L).
Just use that guide (https://forum.xda-developers.com/mediapad-m2/how-to/guide-unlock-bootlader-twrp-root-huawei-t3322340) without the SuperSU flashing and my recoveries in this guide.
Hi guys,
I need help, I have a M2 10 LTE previously modded with TWRP for root and I've just followed this guide to update from 007 to 010 version.
So I've flashed the stock-recovery, rebooted the tablet, requested the firmware update (I don't know if I got any error during the process) and the tablet has rebooted. Now it's stuck on HUAWEI logo..
I use this tablet for work so I really need to recover it asap.
Please help.
Shocker580 said:
Hi guys,
I need help, I have a M2 10 LTE previously modded with TWRP for root and I've just followed this guide to update from 007 to 010 version.
So I've flashed the stock-recovery, rebooted the tablet, requested the firmware update (I don't know if I got any error during the process) and the tablet has rebooted. Now it's stuck on HUAWEI logo..
I use this tablet for work so I really need to recover it asap.
Please help.
Click to expand...
Click to collapse
Could upload the B010 fullstock ROM/firmware. Thus you could reset the device to the latest stock ROM using the /dload method and gain a factory rested Huawei, as if out of the box. Just quote me if you'd want me to upload and I'll share the link asap. Took that way myself as soon as I found the full stock ROM.
Sent from my htc_ocnuhl using XDA Labs
thanx
Dear xsycox
I have an issue where I updated my W version tablet to L version accidentally and I am having issue getting it back..
I am currently trying to get some help in this thread: https://forum.xda-developers.com/me...-m2-installed-wrong-update-zip-t3563105/page2
Can you please help me out? do you have any idea what ican do to get back to W version?
Thanks!
I have this device, but right now I am unable to root and twrp it because of warranty but I really want to build a ROM for it and we have the sources so I really want to do it. Any beta testers would be frickin amazing.
So, building asteroids and syncing with latest sources and also trying to fix bluetooth is my main goal here.
First test build is complete! Link: [urlhttp://www.mediafire.com/?0c0xusva0z5e0[/url]
That is the link to a folder containing 2 files, an ext4 file and a fastboot file.
To flash it, make sure your bootloader is unlocked
This will only dual boot the software, because it is just a test and in case it'd mess anything up, it won't affect the watch.
Once you've downloaded the files and put them into your adb and fastboot folder, enable adb debugging (obviously huehuehue).
Once that is all done, don't switch off your watch, leave it in android wear and make sure that adb detects it (adb devices and it should say authorized next to it).
Run adb push -p /location/to/file/asteroid-image-tetra.ext4 /sdcard/linux/rootfs.ext4 (pushes the file to the virtual sdcard)
Once that is done, reboot to bootloader by running adb reboot bootloader.
Then, once you've sure made that fastboot recognizes it (fastboot devices), do fastboot boot /location/to/zImage-dtb-tetra.fastboot
If you want to try and overwrite your current android wear installation, do fastboot flash, however I don't recommend this.
Good luck! Oh, and as a sidenote, since this isn't android wear, the android wear app won't work and I am surprised that bluetooth even works (if it does, report it here!).
RAZERZDAHACKER said:
I have this device, but right now I am unable to root and twrp it because of warranty but I really want to build a ROM for it and we have the sources so I really want to do it. Any beta testers would be frickin amazing.
Please, either send me a pm or write here on this thread and I'll try to release a flashable zip asap
Click to expand...
Click to collapse
Hi
I'm always open for some beta testing. In what direction of development where you thinking? A themed stock, or something radical?
amunarjoh said:
Hi
I'm always open for some beta testing. In what direction of development where you thinking? A themed stock, or something radical?
Click to expand...
Click to collapse
Not themed stock, sure they're great for some people but I am not a huge fan of them so I will obviously not make one. Right now I am compiling resurrection remix for my phone but I might try later on and get a compiled version
RAZERZDAHACKER said:
I have this device, but right now I am unable to root and twrp it because of warranty but I really want to build a ROM for it and we have the sources so I really want to do it. Any beta testers would be frickin amazing.
Please, either send me a pm or write here on this thread and I'll try to release a flashable zip asap
Click to expand...
Click to collapse
I am willing to be a beta tester
Alright, stay tuned. Building rom right now, also getting instructions for how to flash it (I don't think it is a simple twrp flash, not sure, we need some tester to confirm that).
RAZERZDAHACKER said:
Not themed stock, sure they're great for some people but I am not a huge fan of them so I will obviously not make one. Right now I am compiling resurrection remix for my phone but I might try later on and get a compiled version
Click to expand...
Click to collapse
That sounds interesting. Looking forward to further development
Build finished after a couple of hours. Since I am new to this whole android wear thing, I am a bit confused as to which files to flash, but I assume it is the one that is the largest and has the correct file format, right? So here is where the beta tester thingy comes into place. I am still experimenting on flashing the rom (the flashing method can be a bit confusing for new people) so I am planning on coding a toolkit that does all of that for ya, but the main thing is that I use linux and I don't really have a windows machine available to test this and quickly be able to change some things in the code (or either the rom files and then pack em up) so if someone is willing to perhaps skype or something similar where they can test such things that would be amazing, since I don't believe that a lot of people are running linux and want to flash this particular rom for this particular device etc.
Enough ranting! Here comes the rom link! http://www.mediafire.com/?0c0xusva0z5e0
That is the link to a folder containing 2 files, an ext4 file and a fastboot file.
To flash it, make sure your bootloader is unlocked
This will only dual boot the software, because it is just a test and in case it'd mess anything up, it won't affect the watch.
Once you've downloaded the files and put them into your adb and fastboot folder, enable adb debugging (obviously huehuehue).
Once that is all done, don't switch off your watch, leave it in android wear and make sure that adb detects it (adb devices and it should say authorized next to it).
Run adb push -p /location/to/file/rootfs.ext4 /sdcard/linux/rootfs.ext4
Once that is done, reboot to bootloader by running adb reboot bootloader.
Then, once you've sure made that fastboot recognizes it (fastboot devices), do fastboot boot /location/to/file.fastboot.
If you want to try and overwrite your current android wear installation, do fastboot flash, however I don't recommend this.
Good luck! Oh, and as a sidenote, since this isn't android wear, the android wear app won't work and I am surprised that bluetooth even works (if it does, report it here!).
Doesn't boot for me get stuck at the Smartwatch 3 screen then reboots in to wear.
niai_mack said:
Doesn't boot for me get stuck at the Smartwatch 3 screen then reboots in to wear.
Click to expand...
Click to collapse
Thanks for trying, and you followed the instructions here I assume. I'll try to compile a new one today (I got some interesting warnings when compiling)
Aye I followed to the tea, put it in /sdcard/linux/ with the name rootfs.ext4 then booted with the supplied fastboot file.
You do know there's the official release from the dev of Asteroid OS that works without any issues (meaning it boots and functions as expected, minus the bugs), right? In case you didn't, here it is: https://asteroidos.org/install/
I get that you're trying to do something new, and I'm all for it. I'm just posting this here, in case anyone else was curious. It's been out for quite a while now, almost a year by my reckoning.
Bluetooth does not work though, blame Broadcom.
Some extra info. When you fastboot boot the kernel from Asteroid OS, it loads the system that you earlier pushed to your internal memory using adb. You can run the (barebones) OS till your next reboot. Once you reboot, you'll be taken back to Android Wear itself, and you have to reflash the kernel to go back to Asteroid.
niai_mack said:
Aye I followed to the tea, put it in /sdcard/linux/ with the name rootfs.ext4 then booted with the supplied fastboot file.
Click to expand...
Click to collapse
Can you perhaps try "adb push -p /location/to/file/rootfs.ext4 /sdcard/linux/rootfs.ext2" ? Thanks.
I can test as well
d_crossfader said:
I can test as well
Click to expand...
Click to collapse
Sweet, I assume you pretty much know what to do. Can you also test the above mentioned flashing method? So you're replacing the vritual sdcard with ext2 instead of 4.
drakonizer said:
You do know there's the official release from the dev of Asteroid OS that works without any issues (meaning it boots and functions as expected, minus the bugs), right? In case you didn't, here it is: https://asteroidos.org/install/
I get that you're trying to do something new, and I'm all for it. I'm just posting this here, in case anyone else was curious. It's been out for quite a while now, almost a year by my reckoning.
Bluetooth does not work though, blame Broadcom.
Some extra info. When you fastboot boot the kernel from Asteroid OS, it loads the system that you earlier pushed to your internal memory using adb. You can run the (barebones) OS till your next reboot. Once you reboot, you'll be taken back to Android Wear itself, and you have to reflash the kernel to go back to Asteroid.
Click to expand...
Click to collapse
Missed your reply. Correct, and I am aware of that. Just that I want to get into android wear development so I decided to build this from source and perhaps eliminate the bluetooth thing and maybe even have it as a permanent rom instead of android wear, just saying. It'd be pretty cool, though not the most practical thing ever.
RAZERZDAHACKER said:
Missed your reply. Correct, and I am aware of that. Just that I want to get into android wear development so I decided to build this from source and perhaps eliminate the bluetooth thing and maybe even have it as a permanent rom instead of android wear, just saying. It'd be pretty cool, though not the most practical thing ever.
Click to expand...
Click to collapse
Having it permanent is easy. All you'd have to do is fastboot flash the kernel as opposed to fastboot boot.
The Bluetooth thing is almost impossible to fix, it's due to the blobs from bcm. Unless you're proficient at reverse engineering complex code, it's pretty hard.
drakonizer said:
Having it permanent is easy. All you'd have to do is fastboot flash the kernel as opposed to fastboot boot.
The Bluetooth thing is almost impossible to fix, it's due to the blobs from bcm. Unless you're proficient at reverse engineering complex code, it's pretty hard.
Click to expand...
Click to collapse
I can always try :/
RAZERZDAHACKER said:
Sweet, I assume you pretty much know what to do. Can you also test the above mentioned flashing method? So you're replacing the vritual sdcard with ext2 instead of 4.
Click to expand...
Click to collapse
I can do the steps on the first page, not sure about replacing the virtual sd though
d_crossfader said:
I can do the steps on the first page, not sure about replacing the virtual sd though
Click to expand...
Click to collapse
What you're doing on the first page is basically moving the files and flashing them from the virtual sd card so all I ask is if it doesn't work to change the last number in the adb command from a 4 to a 2
RAZERZDAHACKER said:
What you're doing on the first page is basically moving the files and flashing them from the virtual sd card so all I ask is if it doesn't work to change the last number in the adb command from a 4 to a 2
Click to expand...
Click to collapse
cool, will try in a few
Hey guys.
Yesterday, I swapped out my Oneplus 6T, and got a new Pixel 3 XL 64GB.
I managed to have no issues unlocking the bootloader, and I do have relative familiarity with adb tools.
I'm running a Dell XPS 13 which has a USB Type C port which I have been using for cmd through Windows 10 in the beginning much to my own success.
After unlocking the bootloader, I had opt'd in for the ota update for Android Q and downloaded without hesitation.
I booted into TWRP, and when attempting to flash through the USB OTG cable it failed. I do not recall, and didn't think to use the webcam on my PC at the time to screenshot the errors.
I can get into the bootloader, however now when I run adb devices nothing appears.
If I boot a TWRP img, go to advanced > adb sideload and run a session. I can then proceed to run adb devices and successfully it reports back my serial number of the device. ( can provide screenshots of this if it's of any assistance )
However, no way have I been able to flash the Factory images, from as early as September 2018 to the latest for Android 9.0, nor have I have been able to reflash the Android Q factory images using cmd and the flash-all.bat
I've also followed this guide step by step uninstalling every ADB and Android related driver prior to installing the "lastest google drivers" https://forum.xda-developers.com/pixel-3-xl/how-to/guide-progress-available-t3876849/page6
Sending sparse 'vendor_a' 2/2 (193888 KB) FAILED (Error reading sparse file) is where it hangs, and I'm absolutely at a stand still I wouldn't be posting if I hadn't searched and tried everything I could find any way related to it.
Also seems to be missing multiple sig files when running the flash-all.
If anyone can be of assistance it would be greatly appreciated I do not want to have to RMA to Google.
Thanks guys!
You can not adb sideload an ota in TWRP. It has to be the factory recovery.
When you are in the bootloader you need to do fastboot devices to see your device.
Did you get Q running? If you did I would download the factory image for it and edit the flash-all.bat to remove the -w.
Also make sure you have the latest platform-tools. I think they got updated when Q came out.
I've never had a problem but I know a lot of people have problems with C to C cables. May want to try an A to C cable if you can.
hatdrc said:
You can not adb sideload an ota in TWRP. It has to be the factory recovery.
When you are in the bootloader you need to do fastboot devices to see your device.
Did you get Q running? If you did I would download the factory image for it and edit the flash-all.bat to remove the -w.
Also make sure you have the latest platform-tools. I think they got updated when Q came out.
I've never had a problem but I know a lot of people have problems with C to C cables. May want to try an A to C cable if you can.
Click to expand...
Click to collapse
Sadly, I can't get to a USB A to C cable for 6 more days.
I did manage to get to Q, and I don't know what rushed me to thinking I could be flashing twrp on the beta.
I have been using factory images, I haven't sideloaded with adb, as I can't quite seem to figure out the flashing process for TWRP. Is there a method you could recommend we try?
I have the latest tools, and I'm 99.9% positive in one of the 20+ flashes I tried Today of various factory images, flashing the last factory with Q did not solve the trick with or without the -w.
If you are trying to flash from within TWRP, make sure everything is properly mounted.
Sent from my Pixel 3 XL
I think your using an old android Windows platform tools.
The newest version is r28.0.2, that should fix your problem.
Also in android Q with the pixel 3 xl, you can't flash anything with TWRP, the storage is not mounted.
Eudeferrer said:
If you are trying to flash from within TWRP, make sure everything is properly mounted.
Sent from my Pixel 3 XL
Click to expand...
Click to collapse
As the other user has mentioned, I may be at a loss at being able to flash with TWRP after installing Q.
Gordietm said:
I think your using an old android Windows platform tools.
The newest version is r28.0.2, that should fix your problem.
Also in android Q with the pixel 3 xl, you can't flash anything with TWRP, the storage is not mounted.
Click to expand...
Click to collapse
Could you give me a detailed step by step, perhaps with the url's for the drivers & SDK tools.
I've used the links provided in the Soft Brick guide, and got the drivers direct from google themselves.
Although when I currently plug in my phone, it does install "Lemobile Android Drivers", the Google Drivers remove this but appear to be older drivers?
Download from here the latest platform tools, then flash all the factory image.
https://developer.android.com/studio/releases/platform-tools
Eudeferrer said:
If you are trying to flash from within TWRP, make sure everything is properly mounted.
Sent from my Pixel 3 XL
Click to expand...
Click to collapse
Gordietm said:
Download from here the latest platform tools, then flash all the factory image.
https://developer.android.com/studio/releases/platform-tools
Click to expand...
Click to collapse
Okay will do, please confirm if this is correct.
Extra Android platform-tools, and factory image to the same folder, then extract the zip file found within the folder itself with the zip found from the Factory Image
I erase system a & b, and boot a & b
Flash-All should work start to finish right?
What are the odd's I'm going to be stuck with a RMA?
I'm sure I've exhausted myself trying this exact process so many times yesterday.
Download platform tools, vr28.0.2
Extract it and put the contents in a folder you'll remember
Download the factory image and extract it.
Put the bootloader, radio, system image zip and flash all.bat files in the same folder as the platform tools.
Connect your phone and put in bootloader mode.
Double click flash all.
Gordietm said:
Download platform tools, vr28.0.2
Extract it and put the contents in a folder you'll remember
Download the factory image and extract it.
Put the bootloader, radio, system image zip and flash all.bat files in the same folder as the platform tools.
Connect your phone and put in bootloader mode.
Double click flash all.
Click to expand...
Click to collapse
This sounds identical to what I've be doing, which has been causing the vendor_a issue, but I will give it another run for you shortly here. Just woke up, and rather be fully awake before I go tackling this.
If you can think of any other method, or even an explanation why the vendor img doesn't seem to work that would be awesome.
Also, there is threads I found through google here on XDA with users have a similar issue hanging at vendor, but not due to the same mistake. I'll find you the URL's shortly here.
It's because you were using r28.0.1 before, download r28.0.2
Gordietm said:
Download platform tools, vr28.0.2
Extract it and put the contents in a folder you'll remember
Download the factory image and extract it.
Put the bootloader, radio, system image zip and flash all.bat files in the same folder as the platform tools.
Connect your phone and put in bootloader mode.
Double click flash all.
Click to expand...
Click to collapse
Gordietm said:
It's because you were using r28.0.1 before, download r28.0.2
Click to expand...
Click to collapse
I've been using r28.0.02 just confirmed by looking at everything I had downloaded for trying to fix this yesterday :/
Ok, go back and flash the march android p factory image. Let it boot up and setup. Enroll the q beta program and update to q with your phone. Try that.
Gordietm said:
Ok, go back and flash the march android p factory image. Let it boot up and setup. Enroll the q beta program and update to q with your phone. Try that.
Click to expand...
Click to collapse
Was on the newest 9.0, updated through Q with the opt in, boot into twrp, flashed it, broke the phone ever since. That's the simplified issue, following the soft brick guide with updated tools & drivers using C to C cable no factory image has worked. All breaking at different points, closest an image got was the newest 9.0 failing at the Vendor img,
Gordietm said:
Ok, go back and flash the march android p factory image. Let it boot up and setup. Enroll the q beta program and update to q with your phone. Try that.
Click to expand...
Click to collapse
I have access to another phone here, and can make a video of what I'm exactly doing?
Would this be of any use to troubleshoot, I really don't want to end up on the path to an RMA.
At this point, you're probably best to talk to someone else who has more experience at this than I do.
Good luck!
Gordietm said:
Ok, go back and flash the march android p factory image. Let it boot up and setup. Enroll the q beta program and update to q with your phone. Try that.
Click to expand...
Click to collapse
Gordietm said:
At this point, you're probably best to talk to someone else who has more experience at this than I do.
Good luck!
Click to expand...
Click to collapse
Haha, well that's def not Google either, they straight up said RMA it.
Thanks for trying bro.
XZeeWhy said:
Haha, well that's def not Google either, they straight up said RMA it.
Thanks for trying bro.
Click to expand...
Click to collapse
The only other thing I can think of is wither the cable or the usb-c port on the computer. You said you can't get to an A to C cable but do you have another computer you could use?
XZeeWhy said:
Was on the newest 9.0, updated through Q with the opt in, boot into twrp, flashed it, broke the phone ever since. That's the simplified issue, following the soft brick guide with updated tools & drivers using C to C cable no factory image has worked. All breaking at different points, closest an image got was the newest 9.0 failing at the Vendor img,
Click to expand...
Click to collapse
After failing on the Vendor image, you can sideload the OTA and that should get you back up and running......for some strange reason I always seem to fail there and sideload the OTA at that point has ALWAYS fixed me.
GL!!
hatdrc said:
The only other thing I can think of is wither the cable or the usb-c port on the computer. You said you can't get to an A to C cable but do you have another computer you could use?
Click to expand...
Click to collapse
There is another PC here, but it doesn't have a Type C port, and I don't have an adapter on hand either.
Certainly willing to give Windows a clean install or do a live boot or install of linux to see if a fresh install or another operating system may help resolve it.
So stock factory images can not be flashed via TWRP?
It does seem to change various images on the device when rebooting to bootloader after using Flash All so I feel like it's getting quite a large amount of the partial install.
If I have boot loader & TWRP, I mean there has got to be a way right?
My phone arrived last night. I immediately, following the instructions I found here, magisk'd it. As soon as I flashed the patched image and rebooted... I found that the touch screen had stopped working.
So I booted into recovery (which was hard, because I can't figure out any way to shut my phone down), and wiped data / factory reset. The bootloader is still showing as unlocked. And the touch screen is still not working.
Does anybody know why this might be or what I should do about it? Note that I didn't buy from Google, I bought new from a well-reputed ebay seller...
Send it back. It sounds like a hardware issue.
sic0048 said:
Send it back. It sounds like a hardware issue.
Click to expand...
Click to collapse
Alright.
Problem number 2: if I lock the bootloader, it tells me there's no valid operating system on the phone and won't start up. It only starts up while the bootloader is locked. So... do I send it back with the bootloader unlocked and hope they don't mind?
DanHakimi said:
Alright.
Problem number 2: if I lock the bootloader, it tells me there's no valid operating system on the phone and won't start up. It only starts up while the bootloader is locked. So... do I send it back with the bootloader unlocked and hope they don't mind?
Click to expand...
Click to collapse
If they are a reputable seller on ebay they probably wouldn't want to sell you a broken phone as it hurts their reputation; I'm not saying it didn't happen, but individual sellers are usually careful on that end.
Have you at least tried fastboot flashing the stock "bonito" image yet and see if that restores your touch? https://developers.google.com/android/images
*Also, keep in mind that Q is supposed to be coming out pretty soon(which may or may not help you situation). Pixel phones supposedly get official Q on Sep 3rd or you can join the beta program if you can't wait until then.
good luck:good:
Reflash the factory image and relock the bootloader... It is an official process from Google, if that fails contact the seller and RMA the unit.
Hey buddy! I was in the same boat as you, so maybe your situation was the same as mine. My problem was that I had flashed the incorrect boot image. What I'd suggest is what I did: use a mouse to navigate through the phone and check the system version, then download the exact same OS version from google, extract, and flash that stock boot image. If it works, you can patch that same stock boot image with magisk and flash that one to get root and keep the touch screen working.
I hope this works out for ya. Cheers!
As it's new and you've got nothing to worry about saving I'd just flash the latest factory image via fastboot and once it's up extract the boot from that image and patch it. The fellow above is probably correct but there is one other thing, use an A to C cord, not the C to C cord for all your flashing.
Bob nesta said:
If they are a reputable seller on ebay they probably wouldn't want to sell you a broken phone as it hurts their reputation; I'm not saying it didn't happen, but individual sellers are usually careful on that end.
Have you at least tried fastboot flashing the stock "bonito" image yet and see if that restores your touch? https://developers.google.com/android/images
*Also, keep in mind that Q is supposed to be coming out pretty soon(which may or may not help you situation). Pixel phones supposedly get official Q on Sep 3rd or you can join the beta program if you can't wait until then.
good luck:good:
Click to expand...
Click to collapse
Yes, I've tried multiple versions of the bonito image, and none of them would flash properly. I'm really just trying to figure out if they're going to blame me because I unlocked the bootloader.
Will Q actually release tomorrow? Like, stock images up and everything? Oh, well, I might as well wait until tomorrow while I try to figure out their return policy.
DanHakimi said:
Yes, I've tried multiple versions of the bonito image, and none of them would flash properly. I'm really just trying to figure out if they're going to blame me because I unlocked the bootloader.
Will Q actually release tomorrow? Like, stock images up and everything? Oh, well, I might as well wait until tomorrow while I try to figure out their return policy.
Click to expand...
Click to collapse
You can relock the bootloader. Instructions are in the link I provided earlier. How would they know you unlocked it?
As far as Q - maybe? That's why I said "supposedly" it comes out the 3rd (https://www.theverge.com/platform/a...ndroid-10-pixel-september-3-release-leak-date) , but there are no guarantees in life (except death & taxes).
Again, just to be sure, you are using a USB A to C and not a C to C, correct?
DarkShadowMX said:
Hey buddy! I was in the same boat as you, so maybe your situation was the same as mine. My problem was that I had flashed the incorrect boot image. What I'd suggest is what I did: use a mouse to navigate through the phone and check the system version, then download the exact same OS version from google, extract, and flash that stock boot image. If it works, you can patch that same stock boot image with magisk and flash that one to get root and keep the touch screen working.
I hope this works out for ya. Cheers!
Click to expand...
Click to collapse
I don't have a USB-C mouse, but I guess I could keep trying images until one of them works...
krabman said:
Again, just to be sure, you are using a USB A to C and not a C to C, correct?
Click to expand...
Click to collapse
Yes, A to C.
Bob nesta said:
You can relock the bootloader. Instructions are in the link I provided earlier. How would they know you unlocked it?
Click to expand...
Click to collapse
No, again, like I said, I can't. I tried fastboot OEM lock. And I tried flashing multiple stock images. Nothing seems to be working. I can try again and get you the exact error messages...
DanHakimi said:
No, again, like I said, I can't. I tried fastboot OEM lock. And I tried flashing multiple stock images. Nothing seems to be working. I can try again and get you the exact error messages...
Click to expand...
Click to collapse
Please do. I'm no dev & can probably offer little to no help, but if you post your errors someone else may be able to help you out.
It could just be a cable/driver/fastboot issue & not the phone, so please provide error info.
Ok, do the full smash. This assumes a basic familiarity with flashing mechanics.
1. Download and install the latest fastboot package.
2. Download the latest image from google again.
3 Use a known good A to C usb cord
4 Before flashing the image type all the following commands one by one in fastboot...
fastboot erase system_a
fastboot erase system_b
fastboot erase boot_a
fastboot erase boot_b
fastboot reboot-bootloader
5 Flash the image using the flash all script.
6 Once you're up extract the boot from the image you flashed and patch it in magisk.
7 Flash the patched boot image.
DanHakimi said:
I don't have a USB-C mouse, but I guess I could keep trying images until one of them works...
Click to expand...
Click to collapse
I don't either. I used a USB OTG cable
Had a **** ton load of issues trying to go from rooted and TWRP with custom rom to Android 10.. Every time I ran the flash-all.bat it would fail at one stage or another.. Finally grabbed the Pie Ota from the site, sideloaded it through TWRP then wiped everything through stock recovery and then took the Android 10 update. My point is, use the OTA and sideload it
I was rooted on Android 10 beta 6 and trying to download the OTA through the phone update failed every time. I uninstalled magisk and restored images..but still failed. I finally had to sideload the OTA image and it finally updated. That was the only way to get mine to work. Then I took the boot image from beta 6 that was already patched through magisk and re-flashed it because the boot image from Android 10 official patched through magisk would not give root...kept failing. Then when I re-flashed last months beta 6 image, upon reboot the screen would freeze and no apps would load. I then booted into recovery and did a factory reset and upon reboot magisk was identified and root was acquired....phone worked perfectly after that and no issues....weird. I then just reloaded all of my apps from backup and was on Android 10 official, rooted through magisk.
I used the dongle included with the phone to make my usb-wireless mouse work. The OS is currently showing the July 5 version of Android 9. When I try flashing that specific version, I see what I attached in my screenshot. Other versions show similar bugs, although perhaps a few more. I haven't tried Android 10 yet...
DanHakimi said:
I used the dongle included with the phone to make my usb-wireless mouse work. The OS is currently showing the July 5 version of Android 9. When I try flashing that specific version, I see what I attached in my screenshot. Other versions show similar bugs, although perhaps a few more. I haven't tried Android 10 yet...
Click to expand...
Click to collapse
I suspect you are running out of hard disk space on the computer that you are using to try to flash all this with. I ran into a similar issue once when the C drive of my computer was nearly full. The system file ends up needing a lot of disk space in order for it to be unpacked. The error you are getting is that you are running out of space and it cannot unpack it. Again, this isn't phone memory space, this is actual computer hard drive space.
Thanks in advance if anyone can help me with this.
I tried to root my phone via Magisk using a tutorial on YouTube. I noticed after Magisk had patched the boot.img it reduced in size from around 65MB to 30MB, which seemed odd. Flashed it, and phone became stuck in a boot loop. I tried to use fastboot to put the original boot.img back, and ended up being told the system was corrupted.
Thought I would just flash the factory firmware back on to the phone - however, that is failing partway through, when it tries to flash vendor.img, with an error "write to device failed in SendBuffer()"
I've tried multiple different versions of ADB and Fastboot, from HighOnAndroid and Google, tried flashing from a different laptop, but it fails at the same point regardless. The only thing I haven't been able to try is a different cable, but it would seem odd if that was the cause?
My device was originally on Bonito 10.0.0 (QQ1A.191205.011, Dec 2019) - I've tried to flash that back, and also tried 10.0.0 (QQ1A.200105.002, Jan 2020), neither of them working.
I'm using ADB and Fastboot from the Platform Tools at https://developer.android.com/studio/releases/platform-tools - a lot of posts I've read talk about "installing ADB and Fastboot", but they're just executables that run fine without any installation, unless I'm missing something.
Does anyone have any ideas of what I could try please?
Same old story - different cable, different port, worked.
I also suspect that the platform tools were not compatible with QQ1A.200105.002, Jan 2020, since the one I successfully managed to flash in the end was the December version.
Since I changed both cable and version at the same time, I can't say which one it was.
Hope this helps someone else.
smimon said:
Same old story - different cable, different port, worked.
I also suspect that the platform tools were not compatible with QQ1A.200105.002, Jan 2020, since the one I successfully managed to flash in the end was the December version.
Since I changed both cable and version at the same time, I can't say which one it was.
Hope this helps someone else.
Click to expand...
Click to collapse
I wonder if this is why Magisk Installer doesn't like my boot image, consequently failing to patch it.
clayndwoods said:
I wonder if this is why Magisk Installer doesn't like my boot image, consequently failing to patch it.
Click to expand...
Click to collapse
Known issue with Cannery Channel. Try latest Stable. Also checkout Magisk thread.
Android
I figured it out. I was trying to patch the wrong file, apparently.
I'm a bit concerned, though, as the patched file is 29.6Mb and the orignal boot.img is around 60Mb.
I don't want to hose this phone, has I just got it as a replacement from Google. I tried sideloading the Android 10 update using TWRP (my original phone had TWRP and Magisk installed) and bricked the phone. Well, not exactly bricked. It was stuck in recovery, the only thing that would work was the bar code display.
You never know what you like so much about the pixel until you have to use a Samsung while waiting for your replacement Pixel to arrive. I can't survive without call screening LOL!
clayndwoods said:
Android
I figured it out. I was trying to patch the wrong file, apparently.
I'm a bit concerned, though, as the patched file is 29.6Mb and the orignal boot.img is around 60Mb.
Click to expand...
Click to collapse
The patched file is normally smaller than the stock boot.img. That's OK and expected.