Database Develop

[Q] Heimdall does not recognize phone

Good day!
I'm on Win 7 64 bit and did all the procedures here, ran zadig, etc., before I went to download mode and ran Heimdall....
However, after I ran Heimdall and chosen the files the "Start" button on Heimdall is still grayed out so I cannot start the flashing process...
Any help will be highly appreciated.
***Added: have reseached and was even able to flash using odin on my TAB... I need to bring back my TAB to its original DXKM3 firmware and do not have the firmware to use for odin, that's why I'm trying to use heimdall...
***Also tried it on my laptop with the same results...

Lhon0901 said:
Good day!
I'm on Win 7 64 bit and did all the procedures here, ran zadig, etc., before I went to download mode and ran Heimdall....
However, after I ran Heimdall and chosen the files the "Start" button on Heimdall is still grayed out so I cannot start the flashing process...
Any help will be highly appreciated.
***Added: have reseached and was even able to flash using odin on my TAB... I need to bring back my TAB to its original DXKM3 firmware and do not have the firmware to use for odin, that's why I'm trying to use heimdall...
***Also tried it on my laptop with the same results...
Click to expand...
Click to collapse
Uncheck the partition box. Whenever it's grayed out, it means that for one of your options you haven't met the pre-reqs. For example partition requires a PBL, SBL and a recovery file I believe. Error -12 after clicking start refers to a driver issue.

Lets see if I can explain this how I think you're stating it....
Odin and Heimdall are flashing programs. They're only purpose is to write data to your phone.
Unlike, say, the HD2, which has cLK and Magldr for bootloaders and requires the ROM to be written for that bootloader, there are not separate versions for Odin and Heimdall.
It's only a matter of knowing what files need to go where and in which program.
Odin and Heimdall do the exact same thing, only Odin was a leaked software and Heimdall was written specifically for Galaxy S devices.
Hope this helps

btyork said:
Lets see if I can explain this how I think you're stating it....
Odin and Heimdall are flashing programs. They're only purpose is to write data to your phone.
Unlike, say, the HD2, which has cLK and Magldr for bootloaders and requires the ROM to be written for that bootloader, there are not separate versions for Odin and Heimdall.
It's only a matter of knowing what files need to go where and in which program.
Odin and Heimdall do the exact same thing, only Odin was a leaked software and Heimdall was written specifically for Galaxy S devices.
Hope this helps
Click to expand...
Click to collapse
Okay, I'll try the partition part and see if it works, but I beleive it's not checked as I put no file in it... As for the second post, yes, I have found the firmware I need but it's extracted and not in tar form... That's why I need heimdall...
Maybe if somebody can point me on how to compile it to TAR again I'll just use odin...
***Added: I got my hands on a DXKM3 firmware that came with my phone here. Now if someone can help me put those files again in the TAR format I would be very glad... Getting heimdall to work would, too...
Thanks for the replies!!!

You're right!!! I failed to notice that factory.rfs is not yet extracted, and "Start" magically became selectable!!!
I feel kinda stupid... T_T
Was able to flash now... Thanks for the help guys!!!

Flashing in Odin always fail - no recovery

So I know I am not perfect at this, but I also am not new at it. I have reached an impass and am reaching out to the vast experience that is XDA. I was running on GB just fine and decided to flash a new kernel through SGS kernel flasher, bootloop, couldn't for the life of me get into recovery. So when I got home I tried to flash a new kernel through Odin, fail. Anything else I try to flash now fails. I don't know what to do or try, I can still get into dl mode, but definetly not recovery or even boot up now.
Please help as I don't think samsung will fix it as it is.

Try flashing with EZbase. Its a preconfigured set of files for flashing in EZodin. Meant specifically for recovery
http://forum.xda-developers.com/showthread.php?t=991792&highlight=ezbase

Kops said:
Try flashing with EZbase. Its a preconfigured set of files for flashing in EZodin. Meant specifically for recovery
http://forum.xda-developers.com/showthread.php?t=991792&highlight=ezbase
Click to expand...
Click to collapse
It is still failing to flash even through EZBase. Usually as soon as Firmware update starts it says Complete(write) operation fail.

Have you tried flashing with sd and sim removed?
GTi9000 insanity cm012/glitch

slaphead20 said:
Have you tried flashing with sd and sim removed?
GTi9000 insanity cm012/glitch
Click to expand...
Click to collapse
Still nothing but fail

