Dear XDA'ers,
I know their are a lot of topics on this problem, but I can't seem to find the answer.
The first thing I tried was going into recovery mode and doing a factory reset. That did not do the trick.
After that I wasn't able to get into recovery mode anymore, so I went online and searched some topics.
I downloaded a stock S2 ROM and flashed it through ODIN, but it kept failing.
From searching topics it seemed like my S2 suffered from NAND rw corruption.
And nothing fixed, so eventually I went to flash the bootloader. This was the first flash that was succesfull and it got me back to the samsung home screen. Then I tried to flash a new 3 part stock ROM, but it is not working, it keeps getting stuck at this point.
Any one that can talk me through this? Have not a lot of experience with this, so please try to keep it simple for me.
Thanks in advance
If the NAND is really stuffed, motherboard replacement. There is no other fix. Or you could search for Hopper8's 'Odin troubleshooting' thread & keep trying the stuff in the thread over & over & over.
Up to you.
MistahBungle said:
If the NAND is really stuffed, motherboard replacement. There is no other fix. Or you could search for Hopper8's 'Odin troubleshooting' thread & keep trying the stuff in the thread over & over & over.
Up to you.
Click to expand...
Click to collapse
but if that would be stuffed. I shouldn't be able to flash a bootloader should I?
You're the one who mentioned NAND corruption.
If the NAND really is corrupted, then that's the fix. And no, 'successfully' flashing a bootloader (or anything) does not necessarily mean the phone is easily fixable. 'Success' in Odin without the phone working/booting normally isn't success at all.
As per my previous post, find the thread (which really is the reference of these things here), try the stuff in it, see if you can fix it.
If not, you know what to do.
same problem bootlooping
hi guys i am currently having the same problem, i successfuly flashed the JB stock firmware but it's still keep bootlopping..my combo button doesnt work so i am using USB JIG to go into donwload mode, i can even go to recovery mode..hoping for some can link me or provide with FULL PACKAGE, meaning it has a PIT file, BOOTLOADER, CSC, PDA AND PHONE..I think this will be my last resort, so if anyone having this file im looking for plz plz plz direct mo to tha..thnaks
yes u have emmc corruption I have fixed it
but my fix was for data partition your problem is the kernel partition ill make a fix for your phone and inform u soon
Sent from my GT-I9100 using xda premium
follow my guide
http://forum.xda-developers.com/showthread.php?t=2400535
but instead of using the data fix pit as mentioned in the guide use the attached kernel fix pit file the rest of the steps are the same
Sent from my GT-I9100 using xda premium
iamtalha said:
follow my guide
http://forum.xda-developers.com/showthread.php?t=2400535
but instead of using the data fix pit as mentioned in the guide use the attached kernel fix pit file the rest of the steps are the same
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
No luck .
Stuck at NAND WRITE:
Log:
<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> Firmware update start..
<ID:0/006> zImage
<ID:0/006> NAND Write Start!!
Related
Hello everyone!
First of all, let me start by thanking everyone for such a wealth of information here on XDA Developers! And a big thanks goes to all the devs who worked so hard to provide us with some wonderful tools/apps and help as well!
Now, my problem is that I am a complete noob. I tried my best to do some research before I could start playing around with roms and what not. I rooted my Samsung Galaxy VIBRANT and after rooting it, I wanted to install the Voodoo lagfix. I used the instructions available here. After that, the phone stopped working in a way that it kept going back to Recovery Mode. Every time I had to select REBOOT option only to end up in Recovery Mode again.
I then tried to use ODIN to get back to stock as it made most sense. I downloaded the files by following this link http://forum.xda-developers.com/showthread.php?t=734475&highlight=stock+JFD and followed the instruction. Odin successfully finished the task and then my phone rebooted and the glorios Samsung GALAXY S logo appear but after that everything goes dark and by everything I mean everything but the 4 touch sensitive buttons. They are lighting up but the screen doesn't work.
Naturally, I didn't panic because from what I have read here, it is very difficult to brick the phone as ODIN appears to always come to rescue. The thing is that it just doesn't move forward.
After a while, I started to panic and then I following this link http://forum.xda-developers.com/showthread.php?t=1047087 and download the files again and followed all the instruction but with same result.
Here is the ODIN log
<ID:0/008> Added!!
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> cache.rfs
<ID:0/008> modem.bin
<ID:0/008> factoryfs.rfs
<ID:0/008> dbdata.rfs
<ID:0/008> param.lfs
<ID:0/008> zImage
<ID:0/008> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/008> Removed!!
<ID:0/007> Added!!
<ID:0/007> Removed!!
After ODIN is done doing it's thing and the phone reboots, it says "Data Wipe Failed" just for a second before it boots to the Galaxy S logo screen. Afer this, it goes dark.
Guys, have I done the almost undoable? Have I just bricked my phone? I tried to search for this problem but maybe I suck at it and couldn't really find anything very useful and related to my problem so I decided to start a new thread. I apologize if I should have tried some other keyword to get better search results but believe when I say that I really did try.
There are thousands of brilliant android minds here and I am dead sure that someone will help me out of this grave situation and save me from using my old Nokia 5800 XM again!!!
Thanks again,
Z
Try these 3 methods!!
aio toolbox
usb jig
or
power off phone
pull out battery
GRAB THIS STUFF : http://forum.xda-developers.com/showthread.php?t=1047087
turn on odin
attach phone to pc with usb cable
now while holding down both volume buttons put battery back in.
now you should be in download mode and go back to stock with odin from here!
make sure u put the proper tar file in pit and the .pda file in pda in there proper places on odin and ur set to go.
Enjoy and also make sure u have the proper samsung drivers
Thank you for your answer. I have already tried the ODIN method to no avail. The phone screen is still black while the touch sensitive buttons are on. I have no idea what the following are
aio toolbox
usb jig
And I am going to take a look at it. While I do that, could you please tell me if you think that I have bricked my cellphone already?
zee.syed said:
Thank you for your answer. I have already tried the ODIN method to no avail. The phone screen is still black while the touch sensitive buttons are on. I have no idea what the following are
aio toolbox
usb jig
And I am going to take a look at it. While I do that, could you please tell me if you think that I have bricked my cellphone already?
Click to expand...
Click to collapse
I don't think the toolbox will help you
http://forum.xda-developers.com/showthread.php?t=954509
http://www.mobiletechvideos.com/blog/?tag=jig
the later you can go to youtube and see it in action
Thank you everyone for your help! I kept searching and searching and I finally found the solution. Here is what I did...
Follow this link: http://forum.xda-developers.com/showpost.php?p=8698655&postcount=150
Download "Froyo That does not Brick" HERE
Download "True Stock 2.1 firmware for Vibrant" from HERE
Follow the instruction posted HERE
Remember that after the first step, you WILL see error in recovery mode. Do not panic and take out the battery and proceed with Step 2 and that'll help you. I hope this will help.
Now, I have another question. Can is it safe to ROOT my phone again? If it is, what method should I use since I am back on Eclair?
Thank you,
Zee
zee.syed said:
Thank you everyone for your help! I kept searching and searching and I finally found the solution. Here is what I did...
Follow this link: http://forum.xda-developers.com/showpost.php?p=8698655&postcount=150
Download "Froyo That does not Brick" HERE
Download "True Stock 2.1 firmware for Vibrant" from HERE
Follow the instruction posted HERE
Remember that after the first step, you WILL see error in recovery mode. Do not panic and take out the battery and proceed with Step 2 and that'll help you. I hope this will help.
Now, I have another question. Can is it safe to ROOT my phone again? If it is, what method should I use since I am back on Eclair?
Thank you,
Zee
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=849028
get the update.zip from there and put it on sd (16gb)
go to recovery reinstall packages
reboot and done
get rom manager off market and flash clockwork recovery choosing vibrant if you want to flash roms
If someone could help me I would be forever grateful. I got my AT&T GS3 yesterday and today after a LOT of hesitation I decided to see if I could root it. I couldn't find a lot of helpful resources and I ended up at the guide found at galaxys3root.com/galaxy-s3-root/how-to-root-galaxy-s3/. I was somewhat afraid because the guide refers to the I9300 but mine is the I747 and it turns out that fear was justified. Odin says FAIL with an ominous red background and says the following:
Code:
<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> Firmware update start..
<ID:0/006> recovery.img
<ID:0/006> NAND Write Start!!
<ID:0/006> cache.img
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
After that I looked at my phone's screen and it had a short message in red that said "Unsupport dev_type". Now when I turn on the phone I am greeted by the ODIN MODE screen and a message that says "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
At this point I don't have critical data that can't be restored though I would love to not lose my data anyway. I am much more concerned about being able to boot my phone again. Is there any hope or am I totally screwed?
Search Chainfire thread here to see if your device is supported for rooting
http://forum.xda-developers.com/showthread.php?t=1695238
For official firmware and guide (and also rooting) try Intratech thread here:
http://forum.xda-developers.com/showthread.php?t=1671969
Sent from my GT-P6810 using XDA Premium HD app
I wish I had found that thread via my google searches before I attempted to root. I am certain that there is no working root right now for my I747. I am really hoping there is something else I can do to get my phone working again. At least my phone works in odin/download mode still. I just hope there is some way I can fix whatever the cf root did to my phone. Any further suggestions?
Reinstall official firmware and then make a backup and flash the correct I747 root. nothing from I9300 will work with your model
Sent from my GT-I9300 using xda premium
Get the official firmware from the link posted above and flash it via Odin.
when the Sgs2 was release last year for att I accidentally flash the International (I9000) on it so I know how you feel
Sent from my GT-I9300 using xda premium
Dang...guess I'll just have to wait for a firmware to be posted for mine. Unfortunately there is no stock firmware released yet for mine. I just found this thread as well where others have done the same thing inadvertently and are also waiting for a stock boot.img: http://forum.xda-developers.com/showthread.php?t=1703488&page=19
possible solution
I don't know if this will help but i managed to get out of the same situation. After getting the error the phone would boot and tell me to fix w Kies. I found that if I took the battery out for a while then started it back up using vol down and home button then plugged phone in after the warning, and hit volume down my phone telling it to reboot and it started up no problem.
You know there is a forum for the AT&T version right? There is a rooting guide there. ALWAYS make sure that you are using the root method for the RIGHT model of phone before you do anything.
Go the to the XDA main forum page. Scroll down to the bottom and you will see the AT&T GSIII forum areas.
Thanks to the work of several people who did the same thing I was able to recover the stock boot.img. For anyone else who lands on this thread, you can find a stock boot and instructions at http://forum.xda-developers.com/showthread.php?t=1727443.
Baldilocks, I will always make sure to go there from now on. Usually I haven't been much more than a casual lurker of the forums so I wasn't aware of that but I've learned my lesson. Thanks everyone!
v0rtex said:
Thanks to the work of several people who did the same thing I was able to recover the stock boot.img. For anyone else who lands on this thread, you can find a stock boot and instructions at http://forum.xda-developers.com/showthread.php?t=1727443.
Baldilocks, I will always make sure to go there from now on. Usually I haven't been much more than a casual lurker of the forums so I wasn't aware of that but I've learned my lesson. Thanks everyone!
Click to expand...
Click to collapse
I try everything, with several boots, odin versions, etc. The main problem was the usb . It works without problem with the new one usb.
i was following steps to install google now in this thread
http://forum.xda-developers.com/showthread.php?t=1749045
when i came to step of changing value the file wouldnt save my change so i gave extra(besides read and write i also checked execute and special) permission of build.prop file in system folder.
i restarted my phone after that and now phone shuts down after galaxy boot logo.
i tried following this thread
http://forum.xda-developers.com/showthread.php?t=1737855
i can get to download mode, but when i get to step of installing stock rom through odin it isnt working
i get error in odin:
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
main line i messed up permission of build.prop how to can i replace it from odin?
thanks
please dont tell me my 500 bucks drain down the toilet. :crying:
Can you enter download mode?
If so, try restoring your phone with the factory Rom using odin
Sent from my SPH-L710 using Tapatalk 2
If you can't get into download mode you are screwed! Sorry
But if you can you should be able to flash stock through Odin.
Sent from my SGH-T999 using xda premium
yes i can get to download mode but i cant install stock rom.
thats what the t-mobile thread was asking to do. i can install stock kernel but not rom.
Why were you trying to install google now, when they said in the thread that it was only for ASOP Roms (CM9 or AOKP) anyway? Maybe try to push via adb if someone has a copy for you model if possible.
crystalstylez said:
Why were you trying to install google now, when they said in the thread that it was only for ASOP Roms (CM9 or AOKP) anyway? Maybe try to push via adb if someone has a copy for you model if possible.
Click to expand...
Click to collapse
can you please tell me how it is done or link me some thread you would recommend?
thanks
Good luck. This is ugly. I still have not rooted my device because besides working great as is, I am not comfortable hacking it. I know if I mess it up it is my fault and the thought of ruining it and cost I paid is making me cautious. I may hack it down the line. But for now, I'm going to enjoy it as is.
Hopefully, you get it restarted somehow.
omar300 said:
i was following steps to install google now in this thread
http://forum.xda-developers.com/showthread.php?t=1749045
when i came to step of changing value the file wouldnt save my change so i gave extra(besides read and write i also checked execute and special) permission of build.prop file in system folder.
i restarted my phone after that and now phone shuts down after galaxy boot logo.
i tried following this thread
http://forum.xda-developers.com/showthread.php?t=1737855
i can get to download mode, but when i get to step of installing stock rom through odin it isnt working
i get error in odin:
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
main line i messed up permission of build.prop how to can i replace it from odin?
thanks
please dont tell me my 500 bucks drain down the toilet. :crying:
Click to expand...
Click to collapse
I'm guessing u installed all the right drivers if Odin sees your phone right? Are u using the most updated version of Odin made for our phones? U try download the rom agn? Maybe bad download, if yes try download a different version of rom, maybe the rooted one or if that's the one u used download the factory one, u try different computer? Reboot computer? , pull battery from phone for few min, some of these things sound stupid and pointless but take it from a guy with 7 samsungs its almost impossible to brick a Samsung
yea i got all the drivers and download correctly working. its weird cus it can install kernal and not rom, oh and im trying to install stock rom. only stock rom for t mobile comes in .tar type all other are made for cmw .zip format. im sure it can be unbricked but it will take some developer to get that done. i found this thread where alot of people messed up on same thing so hoping there will be solution soon. http://forum.xda-developers.com/showthread.php?p=28531684#post28531684
omar300 said:
yea i got all the drivers and download correctly working. its weird cus it can install kernal and not rom, oh and im trying to install stock rom. only stock rom for t mobile comes in .tar type all other are made for cmw .zip format. im sure it can be unbricked but it will take some developer to get that done. i found this thread where alot of people messed up on same thing so hoping there will be solution soon. http://forum.xda-developers.com/showthread.php?p=28531684#post28531684
Click to expand...
Click to collapse
What about the tool kit? U can install rooted rom from there while in Odin no? Try the 3.06 version of Odin? I.mean **** what u have to lose at this point . I'd still redownload the file if was me even if waste of time . I have a at&t version and we have 100% stock Odin and a rooted Odin ..
U said u can install the kernel?? Can u get into cwr with correct kernel? Probably dumb question but I asked anyway
Rooting is of no real risk for ATT at least.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
drawde40599 said:
What about the tool kit? U can install rooted rom from there while in Odin no? Try the 3.06 version of Odin? I.mean **** what u have to lose at this point . I'd still redownload the file if was me even if waste of time . I have a at&t version and we have 100% stock Odin and a rooted Odin ..
U said u can install the kernel?? Can u get into cwr with correct kernel? Probably dumb question but I asked anyway
Click to expand...
Click to collapse
I reinstalled the cwr and went in it and advance restored the system and it worked!
A friend of mine over at a Swedish forum is having problems with his SGS3 i9300. His phone just died, completely random, and refused to boot. he can only boot to download mode, nothing else.
He tried flashing a stock nordic ROM, which failed since ODIN threw him a "there is no pit partition" message. He tried flashing various PIT files, but it all stops with "there is not PIT partition" He did not do anything to his device for this to happen, it just died on him and that's where it all started.
Shot in the dark, but has his NAND memory somehow crashed, which caused the error of not booting/not accepting PIT files?
Theshawty said:
A friend of mine over at a Swedish forum is having problems with his SGS3 i9300. His phone just died, completely random, and refused to boot. he can only boot to download mode, nothing else.
He tried flashing a stock nordic ROM, which failed since ODIN threw him a "there is no pit partition" message. He tried flashing various PIT files, but it all stops with "there is not PIT partition" He did not do anything to his device for this to happen, it just died on him and that's where it all started.
Shot in the dark, but has his NAND memory somehow crashed, which caused the error of not booting/not accepting PIT files?
Click to expand...
Click to collapse
Hi! It just happened to me today! In the morning I was using the phone - calling someone.
Then put it into my pocket, went to work, and there it was already at the boot page, and staying there when resetting.
Tried to flash with odin, and I get the same error message as your friend.
I had a stock 4.0.4 rom, never touched anything on the phone yet.....
Any idea from someone?
edit:
as i9000 has linked to newer firmware with everything in post bellow, so just use that.
http://forum.xda-developers.com/show....php?t=1825272
niches said:
Hi! It just happened to me today! In the morning I was using the phone - calling someone.
Then put it into my pocket, went to work, and there it was already at the boot page, and staying there when resetting.
Tried to flash with odin, and I get the same error message as your friend.
I had a stock 4.0.4 rom, never touched anything on the phone yet.....
Any idea from someone?
Click to expand...
Click to collapse
Return under warranty .
jje
JJEgan said:
Return under warranty .
jje
Click to expand...
Click to collapse
yeah, problem is I bought it from amazon.de so I have to send it then via Post :S
tumult said:
full firmware flash with pit, bootloader, tz, etc..
hooe the link still works, if not i can make mirror tomorrow
also check in Odias thread in original android development if pit for 16 & 32 is same, but as far as i remember it is.
ps. i have flashed this firmware (without pit, but it is safe to download , no viruses, etc).
hope it helps
Click to expand...
Click to collapse
Thanks, I'll try it when I arrive home from celebrating the 253rd birtday of Mr. Guiness
Theshawty said:
A friend of mine over at a Swedish forum is having problems with his SGS3 i9300. His phone just died, completely random, and refused to boot. he can only boot to download mode, nothing else.
He tried flashing a stock nordic ROM, which failed since ODIN threw him a "there is no pit partition" message. He tried flashing various PIT files, but it all stops with "there is not PIT partition" He did not do anything to his device for this to happen, it just died on him and that's where it all started.
Shot in the dark, but has his NAND memory somehow crashed, which caused the error of not booting/not accepting PIT files?
Click to expand...
Click to collapse
All ROMs have full set images of partitions and may be flash with pit and repartition, pit - attached...
http://forum.xda-developers.com/showthread.php?t=1825272
as i9000 said:
All ROMs have full set images of partitions and may be flash with pit and repartition, pit - attached...
http://forum.xda-developers.com/showthread.php?t=1825272
Click to expand...
Click to collapse
edit: i was wrong, all partitions are there.
when you say full partition, you mean sboot.bin and tz.img also? sorry, don't think so , but if so good to know.
that's why i posted link above, that was only full firmware I could find.. but maybe it's just me.
tumult said:
when you say full partition, you mean sboot.bin and tz.img also? sorry, don't think so , but if so good to know.
that's why i posted link above, that was only full firmware I could find.. but maybe it's just me.
Click to expand...
Click to collapse
You can watch attached screen, 9 images:
sboot.bin
param.bin
tz.img
boot.img
recovery.img
system.img
cache.img
hidden.img
modem.bin...
You upload link of ROM full service ROM for Russia...
Why swedish man csc ser, russian location?
all the more so very old...
as i9000 said:
You can watch attached screen, 9 images:
sboot.bin
param.bin
tz.img
boot.img
recovery.img
system.img
cache.img
hidden.img
modem.bin...
You upload link of ROM full service ROM for Russia...
Why swedish man csc ser, russian location?
all the more so very old...
Click to expand...
Click to collapse
and i said sorry if i missed it .. anyway, i will delete my link then as yours are uptodate.
tumult said:
and i said sorry if i missed it .. anyway, i will delete my link then as yours are uptodate.
Click to expand...
Click to collapse
should not be deleted link, and the Russian people attend the xda forum ...
tumult said:
edit:
as i9000 has linked to newer firmware with everything in post bellow, so just use that.
http://forum.xda-developers.com/show....php?t=1825272
Click to expand...
Click to collapse
this is all great, but I think that does not work, I have met with this diagnosis: "there is no pit partition"
INTERNAL MMC IS DEAD... ((((
I'm having a similar problem. Except mine is a GT-I9300. Odin gives me this error.
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006>
<ID:0/006> There is no PIT partition.
<ID:0/006> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
TinyGrasshopper said:
I'm having a similar problem. Except mine is a GT-I9300. Odin gives me this error.
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006>
<ID:0/006> There is no PIT partition.
<ID:0/006> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Hey all, I have exactly the same error message. Running cm10 and my phone just froze, after re-boot i'm stuck on boot screen, no recovery and can only enter download mode....HELP!!!!
Someone reported that they had success with flashing the CF-Root to gain CWM recovery back and then flashing DarkyROM from it. But I don't know if that is even true.
PjotrFias said:
Someone reported that they had success with flashing the CF-Root to gain CWM recovery back and then flashing DarkyROM from it. But I don't know if that is even true.
Click to expand...
Click to collapse
thanks for the reply, i tried it but to no avail :crying:
Where did it stop? The first part?
PjotrFias said:
Where did it stop? The first part?
Click to expand...
Click to collapse
yeah i got the no pit message, tried flashing the pit file but won't do it...
I've just received this error on my phone too, Has there been any progress on solutions to this?
Another problem is that I can get into download mode and my system status is "Custom", How will this effect a return to manufacturer?
alot of replies with this errors lately...u guys used any custom FW ?
I had the latest 4.1.2 stock OTA installed via CWM and I wanted to unroot and go back to stock and that seemed to work fine.... I went to the old version VRALL4 and once rebooted it asked me to update OTA so I did and that was fine........ and it asked me to do it again for some reason and now I'm in a boot loop. The Galaxy note 2 logo flashes on the screen real fast and turns off over and over. I can only get into ODIN and not stock recovery. I've tried re-flashing the original odin package, and the pre-rooted odin packages and nothing is working.... what can I do? am i fux0rd? thx
edit: also USB all drivers are installed .......
Try a factory reset in the stock recovery. Then give it a whirl.
Sent from my SCH-I605 using Tapatalk 2
enkrypt3d said:
I had the latest 4.1.2 stock OTA installed via CWM and I wanted to unroot and go back to stock and that seemed to work fine.... I went to the old version VRALL4 and once rebooted it asked me to update OTA so I did and that was fine........ and it asked me to do it again for some reason and now I'm in a boot loop. The Galaxy note 2 logo flashes on the screen real fast and turns off over and over. I can only get into ODIN and not stock recovery. I've tried re-flashing the original odin package, and the pre-rooted odin packages and nothing is working.... what can I do? am i fux0rd? thx
edit: also USB all drivers are installed .......
Click to expand...
Click to collapse
Checkout this thread by Adam Outler called "DON'T ACCEPT OTA UPDATES" in the Verizon Galaxy Note II General section. I'm aware that you aren't experiencing this specific problem, but it should fix your boot loop problem. You'll need the two files that he makes available just below the picture. I've had others tell me that they used those files to successfully fix boot loops.
RomsWell said:
Try a factory reset in the stock recovery. Then give it a whirl.
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
I can only get into odin... not even stock recovery. the odin app doesn't even work most of the time....
If i hold vol up + power + home it just continues to boot loop flashing the note 2 logo....... downloading one more odin file to see if this can fix it..... :crying:
I knew I should have used triangle away before doing this as if I take it to the VZ store they're going to be able to tell that it'd been modified before....
The lesson you should learn from this is DO NOT ACCEPT OTAS! Not sure how you haven't understood that since it has been stated more than enough times in almost every thread.
BoostedB18C said:
The lesson you should learn from this is DO NOT ACCEPT OTAS! Not sure how you haven't understood that since it has been stated more than enough times in almost every thread.
Click to expand...
Click to collapse
First of all, I'm not a noob and I did get the system back up.... as I said above i was trying to UNROOT not ROOT my device using Odin which I have done many times. This is the first time I've ran into the boot loop issue.... so I flashed a stock unrooted odin tar.md5 and this is the issue that I had.... now when I did that, I thought I was unrooted but obviously the bootloader did not get flashed back to stock... anyways thanks for your oh so useful post in lumping me in with the n00bz... :laugh:
anyways
now im facing another issue where its still has the rooted bootloader installed but an "official" stock rom on it.....
I'm not saying you're a noob. All I'm trying to get you to understand is to read before doing. As with your unlocked bootloader issue, you probably overlooked that there are 2 ways to restore to stock. One re locks the bootloader and the other doesn't. Read more and don't skim the guide, that's all I'm saying my dude.
BoostedB18C said:
I'm not saying you're a noob. All I'm trying to get you to understand is to read before doing. As with your unlocked bootloader issue, you probably overlooked that there are 2 ways to restore to stock. One re locks the bootloader and the other doesn't. Read more and don't skim the guide, that's all I'm saying my dude.
Click to expand...
Click to collapse
thats what Ive been trying to find for ages and I've downloaded 4 or 5 different "stock" odin packages which puts me back to the original 4.1.1 I506VRALJB version....
So I'm trying to find the ODIN package that wipes everything (bootloader esp)....... thanks..... and with goo.im having so many issues its really tough finding all the files I need.
....hmmmmmmm so I updated superSU and unchecked a box that "hides" root - but if I accept another OTA i'm sure I'll be stuck with another boot loop until I really flash the unlocked bootloader with the OEM one right?
DO NOT ACCEPT OTAS! Lol. I forgot which thread had the right file. I'll look around and try to find it. Which files from which threads have you tried?
This is where I pointed the last person I helped and it worked for them
http://forum.xda-developers.com/showthread.php?p=41584579
BoostedB18C said:
DO NOT ACCEPT OTAS! Lol. I forgot which thread had the right file. I'll look around and try to find it. Which files from which threads have you tried?
Click to expand...
Click to collapse
lol yea my goal is to be on the latest and greatest OTA but of course im not going to accept an OTA until I'm 100% locked first....
http://forum.xda-developers.com/showthread.php?t=2040264
Tried this one which puts me on the original oem rom that came with the phone w/ no updates....
The only way I was able to get out of the boot loop is use the PIT file and this file root66_VZW_stock_system.tar.md5
http://galaxynote2root.com/galaxy-note-2-root/how-to-root-verizon-galaxy-note-2-sch-i605/
Here is where I Found the "pre-rooted" file... I put that in the bootloader section of ODIN along with the PIT file and this fixed my boot loop problem.
so even tho ODIN mode says "official" and not custom - this is bc I disabled root thru superSU even though its still rooted..
http://d-h.st/Qd4
I think this is the baseline unrooted baseband......trying it out.
enkrypt3d said:
http://galaxynote2root.com/galaxy-note-2-root/how-to-root-verizon-galaxy-note-2-sch-i605/
Here is where I Found the "pre-rooted" file... I put that in the bootloader section of ODIN along with the PIT file and this fixed my boot loop problem.
so even tho ODIN mode says "official" and not custom - this is bc I disabled root thru superSU even though its still rooted..
Click to expand...
Click to collapse
I would advise you to stay away from guides that are not on xda. Just because there is more knowledge here.
BoostedB18C said:
I would advise you to stay away from guides that are not on xda. Just because there is more knowledge here.
Click to expand...
Click to collapse
Just showing where I Got the file to recover from boot loop.... that guide isnt even for the right phone model...... read back as I added a bunch to my last post.
Trying to flash with the below file in the "phone" section so that it wipes the entire phone but it fails.... I've also removed superSU by using the option to "unroot" inside SuperSU..... whats going on? I have the PIT File in place, "phone bootloader update" checked or unchecked doesn't seem to matter..... and same for Phone EFS Clear......
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CI605_I605VRLJB_I605VRALJB_CL414933_HWID04_HW-Rev0406_low_ship_user.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Added!!
<ID:0/004> Removed!!
<ID:0/004> Added!!
<ID:0/004> Removed!!
<ID:0/004> Added!!
<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> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response from boot-loader
<ID:0/004> cache.img
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response from boot-loader
<ID:0/004> hidden.img
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response from boot-loader
<ID:0/004> modem.bin
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response from boot-loader
<ID:0/004> param.bin
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response from boot-loader
<ID:0/004> recovery.img
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response from boot-loader
<ID:0/004> sboot.bin
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response from boot-loader
<ID:0/004> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
http://forum.xda-developers.com/showthread.php?t=2120726
This is the exact problem I have.....
From what I am understanding you can't write boot on Vrall4. So you would need to be on vraljb before being able to re lock the bootloader. I'm my head it makes sense but not sure how you need to go about it. I only looked at it real quick and I can't look into it right now. I'll check with you later and see what you have figured out. So post anything that you come across.
finally resolved it by erasing nand and flashing root66, then factory reset, then flashing one without the sboot.bin......
it took so many times - i dont think ive ever flashed this phone this many times before....... ugh what a pIta.... never rooting this phone again as its so freakin tempermental.
Or just don't unroot it. Problem solved??
Sent from my SCH-I605 using Tapatalk 2
enkrypt3d said:
finally resolved it by erasing nand and flashing root66, then factory reset, then flashing one without the sboot.bin......
it took so many times - i dont think ive ever flashed this phone this many times before....... ugh what a pIta.... never rooting this phone again as its so freakin tempermental.
Click to expand...
Click to collapse
please instruct me on all steps u took... where did u put the files and what u checked and what not.. i have the same exact problem except it gets stuck at Logo... i cannot go into recovery as well.
i have tried all the same files as u and all fail except root66 but it stays stuck on logo
as far as I can remember, take odin, put the pit file in the pit location in odin:
http://d-h.st/mKu
Then flash with root66...
http://androidfilehost.com/?fid=9390210501348163619
then see if u can get into stock recovery and do a factory reset and then go back into odin mode.... then tick nand erase and then use the alternate restore and put it in the phone section of the ODIN app and flash it....... of course this doesnt have the sboot but this was the only way i was able to get it back up....
if u are able to get the phone back up with root66, then stop there..... erasing the nand and not doing it right can brick it. i spent 2 days fixing mine and I must have tried flashing the phone at least 25 times... when I got root66 up and running I went into SuperSU app and went into settings and theres an option to remove or hide root. this may have helped. right now im finally on the latest OTA and it says official (not custom rom) in odin mode and in the about phone section. Hope this helps.
keep the back cover off the phone bc you'll be pulling the battery out if it gets stuck... good luck. FYI I always use the PIT file and that always seemed to have helped.
enkrypt3d said:
as far as I can remember, take odin, put the pit file in the pit location in odin:
http://d-h.st/mKu
Then flash with root66...
http://androidfilehost.com/?fid=9390210501348163619
then see if u can get into stock recovery and do a factory reset and then go back into odin mode.... then tick nand erase and then use the alternate restore and put it in the phone section of the ODIN app and flash it....... of course this doesnt have the sboot but this was the only way i was able to get it back up....
if u are able to get the phone back up with root66, then stop there..... erasing the nand and not doing it right can brick it. i spent 2 days fixing mine and I must have tried flashing the phone at least 25 times... when I got root66 up and running I went into SuperSU app and went into settings and theres an option to remove or hide root. this may have helped. right now im finally on the latest OTA and it says official (not custom rom) in odin mode and in the about phone section. Hope this helps.
keep the back cover off the phone bc you'll be pulling the battery out if it gets stuck... good luck. FYI I always use the PIT file and that always seemed to have helped.
Click to expand...
Click to collapse
ah man... i can get PASS! on root66 but it still gets stuck at logo.. anything else i flash will just fail at boot.img nand write... think im just f*ck'ed dude..
my thread is here if anything... thank you !
http://forum.xda-developers.com/showthread.php?t=2296441
Best bet is to erase nand and try flashing with the alternative rom and pit file at the same time...tomorrow I'll post the files I used as most mirrors are slow as balls..
Sent from my SCH-I605 using xda app-developers app