yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] Masta_mind257:
Mine has done this something vaguely similar. I had YouTube open both times, the screen started distorting and then the phone just blacked out. When I tried turning it on again it got stuck at the S4 logo. Had to pull out the battery and I had to reflash the ROM to get it running again, no data loss though.
[Galaxy S 4 i9505 Original Android Development] invisiblek:
I just can't understand what is so much different about this device. To the point where I'm not even convinced that it is the rom/recovery anymore. I've successfully flashed a jfltexx recovery and rom (several times) on my jfltevzw. You'd think if it was an issue with the rom or recovery I'd be able to reproduce it in that fashion.

So I notice there is a new ROM for I9505 available: XXUBMF5

I whipped together a zip that flashes all the firmware for this release (aboot, sbl2, sbl3, rpm, tz, NON-HLOS, modem)

This could possibly fix the problem we are seeing here.

My question is: Since this is apparently a release for the Spain (PHE) I9505, will it be bad for other I9505's? Specifically would it cause a brick? My initial searching is showing that it would not. The build.prop doesn't reference the fact that it is specific to PHE or Spain. I peeked at aboot in a hex editor and it also doesn't appear to show anything specific for PHE or Spain.

Anyway, who wants to test it? Preferably someone who is really good at getting status 7 errors flashing CM roms. PM me please.

It should be noted, there is a very slight chance of a brick here unless someone can confirm 100% that firmware is cross-compatible between regions.

I'm seeing no mention of regional issues in this thread: http://xdaforums.com/showthread.php?t=2250824

This should be safe to do!

If you've odin'd a stock tar from a different region, then there should definitely be no issue here. If anyone has done this already, please let me know.

Thanks!

EDIT: appears to not brick. Also appears to not fix anything...

For those who want it: http://invisiblek.org/gt-i9505/firmware/jfltexx_XXUBMF5_firmware.zip

Flash via recovery.
[Galaxy S 4 i9505 Original Android Development] pitcher85:
I flashed many different stock tars or modified sock tars via Odin in the last weeks.

Most of them were not of my region and everything was and is working fine. So there is no problem with flashing stock from different regions.
[Galaxy S 4 i9505 Original Android Development] qpop:
invisiblek, thanks for all the work that you're doing maintaining our device.

As I understand it, deleting the line re: system is a dirty workaround due to the fact that you could end up with incompatibilities if there was a major system update.

A potential solution was posted a few pages back:

Does using the delete_recursive command provide a cleaner workaround? This has solved all Error 7 issues that I have had on a UK XX I9505 and I am unable to install the official nightlies whatsoever without making this change.

I wonder what your thoughts are?
[Galaxy S 4 i9505 Original Android Development] ginux_:
Good summary!

Has anyone tried unmounting /system manually before installing? It would be great if we could isolate the issue to a specific command that is not working with recovery - Or do we already know exactly wich line is causing/fixing the status 7 problem?

I might be able to try deleting one line at a time later and see if it works, just need to figure out the use for an eventual $600 paper weight :)
[Galaxy S 4 i9505 Original Android Development] live-evil:
We already know which line causes the status 7 issue. In the updater script the line "format("ext4", "EMMC", "/dev/block/mmcblk0p16", "0", "/system");" causes it to freeze. Which is why someone suggested a different way of deleting the /system partition.
[Galaxy S 4 i9505 Original Android Development] footsouljah:
New nightly is out ;)
[Galaxy S 4 i9505 Original Android Development] Cygnust:
Hi, sorry for the dumb question but how different is a firmware from a rom ?
[Galaxy S 4 i9505 Original Android Development] 3bs11:
Anyone else can't connect to wifi and bluetooth at the same time? I was connected to my wifi but when I connected my bluetooth headphones the wifi disconnected.

Edit: installed after wiping to install a new ROM in philz recovery.
[Galaxy S 4 i9505 Original Android Development] BillGoss:
A ROM only updates the system and boot partitions. Whereas a firmware update updates many other partitions, such as aboot, sbl2, sbl3, rpm, tz, NON-HLOS, modem.

Sent from my GT-I9505
[Galaxy S 4 i9505 Original Android Development] soza971:
Carrier label not showing up in notification bar but i got a number anyone else got that?
[Galaxy S 4 i9505 Original Android Development] SoLChoBo:
Ok, this is new...

...I have tried to install the new nightly, before doing it I have edited the updater script removing the "format" string.

Now I get status 6 error...

...what should I do?

;)
[Galaxy S 4 i9505 Original Android Development] ramon.nmgn:
I got a few noob guestions for you guys (sorryyy:angel:)

