Database Info

[Q] Droid 2 Global Roms

I'm new to rooting and just rooted my Droid 2 Global and have no idea what to do next. Where do I find roms? What are the best ones? And how can I get rid of some of this junk moto has on here?

Google team defuse
Sent from my DROID2 GLOBAL using XDA App

I'm sorta new to this too. I rooted with Z4Root. I'd recommend going to the market and downloading Root Uninstaller. That helped me get rid of all the stupid crap verizon put on there, like Blockbuster, Kindle, CityID, etc.
Another thing you could do is look up "root" in the market. It will show you all the apps that require root access.
Becareful though, just like your home computer, uninstalling some software may have unintended consequences. Hope that helps.

marcort said:
I'm sorta new to this too. I rooted with Z4Root. I'd recommend going to the market and downloading Root Uninstaller. That helped me get rid of all the stupid crap verizon put on there, like Blockbuster, Kindle, CityID, etc.
Another thing you could do is look up "root" in the market. It will show you all the apps that require root access.
Becareful though, just like your home computer, uninstalling some software may have unintended consequences. Hope that helps.
Click to expand...
Click to collapse
Thanks a lot. Has anything you uninstalled caused you problems?

Not yet. But I only uninstalled the factory installed extra stuff. I noticed a slight pickup in speed and battery life (although it could just all be in my head... LOL). Let me know if you do anything else cool. Im still trying to build up enough balls to actually start flashing roms.

marcort said:
I'm sorta new to this too. I rooted with Z4Root. I'd recommend going to the market and downloading Root Uninstaller. That helped me get rid of all the stupid crap verizon put on there, like Blockbuster, Kindle, CityID, etc.
Another thing you could do is look up "root" in the market. It will show you all the apps that require root access.
Becareful though, just like your home computer, uninstalling some software may have unintended consequences. Hope that helps.
Click to expand...
Click to collapse
This is a bad idea, don't do it.
When you delete the bloatware that comes on the phone, you make your phone unable to receive OTA updates from Verizon. This includes any future updates to Android version 2.3 (Gingerbread). The updates run as a patch, they check for all of the system data to be present. This includes pre-installed apps like blockbuster, amazon, etc. If ALL of the system data isn't present, the patch can't run.
Instead, you should use Titanium Backup to freeze these programs. It does the same thing, but instead of removing the files, it changes their extension, so that they can't run. It has the same effect, but when you want an update, you just unfreeze your programs, update, and then refreeze them. It also lets you make backups of your apps and app data.
If you don't want to pay for TiBu, you can always manually change all the filenames from cityID.apk to cityID.bak, etc etc. This does the same thing, for free, but is more involved and less beginner friendly.

Do what ever you want......if you want to go back to stock to get offical ota updates just search for the sbf file and your all good. Just know what your doing before you do it. If you delete bloatware it will effect ota updates. But flash the sbf with rsd lite and you'll be fine
Sent from my DROID2 GLOBAL using XDA App

You could do that, yes. But freezing bloatware is more efficient. Flashing an SBF is more time intensive, and has a higher chance (not high, mind you, but highER) of not working correctly. Also, TiBU has the added benefit of being a backup utility that's easy to use and very functional and stable.

Ok.
Sent from my DROID2 GLOBAL using XDA App

Well I guess that shows how much of a dummy I am with this stuff. I ended up reinstalling the stuff I removed from the market and unrooting because I had to send the phone back. It had a really weird charging issue that was present when I bought it. Im on the new one now. (Rooted to try and fix the charging issue. It didnt work). I haven't rooted the new phone yet. Im reading through all the forums to try and gain a little better understanding of how to do this stuff without wrecking my phone or missing out on updates. Thanks for all the good info! I wont be screwing around with bloatware so soon this time.

Definitly do not go the uninstall route on the Blur stuff.
Freezing is better!
As for ROMs there is only one ROM that I know of and it is Fission.
Get the ROM manager here at XDA and flashing it is a snap. It even has the Stock Droid in the manager so you can easily go back to stock when needed.

The stock rom in the rom manger still has root, busybox and is deodexed. If sent back with these programs on it will void your warranty. So if you ever need to send back sbf 1st to be safe. The .sbf takes like 15 minutes. Maybe two minutes more then flashing a ROM. So I really don't get how flashing a .sbf is difficult. And it actually is the safest due to the locked bootlader and the drivers usually never fail if running Windows 32 bit.

so i'm assuming that all of the other "popular" ROM's (liberty, rubix, apex, etc.) that say they are for the DX and D2 wont work on the D2G? I've installed many ROM's on my D2G and all of them get stuck on airplane mode and wont unlock. I end up having to restore and revert back to stock...

Yep, pretty lame that all these devs havent taken numerous peoples' offers to test out d2g ports of the d2 roms. i mean i have no idea how to port it myself but theres people saying "if you try it, ill test it" and still no devs take anyone up on the offer.

So does ne one think that we are going to get ne roms ported over to us from the dx or the d2 cuz I was lookin forward to flashing liberty to my D2G so can some1 pm if they got ne idea or if they kno when we can expect a new rom
Sent from my DROID2 GLOBAL using XDA App

