I've been told that clockwork isnt currently working to do this, so...
http://dl.dropbox.com/u/2056318/update-template/bstats.zip
Install via clockwork.
Now you can run it via adb, OR terminal emulator in Android. Keep in mind it requires superuser permissions.
What exactly am I running? I installed, does installing wipe stats?
Sent from my SCH-I500 using XDA App
Zacisblack said:
What exactly am I running? I installed, does installing wipe stats?
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
running that deletes batt stats.. its not installing a program or anything.
thank you, kind sir.
So every time we wanna wipe the battery stats we just run this?
Sweet
What exactly does wiping the battery stats accomplish?
Sent from my SCH-I500 using XDA App
As explained in this thread http://forum.xda-developers.com/showthread.php?t=957132, some think that it helps with battery life. Thanks for creating this (and everything else!), adrynalyne.
I had horrible battery life when I first flashed EB01. I have sinced wiped and gave a full charge with the phone not booted and I have seen 100% if not more improvement. Does this do anything different than wiping battery stats in CWM?
teeharding said:
I had horrible battery life when I first flashed EB01. I have sinced wiped and gave a full charge with the phone not booted and I have seen 100% if not more improvement. Does this do anything different than wiping battery stats in CWM?
Click to expand...
Click to collapse
Wiping the battery stats doesn't seem to be working with CWM for EB01.
Says error line 3 when I try to install this using Red CRW.
kaus said:
Says error line 3 when I try to install this using Red CRW.
Click to expand...
Click to collapse
Is there any reason not to simply open a root-friendly file explorer and delete batterystats.bin? After recent experiences, I'm not terribly inclined to trust Clockworkmod with anything when an easy alternative is available.
Another Fascinating post by my XDA app...
I used the script. Open the .zip in astro and look for the script. Copy it and run it in terminal, it will reboot your phone and hopefully wipe the stats. My phone read 65% before I wiped the stats with the script and after, it read 74%. So I'm hoping that it worked correctly. Lol
Sent from my cellphone.
YAY! I have been having battery problems since I flashed EB01. I tried the normal wipe and relearn tricks I've been using, with no luck. My battery died in 6 hours yesterday, with 1 3 minute phone call. So I charged the phone overnight, tried this script, and after 6 hours of moderate use I'm at 85%.
Thanks Adrynalyne, for making me like my phone again.
just did this as a trial and error to learn a little more how to use terminal. =)
i missed out on the adb tutorial on irc a few months back... soo....
figuring it out the hard way.
I'm still a bit confused with this. Do we either
1. Install via CWM red when we want our stats wiped? or
2. Install via CWM red, then use terminal emulator or adb to run the script? or
3. Something else entirely that I am not smart enough to think of?
Thanks adrynalyne for all you do!
hazenberger said:
I'm still a bit confused with this. Do we either
1. Install via CWM red when we want our stats wiped? or
2. Install via CWM red, then use terminal emulator or adb to run the script? or
3. Something else entirely that I am not smart enough to think of?
Thanks adrynalyne for all you do!
Click to expand...
Click to collapse
No. 2
10 char
Thanks. Quick follow up. How do I run the script using terminal emulator? Thanks
Sent from my SCH-I500 using XDA App
ok, i had to first download it to my phone.
go into astro,
find "download folder"
open said folder
find batt stat file
open it, look for system
ultimately you need to find the file labeled with the name "script". but you cannot "open" it. you long press on that file and then open it in in text editor.
then you delete the first two characters which is the #!. then long press that page, select all, copy.
press your home key at the bottom of the phone,
open up your terminal emulator app (which if you are embarking on this, you should have downloaded long ago from the app store)
type "su" from the $ prompt. it should then give you su access and you will see the # prompt.
long press the screen again, and select "paste".
this will autorun and restart your phone. if it doesn't restart, you did something wrong.
bear in mind, i am not a genius, and i have almost ZERO knowledge of development or how to use adb, and i figured it out on my own in about 20 minutes.
so you can do this. plus, if you do something wrong, "most" of the time the worst that will happen is nothing. the adb shell in the terminal only responds to very specific text commands. so don't be too scared.
helpful?
Perfect (except you typed copy when you meant paste ;-> ) the phone reset itself. Now to see if there is any difference in batt life.
Sent from my SCH-I500 using XDA App
upsidedownaaron said:
ok, i had to first download it to my phone.
go into astro,
find "download folder"
open said folder
find batt stat file
open it, look for system
ultimately you need to find the file labeled with the name "script". but you cannot "open" it. you long press on that file and then open it in in text editor.
then you delete the first two characters which is the #!. then long press that page, select all, copy.
press your home key at the bottom of the phone,
open up your terminal emulator app (which if you are embarking on this, you should have downloaded long ago from the app store)
type "su" from the $ prompt. it should then give you su access and you will see the # prompt.
long press the screen again, and select "copy".
this will autorun and restart your phone. if it doesn't restart, you did something wrong.
bear in mind, i am not a genius, and i have almost ZERO knowledge of development or how to use adb, and i figured it out on my own in about 20 minutes.
so you can do this. plus, if you do something wrong, "most" of the time the worst that will happen is nothing. the adb shell in the terminal only responds to very specific text commands. so don't be too scared.
helpful?
Click to expand...
Click to collapse
Thanks for the detailed instructions, upsidedownaaron. I found them helpful. However, near the bottom of your instructions you say to "copy" from inside Terminal Emulator. I'm pretty sure that you meant to "paste" the script that you previously copied.
oops, retard moment fixed. =)
edited to say "paste".
i most likely missed that due to eating paste.
Related
EDIT: DEAD. Unlock you bootloader and get perm root.
It still uses zergrush and absolutely does not provide any other capability than other temp roots. (Although some people have reported root apps see root better so it might actually be better). The only difference is I have the things relating to root (ie su,busybox, etc) stored in a ramdisk that lasts alot longer than things "written" or linked to /system. This is because we still have /system write locked so when we write things to it (like the original zergrush implementation) it gets forgotten after while.
Your mileage may vary. I am obviously not responsible for bricks, data loss, etc if you use this. I and others have used it for about a week and it has been fine.
To use:
0) Make sure superuser isn't installed
1) Reboot phone (full reboot), make sure usb debugging is on.
2) Plug in phone in charge only mode to PC.
3) Kill everything in the built in task manager, then go back to the rosie home screen.
4) Extract zip and doubleclick temproot.bat
5) There is a 20 second time out at the beginning just in case you forgot to plug in your phone, etc so you have time to cancel the process before it starts. To skip it just hit enter on the keyboard or wait the 20 seconds.
6) Hit the thanks button (bottom left of this post) if you like it!
Let me know if you like it better or if something bad happens so I can take it down. Lets hope we get S-Off soon and don't have to deal with this temp root **** anymore.
Troubleshooting:
1) Bootlooping? Pull the battery. If you still are boot looping, an RUU restore may be necessary. I believe this has only happened to one user and it was likely a result of something that was done AFTER root and not directly caused by this program.
2) Just not working? Reboot both your PC and Phone. If ADB cannot see your phone, it is not a fault of the program. If you haven't gotten other temp root methods to work, it is likely this one won't either.
3) If you want bluetooth to work while you are rooted, turn it on before running this app. It won't toggle on for some reason after the program is run.
Finally, if you want to contribute, thank the Revolutionary team for their work on the zergRush exploit!
ok so let me be the first to ask.... what's "better" about it?
It should stick longer.
has anyone figured out exactly why we lose root within minutes?
So every time we want to use this root again we'll have to uninstall SU first?
You can probably run without but I have always removed it first
ya it worked perfectly thanxs
You have to have drivers installers and such before you do this method? Thing is ny computer broke so I would be using a school computer which restricts me from downloading htc drivers
Sent from my ADR6425LVW using xda premium
The root access is definitely better. I have root access apps that would force reboot my phone before that actually run now. Nice work! It definitely sticks longer.
bast525 said:
has anyone figured out exactly why we lose root within minutes?
Click to expand...
Click to collapse
Since we don't have write access to /system. When the superuser stuff gets "written" to /system it really isn't so it goes away randomly after awhile. This helps to prolong the life of superuser.
NoNotReally said:
So every time we want to use this root again we'll have to uninstall SU first?
Click to expand...
Click to collapse
I am not sure... Try it. If you do I can have the script uninstall before it runs perhaps.
bokechukwu1 said:
You have to have drivers installers and such before you do this method? Thing is ny computer broke so I would be using a school computer which restricts me from downloading htc drivers
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
Yes this just is what I think is a better root method. It is the same exploit, it is just stored on the device a bit differently.
mohkg said:
ya it worked perfectly thanxs
Click to expand...
Click to collapse
Good to hear.
flexor224 said:
The root access is definitely better. I have root access apps that would force reboot my phone before that actually run now. Nice work! It definitely sticks longer.
Click to expand...
Click to collapse
Also good to hear.
It has worked to control setcpu profiles for me very well over the past few days so it has stuck for about 72 hours+ for me before I rebooted to retest this script before release.
confirmed, this root is definitely working better. not only lasting longer, but some apps that require root that wouldn't work or wouldn't work fully before are now working. for instance, I have an sql database editor app that was not recognizing root before and wouldn't let me edit databases. works perfectly now. I want to try WiFi tether but do we know if Verizon can detect this now?
also, I'm guessing you're setting some low clock speed with setcpu when asleep/idle... noticing better battery?
Thank you! This works amazingly well. My root actually sticks this time. It doesnt give me a single issue.
Thank you once again!
I have run this script several times now and no worky.
- Installed drivers (no old drivers to conflict)
- fresh reboot, charge only, USB debug, tasks are terminated
- adb sees my device
SU does push to the phone, but apps like TB cannot get root access. Any thoughts folks? I have tried ever one of these temp root methods without success.
plug in your phone for me. Then shift+click on the folder that you extracted the stuff to and do open command prompt here or whatever. Then in there type adb shell and see if you get a shell.
It is likely if you haven't gotten success before this won't help. This is just and improved root, but not an improved way to get it on the device.
con247 said:
plug in your phone for me. Then shift+click on the folder that you extracted the stuff to and do open command prompt here or whatever. Then in there type adb shell and see if you get a shell.
It is likely if you haven't gotten success before this won't help. This is just and improved root, but not an improved way to get it on the device.
Click to expand...
Click to collapse
I have shell con.
My root held overnight. I was able to clear battery stats using Battery Monitor Widget (other temp roots could not), and using CPU Boost to underclock and run a screen off profile.... unfortunately I'm not really noticing any better battery.
Irieone said:
I have run this script several times now and no worky.
- Installed drivers (no old drivers to conflict)
- fresh reboot, charge only, USB debug, tasks are terminated
- adb sees my device
SU does push to the phone, but apps like TB cannot get root access. Any thoughts folks? I have tried ever one of these temp root methods without success.
Click to expand...
Click to collapse
Adb can see your device but still doesn't work..... Post the output from an adb command and maybe we can help.
Sent from my HTC Rezound via the XDA app
Definitely the best temp root method so far!
Already past 24hrs! Past methods would last an hour or so. This is awesome. How did you figure this out? Maybe it'll help those trying to get S-Off? Thanks!
It won't help with perma-root/s-off. I figured a ramdisk wouldn't get killed nearly as fast as the fake /system write does.
I am able to get it to run through now. At the end it tells me it needs to reboot my phone, enjoy root, etc... When the phone reboots. It boot-loops. I have to pull battery.
Not too sure if this belongs in Q and A... But I have a Titanium Backup folder copy on my PC. Well, when I try to delete the folder it causes the program to "not respond". So I bring up task manager and "end task". It then closes everything on my PC, and all the desktop icons disappear. There's nothing other then the wallpaper. Only thing that still works is task manager. Restart PC, try again. Same thing. Happens when I put the folder in recycle bin, or by deleting just some of the folder contents. I did some spring cleaning on the PC today, and this is the only problem I've had and its consistant, and specific to this folder. Any ideas on how to delete it?
Use Astro/file explorer/Root broswer to delete it from your device.
That would probably work to get it off my phone, but the problem is on my PC. when I was in newb stages I had a backup of a backup on my PC. It's just this one TB Backup file on my PC that is causing problems and wont delete.
You could move all the files to a folder except the TB Backup and just format the sd card. that could help.
Virus scan your pc, if you haven't already. Or boot into safe mode and that should allow you to delete the file. Or you could do a system restore.
Root-Hack_Mod*Always\
laie1472 said:
Virus scan your pc, if you haven't already. Or boot into safe mode and that should allow you to delete the file. Or you could do a system restore.
Click to expand...
Click to collapse
Yeah, did a scan and it didn't pick anything up. But I had a hell of a trojan about a month ago and I was thinking it could possibly have to do with that. Although I did a very deep clean. I will give safe mode a shot. I got the PC from my parents with a bunch of virus/trojan issues only a few months ago, and because of all the cleaning and the other trojan I got....I'm not too positive a system restore will be good. I was going to create a new restore today since all has been great....until this.
Ok sounds like some spyware or malware. As said before boot into SAFE MODE, but select the SAFE MODE WITH NETWORKING. Go to http://www.superantispyware.com/ download the free version. Install it, then run superanti spyware. Select to do a COMPLETE SCAN not quick scan. On the next screen select HIGH BOOST and scan inside of ZIP files, which will use most of your cpu it will run about 80% just let it run because it will slow down anything else you try to do. After it is done get rid of the bad files, tracking cookies and/or any trojans left. Reboot the computer, but into safe mode with networking again. Then go to http://www.malwarebytes.org/ and download the free version and install. Run the complete scan in malwarebytes. Let that run and when it finishes is will ask for a reboot. Reboot, again and you should be good to go. I have seen this on teachers computers at least weekly, because of the stupid Ransom WARE. If that doesn't work than my last suggestion would be download combofix from bleepingcomputer and run that. Hope this helps a lil
gokart2 said:
Yeah, did a scan and it didn't pick anything up. But I had a hell of a trojan about a month ago and I was thinking it could possibly have to do with that. Although I did a very deep clean. I will give safe mode a shot. I got the PC from my parents with a bunch of virus/trojan issues only a few months ago, and because of all the cleaning and the other trojan I got....I'm not too positive a system restore will be good. I was going to create a new restore today since all has been great....until this.
Click to expand...
Click to collapse
Let me know if the safe mode works.
Root-Hack_Mod*Always\
dont forget to check the permissions of the folder itself tooif windows doesnt let you find them and you have two new choices so keep us all posted
mikejones13 said:
Ok sounds like some spyware or malware. As said before boot into SAFE MODE, but select the SAFE MODE WITH NETWORKING. Go to http://www.superantispyware.com/ download the free version. Install it, then run superanti spyware. Select to do a COMPLETE SCAN not quick scan. On the next screen select HIGH BOOST and scan inside of ZIP files, which will use most of your cpu it will run about 80% just let it run because it will slow down anything else you try to do. After it is done get rid of the bad files, tracking cookies and/or any trojans left. Reboot the computer, but into safe mode with networking again. Then go to http://www.malwarebytes.org/ and download the free version and install. Run the complete scan in malwarebytes. Let that run and when it finishes is will ask for a reboot. Reboot, again and you should be good to go. I have seen this on teachers computers at least weekly, because of the stupid Ransom WARE. If that doesn't work than my last suggestion would be download combofix from bleepingcomputer and run that. Hope this helps a lil
Click to expand...
Click to collapse
Yeah, I did something like this in order to get the last trojan off. I tried/have a million virus/anti-malware programs, of course only one active now which is the malwarebytes one. The trojan I had was a Win32/Sirefef one, can't remember specifically which one. But I did have to do a combo fix and I continued to check for about a week after....all was good.
laie1472 said:
Let me know if the safe mode works.
Click to expand...
Click to collapse
Will do.
wloftus said:
dont forget to check the permissions of the folder itself too if windows doesnt let you find them and you have two new choices so keep us all posted
Click to expand...
Click to collapse
I didn't check the actual permissions, will do that too.
Thank you all for the ideas/help. Much appreciated! Won't be back to the PC until tomorrow, will let you know what I find.
Update... Ran multiple virus scans and nothing showed up on any of them. Tried deleting folder in safe mode, but it still froze up without any icons. Still did the same if I tried erasing only one of the files in the TB folder itself. Permissions were set normal, as other files that I erased with no issues. Ended up erasing all my other phone backups (twrp, etc...) that were in the "BACKUPS" folder, the same folder the TB folder was in. Then I erased the "BACKUPS" folder itself with the TB one in it, and that seemed to do it. Definetly weird, but at least I got it deleted.
Your asking I. The wrong place buddy. This is for EVO 3d questions.
Have you tried to even search about it.
Sent from my PG86100 using Tapatalk
gokart2 said:
Update... Ran multiple virus scans and nothing showed up on any of them. Tried deleting folder in safe mode, but it still froze up without any icons. Still did the same if I tried erasing only one of the files in the TB folder itself. Permissions were set normal, as other files that I erased with no issues. Ended up erasing all my other phone backups (twrp, etc...) that were in the "BACKUPS" folder, the same folder the TB folder was in. Then I erased the "BACKUPS" folder itself with the TB one in it, and that seemed to do it. Definetly weird, but at least I got it deleted.
Click to expand...
Click to collapse
what you need to do to avoid all this is just download any linux live version... i personally use hirens boot cd 15... once downloaded take the image and either burn it do a cd or use a linux installer... i use pendrivelinux load that up and let it install your boot cd to your usb thumb drive....once that is completed reboot your computer and as it reboots have it load the usb drive first once that loads up you then can boot into partition magic and use linux's permissions and rights to over take windows permissions does that all automatically.... from there you right click and delete....need help or info feel free to pm me
iTzLOLtrain said:
Your asking I. The wrong place buddy. This is for EVO 3d questions.
Have you tried to even search about it.
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
I'm asking in the wrong place...is that what u meant? Read from the original post. If it was that far out of the wrong place, it would more then likely have been moved by now. I always search, and search for awhile before posting. It seemed somewhat relative to me do to the fact the file came from my evo3d, and is a file made by an android app everyone rooted uses. I was also aked yo give an update on the problem.
wloftus said:
what you need to do to avoid all this is just download any linux live version... i personally use hirens boot cd 15... once downloaded take the image and either burn it do a cd or use a linux installer... i use pendrivelinux load that up and let it install your boot cd to your usb thumb drive....once that is completed reboot your computer and as it reboots have it load the usb drive first once that loads up you then can boot into partition magic and use linux's permissions and rights to over take windows permissions does that all automatically.... from there you right click and delete....need help or info feel free to pm me
Click to expand...
Click to collapse
Thanks, this was originally what I was after...but in a windows software program. BUT....I will more then likely do this anyway. Slowly working the noob out...but there's SOOOOOOOOO much to learn (still), I feel overloaded sometimes. I'm in the process of downgrading hboot on the 3d, and downgrading iOS and performing a jailbreak on my old 3g so the boss and kids stop whining at how slow it is and why there's still a phone button on it...lol.
gokart2 said:
I'm asking in the wrong place...is that what u meant? Read from the original post. If it was that far out of the wrong place, it would more then likely have been moved by now. I always search, and search for awhile before posting. It seemed somewhat relative to me do to the fact the file came from my evo3d, and is a file made by an android app everyone rooted uses. I was also aked yo give an update on the problem.
Click to expand...
Click to collapse
Have you even tried formating the sdcard?
Sent from my PG86100 using Tapatalk
Ohhhhh boy.
gokart2 said:
Ohhhhh boy.
Click to expand...
Click to collapse
is this a good ohhhhh boy?
Welp, after spending over 26 honest-to-God hours researching a "cure" for this, I am still without a solution. I hope a kind soul will be able to guide me to the light, because I have been unable to find it on my own.
I am going to try to be as through as possible, if for nothing else than doing a mental checklist to see if I missed some obvious step along the journey. Also, maybe a keen observer will be able to spot what I'm doing wrong.
So,
My Asus Prime is bricked. I'm stuck on scenario 3 (according to this post:http://forum.xda-developers.com/showthread.php?t=1514088&)
In chronological order, here's what happened:
1. I'm running Virtuous Prime 1.0
2. I flash ClockworkMod Recovery Touch v5.8.1.8
3. I rebooted into recovery and wiped data/factory reset, cache, dalvik cache
4. I performed a backup of my old ROM
5. I flashed a new ROM, then hit 'reboot system now'
6. I'm stuck at the Asus logo screen; Android won't boot.
I am able to access recovery and activate Fastboot mode; definitely scenario 3.
Then, also in chronological order:
1. I restarted the tablet, pressed the up volume key and accessed the other menu with 3 options
2. I hit the 'wipe data' option
3. Try to boot Android
4. Still stuck at the 3 option screen
From what I read, this situation is likely the result of clockworkMod Recovery flashing a bad kernel. Supposedly, it can fixed by flashing a 'good' kernel via fastboot, which requires both a "stock kernel" and a more recent clockwork mod recovery image.
I downloaded the SDK package and downloaded pretty much everything, including the USB drivers. I downloaded a stock kernel called stock_9.4.2.21_kernel-signed and a CWM recovery image and placed them inside the "tools" folder.
I opened a command window and while having the tablet plugged in, typed 'adb devices'. I get 'List of devices attached' but then a blank space.
Here's what happened next:
1. I re-plugged in the tablet in Recovery mode to my AMD X64 Windows 7 PC and got an "USB device not recognized" message.
2. I went to Device Manager and under "Universal serial bus controllers" I see a yellow triangle mark besides an "unknown device" option.
3. Right click on "unknown device" and try to update the drivers manually using the Universal_Naked_Driver_Beta_0.6.1
4. When I select the folder in which the drivers are located Windows gives me a message of "the best driver software for your device is already installed". Back to step 3.
5. I try "let me pick from a list of device drivers on my computer" and hit "have disk option"
6. Upon choosing the android_apxusb file inside the universal naked drivers folder, I get the following error: "the folder you specified doesn't contain a compatible software driver for your device (...) make sure it is designed to work with Windows for x64-based systems."
7. Try again this time choosing file android_apxusb; same error.
I heard that some Windows 7 x64 users are having issues installing drivers; that may be my case too. I, however, don't have access to any other Window or Macs or Linux PCs in my house. Still, if this is the issue, then I might try redoing things in a different PC at a friend's house or something.
Bottom line? I think I know what to do, but I can't install the universal naked (nor the official Asus Prime) drivers. What now? Is there an easy fix for Brick scenario 3?
I have read God knows how many discussions on the subject, but I haven't been able to find a solution to my issue. I got no support from Freenode #asus-transformer; some ops were even downright rude. Any help is greatly appreciated.
For what is worth, I'll be donating $50 to whoever is able to help me navigate through this issue and get my tablet back and running.
Thanks again for reading this far.
TL;DR: I bricked my Prime and I'm stuck in scenario 3. I will donate $50 dollars to whoever can help me unbrick it.
Hey,
try to get a Live CD like Ubuntu.
Get the Linux files from the ViperMOD thread. It includes the "adb" executable.
Try to get ADB running there.
Go to the freenode IRC Channel "#asus-transformer" on Freenode (http://webchat.freenode.net/?channels=asus-transformer) and ask for help like described in the unbrick thread!
Greetz
Edit: No need for donate!
hanzo001 said:
3. I rebooted into recovery and wiped data/factory reset, cache, dalvik cache
4. I performed a backup of my old ROM
Click to expand...
Click to collapse
In that order? So you backed up an empty rom?
You don't mention; do you have valid nandroid backup? Can you restore it?
Do you have a rom zip on your device? What happens if you wipe and re-flash?
I would suggest a couple of options.
I notice that you have not once (according to what you have written) formatted /System if you still have a good ROM on your memory card that is flashable I would format all partitions in recovery /System, /Cache, /Staging and /Data then reflash the ROM.
You could also try an advanced restore and flash only the boot image from your nandroid.
Also, I have to agree with chrischdi, there is no need for a bounty for this. Your problem is one of the reasons we are all here in the first place.
Thanks for your answer; I'll answer yours
djmcnz said:
In that order? So you backed up an empty rom?
You don't mention; do you have valid nandroid backup? Can you restore it?
Do you have a rom zip on your device? What happens if you wipe and re-flash?
Click to expand...
Click to collapse
1. Yes, in that order; I backed an empty ROM
2. No, I don't have a valid nandroid backup (go figure; just this single freaking time I forgot to backup before wiping data/cache/dalvik cache)
3. No other ROM on my device. I had a new ROM when I performed the flashing, but when I got to the point where I hit "deleate data" in the 3-option menu, I lost everything on the SD card
4. When I wipe and reflash I'm stuck on the same loop. Maybe flashing a 'good' ROM will fix it; the issue is, my PC doesn't know what I'm plugging in when I connect the tablet to it.
Thank you for your support
Thank you, I'll try a Live CD. I'm downloading now even as we speak.
When that's finished, I'll grab the Linux files.
I guess that sorts of confirms my hypothesis that my main issue is with Windows... *sigh* WINDOWS!
I tried getting help from freenode's #asus-transformer in the past, but... lets say that on the overall my experience could have been better. I'll try again later tonight, where hopefully I'll be able to talk to RaYmAn, a volunteer in the original Diamonback post who is offering supports to users in my specific situation.
By the way, thanks for pointing me with a clickable link to the IRC chat; I've never used IRC before in my life, and getting it to work, dumb as it may sound, took me quite to figure out. Thank you again for your help and support!
chrischdi said:
try to get a Live CD like Ubuntu.
Get the Linux files from the ViperMOD thread. It includes the "adb" executable.
Try to get ADB running there.
Click to expand...
Click to collapse
Thank you for your answer. It is really nice to have a helpful person around; Like I mentioned in my op, my experience on freenodes' #asus-transformer chat was a bit... discouraging. I figured most would want some form of payment for their time, but here you both are, proving that there is kindness in this world.
I'll address your comments:
1. I did wipe /System; after NOTHING I tried on recovery worked, I did manual wiping of everything, trying to boot each time; similar results.
2. I do not have a good ROM on the memory card. Before doing the 'wipe data' from the 3-option menu, re-flashing a good ROM did no good nevertheless. From here is where I started suspecting that it was the fault of CWM not flashing a proper kernel.
3. I tried the advanced restore as well, an like in #1, I tried rebooting each time, just to make sure it would work. But it didn't.
Thank you again for your support. It feels great to know there's someone backing you up out of the goodness of their heart.
Right now I'll try to redo my steps from a Live CD Linux environment; hopefully that'll work. Freaking Windows...
Doktaphex said:
I would suggest a couple of options.
I notice that you have not once (according to what you have written) formatted /System if you still have a good ROM on your memory card that is flashable I would format all partitions in recovery /System, /Cache, /Staging and /Data then reflash the ROM.
You could also try an advanced restore and flash only the boot image from your nandroid.
Also, I have to agree with chrischdi, there is no need for a bounty for this. Your problem is one of the reasons we are all here in the first place.
Click to expand...
Click to collapse
Thank for your support, guys
I just wanted to shout out a big thanks to the great people who have offered me suggestions regarding this issue. I'll re-do my steps this time from inside the Live CD version of Ubuntu later tonight, and I will update.
Best regards,
me
hanzo001 said:
I just wanted to shout out a big thanks to the great people who have offered me suggestions regarding this issue. I'll re-do my steps this time from inside the Live CD version of Ubuntu later tonight, and I will update.
Best regards,
me
Click to expand...
Click to collapse
Hope it works out for the best, life is better with a little Nix in it.
What if you load a rom like aokp onto an external SD then flash that? That flashes everything you would need. Then if you want to back to virtuous you could restore the stock boot img. Im tired and I'm probably not understanding the issue correctly so forgive me if that is indeed the case.
Sent from my MB870 using xda premium
CadenH said:
What if you load a rom like aokp onto an external SD then flash that? That flashes everything you would need. Then if you want to back to virtuous you could restore the stock boot img. Im tired and I'm probably not understanding the issue correctly so forgive me if that is indeed the case.
Sent from my MB870 using xda premium
Click to expand...
Click to collapse
You cannot use an external SDcard with any version of CWM for the Prime.
CadenH said:
What if you load a rom like aokp onto an external SD then flash that? That flashes everything you would need. Then if you want to back to virtuous you could restore the stock boot img. Im tired and I'm probably not understanding the issue correctly so forgive me if that is indeed the case.
Sent from my MB870 using xda premium
Click to expand...
Click to collapse
Thanks for the thought. I tried that too; for some reason, ClockworkMod Recovery won't read the SD card at all!
Linux
[Update]
In general, this could be going better.
I finally got Ubuntu.
I plugged in the tablet while (the tablet is) on recovery mode, and nothing happens.
I was expecting a pop-up menu, or a notification somewhere acknowledging that I connected a device to the PC, but nothing. I'm just going to assume that Linux somehow knows.
I then downloaded the Android SDK for Linux, unziped, and there's no executable file inside. I'm supposed to download the rest of the file via the terminal, apparently, but this one doesn't work like its Windows counterpart either, so I have no clue what to do now.
Jesus...
Bottom line: I'm in Linux, I downloaded the Android SDK, the universal naked drivers and a stock kernel. Now what?
Try to get ADB running in the recovery mode.
In the files of ViperMOD are the executables. Just open up a console / shell and go to the directory via the "cd" command.
Then in the ViperMOD directory execute "sudo ./adb shell" to try the adb connection.
If the adb connection is ok, mount the sdcard via Recovery Menu and then push a file / rom to the sdcard.
For example with the command:
"sudo ./adb push /media/rom.zip /sdcard/"
(I don't know if this are the correct paths.)
Greetz
Thank you, Chris.
While on the terminal, I'm inside the viperMOD folder. Whenever I try execute "sudo ./adb shell" I get this: "sudo ./adb: order not found"
The tablet is plugged in, and in recovery mode.
I haven't installed Java nor the Android SDK because I haven't figured out a way to do it --why can't Linux be double-click action-oriented? *sigh* Anyway, does not having those things installed have something to do with the answer I'm getting from the Terminal?
If so, how in the world do I install them?
I'm never using Touch Recovery again, my word.
Thanks in advance.
Hey,
are you sure that there is "order not found?"
Try the command "ls" to see what files are available. If there is one, called "adb" you are in the right directory. If there is no "adb" then you have to move to the right directory.
Maybe you could try a "chmod +x adb" first and then execute "sudo adb shell" or such if you are in the right directory.
This is going to sound like a stupid question and sorry if it does. but you can access clockwork still right? what happens when you try to flash back your backup? This is important because I had an error sort of like yours that no one could solve here want to make sure its what happened to me. When i tried to restore the original rom it would get to the part where it was restoring data partition and then error on me reading file or something like that. If thats what you see i know the answer. or at least how i fixed mine.
push a rom
Read NIlsonf post about how to adb push a rom to cwm, you get a stock rooted rom
And adb push the blob file, then run the dd command, unmount staging mount data.
This is what fixed mine, and it looks like it fixed nilsonf's also.
Was this ever resolved? I have the same issue and it looks like I've been through many of the same steps as you've gone through. If you were able to do anything to fix it, please let me know.
I would even up the reward to $100.
Just thinking
Why dont you get someone elses CWM backup and adb push it to the device and restore it from that?
I know there are a couple posts out there on how to fix this, but this is one of the most legitimate ways to fix the multitasking issue we have all come to know and hate on Android devices running Sense. If you don't want to install a whole new ROM, such as MEANROM, you don't have to! This is a small guide to using the V6 SuperCharger script by Zeppelinrox. I know the amount of steps seems like a lot, but it's really not that many. Most of the steps will be followed by just reading what you see on the screen and accepting the recommended option!
Zeppelinrox said:
What's it do?
It makes your phone FAST... super snappy with better multitasking!
It rearranges and fixes the OOM Groupings and Priorites and lowmemorykiller values.
So basically, it's a COMPLETE MEMORY MANAGEMENT FIX!
It's the ONLY one of it's kind
NO LAUNCHER REDRAWS, faster than ever, multitasking is better... why?
Because it works with the lowmemorykiller and letting it work the way it's meant to work.
Also, because of the rearrangement, it works the same on all roms!
The problem with using minfree tweakers like AMM or AKMO is that it doesn't work the same on all roms.
Secondary apps may be in slot 3 on some roms but in slot 5 in others!
That's why you hear people comment "I tried AKMO but it didn't do anything..."
Most likely it didn't do anything because the apps weren't sitting where they were expected to be.
So fasten your seat belts and enjoy the ride!
Click to expand...
Click to collapse
So, everything you need to know or want to know can be found at Zep's original thread here. There is a lot of information, and because he is so technical, I think that sometimes his instructions can be hard to read for some, so I thought I would put together a VERY SIMPLE GUIDE to give you guys a hand. You can find the best instructions from him under Installing/Using.
http://forum.xda-developers.com/showthread.php?t=991276
On to the instructions...
How To Use Supercharger
Please only proceed if you are rooted and have busybox
Download script manager from the market: https://play.google.com/store/apps/details?id=os.tools.scriptmanager&hl=en
Download zep's latest V6 Script (V6_SuperCharger_for_Android-Update9_RC11_Test_6.sh.pdf): http://forum.xda-developers.com/showpost.php?p=18703418&postcount=5021
remove the .pdf extension (should now end in .sh) and place on your phone /sdcard (you can use rom tool box or estrongs to rename the file)
At this point, I highly recommend you make a nandroid through TWRP or CWM. The script has a built-in undo feature, which works well, but I still think we all know this is best.
Open up Script manager on your phone. Make sure to check 'Browse as Root' Option
Navigate to the location wher you placed the V6 .sh script
Click the Skull/Crossbones to run as root. This should turn green. NOTE: DON'T USE THE BOOT OPTION
Hit Run
At this point, get ready for an onslaught of text. Don't be afraid and try your best to read even though much of it may not make sense!
You may be asked about your launcher. Answer the question correctly for your setup.
Any time you are asked to press Enter, go ahead and proceed. This is the last time I will tell you to hit Enter for most occasions.
Pick your scrolling speed. I recommend slow or normal the first time you do this, so you can keep up.
On the kernel panic screen, I recommend choosing the Rock(H)ard Option, so hit H and then enter
Accept the Misc and 3G tweaks by hitting Y
Feel free to keep or disable the annoying animation (the scrolling V6 at the beginning of the script)
Hit Y(es) for SuperMinFree Calculator settings. This is an automatic calculation. You can change this later when you get more confident. Many will choose the 1000HP option for our phone (based on available memory)
It will now backup your build.prop and some other system files.
ICS and newer Android services store a lot of the memory tweaks in services.jar. This script will now take you through an ICS patcher. Accept the Automatic Transmission. This will upload services.jar, and download the patched one.
It will eventually tell you that it needs to wipe your caches and restart. You will definitely want to do this. You will need to wait 4-5 minutes while it rebuilds your Dalvik Cache
Almost done! After your phone boots up and stabilizes, go back into Script Manager. Navigate to /data/99Supercharger script. Check the SU (skull/crossbones) and check the boot option.
Zepelinrox said:
- Stock ROMs - It also creates /data/99SuperCharger.sh which you can load up on boot (run as root) with Script Manager. The OOM groupings work as well since it happens on boot in local.prop or build.prop (18 entries added)
Click to expand...
Click to collapse
Reboot your phone and now your phone will run the supercharger script on startup. If you ever want to verify that your script is working, or if you want to mess with any of the extra options (including removal), run the original V6 shell script you downloaded as root, just like we did at the beginning. This will tell you if you are 100% optimized and give you a whole menu of options to play with!
I can actually open multiple apps now and go back to the first one without it having to reload. Waze is the best example. If I ever switched out and then back, it always had to reload...not anymore! Again, this all seems like a lot, but it's really pretty easy once you give it a shot!
Let me know if anything is unclear so that I can adjust this OP to help others.
Make sure to give Zep a 5 Star Rating in his OP and also give him thanks, he is the man!
Reserved just in case.
ok i need to correct you on one of your steps...DO NOT SELECT THE BOOT OPTION FOR THE SCRIPT. IT COULD CAUSE YOUR PHONE TO BOOT LOOP. only select run as root. it even tells you that on the guide that zeppelinx put in his thread.
edit: sorry for caps but i wanted to point this out before someone made this mistake
bog3nator said:
ok i need to correct you on one of your steps...DO NOT SELECT THE BOOT OPTION FOR THE SCRIPT. IT COULD CAUSE YOUR PHONE TO BOOT LOOP. only select run as root. it even tells you that on the guide that zeppelinx put in his thread.
edit: sorry for caps but i wanted to point this out before someone made this mistake
Click to expand...
Click to collapse
You have to run /data/99Supercharger as root and give it boot option or it won't be applied at boot. But you are right, if you are worried, you could just run it as root the first few times. I personally always set this one to boot as well. If you had to, you could always adb in recovery, and remove /data/Supercharger if you are having problems.
*EDIT
This is mostly a concern for ROMS/Kernels that utilize /etc/init.d but I will add this caveat to the OP
adma84 said:
You have to run /data/99Supercharger as root and give it boot option or it won't be applied at boot. But you are right, if you are worried, you could just run it as root the first few times. I personally always set this one to boot as well. If you had to, you could always adb in recovery, and remove /data/Supercharger if you are having problems.
*EDIT
This is mostly a concern for ROMS/Kernels that utilize /etc/init.d but I will add this caveat to the OP
Click to expand...
Click to collapse
if the rom uses init.d then the script will install a service to the init folder and it will auto load when then phone is restarted, no need to try and force it to run. also if it is a stock rom (with the script manager program) you can set the 99supercharger to run after boot as a task.
bog3nator said:
if the rom uses init.d then the script will install a service to the init folder and it will auto load when then phone is restarted, no need to try and force it to run. also if it is a stock rom (with the script manager program) you can set the 99supercharger to run after boot as a task.
Click to expand...
Click to collapse
What you are saying is exactly the point I made in the OP. Is this unclear? You should only ever run 99Supercharger on boot, not the original V6Supercharge Script. And yes, this is geared mostly towards stock users, who do not have init.d support and therefore need SManager to run the boot script for them.
adma84 said:
What you are saying is exactly the point I made in the OP. Is this unclear? You should only ever run 99Supercharger on boot, not the original V6Supercharge Script. And yes, this is geared mostly towards stock users, who do not have init.d support and therefore need SManager to run the boot script for them.
Click to expand...
Click to collapse
i understand what you are saying but the boot symbol next to the run ass root symbol in the script should not be checked. if you need it to run at boot the script manager program can do that for you, by setting up a scheduler when you reboot. after boot it will run the script but not during
p.s. let me re-read what you put so i am just not looking stupid lol. i think i need a nap
edit: yea if you need it to run at boot do it through the script manager program and set it up to schedule it to load the script after your phone is already booted to avoid any potential boot loops (but dont check the boot logo at the top left hang corner of the actual script itself
bog3nator said:
i understand what you are saying but the boot symbol next to the run ass root symbol in the script should not be checked. if you need it to run at boot the script manager program can do that for you, by setting up a scheduler when you reboot. after boot it will run the script but not during
p.s. let me re-read what you put so i am just not looking stupid lol. i think i need a nap
edit: yea if you need it to run at boot do it through the script manager program and set it up to schedule it to load the script after your phone is already booted to avoid any potential boot loops (but dont check the boot logo at the top left hang corner of the actual script itself
Click to expand...
Click to collapse
Can you post the steps to describe how you personally do boot scripts with SManager?
After Android starts up, it will send a boot intent to all apps registered to receive such an intent. This is where SManager is allowed to execute any scripts you have marked with the boot option. This happens much later than a traditional /etc/init.d start script, but is no less effective. Please let me know how you mark scripts as bootable and I can add that recommendation as well. Thanks.
adma84 said:
Can you post the steps to describe how you personally do boot scripts with SManager?
After Android starts up, it will send a boot intent to all apps registered to receive such an intent. This is where SManager is allowed to execute any scripts you have marked with the boot option. This happens much later than a traditional /etc/init.d start script, but is no less effective. Please let me know how you mark scripts as bootable and I can add that recommendation as well. Thanks.
Click to expand...
Click to collapse
1. open script manager
2. click menu
3. click more
4. click advanced options
5. click scheduler
6. click add new task
7. click select file
8. navigate to 99supercarger file the script created and click on it
9.you can from there click on boot (inside the file you just clicked on)
10. click save
it will boot the script after the phone is done booting, to prevent the possibility of boot looping. you can also create an event to do an engine flush however often you want (i do one at midnight everyday)
This gets executed at the same time during system boot as the method I mentioned. Both are valid. Thanks for the feedback!
Sent from my Nexus 7 using xda app-developers app
adma84 said:
This gets executed at the same time during system boot as the method I mentioned. Both are valid. Thanks for the feedback!
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
i thought you were saying click the boot thing during install ....i am sorry haha i got really tired all of a sudden and stuff wass getting jumbled together...
v6 works awesome though i have been using it for about 1 year now on this phone and my old evo
Also, for anyone that gives this a shot, please post back with your results!
Not to be "that guy" buuuut the effects of v6 at least from my experience with this phone (again fresh frombcustoms preorder release) the day i got it i was rooted and installed v6 because ive used it on all my prior evos since i found it probably right around when zep released lol...anyways on this phone its a strictly placebo effect and actually created more lag and launcher reloads...i was running the 1000hp option and tried the i believe 750hp whatever the one down from 1000 is anyways both of them gave me same results and once i removed the script all was good in the hood as they say lol...but if its working for yall then maybe zep fixed some ish for this problem and i didnt know about it...well this epic runon sentence is finished sorry for the length and useless points
Sent from the depths of hell
yea i also used it on my og evo and i just put it on last night again on this one, tried the 750 option and 1000 option. today at school my memory got so low it locked my phone, that never happened with mean rom and the tweaks he puts in. undoing the supercharge now.
Sorry everyone.
Sent from my Nexus 7 using xda app-developers app
adma84 said:
Sorry everyone.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
no thanks man for helping out, i just think this phone doesnt do well with it, and that may be because of how HTC changed the multitasking settings themselves. it may conflict with v6
Theres something up with it because its def just this phone because nothing solves it at all
Sent from the depths of hell
wileout said:
Theres something up with it because its def just this phone because nothing solves it at all
Sent from the depths of hell
Click to expand...
Click to collapse
I wonder if it's hard coded into sense somewhere
Sent from my EVO using xda app-developers app
bog3nator said:
I wonder if it's hard coded into sense somewhere
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
Im thinking its sonething stupid like a character in the code is supposed to be one way and its mirrored the other way lol
Sent from the depths of hell
It's definitely helps with multitasking. I can keep apps open in the background much easier. Problem is that it chokes out the available ram for running apps, so it can make it feel sluggish. I think it's overtweaking the mem settings.
Hello XDA peeps going to attempt to unlock, root and flash a Rom for the first time tonight...any tips, suggestions and knowledge thrown my way would be greatly appreciated. Already looked around threads for "how to" I think I got good idea but knowledge is power haha
Sent from my HTC6435LVW using xda app-developers app
kenohki88 said:
Hello XDA peeps going to attempt to unlock, root and flash a Rom for the first time tonight...any tips, suggestions and knowledge thrown my way would be greatly appreciated. Already looked around threads for "how to" I think I got good idea but knowledge is power haha
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
unlocking is easy now with the new method, as long as htc's website is working.
then just install a recovery via fastboot and flash a rom. Id recommend viperdna
Bigandrewgold said:
unlocking is easy now with the new method, as long as htc's website is working.
then just install a recovery via fastboot and flash a rom. Id recommend viperdna
Click to expand...
Click to collapse
Im having issues with the new method. I feel like I have followed every bit of instructions yet my computer can seem to either recognize my device or does not find "fastboot" as internal or external storage.
It seems so easy too...
KevC90 said:
Im having issues with the new method. I feel like I have followed every bit of instructions yet my computer can seem to either recognize my device or does not find "fastboot" as internal or external storage.
It seems so easy too...
Click to expand...
Click to collapse
That just means you didn't correctly install the android sdk, or whatever its called.
Sent from my HTC6435LVW using xda app-developers app
Bigandrewgold said:
That just means you didn't correctly install the android sdk, or whatever its called.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Been meaning to ask this now but when it comes to downloading the new method APK file and hasoons toolkit v2.1 for the dna do I have to install them both through my phone or do I download them on to my computer and transfer the files through there.
Sorry if I ask a lot. I have just been reading so much and every time I thought I figured it out it shows the same message.
KevC90 said:
Been meaning to ask this now but when it comes to downloading the new method APK file and hasoons toolkit v2.1 for the dna do I have to install them both through my phone or do I download them on to my computer and transfer the files through there.
Sorry if I ask a lot. I have just been reading so much and every time I thought I figured it out it shows the same message.
Click to expand...
Click to collapse
Apk file just install on your phone. And I never used a toolkit so idk.
Sent from my GT-P7510 using xda app-developers app
Bigandrewgold said:
Apk file just install on your phone. And I never used a toolkit so idk.
Sent from my GT-P7510 using xda app-developers app
Click to expand...
Click to collapse
Are you using a windows vista comp or apple? Originally I just installed the apk, ran it, rebooted my phone (manually, ive seen a video where the phone rebooted itself and he manually booted it into bootloader), ran cmd "fastboot oem readcid" and nothing... it almost makes me want to return the phone.
KevC90 said:
Are you using a windows vista comp or apple? Originally I just installed the apk, ran it, rebooted my phone (manually, ive seen a video where the phone rebooted itself and he manually booted it into bootloader), ran cmd "fastboot oem readcid" and nothing... it almost makes me want to return the phone.
Click to expand...
Click to collapse
Did you select fastboot in bootloader.
Sent from my HTC6435LVW using xda app-developers app
Bigandrewgold said:
Did you select fastboot in bootloader.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Yes I did.
Installed apk through my phone
Ran the apk
Manuel reboot into bootloader (should I have fastboot check on in app>settings>battery?)
Hit the power button on fastbook
Open up CMD script and type "fastboot oem readcid"
and....
nothing... =[
Should my usb settings be set to anything in particular?
KevC90 said:
Yes I did.
Installed apk through my phone
Ran the apk
Manuel reboot into bootloader (should I have fastboot check on in app>settings>battery?)
Hit the power button on fastbook
Open up CMD script and type "fastboot oem readcid"
and....
nothing... =[
Should my usb settings be set to anything in particular?
Click to expand...
Click to collapse
What does your cmd prompt say after you press enter.
Sent from my HTC6435LVW using xda app-developers app
Bigandrewgold said:
What does your cmd prompt say after you press enter.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
'fastboot' is not recognized as an internal or external command, operable programs or batch file.
KevC90 said:
'fastboot' is not recognized as an internal or external command, operable programs or batch file.
Click to expand...
Click to collapse
That's because you're doing it out of a regular ol' command prompt.
There's two things you an do to alleviate that problem.
1) Follow this:
Right click on the My Computer icon and select the properties tab.
Select Advanced and click the Environment Variables button.
In the new dialog box double-click on Path (located under System Variables) and type in the full path location to the tools directory.
So essentially if your directory for ADB and fastboot are under C:\<SDK FOLDER NAME>\tools or C:\<SDK FOLDER NAME>\platform-tools, add those to the Path.
2) Go to the directory where ADB/Fastboot, hold SHIFT and then right click. It'll give you the option to open up a command prompt from that directory with should allow you to run those specific commands.
Also, getting back to the Paths. Make sure when you go to add a new path that you put a ; IMMEDIATELY after the very last one. Then absolutely no spaces right after that ;. So.... example coming up..
Let's say a path was C:\banana\peel, and you want to add your ADB folder. So it'll be typed like so, C:\banana\peel;C:\<SDK FOLDER>\tools and then you repeat the same exact thing for the next folder.
I really hope this helps!
Shamrock13 said:
That's because you're doing it out of a regular ol' command prompt.
There's two things you an do to alleviate that problem.
1) Follow this:
Right click on the My Computer icon and select the properties tab.
Select Advanced and click the Environment Variables button.
In the new dialog box double-click on Path (located under System Variables) and type in the full path location to the tools directory.
So essentially if your directory for ADB and fastboot are under C:\<SDK FOLDER NAME>\tools or C:\<SDK FOLDER NAME>\platform-tools, add those to the Path.
2) Go to the directory where ADB/Fastboot, hold SHIFT and then right click. It'll give you the option to open up a command prompt from that directory with should allow you to run those specific commands.
Also, getting back to the Paths. Make sure when you go to add a new path that you put a ; IMMEDIATELY after the very last one. Then absolutely no spaces right after that ;. So.... example coming up..
Let's say a path was C:\banana\peel, and you want to add your ADB folder. So it'll be typed like so, C:\banana\peel;C:\<SDK FOLDER>\tools and then you repeat the same exact thing for the next folder.
I really hope this helps!
Click to expand...
Click to collapse
Following the first method (thanks alot for the help too man, I appreciate it).
Ive found the PATH section you told me about, but I dont understand what you mean by "the full path location to the tools directory".
2) Where is the ADB/Fastboot directory?
New member here as well and was my first rooting and not as hard or challenging as you might think unless things go wrong.
Talk about noob on my part haha I didn't have any files (adb and sdk) well in my defense when I rooted my razr I had some program I downloaded that basically did everything for me so I guess haha thanks for these tips people keep them coming well attempt this again tonight or weekend
Sent from my HTC6435LVW using xda app-developers app
kenohki88 said:
Talk about noob on my part haha I didn't have any files (adb and sdk) well in my defense when I rooted my razr I had some program I downloaded that basically did everything for me so I guess haha thanks for these tips people keep them coming well attempt this again tonight or weekend
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Its okay. I was confused on this too because i ran the fastboot and it said it didn't recognize it. So i realized that fastbook has to be a program that i have to install. Eventually i figured out it was from the android sdk, but all the guides assume you have android sdk installed. They might want to consider adding something like "make sure you have android sdk installed and your Path set" in their guides. I know that would have saved me some trouble haha. ^_^
Yea that would have saved me some sleep haha I still can't get it to work though when I do CID exploit command prompt says no recognized ADB devices I think it might be cause I can't install HTC drivers (I hope cause I'm getting frustrated) haha will try again in next couple days
Sent from my HTC6435LVW using xda app-developers app