yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] king of the lone woods:
Idk about keys are such,

I just feel it in the way Google by anyway doesn't help nor gave to user's user-friendly (adb don't work)

But we here use QFIL,the low level chip (than beyomd layer of creamy android controlled by google)

Kinda i feels like how we handle the "storage" HDD/SSD in computers that are not simply manipulated by "OS" of a monopoly

I am just thinking like that.. maybe you could see this way (since chip is just,data backup via qfil is in "Qualcomm"s format .. and not Google's control)

Could you please see this way & Eureka me some 😄

(I am really appreciating the time,effort,mind you put to share time for me) i am glad to have such

Just about internet bestowed us to communicate,discuss than what "they control" 😅

Wish all be well 😃🌟✨🙌

22.12.2023 05:23/4 am ist

Rf yda4:57p
[Android Q&A, Help & Troubleshooting] king of the lone woods:
Hello,i hope you had a great holidays 😇

Could you please take some time to see these again & tell me,shall i proceed with "getting my phone to customer service,to flash rom freely" and then i take it back to home,

Use qfil to restore my data (which is in Qualcomm's format,means not controlled by Google's layer of android 😅)

Hope you do well 😃🌟✨🙌

03.01.2024 03:56 pm ist
[Android Q&A, Help & Troubleshooting] king of the lone woods:
Hello 😇

Good today to you,

Please consider here if you find time,mind

Thank you

All be well 😃🌟✨🙌

06.01.2024 03:03/4 pm ist
[Android Q&A, Help & Troubleshooting] Renate:
You said that you had EDL working?

Can you read the "misc" partition?

Post a copy or just dump the first 64 bytes or so.
[Android Q&A, Help & Troubleshooting] king of the lone woods:
Now i seen your reply,

Pardon me,into some work,would reply in some time 😇

06.01.2024 06:16 pm ist

Rf tda3:57p
[Android Q&A, Help & Troubleshooting] king of the lone woods:
thank you for waiting,

I didn't even know misc exists (though i remember seen it past,but cant see until i backup everything + rename them for better handling again)

here you go 😇

Let me be the chaos defeater of another unheard story of some big corp dominate world 😅

*2 Take care be well *

07.01.2024 05:48/9 am ist

Edit(Yep,i still need to sleep with my time zone 😄) 05:50am
[Android Q&A, Help & Troubleshooting] Renate:
Thanks. It's all zeores. I was just trying to find out if there was some strange command in it.

So, just to recap: You've got EDL, fastboot and recovery?

Could you read the recovery partition and post it?
[Android Q&A, Help & Troubleshooting] king of the lone woods:
Well,I read all of partitions it showed,here it is

Since they are in "Qualcomm"s format,we may need a opensource project i hear somewhere to read it,else,its on the phone (Bluetooth transferring & uploads take time 😅)

07.01.2024 06:19/21 pm ist

Ed: 14-40ma

Sorry,

I may have to attach the file laptop (android phone sucks at it)

Some time later,after i finish my first meal of the day 😇

07.01.2024 07:02 pm ist (all ed)

here we go (using laptop now)

its just 64mb now,website cant upload

07.01.2024 11:17pm ist
[Android Q&A, Help & Troubleshooting] Renate:
It's noon here and I've had four meals already.

(Ok, they were very small.)
[Android Q&A, Help & Troubleshooting] king of the lone woods:
finally:

recovery ReadData_emmc_Lun0_0x98000_Len131072_DT_07_01_2024_05_22_29.bin

drive.google.com

see ya

08.01.2024 12:50 am ist

4 meals within noon,hmm

a diet right :)

btw take care of healthy diet,let the digestive system rest at times (leads to overall physical,mental health) which i miss too

take care :)

08.01.2024 12:52 am ist

17+ma
[Android Q&A, Help & Troubleshooting] Renate:
Huh? Why does it want me to sign in?

