Moto X to ghost / obake is dead. - Droid Ultra General

http://www.cyanogenmod.org/blog/housekeeping-sony-and-moto-x
Sent from my XT1080 using Tapatalk

I had a feeling this was coming soon.
Sent from my XT1080 using Tapatalk

So Moto X ROMs cannot be flashed on 2013 Droids anymore?

I am sure you can still flash the X version, but you will probably end up with some problems because of the minor hardware differences.

thanks for the heads up, im sorry to hear this but i was expecting this, but still im pretty sure the moto x build will still work.

Someone will port it. I'm pretty sure its just driver and some file swap
Sent from my XT1080 using Tapatalk

tecsironman said:
Someone will port it. I'm pretty sure its just driver and some file swap
Sent from my XT1080 using Tapatalk
Click to expand...
Click to collapse
I can port a stable or RC version, but no way will I be doing it for nightlies.

Is there still an MMS/LTE bug on CM for the Moto devices? I remember it was a problem with my droid 4, even after it got picked up for official support.
Sent from my XT1080 using Tapatalk

ws6formula350 said:
Is there still an MMS/LTE bug on CM for the Moto devices? I remember it was a problem with my droid 4, even after it got picked up for official support.
Sent from my XT1080 using Tapatalk
Click to expand...
Click to collapse
I'm not to sure. I would love to use cm again as my daily driver like I did when I had my s3 but with no notification light and the add bonuses with the stock 4.4.4 with gravity box I don't see the need to change.
Sent from my XT1080 using Tapatalk

This news ruined my spirits..... I love CM rom.

Just tried the new ghost build with my Droid Mini. Works fine once I modify the install script, install the binary package for the mini, and update the build.prop.
Can probably do the same with the Ultra and Maxx.

Rottgrub said:
Just tried the new ghost build with my Droid Mini. Works fine once I modify the install script, install the binary package for the mini, and update the build.prop.
Can probably do the same with the Ultra and Maxx.
Click to expand...
Click to collapse
How do you do that?

