Database Users

New method to Root?

Just wondering if there will be a new method of rooting. Like the one click method over at android central which does not work since the DIO1 update. All the other methods require all kinds of command prompt.
Swyped via Fascinate.

the one click root method that has been there since the beginning is easy all you do is download the file unzip it and click start root. cant get much easier then that

Yeah, I can confirm that one click root still works for me on the DIO1 update.

If for some reason once click root isn't working on your PC, just do the manual adb method, its really the same thing.

Super one click root works for almost everything, including the fascinate
Sent from my SCH-I500 using XDA App

One click root didn't work for me, I could write a new one for you, but honestly the manual adb method is pretty easy you just copy and paste the commands.

I always get the same device not found for me.
Swyped via Fascinate.

shawn_pike said:
******************************************************************************
* *
* Dirrk's EZ Root v0.2 (Sebastien Krahmers Exploit) *
* *
******************************************************************************
*
* Testing if your device is connected
*
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
I500982af593 device
*
* If you are NOT connected please follow these directions
* Install the correct drivers
* Turn On Debugging
* Check usb port, cable and phone
* Then rerun this application
*
Press any key to continue . . .
*
* Pushing the files to your phone
* rage.bin, busybox, Superuser.apk, su, com.sh
1259 KB/s (1867568 bytes in 1.448s)
89 KB/s (26264 bytes in 0.285s)
876 KB/s (196521 bytes in 0.219s)
114 KB/s (5392 bytes in 0.046s)
5 KB/s (281 bytes in 0.052s)
* Restarting your phone to ensure the exploit will work
* When your phone comes back on please unlock it if it is locked and then
* wait
* About to exploit your device
* This will take about 3 minutes
*
* If it doesn't respond after waiting 5 minutes then it probably failed,
* so you should close this and run again
*
* Start Time: 19:58:31.93
*
error: device not found
*
** Successfully exploited, installing permanent root files and deleting temp fil
es
*
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found*
* Restarting your phone now.
*
error: device not found
* Complete
*
******************************************************************************
Press any key to continue . . .
This is the error i get no matter what I do....
Drivers are installed
debugging is on..
Any Ideas?
Click to expand...
Click to collapse
Swyped via Fascinate.
Swyped via Fascinate.

This is the same message I aways get.
Swyped via Fascinate.

Just Odin cwm, and flash superuser from chainsDD.

Flash CWM. Have root. Install su / busybox if necessary.

I'm sorry but that doesn't work for me.
Swyped via Fascinate.

I'm sorry but yes flashing clockwork with Odin does work for u. And unfortunately if using Odin doesn't work u need to stop and forget about root. Likely u don't have the drivers correctly installed. I would put money on it. Especially if u have windows7. Odin can And will work EVERY SINGLE TIME.
Sent from my SCH-I500 using XDA App

I'm sorry its just I rooted the X with no problem and now this is giving me a hard time. if your could just point me in the right direction that would be great. sorry for the trouble.
and i'm have vista

also when i plug my phone in it says the device drivers were installed successfully and are ready to be used...

1.download odin and odin files for the cwmkernel and recovery.
2.turn phone off, hold down the vol. down button only and plug phone into pc. this well put you into download mode.
3. open odin and click the pda button and flash the kernel then flash the recovery.
4.while in recovery either push your files or flash on of the roms with root and everything in it
Sent from my LV-Voodoo Fascinate using XDA App

If rooting via manual method is too complicated for you perhaps you shouldn't be rooting your phone. No offense but we have had a lot of people not knowing what they're doing and soft bricking their phones. They can't fix it because they don't know what they did.
Sent from my SCH-I500 using XDA App

works with dI01
I followed these instructions here to the dot:
h ttp://forum.androidcentral.com/fascinate-roms-hacks/33899-how-root.html
I got my phone just over a week ago, came with DI01 on it..
It took me three tries using the one click method, as I was getting device not found errors.. The time it worked, I had just rebooted PC and phone
When your phone restarts be sure to unlock it as fast as you can.. that seemed to help mine as well.

You can just manually do a adb install same as one click
Also make sure you have drivers installed

New Info about Clockwork Brickings

