Related
While I did find a similar posts, they were for different devices. I also tryed to search o different sites for similar problems to no avial.
What Happened: After backing up system data and app data then removing Foxhound ROM with factory reset, and installing UltimaROM i came to find that the modem did not install correctly result in no connection to my cell network. I booted into TWRP recovery to try and do a re-install of the ROM only to find that TWRP was restarting itself every 3 seconds or so. I attempted to restart the device which i found to result in a TWRP bootloop that i cannot get out of, it constantly is booting into recovery mode and i cannot get it restart the OS.
What I've tried: Since i can get into download mode i decided to attempt to re-install TWRP using Samsung Galaxy S3 Toolkit but since i do not have USB debugging on i cannot do that. I'm mainly looking for a fix before i go and claim it on the warranty saying update went bad or something. If people need more information I will try to provide it as best i can.
Summery if i confused people is that TWRP is in a bootloop, i am unable to get to the OS, but i still have download mode available.
I fixed it but not how I would have liked to. I ended up losing all data due to flashing stock ROM using ODIN. I would still much appreciate a alternative method that does not involve loss of data though just for future reference, that is if anyone knows a alternative method.
Sent from my GT-I9300 using xda app-developers app
could've tried reflashing TWRP or any other recovery through odin
I have an LG Optimus Q (LGL55c) with twrp loop. I was trying to go back to stock rom, instead I deleted all the system files in twrp when it was working...Then I rebooted back into recovery and get the loop. Does this mean I completely bricked my phone? I tried using adb, adb shell doesn't work. It does find the device. Even tried the LG update with no sucess Any ideas or suggestions?
I just read the forum title, I thought this was for the Optimus Q not the Samsung S3. Sorry mods
Temasek unofficial cm12 5.02
I was running this rom when my power button shorted and I got it replaced but then I tried to do a complete wipe and clean flash but since then it has been twrp bootlooping, tried to flash the latest recovery through Odin but still doesn't work also tried stock firmware flash but says binary not available.
This is my secondary device and I've not been in touch with Odin for a while. Any help will be appreciated.
Thanks
Download latest firnware from sammobile.com and flash it with Odin, as described on sammobile: does Odin finish with '1 succeeded'?
I'm in a very similar situation, but with my Samsung Galaxy Note 2 (N7105). It's rooted, and I am, or was using TWRP 2.7.0.2. ROM is CyanogenMod 12, 5.0.2 Lollipop.
I did a factory reset from INSIDE Android, and chose to wipe internal memory. Phone did the reset and wipe, rebooted into TWRP instead of Android, and now I have TWRP boot loop.
I posted more about it here: http://forum.xda-developers.com/showpost.php?p=60247503&postcount=3671
I have the Problem toooo!
What must i do Now!
with my S3 is the same!!!
For posterity:
With an old (2014?) version of TWRP and a custom ROM, I tried reverting to factory settings. That caused the phone to reboot TWRP, and the screen would flash every couple of seconds. I flashed a stock recovery image I found on Google, and when it restarted again, the wipe was completed successfully. My intention was to wipe all user data anyways so I can't say if this method might save it.
I tried following this:
http://forum.xda-developers.com/showthread.php?t=1580070
"INSTRUCTIONS" part:
* RECOVERY: FACTORY RESET IF YOU WERE USING ANOTHER ROM!
* RECOVERY: Install Rom: Download
* RECOVERY: Install Gapps, ALWAYS-EVEN FOR UPDATES: Download (find the latest one that carries the "jb" tag)
* RECOVERY: Wipe Cache Partition
* RECOVERY: Wipe Dalvik Cache
* Reboot and enjoy
Click to expand...
Click to collapse
did all the above, never forgot any of the 3 wipes/resets that were necessary.
used this rom file:
http://goo.im/devs/paranoidandroid/roms/i9100g
(latest one)
for my Galaxy Samsung S II GT-i9100g.
I had CWM and also had a rooted android 2.3.
first boot it showed me the normal samsung boot screen, for 45 minutes....
so I restarted and the phone gave me the same behaviour..
so I removed the battery to turn off the phone, and attempted to reinstall the whole thing, going through this process again from scratch
not forgetting any of the wipes etc...
now every time I boot it, it leads me to CWM instead of the normal boot screen and the expected paranoid rom eventually...
I followed this path because CM 10 failed me because upgrading from 2.3 to 4.x requires going through something that is called "stock" or as I think it actually is - google's /manufacturer's original firmware/rom production line thingy
and after that it needs me to re-enable root on that stock rom all over again. And only then I may attempt to install CM10...
so I picked paranoid instead, because in it's instructions is showed me no such constraint. heck it can't give me that constraint because there is no "stock" of android 3.x for smartphones
but then this issue happened... so I need your help.
I found similar search results but couldn't figure out their solutions or how whatever triggered that same problem (which isn't mentioned in those threads) is related to what I did to my phone... (so that I will not repeat the same mistake)
your help is much appreciated as I need it so so much!
Huh?
Just flash a stock ROM, get back on your feet and go CM or paranoid.
Sent from the little guy
gastonw said:
Huh?
Just flash a stock ROM, get back on your feet and go CM or paranoid.
Sent from the little guy
Click to expand...
Click to collapse
by "flash"ing you mean the option "install from a zip file" in CWM in recovery mod?
if I have some rom, the only way for me to install another would always be by going through that middle step of also installing a 'stock' rom as well?
there is no way around it?
installing a 'stock' rom, wouldn't it make me loose my root I have on the phone and force me to root it all over again before I can continue install anything at all?
thats the reason I wanted to try out the paranoid way of doing this instead of the CM10, because I have no interest in rooting my already rooted phone and I hoped that paranoid does not need me to go to stock first....
Couple of things:
Stock: why, when in trouble, we suggest stock?
Stock is the original state of the phone.
Samsung write it for our device to work flawless, so, by flashing stock we can check if our device is fully functional.
Imagine you flash a custom ROM and you lose IMEI, you go "wtf?" right?
In order to check if your EFS folder is f&#cked up, you flash stock and check if your IMEI is still there.
We can always use stock to take a long breath "phew, we're fine" after a f*&k up.
You can flash stock via CWM (zip file), Odin (tar file, md5) and mobile Odin (tar, zip and md5).
CWM: custom recovery, you can get it by flashing a custom kernel or by flashing it via stock Recovery (generally comes with BusyBox and SuperUser app, which gives you Root).
Odin: Just download any version and follow directions.
Mobile Odin: Well, this is a hell of an app, you need Root to run it.
It does all that Odin does, plus it roots your ROM (only stock ROMs) while it's flashing it, all by itself. Costs 5 bucks, but it's damned worthwhile.
Wanna know the best scenario?
You get M.O Pro, you get a nandroid back up online app, you get CWM zip files (sitting on your SD).
With that line up, you can flash whatecer the hell you want and you will ALWAYS have root.
Sent from the little guy
some questions
ONE QUICK IMPORTANT QUESTION BEFORE THE REST:
If I use mobile odin, will I be able to use it to install stock rom and also root it at the same time?
SECOND IMPORTANT QUESTION:
you said I could flash whatever I want and still have root, but my problem was not 'not having root', it was not having the flash process complete successfully... how do I attack that?
THIRD IMPORTANT... info... :
My "BUILD" version is "GINGERBREAD.XXKL5", isn't that a 'stock' one?
If you don't have a lot of time,
then the rest of this post is not as important as the 2 questions above...
gastonw said:
Couple of things:
Stock: why, when in trouble, we suggest stock?
Stock is the original state of the phone.
Samsung write it for our device to work flawless, so, by flashing stock we can check if our device is fully functional.
Imagine you flash a custom ROM and you lose IMEI, you go "wtf?" right?
In order to check if your EFS folder is f&#cked up, you flash stock and check if your IMEI is still there.
We can always use stock to take a long breath "phew, we're fine" after a f*&k up.
You can flash stock via CWM (zip file), Odin (tar file, md5) and mobile Odin (tar, zip and md5).
CWM: custom recovery, you can get it by flashing a custom kernel or by flashing it via stock Recovery (generally comes with BusyBox and SuperUser app, which gives you Root).
Odin: Just download any version and follow directions.
Mobile Odin: Well, this is a hell of an app, you need Root to run it.
It does all that Odin does, plus it roots your ROM (only stock ROMs) while it's flashing it, all by itself. Costs 5 bucks, but it's damned worthwhile.
Wanna know the best scenario?
You get M.O Pro, you get a nandroid back up online app, you get CWM zip files (sitting on your SD).
With that line up, you can flash whatecer the hell you want and you will ALWAYS have root.
Sent from the little guy
Click to expand...
Click to collapse
the saddest part is that I couldn't figure out most of what you just said
what is 'nandroid'? 'flashing'? do you mean like dd in linux? copying to the entire flash storage device?
'IMEI'? huh..? O_O
at the moment I was able to 'get back on my feet', I restored everything back to normal with manual copying of important parts of the CWM corrupted backup from this week, and old stuff for a CWM backup made few months ago.
now that I am at a 'normal' state.. I want to install paranoid or CM10 on my GT-I9100g.
which one of those 2 does not force me going through installing stock?
I have this fear of installing stock that it will take away my root and that I will have to use adb from command line to re-enable root afterwards, which I have bad experience with.
I need to know a few things before I attempt to install stock via CWM,
will installing stock disable my root? will installing stock disable my ability to load recovery boot menu CWM?
is 'root' an attribute or state that belongs to the running rom itself after boot has been completed and to that only?
or does it also belong to the state the device is at while in the recovery boot menu CWM ?
I tried messing around with ADB in the past to see if I could root devices via that way but it wasn't very successful so thats why I'm afraid of having to attempt it again.
bumpitybump
even though a year later, I would still love some replies
resurrecting my motivation to do this once again.
copy paste from my other post;
before flashing, you will need these;
-stock rom (get it from Sammobile, sign in and select your country and phone model)
-blazing kernel for recovery (search in XDA)
-custom rom (CM, PA, Supernexus...your choice)
-backup your data
-GApps (get the latest one)
-you must know what are you doing and dont flame/blame other member if something wrong
how to flash;
-make sure you are on latest stock rom (mine is JellyBean 4.1.2), if not like the OP, flash the latest stock rom using Odin;
*reboot your phone in Download Mode
*open Odin and in PDA option select your stock rom and then Start
*if done it will display Done and disconnect your phone, it will boot up
*if bootloop, reboot into Recovery Mode, and then wipe data and cache, and then reboot normally
-after updating your phone to latest stock rom, copy your custom rom, GApps, and Blazing kernel into external SD card, then reboot into Recovery Mode
-choose "apply update from external storage" and choose Blazing kernel, wait for it to finish update
-reboot normally, and then reboot back to Recovery Mode. this time you will notice that your recovery is different from the previous one
-select install zip > choose from external storage/sdcard 1 > and then choose your custom rom. then wait for it to finish update
-repeat the above step to install GApps, and after that reboot normally
-if bootloop, reboot back to Recovery Mode and then wipe data, cache and dalvik and then reboot
-done, now you are running on custom rom
Click to expand...
Click to collapse
and about the root, i believe that almost all custom rom rooted
I have tried to install smartdroid in my s3 using TWRP as recovery manager. Since I previously backed up my stock rom I was able to back from a flashing problem I had "some changes failed". As I saw this can be overcame using Philz I changed the recovery. Then I tried to install, again, the smartdroid. This time it finishes but never booted up correctly.
Now, I am not able to reload my backed up rom (as it was made with TWRP and now I have Philz) nor installing smartdroid. So well, I want to install TWRP but I haven't seen the zip file to install it from Philz recovery What can I do?. Can I use odin from Philz?
Thanks
I didn't remember the download mode!, This post saved my day http://forum.xda-developers.com/galaxy-s3/help/twrp-flashing-tar-t2680354
Hey Guys,
I'm having a bit of an issue. Currently I was running STOCK Android 4.3 JB, have been for a while, it started to get a bit slow & I was wanting to fresh install, but also try out a 5.0 lollipop ROM. I've rooted my phone in the past and installed custom ROMs before without a problem (Revolution Remix + Cyanogenmod 11), however, I decided to try Liquidsmooth 5.0 lollipop. i followed this video,
https://www.youtube.com/watch?v=QquFDFEEKlI
http://forum.xda-developers.com/galaxy-s3/development/rom-liquidsmooth-lollipop-4-0-b1-t2980477
I downloaded both files and copied them onto my MicroSD card.
I backed up my data (contacts, images, files etc..)
Booted into "Recovery Mode", wiping Cache & factory Reset
When to install from SD, located file and it started reading/installing (sorry can't remember exactly what it did), but during process it failed. I went back into Android (had to setup again), Went and made sure Developer Mode and USB Debugging was on, still didn't work.
Went to make sure CWM was installed/update, which it said it was (possibly from previous custom installs?), tried updating, failed. It said
Went and installed 'SuperSU' from Play store, but got this error.
Decided to try re-install STOCk 4.3 JB, I
made sure USB Debugging was on
loaded Odin 3.07 (or was it 3.09) and loaded 4.3 Firmware under PDA (left everything else as is)
Started and let it do its thing. It finished/PASSED and phone restarted.
i went back into the phone, installed ROM manager & SuperSU again to give it another shot... but same problem again, getting the error above.
I'm not sure what's happened and I'm not sure what "solutions" to search for... anyone have any suggestions?
At this stage I'm thinking of just going back to STOCK 4.3, then maybe try again (either with Liquidsmooth lollipop, or, Slimkat 4.4)
Thanks guys, any help would be super appreciated,
Regards,
~ Dave
Le Widget said:
Hey Guys,
I'm having a bit of an issue. Currently I was running STOCK Android 4.3 JB, have been for a while, it started to get a bit slow & I was wanting to fresh install, but also try out a 5.0 lollipop ROM. I've rooted my phone in the past and installed custom ROMs before without a problem (Revolution Remix + Cyanogenmod 11), however, I decided to try Liquidsmooth 5.0 lollipop. i followed this video,
https://www.youtube.com/watch?v=QquFDFEEKlI
http://forum.xda-developers.com/galaxy-s3/development/rom-liquidsmooth-lollipop-4-0-b1-t2980477
I downloaded both files and copied them onto my MicroSD card.
I backed up my data (contacts, images, files etc..)
Booted into "Recovery Mode", wiping Cache & factory Reset
When to install from SD, located file and it started reading/installing (sorry can't remember exactly what it did), but during process it failed. I went back into Android (had to setup again), Went and made sure Developer Mode and USB Debugging was on, still didn't work.
Went to make sure CWM was installed/update, which it said it was (possibly from previous custom installs?), tried updating, failed. It said
Went and installed 'SuperSU' from Play store, but got this error.
Decided to try re-install STOCk 4.3 JB, I
made sure USB Debugging was on
loaded Odin 3.07 (or was it 3.09) and loaded 4.3 Firmware under PDA (left everything else as is)
Started and let it do its thing. It finished/PASSED and phone restarted.
i went back into the phone, installed ROM manager & SuperSU again to give it another shot... but same problem again, getting the error above.
I'm not sure what's happened and I'm not sure what "solutions" to search for... anyone have any suggestions?
At this stage I'm thinking of just going back to STOCK 4.3, then maybe try again (either with Liquidsmooth lollipop, or, Slimkat 4.4)
Thanks guys, any help would be super appreciated,
Regards,
~ Dave
Click to expand...
Click to collapse
First of all and most important don't use rom manager! it causes more problems than anything else.The best way to install custom roms is to use Cwm,PhilZ or Twrp to install anything!
Flash superSU zip in recovery from here >> http://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip?retrieve_file=1 << SuperSU forum here >> http://forum.xda-developers.com/showthread.php?t=1538053 << Technically you should not need to flash SuperSU because nearly all custom roms come with root built in so you could flash a custom recovery then wipe and flash your rom (but I can see you have been having problems doing that)
What you should do is
(1) Flash a custom recovery with Odin (Recommend PhilZ)
(2) Reboot to custom recovery
(3) Wipe phone
(4) Install custom rom (which is already rooted) from Ext SD card
(5) Reboot (If you get bootloop factory reset/ wipe cache
Also to note PhilZ recovery (which I think is better as more options and is based on Cwm) as a option to fix root in settings.
tallman43 said:
First of all and most important don't use rom manager! it causes more problems than anything else.The best way to install custom roms is to use Cwm,PhilZ or Twrp to install anything!
Flash superSU zip in recovery from here >> http://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip?retrieve_file=1 << SuperSU forum here >> http://forum.xda-developers.com/showthread.php?t=1538053 << Technically you should not need to flash SuperSU because nearly all custom roms come with root built in so you could flash a custom recovery then wipe and flash your rom (but I can see you have been having problems doing that)
What you should do is
(1) Flash a custom recovery with Odin (Recommend PhilZ)
(2) Reboot to custom recovery
(3) Wipe phone
(4) Install custom rom (which is already rooted) from Ext SD card
(5) Reboot (If you get bootloop factory reset/ wipe cache
Also to note PhilZ recovery (which I think is better as more options and is based on Cwm) as a option to fix root in settings.
Click to expand...
Click to collapse
hi tallman, much appreciated for the reply
For some reason I couldnt get Philz Custom Recovery to work with odin, kept getting an error :/ . So I ended up trying TWRP, which worked, I booted into it then installed Liquidsmooth + gapps, all installed ok, but all up it was the same process you mentioned, which I greatly appreciate.
So running Liquidsmooth 5 now with TWRP recovery, though will likely give Philz recovery a shot down the track
Le Widget said:
hi tallman, much appreciated for the reply
For some reason I couldnt get Philz Custom Recovery to work with odin, kept getting an error :/ . So I ended up trying TWRP, which worked, I booted into it then installed Liquidsmooth + gapps, all installed ok, but all up it was the same process you mentioned, which I greatly appreciate.
So running Liquidsmooth 5 now with TWRP recovery, though will likely give Philz recovery a shot down the track
Click to expand...
Click to collapse
Good to hear it's working Yes it's worth persevering with PhilZ it's a good recovery although Twrp is not bad either:good:
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.
CqN said:
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.
Click to expand...
Click to collapse
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
noppy22 said:
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
Click to expand...
Click to collapse
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.
noppy22 said:
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
Click to expand...
Click to collapse
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.
CqN said:
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.
Click to expand...
Click to collapse
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 @jajb 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
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
CqN said:
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
Click to expand...
Click to collapse
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
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.
CqN said:
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.
Click to expand...
Click to collapse
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
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.
CqN said:
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.
Click to expand...
Click to collapse
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....