yashsingh1/xdaforums huggingface dataset:
[Nokia G10 / G20 / G21] kali77noob:
I got a Nokia G300

Product- aoki

Variant- sm-emmc

The first sock screen I make, Its telling me that is the wrong one. Does anyone here know of a work a round for this???

Please im without a phone and on a borrowed laptop. I really need to get this phone working.

Even if it is a Factory Reset Option or Root

PLEASE HELP:unsure:

:unsure:
[Nokia G10 / G20 / G21] mvikrant97:
You want to factory reset the device?
[Nokia G10 / G20 / G21] Samarimama:
He says yes
[Nokia G10 / G20 / G21] Samarimama:
What do you mean by sock screen ?
[Nokia G10 / G20 / G21] mvikrant97:
Power off your phone completely.

Hold Volume Down and Power key together and release the buttons once you see the Android One logo on your phone screen.

Now your phone will be in fastboot mode.

Install ADB and Fastboot drivers on your computer and open CMD and connect your phone in fastboot mode.

Type command fastboot erase userdata and the phone shall reset.

if the above command does not works, type put phone in fastboot mode again and type command in CMD as follows

fastboot reboot-recovery or fastboot reboot recovery.

Please let me know if this helps.
[Nokia G10 / G20 / G21] kali77noob:
Only if i have to though. Im just tirred of fu***ng with it
[Nokia G10 / G20 / G21] kali77noob:
fastboot reboot recovery did not work.....

and i got this when i did>>>>>>>>

fastboot erase userdata

C:\WINDOWS\system32>fastboot erase userdata

erasing 'userdata'...

FAILED (remote: did not have permission to erase)

finished. total time: 0.009s
[Nokia G10 / G20 / G21] mvikrant97:
Can you give remote access to your computer so that I can use another tool that can reset your device?
[Nokia G10 / G20 / G21] kali77noob:
Nope not giving remote access to anyone..... I was able to delete the file that held the screen lock pass code..... But do u have a Root Solution by chance?
[Nokia G10 / G20 / G21] mvikrant97:
I do understand your concern. I would first recommend you to unlock bootloader and then use magisk to patch the boot.img.

I cannot do bootloader unlocks for Qualcomm phones.
[Nokia G10 / G20 / G21] GameraRebirth67:
yes i do
[Nokia G10 / G20 / G21] GameraRebirth67:
helo i need my nokia g300 remote hard reset fastbook cammands dont work and keep gett ?dont have permission to erase? message
[Nokia G10 / G20 / G21] GameraRebirth67:
let me kmow i can give you

my ulteviewer codes
[Nokia G10 / G20 / G21] mvikrant97:
Please don't share it here. I will get back to you with a possible solution to unlock your device.
[Nokia G10 / G20 / G21] GameraRebirth67:
ok i will stand by
[Nokia G10 / G20 / G21] GameraRebirth67:
hello i have a nokia g300 that i need help factor reseting.i ve tried thge fastbook cmd prompt method i get a you dont have permission message please help
[Nokia G10 / G20 / G21] mvikrant97:
You will have to avail online paid service. Please PM me as I cannot discuss it on the forum.
[Nokia G10 / G20 / G21] SolusVir:
Is that an open offer? Cuz I've got a brick that used to be a Nokia G300, and a computer I don't much value, so I'll take the chance.
[Google Pixel 6 Pro] yuuou:
The pixel6 pro has an automatic reboot after aosp is flashed in, then it won't boot and becomes a brick, all buttons are unresponsive. I don't know what the problem is, the original Android version is 14, the one I flashed in is 13.

After installing the driver and plugging it into the computer, the port device will appear, and the QFIL software can recognize this port. Need "FireHose Programmer" && "rawprogram*.xml,", please help to solve the brick method or related resources

View attachment 5898953

View attachment 5898955

Since there is no Google service in my area, I can't send it back to the manufacturer for repair.
[Google Pixel 6 Pro] GcamApk:
If your Pixel device is hard bricked, meaning it is completely unresponsive and cannot be turned on, there are a few steps you can take to try to resolve the issue. Here are some steps you can try:

Try a hard reset: Press and hold the power button and volume down button simultaneously for at least 15 seconds to perform a hard reset. If your device is responsive, this should force it to reboot.

Check your USB connection: Make sure that your device is properly connected to your computer via USB. You can try using a different USB port or cable to see if this resolves the issue.

Use fastboot to flash a factory image: If your device is still unresponsive, you can try using the fastboot tool to flash a factory image onto your device. This process can be complex and may require technical knowledge, so it is recommended to follow a detailed guide or seek professional assistance.