Maybe try an older or newer version of Odin depending on what version your using, or try Heimdall. And try re-downloading all the files including odin, they maybe corrupt?And lastly try reinstalling the USB drivers. Hope something there works

Shrapnel2 said:
Maybe try an older or newer version of Odin depending on what version your using, or try Heimdall. And try re-downloading all the files including odin, they maybe corrupt?And lastly try reinstalling the USB drivers. Hope something there works
Click to expand...
Click to collapse
+1
agreed! best advice.
Leave battery out for 5-10 mins, redownload files as suggested, install on pc, odin 3.1 shouldn't present you with any problems so try that.
If you're getting into dl mode you WILL be able to flash.

J 3 M said:
+1
agreed! best advice.
Leave battery out for 5-10 mins, redownload files as suggested, install on pc, odin 3.1 shouldn't present you with any problems so try that.
If you're getting into dl mode you WILL be able to flash.
Click to expand...
Click to collapse
Ok i have been trying odin 1.7 and ezbase maybe i will get odin 3.1
Edit: whoa where can i find odin3.1

Odin failure may suggest a faulty USB port or USB cable,try using a different port to flash n if that does not work a different cable.. and it's also a possibility that the downloaded rom may be corrupted so download a new clean stock rom from SamFirmware.com ..hope this solves your issue!!
Sent from my GT-I9000 using XDA Premium App

doomsdaycs said:
Odin failure may suggest a faulty USB port or USB cable,try using a different port to flash n if that does not work a different cable.. and it's also a possibility that the downloaded rom may be corrupted so download a new clean stock rom from SamFirmware.com ..hope this solves your issue!!
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
Well i did try to just flash a pit file and it worked. Also i tried different files and none worked.

So i think its toast. It wont charge and its deadnso no more dl mode. Thanks you all for your attempt at help for my sirry ass.
Edit: got it going by leaving the battery out for a while. Still no charging available though.

joelhon said:
Ok i have been trying odin 1.7 and ezbase maybe i will get odin 3.1
Edit: whoa where can i find odin3.1
Click to expand...
Click to collapse
use ezodin, which comes with the ezbase rom, read the instruction thoroughly, it is wonderfully simple....another classic from Nitr8.....and let me know how you get on......ezbase has full graphic walkthrough instructions too atb

slaphead20 said:
use ezodin, which comes with the ezbase rom, read the instruction thoroughly, it is wonderfully simple....another classic from Nitr8.....and let me know how you get on......ezbase has full graphic walkthrough instructions too atb
Click to expand...
Click to collapse
Sorry i meant that i tried ezodin and still it failed to flash.

So update time. I tried to flash jg8 jpu and jh2 all no luck. I even tried to flash just a bootloader and it failed as well. I really dont know anymore.

did you check the green confirmation screen in Odin and/or ezflash? if there is not confirmation that the application has found your device at the appropriate com port the flash won't work

klinggalaxy said:
did you check the green confirmation screen in Odin and/or ezflash? if there is not confirmation that the application has found your device at the appropriate com port the flash won't work
Click to expand...
Click to collapse
I think you meant yellow?
GTi9000 insanity cm012/glitch

I would ignore ezbase and flash jm9. If you have tried to change kernel with lagfix on, then you will need jm9. I recommend odin 1.7.
I have been in some sorry states with my phone, jm9 has always resolved any problem, even when ezbase has failed.
Sent from my GT-I9000 using XDA Premium App

klinggalaxy said:
did you check the green confirmation screen in Odin and/or ezflash? if there is not confirmation that the application has found your device at the appropriate com port the flash won't work
Click to expand...
Click to collapse
Really, are you kidding me? Do you not see my signature? Don't you think maybe I have done this a FEW times? I don't mean to be harsh, but seriously! That would be like saying make sure your computer is on before you try and flash. Make sure you take you pants down to have a sh*t. WOW! I am just a little tense and on edge right now so stupid comments are really not too appreciated. Plus it wouldn't even run if Odin didn't see your device. OMG!
UPDATE: Nothing was working so it is back to the store to have a look, fingers crossed they don't claim water damage or voided warranty for other reasons and want to charge me out the ass to fix it. Gotta love loaner phones, it's like being in the stone age.

[Q] When odin one click doesnt work...

