yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 General] Chahk:
Are you using the recovery I linked to?

Also, when modifying the ROM zip, make sure you are not editing the updater-script or build.prop files in an editor that will mangle line endings like Notepad. Try an advanced editor like Notepad++ instead.
[Galaxy S 4 General] drdingo21:
Yep! Everything from your op. are you not getting a password prompt?

I also didn't edit the files. I just dropped them into the Zip
[Galaxy S 4 General] Chahk:
No, no password prompts here. Can you try re-flashing the recovery via download mode again?
[Galaxy S 4 General] taney:
I heard the LTE bands are different for the phone because of the locked radio and modem. Only the GE edition can operate on both US carriers.
[Galaxy S 4 General] drdingo21:
Alright. New computer with windows JUST installed.

When I flash the recovery and reboot it doesn't boot into recovery right away. It sits on the Teamwin splash (which it did before) but a reboot gets me into recovery. I still get the password prompt. I re downloaded everything in the OP. Is there somewhere else I should try grabbing the recovery?

---------- Post added at 09:46 PM ---------- Previous post was at 09:16 PM ----------

So I fixed my problems.

I've had my phone since they day they were shipped. I just tried the how to above with out any kind of wipe before hand.

I reflashed the stock recovery then did a full wipe and then wiped the cache again to be sure. Reflashed the attached recovery and all is well! I assume there was something making twrp think there was a password.

thanks for the tutorial!
[Galaxy S 4 General] irishrally:
Can your tweaked installer be used in the same way to make other 9505 ROMs and kernels work on the 9505G?
[Galaxy S 4 General] warwolfx0:
i had to change zadigto libusb0 (v1.2.5.0) from the default WinUSB (v6.1.7600.16385)

then everyting worked

i know have twrp on my i9505G.

btw if you boot the file using fastboot the touchscreen dose not work but once you flash it it works.
[Galaxy S 4 General] samomamo:
What is the point of this? We have cm10 already. Why go thru this?
[Galaxy S 4 General] tublah:
Not that I've found. I've tried a couple other TouchWiz ROMs (even really small ones) and they all refuse to boot. :( So much for an unlocked bootloader, eh? :)
[Galaxy S 4 General] drdingo21:
We don't have CM10. We have asop. Lots of differences.
[Galaxy S 4 General] samomamo:
I don't understand. What's this?

http://download.cyanogenmod.org/?device=jfltexx&type=nightly

---------- Post added at 06:07 PM ---------- Previous post was at 06:03 PM ----------

OK I get it this is for Google edition of the GS4.
[Galaxy S 4 General] drdingo21:
That is CM 10. CM10 is AOSP which is Android open Source Project. There is nothing included with the ROM except android. Which is why you have to flash GAPPS (that and the ceases and desist that google sent to them).

CM10 includes many different tweaks than the ROM that included with the GE s4 and CM10 is maintained by the community - which is why sometimes you see things not working.
[Galaxy S 4 General] irishrally:
Have you tried any AOSP or other CM based ROMs?
[Galaxy S 4 General] toanau:
But couldn't you flash this like any other ROM.
[Galaxy S 4 General] Chahk:
You could... But only once, before you soft-brick the S4 and need to Heimdall back to stock.

Look, the Google Edition S4's (i9505G) hardware is most closely alike to the international S4 version (i9505), but their partition structures are slightly different, requiring small tweaks to the installer script, and a new custom recovery. The i9505G is vastly different from any TouchWiz versions, both hardware wise and partition wise. In other words, you cannot just flash any ROM on it without bad things happening. Bottom line is that until the TeamWin releases an official TWRP, and CyanogenMod team starts supporting GS4 GE officially (at least in the nightlies) this is the easiest way to get CM 10.1 into our i9505Gs.
[Galaxy S 4 General] drdingo21:
Im not really sure what you updated in the script What about another AOSP Rom? Like rootbox?
[Galaxy S 4 General] Chahk:
I added i9505G's product name to the first assert statement so that it doesn't abort the flashing immediately, and also the destination of kernel boot.img is different ("/dev/block/mmcblk0p21" on i9505G vs. "/dev/block/mmcblk0p20" on i9505) which had to be fixed. If you wish, you can extract the updater-script from latest CM nightly and compare it with my edited one in WinMerge or a similar tool.

