** Unable to Flash Pipo N7 (4032 error) Fix **
** As usual, I’m not responsible to any FURTHER damage you might do to your tablet or yourself, by trying to manipulate the system’s ROM or Li-Ion batteries **
Background
I’ve seen a lot of people trying to flash a different ROM on these tablets and resulting with a bricked device. Ironically the ROM that bricks the device comes directly from Pipo. I’ve been in touch with Pipo engineering and they told me that the ROM posted in their website is exclusive for Android 6.0 devices, and currently there is no 7.0 ROM in their website.
As with a lot of small Chinese technology manufacturers, their company lacks of some organization, which has lead to these type of confusion. That’s some of the risk that one takes when buying these brands.
Problem
You try to roll back to Android 6.0 for whatever reason you want: stability, speed, or simply that was the only ROM available for you to recover from an error or troubleshooting your tablet.
After installing VCOM drivers (won’t even talk about this, the whole web has info on this), and flashing the 6.0 ROM via SP Flash Tools, the tablet is bricked.
Behaviour
The tablet won’t power up and there is no access to recovery, adb sideload, etc. The only response is under DEVICE MANAGER, the port appears and disappears.
The only way to make the port “stop” reconnecting, is to open SP Flash Tools and select a command (i.e. download, format, readback, etc.). Only by doing this you will be able to stablish a link with the tablet, which is expecting now to receive a Preloader.
If you try to flash the ROM again, you will now get a fat S_FT_enable_dram_fail (4032) error. All of this was done WITH THE NEGATIVE BATTERY LEAD UNSOLDERED.
Solution
Drivers
If you were able to brick it with the wrong ROM, then you don’t need to troubleshoot driver issues, sounds logic right? Drivers discarded.
Battery
The battery is soldered, you have two options. Open the tablet with a credit card-->>[ https://www.youtube.com/watch?v=T5ucwSLCVOQ ] all along the side to unlock the clips, and then unsolder the negative lead (protect is with some tape or something while working), or just use the RESET switch on top.
ROM
Attached is the working ROM for the following PipoN7 product (latest that has been shipped since Dec 2017)
https://www.4shared.com/rar/Znmpc-q-gm/N7_OEM_70.html
Procedure
Unpack the ROM (verify the path is not too long, or else you might get an Error on SP Flash Tools)
Open SP Flash Tools, select the scatter file, verify ALL FILES are checked and press download
Connect the tablet, if the process doesn’t start, press the Tablet’s reset button on top
If the reset button doesn’t work, you need to unsolder the battery and try again
When finished close Flash Tools, disconnect and leave the tablet charging (when bricked the battery usually discharges). When connected you should see the battery icon, indicating charge
With this ROM also, we can probably have Custom Builds in the future, to make improvements to this great nifty little tablet.
Good Luck!
Related
Hello all,
I have googled, and searched forums high and low to no result so I thought i'd ask.
I recently purchased "KVD APOLLO ONE K6589 Quad-Core Android 4.2.1 WCDMA Smartphone w/ 5.5"
Im new so I can't post external links, however if you go to google or deal extreme and search, you'll find it easy enough.
The phone itself was next to nothing ($180) so even if its Unrootable, I'm not too fussy.
I would however prefer it rooted, I have read that you can basically use the MTK6577 rooting tool on the device?
Would this risk bricking the device.
I'v attempted to contact the manufacturer however to no avail! This is a rather new model so I know im being a tad impatient but if anyone can help then please do
Thanks guys
Potentional Tutorial
philipkroberts said:
Hello all,
I have googled, and searched forums high and low to no result so I thought i'd ask.
I recently purchased "KVD APOLLO ONE K6589 Quad-Core Android 4.2.1 WCDMA Smartphone w/ 5.5"
Im new so I can't post external links, however if you go to google or deal extreme and search, you'll find it easy enough.
The phone itself was next to nothing ($180) so even if its Unrootable, I'm not too fussy.
I would however prefer it rooted, I have read that you can basically use the MTK6577 rooting tool on the device?
Would this risk bricking the device.
I'v attempted to contact the manufacturer however to no avail! This is a rather new model so I know im being a tad impatient but if anyone can help then please do
Thanks guys
Click to expand...
Click to collapse
philipkroberts said:
Hello all,
I have googled, and searched forums high and low to no result so I thought i'd ask.
I recently purchased "KVD APOLLO ONE K6589 Quad-Core Android 4.2.1 WCDMA Smartphone w/ 5.5"
Im new so I can't post external links, however if you go to google or deal extreme and search, you'll find it easy enough.
The phone itself was next to nothing ($180) so even if its Unrootable, I'm not too fussy.
I would however prefer it rooted, I have read that you can basically use the MTK6577 rooting tool on the device?
Would this risk bricking the device.
I'v attempted to contact the manufacturer however to no avail! This is a rather new model so I know im being a tad impatient but if anyone can help then please do
Thanks guys
Click to expand...
Click to collapse
Also looks like im getting the Star N9589 just due to the more support available.
Anyhow until then, failing any answers from here, another chinese forum a spanish one and Yahoo answers I am going to go with the following method, If it dies, It dies this was my own fault for not doing enough research and at least it lets others know. I would send it back to DX But cba with postage fees and the hassle;
THIS IS DONE AT YOUR OWN RISK! -
APOLLO ONE - MTK 6589 K6589
Please note all tools and zip files mentioned I cant link to yet should you feel you want them please post in this thread and I will PM you, Gotta get my post count up first!
Guide by philipkroberts Twitter @philipkroberts
Revision 1 - People to be added to credits for leehed source, currently untested, concept only
Before anything try and boot into any form of recovery mode and backup if possible!
DISABLE UAC in WINDOWS 7
RIGHT CLICK RUN AS ADMIN ON ALL FILES
ALLOW NON TRUSTED DRIVER INSTALLATION (Google this if unsure)
On the phone install anububu on pc phone. - See what model it detects as and note it down.
Run MTK DROID TOOLS and connect phone see if drivers After a few seconds, the box should turn blue, and it should say "Apollo ONE or Other Name " besides it. The drivers are working.
If not try the other drivers in the drivers folder using device manager, there are many tutorials for this I cba typing one im so tired! and make sure you have the only trusted drivers thing turned off, if you constantly get unknown driver then your out of look and wil have to try and source some yourself.
Win7 (This method has not been tested by myself. Confirmation required.)
HOW TO MANUALLY INSTALL ANY DRIVERS IF NEEDED
a - Downloading This tool Called EASYBCD
b - Use it to restart your computer in advanced boot mode. (PRESSING F8 WHILST BOOTING UNTIL YOU GET THE OPTION FOR Disable signed driver enforcement)-Must be done everytime you wanna root a phone with this method.
c - Follow instructions and disable SDE.
d Manually install drivers, if above did not work (Yellow sign issue)
e Navigate to control panel - > Hardware and Sound - > Device Manager
f You should see a driver notice with a yellow warning sign next to it.
g Right click on it and choose "Update driver..".
h- Manually assign drivers, usually the choice furthest down.
i- In the window which should have appeared, navigate to the preload/Mt6590 folder and press OK.
j- If SDE is turned off, you should see a red warning window. This is normal, just accept the message prompted.
k- The drivers should now be successfully installed.
l - Once this is done open C:\Users\Hate\Desktop\Chinese Droid Rooting\MTKROOT TOOLS\Root_with_Restore_by_Bin4ry_v28\runme.bat Hope it ****ing works if so your rooted, If not try this next few steps, AGAIN at your own risk, no need to format just continue from here.
THE FOLLOWING STEPS ARE FOR THE STAR S5 - SAME PROCESSOR BUT NO GARUNTEE. DO NOT FOLLOW THESE STEPS UNLESS YOU ROOTED ANOTHER WAY AND NOW JUST WANT TO INSTALL A CWM
THE FOLLOWING STEPS ARE FOR THE STAR S5 - SAME PROCESSOR BUT NO GARUNTEE. DO NOT FOLLOW THESE STEPS UNLESS YOU ROOTED ANOTHER WAY AND NOW JUST WANT TO INSTALL A CWM
THE FOLLOWING STEPS ARE FOR THE STAR S5 - SAME PROCESSOR BUT NO GARUNTEE. DO NOT FOLLOW THESE STEPS UNLESS YOU ROOTED ANOTHER WAY AND NOW JUST WANT TO INSTALL A CWM
THE FOLLOWING STEPS ARE FOR THE STAR S5 - SAME PROCESSOR BUT NO GARUNTEE. DO NOT FOLLOW THESE STEPS UNLESS YOU ROOTED ANOTHER WAY AND NOW JUST WANT TO INSTALL A CWM
0 - Use PC to copy UPDATE-SuperSU-v.1.25.zip to the root of SD CARD, do not unpack just leave whole zip there.
1 - Turn off your phone, remove your battery. (Do not connect your phone to the computer yet!)
2 - Navigate to the "SP Flash Tool" folder, and run the tool.
3 - On the right side of the tool, there should be a button, iconed with a folder, named "Scatter-Loading". Click this.
4 - Navigate to the "Yulypis Recovery" folder, and double-click on the "Mt6589_Android_scatter-emmc.txt".
5 - You should be back at the SP Flash Tool start-screen, and there should have appeared a list of text and hex-codes.
6 - The "Recovery" line, should be ticked off, and preloader should be red.
7 - Now, click on the button named "Download", with a blue arrow on it. Press "YES" on the NOT ALL images has been correctly loaded warning.
8 - Connect your phone to a USB 2.0, with removed battery. The program should now work, and if drivers is set up correctly, the 0% will turn 100% and a green circle will appear in the middle of the screen. If your phone disconnects before the flashing tool is able to recognize your device, try putting the battery back into the phone before running SP Flash tool. Additionally, if this doesn't work, try using different drivers in the drivers folder
9 - Disconnect your K6589 from the computer when you see the green circle, insert the battery and boot the phone. Wait for it to get to the start screen.
11 - Installing SuperSU through Yulypis recovery
12 - Run "MtkDroidTools.exe" from the folder.
13 - Connect your device, and after a few seconds, information about your device should appear.
14 - Click on reboot, on the mtkDroidTools start-screen, and choose "..recovery".
15 - If recovery has been properly flashed, your device will now enter Yulypis recovery. Blue, with english text.
16 - Controllers: "Power = Enter, Initialize", "Volume down = Scrolling down". (Don't remember if volume up was bugged or not)
17 - Enter "Install zip from SDcard" - > Navigate to the earlier copied "UPDATE-SuperSU-v.1.25.zip and initialize it by pressing the power button.
18 - Follow the on-screen instructions, and it should be prompted to install after 1-2 more screens.
19 - Reboot the device by clicking on "+++++back+++++" and "Reboot now / Reboot Device".
Either way I am going to smash this in a week or so when the phone arrives from DX and will keep people update.
Peace
Please I want to buy this phone. Can you answer me a few doubts I have?
- How is the viewing angle? Cause i purchased a tablet from china and the angle is very bad.
- Has proximity sensor?
Are you ok with the phone?
thank you.
cabrote said:
Please I want to buy this phone. Can you answer me a few doubts I have?
- How is the viewing angle? Cause i purchased a tablet from china and the angle is very bad.
- Has proximity sensor?
Are you ok with the phone?
thank you.
Click to expand...
Click to collapse
I'm still awaiting the phone, hence why that guide is at your own risk.
However from what I have been told and gather that should root the phone no problems.
As for custom roms, I wouldn't even bother trying!
Once the phone gets here I will test my tutorial and re-write it into a more easy on the eyes fashion.
Thanks
http://www.fastcardtech.com/APOLLO-ONE-K6589?u=37825
They sell the phone, for an extra $3 they root before sending.
It cant be that hard, I'd love to know someone in that factory!
I'm looking for a link to download the full stock firmware for this device.
Anyone, please?
...or at least a firmware dump from a non-modified working phone.
One could use MTK Droid Tools and SPFlash to perform this task easily.
PM me for assistance if you need it.
Thank you.
My Chinese Android car head unit is stuck in a bootloop (the home screen shows but the unit reboots after a few seconds). I got a firmware zip file from the manufacturer (the zip contains files like scatter.txt, ramdisk2.img, boot.img and so on). However, I'm unable how to find out how on earth I can install this firmware and get out of my bootloop.
I have no access to Android itself (the system reboots too soon). There are no physical buttons to activate recovery mode. When I use a USB keyboard I can get into recovery by pressing ALT GR and PRT SCR but after a reset "no command" shows up and I'm stuck again...
Any help please?
Flashing instructions
[Apologies for the lengthy reply, I have to assume that you have no experience in flashing MTK SoC]
Sorry to hear that! I am also contemplating t buy a Chinese Android headunit with GPS but I am still contemplating. Reason being which model to buy? I am an avid Lenovo devices fan because in my part of the world models from Lenovo uses a lot of MTK SoC. (Any other other brand I buy is also a must to be on MTK SoC)
Ok! Now based on your short description I saw "scatter.txt" file mentioned so it is definitely an MTK devices, 100%.. When you boot loop you definitely will not be able to access any function, more so with a head unit that dont provide hardware buttons. I can only help you understand the method to reflash the firmware on MTK devices the rest you have to figure it out yourself.
The USB port is your key here. If the manufacturer did not provide you with USB "IN" (female) port which is not normal and only provide you with USB connectors you will have to decode/or just connect the wiring from the connectors to a USB female Port (which what China manufacturers do at the back of the head unit). There are also head units that provide ready to use USB port on the facia.
Whatever it is I cant tell you which port to use. This where you will have to experiment yourself.
Download MTK flashing tool "SP Flashtool" (find the ones that is suitable upto MTK device 6592 because it should be back ward compatible with older devices) The Chinese dont use the latest MTK SoC for their head units, that is only reserved for the high end heads.
Read up on how to install SP Flashtool on your PC and other accompanying Drivers you have to install, (if you only have a Mac go borrow somebodys Win7 or Win10 PC) there are no Mac SPFlashtool.
Once you have install according to SPFlashtool instructions you read. (It has to follow a certain sequence) e.g "1- ADB Driver" so on and so forth because if you dont follow the sequence it might fail to start the flashing operation. (You will not know it but I am pretty damn sure you will be cussing me).
First read up on how to install ADB driver for MTK devices correctly. Confident? Now try connecting your device to the PC experimenting to identify the correct USB port to use. If the ADB is installed correctly and you got the right USB from the device connected your PC wil give an audible sound( it should unconnected to condition evreytime you test). OK good connection! Only then try installing SP Flash tool and try a dry running the SPFT. If your installation is correct there should be either color changes to the SPFT window because it doesnt detect any devices.
You are good to go! Your MTK Android device should be in the "OFF" condition (after every shutdown there are still some operation running in the background,so it is a good practice to wait at least 5 seconds for it to be 100% OFF.) Run the SPFT fully loaded with the firmware dislayed in the SPFT window. Then initiate "Download" (make sure all indicators is at "download only" do not change this option or you are gonna have a really dead duck.) At this point the SPFT is active and waiting for you to attach the device to PC (before running make sure the PC and device is not connected yet!). If everything is per instructed ADB, USB Cables/Ports, SPFlashTool (download only) you will see color lines in the SPFT Window, wait till the end of process it will display notificatio. If the firmware is correct and you have attached and 12V DC source to the device it should boot up as fresh as new.(provided that the supplier gave you the correct firmware).
A word of advise these cheap head units normally bluff their actual Android version e.g actual KitKat advertised and displayed as Marshmallow. Best of luck!
The zip file attached are screenshots of the flashing process.
Thanks for your very elaborate information, but it won't work. The ZIP I got is an OTA zip file. The scatter.txt inside those zips isn't compatible with the SP Flash Tool.
wimpie3 said:
Thanks for your very elaborate information, but it won't work. The ZIP I got is an OTA zip file. The scatter.txt inside those zips isn't compatible with the SP Flash Tool.
Click to expand...
Click to collapse
Doesnt the seller provide you with the original firmware? He only gave you an OTA?? Oh $#it! The OTA file is small probably a few Mb? The full firmware in your case should be around 800Mb upwards. You are right an OTA cannot use SPFT it can only be flash through the original recovery (not custom recovery). If its a popular Chinese model ML-CK1018 or Joying brand ( I assume you bought a Joying? Thats the only brand that release an OTA not long ago) There is remote possibility of getting the firmware.Anyway just give your brand and model number. I will try to look on Russian or Chinese site but no promises! Will try.
But I am pretty sure it is an MTK SoC since you can unzipped and it shows "scatter.txt" file. Most other SoC arent normally in zip format and have scatter file.
Sent from my HT70 using Tapatalk
The OTA ZIP file is about 900MB.
It's a NAVITOPIA 9 inch 4G LTE WIFI Head Unit with Android 6.0 2G + 32G.
I'm in the same boat, have a plastic bookend at the moment, will not connect to the PC because flashed and formatted my device with the update firmware!!!
Hi,
I bricked my phone, a SHARP Aquos C10.
After unlocking the bootloader I was able to install several rom. The last one was LineageOS 18.
I bricked the phone when I tried to replace LineageOS Recovery with TWRP by dint of trying.
The phone is not completely blocked. It gets stuck for a long time on the "battery" logo which replaced the "Sharp" logo when the unlocked it. After several minutes, it vibrates and restarts.
I can restart it by long pressing the OFF button, I can't turn it off, I can't put it in recovery mode.
I can just put it in download mode but unfortunately it is no longer recognized by the PC.
So, bricked or not bricked.
Thank you for your help.
Nobody can help me ?
Hallo,
if you still can go to the download mode, maybe not all hope is lost. Your phone might not have
a hard brick, but only a soft brick. Everything should be fine as long the download mode isn't bricked too.
I had a similar problem once with a tablet after flashing it.
You need to install the USB-Drivers for your device on your PC and then reconnect it.
This might sound ridicolous if you already have installed them, but sometimes
a deinstallation of the USB-drivers and reinstallation of the drivers might help.
I found the following site for the drivers:
"https://gsmusbdriver.com/sharp-aquos-c10".
If you prefer an official source, you can use: "http://www.sharpusa.com/Home/CustomerSupport/SharpCareCenter/MobileSupport/ADBDriver.aspx"
However both sources seem to look reliable for me, even if I can't test it, without having a SHARP device.
If you are not sure, you might compare it with other tutorials and look for reviews.
Installing the drivers can't lead to harm to your device until you don't connect it.
Things can't really get worse if you install the drivers. The only thing that could happen is, that either the PC will say that it recognizes the device or that no device can be recognized, so it's worth a try. Please report me, if it worked for you and you are able to flash again. I hope this will help.
With kind regards
dontdropme
Hello,
Thank you very much for your help.
Yes, I installed the USB drivers. I unlocked the phone for you I installed another rom.
I reinstalled the drivers following your links. Unfortunately that does not change anything. The phone is not recognized. No sound comes out of the computer when I connect the USB cable.
I tried on 2 computers, 1 on Windows 10 and in Windows 10 / Xubuntu dualboot.
When the battery is empty and I try to turn it on, a red battery will light up and flash. As I charge it, the battery changes color to green.
I don't have download mode if the cable is not plugged into the computer or the charger.
:/
Hallo,
the download mode is supposed to be only able to get started if you connect the device to the computer or another device, this is not strange. You need to go to the download mode and try to flash the stock firmware for you device. Try it at first without a device recognition of your PC and find out, if you need to do a hard reset before, to regain factory settings. I have listed, in color, a short number of things you could do now. If this still doesn't work only the SHARP team or a specialized company might help.
What you could do, is to ask the SHARP support for a source for the USB drivers and how to do a hard reset to regain the factory settings. I don't know which flashing tool you use for you device.
Normally if your device is not recognized by plugging it in to the PC-USB-Port the flashing tool shouldn't recognize it either, but it might be just an error of Windows, and the flashing tool is not allways depentent to the USB-drivers, but relies only on the question if you can go to the download mode, so you could give it a try to flash even in this case. Start the flashing software and look what will happen.
You said, that you have successfully flashed until now, which means that the flashing tool supports you device. If you can't flash now anymore, you might also not make a backup, which would be important, because the only things you could try now, is to find the stock firmware and flashing it.
If you haven't installed any important data on your system after flashing LineageOS or if you already made backups of your applications in a cloud or another drive you need not to care. It is possible that you will need to do a hard reset before. You can find on hardreset.info, in the section "All devices", how to do it or ask the SHARP support. If you fear you have still important data on your phone a backup is normally recommended.
Because flashing a ROM not only wipes your data, but removes the guarantee, the result is: Restoring the phone to a usable device by any helping team of SHARP's customer care service in you city, even if you have any service buildings, might be expensive in this case. To go around high prices you would need too look around also for other data restoring companies or specialists, if nothing works.
But at first, if you are able to do it; I would recommend to do a hard reset of your device, which should restore it to factory setting, which should make the drivers work.
Even if they don't work, ask SHARP for actualized USB-drivers. Try flashing also with and without working USB drivers, and find SHARP's stock firmware for you device first, which is a "must do", if you want to have access to the original recovery mode again. Flash this stock firmware after you have done a hard reset. After flashing the stock firmware you should be able to go to the custom recovery mode again, if not, only a specialized company or a help team of SHARP's customer service might help.
Hello,
The adb and fastboot commands wait for the device to connect.
SHARP support is not responding.
Hello, did you try "https://getsupport.sharpusa.com/Contact-Us/Product-Support"?
Because of the actual situation with the Virus, they might need longer to answer, so you need to be patient. As I see you already tried to connect your device after the use of CMD.exe. Installing the drivers with CMD and checking the Windows Hardware Manager if the Installation worked correctly is one way to do a driver install. I am sorry if this didn't work for you. If it does not, only a specailized soft- and hardware team can help, which could get expansive, but maybe not as much as buying a new device, so I hope for you Sharp will answer and give a correct Installation guide and that it will fit to solve your problem. I wish you good luck and that you don't need any other company than Sharp to help. I know that nobody is amused if all help and waiting does not help, after bricking bis device, but unfortunately I can't do more for you. I wish you success and keep your device in a safe place just for the case.
Hi everyone. As I said on a former post, I have an Alcatel 1t 7 tablet; I need its stock recovery image, but even stock firmware is getting impossible to find. I mean, apparently there are firmware for that reference of tablet, but what happens, is that there are several models that share the same physical appearance, but have different hardware, so, they have different firmware, and by that reason, their firmware don't work for my tablet. Anyway...
The fact is, looking that its original firmware is not available on the internet, at least publicly; I'm trying to reflash my tablet by using alcatel's tool called "Alcatel Mobile Upgrade", a tool that I don't guess, would be unknown for many of you. So as I said, I'm trying to reflash it with it (and in the process, restore stock recovery, I hope). So I installed MTK drivers, installed the version recommended for this tablet, followed program's instructions, but when I reach step 2 of 4, the program warns me saying this: "Read terminal information failed. Unplug device, remove the device battery and plug it again - Repeat step 2 and try again".
The issue is, that its battery is internal, not removable; even, is soldered to the board. And I must add, that at first, when I bought this tablet and began to "experiment" with it, I was using SP flash tool, and it was giving me almost the same warning that Alcatel mobile upgrade, but later I discovered what that was a fail of the used sp flash tool version. On a webpage, someone recommended a specific version of sp flash tool to fix that issue; I mean, that I could download firmware to the device without having to "unplug battery"; and It worked.
So first ¿How can upgrade my tablet by using that program?¿What am I doing wrong?¿ Which device must appear under device manager, to it can work?¿mtk usb port, Mediatek DA usb VCOM, Android preloader, or which one? And second, ¿Could be this problem, due to alcatel's mobile upgrade version?
let battery drain to make sure device is powered off. you only have preloader mode for a second - within this time pick up in device manager and install preloader drivers.
if drivers installed correctly, first start flashing, then connect phone. flash tool will keep device in preloader mode for the flashing time period
aIecxs said:
let battery drain to make sure device is powered off. you only have preloader mode for a second - within this time pick up in device manager and install preloader drivers.
if drivers installed correctly, first start flashing, then connect phone. flash tool will keep device in preloader mode for the flashing time period
Click to expand...
Click to collapse
Thank you for replying. Definitely using Alcatel mobile upgrade is not an option, at least to me. I mean, I couldn't make it work in any way. "Fortunately", after an exhaustive search, I could find a post on internet, that recommended for a similar issue, to use Sugar MTK; the publisher shared this program and its credentials, for can use it . So I downloaded and used it, and I could restore my original stock. Now my issue is to port it to TWRP, but now I'm gonna to write a new post about it.
link me to the sugarmtk
So i have a Pixel 6 (not the pro). I love it, despite it being a bit buggy at times. My girlfriend loves it too so she also got one. Her screen got damaged and we took it to a local repair place. They ordered the part (took about 5 days to come in) and the repair took about an hour. The repair seems to be of decent quality work. Then we realized that the fingerprint sensor was not being detected and the option to use fingerprints was no longer available in the settings. A little bit of research and i found that this is a common problem which google has failed to provide any kind of solution for.
I read through googles bug report page found here ( https://issuetracker.google.com/issues/218761008?pli=1 ) as well as a couple other pages on google, reddit, etc. I am creating this thread because i am fairly certain that a solution to this problem can be engineered by the community but personally lack the skills required to accomplish this single handedly...
So...
The issue is that the fingerprint sensor needs to be calibrated after being replaced using the official tool found here ( https://pixelrepair.withgoogle.com/udfps )
There are two ways to connect to your phone when you run this tool. Using fastboot (via "adb reboot bootloader) or fastbootd (via "adb reboot fastboot
When attempting to run the tool via fastboot the tool fails at the download step saying "Couldn't find the unique calibration software for this device"
when attempting to run the tool via fastbootd it fails at the installation step saying "Couldn’t install the software" (seemingly having successfully downloaded the tool but being unable to install it in fastbootd)
Certain posts on the google bug report page have claimed success by running the tool on different firmware builds. I have tried flashing the oldest 12.0 build, the current 12.1 build, and the beta 13 builds as suggested by various reports to no avail.
However, when i run this tool on my own device which has the factory original screen, it runs and completes flawlessly. This leads me to believe that reports saying the issue is with the build quality of the screen replacements being sources by boutique repair shops causing the tool to not recognize the screen may have some merit.
Now...
At the bug report page I linked to above, post #20, it shows a user who inspected the url for the command which is failing with a 404 code. I assume this is what happens when running via fastboot and it fails to download the tool...
This is where i lack the skills needed to implement a solution. Im pretty sure that there is a way to redirect the failing url to a destination of ones choosing. If so, it should be possible to extract the url used by the tool when it succeeds on the downloading step (either via the fastbootd method or when used on a device that has not been repaired). The URL could then be used as a redirection target for the tool, or possibly downloaded (or extracted from the browser cache) and run independently.
I dont know if any of my ideas here are viable, but there seems to be a disturbingly large number of users who would benefit from a solution.
Any ideas?
PS: please forgive any formatting failures on my part