Hi guys, any info on flashing aquaris to daily images??? How to and what images and recovery to use? Thanx in advance.
Best regards.
Sent from my awesome Ubuntu Touch device using the Forum Browser app
cybermm said:
Hi guys, any info on flashing aquaris to daily images??? How to and what images and recovery to use? Thanx in advance.
Best regards.
Sent from my awesome Ubuntu Touch device using the Forum Browser app
Click to expand...
Click to collapse
I followed this tutorial //developer.ubuntu.com/en/start/ubuntu-for-devices/installing-ubuntu-for-devices/ where it says "Upgrade manually". For daily builts use the ubuntu-touch/devel channel.
Thanx a lot man. Great find.
Sent from my awesome Ubuntu Touch BQ using the Forum Browser app
Thanks guys and any way to go back to the official channel after a trial on that daily builds?
The channel for daily builds is ubuntu-touch/devel-proposed. The builds from "ubuntu-touch/devel" are more than 4 months old!!!
To get back, do a simple
Code:
ubuntu-device-flash touch --channel=ubuntu-touch/stable
I'm flashing my BQ device with devel-proposed. Let you know how it is
Edit: After 1 day, what I can say.
System is faster that with the dedicated build for the BQ.
Notifications envelope is no more green when a notifications are received but only white (grey if nothing comes).
I don't have the first scope summarizing weather, calendar etc ...
So, everything works perfectly. I will stay with that channel a little bit longer .
Just a question, @nikwen :as you have a nexus4, does your nexus 4 take blurred photo? Because my BQ is disastrous for the focus. I don't know if it is coming from the software or the hardware.
mousse04 said:
I'm flashing my BQ device with devel-proposed. Let you know how it is
Edit: After 1 day, what I can say.
System is faster that with the dedicated build for the BQ.
Notifications envelope is no more green when a notifications are received but only white (grey if nothing comes).
I don't have the first scope summarizing weather, calendar etc ...
So, everything works perfectly. I will stay with that channel a little bit longer .
Just a question, @nikwen :as you have a nexus4, does your nexus 4 take blurred photo? Because my BQ is disastrous for the focus. I don't know if it is coming from the software or the hardware.
Click to expand...
Click to collapse
Yes, the enhancements on vivid are really nice. In the near future, they will start basing the stable builds on that channel but by then we'll have vivid+1.
It's still more buggy than the stable channel though. (Surprise! )
Regarding your question: I'm not happy with the camera focus either. Seems to be a software issue.
In fact, I found a bug report on Launchpad. If that hasn't been filed by you, it would be nice if you could select that it affects you to increase the developers' awareness. You can log in with the Ubuntu One account you use on your phone.
About focus problem : voted
I didn't get any bugs yet except that GMAIL notifications doesn't work at all now . I thought, your fix was included in that build .
another question, I received an update this morning but when I go to the ChangeLog page, I can't see anything (http://people.canonical.com/~lzemczak/landing-team/ubuntu/vivid/).
When an official changelog occurs ?
@ nikwen : do you know how to go in root mode? I enabled dev mode with a password and then try to add a repository by using sudo apt-add-repository ... but the command finishes with cannot touch /etc/apt/trusted.gpg.d .... read-only file system
Thanks a lot
mousse04 said:
About focus problem : voted
I didn't get any bugs yet except that GMAIL notifications doesn't work at all now . I thought, your fix was included in that build .
another question, I received an update this morning but when I go to the ChangeLog page, I can't see anything (http://people.canonical.com/~lzemczak/landing-team/ubuntu/vivid/).
When an official changelog occurs ?
Click to expand...
Click to collapse
The changelog appears in the evening when the landing team posts an email about the day's progress on the Ubuntu phone mailing list.
However, my fix has finally made its way into devel-proposed image 172! You're just going to run into the following issue: https://bugs.launchpad.net/ubuntu/+source/account-polld/+bug/1434521 I'm working on that one though.
mousse04 said:
@ nikwen : do you know how to go in root mode? I enabled dev mode with a password and then try to add a repository by using sudo apt-add-repository ... but the command finishes with cannot touch /etc/apt/trusted.gpg.d .... read-only file system
Thanks a lot
Click to expand...
Click to collapse
Yes, apt requires a writable image, which comes with some caveats though. More on that topic at https://developer.ubuntu.com/en/start/ubuntu-for-devices/installing-ubuntu-for-devices/. (Spoiler: You'll lose OTA updates.)
Thakns @nikwen, you are the best .
But according to the article you sent me, just doing "rm -rf /userdata/.writable_image" should be enough if Ï want to go back to OTA updates. Without re-installing all the system right ?
another thing, how to be up to date on core-apps in that case ?
mousse04 said:
Thakns @nikwen, you are the best .
But according to the article you sent me, just doing "rm -rf /userdata/.writable_image" should be enough if Ï want to go back to OTA updates. Without re-installing all the system right ?
another thing, how to be up to date on core-apps in that case ?
Click to expand...
Click to collapse
Well, contrary to what the documentation says you will still be offered OTA updates, even in writable mode. However, installing them might break your installation so it's not recommended. Removing that single file with the command you posted, will revert back to non-writable mode but it won't undo the changes you did in writable mode.
Regarding that, the article says the following:
To restore the normally read-write protected system area to a pristine state that does not include any changes you made while in read-write mode by installing the Ubuntu system:
Code:
$ ubuntu-device-flash touch --channel=CHANNEL
Click to expand...
Click to collapse
That's the way to go (in addition to deleting the file indicating that you're in rw mode).
EDIT: Forgot to mention that in contrast to system apps (camera, dialer, etc.) the core apps (e.g. filemanager, terminal and calculator) receive updates through the store and app updates are always safe to install.
adb error:closed
I tried this but i am not possible to connect to my device i get this:
Code:
% adb shell
error: closed
I running adb in version
Code:
% adb -version :(
Android Debug Bridge version 1.0.31
And my ubuntu is
Code:
% lsb_release -r :(
Release: 14.10
And adb device shows
Code:
% adb devices :(
List of devices attached
JU001259 device
adb in debug shows me
Code:
% ADB_TRACE=1 adb shell
adb.c::main():Handling commandline()
commandline.c::adb_commandline():starting interactive shell
adb_client.c::_adb_connect():_adb_connect: host:version
transport.c::writex():writex: fd=3 len=4: 30303063 000c
transport.c::writex():writex: fd=3 len=12: 686f73743a76657273696f6e host:version
transport.c::readx():readx: fd=3 wanted=4
transport.c::readx():readx: fd=3 wanted=4 got=4
4f4b4159 OKAY
adb_client.c::_adb_connect():_adb_connect: return fd 3
adb_client.c::adb_connect():adb_connect: service shell:
transport.c::readx():readx: fd=3 wanted=4
transport.c::readx():readx: fd=3 wanted=4 got=4
30303034 0004
transport.c::readx():readx: fd=3 wanted=4
transport.c::readx():readx: fd=3 wanted=4 got=4
30303166 001f
adb_client.c::_adb_connect():_adb_connect: shell:
transport.c::writex():writex: fd=3 len=4: 30303132 0012
transport.c::writex():writex: fd=3 len=18: 686f73743a7472616e73706f72742d61 host:transport-a
adb_client.c::switch_socket_transport():Switch transport in progress
transport.c::readx():readx: fd=3 wanted=4
transport.c::readx():readx: fd=3 wanted=4 got=4
4f4b4159 OKAY
adb_client.c::switch_socket_transport():Switch transport success
transport.c::writex():writex: fd=3 len=4: 30303036 0006
transport.c::writex():writex: fd=3 len=6: 7368656c6c3a shell:
transport.c::readx():readx: fd=3 wanted=4
transport.c::readx():readx: fd=3 wanted=4 got=4
4641494c FAIL
transport.c::readx():readx: fd=3 wanted=4
transport.c::readx():readx: fd=3 wanted=4 got=4
30303036 0006
transport.c::readx():readx: fd=3 wanted=6
transport.c::readx():readx: fd=3 wanted=6 got=6
636c6f736564 closed
adb_client.c::adb_connect():adb_connect: return fd -1
error: closed
And yes i added my hex code to ~/.android/adb_usb.ini
So has anyone the same error or a solution?
nikwen said:
Well, contrary to what the documentation says you will still be offered OTA updates, even in writable mode. However, installing them might break your installation so it's not recommended. Removing that single file with the command you posted, will revert back to non-writable mode but it won't undo the changes you did in writable mode.
Regarding that, the article says the following:
That's the way to go (in addition to deleting the file indicating that you're in rw mode).
EDIT: Forgot to mention that in contrast to system apps (camera, dialer, etc.) the core apps (e.g. filemanager, terminal and calculator) receive updates through the store and app updates are always safe to install.
Click to expand...
Click to collapse
Actually , my idea was :
Make the OTA update.
Move to RW file system
Update the coreapps
Remove the RW file system
Make the OTA Update etc ....
In RW, I only want to get latest core-apps
@nodude Have you enabled developer mode in the system settings? That's necessary to make adb work.
@mousse04 No, that won't work. The part which makes trouble in RW mode is that you modify the system partition by installing packages using apt-get. If you leave RW mode, these changes are still there so nothing has changed.
However, you really don't need RW mode to update the core apps. They are all in the store.
Sent from my awesome Ubuntu Touch device using the Forum Browser app
@nikwen : yes but currently there is a new version of calendar to fix the google sync issue. And it is not in the store yet, only available via : citrain device-upgrade 21 [DEVICE PASSWORD] ubuntu
available only in RW mode
mousse04 said:
@nikwen : yes but currently there is a new version of calendar to fix the google sync issue. And it is not in the store yet, only available via : citrain device-upgrade 21 [DEVICE PASSWORD] ubuntu
available only in RW mode
Click to expand...
Click to collapse
Well, that's no change in the core apps. That's actually a syncevolution change: http://people.canonical.com/~platform/citrain_dashboard/#?distro=ubuntu&q=ubuntu/landing-021
Sadly, the only way to go if you want the software is the following: Switch to RW mode, install the software from the silo, wait for it to arrive in the official builds and reflash your device (keeping your data).
Hi @nikwen, as the OTA is coming, what do you think : is it better to go with this new OTA, or staying with developper vivid channel ?
My question is because when I switched to the developper channel, many bug were fixed (battery consumption notably). But according to the changelog, this new OTA have many bug fixes also.
So what does vivid bring compare to current OTA release?
@mousse04 OTA-3 was a bugfix release only. It didn't come with any new features but improved battery consumption.
It's up to you whether you switch back or not.
Sent from my awesome Ubuntu Touch device using the Forum Browser app
Related
I am considering flashing my main phone, and I cannot find an answer to this question:
Is the OS update functionality now working? i.e. if I install "current" now and run the updater next week, will I get the newer version? I don't want to switch until I no longer have to flash to get the newest version.
Thank you!
I installed Ubuntu touch on my nexus 4 last week , but I did the full install, not the way you flash a ROM normally , via Ubuntu on my computer.
If you ask me, is it functional, well yes you can make phone calls and send text message but it's very buggy, sometimes it freeze and you need to power off the phone manually and restart it.
It's totally better than the version I flashed 5 months ago but it's not something I would use as daily driver, except if your a die hard Ubuntu fan.
In back on android for your information.
My advice is wait for the 1.0 public version to become available.
Sent from my Nexus 7 using xda app-developers app
jonathan,
I think you misread the question...
I'm on an ubuntu-system build dated Sept. 20 2013 (near as I can determine).
I can see that there are OTA Updates available (the size of available update keeps increasing when checked), but have not yet had success getting the phone to update either via WiFi or 3G, automatically or manually, with the update manager app or via system settings (2 areas there purport to allow updating).
Soon (hopefully over the weekend) I will manually install a newer version of ubuntu-system via my Ubuntu Box.
I'll check back in and let you know...
For the record: I flashed the newest version. I quickly learned that you needed to do some cl work to get the clock set correctly. Unfortunately, given the recent switch to a read-only file system by default, I couldn't get the fixes to work. I reverted back to the legacy non-r/o version but found it way too buggy to use as a daily driver.
Some other things I noticed: gps doesn't really work (or I couldn't get it to) with google maps and you can't send multi-recipient sms. I could put up with living in UTC time for a few weeks, but those two things are deal breakers for me. Going to keep my eyes on the status of the project.
Thanks to a terminal command tip from eagleofdeath13 I found the workaround for correcting the timezone under the read only file system.
RumoredNow said:
That's the most helpful thing I've seen since ubuntu-system emerged... Thanks, I was ready to revert to cdimage-touch, but now I won't have to. :highfive:
So following the example, I opened terminal on my GNex (latest ubuntu-system --channel saucy --no-backup) and typed in
Code:
sudo mount /dev/loop0/ -o remount, rw
after entering the password for sudo, I next typed
Code:
sudo dpkg-reconfigure tzdata
and it brought up the timezone applet.
I was allowed to write my current time to the system!!!!!
Click to expand...
Click to collapse
The Read/Write command lasts only the one terminal session, but is very useful.
GPS and maps I have no cures for.
I have an Amazon Kindle Fire 7 inch 5th generation tablet running the unofficial build of Cyanogenmod 12.1 for this device (main thread). I've got root, I'm running without GApps, and my setup is working great. The only thing I have yet to resolve is that I cannot spoof my MAC address. If I try to do so with something like:
Code:
su
busybox ifconfig wlan0 down
busybox ifconfig wlan0 hw ether 00:11:22:33:44:55
busybox ifconfig wlan0 up
it will fail on "busybox ifconfig wlan0 hw ether 00:11:22:33:44:55" with the message:
Code:
ifconfig: SIOCSIFHWADDR: Operation not supported on transport endpoint
I also tried two similar approaches:
Code:
su
busybox ifconfig wlan0 down && macchanger -r wlan0
fails with
Code:
[ERROR] Could not change MAC: interface up or insufficient permissions: Operation not supported on transport endpoint
while
Code:
su
ip link set wlan0 address 00:11:22:33:44:55
fails with:
Code:
RTNETLINK answers: Operation not supported on transport endpoint
From the googling I have done, it seems that this may be due to a limitation of the hardware, kernel or wifi drivers? Hopefully that doesn't mean there is nothing I can do and nothing more to try. Are there perhaps other methods that would bypass this problem?
For a bit of additional info, the application "Dalvik Explorer" shows under device details "Hardware: MT8127", which I hope is a useful piece of information to someone with more technical expertise than me. If it is a driver issue, are there perhaps newer drivers for that I could manually load somehow? If it is a kernel issue, is there anything I can do to modify the kernel (not something I have the slightest bit of experience with, but I'll be damned if I can't try). Any guidance or ideas would be extremely helpful.
Spoofing your MAC ID would require a kernel mod.
Our bootloader is locked so this is not achievable right now.
ggow said:
Spoofing your MAC ID would require a kernel mod.
Our bootloader is locked so this is not achievable right now.
Click to expand...
Click to collapse
Aw.
Well, thanks for letting me know. And thank you for bringing Cyanogenmod to this device, I have been enjoying it greatly!
ggow said:
Spoofing your MAC ID would require a kernel mod.
Our bootloader is locked so this is not achievable right now.
Click to expand...
Click to collapse
cyanogen_aw_yeah said:
Aw.
Well, thanks for letting me know. And thank you for bringing Cyanogenmod to this device, I have been enjoying it greatly!
Click to expand...
Click to collapse
Unless Amazon has deprecated this (e.g. with a kernel update?),
on my 2015 Fire + CM12.1 (per OP's link) I'm able to spoof my MAC address using the idme command.
Code:
su -c idme mac_addr 38aa3c123456
su -c idme print mac_addr # check to see that it set it
Then restart the device. After rebooting, go to CM Wi-Fi settings -> Advanced and see if it worked. It seems certain OUIs (first half) are rejected by the OS.
I found this while poking through the kernel code earlier this year. But per @ggow's comment, maybe they've nixed it since then.
Working On FireHD 10 2017
jrodat said:
Unless Amazon has deprecated this (e.g. with a kernel update?),
on my 2015 Fire + CM12.1 (per OP's link) I'm able to spoof my MAC address using the idme command.
Code:
su -c idme mac_addr 38aa3c123456
su -c idme print mac_addr # check to see that it set it
Then restart the device. After rebooting, go to CM Wi-Fi settings -> Advanced and see if it worked. It seems certain OUIs (first half) are rejected by the OS.
I found this while poking through the kernel code earlier this year. But per @ggow's comment, maybe they've nixed it since then.
Click to expand...
Click to collapse
I can confirm this is working on my fire hd 10 2017!!! You have made my day I wish you the best of luck in life!!!
AustinR66 said:
I can confirm this is working on my fire hd 10 2017!!! You have made my day I wish you the best of luck in life!!!
Click to expand...
Click to collapse
Hi can you tell me how to do this i want to do it on a fire 7 do i need root access? If so what do i need to install and where do i type these idme commands? Sorry bit of a noob to all this.
saupe2005 said:
Hi can you tell me how to do this i want to do it on a fire 7 do i need root access? If so what do i need to install and where do i type these idme commands? Sorry bit of a noob to all this.
Click to expand...
Click to collapse
Hey,
If you have Cyanogenmod, you should be able to do it without installing anything.
These directions are for my Fire 7 2015. Screenshots included at the bottom.
Go to your Settings app and click "About tablet"
Find the line that says "Build number" and tap repeatedly on it. Eventually it will say "Developer settings unlocked" (or something like that).
Now go back to the main Settings page and open "Developer options". On this page you must enable 2 things:
"Root access" - enable this for 'apps'
"Local terminal" - enable this too.
Then reboot the device.
(This is needed for enabling root access.)
The Terminal app may not show directly on your launcher, but you will see it if you list all your apps.
Open the Terminal app, and enter the following commands, on separate lines:
Code:
su
idme mac_addr 4c0b3a000002
idme print mac_addr
(The "su -c" version wasn't working for me with the built-in Terminal app, I had to enter "su" by itself)
- The first line ("su") may show a popup asking you to confirm Root access
- The second line should display to your screen "Writing idme data..."
- The third line prints the mac address to make sure you set it successfully.
After this, you must reboot your device, to activate the new MAC address.
Sometimes the kernel will ignore the new mac, if the first 6 chars (the oui) are unrecognized. The prefixes "4c0b3a" and "38aa3c" both work for me. Or you can use the 6 chars that are built-in for your device. (run the "idme print mac_addr" line to see what they are.)
A mac address is all Hex chars, so only 0-9 and A-F are valid characters.
Check your Wi-Fi settings -> Advanced to make double-sure that it worked.
Hope this helps
Here are the screenshots (Click to zoom)
jrodat said:
Hey,
If you have Cyanogenmod, you should be able to do it without installing anything.
Thanks for your reply.
I dont seem to have the same options as you i have a fire 7, 7th gen i have managed to enable developer options by tapping my serial number but dont see any options about root access any ideas?
Click to expand...
Click to collapse
saupe2005 said:
I dont seem to have the same options as you i have a fire 7, 7th gen i have managed to enable developer options by tapping my serial number but dont see any options about root access any ideas?
Click to expand...
Click to collapse
The instructions were for Cyanogenmod OS 12.1 (thread title), that could be why it looks different.
I should've paid attention when you said "7th gen", my bad. I didn't realize, there's no way to root the 7th gen yet (or install a custom ROM):
https://forum.xda-developers.com/am...th-gen-2017ask-question-t3636919#post73033591
If/when someone cracks it, basically what you would need is a Terminal app from the Play Store, and root. Then the rest of the steps should work.
sorry about that :/
jrodat said:
The instructions were for Cyanogenmod OS 12.1 (thread title), that could be why it looks different.
I should've paid attention when you said "7th gen", my bad. I didn't realize, there's no way to root the 7th gen yet (or install a custom ROM):
https://forum.xda-developers.com/am...th-gen-2017ask-question-t3636919#post73033591
If/when someone cracks it, basically what you would need is a Terminal app from the Play Store, and root. Then the rest of the steps should work.
sorry about that :/
Click to expand...
Click to collapse
You gotta root it but if there is no root available then your out of luck. Sorry mate.
Hey guys and girls, so its a struggle to find firmware for these newer boxes anywhere. The Q1 X96MAX Plus is a revised version of the older model and contains a different WiFi radio set and Ethernet chip.
The old firmware from the other X96max plus on the web if flashed Will brick him but he has an automatic mask mode built in. If you brick him.. Leave him plugged into USB A to USB A and run the firmware below, he will automatically connect and accept this firmware version.
Hope this helps some people as there's not much on this Box in respect of development.
Basically the lack of development is due to the Chinese running scarce of Realtek chips and using whatever they could find to finish production. So many developer are faced with a lottery of trying to figure what firmware WiFi etcetera will work on which box as these models seem to vary so much from box to box instead of the usual one size fits all.
Here it is download, extract and flash with Amlogic UBT :
Q1 FIRMWARE #1
666.25 MB file on MEGA
mega.nz
Q1 FIRMWARE #2
683.48 MB file on MEGA
mega.nz
Regards
Firmware link is courtesy of Vasily Schevchuk, an amazing bloke check out his site here :
https://www.evolutiontv-vs.com/uncategorized/блог-системных-файлов.html
##Edit## Updated 13/02/2021
Bertonumber1 said:
Hey guys and girls, so its a struggle to find firmware for these newer boxes anywhere. The Q1 X96MAX Plus is a revised version of the older model and contains a different WiFi radio set and Ethernet chip.
The old firmware from the other X96max plus on the web if flashed Will brick him but he has an automatic mask mode built in. If you brick him.. Leave him plugged into USB A to USB A and run the firmware below, he will automatically connect and accept this firmware version.
Hope this helps some people as there's not much on this Box in respect of development.
Basically the lack of development is due to the Chinese running scarce of Realtek chips and using whatever they could find to finish production. So many developer are faced with a lottery of trying to figure what firmware WiFi etcetera will work on which box as these models seem to vary so much from box to box instead of the usual one size fits all.
Here it is download, extract and flash with Amlogic UBT :
File on MEGA
mega.nz
Regards
Firmware link is courtesy of Vasily Schevchuk an amazing bloke check out his site here :
https://www.evolutiontv-vs.com/uncategorized/блог-системных-файлов.html
Click to expand...
Click to collapse
The file you posted is no longer available. Could you post it again? Thanks a lot!
lchang.atsoft said:
The file you posted is no longer available. Could you post it again? Thanks a lot!
Click to expand...
Click to collapse
OP updated, 2 newer firmwares, also check out Vasily' site
Bertonumber1 said:
OP updated, 2 newer firmwares, also check out Vasily' site
Click to expand...
Click to collapse
Thank you for posting the files again. Do you know firmware for it that is rooted?
Will this firmware work on the older X96max Plus models?
delucai7 said:
Will this firmware work on the older X96max Plus models?
Click to expand...
Click to collapse
No there is a firmwares for that model. Search for vasily-ts vasikh shevchuk and slimhouse have great firmwares for amlogic boxes.
Regards
Hi.
Is there any way to get rooted firmware for X96 Max+ Q1? Maybe someone know how to root it via twrp/magisk? I know that SuperSu may brick device causing bootloop.
wonzay said:
Hi.
Is there any way to get rooted firmware for X96 Max+ Q1? Maybe someone know how to root it via twrp/magisk? I know that SuperSu may brick device causing bootloop.
Click to expand...
Click to collapse
Hello, I was talking to someone on YouTube about this earlier too.
There maybe a rooted firmware from Vasily Shevchuk :
https://www.evolutiontv-vs.com/uncategorized/блог-системных-файлов.html
scroll to near bottom of page.
I'm afraid TWRP only works via USB and won't give you root privileges on this System as Root device.
You're best bet is to install slimbox rom and patch magisk to boot. At least that way you will have a root and manager app to control it.
Here is a link to slimhouse slimbox firmwares :
project slimBOXtv
A project to create firmware for TV boxes and sticks with an Amlogic processor. Amlogic S905X, S905X2, S905X3, S912, S922, S905W, S905W4, S905Y2, S905L (Android 9) Amlogic S905X4, S905W2, S905Y4 (Android 11) slimBOXtv ATV and AOSP are two...
forum.xda-developers.com
You will also find more help and guidance in that amlogic thread with regards to what you want.
Regards
Thanks for the info. I will try slimbox maybe, but something in stock rom is not clear for me. When I type "su" in console, there is no error message like "su not found", but something similar to "you have no rights to access this executable". I thought that I am be able to boot twrp, mount system as r/w and do some kind of "magic" via commands "chmod&chown". Maybe it's a little bit naive idea.
Sorry for language, it's not native for me.
wonzay said:
Thanks for the info. I will try slimbox maybe, but something in stock rom is not clear for me. When I type "su" in console, there is no error message like "su not found", but something similar to "you have no rights to access this executable". I thought that I am be able to boot twrp, mount system as r/w and do some kind of "magic" via commands "chmod&chown". Maybe it's a little bit naive idea.
Sorry for language, it's not native for me.
Click to expand...
Click to collapse
Hmm I can't remember if it was this box that had the su file in the xbin folder but it needed chmod permissions to work.
By far the easiest way is to just connect via USB, get rid of stock rom an use slim, then patch the boot. Save yourself the headache
Regards
I will try slimbox, but in the future. This is not my tv box, you know.
Found su here:
:/ $ ls -lh /system/xbin/su
-rwsr-x--- 1 root shell 16K 2008-12-31 17:00 /system/xbin/su
Click to expand...
Click to collapse
wonzay said:
I will try slimbox, but in the future. This is not my tv box, you know.
Found su here:
Click to expand...
Click to collapse
Ah.. So it was that box.. Then maybe change permissions and make it executable.
You may not have proper root but it should get you a root shell at least
Regards
Which version of twrp should I use to do that? This is X96 Q1 4/64 box. I don't wanna brick it. I need root shell to change keyboard's config file ("enter" key in hardware bt keyboard doesn't work properly).
wonzay said:
Which version of twrp should I use to do that? This is X96 Q1 4/64 box. I don't wanna brick it. I need root shell to change keyboard's config file ("enter" key in hardware bt keyboard doesn't work properly).
Click to expand...
Click to collapse
You'll only have twrp with a custom rom installed, stock firmware = stock recovery slimbox or one of vasilys roms and it will be a recovery.img via USB flash drive that boots from the update menu.
Have you tried installing a soft keyboard such as SwiftKey, Leanmey or some other that will change default settings?
I was using Leanmey without issues with a Rii mini USB keyboard/mouse.
Again, you're best bet is to flash the slimhouse firmware. These boxes are pretty indestructible and have a built in auto mask rom mode that kicks in after 5 minutes during brick and will accept stock firmware again regardless (so don't worry) .
Hope this helps
Regards
Do you mean in this way?
Bertonumber1 said:
I was using Leanmey without issues with a Rii mini USB keyboard/mouse
Click to expand...
Click to collapse
I will try this. I have tried "simple keyboard", but no success. Enter key doesn't work properly when software keyboard is hidden, because "key 28" in the file "/vendor/usr/keylayout/Generic.kl" has wrong value "DPAD_CENTER" instead of "ENTER". No root = no fun, but at this moment I don't need slimbox, because everything works fine (bt, wifi, hw mouse&keyboard, even custom adw launcher/adaway/yt vanced), except this stupid enter.
wonzay said:
Do you mean in this way?
I will try this. I have tried "simple keyboard", but no success. Enter key doesn't work properly when software keyboard is hidden, because "key 28" in the file "/vendor/usr/keylayout/Generic.kl" has wrong value "DPAD_CENTER" instead of "ENTER". No root = no fun, but at this moment I don't need slimbox, because everything works fine (bt, wifi, hw mouse&keyboard, even custom adw launcher/adaway/yt vanced), except this stupid enter.
Click to expand...
Click to collapse
Your box sounds identical to all my devices app wise ( you missed Newpipe for downloading though )
How did you get on with this? There is three options, you may try inserting the lines for the key into the file or you may try flashing another firmware... If that fails try another keyboard.
I don't know if you've done this already though
Regards
I have left this subject alone (for a time). "Enter" key works via AOSP stock software keyboard - it has option to set default key. The only disadvantage of this "method" is that the AOSP keyboard is visible on the screen.
Ok, I figured it out, enter key works properly on my hardware bt keyboard. X96 MAX+ Q1 gains superuser powers when is connected via adb (root) over wifi. I remounted "read-write" /vendor partition, went to file "/vendor/usr/keylayout/Generic.kl" (make a backup!) and changed the line "key 28 DPAD_CENTER" to "key 28 ENTER". Don't forget to mount back /vendor as "read-only". At the end reboot your box.
Useful commands:
adb:
Code:
adb root
adb connect [ip address of the box]
(backup Generic.kl)
adb pull /vendor/usr/keylayout/Generic.kl
adb shell
re-mount, read write & read only:
Code:
mount -o rw,remount /vendor
mount -o ro,remount /vendor
Shell text editor - only vi is avaliable on my box:
Code:
busybox vi /vendor/usr/keylayout/Generic.kl
On the other hand you can pull "Generic.kl" to your computer, edit it locally, then push to "/vendor/usr/keylayout/" and chmod it correctly. The funny thing is that the "Generic.kl" in "/system/usr/keylayout" has right value for the key 28, but "vendor" path has a higher priority (I think).
ADB can be run directly from the box too, just use app called "termux" (get the latest version from "fdroid") and install in it "android-tools" package via the command:
Code:
apt update && apt install android-tools
Bertonumber1 said:
you missed Newpipe for downloading though
Click to expand...
Click to collapse
Similar tool for this purpose is "youtube-dl". I use it in termux (requires python3), but works anywhere python is installed (linux, windows, macos and so on).
First time posting and I wanted to say thank you to all the excellent talent here on XDA! None of this would have been done without the work of so many people.
I have a Moto G Play (2021) (XT2093-4) that I recently purchased (Best Buy - $159 US/Carrier Unlocked) and I wanted to document my adventure in to rooting, making '/system' RW, and fixing the missing LED notification light (hint: I used the charging light) (hint^2: It's not required to make '/system' RW in order to fix the LED notification light - I just wanted more control over my phone).
First, "OEM unlocking" was greyed out for me, but became available after several days of having the phone online with a SIM card.
I followed the instructions here to unlock the bootloader and root with Magisk (Non-TWRP). Along with these instructions.
Once bootloader is unlocked, you will need the 'boot.img' file from your stock firmware. I used the "Rescue and Smart Assistant" utility to grab a copy of the stock firmware (GUAMNA_RETAIL_QZAS30.Q4_39_35_9_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml) and extracted the "boot.img" file for the next steps.
Continue installing Magisk (Filenames may be different! Don't just copy and paste.):
Code:
adb install Magisk-v23.0.apk
adb push boot.img /sdcard/Download
(Follow the instruction on your phone to patch 'boot.img' in Magisk)
adb pull /sdcard/Download/magisk_patched-23000_aKKMt.img
adb reboot bootloader
fastboot flash boot_a magisk_patched-23000_aKKMt.img
fastboot flash boot_b magisk_patched-23000_aKKMt.img
You should now have a working, rooted Moto G Play. You can just stop here and have fun with your phone, but I noticed that even with root, the system partition was not RW.
I followed these instructions to make '/system' writable (Note: you will need the 'sysrw_repair.zip' that's included in the bundle and a Linux system):
Code:
adb push systemrw_1.32_flashable.zip /data/local/tmp/
adb shell
su
cd /data/local/tmp/
unzip systemrw_1.32_flashable.zip
cd systemrw_1.32/
chmod +x systemrw.sh
./systemrw.sh in=`ls -l /dev/block/by-name/super | awk '{print $NF}'` out=/data/local/tmp/systemrw_1.32/img/super_original.bin size=50
The phone doesn't have enough space to complete 'lpmake' on the device and will end with an "Error 73" code. Running the "sysrw_repair_v1.32" tool on a Linux machine was a workaround because it pulls the '*.img" files to your local machine then combines them in to a single '.bin' file. But, before I did that, and because it's really annoying, I made some room to stop the phone from complaining about a lack of space:
(Still on the phone's adb)
Code:
rm ./img/super_original.bin
Now, on the Linux machine, I unzipped 'sysrw_repair_v1.32_proper.zip' then commented out line 39 (where it calls the "flash()" function) of the script (sysrw_repair.sh) because I wanted to flash the "super" partition myself.
(On another Linux terminal)
Code:
cd /path/to/unzipped/sysrw_repair/dir/
chmod +x sysrw_repair.sh
./sysrw_repair.sh
This results in a new folder (img) with a rather large bin file (super_original.bin).
(Back on the phone adb)
Code:
exit # Exit root
exit # Exit adb
adb reboot bootloader
Now it's time to flash the fixed bin file to the "super" partition:
Code:
cd /path/to/unzipped/sysrw_repair/dir/
fastboot flash super ./img/super_original.bin
fastboot reboot
You should be able to login and have a writable '/system':
Code:
adb shell
su
mount -o rw,remount /
No errors should appear.
Last, I like having an LED indicator that tells me that I have an SMS/MMS notification waiting. Motorola thought it would be wise to eliminate that feature altogether instead of having the option to enable it. So, I forced it back on using a startup script that dumps the notifications and greps for some key words. And, if it finds something, it "breaths" the charging LED. The script loops until the notification is gone, then keeps checking for new notifications every 30 seconds. (Note: the "/data/adb/service.d/" directory is used by Magisk like an INIT service):
(Still root on the phones adb)
Code:
cd /data/adb/service.d/
cat <<EOF > ledfix.sh
#!/bin/sh
while true; do
if dumpsys notification | egrep NotificationRecord | egrep sms > /dev/null
then
if [[ $(cat /sys/class/leds/charging/breath) == 0 ]]
then
echo 1 > /sys/class/leds/charging/breath
sleep 2
continue
else
sleep 2
continue
fi
elif egrep 'Charging' /sys/class/power_supply/battery/status > /dev/null
then
if [[ $(cat /sys/class/leds/charging/breath) -ne 0 && $(cat /sys/class/leds/charging/brightness) -ne 0 ]]
then
echo 0 > /sys/class/leds/charging/breath
echo 255 > /sys/class/leds/charging/brightness
elif [[ $(cat /sys/class/leds/charging/breath) == 0 && $(cat /sys/class/leds/charging/brightness) == 0 ]]
then
echo 255 > /sys/class/leds/charging/brightness
else
continue
fi
else
echo 0 > /sys/class/leds/charging/breath
echo 0 > /sys/class/leds/charging/brightness
fi
sleep 30
done
EOF
chown 0.0 ledfix.sh
chmod 0755 ledfix.sh
reboot
Now, the charging light will fade off and on about every 2 seconds if there's an SMS/MMS notification waiting. And will check for notifications every 30 seconds. I'm sure someone can come up with a better way of doing this, but this was a nice quick-and-dirty way to get what I wanted.
Hope this helps!
I created an account to say thank you for this, I have already done a good portion, having unlocked the bootloader, the problem is the Rescue Smart Assistant, it won't let me log in, it keeps telling me it can't connect, and the GUI is different because of an update, there is no download button inside the program, only a greyed out rescue button. How did you manage to make the backup Boot.img? Maybe you are using a different OS, and/or version of the program (Not the app, that is already auto-installed), I'm using Windows 10, are you on Linux? I might just need to try from Linux, maybe in a VM.
I was trying to do this before I found this post, and have already installed ADB, the SDK, fastboot, and Motorola Drivers, I just need a way to get the Boot.img, and to patch it, also figure out how to flash it. The last android I rooted with a custom rom was the HTC EVO 4G with Oreo/Jellybean, so I'm a little rusty, but am able to understand technical jargon.
If anyone could help, that would be awesome. I've reinstalled different versions of Rescue Smart Assistant as well, they always upgrade on boot, same problem. I've added exceptions to my firewall and everything.
UPDATE: Was about to post this when I had updated from android 10 to 11 and decided to try logging in again a little closer to my router, to see if the connection was timing out, I think that was the cause, as I can now sign in, and the GUI seems correct from the first appearance. I don't see why I should have any trouble following the rest of the guide, but feel I should share my trials and frustrations anyways, for anyone else experiencing the same,
Thanks again.
PROFSLM said:
I created an account to say thank you for this, I have already done a good portion, having unlocked the bootloader, the problem is the Rescue Smart Assistant, it won't let me log in, it keeps telling me it can't connect, and the GUI is different because of an update, there is no download button inside the program, only a greyed out rescue button. How did you manage to make the backup Boot.img? Maybe you are using a different OS, and/or version of the program (Not the app, that is already auto-installed), I'm using Windows 10, are you on Linux? I might just need to try from Linux, maybe in a VM.
I was trying to do this before I found this post, and have already installed ADB, the SDK, fastboot, and Motorola Drivers, I just need a way to get the Boot.img, and to patch it, also figure out how to flash it. The last android I rooted with a custom rom was the HTC EVO 4G with Oreo/Jellybean, so I'm a little rusty, but am able to understand technical jargon.
If anyone could help, that would be awesome. I've reinstalled different versions of Rescue Smart Assistant as well, they always upgrade on boot, same problem. I've added exceptions to my firewall and everything.
UPDATE: Was about to post this when I had updated from android 10 to 11 and decided to try logging in again a little closer to my router, to see if the connection was timing out, I think that was the cause, as I can now sign in, and the GUI seems correct from the first appearance. I don't see why I should have any trouble following the rest of the guide, but feel I should share my trials and frustrations anyways, for anyone else experiencing the same,
Thanks again.
Click to expand...
Click to collapse
You can also get the firmware from
Lolinet Mirrors
https://t.me/MotoUpdatesTracker
Search for Firmware by codename, software channel, Software Version, and build #
So I wasn't going crazy when I could swear a LED notification light in the upper right side above the screen blinked once whenever I rebooted the phone?
Why would Motorola include such a thing and not utilize it for more than merely a boot up indicator? Like I dont even get to see it come on while charging, it literally only blinks once during boot and that's it.
mario0318 said:
So I wasn't going crazy when I could swear a LED notification light in the upper right side above the screen blinked once whenever I rebooted the phone?
Why would Motorola include such a thing and not utilize it for more than merely a boot up indicator? Like I dont even get to see it come on while charging, it literally only blinks once during boot and that's it.
Click to expand...
Click to collapse
I know!
I don't know what triggers that light to come on. I even waited until the battery was at 6% and the light still never came on.
So, I updated the script above to make the light go full brightness if the battery is charging. The order matters, so if a notification comes in while charging, it'll "breath" the LED. Also, if the battery is full, then the light will turn off. Kind of telling you that it's time to unplug.
I followed these steps and my touch screen stopped working. I had previously installed twrp already on it while trying to learn how to root it, and when i boot into fastboot it goed through twrp, i also used the boot.img file from lolinet, not sure which of these caused the issue. Interestingly though, the touch screen does work whilst in twrp. any suggestions on how to fix or what would be causing it? Phone does work with usb mouse over OTG
jorduino said:
I followed these steps and my touch screen stopped working. I had previously installed twrp already on it while trying to learn how to root it, and when i boot into fastboot it goed through twrp, i also used the boot.img file from lolinet, not sure which of these caused the issue. Interestingly though, the touch screen does work whilst in twrp. any suggestions on how to fix or what would be causing it? Phone does work with usb mouse over OTG
Click to expand...
Click to collapse
Are you absolutely sure you used the correct boot.img from an image version exactly matching your phone variant version?
mario0318 said:
Are you absolutely sure you used the correct boot.img from an image version exactly matching your phone variant version?
Click to expand...
Click to collapse
Im not completely sure how to get the right file, but I think the first time it was the wrong one, but then when i got what i thought was the right one, it just didn't work at all and I had to recovery flash it. I had just updated so maybe the correct image wasn't available yet. Im going to try again though
Oh! Hello @latentspork. Thanks for your interest in my SystemRW project. I just came across this thread randomly...
I'm happy you got my script to work on your Motorola device by using the included sysrw_repair script
Please feel free to send me your log files from script folder. Thanks. It's useful for further development of the script
latentspork said:
The phone doesn't have enough space to complete 'lpmake' on the device and will end with an "Error 73" code. Running the "sysrw_repair_v1.32" tool on a Linux machine was a workaround because it pulls the '*.img" files to your local machine then combines them in to a single '.bin' file. But, before I did that, and because it's really annoying, I made some room to stop the phone from complaining about a lack of space:
Click to expand...
Click to collapse
That's not 100% accurate. Lpmake error 73 means CAN'T_CREATE and has nothing to do with error 70 (insufficient space).
To this day I still don't know exactly what causes error 73 on some devices (mostly Motorola and others) but it looks like some kind of kernel panic. If anyone knows how to avoid this error 73 in Android please let me know! Thanks!
Yes that's true the included sysrw_repair script (Linux only) pulls the image files from the phone to your computer and attempts to run the same lpmake command with the same arguments that just failed with error 73 on the phone itself and now all of a sudden it just works in Linux. Go figure.
latentspork said:
(Still on the phone's adb)
Code:
rm ./img/super_original.bin
Click to expand...
Click to collapse
Why would you delete the super_original.bin ? That's your stock read-only super image which by default is automatically dumped by script for backup purposes in case you ever get a bootloop.
And if you launch the script by specifying a custom input value (in=x) like in your example above then you won't even have a super_original.bin file to begin with because script will skip the whole dumping of original super image process.
latentspork said:
This results in a new folder (img) with a rather large bin file (super_original.bin).
Click to expand...
Click to collapse
I think you mean super_fixed.bin
latentspork said:
Now it's time to flash the fixed bin file to the "super" partition:
Code:
cd /path/to/unzipped/sysrw_repair/dir/
fastboot flash super ./img/super_original.bin
fastboot reboot
Click to expand...
Click to collapse
Here in your instructions you are manually flashing the wrong file. Shouldn't you be flashing super_fixed.bin to your super partition?
Usually I only flash the super_original.bin to get back out of a bootloop...
latentspork said:
Now, on the Linux machine, I unzipped 'sysrw_repair_v1.32_proper.zip' then commented out line 39 (where it calls the "flash()" function) of the script (sysrw_repair.sh) because I wanted to flash the "super" partition myself.
Click to expand...
Click to collapse
See that's why I included that automatic flash() function in the repair script. Then you don't have to worry about manually flashing the wrong file to your super partition
Enjoy a fully read/write-able device!
Great news! New SystemRW version coming soon!
@lebigmac
I really appreciate the reply and the tool! It did work really well on my model (XT2093-4).
That's not 100% accurate. Lpmake error 73 means CAN'T_CREATE and has nothing to do with error 70 (insufficient space).
To this day I still don't know exactly what causes error 73 on some devices (mostly Motorola and others) but it looks like some kind of kernel panic. If anyone knows how to avoid this error 73 in Android please let me know! Thanks!
Click to expand...
Click to collapse
I only assumed that "Error 73" was caused by insufficient space, because the phone really did run out of space. I noticed that the phone was out of space because I got a home screen notification warning, asking me to free up space. I confirmed it with a "df -h" at the shell. Apparently, the OS takes up almost 15GB. When you add the ".img" files, there's only about 5GB left. There wasn't enough room to complete the ".bin" file. Maybe I could have used an SD card or something.
You're probably correct in that "Error 70" is the correct error for that, but on my phone, I never saw that error. I did notice that the tool was still trying to write data as the phone ran out of space, then it would throw the "Error 73". Maybe it didn't register the lack of space, or just an oddity with my model? No idea.
Why would you delete the super_original.bin ?
Click to expand...
Click to collapse
This is the file that was created when I initially ran the "./systemrw.sh" command on the phone. The result of running the command on the phone were several ".img" files and a very large "super_original.bin", but it was incomplete because the command threw an "Error 73". I was following your instructions, and I noticed that the output name of the file was "original" instead of "fixed". I probably could of outputted it to a new name to reduce confusion, but I didn't really care too much about the name as long as I had a working file.
I think you mean super_fixed.bin
...
Shouldn't you be flashing super_fixed.bin...
Click to expand...
Click to collapse
Normally, yes. But the Linux script also outputted the filename "super_original.bin". Again, as long as it worked, I was okay with it. The commands I used above were the exact commands that I ran at the time. I copied them from the terminal consoles I was using. So I don't know why it wasn't outputting the correct filename (again, I was following your instructions and was a little confused that the names came out differently - I just figured I was doing something wrong like not use the proper output command or something).
Then you don't have to worry about manually flashing the wrong file to your super partition...
Click to expand...
Click to collapse
I was really just being cautious because my previous phone broke and I didn't have a fallback.
But, at no point were there two bin files (original and fixed), so there wasn't much confusion. Where I originally had just ".img" files before running the script, I now had a single ".bin" file. I knew that was the file I needed.
But again, thank you for all the hard work on this tool! I was reading that it's worked on lots of different model phones, and it's always good to see the open source community doing things that help all kinds of people.
For moto notification for this phone at least use https://play.google.com/store/apps/details?id=br.com.itsmeton.motoledreborn or moto led reborn from the play store it just works
Hi, sorry. This can be removed. I put it in place because I was having issues with the xda app. For whatever reason, every time I tried to share this particular post, it would share a link for the post which I used originally, rather than the current post. I knew that if I commented I could get back here easily on my PC.
So what is the place holder for
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.