Hi devs,
Strictly speaking, this is not a development issue, but I thought it warranted some special attention as it sheds a little bit of new light on the "bricking" caused by Clockwork (version unknown).
A new XDA member, SoSickWiTiT, brought back an Eris from the grave. The phone he started with could only be put into RUU mode - initially it would not even start correctly in Hboot or Fastboot mode (weird, right?), and is now fully functional. The long and tortuous thread is here in the Q&A forum.
The essential finding was that the "bricking" was apparently caused by enormous numbers of pages in the flash memory device being marked as bad pages, and that this was correctable by using the "flash_erase" tool of the mtd-util project. (This tool allows you to reclaim flash pages marked as bad if they erase successfully.) I built some of the tools for ARM/Android and posted them up here.. As long as you can get Amon_RA to come up, you can run this tool from Amon_RA (using adb) and erase/reclaim partitions on a partition-by-partition basis.
Also SoSickWiTiT found a useful hack that I hadn't seen before: because he could only get his phone to start in RUU mode, he started the "Official RUU", ran it to the point where it unpacks all files, and then replaced the "rom.zip" file (in the Temp folder the RUU utility unpacks) with the HTC Root-ROM (renaming it to "rom.zip", of course). Because it signed by HTC, it got the 1.49.2000 S-OFF bootloader installed (but the rest of the install failed). SoSickWiTiT was then able to flash Amon_RA via fastboot and continue gaining traction from there. Note that just flashing a ROM from this point would not work - his mtd3 (system) partition appeared as if over 60% of the pages were marked as bad, and I think his boot partition was similarly affected. "flash_erase" was able to reclaim these pages using the "-N" command line option.
Anyway, the behavior of his phone (excluding the RUU-only behavior) was consistent with prior bricking reports of how filesystems appear to be "corrupted", and this causes difficulties flashing new ROMs (largely due to lack of free space). SoSickWiTiT reports that the phone he obtained from a friend had been bricked by "a failed ROM flash in Clockwork/ROM Manager followed up with an attempt to use the RUU" - there have been at least one other report of this exact same scenario causing the "bricking".
So now I am wondering - are there a few "bricks" laying around that might be rescued?
bftb0

Very interesting and good to know, thanks! And thank you for the tool, great work.

Think this could be applied to deleting the NRAM flash on a router? =p

WAIT wait wait!!!
He changed the bootloader from S-On to S-off??? Was it on 1.49? If so couldnt that have been used to root our phones, A LONGGG time ago? lol

Nikolai2.1 said:
WAIT wait wait!!!
He changed the bootloader from S-On to S-off??? Was it on 1.49? If so couldnt that have been used to root our phones, A LONGGG time ago? lol
Click to expand...
Click to collapse
A looooooong time ago - December '09 (circa "MR1") iirc, someone attempted to stuff a different - and unsigned - "rom.zip" file into the running (MR1) RUU.
Naturally, that didn't work, 'cuz it wasn't a HTC-signed PB00IMG.zip file. To my knowledge, this is the first time anybody tried doing things this way (swapping in the validly-signed HTC Root-ROM into the RUU's "rom.zip" location)... maybe it would have worked for the "leakers". I suppose that someone could roll back their phone and give it a shot to see it if works, but that seems sort of academic at this point - hence your "LOL".
There is evidence that both the RUU- and Hboot- based update processes actually end up checking the contents of the "misc" partition for version information TWICE - first before any flashing occurs, and second, only after the bootloader has been flashed and reloaded, but before the remainder of the PB00IMG.zip/rom.zip file has been flashed. I don't think that even at this point in time this behavior is well understood: it is possible that the hboot flash of the bootloader can occur, but then the subsequent flashing of the rest of the PB00IMG.zip file fails due to a "Main Version is Older" error. Sort of hard to understand why that would ever occur (it happened to me once, so I know it occurs).
For anybody that has a brick, but can get RUU mode running, it is certainly worth a try to see if they can replace the bootloader with the S-OFF bootloader - what do they have to lose? In this particular case, it is hard to know what the state of the misc partition was; after all, it was a phone that was previously rooted. The result obtained using the RUU utility likely depends on what was going on in the misc partition on that phone, so it is not obvious that this (RUU utility) "trick" is universal. It might have been that the same phone would have been happy to accept the Root PB00IMG.zip file - but SickWiTiT couldn't get the phone into Hboot mode initially, so that wasn't tried.
cheers
bftb0

So if I have been using Clockwork to flash a few roms do you think I would have any bad pages in my flash memory? Is there an easy way to check this?

xtreme3737 said:
So if I have been using Clockwork to flash a few roms do you think I would have any bad pages in my flash memory? Is there an easy way to check this?
Click to expand...
Click to collapse
I don't think that using Clockwork causes slow growth in bad pages; afaik, when the problem occurs - whatever causes it - only then do you see a catastrophic number of pages marked this way. I mentioned it only in case someone bricks their phone and then asks for advice here - they can check to see if this repair works for them at that time - after they have determined that this is the nature of their problem. In the meantime, there is not much need to worry about it.
Short of actually performing a flash_erase with the "-N" option turned on, I don't know off the top of my head a way to determine the number of bad blocks easily, and there are good reasons why you should not be doing that unless you absolutely have to.
The tool "nanddump" that I compiled actually reports the number of bad blocks - but it also wedges the Amon_RA kernel when you run it. Rats.
bftb0

I just wanted to add my thanks for this very informative and interesting information and tool in case it becomes necessary. I do use Clockwork (loaded from Amon RA), BTW.

