Related
Well, I just messed up with my phone trying to flash B2G
Did it like it's said in this tutorial, worked, but then got an error. So I tried to restore my old backup => didn't work, got bootlooped
reflashed siyah, restored backup => doesn't work, bootloopat cm logo
original 4.0.3 via odin => didn't work
just siyah, full wipe and then install new zip => didn't work and REBOOTS AFTER WIPING DATA, IN EVERY KERNEL TRIED YET!
then I tried flash original 4.0.3 (xwlp7) and then the cfkernel for it, but => didn't work!
does somebody have an idea? Damn, I'm desperate!
Did you wipe cache and dalvik when re flashing stock firmware?
I've been in the same situation and I wiped cache and dalvik and factory reset, then boot to download, flash stock firmware package including stock kernel then once flashed wipe cache and dalvik and factory reset again.
Worked for me
Sent from my GT-I9100 using xda app-developers app
tried it out, stucks a this f*cking factory reset...
just this blue bar at the bottom about 10 minutes and then I gave up - or does this need more time to just wipe data?
Flash stock rom via odin like it says in the other eleventy million "bricked" topics.
Sometimes it can take a while if you are using CWM the other thing to try is go into mounts and storage and then format Data, System and internal sd card.
Then re flash via Odin
You do definitely have the correct firmware for your model?
Sent from my GT-I9100 using xda app-developers app
Yeah, I took the one from sammobile where it says switzerland - orange (and thats what I have...)
Tried with format internal storage, but still get bootloop (tried factory reset after this, but didn't work too )
Should I try with Phone EFS Clear or Phone Bootloader Update maybe (tried Re-Partition, didn't work too, maybe I need another pit?)
or should I try with the KI4 I had when I got the phone at the beginning (long time ago) with phone Bootloader update?
-angel* said:
Yeah, I took the one from sammobile where it says switzerland - orange (and thats what I have...)
Tried with format internal storage, but still get bootloop (tried factory reset after this, but didn't work too )
Should I try with Phone EFS Clear or Phone Bootloader Update maybe (tried Re-Partition, didn't work too, maybe I need another pit?)
or should I try with the KI4 I had when I got the phone at the beginning (long time ago) with phone Bootloader update?
Click to expand...
Click to collapse
You need another pit file.
Visit here: forum.xda-developers.com/showthread.php?t=1760107
I don't geht it working...
But I got now another solution, just flash siyah and use it as second rom (Custom), but seems like me dummy broke the partitions of the first rom
If somebody can give me a noob-proof (!!) guide with this pits, just here with it, but fortunately second rom is working :good:
-angel* said:
I don't geht it working...
But I got now another solution, just flash siyah and use it as second rom (Custom), but seems like me dummy broke the partitions of the first rom
If somebody can give me a noob-proof (!!) guide with this pits, just here with it, but fortunately second rom is working :good:
Click to expand...
Click to collapse
use the guide here:[GUIDE] Fix an unflashable or soft bricked GSII (I9100G/M/P/T VERSION INCLUDED!)
Well, I read this guides before, but I don't get what pit I need...
In this guide there isn't any pit and in here there are about 20 different
-angel* said:
Well, I read this guides before, but I don't get what pit I need...
In this guide there isn't any pit and in here there are about 20 different
Click to expand...
Click to collapse
you can use the .pit file from here
then follow the instructions in the previous guide.
good luck
Damn, didn't work for me too - seems like I have to just stay on only a second rom
-angel* said:
Damn, didn't work for me too - seems like I have to just stay on only a second rom
Click to expand...
Click to collapse
it seems you have corrupt nand.
You need you use the any of the .pit files in the previous tutorial. one of the first 8 pit files (especially the 8th one) should work for you.
Sure? Because in odin it sais "nand write start" and then no error?
-angel* said:
Sure? Because in odin it sais "nand write start" and then no error?
Click to expand...
Click to collapse
I know but some part of of the disk which may not even affect flashing may be responsible. you can just simply search for bootloop in Q&A section, you should find some pit files that have helped others fix similar problem.
Edit: You can try the stock pit file included with the zip package first, before trying any other pit file(s)
Should I try to just reset counter, format internal story, flash original 4.0.3 (then Counter should be still on zero, right?) and then bring into warranty and just say I got a bad OTA update?
hi guys, before, the S3 (i9300 international) keep looping and cant go to the Rom, it just happen like that, my Girlfren only use for games. and its already rooted.
Then I go to recovery mode, try to wipe cache, then wipe data, but everytime I wipe data, it always restart, I tried 3 times keep restart.
after that I just flash with the new Rom, but I dont realize that Rom, is only 160mb (i dont know its that only update or what?), I just keep flashing it, and first time still looping, and somehow, its work, i can go into the rom. but then I restart it again, now the big problems come, theres a warning, I forgot what it is, it needs Reset Factory, then I confirm it.
when restart, it just stuck at "Galaxy S3" text. I cant go to Recovery mode, only download mode. then I try flash using odin, it detect the usb, but theres no Pit file. so I cant flash it.
what is wrong?? is that they called Sudden Death Syndrome?
Can someone help me?
Thanks before
d12ew said:
hi guys, before, the S3 (i9300 international) keep looping and cant go to the Rom, it just happen like that, my Girlfren only use for games. and its already rooted.
Then I go to recovery mode, try to wipe cache, then wipe data, but everytime I wipe data, it always restart, I tried 3 times keep restart.
after that I just flash with the new Rom, but I dont realize that Rom, is only 160mb (i dont know its that only update or what?), I just keep flashing it, and first time still looping, and somehow, its work, i can go into the rom. but then I restart it again, now the big problems come, theres a warning, I forgot what it is, it needs Reset Factory, then I confirm it.
when restart, it just stuck at "Galaxy S3" text. I cant go to Recovery mode, only download mode. then I try flash using odin, it detect the usb, but theres no Pit file. so I cant flash it.
what is wrong?? is that they called Sudden Death Syndrome?
Can someone help me?
Thanks before
Click to expand...
Click to collapse
yes. you flashed some wrong file and your S3 is under SDS. though, try flashing 3 files from odin(i.e., pit file separately) goodluck :good:
sriram231092 said:
yes. you flashed some wrong file and your S3 is under SDS. though, try flashing 3 files from odin(i.e., pit file separately) goodluck :good:
Click to expand...
Click to collapse
where I can find a pit file for the S3?
I found it one, but it stuck at "maping re-partition" at odin
thanks
d12ew said:
where I can find a pit file for the S3?
I found it one, but it stuck at "maping re-partition" at odin
thanks
Click to expand...
Click to collapse
may help you: http://forum.xda-developers.com/showthread.php?t=2183140
be sure you tick re-partition when you flash PIT files. good luck
sriram231092 said:
may help you: http://forum.xda-developers.com/showthread.php?t=2183140
be sure you tick re-partition when you flash PIT files. good luck
Click to expand...
Click to collapse
thank u so much.. i will try it.
I should tick that Auto reboot, Re-partition, and F.Reset time, right?
flashing a wrong file has nothing to do with SDS, actually.
it can, however, kill the phone, which is probably what happened here. you can try restoring the pit, but it's unlikely that it'll work considering you don't know what you're doing
Glebun said:
flashing a wrong file has nothing to do with SDS, actually.
it can, however, kill the phone, which is probably what happened here. you can try restoring the pit, but it's unlikely that it'll work considering you don't know what you're doing
Click to expand...
Click to collapse
i try and keep failed to restoring the pit
yeah I dont know what am I doing, would u care to help me?
d12ew said:
i try and keep failed to restoring the pit
yeah I dont know what am I doing, would u care to help me?
Click to expand...
Click to collapse
You now require to buy a new motherboard .
jje
hi, i flashed my galaxy s2 i777 to JB 4.1.2 with odin and when it restarted, it didnt recognize the sim card, then i checked and the IMEI an Baseband were gone, i have a screenshot with the IMEI it had, but i didnt backed EFS, i didnt even know that i had to, when flashing, its not the first time i flash, i had 4.0.3 then flashed to 4.1.2, and then i had a problem and flashed to 4.3 then it got stuck on rethink possible screen so i flashed back to 4.1.2, and now im without IMEI o BASEBAND, like this it doesnt recognize any sim card, please help, ive already searched in the forum but didnt find a working solution for me!
Thanks!
Did ya try to wipe data/factory reset in Recovery and then re Odin stock 4.1.2 firmware ?
Sent from my Nexus 5 using Tapatalk
4-2ndtwin said:
Did ya try to wipe data/factory reset in Recovery and then re Odin stock 4.1.2 firmware ?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
yes i did, twice, i used gsii repair too, it said that my phone was unlocked but nothing happened when restarted, i tried the method of erasing efs folder, copying, recopying, and all that, i use the command su chown 1001:radio /efs/.... but it says "no radio found". any idea why is that happening?, i need help with this!! and thanks.
PD: one question, i always see that everyone asks here to read the stickies, where are the stickies or what are they?, what i do is read the previous threads in search for an answer but i havent see the stickies.
juanf9224 said:
yes i did, twice, i used gsii repair too, it said that my phone was unlocked but nothing happened when restarted, i tried the method of erasing efs folder, copying, recopying, and all that, i use the command su chown 1001:radio /efs/.... but it says "no radio found". any idea why is that happening?, i need help with this!! and thanks.
Click to expand...
Click to collapse
Did you use a pit file and repartition during one of your flashes?
PD: one question, i always see that everyone asks here to read the stickies, where are the stickies or what are they?, what i do is read the previous threads in search for an answer but i havent see the stickies.
Click to expand...
Click to collapse
Sticky threads are at the top of each forum in the desktop version of the forum, and have a push pin icon on the left. On the mobile version of the forum, I think there is a separate tab for the sticky threads.
creepyncrawly said:
Did you use a pit file and repartition during one of your flashes?
Click to expand...
Click to collapse
i didnt, altough, i wanted to, because i saw that it was the solution to a problem i had when flashing, but no, i didnt use the pit file nor repartition.
creepyncrawly said:
Sticky threads are at the top of each forum in the desktop version of the forum, and have a push pin icon on the left. On the mobile version of the forum, I think there is a separate tab for the sticky threads.
Click to expand...
Click to collapse
ohhh, i see, thanks.
juanf9224 said:
i didnt, altough, i wanted to, because i saw that it was the solution to a problem i had when flashing, but no, i didnt use the pit file nor repartition.
Click to expand...
Click to collapse
Well, I don't know exactly what you did to mess with the imei/efs. Without a backup, it's going to be difficult to recover from that problem. Frankly, I don't know enough about it to be of any help. I think I've read that you can get the phone working with a generic IMEI but you can't get the original IMEI back. But again, it's just speculation on my part. Maybe someone else who knows more will jump in.
when I had this issue I flashed with odin back to JB 4.1.2 stock and that seemed to fix it, don't know if it will be work for you but its worth looking into
creepyncrawly said:
Well, I don't know exactly what you did to mess with the imei/efs. Without a backup, it's going to be difficult to recover from that problem. Frankly, I don't know enough about it to be of any help. I think I've read that you can get the phone working with a generic IMEI but you can't get the original IMEI back. But again, it's just speculation on my part. Maybe someone else who knows more will jump in.
Click to expand...
Click to collapse
i tried to downgrade to ics 4.0.3 but always fails with odin, i was looking into the version of the firmware by typing *#1234# and in it says:
PDA : 1777UCMD8
PHONE: Unknown
CSC: I777ATTMD8
is there any way to get the phone file, i see in odin that it has a phone option, so, i'd like to try and flash that file and see, any idea where to get it for JB 4.1.2?
micallan_17 said:
when I had this issue I flashed with odin back to JB 4.1.2 stock and that seemed to fix it, don't know if it will be work for you but its worth looking into
Click to expand...
Click to collapse
my actual firmware is JB 4.1.2 so i cant go back to it since that's the one i have, and i've tried to downgrade to 4.0.3 wich is the rom it had when i bought it, but it always fails on factoryfs.img dont know why.
juanf9224 said:
my actual firmware is JB 4.1.2 so i cant go back to it since that's the one i have, and i've tried to downgrade to 4.0.3 wich is the rom it had when i bought it, but it always fails on factoryfs.img dont know why.
Click to expand...
Click to collapse
yes but regardless of you currently being on 4.1.2 you can still reflash the stock jb 4.1.2 firmware via odin, you can try redownloading the image file since you might have a case of a corrupted image.
I agree that you should attempt to flash stock ucmd8 again after re-downloading the file. You should flash the .tar.md5 version. Odin will check the md5 sum of the file before flashing and only flash it if it is not corrupt. You can find a download for it in the Download Repository. It's the very last item at the bottom.
micallan_17 said:
yes but regardless of you currently being on 4.1.2 you can still reflash the stock jb 4.1.2 firmware via odin, you can try redownloading the image file since you might have a case of a corrupted image.
Click to expand...
Click to collapse
Yes, i've reflashed several times jb4.1.2 but the imei is still unkown as well as the baseband.
Where do i get the image file so i can flash it? Or you mean the firmware?
juanf9224 said:
Where do i get the image file so i can flash it? Or you mean the firmware?
Click to expand...
Click to collapse
By the image file, he means the firmware file. I put a link to the Download Repository in my last post, and it is also in my signature on every post. Did you download from there and try flashing that file? If not, please do that as your next step.
creepyncrawly said:
By the image file, he means the firmware file. I put a link to the Download Repository in my last post, and it is also in my signature on every post. Did you download from there and try flashing that file? If not, please do that as your next step.
Click to expand...
Click to collapse
i see, ill try now with that, thanks man, ill be back to let you know if it worked.
creepyncrawly said:
I agree that you should attempt to flash stock ucmd8 again after re-downloading the file. You should flash the .tar.md5 version. Odin will check the md5 sum of the file before flashing and only flash it if it is not corrupt. You can find a download for it in the Download Repository. It's the very last item at the bottom.
Click to expand...
Click to collapse
i flashed with that JB from the repository but nothing, same as always, the last thing i want to try is to downgrade, but when i try to downgrade to 4.0.3 it always fail on factoryfs.img, and i flashed 4.3 but it got stuck on rethink possible, do i need some specific way to downgrade?
juanf9224 said:
i flashed with that JB from the repository but nothing, same as always, the last thing i want to try is to downgrade, but when i try to downgrade to 4.0.3 it always fail on factoryfs.img, and i flashed 4.3 but it got stuck on rethink possible, do i need some specific way to downgrade?
Click to expand...
Click to collapse
At this point, downgrading to 4.0.3 is probably not a solution. From all the information that you have posted so far, it appears that your phone either has a firmware issue such as corrupt memory, or a hardware issue such as damaged eMMC memory. It is also possible that a necessary step is being skipped, such as performing a wipe data/factory reset from within recovery. Although both myself and 4-2ndtwin have mentioned that you should do that, you have never specifically stated in any of your three threads that you followed our advice.
So first things first, have you performed a wipe data/factory reset from within recovery? Have you included this step with every attempt to flash a firmware through Odin3?
creepyncrawly said:
At this point, downgrading to 4.0.3 is probably not a solution. From all the information that you have posted so far, it appears that your phone either has a firmware issue such as corrupt memory, or a hardware issue such as damaged eMMC memory. It is also possible that a necessary step is being skipped, such as performing a wipe data/factory reset from within recovery. Although both myself and 4-2ndtwin have mentioned that you should do that, you have never specifically stated in any of your three threads that you followed our advice.
So first things first, have you performed a wipe data/factory reset from within recovery? Have you included this step with every attempt to flash a firmware through Odin3?
Click to expand...
Click to collapse
i did, last night i flashed to ics 4.0.3 and perform a wipe data/factory reset before, but it got stuck on rethink possible screen, now ill flashed back to 4.1.2 , in case of corrupt memory, what could do?
creepyncrawly said:
At this point, downgrading to 4.0.3 is probably not a solution. From all the information that you have posted so far, it appears that your phone either has a firmware issue such as corrupt memory, or a hardware issue such as damaged eMMC memory. It is also possible that a necessary step is being skipped, such as performing a wipe data/factory reset from within recovery. Although both myself and 4-2ndtwin have mentioned that you should do that, you have never specifically stated in any of your three threads that you followed our advice.
So first things first, have you performed a wipe data/factory reset from within recovery? Have you included this step with every attempt to flash a firmware through Odin3?
Click to expand...
Click to collapse
i now flashed to 4.0.4 and got stuck on rethink possible screen too, im almost giving up ._. nothing seems to work x_x.
Don't give up just yet. Try going all the way back to i777uckh7 firmware. If it doesn't boot. Power off, reboot recovery, wipe data/factory reset, then reboot. If successful, save ur EFS folder 1st, back it up with an app or Root Explorer, etc. Save it in a few places, external sdcard, pc. Then u could proceed to update to JB or wherever u r wanting to go.
Sent from my Nexus 5 using Tapatalk
I agree with 4-2ndtwin. Don't give up, and follow his suggestion.
In fact proceed according to the following sequence. If Step 1 solves the issue, stop there, otherwise proceed to step 2, and then if necessary step 3.
Step 1) 4-2ndtwin's suggestion. Download "I777UCKH7-CL503881 FULL tar.md5" from the section titled I777UCKH7-CL503881 Stock Binaries. Flash with Odin3 v1.85 (preferred version). Perform wipe data/factory reset from within recovery.
Step 2) Download the Tar version of Siyah 2.6.14 Kernel. Flash it in PDA. Without ticking Re-Partitioning. Next repeat Step 1 above.
Step 3) Download the SBL Bootloader from the Download Repository. Flash it as PDA in ODIN, without ticking Re-Partitioning. (Please observe normal bootloader flashing caution.) Next repeat Step 2 above.
To recap the above for clarity:
Step 1 - I777UCKH7 full distribution --> wipe data/factory reset
Step 2 - SiyahKernel v2.6.14 --> I777UCKH7 full distribution --> wipe data/factory reset
Step 3 - Secondary Bootloader --> SiyahKernel v2.6.14 --> I777UCKH7 full distribution --> wipe data/factory reset
I was able to downgrade from the NG6 update released a few days ago back to NC5.
Knox Warranty Void: 0x0
I used the info and tut from this post
I used the full wipe method, I'm unsure if the no wipe one works
Information:
1. ROOT METHOD can be found here
2. Otherwise, Download Odin 3.09 here (Note: Bootloader = BL , PDA = AP , Phone = CP)
Download: VRUFNC5 No-Wipe SCH-I545_VZW_1_20140330160240_yni63xq6zh.zip
MD5: 71d1c7ea58d2ba81ccadd965b54a2215
Download: VRUFNC5 Full-Wipe SCH-I545_VZW_1_20140330160240_8il17ls9o2_fac.zip
MD5: 8a22dd4a47c2c5f890227fd952657d38
Directions:
No-Wipe
1. Unzip the file and you should have a tar.md5
2. Select the tar.md5 in Odin under PDA (or AP if using Odin 3.09) and keep Odin's default settings
3. Click start and wait for it to say Pass!
Full Wipe ( AKA Emeregency Repair)
1. Unzip the file and you should have a ALL_VZW_I545VRUFNC5_I545VZWFNC5_1151670_REV06_user _low_ship_MULTI_CERT.tar.md5
2. Select the tar.md5 in Odin under PDA (or AP if using Odin 3.09) and keep Odin's default settings
3. Extract the PIT file from your phone or Odin tar, also I've uploaded it here just in case.
4. Put the PIT file in PIT and load the the Odin tar.md5 in PDA (or AP if using Odin 3.09) then click start.
Click to expand...
Click to collapse
Just confirming that this downgrade from ng6 worked for me too. im back to nc5 and yet to see if there will be no more reboots that everyone is having issues with on ng6.
Is there a way to do this with out using odin on a computer?
Im trying this right now via odin..... wish me luck.
brewer15650 said:
Im trying this right now via odin..... wish me luck.
Click to expand...
Click to collapse
Good Luck!!
Let everyone know how it went. I don't intend to take this update, but others will and will, undoubtedly, need to take the path you are now on...
snickerzz said:
I was able to downgrade from the NG6 update released a few days ago back to NC5.
Knox Warranty Void: 0x0
I used the info and tut from this post
I used the full wipe method, I'm unsure if the no wipe one works
Click to expand...
Click to collapse
No-Wipe works fine.
jwhistler said:
Good Luck!!
Let everyone know how it went. I don't intend to take this update, but others will and will, undoubtedly, need to take the path you are now on...
Click to expand...
Click to collapse
Worked like a charm. I did the full wipe and repartion(PIT). Took me a 1st timer using odin maybe 30mins to do.
npjohnson said:
No-Wipe works fine.
Click to expand...
Click to collapse
I am having a hellish time with no-wipe. Constant errors prevent input of even the lockscreen PIN. I've tried different cables, ports, running Odin as administrator and not... Ideas?
posaune76 said:
I am having a hellish time with no-wipe. Constant errors prevent input of even the lockscreen PIN. I've tried different cables, ports, running Odin as administrator and not... Ideas?
Click to expand...
Click to collapse
turn on usb debugging in the settings and turn off the lock code
snickerzz said:
turn on usb debugging in the settings and turn off the lock code
Click to expand...
Click to collapse
Damn. That probably was the thing that was killing me. After the first attempt, though, I could barely fight through the errors to a home screen, let alone change settings (delete corporate account to get rid of PIN, turn on dev mode, etc.). Ended up doing full wipe. Thanks for the thought. Lesson learned in case there's a next time.
Using Odin 3.09 for the no-wipe method, I load the NC5 .md5 file, and select it as instructed, but once I hit start, I get message stating "All threads completed. (succeed 0 / failed 0) " instantaneously without anything actually happening. I have both developer mode and USB Debugging enabled.
Am I missing something?
Ignore all of that. I loaded the .md5 file up before the phone was connected in Download Mode. Re-loading it fixed everything.
I flashed NC5 over NG6. constant ERROR!! process.acore HELP
It flashed successfully via ODIN. MD5 checker matched. So no corrupt rom. After booting, i keep getting non-stop android.process.acore & android.process.media stopped working every 1 sec, and hitting ok keeps bringing it back and I cannot do anything !!! This is so frustrating. I specifically wanted no wipe. Please tell me i dont have to Full Wipe it. How did it work for you, tell me the step by step. My NG6 was rooted, should I have unrooted first. Tell me what to do!!!
I tried to do this method,but I have had no luck. My phone returned the error "fused 6 binary 5" - What is it that I'm missing?
i keep getting errors
Going to try it.
fyi, after error upon error I tried a different cable using a different USB port. Worked like a charm!
I did the no-wipe method and got the android.process.acore & android.process.media errors. I ended up doing a full wipe and it worked fine. Unfortunately my Titanium Backup I ran the night before didn't run quite right ><. Live, learn and check backups!
NG6
Was NG6 released with a new update from VZ, or was this ported from the S5?
jwhistler said:
Good Luck!!
Let everyone know how it went. I don't intend to take this update, but others will and will, undoubtedly, need to take the path you are now on...
Click to expand...
Click to collapse
Is there a way unrooted to stop the update??
I had to take the wipe method but no biggie.
rfd177 said:
Is there a way unrooted to stop the update??
I had to take the wipe method but no biggie.
Click to expand...
Click to collapse
Are the problems with NG6 isolated to rooted phone, custom roms, or both at the same time?
i've just flash rom 4.3 for I9300 via odin but my phone is SHW-M440S. Odin showed red "fail" and the progress in s3 was about 10% and i unplugged the usb cable. When i turn on my s3 again, it said that upgrade... and i can only go to download mode. I'm downloading SHW-M440S rom and gotta install it again. May it work? I'm too scared now :crying:
Flash the firmware via odin and it will work for sure. Be sure to perform a factory reset after flashing. This happens for various reasons. No need to panic.
i've flash it again, odin fail and s3 even didnt show the progress
sriram231092 said:
Flash the firmware via odin and it will work for sure. Be sure to perform a factory reset after flashing. This happens for various reasons. No need to panic.
Click to expand...
Click to collapse
I just dont know i could thank you. It worked. Thank for encouraged me :crying: I'm really really crying
But i still want to ask you: why i install new rom but my phone isnt different from its before? My apps and data still there
Fails occur due to various reasons some of them are loose usb connections, drivers problem, Samsung kies running in the background etc., So the stock firmware would definitely recover the phone. And the main point of your mistake is, you flashed the wrong firmware. Glad that your phone isn't hard bricked! The shops won't get deleted most of the times but it's better to backup your data and factory reset the phone from recovery mode for a fresh installation.