yashsingh1/xdaforums huggingface dataset:
[Google Pixel 3 Questions & Answers] RogerSC:
Here are the versions of adb and fastboot that I have (Minimal ADB and Fastboot):

Thanks for the thoughts about not re-locking the bootloader until I get the factory image flashed correctly, that was my original intent. But I'm not sure how long it will take me to figure that out, and how many more runs at this that I want to take.

As to how I got here, I noticed a few days ago that my idle battery usage had jumped up to over 2% per hour from about 0.5% per hour. I try to keep minimal apps on my phone, no reason that I could see for this jump. So I fiddled with settings for some time, and couldn't get the battery consumption back to where it was. I got rid of a few apps that I was carrying around for when I was traveling, and that didn't help. So I did a full factory reset to defaults, and reconfigured the phone manually, without using a backup. No difference. So I tried a factory default reset one more time, and made a really minimal configuration, not including even the Nova Launcher that I had switched to shortly after getting the phone. That didn't help the idle battery usage. At this point I figured I'd try sideloading the latest OTA, which I did. That really did help, but still not back to where I knew I the phone could be. I waited a day to see where things ended up, since I'm aware of the process of a new OS having to do a bunch of work to feel at home on a phone *smile*.

So here's where my thinking went off the rails, it would seem *smile*...I decided to unlock the boot loader to flash the latest full factory image and wipe my data. As I've done before with other phones. And then basically start from ground 0. That should give me the "best" results, in my mind. So I did that, unlocked the bootloader, but writing the factory image failed. In retrospect, I most likely should have given the OTA image more time to settle out, and have learned from jumping to the "best" solution before exhausting the potential of what should be an equivalent solution (an OTA with a factory reset to defaults).

At any rate, yes, I'll spend some time trying to figure out what I'm missing here, how to get the factory image flash to work. I'm not paranoid about having my bootloader unlocked, I just don't like the idea *smile*.

Thanks.
[Google Pixel 3 Questions & Answers] jd1639:
I'm 90% sure that the problem is you don't have the latest fastboot. So make sure you download the r28 revision of the sdk tools. With the older version somethings will flash, like the bootloader, but the rest will fail.
[Google Pixel 3 Questions & Answers] RogerSC:
Can you or someone else please point me at a download of the r28 revision of the sdk tools? Or should I try the latest version of Android Studio rather than the latest Minimal ADB and Fastboot that's worked for me in the past? I should be able to find these tools myself, but I'm not connecting with this version...must not be using the right google search strings *smile*.

Update: Never mind:

https://developer.android.com/studio/releases/platform-tools
[Google Pixel 3 Questions & Answers] jd1639:
Minimal adb is not updated. Just Google sdk platform tools. It's a zip file. Just extract it and put it all where ever your fastboot is now and over write your existing fastboot and adb.
[Google Pixel 3 Questions & Answers] sliding_billy:
https://developer.android.com/studio/releases/platform-tools
[Google Pixel 3 Questions & Answers] RogerSC:
Okay, did that, and re-flashed...seemed to go all the way through, but I see that my data was not wiped by "flash-all". That doesn't seem right. So I tried to run flash-all again to get the messages, but got this instead:

C:\adb>adb reboot bootloader

C:\adb>fastboot devices
89UX0H5VY fastboot

C:\adb>flash-all
Sending 'bootloader_a' (8489 KB) FAILED (Write to device failed in SendBuffer() (Too many links))
Finished. Total time: 0.312s
rebooting into bootloader FAILED (Write to device failed (Unknown error))
Finished. Total time: 5.000s
Sending 'radio' (71148 KB) FAILED (Write to device failed (Unknown error))
Finished. Total time: 15.015s
rebooting into bootloader FAILED (Write to device failed (Unknown error))
Finished. Total time: 5.029s
extracting android-info.txt (0 MB) to RAM...
fastboot: error: device doesn't have required partition product!
Press any key to exit...

So now I'm wondering:

1. What happened to the partitions, and how can I restore them?

2. How can I tell if the factory flash worked, despite not wiping my data?

Luckily my phone is still working as it was. And I still have the dream of getting it back to stock *smile*.

