Hey Guys!
I have an issue with my HTC One XL.
I want to run the Viper XL Rom with Sense 5. But i always get Data and Signal drops, so i wanted to update my Firmware.
But in order to update my firmware, I have to get S-Off. And in order to get S-Off I have to get the super CID.
I tried to change the CID of my HOXL with the One-Click tool, but the only thing that happens after running this tool is that my screen is freezed and my HOXL is ****ed up.
So I tried the HEX-Edit method. So I changed the CID with Hex-Edit and pushed it back on my HOXL. But after rebooting it, my CID is still the old one.
Does any of you guys know a solution for my Problem? I really want to go S-Off ):
Sorry for my bad english! I hope it's not that hard to understand.
Facts about my HOXL:
Unlocked via HTC Dev
Rooted
HBoot 2.14
S-On
ViperXL 3.2.8
Bulletproof Kernel
Read.
But since english doesn't seem to be your first language update to 2.15 hboot or install beastmode kernel
Sent from my VENOMized HoxL
area51avenger said:
Read.
But since english doesn't seem to be your first language update to 2.15 hboot or install beastmode kernel
Sent from my VENOMized HoxL
Click to expand...
Click to collapse
But to install Beastmode i need to be S-Off, don't I?
Kureno7 said:
But to install Beastmode i need to be S-Off, don't I?
Click to expand...
Click to collapse
Nope. You can flash kernels using fastboot with s-on.
redpoint73 said:
Nope. You can flash kernels using fastboot with s-on.
Click to expand...
Click to collapse
But I read that there is no boot.img for Beastmode?
If there is one, that whole thing is much more easier then I expected
Kureno7 said:
But I read that there is no boot.img for Beastmode?
If there is one, that whole thing is much more easier then I expected
Click to expand...
Click to collapse
I actually haven't been following Beastmode. How does it install, an AROMA installer (I see the download is a zip)?
If so, just flash in recovery (s-off not needed).
redpoint73 said:
I actually haven't been following Beastmode. How does it install, an AROMA installer (I see the download is a zip)?
If so, just flash in recovery (s-off not needed).
Click to expand...
Click to collapse
With Bulletproof Kernel I always had to flash the .zip file in recovery and the "boot.im" separately via fastboot, otherwise I was stuck in Bootloop.
Kureno7 said:
With Bulletproof Kernel I always had to flash the .zip file in recovery and the "boot.im" separately via fastboot, otherwise I was stuck in Bootloop.
Click to expand...
Click to collapse
That's because boot.img won't install in recovery with s-on (and hboot 1.14 or higher). But AROMA bypasses this, which is why I ask if Beastmode uses an AROMA installer or not. I think it does, but someone with actual experience with Beastmode will need to confirm.
redpoint73 said:
That's because boot.img won't install in recovery with s-on (and hboot 1.14 or higher). But AROMA bypasses this, which is why I ask if Beastmode uses an AROMA installer or not. I think it does, but someone with actual experience with Beastmode will need to confirm.
Click to expand...
Click to collapse
Ahh, alright! But I see, that there is a Wifi issue with the Beastmode Kernel.
What about upgrading my HBoot to 2.15. Does that also solve my problem with data drops and reboots?
Is it safe to upgrade HBoot?
Kureno7 said:
What about upgrading my HBoot to 2.15. Does that also solve my problem with data drops and reboots?
Is it safe to upgrade HBoot?
Click to expand...
Click to collapse
Yes and yes
Sent from my VENOMized HoxL
Kureno7 said:
Ahh, alright! But I see, that there is a Wifi issue with the Beastmode Kernel.
What about upgrading my HBoot to 2.15. Does that also solve my problem with data drops and reboots?
Is it safe to upgrade HBoot?
Click to expand...
Click to collapse
The Beastmode kernel uses an aroma installer so you should be ok to flash it while s-on. A few people have reported WiFi problems but I personally never experienced this at all. The only way to find out is flash it, so I suggest doing that. You can always revert if you want to by dirty flashing ROM.
The 2.15 firmware package doesn't just update the hboot, it updates hboot, radio, WiFi modules, and media modules. You need s-off to update to the 2.15 firmware package.
All of this information is readily available in the Viper thread if you took the time to search properly.
Sent from my Evita
Kureno7 said:
What about upgrading my HBoot to 2.15. Does that also solve my problem with data drops and reboots?
Is it safe to upgrade HBoot?
Click to expand...
Click to collapse
I think you mean the 2.15 "firmware" package, which contains not only hboot, but also new radio, WiFi and media modules. Its the radio that seems to be the culprit, so only updating hboot will likely not solve the issue.
I personally feel this is a more comprehensive solution (update to 2.15 firmware), as it will persist even after flashing other ROMs; and its how I addressed the signal issue.
Yes, upgrading hboot is relatively safe. But be aware that any update of hboot (even on a stock device) carries a small chance of bricking the phone if for some reason the update does not go completely right (such as a corrupted file or interrupted flash). But the chances are very small.
---------- Post added at 11:40 AM ---------- Previous post was at 11:12 AM ----------
timmaaa said:
The Beastmode kernel uses an aroma installer so you should be ok to flash it while s-on.
Click to expand...
Click to collapse
Thanks for confirming.
I would suggest Going S-off Its not that hard to do and is so useful.
Beastmode RELOADED 3.5
-Updated aroma installer binaries
-Fixed module installation
When I was on ViperXL It fixed my wifi/data issues (Mostly)
Going s-off and AOSP is the way to go
Hey guys. I don't mean to hijack the thread at all but I'm got the same conundrum at the moment. Running Viper XL 4.2.0 on an unlocked Telstra One XL with Hboot 2.14. I've already tried flashing beastmode 3.5. to no success as I get a boot loop. So I'd preferably like to just get the phone to a complete stock state and then use the WinDroid all in one tool to get where I need to go; S-Off and SuperCID.
Counterflak said:
Hey guys. I don't mean to hijack the thread at all but I'm got the same conundrum at the moment. Running Viper XL 4.2.0 on an unlocked Telstra One XL with Hboot 2.14. I've already tried flashing beastmode 3.5. to no success as I get a boot loop. So I'd preferably like to just get the phone to a complete stock state and then use the WinDroid all in one tool to get where I need to go; S-Off and SuperCID.
Click to expand...
Click to collapse
You don't need to go to a stock state to get SuperCID and s-off, that's taking an unnecessarily long route. To get SuperCID you just need to use the hex edit method. To get s-off you'll probably need to flash an older ROM though as people on Android 4.2.2 have had many problems succeeding.
Sent from my Evita
After some research i found the "solution" for my problem with getting super cid.
My HOXL is branded from Vodafone and the guys from Vodafone "locked" the part in system where you can change the CID.
So it's read only.
Finally, there is no way to go S-Off for me i guess.. ):
Or have u guys other ways except of "Hex-Edit" and "All in one Tool" ?
Greetz!
timmaaa said:
You don't need to go to a stock state to get SuperCID and s-off, that's taking an unnecessarily long route. To get SuperCID you just need to use the hex edit method. To get s-off you'll probably need to flash an older ROM though as people on Android 4.2.2 have had many problems succeeding.
Sent from my Evita
Click to expand...
Click to collapse
Managed to pull the file and edit it ok, but I get the following went trying to push the file back I get the following:
Code:
[email protected]:/ # >dd if=/sdcard/mmcblk0p4 of=/dev/block/mmcblk0p4
>dd if=/sdcard/mmcblk0p4 of=/dev/block/mmcblk0p4
sh: can't create dd: Read-only file system
The last OTA I downloaded was the update that included a touch screen firmware before flashing Viper, but I believe this had some sort of write protection on it as well (Not sure where I read that, might have been on whirlpool) . Of course, the only way to downgrade it that I can find requires S-OFF as well as SuperCID.
Counterflak said:
Managed to pull the file and edit it ok, but I get the following went trying to push the file back I get the following:
Code:
[email protected]:/ # >dd if=/sdcard/mmcblk0p4 of=/dev/block/mmcblk0p4
>dd if=/sdcard/mmcblk0p4 of=/dev/block/mmcblk0p4
sh: can't create dd: Read-only file system
The last OTA I downloaded was the update that included a touch screen firmware before flashing Viper, but I believe this had some sort of write protection on it as well (Not sure where I read that, might have been on whirlpool) . Of course, the only way to downgrade it that I can find requires S-OFF as well as SuperCID.
Click to expand...
Click to collapse
Haha same here mate! Hope one of the experienced members have a solution:crying:
Sorry for disturbing you again guys!
I tried the following ways:
Flash Viper 4.2.0 -> Flash boot.img = Bootloop
Flash Viper 4.2.0 -> Flash Beastmode 3.5 = Bootloop
Flash Viper 4.2.0 -> Flash Beastmode 2.0 -> Flash Beastmode 3.5 = Bootloop
Flash Viper 4.2.0 -> Flash Beastmode 2.0 -> Flash Beastmode 3.5 -> Flash Beastmode 2.0 boot.img = Bootloop
So I restored my data via Backup. Now I'm on Viper 3.2.8 again.
Does any1 of you know a great rom, that I can use on my HOXL, without going S-Off or updating Firmware?
What about this one:
http://forum.xda-developers.com/showthread.php?t=2064724
Is it possible to use AOKP on my phone? Or do I need to downgrade my touchscreen's firmware or stuff like that?
Thx 4 your help !
I believe those older builds of AOKP do require downgraded ts firmware, which in turn requires s-off. I'm puzzled as to why Viper is looping for you though, did you make sure the md5 was correct?
Sent from my Evita
Related
Hy
After installing ViperOneS, my wifi doesn't work! Please Help!!
I triet to make the OTA Update to 2.2.0 - failed!
thx
Hboot version?
Gonzo23 said:
Hy
After installing ViperOneS, my wifi doesn't work! Please Help!!
I triet to make the OTA Update to 2.2.0 - failed!
thx
Click to expand...
Click to collapse
What Hboot do you have? I believe 1.14 will cause your wifi to break. I haven't been on this forum in awhile, but one option was to downgrade your hboot. It's isn't extremely difficult, but you have to have Ubuntu installed.
Trickdroid wifi worked at one point regardless of hboot, however, I'm not sure if that's the case anymore.
Nick
You need the Wifi Partitions fix which can be found
Bundled with the radios: http://forum.xda-developers.com/showthread.php?t=1998270
or Standalone: http://forum.xda-developers.com/showthread.php?t=2064868&highlight=wifi+partitions
But you will need a low hboot version.
If not, then SuperCID and S-OFF your phone and it will work. I just did my SuperCID and S-OFF last night and it was easy as long as you're comfortable with adb, fastboot, and reading instructions.
tsphan said:
You need the Wifi Partitions fix which can be found
Bundled with the radios: http://forum.xda-developers.com/showthread.php?t=1998270
or Standalone: http://forum.xda-developers.com/showthread.php?t=2064868&highlight=wifi+partitions
But you will need a low hboot version.
If not, then SuperCID and S-OFF your phone and it will work. I just did my SuperCID and S-OFF last night and it was easy as long as you're comfortable with adb, fastboot, and reading instructions.
Click to expand...
Click to collapse
How do I install a wifi partition? Or a radio for that matter?
Can I use fastboot and do something like
fastboot flash partition <filename> ?
Or simply flash the zip from recovery?
I have hboot version 1.08, so I should be safe to do so, right?
Thanks!
With your hboot you should be able to just flash the wifi partitions on recovery.
Sent from my Galaxy Nexus using xda app-developers app
npiper05 said:
but one option was to downgrade your hboot. It's isn't extremely difficult, but you have to have Ubuntu installed.
Click to expand...
Click to collapse
People need to forget about the hboot downgrade...s-off is much safer and easier.
HTC_One_S | S-OFF | Root_Box | Bubba_3.7b_SoftOV
Gonzo23 said:
Hy
After installing ViperOneS, my wifi doesn't work! Please Help!!
I triet to make the OTA Update to 2.2.0 - failed!
thx
Click to expand...
Click to collapse
I had a similar problem yesterday... I found out its a problem with the kernel I had. I later used the Boot.img kernel from Trickdroid (obtain from their website). I fastboot flashed it and voila my Viper Rom worked well with it! Wifi working great
Hey guys, after loads of testing the Trickdroid 10.x I decided migrating to [ROM][S4][JUNE29]V1.8.1 T-Mobile HTC One S JellyBean Stock/Rooted/deodexed/. So, as it was advised over there to update the firmware before flashing the ROM, I downloaded firmware.zip and did exactly as mentioned.
S-OFF
1. fastboot erase cache
2. fastboot oem rebootRUU
3. fastboot flash zip firmware.zip
4. fastboot reboot
Click to expand...
Click to collapse
These are all I did in a step by step process:
1. Updated the firmware (Success) - I could see hboot upgraded from 1.14 to 2.15.
2. Booted into recovery (twrp 2.4.0.0, which had no problems flashing 1.7.1) and flashed 1.8.1 - Caused continuous boot loops, I know I am S-OFF and don't need to flash boot.img.
3. Tried getting my ass on another rom, flashed Viper - Booted but I don't get any network signals + reboot if I unlocked the lockscreen.
4. Thought of trying some aosp/cm ROM, tried LiquidSmooth - Same thing repeats.
Solved signal issue by disabling fast dormancy lol !
vatsaman said:
Hey guys, after loads of testing the Trickdroid 10.x I decided migrating to [ROM][S4][JUNE29]V1.8.1 T-Mobile HTC One S JellyBean Stock/Rooted/deodexed/. So, as it was advised over there to update the firmware before flashing the ROM, I downloaded firmware.zip and did exactly as mentioned.
These are all I did in a step by step process:
1. Updated the firmware (Success) - I could see hboot upgraded from 1.14 to 2.15.
2. Booted into recovery (twrp 2.4.0.0, which had no problems flashing 1.7.1) and flashed 1.8.1 - Caused continuous boot loops, I know I am S-OFF and don't need to flash boot.img.
3. Tried getting my ass on another rom, flashed Viper - Booted but I don't get any network signals + reboot if I unlocked the lockscreen.
4. Thought of trying some aosp/cm ROM, tried LiquidSmooth - Same thing repeats.
Someone please help me!
Click to expand...
Click to collapse
I had this same issue. What I found after hours was that the only solution was to start at the beginning.
I had to return to S-ON (But keep SuperCID)
Lock Bootloader
Flash a Stock RUU w/low Hboot (Keeping SuperCID lets flash any)
After that was completed, I was up and running again, but I still had a signal issue. With the Lower HBoot I was able to re-flash the radio and I was up and running.
From there, I re-unlocked the Bootloader, installed the custom recovery and was able to flash a different ROM again.
I found that it was very dangerous to update to the 2.15 firmware, just caused problems for me. Hopefully that helped.
Also, with the [ROM][S4][JUNE29]V1.8.1 T-Mobile HTC One S JellyBean Stock/Rooted/deodexed/, it is USA based, so unless you are in the US I would just avoid it. I am but I chose Viper just because of the Firmware updates.
mjsheldon4 said:
I had this same issue. What I found after hours was that the only solution was to start at the beginning.
I had to return to S-ON (But keep SuperCID)
Lock Bootloader
Flash a Stock RUU w/low Hboot (Keeping SuperCID lets flash any)
After that was completed, I was up and running again, but I still had a signal issue. With the Lower HBoot I was able to re-flash the radio and I was up and running.
From there, I re-unlocked the Bootloader, installed the custom recovery and was able to flash a different ROM again.
I found that it was very dangerous to update to the 2.15 firmware, just caused problems for me. Hopefully that helped.
Also, with the [ROM][S4][JUNE29]V1.8.1 T-Mobile HTC One S JellyBean Stock/Rooted/deodexed/, it is USA based, so unless you are in the US I would just avoid it. I am but I chose Viper just because of the Firmware updates.
Click to expand...
Click to collapse
Thanks a ton for the help!!
What Hboot does the latest Tmob JB RUU contain ?? And why lower hboot in specific ?
Any particular reason ??
The new ruu updates it 2.15. Lower firmware= lower hboot. The lower hboot means makes it easier to flash radios. Most cannot be flashed higher than 1.13
Sent from my HTC One X using xda premium
Love you bro!! :good::laugh:
My baby is up now.. And I'll stay on stock for quite a few days!! Hufff..
mjsheldon4 said:
The new ruu updates it 2.15. Lower firmware= lower hboot. The lower hboot means makes it easier to flash radios. Most cannot be flashed higher than 1.13
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Can I download the OTA update and apply it on SuperCID ??
Yes. OTA update only requires stock Rom and recovery. CID is not checked.
Sent from my HTC One X using xda premium
mjsheldon4 said:
Yes. OTA update only requires stock Rom and recovery. CID is not checked.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Thanks a lot! But I still have problems regarding signal reception. Any fix ??
That's where the lower HBoot comes into play. You are still able to flash a different radio. In the dev thread is the new 1.15 radio. Works great.
Sent from my Xoom using xda premium
vatsaman said:
Can I download the OTA update and apply it on SuperCID ??
Click to expand...
Click to collapse
Don't do it...this was the common factor for all the bricks after first jb ota
HTC_One_S | S-OFF | Dark_Sense_1.5 | Bulletproof_1.4
Inverted Sense _Click Me
This is very true. The ota update has caused more problems then good.
Sent from my HTC One S using xda premium
Yeah!! Revived to phone back completely to normal! Thanks a ton for your helo folks.
ryanshew said:
Don't do it...this was the common factor for all the bricks after first jb ota
HTC_One_S | S-OFF | Dark_Sense_1.5 | Bulletproof_1.4
Inverted Sense _Click Me
Click to expand...
Click to collapse
Thank god I din't go for it :good: :laugh:
mjsheldon4 said:
This is very true. The ota update has caused more problems then good.
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
I have random signal drops now :crying:
vatsaman said:
I have random signal drops now :crying:
Click to expand...
Click to collapse
why didnt you just updated the official way,
mostly all problems are caused with flashing it manually or flashing only parts,
since there are multiple firmware versions for multiple devices its easy to **** up.
genericly people do it like this-----> flash first---->read/research later.
if your s-off reverting back is easy.
real187 said:
why didnt you just updated the official way,
mostly all problems are caused with flashing it manually or flashing only parts,
since there are multiple firmware versions for multiple devices its easy to **** up.
genericly people do it like this-----> flash first---->read/research later.
if your s-off reverting back is easy.
Click to expand...
Click to collapse
I did the RUU later.. yet to progress
vatsaman said:
I did the RUU later.. yet to progress
Click to expand...
Click to collapse
So you still stuck then?
Verstuurd van mijn One S met Tapatalk
real187 said:
So you still stuck then?
Verstuurd van mijn One S met Tapatalk
Click to expand...
Click to collapse
I'm not stuck. Everything is fine except that random signal loosing thing.
vatsaman said:
I'm not stuck. Everything is fine except that random signal loosing thing.
Click to expand...
Click to collapse
have you tried flashing a original ics ruu, just to check signalproblem.
flashed different radio`s?
real187 said:
have you tried flashing a original ics ruu, just to check signalproblem.
flashed different radio`s?
Click to expand...
Click to collapse
Yes.
Hello.
I have an htc one xl (evita) which will not boot certain roms. I can boot some roms such as miui v5 and magiRom but I can not figure out why it will not boot roms such as CyanogenMod, ChameleonOS or TeamBaked BB9 as examples. These that will not boot will only boot loop and I'm going froot loop.
I am S-off, HBoot 1.09. Using TWRPv2.3.1.0.
I have tried TWRPv2.5, Hboot >1.09 and flashing boot.bin separately.
I have also tried some suggestions from these posts with no success so far ..
http://www.smartphonejam.com/2013/0...-on-HTC-Screen-Logo-Bootloop-after-Flash.html
http://forum.xda-developers.com/showthread.php?t=2159863
Any suggestions on how to boot other roms?
Thanks in advance for your help.
ps. I'm on mac - so if you have any suggestions and tools, please keep the mac in mind.
andason said:
Hello.
I have an htc one xl (evita) which will not boot certain roms. I can boot some roms such as miui v5 and magiRom but I can not figure out why it will not boot roms such as CyanogenMod, ChameleonOS or TeamBaked BB9 as examples. These that will not boot will only boot loop and I'm going froot loop.
I am S-off, HBoot 1.09. Using TWRPv2.3.1.0.
I have tried TWRPv2.5, Hboot >1.09 and flashing boot.bin separately.
I have also tried some suggestions from these posts with no success so far ..
http://www.smartphonejam.com/2013/0...-on-HTC-Screen-Logo-Bootloop-after-Flash.html
http://forum.xda-developers.com/showthread.php?t=2159863
Any suggestions on how to boot other roms?
Thanks in advance for your help.
ps. I'm on mac - so if you have any suggestions and tools, please keep the mac in mind.
Click to expand...
Click to collapse
3.18 ruu.
Sent from my One X using xda premium
jacobas92 said:
3.18 ruu.
Sent from my One X using xda premium
Click to expand...
Click to collapse
man i've looked at a lot of stuff regarding how to get to 3.18 but i keep finding a bunch of conflicting info that my brain is busted. If anyone can reply to some answers with my further info I would appreciate it...
My CID is 11111111
I'm S-off
hboot 1.09
What steps do I need to take to get to 3.18?
I can't seem to find a stock evita recovery image. My understanding is I need to relock boot loader, install stock recovery, upgrade to 3.18 and then restart the process of unlocking. Is this correct? Is the stock recovery located in an original at&t update?
andason said:
man i've looked at a lot of stuff regarding how to get to 3.18 but i keep finding a bunch of conflicting info that my brain is busted. If anyone can reply to some answers with my further info I would appreciate it...
My CID is 11111111
I'm S-off
hboot 1.09
What steps do I need to take to get to 3.18?
I can't seem to find a stock evita recovery image. My understanding is I need to relock boot loader, install stock recovery, upgrade to 3.18 and then restart the process of unlocking. Is this correct? Is the stock recovery located in an original at&t update?
Click to expand...
Click to collapse
As long as you're s-off, just go ahead and run this http://bugsylawson.com/index.php/fi...radio-024p320906-101303234-release-signedexe/ I know you wrote s-off, I'm just being double sure because if you're s-on it'll brick you. S-off you'll be fine. You won't have to relock or anything like that. With s-off you can just do whatever you want :good:
RollTribe said:
As long as you're s-off, just go ahead and run this http://bugsylawson.com/index.php/fi...radio-024p320906-101303234-release-signedexe/ I know you wrote s-off, I'm just being double sure because if you're s-on it'll brick you. S-off you'll be fine. You won't have to relock or anything like that. With s-off you can just do whatever you want :good:
Click to expand...
Click to collapse
Thanks. I'll find me a windows pc tomorrow and go for it. After I flash this in windows, do i then just flash any custom rom I want to go to which has the 3.4 kernel and will I be limited only to those now?
andason said:
Thanks. I'll find me a windows pc tomorrow and go for it. After I flash this in windows, do i then just flash any custom rom I want to go to which has the 3.4 kernel and will I be limited only to those now?
Click to expand...
Click to collapse
Yeah any 3.4 ROM, but you can also use non-3.4 if you so choose.
RollTribe said:
Yeah any 3.4 ROM, but you can also use non-3.4 if you so choose.
Click to expand...
Click to collapse
Thanks again. Much easier then what I thought I was understanding in my reads. I did see other people mention that as long as you were s off then everything else just about doesn't matter and then other contradicting that. Got to the point that I thought it made be easier to start all over in combination I was trying to install wine and it failed after about 45 minutes of downloading.
arrrggh.
andason said:
Thanks again. Much easier then what I thought I was understanding in my reads. I did see other people mention that as long as you were s off then everything else just about doesn't matter and then other contradicting that. Got to the point that I thought it made be easier to start all over in combination I was trying to install wine and it failed after about 45 minutes of downloading.
arrrggh.
Click to expand...
Click to collapse
Yeah, man, Wine doesn't work, I tried back when I used Mac for my Android needs. Everything is SO much easier with a windows PC
after flashing the 3.18 ruu, i can still flash any custom roms i want? aosp, sense base. what about ics version roms?
claudiuslu2011 said:
after flashing the 3.18 ruu, i can still flash any custom roms i want? aosp, sense base. what about ics version roms?
Click to expand...
Click to collapse
Yup all Roms
is there any advantage on the 3.18ruu?
Yeah, you need it to run AOSP 3.4 kernel roms
andason said:
Thanks again. Much easier then what I thought I was understanding in my reads. I did see other people mention that as long as you were s off then everything else just about doesn't matter and then other contradicting that. Got to the point that I thought it made be easier to start all over in combination I was trying to install wine and it failed after about 45 minutes of downloading.
arrrggh.
Click to expand...
Click to collapse
Thanks. Everything seems to work fine now.
A couple of things to note for others who make look at this thread - After flashing the rom in your link: http://bugsylawson.com/index.php/fi...radio-024p320906-101303234-release-signedexe/
1. Hboot will be at 2.14 - So if you wish, downgrade back to 1.09, otherwise you will need to flash the boot.img and then the rom when trying new roms.
2. The after market recovery (will now be oem recovery) will be gone so be sure to reinstall your preferred recovery (TWRP or CW)
3. The touchscreen may not respond in some roms, so you may have to downgrade your touchscreen panels firmware http://forum.xda-developers.com/showthread.php?t=2159863
exad said:
You only need to downgrade touchscreen firmware if:
You're on 2.14 hboot + You are flashing an AOSP ROM not yet on 3.4 Kernel.
Click to expand...
Click to collapse
Thanks again for the help.
andason said:
Thanks. Everything seems to work fine now.
A couple of things to note for others who make look at this thread - After flashing the rom in your link:
1. Hboot will be at 2.14 - So if you wish, downgrade back to 1.09, otherwise you will need to flash the boot.img and then the rom when trying new roms.
2. The after market recovery (will now be oem recovery) will be gone so be sure to reinstall your preferred recovery (TWRP or CW)
3. The touchscreen may not respond in some roms, so you may have to downgrade your touchscreen panels firmware http://forum.xda-developers.com/showthread.php?t=2159863
Thanks again for the help.
Click to expand...
Click to collapse
You actually don't need to downgrade your hboot, if you're s-off you don't need to manually flash boot.img no matter what your hboot version is.
Sent from my Evita
odd that rom would not boot with 2.14..but with 1.09 no problems?
andason said:
odd that rom would not boot with 2.14..but with 1.09 no problems?
Click to expand...
Click to collapse
There was probably some other factor causing the issue. I boot all roms with 2.14 no problem.
andason said:
odd that rom would not boot with 2.14..but with 1.09 no problems?
Click to expand...
Click to collapse
Which ROM? After s-off?
Sent from my Evita
timmaaa said:
You actually don't need to downgrade your hboot, if you're s-off you don't need to manually flash boot.img no matter what your hboot version is.
Sent from my Evita
Click to expand...
Click to collapse
do i need to downgrade my touch firmware?
claudiuslu2011 said:
do i need to downgrade my touch firmware?
Click to expand...
Click to collapse
You only need to downgrade touchscreen firmware if:
You're on 2.14 hboot + You are flashing an AOSP ROM not yet on 3.4 Kernel.
timmaaa said:
Which ROM? After s-off?
Sent from my Evita
Click to expand...
Click to collapse
It may be I am mistaken. I thought it was baked but i was also trying a rom I was trying to port. During the time i was flashing from 1.09 to 2.14 and also seen that baked required 2.14. So with all that going on i was just trying boot.img and then the rom to ensure no errors.
*** WHAT MY PROBLEM IS***
PLEASE can someone confirm any AOSP ROM that works with 2.15 HBOOT?
***WHAT I KNOW***
( i know the CM 10.2 thread says that RUU 3.18 which will make the hboot 2.14 but since 2.15 is latest i assume it should support)
(i also know that [HBOOT 2.15 is essential for SENSE 5 4.2.2 to run,i believe that's the only reason people go for 2.15)
***WHAT I HAVE TRIED***
NOW from what i have tried is that the 1st stable cm 10 release doesn't work with 2.15 (obviously too old build) my screen also became responsive(i believe that because of touch panel firmware) then with the latest stable release of cm 10.1 it specified that it needs hboot 2.14 and hence couldn't flash.
with PAC 4.3 it does gets installed but screen is unresponsive and infinite bootloops!:silly:
***WILL THIS WORK***
so now if i RUU 3.18 i will have to unlock boot loader and root it (M SOFF SUPER CID) which i m not really ready to do!
now there are methods that can help u downgrade/upgrade your firmware , can i do that?
also will using torched kernel help in me in any way?
***WHY DO I WANT AOSP***
Viper XL 4.2.2 best ROM ever hats off but the thing is i dont know why but i have Signal issues i tried flashing the recommended RADIO version.
since the vendor had already RUUd my device that was meant from some ASIAN region and already came with SENSE 5 and i dint mess up with it in any way still i had signal issues (which are unpredictable) i found by GSAM BATTERY monitor that around 30 to 40% of my battery is consumed by RADIO.
also the best signal is around -81db
i also had some issues with camera!
and then there is the numerous options i can have with AOSP.
****LASTLY CAN ANYONE HELP****
:angel:
Just RUU. Your bootloader will remain unlocked and your S-OFF will remain
After the RUU you can flash recovery and flash a rom. You can technically just flash the 2.14 firmware.zip by extracting it from an OTA or an RUU, but easier to just ruu. and you get a nice clean wipe too.
I misread the m soff part sorry. You could have just run the ruu and twrp and been done in the time it took you to write that post.
Sent from my HTC One XL
954wrecker said:
He makes it hard to understand but he is S-ON so he is screwed at this point
Sent from my HTC One XL
Click to expand...
Click to collapse
no no no i am SOFF i know for sure!!!
exad said:
Just RUU. Your bootloader will remain unlocked and your S-OFF will remain
After the RUU you can flash recovery and flash a rom. You can technically just flash the 2.14 firmware.zip by extracting it from an OTA or an RUU, but easier to just ruu. and you get a nice clean wipe too.
Click to expand...
Click to collapse
jus for the sake for reassurance:
after RUU:
will Bootloader remain Unlocked?
will it still be SOFF?
and SUPERCID?
so these things will survive the RUU?
954wrecker said:
I misread the m soff part sorry. You could have just run the ruu and twrp and been done in the time it took you to write that post.
Sent from my HTC One XL
Click to expand...
Click to collapse
LOL u are right thanks!
its just that m kinda paranoid cause every day in the Help and Troubleshooting section there is some thread dats says BRICKED so always to be on the safer side!
Sonone said:
jus for the sake for reassurance:
after RUU:
will Bootloader remain Unlocked?
will it still be SOFF?
and SUPERCID?
so these things will survive the RUU?
Click to expand...
Click to collapse
yes
exad said:
yes
Click to expand...
Click to collapse
thanks a lot EXAD!!!:good::good:
btw earlier you mentione its possible to extract the firmware file?
how can it be done?
Sonone said:
thanks a lot EXAD!!!:good::good:
btw earlier you mentione its possible to extract the firmware file?
how can it be done?
Click to expand...
Click to collapse
the easiest way is to extract firmware.zip from a 3.17/3.18 ota file for your carrier.
exad said:
the easiest way is to extract firmware.zip from a 3.17/3.18 ota file for your carrier.
Click to expand...
Click to collapse
I wouldn't mess with extracting the firmware files from the OTAs manually. If one of the hboot modules is missing, a brick can result. The OP is probably OK, since he has already manually updated to hboot 2.15. But RUU is still seems the safest way.
redpoint73 said:
I wouldn't mess with extracting the firmware files from the OTAs manually. If one of the hboot modules is missing, a brick can result. The OP is probably OK, since he has already manually updated to hboot 2.15. But RUU is still seems the safest way.
Click to expand...
Click to collapse
as always thank you...
since u recoomend thats the safest way i will try out that.
have to download the RUU 3.18!!!
*waiting*
Hello I have supercid, s-off and previously flashed MAXIMUSHD ROM and that's on hboot 2.16 so I got board and sick of sense 5 and I want to try out one of the kitkat ROMs but I need hboot 2.15 for that and yes I know that there are hboot 2.16 kitkat roms but they are unstable so can someone tell me step by step how to downgrade hboot 2.16 to 2.15 because I'm quite of a dumb person
the_ziom said:
Hello I have supercid, s-off and previously flashed MAXIMUSHD ROM and that's on hboot 2.16 so I got board and sick of sense 5 and I want to try out one of the kitkat ROMs but I need hboot 2.15 for that and yes I know that there are hboot 2.16 kitkat roms but they are unstable so can someone tell me step by step how to downgrade hboot 2.16 to 2.15 because I'm quite of a dumb person
Click to expand...
Click to collapse
This is how I proceed :
1) Downgrade to 2.15 hboot by flashing the old firmware (extract firmware.zip and flash as you did for MaximusHD)
2) Run the latest RUU to get everything clean (I flashed this one)
3) Flash custom recovery with fastboot (TWRP 2.3.X.X)
4) You're done !
benJX said:
This is how I proceed :
1) Downgrade to 2.15 hboot by flashing the old firmware (extract firmware.zip and flash as you did for MaximusHD)
2) Run the latest RUU to get everything clean (I flashed this one)
3) Flash custom recovery with fastboot (TWRP 2.3.X.X)
4) You're done !
Click to expand...
Click to collapse
thank you but i have super cid and from what i have read i have to install the ruu according to my cid
tell me if im right
the_ziom said:
thank you but i have super cid and from what i have read i have to install the ruu according to my cid
tell me if im right
Click to expand...
Click to collapse
In fact, the CID matters if you have one from an operator (have a look here, but not the last one, it's the superCID), in this case, you have to choose a RUU according to your operator.
But being superCID, you can run any RUU, so run the last generic one (see my link) and everything will be ok to start from official clean install. Of course you'll stay S-OFF after running the RUU.
The only thing requested is to be on 2.15 hboot, that's why you have to downgrade to older firmware in order to run this.
Hope it will help.
I have kind of a similar question. After moonshine S-OFF, I'm on modified moonshine HBOOT 2.15.4444. Now I want to go back to the stock HBOOT 2.15.0000. Do I just need to run the RUU to go back? I'm bootloader unlocked, CID T-MOB010, TWRP recovery, and I flashed radio 1.20. Do I need to flash radio back to match the RUU before I run it?
Thanks
dr3amsINdigital said:
I have kind of a similar question. After moonshine S-OFF, I'm on modified moonshine HBOOT 2.15.4444. Now I want to go back to the stock HBOOT 2.15.0000. Do I just need to run the RUU to go back? I'm bootloader unlocked, CID T-MOB010, TWRP recovery, and I flashed radio 1.20. Do I need to flash radio back to match the RUU before I run it?
Thanks
Click to expand...
Click to collapse
Running an RUU is the safest option, although its a bit hit and miss getting the RUU to run correctly. Flashalot recently made a guide (http://forum.xda-developers.com/showthread.php?t=2678700) if you run into any problems. I would try it without changing the radio, if it doesn't work then flash the matching one and go from there.
Now I cannot recommend this, as I have only tried it once myself and the consequences if it went wrong could mean a dead phone, but this post (http://forum.xda-developers.com/showpost.php?p=39216236&postcount=274) details how you can manually flash a hboot version in RUU mode since you are S-OFF. It comes from this thread: http://forum.xda-developers.com/showthread.php?t=1777223. Use it at your own risk, there have been two incidents of bricks but it depends how lucky you are feeling!
rosswhite said:
Running an RUU is the safest option, although its a bit hit and miss getting the RUU to run correctly. Flashalot recently made a guide (http://forum.xda-developers.com/showthread.php?t=2678700) if you run into any problems. I would try it without changing the radio, if it doesn't work then flash the matching one and go from there.
Now I cannot recommend this, as I have only tried it once myself and the consequences if it went wrong could mean a dead phone, but this post (http://forum.xda-developers.com/showpost.php?p=39216236&postcount=274) details how you can manually flash a hboot version in RUU mode since you are S-OFF. It comes from this thread: http://forum.xda-developers.com/showthread.php?t=1777223. Use it at your own risk, there have been two incidents of bricks but it depends how lucky you are feeling!
Click to expand...
Click to collapse
Yeah I heard about that method, but I thought it would be safer to just run the RUU even though it's more work. I think the bricks were from flashing the zips in recovery, not the new ones you flash in fastboot. Either way, I didn't feel like risking it.
Thanks! I'll try the RUU.
dr3amsINdigital said:
Yeah I heard about that method, but I thought it would be safer to just run the RUU even though it's more work. I think the bricks were from flashing the zips in recovery, not the new ones you flash in fastboot. Either way, I didn't feel like risking it.
Thanks! I'll try the RUU.
Click to expand...
Click to collapse
Wise choice, yeah you are right, the bricks were when they were flashing the zips in recovery. Its actually pretty safe in RUU mode but what's the point of risking it.
benJX said:
In fact, the CID matters if you have one from an operator (have a look here, but not the last one, it's the superCID), in this case, you have to choose a RUU according to your operator.
But being superCID, you can run any RUU, so run the last generic one (see my link) and everything will be ok to start from official clean install. Of course you'll stay S-OFF after running the RUU.
The only thing requested is to be on 2.15 hboot, that's why you have to downgrade to older firmware in order to run this.
Hope it will help.
Click to expand...
Click to collapse
dr3amsINdigital said:
I have kind of a similar question. After moonshine S-OFF, I'm on modified moonshine HBOOT 2.15.4444. Now I want to go back to the stock HBOOT 2.15.0000. Do I just need to run the RUU to go back? I'm bootloader unlocked, CID T-MOB010, TWRP recovery, and I flashed radio 1.20. Do I need to flash radio back to match the RUU before I run it?
Thanks
Click to expand...
Click to collapse
rosswhite said:
Running an RUU is the safest option, although its a bit hit and miss getting the RUU to run correctly. Flashalot recently made a guide (http://forum.xda-developers.com/showthread.php?t=2678700) if you run into any problems. I would try it without changing the radio, if it doesn't work then flash the matching one and go from there.
Now I cannot recommend this, as I have only tried it once myself and the consequences if it went wrong could mean a dead phone, but this post (http://forum.xda-developers.com/showpost.php?p=39216236&postcount=274) details how you can manually flash a hboot version in RUU mode since you are S-OFF. It comes from this thread: http://forum.xda-developers.com/showthread.php?t=1777223. Use it at your own risk, there have been two incidents of bricks but it depends how lucky you are feeling!
Click to expand...
Click to collapse
HELP my device does not see any memory and i cant flash any rom hellpp
the_ziom said:
HELP my device does not see any memory and i cant flash any rom hellpp
Click to expand...
Click to collapse
What hboot are you on now? Did you run an RUU to downgrade?
rosswhite said:
What hboot are you on now? Did you run an RUU to downgrade?
Click to expand...
Click to collapse
Hboot 2.15 after running the |RUU.exe|
dont have the memory (does not see device when trying to side load , recovery cant mount sdcard)
help i need my phone
the_ziom said:
Hboot 2.15 after running the |RUU.exe|
dont have the memory (does not see device when trying to side load , recovery cant mount sdcard)
help i need my phone
Click to expand...
Click to collapse
Which recovery did you flash? Try TWRP 2.7.0.0.
the_ziom said:
Hboot 2.15 after running the |RUU.exe|
dont have the memory (does not see device when trying to side load , recovery cant mount sdcard)
help i need my phone
Click to expand...
Click to collapse
Can you boot on stock android rom installed by the ruu ?
rosswhite said:
Which recovery did you flash? Try TWRP 2.7.0.0.
Click to expand...
Click to collapse
i already have twrp 2.7 and i flashed phillz and still nothing
benJX said:
Can you boot on stock android rom installed by the ruu ?
Click to expand...
Click to collapse
yes but i formated my memory to instal a pac man rom
the_ziom said:
yes but i formated my memory to instal a pac man rom
Click to expand...
Click to collapse
So actually you can confirm you are on HBOOT 2.15, Pihllz recovery and no rom installed ?
If yes reboot to bootloader, select clear storage, flash this recovery. Your sdcard should be mountable and let you install your rom.
####
benJX said:
So actually you can confirm you are on HBOOT 2.15, Pihllz recovery and no rom installed ?
If yes reboot to bootloader, select clear storage, flash this recovery. Your sdcard should be mountable and let you install your rom.
Click to expand...
Click to collapse
Another Problem
when ever i try to flash any rom it fails! and i dont know what to do HElp
So many developers and only 2 can help me
Please I'm begging for help
the_ziom said:
Another Problem
when ever i try to flash any rom it fails! and i dont know what to do HElp
Click to expand...
Click to collapse
Flash stock recovery : http://loadbalancing.modaco.com/download.php?file=ville_recovery_signed.img
Then Clear Storage from bootloader and flash TWRP recovery