yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy A52s 5G] Plexus999:
View attachment 6078697

Run chmod a+x script2.sh

14open: ../r.img failed with 2: No such file or directory

15open: system/bin/recovery failed with 2: No such file or directory

16open: system/bin/recovery failed with 2: No such file or directory

17open: system/bin/recovery failed with 2: No such file or directory

18open: system/bin/recovery failed with 2: No such file or directory

19open: system/bin/recovery failed with 2: No such file or directory

20open: system/bin/recovery failed with 2: No such file or directory

21open: system/bin/recovery failed with 2: No such file or directory

22open: system/bin/recovery failed with 2: No such file or directory

23open: system/bin/recovery failed with 2: No such file or directory

24open: system/bin/recovery failed with 2: No such file or directory

25open: system/bin/recovery failed with 2: No such file or directory

26open: system/bin/recovery failed with 2: No such file or directory

27open: system/bin/recovery failed with 2: No such file or directory

28open: system/bin/recovery failed with 2: No such file or directory

29open: ../r.img failed with 2: No such file or directory

30cp: cannot stat 'new-boot.img': No such file or directory

31wc: recovery.img: No such file or directory

32usage: avbtool add_hash_footer [-h] [--image IMAGE]

33 [--partition_size PARTITION_SIZE]

34 [--dynamic_partition_size]

35 [--partition_name PARTITION_NAME]

36 [--hash_algorithm HASH_ALGORITHM] [--salt SALT]

37 [--calc_max_image_size]

38 [--output_vbmeta_image OUTPUT_VBMETA_IMAGE]

39 [--do_not_append_vbmeta_image]

40 [--algorithm ALGORITHM] [--key KEY]

41 [--signing_helper APP]

42 [--signing_helper_with_files APP]

43 [--public_key_metadata KEY_METADATA]

44 [--rollback_index ROLLBACK_INDEX]

45 [--rollback_index_location ROLLBACK_INDEX_LOCATION]

46 [--append_to_release_string STR]

47 [--prop KEY:VALUE] [--prop_from_file KEY:PATH]

48 [--kernel_cmdline CMDLINE]

49 [--setup_rootfs_from_kernel IMAGE]

50 [--include_descriptors_from_image IMAGE]

51 [--print_required_libavb_version]

52 [--chain_partition PART_NAME:ROLLBACK_SLOT:KEY_PATH]

53 [--flags FLAGS] [--set_hashtree_disabled_flag]

54 [--use_persistent_digest] [--do_not_use_ab]

55avbtool add_hash_footer: error: argument --partition_size: expected one argument

56Error: Process completed with exit code 2.
[Google Pixel 7 Pro] UltimateGamer83:
The only successful flashes I've been able to get lately are Graphene OS and Calyx and those are official. I haven't seen any other official builds lately.
[Google Pixel 7 Pro] JohnTheFarm3r:
You do realize official doesn't guarantee "long support", nor does g

uarantee a better end-user experience compared to a non-official ROM?
[Google Pixel 7 Pro] 96carboard:
Think QUALITY over QUANTITY. Everybody and his brother can whip up a custom build, but 99.999% of them are pointless trash. You've got factory for blingy spyware, GrapheneOS for security, and calyx for somewhere in between.
[Touch HD General] janne303:
Hello all!

I wonder if its possible to have an alarm on the phone when turned of. Ive searched everywhere for some answers.

I want to shut down the phone at nights and I want the phone to start up and wake me up hehe
[Touch HD General] Mike fait nimps:
I just tried it 2 times , and it doesn't seem to work with klaxon.:(

Sorry mate i think you should keep it on if you don't want to be late tomorow:D
[Touch HD General] janne303:
Its hilarious that a phone this new doesnt support that kind of alarm. All of my other phones works that way....
[Touch HD General] sebbes:
It's not a phone, it's a smartphone, pretty much a small PC...

So if you poweroff your desktop, usually not much it can do :D

That's the same, workaround is to use PlaneMode (along WirelessTime freeware in example)

This way, it wont be off at all..
[Touch HD General] Coude:
Like for PDA, you usually never power off this kind of system. You put it in standby mode instead (either automatically or manually)

And the alarm works well with the HD is in stanby mode. It will wake up and ring.

