[Q] root encrypted device - Transformer TF300T Q&A, Help & Troubleshooting

Hi,
work the method described in http://forum.xda-developers.com/showthread.php?t=1704209 also if my pad is encrypted?
Thanks
Midyr

Midyr said:
Hi,
work the method described in http://forum.xda-developers.com/showthread.php?t=1704209 also if my pad is encrypted?
Thanks
Midyr
Click to expand...
Click to collapse
I don't think so, I wouldn't try it. Just unencrypt it for a few minutes to root.

hm, what a pity!
thanks
Midyr

I would GUESS that /system isn't touched when "encrypting". Only /data et other stuff.
So my GUESS is that it would work just the same.

/dev/void said:
I would GUESS that /system isn't touched when "encrypting". Only /data et other stuff.
So my GUESS is that it would work just the same.
Click to expand...
Click to collapse
One of the first steps in miloj's root method is to push a file to /data/local, so it probably wouldn't work.

OK, then there ist really no chance
BTW: Is there any documentation about the enctryption-function?
Thanks for help
Midyr

prototype7 said:
One of the first steps in miloj's root method is to push a file to /data/local, so it probably wouldn't work.
Click to expand...
Click to collapse
Ouch. I totally forgot about that part.
Is /data/local encrypted aswell (because that seems a bit redundant)?
I guess it's both easier and safer to encrypt the whole /data partition, so I guess it may be.

Related

Android symlink errors system/xbin/su PLEASE HELP

