yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Q&A, Help & Troubleshooting] CqN:
I am currently on cm-10.1.3 galaxy s2 i9100 intl (International, NOT G). It has CM-based Recovery v6.0.3.6. How do I upgrade to new rom cm-11 nightly?

1. Can the above CM-based Recovery v6.0.3.6 be usd for the flashing? Any link to a detailed post would be appreciated? I have seen references to problems if the above used, or first one has to goto cm-10.2 etc. It looks like cm-10.2 has been pulled back, I do not see that among cm downloads area.

2. Using the built in 'CM Check for updates' I downloaded the latest cm-11 nightly, it went without any error. But I do not see that .zip file anywhere. Where is that supposed to be?

Any help is appreciated.
[Galaxy S II Q&A, Help & Troubleshooting] :
The cm11 zip file will most likely be in your internal sd card. You should be able to flash it from there from recovery, but first I would update the recovery to something more recent

Just download the latest philz recovery from HERE You want the "latest philz" from the third post. Flash this recovery, reboot into recovery(not system), do a full wipe after any backups you want to do, then flash the cm11 zip and compatible gapps(optional)

There are other recoveries you can use, just use the latest one if possible, philz is what I use
[Galaxy S II Q&A, Help & Troubleshooting] CqN:
Thank you very much for your very helpful reply. I have more to clarify now.

A. Well, I found out why I dont see the cm-11 zip file. (I did search in the *nix console with

'find / -name cm-*.zip'. Couple of the other older zips do show up.). To see the problem I had to watch during the full download; towards the end it has a very brief popup like 'MD5 check failed'. I have no idea why the latest cm-11-20150426-nightly md5 is failing at my end!! The previous 20150412 could not be downloaded either (though I was not there to catch the md5 error, but since there was no file, I assume it failed similarly.) So I tried the 20150406, and that did ask me if I wanted to flash, I cancelled that, and the zip is in the /storage/sdcard0/cmupdater/ . Good.

B. I had never used any philz recovery tool before. So to flash this new recovery, I use the current CM-based Recovery v6.0.3.6, just like I load the gapps zip?

B1. When you say philz, from third post, this one? 8th September 2012, 11:40 PM |#3 ?

It says it 'can be flashed in stock recovery 3e: No Yellow Triangle'. Mine is no longer the stock recovery, since I had updated to the v6.0.3.6. My phone has a Yellow Triangle on boot! Does this mean I cannot use this one? Kindly explain.

So philz recovery is different flavour from the CM-10.1.3 based I have? I had used the flashing only once before to come from the stock to the 10.1.3. Are these two recoveries fully compatible?

C. I had already downloaded the gapps zip for cm-11. The date of that is rather old; I assume there is only one gapps zip version for the cm-11?

D. Since there have been so many cm-11 NIGHTLYs out there, no stable, or monthly, how does one select one of the more stable among them. I really do not need the latest, the primary reason is the main version Andorid upgrade, and I want the ones after the battery drain problem, and the music stop problems were fixed. Is there any place where they give a relative 'goodness' grading to these NIGHTLYs?

Thank you for your continuing help.
[Galaxy S II Q&A, Help & Troubleshooting] CqN:
This is a continuation of my last reply to you. Double checking: The latest zip file I see at the goo.im downloads site phiilz_touch->CWM_Advanced_Editiion->i9100 is

philz_touch_6.48.4-i9100.zip Sun, 06 Jul 2014 22:47:33 GMT

Should I flash this from my CM-based Recovey v6.0.36 ?. After this flash, i suppose I can do a regular phone booting also, before flashing the cm-11? Thank you.
[Galaxy S II Q&A, Help & Troubleshooting] :
The latest philz is correct - 6.48.4. Yes you can flash it from your recovery, it is just an updated version of the v6.0.3.6, something like 6.0.4.something with touch ui. It will work flashing later android versions where the earlier one may not. Just flash it and reboot straight back into recovery when you are ready to do your backups, wipes and installs.

