yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] Wogz:
Probably the same problem i'm having, see previous post above. Wolfram alpha used to be compatible in omni 6, but not with this rom.

[MENTION=4460995]sooti[/MENTION] help.

PS: Not many people here nowadays, things seem slower than usual.
[Galaxy S I9000 Android Development] tvcsantos:
I want to try this rom over the CyanogenMod 13.0 version of 14/6/16 but it gives me an error saying "can't install this package over newer build"

Can you help me with this please
[Galaxy S I9000 Android Development] Wogz:
strange, which rom installed over which? never seem an error like this before
[Galaxy S I9000 Android Development] tvcsantos:
Sorry forgot to tell which rom :P, I want to install the omni 6.0.1 over the Cyanogen
[Galaxy S I9000 Android Development] Wogz:
That's really strange indeed, but i recommend cyano 13 instead of omni anyway, but hopefully someone has a answer for your error.
[Galaxy S I9000 Android Development] xc-racer99:
You can edit the Omni ROM zip - remove the "assert" with a date in it at the beginning of META-INF/com/google/android/updater-script. This should work.
[Galaxy S I9000 Android Development] tvcsantos:
Actually i agree with you this rom is actually good. The only problem that I'm having is that I can't install google plus I've mentioned before, and I wanted to check out if with omni I can

I'll check if it works thanks
[Galaxy S I9000 Android Development] tvcsantos:
Yup it works thanks. And also with omni i can install google plus, [MENTION=4460995]sooti[/MENTION] can you tell why. And yes after seeing omni I prefer cyanogen.
[Galaxy S I9000 Android Development] tvcsantos:
Ok I got it, the problem was with A-Gapps! Tried a fresh install of the rom but now with open-gapps and it works :) now I can install google plus
[Galaxy S I9000 Android Development] rusiu559:
How to flash gapps from 1st version ?
[Galaxy S I9000 Android Development] TiMiN8R:
I have a kinda big problem. Flashed this ROM over Omni 6.0..1 after full wipe, but now the phone goes into bootloop, then back to TWRP. TWRP can't mount /data, no such device. Could this be a side-effect of the partition resize? And how can I fix this? Preferably without ODIN back to 2.3.6 etc, it's been years since I last had to do that :D

Luckily this phone is just my second back-up phone...

Edit: Okay, so I did go back to Gingerbread, flashed CF-Root kernel with CWM 3 and from there I've tried several different ROM's/kernels/recoveries and upgrade paths but for some reason at some point /data and sometimes /system keep dying on me. Why?

Edit 2: finally after messing around the whole day I got it to work. The installation steps were a little more involved than the ones in the OP. After flashing the ROM zip (for the second time, because of the partition resize) TWRP was unable to mount /data as mentioned. This time I was able to repair the file system on data (ext4) and then could install the gapps. I'm pretty sure I tried this before but couldn't? Guess I'm just rusty...
[Galaxy S I9000 Android Development] Full HD:
Thanks for that information repairing the data partition. I had that bootloops (Start, Samsung logo, reboot, TWRP), too and this step saved me from Odin & flashing stock rom. :good::good: CM13 is booting now.
[Galaxy S I9000 Android Development] Draal:
Now I have installed these rom too. First of skeptical, because of its size, I'm very surprising how fast it runs.

I flashed it from the recovery from the CM 11 nightly with a-gapps what went smoothly.

Until now, it runs extremely well and all functions work smoothly. The synchronization with Google Clouds worked beautifully. :)

Wifi is sometimes a bit sluggish in motion, but then it works perfectly.

The write access to the system partition will not work. Root Uninstaller, X-plore and the terminal can not write because, although they are equipped with root privileges at.

Wogz had, I believe, some contributions reported previously from a similar problem.

Is that so anchored in SELinux?

My intention was to remove some standard apps. I remained only the possibility these apps over the recovery to remove it.

Nevertheless, one fine ROM which will hopefully further developed.

Best wishes

