Database Develop

[Q] custom rom after applying the "easily update to 5.7.893 and keep webtop"

[Q] custom rom after applying the "easily update to 5.7.893 and keep webtop"
Hey guys new to the bionic and have already done lots of flashing and changing to it. I read the easily update thread so I reverted back to stock using the For3v3r root and applied the update and the webtop mod. After searching through the entire thread all pages no one asked or said anything about whether or not that mod will work if you flash a custom rom.
So my question is...Can I flash a custom rom after and it still work? I specifically like liberty so any help would be fantastic.
Thanks in advanced and I promise I searched and searched for this answer. Please help

I dont really know what you are asking. If you are asking if you can install a custom ROM after updating to 5.7.893, then I would say yes. If you are asking if you had a custom ROM on there first and then tried to upgrade, I would say, yes that should work too, so I guess the answer is "yes".

Thank you for your response. I guess to be more clear is if I am on the stock rom with this webtop mod applied can I go ahead and flash a custom rom without loosing the ability to have the webtop mod?

rkuhldude77 said:
Thank you for your response. I guess to be more clear is if I am on the stock rom with this webtop mod applied can I go ahead and flash a custom rom without loosing the ability to have the webtop mod?
Click to expand...
Click to collapse
Generally any restrictions regarding mods and custom ROMs are contained in the post for the ROM or mod. The 5.7.xxx update is a system update. Think of it as firmware....the under layer. It may come in a Stock package, but if you Flash or mod in any way, you would be impacting only that stock package.....unless the OP posts in the thread.
Many people on other devices, may revert to Stock implementations....to do the OTA....then continue with other flashes like before. Things that are flashed, kernel, baseband, system, radio etc.....all work together with the hardware to deliver your Bionic experience.

That actually makes a lot of sense. I can obviously follow instructions to flash especially when the devs make one click roots and other tools to make it easy for noobs like me, but what you just said made my understanding much better.
Thanks again.

would restoring a nandroid from a 5.893 system be a bad idea?

I actually updated mine with forever root to 5.7.893 then flashed Liberty 1.0 ROM on my phone and its worked great so the answer is definitely yes.

[Q] Just a few questions ;)

What i have done in the last 24 hours:
1. Updated to 4.3 on stock ROM
2. Unlocked bootloader on my Z1
3. Flashed "PhilZ Touch 6" dual bootloader (idk what "dual means" :S) (Dec 3 2013 version)
4. Used the built in root tool in "PhilZ" to root my phone and installed the corresponding app "SuperSU"
Questions:
Does bootloaders come with a custom kernel?
My bootloaders "About" says its made for the "Z" (not Z1). Did i **** up or is this incorrect?
If i flash kernel (for my device) via CWM will i break something?
Does roms require a certain kernel?
Can i flash .img files via CWM or is it required that the file is .zip?
I see kernels on the forum that advertise being 4 kitkat, do i need to flash that kernel WITH a kitkat rom to use that kernel?
Why shuld i flash a kernel?
As CM is not officially supported on the Z1 yet is there a cool alternative rom i can use?
Thats all the Q's i came up with, hope you can help me answer my ridiculous questions and wish me luck on my first android phone! :good:

bump

I won't get my device until tomorrow, but there a few things I could explain:
Some ROMs need to have a specific kernel. You cannot use Stock kernel with Cyanogenmod, or vice versa. Custom kernels are often a good idea to flash if you want some extra optimizations, you can get extra performance and save battery life with an enhanced kernel.
As for an alternative ROM, why don't you just check out the dev forums? There are Cyanogenmod ROMs, they're just unofficial.
Also, did you back up your TA? Otherwise, you'll be in for some real big trouble.

kusanou said:
I won't get my device until tomorrow, but there a few things I could explain:
Some ROMs need to have a specific kernel. You cannot use Stock kernel with Cyanogenmod, or vice versa. Custom kernels are often a good idea to flash if you want some extra optimizations, you can get extra performance and save battery life with an enhanced kernel.
As for an alternative ROM, why don't you just check out the dev forums? There are Cyanogenmod ROMs, they're just unofficial.
Also, did you back up your TA? Otherwise, you'll be in for some real big trouble.
Click to expand...
Click to collapse
****, i did not backup my TA. What does that mean for me?
I read in some threads that TA only gives you the option to revert back to absolute factory defaults. As i am having no problems i dont see why i would do that.
Edit: Thats wierd, my TrackID still works after unlocking bootloader, flashing recovery and rooting. Am i super lucky?