You can try doing a similar edit to another AOSP-based ROM. Here's a list of partitions from i9505G:

aboot -> /dev/block/mmcblk0p6
apnhlos -> /dev/block/mmcblk0p1
backup -> /dev/block/mmcblk0p24
boot -> /dev/block/mmcblk0p21
cache -> /dev/block/mmcblk0p18
efs -> /dev/block/mmcblk0p10
fota -> /dev/block/mmcblk0p23
fsg -> /dev/block/mmcblk0p25
m9kefs1 -> /dev/block/mmcblk0p13
m9kefs2 -> /dev/block/mmcblk0p14
m9kefs3 -> /dev/block/mmcblk0p15
mdm -> /dev/block/mmcblk0p2
misc -> /dev/block/mmcblk0p19
modemst1 -> /dev/block/mmcblk0p11
modemst2 -> /dev/block/mmcblk0p12
pad -> /dev/block/mmcblk0p9
param -> /dev/block/mmcblk0p20
persdata -> /dev/block/mmcblk0p27
persist -> /dev/block/mmcblk0p17
recovery -> /dev/block/mmcblk0p22
rpm -> /dev/block/mmcblk0p7
sbl1 -> /dev/block/mmcblk0p3
sbl2 -> /dev/block/mmcblk0p4
sbl3 -> /dev/block/mmcblk0p5
ssd -> /dev/block/mmcblk0p26
system -> /dev/block/mmcblk0p16
tz -> /dev/block/mmcblk0p8
userdata -> /dev/block/mmcblk0p28

(You can get this list by using the following command: adb shell ls -l /dev/block/platform/msm_sdcc.1/by-name/ )

Now go through the updater-script, and find where it's mounting or extracting something to a /dev/block/... Now cross-reference the source (e.g. /system or boot) to the above list to make sure the "mmcblk..." match. Alter to the proper one where it doesn't.
[Galaxy S 4 General] drdingo21:
You sir a god among men.

With the listing you just posted - I was able to flash liquid smooth with out any problems. I suddenly enjoy my phone 10 times more.

You're a stud.
[Galaxy S 4 General] MJHawaii:
Thank you for this. Once we get recovery support and the Script done things will start to move. I really think we need our own A&D sub-forum here instead of sourcing through everything

---------- Post added at 11:25 PM ---------- Previous post was at 11:19 PM ----------

Were you able to successfully create and replace a script on Liquid Smooth and flash it via recovery? Please share more details
[Galaxy S 4 General] drdingo21:
Yes! Runs like a champ. I used the attached build prop and just edited the liquid smooth updater script and didn't wipe the cache and all is well. The liquid smooth has way less to edit. If you want when I get home I can post the file.
[Galaxy S 4 General] MJHawaii:
Awesome that's great news please post that file and Mahalo
[Galaxy S 4 General] drdingo21:
Files are attached.

Just go download liquid smooth for 9505 and drop the files where the OP says:

Then copy to your phone and flash. After the flash don't wipe anything just restart your phone.

All credits goto Chahk hes the one that did the work and put everything together
[Galaxy S 4 General] MJHawaii:
Thanks I will thank Chahk actually I wanted a starting point for modding the base and the updater-script writing had me at a loss. If I can I'd like to send mine to you and Chahk for review once I finish it
[Galaxy S 4 General] Chahk:
Hey, look what showed up on the TWRP2 site: http://teamw.in/project/twrp2/192 :)

It's officially official: custom recovery for the i9505G, courtesy of Team Win.
[Galaxy S 4 General] MJHawaii:
Nice!!
[Galaxy S 4 General] toanau:
Does it means we r our own getting custom ROM soon.