- When i play music from my ext-sdcard in "Apollo", it plays the first 1 a 2 seconds of the song and then it stops. After 5 seconds the song repeats and plays the full song.... This happens with all my songs.

I already formatted my sd card but it doesnt help.

- Will me firmware gets updated everytime i reflash an updated CM rom?

I hope someone can help me with this.
[Galaxy S 4 i9505 Original Android Development] 9Lukas5:
I have flashed it also, and noticed the same ting as trying to flash one of the modem zips for cwm, it says it flashes, but at least no changes are applied, my baseband stays the same.

As mobile odin is now available for our device, could you make that file for Odin?

L
[Galaxy S 4 i9505 Original Android Development] thisisfraa:
Maybe your SD card is too slow? Try Poweramp en change the buffer setting under Settings -> Audio -> Advanced Tweaks -> Audio Buffer Size. You can also try changing the Audio Thread Priority settings there.
[Galaxy S 4 i9505 Original Android Development] sam3000:
What happens if you sleep (eg 5s) after the format instead of removing it?
[Galaxy S 4 i9505 Original Android Development] 9Lukas5:
If the error appear during the format line in the script, it doesn't even get to the sleep you want to include.

But I ment I red somewhere in here, that s.o. has got a log that showed that the recovery expected 3 arguments for formatting with the used binary instead of the used 5 arguments. Isn't there a format command with only 3 arguments to test if that is working (better)?

L
[Galaxy S 4 i9505 Original Android Development] NZgeek:
The big problem with doing this is that you're only treating the visible symptom, not the root cause. It's not really a viable long-term solution. In fact, it might make things worse because there's less incentive to fix the real problem if the hack fix works.

Think about it this way: there's a light bulb in your house that blows every few weeks. You can change the bulb every time it blows, but this only fixes the immediate problem (lack of light). If you want to avoid replacing the bulb all the time, you need to get someone in to check your writing.
[Galaxy S 4 i9505 Original Android Development] stony007_de:
Who can say me, what is a compatible recovery.

I used TWRP and Philz CWM but every time an get an issue while I tried to install the nightly.????

I came from PAC

Gesendet von meinem GT-I9505
[Galaxy S 4 i9505 Original Android Development] live-evil:
that is because PAC rom has removed the line, format("ext4", "EMMC", "/dev/block/mmcblk0p16", "0", "/system"); from the updater-script file. If you want to install the nightly you have to reboot into recovery a few times and attempt to flash again and again until it sticks or remove the line from the updater-script.
[Galaxy S 4 i9505 Original Android Development] supertack:
So why CM team don't remove this damned line ?! :eek:

To be honest, I've never been so disapointed by using CM like this time on my i9505 ! Yes, the device is just out for few months, but I feel that development is so buggy !!!
[Galaxy S 4 i9505 Original Android Development] Stevemeister:
Relax dude, we are lucky to have Dan supporting our device officially because he doesnt own the device. If you want better dev support than donate a dev some money to get one now or be patient. Development isnt buggy or slow btw Steve has CM ported within the first week after release with all major functions working. We have one big bug/issue, thats the recovery issue and a few small bugs. So give the devs some credit please.

And removing the line probably isnt the right solution, so give the devs some time to find a proper solution.
[Galaxy S 4 i9505 Original Android Development] -sandro-:
the google edition release will fix everything (hopefully) :p:p
[Galaxy S 4 i9505 Original Android Development] supertack:
You're 100% right. I'm myself an opensource developer and I know how hard is to develop for the others...and for free most of time ! ;)

So I'm not angry or kind of this...I just try to understand why the i9505 is so hard to have CM ported to it. I had before the i9300 and I was a CM user for two years !
[Galaxy S 4 i9505 Original Android Development] live-evil:
They won't remove the line because installing a rom on a non empty partition is pretty risky. A better workaround is to replace the format line with, delete_recursive("/system"); at the core though this is a bug that needs to be understood and fixed properly. Programmers like most mathematically inclined hate imperfect solutions. So using a workaround is like admitting defeat :laugh:
[Galaxy S 4 i9505 Original Android Development] simondavies315:
Has the carrier bug been fixed in the official builds yet or are people still getting network numbers?
[Galaxy S 4 i9505 Original Android Development] wicki30:
Been using this Official CM for weeks now. Upgrading to every latest nightlies without much problem.

1. Download nightly to ExtSd,

2. Enter recovery (philz)

3. Format system

4. Install the unmodified cm zip

