yashsingh1/xdaforums huggingface dataset:
[LG V35 Questions & Answers] AsItLies:
I'm sure all that was frustrating for you, but lets try to clarify it, especially so others can have the correct information.

You say if you have the stock abl and boot, download mode is almost guaranteed to work :) Which is pretty humorous as it's the laf partitions that are used in download mode ;) And it's not 'almost' guaranteed, it's 100% guaranteed, with the correct original partitions ;)

And you don't have to flail around trying a kazillion button combinations, as there is 1 combination that will always work; press and hold vol up while plugging into usb port. Boom. It works. Every time.

If that doesn't work, then the partitions are wrong, not the key combination you're using. So here's the situation with the partitions: The engineering abl can be used to get fastboot access, as known. You can get into fastboot with that partition directly after flashing it with EDL (qfil), even if you are on Pie. But you can not leave it there if you want to BOOT Pie, as it's an Oreo partition, and it won't boot unless it's Oreo.

Another way to get fastboot (although it seems to be a somewhat 'crippled' version of fastboot), would be to erase the laf partition (don't touch abl). This would give you fastboot but you would get to it the way you would normally get do download mode (remember download is the laf partition), because laf isn't there, you'll get a version of fastboot instead.

But if you use the 2nd method to get fastboot, (deleted laf), that means if you want to use download mode (lgup), you have to flash the original laf back first.

Hey, it's all fun and we're all learning some new things. I hope this helps to make it a little clearer. Cheers
[LG V35 Questions & Answers] Error-404-Go-Home:
Wow, thank you! That actually clears things up a lot for me (and hopefully other people :p) I am now restoring a backup of my UserData with TWRP and working my way around a lot of little issues, learning about stuff the whole way through. I hope to eventually get LineageOS working on this as I really liked it on the switch (hey, it works on the V40...), but that is going to take a lot longer to figure out :fingers-crossed:. Have a good one! :)
[Samsung Galaxy A3, A5, A7 (2017) Questions & Answe] Tonneff:
Hello, a friend of mine broke his samsung Galaxy A5 (2016) and it is unusable: broken touchscreen and black screen.

Unfortunately he is full stock (recovery too) and usb debugging is NOT active and i wonder if there is a way to activate or bypass it without touching the screen.

Thanks in advance.
[Samsung Galaxy A3, A5, A7 (2017) Questions & Answe] xgty:
Samsung Galaxy A5 (2016) broken screen, recover data

facing the same problem with stock Samsung Galaxy A5 (2016), broken screen (no display, no touch functionality) and disabled usb debugging.

tried to mount the device on pc as usual, but no success since i cannot touch the "yes" button.

i followed these steps to use adb on recovery mode with a hope to reach the files, but no success:

- wait until battery is drained, cause it is not possible to turn off the phone without touching :)

- boot into recovery mode (vol-up + power + home)

- "adb devices" -> no devices found

- selected "apply update via ADB" option from recovery (i figured this is the second option -from a screenshot on internet, i used volume and power buttons to select, without exactly seeing anything on screen:)

- "adb devices" -> now shows the device!

- "adb shell" exits with "error: closed"

- only "adb sideload" is possible at this point. any other adb command fails.

i am stuck and cannot recover files on the device. i think if i sideload a custom rom it will be possible to run "adb shell", "adb pull", etc. on recovery. but i dont know what to use and dont know if it is possible to flash a custom rom without seeing anything on screen.

any help from XDA community will be greatly appreciated!
[Mogul, XV6800 ROM Development] samuel1613:
got it at launch, afraid of roms but plunged in last week (finally).

Now it's got:

GPS radio (thanks DCD),

mapping (via GPSgate and iguidance)

total commander

HHC (plus all appearances)

pocket esword (and NASB)

calc-lite

skyfire

keep recordin'

and about 2 gigs of music

so now what?!?

What else do you guys do with these things?

