yashsingh1/xdaforums huggingface dataset:
[ZTE Axon 7 Questions & Answers] dnlilas:
Did you mean that you run Windows 32-bit so you can't use axon7toolkit (64-bit)?

To get back Qualcomm HS-USB QDLoader 9008 needed for MiFlash, in EDL mode, in Windows device manager, uninstall the driver QUSB_BULK and check option delete the driver. Unplug and replug the phone, then under unknown device QUSB_BULK install the Qualcomm HS-USB QDLoader 9008 driver from Qualcom bulk driver (qcser.inf).
[ZTE Axon 7 Questions & Answers] Whoooo?:
Hi there,

Yes, the version you linked doesn't work on Win 32 - hence I#m using this one: https://xdaforums.com/axon-7/development/tool-axon7toolkit-t3573108

Unfortunately it doesn't seem to support command line.

I reinstalled the Qualcomm drivers - MiFlash now detects the phone, but when I try to select the package it first complains 'cannot find script', then it shows an error 'cannot receive hello package' and times out after trying to reset the status... aaargh :(
[ZTE Axon 7 Questions & Answers] dnlilas:
For MIFlash problems, I already mentioned. I cannot even get MiFlash to recognize my phone, while similar tool like Qualcom Qfil/QPST can without problem.

You said "the version you linked doesn't work on Win 32" : I did not understand. Which one, axon7tool-1.5-win64.exe ? This is command line tool only.
[ZTE Axon 7 Questions & Answers] Whoooo?:
Hi there,

Yes, that's (one of) my problem(s), the axon7tool-1.5-win64.exe doesn't work (even in command line) on Win 7 32-bit. At least for me... :(

EDIT:

Aaaaaargh: MiFlash, 'Run as Admin' and the fastboot package flashed successful.... no problems by the looks of it.

Also no idea how to check if the bootloader is really unlocked...
[ZTE Axon 7 Questions & Answers] dnlilas:
OK I did not realize that you are running Windows 7 32-bit, this is why axon7tool-1.5-win64.exe (64-bit) of course could not be run.

I think the best for you is manage to find out a computer running Windows 64-bit and use axon7tool-1.5-win64.exe (EDL mode, QUSB_BULK WinUSB driver) to install TWRP (tenfar). Once TWRP installed, you can then use your Windows 7 32-bit to unlock bootloader, upgrade TWRP, flash stock ROM, flash custom ROM etc... all using TWRP as I mentioned previously.
[ZTE Axon 7 Questions & Answers] Whoooo?:
OK, got it (I think I will post a guide here soon, clarifying some things) -

I now hav unlocked bootloader and TWRP 3.1.

Question, with dm-verity, do I swipe to 'allow modifications' before flashing e.g. RR? Or do I flash a non-stock kernel first (or does RR use a different one)? And if, which one?

Sorry for the stupid question, I haven't read up on dm-verity before...

https://twrp.me/devices/zteaxon7.html
[Google Pixel XL Questions & Answers] mazubo:
Hi all,

*I've unlocked bootloader

* Have tried fastboot boot TWRP.img, as well as tried flashing TWRP RC1 via the Skipsoft toolkit.

Every way I've tried the phone just sits at the TWRP boot screen and doesn't allow me to go any further..

Any help here would be truly appreciated!

Cheers,
[Google Pixel XL Questions & Answers] dutchy716:
I've been having the same issue tonight. Re-flash the stock image, go through the whole setup process and make sure you add a lockscreen pin, then flash TWRP. That is what worked for me. I still can't flash a Rom though for some reason. It's driving me insane.
[Google Pixel XL Questions & Answers] jhs39:
You're braver than me. I haven't had my Pixel XL long but this is the first phone I've ever owned where I am afraid to try and install a custom recovery and ROM. With the dual partitions and what I hear about TWRP still being buggy it just seems like Google didn't want people to run anything but pure Android on the Pixels.
[Google Pixel XL Questions & Answers] mikefnz:
Same issue here, but no solution. Adding a lockscreen pin didn't change anything for me. I just get a teamwin image but it just sits there & doesn't actually open TWRP. My bootlocker is unlocked but thats as far as I can get 7.1.2 with May security. I have tried reloading everything and followed commonly recommended steps.

Any suggestions greatly appreciated. I would love to get this thing rooted and get some ROM flexibility - even to just get rid of the Nav Bar ....
[Google Pixel XL Questions & Answers] mac796:
I have never had a problem. Make sure your using the rc1 fast boot TWRP. Should be fastboot boot twrp.img. I change file name to this or copy and paste. Then you install rc1 or rc2 zip.

I know you will have problems if you try to install the wrong file.
[Google Pixel XL Questions & Answers] mazubo:
I am doing exactly as you mentioned.. flash rc1.img, however the phone does not go beyond the boot screen, it just sits there.... Can I ask what steps you are taking prior to flashing twrp? Thanks!
[Google Pixel XL Questions & Answers] XtraArrow:
Hmm are you on may bootloader because i think modifying the boot partition causes bootloop without the boot signature?
[Google Pixel XL Questions & Answers] mazubo:
Yes I am.. should I downgrade to 7.1.1? Tjere was no mention of that issue in the skipsoft toolkit thread... Weird!
[Google Pixel XL Questions & Answers] XtraArrow:
Sure, i guess.. or you could just manually flash the April bootloader. a lot easier.
[Google Pixel XL Questions & Answers] mazubo:
Ok, would flashing just the bootloader wipe the phone? Also how would I find just the bootloader? Thanks for the suggestion, I haven't flashed just a bootloader before..
[Google Pixel XL Questions & Answers] mac796:
That strange. I just flash a factory image from Google

Set up a security pattern

Enable adb debugging

Fastboot boot twrp 3.0.2-0 rc1 IMG

Make sure it asks for your security pattern if it doesn't reboot to bootloader and fastboot twrp again, and keep repeating until it does

Install twrp 3.1.0.0 rc2 or rc1 zip

If your using may bootloader's fish VBS 6 zip

And it should stick, if you flash. Anything else that messes with boot flash that VBS zip at the end again
[Google Pixel XL Questions & Answers] XtraArrow:
If you download the offiial april firmware, you can manually extract it from the .zip then you would do this command in fastboot :--------- fastboot flash bootloader PUTFILEHERE.img

EDIT: Are you able to get into TWRP by any chance??
[Google Pixel XL Questions & Answers] mazubo:
Hmm, maybe this is where I've gone wrong.. I thought the need to create a security pin/pattern was only if coming from a previously rooted state, or from a custom ROM. I will try this as well and report back.. thanks!
[Google Pixel XL Questions & Answers] mazubo:
Unable to get into twrp as previously mentioned. I flash the IMG file, then it just hangs on the TWRP boot screen..
[Google Pixel XL Questions & Answers] XtraArrow:
Alright, try doing what I mentioned. Download April firmware, extract the bootloader.img from it and flash using command above.
[Google Pixel XL Questions & Answers] mazubo:
This seems likely to work. Thanks for the suggestions, and I'll report back! Cheers!
[Google Pixel XL Questions & Answers] XtraArrow:
I'm no expert but it's seems like a decent suggestion. Let us know how it goes.
[Google Pixel XL Questions & Answers] freddy0872:
[MENTION=4147343]mazubo[/MENTION]

You keep stating that you just flash the image. Are you flashing it from the bootloader then trying to boot to recovery?

You have to boot TWRP from your PC first. Then from TWRP you can then "flash" TWRP.

Just wanted to make sure that was a step you were taking!
[Google Pixel XL Questions & Answers] defrt:
Just wait. It will take little longer
[Google Pixel XL Questions & Answers] mazubo:
Yes, I have tried fastboot to flash the TWRP img, as well as skipsofts toolkit. I guess I've been using the term "flash" for fastboot, as I haven't been able to use twrp yet.. I understand that you need to flash the TWRP img via pc and then flash the TWRP zip, then SuperSU or magisk, whatever your poison may be :)!
[Google Pixel XL Questions & Answers] freddy0872:
Okay just make sure that you have the .img file saved some where on your PC.

Also, save the twrp.zip file to your pixel

Then boot to bootloader

Once there run the following

fastboot boot "path/to/twrp.img"

(The path to twrp.img would be where ever you saved the img file.)

That should boot you to a "Temp TWRP" if you will. Once there you can proceed to install TWRP.zip as a normal zip file.

Just wanted to clarify your not flashing anything at the bootloader... your just booting the image from PC. :)
[Google Pixel XL Questions & Answers] mazubo:
Man, thanks for the detailed instructions, and sorry I was using the wrong terminology.. duly noted!
[Google Pixel XL Questions & Answers] freddy0872:
No worries my friend!

