yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Q&A, Help & Troubleshooting] JJSJJS:
Hi, i'm new in these things so have a few questions.

Iwould like to flah thecyanogenmod but my galax 2s syas it is not a gt-I9100.

So i read some things about removing the assert line from a script and so on.

Do i need to flah an older rom before the cm11 nightly?

Do i need to flash the kernel first? or just use the latest cwm? (or rom manager/clockword?)

Can i reflash the S2 with an cyanogenmod kitkat version after i flashed it with an other kitkat rom for this device?

(still i did not succed to flash any rom to it)

thanks for any help !
[Galaxy S II Q&A, Help & Troubleshooting] vishal11in:
First of all check if it g version or not.

To best of my understanding you can install it directly as far as you are rooted.
[Galaxy S II Q&A, Help & Troubleshooting] banjara:
You don't need to flash an older version before KK. You just need KK compatible recovery. Or you can flash a KK compatible kernel, reboot to recovery and flash your KK rom.
[Galaxy S II Q&A, Help & Troubleshooting] JJSJJS:
Hello, thank you both for your replies.

Finally some clear answers :)

The model says GT-I9100 and not with g behind it, thanks.

I found some things about the status 7 error and about removing some line in a script in the zip.

So i will try the kitkat recovery (in my understanding this is also the kernel?) and then flash it with kitkat rom.

I would like to flash the one from cyangenmod, but doe it really mather which custom kitkat rom i take? At least they are all without the providers code like Vodafone or others?

Thanks again. I will update the thread if it succeeds or not.
[Galaxy S II Q&A, Help & Troubleshooting] JJSJJS:
Hi,

so i could not install the latest Recovery_CWM_6.0.4.7_I9100.zip as it gave an error E: signature verification failed.

then i tried recovery-clockwork-touch-5.8.1.5-galaxys2.zip and this works. But with this i can't install CM11. as i get the status 7 error.

So i will try some other versions kitkat compatible.

I also took a look at the kernels section but it is not clear wich one to use for CWM6 as i don't know what XXLSR or DDLS3 means, and which is correct for Netherlands.

Do you have any idea? (i am not allowed to post there yet)

Thanks for your help.
[Galaxy S II Q&A, Help & Troubleshooting] banjara:
For choice of kernel -

1. Gustavo's - I don't remember the version. Check the op.

2. Dorimanx - you can try 10.43v100.

3. Apollo - 7.0b Cm

They will bring the KK compatible recovery you want on your phone. Then after rebooting to recovery you can flash any custom rom as they are not locked by any carriers.
[Galaxy S II Q&A, Help & Troubleshooting] JJSJJS:
Thank you very much Banjara !

i'll keep trying, will report if i succeed ;)
[Galaxy S II Q&A, Help & Troubleshooting] JJSJJS:
oh oh no good.....

oh boy oh boy

i followed this http://xdaforums.com/galaxy-s2/development/kernel-lazing-safe-stock-kernels-t2293576

and now it is stuck on boot screen, can't even reboot in recovery mode to get the back rom back pfffff

what should i do now......even the usb cable aint working, i'm flashing to the external sdcard via an other phone and the replace the sdcard to the galaxy s2

thanks for any help :crying::crying::crying::crying::crying:
[Galaxy S II Q&A, Help & Troubleshooting] banjara:
If you are able to go back to download mode

1. Flash a stock rom via odin

2. Flash a custom kernel via Odin. You might find some in the link you put there or you can search for hirox kernel. Remember, you have to download Odin flash able kernel and follow the op.

3. Once you have custom kernel, reboot to recovery. Flash any of the kernels in clockworkmod mentioned in my previous post.

4. Reboot to recovery. Flash your rom.

If you are unable to go to download mode try all the methods mentioned in the below link to bring it back to normal. It will need patience and perseverance. http://xdaforums.com/galaxy-s2/general/guide-t2345831
[Galaxy S II Q&A, Help & Troubleshooting] JJSJJS:
Thank you for your patience and your help Banjara.

