Soft-bricked Phone - Galaxy S III Mini Q&A, Help & Troubleshooting

Hello guys!
I got a new galaxy s3 mini (i8200) today so I tried to install a custom ROM since the installed android version was pretty old. I chose cyanogenmod 11.0 from novafusion and I tried to install it using odin. During the setup I got an error:
Code:
<ID:0/011> NAND Write Start!
<ID:0/011> FAIL!
<ID:0/011>
<ID:0/011> Complete (Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
So I ended up with the phone soft-bricked and I decided to try to use KIES for firmware recovery but without success. So now I have two problems:
- The phone is soft-bricked
- I guess it ran out of battery and whenever I connect the phone to the computer (or even try to charge it) it ends up restarting itself.
Video -- the problem:
[ LINK ]
What should I do now?

icewavedesign said:
Hello guys!
I got a new galaxy s3 mini (i8200) today so I tried to install a custom ROM since the installed android version was pretty old. I chose cyanogenmod 11.0 from novafusion and I tried to install it using odin. During the setup I got an error:
Code:
<ID:0/011> NAND Write Start!
<ID:0/011> FAIL!
<ID:0/011>
<ID:0/011> Complete (Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
So I ended up with the phone soft-bricked and I decided to try to use KIES for firmware recovery but without success. So now I have two problems:
- The phone is soft-bricked
- I guess it ran out of battery and whenever I connect the phone to the computer (or even try to charge it) it ends up restarting itself.
Video -- the problem:
[ LINK ]
What should I do now?
Click to expand...
Click to collapse
http://www.gsmarena.com/samsung_i8200_galaxy_s_iii_mini_ve-6190.php
CPU: 1.2 GHz dual-core Cortex-A9
NovaFusion is based on NovaThor.
You can cry now...
... And good luck !

There is a sticky unbrick thread here:
http://forum.xda-developers.com/showthread.php?t=2159660
For the charge problem, I think it works in download mode, try to enter that and leave it for a while.
EDIT: missed that this is an i8200... Do you have a backup of stock? If not, I guess you will need to hunt one down...

Forget. My bad.

jakot said:
There is a sticky unbrick thread here:
http://forum.xda-developers.com/showthread.php?t=2159660
For the charge problem, I think it works in download mode, try to enter that and leave it for a while.
EDIT: missed that this is an i8200... Do you have a backup of stock? If not, I guess you will need to hunt one down...
Click to expand...
Click to collapse
I'm trying but I only found few options available and it's so annoying to download 600+ mb when the speed is limited to 30 kbps by the file host.
LE: Is stuck in download mode (Odin Mode) and when is charging the same thing as in the video happens.
Let's say I will be able to charge it, should I flash the stock rom image using odin or there are any other steps that I need to do in order to un-brick it?
.

icewavedesign said:
I'm trying but I only found few options available and it's so annoying to download 600+ mb when the speed is limited to 30 kbps by the file host.
Let's say I will be able to charge it, should I flash the stock rom image using odin or there are any other steps that I need to do in order to un-brick it?
.
Click to expand...
Click to collapse
Your system or boot (kernel) partition is corrupt because you tried to flash a ROM for GT-i8190/N/L model only. You should flash a stock firmware for GT-i8200 model (available on sammobile.com/firmware) if you want a working phone

xXPR0T0TYPEXx said:
Your system or boot (kernel) partition is corrupt because you tried to flash a ROM for GT-i8190/N/L model only. You should flash a stock firmware for GT-i8200 model (available on sammobile.com/firmware) if you want a working phone
Click to expand...
Click to collapse
That's true, it was my bad and I realized that later when the phone was already bricked. Do I also need "PIT" file (repartition) or flashing the stock firmware would solve the problem?

icewavedesign said:
That's true, it was my bad and I realized that later when the phone was already bricked. Do I also need "PIT" file (repartition) or flashing the stock firmware would solve the problem?
Click to expand...
Click to collapse
You don't need a PIT file. Just flash a stock firmware for your phone model and everything will be ok

Related

[Q] Flashing Kernel

Hi, I have rooted my tab ,no problem. But I read all the posts about EXT4 and kernel flashing needed for flashing roms, but I cannot find a definitive guide on how to flash the kernel using odin or EXT4.
Can anyone help with a small , simple guide on how to do this please?
I've been looking for hours and darent try it without knowing fully how.
Thanks
Stu.
Galaxy Tab UK
Recovery mod installed and Rom backed up.
Havent looked yet but i quick guide would be great if it doesnt already exist.
Sent from my HTC HD2 using XDA App
You can follow the instructions from this thread
http://forum.xda-developers.com/showthread.php?t=925760
Stu308 said:
Hi, I have rooted my tab ,no problem. But I read all the posts about EXT4 and kernel flashing needed for flashing roms, but I cannot find a definitive guide on how to flash the kernel using odin or EXT4.
Can anyone help with a small , simple guide on how to do this please?
I've been looking for hours and darent try it without knowing fully how.
Thanks
Stu.
Galaxy Tab UK
Recovery mod installed and Rom backed up.
Click to expand...
Click to collapse
Sent from my GT-P1000 using Tapatalk
Seen that post , but it doesnt say what to do with odin? As in where to load the .tar file etc.
You flash the Modaco kernel via Odin, if your file system isn't ext4 (which it won't be then you may need to manually reboot your phone - My phone still rebooted automatically coming from a rfs file system)
Once your phone reboots it should enter recovery automatically and you just sit back and let CWM backup / covert your file system to ext4 / restore your rom back on to your coverted file system
(I believe there are instance also when you phone does not automatically enter recovery on reboot, in this situation you will need to manually enter recover after flashing the kernel in Odin - to do this you hold down the power button and volume up)
Another thing worth noting, i had encountered an issue during the conversion process where CWM was not able to restore my existing rom, when this happens you can download a ext4 rom (i.e. modaco rom or overcome 1.1.3) and flash the file via CWM - i.e. you can leave the kernel and try another Rom.
Hope this helps.
thanks bendjlee, but how do I use odin? (where to put .tar file which mode should tab be in etc..).
Stu308 said:
thanks bendjlee, but how do I use odin? (where to put .tar file which mode should tab be in etc..).
Click to expand...
Click to collapse
under pda
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
This is what I get, doesnt work. Should I be in recovery or the phone in normal mode?
I also had "fail" in red in the left had box of odin, my tab is rooted and clockwork mod installed. What is wrong?
You'll need to put your tab to download mode first before connecting to your computer to odin. Turn on the tab with "volume down" held
Stu308 said:
I also had "fail" in red in the left had box of odin, my tab is rooted and clockwork mod installed. What is wrong?
Click to expand...
Click to collapse
Sent from my GT-P1000 using Tapatalk
ahh, will try it that way , but Im sure I tried that. Do I put phone in debugging mode before I go into download mode?
Download mode is different than recovery and debug. It would display an image of an android with a shovel. That is the mode you need to be in.
Even though the question was asked by someone else, these attempts to answer the question helped solve a similar problem on my side. Thanks!

[Q] bricked galaxy s? which firmware

Hi,
I've got here a bricked galaxy s from a friend of my. he tried to root the galaxy s without knowing how.
But the problem is.. I don't know which firmware he had. So i don't know which .tar file i need for odin3 to restore.
Can i track somehow the firmware? its an europe version with 2.2 he said. Or is there an other way to restore this phone?
When i startup the phone it hangs at the galaxy s logo. I can enter download mode
Use Sammobile.com
You'll need to make a login first and then just follow the click to the files..
There are also stock packages in the general section such as cf-root, to gain root access. And there are other stock firmware threads there.
Try only flashing the code.tar file, I think that's where the kernal is but best to confirm that somewhere. Otherwise just flash the whole stock package.
i bricked my galaxy and i recomand a stock package and from that you can root and you can change to a custom rom if he wants that...
Talon26 said:
Use Sammobile.com
You'll need to make a login first and then just follow the click to the files..
There are also stock packages in the general section such as cf-root, to gain root access. And there are other stock firmware threads there.
Try only flashing the code.tar file, I think that's where the kernal is but best to confirm that somewhere. Otherwise just flash the whole stock package.
Click to expand...
Click to collapse
can you be more specific how to get the right firmware? Do i need to go to SAMFIT? or SAMSUNG LETTER CODE? i have no idea how to find it
Ok, sorry i thought Sammobile.com had complete instructions on how to find the firmware for you like it used to, but I haven't used it in a while..
I don't remember what all those codes mean and tbh it doesn't matter too much. The main thing is to find your CSC code. This will be the factor that would usually cause problems (actually annoyances) if incorrect, e.g. SMS messages not being received with the correct time and date.
Here, Ramad a very respected member of the community has made a collection of firmware generally with multi-CSC's. You can use these downloads or really any of the other downloads from sammobile (link to the Europe section). It doesn't matter much if he doesn't get the correct firmware because they are all available in Europe.
Find your CSC from Samfit samsung letter code. They are the 3-letter codes nearing the bottom. Press " Ctrl + F " and then type in your country. This will highlight your country on the page. Look to see if your carrier has a specific code, if it does then remember is and look at Ramad's list.
Go down to the 2.2 or 2.2.1 section and again " Ctrl + F " and type in the CSC. Look for the firmware that has it listed. Download that firmware and flash using the instructions at the top of Ramad's thread or using the pdf that you can download from sammobile. Generally the latest build date is best to download. But if you don't it doesn't matter because you will be using stock you can plug it into Kies and it will update it for you.
To check your CSC the long way (I cannot remember the short way ) type in *#272*(your imei)#
This will display your current imei and allow you to change it. Changing it to the one you want will factory reset your phone so be ready.
If i have left anything out or you have any more questions then let me know...
Hope all goes well
http://www.google.co.uk/url?sa=t&rc...2ZTkBw&usg=AFQjCNHCNRbuqVFXltW99vQc1_pfPlNr4Q
check this out video guide
Oke. I really bricked the phone now i guess.
If i turn on power.. it doesnt do a thing. can't enter download mode either
i downloaded the right .tar file im almost sure. But when it was flashing.. The phone was constantly rebooting. so the usb connectiong diddnt stay on.
Not to worry. You probably haven't bricked it. The worst you will probably have to do is make a purchase of a USB jig which forces download mode...
Before that however there are multi tricks to try get it into DM. (Obviously make sure your battery is sufficiently charged.)
1. Hold down the combo and then put the battery in, whilst holding the combo. (You will probably need help)
2. Start Odin (make sure all kies apps are closed on the comp first) plug in phone. Hold down combo.
3. Same as number 2 without battery. If it doesn't work. Set up as 2 hold combo then battery in.
4. Same as 2 with charger instead of computer.
I think those are all the combinations but you can search for it. There used to be a thread on general listing all the ways you could be bricked and ways of getting out.
Anddddd if all that fails, then you can make or buy a USB jig. Search general if you want to buy it but also you can find links to buyers members have used.
And in the worst case none of that works.. you can set the unbrickkable mod which means you will loose warranty for ever and never get it back as it is a hardware modification. I'll give the link to that if and when you need it.
Good luck
Sent from my GT-I9000 using XDA
pfjew. it worked. can enter download mode!
But when i want to flash my proper firmware it asks for a pit file this time. But i don;t have a pit file at my firmware that i downloaded from sammobile. only a .tar file and a .dll
Which .pit should i use? I really want the right one this time. Deffenitily dont want to brick the damn thing i grabbed this firmware from sammobile
I9000XWJW1 ## 2.3.6 2012 January I9000XENJV5 Netherlands
I did a quick search because Sammobile is now super crap. Remember reading this..
[GUIDE] [INFO] The reality of PIT files
Having a quick scan of what it says, I believe it does not matter...But best to read to be sure.
Let us know if it works
it worked. flashed the firmware. rom doesnt work.. Boot loop.
Can enter Android system recovery now. But because that doent support my external sd, and i can't boot properly i can't flash a new rom?
I would like to flash CWM with external_sd support. searching for that one now
(i know how at my optimus 2x.. but everything is lots easier at optimus 2x compared to sgs)
Have you tried flashing it again?
Also have you tried flashing an older rom with a multi csc that includes your csc?
And finally [ODIN] DarkyROM 10.2 Resurrection GT-I9000, usually helps people stuck in your situation. Id try the first two though because it keeps stock.
last one worked. thanks A LOT!
Hi,
my SGS seems to be bricked. I have tried everything described in the posts before, but nothing worked.
Here is what I did:
I downloaded several roms (those mentioned in the previous posts and from other forums) and installed them via Odin3 (1.85). The Odin log says everything went fine:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PHONE_XXJW4.tar.md5 is valid.
<OSM> CSC_OXAJW4.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> zImage
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/003> Removed!!
Click to expand...
Click to collapse
The SGS reboots and stucks at the very first Samsung logo (the one without animation). When I hit the softkeys, the light goes on, but doesn't turn off again.
After each installation I didn't touch the phone for 20 minutes hoping that something happens - but nothing
Only 2 options are left:
- returning to the download mode
- removing the battery
Another strange issue: When I try to load the SGS, the displays turns on and shows the battery symbol, but it is not animated.
Has anyone an idea what else I can do?
Thank you for your help in advance!
@keinfilter:
from samfirmware.com the flash program for i9000 is 1.82 or 1.3 or 1.0
have you used the 512 pit file?
Well you say you have done all of the above...
1. You cant even boot with [ODIN] DarkyROM 10.2 Resurrection GT-I9000??
2. Wipe by going into recovery and doing all these wipes...
wipe date/factory reset + wipe cache + mount and storage>>>format system+cache+datadata+data (I dont wipe boot and you need sdcard)
After doing all the above wipes try Darky or stock with repartition checked...
3. I'm assuming that you used single tar files for flashing via odin, have you tried Odin flashes with 3 files?? If not either find a rom with 3 files or split one of the roms using the following guide by Ramad
Let us know if any of that works...
Good luck
Thanks for the very fast answers!
from samfirmware.com the flash program for i9000 is 1.82 or 1.3 or 1.0
have you used the 512 pit file?
Click to expand...
Click to collapse
I tested all three version (1.82, 1.3, 1.0), each with 3 files roms and the 512 pit file. Nothing changed, still the samsung logo.
1. You cant even boot with [ODIN] DarkyROM 10.2 Resurrection GT-I9000??
Click to expand...
Click to collapse
After trying the DarkyROM with his ODIN again, the DarkyROM logo (Galaxy S GT-I9000 powered by DarkCore & Darky's rom) is displayed instead of the samsung logo. But the boot process doesn't continue
DarkyROMs zip archive contains only the PDA.tar, what about the CHC and PHONE? Do I have to use these from other roms? I haven't tested it yet, because I don't want to make it worse.
Wipe by going into recovery and doing all these wipes...
Click to expand...
Click to collapse
I can't access the recovery mode. Tried it via holding Vol up + Home button + Power button until the Samsung logo was shown the 2nd time and then releasing all buttons, but nothing else than the samsung logo.
3. I'm assuming that you used single tar files for flashing via odin, have you tried Odin flashes with 3 files?? If not either find a rom with 3 files or split one of the roms using the following guide by Ramad
Click to expand...
Click to collapse
All the roms I tried consisted of 3 files but the DarkyROM.
Edit: Btw: I have no micro-sd or sim card inserted because I read in any forum it is better to remove them. I don't know if this makes any difference.
Has anyone further ideas? Any help would be appreciated!
Try to reflash in JVU STOCK with PiT512, MODEM, CSC, etc... with battery fully charged.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Envoyé avec Tapatalk 2.0.1 depuis mon Samsung Galaxy S GT-I9000
ROM : SLIM ICS 3.3
Kernel : Origine ROM
Modem : JW4

no recovery , only download mode (i need .pit file )

Hi
I was on RocketRom V5 and wanted to go back to GB
so i tried to install a stock GB rom using PC odin but it failed in the middle of the proccess
now the phone can only go to download mode
and if I tried to boot it or go to recovery mode it says "Frimware upgrade encountered an issue. please select recovery mode in kies & try again"
now every time i try to install a stock rom using PC odin it fails
and the useless kies is giving me an error like massage in chinese
so if there is a way to install any rom without using kies it will very helpful
max-thamer said:
Hi
I was on RocketRom V5 and wanted to go back to GB
so i tried to install a stock GB rom using PC odin but it failed in the middle of the proccess
now the phone can only go to download mode
and if I tried to boot it or go to recovery mode it says "Frimware upgrade encountered an issue. please select recovery mode in kies & try again"
now every time i try to install a stock rom using PC odin it fails
and the useless kies is giving me an error like massage in chinese
so if there is a way to install any rom without using kies it will very helpful
Click to expand...
Click to collapse
I too am facing the same situation. Hope someone comes up with a solution.
have you made a wipe while on ICS? was your phone booting normaly when you flashed it with PC ODIN?
try version 1.87 ,and if that doen't work then search for version 3 of ODIN
also do note that you should open task manager and shutdown any kies processes (usually two of them) ,kies will stop an ODIN flash ,so make sure to kill it first
i was really excited when i saw a reply i thought it was an answer
if you found a solution please post it here
max-thamer said:
i was really excited when i saw a reply i thought it was an answer
if you found a solution please post it here
Click to expand...
Click to collapse
it is an answer !!
kill KIES and you should have a smooth flashing ,unless you have corrupted your emmc by wiping on ICS of course
MR.change said:
have you made a wipe while on ICS? was your phone booting normaly when you flashed it with PC ODIN?
try version 1.87 ,and if that doen't work then search for version 3 of ODIN
also do note that you should open task manager and shutdown any kies processes (usually two of them) ,kies will stop an ODIN flash ,so make sure to kill it first
Click to expand...
Click to collapse
my phone was ok on rocketrom and it was booting ok until i tried to install a rom using PC odin
and i uninstalled kies completly to avoid any problems
i even tried odin 3 and still no luck
i will try odin 1.87 and reply back
MR.change said:
it is an answer !!
kill KIES and you should have a smooth flashing ,unless you have corrupted your emmc by wiping on ICS of course
Click to expand...
Click to collapse
i was referring to the post above you
as i said i uninstalled kies completely
and i was on speedmod kernel which its developer says he did something to the kernel which should prevent the emmc bug
is there a way to know for sure that i corrupted the emmc or not ?
when you uninstalled kies, drivers may have been affected. reinstall drivers and try again. if you can, use another pc.
Zapped through server hops to XDA forums
just tried PC odin 1.87 and no diffrence
when you uninstalled kies, drivers may have been affected. reinstall drivers and try again. if you can, use another pc.
Zapped through server hops to XDA forums
Click to expand...
Click to collapse
i tried to install the drivers again but it said the drivers are already installed
i think i will try another pc
max-thamer said:
i was referring to the post above you
as i said i uninstalled kies completely
and i was on speedmod kernel which its developer says he did something to the kernel which should prevent the emmc bug
is there a way to know for sure that i corrupted the emmc or not ?
Click to expand...
Click to collapse
yes speedmod is safe ,you have nothing to worry about a brick.
now there could be many things that effect a flash:
1.bad cable
2.running as a standard account (select run as administrator)
3.wrong set of drivers ,to resolve download and install the latest KIES ,then kill it's processes.
4.wrong ODIN version (1.87 recommended)
5.as a last resort you shold flash a pit file (but that's risky)
anyway go to this thread and download ODIN from there and flash a GB ROM
http://forum.xda-developers.com/showthread.php?t=1424997
note that the drivers are included in this thread if you do not wish to install KIES again.
just follow this guide to the letter and you should be fine.
i changed the cable with a brand new cable that was in the original package of the phone
run as administrator
reinstalled the drivers from DR.ketan thread
tried odin 1.85 & 1.87 & the new odin 3 that has a slightly diffrent cyan UI
so im afraid i need to take the risk (BTW, what are the risks ?)
and flash a pit file
so can you please tell the right way to flash a PIT file so i can avoid the risks
your help are greatly appreciated
so anybody has a sulotion for this ?
i have been searching for a solution till now with no luck
max-thamer said:
so anybody has a sulotion for this ?
i have been searching for a solution till now with no luck
Click to expand...
Click to collapse
If you can have it covered under warranty somehow, then try to seek help from SS service. Otherwise, the method in the thread below could be useful.
http://forum.xda-developers.com/showthread.php?t=1661590&page=2
cheers,
i think i will take to samsung service
thank you guys for helping
max-thamer said:
i changed the cable with a brand new cable that was in the original package of the phone
run as administrator
reinstalled the drivers from DR.ketan thread
tried odin 1.85 & 1.87 & the new odin 3 that has a slightly diffrent cyan UI
so im afraid i need to take the risk (BTW, what are the risks ?)
and flash a pit file
so can you please tell the right way to flash a PIT file so i can avoid the risks
your help are greatly appreciated
Click to expand...
Click to collapse
the risks could involve a permanent brick (not even download mod) , can you post exactly what ODIN says?
post ODIN log please
EDIT: maybe by any chance that you flashed an ICS bootloader? if so then it maybe the cause for this ,you should try to flash the official LPf using ODIN ,and if it works and the phone boots then flash Speedmod ics kernel on top of it (before wiping or anything).
here I found this pit file on the internet ,you need to choose your model (16gb or 32 gb) ,it's most likely 16gb ,right?
remember this is a last resort ,so don't use it
i will go with safer method and take it to samsung service :d
thanks anyway youve been a great help
EDIT :
sh*t , its a day off for samsung service
so ill live another day without my Gnote
this is ODIN log
<ID:0/009> Firmware update start..
<ID:0/009> cache.img
<ID:0/009> NAND Write Start!!
<ID:0/009> factoryfs.img
<ID:0/009>
<ID:0/009> Complete(Write) operation failed.
<ID:0/009> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
what do you think ?? flashing a .pit file would solve anything
and should i load a pit and a PDA file in odin or only .pit file ??
max-thamer said:
i will go with safer method and take it to samsung service :d
thanks anyway youve been a great help
Click to expand...
Click to collapse
if you still have warranty then by all means ,take it to the service center.
if you don't however then you should not give up this easily ,unless you have some cash lying around and you wish to give it to them.
either ways it's your call
good luck
max-thamer said:
i will go with safer method and take it to samsung service :d
thanks anyway youve been a great help
EDIT :
sh*t , its a day off for samsung service
so ill live another day without my Gnote
this is ODIN log
<ID:0/009> Firmware update start..
<ID:0/009> cache.img
<ID:0/009> NAND Write Start!!
<ID:0/009> factoryfs.img
<ID:0/009>
<ID:0/009> Complete(Write) operation failed.
<ID:0/009> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
what do you think ?? flashing a .pit file would solve anything
and should i load a pit and a PDA file in odin or only .pit file ??
Click to expand...
Click to collapse
weird ,it's failing to flash at factoryfs ,but it's not getting stuck during the operation.
I want you to try two things:
1.try to flash just a kernel ,try this http://forum.xda-developers.com/attachment.php?attachmentid=1068654&d=1337346991
this is the cm9 safe kernel ,if the flash with ODIN goes successful then you can boot into recovery and try to fire a nandroid restore from there
be careful flashing this with ODIN will give you a triangle and count ,so if you still have your warranty ,try to find and flash a stock kernel (which will not give you a triangle).
2.if none of the above works ,then select only the 16 GB pit file and flash it alone ,do not interrupt a pit file flash ,let it take as long as it wants . if you interrupt it then your phone is gone.
after that flash a full GB ROM with removing .pit and unticking repartition.
but I haven't done this before so if you want to go through with it I suggest you wait for someone with actual experience at this.
pit file
Here you go with 16 GB pit file

[Q] Soft brick S3mini GT-i8190

Hi
So problem started when phone would not boot, even twrp would show splash screen then reboot.
I tried to reflash cm11 using odin 3.07 it failed...
then had the "firmware upgrade encountered an issue. please select recovery mode in kies and try again"
I tired kies, failed does not recognise the phone.
followed unbrick/ restore baseband thread
odin failed again on flash
tried various builds of rom, (carbon, cm11, baseband). all fail seems to be at "system.img"
Tried to load twmp only with odin. got to reset in bule top left of odin. froze, did hard reset. odin says sucsess, but cant boot still shows "firmware upgrade encountered error"
I can get into download mode
custom binarys is also incrementing on each attempt. currently 7
Model gt- i8190
rom was cm11.0_golden.nova.20140817.ODIN_TWRP.tar
baseband I8190XXAMC1_I8190OJVAMC3_HOME.tar (South Africa)
Any help would be appreciated....
Kill_Switch422 said:
Hi
So problem started when phone would not boot, even twrp would show splash screen then reboot.
I tried to reflash cm11 using odin 3.07 it failed...
then had the "firmware upgrade encountered an issue. please select recovery mode in kies and try again"
I tired kies, failed does not recognise the phone.
followed unbrick/ restore baseband thread
odin failed again on flash
tried various builds of rom, (carbon, cm11, baseband). all fail seems to be at "system.img"
Tried to load twmp only with odin. got to reset in bule top left of odin. froze, did hard reset. odin says sucsess, but cant boot still shows "firmware upgrade encountered error"
I can get into download mode
custom binarys is also incrementing on each attempt. currently 7
Model gt- i8190
rom was cm11.0_golden.nova.20140817.ODIN_TWRP.tar
baseband I8190XXAMC1_I8190OJVAMC3_HOME.tar (South Africa)
Any help would be appreciated....
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2159660
Try flashing:
http://forum.xda-developers.com/attachment.php?attachmentid=1937012&d=1367738404
KoolKid98189 said:
http://forum.xda-developers.com/showthread.php?t=2159660
Try flashing:
http://forum.xda-developers.com/attachment.php?attachmentid=1937012&d=1367738404
Click to expand...
Click to collapse
thx kookkid,
i already did do the param flash which passes, however then i still cant get into twrp, and i sit stuck on the samsung logo
if i then try flash the rom it fails again , and back to square 1
On the phone after failure i get in red text "movi_write card_status :0 (430) start_blk:1477552" (it overwrites the "current binary: custom" line that shows up in download mode
odin just shows this:
<ID:0/005> recovery.img
<ID:0/005> STE_boot1.img
<ID:0/005> STE_boot2.img
<ID:0/005> modem.bin
<ID:0/005> system.img
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Kill_Switch422 said:
thx kookkid,
i already did do the param flash which passes, however then i still cant get into twrp, and i sit stuck on the samsung logo
if i then try flash the rom it fails again , and back to square 1
On the phone after failure i get in red text "movi_write card_status :0 (430) start_blk:1477552" (it overwrites the "current binary: custom" line that shows up in download mode
odin just shows this:
<ID:0/005> recovery.img
<ID:0/005> STE_boot1.img
<ID:0/005> STE_boot2.img
<ID:0/005> modem.bin
<ID:0/005> system.img
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Try reflashing stock or if that fails then your eMMC chip is screwed! That happened to me so I called Amazon and they gave free replacement and never found out! Don't give it to Samsung! This is why I'm scared of rooting my S3 mini!
Please visit this forum and vote on the poll
http://forum.xda-developers.com/galaxy-s3-mini/help/previously-bricked-s3-minis-t2861724
KoolKid98189 said:
Try reflashing stock or if that fails then your eMMC chip is screwed! That happened to me so I called Amazon and they gave free replacement and never found out! Don't give it to Samsung! This is why I'm scared of rooting my S3 mini
Click to expand...
Click to collapse
process followed was flash param, then flash stock. thats when it fails........................
ARRGGGGG
thx anyway
anyone else got a new thought or how to test
Kill_Switch422 said:
process followed was flash param, then flash stock. thats when it fails........................
ARRGGGGG
thx anyway
anyone else got a new thought or how to test
Click to expand...
Click to collapse
Try flashing just the param and see what happens? Then try to flash the recovery then see what happens.
One more question, did you encrypt your device?
KoolKid98189 said:
Try flashing just the param and see what happens? Then try to flash the recovery then see what happens.
One more question, did you encrypt your device?
Click to expand...
Click to collapse
I didnt encrypt no.
If I flash only param, it passes. I then get the samsung logo on boot, and nothing more.
If I flash param, then twrp they both pass, but I get the please connect to kies firmware error. booting with power home vol down has no effect...
If I flash param then twrp then stock. fail on system.img
If I just flash stock fail on system.img
used heimdall to only flask kernal with system.img completes but at end gets error:
Ending session...
ERROR: Failed to receive session end confirmation!
then back to kies firmware error
Possibly related... I have found that my battery is not charging at all ...... is this dependent on a running phone? (dont think it is a factor, since I am able to flash param and twrp and pit without a problem) but covering bases.
Kill_Switch422 said:
I didnt encrypt no.
If I flash only param, it passes. I then get the samsung logo on boot, and nothing more.
If I flash param, then twrp they both pass, but I get the please connect to kies firmware error. booting with power home vol down has no effect...
If I flash param then twrp then stock. fail on system.img
If I just flash stock fail on system.img
used heimdall to only flask kernal with system.img completes but at end gets error:
Ending session...
ERROR: Failed to receive session end confirmation!
then back to kies firmware error
Possibly related... I have found that my battery is not charging at all ...... is this dependent on a running phone? (dont think it is a factor, since I am able to flash param and twrp and pit without a problem) but covering bases.
Click to expand...
Click to collapse
Try the stock recovery?
KoolKid98189 said:
Try the stock recovery?
Click to expand...
Click to collapse
when i do the stock recovery , it seems to flash ok, on reset, goes into connect kies error
odin gives pass:
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
recovery boot (vol up power and home, just shows same screen)
Kill_Switch422 said:
when i do the stock recovery , it seems to flash ok, on reset, goes into connect kies error
odin gives pass:
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
recovery boot (vol up power and home, just shows same screen)
Click to expand...
Click to collapse
Try flashing a stock baseband kernel, the stock recovery, the stock firmware and then finally the param and tell me what happens.
KoolKid98189 said:
Try flashing a stock baseband kernel, the stock recovery, the stock firmware and then finally the param and tell me what happens.
Click to expand...
Click to collapse
please confirm you mean the
boot.img -> baseband stock
recovery.img ->recovery stock
system.img ->firmware stock
then param
if so odin fails every time I try load the system.img
the rest load just fine.

[Q] Help me please

Hello new in this forum.....
The threads I read overwhelmed me.... :cyclops:
I have a N7000 from a friend of mine. It had a dedicated 4.0.4 rom from "3" (italian operator) build IMM76D.XXLRL
I tried to install a new italian rom 4.1.2 via odin but every attempt failed
Unfortunately I ended up into a thread about ICS kernel (sorry if I make some mistakes with names but I'm really lost....)
so downloaded the ICS and with my surprise it was installed into the phone.
From that moment the N7000 hang at samsung logo with the yellow triangle....
And the worst thing It goes in download mode but not in recovery mode.....
I tried to read many post before write, trying to understand waht to do but now I'm totally confused..... md5,tar,img, zip...... kernel,root, cwm., rom ....
Someone may explain to me if there is something to do to save the phone?
Thanks i n advance
Andrea
andrew59it said:
Hello new in this forum.....
The threads I read overwhelmed me.... :cyclops:
I have a N7000 from a friend of mine. It had a dedicated 4.0.4 rom from "3" (italian operator) build IMM76D.XXLRL
I tried to install a new italian rom 4.1.2 via odin but every attempt failed
Unfortunately I ended up into a thread about ICS kernel (sorry if I make some mistakes with names but I'm really lost....)
so downloaded the ICS and with my surprise it was installed into the phone.
From that moment the N7000 hang at samsung logo with the yellow triangle....
And the worst thing It goes in download mode but not in recovery mode.....
I tried to read many post before write, trying to understand waht to do but now I'm totally confused..... md5,tar,img, zip...... kernel,root, cwm., rom ....
Someone may explain to me if there is something to do to save the phone?
Thanks i n advance
Andrea
Click to expand...
Click to collapse
so, what is your question actually??
Mate, I think the question is simple.
From what I understand in your comment, it seems you tried to install the Stock Rom 4.1.2 Italy, when you were the 4.0.4 / 4.0.3 Stock Rom Italy. On installation through ODIN pc you had a problem where it remains in the Samsung logo, will not let you enter the Recovery mode, only the Download mode. Is that so?
I should arrived that case do not leave any triangle would remove the battery, and after 10-15 seconds reintroduce it, and just then press buttons to enter the Recovery mode. If it fails, repeat the removal of the battery, but now when placed connect the DC charger to the phone I tried to turn normally to 20-25 seconds (just outside and away the logo of battery charging), and try to turn it on Recovery mode again, but we will keep down so long that should disappear all as to turn it off, and you press the keys for the Recovery mode, this time releasing anything else lighting appear on the screen, just a moment before letters GT-N7000, now if it really is accessible Recovery should apparate.
If you enter Recovery Mode Stock Samsung, you will have look out if a line appears below indicating the application, or wondering whether to apply the new CSC, we accept without thinking, since it must reaffirm the phone to initiate a Stock Rom.
Now if I come to this moment really was not accessible Recovery mode should get a screenshot of ODIN pc which finishes entering files to mobile, if it were really a fault, and do not leave do the installation, if you checked any box incorrectly, of which are not activated.
Other options include USB cable failure, USB port, lack of USB debugging enabled before starting the installation, do not put at least 10 minutes in the backlight time (this can try to fix running a finger across the screen every 23 seconds if it was 30 seconds off), but that the capture can determine ourselves if the error is only for ODN pc, which can be a failed in the installation and have not really finished the installation, in this case it would be almost insurance problem USB cable used, and in extremis or USB port.
fusionero said:
Mate, I think the question is simple.
From what I understand in your comment, it seems you tried to install the Stock Rom 4.1.2 Italy, when you were the 4.0.4 / 4.0.3 Stock Rom Italy. On installation through ODIN pc you had a problem where it remains in the Samsung logo, will not let you enter the Recovery mode, only the Download mode. Is that so?
I should arrived that case do not leave any triangle would remove the battery, and after 10-15 seconds reintroduce it, and just then press buttons to enter the Recovery mode. If it fails, repeat the removal of the battery, but now when placed connect the DC charger to the phone I tried to turn normally to 20-25 seconds (just outside and away the logo of battery charging), and try to turn it on Recovery mode again, but we will keep down so long that should disappear all as to turn it off, and you press the keys for the Recovery mode, this time releasing anything else lighting appear on the screen, just a moment before letters GT-N7000, now if it really is accessible Recovery should apparate.
If you enter Recovery Mode Stock Samsung, you will have look out if a line appears below indicating the application, or wondering whether to apply the new CSC, we accept without thinking, since it must reaffirm the phone to initiate a Stock Rom.
Now if I come to this moment really was not accessible Recovery mode should get a screenshot of ODIN pc which finishes entering files to mobile, if it were really a fault, and do not leave do the installation, if you checked any box incorrectly, of which are not activated.
Other options include USB cable failure, USB port, lack of USB debugging enabled before starting the installation, do not put at least 10 minutes in the backlight time (this can try to fix running a finger across the screen every 23 seconds if it was 30 seconds off), but that the capture can determine ourselves if the error is only for ODN pc, which can be a failed in the installation and have not really finished the installation, in this case it would be almost insurance problem USB cable used, and in extremis or USB port.
Click to expand...
Click to collapse
Thanks to reply.....
I was not really clear probably.
I tried to install 4.1.2 over 4.0.4 dedicate rom (3 H3G italian operator)
Odin always failed hanging or giving some fault
So I installed the ICS kernel (or rom) everything was fine. So I suppose the cable is ok , odin is ok etc....
But from the moment I downloaded the ICS, at reboot the phone hang on samsung logo with yellow triangle. ANd if I try to switch off the phone it restart and hang on logo.
Download mode is still working but recovery mode not.....
I'm looking for some kernel, rom, cwm to download, to recover the phone.....
The best thing to do is reinstall the ROM 4.1.2 (the 4.0.x are more dangerous if we wipes, JellyBean when they are not), but check that no error appears, if it appears only after installing the Rom rather fails during it, you can download the kernel Philz for you version, right now if you tell me the link to SamMobile I can tell you what, so you can tell which is correct, although it is not hard to tell if you look at the post of Philz above kernel with all links to them. After installation and download the kernel, you turn the phone into Recovery mode, you select mount usb (I think it came out well, but stresses) and connect your phone to your pc, you can pass the kernel to the internal SD and another copy to the SD external (remember to leave both copies at the root of both SD's). You MUST complete the transfer and disassemble with the option displayed on screen, and disconnect the USB cable. You continue by going to install zip, and should be able to select the Kenel Philz to install, after installing (if you get an error: Status 7 quiet, it was not the correct version of the kernel, and not actually installed), you will have to restart the mobile again, but when you start on with the letters GT-N7000, you will have to restart it by pressing Vol + - Power - Home, all at once, and keep it until the letters again, and keep it until it goes - restart, then you press the 3 keys, and when the letters appear, you must drop the 3 keys, and should you appear the menu Recovery kernel Phliz, there as you will see below something that says CSC implemented or instead ask if you want to apply, accept if you ask, and you should be able to restart the phone and wait about 5 minutes maximum to emit sound and vibration as it is booting at all, and then you should be able to start getting bills from Samsung and Google.
Thank fusionero
the problem is I'm not able to install the 4.1.2 , odin hang or fail
The ROM version I need is
sammobile.com/firmwares/download/22314/N7000XXLT9_N7000ITVLT3_ITV
So I think nex step is to install kernel Philz but I don't know which version I need. On the phone was installed 4.0.4 build IMM76D.XXLRL
CIAO
You must enter this http://www.sammobile.com/firmwares/download/22314/N7000XXLT9_N7000ITVLT3_ITV.zip/ address, and you must connect to you account to download that version you mention, I just check and this downloading smoothly on my pc . The problem is that it would open without ending .zip or you caught hours of server failure, just that i found this morning when downloading another who asked me.
As to what you mention about the version you have installed, as you are looking at the correct thread ( http://forum.xda-developers.com/showthread.php?t=1901191 ), the kernel you need for what you indicate ( 4.0.4 build IMM76D.XXLRL CIAO ) is this:
Update to all ICS 4.0.4 kernels from 3.71 ---> 3.99:
http://www.mediafire.com/?3ale6m9q6b6a3
Updated kernels list:
PhilZ-cwm6-BULR1-SWC-v3.99
PhilZ-cwm6-DDLR6-ODD-v3.99
PhilZ-cwm6-DDLR9-INU-v3.99
PhilZ-cwm6-DDLRB-ODD-v3.99
PhilZ-cwm6-DXLP9-OLB-v3.99
PhilZ-cwm6-DXLR2-OLB-v3.99
PhilZ-cwm6-DXLR5-OLB-v3.99
PhilZ-cwm6-JPLPD-OJP-v3.99
PhilZ-cwm6-JPLR8-OJP-v3.99
PhilZ-cwm6-UBLPC-UUB-v3.99
PhilZ-cwm6-UBLR3-PSN-v3.99
PhilZ-cwm6-UBLR5-TCE-v3.99
PhilZ-cwm6-XXLPY-XEN-v3.99
PhilZ-cwm6-XXLQ3-OXX-v3.99
PhilZ-cwm6-XXLRG-DBT-v3.99
PhilZ-cwm6-XXLRI-AUT-v3.99
PhilZ-cwm6-XXLRK-XEU-v3.99
PhilZ-cwm6-XXLRL-HUI-v3.99 - Is this your kernel
PhilZ-cwm6-XXLRQ-DBT-v3.99
PhilZ-cwm6-XXLRT-DBT-v3.99
PhilZ-cwm6-XXLRU-VDI-v3.99
PhilZ-cwm6-XXLRW-SFR-v3.99
PhilZ-cwm6-ZSLPF-OZS-v3.99
PhilZ-cwm6-ZSLPM-OZS-v3.99
PhilZ-cwm6-ZSLPN-OZS-v3.99
Click to expand...
Click to collapse
andrew59it said:
Hello new in this forum.....
The threads I read overwhelmed me.... :cyclops:
I have a N7000 from a friend of mine. It had a dedicated 4.0.4 rom from "3" (italian operator) build IMM76D.XXLRL
I tried to install a new italian rom 4.1.2 via odin but every attempt failed
Unfortunately I ended up into a thread about ICS kernel (sorry if I make some mistakes with names but I'm really lost....)
so downloaded the ICS and with my surprise it was installed into the phone.
From that moment the N7000 hang at samsung logo with the yellow triangle....
And the worst thing It goes in download mode but not in recovery mode.....
I tried to read many post before write, trying to understand waht to do but now I'm totally confused..... md5,tar,img, zip...... kernel,root, cwm., rom ....
Someone may explain to me if there is something to do to save the phone?
Thanks i n advance
Andrea
Click to expand...
Click to collapse
Your phone is not booting since you flashed an ICS kernel over a JellyBean ROM
Android ICS version : 4.0.4
Android JB version : 4.1.2
so I hope you understand the difference.
You are lucky you didn't brick your device or have you already
But since you are able to go in download mode I think its not bricked yet.
It was probably a bad download which failed the installation so download ROM again and this time verify that your download is not corrupt by running it via md5 if provided.
also please provide the link of the ROM thread that you are trying to install so that I can understand better
and if you are not looking to flash a custom ROM or rooting your device in order to do so then in that case the steps are pretty straight forward
download Stock ROM
extract ROM
open Odin
select appropriate files i.e Choose CODE in PDA, MODEM in PHONE, Multi CSC in CSC
put phone in download mode and connect
the bar should turn yellow once connected.
once connected click on flash
bar should turn green if successful
REVENGE SOLVES EVERYTHING
tysonraylee said:
Your phone is not booting since you flashed an ICS kernel over a JellyBean ROM
Android ICS version : 4.0.4
Android JB version : 4.1.2
so I hope you understand the difference.
You are lucky you didn't brick your device or have you already
But since you are able to go in download mode I think its not bricked yet.
It was probably a bad download which failed the installation so download ROM again and this time verify that your download is not corrupt by running it via md5 if provided.
also please provide the link of the ROM thread that you are trying to install so that I can understand better
and if you are not looking to flash a custom ROM or rooting your device in order to do so then in that case the steps are pretty straight forward
download Stock ROM
extract ROM
open Odin
select appropriate files i.e Choose CODE in PDA, MODEM in PHONE, Multi CSC in CSC
put phone in download mode and connect
the bar should turn yellow once connected.
once connected click on flash
bar should turn green if successful
REVENGE SOLVES EVERYTHING
Click to expand...
Click to collapse
Thanks everyone....
I think you hit the problem..... but my original ROM version was 4.0.4 .... (H3G)
Anyway probably something went wrong.... I don't need a custom ROM or to root the device.
I need to install N7000XXLT9_N7000ITVLT3_ITV if possible but the flash doesn't start via ODIN
May you explain step by step what have I to do? I really appreciate....
What do you mean "select appropriate files i.e Choose CODE in PDA, MODEM in PHONE, Multi CSC in CSC" ?
md5 is not a single file? I read something about more files to place in odin.....
@ fusionero: I already downloaded the files.... also PHILZ XXLRL but the device doesn't start anyway.....
andrew59it said:
Thanks everyone....
I think you hit the problem..... but my original ROM version was 4.0.4 .... (H3G)
Anyway probably something went wrong.... I don't need a custom ROM or to root the device.
I need to install N7000XXLT9_N7000ITVLT3_ITV if possible but the flash doesn't start via ODIN
May you explain step by step what have I to do? I really appreciate....
What do you mean "select appropriate files i.e Choose CODE in PDA, MODEM in PHONE, Multi CSC in CSC" ?
md5 is not a single file? I read something about more files to place in odin.....
@ fusionero: I already downloaded the files.... also PHILZ XXLRL but the device doesn't start anyway.....
Click to expand...
Click to collapse
Did you download the XXLT9 ROM?? or the ROM that you want to flash ??
if so then it should be a zip file, if you extract that zip file you should have 3 files in it (sometimes only PDA file is present and the other two i.e Modem and CSC are not present, dont worry the PDA file alone is enough)
Open Odin, click on PDA button and select the firmware file with .tar.md5 extension (The firmware file look something like: N7000XXDLJ5_N7000ODDDLI7_INU.tar.md5 Select the one that looks similar to the ROM you downloaded)
and if there are CSC and Modem files then select them by clicking Phone and CSC in Odin accordingly. It will be mentioned in the file name if its a Modem or CSC file
if MODEM_XXXX.tar.md5 then select that file by clicking the PHONE in Odin and if XXXX_CSC_XX.tar.md5 then select it by clicking CSC in Odin
remember that you lose all your data
Then just click flash and it should flash
md5 is a single file and is used to check the integrity of the file you downloaded. Its just used to make sure that the file you downloaded doesnt have any errors or is corrupt. you use the .md5 file and compare it with the md5 of the ROM.zip If it matches then its not corrupted or is a bad download. (.tar.md5 and .md5 are different files as in .tar.md5 is a firmware file and .md5 is a hash file used for integrity check)
Just right-click the rar/zip file and select properties and select the "file hashes" tab and if you downloaded a .md5 open that file by clicking "compare file" in the same tab
.md5 is always provided along with file you downloaded and its size is always in kbs , if its not provided then you cant do the hash check
If you dont have "file hashes" tab after right-clicking and selecting properties of the rar/zip file then you should download and install HashTab to get that option
follow this video for a better understanding https://www.youtube.com/watch?v=Ulz-1UYzHBA
the process is same but you should use your ROM files i.e Italian N7000 files to flash your phone and yes Odin version doesnt matter, you can use any version
Hello
I downloaded N7000XXLT9_N7000ITVLT3_ITV.ZIP
Extracted the file into a folder and had N7000XXLT9_N7000XXLT3_N7000ITVLT3_HOME.tar.md5 (there is also SS_DL.dll)
Tried to flash the md5 file with odin (V.1.85) , but odin returns a fail.....
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXLT9_N7000XXLT3_N7000ITVLT3_HOME.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> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> cache.img
<ID:0/007> NAND Write Start!!
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
andrew59it said:
Hello
I downloaded N7000XXLT9_N7000ITVLT3_ITV.ZIP
Extracted the file into a folder and had N7000XXLT9_N7000XXLT3_N7000ITVLT3_HOME.tar.md5 (there is also SS_DL.dll)
Tried to flash the md5 file with odin (V.1.85) , but odin returns a fail.....
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXLT9_N7000XXLT3_N7000ITVLT3_HOME.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> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> cache.img
<ID:0/007> NAND Write Start!!
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
did you follow the video??
did you select N7000XXLT9_N7000XXLT3_N7000ITVLT3_HOME.tar.md5 by clicking PDA??
REVENGE SOLVES EVERYTHING
Yes of course.....
andrew59it said:
Yes of course.....
Click to expand...
Click to collapse
still odin fails?? even after following the video??
are you using the original cable to flash ??
try plugging the cable into a different usb port and flash
Yes it fails
I will try with another cable and port. But if I flash Philz rom it works.....
andrew59it said:
Yes it fails
I will try with another cable and port. But if I flash Philz rom it works.....
Click to expand...
Click to collapse
after trying that try the solution from this post http://forum.xda-developers.com/showthread.php?p=41844601#post41844601
and also try and follow the thread as people have posted different solutions regarding your problem
Also this would be the extent of help i can provide
if that doesnt work i dont know what will
So please forgive me for not being able to help any further :angel:
maybe you should use odin3 v3.04 or v3.09.
usually i use odin3 v1.8X for multiple file roms but in your case, you have only One-file rom.
---------- Post added at 01:12 PM ---------- Previous post was at 01:09 PM ----------
besides, extract all the files in odin archive and place them in one folder dont just start the odin .exe file directly from the archive.
Hello changed the cable the port and ODIN (ver 3.04)
The same problem..... look at the picture attached....
I'm loosing hope.....:crying:
Thanks to all....
solved the problem!!! WOW! :good::victory:
The solution was to change pc, I went on my girlfriend laptop and everything went smooth as silk.....
Thank you all to supporting me !!
andrew59it said:
Thanks to all....
solved the problem!!! WOW! :good::victory:
The solution was to change pc, I went on my girlfriend laptop and everything went smooth as silk.....
Thank you all to supporting me !!
Click to expand...
Click to collapse
congrats
REVENGE SOLVES EVERYTHING

Categories

Resources