I have been trying to for over a week in the captivate forum to get ANYONE to try and help me and so far no one will. So i'm really hoping someone will take the time, i will PAY YOU UP FRONT over paypal to help me. I am DEAD SERIOUS.
Have a captivate, but this problem is not exclusive to this phone. This error has happened on just about any/every android phone there is.
Phone was working fine, have been putting any and all custom roms on that i wanted, but went to install a new custom rom (cog4), and it fails every single time at system/xbin/su. Now ANY rom i install (custom), gives me that same error. NO CUSTOM ROM WILL INSTALL. THEY ALL FAIL. I have flashed back to stock a million times, wiped, re-partitioned the sd card, master cleared, and done all of those in every combination possible. The ONLY rom i can put on here is the one i had RIGHT before this problem started (cog3.04). Only roms that can be flashed via odin will go on my phone now. All zip files fail.
I am not a noob and know my way around a computer. I promise if someone tries to help me i will be very prompt in my responses and will try ANYTHING that you ask me to. I have been googling for over a week hours a day, i am never gonna resolve this issue unless someone with the know-how helps me Every time this topic is brought up on any forum on the internet, the problem never gets solved and it fades away....there is no answers out there. Someone who knows this stuff is my only hope
I will pay you to help me even if your troubleshooting does not work
Just out of curiosity, did you open Rom Manager once you installed it to grant it superuser rights? Also, make sure you Click the top link in Rom Manger and choose your phone. "Flash ClockworkMod Recovery"
Yes tim i have done that.
I sent you a private message -- here is the same:
Have you tried adb root - and then from / rm -rf * and see if you can wipe all clean. Ofcourse if the issue is the partition, then this won't help. Also I have never tried this - as this has never been an issue for me.
http://modmymobile.com/forums/403-m...5-fix-root-eclair2cliq-beta-1-08-06-10-a.html
could something like this work for me?
JoelParke said:
I sent you a private message -- here is the same:
Have you tried adb root - and then from / rm -rf * and see if you can wipe all clean. Ofcourse if the issue is the partition, then this won't help. Also I have never tried this - as this has never been an issue for me.
Click to expand...
Click to collapse
I am definitely rooted and have su permissions, but it will not let me access SYSTEM from recovery or when the phone is on. Says access denied.
xsteven77x said:
http://modmymobile.com/forums/403-m...5-fix-root-eclair2cliq-beta-1-08-06-10-a.html
could something like this work for me?
Click to expand...
Click to collapse
I read that post but the update-script in Cog4 doesn't have those lines. You could in theory edit the script so that it just has those three lines but I'm not sure that would be sufficient to install Cog4. That may be a question for DG.
Do you have the root explorer app?
timbrendelaz said:
I read that post but the update-script in Cog4 doesn't have those lines. You could in theory edit the script so that it just has those three lines but I'm not sure that would be sufficient to install Cog4. That may be a question for DG.
Do you have the root explorer app?
Click to expand...
Click to collapse
Yes i do 10char
xsteven77x said:
http://modmymobile.com/forums/403-m...5-fix-root-eclair2cliq-beta-1-08-06-10-a.html
could something like this work for me?
Click to expand...
Click to collapse
Not sure as this looks like a patch and specifically asks for no wipe. Also my knowledge is limited as to what harm you can do that will make the phone unusable -- BUT you are already into that realm . Perhaps someone with deeper specific experience can answer this????
Open Root Explorer and remount R/W. Switch to the system partition and look at the permissions on bin and xbin. They should both be rwxr-xr-x
timbrendelaz said:
Open Root Explorer and remount R/W. Switch to the system partition and look at the permissions on bin and xbin. They should both be rwxr-xr-x
Click to expand...
Click to collapse
K will report back.
Also it looks like the update.zip file is long gone....
JoelParke said:
Also it looks like the update.zip file is long gone....
Click to expand...
Click to collapse
??? 10 chars
xsteven77x said:
I am definitely rooted and have su permissions, but it will not let me access SYSTEM from recovery or when the phone is on. Says access denied.
Click to expand...
Click to collapse
using adb remount will set the /system partition as read/write. This may help.
xsteven77x said:
??? 10 chars
Click to expand...
Click to collapse
I attempted to look at the original link your posted and tried to download the patch -update.zip - which was missing on the thread. Sorry this wasn't clear.
JoelParke said:
using adb remount will set the /system partition as read/write. This may help.
Click to expand...
Click to collapse
I have been doing that within sgs tools, not the same thing?
timbrendelaz said:
Open Root Explorer and remount R/W. Switch to the system partition and look at the permissions on bin and xbin. They should both be rwxr-xr-x
Click to expand...
Click to collapse
Having alot of trouble getting my root explorer installed. Keeps saying parsing error UGH COME THE **** ON!!!!
JoelParke said:
I attempted to look at the original link your posted and tried to download the patch -update.zip - which was missing on the thread. Sorry this wasn't clear.
Click to expand...
Click to collapse
Oh ok sorry i didnt understand. Ty for trying regardless though.
xsteven77x said:
Having alot of trouble getting my root explorer installed. Keeps saying parsing error UGH COME THE **** ON!!!!
Click to expand...
Click to collapse
LOL, of course......
If it doesn't install, try installing Terminal Emulator from the Market
Ok so inside of the system folder they both have the permissions set to what you wrote.... .
There is only a bin in the folder right before the system folder...should there be an xbin there too?

Is there another way to root ICS 9.2.2.3 ?

