Related
trying to unlock my bootloader and im not able to run the fastboot package i have unzipped to my desktop in C:\Users\chris\Desktop\fastboot-package but first try i entered the wrong unique code and have tried numerous times and cant seem to to get it going again gotta be somthing so simple ill slap my mom when i get the answer
hchris24 said:
ill slap my mom when i get the answer
Click to expand...
Click to collapse
Respect your mum!
Just for that............no answer!
For those all so senisitive plenty of respect for my mom its my noobisim not hers help is much is much appreciated
Do you have ADB installed? Try installing ADB then unzipping the fastboot package into that folder. There are really good directions on xda, or google.
But if you get to the point where you fastboot oem unlock. There should be the unique id number there that you use to unlock...
Also try to reflash the pudding and the fastboot oem unlock command.
Sent from my MB860 using Tapatalk
What happens when you try?
Tried all that but unzipping to adb folder only to desktop will try that tomorrow morn when I get home from work and will repost thanks for the reply
I got all the way to the warranty warning screen entered the id but must of entered.it incorrectly it unlock aborting tried again with redoing reflash all over again and problem is when entering.the first command in adb shell it says wrong path specified that's where im stuck now
What I did was extract these files to : c:\atrix
pudding_183.sbf
adb
adbwinapi.dll
adbwinusbapi.dll
fastboot
IHOP_bell.sbf
moto-fastboot
recovery
I'm not sure if I needed every file but I got done by changing my directory to
cd c:\atrix
then fastboot oem unlock
wrote down the code
then fastboot oem unlock (your # here)
fastboot reboot
Make sure you enter it exactly as it shows on the screen, and yes that does include capitol letters.
That's the only tip I can think of.
Sent from my MB860 using XDA App
Thanks for the last two posts ill try all post back in the morn
this is what i get now after moving everything to one folder cd C:\Users\chris\Desktop\fastboot-package is not recognized as internal or external,
operable command or batch file
hchris24 said:
the first command in adb shell it says wrong path specified that's where im stuck now
Click to expand...
Click to collapse
I could be mis-reading this so if I am I apologize however it seems that you are using the wrong program you need to use the fastboot exe not adb which would be the reason for getting the error messages. (if that is the case)
Prolly not your case, but I extracted the files to a folder so when I typed in their destination, the powers that be couldn't see them where I told them to look...
Sent from my MB860 using XDA Premium App
thanks for the help gentlemen i am now unlocked
Phone: Evo 3D
Android Version: 2.3.4
Software number: 2..08.651.3
Hboot: 1.50
S-On
Done:
1) HTC boot unlock (http://htcdev.com/bootloader)
2) http://forum.xda-developers.com/showthread.php?t=1239821
-was able to push flies over to phone, but command line "fastboot flash recovery recovery.img" resulted in errors
3) tried to downgrade Hboot using RUU and got an error telling me that my current version was most up to date
Common Threads:
1) http://forum.xda-developers.com/showthread.php?t=1388740
-I downloaded Superuser, titanium back up, and a random program that claimed to verify rooting -- all said I was NOT rooted
2) http://forum.xda-developers.com/showthread.php?t=1307982
-My true goal is to install wifi teathering and titanium backup, I don't care much for custom roms
Forum Confusion:
Unlocking the boot loader does not seem to be the same as rooting, but when I've search through the forums people offer one as a solution to the other.
I'd really appreciate any feedback
thanks guys,
-Nave
navenine said:
Phone: Evo 3D
Android Version: 2.3.4
Software number: 2..08.651.3
Hboot: 1.50
S-On
Done:
1) HTC boot unlock (http://htcdev.com/bootloader)
2) http://forum.xda-developers.com/showthread.php?t=1239821
-was able to push flies over to phone, but command line "fastboot flash recovery recovery.img" resulted in errors
3) tried to downgrade Hboot using RUU and got an error telling me that my current version was most up to date
Common Threads:
1) http://forum.xda-developers.com/showthread.php?t=1388740
-I downloaded Superuser, titanium back up, and a random program that claimed to verify rooting -- all said I was NOT rooted
2) http://forum.xda-developers.com/showthread.php?t=1307982
-My true goal is to install wifi teathering and titanium backup, I don't care much for custom roms
Forum Confusion:
Unlocking the boot loader does not seem to be the same as rooting, but when I've search through the forums people offer one as a solution to the other.
I'd really appreciate any feedback
thanks guys,
-Nave
Click to expand...
Click to collapse
Try this, starting over. You shouldnt run into any hiccups.
tailsthecat3 said:
Try this, starting over. You shouldnt run into any hiccups.
Click to expand...
Click to collapse
I received Error [155] Unknown Error
Display From Phone:
***Unlocked***
Shooter XC ship S-ON RL
HBoot-1.50.0000
eMMC-boot
Aug 7 2011, 10:21:40
RUU
Security fail!
Update Fail!
when it rebooted after recovery I still had all of my user data
navenine said:
I received Error [155] Unknown Error
Display From Phone:
***Unlocked***
Shooter XC ship S-ON RL
HBoot-1.50.0000
eMMC-boot
Aug 7 2011, 10:21:40
RUU
Security fail!
Update Fail!
when it rebooted after recovery I still had all of my user data
Click to expand...
Click to collapse
Ive been through this. Relock(lock) it, run the RUU, then proceed with the instructions I linked.
I was never able to run the RUU while the device was 'unlocked'.
tailsthecat3 said:
Ive been through this. Relock(lock) it, run the RUU, then proceed with the instructions I linked.
I was never able to run the RUU while the device was 'unlocked'.
Click to expand...
Click to collapse
I've been trying to lock it back through the CMD, I wrote a little batch file (and I've manually typed it):
cd c:\android
fastboot oem lock
but after it runs a line shows up as follows:
< waiting for device >
I have USB debugging mode on, and I've tried it with the sd card both mounted and unmounted, I have all the drivers, and adb commands are effective...
do you know what I'm missing?
Thanks again for the help,
-Evan
hey im trying to use the ruu to get back to stock , just re locked the phone , and im STILL getting errors with ruu, its saying Update Failed : Hboot version is older , im on hboot 1.5000 .........Im losing my mind trying to get this thing back to stock and out of htc screen logo bootlooping.........any ideas?
navenine said:
I've been trying to lock it back through the CMD, I wrote a little batch file (and I've manually typed it):
cd c:\android
fastboot oem lock
but after it runs a line shows up as follows:
< waiting for device >
I have USB debugging mode on, and I've tried it with the sd card both mounted and unmounted, I have all the drivers, and adb commands are effective...
do you know what I'm missing?
Thanks again for the help,
-Evan
Click to expand...
Click to collapse
That tells me that youre not in fastboot on your device. I can dupe the same message with my phone disconnected from the pc, then I plug it in in fastboot, and all is good.
Please reinstall the drivers needed but it sounds like youre good. On occasion, I wont be able to flash some things or a file cant load. A reboot of the pc fixes those rare cases for me. Also, refreshing the folders where the files are located.
I also had issues using fastboot, flashing things to the evo because I had my nexus connected for a tether.
If I could do it for you, I would. Hopefully I can help.
tailsthecat3 said:
That tells me that youre not in fastboot on your device. I can dupe the same message with my phone disconnected from the pc, then I plug it in in fastboot, and all is good.
Please reinstall the drivers needed but it sounds like youre good. On occasion, I wont be able to flash some things or a file cant load. A reboot of the pc fixes those rare cases for me. Also, refreshing the folders where the files are located.
I also had issues using fastboot, flashing things to the evo because I had my nexus connected for a tether.
If I could do it for you, I would. Hopefully I can help.
Click to expand...
Click to collapse
this just got even worse, I uninstalled the drivers, and now I can't reinstall them. I can't find them. My computer wont recognize my phone at all. I've tried to goto the device manager and find them online automatically, and I've tried the google USB drivers from the extra folder from the SDK Manager...
if you can point me toward the USB drivers that'd be great, but regardless, what your saying is I need to connect my phone while its in the bootloader? not once its booted? or are you saying I need to boot my phone through the bootloader selecting "fastboot" first?
thanks again
-Nave
http://forum.xda-developers.com/showpost.php?p=17083782&postcount=1
Theyre all in there. Youll need those files to root but you should already have the htc sync drivers installed, plus the android usb drivers. You can remove htc sync after installation but keep the drivers.
Boot into hboot and connect it, it may recognize the hardware. Then select fastboot. Fastboot is 'hot swappable' we'll call it, so you can be in fastboot and disconnect and reconnect your usb cable and youll see when its connected-- itll read 'fastboot usb'.
try here
http://developer.android.com/sdk/win-usb.html
tailsthecat3 said:
http://forum.xda-developers.com/showpost.php?p=17083782&postcount=1
Theyre all in there. Youll need those files to root but you should already have the htc sync drivers installed, plus the android usb drivers. You can remove htc sync after installation but keep the drivers.
Boot into hboot and connect it, it may recognize the hardware. Then select fastboot. Fastboot is 'hot swappable' we'll call it, so you can be in fastboot and disconnect and reconnect your usb cable and youll see when its connected-- itll read 'fastboot usb'.
try here
http://developer.android.com/sdk/win-usb.html
Click to expand...
Click to collapse
Great, I have all the drivers, my phone is relocked, and I'm running the RUU prog now, I'll post in a few minutes to say what happens
thanks for all the help so far, I really do appreciate it!
-Nave
navenine said:
Great, I have all the drivers, my phone is relocked, and I'm running the RUU prog now, I'll post in a few minutes to say what happens
thanks for all the help so far, I really do appreciate it!
-Nave
Click to expand...
Click to collapse
Good. Ive done the process on two different 3D's, a few times. If you follow the instructions, its almost as easy to root as my nexus s was.
tailsthecat3 said:
http://forum.xda-developers.com/showpost.php?p=17083782&postcount=1
Theyre all in there. Youll need those files to root but you should already have the htc sync drivers installed, plus the android usb drivers. You can remove htc sync after installation but keep the drivers.
Boot into hboot and connect it, it may recognize the hardware. Then select fastboot. Fastboot is 'hot swappable' we'll call it, so you can be in fastboot and disconnect and reconnect your usb cable and youll see when its connected-- itll read 'fastboot usb'.
try here
http://developer.android.com/sdk/win-usb.html
Click to expand...
Click to collapse
I pushed everything over, got it into the fastboot USB and then typed the "fastboot flash recovery recovery.img" command line
my script was:
sending 'recovery' <5068 KB>...
Okay [ 1.207s]
writing 'recovery'...
<bootloader> signature checking...
FAILED <remote:signature verify fail>
finished. total time: 1.855s
any ideas?
tailsthecat3 said:
Good. Ive done the process on two different 3D's, a few times. If you follow the instructions, its almost as easy to root as my nexus s was.
Click to expand...
Click to collapse
Great! thank you soooo much I finally have everything working the way I want it!
haha it seems so much easier now that I know what I was supposed to do
navenine said:
Great! thank you soooo much I finally have everything working the way I want it!
haha it seems so much easier now that I know what I was supposed to do
Click to expand...
Click to collapse
Where were you going wrong? And what'd you do to correct it? So everyone knows, in case they encounter the same issues.
Sent from my Google Nexus S 4G via XDA Premium
Good Idea:
Problem 1)
The RUU wouldn't run
I had this problem because I had already unlocked the the bootloader
I had to re-lock it in order to fix it
Problem 2)
Then The Recovery.img would push through because I forgot to re-unlock the phone
what I did that made it easier:
I wrote a little batch file to run the scripts - a batch file is a command prompt command list set. you open a notepad, type in the the command lists and save it with a .bat file extension...
so I would install all the files and then make a batch file with the following:
cd C:\android
adb push recovery.img /sdcard/
adb push su-2.3.6.3.zip /sdcard/
adb reboot bootloader
pause
fastboot flash recovery recovery.img
change the C:\andriod to whatever your directory set was
and when the batch program runs
anyway good luck to anyone who ends up here, and thanks again tailsthecat3 for the great help
navenine said:
Good Idea:
Problem 1)
The RUU wouldn't run
I had this problem because I had already unlocked the the bootloader
I had to re-lock it in order to fix it
Problem 2)
Then The Recovery.img would push through because I forgot to re-unlock the phone
what I did that made it easier:
I wrote a little batch file to run the scripts - a batch file is a command prompt command list set. you open a notepad, type in the the command lists and save it with a .bat file extension...
so I would install all the files and then make a batch file with the following:
cd C:\android
adb push recovery.img /sdcard/
adb push su-2.3.6.3.zip /sdcard/
adb reboot bootloader
pause
fastboot flash recovery recovery.img
change the C:\andriod to whatever your directory set was
and when the batch program runs
anyway good luck to anyone who ends up here, and thanks again tailsthecat3 for the great help
Click to expand...
Click to collapse
I appreciate that, thank you.
Ok, so I've read through the LOOK HERE FIRST thread, I've downloaded RSD Lite (can I still use version 5.5?, can't seem to find a link for 5.6), and I downloaded Motorola_PreRelease_Mobile_Drivers_5.2.1_32bit (again can't seem to find or don't know if I need newer drivers, and don't know what to do with the drivers). I also downloaded the derpunlock.sbf (should this file be only 10.2mb's?). I'm assuming qbking77's tutorial vid is obsolete now since the pudding thread is closed, but can I still follow that video?. Can someone point me in the right direction here? I can't brick this phone.
Airwolf79 said:
Ok, so I've read through the LOOK HERE FIRST thread, I've downloaded RSD Lite (can I still use version 5.5?, can't seem to find a link for 5.6), and I downloaded Motorola_PreRelease_Mobile_Drivers_5.2.1_32bit (again can't seem to find or don't know if I need newer drivers, and don't know what to do with the drivers). I also downloaded the derpunlock.sbf (should this file be only 10.2mb's?). I'm assuming qbking77's tutorial vid is obsolete now since the pudding thread is closed, but can I still follow that video?. Can someone point me in the right direction here? I can't brick this phone.
Click to expand...
Click to collapse
10.2 is correct.
I used this file two days ago:
Code:
Start RSD lite
Reboot phone into RSD mode (power+vol down)
Flash derpunlock.sbf
It may require a battery pull to get the phone to properly reboot
Reboot phone into fastboot mode
Open command prompt in the moto-fastboot folder and do the following:
moto-fastboot devices
moto-fastboot oem unlock
moto-fastboot erase recovery
moto-fastboot flash recovery recovery-red-photon3.img
moto-fastboot reboot
Kevets said:
10.2 is correct.
I used this file two days ago:
Code:
Start RSD lite
Reboot phone into RSD mode (power+vol down)
Flash derpunlock.sbf
It may require a battery pull to get the phone to properly reboot
Reboot phone into fastboot mode
Open command prompt in the moto-fastboot folder and do the following:
moto-fastboot devices
moto-fastboot oem unlock
moto-fastboot erase recovery
moto-fastboot flash recovery recovery-red-photon3.img
moto-fastboot reboot
Click to expand...
Click to collapse
Ok, I don't know why this is so difficult to me. I've flashed tons of roms when I had my evo, and I've tried a few locked roms on this phone, flashed via bootstrap, but this unlock process has me stumped. Where do I get the correct derpunlock.sbf if don't have it? Do I have to flash moto-fastboot from my pc?
From here,
Start RSD Lite on your computer
Reboot phone into RSD mode: VOL down/Power. Use VOL down to scroll though options til you see "RSD" then VOL up to enable.
Connect phone to computer.
Flash derpunlock.sbf.
Close RSD Lite and disconnect phone.
Double click "Command Prompt" shortcut in the "Unlock" folder.
In the Command Prompt window type moto-fastboot oem unlock
Look for the UNIQUE ID number and copy it.
Type moto-fastboot oem unlock YOUR_UNIQUE_ID_THAT_YOU_JUST_COPIED (fastboot should reply <bootloader> Device is now unlocked )
Kevets said:
From here,
Start RSD Lite on your computer
Reboot phone into RSD mode: VOL down/Power. Use VOL down to scroll though options til you see "RSD" then VOL up to enable.
Connect phone to computer.
Flash derpunlock.sbf.
Close RSD Lite and disconnect phone.
Double click "Command Prompt" shortcut in the "Unlock" folder.
In the Command Prompt window type moto-fastboot oem unlock
Look for the UNIQUE ID number and copy it.
Type moto-fastboot oem unlock YOUR_UNIQUE_ID_THAT_YOU_JUST_COPIED (fastboot should reply <bootloader> Device is now unlocked )
Click to expand...
Click to collapse
I understood that part, but where do I get the derpunlock.sbf? Is it inlcuded in the Root-Unlock-Relock w 198_7sbf?
Airwolf79 said:
I understood that part, but where do I get the derpunlock.sbf? Is it inlcuded in the Root-Unlock-Relock w 198_7sbf?
Click to expand...
Click to collapse
I'm sorry, I misunderstood your first reply. So I do have the correct derpunlock.sbf then. Ok, I'll give it a whirl. Thank you.
Airwolf79 said:
I'm sorry, I misunderstood your first reply. So I do have the correct derpunlock.sbf then. Ok, I'll give it a whirl. Thank you.
Click to expand...
Click to collapse
Where is the "Unlock" folder located?
Airwolf79 said:
Where is the "Unlock" folder located?
Click to expand...
Click to collapse
I'm pretty sure it's in lokifish's unlock relock pack. If I'm not mistaken it's just a folder that holds everything you need to unlock, so it makes it easier on you.
Sent from my MB855 using xda app-developers app
Can somebody please post or point me to a working link so I can download the files necessary to unlock my bootloader. It appears every link I've tried is either broken or the files are not available anymore...
Sent from my MB855 using xda app-developers app
Here is the unlock and fastboot. Link is temporary.
https://www.box.com/s/92d6ac95e13febbe000d
Kevets said:
Here is the unlock and fastboot. Link is temporary.
https://www.box.com/s/92d6ac95e13febbe000d
Click to expand...
Click to collapse
Why temporary?
My personal account. Can't guarantee they'll be there forever.
Sent from my MB855 using xda premium
Thanks guys, I was able to get it unlocked without the unlock folder. I just used my pc's command prompt directed to fastboot in the sdk tools folder. Much appreciated, now rom flashin like crazy time.
Kevets said:
My personal account. Can't guarantee they'll be there forever.
Sent from my MB855 using xda premium
Click to expand...
Click to collapse
Okay, thanks much.
Airwolf79 said:
Ok, so I've read through the LOOK HERE FIRST thread, I've downloaded RSD Lite (can I still use version 5.5?, can't seem to find a link for 5.6), and I downloaded Motorola_PreRelease_Mobile_Drivers_5.2.1_32bit (again can't seem to find or don't know if I need newer drivers, and don't know what to do with the drivers). I also downloaded the derpunlock.sbf (should this file be only 10.2mb's?). I'm assuming qbking77's tutorial vid is obsolete now since the pudding thread is closed, but can I still follow that video?. Can someone point me in the right direction here? I can't brick this phone.
Click to expand...
Click to collapse
follow like how qbking's video says just instead of the huge sbf file he flashes in the video you just flash derpunlock.sbf simple
Okay, so I got hboot 2.09 unlocked. I then proceeded to follow QBKing77 instructions for rooting and installing openrecovery. I downloaded the root files from the link he provides. When I type in "fastboot flash recovery openrecovery-twrp-2.3.1.0-jewel.img" and hit enter, it tells me error: cannot load fastboot flash recovery openrecovery-twrp-2.3.1.0-jewel.img,: Unkown Error. Can anyone offer any suggestions here? Thanks.
cmparramore said:
Okay, so I got hboot 2.09 unlocked. I then proceeded to follow QBKing77 instructions for rooting and installing openrecovery. I downloaded the root files from the link he provides. When I type in "fastboot flash recovery openrecovery-twrp-2.3.1.0-jewel.img" and hit enter, it tells me error: cannot load fastboot flash recovery openrecovery-twrp-2.3.1.0-jewel.img,: Unkown Error. Can anyone offer any suggestions here? Thanks.
Click to expand...
Click to collapse
Do you have android SDK instaslled?
bigdaddy619 said:
Do you have android SDK instaslled?
Click to expand...
Click to collapse
Yes I actually went back through the entire process, and checked the path to make sure it was installed correctly. Rebooted the computer and the phone, but still getting unknown error message.
try this open your sdk folder and press shift and right click platform tools and select open cmd window here
that will put you in a writeable folder
Unfortunately I do not get that option. Running windows XP.
hmmmm
is the .img file in your platform tools folder?
drivers installed?
does your pc recognize your phone when you plug the USB in?
---------- Post added at 05:47 AM ---------- Previous post was at 05:36 AM ----------
try downloading this it has all the files you need
once you open cmd window point to this folder
http://d-h.st/5zT
Yes, Yes & Yes
try this
DOH!! Dang, it helps if you use the right directory. I am such a dunce. Thanks for all the help and sorry for being such a goonhead, maybe I need some more coffee!!
hahaha no worries
hey do you know if there coming up with a s-off for hboot 2.09
cmparramore said:
Yes, Yes & Yes
Click to expand...
Click to collapse
Worked for me. and I'm hboot 2.09 also. I don't have windows xp but when I open the sdk directory. hold shift and right click I get a prompt saying "open command window here" I then issue the fastboot flash recovery openrecovery-twrp-2.3.3.0-jewel.img command. it flashes just fine. I think you're missing a step or two.
Please take a look at my thread on rooting/superuser/TWRP installs. It's a pretty good guide. I tried to take the mystery out of this process.
http://forum.xda-developers.com/showthread.php?t=2038123
I am having issues rooting via qbking77's method on Youtube.
I'm stuck at the 5:42 mark where I need to mount USB storage via Teamwin / TWRP recovery.
The 'Mount Cache/Mount SD Card/Mount Internal' aren't' checked on my phone and I can't check them manually. When I click on 'Mount USB Storage'. My computer pops up a message telling me that 'You need to format the disk drive in F:before you can use it. I'm not sure what to do next.
Any suggestions? Thanks.
Thanks this forum helped me find my problem while following qbking77 video on how to root. I realized after quite a few tries that the twrp img file had changed a bit since the video was posted. When bigdaddy619 check for file I found file to be openrecovery to have some different numbers.
Also the actual root file towards the end of the video name/version had changed also. Little details make a big difference.
Im having an issue trying to install openrecovery as well. Ive followed all of qbking77's instructions in the videos. Im running HBOOT 2.09 which is already unlocked. I have SDK tools and everything as well. When i get to the step to install openrecovery, I go to the folder containing the file and shift+right click and open a cmd window. This is what I get:
C:\Users\Jeremy\Desktop\Root_HTC_EVO_LTE>fastboot flash recovery openrecovery-tw
rp-2.5.5.0-jewel.img
< waiting for device >
sending 'recovery' (8196 KB)...
And thats it. It locks up and doesn't go any further. I've tried several times and retraced my steps through the whole install procedure with the same result. Can you fellas help me out?
PooPCovington said:
Im having an issue trying to install openrecovery as well. Ive followed all of qbking77's instructions in the videos. Im running HBOOT 2.09 which is already unlocked. I have SDK tools and everything as well. When i get to the step to install openrecovery, I go to the folder containing the file and shift+right click and open a cmd window. This is what I get:
C:\Users\Jeremy\Desktop\Root_HTC_EVO_LTE>fastboot flash recovery openrecovery-tw
rp-2.5.5.0-jewel.img
< waiting for device >
sending 'recovery' (8196 KB)...
And thats it. It locks up and doesn't go any further. I've tried several times and retraced my steps through the whole install procedure with the same result. Can you fellas help me out?
Click to expand...
Click to collapse
When you type adb devices and hit enter, what happens?
Sent from my EVO using xda premium
FinZ28 said:
When you type adb devices and hit enter, what happens?
Sent from my EVO using xda premium
Click to expand...
Click to collapse
When I type "adb devices" with my phone connected and in bootloader menu this is what i get:
C:\Users\Jeremy\Desktop\Root_HTC_EVO_LTE>adb devices
List of devices attached
C:\Users\Jeremy\Desktop\Root_HTC_EVO_LTE>
Not sure if that's what i'm supposed to get, but if I instead type "fastboot devices" I get this:
C:\Users\Jeremy\Desktop\Root_HTC_EVO_LTE>fastboot devices
HT25PS403929 fastboot
C:\Users\Jeremy\Desktop\Root_HTC_EVO_LTE>
PooPCovington said:
When I type "adb devices" with my phone connected and in bootloader menu this is what i get:
C:\Users\Jeremy\Desktop\Root_HTC_EVO_LTE>adb devices
List of devices attached
C:\Users\Jeremy\Desktop\Root_HTC_EVO_LTE>
Not sure if that's what i'm supposed to get, but if I instead type "fastboot devices" I get this:
C:\Users\Jeremy\Desktop\Root_HTC_EVO_LTE>fastboot devices
HT25PS403929 fastboot
C:\Users\Jeremy\Desktop\Root_HTC_EVO_LTE>
Click to expand...
Click to collapse
My bad, forgot you were in fastboot. Looks like everything is working as it should, though, so I can't think of why you would be having the problems you are
Sent from my EVO using xda premium
FinZ28 said:
My bad, forgot you were in fastboot. Looks like everything is working as it should, though, so I can't think of why you would be having the problems you are
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Anyone else have any ideas? I've rooted this phone before in the past and never had a problem unlocking and rooting or unrooting and relocking so this is most peculiar. I've tried qbking77's method, i've also tried other tutorials out there as well as attempting to use other versions of openrecovery but it just won't root.......
PooPCovington said:
Anyone else have any ideas? I've rooted this phone before in the past and never had a problem unlocking and rooting or unrooting and relocking so this is most peculiar. I've tried qbking77's method, i've also tried other tutorials out there as well as attempting to use other versions of openrecovery but it just won't root.......
Click to expand...
Click to collapse
Try uninstalling everything HTC from your PC
reboot PC and device
re-install drivers including HTC Sync(you can delete it afterwards and the drivers will remain)
plug in your device via usb cable it should install the drivers again also boot into the bootloader drivers should install again
You should be good to go now
Hello fellow Android users,
I am here to ask for your help.
Just to be clear, my phone is an HTC Desire 601 locked with FIDO, use to have Android 4.4.2, Zara_UL, Unlocked bootloader, S-ON and no OS installed.
My HTC Desire 601 has had a rough week.
Everything went well for unlocking the bootloader, rooting, installing new recovery.
Then I wanted to go S-OFF, but Firewater told me the current kernel was blocking the exploit.
So I decided to flash KofilaKernel for my device and try again. The install went well,
only problem was I wiped my cache and system and now, NO MORE OS INSTALLED and still S-ON.
Couldn't use Firewater anymore...
So I tried installing custom ROM and also tried going back to stock, miserably failing.
A. I tried flashing InsertCoin custom ROM wich failed because of S-ON (forgive noobishness)
B. I tried using "fastboot boot" command that made possible flashing custom ROM with S-ON.
I was counting on this one, but had problems too : Most recoveries wouldn't boot (ClockWorkMod several versions, TWRP several versions) except one TWRP recovery wich booted, but the touch screen WAS NOT ACTIVATED. Tried using side buttons with no luck, and power button just locked the screen. I have heard that Google has changed the fastboot boot for newer android versions and that you had to add something to the command like :
"fastboot -c "lge.kcal=0|0|0|x" boot recovery.img"
This example is for Nexus 4 I think, but I don't know the one for Desire 601... I tried it and it wouldn't boot.
C. I have tried "fastboot flash system system.img" with stock image. Had an error saying not enough memory available.
I wiped everything with TWRP and with CLCKWRKMOD : System, cache, dalvik cache, etc... tried again to flash system with no luck.
D. I have tried the Telus RUU.exe file. Told me I had the wrong RUU for my phone and to find the right one, wich doesn't exist for Android 4.4.2 as far as I know.
E. I have tried flashing several versions of 4EXT recovery to get SmartFlash, but it is not compatible with HTC Desire 601.
There I am.
Please help a brother with unusable new phone LOL.
Thanks a bunch for any help.
black-venomz
black-venomz said:
Hello fellow Android users,
I am here to ask for your help.
Just to be clear, my phone is an HTC Desire 601 locked with FIDO, use to have Android 4.4.2, Zara_UL, Unlocked bootloader, S-ON and no OS installed.
My HTC Desire 601 has had a rough week.
Everything went well for unlocking the bootloader, rooting, installing new recovery.
Then I wanted to go S-OFF, but Firewater told me the current kernel was blocking the exploit.
So I decided to flash KofilaKernel for my device and try again. The install went well,
only problem was I wiped my cache and system and now, NO MORE OS INSTALLED and still S-ON.
Couldn't use Firewater anymore...
So I tried installing custom ROM and also tried going back to stock, miserably failing.
A. I tried flashing InsertCoin custom ROM wich failed because of S-ON (forgive noobishness)
B. I tried using "fastboot boot" command that made possible flashing custom ROM with S-ON.
I was counting on this one, but had problems too : Most recoveries wouldn't boot (ClockWorkMod several versions, TWRP several versions) except one TWRP recovery wich booted, but the touch screen WAS NOT ACTIVATED. Tried using side buttons with no luck, and power button just locked the screen. I have heard that Google has changed the fastboot boot for newer android versions and that you had to add something to the command like :
"fastboot -c "lge.kcal=0|0|0|x" boot recovery.img"
This example is for Nexus 4 I think, but I don't know the one for Desire 601... I tried it and it wouldn't boot.
C. I have tried "fastboot flash system system.img" with stock image. Had an error saying not enough memory available.
I wiped everything with TWRP and with CLCKWRKMOD : System, cache, dalvik cache, etc... tried again to flash system with no luck.
D. I have tried the Telus RUU.exe file. Told me I had the wrong RUU for my phone and to find the right one, wich doesn't exist for Android 4.4.2 as far as I know.
E. I have read about 4EXT recovery and SmartFlash, but the only way to get 4EXT recovery seems to be through app and I don't have any OS so it's impossible.
There I am.
Please help a brother with unusable new phone LOL.
Thanks a bunch for any help.
black-venomz
Click to expand...
Click to collapse
I'd just reinstall a rom based off of your current firmware and then you need to copy the boot.img out of it and flash in bootloader. The command you'll want to use is:
fastboot flash boot boot.img
Be cautious trying to run KK roms on JB firmware as you'll have issues with the radio and touch, bare minimum. Only ways to update firmware are via being S-Off and doing a firmware update of just the essentials or find a KK RUU for your phone, if it is available.
es0tericcha0s said:
I'd just reinstall a rom based off of your current firmware and then you need to copy the boot.img out of it and flash in bootloader. The command you'll want to use is:
fastboot flash boot boot.img
Be cautious trying to run KK roms on JB firmware as you'll have issues with the radio and touch, bare minimum. Only ways to update firmware are via being S-Off and doing a firmware update of just the essentials or find a KK RUU for your phone, if it is available.
Click to expand...
Click to collapse
So a ROM based on my current firware wouldn't need S-OFF to be installed ? Can I install stock ROM via recovery even if S-ON ?
Do you know where I could find such thing ?
Many thanks.
black-venomz
black-venomz said:
So a ROM based on my current firware wouldn't need S-OFF to be installed ? Can I install stock ROM via recovery even if S-ON ?
Do you know where I could find such thing ?
Many thanks.
black-venomz
Click to expand...
Click to collapse
Correct, you can install a rom while S-On, as long as you install the boot.img separately. You can install a rom based off of stock, but you won't be able to do the official RUU type rom from it unless there is an RUU zip for your phone (some HTCs have this, but most are just via an exe of a PC) but that would actually go through the bootloader instead of recovery.
es0tericcha0s said:
Correct, you can install a rom while S-On, as long as you install the boot.img separately. You can install a rom based off of stock, but you won't be able to do the official RUU type rom from it unless there is an RUU zip for your phone (some HTCs have this, but most are just via an exe of a PC) but that would actually go through the bootloader instead of recovery.
Click to expand...
Click to collapse
Ok great !
So I have access to a stock ROM apparently. I can't post links yet, but if you look up on Google "htcdesire 601 stock rom" you will find a google docs page with the stock ROM for desire 601 4.4.2.
Would you be king enough to walk me through the steps to achieve this ? There are many .img files in this folder and I am far from an expert.
Thanks again.
black-venomzz
I did :
1. Copy whole .zip file on sd card found when searched "htc desire 601 stock rom" on google in google docs pasge (can't post link yet).
2. Install .zip with TWRP.
- Failed (still bootloop) -
The tried :
1. fastboot flash boot boot.img (boot.img was found in the .zip file)
2. Copy whole .zip file on sd card
3. Install .zip with TWRP
- Failed (still bootloop) -
I'm probably missing something here...
You might not have the correct zip for your variant of 610. They make a few and could depend on the carrier as well. Should also factory reset in TWRP.
es0tericcha0s said:
You might not have the correct zip for your variant of 610. They make a few and could depend on the carrier as well. Should also factory reset in TWRP.
Click to expand...
Click to collapse
Still need help guys ! I believe I have the right one.
Could you check it out ? It looks legit.
**drive**.google.**com/folderview?id=0B6WBFlAKqe30ZG1wOGk2T0xwTkE&&tid=0B6WBFlAKqe30TjRLa2Qxa0toYlU
(I still can't post links on threads because I'm new...)
I tried Installing ROM from zip in TWRP (successful) and then fastboot flash boot boot.img but still didn't work !
My phone is still bricked.
Any help would be appreciated.
black-venomz said:
Still need help guys ! I believe I have the right one.
Could you check it out ? It looks legit.
**drive**.google.**com/folderview?id=0B6WBFlAKqe30ZG1wOGk2T0xwTkE&&tid=0B6WBFlAKqe30TjRLa2Qxa0toYlU
(I still can't post links on threads because I'm new...)
I tried Installing ROM from zip in TWRP (successful) and then fastboot flash boot boot.img but still didn't work !
My phone is still bricked.
Any help would be appreciated.
Click to expand...
Click to collapse
Couldn't find that page, even after taking out the asteriks. But you'll need to boot to the bootloader and run this command:
fastboot getvar all
to find out your exact model/region/carrier/etc.
es0tericcha0s said:
Couldn't find that page, even after taking out the asteriks. But you'll need to boot to the bootloader and run this command:
fastboot getvar all
to find out your exact model/region/carrier/etc.
Click to expand...
Click to collapse
I ran the command. See attachment. I don't know how to compare it to ROM.
Here is the link again :
**https**://**drive.**google.**com/folderview?id=0B6WBFlAKqe30eUh3WXB4eURwRjQ&&tid=0B6WBFlAKqe30TjRLa2Qxa0toYlU
If it still fails (wich truly shouldn't) I access it by searching "htc desire 601 stock ROM" on Google and it's the first one, the page is called "Firmware"
Thank you for your help !
Edit : I know why the link fails. It seems xda adds a space somewhere in the link. Need to remove it for the link to work.
black-venomz said:
I ran the command. See attachment. I don't know how to compare it to ROM.
Here is the link again :
**https**://**drive.**google.**com/folderview?id=0B6WBFlAKqe30eUh3WXB4eURwRjQ&&tid=0B6WBFlAKqe30TjRLa2Qxa0toYlU
If it still fails (wich truly shouldn't) I access it by searching "htc desire 601 stock ROM" on Google and it's the first one, the page is called "Firmware"
Thank you for your help !
Edit : I know why the link fails. It seems xda adds a space somewhere in the link. Need to remove it for the link to work.
Click to expand...
Click to collapse
I'll look around for it later, but real quick, you probably want to take down the picture since it has your IMEI and Serial Number of the phone listed, for safety's sake.
es0tericcha0s said:
I'll look around for it later, but real quick, you probably want to take down the picture since it has your IMEI and Serial Number of the phone listed, for safety's sake.
Click to expand...
Click to collapse
Ok I'll wait ! Thanks for the tip. If you need it for the info, I'll post it again without IMEI/Serial.
black-venomz said:
Ok I'll wait ! Thanks for the tip. If you need it for the info, I'll post it again without IMEI/Serial.
Click to expand...
Click to collapse
Ok, I think we might be on the right track now...
According to the read out from getvar, you were on 4.2.2. It's also listed as a Rogers phone (I'm assuming there's a direct connection between Fido and Rogers, though being an American, I'm not 100% up to date with Canadian carriers...) so I found the RUU for 4.2.2 (system 1.10.631.8 which you can see in the getvar list) http://www.htcdev.com/devcenter/downloads/P510 (it won't let me do a direct link for some reason) and pick the Rogers one for 1.10.631.8
This should get you back up and running.
Make sure to relock the bootloader before you run it or it'll fail. You can re-unlock afterwards. Should be able to do "fastboot oem lock" then when ready to unlock again then "fastboot oem unlock" should work since you've already used the bootloader key.
es0tericcha0s said:
Ok, I think we might be on the right track now...
According to the read out from getvar, you were on 4.2.2. It's also listed as a Rogers phone (I'm assuming there's a direct connection between Fido and Rogers, though being an American, I'm not 100% up to date with Canadian carriers...) so I found the RUU for 4.2.2 (system 1.10.631.8 which you can see in the getvar list) http://www.htcdev.com/devcenter/downloads/P510 (it won't let me do a direct link for some reason) and pick the Rogers one for 1.10.631.8
This should get you back up and running.
Make sure to relock the bootloader before you run it or it'll fail. You can re-unlock afterwards. Should be able to do "fastboot oem lock" then when ready to unlock again then "fastboot oem unlock" should work since you've already used the bootloader key.
Click to expand...
Click to collapse
Your a life saver thanks !
I'll make sure to relock.
The only thing is I have no clue how to use this RUU. It's not like a ".exe" that you execute.
The .zip file contains a .tar.gz file, wich contains another .tar file, wich contains binaries I believe.
The readme.txt file talks about using Linux commands but I'm far from an expert.
I'll do a little research on my own since you helped me a lot already, but if you have any tips feel free to share !
Thanks again,
black-venomz
BTW for information purposes,
Fido is indeed a subsidiary brand of Rogers.
black-venomz said:
BTW for information purposes,
Fido is indeed a subsidiary brand of Rogers.
Click to expand...
Click to collapse
Ah shoot, I didn't realize it at the time, but that's like the source code, as in, if you wanted to compile a rom for your phone. That actually isn't what we need. :/ I'll have to keep looking...
es0tericcha0s said:
Ah shoot, I didn't realize it at the time, but that's like the source code, as in, if you wanted to compile a rom for your phone. That actually isn't what we need. :/ I'll have to keep looking...
Click to expand...
Click to collapse
****e. How do people build RUU.exe in the first place ? Can't we build one with these binary files ?
Edit : Did some reading and found out only vendors can make RUU's.
Tried this, found on another thread.
"The RUU is your normal, executable program and does everything for you. The ZIP is an RUU but you have to set the phone up to flash it by using fastboot commands. the process is:
1. Connect phone in fastboot mode
2. Run the command 'fastboot oem rebootRUU'
3. Once the phone is at the HTC screen, you run the command 'fastboot flash zip name_of_zip.zip'
4. It will flash the first part and then give an error and you run the same command as above a second time straight away
5. Once the second flash sequence has finished, you the type 'fastboot reboot' and it will reboot the phone and finish the installation"
It failed, but I didn't relock bootloader yet. Will try that now.
Edit : Also failed with relocked bootloader.
Fastboot error message was :
"(bootloader) signature checking
FAILED (remote : 12 signature verify fail)"
black-venomz said:
Tried this, found on another thread.
"The RUU is your normal, executable program and does everything for you. The ZIP is an RUU but you have to set the phone up to flash it by using fastboot commands. the process is:
1. Connect phone in fastboot mode
2. Run the command 'fastboot oem rebootRUU'
3. Once the phone is at the HTC screen, you run the command 'fastboot flash zip name_of_zip.zip'
4. It will flash the first part and then give an error and you run the same command as above a second time straight away
5. Once the second flash sequence has finished, you the type 'fastboot reboot' and it will reboot the phone and finish the installation"
It failed, but I didn't relock bootloader yet. Will try that now.
Edit : Also failed with relocked bootloader.
Fastboot error message was :
"(bootloader) signature checking
FAILED (remote : 12 signature verify fail)"
Click to expand...
Click to collapse
You can flash RUUs like that, but that zip does not house the files you would need. RUUs have to be signed with HTC's special key or it won't work. That's why it was only a 99MB file...
---------- Post added at 12:16 AM ---------- Previous post was at 12:00 AM ----------
http://forum.xda-developers.com/desire-601/help/rogers-ruu-available-t2836217
https://drive.google.com/folderview...RFdlTWc&tid=0BzrP5DWIlpplWkNROHh6Y3o4UHc#list
es0tericcha0s said:
You can flash RUUs like that, but that zip does not house the files you would need. RUUs have to be signed with HTC's special key or it won't work. That's why it was only a 99MB file...
Click to expand...
Click to collapse
Thanks for looking around. Unfortunately the RUU failed (see picture).
I think my phone was updated with Android 4.4.2 when I bought it (recently) so it might be what's causing the error.
I wanted to try with a Telus RUU for 4.4.2 but it's not there..........
I'm starting to lose hope here.