Related
Hi,
I had a few questions about kernels...hope someone can help me in answering these...
I am thinking of trying out the Netarchy kernel on my Nexus S, but i was just wondering is there anywhere I can download the stock kernel (so that if anything does go wrong i dont have to do a full nandroid restore?)
Also, when installing a new kernel does that wipe data (of course I will make a backup etc before installing it, but should all my settings and apps etc remain intact normally?)
what impact does an OTA update have if i am running a non stock kernel? so say i am using Netarchy's kernel, and google releases a new OTA update...will i still be able to install the update? If i do, will it revert to stock kernel?
Thanks in advance,
brownmonkey said:
Hi,
I had a few questions about kernels...hope someone can help me in answering these...
I am thinking of trying out the Netarchy kernel on my Nexus S, but i was just wondering is there anywhere I can download the stock kernel (so that if anything does go wrong i dont have to do a full nandroid restore?)
Also, when installing a new kernel does that wipe data (of course I will make a backup etc before installing it, but should all my settings and apps etc remain intact normally?)
what impact does an OTA update have if i am running a non stock kernel? so say i am using Netarchy's kernel, and google releases a new OTA update...will i still be able to install the update? If i do, will it revert to stock kernel?
Thanks in advance,
Click to expand...
Click to collapse
I'm not aware of anywhere that the stock kernel is available for download so doing a NANDroid backup is really your best option. If you have anything that deviates from stock (kernel, rom, theme, even just deleted stock apps) it will prevent you from being able to successfully update from an OTA.
You can find a lot of information about all the available kernels here just scroll down to the third post and you'll find the info.
Finally, just as a note of personal opinion, getting OTA updates is a little overrated. If you run a custom ROM, the OTAs will be included in those ROMs eventually so you won't have to worry about restoring a stock ROM just to get the updates.
kenvan19 said:
I'm not aware of anywhere that the stock kernel is available for download so doing a NANDroid backup is really your best option. If you have anything that deviates from stock (kernel, rom, theme, even just deleted stock apps) it will prevent you from being able to successfully update from an OTA.
You can find a lot of information about all the available kernels here just scroll down to the third post and you'll find the info.
Finally, just as a note of personal opinion, getting OTA updates is a little overrated. If you run a custom ROM, the OTAs will be included in those ROMs eventually so you won't have to worry about restoring a stock ROM just to get the updates.
Click to expand...
Click to collapse
Thanks for the quick answer. I had read that post before (it was actually how i came to discover kernels ). The reason why I was asking about the OTA is because I actually use the stock ROM but was just thinking about trying out the Netarchy kernel just to see what its all about. Hence if there is an OTA update, and i am running a different kernel to the stock, is the only way for me to incorporate the update by flashing the new stock rom and then reinstall the netarchy kernel?
Also, if i install it, do you know if it wipes data/apps?
Thanks
brownmonkey said:
Thanks for the quick answer. I had read that post before (it was actually how i came to discover kernels ). The reason why I was asking about the OTA is because I actually use the stock ROM but was just thinking about trying out the Netarchy kernel just to see what its all about. Hence if there is an OTA update, and i am running a different kernel to the stock, is the only way for me to incorporate the update by flashing the new stock rom and then reinstall the netarchy kernel?
Also, if i install it, do you know if it wipes data/apps?
Thanks
Click to expand...
Click to collapse
I apologize as I forgot to mention that part of your question, I'm sick with the flu and a little out of it on some cold medications lol. You only lose data and apps when flashing if you wipe the /data partition in mounts and storage and this is not required nor is it recommended when flashing a kernel. Sorry for answering out of order, but I thought I should clear that up first. As to the other question, you have it correct; you would need to flash the new update ROM and then flashing a new kernel.
I should also note that whenever you install a new ROM, you will need to reflash a custom kernel. This is because the vast majority of ROMs released include a kernel and when you flash them it will overwrite whatever kernel you currently have.
Finally, if you have any other questions you can always feel free to post them on that thread. I'm the one who wrote it and I check it often to try and answer questions as best and as quickly as I can. Happy flashing!
Are you using a custom ROM? Flashing CM7 has the stock kernel. There are probably other ones out there that includes stock kernel with them such as OTA.
Hi,
I have a rooted sensation and would like to install the latest Revolution HD 3.6.3 XE rom.
I have installed roms to my Desire before no problems but when you go to the Revolution download page there are links for downloading Radios and performing checksums. This is something that I have never done before.
Can anyone tell me whether the 3.6.3 rom download is a one operation install or do I have to install other files like the radio?
If so is there an idiot proof guide to installing? I have trawlled through the Revolution post but it is 1000's of pages!
I tried to post this question on the Revolution post but I am unable to as it is reserved for experienced users only.
Any help would be appreciated.
Thanks
Dave
Concerning the cecksums:
You can verify them for example with DownThemAll, which is a Firefox downloadhelper addon.
Concerning flashing ROMs:
If you have a rooted sensation, I assume, you have done it with the revolutionary tool?
Well, if so, you should have installed the ClockWorkMod, with is a mod for the recovery menu (power off the phone - power on while pressing volume down - select recovery).
To install a ROM simply put it on the SD card. It can then be installed with CWM by performing 'install from sd'. That's it.
Two other things... sometimes the ROMs require you to perform a fullwipe. Make sure you do this before installing the ROM. Also always make sure, that you have a backup if things go wrong!
Also have a read at http://forum.xda-developers.com/showthread.php?t=1200403!
whittall1 said:
Hi,
I have a rooted sensation and would like to install the latest Revolution HD 3.6.3 XE rom.
I have installed roms to my Desire before no problems but when you go to the Revolution download page there are links for downloading Radios and performing checksums. This is something that I have never done before.
Can anyone tell me whether the 3.6.3 rom download is a one operation install or do I have to install other files like the radio?
If so is there an idiot proof guide to installing? I have trawlled through the Revolution post but it is 1000's of pages!
I tried to post this question on the Revolution post but I am unable to as it is reserved for experienced users only.
Any help would be appreciated.
Thanks
Dave
Click to expand...
Click to collapse
Generally the Radio is separate from the ROM. Check your Radion and make sure it's up to the level the ROM needs.
Radios: http://forum.xda-developers.com/showthread.php?t=1178143
Checksum is just a way of confirming what you downloaded is 100% valid. You can get MD5 checkers for Windoz and Android.
From what I remember, it's a:
CWM Nandroid (Always do this);
Update Radio (IF required);
Use the Superwipe Script (run it from CWM), it just cleans it all up;
Install the ROM via CWM;
Boot and enjoy.
There are other scripts out there to backup downloaded apps then re-install. You can also to lighten the Sense ROMs, e.g. the following is referenced in the ARHD page: http://forum.xda-developers.com/showthread.php?t=1217664 There are instructions in the Sense cleaner page for the right sequence.
JUST MAKE SURE you do a nandroid backup before you start anything.
Thanks,
When you say check the radio and make sure its up to the level, presumably the radio is never wiped regardless of how many different roms you try.
Does this explain why there is a recommended radio?
Dave
Thanks,
When you say check the radio and make sure its up to the level, presumably the radio is never wiped regardless of how many different roms you try.
Does this explain why there is a recommended radio?
Dave
I believe that's the case for Custom ROMs, i.e. ROM and Radio are two separate entities. If you flash the RUU completely (the .exe) it applies an RUU specific radio. If you just keep re-flashing Custom ROMs they just use the currently installed radio.
There are a few ways to install the radio, again I believe most people recommend using fastboot, the PG58IMG.zip way is a different way and both have worked fine for me.
All the Custom ROMs should reference their "recommended" radio in the ROM thread. Usually the latest or a very recent one. Some of the RUUs if they are old will have applied a much, much older radio.
Just for ref. what is your radio ?
Hi again,
OK ive flashed a new Revolution Rom.
Ive a few queries does anyone know where I can post questions because I can't post the direct to the Revolution post.
As for my radio I think its:-
10.56.9035.00U_10.14.9035.01_M
Yes: 10.56.9035.00U_10.14.9035.01 is almost the most recent. It's recommended one for CM7, the more recent one from ARHD seems to be :
http://forum.xda-developers.com/showthread.php?t=1098849
To quote from there:
With 3.6.x ROMs I strongly recommend flashing 10.58.9035.00U_10.15.9035.02_2 radio.
I'm still a bit stumped by what queries you actually have.
Ok, I've run a couple of benchmarks and it comes back with a 1.18 mhz speed rating.
Also the ROM appears to be the latest one to rownliad but the version number is less than the one listed on the ROM page.
The latest one is supposed to be 3.6.3 xe but the one I've downloaded and installed is just 3.6.3.
One more thing, I would like to remove some of the stick apps such as teeter, news etc to free up some RAM. How do I do this?
You can use any of the file explorer programs to remove unwanted apps. You just have to go into the settings to check root access granted. Alson, 3.6.3 is the xe version (it installs Beats Audio) I believe 4.1.3 is the non-xe variant of ARHD.
whittall1 said:
Ok, I've run a couple of benchmarks and it comes back with a 1.18 mhz speed rating.
Also the ROM appears to be the latest one to rownliad but the version number is less than the one listed on the ROM page.
The latest one is supposed to be 3.6.3 xe but the one I've downloaded and installed is just 3.6.3.
One more thing, I would like to remove some of the stick apps such as teeter, news etc to free up some RAM. How do I do this?
Click to expand...
Click to collapse
Hi,
The CPU speed can be adjusted with the Daemon Controller.Have a look on the [OP] for a good article to explain it.HERE
There are currently 2 ARHD ROMS available.
3.6.3 which uses Sense 3.0
and 4.1.4 which uses Sense 3.5
If you want to trim down your ROMS,read up on the ROM CLEANER
It can remove all the bloatware and anything else you want,before the ROM first boots up.
Hi,
I just sent my One S to Vodafone because of the chipping issue (it wasn't very much but if they change it it would be nice) and I expect to get a new flashed phone back from them.
At the moment I have (or more had) the Virtuos 1.4.0 Rom installed because I kinda like the Sense look&feel more than the AOSP way but I wanted to have the 3-dot menu mod.
As the Mod is now available for odexed 1.78 ROMs and the Virtuos ROM isn't updated I'm thinking about keeping the stock ROM, clean it in parts with the ROM Cleaner and then apply the Mod (and maybe some other also) to still get OTA Updates.
My Question now is: What does the phone need to get the OTA Updates?
Somewhere I read that it would need the default recovery, is this true? and what else does it need? I want to have CWM to make nandroids etc. - would it be necessary to unlock the bootloader, flash CWM and reflash the default recovery if there are OTAs?
Also I'm thinking about changing the phone from a branded Vodafone one to the default HTC Eu version like this. Does this make it possible to receive OTA from HTC after flashing an RUU and what do I have to consider?
With an official ruu (eg. EU) you should always get updates. Although devs update moreoften.
Sent from my HTC One S using XDA
Eumaniac said:
With an official ruu (eg. EU) you should always get updates. Although devs update moreoften.
Sent from my HTC One S using XDA
Click to expand...
Click to collapse
Thank you for the answer!
But what can you modify and still get OTA Updates? I'm thinking as said about if the CWM as Recovery etc. affects the "OTA-Ability"
You need stock recovery, Stock ROM, All the stock bloatware. you may even need re locked bootloader.
its easier to run an RUU or wait for ROM devs to include the update into the ROM
azzledazzle said:
You need stock recovery, Stock ROM, All the stock bloatware. you may even need re locked bootloader.
its easier to run an RUU or wait for ROM devs to include the update into the ROM
Click to expand...
Click to collapse
Okay, so no chance to modify it a little bit without affecting the OTA ability
I have a nandroid of the default ROM so then I think I should be able to make an OTA by restoring the nandroid, flashing the signed stock recovery and then give it a try?! - As said the Phone is brandet so flashing a RUU would be a little bit more riskier
Mh... I'll just try it when the net OTA is there
My Problem now just is that the Virtuos ROM isn't up to date and every other ROM doesn't fit my needs
The MoDaCo is very "*****y" (doesn't want to boot sometimes) and misses the "Facebook for HTC Sense" and "Twitter for HTC Sense" apps...
Oh and if somebody is interested:
I got my phone changed without any discussion from Vodafone. They just sent me a new one and the delivery boy took my old back to Vodafone.
you could certainly try the Nandroid way ! lots have people have successfully done it this way
Done a bit of research now and all the keywords I have searched through haven't returned any results of this particular issue.
I have flashed CM10 (Stable) to the XL, has installed and boots fine, however there is 0 feedback from the touchscreen so i can't use it at all.
I couldn't really find anyone else with a similar issue. Has anyone run into this, or know what may be causing it?
Have downloaded numerous times, different versions of twrp, everything's been cleared out/wiped (both before and after flash).
I'll add that I have not had this issue at all elsewhere, EXCEPT where yesterday I updated stock to the latest version to give it a go (was hoping for more of a JB experience...). In this case there is / was a bug with TWRP where if you installed Android 4.1 (Latest stock), the touch would no longer work in TWRP. Luckily the TWRP dev updated to 2.3.3.1 today, fixing the touch again (which some themes such as viper require). But I have no idea if any of this is related, shouldn't be though,given the rom should work standalone...
Any ideas would be great. I battled to overcome that damn TWRP mess (seen above) that I got myself into, then I got past a boot issue and now that I'm booted the damn touch doesn't work lol.
Hope to hear some good news,
regards.
Well known and posted about all over this forum.
HTC changed some firmware relating to the touchscreen in the 3.17 update. Roms require a kernel update to work. Twrp can cheat and just use htc's new kernel, cm10 build their kernel from source so could be hard to figure what changed until HTC release source.
-known issue, but only yesterday I told h8rift and Rohan who previously were unaware of the issue.
-The change is in firmware delivered with 3.17
-Requires kernel update to resolve issue.
-Twrp easy to fix.
-Cm and others not so easy and may require waitng for source from HTC.
twistedddx said:
Well known and posted about all over this forum.
HTC changed some firmware relating to the touchscreen in the 3.17 update. Roms require a kernel update to work. Twrp can cheat and just use htc's new kernel, cm10 build their kernel from source so could be hard to figure what changed until HTC release source.
-known issue, but only yesterday I told h8rift and Rohan who previously were unaware of the issue.
-The change is in firmware delivered with 3.17
-Requires kernel update to resolve issue.
-Twrp easy to fix.
-Cm and others not so easy and may require waitng for source from HTC.
Click to expand...
Click to collapse
Thanks for your reply. I just tried installing JellyBam now and alas the same issue, checking here confirms things
Can you recommend a Kernel that will work for the mean time? I was actually looking at some of the kernels, but didn't really go anywhere with it.
You can only use roms and kernels made from 3.17 for the time being.
twistedddx said:
You can only use roms and kernels made from 3.17 for the time being.
Click to expand...
Click to collapse
This sucks. I can't find a single rom/kernel that is compatible with whatever this 3.17 'thing' is (what's this the version of?). Can i roll back this version?
I can't even use the RUU to go back to stock because now the phone has blank version numbers and details and errors out.
My restores also don't work. Only JB roms actually boot now and all of them don't have any touch screen support. I AM able to get touch support if i install the ElementX JB kernel, however that then throws infinite "nfc and android.phone process-stop" messages (just after applications are being upgraded w/ the first boot of a JB rom).
Just looking to make the phone work
Playing around with Joker and have got the phone back into a working state. *phew*
xlmama said:
I can't find a single rom/kernel that is compatible with whatever this 3.17 'thing' is (what's this the version of?). Can i roll back this version?
I can't even use the RUU to go back to stock because now the phone has blank version numbers and details and errors out.
Click to expand...
Click to collapse
3.17 is the HTC build number of the OTA(Over The Air) update you accepted and installed on your phone. Your phone did tell you it was about to install 3.17 and the phone would have referred to it's software version as 3.17 if you had checked.
Currently there is no known way to downgrade the parts that need to be downgraded to restore things to how they were.
This ROM will work on your phone:
http://forum.xda-developers.com/showthread.php?t=2076361
Make sure to flash the boot.img from fastboot.
Extract the boot.img from the zip and do:
fastboot flash boot boot.img
As time goes on more Sense ROM's will be released based on 3.17 and newer anyways so will be less of an issue.
And for non-sense based things like CM eventually HTC will release the source to their kernel and an update to CM will fix the problem also.
twistedddx said:
3.17 is the HTC build number of the OTA(Over The Air) update you accepted and installed on your phone. Your phone did tell you it was about to install 3.17 and the phone would have referred to it's software version as 3.17 if you had checked.
Currently there is no known way to downgrade the parts that need to be downgraded to restore things to how they were.
This ROM will work on your phone:
http://forum.xda-developers.com/showthread.php?t=2076361
Make sure to flash the boot.img from fastboot.
Extract the boot.img from the zip and do:
fastboot flash boot boot.img
As time goes on more Sense ROM's will be released based on 3.17 and newer anyways so will be less of an issue.
And for non-sense based things like CM eventually HTC will release the source to their kernel and an update to CM will fix the problem also.
Click to expand...
Click to collapse
Thanks for your help. I'm now not clueless about my phones fate. :victory:
I have the same issue - updated to Andriod 3.17 about a week ago, and decided to flash CM10 afterwards. As a result, I am stuck with no touchscreen functionality.
Have there been any updates the past few days in terms of ROM's being released that will work on 3.17? How far into the future are we talking about before a release of CM10 will become available?
Is there no way to revert back to ICS and thus have a fully functioning version of CM10?
Is there any news on this issue ?
It's not possible until HTC releases kernel source. There's nothing the devs can do. You can only run sense roms
Sent from my VENOMized HoxL
twistedddx said:
3.17 is the HTC build number of the OTA(Over The Air) update you accepted and installed on your phone. Your phone did tell you it was about to install 3.17 and the phone would have referred to it's software version as 3.17 if you had checked.
Currently there is no known way to downgrade the parts that need to be downgraded to restore things to how they were.
This ROM will work on your phone:
http://forum.xda-developers.com/showthread.php?t=2076361
Make sure to flash the boot.img from fastboot.
Extract the boot.img from the zip and do:
fastboot flash boot boot.img
As time goes on more Sense ROM's will be released based on 3.17 and newer anyways so will be less of an issue.
And for non-sense based things like CM eventually HTC will release the source to their kernel and an update to CM will fix the problem also.
Click to expand...
Click to collapse
Not mine, tried it twice. The only ROM I've been able to get running is PA 2.54, and the only way I could get the touchscreen to work is by flashing the Kernal from Hatkas ROM. Even that fc'd NFC to the point repeatedly So I'm thinking if I can find [or get help finding] a 3.17.661 kernal that will work with PA, I'll be golden.
I think I may be having the same problem, though I don't remember ever upgrading to 3.17. Is what you all are seeing like the screen doesn't even turn on? It just stays black, but the power button and volume button seem to be responsive? I can't even seem to get into recovery or bootloader, and this all started when I flashed the latest CM10 nightly.
Never mind.
Magickalhack said:
Not mine, tried it twice. The only ROM I've been able to get running is PA 2.54, and the only way I could get the touchscreen to work is by flashing the Kernal from Hatkas ROM. Even that fc'd NFC to the point repeatedly So I'm thinking if I can find [or get help finding] a 3.17.661 kernal that will work with PA, I'll be golden.
Click to expand...
Click to collapse
You do realized you flashed a sense kernel for an aosp Rom?... And you're wondering why it gave you FC's?
I'm on hboot 1.09, did not do OTA update, and the touchscreen works on CM 10.1 90% of the time, but sometimes I open it up and it doesn't respond. Hitting the sleep button twice fixes it but it's annoying. Would the above fix do anything for me? What else could be the problem?
slash178 said:
I'm on hboot 1.09, did not do OTA update, and the touchscreen works on CM 10.1 90% of the time, but sometimes I open it up and it doesn't respond. Hitting the sleep button twice fixes it but it's annoying. Would the above fix do anything for me? What else could be the problem?
Click to expand...
Click to collapse
Do you use s2w? That causes that issue
Sent from my VENOMized HoxL
Hey, sorry for such a noob question, I do lots of reading on here and tried to post within a certain rom, C-Rom Kit-Kat 4.4.2 5/13/14, and it won't allow me since I have never posted anything on XDA. I have the Verizon HTC ONE M8 and it is bootloader unlocked, s-off, and on the stock rom with build number 1.56, with lots of customization but I found a new rom I wanted to try. It is an AOSP rom like mentioned above but I never seemed to find what build number it is on? I know with a SENSE rom you have to be careful of what build number your phone is, whether it is 1.54 before the update or 1.56 after the update.
My question is, when flashing an AOSP/AOKP/CM rom through TWRP, does the build number matter? In all the AOSP roms I never haven't been able to find where the OP states which it is, making me wonder if I need to worry about it or not? I want to flash away from the stock rom but only to an AOSP type rom.. I want to be careful because since we don't have a removable battery, I am worried I will be stuck in bootloop and I am not sure how to get out of it without a battery pull.. (I know holding power and volume up will restart the phone but how would you get back into recovery to restore a backup?)
Also while I am at my first post, do you recommend TWRP, CWM, or Philz touch recovery? I would like to stick to one recovery throughout the tenure of the rooted ONE M8, makes keeping backups
Thanks for the help and I greatly appreciate it! And I apologize again for such a noob question..
pahlerc1 said:
Hey, sorry for such a noob question, I do lots of reading on here and tried to post within a certain rom, C-Rom Kit-Kat 4.4.2 5/13/14, and it won't allow me since I have never posted anything on XDA. I have the Verizon HTC ONE M8 and it is bootloader unlocked, s-off, and on the stock rom with build number 1.56, with lots of customization but I found a new rom I wanted to try. It is an AOSP rom like mentioned above but I never seemed to find what build number it is on? I know with a SENSE rom you have to be careful of what build number your phone is, whether it is 1.54 before the update or 1.56 after the update.
My question is, when flashing an AOSP/AOKP/CM rom through TWRP, does the build number matter? In all the AOSP roms I never haven't been able to find where the OP states which it is, making me wonder if I need to worry about it or not? I want to flash away from the stock rom but only to an AOSP type rom.. I want to be careful because since we don't have a removable battery, I am worried I will be stuck in bootloop and I am not sure how to get out of it without a battery pull.. (I know holding power and volume up will restart the phone but how would you get back into recovery to restore a backup?)
Also while I am at my first post, do you recommend TWRP, CWM, or Philz touch recovery? I would like to stick to one recovery throughout the tenure of the rooted ONE M8, makes keeping backups
Thanks for the help and I greatly appreciate it! And I apologize again for such a noob question..
Click to expand...
Click to collapse
Correct me if im wrong, but the sense build is just telling what that ROM is based on. Once your S-OFF, you can flash them as you please. I know the bootloader version was what would cause bricks in the past (flashing a 4.2.2 rom in a 4.3 bootloader) but i havent seen anything like that for the M8 yet.
Vol DOwn and power will get you to hboot which will let you get to recovery. I use CWM but theyre all comparable, just personal preference.
Abe21599 said:
Correct me if im wrong, but the sense build is just telling what that ROM is based on. Once your S-OFF, you can flash them as you please. I know the bootloader version was what would cause bricks in the past (flashing a 4.2.2 rom in a 4.3 bootloader) but i havent seen anything like that for the M8 yet.
Vol DOwn and power will get you to hboot which will let you get to recovery. I use CWM but theyre all comparable, just personal preference.
Click to expand...
Click to collapse
Thanks for the reply! I can't wait to flash this new AOSP rom so I can remove all the bloatware put on by Verizon and Sense.. Just want to vierfy, so if the build number no longer matters since I am s-off, you're saying I can flash the ARHD rom on my phone even though it states the build number 1.54 and I have 1.56? Because I would also love to have a stock sense rom with lots of optimizations and tweaks for performance with less bloatware.
Thanks again
pahlerc1 said:
Thanks for the reply! I can't wait to flash this new AOSP rom so I can remove all the bloatware put on by Verizon and Sense.. Just want to vierfy, so if the build number no longer matters since I am s-off, you're saying I can flash the ARHD rom on my phone even though it states the build number 1.54 and I have 1.56? Because I would also love to have a stock sense rom with lots of optimizations and tweaks for performance with less bloatware.
Thanks again
Click to expand...
Click to collapse
I just read that if you have the newest 1.55.6.. firmware and baseband and try to flash roms with the older baseband (1.54) then you might run into problems with losing root and and other issues..
Can someone please verify this? Currently on stock rom, rooted, s off, bootloader unlocked, with baseband 1.55.6.. Looking into flashing either AOSP rom or Sense rom but does it matter if its based on 1.54 or the newest 1.56?
Thanks, the help is greatly appreciated
pahlerc1 said:
I just read that if you have the newest 1.55.6.. firmware and baseband and try to flash roms with the older baseband (1.54) then you might run into problems with losing root and and other issues..
Can someone please verify this? Currently on stock rom, rooted, s off, bootloader unlocked, with baseband 1.55.6.. Looking into flashing either AOSP rom or Sense rom but does it matter if its based on 1.54 or the newest 1.56?
Thanks, the help is greatly appreciated
Click to expand...
Click to collapse
you're just gonna end up with whatever baseband you flash as the latest baseband. where are you seeing people lose root bc of flashing a different baseband?
Abe21599 said:
you're just gonna end up with whatever baseband you flash as the latest baseband. where are you seeing people lose root bc of flashing a different baseband?
Click to expand...
Click to collapse
It was in a different thread, can't recall which.. I have been doing way too much reading I think it was in one last few pages of the venom rom thread.. I'll just wait for Venom and Skyfall to update their baseband to the latest 1.56 build. No worries. Thanks.
Updated to the latest VZW firmware, and have had no issues using the multi-variant roms, which use the non-Verizon versions. My radio base still reflects the updated version (0321). On Viper right now with no issues, waiting for AOKP. Been using 2.7.0.2 TWRP with no problems. If you have a concern about flashing any ROM (and/or gapps if you are trying an AOSP ROM), just make sure you make a backup in recovery before anything else, and if the new stuff doesn't work well or borks your device, just learn how to get back into recovery and restore your backup. Read first, try second.
ebb said:
Updated to the latest VZW firmware, and have had no issues using the multi-variant roms, which use the non-Verizon versions. My radio base still reflects the updated version (0321). On Viper right now with no issues, waiting for AOKP. Been using 2.7.0.2 TWRP with no problems. If you have a concern about flashing any ROM (and/or gapps if you are trying an AOSP ROM), just make sure you make a backup in recovery before anything else, and if the new stuff doesn't work well or borks your device, just learn how to get back into recovery and restore your backup. Read first, try second.
Click to expand...
Click to collapse
Okay thanks for the help. I always make sure to read first and create a backup, I've made the mistake once and took a long process to get it solved and won't let that happen again that's for sure! Thanks for the response, I just flashed Skyfall 2.5 and it is amazing!