5. error 7

6. Back - advanced - reboot recovery

7. install the cm zip again (success)

8. Install gapps

9. Reboot

Ok

Its like this for every nightly.
[Galaxy S 4 i9505 Original Android Development] invisiblek:
Here you go. http://invisiblek.org/gt-i9505/firmware/jfltexx_XXUBMF5_firmware.tar.md5

Let me know...
[Galaxy S 4 i9505 Original Android Development] simondavies315:
Are there any leads on what's causing the status 7 and any possible solutions yet? I program a bit myself so I'm just asking out of curiosity

Hopefully it won't kill the cat :)
[Galaxy S 4 i9505 Original Android Development] invisiblek:
I can tell you that

script aborted: format() expects 3 args, got 5

Does not exist in the update-binary. I find this quite odd, quite annoying as well.

Here's an error I might expect if format fails:

https://github.com/CyanogenMod/android_bootable_recovery/blob/cm-10.1/updater/install.c#L201

Seeing as how this is the code that actually produces the update-binary....I find this odd.

Nowhere in (at least stock) clockworkmod recovery does anything expect 3 args either.

I'd sure like to get a recovery.log and dmesg.log of this thing failing on stock clockworkmod...

I'm not sure if that's been provided yet.

The way I'd do it, is start the log dumps via adb before attempting to flash the rom. At least I'd get the failure up to that point. Apparently it locks up when it fails or something.
[Galaxy S 4 i9505 Original Android Development] simondavies315:
This is why I find programming so frustrating, Arrays had me stumped for a while and pointers are evil.

Want me to forward any of this onto my friend? He is an amazing hacker and programmer. He is currently looking into writing kernels
[Galaxy S 4 i9505 Original Android Development] live-evil:
that odin flashable update didn't fix anything either. I also find it odd that this error isn't present in the us variants. There is a samsung engineer somewhere laughing his head off.
[Galaxy S 4 i9505 Original Android Development] BillGoss:
No one has posted one yet. And the slacker who said he'd try is off visiting family - as though that were an excuse! :mad:

Oh, wait, that's me!! :p