Thanks.
[Google Pixel 3 Questions & Answers] jd1639:
I'm sure all your partitions are still there. Did you edit the flash all to remove the -w? If you didn't I'm very surprised that it didn't wipe your device. I don't know what happened the second time you flashed. Possibly a bad USB cable, I don't know. But your device boots up ok?
[Google Pixel 3 Questions & Answers] RogerSC:
Yes, my phone still boots fine, and looks good. I tried flash-all again (haven't removed the "-w"), and got the same output as the above. So I'm really wondering what's going on here. I did reboot my phone between getting the quoted output above and then getting the same output with a second try.

Okay, just tried again, and this time different results, but still failures after a certain point. Got more output the first time, but again, no data wipe, so I don't think that worked, either. Seems like this should just work, but no:

C:\adb>fastboot devices
89UX0H5VY fastboot

C:\adb>flash-all
Sending 'bootloader_a' (8489 KB) OKAY [ 0.297s]
Writing 'bootloader_a' (bootloader) Flashing Pack version b1c1-0.1-5034669
(bootloader) Flashing partition table for Lun = 0
(bootloader) Flashing partition table for Lun = 1
(bootloader) Flashing partition table for Lun = 2
(bootloader) Flashing partition table for Lun = 4
(bootloader) Flashing partition table for Lun = 5
(bootloader) Flashing partition msadp_a
(bootloader) Flashing partition xbl_a
(bootloader) Flashing partition xbl_config_a
(bootloader) Flashing partition aop_a
(bootloader) Flashing partition tz_a
(bootloader) Flashing partition hyp_a
(bootloader) Flashing partition abl_a
(bootloader) Flashing partition keymaster_a
(bootloader) Flashing partition cmnlib_a
(bootloader) Flashing partition cmnlib64_a
(bootloader) Flashing partition devcfg_a
(bootloader) Flashing partition qupfw_a
(bootloader) Flashing partition storsec_a
(bootloader) Flashing partition logfs
OKAY [ 0.284s]
Finished. Total time: 0.774s
rebooting into bootloader OKAY [ 0.062s]
Finished. Total time: 0.062s
Sending 'radio_a' (71148 KB) FAILED (Write to device failed in SendBuffer() (Too many links))
Finished. Total time: 0.871s
rebooting into bootloader FAILED (Write to device failed (Unknown error))
Finished. Total time: 5.027s
extracting android-info.txt (0 MB) to RAM...
fastboot: error: device doesn't have required partition product!
Press any key to exit...

No idea where to go from here with these failures, and then that final message about partitions...
[Google Pixel 3 Questions & Answers] jd1639:
Something is not right at all with the flash. The output you posted is not close to what it should be. Are you sure you downloaded the right factory image? There's one that's domco, or something like that, which is not the correct one. That's for the Japanese pixel 3. I'm not sure if this will post correctly but the latest pixel 3 factory image is, Link

Edit, https://dl.google.com/dl/android/aosp/blueline-pq1a.181205.006-factory-af1829a6.zip
[Google Pixel 3 Questions & Answers] RogerSC:
Okay, did only two things:

1. Moved USB cable to a USB 2.0 port instead of USB 3.0 port.

2. Re-extracted the above .zip file (I did have the right one, by the way *smile*).

Not sure which one was the determining factor, but neither should have been a problem, by all rights.

The short story is that the full factory image flashed fine this time, and I've re-locked the bootloader on my phone.

Now, all I have to do is re-configure my phone, since data was wiped as expected this time around...I'm fine with that *smile*.

Now that was easy...great illustration of how dangerous a little knowledge can be in my hands *smile*.

Thanks for your patience, appreciate it.
[Huawei MediaPad M5  Guides, News, & Discussion] CorruptedSanity:
I found that by going into settings, then storage, then storage cleaner and cleaning about 3GB

My device for very snappy again.

Previously it took a second to open dual screen apps for example.

Just a helpful hint.
[Huawei MediaPad M5  Guides, News, & Discussion] sofir786:
I do this regularly, I've had my non pro version a month now and doing this every couple of days if it's had heavy use helps it perform better for sure
[Huawei MediaPad M5  Guides, News, & Discussion] jhs39:
What are you cleaning that takes up 3GB of space? Normally the system cache on Android devices takes up a fraction of that space so you are apparently deleting actual files, photos or other media.

Do you actually know what you are deleting or do you just let the cleaner remove whatever it chooses?
[Huawei MediaPad M5  Guides, News, & Discussion] CorruptedSanity:
I didn't answer earlierbecause I couldn't remember exactly what got culled.

Waited a bit for stuff to pile up.

Today the cleaner says I can ridmyself of 3.5 gb

See screen shot.

I'm not sure what it's cleaning.

It lists apps and sizes but not what is going to be deleted.
[Huawei MediaPad M5  Guides, News, & Discussion] jhs39:
I'm surprised your system cache is that large but I guess it is. Thanks for the screenshot.
[Galaxy Tab 4 Q&A, Help & Troubleshooting] mojorisin7178:
Hi I have had this tablet sitting in my draw for 2 years last night I couldn't sleep and decided I was going to get this thing working. So I did my homework and actually got it up and running. The only thing that seems to be a problem is it's not taking much of a charge. According to accubattery with the screen off it is only charging at 4 percent per hour. The charger I am using is a 3 amp charger. With the same charger and wire my old s5 gets 48percent an hour.

I installed the latest twrp. Los 14.1 12-19 build and magisk 18.0 for root.

Does anyone know of why it would be trickle charging like this? I am guessing it is something to do with the kernel but I don't know enough about kernels to mess with the settings. Any help would be greatly appreciated.
[Xiaomi Redmi Note 3 Questions & Answers] Anirudh44:
I have a kenzo snapdragon. Whenever I flash any rom like nitrogen,havoc etc. The device daoesnt boot. I get stuck on bootlogo cant boot into system. Previously i backed up the stock MiUi rom which came with the device. By restoring that i was able to get the device running and can use it. But now i had to format my kenzo and therefore i lost that backup. Now no rom is booting up for me. I have unlocked bootoader officailly and havw twrp installed. Please tell me what am i doing wrong. Why this roms arent booting up?
[Xiaomi Redmi Note 3 Questions & Answers] Black_Stark:
Make sure u came from latest miui rom 9 or 10.

Reason why its not booting is coz ur data and internal sd is encrypted . coz u came from miui. Miui encrypts data and internal sd by default. So custom roms cant boot it.

U need to format data in twrp.

Go to twrp

press format data.

Type YES to format

Format command will decrypt and erase ur data and internal sd.

So before that take backup of internal sd.

So first format data( must do)

Then wipe data reset

Flash rom

Flash gapps

Reboot
[Xiaomi Redmi Note 3 Questions & Answers] Anirudh44:
I did that. I also thought the same thing. Thats why i formatted data from twrp. And thats how i lost my backup. Bit it still isnt going past the boot logo for any roms.
[Xiaomi Redmi Note 3 Questions & Answers] Black_Stark:
What miui version u r now.? 10.1 stable?

When u take twrp backup u should choose external sd card.
[Xiaomi Redmi Note 3 Questions & Answers] Anirudh44:
I was on 7.3.6.0 miui which is the older version. Which came with the phone. I coulnt switch to any other rom. Cause it wasnt booting. Thats the main problem. And now i dont have that backup also
[Xiaomi Redmi Note 3 Questions & Answers] Black_Stark:
Lol.....:laugh:now i caught u.

Ur device is kenzo right???

U r on outdated 7.3.6 version. Ur bootloader is outdated.

download and flash this kenzo 10.1 stable firmware first.

Its 50mb zip file.

Go to twrp and flash this zip

Flash only if u r offically unlocked bootloader.

https://sourceforge.net/projects/xi...V10.1.1.0.MHOMIFI_a5f84d1b80_6.0.zip/download

After flashing firmware

U can Then format data

Wipe data reset

Flash rom

Flash gapps

Rebooot

It will succesfully boot.

---------- Post added at 02:30 PM ---------- Previous post was at 02:22 PM ----------

Use only twrp official 3.2.3 latest version

https://dl.twrp.me/kenzo/twrp-3.2.3-0-kenzo.img.html
[Xiaomi Redmi Note 3 Questions & Answers] Anirudh44:
Thanks very much mate.... But I didnt see ur reply and flashed global stable MIUI 10 rom on my device through mi flash. And guess what the device is working perfectly fine. So in that sense u were right. I think it would have been cause of outdated bootloader. But the sad thing is my bootloader got locked again.

Now have to wait 72 hours more for unlocking....
[Xiaomi Redmi Note 3 Questions & Answers] Black_Stark:
Lol...u selected" flash all and lock " option.

U should select "flash all" option.
[Xiaomi Redmi Note 3 Questions & Answers] Anirudh44:
Yes Im pretty sure i selected 'flash all' option. Not the lock option. But i did got locked.
[Xiaomi Redmi Note 3 Questions & Answers] Colossus96:
Even if u get locked again, u don't need to wait to get permission again. Just login to mi unlock app with the id u got permission in thw 1st place. Then just unlock the phone.
[Xiaomi Redmi Note 3 Questions & Answers] hiren29:
or else just flash lazy flasher....and decrypt the device
[Xiaomi Redmi Note 3 Questions & Answers] jimakos98:
I'm facing the same issue, where no custom ROM will boot, but I came form latest global stable miui 10.1 and also flashed the latest firmware you linked just in case and still I can't boot with any custom ROM installed. I have officially unlocked my bootloader and I'm using latest twrp. I followed your instructions but I still have this problem.
[Xiaomi Redmi Note 3 Questions & Answers] Black_Stark:
R u flashing magisk ?
[Xiaomi Redmi Note 3 Questions & Answers] jimakos98:
No, I

flash firmware

format data

advanced wipe --> wipe data, system, cust, dalvik / art cache, internal storage

flash rom

flash gapps

reboot

and get infinite boot logo animation.
[Xiaomi Redmi Note 3 Questions & Answers] Skew01:
If you use redwolf or orangefox recovery, no need lazy flasher. Orange fox contain magisk install menu.
[Upgrading, Modifying and Unlocking] overtones:
Dear Community!

I need your help! After factory resetting my Motorola G3 it stucks on logo. I can access bootloader and recovery mode, but even after doing factory reset again it gets stuck on the same place. I can run adb and fastboot and it recognizes my device, but I can't install new OS because the phone is locked. I also cannot unlock - after entering "fastboot oem unlock" and the unlock key from Motorola, I get the message

(bootloader) Check 'Allow OEM Unlock' in Developer Options.

FAILED (remote: '')

Finished. Total time: 0.020s

Probably, because I can't access the device's menu and allow rooting. I would appreciate any help! I am sorry, probably I made some mistakes in my explanations... Thank you!
[Upgrading, Modifying and Unlocking] Ibuprophen:
I don't have this device but, the following area of the forum is specific to your device.

https://xdaforums.com/2015-moto-g

Also, you should be able to obtain some member guidance within the following Q&A thread that's specific to your device as well.

https://xdaforums.com/showthread.php?t=3387661

Good Luck!

~~~~~~~~~~~~~~~

UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Enigma Machine {aenigma = Latin for "Riddle"}.
[Touch Cruise General] confusedxx:
I just got a Touch Cruise this weekend and love it so far.

But I find that I would really like to get 2 things for it:

1. a better keyboard. I know there is a learning curve, but I am not sold on any of the keyboards that came with the device. I heard there is a freeware keyboard that is much better. Anyone know of it?

2. is there an application like google maps or google mail that you all use to track stocks and see how your portfolios are doing? Something like this would make the device even more useful.

thanks,
[Touch Cruise General] LogLux:
Try out this keyboard: It's a little bit bigger than the standard one. I use it and it works great.

pocketcm keyboard

Google Maps can be found here: Google Maps Mobile v2.0.1.17
[Touch Cruise General] gnick666:
for the second one you can search for google2go... it's a hotlink collection for the IE. It launches as a normall app, and does include the mobile google finance
[Touch Cruise General] hambola:
PocketCM keyboard is great. a lot of good skins for it too.

For a maps program Windows Live Search Mobile is by far the best. Seriously one of the best apps from Microsoft and it's for free. It includes movie times, gas prices, maps with gps, speech recognition for addresses and business locations. I think it's only available in the US & UK though, so really depends on where you're at.

As for stocks I use Pocket StockCenter. You can setup your portfolio, number of shares for each symbol, amount paid, etc.
[Touch Cruise General] MusicArt1st:
or you could try Vitos' Zoomboard which is quite good
[Touch Cruise General] maevro:
While I agree PCM is a great keyboard, I have been using TouchPAL and have been happier.

http://www.cootek.com
[Touch Cruise General] confusedxx:
I just installed PocketCM keyboard but my Polaris continues to use the Old Keyboard. When I select PocketPC keyboard and then options, it says PocketPC keyboard must be the SIP inorder to Configure it.

What is SIP and how do I get the PocketCM keyboard to work?
[Touch Cruise General] hambola:
I've seen that as a bug sometimes, when you hit the small arrow by the keyboard icon and select PocketCM and it gives you that standard keyboard with the really small keys. Try resetting and selecting the pocket CM keyboard. Then you should be able to go into options and modify it.

Also search for SIP changer, there are tons of threads and the file is floating around. Allows you to set the default SIP on startup.

By the way SIP is "soft input panel" or something like that, it's basically the app that pops up that allows you to input characters whether it be the default HTC ones, default Windows ones, or something like PocketCM.

HTH
[Google Pixel 2 XL Questions & Answers] AshtonHunter:
OK so first of all, if this is the wrong place for this I'm sorry, it's quite late for me and I've been researching how to fix this for about two days and running up with nothing.

I recently upgraded to a Pixel 2XL, loving the device but unfortunately a couple of my apps save data into the data/data part of phone. The only way to then move that over and preserve the data is to use something like adb backup and restore. The backup seems to work fine, but so far every time I try to use restore on my pixel 2xl it 'ends' without actually adding the missing app data across.

I've tried using usb 2 and 3, no difference. I've made sure the usb debugging is on and that my phone is unlocked. I also made sure to try using the commands through both cmd and powershell and that both were in admin mode. I've also tried looking into other options like a friend suggested using es file explorer manager to change the download location, but I wasn't able to puzzle out a way to make something that was in data/data save elsewhere.

My phone isn't rooted, and I'd rather not go that far if I can help it. Any advice or ideas?
[Google Pixel 2 XL Questions & Answers] simplepinoi177:
Aahhh,"...your phone isn't rooted..."that's probably it/key. I'm unsure whether any kind of "restore" works without root access -- backup of course works because that simply involves "copying" and "storing" files (essentially the basic process of backing up) and, as the system needs to be able to read and access the data, you pretty much have the "read access" to it. Restore on the otherhand, for those who are unaware, are essentially "copying" those stored files and "over

writ

ing" the existing files -- which require "write access". The process of "rooting" is to acquire "root access" which allows both "read/write access" (therefore: "r/w access"). *again, for those who are unaware.

Sorry for just blabbering on about that, I guess I got carried away. In any case, basically (all in all, the reason why I blabbered on) I don't think you're going to go far without root access -- or "rooting" as you say -- but there is one thing I can suggest. When using adb, try running this command first before running any other adb command (i.e. restore):

adb root

It might just give you enough of that "root access" I was blathering about...

Also, among the all the things you made sure to do and include you made sure of, one thing you didn't mention is making sure you have the most up to date platform-tools (r28.0.1 *at least last I personally saw a few weeks ago).

Good luck to you, hope I made these things somewhat understandable, and hope this helped as well....
[Google Pixel 2 XL Questions & Answers] AshtonHunter:
Thank you for the suggestions, tried it but no dice sadly. I kinda am hairy on rooting it too as I just got the phone and it's been a long time since I've done android dev work. If you have any other ideas I'd be welcome to hearing them but again thanks for trying. :)
[Google Pixel 2 XL Questions & Answers] Strephon Alkhalikoi:
Where your bootloader is apparently unlocked, download a TWRP recovery image to the directory fastboot is in and boot it using the fastboot command "fastboot boot twrp.img". From there, take a nandroid backup of your device. Restoring is done in the same fashion. AND, since TWRP is memory resident when booting it this way, the stock recovery remains untouched.
[Google Pixel 2 XL Questions & Answers] simplepinoi177:
Great idea! And that's why veterans and those with experience are the best to go to...!
[Google Pixel 2 XL Questions & Answers] AshtonHunter:
OK so first, thank you so much for all the advice. I've taken awhile to get back to you because this took some time to parse. I'm admittedly kind of a novice at this. So I've used the instructions here https://www.xda-developers.com/how-to-install-twrp/ to try and install twrp. I think I did it right, had the zip contents and img file in the same directory that adb is in, then ran the command...and this is what I got back.

N:\platform-tools>fastboot flash recovery twrp-3.2.3-1-taimen.img

Sending 'recovery' (40960 KB) OKAY [ 1.203s]

Writing 'recovery' FAILED (remote: 'Flashing is not allowed in Lock State')

Finished. Total time: 1.219s

as the 'fastboot reboot' command appeared to bring me right back to normal operating for the phone I'm guessing the failed stopped me with that 'flashing not allowed in lock state' there. Am I missing a step?
[Google Pixel 2 XL Questions & Answers] simplepinoi177:
close, but not exactly right...

you got the downloading platform tools right, and putting the necessary files in that same folder that fastboot.exe resides in also right (you wouldn't believe how many novices actually make the mistake of not doing this)...

but you don't

ever

(underlined and emphasized not really for you AshtonHunter, but for any who are under the wrong impression; it's caused endless headaches and has even been complained by developers on Twitter...) "fastboot flash" TWRP with Pixels (any; and AFAIK any a/b slotted devices). You boot the twrp .img file. Also, for those who do not know and for future reference, there is no "recovery" for fastboot to "flash" to on Pixels (any), as there no longer is a separate partition for recovery; recovery resides in the boot partition. All in all, the command should be exactly this:

fastboot boot twrp-3.2.3-1-taimen.img

Immediately afterwards, you'll see your Pixel 2 XL restart and load up TWRP...

Good luck to you and hope this helps...