Well, between noon and 3 AM I might eat an apple.
[Android Q&A, Help & Troubleshooting] king of the lone woods:
just checked & changed its permissions

btw,3 am is good for well sleep (its 1:44 am here & i am yet to eat dinner)

thing is,people with high brain frequency cant sleep at nights..

we have to train such bran to be wake up,sleep,full focus as we want (imagine,like controlling one's mighty power)

go back at your past self,collect good memories,habits,things make you hopeful,make you kaugh,fulfill,bring it now to present

a focused mind is powerful than non controlled power entity :)

good night take care,

wish all be well :)

08.01.2024 01:47 am IST

42+ma ed 43ma,01:48 am
[Android Q&A, Help & Troubleshooting] Renate:
Was that just using fastboot boot recovery.img or did you try fastboot flash recovery recovery.img

Oh, I think that you have stupid signing on recovery. :(
[Android Q&A, Help & Troubleshooting] king of the lone woods:
I didn't tried with it yet(recovery image),

But i tried "adb fastboot recovery" somealike commands in the past & adb/phone didn't cooperate at all(heard that Google controls what one user can do with android,adb these times & as more like apple)

Would reply you with answer (gotta take a meal 😅)

Hope you do well too 😃✌

08.01.2024 03:50/1 pm ist

Rf tda 5:24a
[Android Q&A, Help & Troubleshooting] Renate:
But you don't have any ADB. This was supposed to be done with buttons to take you to fastboot.
[Android Q&A, Help & Troubleshooting] king of the lone woods:
Well,adb didn't work at all (just tried now,thought about you care to tell)

Its just adb needs "usb/adb authorized" by tapping "yes" when we connect it to phone,while its in good condition (android 😫)

I think,the only way left to try is still,that idea i said earlier.. flash it & restore it with qfil (or to find a tool to decrypt qualcomm's format)

Just saying

Have a good night 😃✌ (me too 😅 yet to sleep + some work in morning)

09.01.2024 05:47 am ist

Rf yda 5:24am (ed rf yda 4:06pm) above was previous reply 05:48+

I tried with combo,then we need adb to command it right?

Yep,adb stuck with authorization (i think there's no *internal* storage left too - a problem,since i can't sideload rom via sd card too) lack of storage left is one reason of bootloop i have,other than bad phone fill itself

09.01.2024 05:50/1 am ist

Yes,i tried both commands (i reply now in another phone)

Adb commands doesn't work at all in fastboot,

Only command it works when fastboot->recovery->sideload (key combos),

Thing is,there's no phone storage left for "sideload" to work

Maybe you like to see screenshot of it?

Maybe i should start a new thread or talk in qfil thread i created to continue (and forgot this whole "adb" thing,since its useless without usb/adb authorized beforehand)

09.01.2024 04:01/2 pm ist

R vi msg 6:09a
[Android Q&A, Help & Troubleshooting] Renate:
Are you saying that the phone we're talking about boots and you've been posting on that?

Yes, but you didn't say if it booted to recovery when you did that.

Well, they wouldn't would they? Because fastboot is not ADB.

No, you've started enough threads on one issue.

If anyone wants to jump in here, they can.

You can change the thread title if you like.

If you have stock software for this, just say clearly what you've got.
[Android Q&A, Help & Troubleshooting] king of the lone woods:
Huh,me too tired,i can understand that you have to come again,read all this to think(cause you are helping other threads too),while i have narrow idea about it

1.i reply in my brother's phone (bootloop/my phone is still same condition)

2.maybe,i missed the style to convey but replied like "i can get into recovery via key combos"

3.yes,fastboot is not adb.. but i don't know how to push a .img while the phone has no storage left (cause of bootloop)

4.yep,could be solved,if i had just one brave move than wait for weeks to try

5.i don't have stock rom.. but i can get the phone to local "official" service center..

They would flash it (wipe data)

# thing i ask you is,shall i move on with step 5,in hope,so i can restore "data" i previously extracted via QFIL (since its in qualcomm format,unhindered by android)

I hope you can understand now 😇

Wish you well 😃🌟✨🙌

Rf yda5:35 pm ist

10.01.2024 06:58 am ist

I thought about closing this thread,with follow up to qfil post i made,but postponed until fix .. maybe,

At times,gotta make a fine guidance at end is best for all efforts right 😃

10.01.2024 07:02 am ist
[Android Q&A, Help & Troubleshooting] Renate:
Why do you speak of QFIL as if it's a magic wand when you don't have the stock software to write?

I've said it before, if you wipe your device and then restore userdata from your backup there is no guarantee that you will be able to access it.

No, I'm not an expert on the whole encryption bit, but it seems that the NVRAM may get reinitialized and your decryption keys will get lost.

In which case your data is gone, gone, gone.

Yes, but you STILL have not clearly said what happened when you tried the last two things I asked you.
[Android Q&A, Help & Troubleshooting] king of the lone woods:
I still have everything backed up via qfil,including keys too(!)

So,if i had keys,maybe i could just swap after fladhed it,so,we can put the partitions we need to get userdata partition working in

Just thought..

Give me sometime,i will post the "whole" retrived partitions list,so you can go through once (giving clearity to one helps is good than single pitches)

All be well 😃🌟✨🙌

10.01.2024 05:08 pm ist

55+ma (ed to 58ma)
[Android Q&A, Help & Troubleshooting] Renate:
Whatever keys you have are further encrypted in TEE.

AFAIK, the entire eMMC is not enough for you to recover your data.

And do you read this stuff? You still have not responded to my question but only offer things that I did not ask for.
[Android Q&A, Help & Troubleshooting] king of the lone woods:
Which question you want to be answered (pardon my talking style,non native english),i thought i replied each with numbers 😳

10.01.2024 05:31 pm ist

16+ma(ed: 15-17ma)
[Android Q&A, Help & Troubleshooting] Renate:
I gave you a recovery image and two ways to run it. What specifically happened each time?
[Android Q&A, Help & Troubleshooting] king of the lone woods:
pardon me,i am bad at this (using windows btw)

yep,i realized adb/google wont help such & passed to qfil..

its just,i drag into here,that makes the mess i think,sorry

(reply via laptop) while my phone is still idle

11.01.2024 05:04/6 am ist
[Android Q&A, Help & Troubleshooting] king of the lone woods:
even sideload

11.01.2024 05:11 am ist
[Android Q&A, Help & Troubleshooting] king of the lone woods:
A model meant to fail,even by reviews (i didn't have a job due to covid,my old phone was repair then,so i choosed my mom's old phone,this,ever since,its just chaos)

Edit:when connected to laptop,it automatically goes there,

Which got fixed after sideload->update fail->power down*

Once fixed it,gotta be away of it soon for good sake,by god 🙇

11.01.2024 05:15/16 am ist

Rf tda 01:35am
[Android Q&A, Help & Troubleshooting] Renate:
First

When a command prints out lots of help information it means that the command that you typed is nonsense.

Since I didn't give you nonsense commands, you should have checked what you typed and told me that the command was not accepted.

Second

adb is one thing and fastboot is another thing.

Although they are both Android utilities they never appear in the same command line.

When I say a fastboot don't you say adb fastboot.

We're 50 posts along here and not making any progress.
[Samsung Galaxy S23 Ultra] Filenest:
Tried multiple times without luck.

S23Ultra connected to PC.

Button set to wake Bixby.

Registar (Goodlock) disabled.

Turn off the phone from dropdown.

Wait for confirmation phone is off (vibrates)

Hold power+volume up til the logo appears

let go of the volume up but still hold the power button

The phone just boots in normal mode, not recovery

Please help me find out what I am obviously missing here.
[Samsung Galaxy S23 Ultra] OnnoJ:
Plenty of YouTube videos show right way...
[Samsung Galaxy S23 Ultra] dr.ketan:
Since last 3 years (A11 or A12) you needs to connect device to PC to enter to Recovery/Download
[Samsung Galaxy S23 Ultra] Xode:
Instead of "Hold power+volume up til the logo appears" , hold power+volume up until you enter into recovery...or watch the video ..
[Samsung Galaxy S23 Ultra] JohnTheFarm3r:
Enable ADB inside the developers settings, and execute a command on the PC via CMD

adb reboot recovery
[Samsung Galaxy S23 Ultra] Filenest:
Wooow, very helpful. Not a complete n00b. Watched them all to no effect.

Did you read my post?

It does not ever enter recovery mode, that is the problem. Did with and without holding both, or only power, no go.

ADB is enabled. Will try your solution, thanks for the suggestion. Will report back.
[Samsung Galaxy S23 Ultra] Filenest:
Thanks a bunch, John, this was the trick that worked, and the solution to my problem. Appreciate it.
[Samsung Galaxy S23 Ultra] dr.ketan:
Apologies, missed it
[Samsung Galaxy S23 Ultra] profi_fahrer:
Did you Update to Android 14? If yes, try to turn off the "Auto Blocker" which is located under Settings -> Security and Privacy
[Samsung Galaxy A32 4G] tiptel170:
Hi there,

I have an Samsung SM-A325F with Android 11, and the problem is I can not wipe out the FRP from the phone.

The steps I had done:

factory reset and reinstalled the Andorid 11, from the StockROM. There no an result for the bypassing the FRP.

I'm at the startpage from the phone, with the emergancy call and type the code " +#0#* ", then I' m in the page for checking the phone, and with the various FRP bypass tools should be activated the USB-Debugging mode.

But nothing is happing, there. Then I open the super.img file and activating manually the USB-Debugging and uploaded to the phone, with the result, it's not an certificated super.img for this phone.

Quellen:
prop.default: https://gist.github.com/gregor160300/068c06c0314c19855e999473708c7635
mounting img-files: https://www.linuxquestions.org/questions/linux-general-1/how-to-mount-extract-a-img-745594/
building super.img: https://xdaforums.com/t/editing-system-img-inside-super-img-and-flashing-our-modifications.4196625/

1. for LZ4 in $(ls super.lz4); do yes | lz4 $LZ4; done
2. Install the otatools - here: /bin/...
3. chmod 777 /bin/otatools/bin/simg2img /bin/otatools/bin/lpunpack /bin/otatools/bin/lpmake
4. /bin/otatools/bin/simg2img ~/android/super.img ~/android/super1.img
5. /bin/otatools/bin/lpunpack --slot=0 ~/android/super1.img /mnt/1 -> it contains four files: system.img odm.img product.img vendor.img
6. mount -t ext4 -o loop /system.img /mnt/2
7. Follow lines has to change in this file: /mnt/2/system/etc/prop.default
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.sys.usb.config=adb
ro.adb.secure=0
8. Save this file
9. umount /mnt/2
10. e2fsck -yf /mnt/1/system.img
11. resize2fs -M /mnt/1/system.img
12. stat -c '%n %s' /mnt/1/*.img
/mnt/1/odm.img 4349952
/mnt/1/product.img 1111625728
/mnt/1/system.img 4985229312
/mnt/1/vendor.img 760479744
13. du -cb /mnt/1
6861684736 /mnt/1
6861684736 insgesamt
14. stat -c '%n %s' ~/android/super.img
15. /bin/otatools/bin/lpmake --metadata-size 65536 --super-name super --metadata-slots 2 --device super:7843348480 --group main:6861684736 --partition system:readonly:4985229312:main \
--image system=./system.img --partition vendor:readonly:760479744:main --image vendor=./vendor.img --partition product:readonly:1111625728:main \
--image product=./product.img --partition odm:readonly:4349952:main --image odm=./odm.img --sparse --output ~/android/super2.img
16. heimdall flash --super super2.img

So what can I do for opening the USB-Port for the debugging?

Greatings tiptel170
[Samsung Galaxy A32 4G] windows4droid:
There are many videos on YouTube
[Samsung Galaxy A32 4G] mvikrant97:
Samsung Galaxy FRP Unlock Thread!

Please apologise me if your thread or messages remain unanswered but I get a lot of messages and notifications from so many thread and users on a daily basis from all over XDA so there would be a delay in answering you back. Thank you for your...

xdaforums.com
[Samsung Galaxy A32 4G] capulin:
download the file AndroidUtility.v114.00.1482.NoSCARD.Edition and on youtube search for this video.... Android Utility No SCARD Edition - v114 solution, download and install Android Utility.... The video will show you step by step how to activate USB debugging on your phone.
[Samsung Galaxy A32 4G] capulin:
Once you have activated the USB by the procedure that indicates, go to the samfw.com page and download the program SAMFW Tool 4.7.1 and with these two programs you can do the FRP safely...
[Samsung Galaxy A32 4G] capulin:
Sorry my bad English I'm using an online translator. With these two programs I was able to make an FRP bypass to a Samsung SM-A325M that they gave me as a gift and they had forgotten the Google account and the password to access the cell phone.
[Samsung Galaxy A32 4G] tiptel170:
My problem is how to enable the USB debugging, from extern. Likes odin, heimdall, fastboot or secret keys over emergency call.
[Samsung Galaxy A32 4G] tiptel170:
I opened the super.img.lz4 with an text-editor and searching for this lines:

ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.sys.usb.config=adb
ro.adb.secure=0

And change the entries, then I save it.

The next step is I had to decompress the super.img.lz4 with this:

for LZ4 in $(ls *.lz4); do yes | lz4 $LZ4; done

And finaly upload to the phone with this command:

heimdall flash --super super.img

And here is the part I'm not shure what is happening:

Initialising connection...
Detecting device...
Claiming interface...
Initialising protocol...
Protocol initialisation successful.

Beginning session...

Some devices may take up to 2 minutes to respond.
Please be patient!

Session begun.

Downloading device's PIT file...
PIT file download successful.

Uploading super
18%
ERROR: Failed to confirm end of file transfer sequence!
ERROR: super upload failed!

Ending session...
ERROR: Failed to receive session end confirmation!
Releasing device interface...

This happens by 1%, 5% or 70% by the transfer. I think, the system-part in the super.img will be transfered but in the phone is the system-part write protected by the FRP protection. I can only transfer the pure super.img to the phone without any manipulation.

There must be an way for overwrite this write-protection in the phone.

And the same is I start the phone and open the MTP driver in Windows, then I can install app in the phone - only from the Samsung store. Apps erxtern, can not install the phone - with the reason "no space left in the device". Clearly, there is the write protection acatived for the system and user.

May be it can help this information.

Greatings tiptel170
[Samsung Galaxy A32 4G] tiptel170:
@mvikrant97,

thank you for your helping hand. In finaly I was able to unlock the phone with the application called zero knox. In the last part I would like install the last stock rom for the lineage os, and the cpu had died. :-( I bought an new mainboard for this phone and fixed it. It was an bad luck.
[Off-topic] cmfCyangenModteam:
Its should be that phone which will had 320x480 resolution,

4GB of RAM i think is enough, would be an 1.6GHz GPU processor, and a processor which would had 2.6GHz, ( 4 cores) Bluetooth 3.0, WiFi 4, and GPS,

There would be an audio jack, micro USB, and a sound speaker behind the phone at lower part,

There would be an 9000mAH battery, and a frontal/back camera which would had 13MP, and a frontal sound speaker, there would be an flashlight near the camera (down)

This just seems like a crazy cake, just my concept.

(Please make this post into Off-topic, i accidentally clicked this section,)
[Off-topic] InTheCage:
How about a phone without a screen with a full size hdmi cable attached.

That way you can plug into any tv and make calls, browse the internet, endless possibilities.

All jokes aside, you don't tell us why you want this kind of telephone, why for example is Bluetooth 3.0 important?
[Off-topic] cmfCyangenModteam:
This seems a crazy idea, but it limits phone to that level than it cant be literally used outside, Just imagine yourself carrying a big TV after all.

About BT 3.0: That phone would be just, an literal testing machine, not even intended to use like calls, SMS, MMS, etc.

After all, the system would be just Android 2.3

Only pure tasks, nothing else, no internet access, etc.
[Off-topic] karandpr:
Not so crazy really. They already make those lol.

Except for the battery ,you just described a Unihertz Jelly phone.

Jelly Series

Shop Jelly series smartphones and their accessories from Unihertz now! Running Android OS, these palm-sized smartphones can meet your daily needs while sparing more space for your pocket or handbag! They're also designed for outdoor activities thanks to their light weight and tiny size. Shop...

www.unihertz.com
[Off-topic] cmfCyangenModteam:
Oh man, i didnt even think that when posting this, to be honest

Im also pretty wondered than these phones support a/b/g/n mode for WiFi,
[Off-topic] popopopo1:
And a SD port, for saving medias files.
[Moto G40 / G60] Annuart:
*DO THE PROCEDURE AT YOUR OWN RISK, I WILL NOT BE RESPONSIBLE FOR ANY DAMAGE OR BRICKS ON YOUR PHONE*

I managed to relock the bootloader in my phone using Android 12. Sadly, as far as I know, there is no safe way to relock your bootloader on Android 11. I'll assume that you already have the drivers and adb installed. Remember to always backup your media and personal info before doing anything.

Things you will need (I don't know if i can provide links,so you'll have to search on your own):

Motorola Mobile drivers (found in motorola support pages)

ADB setup

Lenovo Rescue and Smart Assistant (RSA) (just google the whole name and will be one of the first results)

Stock firmware (You can find it on pages like MOTO STOCK ROM or lolinet)

The knowledge or a tutorial to install the stock rom through ADB (although there are many videos for different phone models, you can use the same procedure as long as you use your corresponding firmware files)

1.- Install the moto g60 corresponding stock firmware (which will be A11). For the dual sim 6GB/128GB are the ones with the name XT2135-2 RETIN. The "RETIN" part can vary depending on your phone update channel (You can find the firmware in pages like MOTOSTOCKROM or lolinet).

2.- After installing stock firmware, boot your phone and make sure that everything is working (you can skip the google account setup).

3.- Download and install Rescue and Smart Assistant (RSA) on your PC.

4.- Reboot your phone in bootloader mode, connect the USB to your PC and use RSA to install the latest available firmware for your phone.

5.- Once the phone is updated, boot the system to make sure that everything is working.

6.- Reboot in recovery mode and wipe/factory reset.

7.- Once again, boot your phone to check if everything is in order.

8.- Reboot in bootloader mode and connect it to your PC.

9.- Through CMD, type "fastboot oem lock" (WITHOUT THE QUOTES) and press enter.

10.- The phone will ask if you want to relock the oem. Use volume -+ to move and select the affirmative option.

11.- DO NOT REBOOT TO SYSTEM YET. In your CMD type "fastboot reboot recovery" (WITHOUT THE QUOTES) to enter the recovery and do another factory reset.

If you did everything right, you can boot your system and the phone will start normally. Until now I've realized this procedure 2 times and both have worked, but there's always the risk of something going wrong or just having really bad luck.
[Moto G40 / G60] ZG_DEV:
Thank you for this great guide !
[Moto G40 / G60] sharunyhtgg:
in step 1, i need to flash rom using RSA or .bat method?
[Moto G40 / G60] Annuart:
.bat