Related
All, I am sorry I didn't search more, but I am desperate. I go on travel in a few hours.
Long story short, my phone stopped working with 3g, I spent 4-5 hours on phone with sprint trying to fix. THey want it back to the store. It was HTC unlocked with Fresh. I used fastoot to do fastboot OEM lock, the phone rebooted and goes back to the bootloader screen, I can't get it to go back to Android
It says Tampered, Relocked, security warning. Please. Any help. Can I RUU from fastboot?
Yes
As long as you have the boot loader locked you can run the RUU, you can find the RUU in Android Developement.
Hook the phone to your computer, open a command prompt and type "adb reboot recovery" make sure USB debugging is checked. That should get you into TWRP recovery, then go from there.
musicman625 said:
As long as you have the boot loader locked you can run the RUU, you can find the RUU in Android Developement.
Hook the phone to your computer, open a command prompt and type "adb reboot recovery" make sure USB debugging is checked. That should get you into TWRP recovery, then go from there.
Click to expand...
Click to collapse
After relocking the bootloader, I can no longer enter recovery. RUU doesn't seem to want to run because my phone is not up and running (it is already at fastboot prompt). Can I just get it to recognize my phone in fastboot mode somehow?
U need to unlock it again and flash the stock Rom if u relock it with a custom Rom it doesn't allow it to boot
Sent from my EVO using xda premium
adma84 said:
After relocking the bootloader, I can no longer enter recovery. RUU doesn't seem to want to run because my phone is not up and running (it is already at fastboot prompt). Can I just get it to recognize my phone in fastboot mode somehow?
Click to expand...
Click to collapse
As long as you have the proper drivers you should be able to run the RUU from fastboot. While in fastboot if you type 'fastboot devices' (without quotes) is your phone listed?
Sent from my ELTE using Tapatalk 2
dylan6879 said:
U need to unlock it again and flash the stock Rom if u relock it with a custom Rom it doesn't allow it to boot
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Didn't know that was the case. Thanks
crump84 said:
As long as you have the proper drivers you should be able to run the RUU from fastboot. While in fastboot if you type 'fastboot devices' (without quotes) is your phone listed?
Sent from my ELTE using Tapatalk 2
Click to expand...
Click to collapse
RUU is finally running now. Failed several times, and then just started working. I hope it works. Thank you everyone. Will post back
This happened to me as well. The only thing that I did that finally made it work, was to make sure that the path that I performed the fastboot oem lock command in was the path that contained the fastboot file.
When I did this, it would boot into my custom ROM and I was able to run the RUU without any problems.
When I would try to run the RUU from bootloader it would always tell me my battery was low, even though I was over 90%.
Happend to me too . I just ran ruu while in fastboot .
Sent from my EVO using xda premium
I'm S-on. I was GB, rooted on ViperRom. Flashed .10 following Nils instructions. Everything was fine. Unlocked and tried to flash Amon Ra. The PC would not detect the phone. I deleted the PH98IMG and booted into recovery hoping the phone would be detected for adb. Now the phone is stuck at HBoot. It cannot find a PH98 since I stupidly deleted it and now I cannot get back to a working phone. Any sugestions are greatly appreciated. Thanks.
was your PC detecting the phone earlier?
Did you let the ruu make its second pass of the install? Did it boot normally before you went back to bootloader to flash a recovery? Also you have to be in fastboot menu to connect to usb
Sent from my ADR6425LVW using xda app-developers app
kancherlapraneeth said:
was your PC detecting the phone earlier?
Click to expand...
Click to collapse
Yes. I am positive it did before flashing the .10 RUU and i'm fairly sure it did in order for me to unlock, I just do not remember completely.
Squirrel1620 said:
Did you let the ruu make its second pass of the install? Did it boot normally before you went back to bootloader to flash a recovery? Also you have to be in fastboot menu to connect to usb
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
OH man, I forgot about going back into the fastboot menu. That seems to have solved it. I know have my phone back. Now I have to try and figure out why the pc is not detecting my phone. In the command prompt when I change directories to where fastbot and ADB are. I type adb devices, it does not detect the phone.
Thanks for the help on theHBoot issue. Phone is back but after booting up it flashes that it needs a SIMcard. Then loads up fine. I was able to connect thru the pc. I forgot to enable usb debugging and uncheck fastboot, but even after detected it will not let me flash amon ra. it gives me an error. I am bone tired and will try any suggestions tomorrow.
If you flashed a good ROM and your stuck in hboot, use fastboot and use the following command 'fastboot oem boot' that will force your phone to boot.
first off, I'm an idiot with this whole thing and shouldn't be doing it probably. i just don't know enough about it to be playing with expensive phones like this so i understand I deserve whatever i get.
i was running a custom rom on an S-ON phone. i forgot the name of the rom (was made by TEAM COOL or something). But I wanted to unroot and go back to normal stock ROM and download the JB update. First, in the SU app, I did a complete unroot. that did nothing except not let me use the app anymore.
then I tried doing the RUU way of going back, but when it would go to the loading bootloader portion, the usb would disconnect and it would fail with error 171.
so then, and i don't know how i got here, but i went into recovery and did a factory reset and now i have no rom. I have tried installing meanrom but it fails after some line regarding a kernal. my phone won't do anything except boot to the white HTC screen or into the bootloader.
i have no idea what to do, I just want it working at this point.
i've been searching forums like crazy but all the solutions are things I already have done or things that won't work for me.
If you haven't done so yet, you need to relock the bootloader before running ruu. Put your phone in fastboot and using SDK or ADB Tools, type fastboot oem lock
om4 said:
If you haven't done so yet, you need to relock the bootloader before running ruu. Put your phone in fastboot and using SDK or ADB Tools, type fastboot oem lock
Click to expand...
Click to collapse
thank you for your help! however, whenever i do this, it just says < waiting for device >
so i finally got a rom to install--clean rom. that is the one i used to have. but when i reboot, it gets stuck on a black screen and won't go any further.
I had the same thing happen. Had to run a boot.img flash utility i found on another thread elsewhere on xda. The flash utility was updated for jb. If i can locate where i found it then i will get back to you.
Sent from my EVO using Tapatalk 2
I was curious if you ever found that rom or if anybody can help me? The phone is still out of commission. It's been tough to make it through the holidays especially since my laptop was stolen the very next day that all this happened
bump again. I'm assuming the phone is bricked for good if the brightest minds on the subject don't even know
i'm using my dad's old evo 4g for now.
unclefarkus said:
bump again. I'm assuming the phone is bricked for good if the brightest minds on the subject don't even know
i'm using my dad's old evo 4g for now.
Click to expand...
Click to collapse
Have you tried meanbean? It has the boot.img flash tool baked in for s-on, just follow the instructions to the tee in the OP... It's in the Android development thread... Good luck
Sent from my EVO using xda app-developers app
Sounds like you need to flash a Rom that has the s-on installer or fastboot flash the kernel for the Rom you have installed
Most roms come with the kernel installer built in now days. just keep trying to flash em. fyi if your phone turns on , even a little bit , you are not bricked
I am trying to flash meanbean. I wiped the cahes and did factory reset, then flashed the ROM. It's been on "Installing /system..." for about 30 minutes now. Something seems wrong. I'm scared to interrupt it in case that's normal or if interrupting it will break it for good.
Well, I think that might be because my twrp version is really old...2.1.8. I tried updating but had no luck.
Now nothing flashes. It gets to 'verifying partition sizes' then fails. Tried this on several roms that would previously flash, just not work.
unclefarkus said:
Well, I think that might be because my twrp version is really old...2.1.8. I tried updating but had no luck.
Now nothing flashes. It gets to 'verifying partition sizes' then fails. Tried this on several roms that would previously flash, just not work.
Click to expand...
Click to collapse
Update twrp through goomanager, its in the market, then try again.
Sent from my EVO using xda premium
mrlakadaddy said:
Update twrp through goomanager, its in the market, then try again.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
lol how could he do that if he dont have any rom installed...dafuq?
You need to FASTBOOT install it:
Turn off your device. Turn on the device and keep holding volume down until a menu shows up. Select fastboot from the menu list. Plug the device into your computer. If you have the right drivers installed, your screen should now say FASTBOOT USB. Run the following command via the command line:
fastboot flash recovery TWRP.img
Boatiy said:
lol how could he do that if he dont have any rom installed...dafuq?
You need to FASTBOOT install it:
Turn off your device. Turn on the device and keep holding volume down until a menu shows up. Select fastboot from the menu list. Plug the device into your computer. If you have the right drivers installed, your screen should now say FASTBOOT USB. Run the following command via the command line:
fastboot flash recovery TWRP.img
Click to expand...
Click to collapse
Don't forget the clear cache commands
Sent from my EVO using xda app-developers app
I have given this a go, however, as I should expect by now, nothing happens.
It says "waiting for device" and that's it
Upon typing "adb devices" nothing shows up.
Furthermore, when I go to Fastboot, Fastbook usb does show up, but I get a message on the computer saying the usb device has malfunctioned.
unclefarkus said:
I have given this a go, however, as I should expect by now, nothing happens.
It says "waiting for device" and that's it
Upon typing "adb devices" nothing shows up.
Furthermore, when I go to Fastboot, Fastbook usb does show up, but I get a message on the computer saying the usb device has malfunctioned.
Click to expand...
Click to collapse
Can you get into bootloader? If so go to the TWRP website and download the hboot zip. Put on external sd card and enter bootloader.
Sent from my EVO using Tapatalk 2
Perhaps what is happening when you try oem lock and get that error is that adb is still running from a prior attempt or because of some other program. Try opening your task manager and ending all processes of adb and other programs that connect to the phone. Then try oem locking again and go from there.
Sent from my EVO using xda premium
I made a little bit of progress!
I determined that Windows 8 was the reason I get the usb malfunctioning message. I obtained a Windows 7 computer and it worked like a charm.
That said, I'm not out of the woods yet.
I relocked the phone using fastboot and then have been attempting to flash a stock RUU now that the usb issue is sorted out.
That seems to work but it gets stuck at "sending....." for as long as 35 minutes. I've tried about 4 times, giving between 20-35 minutes and it won't go beyond sending.
I can at least fastboot now; but the phone is locked. Which is fine; I just want back to stock anyways.
Tampered
Re-locked
S-On
Hboot-1.19.0000
Radio-1.12.11.0809
OpenDSP-v29-1.0.45.0622
eMMC-boot
Aug 9 2012
I flashed the 2.13.651.1 RUU by the way.
Any new advice haha?
I loaded a PJ img via sd card and it's alive and updating to JB OTA right now! Thanks for all the help over the past month folks
Hello all, I've just recently recovered my DNA back to stock from a botched ROM install on the 3.06 software. Prior to running the RUU, I used Rumrunner to unlock my bootloader to put CWM on as my recovery. Then I had to re-lock it to run the RUU. Now I'm stuck at re-unlocking it. The HTCdev site is giving me a MID not allowed error and I'm thinking it has something to do with the fact that I used Rumrunner? Call me stupid, the DNA is still relatively new to me. Thank you!!
You shouldn't need to relock it to RUU. The RUU will overwrite your recovery with stock but the bootloader should remain unlocked (and s-off if you did that as well). At this point you should be able to just run rumrunner again to unlock the bootloader and then you can flash a custom recovery and go from there.
Sent from my HTC6435LVW using xda app-developers app
iissmart said:
You shouldn't need to relock it to RUU. The RUU will overwrite your recovery with stock but the bootloader should remain unlocked (and s-off if you did that as well). At this point you should be able to just run rumrunner again to unlock the bootloader and then you can flash a custom recovery and go from there.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Tried doing Rumrunner again, Getting this error, "ERROR: run rumrunner again and READ (no adb connection to device. Debugging on?
Drivers?)" I've uninstalled the drivers via device manager, let windows 7 reinstall them and installed/uninstalled HTCsync with no luck.
Edit: Nevermind, tried a different cable. Hate it when that happens.
Edit 2: Rumrunner must have failed, device still relocked.
Hubblemuffin said:
Tried doing Rumrunner again, Getting this error, "ERROR: run rumrunner again and READ (no adb connection to device. Debugging on?
Drivers?)" I've uninstalled the drivers via device manager, let windows 7 reinstall them and installed/uninstalled HTCsync with no luck.
Click to expand...
Click to collapse
Does 'adb devices' show your serial number? Did you enable debugging in the developer options?
iissmart said:
Does 'adb devices' show your serial number? Did you enable debugging in the developer options?
Click to expand...
Click to collapse
I don't even see ADB devices in device manager. Just Android USB Devices.
Hubblemuffin said:
I don't even see ADB devices in device manager. Just Android USB Devices.
Click to expand...
Click to collapse
ADB Devices is a command issued from the command prompt. It should return the S/N of the device connected. If there is no response the drivers are not installed on the PC. If you are using Win 8 or 8.1 you will have issues
RLGL said:
ADB Devices is a command issued from the command prompt. It should return the S/N of the device connected. If there is no response the drivers are not installed on the PC. If you are using Win 8 or 8.1 you will have issues
Click to expand...
Click to collapse
Not too familiar with running that command. I'm new to the whole HTC scene. My Note 2 was significantly easier to work with in this respect.
Hubblemuffin said:
Not too familiar with running that command. I'm new to the whole HTC scene. My Note 2 was significantly easier to work with in this respect.
Click to expand...
Click to collapse
Hı, have you find out a solution to this one ?
I am struggling with a similar situation:
http://forum.xda-developers.com/showthread.php?p=51140962
I did, sorry for not posting it here. I went and got a new cable from tiger direct and tried again. For some reason, the bootloader still says relocked but I have root access. I don't feel confident enough to try and see if CWM or TWRP and I don't want to go through the RUU garbage again. Shoot me a PM and I'll tell you everything what not to do. LOL
Sent from my HTC6435LVW using xda app-developers app
Hubblemuffin said:
I did, sorry for not posting it here. I went and got a new cable from tiger direct and tried again. For some reason, the bootloader still says relocked but I have root access. I don't feel confident enough to try and see if CWM or TWRP and I don't want to go through the RUU garbage again. Shoot me a PM and I'll tell you everything what not to do. LOL
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
I have heard if you flash a new hboot the relocked text will go away, but I haven't had this issue myself so I can't personally confirm it. I do recommend updating your hboot and radio, though, for other reasons like better radio signal.
iissmart said:
I have heard if you flash a new hboot the relocked text will go away, but I haven't had this issue myself so I can't personally confirm it. I do recommend updating your hboot and radio, though, for other reasons like better radio signal.
Click to expand...
Click to collapse
Updating the hboot and radio seems a little daunting. Definitely something I want to look in to once I can figure out how to get a ROM on this without calling a mulligan and starting from scratch again.
Hubblemuffin said:
Not too familiar with running that command. I'm new to the whole HTC scene. My Note 2 was significantly easier to work with in this respect.
Click to expand...
Click to collapse
Adb is universal to all android devices, I highly recommend getting used to it if you plan on rooting future devices, the only thing native to HTC is the S-OFF portion of eMMC
Hubblemuffin said:
I did, sorry for not posting it here. I went and got a new cable from tiger direct and tried again. For some reason, the bootloader still says relocked but I have root access. I don't feel confident enough to try and see if CWM or TWRP and I don't want to go through the RUU garbage again. Shoot me a PM and I'll tell you everything what not to do. LOL
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Are you S-OFF? If so issue this command in fastboot:
fastboot oem writecid 22222222
Go to htcdev.com and then it will allow you to unlock the bootloader also make sure you have 8 2's in the command.
Help,
i wanted to try different roms on my HTC One (M7). After i loaded a slim rom, i had locked the bootloader and it started boot looping. Wiped my phone clean, now i can't flash or push any file on my phone. What can i do to fix this?
shado2us said:
Help,
i wanted to try different roms on my HTC One (M7). After i loaded a slim rom, i had locked the bootloader and it started boot looping. Wiped my phone clean, now i can't flash or push any file on my phone. What can i do to fix this?
Click to expand...
Click to collapse
Sounds like a bit of a pickle. I'll need a bit more info to make sure I point you in the right direction.
Which version (carrier) of the M7 is it?
Do you still have a custom recovery? Which one?
S-On?
What version of the software did you have on the phone before modifying?
PC/Mac/Linux? Which version?
Do you have working adb and fastboot drivers?
Have you re-unlocked the bootloader? (You should if you want to do more custom stuff)
Are you going back to Sense or a non Sense based rom?
Curious as to why you would relock the bootloader unless you had planned on returning to stock with an RUU...?
es0tericcha0s said:
Sounds like a bit of a pickle. I'll need a bit more info to make sure I point you in the right direction.
Which version (carrier) of the M7 is it?
Do you still have a custom recovery? Which one?
S-On?
What version of the software did you have on the phone before modifying?
PC/Mac/Linux? Which version?
Do you have working adb and fastboot drivers?
Have you re-unlocked the bootloader? (You should if you want to do more custom stuff)
Are you going back to Sense or a non Sense based rom?
Curious as to why you would relock the bootloader unless you had planned on returning to stock with an RUU...?
Click to expand...
Click to collapse
i am using Straight Talk
twrp
S-off
stock 4.4.2
pc win7
yes
either
it happened by itself, didn't want to go back to lock
shado2us said:
i am using Straight Talk
twrp
S-off
stock 4.4.2
pc win7
yes
either
it happened by itself, didn't want to go back to lock
Click to expand...
Click to collapse
Ok, so far so good. however I'm not clear if the "yes" answer is for the working adb / fastboot drivers or if you have re-unlocked the bootloader. You're using ST, but is the phone originally an ATT, T-mo, or International version? And does the PC recognize when you plug in the phone while in TWRP? If so, are there any error messages like USB Device Not Recognized or anything of the sort?
es0tericcha0s said:
Ok, so far so good. however I'm not clear if the "yes" answer is for the working adb / fastboot drivers or if you have re-unlocked the bootloader. You're using ST, but is the phone originally an ATT, T-mo, or International version? And does the PC recognize when you plug in the phone while in TWRP? If so, are there any error messages like USB Device Not Recognized or anything of the sort?
Click to expand...
Click to collapse
trying to re-unlock
originally international
pc does recognize
when i try to do recovery:
target reported max download size of 1526722560 bytes
sending 'recovery' (9944 KB)...
OKAY [ 1.180s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.233s
when i try to fastboot flash, adb push and adb sideload other files:
error: device not found
Ok, so seems like there is a couple things going on. First off, if you are trying to unlock the bootloader, then why are you trying to send recovery? And secondly, sounds like you are having some issues with drivers perhaps. When you go to your Device Manager, do you have any yellow exclamation points for HTC? Fastboot options only work in bootloader and adb will only work in recovery or booted into the OS. Here's what we should do, check drivers, re-unlock the bootloader, fastboot flash the latest recovery, then make sure adb is working to either sideload a rom or push one to your internal storage.
es0tericcha0s said:
Ok, so seems like there is a couple things going on. First off, if you are trying to unlock the bootloader, then why are you trying to send recovery? And secondly, sounds like you are having some issues with drivers perhaps. When you go to your Device Manager, do you have any yellow exclamation points for HTC? Fastboot options only work in bootloader and adb will only work in recovery or booted into the OS. Here's what we should do, check drivers, re-unlock the bootloader, fastboot flash the latest recovery, then make sure adb is working to either sideload a rom or push one to your internal storage.
Click to expand...
Click to collapse
i have no kernal/rom on my phone. fastboot, adb and sideload doesn't work to put files on my phone. just got throught trying to unlock with my wifes macbook air and still wont unlock. i am getting very frustrated with all of this not working.
shado2us said:
i have no kernal/rom on my phone. fastboot, adb and sideload doesn't work to put files on my phone. just got throught trying to unlock with my wifes macbook air and still wont unlock. i am getting very frustrated with all of this not working.
Click to expand...
Click to collapse
If it's not working on the PC then it's an issue with drivers, cord, or ports. Most likely drivers. You never mentioned what your Device Manager says when you plug the phone in. Step number 1 was to check drivers, yet you didn't mention trying to troubleshoot that or anything of the sort.
es0tericcha0s said:
If it's not working on the PC then it's an issue with drivers, cord, or ports. Most likely drivers. You never mentioned what your Device Manager says when you plug the phone in. Step number 1 was to check drivers, yet you didn't mention trying to troubleshoot that or anything of the sort.
Click to expand...
Click to collapse
it shows
android usb devices
my htc
shado2us said:
it shows
android usb devices
my htc
Click to expand...
Click to collapse
In what mode on the phone are you that it shows this and are there any yellow exclamation points? Are you using a USB 2.0 or 3.0 port? 2.0 is recommended. When you are in the bootloader and choose fastboot, does it change to fastboot usb on the phone?
es0tericcha0s said:
In what mode on the phone are you that it shows this and are there any yellow exclamation points? Are you using a USB 2.0 or 3.0 port? 2.0 is recommended. When you are in the bootloader and choose fastboot, does it change to fastboot usb on the phone?
Click to expand...
Click to collapse
in fastboot mode drivers are good; in recovery mode the driver is under other devices named one and that is yellow with error code 28. my ports are 2.0. yes it does change
shado2us said:
in fastboot mode drivers are good; in recovery mode the driver is under other devices named one and that is yellow with error code 28. my ports are 2.0. yes it does change
Click to expand...
Click to collapse
Ok, well if fastboot drivers are working, then what trouble are you having doing the unlock again? Just gotta use the unlock.bin file you got from HTC. But your adb drivers are messed up in recovery so that will prevent you from being able to adb push or sideload. This is not an uncommon issue with HTCs in recovery on Windows. See if the drivers from here: http://forum.xda-developers.com/showthread.php?t=2232799 will get you back on track. If that doesn't work, try the Universal Naked Driver.
es0tericcha0s said:
Ok, well if fastboot drivers are working, then what trouble are you having doing the unlock again? Just gotta use the unlock.bin file you got from HTC. But your adb drivers are messed up in recovery so that will prevent you from being able to adb push or sideload. This is not an uncommon issue with HTCs in recovery on Windows. See if the drivers from here: http://forum.xda-developers.com/showthread.php?t=2232799 will get you back on track. If that doesn't work, try the Universal Naked Driver.
Click to expand...
Click to collapse
nope, nothing. when i go to fastboot flash unlocktoken Unlock_code.bin, it does not go to the disclaimer, nothing happens. the universal naked drivers worked for adb.
shado2us said:
nope, nothing. when i go to fastboot flash unlocktoken Unlock_code.bin, it does not go to the disclaimer, nothing happens. the universal naked drivers worked for adb.
Click to expand...
Click to collapse
Well something has to happen, as in, what does it say on the CMD prompt when you enter the command? And if the drivers work for adb, then you wouldn't see the exclamation point in your device manager and you would be able to connect via adb in recovery.
ok, now I am at stock again. Not going to install slim roms unless I have all the files I need.
Sent from my HTC One using xda app-developers app
Glad you are back up again! Did you get an RUU to return to stock then? But yea, as a general rule of thumb, I never modify a device that I don't have the files and guide on how to return to stock.