mrzone64 said:
****, i did not backup my TA. What does that mean for me?
I read in some threads that TA only gives you the option to revert back to absolute factory defaults. As i am having no problems i dont see why i would do that.
Edit: Thats wierd, my TrackID still works after unlocking bootloader, flashing recovery and rooting. Am i super lucky?
Click to expand...
Click to collapse
It's mostly needed for Bravia engine stuff, as well as the BIONZ image processor. I guess if you don't care too much about that, and you don't have any reason to have to go back to absolute factory settings in the case of a warranty return, then it should be fine.

[Q] Newbie to Moto X, got some questions. XT1053.

So I finally got me a sweet deal and got a second hand XT1053.
Unlocked its bootloader, then flashed T-Mobile´s 4.4.3 and finally the OTA to 4.4.4, because here in Mexico all I was able to get was 4.4.2.
Now, I want to try custom ROMs, and Ive been reading about the procedure.
As any sane person would, I want a nandroid backup before messing around. Im guessing flashing TWRP will take care of this, like it did with my LG L9, right?
Is it wise to do this on the verge of Android L being ported to our Moto X?
How difficult is it to get the phone to a fully stock state (minus the bootlader, of course)? As far as I know, I only need to flash my nandroid backup then flash the stock recovery. Is it as simple as that?
I read somewhere that flashing custom ROMs messed up with Motorola´s active display/voice control, and I assumed they meant that custom ROMs lacked these features because of their proprietary nature. Am I correct? Or does some kind of unrepairable damage will forever afflict these features, even if I get back to stock?
And lastly, what ROM do you recommend? I´d like the active display feature if possible, guess I can do without it. CM theme chooser would be nice too.
Thanks in advance, eagerly awaiting some answers before I take a step forwards.
Attached a screenshot of my phone´s info.

You are right about everything you've mentioned. Good research done for sure! ?
Do a backup with twrp. And yes, you can restore it and flash the stock recovery and you're good for the OTA.
Aosp/cm roms don't have the Moto features. But yes, you can return to stock and have them again. There's a few stick based custom roms that of course still have the features. The other roms, unless something changed, do come with some bugs unfortunately as well.
Most use stock, with gravity box for customizing.
And in case you missed it.... Never try to downgrade from 4.4.4....or you risk your device bricking. You can flash lower version custom roms, cause they won't try to change the bootloader. But don't downgrade stock firmware. Ever. ?
Enjoy!

Thank you very much!
As soon as I read this I rooted my phone, I´ll check a ROM or two before settling on one for daily use, have heard nice things about krypto´s one.
And yeah, there can never be enough warnings, I´ll treat the T-Mobile stock ROM as if it were my very first one.
One question though, the latest version of T-Mobile firmware is 4.4.3 under http://sbf.droid-developers.org/phone.php?device=0 so Im gussing I should only use my nandroid backup, right?
Thanks in advance!

no_un_bot said:
Thank you very much!
As soon as I read this I rooted my phone, I´ll check a ROM or two before settling on one for daily use, have heard nice things about krypto´s one.
And yeah, there can never be enough warnings, I´ll treat the T-Mobile stock ROM as if it were my very first one.
One question though, the latest version of T-Mobile firmware is 4.4.3 under http://sbf.droid-developers.org/phone.php?device=0 so Im gussing I should only use my nandroid backup, right?
Thanks in advance!
Click to expand...
Click to collapse
Until there's a 4.4.4 SBF, yes. That's the safest bet.

newbie needs details
no_un_bot said:
So I finally got me a sweet deal and got a second hand XT1053.
Unlocked its bootloader, then flashed T-Mobile´s 4.4.3 and finally the OTA to 4.4.4, because here in Mexico all I was able to get was 4.4.2.
Now, I want to try custom ROMs, and Ive been reading about the procedure.
As any sane person would, I want a nandroid backup before messing around. Im guessing flashing TWRP will take care of this, like it did with my LG L9, right?
Is it wise to do this on the verge of Android L being ported to our Moto X?
How difficult is it to get the phone to a fully stock state (minus the bootlader, of course)? As far as I know, I only need to flash my nandroid backup then flash the stock recovery. Is it as simple as that?
I read somewhere that flashing custom ROMs messed up with Motorola´s active display/voice control, and I assumed they meant that custom ROMs lacked these features because of their proprietary nature. Am I correct? Or does some kind of unrepairable damage will forever afflict these features, even if I get back to stock?
And lastly, what ROM do you recommend? I´d like the active display feature if possible, guess I can do without it. CM theme chooser would be nice too.
Thanks in advance, eagerly awaiting some answers before I take a step forwards.
Attached a screenshot of my phone´s info.
Click to expand...
Click to collapse
hello, i a newbie to all of this
i have the same device as yours, how did you do that? details if it not much trouble

sherif2015 said:
hello, i a newbie to all of this
i have the same device as yours, how did you do that? details if it not much trouble
Click to expand...
Click to collapse
Hi there, Im at work and cannot explain in much detail, but when I get home i will help you out.
You can send me a private message if you want me to explain in español.

