Related
Flashing a 3g us xoom and when installing i get a "random offset 0x2d" then is says zip installed or whatever it says at the end of it. When I boot up it goes to a blank screen with a bunch of triangles going around in a circle down in the lower right of the screen. Any ideas?
malkamus said:
Flashing a 3g us xoom and when installing i get a "random offset 0x2d" then is says zip installed or whatever it says at the end of it. When I boot up it goes to a blank screen with a bunch of triangles going around in a circle down in the lower right of the screen. Any ideas?
Click to expand...
Click to collapse
Nothing to worry about those triangles are the boot animation lol...
The offset is nothing and has been explained before... Dont stress and now let your xoom boot lol
Sent from my Galaxy Nexus using Tapatalk 2 Beta-5
Ok thanks I did a quick search for that error but got nothing. it just loaded so fast after that then after loading gapps it just sat there and those arrows went round around forever.
malkamus said:
Ok thanks I did a quick search for that error but got nothing. it just loaded so fast after that then after loading gapps it just sat there and those arrows went round around forever.
Click to expand...
Click to collapse
First boot usually takes a while... Did u follow steps wiping cache n dalvik n did u fix permissions to help ensure you don't get in a bootloop
Sent from my Galaxy Nexus using Tapatalk 2 Beta-5
I did not fix permissions did the rest though and it did finally boot and is running ics. I guess the permissions are on? Thanks for the help
malkamus said:
Flashing a 3g us xoom and when installing i get a "random offset 0x2d" then is says zip installed or whatever it says at the end of it. When I boot up it goes to a blank screen with a bunch of triangles going around in a circle down in the lower right of the screen. Any ideas?
Click to expand...
Click to collapse
LOL! Yeah it's the boot animation. It's all good.
malkamus said:
I did not fix permissions did the rest though and it did finally boot and is running ics. I guess the permissions are on? Thanks for the help
Click to expand...
Click to collapse
Sure permissions are 'on', however... FIXING permissions fixes incorrect permissions you should do this as sometimes apps or system apps whatever can have force closes or problems due to the permissions not being correct... It takes an extra couple minutes if required but can make a difference
Sent from my Galaxy Nexus using Tapatalk 2 Beta-5
Is this something I can still do after ics is up and running? Or do I need to reflash it again after?
Yes go into recovery, under advanced you'll see to option to fix permissions.
Do so and be patient it may take a while. No need to reflash. Reboot and enjoy. Has helped me at times to get things running smoother!
thanks all of ya. Up and running ICS. Have done several phones but the xoom worried me a bit, but excellent rom and fantastic assistance from you all.
hellow,
first of all sorry if this has bin asked before i tried searching came up with no founds .
entering the thread name gave me no results aswell.
anyways ,
when i changed my theme on my X10 running CM7 it seemed to reset my icons and downloaded apps meaning i was back on to factory settings.
my question is is this normal ? kinda scared to change my themes after that!
or am i going about it all wrong and should i pick ADW themes instead of the theme chooser itself ?
thnx in advance.
it's not.
Changing theme should not touch your app/setting, ony icons/colors/fonts. :|
Probably something goes wrong with that change.
Aha,
well its bin a while since i picked my theme but i seem to recall it going straight to rebooting after loading x amount of time.
after reboot sending me into the settings guide you get when doing a full wipe.
BUT as you said that it shouldn't do that i tried again .
and the result was changing evrything as it should exept offcourse the icons i selected manually so it worked cheers!!
Have fun, and format /system before flashing!
added camera app, fm radio, media_codecs.xml (fixes sound probs)
http://www.mediafire.com/file/rm3t3813wwxaewd/cm-10-20120826-UNOFFICIAL-sholes.zip
bootloops? ts problems?
did you format system?
try safe kernel (stockish ram/sgx/dsp timings)
http://www.mediafire.com/file/0kci9mvja4b9ssn/jb_safe_kernel.zip
or safer kernel (doesn't reprogram core clock at boot, exact stock timings)
http://www.mediafire.com/?do6yfe1c79v7xj7
or safest (same as safer with cpu max at 800mhz instead of 1000)
http://www.mediafire.com/file/926lgj8qu2a8l8s/jb_safest_kernel.zip
still no go?
try ics build here:
http://forum.xda-developers.com/showpost.php?p=29471613&postcount=1855
with 160mhz kernel
then wipe everything and try this build again, or enjoy ics :]
if you get stuck without touchscreen don't sbf back to stock
try safe kernel and ics build, if you still have troubles pm me
Gapps: http://www.mediafire.com/file/6gm3mm7iyi775n6/gapps-jb-20120726-minimal-datainstall.zip
broken: lots? please test
greets and credit: nadlabak, quarx2k, tpruvot, mbm, everybody at #motomagic, et cetera
kfazz said:
Have fun!
Build: http://www.mediafire.com/file/elk7kvw2hyu28ij/cm-10-20120824-UNOFFICIAL-sholes.zip
Gapps: none yet
broken: lots? please test
greets and credit: nadlabak, quarx2k, tpruvot, mbm, everybody at #motomagic, et cetera
Click to expand...
Click to collapse
Downloading
since this is CM10 based would regular cm10 gapps work? Thanks
Edit: It doesn't seem to boot. It gets stuck on the android screen.
about 3m freee in system, so regular jb gapps wont work unless modified to use /data. ics gapps work.
if you have bootloop:
adb shelll and
rm /system/lib/hw/gps.sholes.so
or just delete it from the zip before flashing
kfazz said:
about 3m freee in system, so regular jb gapps wont work unless modified to use /data. ics gapps work.
if you have bootloop:
adb shelll and
rm /system/lib/hw/gps.sholes.so
or just delete it from the zip before flashing
Click to expand...
Click to collapse
Installd ics gapps.
So, got rid of bootloop using adb to remove gps. Boots up fine after that.
CPU overclock settings can not be changed in settings. Works fine in setcpu.
No camera app included.
EDIT: Phone was plugged into usb port on computer entire time, and I noticed that the battery was not charging. Flashed back to my daily driver for now and phone is charging again. Not sure if this is common to anyone else or just a bug for me.
this is filthy! so fast. i used http://forum.xda-developers.com/showpost.php?p=30325746&postcount=1977 nightwing's .zip to get market over adb. wireless also works. mp3's through music load up like it's going to play, but then flashes a screen where song progress is complete and goes back to the artist list, but media server found all my songs. m4a's say file not supported. bluetooth paired with my keyboard and worked. voice dialer worked to open apps and i got a few beeps out of it at the end of commands so some sound is working. mine's not activated though so i can't test radios. donations on the way. thanks for all the hard work.
peeyourownpants said:
this is filthy! so fast. i used http://forum.xda-developers.com/showpost.php?p=30325746&postcount=1977 nightwing's .zip to get market over adb. wireless also works. mp3's through music load up like it's going to play, but then flashes a screen where song progress is complete and goes back to the artist list, but media server found all my songs. m4a's say file not supported. bluetooth paired with my keyboard and worked. voice dialer worked to open apps and i got a few beeps out of it at the end of commands so some sound is working. mine's not activated though so i can't test radios. donations on the way. thanks for all the hard work.
Click to expand...
Click to collapse
I can confirm 3G and calling works.
also, is there a way to get google now on this?
db2u said:
Installd ics gapps.
So, got rid of bootloop using adb to remove gps. Boots up fine after that.
CPU overclock settings can not be changed in settings. Works fine in setcpu.
No camera app included.
EDIT: Phone was plugged into usb port on computer entire time, and I noticed that the battery was not charging. Flashed back to my daily driver for now and phone is charging again. Not sure if this is common to anyone else or just a bug for me.
Click to expand...
Click to collapse
Might flash back to test some more once my battery gets up to a decent level
Can't get it to boot, using CWR 3 from Rom Manager
jyeley5 said:
Can't get it to boot, using CWR 3 from Rom Manager
Click to expand...
Click to collapse
Originally Posted by kfazz
if you have bootloop:
adb shelll and
rm /system/lib/hw/gps.sholes.so
jyeley5 said:
Can't get it to boot, using CWR 3 from Rom Manager
Click to expand...
Click to collapse
db2u said:
Originally Posted by kfazz
if you have bootloop:
adb shelll and
rm /system/lib/hw/gps.sholes.so
Click to expand...
Click to collapse
I have 3 loops at the "M" screen each time before it moves on to the android screen and finishes the boot even with gps.sholes.so removed
Sent from my Galaxy Nexus using Tapatalk 2
Finally got it booting, thanks for the help!
kfazz: Awesome work!!! What's the current status of FM radio though? I tried the FMRadio.apk from the Defy and it FC'd as soon as I plugged in my headphones
peeyourownpants said:
I have 3 loops at the "M" screen each time before it moves on to the android screen and finishes the boot even with gps.sholes.so removed
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I used to get that on CM7.1 I think it was a bad flash, It went away when I flashes Steeldroid, and I am definitely not getting it on this build
mediafire virus
After using link at top of page to download from media fire using Windows explorer I got a message saying virus detected on my computer and the page looks exactly like Microsoft security essentials I clicked no and computer crashed!!! This makes 2 times I have gotten virus from media fire last time I was able to restore to an earlier backup this time computer wouldn't let me boot into recovery or anything after much trouble I got it to boot into safe mode only because I have recovery disks that came with PC but have not been able to repair it complelty yet because if I try to restore it ends with an error about system contains some file ( idont remember name) so if I can't figure it out I guess I will backup important files and do a complete restore from factory disks ( last resort ) . Just a warning . If anybody has any answers and or ways to prevent this please PM me. Hopefully this won't happen to anyone else
Sorry for highjacking thread I know this is off subject but don't want anyone else to become a victim!!
Link worked fine when downloaded from phone but I have no way to modify zip or use adb to make JB boot
Sorry to kfazz for this post I know its not his fault I found many people with same problem with a Google search
Keep up the great work kfazz you are the best!!
peeyourownpants said:
I have 3 loops at the "M" screen each time before it moves on to the android screen and finishes the boot even with gps.sholes.so removed
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Similar problems, but mine's randomly deciding to boot up or not. Sometimes it doesn't boot at all, other times it boots on the first try.
However since the Camera, Wifi, and other Jelly Bean goodness works, I can't help but to thank you on this release, Good luck on further development!
EDIT: And now it won't even boot, sometimes it just gets stuck at a blank screen. Bummer.
denwaotoko said:
Similar problems, but mine's randomly deciding to boot up or not. Sometimes it doesn't boot at all, other times it boots on the first try.
However since the Camera, Wifi, and other Jelly Bean goodness works, I can't help but to thank you on this release, Good luck on further development!
Click to expand...
Click to collapse
i cant get the new build to boot i removed the gps.sholes file and im just bootlooping at m logo
wolf45801 said:
i cant get the new build to boot i removed the gps.sholes file and im just bootlooping at m logo
Click to expand...
Click to collapse
Which one, the one with fm radio and camera? I was able to get the first build to boot fine after removing gps.sholes
ASAM123 said:
Which one, the one with fm radio and camera? I was able to get the first build to boot fine after removing gps.sholes
Click to expand...
Click to collapse
i couldn't get the newest to boot either, just loops at the M.
i poked into the .zip and the gps file is gps.goldfish.so, not sure if that's relevant...
ASAM123 said:
Which one, the one with fm radio and camera? I was able to get the first build to boot fine after removing gps.sholes
Click to expand...
Click to collapse
i finally got it working i downloaded the new one but for some reason mediafire didnt download the full rom so had to redownload
I can't get it to boot up. I end up with red M bootloops with both the 8/24 and 8/26 builds. I wiped everything between flashes. Any ideas?
Flashed over 7/12 ics build seems as good as ics was don't think I will be going back to ics. Gallery opens but never shows any pics fm radio is nice only plays in mono other than that everything else I have tested is working correctly great work as usual
Thanks to all who are making this possible
Sent from my Droid using xda app-developers app
Moto G 16GB, bought off Amazon.co.uk. Rooted and flashed 4.4.2 before it was pushed to the device (I think it was an image off US version, found it in these forums back when I got the phone). I've been getting a prompt to install some Motorola US update for a few weeks, it pops up every now and then, has gone away when I tapped "No, thanks" option. All was fine until this morning...this is a really weird problem.
I don't know if the phone updated itself overnight, but when I dismissed the alarm this morning I couldn't get past the lockscreen. I put in my lock code and the phone had the stock wallpaper, then cycled to black background, then back to stock wallpaper and then I got a pop up saying "Unfortunately, the process com.android.systemui has stopped." and I was bumped back to the PIN lockscreen. Tried again, same thing. Now it doesn't even say anything about androidui, just cycles between black background and stock wallpaper and kicks me out.
Tried hooking it up to a PC and Mac, but neither recognized it and the phone appeared to be just charging. Power cycled it a dozen times by holding down the power button for about 6 seconds and I always end up with the same problem of not getting past the lockscreen. Every time I boot the phone now it says "Android is upgrading... Optimizing app 1 of 1". This is why I thought maybe I was pushed some incompatible US update?
Underneath it all the phone works fine, got the alarm this morning, received an SMS, answered a phone call. I can even get to the camera from the lockscreen. Is there any other options besides complete wipe and starting from the beginning again?
Probably OT, but I've always had trouble with the launcher quitting, no matter what launcher I'm using, on Moto G and the previous GNex.
Any help is appreciated, I'm bummed.
Hi,
i've today the same, exactly the same problem. It's strange, because i can't reset my phone to factory default, i went to the recovery menu, then "factory", but it only rebooted...
My "solution":
I reinstalled the original firmware:
http://forum.xda-developers.com/showthread.php?t=2542219
Then all works fine.. No matter why this error occurs.. an automatic firmware update? ..i don't know...
the exact same thing happened to me today out of nowhere and i'm about to leave on a trip, i'm so angry!
Jeez...well, looks like I'm not the only one. WTF happened? I left on a weekend trip too and I'm P.O.'d. I haven't been too religious with my backups either, that's why I was trying to find a way to back things up before wiping it all, but it looks like I'm out of luck. Guess a full wipe is in order.
hmmm i'm a complete dufus when it requires ADB, i've followed the procedures at the link but everytime i try to enter an input cmd says "mfastboot is not a recognized command"
electrictimes said:
Jeez...well, looks like I'm not the only one. WTF happened? I left on a weekend trip too and I'm P.O.'d. I haven't been too religious with my backups either, that's why I was trying to find a way to back things up before wiping it all, but it looks like I'm out of luck. Guess a full wipe is in order.
Click to expand...
Click to collapse
my phone wasn't even rooted, pure stock kitkat, i'm taking my heavy ass old notebook with me and will spend my days off trying to fix this **** it seems
a.monteiro said:
hmmm i'm a complete dufus when it requires ADB, i've followed the procedures at the link but everytime i try to enter an input cmd says "mfastboot is not a recognized command"
Click to expand...
Click to collapse
Take a look:
c) If the firmware file you downloaded is a .xml.zip file then download Motorola Fastboot mfastboot-v2.zip (attached to this post) and extract the .exe into the same folder as the stock firmware files (the same folder as the .bin and .img files). If your firmware is a .tar.gz file then skip this step.
I'm debating if I should go ahead and restore the firmware OR wait for Motorola to right their wrongs!
a.monteiro said:
the exact same thing happened to me today out of nowhere and i'm about to leave on a trip, i'm so angry!
Click to expand...
Click to collapse
Same situation....
ifishy said:
Take a look:
c) If the firmware file you downloaded is a .xml.zip file then download Motorola Fastboot mfastboot-v2.zip (attached to this post) and extract the .exe into the same folder as the stock firmware files (the same folder as the .bin and .img files). If your firmware is a .tar.gz file then skip this step.
Click to expand...
Click to collapse
I... did that, but obviously not the correct way, i'm downloading the files on my note and will try again. Maybe I should unpack the firmware files at some specific place? The instructions said nothing about this so I did nothing.
zofari said:
I'm debating if I should go ahead and restore the firmware OR wait for Motorola to right their wrongs!
Click to expand...
Click to collapse
Just reminded me that my phone is still within warranty, doing this restore may void it?
a.monteiro said:
I... did that, but obviously not the correct way, i'm downloading the files on my note and will try again. Maybe I should unpack the firmware files at some specific place? The instructions said nothing about this so I did nothing.
Just reminded me that my phone is still within warranty, doing this restore may void it?
Click to expand...
Click to collapse
My phone is back working..at the cost of wiping out all my data.
zofari said:
My phone is back working..at the cost of wiping out all my data.
Click to expand...
Click to collapse
Guess this is the only way out of this, then. What a mystery... I wonder if this is the "Welcome to Lenovo" update 1.0 lol.
i'm getting a "missing AdbWinApi.dll" although i've installed all the applications required, any help?
edit: guess i also need the android sdk, right?
edit2: got it, just copy the dlls from the minimal adb directory into the firmware directory and it's good to go, just configuring my newly restored device, thanks all
I wonder why this happened? I was using google play store at the moment, updating the flipboard app...
a.monteiro said:
I wonder why this happened? I was using google play store at the moment, updating the flipboard app...
Click to expand...
Click to collapse
I guess It's the problem of flipboard app!
My father's phone is also experiencing this issue, I can't even reset the phone to factory settings.
This occurred when I was also updating the flipboard app... seriously I'll have to RMA this...
----------------------
So I also have an issue where when you unlock the screen, it just locks back up (no android dialogue saying that com.android.systemui has crashed, but the same result).
I'm also unable to go into bootloader -> Recovery to factory reset the phone.
I stupidly tried to uninstall the flipboard app and reinstall it and it killed the phone... it's now stuck and quite annoying.
I'm 99% sure it's Flipboard.
Looks like others are having issues with Flipboard too
http://forums.androidcentral.com/moto-g/391289-something-seriously-wrong-my-moto-g.html
----------------
I solved the issue by following the instructions here:
https://motorola-global-portal.custhelp.com/app/answers/prod_answer_detail/a_id/97329/p/30,6720,9050
how could a flipboard update screw android so badly? what a strange day
edit: they seemed to have pulled the update back or fixed it though, during my restore flipboard installed without issues
Holy S*** I'm in the same situation. It's definitely the Flipboard update that caused everything. Support just acknowledged me but never gave me any solution. I'm running ART and I think that was contributing the problem. It's terrifying knowing how a single app can completely ruin your phone!!
Anyway guys, is there anyway I can save my pics and stuff before I wipe my data?
Good detective work, I now remember updating the Flipboard app w/ bunch of others as well when things were still all good. Could this be remedied if Flipboard would manage to push a working update? I really don't wanna wipe everything, and I'm not sure I can.
Word from Flipboard (via Twitter):
"Flipboard does not support the experimental OS ART at this time."
I've been trying to theme my phone, using Substratum, but keep getting stuck on the Sprint logo on reboot after applying a theme. Afterwards, the only way to fix it is to restore a backup.
Anybody know why? Is there a way to make it work?
Thanks!
Ps. I'm rooted mm 6.0.1, xposed framework
Sent from my SM-G900P using XDA-Developers mobile app
i tried it last week but it failed and i didnt revisit on it. @AthieN has has success with it. If he sees this (which is why i tagged him), he should be able to shed some light
---------- Post added at 11:25 AM ---------- Previous post was at 11:25 AM ----------
i tried it last week but it failed and i didnt revisit on it. @AthieN has has success with it. If he sees this (which is why i tagged him), he should be able to shed some light
dieseldeeznutz said:
I've been trying to theme my phone, using Substratum, but keep getting stuck on the Sprint logo on reboot after applying a theme. Afterwards, the only way to fix it is to restore a backup.
Anybody know why? Is there a way to make it work?
Thanks!
Ps. I'm rooted mm 6.0.1, xposed framework
Sent from my SM-G900P using XDA-Developers mobile app
Click to expand...
Click to collapse
youdoofus said:
i tried it last week but it failed and i didnt revisit on it. @AthieN has has success with it. If he sees this (which is why i tagged him), he should be able to shed some light
Click to expand...
Click to collapse
It's pretty buggy. After applying the theme, reboot to recovery and wipe all caches (including dalvik) and that should correct the issue. At least, that's how I've worked around the looping problem.
Also, if you get stuck and can't boot, you don't need to restore to fix it. Just boot into recovery, mount up the system partition, navigate to system/vendor/overlay and remove the apk's in there (those are where the theme files are located) and then reboot & try again.
If your device is getting stuck after applying a theme, it's usually due to a conflict of some sort. To figure it out, I'd recommend capturing a logcat during boot up to see what's going on. In my experience, it's usually system related themeing that breaks the device (like settings, navbar, etc.) so I typically stay away from those options and just theme my GAPPS.
Hope that helps!
Sent from my SM-G900P using Tapatalk
AthieN said:
It's pretty buggy. After applying the theme, reboot to recovery and wipe all caches (including dalvik) and that should correct the issue. At least, that's how I've worked around the looping problem.
Also, if you get stuck and can't boot, you don't need to restore to fix it. Just boot into recovery, mount up the system partition, navigate to system/vendor/overlay and remove the apk's in there (those are where the theme files are located) and then reboot & try again.
If your device is getting stuck after applying a theme, it's usually due to a conflict of some sort. To figure it out, I'd recommend capturing a logcat during boot up to see what's going on. In my experience, it's usually system related themeing that breaks the device (like settings, navbar, etc.) so I typically stay away from those options and just theme my GAPPS.
Hope that helps!
Sent from my SM-G900P using Tapatalk
Click to expand...
Click to collapse
thanks for the response I'll give it a try!