Draal
[Galaxy S I9000 Android Development] johnny87au:
Any instructions how to install all these ? I was just told i need to upgrade to 6.0 from 2.2 (froyo) but there isnt any instructions how to install the rom +Gapps ? im absoulately clueless hehe
[Galaxy S I9000 Android Development] Audiracecar90:
first flash any Jelly bean rom> Kitkat rom> Lollipop rom > android M
[Galaxy S I9000 Android Development] johnny87au:
Well i cant even acess my recovery mode on gingebread? Do you have skype or facebook so u can instruct me? Im kinda new to this stuff and literally stuck for hours lol
[Galaxy S I9000 Android Development] Audiracecar90:
for recovery and download mode please follow the instruction mention in the video
[Galaxy S I9000 Android Development] sooti:
Just a small update:

I have been on vacation and also very busy with work, but now that android N is officially out, you can expect me to start scouting out options for the i9000, no promises or ETA's but since low ram support is supposed to be improved in N, hopefully it will run as well if not better on this device, but again, no promises :) might take months for a first build, so don't message me here with ETA's. ill post an update when there is one
[Galaxy S I9000 Android Development] Wogz:
mind blown. ram support improved in next android. 2x mind blown.
[Galaxy S I9000 Android Development] xc-racer99:
Hey, just so you know, [MENTION=6794010]Coldwindofnowhere[/MENTION] and I have had a booting build. For AOSP, you can check out my patches at https://github.com/xc-racer99/android_patches. The main issues are RIL (rild keeps SIGSEV-ing if I have a SIM in) and hardware decoding/encoding, as well as GPS (the gps libraries are referencing an OpenSSL function that no longer exists in BoringSSL).
[Galaxy S I9000 Android Development] sooti:
Wow nice, how's the performance?
[Galaxy S I9000 Android Development] xc-racer99:
I would say on par to slightly better than Marshmallow. Its especially good considering that I had to disabled datadata because of force-closes (perhaps it would be possible to still use it, but you'd have to mount it immediately after /data was mounted). RAM usage is amazing low, I use only roughly 65% of available ram when doing nothing (this is a CMA kernel, but still).

I'm working on RIL from a weird angle: I'm trying (on Marshmallow first) to get the opensource rild and libril.so working because we were still using the prebuilt rild and libril.so from Gingerbread. I've had some success - I register just fine on the network, SMS works, calls work, but data is totally broken (lots of work to be done here).
[Galaxy S I9000 Android Development] Alokhacker:
1. Is there a way to test i9000 roms without actually having device? using android simulator, studio, sdk? I would like to play with settings before I applying on my device so that even if I mess up it wont break my actual phone.

2. whats is prerequisites for android developer?
[Galaxy S I9000 Android Development] sooti:
Nice! sounds like your making great progress, ill look into getting it working on CM if not ill work on omni since they keep old commits so it should be very easy to build a working build, not sure about RIL
[Galaxy S I9000 Android Development] xc-racer99:
To the best of my knowledge, there is no way to test an i9000 ROM without actually using it on an i9000. If you're talking things like Xposed, etc, then I guess you could probably build for the emulator and run it on that, but it wouldn't have any i9000-specific bugs.

Here's the development guide that I always like to use:

:D

Yeah, its going ok. I'm quite unsure as to what the issue is with RIL - using the RIL stack I built for Marshmallow, it also SIGSEV's in Nougat... I think I'll try with the Replicant RIL stack and see if I can get it working. It might be (another) google bug - there's been two of them that the Galaxy Nexus team has had to work around (one with converting relative to absolute timespecs and the other with the standard libril.so not accepting a simcardv5 response (when the specs say that it should).

If you do get a build booting, the thing to work on would be hardware encoding/decoding. I have no idea why its broken but haven't invested any time into it.

I can send you some device tree and kernel patches as well, if you want. I do not think that Omni would be any better than CM as they no longer support many legacy devices.

Edit: If someone could send me a radio log from an i9000, that would be great. I'm having to add support for my own modem (m5730), and it's different than the xmm6160 in your phones.

Edit 2: Nevermind, I've found a radio logcat online.
[Galaxy S I9000 Android Development] jupiter5700:
Hi, sooti! Can you try to add tv-out support in this amazing rom please?
[Galaxy S I9000 Android Development] _Peek:
Latest i9000 stable config

Flashed 2x Samsung Galaxy S units today as follows:

Device Model: GT-I9000

Android version: 6.0.1

CyanogenMod version: 13.0-20160613-UNOFFICIAL-galaxysmtd

GAPPS version: open_gapps-arm-6.0-pico-20161217.zip

Baseband version: I9000XXJVT

Their intention is to be the kids' first training phones. However the 4.4.2 ROM lost against our patience.

Performance "enhancements" once the ROM is operational:

Set ro.config.low_ram -> false

Transition Animation Scale -> 6x

Window Animation Scale -> 6x

However, I can't find the option to set the processor governor's min & max speed to 1400 & 200 accordingly...

The last hurdle being the /data partition's size. At present I'm playing with Launchon's REPIT to try and resize the /system partition to 2GB & the /data partition to include all of the /sdcard partition. Hoping to have around 6GB on the /data partition to ease storage requirements with app installations. The /data partition is also set to F2FS, though the ROM still reformats the /system partition to EXT4.

Is there a REPIT formula that worked best for the i9000 ?

Also, is there any point in rooting these ROMs ?

Thanks
[Galaxy S I9000 Android Development] chrixiss:
I have had it work for weeks with me, but today my phone ran out of battery while it crashed and now it won't start up.

It just gets stuck during start up on the animated CyanogenMod logo, but for like an hour without anything else happening.

How do I now launch it in recovery mode? Starting up with the volume up and home button pressed isn't working, it just does a normal startup.
[Galaxy S I9000 Android Development] Rhods23:
Hi, I have a gt-I9000b (brazilian model with digital TV) and when I try to install this ROM via CWM, a message shows that this model is not supported. What file I need to change to make works?

Thanks.
[Galaxy S I9000 Android Development] Coldwindofnowhere:
In /META-INF/com/google/android/updater-script you'll have somehting like that :

assert(getprop("ro.product.device") == "galaxysmtd"||
abort("This package is for device:galaxysmtd; this device is " + getprop("ro.product.device") + "."););

Remove those lines and error 7 will be gone. Not sure if the rom will work fine with your variant but this will surely solve your issue.
[Galaxy S I9000 Android Development] laharl_22:
Hello i have a big problem when i flash this rom over omni 5.1.1 it boot to new twrp and i have unable to mount data and storage on flash or full wipe .how fix that please?
[Galaxy S I9000 Android Development] jupiter5700:
Remove battery then try again.
[Galaxy S I9000 Android Development] laharl_22:
Thanks it solved i was forgot to format data in f2fs partition
[Galaxy S I9000 Android Development] k2-18b:
Camera App - open-camera-1-31

With Open-Camera (1-31) the picture does not get stuck.
[Galaxy S I9000 Android Development] k2-18b:
Switch between Network Types isn´t possible ???

So am I. Settings > Cellular > Preferred network type > it´s fixed 3G.
[Galaxy S I9000 Android Development] k2-18b:
How to install coming from rooted Gingerbread 2.3.6

Coming from rooted Gingerbread 2.3.6 (GT-I9000_XWJW9_JW3_DBTJW2; CF-Root-XX_OXA_JW4-v4.4-CWM3RFS).

Pre-Caution

cm-13.zip on internal sdcard, USB-Debugging is activate, Accu is about 80%

ClockworkMod Recovery (v.3.0.0.5)

wipe cache partition

advanced > Wipe Dalvik Cache

install CM-13.zip from sdcard

=> This VERSION uses an incompatible partition layout. Your /data will be wiped completely. .So, make your backups then just run this update.zip again to confirm install. ATTENTION ==== assert failed: run_program("/tmp/updater.sh") == 0 E:Error in sdcard/FIRMWARE 2020.11/cm-13.0-20160614-UNOFFICIAL-galaxysmtd.zip (Status 7) Installation aborted.

don´t reboot

install CM-13.zip from sdcard

=> Galaxy Logo appears….. TWRP 3.0.2-0: Running OpenRecoveryScript, Unmodified System Partition

TWRP Recovery 3.0.2-0

Swipe to Allow Modifcations

=> TWRP Menue Status quo: Mount: Cache yes , System and Data can´t, SDCard could. File-Format: Cache yaffs2, System ext4, Data = auto, SDCard = vfat, Android Secure X, MicroSDCard vfat

Wipe > Swipe to Factory Reset

Status quo: Mount: Cache and SDCard yes, System and Data

install CM-13.zip from sdcard

=> Formattig /system Extracting /system …… Error…..Failed to mount data Status quo: Mount: Cache and SDCard yes, System could, Data can´t

Reboot > Recovery

=> Galaxy Logo, galaxy logo, TWRP Status quo: Mount: Cache and SDCard yes, System could, Data can´t

Mount > System

Wipe > Advanced Wipe > Data > Repair or Change File System > Change File System > f2fs

Status quo: Mount: Cache, System, data, System, SDCard yes

install CM-13.zip from sdcard, and wait about 2 minutes

=> Formattig /system Extracting /system …… Symlinking Flashing boot.img CM-13 flashig complete! Script succeeded: result was [/system) Updating partition details… ...done

Wipe cache/dalvik

Reboot System

CM-13 Boot animation appears

I have hardly any knowledge in Android and have tried and reproduced this way. The system starts and works fine. If anyone knows better, please correct me! :highfive:

:rolleyes:
[Galaxy S I9000 Android Development] k2-18b:
For everyday use without internet

Since I have no Android knowledge I had to try it out. My starting point was a device with Android 2.3.6 Gingerbread (GT-I9000_XWJW9_JW3_DBTJW2) that was already rooted (CF-Root-XX_OXA_JW4-v4.4-CWM3RFS).

If I have correctly understood the few posts here in the forum, the S1's bootloader and the newer TWRP installation or flash routine do not speak the same language. This incompatibility can be bridged "somehow" via the detour of a double installation - somehow, because I unfortunately don't have the necessary know-how to describe the matter aptly - and Cyanogenmod 13 can be installed on the i9000.

A test with Antutu v5.7.1 with the newly installed CM-13 resulted in 8,500 points, an internal SD card formatted according to f2fs brought another gain in CM-13 from 1,000 to 9,500 points. I do not yet know how the internal SDCard format changed after f2fs will work. LineageOS 14 scored 7,100 points and Cyanogenmod 11 reached 6,500.
[Galaxy S I9000 Android Development] k2-18b:
Installation from rooted Gingerbread 2.3.6

Gingerbread 2.3.6 (GT-I9000_XWJW9_JW3_DBTJW2) with CF-Root (CF-Root-XX_OXA_JW4-v4.4-CWM3RFS).

Precaution

cm-13.zip on internal sdcard, USB-Debugging is activate, Accu is about 80%

in ClockworkMod Recovery (v.3.0.0.5)

wipe cache partition

advanced > Wipe Dalvik Cache

install CM-13.zip from sdcard

This VERSION uses an incompatible partition layout. Your /data will be wiped completely. .So, make your backups then just run this update.zip again to confirm install. ATTENTION ==== assert failed: run_program("/tmp/updater.sh") == 0 E:Error in sdcard/FIRMWARE 2020.11/cm-13.0-20160614-UNOFFICIAL-galaxysmtd.zip (Status 7) Installation aborted.

don´t reboot

install CM-13.zip from sdcard

Galaxy Logo appears….. TWRP 3.0.2-0: Running OpenRecoveryScript, Unmodified System Partition

now in TWRP Recovery 3.0.2-0

Swipe to Allow Modifcations

TWRP Menue Status quo: Mount: Cache yes , System and Data can´t, SDCard could. File-Format: Cache yaffs2, System ext4, Data = auto, SDCard = vfat, Android Secure X, MicroSDCard vfat

Wipe > Swipe to Factory Reset

Status quo: Mount: Cache and SDCard yes, System and Data can´t

install CM-13.zip from sdcard

wait about 30 seconds

Formattig /system Extracting /system …… Error…..Failed to mount data Status quo: Mount: Cache and SDCard yes, System could, Data can´t

Reboot > Recovery

Galaxy Logo, galaxy logo, TWRP Menue Status quo: Mount: Cache and SDCard yes, System could, Data can´t

Mount > System

Wipe > Advanced Wipe > Data > Repair or Change File System > Change File System > f2fs

Status quo: Mount: Cache, System, SDCard yes, data can.

Mount > data

install CM-13.zip from sdcard, and wait about 2 minutes

Formattig /system Extracting /system …… Symlinking Flashing boot.img CM-13 flashig complete! Script succeeded: result was [/system) Updating partition details… ...done

Wipe cache/dalvik

Reboot System

CM-13 Boot animation appears.
[Galaxy S I9000 Android Development] Myjosito:
Hi all

Thanks for this wonderful Rom.

I know the thread is quite old now, but let's hope someone can give me a hand :)

I'm installing it through TWRP, no big issue during installation, can manage to Wipe/mount/install things.

Installing beta 4 from sooti (thanks man !) + A-GAPPS_601_01092016_v6.0 from dracov76 (thanks also ;)).

then wipe cache+Dalvik and boot logo's there.

Need some time to setup things (crash sometime), but I can finalize anyway...but my biggest problem is probably the remaining 16M Memory I have to deal with at the end. I could activate Bigmem, but no big change at the end, things are quite slow, and I can't install anything from the market. I suppose everything is linked of course, the rom itself seems perfect to me, if only I could increase memory and if the market could let me install programs...

I could setup a 8Gb sd card as internal, but I couldn't see any improvement at all. which I guess is strange...

One thing: I can't activate the Developer mode when I do the 7x click on "Build" stuff. Tried many times, it doesn't work with this rom for me (though it works with "reductionEdition" rom, but I have the Wifi loop issue with this one...). Did I miss sometihing ? (Of course I did ! ;) )

