Database Info

[Completed] Lenovo A6010 8GB problem

Hello,
I had my device running slow from the moment I opened it the first time.
I know I should have take it to the warranty, but I needed the time all day.
I dropped it so I couldn't take it there anymore.
Now, since the warranty is void, I wanted to change the 5.0.2 lollipop, hoping for a normal response time from it.
I tried installing TWRP and I didn't suceed. It got stuck on the Lenovo logo.
I managed to put back a recovery from another ROM (lenovo) and used QcomDLoader.exe to flash another rom. A stock version of A6010 but of 16GB ROM not 8 like mine.
It didn't work, even if I waited more than 500 seconds (more than 5 minutes). Now, it's in black screen, won't come out of it.
I managed to find some errors with another qualcomm flash applications:
Code:
Sahara Version:0
Start Sending Programmer
Download Fail:System.Exception: Unable to download Flash Programmer using Sahara Protocol
at QC.QMSLPhone.Phone.QPHONEMS_SaharaArmPrgDownload(String sFileName)
at QC.SwDownloadDLL.SwDownload.QPHONEMSSaharaDownloadArmPrg(UInt64& version, String armPrgPath)
Download Fail:Sahara FailSahara Fail
Finish Download
I hope someone has an idea that could help me out. I'm trying non-stop for 10 hours now. My head really hurts, I didn't just post this here without trying to solve it myself first.
Thank you in advance for your help!
Andrei

UPDATE:
Okay, so I managed to install a 8GB A6000 firmware, but the GSM network is not working. It shows 2 sims of 2G and none is working.
I have the open source files of my original firmware on lenovo's site.
How could I replace the entire OS, so masically copy/paste the files from computer onto the phone? Or ..can I make a flash version from those files?
Thank you!
Andrei

Hi,
Try posting your question here:
Android Q&A, Help & Troubleshooting
The experts there may be able to help.
Good luck!

[Solved] Root for 8.0 / semi-bricked phone

Hi guys,
I've a brand new Nokia 3 (TA-1032) and updated it OTA with Android 8.0.0 and sec patches from July 5th. Now I'm trying to root that phone and as far as I've understood the various thread, I've to downgrade to Android 7.0. However, it seems I mixed up some guides...
When starting my phone, the following message is displayed: "Orange state, can't be trusted". After a couple of seconds the phone boots normally.
Any ideas how I can root my phone? I'm damn sure the solution is somewhere out there on xda dev, but a wealth of information creates a poverty of attention.... meaning I've no idea where to start.
Thanks and enjoy the weekend
Youser
===
Update: I could successfully go back to Android 7 with OST and root my device. Problem is solved.

Going back to U-Model Firmware from A2020G_PRO_V1.6_FULL_EDL

