Related
10 charact
..........
Also reserved please
This sounds like something that can kill a lot if time while I'm in the office.
What are we looking for when doing this?
Sent from my DROID BIONIC using xda premium
ROB281 said:
This sounds like something that can kill a lot if time while I'm in the office.
What are we looking for when doing this?
Sent from my DROID BIONIC using xda premium
Click to expand...
Click to collapse
Well, I'll get to the point soon. still modifying the post. but basically the gist of it is to check ALL of motorola's update servers for updates, not just the one that comes programmed into the device. If we're lucky and we find a hidden update, we may be able to get an unlocked bootloader (or other goodies?), which will allow us to use our device as we please (new kernels, better mods, etc)
Thanks for writing this up, I've been hesitant to try it since some of the paths/files in other posts did not exist on the Bionic.
Sent from my DROID BIONIC using XDA App
karthakon said:
Thanks for writing this up, I've been hesitant to try it since some of the paths/files in other posts did not exist on the Bionic.
Sent from my DROID BIONIC using XDA App
Click to expand...
Click to collapse
Well, I was bold and basically just created the files. When I ran the *#*#4636#*#* test, I found that it did indeed change my could update server.
also the com.motorola.blur.setup was in /data/data/ and not the system/etc/motorola.
Thank you.
Sent from my ADR6400L using xda premium
Thank you for this. The previous directions were based on the Atrix so there were a lot of files listed that I never saw so I felt unsafe just making them up and moving things around. I'll get on this sometime in the very near future.
K.AuthoR said:
Thank you for this. The previous directions were based on the Atrix so there were a lot of files listed that I never saw so I felt unsafe just making them up and moving things around. I'll get on this sometime in the very near future.
Click to expand...
Click to collapse
I actually have been testing some methods that may not even req a wipe in between or possible before
Sent from my DROID BIONIC using Tapatalk
Apparently someone found an update somewhere. Good sign. I'm going to check it out in an hour or two. Don't have my hands on it yet.
Sent from my DROID BIONIC using Tapatalk
Looking at these right now. I'll go ahead and update the main thread with your corrections. Thank you for figuring it out!!!!
kennethpenn said:
Looking at these right now. I'll go ahead and update the main thread with your corrections. Thank you for figuring it out!!!!
Click to expand...
Click to collapse
when I hit the server, it says it's a 5.5.886 -> 5.5.891 update
phydo said:
when I hit the server, it says it's a 5.5.886 -> 5.5.891 update
Click to expand...
Click to collapse
Just so everyone can see it: the update label will always be for the build ID that the zip is supposed to be installed over. That means if you've got an update:
Blur_Version.1.XT875.Verizon.en.US.zip --> This means the zip should be installed over devices running Build number "1."
Blur_Version.5.5.886.XT875.Verizon.en.US.zip --> This means the zip should be installed over devices running Build number "5.5.886."
Was anyone ballsy enough to attempt to install the update? It doesn't have a bootloader inside, but it may still be dangerous.
P3 flashed it and it does absolutely contain a bootloader update.
The critical pieces are the mbm.bin, mbmloader_hs.bin and mbmloader_ns.bin.
HS and NS refer to Hardware Secure and Non Secure parts and both are included in these updates because both types of hardware are present in the test groups or whomever is the intended recipient of these files.
There is not an unlock, per se, but both secured and unsecured mbmloaders are present and the updater script has a check for the ro.secure status and loads the appropriate file for the target device.
The D3 update and assumedly this file as well cannot be reverted to stock release version, so this file must be regarded very carefully and assessed before any decision to flash or not is made.
There is a LOT more discussion we need to have about these files and OMAP SoCs I think regarding the differences between them and the Tegra II SoCs and fuse arrays!
Edit: This breaks the djrbliss root method using the tcmd exploit. We need to look further and discuss with him other possibilities for root. Reverting has not been established yet and may brick since we dont have a complete XML.zip.
WARNING!!!! This is a very dangerous file to flash at this stage!!! Please do not rush into testing it yet!!!
Thanks to those who got the file and thanks to P3Droid for guinea pigging.
Oh and I have to add that clarified cheescake is an oxymoron...you garnish cheesecake with wonderful things!
cellzealot said:
P3 flashed it and it does absolutely contain a bootloader update.
The critical pieces are the mbm.bin, mbmloader_hs.bin and mbmloader_ns.bin.
HS and NS refer to Hardware Secure and Non Secure parts and both are included in these updates because both types of hardware are present in the test groups or whomever is the intended recipient of these files.
There is not an unlock, per se, but both secured and unsecured mbmloaders are present and the updater script has a check for the ro.secure status and loads the appropriate file for the target device.
The D3 update and assumedly this file as well cannot be reverted to stock release version, so this file must be regarded very carefully and assessed before any decision to flash or not is made.
There is a LOT more discussion we need to have about these files and OMAP SoCs I think regarding the differences between them and the Tegra II SoCs and fuse arrays!
Edit: This breaks the djrbliss root method using the tcmd exploit. We need to look further and discuss with him other possibilities for root. Reverting has not been established yet and may brick since we dont have a complete XML.zip.
WARNING!!!! This is a very dangerous file to flash at this stage!!! Please do not rush into testing it yet!!!
Thanks to those who got the file and thanks to P3Droid for guinea pigging.
Oh and I have to add that clarified cheescake is an oxymoron...you garnish cheesecake with wonderful things!
Click to expand...
Click to collapse
So I decided that I just couldn't sleep not knowing if the root patch had been fixed. So I decided to flash the update.zip. And what I expected to happen, happened, it zapped the local.prop exploit.
So here I sit on the new build unrooted and stock. I'm fairly certain that if I try to revert back to the OG build I will have a paper weight on my desk until a full xml fastboot file can be found. I would suggest you all wait and don't flash this yet.
jimmydafish said:
So I decided that I just couldn't sleep not knowing if the root patch had been fixed. So I decided to flash the update.zip. And what I expected to happen, happened, it zapped the local.prop exploit.
So here I sit on the new build unrooted and stock. I'm fairly certain that if I try to revert back to the OG build I will have a paper weight on my desk until a full xml fastboot file can be found. I would suggest you all wait and don't flash this yet.
Click to expand...
Click to collapse
thats what i call takin one for the team!!! thanks bro!!! You'll be rooted again in no time, maybe even s-off!!!
Enzopreme said:
thats what i call takin one for the team!!! thanks bro!!! You'll be rooted again in no time, maybe even s-off!!!
Click to expand...
Click to collapse
S-off doesn't apply to Moto products...
Sent from my DROID BIONIC using xda premium
cellzealot said:
P3 flashed it and it does absolutely contain a bootloader update.
The critical pieces are the mbm.bin, mbmloader_hs.bin and mbmloader_ns.bin.
HS and NS refer to Hardware Secure and Non Secure parts and both are included in these updates because both types of hardware are present in the test groups or whomever is the intended recipient of these files.
There is not an unlock, per se, but both secured and unsecured mbmloaders are present and the updater script has a check for the ro.secure status and loads the appropriate file for the target device.
The D3 update and assumedly this file as well cannot be reverted to stock release version, so this file must be regarded very carefully and assessed before any decision to flash or not is made.
There is a LOT more discussion we need to have about these files and OMAP SoCs I think regarding the differences between them and the Tegra II SoCs and fuse arrays!
Edit: This breaks the djrbliss root method using the tcmd exploit. We need to look further and discuss with him other possibilities for root. Reverting has not been established yet and may brick since we dont have a complete XML.zip.
WARNING!!!! This is a very dangerous file to flash at this stage!!! Please do not rush into testing it yet!!!
Thanks to those who got the file and thanks to P3Droid for guinea pigging.
Oh and I have to add that clarified cheescake is an oxymoron...you garnish cheesecake with wonderful things!
Click to expand...
Click to collapse
I suppose I was looking for the wrong things. On other devices, "ap20bl.img" was responsible for bringing such goodies as an unlock capability.
The blog where i found everything
This server was not really that private ... http://cafe.naver.com/develoid.cafe?iframe_url=/ArticleRead.nhn?articleid=24692&
http://dogsolefoot.iptime.org/D.Kim Kor/frame.htm?action=SkinFile#/Atrix/
On this site there is roms that have not been posted on xda.
After going to the website, click the rom folder, and there they are.
If you go to the fifth folder from the bottom, then go to the secret folder, there are files that seem to be ICS ports.
Tell me what you think!
The Site seems to be down...
http://dogsolefoot.iptime.org/D.Kim Kor/frame.htm?action=SkinFile#/
Mirror of Roms:
*If you have any please post ill give credit
http://www.multiupload.com/IE98U6DSI9 - TurTleRom beta5
Very cool! Folks, if you're thinking of flashing this, you may want to consider reviewing the contents of the .zip before flashing, removing anything like recovery.img that could lock you out of the Rom Manager or RomRacer CWM you're familiar with.
If you have no idea what I'm talking about, wait for someone else to come around and take a look first.
Happy Hacking and don't brick yourself!
----
While I was writing this, I see the trolls have descended upon the thread. If you're not technical enough to rip it apart and flash it, don't post.
It's a developer forum folks, nobody cares if you're anxiously awaiting everyone else to take the first try, we only care if you did and your results...
Damn, im so tempted..
I will review the contents of the zip, and report back.. Although I don't technically know what Im looking for besides a recovery image.
currently downloading some of those and taking a look inside them, everyone please go about this careful!
You're so freaking awesome man, here you come to the rescue again
checked out the one tittled ics_port_olympus_singed_test.zip, currently in the process of flashing it, will let you guys know whats up! the size seems legit
I would have to reluctantly check out mentally from my family for the night if this is true
ROM > TurtleRom > TurTleRom beta5.zip is ro.modversion=CyanogenMod-7-12112011-NIGHTLY-Olympus Didn't bother looking further as this looks boring
MIUI > alpha2-miui-Snya.zip is CM7 based too, but looks like it's default locale is in korean. Definitely has MIUI apks, rooted with Dolphin Browser HD too and Titanium Backup.
samcripp said:
checked out the one tittled ics_port_olympus_singed_test.zip, currently in the process of flashing it, will let you guys know whats up! the size seems legit
Click to expand...
Click to collapse
What directory did you find that in Sam?
_Alex_ said:
What directory did you find that in Sam?
Click to expand...
Click to collapse
It's in the op
Sent from my MB860 using XDA App
Yeah, that one's in 디프/secret.
_Alex_ http://dogsolefoot.iptime.org/Atrix/ROM/디프/secret/ics_port_olympus_test_signed.zip
but the file has installations issues, it aborts, let me fix that shiot and give it a second try!
Just found a kernel in there too called the jaryo 1.45 kernel it booted up fine but when i checked my about phone settings it clearly shows its actually fauxs kernel so nothing new there either.
my Koreans a bit rusty but this hopefully will turn out good.
Lots of it is just mirrors to other roms and something about a trackball
sent from my Atrix via XDA premium
the are several ics ports in there!
just waiting to see if it is safe!
marko! said:
my Koreans a bit rusty but this hopefully will turn out good.
Lots of it is just mirrors to other roms and something about a trackball
sent from my Atrix via XDA premium
Click to expand...
Click to collapse
Yeah im bettin this is all the same ole **** with just different names. that ics port is probably just evogp's rom!
No, it's clearly not; the build.prop file, for example, is totally inconsistent with a CM7 build.prop, and quite consistent with the build.prop files of other ICS beta ROMs that have been appearing.
begadkepat said:
No, it's clearly not; the build.prop file, for example, is totally inconsistent with a CM7 build.prop, and quite consistent with the build.prop files of other ICS beta ROMs that have been appearing.
Click to expand...
Click to collapse
Looks asop to me. Launcher2 is included some other stuff. The updater script is messy
Only one apn included and odexed
sent from my Atrix via XDA premium
I found this site the other day it supposedly has an miui ics rom and is also in korean. http://m.cafe.naver.com/ArticleList...arch.menuid=78&search.boardtype=L&usenotice=N only thing is i believe youve got to register to dl
so has anyone tried ics yet?
Hey people! This is my first post here, but I've been watching this place for over 3 years now. Primarily a Mac developer, but switched from iOS to Android even before ICS came out. I own an HTC Aria and a Galaxy Tab 10.1 (also one of those iCuttingBoards that apple makes).
This is just a zip file with all the files modified for the HTC Aria. Works great with that last EGL-enabled build of the CM9 rom in WinSuk's thread (I need 10 posts to thank him!?!? wtf?).
Here are instructions for rooted users:
1) Download the zip.
2) Unpack and you'll see the system folder with its hierarchies.
3) Open up Terminal (i'm a Mac) or cmd.exe (Windows).
4) adb push <my_unzipped_folder_here>/system/framework/android.policy.jar /system/framework/android.policy.jar
5) adb push <my_unzipped_folder_here>/system/usr/keylayout/ /system/usr/keylayout/
6) Reboot!
7) ENJOY!
The HTC Aria with CM9 + EGL, and this mod makes it a seriously amazing phone (arguably far better than stock. it runs faster than my iCuttingBoard 1st gen too!)
Galaxas0 said:
Hey people! This is my first post here, but I've been watching this place for over 3 years now. Primarily a Mac developer, but switched from iOS to Android even before ICS came out. I own an HTC Aria and a Galaxy Tab 10.1 (also one of those iCuttingBoards that apple makes).
This is just a zip file with all the files modified for the HTC Aria. Works great with that last EGL-enabled build of the CM9 rom in WinSuk's thread (I need 10 posts to thank him!?!? wtf?).
Here are instructions for rooted users:
1) Download the zip.
2) Unpack and you'll see the system folder with its hierarchies.
3) Open up Terminal (i'm a Mac) or cmd.exe (Windows).
4) adb push <my_unzipped_folder_here>/system/framework/android.policy.jar /system/framework/android.policy.jar
5) adb push <my_unzipped_folder_here>/system/usr/keylayout/ /system/usr/keylayout/
6) Reboot!
7) ENJOY!
The HTC Aria with CM9 + EGL, and this mod makes it a seriously amazing phone (arguably far better than stock. it runs faster than my iCuttingBoard 1st gen too!)
Click to expand...
Click to collapse
Ok, Am I missing something? Where is the link?
benbailey84 said:
Ok, Am I missing something? Where is the link?
Click to expand...
Click to collapse
The OP forgot to add it/attach the file .
Whoops! It should be attached now.
Galaxas0 said:
Whoops! It should be attached now.
Click to expand...
Click to collapse
Seriously crippled my Aria running MunJeni's CM9 4.0.4 ROM.
The hard buttons wouldn't work, and lots of other stuff broken.
Is this intended to be loaded into ICS or CM7?
Yeah. Just flashed munjeni's ROM... not fun. I'll release a new version as this one was meant for WinSuk's ROM.
Sent from my Liberty using XDA
Galaxas0 said:
Yeah. Just flashed munjeni's ROM... not fun. I'll release a new version as this one was meant for WinSuk's ROM.
Sent from my Liberty using XDA
Click to expand...
Click to collapse
Thanks for checking and for the work on this!
I'm probably asking a silly question, but what exactly is the multitasking button supposed to look like and what's it supposed to do?
I can press and hold the home screen for app switching, so I'm curious about what this button does and what advantage it offers.
.
Oh, this just takes the ICS Multitasking (the Recent apps) which the HOME PRESS + HOLD brings you, and puts that on the search button, which I've never used. Ever. Ever in the history of ever. So i'd love to have easier access to the multitasking.
P.S. does anyone know how to make this a flashable CWM zip?
Hmm awesome man..:thumbup:
Sent from my Android using xda premium
It's good!
Enviado desde mi LG-D802 mediante Tapatalk
Law and order
Rules: http://forum.xda-developers.com/announcement.php?f=1058
Also, Something you can stress enough:
ALWAYS USE THE SEARCH BUTTON AND POST QUESTIONS IN THE Q&A SECTION AND NOT THE DEVELOPMENT/GENERAL/ANY OTHER SECTION!!!
What is this and that (Glossary of android terms)
Rooting:
Allowing your device to run root only applications (You see them in the play store all the time). You can also access the Linux internals with root. It is an essential in order to unlocking the bootloader.
Bootloader unlocking:
This allows of flashing custom kernels and recoveries. After you unlock the bootloader, DO NOT OTA UPDATE!!! This will lose your bootloader unlock and/or Brick your device where you cannot unbrick it...
ADB:
ADB = Android Debug bridge. You can push files to the device, pull files from the device, and install applications. In order to use this you must goto Settings > Developer Options -> USB Debugging. You must also enable for rooting your device.
ROM:
Basicly, A custom firmware that is made unofficially by developers outside Motorola. These include tweaks and themes to make the device how you want and not ho Your carrier & Motorola want. You will need a custom recovery to install these (Requires bootloader unlock unless it says safestrap, or ss).
Kernel:
It is kind of like a rom, but without themes. These are mainly used for overclocking and undervolting. You need a bootloader unlock in order to use this.
I'll finish it after lunch...
Reserved...
Reserved again...
IMO this is pretty much a useless thread, a person wouldn't be browsing xda if he didn't know the meaning of the stuff listed above.
thread can be made useful by adding guide & links to bootloader unlocking, rooting, installing CWM, etc.
coldfear00 said:
IMO this is pretty much a useless thread, a person wouldn't be browsing xda if he didn't know the meaning of the stuff listed above.
thread can be made useful by adding guide & links to boot loader unlocking, rooting, installing CWM, etc.
Click to expand...
Click to collapse
Agreed!!!
But, I'm going to update it after school to make this actually useful.
coldfear00 said:
IMO this is pretty much a useless thread, a person wouldn't be browsing xda if he didn't know the meaning of the stuff listed above.
thread can be made useful by adding guide & links to bootloader unlocking, rooting, installing CWM, etc.
Click to expand...
Click to collapse
Yeah, a FAQ would be better than a glossary
Give him some time he tends to get ahead of himself.
Sent from my JokerMATRIX HD MAXX
Markyzz said:
Yeah, a FAQ would be better than a glossary
Click to expand...
Click to collapse
Sure, make a faq too.
Nice idea
tcf38012 said:
Sure, make a faq too.
Nice idea
Click to expand...
Click to collapse
I've been wanting to talk with some "power users" to get a good list of FAQs and answers. I'm just sick of seeing the same posts over and over again..
Feel free to PM me if you want some help with it
The way I see it, we already have most of the needed information but it's scattered around, disorganized. Some guides are good and others are crap. So this could include links to the helpful stuff rather than rewriting again.
My contribution: Use safestrap instead of CWM because nearly all ROMs were made specifically for SS.
Also SS allows you to flash RAZRHD roms with my wifi fix. Don't flash to stock if the ROM contains files in /system/etc/rootfs.
CWM: don't use it unless you want CM10 or you're an expert. Stop flashing RAZRHD roms with custom kernels. The LCD doesn't work.
progrockguy said:
My contribution: Use safestrap instead of CWM because nearly all ROMs were made specifically for SS.
Also SS allows you to flash RAZRHD roms with my wifi fix. Don't flash to stock if the ROM contains files in /system/etc/rootfs.
CWM: don't use it unless you want CM10 or you're an expert. Stop flashing RAZRHD roms with custom kernels. The LCD doesn't work.
Click to expand...
Click to collapse
You should be able to flash the Razr HD roms with CWM/TWRP as long as you mount /system before flashing.
Incredible long lunch
PD: Remember my advice
Lol right. And he's made a couple other help topics..
Sent from my PACMAN MATRIX HD MAXX
OP when you are done with your lunch and require the Thread to be reopened...PM me, Thanks, Thread Temp Closed for Lunch....
Since the bootloader just got unlocked, does anybody know if the moto maxx roms work on the turbo yet and if they don't how can we get them up and working?
Sent from my XT1254 using Tapatalk
I know CM is not working yet, but I can't vouch for any of the stock modified ROMs.
Sent from my XT1254 using Tapatalk
Just tried flashing XT1225 5.0.2 system. It boots up, but fails to set up. Reboots at the first setup screen.
I guess XT1250 4.4.4 will work since it has same FCC ID.
CM 12.1 s being worked on right now. See this page. Looks like it's been solved. You will probably get it in the next day or so with a new nightly.
Or workaround instructions may be posted before then.
http://forum.xda-developers.com/mot...axx-xt1225-cm12-0-pre-release-t3060089/page85
Once CM 12.1 is sorted, then the other ROMs, especially Resurrection Remix will adopt the same procedure. @Skrilax_CZ, the CM dev and @baybutcher27, the Resurrection Remix and Mokee dev, are helping each other on this. @baybutcher27 also has a custom kernel with lots of neat features, in addition to CM base kernel, so they both want this to work for ALL Quarks.
several trials and errors I did.
XT1250 KK -> XT1254 DOES Work without any FCs. Since it is an identical device, it should work fine. However, it needs LP stock rom which is unavailable I think.
XT1225 LP -> XT1254 DOES NOT Work.
- With XT1225 boot.img : Reboot after choosing language from Setup Wizard
- With XT1254 boot.img : Constant Telephone FC. Device seems to be working I guess
What are the odds of the quark forums being put back together now that we are unlocked? Rather than monitoring 3 diff forums? Not sure how it was before but making it similar to the G2 forums, where you had a general G2 dev forum, then a sub-forum for each specific carrier.
Anybody on XT1254, can you open adb and do "getprop ro.boot.radio" and "getprop ro.boot.carrier" and post the output?
Skrilax_CZ said:
Anybody on XT1254, can you open adb and do "getprop ro.boot.radio" and "getprop ro.boot.carrier" and post the output?
Click to expand...
Click to collapse
Code:
[email protected]:/ $ getprop ro.boot.radio
0x4
[email protected]:/ $ getprop ro.boot.carrier
[email protected]:/ $
Skrilax_CZ said:
Anybody on XT1254, can you open adb and do "getprop ro.boot.radio" and "getprop ro.boot.carrier" and post the output?
Click to expand...
Click to collapse
I attached a screen of my ADB screen
mbarry55 said:
What are the odds of the quark forums being put back together now that we are unlocked? Rather than monitoring 3 diff forums? Not sure how it was before but making it similar to the G2 forums, where you had a general G2 dev forum, then a sub-forum for each specific carrier.
Click to expand...
Click to collapse
That was what some of us suggested -- but the the Droid Turbo owners wanted us far, far away. Now they need us.
I suppose it might have been confusing at the time
I came from a razrm and while I shared a cm11 rom with several phones specs were different on the devices.
Personally I would like to see the forums merged as well. If it didn't make sense then. It does make sense now.
Sent from my XT1254 using XDA Free mobile app
mrkhigh said:
I suppose it might have been confusing at the time
I came from a razrm and while I shared a cm11 rom with several phones specs were different on the devices.
Personally I would like to see the forums merged as well. If it didn't make sense then. It does make sense now.
Sent from my XT1254 using XDA Free mobile app
Click to expand...
Click to collapse
Perhaps the same people who petitioned for the divide need to petition for a merger?
I'm not sure who finally approved the Quark forum split, but @TonyStark was very helpful in making it go smoothly. Some stuff got put in wrong forum and he fixed it promptly.
Now with bootloader unlock and common kernels, ROMs, there's no reason to be divided anymore. Everything now works on all QUARKS.
I can see this being an issue. It seems as though a maxx dev put out a kernel for the Turbo that will run RR and CM12.1. Would that dev post it here as well, or link it with flashing instructions?
A lot of us have been sitting idle waiting for the bootloader unlock to happen, and haven't had to delve very deep into the inner workings of lollipop. I personally haven't had a bootloader unlocked phone since 2011 or so, so I m trying to be very cautious in what/how I flash. Having to bounce between forums and even devices is quite worrysome when you haven't been actively flashing for some time.
boomslick08 said:
I can see this being an issue. It seems as though a maxx dev put out a kernel for the Turbo that will run RR and CM12.1. Would that dev post it here as well, or link it with flashing instructions?
Click to expand...
Click to collapse
You are referring to @baybutcher27, who is also the Resurrection Remix dev and OFFICIAL TWRP QUARK dev. And yes he also has his own kernel, based on CM kernel but with additional options.
CM dev @Skrilax_CZ made CM kernel work for XT1254. But that will show up in tomorrow's "nightly".
You can find links to everything here:
Moto Maxx Original Android Development
http://forum.xda-developers.com/moto-maxx/orig-development
Moto Maxx Android Development
http://forum.xda-developers.com/moto-maxx/development
Moto Maxx Themes and Apps
http://forum.xda-developers.com/moto-maxx/themes-apps
Once you go to those links, read the first post and the last few posts. There's plenty of instructions.
Now that the XT2254 bootloader is unlocked, it's just another Quark. Everything will work.
Whether they duplicate those threads over here is up to the devs. That's double work to maintain two threads for the exact same releases.
If they decide to keep the devices separated it really just needs a post with a link saying "go here" in the droid rom section
Sent from my XT1254 using XDA Free mobile app
Has anyone got CM12 to work properly? I did a FDR, flashed the rom, and then butchers updated kernel. I can get it to boot, but it won't update/install any of my apps from the play store.
EDIT: OOps, i flashed one of the radio images in skrilax's CM12 thread. Not i can't get any signal. Anyone have the radio.img from SU4TL-44?
Wouldn't the download for 10/10/15 have what you need?
http://forum.xda-developers.com/showthread.php?p=61752986
Sent from my XT1254 using XDA Free mobile app
mrkhigh said:
Wouldn't the download for 10/10/15 have what you need?
http://forum.xda-developers.com/showthread.php?p=61752986
Sent from my XT1254 using XDA Free mobile app
Click to expand...
Click to collapse
Thought it did, i found it elsewhere. Got it to connect to cell when it loads up, still having the play store issue on RR as well as CM12.
I think it has something to do with the 'Storage space running out' message i'm getting. Not sure why thats there, never had it on any other rom/phone.
I have RR running without a hitch it seems. Calls, sms, mobile data all working normally. Havent had any google play issues yet either and ive installed quite a few apps. So far, so good here.
brennam7 said:
Thought it did, i found it elsewhere. Got it to connect to cell when it loads up, still having the play store issue on RR as well as CM12.
I think it has something to do with the 'Storage space running out' message i'm getting. Not sure why thats there, never had it on any other rom/phone.
Click to expand...
Click to collapse
I had that happen when I first flashed it this morning. I had done just a factory reset in twrp. When I mounted system and wiped the partition than reinstalled RR I didn't have a single problem. It shouldn't be doing that anyways seeing that the system partition is 5GB