D2G Rooting
Hey Guys- I just rooted and installed Fission ROM on my D2G- WHEW!! My wife (the IT pro) and I rooted this past Sunday evening. We used Z4ROOT- this part was fairly easy. Then we spent the next 6 hours- with no luck whatsoever- trying to install a custom ROM. We finally found out that there aren't many out for the D2G just yet.
We finally found Fission ROM, but could not get it installed. You must have a bootstrap program to install the rom. I found this out by accident. Finally installed Fission on Tuesday night. Only used for a few hours, but so far so good.
BTW- there are several bloatware freezers on the market. I had read not to remove it, so I froze it. App Freezer for Root seems to be working fine.
Be careful, and good luck!

biknut1 said:
We finally found Fission ROM, but could not get it installed. You must have a bootstrap program to install the rom. I found this out by accident. Finally installed Fission on Tuesday night. Only used for a few hours, but so far so good.
Click to expand...
Click to collapse
There are instructions with everything you need to know (including koush's bootstrap) provided by team defuse on their website. The entire process shouldn't take more than 30 minutes tops.
And you can delete anything you want now that there is the D2 global SBF for recovery. Just make sure you know how to use it before things go awry so you don't panic and flood the forums with questions that have already been answered.
Sent from my DROID2 using XDA App

pfallin said:
so i'm assuming that all of the other "popular" ROM's (liberty, rubix, apex, etc.) that say they are for the DX and D2 wont work on the D2G? I've installed many ROM's on my D2G and all of them get stuck on airplane mode and wont unlock. I end up having to restore and revert back to stock...
Click to expand...
Click to collapse
how do you revert back to stock. yes i made a backup.

How do you get the OTA Update? I mean, you have to be on Verizon to get it, right? What if you unlocked the phone and use it outside the US with a different sim card from some other carrier? Can you still get the update? Please help.
And, if somehow I can find this precious update, then if I change my rom to Fission, I won't get updates anymore, right? Then what is the point of getting new roms? I'll have to be checking for newer roms with newer updates from Verizon all the time? Is this the idea?
Thank you,

hgrimberg said:
How do you get the OTA Update? I mean, you have to be on Verizon to get it, right? What if you unlocked the phone and use it outside the US with a different sim card from some other carrier? Can you still get the update? Please help.
And, if somehow I can find this precious update, then if I change my rom to Fission, I won't get updates anymore, right? Then what is the point of getting new roms? I'll have to be checking for newer roms with newer updates from Verizon all the time? Is this the idea?
Thank you,
Click to expand...
Click to collapse
Yes, you can get the update, no matter you are not on Verizon network. But update will not be 'pushed' to you, you have to go to system/about phone/system updates. Phone will check for update and let you know if one is available. If you are already running 2.4.330, you will get prompt no update is available. If you are on 2.4.29 - you must get the prompt update is available and will be downloaded.
Update will work only if you are using stock firmware (for me it worked fine no matter I had rooted the phone, you must make sure there are no 'frozen' apps before update is applied, or it will fail to install). On Fission, it will not show/work. Many users, including myself, have reported update does not seem to be adding anything benneficial to users on GSM/UMTS networks. On some networks (in Canada and Australia so far) update causes the phone to become unreliable when it comes to keeping connection to the cellular network. Another user (in Germany) reports no problems using the updated firmware. I suspect this is related to frequencies - in Canada and Australia we use bands that overlap with US bands which as we all know have some software restrictions imposed by the phone. In Europe (Germany, Greece) you guys use 2100Mhz.
Again - update addresses some CDMA issues, I find absolutely no different with/without the update in terms of battery life or call quality. (I am on Rogers Canada - GSM/HSPA 850/1900.)

[stock firmware][D80020c] recovery friendly D80020c

This is for D800 (AT&T LG G2) users ONLY.
This package will update a phone with D80010d firmware to a "mixed" firmware that boots normally to D80020c (kitkat), but retains the older boot loader and compatibility with loki patched custom recoveries. The "normal" boot is 100% unmodified stock.
This "mixed" firmware is currently the only known way for a stock D80020c (kitkat) system that also allows custom recovery.
What's installed:
rpm, tz, modem, and system partitions from the stock D80020c (kitkat) LG G2 firmware.
LG's D80020c kernel, recompiled by @Savoca, and made compatible with the D80010d bootloader.
That will leave your existing D80010d boot loader (aboot) intact, as well as whatever custom recovery already installed.
This firmware package will (or at least should) refuse to install on ANY firmware other than the D80010d firmware. Please don't reply to this thread if you are using anything else. (That was as polite as I'll be on that issue...)
I STRONGLY suggest doing a full wipe on your device after flashing this. You don't have to, but it'd be a really good idea...
This is NOT my software. This is 100% LG's software and firmware. Don't ask for support in this thread. It won't be provided.
Instructions:
Restore your phone to the stock LG G2 D80010d firmware. Please click "here" for directions. (remember that you have the AT&T device when reading that post...) If you don't like that post, here's a youtube video (not mine) for doing the same thing. Make sure you restore the D80010d firmware and _not_ the D80010o firmware!!
Root the device and install recovery (recovery is required, root is not.) This is a link for rooting instructions. While you are welcome to use CWM for your recovery, this is a link for installing TWRP recovery. (Since cyanogenMod took freely given contributions to their codebasse and went private/for-profit, I have a personal bias against them - so my personal recommendation is for TWRP.)
Copy the d80010d_to_20c.zip package linked below to your phone.
Reboot into recovery and install the d800_to_20c.zip package.
Optionally, also install a superSU or other root package.
Optionally, but suggested, Perform a "factory reset" on your device.
Download Links:
The main package (about 1.7GB): Dev-Host (md5: 7cfe7de4ab31f727b72178b8fb618fd3)
SuperSU: Direct from Chainfire's webpage
Credits:
Several people spent countless hours working on finding a way to get recovery working with LG's kitkat. The kernel used in this package was made by @Savoca - who used the solution found by @JackpotClavin. Others involved are (as far as I'm aware) @AndroidUser00110001 and @jakew02. Of course, @Chainfire for the 'su' package.
Source:
All the images in the recovery package are completely stock with the exception of the kernel and kernel modules. The kernel is modified and recompiled with only the following patch: https://github.com/JackpotClavin/an...mmit/7b6187a0e5fb8ca59888cacf5f5b863baa8d1064. (The installer overwrites the kernel images in /system with those from the kernel compile.) The base kernel source is found on LG's opensource website under the D800 heading.
May 2014 Update:
I'm no longer able to tinker with my G2. My wife took it from me (for her own use), and she gets angry when I mess up all her settings.
(I ended up getting a HTC One M8 to tinker with.)
While I'll leave the thread unlocked so users can assist each other, please don't expect prompt responses from me or maintenance.