Hello guys,
i have a A2020U model Axon 10 Pro and i recently managed to unbrick my phone with the A2020G_PRO_V1.6_FULL_EDL with Miflash.
Can anyone tell me a safe way to get back to U-model firmware?
I tried to flash GEN_NA_P855A03V1.0.0B11_DL with Miflash & EDL-Tool --> no luck!
EDL-Tool LOG:
Code:
ERROR: C:\EDL_TOOL\flash\full\userdata.img - SPARSE image!!!
ERROR: C:\EDL_TOOL\flash\full\vendor.img - SPARSE image!!!
ERROR: C:\EDL_TOOL\flash\full\system.img - SPARSE image!!!
ERROR: C:\EDL_TOOL\flash\full\system_other. img - SPARSE image!!!
Miflash LOG:
Code:
[19:03:25 COM20]:MiFlash 2019.12.6.0
[19:03:25 COM20]:flash in thread name:COM20,id:8
[19:03:25 COM20]:need provision
[19:03:25 COM20]:need provision
[19:03:25 COM20]:flash in thread name:COM20,id:8
[19:03:25 COM20]:need provision
[19:03:25 COM20]:[COM20]:start flash.
[19:03:26 COM20]:cannot receive hello packet,MiFlash is trying to reset status!
[19:03:27 COM20]:try to reset status.
[19:03:29 COM20]:write time out try agian 1
[19:03:32 COM20]:write time out try agian 2
[19:03:34 COM20]:write time out try agian 3
[19:03:37 COM20]:write time out try agian 4
[19:03:39 COM20]:write time out try agian 5
[19:03:42 COM20]:write time out try agian 6
[19:03:44 COM20]:write time out try agian 7
[19:03:45 COM20]:error:Timeout bei Schreibvorgang überschritten.
[19:03:45 COM20]:System.Exception: write time out,maybe device was disconnected.
bei XiaoMiFlash.code.Utility.Comm.WritePort(Byte[] send, Int32 offSet, Int32 count)
bei XiaoMiFlash.code.bl.SerialPortDevice.SaharaDownloadProgrammer(Int32 programmertype)
bei XiaoMiFlash.code.bl.SerialPortDevice.XiaomiFlash() bei XiaoMiFlash.code.Utility.Comm.WritePort(Byte[] send, Int32 offSet, Int32 count)
bei XiaoMiFlash.code.bl.SerialPortDevice.SaharaDownloadProgrammer(Int32 programmertype)
bei XiaoMiFlash.code.bl.SerialPortDevice.XiaomiFlash()
[19:03:45 COM20]:before restart close COM20
[19:03:45 COM20]:vboy-test err return
[19:03:45 COM20]:flashSuccess False
[19:03:45 COM20]:isFactory False CheckCPUID False
[19:03:45 COM20]:before:flashSuccess is False set IsUpdate:True set IsDone True
[19:03:45 COM20]:after:flashSuccess is False set IsUpdate:false set IsDone true
Does anybody know how to get rid of the SPARSE Image difficulties (as seen in ETL-Tool Log)? I am working on Win10.
Can someone provide a A2020U Firmware that is flashable via SD Card?? I would like to try it that way.
Are there any advantages staying on the G firmware?
-GrayFox

@GrayFox1950 @Unjustified Dev @pmartin
I thought I'd offer the following after our last few posts on various threads. I'm a AT&T corporate engineer and have a friend who is a developer in our in-house Android device team. After much banging my head against my desk, I admitted defeat and reached out to him. After getting together for a few flights of high-end scotch, I now have a MiFlash flashable EDL of the NA Android 9.x v1.11 build. Once booted it shows up as "GEN_NA_A2020U_PROV1.11". Once it is running it received an OTA to v1.13. So now, I have my phone BL Unlocked, TWRP, Magisk and Xposed installed.
Currently I'm fighting an issue which occurs while writing large amounts of data to the external SD Card. If the phone goes to sleep while the copy / move process is ongoing, it WILL fail. If I tap the screen every 20 seconds or so, it works fine. When the data transfer fails, the SD Card disappears from the OS. A reboot brings it right back. (Weird, right?)
Ultimately, I want to be running Lineage 16.x with the phone storage decrypted. I just found an online archive of the the No-verity-opt-encrypt script. I'm wondering if they will work for our phones. https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
Any ideas on any of this?
If you are interested, I can upload it to AndroidHosting.

