Related
Hey guys,
I was running the latest Viper rom. Every great once in a while the phone would just turn off. I could get it back fine and this happened about 5-6 times. Today the phone got stuck in a boot loop. I figured something went wrong.
I attempted to restore the phone to stock using the RUU thread found here: http://forum.xda-developers.com/showthread.php?t=2152993
I restored it once fine, said it was good. Phone only rebooted over and over. The HTC logo came up 3-4 times then screen went blank. So I flashed again. Same thing, nothing.
Now I had been playing around and think I updated my radio. Now the RUU from that thread above says it cannot upgrade my phone. I can get to fastbook and lock and unlock the bootloader. I did install latest TWRP but it never enters recovery. I had hoped to just install a basic rom from the 2.04 update and be done. But I cannot get into recovery.
I'm stuck and don't know what else to do. Is there and RUU file like the one above for the new 2.04?
I still think something else is wrong with this phone. Somehow doubt VZW will take it back and exchange.
S-ON
Phone displays HBOOT-1.33.0001
RADIO-1.01.01.0110
Any ideas what I can do next please?
I think the radio got updated when I tried to do S-OFF. Instead of an error at step 3 it flashed. Now I've gone back and tried it again and though I get the proper errors is still shows S-ON. Maybe this isn't even needed. I think my days of tinkering with Android should be over. I can follow guides and such
When I try to enter recovery for TWRP I get a lot of colored lines. Going to try reflashing that and see what gives. I feel that if I could get into TWRP and get a rom file on the phone since I cannot get into Android I might have a chance.
Tersanyus said:
I think the radio got updated when I tried to do S-OFF. Instead of an error at step 3 it flashed. Now I've gone back and tried it again and though I get the proper errors is still shows S-ON. Maybe this isn't even needed. I think my days of tinkering with Android should be over. I can follow guides and such
When I try to enter recovery for TWRP I get a lot of colored lines. Going to try reflashing that and see what gives. I feel that if I could get into TWRP and get a rom file on the phone since I cannot get into Android I might have a chance.
Click to expand...
Click to collapse
Did you take the verizon update as you mentioned 2.04? If you did you will have to wait a bit yet to root again. Your only option would be stock verizon. Their software update basically closed the previously open window. If not...You HAVE updated radio per the # you posted, not sure if that really matters with regard to recovery. It seems like you have compounded many issues. I would try relocking bootloader and flash stock RUU again. Try to get back to stock verizon. If that's a no go, would try reflashing old radio and try stock ruu. How are you getting to try bootloader/recovery, turning on phone holding down vol button? Last ditch if it's says s-on and locked, I think you would be ok to try for a new phone.
I did not take the OTA from Verizon. I never got any prompt for an update. I did the updates for Viper that turned I think just turned that off.
Getting to bootloader is fine. I can lock it and unlock it fine. I know the RUU only loads if locked. I know recovery can only be installed if unlocked I believe. And yes I do that from vol down plus power button.
If I use newest TWRP recovery just gives a whole bunch of colored lines. If I try 2.4.0.0 I can see TWRP come up briefly then the phone reboots again.
The RUU exe file just now gives error 158. Basically it thinks it is not the correct ROM
I found the 1.15 radio but it won't flash. http://forum.xda-developers.com/showpost.php?p=38379254&postcount=19
Just gives error of FAILED remote: 92 supercid
Tersanyus said:
The RUU exe file just now gives error 158. Basically it thinks it is not the correct ROM
I found the 1.15 radio but it won't flash. http://forum.xda-developers.com/showpost.php?p=38379254&postcount=19
Just gives error of FAILED remote: 92 supercid
Click to expand...
Click to collapse
Is there a boot.img for the ruu? Maybe the previous boot image is still directing the process, a thought at least. Also that error 92 cid MAY be the issue, Do you have the newest one on (cid)? I had a lot of issues getting s-off and had to run supercid again to run the process after several error 92 messages. I would look at the whole s-off thread in original dev section maybe some answers in there or a direction to head in.
---------- Post added at 10:39 AM ---------- Previous post was at 09:48 AM ----------
rootntootn said:
Is there a boot.img for the ruu? Maybe the previous boot image is still directing the process, a thought at least. Also that error 92 cid MAY be the issue, Do you have the newest one on (cid)? I had a lot of issues getting s-off and had to run supercid again to run the process after several error 92 messages. I would look at the whole s-off thread in original dev section maybe some answers in there or a direction to head in.
Click to expand...
Click to collapse
Can you get to fastboot? adb can communicate with the phone? Says in red fastboot usb? Also how are you doing RUU, assuming your using executable from your pc? Forgot to ask..
Yes I can get to fastboot fine. I do a "fastboot devices" and it is read. adb doesn't seem to do anything though. The RUU is the .exe I found.
For the cid I did the old one so mine reads all 1's. I didn't think I could so the new cid as I cannot boot into Android at all.
Ok success!! Yes.
I did the S-OFF directions once. Nothing, no change.
Did it again this time it booted to factory rom.
I am S-OFF cid is all ones.
I got the prompt for the OTA update, took ot, phone rebooted to recovery, TWRP, then nothing.
Wifi not working, I know I read about that so looks like I have a little more work.
Tersanyus said:
Ok success!! Yes.
I did the S-OFF directions once. Nothing, no change.
Did it again this time it booted to factory rom.
I am S-OFF cid is all ones.
I got the prompt for the OTA update, took ot, phone rebooted to recovery, TWRP, then nothing.
Wifi not working, I know I read about that so looks like I have a little more work.
Click to expand...
Click to collapse
Not sure how you got there s-off should have all 2's....but it sounds like progress. If you are back to recovery and have a rom to flash in your phone that's great...but you'll need adb working to flash the image file that's associated with it, that will likely fix your wifi issue as well. Even with S-off most of the roms still need to have their respective image files flashed but I am unsure about stock RUU, someone with more experience may know that answer and can maybe steer you in the right direction...
Tersanyus said:
Ok success!! Yes.
I did the S-OFF directions once. Nothing, no change.
Did it again this time it booted to factory rom.
I am S-OFF cid is all ones.
I got the prompt for the OTA update, took ot, phone rebooted to recovery, TWRP, then nothing.
Wifi not working, I know I read about that so looks like I have a little more work.
Click to expand...
Click to collapse
If you have a custom recovery then you can't install the ota. If you want the ota stuff you can install the Rom kernel and radio from it.
As far as wifi not working, just flash a kernel, right now it sounds like you have the modules from one kernel and the boot.img from another.
Sent from my HTC6435LVW using xda app-developers app
---------- Post added at 09:43 PM ---------- Previous post was at 09:40 PM ----------
rootntootn said:
Not sure how you got there s-off should have all 2's....but it sounds like progress. If you are back to recovery and have a rom to flash in your phone that's great...but you'll need adb working to flash the image file that's associated with it, that will likely fix your wifi issue as well. Even with S-off most of the roms still need to have their respective image files flashed but I am unsure about stock RUU, someone with more experience may know that answer and can maybe steer you in the right direction...
Click to expand...
Click to collapse
You don't need all 2s to get s off, you can do it with all ones without a problem.
Sent from my HTC6435LVW using xda app-developers app
Bigandrewgold said:
If you have a custom recovery then you can't install the ota. If you want the ota stuff you can install the Rom kernel and radio from it.
As far as wifi not working, just flash a kernel, right now it sounds like you have the modules from one kernel and the boot.img from another.
Sent from my HTC6435LVW using xda app-developers app
---------- Post added at 09:43 PM ---------- Previous post was at 09:40 PM ----------
You don't need all 2s to get s off, you can do it with all ones without a problem.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
BTW There was nothing wrong with your phone, it's just that when you restored, you needed to flash the boot.img from your rom that you restored. It was most likely a kernel issue that we could correct with viper.
It sounds like you just need to install the matching rom and boot.img. If you're s off, just fastboot flash the boot.img for whatever rom you currently have installed. For the OTA update, you can install the radios without an RUU if you're s off.
I ran for several hours and several reboots on the RUU .exe file. When I downloaded a custom rom from http://forum.xda-developers.com/showthread.php?t=2150262 - That fan fine for an hour or so. Then boot loop over and over again. Thankfully I made a backup in twrp. I restored that and all is well.
I can't stand this factory rom, the part that really annoys me, besides the VZW bloat, is the recent apps button. For over a year with other HTC's I am used to making that the menu button. Had that in the custom rom.
So it looks like that rebooting loop just means I need to fastboot the boot.img?
I go back to the rom I linked about and fastboot the boot.img. I really liked viper rom but am going to stick to stock that is rooted and debloated.
My cid is all 1's since I did that before all this OTA came out. I did that about 3 weeks ago the day I got the phone.
Thanks for the tips. I'll let you know what happens when I go back to the rom above.
Bigandrewgold said:
If you have a custom recovery then you can't install the ota. If you want the ota stuff you can install the Rom kernel and radio from it.
As far as wifi not working, just flash a kernel, right now it sounds like you have the modules from one kernel and the boot.img from another.
Sent from my HTC6435LVW using xda app-developers app
---------- Post added at 09:43 PM ---------- Previous post was at 09:40 PM ----------
You don't need all 2s to get s off, you can do it with all ones without a problem.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Sorry about the 2's info but read that the older cid apk would no longer work (from thread below) and myself put on the new one which yields the all 2's. Bottom line, glad you made progress, hopefully problem resolved
http://forum.xda-developers.com/showthread.php?t=2109862
Hey guys,
After months of going through every possible related thread, or almost every one, i've reluctantly had to resort to opening a new one.
I have the AT&T HTC One X+ and I wanted to use it in Pakistan with the service provider being mobilink, Initially my phone was locked so I had to purchase an unlock code online. Once unlocked I inserted my Pakistani sim and I could make calls but wifi would not connect to any network and mobile data would not work at all. Frustrated, i turned to rooting and installing a custom ROM for the first time ever, thinking it would solve my problem according to my research on this forum. In retrospect I might have been wrong.
Nevertheless, I installed CM10, the brainchild of the highly esteemed Lloir, without any hitches via Hasoon's toolkit. I didnt care about my data and tried to make a recovery but I might have failed. Anyways, I downloaded the RUU as well. Everything was fine except the problems we all knew about i.e the calling issue, the camera, etc. Except, my problem was still not solved; my Pakistani sim always had the same effect, wifi and mobile data would stop working. It would take a factory reset to be able to use wifi and MD at all.
Frustrated, i wanted to try another ROM, namely Viper. Here is where the current problem began. I followed the steps on Hasoons toolkit thread to uninstall the custom ROM, revert to default, and relock the bootloader. Ever since i relocked the bootloader I havent been able to either unlock it again, nor boot into recovery. Command prompts never work for me because I'm obviously doing something wrong. But i did set-up the android sdk custom prompt thing and made the desktop shortcut and that seems to at least recognize my phone when its not in fastboot (as does my windows 7 ultimate 64-bit laptop), or in other words, when i'm using the phone proper and not in bootloader.
So, to highlight my issues: i'm stuck with a relocked bootloader with the default ROM (i did manage to revert back from CM10 before relocking), and i cannot boot into recovery. Luckily, i'm $10/month for insurance so I can get another phone for $200 but I'd rather man up and fix this myself with your help of course.
Please help,
Thanks,
Ammar.
Why not just flash a ruu again and start from scratch? It does it all for you.
You won't be able to get into recovery, manipulate fastboot and install roms etc since u locked your bootloader.
Relock bootloader, run ruu, unlock bootloader then flash custom recovery via fastboot and install a rom.
Find the ruu here for:
http://forum.xda-developers.com/showthread.php?p=36580543
Sent from my HTC One X+ using xda premium
somemadcaaant said:
Why not just flash a ruu again and start from scratch? It does it all for you.
You won't be able to get into recovery, manipulate fastboot and install roms etc since u locked your bootloader.
Relock bootloader, run ruu, unlock bootloader then flash custom recovery via fastboot and install a rom.
Find the ruu here for:
http://forum.xda-developers.com/showthread.php?p=36580543
Sent from my HTC One X+ using xda premium
Click to expand...
Click to collapse
bootloader is already locked, i've flashed the default ROM, still can't unlock bootloader or go into recovery. upon clicking recovery in bootloader menu phone shows a red triangle on top of an image of a phone and then phone restarts.
Run the RUU my man. Running that reverts everything back to default. No recovery or anything. It's just like you got your phone out of the box
Sent from my HTC One X+ using Tapatalk 2
Dfballa said:
Run the RUU my man. Running that reverts everything back to default. No recovery or anything. It's just like you got your phone out of the box
Sent from my HTC One X+ using Tapatalk 2
Click to expand...
Click to collapse
He's right. I locked mine up a few weeks ago and used RUU and it was like I took it out of the box. Unlocked bootloader and started over again. Worked like a charm.
Everyone should have the RUU on hand just incase something like this happens
Sent from my HTC One X+ using Tapatalk 2
Hello all, and thank you for taking your time to attempt to help me with my problem.
I could not find a solution even after hours of researching and trial and error, so please forgive me if this happens to be one of those problems that are seemingly impossible to solve, when the actual solution is really quite simple! I'm hoping it is at the very least...
A few days ago I received an HTC Evo 3d from a family member.
I'm certain that the phone was completely stock, never rooted, no custom ROMs ---- just an ordinary HTC 3vo.
So I decide that I'm going to go ahead and find the steps necessary in order to flash a custom ROM, and I believe I did with this:
http://forum.xda-developers.com/showthread.php?t=1889438
I followed the guide, and eventually got to "***Step3: Perform JuopunutBear (wire trick) to get S-OFF status" where I had a little difficulty with the timing of the taps on the SD card. At one point I removed the battery from my phone because I thought it was stuck on the screen with the green arrow pointing downward, and after trying to reboot I found that the same JuopunutBear screen with the green arrow was still there.
I removed the battery once more, but this time when booting I held the volume down button to initiate bootloader. That went successfully, and so after trying the methods I found at http://unlimited.io/jbtroubleshooting.htm to remove this screen, I figured that I might try and flash a ROM from recovery and maybe that would fix it?xD My logic proved only half correct because even after formatting data/cache/dalvik, and then flashing a few different ROMs (not in the order of course) to see if any of them would allow the phone to boot up completely into OS, the phone is now stuck in a bootloop :'(
If I didn't provide enough information in the above description then I'd be glad to give any more details.
My bootloader reads like this:
- Juopunutbear -
SHOOTER XC SHIP S-OFF RL
HBOOT-1.57.5757
eMMC-boot
Apr 20 2012, 17:39:22
^ Never noticed that the date is inaccurate before typing all of this out! Not sure that has anything to do with my problem here, but still interesting..
Thank you again for taking your time to help me.
This phone has given me trouble since it was first given to me lol.
The first issue before rooting or anything was with the inability to use wifi!
I ended up having to buy service for the phone to even register my Gmail account..
You're in good shape
With s off you can recover easily.
The question is what do you want to run?
If you're going to stay ics sense, then you'll just need to format all partitions except sd and flash a Rom
If you want to run a jb Rom, you need to downgrade your hboot to the jbear 1.50
Sent from my PG86100 using xda app-developers app
---------- Post added at 08:42 AM ---------- Previous post was at 08:40 AM ----------
I think the date is the release of the bootloader or something...shouldn't be today's date
Sent from my PG86100 using xda app-developers app
Thank you for the reply
I'll try flashing different sense ROMs specifically,
and see if it will boot all the way through to the home screen.
Have you installed a recovery?
I suggest 4ext
Sent from my PG86100 using xda app-developers app
I have installed a recovery, and it just happens to be 4ext!
I've been installing my ROMs by toggling usb storage in recovery, placing the ROM on the root of my microSD, and after disconnecting from usb storage I proceed to flash the chosen ROM, provided I've already wiped everything.
My trouble usually comes afterward when the ROM has completed it's installation and I go to reboot. Every time I've tried so far I've encountered a bootloop :/ But we'll see this time!
Gotcha
You'll get it sorted
What Rom are you trying now?
Sometimes you need to flash the boot.IMG after the Rom, but that usually only happens if youre s on.
If it still bootloops I would try this next:
Boot to recovery
Wipe all partitions
Reboot recovery
Wipe all partitions again
Flash Rom
Reboot phone
If all else fails you can run the ruu (will return u to stock Rom and recovery) and you will keep s off but will need to install recovery again.
Sent from my PG86100 using xda app-developers app
I chose Team d3rp - Lights Out just to see if it would work, and to my surprise it did!!!
I wiped everything but my sd manually once,
and after flashing the ROM, the aroma installer gave the option to wipe again so I did.
After a suspenseful minute or two during the reboot, I finally got everything set up!
I can't thank you enough..!!
I'm not sure if I should make another thread or not, but the only problem I see now is with the wifi.
I have it connected to my network, and it's showing full signal,
but I can't access the internet and 3g doesn't even pick up when wifi is on.
If needed I'll make another thread, but I figured I would ask just in case!
I appreciate all the help so far.
Try a reboot or different kernel...don't know why it doesn't work
Sent from my PG86100 using xda app-developers app
Hello, a couple of days ago I received an HTC Evo 3D, but I don't like the stock HTC rom, so I decided to use NonSense (http://forum.xda-developers.com/showthread.php?t=1507616). I updated firmware, and installed CWM 6.0, wiped partitions and installed that ROM. But now i got a bootloop :/ .
Bootloader is unlocked..
egerth said:
Hello, a couple of days ago I received an HTC Evo 3D, but I don't like the stock HTC rom, so I decided to use NonSense (http://forum.xda-developers.com/showthread.php?t=1507616). I updated firmware, and installed CWM 6.0, wiped partitions and installed that ROM. But now i got a bootloop :/ .
Bootloader is unlocked..
Click to expand...
Click to collapse
Again, more info please. What h-boot? S-on or s-off?
Sent from my Nokia 3310 using Tapatalk
donkeykong1 said:
Again, more info please. What h-boot? S-on or s-off?
Sent from my Nokia 3310 using Tapatalk
Click to expand...
Click to collapse
S-off, I think it has to be s-on, hboot 1.53.0007, i'm currently trying to use RUU get back to stock, RUU says :
from image version 3.28.401.1 to 3.28.631.1
But it fails because of model id.
Bootloader is currently relocked.
egerth said:
S-off, I think it has to be s-on, hboot 1.53.0007, i'm currently trying to use RUU get back to stock, RUU says :
from image version 3.28.401.1 to 3.28.631.1
But it fails because of model id.
Bootloader is currently relocked.
Click to expand...
Click to collapse
You can only flash sense based ROMs with that h-boot. Since you're s-off just downgrade your h-boot to 1.49.0007 or 1.49.1107 and you can flash anything you want
Sent from my Nokia 3310 using Tapatalk
Oh crap, made a mistake, I have s-on.
Then you can only flash sense based ROMs. Try Cool ICS, it's great. Or do s-off ?
Sent from my Nokia 3310 using Tapatalk
donkeykong1 said:
Then you can only flash sense based ROMs. Try Cool ICS, it's great. Or do s-off ?
Sent from my Nokia 3310 using Tapatalk
Click to expand...
Click to collapse
I was about to download that, hopefully it'll work. :fingers-crossed:
You need 4ext recovery and smartflash enabled because Cool uses custom kernel
Sent from my Nokia 3310 using Tapatalk
donkeykong1 said:
You need 4ext recovery and smartflash enabled because Cool uses custom kernel
Sent from my Nokia 3310 using Tapatalk
Click to expand...
Click to collapse
I tried with CWM, and after a successful flash and boot, I flashed boot.img via fastboot, seems to be working, thank you!
You're welcome
Sent from my Nokia 3310 using Tapatalk
From Mo Versi w/HTC:
Thank you for your support on HTC EVO 4G LTE 4.3 + Sense 5MR update. Below is the link for the final software release that includes support on Win8. Please note the following as this is an RUU update (side load):
*
It is our responsibility to caution you that not all claims resulting or caused by installing this software may be covered under warranty.*Please understand that you will not be able to return your device to the original state or earlier software, and going forward your device may not be held covered under the warranty for all claims resulting from installing this software. HTC bears no responsibility if your device is no longer usable afterwards. We strongly suggest that you do not install this software unless you are confident that you understand the risks involved and the potential consequences both to your device and to your warranty.
*
In order to install the SW, double click the RUU file with your device connected to the PC. The upgrade process will take approximately 20 minutes. Please do not unplug the device from the PC.
*
Download link here
*
Thanks,
Mo
----------------------
EDIT: The official link has been taken down. If you would still like to download the RUU anyway, I have uploaded it here and here.
NOTE: For those having issues updating via the RUU (drivers, Windows 8.1, etc), see this post for an alternative install method.
NOTE 2: There is an updated RUU (4.13.651.4) which was released to some testers from HTC. The update fixes the data roaming issue. It hasn't been released officially, but there is a download link for it here and a mirror here.
Excellent! Thanks Captain
Interesting, I don't think I've ever seen an official update that voided your warranty before.
Should I be worried that it's been stuck on the "sending" screen (on the PC, Windows 7) and the phone on the HTC logo for over 30 minutes?
---------- Post added at 11:47 PM ---------- Previous post was at 11:29 PM ----------
jporter12 said:
Should I be worried that it's been stuck on the "sending" screen (on the PC, Windows 7) and the phone on the HTC logo for over 30 minutes?
Click to expand...
Click to collapse
I restarted it, and it's going this time. No idea what the deal was, but it's working now! Loaded and first booting.
It works,the only thing is supersu. I have to fine one that works with 4.3.
Sent from my EVO using XDA Premium 4 mobile app
djmadclass said:
It works,the only thing is supersu. I have to fine one that works with 4.3.
Sent from my EVO using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Not sure what SuperSU has to do with this RUU, but you should be able to flash SuperSU fine (as long as you're using the recovery from my thread).
So to clarify (sorry if this is a stupid question), but will this keep root? Just have to flash SU after? I'm rooted and s-off right now with custom ROM.
Deathalo said:
So to clarify (sorry if this is a stupid question), but will this keep root? Just have to flash SU after? I'm rooted and s-off right now with custom ROM.
Click to expand...
Click to collapse
This is an official RUU from HTC. You will lose root and custom recovery. You'll have to flash the custom TWRP from my thread or Philz's modified CWM, and then you can flash SuperSU for root. Make sure your bootloader is unlocked after running this though - otherwise you won't be able to write permanently to /system.
Thanks, captain. I figure it out. I used the modified twrp.
Sent from my EVO using XDA Premium 4 mobile app
Can anyone using this RUU comment on if their bootloader is still unlocked after?
Still on hboot 1.12.2222 (I think) and can probably figure out flashing supersu through TWRP after I flash TWRP.
Captain, can you link your thread? I've only used your zips for flashing firmware bits, radios, etc.
Thank you,
Skid
Skid71 said:
Can anyone using this RUU comment on if their bootloader is still unlocked after?
Still on hboot 1.12.2222 (I think) and can probably figure out flashing supersu through TWRP after I flash TWRP.
Captain, can you link your thread? I've only used your zips for flashing firmware bits, radios, etc.
Thank you,
Skid
Click to expand...
Click to collapse
My bootloader stayed unlocked the entire time. My thread is in OG Dev. If you flash the RUU, you'll only need a recovery.
I'm experiencing a weird problem with the update. HTC beats audio doesn't enable unless I do the refresh on the blink homescreen or if I disable it, and enable it via settings. Once it goes to another track, it turns off again despite showing the icon that means it is on. I have to repeat the said steps to get it on again. This is using the HTC music app, and Google Play music app. Anyone aware of this? This is all stock with the new RUU.
Sent from my EVO using Tapatalk
c3T said:
I'm experiencing a weird problem with the update. HTC beats audio doesn't enable unless I do the refresh on the blink homescreen or if I disable it, and enable it via settings. Once it goes to another track, it turns off again despite showing the icon that means it is on. I have to repeat the said steps to get it on again. This is using the HTC music app, and Google Play music app. Anyone aware of this? This is all stock with the new RUU.
Sent from my EVO using Tapatalk
Click to expand...
Click to collapse
I believe that's a known issue.
Captain_Throwback said:
I believe that's a known issue.
Click to expand...
Click to collapse
Okay, thank you. I tried searching on Google, and I did not find anything. Will they address this, or is it unlikely?
Sent from my EVO using Tapatalk
c3T said:
Okay, thank you. I tried searching on Google, and I did not find anything. Will they address this, or is it unlikely?
Sent from my EVO using Tapatalk
Click to expand...
Click to collapse
Well they knew about it before giving us the final version and they didn't fix it. That suggests to me that it's unlikely to be fixed.
Thanks for this, downloaded and I'm gonna give it a shot, I'd like to root after, but I'm a bit confused, Where do I get the modified twrp? and also a little help on how to flash it cause it's been a while I flash something to my evo and with all the keeping up with my note 2, well I feel like new to the htc evo again.
Thanks!
kbrn said:
Thanks for this, downloaded and I'm gonna give it a shot, I'd like to root after, but I'm a bit confused, Where do I get the modified twrp? and also a little help on how to flash it cause it's been a while I flash something to my evo and with all the keeping up with my note 2, well I feel like new to the htc evo again.
Thanks!
Click to expand...
Click to collapse
Look for my thread in OG Dev.
Will my phone stay S-off after taking this RUU?
Sent from my EVO using xda app-developers app
JManekia said:
Will my phone stay S-off after taking this RUU?
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
Yes.
i thought i read somewhere that needed to relock bootloader, so i did, caused me lots of problems trying to flash ruu. it wouldnt complete ruu, got some htc_fastboot.exe errors, had to restart ruu 3-4x...finally decided to unlock bootloader again and give it a go. completed, no issues so far, all is good again. now shows only unlocked, not tampered unlocked as before ruu
Any way to revert? Cracked my screen today and need to go back.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Dunk it in water
Sent from my HTC One_M8 using XDA Premium HD app
Just hide it: http://forum.xda-developers.com/showthread.php?t=2708565
spoke with htc... They saw I requested a bootloader unlock token and wont replace the glass.
hugebulge said:
spoke with htc... They saw I requested a bootloader unlock token and wont replace the glass.
Click to expand...
Click to collapse
What would a broken glass have anything to do with unlocking the bootloader? If so, then shame on you HTC.
Vandam500 said:
What would a broken glass have anything to do with unlocking the bootloader? If so, then shame on you HTC.
Click to expand...
Click to collapse
My thoughts exactly. a second rep told me to go back s-on with the bootloader saying locked and I will have no issues having it repaired. He also said that the screen alone is never changed, It always includes the mainboard.
hugebulge said:
spoke with htc... They saw I requested a bootloader unlock token and wont replace the glass.
Click to expand...
Click to collapse
Wow really? I would call again and talk to someone else. That is BS. Developer edition has the advantage plan and comes with unlocked boot loader. I would point that out. If they say no, ask to speak to their manager.
---------- Post added at 06:43 PM ---------- Previous post was at 06:39 PM ----------
You can lock your boot loader and to turn s-on on m7 is
fastboot oem writesecureflag 3
I don't know if this works on m8, try at your own risk or see if anyone else has tried it.
---------- Post added at 06:45 PM ---------- Previous post was at 06:43 PM ----------
Just out of wonder, what was your scenario when you cracked your screen? Did you have a case? How high? Concrete?
Dot case , 3 feet and a 1/4 inch rubber floor over concrete. I can't believe it cracked. Its a one inch crack from the right side to the bottom of the screen. I probably dropped my m7 30 times in the year I owned it without a problem.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
I believe there is a S-On feature in Hasoon2000's all in one tool that takes you back to S-On. When I was looking through all the features it has earlier today it seemed like it has everything you need to basically revert back to stock as if you never messed with the device. link to thread --> http://forum.xda-developers.com/showthread.php?t=2699065
Pure+ said:
I believe there is a S-On feature in Hasoon2000's all in one tool that takes you back to S-On. When I was looking through all the features it has earlier today it seemed like it has everything you need to basically revert back to stock as if you never messed with the device. link to thread --> http://forum.xda-developers.com/showthread.php?t=2699065
Click to expand...
Click to collapse
thanks a lot. Have any idea how to get back to locked bootloader?
hugebulge said:
thanks a lot. Have any idea how to get back to locked bootloader?
Click to expand...
Click to collapse
I seem to recall "re-lock bootloader" as being one of the many great features of the toolkit.
I used the toolkit and relocked the bootloader, went back to s-on. The phone still says tampered and relocked in the bootloader. The problem I'm running into is, I want to return the phone to AT&T store. I have clicked to reset the device from settings, as well as from the bootloader and the phone does not restore it just boots into teh bootloader showing tampered and relocked. I think this is because the know the AT&T rep will restore it and see it. Anyone know of a way to fix this?
JakeT85 said:
I used the toolkit and relocked the bootloader, went back to s-on. The phone still says tampered and relocked in the bootloader. The problem I'm running into is, I want to return the phone to AT&T store. I have clicked to reset the device from settings, as well as from the bootloader and the phone does not restore it just boots into teh bootloader showing tampered and relocked. I think this is because the know the AT&T rep will restore it and see it. Anyone know of a way to fix this?
Click to expand...
Click to collapse
Sounds like you didn't flash the stock recovery.
There is a guide on how to lock your boot loader without it saying relocked in the m8 forums.
You would need to soff, unlock boot loader, flash stock rom and recovery, boot into twrp "don't flash recovery" and root your phone, relock phone the proper way, remove tampered label, go back to s-on, use supersu to remove root, then factory restore.
an0ther said:
Sounds like you didn't flash the stock recovery.
There is a guide on how to lock your boot loader without it saying relocked in the m8 forums.
You would need to soff, unlock boot loader, flash stock rom and recovery, boot into twrp "don't flash recovery" and root your phone, relock phone the proper way, remove tampered label, go back to s-on, use supersu to remove root, then factory restore.
Click to expand...
Click to collapse
Your directions arent very clear. How would you boot into twrp after you just flashed stock ROM and recovery.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
hugebulge said:
Your directions arent very clear. How would you boot into twrp after you just flashed stock ROM and recovery.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
have twrp on your computer in fastboot directory
fastboot boot twrp.img
it will boot twrp without flashing recovery
Sent from my HTC One_M8 using XDA Premium 4 mobile app