---------- Post added at 10:49 PM ---------- Previous post was at 10:30 PM ----------

Any be know if there is step by step video on how to CM on GE S 4. I am already rooted and with trwp recovery installed.
[Galaxy S 4 General] MJHawaii:
I'm working on a new ROM for the I9505G now and hopefully I will have it ready soon. Im not aware of any how to videos your going to have to search YouTube for that.
[Galaxy S 4 General] Mohammad_Adib:
Confirmed working.

Wifi AP confirmed working.

P.S, Google Wallet wont work on rooted devices. Google made it that way, so it doesn't matter anyway.

Great job! I'm extremely happy!

Edit: sometimes doesn't boot!
[Galaxy S 4 General] drdingo21:
Since the hardware is almost identical you should be able to run an AOSP ROM in the 9505 section which the changes that I and Chahk listed above
[Galaxy S 4 General] toanau:
I am already rooted with latest twrp I installed. So at this point I don't the computer anymore. I download the CM rom file also with script in my phone. Now the next thing is to replace the "updater script" in the CM ROM. Is this correct.
[Galaxy S 4 General] toanau:
Also do u need to replace the "build prop" in the CM ROM.
[Galaxy S 4 General] MJHawaii:
Yes the updater-scipt and the build prop then your good to go

---------- Post added at 03:53 PM ---------- Previous post was at 03:53 PM ----------

Yes you do as stated in the OP
[Galaxy S 4 General] toanau:
I used T-Mobile in the US this should be no problem?
[Galaxy S 4 General] MJHawaii:
I'm not sure I understand your question can you be more specific?
[Galaxy S 4 General] toanau:
I am in the USA using T-Mobile. I am not sure would there be any problem using a international ROM. Would it have any impact with my service with my provider
[Galaxy S 4 General] MJHawaii:
Well a ROM is not going to change your hardware so you should have no trouble with service. Flashing international ROMs is a no go my friend you can get away with flashing asop ROMs like CM and liquid by replacing the script and prop but touchwiz is a no go for the moment until a port is successfully made. So to answer you question No at the moment.
[Galaxy S 4 General] toanau:
So u still need a computer to copy and paste to file over the cm ROM. I tried using ES file to move the file but a no go. Do u recommended any app that could do this. Beside using computer
[Galaxy S 4 General] MJHawaii:
Yes you need a PC when your modifying scripts and props. Some ROMs will be posted soon though. I am working on something ( slowly) and I am sure others are too
[Galaxy S 4 General] toanau:
By any chance do u know if we r getting our own forum
[Galaxy S 4 General] MJHawaii:
Not sure on that bud I know people have requested it
[Galaxy S 4 General] Chahk:
You can try using Android apps that can modify ZIP archives. I haven't had the best experience with those - most were simply unable to open archives of large sizes like 190MB+ ROMs. It's been a while since I tried though, so newer versions may work better now. Take a backup in recovery and give it a shot. Worst case - just restore the backup.
[Galaxy S 4 General] toanau:
I currently use ES file now. So far it could go in to the zip file but I can't copy and paste into a zip file. I am trying to copy paste the two script. So this work with other ROM too like liquid ROM.
[Galaxy S 4 General] letolkki:
reboot stuck on google screen/ power up works fine

I used your method on cm10.1 source code build and it works. However if I reboot the device is stuck on google splash page with no adb or usb responce on computer. If I yank battery then put it back in and power up it boots fine. Is there something obvious that I'm missing or a bootmode that reboot isn't picking up.

Thanks
[Galaxy S 4 General] toanau:
Which software did used to paste the script file to CM ROM. I tried using 7win but it crashes when I try to paste the script
[Galaxy S 4 General] Chahk:
I remember something similar happening to me a few times. I chalked it up to a bad edit to build.prop, restored from backup and moved on. Now that you mention the same thing happening to you, I'm thinking we should leave build.prop that comes with CM nightly alone. The Settings -> About phone will make it look like the international GS4, but at this point it doesn't matter.

