Related
Hi,
Thanks to thiagodark I've finally rooted my phone (Got it in Feb)
Now for step 2 ... Flashing Roms
Can some one suggest where I start? I see that the [ROM] [Nightly] CyanogenMod 7 (alpha) is pretty popular ... would that be a recommended start?
Two things I look to after flashing a rom would be a) install BLN (so, the rom has to have support for that) and b) should have the power widget in the notification (where I can pull down notification and toggle wifi, sound, bluetooth or whatever). Would also prefer if the a 2.3.4 Rom.
Two other things I'd like to know and would really appreciate help with are:
a) Can I flash a rom and then install any kernel ... are they all compatible?
b) I did a Google Search and found these steps to Flash a Rom:
Flash a Custom ROM
1. Head over to our Nexus S ROMs section, choose a ROM you want and download it and save it to your computer.
2. Plug your phone in and mount the internal storage so we can transfer files to it.
3. Copy the ROM .zip file over to the root of the internal storage (NOT in any folders, just on the internal storage itself).
4. Turn off the phone.
5. Turn the phone on by holding down Volume Up and Power until Fastboot mode comes up.
6. Scroll down and select Recovery and wait for the phone to reboot into recovery mode.
7. Once in recovery mode, scroll to Backup, then select Backup and wait for the phone to backup its current ROM.
8. Once it is done, select Wipe Data
9. Then select Flash zip from SD Card
10. Select choose zip from sd card.
11. Select the ROM’s zip file you loaded onto the internal storage earlier and wait for it to flash. Done!
12. Repeat to load a different ROM.
Click to expand...
Click to collapse
My question is .... Is step 7 what is called a Nandroid? And do I need to do this every time or do I just need to do it when I think that the current setup is good enough to back up? ... yes, I will do it the first time and then only when I think I like a Rom, but want to try another and may revert.
Thanks a ton
Paparasee said:
Hi,
Thanks to thiagodark I've finally rooted my phone (Got it in Feb)
Now for step 2 ... Flashing Roms
Can some one suggest where I start? I see that the [ROM] [Nightly] CyanogenMod 7 (alpha) is pretty popular ... would that be a recommended start?
Two things I look to after flashing a rom would be a) install BLN (so, the rom has to have support for that) and b) should have the power widget in the notification (where I can pull down notification and toggle wifi, sound, bluetooth or whatever). Would also prefer if the a 2.3.4 Rom.
Two other things I'd like to know and would really appreciate help with are:
a) Can I flash a rom and then install any kernel ... are they all compatible?
b) I did a Google Search and found these steps to Flash a Rom:
My question is .... Is step 7 what is called a Nandroid? And do I need to do this every time or do I just need to do it when I think that the current setup is good enough to back up? ... yes, I will do it the first time and then only when I think I like a Rom, but want to try another and may revert.
Thanks a ton
Click to expand...
Click to collapse
First you will want to do is download ROM manager onto your phone, then flash the latest Recovery from within it.
Then you should do a Nandroid (this is the backup option in recovery... do this while everything is stock) this backsup your whole phone (apart from SD card) so if you screw something up you can restore it! It is real useful, you can nandroid as much as you like, all it is is an image of your phone.
If you are just starting out i would avoid the CM nightlies and find the stable thread which is 7.0.3. That coupled with Netarchys latest kernel (includes BLN) really works wonders.
As far as the actuall flashing, all you need to do is copy both zip files onto your sd card, reboot into the recovery (you can do that from within the ROM manager).
Once in the Recovery, wipe data,cache and dalvik, then select flash from zip and choose the rom.
Wipre cache and dalvik again and then flash the kernel and restart the phone.
Thats it you should be good to go. If you ever get any Force Closes restart into recovery again and run the Fix permissions
Happy flashing
Edit
Compatibility wise, CM 7.0.3 is still android 2.3.3 (will be updated to 2.3.4 with cm7.1) so you need a 2.3.3 kernel. You also need to know if your phone is NS3G or NS4G, they are not compatible
Thanks bringonblink ... guess I'm starting to get an understanding now.
Is this Rom Manager available on the market? ... I'll check
Since rooting, I've used my phone for a day, so I presume you suggest that I wipe data and then do the nandroid in step 7 above, then install the Rom manager and go from there?
I understand your suggestion of the stable CM7. Since there is just one link for the download, no confusions
The Netarchy though is a different story ...
What is the CFS and BFS build stuff.
I'm currently using a Nexus S i9020 with 2.3.4.
So, I use the CM7 + which version of Netarchy?
Thanks once again
Paparasee said:
Thanks bringonblink ... guess I'm starting to get an understanding now.
Is this Rom Manager available on the market? ... I'll check
Since rooting, I've used my phone for a day, so I presume you suggest that I wipe data and then do the nandroid in step 7 above, then install the Rom manager and go from there?
I understand your suggestion of the stable CM7. Since there is just one link for the download, no confusions
The Netarchy though is a different story ...
What is the CFS and BFS build stuff.
I'm currently using a Nexus S i9020 with 2.3.4.
So, I use the CM7 + which version of Netarchy?
Thanks once again
Click to expand...
Click to collapse
Rom Mangager is in the market yes.
No before you wipe , flash, crack, hack ANYTHING else again do a bone stock Nandroid backup and save it on your pc or something. This is because RIGHT NOW your phone is in a working state. THEN wipe cache ,dalvik and data and flash Rom.
7.0.3 is really nice, i had been keepign upwith the nightlies but for me 7.0.3 is the sweet spot... will flash to 7.1 stable when its out though xD.
CFS and BFS are different types of shedulers that run the phone (there is a proper explanation in netarchys thread on the first post i think)
You will want to get CFS as it is mroe stable and generally more user friendly lol.
You'll want CM7.0.3 + CFS Universal 2.3.3 1.3.4
Hey bringonblink ... thank you for your reply
I installed Rom Manager as suggested and then flashed the latest Recovery from within it. Booted into Recovery and did a backup. I then went rebooted, went to my internal storage and found the backup in a clockworkmod folder.
I then went to Rom Manager again and clicked on "Install Rom from SD card". I chose update-cm-7.0.3-NS-signed.zip, ticked Backup, Wipe Data and cache and Wipe Dalvik Cache then pressed ok to reboot.
I then got the big triangle with the ! and droid ... waited, nothing happened so I pressed power and volume up. ... this takes me to the regular stock recovery.
Why not to CWM recovery? Did I do something wrong?
Thanks for any help
Hmm flash the recovery again, but from rom manager choose reboot to recovery, don't actually update in rom manager
Sent from my Nexus S using XDA App
bringonblink said:
Hmm flash the recovery again
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
I guess that was the key ... when I flashed recovery again, and then chose to install the rom with all those options ticked, it worked!!!!
Am now using a custom rom ... THANK YOU!!!
Now to the Netarchy kernel ... again ... through CWM recovery I presume.
PS: I never expected a reply so soon ... thought you might be sleeping ... thanks again.
Paparasee said:
I guess that was the key ... when I flashed recovery again, and then chose to install the rom with all those options ticked, it worked!!!!
Am now using a custom rom ... THANK YOU!!!
Now to the Netarchy kernel ... again ... through CWM recovery I presume.
PS: I never expected a reply so soon ... thought you might be sleeping ... thanks again.
Click to expand...
Click to collapse
Thats alright was on my way to work , so on the phone with xda app xD.
Yup same deal again for kernel
Thanks pal ... really appreciate it!
Installed the kernel & google addons too!
All ok now except ... don't have Gmail why is that and how do I get Gmail?
Thanks again!
Paparasee said:
Thanks pal ... really appreciate it!
Installed the kernel & google addons too!
All ok now except ... don't have Gmail why is that and how do I get Gmail?
Thanks again!
Click to expand...
Click to collapse
Market
Sent from my Nexus S using XDA App
matt2053 said:
Market
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Ayeeeeeeeee
For some strange reason, when I go to the market from my PC, I see Gmail, but when I try to install, I get the message:
This item cannot be installed in your device's country!
If I go through the market on my phone, I just cannot find gmail although there is a lot of other apps that include the word gmail.
incidentally ... after flashing CM7, anything I try installing through my PC browser gives the same result as above...
By the way ... any reason why gmail is not included with the rom and with the google addons?
Gmail is in the usual Google Apps package. Maybe try flashing it again.
Paparasee said:
For some strange reason, when I go to the market from my PC, I see Gmail, but when I try to install, I get the message:
This item cannot be installed in your device's country!
If I go through the market on my phone, I just cannot find gmail although there is a lot of other apps that include the word gmail.
incidentally ... after flashing CM7, anything I try installing through my PC browser gives the same result as above...
By the way ... any reason why gmail is not included with the rom and with the google addons?
Click to expand...
Click to collapse
gmail is not available yet in some countries. what you can do is install marketenabler and fake your provider and install gmail.
on cm7, the google apps are not included as they are propriety apps, they are not open source ( if u understand what i mean)
a few years ago, google tried to sue cyanogen for distributing the google apps through cyanogenmod. they then reached an agreement that cyanogenmod could exist provided no gapps were included within.
Hey, thanks for that explanation ... let me check the work around
Hey! am back!
Rather than go through the the trouble of installing market enabler, I just went about testing a couple of other Roms ... since I also wanted to know in what way other roms were different.
I tried Liquid and Infinity ... both were nice and both had gmail, so was happier with them! Wonder why Google went after the cyanogen guys, but the others include those apps
Anyway ... am now downloading Zulu.
After having installed custom roms such as Cyanogen-mod, Liquid and Infinity, I've realized that there are some must haves ...
a) Gmail & Talk (working over 3G)
b) Sip over 3G
c) Power Controls in notification (sexy as in Liquid)
d) screen lock as in Cyanogen (the modded rotary type with an option to add a 3rd party app)
e) BLN support (have not yet got used to the small lights turning on as in BLN but, guess I'll learn).
Would some one know of a Rom that caters to the above ... I'm experimenting with each, but if someone can help, I'd be able to settle in faster
Cheers!
Paparasee said:
Hey! am back!
Rather than go through the the trouble of installing market enabler, I just went about testing a couple of other Roms ... since I also wanted to know in what way other roms were different.
I tried Liquid and Infinity ... both were nice and both had gmail, so was happier with them! Wonder why Google went after the cyanogen guys, but the others include those apps
Anyway ... am now downloading Zulu.
After having installed custom roms such as Cyanogen-mod, Liquid and Infinity, I've realized that there are some must haves ...
a) Gmail & Talk (working over 3G)
b) Sip over 3G
c) Power Controls in notification (sexy as in Liquid)
d) screen lock as in Cyanogen (the modded rotary type with an option to add a 3rd party app)
e) BLN support (have not yet got used to the small lights turning on as in BLN but, guess I'll learn).
Would some one know of a Rom that caters to the above ... I'm experimenting with each, but if someone can help, I'd be able to settle in faster
Cheers!
Click to expand...
Click to collapse
They went after Cyanogen because it is the biggest Most ROMS are based off of it too.
BLN is needed in the kernel, not ROM, Netarchys support this.
I think you will like NScollab, runs off of CM7 with some nice tweaks, also includes netarchys kernel as default.
Oh and it already has all gapps included , including gmail
What a coincidence ... was just downloading NScollab ... 28% done
Thanks!
bringonblink ... am liking this NScollab rom
Edit: Never mind ... googled and found ... no use to me
When I go to the market, I get a pop up asking me if I need to install some apps. Any idea what they do and if it is needed?
The apps are:
Google Chrome to Phone ... never heard of this
Google Goggles ... I know this and won't need it.
Kickback
Soundback
Talkback ... these are the 3 I have no idea about!
Click to expand...
Click to collapse
Thanks ... and cheers!
CyanogenMod 11.0 is a free, community built distribution of Android 4.4.2 (KitKat) which greatly extends the capabilities of your phone.
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
This is a build of CM11.0 for the Samsung Epic 4G. It may cause all the things in the disclaimer to happen, or steal your girlfriend while you are busy flashing ROMs.
Please submit a patch to our Gerrit instance if you want to help out.
WARNING: If you are any build prior to the 11/12 CM11.0 build, this will wipe your data due to a resizing of the mtd partitions. If you wish to go back to another ROM, you will need to ODIN back to stock. If updating from a build prior to 11/12, it is recommended to format /system, /data, and /cache AFTER making your backup.
Recommended steps before you install:
1. Install AppBak from Market, run it and save a list of all your apps.
2. Install SMS Backup and Restore from Market, run it and backup your SMS history.
3. Install Call Logs Backup and Restore from Market, run it and backup your call log history.
4. Boot into CWM recovery. Make a full Backup. You will need this backup later if you decide to go back to your previous ROM and data.
5. It is recommended that you wipe data before installing CM11.0 for the first time.
Additional Disclaimer:
Any bug reports coming from an Unofficial CM11.0 build, or a modified/patched Official CM11.0 build (modem patch, kernels, etc.) should be directed to the originating thread. It is hard enough to provide bug support for the official releases without having to worry about bugs that may have been introduced by outside means. Bug reports are very welcome if you can reproduce them after flashing back to an official, stock build. We do want to be able to fix all the things. Thank you.
**Google Apps are not included in these ROMs. You'll need to install those yourself if you want them.
Nightly Builds
http://download.cyanogenmod.org/?device=epicmtd
Known Issues:
- 3g data basically works - Although it has the wifi/mobile data toggle bug again. Disable mobile data before turning on wifi for best results. Fixed 12/04
- Stock browser (and anything else using webviews) - Big black boxes. Use another browser temporarily until fixed. Fixed 11/17
- Wimax temporarily disabled
- Current bluetooth behavior untested for improvement.
- Wired headset mic & buttons. (Yeah, Yeah, someday...)
- Probably more.
Previous preview Builds
cm-11-20140101-UNOFFICIAL-epicmtd.zip
cm-11-20131226-UNOFFICIAL-epicmtd.zip
cm-11-20131211-UNOFFICIAL-epicmtd.zip
cm-11-20131210-UNOFFICIAL-epicmtd.zip
cm-11-20131206-UNOFFICIAL-epicmtd.zip
cm-11-20131205-UNOFFICIAL-epicmtd.zip
cm-11-20131117-UNOFFICIAL-epicmtd.zip
cm-11-20131112-UNOFFICIAL-epicmtd.zip
Potentially Unstable Build - 12/04
Alot more features have been added back in, but I've been experiencing some weirdness especially after a reboot. Certain issues seem to be tied to certain gapps packages. I have not determined the best one to use, but I post this build for those of you who want something more current.
Features (including but not limited to the following, some of which may have already existed in previous builds):
*** I think I have taken even more space from /data to give to /system. Make your backups before flashing ***
- Working data (data toggle shuffle no longer necessary)
- Quick access ribbon
- Quick access panel (with Torch enabled)
- Circle battery
- Lockscreen shortcuts
- Vibrator intensity and capacitive button backlight control
cm-11-20131204-UNOFFICIAL-epicmtd.zip
EDIT:
Stable version
This version uses the boot.img from the 11/17 build (thanks to didhiy for experimenting), therefore it has the same partition layout as the 11/17 build. Should be safe to flash over the 11/17 build, but backups are still always recommended.
cm-11-20131204-UNOFFICIAL-fixed-epicmtd.zip
12/10/2013
- All kernel & device patches included in the latest build have been merged or uploaded to gerrit (to possibly be merged later).
- Additional patches necessary for the build include the following:
http://review.cyanogenmod.org/#/c/55500/
http://review.cyanogenmod.org/#/c/55109/
http://review.cyanogenmod.org/#/c/55110/
http://review.cyanogenmod.org/#/c/55111/
http://review.cyanogenmod.org/#/c/55512/ (12/11/13) Merged.
- Recommended gapps: http://d-h.st/eWW (12/09).
Actually, it looks like the Wifi / 3G data toggle shuffle bug is back. So as a reminder, if you want to turn on wifi, turn off mobile data first. Otherwise, when you turn off wifi, your 3g data will not reconnect without a reboot.
First! :laugh:
Amazing work bbelos! I will have to give this a try when I get a little free time.
bricked
this may have softbricked my phone im not sure I tried to install it and then the phone turned off now it wont go past the boot screen
Jduncan312 said:
this may have softbricked my phone im not sure I tried to install it and then the phone turned off now it wont go past the boot screen
Click to expand...
Click to collapse
Can you still boot into recovery? Try flashing it again. Sometimes the repartitioning is a little touchy.
Sent from my SPH-D700 using xda app-developers app
no I cant..it wont even turn on now I cant even get into download mode lol
Jduncan312 said:
no I cant..it wont even turn on now I cant even get into download mode lol
Click to expand...
Click to collapse
try to pull battery for a while, put it again then try download mode
Wow, can't believe you have an unofficial officialish version up and running before my GSM Gnex.
Downloading now... Hope it fares well in terms of battery.
P.S. Not even having an unofficial CM11 for Galaxy Nexus is lame!
Sent from Google Nexus 4 @ Android 4.4 KRT16M
Jduncan312 said:
no I cant..it wont even turn on now I cant even get into download mode lol
Click to expand...
Click to collapse
Well, I just re-tested it. Restored back to cm-10.2 and downloaded the zip from the link. Wipe data/reset and format /system (like the warning recommends), and flashed the zip. It rebooted right away back into recovery (because it had to flash the kernel first). Flashed the zip again, then gapps and then I rebooted with a successful boot-up.
Worst case if you still can't get into recovery, you'll still be able to get into download mode and get restored and try again. There shouldn't have been any way for it to kill the bootloader.
Sent from my SPH-D700 using xda app-developers app
Downloading now, I want to try the sweety kit kat on epic
Sent from my SPH-D700 using xda app-developers app
I had to flash gapps a second time (after the included recovery replaced twrp) but so far it works just fine.
ART helps a ton, it's instantly noticeable, but takes up quite a bit of space.
You guys rock.
Still Epic.
Edit: webview/browser seems to be very unstable. half of the surface blacks out and lags the device. this is with both dalvik and ART
Sent from my LG-LS970 using Tapatalk
bbelos said:
Well, I just re-tested it. Restored back to cm-10.2 and downloaded the zip from the link. Wipe data/reset and format /system (like the warning recommends), and flashed the zip. It rebooted right away back into recovery (because it had to flash the kernel first). Flashed the zip again, then gapps and then I rebooted with a successful boot-up.
Worst case if you still can't get into recovery, you'll still be able to get into download mode and get restored and try again. There shouldn't have been any way for it to kill the bootloader.
Sent from my SPH-D700 using xda app-developers app
Click to expand...
Click to collapse
tested... boot without problem :thumbup:
first impression, can't install apk from file manager
with "package parsing error" warning
Anyone else keep getting errors with phone and gapps processes booting up even after wiping data/cache, format /system and wiping dalvik?
Just tested it out. Lags are significantly more obvious than 4.3 and 4.2, but the beauty of KitKat totally overwhelms that. One thing I noticed is that Mass Storage speed is slower than usual.
Sent from Google Nexus 4 @ CM11
---------- Post added at 06:23 PM ---------- Previous post was at 06:20 PM ----------
didhiy said:
can't install apk from file manager
with "package parsing error" warning
Click to expand...
Click to collapse
Oops... same here. Forgot to check up on that. Reverting.
Sent from Google Nexus 4 @ CM11
mi7chy said:
Anyone else keep getting errors with phone and gapps processes booting up even after wiping data/cache, format /system and wiping dalvik?
Click to expand...
Click to collapse
I didn't try install gapps, no problem with phone service
AndyYan said:
Just tested it out. Lags are significantly more obvious than 4.3 and 4.2, but the beauty of KitKat totally overwhelms that. One thing I noticed is that Mass Storage speed is slower than usual.
Sent from Google Nexus 4 @ CM11
---------- Post added at 06:23 PM ---------- Previous post was at 06:20 PM ----------
Oops... same here. Forgot to check up on that. Reverting.
Sent from Google Nexus 4 @ CM11
Click to expand...
Click to collapse
I really like the dialer :thumbup:
so beauty & pretty
mi7chy said:
Anyone else keep getting errors with phone and gapps processes booting up even after wiping data/cache, format /system and wiping dalvik?
Click to expand...
Click to collapse
I can't get gapps to work either. I've tried a few different ones that are supposed to be for 4.4 but all force close and stop the boot process. End up with a black screen and force close pop ups. I'm guessing a compatible gapps isn't available yet or I just haven't been able to find it.
didhiy said:
tested... boot without problem :thumbup:
first impression, can't install apk from file manager
with "package parsing error" warning
Click to expand...
Click to collapse
Same error..
I have flashed the gapps and can't sign in to google
Reverting to CM 10.2 no problem here like Jduncan said
Sent from my SPH-D700 using xda app-developers app
I start with a fresh wipe of my phone and then install BeanStalk with gapps (I'm currently using BS version 4.4.275 with gapps 20140105. Everything is fine for months. Then a couple of apps will start to crash a few times (the camera, dialer, browser and google apps). I've stopped using titanium backup and clockwork mod to restore my data because they were causing issues. Then the force closes become more and more frequent. I ran fix permissions and i have know clue if it helped or not. Then finally all hell breaks loose and everything begins to force close and give errors of no space left on phone. No launcher will stay open everything just bugs out. This seems to be an on going matter. It doesn't seem to resolve no matter what rom I run. I've gone through every folder sizing it and my phone is not out of space. I am getting very frustrated with my Infuse. I don't understand what some of the stuff means in my catlog file. If someone could help I'd greatly appreciate it.
i found out that Google+ and Google Drive might be the cause (such as when you upload or backup your photos to those clouds)
if you have time, go read those last 10 pages of BeanStalks, you will see what others have offered to resolve this issues
as for me, I'd do full wipe, specially format the sdcard0 (keep the Rom and Gapps to your SDcard1), and stop using the two Google services mentioned above. and use another Gapps (I am using the minimal one) Good luck!
Same problem with Unofficial CM 11.2 also
Exactly the same issue I am having with Unofficial CM 11.2 from scott.
I have been using Scott Harts Unofficial CM from 10.1 to 11.2 on my Samsung infuse and each time i notice a pattern.
Each of the above ROMs start out pretty smooth, and the phone works without any issues for 6 months or so. Then occasionally and app or two start crashing. Then in a weeks time all hell breaks loose and almost all apps start crashing such that the phone becomes unusable. Especially trebuchet starts crashing and that is the end of story.
In the past i have noticed this happens a month or so after an updated rom has been released and I used to upgrade to the new one and the cycle continues.
I am currently on the latest Unoffical CM 11_2 (Kitkat) and the appropriate Gapps installed and the same issue has happened twice.
I have tried the following to fix the issue and nothing helps
1. Clear data for trebuchet and a bunch of other apps.
2. Reinstall Gapps
3. Wipe Cache >> Wipe Dalvik Cache
4. Wipe Cache >> Wipe Dalvik Cache > install Gapps
5. Wipe Cache >> Wipe Dalvik Cache > install custom Rom >> install gapps >> wipe cache and dalvik again
The only way I have been able to get it working in the past is
1. Wipe data/factory reset > Clear Cache > clear Dalvik cache and possibly reinstall ROM and gapps (not sure, but I guess factory reset also does the trick)
So my phone is stuck in this mode and I would like to help debug the situation. Can someone help with the next steps? So that I can capture all required information before I do a factory reset .
Unable to get RSA prompt
Well I went ahead with a factory reset, installed Unofficial CM11_2 from Scott. Got the latest gapps from goo.im and phone seems normal again. But that is the expected behavior untill it starts acting up again.
I tried a lot to connect the phone through ADB and each time it remains unauthorized.
I tried on 2 different laptops, Windows 7, Windows Vista as well as Ubuntu - it always remained unauthorized and no matter what i tried ... changing USB ports , OS machines...nothing helped.
I never got the RSA signature prompt on my phone so could not do anything with ADB.
Any body has any ideas ?
hemen_kap said:
Well I went ahead with a factory reset, installed Unofficial CM11_2 from Scott. Got the latest gapps from goo.im and phone seems normal again. But that is the expected behavior untill it starts acting up again.
I tried a lot to connect the phone through ADB and each time it remains unauthorized.
I tried on 2 different laptops, Windows 7, Windows Vista as well as Ubuntu - it always remained unauthorized and no matter what i tried ... changing USB ports , OS machines...nothing helped.
I never got the RSA signature prompt on my phone so could not do anything with ADB.
Any body has any ideas ?
Click to expand...
Click to collapse
This has been an issue for a while, if the problem is showing up like this:
http://forum.xda-developers.com/showthread.php?t=2175261
Honestly haven't tried ADB with the newer stuff (namely Beanstalk), I just know that ADB as been a problem in the past for Scott's ROM's.
joel.maxuel said:
This has been an issue for a while, if the problem is showing up like this:
http://forum.xda-developers.com/showthread.php?t=2175261
Honestly haven't tried ADB with the newer stuff (namely Beanstalk), I just know that ADB as been a problem in the past for Scott's ROM's.
Click to expand...
Click to collapse
Yes, it is the same problem. Any suggestions ? How is the AOSP based Carbon ROM, any idea if it has the same issue too ?
hemen_kap said:
Yes, it is the same problem. Any suggestions ? How is the AOSP based Carbon ROM, any idea if it has the same issue too ?
Click to expand...
Click to collapse
Not sure about the other ROM's. I could go on a flashing journey, but I have two new devices I'm getting adjusted to right now. If you are not tied down to CM (don't know if it's your DD), I would suggest trying Carbon or CyanFox.
Me, I didn't need ADB that much at the time so I stuck with what I have. Not a solution, but I hope you find a ROM that works (partnered with a minimal gapps).
joel.maxuel said:
Not sure about the other ROM's. I could go on a flashing journey, but I have two new devices I'm getting adjusted to right now. If you are not tied down to CM (don't know if it's your DD), I would suggest trying Carbon or CyanFox.
Me, I didn't need ADB that much at the time so I stuck with what I have. Not a solution, but I hope you find a ROM that works (partnered with a minimal gapps).
Click to expand...
Click to collapse
Unfortunately the infuse is the only phone I have (so my DD)...but the lure to test the ADB on carbon is also compelling for me. Let me try moving to a non smart phone and try this out.
OK. So i installed the Carbon KK nightly, and encountered the same issue. adb devices always lists the phone as
0123456789ABCDEF unauthorized.
Also i never received the rsa prompt...
Moreover the device key seems to suggest it is some default value as compared to an actual device key.
Got it Working !!!
Ok so finally got it working.
I moved away from Scott's Unofficial CM11_2 on my daily driver and moved to Carbon ROM. Loving the new rom so far.
Once i moved to this ROM, I started adb on my desktop (adb kill-server, adb start-server) and was waiting
then on phone enabled Developer options and Android debugging over USB and connected the phone to desktop, and zingggg I get the RSA prompt.
One important thing it read is that you phone should be unlocked when you connect it to your desktop, so in case you have things like PIN or gestures that lock your screen....ensure that your screen is not locked when the phone is being connected.
Not sure if this was the issue or if it was the CM rom,,,but issue is resolved, I am loving Carbon...so not going back to CM to check the lockscreen theory....but worth a try for someone who is pulling his/her hair out like i was.
Ciao !!!
---------- Post added at 05:00 PM ---------- Previous post was at 04:41 PM ----------
missed mentioning that do not worry about the device id of 0123456789ABCDEF....i noticed it does not change for me even when adb connects properly.
It is the unauthorised state that needs to change to device.
What's the default launcher on Carbon, or does it give you a choice like Beanstalk?
Will be retiring the Infuse soon, so am thinking on what ROM to put on when I go to sell it (or give away). The requirement is that is not overwhelming to a new user. Cyanogenmod has a lot of customization, but it doesn't necessarily get in the way. I'd call it borderline overwhelming. Beanstalk is quite overwhelming, because you are forced to pick a launcher right from the beginning (even though I like it for the Jellybean qualities).
Because of these, I just may return it to stock, but have it rooted and with CWM.
joel.maxuel said:
What's the default launcher on Carbon, or does it give you a choice like Beanstalk?
Will be retiring the Infuse soon, so am thinking on what ROM to put on when I go to sell it (or give away). The requirement is that is not overwhelming to a new user. Cyanogenmod has a lot of customization, but it doesn't necessarily get in the way. I'd call it borderline overwhelming. Beanstalk is quite overwhelming, because you are forced to pick a launcher right from the beginning (even though I like it for the Jellybean qualities).
Because of these, I just may return it to stock, but have it rooted and with CWM.
Click to expand...
Click to collapse
I do not see any option to select a launcher like Scotts CM had. So i guess there is no direct option to select it.
Quick search in the running apps shows Launcher 3 running, and apk also available in the priv-app folder in rom, so can conclude launcher is Launcher3.
I did not find it overwhelming in any way.
-Hemen
hemen_kap said:
I do not see any option to select a launcher like Scotts CM had. So i guess there is no direct option to select it.
Quick search in the running apps shows Launcher 3 running, and apk also available in the priv-app folder in rom, so can conclude launcher is Launcher3.
I did not find it overwhelming in any way.
-Hemen
Click to expand...
Click to collapse
I flashed it last night (latest nightly), and it gave me the option of either Launcher3 or Google Now Launcher. I think if someone who was new to the device would be stumped a little by this, but would probably select the Google Now one (the question would be would they press once or always) and be done with it.
Having something recognizable runs at an advantage here compared to Beanstalk, where, unless you know CyanogenMod (or have played with a lot of launchers) you wouldn't know what to select. That would be overwhelming.
Anyway, I wiped the data again, breezed through setup (skipped everything but language and time zone), so it's all ready to go. If need be I can get them set up with a network and Google account before I throw them to the wind.
EDIT:
I see why I got the prompt ... I used the Paranoid Android micro apps package, which includes ... the Google Now Launcher.
hemen_kap said:
Exactly the same issue I am having with Unofficial CM 11.2 from scott.
I have been using Scott Harts Unofficial CM from 10.1 to 11.2 on my Samsung infuse and each time i notice a pattern.
Each of the above ROMs start out pretty smooth, and the phone works without any issues for 6 months or so. Then occasionally and app or two start crashing. Then in a weeks time all hell breaks loose and almost all apps start crashing such that the phone becomes unusable. Especially trebuchet starts crashing and that is the end of story.
In the past i have noticed this happens a month or so after an updated rom has been released and I used to upgrade to the new one and the cycle continues.
I am currently on the latest Unoffical CM 11_2 (Kitkat) and the appropriate Gapps installed and the same issue has happened twice.
I have tried the following to fix the issue and nothing helps
1. Clear data for trebuchet and a bunch of other apps.
2. Reinstall Gapps
3. Wipe Cache >> Wipe Dalvik Cache
4. Wipe Cache >> Wipe Dalvik Cache > install Gapps
5. Wipe Cache >> Wipe Dalvik Cache > install custom Rom >> install gapps >> wipe cache and dalvik again
The only way I have been able to get it working in the past is
1. Wipe data/factory reset > Clear Cache > clear Dalvik cache and possibly reinstall ROM and gapps (not sure, but I guess factory reset also does the trick)
So my phone is stuck in this mode and I would like to help debug the situation. Can someone help with the next steps? So that I can capture all required information before I do a factory reset .
Click to expand...
Click to collapse
Hi,
I was using CM 10.1 from Scott for like a year and didn't have any trouble at all, really the best ROM. Only had two small problems: wouldn't film on 720p without bugging, and MHL to HDMI was not working.
Now I installed CM 11, with latest gapps ( didn't know there was a CM11.2 ), and camera issue on filming is the same. But now it's worse, battery life is lasting half the time it was before, and gallery is crap, bugging every time. Did you have the same issues? Tell me the post of CM11.2 please..
Sent from my SGH-I997 using XDA Free mobile app
jloibman said:
Now I installed CM 11, with latest gapps ( didn't know there was a CM11.2 ), and camera issue on filming is the same. But now it's worse, battery life is lasting half the time it was before, and gallery is crap, bugging every time. Did you have the same issues? Tell me the post of CM11.2 please..
Click to expand...
Click to collapse
Not sure about this, but I think CM 11.2 is referred to as KitKat 4.4.4, which would be latest in the CM thread. So you are probably already running it.
Sent from my Asus MeMO Pad 8"
jloibman said:
Hi,
I was using CM 10.1 from Scott for like a year and didn't have any trouble at all, really the best ROM. Only had two small problems: wouldn't film on 720p without bugging, and MHL to HDMI was not working.
Now I installed CM 11, with latest gapps ( didn't know there was a CM11.2 ), and camera issue on filming is the same. But now it's worse, battery life is lasting half the time it was before, and gallery is crap, bugging every time. Did you have the same issues? Tell me the post of CM11.2 please..
Sent from my SGH-I997 using XDA Free mobile app
Click to expand...
Click to collapse
apart from the issues that i mentioned - my experience with CM 11.2 has been great. There are some obvious things like MHL etc that do not work, but those are known issues.
joel.maxuel said:
I flashed it last night (latest nightly), and it gave me the option of either Launcher3 or Google Now Launcher. I think if someone who was new to the device would be stumped a little by this, but would probably select the Google Now one (the question would be would they press once or always) and be done with it.
Having something recognizable runs at an advantage here compared to Beanstalk, where, unless you know CyanogenMod (or have played with a lot of launchers) you wouldn't know what to select. That would be overwhelming.
Anyway, I wiped the data again, breezed through setup (skipped everything but language and time zone), so it's all ready to go. If need be I can get them set up with a network and Google account before I throw them to the wind.
EDIT:
I see why I got the prompt ... I used the Paranoid Android micro apps package, which includes ... the Google Now Launcher.
Click to expand...
Click to collapse
You can download the Nova Launcher from the google play store if you want to have the same experience as with Scotts Beanstalk. I love the carbon ROM but I am so accustomed to the Nova launcher that I cant live without it.
hemen_kap said:
Exactly the same issue I am having with Unofficial CM 11.2 from scott.
I have been using Scott Harts Unofficial CM from 10.1 to 11.2 on my Samsung infuse and each time i notice a pattern.
Each of the above ROMs start out pretty smooth, and the phone works without any issues for 6 months or so. Then occasionally and app or two start crashing. Then in a weeks time all hell breaks loose and almost all apps start crashing such that the phone becomes unusable. Especially trebuchet starts crashing and that is the end of story.
In the past i have noticed this happens a month or so after an updated rom has been released and I used to upgrade to the new one and the cycle continues.
I am currently on the latest Unoffical CM 11_2 (Kitkat) and the appropriate Gapps installed and the same issue has happened twice.
I have tried the following to fix the issue and nothing helps
1. Clear data for trebuchet and a bunch of other apps.
2. Reinstall Gapps
3. Wipe Cache >> Wipe Dalvik Cache
4. Wipe Cache >> Wipe Dalvik Cache > install Gapps
5. Wipe Cache >> Wipe Dalvik Cache > install custom Rom >> install gapps >> wipe cache and dalvik again
The only way I have been able to get it working in the past is
1. Wipe data/factory reset > Clear Cache > clear Dalvik cache and possibly reinstall ROM and gapps (not sure, but I guess factory reset also does the trick)
So my phone is stuck in this mode and I would like to help debug the situation. Can someone help with the next steps? So that I can capture all required information before I do a factory reset .
Click to expand...
Click to collapse
OK the exact same problem has started again today on Carbon ROM. Wonder if this is a Cyanogen thing, as that seems to be common between the two.
Anyone else facing this ?
-Hemen
hemen_kap said:
OK the exact same problem has started again today on Carbon ROM. Wonder if this is a Cyanogen thing, as that seems to be common between the two.
Anyone else facing this ?
Click to expand...
Click to collapse
Hmm, don't think I kept a ROM on my Infuse long enough to encounter this problem (except for my several months with CM 10.1, no issues). As for other phones, I use Jellybean on my semi-retired HTC and did not have this problem (closest I came was when I tried out Fly-On mod - lag closures often). But I don't think It's a Jellybean problem.
I think (and this may have been covered already) this has to do with the piddly datadata partition filling up. One way to check is open a terminal emulator (app on the phone of adb shell) and type:
Code:
df
Look for datadata in that listing. If it is in the 90% range, that spells trouble. If that is the case, you could try one of two solutions.
I don't know what possessed the developers to separate the data partitions in KitKat (I know, for "performance reasons") but leave 1/2 a GB for it. Lower end phones these days give you twice that.
Over the past few years or so I've installed ROMs going back to ICS. 99% of the time there was absolutely no issue. I habitually do a (1) factory wipe, (2) dalvik wipe, (3) system format, (4) sdcard0 format, (5) install ROM zip, (6) install gapps, (7) wipe cache and (8) wipe dalvik.
In the hundreds of ROMs I've installed and tested, 1 or 2 were bad compiles, and everyone soon knew it. They were immediately removed from any host site. So, if you're having issues, (1) install you ROM as above, (2) perhaps install a smaller gapps, and/or (3) check that you're not overloading your phone from the PlayStore.
The last and rarest issue could be your phone, but rule of thumb that works 99% of the time is: (1) assume it's always your fault first, and (2) read, read, read, read, read.
Updated: 03/24/2015
Hi all,
I did this mostly for practice but I thought it might be helpful so I went ahead and posted.
Stock LG D850 20f ROM
[*]Rooted/SuperSu
[*]Most bloat removed
[*]Oversharpening fix
[*]Flashable zip
[*]init.d support*
[*]CarrierIQ Remover*
*Init.d support is implemented in ROM only, not the kernel. CarrierIQ is removed automatically after first boot via an init script. Say thanks to @skeevydude for his help in getting this done. I shouldn't say "help", he pretty much did it!
Installation
Flash the Lollipop modem - see @autoprime 's thread here for modem zip
Flash the ROM zip
Wipe cache and dalvik (and in some cases data) if coming from a different ROM
Download
v3* - https://www.androidfilehost.com/?fid=95916177934548695
[QRCODE]https://www.androidfilehost.com/?fid=95916177934548695[/QRCODE]
*No change at all to the ROM itself since v2, I just realized that I've been forgetting to zero out the free space on the image file before uploading, which saves about 600 MB when zipped. New flashable zip is about 1.1 GB instead of 1.7 GB.
Older versions:
v1 - https://www.androidfilehost.com/?fid=95916177934543883
Apps Removed
/system/app:
Google Books
Google Chrome
Google Cloud Print
Google Drive
Facebook
Hangouts
Google Newsstand
Google Play Games
Google Play Music
Google Play Movies and TV
Google Plus
Twitter
/system/priv-app:
ATT Address Book
ATT Caller Name ID
ATT DriveMode
ATT Games
ATT Locker
ATT Lookout
ATT Mobile Locate
ATT Remote Support
ATT Smart Wifi
ATT Mobile TV
ISIS Wallet
ATT Visual Voicemail
MLT (LG tracker)
/system/vendor/app:
Amazon Kindle
ATT Family Map
ATT Home
ATT Keeper
ATT MHS Launcher
ATT Navigator
Uber
DeviceHelp
myATT
YP Mobile
ATT Apps
In case you want some of the ATT apps back, I have uploaded a zip here with those apps. This is NOT a flashable zip. You have a couple of options:
1. You may be able to install these as a normal (user) app by just pulling out the apk and installing the usual way.
2. If that doesn't work as expected, copy the app folder from the zip into the appropriate system folder as listed in the "Apps Removed" section.
Download: ATT Apps
Xposed Info
cmulk said:
Xposed has a couple of bad side effects at this point, so before doing anything you need to use Titanium or something similar to Freeze (this basically what the "helper" does):
LGSmartCover
Weather
Weather Theme
WeatherPlatform
Then you can install xposed as in the thread here: http://forum.xda-developers.com/showthread.php?t=3034811
However, there is still one more bug to keep in mind: Xposed will crash the Tethering and Networks menu. There is no fix for that yet, but as a workaround you can download some apps from the play store (like Mobile Network Settings), to shortcut around the menu that force closes.
Click to expand...
Click to collapse
Credits
@autoprime - Flashable zips, bump'd boot.img, and very clear instructions in his thread here
@timmytim - uploading the lollipop stock images (although I know a lot of others were working on that too)
@Skin1980 - Oversharpening fix
@skeevydude - init.d support and carrierIQ remover
CarrierIQ Removal
CarrierIQ has now been removed!
The removal is done via an init script that runs at boot to disable the IQ service before removing the files in order to prevent a force close. However, if you have to wipe data/factory reset without re-flashing the ROM, you will get a force close on the first boot. The good news is that I've tested this scenario and it should fix itself if you just wait about 20 seconds. In other words, the mentioned script does it's thing to stop the service to fix the force close and you are good to go after that.
Old info below:
cmulk said:
On the 20f lollipop rom (either mine or stock, there's no difference) either freezing LADDM or removing the libraries and LADDM as you mention will cause a force close unless you disable the "IQService" first, which is built into the framework-res.apk. I have repeated it multiple times and it has been discussed quite a bit in the Lounge and other threads. Disabling the service is easy for users to do with the "DisableService" app, and then you can remove LADDM and the libraries as mentioned. The difficulty is that disabling a service is a user setting, so, for example, if I reflash my ROM without the IQ files onto a phone with clean /data, I will again get the force close and an unusable ROM.
Click to expand...
Click to collapse
Manual Steps
In the meantime, here is how users can manually disable CarrierIQ. I take no credit for this method, it is posted in several places by several people, I'm just putting it here for convenience:
YOU MUST DO THIS IN ORDER (or at least the first few steps)
1. Download the "DisableService" app from the play store
2. In the DisableService app, go to System -> Android System and disable the "IQService" service
3. Use a root explorer to delete the folder /system/app/LADDM
4. Use a root explorer to delete /system/lib/libiq_client.so and /system/lib/libiq_service.so
5. (Optional) Uninstall DisableService
Remember, disabling the service is a user setting, so if you need to wipe /data for some reason, you will need to re-flash the ROM (which has the CarrierIQ files included) or else you will get a constant force close when your phone boots.
I'll give it a try, thanks
Flashing now. Will report.
I will be watching this ROM. Thanks for posting.
Exactly what does " if coming from a different ROM" mean? I'm on 4.4.2 10f Wulf (stock - rooted) ROM
JeffDC said:
I will be watching this ROM. Thanks for posting.
Exactly what does " if coming from a different ROM" mean? I'm on 4.4.2 10f Wulf (stock - rooted) ROM
Click to expand...
Click to collapse
Just clean flash to save yourself a hassle
2SHAYNEZ
Thanks for your work. I wish I had some skill in this realm. It'd be nice to pick and choose which apps you wanted removed. I prefer the stock ATT Visual Voicemail app over the one in the Play Store as its more reliable. I also use some of the Google Apps that are removed here as well. But great job in getting something debloated out there.
Sent from my LG-D850 using Tapatalk
Flashing lollipop Issues
Thanks for your work.... When flashing the 2 lollipop roms, 9 out of 10 times I get just a screen with icons, no wallpaper, no notification pull down no buttons at the bottom. I flash the modem the rom then SU and clear cache. I have only got the other ROM to flash successfully once. The same is going on with this ROM, is this happening to anyone else. I flashed it 5 times with the same results, would anyone know why this is happening, seems others dont have this issue. Thank you again for bringing us a debloated Lollipop rom.
shayneflashindaily said:
Just clean flash to save yourself a hassle
2SHAYNEZ
Click to expand...
Click to collapse
Here is what I understand for a clean flash:
"1. Boot into Recovery
2. Make a Nandroid backup
3. Wipe data/factory reset
4. Wipe cache partition
5. Wipe Dalvik Cache
6. Flash ROM
7. DO NOT REBOOT – STAY IN RECOVERY
8. Select backup and restore
9. Select advanced restore
10. Select the Nandroid backup you made above
11. Select Restore data
12. Select Yes – Restore data
13. WAIT!
14. REBOOT"
What I do not understand is step 8, which selects the backup made in step two... and then flashing the backup over the (new) ROM flash in step 6. Wouldn't that overwrite the new ROM you just flashed?
JeffDC said:
Here is what I understand for a clean flash:
"1. Boot into Recovery
2. Make a Nandroid backup
3. Wipe data/factory reset
4. Wipe cache partition
5. Wipe Dalvik Cache
6. Flash ROM
7. DO NOT REBOOT – STAY IN RECOVERY
8. Select backup and restore
9. Select advanced restore
10. Select the Nandroid backup you made above
11. Select Restore data
12. Select Yes – Restore data
13. WAIT!
14. REBOOT"
What I do not understand is step 8, which selects the backup made in step two... and then flashing the backup over the (new) ROM flash in step 6. Wouldn't that overwrite the new ROM you just flashed?
Click to expand...
Click to collapse
I always do a clean flash.. dont need to back up and restore and still get bad results.
louvass said:
I always do a clean flash.. dont need to back up and restore and still get bad results.
Click to expand...
Click to collapse
That's not encouraging.
louvass said:
Thanks for your work.... When flashing the 2 lollipop roms, 9 out of 10 times I get just a screen with icons, no wallpaper, no notification pull down no buttons at the bottom. I flash the modem the rom then SU and clear cache. I have only got the other ROM to flash successfully once. The same is going on with this ROM, is this happening to anyone else. I flashed it 5 times with the same results, would anyone know why this is happening, seems others dont have this issue. Thank you again for bringing us a debloated Lollipop rom.
Click to expand...
Click to collapse
I have not seen that issue, but in case you are not clearing data you may need to try clearing dalvik cache.
Also, (and this is just a shot in the dark) you could try formatting system before doing anything else just in case something strange is left behind there.
JeffDC said:
That's not encouraging.
Click to expand...
Click to collapse
You can try dirty flashing first without losing any of your data.
1. Back up your current Boot and System
2. Back up your current modem (if you're coming from the Kitkat modem), or just download a flashable KK modem already posted on XDA
3. Flash the modem and ROM in this post
4. Wipe cache and dalvik
5. See if it works
If it's not working, then you will need to restore your boot, system, and modem to go back to your original kitkat setup without losing data.
Otherwise, you'll have to backup with Titanium and do a clean flash (wipe data) as already mentioned. Using Titanium makes clean flashing not so bad
I do clear Wipe cache and dalvik I wipe everything and it boots back into a desktop and thats it no notification, the same thing happened with the first lollipop.. but after 10 flashes it finally took... so I thought Id try your de-bloated and the same thing is happening again, not sure why this is. I can jump back to kk after flashing the modem without issues. Thank you again for your work.
Pdj7969 said:
Thanks for your work. I wish I had some skill in this realm. It'd be nice to pick and choose which apps you wanted removed. I prefer the stock ATT Visual Voicemail app over the one in the Play Store as its more reliable. I also use some of the Google Apps that are removed here as well. But great job in getting something debloated out there.
Click to expand...
Click to collapse
I agree that I use most or all of these Google apps as well. However, they update so often anyway that I prefer to just have them as user apps (otherwise you end up with 2 copies - the old static version in the system apps folder, and the updated version in the user apps folder).
As for the visual voicemail, I have posted the ATT apps in a zip in the OP. Visual voicemail is in the VVM_ATT folder.
Thanks!
cmulk,
Would you please clarify post 5 and 9 questions?
JeffDC said:
cmulk,
Would you please clarify post 5 and 9 questions?
Click to expand...
Click to collapse
Sure thing! That's actually what I meant to do in post 13. I am not sure if you can flash over 10f without wiping data, but you could give it a try without losing anything (except time) if you look at post 13.
You should clear cache and dalvik mostly any time you are flashing, unless you are just flashing over another stock 20f ROM.
louvass said:
I do clear Wipe cache and dalvik I wipe everything and it boots back into a desktop and thats it no notification, the same thing happened with the first lollipop.. but after 10 flashes it finally took... so I thought Id try your de-bloated and the same thing is happening again, not sure why this is. I can jump back to kk after flashing the modem without issues. Thank you again for your work.
Click to expand...
Click to collapse
Have you tried formatting /system before doing anything else? I'm not sure that will make any difference, but just for process of elimination at least
cmulk said:
Have you tried formatting /system before doing anything else? I'm not sure that will make any difference, but just for process of elimination at least
Click to expand...
Click to collapse
Thanks I do clear everything but my external mem.
Ever since flashing this I'm getting "no sd card" messages every time I try to download anything ( I don't have an external sd card) but it's never been a problem before. I've restored a backup of my stock Tim and the problem followed me after full wipes.
Hello. This is my first ROM, based off of Cyanogenmod. A few Cyanogen features have been removed, and some non-CM features have been added. I am still testing it, but it seems to work fine for my t769.
WILL NOT WORK ON EXHILERATE
If any moderator wants me to remove DL links and close thread, notify me immediately.
This is my personal ROM, I build one after every CM nightly that comes out. I'm just uploading it here/my Dropbox for anyone who wants the same experience.
What exactly have I done?
-UberKernel v1 1.89GHz stock clock
-Removed CM's annoying Statistics and Bug Reports
-Removed stock CM apps
-Added ES File Explorer Free in place of CM File Manager
-Added Kernel Tuner
-Added stock 4.2 AOSP Launcher in place of Trebuchet
-Replaced CM's Torch with the one from CM10 (now has strobe, a useful feature that was removed in KitKat)
-Replaced Browser with AOSP 4.1.2
-Added Anthony Resario's Afterburner theme
-Replaced CM's boot screen with a generic Android boot screen
-Replaced DeskClock with the AOSP equivalent from 4.1.2
-Removed some live wallpapers
-Added Link2SD system app
How to install
1. Make sure you have a recovery installed. If not, I will be uploading an Odin-compatible package in the future. I recommend Philz Touch, although a different CM based recovery will work. Not tested on TWRP, use at your own risk.
2. Make a NANDROID backup.
3. Wipe Data
4. Wipe /sytem
5. Wipe /cahce
6. Factory reset
7. Install ROM
8. Wipe the Dalvik
9. Factory reset
10. Reboot, and keep an eye on it. Apps will prompt for SU on boot.
11. After it's done, reboot and install GApps if you want/need them.
DISCLAIMER:
I am not responsible if you brick, fry, or otherwise destroy your device as a result of flashing this ROM. I will not claim liability or replace your device. All features included in this ROM are properties of their respective owners, I merely assembled them into one place.
Changelog:
1/10/2016 - First beta/testing release
Planned features:
-Better DSP manager
-New default background
-possible shutdown sequence
-Flash Player support
-maybe 2.0GHz clock rate if it doesn't burn my device
-Tweak battery/4G
-Button light fix
-AOSP KitKat launcher
DOWNLOAD LINKS:
Newest Version:
Dropbox
Google Drive
Older versions:
Dropbox
Google Drive
XDA:DevDB Information
NoobROM 4.4.4, ROM for the Samsung Galaxy S Blaze 4G
Contributors
SiberianLeopard, SiberianLeopard
Source Code: http://download.cyanogenmod.org/?device=t769&type=
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.0.x
Based On: Cyanogenmod
Version Information
Status: Testing
Current Beta Version: 0.7
Beta Release Date: 2016-01-10
Created 2016-01-10
Last Updated 2016-01-10
New nightly coming! Stay tuned!
Development will also branch to the MyTouch 4G Slide and the Samsung Galaxy Epic 4G Slide.
Also mine
One more for good measure
Whats the battery life on this build??!
PowSniffer0110 said:
Whats the battery life on this build??!
Click to expand...
Click to collapse
I'm behind on a nightly, so not as good as normal. Right now, my Blaze hasn't had its 4 year old battery replaced, but when on standby with WiFi, min/max frequency set to 192/1890MHz and Governor set to Samsung with a ROW I/O scheduler, get about 3 days until it completely dies. The temperature sensor in my battery is shot, so I can't accurately report temperatures until I can find a decent OEM battery replacement. WiFi doesn't work properly, which is a bug in the kernel I have to fix in the updater script. My suggestion (until I fix various things with my ROM) is to download the latest CM nightly, flash UberKernel V1, and use Link2SD to uninstall all of the CM bloatware. If you're feeling adventurous and daring you can flash this and report the results.
Im on Validus by GZRoms 4.4.4 and the thread seams to be closed.... Cant ask questions. I have NO more internal space, with barely any apps installed. It partitioned my internal to have its on storage, built in SD, and my ACTUAL external SD. I cannot figure how to move apps to SD, it will not work, Ive tried the app2sd fixes, ive gone to apps and enabled 'App moving' and rebooted. No dice. Any help?
---------- Post added at 04:35 PM ---------- Previous post was at 04:33 PM ----------
My battery life is terrible most times on Validus 4.4.4 as well, even with the UBER 4.1 kernel. Thats why i asked you about the battery life on yours cause I need more. Have you used that 4.4.4? That one and yours seem to be the only ones and I need to be able to move apps2sd so I can actually have the apps I want. Literally have only 10 apps installed probably.
PowSniffer0110 said:
Im on Validus by GZRoms 4.4.4 and the thread seams to be closed.... Cant ask questions. I have NO more internal space, with barely any apps installed. It partitioned my internal to have its on storage, built in SD, and my ACTUAL external SD. I cannot figure how to move apps to SD, it will not work, Ive tried the app2sd fixes, ive gone to apps and enabled 'App moving' and rebooted. No dice. Any help?
---------- Post added at 04:35 PM ---------- Previous post was at 04:33 PM ----------
My battery life is terrible most times on Validus 4.4.4 as well, even with the UBER 4.1 kernel. Thats why i asked you about the battery life on yours cause I need more. Have you used that 4.4.4? That one and yours seem to be the only ones and I need to be able to move apps2sd so I can actually have the apps I want. Literally have only 10 apps installed probably.
Click to expand...
Click to collapse
Try Link2SD, and try my ROM. I just released a new nightly, the WiFi should work, if not I need to update it again.
Also, the Blaze only comes with 1.4GB of internal storage. I use PA GApps pico, and install anything else I actually use (like maps and Hangouts Dialer). GApps can easily take up massive amounts of space. Battery life has been fixed in my latest nightly. Please try out the ROM and see what it does. You have to do a FULL SYSTEM WIPE, except for EFS and RADIO partitions. I use PhilZ Touch. app2SD is frankly a terrible app in comparison to Link2SD, which is included in my ROM. If you use the SAMSUNG governor and ROW I/O scheduler and the battery life still sucks, get a new battery. If you also constantly have 4G, Wifi, and Bluetooth as well as NFC on, that will definitely drain your battery. Open Battery Stats in Settings and tell me what uses the most battery. Turn your screen brightness all the way down.
SiberianLeopard said:
Try Link2SD, and try my ROM. I just released a new nightly, the WiFi should work, if not I need to update it again.
Also, the Blaze only comes with 1.4GB of internal storage. I use PA GApps pico, and install anything else I actually use (like maps and Hangouts Dialer). GApps can easily take up massive amounts of space. Battery life has been fixed in my latest nightly. Please try out the ROM and see what it does. You have to do a FULL SYSTEM WIPE, except for EFS and RADIO partitions. I use PhilZ Touch. app2SD is frankly a terrible app in comparison to Link2SD, which is included in my ROM. If you use the SAMSUNG governor and ROW I/O scheduler and the battery life still sucks, get a new battery. If you also constantly have 4G, Wifi, and Bluetooth as well as NFC on, that will definitely drain your battery. Open Battery Stats in Settings and tell me what uses the most battery. Turn your screen brightness all the way down.
Click to expand...
Click to collapse
I'm downloading now and gonna test the link2sd and the battery life. Is this what you're running still?
PowSniffer0110 said:
I'm downloading now and gonna test the link2sd and the battery life. Is this what you're running still?
Click to expand...
Click to collapse
Development has been halted as of now because some [email protected] stole my Blaze. I'm saving for a new one but I kinda need the $70 because its part of my food budget.
Every time I try to install setup wizard fails and the phone doesn't fully boot correctly. Any suggestions??
PowSniffer0110 said:
Every time I try to install setup wizard fails and the phone doesn't fully boot correctly. Any suggestions??
Click to expand...
Click to collapse
If it's the Cyanogenmod setup wizard, I cannot help, as I said development has been halted until I can get another Blaze.
It if's the Google setup, boot the phone without flashing GApps a few times, finish the CM setup wizard, change a few settings, browse the web. After that then flash GApps and add an account through settings.
Another thing you can try is booting the phone in Safe Mode by holding the Vol+ and Vol- keys during boot.
I can't seem to be able to clear the defaults for Launcher so that I enable a new one. Am I missing something or is it just not possible?
shmargin said:
I can't seem to be able to clear the defaults for Launcher so that I enable a new one. Am I missing something or is it just not possible?
Click to expand...
Click to collapse
Go to Settings and then go to Home, there you can change what launcher you use.
SiberianLeopard said:
Go to Settings and then go to Home, there you can change what launcher you use.
Click to expand...
Click to collapse
Sorry, I should have said, I tried looking there too, I don't have a home option anywhere in settings, not under personalization, or anywhere else that I can find.
shmargin said:
Sorry, I should have said, I tried looking there too, I don't have a home option anywhere in settings, not under personalization, or anywhere else that I can find.
Click to expand...
Click to collapse
Use Link2SD to make the launcher you want a system app and then uninstall the one I included. I just bought another Blaze (mine was stolen) so I will resume development as soon as it arrives.
Also, how do you like the ROM? Does everything function properly?
By the way, the thanks button is right at the bottom of all of my posts.
SiberianLeopard said:
Use Link2SD to make the launcher you want a system app and then uninstall the one I included. I just bought another Blaze (mine was stolen) so I will resume development as soon as it arrives.
Also, how do you like the ROM? Does everything function properly?
By the way, the thanks button is right at the bottom of all of my posts.
Click to expand...
Click to collapse
Havent used it much, everytime I try and install, I get the error of Setupwizard force close and can never set up the ROM. When is your Blaze arriving? Any chances we will get any new updates or advances? I will try and reinstall today.
PowSniffer0110 said:
Havent used it much, everytime I try and install, I get the error of Setupwizard force close and can never set up the ROM. When is your Blaze arriving? Any chances we will get any new updates or advances? I will try and reinstall today.
Click to expand...
Click to collapse
I don't know when, probably next week and depending upon where CM source is at in development we might see NoobROM 5.1. I like KitKat better, and this is more of a personal project so it might stay KitKat with 5.1 APIs.
I might just scrap the CM wizard. It's pretty useless and only serves its purpose for new users.
SiberianLeopard said:
Development has been halted as of now because some [email protected] stole my Blaze. I'm saving for a new one but I kinda need the $70 because its part of my food budget.
Click to expand...
Click to collapse
Hey I got it up and running pretty well, couple problems.... battery charged all night over night and my battery will not move past 26%. I dont think this is ROM specific as I was having weird battery issues before. I don't know what to do tho? And I have quite a few Force Closes of apps, including Facebook, and ESPN. They force close regularly and are pretty much unusable. Valadis ROM seemed a lot more stable. I love the link2SD tho it works almost flawless! I can now have my apps back, even tho 1 of 2 internal storage still shows only 20+MB free internal? Why? I have all my apps installed externally. Anyway, if we flash a different kernel, or the one from Valadus ROM, will it break the link2SD feature?? Idk what it is, but that ROM is smoother and less Force Closes. I'll keep running this and look forward to an update!
PowSniffer0110 said:
Hey I got it up and running pretty well, couple problems.... battery charged all night over night and my battery will not move past 26%. I dont think this is ROM specific as I was having weird battery issues before. I don't know what to do tho? And I have quite a few Force Closes of apps, including Facebook, and ESPN. They force close regularly and are pretty much unusable. Valadis ROM seemed a lot more stable. I love the link2SD tho it works almost flawless! I can now have my apps back, even tho 1 of 2 internal storage still shows only 20+MB free internal? Why? I have all my apps installed externally. Anyway, if we flash a different kernel, or the one from Valadus ROM, will it break the link2SD feature?? Idk what it is, but that ROM is smoother and less Force Closes. I'll keep running this and look forward to an update!
Click to expand...
Click to collapse
Slow down, speed racer.
To answer your questions:
Q. What's wrong with my battery?
A. The Blaze is known for battery issues. Go into recovery, wipe everything (SD card, system, dalvik, factory reset, and data+cache), and then flash a new ROM. If your battery issues persist your battery is shot. Order a new one online.
Q. Is your kernel stable?
A. It's as stable as I could get it. If you're having trouble with FCs, reinstall PA GApps 4.4.4.
Q. Will flashing a new kernel break the ROM?
Short answer: Yes.
Long, complicated answer: No.
Q. I have no space left.
A. To free up internal storage, make sure your SD card is at least 16GB, I recommend 32 for this ROM. Install all the apps you want and then get rid of the Play Store. I use Blackmart, and will include it in the next update.