Develop Bugs

Galaxy S3 bootloops after flashing any custom rom

So I rooted my phone and installed the latest CWM recovery but every time I try to install any custom rom I get a status 7 error and it says something along the line of asserts failed ro.product.drvice == d2att. I've tried using TWRP, I've unrooted and installed stock, nothing seems to work. Last week I was running Jellybam fine for about 2 days, got stuck in bootloop, tried numerous ways to fix it, ended up returning to stock but now I cannot flash anything. Help me please

The status 7 error happens when the ROM ur about to flash, checks to see if the model of ur phone is compatible with said ROM. Its a good thing(safety mechanism) but can be a pain at the same time. What version of cwm are u using? Download the latest cwm recovery thru the ROM manager app and that can sometimes fix the issue. What ROM are you trying to install?
Sent from my SAMSUNG-SGH-I337 using xda premium

I think 6.0.2.3? not 100% sure though.. and I need to be rooted in order for rom manager to work... I tried using it but it kept saying the flash failed.. I'm using the root recovery. I've tried flashing CM 10.1 and RC5 as well as the latest and 3 before that Jellybam Roms

shewantsmyduck said:
I think 6.0.2.3? not 100% sure though.. and I need to be rooted in order for rom manager to work... I tried using it but it kept saying the flash failed.. I'm using the root recovery. I've tried flashing CM 10.1 and RC5 as well as the latest and 3 before that Jellybam Roms
Click to expand...
Click to collapse
Latest cwm is at 6.0.3.1
I think you're getting a little confused.
You need to be rooted to have any custom recovery installed, so right off the bat you are rooted. You shouldn't flash anything with rom manager, it can cause serious harm to your phone. Tom manager is best for just updating your recovery.
There are two main reasons for a status7 error, out of date recovery or an out of date bootloader.
Update your recovery to 6.0.3.1 and he to flash it again, if it comes back you'll need to update your bootloader a two second search in these threads will provide you with a large handful of threads where people had identical issues as you
Sent from my SGH-I747 using xda app-developers app

Checked my bootloader and it says i747UCDLK3 and I think that's the latest... I'll root and install latest CWM through rom manager once I get home

And one question though... I tried using TWRP 2.5 (the latest) and I still got the status 7 error...?

shewantsmyduck said:
So I rooted my phone and installed the latest CWM recovery but every time I try to install any custom rom I get a status 7 error and it says something along the line of asserts failed ro.product.drvice == d2att. I've tried using TWRP, I've unrooted and installed stock, nothing seems to work. Last week I was running Jellybam fine for about 2 days, got stuck in bootloop, tried numerous ways to fix it, ended up returning to stock but now I cannot flash anything. Help me please
Click to expand...
Click to collapse
Can you flash any stock modded rom's ? You state you went back to stock but what method did you use to go back to stock ?
Why oh why were you using jellybam...

My cousin has it on his Verizon GS3 and it works perfectly fine so I thought I'd give it a shot. To go back to stock I followed some unroot and return to stock I found online.. not sure of the link. It basically consisted of flashing it in Odin and returned it back to stock 4.0.4 which I then updated to 4.1.1 using att ota. I'm not sure if it was a a modded stock rom or not. And I really don't feel like going back through that mess again only to flash it and get stuck in another boot loop I want to be pretty positive that it will work :/

shewantsmyduck said:
My cousin has it on his Verizon GS3 and it works perfectly fine so I thought I'd give it a shot. To go back to stock I followed some unroot and return to stock I found online.. not sure of the link. It basically consisted of flashing it in Odin and returned it back to stock 4.0.4 which I then updated to 4.1.1 using att ota. I'm not sure if it was a a modded stock rom or not. And I really don't feel like going back through that mess again only to flash it and get stuck in another boot loop I want to be pretty positive that it will work :/
Click to expand...
Click to collapse
The ODIN flash to stock 4.0.4 probably installed the old ics bootloaders, and the ota update to 4.1.1 may not have included the new jb bootloaders.