Is there already a method on the root 9.2.2.3 ?
aga37 said:
Is there already a method on the root 9.2.2.3 ?
Click to expand...
Click to collapse
Perhaps downgrade your ROM to an earlier version. Someone has done it with HC.
http://forum.xda-developers.com/showthread.php?t=1400532
[Edit] Ignore me. Apparently you cannot go back to a lower version number.
Bump
aga37 said:
Is there already a method on the root 9.2.2.3 ?
Click to expand...
Click to collapse
aga37 said:
Is there already a method on the root 9.2.2.3 ?
Click to expand...
Click to collapse
have you tried this
http://forum.xda-developers.com/showthread.php?t=1515470
TNS201 said:
have you tried this
http://forum.xda-developers.com/showthread.php?t=1515470
Click to expand...
Click to collapse
It has been patched up with this update
wolf849 said:
It has been patched up with this update
Click to expand...
Click to collapse
confirmed
if you have a B50 or B60 TF101 you can try my way. this will restore it back to 9.2.1.11 and then OTA 9.2.3.3
http://forum.xda-developers.com/showthread.php?t=1524302
chadster214 said:
if you have a B50 or B60 TF101 you can try my way. this will restore it back to 9.2.1.11 and then OTA 9.2.3.3
http://forum.xda-developers.com/showthread.php?t=1524302
Click to expand...
Click to collapse
Problem is that 9.2.2.3 update came for tf101g and that means SBK3 device, therefore root by nvflash will not make the trick...
P.S. As far as we are talking about 3g devices
Is it possible to flash recovery.img on device via adb ? (Fastboot) Then boot into CWM and flash a rooted rom ?
Sent from my GT-I9100 using XDA
Nick502 said:
Is it possible to flash recovery.img on device via adb ? (Fastboot)
Click to expand...
Click to collapse
The bootloader does support the fastboot protocol (and some obscure methods of booting a kernel via JTAG), but it's locked down to the point that you can't even get fastboot to recognize the device.
So no luck there
ViperMod is your answer I believe
I've not had to root since any version of ICS, but many are have success with ViperMod: http://forum.xda-developers.com/showthread.php?p=21009605
You might have to drop back to a 9.2.2.17 or 19 but there are lots of roms out there that are still on that version. I would give it a try on the 9.2.2.3 though, my guess would be it will work. cheers.
chadcspencer said:
I would give it a try on the 9.2.2.3 though, my guess would be it will work. cheers.
Click to expand...
Click to collapse
It doesn't work
I tried with my TFT101G build 9.2.2.3 but didn't work!
OK, so to sum it up:
1. SUID /proc/<pid>/mem write has been patched in this release (aka 9.2.2.3) therefore mempodroid exploit and basing on it viperMod is useless
2. qEmu vulnerability in /data/local.prop is also patched up so TPsparkyroot will also fail.
3. The location of backed up files and temp storage have been shifted out from data therefore all rooting tools connected with ASUS backup app will not do the trick.
4. Jumping back to previous software is unachievable without root.
So I ask you to post ONLY methods that are not listed above.
(However I think that we have to wait for next linux Local Privilage Escalation bug to be discovered in order to get rooted)
Cheers
P.S. Sorry for any mistakes English is not my native.
ICS 9.9.23G
I have a question is 9.2.23 ics available for all transformers? When I got my update it was 9.2.17. Then I used vipermod to root and voodoo root keeper.do I need to temp unroot to receive this update?
thunderman98 said:
I have a question is 9.2.23 ics available for all transformers? When I got my update it was 9.2.17. Then I used vipermod to root and voodoo root keeper.do I need to temp unroot to receive this update?
Click to expand...
Click to collapse
OTA is only for TF101G. You can install firmware pack from ASUS website through custom recovery, but I do not see any point of doing that.
Any news ? Anyone succeeded in rooting 9.2.2.3??????
Thanks in advance
hearts king101 said:
Any news ? Anyone succeeded in rooting 9.2.2.3??????
Thanks in advance
Click to expand...
Click to collapse
Nope, I've only achieved /data and /cache readwrite access but nothing more Unless you know any thing that can be done in that situation.
wolf849 said:
Nope, I've only achieved /data and /cache readwrite access but nothing more Unless you know any thing that can be done in that situation.
Click to expand...
Click to collapse
If you can write to arbitrary locations on /data try dropping a /data/local.prop with 'ro.kernel.qemu=1' inside (without quotes), reboot and then issue "id" through adb shell to check if adb is running as root.
If it works, ViperMod can be adapted almost painlessly to push su, Superuser.apk and busybox with the correct permission bits
sbiriguda said:
If you can write to arbitrary locations on /data try dropping a /data/local.prop with 'ro.kernel.qemu=1' inside (without quotes), reboot and then issue "id" through adb shell to check if adb is running as root.
If it works, ViperMod can be adapted almost painlessly to push su, Superuser.apk and busybox with the correct permission bits
Click to expand...
Click to collapse
Unfortunately I've tried that and than I came to a conclusion that 'ro.kernel.qemu=' has been shifted... Try read build.prop on /system and you will find it there, so /data write does nothing for now
EDIT:
Nonetheless, I have rw access to /cache where dlpkgfile is held, so maybe it is possible to do a downgrade of firmware through that hole.
EDIT2:
BTW, I did it by flashing TW 9.2.2.3 firmware on to WW 9.2.2.3 through EP101_SDUPDATE (or similar).
Than:
adb mv /data/local/tmp /data/local/tmp.bak
adb shell ln -s /cache /data/local/tmp
adb rebbot
After that /data becomes readwrite
EDIT3:
There is also one more question: where is held /tmp partition needed to repack the blob maybe by accessing it and pushing blob we can manually force its update.