GrayFox1950 said:
Hello guys,
i have a A2020U model Axon 10 Pro and i recently managed to unbrick my phone with the A2020G_PRO_V1.6_FULL_EDL with Miflash.
Can anyone tell me a safe way to get back to U-model firmware?
I tried to flash GEN_NA_P855A03V1.0.0B11_DL with Miflash & EDL-Tool --> no luck!
EDL-Tool LOG:
Code:
ERROR: C:\EDL_TOOL\flash\full\userdata.img - SPARSE image!!!
ERROR: C:\EDL_TOOL\flash\full\vendor.img - SPARSE image!!!
ERROR: C:\EDL_TOOL\flash\full\system.img - SPARSE image!!!
ERROR: C:\EDL_TOOL\flash\full\system_other. img - SPARSE image!!!
Miflash LOG:
Code:
[19:03:25 COM20]:MiFlash 2019.12.6.0
[19:03:25 COM20]:flash in thread name:COM20,id:8
[19:03:25 COM20]:need provision
[19:03:25 COM20]:need provision
[19:03:25 COM20]:flash in thread name:COM20,id:8
[19:03:25 COM20]:need provision
[19:03:25 COM20]:[COM20]:start flash.
[19:03:26 COM20]:cannot receive hello packet,MiFlash is trying to reset status!
[19:03:27 COM20]:try to reset status.
[19:03:29 COM20]:write time out try agian 1
[19:03:32 COM20]:write time out try agian 2
[19:03:34 COM20]:write time out try agian 3
[19:03:37 COM20]:write time out try agian 4
[19:03:39 COM20]:write time out try agian 5
[19:03:42 COM20]:write time out try agian 6
[19:03:44 COM20]:write time out try agian 7
[19:03:45 COM20]:error:Timeout bei Schreibvorgang überschritten.
[19:03:45 COM20]:System.Exception: write time out,maybe device was disconnected.
bei XiaoMiFlash.code.Utility.Comm.WritePort(Byte[] send, Int32 offSet, Int32 count)
bei XiaoMiFlash.code.bl.SerialPortDevice.SaharaDownloadProgrammer(Int32 programmertype)
bei XiaoMiFlash.code.bl.SerialPortDevice.XiaomiFlash() bei XiaoMiFlash.code.Utility.Comm.WritePort(Byte[] send, Int32 offSet, Int32 count)
bei XiaoMiFlash.code.bl.SerialPortDevice.SaharaDownloadProgrammer(Int32 programmertype)
bei XiaoMiFlash.code.bl.SerialPortDevice.XiaomiFlash()
[19:03:45 COM20]:before restart close COM20
[19:03:45 COM20]:vboy-test err return
[19:03:45 COM20]:flashSuccess False
[19:03:45 COM20]:isFactory False CheckCPUID False
[19:03:45 COM20]:before:flashSuccess is False set IsUpdate:True set IsDone True
[19:03:45 COM20]:after:flashSuccess is False set IsUpdate:false set IsDone true
Does anybody know how to get rid of the SPARSE Image difficulties (as seen in ETL-Tool Log)? I am working on Win10.
Can someone provide a A2020U Firmware that is flashable via SD Card?? I would like to try it that way.
Are there any advantages staying on the G firmware?
-GrayFox
Click to expand...
Click to collapse
After a lot of crying and freaking out, I finally was able to get that same firmware flashed. Unfortunately, I live in the US and my sim card won't work with it. Please let me know if you find a way to go back to the A2020U firmware.

I am still stuck on A2020G but by flashing NON-HLOS.bin and NON-HLOS_b.bin( I had to copy NON-HLOS.bin and rename it to NON-HLOS_b.bin to get it to flash properly) I got my mobile data back. The only issue is that I have no sound on phone calls, which is kind of a huge issue. Texts and data work, just no sound on calls. The other person on the phone can't hear me either. I have tried using earbuds and bluetooth to see if calls would work that way and they don't. I have also tried a factory reset because, why not? Idk I'm kinda running out of ideas.

Actually, there is no sound on either end when using fb messenger or Google duo, as well. Video calls have no sound either. I guess I'm going to continue to keep talking to myself on here until I fix this phone or someone decides to help my stupid a$$ out. Oh, and and the fingerprint scanner doesn't work.

ufo8mymunky said:
Actually, there is no sound on either end when using fb messenger or Google duo, as well. Video calls have no sound either. I guess I'm going to continue to keep talking to myself on here until I fix this phone or someone decides to help my stupid a$$ out. Oh, and and the fingerprint scanner doesn't work.
Click to expand...
Click to collapse
I uploaded a2020u b12 android 9 firmware a while back, use unjustified devs edl tool to flash it, your fingerprint scanner does not work because the a2020g/u have different fp firmware, try flashing persist.img from a2020u to see if that fixes it, as for no microphone/audio incall, that could be vendor with wrong audio policy config xml, flash vendor.img from the a2020u to see if it will fix it.