The nightly cm11's are all very stable at this stage; I would download the latest, but the more important bug fixes were implemented from about mid january(eg. fpbug fix). Anything after that would be ok. The gapps, I would download the latest just before I flashed the rom, you are better off with the latest play services etc. As long as they are compatible to 4.4.4, you can choose whatever gapps you want. I like minimal gapps by [MENTION=5772029]jajb[/MENTION] for example, but it's up to you. HERE are most of the gapps available at the moment.

If you can I would download the rom by pc. You are recommended to check the md5 sum whenever you download roms/gapps to make sure the download was successful
[Galaxy S II Q&A, Help & Troubleshooting] CqN:
noppy22, Thank you. That clears up many things. The link to the gapps is a big help. I had previously read somewhere that my phone needed a small foot print gapps, because the system (?) partition was ony about 500mb. That was what I had downloaded, but I can check the newer ones.

How do I check the md5 checksum after the download? I have access to the terminal, and I can use minimal *nix commands, once i know the utility name :) At philz, there were .zip and .zip.md5 of the same version date. Can I flash either one? I know, as I mentioned in two msgs ago, when I use the system download of nightly, it automatically checks the md5, and saves only if it is correct. But I simply downloaded the gapps, and the .zip of he philz, so I do not know how to check the md5. Info-zip versions of zip has their own integrity check with unzip -t, but the unzip in busybox of Android appears minimal without those features. Thank you agian, I am almost ready to upgrade, as soon as I hear back from you :)
[Galaxy S II Q&A, Help & Troubleshooting] :
Yes you are generally better off with a smaller gapps package due to the smaller /system in the s2, more so in the newer lollipop roms.

You can check the md5 in a variety of ways, google will tell you ways to if you want to search, and there are apps in the market that check for you. I personally use hashtab, which you download to your pc. It gives you a tab in "properties" that allows you to compare the md5 value against the download site
[Galaxy S II Q&A, Help & Troubleshooting] CqN:
Thank you. I got my s2 running on 4.4.4, thanks to your help. Everything went fine; I will reload another newer 'small' gapps pkg soon.

As for the md5 check, I was wondering if there is a way to do that from the phone (after a download) or using philz recovery, after download of a .zip.
[Galaxy S II Q&A, Help & Troubleshooting] :
Just go to play store and search for "md5 checker". There are several there. Sorry I haven't used any, so can't recommend but they should be able to give you a reference point
[Galaxy S II Q&A, Help & Troubleshooting] CqN:
I have run into a problem, and I am stuck. While playing with the setting of profiles, I lost wifi, and the cell connection permanently. It is possible there is bug in the new profile version. Anyway, I flashed again the same nightly (after wipe for loading a new rom), and then this time without the gapps re-flashing, booted the system up. Both the wifi and the cell connected this time. Of course there was no google apps. So, I reflashed the philz advanced (the cm flash always gets rid of the philz advanced), then added the same apps pkg as before. But then when I booted the system up, both the wifi and the cell were not connecting!!

Any suggestions? Thank you.

PS. A related question. Does philz provide a way to save all the installed up and their setting to the external sdcard, and then reboot it? I am particularly interested in the settings save and restore.
[Galaxy S II Q&A, Help & Troubleshooting] :
I don't know about the connection problems, you could post the problem in the cm11 thread as it is more specific to that rom. I have heard problems in cm12 with using gapps not released by cm, so you could try cm gapps HERE

Other than using the backup feature of philz, there isn't really any option to save settings. You could check out titanium backup from the market. It has the most comprehensive features for backing up apps and settings, although I have had problems with re-installing stuff using it, but plenty of people swear by it....
[Galaxy Ace S5830i Q&A, Help & Troubleshooting] fedor12:
I'm trying to fix an ace gt-s5839i (rooted with stock ROM) that won't boot up, it always goes straight to recovery.

I've searched for fixes on this forum (and others) and the fixes i have tried so far have not worked, these include flashing a new recovery (clockwork), flashing a whole new custom ROM (razordroid and CM) and flashing stock ROM through Odin, also it won't even let me wipe data through recovery as it will just stick on formatting data.