Note that the usual phone are in some kind of standby mode, not fully powered off otherwise the alarm wouldn't work either !
[Touch HD General] Surfer_D:
you can switch off the phone part in standby mode and it will give you busy signal though reminders and alarms will work.
[Android Head-Units] MikeA3:
I just put this head unit in but not sure how to wire it up correctly? Is there something I can splice the brake cable onto to make it think it's always on?
[Android Head-Units] TorstenH:
You could spice the ACC cable and connect it with the break input of the head unit.

As soon as ignition is on the head unit will get the signal that hand break is active.
[Android Head-Units] MikeA3:
Thank you, so I can just attach it to 12v line and it should trick it?

I can sort of get around it with split screen on the left I can double tap the open apps button and it shows like this until I touch it

View attachment 5812387
[Android Head-Units] TorstenH:
BREAK is an input and you can connect 12V+ to it without risk.
[Google Pixel 7 Pro] Albi Lukaj:
hi, anyone has some kind of advice to flash old firmware as the newest have a lot of problems in terms of camera quality ? i don't have rooted my pixel 7 pro ...
[Google Pixel 7 Pro] Misterxtc:
You can install the OTA update from here. Just follow the instructions Google provided at the top of the page and you should be all updated. It's only the full images that require the bootloader to be unlocked.
[Google Pixel 7 Pro] UltimateGamer83:
Just go look up factory images for Pixel phones. You can install firmware right from the web browser. You don't need to have root. Root is optional.
[Google Pixel 7 Pro] V0latyle:
Do you mean without an unlocked bootloader? Root is not the same thing and does not determine how you can flash firmware.

If your bootloader is unlocked, you can use the Android Flash Tool. If your bootloader is not unlocked, downgrading is impossible.

This only works if OEM Unlocking is enabled in Developer Options.
[Google Pixel 7 Pro] Albi Lukaj:
so i just need to unlock the bootloader and then i can install old firmware following the procedure ?
[Google Pixel 7 Pro] V0latyle:
Yes
[Google Pixel 7 Pro] simplepinoi177:
@Albi Lukaj, Please be aware that unlocking your bootloader

WILL WIPE YOUR DEVICE AND RETURN IT TO STOCK

!!!

If that is not preferable, you might try applying the OTA like stated in Post #2, but I am not sure if it works downgrading a version (it probably doesn't)...
[Motorola Edge 30 Ultra / Motorola Moto X30 Pro] Last1left_91:
First of all, I will say that Google is the most arrogant/ignorant company that I've ever heard of. There are milions of complaints regarding the "NavBar stupid/sht pill"/StatusBar. Why, the hell would I invest in a phone with good screen to body ratio and dpi, if I cant take full advantage of it. Before Android 12/13, you could easily remove statusbar/navbar(pill) the way you wanted. But, Google decided they are the boss and removed all those possibilities to remove those via adb. Another thing, if I try to use a custom gesture app, I can only use the diagonal gestures because the normal ones(left,right) cannot be overriden because Google never allowed that. How shty can a company be to not even care of their users and even do everything against them, really!!

Another thing, is that I still dont have Android 13 on my Moto Edge 30 Ultra while I got bored of it when having S20 Ultra! And another thing is that touching the screen doesnt always wakes it up. Maybe is some sort of measure from Motorola to conserve battery because I dont find them capable of doing something good as Samsung did. Is anyone else experiencing/experienced this?

As I said, on my S20 Ultra I could do all the things, apps like System UI Tuner, cmd commands and gesture, everything worked flawlessly such that I always had a FULL immersive experience. After I changed the company, everything is havoc! Google, shame on you!

If you guys emphatize with how I feel, please thumbs up! Take care!

Look how ugly it looks like. 3 years later and will be in the same situation if we rely on these thieves!!
[Motorola Edge 30 Ultra / Motorola Moto X30 Pro] ijuanp03:
1. I can hide my navigation bar via Settings

View attachment 5820021

2. No issue with tapping the display to wake up screen. Btw, it's not double tap but single tap.

View attachment 5820035

3. I LOVE the new Motorola homescreen especially the new Motorola widget. Everything is there - the battery widget, alarm widget, weather and clock in one. Very consistent, minimal and uncluttered. Good job, Moto!