rafyvitto said:
I uploaded a2020u b12 android 9 firmware a while back, use unjustified devs edl tool to flash it, your fingerprint scanner does not work because the a2020g/u have different fp firmware, try flashing persist.img from a2020u to see if that fixes it, as for no microphone/audio incall, that could be vendor with wrong audio policy config xml, flash vendor.img from the a2020u to see if it will fix it.
Click to expand...
Click to collapse
I tried flashing it. It said my device was corrupt. I am still on the A2020G but I got my service to work by flashing the non_hlos.bin from the a2020u from for the a slot and the non_hlos.bin from a2020g in the b slot. A weird side effect of that is now I have two data icons in the status bar(I'm gonna attach a pic because I think it's weird).
My fingerprint scanner was working after a fresh flash of the G variant. Once I flashed the U non_hlos.bin it went away and so did all my sensors. After doing the half&half flash, I got everything back but the fingerprint scanner. I'm going to wait awhile before I break the phone again.

karlnorth said:
@GrayFox1950 @Unjustified Dev @pmartin
I thought I'd offer the following after our last few posts on various threads. I'm a AT&T corporate engineer and have a friend who is a developer in our in-house Android device team. After much banging my head against my desk, I admitted defeat and reached out to him. After getting together for a few flights of high-end scotch, I now have a MiFlash flashable EDL of the NA Android 9.x v1.11 build. Once booted it shows up as "GEN_NA_A2020U_PROV1.11". Once it is running it received an OTA to v1.13. So now, I have my phone BL Unlocked, TWRP, Magisk and Xposed installed.
Currently I'm fighting an issue which occurs while writing large amounts of data to the external SD Card. If the phone goes to sleep while the copy / move process is ongoing, it WILL fail. If I tap the screen every 20 seconds or so, it works fine. When the data transfer fails, the SD Card disappears from the OS. A reboot brings it right back. (Weird, right?)
Ultimately, I want to be running Lineage 16.x with the phone storage decrypted. I just found an online archive of the the No-verity-opt-encrypt script. I'm wondering if they will work for our phones. https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
Any ideas on any of this
If you are interested, I can upload it to AndroidHosting.
Click to expand...
Click to collapse
by any chance do you still have that flash file on you that you can share or post im softbricked myself only can access bootloader mode and i cant seem to boot recovery twrp at all
i also cant find a flashable rom i keep getting "cant find flash script" or "cant find flash all bat" . i got miiflash up and running and it detects my ZTE Axon 10 pro otherwise and i have like two separate north america rom and it's driving me nuts because i cant find a way to flash them with mii flash or QFIL i get error messages in both programs and i feel like ive done everything ive could to try to get them to work. i just want to simple flash the android 10 rom and install magisk but now im stuck in bootcycle hell

Hi Electro, I do have the file. I'll upload it this afternoon to Android File Hosting and post a link for you. Okay?
Also, do you want your phone on Android 9 or 10? My EDL is going to be for 9.0. I'm simply not a fan of Android 10 on this device.
Plus I'm now running LineageOS 9.0 on mine. I really like the performance and flexibility of LineageOS versus the stock OS. (I still catch myself calling it CyanogenMod... Sigh)

yes please 9 if 10 is that bad ill take 10
---------- Post added at 12:44 AM ---------- Previous post was at 12:38 AM ----------
karlnorth said:
Hi Electro, I do have the file. I'll upload it this afternoon to Android File Hosting and post a link for you. Okay?
Also, do you want your phone on Android 9 or 10? My EDL is going to be for 9.0. I'm simply not a fan of Android 10 on this device.
Plus I'm now running LineageOS 9.0 on mine. I really like the performance and flexibility of LineageOS versus the stock OS. (I still catch myself calling it CyanogenMod... Sigh)
Click to expand...
Click to collapse
But yea totally give me android 9 EDL for the US model
also if you could after you post it could you outline the steps you took to get on LineageOS with Magisk i keep getting mixed signals from everything leaving me confused and this is like the 6th devices i've rooted
also im new to the mi tool i been trying to flash using like 3 other firmwares i been seeing laying around but get cant find flash.bat or the cant find mi hello packs. should it be done in bootloader or EDL mode plus any other settings i need to make sure are up. im sorry i know im asking a lot but i'd really appreciate any help
*also getting "Object reference not set to an instance of an object"

