Related
just got my hox, tried 2 different procedures to root the phone, neither way will root it. any suggestions?
There is a sticky in the dev section. It may take a few tries but it absolutely does work.
Sent from my HTC One X using xda premium
is that the one that says act now, may not last forever?
That's the one.
Sent from my HTC One X using xda premium
Ramsport said:
is that the one that says act now, may not last forever?
Click to expand...
Click to collapse
Yes, try the one-click method for 1.85.
Sent from my HTC One X using xda premium
im using the one-click 1.85 now, its stuck at the waiting for device to reboot screen. how long do you have to wait for it?
if i manually reboot the phone it starts the process, but it keeps saying failer when it tries to access phone.
Read the instructions.
_MetalHead_ said:
There is a sticky in the dev section. It may take a few tries but it absolutely does work.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
How many tries is a few? I've been using instructions from these threads
http://www.theandroidsoul.com/root-htc-one-xl-att-one-x-1-85-update-with-just-one-click/
http://forum.xda-developers.com/showthread.php?t=1709424&
http://briefmobile.com/how-to-root-htc-one-x-att
to no avail, doing the 2-day push forward/reboot routine, at least 20 times. I wait anywhere from 10-30 minutes per try and I always get stuck on
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
81 KB/s (334 bytes in 0.004s)
rm failed for /data/data/com.redbend.vdmc/lib/libvd*, No such file or directory
Go to Settings, ATT Software update, check for updates.
Waiting for device to Reboot...
Click to expand...
Click to collapse
I realize the most popular remedy is to keep trying to push the date and reboot, but I've been at this all night with the same result, even having followed the directions. Any help is greatly appreciated.
mavrinex said:
How many tries is a few? I've been using instructions from these threads
http://www.theandroidsoul.com/root-htc-one-xl-att-one-x-1-85-update-with-just-one-click/
http://forum.xda-developers.com/showthread.php?t=1709424&
http://briefmobile.com/how-to-root-htc-one-x-att
to no avail, doing the 2-day push forward/reboot routine, at least 20 times. I wait anywhere from 10-30 minutes per try and I always get stuck on
I realize the most popular remedy is to keep trying to push the date and reboot, but I've been at this all night with the same result, even having followed the directions. Any help is greatly appreciated.
Click to expand...
Click to collapse
When it says waiting for device to reboot, are you manually rebooting it? You should. I have now used this method 4 times and every time it took a few tries. Check your app drawer and see if there is an app called SuperSU. If you do have it, click on it. If it says no binary installed then you need to try and root again. If it says binary needs to be updated, click update. That means you're rooted.
Use the directions from here, not some other site.
http://forum.xda-developers.com/showthread.php?t=1709296
Sent from my HTC One X using Tapatalk 2
I used the manual method the auto click is based on and it worked like a charm
I was able to root mine from 1.85 yesterday without a problem. I used the one click method found in the DEV section. It took me 3 tries to get superSU installed, and then a 4th try to have the binaries installed to.
When it says waiting for device to reboot, are you manually rebooting it? You should. I have now used this method 4 times and every time it took a few tries. Check your app drawer and see if there is an app called SuperSU. If you do have it, click on it. If it says no binary installed then you need to try and root again. If it says binary needs to be updated, click update. That means you're rooted.
Click to expand...
Click to collapse
Thanks for that, I didn't see any instructions to reboot manually. But even after implementing that into my cycle, I am stuck again... here's the last bit
* daemon started successfully *
pkg: /data/local/tmp/Superuser.apk
Success
adb server is out of date. killing...
* daemon started successfully *
Unable to chmod /system/xbin/su: No such file or directory
Unable to chmod /system/xbin/su: No such file or directory
Unable to chmod /system/xbin/busybox: Read-only file system
Unable to chmod /system/xbin/busybox: Read-only file system
Unable to chmod /system/app/Superuser.apk: No such file or directory
rm failed for /data/local.prop, No such file or directory
Done! Rebooting...
Press any key to continue . . .
Click to expand...
Click to collapse
When SuperSU does actually install, maybe every other time, it keeps bringing up "there is no SU binary installed".
I made two rounds up to July 3 after resetting the date back to auto just once... now I'm at July 7..... still going..
Hello, just got a HOX with 1.85 RUU and the one click root wont work cause the OTA is recognize and it starts downloading the update. What can I do?
rickmarz said:
Hello, just got a HOX with 1.85 RUU and the one click root wont work cause the OTA is recognize and it starts downloading the update. What can I do?
Click to expand...
Click to collapse
We don't know. Sorry. This update just hit yesterday and has us all scrambling for answers.
gunnyman said:
We don't know. Sorry. This update just hit yesterday and has us all scrambling for answers.
Click to expand...
Click to collapse
Thanks anyway gunny. I'll wait to see what comes around.
Sent from my HTC One X using xda premium
I think it's been reported that the relese of this update breaks the exploit beaups found.
If HTC let us legally unlock the bootloader wed have no problem but...
i read that some people have successfully rooted during the download of the OTA but not sure how
TheLlamaGod said:
i read that some people have successfully rooted during the download of the OTA but not sure how
Click to expand...
Click to collapse
Yes,
As long as you are on 1.85, the exploit still works.
Hello , i am still in 1.85 . So i am still able to do the root? I don't have an ATT service , i use straighttalk do i necessarily need an att sim card in my phone? to run the update? Because when i do it with the straighttalk sim card inside the phone displays that the server is not working . Can i do it via wifi?
Thanks!
Help me please!
This is exactly what mine says. I have a HTC one x on att and windows 7. Please help!
Exploit by beaups, script by designgears
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
0 KB/s (334 bytes in 1.000s)
Go to Settings, ATT Software update, check for updates.
Waiting for device to Reboot...
/data/local.prop was created, looking good.
remount succeeded
1796 KB/s (91980 bytes in 0.050s)
2319 KB/s (1116332 bytes in 0.470s)
rm failed for /system/app/Superuser.apk, No such file or directory
2271 KB/s (574184 bytes in 0.246s)
Error: Could not access the Package Manager. Is the system running?
Unable to chmod /system/app/Superuser.apk: No such file or directory
Done! Rebooting...
Press any key to continue . . .
Well its saying the superuser.apk is not in the folder is there a superuser.apk in the folder on your pc where the bat file is?
Sent from my HTC One XL using Forum Runner
E.Cadro said:
Well its saying the superuser.apk is not in the folder is there a superuser.apk in the folder on your pc where the bat file is?
Sent from my HTC One XL using Forum Runner
Click to expand...
Click to collapse
Yes. This is the list of files inside that folder : adb, AdbWinApi.dll, AdbWinUsbApi.dll, busybox, magic.sh, root, su, Superuser.apk
swdsc said:
Yes. This is the list of files inside that folder : adb, AdbWinApi.dll, AdbWinUsbApi.dll, busybox, magic.sh, root, su, Superuser.apk
Click to expand...
Click to collapse
Are on 1.85?
Sent from my HTC One XL using Forum Runner
E.Cadro said:
Are on 1.85?
Sent from my HTC One XL using Forum Runner
Click to expand...
Click to collapse
it's 1.85.502.3
swdsc said:
it's 1.85.502.3
Click to expand...
Click to collapse
I would go back to the original thread and have a read then. There are a lot of tips
Like making sure the phone is charged over 40%
Making sure usb debugging is enabled that fastboot is turned off that your in charge only that WiFi is on to name a few. Some people had to try 4 to 5 Times. I'm sure if you take the time to read through you will find enough suggestions to help.
If all else fails find the original thread by beaups and try to do it manually.
The rm superuser thing I forgot was added to the script later its looking for superuser on the phone to remove it and move to data app I believe.
If your still stuck report back.
Sent from my HTC One XL using Forum Runner
Alright other people have been saying it is working on windows so I decided to try it out. I installed the Samsung drivers and installed the java jdk. When I run it and click "Do it" for the Root GS3 with DebugFSRoot option my phone reboots and all I get is this and it just sits there....
Step 1 - Setup...
Copying files:
Copying su:3020 KB/s (380532 bytes in 0.123s)
Copying debugfs:3455 KB/s (1862336 bytes in 0.526s)
Copying debugfsinput:47 KB/s (144 bytes in 0.002s)
...done copying files.
Linking /system to tmp...
...done linking /system
Rebooting...
Step 2 - Rooting...* server not running ** daemon not running. starting it now on port 5037 *
* daemon started successfully *
Any help?
I had the same issue so I went with this method
http://forum.xda-developers.com/showthread.php?t=1792342
slick_shoes said:
I had the same issue so I went with this method
http://forum.xda-developers.com/showthread.php?t=1792342
Click to expand...
Click to collapse
Went through the whole process for the other one too and the cmd window even showed that I had root but my phone still wont let me use rooted apps even after a reboot.
*facepalm* Had to restart my computer. 2nd method worked like a charm!
Just downlod ez unlocker in the app store it a app to unlock one touch and it was updated today to have a relock feature!
Sent from my SCH-I535 using Tapatalk 2
tonytownsend said:
Just downlod ez unlocker in the app store it a app to unlock one touch and it was updated today to have a relock feature!
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
That doesn't root which is what the op was trying to do.
slick_shoes said:
I had the same issue so I went with this method
http://forum.xda-developers.com/showthread.php?t=1792342
Click to expand...
Click to collapse
Ditto here.
+1 on the EZ unlocked. Couldn't be any easier than that.
RE: Casual R131. "You just download it, connect your Galaxy S III, launch the tool". Ok, I'm a NOOB to android. What tool?
In windows or linux, once you download, I take it you decompress.
Then what exactly do we do? Open a command prompt in Win? Then run what?
Same for Linux, run what from what. Just launch the tool is too vague for us newbees.
Understand the setup of this just fine. Not the execution.
Your help is appreciated.
I ran into the same issue. I clicked Do It again after waiting there for a few minutes. It restarted the process. When you get to step 2, wait for the device to be Connected before clicking okay. Worked like a charm.
meekell said:
I ran into the same issue. I clicked Do It again after waiting there for a few minutes. It restarted the process. When you get to step 2, wait for the device to be Connected before clicking okay. Worked like a charm.
Click to expand...
Click to collapse
This is what I had to do. I just repeated this a couple times until su worked.
Sent from my Nexus 7 using Tapatalk 2
Hi I have a kyocera Milano that I would love to root but can't seem to find ANY solution to do such.
Phone Specs:
Android 2.3.4
Model number: C5121
Software Version: ADD1015
Hardware Version: 0305
Baseband Version: ADD10
Kernal version: 2.6.35.7-perf [email protected] #1 Mon Dec 12 17:56:45 PST 2011
Computer Specs:
2.2ghz Celeron 64-bit
2gb RAM
Windows 7 64-bit
Android SDK Installed
Phone drivers Installed
Adb for phone installed
-------------------------------------------------
Whenever I do a run of ZergRush I get this:
This is a generic zergRush one click root.
244 KB/s (23052 bytes in 0.092s)
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[+] Found a GingerBread ! 0x00015118
[*] Scooting ...
[*] Sending 149 zerglings ...
[*] Sending 189 zerglings ...
[-] Hellions with BLUE flames !
remount failed: Operation not permitted
mount: Operation not permitted
mount: Operation not permitted
Unable to chmod /system/bin/sh: Operation not permitted
failed to copy './su' to '/system/bin/su': Permission denied
failed to copy './su' to '/system/bin/su': Permission denied
failed to copy './busybox' to '/system/bin/busybox': Permission denied
Unable to chmod /system/bin: Operation not permitted
Unable to chmod /system/bin/su: No such file or directory
Unable to chmod /system/bin/su: No such file or directory
failed to copy './Superuser.apk' to '/system/app/Superuser.apk': Permission deni
ed
2745 KB/s (92780 bytes in 0.033s)
pkg: /data/local/tmp/androidterm.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
3586 KB/s (279097 bytes in 0.076s)
pkg: /data/local/tmp/Root_Explorer_v2.17.2.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
Your device is now rooted.
Press any key to continue . . .
Click to expand...
Click to collapse
now when it goes to install android terminal and Root Explorer I get errors because they're already installed, but it still wouldn't root even before i had them installed.
I would love any help on how to root this, or at least a point in the right direction in doing this. I know no one has really had success with rooting the Milano on 2.3.4, but i figured with 4.6 million people Someone surely could help.
Thank you so much in advance.
*bump*
Sent from my C5121 using xda app-developers app
I did it! Finally!
Dslrocks10 said:
Hi I have a kyocera Milano that I would love to root but can't seem to find ANY solution to do such.
I would love any help on how to root this, or at least a point in the right direction in doing this. I know no one has really had success with rooting the Milano on 2.3.4, but i figured with 4.6 million people Someone surely could help.
Click to expand...
Click to collapse
I just got my phone from Ting a couple weeks ago and rooted it yesterday.
Unfortunately I can't directly post Outside links (Not at 10 posts yet, and have no idea what else to post about other than this at the moment, which requires a link (For Credit Due Purposes) and I know it will be helpful to people that were as desperate as me for something that was starting to seem rather impossible and no one was paying that much attention to it.), but this is important enough that I'll try to just chop it up - You'll just have to put it back together to go to that site.
This works:
androidforums
.com/milano-all-things
-root/709963-no
-pc-root-method
.html
Not sure why the guide says "Enable usb debugging in Settings, Applications, Development" since you never use the PC, I enabled it anyway, and also enabled to install third party apps, or else Poot won't install, not sure why that isn't on the guide. (Maybe they got mixed up?)
A few things you might want to know:
After hours I finally found the solution. But the terminal still doesn't work for uninstalling ("pm uninstall com.google.android.books.apk" = Failure), you have to do everything though your phone (I'm using the app "RootAppDelete"). The phone roots itself with a third party app called "Poot" using libraries from "Ministro 2"
Before doing this you're gonna need something like 25MBs of storage or so (Can delete everything afterwards with the exception of SuperUser (Can't delete that) to get the space back (Also, you need a app to actually use root actions). - The "Ministro 2" packages are huge for this phone's tiny internal storage! 11MB around)
Make sure to install anything small first and anything big right before the phone gets over 15MB full, because at that time you can't install anything else, with low memory errors.
Another thing that might have helped me when I did this is - back when I couldn't root I made all apps default install to the phone with the android sdk platform-tools (I didn't want to risk anything so I moved Poot, Ministro 2 and SuperUser back to the phone before running Poot. since they default installed to the SD)
"adb shell"
"pm SetInstallLocation 2"
Know its been said elsewhere, but this works with the Milano. Wanted to say that in case you needed the space to use Poot.
And the last problem is after I did all this, now my headphone jack wants to think it has headphones plugged in all the time, If I move the phone around it starts playing on the phone's speaker. It seems like something is lose. Not sure if that was caused by the root (since it wasn't doing it before, and I've never used the headphone jack before) or because there was lose hardware, not sure. Still working on a solution to that, which I found
something similar here, almost looks like a common problem: http://forum.xda-developers.com/showthread.php?t=817872
I would put my proof of doing this have a screen shot of root checker, but alas its an outside link. Understand though.
And as I've read a million times before this, here's a disclaimer: I'm not responsible and use at your own risk.
July 20th 2013
Updated with cyanide2.2, fixing bug that resulted in the su binary being deleted when extracted.
Original Release (bloggers re-source this link): http://www.androidpolice.com/2013/0...band-with-the-newest-ota-1_65k_1027-or-older/
Republic Wireless pushed a new update today, breaking the previous root I released. Here is a new root, that works on all versions of the firmware to date.
Install the app, run the app, press agree, phone will reboot twice, and then you have root. Then install supersu from the market.
APK : attached
Sourcecode: http://github.com/cunninglogic/Cyanide
So quick and easy it took 3 minutes total Thanks
jcase said:
original release (bloggers re-source this link): http://www.androidpolice.com/2013/0...band-with-the-newest-ota-1_65k_1027-or-older/
republic wireless pushed a new update today, breaking the previous root i released. Here is a new root, that works on all versions of the firmware to date.
Install the app, run the app, press agree, phone will reboot twice, and then you have root.
Apk : http://d-h.st/swm
sourcecode: http://github.com/cunninglogic/cyanide
Click to expand...
Click to collapse
thank you!
I was previously rooted on my Defy XT, and had installed busybox. Now I've updated my phone to RW latest, but you're Cyanide utility doesn't work. I'm not sure if it's perhaps busybox related issue, or some other root required app. All the binaries from before the update have stayed in the system, but something isn't running through correctly, because I'm not getting root, and SuperSU is not being installed. Any ideas?
thanks
lancethepants said:
I was previously rooted on my Defy XT, and had installed busybox. Now I've updated my phone to RW latest, but you're Cyanide utility doesn't work. I'm not sure if it's perhaps busybox related issue, or some other root required app. All the binaries from before the update have stayed in the system, but something isn't running through correctly, because I'm not getting root, and SuperSU is not being installed. Any ideas?
thanks
Click to expand...
Click to collapse
Cyanide is made to work on stock, or as stock as possible phones. Alterations surely can break it. Setup adb, get it working with the phone, then PM me.
Are there roms for this thing?
No, there are no ROM's available. You root it, there is no going "back".
However, good job jcase! I keep your cyanide on the phone, ready to launch it. Still having 30 days warranty thou.
tethering
I have the Republic defy XT and would consider rooting if I can then tether my tablet to it while out an about.
I used to have the HTC Hero and rooted with custom ROM and was able to tether my Nexus 7 (wifi version) to it via bluetooth. That gave me internet when away from wifi.
If I root the defy, will I be able to get tether working? Has anyone actually done this? Currently, bluetooth can see and pair with the phone, but won't connect.
Thanks
NO ROOT for BT Tether
jneg123 said:
I have the Republic defy XT and would consider rooting if I can then tether my tablet to it while out an about.
I used to have the HTC Hero and rooted with custom ROM and was able to tether my Nexus 7 (wifi version) to it via bluetooth. That gave me internet when away from wifi.
If I root the defy, will I be able to get tether working? Has anyone actually done this? Currently, bluetooth can see and pair with the phone, but won't connect.
Thanks
Click to expand...
Click to collapse
You do not nned to root the Defy XT to be able to tether. Download and install PDANet for
Install this on phone:
https://play.google.com/store/apps/..._apps#?t=W251bGwsMSwyLDEwOSwiY29tLnBkYW5ldCJd
Install this on tablet:
https://play.google.com/store/apps/...=W251bGwsMSwyLDEsImNvbS5wZGFuZXQudGFibGV0MiJd
The free version restricts speed and HTTPS.
nilesf said:
You do not nned to root the Defy XT to be able to tether. Download and install PDANet for
Install this on phone:
https://play.google.com/store/apps/..._apps#?t=W251bGwsMSwyLDEwOSwiY29tLnBkYW5ldCJd
Install this on tablet:
https://play.google.com/store/apps/...=W251bGwsMSwyLDEsImNvbS5wZGFuZXQudGFibGV0MiJd
The free version restricts speed and HTTPS.
Click to expand...
Click to collapse
I'll give it a shot. Thanks very much for the suggestion!
jneg123 said:
I'll give it a shot. Thanks very much for the suggestion!
Click to expand...
Click to collapse
I tried PDANet and didn't have very good luck. I can get basic internet connection for browsing but run into issues with some apps. I installed the paid version and tested to see if this would help and still no go.
I tried Google Maps and it tracked position just fine. I tried the "Layers" feature to add traffic info and had a message that there wasn't a network connection. This message came up with both the free and paid version.
"No Network Connection" came up again with Words with Friends and the Gmail apps. I didn't test further and got the refund from Google Play. I didn't want to keep testing and then not be able to get a refund.
Any other BT tethering suggestions?
thanks
Thumbs Up!
Just a thumbs up and let you know that your app worked on my RW Defy running the latest build 1_65K_1027. Working just fine and glad to see since I'm coming from my rooted Droid Bionic and missed Call Blocker featured I used all too often.
Thanks, Sorli...
It is not working for me
I received new phone today from RW and it is stock with 1_65K_1027 when I run Cyanide it does not install SuperSU and I do not have root access. I have used this method previously on my old original RW phone. I reran after factory data reset and still same result, not working for me. Any help would be great as I love my old RW phone when it was rooted.
Thanks in advance.
Hmm...not sure really, but figured I reply to your post just to let you know someone is out here, running the same build 1-65K_1027, and successful months ago.
Did you hear back from the Cyanide developer and hopefully he has some notes of interest and what may have changed?
Obviously, I did my installation months ago and hopefully nothing has changed, but you also said you are now using a newer Defy. What happened to your older unit?
Hope you figure it out and I'm actually waiting for a new RW phone. Been waiting a while and may just drop kick RW if they don't come out with something new soon as reported "End of Summer!" in previous Blog posts. Sorli...
daedreamah said:
I received new phone today from RW and it is stock with 1_65K_1027 when I run Cyanide it does not install SuperSU and I do not have root access. I have used this method previously on my old original RW phone. I reran after factory data reset and still same result, not working for me. Any help would be great as I love my old RW phone when it was rooted.
Thanks in advance.
Click to expand...
Click to collapse
Old RW phone locked up and had over-heating issues...I could not use GPS wile plugged in to car charger at the same time. RW swapped phone and new one was sent to me. My old phone I used Cyanide no problems to install and use Titanium Back up to make backups of the pre-installed apps then uninstall them. I performed another Factory data reset from the privacy settings on the phone and then reinstalled Cyanide - still no go for me - does not install SuperSU and I do not have root access.
Thanks for you reply, do you have any suggestions ?
What is weird is my install (x2) went perfectly without problems both times. Test drove on my wife's phone did not have any problems.
Does it work at all...initiate the process, reboot, and then nothing?
May need to document your steps (what seems to work, where it may fail, errors if any, etc) and then email the developer to see what he may have to say and see if he can help. Sorli...
daedreamah said:
Old RW phone locked up and had over-heating issues...I could not use GPS wile plugged in to car charger at the same time. RW swapped phone and new one was sent to me. My old phone I used Cyanide no problems to install and use Titanium Back up to make backups of the pre-installed apps then uninstall them. I performed another Factory data reset from the privacy settings on the phone and then reinstalled Cyanide - still no go for me - does not install SuperSU and I do not have root access.
Thanks for you reply, do you have any suggestions ?
Click to expand...
Click to collapse
Unboxed new phone, activated it, put in old SDCARD with Cyanide on it, Under application settings checked unknown sources, installed via the built in file manager and then ran the app on the phone, Agreed to the warning, phone rebooted then rebooted again. No SuperSu and no root. Downloaded the latest Cyanide and re-installed same results. I have done this before an another RW Defy and no problems like all of you, but this one will not work for me.
Thanks.
daedreamah said:
Unboxed new phone, activated it, put in old SDCARD with Cyanide on it, Under application settings checked unknown sources, installed via the built in file manager and then ran the app on the phone, Agreed to the warning, phone rebooted then rebooted again. No SuperSu and no root. Downloaded the latest Cyanide and re-installed same results. I have done this before an another RW Defy and no problems like all of you, but this one will not work for me.
Thanks.
Click to expand...
Click to collapse
This could have been silently patched some how, I am getting other report of it not working on firmware that I have confirmed it to work on. I will release a new root around Aug 11th. Possibly sooner if someone put one of these phones in my hands for a little while.
jcase said:
This could have been silently patched some how, I am getting other report of it not working on firmware that I have confirmed it to work on. I will release a new root around Aug 11th. Possibly sooner if someone put one of these phones in my hands for a little while.
Click to expand...
Click to collapse
If I can be of any help via trial and error please let me know. At this time the RW is my only phone otherwise I would send it in...I have managed to get it to communicate via ADB using the adb devices command and it responded. If you want to test I am up for it. Thanks
jcase said:
This could have been silently patched some how, I am getting other report of it not working on firmware that I have confirmed it to work on. I will release a new root around Aug 11th. Possibly sooner if someone put one of these phones in my hands for a little while.
Click to expand...
Click to collapse
Same issue here, it appears that the permissions of the symlink are being changed and not the target of the symlink.
I changed the app, so that it would have to be launched 2x instead of doing the 2nd step automatically.
Here's what I saw.
/system/etc/install-recovery.sh did not exist
$ ls -l
ls -l
-rw-r--r-- root root 135246 2013-07-11 22:41 last_alog_system_20130711_224159
-rw-r--r-- root root 138909 2013-07-11 22:41 last_alog_events_20130711_224159
-rw-r--r-- root root 144210 2013-07-11 22:41 last_alog_radio_20130711_224159
-rw-r--r-- root root 139601 2013-07-11 22:41 last_alog_main_20130711_224159
-rw-rw-rw- app_98 app_98 2 2013-07-11 22:41 onboot
lrwxrwxrwx app_98 app_98 2013-07-11 22:41 with_love_from_jcase -> /system/etc
lrwxrwxrwx app_98 app_98 2013-07-11 22:41 i_like_pie -> /system/etc/install-recovery.sh
/system
drwxr-xr-x root root 1980-01-05 17:00 etc
Tried modifying the sym link to a file that did exsit.
lrwxrwxrwx shell shell 2013-07-11 22:54 with_love_from_dlm -> /system/etc/init.qcom.post_boot.sh
permissions on /system/etc/init.qcom.post_boot.sh were unchanged.
I could get you remote access to the phone, sending may be an option.
I'm ready to root this again, please contact me via jcase at cunninglogic dot com.
Even if I can't find a root I can release, I will guarantee leaving the phone rooted when I am done testing
DewJunkie said:
Same issue here, it appears that the permissions of the symlink are being changed and not the target of the symlink.
I changed the app, so that it would have to be launched 2x instead of doing the 2nd step automatically.
Here's what I saw.
/system/etc/install-recovery.sh did not exist
$ ls -l
ls -l
-rw-r--r-- root root 135246 2013-07-11 22:41 last_alog_system_20130711_224159
-rw-r--r-- root root 138909 2013-07-11 22:41 last_alog_events_20130711_224159
-rw-r--r-- root root 144210 2013-07-11 22:41 last_alog_radio_20130711_224159
-rw-r--r-- root root 139601 2013-07-11 22:41 last_alog_main_20130711_224159
-rw-rw-rw- app_98 app_98 2 2013-07-11 22:41 onboot
lrwxrwxrwx app_98 app_98 2013-07-11 22:41 with_love_from_jcase -> /system/etc
lrwxrwxrwx app_98 app_98 2013-07-11 22:41 i_like_pie -> /system/etc/install-recovery.sh
/system
drwxr-xr-x root root 1980-01-05 17:00 etc
Tried modifying the sym link to a file that did exsit.
lrwxrwxrwx shell shell 2013-07-11 22:54 with_love_from_dlm -> /system/etc/init.qcom.post_boot.sh
permissions on /system/etc/init.qcom.post_boot.sh were unchanged.
I could get you remote access to the phone, sending may be an option.
Click to expand...
Click to collapse