Any idea what is up and how i can fix it? The phone belongs to a relative of mine and he said he woke up one day and the phone was in bootloop, he took out the battery and put it back it back in and ever since then it just goes straight to recovery.
[Galaxy Ace S5830i Q&A, Help & Troubleshooting] ehsanotaku:
Ok , I did mention troubleshooting method for similar cases like you in many posts here mate ,, Just get yourself stock s5830i firmware compatible with your Region/Carrier and make a wipe / split packages with the help of splitfus2 or simply use one of the pre-made packages >> Follow my instruction @post#4 from the line :"1. Download one of the newest ,,," to the end of the post .

btw razordroid was obsolete and buggy at the best of the times anyway , try newer/more stable from development sub forums .

After resolving your boot loop and partition issues you may flash your newer s5839i stock fw from i,e: sammobile database on top of your s5830i over Odin ( normal flashing procedure ).

Hope I did Help you
[Desire 816 Q&A, Help & Troubleshooting] Mr.Ragabino:
hi ,

I need Ruu for desire 816 dual sim a5_dug

Information Device :

a5_dug pvt ship s-on

hboot-3.19.0.0000

radio-1.13.3230.16.05

opendsp-v24.2.2.00541_a5dus_crc.0311os-
[Android General] Marc Kevin Flores:
Porting a Rom easy steps

Notice:

This is not work for any device its work to BCM21553, Before you port a ROM, make sure you asked permission from the Developer! :)

Usable Porting Rom:

Samsung Galaxy Pocket S5300

Samsung Galaxy Pocket Duos S5302

Samsung Galaxy Y S5360

Samsung Galaxy Y Duos S6102

Samsung Galaxy Ace Duos S6802

Please Note:

I AM NOT RESPONSIBLE FOR ANY DAMAGE OR ERRORS TO PORT A ROM OR CUSTOM ROM

Things to Need:

Winrar/7zip

Knowledge to port

Any ROM work for you

Rom to Port

Rooted Phone

CWM to flash your rom

Advice:

if you are dual sim then you want to port single sim custom rom, your rom will be single sim that is the bug

Copy these files from stock to port:

system/bin/charging_mode

system/bin/e2fsck

system/bin/vold

system/etc/gps (whole folder)

system/etc/permissions/handheld_core_hardware.xml

system/etc/permissions/platform.xml

system/etc/wifi (whole folder)

system/etc/afc_fa.dat

system/etc/calib.dat

system/etc/param.dat

system/etc/sensors.dat

system/etc/vold.fstab

system/lib/hw (whole folder)

system/lib/modules (whole folder)

system/lib/libacdapi_azi.so

system/lib/libbrcm_ril.so

system/lib/libcamera.so

system/lib/libcamera_client.so

system/lib/libcameraservice.so

system/lib/libgcomm_jni.so

system/lib/liblifevibes_mediashare_jni.so

system/lib/libmedia.so

system/lib/libril.so

system/lib/libsensorservice.so

system/usr/keychars (whole folder)

system/usr/keylayout (whole folder)

system/build.prop (if you dont replace the build.prop your homescreen will big or equal dependent to your screen of the rom)

if your rom are in backup from cwm include this file:

system/CSCFiles.txt

system/CSCVersion.txt

system/SW_Configuration.xml

META-INF/update-binary

META-INF/updater-script

Repack into Zip folder not Rar, Put it into the root of your SD go into recovery, Wipe data, Wipe cache and Flash your created Rom and you are done Happy Porting :D

I hope it will be work my guide :)
[Android General] vblego:
Will it work if custom ROM version is KitKat while stock is gingerbread
[Android General] Marc Kevin Flores:
i think its not work bro, it need same version
[Nexus 7 (2013) Android Development] Scott:
AS the name implies this is a stock rooted Android 5.1.1 - LMY48G Lollipop ROM!

Features

100% Stock

Rooted / Powered by SuperSU by [MENTION=631273]Chainfire[/MENTION]!

Busybox

FSTRIM on install

Zip Aligned

No other edits