I suppose I should setup partitions size in TWRP... any suggestion please ?

Thanks in advance :)

and happy new year for all of you !
[Xperia Z5 Q&A, Help & Troubleshooting] vincent-h:
I got the Marshmallow update this morning on my phone. After updating all was good until it restarted and now after it all loads it all I see is a black screen with the error: "Unfortunately, System UI has stopped."

I cannot get into the android interface to do anything the most I can do is just constantly restart the phone. Are there any suggestions on what I can do to fix this or get it out of this pretty much bricked mode?

Thanks,

Vincent
[Xperia Z5 Q&A, Help & Troubleshooting] gm007:
Use xperia companion and repair ur phone.
[Samsung Gear 2] Faspaiso:
Hi

I really like the Samsung Gear S2, but if they drop updates like this, when the watch is 2 years old? I rather get a Android Wear, as at least they keep updating it for more than two years. I can see the last update for this watch is 24-04-22, which is a year after it's released, all development from Samsung has stopped. Is this normal Samsung procedure or is there a special reason that they stopped on this device (like they sold too little)?

So do you think that I can get updates in the future from Samsung if I buy a new one or should I just buy an Android Wear?

Thanks in advance
[Samsung Gear 2] RiverCity.45:
Typical of Samsung. They put out new tech so often, they drop support quickly. Samsung is known for this, unfortunately.
[Samsung Gear 2] the dreamer:
We need an update for gear 2
[Samsung Gear 2] markek:
I agree. Specifically one that would allow it to work with the new Gear Manager for iphone.
[Kindle Fire Q&A, Help & Troubleshooting] villainous:
Forgive me if I am not describing this in the best terms.