so my dilemma is as follows.. i was running continuum 4.1 on my captivate. i decided i wanted to try one of the new gingerbread roms, so my first step was to use odinoneclick 1.0 to get to complete stock and go from there. my luck, odin froze on me at sbl.bin... so i am soft bricked but i can use the vol up/down plug usb method to get to download mode. because i have only used one click before, and not a full odin like 1.7, i am having trouble figuring out exactly what i need, and what steps are necessary to safely get me back to stock using odin 1.7 so i can then load GB bootloaders and stop messing with BL's from now on.. so i suppose my main question is should i first flash eclair before trying to flash GB bootloaders/rom? my other question being, if so, what files do i need, and do i need to place a pit file and repartition? sorry if this is a noob question, i just dont want to screw it up any further and wasnt sure if specific steps must be taken when you are soft bricked.. thanks very much in advance!

No need to flash Eclair. Just flash the KF1 file in this post and then XCal's reorient for GB and you'll be good to go. Just don't boot into the OS after flashing XCal's kernel else you'll get bootloops since it was designed for I9000 based ROMs rather then I897. Just reboot back into recovery after flashign XCal's Kernel and then flash whatever GB ROM you want.
http://forum.xda-developers.com/showthread.php?t=1126704
I personally prefer to flash my phone using Heimdall on my laptop running Kubuntu as it's generally more stable/successful, and it's easier to choose which files you want to flash if you only want to flash specific files (Like the bootloaders).
Also KH3 is out and it looks like it might have updated bootloaders, but it's not a full ROM from what I was able to grab. It's missing the param.lfs, dbdata.rfs, and the pit file. Also has an added SS_DL.dll which I'm not sure what the purpose of that file is since it's a Windows file...
http://forum.xda-developers.com/showthread.php?t=1232703

Moved to Q&A.....
NO QUESTIONS IN DEVELOPMENT PLEASE!!!!!

conantroutman said:
Moved to Q&A.....
NO QUESTIONS IN DEVELOPMENT PLEASE!!!!!
Click to expand...
Click to collapse
my apologies! my intention was to post in q&a but i was at work sneaking on the pc i must have been clicking too fast..
and kyuta... thank you for the suggestion! so is it safe to just use the whole odin package in the link you provided just to get a clean install, and then move on to a rom/kernel of choice at a later time?

im getting a big red FAIL on every attempt at flashing KF1 file with odin 1.3 and 1.7 im not sure which route to take at this point. do i need to flash the pit file with the bootloaders?

dartdc97 said:
im getting a big red FAIL on every attempt at flashing KF1 file with odin 1.3 and 1.7 im not sure which route to take at this point. do i need to flash the pit file with the bootloaders?
Click to expand...
Click to collapse
just make sure u hav right file downloaded...and right click on odin and click run as administrator...try changing the usb ports....and try changing the usb cable...and see if u hav proper driver installed ....
check all these which i hav mentioned...
then u shd be able to go back to either eclair(jf6) or gingerbread(kf1) stock

killer_raj said:
just make sure u hav right file downloaded...and right click on odin and click run as administrator...try changing the usb ports....and try changing the usb cable...and see if u hav proper driver installed ....
check all these which i hav mentioned...
then u shd be able to go back to either eclair(jf6) or gingerbread(kf1) stock
Click to expand...
Click to collapse
Just to add this this: Try using XP service pack 2 mode if you are using Windows 7 x 64.

[Q] ODIN - Check image files !! Works for others though...

So I've downloaded the following kernels from a link here on XDA that should be swapping kernels to allow me root on my recently upgraded, stock ROGERS 2.3.3 Captivate. Odin is telling me to "Check image files !!" when I load the .tar files into the Select Intergrated Package (and yes, the one package switch is on). I opened the tar to double check it wasn't double-compressed.
What else would be giving me this problem? I'm using Odin 4.28. Curiously, it is showing my phone as detected, my phone IS in downloading mode, but Odin just says (Android) in the Title, no specific model. But it says it's found it on COM 6. <1> Added!! and Detected!!
It's when I load up the kernel tar's and try to start that it yells at me. Is this triggering anything in anyone's mind that I'm doing wrong? Or do I need to provide more info?
I am using Vista 32-bit (legit) on a Dell studioXPS. And I ran it as administrator.

never heard of ODIN 4.28. i think its only up to version 1.82 or so.
sounds like you are using the wrong ODIN

Pirateghost said:
never heard of ODIN 4.28. i think its only up to version 1.82 or so.
sounds like you are using the wrong ODIN
Click to expand...
Click to collapse
Yeah. That is def the wrong version of Odin. Download the i9000 bootloaders in my sig. Unzip it. Delete the pda.tar.md5 file. Use the included version of Odin (1.82 I think) to flash your kernel.

