Related
I know this might sound stupid, but I've never done this with a Z before and I'm a bit scared about bricking my new phone, so...
Got my Z about a week ago, used Visionary+ (yeah, I know, boo) to temproot and restore my apps with TitaniumBackup. Unrooted with the button in the app and haven't used Visionary since. Until last night, when I wanted to take some screenshots using drocap2. Temproot failed at first, so I rebooted and tried again. This time it worked and when I was done I used Unroot again.
Only this time after rebooting my weather info was gone. Readded the clock, that didn't fix it. The weather app just said "Current City" - it wasn't showing any weather info.
I figured that's not biggie, but I found another bug which is: if I power the phone off and then back on while "Fast Boot" is on I lose access to my phone app and contacts (both show a black screen) until I do a full reboot.
So now I decided to reinstall everything and start afresh (this time I'm using rage to root ).
Right now I'm running everything stock (ROM, recovery, SPL are untouched). If I have one of the CIDs contained in the android-info.txt inside the official 1.34.405.5 RUU (HTC__032), is it okay to just run the RUU? Or should I stick to a hard reset from fastboot or recovery?
Thanks!
Try hard resetting first, this will erase all data in your phone, and if that is not working go in your device to settings>aboutphone>Softwareinformation and check there if your build number is:
1.34.405.5
if it is then let me know and I can give you a PC10IMG.zip (I have done this method before), and simply you will copy the zip to your sd card, turn on the phone into bootloader, and the phone will do the rest.
Or simply flash one of those exe RUU jsut be sure is the same build number.
My build is 1.34.405.5. The RUU I have is RUU_Vision_HTC_WWE_1.34.405.5_Radio_12.28b.60.140e_26.03.02.26_M_release_155556_signed.exe
Isn't the PC10IMG.zip a renamed rom.zip from inside the RUU?
keinengel said:
Isn't the PC10IMG.zip a renamed rom.zip from inside the RUU?
Click to expand...
Click to collapse
Yes, it is.
Both methods i.e. zip or ruu will do what you are asking for so is up to you to choose one.
I rather the zip one, since to me the ruu kind of did not work, and then I needed to install htc syn and stuff (I am a mac user, no needs for drives just as linux )
Anyhow hope I helped
Okay, I'll transfer the rom.zip to my SD card and rename it, thanks!
Which reminds me, I used Visionary because rage only seemed to be giving me shell root. TitaniumBackup couldn't seem to get root rights. I followed the steps, I'm very well accustomed to adb and fastboot commands and also shell commands, but couldn't get it up and running. I'll try again after restoring my phone.
keinengel said:
Which reminds me, I used Visionary because rage only seemed to be giving me shell root. TitaniumBackup couldn't seem to get root rights. I followed the steps, I'm very well accustomed to adb and fastboot commands and also shell commands, but couldn't get it up and running. I'll try again after restoring my phone.
Click to expand...
Click to collapse
If you had permanent root in the shell (i.e. could successfully do an "su" after a reboot"), then you had permanent root alright. If there was a problem with another app getting root rights, then it may have been something to do with the Superuser app, because that pops up and asks for permission the first time an app asks to run as root.
keinengel said:
Okay, I'll transfer the rom.zip to my SD card and rename it, thanks!
Which reminds me, I used Visionary because rage only seemed to be giving me shell root. TitaniumBackup couldn't seem to get root rights. I followed the steps, I'm very well accustomed to adb and fastboot commands and also shell commands, but couldn't get it up and running. I'll try again after restoring my phone.
Click to expand...
Click to collapse
you should not rename the zip file, unless it has other name, but it should be called PC10IMG.zip
steviewevie said:
If you had permanent root in the shell (i.e. could successfully do an "su" after a reboot"), then you had permanent root alright. If there was a problem with another app getting root rights, then it may have been something to do with the Superuser app, because that pops up and asks for permission the first time an app asks to run as root.
Click to expand...
Click to collapse
I never got permanent root, because I didn't want it. I did all the rooting, flashing radios/spls/recoveries and custom ROMs I'd ever need with my trusty old Magic. Now I'm trying to stay clean
I just needed temproot for TitaniumBackup and drocap2 - that's it. Don't need supercid, s-off or anything else - and that's what made Visionary so attractive. Too bad it's hit-and-miss.
My problem with rage was that I had root access from the terminal, but couldn't run those two apps without permanently rooting. Besides, I'm not quite sure how to unroot, should I ever need to. Would flashing the stock PC10IMG.zip from fastboot be enough? I see it overwrites most partitions, but would it also overwrite the radio config one?
keinengel said:
I never got permanent root, because I didn't want it. I did all the rooting, flashing radios/spls/recoveries and custom ROMs I'd ever need with my trusty old Magic. Now I'm trying to stay clean
I just needed temproot for TitaniumBackup and drocap2 - that's it. Don't need supercid, s-off or anything else - and that's what made Visionary so attractive. Too bad it's hit-and-miss.
My problem with rage was that I had root access from the terminal, but couldn't run those two apps without permanently rooting. Besides, I'm not quite sure how to unroot, should I ever need to. Would flashing the stock PC10IMG.zip from fastboot be enough? I see it overwrites most partitions, but would it also overwrite the radio config one?
Click to expand...
Click to collapse
Jut put the PC10IMG.zip in the root of your sd card. Then turn completly off the phone, and turn it on into bootloader (down key volume + power button), and the device shall recognize the zip.
Hi, I've got a Motorola Defy in Argentina (Carrier: Personal, means telecom). Well, I want to Root it, I've tryied z4mod, the ADB Method, 1 click, etc, and I still got the message "The application xxxx needs root user permissions", btw I have the Root (#) console in "adb shell", but I can't move files to /system/media (whit "AndExplorer" from mobile). Do I have to mount the FS there??
I've got the "Superuser" app working, and some applications whit "Root permissions" (because I've checked Remember my answer on the Popup when the app needs root privilegies)
Im a little bit confused because the version is not similar that you use here.
Version Number: JORLA_U3_6.14.7
Firmware version: 2.1-update1
So, I want to root it, and maybe upgrade to Froyo, but that questions make me scared (specially if i brick it).
What should I do?
PS: I've made a "Backup" with SystemRecovery app. This backup will work if I want to back my firmware to the stock one? (forgive the apps, I don't care).
Nobody can guarantee your backup will work, but it's a risk you'll have to take if you want to hack.
According to my search, your carrier uses UMTS 850 / 1900. This means you could have a different baseband firmware than the T-Mobile users here, and definitely different from the European users. The problem is, the only SBF files available are for European 900/2100.
So first things first, take a nandroid backup from the custom bootstrap recovery if you can get that working. Back up those files somewhere safe.
Read about the "3g fix". There is a folder containing the baseband firmware files, and you'll want to back those up in case you lose 3g on a custom ROM.
If your phone becomes unbootable, you'll have to flash an SBF to boot it, *then* root it again, install custom recovery again, and finally restore the nandroid backup.
Sent from my Nexus One using XDA App
Ok, thanks for the info. I've tryied to do a "nandroid backup" with the upgrade.zip stuff, but it just restarts and do nothing. I can't see any changes on my SDcard.
BTW, how I can run a .apk as root? (I want the AndExplorer to be root so I can copy some stuff to /system). I've got actually a root (#) terminal in adb shell and in Terminal emulator (via command su).
Thanks
cocus said:
Ok, thanks for the info. I've tryied to do a "nandroid backup" with the upgrade.zip stuff, but it just restarts and do nothing. I can't see any changes on my SDcard.
BTW, how I can run a .apk as root? (I want the AndExplorer to be root so I can copy some stuff to /system). I've got actually a root (#) terminal in adb shell and in Terminal emulator (via command su).
Thanks
Click to expand...
Click to collapse
How are you attempting to do this backup?
You need to download the bootstrap custom recovery, and use that to boot into the recovery menu. From there you go into backup/restore.
If you have successfully rooted your phone, then all apps have the opportunity to run as root. They should be able to make the request via Superuser Permissions, which would then prompt you.
Ok, but the bootstrap custom recovery is for 2.51 or similar firmware numbers, I've got 6.14. So, I really didn't test because I don't have experience with this things and I don't want to screw up all.
I tell you, for example, the Terminal Emulator runs on root when I run "su": Android requested Superuser permissions to me, and I ticked remember option, and now I can run "su" without the Superuser request.
BTW, I've got a root shell on adb (when I reboot the phone, I loose the root ). That means that is rooted??? (Got it using RATC)
Well, either it's compatible or it's not. If the bootstrap makes your phone unbootable... I guess you'll have to try for a warranty claim
Sent from my Nexus One using XDA App
Hahaha, I like to flash things and understand how it works, but in this case, I would prefer not screw nothing. Btw, I've buyed it on 15/jan.
So, for my other question the Terminal Emulator runs on root when I run "su": Android requested Superuser permissions to me, and I ticked remember option, and now I can run "su" without the Superuser request.
But when I restart the phone, I loose the # on "adb shell".
BTW, I've found the open source code of an earlier version of my defy on
opensource.motorola.com/sf/go/projects.moto_defy/frs.defy_latam
Anyone knowns how to compile this? I've got Debian lenny, Ubuntu 10.04, Ubuntu 10.10.
Thanks
Compiling a ROM yourself won't help if you can't sign it with Motorola's key. Yay locked bootloader...
Sent from my Nexus One using XDA App
Cocus,
I got the same phone as yours. Also from Personal.
And I am on the same situation, want to flash it, but not to brick it.
Let me know if you find out something ...
Hi, yes you can contact me via PM & I will send all the stuff that I've got. But I only get the rootshell via RageAgainstTheCage. When you reboot it you loose it, but you can use "su" or "rootshell" to get it again.
Now Im playing with C and C++ native code, with the ndk and sdk (no java ). Contact me
z4root worked in argentine (Latin American) defy.
Hi
I have a Motorola Defy like yours , (in Argentina - Carrier: Personal ).
I have rooted successfully using z4root 1.3.0 , that you can get from this post (look attached file at end ):
http://forum.xda-developers.com/showthread.php?t=833953
With z4root 1.3 you have the option of get root temporarily or permanent. The first one doesn't works for me ( no errors but no root ). The permanent root yes, works like a charm .
Hi, It seems that is not working for me... I've touched the permanent option, it restarted and the z4root says that is rooted, but I haven't the root console in adb shell, neither the apps run as root.
Edit: If I try to run "su" on the non-root console($) it says "Permission denied". But, running "rootshell" from RATC, it gives me a root shell.
You will need the following software:
Superuser
Root explorer
Visionary r13
Z4Root
Terminal
and the rooting files provided in the other post...place those in the root directory of your sd card.
Why use this method?
I noticed that some phones cannot be rooted using the traditional rooting method through terminal. My phone an my friend's phone were not easy to root. My brothers rooted with the visionary method.
When that fails, you can use this one...that I discovered while trying to unroot my phone using many different methods.
The method:
- First make sure superuser is running.
- make sure usb debugging is on, and third party apps is checked.
- Open visionary, make sure the mount as R/W after root is checked and do a
temp root
- Open z4root and do a temp root.
- run terminal and type: su
- keep terminal open but switch to home screen
- open root explorer
- press mount as R/W
- navigate to that "root" folder on your sd card with the root files and open root.sh and then click execute
- switch back to terminal and type:
cd /sdcard/root
hit enter and then type:
sh root.sh
and hit enter...the phone will do some stuff and after it's done, reboot it.
Once it is off and about to start, press power button and vol down button at the same time. It should have s = off on it.
reboot again into the OS and open z4root and do a perm root.
After that is done, it will keep saying rebooting but it will not do it automatically so go ahead and reboot it with the power button.
Once the phone has booted again, uninstall z4root and visionary and anything else except root explorer.
That's it! There is no such thing as un-rootable!
what's z4root used for when visionary does temproot for you?
Sent from my HTC Glacier using XDA Premium App
You may not need it but when I was attempting to root the phone, that's what I used.
I am thinking you can follow the steps, omit the z4root steps and just use visionary.
For some reason my phone did not want to unlock just with visionary.
Dont work for me,,,,i try all the stuff here,,i dont know what im doing wrong,,cause the phone said s.off but when im reboot the phone still on
Sent from my HTC Glacier using XDA App
Wait it says s-off? Then you're good, all you do after the reboot, is run z4root and perm root it
If you follow the directions that grankln posted and do it right then you wont have any problems rooting it. If someone follows that guide and correctly it will root their phone. Its proven to work so if its not working on someone's phone chances are high they aren't doing it right. This thread in unnecessary especially since there are already a few methods of rooting already posted. You are just going to confuse people more
Sent from my Dell Streak 7 using XDA App
graffixnyc said:
If you follow the directions that grankln posted and do it right then you wont have any problems rooting it. If someone follows that guide and correctly it will root their phone. Its proven to work so if its not working on someone's phone chances are high they aren't doing it right. This thread in unnecessary especially since there are already a few methods of rooting already posted. You are just going to confuse people more
Sent from my Dell Streak 7 using XDA App
Click to expand...
Click to collapse
I've never seen that guide fail when all steps are performed correctly. Even in irc, when people say that that method doesn't work, I walk them through the steps and it magically works when it failed every time before.
No luck
lumos5 said:
You will need the following software:
Superuser
Root explorer
Visionary r13
Z4Root
Terminal
and the rooting files provided in the other post...place those in the root directory of your sd card.
Why use this method?
I noticed that some phones cannot be rooted using the traditional rooting method through terminal. My phone an my friend's phone were not easy to root. My brothers rooted with the visionary method.
When that fails, you can use this one...that I discovered while trying to unroot my phone using many different methods.
The method:
- First make sure superuser is running.
- make sure usb debugging is on, and third party apps is checked.
- Open visionary, make sure the mount as R/W after root is checked and do a
temp root
- Open z4root and do a temp root.
- run terminal and type: su
- keep terminal open but switch to home screen
- open root explorer
- press mount as R/W
- navigate to that "root" folder on your sd card with the root files and open root.sh and then click execute
- switch back to terminal and type:
cd /sdcard/root
hit enter and then type:
sh root.sh
and hit enter...the phone will do some stuff and after it's done, reboot it.
Once it is off and about to start, press power button and vol down button at the same time. It should have s = off on it.
reboot again into the OS and open z4root and do a perm root.
After that is done, it will keep saying rebooting but it will not do it automatically so go ahead and reboot it with the power button.
Once the phone has booted again, uninstall z4root and visionary and anything else except root explorer.
That's it! There is no such thing as un-rootable!
Click to expand...
Click to collapse
well it doesn't work. i try many ways & still nothing.
still have S-ON
Hboot- 0.86.0000
this sucks. rooted about 41 G1/ Mytouch 3G never faced a problem.
smh guess someone should come out with a video for this
lumos5 said:
You will need the following software:
Superuser
Root explorer
Visionary r13
Z4Root
Terminal
and the rooting files provided in the other post...place those in the root directory of your sd card.
Why use this method?
I noticed that some phones cannot be rooted using the traditional rooting method through terminal. My phone an my friend's phone were not easy to root. My brothers rooted with the visionary method.
When that fails, you can use this one...that I discovered while trying to unroot my phone using many different methods.
The method:
- First make sure superuser is running.
- make sure usb debugging is on, and third party apps is checked.
- Open visionary, make sure the mount as R/W after root is checked and do a
temp root
- Open z4root and do a temp root.
- run terminal and type: su
- keep terminal open but switch to home screen
- open root explorer
- press mount as R/W
- navigate to that "root" folder on your sd card with the root files and open root.sh and then click execute
- switch back to terminal and type:
cd /sdcard/root
hit enter and then type:
sh root.sh
and hit enter...the phone will do some stuff and after it's done, reboot it.
Once it is off and about to start, press power button and vol down button at the same time. It should have s = off on it.
reboot again into the OS and open z4root and do a perm root.
After that is done, it will keep saying rebooting but it will not do it automatically so go ahead and reboot it with the power button.
Once the phone has booted again, uninstall z4root and visionary and anything else except root explorer.
That's it! There is no such thing as un-rootable!
Click to expand...
Click to collapse
Is this the Best way to Root the MyTouch?
PMGRANDS said:
Is this the Best way to Root the MyTouch?
Click to expand...
Click to collapse
Look at the past post, post count, and you will have your answer... Tried and true is the way to go though!
Sent from my HTC Glacier using xda premium
This method works on 2.3.4 ?
sent from HTC Glacier using tapatalk
King350z said:
This method works on 2.3.4 ?
sent from HTC Glacier using tapatalk
Click to expand...
Click to collapse
No, you have to downgrade. Check the resource Bible, they're a few threads on how to do it. Then you can root your phone.
If I helped, give thanks, if you please.
........Death before dishonor........
For God's sake. Having root without write access to the system partition is next to worthless. If anyone has questions regarding rooting there phone then please read the how to http://forum.xda-developers.com/showthread.php?t=858996. If you can't figure it out do not go ahead with a procedure you don't understand! Not trying to be a **** but what works is posted. Its proven. It does the trick.
Sent from my HTC Glacier using Tapatalk
Hi all,
I have had my htc desire z for about two weeks now, But since i have had my phone i've been having a few problems.
I had rooted my phone using visionary +. And all was going well untill i was trying to install setcpu to overclock my cpu. After installation my phone rebooted and now every thing that i need root access for is showing up as not accessable.
Busybox installer error message:
Your phone is roote
Busybox not found
The application failed, either because your device is not nand unlocked or we were unable to remount.
Rom manager error message:
An error occured while attempting to run priviledged commands!
Is it possible(if yes, how) to unroot and flash my desire back to stock settings including the permissions back to stock.
If not how can i root my phone so i can use all of the fuctions
Regarding the phone info the spaces are actually . but the system will not allow me to enter these as of yet
Thanks in advance
All the best
Gaz
I forgot to mension in the last post that i have expiriance with mobile phone's and flashing so i'm not affraid to tackle big complicated ways of undoing the process.
It sounds like maybe you only had temp root.
Did you also do gfree? I did Visionary and gfree, and perm rooted just fine.
However, many on here believe the rage + gfree method is safer, as Visionary has been known to create some semi-bricks. I don't THINK there is any harm in doing rage + gfree at this point, but others on here can probably enlighten.
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD
I tried using root checker to find the issue. It came back with an error message telling me the SU binary was not found in the correct path. I used terminal emulator to try to locate the file but with no success. Any ideas on how to find and move the binary su???
What's displayed on your screen after reboot in recovery?
As in; remove battery, insert battery, hold volume down and power button.
It will not reboot in to root. It runs Visionary and nothing happens.
And when i try to open an app that need root access it fails because it cannot gain permission from superuser. At this point i have tried to unistall all apps that had anything to do with rooting my phone but still no succes. I need to find the stock SU Binary
One click root with impactor now works. Works on <4.3. No need for unlocked bootloader. Does not wipe data.
http://www.saurik.com/id/17
Copy over the superuser.apk and the such binary onto your phone, then use the MV command to move it to /system/app and /system/xbin respectively.
Beamed from my Grouper
Mach3.2 said:
Copy over the superuser.apk and the such binary onto your phone, then use the MV command to move it to /system/app and /system/xbin respectively.
Beamed from my Grouper
Click to expand...
Click to collapse
What should the permissions on each be?
EDIT: Can you alternatively only push the su binary and download superuser from gplay?
krackers said:
What should the permissions on each be?
EDIT: Can you alternatively only push the su binary and download superuser from gplay?
Click to expand...
Click to collapse
If the binary is wrong, the one from play store may not work.
Permission should be rw-r-r(0644) for the su.apk and rwsr-sr-x(0645) for the su binary.
Beamed from my Maguro.
I tried it myself and while it appears that commands do run, they don't appear to work. I think it might have to do with running as system vs running as root. Why else would saurik use an indirect method of gaining root (using ro.kernel.quemu) as opposed to directly pushing the su binaries.
krackers said:
I tried it myself and while it appears that commands do run, they don't appear to work. I think it might have to do with running as system vs running as root. Why else would saurik use an indirect method of gaining root (using ro.kernel.quemu) as opposed to directly pushing the su binaries.
Click to expand...
Click to collapse
This is correct: sometime in the Android 4.1 release cycle, they removed the ability to use /data/local.prop as an attack vector to go from system->root. The signature bug lets you modify the code of any APK, but the most powerful user an app can ever run as is system, not root.
However, in an update to Impactor today, I've added a system->root escalation. This allows one-click rooting, and even though the system->root I'm using has already been patched in AOSP (the idea was not to waste something to go along with a shell->system that is already long burned) it works on my 4.2.2 Nexus 4 (and so I'd imagine will also work fine on a Galaxy Nexus) as Android sucks at getting patches to real devices ;P.
Using Impactor on my Panasonic Eluga dl01 does somehow not work.
(Android 4.0.4)
I get following error message:
/data/local/tmp/impactor-6[3]: /data/local/tmp/impactor-4: Operation not permitted
I also tried and played around with the command line in Impactor.
"adb devices" won't list my phone
But when I use the adb from the current Android SDK I just installed, it will display my phone with "adb devices".
I also downloaded a ICS 4.04 root zip file with a script and adb files inside. When using that adb version, my phone won't be displayed too. Now when I run adb from the android SDK, it will say something like "server is outdated" then something like "kill and restart with new server" --> "adb devices" lists my phone correctly again.
May be the adb version used in Impactor is outdated and responsible for the error message?
I would really appreciate any help with this topic, because the Panasonic Eluga phone was never rooted until now and no known root method is available. I always kinda hoped that someone would use the masterkey thing to make a universal rooting tool
saurik said:
This is correct: sometime in the Android 4.1 release cycle, they removed the ability to use /data/local.prop as an attack vector to go from system->root. The signature bug lets you modify the code of any APK, but the most powerful user an app can ever run as is system, not root.
However, in an update to Impactor today, I've added a system->root escalation. This allows one-click rooting, and even though the system->root I'm using has already been patched in AOSP (the idea was not to waste something to go along with a shell->system that is already long burned) it works on my 4.2.2 Nexus 4 (and so I'd imagine will also work fine on a Galaxy Nexus) as Android sucks at getting patches to real devices ;P.
Click to expand...
Click to collapse
Do you need to have an unlocked bootloader for the root exploit to work? I am hoping to get root without having to wipe the device by unlocking.
To the poster above me: Try using a different computer and if that doesn't work, switch operating systems.
krackers said:
Do you need to have an unlocked bootloader for the root exploit to work? I am hoping to get root without having to wipe the device by unlocking.
Click to expand...
Click to collapse
That's the whole point in securing Android, not that people have easier ways instead of unlocking a device.
Tested and works great. I now have root. Yay!
Does it show any of the problems that chainfire's superSU 1.41 shows?
Sent from my Galaxy Nexus using xda app-developers app
The root exploit only places the su binary and sets the right permissions. You can use any root manager you want (I used clockworkmod's superuser app).
mercuriussan said:
Using Impactor on my Panasonic Eluga dl01 does somehow not work.
(Android 4.0.4)
Click to expand...
Click to collapse
The feature of installing su will not work on every device: a lot of emphasis is put on "rooting" Android devices, but on many devices even root can't do things like modify the files in /system; I'd use the term "jailbreak" as to being what people really want to do with their device, but Android people seem to have that term ;P. What this means is that you really need a kernel exploit, not just a shell->system->root escalation.
mercuriussan said:
I get following error message:
/data/local/tmp/impactor-6[3]: /data/local/tmp/impactor-4: Operation not permitted
Click to expand...
Click to collapse
This error message actually indicates that Impactor succeeded in obtaining root control over your phone. However, when it tried to then, as root, remount /system writable so it could copy the su binary in place, it wasn't allowed to do so. A future version of Impactor will make it easier to drop to a root shell so you can test things out manually, but this means that while you can run code as root, you won't be able to install su.
However, if you have the time to play with it, get a copy of busybox and use adb to push it to /data/local/tmp (this is also something Impactor should help you do, but does not yet). (You will also need to make it executable, don't forget: "chmod 755 /data/local/tmp/busybox".) Then run the suggested Impactor command involving telnetd. Finally, via a shell, run "/data/local/tmp/busybox telnet 127.0.0.1 8899": you are now root.
You can verify that you are root because you will now have a # as a prompt instead of a $. Then run "mount -o remount,rw '' /system" (<- note, that's two single quotation marks as an argument between remount,rw and /system). This is the command that should fail with the "Operation not permitted" message. You are, however, root, so maybe there's something you want to do on the device at that point ;P.
mercuriussan said:
I also tried and played around with the command line in Impactor.
"adb devices" won't list my phone
But when I use the adb from the current Android SDK I just installed, it will display my phone with "adb devices".
Click to expand...
Click to collapse
The "Open Shell" in Impactor connects you to the device via adb: if you run adb on the device and ask for a list of devices attached to the device--something I didn't even realize was possible until you pointed it out here ;P I tested it, though, and wow: that actually is possible--you will get a blank list. However, suffice it to say that if you were able to type that at all, it can see your device.
Thanks for the suggestion, I'll try my luck in finding some exploit I can use...
So since Google patched this in 4.3, does this mean almost all devices before 4.2.2 can be rooted with this method?
bmg1001 said:
So since Google patched this in 4.3, does this mean almost all devices before 4.2.2 can be rooted with this method?
Click to expand...
Click to collapse
Yup - assuming they haven't been patched against the methods used (most haven't been).
Very interesting read. Thanks saurik & OP.
Eluga DL1
Hi there,
this post is in some ways a duplicate but different people seem to follow this thread because it is directly involving sauriks impactor.
Is there anything available that i can throw at Elugas 4.0.4 kernel to get r/w on the system partition?
I will try everything that is suggested to me.