Sent from my GT-I9505
[Galaxy S 4 i9505 Original Android Development] invisiblek:
Thought so, but apparently its quite an elusive log to obtain :eek:
[Galaxy S 4 i9505 Original Android Development] mattisdada:
The latest "auto CM updater" semi-bricked my device, highly recommend not to use the automated updater! (It's still in a semi-bricked state, still trying to figure out how to recover without loosing data :/)

Why does it semi-brick the device?

Well, it downloads the ROM, places the ROM in a location so Recovery automatically picks it up and flashes it. But the particular ROM it downloaded was buggy and doesn't actually get past the "Samsung Galaxy S 4" black boot screen, fair enough. But now every time you enter in recovery, it just re-flashes the ROM and reboots, even if you flash on a new recovery, lawl :P, this means no ADB or recovery......

This is just a notice for people in this thread, I am NOT asking for help.

EDIT: Teamwins recovery actually deleted the file on reboot and fixed the "never get back into recovery" issue. Thanks teamwin! :D. But apparently that bad zip corrupted the /system partition, had to reformat with ext4 to actually mount the damn thing :P
[Galaxy S 4 i9505 Original Android Development] NZgeek:
I might have a go at this in the weekend, if I get time. I'm getting odd issues on PAC and plan to move to plain CM, so I may as well get adb working and capture some logs while I'm at it.
[Galaxy S 4 i9505 Original Android Development] thisisfraa:
I had the same issue last week, but I use Philz Touch and apparently that does not remove the file. Like yourself; I did not get the past the Samsung boot logo and I couldn't go back to the recovery since it kept on flashing each time. The only workaround for me was to flash back to stock (which took a while since Odin kept on failing), flash Philz Touch again and then restore a backup I made the day before. From that day on I decided to never use the CM Updater again and I'm just gonna do it manually. Here's a thread I made about the issue back then: http://xdaforums.com/showthread.php?t=2321443
[Galaxy S 4 i9505 Original Android Development] mattisdada:
Ah cool, well I did get around the issue via flashing on via Odin Teamwin recovery (I edited my original post), and after it failed to update once it deleted the file and let me get back into the recovery again, yay. I just flashed on an old CM10 (10.1-20130610-UNOFFICIAL-jfltexx, which has been the best build I've used thus far) and I was back with nothing lost! (I did have to format /system again, it was corrupted and wouldn't let me flash anything over the top! :P)
[Galaxy S 4 i9505 Original Android Development] Stevemeister:
adb pull /tmp/recovery.log
adb shell dmesg > dmesg.txt

This is what you need right? From stock cwm that is.
[Galaxy S 4 i9505 Original Android Development] qpop:
If anybody can explain to me how to install http://www.clockworkmod.com/rommanager the official 6.0.3.2 recovery from a .img file I will happily obtain whatever log is needed. Half an hour of trying has so far ended in failure.
[Galaxy S 4 i9505 Original Android Development] Stevemeister:
Flash via Odin (you'll need to .tar it) or use the Mobile Odin app. Not sure if there is a way to do it via ADB since we don't have fastboot. I think that rommanager can also flash recoverys (touch=payed version).
[Galaxy S 4 i9505 Original Android Development] qpop:
How does one flash a .img? I thought we could only flash .Tar.gz
[Galaxy S 4 i9505 Original Android Development] Stevemeister:
I did it on a stupid but quick other way. I replaced the recovery.img within the flashable zip from Philz recovery with the one on the Rommanager site (you need to rename it to recovery.img) and didnt change the script because I'm to lazy for that lol.
[Galaxy S 4 i9505 Original Android Development] invisiblek:
Almost...

the problem is you won't be able to do the pull if adb stops working after the flash (seems to be the case)

I'd do this:

adb shell "tail -f | dmesg" > dmesg.txt

and

adb shell "tail -f -n +0 /tmp/recovery.log" > recovery.log

Possible other approach would be to start the pipes via adb to the /sdcard and then after it fails, boot back into recovery and pull them. This would probably give an even better log.

adb shell
tail -f -n +0 /tmp/recovery.log > /sdcard/recovery.log &
tail -f | dmesg > /sdcard/dmesg.txt &

the above method would run this in those in the background, they should actually continue to run until you reboot out of recovery
[Galaxy S 4 i9505 Original Android Development] pitcher85:
.

This can easily be done with the SGS4 Flasher.

.
[Galaxy S 4 i9505 Original Android Development] 9Lukas5:
You can

1. Rename it to recovery.img and mobileOdin will flash it as recovery

2. Download SGS4 flasher from Playstore and flash with that

L
[Galaxy S 4 i9505 Original Android Development] simondavies315:
Maybe they have fixed this in the official CWM :/

Try flashing the latest version of Philz CWM Touch and you will get status 7 errors
[Galaxy S 4 i9505 Original Android Development] GalaxyS49505:
Its so hard to remove battery after Error 7 and install it again?
[Galaxy S 4 i9505 Original Android Development] simondavies315:
What are you on about lol
[Galaxy S 4 i9505 Original Android Development] egendomligt:
If that were the case then the issue/discussion would longer belong in this thread. (But I'd be sure to help Phil out ofc)

But to make sure, could someone reproduce my steps to see if it works (apart from the freezes) for you too?
[Galaxy S 4 i9505 Original Android Development] Stevemeister:
This is what i'm getting after a 'succesfull' flash.

-- Installing: /sdcard/0/Download/cm-10.1-20130619-NIGHTLY-jfltexx.zip
Finding update package...
I:Update location: /sdcard/0/Download/cm-10.1-20130619-NIGHTLY-jfltexx.zip
I:using /data/media for /sdcard/0/Download/cm-10.1-20130619-NIGHTLY-jfltexx.zip.
Opening update package...
Installing update...
Warning: No file_contexts
mount: failed to mount /dev/block/mmcblk0p16 at /system: Invalid argument
about to run program [/tmp/backuptool.sh] with 2 args
grep: /system/build.prop: No such file or directory
Not backing up files from incompatible version: 10.1
run_program: child exited with status 127
unmount of /system failed; no such volume
Creating filesystem with parameters:
Size: 2894069760
Block size: 4096
Blocks per group: 32768
Inodes per group: 8032
Inode size: 256
Journal blocks: 11040
Label:
Blocks: 706560
Block groups: 22
Reserved block group size: 175
Created filesystem with 11/176704 inodes and 23193/706560 blocks
about to run program [/tmp/backuptool.sh] with 2 args
/tmp/backuptool.sh: cd: line 72: can't cd to /tmp/addon.d/
find: /tmp/addon.d/: No such file or directory
find: /tmp/addon.d/: No such file or directory
find: /tmp/addon.d/: No such file or directory
cp: can't stat '/tmp/addon.d/*': No such file or directory
script result was [/system]

Grabbing the log after failed flash is indeed a pain.
[Galaxy S 4 i9505 Original Android Development] BillGoss:
It's great to see others trying to get the log files. Happy hunting!

And if the official CWM doesn't have the problem, that's even better.

Sent from my GT-I9505
[Galaxy S 4 i9505 Original Android Development] invisiblek:
Yea... Nothing has changed to fix it though. It still fails I'm sure
[Galaxy S 4 i9505 Original Android Development] Theshawty:
Do we know the exact reason for why it fails?

Sent from my S4 using a futuristic mind controllable Tapatalk 8 private alpha
[Galaxy S 4 i9505 Original Android Development] invisiblek:
If we did, fixing it would be hell of a lot easier. =)

We're having trouble getting a solid log of the error.
[Galaxy S 4 i9505 Original Android Development] ikenley:
Looking at the screen in download mode the following text is displayed:

ODIN MODE

PRODUCT NAME: GT-I9505

CURRENT BINARY: Custom

SYSTEM STATUS: Official

CSB-OEM_CONFIG_LSB: 0x30

WRITE PROTECTION: Enable

Is the last line the same with all Galaxy S4 variants including yours [MENTION=2385005]invisiblek[/MENTION] ?

It reminds me of the S-On issues with the HTC One X. Even though you can root and flash, there are parts that are still locked.

I hope I haven't wasted space by speculating here. I appreciate all the work you have been doing.
[Galaxy S 4 i9505 Original Android Development] invisiblek:
No outside the box ideas are ever a waste of space.

Unfortunately its identical to mine other than the PRODUCT NAME and SYSTEM STATUS (Custom)

If it was a qcom bootloader locking issue, we'd have more issue than just this :silly:
[Galaxy S 4 i9505 Original Android Development] Stevemeister:
The issues are so inconsistent.

- Sometimes recovery won't boot, it says booting recovery in the top left corner but it crashes (happens often after a failed flash)

- Touch input takes a few secs to really detect touch input once recovery booted up (present on all recoverys)

- Sometimes format system makes the recovery crash (usually the first time I try it, sometimes freezes at formatting /system and sometimes succeeds but takes ages and crashes after that)

- If format system finishes quickly flashing the cm zip will always succeed

- Failed cm installation means you need to reflash gapps because they are all deleted (succesfull installation doesnt delete gapps)

- My adb crashes when I use ''adb shell "tail -f -n +0 /tmp/recovery.log" > recovery.log''

Looking for patterns but everything seems to point at that mount/format system error.
[Galaxy S 4 i9505 Original Android Development] invisiblek:
So in this recovery log, I see a backup and a /system wipe

That doesn't really help.

Ideally I'd like a recovery.log after these steps only:

1. Boot into recovery

2. Attempt to flash rom

The dmesg definitely shows some promise though. It appears that /system might be getting corrupt or something odd.

I'll do some investigating this weekend on this. My power is out at home right now so I can't even really check anything out...
[Galaxy S 4 i9505 Original Android Development] Stevemeister:
Got a dmesg and recovery log after failed cache mount (which occured when I tryed to wipe cache)

https://www.dropbox.com/s/mt03ybkoi7d9yu6/dmesg.txt

https://www.dropbox.com/s/um9xgy5u7q130qw/recovery.log
[Galaxy S 4 i9505 Original Android Development] BillGoss:
How did you manage to get the files? I get no ADB connection when I'm in recovery. My PC tells me (sound) that something has connected but an ADB devices shows nothing.

Sent from my GT-I9505
[Galaxy S 4 i9505 Original Android Development] broodplank1337:
Ok just installed latest nightly. First I tried to install it with only a factory format but then there were some problems with /cache and the permissions couldnt be set.

I tried to boot but it didn't work as I was expecting.

Then I rebooted in cwm again and formatted system, and did another factory reset. then installed the nightly and everything worked out just fine.

The first boot had a non responding camera but after a reboot everything worked out well.

Btw its a big difference from the samsung stock rom, my phone gets less hot then it did on the stock rom. (on stock rom my phone just turned off when doing an antutu benchmark with stock settings/kernel and my cpu was like 55 degrees celcius)

Getting around 23k with interactive/row.

Only bug is afaik the led, not bugged actually but just useless. (but I guess this is a common problem with leds and cm). I guess the driver for the led is inside the kernel. and the led management should be handled inside the rom.

Anyways, its running great. no issues found so far.

Ill make my own rom soon using CM10.1 and AOSP ^^
[Galaxy S 4 i9505 Original Android Development] 3bs11:
No issues with calls? By call issues I mean no voice on either end of the call so I can't hear them and they can't hear me. It happens randomly.