Related
I'm putting together a walkthrough of how through much trial and error I came up with, in my opinion, the best way to get Darky's awesome new rom onto our Canadian Galaxy i9000M that is infamous for crashing hard, with the least amount of risk possible.
**this will take a day or two as I have a busy life...just want to help some people in my spare time so don't get mad because I'm only starting with the introduction. **
Short version (From stock i9000M 2.2 JL2):
1. Download:
Darkys rom v8.0
Latest Odin
Speedmod K12O hz=500 (Odin version not CWM!)
Superoneclick root
2. Plug in your phone, enable usb debugging, run oneclickroot, hit root. Wait for everything to finish. Disconnect. Rooted!
3. Reboot download mode. Use Odin to flash only the .tar file from speedmod as the PDA leaving everything else unchecked. Wait for reboot.
4. Put Darkys rom on root of sdcard.
5. Download rom manager from market, flash latest recovery. Reboot recovery using app.
6. Select zip using recovery and apply. Voila! Done!
7. **These are only quick instructions for someone who has basic knowledge of flashing a rom and lacks many minor but VERY important details! If you are unsure of what you are doing or have never done it before do not attempt this!!.
I only posted this because myself and it appears a few others have had a.much less painful experience by first flashing the speedmod kernel before Darkys rom. A detailed instruction for brand new flashers with no experience will follow when I have the time
A more detailed guide is available here:
androidforums.com/galaxy-s-all-things-root/264530-flashing-darky-v9-gt-i9000m-minimal-risk.html
Sent from my GT-I9000 using Tapatalk
Can you elaborate on why you did not choose the latest Darky's ROM?
Sent from my GT-I9000M using XDA App
i can answer that question for you.. look at the date of when he made this post and the dates of Darky's releases... he was using the "lastest" rom at the time he made the post =]
thx
Sent from my GT-I9000M using XDA App
cripez said:
i can answer that question for you.. look at the date of when he made this post and the dates of Darky's releases... he was using the "lastest" rom at the time he made the post =]
Click to expand...
Click to collapse
He made the post recently? Jan 2011?
he made that post in january 17... its now feb 02.
darky released the 9.1 on jan 23rd... before that it was still the 8.0
=]
The SAFEST way to Flash Darky's or any Custom rom would be this order.
1. Flash JL2 , the new .SBL (Secondary Boot Loader) included with JL2 is believed to fix the dreaded internel SD death's that so many of us had.
2.Download latest Darky's Rom and make a folder on your phone name it what ever you want and put the rom in there, you can also leave the rom in downloads if you downloaded it directly to the phone.
3. Flash Hardcores Kernel with ODIN.
4.Boot device into CWM recovery, Root device it's in the advance options.
5. Install Darky's rom , using Install zip from SD method in CWM recovery.
6.done.
Samdroid_G_S said:
The SAFEST way to Flash Darky's or any Custom rom would be this order.
1. Flash JL2 , the new .SBL (Secondary Boot Loader) included with JL2 is believed to fix the dreaded internel SD death's that so many of us had.
2.Download latest Darky's Rom and make a folder on your phone name it what ever you want and put the rom in there, you can also leave the rom in downloads if you downloaded it directly to the phone.
3. Flash Hardcores Kernel with ODIN.
4.Boot device into CWM recovery, Root device it's in the advance options.
5. Install Darky's rom , using Install zip from SD method in CWM recovery.
6.done.
Click to expand...
Click to collapse
if my phone is still with me (currently being thrown around by samsung)
this is the method I would use as well.
Yes this is roughly the method I used. I was nervous but it was pretty easy.
From JL2 stock you basically just need to Odin flash hardcore's kernel and then you can install whatever compatible .zip(s) you want in recovery mode (as well as root or apply tweaks).
I did a doc rom first and since I have updated the kernel and downgraded wifi drivers. No random force closes yet at all, the new board (and JL2 sbl) have my 10.08 unit running flawlessly so far.
Trying not to go too flash crazy. Although some would say to do the opposite and see if the phone will die under warranty, I think the hardware is fine but don't want the pain of trying to recover from messed up flash. So I'm waiting for a significant release before flashing a whole new base.
I just flashed darkys 902 rom and using darkys config picked speedmod (I dont like voodoo). Worked good, but had to flash JL2 modem to get 850 back. I usually run the JL2 modem anyway, just because it seems to give me the best battery life and good GPS.
Samdroid_G_S said:
The SAFEST way to Flash Darky's or any Custom rom would be this order.
1. Flash JL2 , the new .SBL (Secondary Boot Loader) included with JL2 is believed to fix the dreaded internel SD death's that so many of us had.
2.Download latest Darky's Rom and make a folder on your phone name it what ever you want and put the rom in there, you can also leave the rom in downloads if you downloaded it directly to the phone.
3. Flash Hardcores Kernel with ODIN.
4.Boot device into CWM recovery, Root device it's in the advance options.
5. Install Darky's rom , using Install zip from SD method in CWM recovery.
6.done.
Click to expand...
Click to collapse
Hello...just trying to get an understanding before I proceed.
1. I will be receiving a new handset from Samsung. If it already has JL2 with a newer date, do I still need to flash SBL or do the latest phones come out with a fixed SBL?
2. Ok.
3. On these particular Bell phones, is HardCores kernel the best choice or basically install what ever kernel I want to get a feel of what I like?
4. CWM, is it just a different interface or program similiar to stock recovery mode?
Thanks in advance.
Samdroid_G_S said:
The SAFEST way to Flash Darky's or any Custom rom would be this order.
1. Flash JL2 , the new .SBL (Secondary Boot Loader) included with JL2 is believed to fix the dreaded internel SD death's that so many of us had.
2.Download latest Darky's Rom and make a folder on your phone name it what ever you want and put the rom in there, you can also leave the rom in downloads if you downloaded it directly to the phone.
3. Flash Hardcores Kernel with ODIN.
4.Boot device into CWM recovery, Root device it's in the advance options.
5. Install Darky's rom , using Install zip from SD method in CWM recovery.
6.done.
Click to expand...
Click to collapse
Ok, I bought a Bell phone, wanting to use on Rogers, but I didn't realize the severity of this internal sdcard problem.
I'm glad JL2 seems to fix the issue. Currently I'm running Eclair, 2.1.
So 1), Install JL2 as instructed here: http://forum.xda-developers.com/showthread.php?t=853950
3) Install hardcore kernel here: http://forum.xda-developers.com/showthread.php?t=822756
4) Install Darky's rom here: http://forum.xda-developers.com/showthread.php?t=814091
2 Questions:
A) won't running Darky's rom ALSO install SpeedMod's kernel? (and an option for voodoo)? So I can essentially skip step 3? Is there a reason why I'd want to use ODIN?
B)And won't installing Darky's rom Also over write the modem in JL2, thus making unsafe for internal sd again?
(Or does JL2 refer to more than just the modem).
I thought Bell and Rogers use different frequencies, so the phones can't be crossed over.
adamge said:
I thought Bell and Rogers use different frequencies, so the phones can't be crossed over.
Click to expand...
Click to collapse
No, They work fine. Used the Bell Motorola Milestone on Fido for a couple months before changing.
Bell SIM cards can also run on unlocked rogers phones.
evilution said:
2 Questions:
A) won't running Darky's rom ALSO install SpeedMod's kernel? (and an option for voodoo)? So I can essentially skip step 3? Is there a reason why I'd want to use ODIN?
B)And won't installing Darky's rom Also over write the modem in JL2, thus making unsafe for internal sd again?
(Or does JL2 refer to more than just the modem).
Click to expand...
Click to collapse
I think I found my own answers:
A)Once you flash to JL2, you cannot flash CWM reboot recovery.. JL2 runs 3e recovery, but CWM uses 2e.. You'll get an error trying to apply update.zip..
You must use odin to change the kernel. I don't think it matters if you use voodoo or supermod.
B) Darky's rom actually changes the modem and you lose 850. If you want it again, take the JL2.tar file and delete everything except modem.bin.. More details here: http://cloudrainstar.blogspot.com/2010/12/xxjpy-darkys-70-ugjl2-modem-bmcjl2-csc.html
evilution said:
I think I found my own answers:
A)Once you flash to JL2, you cannot flash CWM reboot recovery.. JL2 runs 3e recovery, but CWM uses 2e.. You'll get an error trying to apply update.zip..
You must use odin to change the kernel. I don't think it matters if you use voodoo or supermod.
B) Darky's rom actually changes the modem and you lose 850. If you want it again, take the JL2.tar file and delete everything except modem.bin.. More details here: http://cloudrainstar.blogspot.com/2010/12/xxjpy-darkys-70-ugjl2-modem-bmcjl2-csc.html
Click to expand...
Click to collapse
Thanks for that info. I did not know Darky 's would remove 850 band. It really pays to read through this information thoroughly before proceeding.
Thanks for this guys I was stressing to the max trying to figure out what to do for my Canadian Bell phone. This worked AWESOME!!!
Can't believe how nice Darky's Rom is.
LegendDroid said:
Thanks for this guys I was stressing to the max trying to figure out what to do for my Canadian Bell phone. This worked AWESOME!!!
Can't believe how nice Darky's Rom is.
Click to expand...
Click to collapse
Glad to know you got it working...
Did you have to re-flash jl2 to get band 850?
Yea Rasher I did.
I was getting so brain fried I was trying to flash with ODIN while the phone was still on the home screen....
I finally remembered to put it back into download mode and flashed the JL2 modem back in.
WOW and WOW I can't believe how fast the GPS is.
It was non-existant for me on the stock UGJL2
Thanks again guys
Oh just incase anyone else reads this and forgot to do that, in order to use your phone in BC you will most likely need to do this guys first part of his tutorial on flashing the JL2 MODEM.bin after Darky's ROM.
http://cloudrainstar.blogspot.com/2010/12/xxjpy-darkys-70-ugjl2-modem-bmcjl2-csc.html
This thread has made be a bit confused.
If i have a Bell phone, on the rogers network. What do i need to do? If i flash darky's rom and it gets rid of the 850 band, does that matter?
I accidentally uninstalled Touchwiz using Titanium Backup. Since I already use ADW.Launcher, I thought its not a big deal, until I did a hard reset.
Upon hard reset, my Galaxy S tries to install Touchwiz, which of course fails, and the darn phone just crashes and hangs. I managed to get it to boot up eventually after some trouble, but I'll prefer not to have to do this everytime I hard reset.
Can someone please please send me the TouchWiz apk and odex files so that I can put them back in the system directory ? I'm using stock Froyo 2.2 ( Build FROYO.DXJPA, Kernel 2.6.32.9 ). Please email them to [email protected], or tell me where I can download them.
I know this would cease to be a problem if I just flash a custom rom, and I would love to try that in future, but not now.
Thanks so much in advance.
Easy way would be to go to the Rom Kitchin build update zip with only the Touchwizz in it and flash it from SD card via CWM.
http://romkitchen.org/sgs/?s=generator
APK might be in Perkas file stash from this forum ..###
jje
JJEgan said:
Easy way would be to go to the Rom Kitchin build update zip with only the Touchwizz in it and flash it from SD card via CWM.
http://romkitchen.org/sgs/?s=generator
APK might be in Perkas file stash from this forum ..###
jje
Click to expand...
Click to collapse
Thanks, but I'm on 2.2, which means I have the 3e loader which does not allow me to setup update.zips which are unsigned. For this reason, i was also not able to get CWM installed. I know there's a way to downgrade the loader to 2e, but I'll rather not try that at this moment.
I agree with jje. The best and probably easiest way would be to flash 2e recovery. Chainfire has created a kernel for that purpose and as long as you can access download mode you should be fine.
Sent from my GT-I9000 using XDA Premium App
chriszzz said:
Thanks, but I'm on 2.2, which means I have the 3e loader which does not allow me to setup update.zips which are unsigned. For this reason, i was also not able to get CWM installed. I know there's a way to downgrade the loader to 2e, but I'll rather not try that at this moment.
Click to expand...
Click to collapse
Flash SpeedMOD kernel with Odin and you'll get CWM.
Hi JJEgan, anfearg, Intratech
Thanks for the advice so far. But would it be possible for me to just simply use a file manager to copy the TouchWiz apk and odex files to my system/app directory ? My phone is rooted, so I know it's possible as long as I can get those files. I'm just not sure if there's anything else that needs to be configured to get Android to use those files during setup. If this is workable, this would be the easiest route. Now I just need to get my hands on those files.
I know Odin can fix this, but I'll rather just stick to the current stock rom for now, and just add the missing 2 files.
Intratech said:
Flash SpeedMOD kernel with Odin and you'll get CWM.
Click to expand...
Click to collapse
I'm going to take a look at Odin and see if its not too risky to flash my i9000. I've flashed my old WinMo phones in the past, so flashing is not new to me. But I've yet to try it for Android. Maybe I'll give it a go.
chriszzz said:
Hi JJEgan, anfearg, Intratech
Thanks for the advice so far. But would it be possible for me to just simply use a file manager to copy the TouchWiz apk and odex files to my system/app directory ? My phone is rooted, so I know it's possible as long as I can get those files. I'm just not sure if there's anything else that needs to be configured to get Android to use those files during setup. If this is workable, this would be the easiest route. Now I just need to get my hands on those files.
I know Odin can fix this, but I'll rather just stick to the current stock rom for now, and just add the missing 2 files.
Click to expand...
Click to collapse
OK, so I spent a couple of hours googling and downloaded Odin, a couple of stock ROMs, PIT files and USB drivers. Fired up Odin, followed instructions, and I'm now back to 2.1 with the 2e loader. Sweet. Had a heart stopping moment when Odin said "FAILED" in red, so i just reflashed another ROM and it went through successfully.
Looks like I'm in the ROM flashing crowd now.
Quick question : some ROMs ( like the one I flashed successfully with Odin ) contains just a few tars - 1 each for CODE/PDA, CSC and MODEM/Phone.
Others ( like the one that Odin failed to flash ) just contains a bunch of directories with files that have bin, rfs, lfs extensions.
Why are there 2 different types of ROM packaging ? Is the first one ( with the tar files ) specific to Odin ? How do I flash the other type then ? With ClockWorkMod ?
chriszzz said:
I'm going to take a look at Odin and see if its not too risky to flash my i9000. I've flashed my old WinMo phones in the past, so flashing is not new to me. But I've yet to try it for Android. Maybe I'll give it a go.
Click to expand...
Click to collapse
chriszzz said:
OK, so I spent a couple of hours googling and downloaded Odin, a couple of stock ROMs, PIT files and USB drivers. Fired up Odin, followed instructions, and I'm now back to 2.1 with the 2e loader. Sweet. Had a heart stopping moment when Odin said "FAILED" in red, so i just reflashed another ROM and it went through successfully.
Looks like I'm in the ROM flashing crowd now.
Quick question : some ROMs ( like the one I flashed successfully with Odin ) contains just a few tars - 1 each for CODE/PDA, CSC and MODEM/Phone.
Others ( like the one that Odin failed to flash ) just contains a bunch of directories with files that have bin, rfs, lfs extensions.
Why are there 2 different types of ROM packaging ? Does each ROM come in both forms ? Can they be converted from 1 form to the other ?
Click to expand...
Click to collapse
the .tar types are to be flashed via odin only whereas the ones with the directories are to be flashed via CWM(2e recovery).... mix them up and you'll be in trouble... ;-)
You only needed to flash the recovery 2e zip file through Odin from the forum .
jje
chriszzz said:
<snipped>.. Others ( like the one that Odin failed to flash ) just contains a bunch of directories with files that have bin, rfs, lfs extensions.
Why are there 2 different types of ROM packaging ? Is the first one ( with the tar files ) specific to Odin ? How do I flash the other type then ? With ClockWorkMod ?
Click to expand...
Click to collapse
The single .tar file with .rfs, .bin, etc. is a high-level package. It's sort of a firmware update and can only be flashed on top of an existing firmware. That is, you don't tick re-partition in odin. The ones that come with 3 separate files for CSC, PDA and MODEM are either medium or low-level packages. I think, the low-level ones come with bootloaders. These can be flashed with re-partition ticked.
Thanks guys.
Today I learned how to flash using ODIN (flashed a European 2.1 ROM onto my international i9000 originally with Asian ROM, and downgraded my 3e loader to 2e).
Then I learned to use ClockWorkMod, which I used to flash Darky's ROM 9.5 ( nice ROM, although booting up seems to take an usually long time. Not sure why ). Finally, I almost had a heart attack, twice, when my phone refused to boot after flashing. Nothing a 3 button combo to download mode couldn't fix though.
Fun fun fun. Thanks all.
Here's what I did to get JVH (with 850mhz band) and CSC for Canada on my phone. It worked for me at least
Files:
SpeedmodK15E_withLoaders.tar.md5 (8.38 MB)
http://www.multiupload.com/SRVH1BTK8R
JVH_KC1_BMC.zip (169.32 MB)
http://www.multiupload.com/1FHETKJOWA
StockJVH_Kernal_noLoaders.tar.md5 (5.47 MB)
http://www.multiupload.com/PM3AXR7JFG
**************Disclaimer:***************
I'm not responsible if this bricks your phone, as "the boss" said if I break mine, she'll break me... or I get a $20 replacement phone
Backup your /efs folder, backup EVERYTHING, just in case... I'm paranoid so I did it all
ROM NOTES:
Got deodexed from here:
http://forum.xda-developers.com/showpost.php?p=11256520&postcount=1
Modem:
KC1
Busybox:
1.18.4
Hosts file updated for ad blocking using:
http://winhelp2002.mvps.org/hosts.htm
Here's the steps I followed:
Save all files to folder/desktop
Connect phone via usb and copy JVH_KC1_BMC.zip to root of sdcard
Restart phone in download mode
Open Odin and click PDA
Select Speedmod tar file
Uncheck Auto-Reboot
Check F.Reset Time (I don't know what it does, but it's always checked)
Flash the tar.
Once complete and the box says "PASS" in green, unplug your phone and pull the battery (I was told it's safe, as it's in the MIUI instructions as well)
Put battery back in and start phone in recovery with VOL UP+HOME+POWER
In recovery choose to update from zip
Choose file from sdcard
Choose the JVH_KC1_BMC zip file and update
The phone will restart/install.
Once it's started up for the first time I recommend restarting in download mode and flashing the stock JVH kernal
You can also use any kernal you want.
Let me know if I can help at all. I was trying to make a completely odin flashable tar for this but failed miserably :9
I'll do my best to answer any questions however this is my first time making something to flash for you all
Note:
I'm not sure where to put this, sorry to mods/admins if it's in the wrong spot, please let me know
Hi,
I saw your thread, and I found it very interesting for people who own a Bell SGS 9000m Vibrant and wanna upgrate to Gingerbread.
So I decided to flash the Gingerbread JVH ROM just like you did, but I need to know a few things:
1. Will I be able to downgrade to my original stock froyo after this flash ?
2. Will I be able to update via Kies in case Bell release an official gingerbread update ?
3. Right now my phone is SIMUnlocked, will I lose my SIMunlockation after the flash ?
4. And is my actual configuration right to excecute this flash or should I flash something else before ?
My configuration is the following:
Baseband version
I9000UGJL2
Firmware
2.2
Kernel
2.6.32.9
[email protected] #3
Build number
FROYO.UGJL2
galaxy s vibrant bell
gt-i9000m
Thanks for your hard work, I hope to read back from you soon.
I have exact same configuration and exact same questions as poster above!!!
Still no answer... Guess we'll have to try if wanna know...
nguetto said:
Hi,
I saw your thread, and I found it very interesting for people who own a Bell SGS 9000m Vibrant and wanna upgrate to Gingerbread.
So I decided to flash the Gingerbread JVH ROM just like you did, but I need to know a few things:
1. Will I be able to downgrade to my original stock froyo after this flash ?
2. Will I be able to update via Kies in case Bell release an official gingerbread update ?
3. Right now my phone is SIMUnlocked, will I lose my SIMunlockation after the flash ?
4. And is my actual configuration right to excecute this flash or should I flash something else before ?
Click to expand...
Click to collapse
1. yes, it's possible
2. yes, but you would either need to downgrade first or do a kies hack
3. no
4. you can do it straight
Thanks zorxd.
I am going to try. So there is no need for me to select any Pit file or did the guy forget to mention it ? Also can we tick the repartition option in Odin?
Sorry if I ask usekess question I am used to flash android but new to the SGS flashing...
when you repartition you need a PIT file.
My advice is to not repartition unless you need it.
Too late... I did it got stuck into bootloop. I had an error when I tried to install the zip from the recovery (I had recovery 3e) : E : Short write of /tmp/sideload/package.zip (No space left on device) . However, I flashed the back eclair JHL and went back to the stock eclair rom. I am going to restart from there following your intructions. I now have recovery 2e ( Somehow I can't get ClockWorkMod Recovery to load directly; it always send me to recovery 2e and there I apply update.zip to go to CWM recovery)
Thanks for your help, I'll let you know if I manage to get it done.
Still get the error E:Short write of/tmp/sideload/package.zip (No space left on device) when try to install JVH_KC1_BMC.zip from the recovery 3e ( this recovery comes right after I flash SpeedmodK15E_withLoaders.tar ...
Don't know what else to try... Help please..
I did it a slightly different way. From 2.2, I flashed a stock 3 part gingerbread rom (phone, PDA, CSC) with bootloader update using ODIN 1.82. I then flashed CF root gingerbread kernel for CWM3 and then flashed the KC1 modem from clockwork recovery for the 850 band.
Could you please show me the exact files you used so I can try to do the same ?
Aren't there at least a couple threads on how to install jvh/jvp on an i9000? Its the exact same process as those you just have to flash the kc1 modem via cwm after you are done. It sounds like you guys are experimenting too much.
Sent from my Darky's i9000m
nguetto said:
Could you please show me the exact files you used so I can try to do the same ?
Click to expand...
Click to collapse
Our canadian phone is not really different from all the other ones, so you don't need a special "Bell Canada" installation.
If you want JVH, you can follow this thread:
http://forum.xda-developers.com/showthread.php?t=818556
You don't have to do everything like fugumod, etc. I would flash JVH via odin and then flash CF root kernel via odin so you get CWM3.
There's also leaked 2.3.4 JVP gingerbread out, if you feel inclined:
http://forum.xda-developers.com/showthread.php?t=1102881
There's a way to enable 850 band on the different gingerbread modems, but i never bothered, I just flashed the KC1 modem for Bell which has the band (via CWM3). Search for I9000UGKC1
http://forum.xda-developers.com/showpost.php?p=9874879&postcount=1
Okay I am really starting to freak out now...
I am stuck in bootloop, I can't get out og it. I tried flash Back the Stock Bell Firmware but it keeps boot looping. Download mode is okay. But it started doing this I had a message like sd could not be mounted in recovery 3e. Now I can't even access recovery after I flash Eclair but Download mode is still okay...
Aby ideas ?
Have you tried flashing back the stock JL2 firmware from bell? (found on samfirmware.com)
I've never encountered this error before, I wonder if it is a problem with the bootloaders, as the official froyo firmware from bell had a secondary bootloader and gingerbread has its own bootloaders as well.
nguetto said:
Okay I am really starting to freak out now...
I am stuck in bootloop, I can't get out og it. I tried flash Back the Stock Bell Firmware but it keeps boot looping. Download mode is okay. But it started doing this I had a message like sd could not be mounted in recovery 3e. Now I can't even access recovery after I flash Eclair but Download mode is still okay...
Aby ideas ?
Click to expand...
Click to collapse
I imagine you'll need the stock bell firmware as said above and also the proper PIT file to go along with it.
Sent from my Darky's i9000m
Also if you repartitioned it when you tried to flash the whatever it was when you tried you will also have to repartition it when going back down to froyo.
2.2 and 2.3 use different bootloaders therefore if you try to mix and match rom's without the bootloaders and repartioning you will get a ****y phone.
Sent from my Darky's i9000m
Thanks for your help guys. I didn't solve it yet, but i will open a new thread to prevent this one from getting to messy.
Hi All,
I'm not sure if this is the right place to post this as I'm relatively new to posting on XDA. My girlfriend has a Galaxy S4 (I337) that I quickly and easily installed Cyanogenmod on. It's awesome and significantly better than TouchWiz. So, I bought an S4 off Ebay assuming it would be similar enough. It turns out this new S4 is an I9500 and before shipping it was updated to 4.3, which appears to lock the bootloader and prevent downgrading. I've tried Odin, Heimdall, ADB, Philz, Chainfire, Cofface, stock ROMs, etc with no luck. Today I did manage to root the phone and confirm root with TowelRoot. I'm wondering/hoping someone might have some resources to get CM on this thing. While I'd prefer not to brick it I am willing to take risks as I have a Razr (soft-bricked and unbricked) running CM and am relatively comfortable with computers/Linux.
I've been Googling and trying things for a month now and can't even find that much information on the locked bootloader. Any help would be greatly appreciated, thanks.
--
SL
The I9500 doesn't have a locked bootloader. You just can't downgrade from 4.3 to 4.2.2 with official roms. Same applies when you are running 4.4, then you also can't downgrade officially.
Just flash a custom recovery true Odin and flash away.
Why would you even want to downgrade? Are you sure you are picking the right files? You cant flash the files for the I337 on the I9500. So just go to the section for the I9500 roms and flash away.
Hi Lennyz1988,
Thanks for the quick reply. I don't specifically want to downgrade but that's the last option I've tried. Ultimately the goal is to put Cyanogenmod on the phone. When I attempt to upload any file via Odin I get "secure magiccode check fail : boot" (or fail : recovery) depending on what I'm flashing. All the reading I've done says that when these phones are updated to 4.3 a fix has been applied that stops Odin from working. Thus, I my last resort is/was to try and downgrade. As I said, I've been Googling for the last month and while few people have posted about this I have not found any solutions.
Hoping someone might have a solution or anything new to try that I haven't tried already, thanks again,
--
SL
Download the latest TWRP recovery:
http://techerrata.com/browse/twrp2/i9500
Fire it up in Odin under PDA. You need the .tar (DON'T EXTRACT IT).
If it fails:
- Different usb port
- Different cable
- Different pc
- Reinstall drivers
- Make sure Kies is not running the background.
Or you can use heimdall to flash it. Use the command line though:
heimdall flash --recovery nameoftherecovery.img (you need the .img instead of the .tar)
No luck there, Odin still fails with the same message. I have tried Heimdall on 2 different computers (4 different usb cables) and always get the libusb 12 error.
Since I have root access I figured I might be able to wipe the recovery partition from a terminal emulator. I copied recovery.img from the I9500 CWM to the internal sd card. I then went to /dev/block/msm_sdcc.1/by-name to figure out what partition is recovery, turns out its 21. I then did “dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p21”. I then booted into recovery and it just hung up. I had previously found a stock recovery partition so I flashed that via Odin (the only file I have found that works flashing via Odin). I could then boot back into the normal recovery. I then tried flashing both recovery and cache with the CF Auto files (cache is partition 18). Same result, it just hangs when trying to boot into recovery. At one point I did manage to flash a recovery that then came up with a warning about “software installed that is not supported by AT&T” and I couldn’t get past that so had to flash the stock recovery again.
On a side note, I accidentally wiped the EFS partition in this process (if found a tutorial that shows the S3 had recovery in partition 10, which is EFS on the S4). As a result 1.) the menu didn’t pop up when I hit the power button and 2.) wifi didn’t work. So, I made an .img of the EFS partition on my GT-I337 and moved it to the I9500 and that worked restoring both. In case anyone makes the same mistake.
I have now also used CWM ROM Manager and GooManger and tried installing recovery that way with no luck.
Just check if the internal memory partitioning is correct ( number, size and format) (use fdisk or parsed).
ODIN will install according to the PIT file and if drivers and cables are OK it is no other explanation than that.
PS: do not trust heimdall data because it just read the PIT file and do not give the true info from the memory part.!
Uhm on the TWRP website they say that the I9500 has it on partition 10.....
This would be the proper partition based on their website:
mmcblk0p10
Are you absolutely sure you have an i9500? Because my guess is that you don't.....
Boot into download mode. What does it say your model is?
Because on the AT&T it's partition 21.... So my guess is that you are messing up....
Thanks everyone for the input/feedback,
Something I think I had forgotten to mention previously, when the initial root/recovery attempts didn't work I downloaded an app to verify it is a genuine Samsung as I have heard of very good knock-offs. It is genuine according to the app.
Good point/catch regarding the location of the recovery partition. Under About Phone it shows as an I9500 and always has. When in download mode it currently shows as I337 but I wasn't sure if that was simply a result of all my attempts so I figured best to go with the one I am certain has been the same since I bought the phone. I had been hesitant to try wiping the recovery with for the I337 as that is how I soft-bricked my RazrHD (ultimately un-bricked it).
Tonight I will try the I337 files and see if Odin is successful. Thanks again.
Damn! Turns out my phone is an I337. The hardward (under the battery) says I9500 and when I plug it into a computer it shows up as I9500. On the weekend I thought I read that there is now the ability to flash recovery and install CyanogenMod on I337 if its updated to 4.4.2. So, I donwloaded the firmware and flashed with Odin. It flashed successfully but now I realize I am mistaken and 1.) cannot flash recovery, and 2.) cannot downgrade. For the time being I have installed Nova Launcher and removed as much of TouchWiz as possible. It's not perfect but at least usable. I'd like to start researching what it would take to flash recovery on this phone but I suspect I'm too busy at this moment.
Thanks everyone for the help,
So my brand new SD care went corrupt while I had a lot of programs running from it... By means of Link2SD app I put system files on there too and now I get
E:failed to mount /system (Invalid argument)
I can't seem to fix this problem and it doesn't seem that this problem arises very often because I have found nothing in searching. Any help would be great... I don't want to have to put a hammer to it and then call Asurion for a replacement..... but that does sound fun lol.
I have tried to Odin everything I have in my backups but not sure if any of those are actually the original rom. I have been trying to figure out how to Odin CM or TWRP on to it... or get them install in some form with out the APK. I saw something about them being able to fix the issue.
Have you tried using ODIN and flashing back to a fresh, stock ROM?
I forgot to put all that. I have tried to Odin everything I have in my backups but not sure if any of those are actually the original rom. I have been trying to figure out how to Odin CM or TWRP on to it... or get them install in some form with out the APK. I saw something about them being able to fix the issue.
Our phones do not support CM or TWRP because we have a locked bootloader. You are on a Verizon G900V, right?
Here's a link to a post with stock ROMs you can Flash via Odin. Choose the appropriate one for the version you want and Flash. Make sure you back up anythibg you want to save.
http://forum.xda-developers.com/showthread.php?t=2784880
It doesn't matter what I flash I get the same error. The other things I have found say that the system and/or EFS needs to be re-made so to speak. TWRP has a command that does it and CM allows you to go in though ADB and do it..... That is the best I have found for answers so far. I don't see anything for FlashFire or SuperUser.
Flash using ODIN not FlashFire or anything else.
I have flashed with Odin.... I get no where.... doesn't matter what kernel I use or ROM or anything.... I was saying that the people that have solved this porblem before are using CW or TWRP to access the ADB to send commands for the phone to re-setup the system/EFS
Did you Flash the pit file on the page I linked earlier? That should repartition everything.
Still the same problem
So I just kept flashing tar files from the post above and finally the NI2 took along with the pit file. Thanks for your help @btonetbone
Eventually the NI2 + .pit file being flashed together fixed the problem.