I have couple of question and need some help. With the new AOKP nightlies being release every 3 days or so, I would like to stay updated on them. So when I download them and proceed to update and flash over the old nightly. (Wipe Cache, Wipe Dalvik Cache) Upon reboot everything is gone icluding Gapps and seems that it instead of just updating the rom and keeping everything, It updates everything and wipes clean as if it was a fresh flash instead of a update flash ("Dirty flash"). Does anybody know why this happens? Is it that with the AOKP nightlies, you just have to always do a clean install and flash?
MichaelDrakeMS said:
I have couple of question and need some help. With the new AOKP nightlies being release every 3 days or so, I would like to stay updated on them. So when I download them and proceed to update and flash over the old nightly. (Wipe Cache, Wipe Dalvik Cache) Upon reboot everything is gone icluding Gapps and seems that it instead of just updating the rom and keeping everything, It updates everything and wipes clean as if it was a fresh flash instead of a update flash ("Dirty flash"). Does anybody know why this happens? Is it that with the AOKP nightlies, you just have to always do a clean install and flash?
Click to expand...
Click to collapse
When I do this it causes my keyboard to f/c but my apps are still there
Sent from my Galaxy Nexus using xda app-developers app
dustinhayes93 said:
When I do this it causes my keyboard to f/c but my apps are still there
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I can see why the keyboard won't work. That might be due to having to re install Gapps. But I don't understand why every time I update to the new nightlies, all my stuff is gone and it's like a full wipe fresh install/flash. Does anybody know how to avoid this from happening? Or is it that AOKP nightlies won't allow these types of updates.
I don't think there is a way around this. I've been using aokp for awhile and i just keep all my apps backed up so i can restore them after install.
Okay. Thank you for the help.
Sent from my One X using xda app-developers app
My brother just got himself a skyrocket he's on the newest radio w/custom recovery installed but can't seem to flash anything but cm 10.1 with an old 4.2 GApps package.
Kinda frustrating because I haven't seen anyone else having this issue in any other thread. I did to his all I did to mine and I'm running Wantowan2's DU. Just says installation failed and we can't even flash other recovery from within recovery. Where should we go from here
Sent from my SGH-I727 using xda app-developers app
Odin back to stock and start over. Something got messed up in your recovery
Make sure you've got the proper recovery for 4.3 as well.
Sent from my SGH-I727
Well we did Odin back to stock and Odin flashed twrp 2.6.3 and tried to flash the new cwm touch 6043 and it just failed. Not sure why. I repeated process with my phone and it worked but I feel like he did some stuff he's not telling me.
And the only things that do flash remain to be the cm 10.1.3 and GApps from 2012
Sent from my SGH-I727 using xda app-developers app
K
Boot_Derran said:
Well we did Odin back to stock and Odin flashed twrp 2.6.3 and tried to flash the new cwm touch 6043 and it just failed. Not sure why. I repeated process with my phone and it worked but I feel like he did some stuff he's not telling me.
And the only things that do flash remain to be the cm 10.1.3 and GApps from 2012
Sent from my SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
The gapps isn't right for 4.3, cm 10.1. Flash the 8-13-2013 gapps
Edit, you can find it on the OP of this http://forum.xda-developers.com/showthread.php?p=46685423
My understanding is that cm 10.1.3 is android version 4.2.2 and the gapps he used worked. No force closes or anything but one thing he mentioned is that his first flashing of the ROM did not include a full wipe. He did not format system. And even after a full wipe in twrp 2.6.1; data, cache, android secure, dalvik, and system still nothing. Still shows dead android and failed install
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Boot_Derran said:
My understanding is that cm 10.1.3 is android version 4.2.2 and the gapps he used worked. No force closes or anything but one thing he mentioned is that his first flashing of the ROM did not include a full wipe. He did not format system. And even after a full wipe in twrp 2.6.1; data, cache, android secure, dalvik, and system still nothing. Still shows dead android and failed install
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
What is the exact error message that TWRP is giving?
Gotta wait for my bro to get off work but will post as soon as I can get his phone and give it another go
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Hi – I have a stubborn issue with my Blaze 4G not working on CM roms, I would appreciate any help you guys can provide. Below are the details:
I recently bought a T-Mobile Samsung Galaxy S Blaze 4G, and did the following:
- Rooted it using the following guide (it now has ICS)
- SIM Unlocked it using the following guide (now it works on other networks)
- Updated to CWM 6.0.3.8, since JB roms needs it
- Flashed the T769-UVLH5 modem, since CM support it
And now when I flash CM 10 stable or 10.2 nightly it gets stuck in booting and displaying the CM logo animation screen, after few minutes it reboots and does it all over again.
I remember when I upgraded to CM JB on my SGS3 I needed to flash a JB stock rom on it to get the new boot loaders for JB, but I saw no mention of this on this forum. What else am I missing?
Thanks.
TINGEA said:
Hi – I have a stubborn issue with my Blaze 4G not working on CM roms, I would appreciate any help you guys can provide. Below are the details:
I recently bought a T-Mobile Samsung Galaxy S Blaze 4G, and did the following:
-Rooted it using the following guide (it now has ICS)
-SIM Unlocked it using the following guide (now it works on other networks)
-Updated to CWM 6.0.3.8, since JB roms needs it
-Flashed the T769-UVLH5 modem, since CM support it
And now when I flash CM 10 stable or 10.2 nightly it gets stuck in booting and displaying the CM logo animation screen, after few minutes it reboots and does it all over again.
I remember when I upgraded to CM JB on my SGS3 I needed to flash a JB stock rom on it to get the new boot loaders for JB, but I saw no mention of this on this forum. What else am I missing?
Thanks.
Click to expand...
Click to collapse
You wiped data/cache/system? Reinstall it. Anyways use the new 6.0.4.4 recovery.
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Somcom3X said:
You wiped data/cache/system? Reinstall it. Anyways use the new 6.0.4.4 recovery.
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Click to expand...
Click to collapse
Thanks Somcom. I have to admit that I forgot to do the wipes. but even after doing the wipes (data/system/ factory rest/ cach/devalk) and reinstalling the CM nightly, I still have the same issue.
as for recovery, I updated to the latest version using the rom manager, and according to the official site clockworkmod[dot]com[slash]rommanager (can't post links) I have the latest version for Blaze. how do you get the 6.0.4.4 on blaze?
I still feel it's a ICS vs JB bootloaders issue, but not sure how to proceed next.
Thanks!
TINGEA said:
Thanks Somcom. I have to admit that I forgot to do the wipes. but even after doing the wipes (data/system/ factory rest/ cach/devalk) and reinstalling the CM nightly, I still have the same issue.
as for recovery, I updated to the latest version using the rom manager, and according to the official site clockworkmod[dot]com[slash]rommanager (can't post links) I have the latest version for Blaze. how do you get the 6.0.4.4 on blaze?
I still feel it's a ICS vs JB bootloaders issue, but not sure how to proceed next.
Thanks!
Click to expand...
Click to collapse
No boot loaders man. This is before Samsung's complications.
Recovery is here.
http://d-h.st/AFu
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Thanks Somcom3X, but still didn't work. When installing the CM room in recovery 6.0.4.4 I get a bunch of getprop assert failures. This used to work on the previous version (6.0.3.8). Now the Rom won't install.
Also, I'm curious what did you mean by this is before Samsung's complications?
Thanks
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
TINGEA said:
Thanks Somcom3X, but still didn't work. When installing the CM room in recovery 6.0.4.4 I get a bunch of getprop assert failures. This used to work on the previous version (6.0.3.8). Now the Rom won't install.
Also, I'm curious what did you mean by this is before Samsung's complications?
Thanks
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
After 2011 samsung began installing software and counters to try and prevent people from rooting and installing custom firmwares.
knox is an example of this.
These devices don't have any of that complicated security.
You handy with odin? Your recovery is not right. Just to be clear, what is your model number?
If it is T 7 6 9, your good to go to odin. I'd recommend going back to stock, and then install a recovery and you should be good to go.
Somcom3X said:
After 2011 samsung began installing software and counters to try and prevent people from rooting and installing custom firmwares.
knox is an example of this.
These devices don't have any of that complicated security.
You handy with odin? Your recovery is not right. Just to be clear, what is your model number?
If it is T 7 6 9, your good to go to odin. I'd recommend going back to stock, and then install a recovery and you should be good to go.
Click to expand...
Click to collapse
Thanks again, I use the guide here to convert the image into a tar.md5 to flash using odin, but after flashing successfully I still have the same issue when installing the CM zip file in recovery, and yes it is the T-mobile Samsung Galaxy S Blaze 4G T769.
any other possible causes?
BTW - when I was flashing via Odin my upload phone screen was showing that I have a custom rom and the counter was 1.... do I need to fix that?
TINGEA said:
Thanks again, I use the guide here to convert the image into a tar.md5 to flash using odin, but after flashing successfully I still have the same issue when installing the CM zip file in recovery, and yes it is the T-mobile Samsung Galaxy S Blaze 4G T769.
any other possible causes?
Click to expand...
Click to collapse
SOLUTION:
The reason your stock recovery system keeps getting overwritten at Android startup is because of a script that is being run.* All you need to do is either rename this script or simply delete it.
Please keep in mind that if you restore your stock ROM, this script will be restored with it so you will have to rename or delete it again.* Do the following:*
1.
Make sure your device is powered on and running normally,
2.
Make sure you have rooted your device and that you have all of the necessary permissions in order to manipulate system files.*
3.
In the root file system go to \system\etc
4.
Find the file named install-recovery.sh and either rename it or, as I did, delete it.*
That’s all there is to it.*
Please keep in mind that you will need to flash your custom system recovery one more time after modifying the script file.* After that, reboot away and you will always be able to get back into your new system recovery.
Good Luck and Happy Tweaking.
Click to expand...
Click to collapse
Try that.
Found it here http://mark.candleshoreblog.com/201...-factory-stock-roms-at-android-system-reboot/
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Somcom3X said:
Try that.
Found it here http://mark.candleshoreblog.com/201...-factory-stock-roms-at-android-system-reboot/
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Click to expand...
Click to collapse
Thanks Somcom3X - but I'm not sure this is needed for my case. I read the original blog post and my recovery does not get overwritten. I actually rebooted multiple times into CWM recovery and each time it is the same 6.0.4.4.
I also went into the /system/etc folder and there is no install_recovery.sh file.
to clarify, here is where I'm stuck now:
- when I use CWM 6.0.3.8 CM install completes successfully, but then CM will not boot, and will keep on cycling on the boot logo screen.
- when I use CWM 6.0.4.4 I can't start to install CM as it complained that my phone is not t769.
in all cases I'm using CM 10.2 nightly for T769.
Thanks for the help.
You should delete assert lines at the top of the zip's updater-script and it will let you flash it.
Sent from my SAMSUNG-SGH-T769 using Tapatalk
I removed the assert lines from the updater script, and it was able to complete the install process afterwards, however when I booted the new CM 10.0 system it got stuck on the cyanogenmod boot logo. I made sure I do a system/data rest, cleared cash, and cleared devalk.
I do not think it's an issue with my recovery as I'm getting the same result as I did with the official 6.0.3.8.
Something else is going on.
Any ideas?
Thanks.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
TINGEA said:
I removed the assert lines from the updater script, and it was able to complete the install process afterwards, however when I booted the new CM 10.0 system it got stuck on the cyanogenmod boot logo. I made sure I do a system/data rest, cleared cash, and cleared devalk.
I do not think it's an issue with my recovery as I'm getting the same result as I did with the official 6.0.3.8.
Something else is going on.
Any ideas?
Thanks.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Tar back to stock GB. Upgrade to ICS. Then root and install cwm. Flash away
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Somcom3X said:
You should delete assert lines at the top of the zip's updater-script and it will let you flash it.
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Click to expand...
Click to collapse
Thanks Somcom3X - but this is more trouble than what I wanted to put in - I'll stick with the rooted stock ROM I have. I was hoping the process was a little more straight forward, similar to my SGS3.
thanks for all your help thus far!
Somcom3X said:
Tar back to stock GB. Upgrade to ICS. Then root and install cwm. Flash away
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Click to expand...
Click to collapse
Ok, my rooted ICS stock is acting up (random shutdowns and such), so I need to give this another try and get this phone to CM.
I tared back to stock GB, skipped the upgrade to ICS (was not able to upgrade via the ROM software update option), flashed CWMR (5.0.4.x) via Odin, upgraded to CWMR 6.0.4.5, installed CM 11 nightly, and then wiped data/factory rest and Dalvik .... and ....
it is still stuck on the boot screen....
I seriously would appreciate a silver bullet right now!
TINGEA said:
Ok, my rooted ICS stock is acting up (random shutdowns and such), so I need to give this another try and get this phone to CM.
I tared back to stock GB, skipped the upgrade to ICS (was not able to upgrade via the ROM software update option), flashed CWMR (5.0.4.x) via Odin, upgraded to CWMR 6.0.4.5, installed CM 11 nightly, and then wiped data/factory rest and Dalvik .... and ....
it is still stuck on the boot screen....
I seriously would appreciate a silver bullet right now!
Click to expand...
Click to collapse
Hmm. Go back to stock ics, flash a 10.2 recovery, then flash whatever you desire.
Sent from my SAMSUNG-SGH-T769 using Tapatalk
What is a10.2 recovery? Is it a certain version of CWMR? And do I need to flash it via Odin? Thanks
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
TINGEA said:
What is a10.2 recovery? Is it a certain version of CWMR? And do I need to flash it via Odin? Thanks
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
It would be cwm 6.0.2.7
You can flash the img through a zip or by terminal on the phone.
Odin needs a tar'd recovery img
Sorry been very busy.
Have you tried this?
http://forum.xda-developers.com/showthread.php?t=2577265
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Thanks Somcom3X - I looked all over this forum and the internet, and could not find a link for a 6.0.2.7 CWM for Blaze - I found it for other phones but not Blaze. can you please point me to a link if you happen to know of one. the official site does not have an archived list of previous versions.
as for the provided link, I did follow it through, and downloaded the recovery Tar (it was CWM 5.5.04) but that yielded the same results after installing CM 10 and 10.2 - stuck at boot screen logo. I'm reasonably confident now that it is not a recovery issue, as I flashed half a dozen different versions and none worked with CM 10, 10.2, or 11.... it has to be something else!
Thanks.
TINGEA said:
Thanks Somcom3X - I looked all over this forum and the internet, and could not find a link for a 6.0.2.7 CWM for Blaze - I found it for other phones but not Blaze. can you please point me to a link if you happen to know of one. the official site does not have an archived list of previous versions.
as for the provided link, I did follow it through, and downloaded the recovery Tar (it was CWM 5.5.04) but that yielded the same results after installing CM 10 and 10.2 - stuck at boot screen logo. I'm reasonably confident now that it is not a recovery issue, as I flashed half a dozen different versions and none worked with CM 10, 10.2, or 11.... it has to be something else!
Thanks.
Click to expand...
Click to collapse
I'm very sorry for the delay. Been very very busy.
https://www.dropbox.com/s/awp1zy4u3x34a2v/CWM-cm-10.2-Recovery-t769.zip
That is my personal 10.2 recovery. Works fine for me.
The author is me, but I was too lazy to change the lines.
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Hi There,
My Atrix 2 is running on Slimkat 4.4.3.build.5.9, while trying to update the same via OTA getting error as Can not read SlimOTA properties.
Pls help!!!!!!
Thanks in advance!
Atrix2dBeast said:
Hi There,
My Atrix 2 is running on Slimkat 4.4.3.build.5.9, while trying to update the same via OTA getting error as Can not read SlimOTA properties.
Pls help!!!!!!
Thanks in advance!
Click to expand...
Click to collapse
No one can help you. Because atrix 2 is not officially supported by slim team.
Sent from my MB865 using XDA Premium 4 mobile app
Can not read SlimOTA properties!!
noranora said:
No one can help you. Because atrix 2 is not officially supported by slim team.
Sent from my MB865 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Okay......thanks for the reply. But then how can I update it to 4.4.4 Build 6.0 without Format/Wiping data?
Pls help @alteredlikeness
Atrix2dBeast said:
Okay......thanks for the reply. But then how can I update it to 4.4.4 Build 6.0 without Format/Wiping data?
Click to expand...
Click to collapse
Ideally you should wipe everything and then clean install the ROM. To retain your data and apps, you can take backup using titanium backup or take backup of data partition using BMM then restore (though I am not too sure about BMM method if it really works perfectly).
If you don't want to wipe then you can try to dirty flash the 6.0 ROM on the existing version. Just don't perform format or wipe, just flash the ROM+Gapps. see If it goes well.
Can not read SlimOTA properties!!
Jack Sparrow xda said:
Ideally you should wipe everything and then clean install the ROM. To retain your data and apps, you can take backup using titanium backup or take backup of data partition using BMM then restore (though I am not too sure about BMM method if it really works perfectly).
If you don't want to wipe then you can try to dirty flash the 6.0 ROM on the existing version. Just don't perform format or wipe, just flash the ROM+Gapps. see If it goes well.
Click to expand...
Click to collapse
Okay...that means there is no way to get OTA update:crying:.........anyways...thanks a lot for replying!
Atrix2dBeast said:
Okay...that means there is no way to get OTA update:crying:.........anyways...thanks a lot for replying!
Click to expand...
Click to collapse
Even if there is OTA support in the ROM then also it doesn't mean that the phone will be updated automatically like how it happens in case of official firmware updates. The OTA in most of the custom ROMs just downloads the ROM file on your phone, thats it. Rest you will have to manually install/flash the ROM using that downloaded file like how you maybe doing it now. OTA just cuts the step of finding and downloading the ROM file from internet. So IMO its not a feature which matters much.
Ok bro...thanks a lot for sharing the info and for the timely response...
Sent from my MB865 using XDA Free mobile app
Can not read SlimOTA properties!!
Jack Sparrow xda said:
Ideally you should wipe everything and then clean install the ROM. To retain your data and apps, you can take backup using titanium backup or take backup of data partition using BMM then restore (though I am not too sure about BMM method if it really works perfectly).
If you don't want to wipe then you can try to dirty flash the 6.0 ROM on the existing version. Just don't perform format or wipe, just flash the ROM+Gapps. see If it goes well.
Click to expand...
Click to collapse
Tried dirty flashing...it worked...post booting found that gapps were not working....so flashed latest gapps again...now its rebooting again n again....what to do??
Atrix2dBeast said:
Tried dirty flashing...it worked...post booting found that gapps were not working....so flashed latest gapps again...now its rebooting again n again....what to do??
Click to expand...
Click to collapse
Perhaps it's time for you to clean flash? Idk. Sounds like it's bootlooping. 5.9 gapps was 4.4.3. Meanwhile version 6 is 4.4.4. Sometimes its best for you to start afresh to avoid any issue.
Sent from my MB865 using XDA Premium 4 mobile app
Atrix2dBeast said:
....so flashed latest gapps again...now its rebooting again n again....what to do??
Click to expand...
Click to collapse
No option other than clean install. That type of issue why its always recommended to clean flash the newer versions.
To have little bit of hope, backup the data partition using BMM then later try to restore the data partition using that backup once you successfully flash the ROM. If it works then all is good and if it doesn't then....
Can not read SlimOTA properties!!
Jack Sparrow xda said:
No option other than clean install. That type of issue why its always recommended to clean flash the newer versions.
To have little bit of hope, backup the data partition using BMM then later try to restore the data partition using that backup once you successfully flash the ROM. If it works then all is good and if it doesn't then....
Click to expand...
Click to collapse
Okay....flashed 4.4.4 built 6 again(clean install)...rebooted...and then flashed gapps for the same build....but again its rebooting....had to fxz again...what i am doing wrong here???
Atrix2dBeast said:
Okay....flashed 4.4.4 built 6 again(clean install)...rebooted...and then flashed gapps for the same build....but again its rebooting....had to fxz again...what i am doing wrong here???
Click to expand...
Click to collapse
What are the steps you are following? Are you flashing using BMM? Which system? What GApps version? Try not to reboot between ROM and GApps flashing. Flash only minimal GApps.
I haven't faced any such issue with any of the ROMs so far. I just follow the BMM guide word to word.
Right now I am having 5.10 build and its pretty much stable and almost bug-free for me on System 1. There are few experiments going on in the builds after 5.10 so I would recommend you should also flash the 5.10 build.
Can not read SlimOTA properties!!
Jack Sparrow xda said:
What are the steps you are following? Are you flashing using BMM? Which system? What GApps version? Try not to reboot between ROM and GApps flashing. Flash only minimal GApps.
I haven't faced any such issue with any of the ROMs so far. I just follow the BMM guide word to word.
Right now I am having 5.10 build and its pretty much stable and almost bug-free for me on System 1. There are few experiments going on in the builds after 5.10 so I would recommend you should also flash the 5.10 build.
Click to expand...
Click to collapse
I am using BMM only....on system 1...made a mistake of rebooting between ROM and GApps flashing.:silly: