[Q] Split screen after installing CM 10.1 and 9 - Atrix 4G Q&A, Help & Troubleshooting

I have followed carefully (twice) the instal Tut's for both CM 9 and CM 10.1 however I have a screen problem and hang on start up.
When turning on the Atrix 4G (MB860) it seems to start Ok saying Unlocked and the Red M logo shows in the middle, as normal.
Then suddenly the screen seems to split into segments so there are 2 Unlocked texts at the top and an M in the middle at he very bottom, and two half M's either side. The phone hangs at that point.
Any ideas please ?
thanks

Krammig said:
I have followed carefully (twice) the instal Tut's for both CM 9 and CM 10.1 however I have a screen problem and hang on start up.
When turning on the Atrix 4G (MB860) it seems to start Ok saying Unlocked and the Red M logo shows in the middle, as normal.
Then suddenly the screen seems to split into segments so there are 2 Unlocked texts at the top and an M in the middle at he very bottom, and two half M's either side. The phone hangs at that point.
Any ideas please ?
thanks
Click to expand...
Click to collapse
that was normal, everyone have 2 unlocked & 2 1/2 logos. just wait, it took 3~5 minutes to boot.

thecjan said:
that was normal, everyone have 2 unlocked & 2 1/2 logos. just wait, it took 3~5 minutes to boot.
Click to expand...
Click to collapse
Thanks for that feedback. I tried again but it is still doing the same thing. I even went for a walk around the block to give it time

do you had full wipe?

Correct yes.
Via the Advanced section I did a Cache, Dalvik, System etc etc.
Then I installed the CM-9 same hanging situation.
Full wipe again via all items, then I tried 10.1 same hanging situation.
I have Unlocked the phone, and I did also Root the phone, but what if the Root didn't work, would it hang like this or do something different. I guess what I am asking is, can I check the root worked, or can I assume it worked if the install gets this far anyway ?
thanks

And i bet you're on a 3.1.10 kernel and if you turn off your device and plug it into charge, the battery meter doesn't flash. Am i right?
Sent from my MB886 using xda app-developers app

@ palmbeac05 thanks for the reply. All I can see is Recovery v4.0.0.2 Not sure where to check for the Kernel as I can't get in any further than the M logo screen, (apart from the Recovery section)
thanks

Krammig said:
@ palmbeac05 thanks for the reply. All I can see is Recovery v4.0.0.2 Not sure where to check for the Kernel as I can't get in any further than the M logo screen, (apart from the Recovery section)
thanks
Click to expand...
Click to collapse
so, you did not flashed K's kernel ?

Krammig said:
@ palmbeac05 thanks for the reply. All I can see is Recovery v4.0.0.2 Not sure where to check for the Kernel as I can't get in any further than the M logo screen, (apart from the Recovery section)
thanks
Click to expand...
Click to collapse
First off, you should really update that recovery. 4.x recoveries have been long since retired. We're now on 5.0.2.x up to 6.0.4.4
Second, what exact rom are you using (meaning state the file name of the rom package you are using)?
Sent from my MB886 using xda app-developers app

The ROM I have downloaded is cm-10.1-20131211-UNOFFICIAL-epinter-olympus.zip
And gapps-jb-20131207-olympus.zip
I tried gapps-kk-20140105.zip but it came up with an error during the install.
I hope I am using the correct versions as these are the ones I could find on the net ?
cheers

Krammig said:
The ROM I have downloaded is cm-10.1-20131211-UNOFFICIAL-epinter-olympus.zip
And gapps-jb-20131207-olympus.zip
I tried gapps-kk-20140105.zip but it came up with an error during the install.
I hope I am using the correct versions as these are the ones I could find on the net ?
cheers
Click to expand...
Click to collapse
CM10-10.2 is JB. CM11 is KK. Why you would flash KK gapps onto a JB build is extremely confusing.
That build is using the 3.1.10 kernel. To see that, go to options>about phone.
Boot logo and charging meter (as mentioned in my previous post) are related in terms of the kernel. Fix one, get a glitchy image on the screen for the other. Normal, and already discussed across all 3.1.10 kernel based roms.
Sent from my MB886 using xda app-developers app

palmbeach05 said:
CM10-10.2 is JB. CM11 is KK. Why you would flash KK gapps onto a JB build is extremely confusing.
That build is using the 3.1.10 kernel. To see that, go to options>about phone.
Boot logo and charging meter (as mentioned in my previous post) are related in terms of the kernel. Fix one, get a glitchy image on the screen for the other. Normal, and already discussed across all 3.1.10 kernel based roms.
Sent from my MB886 using xda app-developers app
Click to expand...
Click to collapse
..."Why you would flash KK gapps onto a JB build is extremely confusing."... If you're confused then imagine how I feel Just kidding.
I am absolutely new to all this so apologies for my lack of familiarity. I'm flying by the seat of my pants here. I'm trying to catch on as I read posts around the place.
So as I read your feedback I should ;
a) upgrade the Recovery to 5.x or 6.x (not sure where to find these)
b) locate CM10-10.2 JB or CM 11 KK and use the appropriate gapps (JB or KK)
glitchy image doesn't worry me at all, I am just keen to get a V4.x of Android installed so I can use this phone for some other security development that needs Android 4.x, otherwise I have to splash out $150 to buy a new phone which I'm not keen on doing.
It would be nice also to have the fingerprint working on the upgraded version. I saw an addon for Beanstalk somewhere and the developer said that installing that apk would activate the finger scanner. That said, I don't really have much of an idea what I am talking about, just what I have gleaned reading postings. I am 59 years old and with a bunch of old school IT like IBM mainframes etc behind me but am new to all this upgrading of mobiles
If you could steer me to any links that would be great.
thanks