I may try to bang something together this weekend to make it easier.
Basically though, you need to have all the binaries specific to your device. Since Mini was never supported, we've had these for a while. Then just need to add:
qemu.hw.mainkeys=1
To build.prop, and edit the install script to not blow out on the assert. (For whatever reason, recovery doesn't identify the xt1030, and populate the right property.)

Rott- Any chance on still making that guide? I want to update to a newer version of EHNDROIX but can't due to no support.

Work has had me traveling, so I haven't had much time to look into it. I do have a preliminary package for the Droid Mini (xt1030) put together that I'm testing.
Which phone do you have? If you can, run "adb shell" while in OS and also in recovery and let me know what your device reports for:
getprop ro.product.device
getprop ro.build.product
getprop ro.product.model
For whatever reason, the Mini doesn't report correct properties in recovery (Philz ghost builds). Makes it tough to make an "all-in-one" package for the Mini, Ultra, and Maxx.
In any case, I've attached the Droid Mini (xt1030) test version. Will probably blow up your hamster, etc, etc. The update-script and build-prop script are complete junk, but should give you an idea of what I'm doing.

IS Maxx a Moto Ghost code name?
tecsironman said:
http://www.cyanogenmod.org/blog/housekeeping-sony-and-moto-x
Sent from my XT1080 using Tapatalk
Click to expand...
Click to collapse
I'm confused

jerbear44 said:
I'm confused
Click to expand...
Click to collapse
The Motorola ‘moto_msm8960dt’ device variant is getting a rebranding to be simply known as ‘ghost’ – encompassing all previously supported variants of the Moto X (1st gen) device. Notably, however, we are officially dropping support for the ‘obake’ device (Moto Droid Maxx Dev Edition) moving forward.
Sent from my XT1080 using Tapatalk

Rottgrub said:
Work has had me traveling, so I haven't had much time to look into it. I do have a preliminary package for the Droid Mini (xt1030) put together that I'm testing.
Which phone do you have? If you can, run "adb shell" while in OS and also in recovery and let me know what your device reports for:
getprop ro.product.device
getprop ro.build.product
getprop ro.product.model
For whatever reason, the Mini doesn't report correct properties in recovery (Philz ghost builds). Makes it tough to make an "all-in-one" package for the Mini, Ultra, and Maxx.
In any case, I've attached the Droid Mini (xt1030) test version. Will probably blow up your hamster, etc, etc. The update-script and build-prop script are complete junk, but should give you an idea of what I'm doing.
Click to expand...
Click to collapse
The MAXX Dev edition I have is reporting the following info back either in Recovery or booted up:
getprop ro.product.device
obake
getprop ro.build.product
moto_msm8960dt
getprop ro.product.model
DROID MAXX

bsilvertab said:
The MAXX Dev edition I have is reporting the following info back either in Recovery or booted up:
getprop ro.product.device
obake
getprop ro.build.product
moto_msm8960dt
getprop ro.product.model
DROID MAXX
Click to expand...
Click to collapse
I think thats were the issue lies with all these new roms. They are all moving to "ghost". I figured that and "ghost" rom would install with my droid ultra but thats not the case. I stopped fussing around with the roms. Stock with gravity box and exposed works just fine for me.

tecsironman said:
I think thats were the issue lies with all these new roms. They are all moving to "ghost". I figured that and "ghost" rom would install with my droid ultra but thats not the case. I stopped fussing around with the roms. Stock with gravity box and exposed works just fine for me.
Click to expand...
Click to collapse
The ghost builds assert on ro.product.device, or ro.build.product = "ghost", which any of the new recovery images for the ghost builds should supply. Does on my xt1030 at least. I use the recovery here, which seems to work well enough:
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/ghost/
I should have some time to put together a better patch and instructions this weekend. Should be able to include Ultra/Maxx bins (if I can find them), but would need someone to test, since I don't have the xt1080.
Cheers!

Related

[Q] ROM's for Locked 4.1.2 - 98.30.1

Lost the unlocked/rooted X907, had to replace it with a retail version as I was traveling and needed something immediately and wanted to stick with the X907 - as opposed to getting an older one on ebay which I'm probably going to do now anyway just to have a backup. It's the 4.1.2 - 98.30.1 - as I understand it I'm stuck with it locked. I've rooted it with the SafeRoot script.
I've searched a bit and found a few leads, but was wondering if there were any others in a similar situation that make a recommendation for any 4.1.2 ROM's, and/or provide more links on the subject. It seems to me that there would be many who might have the similar misfortune for whatever circumstance. cheers -
blksheep said:
Lost the unlocked/rooted X907, had to replace it with a retail version as I was traveling and needed something immediately and wanted to stick with the X907 - as opposed to getting an older one on ebay which I'm probably going to do now anyway just to have a backup. It's the 4.1.2 - 98.30.1 - as I understand it I'm stuck with it locked. I've rooted it with the SafeRoot script.
I've searched a bit and found a few leads, but was wondering if there were any others in a similar situation that make a recommendation for any 4.1.2 ROM's, and/or provide more links on the subject. It seems to me that there would be many who might have the similar misfortune for whatever circumstance. cheers -
Click to expand...
Click to collapse
My fav is LS 2.37, it works on slot 1 just fine. I have a collection of old 4.1 custom ROMs that will work if you want, but LS 2.37 is the best and still findable without much difficulty
rocketrazr99 said:
My fav is LS 2.37, it works on slot 1 just fine. I have a collection of old 4.1 custom ROMs that will work if you want, but LS 2.37 is the best and still findable without much difficulty
Click to expand...
Click to collapse
Cheers - I will give that one a shot.
SS compatible ROMs:
-Early builds of CM10 (way early, like at the beginning of thread early)
-DeadCalm was SS enabled, not sure if it was modified for an unlocked bootloader only
-Energy is SS enabled and never altered for unlocked bootloader
-Flying Jelly was SS enabled and I don't think it was modified to work only on an unlock bootloader
-Eclipse v1.2 was SS enabled, I don't think it was modified for unlocked bootloader
Courtesy of RikRong
Hmm. Couldn't get LS 2.3.7 to boot, installed on rom slots 1-3, SS 3.1.1 with wipes and resets. Blank screen. I'll give these others a shot then try and diagnose what's up.
blksheep said:
Hmm. Couldn't get LS 2.3.7 to boot, installed on rom slots 1-3, SS 3.1.1 with wipes and resets. Blank screen. I'll give these others a shot then try and diagnose what's up.
Click to expand...
Click to collapse
Isn't LS for LS-970?
http://forum.xda-developers.com/showthread.php?t=2526022
liquid smooth is out for several device's...smh
Sent from my XT907 using xda app-developers app
ezknives said:
liquid smooth is out for several device's...smh
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
Okay.. let me rephrase.. where's the one for the droid razr m? I think there safestrap friendly aren't they or the 2.2.7 was..?
http://www.drdevs.com/devs/teamliquid/Official/2.37/
There you go... I'm not sure if it is ss friendly but that's the 2.37 version
Sent from my XT907 using xda app-developers app
ezknives said:
http://www.drdevs.com/devs/teamliquid/Official/2.37/
There you go... I'm not sure if it is ss friendly but that's the 2.37 version
Click to expand...
Click to collapse
Doesn't work..
So there yah go!

[HOWTO] Enable multiple user accounts on non-KitKat ROM

When I picked up my Note 10.1 2014 Edition (SM-P605) I was very disappointed to find that multiple user accounts had been disabled. A little research revealed that there was a US Cellular ROM in the past that had it enabled, but all other ROMs did not. Also, apparently the new KitKat ROM is going to have it. But what to do while we wait for Samsung to update our device?
Well, as it turns out, the answer is a lot easier than you might think, provided you have a rooted device.
Disclaimer: My device is the SM-P605 running P605XXUBMJA. I gained root using Chainfire's CF-Auto-Root. Try this at your own risk.
Basically, ALL you have to do is add a single line to the bottom of your build.prop file in /system, as follows:
Code:
fw.max_users=4
I edited my build.prop using my file editor (Solid Explorer) after giving it root privileges. You can also do it via a terminal emulator or ADB. Reboot your device, and that's all there is to it!
After a reboot, I had the "Users" option under General in Settings, and I was able to add my wife as a second user. We can now switch users either from the lockscreen, or the notification pull-down. After reading countless posts here on XDA saying that it was impossible, I really was surprised at how easy it was in the end.
Hopefully this helps others like me that are impatiently waiting for the KitKat update so that they can share their tablet with family members / guests.
Enjoy!
StNickZA said:
When I picked up my Note 10.1 2014 Edition (SM-P605) I was very disappointed to find that multiple user accounts had been disabled. A little research revealed that there was a US Cellular ROM in the past that had it enabled, but all other ROMs did not. Also, apparently the new KitKat ROM is going to have it. But what to do while we wait for Samsung to update our device?
Well, as it turns out, the answer is a lot easier than you might think, provided you have a rooted device.
Disclaimer: My device is the SM-P605 running P605XXUBMJA. I gained root using Chainfire's CF-Auto-Root. Try this at your own risk.
Basically, ALL you have to do is add a single line to the bottom of your build.prop file in /system, as follows:
Code:
fw.max_users=4
I edited my build.prop using my file editor (Solid Explorer) after giving it root privileges. You can also do it via a terminal emulator or ADB. Reboot your device, and that's all there is to it!
After a reboot, I had the "Users" option under General in Settings, and I was able to add my wife as a second user. We can now switch users either from the lockscreen, or the notification pull-down. After reading countless posts here on XDA saying that it was impossible, I really was surprised at how easy it was in the end.
Hopefully this helps others like me that are impatiently waiting for the KitKat update so that they can share their tablet with family members / guests.
Enjoy!
Click to expand...
Click to collapse
One has to ask, with tears in my blood shot eyes, why Samsung had to disable it in the first place.
Not a very friendly thing to do!
Chaos-sa said:
One has to ask, with tears in my blood shot eyes, why Samsung had to disable it in the first place.
Not a very friendly thing to do!
Click to expand...
Click to collapse
Yeah who knows? Maybe ask these idiots - http://forum.xda-developers.com/showthread.php?t=2741664
Apparently it is unreasonable to expect Samsung to keep core Android functionality.
StNickZA said:
Yeah who knows? Maybe ask these idiots - http://forum.xda-developers.com/showthread.php?t=2741664
Apparently it is unreasonable to expect Samsung to keep core Android functionality.
Click to expand...
Click to collapse
I read this post and quite frankly you have every reason to point out Samsung's short comings. They have got to big for there boots and when you have paid for a product, irrespective how much, you have a right to a certain level of expectations.
Lets face it we all want upgrades otherwise we wouldn't be here on XDA and for a product as new as the Note 10.1 2014 we have a right to expect 4.4. No they are not "legally" obliged to give it but hey our next buy will then become some manufacturer that steps up for us...the consumer. Sony is my bet!
Hehe. Oh well, with multi user accounts now working, I'm less worried about the Kitkat update than before.
Sent from my Nexus 5 using Tapatalk
I can confirm that this actually works!!!
StNickZA said:
Yeah who knows? Maybe ask these idiots - http://forum.xda-developers.com/showthread.php?t=2741664
Apparently it is unreasonable to expect Samsung to keep core Android functionality.
Click to expand...
Click to collapse
I was one of those idiots haha, tbh its not unreasonable but everyone knows samsung are **** with updates and many things but Oh well you have found a solution so alls good.
Being a Samsung owner for over 2 years now I have learned Samsung are the worste for this but have just learned to accept it, its probably daft of me to expect others to accept it too.
Sent from Galaxy Note 10.1 2014 Edition via Tapatalk.
Didnt work on my "NC2 Rom".
hanspampel said:
Didnt work on my "NC2 Rom".
Click to expand...
Click to collapse
Hmm, strange. I updated to P605ZSUBNC2 last night and repeated the same steps. All working just fine.
Hmm maybe its because i modified the secSettings.apk.
Edit: Ahh works now.
So guys ive made a flashable zip for this edit to build.prop. Works fine. Tested by me. But you should have busybox installed, otherwise i shouldnt work so.
hanspampel said:
So guys ive made a flashable zip for this edit to build.prop. Works fine. Tested by me. But you should have busybox installed, otherwise i shouldnt work so.
Click to expand...
Click to collapse
Thanks!! That's really awesome of you
Just a quick question - I imagine that there wouldn't be any issue with future updates right? When the option will be added officially I mean (obviously OTA won't work anyway though, with a 'customised system' preventing normal Samsung updates)
Thanx a mil
StNickZA said:
When I picked up my Note 10.1 2014 Edition (SM-P605) I was very disappointed to find that multiple user accounts had been disabled. A little research revealed that there was a US Cellular ROM in the past that had it enabled, but all other ROMs did not. Also, apparently the new KitKat ROM is going to have it. But what to do while we wait for Samsung to update our device?
Well, as it turns out, the answer is a lot easier than you might think, provided you have a rooted device.
Disclaimer: My device is the SM-P605 running P605XXUBMJA. I gained root using Chainfire's CF-Auto-Root. Try this at your own risk.
Basically, ALL you have to do is add a single line to the bottom of your build.prop file in /system, as follows:
Code:
fw.max_users=4
I edited my build.prop using my file editor (Solid Explorer) after giving it root privileges. You can also do it via a terminal emulator or ADB. Reboot your device, and that's all there is to it!
After a reboot, I had the "Users" option under General in Settings, and I was able to add my wife as a second user. We can now switch users either from the lockscreen, or the notification pull-down. After reading countless posts here on XDA saying that it was impossible, I really was surprised at how easy it was in the end.
Hopefully this helps others like me that are impatiently waiting for the KitKat update so that they can share their tablet with family members / guests.
Enjoy!
Click to expand...
Click to collapse
StNickZA...Thanx alot for this one line of code, added it last night and works PERFECT:laugh:
hanspampel said:
So guys ive made a flashable zip for this edit to build.prop. Works fine. Tested by me. But you should have busybox installed, otherwise i shouldnt work so.
Click to expand...
Click to collapse
I've rooted my Galaxy Note 10.1 2014 edition (Original ROM), I installed the busybox, then I flashed the zip file, but nothing happened.
Please advise me.
StNickZA said:
When I picked up my Note 10.1 2014 Edition (SM-P605) I was very disappointed to find that multiple user accounts had been disabled. A little research revealed that there was a US Cellular ROM in the past that had it enabled, but all other ROMs did not. Also, apparently the new KitKat ROM is going to have it. But what to do while we wait for Samsung to update our device?
Well, as it turns out, the answer is a lot easier than you might think, provided you have a rooted device.
Disclaimer: My device is the SM-P605 running P605XXUBMJA. I gained root using Chainfire's CF-Auto-Root. Try this at your own risk.
Basically, ALL you have to do is add a single line to the bottom of your build.prop file in /system, as follows:
Code:
fw.max_users=4
I edited my build.prop using my file editor (Solid Explorer) after giving it root privileges. You can also do it via a terminal emulator or ADB. Reboot your device, and that's all there is to it!
After a reboot, I had the "Users" option under General in Settings, and I was able to add my wife as a second user. We can now switch users either from the lockscreen, or the notification pull-down. After reading countless posts here on XDA saying that it was impossible, I really was surprised at how easy it was in the end.
Hopefully this helps others like me that are impatiently waiting for the KitKat update so that they can share their tablet with family members / guests.
Enjoy!
Click to expand...
Click to collapse
While I can confirm this totally works like a charm, I am experiencing a weird issue. THE LOCKSCREEN
Its behaving strangely. When i change users (both pass protected) the lockscreen always keeps the previous user's wallpaper. Sometimes it also "freezes" for a couple of seconds and cannot enter pin or pattern.
Am I the only one having these issues?
Im just rooted with towelroot and supersu, fully stock
It works! SM-P600 4.3 in the UK whoop! many thanks!
Happy bunny, it's really saved the day, very poorly wife can now use it and I'll be able to hangout with her from our sons graduation (without me loosing all my work stuff)! Chuffed to bits!

