These days, as I'm more onto porting,development and testing of ROMs, just wanna be sure with the possibilities for a BRICK. Plz help me out guys!!
Just don't mess around with low-level stuff like partitions, hboot, radio and stuff like that. Also, porting a ROM incorrectly could mess up your main board if the device that you are porting from has much higher/lower CPU/GPU frequencies than this device.
vatsaman said:
just wanna be sure with the possibilities for a BRICK.
Click to expand...
Click to collapse
Ways to brick that I know of:
* Turning S-On after you flashed a modified hboot, or flashing an modified hboot while S-On (which you can actually do on 1.06 and 1.09. don't.)
* Taking certain recent OTAs while on SuperCID (you need it to gain S-Off but I suggest to change to HTC__001 afterwards.)
There have been reports of devices in qhsusbdload mode after completely draining the battery. But not for a while I think.
usaff22 said:
Just don't mess around with low-level stuff like partitions, hboot, radio and stuff like that. Also, porting a ROM incorrectly could mess up your main board if the device that you are porting from has much higher/lower CPU/GPU frequencies than this device.
Click to expand...
Click to collapse
Thanks a lot for the info. Another clarification.. Are the files related to hboot, radio and partitions are included in the ROM zips ?? If yeah please name the folder, so that I'll get my hands cleaned up while working with them :victory:
vatsaman said:
Thanks a lot for the info. Another clarification.. Are the files related to hboot, radio and partitions are included in the ROM zips ?? If yeah please name the folder, so that I'll get my hands cleaned up while working with them :victory:
Click to expand...
Click to collapse
No, they are in firmware.zip, not in the rom.zip itself.
usaff22 said:
No, they are in firmware.zip, not in the rom.zip itself.
Click to expand...
Click to collapse
So we won't be dealing with firmware.zip while porting the ROM ??
vatsaman said:
So we won't be dealing with firmware.zip while porting the ROM ??
Click to expand...
Click to collapse
Nope
HTC_One_S | S-OFF | ViperOneS_2.2.0 | Black&Blue_Inverted_Sense | Bulletproof_1.4
Inverted Sense _4+_and_5_click me
Related
Ok guys too many people having issues with new rom sense 4 not booting up...
So here is a renegineered hboot 2.00.002...
After this all roms including all sense4 versions and even russian roms will work with no issues...
Old roms will continue to work as well with no problems
This should be used only by people having hboot starting with 6.98...
People with hboot 2.00.002 don't need this...
People with hboot starting with 0.98 can either flash 2.00.002 or this hboot...
Steps :
1. Download attachment and copy to root of sd card (i.e not inside any folder)
2. Reboot into bootloader
3. Select bootloader
4. The attachment will be auto detected and updated within 5-7 sec max.
5. Now go to recovery again select format all partitions except sd card if you dont want to flash a new rom else wipe cache and dalvik cache if you wnat to just update hboot and continue with old rom (Remember next time you flash a new rom select format all partitions except sd card from recovery).
* Formatting all partitions except sd card from recovery is recommended after hboot upgrade !
6. Don't forget to delete the attachment from the sd card.
7. Done
Tested well and works perfect !
Also fastboot commands work except for the 1 to change id...everything else works as it should and you can always revert back with no issues
HBoot Download
md5 : d44d182207a69c16f5272604c00665e6
Why don't you post how to revert to old hboot and S-on (in case is needed)...that will be a usefull post
I'll do it now One question - does this give you Eng S-OFF too??
Edit: vampire36, just noticed something - we both joined xda on the same day Not that it means anything at all, just an interesting detail.
Sent from a device waiting for the Kernel 3 source code. WAKE UP HTC !!!!!
shrome99 said:
I'll do it now One question - does this give you Eng S-OFF too??
Edit: vampire36, just noticed something - we both joined xda on the same day Not that it means anything at all, just an interesting detail.
Sent from a device waiting for the Kernel 3 source code. WAKE UP HTC !!!!!
Click to expand...
Click to collapse
Ohhh thats cool and interesting
S-off well it keeps the state as it..so if its S-off remains S-off...
.sh4d0w. said:
Why don't you post how to revert to old hboot and S-on (in case is needed)...that will be a usefull post
Click to expand...
Click to collapse
Okies will look into it...and will need to test the method before posting
But will do something about it
Could you please explain what the issues and differences are?
Is this to do with system.lib?
Thanks in advance
Swyped from my DesireS
Well, i tried to flash the full Sense 4 port for 3 hours yesterday, but it always led to a black screen, since the system partition got filled up and the updater-script was trying to mount the lib partition, which wasn't there. This fixes these errors by adding a lib partition. It will be a problem in all future ROMs, so I'm flashing this now....
And what will be the advantage of this over the 2.00.2002 one? Besides the flashing procedure which was by adv for the eng 2.0.2002
Sent from my HTC Desire S
I will try it.
Does it can be helpful with Google Maps compass?
My Google Maps compass didn't work on all Android4.0 roms....;'(
I tried this Hboot, but i ran into troubles.
First of all the phone rings before it goes into the bootloader... never happend.
When i start the rom, the same.
The cam is also broken. The cam pic looks wierd...
Maybe I done something wrong?
Edit:
Now I went back to this one:
PG88IMG-OLD-RADIO-20.28b.30.0805U_38.03.02.11
Everything works fine again.
ben_pyett said:
Could you please explain what the issues and differences are?
Is this to do with system.lib?
Thanks in advance
Swyped from my DesireS
Click to expand...
Click to collapse
shrome99 said:
Well, i tried to flash the full Sense 4 port for 3 hours yesterday, but it always led to a black screen, since the system partition got filled up and the updater-script was trying to mount the lib partition, which wasn't there. This fixes these errors by adding a lib partition. It will be a problem in all future ROMs, so I'm flashing this now....
Click to expand...
Click to collapse
I guess shrome answered it...though we can always change the updater script but it will be a pain to do each time...So this way you don't have to worry about it...partition is added and ics roms i guess will go this way...
datoml said:
I tried this Hboot, but i ran into troubles.
First of all the phone rings before it goes into the bootloader... never happend.
When i start the rom, the same.
The cam is also broken. The cam pic looks wierd...
Maybe I done something wrong?
Click to expand...
Click to collapse
These are rom issues due to new partition and nothing to do with hboot...you can just do a clean install of the rom...and then check
As i have said do foramt all partition except sd card and then flash the rom...all will be well
Is this an updated of the eng 2.00.2002?
Or it s older
vampire36 said:
These are rom issues due to new partition and nothing to do with hboot...you can just do a clean install of the rom...and then check
As i have said do foramt all partition except sd card and then flash the rom...all will be well
Click to expand...
Click to collapse
I went no back to this hboot:
PG88IMG-OLD-RADIO-20.28b.30.0805U_38.03.02.11
Everything works well again.
Before I clean my phone again, what will be the benefits with this new hboot?
if people remove the lines in updater-script to flash files to /system/lib partiton, and remove in the boot.img > init.rc the lines to mount lib partition there's actually no need to upgrade your HBOOT. you'll even ruin your camera pictures... Lol i really need to downgrade my hboot but cant really find a good tutorial
if you flash SenseMOD FlashONE and use the F1 kernel located on our website, you wont have any problems with older HBOOTs
djpbx said:
if people remove the lines in updater-script to flash files to /system/lib partiton, and remove in the boot.img > init.rc the lines to mount lib partition there's actually no need to upgrade your HBOOT. you'll even ruin your camera pictures... Lol i really need to downgrade my hboot but cant really find a good tutorial
if you flash SenseMOD FlashONE and use the F1 kernel located on our website, you wont have any problems with older HBOOTs
Click to expand...
Click to collapse
Well i guess there are many who still don't know porting stuff and other details...so that will be a pain for them...
About camera pictures...you need to do a clean install after flashing hboot...so that all libs are now at same place...no issues
datoml said:
I went no back to this hboot:
PG88IMG-OLD-RADIO-20.28b.30.0805U_38.03.02.11
Everything works well again.
Before I clean my phone again, what will be the benefits with this new hboot?
Click to expand...
Click to collapse
Your confusing thats the older radio not hboot...
hboot and radio are different...radio that you flashed will have affect on the network...not camera pictures
hboot affect the system partition schema
Check your hboot version by rebooting into recovery...if the zip has no parts of hboot...it will still be v7
kylon said:
Is this an updated of the eng 2.00.2002?
Or it s older
Click to expand...
Click to collapse
Its same...just modified and reengineered as they say
I have revolutionary hboot. Can I install this ENG 2.00.002 hboot?
Also 2.00.2002 is eng.
I would like to know if this in an updated version
Are there any differences?
It seems like a lot of the issues that come up deal with the hboot is there a way to flash a hboot after its modified? Of completely format a phone and have it rebuild from a older image/RUU?
leighton1245 said:
It seems like a lot of the issues that come up deal with the hboot is there a way to flash a hboot after its modified? Of completely format a phone and have it rebuild from a older image/RUU?
Click to expand...
Click to collapse
no
absolutelygrim said:
no
Click to expand...
Click to collapse
If you read in the s-off dev thread it can be done i was just looking for info on how it was done? sorry i put question up incorrectly.
We need s-off to do this. We don't have s- off
gunnyman said:
We need s-off to do this. We don't have s- off
Click to expand...
Click to collapse
Ahh i see thank you
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*
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