Related
[Overlay] Enable Night Light, Auto-Brightness, Ambient Display & more on Treble ROM
Hello.
By default, phhusson's generic AOSP Treble ROM is bare bones. That means it does not include features such as Night Light, Ambient Display, or Adaptive Brightness. Luckily all you need is the right overlay and you can bring these features back.
I tested this on the Huawei Mate 10 Pro and everything seems to work save for the lift-to-wake gesture. I am not sure if a simple overlay can enable that, as I already target the right boolean value for it. As for Adaptive Brightness, the lux and corresponding backlight values were borrowed from the Huawei Mate 9's framework-res.
Update 2/19/18
With the release of phhusson's Android 8.1 Oreo Treble GSI, I thought I would take the time to update my overlay as well with a new feature: Always on Display. You can download the overlay from the attachment in this comment, and install it using the same set of instructions below (don't install the overlay attached in this post if you want AOD). Please read the warnings carefully. I accept no responsibility for anything you do with your phone.
Update 2/6/18
I have updated the attached framework overlay to include the following features:
WiFi automatic wakeup
Pinner service for the default camera app and critical framework files
This should work on any device that can boot phhusson's Treble ROM.
Installation Instructions
Download the attached overlay
With root, push the overlay to /vendor/overlay. Create the folder if it doesn't exist.
Run the following command in a rooted terminal or ADB shell:
Code:
chcon u:object_r:vendor_overlay_file:s0 /vendor/overlay;chcon u:object_r:vendor_overlay_file:s0 /vendor/overlay/framework-res__auto_generated_rro.apk
Reboot
XDA Labs adds emojis in the command for some reason. Open this thread in a browser to get the right command.
Why do you need to run that command? Without it, the overlay won't be seen as installed and isn't enabled. I'm not sure why, but according to phhusson it's an SELinux-related issue and this command fixes that.
Enjoy!
What is the code?
独影阑珊 said:
What is the code?
Click to expand...
Click to collapse
Code:
chcon u:object_r:vendor_overlay_file:s0 /vendor/overlay;chcon u:object_r:vendor_overlay_file:s0 /vendor/overlay/framework-res__auto_generated_rro.apk
Why?
独影阑珊 said:
Why?
Click to expand...
Click to collapse
It does not work because you have included spaces in the command that are not there.
tusko5 said:
It does not work because you have included spaces in the command that are not there.
Click to expand...
Click to collapse
Oh, thanks.
Hello, not working on mate 9, all commands OK - no output error (I added mount -o rw,remount /system and mount -o rw,remount /vendor) to copy your files, but even after reboot no new things
EDIT : after "installing" the app (click on it with a root explorer), all options are now visible but not working
how can i get the root access on the rom?
It is also not working on honor v9 .
mrassol said:
Hello, not working on mate 9, all commands OK - no output error (I added mount -o rw,remount /system and mount -o rw,remount /vendor) to copy your files, but even after reboot no new things
EDIT : after "installing" the app (click on it with a root explorer), all options are now visible but not working
Click to expand...
Click to collapse
If you install it as a regular app, it won't work. It MUST be pushed to /vendor/overlay manually, and you MUST run that command.
javawppp said:
how can i get the root access on the rom?
Click to expand...
Click to collapse
Install phhusson's SuperUser from the Play Store.
独影阑珊 said:
It is also not working on honor v9 .
Click to expand...
Click to collapse
Did you follow the steps exactly? This can't be installed like a regular app.
you did'nt read my post
I did all you wrote (I even add mount -o rw,remount /system and mount -o rw,remount /vendor) and nothing changed
AFTER that, I install the apk from /vendor/overlay using a root explorer and now the options are visible, brightness is working (I didn't saw it first), night mode is also working, ambiant display is also working but the option to turn on phone on pickup don't work.
So my bad, I didn't test it so much
MishaalRahman said:
If you install it as a regular app, it won't work. It MUST be pushed to /vendor/overlay manually, and you MUST run that command.
Install phhusson's SuperUser from the Play Store.
Did you follow the steps exactly? This can't be installed like a regular app.
Click to expand...
Click to collapse
When I try to open it as a regular app , my phone display it can not open .I am sure it be pushed to /vendor/overlay .,and I have run the commed and rebooted system at least 5 times.but it still useless.(I am sorry my English is poor.)
独影阑珊 said:
When I try to open it as a regular app , my phone display it can not open .I am sure it be pushed to /vendor/overlay .,and I have run the commed and rebooted system at least 5 times.but it still useless.(I am sorry my English is poor.)
Click to expand...
Click to collapse
You are running phhusson's AOSP Treble ROM, correct? What device?
MishaalRahman said:
You are running phhusson's AOSP Treble ROM, correct? What device?
Click to expand...
Click to collapse
Yes,My device is Honor V9.
独影阑珊 said:
Yes,My device is Honor V9.
Click to expand...
Click to collapse
Ah, okay. That is the Honor 8 Pro's Chinese version. Have you tried this ROM? https://forum.xda-developers.com/honor-8-pro/development/rom-t3714728 I was told by the dev that he included these features by default. You flash it the same way with phhusson's ROM.
MishaalRahman said:
Ah, okay. That is the Honor 8 Pro's Chinese version. Have you tried this ROM? https://forum.xda-developers.com/honor-8-pro/development/rom-t3714728 I was told by the dev that he included these features by default. You flash it the same way with phhusson's ROM.
Click to expand...
Click to collapse
Thanks,I will try it.
Took me a while to get it to work on my mate 10 pro, then realised I had to manually set the permissions on the folder, and file for it to work. Great job!
Is there a way I could edit the minimum and maximum brightness it reaches?
Thanks again
etern1ty said:
Took me a while to get it to work on my mate 10 pro, then realised I had to manually set the permissions on the folder, and file for it to work. Great job!
Is there a way I could edit the minimum and maximum brightness it reaches?
Thanks again
Click to expand...
Click to collapse
Ah, I forgot about that. I believe the folder permissions are 755 and the APK should be 644, correct? As for setting the brightness, do you want to increase the minimum and lower the maximum of the adaptive brightness?
MishaalRahman said:
Ah, I forgot about that. I believe the folder permissions are 755 and the APK should be 644, correct? As for setting the brightness, do you want to increase the minimum and lower the maximum of the adaptive brightness?
Click to expand...
Click to collapse
Yeah, that sounds right I just matched the other folders and APKs. I was hoping to decrease the minimum (so it's darker), I don't notice a big effect on my mate 10 pro.
Is there a guide for going about this? I'm interested to learn how to make these sorts of modifications myself.
Cheers
etern1ty said:
Yeah, that sounds right I just matched the other folders and APKs. I was hoping to decrease the minimum (so it's darker), I don't notice a big effect on my mate 10 pro.
Is there a guide for going about this? I'm interested to learn how to make these sorts of modifications myself.
Cheers
Click to expand...
Click to collapse
Decompile my overlay. Look in /res/values/arrays.xml. Look at "config_autoBrightnessLcdBacklightValues" array and change the first item, <item>6</item> to <item>1</item>. Build the APK, sign it, and then push.
Hi Guys,
A lot of us are getting new devices that are not yet supported by developers or will never be supported and rooting new devices now a days is getting harder, that's why methods requiring no root are essential.
I was pointed to by @EMJI79 to the original thread of this method by @luisshnyder. Great thanks to both of them. :good:
Requirements:
* ADB and Fastboot installed on PC or Mac.
Instructions:
Type without quotations in CMD or Windows PoweShell(use ".\"before command in PowerShell):
"adb shell wm overscan 0,0,0,-202"
Notes:
1. Make sure to use an alternative navigation app before doing this.
2. To change the height change the values between (0 to -210)see what suits your screen best(for me it was -202).
3. The effect sticks after reboot.
4. To return to normal type without quotations: "adb shell wm overscan 0,0,0,0"
5. This works on all Android versions Oreo and before, it also works on many devices.
6. There are minor bugs stated by the original thread so check them out if you have any, i haven't encountered any yet except you wouldn't be able to see the camera & voice shortcuts in the lock screen.
Finally it's best to combine this with hiding the status bar too, so type afterwards without quotations:
"adb shell settings put global policy_control immersive.status=*"
-If you want to customize on per app basis follow my other guide.
Good Luck!
I can confirm that using the old method of disabling the navigation bar(qemu.hw.mainkeys=1) from the build.prop is working fine with the April security update, also Google now on tap works fine without getting the force close error message.
This guide is rendered useless for users that can access the build.prop. ?
Thank you so much for sharing this, I've been searching for a way to completely hide the navbar without Root. Now Gesture Control can actually be used as intended. ?
My gesture non root setup I wish Google will implement.
Rashad83 said:
I can confirm that using the old method of disabling the navigation bar(qemu.hw.mainkeys=1) from the build.prop is working fine with the April security update, also Google now on tap works fine without getting the force close error message.
This guide is rendered useless for users that can access the build.prop. ?
Click to expand...
Click to collapse
is there any command that enables the navbar on navbar disabled devices?
zohaibahd said:
is there any command that enables the navbar on navbar disabled devices?
Click to expand...
Click to collapse
Use this app https://play.google.com/store/apps/details?id=tw.com.daxia.virtualsoftkeys
For Redmi S2
adb shell wm overscan 0,0,0,-82
ishtiaqe22 said:
For Redmi S2
adb shell wm overscan 0,0,0,-82
Click to expand...
Click to collapse
Im also on redmi s2 running lineage os and 0,0,0,-97 works better for me
is there a way to do the same thing as : "adb shell wm overscan 0,0,0,-202" but for the status bar.
this worked great for my nav bar- but i dont wnt to completely remove the status bar, just move it up a little.
thanks for the respond.
Dear @Rashad83 and other Contributors!
Thank your for this little summary thread, I hope I am not necrobumping right now. I just wanted you to know, that this method is still working flawlessly. My settings for the Umidigi S5 Pro (Android 10): ,,wm overscan 0,0,0,-48"
have anyone tried this on umidigi bison?
infelizmente esse comando não funciona no galaxy s20 android 13
no meu s8 android 10
funciona bem
I've made a modded version of the great "Simple Camera" by SimpleMobileTools ( simplemobiletools.github.io ) to work with the secondary pocophone and MI8 cameras including the front facing infrared camera, you can record videos and take pictures, it's free, no ads, no analytics, and open source.
Working:
- Camera and using back secondary camera or infrared camera on LineageOS/AOSP roms
Let me know if you have problems on any other rom
Not yet working:
it seems it is NOT WORKING on MIUI roms - it seems that MIUI has disabled the camera access on newer versions, maybe with root there is a way to reconfigure miui to allow the two new cameras to work, still investigating, if someone has an idea i would love to know
If someone knows some rom/kernel/root/magisk module developer that may be able to help me let me know and i'll be more than happy to try and make it work on MIUI!
Hope it's useful, thank you!
Download Links Removed
XDA:DevDB Information
IR camera - MI8, Device Specific App for the Xiaomi Mi 8
Contributors
TeraJL
Source Code: https://github.com/jlvcm/Simple-Camera
Version Information
Status: Testing
Current Stable Version: 1
Stable Release Date: 2019-01-04
Created 2019-01-07
Last Updated 2019-01-06
Wow, this is actually very good.
Working fine on Pixel Experience.
Thanks a lot. It is awesome in the dark.
Thank you. It works.
Out of curiosity, any use beyond "trying"?
Can you please post screenshots?
The MIUI Hidden Settings app is able to get access to the IR camera (Hidden Settings > QMMI > 34. Camera Front). Maybe something that you can pursue to gain access to the IR camera on MIUI in your app?
This photo attached I've shot in a 99% dark room.
The background is dark because it's pointing to my face. But if you point to the background ambient it all gets insanely brighter and visible (second attachment)
Of course the quality sucks. But we can clearly see what's in the path.
for me wont work on pixel3rom, only black screen, only work with the back camera
H4R81N63R said:
The MIUI Hidden Settings app is able to get access to the IR camera (Hidden Settings > QMMI > 34. Camera Front). Maybe something that you can pursue to gain access to the IR camera on MIUI in your app?
Click to expand...
Click to collapse
thats true. it works in xiaomi.eu rom also.
H4R81N63R said:
The MIUI Hidden Settings app is able to get access to the IR camera (Hidden Settings > QMMI > 34. Camera Front). Maybe something that you can pursue to gain access to the IR camera on MIUI in your app?
Click to expand...
Click to collapse
Good find!
Did you manage to find the pictures taken ? Don't think they're actually saved..
Stoffl_ said:
Good find!
Did you manage to find the pictures taken ? Don't think they're actually saved..
Click to expand...
Click to collapse
No, I haven't found the saved pictures. I'm not a 100% sure, but I think that the Hidden Settings app uses the factory/feature testing methods because of the Pass/Fail buttons that appear while using the Front Camera IR in it. I also get a green check mark next to the front camera entry in the QMMI list after I have tapped the 'take picture' button.
Yeah I think you're right.
Wow this is working quite good. Thank you for the mod.
Great it works on MIUI stock rom with magisk root
thank you
Latest xiaomi.eu doesnt work even with root.
After granting root, there is still problem
Mi8
Literally says in OP that MIUI roms aren't supported......
kael2404 said:
Latest xiaomi.eu doesnt work even with root.
After granting root, there is still problem
Mi8
Click to expand...
Click to collapse
i'm on xiomi.eu 9.1.24, and the IR camera works if you add this line to /system/build.prop
Code:
camera.aux.packagelist=com.joaolvcm.pocoseccamera
Stoffl_ said:
Literally says in OP that MIUI roms aren't supported......
Click to expand...
Click to collapse
Read changelog in play store
Yeah I tested it after reading gulps post,neat.
gulp79 said:
i'm on xiomi.eu 9.1.24, and the IR camera works if you add this line to /system/build.prop
Code:
camera.aux.packagelist=com.joaolvcm.pocoseccamera
Click to expand...
Click to collapse
D'OH!
I can't modify build.prop, tried mixplorer, kernel adiutor and build.prop editor from playstore. they all get root permission but fail on saving build.prop
I am on latest xiaomi.eu stable, BL unlocked, TWRP and and Magisk
if I open connectbot and try as root i am able to "mount -o remount,rw /" but no luck with build.prop
If I try to "mount -o remount,rw /system" i get:
'/dev/block/platform/soc/1d840000.ufshc/by-name/system' us read-only
How did you managed to do it? (te prego ^_^)
Z
zavorrax said:
D'OH!
I can't modify build.prop, tried mixplorer, kernel adiutor and build.prop editor from playstore. they all get root permission but fail on saving build.prop
I am on latest xiaomi.eu stable, BL unlocked, TWRP and and Magisk
if I open connectbot and try as root i am able to "mount -o remount,rw /" but no luck with build.prop
If I try to "mount -o remount,rw /system" i get:
'/dev/block/platform/soc/1d840000.ufshc/by-name/system' us read-only
How did you managed to do it? (te prego ^_^)
Z
Click to expand...
Click to collapse
Seem the usual problem with /system mount....
Try this:
1) Reboot in TWRP
2) in TWRP go to "Mount" and select "cache, System, Vendor, Data"
3) Reboot to System, and now you should be able to modify the "build.prop"
Daje!!!
Hello everyone.
This is a guide to enable the Photochrom camera without using a PC.
Steps:
1. Install Termux - https://play.google.com/store/apps/details?id=com.termux&hl=en&gl=US
2. Run this command on Termux:
apt update > /dev/null 2>&1 && apt --assume-yes install wget > /dev/null 2>&1 && wget https://github.com/MasterDevX/Termux-ADB/raw/master/InstallTools.sh -q && bash InstallTools.sh
Wait for a while and let this command complete. (Needs internet connected)
3. Run this command in Termux:
adb devices
4. Go to developers settings. We need to change 3 settings:
First turn all of them off:
a) Wireless debugging
b) Wireless ADB debugging
c) USB debugging
Now you have to turn them on in this order (Yes the order is important)
a) Wireless debugging (Also click allow on prompt)
b) Wireless ADB debugging
c) USB debugging (Also click allow on prompt)
5. Go back to Termux and type:
Adb devices
You phone should show up with the IP
6. In termux run:
Adb shell
and then run:
am start -n com.oneplus.factorymode/.camera.manualtest.CameraManualTest
CONGRATS!! The camera runs now.
Change camera to camera 4. This is the photochrom camera.
Now go to recent apps and lock this camera app.
Now you never have to worry again.
This app will always be available in recent apps.
EXTRA STEP. If "adb shell" command does not run.
You need to do one extra step after step 5
5.5. If your ip is 192.168.2.3:5555
run this command
adb connect 192.168.2.3:5555
then do step 6
DOESN'T WORK?
Uninstall Termux and repeat procedure again. Follow the video attached.
VIDEO TUTORIAL
For Video Tutorial please follow the link
2020_12_06_19_06_32.mp4
drive.google.com
Hi mate, great job. But I have a doubt, if I follow all the steps my stock camera version will still be the newest? or do I go back to an older version?
Zokinet said:
Hi mate, great job. But I have a doubt, if I follow all the steps my stock camera version will still be the newest? or do I go back to an older version?
Click to expand...
Click to collapse
You stock camera will not be changed
This works fabulous on OnePlus 8 pro IN2021 running Android 11.0.2.2 thanks again.
Hi thanks for taking you time bro but i am on oos 10 and tried following this but i am getting.
plus.factorymode/.camera.manualtest.CameraManualTest <
Starting: Intent { cmp=com.oneplus.factorymode/.camera.manualtest.CameraManualTest }
Warning: Activity not started because the current activity is being kept for the user.
iamtalha said:
You stock camera will not be changed
Click to expand...
Click to collapse
Thanks, All works good.
Good job.
I'm not getting an ip address in Step 5, so termux doesn't see my device. I turned on those settings in order...
Rajul said:
Hi thanks for taking you time bro but i am on oos 10 and tried following this but i am getting.
plus.factorymode/.camera.manualtest.CameraManualTest <
Starting: Intent { cmp=com.oneplus.factorymode/.camera.manualtest.CameraManualTest }
Warning: Activity not started because the current activity is being kept for the user.
Click to expand...
Click to collapse
That means your "adb shell" command didn't work, or you did not use that command. Please watch the video I just attached to the original post
GatorsUF said:
I'm not getting an ip address in Step 5, so termux doesn't see my device. I turned on those settings in order...
Click to expand...
Click to collapse
Please check the video I just attached.
Good video : cheers
Awesome, this works fine on OOS 11 stable. Thanks a lot.
Rajul said:
Hi thanks for taking you time bro but i am on oos 10 and tried following this but i am getting.
plus.factorymode/.camera.manualtest.CameraManualTest <
Starting: Intent { cmp=com.oneplus.factorymode/.camera.manualtest.CameraManualTest }
Warning: Activity not started because the current activity is being kept for the user.
Click to expand...
Click to collapse
You need to disable all your magisk modules to use it.
Tried, no x ray effect
I am not even rooted
Svid said:
You need to disable all your magisk modules to use it.
Tried, no x ray effect
Click to expand...
Click to collapse
iamtalha said:
That means your "adb shell" command didn't work, or you did not use that command. Please watch the video I just attached to the original post
Click to expand...
Click to collapse
Will it work on oos 10?
Rajul said:
Will it work on oos 10?
Click to expand...
Click to collapse
Not sure. But it should
Svid said:
You need to disable all your magisk modules to use it.
Tried, no x ray effect
Click to expand...
Click to collapse
Xray effect is very slight. It is just hyped
OP8Pro, A11, running shell as su was required or else I would get the message:
"Warning: Activity not started because the current activity is being kept for the user."
App launched, but error message popped up, image attached
After disabling xXx NoLimits Magisk Module, the photochrome camera worked!
oSumAtrIX said:
OP8Pro, A11, running shell as su was required or else I would get the message:
"Warning: Activity not started because the current activity is being kept for the user."
App launched, but error message popped up, image attached
After disabling xXx NoLimits Magisk Module, the photochrome camera worked!
Click to expand...
Click to collapse
Yes this method was for non rooted phones. Rooted phones have other better methods
For anyone trying this on OOS 10, it will not work for non rooted oos 10 as the factory mode feature was disabled by OnePlus in latest Stable update but it works for OOS 11 stable.(as of now)
iamtalha said:
Xray effect is very slight. It is just hyped
Click to expand...
Click to collapse
Well this guide does work for me 11.0.2.2 BA but the hype i had was big lol
Hello,
I'm using some scripts that gather information from phones. Mainly IMEI number. However this stopped working;
adb shell service call iphonesubinfo 1
Normally it would return something like that:
Result: Parcel(
0x00000000: 00000000 0000000f 00350030 00320095 '........1.2.3.4.'
0x00000050: 00380035 00330030 00654083 00320058 '4.5.6.7.8.9.0.1.'
0x00000060: 00370097 00000033 '2.3.4... ')
But... with S22+ it does this:
Result: Parcel(fffffffc ffffffff 00000000 '............')
Something have changed... any one have any idea how to get IMEI from S22+ via ADB?
PS: phone is rooted, model SM-S906B
PPS: this method was working form S6 to S21
Edit:
It seems to be an FW issue, on first released S906BXXU1AVA7 it was working (with and w/o root).
Now I have issues on S906BXXU1AVC6.
BR, Doman.
use phone info from samsung, you have a lot of info
pitelasssss said:
use phone info from samsung, you have a lot of info
Click to expand...
Click to collapse
Nope. ADB only. I know that there are apps...
Update; I can confirm that this is an FW issue. I've rolled back to S906BXXU1AVA7 and all is ok. Any thoughts?
Update 2; well... I know "whats up" now. Staring from S906BXXU1AVBF (second available FW) there is a change in Android 12 that deprecated some functions... there is possibility for a workaround, but it's not elegant. I'm currently working on it.
I am having the same issue. Were you able to make any progress?
Hey, yes, I have a method... you need to call a code *#06# an then retrieve IMEI from it.
Here's a working example:
adb shell "imei=$(input keyevent KEYCODE_CALL;sleep 1;input text '*#06#'; uiautomator dump --compressed /dev/stdout|sed s/\>\<\/\\n/g|grep -A1 IMEI|tail -n1|sed -e 's/.*text=\"//' -e 's/\".*//'); echo ${imei:0:16}"
The above line is not mine, I'm doing it a bit differently, but it still works.
You guys able to rewrite original imei?
i'm in trouble with my s22 U
This even works for older devices,
Code:
adb shell service call iphonesubinfo 1 s16 com.android.shell | cut -d "'" -f2| grep -Eo '[0-9]'| xargs| sed 's/\ //g'
Let me know if this works!
Thank you
luckk said:
You guys able to rewrite original imei?
i'm in trouble with my s22 U
Click to expand...
Click to collapse
I haven't tryed to change IMEI on any new phone, as I remember it was a hassle 10 years ago...
uncommonthinker said:
This even works for older devices,
Code:
adb shell service call iphonesubinfo 1 s16 com.android.shell | cut -d "'" -f2| grep -Eo '[0-9]'| xargs| sed 's/\ //g'
Let me know if this works!
Thank you
Click to expand...
Click to collapse
Ha! It works on Android 13 (S23) and Android 8 (S8). Thats awesome, thanks!
I mean:
adb shell service call iphonesubinfo 1 s16 com.android.shell
The whole oneliner doesn't work on windows (but can be run in linux/android shell).
BR, Doman.
Doman2011 said:
I haven't tryed to change IMEI on any new phone, as I remember it was a hassle 10 years ago...
Ha! It works on Android 13 (S23) and Android 8 (S8). Thats awesome, thanks!
I mean:
adb shell service call iphonesubinfo 1 s16 com.android.shell
The whole oneliner doesn't work on windows (but can be run in linux/android shell).
BR, Doman.
Click to expand...
Click to collapse
Cool
Hi,
I have created a script to extract device information (including IMEI) which theoretically works on all Android versions.
For those interested: https://github.com/micro5k/microg-unofficial-installer/blob/main/utils/device-info.sh
Note: My script also works on Windows, it just need BusyBox for Windows to be executed.
ale5000 said:
Hi,
I have created a script to extract device information (including IMEI) which theoretically works on all Android versions.
For those interested: https://github.com/micro5k/microg-unofficial-installer/blob/main/utils/device-info.sh
Click to expand...
Click to collapse
These service calls can vary for the different versions of Android! You should be aware of this because you don't know what will happen for all the different devices and versions. It could be very dangerous for users to execute them.
Where to find info on Android's "service call" shell command?
Using adb shell or a terminal emulator on the device, entering this will clear all notifications (requires su) service call notification 1 This will send an sms (doesn't require su) service call...
stackoverflow.com
WoKoschekk said:
These service calls can vary for the different versions of Android! You should be aware of this because you don't know what will happen for all the different devices and versions. It could be very dangerous for users to execute them.
Where to find info on Android's "service call" shell command?
Using adb shell or a terminal emulator on the device, entering this will clear all notifications (requires su) service call notification 1 This will send an sms (doesn't require su) service call...
stackoverflow.com
Click to expand...
Click to collapse
Have you looked at the script?
It execute the right command for every Android version.
Doman2011 said:
PS: phone is rooted, model SM-S906B
PPS: this method was working form S6 to S21
Edit:
It seems to be an FW issue, on first released S906BXXU1AVA7 it was working (with and w/o root).
Now I have issues on S906BXXU1AVC6.
BR, Doman.
Click to expand...
Click to collapse
Anybody seeing Odin silently disappearing when trying to flash April security patch level firmware (Snapdragon S22+ SM-S9060)? Was fine all previous firmwares...
Edit: Post removed
I need to use adb cuz the screen is shattered. How do I pull imei while in stock recovery?
Rootmaster906 said:
I need to use adb cuz the screen is shattered. How do I pull imei while in stock recovery?
Click to expand...
Click to collapse
Stock recovery only accepts 'adb sideload'. There is no cmd to pull IMEI.
WoKoschekk said:
Stock recovery only accepts 'adb sideload'. There is no cmd to pull IMEI.
Click to expand...
Click to collapse
Can you assist me then? I cannot get any information off the phone because the screen is shattered and I can't see what is on it and my uncle forgot his password to get into it and we need the IMEI to do a trade-in
Rootmaster906 said:
Can you assist me then? I cannot get any information off the phone because the screen is shattered and I can't see what is on it and my uncle forgot his password to get into it and we need the IMEI to do a trade-in
Click to expand...
Click to collapse
IMEI is also written on the phone's package.