Related
I accidentally uninstalled Touchwiz using Titanium Backup. Since I already use ADW.Launcher, I thought its not a big deal, until I did a hard reset.
Upon hard reset, my Galaxy S tries to install Touchwiz, which of course fails, and the darn phone just crashes and hangs. I managed to get it to boot up eventually after some trouble, but I'll prefer not to have to do this everytime I hard reset.
Can someone please please send me the TouchWiz apk and odex files so that I can put them back in the system directory ? I'm using stock Froyo 2.2 ( Build FROYO.DXJPA, Kernel 2.6.32.9 ). Please email them to [email protected], or tell me where I can download them.
I know this would cease to be a problem if I just flash a custom rom, and I would love to try that in future, but not now.
Thanks so much in advance.
Easy way would be to go to the Rom Kitchin build update zip with only the Touchwizz in it and flash it from SD card via CWM.
http://romkitchen.org/sgs/?s=generator
APK might be in Perkas file stash from this forum ..###
jje
JJEgan said:
Easy way would be to go to the Rom Kitchin build update zip with only the Touchwizz in it and flash it from SD card via CWM.
http://romkitchen.org/sgs/?s=generator
APK might be in Perkas file stash from this forum ..###
jje
Click to expand...
Click to collapse
Thanks, but I'm on 2.2, which means I have the 3e loader which does not allow me to setup update.zips which are unsigned. For this reason, i was also not able to get CWM installed. I know there's a way to downgrade the loader to 2e, but I'll rather not try that at this moment.
I agree with jje. The best and probably easiest way would be to flash 2e recovery. Chainfire has created a kernel for that purpose and as long as you can access download mode you should be fine.
Sent from my GT-I9000 using XDA Premium App
chriszzz said:
Thanks, but I'm on 2.2, which means I have the 3e loader which does not allow me to setup update.zips which are unsigned. For this reason, i was also not able to get CWM installed. I know there's a way to downgrade the loader to 2e, but I'll rather not try that at this moment.
Click to expand...
Click to collapse
Flash SpeedMOD kernel with Odin and you'll get CWM.
Hi JJEgan, anfearg, Intratech
Thanks for the advice so far. But would it be possible for me to just simply use a file manager to copy the TouchWiz apk and odex files to my system/app directory ? My phone is rooted, so I know it's possible as long as I can get those files. I'm just not sure if there's anything else that needs to be configured to get Android to use those files during setup. If this is workable, this would be the easiest route. Now I just need to get my hands on those files.
I know Odin can fix this, but I'll rather just stick to the current stock rom for now, and just add the missing 2 files.
Intratech said:
Flash SpeedMOD kernel with Odin and you'll get CWM.
Click to expand...
Click to collapse
I'm going to take a look at Odin and see if its not too risky to flash my i9000. I've flashed my old WinMo phones in the past, so flashing is not new to me. But I've yet to try it for Android. Maybe I'll give it a go.
chriszzz said:
Hi JJEgan, anfearg, Intratech
Thanks for the advice so far. But would it be possible for me to just simply use a file manager to copy the TouchWiz apk and odex files to my system/app directory ? My phone is rooted, so I know it's possible as long as I can get those files. I'm just not sure if there's anything else that needs to be configured to get Android to use those files during setup. If this is workable, this would be the easiest route. Now I just need to get my hands on those files.
I know Odin can fix this, but I'll rather just stick to the current stock rom for now, and just add the missing 2 files.
Click to expand...
Click to collapse
OK, so I spent a couple of hours googling and downloaded Odin, a couple of stock ROMs, PIT files and USB drivers. Fired up Odin, followed instructions, and I'm now back to 2.1 with the 2e loader. Sweet. Had a heart stopping moment when Odin said "FAILED" in red, so i just reflashed another ROM and it went through successfully.
Looks like I'm in the ROM flashing crowd now.
Quick question : some ROMs ( like the one I flashed successfully with Odin ) contains just a few tars - 1 each for CODE/PDA, CSC and MODEM/Phone.
Others ( like the one that Odin failed to flash ) just contains a bunch of directories with files that have bin, rfs, lfs extensions.
Why are there 2 different types of ROM packaging ? Is the first one ( with the tar files ) specific to Odin ? How do I flash the other type then ? With ClockWorkMod ?
chriszzz said:
I'm going to take a look at Odin and see if its not too risky to flash my i9000. I've flashed my old WinMo phones in the past, so flashing is not new to me. But I've yet to try it for Android. Maybe I'll give it a go.
Click to expand...
Click to collapse
chriszzz said:
OK, so I spent a couple of hours googling and downloaded Odin, a couple of stock ROMs, PIT files and USB drivers. Fired up Odin, followed instructions, and I'm now back to 2.1 with the 2e loader. Sweet. Had a heart stopping moment when Odin said "FAILED" in red, so i just reflashed another ROM and it went through successfully.
Looks like I'm in the ROM flashing crowd now.
Quick question : some ROMs ( like the one I flashed successfully with Odin ) contains just a few tars - 1 each for CODE/PDA, CSC and MODEM/Phone.
Others ( like the one that Odin failed to flash ) just contains a bunch of directories with files that have bin, rfs, lfs extensions.
Why are there 2 different types of ROM packaging ? Does each ROM come in both forms ? Can they be converted from 1 form to the other ?
Click to expand...
Click to collapse
the .tar types are to be flashed via odin only whereas the ones with the directories are to be flashed via CWM(2e recovery).... mix them up and you'll be in trouble... ;-)
You only needed to flash the recovery 2e zip file through Odin from the forum .
jje
chriszzz said:
<snipped>.. Others ( like the one that Odin failed to flash ) just contains a bunch of directories with files that have bin, rfs, lfs extensions.
Why are there 2 different types of ROM packaging ? Is the first one ( with the tar files ) specific to Odin ? How do I flash the other type then ? With ClockWorkMod ?
Click to expand...
Click to collapse
The single .tar file with .rfs, .bin, etc. is a high-level package. It's sort of a firmware update and can only be flashed on top of an existing firmware. That is, you don't tick re-partition in odin. The ones that come with 3 separate files for CSC, PDA and MODEM are either medium or low-level packages. I think, the low-level ones come with bootloaders. These can be flashed with re-partition ticked.
Thanks guys.
Today I learned how to flash using ODIN (flashed a European 2.1 ROM onto my international i9000 originally with Asian ROM, and downgraded my 3e loader to 2e).
Then I learned to use ClockWorkMod, which I used to flash Darky's ROM 9.5 ( nice ROM, although booting up seems to take an usually long time. Not sure why ). Finally, I almost had a heart attack, twice, when my phone refused to boot after flashing. Nothing a 3 button combo to download mode couldn't fix though.
Fun fun fun. Thanks all.
So, that's a long story, but a few days ago I tried do flash one more time the CM11. It gave me an error like written below. I used the CWM 6.0.5.3 that supports MTD (flashed it with Odin - .tar.md5), all beautiful, but that's not about it.
When I returned to stock and tried to flash the CWM5 through native recovery and even flashed CWM6 (6.0.5.3) through Odin, it gave me the following error (in both cases, native recovery with every ZIP I tried to flash and CWM also):
"Finding update package...
Opening update package...
Installation <something>
Installation aborted."
After this manipulations, I can't even obtain root access on my phone and I have 3 apps installed, because it's out of memory. I heard that it could be because the file system remained in MTD and it is not compatible, but, if it's like this, how can I return to YAFFS2?
It does not install any ZIP, so I can flash nothing. Nor custom firmwares, nor other fixes (like root) and CWM also.
Please, help!
dushkalex said:
So, that's a long story, but a few days ago I tried do flash one more time the CM11. It gave me an error like written below. I used the CWM 6.0.5.3 that supports MTD (flashed it with Odin - .tar.md5), all beautiful, but that's not about it.
When I returned to stock and tried to flash the CWM5 through native recovery and even flashed CWM6 (6.0.5.3) through Odin, it gave me the following error (in both cases, native recovery with every ZIP I tried to flash and CWM also):
"Finding update package...
Opening update package...
Installation <something>
Installation aborted."
After this manipulations, I can't even obtain root access on my phone and I have 3 apps installed, because it's out of memory. I heard that it could be because the file system remained in MTD and it is not compatible, but, if it's like this, how can I return to YAFFS2?
It does not install any ZIP, so I can flash nothing. Nor custom firmwares, nor other fixes (like root) and CWM also.
Please, help!
Click to expand...
Click to collapse
Simply flash stock rom via odin - this will convert your file system back to rfs for use with stock based roms (cm roms use ext file system)
You can then root the phone and flash a temp cwm or a kernel of your choice for stock based roms with cwm built in
stock rom firmware is found on my firmware thread - Links either in signature or top of firmware thread
Tried it already on a lot if version (XXKI6, XXLK3 and another ones), not working, but I'll try one more time today.
dushkalex said:
Tried it already on a lot if version (XXKI6, XXLK3 and another ones), not working, but I'll try one more time today.
Click to expand...
Click to collapse
make sure you are using the firmware from my thread (the ones you have quoted are old firmwares) - they are wipe packs and will format your system when flashing
I would use this one if you are in Europe
http://d-h.st/FhE
Thx, I'll try it
marcussmith2626 said:
make sure you are using the firmware from my thread (the ones you have quoted are old firmwares) - they are wipe packs and will format your system when flashing
I would use this one if you are in Europe.
Click to expand...
Click to collapse
Tried, the same.
dushkalex said:
Tried, the same.
Click to expand...
Click to collapse
Then there is either a problem with the way you are flashing it or you flashed wrong files on your phone in the past and you may need to include the pit file with the rest of the firmware - you can find the pit file for galaxy y 5360 with an easy google search - there is an xda thread with it
All firmware on my thread is confirmed working and the Europe one I have used myself - So if using the pit file doesn't work along with the firmware file then I would take it to a repair shop
marcussmith2626 said:
Then there is either a problem with the way you are flashing it or you flashed wrong files on your phone in the past and you may need to include the pit file with the rest of the firmware - you can find the pit file for galaxy y 5360 with an easy google search - there is an xda thread with it
All firmware on my thread is confirmed working and the Europe one I have used myself - So if using the pit file doesn't work along with the firmware file then I would take it to a repair shop
Click to expand...
Click to collapse
Thanks Can I flash the .pit separately from the firmware?
dushkalex said:
Thanks Can I flash the .pit separately from the firmware?
Click to expand...
Click to collapse
you flash it all at the same time
PIT and your wipe firmware flashed at the same time haven't fixed it, the FS is broken. Any other ways or I have to prepare money for the service center?
try to format all partition ( data+system+cache ) and flash a stock rom
Hello!
Long story short, I bought a dual SIM Edge+ (G9287) but found out I can't use my second SIM in it.
I tried flashing Audax ROM which doesn't have support for my model and it worked just fine, but couldn't detect my SIM card (even though I'm only using one).
So my question is, can I use SM-G9287C firmware on my G9287 and then flash some ROM? Will it work or will it brick my phone?
Nebell said:
Hello!
Long story short, I bought a dual SIM Edge+ (G9287) but found out I can't use my second SIM in it.
I tried flashing Audax ROM which doesn't have support for my model and it worked just fine, but couldn't detect my SIM card (even though I'm only using one).
So my question is, can I use SM-G9287C firmware on my G9287 and then flash some ROM? Will it work or will it brick my phone?
Click to expand...
Click to collapse
Just curious, when you couldn't use your second sim, were you on stock firmware? If yes, did you enable the 2nd SIM in settings? Setting->SIM Card Manager -> 2nd SIM and turn it on with the toggle.
My phone is G9287C which is a dual sim as well, there's a workaroud to make the dual sim work on CRISSCROSS ROM, though I'm not sure if the same goes for other ROMs. However if the 2nd SIM doesn't work with stock firmware, I believe it wouldn't work other ROMs too.
Naw I couldn't use the second SIM because it's from my work phone, I work for the government and they got retarded protection so I couldn't set up my email and few other things and they also forbid removing SIM cards from their phones. So I had to accept not using the second SIM card.
But when I flashed Audax then I was not using stock firmware, although I was using older G9287 firmware (J7, since it was apparently the only way to be able to successfully flash custom recovery as my old K5 would just re-flash stock recovery after every restart). Still, it would not recognize my home SIM regardless if it was in slot 1 or 2.
Nebell said:
Naw I couldn't use the second SIM because it's from my work phone, I work for the government and they got retarded protection so I couldn't set up my email and few other things and they also forbid removing SIM cards from their phones. So I had to accept not using the second SIM card.
But when I flashed Audax then I was not using stock firmware, although I was using older G9287 firmware (J7, since it was apparently the only way to be able to successfully flash custom recovery as my old K5 would just re-flash stock recovery after every restart). Still, it would not recognize my home SIM regardless if it was in slot 1 or 2.
Click to expand...
Click to collapse
Not sure if it works, but worth trying:
1. Get these 3 files from your stock firmware under folder /system/lib64/
i. libril.so
ii. libsec-ril.so
iii. libsec-ril-dsds.so
then copy to the same folder and overwrite the files after you flashed the custom ROM. Make sure those 3 files are in -rw-r--r-- format. Wait 20 seconds see if the signal icon appears on the status bar.
2. If signal icon does not appear, flash other kernels like arter97 or anything.
3. You might need to flash the radio/baseband "modem.bin" from your stock firmware.
fenrir_ac said:
Not sure if it works, but worth trying:
1. Get these 3 files from your stock firmware under folder /system/lib64/
i. libril.so
ii. libsec-ril.so
iii. libsec-ril-dsds.so
then copy to the same folder and overwrite the files after you flashed the custom ROM. Make sure those 3 files are in -rw-r--r-- format. Wait 20 seconds see if the signal icon appears on the status bar.
2. If signal icon does not appear, flash other kernels like arter97 or anything.
3. You might need to flash the radio/baseband "modem.bin" from your stock firmware.
Click to expand...
Click to collapse
Thanks for trying to help, but I was looking for an answer if the phone will work normally with a firmware from one of the single SIM models
If it works, then I can just flash it and then use pretty much any Edge+ ROM without having to edit much.
Nebell said:
Thanks for trying to help, but I was looking for an answer if the phone will work normally with a firmware from one of the single SIM models
If it works, then I can just flash it and then use pretty much any Edge+ ROM without having to edit much.
Click to expand...
Click to collapse
Ah, my apologies for not reading your question properly. Just for your reference tho, I have only tried Crisscross and Kos ROM and both didn't detect my SIM card. I believe the same goes for all other ROM since they only support single SIM variants, reason being the baseband and RIL are different from ours.
Ahh so I guess not even flashing firmware from a single SIM model would work :/
Last time I'm buying dual SIM anything.
fenrir_ac said:
Not sure if it works, but worth trying:
1. Get these 3 files from your stock firmware under folder /system/lib64/
i. libril.so
ii. libsec-ril.so
iii. libsec-ril-dsds.so
then copy to the same folder and overwrite the files after you flashed the custom ROM. Make sure those 3 files are in -rw-r--r-- format. Wait 20 seconds see if the signal icon appears on the status bar.
2. If signal icon does not appear, flash other kernels like arter97 or anything.
3. You might need to flash the radio/baseband "modem.bin" from your stock firmware.
Click to expand...
Click to collapse
I have also SM-G9287C (dual sim) and I am interested to flash custom ROMs. So far no custom ROM for my dual sim phone is available so I have to flash single sim custom ROM. My question is, will your method work with every custom single sim ROM?
And how to flash radio/baseband "modem.bin"?
Jmakhdoom said:
I have also SM-G9287C (dual sim) and I am interested to flash custom ROMs. So far no custom ROM for my dual sim phone is available so I have to flash single sim custom ROM. My question is, will your method work with every custom single sim ROM?
And how to flash radio/baseband "modem.bin"?
Click to expand...
Click to collapse
I don't know if it would be able to run every custom rom. But as far as I know, my phone is able to run Crisscross rom 1.8 smoothly (haven't tried the latest one 1.9.1) without any hiccups.
Regarding "modem.bin," get the stock firmware from sammobile G9287CDXU2AOK1 (this is the latest one but any stock rom in tar.md5 format will do). Open the file and extract modem.bin (can be done with 7-zip). The Crisscross rom 1.8 doesn't overwrite the baseband (the latest 1.9.1 might wipe the baseband) so this step is just optional and if anything goes wrong you can do this afterwards. If your current baseband is G9287CDXU2AOK2, you can leave this step.
Remember the step 1 I've mentioned in the post earlier is the most important step of the 3.
p/s: I also did this tweak on my phone and it runs even smoother, http://forum.xda-developers.com/s6-edge-plus/general/root-ram-management-multitasking-fix-t3228917
I have 9287 using dual sim and only one card can use 4g while another is 2g only did u check the gsm frequency is supported by your carrier http://www.samsung.com/hk_en/consumer/mobile/smartphones/galaxy-s/SM-G9287ZDUTGY
fenrir_ac said:
I don't know if it would be able to run every custom rom. But as far as I know, my phone is able to run Crisscross rom 1.8 smoothly (haven't tried the latest one 1.9.1) without any hiccups.
Regarding "modem.bin," get the stock firmware from sammobile G9287CDXU2AOK1 (this is the latest one but any stock rom in tar.md5 format will do). Open the file and extract modem.bin (can be done with 7-zip). The Crisscross rom 1.8 doesn't overwrite the baseband (the latest 1.9.1 might wipe the baseband) so this step is just optional and if anything goes wrong you can do this afterwards. If your current baseband is G9287CDXU2AOK2, you can leave this step.
Remember the step 1 I've mentioned in the post earlier is the most important step of the 3.
p/s: I also did this tweak on my phone and it runs even smoother, http://forum.xda-developers.com/s6-edge-plus/general/root-ram-management-multitasking-fix-t3228917
Click to expand...
Click to collapse
So as a conclusion, can you use Crisscross ROM on 9287 with at least one sim card working? Thanks in advance if you clear this up with details
vsdmch said:
So as a conclusion, can you use Crisscross ROM on 9287 with at least one sim card working? Thanks in advance if you clear this up with details
Click to expand...
Click to collapse
Yes.
fenrir_ac said:
I don't know if it would be able to run every custom rom. But as far as I know, my phone is able to run Crisscross rom 1.8 smoothly (haven't tried the latest one 1.9.1) without any hiccups.
Regarding "modem.bin," get the stock firmware from sammobile G9287CDXU2AOK1 (this is the latest one but any stock rom in tar.md5 format will do). Open the file and extract modem.bin (can be done with 7-zip). The Crisscross rom 1.8 doesn't overwrite the baseband (the latest 1.9.1 might wipe the baseband) so this step is just optional and if anything goes wrong you can do this afterwards. If your current baseband is G9287CDXU2AOK2, you can leave this step.
Remember the step 1 I've mentioned in the post earlier is the most important step of the 3.
p/s: I also did this tweak on my phone and it runs even smoother, http://forum.xda-developers.com/s6-edge-plus/general/root-ram-management-multitasking-fix-t3228917
Click to expand...
Click to collapse
fenrir_ac said:
Yes.
Click to expand...
Click to collapse
Can you write up a step by step guide here, pm me or open a thread on xda for how to make custom ROM working on 9287 :good:
vsdmch said:
Can you write up a step by step guide here, pm me or open a thread on xda for how to make custom ROM working on 9287 :good:
Click to expand...
Click to collapse
pm you few days back and still waiting for reply.
Fenrir_ac,
I am also on the 9287. I tried installing CrissCross 1.8 and 1.91 and both times they made my baseband version Unknown and it couldn't read my SIM. I installed a clean stock ROM before i installed both 1.8 and 1.91. I then tried installing the modem.bin from a stock ROM using Odin and the CP option and that didnt work either. Can you please put a detailed description on this thread how to get CrissCross working on a 9287. Thanks!
vex1989 said:
Fenrir_ac,
I am also on the 9287. I tried installing CrissCross 1.8 and 1.91 and both times they made my baseband version Unknown and it couldn't read my SIM. I installed a clean stock ROM before i installed both 1.8 and 1.91. I then tried installing the modem.bin from a stock ROM using Odin and the CP option and that didnt work either. Can you please put a detailed description on this thread how to get CrissCross working on a 9287. Thanks!
Click to expand...
Click to collapse
It's worth to note that my phone is g9287c variant, not g9287 without the letter "c" at the end. It is still a dual sim variant, I faced the very same issues before (sim card not detected on both slots), and therefore I'm just assuming the fix that I did on my phone MIGHT work with your phone too. I'm not a developer so I have no idea what risk would involve in doing this. If you still wish to do so please do it at your own risk.
Few Questions:
1. Are you on stock ROM now? What is your current bootloader version?
2. It makes me wonder why your baseband became "unknown". Did you flash "modem and bootloader" file provided on the CRISSCROSS ROM thread? If yes, please DON'T flash it on your next attempt.
3. When you flash Crisscross ROM 1.8, did you dirty flash instead of clean flash?
4. Did you port over the 3 RIL files ( in the /system/lib64 folder that I mentioned in earlier post) from the stock ROM after flashing Crisscross ROM? It's the most important thing to do.
Here's what I did to make CRISSCROSS 1.8 to work on my phone.
1. Get the latest stock ROM and flash it on my phone, extract the modem.bin file just in case.
2. Update the stock ROM (if there's any) with the built-in software update.
3. Backup somewhere these 3 files from /system/lib64 folder (MOST IMPORTANT STEP!)
i. libsec-ril.so
ii. libsec-ril-dsds.so
iii. libril.so
After back up, flash TWRP with ODIN.
4. DIRTY Flash CRISSCROSS ROM 1.8 through TWRP recovery. I did not flash the latest 1.9 since its a requirement to perform a data wipe.
5. I did not flash the "modem and bootloader" provided in the CRISSCROSS thread.
6. Wipe dalvik and cache after flashing CRISSCROSS ROM. Reboot system and wait until the phone is ready to use.
7. Move the 3 backed up files earlier and overwrite it to the same folder (/system/lib64). Make sure the three files are in -rw-r--r-- format. I'm not sure if root is required for this as it involves overwriting system files.
8. Wait 30 seconds until signal indicator magically appears on the status bar (Only one SIM will work at this stage. The provided AUDAX kernel does not support dual SIM).
9. Reboot to recovery and flash the latest arter97 kernel (v11).
10. I did not flash modem.bin through ODIN since I found that the Crisscross Rom flash did not touch my baseband.
11. Reboot system and turn on your second SIM option in Settings>SIM Card Manager.
Hopefully this will work on your phone. As usual, do a nandroid backup before performing this just in case.
1. I am currently on stock ROM, J7. This was the only Firmware that allowed me to root. Bootloader Verison G9287ZHU2AOJ7
2. I did not do that. All I did was install the zip file in recovery. How am i supposed not to install those files.
3. I did a clean flash on both attempts.
4. No I didnt. I need to do that next.
I will attempt this sometime this week and give you feedback. Thanks for the write up. I also have a problem with artex kernal and Audax kernal where it causes major lag issues for my Gear VR so it looks like i have to use a modified stock kernal.
fenrir_ac said:
It's worth to note that my phone is g9287c variant, not g9287 without the letter "c" at the end. It is still a dual sim variant, I faced the very same issues before (sim card not detected on both slots), and therefore I'm just assuming the fix that I did on my phone MIGHT work with your phone too. I'm not a developer so I have no idea what risk would involve in doing this. If you still wish to do so please do it at your own risk.
Few Questions:
1. Are you on stock ROM now? What is your current bootloader version?
2. It makes me wonder why your baseband became "unknown". Did you flash "modem and bootloader" file provided on the CRISSCROSS ROM thread? If yes, please DON'T flash it on your next attempt.
3. When you flash Crisscross ROM 1.8, did you dirty flash instead of clean flash?
4. Did you port over the 3 RIL files ( in the /system/lib64 folder that I mentioned in earlier post) from the stock ROM after flashing Crisscross ROM? It's the most important thing to do.
Here's what I did to make CRISSCROSS 1.8 to work on my phone.
1. Get the latest stock ROM and flash it on my phone, extract the modem.bin file just in case.
2. Update the stock ROM (if there's any) with the built-in software update.
3. Backup somewhere these 3 files from /system/lib64 folder (MOST IMPORTANT STEP!)
i. libsec-ril.so
ii. libsec-ril-dsds.so
iii. libril.so
After back up, flash TWRP with ODIN.
4. DIRTY Flash CRISSCROSS ROM 1.8 through TWRP recovery. I did not flash the latest 1.9 since its a requirement to perform a data wipe.
5. I did not flash the "modem and bootloader" provided in the CRISSCROSS thread.
6. Wipe dalvik and cache after flashing CRISSCROSS ROM. Reboot system and wait until the phone is ready to use.
7. Move the 3 backed up files earlier and overwrite it to the same folder (/system/lib64). Make sure the three files are in -rw-r--r-- format. I'm not sure if root is required for this as it involves overwriting system files.
8. Wait 30 seconds until signal indicator magically appears on the status bar (Only one SIM will work at this stage. The provided AUDAX kernel does not support dual SIM).
9. Reboot to recovery and flash the latest arter97 kernel (v11).
10. I did not flash modem.bin through ODIN since I found that the Crisscross Rom flash did not touch my baseband.
11. Reboot system and turn on your second SIM option in Settings>SIM Card Manager.
Hopefully this will work on your phone. As usual, do a nandroid backup before performing this just in case.
Click to expand...
Click to collapse
fenrir_ac, you sir are a genius. I am on Cris Cross ROM with signal Thanks!
Hello Canada. I'm on Rogers and updated a few days ago to the new 6.01 Marshmallow ROM. I have root. Seems to be not much development work on our device, the G900W8, wanted to try some custom kernels and see if they would work but they all seem to be for the 900F. I'm interested in battery life improvements.
So I wanted to get a stock kernel I could flash in case something goes wrong and it won't boot, or if I just don't like the kernel. Some custom kernels require you to flash from stock rather than other custom kernels.
So how do we get things like kernel and radio out of our new G900W8 download? The download I have from Rogers is G900W8VLU1DPD3_G900W8OYA1DPD3_G900W8VLU1DPD3.
Use 7zip to open archive the stock rom. Then extract boot.img. IMG files can flash via TWRP.
Did some searches, seems like Flashify will do it. Gonna give it a try.
Saquing18 said:
Use 7zip to open archive the stock rom. Then extract boot.img. IMG files can flash via TWRP.
Click to expand...
Click to collapse
Thank you. I grabbed the file boot.img from the downloaded Rogers ROM file and copied to my PC. It has a file size in Windows Explorer of 12319. I also used Flashify to extract it, copied it to the PC, it has a size of 13,312. Wonder why the size difference?
There are a few reasons why can't some people out there just go and install a custom ROM, here are a few:
1. You are not rooted
This should be clear, you have to have root, I can't even see a way of installing a custom ROM without root. You can search for a guide on XDA Devs to help you.
2. You flashed your ROM the wrong way
Even though there are a few ways of flashing a ROM, only some of them are correct. You can't use Flashify for a ROM, trust me you'll only get into trouble. You can't and you should not try to flash a ROM through Odin, remember, Odin is only used to flash Stock ROMS, yes, you can maybe flash a ROM trought Odin if you knew how to convert your ROM to system images and then pack it up to a .tar.md5 file.
3. Your ROM zip may be corrupted
Double check if your ROM zip is the right size and check if you can open it via WinRAR or 7Zip.
4. You flashed a ROM for a wrong model
With Samsung devices, there will be the F, the I, the A and all the others. If you have an F and flash a ROM for an A, your device will not work. Also, some people don't see the 5 in SM-G925 although they have a G920, so their ROM will work fine, but the touch sides will be inverted.
5. Your proccessor isn't compatibile
I don't know if this is true, but my friend now lives in America, so he has a Galaxy S6 Snapdragon model and I have a Exynos model. This could be a potential problem, but I don't really think.