My fire was stuck at the kindle fire logo, it would load for 2 seconds to the kindle fire logo then turn off and boot to the logo once again, non-stop.

I plugged in my fastboot cable and it immediately booted into fastboot. While connected to fastboot I opened the Kindle Fire utility and under one option was the option to boot into recovery. My thought was, if I could force it to boot into TWRP I could fix permissions/wipe cache or something like that to get it working.

It immediately disconnected from my computer (the noise the computer makes when a USB is disconnected) then it went on connecting and disconnecting non-stop. The screen turned on to kindle fire logo, then to fast boot logo then went black, the entire time it is connecting and disconnected to my computer, making the connection tone then disconnection tone every other second.

I unplugged the kindle then held the power button for 60 seconds, this seemed to turn it off. I hit the power button again, while still unplugged and it shows the kindle fire logo, immediately followed by the fastboot mode logo, then the screen goes off. If i plug it into the computer it is making the connect/disconnect noise.

I feel like if I could get it to stay in fastboot I could use the recovery tool to fix it, but at the moment it is just cycling non-stop and cannot be connected to the computer.

Any ideas?

Thank you for any help you can give me.
[Kindle Fire Q&A, Help & Troubleshooting] villainous:
FIXED

Okay, great news, I fixed it. After trying a combination of EVERYTHING I could find on the internet, a dozen programs and images. So, here is how I did it.