Thanks for the useful info as always.
It really seems like a bad idea to use clockwork
Sent from my nonsensikal froyo

SikYou said:
Thanks for the useful info as always.
It really seems like a bad idea to use clockwork
Sent from my nonsensikal froyo
Click to expand...
Click to collapse
bftb0 said:
I don't think that using Clockwork causes slow growth in bad pages; afaik, when the problem occurs - whatever causes it...
Click to expand...
Click to collapse
I haven't once had an issue with Clockwork Mod through ROM Manager, and have been using it for 3+ months now.

thanks for this thread i sort of helped one person put their phone into the grave by telling them to flash an ruu (still feel bad about it)

jamezelle said:
thanks for this thread i sort of helped one person put their phone into the grave by telling them to flash an ruu (still feel bad about it)
Click to expand...
Click to collapse
That cus you are a baddie jamezelle xD

Very informative read, thanks bftb0!

I spent some time tonight fooling around with RomManager (v3.0.0.7) and ClockworkMod (v2.5.0.1 for the Eris). Sort of an eye-opener, actually.
The way it works is that it is actually NEVER "FLASHES" ANYTHING TO THE RECOVERY PARTITION. Instead, when you first tap on the menu item to "flash the recovery", what ROM Manager does is identify your handset type, and then downloads some files to
/sdcard/clockworkmod, e.g.:
/sdcard/clockworkmod:
----rwxr-x 1 system sdcard_r 829658 Jan 17 02:23 recovery-update.zip
/sdcard/clockworkmod/download/koush.tandtgaming.com/recoveries:
----rwxr-x 1 system sdcard_r 829658 Jan 17 00:56 recovery-clockwork-2.5.0.1-desirec.zip
/sdcard/clockworkmod/download/rommanager.appspot.com:
d---rwxr-x 2 system sdcard_r 4096 Jan 17 02:23 manifests
/sdcard/clockworkmod/download/rommanager.appspot.com/manifests:
----rwxr-x 1 system sdcard_r 11492 Jan 17 02:23 devices.js
Note that "recovery-update.zip" and "recovery-clockwork-2.5.0.1-desirec.zip" are the same size - less than 1 MB. In fact, they are identical. It is a signed update package - but too small to even contain an Android kernel.
Here's how ROM Manager works: when you press the button "Reboot into Recovery", what actually takes place is this:
- Rom Manager copies "recovery-update.zip" into /cache/update.zip, and then places the following command into /cache/recovery/command
Code:
"/sbin/recovery" "--update_package=CACHE:update.zip"
and then executes a "reboot recovery" command.
The next thing that happens is that whatever Custom Recovery that IS ALREADY FLASHED to your recovery partition on the phone boots up, and immediately begins to process the /cache/update.zip file
Here's the $64,000 observation:
This update.zip modifies NOTHING IN FLASH MEMORY - IT ONLY MODIFIES THE RAMDISK OF THE BOOTED RECOVERY ALREADY PRESENT.
Towards the end of the updater-script, it kills off the old /sbin/recovery and /sbin/adbd processes; but since these processes are defined as services, they get restarted automatically, using the new "ClockworkMod" version of these program files. Voila! The ClockworkMod recovery menus pop up.
There are two important observations that arise from this analysis:
- It does not have it's own kernel - it uses the kernel of whatever was already present in the recovery partition boot
- To get ClockworkMod to be cold-bootable, you need to COMBINE IT WITH A KERNEL AND BOOTSCRIPTS FROM SOMEPLACE ELSE - but WHERE exactly?
Now, I don't know if ROM Manager formerly worked in a different fashion - but the point is fairly obvious: if you wanted to provide a rooting method which installs "ClockworkMod" as a recovery - well then, you would need to combine the minimal components of "ClockworkMod" (mostly just the /sbin/recovery program !) with someone else's bootable recovery. And you could not use an HTC stock recovery - because then koush's "update.zip" files would have needed to be signed by HTC in order to get processed.
If you accept the hypothesis that the so-called "Clockwork" brickings have been due to a bug in the kernel MTD driver - and nobody ever seems to see those bugs happening with Amon_RA v1.6.2 - then the real problem comes from a kernel which is was kanged into a flashable "Clockwork Mod" recovery by a third party - not koush.
Who is it then - the unrevoked team? Someone else? What kernel is it?
As I recall, nearly every one of the brickings that have been reported here have been folks that got their rooting instructions from outside the XDA Eris community.
Bottom line - it's starting to look like the problem is not really due to Clockwork - its a problem kernel from unknown origins.
Perhaps Rom Manager did not always work this way on the Eris - but the way it works now is that if you install it after already having Amon_RA in the recovery partition, if you cold-boot (Vol-up+End or via HBOOT), what will come up is Amon_RA, not Clockwork.
So - if you can cold-start your phone into recovery, and up pops a ClockworkMod menu instead of a Amon_RA menu - how did you root your phone originally?
bftb0
(sorry if this post is a bit of a ramble - it's pretty late/early)

When I 'cold boot' I get the Clockwork V2.5.0.1 screen.
I rooted originally the day root was discovered here at XDA. I originally loaded Amon. Somewhere in the last year, I may have clicked the 'install Clockwork mod' at the top of ROM Manager, but I don't think I did.
I don't know if this helps, but I found your post interesting.

meanm50 said:
When I 'cold boot' I get the Clockwork V2.5.0.1 screen.
I rooted originally the day root was discovered here at XDA. I originally loaded Amon. Somewhere in the last year, I may have clicked the 'install Clockwork mod' at the top of ROM Manager, but I don't think I did.
I don't know if this helps, but I found your post interesting.
Click to expand...
Click to collapse
Huh.
If you do that, and then fire up an adb session, what kernel string does
Code:
adb shell uname -a
report?
When I click "Flash ClockworkMod Recovery", all it does is ask me to verify the phone model ("Droid Eris (CDMA)"), requests root (SuperUser), goes to the Internet and downloads stuff, and then pops up a message on the screen saying "Successfully downloaded Clockworkmod Recovery!" If I shut down the phone normally and then cold-boot the recovery afterward, what is there is Amon_RA - not clockwork.
Hmmm. Just used it to perform a ROM backup**. For this operation, the same thing happens - Amon_RA comes up first, followed by chaining to ClockworkMod and then the backup starts happening. I note that it also backs up the recovery partition - maybe it only modifies the recovery partition when it is installing a new ROM?
Hmmm (part 2). Just wiped and flashed a clean ROM using Clockwork. Cold start into recovery afterward gives me Amon_RA, not Clockwork.
Maybe koush has changed the basic methodology somehow. I have to say, the way I currently am experiencing it makes a great deal of sense - it means that koush does not need to be in the kernel-making/kernel-collecting business in order to support ROM Manager on a new handset.
Can anyone with a more long-term exposure to Rom Manager/ClockworkMod (on the Eris) shed some light on this?
bftb0
** Interesting side note: CWM backup now backs up (and I presume restores) /sdcard/.android_secure; also, a "wipe" operation will attempt to wipe any SD card ext partition if it is found.

I will adb when I get home...my work comp doesn't have the required programs installed...

bftb0 said:
** Interesting side note: CWM backup now backs up (and I presume restores) /sdcard/.android_secure; also, a "wipe" operation will attempt to wipe any SD card ext partition if it is found.
Click to expand...
Click to collapse
Also the /cache partition.

bftb0 said:
Huh.
If you do that, and then fire up an adb session, what kernel string does
Code:
adb shell uname -a
report?
Click to expand...
Click to collapse
Linux localhost 2.6.29-DecaFuctCFS-dirty-c6271491

meanm50 said:
Linux localhost 2.6.29-DecaFuctCFS-dirty-c6271491
Click to expand...
Click to collapse
Sorry - I meant adb with your recovery booted, not the normal OS. (The above must be from your regular OS right?)

[22/12/10][SUSPENDED] IcedCube GingerHD2 [Rooted][Experimental][MDJ Kernel]

PLEASE READ THIS POST AND UNDERSTAND IT CLEARLY BEFORE USING THIS ROM!​
Heyo,
This ROM is now a port of the Nexus S Gingerbread ROM leak for the HD2. I would like to make it clear that this ROM may be unstable and not for everyday use! Since we're using a version of Android designed for a different device, we may have issues. The leaked build I'm using is available here - some modding is required though.
Starting from 0.05, my builds come with a 96MB Data.img file to get you out of trouble. I will provide data.img files that are 128MB, 256MB, 512MB and 768MB in size. You can make your own image via a terminal on Linux like this (don't type the dollar sign or the stuff behind it)
Code:
[email protected]:~$ dd if=/dev/zero of=/path/to/Android/folder/data.img bs=1M count=128M
[email protected]:~$ mke2fs /path/to/Android/folder/data.img
(answer 'y' to the question when mke2fs says "data.img is not a special block device, proceed? [y,n]")
Installation
Extract the "Android" folder in the ZIP file below to your MicroSD Card, pop it into your HD2, open File Explorer from WinMo, find the Android folder, tap CLRCAD.exe and then Haret.exe and watch the sparks fly.
For patches, extract the files in the patch archive to your MicroSD Card, overwriting any existing files.
Downloads
You can download the ROM from my server below. Please don't use download accelators, they will make my VPS cry...
LATEST VERSION IS 0.5, PLEASE DO NOT USE OLDER VERSIONS AS YOU WILL BE ASKED TO UPGRADE IF YOU SAY SOMETHING IS NOT WORKING ON THOSE OLDER BUILDS!
Version 0.01 > Get the goodness here! <
Version 0.02 (Patch only, download v0.01 first!) > Get the goodness here! <
Version 0.03 (Only a data.img for people who are having boot problems) > Get the goodness here! <
Version 0.05 > Get the goodness here! <
Version 0.05 requires 7-Zip to extract
Disclaimer
If I used any of your works and I did not acknowledge you, I am not claiming your work as my own. That would be the wrong thing to do (and I am not intending to "kang" any sources). I am also not responsible if your device is bricked or broken by direct or indirect use of this ROM.
Credits
spbeeking - The person that dumped the gingerbread SDK build in the other thread, in which that got over 210 Posts.
dakluck - Found the fix for BSOD (temporary).
m-deejay - Used his kernel. They rock.
jubeh - Found the problem with the SDK Build's lagginess.
supercurio - For the Nexus S ROM Dump.
...last but not least, all HD2 Owners that have given up 250MB+ of their MicroSD Card space to test GingerHD2.
Credit will be given where due. Watch this space!

Changelog Key:
+ means addition/change
- means removal
[!] means danger/caution.
v0.0.6 - Changed over to m-deejay's Gingerbread, working with his base to make a "lite" ROM.
This version is currently under development and will be released when deemed finished!
v0.0.5 Release 1 - ??/12/10 - Coming very soon.
+ Switched to Nexus S ROM Base
+ Replaced Nexus S default GL drivers with the ones for the HD2
+ Working Radio - SMS & Texts should work...
v0.0.4 - 10/12/10 - R.I.P, I totally fudged up v0.04 SDK Sources. Stupid me!
v0.0.3 - 10/12/10 - Patch 2
+ Basic data.img only for people with boot problems. Only use with older releases, don't use it with v0.0.3+ builds.
v0.0.2 - 8/12/10 - Patch
+ Switched kernel to m-deejay's kernel for working 3G Connection, data should work.
+ Fast bootup speed.
[!] Black Screen of Death occurs if you allow the device to go to sleep.
NOTE: BSOD can be fixed temporarily, see below.
[!] Erratic behaviour occurs if you haven't PIN unlocked your SIM Card before booting this ROM.
[!] Can take a while to do things, ie. very laggy.
[!] Black screen after HTC logo, no android logo.
[!] Keyboard comes up as white space (?)
... Possible other things that are buggy or whatnot.
v0.0.1 - 8/12/10
+ First release. Boots somewhat and then has problems.
Temporary Fix for BSOD in sleep (present in v0.0.3 and below)
After pressing power button once, press and hold power button till vibrate, then press back button. May take a few attempts but persistance is key.
(Credit to dakluck)
Bug List
None as of yet for 0.05... (Currently in-dev)
(Outdated) Checklist
WiFi? Not yet working.
BlueTooth? Not tested.
SMS Sending? Seems so (according to m-deejay).
Calls? Working.
3G Data? Working - select APN before going on the 'net.
Sound? Not working, but I'm working on it.
Camera? Not working.
Camcorder? Not working.
Screen (blacklight, touch etc)? Working.
Lights (keypad): Working.
Accerometer/G-Sensor? Not working.
(..to finish..)
Having boot problems?
Download the 64MB Data.img which is v0.03 (it's just a zip with the data.img I use for this ROM) and extract it to the same folder (for example, if GingerHD2 is located in GingerROM on your MicroSD Card, extract it to that folder). Then you should get to the desktop.

IcedCube said:
Reserved for changelog and other stuff
Click to expand...
Click to collapse
that's pretty nice gingerbread , cooool i can't wait to see this fully working

WOW !
Keep up the amazing work !!!
much appreciated.
I will try the build now.

Cool thank you.

thanks
excellent work,at less we can have a try for 2.3,thanks.keep working on 2.3

As I've said, you won't get into the Android UI, but if you can confirm that the kernel is getting stuck at "init: untracked process X exited unexpectedly", that would be appreciated.

Nice work, thanks for sharing. The init.rc file you mention is linked to a pastebin link in the original dump thread. Should be easy to search.

phiredrop said:
Nice work, thanks for sharing. The init.rc file you mention is linked to a pastebin link in the original dump thread. Should be easy to search.
Click to expand...
Click to collapse
No worries. My eMac is being a pain, so I'll have to find the pastebin link manually.

Just a quick bump, I'm just fixing the bootup issue. Once done, I'll upload a patch for you guys (and girls).

Cool... I will give it a spin
Sent from my HTC bravo using XDA App

Keep up the good work. My pray from Indonesia
Sent from my Nexus One using XDA App

Thanks for the credit and all, but didn't you say that you used your own sdk dump?
Sent from my Decepticon using XDA App

spbeeking said:
Thanks for the credit and all, but didn't you say that you used your own sdk dump?
Sent from my Decepticon using XDA App
Click to expand...
Click to collapse
I just wanted to give you a shoutout because you did the dumping before I jumped into the fray and dumped the sources myself
And on that bombshell, the v0.02 patch is up! See the second post for changelog, and first post for downloads. Here's how to install the patch:
For patches, extract the files in the patch archive to your MicroSD Card, overwriting any existing files.
Click to expand...
Click to collapse
It couldn't get any harder. Or could it...?

thanks alot!
seems like the 0.02 patch is down.
mirror pls!

the patch is down

where is the patch? the broken patch link....

youngquazy said:
the patch is down
Click to expand...
Click to collapse
Patch is online; uploaded to wrong folder on VPS. Oops.

Version 0.02 download link Damage

File patch is missing in your server. Version 003 is imminent? thanks

[Q] Bad Rootedupdate? <Solved>

Hi all,
I've been trying to root my legend again (had to unroot it after the first time because I got stuck in a boot loop..)
But now I get stuck at the last step; flashing rootedupdate.zip
Let me first say that everything upto running step2-windows.bat went well, except for step2-windows.bat being unable to write rootedupdate.zip to my sdcard (I/O error).
So I manually copied it to the sd-card to be able to flash it.
However, it now gives me an error, saying
"E: Can't open /sdcard/rootedupdate.zip (bad)"
Does anyone recognize this or know what might cause this? I've tried different rootedupdate.zips, from different locations, but keep getting the same error.

Try download any other rooted rom.. just flash the other rom instead..
Sent from my Legend using XDA App

whitetigerdk said:
Try download any other rooted rom.. just flash the other rom instead..
Sent from my Legend using XDA App
Click to expand...
Click to collapse
Where to find another rooted rom then?
I've already tried different rootedupdate.zip files, since that's the rooted rom always used in guides.

Just flash CM or B or any other from dev forum.
Sent from my HTC Legend

I'm trying to do so now, but I now get stuck at the second step itself. It gives me the following output in my command line;
Code:
Legend Root Step 2
Pushing required files to device...
error: protocol fault (no status)
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
- exec '/system/bin/sh' failed: No such file or directory (2) -
Pushing update file to device sdcard - this may take a few minutes...
- exec '/system/bin/sh' failed: No such file or directory (2) -
To give some more details;
- HBOOT 1.01
- Android 1.31 is running
- Goldcard succesfully created (even re-did this to be sure)
- Step 1 completed succesfully (as far as I can see)
Does anyone know how to solve this?

Just follow the instructions for fake-flash.
Sent from my HTC Legend

BlaY0 said:
Just follow the instructions for fake-flash.
Sent from my HTC Legend
Click to expand...
Click to collapse
You rock!
Never thought of using fake flash for this purpose
But it worked like a charm! Thanks!

[TOOL]PERI-0.42 One click root+recovery/fix-bootloops+soft-bricks ALL Devices+.27! :D

TF101, SL101 and TF101G on ICS firmwares anything else is untested.
Also should work on TF201 and TF300T on ICS ONLY!
For Windows, tested on windows 7 x64 bit, xp 32 bit and windows 7 32 bit.
Your data will be retained, unless you wipe in TWRP or something
UPDATE:
Added V0.41 which includes TWRP
Also V0.42 which is even newer TWRP!
apk not working sofar :[
If you have a TF201, or TF300T, this will work still, but you need to replace the included file 'recoveryblob' with a recoveryblob from a recovery from your device (download the .zip file for the recovery you want, and extract the 'blob' or 'recoveryblob' file from it and place in PERI folder, naming it recoveryblob and overwriting the otherone!)
Initiate project-PERI:
Since there's no one-clicks that I've stumbled across, and many people are asking if this-that etc.. works with .24, I've made an easy one-click (ish) that guides you through it and runs the necessary commands.
Thanks to:
Team Rouge (I used their touch recovery version)
Wolf (For his method to flash recovery!)
Roach (Bootloop fix)
Members here for testing help :] (I'm bad about typos...)
Download here (feel free to mirror):
V0.1- Platypus - 13.42MB
Version 0.1
Mirror - Thanks Alan1995
Mirror 2 - Thanks Alan1995
V0.2- Elephant - 13.39MB
Version 0.2
Mirror - Thanks Alan1995
Mirror 2 - Thanks Alan1995
Mirror 3 - Thanks Alan1995
V0.3- Raptor - 13.39MB
Version 0.3
Mirror - Thanks Alan1995
Mirror 2 - Thanks Alan1995
Mirror 3 - Thanks Alan1995
V0.4- Indri - 13.39MB
Version 0.4
Mirror - Thanks Alan1995
Mirror 2 - Thanks Alan1995
Mirror 3 - Thanks Alan1995
V0.41- TwrpyIndri - 14.29MB
Version 0.41 (TWRP 2.3.2.3)
V0.42- TwrpyIndri Cutting Edge - 14.15MB
Version 0.42 -- Recommended (TWRP 2.5.0.0)
Just unzip it to a folder anywhere and run the .bat file!
Works with or without MicroSD, just let the device totally reboot (E.G. don't let any commands run at the splash screen or in recovery.)
Fixed reboot confusion in V0.2 -Didn't fix in v0.2, Did fix in v0.3 though
If I did anything wrong, or offended any devs, killed someone's cat, or something else, Please let me know!
Post here with any questions or problems, I tested this and everything worked fine, but still consider it as final? release candidate 4.
Did it work?
This should do everything needed, and all is included in zip!
If you want to skip any steps that you've already done if you mess up, just unplug the USB and pretend that it isn't throwing 'device not found' errors, then get back to where you were.
If superuser isn't installing but you have recovery, try 'fix permissions' in recovery. -- Fixed (hopefully) in V0.2
Read the readme and run as administrator! Video-tut is here!
**Also attached to thread.**
PERI - Changelog --
Code:
[*][B]V0.42[/B]
-- Added [I]cutting edge[/I] TWRP 2.5.0.0
-- Thanks jazzruby
[B]V0.41[/B]
-- Added TWRP 2.3.2.3 recovery, finally c:
-- Fixed a couple typos.
-- Fed a llama candy.
[B]V0.4[/B]
-- Added option for ROOT users to just flash recovery.
-- Added unbrick/bootloop fix option for those that can access adb (hopefully works)
-- Bug fix, minor layout change.
-- Second-Last windows release! :D 'Last is auto APX unbrick..' Then the app.
-- Indri
[B]V0.3[/B]
-- Fixed reboot typo that causes failed reboot
-- Other layout issues and typos
-- [I]Added a Readme, read it[/I]
-- Got angry at video recorder for not working.
-- Raptor
[B]V0.2[/B]
-- Fixed a few layout issues and typos.
-- Added driver autoinstaller for Windows 7. (XP Can still use manual)
-- Updated the SU zip I was using, hopefully fixes fake error messages.
-- Fixed reboot confusion (Reordered command layout)
-- Elephant
[B]V0.1[/B]
[I]-- Initial Release[/I]
-- Helps you root and install recovery.
-- Simple mostly automated batch script.
-- Driver install guide too!
-- Reboot bug included!
-- Platypus
[/CENTER]
Tl;DR: This installs recovery and walks you through rooting your device from total stock. It includes everything you need, download is above.
It also functions as a unbrick for soft-bricks where you can access ADB or if your recovery is bootlooping and won't flash anything.
If you already have root: This tool will work on an already rooted tf to install Rouge's latest Touch Recovery (Reads from internal and external)
--if you're in a bootloop and can boot into android via-cold-boot, this will fix it! --
So if anyone who's already rooted doesn't mind doing further testing on it that would be great, the more reports the better!
If the superuser.zip isn't giving you root (For whatever reason ) try flashing the attached SuperSU I packed.
Video:
How to use PERI to root your Transformer!
**coming soon**
Unbricking/fix recovery bootloop:
I added an unbricking help/feature in V0.4 that'll help with bootloops or softbricks. PERI will help you through it.
**If you want to use the 'I'm already rooted just flash recovery' feature, you need to have given adb su access already!!!**
I bricked my tab on purpose using ROM manager to test the unbricker. Seems to work fine, let me know.
It might have bugs though and not work, in which case 'Don't taze me bro!'
I pretty much copy-pasted roach's bootloop fix.
--
If I helped, click thanks!
Thing O Doom isn't responsible for bricks, dead cats, or thermonuclear war. (Although I will help you with the first two. Seek a bomb shelter if you experience the third problem.)
The .bat is open-source, download the .zip and take a look at the .bat with notepad++, if you like.
If you're having driver issues, give USBdeview a looksee.​

What does it do, exactly ? You are downgrading and then rooting with it ?

No, it doesn't need to downgrade, it just runs wolf's exploit and directly flashes recovery on your tf. All user data is safe.
If it was a downgrade, the filesize would be alot bigger as I'd have to include a stock ROM.

tried it on my transformer with the latest .24 update but it could not flash the recovery at first time, got error ..... lemme check again
Edit: got error --- "cannot stat 'recoveryblob': No such file or directory" ---
I am sure that I am using the same transformer as yours as mine was imported from USA.

About Guide
Hi all,
I think ıt should be a more detailed guide.
"Just unzip it to a folder anywhere and run the .bat file!" it seems very easy.
I do not want to offend the developers and Thing O Doom
tigerfire25;
you can try that move the blob file internal memory of asus and try again. I an now at work so I can not try the method. I am just suggesting you, do not hope too much

I tried to make with simplicity in mind, so that really is all you need to do:
1. Make folder and extract contents of .zip into it.
2. Run the .bat file, which then holds your hand through the whole process.
3. ???
4. Profit.
EDIT5: Tigerfire, please try with a MicroSD inserted. This may fix it, thanks for reporting back.

Done
Done on my TF101G B90 with .24, it worked but:
1) when it tries to reboot the device (twice during the procedure) it doesn't work, i had to do it manually
2) the installation of the Superuser gives an error like it didn't succed but after reboot it was installed
Anyway thanks

Yeah, the reboot to recovery scripts don't work, it's actually just a simple 'adb reboot' command. I couldn't get 'adb reboot recovery' to work, sorry about that, that's why I detailed the manual instructions in there.
The superuser zip might be borked, but 'fix permissions' in CWM usually removes the error, but if it installed I figure whats it matter? XD

worked for me o/
I now have revolution HD Rom on my .24 TF101
thanks for your help ^^

Hi Thing O Doom,
Nice work and thanks
Thing O Doom said:
I tried to make with simplicity in mind
Click to expand...
Click to collapse
You might be able to automate the process a little better by running the PnP Utility ('PnPutil.exe').
e.g.
Code:
pnputil -i -a %~dp0\adb-drivers\android_winusb.inf
-a - add package
-i - install package
You can skip the install command (-i) if you like (drivers will now be in the 'driver store' (-a) and installed when device is connected).
PnPUtil - TechNet
Thing O Doom said:
The superuser zip might be borked, but 'fix permissions' in CWM usually removes the error, but if it installed I figure whats it matter? XD
Click to expand...
Click to collapse
You might want to try/use the su pkg from HERE
http://goo.im/superuser/Superuser-3.0.7-efghi-signed.zip
It uses a newer 'update-binary' and cleaner/updated 'updater-script' & pkg.
-JR-

Thanks for the pointers, I'll be uploading V0.2 a bit later to fix some of those bugs and automate the process a bit better.

Added V0.2 and Changelog in OP.
Thanks jazzruby for pointers!

@ Thing of Doom
Quarkko,
1. You use the same recoveryblob (Tf101 and Tf101G are very similar, so 3rd method works on both.)
2. You don't need to do anything, as you won't get OTA updates anymore if you install CWM. You can manually flash rooted updates in CWM later if you want to update.
3. Following to the letter, almost 0. You'd have to unplug your tf DURING the flashing of the recoveryblob. (The dd if command)
4. You still can't use NvFlash, since you have a Tf101G, sorry it hasn't been cracked yet.
Clear guide- Use my PERI: one click root and recovery installer (in my sig), it walks you through it and runs the commands for you. Works on the tf101G
Click to expand...
Click to collapse
Thanks for the reply.
I tried your PERI method! But unfortunately I use XP for these jobs. Should I wait for the xp drivers. Thanks anyway.

You can still use PERI with xp, just not the Autoinstall of drivers portion of it. Hit no when it asks to install drivers, then when it gets to the section that asks if a device shows up, hit no and then it will redirect you to a manual install of the ADB drivers.
All it needs are ADB drivers, which are easy enough to install.

TF101/G ONLY! anything else is untested.
does it mean onnly the g version or only the tf101?
kind regards
gandalf

I'll clarify that in the op. It works with both the tf101 and the tf101G, the slider is untested.

Worked for me.
Asus Transformer TF101 | ICS 4.0.3 | Compilation IML74K.WW_epad-9.2.1.24-20120503
Thank You!

xxanthor said:
Done on my TF101G B90 with .24, it worked but:
1) when it tries to reboot the device (twice during the procedure) it doesn't work, i had to do it manually
2) the installation of the Superuser gives an error like it didn't succed but after reboot it was installed
Anyway thanks
Click to expand...
Click to collapse
I have a TF101 serial number starting with 0 and US version. I also have to face with reboot problem twice.
Command Screen say that;
Reboot: Operation not permitted. (both Revovery and Flashing screens)
I used a laptop with operating windows 7 32 bit. After reboot problem, this time I try to exectue the batch file as an administrator but, the laptop can not see the device.
Finally, I reboot my device twice manually. Then, I waited for the final reboot. The final reboot completed. There is no Superuser apk. I get into the recovery menu and I installed by manually.

Thing O Doom said:
I'll clarify that in the op. It works with both the tf101 and the tf101G, the slider is untested.
Click to expand...
Click to collapse
-thanks.. it did it,but no root.-and the recovery- if i trie to go to recovery after pressing vol up i only see the android layinf with a red triangel and exclamation mark.
May i try once more?
Kind regards and sorry for my englisch
By the way :funny comments

Try V0.2, it fixes reboot problems mostly. If it can't see it, then drivers need to be re/installed. Is USB debugging enabled?
So did you manage to get Rouge recovery on there and root?