This forum and it's people are 100 times better the on Gyanomed were totally no support is given...

I will try it and come back, at least the phone able to start in the download mode.
[Galaxy S II Q&A, Help & Troubleshooting] JJSJJS:
Probably the usb connector has some loose contacts as i can get no contact with pc.

I got this phone from my brother and he told me that it never worked, just loading the battery

So i tried an other cable from an cheap android pad, but also no luck

maybe tommorow, i have another cable from an android stick pc at my job, maybe it will work

else i have to open it to check the connector under a microscope and probably resolder(hotair) it with a lot of flux... what a pitty... :crying:

lucky i have some experience on it, i repaired a lot of qtek phone, some years ago, always that connector broken.

I'm originally an tv(crt,lcd,plasma) repair technician, but now on an other job
[Galaxy S II Q&A, Help & Troubleshooting] JJSJJS:
Pfew, i managed to rsolder the connector with help of the microscope on my job. :)

I could even connect to odin. :D so that's is good progression. i had a wrong kernel downloaded, so it failed.

now i have the correct one and will use Siyah-s2-v6.0b5.tar

But unfortunately the battery is really emptying quickly when it stays in the phone, i don't know why.

So i will have to charge it an then give it another try with this kernel.

The ROM should still be original as i did not flash it before, just the kernel.

The phone is now saying battery empty, can't download.

To be continued...
[Galaxy S II Q&A, Help & Troubleshooting] JJSJJS:
Jippieeee!

GREAT !!!!

It worked! flashed the kernel Siyah-s2-6.0b5 and it started ! :victory:

Now what is the best way to proceed, there are so many topics on this it is overwhelming.

Should i first flash a Kernel or first a rom?

Can i flash them right after each other? (kernel reboots) so ROM and directly Kernel in one go?

thanks for your help!
[Galaxy S II Q&A, Help & Troubleshooting] JJSJJS:
{SOLVED}

Ok this is solved, thank you guys and dolls !

i managed to flash the cwm 6++++ and then the OMNI kitkat (latest) and the gAPPs

and it is working ! i am verry happy ! :laugh::laugh::laugh::laugh::laugh:
[Galaxy S II Q&A, Help & Troubleshooting] banjara:
:thumbup::beer::beer:
[Galaxy S II Q&A, Help & Troubleshooting] JJSJJS:
one more thing

i noticed there is also another kernel now in the phone.

How to get rid of the yellow exclamation mark?

i saw some footage on youtube how to do it with the correct kernel.

But can i also extract the kernel from the ROM.tar i used and flash it with Odin?

Or is there another way?

thanks for your help. ---> edit

ok found some here: http://xdaforums.com/galaxy-s2/orig-development/30-10-2012-k-la-lp-t1103399

but is it also good enough to unroot your device or are some functionality's then lost when using OMNI- rom ?

Thanks for your help
[Galaxy S II Q&A, Help & Troubleshooting] Radelos:
there arent any funcions lost it just gives your phone informations so that it thinks its all fine and dont displays the yelow horror :p . Btw i used TWRP KK kernel on my gs2 and installed prerooted rom aosp neatrom 5.8 kk and dont have problems with triangle. Also neatrom 4.1.2 with extended battery life is there if you dont like kitkat =D
[Galaxy S II Q&A, Help & Troubleshooting] JJSJJS:
Thanks Radelos, then i will try to unroot it again. And that will be it then.

Now using the OmniKK nightly of 8th of june, it runs very smooth, no issues till now, all is working well. :good:
[Galaxy S II Q&A, Help & Troubleshooting] Radelos:
btw idk what is the exact rom your willing to use but for no triangle would also do an clean install of stock rom, then root with framroot that you can find here on site and then flash KK compatible recovery and ofc kk rom with it. Here is the rom i used, its prerooted and on first boot starts direct into recovery so its for lazy ppl =D factory format data/system then flash TWRP touch recovery and in cwm reboot recovery option. And then just flash rom

