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 .
I flashed my stock unrooted n8010 with the n8000 leak files using odin, I did not used the modem. All good and everything working.
Now I want to get back to stock n8010 jb. When in download mode the device apears like n8000 and odin is not able to flash the stock n8010 firmware.
I installed twrp and rooted, modified buildprop to apear like n8010 and tried to flash a custom rom for n8010, no luck, I get a message that the rom is for n8010 and to try a rom for my device.
How can I trick twrp or odin to make them flash n8010 fw/rom ?
I don't have a nandroid backup,
Edit : I managed to flash 4.0.4 with odin (N8010XXALGC_N8010OXXALG4_COA). After the flash it was stuck at samsung logo, I rebooted in recovery (power+volume up, release only power at samsung...) and wiped cache, wiped data and reset. Now the device booted with android 4.0.4 and I'm downloading a 568.29 MB update. I'll see what happends next...
The goal is to get back to stock jb, official (with triangle away I gues)
Edit: I updated to JB, but when in download mode the device is still N8000, so the problem is still not solved.
Sent from my GT-N8010 using Tapatalk
KoRoZIV said:
I flashed my stock unrooted n8010 with the n8000 leak files using odin, I did not used the modem. All good and everything working.
Now I want to get back to stock n8010 jb. When in download mode the device apears like n8000 and odin is not able to flash the stock n8010 firmware.
I installed twrp and rooted, modified buildprop to apear like n8010 and tried to flash a custom rom for n8010, no luck, I get a message that the rom is for n8010 and to try a rom for my device.
How can I trick twrp or odin to make them flash n8010 fw/rom ?
I don't have a nandroid backup,
Edit : I managed to flash 4.0.4 with odin (N8010XXALGC_N8010OXXALG4_COA). After the flash it was stuck at samsung logo, I rebooted in recovery (power+volume up, release only power at samsung...) and wiped cache, wiped data and reset. Now the device booted with android 4.0.4 and I'm downloading a 568.29 MB update. I'll see what happends next...
The goal is to get back to stock jb, official (with triangle away I gues)
Edit: I updated to JB, but when in download mode the device is still N8000, so the problem is still not solved.
Sent from my GT-N8010 using Tapatalk
Click to expand...
Click to collapse
What version of Odin are you using ?Did you try to remove micro SD and full erase you tablets internal memory card? And why not 4.1.2 you install and not 4.0.4?
Because 4.1.2 gives me error, tried 3 versions of Odin: 3.04, 3.09, and 1.85. Tried 4.1.2 from 3 different sources to avoid a bad download. I can only flash 4.0.4, android shows me n8010 but in download mode is still n8000. I have no idea why, I just can't get rid of the n8000 in download mode.
Maybe I need to flash separate files, just like I did with 4.4.2, bootloader. Ap , csc but I don't know where to get those files for 4.1.2, I only have .tar.md5 files.
I attached a ss with odin eror when trying to flash stock 4.1.2
Sent from my GT-N8010 using Tapatalk
KoRoZIV said:
Because 4.1.2 gives me error, tried 3 versions of Odin: 3.04, 3.09, and 1.85. Tried 4.1.2 from 3 different sources to avoid a bad download. I can only flash 4.0.4, android shows me n8010 but in download mode is still n8000. I have no idea why, I just can't get rid of the n8000 in download mode.
Maybe I need to flash separate files, just like I did with 4.4.2, bootloader. Ap , csc but I don't know where to get those files for 4.1.2, I only have .tar.md5 files.
I attached a ss with odin eror when trying to flash stock 4.1.2
Sent from my GT-N8010 using Tapatalk
Click to expand...
Click to collapse
Did you have success installing the bootloader of the leak kitkat rom? Cause mine failed always, the AP file is the 1 working on me only. I have downloaded this TAR_MD5_PACKAGER here( http://forum.xda-developers.com/showpost.php?p=42393470&postcount=2 ) that I'm using to repack the stock and using 7zip to extract the content of the .tar.md5 files, maybe you can try repacking it seperately using this 2 program. And try to install it using Odin( I'm using Odin 1.85). By the way you can still install custom 4.1.2 rom's right, specifically for 8010 ? Lastly why do you wanna go back to stock 4.1.2 do you have problem with the leak rom?
P.S. Did you format your internal memory as I suggested? Cause once I install back to 4.1.2 have error before and have to install twice the rom( that is according to my experience which some think its not relate to installing error).maybe you can try to format all from the system to the internal memory via CWM recovery /mount section.Then try to install again and remove the SD card too.
I had no problems with the kit Kat files, flashed at the same time bl, csc and ap (no modem). I used odin 3.09. I managed to get back to 4.1.2 by flashing stock 4.0.4 then using OTA (im surprised it worked) . Someone else flashed directly 4.1.2 with mobile odin and worked, but with odin from pc you get an error.
The problem is that in download mode appears like n8000; hopefully, when official kk for n8010 is out we'll be able to fix that.
Sent from my GT-N8010 using Tapatalk
KoRoZIV said:
I had no problems with the kit Kat files, flashed at the same time bl, csc and ap (no modem). I used odin 3.09. I managed to get back to 4.1.2 by flashing stock 4.0.4 then using OTA (im surprised it worked) . Someone else flashed directly 4.1.2 with mobile odin and worked, but with odin from pc you get an error.
The problem is that in download mode appears like n8000; hopefully, when official kk for n8010 is out we'll be able to fix that.
Sent from my GT-N8010 using Tapatalk
Click to expand...
Click to collapse
Glad you manage to resolve some of your problem.Plese ignore my post above your's then.
The problem is not solved lol. I just gave up for the moment. It's a miracle that I didn't bricked the damn thing today
I'll stay with a 4.1.2 stock n8010 fw that is using an n8000 4.4.2 bootloader. Sexy
Sent from my GT-N8010 using Tapatalk
Well from everything I've read it seems the problem is that when we flashed the kitkat leak, flashing the bootloader is what allowed us to flash n8000 over our n8010. This could be why when we flash back using odin we get the error cause the bootloader isn't being flashed too so it's trying to flash n8010 onto what it reads as n8000. It seems that there are only a few solutions. 1we need to find a n8010 bootloader file which so far seems to be impossible to find. 2you can flash an original n8010 cmw or twrp back up it will return you to 4.1.2 n8010 but the bootloader will still be n8000. If this option isn't available to you then you can try 3 download a custom rom I have the darkmans customers stock as a backup and it still works going back to simple stock n 8010 but again the bootloader stays as n8000...
Basically until we can get an n8010 bootloader we are stuck with it...
I even rooted the 4.4.2 leak and tried to flash a custom 4.4.2 made for n8010 and did not let me (based on the same leak i think, so the same bootloader) and failed, twrp sees the device as n8000 and did not allowed me to use n8010 rom.
KoRoZIV said:
I even rooted the 4.4.2 leak and tried to flash a custom 4.4.2 made for n8010 and did not let me (based on the same leak i think, so the same bootloader) and failed, twrp sees the device as n8000 and did not allowed me to use n8010 rom.
Click to expand...
Click to collapse
I think I read somewhere that twrp can have issues with flashing 4.4.2 roms it needs to be the most up to date version of twrp... I tried cm 11 before and had to change to Cwm. But I went back to twrp and now it works
I used twrp 2.7, I think it's the latest.
Edit:
I reached a binary counter of 118
I used triangle away and reset it, however I'm still stuck with the n8000 4.4.2 bootloader.
N8000 bootloader
Same issue here, stuck on N8000 bootloader on my GT-N8010. After endless research I still can't find any solution but now the thing is, the official 4.4.2 KK is availble for the GT-8010, you guys think this is the solution, because I have read that though updating to the official Rom (via Odin Mobile) because Odin desktop fails, the device would still be stuck on the annoying N8000 bootloader?
Yes, even if you flash the n8010 4.4.2 with mobile Odin you will still have the damn n8000 bootloader.
Sent from my Nexus 5 using Tapatalk
KoRoZIV said:
Yes, even if you flash the n8010 4.4.2 with mobile Odin you will still have the damn n8000 bootloader.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Any way of downgrading the Bootloader, I've heard of a nandroid backup but I didn't do that before updating, is it possible to find one on the web?
You need a nandroid from a similar device, is possible but not sure if it will solve the problem.
Sent from my Nexus 5 using Tapatalk
KoRoZIV said:
You need a nandroid from a similar device, is possible but not sure if it will solve the problem.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I thought the official Rom would fix this but visibly no. So we don't have a choice of being stuck with the damn N8000 bootloader?
At the moment there is no solution that I know of.
Sent from my Nexus 5 using Tapatalk
N8010 on N8000 bootloader
Hi guys, isn't there a solution about this yet? I have the exact same problem with the N8000 bootloader, my device is a N8010 16GB from mexico and flashed the leaked N8000 kk stock rom. I will still look for a solution. TKS to all of you.
Mean time solution
Hi Guys, I found a way to flash te new N8010XXUDNE4 on the stuck n8000 bootlader, the bootloader problem remains, but it is possible to flash the n8010 stock rom via mobile odin, I did it and it's fully working, But I flashed a N8010XXUDNE4 customized without sboot.bin so it can be flashed via PC odin too, I'm still not allowed to post links here cause I'm new in forums so if you want the link to that rom let me know how to provide it to you.
Possible solution?
Have a look at my thread, does that look a viable approach?
http://forum.xda-developers.com/galaxy-note-10-1/help/recovering-n8010-leaked-locked-n8000-t2802516
ambmar78 said:
Hi Guys, I found a way to flash te new N8010XXUDNE4 on the stuck n8000 bootlader, the bootloader problem remains, but it is possible to flash the n8010 stock rom via mobile odin, I did it and it's fully working, But I flashed a N8010XXUDNE4 customized without sboot.bin so it can be flashed via PC odin too, I'm still not allowed to post links here cause I'm new in forums so if you want the link to that rom let me know how to provide it to you.
Click to expand...
Click to collapse
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
Ok guys, Could be a simple answer. I currently have an S6 and it is unlocked and currently on German Vodafone. I have attempted to revert it to BTU firmware as I'm in the UK. I followed all the available guides to achieve this via odin but it failed almost immediately. It failed at Hidden.img I think? Anyway the phone then failed to start up and took me straight to an error screen telling me to connect it to smart switch. I then found out how to fix it and managed it so phone up and running again. Is it possible to flash the BTU firmware in the first place?
Thanks
Come on guys, surely there must have been someone out there with the same problem as me and has managed to overcome it?
The answer is:
extract the Firmware with winrar and extract the hidden.img separat to your Desktop. rename it to hidden.img.tar and Flash that again (AP), after that your phone should reboot. if not, go into recovery make a reset. Here is a link in german:
https://www.androidpit.de/forum/670145/samsung-galaxy-s6-s6-update-problem-hidden-img-fail
That's how I solved the problem with the phone going into error. I need to know if it is possible to flash the firmware BTU to my phone?
sinbrad said:
I need to know if it is possible to flash the firmware BTU to my phone?
Click to expand...
Click to collapse
It's 100% possible but check first if the rar file is not corrupted.
I had problem with corrupted files failed in odin.
Ok, I completed yet another download of the firmware for BTU but once again the flash failed. I had to carry out flash with hidden.img.tar in order to restore phone. I don't understand why this is happening? Any ideas?
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