I'm not sure how, but my device is bricked, I can get to HTC screen but nowhere beyond that. I was rooted, bootloader unlocked (HTCDev method), S-ON, HBOOT 2.09, had TWRP but it was somehow erased from the device. I have re locked the bootloader to try to try and revert to stock RUU but I can't find correct version anywhere. WHAT DO I DO?! I can provide any additional info you need to help me.
Thanks in advance.
Sounds like a similar issue that somebody else recently had. You can try unlocking again and pushing recovery to your phone to see if that fixes the issue. There is no RUU for software version 3.16. Viperboy has a RUU tool for software version 3.16, but it requires you to be S-off in order to use it.
Sent from my EVO 4G LTE using xda premium
If you can still talk to the device with adb/fastboot commands, then you may be able to use the BabyRacun instructions to load the 3.15 RUU. I finally achieved S-OFF today after going through the process as described in this thread: http://forum.xda-developers.com/showthread.php?t=2341275, which specifically describes a flash to the 3.15 RUU.
Related
I was having a problem with my screen being unresponsive so i needed to take it into a sprint store. i ran a signed 2.17 exe and now I have hboot 1.5 but still have s-off. in the bootloader screen it says locked but still shows s-off. i am confused as to what to do next. i assume i need to unlock but didn't know if i could do this via revolutionary. I tried to do a search but everything i found was related to s-on. I am trying to restore my phone to its rooted state since I have already had the repairs made. Any help and links would be greatly appreciated.
Brandon
Sent from my iPad using Tapatalk HD
brandonb8 said:
I was having a problem with my screen being unresponsive so i needed to take it into a sprint store. i ran a signed 2.17 exe and now I have hboot 1.5 but still have s-off. in the bootloader screen it says locked but still shows s-off. i am confused as to what to do next. i assume i need to unlock but didn't know if i could do this via revolutionary. I tried to do a search but everything i found was related to s-on. Any help and links would be greatly appreciated.
Brandon
Sent from my iPad using Tapatalk HD
Click to expand...
Click to collapse
fastboot oem writesecureflag3 or fastboot oem writesecureflag 3 , one of those will turn s-on
Edit... This might help http://forum.xda-developers.com/showthread.php?t=1578977
Thanks for the quick response. Sorry I was not more clear about what I am wanting to do. I am keeping the phone and the repairs have been made. I now have hboot 1.50 with s-off. I am wanting to flash a custom rom again and need to install a recovery. I didn't know what the process is currently for "unlocking" my phone now. When I rooted the phone originally, i was on hboot 1.4 and used revolutionary. I just do not know what to do to get my phone rooted again. I understand I have part of it with s-off still being on my phone, but the "locked" text at the top of the bootloader screen tells me I need to rectify this before I can flash a recovery. Is this correct?
Thanks.
Brandon
brandonb8 said:
Thanks for the quick response. Sorry I was not more clear about what I am wanting to do. I am keeping the phone and the repairs have been made. I now have hboot 1.50 with s-off. I am wanting to flash a custom rom again and need to install a recovery. I didn't know what the process is currently for "unlocking" my phone now. When I rooted the phone originally, i was on hboot 1.4 and used revolutionary. I just do not know what to do to get my phone rooted again. I understand I have part of it with s-off still being on my phone, but the "locked" text at the top of the bootloader screen tells me I need to rectify this before I can flash a recovery. Is this correct?
Thanks.
Brandon
Click to expand...
Click to collapse
Oh I see, well, your s-off and that locked banner means nothing because s-off should override it. Just flash a PG86IMG.zip of a recovery of your choice and you're good to go. Or you can flash it via fastboot by typing fastboot flash recovery "yourrecovery.img" once you do that, flash a rooted Rom. You could flash a lower hboot with a PG86IMG.zip if you want but its not really necessary.
If you want, I could dig up hboot 1.4 or revs hboot for ya. I think I have em in dropbox.
I got it. Thanks for all the help.
Sent from my PG86100 using Tapatalk 2
I am trying to flash my phone with the RUU 2.13 so I can get the new firmware and flash meanbean. I am following this post (http://forum.xda-developers.com/showpost.php?p=31520093&postcount=11730) to do so. After following what Captain says, which is to relock the bootloader I can't get past the bootloader (which I now understand is normal right?) and then try to run the RUU through HBOOT, however I get the USB error. Is this due to the bootloader being relocked or am I missing the htc drivers on my computer?
Also, I'd rather go to S-Off, so if anyone could shed some light on how I would go from S-On to S-Off I would greatly appreciate it.
Which firmware are you trying to get on your phone? Because the way I'm reading it is you're using the older ruu file to try to get the newest firmware. Just wanna make sure you're using the newest ruu of 3.15 (came out December 22).
Sent from my EVO using xda app-developers app
onefasttreopro said:
Which firmware are you trying to get on your phone? Because the way I'm reading it is you're using the older ruu file to try to get the newest firmware. Just wanna make sure you're using the newest ruu of 3.15 (came out December 22).
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
Ya wow can't believe how long it's been since I've flashed a rom. An old version of MeanRom has lasted me so long. I am on an old firmware (1.13) I believe. I want to preferably go from S-On to S-Off. Before, I tried Captain Throwbacks method (relocking the bootloader, flashing the RUU) however I ran into a USB Connection Problem with the RUU. So I am trying to figure out if it was because I didn't have the right htc drivers installed or something else. If S-On to S-Off would eliminate the need for those steps I would much rather do that. I am trying to get to the latest firmware. Thanks!
What Hboot are you on?
Edit: If you're on 1.12 you're going to have to go the Dirty Racun route, since Lazy Panda is no longer officially supported. This, of course, requires you to RUU to upgrade to either Hboot 1.15 or 1.19, then run Dirty Racun to get S-off. Getting S-off is definitely the way to go, as it can save you some headache down the road. Also, don't run the RUU for 3.15 (JB) as this will update your Hboot and currently there is no exploit to get S-off with the new Hboot. You can still unlock and root it, but you'll be S-on.
Sent using my HTC EVO LTE and a magic wand
FinZ28 said:
What Hboot are you on?
Sent using my HTC EVO LTE and a magic wand
Click to expand...
Click to collapse
^^^^What he said
Sent from my EVO using xda app-developers app
I have read pages and pages from the Android Development forum for the HTC Evo 4G LTE and I can't seem to find a solution that works for me because going S-OFF or re-locking bootloader and loading RUU does not seem feasible for my situation.
The phone has custom recovery (TWRP) and we successfully loaded Viperboy's deodexed 3.15 stock ROM.
Baseband is 1.02.12.0427 (super outdated)
This phone was bought second hand and is a HTC dev unlocked phone, S-ON
I would like to update the baseband to 1.12.11.1200 and update the firmware to 3.16
Caveats: I don't have access to the phone, my friend can reload custom ROMs through TWRP, but beyond that I don't think we can go through Dirty Racun and S-Off, I don't know how we can easily check the HBOOT version to determine if the HBOOT version is 1.12
What would happen if we accepted the Sprint OTA? Are we SOL with the baseband because we are S-ON?
Is there any way we can get on MeanBean 3 or stock rooted 3.16?
Any advise would be greatly appreciated.
I wouldnt accept the OTA update to 3.16
I actually did just that when I relocked my phone on Saturday and had all sort of problems after that. Now, I'm not too sure you would even be able to install the update being that your phone is unlocked *citation needed*.
http://forum.xda-developers.com/showthread.php?t=2135670 - talks about the 3.16 OTA problems
thanks, I've definitely advised my friend to stay away from the OTA and disregard it. I think we are experiencing call/wifi issues due to the old baseband. I wonder what are the next possible steps to move forward from here...
BaconMunch said:
thanks, I've definitely advised my friend to stay away from the OTA and disregard it. I think we are experiencing call/wifi issues due to the old baseband. I wonder what are the next possible steps to move forward from here...
Click to expand...
Click to collapse
1. Stay on this baseband and deal with it.
2. Relock and RUU your way up to 3.15 (stay away from 3.16)
3. S-off and Flash a couple full firmware zips.
Sadly I think those are your only option. And to check your hboot just boot into bootloader. Hold volume down when powering on.
tilltheend714 said:
1. Stay on this baseband and deal with it.
2. Relock and RUU your way up to 3.15 (stay away from 3.16)
3. S-off and Flash a couple full firmware zips.
Sadly I think those are your only option. And to check your hboot just boot into bootloader. Hold volume down when powering on.
Click to expand...
Click to collapse
Thanks, I think that seems realistic, I'm concerned that if I relock through HTCDev, I read that some email/password might go to the original seller of the phone (ebay) for confirmation code, so I don't want to get stuck halfway
I am definitely crossing my fingers for HBoot v1.12, to confirm, once I check my version in the bootloader, I guess I can escape without taking any of the menu options (checking YouTube, I'll just go to recovery, enter TWRP, reboot, system).
BaconMunch said:
Thanks, I think that seems realistic, I'm concerned that if I relock through HTCDev, I read that some email/password might go to the original seller of the phone (ebay) for confirmation code, so I don't want to get stuck halfway
I am definitely crossing my fingers for HBoot v1.12, to confirm, once I check my version in the bootloader, I guess I can escape without taking any of the menu options (checking YouTube, I'll just go to recovery, enter TWRP, reboot, system).
Click to expand...
Click to collapse
Relocking the phone is done through fastboot on the computer. Nothing to do with HTC. And Dev unlocked means you get an unlock token from HTC to the email that you signed up with. So if you make your own account on HTC dev and request a token, it should send nothing to the other owner.
And sorry, but I don't understand what you mean by having Hboot 1.12. You mean only flashing the radio through recovery? If that's what you mean than I can't help with that. Not sure how that works or if there are problems with that.
great news! I had someone take screen shots of the HBoot (v.1.12.0000) and TWRP (v2.2.1) menu
Bootloader shows:
Code:
*** TAMPERED ***
*** UNLOCKED ***
JEWEL PVT SHIP S-ON RL
HBOOT-1.12.0000
RADIO-1.02.12.0427
OpenDSP-v25.1.0.32.0405
eMM-boot
So as far as I know, I'm going to make sure there's nothing wrong with the TAMPERED, and then I can flash 1.12.11.1210 through Captain_Throwbacks Radio Only zip and then looks for a 3.16 custom firmware compatible with S-On since I'm on build number 3.15.651.16 CL124461.
I'd appreciate anyone to chime in if I'm going down a bad path here. Cheers!
BaconMunch said:
great news! I had someone take screen shots of the HBoot (v.1.12.0000) and TWRP (v2.2.1) menu
Bootloader shows:
Code:
*** TAMPERED ***
*** UNLOCKED ***
JEWEL PVT SHIP S-ON RL
HBOOT-1.12.0000
RADIO-1.02.12.0427
OpenDSP-v25.1.0.32.0405
eMM-boot
So as far as I know, I'm going to make sure there's nothing wrong with the TAMPERED, and then I can flash 1.12.11.1210 through Captain_Throwbacks Radio Only zip and then looks for a 3.16 custom firmware compatible with S-On since I'm on build number 3.15.651.16 CL124461.
I'd appreciate anyone to chime in if I'm going down a bad path here. Cheers!
Click to expand...
Click to collapse
You've indeed unlocked the bootloader properly but this only let's you flash recoveries and custom roms. You have to S-OFF the phone to update firmware via bootloader. You're other option would be to RUU which would upgrade the firmware and software and that CAN be done with S-ON, however there is a problem with the update which disables touch input so you should either wait for a dev to make custom 3.16 rom and forget about the firmware OR wait for a fix from HTC and run that RUU whenever it comes out.
xlxcrossing said:
You've indeed unlocked the bootloader properly but this only let's you flash recoveries and custom roms. You have to S-OFF the phone to update firmware via bootloader. You're other option would be to RUU which would upgrade the firmware and software and that CAN be done with S-ON, however there is a problem with the update which disables touch input so you should either wait for a dev to make custom 3.16 rom and forget about the firmware OR wait for a fix from HTC and run that RUU whenever it comes out.
Click to expand...
Click to collapse
Thanks xlxcrossing! I messaged Captain for a a recovery flash for the baseband only and he said my approach is no good either. So seems like I have to RUU to get off 1.12 anyways since LazyPanda is not supported and DirtyRacun starts at 1.15
So I am looking at the UNLIMITED.IO site now
step 1) relock via fastboot
step 2) RUU 1.15 or 1.19 (so this means my firmware/software/hboot will be updated as well?)
From here if I stop, I will be S-ON so I can...
option 1) RUU 2.09 and stay on 3.15
option 2) unlock bootloader from HTCDev and stay S-ON
option 3) unlock bootloader from HTCDev and DirtyRacun S-OFF (which actually seems like a very simple process once unlocked)
BaconMunch said:
Thanks xlxcrossing! I messaged Captain for a a recovery flash for the baseband only and he said my approach is no good either. So seems like I have to RUU to get off 1.12 anyways since LazyPanda is not supported and DirtyRacun starts at 1.15
So I am looking at the UNLIMITED.IO site now
step 1) relock via fastboot
step 2) RUU 1.15 or 1.19 (so this means my firmware/software/hboot will be updated as well?)
From here if I stop, I will be S-ON so I can...
option 1) RUU 2.09 and stay on 3.15
option 2) unlock bootloader from HTCDev and stay S-ON
option 3) unlock bootloader from HTCDev and DirtyRacun S-OFF (which actually seems like a very simple process once unlocked)
Click to expand...
Click to collapse
My advice is get s-off it will save alot of headaches down the road
Sent from my PoS MoPho
BaconMunch said:
Thanks xlxcrossing! I messaged Captain for a a recovery flash for the baseband only and he said my approach is no good either. So seems like I have to RUU to get off 1.12 anyways since LazyPanda is not supported and DirtyRacun starts at 1.15
So I am looking at the UNLIMITED.IO site now
step 1) relock via fastboot
step 2) RUU 1.15 or 1.19 (so this means my firmware/software/hboot will be updated as well?)
From here if I stop, I will be S-ON so I can...
option 1) RUU 2.09 and stay on 3.15
option 2) unlock bootloader from HTCDev and stay S-ON
option 3) unlock bootloader from HTCDev and DirtyRacun S-OFF (which actually seems like a very simple process once unlocked)
Click to expand...
Click to collapse
Sent you a PM
The advice is free....the bandwidth, not so much
Just wanted to say thank you all for the support and advice.
I finally walked my friend over gtalk and successfully achieved S-OFF after relock, 1.15 RUU, unlock with HTC DEV, dirtyracun
Then updated full firmwares incrementally to 3.16
Then while trying to load MeanBean, realized we lost TWRP (and possibly root, need to confirm), I can only guess that went away with the RUU? That's not really documented anywhere unless that's a known thing.
TWRP installation via goomanager failed (maybe due to lack of root), I was able to find TWRP v2.3.1 bootloader, installed that and installed MeanBean 3.0.4
I think that makes us up to date, however we will likely install SuperSU via TWRP once we customize and ensure the phone is running smoothly.
Thanks again all!
Super su is included with the ROM
Sent from my EVO using xda premium
I recently bought my new Evo 3D from eBay. As far as I can tell, it is in perfect shape. I was hoping to flash it to Page Plus and was dismayed when I realized how impossible the rooting process looked. I began with downgrading my 1.58 HBOOT to 1.40. Now I am attempting to flash the 1.13 RUU so I can finally move on in this process, but every time I attempt to flash it (or any other RUU), I get the error, "Error [131]: CUSTOMER ID ERROR." Now most fastboot commands do not work, and my phone bootloops with the stock ROM. Any idea how to fix it?
I used the juopunut bear wire trick for s-off so excuse me if I'm a little ignorant here with the downgrade method. Once you are down to hboot 1.40 (which sounds like you were successful with) can't you use the revolutionary s-off tool?
Once s-off you can easily run any ruu but I guess I don't understand why you need to downgrade even further to s-off, when revolutionary (I thought) works with hboot 1.40 and 1.30
Brian706 said:
I used the juopunut bear wire trick for s-off so excuse me if I'm a little ignorant here with the downgrade method. Once you are down to hboot 1.40 (which sounds like you were successful with) can't you use the revolutionary s-off tool?
Once s-off you can easily run any ruu but I guess I don't understand why you need to downgrade even further to s-off, when revolutionary (I thought) works with hboot 1.40 and 1.30
Click to expand...
Click to collapse
As I understand I can't use Revolutionary without booting into Android (since it needs ADB), which is currently impossible because of the bootloop.
I should also point out that HTCDev unlock fails for me. On hboot 1.58 the fastboot commands are successful, but I am never presented with the unlock dialog on the phone. On hboot 1.4 most fastboot commands fail. Also, I can easily restore to stock by flashing a PG86IMG which includes hboot 1.58.
Macadamia Daze said:
As I understand I can't use Revolutionary without booting into Android (since it needs ADB), which is currently impossible because of the bootloop.
Click to expand...
Click to collapse
Oh, I see now!
Macadamia Daze said:
I should also point out that HTCDev unlock fails for me. On hboot 1.58 the fastboot commands are successful, but I am never presented with the unlock dialog on the phone. On hboot 1.4 most fastboot commands fail. Also, I can easily restore to stock by flashing a PG86IMG which includes hboot 1.58.
Click to expand...
Click to collapse
So far, in every case I've seen, running the latest RUU has solved the bootloader unlock issue for people. I would run the 1.58 RUU and see if you can unlock the bootloader. Then go from there.
Or as I saw mentioned in the other thread, use the PG86IMG version of the RUU or extract it yourself from the exe. Flashing through the bootloader does not perform a cid check.
Brian706 said:
Oh, I see now!
So far, in every case I've seen, running the latest RUU has solved the bootloader unlock issue for people. I would run the 1.58 RUU and see if you can unlock the bootloader. Then go from there.
Or as I saw mentioned in the other thread, use the PG86IMG version of the RUU or extract it yourself from the exe. Flashing through the bootloader does not perform a cid check.
Click to expand...
Click to collapse
So far, I have yet to have any success despite flashing many RUUs. I took a break for quite a while, but decided I may try again. I am downloading now the 2.08 RUU, which one thread suggested.
Macadamia Daze said:
I should also point out that HTCDev unlock fails for me. On hboot 1.58 the fastboot commands are successful, but I am never presented with the unlock dialog on the phone. On hboot 1.4 most fastboot commands fail. Also, I can easily restore to stock by flashing a PG86IMG which includes hboot 1.58.
Click to expand...
Click to collapse
If I remember correctly, the HTCDev unlock doesnt work for the earlier bootloaders. It says so on the very first page when its walking you through the steps. I could be wrong but you may wanna keep that in mind
Hey all,
so I've been running ARHD on firmware 127.538.8 for awhile. I saw the RUU come out for 4.3 on Tmob, so obviously I was all like, **** yeah! So I flashed a stock ROM (based on 127.538.11) and then tried to run the RUU. Unlocked, S-OFF. For some reason, the RUU flashed Hboot (I'm currently stuck at 1.55.00) and then decided to throw an error 155 at me. So I tried relocking the bootloader, with a command I found browsing the forums that sets the status to Locked. Flashing the RUU here didn't work either. Re-unlocked the bootloader (I have no user data at all... it's sad). I realized, okay, I'm Unlocked and have a custom recovery installed (TWRP). Even if I relock, the RUU doesn't flash. My idea right now is to flash the 127.538.11 RUU to get Hboot 1.44, as well as a working non-hacked firmware. I'm not sure if that RUU will work, though I'm hoping it does. If it does, then I can OTA update without a problem.
Do any of you have any ideas as to how to do this? I can RUU to 127.538.11, then downgrade to x.8 and use revone to lock my bootloader and attempt an OTA. I'm not sure what to do here... I can also reflash ARHD 30 and stick with that for awhile. I can do basically anything recommended, as I have S-OFF and TWRP.
Thanks!
I don't mind being stuck on stock, however I do want to be able to warranty my phone in the future -- will having hboot 1.55.00 with 127.538.8 firmware be a problem? Can I downgrade my hboot since I'm S-Off? Any help here would be absolutely wonderful...