[Q] Phone is dead - Sprint Samsung Galaxy S III

rooted my S3 (4.1) and installed clockwork mod.
created a backup of my S3 using clockwork.
installed Jellybomb ROM.
recovered S3 backup using clockwork.
infinite boot....
I can still get into download mode and clockwork recovery but I'm unable to restore my S3.
Odin ( versions 1.83 - 3.09) fails all attempts to install roms, and clockwork is no longer able to read my ext sd card.
Now I have no way of installing anything to the phone.
Any advice?

westnine9 said:
rooted my S3 (4.1) and installed clockwork mod.
created a backup of my S3 using clockwork.
installed Jellybomb ROM.
recovered S3 backup using clockwork.
infinite boot....
I can still get into download mode and clockwork recovery but I'm unable to restore my S3.
Odin ( versions 1.83 - 3.09) fails all attempts to install roms, and clockwork is no longer able to read my ext sd card.
Now I have no way of installing anything to the phone.
Any advice?
Click to expand...
Click to collapse
have you tried using adb push?
look at these steps http://android-revolution-hd.blogspot.com/2013/12/how-to-copy-rom-zip.html
skip 9,10,11,12 because you don't need to create any folders and you are using 4.1.2
I hope that helps

jdelano said:
have you tried using adb push?
look at these steps...
skip 9,10,11,12 because you don't need to create any folders and you are using 4.1.2
I hope that helps
Click to expand...
Click to collapse
Thank you.
At least now I can push roms to the device.
It seems that no matter what rom I attempt to install I get these lines in clockwork:
-- Installing: /sdcard/rom.zp
Finding update package...
Opening update package...
Installing update...
Installation aborted.
I've tried 2 custom roms and Samsungs 4.1 stock Jellybean rom.
Same lines every time.
Am I missing something?

Jessooca said:
Is Odin failing in the middle of flashing a tar file or what is going on exactly.
Did your phone ever reboot or get stuck at the Samsung logo prior to this semi bricked issue?
Any details you can provide will help us better to help you.
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
Odin begins to write and then fails a few seconds afterwards.
After a failed write of any rom I get the boot error screen with the yellow triangle on the device.
Yes, It did get stuck at the Samsung screen prior to my clockwork mod no longer reading my ext sd card.

