Related
Hey guy's, I've beentrying to install clockworkmod on my Epic for some time now to no avail. See, I just rooted my phone using the noobnl's "one click method v2.2.6". The only recovery I have on my phone as of right now is tthe stock recovery. I've read just about every post about the installation on clockworkmod recovery and tried accordingly. Still no custom ecovery. Im really noob to all this "wiz stuff", and would greatly appreciate any help you guy's could give me. Perhaps some DETAILED step by step instructions ( CUZ IM REAL BRAIN DEAD AT TIMES )?? I have DI11 installed on my phone as of now, and im running the stock kernel v2.6.29. again, Im rooted with "noobnl's one click" and I do have root. Also, I need to know if you download to my pc, then push it to my phone using command prompt? Do I flash it with Odin? And what do I do after I run the clockworkmod exploit? Will I have custom recovery after that, is there anymore steps involved? Thank you all for making this site the best web site I"ve been on so far. You guy's are the best. Please hel[p with my dumb question, and sorry to waste your time. Thankx IA..
http://forum.xda-developers.com/showthread.php?t=782300
Download the .zip from that. Extract it to your desktop and rename the folder "cwm". Open up command prompt. Type this:
Code:
cd C:\Users\YOUR USER NAME\Desktop\cwm
adb shell
su
remount rw
exit
exit
After that, run the run.bat from the folder.
Download the .zip from that. Extract it to your desktop and rename the folder "cwm". Open up command prompt. Type this:
Code:
cd C:\Users\YOUR USER NAME\Desktop\cwm
adb shell
su
remount rw
exit
exit
After that, run the run.bat from the folder.
Click to expand...
Click to collapse
Excuse the stupid question please, do I have the sdcard mounted, or unmounted? I heard it can be done either way...
The only thing you use Odin for is to flash a complete .tar file. Ie, returning to stock, or updating to a new release DG27, DI07, or DI18
sniperkill said:
Excuse the stupid question please, do I have the sdcard mounted, or unmounted? I heard it can be done either way...
Click to expand...
Click to collapse
Make sure it is NOT mounted as a mass storage device. Make sure you can access it from the phone. So, don't mount it.
LSanna1488 said:
The only thing you use Odin for is to flash a complete .tar file. Ie, returning to stock, or updating to a new release DG27, DI07, or DI18
Click to expand...
Click to collapse
Technically, custom ROMs can be made for Odin, too... But since it's not a very good method, everyone prefers the recovery method. noobnl released his first rooted kernel for Odin. Odin does a lot more than just complete .tars.
LSanna1488 said:
The only thing you use Odin for is to flash a complete .tar file. Ie, returning to stock, or updating to a new release DG27, DI07, or DI18
Click to expand...
Click to collapse
I ran the commands as you stated, then ran the exploit. It keeps saying,
"remove stock recovery patcher"
"device not found"
system (something) install recovery.sh permission denied
"system/recovery-from-boot.p permission denied
failed to copy 'zImage' to /sdcard/zImage: permission denied
reboot: operation not permitted
im failed for /sdcard/zImage, permission denied
So what do you think is going on? Any thoughts?
I had same exact issue. Went back to completely stock then rooted then did clockwork. Do not mount sd card. Follow instructions exactly.
Sent from my SPH-D700 using XDA App
I'm having the same issue. When trying to 'su' to do the remount I'm getting a permission denied... but apps that require root seem to be working.
sniperkill said:
I ran the commands as you stated, then ran the exploit. It keeps saying,
"remove stock recovery patcher"
"device not found"
system (something) install recovery.sh permission denied
"system/recovery-from-boot.p permission denied
failed to copy 'zImage' to /sdcard/zImage: permission denied
reboot: operation not permitted
im failed for /sdcard/zImage, permission denied
So what do you think is going on? Any thoughts?
Click to expand...
Click to collapse
Is your phone in debug mode? (Settings -> Applications -> Development -> USB Debugging) Did it actually let your run those commands I told you?
Yes, my phone is in fact in debugg mode. My desktop command prompt does let me run the commands.
Adb devices
Adb shell
Su #
Remount rw
Exit
Exit
After I type the command "su" it gives me the #. Then on my phone a superuser request comes thru and askes to chose "yes" or "no". So I hit "yes". But when I run the exploit in the beginning it says "mount", and it says that the operation is not permitted... then it starts saying "I'm failed for" and "operation not permitted" and so on.. I think I'm missing a step somewhere but I don't kno...
Sent from my SPH-D700 using XDA App
Running su through adb shouldn't ask for permission the phone... that is weird.
Sent from my SPH-D700 using XDA App
I spent the weekend trying to get my Epic rooted and cwm installed. I was finally successful with both. CWM I had to install by typing in each command that was in the bat through the cmd window with adb.
Flak said:
I spent the weekend trying to get my Epic rooted and cwm installed. I was finally successful with both. CWM I had to install by typing in each command that was in the bat through the cmd window with adb.
Click to expand...
Click to collapse
So exactly what are the steps you took to install clockworkmod manually through windows command prompt? Do I just look in the bat exploit?
Hi all!
I finally managed to ROOT an aPad M701 using z4Root.apk
Now I want to make an image of my entire ROM tablet, I've heard that under the ROM manager app is a tool called "Flash ClockworkMod Recovery" that has to be installed in order to make a full ROM backup.
The problem is that everytime I try to install it a screen pops out telling me to choose from the list my model of phone (I'm on an aPad tablet), since I'm not on a phone, I'm unable to continue with the process!
Any method or workaround for installing Flash ClockworkMod Recovery on Haipads/aPads M701?
Thanks in advance for the help.
Custom Recovery Image
On Team Telechips website there is a custom Clockwork recovery image toward the bottom of the page.
Use the .bat file they include in their ZIP file or push the .img file to /nand and flash. You will then be able to back up everything with the custom m701 clockwork application.
If the .bat file doesn't work for you, try opening it up as text and use the commands as a guide to push via adb.
Thanks a lot for the reply Clookeno but I dont know where to start with this, do you know any step by step guide I can use to achieve this?
Again thanks for the info.
Adb push issues
Clookeno said:
On Team Telechips website there is a custom Clockwork recovery image toward the bottom of the page.
Use the .bat file they include in their ZIP file or push the .img file to /nand and flash. You will then be able to back up everything with the custom m701 clockwork application.
If the .bat file doesn't work for you, try opening it up as text and use the commands as a guide to push via adb.
Click to expand...
Click to collapse
I'm trying this and when using adb push to /nand I'm getting back "failed to copy 'recovery.m701.img' to '/nand/recovery.m701.img': Read-only file system"
I'm currently running Haipads 2.2 version and I was looking at testing out CM6 version, but can't seem to get the img file over.
And Ideas?
read only file
adb shell mount -o remount,rw /dev/block/mtdblock3 /system
The /nand folder needs to be read-writeable....since you use z4root go into temporary root and the push the file into /nand folder
Locobox said:
Thanks a lot for the reply Clookeno but I dont know where to start with this, do you know any step by step guide I can use to achieve this?
Again thanks for the info.
Click to expand...
Click to collapse
Locobox, there likely isn't a step-by-step guide for the procedure because it has a .bat file which is basically a executable file in windows that runs a set of commands in the DOS prompt for you. Basically you just double click the install_recovery.bat file and it puts the ADB commands in for you to push the recovery image to your tablet.
If you right click the .bat file and click edit you will see the following ADB commands:
adb push recovery.m701.img /nand/recovery.m701.img
adb shell sync
adb shell flash_image recovery /nand/recovery.m701.img
adb shell sync
adb shell reboot recovery
If you are familiar with ADB you can also copy the .img file to your sd card and flash it from there.
i recommend you have root access and the ADB utility.
Sorry it took so long to reply, work has been killing me lately....
poole699 said:
I'm trying this and when using adb push to /nand I'm getting back "failed to copy 'recovery.m701.img' to '/nand/recovery.m701.img': Read-only file system"
I'm currently running Haipads 2.2 version and I was looking at testing out CM6 version, but can't seem to get the img file over.
And Ideas?
Click to expand...
Click to collapse
poole699,
I have tried everything you can think of to put CM6 on the 2.2 Haipad firmware (which is really a modded 2.1) and had no luck. Either the system directories are all messed up or they locked the ability to edit it somehow. If you figure it out let me know because i have wanted to try it for a while.
I have a working team telechips 2.2 with market and correct orientation settings but it took ALOT of trial and error. If you go that route make sure you back-up your pointercal file because if you do not you will likely have to go back to an official release, save it, and try the telechips mod again...
Good luck
Clookeno said:
Locobox, there likely isn't a step-by-step guide for the procedure because it has a .bat file which is basically a executable file in windows that runs a set of commands in the DOS prompt for you. Basically you just double click the install_recovery.bat file and it puts the ADB commands in for you to push the recovery image to your tablet.
If you right click the .bat file and click edit you will see the following ADB commands:
adb push recovery.m701.img /nand/recovery.m701.img
adb shell sync
adb shell flash_image recovery /nand/recovery.m701.img
adb shell sync
adb shell reboot recovery
If you are familiar with ADB you can also copy the .img file to your sd card and flash it from there.
i recommend you have root access and the ADB utility.
Sorry it took so long to reply, work has been killing me lately....
Click to expand...
Click to collapse
Thanks again for the info, but I'm not familiar with ADB. The procedure seems difficult for me hope this thread helps a lot of other users!
Again thanks for the response.
M701 Screen Flip
Hi guys, I've got a bit of a problem with my M701 tablet. I did a factory reset the other day and now the digitizer is inverted. The screen works fine but when I touch the top it senses the bottom & left = right.
This is a complete pain in the arse.
I plugged the unit into a keyboard via the usb port as a workaround until I could get into it to try to resolve the issue but I'm now stuck in a loop at the sign in to google bit. Every time I sign in it takes me back to the sign in page.
This is also a complete pain in the arse.
It doesn't have clockworkmod installed and so when I tried to install update.zip as per the above post, it comes up with 'E:Failed to verify whole-file signature' error message and aborts.
Again, a complete... you get the picture...
So, I'm slightly frustrated with it to say the least and was wondering if any of you intelligent types could either point me in a suitable direction that doesn't involve the bin. Or a window...
Many thanks in advance.
Help
Locobox said:
Hi all!
I finally managed to ROOT an aPad M701 using z4Root.apk
Now I want to make an image of my entire ROM tablet, I've heard that under the ROM manager app is a tool called "Flash ClockworkMod Recovery" that has to be installed in order to make a full ROM backup.
The problem is that everytime I try to install it a screen pops out telling me to choose from the list my model of phone (I'm on an aPad tablet), since I'm not on a phone, I'm unable to continue with the process!
Any method or workaround for installing Flash ClockworkMod Recovery on Haipads/aPads M701?
Thanks in advance for the help.
Click to expand...
Click to collapse
How were you able to root your apad with Z4? I was not able to find the setting to activate the USB Debugging?
Thanks,
~b
is there development in the forums for the Apad line? im looking at getting a m702 the next 1 up, well i want to find a tablet rom maybe alowing me to run gingerbread on it,
any help?
ljohnso16 said:
is there development in the forums for the Apad line? im looking at getting a m702 the next 1 up, well i want to find a tablet rom maybe alowing me to run gingerbread on it,
any help?
Click to expand...
Click to collapse
I'm not sure if this of help to you, but I have a M701 2Gb (probable fake version), I've messed around with the basics on my exploring Android type thread:
http://forum.xda-developers.com/showthread.php?t=1004824
I've put recovery on both 2.1 and 2.3 roms (need different versions). Any other q's then let me know, I don't know much yet but learning the best i can.
A very useful place for info on the M701 is here:
http://www.androidtablets.net/forum/groups/11-haipad-m701-m701-r.html
Hi Guys!
Newbie here. I have root my phone I have installed busybox from Google Play. I want to update my busybox to 1.21 so I installed it. I have launched the application and then clicked install. I have chosen "Normal" for normal installation. Then I tried installing the busybox into "/sdcard/busyboxfree/" to see if it would run so I entered "/sdcard/busyboxfree/" to the installation path after selecting "Normal" rather than "Smart". And then an error occured saying my su binary was not found. And then I tried opening a adb session and typed "su" (screenshot attached). I can see the SU app grant superuser permission for adb but the adb shell got stucked (see screenshot). So I tried navigating to /system/bin/ and /system/xbin/ to search for the su binary but I can't find it. I also lost some sh commands like "ls" and "rm" so I am using the busybox to do those commands. I can use the busybox so I suppose it is still in my system.
I have done some restoration such as Factory reset / Wipe Data, and restoring userdata using recovery mode (I don't have CWM so stock recovery). And then I tried rooting it again using the same process I have made rooting it before but now it is not working, I can't get the root back. So I decided to ask the huge developer community and experts to consult what to do about this. :victory:
But I have followed instructions from a post at XDA. I have dumped the mtd6 "recovery" and mtd11 "system" before I did the busybox installation (see screenshot mtd.png). Is this enough to restore things back? How do I flash these dumped images? I will be attaching a link to download the dumped images.
My question is, is there a way to gain SU permissions (root)? Do I just need to push/replace/configure/etc binaries or files? Any help will be appreciated. Thanks!
Click to expand...
Click to collapse
My phone is a re-branded phone from CloudFone. Model is Excite 350g. Original Phone model is "Mobistar Touch Cream 350".
Downloads
System Dump Image
Recovery Dump Image
Links:
Rooting Process for CloudFone Excite 350g by mrichiem
I bought a phone (ZTE 2050) that has next to nothing as far as development goes. I have tried to install TWRP recovery but it had never actually worked. I have tried using various tools that port recovery to MTK devices. None of them have worked. I have been able to achieve root through Magisk. However, when I do, I no longer have the stock recovery either. There are several other problems that happen as well, but nothing I cannot work around. What could I be doing that is causing me to lose recovery? The chipset is MTK6771 and it is an ARM-V8 64 bit and it is running Android 9. Literally the only things I'm able to find online regarding this phone is the sites that I believe only copy and paste from other phones whether the root method actually works out not. Almost everything tells me to use MTK Tool but that definitely doesn't work. I have issues with Smart Phone Flash Tool working as well despite all drivers being installed correctly. The only way I have been able to achieve root is through unlocking the Bootloader and flashing. And even though I follow the instructions on commands, I still lose the stock recovery. Any help would be greatly appreciated.
Reflash phone's stock ROM.
xXx yYy said:
Reflash phone's stock ROM.
Click to expand...
Click to collapse
I have flashed the stock system at least 50 times by now. I have tried flashing everything in different orders as well. When I have root, it always removes the recovery. When I open my file manager, I use Solid Explorer, it tells me there is no root file system. I have tried other root file managers as well. They all tell me the same thing.
Android is rooted if su cmdlet is present in Android's filesystem
I've got a $100 Chinese MTK phone and the one redeeming feature is that once the bootloader is unlocked, you can fastboot over USB (bootstrap).
I used SP flash tool to backup the ROM and WwR_MTK to extract the partitions allowing me to make my own custom recovery to boot with fastboot. Briefly, I found a twrp recovery online for another MTK phone and just played around with zImage & initrd.
Shell commands, dmesg, cat /proc/partitions & blkid on the phone come in handy to track down in partition layout. No need to flash anything so don't get issues with /system/bin/install-recovery.sh
xXx yYy said:
Android is rooted if su cmdlet is present in Android's filesystem
Click to expand...
Click to collapse
I got it to hang on to the stock recovery. However, the bootloader remains unlocked. If I lock it again in fastboot, it will not allow me to boot the phone. When I try to flash vbmeta, it tells me there is no such file on the system.
xdabookam said:
I've got a $100 Chinese MTK phone and the one redeeming feature is that once the bootloader is unlocked, you can fastboot over USB (bootstrap).
I used SP flash tool to backup the ROM and WwR_MTK to extract the partitions allowing me to make my own custom recovery to boot with fastboot. Briefly, I found a twrp recovery online for another MTK phone and just played around with zImage & initrd.
Shell commands, dmesg, cat /proc/partitions & blkid on the phone come in handy to track down in partition layout. No need to flash anything so don't get issues with /system/bin/install-recovery.sh
Click to expand...
Click to collapse
I'll give that a shot. I just tried to open my root file system and it told me that BusyBox isn't installed. I thought I had read that BusyBox wasn't necessary with Magisk. Last time I tried to install a BusyBox, it screwed the whole system up. Is there one you would suggest? I've seriously messed with this phone 1000x's now and it's made me giggle shy to do anything to it at the moment.
Some devices have 'toolbox' or 'toybox' as a limited replacement for busybox (ls -al /bin/ls should reveal what binary the sym link points to).
I've used the ru.meefik.busybox app from the play store.
finnroth69 said:
the whole system up. Is there one you would suggest? I've seriously messed with this phone 1000x's now and it's made me giggle shy to do anything to it at the moment.
Click to expand...
Click to collapse
xdabookam said:
Some devices have 'toolbox' or 'toybox' as a limited replacement for busybox (ls -al /bin/ls should reveal what binary the sym link points to).
I've used the ru.meefik.busybox app from the play store.
Click to expand...
Click to collapse
xdabookam said:
Some devices have 'toolbox' or 'toybox' as a limited replacement for busybox (ls -al /bin/ls should reveal what binary the sym link points to).
I've used the ru.meefik.busybox app from the play store.
Click to expand...
Click to collapse
Ok, yeah I just checked it and it says toybox.
xdabookam said:
Some devices have 'toolbox' or 'toybox' as a limited replacement for busybox (ls -al /bin/ls should reveal what binary the sym link points to).
I've used the ru.meefik.busybox app from the play store.
Click to expand...
Click to collapse
I just installed the BusyBox and my whole system froze and started acting up.
xdabookam said:
Some devices have 'toolbox' or 'toybox' as a limited replacement for busybox (ls -al /bin/ls should reveal what binary the sym link points to).
I've used the ru.meefik.busybox app from the play store.
Click to expand...
Click to collapse
I rebooted and it started acting ok once again. When I tried to open my file manager to access to root file system, this is still the message I got even though I have not uninstalled the BusyBox.
xdabookam said:
Some devices have 'toolbox' or 'toybox' as a limited replacement for busybox (ls -al /bin/ls should reveal what binary the sym link points to).
I've used the ru.meefik.busybox app from the play store.
Click to expand...
Click to collapse
I just opened the BusyBox app and it says it isn't installed even though I have not uninstalled it either.
cm
xXx yYy said:
Android is rooted if su cmdlet is present in Android's filesystem
Click to expand...
Click to collapse
"cmdlet" not found. Yet Magisk is installed and I am able to access root.
If you can successfully apply su ( read: Switch User cmdlet ) then it got installed by whatever method.
finnroth69 said:
I just opened the BusyBox app and it says it isn't installed even though I have not uninstalled it either.
Click to expand...
Click to collapse
Busybox is just a tool / binary executable command to replace missing
linux commands. You don't need it installed on the phone, just access to the binary to run commands in the shell (copy it from /data/app/....) - its statically linked so should run without issue in the shell.
xXx yYy said:
If you can successfully apply su ( read: Switch User cmdlet ) then it got installed by whatever method.
Click to expand...
Click to collapse
Ok, I understand that. What I don't understand is why I am now being told that vbmeta cannot be found and installed and my bootloader must remain unlocked. Or why I cannot install recovery without losing recovery.
xdabookam said:
Busybox is just a tool / binary executable command to replace missing
linux commands. You don't need it installed on the phone, just access to the binary to run commands in the shell (copy it from /data/app/....) - its statically linked so should run without issue in the shell.
Click to expand...
Click to collapse
I can't copy it it. It won't allow me into the root file system.
xdabookam said:
Busybox is just a tool / binary executable command to replace missing
linux commands. You don't need it installed on the phone, just access to the binary to run commands in the shell (copy it from /data/app/....) - its statically linked so should run without issue in the shell.
Click to expand...
Click to collapse
I can't copy it it. It won't allow me into the root file system.
xdabookam said:
Busybox is just a tool / binary executable command to replace missing
linux commands. You don't need it installed on the phone, just access to the binary to run commands in the shell (copy it from /data/app/....) - its statically linked so should run without issue in the shell.
Click to expand...
Click to collapse
I just installed another BusyBox and the system is running fine afterwards, but this is the message I get when trying to open the root file system.
xdabookam said:
Busybox is just a tool / binary executable command to replace missing
linux commands. You don't need it installed on the phone, just access to the binary to run commands in the shell (copy it from /data/app/....) - its statically linked so should run without issue in the shell.
Click to expand...
Click to collapse
I pulled up the currently installed binary installed through shell.
Here's where I'm at. I've got the system to give me the Mount /System option in recovery, now i just need assistance getting the build.prop pulled to my PC. What's the procedure for pulling the build.prop from the Android to PC via ADB while the system is mounted in recovery? Why am I getting one of these two ADB errors?
Error 1: Connect failed: closed.
error 2: Failed to get feature set: no devices or emulators
OR, am I approaching it wrong?
Thanks in advance,
K0mraid3
you dont need to be in recovery to do it via adb....
adb pull /system/build.prop
that will pull it to where evr you run the adb command
which would be
C;\adb more than likely
or you can choose a destination with
adb pull /system/build.prop c:\buildprop
if you create a folder called "buildprop" in the root directory of c:\
at least thats how i remember doing it many years ago, ive been away for a while at her majesties pleasure, so i cant try it currently as im not rooted
gav83collins said:
you dont need to be in recovery to do it via adb....
adb pull /system/build.prop
that will pull it to where evr you run the adb command
which would be
C;\adb more than likely
or you can choose a destination with
adb pull /system/build.prop c:\buildprop
if you create a folder called "buildprop" in the root directory of c:\
at least thats how i remember doing it many years ago, ive been away for a while at her majesties pleasure, so i cant try it currently as im not rooted
Click to expand...
Click to collapse
Thanks, so far, its still for some reason denying me permission when OS is booted. So i just cant quite figure out where im supposed to execute these commands, is my issue. I can boot directly to BL from recovery menu, but i can also mount system. i think maybe i need sto send command for r/w.. will try that now.
Another question, when i mount /system in recovery, does that carry over on boot?
no you can re mount system via adb though
Code:
$ adb shell
$ su
# mount -o rw,remount /system
gav83collins said:
no you can re mount system via adb though
Code:
$ adb shell
$ su
# mount -o rw,remount /system
Click to expand...
Click to collapse
1.Needs root for this command. If he have rooted device then why so much trouble needed. Simply use root explorer to copy
2.Since long Samsung have removed system from proc/mounts still magisk system_root can be used
3.Even with system in mounts you can't do system rw on S22 because of Samsung have implemented extra layer of protection. Even not with magisk system_root too
Indeed as of now there is no method available to make stock system/vendor/product/odm rw on S22 even with root access.
4.To copy file from system rw mount not needed, ro is fine
dr.ketan said:
1.Needs root for this command. If he have rooted device then why so much trouble needed. Simply use root explorer to copy
2.Since long Samsung have removed system from proc/mounts still magisk system_root can be used
3.Even with system in mounts you can't do system rw on S22 because of Samsung have implemented extra layer of protection. Even not with magisk system_root too
Indeed as of now there is no method available to make stock system/vendor/product/odm rw on S22 even with root access.
4.To copy file from system rw mount not needed, ro is fine
Click to expand...
Click to collapse
im yet to root my device so i cant test but what about
Code:
adb root
adb disable-verity
adb reboot
Then
Code:
adb root
adb remount
gav83collins said:
im yet to root my device so i cant test but what about
Code:
adb root
adb disable-verity
adb reboot
Then
Code:
adb root
adb remount
Click to expand...
Click to collapse
Do you got what I meant?
leave it.
dr.ketan said:
WTF
Do you got what I meant?
leave it.
Click to expand...
Click to collapse
look, there is no need for condescension and bad language, a simple "no" would have sufficed
Lol not meant to hurt you! but on which planet WTF is bad language
Here search WTF on xda
dr.ketan said:
1.Needs root for this command. If he have rooted device then why so much trouble needed. Simply use root explorer to copy
2.Since long Samsung have removed system from proc/mounts still magisk system_root can be used
3.Even with system in mounts you can't do system rw on S22 because of Samsung have implemented extra layer of protection. Even not with magisk system_root too
Indeed as of now there is no method available to make stock system/vendor/product/odm rw on S22 even with root access.
4.To copy file from system rw mount not needed, ro is fine
Click to expand...
Click to collapse
So my device is strange. It doesn't have root, but it indeed shows options in recovery to apply updates from ADB, SD Card aswell as boot directly to BL and to Mount /System, but when I'm booted, the OS is denying me permission to "Su" . I have verified that USB debugging is activated. So I'm trying to see if there's a way to pull the build.prop from Recovery since the Mount /System option is available, but my computer refuses to recognize the device in while in recovery, but easily finds it in Download, BL mode. No FRP lock. No accounts on device. But also no option to unlock bootloader. This device in particular is/was a development sample so I have no clue what the current state of the bootloader etc is in terms of being unlocked prior to me working on it.
It'd also worth noting that this device was loaded with Android 11 when I received it. I'm not kidding. So idk what's going on with this FrankenGalaxy
K0mraid3 said:
It'd also worth noting that this device was loaded with Android 11 when I received it. I'm not kidding. So idk what's going on with this FrankenGalaxy
Click to expand...
Click to collapse
K0mraid3 said:
So my device is strange. It doesn't have root, but it indeed shows options in recovery to apply updates from ADB, SD Card aswell as boot directly to BL and to Mount /System, but when I'm booted, the OS is denying me permission to "Su" . I have verified that USB debugging is activated. So I'm trying to see if there's a way to pull the build.prop from Recovery since the Mount /System option is available, but my computer refuses to recognize the device in while in recovery, but easily finds it in Download, BL mode. No FRP lock. No accounts on device. But also no option to unlock bootloader. This device in particular is/was a development sample so I have no clue what the current state of the bootloader etc is in terms of being unlocked prior to me working on it.
Click to expand...
Click to collapse
These options are normal in stock recovery and can be used only for flashing official zip (OTA), To have root access on your recovery, you needs custom one (TWRP) which is in development stage on S22
Without twrp, You needs to root device (must have oem unlock option in development option) to access system files while you are booted to android.
Android 11 on S22? Can you show me screenshot of settings - about phone - software info?
dr.ketan said:
These options are normal in stock recovery and can be used only for flashing official zip (OTA), To have root access on your recovery, you needs custom one (TWRP) which is in development stage on S22
Without twrp, You needs to root device (must have oem unlock option in development option) to access system files while you are booted to android.
Android 11 on S22? Can you show me screenshot of settings - about phone - software info?
Click to expand...
Click to collapse
Thanks for the clear answer, that's kind of what I'm working on is trying to gain root access, but like you said, I need oem unlocking, which isn't on this device. So I'm trying to find a backdoor/vulnerability that will take me even one step closer to atleast finding a way to set ro.secure. prop. Something VERY interesting I did find, is that if you put the device to Debug medium or high via device keystring activity, and play with the key combos, you can get booted into a mode called RDX, if you plug it into your dev system with the right drivers, it's treats the phone as if it were a Disk and shows a bunch of VZW upgrade software ment for PCs. I've installed it but haven't got it working quite yett.
No idea what you have shown in screenshot, I'd asked something else.
dr.ketan said:
No idea what you have shown in screenshot, I'd asked something else.
Click to expand...
Click to collapse
Maybe Heindall will give me better results. I just refuse to believe the manufacturers have outsmarted us all on this.