Futility's Forgotten Soldier said:
yes please 9 if 10 is that bad ill take 10
---------- Post added at 12:44 AM ---------- Previous post was at 12:38 AM ----------
But yea totally give me android 9 EDL for the US model
also if you could after you post it could you outline the steps you took to get on LineageOS with Magisk i keep getting mixed signals from everything leaving me confused and this is like the 6th devices i've rooted
also im new to the mi tool i been trying to flash using like 3 other firmwares i been seeing laying around but get cant find flash.bat or the cant find mi hello packs. should it be done in bootloader or EDL mode plus any other settings i need to make sure are up. im sorry i know im asking a lot but i'd really appreciate any help
*also getting "Object reference not set to an instance of an object"
Click to expand...
Click to collapse
I had the best luck with a Windows 7 Pro x64 PC running the 2017 build of MiFlash.
https://www.mediafire.com/file/zhlc5y7nkfxhhsa/file That's the full B12 Android 9 EDL stock package. Try restoring that.

karlnorth said:
I had the best luck with a Windows 7 Pro x64 PC running the 2017 build of MiFlash.
https://www.mediafire.com/file/zhlc5y7nkfxhhsa/file That's the full B12 Android 9 EDL stock package. Try restoring that.
Click to expand...
Click to collapse
It didn't work for me. I can't get miflash to work on my laptop.

ufo8mymunky said:
It didn't work for me. I can't get miflash to work on my laptop.
Click to expand...
Click to collapse
Sorry to bother but I recently got this phone and needless to say, I went the same route as you, but I am not sure how to flash correctly NON-HLOS.bin. I have tried another thread earlier as I had another copy of this phone (it was 6 gigs of ram instead) but that one went to edl boot hell. I know have the one with 12 gigs of ram and 256 gigs of storage. I tried karinorth's edl but for the life of me, miflash doesn't like it and on the tool, it says its missing files. I tried mixing files with the european edl and Karinorths at one point and somehow got twrp included ( I never installed it) but it would just bootloop after I tried to boot it up normally. Sorry for the long message but can you guide me on flashing the NON-HLOS.bin?

Oneplus 8T Device Corrupted

Hi everyone
I have a Oneplus 8t. Today morning when I woke up and opened my phone. It showed "Your device is corrupt. It can't be trusted and will not boot. visit this link on another device: g.co/ABH ".
I didn't try to install any kind of custom ROM and didn't download any apps directly from google.
I have really important documents on my phone and don't want to lose them.
When I opened fastboot, I got the following message
Product name: kona
variant: sm8 ufs
bootloader version:
baseband version:
serial number: 4274859a
secure boot: yes
device state: Locked
Please tell me how to proceed.
Kindly help.
You can also contact me at [email protected]

Wow this is weird one . so no recovery , custom kernel or roms or anything ha ?
and your bootloader is locked . how this happend is a mystery to me but i think you'll be able to
fix it with MSM tool and the unbrick guide which is availabe in the forums.

dlb4all said:
Wow this is weird one . so no recovery , custom kernel or roms or anything ha ?
and your bootloader is locked . how this happend is a mystery to me but i think you'll be able to
fix it with MSM tool and the unbrick guide which is availabe in the forums.
Click to expand...
Click to collapse
the phone switched back on its own after 1 day but now it keeps on switching off for no reason and sometimes it takes a day or two to switch back on

Question Rooting the Pixel Tablet

