Related
So I'm stuck at the command prompts. I have messed around with several things, and have also updated the usb driver correctly. Where I am stuck at is getting the adb usb.ini file to show up. I can run C: START adb update usb, and something runs for a split second, but after that I'm still unable to get the ini file to show up. Is there something wrong I'm doing?
just follow this tutorial, its noob proof. I hope this helps........
http://rootkindlefire.com/kindle-fire-root/how-to-root-kindle-fire/
its easier then the tut here
Well I've tried both tutorials but for some reason I must be doing something wrong, because I'm unable to get the usb driver.ini file to show up, so that it can be copied and pasted to the .android folder. I was advised that I had to do the adb update usb command in cmd, so i tried START adb update usb but all it does is run something for a split second then nothing shows up. I'm in the correct directory as far as I know, and I tried different directories for about 3 hours last night. I was able to successfully update the usb drivers through device manager, not sure if I was supposed to run the adb usb update before actually updating through device manager?
Then you didn't follow the instructions because the file would automatically be there if you did.
Movieaddict, you are a godsend. I did attempt to do this by watching the Youtube vid, but the link you sent me actually just showed pictures of what to do. It worked! Now I just have to figure out what to do now that it's rooted lol. Thanks so much!
jtb224 said:
Well I've tried both tutorials but for some reason I must be doing something wrong, because I'm unable to get the usb driver.ini file to show up, so that it can be copied and pasted to the .android folder. I was advised that I had to do the adb update usb command in cmd, so i tried START adb update usb but all it does is run something for a split second then nothing shows up. I'm in the correct directory as far as I know, and I tried different directories for about 3 hours last night. I was able to successfully update the usb drivers through device manager, not sure if I was supposed to run the adb usb update before actually updating through device manager?
Click to expand...
Click to collapse
Ifd u follow the tut i posted u really cant go wrong, seriously!
why when im trying to install the cm7 on the kindle in the cmd appears this error:
cp: can't stat ' /sdcard/log' : No such file or directory
Please help!
are you on recovery process? I have the same situation, when I try to instal CM7, I instaled recovery first, my be there's a mistake for "log" file, now I can't exit recovery. For I have changed boot mode "idme bootmode 0x5001", it still boot into recovery process when I try to restart it.
Please help.
i am in the beginning of the process and have this error :s
Sent from my Kindle Fire using Tapatalk
Soooo...I'm back again. Finished the root process, everything went hunky-dory until I actually tried to install something from the Android Market. Now everything force closes from Android Market, though my Amazon market still works. Also my games are force closing as well. The only way I can actually get back into the Market is if I clear all data to it, then can do searches. Also with my games, I am completely unable to get to work even after reinstalling them. Any ideas?
jtb224 said:
Soooo...I'm back again. Finished the root process, everything went hunky-dory until I actually tried to install something from the Android Market. Now everything force closes from Android Market, though my Amazon market still works. Also my games are force closing as well. The only way I can actually get back into the Market is if I clear all data to it, then can do searches. Also with my games, I am completely unable to get to work even after reinstalling them. Any ideas?
Click to expand...
Click to collapse
try installing app vending.apk
Sent from my Kindle Fire using Tapatalk
The way I fixed that problem for me was updating market apk
Sent from my Kindle Fire using xda premium
Since root has been obtained and an alternative launcher can be installed, as has been mentioned there is really no need to stay on 5.0.0 anymore. I would recommend updating to 5.0.1. However, this procedure can still be applied to 5.0.1 and hopefully it'll prevent any future updates. (As of writing it 5.0.1 is the latest).
The steps are basically as follows:
Enable ADB by going to Settings> Device Options. Keep tapping on the Serial Number field until the Developer options field appears.
Under Developer options Enable ADB
Hook the Fire up to your computer and do the following commands:
adb shell pm hide com.amazon.otaverifier
adb shell pm hide com.amazon.device.software.ota
adb shell pm hide com.amazon.settings.systemupdates
I don't know which of three is the magic one, But you can not longer go to device options > system update. It also never appears to pull down the update in the background.
Rivethread23 - good work and many thanks for this
I know that you have the original Fire 7 with no system update but I wanted to see if any of your commands will work on 5.01. My device is on 5.01 has been in aeroplane mode since purchase, I have been using OTG Ethernet for connectivity and I have not signed into Amazon. Google Play is installed - basically a standalone device on 5.01 with no association with Amazon.
After running the commands and the ADB shell gave a [True State] after each command. Rebooted the device:
System Updates now gives the following error message: [The requested action is not permitted. Check Parental controls settings and try again]. As my device is not associated with Amazon parental controls have not been configured - so I browsed to a few proxy sites and such to confirm no filtering on web browsing etc
I've tried various launchers from Play store and every time the default Fire Launcher kicks back in again.
SD Card issue is still there.
When you tried the System Update button did you get the same error message as me? If so, I wonder if the Adb Shell command to disable OTA works on 5.01 as well?
Update 1: [adb shell pm hide com.amazon.firelauncher] disables the default Amazon launcher. I picked another launcher at random from Google Play. Halo installed and it worked with the default launcher hidden, however using the minimise middle button on the device forces the Parental Control Popup to appear.
So it is possible to hide the default launcher on 5.01 using ADB but it is causing issues. We need a better work around.
Unfortunately this only blocks the update from occurring. I ran into another issue on the 5.0.0 tablet in that I can't get Google play store working. It just says cannot connect. So I don't know if one of the above things broke it. It was getting late so I went to bed. I'll keep plugging at it and see what I can do.
I might finally take both of mine out of the box today, can more people confirm this is working? @Rivethread23, did you get the play store sorted out?
Couldn't wait, dove in. On an out-of-box Fire, running 5.0.0, these do in-fact keep the OTA updates from firing. I have been online, installing apps and customizing the tablet for over an hour with many reboots, no prompts or attempts of an update.
With this, and ads disabled, and the play store turned on we have a usable tablet!
F-Droid works as well, just sideload their APK to get access to lots of software:
https://f-droid.org/repo/org.fdroid.fdroid_96150.apk
Still stuck on Play Store in 5.0.0 *not working* for now.....same problem as OP
I can confirm that the Google Play Services, Login Services, and Framework are (at least partly) working, even though the Play Store is not. I sideloaded Gmail, and it automatically had my info, and downloaded my email.
Wait, I'm confused. In 1 post you say play store is on and working, then you're saying it's not...
Aside from the play store, it sounds like everything else is working fine! Is that correct. I'm asking because I'm thinking about buying a 2nd one of these, only if I can have it working 100% the way I have it now with my tablet, just with the ability to use a different launcher.
With the original 5.0.0 firmware, if you prevented the OTA update to 5.0.1:
+Can change launcher
+Can write to SD from apps
-Can't get Play Store to work (so far, but can manually side-load GApps (Gmail, Hangouts, etc))
In the other thread, people that have gone to 5.0.1:
-Locked to amazon Launcher when using HOME button
-Manual SD writing is disabled
+Google Play Store can be installed and 90% of the GApps work
--------
The key to take away is that if you get another one, and you do the fix in this thread to prevent OTA updates, you can simply wait til everyone gets things fixed and figured out. You can safely use it and not worry about getting pushed to a firmware that might be even more locked down.
On the other hand, if you're not worried about OTA updates breaking stuff, and want a working store, go to 5.0.1 and follow SD_Shadow's instructions in his thread on that subject.
Hopefully root comes soon and we can fix all these problems properly, but until then it's kinda hit and miss depending on what version you got.
Hope that helps.
Thanks Tufkal was going to post something along those lines but you beat me to it.
Essentially you can prevent updates from further locking down the tablet. Who knows what future updates bring? I'll wait and update as thing warrant.
I have two one on 5.0.0 and another on 5.0.1. While I like being able to use the launcher of my choosing on 5.0.0, the working google store and updated amazon store and apps have me using the 5.0.1 one. I am keeping the other on 5.0.0 until development starts then I'll try my hand at making a ROM.
Your device that is on 5.0.0 Firmware have you signed into Amazon and associated your device? Or is it standalone like mine?
Was on Amazon for a day. Factory reset it and am using it sans Amazon. Mostly using the 5.0.1 one myself.
Yep same here. 5.01 with no amazon sign in.
I've been playing around with the launcher again. Tried changing the hardcoded buttons and also with ADB Shell am force-stop pm disable on com.amazon.firelauncher to stop dependent services, ie hard buttons. All to no avail.
root definitely needed for this
I figured out a way to access some hidden functions within the OS last night. Seeing where this leads after work today Apparently I can cast the screen and access the home function disabled in 5.0.1. Problem is the home function doesn't override the hard coding.
Most interesting is something called Prod and Devo Switch that give "Access Denied" when I try to activate it. Hmmmm........
Here's what I have discovered. It's easier done on 5.0.0 but can be done on 5.0.1. You'll need another launcher like Nova installed. Installed "Anycut" from the google store. It'll let you put a shortcut on the desktop for any "activity". There are alot of items there not normally accessible. You can cast to a Chromcast for example (it works). The reason you need another launcher is the Amazon launcher doesn't support shortcuts I guess as they don't appear. They appear on Nova's desktop when created.
Most interesting is a shortcut called "Prod and Devo Switch" which if you look at the info refers to the "Amazon Device Settings" app.. ( com.amazon.device.settings?). It's separate from the user settings. If you try to access it it will say "Access Denied" on 5.0.1. Or "Permission denied" on 5.0.0. Makes me wonder if what needs to happen the app needs some additional permissions to be run. I was looking through the list of permissions via ADB and there are a number of permission groups that are android.xxxxx. However there are only a few permission groups that are amazon.xxxxx one of which is amazon.permission-group.settings. Listing the settings in the group shows a large list. Maybe using ADB pm grant com.amazon.device.settings the correct permissions could unlock this? Thoughts?
Here's what I got from a logcat when I click on the shortcut in novalauncher:
I/ActivityManager( 454): START u0 {act=android.intent.action.VIEW flg=0x1000000
0 cmp=com.amazon.device.settings/.DevoProdConfigActivity bnds=[300,168][400,310]
} from uid 10017 on display 0
W/ActivityManager( 454): Permission Denial: starting Intent { act=android.inten
t.action.VIEW flg=0x10000000 cmp=com.amazon.device.settings/.DevoProdConfigActiv
ity bnds=[300,168][400,310] } from ProcessRecord{9460965 1138:com.teslacoilsw.la
uncher/u0a17} (pid=1138, uid=10017) requires com.amazon.dcp.permission.DISPLAY_D
EBUG_UI
E/Launcher( 1138): Launcher does not have the permission to launch Intent { act=
android.intent.action.VIEW flg=0x10000000 cmp=com.amazon.device.settings/.DevoPr
odConfigActivity bnds=[300,168][400,310] }. Make sure to create a MAIN intent-fi
lter for the corresponding activity or use the exported attribute for this activ
ity. tag=ShortcutInfo(title=Prod and Devo Switch intent=#Intent;launchFlags=0x10
000000;component=com.amazon.device.settings/.DevoProdConfigActivity;sourceBounds
=300%20168%20400%20310;end id=15 type=Shortcut container=-100 screen=1 rank=-1 c
ellX=3.0 cellY=1.0 spanX=1.0 spanY=1.0 dropPos=null user=UserHandle{0} modelGene
ration=-1) intent=Intent { act=android.intent.action.VIEW flg=0x10000000 cmp=com
.amazon.device.settings/.DevoProdConfigActivity bnds=[300,168][400,310] }
E/Launcher( 1138): java.lang.SecurityException: Permission Denial: starting Inte
nt { act=android.intent.action.VIEW flg=0x10000000 cmp=com.amazon.device.setting
s/.DevoProdConfigActivity bnds=[300,168][400,310] } from ProcessRecord{9460965 1
138:com.teslacoilsw.launcher/u0a17} (pid=1138, uid=10017) requires com.amazon.dc
p.permission.DISPLAY_DEBUG_UI
Tried granting that specific permission to Nova launcher or the Fire launcher but both do the same thing:
com.amazon.firelauncher com.amazon.dcp.permission.DISPLAY_DEBUG_UI <
Operation not allowed: java.lang.SecurityException: Package com.amazon.firelaunc
her has not requested permission com.amazon.dcp.permission.DISPLAY_DEBUG_UI
Maybe someone with more knowledge than I create a program with that permission that calls the intent in question?
Again good work on this
I picked up another new device yesterday morning. OTA updates disabled, Fire OS 5.0, no association to Amazon and connectivity via WiFi. Just like you I got Gmail, YouTube and other Google associated apps to work with the exception of the Play store. It finally let me sign in but comes up every time with the [Connection Retry] error.
I followed your instructions and installed AnyCut - and I have been playing around as I thought it might be possible by using shortcuts to load my Google account onto the device.
Shortcut [Add an account] - and the "Couldn't sign in - google server error" came back so not working for now.
Shortcut [Testing] - allows us to pull up more info on the Fire 7 with the 4 below options
Tablet Information - not working
Battery Information - working
Usage Statistics - working
WiFi Information - working
Shortcut [IP Settings] - gives us advanced WiFi options
A lot of the options try to load or there is a visible presence of starting to load and you can clearly see the device stopping them from loading. Basically we are trying to load Android Apps that are locked down by Fire OS which sits on top of Android.
Other apps with Permission Denied
[Log Manager]
[Crash Manager]
[Metrics Debug UI]
Looks like Amazon do not want us to have access to their inbuilt log files on their device
As I do not have access to Google store I have been using F-Droid for my apps. I have installed APK Extractor and it lists all the current APK's on the Fire 7. What is interesting about this is that there are APK's that where not findable using [AnyCut] but show up in APK Extractor.
Will update more in a bit
Here's an interesting note..... I'm on 5.0.0 and trying to get the Play Store working (I believe that 5.0.0 w/ Play Store is a better avenue to attack than trying to fix the launcher in 5.0.1)
For testing reasons I'm on an older version of the Play Store where the search icon is visible.
On the play store screen where it says no connection with the retry button, I hit the search icon and start typing "clas" It autofilled in clash of clans. Then i did "hang" and I see hangouts dialer. The play store app is communicating it would seem.....
tufkal said:
Here's an interesting note..... I'm on 5.0.0 and trying to get the Play Store working (I believe that 5.0.0 w/ Play Store is a better avenue to attack than trying to fix the launcher in 5.0.1)
For testing reasons I'm on an older version of the Play Store where the search icon is visible.
On the play store screen where it says no connection with the retry button, I hit the search icon and start typing "clas" It autofilled in clash of clans. Then i did "hang" and I see hangouts dialer. The play store app is communicating it would seem.....
Click to expand...
Click to collapse
What is the version of your Play APK please? As I have the latest version with no search - but still on 5.0.0
k3ll0gs said:
What is the version of your Play APK please? As I have the latest version with no search - but still on 5.0.0
Click to expand...
Click to collapse
I'm trying all kinds, the one i was using for that test I got here:
https://onedrive.live.com/redir?res...4&authkey=!AIVXLFXAOWDeM0Q&ithint=folder,.apk
I'm with you I tried some work arounds on the 5.0.1 tablet but if we can get the play store working on 5.0.0 it seems to offer more opportunities.
Yep same here - it makes more sense to get Play store to work.
I think I might know what the issue is causing and I believe it is down to the Google Service Framework (GSF) on 5.0 not installing correctly and causing the sync issue when trying to connect. I installed [Device ID] app on 5.0 and there is no serial listed for GSF at all - on my 5.1 tablet GSF would load up on the screen and you could view settings but on 5.0 it does not.
When trying to open the Google Play some I found the following error in Logcat [.onClick: b/5160617: Reinitialize account] this relates to the GSF serial not being present. Logs also show permissions and api errors as well. The only
Looking into a GSF workaround if possible. It might be on the wrong track but I am going to see what else I can find out.
I thought I had found a back door into Google signin. Using an App calling [Applications Info] which I used to pull up the GoogleServiceFframework apk. From there I started to play around with the launch options for the applicable services.
Selecting launch on [Legal Services] takes you to Google Sign In - keyboard was not working for this so I had to adb shell input text of my gmail & password. Unfortunately the same old Google error was appearing even after I cleared the cache and re-installed Gapps.
The last screengrab shows that the System Updates on installed Google Service Framework is corrupt and not working properly. I have also launched other Gapps dependent activities from the services in [App Info] and again they either fail to load of abundance of errors. So installation issues for all of the Gapps in one way or another on Fire 5.0
Obviously there is a difference between the 5.0 Rom + 5.01 Rom that is stopping Gapps from working. Due to the amount of errors in Logcat and in Application Info and dependent services not working. My gut is saying that when we have root on 5.0 we have a better chance of getting Gapps working as we will have the ability to play around with not only System files but System commands too.
If anyone has any ideas or what else we could try please chip in.
rivethead23 said:
Hook the Fire up to your computer and do the following commands:
adb shell pm hide com.amazon.otaverifier
adb shell pm hide com.amazon.device.software.ota
adb shell pm hide com.amazon.settings.systemupdates
Click to expand...
Click to collapse
running those commands will prevent any future update?
Right now I have 5.0.1 and I'm happy with it, I would like to avoid any bad surprises.
redst said:
running those commands will prevent any future update?
Right now I have 5.0.1 and I'm happy with it, I would like to avoid any bad surprises.
Click to expand...
Click to collapse
yes updates would be blocked until you run the unhide commands.
Sent from my KFFOWI using Tapatalk
Thanks to @kryz who managed to generalize the Dirty Cow exploit, XT1528 now has a way to get temporary root : link Notice that the /system will still be read-only, but at least full access to /data is available. Given the state of XT1528, this looks like a pretty good progress!
Steps to get temp root (in Lollipop):
0) uninstall SuperSu apk if you have it installed, see thisfor the reason to uninstall
1) install Croowt.apk, use the 2nd option in the menu : "Get root"
2) install SuperSu apk from the playstore (don't update the binary)
3) install RootChecker apk from the playstore
4) enjoy temporary root (until hard reboot)
I've tested this on 5.0.2, but should probably work on 5.1.1 as well (as long as it was not patched since the end of Oct). Here is the output of Root Checker (where everything looks nice and green !) :
Device: XT1528 (MOTO E Verizon prepaid)
Android Version: 5.0.2
Additional - SELinux
Status: NOT enforcing
Status stored in /sys/fs/selinux/enforce
SuperSu works (untill hard reboot) !!!
@9acca9, @dreyeth, @Whoareyou, @bendrexl, @docna, @caspar347, @Dishe, @hp79
This is great!
Thank you @kryz
I achieved the same with AT&T variant, but very unstable though. Reboots etc.. after so long
jcpowell said:
I achieved the same with AT&T variant, but very unstable though. Reboots etc.. after so long
Click to expand...
Click to collapse
This looks like the old Kingroot behavior - temp root which is highly unstable. Once after a Kingroot attempt I had to factory reset the device due to the "junk" left behind, at least here it's all nice and clean ! I wonder if forcing a soft reboot right after root may help to make it more stable ... Or perhaps something else is going on ?
No idea if anyone is looking into unlocking this phone's bootloader still but hopefully this leads to it. Happened with my Droid Turbo. The initial process was use Kingroot for temp root and sunshine to unlock.
Tried sunshine and after second test it gives an error. Won't even try
jcpowell said:
Tried sunshine and after second test it gives an error. Won't even try
Click to expand...
Click to collapse
The root is very clean - after a hard reboot there won't be a single trace of anything (ha-ha, not so good if one wants a permanent solution!) So reboot, and repeat the process, see what Sunshine does. Kingroot was nasty, leaving tons of trash behind.
Perhaps, you just delete Sunshine data, and launch it again?
I've reported the issue to the developer of the rooting method, perhaps there could be tweaks to make the root more stable : link
bibikalka said:
The root is very clean - after a hard reboot there won't be a single trace of anything (ha-ha, not so good if one wants a permanent solution!) So reboot, and repeat the process, see what Sunshine does. Kingroot was nasty, leaving tons of trash behind.
Perhaps, you just delete Sunshine data, and launch it again?
I've reported the issue to the developer of the rooting method, perhaps there could be tweaks to make the root more stable : link
Click to expand...
Click to collapse
There is a bug if you have SuperSU is installed before get the root, the restore init function will not work properly.
So the instructions in this post should be changed, and clarify that is required uninstall it.
Also ive fixed another bug related to clean the state of the system, the apk is updated in the main post.
Really after the restore clean the phone should be in a clean state, but if supersu is installed i don't know why is denying the access to the app.
Can you check this issue please?
@kryz I'm actually finding it more unstable with the updated app.
I am also having the reboot issue just after root.
Just tried the newest apk, and no reboot, but phone is laggy and unresponsive.
Uninstalled SuperSU,
Phone: XT1528, 5.1
Android Security Patch level: 2016-04-01
System Version: 23.201.2.surnia_verizon.verizon.en.US.vzw
I just attempted again, and I forgot to mention that just after I reinsert the sdcard, i get a warning that CRooWt is not responding with a Wait or Close prompt. Wait just caused another reboot.
Great work @kryz, i know you will get it sorted out. Please let me know how I can help.
Idk, as soon as I attempt to use my phone after root it freezes and reboots. If I let it sit it'll last an hour at least, lol
jcpowell said:
@kryz I'm actually finding it more unstable with the updated app.
Click to expand...
Click to collapse
Let's see what's going on
-Are you using the apk or adb script?
-If you use the apk and don't restore init what happens?
-If you restore init is laggy or reboot?
-Can you try the adb script and tell me if you also get a reboot?
-Finally if you can attach these files:
/sdcard/init.dmp
/sdcard/init.patch
Regards,
---------- Post added at 01:33 AM ---------- Previous post was at 01:16 AM ----------
fenlon said:
I am also having the reboot issue just after root.
Just tried the newest apk, and no reboot, but phone is laggy and unresponsive.
Uninstalled SuperSU,
Phone: XT1528, 5.1
Android Security Patch level: 2016-04-01
System Version: 23.201.2.surnia_verizon.verizon.en.US.vzw
I just attempted again, and I forgot to mention that just after I reinsert the sdcard, i get a warning that CRooWt is not responding with a Wait or Close prompt. Wait just caused another reboot.
Great work @kryz, i know you will get it sorted out. Please let me know how I can help.
Click to expand...
Click to collapse
First about the sdcard, i will look after that bug that i know what's happening,please don't remove/mount/umount for now.
Do you have a computer to do some checks?
You say that with the new version there is not reboot but laggy, can you check if there is some process eating the cpu with top:
Code:
/data/local/tmp/busybox top
I suspect there is the last process restauring init that is eating the cpu, check for this or ;
Code:
ps | grep dirtycow
If that is the case kill it and we will know if is the responsible of that lag.
In other hand can you attach these files:
/sdcard/init.dmp
/sdcard/init.patch
Guessing that you are using the apk, what happen if you don't restore init?
Is laggy or just unstable, don't start wifi/bluetooth you can't change settings are like locked.
Have you tried the script adb version, can you try and tell me if you have the same issue?
Best regards,
Let's see what's going on
-Are you using the apk or adb script?
Apk
-If you use the apk and don't restore init what happens?
It freezes and reboots
-If you restore init is laggy or reboot?
Laggy before freezing then ultimately reboots
-Can you try the adb script and tell me if you also get a reboot?
I'm give it a shot in a bit. Was a bit unsure on how.
-Finally if you can attach these files:
/sdcard/init.dmp
/sdcard/init.patch
Here are the files
https://drive.google.com/folderview?id=0B26uDxbLACN6V2IzM1VvOTlnNk0
@kryz
jcpowell said:
Let's see what's going on
-Are you using the apk or adb script?
Apk
-If you use the apk and don't restore init what happens?
It freezes and reboots
-If you restore init is laggy or reboot?
Laggy before freezing then ultimately reboots
-Can you try the adb script and tell me if you also get a reboot?
I'm give it a shot in a bit. Was a bit unsure on how.
-Finally if you can attach these files:
/sdcard/init.dmp
/sdcard/init.patch
Here are the files
https://drive.google.com/folderview?id=0B26uDxbLACN6V2IzM1VvOTlnNk0
@kryz
Click to expand...
Click to collapse
You told me before, that you got root little bit unstable but you got with the first version?
I attach a new version with some changes reverted and i think will work, tell me if you get root.
In this version doesn't ask for restore when is finish but you can do it after in tools/restore init.
kryz said:
You told me before, that you got root little bit unstable but you got with the first version?
I attach a new version with some changes reverted and i think will work, tell me if you get root.
In this version doesn't ask for restore when is finish but you can do it after in tools/restore init.
Click to expand...
Click to collapse
Got root, but still lags a bit and reboots within minutes if I attempt to open apps etc.. unless I clean init afterwards. Then I get a bit more stability, but still reboots.
jcpowell said:
Got root, but still lags a bit and reboots within minutes if I attempt to open apps etc.. unless I clean init afterwards. Then I get a bit more stability, but still reboots.
Click to expand...
Click to collapse
The last check i think is try the adb script because is not using the same method.
In the apk im hijacking fsck_msdos and i don't release it, is possible that the phone detected to much time in the process and reboot it?
Have you try only check permissions, not get root, and just work with the phone to see if you get rebooted anyways, if you get rebooted i need to clean the fsck_msdos process (the sdcard check).
Thank you for testing
kryz said:
The last check i think is try the adb script because is not using the same method.
In the apk im hijacking fsck_msdos and i don't release it, is possible that the phone detected to much time in the process and reboot it?
Have you try only check permissions, not get root, and just work with the phone to see if you get rebooted anyways, if you get rebooted i need to clean the fsck_msdos process (the sdcard check).
Thank you for testing
Click to expand...
Click to collapse
Yea it reboots in the check as well.
---------- Post added at 04:36 AM ---------- Previous post was at 04:05 AM ----------
I'm a little confused on the ADB. Where exactly am I extracting the rar? Onto my device internal SD?
jcpowell said:
Yea it reboots in the check as well.
---------- Post added at 04:36 AM ---------- Previous post was at 04:05 AM ----------
I'm a little confused on the ADB. Where exactly am I extracting the rar? Onto my device internal SD?
Click to expand...
Click to collapse
If it reboots just checking permissions the problem is the fsck_msdos process not the shellcode in init, i saw in the files that you attach all is ok.
I've updated the apk in the main post, now it will release the sdcard, please check that version in the same way, first before get root, click "check perm" wait to see the results and work with the phone to see if reboots again for a while.
If all is working with "check perm" and you don't get reboot, try get root, is very probably that now doesn't reboot.
I think with the adb script will work because it overwrites run-as, anyways ive updated the apk for release the sdcard check process and it'll return ok status.
The instructions for the rar and adb.
First you need adb installation in your computer, i mean connectivity with the device via adb.exe.
When you have adb working you need to put all the content of the rar in the path /data/local/tmp/.
So extract the rar in your computer in a folder and with adb push copy all the files to that folder:
(in the folder of the rar contents)
Code:
adb push * /data/local/tmp/
Then get a shell with adb:
Code:
adb shell
Execute the script to exploit it:
Code:
cd /data/local/tmp
./exploit.sh
Wait the logs and if all is ok execute:
Code:
run-as -s2
Wait 5 seconds and:
Code:
su
If all is ok you will have a root shell, this method is more stable even doesn't clean the init you can do it in the app, but test all before.
That last apk causes me immediate reboot. Maybe it was not the fsck_msdos cause I was able to do a check and not get a reboot with the debug apk you gave me. I am trying the adb method but I think I am messing up some steps. Will let you know when I get through it.
@kryz I should have some time tomorrow to test the shell commands. Thank you again for taking your time to do this.
I can't get AirMirror to connect to my S820L, either thru AirDroid Web or the Airdroid server app on Win7SP1. Is it working for anyone else?
First I should note I'm using Psilocelium's excellent pared-down v4.4.4 ROM. Whenever AirMirror tries to connect, I get two SuperSu messages on the phone, the first one in two lines. The first line states that "Airdroid has been granted superuser permissions" but the second line reads "kill -15" followed by some process number, which changes each time I make the attempt. Seconds later there's a second message, "Airdroid has been granted superuser permissions for an interactive shell." Then the AirDroid server app shows, "AirDroid failed to get root permissions...."
I also have an LG Optimus Fuel, on which AirMirror works just fine. When I try to use AirMirror with it, I don't get the "kill -15" message, it starts with the interactive shell message, then the chmod and so-on. Originally it was running the same identical version of SuperSU as the Samsung but I've since updated the Samsung to the latest version, which didn't change anything.
So I'm wondering, is AirDroid even known to be compatible with the Core Prime? Or might it be a SuperSU problem, a hiccup in Psilocelium's ROM, or (most likely of all) operator error?
Hello. It's driving me crazy: microphone access permissions for Google Meet, Microsoft Teams, Facebook Messenger keep reverting to disabled state after reboot. I tried setting them from adb (e.g. pm grant com.google.android.apps.meetings android.permission.RECORD_AUDIO) but it behaves the same. I do not have profiles enabled, I already wiped cache from recovery, I do not know what to try next. Storage and Camera permissions remain, just the Microphone is stubborn. Please help, thank you.
Update to 7.3.1.7 (a quick bug-fix release), then go through ALL of the tablet settings and toggle every one of them back and forth one time to end up on the correct setting, even if it looks like it is already on the correct setting (sometimes it isn't).
Just received 7.3.1.7 and the problem is still there after restart. Do you have the same version and for you is the microphone permission working fine for either of the sideloaded apps?
I'm having same problem. It seems to be happening only with sideloaded apps.
Actually I take that back, I just tried facebook app downloaded from Amazon appstore and it's also happening.
Restart your Fire tablet and view logs on your Fire tablet using ADB
Code:
//Enter ADB shell
adb shell
//Start logcat
logcat
and you can see the suspected app that revokes microphone permission.