yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Q&A, Help & Troubleshooting] ehteshamxa:
Carliv Image Kitchen stuck it initial boot logo

Gooing to use Android ver Would it also work on signed images (maybe if my image was signed)
[Galaxy S II Q&A, Help & Troubleshooting] osm0sis:
Yep, AVBv1 is supported, and a few others.

Carliv's and dsixda's are both extremely outdated. Use mine? I see no reason your boot.img shouldn't repack without issue and let you make the modifications I told you above.

Others already suggested using AIK, but you're still using sh*t from 2013 and 2016 for some reason when mine was updated in May. 🙄
[Galaxy S II Q&A, Help & Troubleshooting] ehteshamxa:
Thanks a lot finally got a working boot.img.

But setting these in default.prop:

ro.adb.secure=0

ro.secure=0

ro.debuggable=1

didn't work to bypass rsa authentication.

I am hoping if its possible to place adb_keys using boot.img and system.img (folder init.d isn't here)
[Galaxy S II Q&A, Help & Troubleshooting] alecxs:
do you still get adb devices "unauthorized" or is that other issue?

did you set permissions?

chmod 0755 /path/to/rsa_copy

edit: please show your install-recovery.sh it should work regardless executable or not, if you call it as argument to sh

you could also call the script from userinit.sh if you add the line there instead (the idea behind was avoid flashing system over and over again)

once script is running there will exist rsa_copy.log on /sdcard and if adbkey.pub is found on /sdcard it will installed into phone (that one you have copied from %USERPROFILE%\.android\adbkey.pub from your windows PC or ~/.android/adbkey.pub from your linux PC), and vice versa (existing adb_keys is copied from phone to /sdcard and could be installed to .android directory on PC) either .. or

just double check /sdcard exist and is targeting your emulated Internal Storage, removeable MicroSD Card or is accessable via MTP at least, otherwise the whole purpose of that scripts is pointless ;)
[Galaxy S II Q&A, Help & Troubleshooting] osm0sis:
If you set those correctly you don't need to authenticate at all. It's called "adb insecure", and you can do it as soon as the device hits the bootlogo.

You have an old non-SAR device with default.prop in the boot ramdisk, so there shouldn't be anything else for you to do; I have a feeling you just didn't modify the file/values correctly.
[Galaxy S II Q&A, Help & Troubleshooting] alecxs:
Warning! insecure! use for temporary access on broken screen only

- added /sbin/99userinit_daemon

- modified default.prop

- modified init.rc

boot image from fastboot (or flash with SP Flash Tool)

fastboot boot <file>

Only in case adb still not working:

copy your PC's adbkey.pub to phone. check rsa_copy.log for info about success. reboot phone

(attachment removed)
[Galaxy S II Q&A, Help & Troubleshooting] ehteshamxa:
Thank you for the modified file

but as i said I can not copy file to phone internal storage not mtp(copying file access to phone.

May i place file (adbkey.pub userinnit.sh) on external microsd and change path from /sdcard/ to /storage/0000-8982/

/0000-8982 is memory card folder name getting same on on different devices. would the MicroSD mount at that time
[Galaxy S II Q&A, Help & Troubleshooting] ehteshamxa:
Even adb devices cmd isn't listing the phone now and no RSA prompt

phone's USB debug is enabled
[Galaxy S II Q&A, Help & Troubleshooting] alecxs:
yes that will work
[Galaxy S II Q&A, Help & Troubleshooting] ehteshamxa:
Had you also placed rsa_copy script in boot .img?

or do i still have to place it in system.img
[Galaxy S II Q&A, Help & Troubleshooting] musawarAnwar:
Hi, I'm having the same issue with my Huawei P Smart. Is this also applicable to Huawei?
[Galaxy S II Q&A, Help & Troubleshooting] ehteshamxa:
i think so :)
[Galaxy S II Q&A, Help & Troubleshooting] ehteshamxa:
can I paste the rsa_copy script inside userinit.sh ????
[Galaxy S II Q&A, Help & Troubleshooting] alecxs:
only /sbin/99userinit_daemon is placed in boot.img other files must placed /sdcard yourself (or MicroSD Card if you edit all files with proper path)
[Galaxy S II Q&A, Help & Troubleshooting] ehteshamxa:
not worked by placing it in 0000-8982 microsd
[Galaxy S II Q&A, Help & Troubleshooting] ehteshamxa:
init.d isn't found in system.img and boot

