So my Evita that I rooted/flashed back in October is finally starting to bug out. Six months of smooth sailing, but now it's having Wi-Fi problems, reboot problems, etc. I'm going to go ahead and use it as an opportunity to flash to something newer, but...perhaps someone might be able to tell me what would cause this kind of behaviour? Is it something that could be fixed without reflashing? Something I should just expect over time when I'm using custom ROMs?
Anyways, I have been re-reading up on this stuff to prepare to reflash. Again, I did root/s-off/flash back in October...at that time the Sense 5 ROMs were very early/rough, so I went Sense 4 (CleanROM 6.5). My current bootloader screen reads like this:
*** TAMPERED ***
*** UNLOCKED ***
EVITA PVT SHIP S-OFF RL
CID-11111111
HBOOT-1.14.0002
RADIO-0.19as.32.09.11_2
OpenDSP-v29.1.0.45.0622
eMMC-boot
Jun 11 2012, 14:36:28
Currently installed recovery is TWRP 2.6.3.0
So with all of that said, my goal now is to get as updated as possible, and flash a stable Sense 5 ROM.
Would anyone mind helping me figure out the right plan of attack to do this?
finallygreen said:
So my Evita that I rooted/flashed back in October is finally starting to bug out. Six months of smooth sailing, but now it's having Wi-Fi problems, reboot problems, etc. I'm going to go ahead and use it as an opportunity to flash to something newer, but...perhaps someone might be able to tell me what would cause this kind of behaviour? Is it something that could be fixed without reflashing? Something I should just expect over time when I'm using custom ROMs?
Anyways, I have been re-reading up on this stuff to prepare to reflash. Again, I did root/s-off/flash back in October...at that time the Sense 5 ROMs were very early/rough, so I went Sense 4 (CleanROM 6.5). My current bootloader screen reads like this:
*** TAMPERED ***
*** UNLOCKED ***
EVITA PVT SHIP S-OFF RL
CID-11111111
HBOOT-1.14.0002
RADIO-0.19as.32.09.11_2
OpenDSP-v29.1.0.45.0622
eMMC-boot
Jun 11 2012, 14:36:28
Currently installed recovery is TWRP 2.6.3.0
So with all of that said, my goal now is to get as updated as possible, and flash a stable Sense 5 ROM.
Would anyone mind helping me figure out the right plan of attack to do this?
Click to expand...
Click to collapse
The only thing you need to do to prepare for a Sense 5 ROM is to upgrade your firmware, I have detailed instructions on my How-To Guide For Beginners thread in my signature. Don't ask for a recommendation on a ROM because doing so isn't allowed. To say one ROM is better is to infer that the others are inferior in some way. This is disrespectful to the devs who spend their spare time bringing us these awesome ROMs free of charge. Each user has different tastes anyway, the best way to see which ROM suits you is to flash a few and find out for yourself.
Sent from my Evita
Oh absolutely...in fact you mentioned that to me months ago when I went through this the first time, so I most certainly wasn't looking for a ROM recommendation...just wanted to know what I'd have to do to get where I wanted to be, and in what order I should do it
timmaaa, I noticed you recently told someone who was getting an Evita together for his father that he should go with this firmware:
http://www.androidfilehost.com/?fid=23060877490004040
Because it would allow him to go Sense OR AOSP.
I suppose there's a slight chance I'll want to mess with an AOSP ROM, so should I stick with the one you linked there, or perhaps this one?:
http://forum.xda-developers.com/showthread.php?t=2651052
The 2.15 firmware in my guide thread (and the first link in your post) is the one you want.
Sent from my Evita
Well I guess it really HAS been a long time since I've done this....the folder with fastboot and all of that is still on my PC, but the PC is NOT recognizing the phone at all. In fact, if I plug the phone to the PC via USB while in fastboot, the screen shows "FASTBOOT AC" rather than USB.
USB Debugging is ON. HTC Sync Manager is not seeing the phone either. How did my PC suddenly stop recognizing my phone? What can I do to troubleshoot this?
Eesh...just came down to using a different USB cable...so finicky!
Anyways, all's well...firmware updated, new ROM flashed!
Thanks!
Related
Hi Guys (long time listener first time caller etc etc)
I finally got the courage to install a custom rom on to my HTC One XL (Telstra). After unlocking it installing the custom bootloader (2.5.0.0 TW) I have tried to install some roms and get no where with a few of them and boot loops if they actually install.
The two I can get to install but boot loop are ViperXL and cyanogenmod 10.0.
I am thinking I am doing something really simple wrong, but have tried a lot of things but no luck.
Details below; If there is anything else which might shed some light please let me know.
Evita PVT Ship s-on RL
HBoot-2.14.0000
RADIO-1.26a.32.45.1219
openDSP-v34.1.0.45.1219
eMMC-BOOT
nov 26 2012 18:37:14-1
Is anyone able to steer me in the right direction?
Thanks in advance, Jase
oh, I did install all of Telstra's updates prior to starting. The last one brought android up to 4.1.2 I think.
Jason Broadhurst said:
Hi Guys (long time listener first time caller etc etc)
I finally got the courage to install a custom rom on to my HTC One XL (Telstra). After unlocking it installing the custom bootloader (2.5.0.0 TW) I have tried to install some roms and get no where with a few of them and boot loops if they actually install.
The two I can get to install but boot loop are ViperXL and cyanogenmod 10.0.
I am thinking I am doing something really simple wrong, but have tried a lot of things but no luck.
Details below; If there is anything else which might shed some light please let me know.
Evita PVT Ship s-on RL
HBoot-2.14.0000
RADIO-1.26a.32.45.1219
openDSP-v34.1.0.45.1219
eMMC-BOOT
nov 26 2012 18:37:14-1
Is anyone able to steer me in the right direction?
Thanks in advance, Jase
Click to expand...
Click to collapse
Welcome mate.
Couple of things...
The HBoot version you have won't allow you to update the boot.img of the rom your flashing as part of rom installation. You have 2 options - first is to s-off which pretty much lets you do whatever you like. Check in the original development thread for how to s-off if you're interested.
The second option is to flash (install) the boot.img in bootloader mode.
You can do that either before or after you flash the rom. Before I was s-off I did it both before and after.....
There's a few ways to do it including using adb or some apps will do it automatically for you. Take a look here for one example: http://forum.xda-developers.com/showthread.php?t=1870455
And the second thing - good idea to post questions in the Q&A thread. More people look through there so you'll get your answer faster.
Get rid of twrp5.0, had the same issue, flaahed back to 2.3.3.1 and all is good...
Sent from my HTC One XL using xda premium
Thanks guys. I did the fastboot flash boot and it all came good.
Appreciate the help!
So I did a short search for the answer to this but seems like I cant quit find the answer or it just confusing me and im getting lost. I have an HTC Sensation T-Mobile From the USA model PG58100. This phone is I assume in a bootloop as when it turns on it just stays on the HTC screen. I put it in recovery mode and tried doing just the factory reset but the phone still loops after ward. So i know assume i have to reinstall the stock rom. this phone is not and has never been rooted to my knowledge as I did not receive this new so I am not 100% sure. here is what is displayed when i go into recovery mode
*** LOCKED***
PYRAMID PVT SHIP S-ON RL
HBOOT-1.18.0000
eMMC-boot
Aug 2 2011,22:35:52
I have downloaded Elegencia Sence 4.1 V8.0.0 zip but I will install whatever you guys feel is best for me. I just need the phone back up and running. it does not need to be rooted or have anything special completely stock would be fine. The simplest way to get it working again is all I need. Thank you in advance.
Try here:
http://forum.xda-developers.com/showthread.php?t=2094380
There you have a bunch of RUUs try with some of TMOUS but choose some newer one.
I'm using CM10 and I've been wanting to update my S4 to a KitKat rom for some time and now that some stable builds are starting to come out I decided it was a good time.
On my first try flashing a new rom I got an error message asking for a newer version of hboot (mine is 1.14.0002 and it wanted 2.15.0000), so I looked around and found out I needed a RUU to update that, but since finding one for my phone is pretty difficult I decided to S-Off it, because apparently you can use any RUU that way.
Obviously it's not working, that's why I'm posting this. I did the htcdev method to unlock the phone back when I installed CM10 and to get S-Off I followed the rumrunner method. No problems whatsoever so far. They start appearing as soon as I try to update the 2.15.0000 RUU I downloaded from this other tutorial (the HTC Europe one, since I live here).
Following all the steps in that page I read about needing to change the phone's SuperCID to make it compatible with the RUU. First I tried with the default SCID that my phone had (VODAP304) with no luck. Then after a bit of searching I tried changing it to HTC__001 which seemed to be the correct one for the european RUU, but the same thing happened: it gives an incompatibility error, the process stops, the phone bootloops and I have to do a TWRP restore (the back up is from this morning and I made it just before attempting this, so no data loss of any kind)
These are the numbers bootloader gives me, if they're of any help:
***TAMPERED***
***UNLOCKED***
VLE PVT SHIP S-OFF RL
CID-VODAP304
HBOOT-1.14.0002
RADIO-1.08es.50.02.21
OpenDSP-v29.1.0.45.0622
eMMC-boot
Jun 11 2012, 14:36:28
What exactly am I missing here to update the hboot?
You don't need to install RUU, you need to flash a new firmware. Take a look at [URL="http://forum.xda-developers.com/showthread.php?t=2322755" ]this [/URL] thread.
Sent from my HTC One S
ka_55 said:
You don't need to install RUU, you need to flash a new firmware. Take a look at [URL="http://forum.xda-developers.com/showthread.php?t=2322755" ]this [/URL] thread.
Sent from my HTC One S
Click to expand...
Click to collapse
But isn't that for kernels? In several hours of research I haven't found one post about kernels for my issue
It does look similar to another method I've found recently that flashes the hboot through fastboot/recovery but users say it's much more risky
Rodrows said:
But isn't that for kernels? In several hours of research I haven't found one post about kernels for my issue
It does look similar to another method I've found recently that flashes the hboot through fastboot/recovery but users say it's much more risky
Click to expand...
Click to collapse
Yes it's about kernels and the problem with the new roms is nothing but the kernel. So firmware update is enough as a solution. I don't think it's dangerous if you follow the instructions correctly. But you should follow them word to word with your own risk
Sent from my HTC One S
So I lost my phone this week, and my buddy offered me up his old Inspire for free. He didn't mention the fact that it's like, midway through a failed flash (soft-bricked, I guess?). I've been searching and reading, but I just seem to get further down the rabbit hole with what exactly I'm supposed to do. Really, I haven't run across any threads with this problem yet.
It's currently S-ON, but has CWM installed. There doesn't seem to be a rom installed, because it'll hang on the HTC splash screen on boot (matter of fact, he didn't even give me an SD card with the phone, so I had to scavenge one of my good SanDisk ones) and I'm not entirely sure where to go from here to get it up and running. I don't care much for the Inspire's stock rom, but at this point I'm in dire need of a phone and if it's easier to go back to stock than it is to fix this mess and have a nice ROM, I can live for a little while.
What should I do, and how exactly should I do it? It's been quite a while since I tried this (and even then it was with my lineage of janky huawei handsets).
EDIT: I've got a screencap of the info but the board spam prevention won't let me link it.
***UNLOCKED***
ACE PVT SHIP S-ON RL
HBOOT-0.85.0024
MICROP-0438
RADIO-26.10.04.03_M
eMMC-boot
burk992 said:
So I lost my phone this week, and my buddy offered me up his old Inspire for free. He didn't mention the fact that it's like, midway through a failed flash (soft-bricked, I guess?). I've been searching and reading, but I just seem to get further down the rabbit hole with what exactly I'm supposed to do. Really, I haven't run across any threads with this problem yet.
It's currently S-ON, but has CWM installed. There doesn't seem to be a rom installed, because it'll hang on the HTC splash screen on boot (matter of fact, he didn't even give me an SD card with the phone, so I had to scavenge one of my good SanDisk ones) and I'm not entirely sure where to go from here to get it up and running. I don't care much for the Inspire's stock rom, but at this point I'm in dire need of a phone and if it's easier to go back to stock than it is to fix this mess and have a nice ROM, I can live for a little while.
What should I do, and how exactly should I do it? It's been quite a while since I tried this (and even then it was with my lineage of janky huawei handsets).
EDIT: I've got a screencap of the info but the board spam prevention won't let me link it.
***UNLOCKED***
ACE PVT SHIP S-ON RL
HBOOT-0.85.0024
MICROP-0438
RADIO-26.10.04.03_M
eMMC-boot
Click to expand...
Click to collapse
My strong hunch is that he didn't flash the boot.img in the ROM zip, which you need to do for S-On Unlocked phones. When you flash a ROM in the recovery, make sure you also fastboot flash the boot.img from the ROM zip. The Ace Think Tank thread in DHD General has links with instructions on how to do that.
bananagranola said:
My strong hunch is that he didn't flash the boot.img in the ROM zip, which you need to do for S-On Unlocked phones. When you flash a ROM in the recovery, make sure you also fastboot flash the boot.img from the ROM zip. The Ace Think Tank thread in DHD General has links with instructions on how to do that.
Click to expand...
Click to collapse
Aha! That did the trick. I just flashed Carbon on this thing, but now the Android keyboard won't work. It's okay, I'm sure I can fix it. Thanks for the help!
Yeah, that'll be an issue for the ROM thread. Though of course, if you didn't full wipe first, try that.
IAfter Rooting, S-Offing and installing the Viper ROM, I could not get Wifi to turn on due to a firmware issue. After countless failed attemts to get it to the current version, I decided to move back to stock.
Now, I am inable to get out of Fastboot. When I tried to flash a new ROM, I get the messgae that adb can not see my device. I have no idea what to do, please help.
On top of the astboot screen, it says:
*** TAMPERED ***
*** UNLOCKED ***
M8_UL_CA PVT S-OFF
CID-11111111
HBOOT-3.16.0.0000
RADIO-1.152133156.UA13G
OpenDSP-v38.2.2-00542-M8974.0311
OS-
eMMC-boot 2048MB
Mar 22 2014,00:53:32.0
PLEASE help, I' scared!! Thanks in advance
Hi,
I need to know your device make and model number to point you towards help.
Thanks!
Geeze, I'm sorry.
I am using an HTC One m8 with at&t. I'm not sure how to get the model number.
Also, I must have erased TWRP somehow, because when I select recovery from the Fastboot window, it brings me back to the same place.
You are s-off and super CID, easy to fix...
Here's a guide on updating firmware,
http://forum.xda-developers.com/htc-one-m8/development/firmware-flashing-panic-attacks-t2824048
And you can also flash recovery with fastboot again, same as you did the first time, then put a rom on an external sd card using another device, and flash it on your device from recovery from the sd card.
If you need help on those things, or want other ideas... The place to ask questions about your device is here,
http://forum.xda-developers.com/htc-one-m8/help/help-thread-htc-one-m8-questions-t2897783
Good luck!
Thanks. I'll gove it a try tomorrow when I'm not so tired.
I seriosely can't thank you enough for responding.
That did the trick! You're a life saver, I have no idea how I missed that.
One last question. Now that Firmware is update, it looks like I'm using the google ROM. Can I change it back to Venom i I prefer?
That question should probably be asked in the thread I linked 2nd. I've never converted mine to GPE, or back. ?
You're right, sorry about that.
Seriously, I have no idea how I missed that article but THANK YOU!!!! You quite literally saved my job (conference calls I needed to be on).