I removed build.prop from the attachment and modified instructions in OP accordingly.
[Galaxy S 4 General] letolkki:
I just unzipped the file, replaced the file then zipped it back up on linux.

---------- Post added at 01:35 PM ---------- Previous post was at 01:33 PM ----------

Your OP said the build.prop was optional so I left it out. Lately the phone seems to be rebooting fine now. I hope its not some nasty race condition thing. Thanks
[Galaxy S 4 General] toanau:
Could u do same in liquid smooth ROM. Could u point to me the correct liquid smooth rom there are many different choices
[Galaxy S 4 General] Chahk:
Yes you could. You may want to PM drdingo21, as he already did it according to his post here.
[Galaxy S 4 General] toanau:
So for different ROM u have to use a different script or do we use the same script that u posted
[Galaxy S 4 General] wilbarger:
Chahk, have you done any of the nightly updates to CM10.1 yet? 0719 is running very well for me, so I an not sure if I should let nightly updates install or not.
[Galaxy S 4 General] Chahk:
I've been running every I9505 nightly for the past few days in the same manner: replacing the updater-script with the one attached in OP, pushing it to /sdcard, and flashing via recovery. Everything seems functional as far as I can tell.
[Galaxy S 4 General] wilbarger:
Is it required to do a wipe before flashing the nightly?
[Galaxy S 4 General] Chahk:
It's not any different that flashing any other ROM: you only need to wipe if you are coming from a completely different ROM (e.g. first time coming from stock GPe). As long as you stick to AOSP derivatives like CyanogenMod, you shouldn't have to wipe anything. As always, if you come across any major issues a wipe is recommended to rule out any userdata corruption.
[Galaxy S 4 General] toanau:
Could we use your script on any i9505 ROM. Thanks for your help I got CM and liquid smooth ROM to work in my GOogle edition s4. I was seriously thinking about returning the phone before I found your forum
[Galaxy S 4 General] irishrally:
...wrong thread
[Galaxy S 4 General] Chahk:
I don't recommend just dropping CM's updater-script into a different ROM's zip. That could potentially soft-brick your S4, requiring flashing back to stock via Heimdall. The safest way would be to modify that particular ROM's updater-script using the method I posted about earlier in this thread.
[Galaxy S 4 General] irishrally:
I got jaml's 4.3 ROM for I9505 to work using your method, just needed to change the boot.img mount point from 20 to 21 like you described. You put should your post in the OP ... it's kind of a big deal.
[Galaxy S 4 General] jaypm007:
For what it's worth, I've experienced the same phenomena as letolkki using the CM nightly build.prop. When in this state I've noticed the following:

1) The unit recovers if a SD card is inserted or removed.

2) When I hold the power button for a hard reset it will recover on occasion. When it doesn't, I get stuck in LPM and pulling the battery become my only recourse.

3) Pulling the usb cable doesn't have any effect. Actually when I get in this state, interestingly enough, I don't even see a usb device on the bus.

Other than the reboot issue, everything else was working as advertised. Thanks for posting the updater-script!
[Galaxy S 4 General] Chahk:
I feel that I should mention this in the OP.
[Galaxy S 4 General] ThugEsquire:
To be honest it sounds like you were flashing the wrong recovery from the get-go, and once you flashed the right one, you were fine.
[Galaxy S 4 General] sabre31:
I got miui working using these steps. Nice work and thank you.

