Related
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100XXLPQ_I9100OXALPQ_I9100XXLPQ_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<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> boot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> Sbl.bin
I flashed rom through Odin and its return is like this.
The Sbl.bin is likely to be related to the bootloader.
I cannot access to the recovery or normally reboot.
What can I do?? I tried flashing for several times.
Zillions of thanks if you guys can help me!!!!
What is your device?
aceofclubs said:
What is your device?
Click to expand...
Click to collapse
i9100 of course.
superfan' said:
i9100 of course.
Click to expand...
Click to collapse
Why did you start a new thread? You already had a perfectly good thread going for the same problem here: http://forum.xda-developers.com/showthread.php?p=24175814.
And you've apparently decided to ignore all the advice in that thread that said to flash back to a stock GINGERBREAD firmware, since you again are trying to flash LPQ, which is one of the earlier ICS releases.
superfan' said:
i9100 of course.
Click to expand...
Click to collapse
Not of course. Because the problem you describe is what happens when you try to flash I9100 firmware on a model like I9100G or others that are called SGS2 but are different hardware. Only true way to tell is read the sticker under the battery.
Anyway forget this thread and take the advice in the other thread and report back there.
Good luck.
ctomgee said:
Why did you start a new thread? You already had a perfectly good thread going for the same problem here: http://forum.xda-developers.com/showthread.php?p=24175814.
And you've apparently decided to ignore all the advice in that thread that said to flash back to a stock GINGERBREAD firmware, since you again are trying to flash LPQ, which is one of the earlier ICS releases.
Click to expand...
Click to collapse
I tried to flash KI3, the gingerbread, it still fails. I think it is a new problem, and it is related to the NAND rw corruption mentioned by others. Therefore, I started a new post but not ignoring others' advice.
If you can help me with my problem, zillions of thanks then.
Flash a stock GB rom and see what happens .
jje
Given you say you've tried everything suggested, and given you think it's a bootloader issue, there are literally dozens and dozens of posts on here about same.
Do a Google search (rather than using XDA search), and append 'XDA' to whatever your search terms are.
This problem you're having is not common, and you're not going to find a fix easily for this (as you're discovering) short of having it JTAG'd or sending it to a Samsung service center.
Is samsung customer service accepted to handle this, even i have some custom binary no?
Or if i pay some money, they wll fix that for me??
Sent from my GT-P7500 using XDA
Yep. They'll fix it, but you'll more than likely end up paying for it. A JTAG repair might be a cheaper option. Here's one in the US, I'm sure there are many others around the world (maybe near you, search Google).
Can you still enter download-mode (Vol. down + Home Button + Power Button)? If so, you can try these steps in this Guide here
Be careful with Re-Partition..i ruined my device some days ago with it after try to fix nand rw corruption.
I have tried all of those before. But i even can't flash things through. Even vthe kernel, recovery and bootloaders.
Sent from my GT-P7500 using XDA
So when you try to flash a 3-Part Firmware (without Re-Partition) it stucked again?
PS: Be very careful .. I has a very similar problem and with Re-Partition I shoot it up -.- (http://forum.xda-developers.com/showthread.php?p=24115788#post24115788)
What have you done to shoot it up??
I stucked even i flashed a three part firware without repartition and pit file
Sent from my GT-P7500 using XDA
Hey,
I'm sorry but i didn't solve the problem for me. With "shoot it up" I mean "i killed my phone". Sorry for that mistake!
I followed the guide too but at first step I flashed with Re-Partition and PIT file. Odin stucked at "Partitioning" so after 10min I closed Odin and restart S2...after that my device was completly dead. Screen stays black. Sorry don't know how to fix it. My S2 is on the way to rapaircenter now.
Aur0r4 said:
Hey,
I'm sorry but i didn't solve the problem for me. With "shoot it up" I mean "i killed my phone". Sorry for that mistake!
I followed the guide too but at first step I flashed with Re-Partition and PIT file. Odin stucked at "Partitioning" so after 10min I closed Odin and restart S2...after that my device was completly dead. Screen stays black. Sorry don't know how to fix it. My S2 is on the way to rapaircenter now.
Click to expand...
Click to collapse
I can access to the download mode but I can't flash anything through my beloved s2.
I am going to send it to the repair centre, u suggest me to send them to Samsung's or others??
Go into recoverymode and install a rom in ur memory internal or extaernal
Just do that turn off phone...and them volume up+power+home button u will enter in recovery mode not in download mode...now just search the rom ...notice u do this if its rooted... Look if u just put insecure kernel by odin i sugere u take sd card out download a rom by computer to sd card. input again in phone and turn on in recovery mode... i think will works im not responsabile for nothing can happened but im pass the same like i write...tell something
Sent from my GT-I9100 using XDA
Look the guy up say to you a dificult way to do and also u may brick ur phone...u do somethings in odin i just never do...i just saw now otherwise u already fix it if i put this earlier
Sent from my GT-I9100 using XDA
Hey All,
I definitely hard bricked my phone, I've tried everything on XDA, every Odin, every stock and rooted rom in combination with different Pit's, baselines etc.. etc..
Not sure if I am rooted anymore or unrooted since I have installed so many Rom's.. My screen gets stuck on Samsung Logo, I can only get into Download Mode (Odin Mode) and I am sure of that.
I started off trying to install a custom rom, things went bad, after it all went bad i realized my mistakes reading, upon reading XDA.
My question for all you wonderful people on XDA is.. what do i do now with a paper weight? Do i keep trying and Beat it till it works, or replace the motherboard? & if i replace the mobo can i simply get an AT&T Mobo on this Verizon? (I have at&t, its an unlocked Verizon phone).. & where do I go to do it? (cheapest place please, totally not rich)
more info:
can't partition in odin/ i always encounter some sort of error in the middle of trying to do anything with odin.. I am only successful when i install the 66root file, and if I select the 'T Flash' option in odin it sometimes works with other roms.. but no matter what I still get stuck on the Logo Screen
list of what i have tried:
http://galaxynote2root.com/galaxy-n...o-install-custom-rom-on-rooted-galaxy-note-2/
http://www.androidayos.com/2013/04/...-note-2-sch-i605-original-firmware-stock-rom/
http://forum.xda-developers.com/showthread.php?p=39299305
http://forum.xda-developers.com/showthread.php?t=2118348
http://forum.xda-developers.com/showthread.php?t=2024207
& MUCH MORE.
I know i am dumb for how I went about doing all this so please keep it informational... thank you all!!
gnit0 said:
Hey All,
I definitely hard bricked my phone, I've tried everything on XDA, every Odin, every stock and rooted rom in combination with different Pit's, baselines etc.. etc..
Not sure if I am rooted anymore or unrooted since I have installed so many Rom's.. My screen gets stuck on Samsung Logo, I can only get into Download Mode (Odin Mode) and I am sure of that.
I started off trying to install a custom rom, things went bad, after it all went bad i realized my mistakes reading, upon reading XDA.
My question for all you wonderful people on XDA is.. what do i do now with a paper weight? Do i keep trying and Beat it till it works, or replace the motherboard? & if i replace the mobo can i simply get an AT&T Mobo on this Verizon? (I have at&t, its an unlocked Verizon phone).. & where do I go to do it? (cheapest place please, totally not rich)
more info:
can't partition in odin/ i always encounter some sort of error in the middle of trying to do anything with odin.. I am only successful when i install the 66root file, and if I select the 'T Flash' option in odin it sometimes works with other roms.. but no matter what I still get stuck on the Logo Screen
list of what i have tried:
http://galaxynote2root.com/galaxy-n...o-install-custom-rom-on-rooted-galaxy-note-2/
http://www.androidayos.com/2013/04/...-note-2-sch-i605-original-firmware-stock-rom/
http://forum.xda-developers.com/showthread.php?p=39299305
http://forum.xda-developers.com/showthread.php?t=2118348
http://forum.xda-developers.com/showthread.php?t=2024207
& MUCH MORE.
I know i am dumb for how I went about doing all this so please keep it informational... thank you all!!
Click to expand...
Click to collapse
If you can still access Download Mode then you arent truly hard bricked.
If you havent tried it you need to try flashing the PIT file. There is also the "alternative recovery method" that you should try. I think flashing the PIT file, which I believe is in one of Adams casual posts, will get you back on track but I might be wrong. Hopefully someone else will stroll through and be abke to give you a bit more help than me.
As for the first 2 urls, NEVER EVER EVER use root methods that are not on XDA. Not many people have experience with them and they could be potentially dangerous.
You also need to specify exactly what all you have tried out of those threads instead of just linking the thread.
Sent from my SCH-I605 using XDA Premium HD app
Alternative Retry
shangrila500 said:
If you can still access Download Mode then you arent truly hard bricked.
If you havent tried it you need to try flashing the PIT file. There is also the "alternative recovery method" that you should try. I think flashing the PIT file, which I believe is in one of Adams casual posts, will get you back on track but I might be wrong. Hopefully someone else will stroll through and be abke to give you a bit more help than me.
As for the first 2 urls, NEVER EVER EVER use root methods that are not on XDA. Not many people have experience with them and they could be potentially dangerous.
You also need to specify exactly what all you have tried out of those threads instead of just linking the thread.
Sent from my SCH-I605 using XDA Premium HD app
Click to expand...
Click to collapse
I have tried the alternative recovery method, but i went ahead and tried again. Stuck at "Get PIT for mapping.."
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I605_VRALJB_Restore.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..
USB
gnit0 said:
I have tried the alternative recovery method, but i went ahead and tried again. Stuck at "Get PIT for mapping.."
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I605_VRALJB_Restore.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..
Click to expand...
Click to collapse
I've tried different USB Ports, Chords and Machines (win 7 64bit, win 7 32bit & XP)
gnit0 said:
I have tried the alternative recovery method, but i went ahead and tried again. Stuck at "Get PIT for mapping.."
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I605_VRALJB_Restore.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..
Click to expand...
Click to collapse
I had this problem.
And I just used another computer and it worked fine.
Sent from my SCH-I605 using xda app-developers app
barrackOBAMA said:
I had this problem.
And I just used another computer and it worked fine.
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
If the PIT and alternate recovery method don't work or wouldn't hurt to try it on a different computer as barrackOBAMA suggests. If that doesn't work we can always try something else. The most important thing is to stay calm. These phones are incredibly hard to hard brick, and as long as you can get into Download Mode it can usually be fixed. It might be a long process but it'll be free where if you bought a motherboard it would cost you more money.
Sent from my SCH-I605 using XDA Premium HD app
shangrila500 said:
If the PIT and alternate recovery method don't work or wouldn't hurt to try it on a different computer as barrackOBAMA suggests. If that doesn't work we can always try something else. The most important thing is to stay calm. These phones are incredibly hard to hard brick, and as long as you can get into Download Mode it can usually be fixed. It might be a long process but it'll be free where if you bought a motherboard it would cost you more money.
Sent from my SCH-I605 using XDA Premium HD app
Click to expand...
Click to collapse
thanks guys, I really do appreciate the help and I have no problem testing any method thrown my way, if you guys were to tell me to throw it at a pigeon, I probably would do it. I have tried on 3 different VM's.. not sure if thats really considered a "different machine" or not.. I am in the middle of restoring my old dell laptop to try it on that.
shangrila500 said:
If the PIT and alternate recovery method don't work or wouldn't hurt to try it on a different computer as barrackOBAMA suggests. If that doesn't work we can always try something else. The most important thing is to stay calm. These phones are incredibly hard to hard brick, and as long as you can get into Download Mode it can usually be fixed. It might be a long process but it'll be free where if you bought a motherboard it would cost you more money.
Sent from my SCH-I605 using XDA Premium HD app
Click to expand...
Click to collapse
ah dude.. tried it on a different PC and still stuck on this motherless error <ID:0/004> Get PIT for mapping..
Honestly think I did something to the emmc or whatever it is. I don't know if I'm violating TOS but I will donate 50 bux to whomever can help. If saying I will donate is a violation please forgive.
gnit0 said:
Honestly think I did something to the emmc or whatever it is. I don't know if I'm violating TOS but I will donate 50 bux to whomever can help. If saying I will donate is a violation please forgive.
Click to expand...
Click to collapse
Lemme ask you this, do you have Kies installed? My friend had the same issue with his N2 where it would freeze in Odin and do nothing else at all after it said getting PIT for mapping. He finally had to bring it over to me and use my computer to root it, his is the AT&T version, and even though he had Kies installed he couldn't get the phone to connect right. He finally had to install Kies and all the drivers and them reinstall Kies first then the standalone drivers that were linked and after that everything worked. That may be worth a shot. I also know a lot of people have issues using VM machines and Windows 8, it seems everything works smoothest on Windows 7.
As for boring the emmc, you may have but like I said earlier it's really hard to screw this phone up so I really think it is just an issue with VM ware or possibly you haven't flashed the right file that it needs yet. We'll figure it out though hopefully, it will just take some trial and error.
Have you tried the alternate restore method? If not I will link it, it seems to fix a lot of people's phones when nothing else will.
Honestly I think it is something with the computers you're using and the drivers being wonky as usual.
Sent from my SCH-I605 using XDA Premium HD app
shangrila500 said:
Lemme ask you this, do you have Kies installed? My friend had the same issue with his N2 where it would freeze in Odin and do nothing else at all after it said getting PIT for mapping. He finally had to bring it over to me and use my computer to root it, his is the AT&T version, and even though he had Kies installed he couldn't get the phone to connect right. He finally had to install Kies and all the drivers and them reinstall Kies first then the standalone drivers that were linked and after that everything worked. That may be worth a shot. I also know a lot of people have issues using VM machines and Windows 8, it seems everything works smoothest on Windows 7.
As for boring the emmc, you may have but like I said earlier it's really hard to screw this phone up so I really think it is just an issue with VM ware or possibly you haven't flashed the right file that it needs yet. We'll figure it out though hopefully, it will just take some trial and error.
Have you tried the alternate restore method? If not I will link it, it seems to fix a lot of people's phones when nothing else will.
Honestly I think it is something with the computers you're using and the drivers being wonky as usual.
Sent from my SCH-I605 using XDA Premium HD app
Click to expand...
Click to collapse
Hey Shangrila, appreciate you helping me, I am going to try and completely uninstall all drivers for Samsung, uninstall kies, install drivers and test, if it doesn't work, re-install kies and drivers. I have tried to restore with and without kies, and all over again. I will try again but this time i will completely wipe all drivers and re-install note 2 drivers
May I ask what the first step that you did was that bricked it? You are stuck on the samsung logo flashing?
meat614 said:
May I ask what the first step that you did was that bricked it? You are stuck on the samsung logo flashing?
Click to expand...
Click to collapse
It started with a trade on craigslist. Traded my at&t iPhin 5 (i love you man insider) for this Verizon sch-i605 unlocked. I had no idea if it were able to accept custom roms or not, but i do know it was rooted (used supersu) i am a highly tech savvy guy but i don't know **** about android. I did a factory restore from setting, I then tried to install casual, downloaded it and ran it but it kept erroring so i then went and tried to upload a mod on sdcard and went to recovery mode wipe device and cache.. after that it stopped working. tried to install all sorts of roms, boot loaders, pits and what not. now all i get is error after error, either nand error or getting pit mapping halt. for some reason root66 is the only rom that is successfull but without pit file. and not sure what "T Flash" is on Odin, but some roms work while that is checked.
some roms i have tried:
CI605_I605VRLJB_I605VRALJB_CL414933_HWID04_HW_Rev0406_low_ship_user.tar.md5
I605_VRALJB_Restore.tar.md5
cwm6-root-note2.tar
root66_VZW_stock_system.tar.md5
BootloaderBaseline2.tar.md5
TWRP2430VZW.tar.md5
gnit0 said:
Hey Shangrila, appreciate you helping me, I am going to try and completely uninstall all drivers for Samsung, uninstall kies, install drivers and test, if it doesn't work, re-install kies and drivers. I have tried to restore with and without kies, and all over again. I will try again but this time i will completely wipe all drivers and re-install note 2 drivers
Click to expand...
Click to collapse
If I can help I most definitely will. This sounds exactly like a driver issue thoug because it isnt able to communicate with the phone yo get the PIT for mapping. That was the same exact thing that happened with my friends phone on his laptop when I was setting everything up and showing him how to use Odin to root his phone, it would show up on a port and act like it would work but it would freeze every single damn time on the getting PIT for mapping part and wouldn't do anything else until I unplugged the phone and then it would say failed.
The main thing that helped him was wiping the drivers completely though and then just reinstalling Kies, I think he installed the other drivers after that but i can remember for sure, and it finally worked perfectly. I only have Kies on my laptop, I dont have the second set of drivers, but if you cant get it to work with just Kies try installing the other set and then test it again. You may even have to launch Kies for it to install the drivers correctly, it's been so long I can't remember that part either. Just install Kies first without the other set of drivers, launch Kies and make sure everything is set up with Kies, and see if that works. If not then install the 2nd set and try to use Odin again.
Also what OS are you doing all this on? If it's Windows 7 then it may take a little playing with the drivers to get it right. Also which version of Odin are you using? I cant get the newest version to work correctly on my laptop so that could also be part of it. Have you tried the alternative restore method? While I am 99% site it is the drivers it is always best to cover all bases.
Sent from my SCH-I605 using XDA Premium HD app
---------- Post added at 11:08 PM ---------- Previous post was at 11:06 PM ----------
gnit0 said:
It started with a trade on craigslist. Traded my at&t iPhin 5 (i love you man insider) for this Verizon sch-i605 unlocked. I had no idea if it were able to accept custom roms or not, but i do know it was rooted (used supersu) i am a highly tech savvy guy but i don't know **** about android. I did a factory restore from setting, I then tried to install casual, downloaded it and ran it but it kept erroring so i then went and tried to upload a mod on sdcard and went to recovery mode wipe device and cache.. after that it stopped working. tried to install all sorts of roms, boot loaders, pits and what not. now all i get is error after error, either nand error or getting pit mapping halt. for some reason root66 is the only rom that is successfull but without pit file. and not sure what "T Flash" is on Odin, but some roms work while that is checked.
some roms i have tried:
CI605_I605VRLJB_I605VRALJB_CL414933_HWID04_HW_Rev0406_low_ship_user.tar.md5
I605_VRALJB_Restore.tar.md5
cwm6-root-note2.tar
root66_VZW_stock_system.tar.md5
BootloaderBaseline2.tar.md5
TWRP2430VZW.tar.md5
Click to expand...
Click to collapse
Watch what you check in Odin. You are ONLY supposed to check what is told in the guide, NONE OTHER! Thats a really good way to mess things up and make it harder to fix!
Can you boot into recovery? If so is there a nandroid you could try restoring?
Sent from my SCH-I605 using XDA Premium HD app
aug ttaham
i have been trying with these below none stop
Odin - 3.07
PDA - I605_VRALJB_Restore.tar.md5.xz
PIT - sch-i605-16gb.pit
none stop
gnit0 said:
i have been trying with these below none stop
Odin - 3.07
PDA - I605_VRALJB_Restore.tar.md5.xz
PIT - sch-i605-16gb.pit
none stop
Click to expand...
Click to collapse
What do you mean by none stop? Did you mean non stop? Or they aren't stopping? Sorry for asking, just a little late and I had a long day.
Sent from my SCH-I605 using XDA Premium HD app
shangrila500 said:
What do you mean by none stop? Did you mean non stop? Or they aren't stopping? Sorry for asking, just a little late and I had a long day.
Sent from my SCH-I605 using XDA Premium HD app
Click to expand...
Click to collapse
I meant i have been trying those none stop, ive tried to restore with those files atleast 10 times..
I tried to uninstall drivers and kies and then restoring but i got nothing, then tried with newly installed kies... and nothing as well.. arggg
still stuck on Get Pit Mapping
& no, i cannot get into recovery... just stays at the samsung gn 2 logo screen, and if i hold up button home and power, it just shuts off and on again... even if i release power button when i see the logo... stays at logo
gnit0 said:
i have been trying with these below none stop
Odin - 3.07
PDA - I605_VRALJB_Restore.tar.md5.xz
PIT - sch-i605-16gb.pit
none stop
Click to expand...
Click to collapse
Also this is the alternative method I was talking about:
http://forum.xda-developers.com/showthread.php?t=2040264
In the first post there is a link that says alternative restore, it has a different sboot so it will leave you unlocked. It works a lot when the PIT doesnt, its worth a shot. I still think its drivers but im throwing everything I can out so maybe you'll be able to use your phone, I know how it is to not have one to use until you can fix yours.
Sent from my SCH-I605 using XDA Premium HD app
---------- Post added at 11:27 PM ---------- Previous post was at 11:24 PM ----------
gnit0 said:
I meant i have been trying those none stop, ive tried to restore with those files atleast 10 times..
I tried to uninstall drivers and kies and then restoring but i got nothing, then tried with newly installed kies... and nothing as well.. arggg
still stuck on Get Pit Mapping
& no, i cannot get into recovery... just stays at the samsung gn 2 logo screen, and if i hold up button home and power, it just shuts off and on again... even if i release power button when i see the logo... stays at logo
Click to expand...
Click to collapse
What OS are you using? Are you using VMware right now? It still sounds like a driver issue, is there any chance you have a different computer with Windows 7 installed that you could try if the alternative restore method I linked a minute ago doesn't work?
Sent from my SCH-I605 using XDA Premium HD app
shangrila500 said:
Also this is the alternative method I was talking about:
http://forum.xda-developers.com/showthread.php?t=2040264
In the first post there is a link that says alternative restore, it has a different sboot so it will leave you unlocked. It works a lot when the PIT doesnt, its worth a shot. I still think its drivers but im throwing everything I can out so maybe you'll be able to use your phone, I know how it is to not have one to use until you can fix yours.
Sent from my SCH-I605 using XDA Premium HD app
Click to expand...
Click to collapse
that is the exact file i have been trying with odin 3.0.7 and the pit file.
shangrila500 said:
What OS are you using? Are you using VMware right now? It still sounds like a driver issue, is there any chance you have a different computer with Windows 7 installed that you could try if the alternative restore method I linked a minute ago doesn't work?
Sent from my SCH-I605 using XDA Premium HD app
Click to expand...
Click to collapse
I am trying on a local windows 7 64bit machine.. i have 16gb ram, amd fx 8120 8-core processor, and a ssd hybrid.. my mobo is a asus m5a97.. stopped using the VM's
Hi
I am in a serious trouble.
I am having a Samsung Galaxy S2 GT-I9100G
Its running on Stock Rom JB v4.1.2
I wanted to update it to Kitkat 4.4.2 by CyanogenMod 11 Custom Rom.
In order to do that i have rooted my phone using VRoot.
Installed CWM Recovery 6.0.1.2
Copied the ROM files and Gapps to SD Card.
Done all the prerequisite and started installing the ROM.
Then the installation failed showing Error Status 7.
Upon googling about status 7 i got to know that the CWM Recovery 6.0.1.2 which i used doesn't support for
installing CM11.
Then i searched for the latest CWM Recovery and got to know about the Philz CWM Touch Recovery 6.0.4.5
I also got to know that in order to install Philz CWM Touch Recovery 6.0.4.5 you need to have a PC with Odin
v3.09 installed to flash this latest CWM Recovery.
Then i downloaded philz_touch_6.19.3-i9100g.tar.md5.
Installed Odin v3.09 in my PC.
Gone into Download mode by pressing Home + Volume Down + Power Button then warning screen came up then by
pressing volume up i came into download mode.
Then i connected my device to PC using USB cable. I got the added message. I also got the COM Port number.
But instead of Yellow as said in the tutorial i got Light Blue Color which i ignored. I thought the Odin
software might had made any changes to their software.
I clicked the AP button and selected the TAR file downloaded then clicked the START button.
Again failed. I don't know why that happened.
I removed the USB cable and reinserted then done the same. Then some message came and process is going on...
waited for 20 mins till nothing was happening.
Fed up of all the process i removed the USB cable thinking of forgetting Kitkat and use the stock rom.
After removing the USB cable suddenly a message flashed on the screen.
Firmware update encountered an issue. Please select recovery mode in Kies & try again.
Whatever i do only this is appearing on screen.
Nor it's going into Download Mode or Recovery Mode.
Please help me in recovering my phone to Stock ROM or Custom ROM.
Last hope is jig. It force download mode when.you cant by pressing buttons. If this doesnt help i think that your phone is now a clip for paper. In odin you should choose pda and after that choose kernel. I never had blue sign in odin but i had i9100. You should from the beghinig try philz kernel to root amd get cwm recovery. So as i sad you must try jig usb very cheap thing or you can do it by yourself. Maybe you should either try kies and kies recovery firmware.
Wysłane z mojego D5503 przy użyciu Tapatalka
adithyagem said:
After removing the USB cable suddenly a message flashed on the screen.
Firmware update encountered an issue. Please select recovery mode in Kies & try again.
Whatever i do only this is appearing on screen.
Nor it's going into Download Mode or Recovery Mode.
Click to expand...
Click to collapse
Here's where your problems are.
1. Never unplug your cable during an Odin flash. Wait till it fails. Else you'll get trouble, guaranteed.
2. You're in forced download mode. Flash a Stock ROM using Odin while it says 'firmware update encountered an issue'.
3. Instead of using Odin with Philz, next time you can just flash Philz directly from the external SD card (at least on i9100, not sure about the i9100G). Much easier.
Regarding the blue in Odin, I'm pretty sure that's OK. I've seen reports of other people getting blue instead of yellow. I've always had yellow myself but wouldn't hesitate to flash if it was blue.
Newer versions of Odin have blue in the ID:COM field.
Done as said by you
Hopper8 said:
Here's where your problems are.
1. Never unplug your cable during an Odin flash. Wait till it fails. Else you'll get trouble, guaranteed.
2. You're in forced download mode. Flash a Stock ROM using Odin while it says 'firmware update encountered an issue'.
3. Instead of using Odin with Philz, next time you can just flash Philz directly from the external SD card (at least on i9100, not sure about the i9100G). Much easier.
Regarding the blue in Odin, I'm pretty sure that's OK. I've seen reports of other people getting blue instead of yellow. I've always had yellow myself but wouldn't hesitate to flash if it was blue.
Click to expand...
Click to collapse
I tried flashing Philz CWM Recovery using Odin while firmware update encountered an issue screen flashing on screen
Again it failed showing this Log
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> philz_touch_6.19.3-i9100g.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Can you tell me where i gone wrong!?!!
adithyagem said:
I tried flashing Philz CWM Recovery using Odin while firmware update encountered an issue screen flashing on screen
Again it failed showing this Log
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> philz_touch_6.19.3-i9100g.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Can you tell me where i gone wrong!?!!
Click to expand...
Click to collapse
Why did you flash Philz? I said to flash a stock ROM with Odin, not flash Philz.... Click the Odin link in my signature and you can find a 3-part firmware, which will wipe as it flashes. DO NOT flash the 3-part firmware, you have an i9100G. You need to download a stock ROM from Samfirmware or similar. Instructions are in the thread. If it fails again, then follow all of the troubleshooting steps. Keep flashing till you get a successful flash. There's nothing else you can't try which is in that thread, so keep at it.
Edit: Stop. There is no Philz kernel for i9100G. Why on earth did you flash it? It only exists for i9100. Not the 'G' variant. What to do from here? Flash a stock ROM via Odin, like I said to start with, make sure it's for an i9100G.
However, now that you've unplugged the cable during a flash, and flashed the wrong file at least twice, I'm not holding out high hopes for your phone recovering from this.
The ability of people to read & comprehend the help they've been given here & then actually do what's been suggested seems to get worse & worse as time goes by.
Give some very specific advice (step by step stuff, or refer them to step by step stuff), they go do something completely different. I mean, if that's going to happen, why bother asking for help in the first place ?
@MistahBungle, read the edit on my previous post (if you haven't seen it already). Do you agree the only chance is a stock ROM? I don't know, I don't see many this stuffed up very often.
Edit: Unless, there is a Philz for i9100g. But I can't find an XDA thread for it just by having a cursory glance.
Yep. Flashing a stock rom & praying is pretty much the only option. Classic case of 'attempting to do without learning'. Imagine how much **** these people would be in if the half dozen of us or so who post most of the useful help here decided to move on ?
I did find Philz for i9100g, but it's ages old (newest one I could find was 6.19.3, think Philz is up to 6.30.something). There's also no xda thread for it, so I'm tipping that the i9100 version has been flashed. Still not holding high hopes even with a correct stock ROM.
I know, there's less people here than when I started by a long shot. You're by far the most active on here, but I thought you had an S4? I'll be getting the N5 in a month or so. I still plan to be in S2 threads but obviously to a lesser extent.
I do have an S4, but apart from the first couple of months, lost interest in modding it. I want stuff to 'just work' these days for the most part. I do run a custom rom/kernel, I just haven't changed it in ages & not interested in anything that trips Knox. Just can't be bothered putting up with stuff not working/spending a lot of time trying to make it work.
So...I accumulated a lot more knowledge of the S2, given I spent 18 mths or so actively modding it.
Understood. Yes that's what seems to be happening more now, phones which, if they're not on stock ROM, lose a lot of functionality/have stuff 'not work' for whatever reason. Like the GNote & its S-pen, HTC One and boomsound, Sony and its Bravia engine. I assume you still own the S2 anyway...
While you're here, is there anything in the Odin troubleshooting guide you've noticed which should be changed? I read over it again the other day but couldn't see anything major. If you don't want to read/comment no problem, asking as you're the resident Odin guru.
Yeah still have the S2. Haven't switched in on in 6 mths tho.
Nah, you've got everything covered in your thread. It's a great resource ('Odin expert' ? Hardly. I just read/learned a lot )
Mmm I imagine it's not the greatest experience after using a phone 3yrs newer for a while Cool. I added a couple little things just now (another pit file thread (shudder) which is quite well done & re-hosted the 3-part firmware instead of dropbox. Nothing special). Ok, call yourself what you want but what I'm sure of, is that by being on Q&A so much you have a lot more troubleshooting knowledge than probably anyone else for S2
Hopper8 said:
Why did you flash Philz? I said to flash a stock ROM with Odin, not flash Philz.... Click the Odin link in my signature and you can find a 3-part firmware, which will wipe as it flashes. DO NOT flash the 3-part firmware, you have an i9100G. You need to download a stock ROM from Samfirmware or similar. Instructions are in the thread. If it fails again, then follow all of the troubleshooting steps. Keep flashing till you get a successful flash. There's nothing else you can't try which is in that thread, so keep at it.
Edit: Stop. There is no Philz kernel for i9100G. Why on earth did you flash it? It only exists for i9100. Not the 'G' variant. What to do from here? Flash a stock ROM via Odin, like I said to start with, make sure it's for an i9100G.
However, now that you've unplugged the cable during a flash, and flashed the wrong file at least twice, I'm not holding out high hopes for your phone recovering from this.
Click to expand...
Click to collapse
Thanks Hopper for the help...
I have downloaded the Stock ROM for GT-I9100 Indian Version from Sammobile. I don't know what is 3-part firmware.
Now what i am going to do is Connect the phone to my PC showing (Firmware update encountered an issue. Please select recovery mode in Kies & try again) screen.
Then by clicking AP button selecting the TAR file extracted from the Zip file (Stock ROM).
Double check that only AUTO REBOOT & F.RESET TIME checkboxes are selected.
Hit Start and try my luck.
Shall i go ahead. Waiting for your nod...
*nod*
Edit - Hang on, I hope you downloaded I9100G firmware. If you downloaded I9100 Indian firmware, don't flash that.
MistahBungle said:
*nod*
Edit - Hang on, I hope you downloaded I9100G firmware. If you downloaded I9100 Indian firmware, don't flash that.
Click to expand...
Click to collapse
I have downloaded I9100G firmware only...
sorry it was my typing mistake
really sorry to panic you
I have also got a DLL file in the ZIP which i have downloaded. What is it?
Throw the .dll away, you don't need it.
Thanks to Hopper8
Hopper8 said:
Why did you flash Philz? I said to flash a stock ROM with Odin, not flash Philz.... Click the Odin link in my signature and you can find a 3-part firmware, which will wipe as it flashes. DO NOT flash the 3-part firmware, you have an i9100G. You need to download a stock ROM from Samfirmware or similar. Instructions are in the thread. If it fails again, then follow all of the troubleshooting steps. Keep flashing till you get a successful flash. There's nothing else you can't try which is in that thread, so keep at it.
Edit: Stop. There is no Philz kernel for i9100G. Why on earth did you flash it? It only exists for i9100. Not the 'G' variant. What to do from here? Flash a stock ROM via Odin, like I said to start with, make sure it's for an i9100G.
However, now that you've unplugged the cable during a flash, and flashed the wrong file at least twice, I'm not holding out high hopes for your phone recovering from this.
Click to expand...
Click to collapse
Thank You so much
I got my phone back to the original state:laugh:
Thank You so much for your help...
...
Q&A for [GUIDE][VZW Edition]How to Root/Rom/Return to Stock the VZW Galaxy Note II!
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
Help! Odin Bootloading Issue on Verizon Samsung Galaxy Note II
Used the Odin tool (which I've done in the past without issue) to bootload the 4.4.2 software onto my phone and it now just flashes the start-up banner. Worse, my computer no longer recognizes my phone as a valid device, so attempts to load something else will not work.
---------- Post added at 11:21 AM ---------- Previous post was at 10:26 AM ----------
ConvolutedSpeech said:
Used the Odin tool (which I've done in the past without issue) to bootload the 4.4.2 software onto my phone and it now just flashes the start-up banner. Worse, my computer no longer recognizes my phone as a valid device, so attempts to load something else will not work.
Click to expand...
Click to collapse
Okay, so, I've managed to get my device recognized by placing it in Odin Mode and reconnecting. I still can't bootload any software, though, it keeps resulting in failures. :crying:
ConvolutedSpeech said:
Used the Odin tool (which I've done in the past without issue) to bootload the 4.4.2 software onto my phone and it now just flashes the start-up banner. Worse, my computer no longer recognizes my phone as a valid device, so attempts to load something else will not work.
---------- Post added at 11:21 AM ---------- Previous post was at 10:26 AM ----------
Okay, so, I've managed to get my device recognized by placing it in Odin Mode and reconnecting. I still can't bootload any software, though, it keeps resulting in failures. :crying:
Click to expand...
Click to collapse
This previous thread post gives some tips that might help you fix your phone:
http://forum.xda-developers.com/showthread.php?p=56167850
mattnmag said:
This previous thread post gives some tips that might help you fix your phone:
http://forum.xda-developers.com/showthread.php?p=56167850
Click to expand...
Click to collapse
I appreciate your taking the time to reply to my post. I read over the tips you listed and tried those I hadn't already. I've switched my usb cord to every port on my computer. I've switched to different cords, oem and otherwise. I downloaded KIES, as per the last of your suggestions, and can't say how useful that may or may not be, as my device never would connect to the KIES interface. I've had many attempted firmware loads on my phone via ODIN, but all give me the unsuccessful write message. I've tried flashing TWRP, which I was pretty sure I already had on my phone, but still no bueno. It won't let me access TWRP if I do have it, and if I don't . . . well, there's that. I don't really know what else to do.
---------- Post added at 07:18 PM ---------- Previous post was at 07:10 PM ----------
ConvolutedSpeech said:
I appreciate your taking the time to reply to my post. I read over the tips you listed and tried those I hadn't already. I've switched my usb cord to every port on my computer. I've switched to different cords, oem and otherwise. I downloaded KIES, as per the last of your suggestions, and can't say how useful that may or may not be, as my device never would connect to the KIES interface. I've had many attempted firmware loads on my phone via ODIN, but all give me the unsuccessful write message. I've tried flashing TWRP, which I was pretty sure I already had on my phone, but still no bueno. It won't let me access TWRP if I do have it, and if I don't . . . well, there's that. I don't really know what else to do.
Click to expand...
Click to collapse
Oh, I also tried ODIN 3.7, 3.9, and 3.10.
@ConvolutedSpeech,
You can not install a custom recovery like TRWP on your phone after it got upgraded to 4.4.2 because the bootloader is locked with no current method for you to unlock it.
The only thing you can do right now is to restore the phone back to factory stock 4.4.2. There's a root method called GhettoRoot for 4.4.2, but no bootloader unlock method at present.
If you can post the log from Odin showing the error you're getting when trying to restore your phone, that will help others to help you. (I'm not sure why Kies couldn't see your phone, but I would uninstall it now or make sure it's totally disabled when running Odin again since the 2 programs can conflict).
I won't be able to respond for a while due to my job, but maybe someone else can help out.
mattnmag said:
@ConvolutedSpeech,
You can not install a custom recovery like TRWP on your phone after it got upgraded to 4.4.2 because the bootloader is locked with no current method for you to unlock it.
The only thing you can do right now is to restore the phone back to factory stock 4.4.2. There's a root method called GhettoRoot for 4.4.2, but no bootloader unlock method at present.
If you can post the log from Odin showing the error you're getting when trying to restore your phone, that will help others to help you. (I'm not sure why Kies couldn't see your phone, but I would uninstall it now or make sure it's totally disabled when running Odin again since the 2 programs can conflict).
I won't be able to respond for a while due to my job, but maybe someone else can help out.
Click to expand...
Click to collapse
Thank you for all of your time. From looking at the posts on Ghettoroot it looks like it requires being able to send files to your phone and put it in debugging mode . . . which I can't so much do, given my phone won't let me in it. Maybe there's a workaround I'm missing? I uninstalled Kies and reran ODIN. Here's a c/p of the log:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I605VRUFND7_I605VZWFND7_I605VRUFND7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<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)
If anyone can help it would be much appreciated! Thank you mattnmag, for all of your efforts, so far!
ConvolutedSpeech said:
Thank you for all of your time. From looking at the posts on Ghettoroot it looks like it requires being able to send files to your phone and put it in debugging mode . . . which I can't so much do, given my phone won't let me in it. Maybe there's a workaround I'm missing? I uninstalled Kies and reran ODIN. Here's a c/p of the log:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I605VRUFND7_I605VZWFND7_I605VRUFND7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<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)
If anyone can help it would be much appreciated! Thank you mattnmag, for all of your efforts, so far!
Click to expand...
Click to collapse
Crickets, huh?
@ConvolutedSpeech,
Can you confirm that you do have a Verizon Note 2 model SCH-I605?
Also, did you try to Odin flash any other device's firmware onto your phone (like the international N7100 firmware). If so, that would have overwritten your Verizon bootloader/firmware and you won't be able to use ODIN to restore your phone if that's the case.
If you do have the Verizon Note 2 and didn't accidentally flash another device firmware onto it , then you should be able to restore your phone back to Verizon factory stock 4.4.2.
Droidstyle's restore guide has step by step instructions on how to Odin restore the phone. If you're not flashing the pit file with the firmware tar file... then try that as well.
If it won't work on your computer and you have access to another computer (preferably one with Windows 7), then try the restore on that. Also... make sure you have a good download of the firmware.... you can grab the Verizon 4.4.2 firmware from here if you're not getting it from Sammobile already: http://www.sammobile.com/firmwares/download/30950/I605VRUFND7_I605VZWFND7_VZW.zip/
mattnmag said:
@ConvolutedSpeech,
Can you confirm that you do have a Verizon Note 2 model SCH-I605?
Also, did you try to Odin flash any other device's firmware onto your phone (like the international N7100 firmware). If so, that would have overwritten your Verizon bootloader/firmware and you won't be able to use ODIN to restore your phone if that's the case.
If you do have the Verizon Note 2 and didn't accidentally flash another device firmware onto it , then you should be able to restore your phone back to Verizon factory stock 4.4.2.
Droidstyle's restore guide has step by step instructions on how to Odin restore the phone. If you're not flashing the pit file with the firmware tar file... then try that as well.
If it won't work on your computer and you have access to another computer (preferably one with Windows 7), then try the restore on that. Also... make sure you have a good download of the firmware.... you can grab the Verizon 4.4.2 firmware from here if you're not getting it from Sammobile already:
Click to expand...
Click to collapse
Hey mattnmag,
Yes, I do have a Verizon Note 2 SCH-I605. No, I've been trying to flash the Sammobile sourced version of the download you link to, but I suppose I could try redownloading it, for giggles, one never knows. I'll check out the restore guide and see if I'm missing anything. The computer I'm using is running on Windows 7, but I guess I could try my laptop, which also runs on 7. I really do appreciate all the time you've spent trying to help me.
Thanks!
---------- Post added at 06:50 AM ---------- Previous post was at 06:44 AM ----------
ConvolutedSpeech said:
Hey mattnmag,
Yes, I do have a Verizon Note 2 SCH-I605. No, I've been trying to flash the Sammobile sourced version of the download you link to, but I suppose I could try redownloading it, for giggles, one never knows. I'll check out the restore guide and see if I'm missing anything. The computer I'm using is running on Windows 7, but I guess I could try my laptop, which also runs on 7. I really do appreciate all the time you've spent trying to help me.
Thanks!
Click to expand...
Click to collapse
OIC, haha, that's the guide I used to brick myself. Probably I missed something, but I can't see what, at this point.
---------- Post added at 07:05 AM ---------- Previous post was at 06:50 AM ----------
ConvolutedSpeech said:
Hey mattnmag,
Yes, I do have a Verizon Note 2 SCH-I605. No, I've been trying to flash the Sammobile sourced version of the download you link to, but I suppose I could try redownloading it, for giggles, one never knows. I'll check out the restore guide and see if I'm missing anything. The computer I'm using is running on Windows 7, but I guess I could try my laptop, which also runs on 7. I really do appreciate all the time you've spent trying to help me.
Thanks!
---------- Post added at 06:50 AM ---------- Previous post was at 06:44 AM ----------
OIC, haha, that's the guide I used to brick myself. Probably I missed something, but I can't see what, at this point.
Click to expand...
Click to collapse
AAAAAAAAAAAAAAAAAAGGGGGGGGGGGGGHHHHHHHHHHH!!!!!!!! Okay, either I'm a dumbass, or you're a genius, but at this point I don't care how you want to label it. Flashing the PIT file WITH THE firmware worked beautifully . . . I think . . . my phone is now starting up and I got a full load and pass in ODIN. OMG, tytytytyty! I love you! Hahahaha, yes, it's definitely starting up! Yayyy! F*** yeah, MY PHONE IS ALIVE!
LOL. I'm glad to hear you fixed it. Just to be sure you get a totally fresh start with nothing leftover... it may be a good idea to boot into stock recovery and wipe cache and complete a factory reset.
:thumbup:
mattnmag said:
LOL. I'm glad to hear you fixed it. Just to be sure you get a totally fresh start with nothing leftover... it may be a good idea to boot into stock recovery and wipe cache and complete a factory reset.
:thumbup:
Click to expand...
Click to collapse
Thanks! Based on the success of taking your previous advice, I'll have to do that! Have an AWESOME Thanksgiving!
Returning to stock
So I know that there are different instructions for returning to stock with odin after having taken the MJ9 4.3 OTA update, but I honestly don't remember if I did take the update. I have had this phone for so long, as well as other phones, and I just can't remember if I took it. Is there a way to either be able to tell if I did, or to return to stock safely regardless?
eve.ning_rose said:
So I know that there are different instructions for returning to stock with odin after having taken the MJ9 4.3 OTA update, but I honestly don't remember if I did take the update. I have had this phone for so long, as well as other phones, and I just can't remember if I took it. Is there a way to either be able to tell if I did, or to return to stock safely regardless?
Click to expand...
Click to collapse
When you go to your phone's System Settings/About Phone, what does it show under Android Version and Build Number? That may help you determine what you're running.
An easy way to confirm what bootloader you're on would be to boot into Odin Mode (Volume Down+Home Button+Power Button at the same time, then press volume up to continue to Odin Mode). If it looks like the picture I've attached of ODIN mode from my phone (which is running 4.1.2), then your bootloader would not be on 4.3 or 4.4.2 because there's nothing about Knox.
But... if you see anything about Knox when in Odin mode, then it will be on 4.3 or higher bootloader. If it's on 4.3 or higher, then you won't be able to downgrade back to 4.1.2 and would need to restore to stock 4.3 or 4.4.2 (depending on what build version your on).
In Odin mode it says
ODIN MODE
PRODUCT NAME: SCH-I605
CUSTOM BINARY DOWNLOAD (Yes, 1 counts)
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
It looks like you're still on 4.1.1 or 4.1.2 bootloader... since there's no mention of Knox. You should be able to follow section 1b in Droidstyle's Restore guide to restore the phone to factory stock 4.1.2 VRAMC3. This is the bootloader you'll want to stay on if you want to have the option to use Casual to unlock the bootloader and root/run custom ROM's. Your phone would probably be more valuable to others as well if you're going to sell it on Swappa.
Edit: Look into Chainfire's Triangle away app from the Play Store if you want to reset the Binary count back to 0. (And only use Triangle away on rooted 4.1.2 with unlocked bootloader for our phone... if you try it on 4.3 or 4.4.2, it may hard brick the device. Here's the XDA thread on Triangle Away if interested: http://forum.xda-developers.com/galaxy-s2/orig-development/2014-01-15-triangleaway-v3-26-t1494114
Thank you! So I was originally restoring to stock unrooted because For some reason my phone stopped allowing me to flash any ROM. I unrooted, then rooted with casual noyou, and I still can't flash any ROM. I have verified that I do have root, and I have tried with both CWM and TWRP, but nothing. Any idea what could be causing this? Or how to fix it? I am stuck on stock 4.1.1 now.
I'm not sure if any of the custom ROM'S in the development threads will work with a 4.1.1 base... (they might.. but I'm not sure). I would probably use Droidstyle's guide to Odin restore the phone to 4.1.2 VRAMC3, then would boot into stock recovery and wipe cache & complete a factory reset just to make sure you've got a totally clean slate to work from.
Then, I'd run CASUAL again to root and unlock the bootloader.
(Edit)... I'm also wondering if the custom recovery that you were using to try to flash the ROM could have been too old for the newer ROM'S... or the wrong custom recovery. Some ROM'S need a specific version of the custom recovery to work, so make sure you read through the thread of whichever ROM you want to flash and that you're using the recommended version of the recovery for that specific ROM.
soft bricked note 2?
i wanted to give my son my note 2 for christmas, but i didnt want him to have a rooted phone. i have unrooted and returned to stock a few note 2 phones with no problem, but ..... this time ive run into trouble. i put the proper files into the pda slot, hit start, i got a pass. but i think im on a bootloop. i cant get into recovery, but i can get back into download mode. i would really appreciate some help. this was gonna be his "big" gift and now im screwed thanks so much for all you guys do on this site. ive gotten so much help here.
take care and merry chrismas
Verizon note 2 Root problems.
I had my Note 2 SCH-I605 rooted before this, I bricked it and now its back to life but I can not get anything to work for root. I have tried odin,casual and kingo root and Ghettoroot. Odin says It has passed etc... and I never have root. Kingo says it works and that it has installed su but its never there. I have even checked with root checker to verify. And no root. I have the stock firmware (4.4.2) back on and I used odin to put the stock firmware back on. Can anyone shed any light on what I might be doing wrong.
chanelstout said:
i wanted to give my son my note 2 for christmas, but i didnt want him to have a rooted phone. i have unrooted and returned to stock a few note 2 phones with no problem, but ..... this time ive run into trouble. i put the proper files into the pda slot, hit start, i got a pass. but i think im on a bootloop. i cant get into recovery, but i can get back into download mode. i would really appreciate some help. this was gonna be his "big" gift and now im screwed thanks so much for all you guys do on this site. ive gotten so much help here.
take care and merry chrismas
Click to expand...
Click to collapse
I downloaded stock firmware then applied with odin. It was 4.4.2 if I find the link ill post as soon as I can.
Hello all,
I want to preface everything that while I know a bit about rooting and messing with the stock status of android phones, I'm still generally a newbie at this.
Last night I started experiencing problems with my phone. I was using it normally until it ran out of battery while in a call, but I figured this happened in the past so it shouldn't be a problem. I plugged it in, however it wouldn't boot up. The CM11.2 loading screen just wouldn't stop spinning. Booting into recovery and download mode was working fine, but I couldn't get into the OS. Since I wanted for a long time to upgrade my Jellybean to Lollipop (and found this thread http://forum.xda-developers.com/gal.../rom-cyanogenmod-12-1-nightly-builds-t3147661 just last night), I decided it's time.
I boot into recovery and try and backup my data, but as soon as I click, the device freezes. Fast forward 5 attempts later with 3 different SD cards, it would still do the same thing. Already annoyed, I decide just to factory reset/wipe data, in order to flash the new Nightly and Gapps. As soon as I click, same thing happens, the CWM freezes and I have to manually reboot.
I figured the CWM is corrupt and I started searching on forums what to do. Tried flashing a new CWM with Odin (specifically this) but now I can't boot into recovery anymore, only download mode. I'm scared of doing more on my own. The current state of the phone is that it stays frozen at the "Samsung Galaxy S2" screen, the one with the yellow triangle w/ "!". Could you please help?
@Ricksis
Personally what I would try next is flashing a stock rom with odin and starting again. Although I suspect you might have hardware issues. A lot of S2's are dying these days.
If you can find someone who can lend you a battery(I know, not too many S2's out there any more!) try that, as it is possible the battery is causing these issues. Good luck
Edit: Remember to flash stock pit(if you flash stock rom) if you have repatitioned previously
noppy22 said:
@Ricksis
Personally what I would try next is flashing a stock rom with odin and starting again. Although I suspect you might have hardware issues. A lot of S2's are dying these days.
If you can find someone who can lend you a battery(I know, not too many S2's out there any more!) try that, as it is possible the battery is causing these issues. Good luck
Edit: Remember to flash stock pit(if you flash stock rom) if you have repatitioned previously
Click to expand...
Click to collapse
I don't have problems with the battery generally. It lasts for 8-12h on a normal day (which I think it's a lot for a 3 year old 2000mAh battery), and almost 3 days with the phone in standby. It just happened that last evening I was stuck in a call and away from a plug. Sadly, like you said, noone that I know still has an S2 around.
As for the stock rom, is there one that you would recommend? I'm really reluctant to do more steps on my own. I have not repartitioned and I tried to stay away of PIT flashes since I have also read last night about how they should be the last resort, because they have a high chance of bricking the device.
I tried getting a stock firmware from Sammobile, specifically firmwares/confirm/14909/I9100XWLSU_I9100OROLS5_ORO/. I tried flashing it, and this happened:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100XWMS2_I9100BULS3_I9100VDFLSF_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> cache.img
<ID:0/003> factoryfs.img
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Ricksis said:
I don't have problems with the battery generally. It lasts for 8-12h on a normal day (which I think it's a lot for a 3 year old 2000mAh battery), and almost 3 days with the phone in standby. It just happened that last evening I was stuck in a call and away from a plug. Sadly, like you said, noone that I know still has an S2 around.
As for the stock rom, is there one that you would recommend? I'm really reluctant to do more steps on my own. I have not repartitioned and I tried to stay away of PIT flashes since I have also read last night about how they should be the last resort, because they have a high chance of bricking the device.
Click to expand...
Click to collapse
A battery can die suddenly. I recommend trying to rule it out first as the problems you describe can be because of a battery that has come to the end, and if it is the case you may not get past it.
Anyway get a stock rom for your region from
sammobile.com
or http://androidfirmwares.net/Home/sgs2
or http://www.tsar3000.com/Joomla/inde...alaxy-sii-firmware&catid=55:samsung&Itemid=82
noppy22 said:
A battery can die suddenly. I recommend trying to rule it out first as the problems you describe can be because of a battery that has come to the end, and if it is the case you may not get past it.
Click to expand...
Click to collapse
I tried flashing 3 different stock roms, they all failed like at 3%. I found a friend with an S2, going to his place later today. What should I do/expect from his battery ?
Ricksis said:
I tried flashing 3 different stock roms, they all failed like at 3%. I found a friend with an S2, going to his place later today. What should I do/expect from his battery ?
Click to expand...
Click to collapse
I'm not sure you can expect anything. It's just a common problem. See if you can get it fully charged and try the stock rom with odin again. Also check out this guide
As I said it seems like there is a hardware problem, the battery is just where I would start. Once you can rule that out you can look elsewhere
From your description, your odin flash got past the 'nand write' stage which is where most odin flashes fail.....from that point of view, things are a lot more positive than for other users facing odin flash fails.....
Can you confirm that your device is the international variant? It's just that in your OP you mention flashing a cwm package that you found on the Verizon S2 forum.
http://i.imgur.com/rVnFwJM.jpg
keithross39 said:
From your description, your odin flash got past the 'nand write' stage which is where most odin flashes fail.....from that point of view, things are a lot more positive than for other users facing odin flash fails.....
Can you confirm that your device is the international variant? It's just that in your OP you mention flashing a cwm package that you found on the Verizon S2 forum.
Click to expand...
Click to collapse
I tried with multiple stock roms, but they all fail in the same stage. I bought the phone carrier free, and its code is GT-I9100 (no extra letters afterwards like a lot of S2s have). I also found another solution, but it stopped after NAND WRITE start.
Hopper8 said:
Another option for i9100
If you have an i9100, probably the best option to flash is to flash 4.1.2 JellyBean leak. Huge thanks to It_ler for providing the file after it was lost during the shutdown of hosting site hotfile.com and re-hosting on his dev-host, and for keithross39 for re-hosting the file on his storage. Download it here: or here. This is a 3-part firmware. It will wipe your device as it flashes, and in many cases this extra wipe while flashing contributes to a successful flash. To set this file up in Odin (as it is 3 parts): PDA = CODE_I9100XXLSJ.tar, PHONE = MODEM_I9100XXLS6.tar, and CSC = CSC_HOME_OXX_I9100OXXLS1.tar. As usual, do not tick 'repartition'.
Click to expand...
Click to collapse
I also found this http://forum.xda-developers.com/chef-central/android/nand-write-start-fail-odin-soluction-t2851096
That 3 part firmware mentioned in your quoted text has a better chance of successful flash than a regular firmware as it formats and repartitions the device during the flash.....normal firmwares just overwrite what is already on the device.
I've had a quick look at the thread you linked to, and from what I understand, the OP is providing a way to flash the firmware partition by partition......
In theory, this is a good solution, but unfortunately, I don't know enough about the firmware structure or about the odin flashing process to be able to meaningfully pass comment on that method.......My uninformed instinct tells me 'why not'......but my practical, logical side tells me 'caution'....
http://i.imgur.com/rVnFwJM.jpg
keithross39 said:
That 3 part firmware mentioned in your quoted text has a better chance of successful flash than a regular firmware as it formats and repartitions the device during the flash.....normal firmwares just overwrite what is already on the device.
Click to expand...
Click to collapse
In Odin 3.07, everything but PDA is greyed out for me. I donwloaded v1.85 and tried the 3 part thing: Odin freezes at NAND Write Start!!, and as for my phone, there is no blue progress bar appearing on the screen in the first place while i'm in download mode.
Just tried the pit file solution as well:
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Re-Partition operation failed.
Things to check for odin flashing.......
1) firewall disabled
2) antivirus disabled
2) all Kies processes killed (use task manager)
4) run Odin as administrator
5) only use main board USB sockets (pc/laptop side)
6) make sure Samsung drivers correctly installed.
7) windows 8 & 10 may not allow odin to operate correctly.
8) Use official Samsung usb lead.....no cheap s**te off eBay
9) try all usb ports on pc/laptop
10) try different cables
11) try different PC's/Laptops.......
12) do the whole procedure multiple times.....Odin flashing is a bit like playing the lottery......it may not work the first 9 or 19 times, but for some reason, on the 10 or 20th attempt, it does.......
The only thing that will 'win the day' is perseverance......
http://i.imgur.com/rVnFwJM.jpg
---------- Post added at 11:33 PM ---------- Previous post was at 11:22 PM ----------
There is (possibly) a plan B.......
Are you able to get into recovery?
If you are, you *could* try flashing PhilZ recovery which will root your phone.....then you can give flashing a custom rom a try.......
You possibly still could go that route even without recovery......by (maybe) Odin flashing a custom kernel .tar and then flashing a custom rom......
(I'm not talking about the latest CM12. ....but an older KK or JB based rom.....they're far more stable and complete than the LP based roms.....)
http://i.imgur.com/rVnFwJM.jpg
I had a busy week and only could try some solutions today. Unfortunately, I think they ended up with the hardbrick of my phone, as I am not able to turn it on anymore, not even in download mode.
Are you *sure* that it's not just a failed battery.....you mentioned previously, that you thought there might be an issue with it.....
http://i.imgur.com/rVnFwJM.jpg
keithross39 said:
Are you *sure* that it's not just a failed battery.....you mentioned previously, that you thought there might be an issue with it.....
Click to expand...
Click to collapse
I'm not sure, but I kinda fiddled enough with ODIN for just the battery to be the cause. Of course I am no expert, but I see no connection between the battery failing and all the other problems: cwm11.2 not wiping cache/dalvik or performing factory resets, the option to only boot in download mode later, etc. When I plug the phone to the USB port, nothing happens anymore.
Sooooo... RIP phone? ...
Ricksis said:
Sooooo... RIP phone? ...
Click to expand...
Click to collapse
If you are sure there's nothing else you can try........
But, even though it's an old device, it's still going to cost money to replace it....
You mentioned that odin failed to recognise it......
Another *possibly* would be the USB socket......
It would account for the lack of odin recognition *AND* a dead (uncharged) battery which could lead you to assume the whole phone is dead.
The port may have been ok at the start of your recovery attempts, but they do wear out (especially on older devices simply due to wear and tear) and by the last attempt it could have failed......
The part costs pocket change on ebay and is relatively easy to replace....I've done it myself......
Here's a guide I wrote on replacing the board......
http://forum.xda-developers.com/showthread.php?t=2335961
http://i.imgur.com/rVnFwJM.jpg