yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] JesusFreke:
Also, in case it doesn't have a recovery image with test-keys, you might try connecting to the phone with adb shell from your computer. do you get a $ prompt or a # prompt? If you get a $ prompt (non-root prompt), try typing "su", and see if it goes to a # prompt.

If you can't get root via the above, try rebooting the phone, and then once it's back on, type <enter>reboot<enter> on the keyboard (it doesn't matter what application is up, if any). If that causes the phone to reboot, then you can follow the instructions posted elsewhere to get root access on a normal pre-RC30 G1.

Finally, if none of the above work, try booting the phone into spl mode. Turn off the phone, and then boot it with back+power. If it boots up to a white screen with skateboarding androids then you can use the fastboot program to connect to the phone, which will allow you to flash a different image onto the phone. If you see colored bars instead of the white screen, you're out of luck.
[G1 Android Development] spiritofseth:
ok here are the version numbers

DREA100 DVT2-1 32B

HBOOT-0.95.0000

CPLD-4

Radio-1.22.12.28

Sep 2 2008

Serial0

Also, she can reboot from the terminal in the background so I guess she is in luck, next step would be to place a dev bootloader I presume?
[Moto G7 Play Themes, Apps, and Mods] chuy19312:
I decided and learned to use Moto Bootlogo Maker, so i wanted to create an actual black logo.bin with Motorola Logo by editing an already existing logo.bin file, flashable via TWRP but in case you want to flash it on fastboot, open the zip file and extract logo.bin, then use this command

fastboot flash logo logo.bin

Sadly, it doesn't remove n/a or bad key messages since i do not know how to do it.

Edit: added an fastboot with black logo file, you only need to open the Fastboot flash logo.bat file to simplify flashing on fastboot
[Moto G7 Play Themes, Apps, and Mods] pappyN4:
@chuy19312

Which ROM did you get your file from? I grabbed the official Android 9/10 RETCA and RETUS file from lolinet and used https://xdaforums.com/t/mod-win-bootlogo-change-your-splash-screen-and-various-graphics.3182994/ to unpack. I was thinking a little lock could cover up the "N/A" while still being a simple clean darkmode logo.

But when I repacked it, I never got any image to load. Flashing yours worked, but in a hex editor there's a difference in file names between the two mods so I'm not sure I used the same source. RETCA is the correct one for my phone. Comparing the MotoInjector repack, its the same as the original RETCA version + difference in image sizes. I also tried updating the unlocked/red/orange/yellow file locations with no success.
[Moto G7 Play Themes, Apps, and Mods] chuy19312:
I got it from an logo file i found, i don't remember where i did found it, i had it like an year ago and i did only modify the images on the logo to create an mod

Also, i did use the Moto Bootlogo maker to edit it from here

[TOOL][Moto Bootlogo Maker][Moto G7 Play]

• This tool was created by CaitSith2 in 2014, published in this thread. Tool for creating bootlogo files, for a number of Motorola Devices, but time later in at the end of 2015 it was abandoned by the creator. Now, Nemesis Team will maintain and...

xdaforums.com

Maybe you will get success if you use this program, in my case, i use the Moto G7 Play MetroPCS variation and it does work without problems
[Moto G7 Play Themes, Apps, and Mods] pappyN4:
Figured it out. For some reason whatever calls the pictures (bootloader i'd guess), looks for an "orange" picture in the logo.bin. For whatever reason, the logo.bin that exists in the RETCA QPYS30.52-22-11-4 doesn't have it. Just a unlocked_logo, and orange_continue, orange_warning, along with yellow and reds with same.

So what I did was extract the logo.bin with the MotoLogo tool, replace the unlocked_logo.png with my image, repacked it, then opened up in hex and changed the "logo_unlocked" to "orange".

Maybe some other situation would call "yellow" or "red' but with the LineageOS & recovery I have that's what worked for me
[Moto G7 Play Themes, Apps, and Mods] pappyN4:
Here's what I ended up with. The little lock on the top left just covers the "N/A" that shows up.
[Moto G7 Play Themes, Apps, and Mods] chuy19312:
Very nice, i loved all your logos
[Samsung Galaxy Tab S4 Questions & Answers] ashraf20:
The tablet is stuck on a constant bootloop, and i'm unable to access recovery mode. I can access download mode but even after installing the OFM through Odin, it's still stuck on the bootloop.

Comes up with "custom" on the start up screen. Not sure how to fix it have been trying for a while.

Im using Odin 3.14 and used the firmware on Sammobile, but it still doesn't work.

I put in the Home_csc instead of the csc file. The csc file would come up unsuccessful on Odin.

Not sure what else I can try, any suggestions?
[Samsung Galaxy Tab S4 Questions & Answers] ElfStone:
Hey there,

Are you running official firmware?

This is a long shot, but you could try connecting it to a PC / laptop with Samsung Smartswitch installed. There is a feature in the app called Emergency Firmware Recovery (or something similar). Give it a shot.
[Samsung Galaxy Tab S4 Questions & Answers] ashraf20:
Pre sure its custom ROM, current binary comes up custom and it says custom on the strt up screen.

Also tried smartswitch but its needs an emergency recovery code which I don't have and says " the device isn't supported by initialization"
[Huawei P20 Pro Questions & Answers] ogeeeen:
Hello,

after falling on the ground, the fingerprint sensor on my Huawei P20 pro stopped working. I ordered a new sensor, replaced it, but there was no change.

The phone does not detect the new sensor at all. I also tried factory reset and wiping the cache partition but without success.

The photo shows the original sensor. The caption says: JCD 1808 FP033 (GOODIX) V 1.3

Anyone have any idea what else can I do? Thanks!
[Android Apps and Games] AlexKim3:
Welcome to the unique cosmic world of battles and duels in Space Blade: War Arena! Venture into the depths of the boundless universe, where sword fights and cosmic duels full of adrenaline-pumping action await you.

Choose your hero and arm yourself with a powerful space blade capable of cutting through star systems. Clash with other players in thrilling arenas where every encounter becomes an epic event.

Constantly improve your skills and weaponry, creating a unique combat style. Conquer challenges, defeat mighty bosses, and earn fame on the stages of Space Blade: War Arena.

Prepare for cosmic battles of unparalleled might and become a legend in this captivating arcade combat. Show what you're made of and rule the cosmic world with your own legendary battles!

Space Blade: War Arena - Apps on Google Play

**🚀 Space Blade: War Arena - Forge Your Cosmic Destiny! ⚔️✨**

play.google.com
[Touch Diamond, MDA Compact IV Themes and Apps] kiilerich:
can you help me with the tomtom software to my diamond :( and the same slide that the iphone have
[Touch Diamond, MDA Compact IV Themes and Apps] creedin:
slide 2 unlock 2

for iphone slide

http://xdaforums.com/showthread.php?t=412418
[Touch Diamond, MDA Compact IV Themes and Apps] untrueparadox:
you would have to buy the tomtom software and the maps. or you can try the bay, loads of it there, sorry cant get any closer without having to mark this as warez.
[Touch Diamond, MDA Compact IV Themes and Apps] dannyoneill:
The tomtom app is free and can be found all over the place. Before anyone says its not warez, the application is totally free. Its the maps which cost money.

Ill upload the latest official release to my rapidshare account, keep an eye on my link in my sig. This was downloaded from HTC.
[General Topics] Ced104:
I am not sure if this is the correct thread for this post. Feel free to let me know if it is the wrong one and I guide be to the appropriate thread

I am getting inconsistent results with a lib called "libusb" depending on whether I am using a Tablet or a Phone with the USB-C Port

Objective :

- I am working on a project to get a tablet to communicate with a custom usb device using libusb on Android Studio.

Problem :

- Every device used are known support "USB-OTG" and had the "developper options" enabled

- I am getting inconsistent results using libusb depending on whether I am using a tablet or a phone :

- I ran libusb_init on 2 Tablets running Android 13 and the library reported LIBUSB_ERROR_IO.

- Tablet 1 : Samsung A52s 5G , SM-A528B/DS.

- Tablet 2 : Unknown.

- I ran libusb_init on 2 Phones running Android 13 and the library reported LIBUSB_SUCCESS.

- Tablet 1 : Pixel Tablet 7.

- Tablet 2 : Galaxy Tab 8 , SM-X200.

First indication of success :

- libusb_init would generate the context and return a LIBUSB_SUCCESS status code

What I obtain :

- libusb_init does not generate the context and returns a LIBUSB_ERROR_IO status code.

- After debugging the lib , I have found that the above error code root cause is due to "Permission Access not Granted" while libusb tried to fetch the device files ( by looking at the "errno" variable ).

What I did to resolve it :

- I have rooted the Galaxy Tab 8 tablet and changed the permission of the device files along with the upstream hierarchy. The problem persists.

What I am considering doing:

- Finding the application location using termux and change its permission access.

Questions :

Am I missing a step to perform to make it work ?

Can I get an explanation as to why libusb works as expected on phones, but not on Tablet using the same process ?

Do Tablets have more security restrictions to the user than phones ?
[Redmi Note 12 4G] adrianedu:
Hi guys, I have a problem. I have a redmi note 12 4g (tapas) and I want to install a custom rom, but in no recovery works the touch, I tried ofox, twrp and pitch black and in all I have the same problem. In miui the touch works perfectly, but in the custom recovery does not. Will there be a way to fix this? Has this happened to anyone else? 🤔 I need help please
[Redmi Note 12 4G] NOSS8:
Certain version of TWRP/O.F does not work with an AOSP rom, sometimes there is a recovery included with the AOSP certainly with fewer options but functional to perform classic operations (LOS recovery, for example) or use fastboot CMD .

An example here of TWRP for AOSP in addition to the classic versions (not for your device).

twrp-3.7.0_12-v7.9_A13_FBEv2-lmi-skkk.img

Recovery for Xiaomi devices - Browse /lmi at SourceForge.net

List of relevant recovery in one place

sourceforge.net
[Redmi Note 12 4G] adrianedu:
Yes, but my problem is that I cannot use any custom recovery, I flash them via fastboot and when I enter them, the touch does not work for me and I cannot do anything. I would like to install a custom rom but I can't because of that. The only recovery that I have been able to use to have root is the one that comes with the pixel experience rom, but they told me that it is not recommended to flash roms with that recovery
[Redmi Note 12 4G] NOSS8:
On XDA I don't see any roms in the development section.

A link to the rom?

If it's to root, no need for recovery.
[Redmi Note 12 4G] adrianedu:
I want to install any custom rom, but I need the recovery and the touch does not work on any of them. There are already several custom roms available for this phone.
[Redmi Note 12 4G] NOSS8:
This is why I am asking you for links because the problem may come from the firmware on your phone.
[Redmi Note 12 4G] adrianedu:
but what link exactly do you need bro?
[Redmi Note 12 4G] NOSS8:
the link or links of the roms you want to install (if TG link contact me by PM).
[Redmi Note 12 4G] adrianedu:
ok bro, let me send you a pm
[Redmi Note 12 4G] 2faraway2:
This OFox beta works without any problem, at least to install crDroid (I didn't test it with other custom roms to be honest)
[Redmi Note 12 4G] adrianedu:
I really try that to bro, and same result :( I don't know what else I can do 😢
[Redmi Note 12 4G] Ahmad_Karimi:
The FocalTech touchscreen is only supported in the latest Miui

May be

View attachment 6007177
[Redmi Note 12 4G] adrianedu:
tomorrow im gonna try this. I hope works bro
[Redmi Note 12 4G] adrianedu:
dam bro, this really works, thank you very much!
[General Questions and Answers] Rydah:
Please direct me to a path where i can download it without the 9.5 Beta.

Thanks.

Also Can anybody tell me where the Launcher for the browser is? I Have downloaded the latest build installed on my devices memory. I need it for Throttle Launcher directing purposes. :)
[General Questions and Answers] pacixx:
i search a remote software computer too phone free and not regiester programm
[General Questions and Answers] PhoneRepairHUB:
Control the phone using pc not control pc using the phone
[Google Pixel 2 Questions & Answers] PhoneRepairHUB:
bootloader is unlocked right?
[Google Pixel 2 Questions & Answers] PhoneRepairHUB:
1. Download the required stock image from the official website

2. Unpack.

3. If you need to save data, then in the “flash-all.bat” script you need to remove the “-w” switch in the line:

fastboot -w update walleye-opd1.170816.010-factory-63083164.zip

But to avoid errors, this is not recommended 4.

Connect the phone to the PC, go to the bootloader (while holding down the power button + volume down key.)

5. Run "flash-all.bat". After launch, the process of installing the stock firmware will begin with complete clearing of all data.

6. After installing the firmware, the device will boot into the system.
[Google Pixel 2 Questions & Answers] V0latyle:
Weird.

Are you sure you're using the correct factory image? Latest one should be walleye-RP1A.201005.004.A1

For some reason it seems like it thinks /system_b was modified, is corrupt or missing.

Try fastboot erase system_b

then

fastboot -w --force --verbose image-walleye-rp1a.201005.004.a1.zip
[Google Pixel 2 Questions & Answers] Mobb_Deep73:
Yeah, I am quite sure:

❯ ls -1
walleye-rp1a.201005.004.a1
walleye-rp1a.201005.004.a1-factory-0c23f6cf.zip

My current boot-slot is a, do I still need to erease system_b? I see I didn't mentioned it but I switched it with:

fastboot --set-active=a

Also, from my last attempt:

Warning: skip copying bootloader_a image avb footer (bootloader_a partition size: 0, bootloader_a image size: 39628800).
[Google Pixel 2 Questions & Answers] Mobb_Deep73:
So I tried the following:

❯ fastboot --set-active=b
❯ fastboot reboot bootloader
❯ fastboot erase system_b
******** Did you mean to fastboot format this ext4 partition?
Erasing 'system_b' OKAY [ 0.137s]
Finished. Total time: 0.138s
❯ fastboot -w --force --verbose image-walleye-rp1a.201005.004.a1.zip
fastboot: usage: unknown command image-walleye-rp1a.201005.004.a1.zip

I think you forgot the "update" option:

❯ fastboot -w --force --verbose update image-walleye-rp1a.201005.004.a1.zip

But still, the message in the end is the same. I looks like the partition is way to small?

Warning: skip copying system_b image avb footer (system_b partition size: 2684354560, system_b image size: 140725514723744).
Sending sparse 'system_b' 1/6 (458752 KB) OKAY [ 15.575s]
Writing 'system_b' OKAY [ 0.000s]
Sending sparse 'system_b' 2/6 (458752 KB) OKAY [ 17.899s]
Writing 'system_b' OKAY [ 0.000s]
Sending sparse 'system_b' 3/6 (458752 KB) OKAY [ 18.019s]
Writing 'system_b' OKAY [ 0.000s]
Sending sparse 'system_b' 4/6 (458752 KB) OKAY [ 17.969s]
Writing 'system_b' OKAY [ 0.000s]
Sending sparse 'system_b' 5/6 (524200 KB) OKAY [ 20.189s]
Writing 'system_b' OKAY [ 0.000s]
Sending sparse 'system_b' 6/6 (133844 KB) OKAY [ 7.229s]
Writing 'system_b' OKAY [ 0.000s]
fastboot: verbose: Do flash system_a system_other.img
extracting system_other.img (311 MB) to disk... took 1.244s
archive does not contain 'system_other.sig'
Sending 'system_a' (2621440 KB) FAILED (remote: 'Uploaded data exceeds max-download-size')
fastboot: error: Command failed
[Google Pixel 2 Questions & Answers] V0latyle:
Okay, just making sure.

Shouldn't matter, you can perform an operation on any slot while on any other slot: current is default, you can use --slot=other for the inactive slot, --slot=all for both, or you can specify by name: --slot=a --slot=b

So, you don't need to change active slot

Yeah it does look like the partitions have been changed. Please do not attempt to switch slots, it may permanently brick your device: if you instruct bootloader to switch to slot B, it will attempt to load that slot on boot, and since that partition doesn't exist, the device will go into Qualcomm EDL mode from which there is currently no available recovery method.

edit: looks like you already tried this, don't do that again lol

correct

yeah it seems that LOS and other projects like that reorganize the partition layout on the device and there's no clear way to get things back to factory. This is the one thing Samsung did right - Odin could use a partition map (PIT file) to repartition the device to match original stock, but I'm not sure how to do this on Pixels

@badabing2003 any ideas?
[Google Pixel 2 Questions & Answers] V0latyle:
@Mobb_Deep73 Use the Android Flash Tool to flash the latest build, make sure in the options you check Wipe and Force flash all partitions

@badabing2003 do you know of a way to get a log of the output from the Flash Tool? this would be really useful
[Google Pixel 2 Questions & Answers] Mobb_Deep73:
Flashing from a browser, welcome to 2023... So I did it, it kinda worked with the wipe and force flash options. I could select multiple builds and selected:

6950175
aosp-master-with-phones
aosp_walleye-userdebug
Created Nov 4, 2020

I now have a new message at the bootloader screen, after the flash I got:

ERROR: BootLinux Failed : Bad Buffer Size

Then I powerd it off and booted it again an got:

ERROR: Slot Unbootable: Load Error
[Google Pixel 2 Questions & Answers] V0latyle:
Make sure you have a factory build selected. I had a similar issue when I used it to install the Android 14 beta on my Pixel 3, it wouldn't boot. Had to go back to an Android 13 developer preview or release build.
[Google Pixel 2 Questions & Answers] Mobb_Deep73:
This is quite awesome, Thank you so much! I was to quick the previous attempt and saw now that I could select another build:

RP1A.201005.004.A1 (6934943)
walleye-user (signed) 11.0.0 (Android 11) API level 30

After flashing it booted the stock Android 11 again.

So... then I enabled USB debugging again, reboot into bootloader, flashed recovery, rebooted into recovery and tried to sideload Lineage 20 again. Like the instructions.

adb sideload lineage-20.0-20230919-nightly-walleye-signed.zip

But for some reason it's stuck again on "Verifiying update package..."

After a while I hit CTRL + C and then a message on the Phone pops up "Signature verification failed, install anyway?".

This is kind of odd because I already canceled the adb sideload command, so I select "no".

After that I see:

ERROR: recovery: Failed to read 6 bytes data at offset 883742324: I/O error
ERROR: recovery: Failed to read foter Update package verification took 1117.9 s (result 1)
ERROR: recovery: Signature verification failed
ERROR: recovery: error 21
ERROR: recovery: (adb status 10)

Install completed with status 2.
Installation aborted

Then I reboot the phone and it hangs on the G booting logo. After a hard poweroff and on it's back in the bootloader with the message "ERROR: Slot Unbootable: Load Error" that I can recover from using flash.android.com...

Any thoughts?
[Google Pixel 2 Questions & Answers] badabing2003:
Yeah --force -w are the flags to force and are usually enough when flashing factory image to recreate / resize partitions to match the image.

There are also other low level option to format / create / resize partitions.

I don't use Android Flash Tool ;) so have never looked into a way to get a log output.
[Google Pixel 2 Questions & Answers] V0latyle:
Sometimes starting over from the beginning helps. Glad you were able to get it back.

Well, not quite. They fail to mention that the stock recovery will only install signed authentic Pixel OTA images. You'll have to use a custom recovery. Don't actually flash it to /boot as instructed, just live boot it: fastboot boot recovery.img This loads it into RAM and runs the kernel without actually flashing it to the device.

Yeah, because the LOS package isn't signed with the OEM key. Their instructions are misleading.

As I mentioned above, try booting a custom recovery. The LineageOS one is the boot.img here, so as I described: fastboot boot boot.img

Note: If you want to make it easier on yourself and keep your files organized, just drag and drop the image you want to perform the operation with into the command window and it will auto populate the path. Example: [icdoe]fastboot boot <drag and drop file>[/icode] becomes fastboot boot <path to image>

If you don't want to use the LineageOS recovery, try TWRP. Use in the same manner as above.

I don't have experience with the LineageOS recovery but either option should allow you to install the LineageOS zip from storage or sideload from ADB. Make sure you wipe /system and /data first.
[Google Pixel 2 Questions & Answers] V0latyle:
Ah, I thought this was just to force the update script to ignore the bootloader/baseband version requirements. Good to know.

Well, if the above is true and it's just using the same commands that we already know about, then we don't need to. Still, for the sake of knowledge, it could be useful to get some sort of log dump. I wonder if this could somehow be done through Chrome. Maybe this would help?
[Google Pixel 2 Questions & Answers] Mobb_Deep73:
When using Linux maby you can use the strace or a something similar tool to see what what is happening.
[Google Pixel 2 Questions & Answers] V0latyle:
I don't use Linux tho
[Google Pixel 2 Questions & Answers] Mobb_Deep73:
It was quite an adventure, but I managed to install LineageOS 20 with MindTheGapps...

This made me think together with the signed images part. Step 6 and 7 from booting a custom recovery using fastboot makes sense? First you flash the LineageOS recovery that can verify the image you flash from the same recovery a few steps later.

I used this in a way. The phone doesn't seem to like to get flashed / sideloaded from a computer (used a Linux and a Windows one) with adb commands. So I did:

1. Factory default the phone using flash.android.com to Android 11 (don;t forget to unheck lock bootloader)

2. Used adb to push the LineageOS rom (not the latest one, see step 11) and MindTheGaps zips to /sdcard/Download/ on the phone

3. Reboot to bootloader and used the TWRP recovery (because it is more advanced than the LineageOS one) from ram

fastboot boot twrp-3.3.0-0-walleye.img

4. Started the terminal from TWRP and copied the files to /

5. Wiped data and system

6. Installed LineageOS rom

7. Reboot to bootloader (see this part)

8. Used the TWRP recovery again from ram

fastboot boot twrp-3.3.0-0-walleye.img

9. Flashed MindTheGaps

10. Reboot and success

11. Used the builtin updater to update to a later version to check if it still boots (took very long)

12. Reboot and success
[Google Pixel 2 Questions & Answers] V0latyle:
Nice.

What version of ADB Platform Tools are you using? Some versions have been known to cause problems.
[Google Pixel 2 Questions & Answers] badabing2003:
The issue is that the client (in this case Android flash tools running on the cloud) has to output the necessary logs.

With fastboot being the client, it does, but it does not look like the cloud client is doing that.

What can be captured in Chrome (through developer calls) is the actual calls (request / response) between the cloud client and the local agent,

This is not logs per se.
[Google Pixel 2 Questions & Answers] Mobb_Deep73:
Is there a chance that it's something like an SPA and that the client is the browser?
[Google Pixel 2 Questions & Answers] Mobb_Deep73:
I really think it's the Pixel 2 that cause the troubles. Begin this month I flashed a Pixel 3a by just following the LineageOS guide. But:

❯ adb --version
Android Debug Bridge version 1.0.41
Version 34.0.4-android-tools
Installed as /usr/bin/adb
Running on Linux 6.4.12-arch1-1 (x86_64)
❯ fastboot --version
fastboot version 34.0.4-android-tools
Installed as /usr/bin/fastboot