FXZ for Kit Kat released!

Are you bricked after the OTA? Here's how to unbrick it, locked or unlocked.
One other note: this is NOT an official 183 FXZ, so if this doesn't work, it won't make things worse, but you'll just have to wait for the "official" 183 FXZ.
Thanks go to stras1234 for providing a KK FXZ for those that needed it to unbrick their phone.
Another big thanks goes to SamuriHL for providing a tool to use the FXZ provided by stras1234 to make your job easier to unbrick your phone and get you running with KK.
Go here to get the FXZ and tool to help you profit in the glory that is Kit Kat on the XT926 Droid RAZR HD -> http://www.droidrzr.com/index.php/topic/45494-how-to-xt926-upgrade-to-kitkat-ota/
I have removed all my instructions as they are useless and no longer necessary with the FXZ being released.
Recommended strictly for unlocked bootloaders? Or would those of us with locked bootloaders be safe attempting as well providing we're on stock 9.30?
hi @iBolski i just want you to know that i share your post on the kk tracking post!
cmchance said:
Recommended strictly for unlocked bootloaders? Or would those of us with locked bootloaders be safe attempting as well providing we're on stock 9.30?
Click to expand...
Click to collapse
If you're already on stock 9.30, then it should work. I think the hang-ups for many who are manually loading it themselves via taking the OTA directly, were where if you were pushed the OTA and immediately accepted it and allowed it to go through and update it, it might have worked as long as you were unrooted on stock 9.30.
However, I chose to save the OTA off to the side (from the /cache directory) and hence, booted into the recovery manually, not realising that it installs a newer stock recovery and that's where I got hung up at. I thought the install failed, when in reality, I had to go back into the recovery and install it again. Of course, I tried using vol-down + vol-up and it wouldn't work.
If you currently have root though under 9.30, you might want to hold off until someone verifies if root can be obtained again. Because, without an unlocked boot loader, you will more than likely lose your access to root, especially if the latest "exploit" for 9.30 doesn't work under KK.
Your mileage may vary, but I don't have a locked bootloader phone to test this out on, so please, I do not accept any responsibility for what may happen if you try it, whether you have a locked or unlocked bootloader.
Thanks!
Just what I was needing to hear! I am currently rooted so I'll probably hold off. I've got a used Moto X on order though, should get it in today. After I test it out and verify that I can tolerate it and the smaller battery, then I might do some experimenting with the xt926 model I have and report back. Though, as anticipated as this update is, I'm sure someone will have already beat me to all the testing within a few hours from now lol
I'm on 9.30 with locked bootloader. I've tried your method but can't get pass signature verification. It just won't be installed on 9.30 firmware. There must be anything can be mess in updater script to avoid error signature.
Sent from my DROID RAZR HD using XDA Premium 4 mobile app
Hi! Can you please share "Blur_Version.9.30.1XT926.Verizon.en.US.zip" on dropbox gdocs or smth like that?
Sabissimo said:
Hi! Can you please share "Blur_Version.9.30.1XT926.Verizon.en.US.zip" on dropbox gdocs or smth like that?
Click to expand...
Click to collapse
I can't share the file, but if you look in the KitKat Tracking thread, you should find it there somewhere.
As an official soak tester, I'm not supposed to share the update. Technically, I'm not supposed to share ANY info, but I wanted to share this with other users who were having the same issue as I.
Thanks!
I do not believe the KK update for 9.30 has been shared anywhere.
No where that I can find. I've been scouring and following the forums waiting to find one myself.
sent from my ? and rooted XT1080 that thinks it's an XT1060
There you go, found it:
https://drive.google.com/file/d/0B8pGrRdP0CpyckJnd2JoQklHSjQ/
But I have another problem now: It says "Not a valid aboot" and aborts
I'm not worried about it right now, Moto Verizon just posted saying they approved the soak test and updates would be rolling out.
sent from my ? and rooted XT1080 that thinks it's an XT1060 using Tapatalk pro
---------- Post added at 03:16 PM ---------- Previous post was at 03:13 PM ----------
http://www.droid-life.com/2014/05/1...id-razr-hd-and-razr-m-on-verizon/#more-139933
sent from my ? and rooted XT1080 that thinks it's an XT1060 using Tapatalk pro
Sabissimo said:
There you go, found it:
https://drive . google.com/file/d/0B8pGrRdP0CpyckJnd2JoQklHSjQ/
But I have another problem now: It says "Not a valid aboot" and aborts
Click to expand...
Click to collapse
did your phone actually ota to 9.30 or did you use a sbf/utility and flashed it to 9.30?
the problem some people are having is, they flashed to 9.30 but the correct version they should be on is 9.18 and this post http://www.droidrzr.com/index.php/topic/44920-xt926-update-1824610-update/?p=431391 explains why thats a problem.
Sabissimo said:
There you go, found it:
https://drive.google.com/file/d/0B8pGrRdP0CpyckJnd2JoQklHSjQ/
But I have another problem now: It says "Not a valid aboot" and aborts
Click to expand...
Click to collapse
I got it! I used this link 'below' to finally get it to update while using this thread for advice. Thank so much!
http://sbf.droid-developers.org/phone.php?device=5
Now to try saferoot...???
For all my 9.30.1 people, I love you guys too.http://pan.baidu.com/s/1eQimdea
Enjoy that official KK ota for 9.30.1 over that slow ass chinese server and stop trying to get the 9.18.94 to work.
bweN diorD said:
did your phone actually ota to 9.30 or did you use a sbf/utility and flashed it to 9.30?
the problem some people are having is, they flashed to 9.30 but the correct version they should be on is 9.18 and this post http://www.droidrzr.com/index.php/topic/44920-xt926-update-1824610-update/?p=431391 explains why thats a problem.
Click to expand...
Click to collapse
I flashed to 9.30. When I received the OTA from the soak push, I saved the OTA off to the side and didn't apply it immediately. Then, when I attempted to apply it (after using House of Moto to fastboot it back to 9.30 stock), it rebooted after it started applying and then went back to the recovery screen, but at that point, they had changed how you get into it. It's now volume-up + power, not volume-down + volume-up.
In any case, that second step needs to happen where you go back and re-apply the OTA.
I'm thinking if I would have taken the OTA automatically right after it downloaded, it was probably automated. That, or maybe Motorola/Verizon decided to make it a game and see if people could figure it out? :silly:
Safe root for me was a no go. But kitkat is pretty nice!
Sent from my DROID RAZR HD using Tapatalk
Thanks for all the info. Got KK up and running
I used these instructions - http://forum.xda-developers.com/showpost.php?p=52602576&postcount=1
and I used this file - http://forum.xda-developers.com/showpost.php?p=52610188&postcount=11
All last night I tried using the leaked file someone put up from that "slow ass Chinese server" haha. Long story short, it didn't work at all.
This morning I tried again, and nothing. So I tried this file (the one I linked up top) and it worked like a charm. I installed it via recovery, phone rebooted, used vol up + power to get into new KK recovery, applied leaked file again, and boom I got KK.
As someone in another thread said, during the update it does say "Phase 1 possibly complete". WTF is that all about?
I've flashed my Razr Maxx HD to Kitkat using that slow Chinese server. I'm so happy it runs much smoother than JB. Everything seems fast and smooth. The new aosp lockscreen is much better than blur lockscreen. The aosp messaging is also nice. I can live without root for a while coz I already have a Photon Q modding to max. The only thing I dislike is the stock launcher which is not transparent anymore. So,I replace it with Nova Launcher Prime. It looks better now. Btw,I'm using GSM network and I notice signal is better than previous JB.
huatz84 said:
I've flashed my Razr Maxx HD to Kitkat using that slow Chinese server. I'm so happy it runs much smoother than JB. Everything seems fast and smooth. The new aosp lockscreen is much better than blur lockscreen. The aosp messaging is also nice. I can live without root for a while coz I already have a Photon Q modding to max. The only thing I dislike is the stock launcher which is not transparent anymore. So,I replace it with Nova Launcher Prime. It looks better now. Btw,I'm using GSM network and I notice signal is better than previous JB.
Click to expand...
Click to collapse
Glad it's all working for you now. It definitely performs better than JB ever did.