Just finished rooting my new Tablet.
Unlocked bootloader, Flashed new factory image and patched Magisk all by manual methods.
PixelFlasher didn't work as it does on Pixel 7 Pro, so save some time and wait for the official support.
Happy to help if anyone gets stuck.

Thanks for the update. Which file did you patch with Magisk to get root?
Are you passing Safetynet?

Rooted the thing 5 minutes out of the box.
Magisk stable. Passes safety net.
Follow a Pixel 7 rooting thread use the latest posted images, patch init_boot.img
I disabled verity too in case a custom kernel is done in the future.

bleez99 said:
Rooted the thing 5 minutes out of the box.
Magisk stable. Passes safety net.
Follow a Pixel 7 rooting thread use the latest posted images, patch init_boot.img
I disabled verity too in case a custom kernel is done in the future.
Click to expand...
Click to collapse
Would do the same. Thank you

MArtyChubbs said:
Just finished rooting my new Tablet.
Unlocked bootloader, Flashed new factory image and patched Magisk all by manual methods.
PixelFlasher didn't work as it does on Pixel 7 Pro, so save some time and wait for the official support.
Happy to help if anyone gets stuck.
Click to expand...
Click to collapse
I don't have the tablet, so the support file would greatly help to add official support for it.
Would you be able to provide it?
If not do you recall what exactly happened?
Was it during processing, patching or flashing?
Thanks
Update:
Aside from flashing, which I can't because I don't have the tablet, the latest version of PixelFlasher is able to process, extract init_boot and create a patch without any issues both for factory image and full OTA.
I even went as far as attempting to flash factory (without actually flashing) to inspect the final flashing script, and everything in there looked right.
I don't see how / where it could have failed, based on what I've seen it should work.
Hence a support file would greatly help if there is any issue to identify.
Thanks

just unlocking the bootloader w/PixelFlasher (latest ver.) "corrupted" my Slot B boot (Your device is corrupted) and it refuses to boot (grin).
Also, I'm pretty sure it said "no init_boot found" as part of device info. I can't confirm as I'm not with the tablet today.

ntegra said:
just unlocking the bootloader w/PixelFlasher (latest ver.) "corrupted" my Slot B boot (Your device is corrupted) and it refuses to boot (grin).
Also, I'm pretty sure it said "no init_boot found" as part of device info. I can't confirm as I'm not with the tablet today.
Click to expand...
Click to collapse
If you could provide a support file from PixelFlasher I can check, and you don't need to repeat the steps to get a support file, just launch PF and hit the support button or from the help menu.
If the unlock command has not changed, I don't see how it would cause that.
All the unlock button does is
if it is in adb mode, it reboots to bootloader mode and then issues the command
fastboot flashing unlock
If it is already in bootloader mode, it just issues the command.
I'm baffled and would really like to get to the bottom of this.

badabing2003 said:
If you could provide a support file from PixelFlasher I can check, and you don't need to repeat the steps to get a support file, just launch PF and hit the support button or from the help menu.
If the unlock command has not changed, I don't see how it would cause that.
All the unlock button does is
if it is in adb mode, it reboots to bootloader mode and then issues the command
fastboot flashing unlock
If it is already in bootloader mode, it just issues the command.
I'm baffled and would really like to get to the bottom of this.
Click to expand...
Click to collapse
soonest I could provide is 6 hours or so..

@badabing2003 yeah, I'll try to get that support file within the next hour. The tool said everything was successful but it always rebooted back to the bootloader when unlocking the bootloader or flashing a new image, thus I had to do everything manually
Update: @badabing2003 Support file is attached. Thanks!

I plan on rooting mine right away. Did anyone have a delay on their order? I have a trip coming up and it's supposed to arrive the day before.

