yashsingh1/xdaforums huggingface dataset:
[Xiaomi Mi Pad 4 Guides, News, & Discussion] Alex Kane:
This is the reported allocation on my device:

# fdisk -l /dev/block/mmcblk0

Found valid GPT with protective MBR; using GPT

Disk /dev/block/mmcblk0: 122142720 sectors, 2296M

Logical sector size: 512

Disk identifier (GUID): de1c6fbc-8d97-ad88-8aba-dd5af5595598

Partition table holds up to 64 entries

First usable sector is 34, last usable sector is 122142686

Number Start (sector) End (sector) Size Code Name

1 131072 138239 3584K 0700 xbl

2 138240 145407 3584K 0700 xblbak

3 145408 153599 4096K 0700 tz

4 153600 161791 4096K 0700 tzbak

5 161792 162815 512K 0700 rpm

6 162816 163839 512K 0700 rpmbak

7 163840 164863 512K 0700 hyp

8 164864 165887 512K 0700 hypbak

9 165888 166911 512K 0700 pmic

10 166912 167935 512K 0700 pmicbak

11 167936 172031 2048K 0700 fsg

12 262144 393215 64.0M 0700 boot

13 393216 6684671 3072M 0700 system

14 6684672 10878975 2048M 0700 vendor

15 10878976 10881023 1024K 0700 keymaster

16 10881024 10883071 1024K 0700 keymasterbak

17 10883072 10885119 1024K 0700 cmnlib

18 10885120 10887167 1024K 0700 cmnlib64

19 10887168 10889215 1024K 0700 cmnlibbak

20 10889216 10891263 1024K 0700 cmnlib64bak

21 10891264 10899455 4096K 0700 mdtpsecapp

22 10899456 10907647 4096K 0700 mdtpsecappbak

23 10907648 10973183 32.0M 0700 mdtp

24 10973184 11038719 32.0M 0700 mdtpbak

25 11038720 11563007 256M 0700 modem

26 11563008 12087295 256M 0700 modembak

27 12087296 12120063 16.0M 0700 dsp

28 12120064 12152831 16.0M 0700 dspbak

29 12152832 12154879 1024K 0700 abl

30 12154880 12156927 1024K 0700 ablbak

31 12156928 12158975 1024K 0700 dip

32 12158976 12158983 4096 0700 devinfo

33 12158984 12159495 256K 0700 apdp

34 12159496 12160007 256K 0700 msadp

35 12160008 12160009 1024 0700 dpo

36 12160016 12226863 32.6M 0700 splash

37 12226864 12226871 4096 0700 limits

38 12226872 12228919 1024K 0700 toolsfv

39 12320768 12337151 8192K 0700 logfs

40 12451840 12453887 1024K 0700 ddr

41 12453888 12453919 16384 0700 sec

42 12453920 12455967 1024K 0700 bluetooth

43 12455968 12458015 1024K 0700 bluetoothbak

44 12582912 12582913 1024 0700 fsc

45 12582920 12582935 8192 0700 ssd

46 12582936 12587031 2048K 0700 modemst1

47 12587032 12591127 2048K 0700 modemst2

48 12591128 12656663 32.0M 0700 persist

49 12656664 13180951 256M 0700 cache

50 13180952 13182999 1024K 0700 misc

51 13183000 13314071 64.0M 0700 recovery

52 13314072 13315095 512K 0700 keystore

53 13315096 13317143 1024K 0700 devcfg

54 13317144 13319191 1024K 0700 devcfgbak

55 13319192 13320215 512K 0700 frp

56 13320216 13451287 64.0M 0700 logdump

57 13451288 13455383 2048K 0700 sti

58 13500416 13500671 128K 0700 storsec

59 13631488 13893631 128M 0700 rawdump

60 13893632 13893759 65536 0700 vbmeta

61 13893760 13893887 65536 0700 vbmetabak

62 14024704 15728639 832M 0700 cust

63 15728640 15795487 32.6M 0700 logo

64 15795488 122142686 50.7G 0700 userdata

Although both system and vendor partitions on your unit are ext2 (instead of ext4), your partitions look fine to me and don't need any resizing.

You could try to re-format system and vendor using either TWRP or a root shell.
[ASUS ROG Phone II Questions & Answers] RogPhoney:
So everyone knows, Verizon refused to allow my Verizon SIM cards to work on my Tencent Chinese version of the ROG Phone 2. They said the IMEI is not approved for use on their network (I tried both IMEI for both SIM slots and got the same result). They claim to have no way to make an exception to allow the phone and that Asus would have to go through the certification process for the China models (which they will probably never do).

