Related
I have never had an issue, but a few people have commented recently (odd that it's mostly recent) that when they delete a file it seems to re-appear.
IF (and only if), you are having this issue, could you please post the version of Root Explorer you are using and the build you are running (and perhaps how you got your build, ie kies, ota, odin, flash).
I'm hoping this will lead to a common issue (not likely, worth a shot).
The most recent build is 2.12.4. I don't understand why there is a small number of people having issues. I've been trying to contact the developer as well and hope this thread will help him too.
Thanks.
Have you tried root manager?
I'm using Root Explorer - 2.10.2 with JI6. I updated through Odin. I do have root.
^^ nomad, not trying to sound rude:
"I have never had an issue"
"IF (and only if), you are having this issue, could you please post"
Click to expand...
Click to collapse
I had this issue with 2.12.2 and Bionix Fusion & Obsidian.
Sean what did u do to resolve it?
This is sort of ot, but Astro has decided to let me delete system apps which it never did before. I'm running fusion 1.2 stock kernel.
Don't blame me, blame my keyboard's autocorrection algorithm.
flashyp said:
Sean what did u do to resolve it?
Click to expand...
Click to collapse
didn't resolve it really, I wanted to delete some bloatware but I ended up just freezing the apps in Titanium Backup.
I contacted the developer *and got a super fast response*. Please make sure you are on the latest build. Please see his email pasted below.
Hi,
Thanks very much for your support, it’s much appreciated. I actually have a Galaxy S myself with Android 2.1 and have been running Root Explorer on it successfully for some months now. There was an issue a while back in that remounting the system partition didn’t work, but that was fixed in a recent update. Also, I’ve just updated to Froyo and rooted using Z4Root and Root Explorer is still working well. So on a rooted stock Galaxy S I know there are no problems.
So the question is, what is the difference on the phones where there’s a problem? Are there any major differences in the carrier specific versions? And are the problems only happening on custom ROMs? One person recently reported that Root Explorer didn’t recognise root on his Galaxy and I found that he was running a custom ROM and the su file was placed in a non-standard location.
Ok, something has just come to mind. When I first received my phone I was surprised to find that the system partition was mounted as R/W even before rooting. But of course you still don’t have permission to change system files. I’ve just replicated this situation by remounting system as R/W and renaming su to sux. I then closed Root Explorer and restarted it. It started in non-root mode and when I went to system it correctly reported the file system state as r/w but there was no “Mount R/O” button. I tried a delete and then a rename and the app reported these as having worked. But going out and back in showed that the changes didn’t actually work. I’m pretty sure this must be what’s happening for some people. So the question you need to ask them is whether they can see the mount button. If not then their phone isn’t rooted. Do you agree that this is the most likely scenario?
In the meantime I need to make a change to Root Explorer to properly check whether these operations worked and not mislead the user that the change happened.
Thanks for pointing this out. Galaxy S phones are probably the most popular out there at the moment. I think by fixing this issue there will be a lot more happy Root Explorer users!
Best Regards,
Colin
Click to expand...
Click to collapse
Once I pointed out that users were indeed rooted and saw the button, this is the response I received:
Well that blows my theory out of the water
The actual delete is just a simple rm command so there isn’t much that can go wrong. One possibility is a dodgy BusyBox binary. I’ve seen this cause problems for a few people but it’s very rare. If BusyBox is ok then I can only guess that the remount hasn’t worked. One question to ask is whether the remount operation appears to work. If it does nothing and the mount status stays as either r/w or r/o then this may be the problem. If this is the issue then it would be useful to see the output from a mount command. I can then push this through Root Explorer in debug mode and find out what command it’s running to perform the remount.
Click to expand...
Click to collapse
thanks for your help.
I'm running Root Explorer 2.12.2 on Obsidian v2.2 Froyo. I do see the Mount as R/W button, and I'm running BusyBox v1.17.1
I'm going to try re-installing BB, I'll post back if it fixes the issue.
Edit: WTH, it's working now. I had a dodgy BusyBox install.
Edit x2: And it's broken again. Weird.
The developer said there was an issue with old builds, why not update?
s15274n said:
The developer said there was an issue with old builds, why not update?
Click to expand...
Click to collapse
Working on that now. I don't think it's an issue with Root Explorer though because if, upon the permission failure, I simply re-install BB, RE is then able to edit files again. I need to mess around with it more to be sure, but I'll update RE in the meantime.
I've considered rooting and installing a custom ROM dozens of times ever since I got my Droid X back in August and I've finally decided I'm just going to do it, but i just want to double check a few things before I root my phone and install Fission:
1. I know that rooting voids your warranty, but if I have problems with my phone and I end up needing repairs, can I just unroot my phone back to stock and still have my phone be covered under the warranty?
2. Will my phone be secure rooted with a custom ROM? I don't want people having access to my personal info contact data, and my passwords.
3. If I Overclock to say 1.2 or 1.3 Ghz with ULV, will I have stability problems with demanding 3D games or other demanding apps?
4. After I root and install my Custom Rom, will I need to reactivate my phone or need to re-add my phone contacts/apps?
5. Will Z4Root work on system version 2.3.340?
I have unrooted and exchanged under warranty with no problems. Your phone will be just as secure. 1.2-1.3 are very stable on my phone. If you do have to reactivate it's as easy as dialing *228 and following the prompts. If your contacts are "google" contacts they'll return to your phonebook. Your apps from the market shall return without a problem. And yes, z4root will work with your system version.
Sent from my DROIDX using Tapatalk
I am having difficulty rooting my droid x. I am an android noob, but am a pretty savvy user. I used z4 (permanant) and it says it has been rooted when i launch the app. However i see no appreciable difference in access. My terminal still shows a $ prompt and i cannot uninstall verizons crapware. I used rage against the cage prior to z4 with similar results, but i was able to at least get temporary su access and install the bootstrap recovery and perform a system level backup. It reverted to user access after rebooting. Please help.
Superuser confirmation
alright, if you want super user privileges in terminal type "su", then once you hit enter, you get "#" instead of "$" To test if you have root access, first check app drawer for "Superuser" if its there, open an app that requires it, (wifi teather, root explorer, rom manager to name a few) you should get a pop up similar to this
http://www.google.com/imgres?imgurl...=1&ndsp=12&ved=1t:429,r:8,s:0&biw=888&bih=638
that would be a diffinitive confirmation that you have superuser permissions.
The way I remove verizons crap once rooted, is to use root explorer, go to system/app and find the .apk files you want to remove. There are lists around the forums what is safe to remove. I highly recommend simply renaming the files. For example, the 3g hotspot app is called mynet.apk, so I would just rename it to mynet.bak, or mynet.apk.bak, really anything that lets you know what it is, but removes the .apk extension.
Ok, I have confirmed su access, but am unable to rename any of the offending .apk's. I am simply told that the operation was unsuccessful. I have tried a couple of different file managers, as well as trying from a terminal, still no luck. I like 2.2.1 alright, but if i can't control what apps are running on my phone with root access, I may want another ROM. Any suggestions are appreciated, aswell as any links to a rom installer that is pc-less.
I usually rename apk's from Root Explorer, just prefer the graphical interface, so I can't really help you on the terminal process.
Rom manager is "pc-less" although most roms are posted in forums first it is often the easiest route, also lets you make backups and restore. There are a few posts around on how to install a rom you might want to read first. Also, you should find the thread for the rom before you flash it, in favor of size and speed, some developers go down to bare minimum and may remove something you need/want.
I have not used it, but I hear Titanium Backup allows you to "Freeze" apps, so that is a possible route also.
2.2.1 is not exclusive to people running official vzw builds, many of the roms on the forum (and rom manager) are running 2.2.1, so you will not be taking a step back to an earlier release.
SharkBaitDave said:
I usually rename apk's from Root Explorer, just prefer the graphical interface, so I can't really help you on the terminal process.
Rom manager is "pc-less" although most roms are posted in forums first it is often the easiest route, also lets you make backups and restore. There are a few posts around on how to install a rom you might want to read first. Also, you should find the thread for the rom before you flash it, in favor of size and speed, some developers go down to bare minimum and may remove something you need/want.
I have not used it, but I hear Titanium Backup allows you to "Freeze" apps, so that is a possible route also.
2.2.1 is not exclusive to people running official vzw builds, many of the roms on the forum (and rom manager) are running 2.2.1, so you will not be taking a step back to an earlier release.
Click to expand...
Click to collapse
If you are trying to rename apps in the /system/app portion of the OS, you will need to mount /system as RW first.
from terminal: mount -o rw,remount /dev/block/mtdblock4 /system
After it has been mounted read-write, you should be able to rename...
to remount as read-only: mount -o ro,remount /dev/block/mtdblock4 /system
zwade01 said:
I have unrooted and exchanged under warranty with no problems. Your phone will be just as secure. 1.2-1.3 are very stable on my phone. If you do have to reactivate it's as easy as dialing *228 and following the prompts. If your contacts are "google" contacts they'll return to your phonebook. Your apps from the market shall return without a problem. And yes, z4root will work with your system version.
Sent from my DROIDX using Tapatalk
Click to expand...
Click to collapse
Thank you for your response. Just out of curiosity, did you (or anyone else for that matter) have to reactivate your phone after rooting and installing a custom ROM? I'd rather not have to re-activate my phone every time I want to update a ROM or change to a different ROM.
Thank all of you for the great info. Here's what I've learned after a day of rooting and romming: titanium freezes apps only in the paid version, z4 was the most user friendly app for rooting noobs, milestone overclock works well if you have the patience to lock up your phone several times finding the right settings, and I'm digging apeX 1.3.1. Thx to everyone for your help, i will definately be checking here frequently. One last question: where might i find a side by side comparo of roms with things like features and memory footprint, etc.? Or am I asking for too much. Im not scared of the search button, but i will defer to the more experienced of you. Thanks again.
galaga4991 said:
Thank you for your response. Just out of curiosity, did you (or anyone else for that matter) have to reactivate your phone after rooting and installing a custom ROM? I'd rather not have to re-activate my phone every time I want to update a ROM or change to a different ROM.
Click to expand...
Click to collapse
I used rom manager to load apeX 1.3.1 and did not need to #228. I did not clear the user data or cache, but I do not know if that affected my results or not. Your mileage may vary.
stpvapor said:
Thank all of you for the great info. Here's what I've learned after a day of rooting and romming: titanium freezes apps only in the paid version, z4 was the most user friendly app for rooting noobs, milestone overclock works well if you have the patience to lock up your phone several times finding the right settings, and I'm digging apeX 1.3.1. Thx to everyone for your help, i will definately be checking here frequently. One last question: where might i find a side by side comparo of roms with things like features and memory footprint, etc.? Or am I asking for too much. Im not scared of the search button, but i will defer to the more experienced of you. Thanks again.
Click to expand...
Click to collapse
I don't know that anyone has really done a side by side per say. Since you say you are apeX, then if you are looking for more ROM's that contain blur features, then I would recommend looking into ZapX Bazinga, or Fusion (from the same creator as Fission, but just with blur). I have not worked with any of the Blur ROM's so far...
If you are looking for ROM's that do not have blur, then the big ones are Liberty, Fission 2.5.7, GummyJar 2.5, and Rubix Focused 1.9.5. Liberty is the big one right now, because it just came out and combines the great talents of Kejar31 and Jrummy. Most others I believe are using Fission. All are great choices, as the dev's do some AMAZING work.
Each has their owns unique feel...so I woudl recommend just digging through each thread for their respective ROM's as they usually include what components are built into each ROM on the original post of each thread.
Hope this helps somewhat =)
another ROM to try is DarkSlide. It comes in both flavors, Blurred & Blurless. It's fast, stable & well supported. You only have to re-activate if you wind up bricking your phone & have to flash an SBF. My advice it to spend the $$ on DroidXBootstrapper (available in the market) to make a nandroid backup prior to flashing your new ROM. This way you have a base to go back to in the event you run into problems, or want to try multiple ROMS. One other suggestion is to rename each backup into something that will let you know what the backup actually is, like StockROMBU or the like.
Fellows,
I've seen this one on Mobileread forum.
There is an update for Nook STR, namely 1.0.1, to be delivered during the week.
Nook 1.0.1 update
As per B&N site:
"The All-New NOOK Ver1.0.1 is a minor update based on early customer feedback that includes:
Connect more easily to Wi-Fi hotspots
Improved touchscreen responsiveness
Enhanced accuracy of battery meter"
I hope this one in root friendly.
Is there a way to block it?
Well I hope it's working, cause I had to go to root my nook at my friends house, since my computer is currently broken. I don't have the guts to try it first and then spend the whole afternoon fixing it and bothering my friend again if it won't work. Is there anyone with a backup who would give it a try?
I've downloaded it. It's 103 Mb in size.
But I still don't have the guts to install it and most likely lose my root...
Whoever tried the update please let us know whether it is root friendly...
I did the update but I have never rooted. Waiting for a more specialized ROM optimized for the eink display. My only reason to root would be a better pdf app, but I am getting along fine without that for the time being.
The update does noticably improve the accuracy and response of touch functions. It seems a little snappier to bring up some of the menus and navigating to bookmarks also.
Sent from my SCH-I800 using XDA App
edit...I did some tests and found that an epub stored on an 8gb class 6 Transcend microSD has improved seek time than when stored in the built in memory. Makes me eager to see what an ext4 file system/kernel/rom could do for this device.
Apeine have you tried the update yet? I've read a blog entry out in net land and it does not sound like the update would work with a rooted nook.
Someone posted a way to do the upgrade, that is supposed to run on a "cleaned" Nook (8 boot failures). But I don't want to lose the root either...
Anyway, all my files are in the SD, so I'd just have to do the boot failure. Maybe I'll try later on.
My Nook STR autoinstalled the update over wifi - I didn't even know there was an update coming down the line. Anyway, it definitely undid my root access. I noticed it when my custom front button mapping had stopped working. I still had access to ADWLauncher and any apps I had installed except for the back and menu button in Button Savior no longer worked.
HOWEVER, Z4Root seemed to work perfectly in getting the root back. Just install Z4Root, click permanent root and let it reboot and you should be fine. Wireless ADB isn't working but I don't mind too much at the moment. I used Terminal Emulator and Root Explorer to push my custom button mapping back on the device so now I'm up and running back to where I was.
Well, so I rooted it again, and now I managed to download astro, new market again, and everything is going back to its former place. So, no major problems during update, and I get to call that tiny arrow for button saviour much faster now!
Next step, ad-hoc hack!!! Still wish there could be a way to make it automatically...
iamnotpretending said:
My Nook STR autoinstalled the update over wifi - I didn't even know there was an update coming down the line. Anyway, it definitely undid my root access. I noticed it when my custom front button mapping had stopped working. I still had access to ADWLauncher and any apps I had installed except for the back and menu button in Button Savior no longer worked.
HOWEVER, Z4Root seemed to work perfectly in getting the root back. Just install Z4Root, click permanent root and let it reboot and you should be fine. Wireless ADB isn't working but I don't mind too much at the moment. I used Terminal Emulator and Root Explorer to push my custom button mapping back on the device so now I'm up and running back to where I was.
Click to expand...
Click to collapse
Can you please post a link to which z4root you used?
apeine said:
Well, so I rooted it again, and now I managed to download astro, new market again, and everything is going back to its former place. So, no major problems during update, and I get to call that tiny arrow for button saviour much faster now!
Next step, ad-hoc hack!!! Still wish there could be a way to make it automatically...
Click to expand...
Click to collapse
How did you end up rooting it please?
nickveldrin, I used the touchnooter 1.6.24 again, and it went straight to the homescreen, no redoing the youtube-gmail login part, and it started working again...
I compared the v1.0.1 update's ramdisk.img and the uRamdisk used for rooting the Nook Touch.
They're the same, other than the modifications to start ADBd.
Looking at META-INF/com/google/android/updater-script, other than some firmware flashes (for WiFi), there doesn't appear to be anything that otherwise disables root?
Applied v1.0.1 to my Nook, and re-did the manual rooting process (replacing uRamdisk via noogie.img boot). Worked fine—I've a v1.0.1 Nook and am still able to ADB into the device, run Debian, etc.
So if I apply the upgrade will it return my nook to original status or will the effects of Touchnooter still be there? I didn't know about making a copy of the original root incase I ever needed to return my Nook and am now trying to back track. Or is there another way to totally remove the effects of Touchnooter?
Let's hear about the advantages the advantages of the update from those who have installed it. Anything that stands out?
coenna said:
Let's hear about the advantages the advantages of the update from those who have installed it. Anything that stands out?
Click to expand...
Click to collapse
Stuff I've noticed:
Better battery life w/ WiFi enabled (lasts an extra day or 2?)
Touchscreen feels more "responsive"
Screen refreshing is supposed to be better (as mentioned by B&N), but I haven't noticed it.
So it should be safe to update? Do you just update, boot on sd with the rooted forever screen and then you have your old apps and settings again?
Sent from my LG-P990 using Tapatalk
ravn1,
Mine didn't got that way, but I didn't wait to see how others fared on their update. I had to unroot, reboot, update and root again. Everything was lost (data was on SD, so only apps were really lost).
But I see that some others managed to update without losing everything. Look carefully on which way is better for you.
I'm going to give it a shot. I have a "control" nook STR and a rooted nook STR, so I'll be able to compare.
I noticed (in logcat) that the BN service has started to acknowledge there's an OTA update, but it immediately warns, and does not start the download/update.
com.bn.devicemanager.ACTION_ALARM_WAKEUP
SoftwareUpdateManager( 1014): Cannot prepare download directory
Click to expand...
Click to collapse
This suggests that the OTA update can be blocked at this stage by making the Downloads directory inaccessible, although I'm not sure currently what path it's checking.
Where can I download the 1.0.1 update now that the 1.1.0 update is the only one available on bn.com?
I want to root my A7+ WITHOUT installing someone elses custom rom. I just want it rooted long enough that I can push GAPPS onto it. Is there any special trick with Elocity A7+ ??
Will I only be able to do this with earlier versions from Elocity?
The reason I want to do it this way is twofold.
1) I want EVERTHING to keep working.
2) I don't want Superuser snoops.
I can work with ./adb shell on this Linux or it would be even better for someone to show me how to COMPILE the newly released source from Elocity.
Thank you all !!
Dan
as shown in this thread http://forum.xda-developers.com/showthread.php?t=1431967 you could use Z4root.apk
It allows for temporary root
Cheers !
Yes Thanks . I did Z4Root PERMANENT. Did my thing and then turned off root .
I remembered just before coming back to post here. I never used ./adb shell push this time. Couldn't get RW with ./adb so I just copied from GAPPS folder to /system/app/ using Root Explorer.
First time I copied TOO MUCH AND IT WAS IN ENDLESS LOOP.
I repaired and then copied the important stuff...Installed Gmail and then rebooted.
All is well after reboot. But I had to go through Wizard again. Now running everything !!
Dan
another thing that i find funny about this new setup is that bluetooth and foursquare only run when while im rooted????
if i turn off root they dont work
So as I said in my last post, BLUETOOTH only works while rooted. (after having rooted once) So, I wanted to use BLUETOOTH with a new keyboard. I removed Z4root, but left Superuser running in the background. Well , once again, everything seemed to run great for a week, but then things went south. I was getting a reboot loop type thing, about 5 times before it would finally boot up.
I'm not sure, but is suspect this leaves you wide open to a virus or other malicious garbage. So now I'm back to factory with no Gmail or Youtube but I'm finding workarounds.
Dan
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.