Ok so what is the newest bootloader? I downloaded the root checker that allows you to see your bootloader version and it's on i747UCDLK3.

shewantsmyduck said:
Ok so what is the newest bootloader? I downloaded the root checker that allows you to see your bootloader version and it's on i747UCDLK3.
Click to expand...
Click to collapse
That's the right one
Sent from my SGH-I747 using xda premium

So what should I do now then :s

You're trying to flash the wrong rom for your device, or you're not using the right recovery for your device. What Galaxy S3 model do you have? On which carrier are you and where did you buy the phone?

I have an AT&T i747 that I got at an AT&T store. The Rom is correct as I've downloaded it numerous times and I've tried the latest TWRP recovery and still received the error.

I'm going to try and flash a factory image tomorrow from the development section and root afterwards. As Michael3214 pointed out in a pm, the issue may be that my phones id has changed, hopefully a factory image will fix that.

[Fix] 4.3 ROMs stuck on splash screen after first reboot

For those of you who keep getting stuck on the splash screen after trying to restart your phone after installing a 4.3 ROM.
My steps were (and I take no credit for this, I can't remember who had said to do this and I wasn't logged in so I couldn't click the thank you button):
*Note* If you were already on the Stock 4.3 ROM you do not want to flash the 4.0.4, 4.1.1 or 4.1.2 Stock ROM since you will brick your phone. The Stock ROM contains the Bootloader which should never be downgraded. Fyi: the Bootloader is not the Baseband, the Baseband is just what Modem you're using.
1. Use Odin to flash the latest stock ROM
2. Enter the stock recovery and do a factory reset and clear the cache (I did both twice just to make sure)
3. Use Odin to flash the stock rooted ROM.
4. Enter the stock recovery and do a factory reset and clear the cache. (This might not be necessary but I did anyways just to make sure)
5. Use Odin to flash a custom recovery (TWRP 2.6.0.0 was the newest recovery when I did this last week)
6. Enter the custom recovery and wipe everything, then flash whatever 4.3 based ROM and then flash GApps if you want.
*Note* It seemed like the phone was hanging on the splash screen after either the initial boot or the first restart (I can't remember which, it's been a week) but it did boot and reboot fine.
I hope this helps out some people since I found it to be quite irritating that I could install a 4.3 ROM and set everything up but when I went to restart it would hang at the splash screen (going into the recovery and clearing the cache/dalvik cache wasn't helping).

Are you basically saying to revert back to stock settings and redo the entire root process again?
Sent from my SGH-I747 using xda app-developers app

bullet2binary said:
Are you basically saying to revert back to stock settings and redo the entire root process again?
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Yeah, from what I had read that seemed to be necessary since I had used Odin to update the bootloader (MF1 since my phone is the M variant) by itself when the newest Stock ROM had come out a while ago. I still flashed the newest Stock ROM (same MF1 bootloader for the M variant) but the first time I did it I forgot to enter the Stock Recovery to do a Factory Reset and Clear the Cache and ended up stuck on the splash screen of a 4.3 ROM after flashing a custom recovery. So I needed to reflash back to stock and start over.
Going into the Stock Recovery and doing a Factory Reset and Clearing Cache is necessary and doesn't take much time at all so you may as well do it just to be sure. I also recommend backing up your IMEI if you haven't done it yet.

spongdangly said:
Yeah, from what I had read that seemed to be necessary since I had used Odin to update the bootloader (MF1 since my phone is the M variant) by itself when the newest Stock ROM had come out a while ago. I still flashed the newest Stock ROM (same MF1 bootloader for the M variant) but the first time I did it I forgot to enter the Stock Recovery to do a Factory Reset and Clear the Cache and ended up stuck on the splash screen of a 4.3 ROM after flashing a custom recovery. So I needed to reflash back to stock and start over.
Going into the Stock Recovery and doing a Factory Reset and Clearing Cache is necessary and doesn't take much time at all so you may as well do it just to be sure. I also recommend backing up your IMEI if you haven't done it yet.
Click to expand...
Click to collapse
This seems to have done the job. Running PAC 4.3 right now. I've rebooted successfully once so far.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

Exactly what I ended up doing after nothing else was working. After getting it hanging the first time, even flashing 4.2 roms was giving me boot issues. After reverting back to stock and reflashing I'm now running the 9/1 Pac nightly and the 8/31 kt747 kernel.
I'm probably 10+ reboots in without issue and I flashed the kernel separately!

bullet2binary said:
This seems to have done the job. Running PAC 4.3 right now. I've rebooted successfully once so far.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
exodus454 said:
Exactly what I ended up doing after nothing else was working. After getting it hanging the first time, even flashing 4.2 roms was giving me boot issues. After reverting back to stock and reflashing I'm now running the 9/1 Pac nightly and the 8/31 kt747 kernel.
I'm probably 10+ reboots in without issue and I flashed the kernel separately!
Click to expand...
Click to collapse
I'm glad to hear that this seems to be the proper fix. That's odd that you were having trouble with 4.2 ROMs, but then again I'd been running 4.2 ROMs on my phone since they first started rolling out. It's kind of annoying that everyone's S3 seems to be slightly different then the next.

Yeah this was a weird one all right. Just glad this post had a solution
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

glad i found this otherwise my first noob post would have truly been a noob move. Thanks wouldn't have guessed that fix for a few days at least.
verified it works. but it did require some weird time dealing with a bootloop issue on stock recoveries. had to find a .tar version of CWM to flash via odin for the final result.

Still Stuck at Splash Screen after trying to upgrade to 4.3
Background:
I had been running task's rom since 4.1.x. Upgraded to 4.2 with not problems and I kept the rom current. Tried to upgrade to 4.3 and that is where the problems started. It appeared to work, saw that Google was updating a number of apps but then then I kept getting error messages regarding various about various processes stopping unexpectedly. Rebooted the phone and it came up with Task's kernel splash screen where it remains frozen.
I can get into TWRP (v2.3.3.1) recovery and into Download mode.
I have tried wiping Cache and Dalvik Cache
I have wiped System
I have done a Factory Reset
I have Formatted Data
I have used Odin twice to get back to stock (I747UCDLK3) and both times it says "passed."
When I try to reboot it, however, it comes back to Task's Kernel splash screen (I do not see the Samsung screen)
Any help or suggestions would be great.
UPDATED: Found an older update from April and was able to restore it. Still wondering why 4.3 wouldn't take.

This Works
I was skeptical, but this actually works! Now running Task's 4.3 on my bell i747m without any problems!
Thanks for the tip OP :good:

spongdangly said:
For those of you who keep getting stuck on the splash screen after trying to restart your phone after installing a 4.3 ROM.
My steps were (and I take no credit for this, I can't remember who had said to do this and I wasn't logged in so I couldn't click the thank you button):
1. Use Odin to flash the latest stock ROM
2. Enter the stock recovery and do a factory reset and clear the cache (I did both twice just to make sure)
3. Use Odin to flash the stock rooted ROM.
4. Enter the stock recovery and do a factory reset and clear the cache. (This might not be necessary but I did anyways just to make sure)
5. Use Odin to flash a custom recovery (TWRP 2.6.0.0 was the newest recovery when I did this last week)
6. Enter the custom recovery and wipe everything, then flash whatever 4.3 based ROM and then flash GApps if you want.
*Note* It seemed like the phone was hanging on the splash screen after either the initial boot or the first restart (I can't remember which, it's been a week) but it did boot and reboot fine.
I hope this helps out some people since I found it to be quite irritating that I could install a 4.3 ROM and set everything up but when I went to restart it would hang at the splash screen (going into the recovery and clearing the cache/dalvik cache wasn't helping).
I hope I posted this in the right section but apologies if it's not.
Click to expand...
Click to collapse
If this works you're a life saver! I've been posting around 4.3 threads about this for weeks and no one came up with a decent answer....
Tried reflashing stock with root but didn't work... i'll try your way, see if that works
Gonna try this tonight!!!
Thanks!

I posted in the CM thread about this, but thought I would pass it along.. I didn't have to go back to stock non-rooted. What I did:
I odin'd Mr. Robinson's LK3 rooted
Factory reset from the 3e recovery
Rebooted
Odin'd twrp
Restored nandroid of CM
Good to go.

Solved
Thanks, also works for i727 skyrocket

wont this brick people phones flashing back 4.1.1 stock ? im on stock 4.3 stuck on samsung galaxy s3 logo meaning flashing back to latest stock rom using odin 4.1.2? 4.3 stock rom or 4.3 custom roms?

Kastro1784 said:
wont this brick people phones flashing back 4.1.1 stock ? im on stock 4.3 stuck on samsung galaxy s3 logo meaning flashing back to latest stock rom using odin 4.1.2? 4.3 stock rom or 4.3 custom roms?
Click to expand...
Click to collapse
spongdangly said:
1. Use Odin to flash the latest stock ROM
Click to expand...
Click to collapse
If you were already on the Stock 4.3 ROM you do not want to flash the 4.0.4, 4.1.1 or 4.1.2 Stock ROM since you will brick your phone.
I'll add a note to the OP about not attempting to downgrade to an older Stock ROM though.

spongdangly said:
If you were already on the Stock 4.3 ROM you do not want to flash the 4.0.4, 4.1.1 or 4.1.2 Stock ROM since you will brick your phone.
I'll add a note to the OP about not attempting to downgrade to an older Stock ROM though.
Click to expand...
Click to collapse
what framware did you flash to get 4.3 back working ? a leaked 4.3 Rom with no root ? thien reflash the stock 4.3 ?

Kastro1784 said:
what framware did you flash to get 4.3 back working ? a leaked 4.3 Rom with no root ? thien reflash the stock 4.3 ?
Click to expand...
Click to collapse
When I had done this back in August, I flashed the Rogers 4.1.2 Stock ROM since that was the latest stock firmware at the time and I have a Canadian S3.
If you had already flashed or been on the Stock AT&T 4.3 ROM, I'd recommend reflashing the latest Stock AT&T 4.3 ROM and following the instructions in the OP. Just make sure that you don't attempt to flash an older version of the Stock ROM that you were already on since you will brick your phone. The Stock ROM contains the bootloader and that cannot be downgraded. I don't have an American S3 since I'm Canadian so I don't know which 4.3 bootloader is the newest although I'm sure a quick search would answer that for you.

spongdangly said:
When I had done this back in August, I flashed the Rogers 4.1.2 Stock ROM since that was the latest stock firmware at the time and I have a Canadian S3.
If you had already flashed or been on the Stock AT&T 4.3 ROM, I'd recommend reflashing the latest Stock AT&T 4.3 ROM and following the instructions in the OP. Just make sure that you don't attempt to flash an older version of the Stock ROM that you were already on since you will brick your phone. The Stock ROM contains the bootloader and that cannot be downgraded. I don't have an American S3 since I'm Canadian so I don't know which 4.3 bootloader is the newest although I'm sure a quick search would answer that for you.
Click to expand...
Click to collapse
There is no latest Stock AT&T 4.3 ROM right now to reflash if you're already on the Stock AT&T 4.3 ROM. We cannot keep telling people this. If so, tell us how, because no one has, as of yet.
I've seen entirely too many posts telling people who are having trouble or phone is soft bricked on the Stock AT&T 4.3 ROM to flash or Odin back to stock. Then when asked how, the discussion ends.
That's also one of the reasons why I refuse to upgrade to 4.3 right now. At least I can still Odin back to stock as an option if something does goes wrong, but who am I to tell anyone to stay away from the latest toy, I mean update?

shortydoggg said:
There is no latest Stock AT&T 4.3 ROM right now to reflash if you're already on the Stock AT&T 4.3 ROM. We cannot keep telling people this. If so, tell us how, because no one has, as of yet.
I've seen entirely too many posts telling people who are having trouble or phone is soft bricked on the Stock AT&T 4.3 ROM to flash or Odin back to stock. Then when asked how, the discussion ends.
That's also one of the reasons why I refuse to upgrade to 4.3 right now. At least I can still Odin back to stock as an option if something does goes wrong, but who am I to tell anyone to stay away from the latest toy, I mean update?
Click to expand...
Click to collapse
I'm sorry that I'm unable to help. As I had mentioned I have a Canadian Rogers phone (since I'm in Canada) so I don't know what's going on with the AT&T Stock 4.3 ROMs other then the fact that lots of people are having problems.
If you never flashed or did an OTA update to 4.3 then I'd suggest flashing the Stock 4.1.2 ROM. That or try what Ozark_8125 did since it saves you a couple steps (just make sure that LK3 isn't an older ROM than the one you were on).
If you're unsure what bootloader is currently on your phone and your phone is rooted I'd highly recommend downloading one of the many Root Check apps from the Play Store to verify which bootloader you're currently on.
*Note* I don't know which bootloader is for the 4.1.2 AT&T ROM nor do I know which bootloader came with the 4.3 ROMs. I'm sure a simple search would answer that for you.
Ozark_8125 said:
I posted in the CM thread about this, but thought I would pass it along.. I didn't have to go back to stock non-rooted. What I did:
I odin'd Mr. Robinson's LK3 rooted
Factory reset from the 3e recovery
Rebooted
Odin'd twrp
Restored nandroid of CM
Good to go.
Click to expand...
Click to collapse

Samsung fixed my phone free thanks for the help
Sent from my SAMSUNG-SGH-I747 using Tapatalk

[Q] Downgrading CM11 to stock 4.3 on i747M

I know there are a few threads regarding this issue but I can't seem to find a definitive answer.
I am currently running stock 4.3 jellybean (rooted). My phone hasn't received the 4.4 KitKat update yet, so I wanted to install CM11 in order to get KitKat on my s3. However, I heard CM11 can be buggy on the s3, so in case things go south, I want to be able to revert back to the stock 4.3 rom. Some people have said that you can easily flash the stock ROM via ODIN. However, others said that downgrading from 4.4.2 to 4.3 will hard brick the device since installing CM11 updates the boot loader. So downgrading to 4.3 stock with a 4.4.2 boot loader will cause a hard brick according to other threads I've seen. My question is, how can I downgrade from CM11 to stock 4.3 safely without bricking? Thanks in advance.

If you are sure you are using a Canadian version of the i747m, you can flash back to stock in Odin using a stock 4.3 ROM for the phone's original carrier (Bell, Rogers, Telus).

audit13 said:
If you are sure you are using a Canadian version of the i747m, you can flash back to stock in Odin using a stock 4.3 ROM for the phone's original carrier (Bell, Rogers, Telus).
Click to expand...
Click to collapse
Yes I got the phone from Rogers, it's most definitely i747M. But do I have to worry about any issues with the bootloader? I'm assuming installing CM11 will install the 4.4.2 bootloader, so if I choose to downgrade to the stock 4.3 rom, will it cause any issues seeing as I'm running a 4.3 rom with a 4.4.2 bootloader? I just want to make sure because I heard it can cause some serious problems if the bootloader is newer than the rom.

Mzrz said:
Yes I got the phone from Rogers, it's most definitely i747M. But do I have to worry about any issues with the bootloader? I'm assuming installing CM11 will install the 4.4.2 bootloader, so if I choose to downgrade to the stock 4.3 rom, will it cause any issues seeing as I'm running a 4.3 rom with a 4.4.2 bootloader? I just want to make sure because I heard it can cause some serious problems if the bootloader is newer than the rom.
Click to expand...
Click to collapse
I have never come across a custom ROM that touches the bootloader. A compatible bootloader has to be loaded on the phone before you attempt to install the custom ROM. Supported bootloaders can be found in the ROM's updater script.
I assume your phone has no warranty since you rooted it on stock 4.3. Did you root it by installing a pre-rooted ROM?
You could copy a ROM to your external SD card, install Philz Touch via Odin, reboot directly to recovery, create a nandroid backup, wipe cache, Dalvik, data, and install your KK ROM.

audit13 said:
I have never come across a custom ROM that touches the bootloader. A compatible bootloader has to be loaded on the phone before you attempt to install the custom ROM. Supported bootloaders can be found in the ROM's updater script.
I assume your phone has no warranty since you rooted it on stock 4.3. Did you root it by installing a pre-rooted ROM?
You could copy a ROM to your external SD card, install Philz Touch via Odin, reboot directly to recovery, create a nandroid backup, wipe cache, Dalvik, data, and install your KK ROM.
Click to expand...
Click to collapse
Okay, I was just making sure because I know OTA updates can change the bootloader, so I just wanted to make sure the custom roms don't do that. As for the custom recovery, are you recommending Philz Touch over CWM and TWRP? Do you know which custom recovery is installed from the CM installer?

audit13 said:
I have never come across a custom ROM that touches the bootloader. A compatible bootloader has to be loaded on the phone before you attempt to install the custom ROM. Supported bootloaders can be found in the ROM's updater script.
I assume your phone has no warranty since you rooted it on stock 4.3. Did you root it by installing a pre-rooted ROM?
You could copy a ROM to your external SD card, install Philz Touch via Odin, reboot directly to recovery, create a nandroid backup, wipe cache, Dalvik, data, and install your KK ROM.
Click to expand...
Click to collapse
Oh and one more question, my phone was originally carrier locked to Rogers and unrooted on 4.3 jelly bean. I brought it in to a cell store for them to carrier unlock it for me, but they used a rooting method to unlock it (because SuperSU was installed on it when I brought it back). They didn't unlock it with a code, so I'm guessing they used something like Samsung Tool or z3x shell. If I install CM11, will I lose the unlock, considering it's more of a "soft unlock", or is the unlock permanent regardless of how many roms I flash? Thanks for your help!

Mzrz said:
Okay, I was just making sure because I know OTA updates can change the bootloader, so I just wanted to make sure the custom roms don't do that. As for the custom recovery, are you recommending Philz Touch over CWM and TWRP? Do you know which custom recovery is installed from the CM installer?
Click to expand...
Click to collapse
Philz is based on the latest release of CWM and I prefer CWM over TWRP because I had problems flashing ROMs. Once I switched to Philz/CWM, no more problems.
Mzrz said:
Oh and one more question, my phone was originally carrier locked to Rogers and unrooted on 4.3 jelly bean. I brought it in to a cell store for them to carrier unlock it for me, but they used a rooting method to unlock it (because SuperSU was installed on it when I brought it back). They didn't unlock it with a code, so I'm guessing they used something like Samsung Tool or z3x shell. If I install CM11, will I lose the unlock, considering it's more of a "soft unlock", or is the unlock permanent regardless of how many roms I flash? Thanks for your help!
Click to expand...
Click to collapse
The unlock should be permanent. I unlocked it using the free method when on 4.1.1 and no ROM has ever caused it to re-lock. Reflashing a completely stock ROM, including the bootloader, did not relock the phone.
Please remember that flashing and changing ROMs will always carry a risk of soft bricking or hard bricking your phone. Make sure you read all of the guides and be prepared for disaster.
Good read here: http://forum.xda-developers.com/showthread.php?t=2201860

Sgh-i747 4.4.2

Hello all. I just received a galaxy s3 from my sister in law running 4.4.2. I am aware I can't downgrade the complete firmware using Odin. The phone it's rooted. My question is what can I do with this thing as far as playing with roms and what not? Can I only install 4.4.2 based roms? Can I even unroot? I have been rooting and installing roms for years now but never have a phone felt more unfriendly before this. Thanks in advance.

Is the phone running stock 4.4.2?
You can install a custom recovery to the phone, copy some custom ROMs to an external SD card, and try out a bunch of ROMs.

Yeah its stock 4.4.2 rooted with clockwork mod recovery. Do the roms have to be 4.4 or 4.4.2 based? Tried cyanogenmod 4.3 and failed. I pretty much would like to flash via odin to go back to stock unrooted but 4.4.2 was over the air. Got 4.3 via sammobile but that fails. Kies won't show my device for firmware recovery. Shows it as normal to sync.

What error did you get when trying to flash CM10.2? Is your CWM up to date?
I would have assumed that CM10.2 would be comaptible with your KK bootloader and modem.
Do not make anymore attempts to flash 4.3 via Odin. This could result in a bricked phone because a KK modem on a 4.3 bootloader cannot be fixed using any method available on XDA.

Yeah I'm aware of the boot loader and modem downgrade issue. Tried odin once and just left it as is.

Is your CWM up to date? What error did you get when trying to flash CM10.2?

I don't remember the error. According to Rom manager, my recovery is up to date

What version is the cwm? I prefer to manually flash a custom recovery instead of relying on ROM manager.

Cwm 6.0.4.7. I've always used rom manager except for my galaxy nexus. Flashed with windows terminal and fastboot.

Since CWM is up to date, try flashing the most recent CM11.

Older cm roms, and any older roms should run fine on NE4. Some may not flash though, such as cm10. This is because the updater script doesn't include NE4 as it wasn't out when the rom was built. If you edit the script to make it flash, any of the available roms should run just fine.
As it stands though, the easiest thing would be to do as audit13 suggested and flash cm11. That and most other recent roms should flash just fine w/o any extra work.
Sent from my SAMSUNG-SGH-I747 using Tapatalk

well, after downloading the most recent cm11 nightly and gapps, rebooted into recovery and wiped. when trying to flash cm11, sd card not mounting. couldn't mount, restored a backup only to be greeted to a display that would not go to sleep and a fury of app and processes stopping pop ups. settings-accounts-backup and reset-factory data reset-etc did nothing but ask for a password. did it through recovery to a perfectly working phone with baseband version: unknown, IMEI: unknown, IMEISV: unknown. flashed the NE4 modem Doc posted in another forum, no dice. same message from cm as before. this time i remember. it was a bunch of basebands not including NE4.

And getprop ro.bootloader says NE4. first said unknown but maybe i typed it wrong.

Got it all back running. tried the S3Rx NE4 aroma zip that would end with installation aborted. found enewman17's post on updating using a stock-rooted 4.4.2 zip after flashing Doc's modem zip. all is well! So thank you DocHoliday77, and thank you enewman17!

Glad you got it working!
Sent from my SAMSUNG-SGH-I747 using Tapatalk

installing revolution HD w/ twrp?

hi guys - so i tried to install the revolution rom on my recently unlocked m9 and it'd only boot to the bootloader or download.
i found some threads back from 2012 that said twrp wouldn't install the rev rom, but suspect it's out of date - it seemed to work fine.
is there some magic here? i tried to flash my firmware to the version matching the rom (3.35.401.12) and got a code 10 failure in adb. my current firmware is 3.10.605.7. doesn't flashing the rom update the firmware too? or do i need to successfully flash the rom prior?
should i use a different recovery? twrp launched the rev aroma installer and all seemed to go perfectly smoothly... no problems came up until reboot brought me right back to bootloader.
the aroma install says it might boot loop a couple times, but i booted to bootloader 5+ times before giving up and going back to a deodexed stock vzw rom.
any help is greatly appreciated - i'm hoping to get up to marshmallow before calling it good enough and moving on.

Flashing the rom doesnt update the firmware. S-on makes sure of that.
You must be on the base firmware for the rom to take. You need the vzw marshmallow ota update before you can flash a marshmallow based rom.
Sent from my HTC One M9 using Tapatalk