Notes:

Should update bootloader. It is attached as a flshable ZIP.

First boot is a loooooooooooong time! About 5 to 7 minutes!

You must be on Latest TWRP to enjoy this ROM. No other recoveries supported however they may work.

Install:

Copy ROM to storage

Reboot to TWRP recovery

Factory Reset (no other wipes needed)

Flash ROM

Reboot and Profit!

Troubleshooting

If you get no status bar reboot to recovery and clear all cache. If that doesn't work try flashing the factory image then flash TWRP again and then this ROM.

Getting Symlinks failed during install? Make sure /system is unchecked in TWRP mounts

Problems with internal storage? Look at THIS POST for fix by [MENTION=5094871]freakzapster[/MENTION]

If you appreciate my time and effort please consider a small (or large) donation :)

A little bit goes a long ways!

Please hit Thanks!

MOD EDIT: Link removed as domain has expired. Thread closed until new links can be installed​
[Nexus 7 (2013) Android Development] Scott:
Looks like the Nexus Trolls are at it again! In case you dont know the trolls are jealous hateful people with no skills that go around rating everyone's thread 1 star. I really kind of feel sorry for these sad little creatures :( One day they may seek the therapy they need (and move out of there parents basement).

But untill then...

Can I get everyone to thank the Opening Post and rate it 5 stars?
[Nexus 7 (2013) Android Development] :
Oh snap! Donation coming your way when I get paid
[Nexus 7 (2013) Android Development] SHABBYLEA:
Been waiting to give this a test drive...

Cheers...
[Nexus 7 (2013) Android Development] chrisluffy25:
i flashed the factory image thru flashfire.. and viola.. my root still there :)
[Nexus 7 (2013) Android Development] paulbonner:
Dirty flash over Scott's 5.1 with cache / Davlik clear appears to work fine.
[Nexus 7 (2013) Android Development] ImjuzCY:
My magnetic screen off sensor is not working after the update. Flashed this zip but I'm quite sure it's not the problem of the zip. Anyone else?
[Nexus 7 (2013) Android Development] newkydawg:
Worked for me too. Thanks Scott! :good:
[Nexus 7 (2013) Android Development] yonster:
The Download site seems to be down at present.
[Nexus 7 (2013) Android Development] mindmajick:
Not for me. Just downloaded and flashed fine

-> Sent from my mind to your screen
[Nexus 7 (2013) Android Development] yonster:
Thanks. Downloading now through a VPN. The site didn't seem to like my IP.
[Nexus 7 (2013) Android Development] Scott:
Trolls lost! lol
[Nexus 7 (2013) Android Development] benny3:
Rated thread and Thanks left. I was happy to return the N7 back to you but i'm missing it already....lol

I did pick up the LG GPad 7.0 from Sprint for free but its not even close to the N7. Enjoy the rom everyone and thanks again for your work Scott
[Nexus 7 (2013) Android Development] Deacon-Frost:
Nope, everything's ok here. So it seems not be ROM related.
[Nexus 7 (2013) Android Development] zikario507:
it works for me too!!!
[Nexus 7 (2013) Android Development] yonster:
All good here. Nice job.
[Nexus 7 (2013) Android Development] Scott:
Thanks guys, we are beating the trolls :good:
[Nexus 7 (2013) Android Development] Bright09:
Thanks Scott you always have your Roms up quick :) need to get this flashed I just flashed 5.1 not a week ago finally got the notice for update lol
[Nexus 7 (2013) Android Development] ray1234:
Any tried whether CWM is ok to flash this rom?
[Nexus 7 (2013) Android Development] paulbonner:
Actually, I take that back. My screen and particularly my keyboard have been very unresponsive at times since the dirty flash. If I was a better person I'd do a reset and reflash so I could report the results , but I think I'm just going to reset and flash CleanROM instead, because that's what I really want to be running.

