Related
Was stuck on dl01 with voodoo, bloatware frozen, rooted, and using launcherpro.
I followed the first link in that sticky: http://forum.xda-developers.com/showthread.php?t=908451
and now my phone wont boot up. when I turn it on I see the samsung logo and then it goes through this:
--Wiping data--
Formatting FOTA...
Formatting DATA...
Data Wipe failed.
Formatting Cache
Formatting DBDATA
Wipe_Data Failed.
Click to expand...
Click to collapse
then it will go back to the samsung logo and go around in circles again.
everything went fine with odin. This is what the little message window said:
<ID:0/005> Added!!
<ID:0/005> Removed!!
<ID:0/005> Added!!
<ID:0/005> Removed!!
<ID:0/005> Added!!
<ID:0/005> Removed!!
<ID:0/004> Added!!
<ID:0/004> Removed!!
<ID:0/004> Added!!
<ID:0/004> Removed!!
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> Enter CS for MD5..
<ID:0/005> Check MD5.. Do not unplug the cable..
<ID:0/005> Please wait..
<ID:0/005> Removed!!
<ID:0/005> Removed!!
<ID:0/005> Removed!!
<ID:0/005> Checking MD5 finished Sucessfully..
<ID:0/005> Leave CS..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> cache.rfs
<ID:0/005> dbdata.rfs
<ID:0/005> factoryfs.rfs
<ID:0/005> modem.bin
<ID:0/005> recovery.bin
<ID:0/005> zImage
<ID:0/005> Removed!!
<ID:0/005> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
Click to expand...
Click to collapse
I have no idea what went wrong but now i have no phone and this sux big time.
Dont panic this has happened to me.
Try this link:
http://forum.xda-developers.com/showthread.php?t=1026746
And use the method in SECTION 2: HEIMDALL
Rockstar52 said:
Dont panic this has happened to me.
Try this link:
http://forum.xda-developers.com/showthread.php?t=1026746
And use the method in SECTION 2: HEIMDALL
Click to expand...
Click to collapse
will take a look at that in a minute thanx.
but what the hell went wrong? was it something to do with voodoo?? none of the steps said to disable it or anything....
Yes you must disable VooDo before you do anything. Voodo is a real pain if your a new to flashing.
Rockstar52 said:
Yes you must disable VooDo before you do anything. Voodo is a real pain if your a new to flashing.
Click to expand...
Click to collapse
okay this tutorial is not working. I went strait to heimdall step two and I get two problems.
1) in step 3 it says "Now drop the usb drop down box and you will find an option for SAMSUNG android composite ADB device, or Samsung composite usb driver..."
I dont get that, I get "unknown device" My computer is 6 years old and i have always had problems with the usb recognizing my fascinate. It always says some type of problem and when i troubleshoot it says no drivers are installed even though i have installed them.
2)when I select the unknown device and hit install drivers i get installing drivers failed.
If you can get odin to work again use atlas_v2.2.pit to format back to rfs file-system. Use the PIT button in odin.
fupamobile said:
okay this tutorial is not working. I went strait to heimdall step two and I get two problems.
1) in step 3 it says "Now drop the usb drop down box and you will find an option for SAMSUNG android composite ADB device, or Samsung composite usb driver..."
I dont get that, I get "unknown device" My computer is 6 years old and i have always had problems with the usb recognizing my fascinate. It always says some type of problem and when i troubleshoot it says no drivers are installed even though i have installed them.
2)when I select the unknown device and hit install drivers i get installing drivers failed.
Click to expand...
Click to collapse
Definitely try to Odin the Pit 2.2 that DMT suggested.
Here's a link to a giude that should help get you back to stock as it isn't as intimidating for some as the un-bricking one: http://forum.xda-developers.com/showthread.php?t=1124391
And if that fails might I suggest trying it on a more up to date PC, maybe your issues have come from that if your pc never recognized the phone properly.
Nnneeeedd heellp nowwww!!!!!!!!!!
Go to the development stickies and go to the 2 one...how to go from
Cm7 to anything else...that's not the official title but it its something like that. The links for the eb01. tar, the atlas 2.2pit and newer odin versions are all in the first post.
I use odin 1.7..which version are you on? I'm sure if you use odin 1.7 or newer and put the 2.2 atlas pit file in the pit section with repartition checked and put the official vzw eb01 .tar in the pda section and run it..that will get your phone back in stock unrooted bloated form but at least your phone will work and then you can go and flash what you like..but I would try a different odin version and the eb01 with the pit file and you will get your phone back
Sent from my SCH-I500 using XDA App
Are you willing to just go back to stock or start all over again?
Put the phone in Download mode
Remove battery
plug usb into PC
plug usb into phone [battery still out]
push [and hold] volume button down
Should see yellow triangle [once you see this you can let go off the volume]
Use Odin then to flash the Stock image to your phone.
Link to ODIN v1.3 http://www.mediafire.com/download.php?r5izui8a3trpo85
Download the ED01 stock rom
Put it into the PDA section of Odin and flash and Boom Back to stock!
Stock ED01 http://www.multiupload.com/6ET46L1ATD
Nothing will be deleted off of your sd card
xwhofarted said:
Are you willing to just go back to stock or start all over again?
Put the phone in Download mode
Remove battery
plug usb into PC
plug usb into phone [battery still out]
push [and hold] volume button down
Should see yellow triangle [once you see this you can let go off the volume]
Use Odin then to flash the Stock image to your phone.
Link to ODIN v1.3 http://www.mediafire.com/download.php?r5izui8a3trpo85
Download the ED01 stock rom
Put it into the PDA section of Odin and flash and Boom Back to stock!
Stock ED01 http://www.multiupload.com/6ET46L1ATD
Nothing will be deleted off of your sd card
Click to expand...
Click to collapse
Well I got the drivers installed and i was on to step 5 but heimdall.exe wont open.
I think I will just do it this way i guess. this is all because of stupid voodoo
Voodoo used to be a p.i.t.a but it really isn't that hard now with the newer cwm supporting both voodoo and non voodoo, the steps myself and the person who posted above me are describing direction for odin..not heimdall.I don't know much about heimdall or how to use it but you can get your phone back and working using odin
Use the link in junkboy0's reply..follow the directions in the first post.
fupamobile said:
Well I got the drivers installed and i was on to step 5 but heimdall.exe wont open.
I think I will just do it this way i guess. this is all because of stupid voodoo
Click to expand...
Click to collapse
Sent from my SCH-I500 using XDA App
efan450 said:
Go to the development stickies and go to the 2 one...how to go from
Cm7 to anything else...that's not the official title but it its something like that. The links for the eb01. tar, the atlas 2.2pit and newer odin versions are all in the first post.
I use odin 1.7..which version are you on? I'm sure if you use odin 1.7 or newer and put the 2.2 atlas pit file in the pit section with repartition checked and put the official vzw eb01 .tar in the pda section and run it..that will get your phone back in stock unrooted bloated form but at least your phone will work and then you can go and flash what you like..but I would try a different odin version and the eb01 with the pit file and you will get your phone back
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
what should i do about voodoo though?
i am going to do this as two of you have suggested:http://forum.xda-developers.com/showthread.php?t=1124391
but i dunno about voodoo. just ignore it for now? It addresses it in that post but i dont undestand what it is saying
using Odin and the stock image it will over write the voodoo
I have never used the heimdall way. I have been stuck in boot loops many times and ODIN has always saved the day!
As long as you can get to Download mode your phone can be fixed
fupamobile said:
what should i do about voodoo though?
i am going to do this as two of you have suggested:http://forum.xda-developers.com/showthread.php?t=1124391
but i dunno about voodoo. just ignore it for now? It addresses it in that post but i dont undestand what it is saying
Click to expand...
Click to collapse
Yup ignore voodoo for now...when you use the atlas2.2 file in the pit section and the eb01.tar in the pda section...if repartition isn't checked make sure you check it...run it and it will bring you to stock with voodoo removed and then you can flash whatever you wanted from there...if you get stuck,p.m.me and I'll send you files with complete directions but it would have to wait till I get home from work tonight..don't panic we'll get you up and running again!
Get the newest odin, eb01. tar, and atlas 2.2pit file, and I would grab
One of the newer recovery.tar files too so when your back to stock you can flash a working recovery if you want to flash some rom after all is fixed....i recommend the 3-30 fix all recovery, but just make sure you get a tar file so you can odin it after your phone is fixed.
Sent from my SCH-I500 using XDA App
xwhofarted said:
using Odin and the stock image it will over write the voodoo
I have never used the heimdall way. I have been stuck in boot loops many times and ODIN has always saved the day!
As long as you can get to Download mode your phone can be fixed
Click to expand...
Click to collapse
interesting.
in the q/a section there is a sticky on how to go stock. not only does it not tell me how to address voodoo(why i am here) but it tells me to go to DL09 and them OTA to eb01.
the method you guys are posting seems much more logical. it sends me strait to froyo and doesnt brick my phone because it just overwrites voodoo. correct?
once voodoo is "overwritten", is it gone off my phone? if not, should i address it at all after this tutorial? froyo is downloading right now
xwhofarted said:
using Odin and the stock image it will over write the voodoo
I have never used the heimdall way. I have been stuck in boot loops many times and ODIN has always saved the day!
As long as you can get to Download mode your phone can be fixed
Click to expand...
Click to collapse
I concur...soft bricked, boot looped, many many times and never used heimdall either
Sent from my SCH-I500 using XDA App
fupamobile said:
interesting.
in the q/a section there is a sticky on how to go stock. not only does it not tell me how to address voodoo(why i am here) but it tells me to go to DL09 and them OTA to eb01.
the method you guys are posting seems much more logical. it sends me strait to froyo and doesnt brick my phone because it just overwrites voodoo. correct?
once voodoo is "overwritten", is it gone off my phone? if not, should i address it at all after this tutorial? froyo is downloading right now
Click to expand...
Click to collapse
Correct voodoo will be gone but you can just flash another voodoo kernel later and you can flash voodoo over voodoo just not voodoo to non voodoo with out removing it
Sent from my SCH-I500 using XDA App
efan450 said:
Yup ignore voodoo for now...when you use the atlas2.2 file in the pit section and the eb01.tar in the pda section...if repartition isn't checked make sure you check it...run it and it will bring you to stock with voodoo removed and then you can flash whatever you wanted from there...if you get stuck,p.m.me and I'll send you files with complete directions but it would have to wait till I get home from work tonight..don't panic we'll get you up and running again!
Get the newest odin, eb01. tar, and atlas 2.2pit file, and I would grab
One of the newer recovery.tar files too so when your back to stock you can flash a working recovery if you want to flash some rom after all is fixed....i recommend the 3-30 fix all recovery, but just make sure you get a tar file so you can odin it after your phone is fixed.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
okay. I am just following what that tutorial says to do. I dont even know what a working recovery is. I never even had a rom on this thing. I have realized I am in way over my head here and have spent too much time dealing with my phone.
really all i want is to be up to date, have root, debinged/bloat, launcherpro so i dont have to use stupid touchwiz. thats basically all i need. maybe in the future i might get other stuff. but for now i think it will suit me best to just rely on verizon/samsung to keep my phone up to date and then just re root everytime. seems much simpler and safer
fupamobile said:
okay. I am just following what that tutorial says to do. I dont even know what a working recovery is. I never even had a rom on this thing. I have realized I am in way over my head here and have spent too much time dealing with my phone.
really all i want is to be up to date, have root, debinged/bloat, launcherpro so i dont have to use stupid touchwiz. thats basically all i need. maybe in the future i might get other stuff. but for now i think it will suit me best to just rely on verizon/samsung to keep my phone up to date and then just re root everytime. seems much simpler and safer
Click to expand...
Click to collapse
Recovery..clock work mod...or cwm is the recovery program you will use to install custom rom, kernels, or zip files...I will send you a p.m.later with files, info, and instructions and you can read over it and decide if you want to do it now or wait till you're a lil more familiar with the process..but for now odin the pit atlas 2.2 file and eb01 and you will be stock and be able to use launcher pro.
Sent from my SCH-I500 using XDA App
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'm trying to flash stock firmware with Odin. It's stuck on factoryfs.img.
Here is what shows up on the screen:
<ID:0/009> Added!!
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> factoryfs.img
I am using the one click downloader from this link. Please tell me what I need to do to fix this. Thanks.
I found that sometimes its all in the technique of how you plug things in and the usb used. Try different usb cords. Try different usb ports. and then for some reason what worked for me is have odin open plug usb into computer, and then put the phone into download mode and finally connect the microUSB into the phone. Hope it works, hit back if it does or doesnt
[email protected] said:
I'm trying to flash stock firmware with Odin. It's stuck on factoryfs.img.
Here is what shows up on the screen:
<ID:0/009> Added!!
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> factoryfs.img
I am using the one click downloader from this link. Please tell me what I need to do to fix this. Thanks.
Click to expand...
Click to collapse
How long did you let it go for on the factoryfs.img?
It could be as simple as changing usb cable. Use the one that came with the phone. Or changing to a different usb port, preferably one directly connected to the mother board.
Beyond that, we would need to know more information about your situation. Why are you flashing stock firmware, from what condition of the phone, etc. Give as much detail as possible.
creepyncrawly said:
It could be as simple as changing usb cable. Use the one that came with the phone. Or changing to a different usb port, preferably one directly connected to the mother board.
Beyond that, we would need to know more information about your situation. Why are you flashing stock firmware, from what condition of the phone, etc. Give as much detail as possible.
Click to expand...
Click to collapse
I have tried it on all usb ports that I have on my laptop.
OK here's exactly what I did to my phone:
I downloaded the ICS version for i777 from sammobile and flashed it using ODIN. Then, I installed Siyah kernel using mobile odin. I then installed triangle away to get rid of the flash counter. I used my phone like this for a couple of days. Then today, I installed the AOKP rom. To do this, I first back up using CWM, then i booted in CWM recovery mode, did a complete wipe, deteled cache and dalvik, and then I proceeded to install the rom. Installation worked fine and everything, however the data wasn't working on my phone. So I then tried to enter the T-Mobile APN settings (it's an unlocked phone), however I couldn't save the APN settings. Tried to enter them multiple times and selected save from the menu, but it just wouldn't show up on the APN list. So, I tried to restore to my back up in CWM restore, however that failed. Admittedly, I should have asked for help at this point. However I was frustrated, so I decided to just use Odin again to flash the ICS stock firmware that I got from sammobile. However, it failed and had some error along the lines of completed writing but operation failed? I tried switching to different USB ports and restarted Odin with run as administrator, but kept getting the same error. On one of these numerous tries, I also tried to check the re-partition option just to see if that would change anything (probably not a very smart idea). Anyways, at some point during these numerous attempts, it got to the point where the phone wouldn't boot up and asked me to connect to samsung kies to restore. I tried that but my phone won't connect with kies. I then found your one-click odin stock firmware thing on these boards and used that. Tried multiple times at different ports, but it keeps getting stuck at factoryfs.img. I have left it in there for a good 30 minutes in this current try (4th). Also, this may or may not be relevant, the flash counter keeps going up.
PS: This is my first android phone so I'm pretty new at this, but I did try to read up a lot before trying anything (well, except for when I randomly checked re-partition that one time).
Edit: Sorry I should have made this clear - even though the phone will not boot, I can still get into download mode.
OK. It seems there is always AOKP in the mix somewhere, and I don't know that firmware at all well, but it seems to make some changes that are hard to fix sometimes.
Can you get into recovery mode at this point? You may still be able to depending on what has happened during the various Odin flashes. Try that and let me know, and if so what recovery do you have?
creepyncrawly said:
OK. It seems there is always AOKP in the mix somewhere, and I don't know that firmware at all well, but it seems to make some changes that are hard to fix sometimes.
Can you get into recovery mode at this point? You may still be able to depending on what has happened during the various Odin flashes. Try that and let me know, and if so what recovery do you have?
Click to expand...
Click to collapse
'
Thank you for the swift response. No, I am unable to get into recovery mode. It goes to a screen that says "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again."
I'm sort of guessing here based on information I've gleaned from various threads. You might try flashing just the siyah ICS kernel in Odin. You can download the tar for siyah 3.4.2 from here. It certainly can't make things worse at this point to try. Let me know.
While I didnt have your issues. I also recently bought an i777, my install went very smooth, everything worked more or less on the first try tried diff cords, ports and then finally it was the plug sequence that did it for me. Upon flashing AOKP, I immediately unlocked the phone via that galaxy S unlocker, I followed the steps to the T and my IMEI is still the same. I am also on tmobile, with working edge. I still have the pesky triangle, but I havent read too many good things about the triangle remover.
Perhaps you have a bad rom download? It might sound silly but flashing AOKP for a friend when I redownloaded the rom, everything worked fine. What the guy above me said, try recovery mode instead and then go from there. Good news is that your phone doesnt sound borked
creepyncrawly said:
I'm sort of guessing here based on information I've gleaned from various threads. You might try flashing just the siyah ICS kernel in Odin. You can download the tar for siyah 3.4.2 from here. It certainly can't make things worse at this point to try. Let me know.
Click to expand...
Click to collapse
Ok I tried this, and it completed successfully in Odin, however, the phone now gets stuck on the "Samsung Galaxy SII GT-I9100" screen.
But will it boot into recovery now?
creepyncrawly said:
But will it boot into recovery now?
Click to expand...
Click to collapse
No, it still does not boot into recovery.
OT: How long will I have the 5 min restriction on posting?
Also, I don't know if this is relevant, but when I try to turn off the phone, it turns off but then it'll automatically start back up within a few seconds and then get stuck on the samsung galaxy sII screen
Don't know. 10 posts?
I don't think the flash with partition checked would have caused a problem. You didn't put a path to a pit file in the pit slot did you?
The full UCKH7 firmware package should flash. Is that what you downloaded from sam firmware? You might try downloading that from the Download Repository (link in my signature) and try flashing it once again. It must be the UCKH7 stock though, because that one has the secondary bootloader and param.lfs file. The UCLE5 does not.
creepyncrawly said:
Don't know. 10 posts?
I don't think the flash with partition checked would have caused a problem. You didn't put a path to a pit file in the pit slot did you?
The full UCKH7 firmware package should flash. Is that what you downloaded from sam firmware? You might try downloading that from the Download Repository (link in my signature) and try flashing it once again. It must be the UCKH7 stock though, because that one has the secondary bootloader and param.lfs file. The UCLE5 does not.
Click to expand...
Click to collapse
No, I didn't put a pith file. Also just to make sure I'm flashing the right file, is it the one called "I777 UCKH7 stock param.lfs"?
Flash the firmware from the section titled I777UCKH7-CL503881 Stock Binaries.
You can use either the one-click downloadedr or the tar.md5 file.
Let me know if that flashes.
And also, is that the same file you downloaded from samfirmware? Because that is where this file came from. Or did you download the UCLE5 firmware from samfirmware?
creepyncrawly said:
Flash the firmware from the section titled I777UCKH7-CL503881 Stock Binaries.
You can use either the one-click downloadedr or the tar.md5 file.
Let me know if that flashes.
And also, is that the same file you downloaded from samfirmware? Because that is where this file came from. Or did you download the UCLE5 firmware from samfirmware?
Click to expand...
Click to collapse
It was the UCLE5 file. I'll try this one.
Now it gets stuck on Sbl.bin. Here is what it says:
<OSM> I777UCKH7-REV02-home-low-CL503881.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> Sbl.bin
I'll let it run for another 5 or so minutes, then I'll try different ports and see what happens.
[email protected] said:
Now it gets stuck on Sbl.bin. Here is what it says:
<OSM> I777UCKH7-REV02-home-low-CL503881.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> Sbl.bin
I'll let it run for another 5 or so minutes, then I'll try different ports and see what happens.
Click to expand...
Click to collapse
OK I tried it on all the USB ports that I have on my laptop. No luck. Still getting stuck at Sbl.bin. Any more ideas?
Yes. If it were my phone, I would start by flashing the param.lfs by itself and see if that allows it to boot, or makes progress.
If not, then I would flash the sbl.bin by itself and see if that allows it to boot, or makes progress.
If still not, then I would try the full UCKH7 package with the PIT file, and repartition checked.
You can get all the files from the Download Repository. Please bear in mind that there is risk in everything you are doing, (and have been doing.)
So I flashed my T959 with a T959V kernel and now I'm stuck in the booting screen. I could get into download mode. What can I do to get my phone working again?
What version of android are you running? The easiest thing to do would be to flash a kernel via Odin, but I can't really suggest one unless I know what exactly you're running.
Sent from my SGH-T959
I updated my phone from 2.1 to 2.2 via kies mini, then I rooted the phone with SuperOneClick. Finally I flashed this kernel http://forum.xda-developers.com/showthread.php?t=1080871 with SGS kernal flasher (something like that) from the play store. Now I'm stuck on the boot screen whenever I boot.
I see. Well, let's try something.
Have you ever used Odin before? If not, you can download it here:
ODIN
You're also going to need to download this kernel:
Overstock Kernel
Now, once those two files are downloaded, you're going to wanna' run the Odin executable I linked above. More than likely, there's going to be a check mark checked for Re-partition, F. Time Reset, and/or Auto Reboot. Although regardless of what's checked, you're going to want to uncheck everything. Once everything is unchecked, your going to want to click PDA and select the OverStock kernel you previously downloaded. Put your phone into download mode, an ID:COM should light up yellow, then hit Start. Once it has finished, giving you the message PASS!, you're going to want to pull your phone from the computer and remove the battery pack. Then, put the battery back in and finally, reboot your phone.
Sorry if my steps are confusing. I'm not by my computer, so I'm going off of memory. Please, don't hesitate to ask any questions. I'll be glad to help or explain anything.
Sent from my SGH-T959
I followed your instruction and once I click start, it failed. Here's the log
<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> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> zImage
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
Now my phone has phone to computer icon with a yellow caution sign. Have I successfully hard bricked my phone?
edit: I have a jig if that would help.
I tried to flash the kernel through Odin again and it worked. Now my phone is up and running, but I can't seems to download any apps from the play store. I wipe all the cache in recovery and try to start things fresh, but the play store just wouldn't let me download any apps. It just starts the download, pause and cancel my download as if nothing happened. I tried to install again and the entire play store crashed. At this point how can I download apps and flash custom ROMs?
I think this might help you if you soft brick your device One-Click UnBrick
Regarding the play store issue check this
Hope this will help
tc
After a night of flashing, I returned to JFD and started all over. Everything is running great now. I didn't realize SGS was such an amazing phone until I flashed a custom rom yesterday. Sleeping at 5 am yesterday was well worth it. Thanks for all your help.
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