Rom

http://uloz.to/x13p4YVr/drhd-base-lpq-re-light-tar

KK TWRP touch recovery

http://uloz.to/xyw9UkTk/kk-kernel-21-04-twrp-zip
[Galaxy S II Q&A, Help & Troubleshooting] banjara:
So with this process, will there be no yellow triangle?
[Galaxy S II Q&A, Help & Troubleshooting] JJSJJS:
I flashed the Omni rom and it's working great!

if i install a tool to root and unroot, would'nt it remove the triangle when i unroot it? (framaroot won't unroot it now with this rom, maybe there is an other tool which works with omni rom. I don't want to reflash it again with another rom actually as it works good now.
[Galaxy S II Q&A, Help & Troubleshooting] banjara:
AFAIK, you can't unroot your device unless you flash stock rom again. With a custom rom it's simply not possible.
[Galaxy S II Q&A, Help & Troubleshooting] JJSJJS:
Thanks for letting me know.

I think i'll leave it then the way it is, it don't really bother.

It's working great! Big thumps up to the dev's.
[Galaxy S II Q&A, Help & Troubleshooting] Radelos:
well there is still an option to flash an unrooted kernel that is compatible and then try to root it, but dont know if it would remowe that yellow death from start screen caus i newer rly had that problem. Best would be to reset your download mode counter with an USB jig if all other options fail. Then you wont have any yelow triangle there. You may have to plug the jig in and start like this download mode a few times if it dont work on first :) its also easy to make one home, just need an mikro usb conector + rezistor 301K ohm.
[Galaxy S II Q&A, Help & Troubleshooting] JJSJJS:
Great !

Thanks Radelos. I also saw something like this on youtube with some resistors (3 in series) But it was not said from which pin to which pin it should be connected. Mostly such things are connected from +5V to a data pin or from a data pin to ground. I will google some and see if i can find it exactly.

edit---> ok here http://xdaforums.com/galaxy-s2/help/guide-how-to-make-usb-jig-reset-binary-t1604707
[Samsung Galaxy Nexus] decon89:
Hi everyone,

So yesterday I decided to turn off my phone to save some juice. Now when I try to turn it on, I just get stuck in a boot loop with paranoid android 3. I try to boot into recovery (vol up + standby/power), but since it's been so long since I lasted rooted and flashed my phone, I sort of forget which recovery I had installed. To my surprise I find nothing of use, but a message telling me 'not to turn off target'. Took this picture with my webcam, sorry for the lake of pixels in the image :) http://www.takepictureonline.com/viewPicture.php?Fl=0411277e06c1e8ddb1716cc908d11db6.jpg

Any tips on the next steps here? I wouldn't mind to reflash or anything, but I can't seem to get anywhere from here.
[Samsung Galaxy Nexus] Thymo:
"Do not turn off target" is odin mode not recovery.
[Samsung Galaxy Nexus] decon89:
Thanks Thymo, I'll try and take it from here. Stupid me forgetting that I had to push both volumes keys to access fastboot mode.
[Galaxy S III Q&A, Help & Troubleshooting] Swiifty:
I accidentally updated my gs3 and now when I try to saferoot it I get "your kernel is patched". Is there any safe work around to root my device?
[Galaxy S III Q&A, Help & Troubleshooting] boomboomer:
Best ask in the right forum, see the stuck thread for north American phones.
[Galaxy S III Q&A, Help & Troubleshooting] S /\ E E D:
Use framaroot:

http://xdaforums.com/apps/framaroot/root-framaroot-one-click-apk-to-root-t2130276
[RAZR HD Original Android Development] skeevydude:
reserved for other things
[RAZR HD Original Android Development] skeevydude:
and a third just in case