Alright, quick question - I accidentally flashed the phone, not the pda. I tried to flash the KH2 modem back via phone but ODIN failed. Kies is currently not detecting the phone, and so I decided to try flashing the PDA while I had it open and I would figure the modem out after. ODIN hung, so I closed it and rebooted out of downloading mode and got the Phone ! Computer error. So I figure now I have to flash back to the stock rom and start over again, but this time I would like some advice as to which step to take next. I downloaded I896UXKH2-HOMEBINARY.tar.md5 from another thread here. Can I flash this with Odin - and if so, which is the place to load it? Bootloader? PDA? Phone? CSC? I have no PIT files.

Think it goes into the pda slot. Go back to the thread t you got it from and read the first post of the thread. Also restart your computer before trying to flash again.

can someone upload the modem.zip, please thank you

[SOLVED] Repairing bad flash i9000

[SOLVED] Read on to find out how.
For this to work you must be able to access "Download mode" and make sure that your phone is recognized by the computer.
Here's what happened:
Phone was running CM7.2 and Glitch 13.1 and I wanted Slim ICS 4.2 so what I did was: wipe user data, cache and devik cache then installed Slim ICS 4.2 through CWM and it worked.
But when the phone was trying to do the initial install after it had rebooted from flashing Slim in recovery it just restarts and loops, always about to do the initial install.
Got fed up with this and sort of rage flashed back to stock loosely following THESE instructions, but I didn't follow the instructions like I should have. What I did instead was flash my stock JVC gingerbread firmware (Orange of the UK branded) TAR file as PDA with the 20100512 PIT file in Odin3 1.87. And yes I did check "Repartition" in Odin, because the instructions I had for Hemidall said to have repartition "CHECKED".
This is the result, from 3e recovery.
--Installing package...
Finding update package...
Opening update package...
Verifying update package...
Installing update...
assert failed: getprop("ro.product.device") == "GT-P1000" ||
getprop("re.build.product") == "GT-P1000" ||
getprop("ro.product.device") == "GT-i9000" ||
getprop("re.build.product") == "GT-i9000"
E:Error in /cache/recovery/sec_csc.zip (Status 7)
Installation aborted.
So then some poo came out... but I thought if I followed the instructions EXACTLY as they were writtin these problems would all go away and I can go back to not crapping myself
I followed the instructions perfectly and I still get the same screen as written above, in 3e recovery.
So now too scared to touch the phone without some brief guidance, can someone please please help as I'd really like to be able to start testing and benchmarking ICS roms.
Thank you again XDA

You can try flashing with my recovery kit, worth trying, just download it, unzip and read the .txt first, pictorial instructions included
http://db.tt/MOGZx01S
Sent from my GT-I9300 using xda premium

Thank you slaphead20
My only question is: What have I done, and why will ezbase recovery kit for gb fix it?
Before trying ezbase (which is downloading now and will take 22 minutes) should I try flashing to stock like I normally would with Odin where by I just flash the one TAR file in PDA? But if you don't think it will help then I wont touch it until recovery kit gets here :/

Odin can't see the phone, but Hemidall works perfectly... do I have to somehow revert the drivers in Device Manager for Odin to see my phone again?
As you know Hemidall comes with that "Zadig" drivers thing and it was after using this that Odin stopped seeing my phone

mod2max said:
Odin can't see the phone, but Hemidall works perfectly... do I have to somehow revert the drivers in Device Manager for Odin to see my phone again?
As you know Hemidall comes with that "Zadig" drivers thing and it was after using this that Odin stopped seeing my phone
Click to expand...
Click to collapse
You may need to reinstall driver s,, not sure as I don't use heimdall, the kit I sent you is an Odin based kit, will give you a stripped down gb Rom called ezbase, there is a pit file included, and also a cf root kernel, so you should be able to use heimdall
Sent from my GT-I9300 using xda premium

slaphead20 said:
You may need to reinstall driver s,, not sure as I don't use heimdall, the kit I sent you is an Odin based kit, will give you a stripped down gb Rom called ezbase, there is a pit file included, and also a cf root kernel, so you should be able to use heimdall
Click to expand...
Click to collapse
Well it's 2:00AM Sunday morning here in the UK, got home a few moments ago and had a brainwave "Why not use a virtual machine to install the phone's drivers and test Odin" so I did and it works fine I will flash the recovery kit in the morning (even though it is morning... ) and let you know how it goes.