Did that solve your issue?
[Google Pixel XL Questions & Answers] mazubo:
Haven't had time to get back to the PC. I'll let you know once all is done! Cheers, and thanks again!
[Google Pixel XL Questions & Answers] mikefnz:
Thanks for taking the time to ID a likely solution to this issue. I was stuck with the same issue.

I'm afraid I gave up. After years of rooting HTC and Samsung phones, this one tripped me up. I wasted too much time and had to stop.

This thread at least helped me get rid of the damn nav bar and get a full screen back: https://xdaforums.com/pixel-xl/themes/how-to-enable-true-immersive-modes-t3554299/page3

I will have another attempt in a few weeks when I have more time. In the meantime, I will make do with Beta Andriod O.

Cheers
[Google Pixel XL Questions & Answers] ssingh819:
has anyone figured out how to use fastboot to boot twrp with the May 2017 android O update? (marlin-opp2.170420.019-factory-22308caf.zip)
[Google Pixel XL Questions & Answers] parakleet:
3.1.0 RC2 doesnt work for me. I get bootloops and cannot flash anything, also has an issue with decryption. Probably user error.

3.0.2 RC1 works fine.
[Google Pixel XL Questions & Answers] jacobkuczynski:
I'm having this same issue. I've flashed the April and May updates today and still twrp gets stuck as soon as i fastboot twrp onto my phone. I have not had this issue in the past. In the past it just went straight into twrp and asked for my pin. Is there any resolution yet? I have scrolled through the comments and tried different suggestions and no luck so far
[Google Pixel XL Questions & Answers] jacobkuczynski:
i just got this to work, i uninstalled find my device and i took android device manager off the access. I for s**ts and giggles decided to give it a try and sure enough twrp went through finally
[Google Pixel XL Questions & Answers] jacob5nights:
Still haven't found solution yet has anyone found a way to fix this issue?
[Google Pixel XL Questions & Answers] ByzLat:
No solution for me yet either.
[Google Pixel XL Questions & Answers] gubacsek:
I was spending days to get this work.... From TWRP's log, it looks like google changed something on the encryption and TWRP fails to decrypt the data partition.