(I don't run a web server, or need to do anything of that nature)

I am looking for other awesome things this thing can do, gaming? poker? video? audio? (anyone ever figure out a remote control?) anything... guess I'm just bored with it now that it's perfect...nuthin more to tweak
[Mogul, XV6800 ROM Development] rajuabju:
Let me know if you figure out how to make an ATM spit out tons of $$$ using the infrared :)
[Mogul, XV6800 ROM Development] peepeesea:
now you wait until DCD comes out with a new ROM so you can reflash and start all over again! its great fun i might add.

i'm sure with every reflash new problem will arise and you will spend countless hours on the forums trying to figure them out.

plus always be on the look out for new cool apps, they seem to pop up time to time
[Mogul, XV6800 ROM Development] samuel1613:
dcd's roms

while they are awesome, once I have it done, why go for another? to get an additional 2% ram available, to make it 8% faster after a soft reset? I mean there seems to be no reason to move to another rom at this point (unless it included a gameboy emulator and 300 games or something). I guess there's nowhere to go from here, time to get a new gadget!
[Mogul, XV6800 ROM Development] jambrose:
There is a remote control app that is suppose to be pretty good. Also there are some internet radio apps and I think Sprint has a online TV app but not sure if it works on other carriers or not. Go to Handango.com and you will find all kinds of apps.
[Mogul, XV6800 ROM Development] samuel1613:
I'm looking for free programs, i'm sure I can buy everything from calorie counters to budget analysers, I am looking for what people install that's free.
[Mogul, XV6800 ROM Development] jambrose:
www.freewarepocketpc.net

and other just google.
[Mogul, XV6800 ROM Development] ErikJDurwoodII:
Pong and a D&D Dice Roller
[Mogul, XV6800 ROM Development] samuel1613:
eBook reader, how did I forget!, good idea, will look through the freeware site, thanks!
[Mogul, XV6800 ROM Development] tedet:
music identifier - look at "musicid dxm"
[Mogul, XV6800 ROM Development] serfboreds:
The best things in life are not free. You are doing about 2-8% of what the phone can do using freeware.
[Mogul, XV6800 ROM Development] stlouisfinest68:
u can try smartphonejunkie.com
[Mogul, XV6800 ROM Development] samuel1613:
you're right, the best things in life aren't free, then they're cracked...

but please provide what single thing you use that you find most useful, barring what has already been mentioned, maybe i'll pay for it...
[Mogul, XV6800 ROM Development] samuel1613:
oh and I still cannot find an exe or cab for solitaire (googleing didn't help)
[Mogul, XV6800 ROM Development] jambrose:
Geocaching, that is basically free and fun for all ages.

www.geocaching.com
[Mogul, XV6800 ROM Development] samuel1613:
thanks again, I keep wanting to try that, after reading up on it, i laughed at CSI's attempt to include geocaching in a plot...
[Mogul, XV6800 ROM Development] jambrose:
It is a blast and my kids love it, especially trading the trinkets and tracking the travel bugs, plus it gets them outside and hiking around. :)
[Mogul, XV6800 ROM Development] samuel1613:
geocaching

I have iguidance and gps capabilities, but what's the best way to enter in some coordinates and track them down? how do you do it?
[Mogul, XV6800 ROM Development] jambrose:
there are lots of applications one that seems to have most of all the info and will import a GPX file is BeeLineGPS. Free for 30 days. This way you can export out geocaches on the site and import them to this app and then mark them found and I believe export your find list to check them off on the geocaching site. The have a link on geocaching about good apps to use as well.
[Mogul, XV6800 ROM Development] scrawnyb:
Woodpecker Software GeoScout :-)

the maps are a little mis-aligned on it, but other than that, it's really nice software that syncs up with geocaching.com
[Xperia SP Q&A, Help & Troubleshooting] moenachoneko2020:
I bought a Xperia SP M35t(China Mobile version with LTE)because of interested of it,but the Android version is too low(Just 4.1.2),and I can't connect to Google Services because it was deleted.