View attachment 5820029
[Android Head-Units] dreed75:
Hey everyone. I had a hard time finding out info for my unit so I am posting a thread to help others find this. Thanks to sins07 for getting me started. If anyone has additional information or this information looks incorrect, please let me know.

Amazon link: https://a.co/d/fiiyYcu

Model: D02022HA16

Android: D02022HA16_AHD_00012_V009_HIFI

Android os : 11.0 CAR AUDIO: B7.3.7

CAN PRO : 9.0.6 (disConnected): No Protocol

ddr: 2G Flash: 32G

cpu: A7 1.3GHz x 4

display: 1024*600

mcu: 4.4 (X2)

audio decoder: ST/TDA7729

Anyway, anyone have any luck loading a different ROM on here? I am thinking about doing it and will post here with my results.
[Android Head-Units] thorracing1:
Let me know you're findings I just installed same head unit and I'd like to flash different rom
[Android Head-Units] dreed75:
Haha, ok, I'll be the guinea pig. I just got the male to male usb cable so I think I'll try this weekend.
[Android Head-Units] thorracing1:
I just got mine today maybe I'll mess with it tonight
[Android Head-Units] dreed75:
I plan on using this tutorial when I do it: https://xdaforums.com/t/guide-andro...rp-custom-ui-brick-recovery-and-more.4318121/
[Android Head-Units] thorracing1:
im going to give it a try now see what happens lol
[Android Head-Units] Rdartua777:
Hey Guys - Have the same Unit - Looks like e9250 - XY Auto - Were you successfull?

Thanks,

Yury.
[Android Head-Units] thorracing1:
I just finished backing mine up and reflashing it now im installing the firmware and root stuff
[Android Head-Units] thorracing1:
Got mine finished seems way better im happy with it
[Android Head-Units] Rdartua777:
Android auto works? And Carplay?
[Android Head-Units] dreed75:
Nice! Doing mine today. Does Android Auto work? Any things to watch out for that differ from the tutorial?
[Android Head-Units] thorracing1:
im going to test android auto right now

update plugged my phone in no android auto might have to install an app to get it to work going to work on that
[Android Head-Units] dreed75:
Did you do Android 6 or 8? I tried 8 and it seems stuck on the first power on. I know it says to wait but it just had the "Car Audio" splash screen which slowly faded away and then it is just white and I'm waiting lol. I thought it would be wiped but maybe not quite.
[Android Head-Units] thorracing1:
8 and mine did that too i shut it down and reflashed the firmware and it booted fine
[Android Head-Units] dreed75:
Ok, I've reflashed 3 times and same thing. Did you only select the bootimg, vendor, and Android files? It seems odd that we don't also check preloader. Also, for the scatter file did you put 0xC0000000 for partition size for userdata? He says to but he's also using the 1G version so I didn't know if ours was supposed to be different.
[Android Head-Units] thorracing1:
yes i did to scatter file and yea i only seleced the 3 he said
[Android Head-Units] thorracing1:
did you figure it out?
[Android Head-Units] dreed75:
I tried the 1GB files and it booted up so at least it isn't bricked. I am doing a factory reset, redownloading the 2GB files and then I'll try again.
[Android Head-Units] thorracing1:
nice let me know once you get it working if you can figure out android auto
[Android Head-Units] dreed75:
After the factory reset, the 1GB version was working. I went ahead and tried redownloading the 2GB and flashing but I got the same problem. I am going to press on with the 1GB image and see if I can make it through the rest of the install. I'll try to get AA to work as well. Did you download the Z-Link app like the original ROM used?
[Android Head-Units] dreed75:
The viper driver isn't installing correctly for me. The guide says it should say "Processing yes" but it says no for me. I went back and installed root again and got the same problem. Root is still installed because apps will request superuser access. I haven't hooked it up to speakers yet but I assume I won't get anything out of them. I'll probably try tomorrow night or next.
[Android Head-Units] thorracing1:
yea i tried it gave me a channel error fault
[Android Head-Units] thorracing1:
thats weird mine worked as should first try
[Android Head-Units] thorracing1:
did you ever get carplay working?
[Android Head-Units] GameChanger:
Thank you for posting this thread. I bought this head unit about a month and a 1/2 ago. I've been looking everywhere to try and root this thing. I will be trying what was posted and let you all how it goes. Anything in particular I should be looking out for or have at it?
[Android Head-Units] GameChanger:
I have the same HU specs as yours. I tried flashing both 1 and 2gb versions with no success. I get the same white screen.