Trying to restore/update PA but unfamiliar with the process

Hi Everyone,
Im using an att LG G2 with Paranoid Android installed; I bought the phone at release I am pretty sure and through att. I believe it to be PA version 3.4 and Android version 4.3.1 from looking af the about phone settings. Basically Ive had this phone on loan to someone for about a year and it is just bogged down with shovelware. Netflix wont even load. I was comfortable playing around with ROMs before but ive been in the Ios scene lately and am out of practice. I have some recoveries but I'm concerned with having not played around on the phone's root for several years now so I'd rather not use something that may be incomplete.
My main concern is having the phone back to its speed from before, getting rid of all of the apps, and starting fresh. Id like to keep PA, hopefully upgrade to the latest version, but if i can just factory reset that works too. I'm pretty sure i could reinstall PA starting from scratch with a clean phone. I've been through the forums different times and I really do find that the info is all consolidated well. I hope I don't come accross as lazy or unwilling to search, I just had a bad experience flashing my Galaxy S2 so whenever I'm not certain on the process I try to consult with people more involved.
Thank you all for your time,
Andrew Rapp
Forgive me but I've had this phone on the shelf for a bit and am seeing now that paranoid Android is relatively dead. That'd be unfortunate since I really dug the interface! But if it really is no longer being supported would anyone have a suggestion on a ROM upgrade? Thanks again!
Cm13 or 12.1 both available with a few variants based on them just give them a whirl.
Sent from my LG-D802 using Tapatalk
Treboeth said:
Cm13 or 12.1 both available with a few variants based on them just give them a whirl.
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
I had CM back on my s2! I could get down with checking it out again. Going through their website is a lot of helpful information, however, most of it seems to be garnered at first time users. I'm using this guide here:
https://wiki.cyanogenmod.org/w/Install_CM_for_d800
and I'm curious if I can skip the first half (installing a custom recovery); because I'm pretty sure I have one installed already from when I flashed PA. How would I go about checking?
Just reboot into recovery to check the version.
But it would be best to update to TWRP 2.8.73 (latest version).
Sent from my LG-D802 using Tapatalk
So once I've updated TWRP (which I do have installed) I can skip that first half and just do the second part? Thanks for the help btw; really trying to bring the phone back to life since I love the screen and size
If you have flashed Roms before you know the rule, read the first post then read it again then read it a third time
Make sure you have the correct bootstack, I suggest the official CM ROM to start with by Drastic then you can always try the others AICP,Bliss,ResurrectionRemix and Crdroid.
I like AICP for the customisations been on it for a couple of days to try out.
Sent from my LG-D802 using Tapatalk
I know, being cautious to a fault here >_< I just ended up using flashify to update twrp; that was easy enough. I'll use the app to make a back up I believe and then try following instructions on the website! Thanks for all your help, hopefully I won't need to return XD but still keeping the topic open just in case!
Nope! I get an error when trying to install the CM zip file. In red it says:
E: Error executing updater binary in zip '/sdcard/cm-12.1-20151117-SNAPSHOT-YOG7DAO1KI-d800.zip'
I was able to get in what appears to be a broken CM installation, which fortunately includes file system exploration and messaging. Accessing the phone from the computer is no problem either. Any idea what the issue here may be?
Bump!
Not sure to be honest,if you have followed the steps in the OP post up in the thread by @drastic and I am sure the more knowledgeable will help you solve the problem.
Sent from my LG-D802 using Tapatalk
I'm sorry, which thread is that?
Totalrapture said:
I'm sorry, which thread is that?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=3264508 Cm13 [emoji6]
Sent from my LG-D802 using Tapatalk
Ahhh thanks! Yeah I'd been doing the 12.1 downloads from the CM site but yeah that process seems to be the same. Could it be possible that my something weird had been done with the person I loaned the phone too? He liked to tinker and I wouldn't put it passed him to have done something funny with it, or even I before having loaned it. Coud the bootstack be an incorrect? Is there a way I could check?
Can you get the phone back to stock Lollipop,if you think he has played around this may be the best option.
Sent from my LG-D802 using Tapatalk
Treboeth said:
Can you get the phone back to stock Lollipop,if you think he has played around this may be the best option.
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
I was thinking that'd be the best option; just to start everything over. Would that process be extensive? I'm on a work computer so I can use recovery and get the files on my phone but anything too complex or needing me to use installers I'll probably have to wait until tomorrow
http://forum.xda-developers.com/showthread.php?t=2432476
Should give you all you need, it could take an hour or two but will give you a fresh start.
Sent from my LG-D802 using Tapatalk
Treboeth said:
http://forum.xda-developers.com/showthread.php?t=2432476
Should give you all you need, it could take an hour or two but will give you a fresh start.
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
Thanks! I'll probably wait until my next day off and then try to run through it all