The phone works fine with T-Mobile since they don't seem to require a certification process for phones to be used on their network.
[ASUS ROG Phone II Questions & Answers] Caffeine Cup:
Ah, that's really unfortunate. Hopefully the international version will work with Verizon. The ROG Phone 2 is so close to being perfect, but if it can't be used on Verizon that will sour the experience for a lot of people in the states.
[ASUS ROG Phone II Questions & Answers] JazonX:
Try writing to Asus support?
[ASUS ROG Phone II Questions & Answers] Pointmanipo:
Very strange, put in my Verizon sim yesterday and got data out of the box with 4G+. Called Verizon and gave my IMEI they said it registered on the network and submitted a form to have it added. S/b active today or tomorrow.
[ASUS ROG Phone II Questions & Answers] Mr_Mooncatt:
I know another user here got it working as data only on Verizon and using Google Voice for calls and text. Are you saying the form you submitted is to get voice and texting working as well without that work around?
[ASUS ROG Phone II Questions & Answers] Pointmanipo:
Yes, but the Tech support rep submitted it on my behalf, I checked this morning and its still sitting in the queue.

Supposedly takes a few days.
[ASUS ROG Phone II Questions & Answers] Mr_Mooncatt:
Cool. If you get it fully activated without that work around for calls, Asus may need to ramp up production. There's a lot of us Verizon users chomping at the bit for it. Lol
[ASUS ROG Phone II Questions & Answers] Pointmanipo:
I totally understand, I bought mine from Ebay seller in Hong Kong. Its the Tencent version with WW rom and 12/512 just to clarify.

Hope that helps?
[ASUS ROG Phone II Questions & Answers] Mr_Mooncatt:
If I get it, it'll be the official U.S. Version. But good luck. If it works for you, that may be good news for the rest of us. The only issue I see is lack of frequency support on the Tencent version.
[ASUS ROG Phone II Questions & Answers] docfong:
I wouldn't even bother. Verizon has some of the worse support for unlocked devices unless it's an Apple or Samsung of course! So frustrating..
[ASUS ROG Phone II Questions & Answers] Pointmanipo:
Yes indeed, still waiting for the Status.
[ASUS ROG Phone II Questions & Answers] suzook:
I have been saying this for over a week. Unless we can somehow get VOLTE working, VZW users are screwed. Why not just use google voice??
[ASUS ROG Phone II Questions & Answers] Pointmanipo:
Yes indeed you have.
[ASUS ROG Phone II Questions & Answers] RogPhoney:
So, does data work in any form on Verizon with the Tencent version? I just tried today (Nov 5th) and all the Verizon phone reps including managers who've been there years are claiming it is impossible to add the IMEI because the Rog Phone II still hasn't been added to their list of phones.

If anyone else really did get it to work, please clearly explain your steps.
[8525, TyTN, MDA Vario II, JasJam ROM Development] rock99rock:
The device is Holux GPSlim 236. The phone is Hermes. The phone will pair without question on a 6.0 rom, does not matter who cooked it.

It will specifically not pair with 6.1 roms.

I can see the device when scanning for bluetooth devices, i can choose it, it asks me for passcode, but will not accept the "0000" as the passcode. (tried hardware and software keyboards). IF i type in a passcode OTHER than "0000", it appears to pair, i can see the spp slave service and select it, but once the gps software tries to talk with it, it asks to pair again.

Something is definitely different in the pairing process between 6.0 and 6.1.

Any suggestions are greatly appreciated.

Also see thread about it here from the Himelaya:

http://xdaforums.com/showthread.php?t=378103

Thanks,

Rock
[8525, TyTN, MDA Vario II, JasJam ROM Development] ai6908:
Did you select it as a serial port? You have to do this after you pair the device with the phone!
[8525, TyTN, MDA Vario II, JasJam ROM Development] blackout128:
I am not familar with gps units, does it have a pairing mode like a headset? I know with my Plantronics headset, if I let my phone discover it without the headset being in pairing mode, the phone says it pairs with it, but it really doesn't, so I put it in pair mode then turn on bluetooth on my phone and pair up as normal(0000 passkey) and all works fine.
[8525, TyTN, MDA Vario II, JasJam ROM Development] Wam7:
I have exactly the same GPS unit and have no problem pairing it with the probably 15+ WM6.1 roms I have tried.