no_un_bot said:
Thank you very much!
As soon as I read this I rooted my phone, I´ll check a ROM or two before settling on one for daily use, have heard nice things about krypto´s one.
And yeah, there can never be enough warnings, I´ll treat the T-Mobile stock ROM as if it were my very first one.
One question though, the latest version of T-Mobile firmware is 4.4.3 under http://sbf.droid-developers.org/phone.php?device=0 so Im gussing I should only use my nandroid backup, right?
Thanks in advance!
Click to expand...
Click to collapse
SBF.Droid-Developers.org hasn't been updated in a while, at least as far as the X (2013 or 1st Gen edition) Roms.
Another possible source is -> http://www.filefactory.com/folder/dd05c058d3ff8dbe/?sort=created&order=DESC&show=100&page=1 however, they don't have a 4.4.4 SBF for the XT1053 either.
And you can keep an eye on https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images since Moto should post the 4.4.4 SBF for the Developer Editions. Eventually an XT1053 (GSM) and an XT1060(VZW) 4.4.4 should pop up there, whenever Moto finally gets around to it.

no_un_bot said:
Hi there, Im at work and cannot explain in much detail, but when I get home i will help you out.
You can send me a private message if you want me to explain in español.
Click to expand...
Click to collapse
Hi sorry for bothering you but i really need your help.
English will be fine .
other users might get here so it will be nice to help them as well
thanks for your time

sherif2015 said:
Hi sorry for bothering you but i really need your help.
English will be fine .
other users might get here so it will be nice to help them as well
thanks for your time
Click to expand...
Click to collapse
Alright, guess everything is out there but I don´t mind.
Can you tell me what system version have you got?
Its displayed under Settings > About phone

reply
no_un_bot said:
Alright, guess everything is out there but I don´t mind.
Can you tell me what system version have you got?
Its displayed under Settings > About phone
Click to expand...
Click to collapse
Kitkat 4.4.2 xt1053

same phone, problems loading roms
I have the same phone, I also recently got second hand.
Moto x xt1053 (gsm) carrier unlocked, currently in kitkat4.4.2, running Kangakat 2 rom (came with it), unlocked bootloader, rooted and using SuperSU, newest version of twrp like 2.8 or something like that.
I want to load a custom rom but am having problems, downloaded P.A.C. and AOKP (two i have tried to use) for the device msm8960 using there stable versions not the nightlies. Went into twrp, created backup, factory wiped, flashed rom and g-apps, was "successful" no errors but on reboot of phone it gets stuck in boot loop and won't start up. for the P.A.C i was able to get into twrp and reflash my back up, for the AOKP twrp kept getting stuck on that teamwin image and i could only finally access it by having the usb cable plugged into my computer. I am not a noob, but definately not an expert.
So did you have any luck flashing a new rom to your phone? Does anyone have any advice for me? I really would like to try some different roms.
Thanks

[emoji15]

I hate Tapatalk for all the time spent writing a quick reply and its gone.
Anyways, first of all, make sure you have the latest recovery available, I remember back with my old phone, funky installations happened if you weren't on the latest recovery. I recommend philz one, has support for some pesky partitions that sometimes get messed and other recoveries won't back up.
Now, in my particular case, I first upgraded my 4.4.2 Nextel stock to 4.4.3 T-Mobile stock using RSDLite, then took the OTA to 4.4.4, and until then I figured I'd play with ROMs. Have had no issues other than something I've addressed on another thread and I ultimately fixed.
My suggestion is going back to full stock then doing everything yourself so you know what's actually going on.
You'll have to flash a custom recovery and then root it again but with an unlocked bootloader that's ezpz.
Remember never to downgrade (that is, flashing a lower android version than what you currently run) stock official images (such as the ones from sbf-developers) because you WILL brick your phone. People say you can downgrade when flashing custom ROMs but I wouldn't risk it, and I don't really see why I'd want that.
Double check whatever file you'll try to flash, always use stuff intended for your model, and when that's not possible verify if other users with your model have reported it works for them. As per the version thing, I believe the most recent development unified models under the GHOST parameter but take my words for what they are, that is, my view on things, you should always make one for yourself.
Ask if you don't completely understand a step BEFORE doing it, there's good people willing to help you out.
Best of luck.

[Q] Upgrading Viper ROM, need to update to 4.4.3. Is this how to do it?