switched main package link to dev-host
added "source" section.

As soon as it's done downloading I will let you know that it works unless someone beats me to it that is
EDIT: Finally finished downloading I already flshed back to 10d rooted installed recovery and am now installing kk.zip
Re-Edit: just finished installing also just so you know flashing system only took about 2mins a little bit over that in terms of seconds anyways everything seems to be running fine ill report back tomorrow when its not 1am my time and can test things more thoroughly but I can confirm that everything flashes like its supposed to and also I like the little check you added where it says d80010d bootloader good!
Sent from my LG-D800 using xda app-developers app

XxZombiePikachu said:
... and also I like the little check you added where it says d80010d bootloader good!
Click to expand...
Click to collapse
It's actually checking that loki_patch reports a d80010d bootloader. If not, it'll abort flashing.

Thanks man, now i have kitkat with root and recovery (D80020c)

Damn I wish I had waited for this before flashing kit Kat last week. Of will I'll just have to wait on a recovery compatible with kit Kat or go back to 4.2.2 and then flash this when I have time.
>^·^< Sent From MEOW G2

DowntownJeffBrown said:
Damn I wish I had waited for this before flashing kit Kat last week. Of will I'll just have to wait on a recovery compatible with kit Kat or go back to 4.2.2 and then flash this when I have time.
>^·^< Sent From MEOW G2
Click to expand...
Click to collapse
This is the only way for now to have a recovery on kit Kat
Sent from my LG-D800 using XDA Premium 4 mobile app

Okay, so let me get this straight before I do anything. I'm currently running a custom rom right now, do I still need to revert to stock and install a custom recovery again, or can I just copy the stock kitkat zip to my phone and install from my current recovery?

FlyingColors said:
Okay, so let me get this straight before I do anything. I'm currently running a custom rom right now, do I still need to revert to stock and install a custom recovery again, or can I just copy the stock kitkat zip to my phone and install from my current recovery?
Click to expand...
Click to collapse
What is step #1 on the instructions?
You can do whatever you want with your phone. It won't impact me whatsoever. However, that has nothing to do with what I posted.

Sigh...on every single KitKat Stock ROM ive tried so far...Bluetooth kills the battery, i mean it massacres it. I really dont get what the issue is...some sort of wakelock?

garyd9 said:
What is step #1 on the instructions?
You can do whatever you want with your phone. It won't impact me whatsoever. However, that has nothing to do with what I posted.
Click to expand...
Click to collapse
I'm just trying to get some clarification so I don't have to go out and spend $400 on a new phone.
Would you rather be unaware of what your doing and then break your phone or be cautious and ask a question to the man in charge even if it makes you look like an idiot. I thought so...sorry for wasting your time.

FlyingColors said:
I'm just trying to get some clarification so I don't have to go out and spend $400 on a new phone.
Would you rather be unaware of what your doing and then break your phone or be cautious and ask a question to the man in charge even if it makes you look like an idiot. I thought so...sorry for wasting your time.
Click to expand...
Click to collapse
It clearly says on step #1-
Instructions:
1. Restore your phone to the stock LG G2 D80010d firmware. Please click "here" for directions. (remember that you have the AT&T device when reading that post...) If you don't like that post, here's a youtube video (not mine) for doing the same thing. Make sure you restore the D80010d firmware and _not_ the D80010o firmware!!
So obviously the first step is to flash back to 10d it cannot get any simpler than that
Sent from my LG-D800 using XDA Premium 4 mobile app

XxZombiePikachu said:
It clearly says on step #1-
Instructions:
1. Restore your phone to the stock LG G2 D80010d firmware. Please click "here" for directions. (remember that you have the AT&T device when reading that post...) If you don't like that post, here's a youtube video (not mine) for doing the same thing. Make sure you restore the D80010d firmware and _not_ the D80010o firmware!!
So obviously the first step is to flash back to 10d it cannot get any simpler than that
Sent from my LG-D800 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
more people asking questions that have already been answered. then when you point out that their question has already been answered they say they are trying to clarify even though it's already been clarified in the OP. it's a phenomenon on xda.