Stock 'libart.so'

Hi guys,
Can anyone please provide me stock 'libart.so'? I used the whatsapp ART fix for it and now can't update to 4.4.1 because of modified libart.so.
Thanks.
Nvm. Someone helped me in the general forum. Here is the link to it:
http://forum.xda-developers.com/showpost.php?p=48191317&postcount=190
thegr8anand said:
Nvm. Someone helped me in the general forum. Here is the link to it:
http://forum.xda-developers.com/showpost.php?p=48191317&postcount=190
Click to expand...
Click to collapse
Hello,
have you solved this? How did you put libart.so stock?
minov1972 said:
Hello,
have you solved this? How did you put libart.so stock?
Click to expand...
Click to collapse
Remove the hacked file, copy the original? Needs root in Android or a custom recovery, however.
a hammerhead wrote this.
beekay201 said:
Remove the hacked file, copy the original? Needs root in Android or a custom recovery, however.
a hammerhead wrote this.
Click to expand...
Click to collapse
despite the root tells me permission denied!
minov1972 said:
despite the root tells me permission denied!
Click to expand...
Click to collapse
Well i pushed the file to device in adb mode.
Does anyone have the stock libart-complier.so too?
minov1972 said:
despite the root tells me permission denied!
Click to expand...
Click to collapse
You need to remount the system partition in read-write mode. By default it's set to read-only.

sdcard permissions messed up?

