Related
I will be accepting donations if you like my work. After contacting HTC, they informed me that my device is not under warranty, as a technician determined it to be "user related" damage and that all repairs will be at owner expense.
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=8141983
If you follow my twitter, you know I bricked my G1. I am trying to get it repaired, but due to the long response time I had to buy a mytouch (no point having two G1s IF the other one gets repaired). Using this bad luck to my advantage, I scripted a way for hero to run on both with two simple commands.
How I rooted a brand new "perfected SPL" MT3G and installed Hero in 15 min:
http://forum.xda-developers.com/show...&postcount=154
Link to original thread: http://forum.xda-developers.com/showthread.php?p=4365404#post4365404
Updated, but still feeling slow? Back up. Try rm system/sd/app_s then reboot to recovery and wipe data. then install fresh. Before restoring your data, open the backup folder on your sd card and remove the subfolders for programs you no longer have or need to have backed up.
I noticed a 10% increase in speed and my phone was far from lagging to begin with.
Losing messages? Make sure that system/sd/app/com.android.mms.apk does NOT exist, as this was an old release. Go into settings for messaging (from the conversation list panel) and set priority to "High"
Most Recent:
G1 / MT3G: http://twistedumbrella.slackdev.com/ZeroXd-6.0.zip
Now includes dynamic swap. Rewrote the method of apps to sd for myTouch.
Build will move system apps, user apps, and dalvik to sd on a g1 device.
Build will ONLY move user apps to the sd when using a myTouch.
This will allow the system apps and dalvik to remain on internal device.
This is a completely new method of doing a merge build so bear with me.
I am going to be rewriting things for users without a lot of user apps, like myself.
This will allow the entire build to be placed onto internal for mytouch users.
Once you have updated and are ready to use the phone, execute Terminal and enter the following commands:
su
magic
This configures the system to the specific device. This is until I finish automation.
LEDs have been restored to 93%
Bluetooth restored in MT3G
Porting my own boots for MT3G
Based on the System Image from Haykuro
Using the Kernel and Boot.img from JAC
Extensive system script edits were done
SwitchROM installs itself to system/sd/
LEDs are at about 90-100% brightness
CPU Optimization turned off by default
Enhanced Terminal included
Fixed My Account included
G1 / MT3G: http://twistedumbrella.slackdev.com/ZeroXd-5.2r5.zip
http://twistedumbrella.slackdev.com/Resources.zip
twistedumbrella said:
MultiTouch for MT3G being patched NOW
Click to expand...
Click to collapse
Does that mean multitouch doesn't work and one more unanswered questio IS it from the latest release that modaco did, i asked it since 5.0 so please answer
White Rosie doesn't work i tried it but i doesn't show up and it doesn't even install shows parse error, can you do something about that. Really appreciate your work. Will donate as soon i finish with my exams, I came to US for a holiday for 3 months and as i came back i have exams, only 3 left, have to finish 6 books per subject (thats f*****ng 3 months syllabus) and i have exams after 2 day holidays , thats why i have been a bit inactive in the community, will be active on 24 and will provide a special version of HERO based on my favourite ZEROXD.
Installed JACHeroSki 2.0 and i get stuck on a boot loop. i've tried wiping and re-flashing and same thing.
mgorman said:
Installed JACHeroSki 2.0 and i get stuck on a boot loop. i've tried wiping and re-flashing and same thing.
Click to expand...
Click to collapse
For me 2.0 working fine,but cannot install ZeroXd-5.2r4-installation aborted:/
In v2.0 cannot run wifi:/somebody else?
Had to fix scripts. Check the link on original thread for download. They are the same files. The verification fail happens when your downloading as I upload. It was a last minute fix on the way to work. Sorry for the issues.
hey twisted...great work on the roms...
couple issues with me...
auto-rotate doesn't work...
auto correct and dictionary doesn't work also...
is there any way we can correct this?
tq745 said:
hey twisted...great work on the roms...
couple issues with me...
auto-rotate doesn't work...
auto correct and dictionary doesn't work also...
is there any way we can correct this?
Click to expand...
Click to collapse
What device are you using? MyTouch? Did you run the terminal command?
BTW, for everyone else: http://twistedumbrella.slackdev.com/user.conf
Did some testing, seems to run a little smoother
tq745 said:
hey twisted...great work on the roms...
couple issues with me...
auto-rotate doesn't work...
auto correct and dictionary doesn't work also...
is there any way we can correct this?
Click to expand...
Click to collapse
Thank you... h.nocturna for the fix, and nacron for the heads up...
Here is the fix for auto-complete... Worked for me on 5.1r2
Everything in
open dos prompt.
adb remount
(***back up the original***)
adb pull /system/sd/app_s/HTC_IME.apk c:\(*your directory*)\HTC_IME.apk
(***install the new one***)
adb push c:\(*your directory*)\HTC_IME.apk /system/sd/app_s/HTC_IME.apk
start your Messaging it will crash the first time you want to use the keyboard... restart Messaging and it should work...
HTC_IME.apk here: http://www.mediafire.com/?te0symyx4yz
Mms auto-rotate works for me in 5.1r2 so I dont know. But possibly you still have the old Mms.apk. Try pushing the new one from 5.0 or later rom...
Twisted are you using BFS in your new builds??? Post 5.1 that is....
twistedumbrella said:
What device are you using? MyTouch? Did you run the terminal command?
BTW, for everyone else: http://twistedumbrella.slackdev.com/user.conf
Did some testing, seems to run a little smoother
Click to expand...
Click to collapse
so i opened up better terminal and when i entered su it says
/system/xbin/su: not found
help?
in the meantime i'll try zambesey's way
twistedumbrella said:
What device are you using? MyTouch? Did you run the terminal command?
BTW, for everyone else: http://twistedumbrella.slackdev.com/user.conf
Did some testing, seems to run a little smoother
Click to expand...
Click to collapse
so i opened up better terminal and when i entered su it says
/system/xbin/su: not found
help?
in the meantime i'll try zambezy's way
same issue as above :-(
1.8 is running pretty awesome.
i guess its safe to assume that i shouldn't try 2.0 yet? lol
zeroxd 5.2r4 seems to be faster than jacs 2.0 but i cant get auto rotate to work or multitouch and when i try the commands in first post i get "/system/xbin/su: not found''
did you try running the commands via adb ?
im not familiar with doing it that way i dnt even know wat adb is
just connect your phone to the pc
install the drivers from android SDK
start > run > cmd
cd to the android tools directory
and adb shell
that's how i did with my phone and works perfectly
im not gona risk any damage ill deal without the rotate for a day till its fixed
tq745 said:
so i opened up better terminal and when i entered su it says
/system/xbin/su: not found
help?
in the meantime i'll try zambezy's way
Click to expand...
Click to collapse
should be under /system/bin not xbin
Hello,
This is a dead easy fix to get tethering working completely with android-wifi-tether (http://code.google.com/p/android-wifi-tether/):
UPDATE
New development version has support for this rolled in, instructions are no longer necessary:
http://code.google.com/p/android-wi...name=wireless_tether_2_0_2-pre14.apk&can=2&q=
Steps:
1. Open adb shell (start cmd.exe, run "adb shell")
2. Issue the following commands:
- "mkdir /sdcard/android.tether"
- "cat /etc/firmware/fw_bcm4329_ap.bin > /sdcard/android.tether/fw_bcm4329.bin"
3. Download and install the android-wifi-tether application, start tethering.
Your log from android-wifi-tether should look like the attached image.
Happy configuration free tethering!
NOTE: This works because of the two separate firmwares that HTC has included in /etc/firmware. One is specific for AP-mode and must be more open to this kind of stuff. The original bug stemmed from the usual firmware dropping ARP requests pretty consistently, possibly as a powersaving measure.
The second firmware is loaded using the firmware_path option when loading the bcm4329.ko kernel module.
anyone else confirm this working please.
I confirm this working...
You will need to have root to run the app of course but 2 or 3 people have confirmed it on bug 362 already on the google project.
Not working for me
AWESOME!!!
actually i ever use wifi tether but this is pretty cool because it actually worked. i know on the heroC we had issues with wifi tether all of a sudden not wrking after 2.1. nice to see that its been fixed. good work spreading the word
ya. it will get SU permissions,
i can find the connection.
i connect to it. but no data transmitting.
would be cool if someone can confirm 4g is able to be tethered.
fdot said:
ya. it will get SU permissions,
i can find the connection.
i connect to it. but no data transmitting.
Click to expand...
Click to collapse
same here. any ideas?
toastcfh said:
would be cool if someone can confirm 4g is able to be tethered.
Click to expand...
Click to collapse
Not confirming but based on what I read harry_m stated the wifi tether app uses the current connection, so in theory if you switch between 3g and 4g the app will switch accordingly.
i can confirm
I originally flashed with toast's rom. Used the recovery .bat to install Flipz's stock root rom.
I then flashed toast's radio rom.
wifi tether did NOT work.
I then performed the above instructions, and viola, it works fine. (i am posting via wifi tether)
I want to thank everyone who is hard at work on these projects, you guys are awesome.
fdot said:
ya. it will get SU permissions,
i can find the connection.
i connect to it. but no data transmitting.
Click to expand...
Click to collapse
Check that the log screen looks exactly like mine does. Did you get any errors when you issued the adb commands?
Look on your sdcard for the android.tether folder and see if fw_bcm4329.bin file exists there.
toastcfh said:
would be cool if someone can confirm 4g is able to be tethered.
Click to expand...
Click to collapse
dcmtnbkr said:
same here. any ideas?
Click to expand...
Click to collapse
It should work according to one of the comments given about the issue. http://code.google.com/p/android-wifi-tether/issues/detail?id=362#c36
Because I am weary of rooting my phone not being able to return it to stock, I am gonna try it with the unrevoked root first.
goodfellaslxa said:
I originally flashed with toast's rom. Used the recovery .bat to install Flipz's stock root rom.
I then flashed toast's radio rom.
wifi tether did NOT work.
I then performed the above instructions, and viola, it works fine. (i am posting via wifi tether)
I want to thank everyone who is hard at work on these projects, you guys are awesome.
Click to expand...
Click to collapse
i followed this same exactly.
andrew500 said:
Check that the log screen looks exactly like mine does. Did you get any errors when you issued the adb commands?
Look on your sdcard for the android.tether folder and see if fw_bcm4329.bin file exists there.
Click to expand...
Click to collapse
no errors in adb.
and the .bin file is sitting in the directory.
and the log looks like yours.
running toasts ROM
can't get this to work
followed instructions, and when i click on the tether button it instantly says: unable to start tethering, please try again!
log screen is completely blank
any ideas?
fdot said:
i followed this same exactly.
no errors in adb.
and the .bin file is sitting in the directory.
Click to expand...
Click to collapse
I meant the screen in android-wifi-tether, does it look like the screen cap I included? It should have a debug line about the loaded firmware on the first item.
- Didn't see the edit you made with that screen:
Have you done the OTA update? Could be the SD card bug possibly. The log screen shows it didn't load the external firmware.
"Unable to start teterhing try again"
I skimmed this thread, I am using toast's rom.
I have just applied the Unrevoked root. I cannot access the sdcard via adb shell. Any ideas?
When i send command
"cat /etc/firmware/fw_bcm4329_ap.bin > /sdcard/android.tether/fw_bcm4329.bin"
it gives me error msg
"cannot creat /sdcard/android.tether/fw_bcm4329.bin: directory nonexistent"
i followed this same exactly.
no errors in adb.
and the .bin file is sitting in the directory.
Click to expand...
Click to collapse
I meant the screen in android-wifi-tether, does it look like the screen cap I included? It should have a debug line about the loaded firmware on the first item.
- Didn't see the edit you made with that screen:
Have you done the OTA update? Could be the SD card bug possibly. The log screen shows it didn't load the external firmware.
Click to expand...
Click to collapse
I have not done the ota.
-------------------------------------
Sent via the XDA Tapatalk App
Question to those who have updating their Dream from Rogers, was it at all slow or where their noticeable improvements?
I have one at my disposal but running stock OS (1.5/1.6 i assume). Anyone have a nice and easy to follow tutorial to update this phone without hassles? Also does updating android OS require rooting the device?
Thanks in advance.
Bloodyskullz said:
Question to those who have updating their Dream from Rogers, was it at all slow or where their noticeable improvements?
I have one at my disposal but running stock OS (1.5/1.6 i assume). Anyone have a nice and easy to follow tutorial to update this phone without hassles? Also does updating android OS require rooting the device?
Thanks in advance.
Click to expand...
Click to collapse
try this:
http://theunlockr.com/category/howto/android_how_tos/htc-g1-dream-how-tos/
Follow instructions. This seems to me to be the easiest guide. Be careful of the Rogers/T-Mobile thing. Seems there are different radio's and such. I don't know anything about Rogers. As far as Roms, I use HTCclay's Superfly TCBY. Lot of memory left on phone. Just try a few to see which you like. Good Luck.
By the way, you do have to be rooted. The guide will walk you through it.
crz6662 said:
try this:
http://theunlockr.com/category/howto/android_how_tos/htc-g1-dream-how-tos/
Follow instructions. This seems to me to be the easiest guide. Be careful of the Rogers/T-Mobile thing. Seems there are different radio's and such. I don't know anything about Rogers. As far as Roms, I use HTCclay's Superfly TCBY. Lot of memory left on phone. Just try a few to see which you like. Good Luck.
By the way, you do have to be rooted. The guide will walk you through it.
Click to expand...
Click to collapse
I would say to try the ROM in my sig (the stock ROM)
works for g1 and 32B Magic
he is going to need the EBI1 kernel to go with the rom.
Ok I am reviving this thread because I want to make sure I am following the right steps in doing so. Don't want to mess this up.
Successfully rooted the phone following video I found in the second post of this thread. Can't link you to it because I am still a new member =S! I checked the radio version of the phone and it is 3.22.20.17. Which ROM is recommended?As I said, I just want to get rid of this terrible stock rom from rogers and put froyo (which in turn also allows me to get touch screen keyboard activated) on here.
Thanks in advance.
With that radio you will need to flash ebi1 kernels after you flash the roms.
I completely forgot that Rogers blocked the virtual keyboard with their firmware. That's such bull****.
Sent from my HTC Hero using XDA App
asb123 said:
With that radio you will need to flash ebi1 kernels after you flash the roms.
Click to expand...
Click to collapse
Now you have more information in the link in your sig. Question: Can you re up the RS link you have there? Also, rooting the phone just means that you have the app called Superuser?
Now I get quite lost the moment you start explaining the options HTC Dream users have. Is there a recommended ROM to download for this phone considering its specs?
I completely forgot that Rogers blocked the virtual keyboard with their firmware. That's such bull****.
Click to expand...
Click to collapse
Yes it is sad that rogers has done this. Do whatever they can to screw the consumers over. Just found out it is 1.5.
Any help on this?
Ok still lost on trying to do this and want to follow the set up from cyanogen but its really complicated. I don't want to make a backup of contacts and stuff because it wasn't originally my phone.
Do I still need the amon_ra's recovery?
Bloodyskullz said:
Ok still lost on trying to do this and want to follow the set up from cyanogen but its really complicated. I don't want to make a backup of contacts and stuff because it wasn't originally my phone.
Do I still need the amon_ra's recovery?
Click to expand...
Click to collapse
Think of what you need to do:
1) Obtain root access so that you can flash a new recovery
2) Replace recovery so that you can flash new SPL
3) Flash new SPL so that you can be more compatible with roms / kernels
4) Flash a new rom (IE/ Cyanogenmod 6), and a compatible EBI1 kernel (for instance, Brian Crook's ones on the Cyanogenmod website)
Without getting into huge detail, you do it in this order to prevent your device from being unable to boot / recover.
You can flash the new RADIO and SPL from here: http://forum.xda-developers.com/showthread.php?goto=newpost&t=831139
Along with that, you use the appropriate supported +14MB EBI0 kernel.
More RAM is good
Well that makes sense.
Now I am following the Cyanogen wiki link (can't post there) and it says to launch flash rec but I can't understand from where I have to do this. Anyone care to help? And how does the Andriod SDK help?
Bloodyskullz said:
Well that makes sense.
Now I am following the Cyanogen wiki link (can't post there) and it says to launch flash rec but I can't understand from where I have to do this. Anyone care to help? And how does the Andriod SDK help?
Click to expand...
Click to collapse
Andriod sdk has the adb component needed to initiate commands to your device from your computer. then you need the android windows usb drivers.after installing sdk to see if you have connection with your device, open console on your computer start>run>type cmd and hit enter at the prompt type adb you should get several lines back kind of an options menu. at next prompt type adb devices. if your device is recognized you will get back:
device XXXXXXXX (this will be an actual number).
if you dont get any devices back with your phone attached to usb then you probably need the driver. just google it.
as for flashrec I dont believe I used this. I used exploid to gain root and install 1.33.2005 spl
Where do I get the android driver for windows (7 64bit specifically)? Adb command aint working in my cmd.
So what do I do about flashrec? Man updating this thing is driving me nuts. So many unexpected curves.
I also have Windows 7 64bit and I didn't need a driver it just works for me. Please tell us exactly what you are typing in and what output you are getting. You could also try the instruction to install the usb driver here:
http://developer.android.com/sdk/win-usb.html
What is your build number in settings? If it is 1.89.631.1 you are following the wrong guide. (see the top of that guide)
beav_35 said:
I also have Windows 7 64bit and I didn't need a driver it just works for me. Please tell us exactly what you are typing in and what output you are getting. You could also try the instruction to install the usb driver here:
http://developer.android.com/sdk/win-usb.html
What is your build number in settings? If it is 1.89.631.1 you are following the wrong guide. (see the top of that guide)
Click to expand...
Click to collapse
When I type in ADB command it just states that the command is not recognized (even when SDK is open).
Build number 1.85.631.5.
Now when I turn on phone it accepts it after I plug it into computer. I can mount sd card to copy files without issue.
Do I need another tutorial (preferably video since its easier for me but text is just fine)?
Bloodyskullz said:
When I type in ADB command it just states that the command is not recognized (even when SDK is open).
Click to expand...
Click to collapse
This doesn't mean that it can't find your phone, it means that it can't find the adb.exe.
Bloodyskullz said:
Build number 1.85.631.5.
Click to expand...
Click to collapse
That is a pre-911 build. Don't see too many of those any more. Rogers harassed everyone into updating.
Bloodyskullz said:
Now when I turn on phone it accepts it after I plug it into computer. I can mount sd card to copy files without issue.
Do I need another tutorial (preferably video since its easier for me but text is just fine)?
Click to expand...
Click to collapse
http://www.bleepingcomputer.com/tutorials/tutorial76.html
http://forum.xda-developers.com/showthread.php?t=502010
http://www.youtube.com/watch?v=Z3SpI7m7mFI
Does the zip file for the android SDK make a difference if I can't install it through the .exe? It keeps saying that it doesnt detect the Java SDK when I try to install.
Yes, you can use the .zip. Extract it, run setup.exe, install Platform-tools, cd to the platform-tools directory then you can use adb. Fastboot is in the tools directory. That was just changed in the 2.3 sdk update so I don't know if the guide has been updated yet.
beav_35 said:
Yes, you can use the .zip. Extract it, run setup.exe, install Platform-tools, cd to the platform-tools directory then you can use adb. Fastboot is in the tools directory. That was just changed in the 2.3 sdk update so I don't know if the guide has been updated yet.
Click to expand...
Click to collapse
The only .exe file in the zip is the SDK Manager which isnt exactly an install.
Among our TF700 Forums/Fora, there have been some people with issues involving the acquisition of the legendary root. It seems that though it is simple to get under typical circumstances, it is possible to encounter atypical difficulty for whatever the reason. I will try to gather information from the problems people have encountered and post possible solutions. Let it be known that I, myself, have not personally encountered these issues nor am I a Master Rooter of the Transformer series. I merely want to collect and present possible solutions so that those with problems will have an easier time of finding things to try and get their Infinity properly rooted.
If you have questions regarding why DebugFS isn't working, I propose you consult the main thread here. If none of these methods work, please start your own thread involving the things you have tried and the issues you are encountering as it will be easier for those much more intelligent than I to assist you with your problems.
Notes:
You do not need an unlocked bootloader to get root access.
Rooting the TF700 does not void your warranty - unlocking the bootloader does. (e.g. Not the same thing)
All commands will be listed in "double quotes" - the quotes should not be typed.
Make sure to always use the most up-to-date version of sparkm3's DebugFS script.
I will be updating this thread as I come across more problems / solutions.
DebugFS doesn't complete:
Make sure that ASUS Sync is disabled in Settings -> Accounts & Sync
Make sure Unknown Sources is enabled under Settings -> Security (under Device Administration)
Make sure USB Debugging is enabled under Settings -> Developer Options
Make sure you have installed the drivers (you can download the drivers from sparkym3's OP)
-It should show up in Windows Device Manager as an adb composite device
Make sure your computer can see the device (use adb from within the DebugFS package and type in "adb devices" - a list should show up with your device in the list)
Make sure that ASUS Sync is uninstalled from your PC
Try a different computer
When DebugFS does complete, you should be able to open up Terminal Emulator, type in "su" and your prompt should turn from "$" to "#". Alternatively, you should be able to do the same thing via adb ("adb shell" then "su").
DebugFS does complete but still can't get root:
Try to run the SuperUser application
Try to uninstall and reinstall SuperUser
Try to run the SuperUser Update Fixer (thanks to okantomi)
If all else fails, you can give this a try. (thanks to d14b0ll0s)
Hopefully, this list will eventually help someone.
Thanks for this, well done (I'm going to add a link to this in my tweaks how-to if that's ok).
I believe you could add this one to the list.
Just received my champagne today fully updated .26, got root, busybox, and titanium back up with no problems... New to all this but had no problems getting rooted. Love the infinity (C7) so far GPS works,no light bleeds, good wifi, pretty smooth, hopefully the future updates wont screw my tablet and unlike the 4 primes I had when when it first came out defect after defect. Looks like this one maybe a keeper.
d14b0ll0s said:
Thanks for this, well done (I'm going to add a link to this in my tweaks how-to if that's ok).
I believe you could add this one to the list.
Click to expand...
Click to collapse
You can link to this thread if you believe that it will be helpful for others to read over. Any sort of suggestions of what you think would be easier to follow or details I should provide are welcome.
Also, I read over that post you noted and I have a question about that. The post mentions changing "adb wait-for-device" and suggests that it could be changed to "pause". Reading over the batch file though, it seems that sparky uses both "pause <CON" and "@pause <CON" so it makes me believe that perhaps one of those would be more appropriate. What do you think? or should I be directing this question to sparky?
Edit: I placed a request for the information in the main DebugFS thread.
I believe wait-for-device is more appropriate for a script, while pause is better for manual adb management (just imagine what happens).
d14b0ll0s said:
I believe wait-for-device is more appropriate for a script, while pause is better for manual adb management (just imagine what happens).
Click to expand...
Click to collapse
My question was whether when modifying the batch file if the person should be using "pause" or "pause <CON" as mentioned in burningcf's post
(Copy & Vomited from post)
Alternatively, if you don't feel comfortable with executing the adb actions by hand, you might want to just replace all occurrences of
Code:
adb wait-for-device
with
Code:
pause
(or something like that.)
(/Vomit)
which may be something to try before actually going for a line-by-line manual execution.
Perhaps I should just add a link to the post itself but I'm worried that it might go over some people's heads as to what is going on there. Well, let's see if I can get some more background from sparky and then I'll include what I can.
d14b0ll0s said:
Thanks for this, well done (I'm going to add a link to this in my tweaks how-to if that's ok).
I believe you could add this one to the list.
Click to expand...
Click to collapse
If you would like to update this post you linked to, I update the tool a few days ago to include pauses along with the wait-for-device calls. I removed the pointless lines that got left in there, and I am using a better way to determine su access. Finally, I updated it to kill asus sync if it is running.
The new version that should have all the fixes is v2.2
---------- Post added at 01:36 AM ---------- Previous post was at 01:33 AM ----------
alienedd said:
My question was whether when modifying the batch file if the person should be using "pause" or "pause <CON" as mentioned in burningcf's post
(Copy & Vomited from post)
Alternatively, if you don't feel comfortable with executing the adb actions by hand, you might want to just replace all occurrences of
Code:
adb wait-for-device
with
Code:
pause
(or something like that.)
(/Vomit)
which may be something to try before actually going for a line-by-line manual execution.
Perhaps I should just add a link to the post itself but I'm worried that it might go over some people's heads as to what is going on there. Well, let's see if I can get some more background from sparky and then I'll include what I can.
Click to expand...
Click to collapse
I responded to your post in the other thread, but I will copy it here as well, for easy reading.
There should be no difference between the pause that starts with @ and the one that doesn't (as far as this is concerned), I don't know how both got in there.
The reason that I added <CON to the end was because the script was ignoring the pauses and just continuing anyway (because it already had input stored in the buffer). The <CON just insures that the input is coming from the console (user) instead of some other buffer.
sparkym3 said:
I responded to your post in the other thread, but I will copy it here as well, for easy reading.
There should be no difference between the pause that starts with @ and the one that doesn't (as far as this is concerned), I don't know how both got in there.
The reason that I added <CON to the end was because the script was ignoring the pauses and just continuing anyway (because it already had input stored in the buffer). The <CON just insures that the input is coming from the console (user) instead of some other buffer.
Click to expand...
Click to collapse
Thanks for the explanation in feedback in both threads. Much appreciated it.
Added d14b0ll0s's link to post for "last resort" situations.
alienedd said:
My question was whether when modifying the batch file if the person should be using "pause" or "pause <CON" as mentioned in burningcf's post
Perhaps I should just add a link to the post itself but I'm worried that it might go over some people's heads as to what is going on there. Well, let's see if I can get some more background from sparky and then I'll include what I can.
Click to expand...
Click to collapse
Sorry for reading your post neglectfully, I was sleepy already but I believe sparkym3 responded to it now.
sparkym3 said:
If you would like to update this post you linked to, I update the tool a few days ago to include pauses along with the wait-for-device calls. I removed the pointless lines that got left in there, and I am using a better way to determine su access. Finally, I updated it to kill asus sync if it is running.
The new version that should have all the fixes is v2.2
Click to expand...
Click to collapse
Good job, thanks for this! I will update the rooting part in the tweaks thread.
And I believe there is no reason to add the pause solution here now or just you could mention it's obsolete.
Great post > thanks .... but ......
alienedd said:
Among our TF700 Forums/Fora,.......
If you have questions regarding why DebugFS isn't working, I propose you consult the main thread here. If none of these methods work, please start your own thread involving the things you have tried and the issues you are encountering as it will be easier for those much more intelligent than I to assist you with your problems.
Notes:
You do not need an unlocked bootloader to get root access.
All commands will be listed in "double quotes" - the quotes should not be typed.
Make sure to always use the most up-to-date version of sparkm3's DebugFS script.
I will be updating this thread as I come across more problems / solutions.
DebugFS doesn't complete:
Make sure that ASUS Sync is disabled in Settings -> Accounts & Sync
Make sure Unknown Sources is enabled under Settings -> Security (under Device Administration)
Make sure USB Debugging is enabled under Settings -> Developer Options
Make sure you have installed the drivers (you can download the drivers from sparkym3's OP)
-It should show up in Windows Device Manager as an adb composite device
Make sure your computer can see the device (use adb from within the DebugFS package and type in "adb devices" - a list should show up with your device in the list)
Make sure that ASUS Sync is uninstalled from your PC
Try a different computer
When DebugFS does complete, you should be able to open up Terminal Emulator, type in "su" and your prompt should turn from "$" to "#". Alternatively, you should be able to do the same thing via adb ("adb shell" then "su").
DebugFS does complete but still can't get root:
Try to run the SuperUser application
Try to uninstall and reinstall SuperUser
Try to run the SuperUser Update Fixer (thanks to okantomi)
If all else fails, you can give this a try. (thanks to d14b0ll0s)
Hopefully, this list will eventually help someone.
Click to expand...
Click to collapse
>> sorry if I am missing something >>> pls forgive as am very very NEW TO this " rooting" process
AND am still trying to GET MY TF700 from this crazy 'bay plac e !!!
so my question(s) is...
a) what hardware I need? or Does the transfermer (TF700) come with a USB cable to connect to PC
b) if not ; where can I get one of these ordered > so am ready when i get mine.
c) from what I read @ asus website > doing ROOT and UNLOCKING = voids warranty!! true ??
thanks in advance for answers
Debbie1759 said:
>> sorry if I am missing something >>> pls forgive as am very very NEW TO this " rooting" process
AND am still trying to GET MY TF700 from this crazy 'bay plac e !!!
so my question(s) is...
a) what hardware I need? or Does the transfermer (TF700) come with a USB cable to connect to PC
b) if not ; where can I get one of these ordered > so am ready when i get mine.
c) from what I read @ asus website > doing ROOT and UNLOCKING = voids warranty!! true ??
thanks in advance for answers
Click to expand...
Click to collapse
A) It comes with it
B) no need
C) Rooting does not void warranty but Unlocking will void your warranty.
Sent from my ASUS Transformer Pad TF700T using XDA Premium App
After deleting asus sync, then reisntalling superuser from the market did the trick thanks!
Thanks
jjdevega said:
A) It comes with it
B) no need
C) Rooting does not void warranty but Unlocking will void your warranty.
Sent from my ASUS Transformer Pad TF700T using XDA Premium App
Click to expand...
Click to collapse
Thanks for info..
> looking forward to grabbin this bad boy and ridin him to ROOT ! :angel:
d14b0ll0s said:
Thanks for this, well done (I'm going to add a link to this in my tweaks how-to if that's ok).
I believe you could add this one to the list.
Click to expand...
Click to collapse
having trouble getting rooted and tried your link, everything went fine, it even shows the uid and gid as = 0, but i still dont have root when i boot up and run root checker or superuser to update binaries. starting to look like i might have to go back to stock recovery and do a fresh install of firmware. I have even flashed TWRP through fastboot and installed a rooted rom (Zues v4) and still had no root. Really at a loss for what to do next.
Somehting that might help
alienedd said:
DebugFS does complete but still can't get root:
Try to run the SuperUser application
Try to uninstall and reinstall SuperUser
Try to run the SuperUser Update Fixer (thanks to okantomi)
If all else fails, you can give this a try. (thanks to d14b0ll0s)
Hopefully, this list will eventually help someone.
Click to expand...
Click to collapse
Thanks very much for all your guide, I have always use XDA forums and learn alot about android devices. I want to tell you that yesterday I try to root my TF700 like 10 times and in 3 different computers! I follow all the steps and eveything but I wasn't able to Root it. But in my last try.. I went to setting and in USB Debugging (it was enable) I disable it and enable it again, and then try with the Debug and it finally WORK :laugh:
So well maybe this will help someone that could be in my situation.
Sorry for my bad english.
I give up. I tried DebugFS, and that didn't work completely. Superuser seemed to be working but Busybox installer & TiBu didn't see root. I tried the manual commands in this thread and it's still not working. Screw this. Everyone that posted help threads on rooting & unlocking & etc. has done fabulous work, including this thread. But I'm just destined to live a rootless life.
*I have no interest in installing a custom ROM till JB is pushed out and I know the ROMs are reliable. I don't want to have to deal with so many bugs.
das0527 said:
I give up. I tried DebugFS, and that didn't work completely. Superuser seemed to be working but Busybox installer & TiBu didn't see root. I tried the manual commands in this thread and it's still not working. Screw this. Everyone that posted help threads on rooting & unlocking & etc. has done fabulous work, including this thread. But I'm just destined to live a rootless life.
*I have no interest in installing a custom ROM till JB is pushed out and I know the ROMs are reliable. I don't want to have to deal with so many bugs.
Click to expand...
Click to collapse
I was in the same boat. I finally installed Black Bean rom which is JB based and it gave me root. The development seems to have tripled just in
Sent from my ICS Razr
---------- Post added at 11:36 AM ---------- Previous post was at 11:25 AM ----------
I was in the exact same boat. Installing Baked Black Bean rom gave me root. I understand your concern with JB roms, however, there are only 2 bugs I have experienced-no GPS and portrait mode. Although they sound like big issues they really aren't. Any game or app I use that runs in portrait only mode works fine. Also I have seen 3 to 4 roms drop in the last 2 days. It will not be long until the devs fix all issues. This is a popoular device among Apple haters and I foresee a lot of really good stuff coming for this tablet. Just try out a JB rom and see how you like it...you can always go back. Hope this helps...I was just as frustrated as you.
Sent from my ICS Razr
Will, thank you for the advice. However, until the custom ROMs become more stable - or until JB is pushed out officially - I'm very wary of unlocking & flashing a custom ROM.
das0527 said:
Will, thank you for the advice. However, until the custom ROMs become more stable - or until JB is pushed out officially - I'm very wary of unlocking & flashing a custom ROM.
Click to expand...
Click to collapse
This is how i kind of feel to. My galaxy nexus feeds all my flashing needs.
worked for me
das0527 said:
I give up. I tried DebugFS, and that didn't work completely. Superuser seemed to be working but Busybox installer & TiBu didn't see root. I tried the manual commands in this thread and it's still not working. Screw this. Everyone that posted help threads on rooting & unlocking & etc. has done fabulous work, including this thread. But I'm just destined to live a rootless life.
*I have no interest in installing a custom ROM till JB is pushed out and I know the ROMs are reliable. I don't want to have to deal with so many bugs.
Click to expand...
Click to collapse
>> am still using Virgin TF700..(recovered from FACTORY BACKUP) but did try the ROOT...using the "DebugFS" method..
and it works >>>>> MUST REMEMBER to stop/switch off this apps = ASUS SYNC..... that is something that got me @ first try..
DOH! than I realised .. and once turned off = worked like a charm !!!
just my 0.02c worth !
Right....So your main issue is “device not found in ADB and/or Fastboot”
Adb commands only work when you're booted in the rom or recovery***** Fastboot commands only work when youre in bootloader
Here is a few simple things you can try:
*Try a different recovery.
*Try a different usb data cable.
*Try a different computer.
and this ..a little more time consuming..
*Try this http://forum.xda-developers.com/showthread.php?t=2588979 (obviously delete previous adb/htc sync/drivers etc)
If running windows 8 or above there is a fix in the above link...just read!
*Revert back to windows 7.
*Download “Ubuntu” and run on a livecd (https://help.ubuntu.com/community/LiveCD) then connect phone and do what you have to do.
*last resort look into things like this : https://play.google.com/store/apps/d....wifiadb&hl=en
***If anyone has another solution that works i will update the above****
Cheers
Error 404: Page not found...for the first link
Thanks....updated link
Thanks for this,some seem a bit obvious to try BUT trying another data cable,really?
What about manually updating drivers? I think that should be included.Ta
MommaSmith said:
Thanks for this,some seem a bit obvious to try BUT trying another data cable,really?
What about manually updating drivers? I think that should be included.Ta
Click to expand...
Click to collapse
Yeah, some are obvious! These are plastered All over XDA and can be found with a quick "search" but a majority of members dunno how to search, so i put what i found in one place.
Trying a different data cable is an ACTUAL thing! i had problems a while back with my s3 not being recognized by PC when using Odin, changing data cable fixed it!
Im pretty sure the link to "15 second ADB installer" automatically updates to the mos trecent drivers anyway? i'll check and if it doesn't i will add that on OP.
cheers
Thanks. Hahah Yes some folks don't know how to read, I spent almost a week reading up before I attempted doing anything with my mini and had no problems Installing InsertCoin. I've now changed to PAcman as it uses less space.thank you again
Worked great THANKS. Tried other methods this is the only one that worked.