Related
Hey i'm trying to root my Rogers Dream via this method...
http://wiki.cyanogenmod.com/index.php?title=Rogers_Dream:_Rooting_(Post-911_Patch)
My problem is after completing the whole process I am still not rooted.
I think that nothing happens when i do this part...
chmod 666 /dev/mtd/mtd1
flash_image recovery /data/local/recovery.img
are there suppost to be messages after I type those in?
Basically after the whole process i can't get into recovery, and i do not have su permissions.
Thanks for any insight!
For your link, it says: "There is no text on this page".
Anyways, download RC7 (not RC29), sign in, download telnet from market, then when you have recovery.img on sdcard type in:
su
flash_image recovery /sdcard/recovery.img
and you should be rooted.
OR
follow these directions: http://theunlockr.com/2010/04/26/how-to-root-the-htc-g1dream/
OR download oneclickroot and root it that way to access "su" and flash recovery
Thanks I'll give those a try anyways heres the fixed link
http://wiki.cyanogenmod.com/index.php?title=Rogers_Dream:_Rooting_(Post-911_Patch)
e334 said:
For your link, it says: "There is no text on this page".
Anyways, download RC7 (not RC29), sign in, download telnet from market, then when you have recovery.img on sdcard type in:
su
flash_image recovery /sdcard/recovery.img
and you should be rooted.
OR
follow these directions: http://theunlockr.com/2010/04/26/how-to-root-the-htc-g1dream/
OR download oneclickroot and root it that way to access "su" and flash recovery
Click to expand...
Click to collapse
Ok the unlockr method does not work for me.
The HTC Dream is not on the compatible list for oneclickroot can anyone confirm it working?
Where can I find RC7?
have you tryed this app
http://forum.xda-developers.com/showthread.php?t=747598
just install it with a file manager and run it and you should be rooted after that download rom manager from market and install a custom recovery from there
^__^
I finally managed to get the custom recovery flashed! thanks to the xda guide
http://forum.xda-developers.com/wiki/index.php?title=Rooting_HTC_Branded_EBI1_Dreams
If I managed to flash the recovery, does that mean i have root?
Can someone please explain how to do this part? I just get an error...
run the following two fastboot commands (this will prevent issues flashing your rom)
fastboot erase system -w
fastboot erase boot
Click to expand...
Click to collapse
Will anything happen if I do not do this step?
EDIT: Seems I have root now after the app root, flashed cyanogen waiting for it to boot.
aw man you just destroyed my will live.
I was reading this entire post with intense anticipation and was thoroughly let down when I did not see you post a successful root
Any updates on this?
I just purchased a Rogers Dream to learn about rooting and to play with.
If you did have success with this tutorial could you let me know? http://forum.xda-developers.com/wiki/index.php?title=Rooting_HTC_Branded_EBI1_Dreams
I was considering following this tutorial myself!
Cheers
@bourne-nolonger
I used that method a little while ago with no issues.
The steps are easy to follow and work without issue.
Yes i was successful with XDAs procedure
My will was almost destroyed... i traded my magic for this dream... but now im happy
awsome!
thanks for the feedback guys.
definitely looking forward to finally getting a chance to root my G1.
Will report my results!
Cheers
quick question.
in the wiki under "D - Installing an engineering SPL" step 11 says to
Code:
"powerdown - fastboot oem powerdown"
I was wondering what exactly is meant by this?
I looked at fastboot.exe but none of the command line options seem to have a "powerdown" option. They do however have a reboot/reboot-bootloader, is this what step 11 is referring to?
Sorry I should also ask: Can I follow the wiki that describes how to flash CM5+ to flash CM6.1.0? Is the process the same basically between the two versions of CM?
I want to try 6.1.0 instead of going with 5+
Cheers
bourne-nolonger said:
I was wondering what exactly is meant by this?
I looked at fastboot.exe but none of the command line options seem to have a "powerdown" option. They do however have a reboot/reboot-bootloader, is this what step 11 is referring to?
Click to expand...
Click to collapse
That is because its the oem command and the second option (powerdown) is up to the phone to parse..
Once you run 'fastboot erase system -w' and return to recovery you can install any rom you wish just make sure you have an ebi1 kernel.
You also may wish to check out the 2708+ compatible kernel thread to get some extra ram, warning however if you are a rogers customer you will need to sign the e911 wavier before you can switch to any other radio otherwise they will cut your data service.. if you are with another carrier there is no such requirement.
Thanks for explaining step 11. Not sure I fully understand, but I'll do some additional reading.
I was looking at some of your threads before. I thought the 15mb ram expansion wasn't available for the rogers dream?
This is my first time flashing, could I flash cm first then maybe try yours later?
The g1i have luckily isn't my main phone. I bought it just to get comfortable with rooting and flashing.
Cheers
Sent from my Nexus One using Tapatalk
I managed to successfully root and flash CM6 onto my G1.
I see why people were complaining about performance issues.
Its a little sluggish, but usable (mind you are I am not using this as my daily phone)
thanks to XDA for a beginners guide to rooting this phone!
sorry bout this guys but im just curious.. i thought rc7 was for europe only... i honestly am confused now lol i know for me its rc29 im in america and you are in canada is the device really that different even though its such a short distance..? i apologize if its a stupid question...
Guys,
Whats easiest way to root and install clockworkmod for custom roms?
Any other suggestions, welcomed to prevent bricks
[email protected]
Use the nvflash method its one step and will install clockwork recovery as well as a rom of your choice
Sent from my Transformer TF101 using XDA Premium App
extremely easy, takes like 5 minutes.
Hi!
Any one click root options with the NVFLASH? Any links to this app?
1) Would z4root work?
2) Any zip i can simply load and update using the recovery mode of Asus to install clockworkmod?
Thanks!
rommark said:
Hi!
Any one click root options with the NVFLASH? Any links to this app?
Thanks!
Click to expand...
Click to collapse
NVFlash is one click from the start.
http://forum.xda-developers.com/showthread.php?t=1123429
Just download a .tar.bz2 (some are outdated) then download a ROM and flash it on top. Depending what you flash, you might want to wipe.
Hey,
- Whats to do with .tar.bz2 ?
- How do I flash the NVFLASH?
- If I dont want WIPE? I just want root the stock ROM and put kernel which supports OC without wipe it? Since it comes with custom language packs and support for locals.
Thanks!
rommark said:
Hey,
- Whats to do with .tar.bz2 ?
- How do I flash the NVFLASH?
- If I dont want WIPE? I just want root the stock ROM and put kernel which supports OC without wipe it? Since it comes with custom language packs and support for locals.
Thanks!
Click to expand...
Click to collapse
.tar.bz2: use winrar to extract it. Cut all the files and paste it into the root of /nvflash/ (you do this to make NVFlash flash it)
-Watch the video on the NVFlash thread that I linked.
-If you want to use the stock ROM. Then you have to find that thread that lets you root. You could also use NVFlash and then flash the rooted version of the stock.
If you could click the "thanks" button it'll be most appreciated! thanks
Using the search function would be VERY helpfull.
zephiK said:
.tar.bz2: use winrar to extract it. Cut all the files and paste it into the root of /nvflash/ (you do this to make NVFlash flash it)
-Watch the video on the NVFlash thread that I linked.
-If you want to use the stock ROM. Then you have to find that thread that lets you root. You could also use NVFlash and then flash the rooted version of the stock.
If you could click the "thanks" button it'll be most appreciated! thanks
Click to expand...
Click to collapse
Hey,
1) Thanks done x 3
2) so if i extract the NVFLASH it will root and install clockworkmod?
>> Is it the guide? http://androidroot.mobi/2011/06/13/nvflash-on-asus-transformer/ simply looks pretty long for one click hehe
2) Would it remove my stock rom? I only want root and install CWM without remove my stock rom or settings.
3) Would Z4ROOT work?
Thanks!
triumph_st said:
Using the search function would be VERY helpfull.
Click to expand...
Click to collapse
Posting leaving something positive would be VERY helpful too
--
2. Yes NVFlash will flash a ROM of your choice. You will have to download the .tar.bz2 of the ROM you want (note these are VERY limited and you don't have much choice. So what you might have to do is download a .tar.bz2 of any ROM, then go into Clockwork and just flash another ROM [same old way with flashable zips]).
NVFlash will: Root, Install Clockwork. And yes that is it. It's not long, its one click.
Pretty much: download a .tar.bz2.
extract it, cut it into the root of /nvflash/
install NVIDIA drivers in /nvflash/
double click!
done.
2) Yes it would remove your stock ROM. If thats the case then you need to use another method that I'm not familiar with. NVFlash is the easiest way.
If there's a stock 8.4.4.11 with root, you could use that after flashing. But you won't get OTAs most likely. But people often put the OTAs in a flashable zip so OTAs are useless.
3. Don't know what Z4Root is.
I got my transformer a few days ago and let it upgrade over the air to 8.4.4.11
I then read this thread (http://forum.xda-developers.com/showthread.php?t=1125714) and decide to root it. It';s a few steps but thats because it is written out in absolute detail.
It just roots that particular firmware, and installs CWM. It took less than 10 minutes.
zephiK said:
Posting leaving something positive would be VERY helpful too
--
2. Yes NVFlash will flash a ROM of your choice. You will have to download the .tar.bz2 of the ROM you want (note these are VERY limited and you don't have much choice. So what you might have to do is download a .tar.bz2 of any ROM, then go into Clockwork and just flash another ROM [same old way with flashable zips]).
NVFlash will: Root, Install Clockwork. And yes that is it. It's not long, its one click.
Pretty much: download a .tar.bz2.
extract it, cut it into the root of /nvflash/
install NVIDIA drivers in /nvflash/
double click!
done.
2) Yes it would remove your stock ROM. If thats the case then you need to use another method that I'm not familiar with. NVFlash is the easiest way.
If there's a stock 8.4.4.11 with root, you could use that after flashing. But you won't get OTAs most likely. But people often put the OTAs in a flashable zip so OTAs are useless.
3. Don't know what Z4Root is.
Click to expand...
Click to collapse
looks good!
So basically:
1) You got any suggested .tar.bz2. link to download directly?
2) I simply connecting the ASUS to my windows laptop and finding nvflash folder there, extracting the .tar.bz2. into this folder?
3) I click the bat file from windows.
4) I've some custom rom with clockworkmod working. now I can load any rom i want with clockworkmod.
-- right?
-- I can using NVFLASH backup my stock rom?
[email protected]
rommark said:
looks good!
So basically:
1) You got any suggested .tar.bz2. link to download directly?
2) I simply connecting the ASUS to my windows laptop and finding nvflash folder there, extracting the .tar.bz2. into this folder?
3) I click the bat file from windows.
4) I've some custom rom with clockworkmod working. now I can load any rom i want with clockworkmod.
-- right?
-- I can using NVFLASH backup my stock rom?
[email protected]
Click to expand...
Click to collapse
No NVFlash doesn't backup anything. Read what kibje said, that might be what you're looking for if you want to remain stock
1. Yes
2. No, you have to put the Transformer in APX mode (read the guide again)
3. In this mode, Windows will try and find a driver for it. Manually set it to /nvflash/ whatever it says in the guide.
3. Double click guide
4. Yup
So before I updated to 2.3.4, I used gingerbread to root. Updated to 2.3.4 and lost root.....hence lost wifi teathering. Can't seem to find what to use to root now and I need wifi teathering wifi ASAP...no internet at location...only via ATRIX....need laptop on internet. Any help would be great!
leftshark said:
So before I updated to 2.3.4, I used gingerbread to root. Updated to 2.3.4 and lost root.....hence lost wifi teathering. Can't seem to find what to use to root now and I need wifi teathering wifi ASAP...no internet at location...only via ATRIX....need laptop on internet. Any help would be great!
Click to expand...
Click to collapse
Look around, do a search. If I were to help you, I would simply do a search and then tell you what I found. Why can't you just do that? You don't need people to search for you...
leftshark said:
So before I updated to 2.3.4, I used gingerbread to root. Updated to 2.3.4 and lost root.....hence lost wifi teathering. Can't seem to find what to use to root now and I need wifi teathering wifi ASAP...no internet at location...only via ATRIX....need laptop on internet. Any help would be great!
Click to expand...
Click to collapse
Look at the second post on how to root...
http://forum.xda-developers.com/showthread.php?t=1138204
2nd post......even though im in the states and locked to AT&T? Tried to download that zip via my ATRIX and the download fails.... :sigh:
try to force close your browser app, and then redownload.
it's 8MB, you shouldn't have any problem. make sure you're downloading preinstall.zip from the second post in that thread, and not the sbf from the first post.
then follow the instructions in the second post. eval-'s method is extremely easy and works on every atrix.
leftshark said:
2nd post......even though im in the states and locked to AT&T? Tried to download that zip via my ATRIX and the download fails.... :sigh:
Click to expand...
Click to collapse
That shouldnt matter at all. I mean it clearly says For AT&T users right at the top of the first post before it gives the root info.
Check out RootzWiki. They have information there as well on how to root the Atrix after the Gingerbread update.
Thanks guys. But I think the problem at hand is not being able to dl that zip. About 2seconds after I start the dl...it fails. How to force close?
open up task manager, and close out the browser app. i have to do this sometimes when my downloads aren't working correctly
Some Help
Isn´t that easy to search from phone, so I would try to unlock bootloader, install tenfar CWM Recovery and then flash su and Superuser. To do that:
1.- Unlock: http://briefmobile.com/how-to-unlock-the-atrix-4g-bootloader
2.- CWM Recovery: http://forum.xda-developers.com/showthread.php?t=1138541
3.- Flash SU: http://forum.xda-developers.com/showthread.php?t=1140110
More info here: http://forum.xda-developers.com/showthread.php?t=1154600
I found the easiest root instructions ever. This guy scripted to whole process. Mad kudos to him!
http://forum.xda-developers.com/showthread.php?t=1182871
lhurtado said:
Isn´t that easy to search from phone, so I would try to unlock bootloader, install tenfar CWM Recovery and then flash su and Superuser. To do that:
1.- Unlock: http://briefmobile.com/how-to-unlock-the-atrix-4g-bootloader
2.- CWM Recovery: http://forum.xda-developers.com/showthread.php?t=1138541
3.- Flash SU: http://forum.xda-developers.com/showthread.php?t=1140110
More info here: http://forum.xda-developers.com/showthread.php?t=1154600
Click to expand...
Click to collapse
Why are you trying to tell this guy to unlock the bootloader, he simply wants to root the phone?
I found the easiest root instructions ever. This guy scripted to whole process. Mad kudos to him!
http://forum.xda-developers.com/show....php?t=1182871
Click to expand...
Click to collapse
This also seems to unlock as well, not everyone cares to unlock their phone ya know.
To the OP, try downloading the Dolphon browser, I've found it to be helpful at times when the other browser doesn't want to play nice.
Finally I was able to dl the reinstall.img via opera (dolphin failed too). Ran the fastboot reinstall preinatall.img, it worked, then fastboot reboot. Ran root checker....no root. Downloaded Superuser..."force close"....:sigh:. What am I missing here to root this damn thing? It wasn't as much of a pain to root in the last......much thanks!!
leftshark said:
Finally I was able to dl the reinstall.img via opera (dolphin failed too). Ran the fastboot reinstall preinatall.img, it worked, then fastboot reboot. Ran root checker....no root. Downloaded Superuser..."force close"....:sigh:. What am I missing here to root this damn thing? It wasn't as much of a pain to root in the last......much thanks!!
Click to expand...
Click to collapse
Did you follow the last part of the instructions?
after fastboot & reboot, type in adb ("adb shell") or terminal emulator, exactly:
/preinstall/dosu
/bin/mount -o remount,rw /system
cp /preinstall/su /system/bin/
chmod 6755 /system/bin/su
PATH=/system/bin:$PATH pm install /preinstall/Superuser.apk
Adb shell
$ /preinstall/dosu
I get : bash: groups: command not found
[email protected]:/#
Need to be out in fastmode to do the above maybe?
Nope, device not found. I did have to goto c: to Adb shell.....hrmmmm
Any suggestions before I add on a teathering plan?
i got the same command not found, i just went along with the rest of the process like normal and it rooted for me.
try that, if that doesn't work try /preinstall/su instead of /dosu
Alcapone263 said:
i got the same command not found, i just went along with the rest of the process like normal and it rooted for me.
try that, if that doesn't work try /preinstall/su instead of /dosu
Click to expand...
Click to collapse
+1
10char
C:\ Adb shell
$ /preinstall/su
Permission denied
For those of you wondering why the S-OFF feature was worth your extra time to update, this is a prime example of why S-OFF kicks royal behind.
So here is the situation I was having. Friday morning, T-Mo showed me some love and sent me the Gingerbread update. I didn't have my morning coffee so I wasn't thinking strait and authorized the update. I forgot that it would probably interfere with good ol' ClockworkMod Recovery. Sure enough, it did. So, after the OTA failed due to the recovery, I haven't been able to get T-Mo to show me some OTA love again.
However, I had previously invoked the S-OFF feature when it was discovered how to.
After following the guide at http://forum.xda-developers.com/showthread.php?t=1202060 I found myself with a G2 using stock recovery and bone stock Gingerbread (S-OFF still invoked).
After some thought, I decided to do the following:
Flash ClockworkMod via the bootloader screen, and flash SU via the ClockworkMod screen.
Note: You can only do this if you have S-OFF! And since my guide writing skills are not so pristine, I'm assuming you have some sort of working adb/bootloader/recovery knowledge.
Save the attached files (PC10IMG.zip & su.zip) to your sdcard. Reboot into the bootloader either by using the adb command adb reboot bootloader or by powering off, and then holding Vol-Down+Power.
The bootloader will scan for PC10IMG.zip and then ask you if you want to flash the recovery. Yes! You do!
After this, reboot the phone. Reboot into recovery by using the adb command adb reboot recovery, or booting back into the bootloader and navigating to the Recovery console (if you didn't delete the PC10IMG.zip, bootloader will scan it, but don't let it update again, this is redundant).
Once you are in ClockworkMod, navigate to "install zip from sdcard", then to "choose zip from zip card". Select the su.zip file from the list, and authorize the recovery console to flash the zip. Reboot the phone.
Now, you will see the coveted SuperUser app in your drawer. I figured this was wayyyy to easy to have worked, so I tested some root dependent apps, they work flawlessly. I also used the adb command adb shell followed by su once in the shell. SuperUser requested my permission and after granting it, I am able to remove the bloatware that was replaced during the downgrade, also, rebooting the phone as normal and from a removed battery does not remove this root. So I'll say it's a permaroot.
I compiled the attached files specifically for this. The ClockworkMod Recovery version is 3.0.2.4, SuperUser version is 2.3.6.1.
Thanks!
It sounds like you started where I am: Clockwork Mod, S-OFF and stock Froyo 2.2.
Q. How did you follow the steps in the thread to get onto Gingerbread? Did you remove ClockworkMod? If yes, how did you revert to stock recovery? This is the step that I'm caught on, and can't find a thread regarding. Thanks!
Edit to add:
Did you unroot the phone using these steps?
If so, were you at all scared about the warning regarding PC10IMG.zip?
I ended up using the entire stock 2.2 PC10IMG which wiped clockwork off the phone to stock recovery. I didn't do anything to unroot, since the stock rom replaced recovery, system etc but left s-offf in tact.
ETA: I also didn't read either of those articles and wasn't aware of the bricking issue, I've done the phone flashing, modding and unbricking for about 2 years now and just used experience as a guide..
Sent from my T-Mobile G2 using Tapatalk
rdmerck said:
I ended up using the entire stock 2.2 PC10IMG which wiped clockwork off the phone to stock recovery. I didn't do anything to unroot, since the stock rom replaced recovery, system etc but left s-offf in tact.
ETA: I also didn't read either of those articles and wasn't aware of the bricking issue, I've done the phone flashing, modding and unbricking for about 2 years now and just used experience as a guide..
Sent from my T-Mobile G2 using Tapatalk
Click to expand...
Click to collapse
Okay, so just to verify, you flashed CWM recovery while running the GB update? When you adb shell you open a # prompt? I've been gfree s-off'd since I got my phone so even with the leak or otherwise I've been able to just reflash the stock 1.19/1.22OTA and reroot it but I didn't think to try flashing cwm while it's stock gb'd....so tempted.
I compiled the attached files specifically for this. The ClockworkMod Recovery version is 3.0.2.4, SuperUser version is 2.3.6.1.
Click to expand...
Click to collapse
So I sit down to write up a quick guide this morning and what do I find? Nicely done. Couple of points I wanted to add to why this works -
This method fixes the things that the OTA breaks for root: New stock hboot and stock recovery are flashed and on the rom side it wipes /system/xbin which breaks the su symlink.
Flashing the PC10IMG above fixes the recovery.
Flashing the superuser package reinstalls Superuser.apk, the su binary and fixes the symlink to xbin.
But, still not hboot-eng so your fastboot options are limited.
When I did this I had replaced the DZ engineering hboot.img in rmk's package with the G2 engineering hboot.img and edited android.txt for the new G2 build. This allows you to take care of both in once flash.
Hope this is useful to someone and thank you for saving me from writing a guide!
8/27/2011 Edit:
Realized ro.secure=0 so I repacked the stock boot.img from the 2.3.4 PC10IMG.zip with the below changes to default.prop. This allows use of the "adb remount" so files can be pushed to system folders without needing to go into terminal and mounting rw.
Code:
#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.service.adb.enable=1
Modified installation instructions for full root:
Flash the PC10IMG.zip with the G2 engineering bootloader in this post
Flash the superuser update.zip in the OP
Extract the attached boot.img to the platform-tools directory
Remove the PC10IMG from your sdcard and reboot into bootloader
Select fastboot
Enter the following command in terminal or cmd:
Code:
fastboot flash boot boot.img
fastboot reboot
Kind Regards,
Kevin
zkid2010 said:
Okay, so just to verify, you flashed CWM recovery while running the GB update?
Click to expand...
Click to collapse
Yes. Just flash the PC10IMG and you have clockwork recovery again. However, you absolutely need SuperCID set while in froyo or this does not work.
Kind Regards,
Kevin
Confirm Here that it works...
Root and S-OFF
Gingerbread OTA 2.3.4
Thanks Guys for your help!
Flawless!
This worked flawlessly!!
I admire you so much for figuring this out!!
Thank you so much!
HELP!
sort of noobie here..
so i just updated my g2 to 2.3.4 following http://forum.xda-developers.com/showthread.php?t=1202060
and now i want to perm root my phone and overclock it but im having troubles.
1. how do i get clockworkmod installed? i know you can install this from rom manager but it requires root. right?
cause you said.. "Just flash the PC10IMG and you have clockwork recovery again"..
i tried flashing the PC10IMG.zip but got an error and says aborted.
any help please?
thanks in advance
If you are already on 2.3.4 and had not previously rooted then this thread will be of no use to you since your G2 does not have SuperCID (again, read the wiki.)
You will need to downgrade back to froyo (other threads on this and links in the wiki.) Once rooted, then install one of the rooted stock roms in this forum or follow this guide to reinstall the recovery and superuser (hboot optional.)
Hope that gets you going in the right direction.
Kind Regards,
Kevin
Sent from my T-Mobile G2 using Tapatalk
G2 Problems??
Hi, how can i get S-OFF on my g2 since it seems i can not generate a beta key from the revolutionary website cause g2 it's not in the drop down list, don't know what to pick and i want to be able to have my g2 rooted with android 2.3.. can somebody help me please?
Thanks.
Revolutionary is not available for the Desire Z/G2. Have you flashed the leaked 2.3.3 and trying to root? PM please.
Hey I notice most of the people in this thread are Americans - would this method work for the DZ or is it just for the G2?
Sorry if this is a noobish question.
Not a noob question, this one is new for me too. Fundementals are the same, process would be the same. I don't know if there is any issue using a PC10IMG with the info for a G2 (contained in the file called android-info) so may need rebuild one modified with DZ information.
Proceed with caution and do not do anything you are not 100% sure about.
Sent from my T-Mobile G2 using Tapatalk
I'll hold off on confirming the update in that case! I'm still on stock firmware, didn't apply the update from March either. When I've read enough to be confident on how to perma-root the current firmware I might risk following the method in this thread. Then I'll post back to let you know if it works on the DZ.
My DZ came with 1.34 firmware, I rooted it on this firmware. I accidentally upgraded it and am now on the OTA gingerbread ROM. Is this method suitable in this situation or do I require to flash a rooted stock ROM for this method to work.
Accidentally manually applied the OTA? Should work, you have a G2 now!
Sent from my HTC ThunderBolt using Tapatalk
Is there any newbie guide for how to do this? From getting Clockwork on there to getting this rooted 2.3.4 on. I have a rooted 2.2 with S-OFF right now, stock. Just don't really know what to do from this point on.
How to is in the OTA thread (which needs a helping of Iron Fist.) Come back here when ready to re-root.
Sent from my T-Mobile G2 using Tapatalk
rdmerck said:
Save the attached files (PC10IMG.zip & su.zip) to your sdcard. Reboot into the bootloader either by using the adb command adb reboot bootloader or by powering off, and then holding Vol-Down+Power.
The bootloader will scan for PC10IMG.zip and then ask you if you want to flash the recovery. Yes! You do!
After this, reboot the phone. Reboot into recovery by using the adb command adb reboot recovery, or booting back into the bootloader and navigating to the Recovery console (if you didn't delete the PC10IMG.zip, bootloader will scan it, but don't let it update again, this is redundant).
Once you are in ClockworkMod, navigate to "install zip from sdcard", then to "choose zip from zip card". Select the su.zip file from the list, and authorize the recovery console to flash the zip. Reboot the phone.
Now, you will see the coveted SuperUser app in your drawer. I figured this was wayyyy to easy to have worked, so I tested some root dependent apps, they work flawlessly. I also used the adb command adb shell followed by su once in the shell. SuperUser requested my permission and after granting it, I am able to remove the bloatware that was replaced during the downgrade, also, rebooting the phone as normal and from a removed battery does not remove this root. So I'll say it's a permaroot.
I compiled the attached files specifically for this. The ClockworkMod Recovery version is 3.0.2.4, SuperUser version is 2.3.6.1.
Click to expand...
Click to collapse
**** Im at the step above finally lol this is my first root and I had to downgrade, man Ive been doing this for hours and hours. My brain is fried LMAO **** I currently have my G2 with S-OFF and a stock Gingerbread 2.3.4. I have the PC10IMG.zip and su.zip in the root or directly in my sdcard. In no folders im trying to say... I reboot into the bootloader. The bootloader will scan for PC10IMG.zip and then ask you if you want to flash the recovery. Yes! You do!
Well when I do it it doesnt ask me to "flash the recovery" it says "Parsing....(SD ZIP)
(1) RECOVERY
Do you want to start the update?
<VOL UP> YES
<VOL DOWN> NO
I accept the update by pressing vol. up. It comes back and says Update comeplete... - OK
Press Power to Reboot
I reboot and get into clockworkmod it says click "install zip from sdcard" I click it and a little hat appears but it doesnt do anything from there. I let it set a couple of min but still nothing... I have to pull battery out to get it to reboot. help pls....
Sean...
I was able to root the latest update 9.2.1.21 without downgrading I used wolfs method 3 http://forum.xda-developers.com/showthread.php?t=1622628 to install cwm using cwm recoveryblob then i downloaded wolf su+superuser.apk from the OP and flashed it on using cwm now ihave a rooted 9.2.1.21 without downgrading
NB i used a different recoveryblob than what wolf posted i used the one that usually get place on sdcard when i had installed cwm using gnufabio recoveryinstaller.apk on previous firmware but u could use the one in wolf post it cwm based
what are the commands to enter adb, I have installed the sdk manager and update the usb tablet, but I can not, please help
Sent from my Transformer TF101 using xda premium
max_105 said:
what are the commands to enter adb, I have installed the sdk manager and update the usb tablet, but I can not, please help
Sent from my Transformer TF101 using xda premium
Click to expand...
Click to collapse
In sdk manager select android platform tools and asus drivers and install them once thats done open command prompt and go to the directory containing adb for me it was c:/android-sdk/platform-tools
Ensure debbuging mode and asus sync are turned on on your tf101 plug it up and the run the command
adb devices
this will tell if adb sees your device. If it does then run the command
adb shell
then just follow rest of instructions under method 3 in wolf post http://forum.xda-developers.com/showthread.php?t=1622628
jays473 said:
I was able to root the latest update 9.2.1.21 without downgrading I used wolfs method 3 http://forum.xda-developers.com/showthread.php?t=1622628 to install cwm using cwm recoveryblob then i downloaded wolf su+superuser.apk from the OP and flashed it on using cwm now ihave a rooted 9.2.1.21 without downgrading
NB i used a different recoveryblob than what wolf posted i used the one that usually get place on sdcard when i had installed cwm using gnufabio recoveryinstaller.apk on previous firmware but u could use the one in wolf post it cwm based
Click to expand...
Click to collapse
I just tried this after installing the new 9.2.1.24 (downloaded from Asus), and it seems to work. I followed Wolf's method 3 without any modifications. I have a TF101, US model.
nikolam said:
I just tried this after installing the new 9.2.1.24 (downloaded from Asus), and it seems to work. I followed Wolf's method 3 without any modifications. I have a TF101, US model.
Click to expand...
Click to collapse
What BLOB file did you use
well yes, through CWM one can install su-binary then.
but through CWM you will loose OTA-updates!
just look at the time between .21 and now .24... it is quite comfortable as it is.
why can't we use such a "file linking trick" to mount /system and install su-bin directly?
You can't write to /system as it's mounted read only.
What you can do is keep a copy of mmcblk0p4 before writing the new recovery, then flash it back after rooting. That way you keep your ability to upgrade next time around.
good idea!
I'm still a bit unsure about this RECOVERYBLOB flashing,
but if nothing else comes up I can resort to this.
ty