This is based on my experience but maybe some expert can suggest better treatment, I request them to suggest a solution.
[Google Pixel 6 Pro] yuuou:
Thank you for your answer.

1. no response to any key operation on the device, the power button volume keys +- tried many times for a long time, there will be no response

2. replace the usb and port to connect to the computer there is no connection device other than the com port

3. I can't connect the phone to the computer to use Google's online fastboot tool to reset the phone because I can't turn it on.

Thanks again for your answer.
[Android Auto General] elbrunzy:
My project is to use an RPI4b running KonstaKANG ROM in my car as an dedicated AA device. My car have a nice dashboard but there is absolutely no guidance service. The primary goal would be to use an offline map service. I have tested AA and CarPlay with standard cellular over USB and they work.

My first tentative where done with AOSP13-20230130-KonstaKANG-rpi4.zip (not sure about the 6.1 kernel) and lineage-18.1-20220512-UNOFFICIAL-KonstaKANG-rpi4. While they worked well on the device with a keyboard/mouse/hdmi, I later realize my USB OTG cable was in fact just a charging cable. So of course results where negative.

My second attempt, using better cable, was a bit more interesting. But I was feeding only 2.1a to the OTG USB, so the RPI4b felt a bit sluggish because of underpowered I guess, I have some of those cables on order to give required power to the RPI4b but in the meantime I will just need to be patient. I tested using build lineage-19.1-20230313-UNOFFICIAL-KonstaKANG-rpi4.zip. I wanted to use flamegaps but it would say that "version 12 is not compatible with 12.0" so I did try mindTheGapps and NikGapps, both seem to had the same result. I used AA 8.9.630603 with and without the XLauncherUnlocked v2.0.1. My result where at some point I got error 22, which bring me to try this xda-guide. I installed logcat I was able to snap this from the log :

---

W InputDispatcher :

ActivityRecordInputSink comdp.logcatapp/.activities.FiltersActivity will not receive the gesture at 2051644...

I InputDispatcher

Droping event because there is no touchable window or gesture monitor at (90,99) in display 0.

---

I know it's not as useful as full log, but for now it's all I could salvage from this tentative and it's a information so I note it.

I intend to do a third test this week-end with this version AOSP13-20230412-KonstaKANG-rpi4. Hopefully I will have full log to report back.

Aside from XLauncherUnlocked, I want to also try this AA AIO Tweaker that seem quite interesting. It's option to enable widescreen remind me that I had some consideration about if dashboard and AA would not want to connect because running an RPI4b simulate an 1920x1080 screen that would be incompatible to a car dashboard ?

I'm sorry if that post seem a bit picked up for now but I hope the situation will clarify over time as I wont write from memory, wandering files and jolted notes.

- Should I use v8a or v7a when I download a build of AA from APKMirror ? I found recently that Magisk state I have v8a, is it trustable information ? Maybe it invalidate all my test done with v7a. But from what I read about it, I dont think it make much a difference, but could be someone know better ?

- What would be my best option to run AA and see logs ? Since I'm in a car maybe I can bring here a laptop to do ADB over USB would be faster than setting up Wi-Fi ADB ? I think at this point, collecting logs is the most important part of my investigation. But I'm not so sure how to do it efficiently. I would be thinking than to do something like that and collect the log while I try to connect AA to the dashboard would be the way to go.

Cheers
[Android Auto General] elbrunzy:
I could test the new configuration this week-end. Unfortunately I did not had much luck but now I have debug log and precise description of what I did. One thing I noted is that AOSP13 was very fast, so the sluggishness was not from the RPI4b lacking power it seems. I could debug with logcat using Android Studio via Wifi, it was awesome to see all this working. Here is the configuration I used :

aosp 13 : AOSP13-20230412-KonstaKANG-rpi4

mindthegapps : MindTheGapps-13.0.0-arm64-20230408_162909.zip

magisk : 25.2

busybox : com.jrummy.busybox.installer_6.8.2

systemizer : app_systemizer-v18.

androidAuto : 8.9.630604-release-89630604_minAPI26(arm64-v8a)(nodpi)

I think systemizer might not be necessary as the AA seem to be already system installed as there was no uninstall option in app info. I could copy the log as systemizer.log attached..

Reading the log it appear obvious to me that it's related to that error you keep on seeing whatever test I do. It would appear twice in the log as soon as I click on the "pair a car" in AA.

Checkbox request failed

jwu: 17: API: UsageReporting.API is not available on this device. Connection failed with: ConnectionResult{statusCode=SERVICE_INVALID, resolution=null, message=null}

