I had trouble unlocking the bootloader on my iMac but got it to work.
Just posting this to help out my fellow Mac Heads who've turned from the evil iPhone.
Unlocking your bootloader will probably or definitely void your warranty. I am in no way responsible for you screwing up your beautiful Rezound. (K, that's out of the way.)
Prep work:
1. I had an old Android SDK and couldn't get it to work.
HTC Dev site stated I only needed adb and fastboot for this (but I don't remember when I actually used an adb command). Anyhoo... download the latest Android SDK from the link provided by HTC Dev from the link at the right side (as your following the process). Save and uncompress it in the root of your hard drive and rename it ' android ' (no single quotes) - this step just makes it easier.
2. Check if there is a 'platform-tools' folder. If not then in the 'tools' folder just double click the 'android' file and it'll open Terminal and run the Android SDK Manager app. I only checked the 'Android SDK Platform-tools' for installation but you can install whatever else you want. Click the button 'Install (x) package' close to the bottom right. After it's done you'll find the 'platform-tools' folder and that's where adb will be. (Like I said, I don't remember using any ./adb commands, though)
NEXT FOLLOW THE HTC WEBSITE STEPS
(this is on the website)
1. After you've pulled the battery and placed it back in, hold VolumeDown and Power button to restart. At white screen, select Fastboot with volume rocker and hit the power button. Connect cable from phone to mac.
2. Download the Mac version of the Fastboot in Step 5 of the HTC Website. Uncompress it and place it in the root of the 'android' folder. Rename it 'fastboot' (without single quotes) from 'fastboot-mac'.
3. Open a new Terminal window (Applications/Utitilies).
Type: cd /android
(that's if you had placed the android folder at the root of your hard drive) or you can type: cd then <space> then drag the android folder from a finder window into the terminal window
hit return
Type: ./fastboot oem get_identifier_token
4. Per the instructions at the HTC Website Step 9, Copy the Identifier token text.
(I copied and pasted it into a text app and deleted the "(bootloader)" text in there, then copied the resulting text.)
5. Paste into HTC Website Step 10 inside the "My Device Identifier Token:" box and hit submit.
If it goes through you'll get a Congratulations webpage and your unlock file will be sent to your registered email.
6. Download the Unlock_code.bin file into the android folder where the 'fastboot' file should be.
7. Go back into the Terminal window.
Type: ./fastboot flash unlocktoken Unlock_code.bin
8. Your phone should go off and come up with an Unlock Your Phone screen. Use the volume rocker to select Yes and hit the Power button. Should restart and you're good to go.
Good luck!
TIP:
Originally Posted by AshtonTS
to avoid having to use the ./ (this should probably be done after you set up adb and fasboot but before you start the Actual unlock part)
Code:
nano ~/.bash_profile
and then add
Code:
export PATH=${PATH}:/Users/yourusername/wherever/adbfolder
Will unlocking on OS X also result in a factory reset at the end?
feralicious said:
Will unlocking on OS X also result in a factory reset at the end?
Click to expand...
Click to collapse
Of course.
What Slacker101 said. Yup
I get a permission denied when i type '/android/fastboot oem get_identifier_token'.. any way around that? Also, i enabled myself at root user and admin.
joeyrey said:
I get a permission denied when i type '/android/fastboot oem get_identifier_token'.. any way around that? Also, i enabled myself at root user and admin.
Click to expand...
Click to collapse
Did you check the permissions on the file? Hopefully you can read/write/execute them. I don't see any mention of needing to be root so I'd assume you're safe without su'ing.
joeyrey said:
I get a permission denied when i type '/android/fastboot oem get_identifier_token'.. any way around that? Also, i enabled myself at root user and admin.
Click to expand...
Click to collapse
Since you're on a shared computer, just login as the main administrator member. If you had to enter a password when you dropped in the Android SDK into the root of your drive your specific login will probably have permission problems. Not a big deal, just annoying.
Or you can drop the android folder onto your Desktop and cd into that. Then you would just modify it to /Users/<yourusername>/Desktop/android/fastboot oem get_identifier_token for example. But you may not have to if you've already cd into the folder anyway.
When I follow your steps, I get the following message:
cannot load unlock_code.bin
Please help me
lloydcabraham said:
When I follow your steps, I get the following message:
cannot load unlock_code.bin
Please help me
Click to expand...
Click to collapse
What step are you on?
edit: I'm guessing you're on step 7. Did you download the unlock file you received via email from htc dev directly to where the fastboot directly is in, i.e., /android/ or to a different place?
lloydcabraham said:
When I follow your steps, I get the following message:
cannot load unlock_code.bin
Please help me
Click to expand...
Click to collapse
Are you currently in the same directory as unlock_code.bin when you run the fastboot command?
xjedi said:
What step are you on?
edit: I'm guessing you're on step 7. Did you download the unlock file you received via email from htc dev directly to where the fastboot directly is in, i.e., /android/ or to a different place?
Click to expand...
Click to collapse
Yes, I'm on step 7. All other steps worked perfectly.
---------- Post added at 02:22 PM ---------- Previous post was at 02:18 PM ----------
MrSmith317 said:
Are you currently in the same directory as unlock_code.bin when you run the fastboot command?
Click to expand...
Click to collapse
I copied the file from HTC's email and placed it in the Android folder which is in the root of my hard drive. The fastboot command I'm using is located there also.
FYI. I did downloaded the android sdk manager app since I didn't have a platforms-Tools folder. Now there's 2 fastboot files. One located in the root of the android folder and one located in the Platform-Tools folder where the adb command is.
lloydcabraham said:
Yes, I'm on step 7. All other steps worked perfectly.
---------- Post added at 02:22 PM ---------- Previous post was at 02:18 PM ----------
I copied the file from HTC's email and placed it in the Android folder which is in the root of my hard drive. The fastboot command I'm using is located there also.
FYI. I did downloaded the android sdk manager app since I didn't have a platforms-Tools folder. Now there's 2 fastboot files. One located in the root of the android folder and one located in the Platform-Tools folder where the adb command is.
Click to expand...
Click to collapse
when you typed in the command was it unlock_code.bin or Unlock_code.bin (capital 'U')? I'm not sure but it may be case sensitive (whatever is the exact case name for the unlock file). Try it out anyway.
I cut and paste the command directly from step 7. HTC's attached Unlock_code.bin is capitalized as is the copied command from step 7.
Guys, Thanks for your help. Had to get a new code. Works perfect now!!
You guys are great.
Now it say's sending unlock token... Now writing unlock token. How long should take? Phone hasn't rebooted or anything.
Stuck on writing unlock token. What should I do?
lloydcabraham said:
I cut and paste the command directly from step 7. HTC's attached Unlock_code.bin is capitalized as is the copied command from step 7.
Guys, Thanks for your help. Had to get a new code. Works perfect now!!
You guys are great.
Now it say's sending unlock token... Now writing unlock token. How long should take? Phone hasn't rebooted or anything.
Stuck on writing unlock token. What should I do?
Click to expand...
Click to collapse
Ride it out for a little while. It should reboot and come up with the unlock screen on your phone.
Thanks xjedi. How long would you say I should wait before I know somethings wrong? If it's stuck, can I unplug my phone and redo while stuck at "writing unlock token"?
lloydcabraham said:
Thanks xjedi. How long would you say I should wait before I know somethings wrong? If it's stuck, can I unplug my phone and redo while stuck at "writing unlock token"?
Click to expand...
Click to collapse
I'm always hesitant to disconnect when Terminal says its writing to. Always afraid of getting a Pretty Phone Brick. LOL If it isn't responsive then what can you do.
That being said I'd wait ten minutes. Quit Terminal then technically you'd just have to do that last command. I'd disconnect the phone for a few seconds then reconnect though. Open up Terminal and try again.
xjedi said:
I'm always hesitant to disconnect when Terminal says its writing to. Always afraid of getting a Pretty Phone Brick. LOL If it isn't responsive then what can you do.
That being said I'd wait ten minutes. Quit Terminal then technically you'd just have to do that last command. I'd disconnect the phone for a few seconds then reconnect though. Open up Terminal and try again.
Click to expand...
Click to collapse
Yeah, I know what you mean. I rebooted then went back to the bootloader. As soon as I plugged the phone back in, it finished unlocking successfully. Thanks guys.
Trying to unlock bootloader on my Rezound. NO LUCK AT ALL. Tried it on a Vista PC, and also on a Mac OS X Lion computer, both have android sdk, fastboot (fastboot-mac), and any time the terminal creates a token, htcdev.com says it is invalid. HTC has been of my help. Token I get is:
<<<< Identifier Token Start >>>>
INFO1DF1016E1D1C11FBFE98455CE697DF68
INFO8051B4762C985ECAD8331A9B63DD5375
INFO8DFCDF353626D4E462B2F945A18A53B0
INFO5EF5FB207C39FB48E031952A71770A8C
INFOF2C918518DCD78BFE18825B6C0A35ABF
INFO4678BC4569ED798FBBD4CDAAC41E7C10
INFO16F48B643DD0B0A3C147AD909EA150FC
INFO3C938D0FBC250FDE57A90F7ADE28429D
INFO9EE5AE71DE5CAB290DEBA46CAC643E0F
INFO7686317EB5AEEEA7F11731016D6A003D
INFO3ECB04E09A2AE0705CA7F3E1C47D07C1
INFO30953D12B5B94C2F23250B59ED347F21
INFO887821F1101440BB8FA61F6BC4C44FCD
INFOEE7885B9DFB86491E658CEB43E78713C
INFOEF6B4F5CE5EEAB20041BA337ED187A36
INFO3DE37720EDB4CCF91EFC7F135389286E
INFO<<<<< Identifier Token End >>>>>
This info, when pasted into htcdev.com gives me the following error...
Error Code: Invalid Bootloader Token Length.
Error Reason: The submitted Token appears to be the wrong length and won't work.
Any ideas? Thanks! Jon
mactechnm said:
Trying to unlock bootloader on my Rezound. NO LUCK AT ALL. Tried it on a Vista PC, and also on a Mac OS X Lion computer, both have android sdk, fastboot (fastboot-mac), and any time the terminal creates a token, htcdev.com says it is invalid. HTC has been of my help. Token I get is:
<<<< Identifier Token Start >>>>
INFO1DF1016E1D1C11FBFE98455CE697DF68
INFO8051B4762C985ECAD8331A9B63DD5375
INFO8DFCDF353626D4E462B2F945A18A53B0
INFO5EF5FB207C39FB48E031952A71770A8C
INFOF2C918518DCD78BFE18825B6C0A35ABF
INFO4678BC4569ED798FBBD4CDAAC41E7C10
INFO16F48B643DD0B0A3C147AD909EA150FC
INFO3C938D0FBC250FDE57A90F7ADE28429D
INFO9EE5AE71DE5CAB290DEBA46CAC643E0F
INFO7686317EB5AEEEA7F11731016D6A003D
INFO3ECB04E09A2AE0705CA7F3E1C47D07C1
INFO30953D12B5B94C2F23250B59ED347F21
INFO887821F1101440BB8FA61F6BC4C44FCD
INFOEE7885B9DFB86491E658CEB43E78713C
INFOEF6B4F5CE5EEAB20041BA337ED187A36
INFO3DE37720EDB4CCF91EFC7F135389286E
INFO<<<<< Identifier Token End >>>>>
This info, when pasted into htcdev.com gives me the following error...
Error Code: Invalid Bootloader Token Length.
Error Reason: The submitted Token appears to be the wrong length and won't work.
Any ideas? Thanks! Jon
Click to expand...
Click to collapse
Paste this into the window instead of what you have
<<<< Identifier Token Start >>>>
1DF1016E1D1C11FBFE98455CE697DF68
8051B4762C985ECAD8331A9B63DD5375
8DFCDF353626D4E462B2F945A18A53B0
5EF5FB207C39FB48E031952A71770A8C
F2C918518DCD78BFE18825B6C0A35ABF
4678BC4569ED798FBBD4CDAAC41E7C10
16F48B643DD0B0A3C147AD909EA150FC
3C938D0FBC250FDE57A90F7ADE28429D
9EE5AE71DE5CAB290DEBA46CAC643E0F
7686317EB5AEEEA7F11731016D6A003D
3ECB04E09A2AE0705CA7F3E1C47D07C1
30953D12B5B94C2F23250B59ED347F21
887821F1101440BB8FA61F6BC4C44FCD
EE7885B9DFB86491E658CEB43E78713C
EF6B4F5CE5EEAB20041BA337ED187A36
3DE37720EDB4CCF91EFC7F135389286E
<<<<< Identifier Token End >>>>>
That should work for your device
(if it works hit thanks, please)
mactechnm said:
Trying to unlock bootloader on my Rezound. NO LUCK AT ALL. Tried it on a Vista PC, and also on a Mac OS X Lion computer, both have android sdk, fastboot (fastboot-mac), and any time the terminal creates a token, htcdev.com says it is invalid. HTC has been of my help. Token I get is:
<<<< Identifier Token Start >>>>
INFO1DF1016E1D1C11FBFE98455CE697DF68
INFO8051B4762C985ECAD8331A9B63DD5375
INFO8DFCDF353626D4E462B2F945A18A53B0
INFO5EF5FB207C39FB48E031952A71770A8C
INFOF2C918518DCD78BFE18825B6C0A35ABF
INFO4678BC4569ED798FBBD4CDAAC41E7C10
INFO16F48B643DD0B0A3C147AD909EA150FC
INFO3C938D0FBC250FDE57A90F7ADE28429D
INFO9EE5AE71DE5CAB290DEBA46CAC643E0F
INFO7686317EB5AEEEA7F11731016D6A003D
INFO3ECB04E09A2AE0705CA7F3E1C47D07C1
INFO30953D12B5B94C2F23250B59ED347F21
INFO887821F1101440BB8FA61F6BC4C44FCD
INFOEE7885B9DFB86491E658CEB43E78713C
INFOEF6B4F5CE5EEAB20041BA337ED187A36
INFO3DE37720EDB4CCF91EFC7F135389286E
INFO<<<<< Identifier Token End >>>>>
This info, when pasted into htcdev.com gives me the following error...
Error Code: Invalid Bootloader Token Length.
Error Reason: The submitted Token appears to be the wrong length and won't work.
Any ideas? Thanks! Jon
Click to expand...
Click to collapse
Delete all the "INFO". Then copy that and paste again.
Edit: Looks like AshtonTS beat me to it.
Related
This is the method I used to S-Off several devices (8 in total) on Windows 7 64 bit.
Remember, Team Unlimited does not recommend that you use any OS that is not supported as the drivers can cause some issues.
I have included a method that will test whether your drivers in your current setup will perform in a way that reduces the chance of all hell breaking loose.
Before starting, make sure you have downloaded and installed the HTC drivers for your phone and have Adb downloaded. A great place to get this is from “Team fireballas FakeCid AUTOMATIC bootloader unlock” thread.
We will need this file for a later process as well. (File Download)
Once downloaded, unzip it to C:\Root.
Verifying that your drivers are working correctly. (Typed commands are in red)
1) Attach your phone to you computer with the supplied USB cable.
2) Enable USB Debugging (Settings>Developer Options>USB Debugging)
3) Open a command prompt and navigate to the location you extracted the adb files to by typing: cd\
Then type: cd c:\Root\stuff
Your Prompt should read:
c:\Root\stuff>
4) Now type adb devices
You should see the following output in the command prompt.
C:\ Root\stuff >adb devices
List of devices attached
HT26KS311633 device
Your device will have a different device ID than what is listed above. Just make sure it shows a device ID and device listed after it.
5) Now type: adb reboot bootloader
At this point your phone should reboot into the bootloader with Fastboot selected.
6) Type: fastboot devices
You should see the following output in the command prompt.
C:\inc4>fastboot devices
HT26KS311633 fastboot
Ensure that your device is listed. Your device will have a different device ID than what is listed above. Just make sure it shows a device ID and fastboot listed after it.
7) Type: fastboot reboot
You should see the following output in the command prompt.
C:\inc4>fastboot reboot
rebooting...
finished. total time: 0.070s
Your phone should be rebooting.
You have now verified that your drivers are working correctly even after rebooting into fastboot.
At this point I cannot give you alternative instructions per Team Unlimited. So follow the directions listed HERE.
When you reach step 12 which states:
“Temproot your phone via any method available - we cannot help with this step and it is REQUIRED!”
Follow the following steps that were originally written by captainrewind in the “Team fireballas FakeCid AUTOMATIC bootloader unlock” thread.
Go to Settings -> Connect to PC and change Default connection type to Disk drive and disable Ask me.
Navigate to the folder in the command Prompt by typing
cd c:\Root\stuff
Now that you're there, type:
adb devices
If your phone pops up in the list, you're good to go!
Next, type
adb restore fakebackup.ab
DO NOT click OK to the restore on the device just yet!
Now type:
adb shell "while ! ln -s /data/local.prop /data/data/com.android.settings/a/file99; do :; done"
(errors will appear, ignore)
Accept the restore on the device, then type:
adb reboot
(At this time, you are temprooted, and the phone UI will be in an unusable state, with temproot shell.)
After reboot type:
adb shell
Verify that the prompt is "#" (meaning root) or "$" (meaning normal user). If it's not "#", please start over.
You can now return to Team Unlimited’s instructions and continue with step 13.
This should take you the rest of the way to S-Off.
*Madmoose* said:
I have included a method that will test whether your drivers in your current setup will perform in a way that reduces the chance of all hell breaking loose.
Click to expand...
Click to collapse
Excellent suggestion and great advice. Always make sure your computer can recognize your device in all device states before attempting root.
I found the hard way on a Kindle Fire and now always do this test (a couple of times) to make sure the device being rooted can be seen in all states by the PC. For whatever reason, my (original) Kindle Fire has a different USB Enum for each state and my Windows 7 64-Bit computer didn't recognize it in fastboot which caused a lot of irritation.
This is helpful but I believe unlimited specifically asked not to have any other how to threads
Sent from my Nexus 7 using Tapatalk 2
This isn't a how to about Unlimited's process. And frankly, they can request anything they want, but they will not control other peoples threads. They were talking about their own thread.
*Madmoose* said:
Next, type
adb restore fakebackup.ab
DO NOT click OK to the restore on the device just yet!
Now type:
adb shell "while ! ln -s /data/local.prop /data/data/com.android.settings/a/file99; do :; done"
(errors will appear, ignore)
Accept the restore on the device, then type:
adb reboot
Click to expand...
Click to collapse
I'd like to comment on this part, since it threw me off a bit and scared the daylights out of me.
After you issue the "while..." command, you'll get infinitely scrolling errors/warnings, or at least I did in Ubuntu. Just ignore them, nothing is wrong. While they are infinitely repeating in your terminal, just accept the restore on the phone and they stop. I don't remember the exact text of the error, but if someone could put it here that would probably be helpful to anyone wondering.
Very cool. Thanks madmoose!
Is It Working with HTC ONE V (GSM) ???
No dude this is the incredible 4G threads
I am so going to do this. Soon. Hawk might have an Ecliptic release some day.
Linch89 said:
No dude this is the incredible 4G threads
Click to expand...
Click to collapse
Will this make my laptop s-off
Sent from my Nexus 7 using Tapatalk 2
Only if your laptop is an Incredible 4G...
Add me to the list of S-OFF via Win7 64bit. I restored my Viper TWRP backup and all is running smootly. Now, I am off to customize my bootloader with RegawMOD Bootloader Customizer.
Used a modified version of this to achieve s-off but what really helped me was the "Verifying that your drivers are working correctly." section. When I had tried unlocking earlier I keep getting stuck in the error looping screen when restoring the fakebackup. This little set of instructions pointed me in the right directions for getting the drivers installed correctly.
Many thanks MadMoose and Happy New Year! :victory:
Many thanks to MadMoose. Everything worked for me on Win7 64bit as well, and would have worked more smoothly if I had done it your way
Yesssssssssssssssssss
Wow what a journey, used it on my 64 bit computer per another post here that gave a very nice detailed instructions. had to relock, temproot, s off, flash recovery, and then restore... but i would do it 100 times again! thanks everyone for your activeness in this community, hopefully it continues to grow
Has anyone tried to get s-off with Windows 8 x64 yet? I copied in the drivers, tried all the commands, and they replied normally. Will I brick my phone if I try?
I'm afraid it won't work unlimited said that 64 win7 wasn't officially supported it just happens to work
It may work but unlimited won't help/support you if you have problems.
bberryhill0 said:
It may work but unlimited won't help/support you if you have problems.
Click to expand...
Click to collapse
I'm just wondering if it doesn't work, then am I bricked? Or can I just pull the battery and restart?
spectre559 said:
I'm just wondering if it doesn't work, then am I bricked? Or can I just pull the battery and restart?
Click to expand...
Click to collapse
Went ahead with s-off in win 7 x64. Success!
I installed R3 rom but my wifi cant be turned on. Latest I found that also my USB internet passthrough is not working. I got hint from one member but I absolutely dont know how to perform this.
flash the boot.img inside the R3's zip file using fastboot.
Commands:
fastboot erase cache
fastboot flash boot boot.img
How to flash something inside zip file? do I have to extract it and put it into root?
How to execute commands at all? Where to put them? What do I need to perform? I am total noob and every simple step I ever done took me a day. Now I am stuck. IF someone knows how to make this, please help.
Thank you.
First question do you have ADB installed?
Then you need to unpack boot.img from rom.zip.
When I get my answer we'll go further.
nlooooo said:
First question do you have ADB installed?
Then you need to unpack boot.img from rom.zip.
When I get my answer we'll go further.
Click to expand...
Click to collapse
I should have ADB, because I was rooting my phone month ago and ADB was required. How do I find out? I have SDK tools and i have adb.exe, adbwinapi.dll, fastboot.exe, recovery.img in C\Android. Actually I was trying to connect phone through USB and start adb.exe but it just popped out, scrolled down fast and closed (it was looking like command prompt- black window).
And I unpacked boot.img from R3.zip to my sdcard
Copy boot.img to android folder (where you have SDK platform tools installed), reboot phone to fastboot, connect it to PC and issue commands:
fastboot flash boot boot.img
fastboot reboot-bootloader
fastboot erase cache
And then reboot your phone.
Copy boot.img to android folder (where you have SDK platform tools installed), reboot phone to fastboot, connect it to PC and issue commands:
fastboot flash boot boot.img
fastboot reboot-bootloader
fastboot erase cache
And then reboot your phone.
Actually I tought this is the way, but let me tell you what is happening:
1.Turned phone off
2.entered fastboot on my phone
3.opened adb.exe in my Android-sdk/platform-tools folder
4.the adb window just opened for a 1second, everything scrolled down fast
5.adb window closed.
This is the reason why I need help, but really thank you for taking care
janickonajkrajsi said:
Copy boot.img to android folder (where you have SDK platform tools installed), reboot phone to fastboot, connect it to PC and issue commands:
fastboot flash boot boot.img
fastboot reboot-bootloader
fastboot erase cache
And then reboot your phone.
Actually I tought this is the way, but let me tell you what is happening:
1.Turned phone off
2.entered fastboot on my phone
3.opened adb.exe in my Android-sdk/platform-tools folder
4.the adb window just opened for a 1second, everything scrolled down fast
5.adb window closed.
This is the reason why I need help, but really thank you for taking care
Click to expand...
Click to collapse
You shouldn't click the adb. exe, open cmd and type the commands there.
Sent from my awesome fridge
I'm just wandering how did you manage to unlock bootloader at all.
MaartenXDA said:
You shouldn't click the adb. exe, open cmd and type the commands there.
Sent from my awesome fridge
Click to expand...
Click to collapse
yeah, I also did this according to this post http://forum.xda-developers.com/showthread.php?t=1752270
and this post http://forum.xda-developers.com/showthread.php?t=860421
but Cmd could not recognize this. I tried "fastboot devices" and this was not recognized too.
Then I reinstalled HTC drivers and then tried again. So then I was trying to open adb.exe and then you told me to issue command through cmd and here we are. sorry I am real noob in android things. I was using iphone and everything worked like magic
Isnt there a way to perform this "boot.img flashing" through recovery mod? I mean without the usb connection and without the cmd black hole
janickonajkrajsi said:
yeah, I also did this according to this post http://forum.xda-developers.com/showthread.php?t=1752270
and this post http://forum.xda-developers.com/showthread.php?t=860421
but Cmd could not recognize this. I tried "fastboot devices" and this was not recognized too.
Then I reinstalled HTC drivers and then tried again. So then I was trying to open adb.exe and then you told me to issue command through cmd and here we are. sorry I am real noob in android things. I was using iphone and everything worked like magic
Click to expand...
Click to collapse
First use the command "cd C:\Android"
After that do the commands again.
Be sure you've uninstalled HTC Sync (NOT the drivers) before doing this.
Sent from my awesome fridge
nlooooo said:
I'm just wandering how did you manage to unlock bootloader at all.
Click to expand...
Click to collapse
He didn't get your point...
Sent from my toaster using TapaToast HD
Thank you guys, now it is working.
Quote:
Originally Posted by nlooooo View Post
I'm just wandering how did you manage to unlock bootloader at all.
He didn't get your point...
Yeah it was meant like "hod did this stupid noob even managed to unlock bootloader at all. I got his point, and the right answer was "step by step guide" so actually You didnt got my point.
Dont forget that things that are automatic and obvious to you, are not obvious to everyone. My grandma is learning to work with computers and when she asks me how to send an email, I have to tell her "grab a mouse, then move it there........"
)))))))
Does not matter, thank you guys!
Once you learn to use adb and fastboot it's always the same, so my point was that you've never learned how to use it, you just typed what you saw, without any wish to learn.
Point is to try and learn, not to ask again.
Nobody said you're stupid, just lazy.
Cant get the R3 working. HTC Sense UI crashed error at lock screen
I flashed the sense revolution r3 today but could not get it working.
The following are the issues faced.
1) It starts without installing the mods package, but lacks the full sense widgets like htccontacts, htc calender etc.
2) when i flashed the r3 mod package, it gets stuck at the lock screen. The Sense UI crashes.
3) Without the mods, i faced another bug in people widget. it crashes when i click the phone dialer from it.
I am currently on sense r3.
Please help me install it in full.
now that we know rumrunner works on this device(some pointers in this thread),and the process can leave you with a tampered banner in your bootloader,i thot there might be a demand for this. this will legitimately change the flag that causes hboot to display the tampered banner,without the inconvenience of having to run an RUU.
this is NOT a patched or hex edited hboot. this is legintimately restoreing the tampered flag to its "untampered" setting
*you must be s off.
*you must have superuser installed(see this thread if you need help installing superuser)
read this:
this will not work if your s on
the usual disclaimers:
i have tested this my my rezound,but use this info at your own risk. if it melts your phone into a little pile of plastic goo,its not my fault.
credits
-beaups for schooling me on echo command protocol
request that you do not repack this into any one clicks or tools without permission. i spent a great deal of time comparing before and after hex edits to find this flags location
IF you are an advanced user with adb/fastboot set up and some basic knowlede of the cmd window,you can skip to #2
1)set up adb
-download this file
-install drivers: if you have htc sync installed,you should allready have drivers. if not,you can install htc sync,or install these modified htc drivers from revolutionary (driver mirror)
-unzip your miniadb_v1031.zip file. this is native funtionality in windows 7. you otherwise may need a utility such as "7-zip" to extract,or unzip it. place the unzipped folder onto the root of your C drive on your PC. root means the top level,not inside any folders. so just copy and paste,or drag and drop the folder onto C with everything else that is there. you may want to rename it to "miniadb_m7" since youll be putting some device specific files in here.
-open a command window. on windows 7,click the start bubble in the lower left and type "command" in the search box. xp i believe is similar or the same. doing this should open a small black command window.
-change to your miniadb_m7 directory. type the following at the prompt in your cmd window:
cd c:\miniadb_m7
your command promt should change to "c:miniadb_m7>" provided you: 1)unzipped the miniadb_v1031 zip file,and 2)put the folder on your c drive,and 3)entered the name of the folder correctly ("miniadb_m7" in this case)
-now make sure usb debugging is checked in developer options(you will need to turn it on first),and plug your phone into your PC with a usb cable
-make sure your phone is being recognized- type:
adb devices
if your drivers are installed correctly,this should return your phones serial number. you should hear the "found device" noises when you plug your phone in. if it starts installing drivers,wait for it to finish before typing the adb devices command.
if you get your serial number back,then enter this command:
adb reboot bootloader
this should take your phone to the "fastboot" screen,wich is white with colored letters. this is one mode of your bootloaders interactive modes. at the top youll see fastboot devices as confirmation youre in fastboot.
now enter:
fastboot devices
again,this should return your phones serial number. you should hear the "found device" noises when you plug your phone in. if it starts installing drivers,wait for it to finish before typing the adb devices command.
if you get your serial number back,you can enter the following to boot back to the phones OS:
fastboot reboot
and now,youve installed adb/fastboot and tested youre phones drivers. if at either spot,you have trouble and dont get your serial number back,there is some sort of connection issue. use these steps to troubleshoot:
troubleshooting connectivity issues:
-try a reboot of the PC
-try different usb cables and ports
-dont use a usb hub
-dont use usb 3.0
-make sure nothing capable of comunicating with the phone is enabled and running. htc sync,pdanet,easy tether,and even itunes have all been known to cause issues.
-windows 8 has been known to have issues. try a windows 7 or older machine
failing the above,
-i use these drivers for fastboot and adb(donwload and run as admin): http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe (mirror)
failing that,try manually updating the drivers in the following manner:
-put the phone in fastboot mode(select fastboot from the hboot menu)
-open device manager on the PC
-plug in phone,watch for it to pop up in device manager.
-update drivers with device manager,pointing the wizard to the extracted
driver download folder from above
note that you can check the connectivity of the phone,and make sure drivers are working by in the following manner:
-open cmd window. change to directory containing adb/fastboot utilities
-adb with the phone in the booted OS,usb debug enabled,enter:
adb devices in a cmd window
-fastboot with phone in fastboot,enter:
fastboot devices in cmd window
in either case,a properly connected phone with working drivers installed should report back the phones serial number.
Click to expand...
Click to collapse
this process,in your cmd window,should look something like this:
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Scott>[COLOR="red"]cd c:\miniadb_m7[/COLOR]
c:\miniadb_m7>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
FAxxxxxxxxxx device
c:\miniadb_m7>[COLOR="red"]adb reboot bootloader[/COLOR]
c:\miniadb_m7>[COLOR="red"]fastboot devices[/COLOR]
FAxxxxxxxxxx fastboot
c:\miniadb_m7>[COLOR="red"]fastboot reboot[/COLOR]
rebooting...
finished. total time: 0.037s
c:\miniadb_m7>
2)reset your "tampered flag"
enter the following:
adb devices
adb shell
su (if needed to get a # prompt)
echo -ne '\x00' | dd of=/dev/block/mmcblk0p7 bs=1 seek=4391940
(i would very strongly recomend you copy/paste this)
exit
(exit a second time if you need to to get back to a normal > prompt)
adb reboot bootloader
verify tamered is gone
(yes the pics are of m7. ill try and get some rezound pics up later)
Worked like a charm! Thank you for this. I'm out of thanks for today but I will catch you tomorrow
So... What about on JuopunutBear HBoot? Do I need to flash the stock one first?
Sent from my Nexus 4 using Tapatalk
acejavelin said:
So... What about on JuopunutBear HBoot? Do I need to flash the stock one first?
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
The jpbear hboot is ignoring the flag,so the banner isn't displayed.
You will need to be on a stock hboot to witness the banner disappear,but it actually doesn't matter what you're running to reset it.
Sent from my HTC6435LVW using Tapatalk
scotty1223 said:
The jpbear hboot is ignoring the flag,so the banner isn't displayed.
You will need to be on a stock hboot to witness the banner disappear,but it actually doesn't matter what you're running to reset it.
Sent from my HTC6435LVW using Tapatalk
Click to expand...
Click to collapse
So this might be a silly question, is there any real reason to do this? It won't make any functional difference to my knowledge.
So other than making the banner go away, is there any beneficial use to doing this?
Sent from my Nexus 4 using Tapatalk
You would not want to send in the phone for warranty repair with the tampered banner,but running a signed ruu will make it go away as well.
Other than that, there is no real reason. its completely cosmetic,it doesn't affect any functionality. For some folks,its presence really gets under their skin. Personally,I kind of like the tempered banner.
you actually can turn it back on with a similar command
Sent from my HTC PG09410 using Tapatalk 2
This seems pretty cool!
My only comment is that one need not do all of the fastboot-related driver business, because your command is done using only adb. (Yes, sadly, this is relevant for post-Win 7 versions of Windows, which often can see devices via adb but not fastboot...)
cheers,
john
jrredho said:
This seems pretty cool!
My only comment is that one need not do all of the fastboot-related driver business, because your command is done using only adb. (Yes, sadly, this is relevant for post-Win 7 versions of Windows, which often can see devices via adb but not fastboot...)
cheers,
john
Click to expand...
Click to collapse
I've purposely stayed with windows 7,since phone stuff is 95% of what i use my pc for. you are correct,you don't need fastboot at all for this,after verifying the banner is gone,one can simply manually reboot from the bootloader menu.
Sent from my HTC PG09410 using Tapatalk 2
So removing the tampered flag is only helpful if you need to turn in your phone for warranty reasons..... However if it still says S-off aren't they still going to know it's been tampered with?
Worked great!!!! I know there's not much reason to do this but fun to tinker. Thanks for the step by step instructions. Verified tampered flag removed. See before and after pictures.
Sent from my ADR6425LVW using xda app-developers app
Uncleheff said:
So removing the tampered flag is only helpful if you need to turn in your phone for warranty reasons..... However if it still says S-off aren't they still going to know it's been tampered with?
Click to expand...
Click to collapse
Pre-release phones legitmately come s off,so its existance does not imply an otherwise stock,locked and non-tampered phone has been messed with.
Plus,you can turn s on if you want to.
Works like a charm. Thanks!
Hello,
first i must apologize for my English but, i´ve got my phone back from display repair and i have it now out of warranty so i decide to make a root but i cant find step-by-step guide to do that. I´am on 6.0.1 android, Kernel 3.10.49, type VDF-995NB02-CZ10d.
No flash, no bootloader unlock, anything, i get it back after hard reset.
Can anyone help me please? I rooting for first time no Samsung device. I have some experience but i cannot downgrade to 5.1.1 to use Kingroot or MobileGo to root. After the root i want update back to 6.0.1 or use custom ROM.
i searched on Modaco and here but i cannot find guide what i can undestand and be sure if that will work for me.
Thanks for all replies :angel:
Krejdlis said:
Hello,
first i must apologize for my English but, i´ve got my phone back from display repair and i have it now out of warranty so i decide to make a root but i cant find step-by-step guide to do that. I´am on 6.0.1 android, Kernel 3.10.49, type VDF-995NB02-CZ10d.
No flash, no bootloader unlock, anything, i get it back after hard reset.
Can anyone help me please? I rooting for first time no Samsung device. I have some experience but i cannot downgrade to 5.1.1 to use Kingroot or MobileGo to root. After the root i want update back to 6.0.1 or use custom ROM.
i searched on Modaco and here but i cannot find guide what i can undestand and be sure if that will work for me.
Thanks for all replies :angel:
Click to expand...
Click to collapse
Take a backup of your data before proceeding further.
Try this,
Download adb and Koush Universal adb driver and install them on ur pc, always install the driver first and don't install the drivers adb setup asks u to install.
Run command prompt as administrator.
Open the folder in c drive where adb is installed, u can use file explorer for this.
Press Shift+right click and select open command window here.
Enable USB debugging on your phone and connect it to the pc by a USB cord.
Enter command "adb devices" without quotation marks.
If it shows some device connected, only then proceed further.
Enter command " adb reboot bootloader"
Enter command " fastboot devices", if it shows some device to be connected, only then proceed further.
Enter command " fastboot oem unlock".
Ur phone may then ask for final confirmation on the phone screen, select yes.
When procedure completes, type "fastboot reboot" and ur phone will reboot.
U can now use Kingoroot for pc or any other tool for rooting.
Augustoandro said:
Take a backup of your data before proceeding further.
Try this,
Download adb and Koush Universal adb driver and install them on ur pc, always install the driver first and don't install the drivers adb setup asks u to install.
Run command prompt as administrator.
Open the folder in c drive where adb is installed, u can use file explorer for this.
Press Shift+right click and select open command window here.
Enable USB debugging on your phone and connect it to the pc by a USB cord.
Enter command "adb devices" without quotation marks.
If it shows some device connected, only then proceed further.
Enter command " adb reboot bootloader"
Enter command " fastboot devices", if it shows some device to be connected, only then proceed further.
Enter command " fastboot oem unlock".
Ur phone may then ask for final confirmation on the phone screen, select yes.
When procedure completes, type "fastboot reboot" and ur phone will reboot.
U can now use Kingoroot for pc or any other tool for rooting.
Click to expand...
Click to collapse
Am i in the right folder? :laugh:
from cmd i get this after first two commands
C:\Program Files (x86)\ClockworkMod\Universal Adb Driver>fastboot devices
'fastboot' is not recognized as an internal or external command,
operable program or batch file.
Using Win10
Krejdlis said:
Am i in the right folder? :laugh:
from cmd i get this after first two commands
C:\Program Files (x86)\ClockworkMod\Universal Adb Driver>fastboot devices
'fastboot' is not recognized as an internal or external command,
operable program or batch file.
Using Win10
Click to expand...
Click to collapse
Have you installed adb? If yes, then proceed further.
You are in the wrong folder. The correct path should be C:\adb
Then Shift+right click
Select "Open command window here"
Hello,
C:\platform-tools-latest-windows\platform-tools>adb reboot bootloader
phone rebooting
C:\platform-tools-latest-windows\platform-tools>fastboot devices
after this command it shows nothing
can you please make a steps for ADB drivers instalation, i dont know if i made it properly.
Thanks
Krejdlis if you are able to root please tell me how you did it - currently have the same issue
SomeoneAnonymous said:
Krejdlis if you are able to root please tell me how you did it - currently have the same issue
Click to expand...
Click to collapse
Hi, still in progress, i trying everything but still without succes. Someone know how to easily downgrade to 5.1.1 with this phone?
Now it give me this : <waiting for any device>
Hey all i dont know what the deal is but ive got an lg g5 that just will not boot to the bootloader. I've tried factory resetting it and all the methods to get to bootloader just reboots the phone fully. Adb reboot booloader, key combos, nothing seems to work. Any ideas??
First, connect your smartphone with your PC; plug in the USB cord in order to establish the connection.
On your computer access the Android SDK folder.
From there open a command prompt window: press and hold the Shift keyboard key while right clicking on any blank space.
Next, in the cmd window type “adb reboot bootloader” and wait while the bootloader mode is displayed on your smartphone
That's basically what I did and worked first time..make sure the adb and fastboot package is installed and open the command window from that folder
russy23 said:
First, connect your smartphone with your PC; plug in the USB cord in order to establish the connection.
On your computer access the Android SDK folder.
From there open a command prompt window: press and hold the Shift keyboard key while right clicking on any blank space.
Next, in the cmd window type “adb reboot bootloader” and wait while the bootloader mode is displayed on your smartphone
That's basically what I did and worked first time..make sure the adb and fastboot package is installed and open the command window from that folder
Click to expand...
Click to collapse
Did all that.. I mean I've flashed custom recoveries and roms to other phones before and never really had a problem i couldn't google..this has me stumped. It simply refuses to even access the bootloader.
If it helps it was a koodo phone and is running the latest official patch from lg on nougat. The only thing i could find online was that sprint supposedly removed all access to the bootloader on theirs, but i cant find any real info on that either. It reboots when i send the adb reboot bootloader but its like fastboot just isn't there..?? It reboots right back to the android home screen. Ive tried all possible key combos as well... Ugh
Which model is it..mines the h850
Ive got the h831
I think I've sort of answered my own question. From browsing the forums it appears the Canadian variant has the bootloader locked down and inaccessible, which would explain a lot..lol.. I really hate when this kind of thing is done to the consumer...ugh. Back to xiaomi i guess lol
bproulx said:
... has the bootloader locked down and inaccessible, which would explain a lot..lol.. I really hate when this kind of thing is done to the consumer...ugh. Back to xiaomi i guess lol
Click to expand...
Click to collapse
Interesting - my xianomi hat an locked bootloader and i had to ask for permission (for the phone I bought!) to unlock the bootloader.
LG is also locked, but the unlocking procedure is way easier.
logg.sar said:
Interesting - my xianomi hat an locked bootloader and i had to ask for permission (for the phone I bought!) to unlock the bootloader.
LG is also locked, but the unlocking procedure is way easier.
Click to expand...
Click to collapse
Unless you're from Canada apparently ..lol