xLordNitro said:
Sigh...on every single KitKat Stock ROM ive tried so far...Bluetooth kills the battery, i mean it massacres it. I really dont get what the issue is...some sort of wakelock?
Click to expand...
Click to collapse
I've seen that people have reported that issue on the D802, but I have to admit that I haven't seen the issue whatsoever on the my own D800. I have bluetooth on 100% of the time, and connected twice a day (on my commute to work and my commute back - each about 45 minutes.) My battery on 4.4.2 is about the same as what it was on 4.2.2 - however, "bluetooth" does show up higher on the battery app list of what is using power. Yet, it doesn't seem to have any real impact on overall battery life.
What are you basing the statement that BT is killing the battery on? Some of those OEM batter apps (like the LG one and even the android built-in one) are often misleading. For example, at least with 4.2.2, my phone wouldn't show "pandora" as a battery user (instead blaming 'android system.)
Of course, it's also possible that, for your environment, something really is causing BT to use up more battery than it should. There are several services related to BT, including the newer GATT/ATT (not related to AT&T) calls. (They are related to low power profiles.) It's possible that *something* in your environment is interacting with the phone or one of those services in such a way to cause issue... I'd suggest getting betterBatteryStats, install the piece needed for it to work properly with kitkat, and getting more detailed information from that. (When I say "environment", I mean the physical space around you, the software on your phone, or anything that may influence RF, light, sound, etc around your phone.)
FlyingColors said:
I'm just trying to get some clarification so I don't have to go out and spend $400 on a new phone.
Click to expand...
Click to collapse
...and I'm trying to give EXTREMELY clear and detailed instructions so that people don't have to replace their phone. In fact, my instructions take a paranoid approach.
However, your question is essentially asking if you could skip steps. Does a "cautious" person skip steps?
Well, you can - assuming you know EXACTLY which partitions are installed on your phone, EXACTLY where they came from, EXACTLY what version they are, and you are 100% sure that they all match what is required. Of course, if you already had all that information, then you wouldn't feel the need to ask the question, as you'd obviously be "geeky" enough to not even really need a recovery package to install it.
Don't come into this thread asking if you can skip steps and then say you want to protect the investment in your phone. As well, don't get an attitude with me if I don't put my entire life on hold, and spell out to you the very same directions that are on the first post on this thread. Don't want to follow them? Fine. Don't. Honestly, I could NOT care less what happens to your phone if you don't want to follow the instructions I typed out.
You can read. I know this, as your question was in the context of the thread. Are you one of those people who will install kitkat, won't bother to "factory reset" the phone, and then complain that things don't work properly?
Edit: On second thought, FlyingColors, please don't install the package from this post. I get no benefit if you do, but you've already been a burden. I'd rather you continue to use whatever "custom rom" you are using. It's obviously something you are happy with (as you don't want to restore your phone to stock), and I don't have the patience to answer questions when I've already taken the time to give the answers.
By the way, as you want "clarification": It's not a "rom." It's not even a "ROM." At best, it's "firmware." If it was "ROM", you wouldn't be able to change it. Read Only Memory.

garyd9 said:
I've seen that people have reported that issue on the D802, but I have to admit that I haven't seen the issue whatsoever on the my own D800. I have bluetooth on 100% of the time, and connected twice a day (on my commute to work and my commute back - each about 45 minutes.) My battery on 4.4.2 is about the same as what it was on 4.2.2 - however, "bluetooth" does show up higher on the battery app list of what is using power. Yet, it doesn't seem to have any real impact on overall battery life.
What are you basing the statement that BT is killing the battery on? Some of those OEM batter apps (like the LG one and even the android built-in one) are often misleading. For example, at least with 4.2.2, my phone wouldn't show "pandora" as a battery user (instead blaming 'android system.)
Of course, it's also possible that, for your environment, something really is causing BT to use up more battery than it should. There are several services related to BT, including the newer GATT/ATT (not related to AT&T) calls. (They are related to low power profiles.) It's possible that *something* in your environment is interacting with the phone or one of those services in such a way to cause issue... I'd suggest getting betterBatteryStats, install the piece needed for it to work properly with kitkat, and getting more detailed information from that. (When I say "environment", I mean the physical space around you, the software on your phone, or anything that may influence RF, light, sound, etc around your phone.)
Well i had this problem even when i had apps installed on a different Stock KITKAT rom created by someone. I DID NOT have this problem on the official OTA from AT&T, or on the PowerUser KitKat ROM but that had so many things missing that ireally did enjoy, maybe ill download the pack with the removed apps. So i decided to rewipe everything, ReFlash stock Jellybean and reroot and do everything all over again and then i flashed this, same problem. Bluetooth is completely off, i rarely use it. It went from 100%-60% within 1 hour of just standby, didnt even use the phone. Look at the stats and Bluetooth has been keeping the CPU awake the whole time. So i did what someone suggested, turned it on and off and rebooted. Same problem. Went back to JB, no issues.
Click to expand...
Click to collapse