Try leaving the battery out of the 236 slim for a few minutes and see if that helps. (can't remember is there is another way to reset it)
[8525, TyTN, MDA Vario II, JasJam ROM Development] Hissing Syd:
Bluetooth Pairing with 6.1

In the latest PC Pro magazine in the UK, there is an article on WM 6.1. It says:

"There's another neat feature in WM 6.1, namely that when you try to pair the phone with something like a GPS dongle or hands-free kit that has a fixed PIN, the operating system will cycle through a set of common codes (0000, 1234, 8888 and so on) to try to find the right one."

It goes on to say that there is the potential to get locked out of the pairing if it goes wrong.

I have to say that I have not had any problems pairing with my GPS unit and my car kit, using a number of 6.1 ROMs. Indeed I have seen no evidence of the above software routine trying to pair for me. Possibly, that routine will only appear in the production ROMs, rather than the development ones which we use on XDA Developers.
[8525, TyTN, MDA Vario II, JasJam ROM Development] dan1967:
I had issues with the same device on some roms. I eventually changed BT drivers from WM6 and all went back to normal.

On some WM6.1 roms things went OK though.
[8525, TyTN, MDA Vario II, JasJam ROM Development] miffymiffy:
Try not using any password when you try and pair it manually.

If it asks would you like to pair your device automatically select no and do it manually.

I was having this problem but WM6.1 does not require a bluetooth passcode for most devices.
[8525, TyTN, MDA Vario II, JasJam ROM Development] crusti:
mines gps is a holux 240 and i have the same probs :(

ive mentioned it on a couple of threads, im glad to know im not the only one

im stickin with K's 6 final until this problem gets sorted out
[8525, TyTN, MDA Vario II, JasJam ROM Development] crusti:
this thread doesnt seem to getting any viewing, so im asking could a mod move this to General Discussion>networking please, it might be sutible there
[8525, TyTN, MDA Vario II, JasJam ROM Development] rock99rock:
ummm no, dont move my thread thanks. you can start one over there if you would like.
[8525, TyTN, MDA Vario II, JasJam ROM Development] rock99rock:
You are not the only one :D

I reverted back to the 6.0 and it pairs without issue. I am thinking that alot of these cookers do not pay much attention to the development of bluetooth in some of their roms. Its not like I changed something on the GPS, so something must have happened with the software.... Still investigating. I hope it works on schaps new rom.
[8525, TyTN, MDA Vario II, JasJam ROM Development] rock99rock:
this method paired my jabra automatically, it didnt even ask if i wanted to do it auto, i juck clicked "pair" and there it was.

When pairing the holux 236 on the other hand, it would ask for a passcode, then reject it if you put in the correct code of "0000". If you canceled it, it would appear in the connected devices list!!, but still ask to pair once the gps application tries to connect. VERY jacked up.
[8525, TyTN, MDA Vario II, JasJam ROM Development] rock99rock:
Did that article describe any way of disabling that feature? That functionality could easily trick a simple bluetooth device if it is not expecting such a rampage of codes...
[8525, TyTN, MDA Vario II, JasJam ROM Development] Hissing Syd:
No, there was no mention of if it could be disabled.
[8525, TyTN, MDA Vario II, JasJam ROM Development] rock99rock:
Wam, which rom are you using now that it works with? id like to download and try it. The 5 or so ive tried did not work.

I power cycle the device without any change in pairing succession.

Thanks!

BTW: Other users experiencing differences between 6.0 and 6.1

http://xdaforums.com/showthread.php?t=391488

http://xdaforums.com/showthread.php?p=2240665
[Google Pixel 3a XL Questions & Answers] DanHakimi:
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...
[Google Pixel 3a XL Questions & Answers] sic0048:
Send it back. It sounds like a hardware issue.
[Google Pixel 3a XL Questions & Answers] DanHakimi:
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?
[Google Pixel 3a XL Questions & Answers] GuestK00292:
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:
[Google Pixel 3a XL Questions & Answers] acejavelin:
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.
[Google Pixel 3a XL Questions & Answers] DarkShadowMX:
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!
[Google Pixel 3a XL Questions & Answers] krabman:
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.
[Google Pixel 3a XL Questions & Answers] DanHakimi:
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.
[Google Pixel 3a XL Questions & Answers] GuestK00292:
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).
[Google Pixel 3a XL Questions & Answers] krabman:
Again, just to be sure, you are using a USB A to C and not a C to C, correct?
[Google Pixel 3a XL Questions & Answers] DanHakimi:
I don't have a USB-C mouse, but I guess I could keep trying images until one of them works...
[Google Pixel 3a XL Questions & Answers] DanHakimi:
Yes, A to C.
[Google Pixel 3a XL Questions & Answers] DanHakimi:
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...
[Google Pixel 3a XL Questions & Answers] GuestK00292:
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.
[Google Pixel 3a XL Questions & Answers] krabman:
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.
[Google Pixel 3a XL Questions & Answers] DarkShadowMX:
I don't either. I used a USB OTG cable
[Google Pixel 3a XL Questions & Answers] seniorstew:
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
[Google Pixel 3a XL Questions & Answers] oranget:
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.
[Google Pixel 3a XL Questions & Answers] DanHakimi:
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...
[Google Pixel 3a XL Questions & Answers] sic0048:
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.
[Google Pixel 3a XL Questions & Answers] DanHakimi:
Ah -- I tried to make space just in case that was it, but... I don't know, I guess I'll try making more, and get back to you.
[Google Pixel 3a XL Questions & Answers] DanHakimi:
Well, I had >16b free when I ran this. A slightly different pile of errors, but mostly the same.

I notice that the files it says are missing from my archive -- boot.sig, etc. -- are not actually present anywhere in the images I downloaded from Google. Should they be? The zip files mostly only contain .img files, not .sig files, and not "recovery.img."
[Google Pixel 3a XL Questions & Answers] krabman:
You have a flashing error but do not know what it is, again, you need to do the whole smash. You need to verify your environment by downloading the latest You need to make sure you are using a good cable, switch to a different one or even several, it should be A to C. Make sure the port you are using is on the main board, if you don't know switch to a different one, never flash from a powered hub. Make sure you have plenty of extra space on the drive. You probably have a portable drive, make use of it. If you don't, one of your friends does, make use of it. However you do it get the space you need, it should be gigs, not bytes. Before you flash the image you need to delete boot and system, I gave you those commands earlier.

You get the idea, you need to do what it takes to sort out your flashing error which can only be done by verifying you are good in every detail. I'm going to leave a link with very detailed instruction on how to get out of a soft brick. Follow it and your phone should flash successfully. Good luck.

https://xdaforums.com/pixel-3-xl/how-to/guide-progress-available-t3876849
[Google Pixel 3a XL Questions & Answers] DanHakimi:
How in the world would I know what cables are good and bad? My cable is benson leung approved for power, but I don't know any list of cables that are good for flashing.

I definitely don't know which of my USB ports are on the main board, and don't have the energy to sit around and try every single thing I'm going to try with each of the three ports and every cable I can find and every different version of the rom (which I keep deleting to keep the maximum amount of space free on my laptop), and then try it all again on a different laptop... There has to be a way to figure out what the problem is without doing everything that could possibly be done.
[Google Pixel 3a XL Questions & Answers] sic0048:
Did you try re-downloading the image from Google? For whatever reason, the download you are trying to use isn't complete or got corrupted. Perhaps Windows removed some of the files when it was trying to free up space, (ie remove temp files, etc)
[Google Pixel 3a XL Questions & Answers] krabman:
I was having a flash failure just a few months ago, I verified the download, went and got the latest fastboot, already knew I was on a good port and finally turned to the cable. That cable was one I had used to flash for a few years, should be good, right? Yeah, no, it turned out it wasn't good, somehow it had got damaged. I figured that out by walking out to the car, getting the cable from there, going back inside, flashing again. Only that time successfully.

You are making it way too hard. You probably have a spare cable laying around, try it. If you don't one of your friends does, borrow one. USB ports are usually grouped together on a PC. If the three on the front aren't working try one of the three on the back. A few flash attempts later will tell you if your USB port isn't cooperating. You have already downloaded multiple imagines and they all fail, that is very unlikely, I'd look there last. Your environment is a real suspect, nowadays you don't have to go through an installation as they run in a container. Downloading the latest takes a few minutes.

All the things I described to you I could check in about 20 minutes. It will take you longer because based on your last post you are not familiar with recovering from soft bricks. Getting out of it isn't that hard but you have to follow a process of elimination because there is often no smoking gun and failures can manifest as random. Follow the link, it is a guide with clear and simple instructions and all needed links that will walk you through the process. You should be done in half an hour if your familiar with these processes. More like an hour if you are less familiar, maybe an hour and a half tops if you are completely unfamiliar with it. Or you can keep posting and wishing that someone here will give you the magic bit of information needed to quickly and easily solve your problem with little to no effort. The latter isn't likely to happen. I cant verify your cable, I cant check your MD5, etc. I'm not trying to be a Richard, if you want to get out of a softbrick you have to do what people with soft bricked phones do to get them running. It's easy, go to the link, follow the instructions, you'll be running in no time.