feed my curiosity if you can:
In theory, transplanting the modem file from a sprint rom to the rom from another variant and flashing a matching kernel would give me a functioning rom for me to use? I have a sprint variant but i'm overseas and do not care about CDMA at all.
I'm doing it later today when i come back from work, but i'd like to confirm if my assumption is correct.
Thank you!
I'm a bit curious too. I guess you won't be able to install it straight due to differences in partitions mapping (partition names and size may differ) but if it happenes to be the same your theory looks reasonable to me.
lorendroll said:
I'm a bit curious too. I guess you won't be able to install it straight due to differences in partitions mapping (partition names and size may differ) but if it happenes to be the same your theory looks reasonable to me.
Click to expand...
Click to collapse
I was able to boot an international variant rom but had no service. flashed the modem using twrp, no dice.
Related
Sorry, I'm new to android. I used to use HTC phones and on HTC creating a gold card allows the flashing of any ROM into the mobile. I used a made a gold card for my atrix2 and I want to flash JB into it. shouldn't the gold card correct the CID problem and aloow so. Should I try it or it might brick my mobile. Thanks.
There are hardware differences that make the Asian firmwares incompatible with the AT&T model. They are 2 different animals just like HTC and Motorola are 2 different animals. I personally wouldn't try it because if it were that easy then I'm sure the devs here (who are not new to android) would've utilized that method by now. That being said, if you are patient there may soon be this:
http://forum.xda-developers.com/showthread.php?t=2103137
Sent from this thing.
1BadWolf said:
There are hardware differences that make the Asian firmwares incompatible with the AT&T model. They are 2 different animals just like HTC and Motorola are 2 different animals. I personally wouldn't try it because if it were that easy then I'm sure the devs here (who are not new to android) would've utilized that method by now. That being said, if you are patient there may soon be this:
http://forum.xda-developers.com/showthread.php?t=2103137
Sent from this thing.
Click to expand...
Click to collapse
I already tried it, but failed due to cbt.bin file failure. good thing I didn't brick my phone. just had a boot problem that is fixed by now. thanks.
essa3eg said:
I already tried it, but failed due to cbt.bin file failure. good thing I didn't brick my phone. just had a boot problem that is fixed by now. thanks.
Click to expand...
Click to collapse
Yeah what you tried was the actual firmware flash.... you cant flash that firmware to an att phone. I had one of the people running the firmware get me a copy of the /system and /boot partitions so that I can "port" that to the att phone as a flashable ROM basically.
Just hang tight and watch that thread that was posted earlier by 1BadWolf, as I will have something in about a week to test out, I think.
Hey all,
I've switched back to Tmo with my Skyrocket and I've flashed T769, T879, T989, and I757M radios to my 727 to find a good balance of reception and speed, and those efforts went OK. The I757M even gives me LTE speeds. Key is in every case there were successful flash reports first. It looks like at a Tmo LTE device the T889 might be a better candidate, but I don't want to brick my phone. Can one of the experts let me know what you think? If I get in a bind am I likely to be able to get back into TWRP recovery to flash another radio? I'd stay on a Skyrocket ROM and kernel as I am now.
Thanks!
Looks like the files within the zip are different (e.g. no amss.bin and modem.bin instead of mdm.bin) so guessing not likely, even with renaming, repackaging, and signing.
And.....it is writing to different blocks. Mod, feel free to close and delete or leave for the archives.
Just wondering about something since it seems the Verizon model seems to be the least popular. Alas, what I was under the impression with the way android works is: I can flash ANY rom thats designed for this specific device (the tab 2 7.0). As long as the radio (Baseband) isn't touched then you should be ok.
Am I correct in those assumptions? Would there be an instance where this wouldn't be the case?
Finally, most Rom packages just include the OS, not the kernel, baseband or anything else, right?
JDMpire said:
Just wondering about something since it seems the Verizon model seems to be the least popular. Alas, what I was under the impression with the way android works is: I can flash ANY rom thats designed for this specific device (the tab 2 7.0). As long as the radio (Baseband) isn't touched then you should be ok.
Am I correct in those assumptions? Would there be an instance where this wouldn't be the case?
Finally, most Rom packages just include the OS, not the kernel, baseband or anything else, right?
Click to expand...
Click to collapse
First, most ROMs flash everything. You wouldn't get a boot if it didn't flash the kernel. With that being said, you can't just flash any ROM from any Tab 2 model. There are many different models, 3113, 3110, 3100, etc.
RikRong said:
First, most ROMs flash everything. You wouldn't get a boot if it didn't flash the kernel. With that being said, you can't just flash any ROM from any Tab 2 model. There are many different models, 3113, 3110, 3100, etc.
Click to expand...
Click to collapse
Ok Im starting to understand: Correct me if I'm wrong though, but to make a device work you need :
Rom = Operating systems & drivers
Kernel = heart of the Android OS.
Bootroom = Allows unit to turn on and start the POST.
Baseband / radio = specific software on for the modem (making calls, data, tower connectivity).
Im I anywhere close here. I always assumed the "ROM" only included just that,.....the rom
JDMpire said:
Ok Im starting to understand: Correct me if I'm wrong though, but to make a device work you need :
Rom = Operating systems & drivers
Kernel = heart of the Android OS.
Bootroom = Allows unit to turn on and start the POST.
Baseband / radio = specific software on for the modem (making calls, data, tower connectivity).
Im I anywhere close here. I always assumed the "ROM" only included just that,.....the rom
Click to expand...
Click to collapse
Usually, the term "ROM" is used in an all encompassing way. You're thinking of the term ROM in a strictly PC based way. For Android, a ROM includes everything. If you DL a ROM zip and and unzip it, you'll see that baseband, boot.img (kernel), OS, etc. are all included in a ROM package.
The ROM is the "heart" of the package. The kernel is what allows the software to work with the hardware. You are right about the baseband, it is the radio "heart."
RikRong said:
Usually, the term "ROM" is used in an all encompassing way. You're thinking of the term ROM in a strictly PC based way. For Android, a ROM includes everything. If you DL a ROM zip and and unzip it, you'll see that baseband, boot.img (kernel), OS, etc. are all included in a ROM package.
The ROM is the "heart" of the package. The kernel is what allows the software to work with the hardware. You are right about the baseband, it is the radio "heart."
Click to expand...
Click to collapse
I supposed that is correct. I only questioned this because I've seen "Rom" threads that have people asking: Does it effect the kernel, does it modify the baseband. In almost all of those cases the resounding answer is NO, no id does not effect those. It only writes to the data partition.
Maybe installs of that nature have a different name or category for them, this i am not sure.
JDMpire said:
I supposed that is correct. I only questioned this because I've seen "Rom" threads that have people asking: Does it effect the kernel, does it modify the baseband. In almost all of those cases the resounding answer is NO, no id does not effect those. It only writes to the data partition.
Maybe installs of that nature have a different name or category for them, this i am not sure.
Click to expand...
Click to collapse
Most ROMs use the same baseband of the latest update for that device. Also, many use a stock based kernel. So, in that way, it really doesn't affect the baseband or kernel.
Exactly as the title asks.
I'm trying my A536W bootloader-unlocking guide myself since there weren't any volunteers, and the A536B BTB firmware keeps giving me "FAIL" in ODIN regardless of whether I use PatcheD/original and no matter what version I try with. I tried with binary 4 (which is matching with my phone's current software) and binary 5, but neither seem to work. Doesn't matter whether I pick CSC or HOME_CSC, either, unfortunately.
The only option left that I can think of would be to re-partition and erase NAND while flashing the A536B's firmware along with its extracted PIT file. Anybody have any suggestions or warnings or anything? All help will be greatly appreciated.
OrthodoxOxygen said:
Exactly as the title asks.
I'm trying my A536W bootloader-unlocking guide myself since there weren't any volunteers, and the A536B BTB firmware keeps giving me "FAIL" in ODIN regardless of whether I use PatcheD/original and no matter what version I try with. I tried with binary 4 (which is matching with my phone's current software) and binary 5, but neither seem to work. Doesn't matter whether I pick CSC or HOME_CSC, either, unfortunately.
The only option left that I can think of would be to re-partition and erase NAND while flashing the A536B's firmware along with its extracted PIT file. Anybody have any suggestions or warnings or anything? All help will be greatly appreciated.
Click to expand...
Click to collapse
of course it hardbricks
TringQuack said:
of course it hardbricks
Click to expand...
Click to collapse
I looked around online and some people seem to have done it and gotten away with a softbrick, though. I've found that even guides only mention a softbrick as the worst that can happen. Are you certain that it will hardbrick? Or are you speculating? I don't mean to doubt you: I just want to try what I can to unlock the A536W, and if this could be a method with a softbrick being the worst-case scenario, then I'd like to try it at some point
A PIT flash from 536E to 536B was my only remaining option for converting the phone (which are completely identical). Just like you, i needed confirmation that it was done or that it works, except for a dude here who shadily said "it works", i havent found any information at all that it would.
My two cents would be to leave it and make peace, not worth the risk. In case you do, let us know though.
PS, i think the Patched Odin would be needed here as well.
PlutoDelic said:
A PIT flash from 536E to 536B was my only remaining option for converting the phone (which are completely identical). Just like you, i needed confirmation that it was done or that it works, except for a dude here who shadily said "it works", i havent found any information at all that it would.
My two cents would be to leave it and make peace, not worth the risk. In case you do, let us know though.
PS, i think the Patched Odin would be needed here as well.
Click to expand...
Click to collapse
I did try it out, and it didn't work: patched or unpatched, ODIN wouldn't send it through and would either hang or return with some sort of error message. Unfortunately, I couldn't find a way to force it, either. Even NAND erase and re-partitioning wouldn't work in giving me some headway. I tried Frankenstein-ing different firmware files (even AP and BL from Bmodel while CP and CSC from Wmodel) and PITs, but still no dice. Even tried to flash the Korean version, which is identical spec-wise to the Wmodel besides bands (Bmodel differs in that it has dualSIM), but it still didn't work, sadly. Also tried the same binary-number (4) or going to 5. Still wouldn't budge. Seems my phone will literally only accept the firmware it was designed for, which sucks.
I appreciate your suggestions, though! If you have any ideas as to what else I should try, let me know, please! Maybe I have to change CSC to match whatever firmware I'm flashing first? But that's the job of the CSC file itself, right? Maybe it was just a wild goose-chase, but I hope something's figured out soon
Honestly you had the guts to try more than i would, so nothing i can add. I thought first that my E variant was failing because it's an 8GB variant, but that wouldn't really be logical. Samsung made them unswitchable.
Cant think of an idea except messaging the SamFirm tool guys if they could make it happen somehow, but some of us are keen to keeping the KNOX depending services in tact.
PlutoDelic said:
Honestly you had the guts to try more than i would, so nothing i can add. I thought first that my E variant was failing because it's an 8GB variant, but that wouldn't really be logical. Samsung made them unswitchable.
Cant think of an idea except messaging the SamFirm tool guys if they could make it happen somehow, but some of us are keen to keeping the KNOX depending services in tact.
Click to expand...
Click to collapse
Still, I appreciate the sentiment! It was a bit nerve-wracking, but I had a feeling it'd end up alright (which I'm quite glad was correct considering how much this phone costed me). Who're the "SamFirm Tool Guys"? Is there a way I can get in contact with them? Maybe if we can work out a method that removes KNOX, somebody like-minded will find a method that keeps those services?
OrthodoxOxygen said:
Who're the "SamFirm Tool Guys"? Is there a way I can get in contact with them?
Click to expand...
Click to collapse
I meant this one sorry. They managed to pull that CSC change when all the other apps are asking for money, and a lot easier too.
They look like the only bunch capable of doing it, but i highly doubt there's demand for it.
PlutoDelic said:
I meant this one sorry. They managed to pull that CSC change when all the other apps are asking for money, and a lot easier too.
They look like the only bunch capable of doing it, but i highly doubt there's demand for it.
Click to expand...
Click to collapse
Got it! I'll look around and maybe try to reflash but with a CSC change first when I have the time to mess around again. I'll also try contacting them. Maybe they've already cracked a similar situation and we've just gotta apply it to our device? Or perhaps it's a lot easier than we think it is and the solution's been right under our noses? I hope so, at least. Thanks again. It's much appreciated
I have an RFinder B1+(14) that works fantastic, it has the 6567 chipset. I also have an RFinder B1 Classic with a 6563 chipset that will not boot into Android 8 on the way, and the ROM has not been easy to find.
I suspect they are NOT compatible, but if I did flash the older radio with newer firmware, I'd be able to reverse the damage as long as I didn't overwrite the preloader.
If the two are, in fact, compatible, it would save me some time.
Are they compatible?
N
shadow460 said:
I have an RFinder B1+(14) that works fantastic, it has the 6567 chipset. I also have an RFinder B1 Classic with a 6563 chipset that will not boot into Android 8 on the way, and the ROM has not been easy to find.
I suspect they are NOT compatible, but if I did flash the older radio with newer firmware, I'd be able to reverse the damage as long as I didn't overwrite the preloader.
If the two are, in fact, compatible, it would save me some time.
Are they compatible?
Click to expand...
Click to collapse
Not without porting them from one to the other, "IF" the sources to do so are available(either stock firmware for the two devices or at least the stock source code for the device the ROM will be flashed on.
I have tried without success to compile software. Of course it can be done, I just haven't got the hang of it (I need to learn though).
If there are other things I can do, learn, etc from this thread, I'm all ears. If not, thank you for the info.
shadow460 said:
I have tried without success to compile software. Of course it can be done, I just haven't got the hang of it (I need to learn though).
If there are other things I can do, learn, etc from this thread, I'm all ears. If not, thank you for the info.
Click to expand...
Click to collapse
There really isn't a 100% all in one get it right the first time guide out there. There are lots of guides that give a general idea of how to port stock ROMs but it will still require trial and error to iron out the details. Do some research to see if there are any specific security features preventing the ported ROM from flashing/booting then see if there are any tricks to bypass those specific features. You may need to unlock the bootloader and dig into trying to modify the bootloader.img located in the copy of your devices currently installed stock firmware file(or the last "official" firmware that was installed on your device before you tried to modify it).