Ive factory reset several times now, I've reflashed the android l preview image several times, and flashed two 5.0 roms over it even, and i even tried a multiboot with cm11. My device can't take pictures, video, basically anything to do with the camera doesnt work. Pictures seem to take, but don't save. Video or any panorama crashes the camera, and the error logs show something about permission denied to the files they are trying to create. How can i fix this?
Did you copy all your data back to the phone via recovery?
Usually for L, you run
su
restorecon -FR /data/media/0
...which is mentioned in his sticky lots of times.
But If you copied all sdcard data back to your phone via recovery, there's a different approach
rootSU said:
Did you copy all your data back to the phone via recovery?
Usually for L, you run
su
restorecon -FR /data/media/0
...which is mentioned in his sticky lots of times.
But If you copied all sdcard data back to your phone via recovery, there's a different approach
Click to expand...
Click to collapse
I tried that one, it did nothing and camera still acted up. I've tried every app on the store. Nothing seems to be allowed to write to DCIM, even though I can create files with a normal file manager just fine.
rootSU said:
Did you copy all your data back to the phone via recovery?
Usually for L, you run
su
restorecon -FR /data/media/0
...which is mentioned in his sticky lots of times.
But If you copied all sdcard data back to your phone via recovery, there's a different approach
Click to expand...
Click to collapse
I just tried creating a file inside the camera folder inside DCIM and permission was denied. How could I fix that?
dreamwave said:
I tried that one, it did nothing and camera still acted up. I've tried every app on the store. Nothing seems to be allowed to write to DCIM, even though I can create files with a normal file manager just fine.
Click to expand...
Click to collapse
Using a root explorer, go to /data/media/0/Download and set all the permissions to read, write and execute.
Then hopefully you can download stuff.
Please check that. If that works, I'll let you know the next step
rootSU said:
Using a root explorer, go to /data/media/0/Download and set all the permissions to read, write and execute.
Then hopefully you can download stuff.
Please check that. If that works, I'll let you know the next step
Click to expand...
Click to collapse
I can already download stuff. Is it a common problem with L for this to happen? I've looked it up and found little to nothing.
rootSU said:
Using a root explorer, go to /data/media/0/Download and set all the permissions to read, write and execute.
Then hopefully you can download stuff.
Please check that. If that works, I'll let you know the next step
Click to expand...
Click to collapse
I realize I just went full retard thanks to looking in the camera for permission. I had earlier set permissions with chmod from recovery for the DCIM directory to 777, but not the Camera directory within. Thanks for helping, though!
dreamwave said:
I realize I just went full retard thanks to looking in the camera for permission. I had earlier set permissions with chmod from recovery for the DCIM directory to 777, but not the Camera directory within. Thanks for helping, though!
Click to expand...
Click to collapse
One problem I have consistently had however is that my launcher and default camera app are never remembered. How can I fix this?
dreamwave said:
I can already download stuff. Is it a common problem with L for this to happen? I've looked it up and found little to nothing.
Click to expand...
Click to collapse
No it's uncommon. I've only sewn it for people using recovery or adb to push and pull sdcard folders.
Download and flash this zip via recovery.
http://forum.xda-developers.com/attachment.php?attachmentid=2849968&d=1405300107
and it seems that for any kind of panorama or photosphere it still crashes
they crash with an event trace of java.lang.NullPointerException: attempt to invoke virtual method 'void java.io.FileWriter.close()' on a null object reference
at
com.google.android.apps.lightcycle.panoramamodule.stopcapture(panoramamodule.java:802
etc
etc
etc
Its permissions, we know that. Please flash the fix I posted before anything else.
rootSU said:
Its permissions, we know that. Please flash the fix I posted before anything else.
Click to expand...
Click to collapse
Ok, so pushing it to the sd with adb won't break even more permissions?
dreamwave said:
Ok, so pushing it to the sd with adb won't break even more permissions?
Click to expand...
Click to collapse
Why would you need to do that? You can download it direct to your phone.
rootSU said:
Why would you need to do that? You can download it direct to your phone.
Click to expand...
Click to collapse
ok, I flashed it and my phone is rebooting
dreamwave said:
ok, I flashed it and my phone is rebooting
Click to expand...
Click to collapse
Cross your fingers.
rootSU said:
Why would you need to do that? You can download it direct to your phone.
Click to expand...
Click to collapse
thanks so much, that fixed it completely!
dreamwave said:
thanks so much, that fixed it completely!
Click to expand...
Click to collapse
No problem.
The adb (or TWRP MTP) only seems to break permissions if you're pushing folders. Pishing individual files should be fine.
rootSU said:
Cross your fingers.
Click to expand...
Click to collapse
is this problem new to android l or has it been around a while? I'll also admit I do a lot of adb push/pull/commands and such, and for a lot of the time need to because I only have a wired connection with my computer at school, is there a way to avoid this problem in the future?
dreamwave said:
is this problem new to android l or has it been around a while? I'll also admit I do a lot of adb push/pull/commands and such, and for a lot of the time need to because I only have a wired connection with my computer at school, is there a way to avoid this problem in the future?
Click to expand...
Click to collapse
Its not related to L at all. Files should be fine to push. Its just folders I think that cause the issue.

[Rom][Pre-Rooted][7.0][G920v] Offical nougat pre rooted rom

most of members the old method didn't work with him so i decide to make a pre rooted rom
*Do It AT YOUR OWN RISK!* I am not responsible for ANY damage to your device
Here is the video in how to install it all link that you will need it i put it in description of the video
please don't forget to hit thanks it takes 5 days from me to upload it
[YOUTUBE]
https://www.youtube.com/watch?v=NS0Ggcq0TfU[/YOUTUBE]
also you can open the video from here
https://www.youtube.com/watch?v=q8OT36kfo24
Tears of Joy . Woks Perfect.. Thank you @faw_wal
DDwhite said:
Tears of Joy . Woks Perfect.. Thank you @faw_wal
Click to expand...
Click to collapse
You Welcome
Many thanks faw_wal
I could place it in writing. the steps to follow
I do not know which file I should download first.
Additional I would like to know if you could share a script or a way to remove verizon apps, and keep a clean phone as if it were a total samsung
Thanks for this faw_wal
zpeady said:
Many thanks faw_wal
Click to expand...
Click to collapse
Enjoy
jotademanuel said:
I could place it in writing. the steps to follow
I do not know which file I should download first.
Additional I would like to know if you could share a script or a way to remove verizon apps, and keep a clean phone as if it were a total samsung
Click to expand...
Click to collapse
I'm sorry but it's a lot of steps to write it follow the video if video show to you black screen tonight i'm gonna to fix this problem
no-go
Tried many times, unable to get past the mounting of /system. Hard lock-up.
Edit: Had root on 7.0 finally. Looked like I was using the wrong sboot. I have too many...
Note: Tried to update superSU after I had everything how I wanted it. Lost root. Had to start over. Use caution...
I have gotten my phone rooted thanks for your help.
Now we need to find a way to bypass the system rw,remount freeze, which I think is being controlled by smu_protection or something like that.
EvilRubberDuck said:
Thanks for this faw_wal
Click to expand...
Click to collapse
You Welcome
AndroidFan16 said:
I have gotten my phone rooted thanks for your help.
Now we need to find a way to bypass the system rw,remount freeze, which I think is being controlled by smu_protection or something like that.
Click to expand...
Click to collapse
I think you phone now is rooted and you can mount system as rw just start adb
write adb shell then write su it will ask to get root from your device and then retry if doesn't work with download any explorer app like root explorer and you can edit system from it
lyphe said:
Tried many times, unable to get past the mounting of /system. Hard lock-up.
Click to expand...
Click to collapse
did you get root in super su ?
It works for the mount /system via adb? because I did it from root explorer but it freezes again, if works via adb, tell me, Im now in the 5.1.1 android rom version
does not work video ((
faw_wal said:
You Welcome
I think you phone now is rooted and you can mount system as rw just start adb
write adb shell then write su it will ask to get root from your device and then retry if doesn't work with download any explorer app like root explorer and you can edit system from it
Click to expand...
Click to collapse
Tried it on both, including
Code:
mount -o rw,remount /system
Freezing up
Especially with Amaze. Tried to write on the system partition and it hangs until I do a fresh reboot.
Has anyone tried if Samsung pay still works after root?
Ok, I'm in this nougat rom now, but the writable system still as a dream for us. I'll go back to the stock and enjoy of my Samsung apps instead of freezing my phone. Has someone knowledge about change the imei of this device? I want root for this. Or, if you know how to reboot the lollipop rooted rom correctly, can you explain me how?
Sent from my SM-G920V using XDA-Developers Legacy app
faw_wal said:
did you get root in super su ?
Click to expand...
Click to collapse
Edited original post. Finally got it working, but then lost it trying to update superSU binary.
ok i will corporate with @AndroidFan16 to figure what is the problem and when solve it i will publish it here
aceisaneight said:
Has anyone tried if Samsung pay still works after root?
Click to expand...
Click to collapse
Unsure if it "works" or not, as I never use it. However... It is bothering me to add my VISA-XXXX to Android Pay after boot. I'd say fairly good chance it does, simply because this root has thus far not touched /system for most of us. I do believe that is the red flag for SafetyNet/Pay (but I dunno. It does ask me however...)

Categories

Resources