Related
There was an application called instantroot that roots HTC hero running 1.5 but until the software was upgraded nothing was done for the instantroot application. Do you have information about that? Is the developer still working on it?
rapsass said:
There was an application called instantroot that roots HTC hero running 1.5 but until the software was upgraded nothing was done for the instantroot application. Do you have information about that? Is the developer still working on it?
Click to expand...
Click to collapse
Not heard of it for a while, but this method at http://forum.xda-developers.com/showthread.php?t=726118 works on 2.1 fine with little issues.
Thanks but I'm still looking for a very easy way to do the root. I don't know why(may be I'm afraid) but I still hesitate to root my hero. I'll think about it again, thank again.
Following that link pulser gave will give the easiest way to root your hero.
Its thanks to that I'm able to root it with no problems whatsoever.
Good Luck!! Don't let yourself stay unrooted!!!
Ok. I'll try later as the villainrom web site is not reachable now.
rapsass said:
Ok. I'll try later as the villainrom web site is not reachable now.
Click to expand...
Click to collapse
Hmm. Are you having trouble too getting onto the site?
Here's the instructions as posted.
Hi all,
I believe I have managed to find a way to root the 2.1 RUU for GSM Hero, completely using the work of wag3slav3 over at XDA (http://forum.xda-developers.com/showthread.php?t=724741), so thanks to him
I took his Droid Eris root and used the correct files for our Hero, and thanks to daentech on IRC, we tested the process and it worked. Here are the conditions used in the test:
1) GSM HTC Hero installed with the 2.1 ROM based on RUU (on this occasion an update.zip was used, as the user involved didn't want to lose root obviously). That zip is unrooted and stock, taken straight from the RUU and converted to update.zip.
2) Booted into ROM, and enabled USB debugging. ADB was installed and set up on this machine, as per this guide - http://www.villainrom.co.uk/viewtopic.php?f=46&t=1735
3) Then downloaded this file: http://www.villainrom.co.uk/uploads/GSMRoot.zip
4) Extract it to a folder on your computer. Open the command prompt using Start > Run > cmd.exe (and press enter)
5) use cd to get into the folder you stored the extracted files.
6) Run the command "runindos.bat"
(If you use linux, put adb in your path folder, and then download this shell script: http://www.villainrom.co.uk/uploads/runinlinuxadb.sh and execute it as normal. Rest will be same as in windows. )
7) Ideally, the phone should sit there for a bit, with some things appearing on screen like
Files copied and permissions set, rebooting HTC Andriod 2.1
Your phone will now reboot into normal mode, then reboot into recovery mode
If it does not reboot the second time, wait 10 minutes and manually reboot and begin again
Your phone is now rebooting in Rooted Recovery mode, do a backup and load yourROMs
Click to expand...
Click to collapse
And it will reboot a couple of times. You will hopefully end up sitting in recovery with a blue 'care bear' in the background
If so, you now have a custom recovery installed. Do a nandroid, and flash a custom ROM like VillainROM 12 or whatever. You should now have root.
8) To further enhance the usefulness of recovery flash VR 12 from here: http://villainrom.co.uk/viewtopic.php?f=95&t=1807 which includes a modified recovery that wipes better than the stock Amon-Ra
If you don't get it to work, please post any errors or details of what happens, and copy and paste your entire command prompt window contents into a
Code:
[/quote] box in the forum window so we can see what's happening.
Hope this works
[size=3]PS. Here are some ROM links for you.
http://villainrom.co.uk/viewtopic.php?f=95&t=1807 - VillainROM 12 (Full Sense 2.1 ROM)
http://www.villainrom.co.uk/viewtopic.php?f=45&t=2844 - FroydVillain 1.1.0 (Vanilla 2.2 Froyo ROM)[/size]
[/quote]
If you can't download the file, get it from http://dl.dropbox.com/u/7618177/GSMRoot.zip
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Oh man thank you. I wonder if I must install ADB to root my phone. I ask this because I still can't reach villainrom web site to check this guide http://www.villainrom.co.uk/viewtopic.php?f=46&t=1735
rapsass said:
Oh man thank you. I wonder if I must install ADB to root my phone. I ask this because I still can't reach villainrom web site to check this guide http://www.villainrom.co.uk/viewtopic.php?f=46&t=1735
Click to expand...
Click to collapse
If you find the user btdag, his signature has the same guide, as he wrote it on both sites. I just use that link as it's easier to find.
pulser_g2 said:
If you find the user btdag, his signature has the same guide, as he wrote it on both sites. I just use that link as it's easier to find.
Click to expand...
Click to collapse
I would love to take credit for that guide but the user ante0 created it (such a simple method I overlooked). Here is it quoted. It is missing pictures but should make enough sense (i hope). It is highly recommended to have the latest HTC Sync installed (link in my sig) for this guide.
Tools needed:
Android SDK (Links below)
HTC Sync (Links below)
Winrar - to extract Android's SDK files.
Patience and time.
1. Getting ADB (Android Debug Bridge)
Okay. You now need to get ADB, which is a part of android's SDK. It can be obtained here http://developer.android.com/sdk/downlo ... indows.zip
or if it's updated when you read this you can go here http://developer.android.com/sdk/index.html and download it. Get the Windows version if you use a windows PC.
Next we need to "install" it. This is done by simply extracting it to your harddrive (Install WinRar, then rightclick on the zip file). I chose C:\android-sdk-windows\. (Actually I chose C:\, the folder in the zip is named android-sdk-windows, so it goes there by default.)
After that is done we are now done with the "installing" part.
2. Setting up environment variables (access adb from outside of \sdk\tools directory.)
Now that we have extracted all files we need to set up environment variables to make our lives easier.
I always do this, because if you don't you need to be in the sdk\tools folder at all times...
Okay, so here we go...
Windows XP:
Rightclick on "My computer" and select "Properties".
click on the "Advanced" tab in the box that appears, looks like the pic below.
Image
Click on the button named "Environment Variables".
Now, doubleclick on the text entry named "Path" in the lower list box.
at the end of it, enter "might\have\other\entries\before\;C:\Path\To\SDK\Tools".
In my "path" it looks like this ";C:\android-sdk-windows\tools\".
(";" is required at the start so windows knows it's a new entry.)
Click on OK to exit out of the dialog, then OK again to get out of My computer's properties.
Now we have it set up.
Windows 7/Vista:
This is similar to Windows XP's setup of environment variables.
Rightclick on "My computer" and select Properties.
In the System window that appears click on "Advanced System settings" located in the left list.
Click on the Advanced tab in the box that appears, then on the "environment variables" button.
Same thing here. Doubleclick on "Path" located in the lower list box.
At the end of it, enter "might\have\other\entries\before\;C:\Path\To\SDK\Tools".
In my "path" it looks like this ";C:\android-sdk-windows\tools\".
(";" is required at the start so windows knows it's a new entry.)
Now click on OK, then OK again to exit.
Alright, all set up!
3. Making sure USB works...
Use this guide: viewtopic.php?f=15&t=379
4. Using ADB
I won't list all commands you can use here. I will only list some examples...
Remember to plug your phone in your usb cable (I've forgotten sometimes... lol)
Start by opening a command prompt.
This is done by opening up the startmenu then click on "Run..." (Alternative way: Windowskey + R).
In the "Run..." box, enter "cmd" without quotes.
If you have some knowledge of using a cmd prompt you don't need to read the next part.
To navigate you mainly use the commands CD and DIR.
Here's an image of what it looks like
Image
C:\Documents and settings\jwork> tells you what your current working folder is.
To get out of it, use the command "cd ..".
This will go back one folder, so your new location will be C:\Documents and settings>
One more "cd .." will take you to C:\.
Now, lets say you have a folder named Images in C:\. To enter it you use "cd Images".
If you want to list all files in that folder, enter the command "dir".
Now you might have a image named image01.jpg in that folder, that you want to get to your phone.
Use the command adb push image01.jpg /sdcard/
It should notify you now if the push was successful.
You can check if the image is on your sdcard by using the command "adb shell ls /sdcard/".
That should conclude this guide...
One more thing, if you just enter "adb" it will show a list of all commands with descriptions.
Click to expand...
Click to collapse
Have you ever heard of Universal Androot? It is only one click away to root your hero2.1.
It's working on my hero.
Universal Androot? Never heard of it. But it looks great and easy. Can I also install another firmware after I root my device with it?
Can I install another firmware like FroydVillain 1.2.2 OTA on my hero after rooted it with this application?
If it installs a custom recovery image then yes you should be able to. If not try installing ClockworkMod and then installing AmonRA - once you have root.
You are the best. Thank you.
Application thread in the Nexus forum. Worked on my Hero 2.1 for instant root.
http://forum.xda-developers.com/showthread.php?t=747598
Since we are not able to boot into recovery mode and run update.zip is there a way to manually apply themes to the Desire builds we are using?
Such as [MOD] Smooth Sense Icons v.1.0 (now with screenshots)
Thanks in advance.
+1
i have been asking this question since day 1..and no honest reply
I'd love to know how to skin android full stop I cant even get my hd2 to connect in usb mode
well...the only way to apply some themes is to replace framework-res.apk into system/framework/framework-res.apk...doing this with root explorer has no succes even if you ADB it..this will brick your build and u have to install again the whole system.ext2...!!everywhere is explaining that first phone must go into recovery mode to apply it..!!so,till now cant have any solution but only wait to make a function to have the possibility to run the phone into recovery mode..!!Be patient..soon we'll have it!
[★] said:
I'd love to know how to skin android full stop I cant even get my hd2 to connect in usb mode
Click to expand...
Click to collapse
What build/zImage are you using? The latest zImage allows for USB internet sharing tethering and USB file transfer.
jjones1983 said:
What build/zImage are you using? The latest zImage allows for USB internet sharing tethering and USB file transfer.
Click to expand...
Click to collapse
I dont know what a zimage is (I know nothing about android ) but Im pretty sure my current build is a shubcraft one
yes..
i have even tried with droid exployer and it bricks the rom..it boots the at the android screen it just flashes black..dont understand..im using darkstone sense rom..he has the espresso bar..and i cant add anything too it
[★] said:
I dont know what a zimage is (I know nothing about android ) but Im pretty sure my current build is a shubcraft one
Click to expand...
Click to collapse
from what I've gathered a zimage is based around the kernal & drivers, with shubCRAFT you can connect via USB as long as its on debug.
11calcal said:
from what I've gathered a zimage is based around the kernal & drivers, with shubCRAFT you can connect via USB as long as its on debug.
Click to expand...
Click to collapse
ahh thanks and how do I put it into debug?
edangel said:
well...the only way to apply some themes is to replace framework-res.apk into system/framework/framework-res.apk...doing this with root explorer has no succes even if you ADB it..this will brick your build and u have to install again the whole system.ext2...!!everywhere is explaining that first phone must go into recovery mode to apply it..!!so,till now cant have any solution but only wait to make a function to have the possibility to run the phone into recovery mode..!!Be patient..soon we'll have it!
Click to expand...
Click to collapse
It's possible to change framework-res.apk through the terminal, can't say this will work for everyone and it may completely screw your android build, so a titanium backup couldn't hurt. This was done on shubcraft 1.4d to theme back to stock android (if your looking for the framework, it's somewhere in the shubcraft thread).
1. Place your new framework-res.apk in the root of /sdcard.
2. Run terminal.
3. su
4. mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
5. cd /sdcard
6. cp framework-res.apk /system/framework
Reboot and hopefully success.
gardndj said:
It's possible to change framework-res.apk through the terminal, can't say this will work for everyone and it may completely screw your android build, so a titanium backup couldn't hurt. This was done on shubcraft 1.4d to theme back to stock android (if your looking for the framework, it's somewhere in the shubcraft thread).
1. Place your new framework-res.apk in the root of /sdcard.
2. Run terminal.
3. su
4. mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
5. cd /sdcard
6. cp framework-res.apk /system/framework
Reboot and hopefully success.
Click to expand...
Click to collapse
DO you know of any guide anywhere which tells us where to get the android sdk and how to exactly set it up with adb on windows 7 so we can skin our android hd2's? I cant find much
all those guides
[★] said:
DO you know of any guide anywhere which tells us where to get the android sdk and how to exactly set it up with adb on windows 7 so we can skin our android hd2's? I cant find much
Click to expand...
Click to collapse
are for phones that can be rooted and flashed with recovery..for us on the hd2 we HAVE to adb every file 1 by 1...sucks..and even the terminal method..you will see errors on your phone..i wish darkstone would just say how he put the espresso on his rom.
Go to market and Download ROM Manager from Clockworkmod it's free.
Put the theme on the root of the SD
open ROM Manager
click install from SD
pick out the theme you just put it.
Reboot
themes are ROM/framework specific which is why certain themes are only available for certain ROMs. shu8i builds are based off of cyanogen and are therefore the easiest to theme IMO. I have done a theme thread for that particular set of builds and have had great feedback from users.
So FWIW, a theme cannot be applied to just any ROM. If you want to get into it, you will need to find and extract the .PNG files from the framework-res.apk , pull the framework-res.apk from the build you are currently running, replace the images, and replace the framework-res.apk in your build with the patched one with the new .PNG's
there are plenty of TUTs on XDA explaining how to theme, only difference is us HD2 users have to manually push the files instead of using the convenience of an update.zip that is flashable in recovery.
Moved you guys over to general.. Best of luck!
makomek said:
Go to market and Download ROM Manager from Clockworkmod it's free.
Put the theme on the root of the SD
open ROM Manager
click install from SD
pick out the theme you just put it.
Reboot
Click to expand...
Click to collapse
I understand that this thread is old, but I just found it. Trying to install a new framework-res.apk to my device using this method. I have it in a zip file (which is the format that would be used on a normal device to flash it from recovery mode).
Well I tried this; it lets me choose the theme (zip file) that I want, and it then prompts me to choose OK to reboot in recovery mode and continue the installation. Nothing happens when I choose OK.
Any further info on how to do this? What am I doing wrong?
I've tried this twice already with a factory reset in between each try, and it's worked both times!
Attached is a bunch of files you will need to make this work.
Download the attached Zip file and extrat the contents to your desktop
Mount your G and upload the "G Tablet" folder to your G's internal SD card
Using AndRootFile or any other file manager that supports root access, mount as R/W, and copy the contents of G Tablet\permissions to System\etc\permissions.
Copy the contents of G Tablet\framework to System\Framework
Copy the contents of G Tablet\lib to System\lib
Copy all the APK's found inside G Tablet\APK into your system\app folder.
Install them in this order:
GoogleServicesFramework.apk
OneTimeInitializer.apk
SetupWizard.apk
Talk.apk
Vending.apk
Gmail.apk
Maps.apk
Make sure you remount it as R/O when you're done!
Restart your G, Connect to Wifi, then launch Market.
Follow the standard Google Account setup procedure and enjoy your newly installed Market.
PROOF THAT IT WORKS (the guide might be broken at some point though, see explanation below): http://www.youtube.com/watch?v=3dm2Kax8RQM
Someone please test this and let me know if you have any problems. Factory resetting doesn't delete any files I might have moved into the system folder so I might be missing something in this guide.
Feel free to donate to my beer fund if this helped you
Copying the following over from my thread over at Overclock.net (best computer enthusiast community, ever!)
Guides:
Setting Up ADB:
The ADB drivers do not recognize the Tegra hardware by default. You need to modify the USB inf file in order for it to recognize it and install the proper hardware.
Go to the usb_driver folder inside your Android SDK folder
Open up android_winusb.inf
Add the following under [Google.NTx86] and save (or if you prefer, download my pre-modified android_winusb.inf attached to the bottom of this post, and replace your existing android_winusb.inf with mine).
Code:
;NVIDIA Tegra
%SingleAdbInterface% = USB_Install, USB\VID_0955&PID_7000
%CompositeAdbInterface% = USB_Install, USB\VID_0955&PID_7100&MI_01
If you are running a 64 bit version of Windows, you need to add that code to the [Google.NTamd64] section as well.
Next, open a command prompt and type
Code:
echo 0x955 >> "%USERPROFILE%\.android\adb_usb.ini"
On your G, go to Settings -> Applications -> Development, and check "USB Debugging"
Plug in your USB cable, it will tell you that some drivers were not installed. That's okay! Point it to your usb_driver folder and it'll install the proper drivers.
Make sure ADB is working by opening a command prompt, navigating to your android sdk "tools" folder, and typing
Code:
adb devices
You should see a bunch of numbers if everything is set up correctly.
Click to expand...
Click to collapse
Rooting:
You need to have ADB fully working before proceeding. The easiest way to root is by using CLShortFuse's SuperOneClick. If you can spare the money, consider donating a buck or two to his beer fund
Connect your G and make sure USB debugging is enabled/ADB is working.
Extract the contents of SuperOneClickv1.5.2-ShortFuse.zip to a folder of your choice.
Run SuperOneClick.exe and click on Root. Wait for the process to finish, and you're rooted! Easy as pie.
Click to expand...
Click to collapse
Installing Launcher Pro/ADW:
It's actually really easy.
Download the Launcher Pro APK from here: http://www.launcherpro.com/apk/LauncherPro-0.8.1.1.apk
Connect your G and move the Launcher APK over to your Tablet's internal/external SD card.
Using whatever file manager you prefer (on your G), execute the Launcher Pro APK and install it.
Upon completion, hit the Home button and choose LauncherPro as your default launcher.
Reboot and feel the speed!
Click to expand...
Click to collapse
Fixes:
Wifi Fix:
If your Wifi "errors" upon enabling, try one of the following methods
Method 1:
Reboot. Seriously, it fixes the problem a large portion of the time.
Click to expand...
Click to collapse
Method 2:
Download Wefi from here: http://www.wefi.com/download/android/
Install the APK on your G.
Run WeFi, hit the menu button (button between back and home), and hit Settings
Make sure Automatic Startup is checked. Click on "Wi-Fi on WeFi start" and choose "Always Turn On"
Restart your G and pray.
Click to expand...
Click to collapse
Method 3: Master Reset (you will lose all your apps)
Go to settings -> Security and do a Factory Wipe.
This works only SOMETIMES, but is not a guaranteed fix, so only use this as a last ditch resort
Click to expand...
Click to collapse
nicely done, sir
Awesome job. OCN FTW
Fantastic.. worked like a champ!
Thanks!
Where did you find the USB drivers to mount the device?
Can i also include the contacts, mail, and calendar gapps?
mattmanion said:
Where did you find the USB drivers to mount the device?
Click to expand...
Click to collapse
By mounting I mean connect the USB cable, then under the Notification Icon, Tap "USB Connected, Select to copy files to/from your computer"
insight3fl said:
Can i also include the contacts, mail, and calendar gapps?
Click to expand...
Click to collapse
Go for it, let us know what you find
r34p3rex said:
By mounting I mean connect the USB cable, then under the Notification Icon, Tap "USB Connected, Select to copy files to/from your computer"
Click to expand...
Click to collapse
Do you know if there is a tutorial out there for installing the Root Explorer or Astro file manager on this thing? Sorry, I'm a newbie.
VERY NICE WORK!
FYI I reposted this on the slatedroid.com forum gave you credit and linked back to this thread. If you don't want it on there let me know and I will take it down.
by the way.. All I did to get this working was install the apk's in order and reboot. I do have a problem .. I can't find some apps on the market.. for example winamp doesnt show up..just the winamp 3rd party app.
Anyone else?
Does anyone know why live wallpapers aren't available?
tri0xinn said:
by the way.. All I did to get this working was install the apk's in order and reboot. I do have a problem .. I can't find some apps on the market.. for example winamp doesnt show up..just the winamp 3rd party app.
Anyone else?
Click to expand...
Click to collapse
I will look into that. The most likely reason is the lack of a unique Android ID.
does the regular nullsoft winamp show up for you?
great work man. Just saw the video.
I'm still trying to get adb access. First thing I did was modded the usb files but not the 64bit cuz I didn't see it. Guess I didn't look hard enough. Modded the 32bit one and added the Nvidia tegra info. Then tried adb and the oneclickroot and it didn't work. I then went in and found the amd64 area and added the lines to that portion of the usb.ini file also.
I don't have adb working to root. I'm on Win 7 64bit. any idea's. Then I'll try your guide.
xguntherc said:
great work man. Just saw the video.
I'm still trying to get adb access. First thing I did was modded the usb files but not the 64bit cuz I didn't see it. Guess I didn't look hard enough. Modded the 32bit one and added the Nvidia tegra info. Then tried adb and the oneclickroot and it didn't work. I then went in and found the amd64 area and added the lines to that portion of the usb.ini file also.
I don't have adb working to root. I'm on Win 7 64bit. any idea's. Then I'll try your guide.
Click to expand...
Click to collapse
Gunth you want me to help over Teamviewer?
My files are in place, but the APK files are not "installing" on boot and the tablet sets up normaly and gmail app is not there. I have tried going back in and changing R/O in root explorer, but still not go.. what am I missing? Can these files be pushed to the tablet via adb or do you have to use root explorer? Seems I had the same problem when I did this with my Odroid T.. I tried root explorer but ended up pushing with adb.
Thanks for your work on this
hmmm... it says "install"... I need to launch them from explorer and actualy "install" them? then reboot?
insight3fl said:
My files are in place, but the APK files are not "installing" on boot and the tablet sets up normaly and gmail app is not there. I have tried going back in and changing R/O in root explorer, but still not go.. what am I missing? Can these files be pushed to the tablet via adb or do you have to use root explorer? Seems I had the same problem when I did this with my Odroid T.. I tried root explorer but ended up pushing with adb.
Thanks for your work on this
hmmm... it says "install"... I need to launch them from explorer and actualy "install" them? then reboot?
Click to expand...
Click to collapse
You need to run each APK manually through Root Explorer (or any package installer of your choice). Placing them there does not do anything
xguntherc said:
great work man. Just saw the video.
I'm still trying to get adb access. First thing I did was modded the usb files but not the 64bit cuz I didn't see it. Guess I didn't look hard enough. Modded the 32bit one and added the Nvidia tegra info. Then tried adb and the oneclickroot and it didn't work. I then went in and found the amd64 area and added the lines to that portion of the usb.ini file also.
I don't have adb working to root. I'm on Win 7 64bit. any idea's. Then I'll try your guide.
Click to expand...
Click to collapse
I'm having the same issue Gunth so when you get it working let me know
Just finished up installing the apks. Got a problem though. Now my home and search buttons don't work. Also lost Airplane mode when powering off.
*EDIT* Just watched your video. I don't think that's a finicky button. I think this hack causes the problem.
*EDIT 2* Just did a reset. Home button and search work again. So, it's got to be the hack.
Doc
I am having a problem with rooting my n7 recently I decided that I would flash back to stock clean wipe sd card and reroot, well it didnt work out that way, flashed back to stock without a problem, then rerooted ok, but then was prompted to install 4.2.1 from google, well I did and here I am cant get rerooted after installing update. I use wugs tool kit and has always worked on my GNex and until now my N7, any ideas anyone?
It seems to see ADB, but no Fastboot? very strange, could I need a fastboot file or something?
Yup, better not to use a toolkit.
Need adb.exe and fastboot.exe in the platform-tools folder of the android sdk and the proper drivers.
It is nice (but not neccesary) to add a path in enviromental variables so you don't have to have files in the same directory always.
Sent from my HTC Vision using Tapatalk 2
demkantor said:
Yup, better not to use a toolkit.
Need adb.exe and fastboot.exe in the platform-tools folder of the android sdk and the proper drivers.
It is nice (but not neccesary) to add a path in enviromental variables so you don't have to have files in the same directory always.
Sent from my HTC Vision using Tapatalk 2
Click to expand...
Click to collapse
could you send me more info, or links I am kind of new to this and would like to know what I did and how to avoid/fix it in the future Thanks.
demkantor said:
Yup, better not to use a toolkit.
Need adb.exe and fastboot.exe in the platform-tools folder of the android sdk and the proper drivers.
It is nice (but not neccesary) to add a path in enviromental variables so you don't have to have files in the same directory always.
Sent from my HTC Vision using Tapatalk 2
Click to expand...
Click to collapse
Nice to see you around.
I cannot forget the tremendous help you and Frankdrey gave me to discover, learn, and use an Android system on my G1.
Without both guidance I would, maybe, use now a toolkit and learn nothing.
@gunner - anytime, I love to help, now you can help others as well! Nice to see ya in the n7 forum too!
@flb
Google search android sdk, download appropriate package for your pc.
Open sdk and download all the tools in it.
To add a path I need to know what platform you are in... actually let me know when the above is finished and what platform your pc is and ill give you the rest of the steps
Sent from my HTC Vision using Tapatalk 2
demkantor said:
@gunner - anytime, I love to help, now you can help others as well! Nice to see ya in the n7 forum too!
@flb
Google search android sdk, download appropriate package for your pc.
Open sdk and download all the tools in it.
To add a path I need to know what platform you are in... actually let me know when the above is finished and what platform your pc is and ill give you the rest of the steps
Sent from my HTC Vision using Tapatalk 2
Click to expand...
Click to collapse
adb for dummies.. http://www.mediafire.com/?qrjo6bi8ayblj1r
this includes everything that is needed so you dont need to grab the whole sdk. easy access to adb and to fastboot.
demkantor said:
@gunner - anytime, I love to help, now you can help others as well! Nice to see ya in the n7 forum too!
@flb
Google search android sdk, download appropriate package for your pc.
Open sdk and download all the tools in it.
To add a path I need to know what platform you are in... actually let me know when the above is finished and what platform your pc is and ill give you the rest of the steps
Sent from my HTC Vision using Tapatalk 2
Click to expand...
Click to collapse
First of all thank you for the help, I'm currently running win7 64 bit. Ill check this post tomorrow and give it a try.
Sure thing, simms22 posted a nice link to just get the adb.exe and fastboot.exe, feel free to download those instead of the sdk as that is larger and you may or may not ever use a lot of the other stuff.
Sent from my HTC Vision using Tapatalk 2
demkantor said:
Sure thing, simms22 posted a nice link to just get the adb.exe and fastboot.exe, feel free to download those instead of the sdk as that is larger and you may or may not ever use a lot of the other stuff.
Sent from my HTC Vision using Tapatalk 2
Click to expand...
Click to collapse
Thank you guys for you efforts, Ill try it today.
You can just copy and paste the fastboot and adb .exe and .dll into c:\Windows instead of adding a variable.
Fast and easy lol just like I like 'em
Success! Thanks guys. I think Ill stay rooted and skip unroot rerooting.
First and foremost I AM NOT RESPONSIBLE FOR ANY HARD BRICKS,etc ,etc(Really hard to hard brick a kindle doing this unless you flash a weird rom package)
Now that thats cleared up, I have been seeing too many recovery bootloop bricks lately because I think the main tutorials people use haven't been updated(to mention you need to put a rom on the kindle beforehand now), so I thought why not write a tutorial that explains how to fix this problem since there are so many posts, that way we can just put a link to the tutorial in the peoples threads. So here we go!
Things you need to do this:
a micro-usb cable
patience
minimal command prompt experience
Instructions:
Boot your kindle into twrp (it should do this on its own at this point)
Make sure you have the adb drivers installed(they will need to be installed again if you flashed an older version of twrp), if not, update your drivers in the device manager with the ones in my signature.(See below if you don't know how to update your drivers)
Download the attached file and extract it somewhere
Put the rom and gapps in the folder you extracted the files to
Open a command prompt with admin privileges(start>all programs>accessories right click command prompt, hit run as admin)
CD into the directory where the extracted files are
Type this into the command prompt: adb push rom-or-gapps-name-goes-here.zip /sdcard/
As I said in the filename put either the rom or the gapps, but send both in two commands
At this point once the transfer is done unplug your kindle
If you are going from amazon to a cm based rom, at this point you should wipe system, cache, dalvik cache, and do a factory reset. If not just goto step 11.
Hit install, browse to the /sdcard folder and choose the rom and gapps files and flash them
Reboot and profit!
For people with driver issues that don't know how to install my driver:
Open the device manager
Find the device with a triangle next to it
Right click it and hit update driver
Choose the option that lets you search a folder for drivers by browsing
Choose the folder you extracted my drivers to
Let it search and install the drivers
Profit!
Note: If adb isn't picking up the kindle in recovery, try uninstalling the current kindle devices it detects first and then updating the drivers
It's about time someone posted a tutorial for how to fix this. Great job! This should be a sticky.
thanks
I had the same problem... the looping thing... you're tutorial saved me! thanks a lot.
rom and gapps
sry for my ignorance, but what do you mean with "rom and gapps"?
i explain what i've done:
i did everything in the guide to install twrp and 2nd bootloader.
i can acces in the twrp, but if i enter the reboot menu, if i push the botton "System", i had the boot loop problem (Kindle logo became orange and then blue forever)
Now the question is: where i find the rom and the gapps you're talking about?
You choose a ROM from the android development section for your model kindle, usually it tells what version of gapps(google apps) you need to flash with it. If it doesn't tell what gapps you need its pretty easy to tell, goo.im has the gapps posted for all versions of android, and have a chart telling which version goes with what os.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
*cannot read
When I go to push the file to the kindle I get a message in the command prompt saying *cannot stat 'rom.zip': no such file or directory.
I have the zip in the same folder as the adb file
Any suggestions?
Check the ROM name to make sure its not a typo? It should work. Make sure you didn't rename the ROM and add .zip because windows by default doesn't show extensions, so the filename might actually be ROM.zip.zip now if you did that.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Sigh, I was hoping my first post on XDA wouldn't be a help request, but here I am..
I agonized for hours over the directions in this tutorial, checked all the right boxes, but I ended up in the bootloop as described in the OP. I can get to TWRP fine, but nothing else. My ADB drivers along with the Android SDK package were installed and previously working fine. Now, of course, the device no longer has a driver in Windows. I followed the instructions here, carefully selecting the extracted folder containing the ADB files, and Device Manager tells me—
"Windows was unable to install your Kindle. If you know the manufacturer of your device, you can visit its website and check the support section for driver software."
Click to expand...
Click to collapse
I tried a number of times to reboot both systems, uninstall the Kindle, try to pick it up again, etc., to no avail.
My device is a Kindle Fire HD 7" originally version 7.4.6. I made backups before I started as per the directions in the linked thread and I have my desired ROM and Gapp .zips all ready to go, I just can't get anything to the device. I'd prefer to avoid needing to get a factory cable, if possible.
Thanks for any help!
Edit: I've managed to get my .zip files to the /sdcard/ directory. For anyone stuck on the same problem I was, the instructions in this thread got my ADB drivers up and running again. The rest of the steps here worked fine at that point.
Oh good, someone finally made a tutorial for this.
Help please
hello i am in need of some help, at step 6 can you explain what CD is. Also in Cmd i keep on getting this message below, please could you help me i also have just installed android ADB driver interface driver.
C:\Windows\system32>adb push cm-10.1-20130726-UNOFFICIAL-tate.zip /sdcard/
'adb' is not recognized as an internal or external command,
operable program or batch file.
CD means change directory, it does what it says, right now you are in your system32 folder so when you CD into the directory you extracted the zip file to you won't get that error. You should Google some command prompt basics.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Thanks
Thank you for this guide, googled some basic CMD knowledge and now i have cyanogen. Cheers
gallowayj3 said:
hello i am in need of some help, at step 6 can you explain what CD is. Also in Cmd i keep on getting this message below, please could you help me i also have just installed android ADB driver interface driver.
C:\Windows\system32>adb push cm-10.1-20130726-UNOFFICIAL-tate.zip /sdcard/
'adb' is not recognized as an internal or external command,
operable program or batch file.
Click to expand...
Click to collapse
Extract the file in the first post to somewhere on your C drive. (I put it in the C drive directly so it was just c:\adb\.)
Check this: ht tp://coweb.cc.gatec h.edu/ice-gt/339 - remove the spaces.
That should help.
Do
cd..
until you have just c:/. Then type cd:/adb and it should put you in the right place. Then you can do adb push.
I just figured this out actually and did it.
HELP
everything worked until i am flashing the rom, i get this error
updating partition details...
installing ' /sdcard/rom.zip'...
checking for MD5 file...
skipping MD5 check: no file found
assert failed: getprop("ro.product.device")=="blaze_tablet" || getprop(ro.build.product") == "blaze_tablet" || getprop("ro.product.device") == "tate" || getprop("ro.build.product") == "tate"
E:Error executing updater binary in zip ' /sdcard/rom.zip'
Error flashing zip ' /sdcard/rom.zip'
error flashing zip ' /sdcard/rom.zip'
epdating partition details...
PLEASE HELP
Sounds like an old twrp version I think, try downloading the latest twrp from android development for your device, It should have a flashable zip, just push it to your device and flash that, then reboot into recovery again and try flashing the ROM again.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stuck
Hi guys .., when i typed adb push cm-10.1-20130812-UNOFFICIAL-jem.zip /sdcard , it says
error: device not found.
i thing my pc didn't recognize my kindle. In device manager there ain't any devices not installed .
someone pls Help
Find the android adb device in the service manager and uni stall it and let it install my drivers and see if it works, I'm guessing its a simple driver issue.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Sorry for my stupid question. ) what is service manager?
stunts513 said:
Find the android adb device in the service manager and uni stall it and let it install my drivers and see if it works, I'm guessing its a simple driver issue.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
My bad I think my kindle autocorrected a word incorrectly. It was supposed to say device manager.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
i'm kind of newbie on rooting and installing ROMs.
http://www.youtube.com/watch?v=hUW6KARo8Y4
i tried this youtube instruction and after step 20 My kindle fire wouldn't start. Not even the kindle fire with blue color.
and also pc didn't recognize my kindle , maybe because of it won't power on.
/this instruction is for kindle fire HD 8.9 , i don't know my kindle is 7 inch/
In device manager can't find adb devices .. what should i do?