yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] JJC1138:
Here are some instructions for installing JesusFreke's modified recovery image. You have to install the modified recovery image before you can install modified firmwares. These instructions are simpler than the existing ones because they don't require the use of adb or telnet.

Firstly, you need to already have firmware version RC29 or RC7. To check which version you have go to "Settings" and then "About phone". At the bottom you will see a "Build number" which will include "RC" and then a number. If you have RC30 or RC8 then you need to downgrade. THAT WILL WIPE ALL THE DATA/APPLICATIONS ON YOUR PHONE. Instructions for downgrading are here.

Now that you have RC29/RC7:

Download 'AndroidMod.zip' from one of the links in JesusFreke's post

Extract 'recovery_testkeys.img' from that zip and copy it to your SD card.

Download 'install.zip' which is attached to this post below.

Extract 'install' from that zip and copy it to your SD card.

Put the SD card in the phone or disconnect the phone if it is attached by USB.

Reboot the phone (switch it off and then on again).

When it has finished booting type the following at the home screen. It will start searching your contacts, but don't worry about that. Also, you won't see any visible sign that the first command worked. Just go ahead and type the second command straight afterwards:

cd sdcard<press enter>

sh install<press enter>

After a moment your phone should reboot itself. To check that the flashing worked, switch off the phone and then hold down the home key while you switch it on again. Keep the home key held down until you see the recovery screen (with the "!" triangle and the picture of the phone). Then press Alt+L on the keyboard and if you see "Using test keys" on the second line of text then the modified recovery image is installed and you can now install a modified firmware.
[G1 Android Development] philje123:
Cool! Thanks for that... much simpler... anyone else tried this yet?

I'm going to attempt all this later.

Phil
[G1 Android Development] flak0:
i just tried it and it works. confirmed.
[G1 Android Development] samysam05:
great for beginners!

Hey tried it and it works!! Now how about one on restoring data after backup.
[G1 Android Development] qtronix:
thanks for this just tryed it and worked first time.:D
[G1 Android Development] gottifour:
First off thanks for all information here. Am I correct that after I downgrade to rc29 I then follow the instructions in this thread and then I can install jf 1.3 rc30. Or do I have this all wrong?
[G1 Android Development] korndub:
you are correct. once you have the modded recovery image, you can use jfs update zips.
[G1 Android Development] gottifour:
Sweet! Thanks for the reply. I will attempt this real soon. Do you have any suggestions before I begin? After I modify the firmware I will not get ota updates anymore right? Lets say the cupcake update, or any other for that matter, does come out. I would just have to wait untill a smarter person then me converts it to a new modified image to flash to my phone? Is that right? Thanks for any help. I'm sure this is probably the worng place to ask all of these questions. d
[G1 Android Development] bhang:
in one of the zips from JF is an app that will REsign any update.zip, so when an ota comes you just have to wait for the update.zip to show up then you could REsign it with the dev keys, pretty easy, but it will probably show up pretty fast now that almost every G1 is probably running that keyset.

bhang
[G1 Android Development] gottifour:
UPDATE..

Its working now...I wasn't doing it in the telnet client. I was just typing it in randomly and it didnt work that way for some reason.

