Related
I have a D2G and I used to run Froyo-based CM7, but since the Gingerbread version is further along in development I went back to Gingerbread by SBFing. So I'm on 4.5.608 and neither of the two times I tried to flash CM7 did it work. I had to SBF twice. The first time, I got the file from Rootzwiki, and the second time I got the "7.1 Stable" file from Rom Toolbox. I used the same Google Apps package on both attempts.
So my questions are:
1. Can a Google Apps package get you stuck at the boot logo?
2. If the problem is my file, where can I go to get a good one?
PantherHeel93 said:
I have a D2G and I used to run Froyo-based CM7, but since the Gingerbread version is further along in development I went back to Gingerbread by SBFing. So I'm on 4.5.608 and neither of the two times I tried to flash CM7 did it work. I had to SBF twice. The first time, I got the file from Rootzwiki, and the second time I got the "7.1 Stable" file from Rom Toolbox. I used the same Google Apps package on both attempts.
So my questions are:
1. Can a Google Apps package get you stuck at the boot logo?
2. If the problem is my file, where can I go to get a good one?
Click to expand...
Click to collapse
In order for a Gingerbread ROM to boot it needs the Gingerbread Kernel. Are you booting with a white Motorola logo or a red one?
If it's still white and you're trying to boot Gingerbread CM7 it may be worth it to try to grab the .608 Gingerbread kernel from the TBH hack and flash that in. I've attached it to this post just in case.
PantherHeel93 said:
So I'm on 4.5.608 and neither of the two times I tried to flash CM7 did it work. I had to SBF twice. The first time, I got the file from Rootzwiki, and the second time I got the "7.1 Stable" file from Rom Toolbox. I used the same Google Apps package on both attempts.
So my questions are:
1. Can a Google Apps package get you stuck at the boot logo?
2. If the problem is my file, where can I go to get a good one?
Click to expand...
Click to collapse
7.1 Stable is probably the “official” CM7 build 7.1.0, from the cyanogenmod site.
That one is for Froyo (i.e. can only be installed over 2.4.x stock firmware).
As for RootzWiki builds… did you wipe data prior to or after installing the ROM via CWM?
projektorboy said:
In order for a Gingerbread ROM to boot it needs the Gingerbread Kernel. Are you booting with a white Motorola logo or a red one?
If it's still white and you're trying to boot Gingerbread CM7 it may be worth it to try to grab the .608 Gingerbread kernel from the TBH hack and flash that in. I've attached it to this post just in case.
Click to expand...
Click to collapse
Red. The SBF file put me in this situation:
System version: 4.5.608.A956.Verizon.en.US
Android version: 2.3.3
Kernel version: 2.6.32.9-gb092e69w360842ca25rhe92 #2
Build number: 4.5.1_57_D2G-38
Gasai Yuno said:
7.1 Stable is probably the “official” CM7 build 7.1.0, from the cyanogenmod site.
That one is for Froyo (i.e. can only be installed over 2.4.x stock firmware).
As for RootzWiki builds… did you wipe data prior to or after installing the ROM via CWM?
Click to expand...
Click to collapse
Yeah, the reason is didn't download the stable one first is because I thought as far as anyone had gotten was 7.0 nightlies. I'm just baffled right now as to why I can't get the Gingerbread CM7. I hate stock haha
Before I flash, I backup, reboot, factory reset, wipe data, cache, dalvik, and even battery stats. Then I install CM, then gapps package, then reboot.
Thanks for the help guys, I appreciate it!
Could you specify the file names for both CM7 and gapps you're using?
And you're wrong about RW builds being 7.0; they use the current CM7 source tree, and the “stable 7.1.0” is basically one of old Froyo builds by revnumbers.
Actually, I got everything from here: http://forum.xda-developers.com/archive/index.php/t-1297517.html
I used the latest version "update-cm-7.1.0-DROID2WE" and the "gapps-gb-20110828".
The second time I used the CM file from Rom Toolbox and the same Google Apps package. So if a bad gapps package can eff you over, that's probably it. I just don't want to waste my time and try again before I have some xda-genius opinions haha
This is the Froyo-only “official” build. It will never work with a Gingerbread kernel.
As for ROM Toolbox, I have no idea. The gapps package seems to be the right one, however.
Head to http://ez-netsolutions.com/synik4l/x13thangelx/D2G/cm/ for the latest build of CM7 for the D2G. x13thangelx is currently the lead developer working on this project.
Thanks a lot!!!!!! You're the best haha I'll let you know if it works.
Refer to this thread on RootzWiki for more information: http://rootzwiki.com/topic/3069-dev-threaddroid-2-global-cm7-with-gingerbread-leak-kernel/; note that the opening post hasn't been updated since forever, so you won't find the current build there.
And use this thread if you have any questions: http://rootzwiki.com/topic/4922-cm7-for-droid2-global-users-thread/
Not necessary haha, but I got it and it's working and beautiful and every setting has been adjusted and I'm super happy again!=D You're my hero.
I purchased an Optimus T (P509) in 2012 and had it unlocked to use on a trip I went to europe. I played around with it a lot and messed with custom roms and basebands, and then left it alone for about a year. I'm now downsizing my phone/tech collection in general and looking to update this to use as a daily driver.
Here's the info about my phone:
ClockworkMod recover v5.0.2.0
Baseband: LGP509AT-00-V10l-OPEN-COM-OCT-23-2010
CyanogenMod version: 10-20130108-UNOFFICIAL-p509
Build number: cm_p509-userdebug 4.1.2 JZO54k eng.arjen.20130108.030427 test-keys
My questions are:
What updates to baseband (if any) do I need to do? Would this mess up my unlock?
Do I need to flash a new recovery?
What ROM would be best for my needs as a daily driver? requirements are stable without crashes and everything works, followed by the newest android version.
Really the rom part I can experiment with later, I'm just not sure if I've hosed myself with the baseband 'fixes' that I recall messing with 2 years ago. I have a new sim card on the way that I will use with this.
shivanani said:
I purchased an Optimus T (P509) in 2012 and had it unlocked to use on a trip I went to europe. I played around with it a lot and messed with custom roms and basebands, and then left it alone for about a year. I'm now downsizing my phone/tech collection in general and looking to update this to use as a daily driver.
Here's the info about my phone:
ClockworkMod recover v5.0.2.0
Baseband: LGP509AT-00-V10l-OPEN-COM-OCT-23-2010
CyanogenMod version: 10-20130108-UNOFFICIAL-p509
Build number: cm_p509-userdebug 4.1.2 JZO54k eng.arjen.20130108.030427 test-keys
My questions are:
What updates to baseband (if any) do I need to do? Would this mess up my unlock?
Do I need to flash a new recovery?
What ROM would be best for my needs as a daily driver? requirements are stable without crashes and everything works, followed by the newest android version.
Really the rom part I can experiment with later, I'm just not sure if I've hosed myself with the baseband 'fixes' that I recall messing with 2 years ago. I have a new sim card on the way that I will use with this.
Click to expand...
Click to collapse
1 - Actually upgrading baseband on that device would lock you out of some frequencies the radio ( not the FM radio ) uses to communicate with the carriers towers. I also have a Optimus T ( P509 ), tho no longer in service.
2 - Depends if you want KitKat ( 4.4 ). If you do then you'll need CWM 6.0.4.4 or newer. I am currently working on a utility for older CWM versions to be able to install KitKat but until then you'll need what I just mentioned. If not too interested in KitKat then you can leave your recovery as is. I use CWM 5.0.2.7 Touch by @vivekkalady. I've been using her recovery since she introduced it.
3 - You'll have to search and make that decision for yourself as we all have different needs and habits.
shinobisoft said:
1 - Actually upgrading baseband on that device would lock you out of some frequencies the radio ( not the FM radio ) uses to communicate with the carriers towers. I also have a Optimus T ( P509 ), tho no longer in service.
2 - Depends if you want KitKat ( 4.4 ). If you do then you'll need CWM 6.0.4.4 or newer. I am currently working on a utility for older CWM versions to be able to install KitKat but until then you'll need what I just mentioned. If not too interested in KitKat then you can leave your recovery as is. I use CWM 5.0.2.7 Touch by @vivekkalady. I've been using her recovery since she introduced it.
3 - You'll have to search and make that decision for yourself as we all have different needs and habits.
Click to expand...
Click to collapse
That's interesting what you said about the current baseband, I'm not sure if I changed it after I last used it. But I turned off airplane mode and popped in a T-mob sim and it wasn't able to connect to a network, similar results with H2O wireless card (at&t mvno). I'm not sure if my current version of android is messed up or the baseband.
I don't mind upgrading CWM, is there any downside to doing so? Is there a kitkat build out now that works? I may want to use KitKat as I hear it's meant to be more usable on smaller memory systems like the p509.
I don't mind finding one I like eventually, but looking for a recommendation to start off with that should work without too much difficulty.
Thanks for you help so far, I hope if can figure out this cell network problem :-/
shivanani said:
That's interesting what you said about the current baseband, I'm not sure if I changed it after I last used it. But I turned off airplane mode and popped in a T-mob sim and it wasn't able to connect to a network, similar results with H2O wireless card (at&t mvno). I'm not sure if my current version of android is messed up or the baseband.
I don't mind upgrading CWM, is there any downside to doing so? Is there a kitkat build out now that works? I may want to use KitKat as I hear it's meant to be more usable on smaller memory systems like the p509.
I don't mind finding one I like eventually, but looking for a recommendation to start off with that should work without too much difficulty.
Thanks for you help so far, I hope if can figure out this cell network problem :-/
Click to expand...
Click to collapse
Either your APN settings are wrong, which you can manually fix, or you did upgrade/downgrade/change baseband. The P509 is supposed to be an old baseband phone. The P500 and P509 are identical. Only difference is the P500 is a new baseband device. You can flash a P500 ROM. If you don't get any signal, then most likely your on old baseband. There is a patch for that, no biggie. If you do get signal then you're on new baseband and you should continue to use P500 ROMs. If you decide to flash a P509 ROM you won't have any service which will be a baseband issue. There is a new baseband patch around here somewhere too.
You can find a link to the old baseband patch in the LG Optimus One FAQ. Post #8 or #9, I think.
shinobisoft said:
Either your APN settings are wrong, which you can manually fix, or you did upgrade/downgrade/change baseband. The P509 is supposed to be an old baseband phone. The P500 and P509 are identical. Only difference is the P500 is a new baseband device. You can flash a P500 ROM. If you don't get any signal, then most likely your on old baseband. There is a patch for that, no biggie. If you do get signal then you're on new baseband and you should continue to use P500 ROMs. If you decide to flash a P509 ROM you won't have any service which will be a baseband issue. There is a new baseband patch around here somewhere too.
You can find a link to the old baseband patch in the LG Optimus One FAQ. Post #8 or #9, I think.
Click to expand...
Click to collapse
I wasn't certain what my starting point was since I'd done this so long ago (and I thought I applied the old BB fix at some point too...). Anyways, I took a drastic step and installed the stock rom V10s_00.kdz with the kdz installer from LG. It successfully flashed and I don't have a brick on my hands
The problem is now the phone doesn't recognize any sim cards, of which I've tried 3: tmobile micro, h2o micro, and a gophone minisim. The microsims were put in a cut out minisim as an adapter. The gophone is a normal minisim that is uncut, but it's not activated. I never got a locked or bad sim message, just that there is no sim card in place.
Under phone status it shows a signal strength (varies -65 to -75 and 25 asu)
Under APN settings it matches the T-mobile ones
And the baseband via secret menu is amss6038
I'm wondering if the sim module or gsm module are messed up? I kinda want to try out the emergency calling but would rather not get the police involved
I messed up my SIM contacts when I left an adapter in there and pulled it a little too hard out! I removed the compression plate on the back and it works again. I'll have to get a small piece of electronic safe foam to apply pressure to the back of the SIM to keep it in proper position. (http://forum.xda-developers.com/showthread.php?t=2598308)
I'm interested in the kitkat build here: http://forum.xda-developers.com/showthread.php?t=2589303
If I were to want to use that, do I need to flash the baseband fix on top of the other install instructions? Anything special in terms of timing it at a certain point in the install process?
Thanks for your help so far, I forgot how much fun messing with android was :laugh:
shivanani said:
I messed up my SIM contacts when I left an adapter in there and pulled it a little too hard out! I removed the compression plate on the back and it works again. I'll have to get a small piece of electronic safe foam to apply pressure to the back of the SIM to keep it in proper position. (http://forum.xda-developers.com/showthread.php?t=2598308)
I'm interested in the kitkat build here: http://forum.xda-developers.com/showthread.php?t=2589303
If I were to want to use that, do I need to flash the baseband fix on top of the other install instructions? Anything special in terms of timing it at a certain point in the install process?
Thanks for your help so far, I forgot how much fun messing with android was :laugh:
Click to expand...
Click to collapse
Well, we still aren't sure if your device is new or old baseband. With the recovery you already have, flash CM10.1, CM10.2, or CM10.3 ( All JellyBean ). Latest CM10.2 builds can be downloaded here. Easiest way to work around the baseband thing is to figure out which ROMs, P500 or P509, that will give you cell service. Flash a P509 ROM. If no service then you upgraded baseband so you'll need to use P500 ROMs. Flash a P500 ROM and if no service then you're on old baseband and you should use P509 ROMs. Only difference between P500 and P509 ROMs is the P500 ROMs are NEW baseband and the P509 ROMs are OLD baseband.
As of now the only KitKat ROMs being build are for the P500. If you find you are OLD baseband, flash the oldbb fix from the FAQ I mentioned a couple posts back. Oh, and you'll need the newest CWM 6.0.4.4 or newer recovery to flash KitKat.
Hope all this helps...
shinobisoft said:
Well, we still aren't sure if your device is new or old baseband. With the recovery you already have, flash CM10.1, CM10.2, or CM10.3 ( All JellyBean ). Latest CM10.2 builds can be downloaded here. Easiest way to work around the baseband thing is to figure out which ROMs, P500 or P509, that will give you cell service. Flash a P509 ROM. If no service then you upgraded baseband so you'll need to use P500 ROMs. Flash a P500 ROM and if no service then you're on old baseband and you should use P509 ROMs. Only difference between P500 and P509 ROMs is the P500 ROMs are NEW baseband and the P509 ROMs are OLD baseband.
As of now the only KitKat ROMs being build are for the P500. If you find you are OLD baseband, flash the oldbb fix from the FAQ I mentioned a couple posts back. Oh, and you'll need the newest CWM 6.0.4.4 or newer recovery to flash KitKat.
Hope all this helps...
Click to expand...
Click to collapse
Well, I'm on the old baseband, the reason I know is I used KDZ to nuke it back to p509 stock! The more I read about kdz after I did it the more scared I got, but I lucked out and everything is fine now
The sim unlock is preserved, and I successfully rooted it with gingersnap. I don't have any sort of recover on it yet, it looks like CWM 6.0.4.4 does not work with older roms, just Kitkat based ones. So I'll do some more homework and figure out if I want to jump right into KK or try JB first.
Thanks for all your help, you gave me a quick jumpstart and brought back a lot of knowledge that was tucked away in the back corner of my brain!
shinobisoft said:
Well, we still aren't sure if your device is new or old baseband. With the recovery you already have, flash CM10.1, CM10.2, or CM10.3 ( All JellyBean ). Latest CM10.2 builds can be downloaded here. Easiest way to work around the baseband thing is to figure out which ROMs, P500 or P509, that will give you cell service. Flash a P509 ROM. If no service then you upgraded baseband so you'll need to use P500 ROMs. Flash a P500 ROM and if no service then you're on old baseband and you should use P509 ROMs. Only difference between P500 and P509 ROMs is the P500 ROMs are NEW baseband and the P509 ROMs are OLD baseband.
As of now the only KitKat ROMs being build are for the P500. If you find you are OLD baseband, flash the oldbb fix from the FAQ I mentioned a couple posts back. Oh, and you'll need the newest CWM 6.0.4.4 or newer recovery to flash KitKat.
Hope all this helps...
Click to expand...
Click to collapse
CM10.3
Sent from my GT-I9082 using Tapatalk
It's been a very long time since I last updated my HTC One S, and recently I was going to do an update. I'm not quite sure where to start because I still have my old roms and recovery flashed. I tried searching through various forums but it seems like most of the posts are at least updated to a more recent HBoot. I'm a complete noob when it comes to custom flashing roms and whatnot and was hoping someone might be able to point me in the right direction of what order to update my phone in.
As for my phone's versions:
HBoot 1.06.0000
Android Version 4.0.3
HTC Sense 4.0
ROM: LeeDrOiD One Supreve V2.0.0
Recovery: ClockworkMod Recovery v5.8.1.5
Kernel: Stock as far as I know
Any help is appreciated! And please let me know if additional information is required.
Hello all,
Okay, I admit that I am gonna get a lot of "use the search tool first" replies, but please hear me out. I have done my fair share of searching. Its not that I haven't found anything, its just the things I found are useless for this SGS 4G. I really wanted to install Cyanogen Mo on the SGS (its not actually mine, a friend asked me to do it since he saw my old SGS GT-I9000 running CM).
I am gonna try and give a detailed report . The phone was originally from T-Mobile and now unlocked permanently. Its running firmware version 2.3.3 that I installed just recently. I found out that I can't install CWM on the stock kernel or bootloader or whatever and I needed a new of the thing. So I went on searching and searching....found a handful of help but none work. Every method breaks at some point and I go to the "firmware update failed" thing on the phone, which I then install 2.3.3 again using ODIN and try another method. I have tried a lot of things. Hemidall, ODIN, SuperOneClick, and a lot of gibbrish-sounding methods. None work. I am now running 2.3.3. Here are some infos:
ABOUT PHONE:
Model Number: SGH-T959V
Firmware Version: 2.3.3
Baseband Version: T959VUVKF1
Kernel Version: 2.6.35.7-T959VUVKF1-CL270364
Build Number: GINGERBREAD.VUVKF1
The files I used to flash to 2.3.3 using ODIN v1.85:
PIT: Hawk_Sidekick_VibrantPlus_831.pit
PDA: CODE_T959VUVKF1_CL270364_REV00_user_low_noship.tar.md5
PHONE: T959VUVKF1-Phone-CL1020302.tar.md5
CSC: SGH-T959V-CSC-TMB-VIBRANTP.tar.md5
I hope the above infos are enough. So, can anyone help me and point me to the right direction on how to install CWM and then install CM10 or 9 on my friends SGS 4G?
Thanks,
Tamrat
Hmmm, an interesting set of binaries, ones that don't ring a bell with me. I'm used to seeing T959VUVKJ6.
Where did you find those? Half curiosity, half trying to understand the problem, half since much of the "old" images for the phones got lost when Multiupload and what have you were shut down.
For the SGS4G, the kernel, root file system, and recovery file system are all in "boot.img" -- flash one, you flash them all. They can be flashed through Odin (assuming you really like Windows), heimdall (multi-platform), through recovery, or from a root command line (for the adventurous only).
I would say the most robust way to get where you need to be would be to use Lumin's guide to make sure you've got a viable Gingerbread set-up going, then flash something reliable to get you to MTD, like TeamAcid's CM9.
From there, you should know that some of the KK ROMs use slightly different MTD partitioning and aren't a "just flash this ROM and keep your data" kind of thing.
jeffsf said:
Hmmm, an interesting set of binaries, ones that don't ring a bell with me. I'm used to seeing T959VUVKJ6.
Where did you find those? Half curiosity, half trying to understand the problem, half since much of the "old" images for the phones got lost when Multiupload and what have you were shut down.
Click to expand...
Click to collapse
A long day Googling... and then a site turned up. One thing I forgot to mention was, before I installed this firmware, I had to use the "remove battery->plug usb->press the button combos->insert the battery" to enter download mode, but now I juts have to press vol down and power button.
Thanks for the reply,
Failure again
UPDATE:::
I tried to update to 2.3.6 as the guide suggests and I also wanted a clean stock OS in case the old one was not. But once again updating to 2.3.6 has been a pain. Kies Mini recognizes the phone but it doesn't recognize the firmware running on the phone. And also, firmware update is impossible since the button is greyed out.
I googled again and found the official 2.3.6 firmware for the phone (file name: T959VUVKJ6-REV00-home-low-CL694130.tar.md5) and tried flashing it using ODIN; absolutely no luck. It fails at the stage which says Slb.bin. Restarting the phone after that gives a "firmware upgrade failure" display. Only way to wake up the phone is to flash the previous OS back.
I am really confused here.
*********************EDIT***************
Some how, after like 10 retires and fiddling with ODIN, it finally flashed 2.3.6 to the SGS 4G. Still, fingers crossed.
*********************EDIT 2***************
Finally, its all working fine now. Thank you @jeffsf, thank you very much.
F*****************K
forgot an important step and now my IEMI number is gone........
do i throw the phone now, or is there any other way???
Don't throw your phone away! How do you know that you have "no IMEI" on your phone? We'll go from there.
Hopefully, you've backed up your data before starting to play around with ROMS. If so just load your backed up efs folder onto your storage & use Root Explorer to drop it over your existing one , it will overwrite your imei file & you will be good as new.
========================================================================================
I'm also in need of help, I have been running SlimSaber since last weekend, was wanting to try out Beanstalk. First full wipe, install & reboot wipe again, reinstall etc as per Dao's OP, but after the first install, it won't boot past the kernel splash. Tried again with same result. Decided to click it back to stock & start over, using Gremlin Remover (odin). Then saw that others were having similar issue so I tried to load in build from April1st.
But now it only boots back into recovery, won't boot to the OS ( everything indicated install was complete & no errors.)
1 clicked back again & just tried to put SlimSaber back on again, but have the same problem, will only boot into recovery.
I had to first load CM9 to get CWM 6.xx so I could install kk using TWRP
What am I not doing correctly? Thanks for any suggestions.
Flash kernel
Reboot recovery
Wipe all partitions
(Reboot recovery for good measure and wipe again if paranoid)
Install
Boot
If that doesn't do it, it is likely ROM or hardware.
---
Posted from whatever phone booted today
Since this is running GB VUVKG4, could you recommend a kernel that would work & get me to TWRP (or CWM 5.xx+)?
Either the Team Acid CM9 or Hefe Kernel should work.
---
Posted from whatever phone booted today
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!