I was talking with Moderator in that thread and is telling me that firmware is not compatible with mine. It needs to be XY. Thorracing1 unit is XY so that is probably why he had no issues flashing. Ours on the other hand is different so how did you get the 1gb to work?

For 1gb option I dropped my scatter file into 1 firmware folder like instructions said and start to flash. It won't take and get an error message. The 2gb version flashes complete but get white screen after boot. I am stuck here. All I want is root so any help is appreciated.
[Android Head-Units] temaccount1312:
Will this work on the following?

https://www.amazon.com/Hikity-Bluetooth-Receiver-Navigation-Camera【2G/dp/B0B1LM81NH/

Model: D02022HA16

Android Version: 11.0

Kernel Version: 4.14.116 (gcc version 6.3.1.20170404 (Linaro GCC 6.3-2017.05))

Build Number: android-trunk-p0

Custom build version: android-trunk-p0

Android: D02022HA16_AHD_00012_V009_HIFI

Android OS: Android 11.0

CAR AUDIO: B7.3.7 (X2)

CAN Pro: 9.0.6

DDR: 2G

FLASH: 32G

cpu: A7 1.3GHz x 4

display: 1024*600

MCU: 4.4 (X2)

Audio Decoder: ST/TDA7729

Please let me know if you manage to flash any firmware successfully.
[Android Head-Units] tonysloth:
Do any of you know the factory password on the original software it came with? Or where I could find it?
[Android Head-Units] temaccount1312:
Try 8888
[Android Head-Units] tonysloth:
That worked
[Android Head-Units] Jaser9911:
hello team,

does any one know where Can i find the MCU update file for this multimedia interface unit.

or if i can get the Factory reset password for advanced setting password for this unit. it will be grateful.
[Android Head-Units] temaccount1312:
Followed steps in https://xdaforums.com/t/guide-andro...rp-custom-ui-brick-recovery-and-more.4318121/

Replaced Step 1 firmware with https://4pda.to/forum/index.php?sho...&_x_tr_hl=en-US&_x_tr_pto=wapp#entry115168364

Step 2 TWRP was 1GB version.

Radio Patch was not needed.

Works perfectly!
[Android Head-Units] anotherandrew:
I must be blind... I don't see a firmware link on that post? I mean there's a lot of links to other parts of the discussion but where is the firmware? It's also a very old discussion, my radio is on Android 12, is the intention to roll back to earlier Android to gain access to more features?

What is even stranger is that my versions look very similar but the unit is very different. Same model but different CPU. I'm not sure how to locate firmware for this unit, or if the firmware you found is compatible.
[Android Head-Units] ytremors:
How did it go?
[Android Head-Units] anotherandrew:
I returned the unit. Too many UX glitches lag.

You know it's pretty bad when you actually prefer the stock RNS510 to the aftermarket radio. :-)
[Android Head-Units] Dan0mite:
Did you manage to get this all working? I have the same unit and am getting the white screen. Going to try the 1gb version now
[Android Head-Units] dreed75:
No, I need to restore it to original but haven't gotten around to it yet.
[Samsung Galaxy Tab S8] awns1:
Hey, I haven't rooted anything since 2014, so consider me a newbie,

Is there a way to get only part of the root functionalities, in order to move Cerberus to the system's partition? I think it should only be a matter of privileges. That is the only functionality that I need, I don't want other root features, nor having Knox be affected.

Thanks in advance
[Samsung Galaxy Tab S8] Jake.S:
Keep in mind rooting would void your warranty. Since it requires unlocking bootloader.
[Samsung Galaxy Tab S8] JohnTheFarm3r:
Not if you're living in the EU. EU has strict regulations about consumer protection when it comes to unlocking bootloader or tripping KNOX in Samsung devices.
[Google Pixel 7] Djekill83:
Bonjour à tous,

