Related
My Mesmerize flashed Fascinate's ROM, no signal after factory data reset. What Where can I download the contents of this post and look forward to your answer.
Address the original post：http://forum.xda-developers.com/archive/index.php/t-844886.html
qq25 said:
My Mesmerize flashed Fascinate's ROM, no signal after restore factory settings. What Where can I download the contents of this post and look forward to your answer.
Address the original post：http://forum.xda-developers.com/archive/index.php/t-844886.html
Click to expand...
Click to collapse
if i am understanding correctly you wanna get back to stock MEZ..
If that is so .. http://forum.xda-developers.com/showthread.php?t=881064
i have flashed this rom,Still no signal。Maybe need to refresh CWMrecovery.tar or radio?
qq25 said:
i have flashed this rom,Still no signal。Maybe need to refresh CWMrecovery.tar or radio?
Click to expand...
Click to collapse
That's not a ROM. What you flashed was the Fascinate's full system files. Although some people have had luck doing it, this is a prime example of why you should never flash something that isn't for your phone. If you have flashed the Mesmerize files using Odin to get back to stock and your phone still isn't working. Try using Odin to flash them again. If you still aren't back to a working phone, my guess is that something was flashed incorrectly to begin with.
I hope that you have phone replacement or insurance available if it doesn't work.
What happened is he has a Verizon radio. You need to use ODIN (as phidelt82 said) to flash your device back to a true stock state. This should restore your USCC radio..
So a couple of quick questions.
One (and im asking this because including my og droid i haven't not been rooted in two years) if i return to stock (i.e verizon may replace my tbolt) will it also automatically return my kernel to stock. The only reason i ask is i just did a full data and cache wipe for a new rom and my new adrenaline kernel was still there, which is fine for now but not if i have to take it in.
Second: if it doesnt return to a stock kernel is there a boot.img or even a .zip that will work on clockwork for it.
I did try searching, and i do know how to unroot, I just dont know about the kernel issue once i do unroot.
edit: i did do my own full root, bloatware removed, stock kernel backup before i flashed the kernel, so as long as restoring that backup reverts it to the original kernel that is fine also.
if you use a RUU to return to stock....everything is back to stock including the kernel
magneticzero said:
if you use a RUU to return to stock....everything is back to stock including the kernel
Click to expand...
Click to collapse
thanks i figured that was the case just wanted to make sure.
question answered: so unless someone needs help with this have a good one.
http://forum.xda-developers.com/showthread.php?t=975888
if you use that RUU(out of the box state rom) it will remove root and return everything back to 'normal' so you could return/warranty exchange it
magneticzero said:
http://forum.xda-developers.com/showthread.php?t=975888
if you use that RUU(out of the box state rom) it will remove root and return everything back to 'normal' so you could return/warranty exchange it
Click to expand...
Click to collapse
yeah i found the unroot instructions here http://forum.xda-developers.com/showthread.php?t=1009423 if anyone else needs them and it has the link to the ruu. I just wanted to make sure it did return it. so all is good.
For what it's worth, my son returned a rooted Droid running CM7 because it had a bad camera, he did a mail exchange and never heard a word about it from Verizon. I'm sure the first thing they do with a returned phone is burn a stock image into it even before they "test" it. Think about it, they can't possibly have someone do a forensic examination of the software on returned phones. I think the main way they have of finding modded phones are due to people admitting that they modded it. Just sayin'.
If you make a backup in CWR (Rom Manager) before flashing a new kernel then you can roll back and restore the old configuration... including kernel.
You can also flash the stock kernel from Rom Manager.
No need to RUU unless it is absolutely needed. But this will cause a lot of extra work (need to re-root, etc)
bmcclure937 said:
If you make a backup in CWR (Rom Manager) before flashing a new kernel then you can roll back and restore the old configuration... including kernel.
You can also flash the stock kernel from Rom Manager.
No need to RUU unless it is absolutely needed. But this will cause a lot of extra work (need to re-root, etc)
Click to expand...
Click to collapse
Yea but the OP wanted to know in case they had to return/exchange the phone for whatever reason....
Any way to get a copy of the stock kernal only. Would just like to have it around. Im rooted and running the stock rom with the phone and Adrynalynes 1.9 kernal...
Thanks in advance
magneticzero said:
Yea but the OP wanted to know in case they had to return/exchange the phone for whatever reason....
Click to expand...
Click to collapse
Ah. My bad... then RUU would be the best method!
Jrocker23 said:
Any way to get a copy of the stock kernal only. Would just like to have it around. Im rooted and running the stock rom with the phone and Adrynalynes 1.9 kernal...
Thanks in advance
Click to expand...
Click to collapse
bump? also looking to go back to stock kernel, without unrooting...
i just wanted this all in one place.i wanted my daily driver to be torch or fusion cause of call quality but also want to play around on gb roms.i found a safe way to go back and forth.if something happens to your phone i'm not responsible this is what works for me.
1.flash gb stock just like it says here:http://forum.xda-developers.com/showthread.php?t=1045734
2.i wanted mosaic on to play around with so i flashed mosaic.now from mosaic( I have only tried mosaic so far) you can flash back to 2.2 or 2.1 rom that has NO secondary bootloaders(this is very important).and you have to be on http://forum.xda-developers.com/showthread.php?t=1042543 the kernel from here in order for this to work cause it uses cwm 2.5 still.
3.make sure you wipe data/factory reset and also wipe cache partition and dalvik cache in between flashing roms.
4.if on talon kernel you cant flash from 2.3 to 2.2 cause it uses cwm 3.0.so you need to get kernel flasher from market and the this file http://etc.muteheadlight.net/android/I9000_reoriented_vG.1.1_novoo.tar and flash it from kernel flasher it will put you back on cwm 2.5 and you can go back to 2.2 from there.
this has worked for me several times today i wanted to make sure it worked go and thank all the devs on there respected paged.they work hard on all this development show some appreciation.
again dont mix boot loaders make sure the rom you are flashing does not flash boot loaders.just stay on gb boot loaders.as it is stated you will brick your phone mixing boot loaders.
I hope this helps some people out and explains it good enough.
I just use odin one click to flash back to stock then flash by froyo rom of choice.
To Gingerbread from 2.1 bootloaders:
odin flash bootloader and reorient kernel package HERE (7mb)
odin flash talon or other kernel with CWM3 built in
boot into CWM3
CWM3 flash GB wipe rom!
Back to Eclair/Froyo: (keeping GB booties)
Odin flash a Kernel with CWM2.5 built in (onix)
boot into CWM2
CWM2 flash 2.1 or 2.2 wipe rom.
------AVOID ROMS WITH SBL (secondary boot loader) LIKE A PLAGUE!!! or built-in 3 button fix!----- YOU WILL BRICK!!
****To not worry about mixing Bootloaders or the SBL on Eclair/Froyo roms flash odin-one-click to get stock booties before Odin flashing a Cwm2.5 kernel.
Easy Peasy Lemon Squeezy
i also use odin one-click to get back to stock
Fezz102 you have successfully flashed between GB and Froyo and only used odin to flash the initial boot loaders and rom after that you just swapped kernels with sgs kernel flasher and haven't had a single issue? And you haven't used odin again?
Sent from my SAMSUNG-SGH-I897
Why is everyone so afraid of odin? AS LONG AS IT DOESN'T HANG ON BOOT.BIN OR SBL.BIN YOU CANNOT BRICK. PERIOD.
Kernels don't have bootloaders AT ALL using odin to flash a kernel is recommended by all the kernel devs, they have stated the app is actually more likely to cause improper writes than odin.
studacris said:
Why is everyone so afraid of odin? AS LONG AS IT DOESN'T HANG ON BOOT.BIN OR SBL.BIN YOU CANNOT BRICK. PERIOD.
Kernels don't have bootloaders AT ALL using odin to flash a kernel is recommended by all the kernel devs, they have stated the app is actually more likely to cause improper writes than odin.
Click to expand...
Click to collapse
I'm on a mac I have a pc around but I swear if you saw it you'd be a little nervous to it's a cheap old lap top running xp it doesn't even have a battery, I'd be fine with odin if I had faith in my pc. That being said don't mention heimdall it doesn't recognize 2.1 bootloaders so in order to move up I still need odin.
Sent from my SAMSUNG-SGH-I897
heimdall doesnt recognize 2.1 bootloaders? really?
how was it created with 2.1 bootloaders before the 2.3 ones ever existed??
thats news to me.... learn somethin new every day...
*sarcasm*
This an interesting post from the guys that wrote heimdall the first is a list of confirmed devices that work with heimdall the eighth post is a list of confirmed working bootloaders and osx compatability i9000 this should give you an idea of what I'm talking about. Out of ten only two support osx. As far as the i897 is concerned if you ever flashed your phone with odin 1click and I have the boot loaders included do not support osx. THAT'D be a fact . *touchee*
Sent from my SAMSUNG-SGH-I897
Here's the linkhttp://forum.xda-developers.com/showthread.php?t=891518
Sent from my SAMSUNG-SGH-I897
1tontomato said:
Fezz102 you have successfully flashed between GB and Froyo and only used odin to flash the initial boot loaders and rom after that you just swapped kernels with sgs kernel flasher and haven't had a single issue? And you haven't used odin again?
Sent from my SAMSUNG-SGH-I897
Click to expand...
Click to collapse
no problems so far.just wipe everything and factory reset clear data in recovery the key there is to be in cwm2.5 and not 3.0. and to never flash anything with secondary bootloaders.
Hey if Im currently on a JVH ROM, and want to try out the Galaxy Sense i9000, but the whole deal about the bootloaders is a little irrating. And its even trickier for me to go back to stock considering I have a build 1010, thus One Click soft bricks my phone (*I have a jig*). But it really isnt a big deal because I use the JH2 method and iCezars method for flashing back without risk, without replacing the bootloaders. Those are the two methods I have had to flash back to stock while on a Gingerbread ROM.
But my question lies in whether I can flash back to stock using one of the two methods I stated above which DO NOT FLASH BOOTLOADERS and follow the instructions in the Sense i9000 thread (This isnt a how to, to flash, because from December--February all I did was flash MIUI and CM7), but rather do you know if I could flash with GB bootloaders or would it be too big of a mess?
And if I cant can someone point me into a direction of a .tar file that contains BOTH BOOTLOADERS such as Odin One Click but I have to use Odin 3 and manually put it in and flash.
Thanks!
Just use odin one click, yes it will soft brick you, no it's not s big deal you have a jig, after that soft brick use your jig, and icezar's packages liked you usually do. Bam stock with original bootloaders. That is your only option. Nothing else contains both bootloaders.
studacris said:
Just use odin one click, yes it will soft brick you, no it's not s big deal you have a jig, after that soft brick use your jig, and icezar's packages liked you usually do. Bam stock with original bootloaders. That is your only option. Nothing else contains both bootloaders.
Click to expand...
Click to collapse
Hmm.. I was seriously thinking that but I was worried that it would completely brick the phone because it does flash both bootloaders thus completely bricking the phone.
If I knew I could just Jig it back like ive had to do twice when I used Odin One Click Id use the JH2 package or Cezars and be good.
But since im playing with bootloaders Im worried that it will completely brick cause One Click doesnt even work on my phone.
it only completly bricks the phone if it DOESN'T flash both boot loaders!
what happens when you use one click? a soft brick right? if you get ANY activity out of you phone at all your bootloaders are intact. and your jig will work for download mode after that then you can fix the soft brick by using the .tar package you usually use.
nothing but odin one click will flash both stock bootloaders
studacris said:
it only completly bricks the phone if it DOESN'T flash both boot loaders!
what happens when you use one click? a soft brick right? if you get ANY activity out of you phone at all your bootloaders are intact. and your jig will work for download mode after that then you can fix the soft brick by using the .tar package you usually use.
nothing but odin one click will flash both stock bootloaders
Click to expand...
Click to collapse
yes I know that im not trying to argue you with you... hahah
Im just saying that I dont know Im just a little hesitant as I havent used Odin One Click in a while, plus the fact that it'll be twice the nerve racking coming from Gingerbread Bootloaders.
That is the one thing that is a little scary, but I know if anything flashes on to the screen im good to go, but just a little nervous, but am seriously considering just using the Odin One Click, and just praying that it at least flashes the AT&T screen then off like it normally does.
But I dont know if it'll work the same with GB, I know its mostly in my head but hahahaha
EDIT: I havent used One Click in a while should I wipe my phone before? And secondly I assume disabling lagfix?
FLASHED ONE CLICK.... Going now I will keep it posted when I get back to stock.
the bootloaders though flash went well so I think im in the clear. Lets hope : D
UPDATE: It soft bricked, Jig--> now on Stock.
THANKS SO MUCH!
No problem man.
TRUST THE ZOMBIE!!
Well, you started the topic, so...
I have gone back and forth one cycle now. GR-10, then Odin one-click to ancient stock, (no master clear), reboot recovery by reinstalling packages (update.zip still there), flash Serendipity 6 (rom cwm still on the phone), then restore from my Nandroid backup, and update calls, texts, and some apps. Takes maybe 30 minutes. On continuum now, since it's the only JVH rom.
I'm wondering if I can skip a step. They say the GB bootloaders are fine with Froyo. If so, I should be able to go download mode, flash Onix in Odin (no auto reboot - since the kernel and rom will be incompatible), then pull the battery, boot to recovery by holding volume-up/power, and simply load the old nandroid backup (since I would have the same kernel - Onix - and same modem - JQ1 - as I had when I created the backup). The backup contains the Dalvik cache, IIRC, so I wouldn't even have to clear that. That's about 5 minutes, plus the time it takes to restore newer messages, apps, etc - maybe 15 minutes total.
Does anyone know why this wouldn't work in theory?
Soccer_Dad said:
Well, you started the topic, so...
I have gone back and forth one cycle now. GR-10, then Odin one-click to ancient stock, (no master clear), reboot recovery by reinstalling packages (update.zip still there), flash Serendipity 6 (rom cwm still on the phone), then restore from my Nandroid backup, and update calls, texts, and some apps. Takes maybe 30 minutes. On continuum now, since it's the only JVH rom.
I'm wondering if I can skip a step. They say the GB bootloaders are fine with Froyo. If so, I should be able to go download mode, flash Onix in Odin (no auto reboot - since the kernel and rom will be incompatible), then pull the battery, boot to recovery by holding volume-up/power, and simply load the old nandroid backup (since I would have the same kernel - Onix - and same modem - JQ1 - as I had when I created the backup). The backup contains the Dalvik cache, IIRC, so I wouldn't even have to clear that. That's about 5 minutes, plus the time it takes to restore newer messages, apps, etc - maybe 15 minutes total.
Does anyone know why this wouldn't work in theory?
Click to expand...
Click to collapse
please read post 3
i wrote it. i know its there..
I just flashed the one click ics leak. it worked okay, but it wasnt stable enough for me. So i want to go back to Gingerbread and wait for the official release. Im new to this rooting stuff. This was actually my first time doing it. So if someone could give me step by step directions ide greatly appreciate it. Im not stupid but i am new. I tried one way on getting back to stock http://forum.xda-developers.com/showthread.php?t=1342348 it worked but it wouldnt let me update to 3.6 for one and two it tripped my flash counter !!!! so now im screwed on my warranty. Look, all i want is to go back to stock. please help me guys. Step by step and links please. thanks.
Did you Odin the original recovery? Or do you still have CWM? If you still have CWM you can use the file from this link to reset your flash counter. http://forum.xda-developers.com/showthread.php?t=1575712
Sent from my SAMSUNG-SGH-I727 using XDA
The only thing i know hoe to do it pull up odin, put the tar file in pda and hit start. But i used the one click thigh for the ics i flashed. The one click is different then odin. But does anyone have just a stock file? Like completely stock like nothing ever happened? When i get back to stock or if i get back to stock cant i just recover my back-up? lol plz and thank you guys
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
This is what happens when you don't read and just start flashing away with the first thing you can find. I wanna help, but I almost feel like I shouldn't. I mean, if you just read the stickies you would know how to fix this.
If u look through the threads I believe Konane has a thread for returning to stock..but there is a way..not sure of the exact step order but using Odin flash stock tar file then the reset flash count...then the stock recovery..I'll look to see if I can find a link.
Sent from my ICE Cream Sammy Skyrocket-I727 using xda premium
Under skyrocket Development under stickies Its KOnane return to stock
Sent from my SAMSUNG-SGH-I727 using xda premium
what?
i didnt start flashing away. i backed out of rooting 5 times before i did it because i COMPLETLY sure on what i was doing. and i already did the konan tutorial and yes it does work. but it wont let you get at&t updates. and thats a big problem. from what i was reading about konan's tar is that it wasnt a official stock gingerbread. i went to sammobile to get the official stock file. and i did but the file is in MD5 format and i wasnt sure if i could just put that in odin under pda and go about or not. you guys know? but i DID do sooo much reading and researching before i rooted. thanks guys i really appreciate it. you have no idea
feelinfroggy23 said:
i didnt start flashing away. i backed out of rooting 5 times before i did it because i COMPLETLY sure on what i was doing. and i already did the konan tutorial and yes it does work. but it wont let you get at&t updates. and thats a big problem. from what i was reading about konan's tar is that it wasnt a official stock gingerbread. i went to sammobile to get the official stock file. and i did but the file is in MD5 format and i wasnt sure if i could just put that in odin under pda and go about or not. you guys know? but i DID do sooo much reading and researching before i rooted. thanks guys i really appreciate it. you have no idea
Click to expand...
Click to collapse
Yes you can, sammobile is complete. Just extract from the zip and flash in odin
I had to install cwm to my device after flashing back to stock and flash the uckk1 radio and use the reset flash counter zip. Then I flashed stock cwm in Odin rebooted and was able to receive the update to 2.3.6. Which breaks wallpaper scrolling. My only grip about it.
Just flash the stock radio that will solve your problem of not receiving ota updates.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
read this http://forum.xda-developers.com/showthread.php?t=1652398, it will tell u had to restore to stock and might reset ur counter, if counter is not reset there is a fix for that too now
So like the title says I have been out of the ROM game for a little bit. Every couple of months I check in and see whats new and flash something else.
I was on the Jelly Beans ROM (Build 16 I think) and Android 4.1. I did some searching last night as was going to try flashing Gummy ROM…bad idea. I am guessing I needed something prior to jumping up to a 4.4 base. I booted to recovery and wiped everything and tried to flash with no luck. So the phone would not boot and I could only get into recovery and download mode. I did not have my micro SD adapter in order to get jelly beans back on it to flash so I ended up having to use odin to flash a stock rooted 4.1 image. Finally got everything back up and running but I still want to try some of the 4.4 ROMs. So what exactly do I need first in order to flash one? (Modem maybe)…if you know for sure why that happened and what I need to do please let me know. Thanks!
My Current "About Phone" Info...
Android Version - 4.1.2
Baseband version - I535VRBMB1
Jelly Beans - Build 20
P.S. I have tried doing the research and nothing I have found has been clear but one thing I came across is the official 4.3 update was bad news and broke the root methods? So should I stay away from 4.3 ROMs and is the old root method blocked in 4.4 as well or is that a different case since it wasn't actually released for our phone. If that makes sense lol
aholeinthewor1d said:
So like the title says I have been out of the ROM game for a little bit. Every couple of months I check in and see whats new and flash something else.
I was on the Jelly Beans ROM (Build 16 I think) and Android 4.1. I did some searching last night as was going to try flashing Gummy ROM…bad idea. I am guessing I needed something prior to jumping up to a 4.4 base. I booted to recovery and wiped everything and tried to flash with no luck. So the phone would not boot and I could only get into recovery and download mode. I did not have my micro SD adapter in order to get jelly beans back on it to flash so I ended up having to use odin to flash a stock rooted 4.1 image. Finally got everything back up and running but I still want to try some of the 4.4 ROMs. So what exactly do I need first in order to flash one? (Modem maybe)…if you know for sure why that happened and what I need to do please let me know. Thanks!
P.S. I have tried doing the research and nothing I have found has been clear but one thing I came across is the official 4.3 update was bad news and broke the root methods? So should I stay away from 4.3 ROMs and is the old root method blocked in 4.4 as well or is that a different case since it wasn't actually released for our phone. If that makes sense lol
Click to expand...
Click to collapse
Can't tell you exactly why that happened, but it shouldve worked.
You're right though, stay away from the stock Ota 4.3 update. I'm happy you read first because so many people don't. My guess is your firmware was a little too old. Try to flash the mf1 firmware aio and then try gummy.
To be clear, you can still use any custom rom, even the 4.3 ones, just stay away from the stock rom or anything having to do with 4.3 ML1 firmware
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
Can't tell you exactly why that happened, but it shouldve worked.
You're right though, stay away from the stock Ota 4.3 update. I'm happy you read first because so many people don't. My guess is your firmware was a little too old. Try to flash the mf1 firmware aio and then try gummy.
To be clear, you can still use any custom rom, even the 4.3 ones, just stay away from the stock rom or anything having to do with 4.3 ML1 firmware
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the quick reply. What do you mean try to flash the MF1 firmware...does that mean a 4.2 ROM?
I think I saw the new jellyBeans/alliance ROM was 4.3...or maybe it was something else..either way it would be ok to flash the 4.3 ROM? and if I wanted I could go back to a 4.1 Rom then..
aholeinthewor1d said:
Thanks for the quick reply. What do you mean try to flash the MF1 firmware...does that mean a 4.2 ROM?
I think I saw the new jellyBeans/alliance ROM was 4.3...or maybe it was something else..either way it would be ok to flash the 4.3 ROM? and if I wanted I could go back to a 4.1 Rom then..
Click to expand...
Click to collapse
Yes you can interchange between both of them if you want to.
So go here, read all of the details, and just follow his recommendation:
http://forum.xda-developers.com/showthread.php?t=1788313
Also don't double post, modify your post in the development section and put "wrong section, mod please delete".
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
Yes you can interchange between both of them if you want to.
So go here, read all of the details, and just follow his recommendation:
http://forum.xda-developers.com/showthread.php?t=1788313
Also don't double post, modify your post in the development section and put "wrong section, mod please delete".
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
The reason I have so confused is cause of the link you sent. I read that before and it says..
"You should NOT flash the I535VRUCML1 firmware (or any subsequent releases for that matter). You will brick. This is what vzw/samsung did on the first OTA for the Galaxy S4. They changed the keys they sign the firmware with. This prevents us from 'mis-matching' our firmware like we've been doing all along. We've been leaving aboot (VRUAME6, the african-canadian sock-monkey leaked bootloader) alone and updating everything else. Since they're signing with different keys now, doing this will brick your device. If you update the ENTIRE bootchain (including aboot) you shouldn't brick, but will be stuck with a locked bootloader and any attempt to downgrade (via dd, etc) will brick you as well."
Like i said I have been out for a while and lost track of what firmwares came out and the order of them and which I need to be on to flash a 4.4 ROM. Someone else told me the only reason my first flash failed was because my recovery was older
***EDIT****
Ignore that entire thing I just realized you said to stay away from ML1 and that MF1 is ok..opps
aholeinthewor1d said:
The reason I have so confused is cause of the link you sent. I read that before and it says..
"You should NOT flash the I535VRUCML1 firmware (or any subsequent releases for that matter). You will brick. This is what vzw/samsung did on the first OTA for the Galaxy S4. They changed the keys they sign the firmware with. This prevents us from 'mis-matching' our firmware like we've been doing all along. We've been leaving aboot (VRUAME6, the african-canadian sock-monkey leaked bootloader) alone and updating everything else. Since they're signing with different keys now, doing this will brick your device. If you update the ENTIRE bootchain (including aboot) you shouldn't brick, but will be stuck with a locked bootloader and any attempt to downgrade (via dd, etc) will brick you as well."
Like i said I have been out for a while and lost track of what firmwares came out and the order of them and which I need to be on to flash a 4.4 ROM. Someone else told me the only reason my first flash failed was because my recovery was older
Click to expand...
Click to collapse
I see, that actually makes perfect sense.
I think I read you were on the mb1 firmware, that's new enough to not cause problems.
Basically you can't get the ml1 firmware from that thread I linked you. The only ml1 file available is the modem, and that's perfectly safe to flash.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
I see, that actually makes perfect sense.
I think I read you were on the mb1 firmware, that's new enough to not cause problems.
Basically you can't get the ml1 firmware from that thread I linked you. The only ml1 file available is the modem, and that's perfectly safe to flash.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I think I am getting it... I am on MB1...next was MF1....and then ML1. As long as I have a new recovery I can flash any MF1 based ROM right over MB1...and then I can flash the ML1 modem ONLY. If that is correct let me know..also does it matter if I do MF1 ROM or ML1 modem first?
again just wanted to say thanks for the help I appreciate it
aholeinthewor1d said:
I think I am getting it... I am on MB1...next was MF1....and then ML1. As long as I have a new recovery I can flash any MF1 based ROM right over MB1...and then I can flash the ML1 modem ONLY. If that is correct let me know..also does it matter if I do MF1 ROM or ML1 modem first?
again just wanted to say thanks for the help I appreciate it
Click to expand...
Click to collapse
You're close, firmware is completely independent from rom. You can flash any 4.3, 4.4, or 4.1 rom without changing your firmware.
Right now you can flash mf1 aio package, then ml1 modem, or just flash the ml1 modem over your current mb1 firmware.
Basically you aren't required to be on a specific rom build in order to use a specific modem.
Edit: I think you have the right idea, flash any rom you want, then the mf1 aio package, then the ml1 modem. Your firmware sequence is correct.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
You're close, firmware is completely independent from rom. You can flash any 4.3, 4.4, or 4.1 rom without changing your firmware.
Right now you can flash mf1 aio package, then ml1 modem, or just flash the ml1 modem over your current mb1 firmware.
Basically you aren't required to be on a specific rom build in order to use a specific modem.
Edit: I think you have the right idea, flash any rom you want, then the mf1 aio package, then the ml1 modem. Your firmware sequence is correct.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
ah ok...idk why I was thinking the firmware was what the ROMs were based from....so either way ML1 firmware sucks and I stay away...I guess my last questions are...what would be an advantage of going to the MF1 firmware...
and I always used clockworkmod recovery...do you know the option available now? and maybe some features of each