At the windows command prompt I entered the command: fastboot -i 0x1949 getvar product

this was while my device was constantly connecting and disconnecting, launching straight into fastboot. So the command did not execute right away, it would say < waiting for device >

While plugged into the computer, I held the power button for 20 seconds to shut off the device, then hit the power button to restart the device. The moment the device turned on, before it would power cycle, the command processed and the device would stay on, at the fastboot screen.

Downloading KFHD_SRTv1.3.5 I opened that program. Giving me options to restore the device. I did an ERASE CACHE AND USERDATA (Options 4), once that completed I did the RESTORE-FACTORY RECOVERY (Option 3).

I tried to reboot right here but it would AGAIN begin power cycling through fast boot.

I went back to my command prompt and issued the command: fastboot -i 0x1949 reboot

The device rebooted to the kindle fire screen and DIDN'T go to fastboot, it DIDN'T power cycle. It took a few minutes to load, but when completed it loaded the stock amazon application.

This took me a couple hours, I tried a lot of different methods and a LOT of different boot.img, recovery.img, system.img. I downloaded 15gb of files trying different thing. This worked for me.

Good luck all.
[Elephone M2] skeleton1911:
Elephone M2_S150_20160219_ based on Android 5.1

VibeUI

Rom flashing :

1. Download the ROM and use flash tool Flashtool link

2. Unzip the ROM

3. Install the flashtool and drivers

4. Flash the ROM with it

Download Link :

https://mega.nz/#!3AY3nZQb!y_A1VgZNVO1U9K0nUSAVNdHwpuUTM3qJLTLxx3PFLqo

bugs also reply here: Click

​
[Elephone M2] shingers5:
no one tried this?
[Elephone M2] john_d1974:
im gonna try it, head over to

http://bbs.elephone.hk/forum-294-1.html#.VxXRutQrKt_

thats where all the ROMS come from
[G4 Q&A, Help & Troubleshooting] 804Hokie:
So last week, I had to get a replacement device, after my VS 986 was exposed to too much liquid water. However, the replacement G4 they sent, doesn't have a clear Serial Number like the new one I had before. I'm concerned about the earlier manufactured devices (particularly the ones starting with "505"), but have no way to know which one they sent me advertised as "like new."

Edit: Second Issue resolved
[G4 Q&A, Help & Troubleshooting] welder73:
Install "Lg Phone From" from the Play Store and you'll know your serial number...

Sent from my LG G4