Related
I'm trying to perm root my mytouch 4g using Visionary
I have android 2.2.1 and have successfully temp rooted using Visionary
I download the root folder from HERE
I put them in the root of the SD card and open up Terminal Emulator and type in
su
cd /sdcard/root
sh root.sh
when I type the first line (su) I get the # and am told that Terminal Emulator has been granted superuser permissions.
when I type in the second line (cd /sdcard/root) I get this message
cd: can't cd to /sdcard/root
What could be causing this?
Thanks
Jonathan
The "cd" command is a "change directory" command, and there is no directory called "root" on your SD card, because either you haven't unzipped what you downloaded, or you unzipped it in the wrong place.
Unzipping what you downloaded creates a directory (or a "folder", if you're a Windows user) called "root" that has several files in it -- a kernel module and a script, if I remember correctly. The script loads the kernel module and makes a call to it in order to set S Off.
thank you much, I think I figured out the problem. I'll try again later and see what happens. I'll post back with the results later. Thanks again!
Jonathan
NOTE: Ok, I can now run through the
su
cd /sdcard/root
sh root.sh
commands but when it's done and I check for s-off I don't have it (I still have s-on)
I've tried this twice to no avail. any advise?
i am having the same problem. i've tried this method about 15 times, mostly with visionary r14, but also a couple times with r11. i have also tried the gfree method a couple times as well via the semi-automated method. no s=off!
i have a new MT4G direct from phone upgrade order. i've read of others who have rooted the MT4G before multiple times, but can't do it now with a new phone. i'm wondering if it's something HTC has changed with the newest releases.....
kenrippy said:
i am having the same problem. i've tried this method about 15 times, mostly with visionary r14, but also a couple times with r11. i have also tried the gfree method a couple times as well via the semi-automated method. no s=off!
i have a new MT4G direct from phone upgrade order. i've read of others who have rooted the MT4G before multiple times, but can't do it now with a new phone. i'm wondering if it's something HTC has changed with the newest releases.....
Click to expand...
Click to collapse
HTC was going to install a measure that would prevent "rage methods" from working on their phones. How ever, none of the tech blogs are reporting that this has been rolled out. So i doubt that is the case.
make sure the its set up as sdcard/root. If you've just extracted the folder and copied the extraction to the sdcard it's not set properly.
neidlinger said:
HTC was going to install a measure that would prevent "rage methods" from working on their phones. How ever, none of the tech blogs are reporting that this has been rolled out. So i doubt that is the case.
make sure the its set up as sdcard/root. If you've just extracted the folder and copied the extraction to the sdcard it's not set properly.
Click to expand...
Click to collapse
yes, i understand the root folder in the root of the sdcard, and not 2 root folders. (sdcard/root/root)
like i mentioned, i read posts from a couple people on here with the same problems with new mt4g's after having done it multiple times before with success.
kenrippy said:
yes, i understand the root folder in the root of the sdcard, and not 2 root folders. (sdcard/root/root)
like i mentioned, i read posts from a couple people on here with the same problems with new mt4g's after having done it multiple times before with success.
Click to expand...
Click to collapse
then set up the ADB (see my sig) and do it the long way.
neidlinger said:
then set up the ADB (see my sig) and do it the long way.
Click to expand...
Click to collapse
after doing that, would i start on #4 in this guide?
http://forum.xda-developers.com/showthread.php?t=858996
kenrippy said:
after doing that, would i start on #4 in this guide?
http://forum.xda-developers.com/showthread.php?t=858996
Click to expand...
Click to collapse
nope you would start @ number 1.
you need to download those files and check the MD5SUM of every download load. the files need to be PERFECT for it to work correctly.
and i cannot stress enough. take your time and read directions. Read through the list a few times and make sure you have a good understanding of what you are doing. Doing that wrong can make your phone an expensive paper weight.
instead of pushing stuff to the "SDK tools folder" you store it to the ADB folder TrueBlue had you create in his walkthrough. And make sure to change your target folder to "c:\adb".
and remember you are choosing to do this. so if you screw it up. it's on your shoulders not mine.
neidlinger said:
nope you would start @ number 1.
you need to download those files and check the MD5SUM of every download load. the files need to be PERFECT for it to work correctly.
and i cannot stress enough. take your time and read directions. Read through the list a few times and make sure you have a good understanding of what you are doing. Doing that wrong can make your phone an expensive paper weight.
instead of pushing stuff to the "SDK tools folder" you store it to the ADB folder TrueBlue had you create in his walkthrough. And make sure to change your target folder to "c:\adb".
and remember you are choosing to do this. so if you screw it up. it's on your shoulders not mine.
Click to expand...
Click to collapse
thanks for all the help/info. i'll hold off for a while to see what else unfolds in the coming weeks in regards to alternate root methods. i don't want to brick this thing, just to get it rooted.
kenrippy said:
thanks for all the help/info. i'll hold off for a while to see what else unfolds in the coming weeks in regards to alternate root methods. i don't want to brick this thing, just to get it rooted.
Click to expand...
Click to collapse
The way this phone is made it's going to be pretty difficult to write a "one click s=off" program.
If you are wanting the benefits of being rooted you can always use VISIONary.apk when you need the root features like AD-HOC tethering or Screen Shots.
neidlinger said:
The way this phone is made it's going to be pretty difficult to write a "one click s=off" program.
If you are wanting the benefits of being rooted you can always use VISIONary.apk when you need the root features like AD-HOC tethering or Screen Shots.
Click to expand...
Click to collapse
what i'd really like to do is remove some bloatware and demo games. (not just hide them) any way to do that aside from perm root?
kenrippy said:
what i'd really like to do is remove some bloatware and demo games. (not just hide them) any way to do that aside from perm root?
Click to expand...
Click to collapse
not really. As soon as you reboot they'll pop right back up.
ok thanks.
Two things.
1. I've decided to put off perm rooting until I can understand adb and use it properly. No need to rush, I've got time.
2. Is it true that given time, effort, and ingenuity there really isn't such a thing as a bricked phone? It can always be recovered, it's just a question of how far you have to go to do it?
I've read around a lot and though I've heard many people talk of bricking their phone, it seems like many say that if you can use things like adb commands you can pretty well fix any issue, it's just difficult.
Like I was saying in point 1, I'm newer to all this and I'm learning so thanks for answering!
Jonathan
lanternslight456 said:
2. Is it true that given time, effort, and ingenuity there really isn't such a thing as a bricked phone? It can always be recovered, it's just a question of how far you have to go to do it?
Click to expand...
Click to collapse
At minimum, I believe the phone requires a functioning bootloader in order to be able to connect via USB to fastboot.
Any update on this? I also just got a mytouch 4g yesterday and am trying to root it. Is it possible right now?
Root the mt4g
Friend, I used the adb method here on xda, after I got the forked childs msg, and restart terminal w/e, make sue to pull out battery. Restart, the LAST THING I DID WAS USE VISIONARY r14, to attempt permroot, took me a week before I figured out to try this, the guide said phone would be rooted after terminal commands went through. So, to recap if u entered everything correctly, (my avg protection was telling me my phone was rooted for a week after I pushed gfree using the adb method but had no s-off, tried visionary permroot, BINGO!) THANKS TO ALL THE HARD WORK/GUIDES ON XDA, using ICE GLACIER ROM, titanium backup, rom manager, root explorer, my internet security (ad free web) set cpu, cache cleaner ng, drocap, couldn't get barnacle to work, the tethering on board works fine. Quadrant standard for benchmarking.
My wifes mt4g arrived today, and I had it perm rooted, with s-off in about 20 minutes, following this guide from the wiki:
http://forum.xda-developers.com/showthread.php?t=858996
Sent from my Nexus One using XDA App
danger-rat said:
My wifes mt4g arrived today, and I had it perm rooted, with s-off in about 20 minutes, following this guide from the wiki:
http://forum.xda-developers.com/showthread.php?t=858996
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
dude this method is great especially if your a noob or cant use adb for whatever reason just use visionary for temp root and then using root explorer move the gfree file to data>local then open terminal emulator and follow the instructions that gives you s-off and allows you to use visionary to permaroot when you reboot and then rommanager it now supports 3.xx so you can flash gingerroms just be careful and have fun
I just got one of the new Galaxy Indulge 4G phones and tried rooting it.
BusyBox installer is telling me that the phone is rooted however it is nand locked.
and ideas on how to unlock nand on this phone?
How did you root it?
Thaxx said:
How did you root it?
Click to expand...
Click to collapse
SuperOneClickRoot.
Yeah i tried adb, super one click, and zroot. None of them worked, and for some reason everytime i try to start up root explorer, it crashes trying to get super user. I've tried all means of forcing super user to get onto the phone. No matter what it wont work. Mike thinks its Nand locked. Another thing i noticed is when I used super one click, i had two options at the top right hand corner that looked like names of my device. I can get my serial number with adb, and it shows it. Another darn problem is no drivers are out for this phone yet. Also have no idea of the LTE chip is interfering with this either. So come one come all dev and droid guru's help us out!
So basically I think this means we a need a custom recovery, flash image and stuff. Bah, that'll probably take like a month
K, also tried visionary rooting, which did some wierd ****. I rebooted and it seemed like i had root, but super user still didn't work. It fooled a couple programs into thinking i had root, but it would not let me "touch" the files on the phone. Even though it claimed I had r/w permission.
Silvist said:
Yeah i tried adb, super one click, and zroot. None of them worked, and for some reason everytime i try to start up root explorer, it crashes trying to get super user. I've tried all means of forcing super user to get onto the phone. No matter what it wont work. Mike thinks its Nand locked. Another thing i noticed is when I used super one click, i had two options at the top right hand corner that looked like names of my device. I can get my serial number with adb, and it shows it. Another darn problem is no drivers are out for this phone yet. Also have no idea of the LTE chip is interfering with this either. So come one come all dev and droid guru's help us out!
Click to expand...
Click to collapse
The Samsung Epic 4G drivers worked for me, also tried the rooting process used on the Epic whoever busybox says im rooted but that nand is locked, i downloaded Terminal emulator and it says im not rooted, also installing superuser not possible, I was able to install root explorer but not any good if doesnt let me delete the bloatware only read.
Yeah, busybox says the phone is rooted but nand locked.
superuser app was added to system/apps. however im not able to mount system/apps with R/W from root explorer. The rooting process seems to gain access to r/w the files but the apps cant.
seems 4G still have far distance from us...
Supposedly there's a work around for Nand locked, but the first one didn't work for me.
With the absolutely beautiful ADB exploit I use, titled rageagainstthecage (ratc), absolute ALL devices can be rooted. This is because it exploit is ADB which all devices use. There is an issue though. Some devices have a NAND lock which does not allow you to write to the /system mount. Because of this, you can’t copy su, sqlite or busybox to /system/bin. This creates some issues but there is a work around. For things that don’t need access to /system (like enabling non-market apps) I can use the ratc exploit to make those changes. If your device cannot use su in /system/bin then you can simple select a checkbox (as of v1.5) that says to use ratc.
Click to expand...
Click to collapse
This didn't work still for me. So the only other option was unrevoked, but when I went to the site, it listed only HTC. Kinda confused how using HTC roms is a work around for a samsung phone lol. Still need some master guru's help on this stuff.
I too have been trying and am unable to get nand unlocked, I would really love some other ideas. Anyone out there able to help?
I'm waiting 'till the $50 MIR on the 1st, then I'll jump in with both feet.
Some guy suggested to shell root > perm root > restart device. That doesn't work either. I also noticed something called "media scanner" that scans as the phone boots up, i wonder if that's preventing any modified files.
If anyone knows how NAND unlocking has worked for other phones (and im not just talking about what apps to run or what room to use) please contact me so that we can try a few things out and hopefully get a full root for everyone.
Supposedly Mr. Parker rooted:
http://forum.xda-developers.com/showthread.php?t=803682&page=260
I'm asking him through both post and through private message if he could elaborate. Apparently he had trouble with getting Win 7 x64 to work, but it worked with Win Xp. I'm still not sure what drivers he used, and he said he had it not in debug mode. I tried in non debug, and my phone wouldn't even register. So hopefully he'll expand on how he did it. If not, back to the drawing boards, at least till we get a real pro in here.
Got my hopes up that even though we dont have full root yet, I would be able to get rid of the bloatware.
The SuperOneClick is able to get read/write access and send commands to the phone so I opened Root Explorer on the phone and then rand the superoneclick. As soon as the program mounted the phone with Read/Write I started clicking on the Mount R/W button in root explorer until it showed the app as having read/write access to the system/app directory. I tried deleting the Iron Man app and it said it was deleted successfully.
but then I checked and the app was still there loading root explorer agian then showed that the file was still there and had not been deleted.
Wow you managed to get root explorer to work? Mine just tries to obtain root, and crashes everytime i start it up now. I've tried to unroot, and uninstall and reinstall it. I used Linda manager to view the files on the phone, but like you if i deleted they would return on boot. That's why I think metro or samsung has some kind of media scanner that scans at start up, and it somehow reinstalls files, or prevents root. Can't confirm this yet because super user fails ;/
I've been trying also to get root. Programs often will think i have root access. as far as adb is concerned i do have root access till i dont something that requires it. I've been able to install root manager and look through some files. Im under the impression metro or samsung did install something odd, though im not sure the media scanner is it. Also the phone does not require root in order to install other-market software.
What do you mean programs "think" you have root? You mean you have super user? And what "programs" are you referring to? You can install root manager without a root yes, but in order to put it into "r/w" mode and delete the files from the phone itself, such as bloatware, you need root and Super user access. Most people here I hope are aware that you don't need to root to install "MOST" apps. There "is" apps that require root, and you cannot run them without root access.
Such as:
Titanium backup
Set CPU
Why do I want to root is like everyone keeps saying, to delete all the metro apps, and have "full" manufacturer control over the phone. That's the whole point of rooting. So far no one has rooted this phone PERIOD, or at least shown proof they were even able to. So any info you find regarding rooting please post it here.
Alright, so I tried what Mr. Parker did, and no go. Whether I ran super one click on Win 7 x64 (which was all in admin) or win xp, it would not install super user. In fact I noticed a couple of the files copied from super one click were already on the phone, and weren't able to be overridden. Which may relate to nand lock.
I need help, Any changes I'm making in any system folder it backed up to previous one. Due to this unable to fix sd card permission, unable to change animation and many more.
cjmaaz said:
I need help, Any changes I'm making in any system folder it backed up to previous one. Due to this unable to fix sd card permission, unable to change animation and many more.
Click to expand...
Click to collapse
HTC's devices have a protection layer called "S-ON". It prevents you from making changes to system files, even when you've got root.
So you'll have to get S-OFF using Sunshine (which costs $25) or install an "insecure" kernel.
crystal_ball said:
HTC's devices have a protection layer called "S-ON". It prevents you from making changes to system files, even when you've got root.
So you'll have to get S-OFF using Sunshine (which costs $25) or install an "insecure" kernel.
Click to expand...
Click to collapse
I've tried Firewater rumrunner but probably Sunshine would also fail. HELP ME Posted a different thread about it Click Here. To help ME
Sunshine is only pay when it's work. You should try since most E8 only work with sunshine.
Ok so theres this security exploit or 4 actually that mainly involve sideloading a specially designed apk called quadroot, i assume that you already have an idea what this is if you're reading this if not then google it. I read that alot of the time root access exploits are found by finding apps that have root access and exploiting them to install su to the system partition. In this case you could potentially create your own. So my question is why isn't this being persued as a viable option? Pleas let the people who know what their talking about speak and if you have no legitimate knowledge of your own (im talking google cut paste) then just syfm please.
that-squirrel said:
Ok so theres this security exploit or 4 actually that mainly involve sideloading a specially designed apk called quadroot, i assume that you already have an idea what this is if you're reading this if not then google it. I read that alot of the time root access exploits are found by finding apps that have root access and exploiting them to install su to the system partition. In this case you could potentially create your own. So my question is why isn't this being persued as a viable option? Pleas let the people who know what their talking about speak and if you have no legitimate knowledge of your own (im talking google cut paste) then just syfm please.
Click to expand...
Click to collapse
Interesting. Will look into it. Will update if I find anything.
*UPDATE*
Checked it out. Useless because we still have locked bootloader. We need SYSTEMLESS root. Anything besides that is useless.
I was under the impression that the bootloader being locked only pertains to trying to install unsigned images, the method used for rooting mm in the same manner as lp would require a modified boot.img and no one has a working system image dump for mm being the reason no one can modify the boot.img. if a app was designed to escalate root access to install super su to the system partition and gain root access that way even temporary we could copy the entire system and make a permanent solution.
Hello All! I am me2151.
I am here to tell you some kind of good news.
We have achieved a temporary root shell using a modified recowvery script. Originally Recowvery installed a custom "recovery" but I have modified it to instead create a temporary root shell using the System_Server SELinux context and disable the flashing portion of the script. Yes we are still limited until we can get Kernel or Init context but I am working on that as well.
This exploit will be useful down the line because of one major thing. WE CAN INSERT KERNEL MODULES!!! But they need to be signed. So I am releasing this out here so we can take the next step into our full root! We also have rw to the /data partition and changes save over a reboot.
If we can get someone to sign a kernel module that the system accepts we can set SELinux to permissive.
This exploit SHOULD work for all variants.
NOTE: This should only be used by devs who know what they are doing.
Instructions(this should work on MacOS and Linux only!):
Download linked file below.
Extract to either adb directory OR a directory you have adb access in.
Give execute permissions to temp.sh.
Run temp.sh.
When you are all done with your exploring and stuff type "Reboot" to reboot normally.
https://drive.google.com/open?id=0B8CP3g3AqMuHcmNJUUJWLUJUelE
Credit:
@jcadduono - For recowvery, and pointing me in the right direction on IRC.
@brenns10 - Wrote the lsh used in the exploit to spawn the shell.
The group over here for ideas and solutions.
Very cool work! Glad to see people putting my shell (such as it is) to good use. Wish I had a V20 to try it out
I don't think you'll ever be able to sign a kernel module (SHA512 hash). You'd probably have better luck signing your own boot image.
Here's a theory to toy with:
I think the way to do it would be to gain read access to /init binary allowing you to dirtycow /init with the same init binary but change a very specific (but not vital to system integrity) set of instructions to point back to the setenforce code with a value of 0 without disturbing the rest of the binary/instructions. This way, init should continue running without crashing and taking down the whole system, and you can do something that might trigger that specific instruction set - which would then result in selinux becoming permissive.
This is beyond me, unfortunately. This method would also be very device specific until someone also finds an intelligent way to read init, modify instructions, then dirtycow it back.
I think system server context might be able to read init?
Once you get your permissive selinux, you'll also have to deal with Unix capabilities limitations (find a way around them).
jcadduono said:
I don't think you'll ever be able to sign a kernel module (SHA512 hash). You'd probably have better luck signing your own boot image.
Here's a theory to toy with:
I think the way to do it would be to gain read access to /init binary allowing you to dirtycow /init with the same init binary but change a very specific (but not vital to system integrity) set of instructions to point back to the setenforce code with a value of 0 without disturbing the rest of the binary/instructions. This way, init should continue running without crashing and taking down the whole system, and you can do something that might trigger that specific instruction set - which would then result in selinux becoming permissive.
This is beyond me, unfortunately. This method would also be very device specific until someone also finds an intelligent way to read init, modify instructions, then dirtycow it back.
I think system server context might be able to read init?
Once you get your permissive selinux, you'll also have to deal with Unix capabilities limitations (find a way around them).
Click to expand...
Click to collapse
if system_server can read init then thats a serious flaw.... Question for you. you said it would be very device specific. does that mean its unique for each individual phone or each model?
EDIT:Unfortunately we only have access to the init.rc not the binary it self.
@jcadduono I appreciate your input and direction in this matter another idea we have been toying with is
We have the aboot boot recovery and system dump. From the tmob variant would it be possible to make a tot from that for our devices changing the props to match our device, build, and carrier info? We can also pull apks from /system/apps and /privapps to our ext sdcard
@me2151, @jcadduono, @brenns10: Great work guys, keep it up. Good to see some people are trying for root. What model/s are being tested, or should this theoretically work on all models? Whilst you probably aren't doing it for the cash, there is a bounty I hope someone can claim soon, for a functonal root alone (not boot unlock) posted on this board.
RoOSTA
roosta said:
@me2151, @jcadduono, @brenns10: Great work guys, keep it up. Good to see some people are trying for root. What model/s are being tested, or should this theoretically work on all models? Whilst you probably aren't doing it for the cash, there is a bounty I hope someone can claim soon, for a functonal root alone (not boot unlock) posted on this board.
RoOSTA
Click to expand...
Click to collapse
It should work on all models. I personally use a sprint model(LS997). I think it MAY have been tested on VZW as well.
I can confirm that work on H990DS
Sent from my MI PAD using XDA-Developers mobile app
We know from earlier LG phone releases that the laf partition when bypassed in some way (corrupted, etc) aboot will boot to fastboot when going into download mode. It was my thought that the bootloader could be unlocked from there. However corrupting laf eliminates device recovery. Catch-22.
I think the best way to proceed is to get a working .TOT first which is just a waiting game. That would ensure device recovery and replacing the bootloader in the .TOT and signing it with something unlockable.
This is a great way to explore the locked phones in the meantime, thanks.
ATT Pretty Please
me2151 said:
Hello All! I am me2151.
I am here to tell you some kind of good news.
We have achieved a temporary root shell using a modified recowvery script. Originally Recowvery installed a custom "recovery" but I have modified it to instead create a temporary root shell using the System_Server SELinux context and disable the flashing portion of the script. Yes we are still limited until we can get Kernel or Init context but I am working on that as well.
This exploit will be useful down the line because of one major thing. WE CAN INSERT KERNEL MODULES!!! But they need to be signed. So I am releasing this out here so we can take the next step into our full root! We also have rw to the /data partition and changes save over a reboot.
If we can get someone to sign a kernel module that the system accepts we can set SELinux to permissive.
This exploit SHOULD work for all variants.
NOTE: This should only be used by devs who know what they are doing.
Instructions(this should work on MacOS and Linux only!):
Download linked file below.
Extract to either adb directory OR a directory you have adb access in.
Give execute permissions to temp.sh.
Run temp.sh.
When you are all done with your exploring and stuff type "Reboot" to reboot normally.
https://drive.google.com/open?id=0B8CP3g3AqMuHcmNJUUJWLUJUelE
Credit:
@jcadduono - For recowvery, and pointing me in the right direction on IRC.
@brenns10 - Wrote the lsh used in the exploit to spawn the shell.
The group over here for ideas and solutions.
Click to expand...
Click to collapse
At the moment all I am using root for is to add a line within my build.prop to disable Tethering checks, so I can tether at full 4G speed and not get throttled. Would this be possible using the method above, or would build.prop immediately get replaced at the reboot?
Thanks, and keep up the good work!
NRadonich said:
At the moment all I am using root for is to add a line within my build.prop to disable Tethering checks, so I can tether at full 4G speed and not get throttled. Would this be possible using the method above, or would build.prop immediately get replaced at the reboot?
Thanks, and keep up the good work!
Click to expand...
Click to collapse
no. it is a tcp root shell that can only do a few things such as kernel modules.. only section we were able to write to and have it stick was the /data partition which wont help you in this scenario
elliwigy said:
no. it is a tcp root shell that can only do a few things such as kernel modules.. only section we were able to write to and have it stick was the /data partition which wont help you in this scenario
Click to expand...
Click to collapse
So if we can write to data partition then in theory can we adb push to it using this? I ask because I'd like to install some tbo apps that normally would require flashing. But if we could push them we would be solid
markbencze said:
So if we can write to data partition then in theory can we adb push to it using this? I ask because I'd like to install some tbo apps that normally would require flashing. But if we could push them we would be solid
Click to expand...
Click to collapse
Unfortunately its a tcp shell. not a pure adb shell. so we cannot push or pull to those directories
Wow great progress keep up the good work. You guys are helping those assholes from LG sell more phones. Obviously some people have not made the switch because the lack of root. Root users are very influential leaders to get others to try out a new device.
Sent from my LG-LS997 using XDA-Developers mobile app
Works on the LG G5 also...
Hey guys, with the expectation of many that 'root is coming' to the other v20 models...are we likely to see the same type of root format that applied to the LG G4, where you have to (either) download or rip your own image to a PC. Use commands to insert root, then reflash to the device?
Any root is better than nothing, I know...but I ask because with the amount of software updates for the G4 (v10c software through to v10k before MM came out), meant the sheer amount of times you'd have to go through this process to keep your phone up to date whilst maintaining root was extremely frustrating - as it also meant xposed and related settings/apps needed to be reinstalled each time you performed an OTA update and re-flashed root.
Is this going to be a side effect of dealing with a locked bootloader? PS: If I sound dumb, it's probably because I am.
RoOSTA
roosta said:
Hey guys, with the expectation of many that 'root is coming' to the other v20 models...are we likely to see the same type of root format that applied to the LG G4, where you have to (either) download or rip your own image to a PC. Use commands to insert root, then reflash to the device?
Any root is better than nothing, I know...but I ask because with the amount of software updates for the G4 (v10c software through to v10k before MM came out), meant the sheer amount of times you'd have to go through this process to keep your phone up to date whilst maintaining root was extremely frustrating - as it also meant xposed and related settings/apps needed to be reinstalled each time you performed an OTA update and re-flashed root.
Is this going to be a side effect of dealing with a locked bootloader? PS: If I sound dumb, it's probably because I am.
RoOSTA
Click to expand...
Click to collapse
it shouldnt be an expectation as weve made it clear we do not have root and are hitting hurdles.. we have been advised we need to atack selinux and or the bl but at this point were wanting to try to use debug firmware which hoprfully would allow a bl unlock..
unfortunately nobody can creat a .tot with the debug firmware at al and theres no way at all to flash the images..
we need to somehow leverage an exploit to gain a temp adb root shell before we could even attempt anything and this has not been done in a way thats useful to us..
unfortunately we need more experienced devs at this point.
LG Australia (and as such, Taiwan) have effectively confirmed their H990DS v20 mobile phone's bootloader is confirmed as being unlockable. However (and for no apparent reason) they will not confirm why one region have released a variant of the phone with the bootloader unlock and why they are refusing this to others phones/regions. Because of course, they have zero training and information about anything related to their company expect for goods released in a specific region. That comes from a 'product expert'
Titanium Backup
Howdy,
Just reading through the thread, I understand that it's not quite a "full" root, but would it be enough to run Titanium Backup? I'm hoping to move away from root access with my V20 but it would be really helpful if I could do it temporarily, restore some application and data backups, reboot and uninstall Titanium.
Tim