Anyway, I'd recommend a reset for this one.
[Nexus 7 (2013) Android Development] Telyx:
I dirty-flashed over 5.1 and then wiped cache & Dalvik and have had no issues so far.
[Nexus 7 (2013) Android Development] mindmajick:
+1
[Nexus 7 (2013) Android Development] shezaad879:
Same here. Had no issues. I then dirty flashed CleanRom 6 and still no issues. Also using Elemental X kernel.
[Nexus 7 (2013) Android Development] Shibang:
You're the man. This worked like a charm for me. Keep up the great work!
[Nexus 7 (2013) Android Development] P!X3L:
Can someone mirror this? Site seems to be down
[Nexus 7 (2013) Android Development] Aerobatic:
works for me.
[Nexus 7 (2013) Android Development] vulpy:
Can anyone confirm that GPS works out of the box ? Thx to the developer for his outstanding work!
[Nexus 7 (2013) Android Development] goRt:
Works for me
[Nexus 7 (2013) Android Development] SPreston2001:
I keep getting "Error executing updater binary in zip" when I try to flash this! Any ideas? Thanks
[Nexus 7 (2013) Android Development] Aerobatic:
Haver You tried other versions of TWRP - 2.8.6.0, 2.8.2.2, 2.8.1.0?
[Nexus 7 (2013) Android Development] kurrupt_1:
I did exactly what the post said to do and now I just have a black screen, cant tell if its on or off. I hold the power button down and it doesn't reset, try to boot into recovery and nothing.......Any advice?
[Nexus 7 (2013) Android Development] mugsy77:
Just want to confirm that if I have a Nexus 7 2012 WiFi, I can only use this Stock ROM and not CleanROM 5.1.0 or 6.0 or any older version of CleanROM, correct? Thanks for confirmation.
[Nexus 7 (2013) Android Development] Jhall8:
This thread is for the ROM for the 2013 Nexus 7.
[Nexus 7 (2013) Android Development] waa2398:
When I try to install Bootloader I keep getting an the error "Error executing updater binary in zip. I have, obviously a Nexus 7 2013 [WIFI] with Stock Android 5.1 rooted. Used Nexus Toolkit to install TWRP 2.8..60 and I'm able to boot into Recovery the problem is that I'm not able to flash the freaking bootloader. Any ideas guys?
[Nexus 7 (2013) Android Development] TheDarkDefender:
Hey guys,

Could any one share the stock bootanimation from /data/media.

Thanks.
[Nexus 7 (2013) Android Development] fuzzybabybunny:
Hey guys, some quick questions:

I'm still on Android 4.3

- Can I upgrade CWM and just directly flash to 5.1 using the zip? Or do I need to use Odin since I'm still on 4.3?

- I've heard of battery life being seriously worse on 5.0. How is battery life on this 5.1 rom?
[Nexus 7 (2013) Android Development] Aerobatic:
IMHO better update TWRP (CWM seems to become obsolete), to 2.8.4.0 by CWM (flashable ZIPs can be found in appropriate thread), then to 2.8.7.0 (Flo) or 2.8.7.1 (Deb) TWRP image directly by TWRP 2.8.4.0.

After that flash bootloader 4.05 (found in OP), and then 5.1.1.

BTW, today new factory image was uploaded for Flo: 5.1.1 (LMY48G) https://developers.google.com/android/nexus/images

Hopefully [MENTION=426561]scrosler[/MENTION] will find some time to pack it into most useful form of Flashable Stock Rooted.
[Nexus 7 (2013) Android Development] just lou:
Hopefully. :good:
[Nexus 7 (2013) Android Development] xbs:
Is it possible to get rid of the ota warning?
[Nexus 7 (2013) Android Development] elbee222:
Yes. Settings - Apps - Google Play Services. Uncheck Show notifications.
[Nexus 7 (2013) Android Development] perksynav:
ROM Updated to LMY48G

From the OP Scrosler in another of his threads.....

http://xdaforums.com/showpost.php?p=61703043&postcount=6386
[Nexus 7 (2013) Android Development] Scott:
I updated the OP to reflect the updated ROM :good:
[Nexus 7 (2013) Android Development] Scott:
211 downloads... Anyone have any issues?
[Nexus 7 (2013) Android Development] Isambard Prince:
I can't believe I'm the first to reply, but all good!

