I have an unrooted device with stock ROM (Android Pie) and I don’t plan to root it.
I wonder if it’s possible to make some changes on unrooted device in a file located at the following address: /data/data/com.android.mms/shared_prefs?
Is there any workaround through ADB?
I tried this method https://forum.xda-developers.com/showthread.php?t=1829681 , but unfortunately "run-as con" and its variations return "is unknown"
Please advise on the problem.
Related
A friend of mine bought an Alcatel OT895, which is a not so famous phone, and I don't know how can I root it, is it even possible?
And if rooting is possible, can I install a custom ROM (especially CM7.2) on it? I couldn't find anything useful anywhere.
Someone has to find out what hardware it has and what Android version it has. If you have the technical inclination, you could:
* Connect the phone via USB (with debugging enabled on the device) and access the internal filesystem via ADB (a tool from the Android SDK)
* Extract the relevant information, located in files named like 'build.prop', as well read /proc/cpuinfo
But even without those info (they just help in getting to know the hardware), you could jump straight into running an exploit to see if it works. If the Android version the vendor shipped with the device still has the particular vulnerability, the exploit will work.
Else, you need to extract the boot image and edit files, then repack and flash it. This is only possible if you have access to a safe flashing environment, i.e. custom recovery, so that you can first back up the partition.
There may be other ways, but that depends a lot on who else has posted information related to your device on the Internet or elsewhere.
Thanks, but I'm too noob for this, so I rather leave it on stock.
Is it possible to root an update.zip, then install the update to gain root access. I have seached the net for weeks to find a way to root this table with no luck. I cannot get adb access to the table with the provided drivers (no device found). But I have the Update.zip from the manufacturer is this possible? Can an update.zip be rooted and can someone walk me through this process.
tannerjames said:
Is it possible to root an update.zip, then install the update to gain root access. I have seached the net for weeks to find a way to root this table with no luck. I cannot get adb access to the table with the provided drivers (no device found). But I have the Update.zip from the manufacturer is this possible? Can an update.zip be rooted and can someone walk me through this process.
Click to expand...
Click to collapse
No, the signature validation will fail if you modify it at all.
Sent from my SPH-D710 using Tapatalk 2
tannerjames said:
Is it possible to root an update.zip, then install the update to gain root access. I have seached the net for weeks to find a way to root this table with no luck. I cannot get adb access to the table with the provided drivers (no device found). But I have the Update.zip from the manufacturer is this possible? Can an update.zip be rooted and can someone walk me through this process.
Click to expand...
Click to collapse
It sometimes can be posible to root a stock rom. I did. What type of tablet er phone do you have? I have a Chinees tablet. I have been able to make and flash my home made rooted tock rom thanks to this post here: http://www.chinadigitalcomm.com/post23364.html
Over 200 people flashed my stock rom to there device.
You can alsow take the register key file from you're stock rom and try again if it does not work. It can be found in system\etc\security of you're stock rom. The file you need is testkey.x509
I to did look for weeks to get a way to sign my stock rom right.
If i'm right you're on windows? Me to. And i have Linux to develop rom and recovery and stuff.
Have a look at my thread here. http://forum.xda-developers.com/showthread.php?t=1935162
Here is the stock rom i rooted. Dutch language: http://www.androidworld.nl/forum/to...ent-7-rootedstock-rom-updated-11-11-12-a.html
Have a look at the rom and see you i changed the update script and put su in xbin and bin folder. And the superuser.apk in the right folder.
I gues you have to make sure windows is able to find you're device. Most easy to do that in Lunix! See my first forum post.
You could try and build a Recovery FakeFlash update.zip I think that will flash on you're stock rom. Does for me.
Pm me if you want to be sure i see this post again
Goodluck
Hi,
I'm working on a project where I would sale an android tablet with dedicated App. (not for consumer market but Business to business)
the chosen tablet is Asus TF300T with the Ethernet port.
The problem I have is :
I would like my Application would have access in read/Write to the Ethernet Card settings (not Wifi)
This is relatively easy to do if the tablet is rooted -> but the rooting is something we can't do for many reasons.
by a work around, we succeeded to change the Ethernet IP address but didn't success to apply it (caused by the custom "apply" Asus button in ethernet settings page)
to apply the IP Adress we have to ask to the application user to go to the Settings page and push by himself the "apply" button ..... it's not the best.
My question is :
Is it possible to build a auto-signed flashable zip containing my Application, This flashable zip would install the App and give it the right access to the Ethernet card settings, without root rights needs?
or
Does exist a way that the Application reboot a tablet without root rights?
Thanks a lot for your help
You won't be able to flash anything without unlocking the device as you need a custom recovery installed. You don't need to be rooted to do what you require.
Thanks for your reply,
I understand that the device needs to be unlocked, However, I didn't know a custom recovery was needed to do that.
do you confirm I cannot do it from the standard recovery?
Underscan said:
Thanks for your reply,
I understand that the device needs to be unlocked, However, I didn't know a custom recovery was needed to do that.
do you confirm I cannot do it from the standard recovery?
Click to expand...
Click to collapse
The device won't accept anything from the stock recovery unless it is signed by Asus.
Ah I just got what you are saying - you want to try and flash something on the stock recovery on an unlocked device? How will you do that?
Why can't you put TWRP onto the device and flash your app?
"you want to try and flash something on the stock recovery on an unlocked device? How will you do that?"
I don't know
"Why can't you put TWRP onto the device and flash your app?"
we would like to reduce at maximum the number of TF300T handling between the Asus tablet reception and the shipping to our customer.
If we had found a solution to just flash theTF300 with a flashable zip -> that it ! the App is installed with the good user right (only for our App). -> it would be awesome!
It seems the only way to have it, is to get the Asus signature... seems impossible...
In essence you are wanting to put a custom stock ROM on it.
There are two ways to achieve this
1: unlock, flash twrp via fast boot and then flash the app.
2: root using moto chopper and manually place your app in /system/app
Alternatively you could just ask the user to sideload your app by allowing that through the settings on the device.
sbdags said:
In essence you are wanting to put a custom stock ROM on it.
There are two ways to achieve this
1: unlock, flash twrp via fast boot and then flash the app.
2: root using moto chopper and manually place your app in /system/app
Alternatively you could just ask the user to sideload your app by allowing that through the settings on the device.
Click to expand...
Click to collapse
Doesn't look like the sideloading would grant sufficient privileges though, at least if you're referring to the sideloading I'm thinking of.
Hello to all,
Please some help/advice, I'm new in this.
I have more than a week trying to find a way to install Google Services on a Huawei P40 Lite. version JNY-LX2 (JNY-LGRP2-OVS 10.1.0.297 - C25E5R2P1).
I found some methods failed with (Using LZPlay app) then I found that is needed to do a downgrade and use the Googlefier method or dload method but I'm currently stuck with the following 2 issues
1-) I found a firmware in pro-teammt.ru that is minor to 10.1.0.150 but I cannot find the way to download it.
2-) Before to proceed I´d like to make a backup of the stock firmware that the device has now (if something goes wrong), but I don´t find yet a way to make the stock ROM backup.
Then,
1-) May someone help me out in how to make a stock rom backup. Maybe some written guide that I haven´t found yet.
The device is not rooted but I'm confused, since I see in some sites they say that only can be done in rooted devices and in others sites they say is no needed be rooted.
2-) How to download the firmware from pro-teammt.ru since when I do click on links always appears server connection errors or that maybe have been removed.
3-) The C25 region I found that is for Latam, but C605 is for Latam too I think. So, If only possible to find and download C605 firmware would be work on this device?
Thanks in advance for any help.
Regards
Device's Android must be rooted ( temporarily or permanent ) to fully backup its Stock ROM ( what consists of boot.img, system.img, recovery.img, metadata, etc.pp ): Reason is that Android must get mounted as RW what requires superuser rights.
Once rooted a full backup easily can be done by means of ADB.
Example:
Code:
adb devices
adb exec-out dd if=/dev/block/mmcblk0p7/boot.img > C:\boot.img
adb exec-out dd if=/dev/block/mmcblk0p20/system.img > C:\system.img
...
If you have an eMMC internal storage you can see names and partitions at same time running
Code:
adb shell "ls -l /dev/block/platform/msm_sdcc.1/by-name/"
jwoegerbauer said:
Device's Android must be rooted ( temporarily or permanent ) to fully backup its Stock ROM...
Click to expand...
Click to collapse
Thanks for your answer. Then first step should be roote the device.
Do you know a good guide to root this Huawei model (or guide that works for any device)?
I can search on google, but there is many results and some noise since some are old or different procedures and I'm not sure which would be safer to choose in order to avoid damage the device.
Regards
Because your phone is running Android 10 ( EMUI 10 ) and based on Kinn 810 chipset I guess all the so-called One-Click-ROOT tools aren't working at all.
I don't own this phone, hence I can't guide you further. Thanks for your understanding.
jwoegerbauer said:
Because your phone is running Android 10 ( EMUI 10 ) and based on Kinn 810 chipset I guess all the so-called One-Click-ROOT tools aren't working at all.
I don't own this phone, hence I can't guide you further. Thanks for your understanding.
Click to expand...
Click to collapse
I understand. Thanks for your help anyway.
Regards
Hi,
I want to download the current firmware from a device. (in this case SM-A125F/DSN )
After hours of searching I gave up. All I got are guides etc. to download firmwares from WEB.
I need it as a backup for my experiments. But if, by any chance, someone can point me to a place where I can download this exact firmware, I'd be happy too.
I also tried to find that specific firmware as an alternative to downloading. But no luck after another 60 minutes. (beside some dubious sites that claimed to have everything but wanted money first, so I was obviously digging deep already - maybe I'm just asking the wrong questions (search terms))
Ofc. I'd prefer to download it from device.
SM-A125F/DSN
[ QP1A.190711.020. ] A125FXXU1AUC3
4.9.190-20270726
If you mean backing up / extracting phone's firmware then - if phone's Android is rooted - you may use ADB to achieve this.
Example extracting boot.img
Method 1
Code:
adb devices
adb root
adb pull "<NAME-OF-RELATED-BLOCK-DEVICE-HERE>" > C:\boot.img
Method 2
Code:
adb devices
adb root
adb exec-out "dd if=<NAME_OF_RELATED_BLOCK_DEVICE_HERE> bs=4096" > C:\boot.img
tyvm for the input!
it is not rooted (but the bootloader is unlocked but I fear this won't help, would it ?)
I guess same applies to the other partitions? (root requirement)
further I guess, there is no way to do this without root (you would have mentioned it, even if obscure, right? :] )
i focus on alternative now (search for firmware)
EDIT: yes, I mean "backing up / extracting phone's firmware"
jwoegerbauer said:
If you mean backing up / extracting phone's firmware then - if phone's Android is rooted - you may use ADB to achieve this.
Click to expand...
Click to collapse
Tell me please if it has sense to backup literally all partitions?
asq81:
ADB doesn't know much about rooting as far as I know, especially in download mode.
It wants only USB debug activated.
asq81 said:
Hi,
I want to download the current firmware from a device. (in this case SM-A125F/DSN )
After hours of searching I gave up. All I got are guides etc. to download firmwares from WEB.
I need it as a backup for my experiments. But if, by any chance, someone can point me to a place where I can download this exact firmware, I'd be happy too.
I also tried to find that specific firmware as an alternative to downloading. But no luck after another 60 minutes. (beside some dubious sites that claimed to have everything but wanted money first, so I was obviously digging deep already - maybe I'm just asking the wrong questions (search terms))
Ofc. I'd prefer to download it from device.
SM-A125F/DSN
[ QP1A.190711.020. ] A125FXXU1AUC3
4.9.190-20270726
Click to expand...
Click to collapse
I don't know much about tech, but it seem to me that you would make your life easy if you would:
1. Look at the exact firmware you have at about phone. I guess you have a Samsung Galaxy A12.
2. Use a reliable Samsung firmware website, for example https://www.sammobile.com.
3. Click browse firmware archive
4. Enter your model: SM-A125F
You should have there the firmware specific for numerous countries, as far as the last 2-3 firmwares for your device. I think on sammobile they might ask you to create an account.
F308 said:
Tell me please if it has sense to backup literally all partitions?
asq81:
ADB doesn't know much about rooting as far as I know, especially in download mode.
It wants only USB debug activated.
Click to expand...
Click to collapse
Don't confuse the Android images like
boot.img, system.img,recovery.img,vendor.img,vbmeta.img, etc.pp
and Android partitions.
The described 'pull' method works well! Thank you jwoegerbauer!
(did not try 'dd' - there was no reason to do so for me)
For me it was ok to flash a boot image and leave everything else untouched. (yay, finally found one and let magisk patch it to have root)
In my case I did not plan to do anything to boot image, just had to find a working one (with root) and backup this. BUs from everything else is what I really need. Not a perfect but totally adequate solution!