Thought I'd reinstall the drviers on my PC since it worked on the virtual machine, got Odin back
However, I set up the flash as described in EZOdin and it got to HERE and then it got stuck... been stuck for about 20 minutes now.
In the white "Connection" status box in Odin it says "Set Partition"
Phone is still plugged in, haven't seen any progress bars on the phone or any change in Odin, is it safe to remove the phone (Hemidall would say "Hemidall crashed" but is safe to remove the phone)?
UPDATE
Ok so got the phone removed, safely I think...
It's gone a bit funny like it did when Hemidall crashed... so no boot logo or kernel splash etc, just a white picture of a phone and dotted line connection to a pc. But I fixed that by flashing again with exact set up from the instructions for Hemidall, it got logos back and recovery etc.
But can still access download mode and and Odin sees the phone, hope is not lost
Is it worth trying to flash the files in normal Odin3? I have version 1.87. It might be a one off crash (like Hemidall's was) but I crap my self when stuff like this happens and would rather it didn't do it again

mod2max said:
is it safe to remove the phone (Hemidall would say "Hemidall crashed" but is safe to remove the phone)?
Click to expand...
Click to collapse
Its stalled, Its Failed, but you have no option but to disconnect, which means you will be in upgrade mode or BSOD mode after you pull the plug. meaning you have to Flash again using Pit first but before that you need to remove battery, reinsert, best to remove external SD card and Sim card too.
restart odin and plug in usb cable, it might detect straight away for you to flash again

xsenman said:
Its stalled, Its Failed, but you have no option but to disconnect, which means you will be in upgrade mode or BSOD mode after you pull the plug. meaning you have to Flash again using Pit first but before that you need to remove battery, reinsert, best to remove external SD card and Sim card too.
restart odin and plug in usb cable, it might detect straight away for you to flash again
Click to expand...
Click to collapse
Ahhh that must be what it is, upgrade mode :/
Well I got the phone out and download mode still works and Odin can still see the phone, so I'm pretty safe atm (I think.....) battery has already been removed etc.
But while download mode and Odin work I'm not doing more to the phone now, if I carry on I will actually have heart failure. So I will pick this up again later on this afternoon.

xsenman said:
Its stalled, Its Failed, but you have no option but to disconnect, which means you will be in upgrade mode or BSOD mode after you pull the plug. meaning you have to Flash again using Pit first but before that you need to remove battery, reinsert, best to remove external SD card and Sim card too.
restart odin and plug in usb cable, it might detect straight away for you to flash again
Click to expand...
Click to collapse
Could you please explain what you mean by "using Pit first"? I thought pit files go in it's space in Odin at the same time as flashing everything else (when you use Pits of course).
My current plan is, install the usb drivers on a machine that has never been touched by me, Odin or anything else. So maybe this will determine whether it is EZOdin playing up on the latest version of Windows 7... if it's not either of those then I guess that means I am no longer able to flash PIT files and am screwed.
But I will find out, fingered crossed!
Slaphead20, I've taken the PDA, PHONE and CSC files you gave me and would like to flash them in Odin3. I've stripped the files of their ".md5" extensions and now they are just ".tar" but I was wondering if this would have any bad effects while flashing? Does Odin3 take ".md5" files like EZOdin does? Is it safer to leave the files in their ".md5" format?

How it was solved:
I took the "ezbase recovery kit" that was kindly made available to me from Slaphead20 and unpacked the "PDA", "PHONE" and "CSC" .md5 files, I first removed the ".md5" extensions from the end of each file name and then used WinRAR to unload the contents of each ".tar" folder into a normal uncompressed folder for use with Hemidall.
**I did find that while unpacking these files there was two "cache.rfs" files, they are both the same but we just use one when using Hemidall.**
The reason I used Hemidall instead of EZOdin (which is supplied with the recovery kit) or Odin3 is because firstly when I tried to use the recovery kit in EZOdin, it crashed and I had to unplug the phone unwillingly (that caused "Upgrade mode"). And the reason for not using Odin3 was fear of the same.
The process:
**Make sure your handset has plenty of juice cause the last thing you want is a bad flash and then not being able to charge the batter without an external charger.**
Firstly, get your phone into "Download Mode" with the USB cable unplugged from the computer
Set up Hemidall like so...
**Make sure "Repartition" is checked and "No Reboot" is unchecked for this bit!**
Partition ID______Partitions (Files)
____0___________IBL+PBL = boot.bin
____3___________SBL = Sbl.bin
____6___________KERNEL = zImage
____11__________MODEM = modem.bin
____21__________PARAM = param.lfs
____22__________FACTORYFS = factoryfs.rfs
____23__________DBDATAFS = dbdata.rfs
____24__________CACHE = cache.rfs
After the flash is complete the phone will reboot, the first ever boot of the OS is a long one so just be patent and it will eventually (fingers crossed) load.
Q: What is it doesn't load?
A: Flash the above again until it does, or your doing something wrong -_-"
Once the phone has loaded, shut it down and then go back into "Download Mode" with the USB cable unplugged. Now, with Hemidall select the same pit file as before but make sure that "Repartition" and "No Reboot" are both unchecked, then click "Add" and select "Kernel" for the "Partition Name", browse to the "zImage" file in the "CF -Root for EZbase" folder (or similar). Plug the USB cable into the phone, click "Start" and wait for the phone to reboot, then you will have Root (+ SU) and CWM.
**If any flash you make with Hemidall stalls (fails) after you click "Start" and you have to unplug the phone it will now be stuck in "Upgrade Mode" but get into "Download Mode" and follow this guide from the start.**
Thank you Slaphead20 for this one

hi, thx for such an informative insight here...
there should be a sticky thread for such kind of issues and which would get everyone going in quick !
not sure if mods are listening to this
anyways thanks again
Sent from my GT-I9000 using xda app-developers app

Just as a heads up, all credits to
Nitr8 for the ez components
Chainfire for cf kernel
Samsung for pit file
Link to recovery kit, unzip and read.txt
http://db.tt/MOGZx01S
Sent from my GT-I9300 using xda premium

dude, ive had similar problems, due to this thread i was able to fix, and get my phone running. now ive got one small problem left. cwm wont flash. im stuck on 3e recovery, when i try to flash update.zip, it fails, and obviously i cant update to different rom with that. any hints on how to get cwm on it? and how do u generally get cwm when using that recovery pack?

banana_plug said:
dude, ive had similar problems, due to this thread i was able to fix, and get my phone running. now ive got one small problem left. cwm wont flash. im stuck on 3e recovery, when i try to flash update.zip, it fails, and obviously i cant update to different rom with that. any hints on how to get cwm on it? and how do u generally get cwm when using that recovery pack?
Click to expand...
Click to collapse
flash the cf kernel as pda in Odin, no repartition....for crying out loud there's a pictorial guide with screen shots of Odin loaded up....:banghead::banghead::banghead::banghead:
Sent from my GT-I9300 using xda premium

slaphead20 said:
flash the cf kernel as pda in Odin, no repartition....for crying out loud there's a pictorial guide with screen shots of Odin loaded up....:banghead::banghead::banghead::banghead:
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
now guess what? i did flashed CF kernel. guess does it load CWM afterwards? no. 3e recovery loads up instead. it actually failed for the first time (when flashing in ezodin as pda) the second time it was flashed right. but no CWM. was following tutorial step by step. im sure i was doing exactly whats stated in it. any ideas my dear ?

banana_plug said:
now guess what? i did flashed CF kernel. guess does it load CWM afterwards? no. 3e recovery loads up instead. it actually failed for the first time (when flashing in ezodin as pda) the second time it was flashed right. but no CWM. was following tutorial step by step. im sure i was doing exactly whats stated in it. any ideas my dear ?
Click to expand...
Click to collapse
did you flash as a separate step from the ez base flash?
Sent from my GT-I9300 using xda premium

slaphead20 said:
did you flash as a separate step from the ez base flash?
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
dude, youre absolutely right. as a separate step. been through google for hours, untill now its unsolved for me. 3e recovery stays in.

banana_plug said:
dude, youre absolutely right. as a separate step. been through google for hours, untill now its unsolved for me. 3e recovery stays in.
Click to expand...
Click to collapse
try a new download of the kit, no one, and I mean no one, has ever had that before
Sent from my GT-I9300 using xda premium

slaphead20 said:
try a new download of the kit, no one, and I mean no one, has ever had that before
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
yes. you probably understand why im actually posting here. i nearly never post, not because im a techie, im a total noob, its just that im good at research, and i dont like to bother others. but at this point im pretty tired. will go thru the procedure again (third time) and see what happens. ****ing 3e recovery!
p.s correct me, replacing the kernel with CFROOT one from the pack, should automatically flash CWM? if thats the case, i might go and find another kernel with such capabilities, am i on a right path? p.s when i get rich, ill donate to you a beer ;D