So I want to flash it to Android 7.1.1(Mokee rom),but when I to flash the recovery(TWRP huashan) to boot,it bricks.

I tried to use the Flashtool,but in Windows PC it can't install its drivers

And in another Kali-rolling PC (2020.2),I can't use Flashtool too.

I tried to flash all images myself,but when I flash the system.sin(unzip from an 12.0.c.2.58 ftf),the Fastboot(from Kali-rolling's debian sources and up-to-date)told me that it was too big.

Now I only flashed the kernel.sin,and I can only see a China Mobile's 4G Logo on screen and nothing works.

Any ways to solve it?
[Galaxy S II Android Development] linusdan:
Current state:

Working:

- PowerHAL

- Audio, including headset, bluetooth

- Wifi

- IMEI

- Touchkeys

- Camera Pictures

- Camera Videorecording

- Hardware encode/decoder

- Display

Not working/known issues:

- GPS

- BLN (Maybe never)

- Brightness button light

- HDMI (MHL) (support broken/removed since CM 10)

- Wallpaper (screen goes black even if alternating with another image)

- Home button (to minimize the problem, use gesture navigation of android 10 in Settings > Carbon Fibers > Gestures > System navigation)

Not tested:

- Sensors

- RIL (Phone/SMS)

- DRM, for e.g. Netflix

- Screencast (Chromecast)
[Galaxy S II Android Development] linusdan:
Changelog

13082020

Required recovery: TWRP 3.4.0-i9100 for Android 10

Initial release
[Galaxy S II Android Development] linusdan:
Vintage tee, brand new phone
[Galaxy S II Android Development] TriboDoP:
Just installed this rom. Looks very nice and works fine so far (no gapps installed). Love the bootanimation too!

Thank you very much!
[Galaxy S II Android Development] xdalurker1:
Bug report - RIL fails when attempting to call

Clean install, SIM inserted, carrier service signal OK after reboot.

Running phone dialer app when placing call - I get immediately 'no service' ('x' on carrier signal icon).

Only way to restore is reboot, but bug is persistant.

logcat url:

crash starts at line 869

RIL fails at line 1633:

TinyALSA-Audio RIL Interface: ril_connect() failed
[Galaxy S II Android Development] linusdan:
About magisk

I can't adapt for CarbonROM at the moment, because I need to download the source code to the HD and at the moment I don't have enough space. As soon I can, I generate the adaptation.
[Galaxy S II Android Development] ze7zez:
Clean ROM and no gapps, GPS Test shows no location

(No Fix). What do you mean by "Working GPS"?

.
[Galaxy S II Android Development] linusdan:
I knew I was forgetting something. Sorry :D
[Galaxy S II Android Development] linusdan:
OKEY

I decided not to continue with the maintenance of the bliss as it takes 2 times longer to compile due to the immense amount of fonts and other things that I have no idea what it is, doubling the file size and the costs with the server.

In order not to open another topic, I decided to modify this one and move on.

For anyone who was wearing bliss, sorry. Keep good memories.

Link of CR-8.0 build available on OP.

About magisk: Read here
[Galaxy S II Android Development] JaLoou:
Hello.

Sorry, if you are a real ROM developer then please look at the camera driver in the open source code published by Samsung for the model GT-I9100P, there mentioned a possibility to take pictures (and may videous) with 10bit per color component colour depth! (Currently our device can take 8bit photos only.)

Please, if you are programmer then make a ROM which takes 10bit photos (may 10bit RGB TIFF, 32bit per pixel PNG or at least 10bit RGB DNG).

I can offer bounty of 50USD if you will able to do it for me and for others.

May you can make this improvement to the device as a paid patch and sell it.

If you will achieve that then it will be a great step beyond for our old Galaxy S2.

I had attached a photo taken by our device and we can expect yet more rich colour improvement together with a significant dynamic range widening if 10bit colour depth will be achieved.

P.S.: May you can cooperate with the people from PentaxHack web-site.

[IMG="Colorful bush"]https://drive.google.com/file/d/1ueAyGnh0RLNBvgScN_EQ63ciXqEcYn5S/view?usp=sharing[/IMG]
[Galaxy S II Android Development] guest4711:
;)
;) ;) -;) ;) ;)
;) ;) ;) ;) ;) ;)
;) ;) -;) ;) ;)
;)
[Android Q&A, Help & Troubleshooting] imememe5t:
I need to root my phone which runs with Android 10 and since there are some restriction I need it rooted.