depuis la dernière mise à jour de janvier du pixel 7, je n'arrive plus à me connecter en bluetooth à ma voiture Nissan Juke. Erreur de connexion, j'ai tout essayé et rien ne fonctionne.

avez vous une solution autre que d'espérer que la prochaine mise a jour règle le problème.

Mod translation:

Hello everyone,

since the last january update of the pixel 7, i can no longer connect in bluetooth to my car nissan juke. Connection error, I tried everything and nothing works.

Do you have a solution other than to hope that the next update solves the problem.
[Google Pixel 7] bobbyphoenix:
It's a known issue. Google pulled the update once people started complaining. A fix will be coming soon. Thankfully I didn't get the update because there is also an issue with T-Mobile service users. I'm still on Dec's update. We just have to wait for a fix.
[Google Pixel 7] Djekill83:
Ok merci, donc plus qu'à attendre vers le 5 février pour cette mise a jour.

Mod translation: Ok thank you, so more than waiting around February 5 for this update.
[Google Pixel 7] Badger50:
@Djekill83

Greetings, and welcome to XDA. As a "last time" courtesy, I have translated your first two posts. Please post in English as stipulated by XDA Rule #4:

Spoiler content hidden.

Thank you for your cooperation, and enjoy your stay on XDA.

-Regards: Badger50
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] ILikeOldStuff:
I am contemplating purchase of one of these phones, and tried entering some of their IMEI numbers in the imei checker at https://www.t-mobile.com/resources/bring-your-own-phone , and was shocked to find they are ALL described as "Incompatible".

This is a bit confusing after the articles saying the AT&T and Verizon versions would not work after Jan 2021 but that the T-Mobile version would continue working. I tried looking for a later article saying that support for the T-Mobile version this model was being cancelled but could not find any such announcement.

Is that IMEI checker correct? Or is it because the samples I checked may not have gotten the last modem update installed from T-Mobile?

Is anyone still using this phone (specifically the T variant) on T-Mobile in USA? I'm assuming that last update will be important, but does this still work once it is installed?

If yes to the above, do phone calls work as VoLTE, or is it doing the fallback to 2G?

I've also seen threads about enabling more LTE bands, has anyone done that on this phone? In particular is it possible to add support for B71 (600MHz), or is this radio hardware just too old to allow that?

Thanks much, I would really like to know whether I can use this phone or if I would need to find a different model.
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] dave678:
https://swappa.com/blog/3g-network-shutdown/ Your phone is fine.
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] ForestCat:
SM-N910T with 2ETI1 OTA modem update works fine. 4g/LTE Data, WiFi Calling works. Does not drop out of 4G/LTE for voice. SM-N910V w/ MODestROM v11 (6.01 TW-based N910VVRU2CQI2 ) w/ a vzw 2CTI baseband update, has working 4gLTE data, but no WiFi Calling, or VoLTE (falls back to 2g, but I still have 2g coverage here, so it's usable, if not optimum. Here's the thing: on the VZW phone, if I set the the salescode to TMB, suddenly VoLTE works, but the Setup pages/menus/statusbar are screwed up, so it's not really useable. Here's where it gets REAL interesteing. On a VZW phone w/ VZW 2CTI1 baseband, & VZW BL, flashed with a custom TMB ROM (trltetmo_N910TUVU2EQI2_Stock_Deodexed, debloated, but still TW), EVERYTHING works. But it's not stable, it periodically loses 4g/lte. What it tells me is that the VZW h/w is NOT THE PROBLEM. I've been at this all day, everyday since VZW turned off CDMA on 01/01/23 and killed my service here. Be warned: If you go down this path, you're gonna be mostly on your own. A LOT of dead links, 'retired' devs, etc. Everyone except you, me, and three other people here have long since moved on from this awesome phone. I'll help you if I can. I bought an SM-N910T , but the damn usb port is dead. Already changed the charging board, not the problem. It's the mobo. If I could identify the usb chip (if it's not the 805 itself, I'd change it. So I have a phone with no adb that I can't unlock/root. I'd much rather get my VZW phone fully working on TMB, since I'm heavily invested in the MODestROM. Haven't given up yet. But search my posts, you'll hear the deafening silence, lol.