Has anybody tried to get a touchwiz ROM like omega working?
[Galaxy S 4 General] wilbarger:
I am having the same issue with the TWRP 2.6.0 recovery. If I reboot (volume up, home, pwr) most of the time the teamwin screen stays there. I can reboot into recovery with Goo Manager and it seems to work better for me. Not a huge problem, but he is not the only one this is happening to.
[Galaxy S 4 General] illogic6:
A little off topic, but how can we petition the mods to make a forum specifically for the Google Play variant? I see these forums getting very messy if that isn't done some time soon. (And a lot of bricked/soft-bricked phones)
[Galaxy S 4 General] wilbarger:
Lot of posts about this. I wonder if the HTC One GE is going through the same thing. We do need a separate forum, especially as the custom ROM's are being built. Not like there is lack of space or interest in these new phones that are enough different from the international, att, etc phones that a new forum is deserved. Maybe the mods can help out with this.
[Galaxy S 4 General] jrodsep:
+1 Would love to see a i9505g specific forum. Things can get very confusing for everyone specially for those of us that don't have a lot of modding/flashing experience.
[Galaxy S 4 General] illogic6:
Go here and request the forum be created. The more community support these Play edition phones get, the more they'll sell and hopefully that'll mean we'll see more in the future. That would be a very good thing.

http://xdaforums.com/showthread.php?t=1660354

OP, any chance you could add this link to the first post? Would probably be beneficial for everyone with this phone to make a request.
[Galaxy S 4 General] Chahk:
Done.

I've posted on that thread several times with little results. I'm not sure it's even being looked at by the mods any more. Couldn't hurt to ask (read: beg) though.
[Galaxy S 4 General] illogic6:
I'm starting to wonder if a direct PM to someone would be in order. I just don't know who quite yet. It wouldn't make any sense for these phones to not get their own sections.
[Galaxy S 4 General] irishrally:
Yes it's disappointing. It's really confusing when someone with a i9505 is running a google edition ROM so their taptalk signature says i9505G so someone might think the ROM or kernel they are running is working on the i9505G S4 when really it's not. Not to mention all the ROM/kernel threads with Google Edition in the title or tags that for the most part don't actually run on the i9505G. It's gotten to the point where "i9505G" doesn't mean the Google Edition S4 phone any more, it means a google edition ROM for the i9505. If there was ever a case to be made for a dedicated forum or sub forum this is it. i9505G is a hardware designator so all the i9505 guys running a google edition ROM should update their signatures to "sent from my i9505 running i9505G modified software" or even better the ROM chefs or users should change their build.prop back to i9505.
[Galaxy S 4 General] illogic6:
My point exactly. I see lots of newbs with bricks in our future.
[Galaxy S 4 General] MJHawaii:
Hey Guys I posted a NEW I9505G Discussion thread here http://xdaforums.com/showthread.php?t=2381339
[Galaxy S 4 General] drdingo21:
No. As I said everything was downloaded from the OP.
[Galaxy S 4 General] Chahk:
Just an FYI.

I'm playing around with the unofficial CM10.2 ROM from here. It looks like finally the updater-script was changed to use the logical partition names (/dev/block/platform/msm_sdcc.1/by-name/system) as opposed to hard-coded blocks (/dev/block/mmcblk0p16). This means that ROMs from i9505 variant have become a lot more compatible with i9505G. Modifying the updater-script has gotten a lot easier - just remove the first "assert..." statement and you are done.
[Galaxy S 4 General] baberthal:
Shouldn't we just be able to add our model number to the "assert..." statement, and then flash correctly?
[Galaxy S 4 General] Chahk:
Removing the assert statement has the exact same effect. We are simply bypassing the sanity check that prevents n00bs from flashing ROMs on wrong devices and potentially bricking them.
[Galaxy S 4 General] letolkki:
T-Mobile and ATT cm10.1 build works with this method also

just as a test I tried the updater-script on T-mobile (jfltetmo) and att (jflteatt) variants of cm10.1 nightly and they boot just fine. I haven't tried all the hardware (bluetooth, camera, wifi) tho.
[Galaxy S 4 General] Vivisec:
Hi! I think I'm nearly there, and it so frustrating to be so close. This is what is returned when I try to flash:

E: Unable to find partition size for '/data'

Updating partition details . . .

E: Unable to mount '/preload'

Running boot script . . .

Finished running boot script.

Formatting Cache using make_ext4fs . . .

Done.

Updating partition details . . .

E: Unable to mount '/preload'

Installing '/external_sd/cyanogen/cm-10.1-20130801-NIGHTLY-jfltexx'.