Also there is an entry about failing to find the DRM device (graphic card?). For me it hangs with a black screen (fastboot boot twrp.img), but at least there is a working adb, so I am trying to manually install supersu. With no success of course... (i modified and ran the update-script, and flashed the boot image, but nothing happens after boot, like if i didn't change anything...)

I also started a thread about this, but no dev is picking up the problem. I'm not a developer, just playing around with things. I can't even compile a working recovery image myself.... I gave it today and if i don't succeed, I'll go back to 7.1.2. Can't live without my sound mods :D

It seems I'm the only one in the world, who want's to have a working recovery and root on the pixel.

If this is not the case, I'm willing to offer my help, trying to add something, test something. I'm open to any suggestions, a guide, at least how to compile TWRP for the pixel (to have the fastboot bootable image and so i can modify it ,and test it out a bit...). Anyone, who can add something, please contact me!
[Google Pixel XL Questions & Answers] jhs39:
I'm sure a lot of people would like to have working TWRP on the Pixels. The problem is that the people who program official TWRP can't even seem to do it. Google seems determined to keep people on stock with this phone. If you want to install a custom recovery and flash custom ROMs then the Pixels have to be among the absolute worst phones to own
[Google Pixel XL Questions & Answers] chrisjgg:
Possible solution???

So I had this issue after attempting to Flash oreo and it botched. I flashed back to the Verizon Factory image (7.1.0 - image-marlin-nde63x) After Flashing I was not able to boot into TWRP after setting up my phone. In order to fix this I spent a lot of time searching for the same answer you all were. I found that (From Nexus 6p forum) that in order to get past the splash screen I needed to boot to bootloader and Fastboot format userdata. This allowed me to boot into the TWRP.img but presented another issue as I could not mount a USB OTG drive nor copy the file from my PC to my internal storage. I did find that I could sideload the TWRP.zip file to my phone and it installed perfectly fine boot to twrp, advanced, ADB Sideload. Connect to PC > adb.exe sideload /path/to/twrp-3.0.2-0-RC1.zip.

I hope this helps you all.
[Google Pixel XL Questions & Answers] michaelbsheldon:
After alot of screwing up my PixelXL and going back to 100% stock, one of the main TWRP lessons I've

learned is that you can't easily work with TWRP unless you have booted the rom and set a PIN in Security.

Not doing that creates issues...
[Google Pixel XL Questions & Answers] dbroer91884:
So I know this is an older thread but I had this issue last night and figured it out...

Basically, the issue was for me was that I had updated to Android O then wanted to go back to Nouget to get a Nouget ROM. When I went through the process of doing a flash-all.bat, I noticed that everything seemed like it was flashed to both slot a and slot b....except the bootloader. For me, that was only flashed to the active slot.

So, I did the the flash-all.bat from fastboot on the active slot, let the device boot up and ran through the setup, then I went back to fastboot, changed the active slot using the "fastboot --set-active=_a" (or b) and redid the flash-all.bat. I was able to boot directly to TWRP using this image and able to flash within TWRP this recovery.

Two things I'm not sure of

1) I had set a screen pin because I had heard that was important. Not sure if it helped.