it seem this error to appear all the time, but I pursued the test and attached other logs. You can see the full log with the file logcat_aa8.9_1.txt.

+ add AA-AIO-TWEAKER-5.2.2-hotfix-release :

I disabled tab limitation, bt autoconnect, telemetry. The log error was similar so I saved nothing. But this thing seem very hot and I will certainly use it if I ever make it.

+add enabled zygisk, lsposed 1.8.6. shamiko 0.6, AA XLauncher 2.0.1 (w/ kinginstaller), enabled AAXLU in LSPosed :

shamiko 0.7 cannot install because magisk need to be 2.6, but shamiko 0.6 seem to work with magisk 2.5. I did try different way to launch AA using XLauncher but each time the same checkbox related error message in logcat_aa8.9_2.txt.zip.

~replace with NikGapps-basic-arm64-13-20230418-signed

Since it seem related to some API I did try to change the GApps but I'm not sure I can just bump mindthegapps with nikgapps, but I did try. The swap seemed to work but after that I could not log with Android Studio anymore for some reason so I used ADB shell to save logcat, maybe something else can be seen using it logcat_aa8.9_3.txt.zip.

~upgrade to AA projection.gearhead_9.3.631404-release-93631404_minAPI26(arm64-v8a)(nodpi) :

As a last resort, I did try to upgrade to AA 9.3, but the error about missing UsageReporting.API support was again here logcat_aa9.3_1.txt.zip.

I guess now I need to research about that API and understand why it missing... I'm thinking maybe it's because I did not registered google play service with my account to avoid it upgrading AA automatically. I'll check this out and get back later.

Cheers,
[Android Auto General] elbrunzy:
I was able to fix the UsageReporting.API is not available on this device. by registering the device with playprotect. Then I systemized gearhead, installed latest version that also work on a cellphone (9.3.631434), put AA in debug verbose mode and I get back with the error log about a leaked windows and dropping event because there is no touchable window at (x,y). I'm using a mouse/keyboard and hdmi display when I try to connect AA with the car, so maybe this is not considered as a touchable windows for AA ? Maybe there is touchable windows emulator I could use ?

At this point I start to get out of idea and it seem I get back to my initial point. Has anybody was able to use an raspberry pi as an AA client device ? I think my next step would be try that aa4mg thing, but I'm not so sure what is microG and if those KonstaKANG rom are compatible with it ... oh well, I guess there is only one way to know it.
[Android Auto General] elbrunzy:
Reading about aa4mg lead me to omnirom which seem interesting and look awesome on an rpi4b. I did try the omni-13-202303081341-rpi4-MICROG. Unfortunately I could not quickly install magisk to install aa4mg (there is that tutorial I could try) so I proceed a parallel task to try a fresh version of :

rom :

= lineage-19.1-20230313-UNOFFICIAL-KonstaKANG-rpi4.

install :

+ Magisk 25.2

+ f-droid

+ microG Service Core (via fdroid)

+ aa4mg (via magisk) (! should have volume ctrl here, but default seem fines)

+ aurora store (via fdroid) - AA is not there anymore

+ busybox (aurora)

+ app-systemize (via magisk)

+ kinginstaller

+ android auto 9.3.631434 (via kinginstaller, not rooted)

do :

> systemize : com.google.android.projection.gearhead

> give all permission to AA

> default USB mode : file transfer or USB tether

at this point I get the error "android auto wont run without google play services which are not supported by your device" but what is interesting is that AA seem to run on startup as it would detect the car is plugged. I've yet to receive those power-usb-otg cable so for now I can only say that since AA run on startup of a boot from lineageos if the RPI4b is plugged in the car dashboard.

So what's next ? I will maybe try 8.3 version of AA as I read about the error message of google play services could be fixed using prior version of software, but also review microG Service Core setup as I though this was supposed to replace the play services. Apparently my GmsCore has not the correct signature, so maybe there is the problem since I read it allow GmsCore to pretend to be GooglePlayService. Probably that Konsta KANG LineageOS for RPI4b need extra step to support signature spoofing. So I think I will leave it there for tonight, time goes so fast when you are busy ! According to that wiki, next item on my list of install is Xposed and also lsposed which I already installed in the past :) https://github.com/microg/GmsCore/wiki/Signature-Spoofing
[Android Auto General] elbrunzy:
I could not find procedure to do signature spoofing using zygisk so I did try the riru way :

install :

+ riru-v26.1.7.r530.ab3086ec9f-release

+ LSPosed-v1.8.6-6712-riru-release

+ fake_GApps_4.2_app-release