Originally Posted by palmbeach05
CM10-10.2 is JB. CM11 is KK. Why you would flash KK gapps onto a JB build is extremely confusing.
That build is using the 3.1.10 kernel. To see that, go to options>about phone.
Boot logo and charging meter (as mentioned in my previous post) are related in terms of the kernel. Fix one, get a glitchy image on the screen for the other. Normal, and already discussed across all 3.1.10 kernel based roms.
Sent from my MB886 using xda app-developers app
Click to expand...
Click to collapse
..."Why you would flash KK gapps onto a JB build is extremely confusing."... If you're confused then imagine how I feel Just kidding.
I am absolutely new to all this so apologies for my lack of familiarity. I'm flying by the seat of my pants here. I'm trying to catch on as I read posts around the place.
So as I read your feedback I should ;
a) upgrade the Recovery to 5.x or 6.x (not sure where to find these)
b) locate CM10-10.2 JB or CM 11 KK and use the appropriate gapps (JB or KK)
glitchy image doesn't worry me at all, I am just keen to get a V4.x of Android installed so I can use this phone for some other security development that needs Android 4.x, otherwise I have to splash out $150 to buy a new phone which I'm not keen on doing.
It would be nice also to have the fingerprint working on the upgraded version. I saw an addon for Beanstalk somewhere and the developer said that installing that apk would activate the finger scanner. That said, I don't really have much of an idea what I am talking about, just what I have gleaned reading postings. I am 59 years old and with a bunch of old school IT like IBM mainframes etc behind me but am new to all this upgrading of mobiles
If you could steer me to any links that would be great.
thanks
Click to expand...
Click to collapse
Its all good, we've all been there (being noobs i mean)
The 5.x recovery can be found by going to the general section, the thread that has may 16th in its title, and clicking a link in post #1
The 6.x recovery can be found in the new CM10.2 thread (the one not done by epinter)
This is the only Android phone with fingerprint technology (to the best of my knowledge). Most stable on 2.3.x, however it does work on 4.0.4, although its more hit or miss at that point. I've got my Atrix 4G still and i'm running AtrICS v2.0 (Nov 2012 build) with the home button fix and the latest kernel released by krystian (10 Feb (haven't checked development at the time of this post)). Fingerprint for me does work.
Beanstalk is a JB ROM, i believe based off of the old kernel (2.x). I don't recall if that one had the fp working or not.
If the 4G can't do what you need, the A2 and AHD, both which succeeded the 4G, are both available for under 150 on amazon (my AHD was 134 after tax and shipping)
Sent from my MB886 using xda app-developers app

palmbeach05 said:
Its all good, we've all been there (being noobs i mean)
The 5.x recovery can be found by going to the general section, the thread that has may 16th in its title, and clicking a link in post #1
The 6.x recovery can be found in the new CM10.2 thread (the one not done by epinter)
This is the only Android phone with fingerprint technology (to the best of my knowledge). Most stable on 2.3.x, however it does work on 4.0.4, although its more hit or miss at that point. I've got my Atrix 4G still and i'm running AtrICS v2.0 (Nov 2012 build) with the home button fix and the latest kernel released by krystian (10 Feb (haven't checked development at the time of this post)). Fingerprint for me does work.
Beanstalk is a JB ROM, i believe based off of the old kernel (2.x). I don't recall if that one had the fp working or not.
If the 4G can't do what you need, the A2 and AHD, both which succeeded the 4G, are both available for under 150 on amazon (my AHD was 134 after tax and shipping)
Sent from my MB886 using xda app-developers app
Click to expand...
Click to collapse
Thanks for that info. A quick question - I see one of the Recovery versions says : CWM-Recovery 6 for Galaxy ACE GT-S5830. Does that mean it is specifically for that model and I need to find one that actually refers to the Atrix 4G MB860 ?
cheers

Good News ..... It's working.
It seems the issue might have been the Recovery app / version. After updating that to 5.x and reinstalling the OS it ran like a dream.
I started with AtrICS v2.0 as you indicated and that worked just fone although for some reason WiFi was not being detected.
I then reformatted etc and installed cm-10.1-20131211-UNOFFICIAL-epinter-olympus and it's all looking good, including fingerprint.
Thanks again for your help, much appreciated.
cheers

Krammig said:
Good News ..... It's working.
It seems the issue might have been the Recovery app / version. After updating that to 5.x and reinstalling the OS it ran like a dream.
I started with AtrICS v2.0 as you indicated and that worked just fone although for some reason WiFi was not being detected.
I then reformatted etc and installed cm-10.1-20131211-UNOFFICIAL-epinter-olympus and it's all looking good, including fingerprint.
Thanks again for your help, much appreciated.
cheers
Click to expand...
Click to collapse
Yes you did need to flash a CWM designed specifically for the A4G. AtrICS can be tricky, sometimes, but as long as you installed the main ROM, then the Vendor zip, you should get wifi. If you want to use the 3.1.10 kernel, flash the home fix zip thats in that thread, then upgrade the kernel as needed (highly recommended if you chose this option).
Glad to see you were able to upgrade, and no problem.
Sent from my MB886 using xda app-developers app

Related

Stable CM7.1 released ..!!

Awesome news guys stable version for SGS2 is released .!!
here's the link http://download.cyanogenmod.com/?type=stable&device=galaxys2
EDIT- Sorry posted on wrong section plz move it to general section
Awesome, just flashed it. Figures, I switched to MIUI yesterday from CM build #75 because it was incredibly unstable. Just about the time I get it set up, they release a stable version of CM. But hey I'm not complaining. Can't wait to give it a full day tomorrow. It's going to be a hard choice between the two though, MIUI is pretty clean.
reading on cm forum, seems they fixed the bt bug and its fully functionally, thats a very good news, since this prolly mean we are having also miui with bt working soon
FC heaps on the camera lol...but still great to finally have a stable on CM! =D reminds me of the good old HTC days...
Anyone know if TV out is working? This is probably the only thing stopping me from flashing.
read this today and will be waiting for any user feedbacks because this is going to be my very first CM install.
Going to have to say goodbye on my litening rom..
btw the new build also supports european gs2s right?
droidluck said:
read this today and will be waiting for any user feedbacks because this is going to be my very first CM install.
Going to have to say goodbye on my litening rom..
btw the new build also supports european gs2s right?
Click to expand...
Click to collapse
there are two sections on cm download page: standard and at&t'. European=standard
Sent from my GT-I9100 using Tapatalk
rembrandtlnx said:
there are two sections on cm download page: standard and at&t'. European=standard
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
Thank you for the.reply!
Is there really supposed to be home screen wake up lag on CM?? I thought this was only an issue with Samsung based roms??
dhorn92 said:
Awesome, just flashed it. Figures, I switched to MIUI yesterday from CM build #75 because it was incredibly unstable. Just about the time I get it set up, they release a stable version of CM. But hey I'm not complaining. Can't wait to give it a full day tomorrow. It's going to be a hard choice between the two though, MIUI is pretty clean.
Click to expand...
Click to collapse
Bull****. Been using it since nightly #20 or so, and it has been stable since then.
I want to try this out, although I don't really want to get totally rid of my stock ROM just yet. Was there a way to be able to run this from the SD card or some form of dual boot? I think I read about it somewhere.
Any info on aos bug, general battery life and speed?
Sent from my GT-I9100 using XDA App
ProtoKun7 said:
I want to try this out, although I don't really want to get totally rid of my stock ROM just yet. Was there a way to be able to run this from the SD card or some form of dual boot? I think I read about it somewhere.
Click to expand...
Click to collapse
If you already have root + clockwork recovery do a nandroid backup then install CM7.
If you don't like it you can always restore back
But no SD version that i know of sorry.
---------- Post added at 06:19 PM ---------- Previous post was at 06:16 PM ----------
borchgrevink said:
Any info on aos bug, general battery life and speed?
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
It performs very well imho, my only issue is the camera i just don't feel its up to Samsung stock standards and i use it quite a lot.
mynamesteve said:
If you already have root + clockwork recovery do a nandroid backup then install CM7.
If you don't like it you can always restore back
But no SD version that i know of sorry.
Click to expand...
Click to collapse
Pretty much standard procedure then.
(I wouldn't mind a way to dualboot though; that would be good)
EDIT: Although I seem to keep getting
Code:
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
when I try to back up. I'll try another version if I find it.
Hey, that's indeed a great news !
Unfortunately, when I try to follow the official wiki, I got stuck when Heimdall is supposed to detect my phone in download mode, it says "Failed to detect compatible download-mode device." whereas my phone is in dl mode (the screen says it : "waiting for download"...
It got stuck when I try to flash the kernel given in the wiki. And honestly, I think I already flashed a kernel (because I'm root and there is the yellow /!\ on boot) but can't remember which one...
Help... ?
Not bull****. I started using it on build 75 and it crashed about 10 times a day. I thought it was due to superpower at first, but after completely uninstalling it I still had the issue. Also, the battery life was unusably bad. Maybe you had a better experience. That's great, but I experienced what I did. It was a nightly so I accepted it and tried something else. They released a stable version and now I'm back on it. Its working much better now. For the record I'm a huge fan of cyanogenmod, I have it running on my Matrix 4G as well.
Sent from my GT-I9100 using xda premium
So do we have a "Things that still don't work properly/at all" list? The OP in the main CM7 thread hasn't been updated (yet?).
Have we got full stable BT HSP/HFP/A2DP/AVRCP support?
MHL?
Stable WiFi?
An option to do a loopback mount of the /mnt/emmc mountpoint back to what used to be /mnt/sdcard/external_sd/ ? (Yeah, can always do it in a init.rc file)
Have they fixed the horrendous battery drain? (I last tried a couple of 50-something nightlies)
---------- Post added at 10:31 AM ---------- Previous post was at 10:10 AM ----------
Swali said:
Unfortunately, when I try to follow the official wiki, I got stuck when Heimdall is supposed to detect my phone in download mode, it says "Failed to detect compatible download-mode device." whereas my phone is in dl mode (the screen says it : "waiting for download"...
It got stuck when I try to flash the kernel given in the wiki. And honestly, I think I already flashed a kernel (because I'm root and there is the yellow /!\ on boot) but can't remember which one...
Click to expand...
Click to collapse
Try reinstalling the USB drivers that come with Heimdall.
i am not 100% sure if there are more device specific optimisations than in an normal nightly. Afaik the version changes of cyanogenmod are just for the general sourcecode, which is used to build roms for all supported devices.
So that means no tv-out, no bluetooth and no mhl for us. But thats just a matter of time. sooner or later bluetooth and FM will work; not so sure about mhl.
Sent from my GT-I9100 using XDA App
As to the question about battery life, it is significantly better. Run super power or juice defender and its especially decent. I keep a spare battery in reach anyways, but I usually don't have to put it in until 10 or 11pm if I keep tthe phone unplugged all day.
I don't use a2dp so I haven't tested it, and I prefer iheartradio so I haven't messed with the radio yet either. I keep popping back and forth between my MIUI and cywnogenmod backups, both are awesome in their own ways. Its hard to decide a permanent rom. But I'm leaning toward CM7.
Sent from my GT-I9100 using xda premium
I'm happy on CM7 so far.. only thing I miss is the ability to disable completely the softkey backlights... any tips or suggestions?

[Q] Requesting assistance with CWM recovery

Hey guys and gals (although I suspect mostly guys =|)
I have become a noob. A few years ago I was fully into this with flashing and modding scene with the Huawei ideos 8150 phones, done as a service on a local auction website, mostly as many found they were too slow.
After doing this for about 6 months I dropped it as I went into study, my pc has been formatted numerous times since and I can't for the life of me remember what the Android software is called that directly interacts with the linux subsystem on the phone/device.
Why? I now have a T-mobile Galaxy S Vibrant (SGH-T959) and i've been trying to get CyanogenMod 10.0 onto it.
I have rooted the phone thru SuperOneClick via pc (as Z4root would crash).
I have installed OCLF v2
Android system is curently Froyo 2.2 (krnl 2.6.32.9)
I am able to successfully flash the clockwork mod recovery but please see attachment View attachment 1636948
The phone automatically re-installs the default recovery apk's when the recovery menu is launched. Why?
I have taken a look at alternatives like heimdall and odin to flash the ROM but i'm not at all confident because I've never had a ROM fail to flash, so I'm in-experienced at recovery
I'd really appreciate your help on this - I've done research into why this might be happening, but those cases seemed to be unique down to other factors..
I am not familiar with OCLF v2???
Here is a guide with files etc. The issue you are having is because of froyo more specifically android recovery 3(e). The easiest thing to do IMO is Odin back to stock, that takes care of recovery issue, root again then use the update.zip from this guide.
http://forum.xda-developers.com/showthread.php?p=9375927
Sent from my GT-P5113 using xda premium
samsgun357 said:
I am not familiar with OCLF v2???
Here is a guide with files etc. The issue you are having is because of froyo more specifically android recovery 3(e). The easiest thing to do IMO is Odin back to stock, that takes care of recovery issue, root again then use the update.zip from this guide.
http://forum.xda-developers.com/showthread.php?p=9375927
Sent from my GT-P5113 using xda premium
Click to expand...
Click to collapse
Hey
OneClickLagFix v2 makes an external ext3 directory for swapfiles and prog access or somehting, it's pretty amazing and it sped up I/O via Quadrant by 1600 points making ythe phone so fast it can't complete the boot animation because it's already loaded
Thanks for that guide too, Imma work thru that one shortly
1) You mean the kernel?
2) Recovery doesn't use apks. It's a binary program that runs without the OS. Apks are used within the Android OS, for example being either apps or components like the status bar.
Visit the CyanogenMod wiki for a full update guide for the Vibrant (there's a link in the nightly thread under "from Samsung stock")
Sent from my Galaxy Nexus using xda premium
FaultException said:
1) You mean the kernel?
2) Recovery doesn't use apks. It's a binary program that runs without the OS. Apks are used within the Android OS, for example being either apps or components like the status bar.
Visit the CyanogenMod wiki for a full update guide for the Vibrant (there's a link in the nightly thread under "from Samsung stock")
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Oh wow, a reply form the mod-god himself . I am honored!
I ended up following a poorly written guide to mod my Vibrant from Android 2.3 to JFD using ODIN. Flashed update.zip which seemed to give me a temporary CWM recovery, next reboot it was back on stock. Tried again and the CWM recovery stuck.
Phone is currently running CyangogenMod 10.1 with gapps-jb-20121212-signed as is running amazingly well.
I realize that I've flashed a nightly build of 10.1 and using it as a daily driver was not recommended, but so far it's flawless with the expcetion that I haven't yet tested GPS and I haven't found how to get Google's own navigation software back. I'm a computer tech who often visits customers homes, so fairly important that it works
.produkt-R said:
Oh wow, a reply form the mod-god himself . I am honored!
I ended up following a poorly written guide to mod my Vibrant from Android 2.3 to JFD using ODIN. Flashed update.zip which seemed to give me a temporary CWM recovery, next reboot it was back on stock. Tried again and the CWM recovery stuck.
Phone is currently running CyangogenMod 10.1 with gapps-jb-20121212-signed as is running amazingly well.
I realize that I've flashed a nightly build of 10.1 and using it as a daily driver was not recommended, but so far it's flawless with the expcetion that I haven't yet tested GPS and I haven't found how to get Google's own navigation software back. I'm a computer tech who often visits customers homes, so fairly important that it works
Click to expand...
Click to collapse
Most of the CM work comes from the Galaxy S-line work done by pawitp, and the work done by others in the CyanogenMod team and Gerrit.
You can get Maps from the Play Store.
FaultException said:
Most of the CM work comes from the Galaxy S-line work done by pawitp, and the work done by others in the CyanogenMod team and Gerrit.
You can get Maps from the Play Store.
Click to expand...
Click to collapse
Yea thanks man, I've already sorted that. Only problem that remains is that I cannot get a gpslock after sitting in the sun for 45minutes (omg sun!)
See this thread by moped for GPS help
http://forum.xda-developers.com/showthread.php?p=36456644
Sent from my GT-P5113 using xda premium
samsgun357 said:
See this thread by moped for GPS help
http://forum.xda-developers.com/showthread.php?p=36456644
Sent from my GT-P5113 using xda premium
Click to expand...
Click to collapse
Is there anything this forum doesn't have now ??
Few years ago when I was a frequent, there certainly wasn't this much info in one place - Will let you know how I get on - Althought I am in New Zealand so i'm wondering if this will even work.

Preparing for Android 4.3

Just wanted to know how everyone is preparing for android 4.3 which I'm sure is to be announced and available later on today.
Custom ROM users: are you flashing back to stock?
As a rooted and custom ROM user, I'm torn between flashing back to stock for update or just waiting a few weeks until its baked into some awesome ROMs. Thoughts?
Sent from my Nexus 10 using Tapatalk HD
HarmonyFlame said:
Just wanted to know how everyone is preparing for android 4.3 which I'm sure is to be announced and available later on today.
Custom ROM users: are you flashing back to stock?
As a rooted and custom ROM user, I'm torn between flashing back to stock for update or just waiting a few weeks until its baked into some awesome ROMs. Thoughts?
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
Not doing anything. Doesn't really bother me. Once it's released, if it is found to have some must-have improvements, then i'll most likely wait for AOKP to incorporate it, but for now, my tablet works just fine and i can't see a reason to consider changing things up.
hughlle said:
Not doing anything. Doesn't really bother me. Once it's released, if it is found to have some must-have improvements, then i'll most likely wait for AOKP to incorporate it, but for now, my tablet works just fine and i can't see a reason to consider changing things up.
Click to expand...
Click to collapse
That's fair. For me though, honestly I may end up flashing back just to resolve the Mali driver issue. On my n10 it is a huge problem and I may not be able to wait any longer to resolve it, so hopefully 4.3 includes the drivers. We'll see.
Sent from my Nexus 4 using Tapatalk 4 Beta
I also plan to just wait until it makes its way to CM. I'm planning on building my ROMs from source from this point on (adding PDroid and some other local changes) and it shouldn't take too long until CM is updated. I picked CM mainly because their build instructions are the best I've been able to find.
Just announced that starting today, Android 4.3 will be pushed to the Nexus 4, Nexus 7, Galaxy Nexus and Nexus 10.
Hi guys,
Do you recon 4.3 will need wipe or non - wipe? hope its non-wipe
HarmonyFlame said:
Just wanted to know how everyone is preparing for android 4.3 which I'm sure is to be announced and available later on today.
Custom ROM users: are you flashing back to stock?
As a rooted and custom ROM user, I'm torn between flashing back to stock for update or just waiting a few weeks until its baked into some awesome ROMs. Thoughts?
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
Can we receive update if on stock, but rooted? Do we have to have stock recovery? Never had a Nexus device so I'm just wondering...
Its been so long since I updated mine I can't even remember what to do. I think the Nexus 10 toolkit will do it for me since I'm rooted.
dfox123 said:
Can we receive update if on stock, but rooted? Do we have to have stock recovery? Never had a Nexus device so I'm just wondering...
Click to expand...
Click to collapse
While I'm not positive, I'm fairly certain that you update even without stock recovery, but you will use root unless you use an app called "OTA Root keeper"
It's already available for download at https://developers.google.com/android/nexus/images#mantarayjwr66v
Flash with fastboot.
CazeW said:
It's already available for download at https://developers.google.com/android/nexus/images#mantarayjwr66v
Flash with fastboot.
Click to expand...
Click to collapse
Keep in mind if you do this, your device will be wiped. This is NOT an OTA.
mustbepbs said:
Keep in mind if you do this, your device will be wiped. This is NOT an OTA.
Click to expand...
Click to collapse
I flashed manually and via the script and get stuck at the X logo on boot.
I would hold off on flashing for now.
xetrev said:
I flashed manually and via the script and get stuck at the X logo on boot.
I would hold off on flashing for now.
Click to expand...
Click to collapse
Flashed mine, wiped all data, but works fine (I had restored to stock rom and recovery beforehand).
Notable changes include slightly snappier response, miracast support, and apparently finger flinger is fixed (read that in a other thread, i'm not rooted so can't check)
Chluz said:
Flashed mine, wiped all data, but works fine (I had restored to stock rom and recovery beforehand).
Notable changes include slightly snappier response, miracast support, and apparently finger flinger is fixed (read that in a other thread, i'm not rooted so can't check)
Click to expand...
Click to collapse
Yup, we can't confirm that in the code yet but it looks good. The end to random reboots might be here
Sent from my Nexus 10 using xda app-developers app
Chluz said:
...and apparently finger flinger is fixed (read that in a other thread, i'm not rooted so can't check)
Click to expand...
Click to collapse
Made me laugh. I'm sure you meant surface flinger.
From my S-Off BadSeed DNA
trickster2369 said:
Made me laugh. I'm sure you meant surface flinger.
From my S-Off BadSeed DNA
Click to expand...
Click to collapse
Yep ?
Sent from my Nexus 10 using Tapatalk HD
Did anyone get ota yet? I don't want to flash factory image so I don't lose data as I just lost all my data a week ago
Sent from my Xperia Play (r800x)
xetrev said:
I flashed manually and via the script and get stuck at the X logo on boot.
I would hold off on flashing for now.
Click to expand...
Click to collapse
I had that problem when I flashed the old OS after unlocking bootloader when I got the N10. A subsequent data wipe fixed it:
1. Reboot into Fast Boot
2. Select Recovery using volume rocker. Hit power to select. You'll get the android mascot with the red exclamation point.
4. Press Power and Volume Up at the same time (this is the side of the volume rocker that is away from the power button for those new to the device).
5. Choose to wipe all data. Confirm the selection.
6. Reboot.
I have my rablet rooted and bootloader unkocked. If i update via OTA i will lose root i suppose? I heard that the bootloader changes too. It will be relocked?

[Q] android process a core has stopped- pac man nightlies

I have ported a few different custom rom's to my Verizon s4. I had not had any issues thus far. I decided to try an original android development rom and decided to go with the pac man rom. It seemed, and still does seem like a no brainer being it has the best from roms by top developers. I had been using hyperdrive for the past month or so, and I originally tried to move right to the latest nightlie ( 8/16). I use twrp and as soon as I booted the keyboard would not work for me to set up my phone. I went back into the pac thread and ended up flashing the 7/30 milestone release. It works great, however I would really like to run a 4.3 rom, and I would love for it to be pac man rom. I have tried updating using the exact directions to a t and once my phone updates every time I try and do anything my phone says android process a core has stopped. Also , whenever I click on my phone , contacts, or any other basic phone function it says app not installed. I am a newb, I have only been flashing for about four months. I have a galaxy nexus as well that I play with. I have not ran into an issue I have not been able to resolve using discussions or questions already posted on xda. I am coming up with nothing this time however. This is my first post and my first request for assistance. I hope my post is not to long. I would greatly appreciate any help offered.
Flashed the right gapps?
Sent from my SCH-I545 using Tapatalk 4
yep.....
dadsterflip said:
Flashed the right gapps?
Sent from my SCH-I545 using Tapatalk 4
Click to expand...
Click to collapse
I think I did, there was a link directly under the link for the ROM in the download box of the PAC man ROM page on this site. Those are the gapps I flashed. Goo manager keeps saying there is a gapps update for me though.

[Q] 4.3.x AOSP No Baseband

I've been running AOSP 4.2 on my S4 for quite a while with no issues. Upon trying to upgrade to 4.3 though, boots take upwards of 5 minutes and the baseband isn't recognized (it literally shows "Baseband Version: Unknown"). I then tried to revert to one of the various 4.2 ROMs still out there, and am encountering quite a bit of general instability (lots of FCs), however, the baseband works fine. Any idea what is going on?
I should add that though I am using the ME7 modem, everything else is MDK and that these symptoms are pervasive through several different ROMs.
Update:
When trying to switch to RUIM/SIM in the Radio Settings, I get the following logcat:
Code:
/CdmaSubscriptionListPreference( 1762): Setting Cdma subscription source failed
I/Use2GOnlyCheckBoxPreference( 1762): get preferred network type, exception=com.android.internal.telephony.CommandException: RADIO_NOT_AVAILABLE
have you gone into network settings and verified that your subscription is set to RUIM/SIM instead of NV?
Did you compile the AOSP yourself? What build are you using? Project Elite's baseband and network all work out of the box no problems. I'm not sure if they posted it yet though.
Dubbsy said:
have you gone into network settings and verified that your subscription is set to RUIM/SIM instead of NV?
Click to expand...
Click to collapse
Yes; Whenever I do that I get the logcat I mentioned above and the setting doesn't stick (ie it immediately changes back to NV).
Edit:
When I retried, I got:
Code:
E/CdmaSubscriptionListPreference( 1618): Setting Cdma subscription source failed
Dubbsy said:
Did you compile the AOSP yourself? What build are you using? Project Elite's baseband and network all work out of the box no problems. I'm not sure if they posted it yet though.
Click to expand...
Click to collapse
No; this is with several 4.3 based ROMs including CM and Pacman.
Edit 2:
I'm downloading the Darkslide ROM to try to get that baseband installed and will keep this thread up to date with the result.
murphycr said:
Yes; Whenever I do that I get the logcat I mentioned above and the setting doesn't stick (ie it immediately changes back to NV).
Edit:
When I retried, I got:
Code:
E/CdmaSubscriptionListPreference( 1618): Setting Cdma subscription source failed
No; this is with several 4.3 based ROMs including CM and Pacman.
Edit 2:
I'm downloading the Darkslide ROM to try to get that baseband installed and will keep this thread up to date with the result.
Click to expand...
Click to collapse
Oh you aren't running pure aosp. Gotcha.
I was able to hold subscription on PAC, Slim, and CM10.2
Did you edit anything prior to install? Was your phone's data working just before switching to 4.3?
Dubbsy said:
Oh you aren't running pure aosp. Gotcha.
I was able to hold subscription on PAC, Slim, and CM10.2
Did you edit anything prior to install? Was your phone's data working just before switching to 4.3?
Click to expand...
Click to collapse
Yes. It also works if I switch back to 4.2, but then other things break. Anyway, I'm about to flash the baseband you referred to, so I'll see where that gets me.
Thanks!
murphycr said:
Yes. It also works if I switch back to 4.2, but then other things break. Anyway, I'm about to flash the baseband you referred to, so I'll see where that gets me.
Thanks!
Click to expand...
Click to collapse
the baseband used in all 4.3 builds I've used was MDK.
Me7 baseband is not as good as some people like to claim. It is buggy, and in my opinion it was rushed to release because Verizon wanted to quick kick everyone in the nuts. I tried me7 a few times and everytime I had worse spottier service.
The project elite aosp I was talking about is actually full aosp. And I haven't seen a post for it yet.
Another thing I've noticed in general... What recovery are you using? I don't trust CWM(any variation) at all anymore. I've seen too many installs act up and just not work right at all with CWM and after trying it on twrp 2.5.0.2 the same exact installer worked fine. :silly: I don't know why, but regardless the layout of CWM is piss poor anyway. If you are using CWM, click the link in my sig to go to my GE build. In the second post I have flashable recoveries posted. You can try one out just to see and if you get the same results just flash back to your desired/current recovery:good:
I was having the same problem with my own cm10.2 builds. I blew out my device and vendor repos several times and finally decided that there had to be something in frameworks that doesn't like the dev edition radios. The nightlies wouldn't even work. I ultimately wound up using the official cwm (non-loki only) and was finally able to change from nv to ruim/sim.
Sent from my SCH-I545 Dev Edition using xda app-developers app
So you used the non-loki'd CWM to do what fixed it? (I presume simply having it installed didn't fix it automatically)
On the dev edition, the general consensus in the beginning was that philz touch(cwm based) was the recovery to use probably because he offered a non-loki version. We don't need loki fortunately because of our unlocked bootloader. I later found out that official cwm was also not lokified. If you have the retail version, unfortunately you are stuck with the loki recovery. I was just suggesting that you might try a different cwm since they are not all created equal.
Edit: I guess what I was really trying to say is just try another recovery. Not necessarily one over the other (cwm vs. twrp). It's not the non-loki part that will make the difference. Hopefully you'll find one that works for you. But who would have known that would cause it.
Sent from my SCH-I545 using xda app-developers app
OLD&SLOW said:
On the dev edition, the general consensus in the beginning was that philz touch(cwm based) was the recovery to use probably because he offered a non-loki version. We don't need loki fortunately because of our unlocked bootloader. I later found out that official cwm was also not lokified. If you have the retail version, unfortunately you are stuck with the loki recovery. I was just suggesting that you might try a different cwm since they are not all created equal.
Edit: I guess what I was really trying to say is just try another recovery. Not necessarily one over the other (cwm vs. twrp). It's not the non-loki part that will make the difference. Hopefully you'll find one that works for you. But who would have known that would cause it.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
I've tried both TWRP and PhilZ. Neither seemed to do it. At this point I'm just going to do a full ODIN.
Thanks for all the help though!
No problem, I just hope you figure it out. There are too many people using aosp 4.3 roms with no problems for this to be impossible. :thumbup:
Sent from my SCH-I545 using xda app-developers app
murphycr said:
I've tried both TWRP and PhilZ. Neither seemed to do it. At this point I'm just going to do a full ODIN.
Thanks for all the help though!
Click to expand...
Click to collapse
I have an already Loki patched cwm touch posted in my list if you wanted to try it too.
I've found Odin helps clean all the garbage out though. So either way
Good luck!
sent from my Verizon Galaxy sIV

Categories

Resources