Can someone post a current kernel version screenshot off of their phone please..
Update: (11/08/2014)
Instructions:
Grab file at --> https://drive.google.com/file/d/0B31X8bH_5Gl-NmExWmhlbzJ5T3c/view?usp=sharing
adb push root /data/local/tmp
adb shell
cd /data/local/tmp
chmod 777 root
./root
If you get # symbol for prompt, you have root.
Let me know the results please.. I am trying to do this without actually having a phone, I might as well go get one today though, because this might end up being to painful this way..
Update (11/15/2014):
Well, at this point I have been able to establish a remote shell to my PC. This might not sound like much, but if your on the phone and run my binary it will establish a remote shell to anywhere that you specify where a valid listener is listening on an IP and port that is specified. Malware people would go nuts with this. Why? Because with this essentially I could grab all personal information from your SDcard and other areas without your permission. Pretty much run any command that you can do now locally, I could do on your phone remotely. So, I am seeing now what leverage points I might be able to make with this..
Gl
AngelsPunishment said:
Gl
Click to expand...
Click to collapse
Ohhh. yummy....
Is this root already available??
SM-N910V
http://download.chainfire.eu/590/CF-Root/CF-Auto-Root/CF-Auto-Root-trltevzw-trltevzw-smn910v.zip
Am I missing something or has chainfire already accomplished this.. ?
gatesjunior said:
SM-N910V
http://download.chainfire.eu/590/CF-Root/CF-Auto-Root/CF-Auto-Root-trltevzw-trltevzw-smn910v.zip
Am I missing something or has chainfire already accomplished this.. ?
Click to expand...
Click to collapse
I thought that was for the DE (Developer Edition).
Nooter said:
I thought that was for the DE (Developer Edition).
Click to expand...
Click to collapse
I don't think so. Look at your model, the developer edition I believe would be a different model..
Well, hold on, maybe.. It might have an identical model number. That would be strange...
gatesjunior said:
I don't think so. Look at your model, the developer edition I believe would be a different model..
Well, hold on, maybe.. It might have an identical model number. That would be strange...
Click to expand...
Click to collapse
It's for the Dev edition. It was listed as the retail version model number but it is indeed for the dev version.
Someone want to try this
Instructions:
Grab file at --> https://drive.google.com/file/d/0B31X8bH_5Gl-NmExWmhlbzJ5T3c/view?usp=sharing
adb push root /data/local/tmp
adb shell
cd /data/local/tmp
chmod 777 root
./root
Let me know the results please..
Can you tell us how this method achieves root?
ronaldheld said:
Can you tell us how this method achieves root?
Click to expand...
Click to collapse
Well, it is essentially overflowing to try and gain root, it will not in any way cause any permanent change to your phone or flag anything.
gatesjunior said:
Instructions:
Grab file at --> https://drive.google.com/file/d/0B31X8bH_5Gl-NmExWmhlbzJ5T3c/view?usp=sharing
adb push root /data/local/tmp
adb shell
cd /data/local/tmp
chmod 777 root
./root
Let me know the results please..
Click to expand...
Click to collapse
did you fo this? what did it achieve?
mrnick81 said:
did you fo this? what did it achieve?
Click to expand...
Click to collapse
No, I do not have the phone yet.. Probably go out tonight and get it. But I wanted to start work and get things moving..
Thank you for the attempt!
Has anyone tried it yet? If not I am will give it a whirl.
Chuckleb0ne said:
Has anyone tried it yet? If not I am will give it a whirl.
Click to expand...
Click to collapse
exactly, not going to adb an unproven method
I'll give it a try in a second.
---------- Post added at 03:52 PM ---------- Previous post was at 03:37 PM ----------
Where do i place the root file on my computer? It stops me at (cannot stat root, No such file or directory).
I have a windows computer with adb installed and everything.
gatesjunior said:
No, I do not have the phone yet.. Probably go out tonight and get it. But I wanted to start work and get things moving..
Click to expand...
Click to collapse
Ok, so here is the results.
NM. same results as above.
mrlaigle said:
NM. same results as above.
Click to expand...
Click to collapse
O.k. guys, well that was shot one with no phone. Now I have phone in hand All mine, precious...
Let me know if you need restore tar.
Related
First off, as always, if this causes any damage, or loss of anykind anyhow anyway I am not at fault, don't blame me.
So you rooted? But no longer want root? or want to downgrade to 1.5 with an ruu? or want to flash one of the PB00IMG like the root one with an engineering bootloader?
Tonight I made another custom misc.img, it is attached to this post. You will also need flash_image which can be found here. http://www.multiupload.com/KS2JCAMGBH
Run these commands as root:
Code:
adb push flash_image /data/local/flash_image
adb push misc.img /data/local/misc.img
adb shell chmod 777 /data/local/flash_image
adb shell /data/local/flash_image misc misc.img
Now you can flash any known (to me) ruu or PB00IMG
Cool beans and thx for your continued help even tho you don't have a Eris anymore.
korben dallas said:
Cool beans and thx for your continued help even tho you don't have a Eris anymore.
Click to expand...
Click to collapse
I have 1 motodroid, 1 eris w/ no service and 1 eris with service (Wife), I haven't been able to do dev work on the eris til recently, no root.
That has changed
Great job .thanks for working on the eris
jcase you are a god among eris user keep up the good dev'ing
jcase said:
I have 1 motodroid, 1 eris w/ no service and 1 eris with service (Wife), I haven't been able to do dev work on the eris til recently, no root.
That has changed
Click to expand...
Click to collapse
Oh my bad thought you said while back it had a bad radio and you got a Droid. I guess no more assuming lol
The hits keep on coming!
I suppose this should work equally well for PB00IMG.ZIP installs (from the corresponding RUUs), yes?
This should make life easier for "unrooters"; now if there just some way to convince them that there is really only 1 reason to unroot a phone
bftb0
my only reason for unrooting is sending my phone back ......which i will be doing this weekend..... refurb is suppose to be here today
thanks jcase ....thanks for the continued work on the eris .....
rvpartsguy said:
my only reason for unrooting is sending my phone back ......which i will be doing this weekend..... refurb is suppose to be here today
thanks jcase ....thanks for the continued work on the eris .....
Click to expand...
Click to collapse
Exactaly i just got my beautiful refurb
BTW EVERYONE,......,
if u have a custom boot screen u will want to take it off first or you will be locking it in
Sent from my Eris using XDA App
korben dallas said:
Oh my bad thought you said while back it had a bad radio and you got a Droid. I guess no more assuming lol
Click to expand...
Click to collapse
It did, the one I used. It was the only non leak one I had. Puit kinks in everything.
When I try it it just keeps saying push: not found.
The commands are the same thing for OSX, right? Drag tools to Terminal and then just copy and paste those lines of commands?
hackthis02 said:
When I try it it just keeps saying push: not found.
Click to expand...
Click to collapse
Yeah dude, those instructions didn't work for me either. This is what I did (and it worked):
Code:
adb push flash_image /data/local/flash_image
adb push misc.img /data/local/misc.img
adb shell chmod 777 /data/local/flash_image
adb shell flash_image misc /data/local/misc.img
do we put the two files into the SDK/Tools folder? or are we putting them on the SD card and running these commands while the phone is in recovery? Sorry I'm a little new to this.
derickmc said:
do we put the two files into the SDK/Tools folder? or are we putting them on the SD card and running these commands while the phone is in recovery? Sorry I'm a little new to this.
Click to expand...
Click to collapse
Tools folder.
hey guys, sorry but i'm really confused as to what to do here. i'm running evil eris and i want to downgrade to 2.1leak to get a refurb eris. i'm a complete noob with all the sdk stuff. i've gotten as far as putting the two files in the sdk/tools folder, lol. if someone could help me out with this, it'd be greatly appreciated...thanks a ton.
Just flash the pbooimg.zip back onto the phone. Out should be good from there.
Sent from my Eris using XDA App
niether worked for me. the original post reads.. error opening misc.img: no such file or directory...your method reads..error reading : /data/loca/misc.img headed : Is a directory
lil_dez said:
Yeah dude, those instructions didn't work for me either. This is what I did (and it worked):
Code:
adb push flash_image /data/local/flash_image
adb push misc.img /data/local/misc.img
adb shell chmod 777 /data/local/flash_image
adb shell flash_image misc /data/local/misc.img
Click to expand...
Click to collapse
Me! Me ! Me! too please
Hey I am not understanding what to do either. I have a rooted eris that the screen started flaking out so i Have to send it back.
I rooted alright and I have a basic understanding of the recovery stuff. But could you guys either tell me what to do from scratch on this one or point me in the right direction.
I've been searching the forum for 2 weeks trying to learn how. My kids are teasing me now cuz all I do at home try to learn about this stuff. Well anyway I would appreciate some help.
I have just opened a can of worms
Wow!!! I truly did not realize the full extent of what yous guys are doing on this website. You are smart people!!! hahahaha I opened a can of worms and can't get it shut again.
You guys are the ones writing and developing all kinds of programs.
i hope you guys arent taking this the wrong way!!!
I honestly didnt realize till I researched and found the HTC Developers center.
I have no buisness trying to do any of this stuff!
If some can help me out I would appreciate it!!!!!!
hey all. anyone know if we can turn s-off on wildfire yet? kninda frustraiting... its root but not really root
bassmonkey said:
hey all. anyone know if we can turn s-off on wildfire yet? kninda frustraiting... its root but not really root
Click to expand...
Click to collapse
To me this is a 100% genuine "WTF?" statement... I don't get what you mean mate, please explain..
bassmonkey said:
hey all. anyone know if we can turn s-off on wildfire yet? kninda frustraiting... its root but not really root
Click to expand...
Click to collapse
Not yet till Alpharev v2 realesed
Sent from my HTC Legend
gyroing said:
Not yet till Alpharev v2 realesed
Sent from my HTC Legend
Click to expand...
Click to collapse
Thanks dude, I've just came from having a totally customized hero
N despite the screen rez I'm loving this phone but no access to system folder is pants
Sent from my HTC Wildfire using XDA App
niksakl said:
To me this is a 100% genuine "WTF?" statement... I don't get what you mean mate, please explain..
Click to expand...
Click to collapse
As far as I can tell its a new security thing HTC have added to the hboot, basically makes the system folder read only even with root (think that's correct??)
Sent from my HTC Wildfire using XDA App
bassmonkey said:
Thanks dude, I've just came from having a totally customized hero
N despite the screen rez I'm loving this phone but no access to system folder is pants
Sent from my HTC Wildfire using XDA App
Click to expand...
Click to collapse
Well , it's not totally locked down. You can access it (Read and write) if you boot into recovery. Not the smoothest solution but it works. Also there is AUFS but i don't think i have gotten that to work at all. Maybe it needs to be enabled, haven't really checked but i boot into recovery when i need to change something.
You can change the /system permission with a terminal emulator as Better Terminal Pro on the phone or by the phone connected to your pc via
Code:
> adb shell
doing in both cases:
Code:
# chmod -R 777 /system
when you restart the phone, /system will be reset to the original 755 permissions.
thanks for the response guys
71baker said:
Well , it's not totally locked down. You can access it (Read and write) if you boot into recovery. Not the smoothest solution but it works. Also there is AUFS but i don't think i have gotten that to work at all. Maybe it needs to be enabled, haven't really checked but i boot into recovery when i need to change something.
Click to expand...
Click to collapse
how do you do it through recovery? im guessing thatd be with adb?
Tetractys said:
You can change the /system permission with a terminal emulator as Better Terminal Pro on the phone or by the phone connected to your pc via
Code:
> adb shell
doing in both cases:
Code:
# chmod -R 777 /system
when you restart the phone, /system will be reset to the original 755 permissions.
Click to expand...
Click to collapse
in terminal i entered su
chmod -R777/system
which then gave me; usage: chmod <mode> <file>
i then entered; /system and got permission denied??
bassmonkey said:
thanks for the response guys
how do you do it through recovery? im guessing thatd be with adb?
in terminal i entered su
chmod -R777/system
which then gave me; usage: chmod <mode> <file>
i then entered; /system and got permission denied??
Click to expand...
Click to collapse
If you have written the command exactly as you report is obvious that the os return an error. try to write as i did... (with blanks in between)
of course your phone had to be passed the Unrevoked 3.21 procedure!
http://forum.xda-developers.com/forumdisplay.php?f=701
Anyway if you are not very much concerned in linux shell commands, i would suggest you to wait another more automatic method.
Tetractys said:
If you have written the command exactly as you report is obvious that the os return an error. try to write as i did... (with blanks in between)
of course your phone had to be passed the Unrevoked 3.21 procedure!
http://forum.xda-developers.com/forumdisplay.php?f=701
Anyway if you are not very much concerned in linux shell commands, i would suggest you to wait another more automatic method.
Click to expand...
Click to collapse
lol.'not concerned' very diplomatic yeah, kind of a windoze boy n therefore not really up on linux.
i did root with 3.21 and i tried the chmod command with all the spaces and terminal just gave me 'bad mode' (it also gave me bad mode when i tried adb) so i tried as i posted. bummer but nevermind, come on alpharev 2
71baker said:
Also there is AUFS but i don't think i have gotten that to work at all. Maybe it needs to be enabled, haven't really checked but i boot into recovery when i need to change something.
Click to expand...
Click to collapse
You can enable AUFS in Jacob's latest kernel by typing "aufs --enable" in a terminal emulator app in android, and then reboot the phone.
Anyony give it a try?
How to downgrade and root 2.43.661.1 and up:
http://androidforums.com/desire-hd-all-things-root/382082-how-downgrade-root-2-43-661-1-up.html
I'll try it later this week (see my posts over there)...
wat abt 2.42 ??????????????
And 2.50.405.2? It ins´t for this?
dwyaneW said:
And 2.50.405.2? It ins´t for this?
Click to expand...
Click to collapse
Apparently it works too, this guy has that build number: http://androidforums.com/desire-hd-...downgrade-root-2-43-661-1-up.html#post2995693
Finally we have a way to downgrade from 2.50 !!!
Hi All !
I tested it and it worked, so here are the things you need:
Download the downgrade.zip
An SD card with the 1.32 PD89IMG.zip
Connect your phone in Charge Only mode with USB Debugging enabled.
Run these commands with enter after every line:
adb push fre3vo /data/local/tmp
adb push misc_version /data/local/tmp
adb shell chmod 777 /data/local/tmp/fre3vo
adb shell chmod 777 /data/local/tmp/misc_version
adb shell /data/local/tmp/fre3vo -debug -start F0000000 -end FFFFFFFF
If you success you will see this message:
Potential exploit area found at address (maybe fbb6b600:1a00 or something else).
Exploiting device...
Then run the following:
adb shell (you will have to get the "#"
/data/local/tmp/misc_version -s 1.31.405.3
adb reboot bootloader
Run the ROM setup and you will done
This method is the same as CubZ
im all over both threads, please post offsets at which the exploit was found on your device.
so as we can narrow down the searches to make a quick one click method.
JSLEnterprises said:
This method is the same as CubZ
im all over both threads, please post offsets at which the exploit was found on your device.
so as we can narrow down the searches to make a quick one click method.
Click to expand...
Click to collapse
Potential exploit area found at address (maybe fbb6b600:1a00 or something else). This is the address of my phone.
great
great
great
great
greatgreat
CONFIRMED on Telus Desire HD running 2.43!
Follow the instructions on this link here:
http://driphter.com/index.php?topic=3867.0
I just completed Step 7. Step 8 will have to wait until I get home, since I don't have administrative access on this computer, so I can't run the batch to turn off Radio S-Off yet. BUT my phone is rooted now. Now running on Android 2.2 build 1.32.405
Also, just perm rooted using Visionary+. Just tested it with adb shell and got the magical #.
Thank you JSL from Dripther.com!
Totally works! No problems at all on my unbranded DHD.
JSLEnterprises said:
This method is the same as CubZ
im all over both threads, please post offsets at which the exploit was found on your device.
so as we can narrow down the searches to make a quick one click method.
Click to expand...
Click to collapse
It found an exploit area at fbb7f800:1800 on my Telus-branded Desire HD.
EDIT: I've tried the process about 4 or 5 times, and everything goes fine until it boots into the bootloader. Whenever it gets to that stage, nothing appears to get flashed and my phone goes right back to the way it was. Any particular reason for that?
Finaly, i give it a try.
Sent from my Desire HD using XDA Premium App
Now I downgraded 2.50 build !!
We also have a giude from CuBz90 in "Desire HD Android Development" forum: http://forum.xda-developers.com/showthread.php?t=1152233
Works perfect, custom rom, android revolution installed
Sent from my Desire HD using XDA Premium App
Command_HDX said:
We also have a giude from CuBz90 in "Desire HD Android Development" forum: http://forum.xda-developers.com/showthread.php?t=1152233
Click to expand...
Click to collapse
I had the exact same luck with that. I've used this exact same SD card with my old HTC Hero, so it's not the card. Could it just be something as simple as me having a corrupted download of PD98IMG.zip? I'll check the MD5 and report back.
This works for 2.50xxx. Just did it. If it fails 1st time, unplug and try again.
Sent from my Motorola Startac running Atari 2600 software!
AndroidPolice has the downloads and instructions for a new method of rooting. Just tested it, it *does* in fact work.
You will need ADB access (which, if you've rooted before, you probably already have).
I can confirm this works.
Is there any reason to do this if we are still rooted and have the secured rooted ROM installed? Should I wait until/if Amazon pushes the updated on top of my rooted 6.2.1?
Noob questions: Assume that the app goes on the KF of course. Where do the Superuser files get placed? Already have Superuser on the KF from previous root so can I skip this step?
Thanks!
cant find the drivers for my kindle??????? need help
i keep getting devce not found.....
movieaddict said:
cant find the drivers for my kindle??????? need help
i keep getting devce not found.....
Click to expand...
Click to collapse
I am not sure if we are talking about the same thing but I think they are included in the Kindle Fire Utility.
Masssy said:
I am not sure if we are talking about the same thing but I think they are included in the Kindle Fire Utility.
Click to expand...
Click to collapse
run install_drivers.bat from Kindle Fire Utility 0.6
Nice. Just regain root for 6.2.1.
did that , nothing
Not working here. Noticed that when I hit Root on the new app on the KF, I get this info which was not in the directions. Anyone else? Should these steps be done and in what sequence combined with the published instructions?
Final Steps
On your computer run the following commands:
adb kill-server
adb root
adb shell
Enjoy.
Hellcat6 said:
Not working here. Noticed that when I hit Root on the new app on the KF, I get this info which was not in the directions. Anyone else? Should these steps be done and in what sequence combined with the published instructions?
Final Steps
On your computer run the following commands:
adb kill-server
adb root
adb shell
Enjoy.
Click to expand...
Click to collapse
only one not in the instructiosn was adb kill-server and its not really needed.
adb root <-- what you likely missed
Root was made (I guess...).
But I still can't install the market. Because I can't mount system to R/W (with root manager or kindle utility).
Is it normal? :/
Cholo981 said:
Root was made (I guess...).
But I still can't install the market. Because I can't mount system to R/W (with root manager or kindle utility).
Is it normal? :/
Click to expand...
Click to collapse
root explorer mounts the system in r/w just fine.
this root works as advertised
ota rootkeeper still works for a temp unroot to watch amazon video.
as far as i can tell everything is the same except we're using superuser app so you have to allow each app permission, it's the only real change i can see
---------- Post added at 07:43 PM ---------- Previous post was at 07:43 PM ----------
jcase said:
only one not in the instructiosn was adb kill-server and its not really needed.
adb root <-- what you likely missed
Click to expand...
Click to collapse
i needed to use the kill-server command to get my computer to pick up the kindle after the update... others may as well so it's good info
screwyluie said:
root explorer mounts the system in r/w just fine.
this root works as advertised
ota rootkeeper still works for a temp unroot to watch amazon video.
as far as i can tell everything is the same except we're using superuser app so you have to allow each app permission, it's the only real change i can see
---------- Post added at 07:43 PM ---------- Previous post was at 07:43 PM ----------
i needed to use the kill-server command to get my computer to pick up the kindle after the update... others may as well so it's good info
Click to expand...
Click to collapse
Thanks for the suggestion re: OTA Rootkeeper! Rooted earlier today, but had trouble unrooting to watch videos, and now that's solved!
I haven't got my fire yet but these instructions don't seem very clear; do I have to keep the tablet connected to the PC at all times? Or do I execute the sudo app on the tablet, and then connect it to the PC so I can run the adb commands?
screwyluie said:
root explorer mounts the system in r/w just fine.
Click to expand...
Click to collapse
I meant root explorer (I wrote root manager indeed).
If I click on the "mount R/W" button, it doesn't do anything. :/
EDIT: Done. I had to push vending.apk by adb... dunno why.
jcase said:
only one not in the instructiosn was adb kill-server and its not really needed.
adb root <-- what you likely missed
Click to expand...
Click to collapse
Working now! Figured out that when installing the script in ADB from the directions, I was not leaving a space before each instance of "/system". Duh. Got Market working again as well. Thanks Developers!
Hellcat6 said:
Not working here. Noticed that when I hit Root on the new app on the KF, I get this info which was not in the directions. Anyone else? Should these steps be done and in what sequence combined with the published instructions?
Final Steps
On your computer run the following commands:
adb kill-server
adb root
adb shell
Enjoy.
Click to expand...
Click to collapse
You need to finish the job with these steps (taken from the androidpolice post):
Code:
adb remount
adb push su /system/xbin/su
adb shell chown 0.0 /system/xbin/su
adb shell chmod 06755 /system/xbin/su
adb install com.noshufou.android.su-1.apk
adb reboot
Help! I'm stuck at this step:
adb install com.noshufou.android.su-1.apk
The prompt says it can't find the file. What am I missing?
Thanks!
---------- Post added at 04:47 PM ---------- Previous post was at 04:01 PM ----------
I think I figure it out. The Fire is rooted again. I just need to fiddle with OTA Rootkeeper to be able to watch video streaming again.
Thank you for this thread.
I can run all the steps i just gotta be able to remove the original superuser app that i had before this one. Can someone please tell me how to go about this.
So I'll update randomly...
boot.img and recovery.img -> https://drive.google.com/file/d/0B5QYBzdG6RuyZy1TSHc2VDVhY2M/view?usp=sharing
temp root:
Code:
adb push root /data/local/tmp
adb push wpoff /data/local/tmp
adb push fbunlock /data/local/tmp
adb push recovery.img /data/local/tmp
adb push boot.img /data/local/tmp
adb shell
$ [COLOR="Red"]chmod 755 /data/local/tmp/root[/COLOR]
$ [COLOR="Red"]chmod 755 /data/local/tmp/wpoff[/COLOR]
$ [COLOR="Red"]chmod 755 /data/local/tmp/fbunlock[/COLOR]
$ /data/local/tmp/root
...
#
defeat WP:
Code:
# /data/local/tmp/wpoff --unprotect-all
check WP status(optional):
Code:
# /data/local/tmp/wpoff --dump
If you see it's all zeroes there it means good, or if there are many 5555 it means NG.
unlock bootloader:
Code:
# /data/local/tmp/fbunlock
install TWRP and patched boot:
Code:
# dd if=/data/local/tmp/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
# dd if=/data/local/tmp/boot.img of=/dev/block/platform/msm_sdcc.1/by-name/boot
install SuperSU:
Code:
FLASH SUPERSU LIKE OLD DAYS
Why patch boot?
Cos MIYABI stops ptrace, some apps depends on it won't work properly.
Chinese here:
禁止转载到国内论坛，禁止用于商业用途。日版不会有的。
Note:
a. Remember to rename recovery.00X.zip to recovery.zip.00X before unzipping!
b. If you don't flash boot.img before install SuperSU, you will end up in boot loop. To restore, delete /system/xbin/daemonsu.
Attachments will be uploaded soon.
Hi tewilove, many thanks for publishing this. Amazing work! And a big time saver
tewilove tnx allot !!
hey some one know how can i put su inside in system and then to use SuperSU ?
thank you a lot
thanks but i can not use root app and super su can not install bin su
thank you for your help
tewilove said:
Tested with a 306SH with SW version S4081.
How to:
https://youtu.be/UJs7ruckGgc
This is v1, since the shell code has to be improved yet(WIP).
It only obtains temp root with kernel context. The left things are changing to init context, disable mmc_protect_part, disable miyabi LSM.
There might be v2, which solves all above, if I have time.
And it also works with many other devices.
For example, 305SH, MI4C, SH-01G.
If it keeps crashing, it should be my hard coded offsets.
PS: Please don't reshare this thread.
PS: Chinese: 请不要转载到贴吧，论坛，谢谢。
Click to expand...
Click to collapse
thank you for your help 谢谢某因幡分享
Please I'd like to know how you did that.could you be more clear, a step by step maybe?
Sent from my D6616 using XDA Free mobile app
salmanaman said:
Please I'd like to know how you did that.could you be more clear, a step by step maybe?
Sent from my D6616 using XDA Free mobile app
Click to expand...
Click to collapse
you can watch the video that tewilove make for us .. but we need to wait when some one unlock protect bcs after you restart phone root will disappear..
tewilove said:
Tested with a 306SH with SW version S4081.
Click to expand...
Click to collapse
How can I know that I got the temporary root? Is this step in the input ID?
all step working on my 305sh like youtube video but supersu not working and root checker say me no rooted
soudara said:
all step working on my 305sh like youtube video but supersu not working and root checker say me no rooted
Click to expand...
Click to collapse
yes we know about this .. i try to remount system ( with this command : busybox mount -o remount,rw /system) to get permission but my device is restart when i try .. maybe its from this write protection that @tewilove tell us .. if he can tell us how we can install su in system if its possible for now .. ?
ok so for the moment is useless ?
soudara said:
all step working on my 305sh like youtube video but supersu not working and root checker say me no rooted
Click to expand...
Click to collapse
me too?maybe just kernel root??
---------- Post added at 12:48 PM ---------- Previous post was at 12:31 PM ----------
loonbg said:
yes we know about this .. i try to remount system ( with this command : busybox mount -o remount,rw /system) to get permission but my device is restart when i try .. maybe its from this write protection that tewilove tell us .. if he can tell us how we can install su in system if its possible for now .. ?
Click to expand...
Click to collapse
yea?rootxplore and xposed said no root?
I don't think that folks are understanding what "temp" root means. This solution allows you to achieve root for the current shell session. This does not install the additional binaries to allow other applications to use root access.
With that being said, I am wondering if we can use this temporary elevated access to correct the vulnerability outlined in CVE-2015-1474 affecting /system/lib/libui.so that Sharp has neglected to address in previous OTA updates. The only "corrected" libui.so that I have been able to locate was compiled for v5.0.1 so I am afraid that file would not be compatible with this earlier version of Android on the 306SH. I am not really savvy with in depth programming to be able to fully investigate this and develop a viable solution... anyone who would be able to point me in the right direction would receive many thanks. :banghead:
My apologies if this should have been posted in a separate thread.
awesom! it worked in my 306sh with root permission acquired in shell.
can you use root app and install super su ?
Write protection is keeping us from remounting /system as rw. This prevents us from doing anything that would have any type of impact on the current situation. I want to experiment with attempting to mount partitions with the device powered off... but my device is encrypted so I am unable to access the shell with device off until I perform a factory reset. I am planning on doing that tonight so hopefully I will be able to report back with more information soon.
Sent from my 306SH
soudara said:
can you use root app and install super su ?
Click to expand...
Click to collapse
No. We are working on it though.
On another note, I can't get this temp root to work.
Video of what happens is linked. (too large to attach)
https://mega.co.nz/#!blNTjbhS!p2ljioY_43xlWkpu3EWpj8LvfMVP5eushZT23KLPASk
TechInMD said:
Write protection is keeping us from remounting /system as rw.
Click to expand...
Click to collapse
So I assume, from the quoted text, you have tried mounting /system as rw while in the temp root shell session?
Yes. I tried using the mount command both directly from the root shell prompt plus I tried using busybox to mount also. There seem to be slight variations between them. Also, not sure if it is relevant but I attempted it both through adb and in terminal on the device. I can get to the root prompt but not further.
Sent from my 306SH