2) I probably could have only flashed the bootloader with fastboot flash bootloader command but again, I read to just redo the flash-all.bat so I did.
[Google Pixel XL Questions & Answers] Zwitterion:
This is very helpful. To clarify, you did the following:

1. Flashed the latest Nougat Factory image using the provided flash-all.bat

2. Booted up the ROM, set a PIN.

3. Rebooted into bootloader and then from your PC, ran ""fastboot --set-active=_a" (or is it b? you are unclear here).

4. Ran flash-all.bat again (though you say you think you could have just flashed the bootloader itself at this point since you've changed the active slot)

5. Then successfully booted to temporary TWRP via the RC1 Image and then actually flashed the RC2 zip once you were in TWRP

Some questions:

1. In 5 above, how did you get the RC2.zip onto the phone in order to flash it?

2. Have you flashed any ROMs successfully? If so, which one?

3. Have you rooted? If so, how?

I appreciate any and all guidance. I swapped my N6P for this phone and my regret is growing (despite knowing that the 6P was starting to fail). I had assumed a flourishing dev community around the Pixel, only to see that it's been a year and a proper TWRP (let alone a variety of ROMs) still doesn't seem to be available!
[Google Pixel XL Questions & Answers] dbroer91884:
So trying to remember exactly what I did. Keep in mind I was running Android O, which means the bootloader was also updated to the Android O version.

1. Downloaded latest Android N image.

2. Booted phone into bootloader, noted that my current slot was slot b.

3. Did the flash-all.bat on with latest Android N version.

4. Let phone then completely boot and go through setup (albeit I didn't input anything, I was just making sure I had a bootable slot)

5. Went back to bootloader use the "adb reboot bootloader" command (had to enable in developer options)

6. Since I was still on slot b, I switched to slot a using "fastboot --set-active=a".

7. From there, I ran the flash-all.bat command again. My thinking here was that even though slot a had the Android N information, slot b is still on Android O. Given that we know that TWRP isn't working great yet with Android O, I thought I should change both of them.

8. Let the phone boot up again.

9. This time I set a pin lock since I was going to now flash TWRP. I also connected it to the internet so I could download what I needed to.

10. Downloaded the TWRP RC1.img file and but that in my fastboot folder on my computer.

11. On my phone downloaded the TWRP RC2.zip.

12. Went back to bootloader using adb reboot bootloader

13. ran fastboot boot twrp-3.0.2-0-RC1-fastboot-marlin.img This temporary boot twrp. Since I had set a PIN, it asked for that, which seemed important because it was need to decrypt the data

14. In TWRP, flashed the TWRP RC2.zip.

15. Rebooted the phone and it stuck without issues.

As far as other ROMS I've used, I am using the PureNexus ROM on it. I don't have Root because I don't use it often. I did try to flash Magisk V14 and that failed, but I've not put any effort into figuring that out yet.
[Google Pixel XL Questions & Answers] Zwitterion:
This is superbly helpful - thank you so much for taking the time to go back through it! I am also on Oreo as it asked to update as soon as I booted the new phone and said what the heck. I will try this out and report back. It may be a day or two. I'll see if I can get root, which is most important for me as I want to run Franco Kernel to stop this horrible battery life!
[Google Pixel XL Questions & Answers] dbroer91884:
So did this help?
[Google Pixel XL Questions & Answers] Zwitterion:
I haven't had the opportunity to try and am, frankly, unsure whether I want to go Custom because my main desire is to run Magisk and it appears (from what you say) that this is not a possibility. I my just bite the bullet this weekend and flash Pure Nexus - I will be sure to let you know!
[Google Pixel XL Questions & Answers] dbroer91884:
Just so we all know magisk is now working on the pixel XL so I am now running custom recovery pure Nexus along with magisk and everything seems to be working.
[Google Pixel XL Questions & Answers] dcillusions77:
Had the same problem with Oreo firmware installed. Downgraded to Nougat and all is fine, with a bootable TWRP recovery. Seems like the ROM world for our phones is a booger for Oreo atm. So, I'm sticking to Nougat for now where I can have a bootable recovery without the need of a PC.
[One (M7) Q&A, Help & Troubleshooting] Bill720:
I bought this phone last year to test AT&T's coverage, but am considering promoting it to a more permanent position, so I am finally looking into some of its problems. This phone's camera takes pictures that are clear in the center, but blurry on the left (or top, when shooting in portrait) 20-35%, no matter what. There is a noteworthy dent on the back cover, so the question is if it is more likely that the problem is caused by the bent cover or by damage to the camera module itself. Any ideas?
[One (M7) Q&A, Help & Troubleshooting] daedric:
Either way, you'll have to remove cover, so when you do, take a picture without it. If the problem goes away, it's the back case, replace it.

If not, it might be the camera module, replace it. Either is pretty cheap on Ali, but if you remove the back cover, order a new one. It's almost impossible to remove it without damaging it.
[One (M7) Q&A, Help & Troubleshooting] Bill720:
Good idea; will try!

That's pretty much what I was planning after researching things a bit. I'll order just a screen first, then dismantle the device and replace the screen, but hold off on putting the back cover on until test pictures have been taken. I'm excited to get this phone back into working shape!
[One (M7) Q&A, Help & Troubleshooting] daedric:
There's A LOT of stuff you must remove from the screen, speakers, battery etc etc. It can be done, but pay attention.

Report back latter will you ?

Also, when you're putting the (new) back case on it, the top of the device goes first, not the bottom. Don't worry with the USB plug, worry with the power button/IR blaster and the top mic.
[One (M7) Q&A, Help & Troubleshooting] Bill720:
Not looking forward to it, but it should be an interesting experience

I'll report back with the results either way. I have seen the videos showing how involved the process is and am not looking forward to it. This should prove to be an educational experience in surgical precision, keeping track of parts, not losing screws, and remembering what order things get installed.
[One (M7) Q&A, Help & Troubleshooting] Bill720:
1 down, 2 to go

Screen replacement was a success! :laugh: But wow, that was a lot of work. This has to be one of the most time-consuming screen replacements in the entire industry. As for the camera problem, the issue does persist with the back cover off, so it looks like I'll have to source a new camera module as well as a new back cover (which got slightly damaged in the process).

I'll upload some photos as the project progresses.
[Huawei P10 Questions & Answers] tcdiem:
Hello all

(first post here, long time reader)

If you own a P10 (or P10 plus), could you please run geekbench and report the RAM results along your Aida64 and ddr_rod values? Maybe just the ram results if you have a phone you are certain is LPDDR4?

I've just got my P10 (plus) and trying to check where in the hw lottery I am. From all the forums/news/posts I've read, it is pretty clear how to find if you have eMMC, UFS2.0 or UFS2.1 - Androbench seems consistent enough.

But what about RAM types? On my two devices, Aida64 reports LPDDR4, but the "trusted" 'cat /proc/ddr_rod' reports lddr3 and someone posted (http://overseas.weico.cc/share/1011152.html?weibo_id=4097815745656061) that ddr_proc might report lpdd3 if the value is empty. Would be possible to distinguish it by its speed? Does someone here have knowledge on how much it should report for a device with LPDDR3 and LPDDR4?

Thank you

My values

P10 Plus (VKY-L29, not rebranded)

AIDA64 "Installed RAM": 6Gb LPDDR4

"/proc/ddr_rod": lpdd3

Geekbench single core mem copy: 4.67 GB/sec

Geekbench single core mem bandwidth: 17.2 GB/sec

Geekbench multi core mem copy: 7.85 GB/sec

Geekbench multi core mem bandwidth: 20.5 GB/sec
[Huawei P10 Questions & Answers] mertzi:
Single core

Memory Copy

1696

4.70 GB/sec

Memory Latency

3013

143.7 ns

Memory Bandwidth

3235

17.3 GB/sec

-----------------

Multi core

Memory Copy

2838

7.86 GB/sec

Memory Latency

3045

142.2 ns

Memory Bandwidth

3731

19.9 GB/sec
[Huawei P10 Questions & Answers] tcdiem:
I've just got some time to kill today and went to 3 different shops and benched their display phones (Germany - Bavaria).

On 4 different P10's I've found UFS2.0 (androbench 450-560 Mbyes/s) and 2000+ IOPS. But memcopy speeds about the same, except one which said bandwidth multi core 15GB/s.

On two P10 Plus I've got pretty much same results as from my initial post.