where do I place rsa_copy script to make it run with root privileges
[Galaxy S II Q&A, Help & Troubleshooting] alecxs:
No, I am not aware of any flash tool for Kirin chipset. Furthermore Huawei deny booting on modifications in ramdisk.img anyway, even if AVBv1-signed (I tried on Huawei Y6 2018 it did not work)
[Galaxy S II Q&A, Help & Troubleshooting] alecxs:
place the script on /sdcard

kindly refer to post #31

there is nothing to be placed in /system (I didn't mention init.d)

download attachment and edit all files with AIK and Notepad++

(did you try it btw - adb insecure is already set!?)
[Galaxy S II Q&A, Help & Troubleshooting] ehteshamxa:
just found my manual using the script using android terminal that script is good to go with for copying from /0000-8982/ to data/misc/adb

but script isn't invoking automatically at boot time to copy adb.
[Galaxy S II Q&A, Help & Troubleshooting] ehteshamxa:
Sir @aIecxs

Sir there's code after ur code in default.prop after flashing
[Galaxy S II Q&A, Help & Troubleshooting] ehteshamxa:
yes 2 values set to 0 and debuggable to 1

can you tell me where do I place rsa_copy to run

Also can is it possible to write" touch /storage/0000-8982/testfile "

inside 99deamon to test weather boot is reaching to that point or not.
[Galaxy S II Q&A, Help & Troubleshooting] alecxs:
that doesn't look like Notepad++

if that is content of default.prop I must have done something stupid. please delete that file and throw it into garbage.

edit: couldn't find anything from your screenshots. if I unpack it on my PC everything looks fine. I have changed path to external MicroSD Card now, please try again

(attachment removed)
[Galaxy S II Q&A, Help & Troubleshooting] ehteshamxa:
init.rc isn't triggering 99userinit_daemon

While 99userinit_daemon is configured correctly working fine when called manually.

P.S doing all on test phone to see the results.
[Galaxy S II Q&A, Help & Troubleshooting] alecxs:
might be the case I did it wrong. but most likely it simply does not boot at all
[Galaxy S II Q&A, Help & Troubleshooting] ehteshamxa:
99userinit_daemon is correct just dont know why init.rc isn't trigging

is there any other thing than oneshot (i think it runs scrip only once)

what if we try to rrun it multiple time is there any variable for that
[Galaxy S II Q&A, Help & Troubleshooting] alecxs:
That was also my first thought. But according to this answer setting ro.adb.secure=0 works only on userdebug/eng builds.

"adb insecure" is when the adbd binary is replaced with a modified one. @Chainfire provided some app for this 10 years ago
[Galaxy S II Q&A, Help & Troubleshooting] osm0sis:
I've used it to get kernel logs for years.. it definitely works. adb root won't, that's a whole other thing, but it will start you as root user with adb shell when those props are set in my experience. 🤷‍♂️
[Galaxy S II Q&A, Help & Troubleshooting] ehteshamxa:
Exactly ,I had tested this on an authorized device (MT6735 and Android 6) by turning off USB debugging and flashing this edited default.prop , didn't worked. Both RSA public key and and USB debug enabled was required.
[Galaxy S II Q&A, Help & Troubleshooting] ehteshamxa:
I solved the problem by adding following script in userinit.sh:

# Waiting to copleted RSA_copy script (copying the public keys)
sleep 30

# Enables the Developer Mode
settings put global development_settings_enabled 0
sleep 5
settings put global development_settings_enabled 1

sleep 5

# Enables the USB Debugging
settings put global adb_enabled 0
sleep 5
settings put global adb_enabled 1

I do hope it will work for the others finding the solution

Once again thanks @aIecxs
[Galaxy S II Q&A, Help & Troubleshooting] EWill9:
Hi bro I cannot run the command to capture the adb-keys file. I get the following error:

path in my pc \platform-tools_r33.0.3-windows\platform-tools>adb shell

a50:/ $ ls-l

/system/bin/sh: ls-l: inaccessible or not found

could you help me get past this
[Galaxy S II Q&A, Help & Troubleshooting] MarovEsnaen:
I have the same issue, my phone is Samsung A8 2015 SM-A800F. It's running stock Android 6, the screen is broken, i can't see anything, nor touch anything.

USB Debugging is enabled

I want to move the files from my phone to my computer, but the problem is my phone not rooted yet

Of course it's detected on ADB, but the status is unauthorized. Don't know how to pull adb_keys to my phone while the screen is broken.

can anyone help me?
[Galaxy S II Q&A, Help & Troubleshooting] EWill9:
you are not authorizing adb PC access in the same device that you have to use " adb" to access. adb is used on an authorized device to capture its add keys. after that, we take those keys and push them into the device where adb authorization for the PC does not exist.
[Galaxy S II Q&A, Help & Troubleshooting] alecxs:
I was refering to steps 7. = 8. authorizing adb keys for same device you already have adb access (without key)
[Galaxy S II Q&A, Help & Troubleshooting] Renate:
The command is ell-ess-space-minus-ell
[Galaxy S II Q&A, Help & Troubleshooting] EWill9:
Thank you 😊 . Have you been able run this tutorial successfully?
[Galaxy S II Q&A, Help & Troubleshooting] Renate:
The original post talks about how to do this using methods that are no longer readily applicable.

There are at least four five basic ways to "authorize":

click authorize on the ADB popup

change ro.adb.secure to 0 in prop.default

replace adbd with a patched version that doesn't require authentication ever

add your public key to /data/misc/adb/adb_keys

add your public key to /adb_keys (easy to do with a ramdisk)

All of these run into some "Catch 22" as they would all be easier with ADB running.

If the touch part of the screen is working, that's a plus, but getting anything to work poking blind is difficult.

Using an USB OTG mouse to enable a Bluetooth mouse to authorize the ADB popup is also a challenge.

Depending on Android version mounting /data in recovery and modifying is probably not possible.

Modifying /system in recovery also runs into problems with dm-verity, AVB.

Modifying a boot image and flashing it is possible if you deal with dm-verity, AVB.

Depending on your recovery, you might need low-level tools (like EDL) to pull a copy of your boot image.

You don't need to do that. The public key is already on your desktop.

In Windows it's C:\Users\Username\.android\adbkey.pub

This is the public key (i.e. non-secret) and is around 700 bytes.

The best advice is to always have ADB on, always have ro.adb.secure=1 (for security) and to make sure that your device is authorized on a desktop or two.

Also, backing things up is not a bad idea.
[Galaxy S II Q&A, Help & Troubleshooting] EWill9:
So basically there is no hope there. Because my device is an sm-j530 Samsung and it has no screen attached, I had to remove it since it was shattered. Unless you know some android OTG hotkeys to turn on mobile data?
[Galaxy S II Q&A, Help & Troubleshooting] Renate:
Are you using Magisk already? Or does your boot image have a ramdisk?

I don't love/use/know anything about Samsung devices. Can you replace the boot image without the device exploding?

If you can replace your boot image and you already have or can add ramdisk you just need to add adb_keys in /

(I edited the post above to mention that.)
[Galaxy S II Q&A, Help & Troubleshooting] EWill9:
I don't have any of those unfortunately. Wish there was a way to my stuff.
[Galaxy S II Q&A, Help & Troubleshooting] Renate:
Are you sure that your device has no video output over the USB connector MHL/DP/HDMI capability?

Using OTG, a hub, a keyboard and a mouse would be a challenge.

Still, at least with a keyboard navigating with arrows would be less problematic than a mouse.

Actually, a digitizing tablet would be good as it's absolute and not relative like a mouse.

If you had an identical device to use as reference it might not be too bad.

Just put down a piece of paper and mark it and use it as reference.

You could also borrow a screen from somebody/somewhere. You don't need to unglue the old one, just connect the new one with it loose.
[Galaxy S II Q&A, Help & Troubleshooting] EWill9:
Any chance we could connect and have chat sometime? then I could show you my device
[Galaxy S II Q&A, Help & Troubleshooting] alfanveykov:
Please how to do it, after flash zip, my phone bootloop,
[Galaxy S II Q&A, Help & Troubleshooting] alfanveykov:
why the file is removed, i need it brother
[Galaxy S II Q&A, Help & Troubleshooting] alecxs:
No, you don't need file for QMobile Noir. You have to make your own file with AIK (refer to post #14 + #8)
[Galaxy S II Q&A, Help & Troubleshooting] aiSanaul:
but it needs that swipe action when twrp boots before it let us use adb

how to bypass that
[Galaxy S II Q&A, Help & Troubleshooting] Lubo99:
how can you push something to device using ADB when it is not authorized ?
[Galaxy S 4 Q&A, Help & Troubleshooting] smoke92:
guy can anyone help me get back the original wallpaper option that comes in the phone( samsung original wallpapers )in my S4 i9500 black edition

PS : the icon i want to get back is in a red circle in the first image and how my wallpaper option looks now is in the second image. PLZ help
[Galaxy S 4 Q&A, Help & Troubleshooting] AntaresOne:
I see "Backgrounds" in your screenshot, should be that
[Galaxy S 4 Q&A, Help & Troubleshooting] smoke92:
nop thats an app i installed from the play store
[Galaxy S 4 Q&A, Help & Troubleshooting] smoke92:
the phone is not rooted and still on OFW
[Galaxy S 4 Q&A, Help & Troubleshooting] cmzizi:
Its probable an app that you installed that has hidden your com.wallpaper.apk. Try unistalling a recent app (probable one to do with changing wallapares and im sure you will see your wallpaer icon again)
[Galaxy S 4 Q&A, Help & Troubleshooting] smoke92:
tried that did not work any other ideas ? like is there a way to install them ?
[ONE Q&A, Help & Troubleshooting] awaisuk:
Hello,

I have a rooted oneplus, and ive installed adaway on it, but I cant seem to get it to work. When I install it first time, I think it works, but after some time, when the phone is restarted, adaway loses its ability to block ads.

Anyone else having same problem? Do I need any other app beside being rooted and installed adaway?

It has always worked on my past phones, and I cant get it to work on this phone.

Thanks.
[ONE Q&A, Help & Troubleshooting] Heisenberg:
I use Adaway and it works perfectly for me. You don't need any other app.

Transmitted via Bacon
[ONE Q&A, Help & Troubleshooting] nikzDHD:
Working fine with me. Have you checked your root app to ensure permissions for root are not blocked for adaway?
[ONE Q&A, Help & Troubleshooting] zephiK:
If you're using Chrome, are you disabling the Reduce Data Usage? If you haven't disable that and then adaway should work
[ONE Q&A, Help & Troubleshooting] awaisuk:
It is random, sometimes the ads are blocked and sometime they are not. I have given root permission to adaway. Also, restart has nothing to do with it. As my phone was blocking ads, but recently I am seeing ads again with nothing changed...its weird.
[ONE Q&A, Help & Troubleshooting] Silverquark:
AdAway cant block all ads. It just blocks ips of ad servers which it gets from lists. Maybe the ads you are seeing are just not on that list
[ONE Q&A, Help & Troubleshooting] pdcclf:
Need some advise and guidance. I have installed adaway on my OnePlus one, which is running with sultan's cm13 ROM. SuperSU is working fine. However, adaway cannot detect root, no matter SuperSU or superuser. Tried installed busybox to update the applet, but cannot help. Any clue?
[Xperia Z3 Q&A, Help & Troubleshooting] nGet:
Hi all, I am having some issues with my Z3s mobile data switch. If I have mobile data on and then activate my wifi, the mobiles data 3g icon disappears, which I had assumed is normal because wifi trumps data.

After I turn wifi off, the data connection icon does not come back and i have no internet access. When I go to settings to reactivate the data connection, it says it is already on. I have to shut it off/turn it on manually 3 or 4 times before it reconnects... and it seems like it takes a really long time to reconnect too.

Any thoughts?
[Xperia Z3 Q&A, Help & Troubleshooting] danw_oz:
1. Try to reinstall the internet and mms settings under settings, Wireless and networks, Internet Settings.

2. Try under settings, Wireless and networks, mobile networks, prefered network mode, select any of the non LTE/4G options.

3 .If either of those don't work, then try under settings, Wireless and networks, mobile networks, then network operator, then select your network provider from the list, then do each of the previous step 2 then step 1.

If that still doesn't work take the sim back and get it checked out by your provider, or request a new one.
[Xperia Z3 Q&A, Help & Troubleshooting] nGet:
Thanks for this. Apparently it matters in which order you do things with this phone so when I set it up before installing the sim it messed it up. I reset the phone back to factory defaults but this time with the sim card in it and it now works a lot better--though switching between wifi and mobile data is rather slow, at least compared to my One M8.
[Xperia Z3 Q&A, Help & Troubleshooting] danw_oz:
hmm, shouldn't do I haven't noticed that previously, I would be wary of your sim card.
[Xperia Z3 Q&A, Help & Troubleshooting] emwu_:
I have the same issue on my Z3 Compact. Is there no other way than a factory reset? I'm rooted btw
[Xperia Z3 Q&A, Help & Troubleshooting] nOrbX187:
Try turning off Stamina mode

I've had the same or similar issue with the T-Mobile version of the Z3 (D6616). For my phone, I've noticed that it is Stamina mode that is causing this issue. Another post described a similar issue and the way to resolve it was to clear the data and cache on the "Extended Standby mode controller" app/process. Note however that this causes all the stamina settings to be reset such as the apps active in standby. Eventually though this didn't work any more so I decided to turn off Stamina mode altogether. So far, the Wi-Fi to mobile data switching works flawlessly with Stamina mode off.

My feeling it has to do with an app/apps that affect this particular process. I had reset my phone and installed apps "slowly" (install one app, test, install another app, test, etc.) to see which app would cause this though could not pinpoint a particular app. I've experienced this issue with three Xperia Z3's (the first Z3 I had, the replacement Z3 due to a camera button issue, and my wife's Z3) so this has to be a software issue.

Another option is to put the phone in Airplane mode then take it out of airplane mode.
[Xperia Z3 Q&A, Help & Troubleshooting] Prasad:
I have the same issue. Although it arises sporadically, I simply enable and disable Airplane mode when I'm out of wifi range if the phone fails to catch mobile data.
[Xperia Z3 Q&A, Help & Troubleshooting] RockStar2005:
You can leave STAMINA mode on (under Power management), however...... only enable the "Extended Standby" option and of course Activation should be at 100%/Always on. When Wi-Fi is on, you must also have whitelisted 2 specific apps in STAMINA under the "Apps active in standby" list: The text msg app you're using (i.e. Textra, etc) and I would also whitelist one under "All others" entitled "Phone/Messaging Storage". Again, this is only for when you have Wi-Fi on. Keep the other stuff disabled in here. With regards to STAMINA mode.......

First, put Keep Wi-Fi on during sleep to "Only when plugged in" (Settings, Wi-Fi, Advanced). Also, make sure everything else on that page is unchecked/disabled. Turn off STAMINA mode. Go into Settings, Apps, All, Extended Standby Mode Controller, Clear Data AND Cache. Then go to your text app's (Textra, etc) "App info" page (on same Apps "All" screen) and clear ONLY the cache, then close out the app itself (3D button to the right of the virtual Home button, swipe the text app off the screen). Reset. When you come back, follow what I said above, including turning STAMINA mode back on (note the removal of having to leave "queue background data" off.) Make sure that when you turn STAMINA mode on that the pop-up shows up describing it. If it doesn't at any point, then repeat this paragraph's instructions. What I just said here MAY resolve any lingering MMS issues, and also resolve any issues regarding with STAMINA mode not kicking in too. When I did this my phone spit out a few "missed" incoming MMS messages out all at once. And the battery seems to be last longer too.

It seems that MMS messages will def show up if Wi-Fi is on, but it will take longer to show up if screen is off. Maybe 3-5 minutes longer.

RockStar2005
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] qwerty3656:
I've rooted my phone and stalled CWM (v6.0.4.7). I've tried to install 2 different ROM's the first installed but would not boot. the 2nd (cyanogen 10.1.2) would not install (error status 7). Any help would be appreciated.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nfkeskin:
Try install stock rom to your phone. I had same problem once. I tried many things. But when i installed stock rom to my phone it booted normally.

GT-I9300 cihazımdan Tapatalk kullanılarak gönderildi
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] audit13:
Are you wiping cache, dalvik, and data before installing CM11? What bootloader and modem are on your phone?
[Nexus 5 Q&A, Help & Troubleshooting] ivan.panchev:
Hi everyboy!