Stock or root

My X compact is on its way!
Do you guys recommend rooting or keeping stock?
Important to me would be smooth performance, battery and camera.
Thank you
Sent from my SM-G900T using Tapatalk
I recommend rooting the stock!
there is not actually many custom roms for this phone, and stock rom is really good if you just root it
Kianush said:
I recommend rooting the stock!
there is not actually many custom roms for this phone, and stock rom is really good if you just root it
Click to expand...
Click to collapse
Thanks. Once rooted on stock, what changes you recommend?
Sent from my SM-G900T using Tapatalk
Kianush said:
I recommend rooting the stock!
there is not actually many custom roms for this phone, and stock rom is really good if you just root it
Click to expand...
Click to collapse
Paranoid Android team recently added official support for x compact, but I don't know if they have a stable version yet.
You can't get better than rooted stock, custom ROMS always seem to have issues that prevent them from being a full daily driver.
XperienceD said:
You can't get better than rooted stock, custom ROMS always seem to have issues that prevent them from being a full daily driver.
Click to expand...
Click to collapse
Any recommendations for changes to make on stock one rooted? Thanks
Sent from my SM-G900T using Tapatalk
mario24601 said:
Any recommendations for changes to make on stock one rooted? Thanks
Click to expand...
Click to collapse
The usual, debloat, new fonts, theme the system, couple of build.prop edits and that's about it for me.
My 2 cent.
Stock ROM is very good. You *could* root to debloat, but I have preferred to just deactivate the useless app (which are on the /system partition, so that you won't get a real advantage in removing them).
At the moment I don't see a big thing in rooting the device. On the other side, you could loose some interesting feature (e.g., vodafone wallet, or some home banking functions)..
Enjoy your Xc!
mario24601 said:
Thanks. Once rooted on stock, what changes you recommend?
Sent from my SM-G900T using Tapatalk
Click to expand...
Click to collapse
I actually did not change anything except for some build.prop changes
Stock rom is very good as is, I just recommended root so you can use some apps like greenify :good::good:
A very good thing about Xperia devices is the camera, and with a custom rom the camera app is always lacking (unless they can use/steal the stock camera app?)
Otherwise, I don't care about any other Sony apps.
Rooted stock is very good though I'm happy.
If PA has good camera and I can pass safety net, I might switch one day.
Thanks all! I'll look into build prop, to be honest not sure what this does
Sent from my SM-G900T using Tapatalk
I'm in the same boat. Went from a rooted Z1 Compact to the X compact. It seems so tedious to root the X Compact so I haven't done it yet. However I can say I am missing having root, missing Titanium backup etc. We'll see how we go. Hoping for someone to release a guide to root nougat without having to go back to MM.
Mine came with N loaded. It is international version.
I've yet to try it out extensively.
Sent from my SM-G900T using Tapatalk
mario24601 said:
Thanks all! I'll look into build prop, to be honest not sure what this does
Click to expand...
Click to collapse
Don't get too hung up on build.prop mods as a lot of them don't work anymore if they even did in the first place. The only two entries I have in mine are...
Code:
persist.adb.notify=0
fw.show_multiuserui=0

Categories

Resources