I downloaded the stock untouched 10c firmware zip, and the 10c partitions zip and extracted them. I got bin files and I renamed the modem from bin to IMG and bootloader I'm not quite sure which file is it. IIRC its the aboot.bin which I'd rename to IMG.
In twtp I tried flashing just the modem and its asking which partition boot or recovery to flash it. I chose neither cause modem obviously doesn't belong there.
Can I use flashify for the modem IMG and bootloader one? Once I know which one is bootloader?
Or what's the best way? I'm downgrading both since I've heard res-remix 5.4.1 (android 5.1) will let data work with them
Why are you trying to downgrade? 10m had best battery life, 10r was most stable. 20b is both
Related
I have the latest full stock base for the Galaxy Tab Pro 12.2 Wifi (SM-T900) and want to make a bootloader package that can be flashed in ODIN.
Inside of the full stock tar file is:
boot.img
recovery. img
system. img
cache.img
hidden.img
sboot.bin
Which is the bootloader, and what do I need to do to the file, if anything, so that it can be flashed individually in ODIN? Also, should there be a modem file? Alternatively, is it possible to create a zip of these things (bootloader, modem) that's flashable in TWRP?
Thanks in advance for any help.
trav06 said:
I have the latest full stock base for the Galaxy Tab Pro 12.2 Wifi (SM-T900) and want to make a bootloader package that can be flashed in ODIN.
Inside of the full stock tar file is:
boot.img
recovery. img
system. img
cache.img
hidden.img
sboot.bin
Which is the bootloader, and what do I need to do to the file, if anything, so that it can be flashed individually in ODIN? Also, should there be a modem file? Alternatively, is it possible to create a zip of these things (bootloader, modem) that's flashable in TWRP?
Thanks in advance for any help.
Click to expand...
Click to collapse
I'm not quite sure which one is bootloader. Sometimes you can't flash each one individual ly with odin(ex like creating an odin tar that just has system). Modem files are only on lte devices. Most times you don't need them for custom roms. Anyway, you can extract each IMG and create and tar the IMG up. There are a few commands and guides to tar something and add md5 to them.
As for a flash able zip yes and no. Bootloader can't be flashed in twrp most times since I have never seen anything like that. You usually have to flash bootloader with odin. Modems don't need to be flashed since twrp doesn't mess with it most times. But you can create an flash able zip of kernel, recovery and I'm unsure of system.img(may need to extract or adjust updater scipt. Though I dont fully know).
Usually the twrp flashable in ArchiKitchen so it can help with the updater scipt stuffs. Just don't add any options such as root and busybox to it. I've never seen a flashable bootloader in twrp so it's highly unlikely of it being possible.
Hope this helps!
trav06 said:
I have the latest full stock base for the Galaxy Tab Pro 12.2 Wifi (SM-T900) and want to make a bootloader package that can be flashed in ODIN.
Inside of the full stock tar file is:
boot.img
recovery. img
system. img
cache.img
hidden.img
sboot.bin
Which is the bootloader, and what do I need to do to the file, if anything, so that it can be flashed individually in ODIN? Also, should there be a modem file? Alternatively, is it possible to create a zip of these things (bootloader, modem) that's flashable in TWRP?
Thanks in advance for any help.
Click to expand...
Click to collapse
Hi
The bootloader tar package for flashing in ODIN:
1) boot.img
2) sboot.bin
Use 'Total Commander' (google it) to make tar package (bootloader).
Any luck with the port?
shayind4
I know there are threads with instructions about how to do this all over, but they all seem to vary slightly in their instructions and most of the update posts seem to refer to unrooting and flashing stock OTA, then re-rooting, but would this work as it seems like it would be faster and easier. I have soft-bricked my phone more than once and it has been months since I have done this as you can tell by how old my firmware is, so I just want to confirm this will work.
Right now my Zenphone 551ML is on Z00A_WW_2.19.40.22. I would like to update it to Z00A_WW_2.20.40.90. Originally I used fastboot to flash boot.img, droidboot.img, recovery.img, and system.img from (Z00A_WW_2.19.40.22_system_w_root.zip) downloaded from mega.nz/#F!k4MHiAgL!dVuOKeH3eokcwPSNI79ffw.
Can I just perform the same process to update to new firmware by using "fastboot flash...." command to flash all four .img files to my phone, which I downloaded from mega.nz/#F!k4MHiAgL!dVuOKeH3eokcwPSNI79ffw but using the pre-rooted boot.img, droidboot.img, recovery.img, and system.img files from the Z00A_WW_2.20.40.90 folder?
Thanks!
I'm using note 2 stock rom version 4.1.2 baseband DXDLK7 but I flashed DXDLK5 to fix problem about SOS Call only , the problem is when I flash stock rom 4.3 or 4.4.2 I got SOS only problem again and I stuck in 4.1.2 forever . I flashed modem MJ9 but still not work , and all modem download link in this forum died since hotfile server down . All new custom rom such as lolipop and marshmallow require baseband modem XXUFND3 but i can't go to that modem because SOS Call problem . So how can I fix this problem ? Thanks
Make EFS backup and then:
Download firmware from sammobile for your device i.e. N7100.
Install 7zip to extract it and copy SBOOT. and modem, then use 7zip again and pack (*.tar) those files separately, so you will have sboot.tar and modem.tar
sboot is the bootloader and modem is...modem.
Use Odin to flash modem and bootloader in download mode, then use also Odin to flash TWRP.
Then go to recovery mode and install your ROM using instructions in ROM thread (1st post).
You have to know that stock ROMs are identified by letters and numbers, the newest is probably OE1, I used bootloader and modem from French ROM.
yaro666 said:
Make EFS backup and then:
Download firmware from sammobile for your device i.e. N7100.
Install 7zip to extract it and copy SBOOT. and modem, then use 7zip again and pack (*.tar) those files separately, so you will have sboot.tar and modem.tar
sboot is the bootloader and modem is...modem.
Use Odin to flash modem and bootloader in download mode, then use also Odin to flash TWRP.
Then go to recovery mode and install your ROM using instructions in ROM thread (1st post).
You have to know that stock ROMs are identified by letters and numbers, the newest is probably OE1, I used bootloader and modem from French ROM.
Click to expand...
Click to collapse
Thanks , i'll give it a test later , hope it's work
hmmm i can't see sboot file in the .tar rom file , only boot file
Hey guys
So here is my problem.
My GPS is really bad at the moment. I just found out its because it's not the best version of the modem that's inside. 20a instead of 21c.
So I would like to flash it into 21c.
Since my phone is not rooted, is that a pb?
If not, can you guys gimme a hand to flash it?
I downloaded a .zip file with the right version of the modem on a different thread. But what do I do with it?
I tried to follow the "go to recovery" as mentioned but I just don't know where to go.
Therefore can I update to 6.0 without losing all my files? And then switch back the modem from 30B (6.0) to 21C ?
Thanks
My phone is Asus Zenfone 2 (ZE551ML, Z00AD).
As described in another thread, I was unsuccessfully trying to unlock my bootloader. In the process, I also lost the stock recovery.
I learned how to flash stock recovery to repair it.
My firmware version is WW-2.20.40.198. I haven't been able to find the stock recovery file for that exact firmware version. However, I have been able to get a hold of the WW-2.20.40.196 stock recovery file. I was told on XDA-Developers that this would be fine, so I flashed it via Fastboot.
It seems to be working, although I haven't tried to actually flash firmware through adb yet.
I'm now unsure of which firmware to flash through adb, WW-2.20.40.196 or WW-2.20.40.198.
I have two conflicting ideas.
On the one hand:
1. Since the recovery file I flashed with fastboot was 196, then perhaps I should also flash the 196 firmware file?
Or maybe:
2. If I flash the 198 file, perhaps it will also restore the 198 stock recovery? In that case, perhaps I can just flash the 198 firmware?