xLordNitro said:
I've seen that people have reported that issue on the D802, but I have to admit that I haven't seen the issue whatsoever on the my own D800. I have bluetooth on 100% of the time, and connected twice a day (on my commute to work and my commute back - each about 45 minutes.) My battery on 4.4.2 is about the same as what it was on 4.2.2 - however, "bluetooth" does show up higher on the battery app list of what is using power. Yet, it doesn't seem to have any real impact on overall battery life.
What are you basing the statement that BT is killing the battery on? Some of those OEM batter apps (like the LG one and even the android built-in one) are often misleading. For example, at least with 4.2.2, my phone wouldn't show "pandora" as a battery user (instead blaming 'android system.)
Of course, it's also possible that, for your environment, something really is causing BT to use up more battery than it should. There are several services related to BT, including the newer GATT/ATT (not related to AT&T) calls. (They are related to low power profiles.) It's possible that *something* in your environment is interacting with the phone or one of those services in such a way to cause issue... I'd suggest getting betterBatteryStats, install the piece needed for it to work properly with kitkat, and getting more detailed information from that. (When I say "environment", I mean the physical space around you, the software on your phone, or anything that may influence RF, light, sound, etc around your phone.)
Well i had this problem even when i had apps installed on a different Stock KITKAT rom created by someone. I DID NOT have this problem on the official OTA from AT&T, or on the PowerUser KitKat ROM but that had so many things missing that ireally did enjoy, maybe ill download the pack with the removed apps. So i decided to rewipe everything, ReFlash stock Jellybean and reroot and do everything all over again and then i flashed this, same problem. Bluetooth is completely off, i rarely use it. It went from 100%-60% within 1 hour of just standby, didnt even use the phone. Look at the stats and Bluetooth has been keeping the CPU awake the whole time. So i did what someone suggested, turned it on and off and rebooted. Same problem. Went back to JB, no issues.
Click to expand...
Click to collapse
after you went back to jb then rooted and installed custom recovery then flashed this firmware, did you do a factory reset upon first boot? meaning did you get past the initial set up then go to settings/backup and restore and reset the phone? if not then that could be your problem. the factory reset does indeed reset everything after you initially install kitkat. it worked for me also, i had mms issues every time i initially installed kk. after a factory reset the mms is resolved.

Yep, did that. Still same problem. So im assuming its something to do with the files themselves, and maybe the fixes that are being done to keep recovery. I dont know. But im back on Jellybean for now, i cant let my battery take that huge a hit.

xLordNitro said:
Well i had this problem even when i had apps installed on a different Stock KITKAT rom created by someone. I DID NOT have this problem on the official OTA from AT&T, or on the PowerUser KitKat ROM but that had so many things missing that ireally did enjoy, maybe ill download the pack with the removed apps. ... . It went from 100%-60% within 1 hour of just standby, didnt even use the phone.
Click to expand...
Click to collapse
Wow. That's REALLY strange. I wonder why it's impacting only some users, and not all. (It would make sense that if it happens when BT is turned off, it would impact 100% of users.) Something else that's odd is that it happens with this, but not with the OTA. Even more strange is that it happens with that other "stock kitkat" firmware, as that essentially is the OTA with zero changes - it's even using the OTA provided bootloader and kernel.
I'm not really sure how to guide you on troubleshooting this. Anything I might suggest would take a few days of reverting and flashing various things, and I somehow doubt you'd want to spend the rest of your life doing random experiments for me. Perhaps you should try that poweruser firmware with things added one at a time - as you suggested.
Take care
Gary