EDIT: Feel free to post rom tweaking and compile questions and advise while I'm finishing the guide up. There's quite a bit of content and I'd like to make sure it's correct and working before posting.
[RAZR HD Original Android Development] CWGSM3VO:
So I've done some testing with the Linaro toolchain and the HD. General consensus (and source) seems to indicate the S4 Plus in the device is closer to the Cortex-A9 than the Cortex-A15 but has some extra goodies that "kind of make up for it".

Testing against both the A9 and A15 optimized toolchains, the A9 feels "better" but the A15 works just fine too. Main problem is the razrqcom source in CM11 defaults to A15 so there lies a problem. I will probably have to bite the bullet and compile my own optimized A9 toolchain with VFPv4 (vs VFPv3) and see how it turns out.

Either way, the performance benefit is clearly there. Benchmarks somewhat reflect it but "real world use" it shines vs non-optimized. Once I'm happy, I'll post my findings so others can try their hand at it.

EDIT: I'll make two builds available and update this post. Both are identical except for the toolchain + arch related opts applied. One is Cortex-A15 tuned and one is Cortex-A9 tuned. You decide from there. Keep in mind I'm still using the default GCC (4.7) with no special optimizations applied to it other than for ARM (under build/); everything else is stock and I'm not using my own toolchain yet.
[RAZR HD Original Android Development] Zeljko1234:
So great to follow this thread! Looking forward to test optimized build, especially with the new kernel.

Huge thanks!
[RAZR HD Original Android Development] skeevydude:
Did you ever manage to compile the toolchain with VFPv4?

And I never go by benchmarks other than real world performance in apps...like FPS in ProjectM or FPse...run the wrong IO scheduler during a benchmark and get a bad score, cheat and swap io schedulers during the read/write tests and have *****in scores...benchmarks are too easy to cheat, and due to caching, memory management, etc, lower numbers don't necessarily mean crappier performance ;)
[RAZR HD Original Android Development] CWGSM3VO:
No I haven't gone that far yet. It would only be applicable to Cortex-A9+VFPv4. One thing I've noticed running the A9 optimized build is that while it seems to perform almost as well (In most cases) as A15 optimized builds do but seems to run into some kind of I/O stall. I can mitigate it from changing to deadline (from ROW) but this isn't necessary in the A15 builds.

I did (earlier) a quick grok of the source tree for particular flags and seems armv7-a and A15 is the general assumption. I'm now since eating crow because the A9 build is running into intermittent stalls (I see it in the UI, response time is 0 for a split-second). Given the source assumptions and performance I've seen with the A15 builds, it makes sense for me to pursue that build. Unfortunately one performance gain to be had would be very time consuming because it's scattered throughout the tree would be to change the float abi to hard as the compatibility (at the sake of performance due to overhead) is preferable for something like CM11 versus a personal build.

For benchmarking, I've only been using Quadrant standard. Mainly because it gives me a chance to visually see the differences. Memory I/O scores are in the 11-12K range currently, much higher than I ever got with stock repo. I'm not quite happy with a few things and would like to reduce my footprint into the source. But I do have both an A9 and A15 test build ready, just need to upload them somewhere if anyone wants to play with them (I'll try to get this done soon, done!).

A9: http://www.filedropper.com/cm-11-20140609-unofficial-motomsm8960a9

A15: http://www.filedropper.com/cm-11-20140609-unofficial-motomsm8960-a15

Through work, I might be able to lay my hands on ARMcc and would like to play with that. Their opensource/free offerings of course don't include the compiler.

I think from here, it's worth exploring expanding this to beyond the toolchain.

EDIT: It should be worth noting these screenshots are based in Interactive/Deadline (stock) settings. Didn't bother going into airplane to "get that extra bit" ;) One is A9 and one is A15, guess which is which :) Also, no -O's were hurt during the making of this project, everything is stock (-O2, very safe opts) compiler flag-wise except where A9/15+NEON are applicable.
[RAZR HD Original Android Development] CWGSM3VO:
I've since updated my build to use Linaro 4.7.4 for the host compilation. Everything else is the same, see how it goes (letting it compile overnight). I'm definitely sticking with A15 over A9, I'll post more updates in the morning, wiped out :)
[RAZR HD Original Android Development] skeevydude:
According to this, we're really close to arm A12.

Redoing my android_build picks from last night. Hopefully not being exhausted will make a difference.
[RAZR HD Original Android Development] CWGSM3VO:
There are enough differences to make it hard to peg the Krait as an A9, A12 or A15 :) Curious to see how A12 turns out for you. Everything I've been able to find, it's more "like a" A9 than an A15.
[RAZR HD Original Android Development] skeevydude:
I'm not testing A12...at least not right now...wasn't even able to get a standard O2 build to compile last night, getting cc1 errors with .o's