Thanks @MArtyChubbs and @ntegra for providing support files.
@ntegra
Comments / observations based on your support file.
You started with Pixel 7pro,
You had an error during flashing
Code:
Sending sparse 'vendor_b' 3/3 (130768 KB) FAILED (Error reading sparse file)
fastboot: error: Command failed
rebooting to bootloader ...
Rebooting into bootloader FAILED (Write to device failed (no link))
fastboot: error: Command failed
Sleeping 5-10 seconds ...
flashing pf_boot ...
This is communication issue, phone unplugged or disconnected during flash or wire loose or bad driver / port / cable ...
But then you flashed p7p ok,
Moved to the tablet, which was locked at this point
Code:
Selected Device on 2023-06-20 20:00:50:
Device ID: REDACTED
Device Model: tangorpro
Device Active Slot: a
Device Mode: adb
Has init_boot partition: False
Device is Rooted: False
Device Build: TD2A.230203.028
Device API Level: 33
Device Architecture: arm64-v8a
sys_oem_unlock_allowed: 1
ro.boot.flash.locked: 1
ro.boot.vbmeta.device_state: locked
vendor.boot.verifiedbootstate:
ro.product.first_api_level: 33
ro.boot.verifiedbootstate: green
vendor.boot.vbmeta.device_state:
ro.boot.warranty_bit:
ro.warranty_bit:
ro.secure: 1
ro.zygote: zygote64
ro.vendor.product.cpu.abilist: arm64-v8a
ro.vendor.product.cpu.abilist32:
Device Bootloader Version: tangorpro-1.0-9584303
Magisk Manager Version:
Magisk Path: None
Checked for Package: com.topjohnwu.magisk
You proceeded to unlock the bootloader with PF
Which it did successfully
Code:
Selected Device on 2023-06-21 06:09:09:
Device ID: REDACTED
Device Model: tangorpro
Device Active Slot: a
Device Mode: f.b
Has init_boot partition: False
Device Unlocked: True
One thing to point out, after bootloader unlock, PF keeps the phone in bootloader mode (in case you might want to do other stuff)
But I think people tend to expect it to reboot to system, because I noticed this might have thrown you off seeing it in bootloader mode.
What I'll do for the next release is that unless you select no reboot option, PF should automatically reboot.
Another thing I noticed is that you attempted to create a patch while the phone is in bootloader mode
Which does not work, because that can only work in ADB mode.
In the next version I'll disable the patch button so that when in bootloader mode, you can't press it.
I see that you rebooted to system and the device was unlocked
Code:
Selected Device on 2023-06-21 06:14:41:
Device ID: REDACTED
Device Model: tangorpro
Device Active Slot: a
Device Mode: adb
Has init_boot partition: False
Device is Rooted: False
Device Build: TD2A.230203.028
Device API Level: 33
Device Architecture: arm64-v8a
sys_oem_unlock_allowed: 1
ro.boot.flash.locked: 0
ro.boot.vbmeta.device_state: unlocked
vendor.boot.verifiedbootstate:
ro.product.first_api_level: 33
ro.boot.verifiedbootstate: orange
vendor.boot.vbmeta.device_state:
ro.boot.warranty_bit:
ro.warranty_bit:
ro.secure: 1
ro.zygote: zygote64
ro.vendor.product.cpu.abilist: arm64-v8a
ro.vendor.product.cpu.abilist32:
Device Bootloader Version: tangorpro-1.0-9584303
Magisk Manager Version:
Magisk Path: None
Checked for Package: com.topjohnwu.magisk
Installed Magisk and created a patch.
All good.
You then proceeded to flash with
Flash To Inactive Slot: True
Everything about the flashing went well, but the phone stayed in bootloader mode.
I see now why that happened.
It flashed ok, but then it tried to flash the patched image to boot partition instead of init_boot partition.
PF detects if it needs to flash into init_boot partition or boot partition by doing two checks.
1- If it is defined in PF, and up to version 5.3.2.1 only defined are 'panther', 'cheetah', 'lynx' because at the time of the release only those were known. (tangorpro added in the next version)
2- By checking partitions and seeing if there is a init_boot partition, this way it would be forward working with future devices, but sadly due to oversight the code was looking for init_boot and expecting to find it, but there is init_boot_a and init_boot_b, and not init_boot, (fixed in the next version)
@MArtyChubbs
The flashing your tablet had the same fate as above, PF tried flashing boot partition instead of init_boot.
Fixed, I should have a release later today.
For anyone who cannot wait, and wants to use PF, all you have to do is before hitting OK to continue flashing, hit the Edit script before continuing button and modify the line
Code:
flash boot pf_boot.img
to
Code:
flash init_boot pf_boot.img
As for unlocking, I don't see errors, but I see that the phone was not detected,
Do you recall exactly what happened? perhaps it was showing the wipe message and hence why it was not really yet to be detected?
Code:
2023-06-20 16:58:12 Unlock Bootloader
*** Dialog ***
WARNING!!! THIS WILL ERASE ALL USER DATA FROM THE DEVICE
Make sure you first read either of the guides linked in the help menu.
Failing to follow the proper steps could potentially brick your phone.
Note: Pressing OK button will invoke a script that will utilize
fastboot commands, if your PC fastboot drivers are not propely setup,
fastboot will wait forever, and PixelFlasher will appear hung.
In such cases, killing the fastboot process will resume to normalcy.
Do you want to continue to Unlock the device bootloader?
Press OK to continue or CANCEL to abort.
______________
2023-06-20 16:58:14 User Pressed Ok.
Rebooting device REDACTED to bootloader ...
Waiting 5 seconds ...
2023-06-20 16:58:31 No Device is selected!
2023-06-20 17:12:46 Scanning for Devices ...
No Devices found.

