Does anyone know an easier way to put clockwork onto my phone? I mean other than (adb).. for some reason it doesn't pick up my phone.. Is there an recovery App coming out soon?
Sent from my LG-P925 using xda premium
make sure you have debugging mode on and that your Windows or Mac proper LG drivers are installed so that the phone is recognized also put CMD in the same folder as platform tools in sdk manager folder vice versa for files needed to be pushed to phone.
I got the drivers from the LG website for my cell, hmmm... ill have to recheck everything else because ADB has never gave me this much trouble
Sent from my LG-P925 using xda premium
I'd be willing to code a one click solution if it would be helpful. Its pretty easy as it is tho
Sent from my LG-P925 using xda premium
I had the same problems. I followed everything step by step and made sure I had the right drivers along with everything I would need with Java. Still no luck. I have the combination of feeling stupid and frustrated. I have rooted and installed custom roms on three different phones before.
A one click solution would be amazing if you could come up with that. I will try the ADB way again later.
Vince
Yes a one click, alot of people would thank you ....and i would be gratefull
Sent from my A500 using xda premium
i agree. ive been trying the adb method all day. for some reason just wont work. im prolly missing something
Try updating all the drivers for adb. It would be helpful for you and it would probably solve your issue.
Sent from my LG Thrill 3D using XDA Premium
Does one click root work for you? If it does, there is nothing wrong with your drivers.
Once you get one click root working, put the recover in the ADB folder that is part of one clock root.... then open that fold, hold shift and right click, select open command prompt, then type in the adb commands from the CWM instructions thread.
LG uses the same drivers for all their Android devices, I used their driver installer app and selected the Verizon LG Fathom since it didn't have the Thrill listed anywhere, have had no problems.
Some reason my comp doesnt do any of this correctly... so much for brand new tech
Does one click root work for you?
If not, you have a driver problem, fix it by downloading LG's driver installer, select Verizon for the carrier and then select the Fathom. If you have a drive issue, and that fails to fix it, try a different USB port... make sure you have your phone in debug mode... can you mount your SD cards?
If one click root does work, then YOU, not your new technology, is doing something wrong. So the question is, what are you doing wrong...
Please answer the question, does one click root work? From there, tell us step by step what you are doing, and we will tell you what needs fixing.
almost done
pjcforpres said:
Does one click root work for you? If it does, there is nothing wrong with your drivers.
Once you get one click root working, put the recover in the ADB folder that is part of one clock root.... then open that fold, hold shift and right click, select open command prompt, then type in the adb commands from the CWM instructions thread.
LG uses the same drivers for all their Android devices, I used their driver installer app and selected the Verizon LG Fathom since it didn't have the Thrill listed anywhere, have had no problems.
Click to expand...
Click to collapse
i put recovery in the adb folder, get all the way through the adb process and it says img can not be found? lol wtf
Did one click root work for you?
installed the fathom drivers, my iphoney 4, or my htc inspire was never this hard to work with
one click is the way i rooted my phone
robertmoore208 said:
one click is the way i rooted my phone
Click to expand...
Click to collapse
Ok, then driver issues isn't a problem, I would take a really close look at your ADB commands, and be sure to wait 30 seconds after each one to let it process.
I would recommend copy pasting the longer commands (right click copy, right click paste, the keyboard shortcuts don't work in command prompt window).
now it says permission denied on first command?
Then you don't have root... run one click root again. I would use it's driver check feature as well before running it.
lol i lost root? wow ok strange... i have superuser
Well... if you get accessed denied you either are typing something wrong, skipping a step, or trying to do something that needs root and you don't have root.
Do you have debug mode turned on? Do you see this active in your phones notification bar? That first line doesn't even need root access, if IIRC.
Related
I'm been searching the Nexus One Q&A section for an answer to my problems, but I couldn't find a solution. I'm running a stock version of 2.3.3 on my phone. It's never been rooted, and I have never rooted a device as well. I'm entirely new to this and have no idea what I'm doing. My device has no warranty but I'm still concerned about it. Again, I have no experience at all.
Also, I don't know if I would want to unlock the bootloader as I could lose everything. If there is a way to retain everything reliably (I don't know if those back-up applications are the most effective) that would be convenient.
So, can anyone help me root my virgin Nexus One?
Thanks for your time,
Tread Fox
Mybackup pro backs up apps and data. After you root you can use titanium backup. Also smsbackup and restore for your SMS :]
Alright, that's re-assuring. But what about actually rooting the phone?
Hmm I can't help with rooting because I have an Evo, just sharing some backup knowledge :/
You can use this threads wiki for the N1 and the stickies here:
http://www.nexusoneforum.net/forum/nexus-one-development-hacking/
You need to read several guides until you get a good idea of what you are doing and why.
Use the apps mentioned above to back up your phone info, once rooted you can do a complete and immediate phone backup of everything, like a full image pc backup.
If you do the one-click method, make sure it is for you OS, you will be limited in some things you can do, like fastboot commands and will be unrooted if you dl OTA's.
Read, Read, Read!!!
Before you flash a rom read the op page carefully and the last 20 pages for tips, info, issues etc.
Ken
This works for 2.3.3?
EDIT: So my only options are to unlock the bootloader or roll back? Which do you recommend?
You probably saw this in XDA wiki for N1:
http://forum.xda-developers.com/wiki/index.php?title=Nexus_One/Guides_&_Tutorials#Root
I would unlock, more options as you get more into flashing and you can't be unrooted by Google OTA's.
This is good guide for the S, but you can glean steps and maybe better understanding for the process. At the bottom in related posts is a root guide. I like the steps, but things like the fastboot and superuser may not be for the N1. However you can find them online. Just an easy to understand guide.
http://jaxov.com/2011/02/install-android-2-3-3-gingerbread-on-nexus-one-manually/
TreadFox said:
This works for 2.3.3?
EDIT: So my only options are to unlock the bootloader or roll back? Which do you recommend?
Click to expand...
Click to collapse
Sorry man, just got your message (phone died on me, and I've been playing with my other toys anyway...)
Yes, your options are to unlock the bootloader or roll back.
Both options will lose all date, so you need to backup either way.
My preference is to unlock the bootloader, but I can understand why people may not want to. Unlocking the bootloader can effect any warranty that's remaining on the phone (the phone has a 1 year warranty, no matter who owns it).
Thanks for all your help guys. Does anyone have a specific guide for rolling back? I don't need or want a custom rom, just setcpu...
Read my signature, execute PASSIMG method with FRG33. if it doesn't work (and sometimes it doesn't) - you're out of luck.
TreadFox said:
Thanks for all your help guys. Does anyone have a specific guide for rolling back? I don't need or want a custom rom, just setcpu...
Click to expand...
Click to collapse
This is how to go back to FRG33: http://forum.xda-developers.com/showpost.php?p=11745519&postcount=21
But if I were you, I would just unlock your bootloader. Makes life easier.
I'll unlock the bootloader. I saw a guide on the nexusoneforums on how to do this. But it's about a year old. Is there anything that's changed?
I'm sorry I'm being indecisive, I'm trying to take suggestions from anybody!
TreadFox said:
I'll unlock the bootloader. I saw a guide on the nexusoneforums on how to do this. But it's about a year old. Is there anything that's changed?
I'm sorry I'm being indecisive, I'm trying to take suggestions from anybody!
Click to expand...
Click to collapse
No, nothing has changed. You need to have the Android SDK set up properly. Then just boot into the bootloader by holding down the trackball while pushing the power button. Then open a command prompt in the directory where the fastboot.exe file is (probably C:\Program Files\Android\android-sdk-windows\tools) then just type: fastboot oem unlock
Follow this to set up the, it's easier (just the first post):
http://www.nexusoneforum.net/forum/...mple-sdk-setup-manual-root-guide-windows.html
Sent from my Nexus One using XDA Premium App
I don't know what I'm doing. This is confusing. When I hook up the phone to the pc it says its found new hardware. I'm running XP. What do I do? I think I'm going over my head with this. Also, how do I make sure mybackup will work? I don't want to lose my stuff!
TreadFox said:
I don't know what I'm doing. This is confusing. When I hook up the phone to the pc it says its found new hardware. I'm running XP. What do I do? I think I'm going over my head with this. Also, how do I make sure mybackup will work? I don't want to lose my stuff!
Click to expand...
Click to collapse
If you feel like you are in over your head, you probably are, and have not done enough reading. I just looked at danger-rat's post in the link he provided, and it seems quite straight forward, no? He even tells you how to install the drivers. "Step #3" under "To install the drivers" in the first post TELLS you that windows will detect new hardware and will ask you to install a driver. What seems to be the problem?
I did, and nothing happened. At all. I asked for it to download files from usb driver. Nothing happened at all. Is it something I'm doing wrong?
I have the SDK file on my desktop, I have all of the files inside that are needed. When the computer asks me to download the drivers, I re-direct to the usb driver folder located in the SDK which is located on my desktop. The computer claimed installation was successful, but nothing happened. When I try clicking the fastboot.exe in the tools file, it immediately forcecloses. Is it my pc? Is it the file? Is it the phone? I did read the material and so far nothing has helped.
TreadFox said:
I did, and nothing happened. At all. I asked for it to download files from usb driver. Nothing happened at all. Is it something I'm doing wrong?
I have the SDK file on my desktop, I have all of the files inside that are needed. When the computer asks me to download the drivers, I re-direct to the usb driver folder located in the SDK which is located on my desktop. The computer claimed installation was successful, but nothing happened. When I try clicking the fastboot.exe in the tools file, it immediately forcecloses. Is it my pc? Is it the file? Is it the phone? I did read the material and so far nothing has helped.
Click to expand...
Click to collapse
Well, after you have installed the driver that the computer asked you to install. That's just the driver needed to sync your file and stuff on your sd card. The other driver and adb setup is needed to actually access your phone.
So I asked for it to install the wrong files? What files do I install? Because from that guide it said point to usb driver. I'm only following the guide like you all asked, and nothing happened.
You don't launch fastboot by clicking on it windows.
Sent from my Nexus One using XDA App
well actually I moved it to a different fold thinking it would fix a issue i had. is there a way to restore it or move it back? phone will not boot up btw
tommy_o said:
well actually I moved it to a different fold thinking it would fix a issue i had. is there a way to restore it or move it back? phone will not boot up btw
Click to expand...
Click to collapse
Did you make a backup?
tommy_o said:
well actually I moved it to a different fold thinking it would fix a issue i had. is there a way to restore it or move it back? phone will not boot up btw
Click to expand...
Click to collapse
You should still be able to boot into cwm by holding power and Vol down. After that reflash your ROM, or restore a backup you made. Then you should be good to go
Sent from my VS910 4G using xda premium
Download the rom on your computer, extract the build.prop and push it through adb
taptaptouch said:
Download the rom on your computer, extract the build.prop and push it through adb
Click to expand...
Click to collapse
Or that... Good idea!
Sent from my VS910 4G using xda premium
I didn't make a backup...and smart me didn't have cwm installed...this was the new eazy zv7 to zv8 upgrade...didn't have a windows PC around me to run the bat file (currently on vacay, my host owns a Mac)...got to excited and tried doing what I could til I get home, instead "bricking" it..are there detail instruction on how to use adb ? sorry if this sound confusing and thanks for the responses..any other if needed? just ask..oh yea I'm around a Mac at the moment
tommy_o said:
I didn't make a backup...and smart me didn't have cwm installed...this was the new eazy zv7 to zv8 upgrade...didn't have a windows PC around me to run the bat file (currently on vacay, my host owns a Mac)...got to excited and tried doing what I could til I get home, instead "bricking" it..are there detail instruction on how to use adb ? sorry if this sound confusing and thanks for the responses..any other if needed? just ask..oh yea I'm around a Mac at the moment
Click to expand...
Click to collapse
If I'm correct I don't believe adb can be run on a Mac.
Gel Pen6 said:
If I'm correct I don't believe adb can be run on a Mac.
Click to expand...
Click to collapse
It can, you just need the right copy of it, but unfortunately it will more than likely need lgnspt to fix it.
wow this blows
manage to get the phone working again. of course im stuck in test mode..FML. which means i cant do the ota update. hey mt i kno you have the easy upgrade available but i dont think that applies to people with test mode. i couldnt fine the "hard" way u had before posting the easy one
Hello,
I have been following a thread in the Developer section, I'm unable to post there.
I could not find an answer?
I want to find out if there will be an issue using the NEXUS 7 TOOLKIT AUTO UPDATE V4.3.4 (SkipSoft.net)
I already have the Android SDK installed, a long story whilst playing about with a cheap Chinese Tablet :crying:
I realised the error of my ways and now have a nice Nexus 7 (4.2.2)
*** Anybody help please?, seeing that I can't post in the appropriate thread ***
Thanks
Dave
Nexus 7 toolkit auto update v4.3.4
NinjaMogglet said:
Hello,
I have been following a thread in the Developer section, I'm unable to post there.
I could not find an answer?
I want to find out if there will be an issue using the NEXUS 7 TOOLKIT AUTO UPDATE V4.3.4 (SkipSoft.net)
I already have the Android SDK installed, a long story whilst playing about with a cheap Chinese Tablet :crying:
I realised the error of my ways and now have a nice Nexus 7 (4.2.2)
*** Anybody help please?, seeing that I can't post in the appropriate thread ***
Thanks
Dave
Click to expand...
Click to collapse
Can anybody help please?,
No problems should arise. Though I don't quite understand your question. Is this right: You want to update/install a toolkit, but you have the Android SDK installed? If that's what you are asking then no, there will be no problems.
Confirmation
Logan_M said:
No problems should arise. Though I don't quite understand your question. Is this right: You want to update/install a toolkit, but you have the Android SDK installed? If that's what you are asking then no, there will be no problems.
Click to expand...
Click to collapse
Hi,
Sorry this is quite new to me.
Yes, I had installed the official Android SDK whilst playing/experimenting with a cheap tablet.
Now I have a Nexus 7, and it is recognised by my WinXP PC alraedy.
I want to unlock & root and found the thread in the developers section, but I'm unable to post there.
I wanted to ensure that I would not encounter problems/conflicts if I installed and used the Nexus 7 toolkit auto update v4.3.4 Tool on the same PC.
Hope this makes sense?
Thanks
NinjaMogglet said:
Hi,
Sorry this is quite new to me.
Yes, I had installed the official Android SDK whilst playing/experimenting with a cheap tablet.
Now I have a Nexus 7, and it is recognised by my WinXP PC alraedy.
I want to unlock & root and found the thread in the developers section, but I'm unable to post there.
I wanted to ensure that I would not encounter problems/conflicts if I installed and used the Nexus 7 toolkit auto update v4.3.4 Tool on the same PC.
Hope this makes sense?
Thanks
Click to expand...
Click to collapse
You already have the SDK, that means you don't need a toolkit....
Sent from my Nexus 7 using Tapatalk HD
Pirateghost said:
You already have the SDK, that means you don't need a toolkit....
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Unfortunately having the SDK does not mean I can actually use it
I got in over my head, hence trying to learn/read about it it on XDA
I found the thread that appeared to offer what I want,
a toolkit that I should be able to use to unlock/root with.
Thanks
But of you have the SDK and the drivers installed you don't need toolkit
Its like 3 commands
you dont have to know how to use the entire SDK, all you need to do is be able to follow directions. every nexus is rooted the exact same way. the only thing the toolkit does is hide the commands. you could take the few minutes to learn these commands
fastboot oem unlock
fastboot flash recovery nameofrecoveryfile.img
reboot to recovery
adb push SuperSU.zip /sdcard/ (or /data/media, whatever)
flash supersu.zip with your custom recovery....
Sent from my Nexus 7 using Tapatalk HD
Pirateghost said:
You already have the SDK, that means you don't need a toolkit....
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Pirateghost said:
But of you have the SDK and the drivers installed you don't need toolkit
Its like 3 commands
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Thanks...
It was the commands I had problems with on my last attempts
I got confused over ADB mode, Fastboot mode ??
I was not sure if they are device specific, given the Toolkits appear to be ??
I just don't want to brick my Nexus
Hence the thought of getting something(Toolkit) that I can just select options, hides the complexity.
Also
The toolkit looked like I could Backup all my Apps/Data, then unlock/root, and then do a Restore.
Thanks
NinjaMogglet said:
Thanks...
It was the commands I had problems with on my last attempts
I got confused over ADB mode, Fastboot mode ??
I was not sure if they are device specific, given the Toolkits appear to be ??
I just don't want to brick my Nexus
Hence the thought of getting something(Toolkit) that I can just select options, hides the complexity.
Also
The toolkit looked like I could Backup all my Apps/Data, then unlock/root, and then do a Restore.
Thanks
Click to expand...
Click to collapse
there are many guides and tutorials on all of these points.
here's the problem with toolkits:
THEY HIDE EVERYTHING FROM YOU
sure, more than likely you will be quite successful in merely rooting and unlocking your device with one....
then there is a pretty high certainty that you will begin experimenting with mods/roms/kernels/etc
at some point during your experimentation you will come across a 'soft-brick' or a bootloop, where all you see is either the google screen or the boot animation looping over and over. how do you get out of that situation? the toolkit didnt show you how, you plug in your trusty toolkit, only to find it doesnt see the device.... PANIC MODE ON!!....great. now you are going to come to XDA and make a damn thread about how you just 'bricked' your device and the world is ending....then you get told how to fix it albeit with some frustrations and complications....the right way, with fastboot and adb
or
you could just learn the damn thing and understand what it is you are doing to your device....then there would never be a situation you could not get out of using fastboot and adb.....
it really isnt complicated, and people around here are just Friggin lazy...its ridiculous.
XDA used to mean something, now its just a pisspot of people wanting their devices to be cool, without wanting to learn anything.
All Understould
Pirateghost said:
there are many guides and tutorials on all of these points.
here's the problem with toolkits:
THEY HIDE EVERYTHING FROM YOU
sure, more than likely you will be quite successful in merely rooting and unlocking your device with one....
then there is a pretty high certainty that you will begin experimenting with mods/roms/kernels/etc
at some point during your experimentation you will come across a 'soft-brick' or a bootloop, where all you see is either the google screen or the boot animation looping over and over. how do you get out of that situation? the toolkit didnt show you how, you plug in your trusty toolkit, only to find it doesnt see the device.... PANIC MODE ON!!....great. now you are going to come to XDA and make a damn thread about how you just 'bricked' your device and the world is ending....then you get told how to fix it albeit with some frustrations and complications....the right way, with fastboot and adb
or
you could just learn the damn thing and understand what it is you are doing to your device....then there would never be a situation you could not get out of using fastboot and adb.....
it really isnt complicated, and people around here are just Friggin lazy...its ridiculous.
XDA used to mean something, now its just a pisspot of people wanting their devices to be cool, without wanting to learn anything.
Click to expand...
Click to collapse
Hi,
All understould, and I couldnt agree more. The challenge, with many things now(on the Web) is finding the right information.
There are oodles, and oodles of sites with rooting information, tips and guides... etc..
I've probably watched a dozen or more "Youtube" vid's on the same subject, and they all have subtle differences..!!
I will look for "Manual" Unlocking and Rooting info for the Nexus.. and see what I find
Thanks...
NinjaMogglet said:
Hi,
All understould, and I couldnt agree more. The challenge, with many things now(on the Web) is finding the right information.
There are oodles, and oodles of sites with rooting information, tips and guides... etc..
I've probably watched a dozen or more "Youtube" vid's on the same subject, and they all have subtle differences..!!
I will look for "Manual" Unlocking and Rooting info for the Nexus.. and see what I find
Thanks...
Click to expand...
Click to collapse
not sure why you need to go anywhere other than right here on XDA....
theres a freakin sticky for it even...
http://forum.xda-developers.com/showthread.php?t=2150661
NinjaMogglet said:
Hi,
All understould, and I couldnt agree more. The challenge, with many things now(on the Web) is finding the right information.
There are oodles, and oodles of sites with rooting information, tips and guides... etc..
I've probably watched a dozen or more "Youtube" vid's on the same subject, and they all have subtle differences..!!
I will look for "Manual" Unlocking and Rooting info for the Nexus.. and see what I find
Thanks...
Click to expand...
Click to collapse
NinjaMogglet has given you all the information needed!
Just go grab the required files and chuck them in your platform-tools directory, run a command prompt and navigate to the directory and then run the said commands.
Still not clear??
smt8544 said:
NinjaMogglet has given you all the information needed!
Just go grab the required files and chuck them in your platform-tools directory, run a command prompt and navigate to the directory and then run the said commands.
Click to expand...
Click to collapse
I thank everybody for the comments...
I have since found other "Manual" methods, none of them are consistent
> Some use ADB commands to do certain things?
> There are references to making the "Recovery Stick", with some mnt, mv commands in ADB/FASTBOOT, it's not clear?
> There is reference to being in the right mode USB Debug Mode, PTP & MTP, but which?
> Install a Busy Box?
> and and ...
Whilst it maybe second nature to some of you folks, to me(others?) it a Black Art at the moment
I will do it, I just don't want to get part way in, and have a problem.
Thanks
NinjaMogglet said:
I thank everybody for the comments...
I have since found other "Manual" methods, none of them are consistent
> Some use ADB commands to do certain things?
> There are references to making the "Recovery Stick", with some mnt, mv commands in ADB/FASTBOOT, it's not clear?
> There is reference to being in the right mode USB Debug Mode, PTP & MTP, but which?
> Install a Busy Box?
> and and ...
Whilst it maybe second nature to some of you folks, to me(others?) it a Black Art at the moment
I will do it, I just don't want to get part way in, and have a problem.
Thanks
Click to expand...
Click to collapse
my previous post literally linked you to the ONLY thing you need....why did you ignore it?
its simple:
ADB can be used while in Custom Recovery or while booted into Android with USB debugging enabled.
Fastboot is used ONLY in fastboot mode
settings within the Android OS dont mean a damn thing in recovery or fastboot....which means it doesnt matter what USB mode you are in, or if debugging is enabled, as long as you are doing things from recovery or fastboot
every nexus device roots and unlocks in the same exact manner. the only difference would be that you need to use a recovery made SPECIFICALLY for that device...thats it
FOLLOW THE GUIDE THAT I ALREADY LINKED YOU TO....it tells you everything you need to do
Thanks
Pirateghost said:
my previous post literally linked you to the ONLY thing you need....why did you ignore it?
its simple:
ADB can be used while in Custom Recovery or while booted into Android with USB debugging enabled.
Fastboot is used ONLY in fastboot mode
settings within the Android OS dont mean a damn thing in recovery or fastboot....which means it doesnt matter what USB mode you are in, or if debugging is enabled, as long as you are doing things from recovery or fastboot
every nexus device roots and unlocks in the same exact manner. the only difference would be that you need to use a recovery made SPECIFICALLY for that device...thats it
FOLLOW THE GUIDE THAT I ALREADY LINKED YOU TO....it tells you everything you need to do
Click to expand...
Click to collapse
Thanks...
I did not ignore your link, I read all the pages.
Especially the one's that pointed out the ommisions, like un-lock first, and some of the key presses.
I will get back to this when I'm bright eyed, not 01:25 in the morning.... Just in case.
Thanks again
Post 1 - Information
Post 2 - Downloads and Release / Change Information
Post 3 - Bugs, Future Additions to the GUI, FAQ
I would like to add for those that like my toolkit, PLEASE DO NOT POST IT ELSEWHERE WITHOUT MY PERMISSION!
I have seen multiple sites who copy and paste my work to their site! If I do not approve of it, then do not do it! it will discourage me from adding updates since it is being used for their own benefits!
tl;dr.
If you post my work without permission, don't expect updates!
I created an easy to use GUI program for the HTC Amaze and I decided to make one for the HTC First. I spent a good over 10+ hours to learn how to script, watch videos on how to do it, working on it during school when I should have been listening lol and all that fun stuff. I am going to fix it and up and add more updates to it. You CAN place requests and I will try to fulfill it!
If this helped you out, Please press the thanks button and if you want, you can always donate!
FEATURES
- Install HTC Drivers
- Enter Bootloader (after it enters into bootloader, press the power button to enter Fastboot) REMOVED. No longer necessary.
- Get Token ID. Register at HTCDev, login to the site and submit the Token ID here. Buttons have been replaced and include links.
- Unlock Bootloader (Must place Unlock_code.bin in the folder)
- Install Recoveries
User Provided Recoveries
CWM Classic
TWRP
Kernels
User provided kernels
- Link to this thread
- Link to PM me if you need a phone unlocked
- Link to the One Development thread
- Boot Into Recovery/Bootloader/Phone
- Flash kernel/recovery/RUU zip
- Relock Bootloader (must be in fastboot)
- APK Batch Installer (Credits to hamsteyr)
- Donate to me (Hasoon2000) -> Donating to yours truly for putting time into this!
Here is a screenshot.
How To Use. THIS IS FOR THE PC ONLY. No plans ever for Mac or Linux. Sorry.
1. Download the toolkit DO NOT RENAME THE FOLDER
2. Download Winrar from here. Install it after you download it
3. Extract the folder anywhere.
4. Run the program.
Credits
- The guys at the AutoIT help forum that helped me learn how to make the script!
- Flyhalf205 for building CWM
- Devs for making us ROMS!
- The community for being awesome!
- HTC for making us the phone so we can be a community!
- To everyone else I may have forgotten!
*DISCLAIMER*
I take no responsibility for any fault or damage caused by any procedures within this guide. No warranties of any kind are given.
DONATIONS
Downloads
Mod edit: Download links removed
Changes
V1.0 Released! 4-20-2013
- Initial Release
Bugs
- Directory has to have one word.
Ex:
Will Work. This will solve any issues if the buttons don't work when you press them.
C:\Users\John\Dropbox\Phones\Amaze_All-In-One_Kit_V2.4
C:\Users\John_Smith\Dropbox\Phones\Amaze_All-In-One_Kit_V2.4
Will NOT work. Your directory will look something like this and buttons won't work when you press it.
C:\Users\John Smith\Dropbox\Phones\Amaze_All-In-One_Kit_V2.4
If you have 2 words, put the folder in Drive C:
Ex. This will solve any issues if the buttons don't work when you press them.
C:\Amaze_All-In-One_Kit_V2.4
Click to expand...
Click to collapse
Looking to add in the future
- Kernels
- More recoveries
- Makes Requests!!!
FAQs
Q - Why Did you make this?
A - To make life easier
Q - You are limited on features. Why?
A- You can always make a request!
Q - Will this work on other devices?
A - Only the fastboot commands, HTC Dev unlock (device specific) and the HTC drivers. Toolkit is made for the specific device.
Q - Will you support more devices in the future?
A - If people REALLY want, I can make it happen. I just don't want to make anything that nobody would use.
Q - Awesome! Can I make a donation?
A - Of course! Do not feel obligated though. If you would like to make a donation, you can click the button on my toolkit or under my username.
Nice! Thanks Hasoon!
Love seeing a noob-proof option for a custom recovery and root for the First.
just spitballing for ur one and only bug, why don't u use quotes so multi-worded folders work.. like "C:\Imma folder in an unusual place"
Sent from my Nexus 7 using Tapatalk 2
Where is the RUU Zip? DO we not have one? I need to flash the stock recovery back so please help.
ron1n541 said:
Where is the RUU Zip? DO we not have one? I need to flash the stock recovery back so please help.
Click to expand...
Click to collapse
Doesnt exist. I'm trying all my resources to get it though
Sent from my M7 using xda premium
Hi looks like the link is dead http://d-h.st/users/hasoon2000/?fld_id=2808
tinymiata said:
Hi looks like the link is dead http://d-h.st/users/hasoon2000/?fld_id=2808
Click to expand...
Click to collapse
I really should stop using dev host. It's down every other day. If I can get another file hoster with ftp support, that would be awesome
Sent From My HTC One via Someone's Room
hasoon2000 said:
I really should stop using dev host. It's down every other day. If I can get another file hoster with ftp support, that would be awesome
Sent From My HTC One via Someone's Room
Click to expand...
Click to collapse
I can hook you up on androidfiles.org if you want...hit me up on gtalk if interested
Sent from my M7 using xda premium
So there's an OTA out there (19.8MB, nothing big), but when it rebooted to update, it got stuck in CWM and I couldn't flash it there. I intended to pull the zip so we could make it flashable (and by "we", I mean someone more skilled than I), but I don't see it on the phone when it's plugged in, and when I check Software Update again, it says no update is available.
I'm well aware that flashing the OTA will likely kill root for me, but at this point, I don't really care. I'm hoping this OTA fixes the few bugs I'm having with the phone, and that's more than worth losing root over for me.
EDIT:
Posted the update in the development forum.
chrisliphart said:
So there's an OTA out there (19.8MB, nothing big), but when it rebooted to update, it got stuck in CWM and I couldn't flash it there. I intended to pull the zip so we could make it flashable (and by "we", I mean someone more skilled than I), but I don't see it on the phone when it's plugged in, and when I check Software Update again, it says no update is available.
I'm well aware that flashing the OTA will likely kill root for me, but at this point, I don't really care. I'm hoping this OTA fixes the few bugs I'm having with the phone, and that's more than worth losing root over for me.
EDIT:
Posted the update in the development forum.
Click to expand...
Click to collapse
I will make it flashable soon. I pulled the ota off my device. I just need to go back to stock. I will work on it tomorrow
Oh, I took a peek at it and it just seems like it's video type of update. Just updating a bunch of libs. I haven't checked to see if new firmware is in it yet
Sent from my M7 using xda premium
The DL is working again.:good:
Well, I'm no noob when it comes to working with HTC devices as I successfully unlocked the bootloader and rooted my One X with no problems back in the day. However, I'm running into a problem with the HTC First. I have unlocked the bootloader, and I am attempting to use the Toolkit to install a custom recovery. Unfortunately, when I try to do so, it gives me the following text:
'C:\Documents' is not recognized as an internal or external command,
operable program or batch file.
C:\Documents and Settings\Administrator\Desktop\First_All-In-One_Kit_v1.0\data>
After that it just hangs there and doesn't do anything. I'm not quite sure why it's doing that, nor do I understand why it's trying to access a non-existent folder in C:\
Any insight would be much appreciated.
RCon227 said:
Well, I'm no noob when it comes to working with HTC devices as I successfully unlocked the bootloader and rooted my One X with no problems back in the day. However, I'm running into a problem with the HTC First. I have unlocked the bootloader, and I am attempting to use the Toolkit to install a custom recovery. Unfortunately, when I try to do so, it gives me the following text:
'C:\Documents' is not recognized as an internal or external command,
operable program or batch file.
C:\Documents and Settings\Administrator\Desktop\First_All-In-One_Kit_v1.0\data>
After that it just hangs there and doesn't do anything. I'm not quite sure why it's doing that, nor do I understand why it's trying to access a non-existent folder in C:\
Any insight would be much appreciated.
Click to expand...
Click to collapse
It doesn't like the spaces. Put it at c:/ and try again
Sent from my HTC first using xda premium
jmz said:
It doesn't like the spaces. Put it at c:/ and try again
Sent from my HTC first using xda premium
Click to expand...
Click to collapse
Thanks for responding. I couldn't quite figure it out so I ended up ditching the tool-kit method and manually flashing it through command prompt.
Sent from my HTC first using xda app-developers app
RCon227 said:
Thanks for responding. I couldn't quite figure it out so I ended up ditching the tool-kit method and manually flashing it through command prompt.
Sent from my HTC first using xda app-developers app
Click to expand...
Click to collapse
All you had to do was look at post 3 of this thread and it mentioned the bug.
Sent From My HTC One via Someone's Room
hasoon2000 said:
All you had to do was look at post 3 of this thread and it mentioned the bug.
Sent From My HTC One via Someone's Room
Click to expand...
Click to collapse
I read all the posts before hand. I wasnt convinced that it was the same thing because mine didnt show Users/John as your example did. My computers username is Admin yet when I ran the toolkit it showed it was trying to access Documents which is a non-existent folder on my desktop. That's what I didnt understsnd.
Sent from my HTC first using xda app-developers app
RCon227 said:
I read all the posts before hand. I wasnt convinced that it was the same thing because mine didnt show Users/John as your example did. My computers username is Admin yet when I ran the toolkit it showed it was trying to access Documents which is a non-existent folder on my desktop. That's what I didnt understsnd.
Sent from my HTC first using xda app-developers app
Click to expand...
Click to collapse
Well, it did say this
If you have 2 words, put the folder in Drive C:
Ex. This will solve any issues if the buttons don't work when you press them.
C:\Amaze_All-In-One_Kit_V2.4
Sent From My HTC One via Someone's Room
adb won't recognize my phone. I use the toolkit to install the HTC drivers, but when I run the first script it get a "device not found message"
I'll try this on my laptop, see if it makes a difference. I have rooted many phones with this computer: Xperia X8, Xperia Sola, Atrix 4G, Atrix 2 and adb has always shown something when I run "adv devices" command.
I'm open to suggestions though! I'm running windows 7 Ultimate 64bit, in case this information in useful.
my htc one was previously on a 4.3 rom. I formatted data to go back to 4.1.2. Normally this is no problem as i just sideload a rom using adb. However now when I try to use the adb sideload command or any command it just brings up a list of adb commands. I updated sdk and made sure i installed all 4.1-4.3 apis. What can i do now? adb devices command does show the device connected and in sideload. Is this a problem on the phone end? Please any help would be appreciated, freaking out right now!!
Are you running your commands from you android-sdk/platform-tools folder?
When you say you get a list of adb commands it seems you are not issuing the commands from the proper folder.
and ccesbt
bigdaddy619 said:
Are you running your commands from you android-sdk/platform-tools folder?
When you say you get a list of adb commands it seems you are not issuing the commands from the proper folder.
Click to expand...
Click to collapse
Yes i am issuing them from the platform-tools folder. Its worth mentioning I have literally done this a hundred times before. Fortunately I was able to put a rom.zip on a usb drive and use USB OTG to flash it. I still would like to know what is going on with my adb though. Do you think it could be a problem with the recovery? I am using TWRP and i believe it might be one version old, but it did work before so i really dont know. Going to try a new recovery and see. Thanks for the reply.
hituinthedome said:
Yes i am issuing them from the platform-tools folder. Its worth mentioning I have literally done this a hundred times before. Fortunately I was able to put a rom.zip on a usb drive and use USB OTG to flash it. I still would like to know what is going on with my adb though. Do you think it could be a problem with the recovery? I am using TWRP and i believe it might be one version old, but it did work before so i really dont know. Going to try a new recovery and see. Thanks for the reply.
Click to expand...
Click to collapse
I'm using TWRP 2.5.0.0 and don't have any problems sideloading or pushing files to my device I know there is a different file structure for 4.2.2 and 4.3 roms that could be the problem the path you are trying to use is wrong just a thought not 100% sure though
So apparently it seems to be a driver problem. My computer stopped recognizing the device when it went into recovery. Fastboot works and I was able to use fastboot commands, so it was just recovery. I tired using multiple types of recoveries as well and i still nothing. ADB devices resulted in nothing showing up and any adb command resulted in a list of commands showing. So if you are having this problem try reinstalling drivers for HTC and ADB. I had to use a whole other computer all together because i think sometimes drivers do not work correctly on windows 8. Everything worked perfectly on my windows vista pc.
I have helped a few folks with Win8 rescue their phones in the past couple weeks so I can confirm it will work on Win8
bigdaddy619 said:
I have helped a few folks with Win8 rescue their phones in the past couple weeks so I can confirm it will work on Win8
Click to expand...
Click to collapse
I know it will work because it did before for me too. I am just saying sometimes dealing with windows 8 can be tricky.
I am grateful for people like you who come to the aid of less proficient folk such as myself. Thanks for your help and input!
hituinthedome said:
I know it will work because it did before for me too. I am just saying sometimes dealing with windows 8 can be tricky.
I am grateful for people like you who come to the aid of less proficient folk such as myself. Thanks for your help and input!
Click to expand...
Click to collapse
NP
Reason For Edit: Already Answered, Tapatalk Didnt Want To Load Responses So Didn't See It Was Already Answered