Am I gonna do some damage selecting re-partition in Odin? My tab updated fine to 3.1, I was installing apps and my Tab went into a bootloop. Well I've Odined back to stock several times, but this time after it completes, it bootloops and never boots up.
Would that solve my problem? Or make matters worse?
Try to wipe data from recovery before doing a reparation.
Sent from my GT-I9100 using XDA Premium App
clubtech said:
Try to wipe data from recovery before doing a reparation.
Sent from my GT-I9100 using XDA Premium App
Click to expand...
Click to collapse
Thanks for the reply. It would shut off when i issued the adb command to reboot into recovery, but the 10th time i tried it, it finally booted into recovery. Problem aborted
To the both of you in this thread, LovellKid and Clubtech
Were you to repartition would you use a .pit file, and if so which one, 512 or 813 (Tried without repartion get write error, tried with repartion but without .pit file and get "error at line 1455")
My Google I/O not recognised by any software (adb, fastbbot, kies) can't even get it to bootloop now (which it was doing before) so only alternative is complete crush the thing and try to start again......the old sledgehammer to crack a walnut theory
Seems that Odin is the only thing that will talk to the tab, but gives a write error at end of upload process, can't think of any tricks to get out of this except 100% empty the thing and try to start again
Thanks guys
It seems to me that if Odin can see your device, fastboot should be able to? Have you tried issuing the fastboot -w command?
Sent from my SCH-I500 using XDA App
Related
Here is how I brick my Epic I was looking at some Chinese form to replace libicudata.so with libicudata.so 0126 to sort Chinese contact in pinyin order. After I use root explore I restart my phone it just stuck at the Samsung screen. I was try to going in ClockWorkMod to flash the kernel after numerous try I can't get in ClockWorkMod I can only get in to E2 recovery. Than I put my SD card my computer try to read it and find out all the files in the SD is corrupted.
But my phone still can go to download mode or E2 recovery. Since my SD corrupted my only option is using download mode
ODIN3
I have try to use ODIN3 version 1.0 every time when I try to flash it stop at “param.lfs” and my phone will turn off the screen by itself and I have waited an hour nothing happen. I have try all the different firmware I found on this form and none of them works.
And I try using ODIN3 Version 1.3 when I try to flash after “param.lfs” than tells me write fail.
After trying ten hours on ODIN3 I have give up and search on google I found a flash program call “Heimdall” after flowing instruction to change the drive and modify the flash.bat to have it run than I got and error message “s1_odin_20100512.pit did not match the device” and rebooted my phone and stuck on the Samsung screen. I think the “s1_odin_20100512.pit” is the problem with ODIN3 also.
Please help and any suggestion for me to reflash my Epic 4…..
Sorry for my poor English..
Thank you for reading my post.
If you have the di18 tar file you don't need pit. Try it without. Also try installing drivers and using odin on a different computer. Mine had driver issues before. Especially do this, go into the stock recovery if you still can and wipe data/factory reset, then use odin. Hope this helps.
Sent from my SPH-D700 using XDA App
johnyardavid said:
If you have the di18 tar file you don't need pit. Try it without. Also try installing drivers and using odin on a different computer. Mine had driver issues before. Especially do this, go into the stock recovery if you still can and wipe data/factory reset, then use odin. Hope this helps.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
I have try using 3 different Laptops and PC. no luck at all and I have try wipe data/factory reset also. Thanks
What about a different tar file like di07 or dg27? And then you could just upgrade from there. Also I believe you can use odin to do a complete wipe. Or maybe try flashing just a kernel through odin first and then the system.
Sent from my SPH-D700 using XDA App
Sounds to me like you have a bad downloaded file. Delete the file and re-DL another one. When I use ODIN it works almost instantly assuming you loaded up the proper drivers. If it gets stuck doing something it usually means the file is bad.
Alternatively you could be having power fluctuations, which is why I have a smart ups 1000.
As someone said do you have the proper samsung drivers installed on the pc?
So I bricked my phone. This time couldn't recover. Warranty replaced it, got my replacement the next day. I've never had a problem rooting before, but this time I can't seem to get anything to work. I'm wondering if they sent me a phone with some type of root protection, if that's even possible. Please help, this really sucks. Tried Superoneclick repeatedly, different versions. Univ Androot doesn't support Sammies (at least not ours). Z4Root doesn't work. Tried Oclf and in the recovery menu I get E:signature verification failed Installation aborted. What do I do?
Last resort (well, actually first resort too): flash adrynalyne's clean rom... That has root built in...
of course you need cwm working to do so....
Sent from my SCH-I400 using XDA Premium App
Hmmm
Ok, I have only previously installed CWmod (once rooted) via Rom manager. Now, not having root, I dl'd cwmod_v08 and dropped the recovery and update.zip on my sdcard. I reboot, holding volume up/volume down. I select apply sdcard:update.zip, and I'm still getting a signature verification error, just like I got when I attempted this via OCLF. I read online that it is a problem with Android System Recovery <3e>, and to revert to 2e to remove the signature verification, but I already show 2e. WTF? I'm about to retrieve my hammer and root this piece Thor-style!
Haven't used Odin, but I guess it's time...
First off, lol @ the Thor thing.. haha
Second, yeah it is definitely time... just make sure you are flashing just the adryn_cwm_recovery4 ( something like that) file in the guide in this thread xP
And make sure you use pda, not phone....
If you still can't get it working, just ask here....
Also, before I'm done... i highly suggest not flashing a full dump in Odin.... just saying xP there is a corrupt version out there ( not on purpose)
Sent from my SCH-I400 using XDA Premium App
Ok, I'm using Odin 4.28 and it looks different than all the vid tutorials I'm finding...cwm_recovery_test4_adryn.tar is on my desktop, but when I hit PDA and try to select it (the tar file) it says "Invalid Image Type"...
Newer definitely doesn't always mean better xP i suggest downloading another, older, version...
Sent from my SCH-I400 using XDA Premium App
Ok, DL'd Odin3, it seems to be working better...What did you mean by you recommend not flashing a full dump? Sorry, still learning this stuff...I appreciate the help...
The link is bad for the update.zip file in the *Official* Clockwork Recovery thread. I flashed using odin3 and it seemed to work but when I attempt to apply the update.zip My little android turns into a caution sign-holding android error screen. Don't know if I did something wrong with Odin or if the update.zip files I am able to find online are wrong for loading clockwork with this particular recovery image (the tar is the image, correct? lmao) Help! Please! I'll send you good vibes and spiritual cookies!
Lmao, i love you xP
I would say first trying to push all of the soft keys and see if it pops up then...
That has happened to me before, and I didn't know what was going on either xP
Try that though... If not, then yeah... Your Zip is bad... I'll upload mine
Sent from my SCH-I400 using XDA Premium App
[recovery] clockwork Mod recovery....
Download from that thread... XD
Sent from my SCH-I400 using XDA Premium App
So I just recovered from a softbrick using the Heimdall method. I'm stoked because I'm no longer bricked but I cannot flash anything via Odin now, even after I have re-installed my Samsung USB drivers. It always gets to SetupCS connection or something like that and just stays there. Is there something I'm missing?
What driver is on your system? Is it the fascinate or the nexus s? If you're coming back to some level of stock from a GB rom you might still have the GB (nexus s) drivers. You might have to reload the froyo fascinate drivers for odin to work.
Sent from my SCH-I500 using XDA App
MR H3LLMAN said:
So I just recovered from a softbrick using the Heimdall method. I'm stoked because I'm no longer bricked but I cannot flash anything via Odin now, even after I have re-installed my Samsung USB drivers. It always gets to SetupCS connection or something like that and just stays there. Is there something I'm missing?
Click to expand...
Click to collapse
as long as you get the yellow "com" with a number underneath the box in odin, drivers are not the issue.......try re-downloading the odin package and then flashing it again
kidserious said:
as long as you get the yellow "com" with a number underneath the box in odin, drivers are not the issue.......try re-downloading the odin package and then flashing it again
Click to expand...
Click to collapse
That was my thought as well but its doing it with 3 different Odin packages. This is where I get lost but am I supposed to put the atlas.v2.2 pit in with everything now? I'm at a loss I guess. Phone is functional on ED03 currently but I'm stuck at stock it seems...
Sent from my SCH-I500 using XDA App
MR H3LLMAN said:
That was my thought as well but its doing it with 3 different Odin packages. This is where I get lost but am I supposed to put the atlas.v2.2 pit in with everything now? I'm at a loss I guess. Phone is functional on ED03 currently but I'm stuck at stock it seems...
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
the atlas 2.2 pit file goes in the "PIT" section at the same time as the tar.md5 file goes in the "PDA" section and re-partition checked......when those two files are placed in their respective slots and re-partition is checked, THEN you hit start on odin. If that doesn't work, place this file on the root of your SD card and rename it "update" but without the quotation marks lol: http://forum.xda-developers.com/attachment.php?attachmentid=556632&d=1301538910 Once you do that, boot in the stock blue recovery using the 3 finger method and select "apply SDcard/update.zip" and let me know what happens
Many thanks to you sir. I'm at work currently but ill try this out as soon as I get home.
Sent from my SCH-I500 using XDA App
By the way... what file is that? I'm just curious
kidserious said:
the atlas 2.2 pit file goes in the "PIT" section at the same time as the tar.md5 file goes in the "PDA" section and re-partition checked......when those two files are placed in their respective slots and re-partition is checked, THEN you hit start on odin. If that doesn't work, place this file on the root of your SD card and rename it "update" but without the quotation marks lol: http://forum.xda-developers.com/attachment.php?attachmentid=556632&d=1301538910 Once you do that, boot in the stock blue recovery using the 3 finger method and select "apply SDcard/update.zip" and let me know what happens
Click to expand...
Click to collapse
Alright so I just tried adding the PIT, repartition checked, and added my ODIN package, but still had the same problem. About to install the CWM All file you gave me and try that out.
*edit* Well something just happened. My SD card just got corrupted and I cant even format it now. What the hell is going on?!
*edit 2* OK so the SD card issue fixed itself. Just had to hit format a billion times. I'm now running an OTA update to my phone from Verizon as I had to go all the way back to DI09.
*edit 3* I'm now sitting on ED04 fully stock but away from my computer. I will try again once I get home later on tonight. Just out of curiousity... has anyone else other than kidserious and the other guy had this problem or have experience in dealing with it?
So checking in again. I am still freezing at "SetupConnection..." in Odin. No luck at all with flashing the CWM ALL file as "update". I'm completely out of options at this point. Help?
MR H3LLMAN said:
So checking in again. I am still freezing at "SetupConnection..." in Odin. No luck at all with flashing the CWM ALL file as "update". I'm completely out of options at this point. Help?
Click to expand...
Click to collapse
Let me rack my brain and think........I will get back to you.
RESOLVED
Alright so I finally figured out my own way around this. It was actually fairly simple and I'm a bit ashamed I didn't think to try this earlier.
Hopefully this will be of assistance for any future issues. Thanks Kidserious for your help.
*edit* So I just found some instructions for uninstalling the Heimdall driver from your phone. I'm booting up after a fresh flash of DI01 and hopefully this will work. I'm guessing that even though I'm installing the samsung usb drivers back to my computer, they arn't reaching my phone, and this may be the issue I've been facing. *pauses for a bit to test theory* Yep. That was all it was. Sorry for taking up so much room on here... just FYI to everyone though. If you soft brick and recover via Heimdall you HAVE TO UNINSTALL THE HEIMDALL DRIVER OR NOTHING WILL WORK.
FML. So it didnt work as I had planed. After I flashed my edify rom I samsung bootlooped. And Odin still isnt working for me.
I'm giving up for tonight. Functioning on DI01 stock ): at least it works...
Alright so I'm fairly certain I've narrowed it down to one fix but I seem not to be able to fix it. I need to install the samsunflg husband drover back to my phone and uninstall the heimdall driver. I've tried it twice and or hasn't worked either time
Sent from my SCH-I500 using XDA App
---actually resolved----
Sorry for spamming this thread everyone, even though I've really been the only person posting in it anyways.
I have found my fix. So I was never able to fully uninstall the Heimdall drivers so Odin wouldn't recognize my phone and would hang at "Initalization."
So I took a weird strategy and actually purposely soft bricked my phone. Scary to do but the outcome was well worth it. Here is what I did.
1.) Puropsely soft bricked phone
2.) Put it in to download mode
3.) Went to device manager
4.) Contrary from Heimdall Uninstall instructions phone will now show up under the general usb devices areas. Find this area, expand, and right click on Samsung Composite USB Device.
5.) Go through the options of manually picking the usb driver you want to use.
6.) Install chosen standard samsung USB driver. You may get many options in the list but pick the Digitally Certified one.
7.) I didnt unplug the phone after I flashed the new driver so open up Odin and flash your DI01 Stock Recovery with Atlas v2.2 PIT and Repartition checked.
8.) Once finished phone will be on DI09 fully bloated stock and should work with Odin for any further flashes.
*edit* It appears as if you need to flash the samsung driver to phone evrytime you want to flash something via Odin.
Hi I was flashing an EC09 ROM full package and odin got stuck flashing the modem, After about 30min I pulled my phone and booted it up and found that i had no modem so i also had no network connectivity. I have tried flashing everything else in Hemidall and i can flash everything except the modem.:crying: I want to know if you guys had any Idea about how i can fix this because I have tried everything and i have no idea what to do. Any help appreciated:laugh:
JackMcD007 said:
Hi I was flashing an EC09 ROM full package and odin got stuck flashing the modem, After about 30min I pulled my phone and booted it up and found that i had no modem so i also had no network connectivity. I have tried flashing everything else in Hemidall and i can flash everything except the modem.:crying: I want to know if you guys had any Idea about how i can fix this because I have tried everything and i have no idea what to do. Any help appreciated:laugh:
Click to expand...
Click to collapse
Just try flashing via ODIN again. Mine would get stuck sometimes and I would just unplug my phone, exit Odin, plug the phone back in and start the flash again..
Did you wipe system, data, cache,delvik, all that good stuff, before you flashed?
Sent from my XT912 using xda app-developers app
Check the md5 on the file, reflash, or just flash the modem in heimdall
Sent from my ADR6425LVW using Tapatalk 2
Thanks but Problem Persists
killjoy1179 said:
Just try flashing via ODIN again. Mine would get stuck sometimes and I would just unplug my phone, exit Odin, plug the phone back in and start the flash again..
Did you wipe system, data, cache,delvik, all that good stuff, before you flashed?
Sent from my XT912 using xda app-developers app
Click to expand...
Click to collapse
Thanks killjoy for responding, yes I did wipe everything and i have also tried flashing it in odin again. i have flashed in odin about 4 times already and every time it just hangs on modem.
JackMcD007 said:
Thanks killjoy for responding, yes I did wipe everything and i have also tried flashing it in odin again. i have flashed in odin about 4 times already and every time it just hangs on modem.
Click to expand...
Click to collapse
Have you tried redownloading the ROM? You may also want to try extracting the modem from the full 07 build, and flashing it in heimdall.
Sent from my jellied up mROM v1.3
JackMcD007 said:
Thanks killjoy for responding, yes I did wipe everything and i have also tried flashing it in odin again. i have flashed in odin about 4 times already and every time it just hangs on modem.
Click to expand...
Click to collapse
Yes, try redownloading the rom..also what were you on before you tried flashing ec09?
Sent from my XT912 using xda app-developers app
Thanks for the help, Moving on!
Hi guys tried flashing just the modem in heimdall and it did not work btw i was on EC07 prior to flashing. Anyway i went to verizon and used my upgrade to get a Gnexus:laugh:!
Thanks guys for all the help. I will still check back as my continuum was a trusty little phone and the devs here were super cool.
Bye
ok, so I am not a noob on rooting and such, but this one has me stumped. Have the i337 on mdl baseband. Wanted to return it to stock. I tried to Odin (v3.09) the factory tar from the samsung site, i got a failure, then it went to recovery mode saying to connect kies. I have tried kies 2.6 and 3.0, neither recognize the device. I have tried redownloading samsung firmware thinking it was corrupted and mk2 firmwares in odin, neither worked, they go immediately to fail when i try to execute Odin. I can get into download mode or the kies recovery mode, not sure what to do since it will not take odin. Any ideas?
aawshads said:
ok, so I am not a noob on rooting and such, but this one has me stumped. Have the i337 on mdl baseband. Wanted to return it to stock. I tried to Odin (v3.09) the factory tar from the samsung site, i got a failure, then it went to recovery mode saying to connect kies. I have tried kies 2.6 and 3.0, neither recognize the device. I have tried redownloading samsung firmware thinking it was corrupted and mk2 firmwares in odin, neither worked, they go immediately to fail when i try to execute Odin. I can get into download mode or the kies recovery mode, not sure what to do since it will not take odin. Any ideas?
Click to expand...
Click to collapse
1. Kies and Recovery mode aren't same thing. Kies never will recognize your device being in Stock Recovery Mode. Don't mix things.
2. Find the error now is difficult coz maybe you update your bootloader with the MK2 firmware (that's android 4.3 no android 4.2.2).
3. Get me the errors or one screenshot that appears in ODIN when you try to flash the MK2 firmware pls.
I'll see what I can do, it happens so fast I don't think anything updates, and it shows me no errors, just fail
Sent from my SM-T320 using XDA Free mobile app
aawshads said:
I'll see what I can do, it happens so fast I don't think anything updates, and it shows me no errors, just fail
Sent from my SM-T320 using XDA Free mobile app
Click to expand...
Click to collapse
Maybe Kies was in your task bar when you tried to flash through ODIN?
Not the first but maybe the last ones, what does that do?
Sent from my SM-T320 using XDA Free mobile app
aawshads said:
Not the first but maybe the last ones, what does that do?
Sent from my SM-T320 using XDA Free mobile app
Click to expand...
Click to collapse
Close completely Kies before run ODIN and try again to flash the old bootloader. Tell me how works
Joku1981 said:
Close completely Kies before run ODIN and try again to flash the old bootloader. Tell me how works
Click to expand...
Click to collapse
ok, ran it, failed again, hereare the screenshots with the complete message portion.
aawshads said:
ok, ran it, failed again, hereare the screenshots with the complete message portion.
Click to expand...
Click to collapse
1. Try other version of ODIN. I recommend you the latest one -> HERE
2. And pls.... MK2 isn't firmware for your device, it's for i337M. Don't mix things. Flash MDL again if you had that baseband and show me what errors you will have in ODIN. Good luck
Still failed. Let me know what you see. thanks
Bump, anyone see what I is wrong?
Sent from my SM-T320 using XDA Free mobile app
aawshads said:
Bump, anyone see what I is wrong?
Sent from my SM-T320 using XDA Free mobile app
Click to expand...
Click to collapse
Are you sure you're on the mdl bootloader?
Sent from my Nexus 5 using XDA Free mobile app
Pit file
I see youre trying to flash the mk2 file but you dont have the pit file for the repartition head over here and download the mk2 pit file and then rerun it I also see that you have auto reboot checked, uncheck the auto reboot and then once iit finishes flashing and say reset unpluget you're device and pull the battery then put it back in and go into stock recovery by holding volume up power and home all at the same time and wipe data factory reset and cache partition http://d-h.st/5gz
Thanks, but that did not work either. I have never had a problem I couldn't odin out of, but I have tried everything I can think of and still nothing will work. I just want to sell the phone so I even tried the nb1 which should install no matter what bootloader I am on, and still nothing.