Okay, so, I was at work and I was trying to run an RUU to go back to stock, and I heard I had to relock. Well like an idiot, I start running commands without reading the whole thread first.
I ran 'fastboot oem writesecureflag 3', and now my phone is bricked.
So. I'm S-Off with the earliest exploit on these forums (revolutionary, right?), is there any way I can fix this? I've tried the unbricking Live CD, and it won't recognize my phone at all. What are my options?
thematrixkid17 said:
Okay, so, I was at work and I was trying to run an RUU to go back to stock, and I heard I had to relock. Well like an idiot, I start running commands without reading the whole thread first.
I ran 'fastboot oem writesecureflag 3', and now my phone is bricked.
So. I'm S-Off with the earliest exploit on these forums (revolutionary, right?), is there any way I can fix this? I've tried the unbricking Live CD, and it won't recognize my phone at all. What are my options?
Click to expand...
Click to collapse
Well if you didnt flash a shipped Hboot and turned S-on you are bricked.
unbricking live cd?
If your not talking about Closeone's Downgrade Toolkit Live CD then you should try it...
install the iso into a cd or usb then once your boot into it just run the process to downgrade. if it works your phone should boot and you will be on hboot 1.40
iTzLOLtrain said:
unbricking live cd?
If your not talking about Closeone's Downgrade Toolkit Live CD then you should try it...
install the iso into a cd or usb then once your boot into it just run the process to downgrade. if it works your phone should boot and you will be on hboot 1.40
Click to expand...
Click to collapse
I just figured it out. I was using Closeone's Downgrade Toolkit Live CD, but it didn't work for me. I thought that was the direction I needed to go, but apparently not.
I had to run an Ubuntu 12.04 Live CD and then run the tools listed here: http://forum.xda-developers.com/showthread.php?p=25501934
thematrixkid17 said:
Okay, so, I was at work and I was trying to run an RUU to go back to stock, and I heard I had to relock. Well like an idiot, I start running commands without reading the whole thread first.
I ran 'fastboot oem writesecureflag 3', and now my phone is bricked.
So. I'm S-Off with the earliest exploit on these forums (revolutionary, right?), is there any way I can fix this? I've tried the unbricking Live CD, and it won't recognize my phone at all. What are my options?
Click to expand...
Click to collapse
Your situation is exactly what this thread was designed to fix.
From the second post of that thread:
Prerequisites
•a linux box/live cd with automount disabled and without unity
•the appropriate package for the device
•the latest RUU for your device
•a device bricked by writing security flag 3 with an unsigned hboot, or caused by a damaged hboot via interrupted OTA update/RUU flash on a S-ON device
•a usb cable
•some basic linux experience
•patience
Click to expand...
Click to collapse
I haven't needed to use it myself, but I hope it works for you. I believe that the OP (dexter93) sometimes hangs out on the #juopunutbear freenode IRC channel so you can try going there if you have questions not answered in that thread or need help.
Edit: I see you found it on your own.
ramjet73
Related
So my friend a few months ago was messing around with his evo 3d and managed to brick it. He couldn't fix it so he got a new phone and gave the 3d to me a few days ago. The phone powers on but is stuck on the htc splash screen. The phone goes into recovery/fastboot mode via power and volume down. I've found a thread on how to fix it, but I have no idea how to do any of it. I've googled for about an hour now and can't quite figure out what exactly their talking about.
Here is the thread
http://forum.xda-developers.com/showthread.php?t=1897719
He says he ran the lock cmd for the phone to relock the bootloader I'm guessing. I'm guessing I have to run this through dos. After he did this he ran the ruu.exe which I downloaded.
Anyways, I'm essentially clueless when it comes to htc phones, so if someone could give me a rundown of exactly what to do in plain english it would be much appreciated.
You need to be booted into a linux live environment. If you have a burnable CD / DVD I can help you out.
Indirect said:
You need to be booted into a linux live environment. If you have a burnable CD / DVD I can help you out.
Click to expand...
Click to collapse
I have an old copy of backtrack, would that work?
That'll be fine. Just get backtrack up and running, then install teamviewer and pm me the id / password and I'll help you out.
Well if it goes to recovery, you don't have to do all that, just make sure hboot is right version, s off and unlocked then flash a rom.i don't even think unlocked is required
Edit: Sorry, just read first post thoroughly, go on with the install process
Sent from my SPH-D700 using Tapatalk 2
Ok folks, I got the phone relocked but I guess I downloaded the wrong ruu. Does anyone know how I determine which one to download?
Duganator9 said:
Ok folks, I got the phone relocked but I guess I downloaded the wrong ruu. Does anyone know how I determine which one to download?
Click to expand...
Click to collapse
If you are able to relock you should be able to issue the following fastboot command that will return a key for the model of your phone:
fastboot getvar cid
ramjet73
ramjet73 said:
If you are able to relock you should be able to issue the following fastboot command that will return a key for the model of your phone:
fastboot getvar cid
ramjet73
Click to expand...
Click to collapse
Sorry for the noob question, but I did what exactly do I do with that number?
I tried a while ago to unlock my bootloader using HTCDev when it first came out, would get to the part where the confirmation screen should pop up on your phone screen to unlock the bootloader but the screen never showed after multiple attempts, so frustrated, I gave up and told my self I'd come back later. Well later came around a few days ago and I attempted to unlock the bootloader again with the same results as the first time, get to the point where I'm supposed to confirm on my phone screen but it never shows. Did some research to find out the OTA version of the update to ICS could have possibly been the problem, but before I went any further I did a full backup of my phone using Carbon, then did a factory reset from the fastboot menu. Now the problem is, after I did the factory reset my computer no longer recognizes my phone when I plug it in. It can't find HTC sync on my computer even though it is, adb devices shows nothing, same with fastboot devices in fastboot mode. My computer recognized the phone just fine up until the factory reset. So I guess my question is, what caused this to happen and how can I fix it? Also, maybe some help unlocking my bootloader? I think I have to flash the RUU but my phone is 2.95.651 and I don't think it lets you go backwards unless you are S-OFF?
Edit: I guess I should mention that I've tried uninstalling and reinstalling the HTC drivers, usb debugging is enabled and Fast Boot in the power options is disabled, I'm also using the USB cord supplied with my phone, tried different USB ports, performed a second factory reset, made sure all my SDK stuff was up to date, and scoured these forums for 2 days now trying to figure it out (apologies if I missed the one thread with all the answers I need, I did try though). Additionally, in fastboot when I plug in my USB cord it switches to fastboot usb, but nothing shows up on devices, which I find really odd.
Anybody have any ideas/solutions for this?
Yep,
http://androidforums.com/showthread.php?p=5810229
I used srs root to gain a root shell followed scotty85's instructions to set mainver low via adb shell then used the brick downgrade hboot method and followed it up with 1.13 ruu and finished with revolutionary
Post #50 is my instructions and scotty85 are a few posts back
Ok, so I got it... kind of. What I did was try the above method with no luck but I ended up using wraith's temproot and scotty's mainver workaround from above then while it was still in it's temproot state I was able to flash a 2.89 RUU, and after that I was unable to unlock the bootloader through HTCdev. Now on to actually root/s-offing it ^ ^
embersanenders said:
Ok, so I got it... kind of. What I did was try the above method with no luck but I ended up using wraith's temproot and scotty's mainver workaround from above then while it was still in it's temproot state I was able to flash a 2.89 RUU, and after that I was unable to unlock the bootloader through HTCdev. Now on to actually root/s-offing it ^ ^
Click to expand...
Click to collapse
Do 2.89 and 2.95 both use the same hboot?
Sent from my Evo V 4G using Tapatalk 2
thewraith420 said:
Do 2.89 and 2.95 both use the same hboot?
Sent from my Evo V 4G using Tapatalk 2
Click to expand...
Click to collapse
I'm not sure if they use the same hboot or not. I was able to flash 2.89 RUU in the temproot state on hboot 1.58.0000. After the flash I retried unlocking the bootloader through HTCdev and it worked flawlessly. Then I was able to root it and juopnutbear s-off, which applied juopnutbear hboot 1.58.5858. It seems like temprooting the phone using your method and flashing a 2.89 RUU might be the workaround for people who have trouble using HTCdev due to the OTA update.
I should also mention someone suggested this method on phandroid forums (scott actually, I believe) on a different thread and so I tried it. I was going to link his post here but I haven't met the link post requirement yet. So as a disclaimer, this isn't my idea, it just worked so I posted here.
Now that I'm home from work I figured I could give a more detailed list of what I did to root my Evo 3D, I feel the information above gets a little confusing with so many different places to go. As previously stated I had trouble unlocking my bootloader using HTCdev, it would get to the step where you confirm on your phone the unlock but never show up, I found this was usually caused by updating your phone to ICS using the OTA as compared to an RUU. Somehow something gets messed up and your phone never wants to confirm, hopefully this will help people who don't want to brick/downgrade hboot in order to be able to root their phones but can't unlock from HTCdev do to this error. Anyway, on to it.
1. Download SRSRoot
A 2.89 RUU
The files from [Guide] Quick And Dirty Evo 3D/V Root & S-OFF (Sprint and Virgin Mobile Only)
2. Run SRSRoot
3. SmartRoot
4. Follow the steps until your phone restarts and you just have a status bar at the top (this is your 'temproot')
5. Close SRSRoot (you may have to kill in the task manager, or at least I did to get it to completely quit mid-steps)
6. Navigate to the folder where the files from the 'QnD' guide and open the cmd link in the Root folder.
7. Type, or copy & paste the following in order (not the stuff in brackets like this, these are notes);
adb devices (should return your phones serial number, indicating drivers are working, and you're connected)
adb push misc_version /data/local/tmp/misc_version
adb shell (should change your prompt to a #, if not, have your phone awake and watch the screen to grant superuser permissions when you enter su (not likely applicable here))
chmod 777 /data/local/tmp/misc_version (have your phone awake and be watching it, in case superuser needs you to grant permission (again, not likely applicable))
/data/local/tmp/misc_version -s 1.00.000.0
exit (exit again if your prompt changes to a $)
8. Run your 2.89 RUU exe (it should run and reinstall 2.89 to stock, you may lose information, unsure about that though, so back ups are always recommended)
9. Restart your phone after the install if it doesn't happen automatically
10. Retry unlocking using HTCdev method
Hopefully at this point the bootloader actually unlocks for you and you can start at Step 2 of the 'QnD' guide to get root access and S-Off.
Big thanks to thewraith420 for the temproot method and scotty85 over at phandroid for the mainver change directions.
The reason I asked if 2.89 used the 1.58 hboot is just to further understand why it worked I think that setting the mainver is what let you run the ruu. And it didn't complain about the hboot because they use the same one. Nicely done getting the info together.
Sent from my PG86100 using Tapatalk 2
misc_version location
embersanenders said:
adb push misc_version /data/local/tmp/misc_version
Click to expand...
Click to collapse
I was encountering the same issue as you for the HTC bootloader unlock, so thanks so much for this info, it worked like a charm. It might be helpful for others to know that you can find the misc_version referenced by downloading the file scotty85 mentions in his post on guide-how-manually-downgrade-firmware-build-6-01-605-05 (Sorry, I'm unable to post the link)
So I've explored different options on XDA's site for returning to stock and I guess this is why I'm here. I screwed the hell up. I posted this on Phaded's How-To page, but I figured it would also be best to post this in the general Help & Troubleshooting page.
Here's the best way I can explain my issue. Someone please help.
1. My phone is COMPLETELY formatted. No OS now. Zero data.
2. TWRP is installed as my recovery.
3. I can fastboot and adb (only from the recovery obviously)
4. I moonshined the phone in order to S-Off
5. I tried the method to remove S-Off by Phaded
adb devices (verify device ID is listed)
adb shell
su
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796
exit
Click to expand...
Click to collapse
When I ran the RUU, I got that error 158 problem. I couldn't flash the HBOOT. downloaded it several times and tried.
6. I flashed it with an AOSP rom and tried the RUU again. No luck.
Now I'm stuck. u_u I tried
adb push "file name" "file directory"
Click to expand...
Click to collapse
so I can drop a zip file in the phone, but it seems to not work. Idk if I did it right. I was hoping to flash a ROM by doing that. smh.
Let me know if there's any other info I can provide. Considering the phone still turns on and I can still get to fastboot and adb, I don't think I'm a lost cause.
Thanks everyone!
UPDATE
I sideloaded a ROM (Carbon) and now I'm up and running. But I still can't RUU it! Figured this detail will help.
I'll keep reading and researching, posting my progress.
Thanks!
Its ok that your'e formatted the main concern would be 1. To be able to turn the phone on and 2. Boot into bootloader and recovery . It sounds like you are able to do both so the term "bricked" doesn't apply here.Okay so first obvious question did you obtain s-off also what bootloader are you on. Also what are you trying to achieve moving forward, going to stock or staying with custom roms, sense or aosp. There is only 1 ruu available for DNA and you need to be relocked to run and have fastboot drivers installed ala HTC sync manager.
Sent from my HTC6435LVW using Tapatalk 4 Beta
xlxcrossing said:
Its ok that your'e formatted the main concern would be 1. To be able to turn the phone on and 2. Boot into bootloader and recovery . It sounds like you are able to do both so the term "bricked" doesn't apply here.Okay so first obvious question did you obtain s-off also what bootloader are you on. Also what are you trying to achieve moving forward, going to stock or staying with custom roms, sense or aosp. There is only 1 ruu available for DNA and you need to be relocked to run and have fastboot drivers installed ala HTC sync manager.
Sent from my HTC6435LVW using Tapatalk 4 Beta
Click to expand...
Click to collapse
1. I obtained s-off with moonshine. I used the above command suggested by Phaded and when I put in
fastboot oem lock
Click to expand...
Click to collapse
(or something like that) it says my phone is locked.
2. What do you mean what bootloader? I guess moonshine, cause that's what comes up when I go to my bootloader screen.
3. I trying flashing the ruu and I get this (see image attached) which the suggested fix for error 158 was to flash the hboot 1.15 (or something). But I can't seem to flash it correctly. I can't even find straight forward instructions on how to do it.
Thanks for responding.
The reason I asked about the bootloader version and I'm not 100% sure about this so someone else may need to chime in is that when you ruu you are flashing firmware which includes hboot so if you upgraded hboot before doing s-off or otherwise went up a version then I'm pretty sure the ruu won't downgrade your hboot airgo the error message. Again this might not be true. At this point all that matters is that your s-off and NOT bricked so instead of toying with an ruu I would choose a stock Rom .zip to flash if its truly stock that you want. Your firmware should be up to date if you took 2.06. There is no ruu for 2.06.
Sent from my HTC6435LVW using Tapatalk 4 Beta
What is s-off?
Sent from my Galaxy Nexus using xda premium
93fuelslut said:
What is s-off?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
It means you can write to any partition of your nand (internal memory). This means customs roms, kernels, splash screens, firmware, etc. When you are s-on it is more difficult, I can't get into why too many words it just is. If you're not s-off and you like flashing stuff look into it.
---------- Post added at 12:51 AM ---------- Previous post was at 12:41 AM ----------
xlxcrossing said:
It means you can write to any partition of your nand (internal memory). This means customs roms, kernels, splash screens, firmware, etc. When you are s-on it is more difficult, I can't get into why too many words it just is. If you're not s-off and you like flashing stuff look into it.
Click to expand...
Click to collapse
I'm not finding a solid explanation for error 158 which is disheartening - the best offerings are to change USB ports or restart the ruu. Like I said before you are fine on the software end, you can verify you have up to date firmware by comparing the latest below with what you have.
Baseband (radio) 1.01.04.0308
PRI 2.44_002
As for the hboot, how are you trying to flash it? In recovery?
The hboot needs to match the RUU. You need to find the original hboot . It is in a thread with hboot versions and radio versions.
Link to HBOOT please? and answering your questions
Could someone provide a link for the hboot instructions and flashing?
I think my problem is that moonshine screwed up my phone. I relocked my phone, but when trying to run moonshine again, it doesn't unlock the phone. It just says "WTF: What are you dong" and then it just stops and tells me to hit Enter to exit and the phone is still locked, hence why I think I can't flash HBOOT.
I try and flash HBOOT through recovery. I tried doing fastboot to flash it. Recalling from memory, I think the command was:
fastboot flash "file name.zip"
Click to expand...
Click to collapse
and then it says it can't open the file, unknown error. But I can't find any help guides or how-to's that explain the fix for this.
Thanks! Keep asking questions, cause I don't know what info is relevant.
ibthevivin said:
Could someone provide a link for the hboot instructions and flashing?
I think my problem is that moonshine screwed up my phone. I relocked my phone, but when trying to run moonshine again, it doesn't unlock the phone. It just says "WTF: What are you dong" and then it just stops and tells me to hit Enter to exit and the phone is still locked, hence why I think I can't flash HBOOT.
I try and flash HBOOT through recovery. I tried doing fastboot to flash it. Recalling from memory, I think the command was: and then it says it can't open the file, unknown error. But I can't find any help guides or how-to's that explain the fix for this.
Thanks! Keep asking questions, cause I don't know what info is relevant.
Click to expand...
Click to collapse
Moonshine isn't working because you are still s-off.
My thread has the original hboot and instructions to flash it. You do not flash in recovery. You do not put it on your phone at all. Do not push the file in recovery. Read and follow the instructions in the stock thread.
---------- Post added at 02:04 PM ---------- Previous post was at 02:02 PM ----------
You're doing the command wrong or you renamed it PL83IMG.zip.zip
Please, go in my thread, read each step perfectly and follow. It's really quite simple.
Difference
Is s-off/s-on and being locked/unlocked two different things?
Screenshot
Also here Phaded. I tried different variants of flashing the hboot. I renamed it from PL83IMG.zip to HBOOT.zip. It's not HBOOT.zip.zip cause I know Windows 8 automatically appends the end of the file name with the type extension. As you can see, I boot to fastboot, then run rebootRUU, then I'm trying to flash from there. I got frustrated and tried different things, even unpacking the .zip and trying to flash the .img file.
Thanks for your contribution to the community Phaded.
ibthevivin said:
Could someone provide a link for the hboot instructions and flashing?
I think my problem is that moonshine screwed up my phone. I relocked my phone, but when trying to run moonshine again, it doesn't unlock the phone. It just says "WTF: What are you dong" and then it just stops and tells me to hit Enter to exit and the phone is still locked, hence why I think I can't flash HBOOT.
I try and flash HBOOT through recovery. I tried doing fastboot to flash it. Recalling from memory, I think the command was: and then it says it can't open the file, unknown error. But I can't find any help guides or how-to's that explain the fix for this.
Thanks! Keep asking questions, cause I don't know what info is relevant.
Click to expand...
Click to collapse
Strike.
From my S-Off BadSeed DNA
ibthevivin said:
Also here Phaded. I tried different variants of flashing the hboot. I renamed it from PL83IMG.zip to HBOOT.zip. It's not HBOOT.zip.zip cause I know Windows 8 automatically appends the end of the file name with the type extension. As you can see, I boot to fastboot, then run rebootRUU, then I'm trying to flash from there. I got frustrated and tried different things, even unpacking the .zip and trying to flash the .img file.
Thanks for your contribution to the community Phaded.
Click to expand...
Click to collapse
You need to cd to the directory the file is in, which should be where fastboot.exe is
So if it's in say C:\sdk\
Type cd C:\sdk\
Then run command to fastboot
BOOM!
Alright. Worked. I'll keep you all posted. No one really mentioned in any of the tutorials and how-to's that it is VERY important to make sure to CD to the directory. Like there are developers who say just add it to the PATH in Environment Variables. I figured it was enough, but hey, I was wrong.
Live and learn right?
Thank you Phaded.
So basically my problem was, calling the hboot.zip file is not included under Environmental Variables. I have to intentionally CD to that directory.
Hmm, I must have missed putting in the cd step for the hboot. I'll go edit it.
I am in the process of turning of factory restoring my htc one and i have the bootloader unlocked and i am turning my s-off with moonshine right now because i know that it needs to be off but i dont know what ruu to use and what command to put in in order to remove the tampered icon so can anyone please help?
use revone. will do s-off and let you remove the tampered flag. the post has it all explained already you will need to be on 1.27.531.8 though. Revone Thread
Based on you posting this in the tmobile section il assume your device is on tmobile. in witch case there is only 1 RUU at the current time (official atleast) get it Here
as for downgrading to 1.27.531.8 i cant post the thread link so google for " tmobile HTC one downgrade to 1.27.531.8 " should take you to a rootzwiki page thread.
or if you are looking for 99.999% pure stock just run that RUU linked above. you will need to be relocked witch you can achieve by going into fastboot plug in your usb cable and type into a cmd prompt cd'd to your android sdk directory aka platform-tools folder.
Code:
fastboot oem lock
for example.
F:\androidsdk\sdk\platform-tools>fastboot oem lock
Click to expand...
Click to collapse
Your directory will be different
then you should be set aslong as your CID is T-MOB010 the RUU should flash.
Ok I'm going to just use this thread since it's an issue I need help with also. I attached a photo of what my T-mobile HTC One says. I don't understand the fastboot thing? Can you further explain it to this n00b? Like I guess step by step lamen terms lol. I don't understand ADB or fastboot at all. All my previous devices just had one click root tool buttons to return to stock. All I want is out of the box stock condition with no tampered text. Thank You.
damon7620 said:
Ok I'm going to just use this thread since it's an issue I need help with also. I attached a photo of what my T-mobile HTC One says. I don't understand the fastboot thing? Can you further explain it to this n00b? Like I guess step by step lamen terms lol. I don't understand ADB or fastboot at all. All my previous devices just had one click root tool buttons to return to stock. All I want is out of the box stock condition with no tampered text. Thank You.
Click to expand...
Click to collapse
Fastboot and ADB are all run from the command line on your PC with you phone plugged in. First question, do you have ABD and Fastboot installed on your computer?
RangerLG said:
Fastboot and ADB are all run from the command line on your PC with you phone plugged in. First question, do you have ABD and Fastboot installed on your computer?
Click to expand...
Click to collapse
no
Hello, I unwisely locked my bootloader without flashing a stock recovery or rom, and now my phone displays the flags *Tampered*, *Relocked*, and *Security Warning*.
I tried to unlock my phone again using (fastboot flash unlocktoken Unlock_code.bin) and while fastboot does detect my device, for some reason any command I type causes the terminal to hang indefinitely.
My phone is an ATT m8, and it is S-on. I am pretty sure it is running a fairly old firmware.
HBOOT - 3.16.0.0000
RADIO - 1.16.21331931.LA11G
I hope I have not left out any information, and that someone can assist me.
Thank you.
Try running the RUU: http://forum.xda-developers.com/showthread.php?t=2757462
Fastboot command not working is odd. Maybe try to uninstall and re-install HTC drivers?
redpoint73 said:
Try running the RUU: http://forum.xda-developers.com/showthread.php?t=2757462
Fastboot command not working is odd. Maybe try to uninstall and re-install HTC drivers?
Click to expand...
Click to collapse
Im running linux, running this under wine would probably be a bad idea. Do you think the RUU would work on XP?
As for the fastboot issue, it was working right until i locked the bootloader, so I assume it has something to do with that. I am also under the impression there are no drivers for linux.
edit: I found a windows 7 disk i had lying around, will attempt to dual boot so I can try the RUU.
RUU should work fine on XP, and certainly works on Win7. Not sure, but I think you are right that on Linux with Wine is probably not a good idea.
You can also use this "bootable" RUU (no PC required): http://forum.xda-developers.com/att-htc-one-m8/general/att-1-58-501-1-bootable-ruu-hboot-t2818556
Fastboot in general should work fine on Linux. Plenty of folks here use Linux and fastboot/adb (just not RUUs). I'm not a Linux person though, so I don't really know the details on drivers and such.
Whether the bootloader is locked or not, shouldn't have any affect on fastboot running, either.