Hello Everyone,
I have a chinese i9105p on hand. Nearly all aftermarket roms ask for a 4.2.2 stock before "install proper/newest recovery", however, the highest stock version for a china i9105p is 4.1.2. And it seems impossible to use 4.2.2 roms from the other region. Odin just refuse to flash. I tried flash CM13 and remix directly with cwr4.0.3.2(the version work with android 4.1.2), after flashing the phone goes to reboot loop or stuck at the loading logo.
The missing of 4.2.2 stock rom should not be a limitation. There are no 4.2.2 stock for i9100 at all. And CM13 works for i9100. From there I found out that they upgrade the kernel at the same time when installing recovery.
So I extract the boot.img for a 4.2.2-I9105PXXUBMI1 stock, extract the recovery.img from twrp/cwr, combine the two into a new tar file. Flash with odin. Reboot to recovery. Stuck on loading logo again.
Could some expert help to make a workable recovery which includes the proper kernel already? It should also be useful for the other 4.1.2 users who want cm13, we can direclty flash the recovery and update, instead of download and odin the 4.2.2 stock for a intermediate step now.
Or any other solution to make cm13 work on chn i9105p with the absence of 4.2.2 chn stock?
regards
Wait does Odin actually recognize your device? If it is then I dunno what is going on,try downloading CPU-Z from the Play Store and screenshot what CPU does it say and post it here,because it may be a clone
Dinkec27 said:
Wait does Odin actually recognize your device? If it is then I dunno what is going on,try downloading CPU-Z from the Play Store and screenshot what CPU does it say and post it here,because it may be a clone
Click to expand...
Click to collapse
Thank you for your fast reply, Dinkec. From your signature I can see you are really a guru in ROMs.
The odin I use is from
odindownload[dot]com/download/Odin3_v3.11.1.zip
It works perfectly with the chn i9105p stocks. Any 4.1.2 chn stock or roms based on could be flashed successfully. Actually I have used those stock to revive the phone from brick or booting loop many times. The odin also works with CWM 4.0.3.2/4.0.2.8, and I have flashed CM10.1 with CWM 4.0.3.2 successfully as well. However, any update attempt to android 4.2.2 or higher would lead to boot loop/stuck.
So I am not so worried about if the i9105p is a clone. By the way, it is not a special problem on this i9105p, but a general headache of all chinese i9105p. They feel as if they had been thrown over by samsung and the rest of world.
This is the official firmware for i910p. Anyone could check and confirm that 4.2.2 is missing for CHN area.
www[dot]sammobile.com/firmwares/database/GT-I9105P/
i9105pchn said:
Thank you for your fast reply, Dinkec. From your signature I can see you are really a guru in ROMs.
The odin I use is from
odindownload[dot]com/download/Odin3_v3.11.1.zip
It works perfectly with the chn i9105p stocks. Any 4.1.2 chn stock or roms based on could be flashed successfully. Actually I have used those stock to revive the phone from brick or booting loop many times. The odin also works with CWM 4.0.3.2/4.0.2.8, and I have flashed CM10.1 with CWM 4.0.3.2 successfully as well. However, any update attempt to android 4.2.2 or higher would lead to boot loop/stuck.
So I am not so worried about if the i9105p is a clone. By the way, it is not a special problem on this i9105p, but a general headache of all chinese i9105p. They feel as if they had been thrown over by samsung and the rest of world.
This is the official firmware for i910p. Anyone could check and confirm that 4.2.2 is missing for CHN area.
www[dot]sammobile.com/firmwares/database/GT-I9105P/
Click to expand...
Click to collapse
So there is only three firmwares on the Sammobile site,and no 4.2.2 seen.
Did you try flashing the latest TWRP because that CWM is very out of date and probably is the reason you cannot boot Android 4.3 ROMs and above,you will need to install this recovery through Flashify(an app from the Play Store)
Flash this image from the link below:
https://dl.twrp.me/s2vep/twrp-3.0.2-0-s2vep.img.html
Dinkec27 said:
So there is only three firmwares on the Sammobile site,and no 4.2.2 seen.
Did you try flashing the latest TWRP because that CWM is very out of date and probably is the reason you cannot boot Android 4.3 ROMs and above,you will need to install this recovery through Flashify(an app from the Play Store)
Flash this image from the link below:
https://dl.twrp.me/s2vep/twrp-3.0.2-0-s2vep.img.html
Click to expand...
Click to collapse
You are really an expert. I thought I have offered all the neccessary info, however, I learned from your reply that still many details are missing.
I didn't know Flashify before, but I tried TWRP manager. The TWRP manager from googleplay doesn't work on 4.1.2 stock. I can open the app and choose my phone type, then the app get stuck and logout itself.
I have tried TWRP with odin. Flashing TWRP-2.8.0.1-s2ve.tar.md5/TWRP-2.8.0.1-s2vep.tar.md5 from its official site with odin and reboot into recovery, will result into boot stuck for about several minutes, and then the phone would reboot into its current ROM automatically. I also tried TWRP-2.6.30_4.2.2_ODIN-s2vep.tar.md5 from
http://forum.xda-developers.com/showthread.php?t=2560928
with the 4.1.2 stock and CM10.1 (because the CM 10.1 is said to be 4.2.2). Same result, recovery boot stuck and reboot into rom after a few minutes.
The 2.8.0.1 is the oldest version I could find from its official site. They suggest that the new version might not be compatible with the old kernels, nevertheless, the old version failed.
Reading carefully from the install instruction of xda roms, I learn that it might be the problem of selinux. Starting from android 4.2.2, selinux was introduced. And the problem comes out, the new twrp which support selinux, only works with kernel 4.2.2 or higher. In order to flash a ROM higher than 4.2.2, you have to get a twrp work with that first.
I cannot get a way out of this loop when the 4.2.2 stock rom are missing. But as I mentioned in the original post, there are no 4.2.2 stock at all for samsung SII I9100. So there must be some way out for i9105p as well.
Have tried flashify.
A pop box saying
"Flashify isn't responding. Do you want to close it"
When I use flash recovery and choose a file.
Perhaps flashify and twrp manager only works on 4.2.2 or higher.
i9105pchn said:
Have tried flashify.
A pop box saying
"Flashify isn't responding. Do you want to close it"
When I use flash recovery and choose a file.
Perhaps flashify and twrp manager only works on 4.2.2 or higher.
Click to expand...
Click to collapse
Take a screenshot of the CPU-Z app,it could be that it is bootlooping because the chinese version may have a different chipset
EDIT: Try flashing the .tar.md5 from this link: https://www.mediafire.com/?s6ua6z74n6r9b93
Dinkec27 said:
Take a screenshot of the CPU-Z app,it could be that it is bootlooping because the chinese version may have a different chipset
EDIT: Try flashing the .tar.md5 from this link: https://www.mediafire.com/?s6ua6z74n6r9b93
Click to expand...
Click to collapse
I agree. Here is the screenshot.
i9105pchn said:
I agree. Here is the screenshot.
Click to expand...
Click to collapse
So it is the same chipset... but you have a different storage configuration it seems,because the normal S2 Plus has 8GB of storage,your has 4GB,I will look into modding the recovery because it is possible the mounting points are different and it bootloops.
Did you try flashing that recovery from the last post?
Also do you have an update for your phone because I can see the icon in the statusbar which looks like that thing for updating your phone?
Dinkec27 said:
So it is the same chipset... but you have a different storage configuration it seems,because the normal S2 Plus has 8GB of storage,your has 4GB,I will look into modding the recovery because it is possible the mounting points are different and it bootloops.
Did you try flashing that recovery from the last post?
Also do you have an update for your phone because I can see the icon in the statusbar which looks like that thing for updating your phone?
Click to expand...
Click to collapse
<ID:0/009> Odin engine v(ID:3.1101)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> SingleDownload.
<ID:0/009> recovery.img
<ID:0/009> NAND Write Start!!
<ID:0/009> FAIL!
<ID:0/009>
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Flashing recovery failed. Odin refused to write in just like when I try stock roms from the other region.
You remind me. I ask samsung customer service in China. They say the total rom is 8g. The system takes around 4G and hide it, so it shows out only 3.94GB
This is the official answer.
i9105pchn said:
<ID:0/009> Odin engine v(ID:3.1101)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> SingleDownload.
<ID:0/009> recovery.img
<ID:0/009> NAND Write Start!!
<ID:0/009> FAIL!
<ID:0/009>
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Flashing recovery failed. Odin refused to write in just like when I try stock roms from the other region.
You remind me. I ask samsung customer service in China. They say the total rom is 8g. The system takes around 4G and hide it, so it shows out only 3.94GB
This is the official answer.
Click to expand...
Click to collapse
Weird I get about 5.7GB free,I will look into this tomorrow since it is very late right now in my country,and cool to know that my tar.md5 is corrupt not the recovery,I will upload the img tomorrow and show you how to flash it through an app called Terminal Emulator
Btw try an older version of Odin it may help,just know that my tar.md5 doesn't work I have actually just tried it right now so don't try it,instead try flashing the 4.2.2 firmware with Odin 3.07 or something which has Odin 3.xx in it
Dinkec27 said:
Weird I get about 5.7GB free,I will look into this tomorrow since it is very late right now in my country,and cool to know that my tar.md5 is corrupt not the recovery,I will upload the img tomorrow and show you how to flash it through an app called Terminal Emulator
Btw try an older version of Odin it may help,just know that my tar.md5 doesn't work I have actually just tried it right now so don't try it,instead try flashing the 4.2.2 firmware with Odin 3.07 or something which has Odin 3.xx in it
Click to expand...
Click to collapse
thank you for your reply
I tried odin 3.07. It works exactly the same as 3.11. It refuse to flash any other region. I triedd 4.1.2/4.2.2 DBT region, odin refuse.
I think we are closer to the truth. The CHN version doesn't support the google service package due to local policies. So samsung might apply some special disk allocation on CHN. The hiden partition, or different partition arrangement of chn might be the reason why odin refuse and why recovery always fail.
good night
i9105pchn said:
thank you for your reply
I tried odin 3.07. It works exactly the same as 3.11. It refuse to flash any other region. I triedd 4.1.2/4.2.2 DBT region, odin refuse.
I think we are closer to the truth. The CHN version doesn't support the google service package due to local policies. So samsung might apply some special disk allocation on CHN. The hiden partition, or different partition arrangement of chn might be the reason why odin refuse and why recovery always fail.
good night
Click to expand...
Click to collapse
I have an idea,since it cannot flash through Odin I will give a shot and making a flashable zip since you do have some kind of working recovery which can actually flash Android 4.1.2,I will test it on my device and report back if any success and if there is hopefully there should be a download link,and also if there was different partition arrangement I think that the recovery would not be able to wipe,or factory reset,try wiping cache and see will it succeed or not,if it does then the partition arragement is the same as the normal S2 Plus
Dinkec27 said:
I have an idea,since it cannot flash through Odin I will give a shot and making a flashable zip since you do have some kind of working recovery which can actually flash Android 4.1.2,I will test it on my device and report back if any success and if there is hopefully there should be a download link,and also if there was different partition arrangement I think that the recovery would not be able to wipe,or factory reset,try wiping cache and see will it succeed or not,if it does then the partition arragement is the same as the normal S2 Plus
Click to expand...
Click to collapse
Let me make it clear, odin isn't the problem. The problem is the missing 4.2.2 chn stock. Both odin and CWM are able to flash CHN 4.1.2 stocks and MOD based on CHN 4.1.2 stocks. Neither odin nor CWM could flash any kind of 4.2.2 or higher.
Several chn i9105p holders are surprised about the 4G storage and ask on the samsung official forums. So I think the CHN storage should be different.
I did wipe AND factory reset everytime when I flash ROM, just do it again. Now the total are 3.94G, apps takes up 103M, all kind of files takes 657k, so 3.78G available. The system cannot be so small in the occupied 103M. So there should be a hidden partition which is set to be system partition.
Concerning about the working CWM, I get it from some chinese forum. It might have been modified to work with CHN partition, or the early version CWM might be not sensitive to partition management?
Regards
i9105pchn said:
Let me make it clear, odin isn't the problem. The problem is the missing 4.2.2 chn stock. Both odin and CWM are able to flash CHN 4.1.2 stocks and MOD based on CHN 4.1.2 stocks. Neither odin nor CWM could flash any kind of 4.2.2 or higher.
Several chn i9105p holders are surprised about the 4G storage and ask on the samsung official forums. So I think the CHN storage should be different.
I did wipe AND factory reset everytime when I flash ROM, just do it again. Now the total are 3.94G, apps takes up 103M, all kind of files takes 657k, so 3.78G available. The system cannot be so small in the occupied 103M. So there should be a hidden partition which is set to be system partition.
Concerning about the working CWM, I get it from some chinese forum. It might have been modified to work with CHN partition, or the early version CWM might be not sensitive to partition management?
Regards
Click to expand...
Click to collapse
I have checked the stock recovery of the CHN firmware and the partition layout,it appears to be the same as my S2 Plus,what you can do but personally I do not recommend is to find a pit file for the S2 Plus(I know there is a thread of some sort with a pit file) and flash it with the firmware and tick re-partition because then it will change the partition layout,again I am not recommending this as it may brick your phone,and can you find the chinese forum you downloaded CWM from?
Dinkec27 said:
I have checked the stock recovery of the CHN firmware and the partition layout,it appears to be the same as my S2 Plus,what you can do but personally I do not recommend is to find a pit file for the S2 Plus(I know there is a thread of some sort with a pit file) and flash it with the firmware and tick re-partition because then it will change the partition layout,again I am not recommending this as it may brick your phone,and can you find the chinese forum you downloaded CWM from?
Click to expand...
Click to collapse
pan[dot]baidu.com/s/1nt5Ltc1
pan[dot]baidu.com/s/1eQoAfSI
Here are recovery.
So if the pit are all the same, what could be the reason? Baseband and moderm might be different as the 3g and LTE standard is different in China. I don't know if it would stop eur stock roms from flashing into the chn phone.
regards
i9105pchn said:
pan[dot]baidu.com/s/1nt5Ltc1
pan[dot]baidu.com/s/1eQoAfSI
Here are recovery.
So if the pit are all the same, what could be the reason? Baseband and moderm might be different as the 3g and LTE standard is different in China. I don't know if it would stop eur stock roms from flashing into the chn phone.
regards
Click to expand...
Click to collapse
I have no idea so that is why I wanted to make a flashable zip because it only has system files,no baseband,or bootloader files or anything like that,unfortunately I have had several internet issues and I wasn't able to upload but now it is fine and I will upload overnight
UPDATE 1: I'm now trying to install the zip,will update the post when new progress is made
UPDATE 2: The ROM booted,I will start upload now and will post the link when done
Here is the ROM,it should work,probably the other recoveries didn't work because of SELinux:
http://www.mediafire.com/download/j6z34tg9cgtr48a/Stock-ROM-4.2.2-I9105P.zip
Also if you get any error saying that there is no OS installed just restart anyways,and if it asks to root your phone click Yes
Dinkec27 said:
Here is the ROM,it should work,probably the other recoveries didn't work because of SELinux:
http://www.mediafire.com/download/j6z34tg9cgtr48a/Stock-ROM-4.2.2-I9105P.zip
Also if you get any error saying that there is no OS installed just restart anyways,and if it asks to root your phone click Yes
Click to expand...
Click to collapse
I thought it were a recovery, but it comes out to be a ROM. Well, it would take some time for my poor internet. Would update when the download finish.
Thanks for such a GREAT work.
i9105pchn said:
I thought it were a recovery, but it comes out to be a ROM. Well, it would take some time for my poor internet. Would update when the download finish.
Thanks for such a GREAT work.
Click to expand...
Click to collapse
No problem,and I would recommend factory resetting because I think it may bootloop if you don't
Related
Hi all
my friend install rom from n8000 on n8010 and we have problem to install orginall rom
can any body now where is install bootloader because when we install orginal rom n8010 we have this info on Odin
this is log from Odin
Enter CS for MD5..
Check MD5.. Do not unplug the cable..
Please wait..
KIES_HOME_N8010XXUCMD2_N8010OXACMD2_805288_REV00_u ser_low_ship.tar.md5 is valid.
Checking MD5 finished Sucessfully..
Leave CS..
Added!!
Odin v.3 engine (ID:15)..
File analysis..
SetupConnection..
Initialzation..
Get PIT for mapping..
Firmware update start..
boot.img
NAND Write Start!!
recovery.img
system.img
cache.img
hidden.img
sboot.bin
FAIL!
All threads completed. (succeed 0 / failed 1)
i tyr use flash with pit and i have this info
Odin cant do Re-Partition on tab
i want do it cwm zip pack to install old bootloader but i dont now where this file put
sboot.img
tz.img
this is updater-script from s3 downgrade bootloader
run_program("/sbin/busybox", "dd", "if=/tmp/sboot.bin", "of=/dev/block/mmcblk0p1");
run_program("/sbin/busybox", "dd", "if=/tmp/tz.img", "of=/dev/block/mmcblk0p2");
can any body help me????
Thanks for info
Hi.
I have similar problem.
I flashed my GT-N8010 and i made a mistake.
I "put" ROM for GT-N8000 (N8000XXCMF1) to bootloader mode in ODIN and flash my device.
Now is stuck. Working, but with GT-N8000 firmware only.
In ODIN MODE:
PRODUCT NAME GT-N8000
CUSTOM BINNARY DOWNLOAD: Yes (2 counts)
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
I can't re-flash to GT-N8010 in ODIN (PC) to not any stock N8010 ROM - odin fail.
When i re-flash in MobileOdin:
In ODIN MODE:
PRODUCT NAME GT-N8000
CUSTOM BINNARY DOWNLOAD: Yes (4 counts)
CURRENT BINARY: Custom
SYSTEM STATUS: Official
What's happend?
Could you tell me?
What shall I do?
Thank you for interest my problem.
Elitata1 said:
Hi.
I have similar problem.
I flashed my GT-N8010 and i made a mistake.
I "put" ROM for GT-N8000 (N8000XXCMF1) to bootloader mode in ODIN and flash my device.
Now is stuck. Working, but with GT-N8000 firmware only.
In ODIN MODE:
PRODUCT NAME GT-N8000
CUSTOM BINNARY DOWNLOAD: Yes (2 counts)
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
I can't re-flash to GT-N8010 in ODIN (PC) to not any stock N8010 ROM - odin fail.
When i re-flash in MobileOdin:
In ODIN MODE:
PRODUCT NAME GT-N8000
CUSTOM BINNARY DOWNLOAD: Yes (4 counts)
CURRENT BINARY: Custom
SYSTEM STATUS: Official
What's happend?
Could you tell me?
What shall I do?
Thank you for interest my problem.
Click to expand...
Click to collapse
Service centre paid for repair as warranty is void .
jje
Thx man.
But... this is all what can i do?
Nothing to do myself?
Only warranty option?
Hi,
I have exactly the same issue -- again I also had tried an earlier n8000 rom.
I was only able to install n8010 roms by manally manipulating the flash archive - removing tz.img and sboot.bin
I went right back to the stock 4.1.2 UK rom, and tried to flash that -- but it failed too, and I tried to manually just install the n8010 bootloader (sboot.bin) but that too failed. Kies would not flash the device at all.
Since N8000 roms work, as do hacked N8010 roms I'll just go back to how it was, but I had hoped to be able to get back to official, stock configuration
Has anyone succeeded in fixing this? Since I've never manually modified PIT I'm a little confused as to why I can't get back - can anyone explain? or is there a way to fix this?
Playing with bootloader is the only way where you can really hardbrick your device (only help: using jtag at service centre).
If your devices are not dead at all then service center is not the smartest idea.
As the n8010 lacks of some networking features the rom won't work on n8000 without issues (ie no 3g connection).
This is so-called modem partition (modem.bin file i believe).
The modem is included in not every new firmware, but from time to time only.
Anyway, you may want to look for a firmware/custom rom which include modem.bin for your model; everything related to networking should b back to normal then.
You can find full roms at samfirmware.com
You shall use ODIN - not KIES - to flash those, at it is able to flash both bootloader and modem along with regular stuff on demand. KIES is not.
ALTHOUGH I'm not sure what shall be the effect of improper bootloader combined with proper rom.
And read my first sentence carefully again; I shall take no responsibility if you'll brick your device or do any fatal harm to it. Confirm my information with the xda and internet...
Anyway.
Afair bootloader is located at /dev/block/mmcblk0p1. Don't sure about tz thing, it may be on mmcblk0p2. Not also sure if playing with tz may do irreversible brick, but it shouldn't as it is holding some drm stuff (i.e. hdmi and allshare cast transmission will not work) and you may be able to flash it in the future. But I'm not sure.
Bootloader (sbin) is not included in every firmware, too. Look for further information on the internet.
In final: find a firmware including both sbin and modem. Flash it with odin (you will have to point to the firmware file in PDA field, but also im Bootloader and Modem. You may want not to touch PIT, as it will cause further problems.
And you are back to life.
Btw if your system is turning on, you may try another method of flashing bootloader, using terminal emulator - if you are rooted.
The command is:
dd if=/sdcard/sbin.bin of=/dev/block/mmcblk0p1
Ofc using wrong path to sbin file or wrong sbin file will result in ABSOLUTELY dead device after restart.
Above is also possible with adb and windows/linux pc.
Once again: confirm all of the above with the internet/xda; this answer is only for telling you what are the clue words that you may want to earch for.
Good luck.
Sent from my GT-N8000 using Tapatalk 4
Thanks.useful info.I should probably put up with the 8000 roms.the device status even shows as official. Only annoyance is no signal icon and no ability to flash 8010 Rom without modification.
all otherwise seems fine
Sent from my GT-I9505 using Tapatalk 4
planetf1 said:
Thanks.useful info.I should probably put up with the 8000 roms.the device status even shows as official. Only annoyance is no signal icon and no ability to flash 8010 Rom without modification.
all otherwise seems fine
Sent from my GT-I9505 using Tapatalk 4
Click to expand...
Click to collapse
any solution yet? i was anxious of tasting the kitkat leak of n8000 and now im stuck with its bootloader too... any way of recovering the n8010 bootloader wthout sending to waranty ?
After reading about so many people with this n8000 bootloader problem, I am so glad I resisted and waited for the n8010 firmware. Just wish I could have air command fully working with stock n8010......
tuktukscotty said:
After reading about so many people with this n8000 bootloader problem, I am so glad I resisted and waited for the n8010 firmware. Just wish I could have air command fully working with stock n8010......
Click to expand...
Click to collapse
yeah.. i got carried away . that sucks. i hope someone is kind enough to investigate the restoring of the bootloader for us .
Here's my problem which I was trying to fix for a week now. I got a Galaxy S6 (G920FXXU3COI9 - international) which was working fine but I decided to make some improvements (tmobile wifi calling, etc). So, I decided to root the phone with new kernel (S6-UniBase_BOG8_v2) and then put a new ROM in (Rapture 2.1, my build became G920TUV2COF8). And everything works fine but when I make phone calls on tmobile tower I'm getting nasty while noise (but wifi calling, viber, etc, work just fine. 4G network works fine too but it looks like phone reception is kinda low).
So, I decided to try another ROM or change modem/BL files but Odin 3.10.7 (and 1.8) cannot pass NAND write stage. On another hand, I was able to change kernels. I also tried to reinstall samsung drivers and use another USB port - same result. Trying to flash with new BL/modem throws error on the phone "SW rev check fail device: 3 binary: 2" which doesn't show up when I try to flash ROM.
Any ideas on how to fix noise or change ROM to international or T-Mobile one? I suspect that I'm using incompatible files somewhere but I tried 4 different ROMs with the same results.
<ID:0/005> Odin engine v(ID:3.1100)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Failed in sboot.bin means your flashing an older bootloader.
Sorry to say but you cant downgrade your bootloader.
Your phone has COI9 based from what you said. Where did you get the modem/bootloader file? Im suspecting it is not on COI9 bootloader.
Just flash a latest stock firmware from sam firmware to get the latest bootloader.
batuzai04123 said:
Failed in sboot.bin means your flashing an older bootloader.
Sorry to say but you cant downgrade your bootloader.
Your phone has COI9 based from what you said. Where did you get the modem/bootloader file? Im suspecting it is not on COI9 bootloader.
Just flash a latest stock firmware from sam firmware to get the latest bootloader.
Click to expand...
Click to collapse
thanks. Thants what I thought the problem is. Can you send me the link for the latest bootloader/modem I can flash on my phone.
Do you think I can use T-mobile ROM with my international edition phone?
Dude, Im just using my phone right now, Just search your exact phone model in sammobile and download the whole firmware.
SamMobile provides original/verified/stock full firmwarw for your device. They wouldnt upload a single bootloader or modem img or bin files.
Maybe someone can share their extracted sboot.bin based from COI9. Just be sure to convert it to flashable odin file before flashing or else youll be facing some problems again. Or better, a ready made flashable odin bootloader based from COI9.
batuzai04123 said:
Dude, Im just using my phone right now, Just search your exact phone model in sammobile and download the whole firmware.
SamMobile provides original/verified/stock full firmwarw for your device. They wouldnt upload a single bootloader or modem img or bin files.
Maybe someone can share their extracted sboot.bin based from COI9. Just be sure to convert it to flashable odin file before flashing or else youll be facing some problems again. Or better, a ready made flashable odin bootloader based from COI9.
Click to expand...
Click to collapse
Many thanks, man.
I found the firmware on sams mobile but they have 5 different ones for PDA: G920FXXU3COJ1; I'm confused with CSC code. Thats why I was asking for a direct link.
Excuse my ignorance but by "convert it to flashable odin file" you mean .img to md5 conversion or something else?
And, one more question, I guess it is not a good idea to change ROM from 920F to 920T, or I should try few more 920T before giving up?
Hmm why would you want to flash a TMo version??? If I were you, just stick with your current ROM.
There is no direct link for sammobile, just forget what I've said with COI9 build number, just download the latest firmware for your region. If you find any file just pick the latest date and youll do good. It contains the latest bootloader for your phone.
Md5 thing is just for the checksum for odin. It is added for verification and its the most praticed and suggested way of creating ODIN flashable files.. But IMG will do good.
batuzai04123 said:
Hmm why would you want to flash a TMo version??? If I were you, just stick with your current ROM.
There is no direct link for sammobile, just forget what I've said with COI9 build number, just download the latest firmware for your region. If you find any file just pick the latest date and youll do good. It contains the latest bootloader for your phone.
Md5 thing is just for the checksum for odin. It is added for verification and its the most praticed and suggested way of creating ODIN flashable files.. But IMG will do good.
Click to expand...
Click to collapse
ok, finally got it fix, sorta.
Rapture 2.1 ROM gave me loud white noise during calls but the rest was working fine. The post says to flash the phone with BL and Modem files but Odin failed (I assume since I have newer BL already). So, I went back with latest G920FXX stock ROM and the phone works fine.
Can i use the option nand erase all in odin? If not someone please provide me with a pit file for my S6 SM-G920W8. I cannot flash boot loaders and anything else besides twrp.
You need to have same or newer bootloader version for your phone. Thats all.
batuzai04123 said:
You need to have same or newer bootloader version for your phone. Thats all.
Click to expand...
Click to collapse
Galaxy S6 Flat SM-G920W8 Flashing Error. Nand Write Start, FAIL! I dont know what top do,
My question is if i can flash G920F's Modem and Bootloader on my G920W8?
And why does it not say nand write start fail when i am flashing twrp?
why are you trying to flash a g920f to g920w8???
You should use the same firmware for your phone to prevent issues.
Rrgarding with your last 2 posts, it is contradicting, you mentioned you cannot flash anything besides twrp, but you followed it that you failed in flashing twrp.
If you encountered with flashing firmware, I suggest to use a G920W8 firmware that is latest. I assume you are using an old firmware. Tell us your current and your firmware you are flashing.
Where did you get the twrp version? Are you sure it is not corrupt? A valid ODIN file? .md5 or .tar?
You need to give us more details in your issues.
Nand write start fail
I have solved using Odin3 v3.10.7 with firmware VZW-G920VVRU4BOK7-20151211140939 and Windows 7 for Galaxy S6 SM-G920V
So ummmm... Slight noob here. I searched this thread (http://forum.xda-developers.com/gal...e-deodexed-mod-edition-1-0-t3094423/page1630) to see if it works on G920p and found comments saying it does. Being overjoyed I flashed it. Ran into touchscreen problems so I flashed the correct kernel. It works pretty good except I don't have root for whatever reason. I tried cf auto root... No go. So I just wanted to back to stock and give up finding Roms for this device BUT Odin keeps giving me a fail message like this
Added!!
Odin engine v(ID:3.1005)
File analysis..
SetupConnection..
Initialization..
Get PIT for mapping..
Firmware update start..
SingleDownload.
shoot.bin
NAND Write Start!!
FAIL!
Complete(Write) operation failed
Can anybody help me. I never had this problem it usually works. Is it because I flashed firmware that wasn't based on G920p???
Troundtree97 said:
So ummmm... Slight noob here. I searched this thread (http://forum.xda-developers.com/gal...e-deodexed-mod-edition-1-0-t3094423/page1630) to see if it works on G920p and found comments saying it does. Being overjoyed I flashed it. Ran into touchscreen problems so I flashed the correct kernel. It works pretty good except I don't have root for whatever reason. I tried cf auto root... No go. So I just wanted to back to stock and give up finding Roms for this device BUT Odin keeps giving me a fail message like this
Added!!
Odin engine v(ID:3.1005)
File analysis..
SetupConnection..
Initialization..
Get PIT for mapping..
Firmware update start..
SingleDownload.
shoot.bin
NAND Write Start!!
FAIL!
Complete(Write) operation failed
Can anybody help me. I never had this problem it usually works. Is it because I flashed firmware that wasn't based on G920p???
Click to expand...
Click to collapse
You can encounter that problem when PIT or modem or bootloader are incorect for a rom version you're trying to flash with Odin. Did you manually flashed some modem/bootloader when you were flashing that custom rom? And which version of stock rom are you trying to flash with Odin?
mildj84ns said:
You can encounter that problem when PIT or modem or bootloader are incorect for a rom version you're trying to flash with Odin. Did you manually flashed some modem/bootloader when you were flashing that custom rom? And which version of stock rom are you trying to flash with Odin?
Click to expand...
Click to collapse
No i didn't install anything besides the ROM. I tried installing all the MM files for the s6 found here http://updato.com/firmware-archive-select-model?r=SPR&v=Marshmallow(Android+6.0.1)&q=SM-G920P. It used to work before i flashed this ROM. Now i get a "fail" message every time.
Have you tried the firmware that officially came with yours?
I had once the same problem with a friends G925F which I tried the latest version of MM on and had the same issue. When installing back the firmware of our country it succeeded.
And you can always try Smart Switch the Emergency Recovery function.
RDDraco said:
Have you tried the firmware that officially came with yours?
I had once the same problem with a friends G925F which I tried the latest version of MM on and had the same issue. When installing back the firmware of our country it succeeded.
And you can always try Smart Switch the Emergency Recovery function.
Click to expand...
Click to collapse
If you mean "out of the box" then no. I did try to flash the official MM for my Sprint version. No luck
Hi everyone,
I do have a Snapdragon S22 Ultra that is currently running SM9080.
However, non of the CSC versions available for this firmware has eSim support.
Therefore I would like to try flashing the SM908E firmware (which should have eSim support) and which is also a snapdragen hardware.
My problem right now is that ODIN does not flash the different firmware onto the phone, so I'm looking for help on how to technically do that.
What I've tried so far:
Tried to flash BL/AP/CP/CSC files *without* "re-partition" option enabled.
This gives the error "Re-Partition operation failed."
Tried to flash BL/AP/CP/CSC files *with* "re-partion" option enables and a PIT file selected.
This ends up with Odin reporting "SetupConnection..." and then basically freezing for some time until it reports "Complete(Write) operation failed."
Note the Device is currently not yet rooted.
So I'm a little bit lost now what the problem is and how to do the next step ....
Any suggestions or ideas are highly welcome!
Further info: I've now also tried to
unlock the bootloader
root the AP file with magisk
Nothing helps to.
I can flash e.g. a magisk-rooted firmware SM-S9080 but I can't flash S908E.
This is the error message that I get when trying to use the "re-format" option and also select the PIT file.
<ID:0/005> Odin engine v(ID:3.1401)..
<ID:0/005> File analysis..
<ID:0/005> Total Binary size: 10810 M
<ID:0/005> SetupConnection..
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Thanks for trying... I'm not sure if its going to work... I have the SM9080 as well.
SamLux said:
Hi everyone,
I do have a Snapdragon S22 Ultra that is currently running SM9080.
However, non of the CSC versions available for this firmware has eSim support.
Therefore I would like to try flashing the SM908E firmware (which should have eSim support) and which is also a snapdragen hardware.
My problem right now is that ODIN does not flash the different firmware onto the phone, so I'm looking for help on how to technically do that.
What I've tried so far:
Tried to flash BL/AP/CP/CSC files *without* "re-partition" option enabled.
This gives the error "Re-Partition operation failed."
Tried to flash BL/AP/CP/CSC files *with* "re-partion" option enables and a PIT file selected.
This ends up with Odin reporting "SetupConnection..." and then basically freezing for some time until it reports "Complete(Write) operation failed."
Note the Device is currently not yet rooted.
So I'm a little bit lost now what the problem is and how to do the next step ....
Any suggestions or ideas are highly welcome!
Click to expand...
Click to collapse
You should just be able to flash the home csc in Odin. I currently have a 908e with the 908w csc installed this way.
I suggest you flash twrp if you want to change different model.
Try with a Patched Odin? https://forum.xda-developers.com/t/patched-odin-3-13-1.3762572/
Any look over here?
No luck so far ...
Tried the "patched Odin" -> same propblem
Tried to flash only the CSC file with ODIN -> doesn't work
Installed TWRP according to this guide Link but when I try to install any of firmware ZIP files then I get the error message that the ZIP file is not okay.
So what help now would be if I know how I can use TWRP to maybe flash one of the downlaoded firmware files.
Any idea?