help unlocking bootloader - HTC U11 Questions & Answers

im in adb and when i type in fastboot oem get_identifier_token instead of getting the token, i get "waiting for any device". i followed the htc intructions and this is my result.
i downloaded the files from the htc dev page, and im using minimal adb and tools program. Ive always had success with unlocking previous phones, not sure what im doing wrong here or if im missing something.

you need drivers, what windows version you are on.

dryspuri said:
you need drivers, what windows version you are on.
Click to expand...
Click to collapse
Windows 10

Easiest way would probably be to install HTC Sync Manager, after installed uninstall HTC SYNC. There is no need to know what version of windows you have. Minimal ADB & Fastboot up to date?

yeah, installed the latest last night. ill try your suggestion

also when in Download Mode connect phone and type fastboot devices. If your serial number shows up, you are good to go.

schmeggy929 said:
also when in Download Mode connect phone and type fastboot devices. If your serial number shows up, you are good to go.
Click to expand...
Click to collapse
The serial number never showed up when I did that. However, after I opened htc sync manager, I was prompted to update it. So I followed thru with the update, opened the manager then proceeded with adb and I got the code. Only, I couldn't copy and cut the code out of the adb window I could highlight it but the copy or cut functions wouldn't work after highlighting the area and there was no way to highlight only the code. It wanted to highlight "bootloader" in front of each line. I don't have time to play around again until tonight but I might just try and type the code in by hand.

srimay said:
The serial number never showed up when I did that. However, after I opened htc sync manager, I was prompted to update it. So I followed thru with the update, opened the manager then proceeded with adb and I got the code. Only, I couldn't copy and cut the code out of the adb window I could highlight it but the copy or cut functions wouldn't work after highlighting the area and there was no way to highlight only the code. It wanted to highlight "bootloader" in front of each line. I don't have time to play around again until tonight but I might just try and type the code in by hand.
Click to expand...
Click to collapse
yes you have to delete all the extra spaces that you copy, a pain in the ass. or you could open the ADB & fastboot folder in Powershell.

schmeggy929 said:
yes you have to delete all the extra spaces that you copy, a pain in the ass. or you could open the ADB & fastboot folder in Powershell.
Click to expand...
Click to collapse
Ok so after watching a YouTube video unlocking the HTC 10, I saw how to edit out the extras. Well, I did that after pasting it all in there and I get an error saying the token length is too long.
Ugh
So there's the possibility of having a space in front of each line as you delete the bootloader text. Even though the lines are stacked above one another those imaginary spaces have to be gone.
Success Finally!!

srimay said:
Ok so after watching a YouTube video unlocking the HTC 10, I saw how to edit out the extras. Well, I did that after pasting it all in there and I get an error saying the token length is too long.
Ugh
So there's the possibility of having a space in front of each line as you delete the bootloader text. Even though the lines are stacked above one another those imaginary spaces have to be gone.
Success Finally!!
Click to expand...
Click to collapse
great! i was going to say at the end as well for all the extra spaces.

Just paste it to notepad first and it makes it so much simpler to format.
Sent from my HTC6545LVW using XDA-Developers Legacy app

If you right click on the command window border, then go to properties and uncheck the box that says something like "enable text wrapping" It will allow you to only highlight the code you need to copy.

sasquatch23 said:
If you right click on the command window border, then go to properties and uncheck the box that says something like "enable text wrapping" It will allow you to only highlight the code you need to copy.
Click to expand...
Click to collapse
I'll remember that for next time

Related

[GUIDE] Bad WiMax MAC? Broken 4G after update? Fix HERE!