@badabing2003,
Thanks for the response. great program, excellent support. For me, the first p7p failed (I agree with you) due to comm problem. I forget that the USB ports on one side of my laptop are flakey. I watched it bomb out writing system_b (I think) and just moved the cable to the other side and reran the flash to 100%.
For the tablet... I ran unlock twice (was still locked after first attempt). I "want" to say that the "your device is corrupt" was in between the two runs (unlock / reboot / device corrupt / unlock again) but definitely showing corrupt before first flash attempt. After a couple attempts to boot, I put it back into bootloader (and also download & recovery modes) and flashed the patched image, but it didn't help I'm guessing because of the init_boot(_b). Will be patiently waiting (neither slot are booting-grin) for your next release. I'm in no rush.

@badabing2003 I'd like to thank you as well! Love the tool and your excellent support. You and @Freak07 are such an asset to the community as are soo many other devs...

rester555 said:
I plan on rooting mine right away. Did anyone have a delay on their order? I have a trip coming up and it's supposed to arrive the day before.
Click to expand...
Click to collapse
No, arrived right on time.

MArtyChubbs said:
No, arrived right on time.
Click to expand...
Click to collapse
Looks like mine is coming on the earliest day of the planned shipping dates.

@MArtyChubbs and @ntegra
PixelFlasher 5.3.2.0 is released which adds support for Pixel Tablet.
There is also a dedicated support thread.
📳🔥PixelFlasher for Google Tablet Support Thread.
This is the support thread of PixelFlasher (PixelFlasher is an open-source self contained GUI tool to facilitate Pixel phone device flashing/rooting/updating with extra features). Note: This thread is meant for issues and problems faced in...
forum.xda-developers.com
Thanks for your support.

badabing2003 said:
@MArtyChubbs and @ntegra
PixelFlasher 5.3.2.0 is released which adds support for Pixel Tablet.
works a treat!
Click to expand...
Click to collapse

I got my tablet. Made the painstakingly slow mistake of updating the OTA before unlocking. The OTA takes forever.

Got my tablet. Had it rooted in less than 30 minutes.

rester555 said:
I got my tablet. Made the painstakingly slow mistake of updating the OTA before unlocking. The OTA takes forever.
Click to expand...
Click to collapse
Yep OTA on a device is very slow and is incremental, specially if you have to flash several times if you are free months behind.
Even if you don't unlock your bootloader, you can sideload OTA in PixelFlasher.