Thank you, Scott! [emoji4]
[Nexus 7 (2013) Android Development] teddat:
so far so good. no issues with bluetooth, wifi, gps. still have unlock issues with tasker blanking out the screen but thats not your fault.

thanks!
[Nexus 7 (2013) Android Development] kokopopz:
No issues. Very stable. Thanks.
[Nexus 7 (2013) Android Development] xbs:
Can I dirty flash over the previous version?
[Nexus 7 (2013) Android Development] AxlxA:
Trying to understand but can this work on the nexus 7 2013 4g version as well? Deb?
[Nexus 7 (2013) Android Development] just lou:
No issues or differences from r5.
[Nexus 7 (2013) Android Development] lolcopter:
Worked fine here
[Nexus 7 (2013) Android Development] paztine:
thanks devs..

Thanks dev for this stock build everything is running smoothly so far dirty flash on top of the latest stock firmware.. I am on stock rooted before..Thanks again you never fails us with a stock rooted build... Always a five star for you to keep you going...
[Nexus 7 (2013) Android Development] AxlxA:
Sweetness, flashing right now. Hope all is good. Last time I flashed the previous version I got some errors with google play services. Hope this doesn't happen again. (Dirty flash)

Edit: Yep everything is perfect!!! Love this rom. Sent to my nexus, twrp install zip, wipe cache dalvik cache and reboot
[Nexus 7 (2013) Android Development] Scott:
Alright good!
[Nexus 7 (2013) Android Development] Z23:
All fine here (dirty flash) with elementalx kernel.
[Nexus 7 (2013) Android Development] slimb9:
scott,

seems that your website is down. i looked in the cleanrom thread and a few were having issues also. is there a direct link to the download? if not, no biggy. thanks.
[Nexus 7 (2013) Android Development] Scott:
https://www.androidfilehost.com/?fid=24052804347769041
[Nexus 7 (2013) Android Development] m+a+r+k:
Any chance of an update to LMY48L? Pretty please :o
[Nexus 7 (2013) Android Development] ymDroid:
Any chance of updating this to LMY48I with the Stagefright patch pleaze?
[Nexus 7 (2013) Android Development] lolcopter:
Yeah I just got an OTA prompt for this I think, which presumably won't work
[Nexus 7 (2013) Android Development] just lou:
If you don't feel like waiting, you can use Wug's Toolkit to flash LMY48I over LMY48x without wiping data. Then just use the toolkit to re-root and put TWRP back on it. It took me about 15 minutes.
[Nexus 7 (2013) Android Development] Scott:
Yeah, I forgot about it. I plan doing it tomorrow, which is my day off. I might try to get it done tonight... But realistically tomorrow so I can make sure I dont screw anything up. I usually work till late.
[Nexus 7 (2013) Android Development] ymDroid:
Thank you.
[Nexus 7 (2013) Android Development] ChadH42:
The OTA usually won't work if you have a custom recovery installed.
[Nexus 7 (2013) Android Development] Scott:
Honestly, on stock rooted, it prolly would. However, worse case scenario is a boot loop and stock recovery.

Thats worst case. Best case... Just stock recovery.

You would still have to re-root in either scenario.

But dont worry, I will update stock root tomorrow.
[Nexus 7 (2013) Android Development] Summit1:
Thanks Scott, I look forward to your update. If these Android security updates are indeed going to be pushed out OTA monthly, that's going to suck for you and other rooted ROM developers - having to update your ROMs every month also. Maybe there's a genius somewhere who can create an app that will flip back and forth between custom recovery/rooted and stock recovery/unrooted with the OTA update installed in between? One can dream anyway! ;)
[Nexus 7 (2013) Android Development] Scott:
Nah, I like it. So dont most of my peers. We love this mess :silly:
[Nexus 7 (2013) Android Development] Scott:
Done!

Thread closed...

New party is here: [ROM][Flo][8/15/15] - Stock Rooted 5.1.1 - LMY47I - Root and BusyBox only!