I've search in the internet but appears that there is no way right now. Is there still any way anyway?
[Google Pixel 3a Questions & Answers] captain sideways:
I know it's an old app but I used to use Drivedroid often for mounting and using iso/img files.

Tried using it with my 3a and I get the error message shown in the attached image.

I have read somewhere that USB Mass Storage Mode is part of the kernel; am I missing something simple that would allow me to enable it?

I've tried the stock kernel which didn't work, and I'm currently on ElementalX 2.14 which also doesn't work :(

Also tried the MKV kernel from here but couldn't even boot my phone with that?

Any help or pointing to further reading or resources would be greatly appreciated.

Thanks ?
[Google Pixel 3a Questions & Answers] captain sideways:
Ahh sorry the image upload hasn't worked but it's words to the effect that: no usb mass storage host can be detected.
[Google Pixel 3a Questions & Answers] bombadier:
Sure on the drivedroid thread there is a section with the necessary commits that would need to be added to the kernel to get usb mass storage working, you could try asking in the elemental thread if he would consider adding the required commits to the kernel
[Google Pixel 3a Questions & Answers] captain sideways:
Ah that's lush, thank you ?
[Google Pixel 3a Questions & Answers] bombadier:
Been a while so went and refreshed my memory with the drivedroid thread, the patches might not help with the USB mass storage issue, the patches are for USB/CD Rom drive emulation, definitely worth asking in the elemental kernel thread about it as the developer may have an idea why mass storage is not working with the pixel 3a, think the drivedroid thread mentions that elemental kernel was working on the old nexus 5 (hammerhead) phone,
[Google Pixel 3a Questions & Answers] captain sideways:
Yeah I'm just busy reading up on that myself, I had mentioned it in the EXKM thread a short while ago but didn't get a reply so I think the dev might be a bit busy? Thanks again :)
[Google Pixel 3a Questions & Answers] bombadier:
Just went and checked the elemental thread and saw you asked the question, think it got missed! Have you tried contacting the drivedroid developer to see if they could help troubleshoot the UMS issue?
[Google Pixel 3a Questions & Answers] captain sideways:
Nah I haven't contacted them, I think it's an abandoned project now :(

Which is a shame because it's really useful.
[Google Pixel 3a Questions & Answers] bombadier:
Think the drivedroid developer frozencow, is still active, try asking again in the elemental kernel thread and link to the drivedroid thread, haven't used drivedroid in ages but it is a mighty fine bit of software,
[Google Pixel 3a Questions & Answers] Prajjwal Rodger Massey:
Did you guys find a way around on how to enable and use USB mass storage option?
[Google Pixel 4 XL Guides, News, & Discussion] i5lee8bit:
[UPDATE/KEEP ROOT GUIDE] JULY 2020 (QQ3A.200705.002) "CORAL" Magisk/Stock Boot Images

IMPORTANT!! THESE FILES / THIS THREAD IS FOR PIXEL 4 XL "CORAL" ONLY, NOT PIXEL 4 "FLAME"!!

Here are the factory and Magisk Patched (v.24 is still the latest as of typing this) boot images for the July 2020 (QQ3A.200705.002) update.

**IT IS HIGHLY RECOMMENDED TO PATCH THE STOCK BOOT IMAGE YOURSELF, FROM YOUR OWN DEVICE, USING MAGISK MANAGER. WHILE THERE'S A GOOD CHANCE THE FILE I PROVIDED BELOW WILL BE IDENTICAL (USE A FILE HASH CHECKSUM TOOL IF YOU'RE CURIOUS), THERE IS ALSO A CHANCE THEY MAY HAVE SMALL, BUT SIGNIFICANT, VARIANCES**

