Related
Alright all,
I know there's another thread about "easier" method, but this is easiest for me. 3-Clicks after installation.
I was really tired of typing the same crap over and over after rebooting just to get my temproot back to do more testing/playing.
So I redeveloped this to be quicker/easier upon reboot. Mainly I altered the Term app to be have a scripted start-up on the 1st 3 launches.
I also updated the su/Superuser combo with ChainDD's latest stuff.
Here's how it works, after it's installed.
3ClickTempRooter said:
1) You run the terminal app once, wait a few seconds and it disappears.
2) You run the terminal again, wait for it to FC.
3) You run the terminal a final time and receive root.
Click to expand...
Click to collapse
Now on each reboot, it will be simply 3-clicks (running terminal app 3 times).
Finally ... any executable script placed in /data/local/tmp will be in the path of the new terminal mod. This makes running other scripts very easy.
Installation
Download the attached QuickTempRooter.zip and place it in a directory and unpack it.
Turn on USB debugging and install through adb ...
Here's the adb installation snippet ...
Code:
adb kill-server
adb push su /sdcard/su
adb push Superuser.apk /sdcard/Superuser.apk
adb push busybox /data/local/tmp/busybox
adb push rage /data/local/tmp/rage
adb push root /data/local/tmp/root
adb shell chmod 0755 /data/local/tmp/busybox
adb shell chmod 0755 /data/local/tmp/rage
adb shell chmod 0755 /data/local/tmp/root
adb shell 'pm uninstall com.android.term'
adb install Term.apk
Has made my life wayyy easier when playing with this phone while we wait for the real-deal!!!
Hope you enjoy!
NOTES
If you get a permission denied on the ''adb shell 'pm uninstall com.android.term' '' ... this is normal if you don't have a terminal already installed or have an alternate terminal app (using a namespace other than com.android.term.
If you have another Terminal App installed, you may want to uninstall it first, to avoid confusion.
Also, you may need to reboot after the initial installation for it to work properly!
ummmmm.....Enomther??
Did you get a G2 already?
Great to see you helping out with this
Great to see you here man! Trying this now can't wait to get themes rolling once we get permanent root!
Sent from my T-Mobile G2 using XDA App
I get a permission denied response when running "adb shell 'pm uninstall com.android.term'"
burton14e7 said:
I get a permission denied response when running "adb shell 'pm uninstall com.android.term'"
Click to expand...
Click to collapse
If you didn't already have a terminal app installed that error is normal. Also you may need to reboot once after the initial installation for it to work properly.
~enom~
Thank you sir. Appreciate the goodness.
damn i wish i could hit the thanks button
Thanks man good to have you on the G2 too
Sent from my T-Mobile G2
enomther said:
If you didn't already have a terminal app installed that error is normal. Also you may need to reboot once after the initial installation for it to work properly.
~enom~
Click to expand...
Click to collapse
good to see you on this side.... i have terminal app installed rebooted but still get this denied when running adb shell 'pm uninstall com.android.term
Edit: fixed it uninstalled the Android Terminal E,ulator and just ran the setup now have root thanks
Thank You..
Enom.. (sigh)
Welcome Home..
thank u so much now i can wireless tether. easiest root ever
Sorry, this is my first Android. I came from WM and I was pretty good with it.
I've searched XDA, Youtube, and web to ADB and SDK. I've downloaded it and it's installed. The only thing I don't get is when you said to
"Download the attached QuickTempRooter.zip and place it in a directory and unpack it."
You mean place the extracted files into the sd card correct? That's why the command is "adb push su /sdcard/su".
ddgarcia05 said:
Sorry, this is my first Android. I came from WM and I was pretty good with it.
I've searched XDA, Youtube, and web to ADB and SDK. I've downloaded it and it's installed. The only thing I don't get is when you said to
"Download the attached QuickTempRooter.zip and place it in a directory and unpack it."
You mean place the extracted files into the sd card correct? That's why the command is "adb push su /sdcard/su".
Click to expand...
Click to collapse
No, he means on your PC. You are running adb to push files contained in the zip to your phone.
HamNCheese said:
No, he means on your PC. You are running adb to push files contained in the zip to your phone.
Click to expand...
Click to collapse
So they go into the tools folder? Damn. I think I've in over my head here.
Like this?
If you have better terminal, you can also add the rage and root to specific keys.
At this command I'm getting told "failed to copy 'su' to '/sdcard/su': Read-only file system"
adb push su /sdcard/su
kevdawg said:
At this command I'm getting told "failed to copy 'su' to '/sdcard/su': Read-only file system"
adb push su /sdcard/su
Click to expand...
Click to collapse
Unplug then plug ur phone back in then try again also make sure u are in usb debug mode
Good work, Temp root in like 5 seconds
Quick question, ok I was able to get root for a few mins, then it went away I guess I have to have the terminal always open or ignore so my taskiller doesnt terminated it?
Don't use task killers. (IMHO)
But I tend to have to reboot every once in a while to keep root in tacked within terminal but all my apps seem to stay with su permissions until reboot (or sometimes 12 hours)
I'm trying the rage root method after reading up on all the stuff. I managed to get adb installed and connected, but i can't use adb actions.
I type in c\androidsdk\tools\adb shell
$ su
$ SUermission denied
even without su, if i try to type "adb push su /sdcard/su" it says adb permission denied.
I have kept my phone screen on as per another thread, but i do not get a prompt that asks for adb permissions. Am i missing an app or something? I do have debugging and screen awke both on.
I have placed the g2 root folder in the androidsdk\tools\ folder, both just the files and the entire folder just to be sure.
Obviously I'm new to adb, so If i'm doing something completely wrong just let me know.
as long as you're not rooted (temp or perma) you can't use "su" in adb-commands... If you tell a little more about what you're trying to push, then I can help some more
Im just trying to root the phone with rage since visionary seems unreliable.
Im trying to adb push the su/ sdcard/su as per the first line of instruction in the rage temp root guide
hehe... I used the visionary root, and it have worked good for me btw, I think you should've posted in the rage-thread instead of opening a new topic, but now it's already opened so here it goes
firstly... are you sure you're in the right folder, and have the folder "su" in there?
If so, don't go into "adb shell"... use the lines exactly as stated in the OP. adb inside an adb shell won't give the results you want... Post back if it doesn't work
$ adb push su /sdcard/su
$ adb push Superuser.apk /sdcard/Superuser.apk
$ adb push rage /data/local/tmp/rage
$ adb push busybox /data/local/tmp/busybox
$ adb push root /data/local/tmp/root
$ adb shell chmod 0755 /data/local/tmp/*
Click to expand...
Click to collapse
I don't think Im using adb right then, how do I just type in "adb push ...?" If I do that, it just says that the command is not recognized internally or externally.
For example,
Adb push su/ sdcard/su
gives me that error.
I've tried to set a path directly to adb, but that didn't work, so I was manually going
AndroidSKD\tools\ Adb push su/ sdcard/su but that also didnt work.
I don't have the $ prompt without shell, is that wrong?
I'm pretty sure Im in the right folder, as androidsdk\tools\adb gives me the adb directory, just nothing else works. What exactly does SU folder mean? I have the su file in the tools folder, dont know about the su folder.
Ok, my adb stuff is in c:\tools .. so when I first open command prompt, I have to type this:
cd c:\tools
That puts me into the correct folder. If yours is in C, then you'd probably have to do this:
cd c:\androidsdk\tools
Then type:
adb devices
It should at least give you SOME sort of output, either with your device number (if it's connected, and adb is working properly), or just say devices, with no numbers (incorrectly)
dwang93 said:
I don't think Im using adb right then, how do I just type in "adb push ...?" If I do that, it just says that the command is not recognized internally or externally.
For example,
Adb push su/ sdcard/su
gives me that error.
I've tried to set a path directly to adb, but that didn't work, so I was manually going
AndroidSKD\tools\ Adb push su/ sdcard/su but that also didnt work.
I don't have the $ prompt without shell, is that wrong?
I'm pretty sure Im in the right folder, as androidsdk\tools\adb gives me the adb directory, just nothing else works. What exactly does SU folder mean? I have the su file in the tools folder, dont know about the su folder.
Click to expand...
Click to collapse
You, apparently, need to read some more.
Do it exactly as written here
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2
FYI you will not see the $ symbol. that just indicated the next line you have to enter in commnad prompt. Each time you see $ just mean you type that line then press enter. Wait to see a result of transfer from prompt then enter next line and so on.
rsxtypes72 said:
You, apparently, need to read some more.
Do it exactly as written here
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2
Click to expand...
Click to collapse
This!! I'll be kind though.
Make your life easy. Unzip the contents of g2TempRoot, to your tools folder, in sdk. So, unzip the g2temproot to your desktop. Go into that folder. Copy all, and move them to c:\androidsdk\tools. Now, once that's done, go into command prompt. cd c:\androidsdk\tools. Then, do as follows, as per that link
$ adb push su /sdcard/su
$ adb push Superuser.apk /sdcard/Superuser.apk
$ adb push rage /data/local/tmp/rage
$ adb push busybox /data/local/tmp/busybox
$ adb push root /data/local/tmp/root
$ adb shell chmod 0755 /data/local/tmp/*
(Sorry I couldn't be of more help, as I used VisionaryR12 and it worked fine for me.)
One more word of advise...
I would recommend you try temp root first.
Become used to using adb then try to get full root.
When you use temp root everything you do is temporary only.
Rebooting will reset everything back to stock so its good practice.
thanks for the help guys, but i figured it out. I just wasn't in the right directories from the get go.
Edit: Just finished the perm root! And it didn't brick.
dwang93 said:
thanks for the help guys, but i figured it out. I just wasn't in the right directories from the get go.
any tips on going onto the perm root?
Click to expand...
Click to collapse
Read .. research .. double check .. triple check .. and right before you do it .. check again. As you're doing it, go over every letter, space, and character to make sure it's as it should be.
On the subject of adb, I have it installed, but when I run adb devices to find my phone, I get "???????????? no permissions". What am I doing wrong here?
Daughain said:
On the subject of adb, I have it installed, but when I run adb devices to find my phone, I get "???????????? no permissions". What am I doing wrong here?
Click to expand...
Click to collapse
Upload a screen shot of your command window
with the error
dwang93 said:
thanks for the help guys, but i figured it out. I just wasn't in the right directories from the get go.
Edit: Just finished the perm root! And it didn't brick.
Click to expand...
Click to collapse
dude..I think I am doing something like you...could you please post what you did....I think is an issue of directories..but I'm not that familiar with adb and i have not been able to figure this out.....
Thanks!!!
I am going to root using the [GUIDE][30/06/2011]Root AND Downgrade Desire Z/G2(S-OFF/ClockWorkMod) -No Gingerbread topic to root. I have a question though regarding ADB as i dont want to brick my phone.
when it says :
Now you are ready to begin:
1. Open a CMD prompt window
2. Navigate your way to the folder with psneuter & misc_version IN CMD PROMPT. (So the cmd prompt window should be something like this C:\RootVision> )
3. Now we will use the following 5 commands one after the other
Code:
adb push psneuter /data/local/tmp
adb push misc_version /data/local/tmp
adb shell chmod 777 /data/local/tmp/psneuter
adb shell chmod 777 /data/local/tmp/misc_version
adb shell /data/local/tmp/psneuter
adb shell
do i need to mount the phone or just do this:
Plug phone in
turn on usb debugging
navigate to folder
type in 5 commands or do i need to "register" or "identify" the phone that I want to move the psneuter for example to ? or do I just type in the commands without doing anything ?
so basically I dont need to connect to my phone it does it automatically.
in other words if I just plug my phone in and open up cmd and the first 2 commands are this:
cd C:/RootVision
adb push psneuter /data/local/tmp
Then psneuter will be 'pushed' to my phones /data/local/tmp directory ?
Sorry for the confusing post but trying to get my confusion across.
bump..................
As long as you are in the adb folder it will work by just entering the commands. If you feel more comfortable knowing adb properly sees your phone just type 'adb devices' in command prompt while in your adb folder. It should return something like 'HTC0098755432' or something with a lot of numbers, as long as it doesn't say "No Devices Found" then you're good
Edit: Also I seriously recommend the wiki here on xda for rooting, it's much more concise and provides links to everything you could need
Sent from my Bulletproof G2
PaganAng3l said:
As long as you are in the adb folder it will work by just entering the commands. If you feel more comfortable knowing adb properly sees your phone just type 'adb devices' in command prompt while in your adb folder. It should return something like 'HTC0098755432' or something with a lot of numbers, as long as it doesn't say "No Devices Found" then you're good
Edit: Also I seriously recommend the wiki here on xda for rooting, it's much more concise and provides links to everything you could need
Sent from my Bulletproof G2
Click to expand...
Click to collapse
I find the layout too hard on the eye. Would the topic I referred to work safely to root the desire z ?
If you find it hard on the eye, use the cyanogenmod guide
It's just a stripped down version of the xda wiki.
-Nipqer
trippinz said:
I find the layout too hard on the eye. Would the topic I referred to work safely to root the desire z ?
Click to expand...
Click to collapse
It would most likely work, although being a guide already 4 months out of date, I can't say for sure. What I am absolutely sure of is that the xda wiki or the cyanogen wiki pointed out by the post above me will work and work safely with little to no chance of brick as long as you follow the instructions. Ultimately it's your device to do with as you wish, we simply were pointing out guides that are tested and known to be good
Sent from my Bulletproof G2
Original Thread
qzfive said:
In attempt to get root apps working on my Chacha after obtaining root shell via zergRush, I remembered an old exploit that my old Desire Z used called VISIONary+ that ran an exploit called rageagainstthecage (has since been patched by HTC) and mounted a ramdisk at /system/xbin, copied the su and busybox binaries to this ramdisk, and installed Superuser.apk as a normal application, which allowed for an almost fully functional root until reboot.
I opened up the VISIONary.apk with WinRAR and found a shell script with individual shell commands which match everything the application does. I typed these commands into adb shell running from my computer with my Chacha connected:
adb shell /data/local/zergRush (to obtain temproot via shell)
Once zergRush was done:
adb remount
adb shell mkdir /system/xbin (told me it already exists, assuming this is normal)
adb push Superuser.apk /data/app/
adb shell chmod 0644 /data/app/Superuser.apk
adb shell mount -t tmpfs none /system/xbin (this creates a ramdisk out of /system/xbin for the su and busybox binaries since they can't be pushed to the physical /system/xbin due to locked bootloader)
adb push busybox /system/xbin
adb shell chmod 4755 /system/xbin/busybox
adb push su /system/xbin/su
adb shell chmod 4755 /system/xbin/su
adb shell /system/xbin/busybox --install -s /system/xbin
After I typed all of that into adb on my computer, I obtained temproot on my Chacha (opened SetCPU, was asked for a Superuser prompt, haven't tested anything else yet). If anyone is willing to try this, please do so and report back. If this is better suited in the Development section, please inform me and I will remake this in Development.
EDIT: a modified su/Superuser.apk was required for this to work on newer Sense ROMs (Chacha included) - I have attached the modified su binary (must unzip) and Superuser.apk
VISIONary+ obtained from: http://android.modaco.com/topic/320350-19nov-r14-visionary-one-click-root/
Modified su/Superuser.apk from: http://forum.xda-developers.com/showthread.php?t=886999&highlight=superuser
-----
EDIT 2: attached a .zip which contains a .bat script which executes these commands for you, to make it easier and quicker to apply/reapply this temp root. Use the contents of temproot.zip instead.
Click to expand...
Click to collapse
Test it by myself and it works.
If you're running zergrush more than once you need to remove boomsh and sh.
type the following into adb shell:
1) "rm /data/local/tmp/boomsh"
2) "rm /data/local/tmp/sh"
App tested to be OK
-setcpu
-Titanium Backup (Backup and restore Data app only.)
-Root Explore (can't edit /system unless s-off)
Something that will never happen unless s-off
-flash custom rom
-flash recovery
-motify system, etc.
Bug:
-Speaker won't work ?
Is there some way not to loose root in such case after reboot ? Otherwise I don't see how temp root could be really useful.
Can we uninstall the stock apps using this method?
Sent from my HTC Wildfire S A510e using XDA App
drsjlazar said:
Can we uninstall the stock apps using this method?
Sent from my HTC Wildfire S A510e using XDA App
Click to expand...
Click to collapse
Something that will never happen unless s-off
-flash custom rom
-flash recovery
-motify system, etc.
Have I answered your question ?! NO
Reboot problem.....
It worked pretty well but my phone reboots if I keep it locked for a while.Any suggestions????
Wow, nice to know this works on other devices
The only "bugs" I noticed when I do this on my Chacha (similar device/same processor), is that the SD card unmounts itself when zergRush runs (might be part of the exploit zergRush does?), and that if I do this too early (ie. the "HTC Quietly Brilliant" bootanimation), it throws my phone into a bootloop -- haven't noticed any speaker bugs as of yet.
EDIT: I only get reboots when something tries modifying the /system partition - because my device is still S-ON (I'm trying to find an XTC Clip), the bootloader triggers a reboot
--Just another thought: since this mounts a ramdisk, would it work on any device that's temprootable?
Hmmm. Is it possible to make a fake flash of the recovery? Anyone try this?
qzfive said:
Wow, nice to know this works on other devices
The only "bugs" I noticed when I do this on my Chacha (similar device/same processor), is that the SD card unmounts itself when zergRush runs (might be part of the exploit zergRush does?), and that if I do this too early (ie. the "HTC Quietly Brilliant" bootanimation), it throws my phone into a bootloop -- haven't noticed any speaker bugs as of yet.
EDIT: I only get reboots when something tries modifying the /system partition - because my device is still S-ON (I'm trying to find an XTC Clip), the bootloader triggers a reboot
--Just another thought: since this mounts a ramdisk, would it work on any device that's temprootable?
Click to expand...
Click to collapse
Yes...I have used zergRush many times and it unmounts the SD card everytime.....so I think its not a bug......you answered my question of reboots tough,thanks.
And maybe this temproot method just might work for every device.
It doesnt work on htc pico (s"on).
Zergrush dont succeed
Sent from my Dell Streak using XDA App
jitin02 said:
It doesnt work on htc pico (s"on).
Zergrush dont succeed
Sent from my Dell Streak using XDA App
Click to expand...
Click to collapse
Maybe HTC patched zergRush on the Pico/Explorer
Guyz, ya don't have to fight with mills, take a look at my topic: http://forum.xda-developers.com/showthread.php?p=21167193
Update: New guide is in post # 122
http://forum.xda-developers.com/showthread.php?p=40433602#post40433602
The guide is in post # 98
http://forum.xda-developers.com/showthread.php?p=39362805#post39362805
Hello,
I have a Blu Dash 3.5 and would like to install clockworkmod recovery and enable root access, but so far have not found anything. Could you help me?
thank you
I tried using SuperOneClick, Gingerbreak, zroot but all without success.
Anyone have any other option?
_ _
I managed to set up the android SDK on ubuntu but I get permission denied message when trying to copy the files to the /system
I suppose I have to remount the partition in RW to be able to put the files but no idea how to do this.
_ _
fenrixarena said:
Well you can't without it being rooted, right now I just don't care about it anymore it's just a phone, & $30 isn't worth just freeing up some space. No guarantee that will make it run smoother without crashes either, that could just be a result of interface, so a bit of speed don't seem worth it to me, I have my own ringtones with ringdroid so I'm happy.
Everything having to do with extracting the boot.img requires it to be rooted otherwise I know enough about enough crapola already I could make that all spiffy and zabam if I wanted. I would just literally edit all the img files and provide a simple update.zip given I could get signing to work!
unfortunately I get nothing from fastboot at all, not sure it would help though. oem unlock stuff is all I recall about that besides it being a great wau to flash images to the phone
let me know if you make any progress, I'll put in my effort if you do anything at all that intices me to find a path to progress
Click to expand...
Click to collapse
fenrixarena, hope you get to find any progress on rooting this phone. I also agree with you that it is no worth the time or effort with this kind of phone but I think that the challenge is interesting . In my case I have no idea on how you may root it but I am sure it is possible i guess it all in find another compatible boot.img that can be rooted, right?
Regards,
- -
_ _
What is the address of the site that charges $ 30? We can verify that other users would like to do and split the cost ...
I managed to make root ...
I found the CWM recovery and stock recovery for Qsmart.
I was very curious if it would work in BLU and ended up installing the CWM with fastboot. It did not work, the screen just stays with the BLU and not access the recovery.
Then I installed stock recovery and did not work ...
But I realized that Windows recognized the device connected and I recognized two units with unsupported format.
then returned to the prompt and saw that the ADB was working. I used the command 'adb shell' and to my surprise was how the cursor #
So without wasting time already put su and busybox in /system/ bin and superuser.apk in /system/app, I changed the permissions and restarted the phone. And the root was working perfectly. :victory:
Only one problem, I do not have the recovery installed.
I wonder how I can help you to make root without losing recovery
>>
I use Windowns 7 Pro x64 bits.
I installed the drivers in the SuperOneClick version 2.3.3.
With the drivers installed could use fastboot and adb command.
Turning on the phone + vol - access mode fastboot / bootloader
It would be good to get root without losing the recovery. Because we need him to compile a clockworkmod recovery.
I used the romdump and got the following files:
https://docs.google.com/file/d/0B5rQL4bfhfPRZXhhZkg1Mkx5SHc/edit?usp=sharing
I used the mkfs.yaffs2 to convert the file system.tar for system.img
https://docs.google.com/file/d/0B5rQL4bfhfPRMGdaNnQ4b1RwclU/edit?usp=sharing
This system.img would function on another device?
okay, I am having one problem, what did you type for the permissions?
I've got superuser.apk pushed and the su in the /system/bin but when i try to chmod 777 it returns to -r- after I reboot!
Here's howto manually back up now that I have recovery adb root:
cat /proc/mtd
Then just cat (mtd#) > /sdcard/(image.img)
You can restore via fastboot flash
fenrixarena said:
okay, I am having one problem, what did you type for the permissions?
I've got superuser.apk pushed and the su in the /system/bin but when i try to chmod 777 it returns to -r- after I reboot!
Here's howto manually back up now that I have recovery adb root:
cat /proc/mtd
Then just cat (mtd#) > /sdcard/(image.img)
You can restore via fastboot flash
Click to expand...
Click to collapse
you get root access in adb shell?
send su to /system/bin with permission 6755.
busybox to /system/bin with permission 755.
and superuser.apk to /system/app with 644.
reboot your phone
then download terminal emulator on your phone and enter the command su
if the cursor change to # worked
erickreisbr said:
you get root access in adb shell?
send su to /system/bin with permission 6755.
busybox to /system/bin with permission 755.
and superuser.apk to /system/app with 644.
reboot your phone
then download terminal emulator on your phone and enter the command su
if the cursor change to # worked
Click to expand...
Click to collapse
These are actually good news... Right on!!! Cheers if you manage to root Blu Dash 3.5 :victory:
Can someone guide me on how I can Root my phone? What adb tools do i need?
Regards
az0ik said:
These are actually good news... Right on!!! Cheers if you manage to root Blu Dash 3.5 :victory:
Can someone guide me on how I can Root my phone? What adb tools do i need?
Regards
Click to expand...
Click to collapse
I can upload the cwm.img & adb I used + fastboot. Not all adb.exe will recognize the phone. Also drivers from qsmart for adb bridge.
1 boot holding vol down + power (about 15 sec.)
Fastboot flash recovery cwm.img
Then turn phone off.
Boot holding vol UP + Power (about 15 sec)
Adb push su /system/bin
Adb push busybox /system/bin
Adb push superuser.apk /system/app
adb shell
~# chmod 6755 /system/bin/su
~# chmod 755 /system/bin/busybox
~# chmod 644 /system/app/superuser.apk
reboot your phone
terminal emulator - su
permission granted
IT WORKED!
---------- Post added at 02:21 AM ---------- Previous post was at 02:00 AM ----------
sorry, tomorrow I will upload a zip with the img i used and so forth all in one zip so you can root with that, unless it's here by someone else by then I gotta work!
fenrixarena said:
I can upload the cwm.img & adb I used + fastboot. Not all adb.exe will recognize the phone. Also drivers from qsmart for adb bridge.
1 boot holding vol down + power (about 15 sec.)
Fastboot flash recovery cwm.img
Then turn phone off.
Boot holding vol UP + Power (about 15 sec)
Adb push su /system/bin
Adb push busybox /system/bin
Adb push superuser.apk /system/app
adb shell
~# chmod 6755 /system/bin/su
~# chmod 755 /system/bin/busybox
~# chmod 644 /system/app/superuser.apk
reboot your phone
terminal emulator - su
permission granted
IT WORKED!
---------- Post added at 02:21 AM ---------- Previous post was at 02:00 AM ----------
sorry, tomorrow I will upload a zip with the img i used and so forth all in one zip so you can root with that, unless it's here by someone else by then I gotta work!
Click to expand...
Click to collapse
Thank you so much Fenrixarena!! You are awesome :good::good::good:. I still can believe it, i thought it was a lost hope... I really appreciate for uploading the files I am patient enough to wait another day
Follow the ADB and the recovery I've used.
The drivers installed by SuperOneClick, but have these here:
32 bits - http://www.mediafire.com/?21na032gnzbfza2
64 bits - http://www.mediafire.com/?1hrwo325cb1ej2w
Fx
fenrixarena said:
interesting, I got a cwm4s12.img that's larger(4.51) and because of having a 64bit laptop without 32bit support I had to use a smaller ADB (158kb) to be able to recognize the phone and only on regular usb debugging does superoneclick install drivers which was useless since I needed the drivers to work in recovery.
If those files don't work for you I will upload mine
I got my files from foreign thread, and since I download so many versions and custom versions of programs like adb I'm not sure where it came from !!
oh, and he rooted the phone first, I only did it on a more bothersome platform.
Click to expand...
Click to collapse
the root worked on your phone?
Now we need a recovery. I'm trying to learn how to compile cwm, but it is very complicated.