Checking for MD5 file . . .

Skipping MD5 check: no MD5 file found.

assert failed: getprop("ro.product.device") == "jflte" || getprop("ro.build.product") == "jflte" ||

getprop("ro.product.device") == "jfltexx" || getprop("ro.build.product") == "jfltexx" ||

getprop("ro.product.device") == "i9505" || getprop("ro.build.product") == "i9505" ||

getprop("ro.product.device") == "GT-I9505" || getprop("ro.build.product") == "GT-I9505" ||

getprop("ro.product.device") == "jgedlte" || getprop("ro.build.product") == "GT-I9505G" ||

getprop("ro.product.device") == "i9505G" || getprop("ro.build.product") == "i9505G");

E: Error executing updater binary in zip '/external_sd/cyanogen/cm-10.1-20130801-NIGHTLY-jfltexx'.

Updating partition details . . .

E: Unable to mount '/preload'

FAILED

I have tried both of the updater scipts you provided, and tried it with the build prop switched and not switched. Same result everytime, with the assert failing.

Like I said, I know it's something so simple I'm missing. I'm running TWRP 2.5.0.2. PLEASE HELP

Edit: Jesus, now my phone won't boot even after restore :(

Edit2: Thankfully, Odin restore worked. Lesson learned, don't try to modify the updater script without knowing what you're doing. It will kill you.I'm not going to try this again until someone tells me what I'm actually doing wrong :/
[Galaxy S 4 General] theclueless:
you are using the wrong TWRP
[Galaxy S 4 General] Vivisec:
I am? So would 2.6 work? Sorry, I am very new to this :eek:

Thank you for your advice!
[Galaxy S 4 General] bagelicious:
Absolutely 2.6 will work. It is linked to multiple times in the OP. Maybe you should start over from the beginning and re-read each step. Here's the link. Good luck!

http://teamw.in/project/twrp2/192
[Galaxy S 4 General] noobnl:
you should be able to boot and flash cm now without modifications. 10.1 and 10.2
[Galaxy S 4 General] Chahk:
Can anyone confirm this? Last time I tried the 20130807 jfltexx nightly I ended up not being able to boot at all. Had to go all the way back to stock 4.3.
[Galaxy S 4 General] letolkki:
reboot stuck on google screen/ power up works fine

just as an update of info on reboot problem. When the phone is stuck on reboot it will boot fully eventually. I accidentally witnessed this when leaving the phone in this state while doing something and 6 minutes later it booted up. Another time it was 13 minutes later. Something is hanging it periodically. I just put the phone in a reboot loop to catch the problem. Oddly reboot recovery never gets hung.

Just some tidbits of info in case anyone out there might have some insight as to what is causing this.
[Galaxy S 4 General] noobnl:
it is a known issue on jf family
[Galaxy S 4 General] noobnl:
try the latest nightly
[Galaxy S 4 General] toanau:
Just wondering would your script work with the CM 10.3 nightly.
[Galaxy S 4 General] deaffob:
You mean 10.2? 10.2 is 4.3
[Galaxy S 4 General] toanau:
Sorry about that. 10.2
[Galaxy S 4 General] Chahk:
Latest official 10.1 nightlies, as well as unofficial ones built after 8/8 should not need any modifications to the updater-script. You should be able to flash them directly, provided you have a compatible recovery installed.
[Galaxy S 4 General] toanau:
Does it goes the same for any other CM base rom
[Galaxy S 4 General] Chahk:
Depends on the ROM's cook. Take a look inside the updater-script of whatever ROM you want to flash, and check the third parameter to the "mount" commands. It they read "/dev/block/mmcblk...", then the ROM hasn't been transitioned to the symlinks, and you should follow the steps outlined in the OP. It they read "/dev/block/platform/msm_sdcc.1/by-name/...", then you should be able to flash it without any changes.
[Galaxy S 4 General] deaffob:
Did you flash chenxiaolong's unofficial CM 10.2 without moding the updater-script?