Thanks for the info and link, [MENTION=5964313]wrongway213[/MENTION]

Link to [MENTION=4470081]topjohnwu[/MENTION]'s post: https://twitter.com/topjohnwu/status/1272136975022084097?s=19

ALL FILES BELOW ARE FOR JULY 2020 QQ3A.200705.002!

Magisk v20.4 Patched Boot Image: https://www.androidfilehost.com/?fid=8889791610682886725

Factory Untouched Boot Image: https://www.androidfilehost.com/?fid=8889791610682886726

Factory Untouched DTBO Image: https://www.androidfilehost.com/?fid=8889791610682886727

THESE FILES ARE FOR "10.0.0 (QQ3A.200705.002, Jul 2020)" ONLY! PLEASE ONLY FLASH IF YOU KNOW WHAT YOU'RE DOING!

Also, as most of us know by now, it looks like Google flipped HW attestation back on, and so SafetyNet will now fail (not just on July, but even previous builds). basicIntegrity test passes, but ctsProfile fails (due to hardware attestation method Google flipped back on), regardless of EdXposed / Magisk Hide status. Until people way smarter than us figure it out, if ever, I can't tell you how to fix it other than reverting back to full stock and locked bootloader. Oh well, carry on. Root is still more important to me anyway - for me the pros still far outweigh the cons.
[Google Pixel 4 XL Guides, News, & Discussion] i5lee8bit:
EASY UPDATE / SEAMLESS KEEP-ROOT UPDATE PROCESS

(using a PC - a very intuitive, effective, and relatively safe method).

** You can only follow this guide verbatim if coming

EXACTLY from build "10.0.0 (QQ3A.200605.001, Jun 2020)"

. But the general idea is the same for other builds, you just need the correct files for your device.

coral-qq3a.200605.001-factory-dtbo.img: https://www.androidfilehost.com/?fid=4349826312261824137

coral-qq3a.200605.001-factory-boot.img: https://www.androidfilehost.com/?fid=4349826312261824136

July 2020 sideload OTA zip: https://dl.google.com/dl/android/aosp/coral-ota-qq3a.200705.002-f7e8f879.zip

I DID NOT BOOT BACK INTO O/S UNTIL ALL STEPS WERE COMPLETED - I DID THIS TO ENSURE EVERYTHING WOULD BOOT BACK UP WITH MAGISK / EDXPOSED ALL RUNNING PROPERLY RIGHT AWAY

1. boot into bootloader

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

** I was on custom kernel, so I needed to flash BOTH the stock boot and dtbo images

2. fastboot flash boot coral-qq3a.200605.001-factory-boot.img

3. fastboot flash dtbo coral-qq3a.200605.001-factory-dtbo.img

......* these steps to restore stock recovery; dtbo.img also necessary for some kernel installations.

......* won't hurt to flash both anyway, so if you're unsure, go ahead and do both.

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

4. use volume keys to change selection to boot to Recovery Mode

......- when you reach the android symbol with No Command, hold power button, tap volume up, in case you've forgotten

5. choose option "Apply update from ADB"

6. adb sideload coral-ota-qq3a.200705.002-f7e8f879.zip

7. Once the OTA sideload is done, Reboot to bootloader (you'll also notice it's now on the other slot after OTA flashed)

8. fastboot flash boot coral-qq3a.200705.002-magisk_patched-20.4.img

9. done, start the phone

