Hey all. There's a lot knowledgeable folks around here, so I thought I'd see if I can get some help on my problem.
I've got a Galaxy Tab 10.1 Wifi (GT-P7510, non-branded, UEKME), that I rooted about two months ago, using the instructions found on the Android Forums (can't post a link, but ti's the basic easy way to root, using Odin3). Not a superuser, but wanted to be able to back up everything. Seemed easy enough and the rooting went fine.
Haven't done anything else to it, aside from installing a few run of the mill apps. It did auto-update a couple of times.
Was working fine, now it just got stuck on this screen with a message:
Code:
ODIN3 Download Mode
(Protocol v2.1)
Reason: No Kernal
Secure Mode: Secure
Check Signature: Check
Custom Binary Download: No (0 counts)
Custom Binary: Samsung Official
Waitting USB Cable...
Downloading...
Do not turn off target!!
Apparently, it went to this screen while I was away. I didn't see it until I picked it up and there it was. It comes to this screen after the Samsung title screen (not the animation) and a VERY quick screen with some red writing (goes by too fast to see what it says).
I tried to follow the original instructions again. Put the tab in download mode (power + volume down), open Odin3, select the md5, and hit start. Get a FAIL with this message:
Code:
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> recovery-cwm_4.0.0.4-sam-tab-10.1.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
The screen on the tab updates with this:
Code:
WritePArtition: Error to NvStorMgrFileWrite![err:0x30000]
DownloadPartition_odin: Error to WritePartition![err:0x30000]
Tegra_Nand_Write: Error to DownloadPartition_odin![err:0x30000]
That's as far as I've gotten. I noticed the Re-Partition option is not checked in Odin3, and the errors on the tab have to do with partitions... but didn't want to do that if I could eff it up even more.
I'm also wondering if one of the auto-updates didn't muck up the works. Maybe messed with my bootloader? Again, didn't want to go doing dangerous things without some reassurance. Also, I can't get into recovery mode; it just kinda flashes when I hit the button and stays on the option screen for download/recovery.
Any direction on how to proceed?
Any advice would be so great. It's been like this for about a week and I can't find any help. Thanks everyone.
TL;DR: Stuck in Download Mode, get errors on re-root.
This helped me and I've seen it help many others too in similar situations. Since you're stuck in download mode already it might need to be adjusted and followed from somewhere other than the beginning.
Goto http://www.teamovercome.net/p7500/?page_id=5
Towards the bottom of the guide There is a section called Restocking yer system.
Follow that on down.
Make sure you use the files for you device (7500 or 7510).
Make sure you triple check that you follow everything as suggested. The most common one I see missed is the last step of doing a Wipe data/factory reset.
Let us know how it goes, as this keeps us trying to help when we know we're successful.
Sent from my GT-P7510 using XDA Premium HD app
You have an incomplete bootsector the bootloader is broken but ofcourse your recovery is safe. Just flash a stock firmware on top of it, or flash CWM. You don't have to worry about the options being checked as Odin 1.83 onwards fixes this issue.
Well, I was really hopeful when I read your response and read through the guide, but alas, I still got the FAIL when running Odin.
Aside from the rom, what else is there? I know of bootloaders, but not their function or how they work, and undersstand that loading the incorrect one (or incorrectly) can really make my tab a brick.
Are there any other suggestions?
Thanks for your help so far, maybe we can get this thing working. It's a shame - I've only had it for a couple of months...
Is there any other way to flash my firmware and/or repair my bootsector/bootloader?
Thanks for your help.
stusic said:
Well, I was really hopeful when I read your response and read through the guide, but alas, I still got the FAIL when running Odin.
Aside from the rom, what else is there? I know of bootloaders, but not their function or how they work, and undersstand that loading the incorrect one (or incorrectly) can really make my tab a brick.
Are there any other suggestions?
Thanks for your help so far, maybe we can get this thing working. It's a shame - I've only had it for a couple of months...
Click to expand...
Click to collapse
If you followed what I posted, and triple checked every step and check box in the guide was exactly what you did, then I'm lost for other suggestions. Misledz is on a different time than here, so you can either try my process again, if that's what you used, making sure you do evrything as said in the restocking yer system guide on down or wait for more help.
Yeah, I was hoping because it was a really well written guide with links to the correct files right there that I'd have some luck. The directions are pretty straightforward, so I don't think I missed anything, but I can certainly try again.
Thanks, I'll update in a bit.
I think I'm going to have to wait to see if Misledz has any other suggestions - I just tried it again and got the same fail.
stusic said:
I think I'm going to have to wait to see if Misledz has any other suggestions - I just tried it again and got the same fail.
Click to expand...
Click to collapse
Sorry that sucks.
Hope Misledz or someone comes along for you.
Best of luck.
Edit: Looking at the Odin repartition error makes me think it may be a full hardware failure issue. But there is still hope with the right files or method for it to be fixed.
I can't find it, but there was another thread here with the same "Reason: No Kernal" error and I think it turned out to be a hardware failure.
Sorry well yeah I've been on offset timezone's and I tend to check this section regularly as I hope to learn more about the tablet In hopes I can get some development done on it.
In the sense I'll assure you that you can't really brick the tablet as they are somewhat hard to brick via software, unless you install a firmware that isn't compatible (Like a 7500 on a 7510) or like wipe the bootloader. Put it this way anything done in download mode is safe.
Now to your query. It can't be a hardware issue because as you can see the tablet itself boots perfectly to Odin.
I would suggest skipping the v4 of CWM and flash the v5
[http://www.mediafire.com/?6c5tdmds927npdv]
and
http://www.teamovercome.net/p7500/wp-content/plugins/download-monitor/download.php?id=15
Normally errors like this occur only because of cases like ramdisk being different. One is the 5.1 and the other is the 5.5 version, I suggest it's best to try both. I feel you will have better luck testing both. No worries they are both safe and the 4.0.4 has some issues as far as some tablet's are concerned.
Misledz said:
Now to your query. It can't be a hardware issue because as you can see the tablet itself boots perfectly to Odin.
Click to expand...
Click to collapse
That's reassuring.
Misledz said:
I would suggest skipping the v4 of CWM and flash the v5
[http://www.mediafire.com/?6c5tdmds927npdv]
and
http://www.teamovercome.net/p7500/wp-content/plugins/download-monitor/download.php?id=15
Normally errors like this occur only because of cases like ramdisk being different. One is the 5.1 and the other is the 5.5 version, I suggest it's best to try both. I feel you will have better luck testing both. No worries they are both safe and the 4.0.4 has some issues as far as some tablet's are concerned.
Click to expand...
Click to collapse
I notice the second file is in a p7500 directory. I'm guessing this is an all-encompassing directory with p7500 and 7510 files?
EDIT: I see that the file is for all versions (75xx). Thanks.
I'm at work now, but I'll try it when I get home and give an update.
Thanks for taking the time to help me out.
*fingers crossed*
Dammit. No luck.
Did you already tried flashing with a pit file?
Flash with pit will rebuild your partitions.
When loading pit file repartition will automaticaly be select.
Do not repartion without pit file or your device will become abrick.
After flash with pit file you will see a lot of errors this is normal
And will be fixed after factory reset.
Good luck.
Sent from my GT-P7500 using xda premium
brieuwers said:
Did you already tried flashing with a pit file?
Flash with pit will rebuild your partitions.
When loading pit file repartition will automaticaly be select.
Do not repartion without pit file or your device will become abrick.
After flash with pit file you will see a lot of errors this is normal
And will be fixed after factory reset.
Good luck.
Sent from my GT-P7500 using xda premium
Click to expand...
Click to collapse
If you check out his screen shot posted above it shows he used a pit file at least in one attempt
He's still having issues so your help with this would be and is highly needed and appreciated.
Sent from my GT-P7510 using XDA Premium HD app
I've used the pit file and tar file from the guide that Benzoman directed me to. I also tried using the updated CWMs that were suggested (although a pit file wasn't included).
I had installed the windows drivers a while back, but just installed the Kies. Interestingly, after that, I tried flashing again and, although it still failed, it took a lot longer (as opposed to almost instantly). Almost thought I had it for a second...
Am I right in thinking that I can use the pit file from the guide and the tar file from CWM together?
Slightly off-topic; what's the purpose of flashing a bootloader? That's one thing I haven't tried yet.
Thank you for your continued help. I would have lost all hope by now if it weren't for you and this forum.
So is it all good? I don't tend to like leaving people who need help Especially when it's also educational for me.
Flashing a bootloader wouldn't be advisable cause it may really brick the tab.
You don't really need to pit file as it is used for repartioning, flashing just the PDA is good enough
Misledz said:
So is it all good?
Click to expand...
Click to collapse
No, it's still stuck. It seems like any pit file I try doesn't work, which was why I was asking about the bootloaders (I know it's dangerous, but for all intents and purposes, it's already bricked).
I don't know what else to do; I was hoping the updated CWM would help, but it runs into the same problem the other pda files have. I'd be more than happy to try any other suggestions you may have.
Thanks again.
I don't know if it's any help, but I was able to capture the really quick flash of red text as it boots. See attachment.
stusic said:
I don't know if it's any help, but I was able to capture the really quick flash of red text as it boots. See attachment.
Click to expand...
Click to collapse
Sorry over my head, but hopefully Someone will look at the error and know what's going on.
Sent from my GT-P7510 using XDA Premium HD app
Related
A question. After attempting to flash a theme... I got a bootloop. So I flashed the provided undo file. Now my phone will not boot past the Galaxy S 2 screen with the warning triangle. Any help? I'm kinda panicking...
dont you make any cwm backup first ?
i believe u can still enter recovery mode ( power + home + volume up ) ,
and do full wipe, and flash any other rom .zip .
p/s: i believe you already have root, and install any rom before
no i didnt... i was rooted. i have both cwm and download mode... but phone wont boot. I live in canada so samsung has not uploaded our stock rom files...
If it is not backup-ed, then you will have an issue.
Now, try wipe phone via CWM, clear cache and clear dalvik.
Finger's crossed it work.
If not, last choice will be install any Custom ROM and it will wipe (hopefully) all the not 'right' files.
nope.... nothing... guess i will take it in for warranty... thank you anyways my friend
I got that as well in the past, although mine was caused by incompletely flashing Cyanogen. Had a major freakout before I figured it out.
The only way I found to fix it is to flash stock firmware using Odin (and you will not be able to restore stock Canadian as it hasnt been released for us yet). I went with the xxKG2 (polish firmware I think).
There may be other ways to fix the problem but this will 99% sure take care of it. Your warranty will of course be void untill the Canadian firmware is released.
Cheers!
Sent from my GT-I9100 using XDA App
An additional note: from what I understand you're also getting the insecure kernel triangle. If the counter in download mode also shows that you flashed non-official firmware/kernel, your warranty could already be void. In that case Samsung may now honour their Limited Warranty Agreement.
Sent from my GT-I9100 using XDA App
right but when i purchased the phone i also purchased an extended warranty that covers software problems
Tried following the directions in this stickied thread?
http://forum.xda-developers.com/showthread.php?t=1108499
Ahh, well in that case, lucky you =D
Sent from my GT-I9100 using XDA App
ohyeahar said:
Tried following the directions in this stickied thread?
http://forum.xda-developers.com/showthread.php?t=1108499
Click to expand...
Click to collapse
repeatedly :/ also, there is no publicly released canadian firmware afaik... so flashing an official/stock rom isnt really possible in this case..
on a side note, in recovery mode, it appears that /emmc encountered an error in mounting while all others mounted fine... not sure if this has any relevence, but there you go
Braidonh said:
repeatedly :/ also, there is no publicly released canadian firmware afaik... so flashing an official/stock rom isnt really possible in this case..
on a side note, in recovery mode, it appears that /emmc encountered an error in mounting while all others mounted fine... not sure if this has any relevence, but there you go
Click to expand...
Click to collapse
/emmc is the external sd card, you probably don't have one in the slot so it wasn't able to mount it.
The Yellow Triangle means you had something changed in the kernel partition, so the custom binary counter went up by 1.
As for stock rom, you will have to wait for Bell Canada to release one.
If you are not looking for stock, I'd recommend CyanogenMOD7, however it is still on nightly development, which means it has it fair share of issues.
I prefer CM7 and its problem over the stock which also has a fair share of issues.
if you can use downloading mode , you can flash back stock rom. believe me it will work.
you can study how to flash back stock rom using odin here --> http://forum.xda-developers.com/showthread.php?t=1075278
Braidonh said:
repeatedly :/ also, there is no publicly released canadian firmware afaik... so flashing an official/stock rom isnt really possible in this case..
Click to expand...
Click to collapse
Are you sure you've "repeatedly" followed those instructions? You claim that flashing a stock ROM isn't possible. But those instructions require you to flash a stock ROM.
You don't have to flash the ROM that is specific to your region/carrier. Just flash ANY stock ROM to get your phone working again. Then you can flash back to whatever ROM you were on previously.
But if you wanted to get back onto whatever ROM your phone initially came with, you're out of luck.
hi all, my phone simply would not boot, it shows a down load error screen whenever i try to power up the phone.
i am not able to get into the reset screen using "up vol + home + power", but i am able to get to the download screen using "down vol + home + power"
I have tried flashing a stock rom using odin, but it just got stuck at
<OSM> CODE_I9100XXKG6_CL425236_REV02_user_low_ship.tar.md5 is valid.
<OSM> MODEM_I9100XXKG6_REV_02_CL1044543.tar.md5 is valid.
<OSM> GT-I9100-CSC-MULTI-OXAKG6.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
thereafter the screen went crazy flashing and now i am not able to power up the phone.
i a really at a fix as to what i can do. hope i am able to get some advice and thanks in advance~!
<ID:0/007> Set PIT file..
Wow... you repartitioned the phone. Something that was repeatedly told not to do. Now you have a screwed up partition.
Now you will have to find a official stock rom for your phone, and the correct pit file, then repartition it and hope it works.
The first rule of Odin (for 99% of us) : you never flash a PIT file.
I feel like that should be stickied front page. It would save a lot of people a lot of trouble and possibly around 700$.
Sent from my GT-I9100 using XDA App
I need some help I have the same problem but Odin always fails when I try to flash villainrom 1.1 can you please help me? And any other firmware I flash doesnt work
edgeboy47 said:
I need some help I have the same problem but Odin always fails when I try to flash villainrom 1.1 can you please help me? And any other firmware I flash doesnt work
Click to expand...
Click to collapse
Same problem? You mean you repartitioned the phone as well?
Double check the md5 checksum to see if it is the same as posted if it is posted at all. If not, double check the file size to see if they are the same. Most browsers say the file downloaded is complete when it was disconnected somewhere, and the file is incomplete.
I find it hard to take devs seriously, when they don't post filesize or don't post md5 checksum. Either that, or those two information is really hard to find, not on the download page.
http://www.villainrom.co.uk/forum/content.php/319
Ok so what i mean is cant start the phone I just get the logo with a yellow triangle at the bottom of the page so I tried to flash kernels but that doesnt help, but whenever I try to flash bigger files with Odin (I think they are firmwares, i downloaded them from Intratech's post) or Villainrom 1.1 it always fails when it says boot.bin in the message window for the big files and factoryfs.img for villain rom
Hi everyone.
It's now been a few days that my I9100G is down. I've tried severals things found online : using a .pit file alone then flashing the firmware alone, .pit and firmware at the same time, using severals differents firware package, changing my cable, changing the USB port used, yes kies is closed, yes I've reinstalled the drivers.
I didn't tried with a x86 computer yet but I will this afternoon.
The symptoms
- Boot stuck on the logo.
- Recovery mode unavailable (I press the three buttons, I release them when the logo appear nad nothing more happend).
- Download more available.
What happends:
One day my phone suddently restart on his own. It happends to me. but when it start it was asking me to enter a password to decrypt it... but I don't remember having set this thing (and it's the first time it ever ask me that, even after a lot of reboots).
So, since I'm rooted and with CWM I boot into recovery and try a wipe. But since I don't want to lose everything I first try just a cache wipe. Then the problems started :
- after a first reboot, and since the wipe didn't changed anything, I tried to enter again in the recovery, but I get an error message (I don't remember which, I think it was something like an impossibility to mount some storage) and I get kicked off the recovery mode.
- I try to flash again a version of CWM for the I9100G.
- I can't enter at all in recovery mode anymore
- I try a full reinstalation using a all-in-one package of the firmware. It failed a different places:
- I9100GXXLSR_I9100GXXLSP_I9100GXEFLSR_HOME.tar.md5 usually fail during factoryfs.img
- I9100GXXKL5_I9100GXEFKL3_I9100GXXKL4_HOME.tar.md5 usually fail during modem.img
I start to run out of solutions and I'm in a great need of help now, I've tried all I could on my own.
Here is a bit of log from my last try with Odin :
<ID:0/010> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100GXXKL5_I9100GXEFKL3_I9100GXXKL4_HOME.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> cache.img
<ID:0/010> NAND Write Start!!
<ID:0/010> factoryfs.img
<ID:0/010> hidden.img
<ID:0/010> MLO
<ID:0/010> modem.bin
<ID:0/010>
<ID:0/010> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/010> Removed!!
Click to expand...
Click to collapse
thanks for reading
PS : I don't know if it's normal but I've flashed a couple time before and it never was awefuly long, here each tried take at least 1h-1h30. I would like to know if that's normal ^^
What exactly do you mean by that ?
Edit - Two things come to mind given the stages the flashes have been failing at; bad downloads & something PC side - temporary break in connection b/w phone & PC but not long enough for the PC OS to register, or dodgy USB ports. But that may/may not be ruled out depending on your answer to the above question.
NejaaHal said:
I didn't tried with a x86 computer yet but I will this afternoon.
Click to expand...
Click to collapse
MistahBungle said:
What exactly do you mean by that ?
Click to expand...
Click to collapse
I mean that my computer is running a 64bit OS (windows 7). I will get a computer running a 32bit OS this afternoon (maybe Odin don't like being run on a 64 bit environement <.<
MistahBungle said:
Edit - Two things come to mind given the stages the flashes have been failing at; bad downloads & something PC side - temporary break in connection b/w phone & PC but not long enough for the PC OS to register, or dodgy USB ports. But that may/may not be ruled out depending on your answer to the above question.
Click to expand...
Click to collapse
Bad downloads : maybe, but that would mean that the 3 or 4 differents downloads I did (because I thought of that possibility and I've tried to re-download the roms) all were corrupted at some point ^^'
Connection problem : maybe too, but (yeah again a but) I don't touch my computer at all during the process expeciallt to avoid the connexion to be broke.
PS : all my .tar.md5 archives gives me the "error" "There is no correct records at the end of archive" when I check them with 7-zip
Ahhh OK. Win7 x64 wouldn't normally be an issue. Trying a 32 bit OS more than likely won't give you any different result on the same machine. Given everything you've already tried, you need to try a different machine. And if it were me, I'd try more than one, because the alternative is giving up & paying someone to fix it.
The error you get with 7Zip is normal for stock roms & doesn't affect anything, but very good idea to try checking the integrity of the download though. Try checking the zip before you unzip the tar.md5. If it says files are missing/broken, there's your problem. If not, go with trying on another machine. Also, search for Hopper8's "Odin troubleshooting' thread. As thorough as you've been to this point (and you have been very thorough), there might be something relatively minor mentioned in his thread that you may not have tried.
MistahBungle said:
Ahhh OK. Win7 x64 wouldn't normally be an issue. Trying a 32 bit OS more than likely won't give you any different result on the same machine. Given everything you've already tried, you need to try a different machine. And if it were me, I'd try more than one, because the alternative is giving up & paying someone to fix it.
The error you get with 7Zip is normal for stock roms & doesn't affect anything, but very good idea to try checking the integrity of the download though. Try checking the zip before you unzip the tar.md5. If it says files are missing/broken, there's your problem. If not, go with trying on another machine. Also, search for Hopper8's "Odin troubleshooting' thread. As thorough as you've been to this point (and you have been very thorough), there might be something relatively minor mentioned in his thread that you may not have tried.
Click to expand...
Click to collapse
Yeah, I ment to use another computer ^^ I'm trying right now. Can you confirm me that a flashing can take one hour or more? (I'm not used to that amount of time)
And yeah, I don't want to give up and pay someone to do something I could do. I'm not a newbie in IT stuff, (even if I don't really know the architecture of an android phone and I don't know the use of the differents files in a rom).
7zip tell me that everything is ok about the downloaded .zip.
Thanks for the tip, I'm going to read that thread
No, a stock rom flash on the S2 should only take a couple of minutes tops. Normally in these situations, as long as you have download mode you can recover it, unless the NAND is messed up, then it's a JTAG (not always possible though) or in many cases a motherboard replacement. But forget that for now & only worry about that when you reach the end of the line so far as stuff you can try goes.
OK. So we can rule out bad download plus pretty much all the other stuff you've tried so far. Try on another machine & read his thread to make doubly sure there's not something really small/obvious we're both missing here.
ok, The ROM I've took come from sammobile so I guess it shouldn't take that amound of time.
That's factoryfs.img that take the most of the time ^^
I just realized that I forgot to launch Odin as administrator with windows 7 (my current try is on a x86 windows XP). But my previous (successfull ) flashes were like that too ^^'
I will continue to try on that other computer, but that will take some time to try all ports (since there is roughly 1h-1h30 to try to flash + the time for a full recharge of the battery <.<)
After having read a couple of threads here I realized that I took a .pit file from somewhere but haven't followed the step there :
[Fix] [Guide] [For Noobs] Recover from Corrupted Memory[USE EXTREME CAUTION]
But since I still not know how is organized an android phone I don't know if I've just used a generic thing that have just done nothing or if I could have messed up something. The file have this name : omap4_all_20110627_emmc.pit
I'm sorry for the double post : this is an update
The first try failed during factoryfs.img. I'm currently charging the phone for a next try.
So far I've tried
- I9100GXXLB1_I9100GATOKL1_ATO
- I9100GXXLSR_I9100GXEFLSR_XEF
- I9100GXXKL5_I9100GXEFKL3_XEF
Would anyone have any idea of which other rom I could try?
Shouldn't make any difference which rom you use, as long as it's an I9100G rom. Try every stock rom you're physically able to download; Sometimes with these situations you could try 10 flashes and they all fail, yet for whatever reason the 11th works. If I had a dollar for every occasion I've seen that happen on here over the past ~2 yrs, I'd have a fair bit of money - it's not super common, but it's not unheard of either.
So keep at it, perseverance might just recover it when trying every single thing you/everyone else on here can think of won't.
Okay, I'll keep going then ^^ may a custom rom work better?
I still don't understand why it take so much time ^^'
My guess is....at this point, you probably don't have root access, so a custom rom probably won't flash (can you even get into recovery mode?)
Read hopper8s guide and look for the link to the 3 part or test firmware. Most (if not all) single file firmwares simply overwrite what is already installed.....the test firmware will wipe the previous install and allow you to clean flash the firmware.....it *might* work where other firmwares haven't.......
Sent from my GT-I9100 using xda app-developers app
---------- Post added at 06:36 PM ---------- Previous post was at 06:18 PM ----------
Edit
Forget about the test firmware until you can be sure it's compatiable with the i9100G.....
Sent from my GT-I9100 using xda app-developers app
keithross39 said:
My guess is....at this point, you probably don't have root access, so a custom rom probably won't flash (can you even get into recovery mode?)
Read hopper8s guide and look for the link to the 3 part or test firmware. Most (if not all) single file firmwares simply overwrite what is already installed.....the test firmware will wipe the previous install and allow you to clean flash the firmware.....it *might* work where other firmwares haven't.......
Sent from my GT-I9100 using xda app-developers app
---------- Post added at 06:36 PM ---------- Previous post was at 06:18 PM ----------
Edit
Forget about the test firmware until you can be sure it's compatiable with the i9100G.....
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
No, as I said in my first post I can't access the recovery mode. or I don't do it correctly or it don't work anymore.
Hummm ok I will wait about the test firmware ^^' what could happend if it is not compatible?
I'm a little lost into the amount of rom available. Should I only try official roms? could I try other ones, if yes, which ones?
The worst part is that I don't remember which version was running on my phone. I was rooted, up to date I think, but that's all I remember, and I always see "only use this rom with a x.x.x rom" so <.<
also, after having tried so much time to reinstall it, does the indication "only use this rom with a x.x.x rom" still apply?
It doesn't matter which stock firmware you flash/whether it's specifically for your carrier or not. The aim is to get the phone working normally, so any stock I9100G firmware will do.
The suggestion to try a 3 part firmware is a good one, but I honestly don't know if there is such a thing for the I9100G as there is for the I9100.
You really need to start trying with a different PC and more than one if you can, because the alternative involves paying a Samsung service centre a not insignificant sum of money to fix your phone.
Done some google searching and it seems that there is no test firmware for your phone.....I WOULDN'T recommend using the one linked to in hopper8s thread.....the hardware in the phones (specifically the chipsets) are different......you'd probably kill your phone if you used it.
Below is a link to the latest firmware for your phone...
http://hotfile.com/dl/193267715/c98...GT-I9100G-XEF-I9100GXXLSR-1359122020.zip.html
Sent from my GT-I9100 using xda app-developers app
Thanks for all your answers.
I will then continue to try severals computers and severals roms.
I still wonder one thing :
would it be possible to install all the different parts separately? it always fail at the same step, is it possible to install the different parte one after the other? that would avoid me to have to wait 2h between two tries ^^
Also I wonder : what is the use of the .dll file I always find in the .zip ?
Edit : I just noticed something; in the latest version of Odin there is a option called "NAND erase all". would it be a good alternative to the 3-part test firmware?
I hate to do that but : little up about my last questions ^^'
NejaaHal said:
Hi everyone.
It's now been a few days that my I9100G is down. I've tried severals things found online : using a .pit file alone then flashing the firmware alone, .pit and firmware at the same time, using severals differents firware package, changing my cable, changing the USB port used, yes kies is closed, yes I've reinstalled the drivers.
I didn't tried with a x86 computer yet but I will this afternoon.
The symptoms
- Boot stuck on the logo.
- Recovery mode unavailable (I press the three buttons, I release them when the logo appear nad nothing more happend).
- Download more available.
What happends:
One day my phone suddently restart on his own. It happends to me. but when it start it was asking me to enter a password to decrypt it... but I don't remember having set this thing (and it's the first time it ever ask me that, even after a lot of reboots).
So, since I'm rooted and with CWM I boot into recovery and try a wipe. But since I don't want to lose everything I first try just a cache wipe. Then the problems started :
- after a first reboot, and since the wipe didn't changed anything, I tried to enter again in the recovery, but I get an error message (I don't remember which, I think it was something like an impossibility to mount some storage) and I get kicked off the recovery mode.
- I try to flash again a version of CWM for the I9100G.
- I can't enter at all in recovery mode anymore
- I try a full reinstalation using a all-in-one package of the firmware. It failed a different places:
- I9100GXXLSR_I9100GXXLSP_I9100GXEFLSR_HOME.tar.md5 usually fail during factoryfs.img
- I9100GXXKL5_I9100GXEFKL3_I9100GXXKL4_HOME.tar.md5 usually fail during modem.img
I start to run out of solutions and I'm in a great need of help now, I've tried all I could on my own.
Here is a bit of log from my last try with Odin :
thanks for reading
PS : I don't know if it's normal but I've flashed a couple time before and it never was awefuly long, here each tried take at least 1h-1h30. I would like to know if that's normal ^^
Click to expand...
Click to collapse
No, thats definitely not normal, I have an i9100 and it has never taken longer than a few mins to flash via odin. I did make the mistake once of trying to flash my wifes i9100 which i assumed was an i9100g because it was white, might be not applicable to you, but it may be worth checking you have an i9100g not an i9100 - just look under your battery!
Good luck.
Jimsilver73 said:
No, thats definitely not normal, I have an i9100 and it has never taken longer than a few mins to flash via odin. I did make the mistake once of trying to flash my wifes i9100 which i assumed was an i9100g because it was white, might be not applicable to you, but it may be worth checking you have an i9100g not an i9100 - just look under your battery!
Good luck.
Click to expand...
Click to collapse
Thanks ^^ but I am completly absolutely sure I have a i9100G ^^ because I already had problems before to find a way to root my phone ^^ and it say I9100G on the phone ;p I even tried to change it for a normal i9100 at the store I bought it but they told me they only had that version^^
Edit / news: I've tried to flash some part separately (from here :
[COLLECTIONS][MIRROR] Official Firmwares, Kernels, Modems, Bootloaders ). the bootloader don't fail, the kernel don't fail but the modem always fail while writing (now writing [...] -> blank line -> Received response from LOKE -> fail)
I don't know what to do now <.<
New question : have anyone any solution to allow me to have at least access to the recovery? is there any way to flash only the recovery? I made a lot of searches but couldn't find anything :/
If you can flash a custom kernel, you'll get (usually) CWM recovery.......then at that point you can do the full range of wipes and in theory flash custom roms.....
Sent from my GT-I9100 using xda app-developers app
I was rooted in 4.3, unrooted and successfully took the 4.4.2 OTA. While browsing the forum I saw other people state they'd successfully downgraded back to rooted 4.3. I attempted to do this first with Serge1223 's instructions on his rooted 4.4.2, and this failed. I then tried the no-wipe and COMPLETE-WIPE methods.
Now all I get from ODIN is the following:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I545VRUEMK2_I545VZWEMK2_I545VRUEMK2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
<ID:0/006> Added!!
Help? Please? I can boot into both Recovery and Download modes, but cannot get a fix to take.
caniswesley said:
I was rooted in 4.3, unrooted and successfully took the 4.4.2 OTA. While browsing the forum I saw other people state they'd successfully downgraded back to rooted 4.3. I attempted to do this first with Serge1223 's instructions on his rooted 4.4.2, and this failed. I then tried the no-wipe and COMPLETE-WIPE methods.
Now all I get from ODIN is the following:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I545VRUEMK2_I545VZWEMK2_I545VRUEMK2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
<ID:0/006> Added!!
Help? Please? I can boot into both Recovery and Download modes, but cannot get a fix to take.
Click to expand...
Click to collapse
Once you've updated to 4.4, you can't flash a 4.3 ROM because the kernel has a higher rev level than the kernel in MJ7/MK2.
You've got to use Surge's directions to flash just the base ROM, leaving the 4.4 kernel in place. Then you need to use bypasslkm to install the WiFi module to allow WiFi to work.
This is why I'm trying to discourage people from going to 4.4. You CAN NOT completely return to MK2 - you can get most of the way there, but can't get the MK2 kernel back, so you've got to use bypasslkm.
I'm still on MK2 and will stay there until a lot more of this is figured out. I'd recommend that you either stay with MK2, or assume that once you go to NC5 that you're not going to have to live with it.
k1mu said:
Once you've updated to 4.4, you can't flash a 4.3 ROM because the kernel has a higher rev level than the kernel in MJ7/MK2.
You've got to use Surge's directions to flash just the base ROM, leaving the 4.4 kernel in place. Then you need to use bypasslkm to install the WiFi module to allow WiFi to work.
This is why I'm trying to discourage people from going to 4.4. You CAN NOT completely return to MK2 - you can get most of the way there, but can't get the MK2 kernel back, so you've got to use bypasslkm.
I'm still on MK2 and will stay there until a lot more of this is figured out. I'd recommend that you either stay with MK2, or assume that once you go to NC5 that you're not going to have to live with it.
Click to expand...
Click to collapse
Thanks a lot for your reply @k1mu.
I have had a difficult time understanding Serge1223's instructions on how to flash only the base ROM. I don't quite get how to use bypasslkm. Is it possible you could explain (to someone still seeking a deeper understanding) more detailed instructions?
caniswesley said:
Thanks a lot for your reply @k1mu.
I have had a difficult time understanding Serge1223's instructions on how to flash only the base ROM. I don't quite get how to use bypasslkm. Is it possible you could explain (to someone still seeking a deeper understanding) more detailed instructions?
Click to expand...
Click to collapse
If I don't have Safestrap already installed, am I out of luck? Is my phone just... dead, even though it can boot into Download and Recovery modes?
caniswesley said:
Thanks a lot for your reply @k1mu.
I have had a difficult time understanding Serge1223's instructions on how to flash only the base ROM. I don't quite get how to use bypasslkm. Is it possible you could explain (to someone still seeking a deeper understanding) more detailed instructions?
Click to expand...
Click to collapse
When you update to 4.4.2, there's a new kernel. You can't downgrade that kernel since the bootloader won't allow it.
So, when you downgrade, you install most of the MK2 system, but leave the NC2 or NC5 kernel in place.
Since kernel modules are signed, you can't install a MK2 WiFi driver on the NCx version of the kernel.
What bypasslkm does is to flip the flag that tells the kernel to enforce proper module signatures. This allows the kernel to load the wifi module from the MK2 build without having it be rejected. That's why you need bypasslkm.
That's the explanation of what bypasslkm does. The directions for running it aren't all that hard - push to /data/local/tmp using adb, then run it at boot time. If you can't get that working, then you're probably going to have to stick with Kit Kat until the downgrade process gets better refined.
---------- Post added at 08:40 PM ---------- Previous post was at 08:38 PM ----------
caniswesley said:
If I don't have Safestrap already installed, am I out of luck? Is my phone just... dead, even though it can boot into Download and Recovery modes?
Click to expand...
Click to collapse
You can always use ODIN to flash the Kit Kat ROM again once the NB5 kit becomes available.
k1mu said:
When you update to 4.4.2, there's a new kernel. You can't downgrade that kernel since the bootloader won't allow it.
So, when you downgrade, you install most of the MK2 system, but leave the NC2 or NC5 kernel in place.
Since kernel modules are signed, you can't install a MK2 WiFi driver on the NCx version of the kernel.
What bypasslkm does is to flip the flag that tells the kernel to enforce proper module signatures. This allows the kernel to load the wifi module from the MK2 build without having it be rejected. That's why you need bypasslkm.
That's the explanation of what bypasslkm does. The directions for running it aren't all that hard - push to /data/local/tmp using adb, then run it at boot time. If you can't get that working, then you're probably going to have to stick with Kit Kat until the downgrade process gets better refined.
Click to expand...
Click to collapse
I can't get it to boot into anything anymore other Download Mode that now says "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again", but Kies doesn't recognize my phone.
I fear I may have wiped my partitions. How do I repartition or reinstall 4.4.2? I'd be happy to be back on 4.4.2 with no root and a functional phone....
caniswesley said:
I can't get it to boot into anything anymore other Download Mode that now says "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again", but Kies doesn't recognize my phone.
I fear I may have wiped my partitions. How do I repartition or reinstall 4.4.2? I'd be happy to be back on 4.4.2 with no root and a functional phone....
Click to expand...
Click to collapse
In your "encountered an issue", try using volume up or volume down. One of those may get you past the error and allow a boot to succeed.
k1mu said:
In your "encountered an issue", try using volume up or volume down. One of those may get you past the error and allow a boot to succeed.
Click to expand...
Click to collapse
I can do that to get into regular Download Mode, but there is no more recovery mode (I'm assuming I somehow wiped my recovery, or because the partition (or partition list) is gone?
Do I need a PL, BL, AP, CP of 4.4.2?
caniswesley said:
I can do that to get into regular Download Mode, but there is no more recovery mode (I'm assuming I somehow wiped my recovery, or because the partition (or partition list) is gone?
Do I need a PL, BL, AP, CP of 4.4.2?
Click to expand...
Click to collapse
OKAY!!! I went a little crazy and through some crazy witchcraft, have resurrected my phone. Doubt that anyone will need this, but here's what I did to fix things after getting so far lost:
1. ODIN pushed Serge1223's downgrade to MK2 OP's using the PL from Serge1223's total WIPE MK2.... this got me to a boot screen. It froze there and wouldn't go past.
2. Then I used the leak of 4.2.2 as an OP in ODIN.... and my phone is alive again....
Thank you so much for your efforts in answering my questions @k1mu, and thank you so very much to @serge1223 for supplying such invaluable pieces.
caniswesley said:
OKAY!!! I went a little crazy and through some crazy witchcraft, have resurrected my phone. Doubt that anyone will need this, but here's what I did to fix things after getting so far lost:
1. ODIN pushed Serge1223's downgrade to MK2 OP's using the PL from Serge1223's total WIPE MK2.... this got me to a boot screen. It froze there and wouldn't go past.
2. Then I used the leak of 4.2.2 as an OP in ODIN.... and my phone is alive again....
Thank you so much for your efforts in answering my questions @k1mu, and thank you so very much to @serge1223 for supplying such invaluable pieces.
Click to expand...
Click to collapse
I am literally in the same situation you're in! I've been searching for a solution for two days straight. Is it possible to explain what you did to revive your phone a little more? thanks
Aharmlesspear said:
I am literally in the same situation you're in! I've been searching for a solution for two days straight. Is it possible to explain what you did to revive your phone a little more? thanks
Click to expand...
Click to collapse
Sure. Let's see. I realized that one of the things that I saw on ODIN when I tried to flash was the whole thing about having no recognizable partitions (if yours is saying the same thing, then this is what you'll probably want to do).
1. I grabbed the PIT file from @Surge1223's NO-WIPE and COMPLETE WIPE post, grabbed the MK2 downgrade zip file (also courtesy of @Surge1223), as well as the KitKatNC2 Leak and then went Flash-Crazy with ODIN in this sequence:
Boot your phone into Download Mode.
a. I545VRUEMK2_Downgrade.tar.md5 into the AP slot (or PDA if using Odin 3.07), and the PIT file taken from the NO-WIPE post in the PIT file slot. I can't remember if it failed, but I'm pretty sure it did. As Surge1223 said, though "the file should fail at Cache, thats ok".
Reboot your phone again into Download mode.
b. I545VRUEMK2_Downgrade_system.tar.md5 file with the same PIT file (this probably wasn't necessary, but at this point I was a bit paranoid and praying for it to work). This rebooted, but got stuck at the Verizon boot screen.
I then booted into Recovery and tried a Cache Wipe and Factory Reset. These didn't work, but I'm giving the complete sequence of events because I am also a bit superstitious at times about electronics :silly:
c. At this point I flashed the NC2 Leak in the AP slot. It flashed cleanly, and I was able to boot NC2. However, I decided I wanted to be able to root, so I repeated the steps a and b but without the PIT file <--- at this point just say NO to PIT.
I didn't need to do anything to recover sound. My sound was fine. However, the only downside is, my WIFI is now no longer accessible normally at boot. I have to run the little app I mentioned in another blog post... but the link is here
caniswesley said:
Sure. Let's see. I realized that one of the things that I saw on ODIN when I tried to flash was the whole thing about having no recognizable partitions (if yours is saying the same thing, then this is what you'll probably want to do).
1. I grabbed the PIT file from @Surge1223's NO-WIPE and COMPLETE WIPE post, grabbed the MK2 downgrade zip file (also courtesy of @Surge1223), as well as the KitKatNC2 Leak and then went Flash-Crazy with ODIN in this sequence:
Boot your phone into Download Mode.
a. I545VRUEMK2_Downgrade.tar.md5 into the AP slot (or PDA if using Odin 3.07), and the PIT file taken from the NO-WIPE post in the PIT file slot. I can't remember if it failed, but I'm pretty sure it did. As Surge1223 said, though "the file should fail at Cache, thats ok".
Reboot your phone again into Download mode.
b. I545VRUEMK2_Downgrade_system.tar.md5 file with the same PIT file (this probably wasn't necessary, but at this point I was a bit paranoid and praying for it to work). This rebooted, but got stuck at the Verizon boot screen.
I then booted into Recovery and tried a Cache Wipe and Factory Reset. These didn't work, but I'm giving the complete sequence of events because I am also a bit superstitious at times about electronics :silly:
c. At this point I flashed the NC2 Leak in the AP slot. It flashed cleanly, and I was able to boot NC2. However, I decided I wanted to be able to root, so I repeated the steps a and b but without the PIT file <--- at this point just say NO to PIT.
I didn't need to do anything to recover sound. My sound was fine. However, the only downside is, my WIFI is now no longer accessible normally at boot. I have to run the little app I mentioned in another blog post... but the link is here
Click to expand...
Click to collapse
I appreciate the explanation! Thanks! It's going to take a while to download everything but I will try my best to get this current paperweight back up and running again. I'll post back here with the results - hopefully good! haha
caniswesley said:
Sure. Let's see. I realized that one of the things that I saw on ODIN when I tried to flash was the whole thing about having no recognizable partitions (if yours is saying the same thing, then this is what you'll probably want to do).
1. I grabbed the PIT file from @Surge1223's NO-WIPE and COMPLETE WIPE post, grabbed the MK2 downgrade zip file (also courtesy of @Surge1223), as well as the KitKatNC2 Leak and then went Flash-Crazy with ODIN in this sequence:
Boot your phone into Download Mode.
a. I545VRUEMK2_Downgrade.tar.md5 into the AP slot (or PDA if using Odin 3.07), and the PIT file taken from the NO-WIPE post in the PIT file slot. I can't remember if it failed, but I'm pretty sure it did. As Surge1223 said, though "the file should fail at Cache, thats ok".
Reboot your phone again into Download mode.
b. I545VRUEMK2_Downgrade_system.tar.md5 file with the same PIT file (this probably wasn't necessary, but at this point I was a bit paranoid and praying for it to work). This rebooted, but got stuck at the Verizon boot screen.
I then booted into Recovery and tried a Cache Wipe and Factory Reset. These didn't work, but I'm giving the complete sequence of events because I am also a bit superstitious at times about electronics :silly:
c. At this point I flashed the NC2 Leak in the AP slot. It flashed cleanly, and I was able to boot NC2. However, I decided I wanted to be able to root, so I repeated the steps a and b but without the PIT file <--- at this point just say NO to PIT.
I didn't need to do anything to recover sound. My sound was fine. However, the only downside is, my WIFI is now no longer accessible normally at boot. I have to run the little app I mentioned in another blog post... but the link is here
Click to expand...
Click to collapse
Everything happened just like what you said and my phone is officially working! The only problem is that I wanted to root as well and followed step a and b without the PIT file and it wouldn't get past the samsung screen - would constantly reboot. Any idea how to fix that?
Aharmlesspear said:
Everything happened just like what you said and my phone is officially working! The only problem is that I wanted to root as well and followed step a and b without the PIT file and it wouldn't get past the samsung screen - would constantly reboot. Any idea how to fix that?
Click to expand...
Click to collapse
Have you tried booting into Recovery [If you've never booted into recovery --> (from Power Off, hold down Power + Home + Volume Up until you see the boot screen). Should see in the upper left hand corner blue text reading: "Booting into recovery". The little android dude will appear, and then fall on his side with an explanation pt. This is fine, don't panic. Just let it bring you to the menu. Use volume up and volume down to navigate and power button to select.]
In Recovery do a Factory Reset and Cache Wipe. This should fix the loop. Let me know if not....
telsecr must
caniswesley said:
Have you tried booting into Recovery [If you've never booted into recovery --> (from Power Off, hold down Power + Home + Volume Up until you see the boot screen). Should see in the upper left hand corner blue text reading: "Booting into recovery". The little android dude will appear, and then fall on his side with an explanation pt. This is fine, don't panic. Just let it bring you to the menu. Use volume up and volume down to navigate and power button to select.]
In Recovery do a Factory Reset and Cache Wipe. This should fix the loop. Let me know if not....
Click to expand...
Click to collapse
Yeah I did factory reset and cache wipe when I first did it because it kept looping and I didn't know what else to do. It didn't do anything. I flashed the NC2 file without PIT and that got me back to it booting and loading up. What allows you to root when you did those two steps without the PIT file? Does it make it so it goes back to 4.3 or something?
Aharmlesspear said:
Yeah I did factory reset and cache wipe when I first did it because it kept looping and I didn't know what else to do. It didn't do anything. I flashed the NC2 file without PIT and that got me back to it booting and loading up. What allows you to root when you did those two steps without the PIT file? Does it make it so it goes back to 4.3 or something?
Click to expand...
Click to collapse
The whole idea of flashing with A and B are to put you on 4.3 at the end. Downgrading you from NC2 to MK2. The order of things from this flash were going MK2 (which got stuck like yours did) --> NC2 (which for me, cleared up the loop) --> MK2 (which after a factory reset and wiping the cache, booted back up fine.)
I honestly I am not the expert on these things, I just used the PIT file because at the time my phone was registering as having no established Partitions. so I used the only PIT file I could easily find, crossed my fingers, and got lucky. I stopped using PIT as soon as I was able to boot even back into recovery with a stuck normal Verizon boot screen. I didn't saferoot until I had a functional MK2 (non-root) option. I honestly wanted root so that I could re-establish WIFI. Without root, I don't know of a method to easily re-obtain wifi.
Aharmlesspear said:
Yeah I did factory reset and cache wipe when I first did it because it kept looping and I didn't know what else to do. It didn't do anything. I flashed the NC2 file without PIT and that got me back to it booting and loading up. What allows you to root when you did those two steps without the PIT file? Does it make it so it goes back to 4.3 or something?
Click to expand...
Click to collapse
Does it literally go into a boot loop with the Verizon boot screen? Or is it sitting there for a while? I sat there patiently the first time it booted, and it took a while (setup stuff I think) but booted eventually.
caniswesley said:
Does it literally go into a boot loop with the Verizon boot screen? Or is it sitting there for a while? I sat there patiently the first time it booted, and it took a while (setup stuff I think) but booted eventually.
Click to expand...
Click to collapse
It just kept going to the samsung boot logo and turning off and looping. I'll try again right now - just do the factory reset and cache wipe after both files have been flashed right?
Aharmlesspear said:
It just kept going to the samsung boot logo and turning off and looping. I'll try again right now - just do the factory reset and cache wipe after both files have been flashed right?
Click to expand...
Click to collapse
Yes. I'm assuming you're rebooting after the first flash fails, and then flashing the second file....
caniswesley said:
Yes. I'm assuming you're rebooting after the first flash fails, and then flashing the second file....
Click to expand...
Click to collapse
I reflashed and it got to the verizon boot logo. It's been there for 5-10 min and I think it might be stuck there even though the animation is still continuing (light shining over text). Is this where you format and wipe cache?
Sorry in advance if this is the wrong area to post, I am stressing on my phone not working.
I need some help. My Verizon S4 did the over the air update and was working fine for a week or so. I had the unlocked bootloader previously and it removed that and I was completely stock. Now my phone says "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again" I tried Kies and it doesn't see my phone. Odin fails a few seconds in. I think it's because I have 4.4. Can someone please help me and lead me in the right direction. Thank you so much in advance!
yamaharider said:
Sorry in advance if this is the wrong area to post, I am stressing on my phone not working.
I need some help. My Verizon S4 did the over the air update and was working fine for a week or so. I had the unlocked bootloader previously and it removed that and I was completely stock. Now my phone says "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again" I tried Kies and it doesn't see my phone. Odin fails a few seconds in. I think it's because I have 4.4. Can someone please help me and lead me in the right direction. Thank you so much in advance!
Click to expand...
Click to collapse
Any particular reason you didn't want the bootloader exploit MDK brought you?
Here's the NC5 Odin tars. Most likely you need the full wipe.
http://forum.xda-developers.com/showthread.php?t=2735172
Sent from my SCH-I545 using Tapatalk
Mistertac said:
Any particular reason you didn't want the bootloader exploit MDK brought you?
Here's the NC5 Odin tars. Most likely you need the full wipe.
http://forum.xda-developers.com/showthread.php?t=2735172
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
I actually don't know what the bootloader exploit MDK is. I used to root my phones a lot and put custom ROMS on them as well. I just haven't done much on my S4, being the second day I had the phone I messed it up.
The instructions for the full wipe that are provided was exactly what I did. During Odin when it is running though the process it after 10 seconds or so it comes back and says fail. I don't know what else to try, should I be able to do a full wipe and go to a previous version like Jelly Bean if I had over the air Kitkat on my phone when it failed?
Could you send what failed? What did it say in Odon?
Sent from my SCH-I545 using XDA Premium 4 mobile app
ppat324wi said:
Could you send what failed? What did it say in Odon?
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Here is what it says when I run Odin.
<ID:0/004> rpm.mbn
<ID:0/004> aboot.mbn
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I have this SAME EXACT issue right now, feels good to know i'm not the only one.
Can't even download those tars and **** because whoever uploaded them has a horrible host, and the download fails after like two minutes.
In a huge rush to get my phone working because I need to for a trip tomorrow.... I hope someone helps us!
Looks like a similar case that happened to me. It could be a number of things.
1. Your ODIN may just have had an unlucky attempt. Retry it just to be sure.
If that fails...
2. Sounds like your phone might also be on the updated bootloader now, so you're going to have to find a stock image online somewhere (I don't have an exact link, I'm mobile ) that is using the new bootloader, and ODIN that. It's around 1.6-1.8GB download. ODIN to stock is probably the best way to fix any and all problems.
When I was on the unlocked bootloader, I had a recovery issue that for whatever reason updated and then stopped detecting, giving the error of unauthorized software, see Verizon. I didn't know how exactly to fix that, so what I ended up doing was picking up a mislabeled stock image that was MDK, but in reality was MJ7, and ODIN'd that, losing my unlocked bootloader.
Your situation is definitely fixable. You just need a stock image.
lanegriffi said:
I have this SAME EXACT issue right now, feels good to know i'm not the only one.
Can't even download those tars and **** because whoever uploaded them has a horrible host, and the download fails after like two minutes.
In a huge rush to get my phone working because I need to for a trip tomorrow.... I hope someone helps us!
Click to expand...
Click to collapse
I can upload the wipe/and no-wipe NC% tars to a different host for you. Is mega ok for you, or maybe you want google drive.
PM me
Hello gentlemen, here I am asking for help.
After trying different ROMs, I decided to go back to stock because of the frequent reboots. Today, after a few days since stock, all of a sudden the phone reboots itself and gets stuck on the Galaxy S3 logo (not bootloop). Opening recovery leads to a list of errors similar to this post, if not identical. Alas, being the d***head I am, i didn't backup EFS or system, or at least I don't know where did i put them lol
@xDave7: make shure that the downloaded firmware is correct, and flash it with Odin. Then boot into recovery and do a FactoryReset. If system still won't boot, flash a 3part-rescue-firmware with PIT-file to repartition.
rp158 said:
@xDave7: make shure that the downloaded firmware is correct, and flash it with Odin. Then boot into recovery and do a FactoryReset. If system still won't boot, flash a 3part-rescue-firmware with PIT-file to repartition.
Click to expand...
Click to collapse
Failed, here's the log
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Btw, the firmware I tried to flash was the one Kies gave me, then I downloaded it from sammobile. But since it didn't work out, could you explain me the second method, or link me a guide? Thank you
OP, your eMMC (your phone's, actually) might be on its way to the garbage - and might not. The problem is that if it is - it takes the whole phone with it.
I'd suggest going into the recovery and trying to mount the phone to PC and downloading everything you can - if you can - before doing anything else.
After that, repartition FW + PIT, and if it fails - try working from a different PC. If it fails from any PC when trying to write eMMC - well, then you probably need to buy a new phone.
Repartitioning FW:
http://forum.xda-developers.com/showpost.php?p=30087735&postcount=6
or
http://forum.xda-developers.com/galaxy-s3/help/solved-pit-bricked-dead-problem-gt-t2535367
Hey @Jack_R1, thanks for your answer. Before I proceed with one of those guides, what do you mean with:
Jack_R1 said:
I'd suggest going into the recovery and trying to mount the phone to PC and downloading everything you can - if you can - before doing anything else.
Click to expand...
Click to collapse
because I think I don't get what you mean
He means adb pull, search for how to use it. But you'll probably find all your data is gone anyhow.
boomboomer said:
He means adb pull, search for how to use it. But you'll probably find all your data is gone anyhow.
Click to expand...
Click to collapse
@boomboomer so is this to save files like pictures, music, videos, etc...? Because if that's the case, it doesn't matter really that much, the important matter is to make this phone work again. So, is there anything else I need to know before going with those guides?
Other that you'll probably need to buy a new phone, no.
boomboomer said:
Other that you'll probably need to buy a new phone, no.
Click to expand...
Click to collapse
Well, that's encouraging lol just out of curiosity, is there a reason becuase it stopped working all of a sudden and ****ed itself up so badly?
Nand memory wear.
Flash an official cwm or stock recovery.
Sent from a stolen phone!