Well I know I'm not the only one who got a bad WiMax MAC address after trying to update my WiMax radio image. I should learn to not try and fix things if they aren't broken
If you've gotten the dreaded "00:16:08:00:24:05" MAC address like I did, this guide will help you fix it. You'll need fastboot set up, a NAND unlocked phone with Toast's part 2 method, your correct MAC address for WiMax, and the files below.
FILES:
New radio
New WiMax
You MUST download & flash these again even if you already have. I don't care if you think you already have the right ones, download these. If you don't, don't ask me for help if you use the wrong ones.
STEP 1: Fix MAC
First, get your right MAC address. It can be found under the battery by the WiMax tag, or on your box under the WiMax barcode. It should be 12 digits long, with no colons in it. If it were supposed to be "00:16:08:00:24:05" it would look like 001608002405 on the box. Write that address down with a colon between every two characters to get it in the right format.
Next, boot your phone into fastboot mode. If you don't know how to do this, hold down volume and press power to boot into the bootloader. After it brings up the menu where "FASTBOOT" is highlighted, press power. It should say "FASTBOOT USB" in red where it previously said "HBOOT" in green.
On your PC, open a shell. First off, lets see if you have a bad MAC, run
Code:
fastboot oem wimaxrmac
It should return something like
Code:
INFOcmd_wimaxrmac
INFODev MAC = *Your MAC address will be here*
OKAY
If it doesn't match the code you wrote down, then you have a bad MAC. If it does match the code you wrote, then skip to step 2.
To fix it, you need to run:
Code:
fastboot oem wimaxwmac *Address you wrote down here*
Like if you wanted it to be "00:16:08:00:24:05" then you would run:
Code:
fastboot oem wimaxwmac 00:16:08:00:24:05
It should return something like:
Code:
INFOcmd_wimaxwmac
IFNOWrite OK! MAC = *Address you entered here*
OKAY
Then just run
Code:
fastboot reboot
To reboot back into Android with your correct MAC address.
STEP 2: Flash the images again
Now push those files to your SD card & reboot into recovery.
Once you're in recovery, flash the "evo.2.05.00.06.10.zip" file. Reboot from the menu like it tells you. Once you're in Android, update your Profile & update your PRL.
Now reboot into recovery again, this time flash the "evo.wimax.25641_r01.zip" file. Reboot again from the menu, and guess what. Once again, update your Profile & PRL. Reboot one more time for good measure, and you should have working 4G. I haven't been able to confirm 4G myself, but others have reported it working with my method. My logcat no longer shows any 4G errors and neither does the kernel log, plus all the data now matches how it was before my update, so that leads me to believe it's working.
I wrecked my MAC with the update and fixed it like this, but I haven't had a chance to try out 4G yet since I won't be going into the city where I'll have coverage until Saturday.
Please post here if it works for you or if it isn't clear then just post & I'll try and clear it up.
Regards,
Jesse C.
EDIT: As a few posters had trouble, it came to my attention that you MUST have run Toast's root part 2 image to have access to fastboot oem commands.
EDIT 2: Now full 4G fix.
Thank you so much!
Sent from my PC36100 using XDA App
On it.....!!!!
It's possible this may only update the MAC and not the key, Joshua (unrevoked) told me and a few others that was their main issue.
Let's see what results show.
Hot damn!!!! It works!!!
Neotelos_com said:
It's possible this may only update the MAC and not the key, Joshua (unrevoked) told me and a few others that was their main issue.
Let's see what results show.
Click to expand...
Click to collapse
If it really is the key, we can modify that here too. If we can pull a copy off a working device, we can write it with fastboot too I'm pretty sure
Geniusdog254 said:
If it really is the key, we can modify that here too. If we can pull a copy off a working device, we can write it with fastboot too I'm pretty sure
Click to expand...
Click to collapse
My understanding is the key is specific to each MAC, either way someone reported it works.
We just need people to post their before and after MAC address to confirm.
It does seem there are two variations of the bad MAC from different roms (at least from reports I've heard).
Well i changes the mac....i dont know if 4G is working on it.....
ON XP opening a shell using CMD? I'm not sure how to communicate with my EVO. Been without 4G for a while, trying to get it back up and running.
( waiting for device )
*nevermind*
Sleep..needed badly
Travyevo said:
ON XP opening a shell using CMD? I'm not sure how to communicate with my EVO. Been without 4G for a while, trying to get it back up and running.
Click to expand...
Click to collapse
You need adb from the Android SDK.
You also need to set your phone for USB debugging.
If you look around there's hundreds of tips on doing all this.
asrebel said:
*nevermind*
Sleep..needed badly
Click to expand...
Click to collapse
are you in fastboot?
Neotelos_com said:
My understanding is the key is specific to each MAC, either way someone reported it works.
We just need people to post their before and after MAC address to confirm.
It does seem there are two variations of the bad MAC from different roms (at least from reports I've heard).
Click to expand...
Click to collapse
I saw the same thing. I ended up with the one i posted in the OP but it seems they all start with the 00:16:08 characters.
I don't think its safe to post the after MAC address, sicne it's unique to every device. It won't hurt anything, but I'd rather keep mine private
Neotelos_com said:
You need adb from the Android SDK.
You also need to set your phone for USB debugging.
If you look around there's hundreds of tips on doing all this.
Click to expand...
Click to collapse
ADB appeared to install when i connected it. I'll take a look.
Thanks
my fastboot doesn't seem to recognize the 'oem' command. Is that a function of fastboot?
Anyone 4G back working using this method?
rocolema said:
my fastboot doesn't seem to recognize the 'oem' command. Is that a function of fastboot?
Click to expand...
Click to collapse
Yes. It should work for everyone. Do you have the newest fastboot?
david279 said:
Anyone 4G back working using this method?
Click to expand...
Click to collapse
I thought you said you had it working? Do you not have 4G or did it not fix the 4G errors
It fixed my MAC address. I have no 4G to test to see if thats working.
This is an interesting method.
I have restored my MAC via a different route, but I believe if I were to flash an offical wimax right now, I would lose my MAC again. What I have done requires modification to the wimax.img file.
Does this persist through reboots? If it does, this would likely be the best answer to the problem of the bad mac addresses.
david279 said:
It fixed my MAC address. I have no 4G to test to see if thats working.
Click to expand...
Click to collapse
Ah okay. I'm in the same boat

{GUIDE} Rooting an HTC EVO Shift for Dummies!

First of all I noticed there is not an individual post that gives the entire root process for those that have never used ADB and probably don't have the SDK installed. In other words people that have never rooted a phone before and didn't think they ever would because they think it looks SUPER complicated.
There are several tutorial threads on this subject but I can guarantee that these are the most simple and detailed, START to FINISH, instructions regarding the root process of a HTC EVO Shift that you will find on the web. My information is compiled together from numerous sources and my own personal experience to give less confident people what they need in order to root their phone and remain at ease.
RED-REALLY IMPORTANT INFORMATION THAT YOU NEED TO READ
BLUE-Notes from my experience and further explanations
Purple-File names color coded for easy identification
NOTE: I'm not responsible if you mess up your phone, however this process worked perfectly for me and it is pretty hard these days to brick your phone unless your trying.
Rooting Process
1. First, on your computer download the program "SDK" from Here. Download the file called "installer_r10-windows.exe". Install it. When prompted for the install path paste "C:\AndroidSDK" over the default path. Once finished, open it from the Start Menu. It should be right on your "C:\" drive. Now, select "Install Packages" and make sure you install "Android SKD Platform-Tools". Once finished, close out of Android SKD and AVD Manager.
2. ONLY FOLLOW THIS STEP IF PROBLEMS INVOLVING LOADING SDK OCCURS. Next, Go to the start menu and right click on "My Computer". Select "Properties", then select "Advanced"/"Advanced System Settings", then "Environment Variables", now go to the lower box (system variables) and select "path" then "Edit". Paste the following as your path "C:\AndroidSDK\platform-tools", then select OK. This seems to have fixed most peoples problems.
3. Now, on your phone, press "Menu", then "Settings", then "Applications", then "Development". Check the box that says "USB Debugging" and press "OK" when the confirmation box appears.
4. Now, install HTC SYNC. There should be a folder on your SD card that came with the phone that has a HTC SYNC Setup in it. Just drag this to your desktop and run it. Otherwise download HTCSync. After installation, plug your phone into the computer and select "Disk drive" on your phones prompted menu.
5. Next, download the VISIONary app from Here and save it on your desktop. Once downloaded, Copy "com.modaco.visionaryplus.r14.apk" and Paste it to the SD Card root. Or in other words, drop the file in the first folder of the SD card on your phone.
6. Next, switch your phone's connection status back to "Charge Only". Use any file manager (free from the android marketplace "ES File Explorer") to install the VISIONary app on your phone. On your phone just find the visionary installer in the file manager and click to install. (Icon should look like a caution sign). Once complete, open VISIONary on your phone and click "Temproot Now". Wait for the rooting process to take place. Shouldn't take long at all. At this point your phone is rooted. However, you may noticed that your phone is running slower than normal. Go back into VISIONary and put a check next to the box that says "temp root on boot". Now power off your phone and then turn back on. This will root your phone before background apps are running, thus making it much faster.
7. Next, Download the root file Here. Once installed, connect your phone to your computer as a disk drive and right click on the "shift-root.zip", select extract here, then use browse to locate your phone, more specifically the root of your SD card. If you are having trouble extracting, download 7-Zip. Now change your connection type back to "Charge only" again.
8. Next, Open the command prompt (Start > Run > type "cmd") and paste the following...
Code:
cd C:\AndroidSDK\platform-tools
Hit enter, and type the following...
Code:
adb
If adb runs you're golden. Type this...
Code:
adb shell
Hit enter, you will see this...
Code:
$
Now type...
Code:
su
Hit enter... Now switch back to your phone. Superuser (an automatically installed program) will prompt you to "Allow" on your phone. Click it quickly to allow permissions! Now you will see this in the command prompt...
Code:
#
You have root permissions. If you didn't click allow fast enough just retype "su" and click enter again.
9. Next you have to Verify md5sum. Basically just make sure you copy and paste this EXACTLY...
Code:
md5sum /sdcard/Shift/hboot_orig.bin
Then hit enter.Your result should look like this...
Code:
386c19451e8dd18f9b98fad6b11be4c0 hboot_orig.bin
Make sure the numbers match. You may have some extra path in front of hboot_orig.bin.
If a message saying that the md5sum is not found, paste this code before verifying the md5sum. If it worked in the first place then ignore all this red...
Code:
busybox md5sum /sdcard/Shift/hboot_eng.nb0
It should work now...
Next copy and paste this exactly...
Code:
md5sum /sdcard/Shift/hboot_eng.nb0
Then hit enter.Your result should look like this...
Code:
60ec1006e6ec2e8acb370d6aad35b17e hboot_eng.nb0
Make sure the numbers match. You may have some extra path in front of hboot_eng.nbo. If these do not match do not proceed. Delete the "shift-root.zip" file on your sd card and redownload.
10. Now we're going to flash the "eng spl." This is where the unpleasant things can happen. Make sure you are in "adb shell" with superuser root permission (Granted a "#" symbol). This was explained in Step 8. If you are not in "adb shell" with root permissions (Granted a "#" symbol) then DO NOT proceed.
Now DO NOT REBOOT until you are instructed to do so!!! In the command prompt, paste this EXACTLY...
Code:
dd if=/sdcard/Shift/hboot_eng.nb0 of=/dev/block/mmcblk0p18
Hit enter. You have flashed the "eng spl." Now we need to make sure it flashed properly.
11. Run this command to pull the newly flashed "hboot" to your sdcard. Copy and paste this EXACTLY...
Code:
dd if=/dev/block/mmcblk0p18 of=/sdcard/Shift/hboot_check.nb0
Hit enter. Next you need to check the "md5" to see if it matches. In the command prompt, Copy and paste this EXACTLY...
Code:
md5sum /sdcard/Shift/hboot_check.nb0
Hit enter. It should read...
Code:
60ec1006e6ec2e8acb370d6aad35b17e
if the "md5sum" matches then congratulations its safe to reboot!! you can skip the next bit and continue on to step 12.
If you absolutely cannot get the eng hboot to flash right then copy and paste this into the command prompt...
Code:
dd if=/sdcard/Shift/hboot_orig.bin of=/dev/block/mmcblk0p18
Hit enter. Then pull it to check "md5". Copy and paste this exactly...
Code:
dd if=/dev/block/mmcblk0p18 of=/sdcard/Shift/hboot_check1.bin
Hit enter. Then check the "md5sum" by copying and Pasting this exactly...
Code:
md5sum /sdcard/Shift/hboot_check1.bin
Hit enter. It should read...
Code:
386c19451e8dd18f9b98fad6b11be4c0
If it doesn't, keep trying the previous 2 codes until it does but DO NOT!! reboot till it matches.
12. Now we can Perm root!!! First you need to reboot your phone into "bootloader". Do this by turning off phone and hold (power + volume down) till it boots into bootloader. Look at the top and make sure it says "s" off. If so, reboot the phone back into android by turning off and then back on.
13. Next Put the phone into airplane mode (hold down power and then click "airplane mode"). Go to setting, applications, manage applications and uninstall superuser.
14. Next, temp root with visionary. After you are temp rooted then attempt to perm root with visionary. Your phone will reboot and you are now officially perm rooted any changes you make will now stick on reboot. If it didn't stick, try doing steps 13 and 14 again.
YOUR PERMROOTED
Simplified Backup (with WiMax Backup!)
1. Find "ROM Manager" in the Market (free or paid) and install the app.
2. Open it and select "Flash ClockworkMod Recovery".
3. Click on "HTC Evo Shift 4G" and then give the app root permission if it prompts you.
4. Once the flash is successful, you should see a dialog box that says "Successfully flashed ClockworkMod recovery!"
5. Press OK.ClockworkMod should now be installed on the HTC Evo Shift 4G.
6. Before you backup your phone, open the ROM Manager application and select "All Clockwork Recoveries".
7. Select the most recent version, currently it is v.3.0.1.4 (If you already have the most current version skip to step 6)
8. Press OK.
9. Your phone will flash the most current recovery image.
10. Now once your phone finished, open ROM Manager and select "Backup Current ROM".
11. Press OK.
12. Your phone will begin the backup process, including backup of your WiMax Partition.
13. Once finished your phone will restart. DONE! A backup is now on your memory card.
UnRooting
1. Be sure HTC Sync is installed on your computer. (Link to download near top of first post)
2. Download the sprint RUU Download.
3. Plug your phone in to your PC, select "charge only", then run the RUU File
Sources:
More Detailed Perm Root Instructions
Beginner's Guide to Installing the SDK and Getting Started with ADB
ADB/Fastboot Easy 5 Minute Setup
All About Rooting the HTC Shift: FAQ's & How To's
IF YOU THINK ANY OTHER INFORMATION SHOULD BE ADDED FEEL FREE TO SHOOT ME A PM AND I'D BE HAPPY TO ADD IT.
ADDITIONALLY IF THIS GUIDE HELPED YOU OUT FEEL FREE TO LEAVE A THANK YOU.
There's already a guide and its pretty basic
Sent from my PG06100 using XDA App
JKILO said:
There's already a guide and its pretty basic
Sent from my PG06100 using XDA App
Click to expand...
Click to collapse
I understand there are already guides but they are not necessarily for people that have never rooted a phone before... And that is what this guide is for.
Other guides assume people have all the required software preinstalled and that they know what the guide is referring to when it says to "flash" certain things. They also assume people know how to Temp root using VISIONary and how to check the md5sum. This is for people that have done absolutely nothing to an android phone before and have no clue what the other guides are even talking about.
And yes I understand there are simplified guides that involve individual steps but this is a BEGINNING to END guide for Dummies so there is no need to jump across multiple threads.
To each their own..maybe someone will find a use
Sent from my PG06100 using XDA App
i did. thanks
nice work - seems to be the one from either androidforums.com or Androidcentral forums.
This sort of does exist, maybe not so colorfully, but here is Brando's thread
http://forum.xda-developers.com/showthread.php?t=934165
JKILO said:
To each their own..maybe someone will find a use
Sent from my PG06100 using XDA App
Click to expand...
Click to collapse
The process in the first Perm Root guide seems simple now, but when I was first looking at the guide it was a foreign language. Did my research by looking through about 6-7 other threads and finally had some idea as to what it was talking about.
Completed a successful root on my own phone and made the first draft of this tutorial along the way. More and more info has been added to this guide as I learn more and more. Now its about a month later and I've learned quite a bit about my phone and whole rooting process in general. I've once again updated the guide to make it as simple as possible with my newly acquired knowledge. This guide has over 2500 views on another thread I initially posted and numerous people have used it to root their phone so I figured I'd post it up here as well in order to help more people.
Nice A-Z guide. When I rooted mine a month ago, I needed to get info from 2 or 3 threads and tie missing pieces together. This ends that. It is a great start to finish guide. The other ones assume that you have done this before or only provide half of the entire solution needed to get everything done.
Only suggestion, clockwordmod backs up wimax after a particular version, you may want to state that as a disclaimer...else someone may grab an old version, assume they are fine, and will/could be screwed...
riggsandroid said:
nice work - seems to be the one from either androidforums.com or Androidcentral forums.
This sort of does exist, maybe not so colorfully, but here is Brando's thread
http://forum.xda-developers.com/showthread.php?t=934165
Click to expand...
Click to collapse
I initially posted it on androidforums.com
Similar, but I went one step further than Brando and explained every process in detail. For instance, rather than saying "setup adb" and "temproot your phone using visionary" I explained the process. I know that I myself looked up how to setup adb and temp root my phone when I got to those steps. Figured I'd put everything in one thread to make it easier for people that have never touched an android before.
umrico said:
Nice A-Z guide. When I rooted mine a month ago, I needed to get info from 2 or 3 threads and tie missing pieces together. This ends that. It is a great start to finish guide. The other ones assume that you have done this before or only provide half of the entire solution needed to get everything done.
Only suggestion, clockwordmod backs up wimax after a particular version, you may want to state that as a disclaimer...else someone may grab an old version, assume they are fine, and will/could be screwed...
Click to expand...
Click to collapse
Thankyou.
I stated that clockwork can backup wimax but I'll be sure to add that it is clockwork mod version 3.0.1.4 in the OP.
JKILO said:
To each their own..maybe someone will find a use
Sent from my PG06100 using XDA App
Click to expand...
Click to collapse
IF you don't have something constructive to share.....! STFU
bash78 said:
IF you don't have something constructive to share.....! STFU
Click to expand...
Click to collapse
The threads aren't for flaming..I was just pointing out it had been done but hey you go girl
Sent from my PG06100 using XDA App
Small complaint, but kinda a big deal. You need to make sure to actually list your sources especially when you're taking directions word for word out of other threads. You must give credit where credit is due. That said, it is a great writeup, though a bit overwhelming. I wrote a guide that looks very similar to this at SDX: http://forum.sdx-developers.com/evo-shift-development/(guide)-root/
Not quite as detailed as yours, but informative nonetheless. Overall, great work, just site your sources in the OP and you'll be good to go.
tambourineman86 said:
Small complaint, but kinda a big deal. You need to make sure to actually list your sources especially when you're taking directions word for word out of other threads. You must give credit where credit is due. That said, it is a great writeup, though a bit overwhelming. I wrote a guide that looks very similar to this at SDX: http://forum.sdx-developers.com/evo-shift-development/(guide)-root/
Not quite as detailed as yours, but informative nonetheless. Overall, great work, just site your sources in the OP and you'll be good to go.
Click to expand...
Click to collapse
My sources are, and always have been, at the bottom of my post...?
And basically everything has been changed rather than just taken word for word due to the fact that I wanted it to be as understandable as possible. Most of it I wrote myself using other guides as a framework but the steps are all the same...
Sorry about that. I read through the whole thing but totally missed it. I apologize profusely for missing that and the post that resulted from it. I guess I'm just used to seeing credits at the top. Again, my bad, I'll be more careful in posting criticisms in the future.
Lol. No hard feelings. I was just really confused.
Thank you !!!! Im a dummy and this helps alot!! I thought my phone wasnt getting temp root because it was running so slow using visionary,and now i know why!!!!
Soon to be shifty rooted!!!
Stuck at installing the "installer_r10_windows.exe"
I get the message of the JDK is not found. I have installed/reinstalled 3 times with only the same results.
Steps 3-7 went through without any problems at all.
Any thoughts?
Your going to need to install the Java Developement Kit (JDK) in order for the android SDK to be able to install.
Download
It will prompt you to register it and make a Oracle account after it installs.
It should have prompted you to download the JDK during the SDK install if you don't have it on your computer already?
SHMaRiM said:
Your going to need to install the Java Developement Kit (JDK) in order for the android SDK to be able to install.
Download
It will prompt you to register it and make a Oracle account after it installs.
It should have prompted you to download the JDK during the SDK install if you don't have it on your computer already?
Click to expand...
Click to collapse
I assumed that it would have been, but it wasnt. I've done it a couple of times already, but was not successful. Even after it was registered. It still keeps telling me that I need to install the JDK as it was not found.

[Boot Splash] "Inspired" by Light (w/Preview Pic)

I hope you enjoy this. These are pretty easy for me to make, so if you have a request... ... At any rate, "thank" me if you like it and use it. And if you screw anything up and your phone explodes, or breaks, or Smurfs attack from outer space, it's your fault. you have been warned!
How to flash:
1. Unzip the file so you have "splash1.img" and place this file in your "tools" folder of your SDK package.
2. Boot into your bootloader (fastboot mode)
3. From the command prompt: Change directories to your SDK "Tools" folder then type:
Code:
fastboot flash splash1 splash1.img
4. Reboot and enjoy
Got a preview pic by chance. Also check your pm's.
Preview pic should be up... I see it on my end?? It's HUGE. lol..
Anyone else not see the pic?
EDIT: Just checked the OP on a different PC, and pic WAS NOT showing up. This has now been corrected. ...
How do we revert to default, if desired?
smalis said:
How do we revert to default, if desired?
Click to expand...
Click to collapse
You will have to re-flash the default boot splash. Using the same method as mentioned.
Note: I will update the OP with the stock Boot splash as well, once I receive my phone.
OK, stupid question time (my specialty) I get into the Inspire bootloader OK, but then how do I call up or otherwise access "command prompt"? It's not like I have a menu button I can push, and command prompt doesn't seem to be one of the options displayed on the screen. I may be overlooking the obvious, and if so I apologize.
Ultra Droid said:
OK, stupid question time (my specialty) I get into the Inspire bootloader OK, but then how do I call up or otherwise access "command prompt"? It's not like I have a menu button I can push, and command prompt doesn't seem to be one of the options displayed on the screen. I may be overlooking the obvious, and if so I apologize.
Click to expand...
Click to collapse
What T.A.G. was referring to was using the command prompt in Windows. This would also be used in conjunction with having the Android SDK installed in Windows.
Wolf_2 said:
What T.A.G. was referring to was using the command prompt in Windows. This would also be used in conjunction with having the Android SDK installed in Windows.
Click to expand...
Click to collapse
OK, *now* I understand! Told you, dumb questions are my specialty!
Thanks much!
-Mike
The only dumb questions are those that are not asked.
Sent from my Inspire 4G using XDA Premium App.
tribalartgod-
Awesome job!
kimtyson said:
tribalartgod-
Awesome job!
Click to expand...
Click to collapse
Thanks. I've been slacking on a lot of stuff here lately. Bout to go full force on this stuff again soon. (Job and life away from Android takes priority.) Stay tuned.
can this be flashed through cwr?
stryfe2010 said:
can this be flashed through cwr?
Click to expand...
Click to collapse
I have not tried it. So as of right now, the official answer is NO. If you decide to try anyway, it's at your own risk. I'm not responsible if your phone becomes a pretty brick.

My experience rooting the HTC Thunderbolt (And succeeding!)

**NOTE** Make sure to goto setting>applications>development and turn on debug mode and stay awake!
Hello everyone!
This morning I spent a great deal of time trying to root my Thunderbolt looking across many different forums so I decided to post my path to success here to help anyone else out that was in my situation
So the first problem I ran into was I was on the newer .9 firmware. Multiple people told me either 1. You CANT root or 2. You have to downgrade and lose all of your stuff. Heck no was I doing that!
So I was searching through the depths of cyberspace and I came across this:
thunderboltforums[.]com/forum/htc-thunderbolt-development/7743-tool-bypass-downgrade-get-s-off-no-data-wipe.html (It wont let me post a real link
Which is a tool to root without downgrading! I thought "Wow! This is perfect, 5 minutes and I'll be done!" Wrong.
I had much trial and error but I finally got it working so here is what I did.
I extracted the entire DowngradeBypass.zip into its own folder.
Then I ran the RUN-ME.bat and it asked me "If I had the fastboot drivers installed?" I miss read it as "Do you want the fastboot drivers installed?" And I clicked yes out of stupidity. Since I had not tried anything before I did NOT have them installed so the next time I entered "n" and hit enter.
My next problem was that the driver installation of the fastboot drivers failed. The reason being because my phone was plugged in. So either 1. Dont have it plugged in when you start or 2. Unplug it and go to the support_files folder and double click Driver.exe
Once that was installed it said to press enter to continue, this is where I plugged my phone back in and I made sure it was in charge only mode.
Then it took some time (2 mins aprox.) and then It brought up a new window, the revolutionary window, READ what the little box has to say! I then scrolled down to the bottom of the Web Browser it had opened up (On my computer) and click Download for Windows, then you click cancel. And then I entered in my OS, My phone, my HBOOT (Which for me was 1.05) and then my serial number (It says it in the DOS window that is titled revolutionary. After that click Ok and then copy the beta code it gives you. Then right click on the DOS window (The top bar) and go down to Edit and click paste.
Then you hit enter and it does some more stuff (Like 1.5 mins) and then it will ask you if you want to install clockwork recovery mod. Click Y, and hit enter. You want clockwork if you're a noob like me.
Then once it was done the program suddenly closed and I felt abandoned! I really would of loved the Microsoft word paper clip coming up saying "Looks like you're trying to root your phone! Want some help?"
Anyways, on my phone it said revolutionary at the top and FASTBOOT USB a little lower, so I hit the down volume button a couple times until it finally responded. Then I highlighted recovery and hit the power button. Once it was in the recovery window I went to install ZIP from SD-Card and selected Select from SD-Card and then I scrolled ALL the way down where my su.zip should of been. It wasn't.
So I went back through the menus clicking go back until I got to reboot, I rebooted my phone. When it came back on I put it into disk mode, and I went into support_files on my computer in the DowngradeBypass folder and I copied su.zip to the root of my SD-Card. Then I turned off my phone (And unplugged it) and held the power button down WHILE holding the volume down. I then went through the same process as I mentioned above, this time my su.zip WAS there I selected it and then scrolled down to Confirm and it installed!
Then I went back and rebooted my phone and went it came on I went to the market place and downloaded barnicle (Wifi tether, needs root And despite all my set backs, It worked!!!!
So that was my experience everyone I hope it was helpful to at least someone!
DowngradeBypass.zip = awesomness
+1. A friend upgraded to a new thunderbolt runnig 2.3.4. Revolutionary couldnt pull it off. Used the no DowngradeBypass.zip, obtained root, s-off, and cwm. backedup sense, wiped flashed Thundershead 1.4, Gapps, IMO 6.1, and webkitaccel. Runs smooth as butter!
Thanks for this post! What's the best rom with built-in wifi tethering?
where to paste the beta key
Hey Jeremy,
Thanks a lot for the post. I'm hitting a problem on my end though and I'm hoping you can shed some light...
After completing this step:
"Then it took some time (2 mins aprox.) and then It brought up a new window, the revolutionary window, READ what the little box has to say! I then scrolled down to the bottom of the Web Browser it had opened up (On my computer) and click Download for Windows, then you click cancel. And then I entered in my OS, My phone, my HBOOT (Which for me was 1.05) and then my serial number (It says it in the DOS window that is titled revolutionary. After that click Ok and then copy the beta code it gives you."
the DOS window automatically closes and there is nowhere for me to paste the beta key. Any ideas?
Thanks!
mdemonds said:
Hey Jeremy,
Thanks a lot for the post. I'm hitting a problem on my end though and I'm hoping you can shed some light...
After completing this step:
"Then it took some time (2 mins aprox.) and then It brought up a new window, the revolutionary window, READ what the little box has to say! I then scrolled down to the bottom of the Web Browser it had opened up (On my computer) and click Download for Windows, then you click cancel. And then I entered in my OS, My phone, my HBOOT (Which for me was 1.05) and then my serial number (It says it in the DOS window that is titled revolutionary. After that click Ok and then copy the beta code it gives you."
the DOS window automatically closes and there is nowhere for me to paste the beta key. Any ideas?
Thanks!
Click to expand...
Click to collapse
Go to the revolutionary website, and download then run revolutionary.exe again.

[GUIDE] [VIDEO] Various Guides Including Root and ROM reviews

Sticky Worthy?
How To Guides in Video Form:
How To One Click Unlock Bootloader http://www.youtube.com/watch?v=sSVD5b9nAcI&list=UU1J4DKcJXENzC-FkyMU6dow&index=15&feature=plcp
How To Manually Unlock Bootloader http://www.youtube.com/watch?v=sSVD5b9nAcI&list=UU1J4DKcJXENzC-FkyMU6dow&index=15&feature=plcp
One Click DebugFS method: http://www.youtube.com/watch?v=EpuiKIl7lpI&feature=share&list=UU1J4DKcJXENzC-FkyMU6dow
Video Root Guide: http://youtu.be/cuiJYKV2GGU
^^This is just a Visual aid for the method provided by Invisiblek outlined here http://forum.xda-developers.com/showthread.php?t=1756885
How to Update Your Baseband/Modem to latest OTA : http://www.youtube.com/watch?v=K2dQ2kv9kYs&feature=share&list=UU1J4DKcJXENzC-FkyMU6dow
How To Nandroid backup in Cwm Recovery: https://www.youtube.com/watch?v=4zWSK7cO3xg&feature=youtube_gdata_player
How To Unbrick, Unroot, Factory Restore Galaxy S III http://youtu.be/p0T4FO_NZ8Y
How To Easily Backup Apps and Data to Flashable.zip http://youtu.be/OPPoKlu_4qw
How To Install CM9 or CM10: http://youtu.be/f68NgGgrwAQ
How To Back up and Restore IMEI: http://www.youtube.com/watch?v=dl6Ms3oVEDo&feature=share&list=UU1J4DKcJXENzC-FkyMU6dow
How To Use Your SGS3 as a Netflix Remote: http://www.youtube.com/watch?v=JICq0P1Ywg4&feature=share&list=UU1J4DKcJXENzC-FkyMU6dow
Rom Reviews and Install Guides:
JellyWiz Touchwiz Jelly Bean 4.1.1 Rom Review and Install: http://www.youtube.com/watch?v=twDBZg4wkBk&feature=share&list=UU1J4DKcJXENzC-FkyMU6dow
Liquid v2 RC3 Rom Review and Install http://www.youtube.com/watch?v=ieuy5Bx76-Q&feature=share&list=UU1J4DKcJXENzC-FkyMU6dow
AOKP 4.1.1 Rom Review and Install: http://www.youtube.com/watch?v=kjULad8XS-4&feature=share&list=UU1J4DKcJXENzC-FkyMU6dow
MIUI v4.1 Jelly Bean Review and Install for Unlocked Bootloaderhttp://www.youtube.com/watch?v=azkToBXLjig&list=UU1J4DKcJXENzC-FkyMU6dow&index=2&feature=plcp
Cyanogen Mod 10 Jelly Bean for Unlocked Bootloader http://www.youtube.com/watch?v=7nW0SRKxUQk&list=UU1J4DKcJXENzC-FkyMU6dow&index=14&feature=plcp
Clean Rom Full Review and Install For Unlocked Bootloader http://www.youtube.com/watch?v=0PtIKXddfNI&list=UU1J4DKcJXENzC-FkyMU6dow&index=7&feature=plcp
Bean's Custom Stock Rom Review and Install For Unlocked Bootloader http://www.youtube.com/watch?v=napoMpZKCDA&list=UU1J4DKcJXENzC-FkyMU6dow&index=13&feature=plcp
First ROM Stock Stripped by Invisiblek: for Locked Bootloader https://www.youtube.com/watch?v=9Oek_24wEXI&feature=youtube_gdata_player
Cyanogen Mod 10 Rom Review: for Locked Bootloader http://youtu.be/2efLx_iTBDk
AOKP Android Open Kang Project Milestone 6 Review and Install for Locked Bootloader http://youtu.be/ATiFaCssKHs
Synergy Rom (Battery life and Stability) Review and Install for Locked Bootloader http://youtu.be/bj7w2nu_sKk
fix your link. you forgot the opening [ preceding the closing youtube tag.
Could you please do a back-to-stock video as well?
Thanks for doing this. First Samsung phone so it's quite new to me. Appreciate the video, it'll definitely help
Sent from my PC36100 using Tapatalk 2
Always wish these were made for each phone, the devs put so much work into making roms and root methods, but usually skimp on the instructions for those of us who aren't as experienced. Thanks for this
I will try to update this thread with any other videos I make, or I might make a separate thread. Glad its helped though.
Sent from my Galaxy Nexus using xda app-developers app
Thanks for the video. I'll be going through this as quickly as I can get home from work tomorrow!!
Great video, but in your description, to install the SDK using the Java links, I installed the JDK but the SDK install still thinks it's missing, and won't go any further, making me Cancel out. No idea what to do now...no SDK = no ADB commands :-(
minmongoblin said:
Great video, but in your description, to install the SDK using the Java links, I installed the JDK but the SDK install still thinks it's missing, and won't go any further, making me Cancel out. No idea what to do now...no SDK = no ADB commands :-(
Click to expand...
Click to collapse
Alos agree great video and helped me do root in no time at all! However, like you I am unable to get the adb part of the video working. I followed your other video and written instructions to the "t", and I only got as far as..
"adb is not recognized as an internal or external command"
I got the Java JDK to install fine as well as the SDK with all the required installs you said were needed for it to work. I left out all others as I'm not really too familiar with adb is it is. I changed the path, and named folders and files exactly as you did in your video. However I could never get the cmd to show adb devices.
I know the original post stated that we should know how to use it before we try this, but after trying to do research on this for the past 4 hours last night.. I concluded I have no idea what I am doing wrong/nor how to do it properly apparently.
If anyone would be able to possibly give me some assistance that would be great .
Lemonhead8890 said:
Alos agree great video and helped me do root in no time at all! However, like you I am unable to get the adb part of the video working. I followed your other video and written instructions to the "t", and I only got as far as..
"adb is not recognized as an internal or external command"
I got the Java JDK to install fine as well as the SDK with all the required installs you said were needed for it to work. I left out all others as I'm not really too familiar with adb is it is. I changed the path, and named folders and files exactly as you did in your video. However I could never get the cmd to show adb devices.
I know the original post stated that we should know how to use it before we try this, but after trying to do research on this for the past 4 hours last night.. I concluded I have no idea what I am doing wrong/nor how to do it properly apparently.
If anyone would be able to possibly give me some assistance that would be great .
Click to expand...
Click to collapse
Is your usb debugging enabled on your phohne?
When you cd <path to platform-tools>, then type: adb.exe
Does a long list of commands scroll across the screen?
Having the same problem. I see the long list of commands. But when I type "adb devices" nothing is listed.
trginter said:
Having the same problem. I see the long list of commands. But when I type "adb devices" nothing is listed.
Click to expand...
Click to collapse
I haven't tried it myself yet, but it sounds like you don't have the drivers properly installed.
Sent from my Ally (Cant wait to get rid of this POS and replace it with my S3 tomorrow!)
NightxFall said:
I haven't tried it myself yet, but it sounds like you don't have the drivers properly installed.
Sent from my Ally (Cant wait to get rid of this POS and replace it with my S3 tomorrow!)
Click to expand...
Click to collapse
That would be my guess. Put it in USB Debug mode, and plug the phone in, I think it auto-installs the ADB drivers.
Hmm, the phone is in USB Debugging Mode and plugged in, nothing downloaded.
trginter said:
Hmm, the phone is in USB Debugging Mode and plugged in, nothing downloaded.
Click to expand...
Click to collapse
What is the exact output when you type adb devices?
Good to know root is avail
Will try this tomorrow after work
s197 said:
Is your usb debugging enabled on your phohne?
When you cd <path to platform-tools>, then type: adb.exe
Does a long list of commands scroll across the screen?
Click to expand...
Click to collapse
For those having problems with this, look up "how to add a path to the windows command line“. You should not have to CD to a directory to make a command work .
Sent from my SCH-I535
s197 said:
Is your usb debugging enabled on your phohne?
When you cd <path to platform-tools>, then type: adb.exe
Does a long list of commands scroll across the screen?
Click to expand...
Click to collapse
Yes, usb debugging was on when I tried to do this. I usually always just leave it on honestly.
I guess I should have been more clear about where I was at, but yes i did the
cd platform-tools .. enter.. then adb.exe.. and thats when I got the 'adb' is not an internal or external command. I dont know where I messed up along the way... . I feel pretty confident I did everything correctly.
However there was one difference i did notice. On the path stated in the guide it says system32 something then you list the path to platform tools and whatnot.... but mine had something /windowspowershell/ or something like that.
I went back to the start and deleted my drivers and reinstalled them but deleted the jdk and sdk for the time being.. Maybe ill try again soon if I can figure it out better.
I believe this will help a lot of you. Thanks goes to Adrynalyne....
http://forum.xda-developers.com/showthread.php?t=879701
Lemonhead8890 said:
Yes, usb debugging was on when I tried to do this. I usually always just leave it on honestly.
I guess I should have been more clear about where I was at, but yes i did the
cd platform-tools .. enter.. then adb.exe.. and thats when I got the 'adb' is not an internal or external command. I dont know where I messed up along the way... . I feel pretty confident I did everything correctly.
However there was one difference i did notice. On the path stated in the guide it says system32 something then you list the path to platform tools and whatnot.... but mine had something /windowspowershell/ or something like that.
I went back to the start and deleted my drivers and reinstalled them but deleted the jdk and sdk for the time being.. Maybe ill try again soon if I can figure it out better.
Click to expand...
Click to collapse
It sounds like you're not moving to the right directory. Check to see where your adb file is, on the new SDK it's in platform-tools but if you downloaded ADB from a long time ago, it's in another folder (I think tools, but it's been a while).
What I would do is navigate to your adb file from "my computer". At the top, under address, it will show you the path you need to type. For instance, for me, I open my computer, C: drive, Android folder, then platform-tools. So my path would be:
Code:
cd C:\Android\platform-tools
Everyone's path is different depending on where you put your files.

Categories

Resources