_> FakeGapps : System Framework (default recommended), added FakeStore 0.0.2, added microG Services Cores 0.2.27.223616

_> AAXLU enable module : Android Auto (default recommended), added System Framework, added FakeStore 0.0.2, added microG Services Cores 0.2.27.223616

I though I had stuff to setup to activate signature spoofing, but apparently a reboot and AndroidAuto would not complain anymore about missing Google Play Service ! Quickly Android, to the Carmobile ! I can honestly say my heart skipped a beat when I saw AndroidAuto authorization start on the car dashboard and car pairing tutorial on the Raspberry Pi 4b 🤩. Another good news was also awaiting me there, as I received those USB-USB-C_OTG_Power cable ordered in my first post, and they would work. So I could provide required amp/voltage to the RPI from auxiliary power outlet while using another port for usb data.

The pairing process on LineageOS's AA could not finish as some of the prerequisites apps where not installed, Here is what is missing :

(present) : Android Auto

(missing) : Google App

(missing) : Google Maps

(missing) : Google Text-To-Speech

I also noted you could not start AA from AAXLU in either material3 or stock mode. I will check this out after I will be able to successfully finish the car pairing wizard.

Before I proceed further I will take a clone backup of the microsd and take a break as there is just so much emotion a man can sustain. Of course I dont think I will wait long before install prerequisites and pursue investigation.
[Android Auto General] elbrunzy:
I was able to fix prerequisite this way:

+ install GSF from f-droid's microG repo.

~ fix background location servce permission thanks to ploink here.

~+ check permission : dumpsys package com.google.android.gms | grep granted=false

~+ add permission via adb shell su : pm grant com.google.android.gms android.permission.ACCESS_BACKGROUND_LOCATION

+ aurora store : google 14.17.24.28 arm64 (301236347)

+ aurora store : google maps (11.77.0300)

+ aurora store : speech service by Google (require GSF)

So the wizard would finish but keeping reporting that Maps "Permission needed, google maps in android auto needs a certain permission to work effectively. Review this permission in Settings : Location Allows Maps to determine your device's location" even if it is set. Google App would ask me to logon but complain that the account already exist on the phone. For now I'll just skip that. As I more important problems, the developper settings would crash if I try to acces them, the screen would randomly freeze or display garbage when connection the usb.

I will review those error but what I think I will try next is to see if AndroiAuto AIO can provide any insight on the problem. Try to rollback to AA 8.9. See what debug log tell about the problem.
[Android Auto General] elbrunzy:
Since I was getting some GMSCore permission problems on LineageOS I thought I would give OmniRom since there is a rom for Rpi4b !

omnirom : omni-13-202303081341-rpi4-MICROG

Note, install nikgapp AA at the very beggining as it will otherwise wipe data and many thing will need to be redone.

Here is what I installed :

+ magisk 2.6.1 (enable zygisk) patching with mkbootimg + unpackbootimg. Instruction from rsaxvc.net.

+ aa4mg-v0.6.1.zip (magisk) : (follow install instruction on github + disable wireless screen)

+ LSPosed-v1.8.6-6712-zygisk (magisk)

+ shamiko-v0.7.1-166 (magisk)

+ android auto (modded to remove nikgapps prerequisites), forum.xda-dev thread

+ google app (aurota store or apkmirror)

+ google tts (aurota store or apkmirror)

+ google map (aurota store or apkmirror)

tested to downgrade google map 10.87.4 using : pm install -i "com.android.vending" <apk>

With this procedure it's the farthest I went so far, although it was not working. Each time I would plug the RPI on the car I would need to redo the pairing wizard, with the green error message that Google Maps need location permission (I think I gave everything I could think of). After that, on the RPI it ask to finish the wizard on the car dashboard which is showing an empty screen. I think I will try with OmniRom Android 12 or lower version I could find, of course if anybody has idea for me I would be more than happy to hear about it.
[Android Auto General] elbrunzy:
I installed omnirom 12 for rpi in a similar way as my previous post and results are the same. AA say to continue setup on car screen which is displaying an empty screen. I'm not so sure what to test anymore and start to think it just wont work. I collected a log of when I plug the cable on the car to when I finish the wizard, maybe someone will see something ?
[Samsung Galaxy S21 Questions] juntjoo:
For now I just want to be able have quicker access to deep settings like force dark mode on incompatible apps which is in USB debugging and I want a 5g/4g toggle switch. Are either of these possible with customizable ROM and root access? I've installed ROM'S a couple times before with past phones and liked all the added functionality. Just on the fence Atm. Have you with your s21 and what do you do it for?
[XPERIA X1 General] jhoward1082:
Does anyone know how to uninstall the "stock" version of Opera 9 that comes with the ROM? It does not show up in the remove programs list. I prefer Opera 9.5 beta and would like to get rid of the stock Opera 9 that comes on the device. Any help would be much appreciated. Thanks
[XPERIA X1 General] saq11:
I would also like to know how to do this. I really like the zoom feature in the new beta.
[XPERIA X1 General] contaygious:
i'm suprised you got the new beta to work. I have nothing but issues with it. When I open the bookmarks for instance and then close it, it says opera at the top of my taskbar, but opera is no where to be seen.

