okay i have several questions, so please bear with me. I just can't find the answers to these, and i've been looking for days.
coming from stock android 2.20 firmware. i followed zedomax (on youtube) tutorial and unlocked the bootloader, installed the ViperX ROM (having to use fastboot boot.img, a process i still don't really understand, I thought the recovery was supposed to be able to load ROMs, apparently this is an issue with my version of hboot?), then installed goomanager and updated TWRP. Followed the instructions, have S-OFF. Made a recovery, used Titanium Backup.
However, i still had random reboots, drained battery overnight, and poor/dropped phone signal all the time. Reading in the ViperX thread it seems like people with my issues need to install a kernel (apparently with my firmware i need the beastmode?) and maybe a radio (or is radio and firmware combined, because several people seemed to say that and there's a folder about radio stuff in the kernel zip?) to fix these issues, however there are no installation instructions that i can find in the beastmode release thread and when i found the zip, put it on my internal storage, and tried to load it in TWRP, got the same error message as when i try to load a ROM that way. So it's an issue with hboot 1.14, which is an issue with my firmware (2.20?) And i've spent half the night trying to figure out which firmware i need to fix that, if it can be done. Can i fix my issue so i no longer need fastboot to load a ROM or kernel, and can do it directly from recovery?
sorry for a long rant. i'd love some help. i know there are some 'tools' that are supposed to get around this stuff but i'm trying to genuinely learn what it is i'm doing.
You should have no trouble flashing the Beastmode kernel regardless of your hboot because you're s-off. Which version of the kernel are you flashing? What is the filename? Are you absolutely sure you're s-off?
The recovery does load ROMs and kernels, but there is a restriction in place on hboots equal to or greater than 1.14 which doesn't allow the boot.img to be flashed through recovery. Hence the need to flash it via fastboot. This is only true for s-on devices though, s-off devices circumvent security checks and therefore allow the boot.img to be flashed during the recovery install.
Sent from my Evita
Signal drop and random reboots can either be solved by installing Beastmode kernel or updating to the 2.15 "firmware". Its typically not necessary to do both.
The term "firmware" is a bit confusing. But for the purposes of solving the signal drop and reboot issues on Sense 5 ROMs, the 2.15 firmware being referred to is not the ROM itself, but other modules that came packed with the Sense 5 OTA. The 2.15 "firmware" consists of radio, hboot, boot.img, as well as WiFi and media modules.
The file needed to updated to 2.15 firmware and instruction are included in the top post of Turge's stock ROM thread (SuperCID and S-off required): http://forum.xda-developers.com/showthread.php?t=2423735
timmaaa said:
You should have no trouble flashing the Beastmode kernel regardless of your hboot because you're s-off. Which version of the kernel are you flashing? What is the filename? Are you absolutely sure you're s-off?
The recovery does load ROMs and kernels, but there is a restriction in place on hboots equal to or greater than 1.14 which doesn't allow the boot.img to be flashed through recovery. Hence the need to flash it via fastboot. This is only true for s-on devices though, s-off devices circumvent security checks and therefore allow the boot.img to be flashed during the recovery install.
Sent from my Evita
Click to expand...
Click to collapse
Oh wow that was fast guys, I really appreciate the help.
I wish i could take a screenshot of the bootloader but it says plain as day to me :
*** TAMPERED ***
*** UNLOCKED ***
EVITA PVT SHIP S-OFF RL
CID-111111111
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
I know there's a way to get phone info in cmd but i don't remember what the command is but if you tell me i'll get it for you
file name for the kernel (as far as i know, that thread was messy to me, i felt like most of it was way over my head and that made me nervous to use it) :
Beastmode_RELOADED_3.5.zip 13.0 MB
redpoint73 said:
Signal drop and random reboots can either be solved by installing Beastmode kernel or updating to the 2.15 "firmware". Its typically not necessary to do both.
The term "firmware" is a bit confusing. But for the purposes of solving the signal drop and reboot issues on Sense 5 ROMs, the 2.15 firmware being referred to is not the ROM itself, but other modules that came packed with the Sense 5 OTA. The 2.15 "firmware" consists of radio, hboot, boot.img, as well as WiFi and media modules.
The file needed to updated to 2.15 firmware and instruction are included in the top post of Turge's stock ROM thread (SuperCID and S-off required): http://forum.xda-developers.com/showthread.php?t=2423735
Click to expand...
Click to collapse
thank you for the info! I remember finding a link to that thread and being reluctant to install it because he didn't really label what it was, and the more i read about firmware/radio signals/kernals the more it seemed you you needed to be CERTAIN what you're doing before doing it. Will installing that firmware in the first post overwrite my Viper ROM and necessitate some kind of reinstallation or will i be good to go after that?
self.hating.att.slave said:
Will installing that firmware in the first post overwrite my Viper ROM and necessitate some kind of reinstallation or will i be good to go after that?
Click to expand...
Click to collapse
ROM will be untouched. It just install the modules I mentioned. But always backup your personal data and current ROM when flashing anything.
boot.img will be overwritten. But as you are so far unable to install the Beastmode kernel, it should just be the same kernel as ViperXL, anyway.
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.31a.32.45.16_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.08.111.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT245W302569
(bootloader) imei: 359691041642243
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4170mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-de589c6eef
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Looks like it worked. It sounds like I should be cautiously optimistic at this point, but thanks again for your help.
I'm confident that it has worked, your hboot and radio are both updated.
Sent from my Evita
timmaaa said:
I'm confident that it has worked, your hboot and radio are both updated.
Sent from my Evita
Click to expand...
Click to collapse
Yeah, what I was referring to was the reception and battery/rebooting issues, and so far i haven't had a single one. Battery life is phenomenal, better than it ever was on stock Sense, and I'm really glad I did this. What a great rom. Thanks for your help again guys!
Related
I have had this great phone for around 3-4 months now. In the second week of owning it, I already unlocked the bootloader and rooted my phone. It is not S-OFF, because I'm under the impression that you need to buy extra hardware.
What I want to know is if there is any way that I can flash 3.18 RUU on my AT&T branded (but I use T-Mobile) evita? If there is, can you provide me with a link?
Again, I'm already rooted and I'm bootloader unlocked. Thanks
You don't need to buy any hardware or modify your phone physically to gain s-off, all you need to do is follow the instructions on this thread.
If you have SuperCID (which you most likely do) and try to RUU while you're s-on you'll brick your phone. So my advice is to go to the s-off thread I linked to before, and follow the instructions.
Once you've done that you can run the 3.18 RUU.
Sent from my Evita
Thanks, mate. I appreciate the fast answer. Naturally, I hate being left behind; and seeing that most of the new ROMs require S-Off for the 3.4 kernel, I decided it was time to upgrade. I'll give it a try, as I'm currently trying to flash a ROM because I mistakenly flashed one of ^. Now, it's stuck on the the HTC splash screen, and I guess it's just the first boot scenario. However, it has taken a curious amount of time.
Yeah it's pretty much gonna be essential from now on anyway so you might as well get it outta the way.
What ROM did you try to flash? Also, what firmware/hboot are you currently on?
Sent from my Evita
I tried flashing CarbonROM. It gave me that (Status 7) error so I figured it was the 3.4 kernel giving me problems. After that, I tried flashing a previous version of CarbonROM, and it'd just stay stuck in the splashscreen (This is the ROM that I was discussing in my previous post). Now I tried to flash RageXL, and it's bootlooping. So I'm figuring that I should just go to a stock ROM and get this procedure done, and THEN flash a custom ROM. #BadLuckw3r3w0lv33
Ok. Yep it's the fact that you haven't yet upgraded via the RUU that these ROMs won't boot. Try flashing something like MagioRom or ViperXL just to get the s-off procedure done.
Sent from my Evita
Hmph. I'm pretty sure I've downloaded the latest Google and HTC USB drivers. Still, when I enter "adb reboot bootloader", this pops up:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device offline
I have enabled USB debugging on my HOXL. Perhaps, it's the HTC Sync Manager? I have no clue beyond that point. I even tried restarting my phone AND computer.
EDIT: Nevermind, I just manually rebooted to the bootloader and continued from there. I am now S-Off
:thumbup:
Sent from my Evita
Btw.... If I helped you, please press the thanks button.
Sent from my Evita
Help me please
timmaaa said:
You don't need to buy any hardware or modify your phone physically to gain s-off, all you need to do is follow the instructions on this thread.
If you have SuperCID (which you most likely do) and try to RUU while you're s-on you'll brick your phone. So my advice is to go to the s-off thread I linked to before, and follow the instructions.
Once you've done that you can run the 3.18 RUU.
Sent from my Evita
Click to expand...
Click to collapse
Can i install 2.20 firmware after installing 3.8 firmware.. I have s-off and unlocked bootloader and had my AT&T htc one x evita rooted before i installed 3.18 firmware... please help i cant root my phone on 3.18....
hirias said:
Can i install 2.20 firmware after installing 3.8 firmware.. I have s-off and unlocked bootloader and had my AT&T htc one x evita rooted before i installed 3.18 firmware... please help i cant root my phone on 3.18....
Click to expand...
Click to collapse
If you are already s-off, just install custom recovery, then flash a rooted ROM or SU to get root.
Sent from my HTC One XL using xda app-developers app
Will this RUU work if I have a locked bootloader and s-on?
Chudawg62 said:
Will this RUU work if I have a locked bootloader and s-on?
Click to expand...
Click to collapse
As I said earlier in the thread, SuperCID + s-on + jb RUU = brick.
Sent from my Evita
guys can you please help me here?
my phone is
*** LOCKED ***
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
Junn 11 2012,14:36:28
i dont understand thiss phone that well so can you please tell me if its safe to install the stock jellybean RUU on my phone?
Yes you're s-off so you can run the RUU with minimal risk.
Sent from my Evita
3.17 or 3.18?
Hi,
First off, thanks everyone - this forum has provided me a wealth of information.
I'm wondering if I can run non-sense based roms (ex. Cyanogenmod 10.2 or 11) without downgrading the touchpanel firmware. Here are my phone specs:
C:\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.31a.32.45.16_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.08.111.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT27XXXXXXXX
(bootloader) imei: 359691XXXXXXXXX
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4050mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-de589c6eef
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Currently running ViperXL Android 4.2.2, stock kernel. Had to upgrade to HBOOT 2.15 to get rid of the random reboots and signal drop.
Before I upgraded HBOOT from 2.14 to 2.15 I was pretty sure I was on 3.17. I'm not even sure how to check this again? Would the upgrade to hboot 2.15 put me on 3.18? Sorry for the n0ob questions, help would be appreciated.
Current aosp ROMs no longer require you to down the ts firmware, they haven't since about June. You're a bit confused about the terminology, you didn't just upgrade to the 2.15 hboot, you upgraded to the 2.15 firmware, so you're currently on the 2.15 firmware. The hboot is only one component of the firmware as a whole.
Long story short, yes you can flash non-sense ROMs.
Sent from my Evita.
timmaaa said:
You don't need to buy any hardware or modify your phone physically to gain s-off, all you need to do is follow the instructions on this thread.
If you have SuperCID (which you most likely do) and try to RUU while you're s-on you'll brick your phone. So my advice is to go to the s-off thread I linked to before, and follow the instructions.
Once you've done that you can run the 3.18 RUU.
Sent from my Evita
Click to expand...
Click to collapse
can i run this RUU if i'm on CM10.2 ? and it says it will delete ALL from my phone, do i need to flash a rom and gapps right after i did that or will it still boot on CM10.2 ?
The RUU returns your phone to a stock configuration (ROM/recovery). You need to flash TWRP recovery again afterwards and then your ROM.
Sent from my Evita.
timmaaa said:
The RUU returns your phone to a stock configuration (ROM/recovery). You need to flash TWRP recovery again afterwards and then your ROM.
Sent from my Evita.
Click to expand...
Click to collapse
it doesn't work, i'm getting the usb connection error (170) but the cmd adb devices works just fine and the rumrunner s-off procedure went fine too...maybe i'm missing something ?
Hi all!
Im in a big pickle here and I cant get myself out at the moment.
First hand.. The info
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.13.0000
(bootloader) version-baseband: 0.17.31501S.10_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4011000
(bootloader) cidnum: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3917mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d92cc658
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.093s
Now i've been running cyanogenmod 10 stable since I started rooting etc...
And it's been amazing, but now since there has been a release candidate for 10.1, I was looking into updating it.
I ran into an issue where my boot-loader was not accepted , therefor i would run into an error on Clockwork mod stopping me from flashing 10.1
The bad thing was that I erased my previous installation without backing up the stock and CM10.
So now i'm left with no system. Though I can get into Fastboot and ADB via recovery.I
For some reason if I try to flash CM10 (The rom and the boot file) the cyanogenmod logo will continue spinning.
I tried to fiddle around with my RUU afterwards because I currently have S-On. But i later learned that i need superCID.
^(Which i learned that you need your phone on to alter it to the 8 "1"s) Which i cant do because i have no system.
I might have already altered some files guessing that my boot-loader is named "dirty-d92cc658" and im afraid that I messed up something internally.
So anyways. Im here with my Ville S4 plugged in on fastboot not knowing what to do.
Any Help would be amazing , thank you
Did you try a RUU for Rogers? Not sure if there is one but try to find a RUU that matches your cid
c19932 said:
Did you try a RUU for Rogers? Not sure if there is one but try to find a RUU that matches your cid
Click to expand...
Click to collapse
Do I need to have superCID to flash RUU's ?
Mozziliac said:
Do I need to have superCID to flash RUU's ?
Click to expand...
Click to collapse
If you have a RUU for your specific phone, no, you just need to lock the bootloader.
Have USB debugging turned on (unless running ruu when your phone is in fastboot usb mode)
If you can't find one for Rogers, then yes you have to be super cid to run another RUU.exe (after that change your cid back so an OTA update doesn't brick your phone)
If your phone is on Jellybean, you need to run a JB ruu, if it's Ice Cream Sandwich it won't run. Unless you are supercid I guess.
Khan.orak has a guide for OTA zips to return to stock that you might want.
http://forum.xda-developers.com/showthread.php?p=44365370
Ville / VilleC2 RUU, OTA and Stock Nandroid Collection
http://forum.xda-developers.com/showthread.php?t=2200930
tivofool said:
If you have a RUU for your specific phone, no, you just need to lock the bootloader.
Have USB debugging turned on (unless running ruu when your phone is in fastboot usb mode)
If you can't find one for Rogers, then yes you have to be super cid to run another RUU.exe (after that change your cid back so an OTA update doesn't brick your phone)
If your phone is on Jellybean, you need to run a JB ruu, if it's Ice Cream Sandwich it won't run. Unless you are supercid I guess.
Khan.orak has a guide for OTA zips to return to stock that you might want.
http://forum.xda-developers.com/showthread.php?p=44365370
Ville / VilleC2 RUU, OTA and Stock Nandroid Collection
http://forum.xda-developers.com/showthread.php?t=2200930
Click to expand...
Click to collapse
How can I superCID my phone if I cant boot into the rom?
I've never superCid, can't help you there.
Good news is you can get into bootloader still.
You could fastboot flash a boot.img and flash a rom in recovery.
Just need to mount usb storage in recovery to put the rom.zip on your phone.
Edit: reread that you tried that but rom didn't boot. Hopefully you waited 5-10 min for first load.
try wipedata/factory reset from CWM like 3 times then flashing?
Good luck to ya.
Edit 2: kind of wondering if you can run the Rogers RUU with that low of a bootloader (version-bootloader: 1.13.0000)
Maybe someone can chime in, because that would be nice not having to SuperCid.
Alright so I seemed to get it running on CM 10 by switching recoveries and flashing it's boot.
Then I was able to superCID the phone, which then lead my into S-off'ing it.
Then I was able to update the hboot firmware to 2.15
Cleared the cache and installed the new kernel and flashed cyanogenmod 10.1 rc
Everything went well after that. I did run into a laggy issue, which I then fixed by switching the CPU governor to ondemand instead of interactive.
Thanks for the post guys
Ok, I'll start from the beginning.
I purchased my phone from Rogers at April 2012. So it was Rogers stock 4.0.x rom, everything was locked at that time. I FORGOT the stock hboot/ruu version number for Rogers ONE XL.
From the time being, I rooted it, superCID, unlocked via HTC DEV. After these, I flashed customer recovery, and successfully flashed several roms from time being. Finally I stayed with ViperXL.
Then, facepalm s-off is released, and I s-offed my phone. Everything worked just fine.
The problem occurred when I started to flash sense 5 roms about couple weeks ago. I did not upgrade my firmware and I flashed sense 5 based roms (this is my bad), so I'm experiencing random reboot and signal drops. Then I upgraded my firmware using the instruction in this tread: http://forum.xda-developers.com/showthread.php?t=2423735 . I verified my installtion with ./fastboot gervar all . At this time, there were two warnings on the top of my bootloader: "tampered" and "unlocked".
So, at this time, I tried several sense 5 roms. My recovery at this time was TWRP 2.6.3.0. All the roms have one common problem on my phone: after I locked the screen and left my phone for a while, if I wanna wake my phone/display, nothing happened by pressing the power button. I have to press the power button for 10+ seconds to restart my phone. If I just left my phone for a short time and wake it, it will work properly.
I was thinking are these sense 5 problems, so I tried to flash cm roms yesterday. I followed the instructions in http://forum.xda-developers.com/showthread.php?t=2382933 to upgrade my RUU to 3.18. I flashed TWRP 2.6.3.0, and tried to flash cm 10.1 and 10.2. For cm 10.2, there were a lot of force close when I boot my phone. For cm 10.1, it is so unstable with random reboots as well as did not respond when I try to wake up the phone. I am not questioning CM's roms, I am sure there were something wrong with my phone or what I've done to it.
So, I tried to flash viper rom again with ruu 3.18 installed. The rom won't even boot...... However I found something interesting when I am flashing the viper rom. The size of ViperXL is 700+ MB while the size of CM 10.1 or 10.2 is around 180MB. The time it took to flash ViperXL was shorter than the time it took to flash CM roms.
Then I re-installed the RUU 3.18 update on my phone. Right now, the AT&T stock rom also will not respond after I left my phone idle for a moment......
User timmaaa kindly reminds me about something. I am posting the original post I started in another tread.
Originally Posted by snake3276120 View Post
After I ran the RUU 3.18 upgrade in this tread: http://forum.xda-developers.com/show....php?t=2382933
I boot into bootloader, and ran fastboot getvar all, the result is:
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.14.0000
(bootloader) version-baseband: 0.24p.32.09.06
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.18.502.6
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT246W304864
(bootloader) imei: 359691041684351
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4122mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-97c9a06e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.061s
I'm assuming "(bootloader) version-main: 3.18.502.6" is the RUU version. I also flashed an hboot 2.14, it became 3.17.xxxxxxx. That'w why I am assuming this is the RUU number.
Ok, regardless of the build number or ruu...... I think there is something wrong with my bootloader. It doesn't matter which hboot I flash (hboot 2.14 with version-main 3.17/3.18, or hboot 2.15 with version-main 5.08), and I tried several twrp (2.4.4.0 and 2.6.3.0). The time it took to flash viper xl is really short while viper xl has 700MB. It is even shorter than the time I flash CM, which is around 180 MB. (Sorry for the bad English, I actually mean "The size of ViperXL is 700+ MB while the size of CM 10.1 or 10.2 is around 180MB. The time it took to flash ViperXL was shorter than the time it took to flash CM roms.")
I guess I'll start with the current AT&T stock rom (which still lose respond after I left the phone open for a while, and I have to press the power button for 10 secs to reset my phone)on hboot 2.14 and ruu 3.18. Root it, try to s-off again. Not sure if this will solve the problem.
Something interesting when I'm booting my phone, when the phone displays only the green HTC in the middle of the display, there is some text below it... saying something like "This is an internal build, do not distribute outside of HTC, failure may cause to law action". However, the AT&T stock rom I'm running right now does not have this.
timmaaa:
It's a bit hard to follow what you're saying there but here goes. It's not the RUU number it's the build number. An RUU is the program that updates your phone, the reason you see them referred to as the 3.18 RUU is because they're known by the build number that they update your phone to.
Did you check the md5 of the downloaded file as someone else suggested? It might be corrupt. Also, maybe you should try TWRP 2.6, versions 2.4.x and 2.5.x are well known as being very buggy, and I've seen people have issues with version 2.6.3 too. 2.6 is rock solid though.
The red text you see when the phone boots up is completely normal for a modified phone so you needn't worry about that. The reason the stock ROM doesn't have it is because the RUU has returned your phone to being completely stock, therefore not modified, therefore no red text.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
OK, I am wondering where I can get my RUU number......
Also, in this case, what I should do now? Install TWRP 2.6.0.0 and try to flash everything again?
Currently "tampered" is gone from my bootloader, only "unlocked" stays there.
Lol you've kinda mashed my quote in with your post there so it's hard for people to see where they begin and end.
What do you mean you want to get your RUU number? Like I said an RUU is a program, what exactly do you mean?
Sent from my Evita
timmaaa said:
Lol you've kinda mashed my quote in with your post there so it's hard for people to see where they begin and end.
What do you mean you want to get your RUU number? Like I said an RUU is a program, what exactly do you mean?
Sent from my Evita
Click to expand...
Click to collapse
Because some posts are saying RUU 3.17 or 3.18, so I got confused...... but as long as it's a program, I will assume they are talking about the firmware or bootloader after running RUU 3.17 or 3.18 upgrade.
timmaaa said:
Lol you've kinda mashed my quote in with your post there so it's hard for people to see where they begin and end.
What do you mean you want to get your RUU number? Like I said an RUU is a program, what exactly do you mean?
Sent from my Evita
Click to expand...
Click to collapse
I fixed the qoute
Just to be clear, after you ran the 3.18 RUU you booted the phone without making any modifications and the problem was still occurring, right? It seems to me that it might be some kind of hardware problem that's causing a sleep of death every time the phone goes into sleep mode.
Sent from my Evita
timmaaa said:
Just to be clear, after you ran the 3.18 RUU you booted the phone without making any modifications and the problem was still occurring, right? It seems to me that it might be some kind of hardware problem that's causing a sleep of death every time the phone goes into sleep mode.
Sent from my Evita
Click to expand...
Click to collapse
That's right, I didn't even flash recovery... Well, my stock rom just self-rebooted, and stuck at booting animation while adb is still able to recognize it, and I can issue a reboot from adb. This also applies to my sense 5 roms.
If it's hardware problem, looks like upgrading to hboot 2.15 ruined my hardware, which is hard to believe...... Everything works fine before I upgrade my hboot to 2.15
Unfortunately it isn't under warranty anymore either.
Sent from my Evita
timmaaa said:
Unfortunately it isn't under warranty anymore either.
Sent from my Evita
Click to expand...
Click to collapse
I know... it is unfortunate...
timmaaa said:
Unfortunately it isn't under warranty anymore either.
Sent from my Evita
Click to expand...
Click to collapse
I upgraded my hboot to 2.15 and I flashed MaginRom 4.0. At least it's booting...... looks like my recovery hates aroma installer.
snake3276120 said:
I upgraded my hboot to 2.15 and I flashed MaginRom 4.0. At least it's booting...... looks like my recovery hates aroma installer.
Click to expand...
Click to collapse
Confirm your hboot and baseband version and post here. You said it upgraded, but let's make sure it actually was completely successful.
Also, I think TWRP 2.6.3 has some bugs, not sure if AROMA is one of them. You might check the TWRP thread. But I believe other 2.6.x versions are very stable. I've been on 2.6.0 for a while, and everything seems to be working great, and don't remember any bug reports on that version.
Yeah I can confirm I've seen folks with bugs on 2.6.3 but I've been using 2.6 for months and not a single problem (and no reports of bugs from others).
Sent from my Evita
timmaaa said:
Yeah I can confirm I've seen folks with bugs on 2.6.3 but I've been using 2.6 for months and not a single problem (and no reports of bugs from others).
Sent from my Evita
Click to expand...
Click to collapse
I used 2.6.0.0 to flash my current magiorom 4..... well at least it is usable now, with app/sense/notification bar/wake phone do not respond sometimes... I'm not blaming the rom, I am blaming my phone... probably now it's the time to get a new one lol
redpoint73 said:
Confirm your hboot and baseband version and post here. You said it upgraded, but let's make sure it actually was completely successful.
Also, I think TWRP 2.6.3 has some bugs, not sure if AROMA is one of them. You might check the TWRP thread. But I believe other 2.6.x versions are very stable. I've been on 2.6.0 for a while, and everything seems to be working great, and don't remember any bug reports on that version.
Click to expand...
Click to collapse
Here you are, boss.
PS E:\Program Files (x86)> cd '.\Minimal ADB and Fastboot'
PS E:\Program Files (x86)\Minimal ADB and Fastboot> .\fastboot.exe getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.31a.32.45.16_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.08.111.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3874mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-de589c6eef
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.061s
PS E:\Program Files (x86)\Minimal ADB and Fastboot>
Click to expand...
Click to collapse
I think the result is the same in thread http://forum.xda-developers.com/showthread.php?t=2423735
Quoted from the thread:
Install:
Installing the rom:
Download the rom and copy to your sdcard
Reboot to Recovery
Flash rom
I recommend you wipe data before or after flashing the rom
For root access, flash this: Flash this in recovery for root access
Reboot
OPTIONAL: Installing the Firmware (Warning: You MUST be S-OFF and Super CID to flash this! Flash at own risk!)
Reboot to bootloader (adb reboot bootloader if "USB Debugging" is enabled in Android)
Run: fastboot oem rebootRUU
Run: fastboot flash zip <PathToFirmware.zip>
If the output ends with "FAILED (remote: 90 hboot pre-update! please flush image again immediately)", run the previous command AGAIN
If it ends with "INFO..... OK", reboot to the bootloader: fastboot reboot-bootloader
Verify everything was successful by running: fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.31a.32.45.16_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.08.111.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4140mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-de589c6eef
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Reboot into Android: fastboot reboot or into recovery: fastboot reboot-recovery
Click to expand...
Click to collapse
Please refer to the attachment for a photo of my bootloader
Will TWRP 2.3.3.0 solve my problem? It looks like most roms recommend this recovery.... btw I'm running 2.6.0.0 at the moment.
No, changing TWRP won't solve your problem. You said you're using TWRP 2.6 now and that version is fine. I'd suggest trying one more time to do a clean flash, so wipe cache/dalvik cache/factory reset/system and install the ROM. Hell, do the wipe two or three times to be sure before installing.
Sent from my Evita
timmaaa said:
No, changing TWRP won't solve your problem. You said you're using TWRP 2.6 now and that version is fine. I'd suggest trying one more time to do a clean flash, so wipe cache/dalvik cache/factory reset/system and install the ROM. Hell, do the wipe two or three times to be sure before installing.
Sent from my Evita
Click to expand...
Click to collapse
lol thanks... Every time before I flash a new rom, I just format everything...
I don't know what to tell you then. There's nothing wrong with the ROMs you're using so it's either a case of user error or hardware failure of some kind.
Sent from my Evita
timmaaa said:
I don't know what to tell you then. There's nothing wrong with the ROMs you're using so it's either a case of user error or hardware failure of some kind.
Sent from my Evita
Click to expand...
Click to collapse
Thanks for all the help... I think it is hardware error... because I'm an electrical/computer engineer, I don't think I can't even handle flashing roms... Maybe I need to do more research lol
One XL is a nice phone, I don't wanna switch yet...
snake3276120 said:
Thanks for all the help... I think it is hardware error... because I'm an electrical/computer engineer, I don't think I can't even handle flashing roms... Maybe I need to do more research lol
One XL is a nice phone, I don't wanna switch yet...
Click to expand...
Click to collapse
Could you also try one last thing? Could you upgrade your twrp to latest release and try flashing cm 10.2 0310 nightly please.
Sent from my One X using Tapatalk 4
sandys1 said:
Could you also try one last thing? Could you upgrade your twrp to latest release and try flashing cm 10.2 0310 nightly please.
Sent from my One X using Tapatalk 4
Click to expand...
Click to collapse
Ok I'll do a backup and try tonight....latest twrp do u mean 2.6.3.0, or there is another new release?
My Old One S (Formerly running one of the ViperOneS Rom's until I buggered something up trying to do a factory reset/wipe) is in dire need of some serious upgrades and I could really use a little guidance on getting started. It's been a few phones and probably ~2 years or so since I've really done anything with this device so I'm pretty rusty as far as HTC processes, etc. go, so please bear with me. I want to make sure that I do this right and save myself from tearing my hair out
Some pertinent info:
I use a linux (Ubuntu 14.04) system with my primary box and prefer to do all work with it, though I do have an old laptop with XP on it if I absolutely HAVE to use Windows for something.
Carrier: T-mobile US
Phone info from Bootloader:
VLE PVT SHIP S-ON RL
hboot: 1.14.0004
Radio: 1.08ts.50.02.16
Fastboot devices: HT2xxx407xxx
Right now I can access the bootloader, fastboot, and recovery (TWRP v2.3.3.0).
Please help me with:
I want to upgrade this to a 4.4.4 ROM such as the CM11s port from the OnePlus One or possibly the latest Venom ROM for the OneS (4.3.1) since I had a great experience with the last version I used I know to do this I'll need to RUU to 2.15 or 2.16, but from what I've been reading/researching here on the forums I'm starting to feel a little overwhelmed and want to make sure that I execute the proper sequence of steps to do this correctly.
Where do I start? Should I work to get S-off first, then try to RUU to the latest hboot? Knowing which ROM I would want to use, which RUU should I download? What do I need to do about the radio? At what point should I try to flash a new recovery?
Much thanks, I really appreciate it!
http://forum.xda-developers.com/showthread.php?t=2527194
---------- Post added at 11:42 AM ---------- Previous post was at 11:42 AM ----------
Try that tool
I appreciate the recommended tool Bad.Fish, but that's for the M7 (not the OneS) so I'm not sure that'll work, especially since it says I need to be S-Off and I'm pretty sure I'm still locked so...
Also, a development...
I just tried pushing the previous Viper rom I was running (2.1 I think) over adb to the sdcard and when I try to flash it I get a bunch of errors that it's unable to mount /cache or /sdcard. What could possibly cause this? After rebooting the recovery, the .zip file I pushed using adb doesn't even appear as available anymore...
More info from fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.14.0004
(bootloader) version-baseband: 1.08ts.50.02.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT2xxx407xxx
(bootloader) imei: 35990xxx3722xxx
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4011000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4151mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 8b9e2080
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
So, I have the dreaded "can't mound sdcard" issue that requires installing a stock recovery before re-installing a custom recovery. Knowing my CID is T-MOB010 I see 3 different recovery options from THIS THREAD being 4.19.531.10, 3.24.531.3, and 1.27.531.11. How can I tell which of these I should use?
shoot, I'm just really frickin lost at this point guys, I don't know what to do anymore
samstheman42 said:
I see 3 different recovery options from THIS THREAD being 4.19.531.10, 3.24.531.3, and 1.27.531.11. How can I tell which of these I should use?
Click to expand...
Click to collapse
I would guess the 3.24 (just based on age) but it probably doesn't matter, as I doubt the recoveries are different.
Also, in reply to this: http://forum.xda-developers.com/showpost.php?p=55885509&postcount=523....
You can not 'upgrade' from 2.15 to 2.16 by just flashing a hboot. You have to update all firmware. If I remember correctly, there is a RUU-mode zip for that somewhere. (I no longer use this device, and I never went past 2.15.)
-Jobo
Any help/advice you can give me on how to fix this/get back to a working device would be SO appreciated! Right now, about the only thing that I can get it to do is boot to recovery or into the bootloader, so I know that there's hope! I tried running an RUU yesterday but that failed partway through (I'm not sure why, maybe cause I didn't have the right recovery image?). I know I might need a little bit of hand holding, but I will be so grateful to whomever helps me figure this out.
Ok, I might have FINALLY gotten something going here... running an RUU right now that appears to be working, so with any luck, I'll finally have a working device again
This is really good news because now I won't have to spend upwards of $250 on a new phone! lol
Great success! Phone just booted up and we're back on stock! Woohoo!!!!! Now to start the rooting/rom'ing process
samstheman42 said:
I appreciate the recommended tool Bad.Fish, but that's for the M7 (not the OneS) so I'm not sure that'll work, especially since it says I need to be S-Off and I'm pretty sure I'm still locked so...
Also, a development...
I just tried pushing the previous Viper rom I was running (2.1 I think) over adb to the sdcard and when I try to flash it I get a bunch of errors that it's unable to mount /cache or /sdcard. What could possibly cause this? After rebooting the recovery, the .zip file I pushed using adb doesn't even appear as available anymore...
Click to expand...
Click to collapse
I used it on my one s
---------- Post added at 02:02 AM ---------- Previous post was at 02:01 AM ----------
Use rumrunner to s-off
Hi, I got the SIM unlock code from my carrier for my HTC One S but it doesn't appear to work. It's also a lot shorter than the code I used on my Xperia Z1 (same carrier) but they say that it's supposed to be valid.
My HTC One S has the bootloader unlocked and CyanogenMod 10.2 installed on it. Could not having a locked bootloader and stock ROM be the reason the unlock code doesn't work?
Thanks!
polybius said:
Hi, I got the SIM unlock code from my carrier for my HTC One S but it doesn't appear to work. It's also a lot shorter than the code I used on my Xperia Z1 (same carrier) but they say that it's supposed to be valid.
My HTC One S has the bootloader unlocked and CyanogenMod 10.2 installed on it. Could not having a locked bootloader and stock ROM be the reason the unlock code doesn't work?
Thanks!
Click to expand...
Click to collapse
You probably need the non modified stock firmware installed.
BTW you can also unlock it for FREE
Well, I did get the code for free
Yeah, I've been trying to restore everything to stock to find out but I'm having problems with that also. Perhaps I'll try the link you posted to verify the code. Maybe it's slightly different. Thanks!
Well, the code is the same, guess it just won't unlock without being stock ROM or something and I can't get it back to stock
polybius said:
Well, the code is the same, guess it just won't unlock without being stock ROM or something and I can't get it back to stock
Click to expand...
Click to collapse
Why can't you get it back to stock?
Any of the guides I follow don't seem to work. I relock the bootloader but then I can't seem to apply the matching RUU for the phone. What looks like the matching one (hboot and radio) is a ZIP file (OTA_Ville_U_JB_45_S_TELUS_WWE_3.16.661.4_1.13.50.05.31_10.30.50.08L_release_307532nohrvy5j6i2o2i8i.zip) and I'm not sure how to apply it. The exe RUU versions don't work either because, I'm assuming, they don't match my hboot and radio. I feel like a pretty competent guy when it comes to rooting and imaging Android devices but this just isn't working for me Thanks for your help.
polybius said:
Any of the guides I follow don't seem to work. I relock the bootloader but then I can't seem to apply the matching RUU for the phone. What looks like the matching one (hboot and radio) is a ZIP file (OTA_Ville_U_JB_45_S_TELUS_WWE_3.16.661.4_1.13.50.05.31_10.30.50.08L_release_307532nohrvy5j6i2o2i8i.zip) and I'm not sure how to apply it. The exe RUU versions don't work either because, I'm assuming, they don't match my hboot and radio. I feel like a pretty competent guy when it comes to rooting and imaging Android devices but this just isn't working for me Thanks for your help.
Click to expand...
Click to collapse
May you type in commandline:
fastboot getvar all
and post all values except your imei here?
version: 0.5
version-bootloader: 2.15.0000
version-baseband: 1.13.50.05.31
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno: HT26EW403840
imei: xxxxxxxxxxxxxxxxxx
product: vle
platform: HBOOT-8960
modelid: PJ4011000
cidnum: TELUS001
battery-status: good
battery-voltage: 4146mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-64bedd38
hbootpreupdate: 11
gencheckpt: 0
all: Done!
finished. total time: 0.068s
polybius said:
version: 0.5
version-bootloader: 2.15.0000
version-baseband: 1.13.50.05.31
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno: HT26EW403840
imei: xxxxxxxxxxxxxxxxxx
product: vle
platform: HBOOT-8960
modelid: PJ4011000
cidnum: TELUS001
battery-status: good
battery-voltage: 4146mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-64bedd38
hbootpreupdate: 11
gencheckpt: 0
all: Done!
finished. total time: 0.068s
Click to expand...
Click to collapse
Flash Viper 2.2 as sense base stock rom.
Use rumrunner to gain S-OFF
Flash any RUU you like
Thanks! I'll give that a try. I read you need SuperCID for S-OFF, does rumrunner do that for you?
polybius said:
Thanks! I'll give that a try. I read you need SuperCID for S-OFF, does rumrunner do that for you?
Click to expand...
Click to collapse
Rumrunner will get you S-OFF. Then you can change the CID.
Perhaps you know, I'm getting this when I try to image that Viper ROM.
assert failed: getprop("ro.product.device") == "ville"
Click to expand...
Click to collapse
polybius said:
Perhaps you know, I'm getting this when I try to image that Viper ROM.
Click to expand...
Click to collapse
Try to first flash the included boot.img before flashing Viper 2.1.0
or try try Viper 3
You need any sense based rom to get S-OFF
Ok, so, I guess I missed the part of installing Viper where it says to have TWRP and not ClockworkMod recovery >_<
Got TWRP on there, was able to flash Viper 2.1 EASILY. And it unlocked like a charm. THANKS!! Didn't have to get S-OFF for the unlock. What ROM is the best for the One S in your humble opinion? Should I still get S-OFF?
polybius said:
Ok, so, I guess I missed the part of installing Viper where it says to have TWRP and not ClockworkMod recovery >_<
Got TWRP on there, was able to flash Viper 2.1 EASILY. And it unlocked like a charm. THANKS!! Didn't have to get S-OFF for the unlock. What ROM is the best for the One S in your humble opinion? Should I still get S-OFF?
Click to expand...
Click to collapse
S-OFF means you can flash any stock RUU e.g unbranded and flash any radio version e.g. 1.20 and the kernel (boot.img) get flashed with the rom via recovery and has not to be flashed by fastboot command.
I actually use Candy 5 v1.5.0 but I can't say what fits your needs best
Does Candy have decent battery life? What is your general experience with it? I really want to put Lollipop on this phone
Also, do you have a good tutorial to remove the red Dev warning on boot?
polybius said:
Also, do you have a good tutorial to remove the red Dev warning on boot?
Click to expand...
Click to collapse
Battery performance is very good for me with Candy 5. I use my phone mainy for messaging and making calls (Its a phone lol). I can't say how long last the battery when you play games or surf the web heavily. For me the battery easy lasts two days.
For getting rid of the red warning you can flash a modded HBoot which can be found HERE. Make sure you use the same version number that is actually installed on your phone but "modded"
LS.xD said:
Battery performance is very good for me with Candy 5. I use my phone mainy for messaging and making calls (Its a phone lol). I can't say how long last the battery when you play games or surf the web heavily. For me the battery easy lasts two days.
For getting rid of the red warning you can flash a modded HBoot which can be found HERE. Make sure you use the same version number that is actually installed on your phone but "modded"
Click to expand...
Click to collapse
Hmmm. I have 2.15 but I seem to be getting an error during the flash: FAILED (remote: 41 model id check fail)
Is that the variance in model that you mentioned earlier?
polybius said:
Hmmm. I have 2.15 but I seem to be getting an error during the flash: FAILED (remote: 41 model id check fail)
Is that the variance in model that you mentioned earlier?
Click to expand...
Click to collapse
Seems so And I don't know how to solve it for PJ4011000. May be you can ask or look in the thread if somebody has successfully done it for your model. You probably can edit the flashable file, but I you should NOT try it, if you not exactly know how.