Related
Hi guys.
After my first flash (with success) I had root and all was all right.
But now, I wanted to try litening ROM 2.0, I have to see, that I am not able to flash my device anymore. I tried with odin with 1- and 3-part firmwares,.. only Kernel,..tried with Heimdall, made factory resets thousand times.... after EVERY reboot my SGS2 is in the SAME state since before.
It is a state like I made a special recovery. Installed Apps (after first flash) were gone after every reboot. Token images, ... left....
What can I do now? There has to be a solution I hope ...!?
humphrey74 said:
Hi guys.
After my first flash (with success) I had root and all was all right.
But now, I wanted to try litening ROM 2.0, I have to see, that I am not able to flash my device anymore. I tried with odin with 1- and 3-part firmwares,.. only Kernel,..tried with Heimdall, made factory resets thousand times.... after EVERY reboot my SGS2 is in the SAME state since before.
It is a state like I made a special recovery. Installed Apps (after first flash) were gone after every reboot. Token images, ... left....
What can I do now? There has to be a solution I hope ...!?
Click to expand...
Click to collapse
Hi,
what do u have on Odin display?
because, if you don't kill ALL Kies processes, it's impossible for Odin to connect to your device. (it was the case for me)
Try to kill it with your Windows task manager.
good luck.
keke7442 said:
Hi,
what do u have on Odin display?
because, if you don't kill ALL Kies processes, it's impossible for Odin to connect to your device. (it was the case for me)
Try to kill it with your Windows task manager.
good luck.
Click to expand...
Click to collapse
I forgot to say that here in detail
Odin said PASS (in green) and before klicking start, the correct connection was signed with the yellow COM field.
There is no KIES problem, I killed all KIES processes in TaskManager before.
I discussed this in a lot of forms and nobody could help me yet.
There must be something in my configuration, that makes my SGS2 load a special recovery. (have NO titanium backup installed!!)
..hm ...
humphrey74 said:
I forgot to say that here in detail
Odin said PASS (in green) and before klicking start, the correct connection was signed with the yellow COM field.
There is no KIES problem, I killed all KIES processes in TaskManager before.
I discussed this in a lot of forms and nobody could help me yet.
There must be something in my configuration, that makes my SGS2 load a special recovery. (have NO titanium backup installed!!)
..hm ...
Click to expand...
Click to collapse
Does it boot? and which kernel/recovery do you have installed? which software were you running before you tried to flash to litening?
I had this problem going from villian to litening. I had to install official genertic samsung firmware to sort it out. After I did that I have had no problems with flashing roms.
Sent from my GT-I9100 using XDA Premium App
Yes, it boots. But always into one same state.
I flashed it with XWKDD_insecure.tar (without repart and without PIT file) and then rooted it with "SuperOneKlick".
My Phoneinfo says:
Kernel_version: 2.6.35.7-I9100XWKDD-CL161513 [email protected]#2
Buildnr: GINGERBREAD.XWKE2
After it, cause I was very happy to have a rooted device, I installed AndroidWall, AdFree, AutoKillerMemory, NoLED and AutorunManager
that´s all I did. additionaly I tried to set up the UAString for the stock browser with commands like about:debug, about:config and about:useragent.
That´s all I can remember.
It looks like on the phone there is something, that ignores all flashed data on booting and loads a backup-state. whereever that could be loaded from .... .
humphrey74 said:
Yes, it boots. But always into one same state.
It looks like on the phone there is something, that ignores all flashed data on booting and loads a backup-state. whereever that could be loaded from ....
No it loads what you have flashed last .
Use Odin and an stock rom KF3 with single part file flash without repartition or pit .
Then start again as your posts just show that you have flashed nothing at all .
That kernel is very very old .
Post where Odin fails and post phone details if it boots .
Follow lightning rom instructions fully .
jje
Click to expand...
Click to collapse
I had the same issue, but solved after flashing the GT-I9100_KE7_insecure.tar.md5 kernel.
I believe there's a link to the kernel in this thread
JJEgan said:
humphrey74 said:
Yes, it boots. But always into one same state.
It looks like on the phone there is something, that ignores all flashed data on booting and loads a backup-state. whereever that could be loaded from ....
No it loads what you have flashed last .
Use Odin and an stock rom KF3 with single part file flash without repartition or pit .
Then start again as your posts just show that you have flashed nothing at all .
That kernel is very very old .
Post where Odin fails and post phone details if it boots .
Follow lightning rom instructions fully .
jje
Click to expand...
Click to collapse
I downloaded the old stock kernel 'I9100XWKF3_Kernel.tar' and flashed it with odin.
Result:
<ID:0/011> Added!!
<ID:0/011> Odin v.3 engine (ID:11)..
<ID:0/011> File analysis..
<ID:0/011> SetupConnection..
<ID:0/011> Initialzation..
<ID:0/011> Get PIT for mapping..
<ID:0/011> Firmware update start..
<ID:0/011> zImage
<ID:0/011> NAND Write Start!!
<ID:0/011> RQT_CLOSE !!
<ID:0/011> RES OK !!
<ID:0/011> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/011> Removed!!
I did it several times. Odin says nothing failed.
After reboot, ..same state!
Phone Details after this:
Kernel_version: 2.6.35.7-I9100XWKDD-CL161513 [email protected]#2
Buildnr: GINGERBREAD.XWKE2
Click to expand...
Click to collapse
You need to flash a full firmware not a kernel .
jje
humphrey74 said:
JJEgan said:
I downloaded the old stock kernel 'I9100XWKF3_Kernel.tar' and flashed it with odin.
I did it several times. Odin says nothing failed.
After reboot, ..same state!
Click to expand...
Click to collapse
Download the full KF3 ROM and flash that using ODIN. Then re-do your root. I recommend using CF-Root instead of Superoneclick. It takes the guesswork out.
Click to expand...
Click to collapse
OK, I downloaded the full KF3 ROM and flashed it with Odin.
Finished with PASS.
No change anfter reboot.
As I said in my first post, I can flash what I want .... device boots up into the same state, as I did flash nothing!
I flashed FULL firmwares, rooted kernels ... etc..
Nothing happens
Download XXKG2 from here
http://forum.xda-developers.com/showthread.php?t=1174161
and flash the 3 file version (wipe version)
OK i did flash the 3-parted KG2 exactly like the instructions say.
Odin says:
<ID:0/011> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_I9100XXKG2_CL375027_REV02_user_low_ship.tar.md5 is valid.
<OSM> MODEM_I9100XXKG2_REV_02_CL1037208.tar.md5 is valid.
<OSM> GT-I9100-CSC-HOME-MULTI-OXAKG2.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/011> Odin v.3 engine (ID:11)..
<ID:0/011> File analysis..
<ID:0/011> SetupConnection..
<ID:0/011> Initialzation..
<ID:0/011> Get PIT for mapping..
<ID:0/011> Firmware update start..
<ID:0/011> boot.bin
<ID:0/011> NAND Write Start!!
<ID:0/011> Sbl.bin
<ID:0/011> param.lfs
<ID:0/011> zImage
<ID:0/011> factoryfs.img
<ID:0/011> data.img
<ID:0/011> hidden.img
<ID:0/011> cache.img
<ID:0/011> modem.bin
<ID:0/011> Transmission Complete..
<ID:0/011> Now Writing.. Please wait about 2 minutes
<ID:0/011> Receive Response form LOKE
<ID:0/011> cache.img
<ID:0/011> RQT_CLOSE !!
<ID:0/011> RES OK !!
<ID:0/011> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/011> Removed!!
<ID:0/003> Added!!
As I said .... after reboot thy phone is in same state!!
And now you professionals it´s your turn...
Does it boot straight to OS after flash?
or does it load up recovery (formatting /cache updating media and other stuff)?
omrij said:
Does it boot straight to OS after flash?
or does it load up recovery (formatting /cache updating media and other stuff)?
Click to expand...
Click to collapse
It boots straight to OS after flash. EVERYTIME
hi there
Im not a developer, just a simple user, if were u, these r the tricks that I will play
1- change the usb port
2- restart the computer
3- change the computer
4- uninstall kies and install the independant drivers
5- finally, if all failed, ill wait from kies to do the system update for me, this will give u a fresh start over
hope this would help
drreality said:
hi there
Im not a developer, just a simple user, if were u, these r the tricks that I will play
1- change the usb port
2- restart the computer
3- change the computer
4- uninstall kies and install the independant drivers
5- finally, if all failed, ill wait from kies to do the system update for me, this will give u a fresh start over
hope this would help
Click to expand...
Click to collapse
hey
- I changed the USB port
- I restarted the computer very often
- I tried with other computer
- I tried update with KIES
No other result than it boots into same state
Factory reset after flash?
Yes, I did this too. And not only once ...
No change happens
I followed the instructions on (youtube DOT com SLASH watch?v=SpHZ2n9lTcs) this YouTube video to install CyanogenMod on my AT&T Galaxy S4. I flashed the CWM using Recovery Tools, then when it rebooted it wouldn't boot into recover (it would say "System software not authrized by AT&T") so I downloaded Odin and tried flashing it from there but I get the following messages:
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
On the phone screen is the Download mode page with the message at the top
start[224,1440]
secure magiccode check fail : recovery
Could someone please help me complete the installation or at least revert back to stock? I can't use my phone at all now
leaf68 said:
I followed the instructions on (youtube DOT com SLASH watch?v=SpHZ2n9lTcs) this YouTube video to install CyanogenMod on my AT&T Galaxy S4. I flashed the CWM using Recovery Tools, then when it rebooted it wouldn't boot into recover (it would say "System software not authrized by AT&T") so I downloaded Odin and tried flashing it from there but I get the following messages:
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
On the phone screen is the Download mode page with the message at the top
start[224,1440]
secure magiccode check fail : recovery
Could someone please help me complete the installation or at least revert back to stock? I can't use my phone at all now
Click to expand...
Click to collapse
@leaf68 I'm guessing that u are on either MF3 or MK2,since u bricked trying to flash CWM recovery.Try flashing these via ODIN MF3.tar or u can follow my latest MK2.tar.Check post#2 for guide on how to.....GOODLUCK......:good::good:
ted77usa said:
@leaf68 I'm guessing that u are on either MF3 or MK2,since u bricked trying to flash CWM recovery.Try flashing these via ODIN MF3.tar or u can follow my latest MK2.tar.Check post#2 for guide on how to.....GOODLUCK......:good::good:
Click to expand...
Click to collapse
Thank you very much for your response. Right before you posted this, I plugged my phone into my laptop and despite doing this multiple dozen times, it actually booted out of nowhere. Thanks again and I'll hold on to the files in case I need them in the future
yes!
Finally got personal!
It was my USB cable that changed with the Moto X and now worked (S4 Cable sucks anyway!)
Who have some problem there are several possibilities! Do the following.
Test all kinds of Odin, but before connecting first add the file;
If you get caught try to install a recovery may be the "philz_touch_6.44.8-jflte.tar.md5" or "openrecovery-TWRP-2.7.1.0-jfltexx.tar";
If you do not give change the USB port of your PC;
If it persists, replace the USB cable;
That's what I did and it worked guys because of USB CABLE! kkkkkk
have the same problem bro is your phone ok now what did you do?
diogomitsuda said:
Finally got personal!
It was my USB cable that changed with the Moto X and now worked (S4 Cable sucks anyway!)
Who have some problem there are several possibilities! Do the following.
Test all kinds of Odin, but before connecting first add the file;
If you get caught try to install a recovery may be the "philz_touch_6.44.8-jflte.tar.md5" or "openrecovery-TWRP-2.7.1.0-jfltexx.tar";
If you do not give change the USB port of your PC;
If it persists, replace the USB cable;
That's what I did and it worked guys because of USB CABLE! kkkkkk
Click to expand...
Click to collapse
I can vouch. It's the cable and the port. Try switching ports between failed flashes. I guarantee you it will eventually work. It's really sensitive.
Hello, I accidentally deleted my systems folder. I was trying to overwrite one file but apparently it deleted my entire system folder, now I cannot use recovery. If I try to go into recovery mode i get "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again."
I tried downloading Kies and updating it through that but I then get the error "the device's version cannot be updated." I have updated KIES to the newest firmware and still get the error.
I have tried adb pushing but my device is unrecognized and does not fully connect to my computer (Kies will just be stuck at "Connecting...")
I have tried installing a stock rom back with odin (ran as administrator), but odin gives me the error:
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
So it seems I have tried pretty much everything so far with no avail, may someone please help me? I am really stressed out and confused at all these errors.
titaniums4 said:
Hello, I accidentally deleted my systems folder. I was trying to overwrite one file but apparently it deleted my entire system folder, now I cannot use recovery. If I try to go into recovery mode i get "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again."
I tried downloading Kies and updating it through that but I then get the error "the device's version cannot be updated." I have updated KIES to the newest firmware and still get the error.
I have tried adb pushing but my device is unrecognized and does not fully connect to my computer (Kies will just be stuck at "Connecting...")
I have tried installing a stock rom back with odin (ran as administrator), but odin gives me the error:
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
So it seems I have tried pretty much everything so far with no avail, may someone please help me? I am really stressed out and confused at all these errors.
Click to expand...
Click to collapse
I managed to fix this! WOW was this such a headache!
after a long time researching, I found out the 4.4.2 update has some sort of updated bootloader that will not let you install older firmware. So I downloaded the 4.4.2 stock rom from www sammobile com
After you download that, i ran it with odin 1.09 and it installed.
My phone went into some weird loop where the samsung logo would come out for 1 second then my phone would vibrate every 2 seconds and not turn on... great another wall...
After more research i found out it could have been a power button issue, luckily it wasnt this, someone had mentioned that if you go into download mode and hold down the power button until your phone reboots you can get out of this "glitch". So this got me out of the glitch and my s4 started up normally!
Right now I am back to stock, I hope this helps out anyone who encounters something similar!
titaniums4 said:
Hello, I accidentally deleted my systems folder. I was trying to overwrite one file but apparently it deleted my entire system folder, now I cannot use recovery. If I try to go into recovery mode i get "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again."
I tried downloading Kies and updating it through that but I then get the error "the device's version cannot be updated." I have updated KIES to the newest firmware and still get the error.
I have tried adb pushing but my device is unrecognized and does not fully connect to my computer (Kies will just be stuck at "Connecting...")
I have tried installing a stock rom back with odin (ran as administrator), but odin gives me the error:
Initialzation..
Get PIT for mapping..
Firmware update start..
sbl2.mbn
NAND Write Start!!
sbl3.mbn
rpm.mbn
aboot.mbn
FAIL! (Auth)
All threads completed. (succeed 0 / failed 1)
So it seems I have tried pretty much everything so far with no avail, may someone please help me? I am really stressed out and confused at all these errors.
Click to expand...
Click to collapse
I think u should download new firmware from sammobile (because sometimes some firmware corrupted) and try different pc for reflash stock...
Sent from my GT-I9500 using XDA Premium 4 mobile app
fleming.patel said:
I think u should download new firmware from sammobile (because sometimes some firmware corrupted) and try different pc for reflash stock...
Sent from my GT-I9500 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
thanks for the reply, however i already fixed this!
titaniums4 said:
I managed to fix this! WOW was this such a headache!
after a long time researching, I found out the 4.4.2 update has some sort of updated bootloader that will not let you install older firmware. So I downloaded the 4.4.2 stock rom from www sammobile com
After you download that, i ran it with odin 1.09 and it installed.
My phone went into some weird loop where the samsung logo would come out for 1 second then my phone would vibrate every 2 seconds and not turn on... great another wall...
After more research i found out it could have been a power button issue, luckily it wasn't this, someone had mentioned that if you go into download mode and hold down the power button until your phone reboots you can get out of this "glitch". So this got me out of the glitch and my s4 started up normally!
Right now I am back to stock, I hope this helps out anyone who encounters something similar!
Click to expand...
Click to collapse
Hey I am also in a similar difficulty. > http://forum.xda-developers.com/galaxy-s4/help/help-firmware-upgrade-encountered-issue-t2821045
Basically read this above, and tell me what you think I should do. One thing I forgot to add is that when I try to flash a Official Firmware via ODIN, my S4 doesn't really do anything then ODIN would say FAILED, and it would have no affect on my S4 because it just stays on the firmware upgrade encountered an issue part.
Hi guys I'm having problems trying to root my note 3, in fact i can't flash anything with odin.
It is a n900w8 from Telcel, with 4.4.2 stock rom.
I tried flashing to root it and tried to flash a custom recovery and nothing.
this is what odin shows:
<ID:0/009> recovery.img
<ID:0/009> NAND Write Start!!
<ID:0/009> FAIL! (Auth)
<ID:0/009>
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
and in the phone it shows in red letters : Secure check fail : recovery
I already checked the reactivation lock, and it isn´t checked.
Do you have an idea of what could it be?
If you need another info pleas tell me, i would appreciate any help thanks
1. Reinstall the Samsung's drivers.
2. Try other USB cable/port.
3. Take a look if you are flashing the latest firmware for your device. Latest is: HERE.
Joku1981 said:
1. Reinstall the Samsung's drivers.
2. Try other USB cable/port.
3. Take a look if you are flashing the latest firmware for your device. Latest is: .
Click to expand...
Click to collapse
thanks for the answer but i didn´t work , I can flash that rom but only that. I tried to flash the root and the same error.
Evening fellas!
I hope i can get some help over because i am freaking out!
Let me start with what i wanted to achieve. I wanted to go and use Stuff on my phone which wasnt usable due to the SafetyNet API, because i got a custom firmware and root Access. I tried to flash Magisk but it doesnt worked, neither did my SuperSU proberly.
My idea was to unroot and then simply flash the stock firmware via Odin on my phone. 1st couple of tries it didnt work. However, it also didnt affect my phone at all. So i then went into my recovery (TWRP) and did factory reset. Just to clean things up. I tried again to flash and yeah, he actually did it! Just with the minor exception that the flasing failed like 3% before its completion and now i got basiclly a white brick. I ve tried numerous times to flash that firmware again, get some other firmware running - I also tried to flash the Stock Rom completly (which also was able to start the flashing just before it failed in the middle).
I dont find any help on the internet, or at least not help that helps me in my specific situation. I honestly dont know what to do else... I do appreciate any help!
Please help me xda-users, you re my last hope!
Did you try using the original USB cable? Tried different USB ports?
audit13 said:
Did you try using the original USB cable? Tried different USB ports?
Click to expand...
Click to collapse
Yes, i just did. I ve used several USB Ports of my Computer (Haven't tried another computer yet, but that will come too). I also used two different cables. One Original and one third-party cable from amazon, which worked just fine for normal file copying and moving, on the S4 before its brick and the Samsung Grand Prime as well (as i use that in the mean time).
As from yesterday at some random points i was still able to get to flash something for just a second or so, the only messages i get from odin today are these:
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> FAIL! (DeviceInfo)
<OSM> All threads completed. (succeed 0 / failed 1)
I dont find any helpful information on that error message either, which is the worst part of it all.
Is Odin assigning a COM port to the phone?
audit13 said:
Is Odin assigning a COM port to the phone?
Click to expand...
Click to collapse
Yes, everything is detected. Odin is detecting the Samsung Grand Prime just as well as the Galaxy S4. I've also tried different version of Odin. v3.12.3 and v3.13.1. They both give me the same output.
During the initalization phase, Odin is trying to communicate with the phone and is not able to do so.
What about Odin 3.07 with Win7?
Thread moved to Help & Troubleshooting.
audit13 said:
During the initalization phase, Odin is trying to communicate with the phone and is not able to do so.
What about Odin 3.07 with Win7?
Click to expand...
Click to collapse
I ve been using Windows 7 all the time, but now i also tried it with Odin v3.07 and look there: It actually worked! I was able to flash the Stock Firmware, i downloaded days ago, on the phone.
But i still have some problems. As i had the stock firmware running everything seemed to work just fine. At first some google processes repeatedly stopped all the time, but i got that fixed after a factory reset. But i wasnt able to get any google Service running even though i was logged in successfully. It seemed like it was working, but i got fooled. So i tried to flash the whole stock rom and thats where the fun begins all over again.
With using Odin v3.07 i set the files for the Bootlader(BL), PDA(AP),Phone(CP) and CSC but it wont work. Here's the Odin log:
<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!!
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
vM44tze said:
I ve been using Windows 7 all the time, but now i also tried it with Odin v3.07 and look there: It actually worked! I was able to flash the Stock Firmware, i downloaded days ago, on the phone.
But i still have some problems. As i had the stock firmware running everything seemed to work just fine. At first some google processes repeatedly stopped all the time, but i got that fixed after a factory reset. But i wasnt able to get any google Service running even though i was logged in successfully. It seemed like it was working, but i got fooled. So i tried to flash the whole stock rom and thats where the fun begins all over again.
With using Odin v3.07 i set the files for the Bootlader(BL), PDA(AP),Phone(CP) and CSC but it wont work. Here's the Odin log:
<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!!
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Okay, i don't know whats wrong now - but now i cant even flash back the stock firmware that worked before with odin v3.07. Odin now says:
<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> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
EDIT: Its not even being detected anymore.
There is no need to split the tar.md5 into 4 parts. In Odin 3.07, you can flash it as a single file in PDA.
You're flashing the latest stock ROM? Is it possible the USB port on the phone is damaged?