I am having issues flashing my phone with Odin, Odin says it is starting to write Nand but it just stays like that for a minute or so then it says it failed to write Nand. I have tried Odin 3.07 and 3.09 but get the same error each time. My phone is a UK model (from Amazon UK GT-I9205ZKABTU). I am attempting to flash Kitkat BTU, not sure what versions I was on before!.
To cut a long story short a while back I attempted to root it, I flashed CWM with Odin, this seemed to flash fine so and I rooted. The phone never didn't appear to be fully rooted as I could root apps that required root access but apps like Skygo said the phone was rooted!. The other night I was on my phone and it crashed, when I went to power it back on it would only boot as far as the white writing that states model number then it would switch itself off, when I connected the charger the phone would display the battery image but didn't appear to charge and I also could get into recovery. I them attempted to re-flash custom recovery, flashed but now the phone says something like software update failed and I cannot access recovery but I can access download mode.
A couple of questions if I may;
1. Would I get the Nand Write fail error if I am flashing the incorrect firmware for the phone?
2. Would I get the Nand Write fail error if the charger port is not working as it should?
3. Where is the best place to download stock roms?, even if I get an older version I don't mind.
Any ideas guys?
newgen2005 said:
-cut-
A couple of questions if I may;
1. Would I get the Nand Write fail error if I am flashing the incorrect firmware for the phone?
2. Would I get the Nand Write fail error if the charger port is not working as it should?
3. Where is the best place to download stock roms?, even if I get an older version I don't mind.
Any ideas guys?
Click to expand...
Click to collapse
1. Yes - you have to choose firmware for your model of phone
2. Yes - try to change USB cable (for original) and use USB port on the back of your PC (from Main Board). No hubs between phone and PC.
3. HERE or HERE
In such state the best way is to flash by Odin stock firmware for your model. Then with functionality restored you can try once more to install custom ROM.
Thanks for your help trurl3, I will try again when I get home.
I have tried on another PC and I getting the same nand write error. I am searching for stock firmware but I am not sure if my phone is LTE!, when I go into download mode is says the product name is GT-I9205. I am trying to flash this I9205XXUDOA1_I9205BTUDOA1_I9205XXUDOA1_HOME.tar.md5, is this the correct firmware?. I purchased the phone from Amazon.co.uk direct (sim free). Is it possible I may have a none GT-I9205?
Even tried Kies, I put in model and serial number, Kies is happy, Kies downloads the relevant firmware 100% but fails then comes up with an error message!. The only issue I can think of with Kies is that I am unable to get the phone in recovery, only download mode!, phone also won't connect to Kies!
Hmmm... let's try to install custom recovery for beginning... I recommend to try Philz touch recovery. HERE is tutorial for instalation. If it succeed you will have first outpost for further moves. Although tutorial is meant for Galaxy S4 and (no offence) dummies, installation is the same for all Samsung phones. Only IMPORTANT DIFFERENCE is version of recovery file - it should be meant for Mega which code name is 'meliuslte" so you have to download CWM recovery file from HERE. You will need to download newest file with .tar extension.
Thanks for your help, very much appreciated. I will look at installing custom recovery tonight, will custom recovery still install even if the phone firmware is corrupt/incomplete?.
Yes it should. Only reflashing full stock firmware reverts all custom changes. Of course it depends of character of corruption. Recovery it is one of partitions of Android's file system. If get corrupted then will not work.
Official firmware contains whole sytem and flashing stock firmware you replace all Android's partitions in your phone so you have to use 'download mode' and Odin on PC to flash, because recovery is delted and reinstated during upgrade. Flashing custom ROM's replace not all partiions ( i.e not replace bootloader or recovery). For that you can install custom ROM's from custom recovery, but not stock recovery as them have not all needed functions. Having custom recovery is a must for modding your phone . Using custom recovery you can root it and then install custom ROM.
As we talk about custom ROM I can recommend for you very good custom ROM bult on base stosk TWRP from @megalomanic14. You can find information from link in my sig. There is MegaFire on baze Android 4.2 and MegaKat on baze 4.4. Both ROMs are prerooted already.
trurl3 said:
Yes it should. Only reflashing full stock firmware reverts all custom changes. Of course it depends of character of corruption. Recovery it is one of partitions of Android's file system. If get corrupted then will not work.
Official firmware contains whole sytem and flashing stock firmware you replace all Android's partitions in your phone so you have to use 'download mode' and Odin on PC to flash, because recovery is delted and reinstated during upgrade. Flashing custom ROM's replace not all partiions ( i.e not replace bootloader or recovery). For that you can install custom ROM's from custom recovery, but not stock recovery as them have not all needed functions. Having custom recovery is a must for modding your phone . Using custom recovery you can root it and then install custom ROM.
As we talk about custom ROM I can recommend for you very good custom ROM bult on base stosk TWRP from @megalomanic14. You can find information from link in my sig. There is MegaFire on baze Android 4.2 and MegaKat on baze 4.4. Both ROMs are prerooted already.
Click to expand...
Click to collapse
Hopefully the custom recovery will flash without any errors, I will post back tonight with the outcome.
I also have a Galaxy Note running a custom rom. I installed that last year through custom recovery that I flashed. For some reason the Note seems to be more root and custom recovery friendly .
Once I have custom recovery on the Mega I will be happy, I will have a little confidence that my Mega is not completely broken.
I hope so. I had not any problem with flashing custom ROMs on my Mega. Yesterday flashed CM12.1 to the test how it looks Lollipop on Mega . But wasn't satisfyied... so went back to my 4.2 with MegaFire. Although there is new 4.4 for Mega I am not eager to upgrade...
trurl3 said:
I hope so. I had not any problem with flashing custom ROMs on my Mega. Yesterday flashed CM12.1 to the test how it looks Lollipop on Mega . But wasn't satisfyied... so went back to my 4.2 with MegaFire. Although there is new 4.4 for Mega I am not eager to upgrade...
Click to expand...
Click to collapse
I am hoping to get my Mega up and running again so I can check out how a custom rom works on it. I love the phone but the internal storage is a nightmare. Ideally I want to be able to at least root and be able to install apps to SD and remove some of stock Samsung stuff. I am always getting low on storage warnings, really annoying when I got a 64gb SD card in the phone!
IMHO the best for Mega is to install MegaFire ROM from @megalomanic14. This custom rom is unbranded, prerooted and heavily improved by developer. There is too version X which is debloated from most unnecessary aps.
Not having much luck, now Odin doesn't even attempt to write anything as it is stuck at "initialization". I tried it on 3 different computers, it seems to being doing this since Kies was used last night!. Reinstalled usb drivers etc .Any ideas?
I have tried an older of Odin (3.06) and I get this when trying the custom recovery and stock rom!
PHP:
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Is this a connection issue or am I really lacking the pit partition and do I need to include a GT-I9205 pit file with the stock firmware or custom recovery I am flashing?. I have done a little research regarding the pit file but I am a little confused on what I need to do, I don't want to mess things up even more!. If I need to include a pit file can I just download one someone else has created?.
Thanks
I downloaded a pit file and tried to flash it with stock rom and custom recovery but it didn't work.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I am sorry, it's above me... i can not help you any more. Unfortunately it looks like hardware issue, byt maybe I'm wrong... hopefully...
Thanks for all your help. I a real shame it won't flash!
please re install your usb driver samsung.
and make sure debugging enable before install
use another odin. 1.85 or 3.09
right click odin, run as administrator
Related
I own a Samsung Galaxy S II i777. I've already rooted the phone. I'm about to flash UnNamed ROM over my stock ROM, but I have questions before I feel comfortable doing anything.
(1) I read about backing up my data and stock ROM. I've backed up my data using Titanium Backup, but the ROM is giving me problems. I've installed the ROM Manager app (via Android Market) and flashed the Clockwork Mod 3e through the app. But when I try to backup my stock ROM, at the reboot screen the app gives me an error "E: can't find signature" or something like that, and the backup fails. How can I make a backup (I think it's called a Nandroid backup?) of my stock ROM in case I want to revert?
(2) The procedure I want to follow for everything is here. My goal is to flash anything & everything without incrementing the flash counter (using Mobile Odin Lite, as outlined in the procedure). Is this realistic? What, in general, should I avoid so as not to increment the flash counter?
(3) The app I'm going to be using to flash is Mobile Odin Lite. Is that the same as flashing with Clockwork Recovery? Does using Clockwork Recovery Mod to flash increment the flash counter?
(4) Let's say I want to install a different custom ROM, or an update for UnNamed ROM comes out. Will I be able to do that with Mobile Odin Lite, and without incrementing the flash counter? Can I just flash (using Mobile Odin Lite) over the previous ROM?
Completely_Clueless said:
I own a Samsung Galaxy S II i777. I've already rooted the phone. I'm about to flash UnNamed ROM over my stock ROM, but I have questions before I feel comfortable doing anything.
(1) I read about backing up my data and stock ROM. I've backed up my data using Titanium Backup, but the ROM is giving me problems. I've installed the ROM Manager app (via Android Market) and flashed the Clockwork Mod 3e through the app. But when I try to backup my stock ROM, at the reboot screen the app gives me an error "E: can't find signature" or something like that, and the backup fails. How can I make a backup (I think it's called a Nandroid backup?) of my stock ROM in case I want to revert?
(2) The procedure I want to follow for everything is here. My goal is to flash anything & everything without incrementing the flash counter (using Mobile Odin Lite, as outlined in the procedure). Is this realistic? What, in general, should I avoid so as not to increment the flash counter?
(3) The app I'm going to be using to flash is Mobile Odin Lite. Is that the same as flashing with Clockwork Recovery? Does using Clockwork Recovery Mod to flash increment the flash counter?
(4) Let's say I want to install a different custom ROM, or an update for UnNamed ROM comes out. Will I be able to do that with Mobile Odin Lite, and without incrementing the flash counter? Can I just flash (using Mobile Odin Lite) over the previous ROM?
Click to expand...
Click to collapse
(1) DO not use rom manager. It has problems on this phone. You can install a custom kernel and then make a nandroid backup of the stock system plus custom kernel. However, there is a return to stock package which you can flash to get total stock.
(2) (3) (4) Please go to the guide you linked, scroll down to the bottom of the guide, and read step 4. Then if you have an analytical mind and want to know more about how things work, click on the link at the end of the Discussion section titled "Here is some additional information for noobs about the tools and techniques used in this guide."
Please be assured that you can flash custom binaries without tripping the flash counter. That is what the guide is all about, after all.
creepyncrawly said:
(1) DO not use rom manager. It has problems on this phone. You can install a custom kernel and then make a nandroid backup of the stock system plus custom kernel. However, there is a return to stock package which you can flash to get total stock.
Click to expand...
Click to collapse
Ah OK, and I think I did find the return-to-stock package; is it the "Odin3 One-Click Downloader Stock I-777 UCKH7 No Bootloaders" you posted here?
creepyncrawly said:
(2) (3) (4) Please go to the guide you linked, scroll down to the bottom of the guide, and read step 4. Then if you have an analytical mind and want to know more about how things work, click on the link at the end of the Discussion section titled "Here is some additional information for noobs about the tools and techniques used in this guide."
Please be assured that you can flash custom binaries without tripping the flash counter. That is what the guide is all about, after all.
Click to expand...
Click to collapse
Okay, sorry for coming across as noob. I read the noob-explanation post, and from what I gather, as long as I don't use Odin or Heimdall, I shouldn't trip the flash counter and get that yellow exclamation point? EDIT: Nevermind, figured this one out.
Now, I've already installed ROM Manager and used it to flash the custom kernel. If I uninstall using Titanium Backup, will that undo the flashing that it did? It won't conflict when I flash using Mobile Odin Lite, will it?
Completely_Clueless said:
Now, I've already installed ROM Manager and used it to flash the custom kernel. If I uninstall using Titanium Backup, will that undo the flashing that it did? It won't conflict when I flash using Mobile Odin Lite, will it?
Click to expand...
Click to collapse
I'm not sure what you mean. To my knowledge you cannot install a kernel with ROM Manager. However, I have not installed or even looked at the program since I acquired the SGS II in early October. When I used ROM Manager on the Captivate in Fall 2010, when Captivate was still on Eclair (Android 2.1), it used the stock recovery to install a custom recovery as an update. But since our phone has 3e recovery, requiring files that are flashed to be signed by Samsung, my understanding it that ROM Manager can not flash a ClockworkMod Recovery onto our phone. To my knowledge, you can flash a custom kernel on our phone only with Odin3, Heimdall, adb, Android Terminal Emulator, Mobile Odin, or ClockworkMod Recovery.
I don't see why you would keep ROM Manager, since there is very little that it can do to help you.
As far as how to proceed, I think it would be advisable to follow the Guide from the beginning, even if it means doing something redundantly.
Oops, I think I got the terminology mixed up. I meant I used ROM Manager to flash ClockworkMod Recovery.
Here's a picture of what I'm talking about (taken from the ROM Manager page on the Android Market website, not my phone, but the option is still the same). I did the first option, and I was just wondering if the "flash" was permanent even if I uninstalled the app itself using Titanium Backup. I was just concerned that if I flashed using two tools, then there would be a problem.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
But I followed your guide, and I just successfully flashed my first custom ROM! My phone booted without a hitch, so I assume flashing ClockworkMod Recovery with ROM Manager first didn't have any negative impact. I also didn't see any yellow exclamation point.
Thank you very much for your help ! I've bookmarked your threads about going back to stock and about how to flash without increasing the flash counter.
Not sure if you actually flashed anything from rom manager, regardless of what the screen says.
Anyway, success is sweet. Enjoy your phone.
So I wanted to install the new Android 6.0 for a few days ago. I accidentally installed the 6.0 bootloader first, and the phone i just stuck. I have installed the newest TWRP recovery and tried flashing stock rom ANDROID 5.1.1 , i also tried use smart manager to emeregency recover the phone... nothing semms to work, please help me. Every time im trying to flash a new rom in odin i just says NAND WRITE START!! FAIL!!
Well make sure that your is usb is ok, try on diffrent computer that your device has not been connect because the marshmallow diffrent set of drives , Try re download the copy of the firmware it might get damaged during downloading. Try to use the old tested kies it is more stable...
Hello.
I am currently trying to bring my Samsung Galaxy SII (GT-I9100) to a current CM version. The phone is completely untouched and has never had any custom upload or anything similar.
The problem now is, while there are loads and loads of guides out there, all of them seem very old - and different. One says i need heimdall, other says odin, others seem way easier just adding the files to my SD card and installing through recovery - and basically all that does is confusing the hell out of me.
So, first things first - the most important thing seems to get root access - i've done that successfully using the "How To Root Samsung Galaxy SII GT-I9100"
The one thing that confuses me now is - where is CWM? I thought i installed it using that root method?
Another method i tried before updated my recovery while it was running from the stock one to CWM - but after rebooting into recovery it was the stock one again.
SO i am even more confused now as before.. At least i hope that my phone is and stays rooted, so that is a plus.
The question now is, what am i missing?
Were all of these CWM things i've "installed" just temporary? Where do i get the full version, and how do i install it?
Basically what i'm asking is, is there a current guide for all of the flashing? Can anyone maybe guide me through it? I mean, nowadays it seems the S2 should be flashed very easily, and i'm guessing it's just getting the correct CWM version and flashing it via recovery - but since i'm not sure, i'm asking for some guidance.
The easiest way to get a CWM custom recovery is to flash PhilZ recovery through your standard stock 3e recovery.
Look for your Android build number (under settings>>about device/phone) then go to the PhilZ thread......
http://forum.xda-developers.com/showthread.php?t=1877270
download the matching kernel/recovery zip (NOT .tar), copy to a micro SD card (or possibly even internal storage I can't be sure of that....It's been a while since I rooted my S2), boot into recovery and flash......
Simple as......
Edit....The thread states 'external sd card' so forget about using internal storage......
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks a lot, worked flawlessly!
I hope it is okay that i just ask about the next steps here.. Since i immediately ran into new problems.
So, i booted into the CWM and tried to push my cm package that i want to install via mfastboot-v2 and it failed stating the following errors:
Warning: No file_contextdetected filesystem ext4 for /dev/block/mmcblk0p9
Can't install this package on top of incompatible data. Please try another package or run a factory reset.
E: Error in /tmp/update.zip
(Status 7)
Installation aborted
It seems obvious ofcourse that i need to do a factory reset before, but the S2 is probably susceptible to a superbrick and i should not do that factory reset on my stock rom.
The question is - what now? Also i was not able to mound the external SD card in CWM.
ThePatchelist said:
Thanks a lot, worked flawlessly!
I hope it is okay that i just ask about the next steps here.. Since i immediately ran into new problems.
So, i booted into the CWM and tried to push my cm package that i want to install via mfastboot-v2 and it failed stating the following errors:
Warning: No file_contextdetected filesystem ext4 for /dev/block/mmcblk0p9
Can't install this package on top of incompatible data. Please try another package or run a factory reset.
E: Error in /tmp/update.zip
(Status 7)
Installation aborted
It seems obvious ofcourse that i need to do a factory reset before, but the S2 is probably susceptible to a superbrick and i should not do that factory reset on my stock rom.
The question is - what now? Also i was not able to mound the external SD card in CWM.
Click to expand...
Click to collapse
1) I can't comment on mfastboot v2 as I have no experience of using it.
2) which CM package are you trying to install?
3) the super brick bug only affects android 4.0.4 Icecream Sandwich....
And PhilZ kernels have removed/patched the EMMC_cap_erase command that activates the 'bug' anyway.
4) if your CM package came from XDA or the CM website, then it should install through PhilZ recovery.
5) what are you trying to achieve that requires external SD to be mounted?
The cm i'm trying to install is the latest stable one, being cm-12.1-20151116-SNAPSHOT-YOG7DAO1JN-i9100
About the superbrick, i did not know that the philZ kernels fixed that, good to know.
And i tried to simply put the ROM image onto the external SD card to simply flash it from the CWM - but since that external SD card cannot be mounted, i tried using the adb push method.
Could i use the internal storage and simply apply update from zip file from there? Thought that might be an issue due to it being erased in the process?
CM 12 is lollipop base isn't it? The last CM I flashed to my S2 was 11.....but then my eldest son asked me for a phone so I returned it to stock and loaned it to him.
Obviously haven't been able to flash it since.
As for CM12, I've read that overall, it's not as stable as 11 (contains more bugs) and is heavier on the battery. I'm sure I've also read that the S2s memory partitions have to be re - mapped @gsstudios maybe you can help here as I'm not sure)
As far as I am aware, installing the rom from internal storage shouldn't be an issue......The only time data on that partition is compromised is if you perform a factory reset....and you would only have to do this (if at all) AFTER you have installed the rom. I'm also fairly sure that you have to have a specific version of CWM installed to be able to install newer CM roms, but again, I'd have to suggest waiting for @gsstudios to comment here......
ThePatchelist said:
The cm i'm trying to install is the latest stable one, being cm-12.1-20151116-SNAPSHOT-YOG7DAO1JN-i9100
About the superbrick, i did not know that the philZ kernels fixed that, good to know.
And i tried to simply put the ROM image onto the external SD card to simply flash it from the CWM - but since that external SD card cannot be mounted, i tried using the adb push method.
Could i use the internal storage and simply apply update from zip file from there? Thought that might be an issue due to it being erased in the process?
Click to expand...
Click to collapse
Hi,
There are a few points I will give:
- cm-12.1-20151116-SNAPSHOT-YOG7DAO1JN-i9100 is an old build of CM12.1. It doesn't have all of the latest features like Isorec (isolated recovery for TWRP 3 recovery support), hence it should be avoided. Instead, use CM12.1 Unofficial by CNBLACK or CM12.1 Unofficial by Markox89. Although they are unofficial builds, these are considered more stable than the CM12.1 snapshot build being offered.
- You can install CM12.1 via internal storage. It won't get erased during the flashing process, instead, this only happens when you re-partition your phone using a .pit file. You will need to increase you system partition size in order to flash gapps (google play store, etc) using Lanchon's repit tool. Documentation is already provided.
- Once you've installed CM12.1, it is recommended to change the recovery to TWRP (preferred) or CWM. This is because CM recovery is very limited and will become a problem later if you decide to flash CM13.
gsstudios
Hey there again.
First of all, thank you very much! I successfully flashed one of the cm's you posted @gsstudios and so far it works.
Now though i am struggling with the TWRP installation since i have to increase the partition size for gapps.. As i've read it TWRP must be flashed via heimdall (back to square one..) and there i am having problems with the connection (claiming interface error, was googling for 2 hours now, nothing helped)
Basically what i am now looking for is a way to get TWRP without having to flash via heimdall, but rather installing it through the cm recovery which seems not possible?
I am really sorry that i continue to post my issues here since i'm sure you guys helping out are really annoyed by this.. But currently i am again running my head into a brick wall not knowing how to proceed :/
Edit: jesus..
I have no idea how or why, but apparently i got it now.
I installed ROM manager externally and it showed me that i have CWM and TWRP already installed.. At first i was confused and set up TWRP as my recovery, but that only booted into the normal cm recovery. Then i tried the CWM one and when going into recovery i am now in TWRP.. Am reformatting my partitions, so far without any errors.
I am not less confused but close to being happy. As soon as i can flash gapps afterwards all of this is over and done.
Thanks still, for all the help guys! And sorry for being the usual annyoing user..
No problem fella....but in future, STAY AWAY from rom manager.....It sometimes doesn't play nice with the S2.
In the past I've read that it can 'fubar' recovery and can cause boot loops. (So up til now, you've been lucky).
For further info, Heimdall simply isn't needed.....The primary method of TWRP installation is via Odin. I'm a bit concerned that rom manager said you have both CWM and TWRP installed....Some investigation is in order....
Whichever recovery you boot into with the button combination is the recovery you have installed.....
Hello!
First of all, I'm not a native speaker so let me know if there is something that is not clearly stated / confusing.
I got a little problem with my phone and was unable to find a solution to my problem in this forum or anywhere else so I just registered moments ago
My phone: Samsung Galaxy S2 GT-i9100, running freshly flashed stock ROM (android 4.1.2 , stock recovery)
*HISTORY*
I tried to flash a custom recovery and after soft-bricking it I flashed a "stock ROM" from Samsung which I found on the internet and everything works perfectly again.
However, this shouldn't be of any relevancy to the following problem(s).
*WHAT I WANT*
I want to install the latest snapshot build of Cyanogenmod 12.1 (I would choose CM13 but there are only nightly builds and I don't want that).
As I'm new to all of this I followed manuals which told me to install the custom recovery "TWRP".
To do so I followed this manual: https: //twrp.me/devices/samsunggalaxys2i9100. html
and used "twrp-3.0.2-1-i9100.img"
*THE PROBLEMS*
After Heimdall tells me that everything was successfully flashed (noreboot is set) I turned the phone off and restarted it straight to recovery mode.
Instead of booting the TWRP custom recovery which I just flashed the android stock recovery was booted.
QUESTION 1: Does anyone have an idea why that happens?
As far as I know there is just a 'vestigial' recovery partition on the i9100.
Apparently 'isorec' offers a way to make it available for my custom recovery so that TWRP does not get overwritten by the recovery
which is part of the CyanogenMod (which I'm going to install later on). Is that correct?
QUESTION 2: Is there anything I need to do to make isorec work which is not covered by the manual I use?
Apparently the system partition is too small for CyanogenMod13 + GoogleApps (but I want to use both later on).
QUESTION3: How can I repartition, how much space will I need and how do I do it? Do I have to do it before I flash recovery or before I flash the CM12.1 ROM?
So far I found several really unspecific tutorials and now I'm afraid to brick the phone.
Looking forward to any advice, thanks a lot!
blackdaw
Hi @blackdaw
I'll explain what went wrong and how to do what you want...
1. The TWRP 3.0.2-1.img is a isorec recovery. It won't boot unless you have an isorec-enabled kernel. If the kernel you have is not, then the recovery that is bundled with the kernel is booted instead(ie. the old style monolithic kernel/recovery in the kernel partition). So you need a newer kernel(which means a newer rom that runs with a isorec enabled kernel). Until you have that don't worry, we'll get to that.
2. Re-partitioning. You will eventually need to re-pit, as the newer roms(android 6+) often need a bigger system size even if you don't use gapps. 1GB should be ample. Here is a good guide for updating to MM roms, but also has links for re-partitioning. Take your time and study the different ways to re-pit, but personally I would just re-pit before flashing any roms, then it's done. I use odin(windows) and re-pit at the same time as installing a recovery using this method. As I said there are other ways....
3. What I would do:
Odin re-pit method
*I use gustavos kernel to flash with odin at the same time as the .pit file. Some .tar kernels don't work(Idon't know why)
Once you are in the TWRP/CWM recovery, do your backups/wipes and flash the rom and gapps(if you want) and TWRP 3.0.2-1.img, then reboot.
(No yellow triangle method)
download a kitkat compatible kernel such as the one I've attached
find the correct philz kernel for your stock rom from here. It needs to be in .zip format. Flash the kernel in the stock(3e) recovery, then reboot to recovery. This is all you need to flash older custom roms(you will be rooted and could stay on stock if you wanted but the recovery is obsolete for kitkat and above)
from the new philz/CWM recovery, flash the TWRP kernel I attached then reboot straight to recovery once again. (This kernel won't boot the rom; you will end up with a bootloop if you try. You only need the newer recovery)
now from this TWRP 2.8.7.0, flash the TWRP 3.0.2-1.img just to make sure you have that recovery installed to the recovery partition, and CM12.1(*note below) and gapps(if you want).
use Lanchons re-pitting tool to re-partition
Install diskinfo app from the store to check your partition sizes and if you want an easy way to see free space etc.
Note: I would strongly recommend you use the last nightly or newer unofficial build of CM12.1 if you are set on that rom. There are several major fixes(including the implementation of isorec) that are not included in the last official snapshot build. I've uploaded the last nightly here
I hope I've covered everything. Happy flashing
Hello noppy22,
thank you so much for your reply! I literally spent days reading all sorts of stuff so I would know and understand all alternatives and not brick my phone. However, I didn’t succeed so far, I’m stuck with the first step where I am supposed flash the philz kernel as preparation for flashing the TWRP stock kernel (which you attached).
So far I had about 15 different attempts with different methods but I try to remember what I did and what went wrong:
First I tried to repartition and flash the philz kernel
(versions “philz_touch_6.07.9-i9100.tar.md5” and “philz_touch_6.05.6-i9100.tar.md5”)
at the same time, following the manual you linked under “this method”.
Here is the log of what happens:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> philz_touch_6.07.9-i9100.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> recovery.img
<ID:0/004> NAND Write Start!!
It was stuck at “NAND Write Start!!”. After a long, long time I just pulled the cable.
Afterwards I booted into recovery and tried flashing zip files of the same philz kernels.
Here I encountered an error looking something like this: “ This package is for "9100, …, …" devices; this is a ‘’ “
Instead it should say “ this is a ‘9100’ “ but the space between the ‘ ‘ is just empty, it doesn’t seem to recognize my device.
Others have this problem too: http://forum.xda-developers.com/showthread.php?t=2602107
Next thing I tried was the manual in cyanogen wiki:
(https:// wiki.cyanogenmod.org /w/Install_CM_for_i9100 )
Before the softbrick (as mentioned in first post under ‘history’) this enabled me to use CWM recovery.
Now that I tried it again it does not work any more, saying something like “no kernel partition detected”.
I thought this problem was caused by the new partitioning so I used the repart option in odin together with stock PIT-file. No success.
Now I ran out of options, I tried everything that came to my mind.
Any idea how to fix this? Try fifferent Kernel? I was not brave enough to pick one on my own.
Btw, after all this messing around I’m stuck in bootloop but can still reach Download Mode and Stock recovery.
If you need more detailed information/logs I'll try to reproduce the errors.
Thank you so much, I'm quite desperate!
All the best, blackdaw
Hi @blackdaw
I realise reading your post I was a little unclear on a couple of points. Sorry about that. I'll edit my post above to make it clearer for anyone needing the same help.
All you need to do is flash this kernel I've attached, in odin. Just untick reboot device and when you get a pass, turn off the device and boot into recovery. You will get a bootloop if you try to boot your rom. Before you do this, make sure you have your rom and gapps(if you want them) ready to flash from this new recovery.
Alternatively find the stock rom from sammobile.com and flash the .tar.md5 file from odin and start again. This is usually my goto step if I've messed anything up.
The two points I didn't explain very well were to use philz kernel in .zip format to flash from stock recovery before re-pitting, and I didn't explain when to re-partition. Again sorry about that.
EDIT: I've edited my first post. Hopefully it explains thing a bit better. Let me know how you go
Hi @noppy22,
it works, thank you so much!
So here is what I did in the end:
1. First I followed gsstudios guide to Increase system partition size and used all the software he attached.
The Samsung drivers were already installed so I launched Odin 3.07, loaded the "I9100_1GB-System_4GB-Data_512MB-Preload.pit" in the pit file section, checked "repartition", unchecked "reboot", loaded the "AOSP-LP-Kernel+_26-07-2015_TWRP-2.8.7.0.tar" (which you attached in your last post) in the PDA section and hit start. It took a while but in the end the odin log said something like "1succesfull / 0 unsuccessful"
2. After turning the phone off I rebooting to recovery mode which was now TWRP 2.8.7.0. Just to have the latest version I wanted to flash TWRP 3.0.2-1 but I didn't work because the device was "unable to mount emmc".
However, I justed flashed "cm-12.1-20160203-NIGHTLY-i9100" which you linked to in your first post and rebooted to system. TA DA! It worked!
There was still a problem with the storage. The now 4GB large Data partition and the 32GB external SD-Card were visible but not the 9GB internal SD-Card (UMS) wasn't. After rebooting to recovery to fix the problem a little surprise awaited me: TWRP version 3.0.2 was displayed, even though the previous update pretended to have failed. Well, I can't complain. Wiping the Data partition resolved the problem so android could successfully mount it.
End of story.
Now that everything is working, how can I get updates to the latest CM version? What really puzzles me is that they deleted the latest nightlys of CM12.1 and only left CM13 nightlys on the official CM download page.
Where did you get the CM12.1 nightly version you uploaded?
Is it safe to just do and OTA update?
I read in that one thread that OTA update is not safe for CM13 so if I find a reason to flash it I'll do it via recovery.
Thanks again!
All the best,
blackdaw
Hi @blackdaw,
I'm glad you got it working! The step you missed straight after the re-partition was formatting the new partitions from recovery. Especially sdcard0: without formatting sdcard0, the system will normally report that as corrupted or unable to read.
The 3.0.2 TWRP only booted after you had flashed the isorec enabled kernel(that is, by flashing CM12.1) The older kernel you used re-pitting wasn't isorec enabled, and so it used its own bundled TWRP 2.8.7 recovery. This was over-written by the kernel in CM12.1 when you flashed it......TWRP 3.0.2-1 will now work whenever you have isorec enabled kernel/rom and you don't need to flash it again; it will survive any normal wipes or flashes you make as it resides in the recovery partition.
Don't use OTA when you want to upgrade to CM13. You will need to do a full wipe and install with recovery.
The CM12.1 I still had on my computer from when it was on the CM page. They normally wipe older builds and keep newer ones for space I imagine. They will keep "snapshot" builds a lot longer, but CM12.1 never got a final snapshot, and we've never got a snapshot CM13 build despite being mostly stable depending on when they introduce new features/commits. Check on posts in the official CM13 thread for more info on bugs and which versions are more bug-free.
Good luck
Changing kernel sorts all issues
Changing kernel sorts all issues, thanks you for your help. :good:
Hello, today I tried to install the stock firmware for my SM-G925F instead of having my rooted ROM, so that I could use apps like barclays and snapchat. This wouldn't work on odin, and my error is as follows:
<ID:0/004> sboot.bin
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004>Complete(Write) operation fail
So because this didnt work, I used TWRP to wipe all data, hoping it would wipe the ROM, but it didn't. After I did this I went back into TWRP and tried to power off my device through there, but my device just froze, with the power off button highlighted. I think the kernel from the ROM doesn't allow booting from TWRP, but I can't boot normally. I can still go into download, TWRP and normal boot mode, though. Is there any chance you guys could give me some advice on how to get my device up and running again, even if it is on the ROM I used to root my device?
UPDATE: I tried to use odin again, but it is stuck with setting up connection, might be the drivers I used to try ADB sideloading the ROM, I'll see if i can fix this
DomiShady said:
Hello, today I tried to install the stock firmware for my SM-G925F instead of having my rooted ROM, so that I could use apps like barclays and snapchat. This wouldn't work on odin, and my error is as follows:
<ID:0/004> sboot.bin
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004>Complete(Write) operation fail
So because this didnt work, I used TWRP to wipe all data, hoping it would wipe the ROM, but it didn't. After I did this I went back into TWRP and tried to power off my device through there, but my device just froze, with the power off button highlighted. I think the kernel from the ROM doesn't allow booting from TWRP, but I can't boot normally. I can still go into download, TWRP and normal boot mode, though. Is there any chance you guys could give me some advice on how to get my device up and running again, even if it is on the ROM I used to root my device?
UPDATE: I tried to use odin again, but it is stuck with setting up connection, might be the drivers I used to try ADB sideloading the ROM, I'll see if i can fix this
Click to expand...
Click to collapse
sboot.bin fail means your trying to downgrade which will not work. All you need to do is just flash the correct firmware.
By the sounds of it you have wiped the ROM off the phone. Which ROM was it?
Just flash this stock ROM again
https://www.sammobile.com/firmwares/download/106963/G925FXXS4DPJ2_G925FBTU4DPH1_BTU/
Then flash TWRP
https://dl.twrp.me/zerolte/
Then flash cf autoroot through odin.
https://download.chainfire.eu/737/CF-Root/CF-Auto-Root/CF-Auto-Root-zerolte-zeroltexx-smg925f.zip
I tried to flash that rom, but it failed after hidden.img. Now my device is saying 'An error has occured while updating the device software'. Is it possible to use smart switch to recover from this? I don't mind having an unrooted phone.
DomiShady said:
I tried to flash that rom, but it failed after hidden.img. Now my device is saying 'An error has occured while updating the device software'. Is it possible to use smart switch to recover from this? I don't mind having an unrooted phone.
Click to expand...
Click to collapse
Either use smart switch
Or
http://forum.xda-developers.com/gal...t-files-multi-thread-download-t3171636/page10
Go to this thread to 1st page. Download g925f pit file zerolte_eur_open.
In odin options click pit and insert the downloaded pit file. Then insert the firmware and flash again. You will not get hidden.img fail and it will flash.