(Optional - Flash custom kernel. If you had a custom kernel, you need to re-flash it. I've only personally tested with Kirisakura though.)

*Kirisakura 4.7.5 seems to work fine so far!

This was a 100% seamless update that required no additional / re-setup of any of my Magisk or EdXposed setups. All of the factory files can be found here https://developers.google.com/android/images. boot.img and dtbo.img are in their corresponding full Factory Image zips, and the ota zip is under Full OTA Images.

SafetyNet not passing? READ OP AGAIN. (not fixable as of this posting)
[Google Pixel 4 XL Guides, News, & Discussion] i5lee8bit:
Issues after updating?

If you end up unable to boot or bootlooping afterwards, you most likely have an old Magisk module that isn't playing nice with the new build. There are 2 main things you can do:

1. Flash the new factory untouched boot image. You will of course lose root, and all modules will be disabled. However, it should at least get you able to boot back up quickly and have a working phone if you're in a bind.

2. I would recommend checking Tulsadiver's thread: https://xdaforums.com/pixel-4-xl/how-to/magisk-modules-disabler-booting-magisk-t3990557

Instead of reverting to stock boot image, fastboot boot (NOT FLASH) Tulsadiver's boot image. This will boot your phone in Magisk Core-Only Mode, with all modules disabled but root retained. From here you can open Magisk Manager and disable suspect modules. Before rebooting, go to Magisk Manager's settings and disable Magisk Core-Only Mode. Once you disable the incompatible module, the phone should boot back up.

- See this post (or thread) for more tips / context / an example: https://xdaforums.com/showpost.php?p=82509691&postcount=16

Coming from an earlier build than June 2020?

Download the July 2020 Full Factory Image .zip file and extract it. BEFORE RUNNING THE FLASH-ALL BATCH / SHELL FILE, EDIT THE FILE AND REMOVE THE "-w" FLAG FROM THE LAST FASTBOOT LINE. If you fail to remove -w, your phone will be wiped when it reaches this step. After flashing the full factory image, your phone will automatically reboot into O/S. From here, reboot back into bootloader, and flash the new Magisk patched boot image.

SafetyNet not passing? READ OP AGAIN. (not fixable as of this posting)
[Google Pixel 4 XL Guides, News, & Discussion] knopie:
Thanks again for this service, i have no issues.
[Google Pixel 4 XL Guides, News, & Discussion] wrongway213:
Just a friendly heads up - people should be individually patching their own boot images and not flashing patched boot images from other devices, as per topjohnwu himself

https://twitter.com/topjohnwu/status/1272136975022084097?s=19
[Google Pixel 4 XL Guides, News, & Discussion] i5lee8bit:
Thanks for the heads up! Didn't realize this. I'll update the OP when I get to my laptop. A while back I compared hashes of someone else's prepatched boot image to one I made and they were identical so I (incorrectly) assumed it would always be fine. Thinking about it more I can definitely see MM patching slightly differently based on current config, makes sense. Thanks for the direct reference too :good::good:
[Google Pixel 4 XL Guides, News, & Discussion] Skimpy007:
Anyone having battery issues with this update?

Dropped from 100% to 50% and then 18% in like 10 mins. Restarted phone and now stuck on 50%, doesn't change charging or discharging.
[Google Pixel 4 XL Guides, News, & Discussion] crisco654:
Hi. So I previously used your steps to flash to the June update. Now I'm trying to flash to the July update, but every time I try to enter recovery mode, it just reboots my phone. This is the first time this has happened to me, what am I doing wrong?

Really hope my phone isn't bricked without me installing anything new
[Google Pixel 4 XL Guides, News, & Discussion] i5lee8bit:
Did you already flash the June stock boot and dtbo images? Recovery won't boot unless you have stock boot image (changes to the boot image by custom kernels, and I believe Magisk as well, cause Recovery mode not to work).

You need to first boot into BOOTLOADER, then flash the stock boot and dtbo images. Only then you should be able to boot to recovery.

No issues with battery on either my phone or wife's phone (4 XL and 4) on July update with Kirisakura kernel... Sorry, but it sounds like it could be a hardware problem? D:
[Google Pixel 4 XL Guides, News, & Discussion] sidhaarthm:
Thank you for this useful guide OP - works a treat each time. I've been following it for the last 3 months :)
[Google Pixel 4 XL Guides, News, & Discussion] crisco654:
Thanks, this worked!