Anyone following the RUU threads already knows about this and it's starting to get more attention now. The latest official build of Superuser does not work with newer Sense ROMs (such as Vision 1.72+, anything released recently). HTC has started utilizing a relatively new feature of sqlite; a journaling mode called WAL (write-ahead logging). It's actually smart. WAL journaling should improve sqlite throughput, which represents a large amount of Android's IO and benefits applications across the board. The downside is it broke Superuser because it's actually special in its' use of sqlite.
WAL journaling, as built with these new Sense ROMs, is using exclusive locking. Why is this important for Superuser? It's the one situation where you have an application running within Android's process space and one outside of it, both accessing the same sqlite database. When su runs, it opens the sqlite database to check whether you have allowed access for said command to run. If not, a call is made to the Android application, which fires up and prompts you for an answer. Problem is, su has the database open with an exclusive lock (i.e. nothing else can touch it), so Superuser (the Android app) fails to open the database and cannot run. It'll either force close or do nothing.
To fix this, I have modified Superuser and su. Both changes have been submitted to ChainsDD for review. You can look at his git repository's pull requests to see the changes I'm proposing. I'm basically changing the journal mode being used by su one that is non-exclusive and Superuser to close its' database when sitting idle. I couldn't change Superuser's journal mode no matter what I did; it seems to be set deeper in the stack than I can access.
Here are the links to my pull requests on Github if you want to review the code:
https://github.com/ChainsDD/android_packages_apps_Superuser/pull/14
https://github.com/ChainsDD/android_system_extras/pull/1
Anyway, the end result is I have a working Superuser. Here are the caveats:
This is not an official build, so it's signed with my key, not ChainsDD. He has merged my patches into his Github repository so they should be making their way into a release soon.
I've artificially incremented the version number to 9.9.9, to make sure if you install my version, it'll "win" over any other installed version. Also, this prevents the Market from nagging you for updates.
I don't recommend using this version unless you must. In other words, you are on one of the Sense ROMs which is broken. Use an official build otherwise.
If you ran the RUU and have trashed your custom recovery (Clockwork), this isn't going to help you root the device again. Superuser is a tool for managing root access, not obtaining it.
If you are running Virtuous, you DO NOT need this.
Download Patched Superuser Flashable Zip
great work rmk! but i still prefer to stick with your virtuous.
I'm trying to work around the no root available for 1.72 problem with my stock HTC Z rom updated to 1.72 OTA, but with Rage method temp-root I'm stuck with a frozen terminal after the 'Force Close' step, starting the terminal the 3rd time in the process. I've replaced the gfree_temp_root package's su file with the one provided here, used the APK provided here (pre-installed the apk too before the attempt). It's unfortunately stuck with a frozen black terminal window. Probably the Rage thingy doesn't work with the new 1.72 update, or am I using these files correctly at all?
(guide http://forum.xda-developers.com/wik...cess_.28Permanent_Root_.2F_.22Permaroot.22.29 )
ChainsDD merged my patches into his repositories today so they should make it into an official release soon.
Nice! Is ChainsDD going to be changing Journal Mode himself?
thanks for this, confirmed working on DHD.
Just for a correct understanding:
I need to have root like described here to use SU right?
Or is it now possible to get the new Update via OTA and get root with this method and its a solution for rooting 1.72?
Thanks!
Dacoco said:
Just for a correct understanding:
I need to have root like described here to use SU right?
Click to expand...
Click to collapse
That's a DHD thread and this is the DZ/G2 forum. So you're either in the wrong forum, or looking at the wrong procedure (which could brick your phone).
Soo.... Us stock 1.72 people can root??
MacaronyMax said:
Soo.... Us stock 1.72 people can root??
Click to expand...
Click to collapse
There has been more than one report that rage doesn't work either, on the 1.72 ROMs.
Also, there's the issue of S-OFF that needs addressing, whether that can be re-done at 1.72.
I dont understand, or I miss some information. The 1,72 ROM is not patched yet (or what?).. Then. If I install 1,72 I will loose root. So in what cases I will need this patch?
denich said:
I dont understand, or I miss some information. The 1,72 ROM is not patched yet (or what?).. Then. If I install 1,72 I will loose root. So in what cases I will need this patch?
Click to expand...
Click to collapse
Check this thread - http://forum.xda-developers.com/showthread.php?t=886023
The patched su/Superuser is just part of the solution.
steviewevie said:
That's a DHD thread and this is the DZ/G2 forum. So you're either in the wrong forum, or looking at the wrong procedure (which could brick your phone).
Click to expand...
Click to collapse
Oh! You're right. I just followed some links. Okay thanks.
steviewevie said:
Check this thread - http://forum.xda-developers.com/showthread.php?t=886023
The patched su/Superuser is just part of the solution.
Click to expand...
Click to collapse
According to this- there is now root method to 1.72.. I don't understand, why this patch is needed if rooting 1,72 is not availeble?
denich said:
According to this- there is now root method to 1.72.. I don't understand, why this patch is needed if rooting 1,72 is not availeble?
Click to expand...
Click to collapse
Cause the Virtuous 0.8.X is build from the Egypt 1.72.X Release, if I understood it right
b1oh4zard said:
Cause the Virtuous 0.8.X is build from the Egypt 1.72.X Release, if I understood it right
Click to expand...
Click to collapse
Is the Egypt RUU rootable?
That could solve our problems!
&partialy working for me.. still creating read-only -wal and -shm files
here is an another solution: http://saraev.ca/su/
it is modified to "chmod" own databases - have a look at README file included
don't forget to grant permissions to superuser itself
EDIT: this is a dirty workaround, I hope someone can make it better...
seo said:
&partialy working for me.. still creating read-only -wal and -shm files
here is an another solution: http://saraev.ca/su/
it is modified to "chmod" own databases - have a look at README file included
don't forget to grant permissions to superuser itself
EDIT: this is a dirty workaround, I hope someone can make it better...
Click to expand...
Click to collapse
The one in your link is a dirty workaround for sure, it modifies baksmali code. Mine is working as intended. The wal and shm files are only present when you're actually sitting in the Superuser app. I'll modify the code some more to close the DB anytime it's not being read or written from. As it stands it's already rare to trigger a case where a request would fail.
rmk40 said:
The one in your link is a dirty workaround for sure, it modifies baksmali code. Mine is working as intended. The wal and shm files are only present when you're actually sitting in the Superuser app. I'll modify the code some more to close the DB anytime it's not being read or written from. As it stands it's already rare to trigger a case where a request would fail.
Click to expand...
Click to collapse
yeah i know that..
Hi,
This patch works only on Desire Z or I can install in my Desire HD?
Regards,
Related
GENERIC ROOTED ROM BASED ON
OFFICIAL HTC WWE ÉCLAIR 2.1 (RUU)
***ONLY FOR GSM HERO***
Description:
This ROM is as generic as possible but with root access. It's based on the WWE official HTC RUU for Éclair 2.1. Everything besides rooting is completely untouched. The OTA had some files only needed to update the phone through the OTA process which were now removed from the RUU (by HTC, not me). The com.htc.resources.apk file is the only one which is different between the OTA and RUU. I don't know the differences so it's up to you to install this or not but you probably don't need to install this if you are currently using any of the OTA versions.
Features:
Official HTC WWE Éclair 2.1 (RUU)
Superuser v2.3.5 by ChainsDD
Updated to OTA v3.32.405.2
Rooted
How to install:
Wipe everything:
Data
Dalvik-cache
Battery Stats
Rotate Settings
Flash ROM via recovery mode.
Flash Radio via recovery mode (the phone will reboot twice, do not interrupt the process at any moment).
Reboot the system once after the initial boot.
I suggest to always reinstall the radio after flashing any ROM, I've had GPS problems in the past for not doing so. Either flash the one below or the one that suits you/your network better.
Downloads:
ROM:
http://www.mediafire.com/?dyl5djf4z0gjx3z
Radio:
63.18.55.06PU_6.35.15.11:
http://www.mediafire.com/?nif1igt3moz
63.18.55.06PU_6.35.15.14 (Orange users experiencing SIM lock problems):
http://www.mediafire.com/?mvizwtfjgym
Thanks:
To every single person around the Android dev scene and to everyone which helped me along the way, directly or indirectly, it's just too many people to remember and name them all.
Disclaimer:
I will not be held responsible for any damage to the phone and it's your responsibility to make the necessary backups before flashing this ROM.
GENERIC ROOTED ROM BASED ON
OFFICIAL HTC WWE ÉCLAIR 2.1 (OTA)
+ ADDITIONS
***ONLY FOR GSM HERO***
Description:
This ROM is based on 42turkeys work that you can find on this thread. I'm doing this because I prefer to have a generic and clean ROM and 42turkeys removed some files from his ROM and he's also using an older version of Superuser. I also did a few small improvements that in my point of view, don't take away from being a generic ROM.
Changes to the original 42turkeys ROM:
Fixed problem with rooting.
Courtesy of Kimera ROM by Exit93.
Complete update-script with the usual BusyBox symlinks and a few other things.
Taken from MoDaCo Chungwa repack by Paul.
Updated BusyBox to v1.15.3 and added Sqlite3 v3.5.9.
Replaced older Superuser version with ChainsDD 2.1 version.
Added extra locales:
en_PT, en_FI, fr_BE, fr_CH, pt_PT, nb_FI, da_FI, sv_FI.
Taken from MoDaCo Chungwa repack by Paul.
Re-added all apps/files removed by 42turkeys:
Maps.apk, PDFViewer.apk, Quickoffice.apk, Stk.apk, Stk.odex, YouTube.apk.
Moved some apps/files to DATA instead of SYSTEM:
PDFViewer.apk, PDFViewer.odex, QuickOffice.apk, teeter.apk, teeter.odex.
The system partition would be full otherwise and the ROM was not successfully installed.
Added huge and updated APNs list.
Courtesy of TeamVillain ROMs.
Added small tweaks to the update-script file.
How to install:
Wipe everything:
Data
Dalvik-cache
Battery Stats
Rotate Settings
Flash ROM via recovery mode.
Flash Radio via recovery mode (the phone will reboot twice, do not interrupt the process at any moment).
Reboot the system once after the initial boot.
I suggest to always reinstall the radio after flashing any ROM, I've had GPS problems in the past for not doing so. Either flash the one below or the one that suits you/your network better.
Downloads:
ROM:
http://www.mediafire.com/?w4jnoxnj0em22wmhttp://www.mediafire.com/?mcmzhn0ndjm
Radio:
63.18.55.06PU_6.35.15.11:
http://www.mediafire.com/?nif1igt3moz
63.18.55.06PU_6.35.15.14 (Orange users experiencing SIM lock problems):
http://www.mediafire.com/?mvizwtfjgym
Credits:
ROM: 42turkeys and everyone else involved
Superuser: ChainsDD
Other: Paul O'Brien, Exit93, TeamVillain and everyone else I forgot
Disclaimer:
I will not be held responsible for any damage to the phone and it's your responsibility to make the necessary backups before flashing this ROM.
Does this have root?
Anyone tested on orange branded?
Sonic_01 said:
Does this have root?
Anyone tested on orange branded?
Click to expand...
Click to collapse
I have two problems with this rom.
First root don't work. Tried with Autokiller and no superuser pops up when I try to change the values. - Hense the values isn't changed.
second. - Titanium backup dosn't work. It simply wont start...
Sonic_01 said:
Does this have root?
Click to expand...
Click to collapse
Well, it should...
sblop said:
I have two problems with this rom.
First root don't work. Tried with Autokiller and no superuser pops up when I try to change the values. - Hense the values isn't changed.
second. - Titanium backup dosn't work. It simply wont start...
Click to expand...
Click to collapse
That's odd, this ROM is based on 42turkeys and I don't see anyone complaining about root on his thread. Rooting wise, I only replaced the old Superuser with the newer, didn't change anything else.
I think root is now fixed, I tested Titanium Backup and Root Explorer, both worked fine.
EDIT: Upload finished...
Nazgulled said:
I think root is now fixed, I tested Titanium Backup and Root Explorer, both worked fine.
EDIT: Upload finished...
Click to expand...
Click to collapse
What did you change?
sblop said:
What did you change?
Click to expand...
Click to collapse
or more importantly.... have you tested it!?
sblop said:
What did you change?
Click to expand...
Click to collapse
What do you mean? To make root work? It was a few issues in the update-script. Basically removed /system/bin/su and created a symlink to /system/xbin/su.
And yes, I tested it, I already stated which apps I tested this with .
Nice work, i will test it.
Thanks soo much
Nice work man. Have it on my phone right now and it still works perfectly.
Greets
Nazgulled said:
What do you mean? To make root work? It was a few issues in the update-script. Basically removed /system/bin/su and created a symlink to /system/xbin/su.
And yes, I tested it, I already stated which apps I tested this with .
Click to expand...
Click to collapse
sorry didnt see that the radio you list in first post is known to lock orange branded heros, replace it with the newer one here:
http://forum.xda-developers.com/showthread.php?p=6962178#post6962178
Nice work, REALLY stable version, just what I want
thanks for this release.
@Nazgulled you need to update the radio to .14 for orange users.
andrewb84uk said:
@Nazgulled you need to update the radio to .14 for orange users.
Click to expand...
Click to collapse
Will do, but 2 questions:
1) Where did that new version came from? The other one I got from OTA, what about this .14 version? As far as I can tell, Orange users haven't recieved the OTA yet, or am I wrong?
2) Should everyone else also use this "Orange radio" or are they better off using the "old" one?
Nazgulled said:
Will do, but 2 questions:
1) Where did that new version came from? The other one I got from OTA, what about this .14 version? As far as I can tell, Orange users haven't recieved the OTA yet, or am I wrong?
2) Should everyone else also use this "Orange radio" or are they better off using the "old" one?
Click to expand...
Click to collapse
1) I don't know it just appeared working.
2) Anyone can use it, it works.
I just did another small update to this ROM, adding APNs list, 14 WiFi channels and few small tweaks to the update-script. There's no need to update to this version if you don't care for any of the above.
This is probably the last update to this clean ROM, there's nothing else to do here I believe...
I'll be releasing another ROM (in this thread) with more stuff but nothing too fancy. It will basically be a ROM for me with the stuff I want but I'll release to the public anyway cause someone might be interested. You can still make any suggestions, but I cannot promise you they will be ever added.
Stick to the other ROMs and devs if you're looking for more advanced stuff, my knowledge on the Android scene is somewhat limited for the time being and I don't intend to make anything different from what you can already find on this board.
In short, it will be a ROM customized for my own use.
Time to test some roms.
Hope this one works fine, i am really tiered of buggy roms.
Sharlei said:
Time to test some roms.
Hope this one works fine, i am really tiered of buggy roms.
Click to expand...
Click to collapse
In everyone's defense, if the ROMs you are testing are based on the OTA, it's probably HTC fault if they are buggy. Of course, sh*t happens, but people try to fix it as soon as possible.
Yep, **** happens.
My phone have just rebooted when i tried to take a photo with a lot of apps running in the background. Hate this bug
Hello,
I have successfully rooted my G2 Touch 1.5 with the trickery exploid (hxxp://c-skills.blogspot.com/2010/07/android-trickery.html), because it was not possible to root it with the "One click" method.
Using this guide: hxxp://alldroid.org/default.aspx?g=posts&t=493
According to the README on trickery blog this method should work for 1.x and 2.x firmware. Maybe someone can try this method also for 1.6 and 2.1, if it's working for Hero.
In the attached zip is the changed source code and the compiled binary.
To compile the source follow this tutorial: hxxp://betelco.blogspot.com/2010/01/buildingdebugging-android-native-c.html
skuskom said:
Hello,
I have successfully rooted my G2 Touch 1.5 with the trickery exploid (hxxp://c-skills.blogspot.com/2010/07/android-trickery.html), because it was not possible to root it with the "One click" method.
Using this guide: hxxp://alldroid.org/default.aspx?g=posts&t=493
According to the README on trickery blog this method should work for 1.x and 2.x firmware. Maybe someone can try this method also for 1.6 and 2.1, if it's working for Hero.
In the attached zip is the changed source code and the compiled binary.
To compile the source follow this tutorial: hxxp://betelco.blogspot.com/2010/01/buildingdebugging-android-native-c.html
Click to expand...
Click to collapse
Interesting. Do we have any idea what the 'exploid' package itself does? Just curious. The exploit may well exist in 2.1, but there never was a 1.6 for the hero officially released.
The other method which I released from the Droid Eris folks' work was the 777 permissions exploit. I'm wondering if this could be a similar method, or if it's a totally different attack vector.
Still, would love to know how this one works at a technical level.
EDIT: just noticed you provided changed source code. Taking a look just now...
NOOBIE
Sorry but is there any chance you could throw together a qucik run down of what you actually did compared to the Alldroid guide? sorry but im used to working on my Magic and Dream in which case i would install a new Engineering SPL but i dont know if that would be required on a Hero or not. I dont actually have a Hero to try right now but trying to put a quick guide together for for a friend.
So again i will ask diffrently.....if I follow this guide http://wiki.cyanogenmod.com/index.php?title=Full_Update_Guide_-_Rogers_Dream_911_Patched
The diffrences would be using a Hero recovery, and secondly to skip the part about installing the SPL.
So I guess my question is: All i need is a custom recovery installed right??
Someone please answer, and sorry if it sound like a stupid question (no flamers please)
raymar23 said:
So again i will ask diffrently.....if I follow this guide http://wiki.cyanogenmod.com/index.php?title=Full_Update_Guide_-_Rogers_Dream_911_Patched
The diffrences would be using a Hero recovery, and secondly to skip the part about installing the SPL.
So I guess my question is: All i need is a custom recovery installed right??
Someone please answer, and sorry if it sound like a stupid question (no flamers please)
Click to expand...
Click to collapse
Right. First thing. Forget everything you learned on the magic or dream etc
Second thing. If you're on 2.1, use this method, as all you need is a patched recovery. Then you flash a ROM from recovery and you're sorted.
If you're on 1.5 ROM, then go to http://villainrom.co.uk/viewtopic.php?f=46&t=375 and follow those instructions to root etc. Those are easier methods for now, till we work out how this method works best, and put it to use
anon2122 said:
If you're on 1.5 ROM, then go to hxxp://villainrom.co.uk/viewtopic.php?f=46&t=375 and follow those instructions to root etc. Those are easier methods for now, till we work out how this method works best, and put it to use
Click to expand...
Click to collapse
Yes, but only problem is, that if you should use GoldCard method you lose your original ROM.
And in my country T-mobile didn't release any RUU ROM, which can be flash back in case of warranty.
With this "new" posibility to root you can do NANDROID backup before flashing custom ROM, like it was possible with "One Click" method.
Tnhanks for the answers.
Guess I was trying to complicate something simple
Ill do up a guide on the process after I root the phone. Probably be a few days though.
This will fix Youtube freezing issues for people that are post-OTA AND post-baconbits 0.3 ONLY. I cannot guarantee it will work with any other ROM in any other condition. This will replace your boot.img, and re-load kernel modules (so they match the OTA kernel version) as well as edit init.vision.rc to auto-load vision_oc.ko @1497Mhz.
To the mod that closed my previous thread: HERE IS MY ZIP, IT BELONGS HERE NOW (had you given me 30 more min, I would have posted this in my old thread... but oh wait... someone CLOSED it... thanks for helping with the thread clutter)
http://www.megaupload.com/?d=MQFG74P2
I got the youtube freezing issue after ota and baconbits
gonna give it a try and thanks
how come nobody seem concerned with this issue
Not sure I've had an issue with youtube freezing, but it has seemed to load slower. I just blamed it on crappy wifi.
Sent from my T-Mobile G2 using XDA App
o>c said:
I got the youtube freezing issue after ota and baconbits
gonna give it a try and thanks
how come nobody seem concerned with this issue
Click to expand...
Click to collapse
Concerned? I have been... I tweeted cyanogen and posted on his baconbits forum... but no one cared... so I made my own thread after I had some time to research this issue... and it has to do with us not having the source to the OTA kernel... we only have source to the pre-OTA kernel and it doesn't have this fix in it (who knows what it might be... since we have no source). T-mo/HTC fixed it in the OTA kernel and/or boot.img.
damien667 said:
Concerned? I have been... I tweeted cyanogen and posted on his baconbits forum... but no one cared... so I made my own thread after I had some time to research this issue... and it has to do with us not having the source to the OTA kernel... we only have source to the pre-OTA kernel and it doesn't have this fix in it (who knows what it might be... since we have no source). T-mo/HTC fixed it in the OTA kernel and/or boot.img.
Click to expand...
Click to collapse
For the sake of saving time, which changes to the ramdisk did you make? Also, I'm assuming this is for stock G2's?
eViL D: said:
For the sake of saving time, which changes to the ramdisk did you make? Also, I'm assuming this is for stock G2's?
Click to expand...
Click to collapse
Read my first post. I listed my changes.
To rephrase: It's OTA boot.img with just init.vision.rc changed to auto-load vision_oc.ko(@1497) at boot. update.zip replaces wifi and wifi/calling drivers and adds vision_oc.ko to /system/lib/modules to make them compatible with OTA kernel.
damien667 said:
Read my first post. I listed my changes.
To rephrase: It's OTA boot.img with just init.vision.rc changed to auto-load vision_oc.ko(@1497) at boot. update.zip replaces wifi and wifi/calling drivers and adds vision_oc.ko to /system/lib/modules to make them compatible with OTA kernel.
Click to expand...
Click to collapse
I was curious to the actual line(s) put in the init.rc. But, I can always find out for myself. Just didn't feel like booting to ubuntu...
eViL D: said:
I was curious to the actual line(s) put in the init.rc. But, I can always find out for myself. Just didn't feel like booting to ubuntu...
Click to expand...
Click to collapse
The line in init.vision.rc:
insmod /system/lib/modules/vision_oc.ko pll2_l_val=78
There's no magic going on here, and it was documented by coolbho3000 here: http://forum.xda-developers.com/showthread.php?t=813681
If we perm root our phone after the OTA then the only thing we'll need to add to autoload the vision_oc.ko is that one like to the rc file, correct?
I was going to do that after the line where it did another insmod command.
Does it matter where in the rc file the command is placed?
gteye said:
If we perm root our phone after the OTA then the only thing we'll need to add to autoload the vision_oc.ko is that one like to the rc file, correct?
I was going to do that after the line where it did another insmod command.
Does it matter where in the rc file the command is placed?
Click to expand...
Click to collapse
Correct. I added mine after the kineto_gan.ko insmod. You also need to copy vision_oc.ko to the correct location(/system/lib/modules) and pass it the right argument for the desired max frequency.
Sent from my T-Mobile G2 using XDA App
MOD Edit: This may not be compatible with UK models and may result in a brick. Proceed with caution!
Once this issue has been resolved, PM me (willverduzco) and I will remove this warning.
I am posting this for jwtyler. All questions, comments, and thanks should be directed to him.
UPDATE: This tool is temporarily unavailable. It will be back as soon as jwtyler has time to incorporate a warning about the EU issues and apply a few fixes.
Xoom One Click by Jason Tyler
This is one of my first contributions to the community although I have read and used XDA for years.
If you want to know if you can trust me or my tools check out my upcoming Android App Inventor book on Amazon from John Wiley and Sons.
You can also check my heavy involvement over at the Google App Inventor support forums where I am a community liaison and PowerUser. Hal Abelson will vouch for me. (Heh Heh, Hal will kill me. )
This is an all in one package for Unlock, Root and UnRoot and ReLock of the Xoom MZ600.
It is a GUI front end for the adb commands that are needed.
To use this tool:
1. You MUST have your tablet in Debug mode.
2. You DO NOT have to download the SDK or any images.
3. YOU MUST ACCEPT ALL THE USUAL RISK.
Like ALL rooting there is a risk of bricking your device. It’s a small risk but a risk you need to be aware of.
You WILL void your warranty using this tool.
This tool is easy. I have rooted unrooted and rerooted my Xoom umpteen times today testing it.
NOTE:
The WIFI version tools will only work for unlocking and rooting. I do not have the images for the back to stock on the Wifi.
There are two versions of this tool:
1. Root AND Unroot and back to stock. This one is large because of the stock system.img clocking in at 200+mb
2. The NO UNROOT version. This is lots smaller. It is only about 19mb. You can NOT UNROOT with this tool. (Well, you can unroot but not relock. )
Instructions:
1. Unzip the tool and all of the folders and files into a directory. Preferably a folder on a root drive. (i.e. c:\xoom )
2. Run the Xoom One Click EXE tool and follow the instructions. Read the prompts carefully.
WARNING: WIFI Root is untested as I do not have a Wifi. Let me know how it works. Same process as 3G I just cant test it.
Download Links:
Temporarily Unavailable
Excellent! Thanks!
1st. He he
Xoom Xoom Baby! ...Sent from XDA Premium App
One day warning.
I will be taking this utility down until it encompasses the newest fixes and adequately warns about the EU issue.
I would have taken this down sooner except I was taking a disconnected writing /teaching break and didnt see the issues.
Awesome! Thanks!
Nice! Too bad I rooted before this came up but its nice to see more things available for our xooms!
Thanks!
Sent from my HTC EVO using the XDA app.
Works great on the wifi model! How do you flash the custom rom? tried to said looking for device but wouldn't go any further.
Not sure it worked.
I followed all the steps but i do not see Super User in the app drawer. Should i re-do the steps?
Phutchi said:
I followed all the steps but i do not see Super User in the app drawer. Should i re-do the steps?
Click to expand...
Click to collapse
Have you tested in terminal?
I'm a noob to rooting. haven't done it since my htc wizard. how would i check in terminal?
ok search is my friend. i downloaded a terminal emulator from the market. i enter su and get suermision Denied
and I guess I should mention I am trying this on a WiFi only Xoom.
Thanks Jason for making this. I'll wait for you to add in the HRI66 update first. Gotta have that flash 10.2
One question, does this wipe the device when used? I'd like to root without loosing all my data and game saves. Is this possible yet for this?
Phutchi said:
I'm a noob to rooting. haven't done it since my htc wizard. how would i check in terminal?
ok search is my friend. i downloaded a terminal emulator from the market. i enter su and get suermision Denied
and I guess I should mention I am trying this on a WiFi only Xoom.
Click to expand...
Click to collapse
OK well your not rooted then. Unfortunately I won't be much help due to the fact I rooted via adb.
Hey dude thanks for trying the tool. I am working on updating the tool and when I get the new version posted I will work with you on getting it to work. Thanks for your patience.
For those that might be worried about this because jwtyler has 10 posts... check his sig out. He's been around for a long time and is the Author of App Inventor for Android. So don't worry, he'll take care of it.
I'm excited to try this easy root method out, then overclock my beastly Xoom to 1.5 Ghz
Sweet switched out the Rom files and put in Tiamat Xoom 1.1.6 updated ones works awesome clocked at 1.5 stable with my new wifi only model! Thank You! So easy
Thanks for time and effort!
paulnelson88 said:
Sweet switched out the Rom files and put in Tiamat Xoom 1.1.6 updated ones works awesome clocked at 1.5 stable with my new wifi only model! Thank You! So easy
Click to expand...
Click to collapse
a step by step would be wonderfull. thanks
ericizzy1 said:
a step by step would be wonderfull. thanks
Click to expand...
Click to collapse
I'm just a local electrician but Ive been fascinated by all the work everyone does in here. So I learn things by experimenting I had a hard time with the SDK install and trying to Root my wifi only i just dont have the time to mess around for 4 hrs trying to figure it out but I got lucky with this One Click Root!
Download the updated Tiamat Xoom 1.1.6 BOTH MODELS WORK and unzip them. Then download the One Click Root flies unzip them. Now open the Tiamat 1.0 file in One Click then Delete the flies in there. Go to the 1.1.6 flies and copy them all not folders but files and images then paste. Close out thee program and repopen and install Tiamat follow the instructions. Thats all I did. Worked great ran 2 benchmarks clocked at 1.5 no FC at all!
Files have been removed from mediafire
I removed the files while I fixed an issue with HRI66 OTA breaking the root and soft bricking. The files are in the 3rd post now and Jbrew will update shortly.
OP is updated with new download links.
Please can someone assist with my problem loading 4EXT recovery.
I've downloaded and installed 4EXT Recovery Updater 2.1.4 and installed it on my HTC Desire (with S-OFF). When I run it I'm presented the disclaimer and asked for for root permission (which I give) and I then see the menu (Online Install, Check for news, Recovery etc..).
Any option I select gives me
"Sorry The application 4EXT Recovery Updater (process ext.recovery.updater) has stopped unexpectedly. Please try again".
I guess there must be something about my phone it doesn't like, but what? Other apps appear stable.
I've tried removing, deleting files, rebooting and re-installing.
Any ideas would be most gratefully received, thanks.
Other info:
Used Revolutionary to get S-OFF
HBOOT 6.93.1002
Installed RMD Recovery 1.0.34 succesfully from fastboot on PC-USB
Stock ROM
Model HTC Desire A8181
Android 2.3.3
Baseband 32.56.00.32U_5.17.05.23
Kernel 2.6.35.10-g3f43272
Build 3.14.405.1 CL96875 release-keys
Software (Gingerbread) 3.14.405.1
MICROP-031d
RADIO 5.17.05.23 Jul 22 2011,16:19:16
Contact the developer directly via email or his thread.
Droidzone said:
Contact the developer directly via email or his thread.
Click to expand...
Click to collapse
Only way he can post in his thread is via tapatalk or XDA app, until he has 10 posts.
Or obviously, post 9 spams first
Just use fastboot?
fastboot erase recovery
fastboot flash recovery recovery_name.img
k3lcior said:
Just use fastboot?
fastboot erase recovery
fastboot flash recovery recovery_name.img
Click to expand...
Click to collapse
And where does he get recovery_name.img from?
Fine for one off, but asking people to upload it every time he needs latest version is far from ideal. Better the app works since that's the only way to download it
Sent from my HTC Desire using Tapatalk
Thanks for your replies.
Yes, I don't have enough credits to contact madmaxx82 directly Better earn some more, I guess. I don't suppose someone who does could possibly alert him to my humble post, please?
I've not been able to find 4EXT Touch in .img form anywhere, and wouldn't expect to really. So doing a fastboot flash is unlikely to be a viable solution.
Ok..
Sent from my HTC Desire using Tapatalk
hi,
may i suggest you remove ext4 permission from su applist.
Pm sent
I suspect busybox. Stock rom must be the problem there..
But let's see.
Ahhhhhhhhh!!!!
Thank you all for your assistance, especially madmaxx82 for his PM which enabled me to solve the problem.
Confession time, I think.
I'm a noob to smartphones and Android as you can probably tell, and have been reading loads of blogs, forums etc. etc. trying to understand rooting benefits, issues and procedures. I've read so much that it's starting to hurt. There is so much info out there including some heroic posts on rooting from first principles. However, a lot of techniques have been superceded and you often run up against dead ends, finding that the method you hoped to use is now outdated. Noobs have to be patient enough to solve the puzzle piece by piece. I'm very patient, fortunately.
With that in mind prepare to gasp in amazement at a big hole in my knowledge of this subject after days of reading. Everyone refers to S-OFF and rooting as the big things to achieve on the way. S-OFF I got fairly quickly, but the term "rooting" is badly misused by many and not well described in terms of what constitutes a rooted system. Usually people tell you what you can do with a rooted phone and not the necessary software components you find in one. Until madmaxx82's PM I didn't appreciate that apps need superuser to do their work. Also, In my naivity I thought that apps accessed the filesystem on their own using some kind of system API rather than needing busybox to issue commands.
I know, horrific isn't it - how do I manage to feed myself, you're wondering.
Anyway, after flashing superuser and installing busybox I was able to use the 4EXT Recovery updater and now have 4EXT recovery installed. After getting used to that I'll upgrade to Touch.
Ironically, if I'd just flashed a pre-rooted ROM rather than trying to root my own stock ROM, I'd never have run into this difficulty. Now, I wonder what adventures lie ahead on the road to total enlightenment.
Thanks again for your help, Gentlemen.
grmm22 said:
Thank you all for your assistance, especially madmaxx82 for his PM which enabled me to solve the problem.
Confession time, I think.
I'm a noob to smartphones and Android as you can probably tell, and have been reading loads of blogs, forums etc. etc. trying to understand rooting benefits, issues and procedures. I've read so much that it's starting to hurt. There is so much info out there including some heroic posts on rooting from first principles. However, a lot of techniques have been superceded and you often run up against dead ends, finding that the method you hoped to use is now outdated. Noobs have to be patient enough to solve the puzzle piece by piece. I'm very patient, fortunately.
With that in mind prepare to gasp in amazement at a big hole in my knowledge of this subject after days of reading. Everyone refers to S-OFF and rooting as the big things to achieve on the way. S-OFF I got fairly quickly, but the term "rooting" is badly misused by many and not well described in terms of what constitutes a rooted system. Usually people tell you what you can do with a rooted phone and not the necessary software components you find in one. Until madmaxx82's PM I didn't appreciate that apps need superuser to do their work. Also, In my naivity I thought that apps accessed the filesystem on their own using some kind of system API rather than needing busybox to issue commands.
I know, horrific isn't it - how do I manage to feed myself, you're wondering.
Anyway, after flashing superuser and installing busybox I was able to use the 4EXT Recovery updater and now have 4EXT recovery installed. After getting used to that I'll upgrade to Touch.
Ironically, if I'd just flashed a pre-rooted ROM rather than trying to root my own stock ROM, I'd never have run into this difficulty. Now, I wonder what adventures lie ahead on the road to total enlightenment.
Thanks again for your help, Gentlemen.
Click to expand...
Click to collapse
have a read of teh rooting faq linked via my signature. Should help clarify quite a lot for you hopefully.
rootSU said:
have a read of teh rooting faq linked via my signature. Should help clarify quite a lot for you hopefully.
Click to expand...
Click to collapse
I think I read the rooting guide at one point in my journey and found it very useful indeed. Much appreciated In my noob head I still managed to associate the superuser app with unrEVOked, specifically, rather than 'a rooted phone no matter how achieved'.
I'm wondering is this is a true and complete definition of rooting? "A rooted phone is one in which apps can be granted root access permissions when needed. Rooting always means installing the superuser app so that this can happen. For superuser to function the security flag has to be set to S-OFF. There are several ways of installing superuser and setting S-OFF but these two things are the essence of a rooted phone".
Superuser is a two pronged armament that communicates with the Linux based core Android system and gives you permission to interact with and modify system files, and run certain system programs which require elevated permissions. One, the superuser binary, /system/bin/su provides this functionality, while another, superuser.apk is a gui which allows you to control which apps should be given permissions, and provides an interface to su binary. Busybox is a Linux 'Swiss army knife' utility, much like the multi purpose knife, it is a collection of different Linux utilities, like mount, format, file system check, grep, sed, tar, .. you name any Linux based binary, most of it in Android is provided by busybox. You want to reboot the phone, you need busybox.
Neither of them require s off. Rooting is the process of unsecuring your boot image, and installing superuser and busybox..Once that's done, you can modify and see stuff on /data, that is application data. But you still can't modify system files in /system, on the fly if you're simply rooted (though you can modify them from recovery). That is protected by the radio security flag. S off allows you to do that.
I think that's enough info for one day.
Well I for one would .like.more
Sent from my HTC Desire using Tapatalk
Well there's nothing new that I can tell you!
Droidzone said:
Superuser is a two pronged armament that communicates with the Linux based core Android system and gives you permission to interact with and modify system files, and run certain system programs which require elevated permissions. One, the superuser binary, /system/bin/su provides this functionality, while another, superuser.apk is a gui which allows you to control which apps should be given permissions, and provides an interface to su binary. Busybox is a Linux 'Swiss army knife' utility, much like the multi purpose knife, it is a collection of different Linux utilities, like mount, format, file system check, grep, sed, tar, .. you name any Linux based binary, most of it in Android is provided by busybox. You want to reboot the phone, you need busybox.
Neither of them require s off. Rooting is the process of unsecuring your boot image, and installing superuser and busybox..Once that's done, you can modify and see stuff on /data, that is application data. But you still can't modify system files in /system, on the fly if you're simply rooted (though you can modify them from recovery). That is protected by the radio security flag. S off allows you to do that.
I think that's enough info for one day.
Click to expand...
Click to collapse
Thank you. That's the clearest description of the mechanics of rooting that I have read.
I'm going to go and lie down for a bit now.
Ice cream cools the mind
Sent from my HTC Desire using Tapatalk