But on that chart, we're really close to 12, more-so than we are A9.

Just thought it curious.

Anyhoo, redid everything, might have missed a single endif last night that was causing my errors, we'll see.

I hope this works, I'd like to move on to finishing that part of the guide then getting a 3.4 kernel build of PAC going...not that I can run it, but some of ya'll can.
[RAZR HD Original Android Development] skeevydude:
Figured out my build errors....-Werror....that cflag is annoying, but I didn't do the remove that flag fix, instead appended -Wno-error=unused-parameter to the parts failing, and so far the build seems to be running good.

Starting a second build with a different set of tweaks (may not finish, using Ofast...), when done, will start a third build with a different set of tweaks, and I'll upload all three when I'm done. There will not be a repo sync between builds so the only differences will be cflags, o level, and gcc.

Probably won't finish the 2nd post until tomorrow evening, until then, here is my local manifest if you want to compile PAC with Archidroids V2...I could probably update it to V3...reverted to V2 cause that worked flawlessly a week ago...it had the same build errors as V3...damn 4.4.3 update messing with me...

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<!-- REMOVALS -->
<remove-project name="android_art" />
<remove-project name="android_bootable_recovery" />
<remove-project name="android_build" />
<remove-project name="android_hardware_qcom_display-caf" />
<remove-project name="android_system_vold" />
<remove-project name="android_vendor_pac" />
<remove-project name="platform/prebuilts/gcc/linux-x86/arm/arm-eabi-4.7" />
<remove-project name="platform/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.7" />

<!-- ADDS -->
<!-- ARCHIDROID LINARO TOOLCHAINS -->
<project name="JustArchi/Linaro" path="prebuilts/gcc/linux-x86/arm/arm-eabi-4.7" remote="github" revision="4.7-eabi" />
<project name="JustArchi/Linaro" path="prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.7" remote="github" revision="4.7-androideabi" />
<project name="JustArchi/Linaro" path="prebuilts/gcc/linux-x86/arm/arm-eabi-4.8" remote="github" revision="4.8-eabi" />
<project name="JustArchi/Linaro" path="prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.8" remote="github" revision="4.8-androideabi" />

<!-- Google 4.8 TOOLCHAIN -->
<!-- Uncomment the two lines, comment out both Linaro 4.8s, then repo sync to change toolchains -->
<!-- <project name="platform/prebuilts/gcc/linux-x86/arm/arm-eabi-4.8" path="prebuilts/gcc/linux-x86/arm/arm-eabi-4.8" remote="aosp" revision="master" />
<project name="platform/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.8" path="prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.8" remote="aosp" revision="master" /> -->

<!-- MY MODIFIEDS -->
<project name="skeevy420/android_art" path="art" remote="github" revision="pac-4.4" />
<project name="skeevy420/android_bootable_recovery" path="bootable/recovery" remote="github" revision="pac-4.4" />
<project name="skeevy420/android_build" path="build" remote="github" revision="pac-4.4" />
<project name="skeevy420/android_hardware_qcom_display-caf" path="hardware/qcom/display-caf" remote="github" revision="pac-4.4" />
<project name="skeevy420/android_system_vold" path="system/vold" remote="github" revision="pac-4.4" />
<project name="skeevy420/android_vendor_pac" path="vendor/pac" remote="github" revision="pac-4.4" />