Ok. I have downgraded to rc29 and copied the two images two my sd card. but I'm not sure if I even have root. When I try to change directory it doesnt happen. I have to have root by installing the modified rc29 right? I did type telnetd at the home screen and pushed enter. nothing happened. I know I'm missing something just not sure what yet? I did install the telnet client from the market as well. I'm not understanding something it appears. Anyone? :)
[G1 Android Development] JesusFreke:
use the telnet client to telnet to localhost. *then* you will have root. (note: that's only applicable for RC29. to get root on JFv1.3, just type su in terminal emulator).

To know if you have root access, check the prompt you get. if you get #, then you have root access. if you get $, you don't have root access.
[G1 Android Development] diabolical28:
well this is a big help for many people thank you for your addition
[G1 Android Development] gottifour:
I got the # :)

Thanks so much for everything so far..This is really awesome!!
[G1 Android Development] JJC1138:
Hi there. I just wanted to clarify that if you're following the instructions I posted then you don't need telnet.

No, you don't need the modified RC29 to do this. After you type the "cd sdcard<enter>" command nothing visible should happen. It works because the bug in RC29 which we are exploiting executes everything you type on a hidden root console, so the cd command works, but it just doesn't show you anything. Then you enter the second "sh install<enter>" command and that runs a script that does all the good stuff and then reboots.
[G1 Android Development] gottifour:
Thanks for the reply and for simplifying this for everyone. I was confused at first but now I understand better. I have the modified RC30 working now with the dev boot loader as well. Oh and a new theme too. Thanks again!!!
[G1 Android Development] Koush:
Correct, this is a really good idea! Instead of typeing telnetd to start it as root, you are typing in and running the script that will root your phone-- as root! I'll update my sticky post shortly.
[G1 Android Development] l0uisz:
worked for me now do i delete the install file, DREAIMG file and Recovery test keys files or do i have to keep em?
[G1 Android Development] JJC1138:
You can delete them off your SD card after they're installed.
[OnePlus 12] vegetaleb:
Hello

What is the length of the vable included in the box?
[OnePlus 12] XDRdaniel:
1m
[OnePlus 12] vegetaleb:
Thanks

How to find a compatible 2m cable that can use full potential of the 100w?
[OnePlus 12] Edward Joseph:
For your OnePlus 12's 100W fast charging, here are 2m cable options:

Official OnePlus 100W USB-C Cable (2m): Safest bet for guaranteed compatibility and full 100W potential.

Anker PowerLine III Flow USB-C to USB-C 2m Cable or AUKEY PD Fast Charger Cable USB C to USB C 100W: Reputable brands with cables supporting 100W charging (double-check compatibility for your specific needs).

Remember, the adapter's wattage also affects charging speed.
[OnePlus 12] vegetaleb:
I visited the official OnePlus UK store, they only have the 1m cable
[OnePlus 12] zSyntex:
That's true, OnePlus actually only sell the 1m cable.

I'd suggest you to buy a extension cord, since more and more producers follow this choice.
[OnePlus 12] anatoly1983:
There is baseus and oppo supervooc 2m cables..
[OnePlus 12] Sieluck:
Are they actually passing 100W through them or just showing supervooc but charging much less than should be?

Any link please?
[General Topics] chuckm-droid:
I've been around embedded dev for a while and was looking to step into the Android custom ROMs mainly for automotive applications. I noticed there aren't many active forums specifically for AOSP. Is there little interest in the project or do I really need to dig deep and look in the corners of the internet to find a community?

Would love to hear from you all.

Thanks,

Chuck
[General Topics] hexaheximal:
Vanilla AOSP is rarely what you want nowadays, at least as an end user. AOSP itself is just the base version of Android, published openly by Google, which all Android ROMs are derived from, both stock and custom. However, stock ROMs also include, GMS (Google Mobile Services), which is the package of Google apps for stock Android. Some people have also figured out how to get GMS working on custom ROMs too, although Google doesn't officially support it at all.

If you want to learn how the Android build system works, or want to build a new device powered by Android, however, AOSP *is* what you want, at least to start with.

The official AOSP Gitiles instance is at https://android.googlesource.com and the documentation is at https://source.android.com. I will warn you though - the AOSP docs are... not very extensive...

Take a look at the Start, Download, and Build sections in the AOSP documentation, as well as https://source.android.com/docs/setup/create/avd. Assuming you have a good enough computer (and I mean a REALLY good computer), you should then be able to build your own AOSP image and run it in an AVD!
[General Topics] chuckm-droid:
Thanks Hex. I'm looking at both routes, custom and AOSP. I've found that going custom has been a non-starter with some of the older devices I have. Getting started with AOSP also has its challenges when there's no pointers to additional device-specific proprietary libraries. I shifted to possibly using a jetson nano. LineageOS has a build for it but if I want to go the AOSP route, where are the device-specific proprietary libraries. Nvidia.com nothing. android.com noting. Google search nothing. Then there's the GMS dog and pony show. Why do they make it so difficult. I'm considering other options like Automotive Grade Linux (AGL) but not giving up just yet.

Thanks again
[General Topics] hexaheximal:
That's correct. There are various proprietary blobs involved in Android devices. Normally you get them by contacting the company you got the SoC from and asking for a BSP, but for someone trying to mod an existing device, this is almost impossible to do. I personally recommend getting an Odroid board if you really want to have a proper BSP, since HardKernel (the device vendor) actually publishes the Amlogic (the SoC vendor) BSPs for their devices.

On LineageOS, the way these things work is actually quite simple - it rips the blobs from a stock ROM and puts them back into the custom ROM you build. However, you'll still need a proper LineageOS device tree for that.

If the device is fairly recent (and afaik the board you mentioned does NOT fall under this category unfortunately), you can also try building a GSI instead, so you don't need to even worry about device and vendor trees. Whether a GSI will work, let alone reliably, is a whole other problem.

In your case though, one thing is very clear: You're trying to mod (or at least considering modding) a NVIDIA board. I can see why you would want to do that, but seriously, don't even bother with those devices. NVIDIA is definitely NOT known for being easy to work with as linux hobbyists (see also: the legendary thing Linus Torvalds said about NVIDIA) and while you can probably figure it out given enough time it's generally not worth the effort.
[General Topics] chuckm-droid:
Well, a lot of what I do these days is dependent on Nvidia GPUs and Google TPUs so I can't take as far as Linus. But it gave me a chuckle. AMD + Rocm is a difficult sell at work.

I'll take a look at the odroid-n2+. Fumbling around the interwebs I found a thread for someone needing the BSP for a DragonBoard and a light went off. I have a 410c I picked up for a Coursera IoT course years ago.

I think I just took a step forward. After setting up a new Qualcomm Dev, account I just downloaded the BSP for the 410c. It's old but it's something. I'm still going to check out the odroid-n2.

Thanks for the kickstart.
[General Topics] hexaheximal:
Yeah, I think you'll enjoy the N2+. It's a rather big board, but it's by far the best Amlogic SBC that I know of, especially since HardKernel publishes the BSPs for both AOSP and Buildroot :D

> I think I just took a step forward. After setting up a new Qualcomm Dev, account I just downloaded the BSP for the 410c. It's old but it's something.

What??? How???

Normally you have to buy a EVK and sign an NDA before they'll even give you a BSP.
[General Topics] 雏镜_srcmirror:
因为AOSP界面太丑了 且几乎所有的ROM包都会内置GMS服务 GMS包含了短信 电话 日历 时钟等应用 它们比AOSP界面更美丽 更好用：）
[General Topics] hexaheximal:
[going off of what Google Translate thinks that is in English here]

Correct, *modern* vanilla AOSP feels... lifeless. The core OS is still maintained, but the apps on top of it just feel... off. It's like an abandoned city literally right next to a futuristic wonderland. It just doesn't make sense.

Google has moved so much into GMS nowadays. And the AOSP apps have fallen behind.

LineageOS, however, did a pretty good job of filling in those gaps and modernizing AOSP. If you compare the LineageOS UI to the vanilla AOSP UI, it looks so much better.
[General Questions and Answers] kss7.62:
So i'm new to all this and kinda got into it as a hobby but this is kinda a must have scenario. 3 android phones, samsung a135U1 (Ibroken screen) , samsung A03 basically brand new, and Moto G play 5g 2023, the phone that has a shattered screen is the only phone that has the proper chip set and configuration for my project. i was wondering everything works but the screen and want to test actual touch input. i was thinking about routing the screen touch input, and video output to one of the other phones screens Via USB c 2c and was hoping someone would know an app or program i could use so i dont have to build a tool specially for this. i was thinking the other samsung phone may be the best but its running 64 bit, and the other two phones are 32, also the displays are just about 1:1
[General Questions and Answers] EllieCat:
Try using AirDroid or Scrcpy.
[General Questions and Answers] kss7.62:
Thank you. ill give it a shot.. but now its phantom touching every where making it almost impossible to do anything with it.. any chance i could use a screen mapper like the one in blue stacks 5 to kill input. or the accessibility settings to the one where it kills the input for a section of screen?

its just getting there or getting adb connected again
[General Questions and Answers] EllieCat:
ADB command:

adb root
adb shell
rm -rf /dev/input/event1
[Samsung Galaxy Tab A7 Lite] Cuonglla117:
hi guys

I make this for someone who is tinkering with the Tab's bootloader.

So this is the story. I want to unlock the frp lock, i find out about a tool called MTKClient to unlock the bootloader.

The bootloader got unlocked but the dm-verity got corrupted and it got messed up.

I brick my tab 5-6 times and i just found out if you want to re-lock the tab properly and get rid of that dm-verity problem, here you are:

(MAKE SURE YOU BACKUP NVRAM OR MAKE A FULL DUMP BEFORE TINKERING WITH THE TAB)

1. Make sure the tab is unlocked

2. Read seccfg partition for backup using mtkclient

3. Erase seccfg partition (system will regenerate it later)

4. Reboot your Tab and done.
[Samsung Galaxy Tab A7 Lite] hexaheximal:
Thanks! I have known how to unlock it via mtkclient for a long time, but I didn't realize you could lock it via mtkclient as well.

I'm going to have to try this sometime. ;)
[Android Head-Units] cristalblu:
Greetings,

first of all sorry for the typing errors but I am Italian and I use a translator :LOL:

I have a PX5 Car Tablet with RK3368 processor with 4GB of RAM and 64GB of ROM, the Car Tablet works quite well but I have a problem that no one can solve......

...in the DSP app when I save an equalization with 1 preset this saving is reset after a few days, returning to the default settings.

How can I solve it?

Thank you
[Android Head-Units] cristalblu:
Up☺️
[Android Head-Units] cristalblu:
Up🥲
[Android Head-Units] cristalblu:
Android 10
[Android Head-Units] marchnz:
Here: https://xdaforums.com/search/71084170/?q=Csn2&o=relevance
[Nubia Red Magic 9 Pro] mvikrant97:
Disclaimer: Use it at your own risk.

Download Link

Password to extract file is password

FAQ:

1. Why do we need this?

Ans: This tool is much easier to operate than the Qfil tool and would result is much faster operation to readback and write partitions in EDL mode.

2. Antivirus says its a Virus or Malware.

Ans: Please disable your Microsoft Security Tool or any other Antivirus software which will show a fake alarm as this .exe is not signed.

3. What do I need to make this tool to work?

Ans: You need the device programmer or so called firehose file and the xml files.

Testimonial: I have tested this tool with MI A1 and Poco F1 and it worked with both the devices. MI A1 has emmc storage whereas Poco F1 has UFS Storage.

Qualcomm Flash Loader V2 - Developed by Iwan Zadat Imani (Iwan)​

View attachment 6095364

Features Qualcomm Flash Image Loader V2:​

9008 EDL Functions:-​

Read GPT

Erase Partition

Read Partition

Write Partition

Flash Firmware

FASTBOOT Functions:-​

[Generic] Read Info

Set Boot Slot A/B

Reboot > Normal > Bootloader > EDL1 > EDL2

Command Line

Flash Firmware

How to use it?​

Download the zip file from the below link

Extract the all files from desktop

Open the folder and run the " Qualcomm Flash Loaderv2.exe "

View attachment 6095365

Connect the device to the computer in EDL mode.

Select your device programmer and rawprogram.xml to test it.

​
[Nubia Red Magic 9 Pro] Renate:
My eyes are weak. I can't see a link.
[Nubia Red Magic 9 Pro] mvikrant97:
Eagle eye spotted. Added download link. Thank you.
[Nubia Red Magic 9 Pro] Mr nerd:
Good find dude,

Doesn't work for me but i'm sure it will be helpful to others out there!

Just freezes when i click READGPT after adding the firehose file and all XML's

Must be a driver issue on my end
[Nubia Red Magic 9 Pro] mvikrant97:
Thank you for trying it out. Have you set the memory type to UFS?
[Nubia Red Magic 9 Pro] Mr nerd:
yes sir. tried multiple times same results. it has to be something wrong with my windows or something
[Nubia Red Magic 9 Pro] mvikrant97:
Can you share the screenshot of the error message in the tool?
[Nubia Red Magic 9 Pro] Mr nerd:
no error just freezes window says not responding.

Sent from SM-F926U using ReLabs
[Nubia Red Magic 9 Pro] mvikrant97:
Have you disabled your Antivirus?
[Nubia Red Magic 9 Pro] Mr nerd:
I have not but I don't even think it's on I can,double check later. all I have is windows defender and it's probably already off

I was able to use the Linux EDL to see my partitions but it was very time specific to get the device in firehose mode. I'll try again later today and check my AV. thanks for replying.

Sent from SM-F926U using ReLabs
[Nubia Red Magic 9 Pro] Renate:
I've always maintained that the Qualcomm driver (virtual COM port driver) was a source of unreliability.

You can try my Windows EDL client (in the sig) which uses a generic WinUSB driver (see instructions).

If you want to go back to QFIL, simply reload the Qualcomm driver.
[Nubia Red Magic 9 Pro] Mr nerd:
Thank you I'll try this as well!
[Nubia Red Magic 9 Pro] Mr nerd:
Disabled Windows Defender Completely

View attachment 6095714

Same Results.

Tried your EDL program still no luck on my end I was unable to put the device in firehose mode

but its ok I can still use Linux to flash and what not. no big deal Thank you both for trying to help me really appreciate it!
[Nubia Red Magic 9 Pro] Renate:
If you can't get it into EDL mode, that's a different subject.

There are test points and "EDL cables" work on some devices.

EDL is a useful capability if you can get it working.

Just today, I found a new loader for one of my devices.

I made a full, raw backup of the device.

Now, no matter what I do to it I can restore it to functional with very little effort.
[Nubia Red Magic 9 Pro] Mr nerd:
I can get it in to EDL Mode its just not being seen by the program, its fine i have TWRP install fully Decrypted userdata partition so i have a full back up as well i just wanted to learn more is all.
[Nubia Red Magic 9 Pro] mvikrant97:
I understood it now. The program has some issues.
[Nubia Red Magic 9 Pro] Renate:
Yes, but without quoting exactly what the error message is, you're just saying, "Didn't work".

If you were running my program and it said, "Could not open device" that was because you still have the Qualcomm driver installed.
[Nubia Red Magic 9 Pro] Mr nerd:
It does see the device, it just cant put it in to firehose mode.
[Nubia Red Magic 9 Pro] alejandroprz95:
You can make a backup with this tool?

If you can give a brief explanation
[Nubia Red Magic 9 Pro] Renate:
@Mr nerd You're not being very helpful.

If there is a problem with either the software concerned in this thread or my EDL client, progress can only be made with verbatim, quoted error messages.

That means, your paraphrasing of testing outcomes is less than helpful.

@alejandroprz95 I'm not sure about this particular software.

If you have an unrestricted Firehose loader for your device you can use any EDL client to read and write the entire storage.

For eMMC, that would be a single 32 (or 64 or 128) GB file.

For UFS, that would probably be six files that add up to that total size.
[Nubia Red Magic 9 Pro] Mr nerd:
I'm not trying to troubleshoot anything I'm just telling you what my results were. That, was, the error message "Can not put device in Firehose Mode. " so no need to stress over my issue. I appreciate your concern though. If you want we can troubleshoot it more I'm all, for it. Send me a DM when you're free this, weekend.
[Nubia Red Magic 9 Pro] DarkestSpawn:
What Renate is directing at is debugging is a two way street. Helpful to the community and the Dev. There are other community members that might have the same issue and not say anything, or there could be a bug with the script/program/app that is being used and the Dev wants to figure out if its Operator error or coding error to submit a issue/fix.

Saying "It does see the device, it just cant put it in to firehose mode" is way too generic. Does that mean Device Manager sees it as ADB or Fastboot mode, or is it being recognized by USB Descriptor but no driver has been assigned yet, or it is setup correctly but fails to reboot to EDL, or the program is failing to send firehose communication, or even it sent the firehose but EDL never had a successful handshake between each other.
[Nubia Red Magic 9 Pro] Mr nerd:
I understand that but as I keep stating there is no error other than that. Because it's freezing. I'm assuming it's a driver issue or it's possible it could be my very own windows installation . Because I am not trying to troubleshoot it because it's working on Linux for me but I'm more than happy to if someone wants me to. I also think it could be a firehose file issue for me as well because it's the same error or issue for any program I use it will not pull the partitions for me that's the only thing not working for me on windows. And like I told them before if someone wants to troubleshoot with me I'm more than happy to do it, but I figured it out on Linux so I do not need to troubleshoot on windows nor was I trying to. I followed the instructions and gave results unless there's some king of logs it's not generating or I'm seeing I did not get any errors other than the one I mentioned.

Thanks again for everything.
[Nubia Red Magic 9 Pro] _BLADR_:
Hello, I seem to encounter a problem a t reading the device map.... Does somebody know why this might happen?

Searching for HS-USB QDLoader 9008... OK

COM : COM3

Service : qcusbser

Manufacturer : Qualcomm Incorporated

Handshaking... OK

Reading bootloader info... OK

Serial : XXXXXXXXX

SoC : [ xxxxxxxxxx ]

PK_HASH[0] : DFF7DDA29C8C49B12xxxxxxxxA482825E

PK_HASH[1] : 42E572Bxxxxxxxx3FEA83C101EB7F917

Writing to flash programmer... OK

Connecting to flash programmer... OK

Configuring device...

Reading partition Map... Fail

Nubia Red Magic 5g - Snapdragon 865 5G running official lineageos

Any help would be great!
[Nubia Red Magic 9 Pro] Renate:
This is addressed to everybody.

Don't freaking lie or obfuscate the SoC or hash.

You're just wasting everybody's time and being a pest.

I don't want your stupid serial number. (Which is only the serial number of the processor chip and has no connection to anything.)

And maybe even state the make and model of the device, hmmm?