garyd9 said:
I've seen that people have reported that issue on the D802, but I have to admit that I haven't seen the issue whatsoever on the my own D800. I have bluetooth on 100% of the time, and connected twice a day (on my commute to work and my commute back - each about 45 minutes.) My battery on 4.4.2 is about the same as what it was on 4.2.2 - however, "bluetooth" does show up higher on the battery app list of what is using power. Yet, it doesn't seem to have any real impact on overall battery life.
What are you basing the statement that BT is killing the battery on? Some of those OEM batter apps (like the LG one and even the android built-in one) are often misleading. For example, at least with 4.2.2, my phone wouldn't show "pandora" as a battery user (instead blaming 'android system.)
Of course, it's also possible that, for your environment, something really is causing BT to use up more battery than it should. There are several services related to BT, including the newer GATT/ATT (not related to AT&T) calls. (They are related to low power profiles.) It's possible that *something* in your environment is interacting with the phone or one of those services in such a way to cause issue... I'd suggest getting betterBatteryStats, install the piece needed for it to work properly with kitkat, and getting more detailed information from that. (When I say "environment", I mean the physical space around you, the software on your phone, or anything that may influence RF, light, sound, etc around your phone.)
...and I'm trying to give EXTREMELY clear and detailed instructions so that people don't have to replace their phone. In fact, my instructions take a paranoid approach.
However, your question is essentially asking if you could skip steps. Does a "cautious" person skip steps?
Well, you can - assuming you know EXACTLY which partitions are installed on your phone, EXACTLY where they came from, EXACTLY what version they are, and you are 100% sure that they all match what is required. Of course, if you already had all that information, then you wouldn't feel the need to ask the question, as you'd obviously be "geeky" enough to not even really need a recovery package to install it.
Don't come into this thread asking if you can skip steps and then say you want to protect the investment in your phone. As well, don't get an attitude with me if I don't put my entire life on hold, and spell out to you the very same directions that are on the first post on this thread. Don't want to follow them? Fine. Don't. Honestly, I could NOT care less what happens to your phone if you don't want to follow the instructions I typed out.
You can read. I know this, as your question was in the context of the thread. Are you one of those people who will install kitkat, won't bother to "factory reset" the phone, and then complain that things don't work properly?
Edit: On second thought, FlyingColors, please don't install the package from this post. I get no benefit if you do, but you've already been a burden. I'd rather you continue to use whatever "custom rom" you are using. It's obviously something you are happy with (as you don't want to restore your phone to stock), and I don't have the patience to answer questions when I've already taken the time to give the answers.
By the way, as you want "clarification": It's not a "rom." It's not even a "ROM." At best, it's "firmware." If it was "ROM", you wouldn't be able to change it. Read Only Memory.
Click to expand...
Click to collapse
Too late, I've already installed it and successfully have Kitkat. Even though you probably don't like me, thank you.

Problems going back to other rom
I was running flex rom before end flash kk end the motion sensor calibration work but doesn't work on my other roms only work on kk only. please fix

Downgrading Note Pro 12.2 Verizon from 5.1.1 to 4.4.2?

HI,
I've updated the Verizon version of the Galaxy Note Pro 12.2 and I really don't like it. There's too many instability issues that I haven't seen before! I rely heavily on the S-Note and it keeps crashing on me after a few minutes when it is opened up. I can write for a bit but then it just stops working and brings me back to the home screen. The other problem is the SD Card. I never had an issue with it before, but I am now! Sometimes it goes missing when I go into a file manager looking for a document. And it occasionally freezes up!
Oh, and the best part? I like the fact that Samsung has added the "Galaxy Apps" in this Lollipop version like it is on my Galaxy Note 4 (SM-N910F), BUT IT'S ALL IN DUTCH LANGUAGE!!!
And this is suppose to be an American model with the preference language set US English?? Go figure...
I never had this problem before with KitKat 4.4.2, and I want it back!
Now I've tried using ODIN 3.10.7, 3.07, and 3.09, but I can't get it to connect. It keeps saying "added!! removed!!" when I try to use Home-Volume Down-Power" to reboot in Odin mode.
So does anyone have any suggestions on how I can downgrade?

Did you use the OTA 5.1.1 version that was pushed out by Verizon? I took it last week and this beast is way more stable, no crashes, the SD Card works properly (I have a 128GB card) and no language problems. Try resetting your tablet and getting the OTA (again).

tdetroit said:
Did you use the OTA 5.1.1 version that was pushed out by Verizon? I took it last week and this beast is way more stable, no crashes, the SD Card works properly (I have a 128GB card) and no language problems. Try resetting your tablet and getting the OTA (again).
Click to expand...
Click to collapse
No, I didn't get it by OTA. I did it through KIES. I'm an American ex-pat living in the UK for the past few years and I had this shipped to me from family back in Florida. It doesn't seem that the OTA would work at all and the only way I could get the update is through KIES.
As for resetting, that's what I was trying to do. When I do a "factory" reset, it puts 5.1.1. back on again plus the Verizon repair app is not giving me any joy since it's doing the same and placing lollipop 5.1.1, which is why I'm going through ODIN mode to place the original ROM back onto it that I've downloaded from SamMobile's website. However, as I mentioned, Odin on all versions are giving me "ADDED!! REMOVED!!".
What I really find so strange is that the Verizon Update/Repair app will re-flash with no problem; but when trying to use Odin, it won't connect. Can someone give me a clue on what's going on with that??
It would also mentioned I'm using Odin on Windows 7 64 bit and I've used separate computers so that the drivers for KIES and Verizon Update App doesn't clash, yet I'm still getting the same messages from Odin.
OR am I missing something else??
By the way, Sammy's Galaxy Apps is still in Dutch!!

sjbrother said:
No, I didn't get it by OTA. I did it through KIES. I'm an American ex-pat living in the UK for the past few years and I had this shipped to me from family back in Florida. It doesn't seem that the OTA would work at all and the only way I could get the update is through KIES.
As for resetting, that's what I was trying to do. When I do a "factory" reset, it puts 5.1.1. back on again plus the Verizon repair app is not giving me any joy since it's doing the same and placing lollipop 5.1.1, which is why I'm going through ODIN mode to place the original ROM back onto it that I've downloaded from SamMobile's website. However, as I mentioned, Odin on all versions are giving me "ADDED!! REMOVED!!".
What I really find so strange is that the Verizon Update/Repair app will re-flash with no problem; but when trying to use Odin, it won't connect. Can someone give me a clue on what's going on with that??
It would also mentioned I'm using Odin on Windows 7 64 bit and I've used separate computers so that the drivers for KIES and Verizon Update App doesn't clash, yet I'm still getting the same messages from Odin.
OR am I missing something else??
By the way, Sammy's Galaxy Apps is still in Dutch!!
Click to expand...
Click to collapse
Did you ever get this figured out? I, myself, am having a terrible time with the lollipop upgrade on my 905V. I've tried to ODIN back to 4.2.2 with no luck. ODIN fails every time I try to push one of the older versions to the tablet.
I am like you where I had to use ODIN to upgrade to 5.1.1. I was rooted and I had done a few other things which required me to factory reset a couple times after using ODIN to install an original factory package.
It is possible we are S.O.L. There is simply no DEV support for a device few people have, I don't expect much.
My only shot to try next is to see if putting one of the older versions in a specific folder will give me an option in Kies to revert back.
There is always a chance someone will come along with the answer we need.

Lollipop haywire
I to have the Verizon Note Pro and recently did the update to lollipop and is having a horrible experience... The system seems to be unstable all my apps are crashing a lot... Ive tried to revert back to 4.2.2 using Odin as well but no luck. Ive factory reset numerous times... Ive even reinstalled lollipop several times, with no luck. If any one has any insight on what this problem is or have anyway of going about fixing the crashing, please let me know...

Has this ever been figured out? When I first got my NP 12.2 on verizon I rooted it, but then I OTA updated it, like a dummy, to 5.1.1. I want to flash back down to 4.4 or whatever version it WAS so I can root 4.4 then update to a 5.1.1 or 6.0.1 rooted rom. * Any help would be appreciated.

In the same boat
Any help on this? I would really like to downgrade my NP12.2 to Kitkat to root it.
I pretty much a novice to Android, but have 20+ years with PC and MAC. This doesn't seem like it should be that big of a deal. Thanks for any help!

Working on a Root Tool for S7/Edge T-Mobile that fixes lag, overheat etc! (OnionRoot)

So I rooted my S7 edge tmobile multiple times on 6.0.1 and did lots of testing to push the device to its limits. I soon found out that the device lags like aids when you reboot when you have it rooted. So I'm pretty close to finishing a tool that fixes all those problems. ESPECIALLY when you reboot and the CPU governor switches to performance for no reason.
Have any suggestions on what to add to the tool before release let me know! Also when you are rooting it with my tool, it will install an apk called OnionRoot. This might be added or removed from the root tool idea. Its intent is to fix lag performance and overheating. This may just be a better way of rooting your S7 without lag and what not.
Also if you are experincing any problems I didn't list when you root with the current way by chainfire, let me know to try to fix it before release.

Awesome patiently waiting
Sent from my SM-G935T using XDA-Developers Legacy app

Good ish OP. Cant wait to try it out when it's finished. If you can, try to set it so we can update supersu and its binaries.

Fix the ENGBOOT so that the issues don't exist

Click bait
Sent from my SM-G935T using XDA-Developers Legacy app

so..basically the same thing we have already been doing with kernel aduitor to set the governor then lspeed, and sefix. got ya.

silentwind827 said:
So I rooted my S7 edge tmobile multiple times on 6.0.1 and did lots of testing to push the device to its limits. I soon found out that the device lags like aids when you reboot when you have it rooted. So I'm pretty close to finishing a tool that fixes all those problems. ESPECIALLY when you reboot and the CPU governor switches to performance for no reason.
Have any suggestions on what to add to the tool before release let me know! Also when you are rooting it with my tool, it will install an apk called OnionRoot. This might be added or removed from the root tool idea. Its intent is to fix lag performance and overheating. This may just be a better way of rooting your S7 without lag and what not.
Also if you are experincing any problems I didn't list when you root with the current way by chainfire, let me know to try to fix it before release.
Click to expand...
Click to collapse
The main purpose of your solution is to fix the lag and sluggishness we experience when we use the engineering bootloader to root. If your solution makes it so that we don't have to fiddle around using any other third-party apps and have our phones run fast from the get-go, then by all means please release it ASAP! Any other enhancements can be added in future updates.

uniphase said:
The main purpose of your solution is to fix the lag and sluggishness we experience when we use the engineering bootloader to root. If your solution makes it so that we don't have to fiddle around using any other third-party apps and have our phones run fast from the get-go, then by all means please release it ASAP! Any other enhancements can be added in future updates.
Click to expand...
Click to collapse
Pretty close to finish the basics. Its a tethered root for performance fix but will be untethered before release very close to finishing. I want to make the device run lag free. Thats the goal of this modded root tool.

I rooted my s7 edge many times and the one issue I always had after a few weeks of being rooted was IMS service issue even with the fixes it would still come up which then I had to turn off volte to make calls. If you can get that fixed it would be great. This was always the deal breaker that made me go back to stock.

HiGhDRo3o5 said:
I rooted my s7 edge many times and the one issue I always had after a few weeks of being rooted was IMS service issue even with the fixes it would still come up which then I had to turn off volte to make calls. If you can get that fixed it would be great. This was always the deal breaker that made me go back to stock.
Click to expand...
Click to collapse
I've never had a problem with the IMS service. What exactly happens? Can you explain? Also you're on T-mobile S7/Edge? What processor and android OS ver?

Hurry up man! Lol jk
Sent from my SM-G935T using XDA-Developers Legacy app

So I'm guessing this is basically chainfire's ENGBOOT method with fixes already built in? Would definitely be a nice thing to have, but an unlocked bootloader would still be endgame for us. Have you considered Xposed with this? Xposed makes the phones lag a lot worse than with just root.

silentwind827 said:
I've never had a problem with the IMS service. What exactly happens? Can you explain? Also you're on T-mobile S7/Edge? What processor and android OS ver?
Click to expand...
Click to collapse
T-Mobile s7 edge android 6.0.1. I would set up device as soon as root. All the available fixes and Would work fine for many weeks but then all of a sudden IMS has stopped and could not make or receive calls on volte. Would only work with volte off. Happened 4 different times so I stuck to stock. Now on final beta

HiGhDRo3o5 said:
T-Mobile s7 edge android 6.0.1. I would set up device as soon as root. All the available fixes and Would work fine for many weeks but then all of a sudden IMS has stopped and could not make or receive calls on volte. Would only work with volte off. Happened 4 different times so I stuck to stock. Now on final beta
Click to expand...
Click to collapse
Have you tried to restore to default settings with recovery AND flash AP, BL, CP, and CSC with odin? That should fix it. Maybe try OnionRoot, I dont know how you're rooting your device this might be a fix. I've never had that problem come across, I have the same exactly device.

silentwind827 said:
Have you tried to restore to default settings with recovery AND flash AP, BL, CP, and CSC with odin? That should fix it. Maybe try OnionRoot, I dont know how you're rooting your device this might be a fix. I've never had that problem come across, I have the same exactly device.
Click to expand...
Click to collapse
I tried it all. Went to stock and re rooted 4 times and always happened to me On 2 devices so I stayed stock at the end

HiGhDRo3o5 said:
I tried it all. Went to stock and re rooted 4 times and always happened to me On 2 devices so I stayed stock at the end
Click to expand...
Click to collapse
Try titanium back up and freeze ims service. I don't think that might help but it's worth a shot

CosMiiK said:
So I'm guessing this is basically chainfire's ENGBOOT method with fixes already built in? Would definitely be a nice thing to have, but an unlocked bootloader would still be endgame for us. Have you considered Xposed with this? Xposed makes the phones lag a lot worse than with just root.
Click to expand...
Click to collapse
Didn't mess around too much with engboot. I need to figure out how to fix it to make performance better and battery

ShrekOpher said:
Fix the ENGBOOT so that the issues don't exist
Click to expand...
Click to collapse
I will look into it more and try to solve the problem why the device lags due to engBoot.tar or whatever we call it lol.

CosMiiK said:
So I'm guessing this is basically chainfire's ENGBOOT method with fixes already built in? Would definitely be a nice thing to have, but an unlocked bootloader would still be endgame for us. Have you considered Xposed with this? Xposed makes the phones lag a lot worse than with just root.
Click to expand...
Click to collapse
No fixes in ENGBOOT yet, BUT there are solutions I am working on right now. I know the problem lies in ENGBOOT.tar. Right now the OnionRoot app fixes the governor on start up after a complete boot up sequence.

MorePAIN said:
Hurry up man! Lol jk
Sent from my SM-G935T using XDA-Developers Legacy app
Click to expand...
Click to collapse
Its released for testers now. OnionRoot early release for testers

Do you really need the latest security patch? and other thoughts for newbies et al

By all means, read @Neffy27 's FAQ if you are starting out. even as a refresher for stuff you may have forgotten.
-But do think a bit about what you are doing:
-Do not modify your phone unless you are willing to toss it into the trash, as that could well be the result, no matter how well planned.
-Always have a spare on hand. I used my old Moto G3 when my MZP died suddenly. Worked just fine. You know, things really haven't changed all that much since Gingerbread...
-If you are going to be getting the latest OTA stuff by doing a full flash you might want to reflect on just how much, or little, you would gain. We all like to think that if we have the latest security patch we are somehow more safe, though I don't believe I have ever heard of a phone being affected by something just because it is not on the latest patch. I was running my old Moto z play on an aug '18 (if I remember correctly) patch with no problems up until a few weeks ago when it was done in by an expanding battery envelope which cracked the display. Consider, also, that many of the custom roms that are available are not updated at all - it takes a ton of work to try to get/keep a custom ROM current, AND working! Yet you never hear of viruses or the like.
- Be aware that if you modify ANYTHING on your phone, even as little as a new boot logo to cover up the unlocked bootloader message, you will prevent your phone from taking any further OTA updates. Some mods, like adding TWRP, may still allow it to try to download and install an OTA, but when it reboots to finish that install, it will fail since it needs to re-boot through stock recovery to complete. And it will continue offering you that update.
- There is a difference between the partition structure in our phones on 8.x, and those on 9. 9 is not full Treble, only a "partial" Treble, and really only the addition of a second set of partitions which OTA updates can use to update the system - instead of modifying the single partition set, it modifies the other (a or b) set and boots to that on update completion. If it fails it can always boot the other set. Theoretically! Makes it safer than the old way of doing OTA updates, but this may cause problems if you try to flash a 2 partition set phone with a single partition set ROM. I don't believe anyone has run any experiments on this, so YOU, when you flash things without thinking about the situation, may get an unusable phone. I do not know the answer here. If you read these forums which detail other's problems, you may trod a bit more hesitantly!
-The idea here is to have fun, and sometimes to experiment with new things. To a newbie, losing the use of a $200 phone can be a tough life lesson. Let's help them out by helping them to be cautious!

Agreed. I've been running stock with January 2018 patch, TWRP installed and Magisk for root and successful safety net bypass.
I'm looking to see if running Lineage will help streamline any update processes. It looks like they have their own recovery too.
Maintaining root has become a pain in my ass the past few years.
Sent from my moto x4 using Tapatalk

SR3TLAW said:
Agreed. I've been running stock with January 2018 patch, TWRP installed and Magisk for root and successful safety net bypass.
I'm looking to see if running Lineage will help streamline any update processes. It looks like they have their own recovery too.
Maintaining root has become a pain in my ass the past few years.
Sent from my moto x4 using Tapatalk
Click to expand...
Click to collapse
I would be careful about lineage as folks don't seem to be able to get back to stock from it.
I agree about maintaining root. I will likely just stay on stock with this one.