</manifest>

EDIT:

Build 2 complete, waiting on apk's to optimize then build 3 starts.
[RAZR HD Original Android Development] skeevydude:
Two test builds uploaded, third one compiling, poll, links, and description in PAC thread.

EDIT: Third build available in Pac post 13 (same as the others)

That build marks 3 successful builds with various Archidroid & GCC options.
[RAZR HD Original Android Development] CWGSM3VO:
So as I get more and more into this, I realize I might be missing something. Here's what I got so far:

- Linaro 4.7.4 host compiler under prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.7 and this is verified by running prebuilts/gcc/linux-x86/arm/arm-androideabi-4.7/bin/arm-linux-androideabi-gcc --version which reports Linaro GCC 4.7-2014.04-1~dev 4.7.4 20140402 (prerelease)

- Linaro 4.7.4 toolchain under prebuilts/gcc/linux-x86/arm/arm-cortex_a15-linux-gnueabihf-linaro_4.7.4-2014.04 and build/envsetup.sh is hardcoded to use this path. GCC in there reports as arm-cortex_a15-linux-gnueabihf-gcc (crosstools-NG linaro 1.13.1+bzr2651 - Linaro GCC 2014.04 - Cortex-A15) 4.7.4 20140402 (prerelease)

case $ARCH in
x86) ..
arm) toolchaindir=arm/arm-cortex_a15-linux-gnueabihf-linaro_4.7.4-2014.04/bin
..

My local_manifests/gcc.xml contains:

<remove-project name="platform/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.7" remote="github" revision="4.7-androideabi" />
<project name="JustArchi/Linaro" path="prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.7" remote="github" revision="4.7-androideabi" />

But I've been reading about NDK and having problems locating the Linaro NDK r8e which I believe will give me a 4.7.x build. The NDK as I understand it is used to optimize APKs, etc. Whereas the toolchain/compiler does Kernel/Libs+ROM.

Is this correct? I'd like to make it Linaro all the way through in my builds. I noticed during a build yesterday that it was using the stock arm-4.7 compiler (as far as I could tell) and I think this is related to the NDK. I don't think I'm compiling everything with Linaro that I could be. I also noticed that S-Tools shows no Linaro tag in the kernel uname string/info.

sources:

https://wiki.linaro.org/Platform/Android/Toolchain

http://xdaforums.com/xperia-z/development/tutorial-compile-xperia-z-rom-linaro-t2330970

Anyone shed some light on this for me?
[RAZR HD Original Android Development] skeevydude:
I checked the Linaro site, then repos, and the first one I found with a 4.7 GCC was kitkat-cts-dev. Everything newer than that doesn't contain 4.7, at all. It doesn't surprise me, 4.8+ is better on paper and 4.7- really needs to be phased out. Seeing as how PAC only needed 3 fixes for 4.8, we're almost there, and it looks like 64bit ARM support was added with GCC 4.8, so I expect that to take the place of 4.6 and 4.7 to be phased out (a guess, but a logical one).

GCC 4.9 is required to use A12 tuning.

Speed wise, most benchmarks show 4.7 and 4.8 to be pretty similar in speeds. Didn't check with 4.9.

Good catch on the Linaro NDK part. Now I gotta update my adds/removes, add a Linaro remote, and add in the NDK from their Android repos.

I'm glad I didn't have to fix as many repos as the Sony dude did back then. I tried this with PAC 6 months to a year ago and around the 20th repo that needed fixing I said screw it. Only 4...sure. Oddly, 4.8 needed 3 fixes, 4.7 needed a 4th -- interpret that however you want.
[RAZR HD Original Android Development] CWGSM3VO:
Can you provide the necessary XML so I can be on the same page too? :) For me the NDK looked like it contained the toolchain and a few other things but wasn't sure how to fit it in other than replacing the NDK folder. I'll switch to 4.8/9 here, there's optimized toolchains I can use for that too.