I updated my Nexus 5 with an OTA update to Android 5.0, but I forgot to wipe the cache partition and now I have a few problems, which I think I can resolve by simply wiping the cache, however once I enter into recovery mode I can't go to the 'wipe cache partition' menu. I long-press the volume up button for 5-6 seconds as advised, but it doesn't lead me to the menu. Any suggestions?

Thanks!
[Nexus 5 Q&A, Help & Troubleshooting] KingUsman:
Flash a custom recovery
[Nexus 5 Q&A, Help & Troubleshooting] aaaaleon:
I believe it's holding power, and then press vol up.
[Galaxy Y GT-S5360 and Duos 6102 Q&A, Help & Troubl] :
Q&A for [ROM] Hyperion 8 GM Final Build - Expansion Pack v.1.2

Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.

Before posting, please use the forum search and read through the discussion thread for [ROM] Hyperion 8 GM Final Build - Expansion Pack v.1.2. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.

Thanks for understanding and for helping to keep XDA neat and tidy! :)
[Galaxy Y GT-S5360 and Duos 6102 Q&A, Help & Troubl] Kardelia:
Your roms can be use on pocket s5300. Just they are have some issues. like power button is not locking. if i click power button, white screen coming, and i click again lock screen coming.

hyperion 7 is perfect for s5300, just google play services not installing.
[Galaxy Y GT-S5360 and Duos 6102 Q&A, Help & Troubl] ogztrk:
Sir

İ want turkish languange pack
[Galaxy Y GT-S5360 and Duos 6102 Q&A, Help & Troubl] wiRUSEK_53:
Bootanimation

Hey, how to change bootanimation?
[Galaxy Y GT-S5360 and Duos 6102 Q&A, Help & Troubl] TheFixItMan:
Change the bootanimation.zip in system/media & set it's permissions to rw-r-r

If it uses the stock boot animation (there is no bootanimation.zip) you need to enable custom bootanimation.zip animations first

Flash this zip to enable custom boot animation

http://xdaforums.com/attachment.php?attachmentid=1344993&d=1348299354
[Galaxy Y GT-S5360 and Duos 6102 Q&A, Help & Troubl] wiRUSEK_53:
Ok, but i can't change permissions "Changing permissions was not succesful. Please note that some file systems do not allow permission changes." Help plz