What's the new zoom feature exactly?
[XPERIA X1 General] cursor:
can't you just install opera 9.5 over 9?
[XPERIA X1 General] jhoward1082:
No, unfortunately it leaves the stock version alone and installs another instance
[XPERIA X1 General] kheavy:
Mine is located as a java app - requesting to use bandwidth - repeatedly
[XPERIA X1 General] artesea:
Yours is a different app called Opera Mini.
[XPERIA X1 General] cursor:
oh, thats bad.

um, and if you install it, copy the files to sd card, uninstall and then overwrite 9.0 files with the new ones?
[XPERIA X1 General] jhoward1082:
The beta actually installs in the program files folder, either on the device or storage card depending what you pick obviously. Stock Opera installs directly in the windows folder. I may try just copying the beta files into the windows folder and see what that does, naming them the same obviously, so it overwrites
[XPERIA X1 General] nap007:
nobody know how to uninstall it?
[XPERIA X1 General] hmanxx:
if i dont mind having 2 separate programs,will the 9.5 beta will work
[XPERIA X1 General] guru_fordy:
Yes I had it working like this on my first X1 build. Bit annoying as hyperlinks to 'Opera Browser' are lotteries to which will open lol
[XPERIA X1 General] dadeadman:
Btw which version of opera must i use? Advanced generic has tiny on screen buttons due to the res
[Xiaomi Poco X3 NFC ROMs, Kernels, Recoveries, & Ot] Carlos Arriaga:
ArrowOS

​

/*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, We will laugh at you.
* It is your fault because you chose to do all the modifications on your device.
* Remember projects like these and the work done on them is a hobby to the
* contributors and the team members, no one is working for you nor is getting paid for it
* have some respect for the work done by them since it is done purely on interest or a hobby
*/

ABOUT

ArrowOS is an Android Open Source Project based Android mobile operating system started with the aim of keeping things simple, clean and neat.

Website: https://arrowos.net

Telegram: Channel | TG Portal/Links

Github: https://github.com/ArrowOS

Code Review: review.arrowos.net

E-mail: arrowos.contact

PayPal: Donate to us

Blog: blog.arrowos.net

Checkout more documentation at (maintainership/contributing): Check this out

WHAT WORKS?

Almost everything

KernelSU Support

Miui Camera Support

WHAT DOESN'T WORK?

You tell me

Be sure to include a log : check how to

DOWNLOADS

Vanilla build | Gapps build

Read our blog article/post about:

* HOW-TO report a bug

* GAPPS and VANILLA variants

* Checking build integrity

GPL compliance:

ROM Source- https://github.com/ArrowOS

Kernel Source- https://github.com/xiaomi-surya/android_kernel_xiaomi_surya
[Xiaomi Poco X3 NFC ROMs, Kernels, Recoveries, & Ot] Carlos Arriaga:
Telegram group support
[Xiaomi Poco X3 NFC ROMs, Kernels, Recoveries, & Ot] SmartJuwel:
Hi, very nice with MIUI Camera 👍

Do you plan to integrate the MIUI-Gallery too?
[Xiaomi Poco X3 NFC ROMs, Kernels, Recoveries, & Ot] Carlos Arriaga:
In the future possible
[Xiaomi Poco X3 NFC ROMs, Kernels, Recoveries, & Ot] Truzzman2:
How to install? after the first boot I'm unable to setup google account. The google accounti input screen desappear after fews seconds
[Xiaomi Poco X3 NFC ROMs, Kernels, Recoveries, & Ot] SmartJuwel:
Use latest NikGapps Core
[Xiaomi Poco X3 NFC ROMs, Kernels, Recoveries, & Ot] SmartJuwel:
I found a little bug. PowerOffAlarm is not working.
[Xiaomi Poco X3 NFC ROMs, Kernels, Recoveries, & Ot] sebashebe:
Can not find face unlock
[Xiaomi Poco X3 NFC ROMs, Kernels, Recoveries, & Ot] Truzzman2:
I used it but same result, the page for google account where insert emai address from gmail, disappear after few swcond