So I have an older version of Viper ROM on 4.4.2, and I want to latest version of Viper ROM. From my understanding, it works better when you have 4.4.3, so I need to upgrade to that first. So, what do I need to do? Revert to stock, update OTA, and then re-root, get TWRP again, and then reflash to the new version of Viper ROM? I really hope that's wrong, but I don't even care what I have to do if I can just get a clear understanding of what it is I need to do.
I'm pretty annoyed that Viper ROM offers no support when it comes to updating, but when you search elsewhere on xda for this information it's very hard to find. I've installed custom firmware on phones about 5 times in the past 5 or so years, and I've never come close to having such a hard time at finding basic instructions. Every time aside from the first I haven't been able to fully remember the process, but had no issues like I'm having now when it comes to finding guides.

jaluke said:
So I have an older version of Viper ROM on 4.4.2, and I want to latest version of Viper ROM. From my understanding, it works better when you have 4.4.3, so I need to upgrade to that first. So, what do I need to do? Revert to stock, update OTA, and then re-root, get TWRP again, and then reflash to the new version of Viper ROM? I really hope that's wrong, but I don't even care what I have to do if I can just get a clear understanding of what it is I need to do.
I'm pretty annoyed that Viper ROM offers no support when it comes to updating, but when you search elsewhere on xda for this information it's very hard to find. I've installed custom firmware on phones about 5 times in the past 5 or so years, and I've never come close to having such a hard time at finding basic instructions. Every time aside from the first I haven't been able to fully remember the process, but had no issues like I'm having now when it comes to finding guides.
Click to expand...
Click to collapse
if you are s-off it's pretty easy: http://forum.xda-developers.com/showthread.php?t=2365506 (in the firmware section), and note that the "fastboot flash zip <firmware>.zip" has to be done twice!!

Nexus 6 Help

Hi I have a few questions for my nexus 6 that I am getting today
1) I am going to flash a the new marshmallow update, which one should I pick because for root you need a specific build but on the google factory images the latest build is not supported? I really don't know.
2) After I flash 6.0 can I just do the fastboot flash recovery twrp.img without flashing the boot.img
3) When I go to a new rom like Chroma by Zephik do I still need to change the boot.img to flash the beta super user
For now these are all my questions and I would really appreciate if you could answer it.
side note: I cannot use NRT becuase I am on a mac, if you guys have any alternatives I would really appreciate it too.

1) Flash any of them, they are all rootable. I would recommend going with the latest one. Unless I am mistaken, I believe K, N, and R each have the same radio so there effectively would be no real difference in the end result, as a custom ROM will overwrite everything else.
2) Yes, there is no need to have a modified boot image or root if you plan on flashing a custom ROM.
3) This depends on the ROM, they should have instructions in their post as to what they require. I am pretty sure Chroma comes with a custom kernel already, and I believe it comes pre-rooted as well. It could be that you have to root the ROM after you flash it if you want root though, there are some ROMs that are like that. The OP should have installation instructions.
As for your side note, I don't recommend using a toolkit of any sort. I recommend learning how to use fastboot, and doing it manually. That way if you were to need to fix something in the future, you would have a general understanding of what you did and why, and perhaps that will help you in how to fix it. Rather than clicking a couple buttons in a toolkit. Also, toolkits can fail, and not tell you why. It is often hard to figure out what went wrong when it is doing multiple steps at once, rather than one at a time like if you were to do it the manual way. It really isn't that difficult, and it is very well documented process at this point with tons of guides with pictures and even videos out there.

cupfulloflol said:
1) Flash any of them, they are all rootable. I would recommend going with the latest one. Unless I am mistaken, I believe K, N, and R each have the same radio so there effectively would be no real difference in the end result, as a custom ROM will overwrite everything else.
2) Yes, there is no need to have a modified boot image or root if you plan on flashing a custom ROM.
3) This depends on the ROM, they should have instructions in their post as to what they require. I am pretty sure Chroma comes with a custom kernel already, and I believe it comes pre-rooted as well. It could be that you have to root the ROM after you flash it if you want root though, there are some ROMs that are like that. The OP should have installation instructions.
As for your side note, I don't recommend using a toolkit of any sort. I recommend learning how to use fastboot, and doing it manually. That way if you were to need to fix something in the future, you would have a general understanding of what you did and why, and perhaps that will help you in how to fix it. Rather than clicking a couple buttons in a toolkit. Also, toolkits can fail, and not tell you why. It is often hard to figure out what went wrong when it is doing multiple steps at once, rather than one at a time like if you were to do it the manual way. It really isn't that difficult, and it is very well documented process at this point with tons of guides with pictures and even videos out there.
Click to expand...
Click to collapse
Thanks so much, I actually used adb/fastboot when I was rooting my mytouch 4g so this knowledge should come in handy, one other question if I were to root the latest factory image can I use the MRA58K.img that Chainfire posted for 6.0 or do I have to find a modified boot img that matches the latest factory image which is MRA58R, thank you so much again