Related
wdfowty said:
I'm having a few issues using my bootcamp partition for this (in Parallels), following eugene and king_fyo's tutorials, and was wondering what it would take to root my MyTouch3gS using osx?
I am semi-familiar with ADB, and I have made the loop.sh script, but i'm stuck at that point.
Here are my main questions:
-How to you get the loop to stop? I have to quit Terminal app to stop it.
-Any other things to know? Tips? Success stories? Tutorials maybe (or even a quick and dirty how-to?)
Thank you for your time, and for not flaming the newb
Click to expand...
Click to collapse
EDIT: SOLVED!
So, I'm waiting for my Nexus one to come in the mail, and I think to myself, "Why not give rooting the slide another go?"
Worked second try. How's that for random....
So, here's how I made it work...Dunno if it was 'luck of the draw', but here ya go anyways...Hope it helps someone!
1. Instead of turning off the phone normally, I rebooted straight into recovery, with the phone being on first.
Code:
./adb reboot recovery
2. While rebooting, MANUALLY search for devices as soon as you can type it in, repeating rapidly (This made the difference for me).
Code:
./adb devices
3. You should catch the device in offline mode right before the recovery screen. Unplug device for 5 seconds or so, then plug it back in.
Code:
./adb devices
List of devices attached
HT05MPS02279 recovery
4. You should see your device in recovery, then you're good to go. If not try again.
How to you get the loop to stop? I have to quit Terminal app to stop it.
Click to expand...
Click to collapse
No, simply hit <control> c from inside the Terminal app to break out of the shell script.
Any other things to know?
Click to expand...
Click to collapse
Not really, it may take you several tries to get this as it did for people using M$ Winblows. I tried it about 20 - 30 times on XP and never was successful. After switching to my mac, I got root on the 5th try!
My suggestion is to follow Eugene's guide, it worked great for me! If you have problems, post them here and myself or others will try to help you.
Good luck!
wdfowty said:
I'm having a few issues using my bootcamp partition for this (in Parallels), following eugene and king_fyo's tutorials, and was wondering what it would take to root my MyTouch3gS using osx?
I am semi-familiar with ADB, and I have made the loop.sh script, but i'm stuck at that point.
Here are my main questions:
-How to you get the loop to stop? I have to quit Terminal app to stop it.
-Any other things to know? Tips? Success stories? Tutorials maybe (or even a quick and dirty how-to?)
Thank you for your time, and for not flaming the newb
Click to expand...
Click to collapse
So I set up my camera to record myself rooting my phone using OSX and a couple friends walked into the room. I got distracted explaining what it was I was doing and didn't make the how to. If I have free time tomorrow afternoon I can make a how to vid. My girlfriend just got her slide yesterday and I believe she wants me to root it.
it's exactly the same doing it in Mac OSX as doing it in Windows except you don't have to worry about drivers. Make sure you get android SDK for Mac OSX and that you put it somewhere that is in your PATH variable.
But if you feel more comfortable doing it from Bootcamp Windows partition -- by all means do that.
Don't boot camp it... lol
I'll be posting a Mac OSX version of Eugene's Root Method shortly.
sk8rbebop, Fordude, stangri, Thanks for the quick replies! Wasn't expecting anything so soon!
I think I have tried to press CMD+C to stop the script, must have been my problem. lol.
@stangri What do you mean by PATH variable? I have the Android SDK installed in my home folder...
@sk8rbebop That's pretty funny . I'm going to have a go at it right now, I'll edit this post with my results.
edit: I don't know if this is right, but I stop the script when I see the device in offline mode. But when I unplug device, re-plug and run ./adb devices nothing shows up. The same happens if I don't unplug.
edit2: Still nothing. adb never recognizes device after I stop the loop.
I threw up a guide. Hope it helps.
Don't shut off the loop until something displays under the devices.
Re: Question: How to root MyTouch Slide using OSX?
When u connect the slide to your mac and type "adb devices", do you see your phone listed? Crucial first step before moving on.
To make things a little easier for me, I put the sdk tools folder in my path so I could issue adb commands in any directory I want to.
Sent from my T-Mobile myTouch 3G Slide using Tapatalk
@sk8rbebop Read the guide and i'm still stuck at the loop. I'm having the same issues as earlier, the device will show for a little bit but right before the recovery screen shows, it dissapears. I was stopping the script once I saw the device, before it "dissapeared". Stopping the script after it dissapears does the same...
BTW, I've noticed that I need to start the adb daemon before I run the loop in order for it to even see the device in the loop. Odd.
@Fordude Yes, if I run ./adb devices when the phone is on I get my serial number and it says "device".
edit: I found that I am running an out of date SDK revision, so I am updating to the newest (revision 6), lets see if that makes any difference...
edit 2: No dice. Lame. Oh well I guess...Try try again. My mac seems to be determined not to let this happen
update: So, I'm getting a nexus. Thanks all for your help, happy hacking!
SOLVED
post removed
I get this error after typing "./rageagainstthecage-arm5.bin" into the command prompt. I tried deleting files and starting over, I pretty much tried everything and still get this error. Even if I try starting all over I get this error right from the start. Plz help! Thanks in advance!
I get this. It just started happening. I have no freakin clue how i created this problem but I am sorely annoyed by it.
Anyone got any ideas on how to get rid of the "offline" status of my EVO?
C:\android-sdk-windows>adb devices
List of devices attached
HT05THL04973 offline
mindcrime11 said:
I get this. It just started happening. I have no freakin clue how i created this problem but I am sorely annoyed by it.
Anyone got any ideas on how to get rid of the "offline" status of my EVO?
C:\android-sdk-windows>adb devices
List of devices attached
HT05THL04973 offline
Click to expand...
Click to collapse
I'm also getting this on a Droid X running Android 2.2.1, using the Android SDK Tools Revision 8.
It happened after I ran rageagainstthecage-arm5.bin as part of the "DarkOnion Root for Droid2" procedure for rooting the Droid X. This error is preventing me from completing the procedure. Does anyone know how to fix this error?
EDIT: I was able to correct the error by rebooting my phone (powering down and then powering up). Afterwards, I was able to complete the root procedure, although I'm not sure how to test it.
EDIT2: Just tried running the Wifi Tether app for root users. It says I'm still not rooted. :::sigh:::
If you have hboot 2.10 then you have to do things differently. Namely you need to use Android Terminal Emulator on your phone instead of adb on a command prompt after you push the files over.
It seems that adb gets permanently killed by rage exploit. Check the Hboot 2.02 thread for more details in the dev section.
So, I heard other phones have this option in recovery but what about kaiser?
Do we have thing like such? (I chose recovery in install menu, and it returns back to Install menu)
From past two days I am seeing that my phone sticks to 88% charging (even I remained plugged in for 10 hours) and drops the level from there. Tell me how can I recalibrate my batter? its standard 1350mAH and just to let you guyz know that I am having same good battery backup as it was before i-e 48+ hours.
Thank you!
I asked this question since search didnt give me quiet good response regarding Kaiser
You can try turn off phone and remove battery for a while. In first boot kernel should recalibrate battery level
doesn't help I think :|
The old method on the Galaxy S was to let it drain fully, recharge to full then go into terminal emulator and type
su
rm /data/system/batterystats.bin
then reboot straight away
I found this...
Maybe helpful...
Edit : Take also a look to the link at the bottom..
I don't think you need a recalibration.
Charge overnight, then use "adb shell" and type:
echo 100 > /sys/module/board_kaiser_battery/parameters/set_percentage
FlanFlinger said:
The old method on the Galaxy S was to let it drain fully, recharge to full then go into terminal emulator and type
su
rm /data/system/batterystats.bin
then reboot straight away
Click to expand...
Click to collapse
Doesn't help :| I tried like 6-7 times and still my phone is stuck at 84% and not charging anymore
n2rjt said:
I don't think you need a recalibration.
Charge overnight, then use "adb shell" and type:
echo 100 > /sys/module/board_kaiser_battery/parameters/set_percentage
Click to expand...
Click to collapse
I had to install drivers for adb all again, the HTC Dream Composite Device ones. ADB didnt connect :/ I was so frustrated, I flashed back to WM. Atleast no crashes till yet and battery is charging/draining as it should. Though I will miss finger-griendliness till some time. Maybe on my next fly to android I might start doing gingerbread.
I've been working on this for the past week. Every exploit I've tried just hangs after a while. I've gotten much further manually. I've got unbuntu and been working using various manual methods. The thing I've noticed is that there is no system folder in root. There is a system partition in which app and bin folders exist. Later today I'm going to have time to try some more. If it weren't for these silly rules id reply to somebody elses post, but I guess reading in forums for 3 years as a registered user doesn't count. Never a need to post as I've always found something using a search. And now I've got a phones that's been out for a week and there's no info out on it so I guess I get to develop myself. Not a hard thing...just time consuming and I've got better things to do, but these pink apps gotta go and I need wired or wireless tehter again. Hopefully I have succcess later today and can post how I accomplished it.
I'll be waiting anxiously. please post updates in this thread with your progress!
Any progress on this? I have been attempting but no luck.
update on progress
jb0ne said:
I'll be waiting anxiously. please post updates in this thread with your progress!
Click to expand...
Click to collapse
ok so here's what i've learned so far from trying every method that i can find...
when you boot the phone into the pink screen (volume up and volume down plus power) there is a partition containing 1 folder with 5 files. That folder is called image and the file inside are amss.mbn, boot.img, cust.img, emmcboot.mbn, and recovery.img
The Ascend G300 is a similar phone to the G312 and there is a filed called superrecovery which changes the recovery to set ADB with root priveliges and installs SU in system. If we use the recovery from that batch file made by PauloBrien and push it to the device while in pink screen mode and then reboot into recovery the phone won't power on. You can return to the pink screen and change back to the original recovery, but you can not boot the device into recovery nor regularly. Now this gave me an idea as i'm typing. what if i change it and issue the command in ADB as ADB works during the pink screen. I'm going to try that now.
But this can't be done when in bootloader, only in pinkscreen which makes me think it's fastboot USB mode, but fastboot commands dont work uless you are in the bootloader with the huawei logo which you can only get into by issuing the reboot-bootloader command through adb. once you enter bootloader mode via ADB reboot command then you are able to issue some fastboot commands.
ok so that didn't work...basically when the files in the imge folder are changed the device won't boot into anything but the pink screen mode.
the original recovery file size is 6340KB and the one from PauloBrien is smaller at 5074KB. I'm wondering if file size has something to do with why it won't boot, however, i'm not familiar with what's inside of these files. So...as i reasearch how to build our own clockworkmod recovery i'm wondering if there's a way to change the ADB command inside from not root to root. if it's a on off selecton i'm not sure how i'd affect file size. this is where we get into the realm of knowledge that i don't possess.
so if anybody can offer up some knowledge from where i stand now... please do so.
on a side note, when running exploits, (gingerbreak, zergrush, doomsomething, psneuter, etc)...they all hang.
in linux when trying to drop a file into /system/bin the terminal read out says something about failing to cycle power, not certain what this means.
as i learn a bit more, i'll go ahead and add more...
I am hopeful to hear back from you with a successful root method for this device. I myself just purchased this phone for myself and would really love to see more development on it. Seems like a solid phone with a low entry price. Look forward to seeing what you come up with.
I'm also waiting anxiously for someone to figure this out. I just got this phone and while I really like it, there is just so much packed on this thing that I want to get rid of before I can really enjoy the phone.
I'll be watching this thread as well hopefully OP or someone else will figure out the trick to rooting this phone, like others I have used the usual methods but no luck. I've counted no less than 13 programs I'd uninstall right off the bat.
For what its worth the phone seems to not be considered part of the Ascend models of phones although they are quite similar our model is called the Unite U8680 and the Unite Q U8730 (the slider version). I've sent a email to Huawei lets see if they respond at all.
It's pretty much useless but this is all I can find on the G312 on the Huawei website:
http://www.huaweidevice.com/worldwide/technicaIndex.do?method=gotoProductSupport&productId=4086&tb=0
I'll be watching this thread as well. According to a post on another forum regarding a different Huawei model, dialling *#*# 2846579 #*#* and making some changes in the log file settings suddenly made their phones rootable for some reason. However while the same # gets you into the service mode on this phone, the log file changes made no difference.
I wonder, though, there are quite a few other options in that service mode. Maybe something in there that could be useful.
Edit: There's one menu that looks interesting, the USB one. You can change it to all sorts of modes including "Manufacture mode" whatever that is. Afraid to try it, don't want to brick my wife''s new phone
I've been playing with this menu as well and some of the USB modes do seem interesting. I was hoping this would let me find the product ID for the phone cause I found a link on the Huawei homepage to register to get an unlock code for the boot loader on this phone. If anyone is interested here is a link to the page and sadly the method they say to find the product ID doesn't work on our phone.
http://www.huaweidevice.com/worldwide/servicePolicy.do?method=toApplyUnlock
huawei says the product ID is an 8 digit number. I've been trying to dump the log files so i can scan them for some kind of 8 digit number. i've also tried all the different USB modes as well as a few other changes in the project menu that we're able to access. These haven't given me any success in changing the ownership of the folders needed to gain root access. i've not had any time to tear apart the recovery image to figure out what it's doing. but all in due time somebody will figure this out. still haven't been able to get fastboot to work properly either. am running through the usb modes on that now.
Yes please help i cannot figure out out either
builder.clockworkmod.com
so i've been working on building a recovery image for this devices using koush's site and have been able to build it, but the device won't boot into recovery yet. not sure how to fix this, gonna mess around and keep on trying. i can get it to boot back up and can get it to respond to adb commands when in the mode that just shows the android 4g logo. but i can't get into recovery. not through adb and not through using the power and volume buttons.
still working on it... any body else have anything yet?
No info on rooting this phone but Huawei just posted on their website the open source gingerbread kernel for the G312 U8680 here is a link to it:
http://www.huaweidevice.com/worldwi...=toDownloadFile&flay=software&softid=NDY3MzU=
It's been rooted!
Yep, it's a simple one too. Happy to have my wife's phone rooted Removing bloat, however, is tricky -- it's hidden in an inaccessible partition and when you erase it, it restores it on next reboot.
http://forum.xda-developers.com/showthread.php?p=31237225#post31237225
http://www.droidrzr.com/index.php/topic/4276-how-to-root-huawei-mytouch-4g/
Big thanks to mattlgroff for cracking this nut!
jb0ne said:
Yep, it's a simple one too. Happy to have my wife's phone rooted Removing bloat, however, is tricky -- it's hidden in an inaccessible partition and when you erase it, it restores it on next reboot.
http://forum.xda-developers.com/showthread.php?p=31237225#post31237225
http://www.droidrzr.com/index.php/topic/4276-how-to-root-huawei-mytouch-4g/
Big thanks to mattlgroff for cracking this nut!
Click to expand...
Click to collapse
When you install an update to one of these apps lets use the, yahoo mail on for example, it will show in the /system/app or /data/app. The problem is the apk before the update is in /cust/t-mobile/us/app which is read only and unable to be mounted as R/W and that is why Titanium backup is unable to uninstall it.
I have tried moving it and deleting it manually with no luck. I have not tried through ADB yet but may give that a try next.
jamonthis said:
When you install an update to one of these apps lets use the, yahoo mail on for example, it will show in the /system/app or /data/app. The problem is the apk before the update is in /cust/t-mobile/us/app which is read only and unable to be mounted as R/W and that is why Titanium backup is unable to uninstall it.
I have tried moving it and deleting it manually with no luck. I have not tried through ADB yet but may give that a try next.
Click to expand...
Click to collapse
If you figure it out and find anything out I would love to know about it. Where should I watch for an update in case someone does get that sorted out?
Recovery mode
There is an accessible recovery mode, at least on my querty version of the phone. You have to completely pull the battery first. Put the battery back in, hold Volume up, and then hit power. I held the power button for a couple seconds, and volume up for maybe 6-8 seconds, then started hitting volume up repeatedly. The key is to pull the battery each time you try, I think. It looks like powering off from the phone's power menu just puts it in a suspend sort of mode. (Compare boot times when rebooting, and when pulling battery)
Apparently the bootloader is locked, so not sure how useful it is yet.
For anyone with a T-Mobile MyTouch Q (Huawei U8730), I created a wiki page for it, and we should post in the New Device Forum Requests thread so we have a specific place to post info.
I just purchased a U8730 today and will definitely be figuring out how to root it at some point.
For anyone that cares here's a link in case you haven't registered at the other site.
http://j.gs/1U5q
I'm hoping we can get some development going for this phone. I just picked one up for my daughter a month ago and it's giving her memory filled messages already. It'd be great if we can get it permanently rooted and remove bloat to start... then possibly move onto Cyanogen... considering she had the horrible Comet (also by Huawei) previously and it had development for CM7. I may be taking a leap from my contract soon, but can't go to Straight Talk with her phone unless it's unlocked
I know that it was foolish of me to not fully research this set of commands I have copied the before and after of tit all from the command line. I was attempting to mess around with my phone with QPST. I know, I can REALLY REALLY make things hideous if I don't tread carefully with QPST, but I am willing to take the risk in order to learn, even if I do get burned because my phone bursts into flames.
Any who here is the output from my commandline which I ran because using *#0808# and switching to either RNDIS+DM+MODEM or DM+MODEM+ADB didn't make my phone visible for QPST. And I also tried while in recovery, download mode, and all the other settings in the *#0808# menu, plus variations of the menu and then booting into recovery, normal boot, and download mode. All to no avail, then in frustration I tried the following and it's gotten to the point I can't see my phone via adb anymore. So could someone please give me the undo set of commands for typing into my phones terminal as I can't type them via my computer due to adb not seeing it anymore? Thanks
C:\Users\xxxxx>adb devices
List of devices attached
0123456789ABCDEF device
C:\Users\xxxxx>adb shell
$ echo MODEM USB > /sys/class/sec/switch/usb_sel
echo MODEM USB > /sys/class/sec/switch/usb_sel
cannot create /sys/class/sec/switch/usb_sel: permission denied
$ su
su
# echo MODEM USB > /sys/class/sec/switch/usb_sel
C:\Users\xxxxx>adb shell
error: device not found
Oh!, and if anyone can explain either what the commands did or better yet where I can go read about such commands and what they do that would be great too. Thanks
Not sure how relevant this is or if it will help you but this man seems to be in kinda the same boat, why don't you take a look at this thread particularly post #2 http://forum.slimroms.net/topic/2008-broken-usbuart-path-causing-loss-of-adb/
Sent from my Nexus 7 2013 using Tapatalk
crazymonkey05 said:
Not sure how relevant this is or if it will help you but this man seems to be in kinda the same boat, why don't you take a look at this thread particularly post #2 http://forum.slimroms.net/topic/2008-broken-usbuart-path-causing-loss-of-adb/
Sent from my Nexus 7 2013 using Tapatalk
Click to expand...
Click to collapse
Thank you for the link I haven't tried anything based on the information yet, actually haven't read it all yet. Very complex stuff just lets me know how far I have to go. Odd thing is that I now for some reason have ADB working again. I did a factory reset recently and the other day I reinstalled/refreshed my computer. My computer was infected by a bunch of viruses and malware the phone was just sluggish and I had way more apps I wanted rid of than to keep. Anyway, I don't know if the virus on my system had anything to do with the malfunction or if it was the command I used but for now it is back to working.
I was working on a friends HTC Desire and was having a hell of a time getting fastboot commands to work. I got hboot USB working but when giving a command it would generate a "device connected toi USB has malfunctioned" also the USB ports would shut off untill reboot too intermittantly and even my wifi three or four days ago became disabled and I reset the adapter fine for 5mins then it went a level deeper and deeper till I reinstalled the driver. That being said it is more likely that it was the virus and or the person messing with my system that was causing all the grief. They even triggered email alerts on a couple of my accounts that passwords were input wrong 5 times in a row and that some security settings were being changed. Hopefully I have dealt with that if not I'll have to wait till they get bored. Sorry if that was a little off topic it sort of conencts to my recent problems.