39 replies to this topic

[Buzing Bee]

Get it here http://kan.gd/frm

[RaYmAn84]

Buzing Bee, on Apr 28 2011, 22:40, said:

Get it here http://kan.gd/frm

Woop, woop!

[Putzy]

If we do this, is there a "way back" to Stock should the need ever arise?

[RaYmAn84]

Putzy, on Apr 28 2011, 23:03, said:

If we do this, is there a "way back" to Stock should the need ever arise?

Yes.
Repeat step 9 to 11, but this time dd the blob found in the EP101_UPDATE.zip from Asus OTA.

[qwer23]

RaYmAn84, on Apr 28 2011, 21:47, said:

Yes.
Repeat step 9 to 11, but this time dd the blob found in the EP101_UPDATE.zip from Asus OTA.

Where do I get the EP101_UPDATE.zip from original Asus OTA?

[Putzy]

RaYmAn84, on Apr 28 2011, 22:47, said:

Yes.
Repeat step 9 to 11, but this time dd the blob found in the EP101_UPDATE.zip from Asus OTA.

Just searched XDA and can't find anything for quite a few search terms, even though I know I've seen it! Any chance of posting a link?

[qwer23]

RaYmAn84, on Apr 28 2011, 21:47, said:

Yes.
Repeat step 9 to 11, but this time dd the blob found in the EP101_UPDATE.zip from Asus OTA.

At step 9 I get:

dd: can't open '/dev/block/mmcblk0p4': Permission denied

su worked (I get the #) and md5sum is correct.

Any help?

edit: with the help of netarchy over at xda it went fine:

Quote

The guide, as currently written, cannot be followed verbatim, as md5sum and busybox don't exist.

I posted a comment on that blog with my experience/some adjustments for the guide.

Basically you'll need to md5sum locally, so push the blob, then pull the blob to another location on your drive, run md5sum to make sure the size is right (if it's correct from your adb pull, then you know the copy on the device is good).

I believe at the time of this writing, the busybox line in the guide has been corrected (since busybox won't exist), so the only other correction you will need to make is to chmod 755 the su binary, not 666.

Edited by qwer23, 28 April 2011 - 11:21 PM.

[lordgodgeneral]

Is anyone having a problem with the window becoming unreponsive to commands after obtaining SU (#)??

I run the gingerblockBB it runs, displays

[!] dance forever my only one
#

but I can't seem to be able to type the next command

Any ideas?

[qwer23]

lordgodgeneral, on Apr 29 2011, 01:49, said:

Is anyone having a problem with the window becoming unreponsive to commands after obtaining SU (#)??

I run the gingerblockBB it runs, displays

[!] dance forever my only one
#

but I can't seem to be able to type the next command

Any ideas?

why can't you type the next command? just write next to the #.  the # only indicates that you have root rights.

[lordgodgeneral]

qwer23, on Apr 29 2011, 02:21, said:

why can't you type the next command? just write next to the #.  the # only indicates that you have root rights.

That's what I'm trying to figure out.  I've tried to process about 5 times and its the same each time.  I get to the # (su) and after that point, typing in the command window does nothing.

Its like the device becomes non responsive or something.  I'm def open to ideas on what I may be doing wrong.

[qwer23]

lordgodgeneral, on Apr 29 2011, 10:25, said:

That's what I'm trying to figure out.  I've tried to process about 5 times and its the same each time.  I get to the # (su) and after that point, typing in the command window does nothing.

Its like the device becomes non responsive or something.  I'm def open to ideas on what I may be doing wrong.

That's really weird, because you should be able to type in cmd  even if device disconnects. The error message would then appear after you hit enter. But that you cannot type after getting root rights is strange since you don't change anything on you running windows system  
Sorry, can't help you here, I'm too much a noob, too.

[lordgodgeneral]

I did get it to finally work,

did the following
adb shell
waited for $
then ran ./data/local/gingerbreakBB

after running I got the # and was able to finish the rest of the commands and got CWM installed.

Now I'm having another problem

pushed su to /system/bin and did chmod 755 /system/bin/su (also tried chmod 666 /system/bin/su) but device is still showing its not rooted
Titanium Backup and Root Explorer both failing to detect root.

su is showing up in the /system/bin folder and superuser.apk is installed, but I'm stuck

Tried redownloading and repushing su, but still no difference

finally got it to work.  Had to follow the step to get su installed from installing su on honeycomb for nook

needed to add these lines after copying su to /system/bin
ln -s /system/bin/su /system/xbin/su
chmod 06755 /system/bin/su

source  http://forum.xda-dev...p/t-941445.html

Edited by lordgodgeneral, 29 April 2011 - 04:33 PM.

[redmongoose]

Buzing Bee, on Apr 28 2011, 20:40, said:

Get it here http://kan.gd/frm

Great work.

Thank you very much for this, just got my transformer swapped today by comet (slight build imperfection) and the first thing I did was root it fully  

Now where's Paul's custom rom

[Putzy]

RaYmAn84, on Apr 28 2011, 22:47, said:

Yes.
Repeat step 9 to 11, but this time dd the blob found in the EP101_UPDATE.zip from Asus OTA.

Right - found it I think: http://forum.xda-dev...mp;postcount=29

Replacing the blob from this .zip file with the one included in the root, and re-performing the steps will return to stock recovery, with 'secure' boot - all I would have to do then is remove the root files, and format data - and I'd be totally back to stock, getting OTA updates?

I'm only asking because I may end up RMA'ing this unit for light bleed I also know that at some point - someone else with wonder.

[qwer23]

Putzy, on Apr 29 2011, 20:53, said:

Right - found it I think: http://forum.xda-dev...mp;postcount=29

Replacing the blob from this .zip file with the one included in the root, and re-performing the steps will return to stock recovery, with 'secure' boot - all I would have to do then is remove the root files, and format data - and I'd be totally back to stock, getting OTA updates?

I'm only asking because I may end up RMA'ing this unit for light bleed I also know that at some point - someone else with wonder.

Please give me a quick heads-up what files I have to remove to lose root. I'll send it in RMA the next days.

Regards
qwer23

[Putzy]

qwer23, on Apr 29 2011, 22:24, said:

Please give me a quick heads-up what files I have to remove to lose root. I'll send it in RMA the next days.

Regards
qwer23

Presumably gingerbreakBB, su and SuperUser.apk - I don't quite know yet.

[qwer23]

Putzy, on Apr 29 2011, 21:27, said:

Presumably gingerbreakBB, su and SuperUser.apk - I don't quite know yet.

Thx so far!

On really weird question:
Is there a way to push a whole ROM via adb? I know it would be a lot of work, but even if I unroot and secure boot the device again, I'd still have the custom ROM installed. I can't access via recovery or ROM manager and OTA update fails...

[qwer23]

qwer23, on Apr 30 2011, 00:35, said:

Is there a way to push a whole ROM via adb?

anyone?

[iamdarren]

How do we get into cwm with the method.

I followed the steps but I had stock, then used modaco h1 beta. Then reset factory. Then got the dreaded FOTA. X2 Now I have tried this full root method.

Looks like the super user all don't work only I can't install or update. I'm also seeing the market bug.

I was thinking If I can enter cwm I could flash my first nandroid before any updates were ever installed. And I can get flashing some custom roms.

[ghosti32]

Get a access denied after the chmod777 .  Dont work for me