Jessooca said:
Try a usb port in the back of your computer and a different cable. I got one from my dollar tree and it's great.
Are you sure you aren't trying to flash an older tar file? Once you update to the newest update you have to flash the newest SPRINT SPH-L710 stock tar, I'm sure you know this already. Perhaps you've inadvertently downloaded the wrong tar!?
I have checked marked everything including wiping the efs in Odin 1.87 and it fixed a data issue someone had
This has to be fixable with Odin. I'd flash flash and try flashing again until Odin finishes without an error.
** also since you're on 4.1 why not try the latest tar file, not md5 and Odin that then root with CF Auto Root?
Sent from my SPH-L710 using xda app-developers app
---------- Post added at 04:15 PM ---------- Previous post was at 03:52 PM ----------
One other thing...
Don't use twrp or cwm, use Philz recovery. Twrp works but on some roms it's flaky
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
Thank you for the quick response.
I have tried different cables and usb ports (front and rear of PC case).
I'm also positive that I have the latest stock .tar from Samsung.
Also, I've tried checking "phone EFS clear" in Odin 1.87 as you've mentioned. (I've tried writing roms with all available versions of Odin as well. Versions 1.83 - 3.09 get me the same failed results)
lol, as far as flashing, flashing, and flashing until it works? I've tried. I've become quite desperate.
Here are the lines I get in Odin if it's of any help.
<ID:0/007> Added!!
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> sbl2.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> sbl3.mbn
<ID:0/007> aboot.mbn
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Jessooca said:
** also since you're on 4.1 why not try the latest tar file, not md5 and Odin that then root with CF Auto Root?
Click to expand...
Click to collapse
I'm not clear as to what you mean by this.
Would you please explain this to me?

westnine9 said:
Thank you.
At least now I can push roms to the device.
It seems that no matter what rom I attempt to install I get these lines in clockwork:
-- Installing: /sdcard/rom.zp
Finding update package...
Opening update package...
Installing update...
Installation aborted.
I've tried 2 custom roms and Samsungs 4.1 stock Jellybean rom.
Same lines every time.
Am I missing something?
Click to expand...
Click to collapse
Is there a status # given when it fails?

jdelano said:
Is there a status # given when it fails?
Click to expand...
Click to collapse
No status codes were displayed
Jessooca said:
Download Odin 1.87
Use a download manager to download the latest stock 4.3 TAR file
Put your phone into download mode.
Don't check repartition in Odin and don't use a pit file. Just the tar file in the pda slot.
Let me know where things go wrong this time
Sent from my SPH-L710 using xda app-developers app
---------- Post added at 05:14 PM ---------- Previous post was at 04:59 PM ----------
... here's a link to the tar file
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
Aha!
That little package did the trick!
My S3 is now up and running 4.1
Hmm, I still can't put my finger on what was causing the write fails with the standalone Odin and 4.1 rom.
..Maybe I didn't have the latest Samsung rom like I thought?
In any case that's irrelevant now.
Thank you very much Jessooca. :laugh:

Related

[GUIDE] Rooting the Samsung Captivate Glide i927/i927r

Finally, the Captivate Glide is successfully rooted.
Credit:
lambgx02 who provided the Carrier IQ free kernel (by Rogers) and the insecure kernel and the Rogers rooted ROM!!!
ardatdat who provided the rooted ROM and the overclocked kernel
samsfirware.com that provided the firmware without which nothing would have been possible
myself, crazy tester who bricked his device
Very easy steps:
If you are on Rogers, no need to flash the kernel, it is already CarrierIQ free​
Download Odin 1.85
Download the CarrierIQ FREE kernel (zip file) or the overClocked version of it.
Download the rooted ROM (AT&T based ROM)
or the Rogers rooted based rom (Unzip with WinRAR not 7zip)
Unzip the file and keep the .tar, that the file you are going to push to your device
Put your phone in Download Mode:
Turn off the phone
Press volume UP and keeping the button pressed, press the power button
a screen should ask you if you wanna continue - press volume up to confirm
Launch Odin
in PDA, select the first kernel downloaded (tar file you just unzipped)
DON'T SELECTor UNSELECT ANYTHING ELSE
Press the start button
Wait for your phone to reboot
This kernel will remove any traces of CarrierIQ, and you are now free from AT&T Spyware
IF AND ONLY IF this flashing fails, try the exact same steps with the insecure kernel
Reboot your device into download mode again (steps above)
Flash the rooted rom
Go to the market and make sure you have the latest version of superuser
go to superuser, check you have "su" updated
You're now rooted!
For any other questions, watch this first PLEASE:
There is already a thread for this... reporting for locking.
Sent from my SGH-I897 using xda premium
b-eock said:
There is already a thread for this... reporting for locking.
Sent from my SGH-I897 using xda premium
Click to expand...
Click to collapse
The other thread was about trying to find root access, this is hopefully a thread on the procedure to have it in your phone
b-eock said:
There is already a thread for this... reporting for locking.
Sent from my SGH-I897 using xda premium
Click to expand...
Click to collapse
I don't think it needs locked, they need their own subforum. We can put up with them here till they get it, they need a space to develop, too.
And congrats on getting root into the kernel rom!
Is this msg normal after I start? I also get a big red box at the top right which reads FAIL.
<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> SGH-I927RUXKJ5_STOCK_ROOTED.tar
<ID:0/005> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
clockwork58 said:
Is this msg normal after I start? I also get a big red box at the top right which reads FAIL.
<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> SGH-I927RUXKJ5_STOCK_ROOTED.tar
<ID:0/005> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Nope, you should get PASS in green color if successfully flashed. Try to open odin as administrator (right click, run as administrator) and make sure your device was detected properly by windows & Odin while it is in DL mode.
Sorry my guide was not complete, the kernel is not rooted, it is a CarrierIQ free kernel but the rom is rooted.
As soon as we have the kernel rooted, I will post it here.
I know that they need their space, I already told others to leave it alone, I was just trying to keep it from being cluttered. I am sorry guys good luck!!!
Sent from my SGH-I897 using xda premium
IlluminatedOne said:
Nope, you should get PASS in green color if successfully flashed. Try to open odin as administrator (right click, run as administrator) and make sure your device was detected properly by windows & Odin while it is in DL mode.
Click to expand...
Click to collapse
I still get the same error and now my phone won't even boot.
It says to use Kies to recover but even that won't recognize the device even though windows does pick up the drivers.
I can get to either the Kies screen asking to restore a bad image or the Custom rom screen and that's it.
HELP Pls.
Hey, wait a minute.. I provided the rooted rom..
But in all honesty, that's the easy part. Those nagging Samsung, the testers risking their devices, and of course, the OP who finally found the stock firmware images deserve the credit. Not to mention sammobile.com / samfirmware.com.
clockwork58 said:
I still get the same error and now my phone won't even boot.
It says to use Kies to recover but even that won't recognize the device even though windows does pick up the drivers.
I can get to either the Kies screen asking to restore a bad image or the Custom rom screen and that's it.
HELP Pls.
Click to expand...
Click to collapse
Do you have rogers or ATT ?
lambgx02 said:
Hey, wait a minute.. I provided the rooted rom..
But in all honesty, that's the easy part. Those nagging Samsung, the testers risking their devices, and of course, the OP who finally found the stock firmware images deserve the credit. Not to mention sammobile.com / samfirmware.com.
Click to expand...
Click to collapse
The rooted rom here is not yours but the one from ardatdat
But does not really matter, you both did a great job!!
I'm on Rogers. I'm using the lambgx02's Tar file.
I also just got my phone to recover following the other thread
http://forum.xda-developers.com/showthread.php?t=1357369
about going into 3e recovery mode and doing a reboot and it started fine.
I think the first time I tried, I didn't have kies installed with all the proper drivers.
Should I give it another go?
Update: Tried again, same Fail error. Maybe I'll try using my computer at work instead of my older home laptop.
Recovered again using 3e.
clockwork58 said:
I'm on Rogers. I'm using the lambgx02's Tar file.
I also just got my phone to recover following the other thread
http://forum.xda-developers.com/showthread.php?t=1357369
about going into 3e recovery mode and doing a reboot and it started fine.
I think the first time I tried, I didn't have kies installed with all the proper drivers.
Should I give it another go?
Update: Tried again, same Fail error. Maybe I'll try using my computer at work instead of my older home laptop.
Recovered again using 3e.
Click to expand...
Click to collapse
Let us know I tried twice to make sure everything was ok and it is.
if you are on Rogers you dont need to flash the kernel it is already CarrierIQ free!
CarpeNoctem said:
The rooted rom here is not yours but the one from ardatdat
But does not really matter, you both did a great job!!
Click to expand...
Click to collapse
Oh, I'm sorry ardatdat and Carpe! I didn't even notice!
Must have been a close race!
lambgx02 said:
Oh, I'm sorry ardatdat and Carpe! I didn't even notice!
Must have been a close race!
Click to expand...
Click to collapse
I promise you no race. Just happy to be rooted and have my device back to life thanks to you
Sent from my GT-P1000 using xda premium
Maybe tonight I'll see what I can do with the kernel linked in the OP.
Note I do not own a Glide so I won't be able to test.
Sent from my SAMSUNG-SGH-I897 using XDA App
I hate to ask a newb question, but thats what I am when it comes to things like this. Will rooting using this method factory reset the phone as well?
shatteredzman said:
I hate to ask a newb question, but thats what I am when it comes to things like this. Will rooting using this method factory reset the phone as well?
Click to expand...
Click to collapse
Nope; it only flashes /system. Your data partition stays in-tact.
Of course, any time you mess with the device internals, there's a risk, so I'd highly recommend backing up anyway.
We can have an ezroot kernel if we either set the /system partition. As rw (read/write) instead of read only or set in the default.prop the following: ro.secure=0 & persist.service.adb.enable=1, then there's root in "adb shell" to remount the system partition as rw.
Is it a boot.img or initram packed zImage we're dealing with?

odin stuck on modem.bin

odin get all the way to modem.bin and then it gets stuck. any ideas on how to get it to progress tried different roms and i'm using a non samsung usb cable.
I'd try a new USB port and cable or make sure your USB is clean just typical precautions. Try resdownloading or reinstalling your drivers. Kinda obvious things .... sorry
Ignore wait for someone smarter I doubt these help
Sent from my OG Epic
Btw what are trying to do Odin back to stock?
Sent from my OG Epic
Biggoron said:
Btw what are trying to do Odin back to stock?
Sent from my OG Epic
Click to expand...
Click to collapse
a stock eco5 and a pre rooted eh17 rom
Hmm ec05 sometimes things take a while are you sure your download is complete its like 290mbs and are you doing it properly only auto reboot checked. If you are then id say give it like 5-8 minutes if it hangs then try another usb port and keep on it hopefully it will kick it in there. Just to make sure your using the victory pit file and have the pda checked and the ec05.tar in the file right?
Sent from my OG Epic
Biggoron said:
Hmm ec05 sometimes things take a while are you sure your download is complete its like 290mbs and are you doing it properly only auto reboot checked. If you are then id say give it like 5-8 minutes if it hangs then try another usb port and keep on it hopefully it will kick it in there. Just to make sure your using the victory pit file and have the pda checked and the ec05.tar in the file right?
Sent from my OG Epic
Click to expand...
Click to collapse
yeah the tar file is in the pda section like it needs to be
Hmm no idea sorry man id ask a dev like marcusant or someone..... maybe they could tell you what the deal is with a log or something....
Sent from my OG Epic
Biggoron said:
Hmm no idea sorry man id ask a dev like marcusant or someone..... maybe they could tell you what the deal is with a log or something....
Sent from my OG Epic
Click to expand...
Click to collapse
i can't figure out whats wrong with it
pjames said:
i can't figure out whats wrong with it
Click to expand...
Click to collapse
It still may be a bad download. Why not come up to EI22? Odin this:
http://forum.xda-developers.com/showthread.php?t=1340385
Then Odin the EC05 modem tar seperately here:
http://forum.xda-developers.com/showthread.php?t=1123103
And then flash the EC05toEI22 modem zip.
---------- Post added at 09:59 AM ---------- Previous post was at 09:58 AM ----------
Also try it with the battery and sd card out. Odin works better that way. Use the computer as the power source. Connect it then put it into download mode.
kennyglass123 said:
It still may be a bad download. Why not come up to EI22? Odin this:
http://forum.xda-developers.com/showthread.php?t=1340385
Then Odin the EC05 modem tar seperately here:
http://forum.xda-developers.com/showthread.php?t=1123103
And then flash the EC05toEI22 modem zip.
---------- Post added at 09:59 AM ---------- Previous post was at 09:58 AM ----------
Also try it with the battery and sd card out. Odin works better that way. Use the computer as the power source. Connect it then put it into download mode.
Click to expand...
Click to collapse
i tried it. still stuck on the modem.bin. no change. im think imma give up lol
Man thats a pain i remember when i first tried
To root my phone took me three days to figure out my cable was bad . Everytime i got a different color screen but jere i am now with a blackberry cable >_<
Sent from my OG Epic
Try Heimdall.
Sent from my SPH-D700 using XDA App
This happens to me once in a while. Just switch usb ports. ALSO AVOID USING THE EXTENDED USB PORTS!. Those are the ones in the front off the PC case or on the side. Use the ones directly from the motherboards, meaning use the ones in the back off the pc case. Restart your PC also. If those 2 fail, buy a new usb cord. Also, ive had odin stay at modem forever but pulling the battery out and booting the phone and all is ok. Weird. But happens.
Sent from my SPH-D700 using Tapatalk
kennyglass123 said:
Try Heimdall.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
i downloaded it but it was way too confusing lol
Right click odin. Run as administrator.
Sent from my SPH-D700 using xda premium
pjames said:
i downloaded it but it was way too confusing lol
Click to expand...
Click to collapse
Look at Post 2 in this thread for Heimdall instructions. It is much better once you get the hang of it. And you can remove the modem.bin and flash everything else:
http://forum.xda-developers.com/showthread.php?t=1052813
kennyglass123 said:
Look at Post 2 in this thread for Heimdall instructions. It is much better once you get the hang of it. And you can remove the modem.bin and flash everything else:
http://forum.xda-developers.com/showthread.php?t=1052813
Click to expand...
Click to collapse
okay heimdall worked. but i can't flash the modem. i tried to flash it with heimdall but it crashes and with odin i get this:
<ID:0/011> Added!!
<ID:0/011> Odin v.3 engine (ID:11)..
<ID:0/011> File analysis..
<ID:0/011> SetupConnection..
<ID:0/011> Initialzation..
<ID:0/011> Get PIT for mapping..
<ID:0/011> Firmware update start..
<ID:0/011> modem.bin
<ID:0/011> NAND Write Start!!
and it sticks on that. so close but so far lol
pjames said:
okay heimdall worked. but i can't flash the modem. i tried to flash it with heimdall but it crashes and with odin i get this:
<ID:0/011> Added!!
<ID:0/011> Odin v.3 engine (ID:11)..
<ID:0/011> File analysis..
<ID:0/011> SetupConnection..
<ID:0/011> Initialzation..
<ID:0/011> Get PIT for mapping..
<ID:0/011> Firmware update start..
<ID:0/011> modem.bin
<ID:0/011> NAND Write Start!!
and it sticks on that. so close but so far lol
Click to expand...
Click to collapse
So now we know for sure there is somethng up with the modem on your phone. Try any other modem from this thread. Just pull the modem.bin out and use Heimdall to just flash that:
http://forum.xda-developers.com/showthread.php?t=1123103
Try to get the EC05 modem in then use the EC05toEI22 modem update script in CWM.
kennyglass123 said:
So now we know for sure there is somethng up with the modem on your phone. Try any other modem from this thread. Just pull the modem.bin out and use Heimdall to just flash that:
http://forum.xda-developers.com/showthread.php?t=1123103
Try to get the EC05 modem in then use the EC05toEI22 modem update script in CWM.
Click to expand...
Click to collapse
that didnt work either. im still stuck in airplane mode and base band is unknown and hardware version is unknown as well
pjames said:
that didnt work either. im still stuck in airplane mode and base band is unknown and hardware version is unknown as well
Click to expand...
Click to collapse
Now we know your phone is messed up. Try this to clear out the NVRAM in your modem to reset and reactivate your phone:
http://forum.xda-developers.com/showthread.php?t=1226074

[Q] "secure check fail" when trying to restore stock image w/ Odin (AT&T)

[Q] "secure check fail" when trying to restore stock image w/ Odin (AT&T)
I bought an AT&T Galaxy S III today, and was pretty unsuccessful in rooting it -- mostly due to the fact that every time I tried to boot into "recovery", I would only get a flash of it before a blank screen. I tried several guides and, until a little while ago, I was at least still able to boot normally and use the phone. Now, not only can I not get into recovery mode, if I try to boot normally I only get a flash of the "Samsung" screen before it goes black and nothing else happens. The only mode that I can boot into is Download mode.
At this point, I just want to get back to a working stock ROM. I followed a guide from "galaxys3root"'s website (I can't post links because I'm a new user) because it was the only one that linked to what looked like a full stock image instead of some 10 mb file, but I got an error in Download mode that said, "SECURE CHECK FAIL: aboot." I've only been able to find one other thread that features that error, and it seems to be archived.
Am I screwed, or is there any way I can get back to a working ROM? Has anyone else worked through this same problem?
update: I've tried now with several different images (including a "May 2012" one and a "July 2012" one), and it's the same error message for each:
a red "secure check fail: aboot" on the phone, and a similar error in Odin:
Code:
<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.
Any ideas?
What are you pressing to get into recovery? If you're trying to root your phone...it needs to be in download mode not recovery.
Sent from my SAMSUNG-SGH-I747 using xda premium
defnow said:
What are you pressing to get into recovery?
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
Volume up + Home + Power. I've watched youtube videos and made sure I was doing exactly the same thing, but all I get is a flash of "Samsung" with some blue text in the top left corner that doesn't last long enough to read before it just goes black.
http://forum.xda-developers.com/showthread.php?t=1739426
This is where you go to get rooted. Download the file...boot phone into download mode and use Odin to flash the stock rooted injected Rom.
Can you get into download mode?
Sent from my SAMSUNG-SGH-I747 using xda premium
Use the qualcomm toolkit in the dev stickies mskip ...but it sounds like u need to read more i see a bricked phone in ur future
Sent from my SAMSUNG-SGH-I747 using xda premium
---------- Post added at 01:56 AM ---------- Previous post was at 01:54 AM ----------
j4bora said:
I bought an AT&T Galaxy S III today, and was pretty unsuccessful in rooting it -- mostly due to the fact that every time I tried to boot into "recovery", I would only get a flash of it before a blank screen. I tried several guides and, until a little while ago, I was at least still able to boot normally and use the phone. Now, not only can I not get into recovery mode, if I try to boot normally I only get a flash of the "Samsung" screen before it goes black and nothing else happens. The only mode that I can boot into is Download mode.
At this point, I just want to get back to a working stock ROM. I followed a guide from "galaxys3root"'s website (I can't post links because I'm a new user) because it was the only one that linked to what looked like a full stock image instead of some 10 mb file, but I got an error in Download mode that said, "SECURE CHECK FAIL: aboot." I've only been able to find one other thread that features that error, and it seems to be archived.
Am I screwed, or is there any way I can get back to a working ROM? Has anyone else worked through this same problem?
Click to expand...
Click to collapse
U dont need to flash if u dont know how! Read and read if u still cant do it then its not for u...y u wanna root for..
Sent from my SAMSUNG-SGH-I747 using xda premium
defnow said:
http://forum.xda-developers.com/showthread.php?t=1739426
This is where you go to get rooted. Download the file...boot phone into download mode and use Odin to flash the stock rooted injected Rom.
Can you get into download mode?
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
Yes, Download mode is the only mode I can get to. The problem is that with every ROM I use with Odin, I get the same error about "aboot.mbn" (Including the one in your link.)
j4bora said:
Yes, Download mode is the only mode I can get to. The problem is that with every ROM I use with Odin, I get the same error about "aboot.mbn" (Including the one in your link.)
Click to expand...
Click to collapse
What Odin version are you using? I helped another user who was having the same probelm...so he switched from the newer 3.0.7 Odin to 3.0.4 and it worked.
Just to be sure, you're unzipping the file to get the stock tar file correct?
Sent from my SAMSUNG-SGH-I747 using xda premium
defnow said:
What Odin version are you using? I helped another user who was having the same probelm...so he switched from the newer 3.0.7 Odin to 3.0.4 and it worked.
Just to be sure, you're unzipping the file to get the stock tar file correct?
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
Yes, I'm unzipping the files. I've tried 3.07, 3.04, and 1.85, all with the same result.
If it means anything, I'm doing this all through a virtual machine -- I'm really running Linux, with a Windows 7 client in Virtualbox. USB connections to the virtual machine seem to be normal so I'm not sure if it would contribute anything, but who knows. I'll probably try all this again tomorrow on an actual Windows machine.
1.85 is the one I've been using with no problems but yeah...try a window machine.
Sent from my SAMSUNG-SGH-I747 using xda premium
Lookup Flash/NonTrip under Android DEV section of i747.
The best method and very reliable.
Going forward - use only xda for all your Android needs!
So I tried it on a real Windows machine -- everything went very smoothly this time, and now I have a working phone again
Thank you everyone for your suggestions.
Same problem
Hi im from mexico and i had a i747m from telcel and downloaded the firmware from at&t but when flashed with odin i got same error "aboot" so i downloaded a firmware from same region i747 and it flashed OK
Asking for help
thekoff said:
Hi im from mexico and i had a i747m from telcel and downloaded the firmware from at&t but when flashed with odin i got same error "aboot" so i downloaded a firmware from same region i747 and it flashed OK
Click to expand...
Click to collapse
Buddy, i am from mexico too, and i am always getting the same error. Can you share the files and tell us wich version of odin did you use to flash the firmware?
I would like to remove all the telcel crap in my phone .-.
Hope you can help me.
HELP!
I have the same problem, i dont know what do i have to do? someone can help me or someone have the answer!! I HAVE GALAXY S4 AT&T I337 i hadn't NB1!
THANKS
leo.alexh7 said:
I have the same problem, i dont know what do i have to do? someone can help me or someone have the answer!! I HAVE GALAXY S4 AT&T I337 i hadn't NB1!
THANKS
Click to expand...
Click to collapse
Exactly which bootloader and modem is on your phone? Do you have a working ROM on your phone?
audit13 said:
Exactly which bootloader and modem is on your phone? Do you have a working ROM on your phone?
Click to expand...
Click to collapse
thank you very much for answer me, im dummy and principiant you will know, i don't know exactly that bootloader i have, and 3 days ago in "about device" i saw build "xxxxxxxxNB1" i guess that this is my modem. I had stock rom 4.4.2 at&t with safestrap and super su running, but i installed project x extended rom and really running these custom rom based touch wiz, but i did a stupid action, >>> restore data of my old stock rom for not lost my data (i know, after i read that did it with titanium backup), but my phone only reboot, so i wipe data factory and now my telephone stays on bootlop of samsung galaxy s4. Sorry i believe in xda developers!! HELP ME!
You have the s3 with safestrap? Not sure how that is possible. I thought the ATT Note 3 had safestrap. Your posts also mentions an s4.
Just to confirm, you have the s3 i747 from ATT?
turn off reactivatin lock
j4bora said:
update: I've tried now with several different images (including a "May 2012" one and a "July 2012" one), and it's the same error message for each:
a red "secure check fail: aboot" on the phone, and a similar error in Odin:
Code:
<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.
Any ideas?
Click to expand...
Click to collapse
turn off reactivation lock in settings.
The aboot.mbn file will not flash if you are trying to downgrade the bootloader.

Galaxy S2 Freezes on Start and Won't Flash Anything

I recently acquired an Epic 4G Touch that wouldn't boot into the stock ROM. I thought "Awesome! The ROM must be corrupted. I'll just Odin it back to stock and have a new SG2." Well, I tried Odining it back to stock. I tried the Gingerbread EL29 stock tar image and it hung on the Sbl.bin. I thought maybe my download was just corrupt but after trying 2 other GB odin images it still wouldn't flash. Then I tried flashing CWM recovery through odin and that hung at NAND Write Start. I've switched cables, USB slots and computers. I'm at a loss as to why this is happening. I would really like to get this phone running so I can upgrade my SGS1.
Edit- Just to clarify, I never tried to flash anything through CWM. I tried flashing a kernel that had CWM through Odin.
I put the ROM into the PDA slot. Here's what happened in Odin:
<ID:0/011> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> HOME_SPH-D710_CL839620_user.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/011> Odin v.3 engine (ID:11)..
<ID:0/011> File analysis..
<ID:0/011> SetupConnection..
<ID:0/011> Initialzation..
<ID:0/011> Get PIT for mapping..
<ID:0/011> Firmware update start..
<ID:0/011> boot.bin
<ID:0/011> NAND Write Start!!
<ID:0/011> Sbl.bin
<ID:0/011> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Also tried flashing a PIT file,
<ID:0/011> Added!!
<ID:0/011> Odin v.3 engine (ID:11)..
<ID:0/011> File analysis..
<ID:0/011> SetupConnection..
<ID:0/011> Initialzation..
<ID:0/011> Set PIT file..
<ID:0/011> DO NOT TURN OFF TARGET!!
<ID:0/011> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I wish I would get some sort of response...
Since you can still get into download mode, try this thread.
http://forum.xda-developers.com/showthread.php?p=30996944
:edit: And I failed to mention that this seems to be the 4th thread in the past few weeks and the previous posters didn't fair well.
I hope the best for you.
Sent from my SPH-D710 using Xparent ICS Tapatalk 2
MoHoGalore said:
Since you can still get into download mode, try this thread.
http://forum.xda-developers.com/showthread.php?p=30996944
:edit: And I failed to mention that this seems to be the 4th thread in the past few weeks and the previous posters didn't fair well.
I hope the best for you.
Sent from my SPH-D710 using Xparent ICS Tapatalk 2
Click to expand...
Click to collapse
Thank you for the response. I cannot get into my recovery and my phone will not flash anything in Odin without some sort of error. I think it hosed. He mentioned sending it off for a jtag repair? What exactly is that?
xDecapitator said:
Thank you for the response. I cannot get into my recovery and my phone will not flash anything in Odin without some sort of error. I think it hosed. He mentioned sending it off for a jtag repair? What exactly is that?
Click to expand...
Click to collapse
This is very confusing... How are you trying to flash with CWM if you can't get into recovery mode?
What exactly is happening with the device when you try to power it on?
What happens when you try to go into download mode using Vol down+power?
What happens when you try to get to recovery using vol up+power?
graydiggy said:
This is very confusing... How are you trying to flash with CWM if you can't get into recovery mode?
What exactly is happening with the device when you try to power it on?
What happens when you try to go into download mode using Vol down+power?
What happens when you try to get to recovery using vol up+power?
Click to expand...
Click to collapse
Agreed.
Op - You're trying to write to the phone and, my guess is, you're making a bad situation worse since your getting partial writes. Especially that first screen where pit was mapped and partial flash took, such as boot.
Dont know where crawrj is, but try reaching out to Garwynn. He knows A LOT.
Sent from my SPH-D710 using Xparent ICS Tapatalk 2
MoHoGalore said:
Agreed.
Op - You're trying to write to the phone and, my guess is, you're making a bad situation worse since your getting partial writes. Especially that first screen where pit was mapped and partial flash took, such as boot.
Dont know where crawrj is, but try reaching out to Garwynn. He knows A LOT.
Sent from my SPH-D710 using Xparent ICS Tapatalk 2
Click to expand...
Click to collapse
What? When did I say I was flashing through CWM? I've never even been able to boot to CWM. I said I was trying to flash CWM through download mode which failed. When I try to boot, it sticks at the Samsung Galaxy S2 kernel load screen. When I try to boot into recovery it sticks at the Samsung Galaxy S2 kernel load screen.
xDecapitator said:
What? When did I say I was flashing through CWM? I've never even been able to boot to CWM. I said I was trying to flash CWM through download mode which failed. When I try to boot, it sticks at the Samsung Galaxy S2 kernel load screen. When I try to boot into recovery it sticks at the Samsung Galaxy S2 kernel load screen.
Click to expand...
Click to collapse
Sorry. I misread the OP.
Ok. Try this to get into Recovery
Press and hold the vol up+power button until the splash screen shows up
After the splash shows release the power button and then continue to hold the vol up button. It should take you right to recovery.
graydiggy said:
Sorry. I misread the OP.
Ok. Try this to get into Recovery
Press and hold the vol up+power button until the splash screen shows up
After the splash shows release the power button and then continue to hold the vol up button. It should take you right to recovery.
Click to expand...
Click to collapse
I've done this atleast 20 times (21 now after this post) and it just sticks at the Samsung Galaxy S2 screen. I'm sure I screwed it even further by trying to flash CWM recovery. When I first got it, it booted into the recovery screen but wouldn't actually fully load into recovery. I would just get the Android character but no text. These are the weirdest issues I've ever had with an Android device.
xDecapitator said:
I've done this atleast 20 times (21 now after this post) and it just sticks at the Samsung Galaxy S2 screen. I'm sure I screwed it even further by trying to flash CWM recovery. When I first got it, it booted into the recovery screen but wouldn't actually fully load into recovery. I would just get the Android character but no text. These are the weirdest issues I've ever had with an Android device.
Click to expand...
Click to collapse
That is very strange...
Do you have an external SD card installed? If so, remove it and try to boot into recovery again.
graydiggy said:
That is very strange...
Do you have an external SD card installed? If so, remove it and try to boot into recovery again.
Click to expand...
Click to collapse
Still no luck :|
It fails every time it trys to flash files to the NAND memory. Does this mean the internal storage is screwed?
xDecapitator said:
It fails every time it trys to flash files to the NAND memory. Does this mean the internal storage is screwed?
Click to expand...
Click to collapse
That is possible. You can try to call Sprint and tell them you/a friend was trying to update to ICS and rebooted and it wont boot fully. Act dumb and see if they will replace it. Since it won't boot to anything at all, there is really no way for them to tell. Just say that you bought it from said friend. It is worth a shot. I have done it before with AT&T when I screwed up a Captivate doing a hardware mod.
I just told them that I bought it online and tried to update it but after the update, it wouldn't power on. They let me replace it.
---------- Post added at 09:54 PM ---------- Previous post was at 09:52 PM ----------
Either that or try J-Tag. But I don't know if that will fix it.
That and it's 50 bucks and a time to wait..
Sent from my SPH-D710 using Xparent ICS Tapatalk 2
graydiggy said:
That is possible. You can try to call Sprint and tell them you/a friend was trying to update to ICS and rebooted and it wont boot fully. Act dumb and see if they will replace it. Since it won't boot to anything at all, there is really no way for them to tell. Just say that you bought it from said friend. It is worth a shot. I have done it before with AT&T when I screwed up a Captivate doing a hardware mod.
I just told them that I bought it online and tried to update it but after the update, it wouldn't power on. They let me replace it.
---------- Post added at 09:54 PM ---------- Previous post was at 09:52 PM ----------
Either that or try J-Tag. But I don't know if that will fix it.
Click to expand...
Click to collapse
OK I will definetly try that, thanks. If they don't replace it, I will just sell it for parts and keep using my Epic 4G. Thanks for all of your help
Wait oh wait I have a few questions myself lol what odin are you using? Did you try any one clicks? Did you try removing the sd card and then odin? Did you try to leave battery out all night then try odin again with no sdcard?
Sent from my SPH-D710 using xda premium
I tried 2 different versions of Odin;1.x and 3.x. I used multiple one clicks. I pulled the sd card before flashing. I had to buy a battery for it when I got it and the previous owner had kept the battery out of it for at least a month. I really appreciate all answers but I really feel like I've tried everything :|
Sent from my SPH-D700 using Tapatalk 2
It is possible using a pit file would help. The pit file from when this phone came out would be best. Then run a gb rom in odin along with the pit. If you find the pit link it here before you use it. Wouldn't want more problems.
sent from MY BAD A$$ ET4G
patrao_n said:
It is possible using a pit file would help. The pit file from when this phone came out would be best. Then run a gb rom in odin along with the pit. If you find the pit link it here before you use it. Wouldn't want more problems.
sent from MY BAD A$$ ET4G
Click to expand...
Click to collapse
One Click restores are built with the proper pit of 9-16-11. But it sounds like he's already tried multiple builds.
Flashing each component isn't a bad suggestion but with using the pit, I wouldn't necessarily use just a rom, I'd use a tar since it would contain everything needed to restore the bootloader (boot, Sbl, param, recovery..)
Or try flashing an built bootloader to see if he could get back into recovery alone. There are a few already made in RWilco's Repo..

I need help with .pit file, thanks!

Anyone out there that can help with the Note 2 SGH-T889 .pit file? Thanks in advance, I'd greatly appreciate it.
Edited: I need the file, a download link would be appreciate it.
http://forum.xda-developers.com/showthread.php?p=48398405
Sent from my SGH-T889 using xda app-developers app
Is this to be used only with heimdall or with a PC and Odin as well? Thanks!
Both heimdall and odin, why do you need this file for ?
Sent from my SGH-T889 using xda app-developers app
Well, I mistakenly flashed a file that was supposed to fix the wifi when in the leaked 4.3 roms a while back, but I flashed the 7100 one, and messed everything up. I was still able to get to them rom and all but eventually was just able to get to the custom recovery and thats it, now it just stays at the logo screen. I think I messed up the efs and some other things
I can still connect to a PC thru Odin and it recognizes the phone just fine, I can get to the custom recovery too and flash roms but it never passes the splash screen of that rom.
You can try emergency recovery through Kies or flash stock ROM and then flash flash whatever you want.
Sent from my SGH-T889 using xda app-developers app
I have flashed countless original Stock Roms, with every file they come with, and still hangs
I think it might have to do with the internal sd partion, Im hoping the .pit file fixes that? Not sure.
slick4mitch said:
I have flashed countless original Stock Roms, with every file they come with, and still hangs
I think it might have to do with the internal sd partion, Im hoping the .pit file fixes that? Not sure.
Click to expand...
Click to collapse
Have you tried a factory reset? Sometimes even after Odin I've had to factory reset. By the way since u flashed the wrong bootloader have you flashed the full stock from Sam mobile?
Sent from my GT-N7105 using xda app-developers app
kintwofan said:
Have you tried a factory reset? Sometimes even after Odin I've had to factory reset. By the way since u flashed the wrong bootloader have you flashed the full stock from Sam mobile?
Sent from my GT-N7105 using xda app-developers app
Click to expand...
Click to collapse
Is not that I flashed a wrong bootloader, but yes, I have flashed our 4.3 bootloaders, even our 4.1 bootloader and it always hangs. I did a factory reset, I clean the internal sdcard, nothing, still hangs.
I know my EFS is messed up, it says it when I try to mount in the recovery, it even says it in the regular recovery, but it was loading the rom before with a messed up EFS.
I now have a Note 3 but I have taken upon myself to revive my Note 2
I can't get the .pit file to work usin Odin, it always fails, also I believe my system partition is not mounting at all, nor does the preload partition.
I second ciphercodes Kies recovery idea.
Hastily spouted for your befuddlement
Coug76 said:
I second ciphercodes Kies recovery idea.
Hastily spouted for your befuddlement
Click to expand...
Click to collapse
I tried it but it won't connect to Kies, but the phones does connects to the PC and its recognized by Odin.
slick4mitch said:
I tried it but it won't connect to Kies, but the phones does connects to the PC and its recognized by Odin.
Click to expand...
Click to collapse
And, just to be clear, that was following the emergency recovery process? There is the kies update, apart from the emergency recovery process. I hate to give up on a device...
Hastily spouted for your befuddlement
It just wont connect to Kies. Remember, I can't load up a rom, so Im trying to connect using download mode. It says connecting and stays like that, I think it might be dead
slick4mitch said:
It just wont connect to Kies. Remember, I can't load up a rom, so Im trying to connect using download mode. It says connecting and stays like that, I think it might be dead
Click to expand...
Click to collapse
Have you made any progress on this? I have a T-Mobile Note 2 also needs reviving.....I can only get it into download mode, can't get it into recovery mode......
I keep getting this error:
<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.img
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Please share what you know. thanks

Categories

Resources